We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It seems not possible to write a band name to geotiff metadata that is compatible with GDAL. Geotrellis writes this:
<GDALMetadata> <Item name="DESCRIPTION" sample="0">B02</Item> </GDALMetadata>
While GDAL would like to also see a "role" attribute:
<GDALMetadata> <Item name="DESCRIPTION" sample="0" role="description">B02</Item> </GDALMetadata>
In the Geotrellis code, it is very clear that the role attribute is not used:
geotrellis/raster/src/main/scala/geotrellis/raster/io/geotiff/Tags.scala
Line 52 in fa88aed
Originally reported here: Open-EO/openeo-geopyspark-driver#257
Simply write a geotiff with tags, trying to set a DESCRIPTION on the bands.
Geotrellis can generate metadata compliant with GDAL, as it already tries to do that.
Geotrellis 3.6.x
The text was updated successfully, but these errors were encountered:
Hey @jdries thanks for reporting, definitely sounds like a bug / oversight to me.
Sorry, something went wrong.
No branches or pull requests
Describe the bug
It seems not possible to write a band name to geotiff metadata that is compatible with GDAL.
Geotrellis writes this:
While GDAL would like to also see a "role" attribute:
In the Geotrellis code, it is very clear that the role attribute is not used:
geotrellis/raster/src/main/scala/geotrellis/raster/io/geotiff/Tags.scala
Line 52 in fa88aed
Originally reported here:
Open-EO/openeo-geopyspark-driver#257
To Reproduce
Simply write a geotiff with tags, trying to set a DESCRIPTION on the bands.
Expected behavior
Geotrellis can generate metadata compliant with GDAL, as it already tries to do that.
Environment
Geotrellis 3.6.x
The text was updated successfully, but these errors were encountered: