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
{{ message }}
This repository has been archived by the owner on Nov 26, 2021. It is now read-only.
GeoNames builds two files each day, modifications-$date.txt and deletes-$date.txt, where $date is the previous day. This allows for incremental updates without having to rebuild the entire table.
Having commands that download/store those text files in the meta/geonames directory, as well as separately applying those stored updates incrementally (and delete when applied, perhaps?) would be wonderful for this purpose.
Additionally, with #3, being able to specify feature types would help ensure that no attempts to update or add unneeded (or non-existent) data are made.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
GeoNames builds two files each day,
modifications-$date.txt
anddeletes-$date.txt
, where $date is the previous day. This allows for incremental updates without having to rebuild the entire table.Having commands that download/store those text files in the
meta/geonames
directory, as well as separately applying those stored updates incrementally (and delete when applied, perhaps?) would be wonderful for this purpose.Additionally, with #3, being able to specify feature types would help ensure that no attempts to update or add unneeded (or non-existent) data are made.
The text was updated successfully, but these errors were encountered: