Florian Lohoff

This is a 2 liner simple fix for a growing number of flagged changesets - Would be nice if we could merge and deploy this.

It seems all the lifecycle prefixes are not supported. **razed:building=*** also triggers this warning.

Topic is not the only issue here - One of the real problems is the fixed client id when connecting the MQTT broker which causes the first instance of hms-mqtt-published...

Ah - and possibly the zoom. E.g. i'd like to put images of the fire hydrants in there so i'd like to point users to the perfekt view angle and...

Example : https://www.openstreetmap.org/node/12744225963 I shortened the x/y parameters to only 3 digits. 1° is 1/360 = 0.0027 - 0.001 is 0.3° which should be enough precision. `mapillary=629714899691018&x=0.614&y=0.490&zoom=3` Works in Josm,...

TheMarex: Still fixing the pedestrian crossings you would always pass through at least 1 - going straight you pass 2 highway=traffic_signals. This is on all junctions with seperated lanes on...

TheMarex: While reading through the page i find it VERY inconsistent tagging. We typically tag junctions or intersections to mention the type of intersection regulatory e.g. highway/railway. highway/footway. Having complex...

TheMarex: I am just saying that moving the traffic_light node away from the real intersection node you loose information. And you cant get it back by heuristics.

TheMarex: Its not that complex. You aggregate all lights of the same junction via a relation so that the penalty calculation is able to know if passing multiple junction nodes...

We have the direction on the traffic lights meanwhile which is pretty established. The example crossings in https://github.com/Project-OSRM/osrm-backend/issues/1250#issuecomment-360915099 i would consider tagged wrong. If there is no "single crossing node"...