Closed EmileSonneveld closed 8 months ago
org.openeo.geotrellis.layers.NoDataRasterSource is similar so could be an inspiration.
The region in question was valid in 2 UTM zones. ...29 and ...30. In Python, auto_utm_espg
gives a different result compared to the catalog. I made the code handle CRS differences for SentinelXMLMetadataRasterSource
.
Example job:
j-231129c1874e416da43266d612f91683
Minimal graph that reproduces this:Changing the spatial_extent to different CRS still shows the problem:
Unclear how this error got introduced. The fix is probably to implement all methods here: https://github.com/Open-EO/openeo-geotrellis-extensions/blob/68143219e6882dffd0d05a46aaf29e530c0b93a5/openeo-geotrellis/src/main/scala/org/openeo/geotrellis/layers/SentinelXMLMetadataRasterSource.scala#L52