Support type=boundary relations as native multipolygons #508
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This enables boundary relations to benefit from multipolygon inner/outer processing.
You can now treat boundary relations in one of two ways:
NextRelation
(this is good for administrative boundaries which are often coterminous)relation_function
(this is good for nature reserves, forests and other polygons)An example of the latter would be:
In essence, any relation with inner/outer roles will be processed as a multipolygon by
relation_function
, apart fromtype=multipolygon
which is processed byway_function
. To process relations other thantype=multipolygon
, writing arelation_scan_function
is still required.