a) Not working on this further.
b) Using `tagtransform for OSM` to create an own transformation specification.
c) Writing converters which convert from a format to the format of `tagtransform for OSM` and writing converters to convert from the format of `tagtransform for OSM` to another format programs can work with. Using my specification which needs to be extended to create conpactibility among different formats while ensuring that my spec can be used on its own.
What do you prefer or do you have another options to add?
Sören Reinecke alias Valor Naram
-------- Original Message --------
Subject: Re: [OSM-dev] tagtransform for OSM - A effort make tagging and using OSM data easier; bridging different worlds together
From: Imre Samu
To: Sören Reinecke
CC: OSM-Dev Openstreetmap
> I currently write a specification for tranforming tags in OpenStreetMap to make life of data customers easier.imho: we can import some good ideas from https://wiki.openstreetmap.org/wiki/Osmosis/TagTransform schema .."The tag transform Osmosis plugin allows arbitrary tag transforms to be applied to OSM data as a preprocessing step before using other tools. This allows other tools to concentrate on doing what ever they do, without having to handle numerous different tagging schemes and error corrections."imho: regexp is useful.probably the "lua" is good glue/meta language - for writing "business rules".some examples:Valhalla (routing) admin.lua ( https://github.com/valhalla/valhalla/blob/master/lua/admin.lua )Valhalla (routing) graph.lua ( https://github.com/valhalla/valhalla/blob/master/lua/graph.lua )osm2gsql - openstreetmap-carto.luaRegards,ImreSören Reinecke via dev <email@example.com> ezt írta (időpont: 2019. dec. 5., Cs, 15:59):_______________________________________________Hey all,I currently write a specification for tranforming tags in OpenStreetMap to make life of data customers easier. Different tagging schemes have emerged since the existence of OpenStreetMap, same are existing in parallel and a newer one deprecated an old one. Data customers without knowing the OSM community much get lost. This project aims to help developers who want to take advantage of 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 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.mdExample 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=yesdiaper:female=yesbecomes after the transformation:changing_table=yeschanging_table:location=female_toiletBasically it bridges the OSM community and developers together, it might even resolve the conflict between iD developers and the community.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.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".CheersSören Reinecke alias ValorNaram
dev mailing list
_______________________________________________ dev mailing list firstname.lastname@example.org https://lists.openstreetmap.org/listinfo/dev