Skip to content

Commit

Permalink
sta with OIM link
Browse files Browse the repository at this point in the history
  • Loading branch information
pzaborowski committed Jun 10, 2024
1 parent ef6bc48 commit 5400622
Show file tree
Hide file tree
Showing 9 changed files with 224 additions and 3 deletions.
173 changes: 173 additions & 0 deletions _sources/EDR_collection/examples/edr_collection.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,173 @@
{
"id":"swan2-edr",
"title":"EDR test with SWAN from Sea-Gust",
"description":"SST example netCDF data via EDR API",
"keywords":[
"edr",
"swan",
"aquaculture",
"template"
],
"links":[
{
"type":"text/html",
"rel":"canonical",
"title":"base url",
"href":"http://localhost:5003/swan-edr",
"hreflang":"en-US"
},
{
"type":"app/json",
"rel":"canonical",
"title":"example json query significant_wave_height by 2D bbox (11.25,36.3,11.26,36.31) coordinates and time slice 2023-07-16T02:00Z - 2023-07-16T02:00Z",
"href":"http://localhost:5003/collections/swan2-edr/cube?bbox=11.25,36.3,11.26,36.31&datetime=2023-07-16T02:00Z/2023-07-16T02:00Z&f=json",
"hreflang":"en-US"
},
{
"type":"text/html",
"rel":"canonical",
"title":"example html query significant_wave_height by 2D bbox (10.4,35.5,11.26,36.31) coordinates and time slice 2023-07-16T02:00Z - 2023-07-16T02:00Z",
"href":"http://localhost:5003/collections/swan2-edr/cube?bbox=10.4,35.5,11.26,36.31&datetime=2023-07-16T02:00Z/2023-07-16T02:00Z&parameter-name=hs",
"hreflang":"en-US"
},
{
"type":"text/html",
"rel":"canonical",
"title":"example html query all properties by 2D bbox (10.4,35.5,11.26,36.31) coordinates and time slice 2023-07-16T02:00Z - 2023-07-16T02:00Z",
"href":"http://localhost:5003/collections/swan2-edr/cube?bbox=10.4,35.5,11.26,36.31&datetime=2023-07-16T02:00Z/2023-07-16T02:00Z",
"hreflang":"en-US"
},
{
"type":"text/html",
"rel":"canonical",
"title":"example html query all prameters by POINT(11.0 36.0) coordinates and time slice 2023-07-16T02:00Z - 2023-07-16T02:00Z",
"href":"http://localhost:5003/collections/swan2-edr/position?coords=POINT(11.0 36.0)&datetime=2023-07-16T02:00Z&parameter-name=hs",
"hreflang":"en-US"
},
{
"type":"text/html",
"rel":"canonical",
"title":"example html query significant_wave_height by POINT(11.0 36.0) coordinates and time slice 2023-07-16T02:00Z - 2023-07-16T02:00Z",
"href":"http://localhost:5003/collections/swan2-edr/position?coords=POINT(11.0 36.0)&datetime=2023-07-16T02:00Z&parameter-name=hs",
"hreflang":"en-US"
},
{
"type":"app/json",
"rel":"canonical",
"title":"example json query significant_wave_height by POINT(11.0 36.0) coordinates and time slice 2023-07-16T02:00Z - 2023-07-16T02:00Z",
"href":"http://localhost:5003/collections/swan2-edr/position?coords=POINT(11.0 36.0)&datetime=2023-07-16T02:00Z&f=json&parameter-name=hs",
"hreflang":"en-US"
},
{
"type":"application/json",
"rel":"root",
"title":"The landing page of this server as JSON",
"href":"http://localhost:5002?f=json"
},
{
"type":"text/html",
"rel":"root",
"title":"The landing page of this server as HTML",
"href":"http://localhost:5002?f=html"
},
{
"type":"application/json",
"rel":"self",
"title":"This document as JSON",
"href":"http://localhost:5002/collections/swan2-edr?f=json"
},
{
"type":"application/ld+json",
"rel":"alternate",
"title":"This document as RDF (JSON-LD)",
"href":"http://localhost:5002/collections/swan2-edr?f=jsonld"
},
{
"type":"text/html",
"rel":"alternate",
"title":"This document as HTML",
"href":"http://localhost:5002/collections/swan2-edr?f=html"
},
{
"type":"application/json",
"rel":"data",
"title":"position query for this collection as JSON",
"href":"http://localhost:5002/collections/swan2-edr/position?f=json"
},
{
"type":"text/html",
"rel":"data",
"title":"position query for this collection as HTML",
"href":"http://localhost:5002/collections/swan2-edr/position?f=html"
},
{
"type":"application/json",
"rel":"data",
"title":"cube query for this collection as JSON",
"href":"http://localhost:5002/collections/swan2-edr/cube?f=json"
},
{
"type":"text/html",
"rel":"data",
"title":"cube query for this collection as HTML",
"href":"http://localhost:5002/collections/swan2-edr/cube?f=html"
}
],
"extent":{
"spatial":{
"bbox":[
[
10.4,
35.5,
11.26,
36.31
]
],
"crs":"http://www.opengis.net/def/crs/OGC/1.3/CRS84"
}
},
"parameter_names":{
"hs":{
"id":"hs",
"type":"Parameter",
"name":"sea surface wave significant height",
"unit":{
"label":{
"en":"sea surface wave significant height"
},
"symbol":{
"value":"m",
"type":"http://www.opengis.net/def/uom/UCUM/"
}
}
},
"eastward_wave_direction_unit_vector":{
"id":"eastward_wave_direction_unit_vector",
"type":"Parameter",
"name":"eastward wave direction unit vector",
"unit":{
"label":{
"en":"eastward wave direction unit vector"
},
"symbol":{
"value":"-",
"type":"http://www.opengis.net/def/uom/UCUM/"
}
}
},
"northward_wave_direction_unit_vector":{
"id":"northward_wave_direction_unit_vector",
"type":"Parameter",
"name":"northward wave direction unit vector",
"unit":{
"label":{
"en":"northward wave direction unit vector"
},
"symbol":{
"value":"-",
"type":"http://www.opengis.net/def/uom/UCUM/"
}
}
}
}
}
2 changes: 1 addition & 1 deletion _sources/coverageJSONFisheries/bblock.json
Original file line number Diff line number Diff line change
Expand Up @@ -34,6 +34,6 @@
"coverage",
"spatiotemporal",
"linked-data",
OIM
"OIM"
]
}
2 changes: 1 addition & 1 deletion _sources/coverageJSONFisheries/description.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@

CoverageJSON can be used to encode coverages and collections of coverages. Coverage data may be gridded or non-gridded, and data values may represent continuous values (such as temperature) or discrete categories (such as land cover classes). CoverageJSON uses JSON-LD to provide interoperability with RDF and Semantic Web applications and to reduce the potential size of the payload.

Relatively large datasets can be handled efficiently in a “web-friendly” way by partitioning information among several CoverageJSON documents, including a tiling mechanism. Nevertheless, CoverageJSON is not intended to be a replacement for efficient binary formats such as NetCDF, HDF or GRIB, and is not intended primarily to store or transfer very large datasets in bulk.""
Relatively large datasets can be handled efficiently in a “web-friendly” way by partitioning information among several CoverageJSON documents, including a tiling mechanism. Nevertheless, CoverageJSON is not intended to be a replacement for efficient binary formats such as NetCDF, HDF or GRIB, and is not intended primarily to store or transfer very large datasets in bulk."


## Key features of this profile:
Expand Down
3 changes: 2 additions & 1 deletion _sources/oim-obs/context.jsonld
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@
{
"@context": {
"@context": ["https://raw.githubusercontent.com/ILIAD-ocean-twin/OIM/main/jsonld/crossDomain-context.jsonld",
{
"sosa": "http://www.w3.org/ns/sosa/",
"rdfs": "http://www.w3.org/2000/01/rdf-schema#",
"iliad": "https://w3id.org/iliad/property/",
Expand Down
20 changes: 20 additions & 0 deletions _sources/oim-sta-obs/bblock.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,20 @@
{
"name": "OIM Observations",
"abstract": "Defines SensorThings API Observations to implement the OIM SOSA cross-domain model in a form compatible with ILIAD and other digital twins using this model.",
"status": "under-development",
"dateTimeAddition": "2023-06-05T00:00:00Z",
"itemClass": "schema",
"register": "iliad-apis",
"version": "0.1",
"dateOfLastChange": "2023-06-05",
"link": "https://github.com/opengeospatial/iliad-api-features/oim-sta-obs",
"sources": [
{
"title": "Reference to ILIAD",
"link": "https://example.com/sources/1"
}
],
"maturity": "development",
"scope": "unstable",
"tags": ["iliad", "oim", "sosa", "ditto"]
}
4 changes: 4 additions & 0 deletions _sources/oim-sta-obs/context.jsonld
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
{
"@context": ["https://raw.githubusercontent.com/ILIAD-ocean-twin/OIM/main/jsonld/crossDomain-context.jsonld",
"https://ogcincubator.github.io/bblocks-sta/build/annotated/api/sta/Observation/context.jsonld"]
}
15 changes: 15 additions & 0 deletions _sources/oim-sta-obs/description.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
## Ocean Information Model Observations Profile

Currently a stub where requirements for OIM implementation can be defined as required.

Note specific profiles will define specific requirements for interaction with external systems.

The JSON-LD Context declares the default baseURI of Observation with generic STA context and OIM specific context.

TODO: (MVP)
1 - implement the observableProperties Register as a concept scheme under OGC hosted
2 - define a SHACL or other rule that requires observableProperties to be registered in the ILIAD observable properties register.

Note that it may have an externally resolvable URI or be a proxy handled by ILIAD (using the OGC RAINBOW)

The mechanisms for handling external vocabulary constraints to be define here: (TBD)
4 changes: 4 additions & 0 deletions _sources/oim-sta-obs/examples.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
- title: Oceans Information Model examples
content: |-
TBD - see specific sub-profile for examples.
4 changes: 4 additions & 0 deletions _sources/oim-sta-obs/schema.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,4 @@
"$schema": https://json-schema.org/draft/2020-12/schema
title: A OIM aligned STA Observtion schema
description: 'Component of OGC STA Observation. no particular added constraints are added'
$ref: https://ogcincubator.github.io/bblocks-sta/build/annotated/api/sta/Observation/schema.json

0 comments on commit 5400622

Please sign in to comment.