Changes between Version 17 and Version 18 of GDAL20Changes


Ignore:
Timestamp:
Nov 3, 2011, 3:18:54 PM (12 years ago)
Author:
Even Rouault
Comment:

Mention adding new types of OGR geometries (curve geometries) and RFC 31

Legend:

Unmodified
Added
Removed
Modified

  • GDAL20Changes

    v17 v18  
    3333
    3434Might be necessary to have sub-second precision for OFTDateTime. Has been postponed because of its impact on ABI. Related ticket : #2680
     35
     36== Add new types of OGR geometries (curve geometries) ==
     37
     38Adding new types of OGR geometries (wkbCircularString, and other curve geometries that are mentionned in the last versions of Single Feature specification) can potentially break code (including drivers) not ready to deal with them. We could perhaps imagine ways (*) of adding them without being considered as a breaking change however, so not necessarily 2.0 material.
     39
     40(*) For example, a OGREnableCurveGeometries() method that user code could call to mention it is aware that the new types of geometries exist, in which case OGR will feel free to return them. If this method is not called, those curve geometries could be stroked as regular linestrings.
     41
     42(There's an embryonic sandbox with some preliminary work : http://trac.osgeo.org/gdal/browser/sandbox/rouault/gdal-ogr-curve)
     43
     44== OGR 64bit Integer Fields and FID ==
     45
     46See [wiki:rfc31_ogr_64 RFC 31: OGR 64bit Integer Fields and FID]. For exactly the same reasons given in the previous section, this could be considered as breaking change.
    3547
    3648== Fix object lifecycle management in Python bindings ==