[OSM-talk] [OSM-dev] tagtransform for OSM - An effort to make tagging and using OSM data easier; bridging different worlds together

[Sören Reinecke]

Hello,

I think I need to provide an overview of tagtransform for you to
understand what I want to achieve and to get the idea of bridging. An
update of the repository with better explanation will follow. Some
things changed and some users inspired me so I forgot to update the
README.md accordingly.

Tagtransform specification: (Need ideas to add to the specification,
read here the specification and here you get to know how to contribute)
- The specification enables the convertion from one format to another
by inventing a language that acts as a connection point. This is useful
for offline usage of the rules in the format the app developer can
better work with.
- Bridge between languages
  - e.g. JOSM xml <--> tagtransform specification <--> iD json
  - Data Item database <--> tagtransform specification <--> JOSM xml
- You can contribute to tagtransform
  - by improving the specification
  - by developing scripts that use the specification
  - by developing converters that convert tagtransform specification to
other formats like JSOM xml

Role of validators:
- Validators can take the data from Data Items to create validation
rules
- and can also inspire the Data Item OSM Community by providing them
with validation suggestions.

Role of editors:
- Editors can take the data from Data Items to automatically transform
deprecated tags and to discard discardable tags.
- For offline usage they can fetch data from Data Items and can
transform them to tagtransform specification.
- Recommend a specified POI tagging through presets or automatically
transforming wrong used tags like deprecated ones to new ones.

OSM Data Item Community: (important because tagtransform will use data
they create)
- They have the necessary infrastructure to host key/tag data and they
have already a bunch of these inclusive validation rules and usage
rules.
- They're mappers and understand how keys/tags are used and can
transfer that to meta sphere used by data customers, editors and
validators.
- Go to the Data Item Wikipage to get what it is all about and how to
contribute to Data Items.

Bots/Scripts: (Please do not work on unless we make the specification
production-ready)
- Can be used to query Data Item database for preprocessing data for
later use like offline usage or data analysation at larger scale
- through converting received data to tagtransform specification.
- You can contribute to tagtransform by developing scripts that make
use of the Data Item database of OSM Wiki by fetching them and
converting them to tagtransform specification.

I hope this helps

Cheers

Sören Reinecke alias ValorNaram

-----Original Message-----
From: Sören Reinecke via dev <dev at openstreetmap.org>
Reply-To: Sören Reinecke <tilmanreinecke at yahoo.de>
To: dev at openstreetmap.org
Subject: [OSM-dev] tagtransform for OSM - A effort make tagging and
using OSM data easier; bridging different worlds together
Date: Thu, 05 Dec 2019 15:50:04 +0100

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.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.

> 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".

Cheers

Sören Reinecke alias ValorNaram



_______________________________________________dev mailing 
listdev at openstreetmap.org
https://lists.openstreetmap.org/listinfo/dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20191219/94365835/attachment-0003.html>