HyP3 autoRIFT v0.6.1

Changed

• Upgraded autoRIFT to v1.3.1
  and ISCE2 v2.5.1 built with autoRIFT v1.3.1

HyP3 autoRIFT v0.6.0

Changed

• Upgraded autoRIFT to v1.3.0
  and ISCE2 v2.5.1 built with autoRIFT v1.3.0

HyP3 autoRIFT v0.5.2

Changed

• process.get_lc2_metadata() now fetches STAC metadata from the usgs-landsat S3 bucket instead of the
  https://landsatlook.usgs.gov/ API.

HyP3 autoRIFT v0.5.1

Changed

• Minor updates to the netCDF product metadata
• Pairs that end up having a 0 ROI (no valid data) will not fail at the end of processing,
  but instead will upload a netCDF product that reports 0 ROI

HyP3 autoRIFT v0.5.0

Changed

• autoRIFT products will now be generated with a 120 m pixel spacing instead of 240 m
• hyp3_autorift will directly access Landsat-8 and Sentinel-2 data in the cloud
  instead of downloading the scenes locally
• Upgraded autoRIFT to v1.2.0
  and ISCE2 v2.5.1 built with autoRIFT v1.2.0

Fixed

• Sentinel-2 L1C metadata is generated correctly
• Sentinel-2 search by ESA granule id
• Landsat-8 scene names are no longer truncated in the ITS_LIVE naming schemes

HyP3 autoRIFT v0.4.5

Changed

• Upgraded to hyp3lib v1.6.7 from v1.6.2

HyP3 autoRIFT v0.4.4

Added

• Log message prior to downloading Sentinel-2 and Landsat 8 products

HyP3 autoRIFT v0.4.3

Added

• Ability to specify shapefile used to determine the correct search parameters by geographic location
  • a --parameter-file option has been added to hyp3_autorift
  • a parameter_file keyword argument has been added to hyp3_autorift.process.process
• Ability to specify a preferred product naming scheme
  • a --naming-scheme option has been added to hyp3_autorift
  • a naming_scheme keyword argument has been added to hyp3_autorift.process.process

HyP3 autoRIFT v0.4.2

Fixed

• A partial fix was implemented to correct out of index errors when processing
  optical scenes (typically seen with Landsat-8 pairs) due to calculating different
  overlapping subset sizes when co-registering the images. Currently, only the
  smallest subset size is used, so the bounding box may be 1px too small in x
  and/or y, but there shouldn't be any pixel offsets. Full fix will need to be
  implemented upstream in autoRIFT.

HyP3 autoRIFT v0.4.1

Changed

• hyp3_autorift will determine the polarization of Sentinel-1 scenes based on
  reference scene to allow for VV in addition to HH processing.

Removed

• autorift_proc_pair entrypoint no longer accepts a -p/--polarization option
• hyp3_autorift.process.process no longer accepts a polarization= keyword argument

Fixed

• ValueError exception when processing scenes with short (23 char) Element 84 Sentinel-2 IDs