[mkgmap-dev] Bad performance because of complex boundary relation
From Gerd Petermann gpetermann_muenchen at hotmail.com on Mon Nov 11 09:09:07 GMT 2013
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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20131111/79e9c036/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: r1981462.png Type: image/png Size: 59239 bytes Desc: not available URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20131111/79e9c036/attachment-0001.png>
- Previous message: [mkgmap-dev] One node - two index entries?
- Next message: [mkgmap-dev] Bad performance because of complex boundary relation
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list