I think the behavior depends on the format/specification of the sidecar file in question.
Example:
λ ls -lh soil_group_gura.tif*
-rw-r--r-- 1 dmf 197121 26K Jun 14 2022 soil_group_gura.tif
-rw-r--r-- 1 dmf 197121 938 Jun 14 2022 soil_group_gura.tif.aux.xml
-rw-r--r-- 1 dmf 197121 5 Jun 14 2022 soil_group_gura.tif.vat.cpg
-rw-r--r-- 1 dmf 197121 270 Jun 14 2022 soil_group_gura.tif.vat.dbf
-rw-r--r-- 1 dmf 197121 1.2K Jun 14 2022 soil_group_gura.tif.xml
λ geometamaker describe -nw soil_group_gura.tif
...
sources:
- soil_group_gura.tif
- soil_group_gura.tif.aux.xml
The .aux.xml was created by GDAL, the others were not. We are listing all the files included by GDAL's GetFileList
We could consider trying to add a feature to support detecting these other files. I suspect the ones in my example are generated by ESRI software. In another example with a shapefile, the .xml file was also not included by GetFileList, even when using the ESRI Shapefile driver. So I'm not sure how we would go about determining which files are sidecar files. Having the same basename isn't good enough because it's possible for two different datasets to have the basename (e.g. foo.shp, foo.tif, foo.csv).
I think the behavior depends on the format/specification of the sidecar file in question.
Example:
The
.aux.xmlwas created by GDAL, the others were not. We are listing all the files included by GDAL'sGetFileListWe could consider trying to add a feature to support detecting these other files. I suspect the ones in my example are generated by ESRI software. In another example with a shapefile, the
.xmlfile was also not included byGetFileList, even when using theESRI Shapefiledriver. So I'm not sure how we would go about determining which files are sidecar files. Having the same basename isn't good enough because it's possible for two different datasets to have the basename (e.g.foo.shp, foo.tif, foo.csv).