@Applied-GeoSolutions/ags --
This makes a change to multitemporal that drops the feature of importing of 'module' from a directory pointed to by a config item 'path', like this:
and replaces it with the behavior that the 'module' config of a multitemporal step should either be:
a built-in module of multitemporal -- (i.e. 'module': 'fusion2' loads multitemporal.bin.fusion2)
a multitemporal-conformant module that is importable (i.e. 'module': 'optis.wcc' loads that module explicitly)
Note that this is backward compatible for built-in modules, and also includes the possibility of explicitly importing them as 'module': 'multitemporal.bin.fusion2')
@Applied-GeoSolutions/ags -- This makes a change to multitemporal that drops the feature of importing of
'module'
from a directory pointed to by a config item'path'
, like this:and replaces it with the behavior that the
'module'
config of a multitemporal step should either be:'module': 'fusion2'
loadsmultitemporal.bin.fusion2
)'module': 'optis.wcc'
loads that module explicitly)Note that this is backward compatible for built-in modules, and also includes the possibility of explicitly importing them as
'module': 'multitemporal.bin.fusion2'
)