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

> There are some available options I see: > What do you prefer or do you have another options to add IMHO: it is a hard problem ..( we need more use cases ... for find the global optimum ) on the other hand - I am interested in your Proof of Concept solutions. Probably we need a

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

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

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

Hi, Sorry for my, probably stupid, questions. 1. Is all this written in java? 2. Is there anything going on in Haskell? I’d love to be involved in something using Haskell. Thanks for your answer. Jean Marie Falisse Berensheide, 3 B 1170 Watermael-Boitsfort Belgique +32 2 673 32 22 +32 479

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

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