Skip to content

May 2022

Compare
Choose a tag to compare
@TomAugspurger TomAugspurger released this 20 May 21:02
· 5 commits to main since this release
26dfb95

We're pleased to announce our May 2022 release! This release includes several performance improvements, API enhancements, and many new datasets.

Highlights

  • Improved performance and scalability of our STAC API. Requests to our STAC API, including searches, will return faster and scale to larger concurrent loads. See the pgstac 0.5 and 0.6 release notes for more.
  • The Explorer now includes the ability to pin layers, allowing you to compare multiple queries. See working with multiple layers for more.
  • Many new datasets are available through our catalog. See the datasets section below for more.

New datasets

This release includes many new datasets. Each of these links to the dataset details page, which includes an example notebook.

API updates

STAC API

  • Updated the STAC API to v1.0.0-rc.1
  • Initial support for queryables in the STAC API. See Sentinel-2-l2a for an example. Additional queryables and more metadata description in coming releases.
  • Scalability and performance improvements.

Data API

  • Upgrades to pgstac-titiler 0.1.0a7
  • Scalability and performance improvements.

Documentation and Tutorials

In addition to the dataset examples, we have several new tutorials going in-depth on a specific topic.

Hub environments

Changes

Changes in behavior that existing users may need to account for:

  • The landsat-8-c2-l2 collection is deprecated. This collection only contained Landsat 8 images from Collection 2. Please use the landsat-c2-l2 collection, which now has data from Landsat 4 - 9 spanning all the way back to 1982. Existing workflows using landsat-8-c2-l2 items should be able to switch to landsat-c2-l2 without disruption. landsat-8-c2-l2 is removed from the website but remains in the STAC API; however it will no longer be updated with new items.
  • Some queries on date ranges may return different results with this new release. This is due to corrections in the date range logic in our underlying metadata store, PgSTAC. For Items with all of a start_datetime, end_datetime, and datetime property, only the start_datetime and end_datetime will be considered, whereas previously datetime was the target of the search.