Opened 12 years ago
Last modified 8 years ago
#9440 closed enhancement
Consistent definition of ways treated as areas — at Initial Version
Reported by: | Don-vip | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | 13.12 |
Component: | Core validator | Version: | |
Keywords: | Cc: |
Description
To the simple question "does this way concerns an area", it looks like we have 3 different answers:
- OverlappingWays:
private boolean concernsArea(OsmPrimitive p) { return p.get("landuse") != null || "riverbank".equals(p.get("waterway")) || p.get("natural") != null || p.get("amenity") != null || p.get("leisure") != null || p.get("building") != null || p.get("building:part") != null; }
- UnconnectedWays:
public boolean isArea() { return w.hasKey("landuse") || w.hasKey("leisure") || w.hasKey("amenity") || w.hasKey("building"); }
- WayConnectedToArea:
private boolean isArea(OsmPrimitive p) { return (p.hasKey("landuse") || p.hasKey("natural")) && ElemStyles.hasAreaElemStyle(p, false); }
We should have a single one that matches all the cases.
Note:
See TracTickets
for help on using tickets.