From OpenStreetMap Wiki
Jump to navigation Jump to search

"Connecting ways" section needs redrafting

Connecting ways

The following text is pretty unintelligible. What does it mean precisely?

Note that by default, nor footway=sidewalk or footway=crossing will either be rendered, nor taken for autorouting for any other mean of transport but pedestrian.
All ways that connect to the pedestrian crossing should therefore also connect to the main street (also highway=footway and highway=path). If you don't connect them to the main street, then add bicycle=dismount to indicate that autorouters for cyclists have to consider this way (and tell the cyclist to push his bike).
Note that for a non-sidewalk highway=footway and bicycle=no way, autorouters will assume that pushing your bicycle is possible - if then there is no connection to the next street, you break that.

I suggest redrafting this as

By default, neither footway=sidewalk nor footway=crossing on their own are sufficient for rendering or routing. To make the ways display on the map, add highway=footway. This also makes routing engines consider them for routing by foot.
Nope, that is plain wron. Of course it is sufficient for rendering. But it won't be rendered on the most popular renderers. That's all. If a renderer/maintainer wants to support it, then it is fully sufficient. Same goes for routing. DO NOT ADD highway=footway to it. That completly havocs this tag. --Extremecarver (talk) 08:01, 29 March 2013 (UTC)
For routing purposes, the ways should connect the two adjacent footways; there should be a continuous linked path from one side of the road to the other. If there is a logical highway=crossing node representing the crossing, it should be a member of both the footway=crossing way and the way describing the road being crossed.

I have omitted mentioning bikes being routed down sidewalks because this is illegal in the UK, but legal in the US. It's country-specific, and can be derived from the type of way and access tags anyway. --achadwick 14:05, 22 June 2011 (BST)

I think that sounds much better, I had difficulty understanding the original as well. Agreed about bikes, though I'm no authority in that area, as I don't even have a bike! -- Joshdoe 15:03, 22 June 2011 (BST)
Well but this is especially about bikes. If you use sidewalk tag on top, the assumption is that there is a suitable alternative for cylists. However often this is not the case, and mappers assume the cyclist to either push (this should be allowed anywhere) or just cycle a few meters on the sidewalk. So this has to be considered for ways where there is no alternative and normal footways though often not usable for cyclists, have to be considered at very low priority for routing cylists. Hence if you use sidewalk tag on a footway, note that such ways will neither be shown NOR used at all for cycling (as it would add too much clutter). This therefore means that real non sidewalk footways connecting have to have bicycle information until they touch the next street (in the form of bicycle=dismount). The above proposal completly drops this fact. it has nothing to do with the previous text and is absolutely logical (as by definition) and not needed at all to be mentioned.--Extremecarver 22:02, 23 June 2011 (BST)
I don't quite understand what you're saying. Do you support dropping the final paragraph, or would you like it to be reworded? All it's really saying is that potential direct routes need to be connected somehow, but that is is always the case in OSM. The fact you can push a bike down an otherwise untagged footway is true, and is bourne out by the routing engines I've seen, but I don't think it needs to be mentioned for crossings. It's more important to state when a bike can be *ridden* across a foot crossing. --achadwick 10:41, 24 June 2011 (BST)


Does the writer of this article live in a place where you must dismount when crossing a road in a crosswalk? This is definitely not the case in the U.S.; if sidewalk cycling is legal a cyclist has the same rights in a crosswalk, and even where sidewalk cycling is illegal (per local law) one can stay on where a separate-right-of-way path crosses a road. --NE2 15:32, 25 March 2013 (UTC)

Content removed from article

This phrase was in the main article within 'no-wiki' tagging. I am moving it here to keep the article source cleaner

All the values listed in crossing=* and crossing_ref=* are acceptable. # dubious. The crossing is already mapped as a separate note with these on it. Don't duplicate information please.

-- PeterIto (talk) 07:03, 28 March 2013 (UTC)

does footway=crossing imply cycling=yes?

-- SwiftFast (talk) 18:22, 2 May 2017 (UTC)

