It's not about tastes or individual habilty . It's about " the aim of *keeping it simple* both for data *contributors* (mappers) and data *users" * Semicolon works? I don't have any doubt of it but not in ALL the apps and services as subtags don't do in others...but could be implemented. Is not avoiding anything but I did not write this:"When (not) to use multiple values in https://wiki.openstreetmap.org/wiki/Multiple_values
For better or worse, a mapper's first reaction to MV tags should be to avoid them. This is largely because many data consumers do not handle MV tags well, either because they didn't expect them or because handling them is complicated. As the OSM data model <https://wiki.openstreetmap.org/wiki/Data_model> doesn't directly support multiple values, they have been tacked-on with various degrees of akwardness." -About your article: *"**So what is the conclusion of all this? For mappers I suggest avoiding semicolons where at all possible. If you can, do not use semicolons as special separator characters and do not use them as normal characters either. Often they are not necessary. The over hundred ways tagged with [name=Route Transcanadienne;Trans Canada Highway] should have used different name:fr and name:en tags.* *Mappers should be aware that values with semicolons need to be handled specially by users of the data and many users don’t do that (yet). And even if they interpret them they might understand them in a different way from what you expect. Instead of [amenity=bank;atm] you can use [amenity=bank] and [atm=yes]. Use special tags like int_ref to avoid “overloading” ref. *" -1 is 1 ,1st is 1st , it has meaning by itself (I teach it at the kindergarden school) . Semicolon has the meaning...we want to here in OSM. As a separator there are other characters (| , )so it was "random" (or other reasons I don't know why I admit it.) to choose this or that character. -About the correct suffixes? read the wiki https://wiki.openstreetmap.org/wiki/Tags#Keys_and_values "The key, therefore, is used to describe a topic, category, or type of feature (e.g., highway <https://wiki.openstreetmap.org/wiki/Highway> or name <https://wiki.openstreetmap.org/wiki/Name>). Keys can be qualified with prefixes, infixes, or suffixes (usually, separated with a colon, :), forming super- or sub-categories, or namespace <https://wiki.openstreetmap.org/wiki/Namespace>. Common namespaces are language specification and a date namespace <https://wiki.openstreetmap.org/wiki/Date_namespace>* specification for name keys." *No semicolon, no blankspace: For subtags in OSM we are using COLON. You talk about https://wiki.openstreetmap.org/wiki/Proposed_features/Remove_suffixed_name-tags_from_wiki. And I read " Tagging: alt_name_x, name_x <https://wiki.openstreetmap.org/w/index.php?title=Key:alt_name_x,_name_x&action=edit&redlink=1> =* <https://wiki.openstreetmap.org/w/index.php?title=Tag:alt_name_x,_name_x%3D*&action=edit&redlink=1> " My use is with colon, as a subcategory tag. -Finnish people also use subtags. https://wiki.openstreetmap.org/wiki/Finland:Traffic_signs http://taginfo.openstreetmap.org/search?q=traffic_sign%3A2 -The use about destination sign...is other topic to talk about.OSM was not thinking about traffic signs when established.There are so many kinds and systems in every country (here in Spain we have more than 20 different destination traffic signs, with their specificities and tags.) But ok, you may have reason. I want to learn so help me to map a roundabout sign like this: https://www.mapillary.com/map/im/6bMYhgICHVBL_H70ZnyPAg .It will be so useful because we have to map more than 7000 only in Catalonia. And it would be so interesting OSM Lane Visualizer will be able to make this :) -There are some services who splits...and trashes the information when detects a semicolon. Mapbox streets did it. "Mapbox Streets <https://wiki.openstreetmap.org/w/index.php?title=Mapbox_Streets&action=edit&redlink=1> replaces ; with a spaced em dash ( — ) in any name <https://wiki.openstreetmap.org/wiki/Key:name>=* or name:* <https://wiki.openstreetmap.org/wiki/Key:name>=* tag. For primary keys such as amenity <https://wiki.openstreetmap.org/wiki/Key:amenity>=* or shop <https://wiki.openstreetmap.org/wiki/Key:shop>=*, it considers only the portion up to the first semicolon and drops the rest." -I'm not talking about abolish semicolon uses. I say subtags are better for separate values with correspondence and follow the scheme one tag - one value. Taginfo treats it as an unique value. It's not possible to guess how many values are with semicolon. For this reasons I consider it better to use. Cheers (Salut i senyals) yopaseopor
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
