Re: [Tagging] Nonbreakable spaces in name tags

[Pander]

On 01/31/2018 08:09 PM, Matej Lieskovský wrote:
> @Marc:
> Nominatim handles nbsp well.
> Renderers seem to either ignore it or make use of it.
> Most editors seem to handle it well, but whitespace highlighting would
> be welcome.
> Overpass... theoretically, it is doing exactly what it should be
> doing. Somehow making it simpler to create a regex that does Unicode
> collation would be nice.
>
> Is there anything that literally breaks? I don't think not doing
> Unicode collation at all is an excuse.
Is there also a case for non-breaking hyphens? For example
   's-Hertogenbosch (a place in the Netherlands)

is hyphenated as

   's-
   Hertogenbosch

 which is incorrect. In Dutch you are not allowed to hyphenate less than
two letters. Aparently the apostrophe is calculated as one too. It
should remain one word or hyphenate, when really needed, to

   's-Hertogen-
   bosch

>
> On 31 January 2018 at 19:43, Simon Poole  wrote:
>>
>> Am 31.01.2018 um 19:33 schrieb Simon Poole:
>>> IMHO we should in general treat all unicode space variants as a nomal
>> that should have been "normal"
>>
>>
>>
>> ___
>> 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 mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] colour gray or grey ?

[Pander]

On 10/04/2017 11:13 PM, Pander wrote:
> On 10/04/2017 11:07 PM, marc marc wrote:
>> Hello,
>>
>> https://wiki.openstreetmap.org/wiki/Key:colour
>> gray or grey ? I don't understand why wiki have 2 values.
> 
> Both are correctly spelled.

and because it used this standard https://www.w3.org/TR/css3-color/ see
particularly https://www.w3.org/TR/css3-color/#svg-color

> 
>>
>> Regards,
>> Marc
>> ___
>> 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 mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Re: [Tagging] colour gray or grey ?

[Pander]

On 10/04/2017 11:07 PM, marc marc wrote:
> Hello,
> 
> https://wiki.openstreetmap.org/wiki/Key:colour
> gray or grey ? I don't understand why wiki have 2 values.

Both are correctly spelled.

> 
> Regards,
> Marc
> ___
> 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] shop=fashion

[Pander]

Hi all,

I am not in favour of possible confusing meanings of names of tages and values 
in other languages than English influence these. Otherwise there is no end to 
this. Better add properly translated pages to the wiki.

Best,

Pander

On August 30, 2017 9:37:50 AM GMT+02:00, Simon Poole <si...@poole.ch> wrote:
>I'm afraid we would start running out of usable words real fast if we
>could only use those with non-confusing meanings in their original and
>other languages (maybe Kindergarten, oh perhaps rather not :-)).
>
>Seriously the term boutique is so firmly anchored in the English
>language that doing away with the term in OSM is likely not going to
>work. As to Daniels suggestion of adding more subtags, it doesn't seem
>to be sensible to replace the existing clothes tag with clothes:type
>(minus a couple of values) just so that things are a bit more
>systematic. Adding the others, and using them on boutique, fashion and
>clothes (plus the other garment related top level objects) why not.
>
>Naturally in the end this doesn't actually answer my question as to
>what
>the defining aspects of shop=fashion are :-).
>
>Simon
>
>Am 29.08.2017 um 19:27 schrieb Severin Menard:
>> Hi,
>>
>> IMHO, I would drop shop=boutique because it is one of the most
>> confusing tag, especially in French-speaking contexts.
>>
>> Basically in French from France, boutique is a generic word meaning
>> shop. More than what it sells, it designates the place, generally not
>> very large ("magasin" would then more used). A French butcher tells
>to
>> his/her family after the breakfast: "Have a good day everyonem, I
>will
>> open the boutique now". We have an expression for "boutique de"
>> (literally shop of) something, that can be used for clothes from
>which
>> I guess derivates the shop=boutique concept. Is it only in the
>> Anglo-sphere that the word boutique means this or also in other
>> cultural contexts? Eg in Brazil as far as I know people do not use
>> boutique, while they are quite fond of French words (like maison
>> meaning house) for shops that want to be considered as "chique".
>>
>> In French-speaking African countries, this generic word is massively
>> used for the most generic shop by far: a small convenience store,
>> selling food and non food items all over the walls, up to the
>ceiling,
>> where you ask at a desk what you want. This makes it a kind of kiosk,
>> even if many are not separate shops but taking one part of the
>> basement of a building. And they are not chic at all. And they are
>> very, very numerous: in a large city you find one every 50 or 100
>> meters. For sure there are more African boutiques in the world than
>> the boutiques of hand-made fashion clothes. Of course, new African
>> contributors in these countries logically use shop=boutique for their
>> own cultural reality so some streets in Africa are full of
>false-cognates.
>>
>> So IMHO I would tag these fashionable shop the most generic way as
>> possible, not reflecting only one specific cultural context and
>> avoiding using boutique. I think a subtag to differentiate
>> ready-to-wear and hand-made would fit. What do you think?
>>
>> Sincerely,
>>
>> Severin
>>
>>
>> Date: Mon, 28 Aug 2017 14:42:38 +1000
>> From: Graeme Fitzpatrick <graemefi...@gmail.com
>> <mailto:graemefi...@gmail.com>>
>> To: "Tag discussion, strategy and related tools"
>>         <tagging@openstreetmap.org
><mailto:tagging@openstreetmap.org>>
>> Subject: Re: [Tagging] shop=fashion
>> Message-ID:
>>        
>>
><cap4zaxr9b_5p0fwck5w-32xkwpsuv19oh-kxsohygue7y-x...@mail.gmail.com
>>
><mailto:cap4zaxr9b_5p0fwck5w-32xkwpsuv19oh-kxsohygue7y-x...@mail.gmail.com>>
>> Content-Type: text/plain; charset="utf-8"
>>
>> Hi
>>
>> Just consulted with an authority in these matters - my wife! :-)
>>
>> Her take:
>>
>> shop=clothes is chain stores (ie same shop in multiple shopping
>> centres /
>> towns) aimed at lower-middle end of the market
>>
>> shop=fashion is middle - higher end, but still chain stores
>>
>> shop=boutique is "one-off" shops eg selling hand-made rather than
>> mass-produced clothes; niche / speciality items etc
>>
>> Hope that helps?
>>
>>
>> Thanks
>>
>> Graeme
>>
>>
>>
>>
>>
>> ___
>> 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] Beautified JSON presets for natural=tree

