[
https://issues.jboss.org/browse/TEIID-3909?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-3909.
-----------------------------------
Resolution: Done
Added support at the translator level by mapping all geometry types to our geometry type.
We do not yet have support for geography (which looks like we would need to integrate the
full geotools suite to support). The metadata import will set the appropriate srid and
type in the geometry_columns table.
A bit of messiness is the conversion in and out of the olingo string/type representation
is handled through forked classes - one from JTS (to alter the string logic since odata
does not use WKT) and one from olingo (to minimize dependencies).
Add support for odata translator geospatial handling
----------------------------------------------------
Key: TEIID-3909
URL:
https://issues.jboss.org/browse/TEIID-3909
Project: Teiid
Issue Type: Bug
Components: OData
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 9.0
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
(v6.4.11#64026)