cmr.py line 147 has a logic that assigns the time range to be temporal if native_id argument is used. This logic was introduced just for RTC processing... and it's having unintended effect on other processing, namely DISP-S1 revision date range processing with frame ids.
Since this temporal time override logic only applies for RTC processing, it should be isolated just for that.
What did you expect?
n/t
Reproducible steps
1.
2.
3.
...
Environment
- Version of this software [e.g. vX.Y.Z]
- Operating System: [e.g. MacOSX with Docker Desktop vX.Y]
...
Checked for duplicates
Yes - I've already checked
Describe the bug
cmr.py line 147 has a logic that assigns the time range to be temporal if native_id argument is used. This logic was introduced just for RTC processing... and it's having unintended effect on other processing, namely DISP-S1 revision date range processing with frame ids.
Since this temporal time override logic only applies for RTC processing, it should be isolated just for that.
What did you expect?
n/t
Reproducible steps
Environment