[Pander]

On 07/22/2017 04:22 PM, Adam Snape wrote:
> Hi
> 
> I wasn't arguing in favour of the change, merely addressing John Willis'
> concern. I suppose the intention might be to reduce the likelihood of
> erroneous descriptive name tags such as name=tree. New mappers sometimes
> often fail to realise that name boxes in the editors often should be
> left blank. I suspect that JOSM users are much less likely to make this
> mistake. Then again, I suspect they are also much less likely to be
> deterred from leaving a name because there is no preset name box.
> 
> Regards,
> 
> Adam

Rarely used tags also take up valuable space in apps such as Vespucci.

> 
> On 22 July 2017 at 14:24, Shawn K. Quinn  > wrote:
> 
> On 07/22/2017 08:18 AM, Craig Wallace wrote:
> > On 2017-07-22 13:50, Adam Snape wrote:
> >> Hi,
> >>
> >> Removing the name key from the JOSM preset wouldn't stop somebody
> >> adding a name tag in the few cases where a tree really was named. Nor
> >> would it remove name tags from existing trees.
> >
> > But what's wrong with having the name as an optional tag on the preset?
> > if it is not relevant for that particular tree, just leave it blank.
> > Yes it is the minority of trees, but I think there are quite a few trees
> > that have some sort of name. And it is often of historic interest, so
> > worth recording it.
> 
> If I remember right, we have this field on highway=traffic_signals even
> though only one country (Japan) uses it.
> 
> --
> Shawn K. Quinn >
> http://www.rantroulette.com
> http://www.skqrecordquest.com
> 
> ___
> 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 mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

[Tagging] Beautified JSON presets for natural=tree

[Pander]

Hi all,

I would like to proposed some improvements to Beautified JSON presets
for natural=tree.

In short these are:
 1. rename label "Type" to "Leaf Type" for key `leaf_type` to explain
the key better and avoid confusion with key `type` which is no longer
used for trees
 2. rename label "Cycle" to "Leaf Cycle" for key `leaf_cycle` to explain
the key better
 3. add `key circumference` with label "Circumference (m)" to capture
during survey
 4. add key `diameter_crown` with label "Diameter crown (m)" to capture
during survey
 5. remove key `name` as it is rare for trees

Discussion that was the basis for this is found at
https://github.com/simonpoole/beautified-JOSM-preset/issues/18#issuecomment-317171508
Note that the proposal has already had some evolution. Subsequently,
tree_row could also benefit from a review.

Curious to your views on this.

Best,

Pander

___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging