It's fine to use short_name= if that's a commonly-used shorter name for a feature, which might be used by a renderer when they want a more concise name for rendering, for example, and which is still a name that is in use locally.
I'm just mentioning that it's not necessary to add this to help search applications only. - Joseph Eisenberg On 12/28/19, stevea <[email protected]> wrote: > Right: I've wondered if short_name would be appropriate in this case. Our > wiki says short_name would work, Joseph says "not," though I suppose it is > ultimately up to the search machinery and what it does. If, indeed, as > Joseph says, it already does this (or "they" already do this), the need for > our documented short_name value simply goes away. > > SteveA > >> On Dec 27, 2019, at 7:21 PM, Joseph Eisenberg <[email protected]> >> wrote: >> >> It's not necessary to add an alternative like "Josephine" if the name= >> is already "Josephine County" because geocoding and search application >> already know to search for part of a name. >> >> For example this search already finds the "Josephine County" >> administrative boundary as the first result: >> https://www.openstreetmap.org/search?query=Josephine - and there is no >> short alt_name or short_name. >> >> So I think there is no reason to have this information duplicated if >> we are just worried about search. >> >> -Joseph Eisenberg > > _______________________________________________ Talk-us mailing list [email protected] https://lists.openstreetmap.org/listinfo/talk-us
