So in general, intersections are not supposed to be blocked, and it’s redundant to think about tagging such rules. For major intersections, it’s obvious (if not always obeyed…)
However in my area there are a few special cases, where extra attention is called to an intersection, maybe even a relatively minor crossing with a service road. Sometimes indicated with a traffic sign and sometimes with road markings. This is shown in Figure 3B-24 of the MUTCD 11th edition:
Good question – this is one of many big question marks on the MUTCD tagging guide. That means there isn’t a well-established tag for it so far, but there are a couple occurrences of keep_clear=* that might be contenders. You could follow that if you like it. Otherwise, if the sign is also present, you can map a traffic_sign=US:R10-7 node at the sign’s physical location.
I wonder if mappers in other countries already have a routine tag for intersections that have to remain clear. Apart from a tag that routers could consume somehow, there’s also a highly experimental road_marking=* tagging scheme that a hyperdetailed renderer could use to distinguish options B through D.
Oh I had forgotten or never saw that wiki page, thanks for the link! I’ve very much into mapping this type of thing so I’ll familiarize myself with it more.
I promote parking:restriction*=no_blocking , to be handled together with other =no_* rules. As you can see, “Do not block” is the MUTCD label. It describes the mandate and purpose more strongly.
In UK, white “keep clear” text is informational, not regulatory (cross-hatched yellow box junctions). This can be seen in the pair of keep_clear= on Haine Rd, Kent. They need to be distinguished. Way: Haine Road (886487213) | OpenStreetMap
Even more confusingly, (“school”) “no blocking” text can be printed on yellow zig-zag lines for the regulatory =no_stoppingFile:Traffic-signs-manual-chapter-5-2004-figure-22x05.svg - Wikimedia Commons
I hadn’t thought of parking restriction tagging. That would be a natural approach for the “Do Not Block Driveway” restrictions found in some states or unofficially in random places in just about every city. I’m not sure if keeping the intersection clear should really be conflated with keeping a driveway clear though.
It’s more than a reason. The parking tagging scheme does have a provision for No Stopping restrictions because stopping is a precursor to parking. But I don’t think the requirement to wait at the stop line before proceeding – effectively a prohibition against tailgating – is normally thought of as having anything to do with parking.
By the way, there’s an analogous prohibition against stopping on the tracks at a railroad crossing. Obviously that would never be a good idea, but some crossings near intersections have this sign to belabor the point. Otherwise, drivers get greedy and try to kiss the bumper of the next car that’s safely stopped beyond the crossing.
Guidance: If motor vehicle queues are likely to extend onto the tracks, a DO NOT STOP ON TRACKS (R8-8) sign (see Figure 8B-1) should be used.
Support: Locations where motor vehicles could queue onto the grade crossing include intersections where a STOP or YIELD sign is installed downstream of the grade crossing, where there is a downstream circular intersection, or where there is a pre-signal installed at the grade crossing.
