Opened 9 years ago
Last modified 9 years ago
#5816 closed defect
Create consistent Layer creation options for geometry column name and FID — at Version 1
Reported by: | jpalmer | Owned by: | Even Rouault |
---|---|---|---|
Priority: | normal | Milestone: | 2.0.0 |
Component: | default | Version: | unspecified |
Severity: | normal | Keywords: | |
Cc: |
Description (last modified by )
Various OGR vector drivers provide the option to define the name of the geometry field/column when creating a layer. When scripting for multiple output formats at runtime this is an annoyance.
GDAL should have one consistent layer creation option for this option across all drivers. It should also be possible to retain the older LCO values for compatibility reasons, but not advertise them in the documentation any more. Could be a good idea to address this before GDAL 2.0 is released :)
Below is a list of the different LCO for each driver:
Driver | Layer creation option |
MSSQLSpatial | GEOM_NAME |
PostgreSQL | GEOMETRY_NAME |
GPKG | GEOMETRY_COLUMN |
FileGDB | GEOMETRY_NAME |
MySQL | GEOMETRY_NAME |
SQLite | - none - (GEOMETRY / WKT_GEOMETRY hardcoded) |
OCI | GEOMETRY_NAME |
==> Use GEOMETRY_NAME
Similar situation with FID column name:
Driver | Layer creation option |
MSSQLSpatial | -none - (ogr_fid hardcoded) |
PostgreSQL | FID |
GPKG | FID |
FileGDB | OID_NAME |
MySQL | MYSQL_FID |
SQLite | - none - (OGC_FID hardcoded) -->TODO |
OCI | - none, but use OCI_FID configuration option that default to OGR_FID |
==> Use FID
Change History (1)
comment:1 by , 9 years ago
Description: | modified (diff) |
---|---|
Milestone: | → 2.0 |
Owner: | changed from | to
Summary: | Create consistent Layer creation options for geometry column name → Create consistent Layer creation options for geometry column name and FID |