On Sun, May 10, 2015 at 5:53 PM, Friedrich Volkmann <b...@volki.at> wrote:

> On 10.05.2015 10:38, Eugene Alvin Villar wrote:
> > I prefer designation=* since it it already a widely used tag that fits
> the
> > intended purpose of the proposed admin_title=* tag. The question on
> whether
> > the value should be human-readable or machine-readable can be solved by
> > using correspondence tables to link the two. Barring such a table, I
> don't
> > see a catastrophic problem in automatically converting "civil_parish" to
> > "Civil Parish" and vice versa, to use the example in the talk page.
>
> designation=* is widely used (193 293 times), but look at the values in
> taginfo. The only relevant value is civil_parish (3346 times). All other
> values are just a mess.
>

Then there should be an effort to standardize the possible values of
designation=* when applied to administrative entities. I think your current
proposal is a good time to discuss that.


> The automatic replacement of underscores and lowercase initials with blanks
> and uppercase initials would be easy, but no application developer will
> implement it, and the uppercase initials may be wrong in some cases.
>

Do you have any proof that application developers will not implement it,
other than just personal conjecture? And as I said before, such automatic
replacement, if wrong, is not a catastrophic problem.


> It would also be easy to put a conversion table in the wiki, similar to the
> tables we already have for implicit maxspeed and access values by highway
> type and country. But again, application developers will ignore those
> tables.
>

Again, why are you so sure that developers will ignore such tables? If a
tag such as designation=* when applied to administrative entities were to
be widely and consistently applied, and the documentation on the wiki is
clear, then developers will find value in supporting such tables.
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging

Reply via email to