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
Hi guys. I'm trying to adapt this to update existing data.
Since the process is time expensive (downloading / importing), truncating and reimporting would result in DB downtime.
Geonames exposes their changes throught a modifications.txt file:
modifications-.txt : all records modified on the previous day, the date is in yyyy-MM-dd format. You can use this file to daily synchronize your own geonames database.
I guess we could run a a cronjob that fetches that file and runs the modifications.
Any idea how to tackle this?
The text was updated successfully, but these errors were encountered:
Absolutelly agree with the update you are proposing. In fact, dealing with modifications.txt file from geonames was one of the first to-dos in my list. So I'm not the only one that thinks it would be a MUST have in this script. I will achieve that issue as soon as I have some free time.
Hi guys. I'm trying to adapt this to update existing data.
Since the process is time expensive (downloading / importing), truncating and reimporting would result in DB downtime.
Geonames exposes their changes throught a modifications.txt file:
modifications-.txt : all records modified on the previous day, the date is in yyyy-MM-dd format. You can use this file to daily synchronize your own geonames database.
I guess we could run a a cronjob that fetches that file and runs the modifications.
Any idea how to tackle this?
The text was updated successfully, but these errors were encountered: