Hi, One interest to do it may be to reduce the volume of the database by improving compression, improve indexing of the values, simplify queries by reducing the need for a request to handle variations of case in a value, simplify statistics by reducing post-analysis... for me there is an added value from a theory point of view. But you're right that in a practical POV the better would be that the editors helps in this work by improving consistency at the begining otherwise it's an endless work. Source:date might be automatically proposed at the creation of a source tag for instance. I'm of those who try to harmonize the values on different tags when it can be done (and there is an agreement on a close list of values) and I might work on source one day (even if today it's an open field). Then, as a trademark, because "Bing" is the official way to write it, then I vote to write it this way and not in another way. Yours, LeTopographeFou
Not really. Although such a move appeals to my sense of orderliness and my background in database design. All these weird variations in tag values drive me a little bit crazy but normalizing them is a lot of work that will soon be undermined by people using new free-form source tags anyhow. By the way, I use source=Bing with a capital B. On Wed, Feb 8, 2017 at 8:47 AM, Warin <61sundow...@gmail.com> wrote:
| ||
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
