Hi Michael, At least, I found nothing shocking in your patches, so in my non-oracle-savvy eyes, this looks rather fine. It would then be interesting to see if some tests from django.contrib.gis.tests.geo3d.tests can pass with Oracle. Please create a ticket and link a pull request with your proposal, and we'll be able to further discuss this issue.
Claude Le lundi 3 novembre 2014 13:04:55 UTC+1, MG Sexton a écrit : > > Hi > > I have recently started using Django and tried to use it with our legacy > Oracle Spatial database. The geometries we store in Oracle are all 3D and > as such don’t work with Django. It boils down to this: > > select sdo_util.to_wktgeometry(sdo_geometry(3001, null, SDO_POINT_TYPE(120 > ,-30, 0), null, null)) from dual; > > Yielding the following error: > > ORA-13199: 3D geometries are not supported by geometry WKB/WKT generation. > ORA-06512: at "MDSYS.MD", line 1723 > ORA-06512: at "MDSYS.MDERR", line 17 > ORA-06512: at "MDSYS.SDO_UTIL", line 2509 > > However, as I discovered, all is not lost. A similar query: > > select sdo_util.to_gmlgeometry(sdo_geometry(3001, null, SDO_POINT_TYPE(120 > ,-30, 0), null, null)) from dual; > > Delivers something we can work with: > > <gml:Point srsName="SDO:" > xmlns:gml="http://www.opengis.net/gml";><gml:coordinates > decimal="." cs="," ts=" ">120.0,-30.0,0.0 </gml:coordinates></gml:Point> > > I am new to Python and Django, so I looked through the code, forked the > Django project, and made five changes: > > Call to Oracle uses SDO_UTIL.TO_GMLGEOMETRY to output GML: > > https://github.com/comtesacristain/django/commit/4a5732d3069fc648b887c7c7000e99f45fe60d56 > > GML regex (this probably needs work as I am terrible at regexes): > > https://github.com/comtesacristain/django/commit/96d06f8392432121610a07ed8d7a1fc4c7f5aa8c > > Accessed part of the GDAL C libraries to read from GML: > https://github.com/comtesacristain/django/commit/3cefe8651a8df60bbade66ec0410c67ee2bde1d9 > > > > Checked against the GML regex and used GDAL module > > https://github.com/comtesacristain/django/commit/2eaad60782f2d72836b026bd2cca0d9a1cfff541 > > Part of GDAL module which makes the call to the GDAL C API > > https://github.com/comtesacristain/django/commit/ad5808a5b4b0b7e6b1efb4d29dc09e7d15a344b7 > > I was wondering what it would take to have these made part of the Django > project? I am not the greatest coder, but I thought these might help with > what is currently a bug in the use of Django for 3D spatial geometries in > Oracle. > > Best Regards > > Michael Sexton. > > > > > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/eef9fdc9-e8d8-4f06-9ec6-c6942dbc24a0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
