What you describe is a rather trivial case. I agree that using OSM requires knowledge about all possible tagging methods.
But even when you store all phone numbers as contact:phone in the database, all data consumers will still need to offer that data when people ask for phone. Especially in the case where the mapper said "store phone=..." in the database and later wants to retrieve it. The mapper does not know that the system translated that into "contact:phone". Who will be in charge of deciding what gets transformed into another tag? Is shop=estate_agent and office=estate_agent exactly the same, or does that represent a real-world difference on how estate agents work in the world? Another example is url and contact:url, website, heritage:website. Are they really the same, or do some people use them for different purposes and perhaps multiple of them on 1 object. And what about more complex similar mappings: - a separate cycleway or cycleway=track on the main road - a separate footway or sidewalk=... - postal_code on address point or a postal code boundary - address information on building or as separate node - POI as separate node or on the building - traffic signals tag on the junction or as separate nodes on the incoming ways. - the whole discussion on landuse=forest,natural=wood,landcover=trees which are the same for some but not for others. Those cannot be easily converted from one format to another I fear that data consumers will always have to cope with multiple tagging methods. I feel it is better to properly document those "synonyms" so data consumers are aware of them and can deal with them as they like. If we have a bunch of scripts to help them with this process, the better. But the database should reflect what the mapper wrote, not some modified version of it. regards m. On Thu, Dec 5, 2019 at 6:40 PM Sören Reinecke via talk <talk@openstreetmap.org> wrote: > > Hey all, > > I currently write a specification for tranforming tags in OpenStreetMap to > make life of all stakeholders easier. Different tagging schemes have emerged > since the existence of OpenStreetMap, same are existing in parallel and a > newer ones deprecated old ones. Data customers without knowing the OSM > community much get lost, mappers use deprecated tagging schemes and newbies > get overhelmed by the bunch of possibilities OSM gives (they do not know > exactly how to map). This project aims to help developers and mappers who > want to take advantage of/contribute to the OpenStreetMap great database > which is by the way a brilliant project. This project can also help to make > tagging in OSM more orthogonal and more hassle free. > > I saw conflicting interests between OSM community, OSM developers like the iD > developers and data customers. A renderer might need data in another way as > the community contributes. The community might need another tagging scheme > than a renderer. I thought how we can resolve this, how we can get all sites > on "one table" and that is the idea I had come up with: A specification and > scripts helping to preprocess data for each group. But I hope to achieve in > long term that the community comes together with developers, approves the > automatic toggleable function "correcting tagging by means of the community" > e.g. A mapper is typing in `phone=+33 6156 785847887948950` but the converted > form `contact:phone=+33 6156 785847887948950` will appear in database. This > would make use of short-hands possible and makes life of tagging easier. > > The project bridges different worlds and is therefore a bridge. As bridge > this project should not just connect different worlds together and by > ensuring peace between those but also support exchange between those to > develop a social economy of "send and receive" This project should support > the "come together" of (OSM) developers and mappers. > > > A more readable version can be found here: > https://github.com/ValorNaram/transformation-table-osmtags/blob/master/README.md > and the principles can be found at > https://github.com/ValorNaram/transformation-table-osmtags/blob/master/principles.md > > --- > > Example 1: They want to have the phone number of a POI. There are some > problems with this: > > 1. They need to know both contact:phone and phone to get them all. > 2. They need to support them both. > 3. They need to remove one in case both keys are mapped on one POI. This > really happens, see http://overpass-turbo.eu/s/OI2. > > Example 2: They want to know how many POI's have changing tables (general: > facilities for changing a nappy of a baby). There are some problems with this > too: > > 1. They need to know both changing_table and the deprecated diaper to get > them all. > 2. They need to support them both. Difficult because they're highly > different tagging schemes. > 3. They need to remove one in case both keys are mapped on one POI. This > really happens, see http://overpass-turbo.eu/s/OI5. > > Example 3: They want to develop a mapping tool and want to correct wrong > typed in tags. There are some problems with that: > > 1. They need to know all possible tagging schemes existing for one > purpose (e.g. mapping facilities for changing the nappy of a baby). > 2. They need to know the right/approved/more logical scheme. > 3. They need to know how to convert: > > diaper=yes > diaper:female=yes > > becomes after the transformation: > > changing_table=yes > changing_table:location=female_toilet > > --- > > Basically it bridges the OSM community and developers together, it might even > resolve the conflict between iD developers and the community. > > > I want to hear your opinions on this and also feel not to shame to ask > questions. My answers will be part of the clarification of the project > "tagtransform for OSM". > > Cheers > > Sören Reinecke alias ValorNaram > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk _______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
