OSM Tagging model is a unique piece of knowledge and its usage could be discussed more widely, even outside of OSM.
Recent announcement of Overture Maps Foundation data schema will challenge us shortly. I’ve been involved in tagging improvement for more than 10 years and I now believe a lot in its more general usefulness, even outside of OSM.
It’s time to find how making it obvious.
First of all, tagging is a core component of OSM project and will remain as this in the future, the point isn’t to split mapping and tagging appart.
However, our tagging model could inspire (or already inspires actually) many data managers operating data bases outside of OSM.
A lack of consistency, versatility and even relevancy are sometimes noted about many data sets we can be using in general. They are at least missing some uniformity while some of them describe the exact same objects despite coming from different producers.
The more we have data, the more we need to standardize their structures.
OSM actually have the advantage to be built over a single namespace and force contributors to maintain consistency between very different concepts. It’s not an usual practice, there isn’t so much databases that gather buildings, roads, trees and utility networks in the same place.
Time spent to document tagging is now a significant force to make our semantics usable even outside of OSM.
It’s not necessary to import private databases in OSM nor use OSM tools to get benefit from usage of provided tagging, if applicable.
Developing tagging is not necessary a call to mapping or an attempt to make a given contribution mandatory. It’s also an exercice which demonstrates every day the versatility of OSM semantics and creativity of involved contributors.
In France, we already began to build strategic bridges between OSM tagging and business standards or government standards in order to make things interoperable.
- In 2017, with water hydrants minimal data structure (see OSM wiki)
- In 2021, with pedestrian accessibility standard
- Regularly, during requests for comments for government standards (utility networks, road schemas…)
Such connections are expected to reinforce worldwide in coming years.
Increasing interests about OSM tagging, just like OSM data, are concerning to protect them both at the appropriate extent. The point is to allow the most valuable usages while preserving contributors involvement.
The topic is now central since Overture Maps has announced its own data schema based upon OSM. As the OSM wiki licence regulates documentation usage, how could we regulate and protect usage of the tagging model itself?
Nothing looks more like a group of field names than another group of field names.
Except a few iconic syntaxes like opening_hours, has OSM tagging got enough originality to deserve a protection?
This post is intended to raise such concerns and improve awareness about importance of tagging, at least as important as data itself.