search

opengeospatial / ogcapi-tiles

OGC API - Tiles draft specification
https://ogcapi.ogc.org/tiles
Other
38 stars 18 forks source link

verify consistency of the OpenAPI documents and the spec. #76

Closed joanma747 closed 2 years ago

joanma747 commented 3 years ago

said!

chris-little commented 3 years ago

Very!

jerstlouis commented 3 years ago

Suggesting that we tackle the OpenAPI definitions at our next meeting, re-organizing them as responses/, schemas/ and parameters/, and possibly referencing building blocks from Common (for now we can copy them in the sub-folder until common is itself synchronized with Coverages).

This is the organization used in all other OGC API specifications: Features, Common, Coverages, EDR, Processes.

We should also review and synchronize with the API definitions of implementations such as ours.

We should reference or include separate folders for the TileSet metadata schemas, but keep the files identical, as we did e.g. for OGC API - Coverages & CIS.

jerstlouis commented 2 years ago

The API is now in sync with the latest version of the specification, supports all dataset/collection, styled/not-styled, map/vector/coverage tiles combinations identified so far, includes pre-determined operationIds corresponding to specific requirements and conformance classes (see https://github.com/opengeospatial/ogcapi-tiles/issues/104#issuecomment-1000433817, #101, and https://github.com/opengeospatial/ogcapi-tiles/files/7770664/TilesOperationIds.ods), and has been re-organized into easily re-usable building blocks, and can even be used directly by simply changing the example server if the dynamic /api/* end-points to list available resources (collections, tileMatrixSets, styles) are implemented.

See the latest OpenAPI definition with SwaggerUI.