Ticket #3373 (closed enhancement: duplicate)
Make worldfile priority configurable
|Reported by:||craigleat||Owned by:||warmerdam|
When reading a raster dataset GDAL currently only uses the ESRI worldfile as a fall-back if georeferencing is not found in the raster file. This approach assumes that a user wants the internal georeferencing. I think this assumption is too strict and at least three use cases exist where it is desirable to override the internal georeferencing.
- The creator of a read only dataset inserted an incorrect parameter(s) into the georeferencing string.
- The dataset was created with false eastings or northings and you wish to use it without these shifts. Think of overlaying data from different providers.
- You wish to use data created in standard Transverse Mercator in the south orientated Transverse Mercator projection. Only a change of sign is required and this is easily achieved via a worldfile.
The above requirements can be achieved using the virtual raster driver (.vrt), but somehow the prevalence of worldfiles is more prolific. If an environment variable (WORLDFILE_PRIORITY) existed the priority would at least be configurable and the default would be unset hence no priority.