ASFHyP3 · hjkristenson · Apr 28, 2025 · Apr 21, 2025 · Apr 21, 2025 · Apr 24, 2025
@@ -365,8 +365,8 @@ SDV
 Sentinel-1A
 Sentinel-1B
 Sentinel-1C
+Sentinel-1D
 Sentinel-2
-sexualized
 Shapefile
 shapefile
 show_submodules

@@ -13,4 +13,4 @@
 
 jobs:
   call-changelog-check-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-changelog-check.yml@v0.18.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-changelog-check.yml@v0.18.1
@@ -6,10 +6,10 @@
 
 jobs:
   call-create-jira-issue-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-create-jira-issue.yml@v0.18.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-create-jira-issue.yml@v0.18.1
     secrets:
       JIRA_BASE_URL: ${{ secrets.JIRA_BASE_URL }}
       JIRA_USER_EMAIL: ${{ secrets.JIRA_USER_EMAIL }}
      JIRA_API_TOKEN: ${{ secrets.JIRA_API_TOKEN }}
      JIRA_PROJECT: ${{ secrets.JIRA_PROJECT }}
      JIRA_FIELDS: ${{ secrets.JIRA_FIELDS }}
@@ -12,4 +12,4 @@
 
 jobs:
   call-labeled-pr-check-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-labeled-pr-check.yml@v0.18.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-labeled-pr-check.yml@v0.18.1
@@ -7,6 +7,6 @@
 
 jobs:
   call-release-checklist-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-release-checklist-comment.yml@v0.18.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-release-checklist-comment.yml@v0.18.1
     secrets:
       USER_TOKEN: ${{ secrets.GITHUB_TOKEN }}
@@ -7,8 +7,8 @@
 
 jobs:
   call-release-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-release.yml@v0.18.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-release.yml@v0.18.1
     with:
       release_prefix: HyP3 Docs
     secrets:
      USER_TOKEN: ${{ secrets.TOOLS_BOT_PAK }}
@@ -4,4 +4,4 @@
 
 jobs:
   call-secrets-analysis-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-secrets-analysis.yml@v0.18.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-secrets-analysis.yml@v0.18.1
@@ -7,6 +7,6 @@
 
 jobs:
   call-bump-version-workflow:
-    uses: ASFHyP3/actions/.github/workflows/reusable-bump-version.yml@v0.18.0
+    uses: ASFHyP3/actions/.github/workflows/reusable-bump-version.yml@v0.18.1
     secrets:
       USER_TOKEN: ${{ secrets.TOOLS_BOT_PAK }}
@@ -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.5]
+
+### Changed
+* Updated documentation to include information about Sentinel-1C
+
 ## [0.10.4]
 
 ### Added

@@ -5,8 +5,9 @@
 
 This document is a guide for users of Sentinel-1 Burst Interferometric Synthetic Aperture Radar (InSAR) products generated by the Alaska Satellite Facility (ASF).
 
