Guidelines

Policies to be followed where possible

The API should use OGC-API-Common-Part 1: Core

The API should use Candidate OGC-API-Common-Part 2: Collections

The API should be compatible with OGC API-Features-Part 1: Core

The API should follow the 22 principles of the OGC Web API Guidelines

The API should adhere to OGC Policy on Naming of OGC API Standards, Repositories & Specification Elements

The API should follow OGC JSON Best Practice

The API should follow W3C Data on the Web Best Practices

The API should follow W3C Spatial Data on the Web Best Practices

Current Normative references and other related specs

• OGC API - Common - Part 1: Core

• OGC API - Common - Part 2: Collections

• OGC API - Features - Part 1: Core

• OpenAPI Version 3

• WKT Well Known Text (see Sections 6 and 7)

• WKT Well Known Text for Coordinate Reference Systems (CRS)

• DateTime strings, IETF RFC3339 (profile of ISO8601)

• CoverageJSON and overview

Examples compared to other standards

WCS and EDR

[SOS/SWE/O&M and EDR]

[TestBed16 DAPA and EDR]

[Anything else?]