Hey guys, I have to come back to an issue I already mentioned in the blog post for SNAP 11, the change SNAP-3715 causes some trouble.
It now interferes with the pixelRegion parameter of my operator.
I don’t think it’s a good idea to reserve these parameter names: ‘pixelRegion’ and ‘geometryRegion’. If necessary, SNAP/gpt should print a warning or even fail when loading the operator if it finds an operator with the reserved parameter names.
An alternative implementation could be to introduce a RoiOperatorSPI which overrides
getParameterDescriptors. Here the two parameters could be added and they would show up in the automatic operator documentation, I think. The RoiOperatorSPI can be used instead of the OperatorSPI for all SNAP operators. And implementors would have the choice to use the one or the other.
I already said that this feature is not documented, so actually no user can make use of it.
@kraftek @diana_harosa @TomBlock
All the best
Marco
Marco from EOMasters - Mastering Earth Observation