|
I recently created two new trails from gpx files I recorded on my gps. After uploading the gpx files, I converted them to ways, joined them to existing trails, changed the attributes to footpath and then unlocked them. Everything seemed to work ok. When I view the area, though, they behave oddly. They are visible at some zoom levels but not others. And at some magnifications they appear as broken segments with sections missing. Did I do something wrong or is there another step I need to take? The edits are #6145636 and #6145318. They show up as "still editing." Is that a problem? |
|
The render processes that are behind the map display at www.openstreetmap.org always need some time to render each tile in all the zoom levels you can choose after you added or modified the data. Sometimes the render job is done in seconds, mostly in minutes, but it might even take hours or days when there is some trouble on the servers or when they are overcrowded. There is one way to be sure whether your data has arrived on the main OSM data server after your editing: go to www.openstreetmap.org, choose the area you have been working on ans click on the white plus-symbol (+) at the upper right corner of the screen. Besides you can choose the renderer to display the map, you can choose the "data layer" to display the objects in the OSM data as they are in the data in the right moment now. There you can check your recently added objects about their position and tagging. (More details at http://wiki.openstreetmap.org/wiki/Data_layer) |
|
The mapnik map layer takes some time to render all the tiles. During this time you can experience that some tiles are rendered with the new data and some with the old. This can cause all the symptoms. Just wait a couple of hours before the whole area is rerendered with the new data. As to the "still editing" on the changesets, it is because potlatch has not closed the changeset as it has no way to know you are done editing. After one hour of inactivity the changesets will get closed automaticly. 3
Potlatch can't automatically close the changeset when you end your session, because this is simply done by the user closing their browser window (as a result of which Potlatch will stop executing). If you want to close the changeset manually, not that it really makes much difference, you can choose 'Close changeset' from the Advanced menu or press C.
(23 Oct '10, 18:02)
Richard ♦
|
