
15 Nov
2011
15 Nov
'11
9:34 a.m.
On Mon, Nov 14, 2011 at 10:57:02AM +0200, Marko Mäkelä wrote:
Could mkgmap please issue a warning when it notices that a natural=coastline way is connected to a natural=coastline way that runs in the opposite direction? I will file a similar bug against JOSM.
http://josm.openstreetmap.de/ticket/7061 has a working patch for the validator, so I guess this one does not need to be addressed in mkgmap unless it is very easy to do. My standard workflow for coastline errors (and yes, mkgmap did produce them, but they were unhelpful in this case) is to extract the natural=coastline ways from the map extract (splitter input) with Osmosis, and then run JOSM Validator on it. Marko