-InSAR jobs can be processed on the basis of individual [Sentinel-1 burst SLCs](#sentinel-1-bursts "Jump to the Sentinel-1 Bursts 
-section of this document") that comprise the Sentinel-1 SLC products, and users can select up to fifteen contiguous 
+InSAR jobs can be processed on the basis of individual 
+[Sentinel-1 burst SLCs](#sentinel-1-bursts "Jump to the Sentinel-1 Bursts section of this document") 
+that comprise the Sentinel-1 SLC products, and users can select up to fifteen contiguous 
 along-path bursts to merge together into a single interferogram.
 
 ## Burst InSAR Software
@@ -20,6 +21,16 @@ For those who would prefer to work at the scale of a full IW SLC, our original
 [On Demand InSAR](insar_product_guide.md){target=_blank} products are still available. These products have a larger 
 footprint, and are generated using [GAMMA software](https://www.gamma-rs.ch/software){target=_blank}.
 
+!!! warning "Sentinel-1C acquisitions not yet supported" 
+
+    ISCE2 software does not currently support processing Sentinel-1C acquisitions. Until the software package is 
+    updated, users will only be able to submit granules acquired by Sentinel-1A or Sentinel-1B for Burst InSAR 
+    processing. 
+
+    Users can submit full IW Sentinel-1C granules for processing to InSAR using the 
+    [On Demand InSAR](insar_product_guide.md "Sentinel-1 InSAR Product Guide") option, which leverages 
+    GAMMA software rather than ISCE2. 
+
 ## Burst InSAR Job Types
 
 There are currently two different [burst-based](#sentinel-1-bursts "Jump to the Sentinel-1 Bursts section of this document") 
@@ -206,7 +217,7 @@ reference and secondary SAFE files:
 - Bursts crossing the antimeridian are not supported
 
 When selecting input bursts that span across sub-swaths in the same relative path, you must also take care not to 
-leave gaps. The bursts in neighboring swaths can only be offset along the path by one burst. 
+leave gaps. The bursts in neighboring sub-swaths can only be offset along the path by one burst. 
 
 For example, the grouping of bursts shown in the image on the left in Figure 4 can be submitted for processing, 
 while the grouping in the image on the right would not be valid.
@@ -338,7 +349,7 @@ the following order, as illustrated in Figure 3.
 - Relative burst ID values assigned by ESA. Each value identifies a consistent burst footprint; relative burst ID 
   values differ from one sub-swath to the next.
 - The imaging mode, currently only IW is supported.
-- The swath number, either 1, 2, or 3, indicating which sub-swath the burst is located in.
+- The sub-swath number, either 1, 2, or 3, indicating which sub-swath the burst is located in.
 - The acquisition dates of the reference (older) scene and the secondary (newer) scene.
 - The polarization of the product, either HH or VV.
 - The product type (always INT for InSAR) and the pixel spacing in meters, which will be 80, 40, or 20, based upon the 
@@ -608,7 +619,7 @@ with two exceptions:
   - The four range-doppler images are not included since the products have already been merged
   - The product name is slightly modified
     - The burst ID (`bbbbbb`) is swapped for the zero-padded relative orbit number (`rrr`)
-    - The swath number is removed 
+    - The sub-swath number is removed 
     - The resulting format is `S1_rrr__yyymmdd_yyymmdd_pp_INTn_uuuu`
 
 {% endblock %}

@@ -8,14 +8,19 @@ With over 1.1 million (and growing!) freely available products covering major fa
 
 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.
 
-!!! warning "ARIA-S1-GUNW products are not produced globally"
+!!! 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.
 
 ## 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"). 
 
+!!! warning "ARIA-S1-GUNW On-Demand processing not supported for Alaska"
+
+    ARIA-S1-GUNW products rely on RAiDER software for atmospheric delay correction. This software does not currently 
+    support processing acquisitions over Alaska, causing On-Demand ARIA-S1-GUNW jobs submitted over Alaska to fail. 
+
 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.
 
 ## Accessing Existing Products
@@ -32,6 +37,12 @@ You can download existing ARIA-S1-GUNW products from the Alaska Satellite Facili
 
 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. 
 
+!!! warning "Sentinel-1C acquisitions not yet supported" 
+
+    ISCE2 software, which is used for processing ARIA-S1-GUNW products, does not currently support processing 
+    SLCs acquired by the newly launched Sentinel-1C platform. Until the software package is updated, users will 
+    not be able to submit ARIA-S1-GUNW jobs that include Sentinel-1C acquisitions for On-Demand processing.
+
 ### 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.

@@ -10,13 +10,9 @@ For a step-by-step tutorial on ordering On-Demand InSAR Products using Vertex, v
 
 InSAR processing requires a Digital Elevation Model (DEM) for the removal of topographic phase. We use the [GLO-30 Copernicus DEM](https://dataspace.copernicus.eu/explore-data/data-collections/copernicus-contributing-missions/collections-description/COP-DEM "Copernicus DEM" ){target=_blank} when processing our On Demand InSAR products. Refer to the [Prepare the DEM File section](#prepare-the-dem-file "Jump to the Prepare the DEM File Section of this document") for more information. 
 
-!!! tip "Coverage gaps in Copernicus DEM GLO-30 filled using GLO-90" 
+!!! tip "On-Demand Burst-Based InSAR Now Available" 
 
-    The Copernicus DEM GLO-30 dataset does not provide coverage over Armenia and Azerbaijan. In the past, we have not supported InSAR product generation over those areas, due to the lack of DEM coverage. We now use the Copernicus DEM GLO-90 to fill those gaps. 
-
-    The GLO-90 dataset has a pixel spacing of 90 meters, which is not as detailed as the 30-m pixel spacing in the GLO-30 DEM, but it does allow us to provide InSAR products in these regions, where they were previously unavailable. 
-
-ASF also offers burst-based Sentinel-1 InSAR products. This on-demand processing option allows users to submit InSAR jobs for [individual SLC bursts](https://storymaps.arcgis.com/stories/88c8fe67933340779eddef212d76b8b8 "Sentinel-1 Bursts Tutorial https://arcg.is/zSafi0" ){target=_blank} rather than the full [Sentinel-1 IW SLC products](https://sentinels.copernicus.eu/web/sentinel/technical-guides/sentinel-1-sar/products-algorithms/level-1/single-look-complex/interferometric-wide-swath "https://sentinels.copernicus.eu" ){target=_blank}. Refer to our [Sentinel-1 Burst InSAR Product Guide](burst_insar_product_guide.md) for more information on this option.
+    ASF also offers burst-based Sentinel-1 InSAR products. This on-demand processing option allows users to submit InSAR jobs for [individual SLC bursts](https://storymaps.arcgis.com/stories/88c8fe67933340779eddef212d76b8b8 "Sentinel-1 Bursts Tutorial https://arcg.is/zSafi0" ){target=_blank} rather than the full [Sentinel-1 IW SLC products](https://sentinels.copernicus.eu/web/sentinel/technical-guides/sentinel-1-sar/products-algorithms/level-1/single-look-complex/interferometric-wide-swath "https://sentinels.copernicus.eu" ){target=_blank}. Refer to our [Sentinel-1 Burst InSAR Product Guide](burst_insar_product_guide.md) for more information on this option.
 
 Users are cautioned to read the sections on [limitations](#limitations "Jump to the Limitations section of this document") and [error sources](#error-sources "Jump to the Error Sources section of this document") in InSAR products before attempting to use InSAR data. For a more complete description of the properties of SAR, see our [Introduction to SAR](../guides/introduction_to_sar.md "https://hyp3-docs.asf.alaska.edu/guides/introduction_to_sar" ){target=_blank} guide. 
 {% endblock %}
@@ -219,15 +215,23 @@ HyP3 InSAR output is a zip file containing various files, including GeoTIFFs, PN
 
 ### Naming Convention
 
-The InSAR product names are packed with information pertaining to the processing of the data, presented in the following order, as illustrated in Figure 4. 
+The InSAR product names are packed with information pertaining to the processing of the data, presented in the 
+following order, as illustrated in Figure 4. 
 
-- The platform names, either Sentinel-1A or Sentinel-1B, are abbreviated "A" or "B", indicating the reference and secondary granule's imaging platform
-- The reference start date and time and the secondary start date and time, with the date and time separated by the letter T
+- The platform names, one of Sentinel-1A, Sentinel-1B, or Sentinel-1C, are abbreviated with the letters `A`, `B`, or `C`
+    - Two of these letters follow `S1`, indicating the platform(s) used to acquire the reference and 
+      secondary images, in that order (`S1AA`, `S1BA`, `S1AC`, etc.)
+- The reference start date and time and the secondary start date and time, with the date and time 
+  separated by the letter T
 - The polarizations for the pair, either HH or VV, the orbit type, and the days of separation for the pair
-- The product type (always INT for InSAR) and the pixel spacing, which will be either 80 or 40, based upon the number of looks selected when the job was submitted for processing
+- The product type (always INT for InSAR) and the pixel spacing, which will be either 80 or 40, based upon the 
+  number of looks selected when the job was submitted for processing
 - The software package used for processing is always GAMMA for GAMMA InSAR products
-- User-defined options are denoted by three characters indicating whether the product is water masked (w) or not (u), the scene is clipped (e for entire area, c for clipped), and whether a single sub-swath was processed or the entire granule (either 1, 2, 3, or F for full swath)
-    - *Currently, only the water masking is available as a user-selected option; the products always include the full granule extent with all three sub-swaths*
+- User-defined options are denoted by three characters indicating whether the product is water masked (w) or not (u), 
+  the scene is clipped (e for entire area, c for clipped), and whether a single sub-swath was processed or the entire 
+  granule (either 1, 2, 3, or F for full swath)
+    - *Currently, only the water masking is available as a user-selected option; the products always include the 
+      full granule extent with all three sub-swaths*
 - The filename ends with the ASF product ID, a 4 digit hexadecimal number
 
 

@@ -66,6 +66,12 @@ For deformation mapping, it is best to minimize the perpendicular baseline whene
 
 All of ASF's On Demand InSAR products are generated using the [HyP3 platform](https://hyp3-docs.asf.alaska.edu/products/ "hyp3-docs.asf.alaska.edu" ){target=_blank}. Jobs can be submitted for processing using the [Vertex](https://search.asf.alaska.edu/ "https://search.asf.alaska.edu" ){target=_blank} data portal, the [HyP3 Python SDK](https://hyp3-docs.asf.alaska.edu/using/sdk/ "https://hyp3-docs.asf.alaska.edu/using/sdk" ){target=_blank} or the [HyP3 API](https://hyp3-docs.asf.alaska.edu/using/api/ "https://hyp3-docs.asf.alaska.edu/using/api" ){target=_blank}.
 
+!!! warning "Sentinel-1C Support for InSAR Processing" 
+
+    GAMMA software supports Sentinel-1C acquisitions as input for InSAR processing, but ISCE2 software currently does 
+    not. Until ISCE2 is updated, users will only be able to submit jobs including Sentinel-1C SLCs for processing 
+    using [On Demand InSAR](insar_product_guide.md), not [On Demand Burst InSAR](burst_insar_product_guide.md).
+
 ### Vertex
 InSAR pairs are selected in [Vertex](https://search.asf.alaska.edu/#/ "https://search.asf.alaska.edu" ){target=_blank} using either the [Baseline Search](https://docs.asf.alaska.edu/vertex/baseline/ "https://docs.asf.alaska.edu/vertex/baseline" ){target=_blank} or the [SBAS Search](https://docs.asf.alaska.edu/vertex/sbas/ "https://docs.asf.alaska.edu/vertex/sbas" ){target=_blank} interface. The process of selecting pairs is the same for both IW SLC products and individual SLC bursts, but you will need to select the appropriate dataset when searching for content. As illustrated below, select the **Sentinel-1** option in the Dataset menu to search for IW SLC products, and select the **S1 Bursts** option to search for individual SLC bursts.