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
Have there been any changes recently (since April) which would have previously rejected these dodgy locations when importing? They certainly weren't appearing previously.
Unfortunately I fat fingered my previous dataset and accidentally deleted it.
Previous import was a sqlite one as well I believe.
After my latest build, a bunch of WOF nonsense has been appearing which is weird since it seems the WOF data isn't new.
I can confirm the nonsense is appearing on geocode.earth as well. https://pelias.github.io/compare/#/v1/search%3Fboundary.country=AU&text=Wyoming
Examples here: whosonfirst-data/whosonfirst-data#1649
Have there been any changes recently (since April) which would have previously rejected these dodgy locations when importing? They certainly weren't appearing previously.
Unfortunately I fat fingered my previous dataset and accidentally deleted it.
Previous import was a sqlite one as well I believe.
My WOF Import config:
The text was updated successfully, but these errors were encountered: