This is a two-pronged request and the descendent of #36.
We need at a high level:
SLCs --> OPERA Burst RTC Products
{OPERA Burst RTC Products} --> DSWx S1
Note I am using {*} to indicate a group of products. Previously, I supplied only SLC IDs for 1) (as in #36) hoping the rest could be filled in, but as this is tricky, I wanted to provide as much information as possible.
I have done some accounting to provide relevant IDs to @niarenaw or other operator to ensure we are getting as close to production DSWx-S1 products as possible. Below is the relevant table.
Not all columns are necessary, but am including them for posterity. Each row is associated to a validation site.
For SDS, the most relevant columns are:
mgrs_tile: Associated MGRS tile of the validation site; we will select the one associated with the HLS tile
'slc_ids_to_cover_mgrs_tile': SLC IDs that are needed to cover an MGRS tile (note there could be multiple and separated by a space (i.e. ' ')
'burst_ids': all the JPL burst ids that cover the MGRS tile
'primary_slc_start_time' – this is the start time of the SLC ID that covers the validation site
The hope is that you can do 1) and 2) at as follows:
-> process all the RTC from the 'slc_ids_to_cover_mgrs_tile'.
-> Then use JPL burst ids and the primary SLC start time to query the metadata to get the precise {RTC burst products} needed to generate the DSWx-S1. Note: this particular step will involve some ES work by @niarenaw or another operator
Share Results
[ ] Google Earth Engine (GEE)
[ ] NASA Distributed Active Archive Centers (DAAC) User Acceptance Testing (UAT)
Venue
PST
Product
RTC-S1
SAS Version
No response
SDS Version
No response
Input Data
This is a two-pronged request and the descendent of #36.
We need at a high level:
Note I am using {*} to indicate a group of products. Previously, I supplied only SLC IDs for 1) (as in #36) hoping the rest could be filled in, but as this is tricky, I wanted to provide as much information as possible.
I have done some accounting to provide relevant IDs to @niarenaw or other operator to ensure we are getting as close to production DSWx-S1 products as possible. Below is the relevant table.
https://github.com/OPERA-Cal-Val/dswx-sar-acq-selection/blob/dev/s1_ids_for_val.geojson
Above is a geojson table with columns:
Not all columns are necessary, but am including them for posterity. Each row is associated to a validation site.
For SDS, the most relevant columns are:
mgrs_tile: Associated MGRS tile of the validation site; we will select the one associated with the HLS tile'slc_ids_to_cover_mgrs_tile': SLC IDs that are needed to cover an MGRS tile (note there could be multiple and separated by a space (i.e.' ')'burst_ids': all the JPL burst ids that cover the MGRS tileThe hope is that you can do 1) and 2) at as follows:
-> process all the RTC from the 'slc_ids_to_cover_mgrs_tile'. -> Then use JPL burst ids and the primary SLC start time to query the metadata to get the precise {RTC burst products} needed to generate the DSWx-S1. Note: this particular step will involve some ES work by @niarenaw or another operator
Share Results
Additional Notes
There is no option yet for DSWx-S1.