Changes between Initial Version and Version 1 of Ticket #21273, comment 10


Ignore:
Timestamp:
03/13/2014 06:00:04 AM (8 years ago)
Author:
Jani Tiainen
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #21273, comment 10

    initial v1  
     1Reason why XE doesn't work is obvious:
     2
     3GeoDjango uses Oracle built-in WKT transformations which require Java within DB engine itself and XE is missing that.
     4
     5Also context switching between Java and PL/SQL is dead slow.
     6
    17SDO_GEOMETRY itself has been same for a good while. I do have almost working version of read/write support for Oracle XE, as well as 3D support for Oracle geometries in general.
    28
     
    410
    511Currently I think that backend I've been working on is only failing is some coordinate transformations.
     12
     13For reading I do read plain SDO_GEOMETRY object, convert it to GeoJson (it's slightly more simpler format than WKT and GEOS/GDAL supports 3D GeoJSON better than 3D WKT).
     14
     15For writing I do parse plain GEOSGeometry, construct SDO_GEOMETRY like CLOB string and push it through special PL/SQL function in a database.
     16
     17There is a caveat here: For writing installing (one time for whole database) special package is required.
Back to Top