Opened 7 years ago
Closed 6 years ago
#3413 closed enhancement (fixed)
r.in.gdal/v.in.ogr: add new config option to support GDAL/OGR configuration options
| Reported by: | mmetz | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | 7.6.1 |
| Component: | Datasets | Version: | svn-trunk |
| Keywords: | GDAL/OGR import | Cc: | |
| CPU: | All | Platform: | All |
Description
GDAL/OGR support setting of various configuration options [1].
For GDAL/OGR utilities, these configuration options can be set with
<GDAL|OGR tool> --config <Key> <Value>
These configuration options may be general, GDAL specific, OGR specific, or applicable to a particular GDAL/OGR driver.
Some external data can only be successfully imported if non-default configuration options are used. Therefore r.in.gdal/v.in.ogr should have a new config option to support setting of these configuration options with CPLSetConfigOption().
Change History (6)
comment:1 by , 7 years ago
| Milestone: | 7.4.0 → 7.4.1 |
|---|
comment:2 by , 6 years ago
| Milestone: | 7.4.1 → 7.4.2 |
|---|
comment:4 by , 6 years ago
| Milestone: | 7.4.2 → 7.6.0 |
|---|
Replying to neteler:
How complicated would it be to implement this?
It would be fairly simple for r.in.gdal/v.in.ogr.
Regarding v.external/r.external, it would be more complicated because the raster and vector libraries need modifications.
comment:6 by , 6 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Closing as fixed because GDAL configuration options can now be provided to r.in.gdal / v.in.ogr with the new gdal_config option in 7.6.
Regarding [r|v].external, a new ticket should be created because it requires changes at library level.
While at it, v.external should also support a simple spatial filter with a BBOX and where conditions.
Ticket retargeted after milestone closed