Hey Olivier,hey Mailing-List,
I cleaned up my repository and text form of the specification with
examples can now be found at
https://github.com/ValorNaram/transformation-table-osmtags/blob/master/spec/README.md
. The JSON form of the specification can be found in the same tree at
On 12/12/2019 17:47, Sören Reinecke via dev wrote:
Nothing is wrong with GitHub issues but GitHub has limitations when it
comes to instant team talks. Slack allows to open subthreads when a
point from someone needs to be negotiated. And that allows more deep
communication and organisation.
I think it's time to think about the specification. My idea is to create a format which we can use to import rules from existing projects to, collect and process them all united and then export then back to the various formats used by several projects. The specification therefore is the "bridge"
Nothing is wrong with GitHub issues but GitHub has limitations when it comes to instant team talks. Slack allows to open subthreads when a point from someone needs to be negotiated. And that allows more deep communication and organisation. Original Message Subject: Re: [OSM-dev]
iscussion and work. Ask me and
> I will invite you.
>
> Cheers
>
> Sören Reinecke alias Valor Naram
>
>
> Original Message ----
> Subject: Re: [OSM-dev] tagtransform for OSM - An effort make tagging and
> using OSM data easier; bridging different worlds
Hi all,I've now set up a Slack Workplace for further discussion and work. Ask me and I will invite you.CheersSören Reinecke alias Valor Naram Original Message Subject: Re: [OSM-dev] tagtransform for OSM - An effort make tagging and using OSM data easier; bridging different worlds
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
To: dev@openstreetmap.org
Subject: Re: [OSM-dev] tagtransform for OSM - A effort make tagging and
using OSM data easier; bridging different worlds
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 which
could add hints to wiki pages.
Or maybe a rule generator which could create rules for a target program like
mkgmap?
Gerd
--
Sent from:
On 06/12/2019 14:08, Jean Marie Falisse wrote:
1. Is all this written in java?
Taking the examples from
https://www.openstreetmap.org/user/SomeoneElse/diary/391484 :
* osmosis is written in Java
* osmium is I believe C++
* osm2pgsql's lua interface (obviously) calls things written in
> Probably we need a "Metadata Working Group" to collect this type of informations,> and store the information in the "central metadata repository"(?) .. ( with a good license ) Yes, you're right. We need a group of people working on a specification and on tools to make it easier to validate and
ransform 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
Hello Jean Marie,> 1. Is all this written in java?The specification itself is written in JSON. The programs which parse the spec and use it can be written in the language of your desire. I personally will write one for python3 and one for _javascript_.> Is there anything going on in Haskell? I’d
pactibility 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?
>
> Cheers
>
> Sören Reinecke alias Valor Naram
>
>
> Original Message ----
> Subject: Re: [OSM-dev
There are some available options I see: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
> 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
> what issue was it that you hit that led you to conclude that (initially) tag homogenisation for specific tags was a goal worth pursuing, followed by the initiative to create a "master list of "tag X means the same as Y"? The situation of that I needed to support both `diaper` and
On 05/12/2019 19:24, Sören Reinecke wrote:
> Are you planning to make something that can be integrated directly
into that (or mkgmap, or osmand etc.**).?
No, this is not my aim.
That's a shame. It looks like you're trying to solve the part of the
problem that isn't really much of a
> At your github repository it looks like you're planning to store an explicit list of "tag X means the same as tag Y". Is this going to be stored project by project so that you can say "project A thinks that tag X means the same as tag Y but project B does not"?Yes but I didn't resolve the
On 05/12/2019 14:50, Sören Reinecke via dev wrote:
I currently write a specification for tranforming tags in
OpenStreetMap to make life of data customers easier.
Firstly, thanks for trying to make the lives of people trying to do
things with OSM data easier!
Obviously there are two bits to
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
20 matches
Mail list logo