False positive: "Missing pedestrian crossing information"

[skyper]

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)

[mkoniecz]

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.

[mkoniecz]

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.

[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?

[skyper]

sample file

[skyper]

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.