GeoNames Dump (auto-)update issues
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript, node.js
Research direction
Start by tracing the GeoNames refresh logic that manages the geonames_dump directory and checking how timestamped filenames are interpreted. Verify whether an existing dump is refreshed, then define the supported manual and scheduled update behavior and document what completion looks like, including whether updates can avoid service downtime.
Written by the indexing model from the issue text.
Description
Hi there! Thanks for this app!
I am trying to understand how the Geonames dump config works.
You say:
By default, the local GeoNames dump data gets refreshed each day. You can override this behavior by removing the timestamp from the files in the ./geonames_dump download folder.
But that does not seem to apply.
I say that because I didn't remove the timestamp from the files in geonames_dump, but they also do not seem to have received any updates in the past 2 months.
This is the geonames_dump structure (I am disabling some admin-codes on init)
$ tree geonames_dump/
geonames_dump/
|-- admin1_codes
| `-- admin1CodesASCII_2018-06-08.txt
`-- cities
`-- cities1000_2018-06-08.txt
The files and folders on the dump directory also have the same date/time of 2018-06-08 as their names imply.
So my main questions are:
- Is the described functionality of auto-update disabled or broken?
- Am I right to suppose it is not updating?
- How would I manually update the dump?
(just move/remove the geonames_dump folder and run?) - Is there any way to config the updates? (eg. make it run monthly)
I am a bit new to node.js and could not really find many hints on the code at this point.
It would be nice to have a way to initialize a new dump while still using the old one as well (no downtime on the service). Should be easy to just do it all on a temporary folder and then move it when done, right?
Edit: I just would like to make sure it does not update everyday, but also make it update each 3 months (4 times per year seems more than fine for city limits, having a force-update feature would also be usefull).
Cheers!
Gus
- Dominant language
- JavaScript
- Stars
- 217
- Forks
- 58
- PR merge metrics
- No merged PRs in 30d
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from tomayac/local-reverse-geocoder
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
tomayac/local-reverse-geocoder#86 · 3 comments ·
All issues in tomayac/local-reverse-geocoder
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
bigskysoftware/htmx#4147 ·
Maintainers usually reply within 5 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
vshymanskyy/StandWithUkraine#316 ·
-
bug/1-unconfirmed kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
521xueweihan/HelloGitHub#4010 · 2 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100