Can we find a name for what I called "the map description resource" but it is more than that?

[joanma747]

In the OGC API Tiles, the tiles description has been renamed to tileset. The reason is that the resource represent the full tileset that will be later accessed tile by tile.

So, in the OGC API Map, the map description should be called...?. It is a document that describes the map as a hole and tell us what is possible to include the the map paramentres for this resource. In practice describes the whole map that can be accessed by tiles or by bbox. It transforms the dataset or the collection into a map.

Names?
Full map?
Hypermap?
renderedData?

Opinions?

[jerstlouis]

How about the "Map" resource? :)

We should make a list of things that will be included in this resource:

• Styles
• Collections?
• Could this support more CRSes than the raw data requests?
• Tilesets? (See tilesets resource only contains links to tileset resources. May we remove the thing completely? ogcapi-tiles#43 (comment) for new suggested approach to listing tilesets)
• Custom rendering capabilities? POSTing your own style and/or your own RenderMap process execution document (Rendering a map using a custom style, or using a process execution document with standardized inputs #42)

A related question to naming this also I think is questions I asked in #32:

And what about when the raw data as stored on the server is already color-adjusted (A)RGB imagery (e.g. a mosaic)? Can that be considered both a map and the raw data? Is it still the Maps API, if there is no styling capability available?

[joanma747]

There will not be map metadata because most of what we needed is covered by common or styles.