You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Who's on First team now publishes country specific whosonfirst-data-admin-$$-latest.db SQLite databases.
These new files could be used to limit the amount of data needed for regional builds. This is a common request since the planet DB is quite large (27GB as of this writing).
There are at least a few considerations:
The XX and XY databases would probably always have to be downloaded, as they include records with either disputed or unknown countries.
We would likely need to keep the importPlace configuration parameter and add a countries parameter or something similar. I don't think it's possible to determine what the country code of a specific record or set of records passed to importPlace. So we have to make sure the experience is still good for users who specify invalid combinations of importPlace and country.
The text was updated successfully, but these errors were encountered:
Yes this is definitely happening this quarter but unfortunately isn't the sort of feature that usually attracts sponsorship funding and so it's a lower priority than some other features right now ;(
It took an entire infrastructure (now sponsored by Geocode Earth) to generate proper country bundles, as well as some tweaks to the importer code here.
But you can now set the imports.whosonfirst.countryCode property to a 2-letter country code (as described in the readme). If anyone has any issues don't hesitate to let us know.
The Who's on First team now publishes country specific
whosonfirst-data-admin-$$-latest.db
SQLite databases.These new files could be used to limit the amount of data needed for regional builds. This is a common request since the planet DB is quite large (27GB as of this writing).
There are at least a few considerations:
XX
andXY
databases would probably always have to be downloaded, as they include records with either disputed or unknown countries.importPlace
configuration parameter and add acountries
parameter or something similar. I don't think it's possible to determine what the country code of a specific record or set of records passed toimportPlace
. So we have to make sure the experience is still good for users who specify invalid combinations ofimportPlace
andcountry
.The text was updated successfully, but these errors were encountered: