[mkgmap-dev] Splitter Error

Mon Mar 11 20:44:37 GMT 2013

Do you see a chance to implement an option to control the order of data in the img file?

In our experiments tweaking the order of data in the osm file did have an influence on draw order. But as you described the influence was more or less random.

For rendering shaded depth areas in a sea map it is absolutely necessary to make sure that the depth area polygons are drawn on top of sea or riverbank polygons and not below them.

As another approach to this problem I was thinking about leaving away the sea polygons at all (so they do not cover my depth shading) and creating Bluechart type maps instead of topo maps. As far as I understand, the difference between Bluechart and topo is that blank unmapped areas are rendered as water on a Bluechart but rendered as land on a topo map. So we need sea and riverbank polygons on topos but on a Bluechart we need land polygons. Unfortunately as mkgmap can only generate sea polygons and no land polygons, this approach is out of reach at the moment.

> Hmm,  --preserve-element-order only makes sure that (most of) the data is
> always processed in the same order. I doubt that you can really influnce the
> order of data in the img file. The algorithm that is used to distribute data into
> the sub regions is likely to randomize the result for each small change in the
> style or osm data.
> 
> Gerd
> 
> 
> 
> --
> View this message in context: http://gis.19327.n5.nabble.com/Splitter-Error-
> tp5752745p5752814.html
> Sent from the Mkgmap Development mailing list archive at Nabble.com.
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev