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

[Sören Reinecke]

Hi Gerd,

nice to hear your heartbeat for tagtransform. Take a look at the GitHub
issue 
https://github.com/ValorNaram/transformation-table-osmtags/issues/3
where I wrote down the infrastructure I'm planning. There I mention also the use of bot script to automatically collect rules from various validators and rule databases and to convert these to the format tagtransform uses to unify data from different sources. This allows the modification and the convert back to all the other formats used by different programs. This way we create a sustainable and good ecosystem of validation rules.

The way the team I want to set up communicates and exchanges is GitHub
and Slack. On GitHub we will first work in my repository, later on we
can create an organisation and move the repo. In Slack I need to create
a workplace and figure out how moderation in Slack works.

Cheers

Sören Reinecke alias Valor Naram


PS: This content is of public interest that's why this e-mail belongs
to this list.

-----Original Message-----
From: Gerd Petermann <gpetermann_muenchen at hotmail.com>
To: dev at openstreetmap.org
Subject: Re: [OSM-dev] tagtransform for OSM - A effort make tagging and
using OSM data easier; bridging different worlds together
Date: Wed, 11 Dec 2019 05:38:02 -0700 (MST)

Hi all,
What could be the user interface for such a collection of rules?I can
think of a preprocessor like osmfilter or some kind of wiki tool
whichcould add hints to wiki pages.Or maybe a rule generator which
could create rules for a target program likemkgmap?
Gerd


--Sent from: 
http://gis.19327.n8.nabble.com/Developer-Discussion-f5233107.html

_______________________________________________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/dev/attachments/20191211/1c7f56eb/attachment.html>