v0.9.0-rc2
Pre-release
Pre-release
[v0.9.0-rc2] - 2020-02-12
Added
- Basics added to Common Metadata definitions with new
description
field for
Item properties - New fields to the
link
object to facilitate pagination support for POST requests - Data role, as a suggestion for a common role for data files to be used in case data providers don't come up with their own names and semantics
- Clarification text on HTTP verbs in STAC API
- View Geometry Extension
Changed
- Item
title
definition moved from core Item fields to Common Metadata Basics
fields. No change is required for STAC Items. putFeature
can return aPreconditionFailed
to provide more explicit information when the resource has changed in the server- Sort extension now uses "+" and "-" prefixes for GET requests to denote sort order.
- Clarified how
/search
links must be added to/
and changed that links to both GET and POST must be provided now that the method can be specified in links. - Moved angle definitions between extensions
view
andsat
sat:off_nadir_angle
->view:off_nadir
sat:azimuth_angle
->view:azimuth
sat:incidence_angle
->view:incidence_angle
sat:sun_azimuth_angle
->view:sun_azimuth
sat:sun_elevation_angle
->view:sun_elevation
Removed
- In API, removed any mention of using media type
multipart/form-data
andx-www-form-urlencoded
Fixed
- Fixed Item JSON Schema now
allOf
optional Common Metadata properties are evaluated - Clarified usage of optional Common Metadata fields for STAC Items
- Clarified usage of paging options, especially in relation to what OGC API - Features offers
- Allow Commonmark in asset description, as it's allowed everywhere else
- Put asset description in the API
- Fixed API spec regarding license expressions
- Added missing schema in the API Version extension