From 568429b95ed7d85223a481edeab87771e8d474ab Mon Sep 17 00:00:00 2001 From: Tom Kralidis Date: Fri, 27 Sep 2024 13:09:18 -0400 Subject: [PATCH 1/3] OARec: add GeoJSON information --- workshop/content/docs/api-deep-dive/records.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/workshop/content/docs/api-deep-dive/records.md b/workshop/content/docs/api-deep-dive/records.md index 4a1271f..b1e7d59 100644 --- a/workshop/content/docs/api-deep-dive/records.md +++ b/workshop/content/docs/api-deep-dive/records.md @@ -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. From 300c425b6010d654475a4510de62a29c58a7e6d2 Mon Sep 17 00:00:00 2001 From: Tom Kralidis Date: Sun, 29 Sep 2024 19:38:00 -0400 Subject: [PATCH 2/3] Update records.md --- workshop/content/docs/api-deep-dive/records.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/workshop/content/docs/api-deep-dive/records.md b/workshop/content/docs/api-deep-dive/records.md index b1e7d59..bbf38b1 100644 --- a/workshop/content/docs/api-deep-dive/records.md +++ b/workshop/content/docs/api-deep-dive/records.md @@ -356,7 +356,7 @@ 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. +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 - Records GeoJSON can extend and constrain the schema accordingly for domain specific workflows. ## Summary From a2fcbe0c290bdf83dcb425c005f4a5d1446a144c Mon Sep 17 00:00:00 2001 From: Tom Kralidis Date: Mon, 30 Sep 2024 08:43:51 -0400 Subject: [PATCH 3/3] add GeoJSON for Features --- workshop/content/docs/api-deep-dive/features.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/workshop/content/docs/api-deep-dive/features.md b/workshop/content/docs/api-deep-dive/features.md index 571b525..2648ffd 100644 --- a/workshop/content/docs/api-deep-dive/features.md +++ b/workshop/content/docs/api-deep-dive/features.md @@ -788,6 +788,10 @@ INFO: Open of `OAPIF:https://demo.ldproxy.net/zoomstack' 21: woodland (title: Woodland) (Polygon) ``` +### GeoJSON + +The OGC API - Features GeoJSON Requirements Class specifies a GeoJSON based encoding for based on RFC7946. Given the ubiquity of GeoJSON, numerous tools exist to validate process and decode/encode GeoJSON, making OGC API - Features GeoJSON easy to include in data processing pipelines. OGC API - Features includes the [JSON Schema](https://github.com/opengeospatial/ogcapi-features/blob/master/core/openapi/schemas/featureGeoJSON.yaml) for the GeoJSON representation and thus can be used for runtime or offline validation of data payloads. Applications based on OGC API - Features GeoJSON can extend and constrain the schema accordingly for domain specific workflows. + ## Summary OGC API - Features provides functionality for working with vector data on the Web. This deep dive