Sprint2 Planning

Planning for the Second Sprint on the OGC API EDR Candidate Standard

Objectives

1. Plugfest of all clients against all servers

2. Metadata clarifications

Mandatory metadata & schema (same as Discovery) (cross-API consistency)

Requirements for a client to support

Common, Collections and other API support

Optional metadata (Provenance? Usage?)

Search Engine metadata for discovery on the Web

API-Records consistent with Dublin Core, GeoJSON, API-Features-Core

Easily extended. E.g. Met Ocean extensions

Discussed possibilities of API-records 'q=' and 'type=' options for Met Ocean. 'geometry=' not part of Records 

3. Test development

   OpenAPI Schema

   CITE Tests

4. Cross-API consistency

   API-Common Parts Core, Collections, (CRS?) (Transactions- NO)

   API-Records

   Geospatial workflows

Tasks

Agree Use cases to inform Sprint work one each for sampling geometries (Position, Area, trajectory)

'Show and Tell' demo at pre-sprint Webinar, 4 Nov 2020

First with User Iterface, perhaps via Mark Burgoyne's Jupyter Notebook

then with emphasis on URL and technical detail, using IBL implementation

List of servers

List of clients

See also

Panagiotis (Peter) A. Vretanos https://github.com/opengeospatial/ogcapi-records/issues/42

Tom Kralidis example: https://github.com/opengeospatial/ogcapi-records/blob/master/core/examples/json/example_record.json

Tom Kralidis defining MetOcean types: https://github.com/OGCMetOceanDWG/ogcapi-records-metocean-bp/issues/1

Tom Kralidis "metoc:keywords": { "thesaurus": "http://foo", "keyword-list": ["foo, "bar", "baz"] }