[gdal-dev] Esri JSON Curves

James Klassen klassen.js at gmail.com
Thu Oct 19 14:55:35 PDT 2017


On Thu, Oct 19, 2017 at 2:04 PM, Even Rouault <even.rouault at spatialys.com>
wrote:

> On jeudi 19 octobre 2017 13:38:38 CEST James Klassen wrote:
> > Has anyone looked at reading curved geometries from an Esri rest service
> > queried with "returnTrueCurves=true"?
> >
> > My end goal is to import the data into PostGIS. We were successful using
> > ogr2ogr to translate the curved features from a geodatabase download in
> the
> > past, but that download is being replaced with a rest service.  OGR reads
> > the rest service correctly without "returnTrueCurves=true", but we would
> > like to preserve the integrity of the curves in the source data if
> possible.
> >
> > It doesn't look like there is any code in GDAL 2.2 to deal with this
> > situation.  `ogresrijsonreader.cpp:OGRESRIJSONReadPolygon()` looks like
> it
> > is only looking for a "rings" member, not "curveRings", etc.
>
> This is indeed not supported at the moment.
> It appears to be documented in
> http://resources.arcgis.com/en/help/arcgis-rest-api/index.ht
> ml#//02r3000000n1000000#CURVE
>
> The data model is, non suprisingly, super close to what exists in
> Personnal Geodatabase
> or FileGeodatabase. Arc/CircularArc could be translated to
> CIRCULARSTRING/COMPOUNDCURVE/
> CURVEPOLYGON. Bezier curves would have to be linearized since there's no
> equivalent in
> OGC SF / ISO SQL-MM Part 3 standards.
> So this is "just" a matter of coding it.
>
>
Interesting.  So, some new JSON parsing code feeding into similar code to
what already exists in other drivers to create the right OGR objects.  It
just comes down to time and/or money to actually implement it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20171019/9ddbc7c2/attachment.html>


More information about the gdal-dev mailing list