[OSM-talk] You are still free to continue to use or interpret this tag as you see fit since OpenStreetMap does not have “banned features”

Hauke Stieler mail at hauke-stieler.de
Tue Mar 30 22:43:52 UTC 2021


I referred to the technical complexity of the problem. Let me reformulate 
this: The number of code lines should not be very high in order to deal with 
multiple tags meaning the same.

It's a simple decision a developer has to take: What value would I use? None 
of them? All of them? The first I see? Do I show a warning to the end user? 

Finding answers to these questions and implementing this accordingly is IMHO 
not very challenging regarding the programming part. The discussion between 
developers finding consensus is probably the difficult part here.


Am Mittwoch, 31. März 2021, 00:28:23 CEST schrieb Marc_marc:
> Le 31.03.21 à 00:07, Hauke Stieler a écrit :
> > 1. Multiple tags meaning the same is not a problem for software developers
> https://www.openstreetmap.org/way/803391443
> please share how you deal with it
> I encounter this kind of inconsistency every week
> please share also how you avoid the issue when a average mapper edit
> an objet with software, when the preset have a tag A and the objet have
> the tag B with the same meaning, but the user don't see it in the preset
> due to " Multiple tags meaning the same".
> every day there are contributors who add a postal code to an POI because
> the information is stored in another tag, otherwise (postal_code on the
> commune relationship or on a postal_code relationship)
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20210331/0f41cc51/attachment.sig>

More information about the talk mailing list