[mkgmap-dev] Sea (or lakes) issue

Fri Mar 25 06:51:32 GMT 2011

On Thu, Mar 24, 2011 at 10:36:30PM -0400, Nakor wrote:
>>I checked the coastlines and there is nothing wrong there. Now if I  
>>extract just the coastline and run mkgmap on that, every thing is 
>>fine.
>
>I take that back. I am not able to get a correct tile now for that one 
>although the coastline is correct.

Are the coastline polygons complete, or does your map extract end in the 
middle of the tile? Did you try enabling some warnings, like this:

cat > logging.properties << EOF
.level=WARNING
uk.me.parabola.mkgmap.build.MapSplitter.level=WARNING
handlers: java.util.logging.FileHandler
java.util.logging.FileHandler.level=FINE
java.util.logging.FileHandler.formatter=uk.me.parabola.log.UsefulFormatter
java.util.logging.FileHandler.limit=5000000
java.util.logging.FileHandler.count=4
java.util.logging.FileHandler.pattern=mkgmap.log
java.util.logging.FileHandler.append=false
EOF

java -Xmx1024m -ea -Dlog.config=logging.properties -jar mkgmap.jar ...

After the run, search mkgmap.log.0 case-insensitively for "coastline" 
and "polygon".

This is based on my logging.properties file (available from 
http://www.polkupyoraily.net/osm/), which I in turn adapted from an 
email here a long time ago.

The JOSM validator does not find all errors that mkgmap does. For 
example, if you have two islands on top of each other, or an island in 
the mainland, JOSM will not complain, unless two natural=coastline ways 
intersect. mkgmap will notice the land-on-land situation and complain.  
(For water-on-water, it will warn and convert the anti-island to an 
island.)

	Marko