Skip to content
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

why hardcoded planetfile #121

Open
stvno opened this issue Nov 24, 2017 · 2 comments
Open

why hardcoded planetfile #121

stvno opened this issue Nov 24, 2017 · 2 comments

Comments

@stvno
Copy link
Contributor

stvno commented Nov 24, 2017

While checking the way to load files with the report script, I noticed that the planet file has a hardcoded date:

planet_file_date="2017_09_27-13_04_01"

Any reason why this is, or does it get automatically updated somewhere, if so where?

@dnesbitt61
Copy link
Contributor

No reason I can think of. It does not get updated automatically. The user is able to set which version to use.

@kevinkreiser
Copy link
Contributor

The only reason it doesnt get the latest is because you have to be sure that the osmlr version in the tiles matches the version in the rest of the pipeline. Now that we do have OSMLR generation code that can update OSMLR (to deprecate some and make new ids but keep the bulk of them intact) this will not be an issue. But we havent deployed this yet in dev or production. Once that is done, we can update the script to simply get the latest version of tiles it sees (just list the contents and look at the date strings to find the latest).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants