Changes between Version 10 and Version 11 of rfc41_multiple_geometry_fields


Ignore:
Timestamp:
Feb 27, 2015, 6:29:29 AM (5 years ago)
Author:
Even Rouault
Comment:

Update drivers that implement RFC 41

Legend:

Unmodified
Added
Removed
Modified
  • rfc41_multiple_geometry_fields

    v10 v11  
    425425        changes unrelated to this RFC)
    426426
    427 === Other candidate drivers (upgrade not covered by this RFC) ===
     427=== Other candidate drivers (upgrade not originaly covered by this RFC) ===
    428428
    429429  * GML driver :
    430430    currently, only one geometry per feature reported. Possibility of
    431431    changing this by hand-editing of the .gfs file
     432 --> implemented post RFC in GDAL 1.11
    432433  * SQLite driver :
    433434      - currently, same behaviour as current PostGIS driver.
    434435      - both the driver and the SQLite dialect could be updated to support
    435436        multi-geometry layers.
     437 --> implemented post RFC in GDAL 2.0
    436438  * Google Fusion Tables driver :
    437439    currently, only the first found geometry column used. Possibility of
     
    447449       . at OGRVRTUnionLayer element level :
    448450         GeometryType, LayerSRS, ExtentXMin/YMin/XMax/YMax
     451 --> implemented post RFC in GDAL 1.11
    449452  * CSV : currently, take geometries from column named "WKT". To be extended
    450453    to support multiple geometry columns. Not sure worth the effort. Could
    451454    be done with the extended VRT driver.
     455 --> implemented post RFC in GDAL 1.11
    452456  * WFS : currently, only single-geometry layers supported. The standard allows
    453457    multi-geometry. Would require GML driver support first.