-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default whosonfirst.sqlite
to true
#460
Comments
There's at least one blocker for this: the wof-admin-lookup tests currently fail when |
Now that pelias/wof-admin-lookup#262 is fixed, I think we can set SQLite by default 😄. |
The country-specific SQLite DBs currently available for download from https://dist.whosonfirst.org have a few integrity issues. This causes problems in Pelias such as addresses in NYC or Berlin not having proper admin information. The planet-wide SQLite DB, while a little out of date, is overall more valid. While in the long term we probably want to utilize the country-specific DBs, for now it makes sense to filter them out. Fixes #469 Connects #460
The country-specific SQLite DBs currently available for download from https://dist.whosonfirst.org have a few integrity issues. This causes problems in Pelias such as addresses in NYC or Berlin not having proper admin information. The planet-wide SQLite DB, while a little out of date, is overall more valid. While in the long term we probably want to utilize the country-specific DBs, for now it makes sense to filter them out. Fixes #469 Connects #460 Fixes #437
We've done lots of testing with SQLite DBs recently. They are definitely the way of the future and already work well today. Two PRs left to merge before we can do this:
Should happen soon! |
We have been testing the SQLite download option introduced in #417 for some time, and it appears to be pretty solid.
As far as I know, the SQLite databases are the preferred distribution method for WOF data going forward.
What is left before we consider setting
whosonfirst.sqlite
to true by default?The text was updated successfully, but these errors were encountered: