countries-states-cities-database VS array-to-xml

At $WORK I created a prototype that used https://github.com/dr5hn/countries-states-cities-database for a city/state/country typeahead widget - it was generally ok, loaded data into a read-only sqlite db that was created at container build time. We shipped it to AWS for the demo. There are some data bugs, cities in Turkey and Geneva were the top reported issues. You get what you pay for I suppose. Have not seen Geonames before this post but agree the username vs some form of api key/auth is weird.

This looks promising.. https://github.com/dr5hn/countries-states-cities-database

Depending on what you need from this package, this might be of help https://github.com/dr5hn/countries-states-cities-database

Link

The latter one, though, says that it got its data from countries-states-cities-database, which has some json files with the countries, states and cities. The cities json file is huge. I really don't think that I would ever use all of them, I would only need data from North and South America, at most.

Once you have created the resource you can reuse it as it was originally intended as an API response, but you could also use it with another Spatie package called array to xml to convert your array into an XML file instead of a CSV or Excel file.

could be done that way theoretically, but as processing input from paths to array is needed I'd rather use https://github.com/spatie/array-to-xml mentioned by @lavanderson, less work