#6358 closed defect (invalid)
drv_osm OSM_CONFIG_FILE
| Reported by: | andrewharvey | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Docs | Version: | svn-trunk |
| Severity: | minor | Keywords: | |
| Cc: |
Description
The documentation for the OSM driver at http://www.gdal.org/drv_osm.html says "You can also define an alternate path with the OSM_CONFIG_FILE configuration option" but then later down under Open options it is shown as "CONFIG_FILE". It appears that ogr2ogr accepts -oo CONFIG_FILE= and not -oo OSM_CONFIG_FILE.
I'm not sure if this is an error or I've misunderstood something (regarding the OSM_CONFIG_FILE vs CONFIG_FILE usage) but it's a bit confusing how it currently reads.
Change History (2)
follow-up: 2 comment:1 by , 8 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 8 years ago
Replying to rouault:
Thanks for the explanation, I thought that might be the case, but I wasn't sure based on the help page I read.
Note:
See TracTickets
for help on using tickets.
The doc is OK. There are 2 different mechanisms: an historic one, with (global) configuration option/environmenet variables. The name here is OSM_CONFIG_FILE. The OSM_ prefix is needed here to avoid clashing with other unrelated environmenet variables.
Since GDAL 2.0, drivers can also accept proper open option. In that case, no need for prefix as we have a context.