diff --git a/.github/dictionary.txt b/.github/dictionary.txt index fbbf4001..c1dac48a 100644 --- a/.github/dictionary.txt +++ b/.github/dictionary.txt @@ -365,8 +365,8 @@ SDV Sentinel-1A Sentinel-1B Sentinel-1C +Sentinel-1D Sentinel-2 -sexualized Shapefile shapefile show_submodules diff --git a/.github/workflows/changelog.yml b/.github/workflows/changelog.yml index 556ef1e2..1454dbf6 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.0 + uses: ASFHyP3/actions/.github/workflows/reusable-changelog-check.yml@v0.18.1 diff --git a/.github/workflows/create-jira-issue.yml b/.github/workflows/create-jira-issue.yml index 60ea5edf..5765047a 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.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 }} diff --git a/.github/workflows/labeled-pr.yml b/.github/workflows/labeled-pr.yml index a5d2adbe..ad68c9c3 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.0 + uses: ASFHyP3/actions/.github/workflows/reusable-labeled-pr-check.yml@v0.18.1 diff --git a/.github/workflows/release-template-comment.yml b/.github/workflows/release-template-comment.yml index 701b8448..9175cd8e 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.0 + uses: ASFHyP3/actions/.github/workflows/reusable-release-checklist-comment.yml@v0.18.1 secrets: USER_TOKEN: ${{ secrets.GITHUB_TOKEN }} diff --git a/.github/workflows/release.yml b/.github/workflows/release.yml index 13caf1d7..27e481b2 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.0 + uses: ASFHyP3/actions/.github/workflows/reusable-release.yml@v0.18.1 with: release_prefix: HyP3 Docs secrets: diff --git a/.github/workflows/static-analysis.yml b/.github/workflows/static-analysis.yml index 36490cbb..c700493d 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.0 + uses: ASFHyP3/actions/.github/workflows/reusable-secrets-analysis.yml@v0.18.1 diff --git a/.github/workflows/tag-release.yml b/.github/workflows/tag-release.yml index ad861d47..b34189c4 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.0 + uses: ASFHyP3/actions/.github/workflows/reusable-bump-version.yml@v0.18.1 secrets: USER_TOKEN: ${{ secrets.TOOLS_BOT_PAK }} diff --git a/CHANGELOG.md b/CHANGELOG.md index 0eda7f74..fd93daed 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.5] + +### Changed +* Updated documentation to include information about Sentinel-1C + ## [0.10.4] ### Added diff --git a/docs/guides/burst_insar_product_guide.md b/docs/guides/burst_insar_product_guide.md index a347f05b..6f9e6fdf 100644 --- a/docs/guides/burst_insar_product_guide.md +++ b/docs/guides/burst_insar_product_guide.md @@ -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 %} diff --git a/docs/guides/gunw_product_guide.md b/docs/guides/gunw_product_guide.md index 2c63297e..d58d32a2 100644 --- a/docs/guides/gunw_product_guide.md +++ b/docs/guides/gunw_product_guide.md @@ -8,7 +8,7 @@ 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. @@ -16,6 +16,11 @@ The ARIA project also maintains the [ARIA-tools](https://doi.org/10.1029/2020GL0 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. diff --git a/docs/guides/insar_product_guide.md b/docs/guides/insar_product_guide.md index cb2b29de..d75699a4 100644 --- a/docs/guides/insar_product_guide.md +++ b/docs/guides/insar_product_guide.md @@ -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 diff --git a/docs/guides/insar_product_guide_template.md b/docs/guides/insar_product_guide_template.md index 446fc937..b8cc40b7 100644 --- a/docs/guides/insar_product_guide_template.md +++ b/docs/guides/insar_product_guide_template.md @@ -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. diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index 3c63edd3..1e17e43d 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -5,34 +5,45 @@ SAR datasets inherently contain [geometric and radiometric distortions](#sar-dis ASF's [Sentinel-1 On-Demand RTC](https://search.asf.alaska.edu/#/?topic=onDemand "Vertex On Demand Tutorial" ){target=_blank} products are generated using [GAMMA Software](https://gamma-rs.ch/ "https://gamma-rs.ch" ){target=_blank}. Products are distributed as GeoTIFFs (one for each available polarization) projected to the appropriate UTM Zone for the location of the scene. -A Digital Elevation Model (DEM) is required for radiometric terrain correction. The [GLO-30 Copernicus DEM](https://dataspace.copernicus.eu/explore-data/data-collections/copernicus-contributing-missions/collections-description/COP-DEM "Copernicus DEM" ){target=_blank} is used to process all RTC On Demand products. Refer to the [Digital Elevation Model section](#digital-elevation-models "Jump to the DEM Section of this document" ) for more information. - -!!! tip "Removal of option to use Legacy DEMs for RTC Processing" - - Users no longer have the option to use legacy DEMs (SRTM/NED) when processing RTC jobs [On Demand in Vertex](https://search.asf.alaska.edu/#/?topic=onDemand "Vertex On Demand Documentation" ){target=_blank} or when using the [API](https://hyp3-docs.asf.alaska.edu/using/api/ "https://hyp3-docs.asf.alaska.edu/using/api" ){target=_blank} or [SDK](https://hyp3-docs.asf.alaska.edu/using/sdk/ "https://hyp3-docs.asf.alaska.edu/using/sdk" ){target=_blank}. The [Copernicus GLO-30 DEM](https://dataspace.copernicus.eu/explore-data/data-collections/copernicus-contributing-missions/collections-description/COP-DEM "Copernicus DEM" ){target=_blank} is now used for all RTC processing. - -!!! tip "Coverage gaps in Copernicus DEM GLO-30 filled using GLO-90" - - The Copernicus DEM GLO-30 dataset does not provide coverage over Armenia and Azerbaijan. In the past, we have not supported On Demand product generation over those areas using the Copernicus DEM option. We now use the Copernicus DEM GLO-90 to fill those gaps. - - Users should be aware that 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. +A Digital Elevation Model (DEM) is required for radiometric terrain correction. The [GLO-30 Copernicus DEM](https://dataspace.copernicus.eu/explore-data/data-collections/copernicus-contributing-missions/collections-description/COP-DEM "Copernicus DEM" ){target=_blank} is used to process all RTC On Demand products. Refer to the [Digital Elevation Model section](#digital-elevation-models "Jump to the DEM Section of this document" ) for more information. For a step-by-step tutorial on ordering On-Demand RTC Products using Vertex, visit our [RTC On Demand! StoryMap](https://storymaps.arcgis.com/stories/2ead3222d2294d1fae1d11d3f98d7c35 "RTC On Demand! StoryMap" ){target=_blank}, which also includes links to sample workflows using Sentinel-1 RTC products for GIS applications. -!!! tip "New RTC Pixel Spacing Option Available" - - On Demand Sentinel-1 RTC products can now be processed at [20-m pixel spacing](#pixel-spacing "RTC Pixel Spacing Documentation" ){target=_blank}. Refer to the [Processing Options](#processing-options-and-optional-files "Jump to Processing Options section in document") section for more information. - ## Introduction ### Sentinel-1 Mission -The [Sentinel-1 mission](https://sentinels.copernicus.eu/web/sentinel/missions/sentinel-1 "https://sentinels.copernicus.eu/web/sentinel/missions/sentinel-1" ){target=_blank} collects C-band band SAR from a pair of polar-orbiting satellites launched by the European Space Agency (ESA) as part of the [Copernicus program](https://www.esa.int/Applications/Observing_the_Earth/Copernicus/The_Sentinel_missions "https://www.esa.int/Applications/Observing_the_Earth/Copernicus/The_Sentinel_missions" ){target=_blank}. The Sentinel-1A satellite was launched April 3, 2014, and the Sentinel-1B satellite was launched April 25, 2016. The [Sentinel-1B satellite no longer acquires data](https://www.esa.int/Applications/Observing_the_Earth/Copernicus/Sentinel-1/Mission_ends_for_Copernicus_Sentinel-1B_satellite "https://www.esa.int/Applications/Observing_the_Earth/Copernicus/Sentinel-1/Mission_ends_for_Copernicus_Sentinel-1B_satellite" ){target=_blank} as of December 23, 2021. - -The two Sentinel-1 satellites each have a 12-day repeat cycle, but their orbits are offset 180 degrees so that one or the other will pass over the same location on earth every 6 days. Most areas of the earth will still only have imagery collected every 12 days at best, but while both S1A and S1B were active, Europe and select areas of interest were imaged with a 6-day interval, as described in the [mission observation scenario](https://sentinels.copernicus.eu/web/sentinel/missions/sentinel-1/observation-scenario "https://sentinels.copernicus.eu/web/sentinel/missions/sentinel-1/observation-scenario" ){target=_blank}. -Because this is a polar-orbiting satellite constellation, areas near the poles may have a number of overlapping paths, resulting in even more frequent acquisitions with similar footprints. - -The relatively short interval between acquisitions makes this SAR dataset a very useful tool for monitoring rapid or sudden landscape changes. In addition, SAR can image the earth's surface through cloud or smoke cover and does not require sunlight, so valid imagery can be collected on every pass. This is particularly useful for monitoring conditions during natural disasters such as hurricanes or wildfires, or in areas that are prone to frequent cloud cover. +The +[Sentinel-1 mission](https://sentiwiki.copernicus.eu/web/s1-mission "https://sentiwiki.copernicus.eu/web/s1-mission" ){target=_blank} +collects C-band band SAR from a pair of polar-orbiting satellites launched by the European Space Agency (ESA) as part +of the +[Copernicus program](https://www.esa.int/Applications/Observing_the_Earth/Copernicus/The_Sentinel_missions "https://www.esa.int/Applications/Observing_the_Earth/Copernicus/The_Sentinel_missions" ){target=_blank}. +The Sentinel-1A satellite was launched April 3, 2014, the Sentinel-1B satellite was launched April 25, 2016, +and the Sentinel-1C satellite was launched December 5, 2024. + +Sentinel-1A is still collecting data, but +[Sentinel-1B ended its mission](https://www.esa.int/Applications/Observing_the_Earth/Copernicus/Sentinel-1/Mission_ends_for_Copernicus_Sentinel-1B_satellite "https://www.esa.int/Applications/Observing_the_Earth/Copernicus/Sentinel-1/Mission_ends_for_Copernicus_Sentinel-1B_satellite" ){target=_blank} +on December 23, 2021. Sentinel-1C has now replaced Sentinel-1B in the constellation, returning the Sentinel-1 +mission to full observation capacity [as of March 26, 2025](https://dataspace.copernicus.eu/news/2025-3-25-sentinel-1c-user-data-opening-26th-march "https://dataspace.copernicus.eu/news/2025-3-25-sentinel-1c-user-data-opening-26th-march" ){target=_blank}. + +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}, +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, +coverage was more sparse. Some areas did not have any imagery acquired between December 2021 and April 2025. +Depending on your area of interest, you may have limited data available during that time. For more information, +visit our [Sentinel-1 Mission page](../sentinel1.md). + +Because this is a polar-orbiting satellite constellation, areas near the poles may have a number of overlapping paths, +resulting in even more frequent acquisitions with similar footprints. + +The relatively short interval between acquisitions makes this SAR dataset a very useful tool for monitoring rapid or +sudden landscape changes. In addition, SAR can image the earth's surface through cloud or smoke cover and does not +require sunlight, so valid imagery can be collected on every pass. This is particularly useful for monitoring +conditions during natural disasters such as hurricanes or wildfires, or in areas that are prone to frequent cloud cover. ### SAR Distortions @@ -56,15 +67,11 @@ The RTC product package includes a Layover-Shadow mask (see [Image Files section ## Digital Elevation Models -The quality of the terrain corrections are related to the quality of the digital elevation models (DEMs) used in the process of geometrically and radiometrically correcting the SAR imagery. We use DEMs that are publicly available and have wide-ranging coverage. - -In the past, ASF maintained a collection of DEMs that were pre-processed as appropriate for SAR workflows, and applied a preference hierarchy so that the best available DEM in any given area would be automatically selected for processing. With the public release of the [GLO-30 Copernicus DEM](https://dataspace.copernicus.eu/explore-data/data-collections/copernicus-contributing-missions/collections-description/COP-DEM "Copernicus DEM" ){target=_blank}, we have changed our DEM strategy to leverage a cloud-hosted copy of the global Copernicus DEM. This is now the only DEM available for processing RTC and [InSAR products](insar_product_guide.md "Sentinel-1 InSAR On Demand Product Guide" ){target=_blank}. +The quality of the terrain corrections are related to the quality of the digital elevation models (DEMs) used in the process of geometrically and radiometrically correcting the SAR imagery. -!!! tip "Removal of option to use Legacy DEMs for RTC Processing" - - Users no longer have the option to use legacy DEMs (SRTM/NED) when processing RTC jobs [On Demand in Vertex](https://search.asf.alaska.edu/#/?topic=onDemand "Vertex On Demand Documentation" ){target=_blank} or when using the [API](https://hyp3-docs.asf.alaska.edu/using/api/ "https://hyp3-docs.asf.alaska.edu/using/api" ){target=_blank} or [SDK](https://hyp3-docs.asf.alaska.edu/using/sdk/ "https://hyp3-docs.asf.alaska.edu/using/sdk" ){target=_blank}. The [Copernicus GLO-30 DEM](https://dataspace.copernicus.eu/explore-data/data-collections/copernicus-contributing-missions/collections-description/COP-DEM "Copernicus DEM" ){target=_blank} is now used for all RTC processing. - -We use the 2022 Release of the [Copernicus GLO-30 Public DEM](https://dataspace.copernicus.eu/explore-data/data-collections/copernicus-contributing-missions/collections-description/COP-DEM "Copernicus DEM" ){target=_blank}, [available on AWS](https://registry.opendata.aws/copernicus-dem/ "Registry of Open Data on AWS - Copernicus DEM" ){target=_blank}. +We use the 2022 Release of the +[Copernicus GLO-30 Public DEM](https://dataspace.copernicus.eu/explore-data/data-collections/copernicus-contributing-missions/collections-description/COP-DEM "Copernicus DEM" ){target=_blank}, +[available on AWS](https://registry.opendata.aws/copernicus-dem/ "Registry of Open Data on AWS - Copernicus DEM" ){target=_blank}. !!! tip "Coverage gaps in Copernicus DEM GLO-30 filled using GLO-90" @@ -196,9 +203,9 @@ When DEM matching is applied, the optional steps 2 and 3 are performed. Using th DEM Matching is not always beneficial, however. If the georeferencing of the DEM doesn't match the georeferencing of the Sentinel-1 imagery, DEM matching can result in variable offsets in the output images from one Sentinel-1 acquisition to the next, making it difficult to overlay images for time series analysis. Coregistration also works best when there are distinct topographic features that allow for reliable matching between the SAR image and the DEM. In areas that lack distinctive topographic features, there may also be substantial and inconsistent image offsets. -The orbit files of the Sentinel-1 data are generally quite accurate, and not applying the DEM matching should output files with consistent geolocation. While it may not optimize the RTC calculations, it may be a better option for time series analysis, where having consistent alignment of images from one acquisition to the next is more important than optimizing the backscatter normalization. +If you are interested in optimizing the RTC calculations, and are less concerned about consistent geolocation through time, the DEM Matching option is likely a good choice. ***In cases where consistency is more important than accuracy, consider not applying DEM Matching, or at least testing the outputs to make sure they are suitable for your application.*** -If you are interested in optimizing the RTC calculations, and are less concerned about consistent geolocation through time, the DEM Matching option is likely a good choice. In cases where consistency is more important than accuracy, consider not applying DEM Matching, or at least testing the outputs to make sure they are suitable for your application. +The orbit files of the Sentinel-1 data are generally quite accurate, and not applying the DEM matching should output files with consistent geolocation. While it may not optimize the RTC calculations, it may be a better option for time series analysis, where having consistent alignment of images from one acquisition to the next is more important than optimizing the backscatter normalization. #### Speckle Filter @@ -284,7 +291,7 @@ Example: S1A_IW_20180128T161201_DVP_RTC30_G_gpuned_FD6A | Element | Definition | Example | |----------|------------------------------------------------------------------------------|----------| -| x | Mission: A or B | A | +| x | Sentinel-1 Platform: A, B, or C | A | | yy | Beam Mode | IW | | aaaaaaaa | Start Year-Month-Day | 20180128 | | bbbbbb | Start Hour-Minute-Second | 161201 | @@ -370,13 +377,9 @@ A shapefile indicating the extent of the RTC data coverage is included in the pa ## SAR Scales -!!! tip "On Demand Sentinel-1 RTC Products now available in dB scale" - - Users can now choose to output Sentinel-1 RTC products in decibel (dB) scale. Previously, the only choices for output scale were power and amplitude. The default scale continues to be power. - ### Power Scale -Note that the default output of Sentinel-1 RTC products from HyP3 is in power scale. The values in this scale are generally very close to zero, so the dynamic range of the RTC image can be easily skewed by a few bright scatterers in the image. Power scale is appropriate for statistical analysis of the RTC dataset, but may not always be the best option for data visualization. +The default output of Sentinel-1 RTC products from HyP3 is in power scale. The values in this scale are generally very close to zero, so the dynamic range of the RTC image can be easily skewed by a few bright scatterers in the image. Power scale is appropriate for statistical analysis of the RTC dataset, but may not always be the best option for data visualization. When viewing an RTC image in power scale in a GIS environment, it may appear mostly or all black, and you may need to adjust the stretch to see features in the image. Often applying a stretch of 2 standard deviations, or setting the Min-Max stretch values to 0 and 0.3, will greatly improve the appearance of the image. You can adjust the stretch as desired to display your image to full advantage. Be aware that this does not change the actual pixel values. diff --git a/docs/images/asf_burst_insar_names.png b/docs/images/asf_burst_insar_names.png index 82b24b88..03453a3a 100644 Binary files a/docs/images/asf_burst_insar_names.png and b/docs/images/asf_burst_insar_names.png differ diff --git a/docs/images/asf_insar_names.png b/docs/images/asf_insar_names.png index 3115f595..6eed4e16 100644 Binary files a/docs/images/asf_insar_names.png and b/docs/images/asf_insar_names.png differ diff --git a/docs/sentinel1.md b/docs/sentinel1.md index 4267cb2e..d3a37123 100644 --- a/docs/sentinel1.md +++ b/docs/sentinel1.md @@ -1,25 +1,66 @@ # Sentinel-1 Mission -The Sentinel-1 satellite constellation is part of the Copernicus Earth Observation program, coordinated by the European Space Agency (ESA) on behalf of the European Commission (EC). Sentinel-1 satellites carry C-band Synthetic Aperture Radar (SAR) instruments for global, around-the-clock imagery acquisition, even through cloud cover. +The Sentinel-1 satellite constellation is part of the Copernicus Earth Observation program, coordinated by the European +Space Agency (ESA) on behalf of the European Commission (EC). Sentinel-1 satellites carry C-band Synthetic Aperture +Radar (SAR) instruments for global, around-the-clock imagery acquisition, even through cloud cover. -More information about the mission is available from the [European Space Agency Sentinel-1 Mission website](https://sentinels.copernicus.eu/web/sentinel/missions/sentinel-1 "Sentinel-1 Mission" ){target=_blank}. +The mission was designed to support surface deformation applications, and the stable orbits and consistent +acquisition plans of the Sentinel-1 satellites make it easy to generate high-quality Interferometric SAR (InSAR) +products. These products can measure deformation to the centimeter scale, though the 5.6-cm wavelength +of the C-band SAR sensor limits the viability of InSAR in densely vegetated areas. + +The relatively short interval between acquisitions makes this SAR dataset a very useful tool for monitoring rapid or +sudden landscape changes. In addition, SAR can image the earth's surface through cloud or smoke cover and does not +require sunlight, so valid imagery can be collected on every pass. This is particularly useful for monitoring +conditions during natural disasters such as hurricanes or wildfires, or in areas that are prone to frequent cloud cover. + +More information about the mission is available from the [European Space Agency Sentinel-1 Mission website](https://sentiwiki.copernicus.eu/web/s1-mission "Sentinel-1 Mission" ){target=_blank}. ## The Sentinel-1 Constellation -The Sentinel-1A satellite was launched April 3, 2014, and the Sentinel-1B satellite was launched April 25, 2016. The satellites each have a 12-day repeat cycle and use the same orbit pattern, but are offset 180 degrees to allow repeat passes every 6 days. +The Sentinel-1 mission was designed to be a two-satellite constellation, though there have been periods when +only one satellite has been available for image acquisition. -While both satellites were actively imaging, most global landmasses were imaged every 12 days. Some areas of particular interest to the EC, including Europe and areas undergoing rapid changes due to uplift or subsidence activity, were imaged every 6 days. Refer to the [Sentinel-1 Observation Scenario](https://sentinel.esa.int/web/sentinel/missions/sentinel-1/observation-scenario "https://sentinel.esa.int/web/sentinel/missions/sentinel-1/observation-scenario" ){target=_blank} for more information on the acquisition plan used while both satellites were actively acquiring data. +- Sentinel-1A was launched April 3, 2014, and is still actively acquiring imagery. +- Sentinel-1B was launched April 25, 2016, but [ended its mission](https://www.esa.int/Applications/Observing_the_Earth/Copernicus/Sentinel-1/Mission_ends_for_Copernicus_Sentinel-1B_satellite "https://www.esa.int/Applications/Observing_the_Earth/Copernicus/Sentinel-1/Mission_ends_for_Copernicus_Sentinel-1B_satellite" ){target=_blank} on December 23, 2021. +- Sentinel-1C was launched December 5, 2024, replacing Sentinel-1B in the constellation, and + [has been acquiring imagery regularly since March 26, 2025](https://dataspace.copernicus.eu/news/2025-3-25-sentinel-1c-user-data-opening-26th-march "https://dataspace.copernicus.eu/news/2025-3-25-sentinel-1c-user-data-opening-26th-march" ){target=_blank}. -### Mission Ends for Sentinel-1B +Each Sentinel-1 satellite has a 12-day repeat cycle, and they all use the same orbit pattern. When there are two active +sensors in the constellation, their orbits are offset 180 degrees to allow repeat passes every 6 days. In this +scenario, most global landmasses are imaged every 12 days. However, some areas of particular interest to the EC, +including Europe and areas undergoing rapid changes due to uplift or subsidence activity, are imaged every 6 days. -!!! tip "Sentinel-1B no longer acquiring data" +Refer to the +[Sentinel-1 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} +for more information on the acquisition plans that have been used to meet mission goals under different +constellation configurations. - **As of December 23, 2021, Sentinel-1B is no longer able to acquire data.** An anomaly related to the power supply cannot be repaired, and the satellite will be decommissioned. Refer to [ESA's documentation of the end of the Sentinel-1B mission](https://www.esa.int/Applications/Observing_the_Earth/Copernicus/Sentinel-1/Mission_ends_for_Copernicus_Sentinel-1B_satellite "Mission Ends for Copernicus Sentinel-1B Satellite" ){target=_blank} for more information. +## Transition from Sentinel-1B to Sentinel-1C -While Sentinel-1A is still healthy, the loss of Sentinel-1B has resulted in a significant reduction in the spatial and temporal coverage of the Sentinel-1 mission. Refer to [this article by Iain Woodhouse](https://www.earthblox.io/blog/the-impact-of-the-sentinel-1b-failure-and-looking-forward-to-sentinel-1c "The impact of the Sentinel-1B failure and looking forward to Sentinel-1C" ){target=_blank} for an illustration of the global impact of the Sentinel-1B failure. The image below illustrates a gap in the acquisitions over Alaska. This area of the Yukon-Kuskokwim Delta did not have a Sentinel-1 acquisition during the summer of 2022 until August 15. +As of December 23, 2021, Sentinel-1B was no longer able to acquire data. An anomaly related to the power supply +could not be repaired, and the satellite has been decommissioned. Refer to +[ESA documentation of the end of the Sentinel-1B mission](https://www.esa.int/Applications/Observing_the_Earth/Copernicus/Sentinel-1/Mission_ends_for_Copernicus_Sentinel-1B_satellite "Mission Ends for Copernicus Sentinel-1B Satellite" ){target=_blank} +for more information. + +The loss of Sentinel-1B resulted in a significant reduction in the spatial and temporal coverage of the Sentinel-1 +mission. Refer to +[this article by Iain Woodhouse](https://www.earthblox.io/blog/the-impact-of-the-sentinel-1b-failure-and-looking-forward-to-sentinel-1c "The impact of the Sentinel-1B failure and looking forward to Sentinel-1C" ){target=_blank} +for an illustration of the global impact of the Sentinel-1B failure. The image below illustrates a gap in the +acquisitions over Alaska. This area of the Yukon-Kuskokwim Delta did not have a Sentinel-1 acquisition during +the summer of 2022 until August 15. ![Y-K Delta Gap](images/s1b_hole_alaska.png "Lack of acquisitions over the Yukon-Kuskokwim Delta, Alaska") -The good news is that Sentinel-1C is waiting in the wings, and launch is anticipated in 2023. This satellite will replace Sentinel-1B, but until that is in place, there will continue to be reduced coverage. +The gaps in coverage were particularly noticeable the first few months after Sentinel-1B lost power, but some areas +continued to have little or no coverage in the period from December 2021 to April 2025, when Sentinel-1C began +acquiring data regularly. Keep this in mind as you search for data in your area of interest. If there are fewer +results than you would expect, you can +[download acquisition plans for the mission from ESA](https://sentinel.esa.int/web/sentinel/copernicus/sentinel-1/acquisition-plans "Sentinel-1 Acquisition Plans" ){target=_blank} to view the acquisition plan for your area and time period of interest. + +## The Future of the Sentinel-1 Mission -The gaps in coverage were particularly noticeable the first few months after Sentinel-1B lost power, but there are still some areas with little to no coverage. Keep this in mind as you search for data in your area of interest. If there are fewer results than you would expect, you can [download current acquisition plans for the mission from ESA](https://sentinels.copernicus.eu/web/sentinel/missions/sentinel-1/observation-scenario/acquisition-segments "Sentinel-1 Acquisition Segments" ){target=_blank} to view the acquisition plan for your area and time period of interest. +Now that Sentinel-1C has replaced Sentinel-1B, and Sentinel-1A continues to acquire data, the constellation has +returned to the same observation scenario used when both Sentinel-1A and Sentinel-1B were active. The +Sentinel-1A platform is approaching the end of its mission, however, and +[plans are underway to launch Sentinel-1D to replace it](https://www.esa.int/Applications/Observing_the_Earth/Copernicus/Sentinel-1/Ariane_6_to_take_Sentinel-1D_into_orbit ){target=_blank}.