[mkgmap-dev] Mkgmap dropping data: Area too small to split at...

Sat Jun 18 17:26:49 BST 2011

Hi!

WanMil wrote:
> 
> The only possible solution is to split the polygon so that it contains 
> less points (either by selecting the splitter split points or by 
> changing the osm data). But that's a try and error solution.
> 

Thanks for the information. In that thread you have been discussion
subdivision a lot, but to me it looks like mkgmap does not do any
subdivision on the objects themselves - it just keeps making the area
smaller but adding all items to the first matching area. As the objects are
very large, this does not help, they all keep being assinged to the first
area until that becomes too small.

So I take it the patch you created in January was never included?

Have you any more experiences with your patch? You mentioned that it might
not work? Are you still using it? Do you think it might work with the
current version?

Changing the osm data is no way to go - on the opposite, people keep
creating more and more such huge multipolygons. Splitting them before
calling mkgmap is what I have been trying - but I found no way to tell what
items will cause a problem.

The only practical solution seems to be that mkgmap actually splits up the
objects instead of choking on them. Is that what your patch was doing?

bye
                     Nop

--
View this message in context: http://gis.638310.n2.nabble.com/Mkgmap-dropping-data-Area-too-small-to-split-at-tp6490533p6491135.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.