Thank you guys. Ok for compression, not so much hdd space wasted. There is a space coding issue too. Let's take "United States of America" for instance :
United States of America United_States_of_America United-States-of-America United_States-of-America which are as many different values. Even if contributors shouldn't use strokes or underscores, they can. And then QA has to correct mistakes to make data widely available (i.e. make objects share the same values to be targeted by a consumer request). USA is a single value corresponding to the several ones above. Should we retrieve context with other keys or deal with those ugly blank spaces ? *François Lacombe* francois dot lacombe At telecom-bretagne dot eu http://www.infos-reseaux.com 2014-06-18 12:53 GMT+02:00 Martin Koppenhoefer <dieterdre...@gmail.com>: > > 2014-06-18 11:50 GMT+02:00 François Lacombe < > francois.laco...@telecom-bretagne.eu>: > > Could someone precise me why abbreviations should always be avoided in >> tagging please ? > > > > because you can automatically create an abbreviated version from an > expanded version (for better results with the help of a dictionary), but > the other way round is impossible (without understanding of the context). > > cheers, > Martin > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging > >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging