[mkgmap-dev] [PATCH v2] - handle "anti-islands"

Tue Jan 26 21:34:06 GMT 2010

Hi Mark,

> > I tested both without and with --generate-sea=polygons.  Sorry,
> > I did not run --generate-sea=polygons without your patch.  With
> > generate-sea, I found some anti-treasure like the following.
> > 
> > 2010/01/26 22:41:52 WARNING (Osm5XmlHandler):   Way null (http://www.openstreetmap.org/browse/way/4611686018427399860) has consecutive nodes with the same coordinates (http://www.openstreetmap.org/?mlat=62.22656&mlon=25.82736&zoom=17) but they can't be merged because both are boundary nodes!
> > 
> > This looks like a generated way (bogus browse URL) and a generated node
> > at a tile boundary, lat=62.226562.  The generated node is very close to
> > a real coastline node.  Can you avoid adding a node when it is "Garmin equal"
> > to an existing node?  There are many lakes (tagged as natural=coastline)
> > at my tile boundaries.
> 
> I don't know what's happening there. This generated node you refer to,
> where's it coming from? That message comes from the short-arc removal
> code so the node was either in the original OSM data or it has been
> introduced by the sea generation or possibly by the "soft clipping"
> code. Does it go away if you don't generate sea?

Yes, it goes away if I don't generate sea.  I reran --generate-sea=polygons
without your anti-island patch:

2010/01/26 23:26:58 WARNING (Osm5XmlHandler):   Way null (http://www.openstreetmap.org/browse/way/4611686018427418078) has consecutive nodes with the same coordinates (http://www.openstreetmap.org/?mlat=62.22656&mlon=25.82736&zoom=17) but they can't be merged because both are boundary nodes!

Different generated way id, same warning.

	Marko