core (map without parameter), it will require bbox and crs header in the response.
map-tilesets-list (tiling a map) (TilesetsList, tileset, tiles resources from Tiles)
Parameters
collections-selection (like API Tiles)
scaling (width and height), bgcolor, transparent (boolean flag)
spatial partitioning (one conformance class, like Tiles datetime?)
bbox (old bbox) -- native/storage CRS defaults to CRS84 if no native ?
subset (the coverage approach) -- native/storage CRS defaults to CRS84 if no native ?
crs
bbox-crs, subset-crs, crs (output CRS) (use case: bbox in lat/long and output in mercator),
temporal partitioning (one conformance class, like Tiles datetime?)
datetime
subset (the coverage approach)
Origins
styles (from Styles)
map-geodata
map-dataset
(future work) analytics results? (combine with other OGC API capabilities, e.g. properties=NDVI:(B5-B4)/(B5+B4)&filter=scene.cloudCover>60 and cloudCover < 15&sortby=desc(cloudCover))
Resources
Parameters
Origins
Representations