search

nasa / opera-sds-pcm

Observational Products for End-Users from Remote Sensing Analysis (OPERA)
Apache License 2.0
16 stars 12 forks source link

[New Feature]: DISP-S1 forward processing frame-date_range black list filter #1001

Open philipjyoon opened 6 hours ago

philipjyoon commented 6 hours ago

Checked for duplicates

Yes - I've already checked

Alternatives considered

Yes - and alternatives don't suffice

Related problems

No response

Describe the feature request

We want the ability to "black out" arbitrary list of sensing datetime ranges on a per frame basis. We envision a ADT-maintained json file that specifies a list of date ranges on per frame basis. We could generalize this file a bit and add possibility of adding other per-frame processing directives. Absence of "blackout_dates" indicate that processing should proceed normally as we have data available.

It would something like the following:

{
"831": {}
"832":  {"blackout_dates": [ {"start": ""2024-12-30T23:05:24", "end": ""2025-03-15T23:05:24"}. ...]},
...
"46543": {"blackout_dates": [ {"start": ""2024-11-15T23:05:24", "end": ""2025-04-30T23:05:24"}. ...]}
}
scottstanie commented 6 hours ago

this looks good to me, just to clarifications:

  1. would you want this to be the same file as the "consistent frame database" JSON? or separate?
  2. would the datetimes have to exactly line up with an acquisition sensing time? or just be used as a range?
philipjyoon commented 5 hours ago

@scottstanie

  1. While it's not a strong preference, I'd like it to be a separate file. That way we don't have to swap out "consistent frame database" file every time we want to change the black out dates.
  2. Any arbitrary date range would work. And we can have multiple date ranges per frame as well. When we determine that at least one burst falls within a blackout date range, that entire frame-sensing_datetime will be blacked out / ignored from processing