If the scene is a "duplicate", that is, it is overlapping in area and time with a previous scene already processed, then this scene is not being processed. Before a WARNING message was issued in those cases. But this PR change this to a info message instead, as it is actually normal behaviour.
NB! One can leave out this check (processing any data that comes in - both DR and EARS for example) by not specifying a collection_area_id in the static config.
After the first commit changing the message type I made some refactoring. Hopefully this shall be easy enough to follow.
If the scene is a "duplicate", that is, it is overlapping in area and time with a previous scene already processed, then this scene is not being processed. Before a WARNING message was issued in those cases. But this PR change this to a
infomessage instead, as it is actually normal behaviour.NB! One can leave out this check (processing any data that comes in - both DR and EARS for example) by not specifying a
collection_area_idin the static config.After the first commit changing the message type I made some refactoring. Hopefully this shall be easy enough to follow.
pytestflake8