Re: [Tagging] What separator do you use for multiple value
Hi, > I've always hesitated between the period and the comma. A **period**? That sounds like a very bad idea. It is the decimal separator, so using it for anything else obviously must lead to major issues. I use semi-colon as proposed in [1], it plays nicely with opening_hours and such keys, and I cannot remember having seen anything else in the wild. -nik [1] https://wiki.openstreetmap.org/wiki/Multiple_values___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Namensanzeige bei der Sucheingabe / Names presented in the search function
Hallo Ulrich, On Mon, Jan 30, 2023 at 10:22:26PM +0100, Ulrich Lamm wrote: > Es ist eine Unverschämtheit, bei Sucheingaben die Namen nur noch in der > Landessprache des Suchenden anzuzeigen und dem/der Suchenden damit die heute > gültigen Namen vorzuenthalten. Es ist eine Unverschämtheit, nicht mal die Augen aufzumachen und dann auf die Mailingliste zu kotzen, ohne jegelichen Versuch von Anstand. > Diese Art der Anzeige ist der Versuch, die OSM-Nutzer einzusperren und ihnen > die Vorteile des internationalen Projektes vorzuenthalten. Diese Feststellung ist schlichtweg gelogen. OpenStreetMap.org zeigt alle in der Datenbank bekannten Namen in allen Sprachen an. > It is impertinent to present OSM-users searching for some place abroad only > the names in the language of the country, they ask from, and not to show the > searcher the valid/official names of the country on which he/she wants to get > informations. It is impertinent to not even take a proper look, but then shout on a mailing list without the slightest respect. > This manipulation is the attempt to retain people mentally in the country > where they live, > instead of allowing them to enjoy the advantages of the international project. This statement is a plain lie. OpenStreetMap.org shows all names known in the database in all languages. Please refrain from using this mailing list, or any other OSM communication channel, or even any other communication channel at all, before adjusting your behaviour. -nik signature.asc Description: PGP signature ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] access=student and entrance=inter-building: comments?
Hi, I guess I need a solution for the path access too - because access=private also seems an incorrect label - or would both be covered by access=inder-building ? just out of curiosity, what would happen if you *did* use it as an entrance *before* using the main entrance? -nik signature.asc Description: OpenPGP digital signature ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] access=student and entrance=inter-building: comments?
Hi, 1) Access=student - access designated for students of a school/facility, similar to customers of a shop or visitors of a facility. Does not imply age or gender, though it is used at mostly at K-12 facilities. For use with entrance=* or possibly with certain school amenities (Locker rooms, bathrooms, bicycle parking). Sounds useful, but somehow I see a way that people might forget about the „designated“ part, using the tag for for entrances that may be used by students *and* other personnel, which would make the entrance essentially access=private isntead. 2) entrance=inter-building - an entrance that is designated for only moving between buildings in a facility, even if physically accessible from outside. Usually on the ends of an outdoor walkway considered “indoors because of cultural custom rather than physical access restriction (IE: indoor shoes required). Not to be used on normal outdoor pathway entrances. Is this about entrance usage or about shoes? If it is about shoes, then this seems to matter more for the inter-building *path* than for the entrance itself. -nik signature.asc Description: OpenPGP digital signature ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Node objects in tunnels or on bridges?
quite often there are node-type objects on bridges or in tunnels. What to do with them? Tunnel or bridge tags are dfined only for ways. please be a bit more specific on what you mean. Do you mean… a) … a node on a way that is tagged as tunnel or bridge, or b) … a node that is itself tagged tunnel or bridge? Maybe link to an example on the map ☺. I believe b) would be the correct alternative. E.g., amenity=waste_basket, man_made?surveillance, highway=street_lamp or some such object that is on the bridge/tunnel rather than below it/on ground. Ah. You think the OP is talking about *real-world* objects and how to tag them. I was thinking they are talking about bugs in the map ;). (I don't tend to classify real-world objects as node-type when talking about them ;).) In that case, I believe the layer=* tag should be used instead, giving the object the same layer as the tunnel or bridge. -nik signature.asc Description: OpenPGP digital signature ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Node objects in tunnels or on bridges?
Hi, quite often there are node-type objects on bridges or in tunnels. What to do with them? Tunnel or bridge tags are dfined only for ways. please be a bit more specific on what you mean. Do you mean… a) … a node on a way that is tagged as tunnel or bridge, or b) … a node that is itself tagged tunnel or bridge? Maybe link to an example on the map ☺. Cheers, Nik signature.asc Description: OpenPGP digital signature ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] access=student and entrance=inter-building: comments?
Hi, I hope that helps a bit. yeah, thanks for the detailed explanation. I learnt a lot about an exciting foreign culture today! As for the tagging, there definitely should be something, and on first glance, I do not see an issue with the access=inter_building idea. -nik signature.asc Description: OpenPGP digital signature ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] bridge=movable?
If there is a genuine reason, then surely there should be the equivalent: bridge=static bridge:static=* And yes, this is inconsistent and wrong. The polution of the bridge=* namespace for static bridges most likely is there for historic reasons. -nik signature.asc Description: OpenPGP digital signature ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] bridge=movable?
Hi, What's the purpose of bridge=movable? bridge=movable bridge:movable=swing gives bridge=swing One reason is mentioned in the introduction of the Wiki page: Note that this key may be used without tagging bridge=movable, to indicate a formerly movable bridge that has been fixed shut. In addition, the type of the movable bridge is a detail which maybe is not necessary for most renderers or for navigation, so having a general flag that a bridge is movable (thus delaying a route, for example) is a good thing because renderers do not have to check each and every type of movable bridge in the bridge key. Be aware that the values mentioned in the wiki are not the only allowed values for the bridge:movable=* tag. Someone might encounter a movable bridge that does not fit one of the described tags. They'd invent a new tag, discuss it, and draft it as an addition to the standard, but nonetheless, the bridge can be marked as movable in general and renderes will still do the right thing even though they do not know about the new tag. -nik signature.asc Description: OpenPGP digital signature ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] bridge=movable?
If there is a genuine reason, then surely there should be the equivalent: bridge=static bridge:static=* As a matter of fact, tehre is. I checked Tower bridge in London because the structure is well-known and combines several types of bridges. Checking it, I found out what was changed for bridge tagging and converted it to the new tag style. You can see the differences at http://www.openstreetmap.org/changeset/29134654 Essentially, what you are looking for is bridge:structure=* -nik signature.asc Description: OpenPGP digital signature ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] natural=????
Why? If there is a difference, then there is a difference. BTW, mind fix your From name, Mrs. or Mr. Gmail? -nik Gmail yve...@gmail.com schrieb: In a geo database, tundra alone must be sufficient, don't you think ? Tod Fitch t...@fitchdesign.com a écrit : I'd like to start adding some vegetation information to an area in the mountains of Southern California. There are a couple of situations that I am uncertain of the correct tagging of treeless areas. For this query though I'll restrict it to areas at or above timberline. I believe the wide spread term to describe the ecosystem is alpine tundra. Certainly the Wikipedia article on southern California mountains refers to it that way: http://en.wikipedia.org/wiki/California_montane_chaparral And the Wikipedia page regarding alpine tundra affirms it: http://en.wikipedia.org/wiki/Alpine_tundra But the closest looking tag I see at http://wiki.openstreetmap.org/wiki/Key:natural seems to be natural=fell Fell appears to be a UK centric description for a subset of alpine tundra: http://en.wikipedia.org/wiki/Fell There are currently no natural=*alpine* tags and only a handful natural=tundra, the use of which seems to cover both alpine tundra (mountains in Colorado) and arctic tundra (northern Canada, etc.) without a way to distinguish which of the two are meant. What are the thoughts of extending the natural tag to include: natural=arctic_tundra, natural=alpine_tundra and, possibly, natural=antarctic_tundra With descriptions per Wikipedia: http://en.wikipedia.org/wiki/Tundra http://en.wikipedia.org/wiki/Alpine_tundra Regards, Tod ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging -- Envoyé de mon téléphone Android avec K-9 Mail. Excusez la brièveté. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] Linking to Wikipedia subheaders
Hi, for some attributes in the map around here, there is a subsection in the village's Wikipedia article. For example, for the church, there is a subsection labelled Church, which is accessible using the #Church URL anchor. The OSM wiki details that the syntax for linking to Wikipedia is de:Foo for Foo in de.wikipedia.org. How can I link to a subsection? Would de:Foo#Bar be recognized? -nik -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Linking to Wikipedia subheaders
Wikipedia replaces spaces with underscores when forming URLs for article names. This has nothing to do with URL encoding. -nik John F. Eldredge j...@jfeldredge.com schrieb: Space characters in URLs are normally encoded as %20. An underscore is a valid character in an URL. Martin Koppenhoefer dieterdre...@gmail.com wrote: 2013/8/15 Dominik George n...@naturalnet.de Would de:Foo#Bar be recognized? I'd do it like this, no idea if current services recognize this or not, alternatively as URL with http:// and underscores instead of spaces. cheers, Martin ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging -- John F. Eldredge -- j...@jfeldredge.com Darkness cannot drive out darkness: only light can do that. Hate cannot drive out hate: only love can do that. -- Dr. Martin Luther King, Jr. ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] amenity=police
Hi, the question is: Is there duty one oft law enforcement? If so, the tag is correct IMHO. -nik Bryce Nesbitt bry...@obviously.com schrieb: At: http://wiki.openstreetmap.org/wiki/US_National_Park_Service_Tagging We have ranger stations listed under amenity=police. Rangers are indeed a type of police, but one that often also counts squirrels or displays rocks. Should ranger stations get their own tag? ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] access at own risk
Hi, I assume there might be a difference between access=yes and access=permissive in this regard because it defines who might be liable if not you. I do not think this information should be tagged for reasons mentioned before, but on a side note, for roads with access=permissive and access=private, the operator tag should be used to indicate who is responsible for granting the right of way. -nik Jaakko Helleranta.com jaa...@helleranta.com schrieb: 2013/7/31 Volker Schmidt vosc...@gmail.com I am sure this has been asked many times before: How do I tag correctly a path/track/road that bears the label access at your own risk ? Is there any text before that, like guard dogs roaming free (-- access at your own risk) ? Seriously though, I wonder if such liability notice actually adds any relevant information? .. Where is accessing a property be on someone else's risk (=liability)? Not so often, eih? - access=yes ? (.. i.e. no access tag as this is the default..). -Jaakko ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] access at own risk
Hi,
fly is right here.
When it comes to snow cleaning, owners of the houses along a road are liable in
case of an accident if they didn't fulfill their duties. (At least in Germany -
some British court of law ruled this to be God's will if I am not mistaken).
However, I am not sure whether a sign is relevant here.
So, I propose:
- If in your country, a sign cannot change liabilities, do not tag it. The
access=* tag says it all.
- If the sign is legally relevant, use liability=no *and* the operator=* tag.
I could also imagine to use liability={user,operator} with a regional default.
-nik
fly lowfligh...@googlemail.com schrieb:
Am 31.07.2013 15:46, schrieb Volker Schmidt:
I am sure this has been asked many times before:
How do I tag correctly a path/track/road that bears the label access
at
your own risk
This is no access sign !
It is posted for insurance reason because this way does not cleaned
(snow plowed eg.) and if you happen to have an accident cause of bad
conditions it is your own fault/problem.
We need some other tag to express this.
cu
fly
___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] access at own risk
Hi,
in that case, I am certain that noone will take liability for your actions
anyway, be there a sign or not. The sign is only there to ease the load on the
people who have to deny liability ;).
If the site has a private operator, though, ask them.
-nik
-nik
Volker Schmidt vosc...@gmail.com schrieb:
The signs I am referring to, are in Italy (South Tyrol) on narrow paths
that allow you to walk around the ruins of two medieval castles. The
paths
are unprotected, like alpine paths (where I have never seen any sign of
that kind).
Volker
On 31 July 2013 18:29, Dominik George n...@naturalnet.de wrote:
Hi,
fly is right here.
When it comes to snow cleaning, owners of the houses along a road are
liable in case of an accident if they didn't fulfill their duties.
(At
least in Germany - some British court of law ruled this to be God's
will if
I am not mistaken).
However, I am not sure whether a sign is relevant here.
So, I propose:
- If in your country, a sign cannot change liabilities, do not tag
it. The
access=* tag says it all.
- If the sign is legally relevant, use liability=no *and* the
operator=*
tag.
I could also imagine to use liability={user,operator} with a regional
default.
-nik
fly lowfligh...@googlemail.com schrieb:
Am 31.07.2013 15:46, schrieb Volker Schmidt:
I am sure this has been asked many times before:
How do I tag correctly a path/track/road that bears the label
access at
your own risk
This is no access sign !
It is posted for insurance reason because this way does not cleaned
(snow plowed eg.) and if you happen to have an accident cause of bad
conditions it is your own fault/problem.
We need some other tag to express this.
cu
fly
--
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail
gesendet.
___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
--
Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.___
Tagging mailing list
Tagging@openstreetmap.org
http://lists.openstreetmap.org/listinfo/tagging
[Tagging] Time limits for road access
Hi, I have a question concerning time limits for road access. When tagging a highway or a barrier with access=no, how can I mark that this limitation only exists in a certain time frame? This is the case, for example, on a road nearby that is directly in front of a school and this road must not be uses from 7 to 17 o'clock. Thanks, Nik -- burny Ein Jabber-Account, sie alle zu finden; ins Dunkel zu treiben und ewig zu binden; im NaturalNet, wo die Schatten droh'n ;)! PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 signature.asc Description: Digital signature ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Time limits for road access
Hi, You can express this with conditional tagging like great, thenks! -nik -- # apt-assassinate --help Usage: apt-assassinate [upstream|maintainer] package PGP-Fingerprint: 3C9D 54A4 7575 C026 FB17 FD26 B79A 3C16 A0C4 F296 signature.asc Description: Digital signature ___ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
