OpenStreetMap logo OpenStreetMap

Changeset When Comment
165492965 8 months ago

Awesome! I updated a bunch of crossings as recommended. I also keep finding crossings that aren’t attached and crossing nodes that aren’t at the crossing. So I’m fixing those too. There are some map helping aids that will help find those but I’m not currently using those. I get distracted in my edits go on tangents but hopefully the end product is quality.

165492965 8 months ago

Here’s another page that seems (?) to say what I did is okay (at least not wrong): crossing=*

165492965 8 months ago

Okay based on this page now I don’t think I was wrong… but I do think OSM needs to clarify what the correct answer is:
highway=crossing

165492965 8 months ago

Also if I was wrong (I’m thinking now maybe I was as I look more at the other wiki pages), I will gladly go around and fix this. I’m not alone on this error and this error existed already in some crossings here. WOW, if this is what I’m now thinking it is, then I’ve never seen a signaled crossing correctly tagged across years of editing… I’m glad to know I’m not alone in this goof… the wiki page needs an image to clarify. Both this page and the general signal page. Of course the reasons I stated above hold but if that’s wrong it doesn’t matter. If I’m wrong I’ll immediately go to fix all these as they’re super easy to find and I’ve got sooo many others to fix that I’ve seen across the country.

165492965 8 months ago

Oops, I said one minute for each crossing but I can’t remember the exact time. It’s somewhere in my notes but I don’t have it accessible now. There might be an example posted in this beast of an article: https://nap.nationalacademies.org/read/26518/chapter/8#96

165492965 8 months ago

I so wish I could talk to you via voice as this is a big one I’ve been interested in for years now. That wiki Is exactly what I used. So here’s my thoughts…
All pedestrian push button crossings in the USA follow this and the reason for marking this is two-fold. So pushing the button tells the light to change. The navigation apps know that when a traffic signal for vehicles is next to a traffic signal for pedestrians that it only treats them as one signal when driving. The crossing node is marked as well as the pedestrian crossing itself just as mentioned in the wiki. Now why would we do this? Timing for pedestrians is seen by the length and type of crossing; timing for vehicles is seen as how many and what type of crossings there are (which is only seen by nodes, they don’t see the line of the crossing.) The pedestrian timing is actually longer when a signal is used instead of a marked crossing as average wait time to cross is increased by a minute for every crossing. It doesn’t matter if the crossing is marked or unmarked at this point. The light has changed and all traffic stops. Typically these signals also include the sound and vibration items mentioned on the wiki page. Also on this page the very first “How to map” states to use this tag for crossings, “regulated with light signals,” which seems to imply to me that this is the primary choice that the wiki editors are recommending to use when there’s a question as to which type of crossings picked.

The vehicles only see the node of the crossing and never the crossing itself. The signaled crossings also increase travel time by vehicles so the node must be marked and not just the crossing line itself.

I don’t know if I’ve made a good enough argument but I hope it’s at least good food for thought and I totally appreciate your opinions!

165492965 8 months ago

I believe this was related to railroad crossings? The tags were by there lonesome on a node that didn’t cross. I moved them to the appropriate crossing node as required by OSM wiki. I followed the wiki specifics that said they were required to be on the crossing. Hopefully that helps?