Sonds like an easy workaround without to much data, which have to cached. A manual list would be a good thing, because mainly you as a user know, which polygons are problematic. Maybe mkgmap could throw out a csv-list of each polygon and multipolygon, which is causing problems. r<id>, <link to object > (for mp) w<id>, <link to object> (for p) So the user could have a view to the polygon and could start after checking the list a second run. Of course it won't help, if you don't use a fix areas.list Also wo could start a wiki-page and collect problematic objects. Henning Am 21.09.2012 14:59, schrieb toc-rox:
If a list with the IDs of all huge polygons is helpful, such a list could perhaps created by - user (manually) - mkgmap (automatic)
Regards Klaus