[OSM-talk] [Tilesathome] Ghost water rendering in mapnik & Leaky titles in osmarender

[Andre Hinrichs]

Hi Andrew,

this is caused by the way mapnik and osmarender handle data.

Mapnik uses shapefiles which are created by the coastline checker. So
first the coastline checker needs to create new shape files and then
mapnik needs to import them. Both processes may take a few days. But it
seems, that mapnik is ok now for you area.

Osmarender is different and unfortunately does not have such an
automatism. It's done by the oceantiles_12.dat file which is mostly
maintained by hand. The two tile you speak of where set to 'mixed' which
means there should be a coastline there. If there is no coastline then
the result is not defined.

I've now set them to 'land' so when the tilesathome clients are updated
the next time they will get the new information. But this may take very
long. The last update was 2009-10-14.

I will now rerender the tiles with new data and hope they are ok
afterwards. But when some other renderer gets to this area and there was
no update in the meantime then they will get 'flooded' again.

Regards
Andre


Am Samstag, den 14.11.2009, 01:07 -0500 schrieb Andrew Sawyer:
> I have run into a problem (that can be observed in osmarender) with
> two tiles found here:
> http://www.openstreetmap.org/?lat=43.1289&lon=-70.7753&zoom=12&layers=0B00FTF
> 
> Mapnik appears to be rendering the old coastline data, dispite the
> fact that there is no continuous way for the Piscataqua River (which
> runs from the Atlantic Ocean between the Maine/NH borders) found in
> JOSM or Potlatch.
> 
> A little bit of the history of this area was that the tidal river used
> to be tagged as a natural=coastline then I uploaded new data with
> waterway=riverbank.  I caused some issues with the data, but ended up
> cleaning the area up.  Unfortunately, there is still what appears to
> be two tile leaks of water.  I isolated the area with the other
> waterways and can not locate any ways/nodes that would be contributing
> to this error.
> 
> Is there some issue with the servers or the fact that it used to be a
> coastline for why the waterway is still showing up? Could someone
> address the apparent ghost data so I can go ahead and repair the
> current waterways, so that they are rendered with the new data I
> replaced the old with (before deleting to find the problem with the
> leaking titles).
> 
> Or is this a matter that is solely on the rendering side and nothing
> to do with OSM?
> 
> Sincerely,
> 
> Andrew S. Sawyer 
> http://www.facebook.com/assawyer
> 
> _______________________________________________
> Tilesathome mailing list
> Tilesathome at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/tilesathome