I have had a cordial disagreeement with another mapper about the proper philosophy for tagging ways. When I encounter a fire road I tag it as a footway if there is a barrier that physically prevents vehicles from accessing it legally. The reason I do this is because I use OSM data extensively for vehicle navigation and would not want to be directed onto a way that I could not use. The disagreeing mapper stated that I should tag it as a track if it is large enough to admit a vehicle, even if such navigation is prohibited and/or requires 4 wheel drive to access. Which is the generally accepted philosophy?

asked 29 May '12, 21:23

ras_oscar's gravatar image

ras_oscar
101247
accept rate: 0%

1

Related question: How to tag a fire department-controlled gate?

You probably want to use access=no , emergency=yes .

(30 May '12, 08:45) sleske

If it is something that I would normally map as a track, then I would map it as a track, add the barriers and add access tags - maybe something like "access=no,foot=yes".

If your vehicle navigator still directs you into roads with access=no or access=private then your navigator is broken, but that should not be fixed by trying to map things as something else.

This sound like a variant of the golden rule "Don't map for the renderer".

One may also think about the case that someone could actually write a navigator for fire vehicles. If you have tagged your tracks as footways in order to fit your own needs in your broken navigator, then the navigator in the fire vehicle may get into problems navigating the fire roads.

permanent link

answered 29 May '12, 22:46

gnurk's gravatar image

gnurk
6.1k106095
accept rate: 15%

In general, we'd like OSM data to closely depict the reality on the ground, for various, even "unexpected", uses.

We know for sure that emergency services in some parts of the world are already using OSM data - perhaps not relying on OSM exclusively but at least using it as an auxiliary source of information. So even if conventional vehicles aren't allowed, it would be better to tag the way so that a potential emergency services routing system could use it (e.g. by applying one of the access tags).

permanent link

answered 29 May '12, 22:50

Frederik%20Ramm's gravatar image

Frederik Ramm ♦
74.2k866691149
accept rate: 24%

ok. I understand. However, if I tag it as track and put barriers at the ends(which most closeley represents the ground truth) how would I differentiate between barriers can open for emergency vehicles with the proper key, as opposed to an immobile barrier such as a guard rail or large rocks? I have encountered both.

(30 May '12, 00:28) ras_oscar
2

You have a lot of barriers to chose from at http://wiki.openstreetmap.org/wiki/Key:barrier and most of them implies access=no. But if you look at for example http://wiki.openstreetmap.org/wiki/Tag:barrier%3Dgate or http://wiki.openstreetmap.org/wiki/Tag:barrier%3Dlift_gate you will see that the combination with the access tag is considered useful. So you could tag your locked barrier with something like "barrier=gate,access=private,foot=yes,bicycle=no" and the blocks maybe are something like "barrier=block,foot=yes,bicycle=yes".

(30 May '12, 00:48) gnurk
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×101
×3
×1

question asked: 29 May '12, 21:23

question was seen: 2,263 times

last updated: 30 May '12, 08:47

powered by OSQA