[
https://issues.jboss.org/browse/TEIID-3931?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-3931:
---------------------------------------
Here's a running list of Olingo issues:
1. toString of Geospatial value types should use lower case type names
2. Polygon should support multiple interior holes.
3. The srid should optionally be associated with the value in json output -
https://github.com/apache/olingo-odata4/blob/1fef3a131ea4cc334151a7f10b67...
Otherwise VARIABLE support is not possible.
4. The url parser requires an srid (because it's based upon the string to value type
logic).
3/4 Together mean that any creation of value object from string parsing is then not valid
for json output.
5. srid is not included in xml/json metadata MetadataDocument*Serializer - it is only
included in type definitions in json metadata, but that is unlikely to be utilized.
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)