generally don't count on implications, be explicit. footway=crossing is a subtag for footways and has the same implications as other footways. --Dieterdreist (talk) 23:19, 2 May 2017 (UTC)
I see. I ask because it appears many crosswalks worldwide are tagged "highway=footway, footway=crossing" with no explicit cycling tag, yet in reality most crosswalks are accessible by bikes. So there appears to be a discrepancy that might confuse some bike navigation apps, unless cycling=yes is being implied. -- SwiftFast (talk) 05:08, 3 May 2017 (UTC)
I would generally add bicycle=yes if cycling is legally permitted. In Germany cycling on footway crossings is generally forbidden (you might push your bike which will make you a pedestrian), unless it is also a cycleway crossing, in which case usually bicycle=yes is added or the crossing is also tagged as highway=cycleway. In the southern parts of central Italy and in southern Italy, bicycle is always and almost everywhere permissive (while it is legally forbidden, this is not enforced, but of course if an accident happened you would be in a weak position). In northern Italy the situation is more similar to Germany. The way incomplete tagging is evaluated by applications will vary from one app to the other (might also depend on the country), that's why I would suggest to be explicit in any case, so you are on the safe side. --Dieterdreist (talk) 09:41, 3 May 2017 (UTC)

Crossing without markings

How should I tag a crossing that is not marked? For example, many residential roads do not have marked crossings for pedestrians. Yet, if the sidewalk has been explicitly drawn along those streets, you need to add the most logical crossing points for pedestrians (for example at every road crossing). This is required for pedestrian routing, otherwise the algorithm will never let pedestrians cross the road.--Pbb (talk) 14:28, 21 September 2018 (UTC)

Way or point? Way with footway=crossing, node where footway line and road intersects with highway=crossing + crossing=unmarked Mateusz Konieczny (talk) 22:26, 11 July 2020 (UTC)


@Victor.yarema: Are you sure that schema is actually accepted/used? As far as I know there is no established tagging for this (see say Proposed features/pedestrian crossing as an area) Mateusz Konieczny (talk) 13:29, 16 January 2022 (UTC)

Kerb node in the way, or last node?

I've been mapping some footway=crossings, I was using the footway=crossing to be the way between 2 footway=sidewalks, with 2 barrier=kerbs on that way. In practice this means the ends of the footway=crossing way are actually on top of the sidewalk. (And should really have a different surface=* tag).

eg: w1025588018 w1025587984 w1025587982

I've now noticed that sometimes StreetComplete adds a kerb at the end of the way, in addition to the one already tagged in the way.

eg: n9456040622 n9456040716 n9456040684

If I was to map the footway=crossing just between the barrier=kerbs, I would often end up with two tiny footway=sidewalk ways. eg, between n9456040620 and n9456040622. Are the tiny ways desirable (JOSM sometimes complains about tiny roads)? But presumably this is actually the right way?

The wiki pages doesn't really cover where the kerb nodes should be, and the images kinda suggest the ways continue after the kerb.

--CjMalone (talk) 16:56, 31 January 2022 (UTC)

@CjMalone: Are there sidewalks also to east/west on the linked crossing? "two tiny footway=sidewalk ways" - SC expects such tagging and tries to work also with other styles. In this case it got confused by combination of tagging style that it is not preferring AND incomplete mapping AND lack of fixme=continue. "Are the tiny ways desirable" - I would not say desirable but sometimes needed. With much more significant data processing SC could avoid placing duplicate curbs also in this case Mateusz Konieczny (talk) 22:07, 1 February 2022 (UTC)
@Mateusz Konieczny: The sidewalks do continue, currently tagged as sidewalk=both on w1027981 and w38811205, I hope to get around to turning that into some footway=sidewalks soon. On which nodes should I have placed fixme=continue?
"On which nodes should I have placed fixme=continue?" ones that got fake curbs (and where footway lines would continue), I think Mateusz Konieczny (talk) 23:17, 1 February 2022 (UTC)
It also looks like 1025587993 was never promoted to get duplicate barrier=kerbs, it connects to footway=sidewalks, but a node in the middle, not the end of the way. Presumably that's why StreetComplete treats it differently? --CjMalone (talk) 22:44, 1 February 2022 (UTC)
It is skipped due to footway=crossing - see and in general @CjMalone: Mateusz Konieczny (talk) 23:17, 1 February 2022 (UTC)
They all have footway=crossing. w1025588018 and w1025587993 have exactly the same tags, but only w1025588018 got the extra barrier=kerbs. Is this an error in my mapping that I don't understand, or a bug in SC?
I've just turned w1025587984 into an example of the "two tiny ways" (w1026853697 and w1026853698). --CjMalone (talk) 22:46, 1 February 2022 (UTC)
So it seems footway=crossing should only be over the road (kerb to kerb), the ways ("tiny ways") connecting to the sidewalk shouldn't be tagged footway=crossing. They are potentially footway=sidewalk, or maybe even no footway=* tag at all. [1] --CjMalone (talk) 12:11, 3 February 2022 (UTC)