diff --git a/.github/workflows/changelog.yml b/.github/workflows/changelog.yml index 1454dbf6a..6f12305c2 100644 --- a/.github/workflows/changelog.yml +++ b/.github/workflows/changelog.yml @@ -13,4 +13,4 @@ on: jobs: call-changelog-check-workflow: - uses: ASFHyP3/actions/.github/workflows/reusable-changelog-check.yml@v0.18.1 + uses: ASFHyP3/actions/.github/workflows/reusable-changelog-check.yml@v0.20.0 diff --git a/.github/workflows/create-jira-issue.yml b/.github/workflows/create-jira-issue.yml index 5765047a6..c77e1e814 100644 --- a/.github/workflows/create-jira-issue.yml +++ b/.github/workflows/create-jira-issue.yml @@ -6,7 +6,7 @@ on: jobs: call-create-jira-issue-workflow: - uses: ASFHyP3/actions/.github/workflows/reusable-create-jira-issue.yml@v0.18.1 + uses: ASFHyP3/actions/.github/workflows/reusable-create-jira-issue.yml@v0.20.0 secrets: JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }} JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }} diff --git a/.github/workflows/labeled-pr.yml b/.github/workflows/labeled-pr.yml index ad68c9c33..b86b899b4 100644 --- a/.github/workflows/labeled-pr.yml +++ b/.github/workflows/labeled-pr.yml @@ -12,4 +12,4 @@ on: jobs: call-labeled-pr-check-workflow: - uses: ASFHyP3/actions/.github/workflows/reusable-labeled-pr-check.yml@v0.18.1 + uses: ASFHyP3/actions/.github/workflows/reusable-labeled-pr-check.yml@v0.20.0 diff --git a/.github/workflows/release-template-comment.yml b/.github/workflows/release-template-comment.yml index 9175cd8e2..297ac0c93 100644 --- a/.github/workflows/release-template-comment.yml +++ b/.github/workflows/release-template-comment.yml @@ -7,6 +7,6 @@ on: jobs: call-release-checklist-workflow: - uses: ASFHyP3/actions/.github/workflows/reusable-release-checklist-comment.yml@v0.18.1 + uses: ASFHyP3/actions/.github/workflows/reusable-release-checklist-comment.yml@v0.20.0 secrets: USER_TOKEN: ${{ secrets.GITHUB_TOKEN }} diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 27e481b26..e4ece3ea9 100644 --- a/.github/workflows/release.yml +++ b/.github/workflows/release.yml @@ -7,7 +7,7 @@ on: jobs: call-release-workflow: - uses: ASFHyP3/actions/.github/workflows/reusable-release.yml@v0.18.1 + uses: ASFHyP3/actions/.github/workflows/reusable-release.yml@v0.20.0 with: release_prefix: HyP3 Docs secrets: diff --git a/.github/workflows/static-analysis.yml b/.github/workflows/static-analysis.yml index c700493db..c3c0c4e16 100644 --- a/.github/workflows/static-analysis.yml +++ b/.github/workflows/static-analysis.yml @@ -4,4 +4,4 @@ on: push jobs: call-secrets-analysis-workflow: - uses: ASFHyP3/actions/.github/workflows/reusable-secrets-analysis.yml@v0.18.1 + uses: ASFHyP3/actions/.github/workflows/reusable-secrets-analysis.yml@v0.20.0 diff --git a/.github/workflows/tag-release.yml b/.github/workflows/tag-release.yml index b34189c45..89cde1fe9 100644 --- a/.github/workflows/tag-release.yml +++ b/.github/workflows/tag-release.yml @@ -7,6 +7,6 @@ on: jobs: call-bump-version-workflow: - uses: ASFHyP3/actions/.github/workflows/reusable-bump-version.yml@v0.18.1 + uses: ASFHyP3/actions/.github/workflows/reusable-bump-version.yml@v0.20.0 secrets: USER_TOKEN: ${{ secrets.TOOLS_BOT_PAK }} diff --git a/CHANGELOG.md b/CHANGELOG.md index 589dd24fc..283afd670 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -6,6 +6,11 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [PEP 440](https://www.python.org/dev/peps/pep-0440/) and uses [Semantic Versioning](https://semver.org/spec/v2.0.0.html). +## [0.10.10] + +### Changed +* The cost of autoRIFT jobs has been increased to 50 credits, from 25 credits, on the [credits](docs/using/credits.md) page. + ## [0.10.9] ### Changed diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 7f96ee708..c6c575567 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -1,36 +1,75 @@ # ARIA Sentinel-1 GUNW Product Guide -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)](https://aria.jpl.nasa.gov/products/standard-displacement-products.html){target=_blank} 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/parosen/Geo-SInC/blob/main/EarthScope2024/2.2_TOPS_Data_Processing/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 project also maintains the [ARIA-tools](https://doi.org/10.1029/2020GL090013){target=_blank} software, which is a suite of open-source tools which automates the seamless download, post-processing manipulation, aggregation, and management of ARIA-S1-GUNW products. Users may refer to the dedicated [GitHub](https://github.com/aria-tools/ARIA-tools){target=_blank} page for a more exhaustive overview and installation instructions, and [EarthScope Consortium led tutorials](https://www.youtube.com/watch?v=_a9T59VTz7Q&t=12734s){target=_blank} which demonstrate practical applications. +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 "ASF-ARIA-S1-GUNW Products" ){target=_blank}. + +The +[ARIA Sentinel-1 Geocoded Unwrapped Interferogram (ARIA-S1-GUNW)](https://aria.jpl.nasa.gov/products/standard-displacement-products.html "ARIA Standard Displacement Products" ){target=_blank} +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/ "aria.jpl.nasa.gov" ){target=_blank} +project and hosted at the +[Alaska Satellite Facility (ASF) DAAC](https://www.earthdata.nasa.gov/centers/asf-daac "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. Products are available for VV polarization only. + +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/parosen/Geo-SInC/blob/main/EarthScope2024/2.2_TOPS_Data_Processing/topsApp.ipynb "ISCE2 GitHub repository" ){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 project also maintains the [ARIA-tools](https://doi.org/10.1029/2020GL090013){target=_blank} software, +which is a suite of open-source tools which automates the seamless download, post-processing manipulation, +aggregation, and management of ARIA-S1-GUNW products. Users may refer to the dedicated +[GitHub](https://github.com/aria-tools/ARIA-tools "ARIA-tools GitHub repository" ){target=_blank} +page for a more exhaustive overview and installation instructions, and +[tutorials led by EarthScope Consortium](https://www.youtube.com/watch?v=_a9T59VTz7Q&t=12734s "EarthScope Tutorials on YouTube" ){target=_blank}, +which demonstrate practical applications. !!! tip "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 Products section](#ordering-on-demand-products "Jump to Ordering On Demand Products section of this document") for information on ordering ARIA-S1-GUNW products for specific Sentinel-1 acquisitions. + 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 Products section](#ordering-on-demand-products "Jump to Ordering On Demand Products section of this document") + for information on ordering ARIA-S1-GUNW products for specific Sentinel-1 acquisitions. ## 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-products "Jump to Ordering On Demand Products section of this document"). +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-products "Jump to Ordering On Demand 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. +On Demand ARIA-S1-GUNW products are generated using the same code used by the ARIA project, and have been validated +to ensure that products generated On Demand and those generated by the ARIA team at JPL are fully interoperable. ## 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: +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) "Vertex ARIA-S1-GUNW Search" ){target=_blank} +search portal by following these steps: -1. **Access Vertex** – Go to the ASF Vertex website: [https://search.asf.alaska.edu](https://search.asf.alaska.edu){target=blank}. -2. **Search for ARIA-S1-GUNW Products** – In the dataset selector, click on “ARIA S1 GUNW” to filter for these specific products. You can refine results by specifying a geographic region, date range, or other criteria using the search filters in the “filters” panel. +1. **Access Vertex** – Go to the ASF Vertex website: + [https://search.asf.alaska.edu](https://search.asf.alaska.edu "search.asf.alaska.edu" ){target=blank}. +2. **Search for ARIA-S1-GUNW Products** – In the dataset selector, click on “ARIA S1 GUNW” to filter for these + specific products. You can refine results by specifying a geographic region, date range, or other criteria + using the search filters in the “filters” panel. ![Vertex ARIA S1 GUNW Dataset Selection](../images/vertex-GUNW-dataset-selection.png) -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. +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. ## Ordering On-Demand Products -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. +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. Once processing is complete, you can access them as you would any other +[On-Demand](#accessing-on-demand-aria-s1-gunw-products "Jump to the Accessing On Demand ARIA S1 GUNW Products section of this document" ) +products from ASF. The download links provided will be active for 14 days. !!! warning "Sentinel-1C acquisitions not yet supported" @@ -40,74 +79,108 @@ 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 inconsistent framing of the Sentinel-1 IW SLCs 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. -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. +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. +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*.** +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). +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 cover this footprint for a given date in order to +create a new ARIA-S1-GUNW product (see figure below). ![Frame vs granule geographic footprint](../images/frame_granule_overlap.png "Example of a frame that spans three granules.") #### ARIA Frame ID Maps -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. +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. +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} +- [Ascending ARIA Frame IDs](https://d3g9emy65n853h.cloudfront.net/ARIA_S1_GUNW/ascending.geojson "ARIA-S1-GUNW Ascending Frame IDs GeoJSON" ){target=_blank} +- [Descending ARIA Frame IDs](https://d3g9emy65n853h.cloudfront.net/ARIA_S1_GUNW/descending.geojson "ARIA-S1-GUNW Descending Frame IDs GeoJSON" ){target=_blank} ### Search for Sentinel-1 SLCs for an ARIA Frame ID -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. +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. +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 along the Sentinel-1 orbit path 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. #### 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: +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 must be in VV polarization*** + + - ARIA S1 GUNW jobs do not support acquisitions in HH polarization + - cross-polarized returns (VH or HV) are not supported - ***1. All scenes (reference and secondary) must be from the same relative orbit*** + ***2. 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 + - 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)*** + ***3. 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 + - 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*** + ***4. 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*** + ***5. 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*** + ***6. 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 + - 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*** + ***7. Reference and secondary scenes must 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 + - 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. +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: @@ -126,17 +199,36 @@ Based on your search results, create a list of the reference and secondary Senti !!! 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}. + 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 using the `ARIA_S1_GUNW` job type via the [HyP3 API](../using/api.md#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.md#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. +Unlike our other On-Demand InSAR workflows, customizable processing options (multilooking, filter strength, etc.) +are not available for ARIA-S1-GUNW jobs. + +### Accessing On-Demand ARIA-S1-GUNW Products + +To access the products you submitted On Demand, use the +[On Demand Search Type in Vertex](https://search.asf.alaska.edu/#/?maxResults=1000&searchType=On%20Demand "On Demand Vertex Search" ){target=_blank}. +Once processing is complete, the download links available in this interface are active for 14 days. + +You can also search for your On Demand products programmatically, using the +[HyP3 API](https://hyp3-docs.asf.alaska.edu/using/api/#querying-jobs "hyp3-docs.asf.alaska.edu/using/api/#querying-jobs" ){target=_blank} +or the +[HyP3 Python SDK](https://hyp3-docs.asf.alaska.edu/using/sdk/#finding-existing-jobs "hyp3-docs.asf.alaska.edu/using/sdk/#finding-existing-jobs" ){target=_blank}. ## Product Packaging ### Naming convention -The ARIA-S1-GUNW product names contain detailed information about their acquisition and processing, as illustrated in the figure below. +The ARIA-S1-GUNW product names contain detailed information about their acquisition and processing, +as illustrated in the figure below. GUNW naming convention includes: @@ -151,10 +243,14 @@ GUNW naming convention includes: ![GUNW naming scheme](../images/asf_gunw_names.png "Breakdown of ARIA-S1-GUNW Naming Scheme") - ### Product Elements -The product is packaged as a NetCDF4 file, with its top-level group named `science`. Within the science group, there is a `grids` group, which is further divided into three subgroups: `data`, `imagingGeometry`, and `corrections`. The `data` group contains 2D datasets at a resolution of 3 arc-seconds (~90 m) and the `imagingGeometry` group includes 3D datasets posted laterally at 0.1-degree intervals (~11 km). The `corrections` group provides ionospheric and solid Earth corrections, and if a weather model is available, the corresponding tropospheric correction layer (`HRRR/reference/troposphereWet`) will be included here. All 2D and 3D datasets are in the EPSG:4326 projection. +The product is packaged as a NetCDF4 file, with its top-level group named `science`. Within the science group, +there is a `grids` group, which is further divided into three subgroups: `data`, `imagingGeometry`, and `corrections`. +The `data` group contains 2D datasets at a resolution of 3 arc-seconds (~90 m) and the `imagingGeometry` group +includes 3D datasets posted laterally at 0.1-degree intervals (~11 km). The `corrections` group provides ionospheric +and solid Earth corrections, and if a weather model is available, the corresponding tropospheric correction layer +(`HRRR/reference/troposphereWet`) will be included here. All 2D and 3D datasets are in the EPSG:4326 projection. The output netCDF file will include the layers listed in the table below. @@ -181,24 +277,45 @@ The output netCDF file will include the layers listed in the table below. ### Ionospheric Correction Layers -Although the ionospheric effects for C-band SAR are only about one-sixteenth of those at L-band, the measurement accuracy of Sentinel-1 C-band SAR data can still be degraded by long-wavelength ionospheric signals. Utilizing the [range-split spectrum methodology](https://doi.org/10.1109/TGRS.2019.2908494){target=_blank} available within ISCE2, ARIA-S1-GUNW products include ionospheric correction layers for both the reference and secondary input data. +Although the ionospheric effects for C-band SAR are only about one-sixteenth of those at L-band, the measurement +accuracy of Sentinel-1 C-band SAR data can still be degraded by long-wavelength ionospheric signals. Utilizing the +[range-split spectrum methodology](https://doi.org/10.1109/TGRS.2019.2908494){target=_blank} available within ISCE2, +ARIA-S1-GUNW products include ionospheric correction layers for both the reference and secondary input data. ### Solid Earth Tides Correction Layers -[Solid Earth tides](https://doi.org/10.1109/TGRS.2022.3168509){target=_blank} (SET) are periodic deformations of the Earth's crust caused by gravitational forces from the Moon and Sun, resulting in surface displacements of up to several centimeters. Correcting for SET in InSAR is crucial to prevent these predictable, cyclic motions from being misinterpreted as real ground deformation. ARIA-S1-GUNW products include an SET correction layer for both the reference and secondary input data that are created using the [PySolid](https://github.com/insarlab/PySolid?tab=readme-ov-file){target=_blank} python package. +[Solid Earth tides](https://doi.org/10.1109/TGRS.2022.3168509){target=_blank} (SET) are periodic deformations of the +Earth's crust caused by gravitational forces from the Moon and Sun, resulting in surface displacements of up to +several centimeters. Correcting for SET in InSAR is crucial to prevent these predictable, cyclic motions from being +misinterpreted as real ground deformation. ARIA-S1-GUNW products include an SET correction layer for both the +reference and secondary input data that are created using the +[PySolid](https://github.com/insarlab/PySolid?tab=readme-ov-file "PySolid GitHub repository" ){target=_blank} +python package. ### Tropospheric Delay Correction Layers -Tropospheric delay correction is essential for many InSAR applications because atmospheric variations in temperature, pressure, and humidity can distort phase measurements, mimicking ground deformation and reducing accuracy. ARIA-S1-GUNW products for both the continental U.S. and Alaska also contain a tropospheric delay correction layer that is produced via the Raytracing Atmospheric Delay Estimation for RADAR ([RAiDER](https://github.com/dbekaert/RAiDER){target=_blank}) Python package. +Tropospheric delay correction is essential for many InSAR applications because atmospheric variations in temperature, +pressure, and humidity can distort phase measurements, mimicking ground deformation and reducing accuracy. +ARIA-S1-GUNW products for both the continental U.S. and Alaska also contain a tropospheric delay correction layer +that is produced via the Raytracing Atmospheric Delay Estimation for RADAR +([RAiDER](https://github.com/dbekaert/RAiDER "RAiDER GitHub repository" ){target=_blank}) Python package. -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. +RAiDER uses the +[NOAA High-Resolution Rapid Refresh](https://rapidrefresh.noaa.gov/hrrr/ "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, (i.e. 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. ### 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). - -Buzzanga, Brett, et al. "Toward sustained monitoring of subsidence at the coast using InSAR and GPS: An application in Hampton Roads, Virginia." Geophysical Research Letters 47.18 (2020): e2020GL090013. +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). -Liang, Cunren, et al. "Ionospheric correction of InSAR time series analysis of C-band Sentinel-1 TOPS data." IEEE Transactions on Geoscience and Remote Sensing 57.9 (2019): 6755-6773. +Buzzanga, Brett, et al. "Toward sustained monitoring of subsidence at the coast using InSAR and GPS: An application +in Hampton Roads, Virginia." Geophysical Research Letters 47.18 (2020): e2020GL090013. -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. +Liang, Cunren, et al. "Ionospheric correction of InSAR time series analysis of C-band Sentinel-1 TOPS data." +IEEE Transactions on Geoscience and Remote Sensing 57.9 (2019): 6755-6773. +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. diff --git a/docs/products.md b/docs/products.md index 27f3cabc0..1f1a2d9e9 100644 --- a/docs/products.md +++ b/docs/products.md @@ -86,12 +86,9 @@ There is an extensive archive of but they are only generated in specific geographic locations. If the existing archive does not provide the products you need, you can generate ARIA GUNW products on demand. -ARIA S1 GUNW products are delivered as netCDF files with 90-m pixel spacing. The On-Demand -products are generated using the same +ARIA S1 GUNW products are delivered as netCDF files with 90-m pixel spacing. Products generated On Demand use the same [ISCE2](https://github.com/isce-framework/isce2#readme "https://github.com/isce-framework/isce2" ){target=_blank}-based -code used to generate the archived products, and standard ARIA S1 GUNW products -generated on demand are automatically added to the archive. This allows all users to access the On-Demand products -indefinitely, which is an exception to the 14-day availability period that applies to all other On-Demand products. +code used to generate the archived products to ensure interoperability. The ARIA S1 GUNW products use a set [framing system](guides/gunw_product_guide.md#aria-frame-ids "ARIA Sentinel-1 GUNW Product Guide: ARIA Frame IDs") to select consistent bursts from input Sentinel-1 IW SLCs to generate interferograms. diff --git a/docs/using/credits.md b/docs/using/credits.md index c3ae8f68d..6ed5eedec 100644 --- a/docs/using/credits.md +++ b/docs/using/credits.md @@ -46,7 +46,7 @@ allotment on jobs of that particular type. | {{ table_indent(count=2) }} 14 pairs | 105 | {{ max_jobs_per_month(105) }} | | {{ table_indent(count=2) }} 15 pairs | 110 | {{ max_jobs_per_month(110) }} | | [**AutoRIFT**](https://its-live.jpl.nasa.gov/){target=_blank} | | | -| {{ table_indent() }} Standard product (120-m pixel spacing) | 25 | {{ max_jobs_per_month(25) }} | +| {{ table_indent() }} Standard product (120-m pixel spacing) | 50 | {{ max_jobs_per_month(50) }} | The credit cost of a given job is roughly proportional to the computational resources required to process the job, allowing us to distribute our resources more equitably.