Re: [Tagging] Fire hydrants vs suction_point
Hi, 2017-08-21 1:40 GMT+02:00 Warin <61sundow...@gmail.com>: > On 21-Aug-17 09:18 AM, marc marc wrote: > > The simplest (and in many case the only) way to tranfser hydrants >>> attributes to GPS is to put them in waypoints names. >>> >> you can also just use the same as you did in the past, as you do not use >> the name of the osm tag anyway >> > > Do not use the name tag. If you must, possibly use the tag "description=*"? > Te problem is on GPS side. Viking explained the GPS he use only take POI with a name field without additional attributes. Then it's harder to distinguish presurized hydrants vs suction points but not impossible : concatenate water_source with ref or arbitrary label (hydrants don't usually have names) and you're done. > > Pipe lines would also have a flow_capacity, as would canals, drains. > Humm pipeline uses the tag capacity ... I don't think that is a good fit > with present OSM use of that tag. > > In the interests of having a more universally applied tag I'd rather have > a tag "flow_capacity=*" as a property tag much like length, height etc. +1 on idea Capacity is used several hunder thousand times but flow_capacity never (fire_hydrant:flow_capacity about 7k). Since capacity definition is "The tag describes the capacity a facility is suitable for", it can fit for pipelines, hydrant, canals, drains... in m3/s or m3/h, can't you ? François ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Pepper: Chili, piper, bell pepper
Le 21. 08. 17 à 00:07, Tod Fitch a écrit : > e.g. black pepper corns could be “produce=pepper”, “variety=black_corn”. +1 ! please avoid adding too many value to "top level" tag, If not, this 'll be like landuse : it is impossible to select "all agricultural landuses" of an area without first making a manual classification of all the value found in taginfo to find their "main" landuse. subtab is very useful to have usable datas with a level of detail that depends on the need. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Fire hydrants vs suction_point
On 21-Aug-17 09:18 AM, marc marc wrote: The simplest (and in many case the only) way to tranfser hydrants attributes to GPS is to put them in waypoints names. you can also just use the same as you did in the past, as you do not use the name of the osm tag anyway Do not use the name tag. If you must, possibly use the tag "description=*"? For sake of simplicity, fire_hydrant: and suction_point namespaces should be avoided as done for fire_hydrant:position fire_hydrant:flow_capacity could also just be the already existing key flow_capacity Pipe lines would also have a flow_capacity, as would canals, drains. Humm pipeline uses the tag capacity ... I don't think that is a good fit with present OSM use of that tag. In the interests of having a more universally applied tag I'd rather have a tag "flow_capacity=*" as a property tag much like length, height etc. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Pepper: Chili, piper, bell pepper
On 21-Aug-17 08:07 AM, Tod Fitch wrote: I am bemused by this thread. I know that when I am sent to the grocers to get peppers I’ve never been asked to get a “chili pepper”. Depending on the desired dish it might be a “Anaheim”, “Chipotle”, “Jalapeño”, “Serrano”, “Habaneros” or other type of the spicy peppers. Those are just a few of the types of peppers we might use in the Southwest United States for a Mexican inspired dish. For Asian inspired dishes there are another whole host of spicy peppers available in the local stores. If a “Bell pepper”, I will usually be requested to get a “yellow Bell pepper” or “red Bell pepper” rather than just a “Bell pepper”. So it seems altering a top level “produce=pepper” into “produce=chili_pepper” and “produce=bell_pepper” would not be a good fit for my part of the world. Looking at Wikipedia, there are something like 50,000 varieties of peppers but they can be be broken into two general classes “sweet” and “chili”. So if it is desired to be more specific than just “pepper” it would seem that “chili_pepper” and “sweet_pepper” would be better. But better yet in my mind would be leaving the top level as “pepper” and adding a “variety=*” tag detailing the more specific vulgar (non-latin) name. The world is awash in varieties of common items. I don’t think we want to put all the variations into a top level tag. The term 'vulgar' can be insulting and is rather technical .. 'common' would be more understood. The concept would be to use variety to distinguish produce or products based on the commonly used local names. From taginfo it seems that a “variety” tag is already in undocumented use for wine. Why not embrace and extend that to cover other food stuffs, e.g. “produce=apples”, “variety=jonathan”. I suppose that the British word for corn is maize, so you might have “produce=maize”, “variety=sweet|field|whatever”. Driving by a field I’m pretty sure I can decide if it has corn (maize) in it. But I won’t be able to tell if it is field or sweet corn. Let me tag the top level as “produce=maize” and be done with it. Likewise, I can recognize a few varieties of peppers when they are being grown but far from all. Let me tag the field as “produce=pepper” and if I am confident of the variety I can also add that tag. I'd not use "variety=" but simply use "apple=jonathan". The scheme of using an additional variety tag could even be used to cover the other items called peppers in English, e.g. black pepper corns could be “produce=pepper”, “variety=black_corn”. On Aug 20, 2017, at 2:16 PM, Tom Pfeifer wrote: On 20.08.2017 22:48, Kevin Kenny wrote: The English word 'pepper' also applies to several plants in the genera Aframomum, Capsicum, Pimenta, Schinus, and Zanthophylum (plus others that are used in traditional herbal medicine but not for the kitchen). > I think that the original poster wanted to disambiguate among these, Yes of course, that's why he proposed produce=bell_pepper;chili_pepper. which would make the Linnæan names the best option - there isn't any easy way to clarify it using only vulgar names. Well there is an easy way: Clearly describing in the wiki that produce=pepper means the fruits of 'piper nigrum'. Introducing an inconsistent language scheme will confuse all occasional mappers. Latin names should remain reserved for genus=* and species=*, and you can add species:en=* for all languages as well. Using that approach there then need to be a 'clear description that apples means jonathans", and all the others will have to have another tag! I don't think so, it would be more complex that using a sub tag to describe the specific variety. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Fire hydrants vs suction_point
> The simplest (and in many case the only) way to tranfser hydrants > attributes to GPS is to put them in waypoints names. you can also just use the same as you did in the past, as you do not use the name of the osm tag anyway > For sake of simplicity, fire_hydrant: and suction_point namespaces > should be avoided as done for fire_hydrant:position fire_hydrant:flow_capacity could also just be the already existing key flow_capacity ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Fire hydrants vs suction_point
Hi Viking, Thank you for synthesis and proposal update. 2017-08-20 2:02 GMT+02:00 Viking : > > Francois, as a firefighters, I can say that it's very very important to > distinguish a pressurized hydrant from a dry hydrant (or suction point). > And we all agree. > And now I explain the reason why I prefer this distinction in the primary > key. > First of all in many cases you don't know the pressure, but you know only > that it's a pressurized hydrant. You should use something like > fire_hydrant:pressure=positive that adds complexity and it's error prone > for an inexperienced mapper. > I agree with you for fire_hydrant:pressure=positive complexity. water_source=mains or water_source=network may be enough The point isn't to know exact pressure, only source is a concern for us. > Then, for my fire departement, I've extracted hydrants data from OSM, I've > uploaded it on some old and new GPS and I've sent it on my colleagues > smartphones. > The simplest (and in many case the only) way to tranfser hydrants > attributes to GPS is to put them in waypoints names. But waypoints names > lenght is limited in GPS, so it's likely that someone transferring data > will loose the fire_hydrant:pressure information. > Then it's simpler to look for emergency=fire_hydrant or > emergency=suction_point than look for emergency=fire_hydrant + > fire_hydrant:pressure=positive or emergency=fire_hydrant + > fire_hydrant:pressure=suction. > In conclusion grouping different items under the same primary key and, > even worse, grouping all water sources under emergency=water_source, adds a > not necessary complexity in data managament. > Simpler is always better. In this case it is simpler to keep > emergency=fire_hydrant for pressurized hydrants and emergency=suction_point > for all other non pressurized water sources. > I'll follow you on tagging simplicity and stop argue on grouping under emergency=water_supply. If we take this way, it may be really good to add water_source on both emergency=fire_hydrant and emergency=suction_point. Even if an hydrant is always pressurized, it can be fed by a private water grid. Then we have at least 2 sources : mains and private_network (or similar) For sake of simplicity, fire_hydrant: and suction_point namespaces should be avoided as done for fire_hydrant:position Since all hydrants will have emergency=fire_hydrant, some keys can be lightened fire_hydrant:wrench => wrench (and automatically make it available for suction_points also) fire_hydrant:type or suction_point:type => fire_hydrant or suction_point To follow Moritz logic for pillars, pillar=dry_barrel or wet_barrel is enough > For suction point another proposal of refinement is needed. > Not sure on this point if grouping under a single emergency=* value is abandoned. Both features have keys in common. All the best François ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Fire hydrants vs suction_point
> Umm reflective is not a colour. In my understanding, reflective:colour should be the colour of reflective stripes, if present. > What about tagging both as fire_hydrant:type=pillar > and something like > pillar:type=dry_barrel|wet_barrel +1 Best regards Alberto --- Questa e-mail è stata controllata per individuare virus con Avast antivirus. https://www.avast.com/antivirus ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Pepper: Chili, piper, bell pepper
I am bemused by this thread. I know that when I am sent to the grocers to get peppers I’ve never been asked to get a “chili pepper”. Depending on the desired dish it might be a “Anaheim”, “Chipotle”, “Jalapeño”, “Serrano”, “Habaneros” or other type of the spicy peppers. Those are just a few of the types of peppers we might use in the Southwest United States for a Mexican inspired dish. For Asian inspired dishes there are another whole host of spicy peppers available in the local stores. If a “Bell pepper”, I will usually be requested to get a “yellow Bell pepper” or “red Bell pepper” rather than just a “Bell pepper”. So it seems altering a top level “produce=pepper” into “produce=chili_pepper” and “produce=bell_pepper” would not be a good fit for my part of the world. Looking at Wikipedia, there are something like 50,000 varieties of peppers but they can be be broken into two general classes “sweet” and “chili”. So if it is desired to be more specific than just “pepper” it would seem that “chili_pepper” and “sweet_pepper” would be better. But better yet in my mind would be leaving the top level as “pepper” and adding a “variety=*” tag detailing the more specific vulgar (non-latin) name. The world is awash in varieties of common items. I don’t think we want to put all the variations into a top level tag. The concept would be to use variety to distinguish produce or products based on the commonly used local names. From taginfo it seems that a “variety” tag is already in undocumented use for wine. Why not embrace and extend that to cover other food stuffs, e.g. “produce=apples”, “variety=jonathan”. I suppose that the British word for corn is maize, so you might have “produce=maize”, “variety=sweet|field|whatever”. Driving by a field I’m pretty sure I can decide if it has corn (maize) in it. But I won’t be able to tell if it is field or sweet corn. Let me tag the top level as “produce=maize” and be done with it. Likewise, I can recognize a few varieties of peppers when they are being grown but far from all. Let me tag the field as “produce=pepper” and if I am confident of the variety I can also add that tag. The scheme of using an additional variety tag could even be used to cover the other items called peppers in English, e.g. black pepper corns could be “produce=pepper”, “variety=black_corn”. > On Aug 20, 2017, at 2:16 PM, Tom Pfeifer wrote: > > On 20.08.2017 22:48, Kevin Kenny wrote: >> The English word 'pepper' also applies to several plants in the genera >> Aframomum, Capsicum, Pimenta, Schinus, and Zanthophylum (plus others >> that are used in traditional herbal medicine but not for the kitchen). > I >> think that the original poster wanted to disambiguate among these, > > Yes of course, that's why he proposed produce=bell_pepper;chili_pepper. > >> which would make the Linnæan names the best option - there isn't any easy >> way to >> clarify it using only vulgar names. > > Well there is an easy way: Clearly describing in the wiki that produce=pepper > means the fruits of 'piper nigrum'. Introducing an inconsistent language > scheme will confuse all occasional mappers. Latin names should remain > reserved for genus=* and species=*, and you can add species:en=* for all > languages as well. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Pepper: Chili, piper, bell pepper
On 20.08.2017 22:48, Kevin Kenny wrote: The English word 'pepper' also applies to several plants in the genera Aframomum, Capsicum, Pimenta, Schinus, and Zanthophylum (plus others that are used in traditional herbal medicine but not for the kitchen). > I think that the original poster wanted to disambiguate among these, Yes of course, that's why he proposed produce=bell_pepper;chili_pepper. which would make the Linnæan names the best option - there isn't any easy way to clarify it using only vulgar names. Well there is an easy way: Clearly describing in the wiki that produce=pepper means the fruits of 'piper nigrum'. Introducing an inconsistent language scheme will confuse all occasional mappers. Latin names should remain reserved for genus=* and species=*, and you can add species:en=* for all languages as well. tom ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Pepper: Chili, piper, bell pepper
On Sun, Aug 20, 2017 at 4:15 PM, Tom Pfeifer wrote: > On 20.08.2017 21:50, Tobias Zwick wrote: >> >> And here is the wikipedia article for Piper (plant): >> https://en.wikipedia.org/wiki/Piper_(plant) > > > Well that is the Genus of 2000 different species, of which one is "Piper > nigrum", the common spice. > There are tags for genus [1] and species [2] in OSM, where you can use the > latin name. Beside these exceptions, tagging language is British English, > and in all varieties of English this spicy crop is 'pepper'. The English word 'pepper' also applies to several plants in the genera Aframomum, Capsicum, Pimenta, Schinus, and Zanthophylum (plus others that are used in traditional herbal medicine but not for the kitchen). I think that the original poster wanted to disambiguate among these, which would make the Linnæan names the best option - there isn't any easy way to clarify it using only vulgar names. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Fire hydrants vs suction_point
On 8/20/17 4:22 PM, Moritz wrote: > Just one more thing: > > Dry and wet barrel hydrants are both pillar type hydrants. > > What about tagging both as fire_hydrant:type=pillar > and something like > pillar:type=dry_barrel|wet_barrel > > So the people who are just interested in the type of hydrants > (underground, wall, pillar...) can evaluate fh:type tag. When somebody > wants to know it in more detail he can check for pillar:type. this is basically what my old proposal did. richard -- rwe...@averillpark.net Averill Park Networking - GIS & IT Consulting OpenStreetMap - PostgreSQL - Linux Java - Web Applications - Search ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Fire hydrants vs suction_point
Just one more thing: Dry and wet barrel hydrants are both pillar type hydrants. What about tagging both as fire_hydrant:type=pillar and something like pillar:type=dry_barrel|wet_barrel So the people who are just interested in the type of hydrants (underground, wall, pillar...) can evaluate fh:type tag. When somebody wants to know it in more detail he can check for pillar:type. Moritz -- von unterwegs...___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Pepper: Chili, piper, bell pepper
On 20.08.2017 21:50, Tobias Zwick wrote: And here is the wikipedia article for Piper (plant): https://en.wikipedia.org/wiki/Piper_(plant) Well that is the Genus of 2000 different species, of which one is "Piper nigrum", the common spice. There are tags for genus [1] and species [2] in OSM, where you can use the latin name. Beside these exceptions, tagging language is British English, and in all varieties of English this spicy crop is 'pepper'. [1] https://wiki.openstreetmap.org/wiki/Key:genus [2] https://wiki.openstreetmap.org/wiki/Key:species On 20/08/2017 15:02, Tom Pfeifer wrote: Number 2 and 3 are fine for me. However I could not find 'piper' as a synonym for the spice in my English dictionaries. A piper is a player of a bagpipe or sometimes a flute, thus that is highly confusing. IMHO it would be sufficient to clarify that produce=pepper means the https://en.wikipedia.org/wiki/Black_pepper (Piper nigrum) (so you were referring to the latin term?), and the other to https://en.wikipedia.org/wiki/Bell_pepper (Capsicum) and their spicy versions https://en.wikipedia.org/wiki/Chili_pepper So far none of them is used in the database, so it is just a preemptive definition and no deprecation process. ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Fire hydrants vs suction_point
>For suction point another proposal of refinement is needed. +1 I'm currently on vacation but will do something when I'm back in two weeks. So will be more quiet from my side until then. Cheers Moritz ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Pepper: Chili, piper, bell pepper
You are right. Here is the correct picture: https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_piper.jpg And here is the wikipedia article for Piper (plant): https://en.wikipedia.org/wiki/Piper_(plant) Tobias On 20/08/2017 15:02, Tom Pfeifer wrote: > Number 2 and 3 are fine for me. However I could not find 'piper' as a > synonym for the spice in my English dictionaries. A piper is a player of > a bagpipe or sometimes a flute, thus that is highly confusing. > > IMHO it would be sufficient to clarify that produce=pepper means the > https://en.wikipedia.org/wiki/Black_pepper (Piper nigrum) (so you were > referring to the latin term?), and the other to > https://en.wikipedia.org/wiki/Bell_pepper (Capsicum) and their spicy > versions https://en.wikipedia.org/wiki/Chili_pepper > > So far none of them is used in the database, so it is just a preemptive > definition and no deprecation process. > > BTW your pepper picture does not work in both versions. > > On 20.08.2017 14:27, Tobias Zwick wrote: >> Whoops, it is >> >> https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_pepper.jpg >> >> >> https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_chili.jpg >> >> >> https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_bell_pepper.jpg >> >> >> Tobias >> >> On 20/08/2017 14:00, Tobias Zwick wrote: >>> Hey >>> >>> This is a follow up of my earlier question about whether to use trees=, >>> crop= or produce= for orchard produces. >>> >>> I'd like to establish produce=pepper as deprecated because it is >>> ambiguous. All the following are also known as pepper (with picture): >>> >>> 1. produce=piper >>> aka "pepper", "piper", "black/green/white pepper" >>> https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_pepper.png >>> >>> >>> 2. produce=chili >>> aka "chili pepper", "chili", "chilli" >>> https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_chili.png >>> >>> >>> 3. produce=bell_pepper >>> aka "pepper", "sweet pepper", "bell pepper", "capsicum" >>> https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_bell_pepper.png >>> > > > ___ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Pepper: Chili, piper, bell pepper
Number 2 and 3 are fine for me. However I could not find 'piper' as a synonym for the spice in my English dictionaries. A piper is a player of a bagpipe or sometimes a flute, thus that is highly confusing. IMHO it would be sufficient to clarify that produce=pepper means the https://en.wikipedia.org/wiki/Black_pepper (Piper nigrum) (so you were referring to the latin term?), and the other to https://en.wikipedia.org/wiki/Bell_pepper (Capsicum) and their spicy versions https://en.wikipedia.org/wiki/Chili_pepper So far none of them is used in the database, so it is just a preemptive definition and no deprecation process. BTW your pepper picture does not work in both versions. On 20.08.2017 14:27, Tobias Zwick wrote: Whoops, it is https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_pepper.jpg https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_chili.jpg https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_bell_pepper.jpg Tobias On 20/08/2017 14:00, Tobias Zwick wrote: Hey This is a follow up of my earlier question about whether to use trees=, crop= or produce= for orchard produces. I'd like to establish produce=pepper as deprecated because it is ambiguous. All the following are also known as pepper (with picture): 1. produce=piper aka "pepper", "piper", "black/green/white pepper" https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_pepper.png 2. produce=chili aka "chili pepper", "chili", "chilli" https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_chili.png 3. produce=bell_pepper aka "pepper", "sweet pepper", "bell pepper", "capsicum" https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_bell_pepper.png ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
Re: [Tagging] Pepper: Chili, piper, bell pepper
Whoops, it is https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_pepper.jpg https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_chili.jpg https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_bell_pepper.jpg Tobias On 20/08/2017 14:00, Tobias Zwick wrote: > Hey > > This is a follow up of my earlier question about whether to use trees=, > crop= or produce= for orchard produces. > > I'd like to establish produce=pepper as deprecated because it is > ambiguous. All the following are also known as pepper (with picture): > > 1. produce=piper > aka "pepper", "piper", "black/green/white pepper" > https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_pepper.png > > 2. produce=chili > aka "chili pepper", "chili", "chilli" > https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_chili.png > > 3. produce=bell_pepper > aka "pepper", "sweet pepper", "bell pepper", "capsicum" > https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_bell_pepper.png > > Any comments? > > Tobias > > ___ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
[Tagging] Pepper: Chili, piper, bell pepper
Hey This is a follow up of my earlier question about whether to use trees=, crop= or produce= for orchard produces. I'd like to establish produce=pepper as deprecated because it is ambiguous. All the following are also known as pepper (with picture): 1. produce=piper aka "pepper", "piper", "black/green/white pepper" https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_pepper.png 2. produce=chili aka "chili pepper", "chili", "chilli" https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_chili.png 3. produce=bell_pepper aka "pepper", "sweet pepper", "bell pepper", "capsicum" https://raw.githubusercontent.com/westnordost/StreetComplete/master/app/src/main/res/drawable-xxhdpi/produce_bell_pepper.png Any comments? Tobias ___ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
