Release v0.10.3

.github/dictionary.txt

@@ -35,6 +35,7 @@ acknowledgement
 adaptively
 adf
 al.
+antimeridian
 AOI
 APD
 APIs
@@ -64,9 +65,14 @@ Aσ
 Backscatter
 backscatter
 bandpass
+base_name
+base_name_mb
+basename
 bbbbbb
 Bekaert
+burst2safe
 Buzzanga
+cccc
 Changelog
 Clauss
 CLI
@@ -107,6 +113,8 @@ Downloader
 downsampled
 DV
 DynamoDB
+E053_1
+E054_1
 Earthdata
 EarthScope
 EDL
@@ -190,6 +198,8 @@ incidenceAngle
 include_dem
 include_rgb
 InSAR
+INSAR_ISCE_BURST
+INSAR_ISCE_MULTI_BURST
 Interferogram
 interferogram
 Interferograms
@@ -224,12 +234,16 @@ L5
 L7
 L8
 L9
+lal_f
 landfast
 landuse
+lau_f
 Liang
 lifecycle
 Log10
 lon
+lonl_f
+lonu_f
 lookAngle
 ls_map.tif
 lv_phi
@@ -256,6 +270,8 @@ multilooking
 Multitemporal
 Muro
 MWE
+N27_3
+N27_8
 NAVD88
 NED1
 NED13
@@ -322,15 +338,20 @@ rgb.kmz
 rgb.png
 rgb.tif
 Ridgecrest
+rrr
 RTC
 Rüetschi
 S1
 S1_136231_IW2_20200604T022312_VV_7C85-BURST
 S1_136231_IW2_20200616T022313_VV_5D11-BURST
+S1_rrr__yyyymmdd_yyyymmdd_pp_INTzz_cccc
 S1A
+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
+S1s
+S1s_rrr_lonl_f_lal_f_lonu_f_lau_f_yyyymmdd_yyyymmdd_pp_INTzz_cccc
 S2
 S3
 SAR
@@ -419,6 +440,7 @@ xx
 Yukon-Kuskokwim
 Yunjun
 yy
+yyyymmdd
 zz
 ⅓
 ½

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.3] 
+
+### Changed
+* Updated the [Burst InSAR Product Guide](docs/guides/burst_insar_product_guide.md) to document multi-burst InSAR (the `INSAR_ISCE_MULTI_BURST` job type)
+
 ## [0.10.2]
 
 ### Added

docs/dems.md

@@ -1,17 +1,17 @@
 # Digital Elevation Models
 Digital Elevation Models are required when processing SAR data to higher-level products, such as the [Radiometric Terrain Correction (RTC)](products.md#rtc "RTC Products" ){target=_blank} and [Interferometric SAR (InSAR)](products.md#insar "InSAR Products" ){target=_blank} products available [On Demand](https://search.asf.alaska.edu/#/?topic=onDemand "Vertex On Demand Documentation" ){target=_blank} from ASF. 
 
-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://spacedata.copernicus.eu/collections/copernicus-digital-elevation-model "Copernicus DEM" ){target=_blank}, we have changed our DEM strategy to leverage a [cloud-hosted copy](https://registry.opendata.aws/copernicus-dem/ "https://registry.opendata.aws/copernicus-dem" ){target=_blank} of the global Copernicus DEM. This is now the only DEM option available for processing RTC and InSAR products.
+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](https://registry.opendata.aws/copernicus-dem/ "https://registry.opendata.aws/copernicus-dem" ){target=_blank} of the global Copernicus DEM. This is now the only DEM option available for processing RTC and InSAR products.
 
 !!! tip "Removal of option to use Legacy DEMs for RTC Processing"
 
-    Users no longer have the option to use legacy DEMs 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://spacedata.copernicus.eu/collections/copernicus-digital-elevation-model "Copernicus DEM" ){target=_blank} is now used for all RTC processing.
+    Users no longer have the option to use legacy DEMs 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://spacedata.copernicus.eu/collections/copernicus-digital-elevation-model "Copernicus DEM" ){target=_blank}, [available on AWS](https://registry.opendata.aws/copernicus-dem/ "Registry of Open Data on AWS - Copernicus DEM" ){target=_blank}. For more information, see the 'Releases' section of [this article](https://spacedata.copernicus.eu/collections/copernicus-digital-elevation-model "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" 
 
-    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, due to the lack of DEM coverage. We now use the Copernicus DEM GLO-90 to fill those gaps. 
+    The 2022 release of 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, 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 On Demand products in these regions, where they were previously unavailable. 
 
@@ -29,7 +29,7 @@ Note that the height values will differ from the original source DEM in all case
 
 ## Copernicus DEM
 
-The [GLO-30 Copernicus DEM](https://spacedata.copernicus.eu/collections/copernicus-digital-elevation-model "Copernicus DEM" ){target=_blank} provides global coverage at 30-m pixel spacing (with the current exception of an area covering Armenia and Azerbaijan, see Figure 2). 
+The [GLO-30 Copernicus DEM](https://dataspace.copernicus.eu/explore-data/data-collections/copernicus-contributing-missions/collections-description/COP-DEM "Copernicus DEM" ){target=_blank} provides global coverage at 30-m pixel spacing (with the current exception of an area covering Armenia and Azerbaijan, see Figure 2). 
 
 When an On Demand job is requested, we download the required DEM tiles from the Copernicus Digital Elevation Model (DEM) GLO-30 Public dataset available in the [Registry of Open Data on AWS](https://registry.opendata.aws/copernicus-dem/ "https://registry.opendata.aws/copernicus-dem" ){target=_blank}, managed by [Sinergise](https://www.sinergise.com/ "https://www.sinergise.com" ){target=_blank}. We mosaic the tiles and reproject them to the appropriate UTM Zone for the location of the SAR granule to be processed, resampling them as required for processing. A geoid correction is applied before it is used for On Demand processing.