[
https://issues.jboss.org/browse/TEIID-2384?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2384:
---------------------------------------
Pulled in another set of commits from Tom with some additional refinements.
TODO:
- determine how the SRID will be associated when reading.
- jts does not care if the srid matches when performing the various system functions. We
may need to restrict to only matching srids to stay consistent with expected source
behavior.
- oracle and others seem to use null rather than 0 for an unknown srid. So we may want to
use an Integer field on the GeometryType and update the FROM Text/Binary methods
appropriately.
- the mysql distance function may not be appropriate for pushdown since at least in 5.6 it
was somewhat of an approximation.
- add postgis support to the pg translator
- add get/set srid functions
Managing Spatial Data Types
---------------------------
Key: TEIID-2384
URL:
https://issues.jboss.org/browse/TEIID-2384
Project: Teiid
Issue Type: Feature Request
Components: Query Engine
Affects Versions: 8.2
Reporter: luca gioppo
Assignee: Steven Hawkins
Labels: spatial, types
Fix For: 8.10
It would be useful to be able to consume data from spatial database exposing the VDB as a
spatial database to other application (imagine geoserver).
TEIID could be strategic for merging georeferenced data and make it available to those
systems.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)