support new overpass geometries about osmtogeojson HOT 7 CLOSED

first step for center coordinates in osm-xml: f68658f

from osmtogeojson.

Hard to implement until a proper JSON schema is defined on Overpass API side. json scheme documentation here: drolbr/Overpass-API#93

from osmtogeojson.

There's work underway to also support additional Overpass API geometries for umap import (see separate ticket).

As the import process depends on osmtogeojson, there were some open questions, if the following query could already be handled correctly by osmtogeojson (http://overpass-turbo.eu/s/4kq).

I tried the web interface on http://tyrasd.github.io/osmtogeojson/ but got an empty feature list. I don't know exactly if this is expected or there's some issue with the query itself? I would expect 2 point-like features as a result.

Relevant Coding for osm xml seems to be available on the neogeometries branch. Would this be merged into gh-pages in the near future?

from osmtogeojson.

Yes, the relevant code is currently only in the separate development branch neogeometries (overpass turbo uses code from that branch at the moment). Surely, it will eventually get merged into the main branch and be available in a packaged npm release.

from osmtogeojson.

I just raised an issue for the same thing on uMap (under a different title so didn't find @mmd-osm's issue) so I'd like to add my support for this change.

Any progress on "eventually get merged"?

from osmtogeojson.

Version 2.1.0 has just been released which has full support for both the center and bounds geometry options (example)! There is still some work to do to get full geometry running, though…

from osmtogeojson.

In the meantime full geometry has also been implemented. You can test it out on the beta instance of overpass turbo.

from osmtogeojson.