UK Quarterly Project 2024 Q4: Pedestrian Crossings

I believe that these are often pelican/puffin/toucan crossings, but not always.

Yes, it is possible. We have a few of these in London where the junction is controlled by traffic signals and the crossing has dropped kerbs, tactile paving and dots across the carriageway. There is no button and there are no pedestrian signals, so you have to look at the traffic lights to determine when it is safe to cross. This is where the proposed crossing:signals=shared might be useful.

The nearest example to me is Fairfield Road E3 at its junction with Bow Road Bing street side imagery

1 Like

As an aside, why does the streetside imagery for the UK somehow look like it’s from scans of photos taken in the early 90’s?

1 Like

It not possible for a junction to have pedestrian green man signals, and no call button. The call button “box” also provides crossing information for visually impaired pedestrians by means of the spinning cone under the box. (Though Local Highways Authorities will routinely break rules)

If a junction has several phases of traffic, is is possible to have call button box where the button has no effect on the traffic phases.

It is common in the UK for there to be junctions, especially T-junctions, where road traffic is controlled by signals, but there are no signals for pedestrians.
This junction is a

  • “Signal-controlled junction” for vehicles, and
  • "Uncontrolled crossing" for pedestrians.

Many (most?) drivers misunderstand the rules regarding green/red lights. The law creates a prohibition regarding crossing the White Line. You MUST NOT cross the White Line unless the light is green AND it safe to do so. Emphasis is given that you must not cross the white line if pedestrians are crossing within the junction. This means pedestrians have right of way at all times when crossing at junctions with light for vehicles, but no lights for pedestrians, but in practice drivers believe the green light gives them priority over pedestrians.

1 Like

This crossing for pedestrians is an “Uncontrolled crossing”, which I’ve talked about in my previous post. It’s a good example of a junction where pedestrians always have priority due to the presence of a solid stop line for vehicles. And as I said there is a historical problem with drivers incorrectly believing a Green Light gives them priority through the junction.

1 Like

The traffic planners (probably TfL in this case) agree with you, as the tactile paving is buff rather than pink for the crossing I gave as an example.

That leads to another question: how do we tag this to tell pedestrian/VI/wheelchair routers that traffic flow through the junction is controlled by the traffic lights, but that the crossing itself has no traffic signals?

The historical problem with driver understanding is because the Driving Theory Test is based on rigorous application of Caucus Race standards.

The dots next to a UK zebra crossing are important, right? Hence we should encourage crossing:markings=zebra;dots

2 Likes

Yes. They’re something different legally, but practically speaking there are a lot of commonalities.

There were never equivalents to pelican crossings because signal-controlled junctions in the UK have never had flashing amber phases. However the resemblance to puffin and toucan crossings is extremely strong.

The signal-controlled junctions don’t have the white zig-zag lines on their approaches. However in every other practical way they’re identical to puffin/toucan crossings. Same call boxes. Same pedestrian signals.

Near me there’s a crossroads with three effective puffin crossings and because a cycle track crosses the fourth arm of the junction an effective toucan crossing there. They’re tagged accordingly.

1 Like

Oh, joy. We’ve got a new “upgrade” being blindly implemented by Rapid users.

They’re trying to synchronise the tagging between crossing nodes and crossing ways, but unfortunately giving precedence to the tags on the way over those on the node. The result in London is that armchair mappers on other continents who will never actually use the data are unthinkingly degrading crossing=traffic_signals nodes to crossing=marked.

2 Likes

Is there anything unique in the changesets to find and revert these?

At the risk of stating the bleeding obvious, I guess you have commented on the changesets pointing them at this topic?

I will be next time I come across one.

I also need to get a screenshot of Rapid making these suggestions and raise an issue on its Github project.

1 Like

The changes tend to be made in combination with added sidewalks etc., so it’s more something to find and fix rather than revert at the changset level.

A highway=crossing + crossing=marked node may be suspicious if it’s combined with any of: button_operated=yes, crossing_ref=pelican, crossing_ref=puffin, crossing_ref=toucan, crossing_ref=pegasus, crossing:signals=yes, crossing:markings=dots, traffic_signals:sound=yes, or traffic_signals:vibration=yes.

