Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Panel
borderColorgrey
borderStylesolid
titleImplication

The implication of the Model CRS requirement is as follows: the geo-coding of each raster data node (if any) must be the product’s scene geo-coding or an affine wrapper of it. For This is true for map-projected products , another implication is:  the geo-coding of each (where all raster data nodes must have the same Map CRS) and all the other geo-coding types.


But this means, that we actually don't need a RasterDataNode.geoCoding property at all. We only need the Product.geoCoding and RasterDataNode.imageToModelTransform property properties! With this insight (why only now?) we must conclude that either our original requirement was either too strict or never met (for . For example the AVNIR-2 product reader in S3TBX assigns distinct geo-codings to its bands), or it is too strict.

TODO: check if the AVNIR-2 product reader is the only one with truly different geo-codings per band. If so, we could collocate one or the other band to meet the Model CRS Requirement and then replace the RasterDataNode.setGeoCoding(gc) calls by RasterDataNode.setImageToModelTransform(i2m) calls.

...