This ticket is to fix an inconsistency between S1/RS2/ALOS/etc satellites' processing modules - which have a process_???_slc functions and backscatter which has coregister_secondary / apply_coregistration / etc functions - all with slightly different APIs (different function parameters mostly) that could and should be consistent with one another.
Implementing and enforcing this consistency would be a good step forward to making satellite backends modular (and thus a step toward making them like plugins, instead of the current hard-coded approach of supporting satellites)
This ticket is to fix an inconsistency between S1/RS2/ALOS/etc satellites' processing modules - which have a
process_???_slcfunctions and backscatter which hascoregister_secondary/apply_coregistration/ etc functions - all with slightly different APIs (different function parameters mostly) that could and should be consistent with one another.Implementing and enforcing this consistency would be a good step forward to making satellite backends modular (and thus a step toward making them like plugins, instead of the current hard-coded approach of supporting satellites)