Modify

Opened 10 years ago

Closed 9 years ago

#10223 closed defect (fixed)

False positive: "Missing pedestrian crossing information"

Reported by: skyper Owned by: team
Priority: normal Milestone: 14.12
Component: Core validator Version: latest
Keywords: pedestrian crossing Cc:

Description (last modified by Don-vip)

Have a strange false positive with osmwww:node/27345350. The node isolated on its own does not raise the warning.

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2014-07-03 01:36:33
Last Changed Author: Don-vip
Revision: 7283
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2014-07-02 20:36:46 +0200 (Wed, 02 Jul 2014)
Last Changed Rev: 7283

Identification: JOSM/1.5 (7283 en) Linux Debian GNU/Linux 7.5 (wheezy)
Memory Usage: 607 MB / 882 MB (234 MB allocated, but free)
Java version: 1.7.0_55, Oracle Corporation, OpenJDK 64-Bit Server VM
Java package: openjdk-7-jre:amd64-7u55-2.4.7-1~deb7u1
Dataset consistency test: No problems found

Plugin: OpeningHoursEditor (30416)
Plugin: conflation (0.1.7)
Plugin: imagery-xml-bounds (30495)
Plugin: jts (30416)
Plugin: mirrored_download (30495)
Plugin: notes (v0.9.2)
Plugin: photoadjust (30428)
Plugin: reverter (30436)
Plugin: terracer (30416)
Plugin: todo (29154)
Plugin: undelete (30416)
Plugin: utilsplugin2 (30460)
Plugin: wikipedia (30449)

Attachments (1)

josm_10223_sample.osm (1.1 KB ) - added by skyper 9 years ago.
sample file

Download all attachments as: .zip

Change History (7)

comment:1 by mkoniecz, 10 years ago

This is probably caused by two ways usable by pedestrian reaching node on road, but both ways are on one side of the road. Bing aerial indicates that in this case footway and cycleway connects a bit before road, but there are probably situations where this would be triggered by correct data.

comment:2 by mkoniecz, 10 years ago

No, this place triggers another bug. "Missing pedestrian crossing information" expects highway=crossing, but here [crossing=traffic_signals, highway=traffic_signals] is used instead that also seems to be a valid tagging. Too many conflicting values in highway tag strikes again.

Solution: "Missing pedestrian crossing information" should not be triggered also for nodes with highway and crossing keys.

Last edited 10 years ago by mkoniecz (previous) (diff)

comment:3 by Don-vip, 9 years ago

Owner: changed from team to skyper
Status: newneedinfo

I can't reproduce but we haven't changed anything to this test since your bug report.
Can you please see if you find a way to reproduce the bug?

by skyper, 9 years ago

Attachment: josm_10223_sample.osm added

sample file

in reply to:  3 comment:4 by skyper, 9 years ago

Owner: changed from skyper to team
Status: needinfonew

Replying to Don-vip:

I can't reproduce but we haven't changed anything to this test since your bug report.
Can you please see if you find a way to reproduce the bug?

It is a "info" and no "warning" and I am still able to reproduce it with above mentioned node.

Have a look at the attached example for another case.

Problem is that crossing=* should be sufficient but at least the value traffic_signal is not accepted.

comment:5 by Don-vip, 9 years ago

Description: modified (diff)
Milestone: 14.12

comment:6 by Don-vip, 9 years ago

Resolution: fixed
Status: newclosed

In 7899/josm:

fix #10223 - false positive for "Missing pedestrian crossing information"

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.