Feature request #9477
GDAL translate: support ESRI rasters folders names as inputs
|Assigned to:||-||% Done:||
|Target version:||Future Release - Lower Priority|
|Platform version:||Pull Request or Patch supplied:||No|
GDAL translate: conversion of ESRI Raster to tiff has a bug
ESRI rasters are viewed by GDAL as a folder with several files (see attached esri raster) and not as a single file. To convert an ESRI raster the user has to enter the folder and selecte hdr.adf as input and only then can the conversion begin. This is a bug since GDAL translate (when run from the command line) can do this by simply pointing the folder.
The fix for this bug should also take into account that the output of gdal_translate takes the correct name of the ESRI raster, which in this case is "test_raster" and not "hdr".
I'm setting the priority to High because this bug doesn't allow users to do batch conversion (i.e., select several rasters stored in a folder) of ESRI rasters.
Updated by Giovanni Manghi about 3 years ago
- Tracker changed from Bug report to Feature request
- Subject changed from GDAL translate: conversion of ESRI Raster to tiff has a bug to GDAL translate: support ESRI rasters folders names as inputs
- Priority changed from High to Normal
- Target version set to Version 2.2
There is no crash or data corruption, so I'm lowering the priority.
The issue is not in GDAL (that by the way would have lead to close this ticket as invalid) but in gdal tools:
GDAL can use as inputs the folders (names) ESRI rasters are contained, GDAL tools can't, so it is not possible to do a batch job to convert many ESRI rasters to other formats.
Updated by Filipe Dias about 3 years ago
I looked into GRASS and SAGA and both have the same problem, which means that in the FOSS GIS world, batch conversion of ESRI rasters is problematic. Unfortunately many organizations have their rasters saved in this format and it's a pain to work with them (or convince them to change to QGIS) because of this.
There are of course workarounds  but it would be very important to have this fixed in QGIS:
Updated by Jürgen Fischer almost 3 years ago
- Target version changed from Version 2.2 to Future Release - Lower Priority
Also available in: Atom