Modify

Ticket #3736 (closed enhancement: fixed)

Opened 3 years ago

Last modified 5 months ago

[Patch awaiting end of stabilization phase] Split Crossing Ways test into Crossing Ways and Crossing Waterways

Reported by: avar Owned by: team
Priority: normal Component: Plugin validator
Version: latest Keywords:
Cc: mohler@…

Description

Waterways should cross other ways (e.g. highways) without having connecting nodes. They should be left out of the crossing ways test.

Attachments

crossing-ways-ford.osm (1.8 KB) - added by avar 3 years ago.
ways crossing on a ford
3736.patch (1.3 KB) - added by simon04 6 months ago.

Change History

comment:1 Changed 3 years ago by anonymous

Use layer! Waterway also can be on bridge or in tunnel.

comment:2 follow-up: ↓ 3 Changed 3 years ago by stoecker

  • Status changed from new to closed
  • Resolution set to wontfix

When a waterway crosses a street on same layer something is wrong. Usually a bridge is missing. So this test is perfectly valid and data should be fixed.

comment:3 in reply to: ↑ 2 Changed 3 years ago by avar

  • Status changed from closed to reopened
  • Type changed from defect to enhancement
  • Resolution wontfix deleted
  • Summary changed from Leave waterways out of Crossing Ways test to Split Crossing Ways test into Crossing Ways and Crossing Waterways

Replying to stoecker:

When a waterway crosses a street on same layer something is wrong. Usually a bridge is missing. So this test is perfectly valid and data should be fixed.

Actually a layer=* is missing. It'll still flag it if there's a bridge and no layer=* tag on either objects.

In any case I'd like to reopen this as an enhancement request and ask that when ways are crossing and one of them is a waterway=* that it be reported under another category (Crossing Waterways).

Usually Crossing Ways that aren't waterways are errors in the data like a self-overlapping highway made from GPX data, or two residential streets that cross but don't share a node. Those errors are important and can screw up routing, but crossing waterways without a layer=* are something that's handled by all the renderers and no other user of the data really cares about.

comment:4 follow-up: ↓ 5 Changed 3 years ago by LamoniDave

  • Cc mohler@… added

Perhaps just a JOSM beginner question, but in the case where a road fords a waterway, would both be at the same "layer"? After all, the road traveler's (car, biker, walker, etc.) tires/ shoes/ feet "hit the road" at the same level as the water from the waterway. Is this a case where "a waterway crosses a street on the same layer" where something is not wrong? Should this produce an error? Or is there another way to represent a ford that should address this problem?

comment:5 in reply to: ↑ 4 Changed 3 years ago by avar

Replying to LamoniDave:

Perhaps just a JOSM beginner question, but in the case where a road fords a waterway, would both be at the same "layer"? After all, the road traveler's (car, biker, walker, etc.) tires/ shoes/ feet "hit the road" at the same level as the water from the waterway. Is this a case where "a waterway crosses a street on the same layer" where something is not wrong? Should this produce an error? Or is there another way to represent a ford that should address this problem?

If the waterway and road meet with a highway=ford node then crossing ways won't complain. But if there's a highway=ford way over the waterway then the test will be triggered.

I'm attaching a test file which demonstrates this.

Changed 3 years ago by avar

ways crossing on a ford

Changed 6 months ago by simon04

comment:6 Changed 6 months ago by simon04

  • Summary changed from Split Crossing Ways test into Crossing Ways and Crossing Waterways to [Patch awaiting end of stabilization phase] Split Crossing Ways test into Crossing Ways and Crossing Waterways

comment:7 Changed 5 months ago by simon04

  • Status changed from reopened to closed
  • Resolution set to fixed

In [4678/josm]:

fix #3736 - Split Crossing Ways test into Crossing Ways and Crossing Waterways

View

Add a comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'reopened'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.