|
Hi, newbie here, I read all the stuff before making edits. In the 3rd most zoomed in level only, a select few of the ways I edited are displaying back broken in the view tab. Looks like I'm getting some pre-edit tiles mixed in with post edit tiles. This only appears in the 3rd zoom level all higher and lower resolution zooms render correctly. Also on the edit tab, potlatch 1 and 2 both render correctly in all zoom levels including the 3rd. I do not notice this phenom anywhere else outside of the bounding box of my edits. The fact that it displays correctly in higher resolution would seem to rule out data problems. Is this an artifact of batch update in progress? Or did a batch update fail? My edits have time stamps in the history tab whereas they remained "still editing" for a while. Still the same observation. Just thought I'd provide that tidbit if it helps explain any timing issues. In case it helps my changesets are: http://www.openstreetmap.org/browse/changeset/6856207 and http://www.openstreetmap.org/browse/changeset/6856085 Also these updates ran in a superset of my bounding box: http://www.openstreetmap.org/browse/changeset/6853644 and http://www.openstreetmap.org/browse/changeset/6856059 while I was in the process of editing. How does OSM handle locking and concurrent edits? Normally, one would get a "data updated by another user" error in a typical database transaction. If this is the issue will the tiles get re-rendered automatically? Or does it require a manual fix? The edits were made in potlatch 1. In potlatch 2 when I select osmarender for the background the whole background shows all pre-edit tiles not the mixture as sene in the view tab. That's about all the data I have to offer. Can anyone explain this observation? Thanks! |
|
Different zoom levels may render at different times. It is possible that your updates have appeared at one zoom level, but they have not been rendered for other zoom levels yet. (Alternatively it could be simply that your PC is caching the old tiles - clicking the permalink link, and then clicking refresh in your browser may fix this.) Mapnik and Osmarender do rendering slightly differently. See this page in the Wiki for more information. Thanks E! It looks like it was a combination of both scenarios you described. I had waited about 30 minutes for it to update that zoom level and got impatient and viewed the same inconsistency in IE (was originally working in firefox). So at that time it was probably a zoom level update timing issue and not a caching issue. But my display finally got corrected once I performed your permalink suggestion just now. So at some point it became just a caching issue. I will keep that in mind in the future. Again, thanks!
(04 Jan '11, 07:26)
ducnbyu
If the reply answered your question please mark it as "accepted" to close the question. This removes it from the pool of "unanswered questions" that still need an answer. Thank you.
(04 Jan '11, 07:31)
petschge
|
