The RasterExpressionEvaluator and the RasterBandCombiner require that the input rasters have identical properties. If one raster has a spacing of 0.6666667 and the other 0.6666667000000001 then the second raster is rejected. See https://knowledge.safe.com/content/idea/58136/fuzzy-tolerance-on-rasterbandcombiner.html. Likewise if the origin is off by a picometer, and let's not talk about 20000 vs 19999 rows.
It would be nice to have a transformer that takes one raster as a reference, and then forces all other rasters (candidates) to correspond to it's properties.
This transformer would:
- resample the candidates to the reference _spacingX, _spacingY
- clip and or pad the candidates so they cover the same extent as the reference
- snap the candidates to the reference origin
