Hi Minko, there are two places in the source that filter the data: In ProblemListProcessor.java we select on relations with one of these types: WANTED_RELS = {"restriction", "multipolygon" ,"through_route"}; Other relations are not passed to the keep-complete routines. So, yes, type=multipolygon relations are handled by the routine. Reg. performance: please see this thread: http://gis.19327.n5.nabble.com/splitter-relations-to-be-checked-with-keep-co... Gerd Minko-2 wrote
I don't want to code a complex rule parser, but I can probably add an option to enable the keep-complete function also for all type=boundary rels. (If you don't want to edit the source as suggested)
Gerd
Editing the source is too complicated for me ;-) I don't know if adding type=boundary relations will have a big negative impact on the performance? Some boundaries are tagged as type=multipolygon, are they handled at the moment by the keep-complete function? _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Commit-r2478-Use-outer-polygon-tags-if-the-mu... Sent from the Mkgmap Development mailing list archive at Nabble.com.