[teiid-issues] [JBoss JIRA] (TEIID-2384) Managing Spatial Data Types

[Tom Arnold (JIRA)]

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

Tom Arnold commented on TEIID-2384:
-----------------------------------

> Checked with postgis and they mark the functions as strict/null on null, so we'll keep the current behavior. It is a minor TODO to make the pushdown for mysql/oracle match this.

(I don't completely understand what you're saying here.)

I went with an int (as opposed to Integer) for the SRID because that's how it is on the JTS Geometry. GeometryType has a constant (UNKNOWN_SRID) that indicates that the SRID is not specified. For all of the WKB functions I've looked at, the SRID is an optional argument so I changed JDBC translator to not specify it if it's unknown. I'm not sure if this is necessary if it works as-is, but I think it makes the intent a little clearer for anyone debugging the SQL.

https://github.com/Tom9729/teiid/commit/98e3ade67e3561fb91b2a5ab4a28074581f1260a

> 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.

I think this would be a good thing to add in several places. Oracle and presumably Postgres will reproject (ST_Transform) in the case where both sides have an SRID but the SRIDs do not match. MySQL doesn't care because it doesn't use SRID. Thinking ahead, MongoDB only supports WGS84. 

It would be cool to be able to offer that reprojection capability in non-pushdown cases. I will spend some time in GeoTools trying to get a better understanding of how this works.

> 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)