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
the stream in question is about 1.3k in length according to id. The stream does terminate in a node which is shared with a water area. I thought perhaps the issue was an old school tagging of that way as waterway=riverbank, but that is not the case. It has a proper tagging of natural=water,water=rapids.
So I am at a loss to identify the issue in the tagging so suspect a bug.
Cheers
scarapella
The text was updated successfully, but these errors were encountered:
I noticed that there are a few endpoints on the endpoint map which seem to have a surprising amount of upstream. For example
Node 1153529364 (josm) has 485559 km of upstreams and ends here
the stream in question is about 1.3k in length according to id. The stream does terminate in a node which is shared with a water area. I thought perhaps the issue was an old school tagging of that way as waterway=riverbank, but that is not the case. It has a proper tagging of natural=water,water=rapids.
So I am at a loss to identify the issue in the tagging so suspect a bug.
Cheers
scarapella
The text was updated successfully, but these errors were encountered: