[gdal-dev] AutoCreateWarpedVRT changes Int16 raster to Int32
Denis Rykov
rykovd at gmail.com
Sat Aug 31 23:00:54 PDT 2024
Please disregard my previous message with the gdalinfo output. Here is the
correct one:
$ gdalinfo "dem.tif"
Driver: GTiff/GeoTIFF
Files: dem.tif
Size is 1541, 1335
Coordinate System is:
GEOGCRS["WGS 84",
ENSEMBLE["World Geodetic System 1984 ensemble",
MEMBER["World Geodetic System 1984 (Transit)"],
MEMBER["World Geodetic System 1984 (G730)"],
MEMBER["World Geodetic System 1984 (G873)"],
MEMBER["World Geodetic System 1984 (G1150)"],
MEMBER["World Geodetic System 1984 (G1674)"],
MEMBER["World Geodetic System 1984 (G1762)"],
MEMBER["World Geodetic System 1984 (G2139)"],
MEMBER["World Geodetic System 1984 (G2296)"],
ELLIPSOID["WGS 84",6378137,298.257223563,
LENGTHUNIT["metre",1]],
ENSEMBLEACCURACY[2.0]],
PRIMEM["Greenwich",0,
ANGLEUNIT["degree",0.0174532925199433]],
CS[ellipsoidal,2],
AXIS["geodetic latitude (Lat)",north,
ORDER[1],
ANGLEUNIT["degree",0.0174532925199433]],
AXIS["geodetic longitude (Lon)",east,
ORDER[2],
ANGLEUNIT["degree",0.0174532925199433]],
USAGE[
SCOPE["Horizontal component of 3D system."],
AREA["World."],
BBOX[-90,-180,90,180]],
ID["EPSG",4326]]
Data axis to CRS axis mapping: 2,1
Origin = (76.738472222222228,43.403749999999995)
Pixel Size = (0.000277777777778,-0.000277777777778)
Metadata:
AREA_OR_POINT=Area
Image Structure Metadata:
COMPRESSION=DEFLATE
INTERLEAVE=BAND
Corner Coordinates:
Upper Left ( 76.7384722, 43.4037500) ( 76d44'18.50"E, 43d24'13.50"N)
Lower Left ( 76.7384722, 43.0329167) ( 76d44'18.50"E, 43d 1'58.50"N)
Upper Right ( 77.1665278, 43.4037500) ( 77d 9'59.50"E, 43d24'13.50"N)
Lower Right ( 77.1665278, 43.0329167) ( 77d 9'59.50"E, 43d 1'58.50"N)
Center ( 76.9525000, 43.2183333) ( 76d57' 9.00"E, 43d13' 6.00"N)
Band 1 Block=1541x2 Type=Int16, ColorInterp=Gray
NoData Value=32767
On Sun, Sep 1, 2024 at 12:58 AM Even Rouault <even.rouault at spatialys.com>
wrote:
> What is the gdalinfo output on dem.tif ?
>
> Is this a bug? It appears that the data type change might be influenced by
> the nodata value.
>
> Yes, there is some logic to take the "union" of the largest data types
> involved in the warping (but it should probably ignore nodata values that
> are outside of the validity range of the input data type. I didn't check
> what it does currently)
>
>
>
> _______________________________________________
> gdal-dev mailing listgdal-dev at lists.osgeo.orghttps://lists.osgeo.org/mailman/listinfo/gdal-dev
>
> -- http://www.spatialys.com
> My software is free, but my time generally not.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/gdal-dev/attachments/20240901/bfdfcdb0/attachment.htm>
More information about the gdal-dev
mailing list