logo separator

[mkgmap-dev] Bad performance because of complex boundary relation

From GerdP gpetermann_muenchen at hotmail.com on Tue Jun 17 10:11:58 BST 2014

Hi all,

it seems that finally someone did it :-)

I assume that this will reduce the 
size of the bounds file for this area, so maybe you have to allow 
a decrease in the size of the bounds-latest.zip file.

Gerd


WanMil wrote
> Hi Gerd,
> 
> yes, this relation takes ~40% of processing time when precompiling 
> bounds of the whole world. Simplifying it would be great!
> 
> WanMil
> 
>> Hi,
>>
>> this might be an OSM problem...
>> While working on a "beautifyRoundabout" algo I wondered why one
>> tile in Southamerica needed a very long time to calculate.
>> It turned out to be a problem in the location hook.
>> The boundary relation 1981462 is a very complex polygon.
>> I don't see a simple solution in mkgmap, but
>> wouldn't it be better to create a simple way enclosing the area
>> to map this boundary?
>>
>> Gerd
>>
>>
>> _______________________________________________
>> mkgmap-dev mailing list
>> 

> mkgmap-dev at .org

>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>>
> 
> _______________________________________________
> mkgmap-dev mailing list

> mkgmap-dev at .org

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





--
View this message in context: http://gis.19327.n5.nabble.com/Bad-performance-because-of-complex-boundary-relation-tp5784929p5808830.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.


More information about the mkgmap-dev mailing list