We already have a countries table in the dictionaries schema. If we want to have proper validation, as we do in PBot, we will also need a states table that fks to countries. We also go down to county level in the collections payload schema, though I don't know if we want to validate this (all the third party options I can find skip this level and go straight to cities).
I'm wondering if we really want to maintain this geodata ourselves.
For PBot, I used an npm package (https://www.npmjs.com/package/country-state-city). This one is unmaintained, but works just fine. There are others that appear more current, no idea if they work well.
There are also apis we can access directly, though these are typically freemium.
Another option is to pull a prepackaged sql install like https://github.com/dr5hn/countries-states-cities-database/tree/master/psql.
Do we have access to ESRI's geocoding api?
We already have a countries table in the dictionaries schema. If we want to have proper validation, as we do in PBot, we will also need a states table that fks to countries. We also go down to county level in the collections payload schema, though I don't know if we want to validate this (all the third party options I can find skip this level and go straight to cities).
I'm wondering if we really want to maintain this geodata ourselves.
For PBot, I used an npm package (https://www.npmjs.com/package/country-state-city). This one is unmaintained, but works just fine. There are others that appear more current, no idea if they work well.
There are also apis we can access directly, though these are typically freemium.
Another option is to pull a prepackaged sql install like https://github.com/dr5hn/countries-states-cities-database/tree/master/psql.
Do we have access to ESRI's geocoding api?