Re: [Tagging] Adding values to usage=* key for power transmission

Maybe we could use a key with a namespace: “power:usage=*” or something else. Keeping is separate from the railway usage could give us more clairity. Lukas Sommer 2014-11-24 15:24 GMT+00:00 François Lacombe : > Hi Rainer and thank you. > > I didn't spend time yet on the update done on the Pipeli

[Tagging] semantic issue with "genus" in the wiki, wetland, plant nursery, ...

I believe there are some semantic issues with how the wiki currently suggests to tag details of plants, e.g. with the tags "genus" or "species". This originates from tree tagging (AFAIK), where the suggested tagging is: natural=tree genus=... species=... taxon=... etc. NO ISSUES in this, works a

Re: [Tagging] semantic issue with "genus" in the wiki, wetland, plant nursery, ...

I'm interested in this topic in order to be able to map flowerbeds in a rose garden. Besides the problem with the genus/species/taxon tagging, I also need to be able to properly tag the flowerbeds themselves. There seems to be quite some variants for that as well. So I hope the outcome of this disc

Re: [Tagging] path vs footway

2014-11-30 2:32 GMT+01:00 Paul Johnson : > to me path implies wheelchair=no. >> > > I don't know about that, path's generally the multimodal middle between > footway (like a city sidewalk) and cycleway (which often implies foot=no; > less commonly foot=yes, rarely foot=designated; I explicitly tag

[Tagging] access -> emergency vehicle class ----- (pulling from "path vs. footway")

I copied this last paragraph from the path vs. footway discussion to get comments of more people interested in it (I guess not so many longtime contributors are interested in reading yet another time the path vs. footway discussion). According to the access page, "emergency" is not an access valu

Re: [Tagging] semantic issue with "genus" in the wiki, wetland, plant nursery, ...

> > I think this is an inconsistency in tagging and would be interested to >> hear if you believe the recommendation should be changed. E.g. we could >> have a "plant:genus" to explicitly state that the genus refers to the >> plants rather than the nursery. >> >> I agree about the inconsistency. In

Re: [Tagging] semantic issue with "genus" in the wiki, wetland, plant nursery, ...

Martin Koppenhoefer wrote on 01.12.2014 11:22: > I believe there are some semantic issues with how the wiki currently > suggests to tag details of plants, e.g. with the tags "genus" or "species". > > Now to plant nurseries, according to the wiki the suggested tagging is > (they do not have their o

Re: [Tagging] semantic issue with "genus" in the wiki, wetland, plant nursery, ...

2014-12-01 14:25 GMT+01:00 Holger Jeromin : > > plant=* The generic type of plant that is grown, e.g. tree, herb, bush, > ... > > I think this is an inconsistency in tagging and would be interested to > > hear if you believe the recommendation should be changed. E.g. we could > > have a "plant:gen

Re: [Tagging] How one should tag different sections of library?

I like (3) the best (only 1 amenity, the biggest one) and I think the new tag could be similar to building:part > A way with the tag > building:part =yes or > building:part =*:part > descr

Re: [Tagging] semantic issue with "genus" in the wiki, wetland, plant nursery, ...

> 2014-12-01 14:25 GMT+01:00 Holger Jeromin : >> genus and species is defined as a name for an organism, not only plants. >> >> I added the species to animals in a zoo: >> http://www.openstreetmap.org/way/286321033 >> >> So for producing landuse like plant_nursery a prefix named "product:" >> seems

Re: [Tagging] How one should tag different sections of library?

2014-11-29 15:15 GMT+01:00 Mateusz Konieczny : > There is a large library with multiple sections (for children, for adults, > foreign language > books, reading room, movie/music borrowing, newspaper section etc etc). > > There are separate accounts for separate sections, different opening > hours.

Re: [Tagging] semantic issue with "genus" in the wiki, wetland, plant nursery, ...

2014-12-01 16:59 GMT+01:00 althio forum : > If produce:genus can replace and unite produce/crop/trees for producing > landuse like plant_nursery/farmland/orchard without any loss in meaning I > think it is a worthwhile proposal. no, it can't, because "genus" is expected to be in Latin, and we

Re: [Tagging] How one should tag different sections of library?

> "is there one name or different names?" Each part has its name, but it is name for this part of the library - for example "Main lending library" (Wypożyczalnia Główna), "Children's Section" (Wypożyczalnia dla dzieci). > "I believe multiple libraries aren't any problem" For example - it will b

Re: [Tagging] How one should tag different sections of library?

I would ask if any section of that library is usable as a library on it's own. Let's take the local city library here, which has several sections at different locations. There is the main location, a children- and computer library as a thematic "branch" and several localized branches in some subur

Re: [Tagging] Adding values to usage=* key for power transmission

Hi Lukas, I don't like this : railway guys introduced usage without any namespace. Why should power introduce one ? usage=* is a common tag. The proposal isn't introducing power:location instead of location=* even if there is some specific values. Do you agree ? *François Lacombe* fl dot infos

Re: [Tagging] How one should tag different sections of library?

"I would ask if any section of that library is usable as a library on it's own." Without registration it is impossible to use any, there is a single place for registration. Books/media must be returned to the same section where it was borrowed. In this case everything is in a single building (buil

Re: [Tagging] Adding values to usage=* key for power transmission

Hm. I think the railway guys have a clearly defined list of possible values (there are 6 possible values in the wiki). This way software can process the data, because it is known which values are valid and which not. Checking this would be much more difficult (for data comsumers, but also for edito