ähm, jetzt sind's schon wieder 2 coastlines?

http://tile.openstreetmap.nl/coastlines.html?lat=28.22291&lon=-15.48275&zoom=11&layers=B00T
zeigt das problem sehr schön.
(ich habe allerdings schon einiges gefixt, sollte also beim nächsten durchgang besser aussehen (in ca. 2h)

Es würde extrem helfen, wenn nur eine coastline vorhanden wäre, anstatt mehreren gestapelt...

I suspect you are waiting for renderings to appear? That will take a while.
please do have a look at the FAQ.
And please use clear language when referring to GPX tracks and traced OSM ways.
Potlatch the Editor loaded by the "Edit" tab doesn't have a "save" button because you're editing live data. Commit happens on deselect. Please do read the help of that, too.

Probier einfach mal JOSM aus...
Nicht ganz trivial, aber es lohnt sich ein bisschen Einarbeitung zu investieren.

If it jumps back to the correct position, simply move it manually a tiny bit back and forth, that might save it at the correct position.

Unbedingt den Mapper fragen, woher er die info "Hutteneichweg" hat, wenn er nämlich Quellen die dem Datenbankrecht, bzw. Urheberrecht unterliegen angezapft hat, müssten seine Edits alle überprüft oder komplett gelöscht werden.

Ob per JOSM gelöscht, oder per Potlatch macht für die Undelete-Funktion von potlatch keinen Unterschied.

area=yes gehört da nicht hin.

The autorequester is currently backlogged a bit. A manual request via informationfreeway will always speed up the tile updating process, as manual requests are put into a different priority queue that is handled before the autorequest queue.

The 12 GB figure *is* a tile basically completely mapped out. however the amount of such tiles will grow in the future.
The basic bottleneck of t@h, next to the server, is the transformation from svg->png. There are simply no light-weight but sufficiently feature-complete working svg rasterizers.

no, not redundant, but more the "debug" layer, or "show me everything" layer. As a lot of Map_Features is still not rendered.
Unfortunately I'm not that well versed in db stuff so that I can work on mapnik, however I can work to make tiles@home better, so I do that.

Just to clarify I'm not just another t@h user, I'm the de-facto lead client developer.
Just passing on tiles the client can't render would mean several tiles do not get rendered at all. So a more general solution needs to be found.
or/p looks promising on that aspect, it could make B) workable.

...and then there is openaerialmap, which might just work, if enough aerial photography enthusiasts work together...

if you want to watch your nodes you can tag them and watch them through the OSMXAPI osm.wiki/index.php/XAPI However I will wait for a proper implementation by bbox or polygon.

This comparison shows that some google tiles seem to lack that error
http://geo.topf.org/comparison/index.html?mt0=tah&mt1=googlehybrid&lon=-122.1243611&lat=52.120836&z=15

@tyll it is.
informationfreeway can also show the mapnik layer.

Deelkar, Bremen
53.0952°N 8.8652°E

A bike is the near perfect mode of transportation for mapping!

Looking forward to your additions.

Deelkar, Bremen
53.0952°N 8.8652°E

Grüße vom OSM-Pionier in Bremen
Ich freue mich immer wieder wenn ich sehe, wie die Stadt in OSM wächst :)
(Auch wenn ich selber in letzer Zeit eher wenig zum mappen komme, dafür wächst Osmarender/Tiles@home prächtig...)

To Alexander: That will only update the "osmarender" and "maplint" layers, not the "mapnik" layer which is the default map.

To hjw2: The problem with newbie documentation is that anyone learning the ropes has at first trouble understanding it, because there is no good documentation, then when they have learned their way around, they don't bother updating the information. Secondly traditionally the project evolves quite fast, so any documentation would outdate pretty quickly. (The process does seem to slow down lately, so the chances for good newbie docs are getting better)