Opened 12 years ago

Last modified 11 years ago

#9245 closed enhancement

detect nodes with unneeded highway=crossing — at Version 11

Reported by: mkoniecz Owned by: team
Priority: normal Milestone:
Component: Core validator Version:
Keywords: Cc:

Description (last modified by mkoniecz)

Detection would be very similar to http://josm.openstreetmap.de/ticket/9141 - but with "node that may be left by foo in at least two directions" replaced by "node that may be left by foo in at least one direction" (crossing terminating footway/cycleway sometimes happen, also some people may stop mapping feature at this point).

And main check would be:

first rule:

" Any node with (((without foot access AND without bicycle access) OR (without road)) AND (with highway=crossing)) should be reported as "highway=crossing is probably not needed here"."

second rule:

" Any node with (((without foot access AND without bicycle access) OR (without road AND without railway=*)) AND (with crossing=no)) should be reported as "crossing=no is probably not needed here"."

Change History (11)

comment:1 by mkoniecz, 12 years ago

Description: modified (diff)

comment:2 by mkoniecz, 12 years ago

Description: modified (diff)

comment:3 by mkoniecz, 12 years ago

Description: modified (diff)

comment:4 by skyper, 12 years ago

How to map a simple crossing for pedestrian then ?
You have a road with sidewalks on both sides and a crossing without any connected way.

in reply to:  4 comment:5 by mkoniecz, 12 years ago

Replying to skyper:

How to map a simple crossing for pedestrian then ?
You have a road with sidewalks on both sides and a crossing without any connected way.

I assume that problem is caused by not covering fact that footways may be tagged using sidewalk key. This can be handled by adding "AND (without sidewalk tag OR sidewalk=no OR sidewalk=none)" to "without foot access" check.

comment:6 by royas, 12 years ago

Neither missing sidewalk tag nor sidewalk=(no|none) means that there's "no foot access". Pedestrians can use roadside and there's can be marked crossing for them.

comment:7 by mkoniecz, 12 years ago

I never encountered something like this in my country. So it probably should be reduced "highway=crossing node, not on road" (I encountered this type of problem).

comment:8 by royas, 12 years ago

That will be better. But what with crossing with railway=tram? Here's overpass query for nodes you talk about - quite a lot: http://overpass-turbo.eu/s/1rb

And here's example of marked crossing on road without sidewalks, just roadside: http://goo.gl/maps/MNQyX

comment:9 by mkoniecz, 12 years ago

@royas - thanks for query.

I added "living_street" as road with potential crossings (may make no sense but it frequently happens in Poland).

According to http://wiki.openstreetmap.org/wiki/Railways highway=crossing is not the proper tag and railway=crossing should be used (automated fix may be a good idea here).

Also, during checking results of query 4 were obvious problems (4 - existing crossings on living_street, 8 - should be converted to railway=crossing).

My edits resulted from query:

http://www.openstreetmap.org/browse/changeset/18783800

http://www.openstreetmap.org/browse/changeset/18783764

http://www.openstreetmap.org/browse/changeset/18783741

http://www.openstreetmap.org/browse/changeset/18783664

comment:10 by skyper, 12 years ago

Summary: detect nodes with unneded highway=crossingdetect nodes with unneeded highway=crossing

comment:11 by mkoniecz, 12 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.