A minority of these may really be the type of uncontrolled crossings at traffic lights discussed earlier in this topic, so aerial and sometimes street-side imagery is needed to confirm.

@rskedgell’s most recent edits morphed the table into something highly specific to the UK. That may serve this quarterly project in the short term. However, in the long term, it risks repeating the sordid history of mappers abroad diluting the meaning of UK legal terms to the point of meaninglessness.

For the semantic protection of Britain’s street fauna, I split out a UK-specific table at “Crossings in the United Kingdom” based on these edits, then reverted the original table to serve the rest of the world more generically. I also took the opportunity to distinguish between the 2018/2019 proposal and 2022 proposal, trying to show how the latter skirted around the controversy over the former. Hopefully the revised tables will be a little easier to digest and avoid the confusion that’s apparent in the revision history. Feel free to correct and expand the new UK page as needed.

2 Likes

Fine, if it spares us from silly iD-isms like crossing:markings=yes. If a mapper can see what the markings are, they should tag something useful. If they can’t see the markings, they should ignore what iD and Rapid tell them and leave the tag unset (unfortunately, they won’t).,

A table which had, and still has, a column for UK-specific crossings is UK-specific.

I agree that that should be the case, but unfortunately people keep seeing UK-specific tagging guidelines and thinking they can wantonly apply them elsewhere in a completely different context where different distinctions are needed, just because all the tags are supposed to sound like British English. That’s how both zebra and uncontrolled came to have different meanings globally than in the UK. It didn’t help that the table was located on a global page, so I spun it out to avoid confusion.

Out of curiosity, are the crossing:markings=yes occurrences making it more difficult for you to query for underdetailed crossings? Just trying to understand the practical implications so we can potentially come up with a mitigation strategy.

I think perhaps the problem with the table now at Crossings in the United Kingdom - OpenStreetMap Wiki is that it appears to classify crossing types based on marking and signal configurations in the first four columns, rather than the well-known UK crossing types.

I think it would make more sense for there to be a new column on the left called something like “Crossing Type”, that gives the animal name (where it has one) and possibly a second new column with a description of how to identify it. Then the later columns become attributes of the type, and instructions on how to tag it.

3 Likes

I’ll make this the topic of the OSM UK Online Chat next week. I welcome examples and discussion on how to find, tag and update (and what not to do?) on crossings.

1 Like

Photos of crossing thingies

Sub-projects for someone, maybe.

Types of beastie :llama:

Do we have really good photos of the following crossing_ref types?

Those pages don’t exist yet, and they should. That’s because the most findable way to document a tag properly is to give it a Tag:name=value page.

The photos will help with animal identification too.

Attributes of crossings :loud_sound: :camera:

It’d be nice to collect pairs of near+far photos of the things on a crossing that mean it should have a certain additional tag.

  • Tactile cones on newer button crossings (for traffic_signals:vibration=yes)
  • Loudspeaker grilles for ones with audible beepers (for traffic_signals:sound=walk/yes)
  • The PKD and PCDs on puffin crossings (to help identify the type, they’re not actual cameras as far as I know, some sort of IR thing?)
  • Road marking varieties in the UK
  • All of the horse and rider support stuff around a Pegasus crossing
    • local note: maybe this is one for me to look at?
    • Could use an Overpass query to find potential Pegasuses. Assume there’d be a bridleway leading up to some of them at least

Put on the right Wiki page, these photos photos would help identify the many things on a crossing. Think ahead for them being included in StreetComplete/SCEE too.

3 Likes

One thing that’s bugging me right now is that Vespucci’s presets currently have this confusing thing: a “Tactile map” checkbox under “In case of traffic signals” that results in a traffic_signals:minimap=yes.

I’ve never seen any of those in the UK. The wording, however, always makes me want to select it for the vibrating dangly cone thingy (traffic_signals:vibration=yes), which we have on almost every button-operated crossing installed in the past 20 years, if not longer.

I’ve had a go at doing this at https://wiki.openstreetmap.org/wiki/User:Rjw62/UK_Crossings . It may need some more rows adding, and the tagging columns probably aren’t complete or 100% accurate, but what do people think of the idea?

4 Likes