Changes between Version 33 and Version 34 of GDAL20Changes


Ignore:
Timestamp:
Feb 26, 2015, 1:16:19 AM (9 years ago)
Author:
Even Rouault
Comment:

Update status of some proposed changes

Legend:

Unmodified
Added
Removed
Modified

  • GDAL20Changes

    v33 v34  
    3535For example a 50000x50000x3 dataset cannot be RasterIO()'ed with band interleaving.
    3636
     37==> Implemented in GDAL 2.0dev per [http://trac.osgeo.org/gdal/wiki/rfc51_rasterio_resampling_progress RFC 51]
     38
    373964bit dimensions might also be necessary for WMS global datasets with very high precision, where the number of pixels might exceed 2 billion in the base overview level.
    3840
    … …  
    5153Generally, code review for stricter type would be beneficial, where possible.
    5254
     55==> New GDALOpenEx() in GDAL 2.0dev has open options per [http://trac.osgeo.org/gdal/wiki/rfc46_gdal_ogr_unification RFC 46].
     56GDALRasterIOEx() in GDAL 2.0dev has a GDALRasterIOExtraArg structure that can be extended per [http://trac.osgeo.org/gdal/wiki/rfc51_rasterio_resampling_progress RFC 51]
     57
    5358== Increase size of OGRField structure ==
    5459
    … …  
    6166(*) 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.
    6267
    63 (There's an embryonic sandbox with some preliminary work : http://trac.osgeo.org/gdal/browser/sandbox/rouault/gdal-ogr-curve)
     68==> Implemented in GDAL 2.0dev per [http://trac.osgeo.org/gdal/wiki/rfc49_curve_geometries RFC 49].
    6469
    6570== Support XYZM coordinates ==
    … …  
    7479
    7580OGR_L_SetNextByIndex() currently takes a long, which might not be appropriate on 32bit platforms or 64bit Windows.
     81
     82==> Implemented in GDAL 2.0dev per [http://trac.osgeo.org/gdal/wiki/rfc31_ogr_64 RFC 31].
    7683
    7784== Fix object lifecycle management in Python bindings ==
    … …  
    9198Related ticket : #4280
    9299
     100==> Implemented in GDAL 2.0dev per [http://trac.osgeo.org/gdal/wiki/rfc52_strict_sql_quoting RFC 52].
     101
    93102== OGR : providing a base implementation of CreateFeature(), SetFeature(), etc... called before driver specific code to implement generic checks ==
    94103
    … …  
    101110Related ticket : #4620.
    102111
     112==> Partially implemented in GDAL 2.0dev per [http://trac.osgeo.org/gdal/wiki/rfc49_curve_geometries RFC 49]: CreateFeature() and
     113ISetFeature() now call the virtual methods ICreateFeature() and ISetFeature(). The check for the update flag hasn't been done.
     114
     115
    103116== Provide improved handling for Large Raster Attribute Tables ==
    104117
    105118The current GetDefaultRAT/SetDefaultRAT implementation is not suitable for large RAT's - the whole RAT must be read and held in memory. A solution would be to create a new method to return a derived class that handles the actual reading and writing much like GetRasterBand. This derived class could have methods for reading/writing parts of specified columns from/to application managed memory and handling data type conversion much like RasterIO.
    106119
    107 ==> Implemented per [http://trac.osgeo.org/gdal/wiki/rfc40_enhanced_rat_support RFC 40]
     120==> Implemented per [http://trac.osgeo.org/gdal/wiki/rfc40_enhanced_rat_support RFC 40] in GDAL 1.11
    108121
    109122== Revise how OGR handles string encodings ? ==