That's kinda why I was asking. This works:
gdalbuildvrt -allow_projection_difference \
result.vrt \
STACIT:"/vsis3/sentinel-s2-l2a-stac/2025/12/18/S2C_OPER_MSI_L2A_TL_2CPS_20251218T212314_A006718_T11SMA.json":asset=scl
\
STACIT:"/vsis3/sentinel-s2-l2a-stac/2025/12/17/S2B_OPER_MSI_L2A_TL_2BPS_20251217T200148_A045870_T10JBQ.json":asset=scl
This does not:
gdal raster stack \
STACIT:"/vsis3/sentinel-s2-l2a-stac/2025/12/18/S2C_OPER_MSI_L2A_TL_2CPS_20251218T212314_A006718_T11SMA.json":asset=scl
\
STACIT:"/vsis3/sentinel-s2-l2a-stac/2025/12/17/S2B_OPER_MSI_L2A_TL_2BPS_20251217T200148_A045870_T10JBQ.json":asset=scl
\
result.vrt --overwrite
Is there a way to create .vrt with different projections in GDAL cli,
like gdalbuildvrt does?
Thanks!
Scott
On 12/19/25 15:56, Even Rouault wrote:
Le 20/12/2025 à 00:46, Scott a écrit :
Hey Even,
Will do.
In this case I was working with Sentinel L2A. One raster was zone 10
and the other was zone 11, which would cause stack to complain.
huh, and what result do you expect from stacking tiles in different UTM
zones, when no on-the-fly reprojection is done ... That will result in
non sense.
_______________________________________________
gdal-dev mailing list
[email protected]
https://lists.osgeo.org/mailman/listinfo/gdal-dev
