Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Limit dual insertion in Line and Polygon table to "boundary=administrative" #4549

Closed
wants to merge 1 commit into from

Commits on May 14, 2022

  1. Limit dual insertion in Line and Polygon table to "boundary=administ…

    …rative"
    
    Hi Paul, this is a proposal for a minor change to the relation function. 
    
    Currently, if a relation is tagged as either "type=boundary" or "type=multipolygon" with a boundary tag, then the feature will end up as both a geometry in the Line as well as Polygon table. 
    
    While this is the desired behavior for administrative boundary relations to allow sophisticated Line symbology and de-duplication of administrative boundary lines of different "admin_level", other "boundary" relation types like "type=boundary and boundary=protected_area", should likely only end up in the Polygon table, not the Line table, as they usually do not represent contiguous topological connected structures, but are usually "stand-alone".
    
    This change now limits dual insertion in Line and Polygon table to "boundary=administrative" tagged features only.
    mboeringa authored May 14, 2022
    Configuration menu
    Copy the full SHA
    f174406 View commit details
    Browse the repository at this point in the history