stac-utils / pystac

Python library for working with any SpatioTemporal Asset Catalog (STAC)

Home Page:https://pystac.readthedocs.io

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Normalize extension implementations to follow best practices

gadomski opened this issue · comments

Extensions use differerent patterns and may not be fully correct -- we should make sure all extensions in this repo are up to the latest best practices.

Tasks

  • Build the extensions list below
  • Define "best practices"
  • Audit each extension
  • Close all issues for specific extension versions (noted below)

Best practices

  • Includes tests for all published versions
  • Implements migration for all v1-and-beyond versions

Extensions list

  • Classification
    • v1.0.0
    • v1.1.0
  • Datacube
    • v1.0.0
    • v2.0.0
    • v2.1.0: #856
    • v2.2.0: #856
  • Eo
    • v1.0.0
    • v1.1.0
  • File
  • Grid
    • v1.0.0
    • v1.1.0
  • Item Assets
    • v1.0.0
  • Label: #1249
    • v1.0.0
    • v1.0.1
  • Mgrs
    • v1.0.0
  • Pointcloud
    • v1.0.0
  • Projection
    • v1.0.0
    • v1.1.0
  • Raster
    • v1.0.0
    • v1.1.0
  • Sar
    • v1.0.0
  • Sat
    • v1.0.0
  • Scientific
    • v1.0.0
  • Storage
    • v1.0.0
  • Table
    • v1.0.0
    • v1.0.1
    • v1.1.0
    • v1.2.0
  • Timestamps
    • v1.0.0
    • v1.1.0
  • Version
  • View
    • v1.0.0
  • Xarray Assets
    • v1.0.0

@jsignell no rush, but if you have more "best practices" that you've noticed (or that you notice while working on other tickets), can you add them to the list?

I think this one is good to close! I just checked the last todo items that were associated with merged PRs