From OpenStreetMap Wiki
Jump to: navigation, search

Delete this page.

I suggest to delete this page. All information is included in sidewalk=*. There is no need for double pages. --Rudolf 13:06, 20 July 2012 (BST)

suggest to merge these pages on sidewalk=* ==dr&mx 20:51, 25 July 2012 (BST)
Already done. --Rudolf 11:16, 26 July 2012 (BST)
I'll cleanup RU:* pages --dr&mx 19:11, 26 July 2012 (BST)
Thanks. --Rudolf 21:50, 26 July 2012 (BST)

Undo deletion

I've undone your deletion of the Sidewalk page. Some other contributors tried in the past to separate the concept description (e.g. "how to map" and the key pages. See e.g. Highways which is different from Key:highway or Barriers and Key:barrier. So please do not delete that job done on several places or merge the concept and tag pages everywhere. --Pieren 11:40, 6 August 2012 (BST)

I found your concept at several main keys, especially for the keys in Map features, but I didn't find this concept for subkeys such as track_type=, shelter_type=, shower=, mattress=, reservation= and many others. sidewalk=* is a subkey for highway=*. I don't see any sense to use two different pages for subkeys, while one page includes all the information.
BTW, why don't you declare your doing in the history? Why don't you contribute on the talk-page? I will move this discussion to Talk:Sidewalk.
I still recommend to delete this page. --Rudolf 13:21, 6 August 2012 (BST)
It's not 'my concept' or something I did myself. It has been done by others. I don't know if the idea is good or not, I'm just saying this split into 2 pages, one for concept/one for tag, exists in other places in the wiki )(I pointed some examples above). But as you said, it is not done everywhere. What I don't like is that the work is not completed - at least - for the main keys. But it started. And now, you come and propose to delete one of them. Either you merge/delete all of them or we continue with this concept. I don't care myself but it shall be consistent. --Pieren 15:27, 6 August 2012 (BST)
The concept is okay for main keys, as said above. IMHO sidewalk=* is no main key, but a subkey to highway. You haven't pointed examples for subkeys. I also don't find any examples for subkeys. So, what is the problem to delete a unnecessary page of a subkey, when there is no common concept for subkeys? --Rudolf 16:19, 6 August 2012 (BST)
I have just added a features infobox to the page. Features pages are generally used to describe features that are complex enough to require an overview, and it is my view that sidewalks are indeed complex enough to benefit from a features page and it was a oversight on my part not to have added an infobox already. Personally I would recommend trimming the sidewalk key page back a bit and then ensuring that this page covers the whole subject well. As people get into more and more detailed mapping I suspect that this subject will become more used. To be clear, features pages are not matched one-to-one with keys, they are often used to cover cross-cutting themes that go across multiple keys. Junctions, Health and Historic are all good examples. I would however suggest that we move this page to 'Sidewalks' for consistency with most otehr feature pages which use the plural. PeterIto 16:30, 6 August 2012 (BST)

I have now done a bunch of work on this article and on sidewalk=*. I hope that it now makes more sense to keep the two articles. Personally I think this article would now benefit from some more details on how to tag the more detailed approach. For example, how is one meant to use the kerb tag? There is precious little detail about it on this article or on its own page. PeterIto 22:29, 6 August 2012 (BST)

Good work. What do you think about the double chapters How to map and Presentation? I recommend to avoid duplications. --Rudolf 07:35, 7 August 2012 (BST)
Thanks. Personally I think it makes sense to keep the discussion about tagging separate from a discussion of the services available to view the date when there are many such services, however I agree that they could be merged in this case where there are less. If however four separate services to show the data emerge then a separate section probably makes sense. I am going to be away from the internet for a while now, so feel free to make changes as you see fit. PeterIto

Separated from the road by some form of barrier?

I suggest to use sidewalk=* only for sidewalks seperated from the carriageway by a curb or gutter. If there is a wider barrier in form of a road verge (lawn, bushes ...) I suggest to tag the sidewalk seperatly as highway=footway with footway=sidewalk. --Rudolf 06:15, 9 August 2012 (BST)

If the barrier is not easily passable or if the gap is irregularly shaped or unusually wide, then there are good arguments for mapping the sidewalk as separate way (even though the problem of connecting it with the road is still not reliably solved). But a bit of grass hardly makes any difference for a pedestrian's ability to cross the highway, or any other aspect of using the sidewalk, so I would not necessarily consider this a reason to change to a different mapping style. --Tordanik 09:04, 9 August 2012 (BST)
My suggestion has the intention to find a proper rule for the mapping of sidewalks. What is your suggestion for a explicit mapping howto? --Rudolf 08:42, 17 August 2012 (BST)
My personal opinion at the moment is that any sidewalk which runs mostly parallel to the highway itself and is considered a part of it (e.g. for naming) is probably best mapped as a tag on the way - using either Key:sidewalk or maybe something more advanced along the line of Lanes in the future.
However, it may be best to wait until renderers and routers actually support sidewalks intelligently (at least on an experimental level), then look at what works for them and what doesn't, and use that knowledge to define mapping rules. The main objection to sidewalks-as-a-way is that it may just not be realistically possible for applications to establish the semantic connection with the main highway. If that assumption is accurate, it would not be a good idea to standardize on your suggested rule. After all, data that is not usable by applications is just not useful, even if it conforms to a rule in the wiki. --Tordanik 19:47, 17 August 2012 (BST)

