Proposed features/Site Perimeter
|Status:||Draft (under way)|
|Definition:||A role for Relation:site bringing areas to the relation.|
The area should be treated as being tagged according to the main tag of the site relation.
There are three conditions:
- The main tag of the site relation must be suitable for use as an area.
- The perimeter way can be tagged as a typical closed way (e.g. barrier=fence) or be without tags, but must not be tagged as area itself (e.g. landuse=*).
- Elements within the perimeter should not be additionally added to the relation as implementations can perform an is-in-polygon test to determine what elements belong to the site.
A site relation should NOT be used in cases where the elements are inside one or more areas where the perimeter can be tagged with an appropriate area tag. But often some elements of a site are inside one or more areas, while other elements are not. This proposal tries bring the both worlds site relations and areas together.
|Way or Node||Role||Recurrence?||Discussion|
|perimeter||zero or one||Closed way or untagged multipolygon encircling a subset of the site. Elements within should not be added to the relation.|
Relations of type site.
Should be rendered as if it was an area on its own according to the main tag.
New role for type site.