Hi Mark, On Tue, Jan 26, 2010 at 10:53:48PM +0000, Mark Burton wrote: > > Hi Marko, > > Please try the attached patch and see if it gets rid of the "can't be > merged" error you are getting when generating sea.
Sorry, no dice. I still see several of the warnings, including the one that I reported last night: 2010/01/27 23:40:12 WARNING (Osm5XmlHandler): Way null (http://www.openstreetmap.org/browse/way/4611686018427418010) 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! In another message, you asked: > Can you please check to see whether this location is situated very > close to the corner of a tile? I am guessing that the coastline cuts > the corner of a tile and so you end up with nodes on each of the tile's > edges at the corner. Like I wrote in the message you replied to, it is at the tile border, lat=62.226562. If you go to the browse URL, the marker is very slightly SSW of a node of http://www.openstreetmap.org/browse/way/23553585 (the coastline). I would guess that this is some rounding issue. Initially, mkgmap thinks that the pre-existing node is not at the tile border and adds a node there, and later it notices that the coordinates are equal after all. The complete set of my options are: java -Xmx1024m -ea -Dlog.config=logging.properties -jar mkgmap.jar \ --family-name=foo --generate-sea=polygons -c mkgmap.args This is based on osm2img.sh at http://www.polkupyoraily.net/osm/, just adding --generate-sea=polygons. Best regards, Marko _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
