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 Jul 24, 2021. It is now read-only.
Reporter: lonelypixel [Submitted to the original trac issue database at 12.41am, Thursday, 22nd January 2009]
When you make changes to the map data, you need to request the Slippy Map tiles of that region so that they'll be updated on the following Wednesday. And it seems that at least I am missing this very often and so the map won't reflect my changes or is even broken at the tile borders. Requesting the Map in every zoom level for the entire affected region is an unproductive task since you won't see your changes anyway yet.
My proposal is to have Merkaartor automatically invalidate the affected map tiles by downloading them once, for all zoom levels. Or maybe for all zoom levels from 5 on or so. IIRC, there are also some status URLs to find out whether a certain tile needs updating. This could be done when uploading the map data so that the map will always be rendered with fresh data next time. If uploading data for an area more than once within a session (not restarting Merkaartor), the tiles wouldn't need to be invalidated again. (Remember a list of downloaded tiles.)
The text was updated successfully, but these errors were encountered:
Author: tom[at]compton.nu [Added to the original trac issue at 9.00am, Thursday, 22nd January 2009]
It is not true that you have to request tiles to get the rerendered. All tiles are rerendered every week.
Please do not add this feature to merkaartoor - it will just add needless load to the tile server and force it to spend time sending tiles that nobody will look at rather than rendering them.
Author: tom[at]compton.nu [Added to the original trac issue at 11.18am, Thursday, 22nd January 2009]
You would need to check with Jon Burgess, but I don't believe that description on the wiki is accurate.
As to your example, we're only about 24 hours into this weeks render so it may well not have rendered yet - rendering everything takes most of the week. Visiting the tile may have the effect of speeding that up because the server tries to rerender tiles on demand as people view them if it can. If it is too busy it will serve the old one though and the background rerender will eventually catch up with it.
Reporter: lonelypixel
[Submitted to the original trac issue database at 12.41am, Thursday, 22nd January 2009]
When you make changes to the map data, you need to request the Slippy Map tiles of that region so that they'll be updated on the following Wednesday. And it seems that at least I am missing this very often and so the map won't reflect my changes or is even broken at the tile borders. Requesting the Map in every zoom level for the entire affected region is an unproductive task since you won't see your changes anyway yet.
My proposal is to have Merkaartor automatically invalidate the affected map tiles by downloading them once, for all zoom levels. Or maybe for all zoom levels from 5 on or so. IIRC, there are also some status URLs to find out whether a certain tile needs updating. This could be done when uploading the map data so that the map will always be rendered with fresh data next time. If uploading data for an area more than once within a session (not restarting Merkaartor), the tiles wouldn't need to be invalidated again. (Remember a list of downloaded tiles.)
The text was updated successfully, but these errors were encountered: