[teiid-issues] [JBoss JIRA] (TEIID-3931) Add support for odata service geospatial handling

[Steven Hawkins (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-3931?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13636272#comment-13636272 ] 

Steven Hawkins commented on TEIID-3931:
---------------------------------------

We do already have the ODataWKTWriter, so I can workaround that issue to generate the value object - however the geojson support is effectively broken.  The value parsing requires the srid to be specified - even if 0.  However the geojson logic will throw an exception if the srid is set - https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67cab6bb424239/lib/server-core/src/main/java/org/apache/olingo/server/core/serializer/json/ODataJsonSerializer.java#L991

Looking at the output for the reference service: https://services.odata.org/TripPinRESTierService/Airports

It has: {code}"Loc":{"type":"Point","coordinates":[-122.374722222222,37.6188888888889],"crs":{"type":"name","properties":{"name":"EPSG:4326"}}}{code}

It would be good if the olingo geojson support could include the srid as well.  The atom logic does include srid per value handling.  Or if the assumption is that the srid will be inferred from the $metadata - then there probably shouldn't be a check at all if the srid is set on the value object.

There is also a minor issue with the olingo geospatial value object toString methods - they use an upper case type name POINT(...), but the olingo expected pattern is lower case.


> Add support for odata service geospatial handling
> -------------------------------------------------
>
>                 Key: TEIID-3931
>                 URL: https://issues.jboss.org/browse/TEIID-3931
>             Project: Teiid
>          Issue Type: Enhancement
>          Components: OData
>            Reporter: Steven Hawkins
>            Assignee: Steven Hawkins
>             Fix For: 11.2
>
>
> We should use the Edm.Geometry type for the Teiid geometry type (we can also use system metadata to see if it's appropriate to use a geometry subtype) along with any geospatial operations that odata and Teiid support.



--
This message was sent by Atlassian JIRA
(v7.5.0#75005)