From 2e2c26d93cb1ee82d7c4e6bb998c1ca8ff5c20c7 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 15:09:58 -0900 Subject: [PATCH 01/29] edits to intro section --- docs/guides/gunw_product_guide.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 56e0fa69..007b043b 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -5,7 +5,9 @@ This document is a guide for users of Sentinel-1 Geocoded Unwrapped (GUNW) Interferometric Synthetic Aperture Radar (InSAR) products. -The ARIA Sentinel-1 Geocoded Unwrapped Phase (ARIA-S1-GUNW) product is a standardized InSAR dataset that enables rapid analysis of surface deformation using Sentinel-1 SAR data. Produced by [JPL’s ARIA](https://aria.jpl.nasa.gov/){target=_blank} project and hosted at the Alaska Satellite Facility (ASF) DAAC, it provides 90-meter resolution, CF-compliant NetCDF files containing unwrapped interferometric phase, imaging geometry, various correction layers, and metadata. With over 1.1 million (and growing!) freely available products covering major fault systems, volcanic regions, and coastal zones, ARIA-S1-GUNW facilitates scientific research and disaster response by simplifying access to centimeter-scale ground displacement measurements. Generated through an open-source, cloud-based [ISCE2 TopsApp processing pipeline](https://github.com/isce-framework/isce2-docs/blob/master/Notebooks/UNAVCO_2020/TOPS/topsApp.ipynb){target=_blank}, these products support applications such as earthquake impact assessment, volcanic monitoring, and long-term land motion studies, with ongoing improvements enhancing their accuracy and usability. +The ARIA Sentinel-1 Geocoded Unwrapped Phase (ARIA-S1-GUNW) product is a standardized InSAR dataset that enables rapid analysis of surface deformation using Sentinel-1 SAR data. Produced by [JPL’s ARIA](https://aria.jpl.nasa.gov/){target=_blank} project and hosted at the [Alaska Satellite Facility (ASF) DAAC](https://www.earthdata.nasa.gov/centers/asf-daac){target=_blank}, it provides 90-meter resolution, CF-compliant NetCDF files containing unwrapped interferometric phase, imaging geometry, various correction layers, and metadata. + +With over 1.1 million (and growing!) freely available products covering major fault systems, volcanic regions, and coastal zones, ARIA-S1-GUNW products facilitate scientific research and disaster response by simplifying access to centimeter-scale ground displacement measurements. Generated through an open-source, cloud-based [ISCE2 TopsApp processing pipeline](https://github.com/isce-framework/isce2-docs/blob/master/Notebooks/UNAVCO_2020/TOPS/topsApp.ipynb){target=_blank}, these products support applications such as earthquake impact assessment, volcanic monitoring, and long-term land motion studies, with ongoing improvements enhancing their accuracy and usability. !!! warning "ARIA-S1-GUNW products are not produced globally" From cf7326304b61526cdb3fa15cfcced3940286bd4b Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 15:12:43 -0900 Subject: [PATCH 02/29] edit to warning block --- docs/guides/gunw_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 007b043b..93cbce82 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -11,7 +11,7 @@ With over 1.1 million (and growing!) freely available products covering major fa !!! warning "ARIA-S1-GUNW products are not produced globally" - ARIA-S1-GUNW products are only produced by the ARIA team for key locations, so the ASF archive may not contain the products you're looking for. See the [Ordering On Demand InSAR Products section](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document") for information on ordering ARIA-S1-GUNW products for your area of interest. + ARIA-S1-GUNW products are only produced by the ARIA team for key locations, so the ASF archive may not contain products in your area of interest. See the [Ordering On Demand InSAR Products section](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document") for information on ordering ARIA-S1-GUNW products for your area of interest. {% endblock %} From 407d13fa923db16297ccd5b09fabd8391b30ab66 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 15:33:34 -0900 Subject: [PATCH 03/29] add link for Earthdata ARIA GUNW page --- docs/guides/gunw_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 93cbce82..cf521687 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -3,7 +3,7 @@ {% block header %} # Sentinel-1 GUNW Product Guide -This document is a guide for users of Sentinel-1 Geocoded Unwrapped (GUNW) Interferometric Synthetic Aperture Radar (InSAR) products. +This document is a guide for users of [Sentinel-1 Geocoded Unwrapped (GUNW)](https://www.earthdata.nasa.gov/data/catalog/asf-aria-s1-gunw-1){target=_blank} Interferometric Synthetic Aperture Radar (InSAR) products. The ARIA Sentinel-1 Geocoded Unwrapped Phase (ARIA-S1-GUNW) product is a standardized InSAR dataset that enables rapid analysis of surface deformation using Sentinel-1 SAR data. Produced by [JPL’s ARIA](https://aria.jpl.nasa.gov/){target=_blank} project and hosted at the [Alaska Satellite Facility (ASF) DAAC](https://www.earthdata.nasa.gov/centers/asf-daac){target=_blank}, it provides 90-meter resolution, CF-compliant NetCDF files containing unwrapped interferometric phase, imaging geometry, various correction layers, and metadata. From 9ad78023f40fb65ed29a3f5e0c24ecb205ccbad9 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 15:35:33 -0900 Subject: [PATCH 04/29] additional edits to warning box --- docs/guides/gunw_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index cf521687..a53a70af 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -11,7 +11,7 @@ With over 1.1 million (and growing!) freely available products covering major fa !!! warning "ARIA-S1-GUNW products are not produced globally" - ARIA-S1-GUNW products are only produced by the ARIA team for key locations, so the ASF archive may not contain products in your area of interest. See the [Ordering On Demand InSAR Products section](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document") for information on ordering ARIA-S1-GUNW products for your area of interest. + ARIA-S1-GUNW products are routinely produced only for specific locations, so the ASF archive may not contain products in your area of interest. See the [Ordering On Demand InSAR Products section](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document") for information on ordering ARIA-S1-GUNW products for your area of interest. {% endblock %} From f67a70292d9ea263f74caa1a556363dbbb9ed0a5 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 15:56:13 -0900 Subject: [PATCH 05/29] edit Vertex warning box --- docs/guides/gunw_product_guide.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index a53a70af..348f36ac 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -33,7 +33,8 @@ You can also use the Vertex SBAS tool to download networks of interferograms for {% block novertex %} !!! warning "On Demand Vertex support not currently available for ARIA-S1-GUNW products" - On-demand ARIA S1 GUNW generation via Vertex is not currently available, but we plan to make this feature available in the second half of 2025. + On-demand ARIA S1 GUNW products cannot currently be submitted directly from Vertex, but we plan to make this feature available in the second half of 2025. Vertex is still very useful for selecting Sentinel-1 SLC pairs to submit for processing, but once you identify scene pairs, you will need to submit them using the HyP3 SDK. + {% endblock %} From 0f1308355e7268e5dabb341fd14694425ae1c9c7 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 16:31:23 -0900 Subject: [PATCH 06/29] add clarification on having both an archive and on-demand --- docs/guides/gunw_product_guide.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 348f36ac..d245da5f 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -13,6 +13,10 @@ With over 1.1 million (and growing!) freely available products covering major fa ARIA-S1-GUNW products are routinely produced only for specific locations, so the ASF archive may not contain products in your area of interest. See the [Ordering On Demand InSAR Products section](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document") for information on ordering ARIA-S1-GUNW products for your area of interest. +While there is a large archive ARIA-S1-GUNW products that have already been generated and are [ready for download](#accessing-existing-products "Jump to Accessing Existing Products section of this document") , they may not cover your area of interest. In addition, they archived products may not include the full range of temporal baseline pairings required for your analysis. If you are interested in ARIA-S1-GUNW products that are not already represented in the archive, ASF provides the ability to [generate these products using specific Sentinel-1 SLC pairings](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document"). + +The On Demand ARIA-S1-GUNW products are generated using the same code that is used to generate the archived products, so they are fully interoperable. + {% endblock %} {% block existingproducts %} From a0cab14af19664931e27bf3b58feb5e611f5e2dc Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 16:32:04 -0900 Subject: [PATCH 07/29] remove extra space --- docs/guides/gunw_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index d245da5f..75454ac9 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -13,7 +13,7 @@ With over 1.1 million (and growing!) freely available products covering major fa ARIA-S1-GUNW products are routinely produced only for specific locations, so the ASF archive may not contain products in your area of interest. See the [Ordering On Demand InSAR Products section](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document") for information on ordering ARIA-S1-GUNW products for your area of interest. -While there is a large archive ARIA-S1-GUNW products that have already been generated and are [ready for download](#accessing-existing-products "Jump to Accessing Existing Products section of this document") , they may not cover your area of interest. In addition, they archived products may not include the full range of temporal baseline pairings required for your analysis. If you are interested in ARIA-S1-GUNW products that are not already represented in the archive, ASF provides the ability to [generate these products using specific Sentinel-1 SLC pairings](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document"). +While there is a large archive ARIA-S1-GUNW products that have already been generated and are [ready for download](#accessing-existing-products "Jump to Accessing Existing Products section of this document"), they may not cover your area of interest. In addition, they archived products may not include the full range of temporal baseline pairings required for your analysis. If you are interested in ARIA-S1-GUNW products that are not already represented in the archive, ASF provides the ability to [generate these products using specific Sentinel-1 SLC pairings](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document"). The On Demand ARIA-S1-GUNW products are generated using the same code that is used to generate the archived products, so they are fully interoperable. From 57a213d65aaeb9725757c9083a1b32c13f33e2a6 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 16:37:14 -0900 Subject: [PATCH 08/29] additional edits to intro --- docs/guides/gunw_product_guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 75454ac9..9e4f3b46 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -11,9 +11,9 @@ With over 1.1 million (and growing!) freely available products covering major fa !!! warning "ARIA-S1-GUNW products are not produced globally" - ARIA-S1-GUNW products are routinely produced only for specific locations, so the ASF archive may not contain products in your area of interest. See the [Ordering On Demand InSAR Products section](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document") for information on ordering ARIA-S1-GUNW products for your area of interest. + ARIA-S1-GUNW products are routinely produced only for specific locations, so the ASF archive may not contain products in your area of interest. See the [Ordering On Demand InSAR Products section](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document") for information on ordering ARIA-S1-GUNW products for specific Sentinel-1 acquisitions. -While there is a large archive ARIA-S1-GUNW products that have already been generated and are [ready for download](#accessing-existing-products "Jump to Accessing Existing Products section of this document"), they may not cover your area of interest. In addition, they archived products may not include the full range of temporal baseline pairings required for your analysis. If you are interested in ARIA-S1-GUNW products that are not already represented in the archive, ASF provides the ability to [generate these products using specific Sentinel-1 SLC pairings](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document"). +While there is a large archive ARIA-S1-GUNW products that have already been generated and are [ready for download](#accessing-existing-products "Jump to Accessing Existing Products section of this document"), they may not cover your area of interest. In addition, the archived products may not include the full range of temporal baseline pairings required for your analysis. If you are interested in ARIA-S1-GUNW products that are not already represented in the archive, ASF provides the ability to [generate these products using specific Sentinel-1 SLC pairings](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document"). The On Demand ARIA-S1-GUNW products are generated using the same code that is used to generate the archived products, so they are fully interoperable. From e9aa98267e9d0975d9861c654c4384c39aa8e66b Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 18:01:03 -0900 Subject: [PATCH 09/29] add missing word --- docs/guides/gunw_product_guide.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 9e4f3b46..08ae5954 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -13,7 +13,9 @@ With over 1.1 million (and growing!) freely available products covering major fa ARIA-S1-GUNW products are routinely produced only for specific locations, so the ASF archive may not contain products in your area of interest. See the [Ordering On Demand InSAR Products section](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document") for information on ordering ARIA-S1-GUNW products for specific Sentinel-1 acquisitions. -While there is a large archive ARIA-S1-GUNW products that have already been generated and are [ready for download](#accessing-existing-products "Jump to Accessing Existing Products section of this document"), they may not cover your area of interest. In addition, the archived products may not include the full range of temporal baseline pairings required for your analysis. If you are interested in ARIA-S1-GUNW products that are not already represented in the archive, ASF provides the ability to [generate these products using specific Sentinel-1 SLC pairings](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document"). +## Archived and On-Demand Products + +While there is a large archive of ARIA-S1-GUNW products that have already been generated and are [ready for download](#accessing-existing-products "Jump to Accessing Existing Products section of this document"), they may not cover your area of interest. In addition, the archived products may not include the full range of temporal baseline pairings required for your analysis. If you are interested in ARIA-S1-GUNW products that are not already represented in the archive, ASF provides the ability to [generate these products using specific Sentinel-1 SLC pairings](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document"). The On Demand ARIA-S1-GUNW products are generated using the same code that is used to generate the archived products, so they are fully interoperable. From 4d61c5d917674780840f7a141a323207c9d73445 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 18:01:38 -0900 Subject: [PATCH 10/29] remove template references --- docs/guides/gunw_product_guide.md | 65 ++++++++++++++++--------------- 1 file changed, 34 insertions(+), 31 deletions(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 08ae5954..c1227400 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -1,6 +1,3 @@ -{% extends "guides/insar_product_guide_template.md" %} - -{% block header %} # Sentinel-1 GUNW Product Guide This document is a guide for users of [Sentinel-1 Geocoded Unwrapped (GUNW)](https://www.earthdata.nasa.gov/data/catalog/asf-aria-s1-gunw-1){target=_blank} Interferometric Synthetic Aperture Radar (InSAR) products. @@ -19,10 +16,7 @@ While there is a large archive of ARIA-S1-GUNW products that have already been g The On Demand ARIA-S1-GUNW products are generated using the same code that is used to generate the archived products, so they are fully interoperable. -{% endblock %} - -{% block existingproducts %} -### Accessing Existing Products +## Accessing Existing Products You can download existing ARIA-S1-GUNW products from the Alaska Satellite Facility’s (ASF) [Vertex](https://search.asf.alaska.edu/#/?dataset=SENTINEL-1%20INTERFEROGRAM%20(BETA)){target=_blank} search portal by following these steps: @@ -32,40 +26,54 @@ You can download existing ARIA-S1-GUNW products from the Alaska Satellite Facili 3. **Preview and Select Products** – Click on individual results to view metadata, including coverage area and acquisition details. 4. **Download Data** – To download, first add ARIA-S1-GUNW products to your download queue using the shopping cart icon next to each product, then download your selected products using the “download” panel. -You can also use the Vertex SBAS tool to download networks of interferograms for a specific location. See [this guide](https://docs.asf.alaska.edu/vertex/sbas/){target=_blank} for more information. +## Ordering On-Demand Products -{% endblock %} +If the ARIA-S1-GUNW products you need are not available in the archive, you can use ASF's On Demand platform to submit custom ARIA-S1-GUNW jobs for processing. -{% block novertex %} -!!! warning "On Demand Vertex support not currently available for ARIA-S1-GUNW products" +### ARIA Frame IDs - On-demand ARIA S1 GUNW products cannot currently be submitted directly from Vertex, but we plan to make this feature available in the second half of 2025. Vertex is still very useful for selecting Sentinel-1 SLC pairs to submit for processing, but once you identify scene pairs, you will need to submit them using the HyP3 SDK. +Sentinel-1 IW SLC products are not created in a way that ensures that granules for the same relative orbit and location always fully overlap over time. This results in a frame “jitter” that can make it difficult to create longer series of Sentinel-1 InSAR products. -{% endblock %} +#TODO: add an illustration of non-overlapping SLC footprints +To address this issue, the ARIA team defined a standard set of geographic footprints, called frames, that set the geographic extent for each ARIA-S1-GUNW product. This is possible because while the Sentinel-1 IW SLC products exhibit jitter along the orbit, the smaller burst SLCs that comprise each Sentinel-1 IW SLC product *do* have a consistent footprint. Thus, ARIA-S1-GUNW frames are defined via the specific bursts that each ARIA-S1-GUNW product contains. **ARIA-S1-GUNWs containing the same bursts, and thus sharing the same geographic footprint, are said to have the same ARIA Frame ID.** -{% block framingtip %} -!!! tip "Be aware of the frame interface when requesting ARIA-S1-GUNW products" +To ensure that ARIA-S1-GUNW products are always created using standard footprints, the ARIA Frame ID needs to be provided along with the reference and secondary granules that intersect this footprint for a given date in order to create a new ARIA-S1-GUNW product (see figure below). - To address the "jittering" of Sentinel-1 SLCs granules, ARIA-S1-GUNW products take an extra frame-id parameter that standardizes the footprint of ARIA-S1-GUNW products. See the [ARIA Frame IDs](#aria-frame-ids "Jump to ARIA Frame IDs section of this document") for more information on submitting ARIA-S1-GUNW jobs -{% endblock %} +![Frame vs granule geographic footprint](../images/frame_granule_overlap.png "Example of a frame that spans three granules.") +#### Aria Frame ID Maps -{% block framing %} -### ARIA Frame IDs -Sentinel-1 SLC products are not created in a way that ensures that granules for the same relative orbit and location but different dates always fully overlap. This results in a frame “jitter” that can make it difficult to create longer series of Sentinel-1 InSAR products. +It can be tricky to find all of the appropriate granules for a given ARIA Frame ID for both the primary and secondary acquisition dates. In the future, ASF plans to create utilities to simplify this process. In the meantime, there are geojson files indicating the extent of each ARIA Frame ID that can be downloaded and used for reference. -To address this issue, the ARIA team defined a standard set of geographic footprints (i.e., frames) that set the geographic extent for each ARIA-S1-GUNW product. This is possible because while the Sentinel-1 SLC products exhibit jitter along the orbit, the smaller burst SLCs that each Sentinel-1 SLC product is composed of do have a fixed footprint (e.g., the bursts contained within a given Sentinel-1 SLC product changes based on the acquisition). Thus ARIA-S1-GUNW frames are defined via the specific bursts that each ARIA-S1-GUNW product contains. **ARIA-S1-GUNWs containing the same bursts, and thus sharing the same geographic footprint, are said to have the same ARIA Frame ID.** +There are different ARIA Frame ID maps for the ascending and descending orbit directions. Make sure that you are using the appropriate geojson file. -To ensure that ARIA-S1-GUNW products are always created using the standard footprints, the ARIA Frame ID along with the reference and secondary granules that intersect this footprint for a given date need to be provided in order to create a new ARIA-S1-GUNW product (see figure below). +- [Ascending ARIA Frame IDs](https://d3g9emy65n853h.cloudfront.net/ARIA_S1_GUNW/ascending.geojson){target=_blank} +- [Descending ARIA Frame IDs](https://d3g9emy65n853h.cloudfront.net/ARIA_S1_GUNW/descending.geojson){target=_blank}. -![Frame vs granule geographic footprint](../images/frame_granule_overlap.png "Example of a frame that spans three granules.") +### Search for Sentinel-1 SLCs for an ARIA Frame ID + +1. Search for Sentinel-1 SLC IW products in your area of interest in [Vertex](https://search.asf.alaska.edu/#/){target=_blank} using a Geographic Search and setting the Area of Interest to the desired ARIA Frame ID, as delineated in the [ARIA Frame ID maps](#aria-frame-id-maps). You may want to apply a search filter for the orbit direction that matches the ARIA Frame ID extent that you are using. -It can be tricky to find the appropriate granules for a given ARIA Frame ID, and in the future, we plan to create utilities to simplify this process. For the meantime, a geojson detailing the *ascending* ARIA Frame IDs can be downloaded [here](https://d3g9emy65n853h.cloudfront.net/ARIA_S1_GUNW/ascending.geojson){target=_blank} and a geojson detailing the *descending* ARIA Frame IDs can be downloaded [here](https://d3g9emy65n853h.cloudfront.net/ARIA_S1_GUNW/descending.geojson){target=_blank}. +2. For each footprint that intersects the ARIA Frame ID, use the [SBAS](https://docs.asf.alaska.edu/vertex/sbas/){target=_blank} or [Baseline](https://docs.asf.alaska.edu/vertex/baseline/){target=_blank} tool in Vertex to find other acquisitions to pair with the reference acquisition. -{% endblock %} + - You will need to repeat the process of finding pairs for each footprint that intersects the ARIA Frame ID extent + +3. Create a list of the primary and secondary Sentinel-1 IW SLCs that intersect with the ARIA Frame ID extent. + + Example: + ``` + #TODO: Example ist of input granules [primary1, primary2, primary3] [second1, second2, second3] + ``` + +### Submit On-Demand ARIA-S1-GUNW Jobs + +!!! warning "On Demand support not currently available in Vertex for ARIA-S1-GUNW products" + + On-demand ARIA S1 GUNW products cannot currently be submitted directly from Vertex, but we plan to make this feature available in the second half of 2025. Vertex is still very useful for selecting Sentinel-1 SLC pairs to submit for processing, but once you identify scene pairs, you will need to submit them using the [HyP3 Python SDK](../using/sdk.md){target=_blank} or [HyP3 API](../using/api.md){target=_blank}. + +#TODO: outline use of SDK and API for submitting jobs. -{% block packaging %} ## Product Packaging ### Naming convention @@ -127,10 +135,6 @@ Tropospheric delay correction is essential for many InSAR applications because a RAiDER uses the [NOAA High-Resolution Rapid Refresh](https://rapidrefresh.noaa.gov/hrrr/){target=blank} weather model to calculate the tropospheric delay correction at a spatial resolution of approximately 3 km. If the HRRR weather model is not available for a location of interest, (e.g. outside of the continental U.S. and Alaska) the tropospheric delay correction layer will not be included in the ARIA-S1-GUNW product. The wet and hydrostatic tropospheric delay correction are provided for both the reference and secondary input data. -{% endblock %} - -{% block references%} - ### References Bekaert, David, et al. "The ARIA-S1-GUNW: The ARIA Sentinel-1 Geocoded Unwrapped Phase Product for Open InSAR Science and Disaster Response." IGARSS 2023-2023 IEEE International Geoscience and Remote Sensing Symposium. IEEE, 2023\. @@ -138,4 +142,3 @@ Liang, Cunren, et al. "Ionospheric correction of InSAR time series analysis of C Yunjun, Zhang, et al. "Range geolocation accuracy of C-/L-band SAR and its implications for operational stack coregistration." IEEE Transactions on Geoscience and Remote Sensing 60 (2022): 1-19. -{% endblock %} From 80495c3109c54faa2972beae0088f7d54e5c0ac4 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 18:08:20 -0900 Subject: [PATCH 11/29] remove extra period --- docs/guides/gunw_product_guide.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index c1227400..963de072 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -32,11 +32,11 @@ If the ARIA-S1-GUNW products you need are not available in the archive, you can ### ARIA Frame IDs -Sentinel-1 IW SLC products are not created in a way that ensures that granules for the same relative orbit and location always fully overlap over time. This results in a frame “jitter” that can make it difficult to create longer series of Sentinel-1 InSAR products. +Sentinel-1 IW SLC products are not created in a way that ensures that granules for the same relative orbit and location always fully overlap over time. This results in inconsistent framing of the Sentinel-1 IW SLCs that can make it difficult to create longer series of Sentinel-1 InSAR products. -#TODO: add an illustration of non-overlapping SLC footprints + ##TODO: add an illustration of non-overlapping SLC footprints -To address this issue, the ARIA team defined a standard set of geographic footprints, called frames, that set the geographic extent for each ARIA-S1-GUNW product. This is possible because while the Sentinel-1 IW SLC products exhibit jitter along the orbit, the smaller burst SLCs that comprise each Sentinel-1 IW SLC product *do* have a consistent footprint. Thus, ARIA-S1-GUNW frames are defined via the specific bursts that each ARIA-S1-GUNW product contains. **ARIA-S1-GUNWs containing the same bursts, and thus sharing the same geographic footprint, are said to have the same ARIA Frame ID.** +To address this issue, the ARIA team defined a standard set of geographic footprints, called frames, that set the geographic extent for each ARIA-S1-GUNW product. This is possible because while the Sentinel-1 IW SLC products are not consistently framed along the orbit path, the smaller burst SLCs that comprise each Sentinel-1 IW SLC product *do* have consistent footprints. Thus, ARIA-S1-GUNW frames are defined via the specific bursts that each ARIA-S1-GUNW product contains. **ARIA-S1-GUNWs containing the same bursts, and thus sharing the same geographic footprint, are said to have the same ARIA Frame ID.** To ensure that ARIA-S1-GUNW products are always created using standard footprints, the ARIA Frame ID needs to be provided along with the reference and secondary granules that intersect this footprint for a given date in order to create a new ARIA-S1-GUNW product (see figure below). @@ -49,7 +49,7 @@ It can be tricky to find all of the appropriate granules for a given ARIA Frame There are different ARIA Frame ID maps for the ascending and descending orbit directions. Make sure that you are using the appropriate geojson file. - [Ascending ARIA Frame IDs](https://d3g9emy65n853h.cloudfront.net/ARIA_S1_GUNW/ascending.geojson){target=_blank} -- [Descending ARIA Frame IDs](https://d3g9emy65n853h.cloudfront.net/ARIA_S1_GUNW/descending.geojson){target=_blank}. +- [Descending ARIA Frame IDs](https://d3g9emy65n853h.cloudfront.net/ARIA_S1_GUNW/descending.geojson){target=_blank} ### Search for Sentinel-1 SLCs for an ARIA Frame ID From a07cd8470ff00a0a8e8fbd92b0c502d19c0b29a5 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 18:09:31 -0900 Subject: [PATCH 12/29] add missing letters --- docs/guides/gunw_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 963de072..4db1bfef 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -63,7 +63,7 @@ There are different ARIA Frame ID maps for the ascending and descending orbit di Example: ``` - #TODO: Example ist of input granules [primary1, primary2, primary3] [second1, second2, second3] + ##TODO: Example list of input granules [primary1, primary2, primary3] [second1, second2, second3] ``` ### Submit On-Demand ARIA-S1-GUNW Jobs From 1be2fb5a5d806a31694caf659b07879f084063ef Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 18:10:18 -0900 Subject: [PATCH 13/29] adjust comment --- docs/guides/gunw_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 4db1bfef..3fa8453a 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -72,7 +72,7 @@ There are different ARIA Frame ID maps for the ascending and descending orbit di On-demand ARIA S1 GUNW products cannot currently be submitted directly from Vertex, but we plan to make this feature available in the second half of 2025. Vertex is still very useful for selecting Sentinel-1 SLC pairs to submit for processing, but once you identify scene pairs, you will need to submit them using the [HyP3 Python SDK](../using/sdk.md){target=_blank} or [HyP3 API](../using/api.md){target=_blank}. -#TODO: outline use of SDK and API for submitting jobs. + ##TODO: outline use of SDK and API for submitting jobs. ## Product Packaging From 97de7396b31bf2edb96c4c90e089ebc5d99c6823 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 18:25:27 -0900 Subject: [PATCH 14/29] add ARIA to product guide name and intro section --- docs/guides/gunw_product_guide.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 3fa8453a..9c704beb 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -1,8 +1,8 @@ -# Sentinel-1 GUNW Product Guide +# ARIA Sentinel-1 GUNW Product Guide -This document is a guide for users of [Sentinel-1 Geocoded Unwrapped (GUNW)](https://www.earthdata.nasa.gov/data/catalog/asf-aria-s1-gunw-1){target=_blank} Interferometric Synthetic Aperture Radar (InSAR) products. +This document is a guide for users of [ARIA Sentinel-1 Geocoded Unwrapped (GUNW) Interferograms](https://www.earthdata.nasa.gov/data/catalog/asf-aria-s1-gunw-1){target=_blank}. -The ARIA Sentinel-1 Geocoded Unwrapped Phase (ARIA-S1-GUNW) product is a standardized InSAR dataset that enables rapid analysis of surface deformation using Sentinel-1 SAR data. Produced by [JPL’s ARIA](https://aria.jpl.nasa.gov/){target=_blank} project and hosted at the [Alaska Satellite Facility (ASF) DAAC](https://www.earthdata.nasa.gov/centers/asf-daac){target=_blank}, it provides 90-meter resolution, CF-compliant NetCDF files containing unwrapped interferometric phase, imaging geometry, various correction layers, and metadata. +The ARIA Sentinel-1 Geocoded Unwrapped Phase (ARIA-S1-GUNW) product is a standardized interferometric SAR (InSAR) dataset that enables rapid analysis of surface deformation using Sentinel-1 SAR data. Produced by [JPL’s ARIA](https://aria.jpl.nasa.gov/){target=_blank} project and hosted at the [Alaska Satellite Facility (ASF) DAAC](https://www.earthdata.nasa.gov/centers/asf-daac){target=_blank}, it provides CF-compliant NetCDF files at 90-m pixel spacing, containing unwrapped interferometric phase measurements, imaging geometry, various correction layers, and metadata. With over 1.1 million (and growing!) freely available products covering major fault systems, volcanic regions, and coastal zones, ARIA-S1-GUNW products facilitate scientific research and disaster response by simplifying access to centimeter-scale ground displacement measurements. Generated through an open-source, cloud-based [ISCE2 TopsApp processing pipeline](https://github.com/isce-framework/isce2-docs/blob/master/Notebooks/UNAVCO_2020/TOPS/topsApp.ipynb){target=_blank}, these products support applications such as earthquake impact assessment, volcanic monitoring, and long-term land motion studies, with ongoing improvements enhancing their accuracy and usability. From 1206f2037bc6188ea1c8d6fc81677a396e873d75 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 3 Mar 2025 18:28:54 -0900 Subject: [PATCH 15/29] capitalize ARIA --- docs/guides/gunw_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 9c704beb..7c1c0e4f 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -42,7 +42,7 @@ To ensure that ARIA-S1-GUNW products are always created using standard footprint ![Frame vs granule geographic footprint](../images/frame_granule_overlap.png "Example of a frame that spans three granules.") -#### Aria Frame ID Maps +#### ARIA Frame ID Maps It can be tricky to find all of the appropriate granules for a given ARIA Frame ID for both the primary and secondary acquisition dates. In the future, ASF plans to create utilities to simplify this process. In the meantime, there are geojson files indicating the extent of each ARIA Frame ID that can be downloaded and used for reference. From c5e1665f4df49b01b74ac9c9405cdd0e1a6f8261 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Tue, 4 Mar 2025 11:43:17 -0900 Subject: [PATCH 16/29] add conditional statements and sample list to search section --- docs/guides/gunw_product_guide.md | 37 +++++++++++++++++++++++++++---- 1 file changed, 33 insertions(+), 4 deletions(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 7c1c0e4f..be22dd69 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -53,17 +53,46 @@ There are different ARIA Frame ID maps for the ascending and descending orbit di ### Search for Sentinel-1 SLCs for an ARIA Frame ID -1. Search for Sentinel-1 SLC IW products in your area of interest in [Vertex](https://search.asf.alaska.edu/#/){target=_blank} using a Geographic Search and setting the Area of Interest to the desired ARIA Frame ID, as delineated in the [ARIA Frame ID maps](#aria-frame-id-maps). You may want to apply a search filter for the orbit direction that matches the ARIA Frame ID extent that you are using. +Use a [Geographic Search]() for Sentinel-1 SLC IW products in your area of interest in [Vertex](https://search.asf.alaska.edu/#/){target=_blank}, setting the Area of Interest to the desired ARIA Frame ID, as delineated in the [ARIA Frame ID maps](#aria-frame-id-maps). You may want to apply a search filter for the orbit direction that matches the ARIA Frame ID extent that you are using. -2. For each footprint that intersects the ARIA Frame ID, use the [SBAS](https://docs.asf.alaska.edu/vertex/sbas/){target=_blank} or [Baseline](https://docs.asf.alaska.edu/vertex/baseline/){target=_blank} tool in Vertex to find other acquisitions to pair with the reference acquisition. +For each footprint that intersects the ARIA Frame ID, use the [SBAS](https://docs.asf.alaska.edu/vertex/sbas/){target=_blank} or [Baseline](https://docs.asf.alaska.edu/vertex/baseline/){target=_blank} tool in Vertex to find other acquisitions to pair with the reference acquisition. - You will need to repeat the process of finding pairs for each footprint that intersects the ARIA Frame ID extent -3. Create a list of the primary and secondary Sentinel-1 IW SLCs that intersect with the ARIA Frame ID extent. +There are a number of conditions that must be met when selecting suitable sets of Sentinel-1 IW SLCs for processing to ARIA-S1-GUNW: + + - All scenes (reference and secondary) must be from the same relative orbit + - they must all have the same path number + - the ARIA frames are all constrained to a single path + - All scenes must have the same orbit direction (ascending/descending) + - the orbit direction must match the orbit direction of the ARIA Frame ID you are using + - All reference scenes must be from the absolute orbit + - they must all be from the same pass of the satellite + - acquisitions from different dates cannot be combined + - All secondary scenes must be from the same absolute orbit + - they must all be from the same pass of the satellite + - acquisitions from different dates cannot be combined + - Reference scenes must be acquired after the secondary scenes + - the list of reference scenes are from the most recent pass, and the secondary scenes are from the earlier pass that will be compared to the reference scenes + - Reference and secondary scenes should overlap the frame geometry + - all of the scenes listed must overlap the ARIA Frame ID extent + - do not include any acquisitions where valid pixel data is wholly outside the extent of the ARIA frame, even if the no-data padding around the edges overlaps the frame extent + + +Create a list of the reference and secondary Sentinel-1 IW SLCs that intersect with the ARIA Frame ID extent. Example: ``` - ##TODO: Example list of input granules [primary1, primary2, primary3] [second1, second2, second3] + "reference": [ + "S1A_IW_SLC__1SDV_20250127T010136_20250127T010203_057623_07199D_4B63", + "S1A_IW_SLC__1SDV_20250127T010111_20250127T010138_057623_07199D_4E88", + "S1A_IW_SLC__1SDV_20250127T010045_20250127T010113_057623_07199D_4D3B" + ], + "secondary": [ + "S1A_IW_SLC__1SDV_20250103T010137_20250103T010204_057273_070BB6_CD45", + "S1A_IW_SLC__1SDV_20250103T010113_20250103T010140_057273_070BB6_1133", + "S1A_IW_SLC__1SDV_20250103T010047_20250103T010115_057273_070BB6_99C5" + ], ``` ### Submit On-Demand ARIA-S1-GUNW Jobs From ae6e25f0827312118423daec2373cefd944ba0bf Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Tue, 4 Mar 2025 11:51:15 -0900 Subject: [PATCH 17/29] add link to geographic search guidance --- docs/guides/gunw_product_guide.md | 25 +++++++++++++------------ 1 file changed, 13 insertions(+), 12 deletions(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index be22dd69..0eb265da 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -53,33 +53,34 @@ There are different ARIA Frame ID maps for the ascending and descending orbit di ### Search for Sentinel-1 SLCs for an ARIA Frame ID -Use a [Geographic Search]() for Sentinel-1 SLC IW products in your area of interest in [Vertex](https://search.asf.alaska.edu/#/){target=_blank}, setting the Area of Interest to the desired ARIA Frame ID, as delineated in the [ARIA Frame ID maps](#aria-frame-id-maps). You may want to apply a search filter for the orbit direction that matches the ARIA Frame ID extent that you are using. +Use a [Geographic Search](https://docs.asf.alaska.edu/vertex/manual/#geographic-search-options){target=_blank} for Sentinel-1 SLC IW products in your area of interest in [Vertex](https://search.asf.alaska.edu/#/){target=_blank}, setting the Area of Interest to the desired ARIA Frame ID, as delineated in the [ARIA Frame ID maps](#aria-frame-id-maps). You may want to apply a search filter for the orbit direction that matches the ARIA Frame ID extent that you are using. For each footprint that intersects the ARIA Frame ID, use the [SBAS](https://docs.asf.alaska.edu/vertex/sbas/){target=_blank} or [Baseline](https://docs.asf.alaska.edu/vertex/baseline/){target=_blank} tool in Vertex to find other acquisitions to pair with the reference acquisition. - - You will need to repeat the process of finding pairs for each footprint that intersects the ARIA Frame ID extent + - You will need to repeat the process of finding pairs for each footprint that intersects the ARIA Frame ID extent. There are a number of conditions that must be met when selecting suitable sets of Sentinel-1 IW SLCs for processing to ARIA-S1-GUNW: - - All scenes (reference and secondary) must be from the same relative orbit - - they must all have the same path number - - the ARIA frames are all constrained to a single path - - All scenes must have the same orbit direction (ascending/descending) + 1. All scenes (reference and secondary) must be from the same relative orbit + - they must all have the same path number, which matches the extent of the desired ARIA Frame ID + - note that the ARIA frames are all constrained to a single path + - consider adding a filter to your search to limit the returns to acquisitions with the same path number as the ARIA Frame ID + 2. All scenes must have the same orbit direction (ascending/descending) - the orbit direction must match the orbit direction of the ARIA Frame ID you are using - - All reference scenes must be from the absolute orbit + - consider adding a filter to your search to limit the returns to acquisitions with the same orbit direction as the ARIA Frame ID + 3. All reference scenes must be from the same absolute orbit - they must all be from the same pass of the satellite - acquisitions from different dates cannot be combined - - All secondary scenes must be from the same absolute orbit + 4. All secondary scenes must be from the same absolute orbit - they must all be from the same pass of the satellite - acquisitions from different dates cannot be combined - - Reference scenes must be acquired after the secondary scenes + 5. Reference scenes must be acquired after the secondary scenes - the list of reference scenes are from the most recent pass, and the secondary scenes are from the earlier pass that will be compared to the reference scenes - - Reference and secondary scenes should overlap the frame geometry + 6. Reference and secondary scenes should overlap the frame geometry - all of the scenes listed must overlap the ARIA Frame ID extent - do not include any acquisitions where valid pixel data is wholly outside the extent of the ARIA frame, even if the no-data padding around the edges overlaps the frame extent - -Create a list of the reference and secondary Sentinel-1 IW SLCs that intersect with the ARIA Frame ID extent. +Based on your search results, create a list of the reference and secondary Sentinel-1 IW SLCs that intersect with the ARIA Frame ID extent. Example: ``` From 4e2ceaa7cc0f004f0e6dba5bedd509c383ff2122 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Tue, 4 Mar 2025 11:52:53 -0900 Subject: [PATCH 18/29] edit formatting --- docs/guides/gunw_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 0eb265da..522602fb 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -57,7 +57,7 @@ Use a [Geographic Search](https://docs.asf.alaska.edu/vertex/manual/#geographic- For each footprint that intersects the ARIA Frame ID, use the [SBAS](https://docs.asf.alaska.edu/vertex/sbas/){target=_blank} or [Baseline](https://docs.asf.alaska.edu/vertex/baseline/){target=_blank} tool in Vertex to find other acquisitions to pair with the reference acquisition. - - You will need to repeat the process of finding pairs for each footprint that intersects the ARIA Frame ID extent. + - You will need to repeat the process of finding pairs for each footprint that intersects the ARIA Frame ID extent. There are a number of conditions that must be met when selecting suitable sets of Sentinel-1 IW SLCs for processing to ARIA-S1-GUNW: From 8299cb534ac51f2474c28ea58e8f1e937ba5e3fe Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Tue, 4 Mar 2025 11:53:32 -0900 Subject: [PATCH 19/29] edits --- docs/guides/gunw_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 522602fb..5d1affe7 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -57,7 +57,7 @@ Use a [Geographic Search](https://docs.asf.alaska.edu/vertex/manual/#geographic- For each footprint that intersects the ARIA Frame ID, use the [SBAS](https://docs.asf.alaska.edu/vertex/sbas/){target=_blank} or [Baseline](https://docs.asf.alaska.edu/vertex/baseline/){target=_blank} tool in Vertex to find other acquisitions to pair with the reference acquisition. - - You will need to repeat the process of finding pairs for each footprint that intersects the ARIA Frame ID extent. + - You will need to repeat the process of finding pairs for each footprint along the Sentinel-1 orbit path that intersects the ARIA Frame ID extent. There are a number of conditions that must be met when selecting suitable sets of Sentinel-1 IW SLCs for processing to ARIA-S1-GUNW: From a637d851cd548a190b3cc06c0b8c64037ab9c3ce Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Tue, 4 Mar 2025 11:54:37 -0900 Subject: [PATCH 20/29] add subheading for SLC selection constraints --- docs/guides/gunw_product_guide.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 5d1affe7..e7ba109e 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -59,6 +59,8 @@ For each footprint that intersects the ARIA Frame ID, use the [SBAS](https://doc - You will need to repeat the process of finding pairs for each footprint along the Sentinel-1 orbit path that intersects the ARIA Frame ID extent. +#### Sentinel-1 SLC Selection Constraints + There are a number of conditions that must be met when selecting suitable sets of Sentinel-1 IW SLCs for processing to ARIA-S1-GUNW: 1. All scenes (reference and secondary) must be from the same relative orbit From 57ad7abecfb5264552633b351f9a84faa245550a Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Tue, 4 Mar 2025 12:03:16 -0900 Subject: [PATCH 21/29] update formatting --- docs/guides/gunw_product_guide.md | 57 +++++++++++++++++++------------ 1 file changed, 35 insertions(+), 22 deletions(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index e7ba109e..598ca5d1 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -63,39 +63,52 @@ For each footprint that intersects the ARIA Frame ID, use the [SBAS](https://doc There are a number of conditions that must be met when selecting suitable sets of Sentinel-1 IW SLCs for processing to ARIA-S1-GUNW: - 1. All scenes (reference and secondary) must be from the same relative orbit - - they must all have the same path number, which matches the extent of the desired ARIA Frame ID - - note that the ARIA frames are all constrained to a single path - - consider adding a filter to your search to limit the returns to acquisitions with the same path number as the ARIA Frame ID - 2. All scenes must have the same orbit direction (ascending/descending) - - the orbit direction must match the orbit direction of the ARIA Frame ID you are using - - consider adding a filter to your search to limit the returns to acquisitions with the same orbit direction as the ARIA Frame ID - 3. All reference scenes must be from the same absolute orbit - - they must all be from the same pass of the satellite - - acquisitions from different dates cannot be combined - 4. All secondary scenes must be from the same absolute orbit - - they must all be from the same pass of the satellite - - acquisitions from different dates cannot be combined - 5. Reference scenes must be acquired after the secondary scenes - - the list of reference scenes are from the most recent pass, and the secondary scenes are from the earlier pass that will be compared to the reference scenes - 6. Reference and secondary scenes should overlap the frame geometry - - all of the scenes listed must overlap the ARIA Frame ID extent - - do not include any acquisitions where valid pixel data is wholly outside the extent of the ARIA frame, even if the no-data padding around the edges overlaps the frame extent + ***1. All scenes (reference and secondary) must be from the same relative orbit*** + + - they must all have the same path number, which matches the path of the extent of the desired ARIA Frame ID + - note that the ARIA frames are each constrained to a single path + - consider adding a filter to your geographic search to limit the returns to acquisitions with the same path number as the ARIA Frame ID + + ***2. All scenes must have the same orbit direction (ascending/descending)*** + + - the orbit direction must match the orbit direction of the ARIA Frame ID you are using + - consider adding a filter to your geographic search to limit the returns to acquisitions with the same orbit direction as the ARIA Frame ID + + ***3. All reference scenes must be from the same absolute orbit*** + + - they must all be from the same pass of the satellite + - acquisitions from different dates cannot be combined + + ***4. All secondary scenes must be from the same absolute orbit*** + + - they must all be from the same pass of the satellite + - acquisitions from different dates cannot be combined + + ***5. Reference scenes must be acquired after the secondary scenes*** + + - the list of reference scenes are from the most recent pass, and the secondary scenes are from the earlier pass that will be compared to the reference scenes + + ***6. Reference and secondary scenes should overlap the frame geometry*** + + - all of the scenes listed must overlap the ARIA Frame ID extent + - do not include any acquisitions where valid pixel data is wholly outside the extent of the ARIA frame, even if the no-data padding around the edges overlaps the frame extent + +#### Compile a List of Sentinel-1 SLCs Based on your search results, create a list of the reference and secondary Sentinel-1 IW SLCs that intersect with the ARIA Frame ID extent. Example: ``` - "reference": [ + "reference": [ "S1A_IW_SLC__1SDV_20250127T010136_20250127T010203_057623_07199D_4B63", "S1A_IW_SLC__1SDV_20250127T010111_20250127T010138_057623_07199D_4E88", "S1A_IW_SLC__1SDV_20250127T010045_20250127T010113_057623_07199D_4D3B" - ], - "secondary": [ + ], + "secondary": [ "S1A_IW_SLC__1SDV_20250103T010137_20250103T010204_057273_070BB6_CD45", "S1A_IW_SLC__1SDV_20250103T010113_20250103T010140_057273_070BB6_1133", "S1A_IW_SLC__1SDV_20250103T010047_20250103T010115_057273_070BB6_99C5" - ], + ], ``` ### Submit On-Demand ARIA-S1-GUNW Jobs From 4a4dcd87864275ac45989e406044f7cef8a7270d Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Tue, 4 Mar 2025 12:09:57 -0900 Subject: [PATCH 22/29] add illustrating of shifting S1 footprints --- docs/guides/gunw_product_guide.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 598ca5d1..c14732a9 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -34,7 +34,9 @@ If the ARIA-S1-GUNW products you need are not available in the archive, you can Sentinel-1 IW SLC products are not created in a way that ensures that granules for the same relative orbit and location always fully overlap over time. This results in inconsistent framing of the Sentinel-1 IW SLCs that can make it difficult to create longer series of Sentinel-1 InSAR products. - ##TODO: add an illustration of non-overlapping SLC footprints +In the image below, Sentinel-1 footprints acquired over an area of interest are displayed. Over the full period of record of the mission, the SLC framing has shifted considerably, resulting in some acquisitions that hardly overlap at all. + +![Shifting of Sentinel-1 SLC frames over time](../images/slc_jitter.png "Illustration of the shifting extent of Sentinel-1 SLC footprints over time.") To address this issue, the ARIA team defined a standard set of geographic footprints, called frames, that set the geographic extent for each ARIA-S1-GUNW product. This is possible because while the Sentinel-1 IW SLC products are not consistently framed along the orbit path, the smaller burst SLCs that comprise each Sentinel-1 IW SLC product *do* have consistent footprints. Thus, ARIA-S1-GUNW frames are defined via the specific bursts that each ARIA-S1-GUNW product contains. **ARIA-S1-GUNWs containing the same bursts, and thus sharing the same geographic footprint, are said to have the same ARIA Frame ID.** From 2afa2ee71720f6de1316ffe6ddf116fb09e59896 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Tue, 4 Mar 2025 12:13:21 -0900 Subject: [PATCH 23/29] correct formatting of example code block --- docs/guides/gunw_product_guide.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index c14732a9..6a127a84 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -99,8 +99,8 @@ There are a number of conditions that must be met when selecting suitable sets o Based on your search results, create a list of the reference and secondary Sentinel-1 IW SLCs that intersect with the ARIA Frame ID extent. - Example: - ``` + Example: + "reference": [ "S1A_IW_SLC__1SDV_20250127T010136_20250127T010203_057623_07199D_4B63", "S1A_IW_SLC__1SDV_20250127T010111_20250127T010138_057623_07199D_4E88", @@ -111,7 +111,6 @@ Based on your search results, create a list of the reference and secondary Senti "S1A_IW_SLC__1SDV_20250103T010113_20250103T010140_057273_070BB6_1133", "S1A_IW_SLC__1SDV_20250103T010047_20250103T010115_057273_070BB6_99C5" ], - ``` ### Submit On-Demand ARIA-S1-GUNW Jobs From ae78ce379807df6c8db21d106a2b7de74e9a62ec Mon Sep 17 00:00:00 2001 From: Forrest Williams Date: Tue, 4 Mar 2025 15:24:43 -0600 Subject: [PATCH 24/29] add sdk, api info --- docs/guides/gunw_product_guide.md | 4 +++- docs/using/api.md | 22 ++++++++++++++++++++++ 2 files changed, 25 insertions(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 7c1c0e4f..c2459c1f 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -72,7 +72,9 @@ There are different ARIA Frame ID maps for the ascending and descending orbit di On-demand ARIA S1 GUNW products cannot currently be submitted directly from Vertex, but we plan to make this feature available in the second half of 2025. Vertex is still very useful for selecting Sentinel-1 SLC pairs to submit for processing, but once you identify scene pairs, you will need to submit them using the [HyP3 Python SDK](../using/sdk.md){target=_blank} or [HyP3 API](../using/api.md){target=_blank}. - ##TODO: outline use of SDK and API for submitting jobs. +On-Demand ARIA-S1-GUNW jobs can be submitted via the `ARIA_S1_GUNW` job type via the [HyP3 API](/using/api/#submitting-aria-s1-gunw-jobs){target=_blank}, or via the [HyP3 Python SDK](../using/sdk.md){target=_blank} using the `submit_aria_s1_gunw_job` method of the `HyP3` class. + +Unlink our other On-Demand InSAR workflows, customizable processing options (e.g., multilook, filter strength, etc.) are not available for ARIA-S1-GUNW jobs. ## Product Packaging diff --git a/docs/using/api.md b/docs/using/api.md index b14e72fa..feabf7bb 100644 --- a/docs/using/api.md +++ b/docs/using/api.md @@ -131,6 +131,28 @@ You can also submit InSAR jobs for scene pairs using [ESA granule IDs](https://s } ``` +## Submitting ARIA-S1-GUNW jobs +The ARIA-S1-GUNW job type takes a reference [ESA granule IDs](https://sentinel.esa.int/web/sentinel/user-guides/sentinel-1-sar/naming-conventions){target=_blank} set, a secondary ESA granule ID set, and an ARIA-S1-GUNW Frame ID as input. See the [ARIA-S1-GUNW Product Guide Frame ID section](/guides/gunw_product_guide/#aria-frame-ids){target=_blank} for more details on these inputs. +```json + { + "job_type": "ARIA_S1_GUNW", + "name": "Job Name", + "job_parameters": { + "reference": [ + "S1A_IW_SLC__1SDV_20250127T010136_20250127T010203_057623_07199D_4B63", + "S1A_IW_SLC__1SDV_20250127T010111_20250127T010138_057623_07199D_4E88", + "S1A_IW_SLC__1SDV_20250127T010045_20250127T010113_057623_07199D_4D3B" + ], + "secondary": [ + "S1A_IW_SLC__1SDV_20250103T010137_20250103T010204_057273_070BB6_CD45", + "S1A_IW_SLC__1SDV_20250103T010113_20250103T010140_057273_070BB6_1133", + "S1A_IW_SLC__1SDV_20250103T010047_20250103T010115_057273_070BB6_99C5" + ], + "frame_id": 23474 + } + } +``` + ## Submitting autoRIFT jobs AutoRIFT supports processing Sentinel-1, Sentinel-2, or Landsat-8 Collection 2 pairs. From 22fbe34892298923983080b78bc92115adc8760b Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Tue, 4 Mar 2025 12:27:37 -0900 Subject: [PATCH 25/29] edit framing explanation --- docs/guides/gunw_product_guide.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 6a127a84..c9cd42fd 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -38,7 +38,9 @@ In the image below, Sentinel-1 footprints acquired over an area of interest are ![Shifting of Sentinel-1 SLC frames over time](../images/slc_jitter.png "Illustration of the shifting extent of Sentinel-1 SLC footprints over time.") -To address this issue, the ARIA team defined a standard set of geographic footprints, called frames, that set the geographic extent for each ARIA-S1-GUNW product. This is possible because while the Sentinel-1 IW SLC products are not consistently framed along the orbit path, the smaller burst SLCs that comprise each Sentinel-1 IW SLC product *do* have consistent footprints. Thus, ARIA-S1-GUNW frames are defined via the specific bursts that each ARIA-S1-GUNW product contains. **ARIA-S1-GUNWs containing the same bursts, and thus sharing the same geographic footprint, are said to have the same ARIA Frame ID.** +To address this issue, the ARIA team defined a standard set of geographic footprints, called frames, that set the geographic extent for each ARIA-S1-GUNW product. This is possible because while the Sentinel-1 IW SLC products are not consistently framed along the orbit path, the smaller burst SLCs that comprise each Sentinel-1 IW SLC product *do* have consistent footprints. + +Each ARIA frame is defined by the extent of a specific collection of these individual burst SLCs. Each ARIA-S1-GUNW product is processed to the extent of one of these frames, which results in output products with consistent footprints through time. **ARIA-S1-GUNW products containing the same bursts, and thus sharing the same geographic footprint, are said to have the same *ARIA Frame ID*.** To ensure that ARIA-S1-GUNW products are always created using standard footprints, the ARIA Frame ID needs to be provided along with the reference and secondary granules that intersect this footprint for a given date in order to create a new ARIA-S1-GUNW product (see figure below). From f1b84c21d935bebfe852ed7be3b2089e1883b2b1 Mon Sep 17 00:00:00 2001 From: Forrest Williams <31411324+forrestfwilliams@users.noreply.github.com> Date: Tue, 4 Mar 2025 15:45:06 -0600 Subject: [PATCH 26/29] Update docs/guides/gunw_product_guide.md Co-authored-by: Heidi Kristenson <61886203+hjkristenson@users.noreply.github.com> --- docs/guides/gunw_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index c2459c1f..d33fad12 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -74,7 +74,7 @@ There are different ARIA Frame ID maps for the ascending and descending orbit di On-Demand ARIA-S1-GUNW jobs can be submitted via the `ARIA_S1_GUNW` job type via the [HyP3 API](/using/api/#submitting-aria-s1-gunw-jobs){target=_blank}, or via the [HyP3 Python SDK](../using/sdk.md){target=_blank} using the `submit_aria_s1_gunw_job` method of the `HyP3` class. -Unlink our other On-Demand InSAR workflows, customizable processing options (e.g., multilook, filter strength, etc.) are not available for ARIA-S1-GUNW jobs. +Unlike our other On-Demand InSAR workflows, customizable processing options (multilooking, filter strength, etc.) are not available for ARIA-S1-GUNW jobs. ## Product Packaging From c05594b9d1dabcfd8c6b3c296f0db6d7c6256860 Mon Sep 17 00:00:00 2001 From: Forrest Williams <31411324+forrestfwilliams@users.noreply.github.com> Date: Tue, 4 Mar 2025 15:45:23 -0600 Subject: [PATCH 27/29] Update docs/using/api.md Co-authored-by: Heidi Kristenson <61886203+hjkristenson@users.noreply.github.com> --- docs/using/api.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/using/api.md b/docs/using/api.md index feabf7bb..47989976 100644 --- a/docs/using/api.md +++ b/docs/using/api.md @@ -132,7 +132,7 @@ You can also submit InSAR jobs for scene pairs using [ESA granule IDs](https://s ``` ## Submitting ARIA-S1-GUNW jobs -The ARIA-S1-GUNW job type takes a reference [ESA granule IDs](https://sentinel.esa.int/web/sentinel/user-guides/sentinel-1-sar/naming-conventions){target=_blank} set, a secondary ESA granule ID set, and an ARIA-S1-GUNW Frame ID as input. See the [ARIA-S1-GUNW Product Guide Frame ID section](/guides/gunw_product_guide/#aria-frame-ids){target=_blank} for more details on these inputs. +The ARIA-S1-GUNW job type takes a reference [ESA granule ID](https://sentinel.esa.int/web/sentinel/user-guides/sentinel-1-sar/naming-conventions){target=_blank} set, a secondary ESA granule ID set, and an ARIA-S1-GUNW Frame ID as input. See the [ARIA-S1-GUNW Product Guide Frame ID section](/guides/gunw_product_guide/#aria-frame-ids){target=_blank} for more details on these inputs. ```json { "job_type": "ARIA_S1_GUNW", From 00c28655b34b5d8de17455d8424f8616d4852bbc Mon Sep 17 00:00:00 2001 From: Forrest Williams <31411324+forrestfwilliams@users.noreply.github.com> Date: Tue, 4 Mar 2025 15:45:32 -0600 Subject: [PATCH 28/29] Update docs/guides/gunw_product_guide.md Co-authored-by: Heidi Kristenson <61886203+hjkristenson@users.noreply.github.com> --- docs/guides/gunw_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index d33fad12..5a118e0a 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -72,7 +72,7 @@ There are different ARIA Frame ID maps for the ascending and descending orbit di On-demand ARIA S1 GUNW products cannot currently be submitted directly from Vertex, but we plan to make this feature available in the second half of 2025. Vertex is still very useful for selecting Sentinel-1 SLC pairs to submit for processing, but once you identify scene pairs, you will need to submit them using the [HyP3 Python SDK](../using/sdk.md){target=_blank} or [HyP3 API](../using/api.md){target=_blank}. -On-Demand ARIA-S1-GUNW jobs can be submitted via the `ARIA_S1_GUNW` job type via the [HyP3 API](/using/api/#submitting-aria-s1-gunw-jobs){target=_blank}, or via the [HyP3 Python SDK](../using/sdk.md){target=_blank} using the `submit_aria_s1_gunw_job` method of the `HyP3` class. +On-Demand ARIA-S1-GUNW jobs can be submitted using the `ARIA_S1_GUNW` job type via the [HyP3 API](/using/api/#submitting-aria-s1-gunw-jobs){target=_blank}, or via the [HyP3 Python SDK](../using/sdk.md){target=_blank} using the `submit_aria_s1_gunw_job` method of the `HyP3` class. Unlike our other On-Demand InSAR workflows, customizable processing options (multilooking, filter strength, etc.) are not available for ARIA-S1-GUNW jobs. From 16e29823c292ba7acd931d739ec3a861dcc198fa Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Tue, 4 Mar 2025 13:09:21 -0900 Subject: [PATCH 29/29] change primary to reference --- docs/guides/gunw_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index e5dc5b3e..195064cd 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -48,7 +48,7 @@ To ensure that ARIA-S1-GUNW products are always created using standard footprint #### ARIA Frame ID Maps -It can be tricky to find all of the appropriate granules for a given ARIA Frame ID for both the primary and secondary acquisition dates. In the future, ASF plans to create utilities to simplify this process. In the meantime, there are geojson files indicating the extent of each ARIA Frame ID that can be downloaded and used for reference. +It can be tricky to find all of the appropriate granules for a given ARIA Frame ID for both the reference and secondary acquisition dates. In the future, ASF plans to create utilities to simplify this process. In the meantime, there are geojson files indicating the extent of each ARIA Frame ID that can be downloaded and used for reference. There are different ARIA Frame ID maps for the ascending and descending orbit directions. Make sure that you are using the appropriate geojson file.