Forum

Your understanding is correct, the time estimation is just for the purposes of setting the runconfig. I did do some poking around and found that you can check STUF files (.xml) to get a slightly more accurate estimation of each cycle's start time to make the time range guessing a bit more accurate. ...

For the RSLC processing, as far as I am aware, if you give a time past the RRSD in the runconfig, it shouldn't make a difference and the focus.py script should know to handle that, but if it doesn't and it throws an error, then the solution would just be to truncate the time to the RRSD start/end ti...

Sorry if it was unclear, the S3 and earthdata paths mimic one another, so the watermask link would be for example: https://nisar.asf.earthdatacloud.nasa.gov/NISAR/WATER_MASK/v0.5/EPSG4326.vrt For determining the RRSD, we would use a static file called the NISAR Track Frame Database, it should be on ...

For the DEM, that's right. The watermask files are similarly available, here is the S3 version of the links: aws s3 ls s3://sds-n-cumulus-prod-nisar-products/WATER_MASK/v0.5/ --profile daac PRE EPSG3031/ PRE EPSG3413/ PRE EPSG4326/ 2026-02-11 18:20:01 21072 EPSG3031.vrt 2026-02-11 18:20:01 20022 EPS...

Hey Jonathan, while looking into your inquiry, we do actually have workflows to manually process the L0B data to L1 in our NISAR environments faster than the 1-3 days, but while reviewing them we realized that without access to lot of NISAR S3 buckets, these workflows don't work out of the box and n...