Skip to content

Commit

Permalink
OARec: add GeoJSON information
Browse files Browse the repository at this point in the history
  • Loading branch information
tomkralidis authored Sep 27, 2024
1 parent 7e3ae29 commit 568429b
Showing 1 changed file with 4 additions and 0 deletions.
4 changes: 4 additions & 0 deletions workshop/content/docs/api-deep-dive/records.md
Original file line number Diff line number Diff line change
Expand Up @@ -354,6 +354,10 @@ queryables. An example query based on a "search engine" style search using the
Given OGC API - Records uses OGC API - Common and OGC API - Features as building blocks, please see the [OGC API - Features](features.md#feature) deep dive
for a detailed explanation.

### GeoJSON

The OGC API - Records GeoJSON Requirements Class specifies a GeoJSON based encoding for Record core, based on RFC7946. Given the ubiquity of GeoJSON, numerous tools exist to validate process and decode/encode GeoJSON, making OGC API - Records GeoJSON easy to include in metadata processing pipelines. OGC API - Records includes the [JSON Schema](https://github.com/opengeospatial/ogcapi-records/blob/master/core/openapi/schemas/recordGeoJSON.yaml) for the GeoJSON representation and thus can be used for runtime or offline validation of metadata payloads. Applications based on OGC API - Reocrds GeoJSON can extend and constrain the schema accordingly for domain specific workflows.

## Summary

OGC API - Records provides functionality for working with metadata data on the Web. This deep dive provided an overview of the standard and the various Resources and endpoints that are supported.

0 comments on commit 568429b

Please sign in to comment.