Le vendredi 20 février 2015 16:36:34, Pedro Venâncio a écrit : > Hi, > > Some time ago I opened this bug report (http://hub.qgis.org/issues/11428), > because I thought it was a problem of the implementation of gdaltindex in > QGIS, but now I see that it isn't, because it also happens at the command > line. > > If I put the command line in the folder where the raster files are located > [0], gdaltindex works well, ie, with -write_absolute_path option, absolute > paths are saved in the attribute table, and without -write_absolute_path > option are saved only the names of files. > > But if I reference the input raster files with the absolute paths [1] (for > example, when files are in different folders), the -write_absolute_path > option has no influence, because absolute paths are always recorded in the > attribute table. > > This is the desired behavior, or is it a bug?
Pedro, per the usage message of gdaltindex: "" o Raster filenames will be put in the file exactly as they are specified" on the commandline unless the option -write_absolute_path is used."""" so this is at least the documented behaviour :-) In your case, you would rather need a "-write_relative_path" that would compute the relative path of the referenced paths with respect to the tile index location (which can be something that could not succeed for example if the files are on different drives on Windows) Even -- Spatialys - Geospatial professional services http://www.spatialys.com _______________________________________________ gdal-dev mailing list gdal-dev@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/gdal-dev
