JDBCDataStore should not trust the geometry srid, and use the native srid
instead
---------------------------------------------------------------------------------
Key: GEOT-1990
URL: http://jira.codehaus.org/browse/GEOT-1990
Project: GeoTools
Issue Type: Improvement
Components: data h2
Affects Versions: 2.5-RC0
Reporter: Andrea Aime
Fix For: 2.5.0, 2.6-M0
Currently the JDBCDataStore tries to get the srid out of the Geometry itself.
Oracle tests are now breaking because of this, since the spatial index checks
the inserted geometry srid is equal to the native one.
Generally speaking, whatever is coming from outside (geometry or geometry
descriptor) cannot be trusted to carry the proper native srid, be it because
the geometry has been created without setting it (most common) or because the
feature type has been altered along the way (retyping, whatever else).
We should instead stick the native srid as a user property of the
GeoemtryDescriptor, and access the geometry descriptor generated by the
datastore itself when doing any geometry related operation (to make sure to
grab the srid, and the right one).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
