v0.9.0-rc1
Pre-release
Pre-release
matthewhanson
released this
03 Jan 19:04
·
1234 commits
to master
since this release
[v0.9.0-rc1] - 2020-01-06
Added
- ItemCollection requires
stac_version
field,stac_extensions
has also been added - A
description
field has been added to Item assets (also Asset definitions extension). - Field
mission
to Common Metadata fields. - Extensions:
- Version Indicators extension, adds
version
anddeprecated
fields to STAC Items and Collections - Data Cube extension can be used in Collections, added new field
description
- Added
description
androles
fields to the Asset in the Asset Extension - Projection Extension to describe Items with Assets that have an associated geospatial projection.
- Version Indicators extension, adds
- STAC API:
- Added the Item and Collection API Version extension to support versioning in the API specification
- Run
npm run serve
ornpm run serve-ext
to quickly render development versions of the OpenAPI spec in the browser.
Changed
- Support for CommonMark 0.29 instead of CommonMark 0.28
- Collection field
property
and the merge ability moved to a new extension 'Commons' - Added attribute
roles
to Item assets (also Asset definitions extension), to be used similarly to Linkrel
. - Updated API yaml to clarify bbox filter should be implemented without brackets. Example:
bbox=160.6,-55.95,-170,-25.89
- Collection
summaries
merge array fields now. - Several fields have been moved from extensions or item fields to the Common Metadata fields:
eo:platform
/sar:platform
=>platform
eo:instrument
/sar:instrument
=>instruments
, also changed from string to array of stringseo:constellation
/sar:constellation
=>constellation
dtr:start_datetime
=>start_datetime
dtr:end_datetime
=>end_datetime
- Extensions:
- Data Cube extension: Changed allowed formats (removed PROJ string, added PROJJSON / WKT2) for reference systems
- Checksum extension is now using self-identifiable hashes (Multihash)
- Changed
sar:type
tosar:product_type
andsar:polarization
tosar:polarizations
in the SAR extension
- STAC API:
- The endpoint
/stac
has been merged with/
- The endpoint
/stac/search
is now called/search
- Sort Extension - added non-JSON query/form parameter format
- Fields extension has a simplified format for GET parameters
search
extension renamed tocontext
extension. JSON object renamed fromsearch:metadata
tocontext
- Removed "next" from the search metadata and query parameter, added POST body and headers to the links for paging support
- Query Extension - type restrictions on query predicates are more accurate, which may require additional implementation support.
- The endpoint
Removed
version
field in STAC Collections. Use Version Extension insteadsummaries
field from Catalogs. Use Collections instead- Asset Types (pre-defined values for the keys of individual assets, not media types) in Items. Use the asset's
roles
instead. license
field doesn't allow SPDX expressions any longer. Usevarious
and links instead.- Extensions:
eo:platform
,eo:instrument
,eo:constellation
from EO extension, andsar:platform
,sar:instrument
,sar:constellation
from the SAR extension- Removed from EO extension field
eo:epsg
in favor ofproj:epsg
gsd
andaccuracy
fromeo:bands
in the EO extensionsar:absolute_orbit
andsar:center_wavelength
fields from the SAR extensiondata_type
andunit
from thesar:bands
object in the SAR extension- Datetime Range (
dtr
) extension. Use the Common Metadata fields instead.
- STAC API:
next
from the search metadata and query parameter, added POST body and headers to the links for paging support
Fixed
- The
license
field in Item and Collection spec explicitly mentions that the valueproprietary
without a link means that the data is private. - Clarified how to fill
stac_extensions
. - More clarifications; typos fixed