From ca68dd56a974b23e1950107d7fc92b22bd554b6e Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 1 May 2023 12:56:48 -0800 Subject: [PATCH 01/15] update Pixel Spacing section to accommodate the 20-m option --- docs/guides/rtc_product_guide.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index 3b7140aa..5d2684d2 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -109,13 +109,13 @@ Figure 4 shows the coverage of the various legacy DEM sources. !!! important "On Demand Sentinel-1 RTC now available at 10-m pixel spacing" - There is now a pixel spacing processing option available for Sentinel-1 RTC products. Users can choose to output the RTC products at a pixel spacing of either 30 meters or 10 meters. + There are now three pixel spacing options available for On Demand Sentinel-1 RTC products. Users can choose to output the RTC products at a pixel spacing of 30, 20, or 10 meters. -RTC products can be output either at 30-meter or 10-meter pixel spacing. In most cases, the input SAR image has a higher resolution than either of the RTC outputs. The 10-m RTC product will be closer to the resolution of the source SAR granule, but the 30-m RTC product has a much smaller file size. +RTC products can be output at 30-meter, 20-meter, or 10-meter pixel spacing. In most cases, the input SAR image has a resolution closer to the 10-m products, while the Copernicus DEM (used by default for RTC processing) has a pixel spacing of 30 m. The 10-m RTC product will be closer to the resolution of the source SAR granule, but the 30-m RTC product has a much smaller file size. The 20-m product may be a good tradeoff between the two. -It is *much* faster to process and analyze 30-m RTC products, so it's a good idea to start with the coarser resolution option if possible. If the 30-m pixel spacing is not sufficient for your use case, try the larger 10-m RTC products. +It is *much* faster to process and analyze 30-m RTC products, so it's a good idea to start with the coarser resolution option if possible. If the 30-m pixel spacing is not sufficient for your use case, try the larger 20-m RTC products. If even more detail is required, the 10-m products may be the best. -Keep in mind that the same DEM is used for processing both the 10-m and 30-m RTC products. By default, the DEM is the Copernicus Global DEM with a pixel spacing of 30 meters. The DEM is resampled to a pixel spacing of 10 meters when used for processing the 10-m RTC products, and the output DEM included in the 10-m RTC product package has a pixel spacing of 10 meters to match the output RTC product. *This does not indicate that the source DEM used for the 10-m products is of higher resolution.* +Keep in mind that the same DEM is used for processing both the RTC products, regardless of the output pixel spacing. By default, the DEM is the Copernicus Global DEM with a pixel spacing of 30 meters. The DEM is resampled to a pixel spacing of 10 meters when used for processing the 10-m RTC products, and the output DEM included in the 10-m RTC product package has a pixel spacing of 10 meters to match the output RTC product. The same is true for the 20-m products; the DEM is resampled to a pixel spacing of 20 meters, and the resampled version is included in the product package. *This does not indicate that the source DEM used for the 10-m or 20-m products is of higher resolution.* ## Processing Options and Optional Files From 49e6913b3531adac3240022826dd904debe5a21e Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 1 May 2023 13:03:26 -0800 Subject: [PATCH 02/15] update the Processing Options Pixel Spacing section to accommodate the 20-m option --- docs/guides/rtc_product_guide.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index 5d2684d2..5b0c2237 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -156,11 +156,13 @@ The **scale** option allows users to choose the scale of the output backscatter #### Pixel Spacing -The **resolution** parameter sets the pixel spacing of the output images. Users have the option to set a pixel spacing of either 30 meters or 10 meters. +The **resolution** parameter sets the pixel spacing of the output images. Users have the option to set a pixel spacing of 30, 20, or 10 meters. -The 30-m product has a much smaller file size, and is easier to work with for large areas of interest. The 10-m product provides much more detail of surface features, but is a much larger file. +- The 30-m product has a much smaller file size, and is easier to work with for large areas of interest. It generally aligns with the native resolution of the DEM used for RTC processing. +- The 10-m product provides much more detail of surface features, and is closer to the native resolution of the source Sentinel-1 data. The file sizes are also much larger than those of the 30-m products. +- The 20-m product may be a good compromise between the native resolution of the source SAR imagery and the source DEM, as well as having a file size intermediate to the 10-m and 30-m products. -Refer to the [Pixel Spacing](#pixel-spacing "Jump to Pixel Spacing section in document") section for more information. Note that the source Sentinel-1 imagery and the DEM are the same for both of these options. +Refer to the [Pixel Spacing](#pixel-spacing "Jump to Pixel Spacing section in document") section for more information. Note that the source Sentinel-1 imagery and the source DEM used for RTC processing are the same regardless of the option selected for the output pixel spacing. #### DEM Name From c8bae5ec155c44a531b3eb26c74b69111ae249c6 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 1 May 2023 13:04:46 -0800 Subject: [PATCH 03/15] update the RTC processing options table to include 20m pixel spacing --- docs/guides/rtc_product_guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index 5b0c2237..378782bc 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -123,11 +123,11 @@ There are a number of options users can set when ordering RTC On Demand products Table 2 lists all of the options as displayed in the Vertex user interface and the HyP3 API, and the [Processing Options](#processing-options "Jump to Processing Options section in document") and [Optional Files](#optional-files "Jump to Optional Files section in document") sections provide more information about each option. -| Option Name in Vertex | Option Name in HyP3 API/SDK | Possible Values | Default | Description | +| Option Name in Vertex | Option Name in HyP3 API/SDK | Possible Values | Default | Description | |-----------------------------|-----------------------------|-----------------------------|------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| | Radiometry | radiometry | (gamma0, sigma0) | gamma0 | Backscatter coefficient normalization, either by ground area (sigma0) or illuminated area projected into the look direction (gamma0) | | Scale | scale | (power, decibel, amplitude) | power | Scale of output backscatter values | -| Pixel Spacing | resolution | (10.0, 30.0) | 30.0 | Product pixel spacing in meters | +| Pixel Spacing | resolution | (10.0, 20.0, 30.0) | 30.0 | Product pixel spacing in meters | | DEM Name | dem_name | (copernicus, legacy) | copernicus | Name of the DEM to use for processing: _copernicus_ will use the Copernicus GLO-30 Public DEM, _legacy_ will use the DEM with the best coverage from ASF's legacy SRTM/NED datasets | | Apply DEM Matching | dem_matching | (true, false) | false | Coregisters SAR data to the DEM, rather than using dead reckoning based on orbit files | | Apply Speckle Filter | speckle_filter | (true, false) | false | Apply an Enhanced Lee speckle filter | From 13d1496405de4bb64db58ccf8fbdd0c5f76008ab Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 1 May 2023 13:06:45 -0800 Subject: [PATCH 04/15] update changelog --- CHANGELOG.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/CHANGELOG.md b/CHANGELOG.md index efcd2ce0..0ea7940e 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.3.67] + +### Changed +* Updated the [RTC Product Guide](docs/guides/rtc_product_guide.md) to accommodate the 20-m option for pixel spacing + ## [0.3.66] ### Added From b125e20072f3c50db1752ecac022d1857f7a1bcd Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 1 May 2023 13:23:43 -0800 Subject: [PATCH 05/15] update pixel spacing info box header --- docs/guides/rtc_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index 378782bc..8dd4ba7c 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -107,7 +107,7 @@ Figure 4 shows the coverage of the various legacy DEM sources. ## Pixel Spacing -!!! important "On Demand Sentinel-1 RTC now available at 10-m pixel spacing" +!!! important "On Demand Sentinel-1 RTC now available at 10-m and 20-m pixel spacing" There are now three pixel spacing options available for On Demand Sentinel-1 RTC products. Users can choose to output the RTC products at a pixel spacing of 30, 20, or 10 meters. From 133711151bba350942a9a56dbad8553577f71dce Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 1 May 2023 13:24:08 -0800 Subject: [PATCH 06/15] update new options info box to focus on 20-m products --- docs/guides/rtc_product_guide.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index 8dd4ba7c..73aa6fd6 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -9,9 +9,9 @@ A [Digital Elevation Model (DEM)](#digital-elevation-models "Jump to DEM Section 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. -!!! important "New RTC Processing Options Available" +!!! important "New RTC Pixel Spacing Option Available" - On Demand Sentinel-1 RTC products can now be processed at [10-m pixel spacing](#pixel-spacing "RTC Pixel Spacing Documentation" ){target=_blank}, and can be output in [decibel (dB) scale](#sar-scales "SAR Scales Documentation" ){target=_blank}. Refer to the [Processing Options](#processing-options "Jump to Processing Options section in document") section for more information. + 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 From c3bb110a9241062a855f69fcb28ba9169bca2404 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Mon, 1 May 2023 15:46:51 -0800 Subject: [PATCH 07/15] use US convention for tradeoff --- docs/guides/rtc_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index 73aa6fd6..62ef04cf 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -111,7 +111,7 @@ Figure 4 shows the coverage of the various legacy DEM sources. There are now three pixel spacing options available for On Demand Sentinel-1 RTC products. Users can choose to output the RTC products at a pixel spacing of 30, 20, or 10 meters. -RTC products can be output at 30-meter, 20-meter, or 10-meter pixel spacing. In most cases, the input SAR image has a resolution closer to the 10-m products, while the Copernicus DEM (used by default for RTC processing) has a pixel spacing of 30 m. The 10-m RTC product will be closer to the resolution of the source SAR granule, but the 30-m RTC product has a much smaller file size. The 20-m product may be a good tradeoff between the two. +RTC products can be output at 30-meter, 20-meter, or 10-meter pixel spacing. In most cases, the input SAR image has a resolution closer to the 10-m products, while the Copernicus DEM (used by default for RTC processing) has a pixel spacing of 30 m. The 10-m RTC product will be closer to the resolution of the source SAR granule, but the 30-m RTC product has a much smaller file size. The 20-m product may be a good trade-off between the two. It is *much* faster to process and analyze 30-m RTC products, so it's a good idea to start with the coarser resolution option if possible. If the 30-m pixel spacing is not sufficient for your use case, try the larger 20-m RTC products. If even more detail is required, the 10-m products may be the best. From 21f663afe28969356b1c00b07fb6e1c31bd16b07 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Thu, 4 May 2023 14:39:08 -0800 Subject: [PATCH 08/15] edit pixel spacing guidance section --- docs/guides/rtc_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index 62ef04cf..f626b184 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -113,7 +113,7 @@ Figure 4 shows the coverage of the various legacy DEM sources. RTC products can be output at 30-meter, 20-meter, or 10-meter pixel spacing. In most cases, the input SAR image has a resolution closer to the 10-m products, while the Copernicus DEM (used by default for RTC processing) has a pixel spacing of 30 m. The 10-m RTC product will be closer to the resolution of the source SAR granule, but the 30-m RTC product has a much smaller file size. The 20-m product may be a good trade-off between the two. -It is *much* faster to process and analyze 30-m RTC products, so it's a good idea to start with the coarser resolution option if possible. If the 30-m pixel spacing is not sufficient for your use case, try the larger 20-m RTC products. If even more detail is required, the 10-m products may be the best. +It is *much* faster to process, download and analyze 30-m RTC products than the 10-m products, so it's a good idea to start with the coarser resolution option if possible. If the 30-m pixel spacing is not sufficient for your use case, try the larger 20-m RTC products. If even more detail is required, the 10-m products may be the best option. Keep in mind that the same DEM is used for processing both the RTC products, regardless of the output pixel spacing. By default, the DEM is the Copernicus Global DEM with a pixel spacing of 30 meters. The DEM is resampled to a pixel spacing of 10 meters when used for processing the 10-m RTC products, and the output DEM included in the 10-m RTC product package has a pixel spacing of 10 meters to match the output RTC product. The same is true for the 20-m products; the DEM is resampled to a pixel spacing of 20 meters, and the resampled version is included in the product package. *This does not indicate that the source DEM used for the 10-m or 20-m products is of higher resolution.* From dc57c0c07e73e33e6d4b8bd198d6d923b0755beb Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Thu, 4 May 2023 14:40:57 -0800 Subject: [PATCH 09/15] edit pixel spacing guidance section --- docs/guides/rtc_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index f626b184..f95d6e1a 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -113,7 +113,7 @@ Figure 4 shows the coverage of the various legacy DEM sources. RTC products can be output at 30-meter, 20-meter, or 10-meter pixel spacing. In most cases, the input SAR image has a resolution closer to the 10-m products, while the Copernicus DEM (used by default for RTC processing) has a pixel spacing of 30 m. The 10-m RTC product will be closer to the resolution of the source SAR granule, but the 30-m RTC product has a much smaller file size. The 20-m product may be a good trade-off between the two. -It is *much* faster to process, download and analyze 30-m RTC products than the 10-m products, so it's a good idea to start with the coarser resolution option if possible. If the 30-m pixel spacing is not sufficient for your use case, try the larger 20-m RTC products. If even more detail is required, the 10-m products may be the best option. +It is *much* faster to process, download and analyze 30-m RTC products than 10-m products, so it's a good idea to start with the coarser resolution option if possible. If the 30-m pixel spacing is not sufficient for your use case, try the larger 20-m RTC products. If even more detail is required, the 10-m products may be the best option. Keep in mind that the same DEM is used for processing both the RTC products, regardless of the output pixel spacing. By default, the DEM is the Copernicus Global DEM with a pixel spacing of 30 meters. The DEM is resampled to a pixel spacing of 10 meters when used for processing the 10-m RTC products, and the output DEM included in the 10-m RTC product package has a pixel spacing of 10 meters to match the output RTC product. The same is true for the 20-m products; the DEM is resampled to a pixel spacing of 20 meters, and the resampled version is included in the product package. *This does not indicate that the source DEM used for the 10-m or 20-m products is of higher resolution.* From 9119183b1712d7b50d70ec1c3a9123ffa604c3e2 Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Thu, 4 May 2023 14:41:43 -0800 Subject: [PATCH 10/15] edit pixel spacing guidance section --- docs/guides/rtc_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index f95d6e1a..7549fb47 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -113,7 +113,7 @@ Figure 4 shows the coverage of the various legacy DEM sources. RTC products can be output at 30-meter, 20-meter, or 10-meter pixel spacing. In most cases, the input SAR image has a resolution closer to the 10-m products, while the Copernicus DEM (used by default for RTC processing) has a pixel spacing of 30 m. The 10-m RTC product will be closer to the resolution of the source SAR granule, but the 30-m RTC product has a much smaller file size. The 20-m product may be a good trade-off between the two. -It is *much* faster to process, download and analyze 30-m RTC products than 10-m products, so it's a good idea to start with the coarser resolution option if possible. If the 30-m pixel spacing is not sufficient for your use case, try the larger 20-m RTC products. If even more detail is required, the 10-m products may be the best option. +It is *much* faster to process, download and analyze 30-m RTC products than 10-m products, so it's a good idea to start with the coarser resolution option if possible. If the 30-m pixel spacing is not sufficient for your use case, try the 20-m RTC products. If even more detail is required, the 10-m products may be the best option. Keep in mind that the same DEM is used for processing both the RTC products, regardless of the output pixel spacing. By default, the DEM is the Copernicus Global DEM with a pixel spacing of 30 meters. The DEM is resampled to a pixel spacing of 10 meters when used for processing the 10-m RTC products, and the output DEM included in the 10-m RTC product package has a pixel spacing of 10 meters to match the output RTC product. The same is true for the 20-m products; the DEM is resampled to a pixel spacing of 20 meters, and the resampled version is included in the product package. *This does not indicate that the source DEM used for the 10-m or 20-m products is of higher resolution.* From eb2fdf5f5c77599f43253c5fd68daa4a5a8e9e74 Mon Sep 17 00:00:00 2001 From: Andrew Johnston Date: Thu, 4 May 2023 15:20:55 -0800 Subject: [PATCH 11/15] add release checklist github action --- .github/PULL_REQUEST_TEMPLATE/release.md | 37 ------------------- .github/pull_request_template.md | 8 ---- .../workflows/release-template-comment.yml | 12 ++++++ 3 files changed, 12 insertions(+), 45 deletions(-) delete mode 100644 .github/PULL_REQUEST_TEMPLATE/release.md delete mode 100644 .github/pull_request_template.md create mode 100644 .github/workflows/release-template-comment.yml diff --git a/.github/PULL_REQUEST_TEMPLATE/release.md b/.github/PULL_REQUEST_TEMPLATE/release.md deleted file mode 100644 index da7cffe1..00000000 --- a/.github/PULL_REQUEST_TEMPLATE/release.md +++ /dev/null @@ -1,37 +0,0 @@ -## Description of this release - - - - - -### Developer checklist - -- [ ] Assigned a reviewer - -- [ ] Indicated the level of changes to this package by affixing one of these labels: - * major -- Major changes to the API that may break current workflows - * minor -- Minor changes to the API that do not break current workflows - * patch -- Patches and bugfixes for the current version that do not break current workflows - * bumpless -- Changes to documentation, CI/CD pipelines, etc. that don't affect the software's version - -- [ ] (If applicable) Updated the dependencies and indicated any downstream changes that are required - -- [ ] Updated `CHANGELOG.md` -- [ ] Added/updated documentation for these changes -- [ ] Added/updated tests for these changes - -### Reviewer checklist - -- [ ] Have all dependencies been updated? -- [ ] Is the level of changes labeled appropriately? -- [ ] Are all the changes described appropriately in `CHANGELOG.md`? -- [ ] Has the documentation been adequately updated? -- [ ] Are the tests adequate? diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md deleted file mode 100644 index 555cd6e0..00000000 --- a/.github/pull_request_template.md +++ /dev/null @@ -1,8 +0,0 @@ - \ No newline at end of file diff --git a/.github/workflows/release-template-comment.yml b/.github/workflows/release-template-comment.yml new file mode 100644 index 00000000..c913408f --- /dev/null +++ b/.github/workflows/release-template-comment.yml @@ -0,0 +1,12 @@ +on: + pull_request: + types: + - opened + branches: + - main + +jobs: + call-release-workflow: + uses: ASFHyP3/actions/.github/workflows/reusable-release-checklist-comment.yml@v0.7.1 + secrets: + USER_TOKEN: ${{ secrets.GITHUB_TOKEN }} From dab4688c18922bf86d627d7322c2570dd7340f82 Mon Sep 17 00:00:00 2001 From: Andrew Johnston Date: Thu, 4 May 2023 15:49:08 -0800 Subject: [PATCH 12/15] Update .github/workflows/release-template-comment.yml Co-authored-by: Joseph H Kennedy --- .github/workflows/release-template-comment.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/release-template-comment.yml b/.github/workflows/release-template-comment.yml index c913408f..29e77ad7 100644 --- a/.github/workflows/release-template-comment.yml +++ b/.github/workflows/release-template-comment.yml @@ -6,7 +6,7 @@ on: - main jobs: - call-release-workflow: + call-release-checklist-workflow: uses: ASFHyP3/actions/.github/workflows/reusable-release-checklist-comment.yml@v0.7.1 secrets: USER_TOKEN: ${{ secrets.GITHUB_TOKEN }} From b1c2a5efae57bda8ebd0353d7dbeee13328fe73c Mon Sep 17 00:00:00 2001 From: hjkristenson Date: Thu, 4 May 2023 16:21:26 -0800 Subject: [PATCH 13/15] add notes that the 20-m product is not yet in Vertex --- docs/guides/rtc_product_guide.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index 7549fb47..c6525473 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -13,6 +13,8 @@ For a step-by-step tutorial on ordering On-Demand RTC Products using Vertex, vis 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. + This option is currently available in the HyP3 API and SDK - coming soon in Vertex! + ## Introduction ### Sentinel-1 Mission @@ -111,6 +113,8 @@ Figure 4 shows the coverage of the various legacy DEM sources. There are now three pixel spacing options available for On Demand Sentinel-1 RTC products. Users can choose to output the RTC products at a pixel spacing of 30, 20, or 10 meters. + The 20-m pixel spacing option is currently only available through the HyP3 API or SDK, but is coming soon to Vertex! + RTC products can be output at 30-meter, 20-meter, or 10-meter pixel spacing. In most cases, the input SAR image has a resolution closer to the 10-m products, while the Copernicus DEM (used by default for RTC processing) has a pixel spacing of 30 m. The 10-m RTC product will be closer to the resolution of the source SAR granule, but the 30-m RTC product has a much smaller file size. The 20-m product may be a good trade-off between the two. It is *much* faster to process, download and analyze 30-m RTC products than 10-m products, so it's a good idea to start with the coarser resolution option if possible. If the 30-m pixel spacing is not sufficient for your use case, try the 20-m RTC products. If even more detail is required, the 10-m products may be the best option. From 029d3c1f41f130f48d3bedba12c3096f3fc7ca82 Mon Sep 17 00:00:00 2001 From: Heidi Kristenson <61886203+hjkristenson@users.noreply.github.com> Date: Thu, 4 May 2023 16:26:54 -0800 Subject: [PATCH 14/15] text adjustment Co-authored-by: Joseph H Kennedy --- docs/guides/rtc_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index c6525473..393c049e 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -13,7 +13,7 @@ For a step-by-step tutorial on ordering On-Demand RTC Products using Vertex, vis 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. - This option is currently available in the HyP3 API and SDK - coming soon in Vertex! + This option is currently available in the HyP3 API and SDK - coming soon to Vertex! ## Introduction From 7286f783e0f8cf341110fd4567405020d804db35 Mon Sep 17 00:00:00 2001 From: Andrew Johnston Date: Thu, 4 May 2023 17:34:27 -0800 Subject: [PATCH 15/15] fix typo in pixel spacing section of rtc product guide --- docs/guides/rtc_product_guide.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/rtc_product_guide.md b/docs/guides/rtc_product_guide.md index 393c049e..f6b8a2cf 100644 --- a/docs/guides/rtc_product_guide.md +++ b/docs/guides/rtc_product_guide.md @@ -119,7 +119,7 @@ RTC products can be output at 30-meter, 20-meter, or 10-meter pixel spacing. In It is *much* faster to process, download and analyze 30-m RTC products than 10-m products, so it's a good idea to start with the coarser resolution option if possible. If the 30-m pixel spacing is not sufficient for your use case, try the 20-m RTC products. If even more detail is required, the 10-m products may be the best option. -Keep in mind that the same DEM is used for processing both the RTC products, regardless of the output pixel spacing. By default, the DEM is the Copernicus Global DEM with a pixel spacing of 30 meters. The DEM is resampled to a pixel spacing of 10 meters when used for processing the 10-m RTC products, and the output DEM included in the 10-m RTC product package has a pixel spacing of 10 meters to match the output RTC product. The same is true for the 20-m products; the DEM is resampled to a pixel spacing of 20 meters, and the resampled version is included in the product package. *This does not indicate that the source DEM used for the 10-m or 20-m products is of higher resolution.* +Keep in mind that the same DEM is used for processing the RTC products, regardless of the output pixel spacing. By default, the DEM is the Copernicus Global DEM with a pixel spacing of 30 meters. The DEM is resampled to a pixel spacing of 10 meters when used for processing the 10-m RTC products, and the output DEM included in the 10-m RTC product package has a pixel spacing of 10 meters to match the output RTC product. The same is true for the 20-m products; the DEM is resampled to a pixel spacing of 20 meters, and the resampled version is included in the product package. *This does not indicate that the source DEM used for the 10-m or 20-m products is of higher resolution.* ## Processing Options and Optional Files