
Hi all, I've committed r285 in the problem-list branch: Changes compared to r283: the tag key "boundary" is checked against an exclude list {"administrative", "postal_code", "political"}. If a type=multipolygon rel also has the excluded boundary tag, it is no longer added to the list of problem relations. If a type=boundary rel doesn't have the excluded tag, it is now added to the list of problem relations. This is the simple solution 1b plus the mp filter. Gerd Minko-2 wrote
Ah ok, Then option two, to set your own include parameters would be nice. Or else option 1 with all administrative boundaries excluded. That would be >90% and maybe more if mp's and political bounds are excluded too.
Just to make sure: with hard coded I meant hard coded in java source, so you can't customize it without changing the source and compile the changes.
Gerd
mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/boundary-relations-in-splitter-tp5749069p5749... Sent from the Mkgmap Development mailing list archive at Nabble.com.