Suggestion:Change orientation from left/right to North/South/East/West. Suggestion negated.

I don't like the left/right/both/none concept.

Reasoning: While editing it is sometimes necessary to

- reverse direction (e.g. to combine roads with the same attributes)

- change or create oneway streets


With North/South/East/West/both/none I think we would be better off as it is always right. Does anyone agree/disagree? Please state your case!

Editors such as JOSM already handle direction-dependent tags quite well when reversing or combining ways, so I don't really see the problem. With North/South/East/West, even something as simple as moving a node could flip the sidewalks, a source of errors which no editor is currently aware of. The N/S/E/W solution also has the disadvantage of being potentially ambiguous, especially after combining roads, and would force additional splits for winding roads. --Tordanik 18:57, 27 June 2013 (UTC)
Thank you for your knowledge. I'll drop the suggestion. Can it be deleted?
No need. On talk pages that get too long, we sometimes introduce "archives" and move old questions there. But this page's length is still quite acceptable I think. --Tordanik 20:00, 28 June 2013 (UTC)

Sidewalks in roads with cycleways

In roads without cycleways, it is well established to mention sidewalk=both or sidewalk=left or sidewalk=right with the description of the carriageway.

If there are one or two cycleways in the street, recorded as separate lines, up to now everybody has mentioned the sidewalks as integral parts of these cycleways by the tags highway=cycleway + segregation=yes. Some people even tag highway=path + bicycle=designated, till lately hiding the cycleways from some renderers this way.

I consider it much more logical, and also have started to tag this way, to call sidewalks also sidewalks, if they are situated beside cycletracks.

For the classical street design "sidewalk – cycletrack – parking – carriageway – parking – cycletrack – sidewalk", this can be:

(for cycleways, the renderers detect oneway=yes better than oneway:bicycle=yes)

If there is a unilateral bidirectional cyleway, the nominal direction of both, carriageway and cycleway, should be that they have the other part of the road on their left side. If the division of space is "sidewalk – carriageway – cycletrack – sidewalk", the tagging would be:

(If both lines have the same formal direction instead, one of both lines has sidewalk=left.)

This way of tagging is almost necessary, if the widths are recorded:

For offroad ways that clearly consist of a cycleway and a footway, highway=path for a long time was almostwrong and still makes it more complicated than necessary. And "sidewalk" is not a good style, especially if the footway is wider than the cycleway. Then I'd prefer highway=cycleway + footway=left OR right. As most offroad cycleways are allowed for pedestrians, too, but many paths forbidden or technically inappropriate for cycling, well cyclable ways should be presented as cycleways by the renderers.--Ulamm (talk) 14:35, 30 July 2014 (UTC)

Recently, MAPNIK renderers have begun to understand highway=path + access-tags, but that tagging is more complicated and doesn't show the relative positions of foot- and cycleways drawn as one common line.--Ulamm (talk) 22:14, 30 September 2014 (UTC)

Usage of sidewalk on highway=footway/cycleway/path

I removed the following sentence from Tag:highway=cycleway which may need some more discussion.

"It is also possible to use sidewalk=right/*=left to indicate which side of the segregated path pedestrians should walk on (where right/left is relative to the way's direction). "

The reason for the removal is: It conflicts with the description on this page of where to use sidewalk=*. It says that sidewalk=* is not needed on highway=footway/cycleway/path/....

The (most) common usage of sidewalk=* is, so far as I know, the usage on highways different from cycleways. At the moment according to taginfo sidewalk=* is used around 500,000 times, while it is used 3,966 times on highway=cycleway (which includes 2,090 times sidewalk=none). There is already a proposed tag footway=sidewalk to map such infrastructure in that context.--U715371 (talk) 01:07, 5 January 2015 (UTC)

"It is possible …" is an information. The sentence deleted by User:U715371 is a true information. Deletion of true informations that are not far from the subject is vandalism.
About the subject itself see Talk:Tag:highway=cycleway!--Ulamm (talk) 18:03, 5 January 2015 (UTC)

Sidewalk= no / =none

Anyone know the difference between sidewalk=no and sidewalk=none ?-- pmailkeey 2016:4:5

They mean the same thing. Which one is better depends on whom you ask. Personally, I prefer "no", because of the symmetry with "yes" and because almost all other keys use "no" rather than "none". --Tordanik 09:48, 6 April 2016 (UTC)

Sidelwalk or not - width limits

I was just wondering when to consider a sidewal being a sidewalk and not just a wider kerb that would be dangerous to walk along. As an example consider this Mapillary image. The width is 4 paving stones plus the kerb stone. Is this wide enough to qualify? In my view not as sidewalks should be safe to walk on. Also you would not be able to use a pram/stoller on this one.

What are your thoughts? --ConsEbt (talk) 09:32, 15 September 2016 (UTC)