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
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).
While checking the way to load files with the report script, I noticed that the planet file has a hardcoded date:
reporter/load-historical-data/setup.sh
Line 4 in 230e3fd
Any reason why this is, or does it get automatically updated somewhere, if so where?
The text was updated successfully, but these errors were encountered: