Changeset: 50947147
went on run through Quarry Lake area, mapping what I saw, like fences, trees, buildings, walls, and paths
Closed by ElliottPlack
Tags
created_by | JOSM/1.5 (12450 en) |
---|---|
source | Bing; MD Latest 6 Inch Aerial Imagery; survey |
Discussion
-
Comment from mueschel
Hi,
could you explain the meaning of 'eruv' on this way?
http://www.openstreetmap.org/way/513968801Cheers, Jan
-
Comment from ElliottPlack
Jan,
Sure, an eruv is a physical object that serves as a symbolic boundary in the Jewish Orthodox faith. Read more:https://en.wikipedia.org/wiki/Eruv
There isn't a great tag for this yet on OSM, so I added this under the premise of the "Any tags you like" principle (http://wiki.openstreetmap.org/wiki/Any_tags_you_like) until I come up with a formal proposal. Do you have any ideas?
It is a physical thing, a rope or wire but it doesn't serve as a mobility barrier, it doesn't carry power or communication. This sets it apart from other OSM tags. Fellow OSM'er MDRoads and I have been discussing how best to map these. There are a few others on the map but people are taking the approach of using a boundary relation, which I think is OK but I'm more interested in mapping the physical thing that can be observed out in the world. Here are some photos of the Eruv in Baltimore. It is something you can see and touch, unlike most boundaries.
https://goo.gl/photos/9TgKDkDyjWvmTQGG7
Best,
Elliott -
Comment from mueschel
Alright, I haven't seen this before.
I see one potential problem with the tagging: A barrier=* implies an access restriction, by default access=no. So, if anybody by mistake adds a common node with any highway, routing engines might think traffic is blocked.
I don't think we have a proper tagging for such a symbolic barrier yet - what about using a fully new tag like eruv=*, and subkeys like eruv:type for details? I don't know if similar concepts exist in other religions, maybe one wants to add a religion or denomination tag to make things clear. -
Comment from ElliottPlack
Jan: I'm glad that you found this and commented. I think your idea is superb. I was trying to decide if I should use an existing key like barrier but you make a good point that it could be interpreted by a routing engine as a generic barrier. Better to start something totally fresh.
What do you think about using a colon vs an underscore to separate subtypes? I like the way the colon looks. Is there any functional difference?
I cannot think of any other physical objects that manifest a symbolic border in a religious context. However, I think that a border fence has the same connotation for political divisions. The fence is observable so it gets the fence tag, whereas the boundary is typically set by relation. Once I find the entire length of this eruv (it has to be continuous so that should make it easier to follow), I'd add all the parts as eruv=* and then add some kind of relation. I've seen a few (1-4 on the planet) where people are using a boundary=religious for these. I think that such a boundary might be appropriate, though are usually used for papal states and such with a government. The eruv is somewhat less formal, though I suppose it does have a maintainer and legal backing, so religious boundary might be good for relation.
-
Comment from mueschel
':' versus '_' - there is no functional difference between the two. Usually, ':' is used for subkeys, e.g. a key that further describes the main key, e.g. 'capacity' and the more specific 'capacity:disabled'. The underscore is more used like a replacement for a space as in "internet_access". In your case I would use a colon.
-
Comment from ElliottPlack
Thinking back on this, what do you think about having eruv=rope, eruv=wire, versus eruv=yes paired with eruv:type=rope or wire. Tags like barrier and highway have their 'type' as the tag name.
-
Comment from mueschel
Hi Elliott, this should be fine too. You can still add tags like "eruv:something = this" later on if you feel a need to add more details.
- 513968799, v1
- 513968800, v1
- 513968801, v1
- 513968802, v1
- 513968803, v1
- 513968804, v1
- 513968805, v1
- Travertine Drive (513968806), v1
- Travertine Drive (513968807), v1
- 513968808, v1
- Moores Branch (513968809), v1
- 513968810, v1
- 513968814, v1
- 513968816, v1
- 513968819, v1
- 513968824, v1
- 513968825, v1
- 513968826, v1
- 513968827, v1
- 513968828, v1
Welcome to OpenStreetMap!
OpenStreetMap is a map of the world, created by people like you and free to use under an open license.
Hosting is supported by Fastly, OSMF corporate members, and other partners.
https://openstreetmap.org/copyright | https://openstreetmap.org |
Copyright OpenStreetMap and contributors, under an open license |