Opened 8 years ago

Closed 8 years ago

#6372 closed defect (invalid)

gdal_translate layer re-order problem

Reported by: danbeavers Owned by: warmerdam
Priority: normal Milestone:
Component: GDAL_Raster Version: 1.11.3
Severity: normal Keywords: gdal_translate, re-order
Cc:

Description

gdal_translate -a_nodata 0 -projwin 713209.703116 374491.301936 715298.426748 372165.830836 -of GTiff C:/. . ./visibleRasters.vrt C:/. . ./Superfund9.tif

This does not keep the layer order intact when using multiple layers (8 in this instance) that are visible. Layer order does not follow the order displayed in QGIS.

Version info: QGIS version 2.12.3-Lyon QGIS code revision 99ac688 Compiled against Qt 4.8.5 Running against Qt 4.8.5 Compiled against GDAL/OGR 1.11.3 Running against GDAL/OGR 1.11.3 Compiled against GEOS 3.5.0-CAPI-1.9.0 Running against GEOS 3.5.0-CAPI-1.9.0 r4084 PostgreSQL Client Version 9.2.4 SpatiaLite Version 4.1.1 QWT Version 5.2.3 PROJ.4 Version 492 QScintilla2 Version 2.7.2

Change History (4)

comment:1 by Even Rouault, 8 years ago

The layer order depends on the content of the VRT. Without more elements, it's not obvious that's a GDAL bug.

comment:2 by danbeavers, 8 years ago

I did not realize that I had generated the VRT file or what it really was. Anyone else have this problem should look at http://www.gdal.org/gdalbuildvrt.html But that does not really fix the problem: "If there is some amount of spatial overlapping between files, the order may depend on the order they are inserted in the VRT file, but this behaviour should not be relied on." There does not appear to be a good solution to my problem. Close the ticket.

Last edited 8 years ago by danbeavers (previous) (diff)

comment:3 by Even Rouault, 8 years ago

As stated in my comment in #6374, the order in the VRT can actually be relied on. So your issue must be something else. Perhaps related to nodata / alpha handling ? Can you share a (possibly simplified) test case with VRT + source rasters ?

comment:4 by Even Rouault, 8 years ago

Resolution: invalid
Status: newclosed

Closing due to lack of feedback from reporter. Please reopen if you can provide something new

Note: See TracTickets for help on using tickets.