Logo OpenStreetMap OpenStreetMap

Rendering problems

Diposkan oleh user8192 pada 8 Mei 2010 dalam English

I have been working the southwest area of Morgan Hill, California for the last few weeks and I have noticed a serious problem with the map renderers -- Mapnik, Osmarender, etc. Changes to streets take days to show up, or never show up. I go back to JOSM and check the database, and the changed data appear to be correct, but the renderers never pick them up. Even worse, the presentation varies by zoom level. I see streets and other features that have had their properties changed days earlier, and at certain zoom levels old data still persist. I'm assuming these are problems with the rendering algorithms, and not the underlying database. However, since most site visitors will see the map as a rendered presentation of the database, it seriously limits the usefulness of OpenStreetMap at present.

The weird lag or lack of proper rendering by zoom level seems to imply that the renderers are making multiple passes to render changes for a region and are somehow being interrupted in that task before all zoom levels have been covered, so the changes never show up to the end user. Perhaps this could be fixed, at least in the short term, by allowing editors to select a region, say, 1 km square or smaller, or select a specific way, and manually force the renderers to update views at all zoom levels within the box or length of the way. This could be handled as a queued background task, so as not to bog down the servers excessively.

Lokasi: Santa Clara County, California, United States
Email icon Bluesky Icon Facebook Icon LinkedIn Icon Mastodon Icon Telegram Icon X Icon

Discussion

Ulasan chillly terhadap 8 Mei 2010 pada 15:43

One simple problem can be that your browser caches the old tiles. Have you tried forcing a browser refresh? Additions and position changes seem to render in an hour or two generally in Mapnik and sometimes much quicker. I think simple tag changes, such as a name change, do seem to not trigger a re-render.

Have patience, not very long ago Mapnik only rendered once each week.

Ulasan JohnSmith terhadap 8 Mei 2010 pada 16:42

There is several algorythms that force the server to re-render tiles, however in most cases the problem is your browser is showing cached tiles.

If you click on the "perm link" link, and then hit ctrl+shift refresh this will force your browser to refresh all the tiles in view, unless the tile server is under heavy load, most changes will be re-rendered within a few minutes of the changes being made.

Ulasan 42429 terhadap 8 Mei 2010 pada 16:55

The rendering process starts if there are enough new points within this area.
There are tricks to accelerate the rendering process:

Mapnik:
Select the tile number (image URL), e.g. http://c.tile.openstreetmap.org/14/2655/6369.png and add /dirty to the URL:
http://c.tile.openstreetmap.org/14/2655/6369.png/dirty

Osmarender:
Go to http://www.informationfreeway.org/, Zoom level 12 and press R on the appropriate tile.
Osmarender assigns rendering to many computers in the whole world so it may take one or two days if your rendering process is assigned to an third-world server.

Ulasan davetoo terhadap 8 Mei 2010 pada 23:45

For what it's worth, the main map's Mapnik and Osmarender refresh time is *incredibly* quick now compared to what it was six or nine months ago; I usually see my edits show up in less than four hours. I didn't know about the above tricks to "force" a refresh, but haven't found it necessary.

(95% of my work is up around Fremont/Newark/Union City.)

Log masuk untuk meninggalkan komen