On Mon, 20 Apr 2020 at 18:21, Martin Koppenhoefer <dieterdre...@gmail.com>
wrote:

>
>
> Am Mo., 20. Apr. 2020 um 19:01 Uhr schrieb Paul Allen <pla16...@gmail.com
> >:
>
>> Because "amenity" has come to mean "miscellaneous."
>>
>
> this is trolling,
>

 No it isn't.  I'm entirely serious.  Amenity has come to mean
miscellaneous.
This is not a good thing.

because amenity=social_facility social_facility=food_bank still has amenity
> as the "main" key, if we made it amenity=food_bank we would not change
> anything in this regard.
>

Yes, it would change matters a lot.  It means that hierarchical menus are
possible.  Instead of being presented with dozens (potentially hundreds) of
amenity values to scroll through one can select social facility and get a
sub-menu. This is easier and faster.

>
>
>> Maybe you need a better editing app on your mobile device. :)
>>
>
> I am quite satisfied with both,
>

I am not satisfied with flattening hierarchies just to keep you happy.  I
need
a better reason than the editors you choose to use mean the rest of us
should suffer from your choices.

the mobile and the desktop OSM editing solution I have chosen, and in both
> instances, it is very tedious to type tags like "social_facility:for" and
> "social_facility", which both start the same for many characters
>

If we flatten everything out, moving everything directly under amenity so
that
we don't need sub-tags, then that will mean MORE values start with the same
letters.  Unless we make each value a UID such as 6b*3kjn.  Flattening makes
matters worse for you, not easier.

BTW, good editors narrow down selections as you type.  Or present you with
sub-menus based upon hierarchies.

, while all the other tags hardly require more than 1 or 2 letters,
> sometimes 3-4, e.g. highway is typically completed from "hi" and amenity
> from "am". Any solution where tags are typed in, will benefit from more
> concise tag names.
>

And will suffer from the sort of flattening you propose.  Because the more
things
that get unique amenity values rather than being sub-tagged, the more
values will
have several first letters in common.

Note that conciseness isn't required with a good user interface.  Whatever
other merits your preferred editing solutions have, a good UI for tag
selection does not appear to be one of them.

-- 
Paul
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to