[mkgmap-dev] splitter-r269 - problems with osm-data and srtm-data

Sat Dec 22 12:26:27 GMT 2012

Hello Henning,

I did not yet look closer at this, but I guess the reason is that the srtm
data increases the nodes for a tile so that splitter has to split it. After
that, probably, one small tile contains almost all nodes and the other large
one only a few. Maybe it helps if you use a slightly higher max-nodes value. 

Gerd

Henning Scholland wrote
> Hi,
> I've got some problems with actual splitter and a combined input of osm 
> and srtm-data. I merged them with osmconvert, so I think they are not 
> mixed(--mixed gave the same result as without --mixed).
> 
> I use splitter with an polygon-file of New Zealand [1] and 
> max-nodes=1000000, which is no problem if I use only osm-data as input. 
> Splitter generates thefollowing density-map [2] and then ends with the 
> message:
> 
> Failed to calculate areas.
> Sorry. Cannot split the file without creating huge, almost empty, tiles.
> Please specify a bounding polygon with --polygon-file parameter.
> 
> Tiles should get smaller with srtm data, so my guess would bethat the 
> tiles, which covers parts of the sea could be problematic.If you need 
> further information, let me know.
> 
> Henning
> 
> [1] http://www.aighes.de/data/NewZealand.poly
> [2] http://www.aighes.de/data/densities-out.zip
> 
> _______________________________________________
> mkgmap-dev mailing list

> mkgmap-dev at .org

> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

--
View this message in context: http://gis.19327.n5.nabble.com/splitter-r269-problems-with-osm-data-and-srtm-data-tp5741485p5741487.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.