You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
This is largely a migration of Osmose 1070/1220 (waterway overlaps, waterway intersecting waterway without junction, unconnected waterway, and closed waterway).
Requirements
Is an Edge or a Line (logic should use LineItem where ever possible), since waterways may become an Edge in the future (specifically navigable waterways, so rivers, not small streams), and has valid waterway water values.
Use Cases
This section summarizes the various use cases for this check and provides potential enhancement suggestions if needed. The uses cases should act as a test in a way, such that when the analysis/enhancement is completed, these types of use cases should be found or eliminated.
For each use case, please add a screenshot of the feature & openstreetmap.org link (or other sources). If necessary, edit the screenshot to better illustrate the use case.
This should not be flagged, since sinkholes act as an exit for waterways. Note that this is apparently not a sinkhole (see the description tag, but that is a separate issue).
This should be flagged, if the layer tags are the same. This example has a duplicate node at the crossing location as well, but that should not be necessary.
This should be flagged. Waterways must have a sink. Multiple waterways may deadend into each other (so converge into a dead end). For the purposes of a navigable network, a waterway ending on a water area is considered a dead end (see linked way).
Further investigation
A sample region needs to be tested to see what the approximate false positive rate is. Belize had 311 flags for the standard waterway checks.
Supported regions
All countries
What's not supported (optional):
This check is not currently doing area checks (so riverbank without river, crossing waterway areas, since the crossing waterway areas currently has a bug whereby two areas sharing a point is considered an intersection).
Description
This is largely a migration of Osmose 1070/1220 (waterway overlaps, waterway intersecting waterway without junction, unconnected waterway, and closed waterway).
Requirements
Edge
or aLine
(logic should useLineItem
where ever possible), since waterways may become anEdge
in the future (specifically navigable waterways, so rivers, not small streams), and has validwaterway
water values.Use Cases
This section summarizes the various use cases for this check and provides potential enhancement suggestions if needed. The uses cases should act as a test in a way, such that when the analysis/enhancement is completed, these types of use cases should be found or eliminated.
For each use case, please add a screenshot of the feature & openstreetmap.org link (or other sources). If necessary, edit the screenshot to better illustrate the use case.
Example:
Case 1: Sinkhole area (Colorado, US)
Case 2: Sinkhole point (Utah, US)
description
tag, but that is a separate issue).Case 3: Closed waterway (Colorado, US)
natural=water
+water=canal
instead ofwaterway=ditch
(it looks more like a canal than a ditch).Case 4: Waterway ending in an ocean (Florida, US)
Case 5: Waterway crossing waterway (Colorado, US)
Further investigation
A sample region needs to be tested to see what the approximate false positive rate is. Belize had 311 flags for the standard waterway checks.
Supported regions
All countries
What's not supported (optional):
This check is not currently doing area checks (so riverbank without river, crossing waterway areas, since the crossing waterway areas currently has a bug whereby two areas sharing a point is considered an intersection).
References
The text was updated successfully, but these errors were encountered: