Release v0.10.17

.github/dependabot.yml

@@ -11,9 +11,17 @@ updates:
       interval: weekly
     labels:
       - bumpless
+    groups:
+      pip-deps:
+        patterns:
+          - "*"
   - package-ecosystem: github-actions
     directory: /
     schedule:
       interval: weekly
     labels:
       - bumpless
+    groups:
+      github-actions-deps:
+        patterns:
+          - "*"

.github/dictionary.txt

@@ -385,6 +385,7 @@ S1A_064_E053_1_N27_3_E054_1_N27_8_20200604_20200616_VV_INT80_7EB5
 S1A_IW_SLC__1SDV_20200116T032559_20200116T032627_030820_038928_F5DC
 S1B
 S1B_IW_SLC__1SDV_20200128T032559_20200128T032627_030995_038F51_7D4F
+S1C
 S1s
 S1s_rrr_lonl_f_lal_f_lonu_f_lau_f_yyyymmdd_yyyymmdd_pp_INTzz_cccc
 S2

CHANGELOG.md

@@ -6,6 +6,14 @@ 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.17]
+
+### Changed
+* Updated messages about Sentinel-1C support to indicate that burst-based InSAR now supports S1C as input
+
+### Fixed
+* Fixed outdated ESA Sentinel links. 
+
 ## [0.10.16]
 
 ### Changed

docs/guides/burst_insar_product_guide.md

@@ -21,15 +21,11 @@ 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" 
+!!! tip "Sentinel-1C acquisitions now 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. 
+    ISCE2 has been updated to support processing of data collected by Sentinel-1C. Users can now submit 
+    burst-based InSAR jobs for any available bursts from Sentinel-1 IW SLCs, regardless of the platform used 
+    to acquire the data.
 
 ## Burst InSAR Job Types
 
@@ -66,13 +62,13 @@ section for details). The number of bursts processed impacts the number of credi
 
 ## Sentinel-1 Bursts
 
-[Single Look Complex](https://sentinels.copernicus.eu/web/sentinel/technical-guides/sentinel-1-sar/products-algorithms/level-1-algorithms/single-look-complex 'https://sentinels.copernicus.eu/web/sentinel/technical-guides/sentinel-1-sar/products-algorithms/level-1-algorithms/single-look-complex' ){target=_blank} 
+[Single Look Complex](https://sentiwiki.copernicus.eu/web/s1-processing#S1-Processing-Single-Look-Complex "https://sentiwiki.copernicus.eu/web/s1-processing#S1-Processing-Single-Look-Complex" ){target=_blank} 
 (SLC) data is required to generate interferograms from Sentinel-1 data. The European Space Agency (ESA) packages this 
 type of data into Interferometric Wide (IW) SLC products, which are available for download from ASF. These IW SLC 
 products include three sub-swaths, each containing many individual burst SLCs.
 
 Historically, most InSAR processing has been performed using the full IW SLC scene, but ASF has developed a method of 
-[extracting the individual SLC bursts](https://sentinel1-burst-documentation.asf.alaska.edu/ 'https://sentinel1-burst-documentation.asf.alaska.edu/' ){target=_blank} 
+[extracting the individual SLC bursts](https://sentinel1-burst-documentation.asf.alaska.edu/ "https://sentinel1-burst-documentation.asf.alaska.edu/" ){target=_blank} 
 from IW SLC products, which facilitates burst-based processing workflows.
 
 Refer to the 
@@ -185,7 +181,7 @@ downloading the DEM file, and downloading the orbit and auxiliary data files.
 #### Download Burst Data
 
 The Burst InSAR workflow accepts as input a reference and secondary set of 
-[Interferometric Wide swath Single Look Complex](https://sentinel.esa.int/web/sentinel/user-guides/sentinel-1-sar/acquisition-modes/interferometric-wide-swath "https://sentinel.esa.int/web/sentinel/user-guides/sentinel-1-sar/acquisition-modes/interferometric-wide-swath" ){target=_blank} 
+[Interferometric Wide swath Single Look Complex](https://sentiwiki.copernicus.eu/web/s1-mission#S1Mission-InterferometricWideSwathS1-Mission-Interferometric-Wide-Swath "https://sentiwiki.copernicus.eu/web/s1-mission#S1Mission-InterferometricWideSwath" ){target=_blank} 
 (IW SLC) burst granules. Internally, each set of bursts must share the same polarization (VV or HH), and be 
 contiguous along a single Sentinel-1 orbit path. See 
 [Considerations for Selecting Input Bursts](#considerations-for-selecting-input-bursts "Jump to the Considerations for Selecting Input Bursts section in this document") 
@@ -258,9 +254,9 @@ Burst InSAR processing is performed using the outputs from the processes detaile
 [Pre-Processing](#pre-processing "Jump to the Pre-Processing section of this document") section. 
 
 The Burst InSAR processing code is contained in the 
-[`insar_tops_burst.py`](https://github.com/ASFHyP3/hyp3-isce2/blob/main/src/hyp3_isce2/insar_tops_burst.py ){target=_blank} 
+[`insar_tops_burst.py`](https://github.com/ASFHyP3/hyp3-isce2/blob/main/src/hyp3_isce2/insar_tops_burst.py "https://github.com/ASFHyP3/hyp3-isce2/blob/main/src/hyp3_isce2/insar_tops_burst.py" ){target=_blank} 
 script. This script follows the ISCE2 InSAR workflow in 
-[topsApp.py](https://github.com/isce-framework/isce2/blob/main/applications/topsApp.py#L982){target=_blank} 
+[`topsApp.py`](https://github.com/isce-framework/isce2/blob/main/applications/topsApp.py#L982 "https://github.com/isce-framework/isce2/blob/main/applications/topsApp.py#L982" ){target=_blank} 
 for the steps `startup` through `geocode`. 
 
 If the reference and secondary SAFE files include multiple bursts, processing is performed on a burst-by-burst 

docs/guides/gunw_product_guide.md

@@ -88,8 +88,8 @@ custom ARIA-S1-GUNW jobs for processing. Once processing is complete, there are
 
 !!! 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 
+    The code used for processing ARIA-S1-GUNW products does not currently support processing SLCs acquired by the 
+    Sentinel-1C platform. Until the code has been updated to use the newest version of ISCE2, users will 
     not be able to submit ARIA-S1-GUNW jobs that include Sentinel-1C acquisitions for On Demand processing.
 
 ### ARIA Frame IDs

docs/guides/insar_product_guide.md

@@ -4,15 +4,15 @@
 # Sentinel-1 InSAR Product Guide
 This document is a guide for users of Interferometric Synthetic Aperture Radar (InSAR) Sentinel-1 products generated by the Alaska Satellite Facility (ASF). Users can request InSAR products [On Demand](https://search.asf.alaska.edu/#/?topic=onDemand "https://search.asf.alaska.edu/#/?topic=onDemand" ){target=_blank} in ASF's [Vertex](https://search.asf.alaska.edu/ "https://search.asf.alaska.edu" ){target=_blank} data portal, or make use of our HyP3 [Python SDK](https://hyp3-docs.asf.alaska.edu/using/sdk/ "https://hyp3-docs.asf.alaska.edu/using/sdk" ){target=_blank} or [API](https://hyp3-docs.asf.alaska.edu/using/api/ "https://hyp3-docs.asf.alaska.edu/using/api" ){target=_blank}. 
 
-This process requires [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} as input. Input pairs can be selected in [Vertex](https://search.asf.alaska.edu/ "https://search.asf.alaska.edu" ){target=_blank} using either the [Baseline Tool](https://docs.asf.alaska.edu/vertex/baseline/ "https://docs.asf.alaska.edu/vertex/baseline/" ){target=_blank} or the [SBAS Tool](https://docs.asf.alaska.edu/vertex/sbas/ "https://docs.asf.alaska.edu/vertex/sbas" ){target=_blank} search interfaces. On Demand InSAR products only include co-polarized interferograms (VV or HH). Cross-polarized interferograms (VH or HV) are not available using this service.
+This process requires [Sentinel-1 IW SLC products](https://sentiwiki.copernicus.eu/web/s1-mission#S1Mission-InterferometricWideSwathS1-Mission-Interferometric-Wide-Swath "https://sentiwiki.copernicus.eu/web/s1-mission#S1Mission-InterferometricWideSwath" ){target=_blank} as input. Input pairs can be selected in [Vertex](https://search.asf.alaska.edu/ "https://search.asf.alaska.edu" ){target=_blank} using either the [Baseline Tool](https://docs.asf.alaska.edu/vertex/baseline/ "https://docs.asf.alaska.edu/vertex/baseline/" ){target=_blank} or the [SBAS Tool](https://docs.asf.alaska.edu/vertex/sbas/ "https://docs.asf.alaska.edu/vertex/sbas" ){target=_blank} search interfaces. On Demand InSAR products only include co-polarized interferograms (VV or HH). Cross-polarized interferograms (VH or HV) are not available using this service.
 
 For a step-by-step tutorial on ordering On-Demand InSAR Products using Vertex, visit our [InSAR On Demand! StoryMap](https://storymaps.arcgis.com/stories/68a8a3253900411185ae9eb6bb5283d3 "InSAR On Demand! https://arcg.is/eiP8G0" ){target=_blank}. To learn more about the files included in the On Demand InSAR product packages and how to work with them, refer to our [Exploring Sentinel-1 InSAR StoryMap](https://storymaps.arcgis.com/stories/8be186e4125741518118d0102e6835e5 "Exploring Sentinel-1 InSAR https://arcg.is/11DaW90" ){target=_blank}.
 
 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 "On-Demand Burst-Based InSAR Now Available" 
 
-    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://sentiwiki.copernicus.eu/web/s1-mission#S1Mission-InterferometricWideSwathS1-Mission-Interferometric-Wide-Swath "https://sentiwiki.copernicus.eu/web/s1-mission#S1Mission-InterferometricWideSwath" ){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 %}
@@ -103,7 +103,7 @@ The InSAR workflow used in HyP3 was developed by ASF using GAMMA software. The s
 Pre-processing steps prepare the SAR images to be used in interferometry. The pre-processing steps include image selection, ingest (including calibration), creation of a suitable DEM, and calculation of the burst overlap.
 
 #### Select an InSAR Pair
-Although it is possible to start from RAW data, Sentinel-1 InSAR processing is typically done using [Interferometric Wide swath Single Look Complex](https://sentinel.esa.int/web/sentinel/user-guides/sentinel-1-sar/acquisition-modes/interferometric-wide-swath "https://sentinel.esa.int/web/sentinel/user-guides/sentinel-1-sar/acquisition-modes/interferometric-wide-swath" ){target=_blank} (IW SLC) data as the input.  This means that the data has been formed into an image through SAR processing, but has not been multi-looked.  
+Although it is possible to start from RAW data, Sentinel-1 InSAR processing is typically done using [Interferometric Wide swath Single Look Complex](https://sentiwiki.copernicus.eu/web/s1-mission#S1Mission-InterferometricWideSwathS1-Mission-Interferometric-Wide-Swath "https://sentiwiki.copernicus.eu/web/s1-mission#S1Mission-InterferometricWideSwath" ){target=_blank} (IW SLC) data as the input.  This means that the data has been formed into an image through SAR processing, but has not been multi-looked.  
 
 The SLC pair is [defined by the user](#ordering-on-demand-insar-products "Jump to Ordering On Demand InSAR Products section of this document"), either through the Vertex interface, or using the HyP3 API or SDK. To ensure consistency, the older SLC image is always used as the reference image, and the younger SLC image is always used as the secondary image. This means that positive values in the resulting unwrapped interferogram represent movement away from the SAR platform and negative values represent movement towards the SAR platform. However, these values are relative to the reference point of the unwrapped interferogram. See the [phase unwrapping section](#reference-point "Jump to Reference Point section of this document") for more details.
 

docs/guides/insar_product_guide_template.md

@@ -1,7 +1,7 @@
 {% block header %}{% endblock %}
 
 ## Introduction
-Interferometric Synthetic Aperture Radar (InSAR) processing uses two SAR images collected over the same area to determine geometric properties of the surface. Missions such as Sentinel-1 are [designed for](https://sentinel.esa.int/web/sentinel/missions/sentinel-1/mission-objectives "https://sentinel.esa.int/web/sentinel/missions/sentinel-1/mission-objectives" ){target=_blank} monitoring surface deformation using InSAR, which is optimal when acquisitions are made from a consistent location in space ([short perpendicular baseline](#baselines "Jump to Baselines section of this document")) over regular time intervals.
+Interferometric Synthetic Aperture Radar (InSAR) processing uses two SAR images collected over the same area to determine geometric properties of the surface. Missions such as Sentinel-1 are [designed for](https://sentiwiki.copernicus.eu/web/s1-applications#S1Applications-OverviewofS1Applications "https://sentiwiki.copernicus.eu/web/s1-applications#S1Applications-OverviewofS1Applications" ){target=_blank} monitoring surface deformation using InSAR, which is optimal when acquisitions are made from a consistent location in space ([short perpendicular baseline](#baselines "Jump to Baselines section of this document")) over regular time intervals.
 
 The phase measurements of two SAR images acquired at different times from the same place in orbit are differenced to detect and quantify surface changes, such as deformation caused by earthquakes, volcanoes, or groundwater subsidence.
 
@@ -64,13 +64,19 @@ For deformation mapping, it is best to minimize the perpendicular baseline whene
 
 ## Ordering On Demand InSAR Products
 
-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}.
+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" 
+!!! tip "InSAR Processing Now Supports Sentinel-1C!" 
 
-    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).
+    GAMMA and ISCE2 software have both been updated to support Sentinel-1C acquisitions as input for InSAR processing. 
+    Users can now use any Sentinel-1 IW SLCs in the archive, including those acquired by Sentinel-1C, as input for 
+    either [On Demand InSAR](insar_product_guide.md) or [On Demand Burst InSAR](burst_insar_product_guide.md) 
+    processing.
 
 ### 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.

docs/guides/opera_rtc_product_guide.md

@@ -498,7 +498,7 @@ mission to full observation capacity [as of March 26, 2025](https://dataspace.co
 The Sentinel-1 satellites each have a 12-day repeat cycle, but when there are two functioning satellites, their orbits 
 are offset 180 degrees so that one or the other will pass over the same location on earth every 6 days. Under this 
 scenario, select areas of interest are imaged with a 6-day interval, as described in the 
-[mission observation scenario](https://sentinel.esa.int/web/sentinel/copernicus/sentinel-1/observation-scenario "https://sentinel.esa.int/web/sentinel/copernicus/sentinel-1/observation-scenario" ){target=_blank}, 
+[mission observation scenario](https://sentinels.copernicus.eu/copernicus/sentinel-1/observation-scenario "https://sentinels.copernicus.eu/copernicus/sentinel-1/observation-scenario" ){target=_blank}, 
 while most landmasses are imaged on a 12-day repeat cycle.
 
 For the time period between when Sentinel-1B stopped acquiring data and Sentinel-1C started acquiring data,