Changes between Version 10 and Version 11 of rfc41_multiple_geometry_fields
- Timestamp:
- Feb 27, 2015, 6:29:29 AM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
rfc41_multiple_geometry_fields
v10 v11 425 425 changes unrelated to this RFC) 426 426 427 === Other candidate drivers (upgrade not covered by this RFC) ===427 === Other candidate drivers (upgrade not originaly covered by this RFC) === 428 428 429 429 * GML driver : 430 430 currently, only one geometry per feature reported. Possibility of 431 431 changing this by hand-editing of the .gfs file 432 --> implemented post RFC in GDAL 1.11 432 433 * SQLite driver : 433 434 - currently, same behaviour as current PostGIS driver. 434 435 - both the driver and the SQLite dialect could be updated to support 435 436 multi-geometry layers. 437 --> implemented post RFC in GDAL 2.0 436 438 * Google Fusion Tables driver : 437 439 currently, only the first found geometry column used. Possibility of … … 447 449 . at OGRVRTUnionLayer element level : 448 450 GeometryType, LayerSRS, ExtentXMin/YMin/XMax/YMax 451 --> implemented post RFC in GDAL 1.11 449 452 * CSV : currently, take geometries from column named "WKT". To be extended 450 453 to support multiple geometry columns. Not sure worth the effort. Could 451 454 be done with the extended VRT driver. 455 --> implemented post RFC in GDAL 1.11 452 456 * WFS : currently, only single-geometry layers supported. The standard allows 453 457 multi-geometry. Would require GML driver support first.