diff --git a/definitions/docs/docs.jsonld b/definitions/docs/docs.jsonld index 855f8f88..72230bf4 100644 --- a/definitions/docs/docs.jsonld +++ b/definitions/docs/docs.jsonld @@ -44,6 +44,36 @@ } }, "@graph": [ + { + "title": "OGC API - Maps - Part 1: Core", + "alternative": [ + "OGC API - Maps - Part 1: Core", + "20-058" + ], + "URI": "http://www.opengis.net/doc/IS/ogcapi-maps-1/1.0", + "identifier": "20-058", + "URL": "https://docs.ogc.org/is/20-058/20-058.html", + "type": "doctype:is", + "creator": "Joan Mas\u00f3, J\u00e9r\u00f4me Jacovella-St-Louis ", + "contributor": null, + "description": "The OGC API\u2009\u2014\u2009Maps\u2009\u2014\u2009Part 1: Core Standard defines a Web API for requesting maps over the Web. A map is a portrayal of geographic information as a digital representation suitable for display on a rendering device (adapted from OGC 06-042/ISO 19128 OpenGIS\u00ae Web Map Server (WMS) Implementation Specification). Implementations of the OGC API\u2009\u2014\u2009Maps Standard are designed for a client to easily:\r\n\r\nRequest a visual representation of one or more geospatial data layers in different styles;\r\nSelect by area, time and resolution of interest;\r\nChange parameters such as the background color and coordinate reference systems.\r\nA server that implements OGC API\u2009\u2014\u2009Maps provides information about what maps are offered. OGC API\u2009\u2014\u2009Maps addresses use cases similar to those addressed by the OGC 06-042/ISO 19128 OpenGIS\u00ae Web Map Server (WMS) Implementation Specification Standard.", + "publisher": "Open Geospatial Consortium", + "language": "English", + "license": null, + "source": null, + "rights": "", + "isPartOf": null, + "date": "2024-08-09", + "dateAccepted": null, + "dateSubmitted": null, + "format": "text/html", + "hasFormat": null, + "extent": null, + "@type": "skos:Concept", + "broader": "doctype:is", + "inScheme": "http://www.opengis.net/def/docs", + "notation": "20-058" + }, { "title": "Common Query Language (CQL2)", "alternative": [ diff --git a/definitions/docs/docs.ttl b/definitions/docs/docs.ttl index a47eb624..0adc5b9e 100644 --- a/definitions/docs/docs.ttl +++ b/definitions/docs/docs.ttl @@ -15836,6 +15836,24 @@ This specification is a successor to the OGC’s Web Map Tile Service (WMTS) sta skos:notation "20-057"^^na:doc_no ; skos:prefLabel "OGC API - Tiles - Part 1: Core"@en . + a skos:Concept ; + dct:created "2024-08-09"^^ ; + dct:creator "Joan Masó, Jérôme Jacovella-St-Louis " ; + na:doctype doctype:is ; + rdfs:seeAlso ; + skos:altLabel "20-058"@en, + "OGC API - Maps - Part 1: Core"@en ; + skos:broader doctype:is ; + skos:definition """The OGC API — Maps — Part 1: Core Standard defines a Web API for requesting maps over the Web. A map is a portrayal of geographic information as a digital representation suitable for display on a rendering device (adapted from OGC 06-042/ISO 19128 OpenGIS® Web Map Server (WMS) Implementation Specification). Implementations of the OGC API — Maps Standard are designed for a client to easily:\r +\r +Request a visual representation of one or more geospatial data layers in different styles;\r +Select by area, time and resolution of interest;\r +Change parameters such as the background color and coordinate reference systems.\r +A server that implements OGC API — Maps provides information about what maps are offered. OGC API — Maps addresses use cases similar to those addressed by the OGC 06-042/ISO 19128 OpenGIS® Web Map Server (WMS) Implementation Specification Standard.""" ; + skos:inScheme ; + skos:notation "20-058"^^na:doc_no ; + skos:prefLabel "OGC API - Maps - Part 1: Core"@en . + a skos:Concept ; dct:created "2021-01-28"^^ ; dct:creator "Gobe Hobona" ; @@ -18095,16 +18113,16 @@ This concept of UDT, although often mentioned in the media, is still fairly new skos:prefLabel "OGC Documents" . [] a prov:Activity ; - prov:endedAtTime "2024-07-30T10:34:05.928276"^^xsd:dateTime ; - prov:startedAtTime "2024-07-30T10:34:04.883138"^^xsd:dateTime ; + prov:endedAtTime "2024-08-10T10:33:53.521511"^^xsd:dateTime ; + prov:startedAtTime "2024-08-10T10:33:52.467869"^^xsd:dateTime ; prov:used [ a prov:Entity ; dct:format "application/json" ; - dct:hasVersion "git:3852709b7dabb312dcd088bac852ed1baee222e3" ; + dct:hasVersion "git:c89beb527ab5c15420e81e8661f606c28f76194f" ; rdfs:seeAlso ] ; prov:wasAssociatedWith [ a prov:Agent, schema:SoftwareApplication ; rdfs:label "OGC-NA tools" ; dct:hasVersion "0.3.49" ; rdfs:seeAlso ] ; - prov:wasInformedBy [ dct:identifier "3f4259fb-9ac8-43cf-95e7-9e11bf5969d9" ] . + prov:wasInformedBy [ dct:identifier "5f5b05c3-a60e-424a-98dc-119698b7c563" ] . diff --git a/definitions/docs/docs.txt b/definitions/docs/docs.txt index 5a235b2e..aae9e200 100644 --- a/definitions/docs/docs.txt +++ b/definitions/docs/docs.txt @@ -1,18 +1,72 @@ Validation Report Conforms: False Results (25): +Constraint Violation in UniqueLangConstraintComponent (http://www.w3.org/ns/shacl#UniqueLangConstraintComponent): + Severity: sh:Violation + Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] + Focus Node: + Result Path: skos:prefLabel + Message: More than one String shares the same Language Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): Severity: sh:Violation - Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:message Literal("Requirement 2.1.5 Each vocabulary _MUST_ have one and only one created date indicated using the dcterms:created property that must be either an `xsd:date`, `xsd:dateTime` or `xsd:dateTimeStamp` literal value") ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:dateTime ] [ sh:datatype xsd:date ] [ sh:datatype xsd:dateTimeStamp ] ) ; sh:path dcterms:created ] + Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] + Focus Node: doctype:cr + Result Path: skos:prefLabel + Message: Less than 1 values on doctype:cr->skos:prefLabel +Constraint Violation in UniqueLangConstraintComponent (http://www.w3.org/ns/shacl#UniqueLangConstraintComponent): + Severity: sh:Violation + Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] + Focus Node: + Result Path: skos:prefLabel + Message: More than one String shares the same Language +Constraint Violation in UniqueLangConstraintComponent (http://www.w3.org/ns/shacl#UniqueLangConstraintComponent): + Severity: sh:Violation + Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] + Focus Node: + Result Path: skos:prefLabel + Message: More than one String shares the same Language +Constraint Violation in UniqueLangConstraintComponent (http://www.w3.org/ns/shacl#UniqueLangConstraintComponent): + Severity: sh:Violation + Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] + Focus Node: + Result Path: skos:prefLabel + Message: More than one String shares the same Language +Constraint Violation in UniqueLangConstraintComponent (http://www.w3.org/ns/shacl#UniqueLangConstraintComponent): + Severity: sh:Violation + Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] + Focus Node: + Result Path: skos:prefLabel + Message: More than one String shares the same Language +Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): + Severity: sh:Violation + Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] + Focus Node: + Result Path: skos:prefLabel + Message: Less than 1 values on ->skos:prefLabel +Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): + Severity: sh:Violation + Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:nodeKind sh:IRI ; sh:path skos:hasTopConcept ] Focus Node: - Result Path: dcterms:created - Message: Requirement 2.1.5 Each vocabulary _MUST_ have one and only one created date indicated using the dcterms:created property that must be either an `xsd:date`, `xsd:dateTime` or `xsd:dateTimeStamp` literal value + Result Path: skos:hasTopConcept + Message: Less than 1 values on ->skos:hasTopConcept +Validation Result in OrConstraintComponent (http://www.w3.org/ns/shacl#OrConstraintComponent): + Severity: sh:Warning + Source Shape: + Focus Node: + Value Node: + Message: Requirement 2.1.7 Provenance for a Concept _SHOULD_ be indicated by at least one of the following properties: dcterms:provenance, dcterms:source or prov:wasDerivedFrom. +Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent): + Severity: sh:Violation + Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:definition ] + Focus Node: + Result Path: skos:definition + Message: More than 1 values on ->skos:definition Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): Severity: sh:Violation - Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:message Literal("Requirement 2.1.5 Each vocabulary _MUST_ have one and only one created date indicated using the dcterms:created property that must be either an `xsd:date`, `xsd:dateTime` or `xsd:dateTimeStamp` literal value") ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:dateTime ] [ sh:datatype xsd:date ] [ sh:datatype xsd:dateTimeStamp ] ) ; sh:path dcterms:created ] + Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:message Literal("Requirement 2.1.5 Each vocabulary _MUST_ have one and only one modified date indicated using the dcterms:modified property that must be either an `xsd:date`, `xsd:dateTime or `xsd:dateTimeStamp` literal value") ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:dateTime ] [ sh:datatype xsd:date ] [ sh:datatype xsd:dateTimeStamp ] ) ; sh:path dcterms:modified ] Focus Node: - Result Path: dcterms:created - Message: Requirement 2.1.5 Each vocabulary _MUST_ have one and only one created date indicated using the dcterms:created property that must be either an `xsd:date`, `xsd:dateTime` or `xsd:dateTimeStamp` literal value + Result Path: dcterms:modified + Message: Requirement 2.1.5 Each vocabulary _MUST_ have one and only one modified date indicated using the dcterms:modified property that must be either an `xsd:date`, `xsd:dateTime or `xsd:dateTimeStamp` literal value Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): Severity: sh:Violation Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:message Literal("Requirement 2.1.5 Each vocabulary _MUST_ have one and only one modified date indicated using the dcterms:modified property that must be either an `xsd:date`, `xsd:dateTime or `xsd:dateTimeStamp` literal value") ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:dateTime ] [ sh:datatype xsd:date ] [ sh:datatype xsd:dateTimeStamp ] ) ; sh:path dcterms:modified ] @@ -21,28 +75,28 @@ Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl# Message: Requirement 2.1.5 Each vocabulary _MUST_ have one and only one modified date indicated using the dcterms:modified property that must be either an `xsd:date`, `xsd:dateTime or `xsd:dateTimeStamp` literal value Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): Severity: sh:Violation - Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:message Literal("Requirement 2.1.5 Each vocabulary _MUST_ have one and only one modified date indicated using the dcterms:modified property that must be either an `xsd:date`, `xsd:dateTime or `xsd:dateTimeStamp` literal value") ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:dateTime ] [ sh:datatype xsd:date ] [ sh:datatype xsd:dateTimeStamp ] ) ; sh:path dcterms:modified ] + Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:message Literal("Requirement 2.1.5 Each vocabulary _MUST_ have one and only one created date indicated using the dcterms:created property that must be either an `xsd:date`, `xsd:dateTime` or `xsd:dateTimeStamp` literal value") ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:dateTime ] [ sh:datatype xsd:date ] [ sh:datatype xsd:dateTimeStamp ] ) ; sh:path dcterms:created ] Focus Node: - Result Path: dcterms:modified - Message: Requirement 2.1.5 Each vocabulary _MUST_ have one and only one modified date indicated using the dcterms:modified property that must be either an `xsd:date`, `xsd:dateTime or `xsd:dateTimeStamp` literal value -Validation Result in OrConstraintComponent (http://www.w3.org/ns/shacl#OrConstraintComponent): - Severity: sh:Warning - Source Shape: - Focus Node: - Value Node: - Message: Requirement 2.1.7 Provenance for a Concept _SHOULD_ be indicated by at least one of the following properties: dcterms:provenance, dcterms:source or prov:wasDerivedFrom. + Result Path: dcterms:created + Message: Requirement 2.1.5 Each vocabulary _MUST_ have one and only one created date indicated using the dcterms:created property that must be either an `xsd:date`, `xsd:dateTime` or `xsd:dateTimeStamp` literal value +Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): + Severity: sh:Violation + Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:message Literal("Requirement 2.1.5 Each vocabulary _MUST_ have one and only one created date indicated using the dcterms:created property that must be either an `xsd:date`, `xsd:dateTime` or `xsd:dateTimeStamp` literal value") ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:dateTime ] [ sh:datatype xsd:date ] [ sh:datatype xsd:dateTimeStamp ] ) ; sh:path dcterms:created ] + Focus Node: + Result Path: dcterms:created + Message: Requirement 2.1.5 Each vocabulary _MUST_ have one and only one created date indicated using the dcterms:created property that must be either an `xsd:date`, `xsd:dateTime` or `xsd:dateTimeStamp` literal value Constraint Violation in OrConstraintComponent (http://www.w3.org/ns/shacl#OrConstraintComponent): Severity: sh:Violation Source Shape: Focus Node: Value Node: Message: Requirement 2.3.3 Each skos:Concept in a vocabulary _MUST_ indicate that it appears within that vocabulary's hierarchy of terms by use of either or both `skos:inScheme` and `skos:topConceptOf` properties -Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): +Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent): Severity: sh:Violation Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:definition ] - Focus Node: + Focus Node: Result Path: skos:definition - Message: Less than 1 values on ->skos:definition + Message: More than 1 values on ->skos:definition Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent): Severity: sh:Violation Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:definition ] @@ -52,15 +106,15 @@ Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl# Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent): Severity: sh:Violation Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:definition ] - Focus Node: doctype:rp + Focus Node: Result Path: skos:definition - Message: More than 1 values on doctype:rp->skos:definition + Message: More than 1 values on ->skos:definition Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent): Severity: sh:Violation Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:definition ] - Focus Node: + Focus Node: doctype:rp Result Path: skos:definition - Message: More than 1 values on ->skos:definition + Message: More than 1 values on doctype:rp->skos:definition Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent): Severity: sh:Violation Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:definition ] @@ -73,6 +127,12 @@ Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl# Focus Node: Result Path: skos:definition Message: More than 1 values on ->skos:definition +Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): + Severity: sh:Violation + Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:definition ] + Focus Node: + Result Path: skos:definition + Message: Less than 1 values on ->skos:definition Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent): Severity: sh:Violation Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:definition ] @@ -85,69 +145,9 @@ Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl# Focus Node: doctype:d-ballot Result Path: skos:definition Message: More than 1 values on doctype:d-ballot->skos:definition -Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent): - Severity: sh:Violation - Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:definition ] - Focus Node: - Result Path: skos:definition - Message: More than 1 values on ->skos:definition -Constraint Violation in MaxCountConstraintComponent (http://www.w3.org/ns/shacl#MaxCountConstraintComponent): - Severity: sh:Violation - Source Shape: [ sh:maxCount Literal("1", datatype=xsd:integer) ; sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:definition ] - Focus Node: - Result Path: skos:definition - Message: More than 1 values on ->skos:definition -Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): - Severity: sh:Violation - Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] - Focus Node: - Result Path: skos:prefLabel - Message: Less than 1 values on ->skos:prefLabel -Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): - Severity: sh:Violation - Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] - Focus Node: doctype:cr - Result Path: skos:prefLabel - Message: Less than 1 values on doctype:cr->skos:prefLabel -Constraint Violation in UniqueLangConstraintComponent (http://www.w3.org/ns/shacl#UniqueLangConstraintComponent): - Severity: sh:Violation - Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] - Focus Node: - Result Path: skos:prefLabel - Message: More than one String shares the same Language -Constraint Violation in UniqueLangConstraintComponent (http://www.w3.org/ns/shacl#UniqueLangConstraintComponent): - Severity: sh:Violation - Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] - Focus Node: - Result Path: skos:prefLabel - Message: More than one String shares the same Language -Constraint Violation in UniqueLangConstraintComponent (http://www.w3.org/ns/shacl#UniqueLangConstraintComponent): - Severity: sh:Violation - Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] - Focus Node: - Result Path: skos:prefLabel - Message: More than one String shares the same Language -Constraint Violation in UniqueLangConstraintComponent (http://www.w3.org/ns/shacl#UniqueLangConstraintComponent): - Severity: sh:Violation - Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] - Focus Node: - Result Path: skos:prefLabel - Message: More than one String shares the same Language -Constraint Violation in UniqueLangConstraintComponent (http://www.w3.org/ns/shacl#UniqueLangConstraintComponent): - Severity: sh:Violation - Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] - Focus Node: - Result Path: skos:prefLabel - Message: More than one String shares the same Language Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): Severity: sh:Violation Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:or ( [ sh:datatype xsd:string ] [ sh:datatype rdf:langString ] ) ; sh:path skos:prefLabel ; sh:uniqueLang Literal("true" = True, datatype=xsd:boolean) ] Focus Node: Result Path: skos:prefLabel Message: Less than 1 values on ->skos:prefLabel -Constraint Violation in MinCountConstraintComponent (http://www.w3.org/ns/shacl#MinCountConstraintComponent): - Severity: sh:Violation - Source Shape: [ sh:minCount Literal("1", datatype=xsd:integer) ; sh:nodeKind sh:IRI ; sh:path skos:hasTopConcept ] - Focus Node: - Result Path: skos:hasTopConcept - Message: Less than 1 values on ->skos:hasTopConcept diff --git a/definitions/docs/entailed/docs.jsonld b/definitions/docs/entailed/docs.jsonld index 8dd5c721..55eab67d 100644 --- a/definitions/docs/entailed/docs.jsonld +++ b/definitions/docs/entailed/docs.jsonld @@ -1,18 +1,18 @@ [ { - "@id": "http://www.opengis.net/def/docs/14-073r1", + "@id": "http://www.opengis.net/def/docs/18-086r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-11-03" + "@value": "2019-02-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Wilber, Johannes Echterhoff, Matt de Ris, Joshua Lieberman" + "@value": "Sam Meek" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -27,17 +27,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/60175" + "@id": "https://docs.ogc.org/per/18-086r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Aircraft Access to SWIM (AAtS) Harmonization Architecture Report" + "@value": "18-086r1" }, { "@language": "en", - "@value": "14-073r1" + "@value": "OGC Vector Tiles Pilot: Summary Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -47,7 +47,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document describes the Aircraft Access to SWIM (AAtS) harmonization \r\narchitecture developed by a team funded by the FAA and led by the Open Geospatial \r\nConsortium (OGC). " + "@value": "This OGC Engineering Report (ER) provides the summary findings resulting from completion of the OGC Vector Tiles Pilot (VTP or Pilot). The requirements for the Pilot were generated from a combination of sponsor input and analysis of typical use cases for tiling of vector feature data across the OGC Standards Baseline and related standards. The driving use case for this activity was the visualization of feature data on a client. The three main scenarios considered were consumption of tiled feature data by a web client, a desktop client and a mobile client. As a standards body, the OGC already has standards that fit these use cases. These are; Web Map Tile Service 1.0 (WMTS) for a web client, and GeoPackage 1.2 for a mobile client. Web Feature Service (WFS) 3.0 is suitable for a desktop client and has an in-built method to support tiling, but not specifically for tiled feature data such as that explored in the VTP. One of the purposes of the Pilot was to produce demonstration implementations to support tiled feature data using WFS 3.0, WMTS 1.0 and GeoPackage 1.2 that can be validated by Technology Integration Experiments (TIEs). The draft extension to these standards helped define a draft Conceptual Model for tiled feature data in support of visualization. The Conceptual Model formally captures the requirements for component implementations and rationalizes them into a model documented in the Unified Modeling Language (UML).\r\n\r\nThe ER provides an overview of each of the components, their implementation decisions and the challenges faced. The components are presented as draft extensions to existing standards. The WFS standard is currently in a major revision cycle and is transitioning away from services to a resource-oriented architecture. This transition has implications for access to tiled feature data. This offers options of access to pre-rendered tiles, or to tiles created using WFS 3.0 query functionality. The current WMTS standard only offers access to the pre-rendered tiles and much of the work is therefore about defining and supporting tiled feature data as a media type. The OGC GeoPackage standard is more complex as it attempts to ship all of the tiled feature data in a self-contained package aimed at environments that have Denied, Degraded, Intermittent or Limited (DDIL) bandwidth. DDIL is an important use case for GeoPackage as most normal web services do not function without connectivity. The military, first responders and other groups who work in challenging operational environments require a capability to ship, store and distribute geospatial data in an efficient, modern manner. The combination of GeoPackage and tiled feature data offers the means to supply detailed geospatial data in a portable fashion to satisfy many DDIL use cases. GeoPackage also offers the majority of the future work as it attempts to store information such as styling and attribution separately to the geometries to take advantage of a relational database structure.\r\n\r\nWhen this project was initiated, the term vector tiles was used throughout. However, as the project progressed, the participants agreed that the term tiled feature data was more appropriate than the colloquial term of vector tiles. This engineering report therefore interchangeably uses both tiled feature data and vector tiles to refer to the approach of tiling vector feature data.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58,35 +58,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-073r1" + "@value": "18-086r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Aircraft Access to SWIM (AAtS) Harmonization Architecture Report" + "@value": "OGC Vector Tiles Pilot: Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-001r4", + "@id": "http://www.opengis.net/def/docs/20-045", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-09-13" + "@value": "2020-10-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Benjamin Hagedorn, Simon Thum, Thorsten Reitz, Voker Coors, Ralf Gutbell" + "@value": "Tom Landry" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -96,27 +96,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/15-001r4/15-001r4.html" + "@id": "https://docs.ogc.org/per/20-045.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-001r4" + "@value": "OGC Earth Observation Applications Pilot: CRIM Engineering Report" }, { "@language": "en", - "@value": "3D Portrayal Service 1.0" + "@value": "20-045" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The 3D Portrayal Service Standard is a geospatial 3D content delivery implementation specification. It focuses on what is to be delivered in which manner to enable interoperable 3D portrayal.\r\n\r\nIt does not define or endorse particular content transmission formats, but specifies how geospatial 3D content is described, selected, and delivered. It does not prescribe how aforementioned content is to be organized and represented, but provides a framework to determine whether 3D content is interoperable at the content representation level. More details are available in Design of this standard." + "@value": "This engineering report documents experiments conducted by CRIM in OGC’s Earth Observation Applications Pilot project, sponsored by the European Space Agency (ESA) and Natural Resources Canada (NRCan), with support from Telespazio VEGA UK. Remote sensing, machine learning and climate informatics applications were reused, adapted and matured in a common architecture. These applications were deployed in a number of interoperable data and processing platforms hosted in three Canadian provinces, in Europe and in the United States." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -127,35 +127,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-001r4" + "@value": "20-045" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® 3D Portrayal Service 1.0" + "@value": "OGC Earth Observation Applications Pilot: CRIM Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-034", + "@id": "http://www.opengis.net/def/docs/05-047r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-29" + "@value": "2006-01-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Genong (Eugene) Yu, Liping Di" + "@value": "Martin Kyle, David Burggraf, Sean Forde, Ron Lake" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -165,27 +165,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=33925" + "@id": "https://portal.ogc.org/files/?artifact_id=13252" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-6 Georeferencable Imagery Engineering Report" + "@value": "05-047r3" }, { "@language": "en", - "@value": "09-034" + "@value": "GML in JPEG 2000 for Geographic Imagery Encoding Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document discusses considerations about and recommendations for approaches for georeferenceable imagery under the Sensor Web Enablement thread during OGC Web Services Phase 6. This is an extension to the work described in the previous engineering report number OGC 08-071 . Georeferencealbe imagery is “a referenceable grid that has information that can be used to transform grid coordinates to external coordinates, but the transformation shall not be required to be an affine transformation”. Geolocation of georeferenceable imagery refers to the techniques described in ISO 19130, such as sensor models, functional fit models, and spatial registration using control points." + "@value": "The OpenGIS® GML in JPEG 2000 for Geographic Imagery Encoding Standard defines the means by which the OpenGIS® Geography Markup Language (GML) Standard http://www.opengeospatial.org/standards/gml is used within JPEG 2000 http://www.jpeg.org/jpeg2000/ images for geographic imagery. The standard also provides packaging mechanisms for including GML within JPEG 2000 data files and specific GML application schemas to support the encoding of images within JPEG 2000 data files. JPEG 2000 is a wavelet-based image compression standard that provides the ability to include XML data for description of the image within the JPEG 2000 data file. \r\nSee also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -196,35 +196,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-034" + "@value": "05-047r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 Georeferencable Imagery Engineering Report" + "@value": "OpenGIS GML in JPEG 2000 for Geographic Imagery Encoding Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-059", + "@id": "http://www.opengis.net/def/docs/15-004", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-10-30" + "@value": "2015-07-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lars Schylberg, Lubos Belka" + "@value": "David Graham" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -234,27 +234,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/17-059/17-059.html" + "@id": "https://portal.ogc.org/files/?artifact_id=61936" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-059" + "@value": "15-004" }, { "@language": "en", - "@value": "Technical report from the DGIWG Portrayal Technical Panel testing of SLD (1.1.0) for OGC" + "@value": "Common DataBase Volume 2 Appendices" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The DGIWG Portrayal Technical Panel (DPTP) has been investigating how to standardize the portrayal of military context symbology within Web Services. The team sought to use version 1.1.0 of OGC Style Layer Descriptor standard and version 1.1.0 of Symbology Encoding (SLD and SE) standard to achieve this.\r\nThe team sought to apply military-specific symbology to military-specific topographic feature vector datasets within a number of software products.\r\nThe testing and experimentation highlighted a number of deficiencies in the SLD and SE standards which result in a barrier to interoperability. The ideal situation would be to have SLD and SE descriptors interoperable between all software products that implement the standard. This was found not to be the current situation.\r\nThis position paper describes the findings and outlines recommendations for a revised future version of the SLD and SE standards that resolves these issues.\r\n" + "@value": "The Common DataBase (CDB) Specification provides the means for a single, versionable, simulation-rich, synthetic representation of the earth. A database that conforms to this Specification is referred to as a Common DataBase or CDB. A CDB provides for a synthetic environment repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB can be used as a common on-line (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks; in this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time.\r\nThe application of CDB to future simulator architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the HLA/FOM and DIS protocols, the application of the CDB Specification provides a Common Environment to which inter-connected simulators share a common view of the simulated environment.\r\nThe CDB Specification is an open format Specification for the storage, access and modification of a synthetic environment database. The Specification defines the data representation, organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The Specification makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry.\r\nThe CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. It encompasses the terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the synthetic environment includes the specific attributes of the synthetic environment data as well as their relationships.\r\nA CDB contains datasets organized in layers, tiles and levels-of-detail; together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB is specifically tailored for real-time applications. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -265,35 +265,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-059" + "@value": "15-004" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Technical report from the DGIWG Portrayal Technical Panel testing of SLD (1.1.0) for OGC" + "@value": "OGC Common DataBase Volume 2 Appendices" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-071", + "@id": "http://www.opengis.net/def/docs/02-019r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-03-28" + "@value": "2002-02-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Charles Heazel" + "@value": "Jeff Lansing" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/ug" + "@id": "http://www.opengis.net/def/doc-type/ipr" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -303,27 +303,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/guides/20-071.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1121" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC API - Common - Users Guide" + "@value": "Coverage Portrayal Service" }, { "@language": "en", - "@value": "20-071" + "@value": "02-019r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/ug" + "@id": "http://www.opengis.net/def/doc-type/ipr" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC API — Common Standard is a multi-part Standard that specifies reusable building-blocks that can be used in the construction of OGC API Standards. The OGC API — Common — Users Guide presents information useful to developers or users of implementations of the OGC API — Common Standard. The information in the Users Guide is not normative. That is, it is not mandatory. However, it may prove essential to fully understand the normative text in the OGC API — Common Standard. The Users Guide is therefore intended to serve as an aid to developers and users." + "@value": "The Coverage Portrayal Service (CPS) IPR proposes a standard interface for producing visual pictures from coverage data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -334,35 +334,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-071" + "@value": "02-019r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Common - Users Guide" + "@value": "Coverage Portrayal Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-007r1", + "@id": "http://www.opengis.net/def/docs/16-031r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-08-20" + "@value": "2017-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gerhard Gröger, Thomas H. Kolbe, Angela Czerwinski, Claus Nagel" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -372,27 +372,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=28802" + "@id": "https://docs.ogc.org/per/16-031r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-007r1" + "@value": "16-031r1" }, { "@language": "en", - "@value": "City Geography Markup Language (CityGML) Encoding Standard" + "@value": "Testbed-12 GeoPackage Change Request Evaluations" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211.\r\n\r\nThe aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. \r\n" + "@value": "Testbed 12 work has resulted in Change Requests (CRs) to the GeoPackage Encoding Standard. CRs have been submitted to the GeoPackage Standards Working Group (SWG) as GitHub issues. This engineering report (ER) summarizes the results of these activities." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -403,35 +403,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-007r1" + "@value": "16-031r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS® City Geography Markup Language (CityGML) Encoding Standard" + "@value": "Testbed-12 GeoPackage Change Request Evaluations" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-010r11", + "@id": "http://www.opengis.net/def/docs/09-006", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-08-16" + "@value": "2009-08-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Lott" + "@value": "Keith Pomakis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -441,27 +441,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/18-010r11/18-010r11.pdf" + "@id": "https://portal.ogc.org/files/?artifact_id=33269" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geographic information — Well-known text representation of coordinate reference systems" + "@value": "09-006" }, { "@language": "en", - "@value": "18-010r11" + "@value": "OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Standard defines the structure and content of well-known text strings describing coordinate reference systems (CRSs) and coordinate operations between coordinate reference systems. It does not prescribe how implementations should read or write these strings.\r\nThis Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2019 including its amendments 1 and 2. It extends the WKT in OGC document 12-063r5 (ISO 19162) which was based on ISO 19111:2007 and ISO 19111-2:2009. That version consolidated several disparate versions of earlier WKT (so-called WKT1) and added the description of coordinate operations. \r\n" + "@value": "This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the development of SOAP/XML and REST interfaces for the Web Map Tiling Service (WMTS)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -472,35 +472,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-010r11" + "@value": "09-006" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geographic information — Well-known text representation of coordinate reference systems" + "@value": "OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-111", + "@id": "http://www.opengis.net/def/docs/02-026r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-01-25" + "@value": "2002-12-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Daniele Marchionni" + "@value": "Mike Botts" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -510,27 +510,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=45124" + "@id": "https://portal.ogc.org/files/?artifact_id=11516" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-111" + "@value": "02-026r4" }, { "@language": "en", - "@value": "Ordering Services for Earth Observation Products Adoption Voting Comments and Answers" + "@value": "Sensor Model Language (SensorML) for In-situ and Remote Sensors" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document lists the No votes received during the TC adoption vote (2011-05-03 - 2011-07-02) together with the responses from the OSEO SWG." + "@value": "The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -541,30 +541,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-111" + "@value": "02-026r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Ordering Services for Earth Observation Products Adoption Voting Comments and Answers" + "@value": "Sensor Model Language (SensorML) for In-situ and Remote Sensors" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-087r5", + "@id": "http://www.opengis.net/def/docs/15-067", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-18" + "@value": "2015-11-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Terry Idol, Robert Thomas" + "@value": "Gobe Hobona;Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -579,17 +579,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/18-087r5" + "@id": "https://portal.ogc.org/files/?artifact_id=63663" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Development of Disaster Spatial Data Infrastructures for Disaster Resilience" + "@value": "Testbed-11 Multi-dimensional GeoPackage Supporting Terrain and Routes Engineering Report" }, { "@language": "en", - "@value": "18-087r5" + "@value": "15-067" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -599,7 +599,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report presents the results of a concept development study on Disasters Interoperability, sponsored by US Geological Survey (USGS) and Federal Geographic Data Committee (FGDC), and Department of Homeland Security (DHS), and executed by the Open Geospatial Consortium (OGC). The focus of this study was to understand how to best support the development of, or combination of SDI(s) for the use in disasters, to advance the understanding of stakeholder issues, and serve stakeholders’ needs. The study included stakeholder engagements, workshops and open Request for Information (RFI) that gathered external international positions and opinions on the optimal setup and design of an SDI for disasters. The outflow of this report will guide a series of interoperability pilots to address priority challenges identified by the community in this study. The report follows the format and document of the OGC Arctic Spatial Data Pilot; Phase 1 Report: Spatial Data Sharing for the Arctic. " + "@value": "Routing is one of the most widely used functions of mobile applications. Routing often requires consideration of a variety of factors in order to provide reasonable estimations of journey time and the cost of travel. Another widely used function of mobile applications is the visualization of characteristics of terrain such as slope or viewsheds. The goal of this engineering report is to describe the work carried out in the OGC Testbed-11 for multidimensional terrain and routing support on SQLite databases that conform to the OGC GeoPackage standard. This OGC® Engineering Report (ER) describes an approach for the storage of routing and multidimensional terrain data in such databases. The ER also presents the results and lessons learnt from the experimentation conducted by the testbed." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -610,35 +610,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-087r5" + "@value": "15-067" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Development of Disaster Spatial Data Infrastructures for Disaster Resilience" + "@value": "OGC® Testbed-11 Multi-dimensional GeoPackage Supporting Terrain and Routes Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-047r2", + "@id": "http://www.opengis.net/def/docs/15-043r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-03-28" + "@value": "2016-09-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ron Lake" + "@value": "James Tomkins, Dominic Lowe " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -648,27 +648,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=11418" + "@id": "https://docs.ogc.org/is/15-043r3/15-043r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-047r2" + "@value": "15-043r3" }, { "@language": "en", - "@value": "GML in JPEG 2000 for Geographic Imagery" + "@value": "Timeseries Profile of Observations and Measurements " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The GML (Geography Markup Language) is an XML grammar for the encoding geographic information including geographic features, coverages, observations, topology, geometry, coordinate reference systems, units of measure, time, and value objects.\r\nJPEG 2000 is a wavelet based encoding for imagery that provides the ability to include XML data for description of the image within the JPEG 2000 data file.\r\nThis specification defines the means by which GML is to be used within JPEG 2000 images for geographic imagery. This includes the following:\r\n" + "@value": "The OGC Timeseries Profile of Observations and Measurements is a conceptual model for the representation of observations data as timeseries, with the intent of enabling the exchange of such data sets across information systems. This standard does not define an encoding for the conceptual model; however there is an accompanying OGC Standard which defines an XML encoding (OGC TimeseriesML 1.0 - XML Encoding of the Timeseries Profile of Observations and Measurements). Other encodings may be developed in future." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -679,35 +679,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-047r2" + "@value": "15-043r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML in JPEG 2000 for Geographic Imagery" + "@value": "Timeseries Profile of Observations and Measurements " } ] }, { - "@id": "http://www.opengis.net/def/docs/12-029", + "@id": "http://www.opengis.net/def/docs/17-026r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-04-04" + "@value": "2018-02-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Bastian Schäffer" + "@value": "Rob Cass" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -717,27 +717,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47860" + "@id": "https://docs.ogc.org/per/17-026r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Processing Service Best Practices Discussion Paper" + "@value": "17-026r1" }, { "@language": "en", - "@value": "12-029" + "@value": "Testbed-13: Disconnected Networks Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The following document contains best practices for identifying input data formats for the OGC WPS 1.0.0. It was created due to a lack of interoperability between different WPS implementation based on non-standardized input identifiers." + "@value": "The design of core OGC Web Services (OWS) does not entertain the possibility of network unavailability, internet unavailability, or disconnected clients and datastores. Deployments of these services, and the clients that consume them, often happen in networking environments that have limited bandwidth, sporadic connectivity and no connection to the internet. This Engineering Report (ER) focuses on situations of Denied, Degraded, Intermittent, or Limited Bandwidth (DDIL). Due to these DDIL networking limitations, OWS services and clients may not be capable of effective data exchange and interpretation due to a reliance on external resources and always-on networks.\r\n\r\nThis ER concerns the behavior of common OWS services when used in DDIL environments. The ER documents proposed practices/considerations for implementation of these services to support these environments. The ER also describes software modules or extensions that might mitigate the effects of these environments on both clients and services.\r\n\r\nThis ER intends to guide client and service implementation, as well as deployment strategies for these challenging environments.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -748,35 +748,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-029" + "@value": "17-026r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Processing Service Best Practices Discussion Paper" + "@value": "OGC Testbed-13: Disconnected Networks Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-011r1", + "@id": "http://www.opengis.net/def/docs/14-065", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-06-26" + "@value": "2015-03-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Martin Desruisseaux, Logan Stark" + "@value": "Matthias Mueller" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -786,27 +786,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-011r1.html" + "@id": "https://docs.ogc.org/is/14-065/14-065r0.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-011r1" + "@value": "WPS 2.0 Interface Standard" }, { "@language": "en", - "@value": "Testbed-18: 3D+ Data Space Object Engineering Report" + "@value": "14-065" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "With the growing commercialization of space there is a need to look beyond the earth and explore the integration of sensors or assets in celestial orbits or in free flight in our solar system. Their exact tracking and localization are becoming increasingly important as space emerges as the newest area in need for standard-based mechanisms for streaming and for data integration from various sensors.\r\n\r\nThis Open Geospatial Consortium (OGC) Testbed 18 3D+ Data Space Object Engineering Report (ER) describes existing standards in terms of their ability to represent a suite of multidimensional Coordinate Reference Systems (CRS) and associated geometries as well as identifies shortfalls in these standards." + "@value": "" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -817,30 +817,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-011r1" + "@value": "14-065" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-18: 3D+ Data Space Object Engineering Report" + "@value": "OGC® WPS 2.0 Interface Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-108", + "@id": "http://www.opengis.net/def/docs/21-044", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-05-15" + "@value": "2022-04-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "Luis Bermudez" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -855,17 +855,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46170" + "@id": "https://docs.ogc.org/per/21-044.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-108" + "@value": "21-044" }, { "@language": "en", - "@value": "OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report)" + "@value": "OGC Testbed 17: CITE Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -875,7 +875,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the usability of OGC services and encodings to implement the\r\nOWS-8 observation fusion and tracking thread in an abstract way. The real deployment\r\nand an actual perspective on the engineering and technology viewpoint can be found in\r\nOWS-8 engineering report OGC 11-134, ‘OWS-8 Tracking: Moving Target Indicator\r\nProcess, Workflows and Implementation Results’. In addition, it describes an XMLSchema\r\nbased implementation of the UML information models defined in OWS-8\r\nengineering report “Information Model for Moving Target Indicators and Moving Object\r\nBookmarks” (OGC 11-113).\r\nThe report is also based on the results of the VMTI/GMTI and STANAG 4676 realization\r\nin the OGC concept of operations study; performed as part of OWS 8 and the EC cofunded\r\nresearch project Emergency Support System - ESS” (contract number 217951)." + "@value": "This OGC Testbed 17 Engineering Report (ER) documents the result of the work performed in the CITE thread of the OGC Testbed-17 initiative. CITE is the Compliance Interoperability & Testing Evaluation Subcommittee that provides a forum for an open, consensus discussion regarding approaches and issues related to conformance and interoperability testing as part of the OGC standards process. This ER provides information about the development of a test suite for the OGC API — Processes Standard (OGC18-062r2) to be executed in the OGC Test Evaluation tool (TEAM Engine). The ER also documents an evaluation of an alternative environment for OGC compliance testing.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -886,35 +886,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-108" + "@value": "21-044" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report)" + "@value": "OGC Testbed 17: CITE Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-014", + "@id": "http://www.opengis.net/def/docs/05-005", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-01-05" + "@value": "2005-05-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Jerome Sonnet" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -924,27 +924,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-014.html" + "@id": "https://portal.ogc.org/files/?artifact_id=8618" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-18: Key Management Service Engineering Report" + "@value": "Web Map Context Implementation Specification" }, { "@language": "en", - "@value": "22-014" + "@value": "05-005" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 18 Engineering Report describes the Data Model and API of a Key Management Service (KMS) that supports the flexible but secure exchange of cryptographic keys for applying confidentiality and integrity protection to geographic information. The described KMS is based on the design and implementation from previous OGC Testbeds 16 and 17." + "@value": "This document is a companion specification to the OGC Web Map Service Interface Implementation Specification version 1.1.1 [4], hereinafter WMS 1.1.1. \r\nWMS 1.1.1 specifies how individual map servers describe and provide their map content. The present Context specification states how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent format for storage in a repository or for transmission between clients. This description is known as a Web Map Context Document, or simply a Context. Presently, context documents are primarily designed for WMS bindings. However, extensibility is envisioned for binding to other services.\r\nA Context document includes information about the server(s) providing layer(s) in the overall map, the bounding box and map projection shared by all the maps, sufficient operational metadata for Client software to reproduce the map, and ancillary metadata used to annotate or describe the maps and their provenance for the benefit of human viewers.\r\nA Context document is structured using eXtensible Markup Language (XML). Annex A of this specification contains the XML Schema against which Context XML can be validated.\r\n " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -955,35 +955,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-014" + "@value": "05-005" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-18: Key Management Service Engineering Report" + "@value": "OpenGIS Web Map Context Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-048r1", + "@id": "http://www.opengis.net/def/docs/02-102", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-03-10" + "@value": "2002-03-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Roel Nicolai" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -993,27 +993,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-048r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1220" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 OWS Common Security Extension ER" + "@value": "02-102" }, { "@language": "en", - "@value": "16-048r1" + "@value": "Topic 02 - Spatial Referencing by Coordinates" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC suite of standards address the interoperable exchange of geographic information. The Web Service Implementation Standards define the discovery, delivery, and processing services that make information exchange possible. Common aspects of those Web Service standards have been collected into the OGC Web Services Common standard. While there are multiple versions of OWS Common, and flexibility in how it is applied, this combination of standards does enable interoperability.\r\n\r\nHowever, OWS Common neglected to address security. As soon as a service endpoint (an OGC Web Service instance) is secured, there is no guarantee of interoperability.\r\n\r\nThe OWS Common - Security Standards Working Group (SWG) was approved by the TC in September 2015 (http://www.opengeospatial.org/projects/groups/comsecurityswg). It held its first meeting during the December 2015 TC meetings. The objective of this SWG to define an extension to the existing OWS Common to ensure interoperability between a secured service instance and client. This OWS Common Security Extension adds content to the standard regarding the implementation of security controls in such a way as to preserve interoperability. These additions will be in two areas. The first extension will provide more detail on the use of the HTTP protocol, particularly as it related to security controls. The second extension will address discovery and negotiation of security controls. This will provide an annotation model for the Capabilities document to enable a service provider to specify the security implemented at a service instance (endpoint).\r\n\r\nThis ER shall serve as the technical background to the OWS Common - Security SWG to ensure that the standard that is to be created is comprehensive and suitable for all OGC Web Services standards, to overcome the interoperability hurdle, and - at the same time - maintain backwards compatibility.\r\n\r\n" + "@value": "Describes modelling requirements for spatial referencing by coordinates. This document supplements and corrects ISO 19111. There has never been a motion to adopt 01-063r2. A motion was approved at the Dec 01 meeting in Vancouver to adopt 01-063r1" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1024,35 +1024,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-048r1" + "@value": "02-102" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 OWS Common Security Extension ER" + "@value": "Topic 2 - Spatial Referencing by Coordinates" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-079r1", + "@id": "http://www.opengis.net/def/docs/05-087r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-02-02" + "@value": "2006-04-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -1062,27 +1062,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=59983" + "@id": "https://portal.ogc.org/files/?artifact_id=14034" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "USGS OGC® Interoperability Assessment Report" + "@value": "Observations and Measurements" }, { "@language": "en", - "@value": "14-079r1" + "@value": "05-087r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The USGS Interoperability assessment was conducted under the OGC Interoperability\r\nProgram with the goal to better understand how USGS customers make use of OGC\r\ncompliant Web services operated by USGS. For this assessment, USGS customers have\r\nbeen invited to share their experiences and to describe their use cases and experiences\r\nmade with USGS data services and products. From those descriptions, recommendations\r\nhave been derived that help USGS to better understand their user community and\r\noptimize their service offerings." + "@value": "The general models and XML encodings for observations and measurements, including but not restricted to those using sensors." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1093,35 +1093,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-079r1" + "@value": "05-087r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "USGS OGC® Interoperability Assessment Report" + "@value": "Observations and Measurements" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-128r10", + "@id": "http://www.opengis.net/def/docs/23-047", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-10" + "@value": "2024-07-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Daisey" + "@value": "Alexander Jacob" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -1131,27 +1131,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=56357" + "@id": "https://docs.ogc.org/per/23-047.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GeoPackage Encoding Standard" + "@value": "23-047" }, { "@language": "en", - "@value": "12-128r10" + "@value": "OGC Testbed-19 GeoDataCubes Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. \r\n

\r\nFor the online version of the standard and the developer resources, visit http://www.geopackage.org/" + "@value": "OGC Testbed-19 has continued and furthered an ongoing discussion about how to interact with GeoDataCubes (GDC) in the most interoperable way (see Chapter 1 for more Introduction). Testbed 19 participants produced a draft OGC GDC API standard that incorporates the most relevant developments in the field in and outside of OGC. This work advanced the common understanding of available solutions while discovering to a much better degree the advantages and drawbacks of current solutions. Testbed 19 participants produced prototypes of five back-end implementations and six client implementations as well as an automated test suite, which are described in full detail in Chapter 4. Many of the researched solutions are also available as open source and hence offer a perfect starting point for further GDC activities.\r\n\r\nThe main technologies that were evaluated in Testbed 19 included the OGC API Standards suite1, the openEO API2 and the Spatiotemporal Asset Catalog3 (STAC) specification. Based on cross walk comparisons (see Chapter 2), a unified draft GDC API was developed integrating as much as possible the existing solutions. openEO is largely compliant with the OGC API- Common Standard. As such, the openEO API specification provided the foundation for defining a draft OGC GDC API draft standard. During the Testbed 19 period, more building blocks from the OCG API were incorporated into the draft GDC API document. These building blocks included parts of OGC API — Common, OGC API — Coverages, and OGC API – Processes. There is also future potential for visualization services through maps or tiles or even including components or elements of the OGC Web Services suite of Standards, such as WMS, WMTS, WCS, etc.\r\n\r\nThe current version of the draft GDC API, described in D71 of T19, supports different scenarios enabling implementations of the draft standard to offer only minimal support for data access with minimal manipulation of the data. Minimal manipulation is in terms of subsetting and reprojecting or including more advanced processing capabilities by incorporating building blocks from the openEO specification or from the OGC API — Processes – Part 1: Core Standard. Chapter 3 gives an overview of the draft standard.\r\n\r\nThe interaction capabilities between the different servers and clients developed are described in Chapter 5 and first impressions on usability in Chapter 6.\r\n\r\nFuture work could include the ability to link two processing options into one “integrated” option that supports either submitting openEO process graphs to a OGC API – Processes endpoint (extending and working on Processes — Part 3), or supports integration of an OGC API – Processes process in the process graph of openEO through an extended concept of user defined functions in openEO. Further discussion is also needed on the pros and cons of including authentication in the draft standard. More details about lessons learned and suggestions can be found in Chapters 7 and 8 of this ER." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1162,30 +1162,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-128r10" + "@value": "23-047" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GeoPackage Encoding Standard" + "@value": "OGC Testbed-19 GeoDataCubes Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-044", + "@id": "http://www.opengis.net/def/docs/21-042", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-04-26" + "@value": "2021-11-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Eugene Yu, Liping Di" + "@value": "Gobe Hobona" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -1200,17 +1200,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-044.html" + "@id": "https://docs.ogc.org/per/21-042.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-044" + "@value": "21-042" }, { "@language": "en", - "@value": "OGC Testbed 19 High Performance Geospatial Computing Engineering Report" + "@value": "May 2021 OGC API Code Sprint Summary Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -1220,7 +1220,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Large-scale geospatial analytical computation is critically needed for tackling a wide range of sustainability problems, such as climate change, disaster management, and food and water security. However, such computation often requires high-performance computing (HPC) resources that are not easily accessible or usable by geospatial researchers and practitioners from various domains. To address this challenge, there is a need for developing and standardizing tools and interfaces that can bridge the gap between user frontend and HPC backends and enable effective and efficient use of High-Performance Geospatial Computing (HPGC) resources for geospatial analytics.\r\n\r\nThis OGC Testbed 19 Engineering Report (ER) presents the results of a testbed task that:\r\n\r\n* evaluated previous and current work in the application of HPC for geospatial analytics, and\r\n* developed draft standards for HPGC resource definitions and processing interfaces.\r\n\r\nThis ER provides an overview of the Testbed 19 motivation, objectives, scope, and methodology, as well as a summary of the main findings, recommendations, and future work directions.\r\n\r\nCyberGIS-Compute is reviewed and used as a reference to develop the HPGC API. “CyberGIS-Compute is an open-sourced geospatial middleware framework that provides integrated access to high-performance computing (HPC) resources through a Python-based SDK and core middleware services.”<> The OGC API - Processes<> is adopted as the base API for standardizing and developing the HPGC API. A Python client library is developed to demonstrate the process of client generation by leveraging the OpenAPI client stub/model automatic generation capability<>. Typical use cases and scenarios are demonstrated and scripted in Jupyter Notebooks." + "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from 26 to 28 May 2021 to advance the development of the OGC API - Maps draft standard, OGC API - Tiles draft standard, and the OGC API – Styles draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The code sprint was hosted online. The code sprint was sponsored by Ordnance Survey (OS) and Natural Resources Canada (NRCan)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1231,35 +1231,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-044" + "@value": "21-042" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed 19 High Performance Geospatial Computing Engineering Report" + "@value": "May 2021 OGC API Code Sprint Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-121r9", + "@id": "http://www.opengis.net/def/docs/18-041r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-04-07" + "@value": "2018-10-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside, Jim Greenwood " + "@value": "Gobe Hobona, Bart De Lathouwer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -1269,27 +1269,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=38867" + "@id": "https://docs.ogc.org/dp/18-041r1/18-041r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Service Common Implementation Specification" + "@value": "18-041r1" }, { "@language": "en", - "@value": "06-121r9" + "@value": "Geospatial Standardization of Distributed Ledger Technologies" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Standards. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Standard must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses." + "@value": "This discussion paper is organized as follows.\r\n\r\nBackground: This section introduces DLT and blockchain, as well as the structure of blocks.\r\n\r\nCase Studies: This section presents an overview of example projects that use or are studying blockchain within a geospatial context.\r\n\r\nCurrent Standardization Initiatives: This section presents an overview of a selection of standardization initiatives involving blockchain and geospatial data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1300,35 +1300,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-121r9" + "@value": "18-041r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Service Common Implementation Specification" + "@value": "Geospatial Standardization of Distributed Ledger Technologies" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-000", + "@id": "http://www.opengis.net/def/docs/20-039r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-05-08" + "@value": "2021-01-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Robert Gibb, Byron Cochrane, Matthew Purss" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -1338,27 +1338,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/18-000/18-000.html" + "@id": "https://docs.ogc.org/per/20-039r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-000" + "@value": "DGGS and DGGS API Engineering Report" }, { "@language": "en", - "@value": "GeoPackage Related Tables Extension" + "@value": "20-039r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A GeoPackage [geopackage] is a platform-independent SQLite [sqlite] database file that contains GeoPackage data and metadata tables. GeoPackages, as described by the GeoPackage Encoding Standard [GPKG1_2] are designed to be extensible, including support for additional data types. This document defines the Related Tables Extension (RTE) for the GeoPackage Encoding Standard.\r\n\r\nThe RTE defines the rules and requirements for creating relationships in a GeoPackage data store between geospatial data tables and other tables that contain or reference related content such as attributes or media. Geospatial data tables (such as features or tiles tables) contain location information and/or geometries. There are many examples of where the RTE can be used including relating parcel (land lot) features to pictures of that parcel or linking census boundaries to the related demographic census data." + "@value": "This OGC Testbed-16 Engineering Report (ER) documents the needs and key requirements for drafting an OGC Discrete Global Grid Systems (DGGS) Application Programming Interface (API) standard. The draft DGGS API is defined using the OpenAPI 3.0 specification. The work documented in this ER represents the beginning of a multi-initiative process to fully realize the benefits of standards compliant DGGS implementations and to help drive adoption of DGGS as a key element in advanced Spatial Data Architectures. The Testbed participants investigated a Client-Server DGGS architecture involving one (or more) DGGS Server implementations, DGGS-enabled Data Sources and a simple front-end DGGS Client. DGGS API functionality will be tested using one (or more) simple use case scenarios focusing on the two-way translation between geographic locations and DGGS Zonal Identifiers." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1369,35 +1369,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-000" + "@value": "20-039r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoPackage Related Tables Extension" + "@value": "OGC Testbed-16: DGGS and DGGS API Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-021r4", + "@id": "http://www.opengis.net/def/docs/15-113r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-08-20" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": " Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -1407,27 +1407,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=29405" + "@id": "https://docs.ogc.org/is/15-113r6/15-113r6.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC® Sensor Web Enablement Architecture" + "@value": "15-113r6" }, { "@language": "en", - "@value": "06-021r4" + "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the architecture implemented by Open Geospatial Consortium’s (OGC) Sensor Web Enablement Initiative (SWE). In contrast to other OGC SWE stan-dards, this document is not an implementation standard." + "@value": "The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1438,35 +1438,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-021r4" + "@value": "15-113r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Web Enablement Architecture" + "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-064r10", + "@id": "http://www.opengis.net/def/docs/14-115", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-05-04" + "@value": "2015-01-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Greg Reynolds" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -1476,27 +1476,37 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=10378" + "@id": "https://portal.ogc.org/files/61188" + }, + { + "@id": "https://portal.ogc.org/files/?artifact_id=61188" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geographic Objects Implementation Specification *RETIRED*" + "@value": "OGC Smart Cities Spatial Information Framework" }, { "@language": "en", - "@value": "03-064r10" + "@value": "Smart Cities Spatial Information Framework" + }, + { + "@language": "en", + "@value": "14-115" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*THIS STANDARD HAS BEEN RETIRED*\r\n\r\nThe OpenGIS® Geographic Objects Interface Standard (GOS) provides an open set of common, lightweight, language-independent abstractions for describing, managing, rendering, and manipulating geometric and geographic objects within an application programming environment. It provides both an abstract object standard (in UML) and a programming-language-specific profile (in Java). The language-specific bindings serve as an open Application Program Interface (API)." + "@value": "This White Paper supports development of a Smart Cities Spatial Information Framework\r\nbased on these themes:\r\nK Smart Cities are high-density generators of innovation and information.\r\nK Location information is a major enabler of Smart City technology benefits.\r\nK Benefits of smart technology must be judged by benefits to residents.\r\nK Reuse and repurpose is vital to urban resilience\r\nK Open standards are needed for interoperability, efficiency, application innovation\r\nand cost effectiveness.\r\nDiscussion of these themes and this white paper will occur at the OGC Smart Cities\r\nLocation Powers Summit in Tokyo on December 2, 2014,\r\n1 the co-located OGC Technical\r\nCommittee meeting, and in many other forums in the future. As described in this paper,\r\nthere are many standards initiatives that focus on Smart Cities. Most Smart Cities use\r\ncases in some way involve indoor and/or outdoor location, and thus communication about\r\nlocation is an issue that cuts across the work programs most of the standards\r\norganizations that are involved with Smart Cities.\r\nThis white paper builds on the OGC - Directions Magazine webinar: “Making Location\r\nWork for Smart Cities – the Case for Location Standards”2." + }, + { + "@value": "This White Paper supports development of a Smart Cities Spatial Information Framework\r\nbased on these themes:\r\n- Smart Cities are high-density generators of innovation and information.\r\n- Location information is a major enabler of Smart City technology benefits.\r\n- Benefits of smart technology must be judged by benefits to residents.\r\n- Reuse and repurpose is vital to urban resilience\r\n- Open standards are needed for interoperability, efficiency, application innovation\r\nand cost effectiveness.\r\nDiscussion of these themes and this white paper will occur at the OGC Smart Cities\r\nLocation Powers Summit in Tokyo on December 2, 2014,1 the co-located OGC Technical\r\nCommittee meeting, and in many other forums in the future. As described in this paper,\r\nthere are many standards initiatives that focus on Smart Cities. Most Smart Cities use\r\ncases in some way involve indoor and/or outdoor location, and thus communication about\r\nlocation is an issue that cuts across the work programs most of the standards\r\norganizations that are involved with Smart Cities.\r\nThis white paper builds on the OGC - Directions Magazine webinar: “Making Location\r\nWork for Smart Cities – the Case for Location Standards”2." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1507,35 +1517,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-064r10" + "@value": "14-115" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Geographic Objects Implementation Specification *RETIRED*" + "@value": "OGC Smart Cities Spatial Information Framework" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-073r1", + "@id": "http://www.opengis.net/def/docs/05-029r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-10-16" + "@value": "2005-08-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roel Nicolai" + "@value": "Ron Lake, Carl Reed, George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -1545,27 +1555,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=11518" + "@id": "https://portal.ogc.org/files/?artifact_id=11606" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 2 - Spatial Referencing by Coordinates" + "@value": "05-029r4" }, { "@language": "en", - "@value": "03-073r1" + "@value": "GML Point Profile" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Describes modelling requirements for spatial referencing by coordinates." + "@value": "This document defines a profile of the Geography Markup Language (GML) for a point geometry. Attention is drawn to the fact that this is a profile of GML version 3.1.1. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1576,35 +1586,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-073r1" + "@value": "05-029r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 2 - Spatial Referencing by Coordinates" + "@value": "GML Point Profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-004", + "@id": "http://www.opengis.net/def/docs/04-011r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-03-24" + "@value": "2004-05-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Peter Schut" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -1614,27 +1624,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=98574" + "@id": "https://portal.ogc.org/files/?artifact_id=5859" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Release Notes for OGC GeoPackage 1.3.1" + "@value": "04-011r1" }, { "@language": "en", - "@value": "21-004" + "@value": "Geolinking Service" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the set of revision notes for Geopackage 1.3.1 and does not modify that Standard.\r\n\r\nThis document provides the details of edits, deficiency corrections, and enhancements of the above-referenced Standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility." + "@value": "A Geolinking Service takes attribute data which refers to spatial features, and joins it to a geospatial dataset, so that it can be mapped by a WMS or used in a GIS. When a Geolinking Service uses data from a GDAS, and serves as a front end to a WMS, it enables real-time mapping of data stored in non-spatial databases." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1645,35 +1655,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-004" + "@value": "04-011r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Release Notes for OGC GeoPackage 1.3.1" + "@value": "Geolinking Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-050", + "@id": "http://www.opengis.net/def/docs/03-053r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-04-26" + "@value": "2003-05-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lucio Colaiacomo" + "@value": "Carl Reed, George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-atb" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -1683,27 +1693,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-050.html" + "@id": "https://portal.ogc.org/files/?artifact_id=3835" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-19 Agile Reference Architecture Engineering Report" + "@value": "03-053r1" }, { "@language": "en", - "@value": "23-050" + "@value": "OGC Technical Document Baseline" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-atb" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The concepts of agile architecture and reference architecture may not be new ideas in information or geospatial technologies, but what is meant by the term Agile Reference Architecture?\r\n\r\nAgile Reference Architecture is the long-term vision of the complex and changing nature of how problems will be solved in the future within the location-referenced and geospatial realms. This includes consideration of network availability, as containers integrated with Linked Data, and Application Programming Interfaces (APIs) serve data as secure, trusted, and self-describing resources.\r\n\r\nWhile the Open Geospatial Consortium (OGC) focuses on geospatial information and technologies, that community is also dependent on the overall state of information and communications technology (ICT), including developing cyber, cryptographic, and internet technologies.\r\n\r\nIn today’s infrastructures, the collection, exchange, and continuous processing of geospatial resources typically happens at pre-defined network endpoints of a spatial data infrastructure. Each participating operator hosts some capability at a network endpoint. Whereas some network operator endpoints may provide data access, other endpoints provide processing functionality and other endpoints may support the uploading of capabilities. In other words, such an infrastructure is not agile in the sense that it cannot adapt by itself to meet the needs of the moment. One of the biggest challenges resulting from the static characteristics is ensuring effective and efficient operations of the overall system and at the same time maintaining trust and provenance.\r\n\r\nThis OGC Testbed 19 Engineering Report (ER) outlines novel concepts for establishing a federated agile infrastructure of collaborative trusted systems (FACTS) that is capable of acting autonomously to ensure fit-for-purpose cooperation across the entire system. One of the key objectives is to not create a new data product, but instead a collaborative object is offered leveraging FACTS that allows for obtaining the data product via well-defined interfaces and functions provided by the collaborative object.\r\n\r\nTrust and assurance are two key aspects when operating a network of collaborative objects leveraging STANAG 4774/4778. STANAG 4774 outlines the metadata syntax required for a confidentiality label to better facilitate and protect sensitive information sharing. In addition, STANAG 4778 defines how a confidentiality label is bound to the data throughout its lifecycle and between the sharing parties.The agile aspect is achieved by the object’s ability to activate, deactivate, and order well-defined capabilities from other objects. These capabilities are encapsulated in building blocks. Each building block is well defined in terms of accessibility, functionality, and ordering options. This allows building blocks to roam around collaborative objects as needed to ensure a well-balanced network load and suitable processing power of individual nodes from the network.\r\n\r\nEqually trusted partners in the infrastructure participate in FACTS. They can collect data from other partners and create derived products via collaborative objects. The sharing of data products is only possible directly, meaning direct communication with data consumer and it is only possible via the objects. This guarantees that fundamental trust operations are applied to the data and provenance records are produced before the data product is made available to others. The use of Blockchain technology and Smart contracts is one example of how this fundamental behavior can be planted into collaborative objects. As in trusted networks that are using Evaluation Assurance Level (EAL) approved hardware and software components, the objects will have to undergo a similar assurance process.\r\n\r\nFor ensuring the acceptance and interoperability of an agile reference architecture, built on top of FACTS with collaborative objects and building blocks, standardization is a key aspect. In particular, the core (fundamental) requirements for FACTS as well as the interfaces and capabilities of the collaborative objects and pluggable building blocks should be standardized. The OGC provides a consensus based collaborative standardization environment fits these requirements very well." + "@value": "Spreadsheet of OGC Technical Document Baseline" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1714,30 +1724,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-050" + "@value": "03-053r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-19 Agile Reference Architecture Engineering Report" + "@value": "OGC Technical Document Baseline" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-075r1", + "@id": "http://www.opengis.net/def/docs/09-182r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-05-06" + "@value": "2010-02-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sylvain Grellet, Eric Boisvert, Bruce Simons, Jean-François Rainaud, Henning Lorenz, Rainer Haener" + "@value": "Josh Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -1752,17 +1762,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/19-075r1" + "@id": "https://portal.ogc.org/files/?artifact_id=36889" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-075r1" + "@value": "09-182r1" }, { "@language": "en", - "@value": "Borehole Interoperability Experiment Engineering Report" + "@value": "End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -1772,7 +1782,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes a conceptual model, logical model, and GML/XML encoding schema for the exchange of borehole related data and especially all the elements that are positioned along a borehole trajectory. In addition, this document provides GML/XML encoding instances documents for guidance" + "@value": "This Architecture Implementation Pilot, Phase 2 Engineering Report (AIP-2 ER) describes the practice of deploying, documenting, and registering contributed resources from the point of view of classes of GEOSS users who rely on GEOSS to support discovery and access to those resources. It emphasizes two paradigms for the GEOSS Common Infrastructure: 1) Service-oriented infrastructure for development of service-based community applications by technically advanced users; and 2) Content-oriented search facility and Web-based access mechanisms for end-users with a range of technical skills and domain knowledge. End-to-end here refers to the bidirectional connection between desired discovery practices and goals on the user end; and the required resource interfaces and documentation on the provider end." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1783,35 +1793,39 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-075r1" + "@value": "09-182r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Borehole Interoperability Experiment Engineering Report" + "@value": "End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-083r2", + "@id": "http://www.opengis.net/def/docs/14-095", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-15" + "@value": "2015-01-22" + }, + { + "@type": "xsd:date", + "@value": "2015-01-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Eric Hirschorn" + "@value": "Lance McKee" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -1821,27 +1835,37 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/16-083r2/16-083r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=60920" + }, + { + "@id": "https://portal.ogc.org/files/60920" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-083r2" + "@value": "Information Technology Standards for Sustainable Development" }, { "@language": "en", - "@value": "Coverage Implementation Schema - ReferenceableGridCoverage Extension" + "@value": "OGC Information Technology Standards for Sustainable Development" + }, + { + "@language": "en", + "@value": "14-095" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC GML Application Schema - Coverages (“GMLCOV”) version 1.0 [OGC 09-146r2], recently renamed the OGC Coverage Implementation Schema version 1.0, provides a ReferenceableGridCoverage element for representing coverages on a referenceable grid. However, GMLCOV provides no instantiable subtypes of a critical sub-element of ReferenceableGridCoverage, GMLCOV::AbstractReferenceableGrid. To make use of ReferenceableGridCoverage, an extension deriving from GMLCOV would need to be developed. GML 3.3 is not such an extension of GMLCOV, as it is built independently from GMLCOV. Use of the instantiable referenceable grid elements of GML 3.3 with ReferenceableGridCoverage violates Requirement 14 of GMLCOV 1.0 and Requirement 24 of the OGC Modular Specification[1].\r\n\r\nThis OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension provides a set of referenceable grid elements for use as sub-elements of ReferenceableGridCoverage. Three of these elements have been adapted from GML 3.3, while a fourth emerged from work on a Testbed-11 Engineering Report[2]." + "@value": "Sustainable development, meeting the needs of the present without compromising the ability of future generations to meet their own needs, will be accomplished by balancing social, economic and environmental objectives. In this paper the authors explain that rigorous standards for communicating environmental data are absolutely essential to enable social and economic progress in the Age of the Environment – the Anthropocene Epoch – in which humanity's expanding footprint has become the main cause of change in the planet's geology, water bodies, atmosphere and biosphere. The authors argue for a concerted and ongoing global effort to 1) define data communication and system interoperability requirements for environmental science, business and policy, and then 2) develop and implement consensus-derived, free and open environmental Information Technology (IT) standards that meet those requirements and that co-evolve with the larger IT standards framework and advances in IT." + }, + { + "@value": "Sustainable development, meeting the needs of the present without compromising the\r\nability of future generations to meet their own needs,1\r\n will be accomplished by\r\nbalancing social, economic and environmental objectives. In this paper the authors\r\nexplain that rigorous standards for communicating environmental data are absolutely\r\nessential to enable social and economic progress in the Age of the Environment2 – the\r\nAnthropocene Epoch3 – in which humanity's expanding footprint has become the main\r\ncause of change in the planet's geology, water bodies, atmosphere and biosphere. The\r\nauthors argue for a concerted and ongoing global effort to 1) define data communication\r\nand system interoperability requirements for environmental science, business and policy,\r\nand then 2) develop and implement consensus-derived, free and open environmental\r\nInformation Technology (IT) standards that meet those requirements and that co-evolve\r\nwith the larger IT standards framework and advances in IT." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1852,35 +1876,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-083r2" + "@value": "14-095" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension" + "@value": "OGC Information Technology Standards for Sustainable Development" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-098", + "@id": "http://www.opengis.net/def/docs/15-120r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-13" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Michael Gerlek" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cr" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -1890,27 +1914,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20257" + "@id": "https://docs.ogc.org/bp/15-120r6.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Proposal for WCS Transactional - WCS-T" + "@value": "Volume 0: OGC CDB Companion Primer for the CDB standard (Best Practice)" }, { "@language": "en", - "@value": "06-098" + "@value": "15-120r6" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cr" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Version 1.0 of the Web Coverage Service (WCS) Specification does not address how coverage data gets added to or deleted from a server; it is assumed that some implementation-specific process exists for handling this, likely on the back end (server-side). One of the goals of OWS-4 was to extend WCS to support these operations, generally referred to as " + "@value": "The CDB standard defines a standardized model and structure for a single, “versionable,” virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1921,35 +1945,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-098" + "@value": "15-120r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Change Request: WCS: Proposal for WCS Transactional - WCS-T" + "@value": "Volume 0: OGC CDB Companion Primer for the CDB standard (Best Practice)" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-127r2", + "@id": "http://www.opengis.net/def/docs/21-075", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-01-25" + "@value": "2022-05-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Tom O’Reilly " + "@value": "Andrew Lavender, Samantha Lavender " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/ug" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -1959,27 +1983,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47604" + "@id": "https://docs.ogc.org/guides/21-075.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC® PUCK Protocol Standard " + "@value": "21-075" }, { "@language": "en", - "@value": "09-127r2" + "@value": "OGC Disaster Pilot: User Readiness Guide" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/ug" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard defines a protocol for RS232 and Ethernet connected instruments. PUCK addresses installation and configuration challenges for sensors by defining a standard instrument protocol to store and automatically retrieve metadata and other information from the instrument device itself." + "@value": "Improving the ability of key disaster decision makers and responders to discover, manage, access, transform, share, and exploit location-based and Earth Observation data will enhance decision making and, hopefully, save lives. The OGC Disaster Pilot 2021 has developed a number of prototype capabilities to demonstrate solutions for providing consistent, and reliable information to enable real-time actions to be taken using multiple technologies working together through pre-agreed standards.\r\n\r\nThis User Guide describes how the solution works, how users can be part of it, and showcases what can be achieved if everyone is willing to work together and share data and knowledge to improve the information available to those responding to a disaster." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -1990,35 +2014,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-127r2" + "@value": "21-075" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® PUCK Protocol Standard " + "@value": "OGC Disaster Pilot: User Readiness Guide" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-067r5", + "@id": "http://www.opengis.net/def/docs/07-038", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-04-29" + "@value": "2007-06-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Nicolas Lesage, Marie-Lise Vautier" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -2028,27 +2052,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27297" + "@id": "https://portal.ogc.org/files/?artifact_id=20596" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Service (WCS) Implementation Standard" + "@value": "Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W" }, { "@language": "en", - "@value": "07-067r5" + "@value": "07-038" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Web Coverage Service Interface Standard (WCS) defines a standard interface and operations that enables interoperable access to geospatial coverages [http://www.opengeospatial.org/ogc/glossary/c]. The term grid coverages typically refers to content such as satellite images, digital aerial photos, digital elevation data, and other phenomena represented by values at each measurement point. " + "@value": "This document extends the ebRIM application profile of CS-W for the cataloguing of ISO 19115 and ISO 19119 compliant metadata." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2059,30 +2083,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-067r5" + "@value": "07-038" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Coverage Service (WCS) Implementation Standard" + "@value": "OGC Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-066r1", + "@id": "http://www.opengis.net/def/docs/11-014r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-03-07" + "@value": "2014-05-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Stanislav Vanecek, Roger Moore" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -2097,17 +2121,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/17-066r1/17-066r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=59022" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-066r1" + "@value": "Open Modelling Interface Interface Standard" }, { "@language": "en", - "@value": "GeoPackage Extension for Tiled Gridded Coverage Data" + "@value": "11-014r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -2117,7 +2141,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The “GeoPackage Extension for Tiled Gridded Coverage Data” extension (previously titled Elevation Extension) defines how to encode and store tiled regular gridded data, such as a digital elevation model, in a GeoPackage. In the ISO 19123 Schema for Coverage Geometry standard and in the OGC Coverage Implementation Schema, this type of regular gridded data is classed as grid-regular[1]. The tiles contain values, such as elevation, temperature or pressure, and may be stored as 16-bit PNG files or 32-bit TIFF files. The extension defines two ancillary data tables: one for regular gridded coverages and one for tiles. When using the PNG encoding, a scale and offset may be applied. The extension also allows for a TIFF encoding but constrains many of the TIFF options that are available to simplify development." + "@value": "

The purpose of the Open Modelling Interface (OpenMI) is to enable the runtime exchange of data between process simulation models and also between models and other modelling tools such as databases and analytical and visualization applications. Its creation has been driven by the need to understand how processes interact and to predict the likely outcomes of those interactions under given conditions. A key design aim has been to bring about interoperability between independently developed modelling components, where those components may originate from any discipline or supplier. The ultimate aim is to transform integrated modelling into an operational tool accessible to all and so open up the potential opportunities created by integrated modelling for innovation and wealth creation. \r\n

\r\n

\r\nThis document defines the requirements that a component must meet to achieve OpenMI compliance. These comprise: 1) a very thin core set of requirements covering the information and functions needed to establish a link and make an exchange between two components and 2) a set of optional extensions for handling more complex situations. The document does not describe how to implement the standard. This information together with a range of software tools for creating and running OpenMI-­‐compliant components are provided by the OpenMI Association and third-­‐party software vendors – visit www.openmi.org for further documentation.

\r\n

\r\npdf
\r\ndocx\r\n

" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2128,35 +2152,38 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-066r1" + "@value": "11-014r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoPackage Extension for Tiled Gridded Coverage Data" + "@value": "OGC Open Modelling Interface Interface Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-004", + "@id": "http://www.opengis.net/def/docs/02-058", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-12-11" + "@value": "2002-05-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Kyoung-Sook Kim, Jiyeong Lee" + "@value": "Peter Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-is" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-sap" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -2166,27 +2193,34 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/19-004.html" + "@id": "https://portal.ogc.org/files/?artifact_id=7176" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Anchor Node Extension in IndoorGML - Seamless Navigation between Indoor and Outdoor Space" + "@value": "Web Feature Service" }, { "@language": "en", - "@value": "19-004" + "@value": "Web Feature Service (Transactional)" + }, + { + "@language": "en", + "@value": "02-058" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-sap" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC discussion paper provides an extension module of OGC Indoor Geography Markup Language (IndoorGML) for the seamless navigation between indoor and outdoor spaces. The OGC IndoorGML standard has an issue on the data model that affects the connection of indoor and outdoor spaces via an “Anchor Node,” which is a conceptual part for connecting indoor and outdoor spaces. This discussion paper aims to show use cases of how IndoorGML can connect with other geospatial standards that represent outdoor spaces (and road networks), such as OGC City Geography Markup Language (CityGML) and version 5.0 of the Geographic Data Files (GDF) format." + "@value": "The purpose of the Web Feature Server Interface Specification (WFS) is to describe data manipulation operations on OpenGIS" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2197,35 +2231,39 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-004" + "@value": "02-058" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Anchor Node Extension in IndoorGML - Seamless Navigation between Indoor and Outdoor Space" + "@value": "Web Feature Service (Transactional)" + }, + { + "@language": "en", + "@value": "Web Feature Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-002r3", + "@id": "http://www.opengis.net/def/docs/21-050r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-12-26" + "@value": "2022-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Zarr Developers" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -2235,27 +2273,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=22467" + "@id": "https://portal.ogc.org/files/100727" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-002r3" + "@value": "Zarr Storage Specification 2.0 Community Standard" }, { "@language": "en", - "@value": "Observations and Measurements - Part 2 - Sampling Features" + "@value": "21-050r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Observations and Measurements Encoding Standard (O&M) defines an abstract model and an XML schema [www.w3.org/XML/Schema] encoding for observations and it provides support for common sampling strategies. O&M also provides a general framework for systems that deal in technical measurements in science and engineering. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. " + "@value": "This Community Standard refers to the Zarr V2 Specification. The Zarr V2 Specification\r\nis hosted on the Zarr website at https://zarr.readthedocs.io/en/stable/spec/v2.html. The\r\nZarr V2 Specification is the OGC Community Standard. Everything that follows is a\r\nnon-normative, informal description of Zarr usage written for the benefit of the geospatial\r\ncommunity." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2266,35 +2304,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-002r3" + "@value": "21-050r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Observations and Measurements - Part 2 - Sampling Features" + "@value": "Zarr Storage Specification 2.0 Community Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-184r2", + "@id": "http://www.opengis.net/def/docs/08-091r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-14" + "@value": "2009-09-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Christian Elfers, Roland M. Wagner" + "@value": "Peter Schut" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -2304,27 +2342,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21285" + "@id": "https://portal.ogc.org/files/?artifact_id=32766" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-184r2" + "@value": "08-091r6" }, { "@language": "en", - "@value": "GeoDRM Engineering Viewpoint and supporting Architecture" + "@value": "Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This GeoDRM engineering viewpoint document describes use cases and concepts for GeoDRM, as well as references to distributed computing concepts which are not GeoDRM sensu stricto but are required for any GeoDRM implementation. " + "@value": "This document provides the details for a corrigendum for the existing OpenGIS Standard for the Web Processing Service version 1.0.0 and does not modify that standard. The current OpenGIS Implementation Standard that this document provides revision notes for is 05-007r7. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2335,35 +2373,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-184r2" + "@value": "08-091r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GeoDRM Engineering Viewpoint and supporting Architecture" + "@value": "Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-085r1", + "@id": "http://www.opengis.net/def/docs/10-134", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-03-08" + "@value": "2010-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "USGIF & OGC" + "@value": "Arne Broering, Stefan Below" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -2373,27 +2411,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://usgif.org/usgif_msgwg_ogc_technical_paper_march_2021/" + "@id": "https://portal.ogc.org/files/?artifact_id=39664" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Advancing the Interoperability of Geospatial Intelligence Tradecraft with 3D Modeling, Simulation, and Game Engines" + "@value": "Sensor Interface Descriptors" }, { "@language": "en", - "@value": "20-085r1" + "@value": "10-134" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The objectives of this MS&G\r\nTechnical Paper are focused on identifying technology trends\r\nthat are influencing the convergence of GEOINT and M&S\r\ntradecraft. The purpose is to advance ideas and techniques,\r\nsuch as reality modeling of 3D environments, which increase\r\nthe knowledge-base and capacity of the geospatial analyst\r\ncommunity writ large." + "@value": "This document presents the Sensor Interface Descriptor (SID) schema that enables the declarative description of sensor interfaces, including the definition of the communication protocol, sensor commands, processing steps and metadata association. This schema is designed as a profile and extension of SensorML. Based on this schema, SID interpreters can be implemented, independently of particular sensor technology, which are able to translate between sensor protocol and SWE protocols. They establish the connection to a sensor and are able to communicate with it by using the sensor protocol definition of the SID. SID instances for particular sensor types can be reused in different scenarios and can be shared among user communities. The ability of an SID interpreter to connect sensors and Sensor Web services in an ad hoc manner based on the sensor’s SID instance is a next step towards realizing sensor plug & play within the Sensor Web." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2404,35 +2442,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-085r1" + "@value": "10-134" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Advancing the Interoperability of Geospatial Intelligence Tradecraft with 3D Modeling, Simulation, and Game Engines" + "@value": "Sensor Interface Descriptors" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-011", + "@id": "http://www.opengis.net/def/docs/05-033r9", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-01-28" + "@value": "2005-07-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Peter Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -2442,27 +2480,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8837" + "@id": "https://portal.ogc.org/files/?artifact_id=11266" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Recommended XML/GML 3.1.1 encoding of common CRS definitions" + "@value": "GML simple features profile" }, { "@language": "en", - "@value": "05-011" + "@value": "05-033r9" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document recommends standard XML encodings of data defining some commonly-used coordinate reference systems, including geographic, projected, and vertical CRSs. These recommended encodings are based on GML 3.1.1. These common CRS definitions will often be referenced in data transferred between client and server software that implements various standardised interfaces. This specified definition data encoding is expected to be used by multiple OGC Implementation Specifications. That is, each of these specifications is expected to use a subset and/or superset of this recommended definition data.\r\n\r\nThe position or location of a point can be described using coordinates. Such coordinates are unambiguous only when the coordinate reference system on which those coordinates are based is fully defined. Each position is described by a set of coordinates based on a specified coordinate reference system. Coordinates are often used in datasets in which all coordinates belong to the same coordinate reference system. This paper specifies XML encoding of data defining some coordinate reference systems.\r\n" + "@value": "This profile defines a restricted but useful subset of XML-Schema and GML to lower the " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2473,35 +2511,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-011" + "@value": "05-033r9" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Recommended XML/GML 3.1.1 encoding of common CRS definitions" + "@value": "GML simple features profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-009r1", + "@id": "http://www.opengis.net/def/docs/05-112", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-04-15" + "@value": "2006-04-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Pedro Gonçalves" + "@value": "Milan Trninic" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -2511,27 +2549,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=57477" + "@id": "https://portal.ogc.org/files/?artifact_id=13285" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context" + "@value": "Symbology Management" }, { "@language": "en", - "@value": "14-009r1" + "@value": "05-112" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document identifies the generic rules for obtaining JSON documents directly from existing XML documents and schemas elements. It is primordially targeting the OWS Context JSON Encoding design, but is presented in a generic approach. Such generic approach can offer the guidelines for other OGC services, when defining and using JSON encodings." + "@value": "This document describes Symbology Management System which is a system closely related to OpenGIS Style Management Services (SMS) (described in the document OGC 04-040). Having in mind their identical purpose, the system described in this document will also be referred to as SMS.\r\nThe SMS manages styles and symbols and defines their use in the process of producing maps from source GML data.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2542,35 +2580,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-009r1" + "@value": "05-112" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context" + "@value": "Symbology Management" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-103", + "@id": "http://www.opengis.net/def/docs/06-021r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-03-18" + "@value": "2008-08-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -2580,27 +2618,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=886" + "@id": "https://portal.ogc.org/files/?artifact_id=29405" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "99-103" + "@value": "OGC® Sensor Web Enablement Architecture" }, { "@language": "en", - "@value": "Topic 03 - Locational Geometry Structures" + "@value": "06-021r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Provides essential and abstract models for GIS technology that is widely used." + "@value": "This document describes the architecture implemented by Open Geospatial Consortium’s (OGC) Sensor Web Enablement Initiative (SWE). In contrast to other OGC SWE stan-dards, this document is not an implementation standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2611,35 +2649,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-103" + "@value": "06-021r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 3 - Locational Geometry Structures" + "@value": "Sensor Web Enablement Architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-010r5", + "@id": "http://www.opengis.net/def/docs/07-032", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2007-06-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -2649,27 +2687,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/16-010r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=20586" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-010r5" + "@value": "07-032" }, { "@language": "en", - "@value": "Volume 7: OGC CDB Data Model Guidance (Best Practice)" + "@value": "Frame image geopositioning metadata GML 3.2 application schema" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store.\r\n\r\n" + "@value": "This document specifies a GML 3.2 Application Schema for frame image geopositioning metadata, for XML encoding of the georeferencing coordinate transformation parameters of an unrectified frame image. A frame image is one whose entire two-dimensional extent was collected at one time. A georeferencing coordinate transformation can transform position coordinates between a specific ground-based (or object) Coordinate Reference System (CRS) and the image CRS." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2680,30 +2718,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-010r5" + "@value": "07-032" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 7: OGC CDB Data Model Guidance (Best Practice)" + "@value": "Frame image geopositioning metadata GML 3.2 application schema" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-119r1", + "@id": "http://www.opengis.net/def/docs/18-049r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-02-01" + "@value": "2019-02-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "Paulo Sacramento" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -2718,17 +2756,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=52272" + "@id": "https://docs.ogc.org/per/18-049r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-9: OGC Mobile Apps: Definition, Requirements, and Information Architecture" + "@value": "18-049r1" }, { "@language": "en", - "@value": "12-119r1" + "@value": "Application Package Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -2738,7 +2776,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report represents the results of the OWS-9 innovations thread on mobile applications. Initially, the goal was to help understanding the requirements for developing standards-based geospatially-enabled mobile applications. The report describes how OGC Enabled Mobile Apps can be integrated into information architectures based on OGC standards. Particular emphasize has been put on the future work section, as it provides valuable recommendations for further standardization work (and, equally important, highlights aspects that could be excluded from standardization)" + "@value": "This Engineering Report (ER) describes the work performed by the Participants in the Exploitation Platforms Earth Observation Clouds (EOC) Thread of OGC Testbed-14 in regard to the Application Package (AP).\r\n\r\nThe AP serves as a means to convey different kinds of information describing a certain application - often, but not necessarily, an Earth Observation data processing algorithm - so that different elements of an ecosystem generically known as an Exploitation Platform can exchange information among themselves in a standard and interoperable way. The AP guarantees that, despite potentially very heterogeneous implementations and implementing entities, applications are treated equally. The AP also guarantees that the Earth Observation scientist who developed it on the one hand is shielded from infrastructure details and heterogeneity and on the other hand benefits from the ability to execute the same application on different infrastructure.\r\n\r\nGiven its suitability for conveying a Common Operating Picture (COP), in OGC Testbed-13 the OGC Web Services (OWS) Context standard had been chosen as the basic encoding for the Application Package. Despite serious consideration, and while acknowledging the advantages of that approach, the consensus among Participants was not to continue along this path in Testbed-14 but instead to opt for an AP encoding, consisting of a WPS-T (Transactional Web Processing Service (WPS)) DeployProcess message encoded in JSON (see Chapter 9 for the rationale). The information model conveyed in this manner does not differ significantly from the one that could be conveyed using OWS Context, and its main, common features can be briefly listed as:\r\n\r\na link to the application execution unit,\r\n\r\na description of the application’s inputs and outputs,\r\n\r\nlinks to required Earth Observation data catalogues,\r\n\r\nand the possibility to pass other auxiliary information.\r\n\r\nAn important difference in Testbed-14 with respect to Testbed-13 is that the application execution unit is not limited to a Docker container, but can also be a workflow described in Common Workflow Language (CWL), something which stems directly from one of the Sponsor requirements. Finally, it is important to note that this route does not preclude from embedding an OWS Context structure in the enclosing DeployProcess document if this is desired.\r\n\r\nStarting from the lessons learned and limitations identified in Testbed-13, and embracing the new and changed Sponsor requirements, this ER explains the trade-offs, decisions and conclusions taken by the Participants throughout the project." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2749,30 +2787,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-119r1" + "@value": "18-049r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-9: OGC Mobile Apps: Definition, Requirements, and Information Architecture" + "@value": "OGC Testbed-14: Application Package Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-026", + "@id": "http://www.opengis.net/def/docs/15-118r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-12-19" + "@value": "2018-04-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Pedro Gonçalves" + "@value": "Simon Jirka, Christoph Stasch" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -2787,17 +2825,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-026.html" + "@id": "https://docs.ogc.org/per/15-118r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Federated Clouds Analytics Engineering Report" + "@value": "15-118r1" }, { "@language": "en", - "@value": "19-026" + "@value": "Incident Management Information Sharing Profile Recommendations for OGC Web Services Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -2807,7 +2845,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) documents the results and experiences resulting from the Federated Cloud Analytics task of OGC Testbed-15. More specifically, this ER provides an analysis of:\r\n\r\nThe potential for the OGC Web Processing Service (WPS) Interface Standard as an Application Programming Interface (API) to a workflow automation service for managing job execution involving multiple containers in the Scale Data Center Environment;\r\n\r\nUsing an implementation of the OGC WPS standard as a general frontend to workflow automation with containers;\r\n\r\nThe suitability of the OGC WPS 2.0 standard as an API for Cloud analytics;\r\n\r\nUsing OGC Web Services (WS) as analytics data sources and sinks." + "@value": "The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives:\r\n\r\n• Apply OGC principles and practices for collaborative development to existing standards and technology to prototype an IoT approach to sensor use for incident management;\r\n\r\n• Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability;\r\n\r\n• Develop profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability; and\r\n\r\n• Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario.\r\n\r\nBased on the findings gathered during the implementation and work on these objectives, this Engineering Report describes recommendations on profiles for OGC Web services that shall be used to build IMIS systems." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2818,35 +2856,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-026" + "@value": "15-118r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Federated Clouds Analytics Engineering Report" + "@value": "Incident Management Information Sharing Profile Recommendations for OGC Web Services Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-045", + "@id": "http://www.opengis.net/def/docs/00-028", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-07" + "@value": "2000-04-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Uwe Voges, Kristian Senkler" + "@value": "Allan Doyle" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/sap" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -2856,27 +2894,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21460" + "@id": "https://portal.ogc.org/files/?artifact_id=7196" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "ISO Metadata Application Profile" + "@value": "00-028" }, { "@language": "en", - "@value": "07-045" + "@value": "Web Map Service" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/sap" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies an application profile for ISO 19115/ISO 19119 metadata with support for XML encoding per ISO/TS19139 and HTTP protocol binding. It relies on requirements coming from the CSW 2.0.2 specification (OGC document 07-006)." + "@value": "Provides four protocols (GetCapabilities, GetMap, GetFeatureInfo and DescribeLayer) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2887,35 +2925,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-045" + "@value": "00-028" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile" + "@value": "Web Map Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-172r1", + "@id": "http://www.opengis.net/def/docs/17-080r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-05-13" + "@value": "2018-09-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Kristin Stock" + "@value": "Ryan Franz" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -2925,27 +2963,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=26730" + "@id": "https://docs.ogc.org/is/17-080r2/17-080r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Feature Type Catalogue Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0" + "@value": "CDB Multi-Spectral Imagery Extension" }, { "@language": "en", - "@value": "07-172r1" + "@value": "17-080r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes a Feature Type Catalogue extension package for the OGC® ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 [OGC 05-025r3]. It defines the way an ISO 19110 [ISO 19110:2005] Feature Type Catalogue is included within a Registry, and provides an information model and stored queries for such an inclusion." + "@value": "The “Multi-Spectral Imagery” extension defines how to encode and store reflected electromagnetic radiation from the infrared wavelengths into a CDB. The portion of the spectrum targeted is between the visible spectrum (current imagery and texture in CDB), and longer wavelength infrared that is primarily emissive and can be simulated based on the material temperature. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -2956,30 +2994,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-172r1" + "@value": "17-080r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Feature Type Catalogue Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0" + "@value": "CDB Multi-Spectral Imagery Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-046", + "@id": "http://www.opengis.net/def/docs/22-014", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-03-05" + "@value": "2023-01-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Volker Coors" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -2994,17 +3032,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-046.html" + "@id": "https://docs.ogc.org/per/22-014.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-046" + "@value": "22-014" }, { "@language": "en", - "@value": "Testbed-13: 3D Tiles and I3S Interoperability and Performance Engineering Report" + "@value": "Testbed-18: Key Management Service Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -3014,7 +3052,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 13 Engineering Report (ER) documents the overall architecture developed in the Interoperability of 3D Tiles and I3S using a 3D Portrayal Service and performance study of 3D tiling algorithms activity. The report also summarizes a proof-of-concept of the use of 3D Tiles and I3S as data delivery formats for the OGC 3D Portrayal Service interface standard. The report captures the results from the interoperability tests performed as part of the 3D Tiles and I3S testbed work package. Specifically, this OGC Testbed activity focused on the following tasks:\r\n\r\nCityGML files converted into Cesium 3D Tiles using Analytical Graphics (AGI’s) 3D Tiling Pipeline, and Cesium as the rendering client;\r\n\r\nAn OGC CDB data store converted into 3D Tiles using Compusult’s Streaming engine, Cesium and Ecere’s GNOSIS as rendering client;\r\n\r\nCityGML data store GeoRocket, 3DPS with 3D Tiles as data delivery format, and Cesium as rendering client;\r\n\r\nCityGML converted into I3S, 3DPS with I3S as data delivery format, and Cesium as rendering client;\r\n\r\nCityGML converted into I3S using ArcGIS and FME, 3DPS with I3S as data delivery format, and rendering in ArcGIS client;\r\n\r\nCityGML with application domain extension stored in GeoRocket, converted to 3D Tiles, and Cesium as the rendering client;\r\n\r\n3D Tiles (generated by all streaming engines visualized) from Ecere’s GNOSIS rendering client;\r\n\r\nCDB visualized directly from Ecere’s GNOSIS rendering client; and\r\n\r\nI3S visualized from Ecere’s GNOSIS rendering client.\r\n\r\n" + "@value": "This OGC Testbed 18 Engineering Report describes the Data Model and API of a Key Management Service (KMS) that supports the flexible but secure exchange of cryptographic keys for applying confidentiality and integrity protection to geographic information. The described KMS is based on the design and implementation from previous OGC Testbeds 16 and 17." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3025,35 +3063,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-046" + "@value": "22-014" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: 3D Tiles and I3S Interoperability and Performance Engineering Report" + "@value": "Testbed-18: Key Management Service Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-043", + "@id": "http://www.opengis.net/def/docs/18-010r7", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-01-31" + "@value": "2019-08-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Daniele Marchionni, Raul Cafini" + "@value": "Roger Lott" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3063,27 +3101,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55210" + "@id": "https://docs.ogc.org/is/18-010r7/18-010r7.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Download Service for Earth Observation Products Best Practice" + "@value": "18-010r7" }, { "@language": "en", - "@value": "13-043" + "@value": "Geographic information — Well-known text representation of coordinate reference systems" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Best Practices document specifies the interfaces, bindings, requirements,\r\nconformance classes for online download of Earth Observation products. This protocol\r\ncovers several scenarios implemented by European Space Agency - ESA for providing its\r\nproducts to users:\r\n- The EO Product to be downloaded is already available and can be downloaded as\r\nit is.\r\n- The EO Product is not online available but is stored in a near online archive.\r\n- The EO Product is advertised in a Catalogue, but it is not physically available and\r\nit has to be generated on the fly by a processing facility.\r\n- The EO product is archived in several distributed online archives and it can be\r\ndownloaded in parallel.\r\nThe basic scenarios can be simply supported by Web Browsers, the most complex ones\r\nneed a dedicated client (download manager) supporting Metalink and multisource\r\ndownload.\r\nThis Best Practice document has been prepared basing on the work performed in the\r\nframe of ESA’s Next Generation Earth Observation user services and it was initially\r\nproduced during the ESA" + "@value": "This Standard defines the structure and content of well-known text strings describing coordinate reference systems (CRSs) and coordinate operations between coordinate reference systems. It does not prescribe how implementations should read or write these strings.\r\n\r\nThis Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2019. It extends the WKT in OGC document 12-063r5 (ISO 19162) which was based on ISO 19111:2007 and ISO 19111-2:2009. That version consolidated several disparate versions of earlier WKT (so-called WKT1) and added the description of coordinate operations.\r\n\r\nThis jointly developed draft has been submitted by ISO TC211 for circulation as a Draft International Standard (DIS). This version incorporates comments made during the ISO TC211 New Work Item Proposal acceptance ballot." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3094,35 +3132,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-043" + "@value": "18-010r7" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Download Service for Earth Observation Products Best Practice" + "@value": "Geographic information — Well-known text representation of coordinate reference systems" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-047", + "@id": "http://www.opengis.net/def/docs/14-012r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-11-25" + "@value": "2014-07-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Nicolas FANJEAU, Sebastian ULRICH" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3132,27 +3170,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/19-047.html" + "@id": "https://portal.ogc.org/files/?artifact_id=57203" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-047" + "@value": "14-012r1" }, { "@language": "en", - "@value": "Proposed OGC GeoPackage Enhancements" + "@value": "RESTful encoding of OGC Sensor Planning Service for Earth Observation satellite Tasking" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Open Geospatial Consortium (OGC) GeoPackage Encoding Standard was developed for the purpose of providing an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information. GeoPackage has proven to be an effective container mechanism for bundling and sharing geospatial data for a variety of operational use cases. However, GeoPackage stakeholders have observed persistent interoperability issues, particularly with regards to metadata, extensions, and portrayal.\r\n\r\nThis paper presents the operational need, proposed approach, and way ahead for addressing these interoperability issues. Section 6 presents three new enhancements (extensions) that are designed to improve the interoperability of GeoPackages in general and metadata in particular. Section 7 presents a vision for implementing an Open Portrayal Framework in GeoPackage. Annex A presents specifications for all of the GeoPackage extensions proposed in this paper. Annex B presents a JSON schema for the proposed encoding for application profiles presented in Section 6. In general, the GeoPackage Standards Working Group (SWG) looks to standardize extensions that address a clear use case, have a sound technical approach, and have a commitment to implementation by multiple organizations. As with the GeoPackage Tiled Gridded Coverage Extension and the GeoPackage Related Tables Extension, these new extensions would be tracked as separate documents from the core GeoPackage Encoding Standard.\r\n\r\nThe GeoPackage community will benefit from the increased interoperability of operational “mission-ready” GeoPackages that will result from this approach. Additionally, software will be able to quickly determine the validity and utility of a GeoPackage in target operational environments. This will help ensure that GeoPackage production-consumption lifecycles and supporting application tools and services are better aligned with stakeholder missions." + "@value": "This OGC® Best Practices document specifies the interfaces, bindings, requirements and conformance classes that enable complete workflows for the tasking of sensor planning services for Earth Observation (EO) satellites. In fact it provides the interfaces for supporting the following EO sensor planning scenarios:\r\n•\tPlanning future acquisitions with feasibility study,\r\n•\tDirect planning of future acquisitions,\r\n•\tReservation of planning for future acquisitions.\r\nThis specification includes a comprehensive list of sensor options and tasking options derived from the parent specification OGC 10-135 [NR22] which gathered inputs from several Satellite Agencies and Operators:\r\n•\tESA\r\n•\tEUMETSAT\r\n•\tCNES\r\n•\tDLR\r\n•\tCSA\r\n•\tAirbus Defence & Space\r\nThis document is based on the standard:\r\nOGC 10-135, Sensor Planning Service Interface Standard 2.0 Earth Observation \r\nSatellite Tasking Extension, version 2.0. 2011.\r\n\r\nwhich was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [OR1] and related projects.\r\nWith respect to the parent specification this Best Practice document proposes the following changes:\r\n•\tReplaces SOAP with REST for service encoding. This affects not only the way the service is implemented but also the way the standard is presented and described. In fact, basing the standard on REST implies that the service has to be described in terms of resources and methods applied on them whilst in SOAP services, the description is focusing on operations and in fact the OGC 10-135[NR22] is structured in Web Service operations.\r\n•\tUsage of OpenSearch Description Documents as an alternate method for describing sensors and tasking Options (§7.3.2). This specification uses the sensors and tasking options model already described in the OGC 10-135 [NR22] standard but defines an additional method for describing sensors and tasking options within OpenSearch Description Documents based on the OGC 13-039 [NR23]. Actually this part of the specification refers to the OpenSearch Extension for Earth Observation Satellite Tasking.\r\n \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3163,35 +3201,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-047" + "@value": "14-012r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Proposed OGC GeoPackage Enhancements" + "@value": "OGC RESTful encoding of OGC Sensor Planning Service for Earth Observation satellite Tasking" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-059r2", + "@id": "http://www.opengis.net/def/docs/16-010r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-08-18" + "@value": "2018-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Christian Kiehle, Theodor Foerster" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3201,27 +3239,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40310" + "@id": "https://portal.ogc.org/files/16-010r4" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-7 Web Processing Service Profiling Engineering Report" + "@value": "Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2" }, { "@language": "en", - "@value": "10-059r2" + "@value": "16-010r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The overall scope of this OWS-7 Engineering Report is to clarify how to write and register a WPS profile. WPS profiles enable clients to search and identify equivalent WPS-based processes distributed on the web. Therefore, this ER provides guidelines for designing WPS Profiles based on WPS interface specification 1.0.0." + "@value": "This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store.\r\nPlease note that the term “lineal” has been replaced with the term “line” or “linear” throughout this document\r\nPlease note that the term “areal” has been replaced with the term “polygon” throughout this document.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3232,35 +3270,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-059r2" + "@value": "16-010r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-7 Web Processing Service Profiling Engineering Report" + "@value": "Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-021r3", + "@id": "http://www.opengis.net/def/docs/03-088r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2003-10-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Taylor" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3270,27 +3308,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=54423" + "@id": "https://portal.ogc.org/files/?artifact_id=11519" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "WaterML2.0 - part 2: Ratings, Gaugings and Sections Discussion Paper" + "@value": "OGC Web Services Common" }, { "@language": "en", - "@value": "13-021r3" + "@value": "03-088r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes an information model for exchanging rating tables, or rating\r\ncurves, that are used for the conversion of related hydrological phenomenon. It also\r\ndescribes a model describing the observations that are used to develop such relationships,\r\noften referred to as gauging observations.\r\nThe information model is proposed as a second part of the WaterML2.0 suite of\r\nstandards, building on part 1 that addresses the exchange of time series1." + "@value": "This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3301,35 +3339,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-021r3" + "@value": "03-088r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "WaterML2.0 - part 2: Ratings, Gaugings and Sections Discussion Paper" + "@value": "OGC Web Services Common" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-110r3", + "@id": "http://www.opengis.net/def/docs/04-094r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-10-27" + "@value": "2016-10-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Panagiotis A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3339,27 +3377,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41437" + "@id": "https://docs.ogc.org/is/04-094r1/04-094r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-110r3" + "@value": "Web Feature Service Implementation Specification with Corrigendum" }, { "@language": "en", - "@value": "WCS 2.0 Interface Standard - Core" + "@value": "04-094r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies how a Web Coverage Service (WCS) offers multi-dimensional coverage data for access over the Internet. This document specifies a core set of requirements that a WCS implementation must fulfil. WCS extension standards add further functionality to this core; some of these are required in addition to the core to obtain a complete implementation. This document indicates which extensions, at a minimum, need to be considered in addition to this core to allow for a complete WCS implementation." + "@value": "The OGC Web Map Service allows a client to overlay map images for display served from multiple Web Map Services on the Internet. In a similar fashion, the OGC Web Feature Service allows a client to retrieve and update geospatial data encoded in Geography Markup Language (GML) from multiple Web Feature Services.\r\n\r\nThe requirements for a Web Feature Service are:\r\n\r\nThe interfaces must be defined in XML.\r\nGML must be used to express features within the interface.\r\nAt a minimum a WFS must be able to present features using GML.\r\nThe predicate or filter language will be defined in XML and be derived from CQL as defined in the OpenGIS Catalogue Interface Implementation Specification.\r\nThe datastore used to store geographic features should be opaque to client applications and their only view of the data should be through the WFS interface.\r\n The use of a subset of XPath expressions for referencing properties.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3370,35 +3408,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-110r3" + "@value": "04-094r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® WCS 2.0 Interface Standard - Core" + "@value": "OGC Web Feature Service Implementation Specification with Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-045", + "@id": "http://www.opengis.net/def/docs/08-129", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-03-05" + "@value": "2009-03-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stephane Fellah" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3408,27 +3446,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-045.html" + "@id": "https://portal.ogc.org/files/?artifact_id=29544" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-045" + "@value": "GML 3.2 implementation of XML schemas in 07-002r3" }, { "@language": "en", - "@value": "Testbed-13: Portrayal Engineering Report" + "@value": "08-129" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Portrayal of geospatial information plays a crucial role in situation awareness, analysis and decision-making. Visualizing geospatial information often requires one to portray the information using symbology or cartographic presentation rules from a community or organization. For example, among those in the law enforcement, fire and rescue community, various local, national and international agencies use different symbols and terminology for the same event, location and building, employing syntactic, structural-based and document-centric data models (e.g., eXtensible Markup Language (XML) schemas and Style Layer Descriptors (SLD)). With this approach, interoperability does not extend to the semantic level, which makes it difficult to share, reuse and mediate unambiguous portrayal information between agencies.\r\n\r\nThis Engineering Report (ER) captures the requirements, solutions, models and implementations of the Testbed 13 Portrayal Package. This effort leverages the work on Portrayal Ontology development and Semantic Portrayal Service conducted during Testbed 10, 11 and 12. The objective of this Testbed 13 is to identify and complete the gaps in the latest version of the portrayal ontology defined in Testbed 12, complete the implementation of the Semantic Portrayal Service by adding rendering capabilities and performing a demonstration of the portrayal service that showcases the benefits of the proposed semantic-based approach." + "@value": "" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3439,35 +3477,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-045" + "@value": "08-129" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: Portrayal Engineering Report" + "@value": "GML 3.2 implementation of XML schemas in 07-002r3" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-062r2", + "@id": "http://www.opengis.net/def/docs/10-004r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-11-17" + "@value": "2013-09-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Burggraf, Ron Lake" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3477,27 +3515,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46548" + "@id": "https://portal.ogc.org/files/?artifact_id=41579" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-8 CCI Portrayal Registries Engineering Report" + "@value": "Topic 20 - Observations and Measurements" }, { "@language": "en", - "@value": "11-062r2" + "@value": "10-004r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OWS-8 Cross Community Interoperability (CCI) thread was built on progress made in the recent OWS-7 initiative to cover key technology areas that could not be addressed within the scope of that initiative. The OWS-8 CCI thread aimed to increase interoperability within communities sharing geospatial data, including advancing of interoperability among heterogeneous data models, advancing strategies to share styles to provide a more common and automated use of symbology, improvement of KML, and advancing schema automation allowing communities to better share their information artifacts. This OGC engineering report aims to present findings from the portrayal registries as part of the CCI subthread" + "@value": "This International Standard defines a conceptual schema for observations, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities. \r\nObservations commonly involve sampling of an ultimate feature of interest. This International Standard defines a common set of sampling feature types classified primarily by topological dimension, as well as samples for ex-situ observations. The schema includes relationships between sampling features (sub-sampling, derived samples). \r\nThis International Standard concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3508,35 +3546,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-062r2" + "@value": "10-004r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 CCI Portrayal Registries Engineering Report" + "@value": "Topic 20 - Observations and Measurements" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-000r1", + "@id": "http://www.opengis.net/def/docs/16-070r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-04-17" + "@value": "2018-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Nobuhiro Ishimaru, Chikako Kurokawa, Yuichi Tanaka, Tomohisa Oishi, Kentaro Akahoshi, Tatjana Kutzne" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3546,27 +3584,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=92113" + "@id": "https://portal.ogc.org/files/16-070r3" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-000r1" + "@value": "Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage" }, { "@language": "en", - "@value": "CityGML Urban Planning ADE for i-Urban Revitalization" + "@value": "16-070r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Discussion Paper introduces the CityGML Urban Planning Application Domain Extension (ADE) published by the Japanese government for the i-Urban Revitalization (i-UR).\r\nThe i-UR is an information infrastructure dedicated for urban planning to contribute to data-driven urban development and urban revitalization. OGC KML has been utilized more than 10 years for i-UR, however, there were huge requirements for use of application-specific semantics information for urban planning and multi-scale structured information by LOD (Levels of Detail).\r\nBy using CityGML ADE mechanism, the Urban Planning ADE provides application-specific semantics information integrating with 3D geometry data to visualize and analyze the urban situation. Additionally, the Urban Planning ADE introduces newly extended LOD, LOD-1 (minus one) for nationwide city models and LOD-2 (minus two) for a worldwide city model to visualize global urban activities and study urban structure by integrating geospatial information and statistical grid information.\r\nThis paper describes a brief introduction of i-Urban Revitalization, data model of the Urban Planning ADE and data experiment examples to discuss further utilization of the Urban Planning ADE in urban planning applications.\r\n" + "@value": "This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3577,30 +3615,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-000r1" + "@value": "16-070r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CityGML Urban Planning ADE for i-Urban Revitalization" + "@value": "Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-093r1", + "@id": "http://www.opengis.net/def/docs/17-018", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-04-26" + "@value": "2018-01-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steve Liang, Tania Khalafbeigi" + "@value": "Alaitz Zabala, Joan Maso" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -3615,17 +3653,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-093r1.html" + "@id": "https://docs.ogc.org/per/17-018.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-093r1" + "@value": "17-018" }, { "@language": "en", - "@value": "Incident Management Information Sharing Internet of Things Protocol Mapping Engineering Report" + "@value": "Testbed-13: Data Quality Specification Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -3635,7 +3673,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report details Pilot experiences in connecting a variety of local communications protocols and message formats supported by low-cost sensor devices with OGC SWE Web services published globally over IP networks. It describes the Sensor Hub approach taken to support these connections and the mappings from one protocol to another required to develop integrated SWE-IoT networks." + "@value": "OGC 17-018 (Testbed-13 Data Quality Specification Engineering Report) provides methods to quantify the quality concepts defined in OGC 17-032 and a way to include the quantifications in service descriptions. It extends QualityML quality metrics (that already includes ISO 19157) into the aviation domain. It lists a set of quantitative and conformance measurements that are specified in terms of quality measures, domains, and metrics (value types and units) and are appropriated for each quality type and data type. Secondly, it extends the SDCM to be able to encode and include the above mentioned quality information for each service in a interoperable way." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3646,35 +3684,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-093r1" + "@value": "17-018" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Incident Management Information Sharing Internet of Things Protocol Mapping Engineering Report" + "@value": "OGC Testbed-13: Data Quality Specification Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-075", + "@id": "http://www.opengis.net/def/docs/15-065r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-01-14" + "@value": "2015-11-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf" + "@value": "Eric Hirschorn, Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3684,27 +3722,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/18-075/18-075.html" + "@id": "https://portal.ogc.org/files/?artifact_id=64145" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Moving Features Encoding Part I: XML Core" + "@value": "15-065r1" }, { "@language": "en", - "@value": "18-075" + "@value": "Testbed11 Referenceable Grid Harmonization Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange." + "@value": "This Engineering Report is a deliverable of the Testbed-11 Urban Climate Resilience (UCR) Thread. The UCR Thread responds to the urgent need to make climate information and related data readily available for the public and government decision makers to prepare for changes in the Earth’s climate. An important set of a data sources that will play an important role in detecting changes due to climate effects are a wide array of remote imaging systems." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3715,35 +3753,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-075" + "@value": "15-065r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Moving Features Encoding Part I: XML Core" + "@value": "OGC® Testbed11 Referenceable Grid Harmonization Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-132", + "@id": "http://www.opengis.net/def/docs/18-058r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-08-18" + "@value": "2022-05-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Bruno Simmenauer" + "@value": "Clemens Portele, Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3753,27 +3791,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40149" + "@id": "https://docs.opengeospatial.org/is/18-058r1/18-058r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-132" + "@value": "18-058r1" }, { "@language": "en", - "@value": "OWS-7 Aviation - WXXM Assessment Engineering Report" + "@value": "OGC API - Features - Part 2: Coordinate Reference Systems by Reference corrigendum" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The document describes the results of using OGC Web Services for accessing and using WXXM data, notably within aviation scenarios involving rerouting procedures motivated by the sudden closure of airspace areas caused by the eruption of a volcano. The focus of this document will be to evaluate the ability to encode and serve associated operational data with WXXM 1.1.1." + "@value": "OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks.\r\n\r\nOGC API Features provides API building blocks to create, modify and query features on the Web. OGC API Features is comprised of multiple parts, each of them is a separate standard.\r\n\r\nThis part extends the core capabilities specified in Part 1: Core with the ability to use coordinate reference system identifiers other than the defaults defined in the core." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3784,35 +3822,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-132" + "@value": "18-058r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-7 Aviation - WXXM Assessment Engineering Report" + "@value": "OGC API - Features - Part 2: Coordinate Reference Systems by Reference corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-081", + "@id": "http://www.opengis.net/def/docs/02-112", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2001-09-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "ISO" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pol-nts" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3822,27 +3860,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51856" + "@id": "https://portal.ogc.org/files/?artifact_id=1221" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-081" + "@value": "Topic 12 - The OpenGIS Service Architecture" }, { "@language": "en", - "@value": "Name type specification – ontology resources" + "@value": "02-112" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pol-nts" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "An OGC name is required for ontology resources published by OGC. This includes OWL\r\nontologies, classes and properties." + "@value": "Same as ISO 19119" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3853,35 +3891,82 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-081" + "@value": "02-112" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Name type specification – ontology resources" + "@value": "Topic 12 - The OpenGIS Service Architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-014", + "@id": "http://www.opengis.net/def/doc-type/cs", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/20-072r2" + }, + { + "@id": "http://www.opengis.net/def/docs/17-014r7" + }, + { + "@id": "http://www.opengis.net/def/docs/19-065" + }, + { + "@id": "http://www.opengis.net/def/docs/17-014r8" + }, + { + "@id": "http://www.opengis.net/def/docs/17-014r5" + }, + { + "@id": "http://www.opengis.net/def/docs/17-002r1" + }, + { + "@id": "http://www.opengis.net/def/docs/21-069r2" + }, + { + "@id": "http://www.opengis.net/def/docs/21-050r1" + }, + { + "@id": "http://www.opengis.net/def/docs/20-072r5" + }, + { + "@id": "http://www.opengis.net/def/docs/22-025r4" + }, + { + "@id": "http://www.opengis.net/def/docs/20-094" + }, + { + "@id": "http://www.opengis.net/def/docs/18-053r2" + }, + { + "@id": "http://www.opengis.net/def/docs/17-014r9" + }, + { + "@id": "http://www.opengis.net/def/docs/17-030r1" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/07-026r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-01-15" + "@value": "2008-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "J" + "@value": "Andreas Matheus, Jan Herrmann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3891,27 +3976,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1337" + "@id": "https://portal.ogc.org/files/?artifact_id=25218" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Web Services SOAP Experiment Report" + "@value": "07-026r2" }, { "@language": "en", - "@value": "03-014" + "@value": "Geospatial eXtensible Access Control Markup Language (GeoXACML)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document will discuss how OWS services can be ported to Web Services and highlight various issues/problems that have been discovered and need further discussion." + "@value": "The OpenGIS® Geospatial eXtensible Access Control Markup Language Encoding Standard (GeoXACML) defines a geospatial extension to the OASIS standard “eXtensible Access Control Markup Language (XACML)” [www.oasis-open.org/committees/xacml/]. This extension incorporates spatial data types and spatial authorization decision functions based on the OGC Simple Features[http://www.opengeospatial.org/standards/sfa] and GML[http://www.opengeospatial.org/standards/gml] standards. GeoXACML is a policy language that supports the declaration and enforcement of access rights across jurisdictions and can be used to implement interoperable access control systems for geospatial applications such as Spatial Data Infrastructures. GeoXACML is not designed to be a rights expression language and is therefore not an extension of the OGC GeoDRM Reference Model (Topic 18 in the OpenGIS® Abstract Specification [http://www.opengeospatial.org/standards/as]). " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3922,35 +4007,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-014" + "@value": "07-026r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Services SOAP Experiment Report" + "@value": "Geospatial eXtensible Access Control Markup Language (GeoXACML)" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-061", + "@id": "http://www.opengis.net/def/docs/18-095r7", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-02-20" + "@value": "2020-10-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "George Percivall " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/cp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -3960,27 +4045,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=26765" + "@id": "https://portal.ogc.org/files/18-095r7" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Revision Notes for OpenGIS® Implementation Specification: Geographic information - Geography Markup Language Version 3.2.1" + "@value": "18-095r7" }, { "@language": "en", - "@value": "07-061" + "@value": "Geospatial Coverages Data Cube Community Practice" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/cp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides revision notes for version 3.2.1 of the OpenGIS® Implementation Specification Geographic information – Geography Markup Language (GML)." + "@value": "Data cubes for geospatial information provide the means to integrate observations and other types of geospatial data for use in multiple applications through simplified access and efficient analytics. Using the Geospatial Coverages data structure, this Community Practice defines requirements for a geospatial coverages data cube infrastructure and guidelines for enhancements and extensions to the basic core." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -3991,35 +4076,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-061" + "@value": "18-095r7" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Revision Notes for OpenGIS® Implementation Specification: Geographic information - Geography Markup Language Version 3.2.1" + "@value": "Geospatial Coverages Data Cube Community Practice" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-004r4", + "@id": "http://www.opengis.net/def/docs/06-098", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-01-29" + "@value": "2007-08-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Graham Vowles" + "@value": "Michael Gerlek" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/cr" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -4029,27 +4114,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=17802" + "@id": "https://portal.ogc.org/files/?artifact_id=20257" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-004r4" + "@value": "Proposal for WCS Transactional - WCS-T" }, { "@language": "en", - "@value": "Topic 18 - Geospatial Digital Rights Management Reference Model (GeoDRM RM)" + "@value": "06-098" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/cr" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a reference model for digital rights management (DRM) functionality for geospatial resources (GeoDRM). As such, it is connected to the general DRM market in that geospatial resources must be treated as nearly as possible like other digital resources, such as music, text, or services. It is not the intention here to reinvent a market that already exists and is thriving, but to make sure that a larger market has access to geospatial resources through a mechanism that it understands and that is similar to the ones already in use." + "@value": "Version 1.0 of the Web Coverage Service (WCS) Specification does not address how coverage data gets added to or deleted from a server; it is assumed that some implementation-specific process exists for handling this, likely on the back end (server-side). One of the goals of OWS-4 was to extend WCS to support these operations, generally referred to as " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -4060,30 +4145,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-004r4" + "@value": "06-098" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 18 - Geospatial Digital Rights Management Reference Model (GeoDRM RM)" + "@value": "Change Request: WCS: Proposal for WCS Transactional - WCS-T" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-011", + "@id": "http://www.opengis.net/def/docs/19-019", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-04-02" + "@value": "2020-02-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Nadine Alameh" + "@value": "Martin Klopfer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -4098,17 +4183,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=53036" + "@id": "https://docs.ogc.org/per/19-019.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "13-011" + "@value": "19-019" }, { "@language": "en", - "@value": "OWS-9: Summary of the OGC Web Services, Phase 9 (OWS-9) Interoperability Testbed" + "@value": "OGC Testbed-15: Portrayal Summary ER" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -4118,7 +4203,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report summarizes the results of OGC Web Services Initiative, Phase 9 (OWS-9)." + "@value": "This OGC Engineering Report provides an executive summary of the Open Portrayal Framework (OPF) Thread in OGC Testbed-15. The work in this testbed occurred between April and November 2019. Full details of the requirements, high-level architecture, and solutions are provided in the following Engineering Reports:\r\n\r\nOGC Testbed-15: Styles API Draft Specification Engineering Report\r\n\r\nOGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report\r\n\r\nOGC Testbed-15: Maps and Tiles API Draft Specification Engineering Report\r\n\r\nOGC Testbed-15: Images and Change Sets Draft Specification Engineering Report\r\n\r\nOGC Testbed-15: Open Portrayal Framework Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -4129,35 +4214,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-011" + "@value": "19-019" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-9: Summary of the OGC Web Services, Phase 9 (OWS-9) Interoperability Testbed" + "@value": "OGC Testbed-15: Portrayal Summary ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-066", + "@id": "http://www.opengis.net/def/docs/20-000r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2020-04-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Michala Hill" + "@value": "Nobuhiro Ishimaru, Chikako Kurokawa, Yuichi Tanaka, Tomohisa Oishi, Kentaro Akahoshi, Tatjana Kutzne" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -4167,27 +4252,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/19-066.html" + "@id": "https://portal.ogc.org/files/?artifact_id=92113" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-066" + "@value": "20-000r1" }, { "@language": "en", - "@value": "Volume 14 OGC CDB Guidance on Conversion of CDB Shapefiles into CDB GeoPackages (Best Practice)" + "@value": "CityGML Urban Planning ADE for i-Urban Revitalization" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Best Practice (BP) document describes the conversion process for converting a CDB structured Shapefile into a CDB structured GeoPackage. This is the companion document to Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension). Volume 13 defines the requirements and provides CDB specific guidance on using GeoPackage containers in a CDB data store.\r\n" + "@value": "This OGC Discussion Paper introduces the CityGML Urban Planning Application Domain Extension (ADE) published by the Japanese government for the i-Urban Revitalization (i-UR).\r\nThe i-UR is an information infrastructure dedicated for urban planning to contribute to data-driven urban development and urban revitalization. OGC KML has been utilized more than 10 years for i-UR, however, there were huge requirements for use of application-specific semantics information for urban planning and multi-scale structured information by LOD (Levels of Detail).\r\nBy using CityGML ADE mechanism, the Urban Planning ADE provides application-specific semantics information integrating with 3D geometry data to visualize and analyze the urban situation. Additionally, the Urban Planning ADE introduces newly extended LOD, LOD-1 (minus one) for nationwide city models and LOD-2 (minus two) for a worldwide city model to visualize global urban activities and study urban structure by integrating geospatial information and statistical grid information.\r\nThis paper describes a brief introduction of i-Urban Revitalization, data model of the Urban Planning ADE and data experiment examples to discuss further utilization of the Urban Planning ADE in urban planning applications.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -4198,29 +4283,65 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-066" + "@value": "20-000r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 14 OGC CDB Guidance on Conversion of CDB Shapefiles into CDB GeoPackages (Best Practice)" + "@value": "CityGML Urban Planning ADE for i-Urban Revitalization" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/isx/collection", + "@id": "http://www.opengis.net/def/docs/03-022r3", "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" + "http://www.w3.org/2004/02/skos/core#Concept" ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "http://purl.org/dc/terms/created": [ { - "@value": "Documents of type Implementation Standard Extension" + "@type": "xsd:date", + "@value": "2003-02-04" + } + ], + "http://purl.org/dc/terms/creator": [ + { + "@value": "Simon Cox" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + { + "@id": "http://www.opengis.net/def/doc-type/d-rp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ + { + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + { + "@id": "https://portal.ogc.org/files/?artifact_id=1324" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ + { + "@language": "en", + "@value": "03-022r3" + }, + { + "@language": "en", + "@value": "Observations and Measurements" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ + { + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Documents of type Implementation Standard Extension" + "@value": "This document describes a framework and encoding for measurements and observations." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -4228,57 +4349,82 @@ "@id": "http://www.opengis.net/def/docs" } ], - "http://www.w3.org/2004/02/skos/core#member": [ + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/12-049" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "03-022r3" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@language": "en", + "@value": "Observations and Measurements" + } + ] + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-rp", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/02-066r1" }, { - "@id": "http://www.opengis.net/def/docs/12-039" + "@id": "http://www.opengis.net/def/docs/02-024" }, { - "@id": "http://www.opengis.net/def/docs/08-059r4" + "@id": "http://www.opengis.net/def/docs/01-014r5" }, { - "@id": "http://www.opengis.net/def/docs/12-040" + "@id": "http://www.opengis.net/def/docs/01-029" }, { - "@id": "http://www.opengis.net/def/docs/10-092r3" + "@id": "http://www.opengis.net/def/docs/04-019r2" }, { - "@id": "http://www.opengis.net/def/docs/10-135" + "@id": "http://www.opengis.net/def/docs/04-016r3" }, { - "@id": "http://www.opengis.net/def/docs/13-084r2" + "@id": "http://www.opengis.net/def/docs/03-010r9" }, { - "@id": "http://www.opengis.net/def/docs/11-053r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/03-109r1" + }, { - "@value": "Documents of type Implementation Standard Extension" + "@id": "http://www.opengis.net/def/docs/03-064r5" + }, + { + "@id": "http://www.opengis.net/def/docs/03-022r3" + }, + { + "@id": "http://www.opengis.net/def/docs/03-010r7" + }, + { + "@id": "http://www.opengis.net/def/docs/03-088r6" + }, + { + "@id": "http://www.opengis.net/def/docs/00-029" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-113r3", + "@id": "http://www.opengis.net/def/docs/21-028", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-02-23" + "@value": "2022-01-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Dean Younge" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -4288,27 +4434,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=72712" + "@id": "https://docs.ogc.org/per/21-028.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-113r3" + "@value": "OGC Testbed-17: OGC API - Moving Features Engineering Report" }, { "@language": "en", - "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure" + "@value": "21-028" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time.\r\nThe application of CDB to future simulation architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the High Level Architecture - -Federation Object Model (HLA/FOM) and DIS protocols, the application of the CDB standard provides a Common Environment to which inter-connected simulators share a common view of the simulated environment.\r\nThe CDB standard defines an open format for the storage, access and modification of a synthetic environment database. A synthetic environment is a computer simulation that represents activities at a high level of realism, from simulation of theaters of war to factories and manufacturing processes. These environments may be created within a single computer or a vast distributed network connected by local and wide area networks and augmented by super-realistic special effects and accurate behavioral models. SE allows visualization of and immersion into the environment being simulated . \r\nThis standard defines the organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The standard makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. A series of associated OGC Best Practice documents define rules and guidelines for data representation of real world features.\r\nThe CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. A CDB data store can include terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the data store can includes the specific attributes of the synthetic environment data as well as their relationships.\r\nThe associated CDB Standard Best Practice documents provide a description of a data schema for Synthetic Environmental information (i.e. it merely describes data) for use in simulation. The CDB Standard provides a rigorous definition of the semantic meaning for each dataset, each attribute and establishes the structure/organization of that data as a schema comprised of a folder hierarchy and files with internal (industry-standard) formats.\r\nA CDB conformant data store contains datasets organized in layers, tiles and levels-of-detail. Together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB compliant data store is specifically tailored for real-time applications.\r\n" + "@value": "The OGC Testbed-17 Moving Features thread conducted an interoperability feasibility study that examined specific scenarios that could be supported by a Moving Features Application Programming Interface (API). The use cases considered tracking objects based on motion imagery, analytical processing and visualization. This Engineering Report presents a specification of a prototype Moving Features API, that could serve as the foundation for a future draft OGC API — Moving Features standard.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -4319,35 +4465,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-113r3" + "@value": "21-028" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure" + "@value": "OGC Testbed-17: OGC API - Moving Features Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-074", + "@id": "http://www.opengis.net/def/docs/17-003r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-15" + "@value": "2020-02-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Y. Coene, U. Voges, O. Barois" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -4357,27 +4503,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-074.html" + "@id": "https://docs.ogc.org/is/17-003r2/17-003r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-074" + "@value": "17-003r2" }, { "@language": "en", - "@value": "GeoPackage 1.2 Vector Tiles Extensions Engineering Report" + "@value": "EO Dataset Metadata GeoJSON(-LD) Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Tiled feature data, colloquially referred to as 'vector tiles', can be used to optimize the delivery of vector data over the web. This data may subsequently be used to support visualization (particularly through maps) as well as limited analysis activities. One goal of the OGC Vector Tiles Pilot was to define candidate extensions to existing OGC standards as a way to advance the use of vector tiles technology as part of the OGC baseline. This Engineering Report (ER) describes a set of possible extensions to GeoPackage 1.2 that documents the mechanism to store and retrieve vector tiles in a GeoPackage. These extensions work together to enable a GeoPackage to act as a container format that can support visualization and analysis activities, even in a Denied, Degraded, Intermittent, or Limited Bandwidth (DDIL) environment.\r\n\r\nThe GeoPackage Vector Tiles extensions define the rules and requirements for encoding vector tiles in a GeoPackage data store. There are five draft extensions:\r\n\r\nThe Vector Tiles Extension provides vector tiles support through the GeoPackage tiles option.\r\n\r\nThe Mapbox Vector Tiles Extension allows the content of a tile Binary Large OBject (BLOB) to be a Mapbox Vector Tile as per version 2.1 of the Mapbox Vector Tile (MVT) specification [1].\r\n\r\nThe GeoJSON Vector Tiles Extension allows the content of each tile BLOB to be a GeoJSON file.\r\n\r\nThe OGC Web Services (OWS) Context Extension provides a way to store information describing a list of geospatial resources, including but not limited to maps, their layers, and the styles of those layers.\r\n\r\nThe Vector Tiles Attributes Extension allows attribute information for each feature to be stored in relational tables for more convenient querying.\r\n\r\nTo support vector tiles, a minimum of at least two extensions is required. The first extension enables vector tiles support. However, to be usable, an encoding format must be declared via either the second or third extension. The other extensions are purely optional.\r\n\r\nThese extensions, like all GeoPackage extensions, are intended to be transparent and to not interfere with GeoPackage-compliant, but non-supporting, software packages." + "@value": "JavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. This OGC standard describes a GeoJSON [NR2] and JSON-LD [NR3] encoding for Earth Observation (EO) metadata for datasets (granules). This standard can be applied to encode metadata based on the Earth Observation Metadata Profile of Observations and Measurements (O&M) OGC 10-157r4 [OR1] or as an encoding of the Unified Metadata Model for Granules (UMM-G) conceptual model [OR2].\r\n\r\nThe GeoJSON encoding defined in this document is defined as a compaction[1] through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF XML [OR11] and RDF Turtle [OR12].\r\n\r\nThis document makes no assumptions as to the “service” interfaces through which the metadata are accessed and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful Architecture. The documented approach can be applied in combination with the following technologies:\r\n\r\nOGC OpenSearch extensions [OR19], [OR20], [OR25],\r\nW3C Linked Data Platform [OR21], [OR22],\r\nOASIS searchRetrieve [OR23],\r\nOASIS OData [OR24].\r\nGeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features.\r\n\r\nJSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR18] which allows validation of instances against these schemas." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -4388,35 +4534,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-074" + "@value": "17-003r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Vector Tiles Pilot: GeoPackage 1.2 Vector Tiles Extensions Engineering Report" + "@value": "OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-009r5", + "@id": "http://www.opengis.net/def/docs/07-009r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2007-08-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Shayne Urbanowski" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -4426,27 +4572,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/16-009r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=22873" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-009r5" + "@value": "07-009r3" }, { "@language": "en", - "@value": "Volume 6: OGC CDB Rules for Encoding Data using OpenFlight" + "@value": "OGC Web Services Architectural Profile for the NSG" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of that document for a general overview." + "@value": "The purpose of this document is to generally describe how the various OGC specifications may be used to address the needs of a large enterprise system. It highlights the key elements of the OWS-4 effort as they relate to web service architecture implementation at NGA and in the NSG. The goal is that this document will enable organization that interface with the NSG to understand how to produce and consume data and services in an interoperable environment. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -4457,35 +4603,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-009r5" + "@value": "07-009r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 6: OGC CDB Rules for Encoding Data using OpenFlight" + "@value": "OGC Web Services Architectural Profile for the NSG" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-018", + "@id": "http://www.opengis.net/def/docs/06-009r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-13" + "@value": "2008-02-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Guy Schumann" + "@value": "Arthur Na, Mark Priest" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -4495,27 +4641,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-018.html" + "@id": "https://portal.ogc.org/files/?artifact_id=26667" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Machine Learning Training Data ER" + "@value": "Sensor Observation Service" }, { "@language": "en", - "@value": "20-018" + "@value": "06-009r6" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Testbed-16 Machine Learning (ML) Training Data Engineering Report (ER) describes training data used for developing a Wildfire Response application. Within the context of the application, this ER discusses the challenges and makes a set of recommendations. The two scenarios for the wildfire use case include fuel load estimation and water body identification. The ML training data described in this ER are based on these two scenarios. Suggestions are also made for future work on a model for ML training dataset metadata, which is intended to provide vital information on the data and therefore facilitate the uptake of training data by the ML community. Additionally, this ER summarizes the discussions and issues about ML training data among the Testbed-16 ML thread participants and draws conclusions and recommendations for future work on the subject. Finally, this ER also links to current Analysis Ready Data (ARD) principles and efforts, in particular in the Earth Observation (EO) community." + "@value": "The OpenGIS® Sensor Observation Service Interface Standard (SOS) provides an API for managing deployed sensors and retrieving sensor data and specifically “observation” data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -4526,35 +4672,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-018" + "@value": "06-009r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: Machine Learning Training Data ER" + "@value": "OpenGIS Sensor Observation Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-144r2", + "@id": "http://www.opengis.net/def/docs/12-032r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-02-08" + "@value": "2012-12-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Rahul Thakkar, Michael Maraist" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pol" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -4564,27 +4710,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=59324" + "@id": "https://portal.ogc.org/files/?artifact_id=50486" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "MIME Media Types for GML" + "@value": "WAMI Services: Dissemination Services for Wide Area Motion Imagery - Best Practice" }, { "@language": "en", - "@value": "09-144r2" + "@value": "12-032r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pol" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides guidance on GML MIME type specification. An Internet media type, originally called a MIME type after Multipurpose Internet Mail Extensions and sometimes a Content-type after the name of a header in several protocols whose value is such a type, is a two-part identifier for file formats on the Internet. The identifiers were originally defined in RFC 2046 for use in e-mail sent through SMTP, but their use has expanded to other protocols such as HTTP, RTP and SIP." + "@value": "This OGC Best Practice (BP) describes web interface specifications for the access and dissemination of Wide Area Motion Imagery (WAMI) products and metadata. This BP also describes a framework and interface specifications common to all WAMI services. A WAMI - Primer has been developed to help you implement this Best Practice." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -4595,35 +4741,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-144r2" + "@value": "12-032r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Technical Committee Policies and Procedures: MIME Media Types for GML" + "@value": "WAMI Services: Dissemination Services for Wide Area Motion Imagery - Best Practice" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-092r2", + "@id": "http://www.opengis.net/def/docs/15-045r7", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-04-04" + "@value": "2021-03-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff, Matthes Rieke" + "@value": "Peter Trevelyan, Paul Hershberg, Steve Olson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -4633,27 +4779,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46243" + "@id": "https://docs.ogc.org/is/15-045r7/15-045r7.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-092r2" + "@value": "MetOcean Application profile for WCS2.1: Part 0 MetOcean Metadata" }, { "@language": "en", - "@value": "OWS-8 Report on Digital NOTAM Event Specification" + "@value": "15-045r7" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 8 (OWS-8). It describes the results of the conceptual and schematron rule based validation of the Digital NOTAM Event Specification (DNES). Various conceptual aspects were identified which need clarification and/or revision. Schematron rules were developed for a number of the DNES scenarios. This document contains coverage tables which document normative statements from the DNES and indicate which of them can be tested with existing schematron rules.\r\nSee: http://dp.schemas.opengis.net/11-092r2" + "@value": "The purpose of this Met Ocean profile of WCS2.1 is to define the metadata returned in the response documents resulting from the WCS2.1 operations: GetCapabilities, and DescribeCoverage; for use within the meteorological and oceanographic communities. It also defines the new operation DescribeCoverageCollection.\r\n\r\nThis work has been done by members of the OGC MetOcean Domain Working Group." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -4664,532 +4810,449 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-092r2" + "@value": "15-045r7" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 Report on Digital NOTAM Event Specification" + "@value": "OGC MetOcean Application profile for WCS2.1: Part 0 MetOcean Metadata" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/dp", - "http://www.w3.org/2004/02/skos/core#narrower": [ + "@id": "http://www.opengis.net/def/docs/21-057", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/09-085r2" - }, + "@type": "xsd:date", + "@value": "2022-10-14" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/04-010r1" - }, + "@value": "Jeff Yutzler" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/08-071" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/07-172r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/03-028" - }, + "@id": "https://docs.ogc.org/is/21-057/21-057.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/05-017" + "@language": "en", + "@value": "21-057" }, { - "@id": "http://www.opengis.net/def/docs/13-100" - }, + "@language": "en", + "@value": "OGC GeoPackage WKT for Coordinate Reference Systems Extension" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/11-018" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/09-163r2" - }, + "@value": "This document is a revision to the GeoPackage WKT for Coordinate Reference Systems Extension that previously was published as Annex F.10 of the GeoPackage Encoding Standard 1.3.0 (OGC 12-128r17). This document replaces Annex F.10. The extension defines how to encode coordinate reference systems (CRS) in GeoPackages using the ISO/OGC Well-known text representation of coordinate reference systems [2019] (CRS WKT2) Standard. Specifically, this revision adds coordinate epochs to the encoding of coordinate reference systems in a GeoPackage." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/10-195" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/20-000r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "21-057" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/08-133" - }, + "@language": "en", + "@value": "OGC GeoPackage WKT for Coordinate Reference Systems Extension" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/06-080r4", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/18-056" - }, + "@type": "xsd:date", + "@value": "2010-02-25" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/09-018" - }, + "@value": "Jerome Gasperi" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/09-112" - }, + "@id": "http://www.opengis.net/def/doc-type/sap" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/18-001r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/07-152" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=31065" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/13-099" + "@language": "en", + "@value": "GML 3.1.1 Application Schema for EO products" }, { - "@id": "http://www.opengis.net/def/docs/05-140" - }, + "@language": "en", + "@value": "06-080r4" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/05-118" - }, + "@id": "http://www.opengis.net/def/doc-type/sap" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/15-116" - }, + "@value": "This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGC" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/12-028r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/18-037r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "06-080r4" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/06-184r2" - }, + "@language": "en", + "@value": "GML 3.1.1 Application Schema for EO products" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/07-004", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/03-029" - }, + "@type": "xsd:date", + "@value": "2007-05-07" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/07-169" - }, + "@value": "Panagiotis (Peter) A. Vretanos" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/07-027r1" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/17-059" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/11-088r1" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=20431" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/05-029r4" + "@language": "en", + "@value": "07-004" }, { - "@id": "http://www.opengis.net/def/docs/08-002" - }, + "@language": "en", + "@value": "GeoDDS Mass Market" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/08-079" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/07-023r2" - }, + "@value": "This OpenGIS(r) document describes the API for two web services capable of generating several simplified data formats including GeoRSS and the Basic XML Feature Schema\r\n(BXFS). \r\n" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/07-095r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/07-166r2" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "07-004" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/21-010r2" - }, + "@language": "en", + "@value": "GeoDDS Mass Market (formerly GeoRSS) Interoperability Program Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/16-145", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/05-050" - }, + "@type": "xsd:date", + "@value": "2020-09-17" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/20-054r1" - }, + "@value": "Jon Blower, Maik Riechert, Bill Roberts" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/08-058r1" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/16-012r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/03-026" - }, + "@id": "https://www.w3.org/TR/covjson-overview/" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/20-092" + "@language": "en", + "@value": "16-145" }, { - "@id": "http://www.opengis.net/def/docs/05-115" - }, + "@language": "en", + "@value": "Overview of the CoverageJSON format" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/08-077" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/21-067" - }, + "@value": "This Note describes CoverageJSON, a data format for describing coverage data in JavaScript Object Notation (JSON), and provides an overview of its design and capabilities. The primary intended purpose of the format is to enable data transfer between servers and web browsers, to support the development of interactive, data-driven web applications. Coverage data is a term that encompasses many kinds of data whose properties vary with space, time and other dimensions, including (but not limited to) satellite imagery, weather forecasts and river gauge measurements. We describe the motivation and objectives of the format, and provide a high-level overview of its structure and semantics. We compare CoverageJSON with other coverage formats and data models and provide links to tools and libraries that can help users to produce and consume data in this format. This Note does not attempt to describe the full CoverageJSON specification in detail: this is available at the project website." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/21-041r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/11-058r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "16-145" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/16-142" - }, + "@language": "en", + "@value": "Overview of the CoverageJSON format" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/21-026", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/21-037" - }, + "@type": "xsd:date", + "@value": "2023-07-14" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/12-117r1" - }, + "@value": "Joan Maso" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/09-010" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/06-002r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/09-076r3" - }, + "@id": "https://docs.ogc.org/is/21-026/21-026.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/07-138r1" + "@language": "en", + "@value": "OGC Cloud Optimized GeoTIFF Standard" }, { - "@id": "http://www.opengis.net/def/docs/23-013" - }, + "@language": "en", + "@value": "21-026" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/16-125" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/15-012r2" - }, + "@value": "The Cloud Optimized GeoTIFF (COG) relies on two characteristics of the TIFF v6 format (tiles and reduced resolution subfiles), GeoTIFF keys for georeference, and the HTTP range, which allows for efficient downloading of parts of imagery and grid coverage data on the web and to make fast data visualization of TIFF or BigTIFF files and fast geospatial processing workflows possible. COG-aware applications can download only the information they need to visualize or process the data on the web. Numerous remote sensing datasets are available in cloud storage facilities that can benefit from optimized visualization and processing. This standard formalizes the requirements for a TIFF file to become a COG file and for the HTTP server to make COG files available in a fast fashion on the web.\r\n\r\nThe key work for crafting this OGC Standard was undertaken in the Open-Earth-Monitor Cyberinfrastructure (OEMC) project, which received funding from the European Union’s Horizon Europe research and innovation program under grant agreement number 101059548 and in the All Data 4 Green Deal - An Integrated, FAIR Approach for the Common European Data Space (AD4GD) project, which received funding from the European Union’s Horizon Europe research and innovation program under grant agreement number 101061001." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/06-187r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/15-039" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "21-026" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/08-073r2" - }, + "@language": "en", + "@value": "OGC Cloud Optimized GeoTIFF Standard" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/10-191r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/08-132" - }, + "@type": "xsd:date", + "@value": "2010-12-11" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/07-158" - }, + "@value": "Claus Nagel, Thomas Becker, Robert Kaden, Ki-Joune Li, Jiyeong Lee, Thomas H. Kolbe" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/08-076" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/19-077" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/12-027r3" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=41727" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/06-173r2" + "@language": "en", + "@value": "10-191r1" }, { - "@id": "http://www.opengis.net/def/docs/05-015" - }, - { - "@id": "http://www.opengis.net/def/docs/11-039r3" - }, - { - "@id": "http://www.opengis.net/def/docs/06-140" - }, - { - "@id": "http://www.opengis.net/def/docs/05-117" - }, - { - "@id": "http://www.opengis.net/def/docs/08-078r1" - }, - { - "@id": "http://www.opengis.net/def/docs/02-017r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-163" - }, - { - "@id": "http://www.opengis.net/def/docs/16-129" - }, - { - "@id": "http://www.opengis.net/def/docs/23-040" - }, - { - "@id": "http://www.opengis.net/def/docs/04-051" - }, - { - "@id": "http://www.opengis.net/def/docs/12-031r2" - }, - { - "@id": "http://www.opengis.net/def/docs/16-084" - }, - { - "@id": "http://www.opengis.net/def/docs/08-054r1" - }, - { - "@id": "http://www.opengis.net/def/docs/08-122r2" - }, - { - "@id": "http://www.opengis.net/def/docs/24-025" - }, - { - "@id": "http://www.opengis.net/def/docs/10-191r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-041r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-082" - }, - { - "@id": "http://www.opengis.net/def/docs/06-045r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-042r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-079r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-091r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-009r3" - }, - { - "@id": "http://www.opengis.net/def/docs/18-077r2" - }, - { - "@id": "http://www.opengis.net/def/docs/08-084r1" - }, - { - "@id": "http://www.opengis.net/def/docs/04-050r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-014" - }, - { - "@id": "http://www.opengis.net/def/docs/03-025" - }, - { - "@id": "http://www.opengis.net/def/docs/01-019" - }, - { - "@id": "http://www.opengis.net/def/docs/04-011r1" - }, - { - "@id": "http://www.opengis.net/def/docs/08-001" - }, - { - "@id": "http://www.opengis.net/def/docs/07-056r1" - }, - { - "@id": "http://www.opengis.net/def/docs/13-101" - }, - { - "@id": "http://www.opengis.net/def/docs/07-160r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-123" - }, - { - "@id": "http://www.opengis.net/def/docs/15-096" - }, - { - "@id": "http://www.opengis.net/def/docs/15-074r2" - }, - { - "@id": "http://www.opengis.net/def/docs/10-001" - }, - { - "@id": "http://www.opengis.net/def/docs/07-001r3" - }, - { - "@id": "http://www.opengis.net/def/docs/04-052" - }, - { - "@id": "http://www.opengis.net/def/docs/07-055r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-014" - }, - { - "@id": "http://www.opengis.net/def/docs/05-111r2" - }, - { - "@id": "http://www.opengis.net/def/docs/01-061" - }, - { - "@id": "http://www.opengis.net/def/docs/08-127" - }, - { - "@id": "http://www.opengis.net/def/docs/11-163" - }, - { - "@id": "http://www.opengis.net/def/docs/16-114r2" - }, - { - "@id": "http://www.opengis.net/def/docs/15-075r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-145" - }, - { - "@id": "http://www.opengis.net/def/docs/10-171" - }, - { - "@id": "http://www.opengis.net/def/docs/09-132r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-104r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-007r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-022r1" - }, - { - "@id": "http://www.opengis.net/def/docs/18-041r1" - }, - { - "@id": "http://www.opengis.net/def/docs/20-088" - }, - { - "@id": "http://www.opengis.net/def/docs/08-009r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-101" - }, - { - "@id": "http://www.opengis.net/def/docs/21-077" - }, - { - "@id": "http://www.opengis.net/def/docs/07-032" - }, - { - "@id": "http://www.opengis.net/def/docs/10-196r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-112r1" - }, - { - "@id": "http://www.opengis.net/def/docs/04-039" - }, - { - "@id": "http://www.opengis.net/def/docs/04-060r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-047" - }, - { - "@id": "http://www.opengis.net/def/docs/06-107r1" - }, - { - "@id": "http://www.opengis.net/def/docs/08-000" - }, - { - "@id": "http://www.opengis.net/def/docs/09-084r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-004" - }, - { - "@id": "http://www.opengis.net/def/docs/15-074" - }, - { - "@id": "http://www.opengis.net/def/docs/05-116" - }, - { - "@id": "http://www.opengis.net/def/docs/13-021r3" - }, - { - "@id": "http://www.opengis.net/def/docs/09-122" - }, - { - "@id": "http://www.opengis.net/def/docs/11-094" - }, - { - "@id": "http://www.opengis.net/def/docs/10-134" - }, - { - "@id": "http://www.opengis.net/def/docs/05-102r1" - }, - { - "@id": "http://www.opengis.net/def/docs/14-121r2" - }, - { - "@id": "http://www.opengis.net/def/docs/09-042" - }, - { - "@id": "http://www.opengis.net/def/docs/04-100" - }, - { - "@id": "http://www.opengis.net/def/docs/06-182r1" - }, - { - "@id": "http://www.opengis.net/def/docs/23-022r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-166r2" - }, - { - "@id": "http://www.opengis.net/def/docs/17-049" - }, - { - "@id": "http://www.opengis.net/def/docs/06-155" - }, - { - "@id": "http://www.opengis.net/def/docs/05-084" - }, - { - "@id": "http://www.opengis.net/def/docs/16-079" - }, - { - "@id": "http://www.opengis.net/def/docs/07-012" - }, - { - "@id": "http://www.opengis.net/def/docs/19-090r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-029" - }, - { - "@id": "http://www.opengis.net/def/docs/04-071" - }, - { - "@id": "http://www.opengis.net/def/docs/13-068" - }, - { - "@id": "http://www.opengis.net/def/docs/06-154" - }, - { - "@id": "http://www.opengis.net/def/docs/09-124r2" - }, + "@language": "en", + "@value": "Requirements and Space-Event Modeling for Indoor Navigation" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/23-056" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/15-100r1" - }, + "@value": "This OpenGIS® Discussion Paper presents a Multilayered Space-Event Model for indoor navigation which simultaneously addresses route planning, multiple localization methods, navigation contexts, and different locomotion types. The paper contains the corresponding data models as well as their encoding in GML 3.1.1." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/19-004" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/15-122r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "10-191r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/07-124r2" + "@language": "en", + "@value": "Requirements and Space-Event Modeling for Indoor Navigation" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-027", + "@id": "http://www.opengis.net/def/docs/10-126r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-26" + "@value": "2012-08-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Robert Cass" + "@value": "Peter Taylor" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -5199,27 +5262,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-027.html" + "@id": "https://portal.ogc.org/files/?artifact_id=48531" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-027" + "@value": "10-126r3" }, { "@language": "en", - "@value": "Testbed-13: GeoPackage Engineering Report" + "@value": "WaterML 2.0: Part 1- Timeseries" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report details the processes and results related to generating GeoPackages developed to contain topographic vector features and supporting symbologies based on The National Map (TNM) product of the United States Geological Survey (USGS)." + "@value": "This document is an OGC® Encoding Standard for the representation of hydrological observations data with a specific focus on time series structures. WaterML2.0 is implemented as an application schema of the Geography Markup Language version 3.2.1, making use of the OGC Observations & Measurements standards.\r\nWaterML2.0 is designed as an extensible schema to allow encoding of data to be used in a variety of exchange scenarios. Example areas of usage are: exchange of data for operational hydrological monitoring programs; supporting operation of infrastructure (e.g. dams, supply systems); cross-border exchange of observational data; release of data for public dissemination; enhancing disaster management through data exchange; and exchange in support of national reporting. \r\nThe core aspect of the model is in the correct, precise description of time series. Interpretation of time series relies on understanding the nature of the process that generated them. This standard provides the framework under which time series can be exchanged with appropriate metadata to allow correct machine interpretation and thus correct use for further analysis. Existing systems should be able to use this model as a conceptual 'bridge' between existing schema or systems, allowing consistency of the data to maintained.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -5230,35 +5293,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-027" + "@value": "10-126r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: GeoPackage Engineering Report" + "@value": "OGC® WaterML 2.0: Part 1- Timeseries" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-104r2", + "@id": "http://www.opengis.net/def/docs/16-043", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-08-16" + "@value": "2017-03-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Scarponcini" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -5268,27 +5331,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=75121" + "@id": "https://docs.ogc.org/per/16-043.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-104r2" + "@value": "Testbed-12 Web Integration Service" }, { "@language": "en", - "@value": "InfraGML 1.0: Part 4 - LandInfra Roads - Encoding Standard" + "@value": "16-043" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 4 addresses the Road and RoadCrossSection Requirements Class from LandInfra." + "@value": "For many years OGC has been developing a suite of standards defining web services interfaces and encodings for geospatial processing. The suite includes a Web Map Service (WMS), a Web Map Tiling Service (WMTS), a Web Feature Service (WFS), a Web Coverage Service (WCS), a Web Catalogue Service (CSW), the Sensor Web (SWE) suite of services, etc. These service interfaces and their implementations have, more or less, been developed independently of one another resulting in isolation and poor integration between them. For example, consider a map generated by a WMS. A client or user cannot easily determine which source data was used to create the map and how to download that source data though an OGC data service such as WFS or WCS. Furthermore when one considers the Publish-Find-Bind paradigm, OGC can only partially support the full potential of this paradigm. This is because OGC structured catalogues can only register services in isolation of other related services and cannot automatically determine the relationships among services and the resources they offer.\r\n\r\nIn order to achieve better integration between OGC web services and enhance the publish-find-bind paradigm, this OGC Engineering Report defines and discusses three key elements. These are:\r\n\r\nDefining a new service, called the Web Integration Service (WIS), which allows for the discovery and access to integrated sets of OGC web services deployed at an endpoint.\r\n\r\nSpecifying a means of discovering and describing associations between web resources (both OGC and non-OGC).\r\n\r\nDefining extensions to the OGC catalogue to allow the service to harvest and make discoverable a rich set of linked OGC and non-OGC resources.\r\n\r\nThe Web Integration Service (WIS) is an aggregation service whose only purpose is to provide a list of references to a suite of other, perhaps related OGC services available at an endpoint.\r\n\r\nA new operation, named GetAssociations, is defined as an extension such that existing OGC services (WMS, WFS, WCS, etc.) may implement this operation in order to support rich auto-discovery. This operation enables OGC web services to externalize their internal association knowledge about their content and relationships to other OGC and external resources. For example, a WMS would know if the source data for a layer it offers is a Shapefile, or a WFS feature type, or another WMS layer (i.e. cascading), or if a WMTS layer exists that renders the same information more efficiently. This internal knowledge can now be externalized via the GetAssociations operation.\r\n\r\nCurrently, OGC Catalogues Service instances can harvest the capabilities document of an OGC web service, register that service, register the existence of the individual offerings that the service offers and also register the association between the service and the content it offers. Thus, the entire harvesting process is focused on a single OGC web service and consequently offers a limited scope of discovery. In order to support rich discovery, a catalogue needs to be able to automatically register services found at an endpoint as well as register all known associations among those services, their offerings and other OGC and non-OGC resources. This involves harvesting a service’s capabilities document to determine what content the service offers but it also involves further interrogating the service to determine of what (if any) other associations it is aware. Populated with this enhanced knowledge a client may now use a catalogue to, for example, find the description of feature data and then be able to find the WFS that offer that data, a WMS that renders those features into a map, a WMTS that has a tiled representation of that data, etc. In order to support this kind of rich discovery, a new CSW-ebRIM package is specified that defines ebRIM object types, associations, classifications and stored queries that support the description of integrated OGC web service and their artifacts within the catalogue." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -5299,30 +5362,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-104r2" + "@value": "16-043" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC InfraGML 1.0: Part 4 - LandInfra Roads - Encoding Standard" + "@value": "Testbed-12 Web Integration Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-023r1", + "@id": "http://www.opengis.net/def/docs/20-019r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-12-11" + "@value": "2021-01-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andrea Aime" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -5337,17 +5400,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-023r1.html" + "@id": "https://docs.ogc.org/per/20-019r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report" + "@value": "20-019r1" }, { "@language": "en", - "@value": "19-023r1" + "@value": "GeoPackage Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -5357,7 +5420,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 15 Engineering Report (ER) describes a style encoding and metadata conceptual model that provides information for understanding styles intended usage, availability, compatibility with existing layers, and supporting style search. A style is a sequence of rules of symbolizing instructions to be applied by a rendering engine on one or more features and/or coverages" + "@value": "In Testbed-16, participants researched ways to mitigate these limitations, particularly in the context of the Ordnance Survey (OS) MasterMap Topography datasets. The Testbed activity also made use of OS Open Zoomstack, a smaller, freely available, multi-scale dataset. To address the first two limitations, Testbed participants developed GeoPackage metadata profiles designed to advance the discoverability of the contents of a GeoPackage and exchange the OS portrayal styles and symbols. The metadata proved to be interoperable between the server and client implementation." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -5368,35 +5431,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-023r1" + "@value": "20-019r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report" + "@value": "OGC Testbed-16: GeoPackage Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-116", + "@id": "http://www.opengis.net/def/docs/12-154", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-04-26" + "@value": "2013-02-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Giuseppe Conti, Fabio Roncato" + "@value": "Darko Androsevic" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -5406,27 +5469,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=68040" + "@id": "https://portal.ogc.org/files/?artifact_id=51889" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-116" + "@value": "12-154" }, { "@language": "en", - "@value": "AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper" + "@value": "OWS-9 OWS Innovations GMLJP2 for National Imagery Transmission Format (NITF) Engineering Report " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides a proposal for a new O&M (Observations and Measurements) profile focused on Active and Healthy Ageing, called AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper). This document introduces the overall need for such a profile and it discusses the measures which have been identified." + "@value": "This OGC® document provides mapping of the national imagery transmission format (NITF) version 2.1 format and NITF tagged record extensions (TRE) to GMLJP2 v2.0 (draft) format.\r\nThis Engineering Report was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative. \r\nThis document further describes study results of analyses of NITF and NITF extensions (TRE) capabilities and how they can be supported by GMLJP2 2.0 (draft). This activity was a part of the OGC OWS-9 Innovations thread.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -5437,43 +5500,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-116" + "@value": "12-154" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/orm", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/08-062r7" + "@value": "OWS-9 OWS Innovations GMLJP2 for National Imagery Transmission Format (NITF) Engineering Report " } ] }, { - "@id": "http://www.opengis.net/def/docs/20-090", + "@id": "http://www.opengis.net/def/docs/05-007r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-18" + "@value": "2005-09-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona" + "@value": "Peter Schut, Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -5483,27 +5538,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-090.html" + "@id": "https://portal.ogc.org/files/?artifact_id=12184" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-090" + "@value": "Web Processing Service" }, { "@language": "en", - "@value": "OGC API – Maps Sprint 2020: Summary Engineering Report" + "@value": "05-007r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) documents the results and recommendations from a code sprint that was held from 28 to 29 July 2020 to advance the development of the draft OGC API – Maps Standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application, or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The OGC API - Maps Sprint was an online virtual event. The sprint was sponsored by Ordnance Survey." + "@value": "This document specifies the interface to a Web Processing Service (WPS). A WPS can be configured to offer any sort of GIS functionality to clients across a network, including access to pre-programmed calculations and/or computation models that operate on spatially referenced data. A WPS may offer calculations as simple as subtracting one set of spatially referenced numbers from another (e.g., determining the difference in influenza cases between two different seasons), or as complicated as a global climate change model. The data required by the WPS can be delivered across a network, or available at the server." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -5514,30 +5569,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-090" + "@value": "05-007r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API – Maps Sprint 2020: Summary Engineering Report" + "@value": "Web Processing Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-184", + "@id": "http://www.opengis.net/def/docs/20-029", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-12-13" + "@value": "2020-10-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "Timothy Miller, Gil Trenum, Josh Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -5552,17 +5607,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41573" + "@id": "https://docs.ogc.org/per/20-029.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-184" + "@value": "3D Data Container Engineering Report" }, { "@language": "en", - "@value": "OGC Fusion Standards Study, Phase 2 Engineering Report" + "@value": "20-029" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -5572,7 +5627,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report summarizes two phases of the Open Geospatial Consortium (OGC®) Fusion Standards study and of the fusion prototypes developed during the OWS-7 Testbed which occurred between the two study phases. Recommendations from the first phase of the study were implemented in OWS-7. Based upon the results of OWS-7, responses to two Requests for Information and a multi-day workshop, this report provides a cumulative set of recommendations for advancing fusion based on open standards. " + "@value": "This OGC Engineering Report documents the goals, activities, experiences, and outcomes of the 3D Data Container and Tiles API Pilot. Participants in the Pilot cooperatively defined a GeoVolume (3D Geospatial Volume) resource and developed a GeoVolumes API based on the concept to provide access to different 2D and 3D geospatial dataset distributions organized by region of interest. Multiple client and server implementations of the GeoVolumes API successfully carried out technology interchange experiments that demonstrated the value of the API for improving interoperability between 3D geospatial data formats." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -5583,35 +5638,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-184" + "@value": "20-029" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Fusion Standards Study, Phase 2 Engineering Report" + "@value": "3D Data Container Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-039r2", + "@id": "http://www.opengis.net/def/docs/07-011", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-13" + "@value": "2007-12-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Robert Gibb, Byron Cochrane, Matthew Purss" + "@value": "OGC" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -5621,27 +5676,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-039r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=19820" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-039r2" + "@value": "07-011" }, { "@language": "en", - "@value": "DGGS and DGGS API Engineering Report" + "@value": "Topic 06 - Schema for coverage geometry and functions" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed-16 Engineering Report (ER) documents the needs and key requirements for drafting an OGC Discrete Global Grid Systems (DGGS) Application Programming Interface (API) standard. The draft DGGS API is defined using the OpenAPI 3.0 specification. The work documented in this ER represents the beginning of a multi-initiative process to fully realize the benefits of standards compliant DGGS implementations and to help drive adoption of DGGS as a key element in advanced Spatial Data Architectures. The Testbed participants investigated a Client-Server DGGS architecture involving one (or more) DGGS Server implementations, DGGS-enabled Data Sources and a simple front-end DGGS Client. DGGS API functionality will be tested using one (or more) simple use case scenarios focusing on the two-way translation between geographic locations and DGGS Zonal Identifiers." + "@value": "This International Standard defines a conceptual schema for the spatial characteristics of coverages. Coverages support mapping from a spatial, temporal or spatiotemporal domain to feature attribute values where feature attribute types are common to all geographic positions within the domain. A coverage domain consists of a collection of direct positions in a coordinate space that may be defined in terms of up to three spatial dimensions as well as a temporal dimension." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -5652,35 +5707,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-039r2" + "@value": "07-011" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: DGGS and DGGS API Engineering Report" + "@value": "Topic 6 - Schema for coverage geometry and functions" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-054r1", + "@id": "http://www.opengis.net/def/docs/20-094", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-12" + "@value": "2021-02-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Apple Inc." } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -5690,27 +5745,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=16080" + "@id": "https://docs.ogc.org/cs/20-094/index.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-054r1" + "@value": "20-094" }, { "@language": "en", - "@value": "Image Geopostioning Service" + "@value": "Indoor Mapping Data Format" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the interface to an Image Geopositioning Service that adjusts the georeferencing coordinate transformations of multiple images. This adjustment is normally done using a photogrammetric triangulation process, although other methods could be used. Such triangulation adjusts the parameter values of the image georeferencing coordinate transformations using a least-squares fitting process to measured image positions with known error statistics." + "@value": "Indoor Mapping Data Format (referenced throughout this document as IMDF) provides a generalized, yet comprehensive model for any indoor location, providing a basis for orientation, navigation and discovery. In this release there are also detailed instructions for modeling the spaces of an airport, a shopping mall, and a train station.\r\n\r\nThis release also has an extension model which enables a venue, organization, or even an industry to create valid features and validations not available in the current specification for private or public use\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -5721,35 +5776,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-054r1" + "@value": "20-094" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Image Geopostioning Service" + "@value": "Indoor Mapping Data Format" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-122r1", + "@id": "http://www.opengis.net/def/docs/17-069r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-04-26" + "@value": "2022-05-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Randolph Gladish" + "@value": "Clemens Portele, Panagiotis (Peter) A. Vretanos, Charles Heazel" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -5759,27 +5814,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=66606" + "@id": "https://docs.ogc.org/is/17-069r4/17-069r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Implications for an OGC GeoPackage Symbology Encoding Standard" + "@value": "OGC API - Features - Part 1: Core corrigendum" }, { "@language": "en", - "@value": "15-122r1" + "@value": "17-069r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The GeoPackage Standards Working Group (SWG) presents a discussion of symbology encapsulation for conveying presentation information for vector features contained within in a GeoPackage. " + "@value": "This document specifies the behavior of Web APIs that provide access to features in a dataset in a manner independent of the underlying data store. This standard defines discovery and query operations.\r\n\r\nDiscovery operations enable clients to interrogate the API, including the API definition and metadata about the feature collections provided by the API, to determine the capabilities of the API and retrieve information about available distributions of the dataset.\r\n\r\nQuery operations enable clients to retrieve features from the underlying data store based upon simple selection criteria, defined by the client." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -5790,35 +5845,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-122r1" + "@value": "17-069r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Implications for an OGC GeoPackage Symbology Encoding Standard" + "@value": "OGC API - Features - Part 1: Core corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-100r2", + "@id": "http://www.opengis.net/def/docs/18-009", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-10-07" + "@value": "2020-02-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos" + "@value": "P S Acharya, Scott Simmons, A Kaushal, M K Munshi " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-profile" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -5828,27 +5883,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39853" + "@id": "https://portal.ogc.org/files/?artifact_id=77858" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geography Markup Language (GML) simple features profile" + "@value": "18-009" }, { "@language": "en", - "@value": "10-100r2" + "@value": "OGC India Plugfest - 2017 (OIP-2017) Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-profile" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This approved OpenGIS® Implementation Standard defines a Simple Features profile of the Geography Markup Language version 3.2. This Simple Features Profile has been aligned with the OGC Simple Features standard for SQL version 1.2. Simple Features include: Point, Curve (LineString), Surface (Polygon), Geometry, MultiPoint, MultiCurve, MultiSurface, and MultiGeometry. The detailed abstract model for OGC features and geometry can be found in the OGC Abstract Specification, Topic Volume 1: Features (which is equivalent to ISO 19107)." + "@value": "The Open Geospatial Consortium (OGC) and the Department of Science & Technology (DST) under the Government of India conducted the OGC India Plugfest 2017 (OIP-2017). The OIP-2017 was targeted at enhancing the interoperability among geospatial products and web services based on OGC standards within the Indian Geospatial Information (GI) community. The successful conclusion of OIP-2017 will assist National Spatial Data Infrastructure (NSDI) under DST to provide guidance on best practices using OGC standards for development of applications in several important & flagship schemes/programmes of the Government such as Smart Cities, Atal Mission for Rejuvenation through Urban Trasnformation (AMRUT); National Land Records Moderinisation Programme (NLRMP); Clean India (Swatchh Bharat – Urban & Rural); National Mission on Clean Ganga; Compensatory Afforestation Fund Management & Planning Authority (CAMPA); State SDIs; Digital India, and others.\r\nThis engineering report written jointly by OGC and DST is addressed to both the domestic (Indian) and international audiences.\r\nOIP-2017 was funded by the OGC India Foundation with supporting OGC staff resources from the OGC Innovation Program.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -5859,35 +5914,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-100r2" + "@value": "18-009" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geography Markup Language (GML) simple features profile" + "@value": "OGC India Plugfest - 2017 (OIP-2017) Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-050", + "@id": "http://www.opengis.net/def/docs/03-088r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-05-02" + "@value": "2004-01-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Craig Bruce" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -5897,27 +5952,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12983" + "@id": "https://portal.ogc.org/files/?artifact_id=4550" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-050" + "@value": "03-088r6" }, { "@language": "en", - "@value": "GML Performance Investigations by CubeWerx" + "@value": "OGC Web Services Common" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report proposes and executes methods to evaluate the performance of the use of the Geography Markup Language (GML) as encoded in various ways." + "@value": "This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -5928,35 +5983,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-050" + "@value": "03-088r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML Performance Investigations by CubeWerx" + "@value": "OGC Web Services Common" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-009r6", + "@id": "http://www.opengis.net/def/docs/20-085r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-02-13" + "@value": "2021-03-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arthur Na, Mark Priest" + "@value": "USGIF & OGC" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -5966,27 +6021,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=26667" + "@id": "https://usgif.org/usgif_msgwg_ogc_technical_paper_march_2021/" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-009r6" + "@value": "Advancing the Interoperability of Geospatial Intelligence Tradecraft with 3D Modeling, Simulation, and Game Engines" }, { "@language": "en", - "@value": "Sensor Observation Service" + "@value": "20-085r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Sensor Observation Service Interface Standard (SOS) provides an API for managing deployed sensors and retrieving sensor data and specifically “observation” data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards." + "@value": "The objectives of this MS&G\r\nTechnical Paper are focused on identifying technology trends\r\nthat are influencing the convergence of GEOINT and M&S\r\ntradecraft. The purpose is to advance ideas and techniques,\r\nsuch as reality modeling of 3D environments, which increase\r\nthe knowledge-base and capacity of the geospatial analyst\r\ncommunity writ large." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -5997,61 +6052,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-009r6" + "@value": "20-085r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Sensor Observation Service" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/orm/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type OpenGIS Reference Model" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Documents of type OpenGIS Reference Model" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/08-062r7" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Documents of type OpenGIS Reference Model" + "@value": "Advancing the Interoperability of Geospatial Intelligence Tradecraft with 3D Modeling, Simulation, and Game Engines" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-018", + "@id": "http://www.opengis.net/def/docs/03-021", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-17" + "@value": "2003-01-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Philippe M" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -6066,17 +6090,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20583" + "@id": "https://portal.ogc.org/files/?artifact_id=1328" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-018" + "@value": "Integrated Client for Multiple OGC-compliant Services" }, { "@language": "en", - "@value": "Sensor Planning Service Application Profile for EO Sensors" + "@value": "03-021" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -6086,7 +6110,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion Paper explains how a Sensor Planning Service is organised and implemented for the Earth Observation domain." + "@value": "Provides an overview of the requirements, architecture, and design of Integrated Clients developed during the OGC Open Web Services" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6097,35 +6121,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-018" + "@value": "03-021" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Sensor Planning Service Application Profile for EO Sensors" + "@value": "Integrated Client for Multiple OGC-compliant Services" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-079", + "@id": "http://www.opengis.net/def/docs/09-012", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-09-12" + "@value": "2009-08-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Herring" + "@value": "Craig Bruce" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -6135,27 +6159,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=28176" + "@id": "https://portal.ogc.org/files/?artifact_id=33519" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS5: OGC Web feature service, core and extensions" + "@value": "09-012" }, { "@language": "en", - "@value": "08-079" + "@value": "OWS-6 Symbology-Encoding Harmonization ER" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard specifies the behavior of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations and transaction operations. Discovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers. Retrieval operations allow features to be retrieved from the opaque underlying data store based upon constraints on spatial and non-spatial feature properties defined by the client. Transaction operations allow features to be created, changed and deleted from the opaque underlying data store." + "@value": "This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the harmonization of OGC Styled Layer Descriptor (SLD) and Symbology Encoding (SE) symbology formats with ISO 19117 symbology format, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6166,35 +6190,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-079" + "@value": "09-012" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS5: OGC Web feature service, core and extensions" + "@value": "OWS-6 Symbology-Encoding Harmonization ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-098r1", + "@id": "http://www.opengis.net/def/docs/17-029r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-12-22" + "@value": "2018-01-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó, Lucy Bastin " + "@value": "Benjamin Pross, Christoph Stasch" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -6204,27 +6228,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/15-098r1/15-098r1.html" + "@id": "https://docs.ogc.org/per/17-029r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geospatial User Feedback Standard: XML Encoding Extension" + "@value": "17-029r1" }, { "@language": "en", - "@value": "15-098r1" + "@value": "Testbed-13: Workflows ER" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Geospatial User Feedback XML encoding standard is based on the OGC Geospatial User Feedback conceptual model [OGC 15-097]. Geospatial User Feedback (GUF) is metadata that is predominantly produced by the consumers of geospatial data products based on their use and experience with those products. This standard complements the existing metadata conventions whereby documents recording dataset characteristics and production workflows are generated by the creator, publisher, or curator of a data product. As a part of metadata, the GUF data model internally reuses some elements of ISO 19115-1 (the updated version of the OGC Abstract Specification Topic 11) but not the general structure. This selective use of ISO metadata elements prioritizes future interoperability with developing ISO metadata models.\r\nThis standard can be used in combination with the OGC 15-097 Conceptual Model Standard. In the future, other encodings may be considered, being an alternative using the JSON-LD encoding based on parts of schema.org.\r\n" + "@value": "This Engineering Report (ER) addresses the development of a consistent, flexible, adaptable workflow that will run behind the scenes. A user should be able to discover existing workflows via a catalog and execute them using their own datasets. An expert should be able to create workflows and to publish them. Previous OGC Testbed initiatives investigated workflows in the geospatial domain:\r\n\r\nOWS 3 Imagery Workflow Experiments\r\n\r\nOWS 4 WPS IPR Workflow descriptions and lessons learned\r\n\r\nOWS 4 Topology Quality Assessment Interoperability Program Report\r\n\r\nOWS 5 Data View Architecture Engineering Report\r\n\r\nOWS 6 Geoprocessing Workflow Architecture Engineering Report\r\n\r\nThese initiatives mostly favored Business Processing Execution Language (BPEL) as the workflow execution language. More recent studies ([6], [7]) were performed using BPMN as a means for describing and executing workflows comprised of OGC Web services. This ER will give an overview about existing approaches to compose and execute geospatial workflows and will describe the approach taken in Testbed-13, taking into account security aspects." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6235,35 +6259,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-098r1" + "@value": "17-029r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Geospatial User Feedback Standard: XML Encoding Extension" + "@value": "OGC Testbed-13: Workflows ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-025r1", + "@id": "http://www.opengis.net/def/docs/10-025r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-11-02" + "@value": "2011-03-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -6273,27 +6297,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39967" + "@id": "https://portal.ogc.org/files/?artifact_id=41510" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Feature Service 2.0 Interface Standard (also ISO 19142)" + "@value": "10-025r1" }, { "@language": "en", - "@value": "09-025r1" + "@value": "Observations and Measurements - XML Implementation" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This International Standard specifies the behaviour of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored parameterized query expressions.\r\nDiscovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers.\r\nQuery operations allow features or values of feature properties to be retrieved from the underlying data store based upon constraints, defined by the client, on feature properties.\r\nLocking operations allow exclusive access to features for the purpose of modifying or deleting features.\r\nTransaction operations allow features to be created, changed, replaced and deleted from the underlying data store.\r\nStored query operations allow clients to create, drop, list and described parameterized query expressions that are stored by the server and can be repeatedly invoked using different parameter values." + "@value": "This standard specifies an XML implementation for the OGC and ISO Observations and Measurements (O&M) conceptual model (OGC Observations and Measurements v2.0 also published as ISO/DIS 19156), including a schema for Sampling Features. This encoding is an essential dependency for the OGC Sensor Observation Service (SOS) Interface Standard.\r\nMore specifically, this standard defines XML schemas for observations, and for features involved in sampling when making observations. These provide document models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6304,35 +6328,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-025r1" + "@value": "10-025r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142)" + "@value": "Observations and Measurements - XML Implementation" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-023r1", + "@id": "http://www.opengis.net/def/docs/14-106", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-03-06" + "@value": "2015-01-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó" + "@value": "Carl Reed, Jennifer Harne" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -6342,27 +6366,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-023r1.html" + "@id": "https://docs.ogc.org/bp/14-106/14-106.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "MapML Engineering Report" + "@value": "14-106" }, { "@language": "en", - "@value": "18-023r1" + "@value": "Unified Geo-data Reference Model for Law Enforcement and Public Safety" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This is the second Engineering Report (ER) about the Map Markup Language (MapML) cite:[Rushforth2018] resulting from OGC Testbed initiatives. To find an introduction of MapML and how it works, please, refer to the previous ER OGC 17-019 cite:[Maso2018]. MapML is a new media type that can be included in a element of a section, in a Hypertext Markup Language (HTML) page. This document is mainly focused on the description of the MapML media type and its evolutions. In particular, it considers issues about the Coordinate Reference System (CRS) types in MapML, feature and properties encoding, Cascading Style Sheets (CSS) symbolization, multidimensional data etc.\r\n\r\nThis document describes two implementations done in OGC Testbed-14: a Cloud-based Proxy (cascade) for MapML done by CubeWerx and a ServiceWorker Proxy for MapML done by George Mason University (GMU).\r\n\r\nFinally, this document reviews how the next generation of OGC services can integrate MapML files as part of the designing of use cases and discusses how MapML can be used by social media.\r\n\r\nThis document proposals increases functionality in MapML and makes proposals for increasing the interoperability of the proposed encoding with the OGC standards baseline and future generations of OGC standards for maps and tiles." + "@value": "This document provides an overview of the Unified Geo-data Reference Model for Law Enforcement and Public Safety (Unified Model). The Unified Model was originally developed by the GIS Center for Security (GIS CS), Abu Dhabi Police. The GIS CS was initiated based on a UAE Ministry of Interior issued decree to establish GIS CS with the core mission: “To geo-enable police services and applications using International standards and best practices.” In 2010, the GIS SC initiated a program to develop a Standardized GIS Environment (SGA). Part of this effort was to define and implement a standard data model for sharing Law Enforcement and Public Safety data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6373,35 +6397,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-023r1" + "@value": "14-106" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: MapML Engineering Report" + "@value": "Unified Geo-data Reference Model for Law Enforcement and Public Safety" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-094r1", + "@id": "http://www.opengis.net/def/docs/15-111r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-04" + "@value": "2016-12-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stephane Fellah" + "@value": "Paul Scarponcini" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -6411,27 +6435,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-094r1.html" + "@id": "https://docs.ogc.org/is/15-111r1/15-111r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-094r1" + "@value": "Land and Infrastructure Conceptual Model Standard (LandInfra)" }, { "@language": "en", - "@value": "Characterization of RDF Application Profiles for Simple Linked Data Application and Complex Analytic Applications Engineering" + "@value": "15-111r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) enhances the understanding of the concept of application profiles (AP) for ontologies based on the Web Ontology Language (OWL) and used by Linked Data (LD) applications. The concept of an Application Profile for Unified Modeling Language (UML) and Extensible Markup Language (XML) schemas, in particular Geographic Markup Language (GML) application profiles, is pretty well-defined and understood within the communities of Open Geospatial Consortium (OGC) and International Organization for Standardization (ISO). Moreover, in the context of Linked Data and ontologies, the term is still ill-defined, as ontologies are defined using an Open World Assumption (OWA), as well as classes and properties are first-class modeling objects in ontology modeling. The work documented in this report includes:\r\n\r\nDefinition and characterization of Resource Description Framework (RDF) application profiles for simple linked data applications and complex analytic linked data applications.\r\n\r\nDetermination of preliminary techniques for the development of subsets of ontologies to support different types of applications (simple linked data and complex analytic)\r\n\r\nAn initial model for defining metadata about application profiles, so they can be searched and discovered by agents." + "@value": "This OGC Land and Infrastructure Conceptual Model Standard presents the implementation-independent concepts supporting land and civil engineering infrastructure facilities. Conceptual model subject areas include facilities, projects, alignment, road, rail, survey, land features, land division, and wet infrastructure (storm drainage, wastewater, and water distribution systems). The initial release of this standard includes all of these subject areas except wet infrastructure, which is anticipated to be released as a future extension. \r\nThis standard assumes the reader has a basic understanding of surveying and civil engineering concepts.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6442,35 +6466,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-094r1" + "@value": "15-111r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Characterization of RDF Application Profiles for Simple Linked Data Application and Complex Analytic Applicat" + "@value": "OGC® Land and Infrastructure Conceptual Model Standard (LandInfra)" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-015r2", + "@id": "http://www.opengis.net/def/docs/02-028", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-15" + "@value": "2002-04-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Tom McCarty" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/ipr" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -6480,27 +6504,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-015r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1141" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: Machine Learning Engineering Report" + "@value": "Sensor Collection Service" }, { "@language": "en", - "@value": "20-015r2" + "@value": "02-028" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/ipr" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report describes the work performed in the Machine Learning Thread of OGC’s Testbed-16 initiative.\r\n\r\nPrevious OGC testbed tasks concerned with Machine Learning (ML) concentrated on the methods and apparatus of training models to produce high quality results. The work reported in this ER, however, focuses less on the accuracy of machine models and more on how the entire machine learning processing chain from discovering training data to visualizing the results of a ML model run can be integrated into a standards-based data infrastructure specifically based on OGC interface standards.\r\n\r\nThe work performed in this thread consisted of:\r\n\r\nTraining ML models;\r\n\r\nDeploying trained ML models;\r\n\r\nMaking deployed ML models discoverable;\r\n\r\nExecuting an ML model;\r\n\r\nPublishing the results from executing a ML model;\r\n\r\nVisualizing the results from running a ML model.\r\n\r\nAt each step, the following OGC and related standards were integrated into the workflow to provide an infrastructure upon which the above activities were performed:\r\n\r\nOGC API - Features: Approved OGC Standard that provides API building blocks to create, retrieve, modify and query features on the Web.\r\n\r\nOGC API - Coverages: Draft OGC Standard that provides API building blocks to create, retrieve, modify and query coverages on the Web.\r\n\r\nOGC API - Records: Draft OGC Standard that provides API building block to create, modify and query catalogues on the Web.\r\n\r\nApplication Deployment and Execution Service: Draft OGC Standard that provides API building blocks to deploy, execute and retrieve results of processes on the Web.\r\n\r\nMapML is a specification that was published by the Maps For HTML Community Group. It extends the base HTML map element to handle the display and editing of interactive geographic maps and map data without the need of special plugins or JavaScript libraries. The Design of MapML resolves a Web Platform gap by combining map and map data semantics into a hypermedia format that is syntactically and architecturally compatible with and derived from HTML. It provides a standardized way for declarative HTML content to communicate with custom spatial server software (which currently use HTTP APIs based on multiple queries and responses). It allows map and map data semantics to be either included in HTML directly, or referred to at arbitrary URLs that describe stand-alone layers of map content, including hyper-linked annotations to further content.\r\n\r\nParticular emphasis was placed on using services based on the emerging OGC API Framework suite of API building blocks." + "@value": "The basic function of the Sensor Collection Service (SCS) is to provide a web-enabled interface to a sensor, collection of sensors or sensor proxy. Sensors are defined as devices that measure physical quantities. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6511,35 +6535,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-015r2" + "@value": "02-028" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: Machine Learning Engineering Report" + "@value": "Sensor Collection Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-088", + "@id": "http://www.opengis.net/def/docs/12-052", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-15" + "@value": "2012-07-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "K. Navulur, M.C. Abrams" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -6549,27 +6573,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/20-088.html" + "@id": "https://portal.ogc.org/files/?artifact_id=48650" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-088" + "@value": "12-052" }, { "@language": "en", - "@value": "Standardizing a Framework for Spatial and Spectral Error Propagation" + "@value": "WCS 2.0.1 Corrigendum Release Notes" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Discussion Paper presents a proposal that recommends the development of Open Geospatial Consortium (OGC) standards that define a framework for location-based service metrics that inform the spatial, spectral, and temporal errors associated with various data sources. This paper discusses current industry practices on spatial errors, spectral errors, and error propagation. The paper also presents a proposed framework and a recommended study effort." + "@value": "This document represents the release notes for the OGC Web Coverage Service (WCS) Interface Standard corrigendum 2.0.1. This corrigendum for WCS supersedes previous WCS versions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6580,35 +6604,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-088" + "@value": "12-052" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Standardizing a Framework for Spatial and Spectral Error Propagation" + "@value": "OGC WCS 2.0.1 Corrigendum Release Notes" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-007r4", + "@id": "http://www.opengis.net/def/docs/07-067r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-08-19" + "@value": "2008-04-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Bobbitt" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -6618,27 +6642,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=11498" + "@id": "https://portal.ogc.org/files/?artifact_id=27297" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Units of Measure Recommendation" + "@value": "07-067r5" }, { "@language": "en", - "@value": "02-007r4" + "@value": "Web Coverage Service (WCS) Implementation Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Common semantic for units of measurement to be used across all OGC specifications." + "@value": "The OpenGIS® Web Coverage Service Interface Standard (WCS) defines a standard interface and operations that enables interoperable access to geospatial coverages [http://www.opengeospatial.org/ogc/glossary/c]. The term grid coverages typically refers to content such as satellite images, digital aerial photos, digital elevation data, and other phenomena represented by values at each measurement point. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6649,35 +6673,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-007r4" + "@value": "07-067r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Units of Measure Recommendation" + "@value": "Web Coverage Service (WCS) Implementation Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-038", + "@id": "http://www.opengis.net/def/docs/03-014", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-18" + "@value": "2003-01-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Harrison" + "@value": "J" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -6687,27 +6711,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-038.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1337" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-13: Fit-for-Purpose Engineering Report" + "@value": "03-014" }, { "@language": "en", - "@value": "17-038" + "@value": "OGC Web Services SOAP Experiment Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The objective of the Fit for Purpose (FFP) effort in Testbed 13 was to develop and test filters and encodings in a platform that can ease the work of end-users, especially those who are not expert in dealing with geospatial data and satellite imagery. The platform was demonstrated in a scenario that showed how these filters can enable information exchange for humanitarian relief and analysis of mass movement of populations.\r\n\r\nThis section provides a summary of the interoperability tools and practices used by Testbed 13 participants in this platform. It includes descriptions and testing results of filters and encodings to help simplify access to satellite imagery. This technology was tested in a scenario that showed how OGC-based services, encodings, filters and applications can help coordinate humanitarian relief activities among nations and organizations." + "@value": "This document will discuss how OWS services can be ported to Web Services and highlight various issues/problems that have been discovered and need further discussion." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6718,35 +6742,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-038" + "@value": "03-014" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: Fit-for-Purpose Engineering Report" + "@value": "OGC Web Services SOAP Experiment Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-128r18", + "@id": "http://www.opengis.net/def/docs/16-041r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-11-16" + "@value": "2017-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Liping Di, Eugene G. Yu, Md Shahinoor Rahman, Ranjay Shrestha" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -6756,27 +6780,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://www.geopackage.org/spec131/index.html" + "@id": "https://docs.ogc.org/per/16-041r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-128r18" + "@value": "Testbed-12 WPS ISO Data Quality Service Profile Engineering Report" }, { "@language": "en", - "@value": "GeoPackage Encoding Standard" + "@value": "16-041r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." + "@value": "This Data Quality Engineering Report describes data quality handling requirements, challenges and solutions. One focus is on data quality in general that needs to be communicated from one service to another. In addition, it discusses WPS data quality solutions. The ultimate goal is for it to be nominated as a WPS ISO Data Quality Service Profile. ISO 19139 is used as the base to encode the data quality. WPS and workflows are used to streamline and standardize the process of data quality assurance and quality control. The main topics include: (1) generalized summary and description of the design and best practices for analyzing data quality of all feature data sources used in the Citizen Observatory WEB (COBWEB) project, (2) solutions and recommendations for enabling provenance of data quality transparent to end users when the data is processed through a WPS, (3) best practices and recommendations for designing and prototyping the WPS profile to support data quality service conformant to the NSG Metadata Framework, and (4) general solution for data quality fit for both raster-based imageries and vector-based features." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6787,35 +6811,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-128r18" + "@value": "16-041r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GeoPackage Encoding Standard" + "@value": "Testbed-12 WPS ISO Data Quality Service Profile Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-028r1", + "@id": "http://www.opengis.net/def/docs/17-084r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-17" + "@value": "2021-04-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Y. Coene, U. Voges, O. Barois" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -6825,27 +6849,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21628" + "@id": "https://docs.ogc.org/bp/17-084r1/17-084r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-028r1" + "@value": "17-084r1" }, { "@language": "en", - "@value": "GEOINT Structure Implementation Profile Schema Processing" + "@value": "EO Collection GeoJSON(-LD) Encoding" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document contains a description of the schema tailoring process for application schema development based on the U.S. National System for Geospatial-Intelligence (NSG) GEOINT Structure Implementation Profile (GSIP) as developed in conjuction with the Open Geospatial Consortium Interoperability Program initiative OWS-4." + "@value": "JavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. GeoJSON [NR2] is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. This OGC Best Practice describes a GeoJSON [NR2] and JSON-LD [NR13] encoding for Earth Observation (EO) metadata for collections (dataset series). This standard can be applied to encode metadata based on the OGC 11-035r1 [OR20] or ISO19139 [OR27], ISO19139-2 [OR28] specifications, or as an encoding of the Unified Metadata Model for Collections (UMM-C) conceptual model [OR2].\r\n\r\nThe GeoJSON encoding defined in this document is defined as a compaction1 through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF/XML [OR11] and RDF Turtle [OR12].\r\n\r\nThis document makes no assumptions as to the “service” interfaces through which the metadata are accessed and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful Architecture.\r\n\r\nGeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features.\r\n\r\nJSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR7] which allows validation of instances against these schemas." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6856,91 +6880,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-028r1" + "@value": "17-084r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GEOINT Structure Implementation Profile Schema Processing" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/notes", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/10-099r2" - }, - { - "@id": "http://www.opengis.net/def/docs/22-032r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-052" - }, - { - "@id": "http://www.opengis.net/def/docs/07-061" - }, - { - "@id": "http://www.opengis.net/def/docs/18-066r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-126r8" - }, - { - "@id": "http://www.opengis.net/def/docs/21-004" - }, - { - "@id": "http://www.opengis.net/def/docs/19-034r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-123r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-044" - }, - { - "@id": "http://www.opengis.net/def/docs/18-016r1" - }, - { - "@id": "http://www.opengis.net/def/docs/18-024r1" - }, - { - "@id": "http://www.opengis.net/def/docs/21-066r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-066r5" - }, - { - "@id": "http://www.opengis.net/def/docs/20-006" - }, - { - "@id": "http://www.opengis.net/def/docs/23-018r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-111" + "@value": "EO Collection GeoJSON(-LD) Encoding" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-033r9", + "@id": "http://www.opengis.net/def/docs/10-135", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-07-04" + "@value": "2011-03-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Vretanos" + "@value": "Alexandre Robin, Philippe Mérigot" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -6950,27 +6918,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=11266" + "@id": "https://portal.ogc.org/files/?artifact_id=40185" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GML simple features profile" + "@value": "Earth Observation Satellite Tasking Extension for SPS 2.0" }, { "@language": "en", - "@value": "05-033r9" + "@value": "10-135" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This profile defines a restricted but useful subset of XML-Schema and GML to lower the " + "@value": "The SPS 2.0 Earth Observation Satellite Tasking Extension Standard specifies extensions to the OGC Sensor Planning Service (SPS) 2.0 Interface Standard. The SPS configuration proposed in this extension is intended to support the programming process of Earth Observation (EO) sensor systems. This standard describes a consistent SPS configuration that can be supported by many satellite data providers, most of whom have existing facilities for the management of these programming requests. The resulting extended web service interface can be used for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or canceling such a request, and for requesting information on means of obtaining the data collected by the requested task." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -6981,35 +6949,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-033r9" + "@value": "10-135" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML simple features profile" + "@value": "OGC® Sensor Planning Service Interface Standard 2.0 Earth Observation Satellite Tasking ExtensionOGC® Sensor Planning Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-031", + "@id": "http://www.opengis.net/def/docs/14-100r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-02-08" + "@value": "2015-11-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sam Meek" + "@value": "Ben Domenico, Stefano Nativi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7019,27 +6987,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-031.html" + "@id": "https://docs.ogc.org/is/14-100r2/14-100r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-031" + "@value": "14-100r2" }, { "@language": "en", - "@value": "UML Modeling Best Practice Engineering Report" + "@value": "CF-netCDF 3.0 encoding using GML Coverage Application Schema" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Best Practice provides readers with guidance on how to use the Unified Modeling Language (UML) within the scope of OGC work. Recently there has been a move to a resource-based approach for OGC Application Programming Interface (API) definition through the OpenAPI Specification and away from the service-based approach specified in OGC Web Service (OWS) standards. Previously, the interface definitions were almost exclusively XML based, therefore models described using UML class diagrams and conceptual models in general simply mapped 1:1 to derive the XML schema. Using API resources has resulted in the possibility of deriving multiple target technologies from a single standard and therefore, UML model. An additional point of discussion within the OGC is the value added by conceptual modeling using UML. Models included in OGC Standards vary from diagrams only, to conceptual models and model fragments all the way through to Model Driven Architecture (MDA) where UML models are used to directly derive implementable artifacts such as schemas.\r\n\r\nUML has been the main modeling language of choice within the OGC, although up until now, there has been little guidance within the OGC on appropriate use of UML. These Best Practices do not seek to govern the use of UML within the OGC as it is recognized that UML is a flexible language that has applications beyond the current OGC doctrine. However, the practices seek to provide guidance to assist in adherence to the following principles:\r\n\r\n Correctness — Adherence to the Object Management Group (OMG) UML standard.\r\n Consistency — UML artifacts should be consistent across OGC Standards and with supporting standards such as those specified by ISO/TC 211.\r\n FAIRness — Findable, Accessible, Interoperable and Reusable models.\r\n Value — Any modeling done, UML or otherwise, should add value to the parent standard. That is, the modeling should do work for the community that is not done elsewhere.\r\nThe Practices are as follows:\r\n\r\n Practice 1: UML models should follow the OMG UML 2.5.1 Standard ratified in 2017.\r\n Practice 2: OGC Conceptual Models should be represented as UML Class diagrams.\r\n Practice 3: OGC Conceptual Models should be platform independent.\r\n Practice 4: OGC Conceptual Models should use concepts consistently across standards.\r\n Practice 5: OGC Standards should contain a UML model at least at the conceptual level of detail.\r\n Practice 6: UML models in OGC Standards should add value.\r\n Practice 7: UML models should describe structure in the engineering process.\r\n Practice 8: Modeling artifacts should be provided in full.\r\n Practice 9: UML models should at least be consistent with supporting text, but ideally normative.\r\n Practice 10: UML tooling should produce interoperable artifacts.\r\n Practice 11: UML can be used for modeling semantics, although there are other technologies that are more appropriate.\r\n Practice 12: OGC UML models should be machine readable (i.e. available in XMI format, in addition to the format of the UML Editor used to create the model)." + "@value": "The OGC CF-netCDF data model supports multi-dimensional gridded data and multidimensional multi-point data, representing space and time-varying phenomena. In particular, this extension standard is limited to multi-point, and regular and warped grids.\r\nThis standard specifies the CF-netCDF data model encoding using the OGC GML 3.2.1 coverage application schema, as well as CF-netCDF data exchange format and protocol encoding.\r\nThis standard specifies: (a) the CF-netCDF GML encoding to be used by OGC standards; (b) the CF-netCDF data format exchanged using OGC standards; (c) the Internet protocol characteristics to effectively exchange CF-netCDF data.\r\nAs per the GML 3.3. standard, GML 3.3 imports the 3.2 schema. The canonical location of the 3.2 all components schema document for 3.3 is\r\nhttp://schemas.opengis.net/gml/3.2.1/gml.xsd" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7050,35 +7018,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-031" + "@value": "14-100r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: UML Modeling Best Practice Engineering Report" + "@value": "OGC® CF-netCDF 3.0 encoding using GML Coverage Application Schema" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-035r2", + "@id": "http://www.opengis.net/def/docs/02-069", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-27" + "@value": "2002-08-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jens Fitzke, Rob Atkinson" + "@value": "Ron Lake" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7088,27 +7056,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=15529" + "@id": "https://portal.ogc.org/files/?artifact_id=11339" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-035r2" + "@value": "Geography Markup Language" }, { "@language": "en", - "@value": "Gazetteer Service - Application Profile of the Web Feature Service Implementation Specification" + "@value": "02-069" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines a Gazetteer Service profile of the OGC Web Feature Service Specification. The OGC Gazetteer Service allows a client to search and retrieve elements of a georeferenced vocabulary of well-known place-names." + "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7119,35 +7087,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-035r2" + "@value": "02-069" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Gazetteer Service - Application Profile of the Web Feature Service Implementation Specification" + "@value": "Geography Markup Language" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-140r2", + "@id": "http://www.opengis.net/def/docs/03-073r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-10-04" + "@value": "2003-10-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann, Stephan Meissl, Jinsongdi Yu" + "@value": "Roel Nicolai" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7157,27 +7125,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/10-140r2/10-140r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=11518" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile" + "@value": "03-073r1" }, { "@language": "en", - "@value": "10-140r2" + "@value": "Topic 2 - Spatial Referencing by Coordinates" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Web Coverage Service (WCS) Application Profile - Earth Observation (EO- WCS) defines a profile of WCS 2.0 [OGC 09-110r4] for use on Earth Observation data." + "@value": "Describes modelling requirements for spatial referencing by coordinates." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7188,30 +7156,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-140r2" + "@value": "03-073r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile" + "@value": "Topic 2 - Spatial Referencing by Coordinates" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-073r2", + "@id": "http://www.opengis.net/def/docs/20-021r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-02-09" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Debbie Wilson, Ian Painter " + "@value": "Aleksandar Balaban" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -7226,17 +7194,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46666" + "@id": "https://docs.ogc.org/per/20-021r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-073r2" + "@value": "20-021r2" }, { "@language": "en", - "@value": "OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0" + "@value": "OGC Testbed-16: Data Centric Security Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -7246,7 +7214,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The scope of this guidelines report is to provide:\r\n1.\tOverview of the OGC WFS 2.0 standard\r\n2.\tRecommendations for a minimum set of operations and behaviours that should be supported to ensure consistency across software implementations. \r\n3.\tGuidance for configuring the WFS 2.0 to retrieve AIXM 5.1 data \r\n4.\tSummary of potential improvements to WFS/FE 2.0, GML and AIXM 5.1 specifications to better support aeronautical use cases\r\n" + "@value": "The OGC Testbed-16 Data Centric Security Engineering Report (ER) continues the evaluation of a data-centric security (DCS) approach in a geospatial environment. In order to fully explore the potential of the DCS concept, this ER first specifies two advanced use case scenarios: Data Streaming and Offline Authorization for querying and consuming protected geospatial content. The ER then specifies the communication with a new architectural component called the Key Management Server (KMS) via an Application Programming Interface (API) created for this Testbed. The API was invoked to register keys used to encrypt data-centric protected content. Then clients called the same API to obtain those keys to perform the data verification/decryption.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7257,35 +7225,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-073r2" + "@value": "20-021r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0" + "@value": "OGC Testbed-16: Data Centric Security Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-095r2", + "@id": "http://www.opengis.net/def/docs/11-030r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-11-14" + "@value": "2012-01-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Kuan-Mei Chen, Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7295,27 +7263,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=23979" + "@id": "https://portal.ogc.org/files/?artifact_id=44146" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-095r2" + "@value": "11-030r1" }, { "@language": "en", - "@value": "Web Services Summaries" + "@value": "Open GeoSMS Standard - Core" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides brief and consistent summaries of several OGC Web Service interface specifications that serve data." + "@value": "The OpenGIS® Open GeoSMS standard defines an encoding for location enabling a text message to be communicated using a Short Messages System (SMS). " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7326,35 +7294,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-095r2" + "@value": "11-030r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Services Summaries" + "@value": "OGC®: Open GeoSMS Standard - Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-001", + "@id": "http://www.opengis.net/def/docs/15-012r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-03-21" + "@value": "2015-08-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7364,27 +7332,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=38476" + "@id": "https://portal.ogc.org/files/?artifact_id=63285" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-001" + "@value": "15-012r2" }, { "@language": "en", - "@value": "SWE Service Model Implementation Standard" + "@value": "GeoPackage Plugfest Discussion Paper" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard currently defines eight packages with data types for common use across OGC Sensor Web Enablement (SWE) services. Five of these packages define operation request and response types. The packages are: 1.) Contents – Defines data types that can be used in specific services that provide (access to) sensors; 2.) Notification – Defines the data types that support provision of metadata about the notification capabilities of a service as well as the definition and encoding of SWES events; 3.) Common - Defines data types common to other packages; 4.) Common Codes –Defines commonly used lists of codes with special semantics; 5.) DescribeSensor – Defines the request and response types of an operation used to retrieve metadata about a given sensor; 6.) UpdateSensorDescription –Defines the request and response types of an operation used to modify the description of a given sensor; 7.) InsertSensor – Defines the request and response types of an operation used to insert a new sensor instance at a service; 8.) DeleteSensor – Defines the request and response types of an operation used to remove a sensor from a service. These packages use data types specified in other standards. Those data types are normatively referenced herein, instead of being repeated in this standard." + "@value": "This OGC discussion paper presents the results of the GeoPackage Plugfest. In this\r\ninitiative, participants had the opportunity to evaluate the compliance and interoperability\r\nof software that produces and consumes GeoPackages containing tiled raster data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7395,35 +7363,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-001" + "@value": "15-012r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS® SWE Service Model Implementation Standard" + "@value": "OGC GeoPackage Plugfest Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-063r1", + "@id": "http://www.opengis.net/def/docs/16-011r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-06-02" + "@value": "2018-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joshua Lieberman" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7433,27 +7401,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1269" + "@id": "https://portal.ogc.org/files/16-011r4" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-063r1" + "@value": "16-011r4" }, { "@language": "en", - "@value": "Critical Infrastructure Collaborative Environment Architecture: Computational Viewpoint" + "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*RETIRED* The objective of this document is to provide a vendor-neutral interoperable framework that enables collaborating communities to rapidly and collaboratively publish, discover, integrate and use geospatial information concerned with the protection of critical infrastructure systems in a range of sectors. Specifically, this document specifies a Computational Architecture viewpoint for a Critical Infrastructure Collaborative Environment (CICE)." + "@value": "Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames. \r\nIn previous versions of the CDB standard, this CDB volume was Appendix K in CDB Version 3.2 as submitted to the OGC.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7464,30 +7432,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-063r1" + "@value": "16-011r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Critical Infrastructure Collaborative Environment Architecture: Computational Viewpoint" + "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-084r2", + "@id": "http://www.opengis.net/def/docs/12-128r17", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-01-14" + "@value": "2021-02-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Brackin, Pedro Gonçalves " + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -7502,17 +7470,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55183" + "@id": "https://docs.ogc.org/is/12-128r17/12-128r17.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-084r2" + "@value": "GeoPackage Encoding Standard" }, { "@language": "en", - "@value": "OWS Context Atom Encoding Standard" + "@value": "12-128r17" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -7522,7 +7490,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard describes the Atom encoding of the OWC Context conceptual model. The goal of this standard is to provide a definition of how to encode a context document, which can be extended to allow a context referencing a fully configured service set to be defined and consistently interpreted by clients.\r\n" + "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7533,35 +7501,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-084r2" + "@value": "12-128r17" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC OWS Context Atom Encoding Standard" + "@value": "OGC® GeoPackage Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-017r1", + "@id": "http://www.opengis.net/def/docs/10-003r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-10-12" + "@value": "2010-06-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Richard Martell" + "@value": "Louis Hecht, Jr., Raj Singh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7571,27 +7539,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7048" + "@id": "https://portal.ogc.org/files/?artifact_id=37223" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-017r1" + "@value": "Summary of the Architecture, Engineering, Construction, Owner Operator Phase 1 (AECOO-1) Joint Testbed" }, { "@language": "en", - "@value": "Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW" + "@value": "10-003r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Catalogue Services 2.0 specification (OGC 04-021) establishes a framework for implementing catalogue services that can meet the needs of stakeholders in a wide variety of application domains. This application profile is based on the CSW schemas for web-based catalogues and it complies with the requirements of clause 11 in OGC 04-021." + "@value": "The Architecture, Engineering, Construction, Owner Operator, Phase 1 (AECOO-1) Testbed developed and implemented methods to streamline communications between parties in the conceptual design phase to get an early understanding of the tradeoffs between construction cost and energy efficiency. To that end, the project developed the interoperability components required for these analyses in collaborative team settings. These were Information Delivery Manuals (IDMs) for quantity takeoffs and energy analysis business processes, and used these to define Model View Definitions (MVDs)—standards-based subsets of Industry Foundation Classes (IFCs). AECOO-1 was conducted in response the felt need that overall productivity loss and fragmentation in the capital facilities development industries is no longer tolerable. All stakeholders need to practice the best way they know, and practice profitably; software interoperability problems must not hold them back. Non-interoperable software and data is cause for loss of competition across the market." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7602,35 +7570,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-017r1" + "@value": "10-003r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW" + "@value": "Summary of the Architecture, Engineering, Construction, Owner Operator Phase 1 (AECOO-1) Joint Testbed" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-092r3", + "@id": "http://www.opengis.net/def/docs/21-004", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-04-05" + "@value": "2023-03-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ben Domenico" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7640,27 +7608,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=43734" + "@id": "https://portal.ogc.org/files/?artifact_id=98574" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-092r3" + "@value": "21-004" }, { "@language": "en", - "@value": "NetCDF Binary Encoding Extension Standard: NetCDF Classic and 64-bit Offset Format" + "@value": "Release Notes for OGC GeoPackage 1.3.1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines an OGC® Standard for encoding binary representations of space-time varying geo-referenced data. Specifically, this standard specifies the netCDF classic and 64-bit offset file binary encoding formats. This standard specifies a set of requirements that every netCDF classic or 64-bit offset binary encoding must fulfil." + "@value": "This document provides the set of revision notes for Geopackage 1.3.1 and does not modify that Standard.\r\n\r\nThis document provides the details of edits, deficiency corrections, and enhancements of the above-referenced Standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7671,35 +7639,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-092r3" + "@value": "21-004" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "NetCDF Binary Encoding Extension Standard: NetCDF Classic and 64-bit Offset Format" + "@value": "Release Notes for OGC GeoPackage 1.3.1" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-075", + "@id": "http://www.opengis.net/def/docs/18-067r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-05-06" + "@value": "2020-10-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andrew Lavender, Samantha Lavender " + "@value": "" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/ug" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7709,27 +7677,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/guides/21-075.html" + "@id": "https://docs.ogc.org/is/18-067r3/18-067r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Disaster Pilot: User Readiness Guide" + "@value": "18-067r3" }, { "@language": "en", - "@value": "21-075" + "@value": "OGC Symbology Conceptual Model: Core Part" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/ug" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Improving the ability of key disaster decision makers and responders to discover, manage, access, transform, share, and exploit location-based and Earth Observation data will enhance decision making and, hopefully, save lives. The OGC Disaster Pilot 2021 has developed a number of prototype capabilities to demonstrate solutions for providing consistent, and reliable information to enable real-time actions to be taken using multiple technologies working together through pre-agreed standards.\r\n\r\nThis User Guide describes how the solution works, how users can be part of it, and showcases what can be achieved if everyone is willing to work together and share data and knowledge to improve the information available to those responding to a disaster." + "@value": "This document presents the requirements for defining the Symbology Conceptual Core Model (SymCore), the conceptual basis to define symbology rules for the portrayal of geographical data. It is modular and extensible (one core model, many extensions), also encoding agnostic (one symbology model, many encodings). It contains a minimal set of abstract classes representing explicit extension points of the model." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7740,35 +7708,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-075" + "@value": "18-067r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Disaster Pilot: User Readiness Guide" + "@value": "OGC Symbology Conceptual Model: Core Part" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-112r2", + "@id": "http://www.opengis.net/def/docs/01-029", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-02-23" + "@value": "2001-02-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Ron Lake" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7778,27 +7746,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=72714" + "@id": "https://portal.ogc.org/files/?artifact_id=1034" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Volume 3: OGC CDB Terms and Definitions" + "@value": "Geography Markup Language" }, { "@language": "en", - "@value": "15-112r2" + "@value": "01-029" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice." + "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7809,35 +7777,66 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-112r2" + "@value": "01-029" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 3: OGC CDB Terms and Definitions" + "@value": "Geography Markup Language" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-005r5", + "@id": "http://www.opengis.net/def/doc-type/rfc/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Request for Comment" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Request for Comment" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/03-081r2" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Request for Comment" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/00-106", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-03-09" + "@value": "2000-04-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker" + "@value": "Cliff Kottman, Charles Roswell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7847,27 +7846,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/14-005r5/14-005r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=7198" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-005r5" + "@value": "00-106" }, { "@language": "en", - "@value": "OGC® IndoorGML - with Corrigendum" + "@value": "Topic 06 - The Coverage Type" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes." + "@value": "Incomplete. This document normatively references parts of the previous version of AS Topic 6, document 00-106. Need to be updated to include Roswell Change Proposal (01-011), which includes 19123 and retains material from Topic 6, v6." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7878,35 +7877,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-005r5" + "@value": "00-106" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® IndoorGML - with Corrigendum" + "@value": "Topic 6 - The Coverage Type" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-083r4", + "@id": "http://www.opengis.net/def/docs/09-110r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-04-15" + "@value": "2012-07-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Adrian Custer" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7916,27 +7915,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=71648" + "@id": "https://portal.ogc.org/files/?artifact_id=48428" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-083r4" + "@value": "09-110r4" }, { "@language": "en", - "@value": "GeoAPI 3.0 Implementation Standard with corrigendum" + "@value": "WCS 2.0 Interface Standard- Core: Corrigendum " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be used for the manipulation of geographic information structured following the specifications adopted by the Technical Committee211 of the International Organization for Standardization (ISO) and by the Open Geospatial Consortium (OGC). This standard standardizes the informatics contract between the client code which manipulates normalized data structures of geographic information based on the published API and the library code able both to instantiate and operate on these data structures according to the rules required by the published API and by the ISO and OGC standards." + "@value": "This document specifies how a Web Coverage Service (WCS) offers multi-dimensional cov-erage data for access over the Internet. This document specifies a core set of requirements that a WCS implementation must fulfil. WCS extension standards add further functionality to this core; some of these are required in addition to the core to obtain a complete implementa-tion. This document indicates which extensions, at a minimum, need to be considered in ad-dition to this core to allow for a complete WCS implementation.\r\nThis core does not prescribe support for any particular coverage encoding format. This also holds for GML as a coverage delivery format: while GML constitutes the canonical format for the definition of WCS, it is not required by this core that a concrete instance of a WCS service implements the GML coverage format. WCS extensions specifying use of data encod-ing formats in the context of WCS are designed in a way that the GML coverage information contents specified in this core is consistent with the contents of an encoded coverage.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -7947,35 +7946,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-083r4" + "@value": "09-110r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GeoAPI 3.0 Implementation Standard with corrigendum" + "@value": "OGC® WCS 2.0 Interface Standard- Core: Corrigendum " } ] }, { - "@id": "http://www.opengis.net/def/docs/14-106", + "@id": "http://www.opengis.net/def/docs/17-042", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-01-30" + "@value": "2018-01-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed, Jennifer Harne" + "@value": "Sara Saeedi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -7985,27 +7984,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/14-106/14-106.html" + "@id": "https://docs.ogc.org/per/17-042.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Unified Geo-data Reference Model for Law Enforcement and Public Safety" + "@value": "17-042" }, { "@language": "en", - "@value": "14-106" + "@value": "Testbed-13: CDB Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides an overview of the Unified Geo-data Reference Model for Law Enforcement and Public Safety (Unified Model). The Unified Model was originally developed by the GIS Center for Security (GIS CS), Abu Dhabi Police. The GIS CS was initiated based on a UAE Ministry of Interior issued decree to establish GIS CS with the core mission: “To geo-enable police services and applications using International standards and best practices.” In 2010, the GIS SC initiated a program to develop a Standardized GIS Environment (SGA). Part of this effort was to define and implement a standard data model for sharing Law Enforcement and Public Safety data." + "@value": "This Engineering Report (ER) summarizes the CDB sub-thread work in Testbed 13. The document is structured in three phases and includes a feasibility study; the implementation of data models and schemas mapping that are based on the feasibility study results; and a set of OGC web services that implement the CDB in the form of WFS and WCS (Web Coverage Service) instances.\r\n\r\nThis Engineering Report describes:\r\n\r\nThe conceptual model of an OGC CDB 1.0 datastore as a UML (Unified Modeling Language) diagram to show different datasets (the 3D models, vector features and coverages) structure;\r\n\r\nHow to process and use a NAS-based Profile as a CDB feature/attribute data model or a GML-SF0 application schema;\r\n\r\nHow to access, navigate and visualize a CDB dataset using OGC web services (such as WFS and WCS).\r\n\r\nThis work provides insights into:\r\n\r\nThe in-depth study of the OGC CDB 1.0 feature data dictionary and attribution schema;\r\n\r\nThe requirements and constraints for extending the CDB feature data dictionary (FDD) and attribute schemas;\r\n\r\nThe development and prototyping of the WFS and WCS access to the CDB datastore for a NAS based urban military scenario." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8016,35 +8015,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-106" + "@value": "17-042" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Unified Geo-data Reference Model for Law Enforcement and Public Safety" + "@value": "OGC Testbed-13: CDB Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-032r3", + "@id": "http://www.opengis.net/def/docs/12-040", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-20" + "@value": "2014-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Boyan Brodaric" + "@value": "Peter Baumann, Jinsongdi Yu" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -8054,27 +8053,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/19-013/19-013.html" + "@id": "https://portal.ogc.org/files/?artifact_id=54503" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC WaterML 2: Part 4 - GroundWaterML 2 (GWML2)" + "@value": "Web Coverage Service Interface Standard - Range Subsetting Extension" }, { "@language": "en", - "@value": "16-032r3" + "@value": "12-040" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard describes a conceptual and logical model for the exchange of groundwater data, as well as a GML/XML encoding with examples." + "@value": "This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request which allow extraction of specific fields, according to the range type specification, from the range set of a coverage during server-side processing of a coverage in a GetCover-age request." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8085,35 +8084,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-032r3" + "@value": "12-040" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC WaterML 2: Part 4 - GroundWaterML 2 (GWML2)" + "@value": "OGC® Web Coverage Service Interface Standard - Range Subsetting Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-011r1", + "@id": "http://www.opengis.net/def/docs/19-024r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-05-04" + "@value": "2019-12-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Schut" + "@value": "Hector Rodriguez" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -8123,27 +8122,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=5859" + "@id": "https://docs.ogc.org/per/19-024r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geolinking Service" + "@value": "OGC Testbed-15: Federated Clouds Security Engineering Report" }, { "@language": "en", - "@value": "04-011r1" + "@value": "19-024r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A Geolinking Service takes attribute data which refers to spatial features, and joins it to a geospatial dataset, so that it can be mapped by a WMS or used in a GIS. When a Geolinking Service uses data from a GDAS, and serves as a front end to a WMS, it enables real-time mapping of data stored in non-spatial databases." + "@value": "This OGC Testbed-15 Engineering Report (ER) documents the concept for different types of federation through the lens of security. The primary focus of the work documented in this ER is on analyzing how federated membership, resource and access policy management can be provided within a security environment, while also providing portability and interoperability to all stakeholders.\r\n\r\nIn the Testbed, a practical approach for providing this functionality was exercised and documented for two administrative domains: One based on a centralized entity (Federation Manager) and the other showcasing a distributed architecture." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8154,35 +8153,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-011r1" + "@value": "19-024r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geolinking Service" + "@value": "OGC Testbed-15: Federated Clouds Security Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-004r5", + "@id": "http://www.opengis.net/def/docs/20-032", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2020-10-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Chris Little, Peng Yue, Steve Olson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -8192,27 +8191,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/16-004r5.html" + "@id": "https://docs.ogc.org/per/20-032.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-004r5" + "@value": "20-032" }, { "@language": "en", - "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models (Best Practice)" + "@value": "OGC API - Environmental Data Retrieval Sprint Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This CDB volume provides all of the information required to store Radar Cross Section (RCS) data within a conformant CDB data store.\r\n\r\n" + "@value": "The subject of this Engineering Report (ER) is a development Sprint that was held from March 18-20, 2020 to advance the Open Geospatial Consortium (OGC) Environmental Data Retrieval (EDR) Application Programming Interface (API) candidate standard. Due to the widespread of the virus, the Sprint was held virtually by using GoToMeeting teleconferencing facilities of OGC, email and GitHub." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8223,35 +8222,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-004r5" + "@value": "20-032" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models (Best Practice)" + "@value": "OGC API - Environmental Data Retrieval Sprint Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-093", + "@id": "http://www.opengis.net/def/docs/06-045r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-02-05" + "@value": "2006-07-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Eric LaMar" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -8261,27 +8260,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51784" + "@id": "https://portal.ogc.org/files/?artifact_id=14698" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-093" + "@value": "06-045r1" }, { "@language": "en", - "@value": "OWS-9: UML-to-GML-Application-Schema (UGAS) Conversion Engineering Report" + "@value": "WMS - Proposed Animation Service Extension" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The main scope of the schema automation activities in the OWS-9 initiative was twofold:\r\n•\tSupport for the SWE Common 2.0 XML Schema encoding rule\r\n•\tDevelopment of and support for an encoding rule for JSON instance data\r\nIn both cases the scope includes implementation of the encoding rules in ShapeChange.\r\nIn addition, an initial analysis of the possibilities for generating SWE Common 2.0 record descriptions from schemas in UML has been conducted and the results are described in this document.\r\nThe approach and results to both work items are described and discussed in this engineering report. This Engineering Report has been prepared as part of the OGC Web Services Phase 9 (OWS-9) initiative.\r\n" + "@value": "This document explains how the Web Map Server (WMS 1.0 [1] & 1.1 [2,3]) specification can be extended to allow map animations that move in space over time. It should be read in conjunction with the latest version WMS specification. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8292,35 +8291,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-093" + "@value": "06-045r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-9: UML-to-GML-Application-Schema (UGAS) Conversion Engineering Report" + "@value": "WMS - Proposed Animation Service Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-131r1", + "@id": "http://www.opengis.net/def/docs/07-074", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-08-18" + "@value": "2008-09-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Debbie Wilson" + "@value": "Marwa Mabrouk" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -8330,27 +8329,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40502" + "@id": "https://portal.ogc.org/files/?artifact_id=22122" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-131r1" + "@value": "Location Service (OpenLS) Implementation Specification: Core Services" }, { "@language": "en", - "@value": "OWS-7 Aviation - AIXM Assessment Report" + "@value": "07-074" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report shall focus on evaluating the ability to: \r\n\r\n- Serve, filter and update AIXM 5.1 data via the OGC WFS-T 2.0 interface \r\n- Recommend guidelines or cross-walks for interpreting the new AIXM 5.1 schedules in conjunction with the Timeslice model in a web services environment" + "@value": "This OpenGIS Interface Standard defines OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8361,35 +8360,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-131r1" + "@value": "07-074" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-7 Aviation - AIXM Assessment Report" + "@value": "OpenGIS Location Service (OpenLS) Implementation Specification: Core Services" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-038", + "@id": "http://www.opengis.net/def/docs/21-019", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-06-06" + "@value": "2022-01-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Nicolas Lesage, Marie-Lise Vautier" + "@value": "Aleksandar Balaban" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -8399,27 +8398,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20596" + "@id": "https://docs.ogc.org/per/21-019.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W" + "@value": "OGC Testbed-17: Attracting Developers: Lowering the entry barrier for implementing OGC Web APIs" }, { "@language": "en", - "@value": "07-038" + "@value": "21-019" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document extends the ebRIM application profile of CS-W for the cataloguing of ISO 19115 and ISO 19119 compliant metadata." + "@value": "This OGC Testbed 17 Engineering Report (ER) documents the work completed in the “Attracting Developers: Lowering the entry hurdle for OGC Web API experiments” task.\r\n\r\nOGC Web API Standards are being developed to make it easy to provide geospatial data over the web. These standards provide a certain level of formality to ensure high levels of interoperability. They rigorously define requirements and rules to reduce room for error during interpretation. This rigor sometimes makes the standard documents difficult to read and hence implement. Rather than direct examination of a standard, the majority of developers often prefer to start with implementation guidelines, sample code, and best practice documentation and then refer to the standards document for guidance and clarity.\r\n\r\nThe Testbed-17 (TB-17) API task served as a foundation for further development and exploration and delivers knowledge necessary for agile development, deployment, and executing OGC Standards-based applications following a “How-To” philosophy with hands-on experiments, examples, and instructions.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8430,35 +8429,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-038" + "@value": "21-019" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W" + "@value": "OGC Testbed-17: Attracting Developers: Lowering the entry barrier for implementing OGC Web APIs" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-072", + "@id": "http://www.opengis.net/def/docs/05-027r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-03-28" + "@value": "2005-04-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Charles Heazel" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -8468,27 +8467,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/19-072/19-072.html" + "@id": "https://portal.ogc.org/files/?artifact_id=10048" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC API - Common - Part 1: Core" + "@value": "Recommended XML/GML 3.1.1 encoding of image CRS definitions" }, { "@language": "en", - "@value": "19-072" + "@value": "05-027r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC has extended its suite of Standards to include Resource Oriented Architectures and Web APIs. In the course of developing these Standards, some practices proved to be common across multiple OGC Web API Standards. These common practices are documented in the OGC API — Common Standard. The OGC API - Common Standard is a multi-part standard that specifies reusable building-blocks that can be used in the construction of OGC API Standards. This document presents Part 1, the Core, of the OGC API – Common Standard. Standards developers will use these building-blocks in the construction of other OGC Standards that relate to Web APIs. The result is a modular suite of coherent API standards which can be adapted by a system designer for the unique requirements of their system.\r\n\r\nThe purpose of the OGC API — Common — Part 1: Core Standard (API-Core) is to define those fundamental building blocks and requirements which are applicable to all OGC Web API Standards." + "@value": "This document recommends standard XML encodings of data defining monoscopic image coordinate reference systems. The scope of this encoding now includes unrectified and georectified images. The recommended CRSs for georectified images are recommended for multiple georectified images that are ready to be mosaicked together.\r\n\r\nThese recommended encodings are based on GML 3.1.1 and use XML Schemas. These image CRS definitions will often be referenced in data transferred between client and server software that implements various standardised interfaces. This specified definition data encoding is expected to be used by multiple OGC Implementation Specifications. That is, each of these specifications is expected to use a subset and/or superset of this recommended definition data.\r\n\r\nThe position or location of a point can be described using coordinates. Such coordinates are unambiguous only when the coordinate reference system on which those coordinates are based is fully defined. Each position is described by a set of coordinates based on a specified coordinate reference system. Coordinates are often used in datasets in which all coordinates belong to the same coordinate reference system. This paper specifies XML encoding of data defining image coordinate reference systems.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8499,35 +8498,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-072" + "@value": "05-027r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Common - Part 1: Core" + "@value": "Recommended XML/GML 3.1.1 encoding of image CRS definitions" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-114r1", + "@id": "http://www.opengis.net/def/docs/17-079r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-12-30" + "@value": "2019-01-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Taylor " + "@value": "Steve Liang, Tania Khalafbeigi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -8537,27 +8536,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=61224" + "@id": "https://docs.ogc.org/is/17-079r1/17-079r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-114r1" + "@value": "17-079r1" }, { "@language": "en", - "@value": "WaterML2.0 part 2 – rating tables, gauging observations and cross-sections: Interoperability Experiment Results" + "@value": "SensorThings API Part 2 – Tasking Core" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Part 1 of WaterML2.0 covers exchange of hydrological time-series data, the observational processes used to generate them, and information related to the monitoring points (stations/sites) where time-series data are typically collected. WaterML2.0 Part 2, is a candidate standard that defines how to exchange rating tables, gauging observations and cross-sections in an interoperable manner. \r\nThis engineering report outlines the design and results of an OGC Interoperability Experiment (IE) that implemented and tested the current WaterML2.0 part 2 information model. The OGC IE experiment ran was conducted from November 2013 to August 2014. The use case for the IE involved exchange of data in three scenarios in Australia, US and the UK. \r\nThis report describes the software requirements, design, deployments and challenges faced by the experiment. The results were used to improve the WaterML2.0 part 2 information model and provided the basis for the formation of an OGC Standards Working Group (SWG) in August 2014. This SWG is responsible for formalization of the candidate OGC standard, for submission in 2015. \r\n" + "@value": "The OGC SensorThings API [OGC 15-078r6] provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the Web. At a high level, the OGC SensorThings API provides two main functions and each function is handled by the Sensing part or the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. The Tasking part provides a standard way for parameterizing - also called tasking - of taskable IoT devices, such as individual sensors and actuators, composite consumer / commercial / industrial / smart cities in-situ platforms, mobile and wearable devices, or even unmanned systems platforms such as drones, satellites, connected and autonomous vehicles, etc. This document specifies core of the SensorThings Tasking part." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8568,30 +8567,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-114r1" + "@value": "17-079r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "WaterML2.0 part 2 – rating tables, gauging observations and cross-sections: Interoperability Experiment Results" + "@value": "OGC SensorThings API Part 2 – Tasking Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-017", + "@id": "http://www.opengis.net/def/docs/18-057", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-04-28" + "@value": "2019-02-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Roger Brackin" + "@value": "Jérôme Gasperi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -8606,17 +8605,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=57334" + "@id": "https://docs.ogc.org/per/18-057.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 10 OWS Context in NIEM Engineering Report" + "@value": "18-057" }, { "@language": "en", - "@value": "14-017" + "@value": "OGC Testbed-14: Authorisation, Authentication, & Billing Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -8626,7 +8625,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report was prepared as a deliverable for OGC Testbed 10, an initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Open Mobility thread within the testbed.\r\nThe Engineering Report describes and evaluates options for integrating OWS Context documents in requests for information based on the National Information Exchange Model (NIEM).\r\n" + "@value": "In the context of a generic Earth Observation Exploitation Platform ecosystem, populated by Thematic Exploitation Platforms (TEPs) and Mission Exploitation Platforms (MEPs), which make use of cloud computing resources for Earth Observation data processing, the European Space Agency (ESA) has established two fundamental building blocks within a TEP, with different functions, the Application Deployment and Execution Service (ADES) and the Execution Management Service (EMS). Users interact with a TEP using a Web Client and the TEP contains an EMS and an ADES. The EMS includes most of the control logic, required for deploying and executing applications in different MEPs and TEPs while the ADES instead is responsible for the single application deployment and execution on a specific platform (i.e. TEP and/or MEP).\r\n\r\nThe D009 - ADES and EMS Results and Best Practices Engineering Report describes how the two services should be engineered in the Exploitation Platform context.\r\n\r\nThis Engineering Report (ER) describes the work performed by the Participants in the Exploitation Platforms Earth Observation Clouds (EOC) Thread of OGC Testbed-14 concerning the interfaces proposed for the Authentication, Authorization, Billing and Quoting topics associated to the EMS and the ADES components." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8637,35 +8636,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-017" + "@value": "18-057" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 10 OWS Context in NIEM Engineering Report" + "@value": "OGC Testbed-14: Authorisation, Authentication, & Billing Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-141r2", + "@id": "http://www.opengis.net/def/docs/08-002", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-15" + "@value": "2008-04-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Daniele Marchionni" + "@value": "Peter Rushforth" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -8675,27 +8674,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=22114" + "@id": "https://portal.ogc.org/files/?artifact_id=26610" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-141r2" + "@value": "CGDI WFS and GML Best Practices" }, { "@language": "en", - "@value": "Ordering Services for Earth Observation Products" + "@value": "08-002" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This best practices document describes a profile to order Earth Observation data products. This document expands on the work presented in Best Practices for Earth Observation Products OGC-05-057r4, separating the order services from the catalogue services which are now presented in 06-079. The final goal being to agree to a coherent set of interfaces for ordering of EO products to support access to data from heterogeneous systems dealing with derived data products from satellite based measurements of the earth's surface and environment. " + "@value": "This document gives guidelines and recommendations for administrators, users and implementers of Web Feature Services serving Geography Markup Language encoded response documents. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8706,35 +8705,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-141r2" + "@value": "08-002" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Ordering Services for Earth Observation Products" + "@value": "OGC® Canadian Geospatial Data Infrastructure WFS and GML Best Practices" } ] }, { - "@id": "http://www.opengis.net/def/docs/00-116", + "@id": "http://www.opengis.net/def/docs/22-050r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2000-04-24" + "@value": "2023-09-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman, Arliss Whiteside" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -8744,27 +8743,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7200" + "@id": "https://docs.ogc.org/is/22-050r1/22-050r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "00-116" + "@value": "OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 JSON Profile v1.0" }, { "@language": "en", - "@value": "Topic 16 - Image Coordinate Transformation Services" + "@value": "22-050r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Covers image coordinate conversion services." + "@value": "The OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 JSON Profile v1.0 (GeoXACML 3.0 JSON Profile) Standard defines an extension to the JSON Profile of XACML 3.0 Version 1.1 for supporting GeoXACML Authorization Decision Requests and Authorization Decision encoded in JSON. This ensures an easy uptake in environments where JSON is the preferred encoding.\r\n\r\nFor supporting Geometry as defined by the GeoXACML 3.0 Core conformance class, this profile extends the Attribute DataType definition from JSON Profile of XACML 3.0 Version 1.1 with the geometry data-type urn:ogc:def:geoxacml:3.0:data-type:geometry\r\n\r\nThe GeoXACML 3.0 JSON Profile Standard supports the Attribute value to use Well-Known-Text (WKT), Well-Known-Binary (WKB) hex-encoding or GeoJSON as an encoding alternative for the geometry data-type defined in GeoXACML 3.0.\r\n\r\nTo support the use of the GeoXACML 3.0 specific attributes SRID, Precision, Encoding, and AllowTransformation, this profile extends the default JSON schema definition from JSON Profile of XACML 3.0 Version 1.1 accordingly." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8775,35 +8774,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "00-116" + "@value": "22-050r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 16 - Image Coordinate Transformation Services" + "@value": "OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 JSON Profile v1.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-000", + "@id": "http://www.opengis.net/def/docs/20-054r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-09-08" + "@value": "2021-01-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "C. Perey, J.G. Morley, J. Lieberman, R. Smith, M. Salazar, C. Smyth" + "@value": "Kyoung-Sook Kim, Jiyeong Lee" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/ug" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -8813,27 +8812,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/guides/22-000.html" + "@id": "https://docs.ogc.org/dp/20-054r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-000" + "@value": "An Extension Model to attach Points of Interest into IndoorGML" }, { "@language": "en", - "@value": "OGC GeoPose Reviewers Guide" + "@value": "20-054r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/ug" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The GeoPose Reviewers Guide is a public resource structured to provide quick answers to questions which a reviewer may have about the OGC GeoPose specification. This OGC document is provided to support professionals who need to understand OGC GeoPose and/or are reviewing the GeoPose draft standard but do not wish to implement it.\r\n\r\nGeoPose 1.0 is an OGC Implementation Standard for exchanging the position and orientation (Poses) of real or virtual geometric objects within reference frames anchored to the Earth’s surface (Geo) or within other astronomical coordinate systems. The standard specifies two Basic forms with no configuration options for common use cases, an Advanced form with more flexibility for more complex applications, and five composite GeoPose structures that support time series plus chain and graph structures." + "@value": "The scope of this discussion paper is to investigate types of Point of Interest (POI) data in indoor space and propose a conceptual model to harmonize the POI information with the IndoorGML core and navigation modules. In particular, this document focuses on the management of spatial (and non-spatial) history of indoor POI features. The paper covers the following scope:\r\n\r\nPoints of Interest Feature Types;\r\n\r\nA Conceptual model to extend IndoorGML schema for indoor POI; and\r\n\r\nUse cases in home navigation and hospital facility management." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8844,35 +8843,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-000" + "@value": "20-054r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoPose Reviewers Guide" + "@value": "An Extension Model to attach Points of Interest into IndoorGML" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-163r2", + "@id": "http://www.opengis.net/def/docs/09-072", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-04-02" + "@value": "2009-08-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Frédéric Houbie, Fabian Skivée, Simon Jirka" + "@value": "James Ressler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -8882,27 +8881,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=37944" + "@id": "https://portal.ogc.org/files/?artifact_id=34146" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-163r2" + "@value": "OWS-6 CITE TEAM Engine Engineering Report" }, { "@language": "en", - "@value": "sensorML Extension Package for ebRIM Application Profile" + "@value": "09-072" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the mapping of description of sensors using SensorML specification 1.0 [OGC 07-000] to an ebRIM structure within an OGCTM Catalogue 2.0.2 (Corrigendum 2 Release) [OGC 07-006r1] implementing the CSW-ebRIM Registry Service – part 1: ebRIM profile of CSW [OGC 07-110r4].\r\nIn addition this document contains the definition of a SensorML profile for Discovery which defines a minimum set of metadata to be provided within SensorML documents as well as the structure this data shall possess. This profile is based on the OGC OWS- 6 SensorML Profile for Discovery Engineering Report [OGC 09-033].\r\nIt defines the way sensors metadata are organized and implemented in the Catalogue for discovery, retrieval and management." + "@value": "This document summarizes the work done on the TEAM compliance test engine and DGIWG Profile compliance test by Northrop Grumman for the CITE thread of OWS-6 in 2008-2009." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8913,30 +8912,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-163r2" + "@value": "09-072" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "sensorML Extension Package for ebRIM Application Profile" + "@value": "OWS-6 CITE TEAM Engine Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-094r1", + "@id": "http://www.opengis.net/def/docs/08-085r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-01-04" + "@value": "2016-04-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Alexandre Robin" + "@value": "Lucio Colaiacomo, Joan Masó, Emmanuel Devys " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -8951,17 +8950,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41157" + "@id": "https://docs.ogc.org/is/08-085r5/08-085r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "SWE Common Data Model Encoding Standard" + "@value": "08-085r5" }, { "@language": "en", - "@value": "08-094r1" + "@value": "GML in JPEG 2000 (GMLJP2) Encoding StandardPart 1: Core" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -8971,7 +8970,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard defines low level data models for exchanging sensor related data between nodes of the OGC® Sensor Web Enablement (SWE) framework. These models allow applications and/or servers to structure, encode and transmit sensor datasets in a self describing and semantically enabled way." + "@value": "This standard applies to the encoding and decoding of JPEG 2000 images that contain GML for use with geographic imagery.\r\nThis document specifies the use of the Geography Markup Language (GML) within the XML boxes of the JPEG 2000 data format and provides an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations. The document also specifies the encoding and packaging rules for GML use in JPEG 2000.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -8982,35 +8981,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-094r1" + "@value": "08-085r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® SWE Common Data Model Encoding Standard" + "@value": "OGC GML in JPEG 2000 (GMLJP2) Encoding StandardPart 1: Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-020r2", + "@id": "http://www.opengis.net/def/docs/14-055r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-01-29" + "@value": "2017-04-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Guy Schumann, Albert Kettner, Nils Hempelmann" + "@value": "Pedro Gonçalves, Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -9020,27 +9019,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-020r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=68826" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Engineering report for OGC Climate Resilience Pilot" + "@value": "OWS Context GeoJSON Encoding Standard" }, { "@language": "en", - "@value": "23-020r2" + "@value": "14-055r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Climate Resilience Pilot marked the beginning of a series of enduring climate initiatives with the primary goal of evaluating the value chain encompassing raw data to climate information processes within Climate Resilience Information Systems. This includes the transformation of geospatial data into meaningful knowledge for various stakeholders, including decision-makers, scientists, policymakers, data providers, software developers, service providers, and emergency managers. The results of the OGC Climate Resilience Pilot support the location community to develop more powerful visualization and communication tools to accurately address ongoing climate threats such as heat, drought, floods, and wild-fires as well as supporting governments in meeting commitments for their climate strategies. This will be accomplished through evolving geospatial data, technologies, and other capabilities into valuable information for decision-makers, scientists, policymakers, data providers, software developers, and service providers so they can make valuable, informed decisions to improve climate action. One of the most significant challenges so far has been converting the outputs of global and regional climate models into specific impacts and risks at the local level. The climate science community has adopted standards and there are now numerous climate resilience information systems available online, allowing experts to exchange and compare data effectively. However, professionals outside the weather and climate domain, such as planners and GIS analysts working for agencies dealing with climate change impacts, have limited familiarity with and capacity to utilize climate data.\r\n\r\n" + "@value": "This standard describes the GeoJSON encoding of the OGC Web Services (OWS) Context conceptual model. This standard defines how to encode an OWS context document that 1.) can be extended to allow a context referencing a fully configured service set, and 2.) can be defined and consistently interpreted by clients.\r\nThe OWS Context Document standard (OWS Context) was created to allow a set of configured information resources to be passed between applications primarily as a collection of services (but also potentially in-line content). The objective is to support use cases such as the distribution of search results, the exchange of a set of resources in a Common Operating Picture (COP), or delivery of a set of configured processing services to allow the processing to be reproduced on different processing nodes.\r\nThe goal for OWS Context is to replace previous OGC standards and best practices that provide similar capability. Web Map Context (WMC) has been reasonably successful but is limited to working with only Web Map Service (WMS) instances. Other work on the Location Organizer Folder1 (LOF) was also taken into consideration. The concept of OWS Context and the first prototype document was produced as part of OWS Testbed 7 and documented in [OGC10-035r1], Information Sharing Engineering Report.\r\nA principal goal of the OWS Context SWG was to develop encodings that would appeal for use in mass market applications yet also provide facilities for more advanced uses. OWS-7 originally considered the application of existing encoding standards for OWS Context. The OGC Standards Working Group (SWG) has concluded that this standard can have multiple encoding formats and that each encoding format will be described in a separate OGC Extension to the Core model.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9051,35 +9050,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-020r2" + "@value": "14-055r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Engineering report for OGC Climate Resilience Pilot" + "@value": "OGC OWS Context GeoJSON Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-041r3", + "@id": "http://www.opengis.net/def/docs/07-110r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-24" + "@value": "2009-02-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Bastian Baranski" + "@value": "Richard Martell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -9089,27 +9088,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34977" + "@id": "https://portal.ogc.org/files/?artifact_id=31137" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-041r3" + "@value": "07-110r4" }, { "@language": "en", - "@value": "OWS-6 WPS Grid Processing Profile Engineering Report" + "@value": "CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report describes and reviews the Grid Computing related activity completed during the OGC OWS-6 Interoperability testbed. The document describes the WPS processes deployed in the different demonstration scenarios and offers recommendations to the OGC community as to how to better harmonize the standards work of the OGC with Grid Computing platforms and related concepts and technologies." + "@value": "This profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0.2 specification; it qualifies as a ‘Class 2’ profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9120,35 +9119,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-041r3" + "@value": "07-110r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 WPS Grid Processing Profile Engineering Report" + "@value": "CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-053r2", + "@id": "http://www.opengis.net/def/docs/07-024", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-01-31" + "@value": "2007-07-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Patrick Cozzi, Sean Lilley, Gabby Getz" + "@value": "Thomas Uslander (Ed.)" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -9158,27 +9157,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/18-053r2/18-053r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=20300" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "3D Tiles Specification 1.0" + "@value": "07-024" }, { "@language": "en", - "@value": "18-053r2" + "@value": "Reference Model for the ORCHESTRA Architecture" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "3D Tiles is designed for streaming and rendering massive 3D geospatial content such as Photogrammetry, 3D Buildings, BIM/CAD, Instanced Features, and Point Clouds. It defines a hierarchical data structure and a set of tile formats which deliver renderable content. 3D Tiles does not define explicit rules for visualization of the content; a client may visualize 3D Tiles data however it sees fit.\r\n\r\nA 3D Tiles data set, called a tileset, contains 3D data organized into a spatial data structure. The primary format for delivering the 3D data is glTF 2.0. Additional formats for geospatial tile data are also specified in this document. These tile formats include Batched 3D Models, Instanced 3D Models, Point Clouds and Composite tiles.\r\n\r\nThis document specifies the following elements of a tileset:\r\n\r\nThe core data structures for tilesets\r\nTile formats for delivering 3D data\r\nAn implicit representation of tilesets that are organized in quadtrees or octrees\r\nMetadata that may be associated to elements of a tileset on different levels of granularity\r\nDeclarative styling which may be applied to tilesets for their visualization\r\nThe 3D Tiles specification for tilesets, associated tile formats, metadata, and the associated styling specification are open formats that are not dependent on any vendor-specific solution, technology, or products.\r\n\r\nThe majority of the content in this OGC document is a direct copy of the content contained at the 1.1 tag of the 3d-tiles repo. No normative changes have been made to the content. This OGC document does contain content not contained in the 1.1 tag of the 3d-tiles repo.\r\n\r\nCesium has published the 3D Tiles 1.1 Reference Card as an approachable and concise guide to learning about the main concepts in 3D Tiles, intended to jumpstart developers in adopting 3D Tiles." + "@value": "This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It contains a platform-neutral specification of the ORCHESTRA Architecture and a specification framework for the design of ORCHESTRA-compliant service networks across all viewpoints." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9189,35 +9188,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-053r2" + "@value": "07-024" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC 3D Tiles Specification 1.0" + "@value": "Reference Model for the ORCHESTRA Architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-111", + "@id": "http://www.opengis.net/def/docs/14-004", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-19" + "@value": "2014-04-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "GEOWOW Consortium" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pc" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -9227,27 +9226,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=16571" + "@id": "https://portal.ogc.org/files/?artifact_id=57327" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-111" + "@value": "14-004" }, { "@language": "en", - "@value": "GML 3.1.1 grid CRSs Profile Corrigendum" + "@value": "Sensor Observation Service 2.0 Hydrology Profile" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pc" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a corrigendum for OGC Document 05-096r1, titled GML 3.1.1 grid CRSs profile. This corrigendum is based on change request OGC 06-041." + "@value": "This document an interoperable hydrology profile for OGC Sensor Observation Service (SOS) 2.0 implementations serving OGC WaterML 2.0. This development is based on previous activities and results (i.e. Hydrology Interoperability Experiments as well as the European FP7 project GEOWOW). It is guided by the need to overcome mostly semantic issues between different SOS instances serving hydrological data and the according clients. Therefore, this profile focuses on how to use the entities and requests of the standards and covers the necessary technical details. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9258,35 +9257,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-111" + "@value": "14-004" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML 3.1.1 grid CRSs Profile Corrigendum" + "@value": "OGC Sensor Observation Service 2.0 Hydrology Profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-084r2", + "@id": "http://www.opengis.net/def/docs/16-005r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-02-17" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -9296,27 +9295,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/14-084r2/14-084r2.html" + "@id": "https://docs.ogc.org/bp/16-005r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Moving Features Encoding Extension: Simple Comma Separated Values (CSV)" + "@value": "16-005r4" }, { "@language": "en", - "@value": "14-084r2" + "@value": "Volume 2: OGC CDB Core Model and Physical Structure Annexes (Best Practice)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange." + "@value": "This document provides the Annexes for the CDB Core: Model and Physical Structure Standard. The only exception is Annex A, Abstract Test Suite (ATS). The CDB ATS Annex is in Volume 1: Core document." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9327,30 +9326,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-084r2" + "@value": "16-005r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV)" + "@value": "Volume 2: OGC CDB Core Model and Physical Structure Annexes (Best Practice)" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-018r1", + "@id": "http://www.opengis.net/def/docs/13-046r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-05-15" + "@value": "2014-02-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Fitch" + "@value": "Lew Leinenweber" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -9365,17 +9364,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47989" + "@id": "https://portal.ogc.org/files/?artifact_id=55432" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-018r1" + "@value": "13-046r2" }, { "@language": "en", - "@value": "Surface Water Interoperability Experiment FINAL REPORT" + "@value": "CHISP-1 Summary Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -9385,7 +9384,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report describes the methods, results, issues and recommendations generated by\r\nthe Surfacewater Interoperability Experiment (SW IE), carried out as an activity of the\r\nOGC Hydrology Domain Working Group (HDWG). The SW IE was designed to\r\nadvance the development of WaterML 2.0 and test its use with various OGC service\r\nstandards (SOS, WFS, WMS and CSW). A secondary aim was to contribute to the\r\ndevelopment of a hydrology domain feature model and vocabularies, which are\r\nessential for interoperability in the hydrology domain, although these are not the main\r\nfocus for the IE." + "@value": "This report summarizes the results of OGC’s Climatology-Hydrology Information Sharing Pilot, Phase 1 (CHISP-1). The objective of this initiative was to develop an inter-disciplinary, inter-agency and international virtual observatory system for water resources information from observations in the U.S. and Canada, building on current networks and capabilities.\r\nThe CHISP-1 Initiative was designed to support these Use Case functions:\r\n•\tHydrologic modeling for historical and current stream flow and groundwater conditions\r\n•\tModeling and assessment of nutrient load into the Great Lakes\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9396,35 +9395,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-018r1" + "@value": "13-046r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Surface Water Interoperability Experiment FINAL REPORT" + "@value": "OGC CHISP-1 Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-039r2", + "@id": "http://www.opengis.net/def/docs/18-062r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-04-06" + "@value": "2021-12-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Rob Atkinson, Irina Dornblut" + "@value": "Benjamin Pross, Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -9434,27 +9433,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47831" + "@id": "https://docs.ogc.org/is/18-062r2/18-062r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-039r2" + "@value": "OGC API - Processes - Part 1: Core" }, { "@language": "en", - "@value": "HY_Features: a Common Hydrologic Feature Model Discussion Paper" + "@value": "18-062r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes a conceptual model for the identification of hydrologic features independent from geometric representation. This model allows common reference to hydrologic features across scientific sub-disciplines in hydrology. The Hydrologic Feature Model, HY_Features, is designed as a set of interrelated Application Schemas using ISO 19103 Conceptual Schema Language and ISO 19109 General Feature Model. It is factored into relatively simple components that can be reviewed, tested and extended independently." + "@value": "The OGC API — Processes — Part 1: Core Standard supports the wrapping of computational tasks into executable processes that can be offered by a server through a Web API and be invoked by a client application. The standard specifies a processing interface to communicate over a RESTful protocol using JavaScript Object Notation (JSON) encodings. The standard leverages concepts from the OGC Web Processing Service (WPS) 2.0 Interface Standard but does not require implementation of a WPS.\r\n\r\nBy way of background and context, in many cases geospatial or location data, including data from sensors, must be processed before the information can be effectively used. The WPS Standard provides a standard interface that simplifies the task of making simple or complex computational geospatial processing services accessible via web services. Such services include well-known processes found in Geographic Information Systems (GIS) as well as specialized processes for spatiotemporal modeling and simulation. While the WPS standard was designed with spatial processing in mind, the standard could also be used to readily insert non-spatial processing tasks into a web services environment.\r\n\r\nThe OGC API — Processes Standard is a newer and more modern way of programming and interacting with resources over the web while allowing better integration into existing software packages. The OGC API — Processes Standard addresses all of the use cases that were addressed by the WPS Standard, while also leveraging the OpenAPI specification and a resource-oriented approach.\r\n\r\nThe resources that are provided by a server implementing the OGC API — Processes Standard are listed in Table 1 below and include information about the server, the list of available processes (Process list and Process description), jobs (running processes) and results of process executions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9465,30 +9464,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-039r2" + "@value": "18-062r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "HY_Features: a Common Hydrologic Feature Model Discussion Paper" + "@value": "OGC API - Processes - Part 1: Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-088r1", + "@id": "http://www.opengis.net/def/docs/09-037r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-02-07" + "@value": "2009-07-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Luis Bermudez" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -9503,17 +9502,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-088r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=34098" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-088r1" + "@value": "OWS-6 UTDS-CityGML Implementation Profile" }, { "@language": "en", - "@value": "Strengthening Disaster Risk Reduction Across the Americas Summit - Simulated Exercise Engineering Report" + "@value": "09-037r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -9523,7 +9522,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Disasters are responsible for major socioeconomic damages. Global initiatives call for the improvement of information technology infrastructure to better share data and advance multinational collaboration.\r\n\r\nThe Strengthening Disaster Risk Reduction Across the Americas: A Regional Summit on the Contributions of Earth Observations held on September 3-8 in 2017 in Buenos Aires, Argentina strengthened the collective ability to share the many challenges of disaster risk reduction in Latin America and the Caribbean (LAC) while promoting the awareness and better use of earth observations (EO).\r\n\r\nA simulation exercise took place during the summit. The exercise brought together government, emergency managers, earth observation data providers, academics, non-governmental organizations, and commercial companies. The participants assessed the capabilities and needs of policymakers, regional and on-the-ground decision makers, and learned what information products can be produced, and when and how such products are available.\r\n\r\nThis ER describes the description and results of the simulated scenario including the post-exercise activity that captured the lessons learned from the participants.\r\n\r\n" + "@value": "This OGC document specifies a CityGML-based application schema for a subset of an Urban Topographic Data Store (UTDS) as specified by the US National Geospatial-Intelligence Agency (NGA).\r\nThe particular focus of this implementation profile was to test the applicability of CityGML to UTDS data. \r\nThis document specifies the implementation profile as well as the findings.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9534,30 +9533,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-088r1" + "@value": "09-037r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Strengthening Disaster Risk Reduction Across the Americas Summit - Simulated Exercise Engineering Report" + "@value": "OWS-6 UTDS-CityGML Implementation Profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-014r2", + "@id": "http://www.opengis.net/def/docs/23-011r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-04-26" + "@value": "2023-06-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Greg Schumann, Josh Lieberman" + "@value": "Martin Desruisseaux, Logan Stark" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -9572,17 +9571,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-014r2.html" + "@id": "https://docs.ogc.org/per/23-011r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-014r2" + "@value": "Testbed-18: 3D+ Data Space Object Engineering Report" }, { "@language": "en", - "@value": "Incident Management Information Sharing (IMIS) Internet of Things (IoT) Architecture Engineering Report" + "@value": "23-011r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -9592,7 +9591,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives.\r\n•\tApply Open Geospatial Consortium (OGC) principles and practices for collaborative development to existing standards and technology to prototype an IoT approach to sensor use for incident management. \r\n•\tEmploy an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability. \r\n•\tDevelop profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability. \r\n•\tPrototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario. \r\n" + "@value": "With the growing commercialization of space there is a need to look beyond the earth and explore the integration of sensors or assets in celestial orbits or in free flight in our solar system. Their exact tracking and localization are becoming increasingly important as space emerges as the newest area in need for standard-based mechanisms for streaming and for data integration from various sensors.\r\n\r\nThis Open Geospatial Consortium (OGC) Testbed 18 3D+ Data Space Object Engineering Report (ER) describes existing standards in terms of their ability to represent a suite of multidimensional Coordinate Reference Systems (CRS) and associated geometries as well as identifies shortfalls in these standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9603,35 +9602,49 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-014r2" + "@value": "23-011r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Incident Management Information Sharing (IMIS) Internet of Things (IoT) Architecture Engineering Report" + "@value": "Testbed-18: 3D+ Data Space Object Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-187r1", + "@id": "http://www.opengis.net/def/doc-type/cr", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/06-043r3" + }, + { + "@id": "http://www.opengis.net/def/docs/06-098" + }, + { + "@id": "http://www.opengis.net/def/docs/08-022r1" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/05-110", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-07" + "@value": "2006-04-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steven Keens" + "@value": "Arliss Whiteside, Bill Woodward, co-editor" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -9641,27 +9654,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=19778" + "@id": "https://portal.ogc.org/files/?artifact_id=13186" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Workflow Descriptions and Lessons Learned" + "@value": "05-110" }, { "@language": "en", - "@value": "06-187r1" + "@value": "Feature Portrayal Service" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document examines five workflows discussed during the course of the OWS-4 project. " + "@value": "This document specifies the interface to a Feature Portrayal Service (FPS), which applies styles to digital features to produce a map image. The styles applied are identified or specified by the client, and are applied to digital feature data retrieved from a Web Feature Service (WFS) identified by the client. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9672,69 +9685,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-187r1" + "@value": "05-110" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-4 Workflow IPR" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/pc/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type Profile Corrigendum - Approved" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Documents of type Profile Corrigendum - Approved" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/06-111" - }, - { - "@id": "http://www.opengis.net/def/docs/06-113" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Documents of type Profile Corrigendum - Approved" + "@value": "Feature Portrayal Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-055r1", + "@id": "http://www.opengis.net/def/docs/07-039r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-06-02" + "@value": "2007-05-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Louis Rose" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -9744,27 +9723,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1282" + "@id": "https://portal.ogc.org/files/?artifact_id=21469" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-055r1" + "@value": "KML 2.1 Reference - An OGC Best Practice" }, { "@language": "en", - "@value": "Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint" + "@value": "07-039r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*RETIRED* specifies the Engineering Viewpoint for the Critical Infrastructure Collaborative Environment (CICE). This open, distributed processing environment crosses organizational boundaries and includes a variety of components deployed within multiple communities. The CICE leverages OGC Web Services the publication of the availability of critical infrastructure services and data; the registration and categorization of published service and data providers; and the discovery and use of needed critical infrastructure services and data" + "@value": "KML is a file format used to display geographic data in an Earth browser, such as Google Earth, Google Maps, and Google Maps for Mobile. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9775,35 +9754,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-055r1" + "@value": "07-039r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint" + "@value": "KML 2.1 Reference - An OGC Best Practice" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-019", + "@id": "http://www.opengis.net/def/docs/08-069r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-04-04" + "@value": "2009-03-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gerhard Gröger, Thomas H. Kolbe, Claus Nagel, Karl-Heinz Häfele" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/ts" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -9813,27 +9792,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47842" + "@id": "https://portal.ogc.org/files/?artifact_id=32314" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-019" + "@value": "08-069r2" }, { "@language": "en", - "@value": "City Geography Markup Language (CityGML) Encoding Standard" + "@value": "Web Coverage Processing Service (WCPS) Abstract Test Suite" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/ts" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211.\r\n\r\nThe aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. \r\n" + "@value": "" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9844,30 +9823,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-019" + "@value": "08-069r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC City Geography Markup Language (CityGML) Encoding Standard" + "@value": "Web Coverage Processing Service (WCPS) Abstract Test Suite" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-048", + "@id": "http://www.opengis.net/def/docs/15-073r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-07-22" + "@value": "2015-11-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthias Mohr" + "@value": "E. Devys, L.Colaiacomo, P. Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -9882,17 +9861,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-048.html" + "@id": "https://portal.ogc.org/files/?artifact_id=65887" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-048" + "@value": "Testbed-11 DGIWG GMLJP2 testing results Engineering Report" }, { "@language": "en", - "@value": "OGC Testbed 19 Draft API - Geodatacubes specification" + "@value": "15-073r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -9902,7 +9881,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 19 Engineering Report documents a draft OGC API — GeoDataCube Standard (aka GDC API). The OGC Member participants in this Testbed 19 activity developed, documented, and tested the draft OGC GDC API Standard. The draft will be submitted to the OGC GeoDataCube Standards Working Group (SWG) as a new standards work item.\r\n\r\nThe OGC GeoDataCube SWG was chartered to respond to the long-standing issue of establishing a standard that supports accessing and processing geospatial datacubes in an interoperable way. The draft OGC API — GeoDataCube that was developed in OGC Testbed 19 responds to this need and proposes a draft API specification.\r\n\r\nThe Testbed 19 GDC initiative targeted enhanced interoperability. The draft GDC API Standard was based on OGC API — Common, OGC API — Coverages Standard, OGC API — Processes Standard, the STAC API, and the openEO API. The Testbed 19 participants concentrated on server and client application development, and usability testing based on conformance classes and use cases. The draft GDC API is defined as an OpenAPI 3.0 document and provides endpoints for capabilities, data discovery/access, process discovery, and data processing. Notably, the draft GDI API Standard is extensible through additional implementations of OGC API Standards or openEO API parts. Documentation is available in machine-readable YAML and human-friendly HTML through a GitHub repository." + "@value": "This OGC Engineering Report (ER) describes work done in OGC Testbed 11 to test\r\nGMLJP2 in terms of defining a DGIWG GMLJP2 version 1 profile.\r\nThe requirements for a DGIWG profile of GMLJP2 have been documented in the\r\nDGIWG GMLJP2 version 1 profile. The Imagery WG inside DGIWG has developed a\r\nfilter to map the files produced using the previous GMLJP2 schema into the GMLJP2\r\nversion 2 schema and is about to submit a GMLJP2 2.0 profile to DGIWG.\r\nThe DGIWG implementation of the GMLJP2 profile is based on the OGC GMLJP2 v2\r\nand other requirements are coming directly from the adoption inside the DGIWG of the\r\nnew OGC GMLJP2 version 2.\r\nThis Testbed 11 activity is a response to the need of harmonization between DGIWG and\r\nOGC." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9913,35 +9892,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-048" + "@value": "15-073r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed 19 Draft API - Geodatacubes specification" + "@value": "OGC® Testbed-11 DGIWG GMLJP2 testing results Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-191r1", + "@id": "http://www.opengis.net/def/docs/03-064r10", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-12-11" + "@value": "2005-05-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Claus Nagel, Thomas Becker, Robert Kaden, Ki-Joune Li, Jiyeong Lee, Thomas H. Kolbe" + "@value": "Greg Reynolds" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -9951,27 +9930,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41727" + "@id": "https://portal.ogc.org/files/?artifact_id=10378" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Requirements and Space-Event Modeling for Indoor Navigation" + "@value": "03-064r10" }, { "@language": "en", - "@value": "10-191r1" + "@value": "Geographic Objects Implementation Specification *RETIRED*" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OpenGIS® Discussion Paper presents a Multilayered Space-Event Model for indoor navigation which simultaneously addresses route planning, multiple localization methods, navigation contexts, and different locomotion types. The paper contains the corresponding data models as well as their encoding in GML 3.1.1." + "@value": "*THIS STANDARD HAS BEEN RETIRED*\r\n\r\nThe OpenGIS® Geographic Objects Interface Standard (GOS) provides an open set of common, lightweight, language-independent abstractions for describing, managing, rendering, and manipulating geometric and geographic objects within an application programming environment. It provides both an abstract object standard (in UML) and a programming-language-specific profile (in Java). The language-specific bindings serve as an open Application Program Interface (API)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -9982,35 +9961,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-191r1" + "@value": "03-064r10" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Requirements and Space-Event Modeling for Indoor Navigation" + "@value": "OpenGIS Geographic Objects Implementation Specification *RETIRED*" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-014r5", + "@id": "http://www.opengis.net/def/docs/07-023r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-10-10" + "@value": "2007-05-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Paul Cote" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10020,27 +9999,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1012" + "@id": "https://portal.ogc.org/files/?artifact_id=21622" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "01-014r5" + "@value": "OGC Web Services Architecture for CAD GIS and BIM" }, { "@language": "en", - "@value": "CT Definition Data for Coordinate Reference" + "@value": "07-023r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A data model for coordinate reference systems to provide a common framework across all OGC specifications." + "@value": "This document lists the design principles and requirements for future versions of a potential architecture for integrating workflows and information models from Computer Aided Design and Building Information Modelling with the principles of the OGC Web Services Architecture. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10051,35 +10030,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-014r5" + "@value": "07-023r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CT Definition Data for Coordinate Reference" + "@value": "OGC Web Services Architecture for CAD GIS and BIM" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-025", + "@id": "http://www.opengis.net/def/docs/10-073r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-01-18" + "@value": "2010-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Josh Lieberman" + "@value": "Scott Fairgrieve" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10089,27 +10068,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1320" + "@id": "https://portal.ogc.org/files/?artifact_id=39728" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-025" + "@value": "OWS-7 CCSI-SWE Best Practices Engineering Report" }, { "@language": "en", - "@value": "Web Services Architecture" + "@value": "10-073r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Specifies and discusses a common architectural framework for OGC Web Services" + "@value": "This document seeks to define the Best Practices for integrating Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) compliant and potentially other CBRN-based sensors into an OGC Sensor Web Enablement (SWE)-based environment. The document focuses on the practical application of SWE services and encodings for describing and interacting with CCSI sensors and data and draws heavily from and expands upon work performed in the OGC Web Services Phase 6 (OWS-6) testbed to define methodologies for integrating CCSI sensors into a SWE-based environment both now, by building upon the OWS-6 work, and in the future, by defining CCSI profiles of the SWE specifications." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10120,35 +10099,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-025" + "@value": "10-073r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Services Architecture" + "@value": "OWS-7 CCSI-SWE Best Practices Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-085", + "@id": "http://www.opengis.net/def/docs/10-070r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-02-20" + "@value": "2010-11-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Richard Creps,Victor Brown,Bill Floyd,John Garcia,Jeff Grinstead,Robert Kraus,Steve Matney,Robert Qu" + "@value": "Peter Schut" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10158,27 +10137,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7564" + "@id": "https://portal.ogc.org/files/?artifact_id=40095" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "EA-SIG Collaboration White Paper" + "@value": "Georeferenced Table Joining Service Implementation Standard" }, { "@language": "en", - "@value": "04-085" + "@value": "10-070r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*RETIRED* The focus of collaboration services discussed in this white paper is on applications that directly support user interaction and on the applications that monitor, manage and control these interactive services." + "@value": "This document is the specification for a Table Joining Service (TJS). This OGC standard defines a simple way to describe and exchange tabular data that contains information about geographic objects." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10189,30 +10168,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-085" + "@value": "10-070r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "EA-SIG Collaboration White Paper" + "@value": "OpenGIS® Georeferenced Table Joining Service Implementation Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-137r2", + "@id": "http://www.opengis.net/def/docs/09-063", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-12" + "@value": "2009-09-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lorenzo Bigagli" + "@value": "Lewis Leinenweber" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -10227,17 +10206,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-137r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=34127" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 PubSub / Catalog Engineering Report" + "@value": "09-063" }, { "@language": "en", - "@value": "16-137r2" + "@value": "OWS-6 GeoProcessing Workflow Thread Summary ER" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -10247,7 +10226,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes how the OGC PubSub standard can be used as a mechanism to automatically notify analysts of data availability for CSW and other OGC Web Services (e.g. WFS, WCS). In particular, this document proposes the following:\r\n\r\nSpecific PubSub 1.0 extensions for CSW 2.0.2 and 3.0, leveraging on standard functionalities, data models, and semantics to enable sending notifications based on user-specified area of interest and/or keywords;\r\n\r\nA general, basic mechanism for enabling PubSub for the generic OGC Web Service over the existing request/reply OWS’s, i.e. usual requests as filters, usual responses as appropriate updates/data pushes, existing semantics and syntax expressiveness.\r\n\r\nThis document is the result of activity performed within the Large-Scale Analytics (LSA) Thread of the OGC Testbed 12 Interoperability initiative, being identified as document deliverable A074 PubSub / Catalog Engineering Report. This document also captures lessons learnt from the implementation of component deliverable A016 CSW 2.0.2 with PubSub Core Support Server." + "@value": "This OGC® document summarizes work completed in the GeoProcessing Workflow thread of the OWS-6 Testbed, it is applicable to the OGC Interoperability Program testbed.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10258,35 +10237,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-137r2" + "@value": "09-063" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 PubSub / Catalog Engineering Report" + "@value": "OWS-6 GeoProcessing Workflow Thread Summary ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-069r4", + "@id": "http://www.opengis.net/def/docs/19-083", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-05-11" + "@value": "2020-02-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele, Panagiotis (Peter) A. Vretanos, Charles Heazel" + "@value": "Joan Masó" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10296,27 +10275,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/17-069r4/17-069r4.html" + "@id": "https://docs.ogc.org/per/19-083.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC API - Features - Part 1: Core corrigendum" + "@value": "Citizen Science Interoperability Experiment Engineering Report" }, { "@language": "en", - "@value": "17-069r4" + "@value": "19-083" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the behavior of Web APIs that provide access to features in a dataset in a manner independent of the underlying data store. This standard defines discovery and query operations.\r\n\r\nDiscovery operations enable clients to interrogate the API, including the API definition and metadata about the feature collections provided by the API, to determine the capabilities of the API and retrieve information about available distributions of the dataset.\r\n\r\nQuery operations enable clients to retrieve features from the underlying data store based upon simple selection criteria, defined by the client." + "@value": "This Engineering report describes the first phase of the Citizen Science (CS) Interoperability Experiment (IE) organized by the EU H2020 WeObserve project under the OGC Innovation Program and supported by the four H2020 Citizen Observatories projects (SCENT, GROW, LandSense, and GroundTruth 2.0) as well as the EU H2020 NEXTGEOSS project. The activity covered aspects of data sharing architectures for Citizen Science data, data quality, data definitions and user authentication.\r\n\r\nThe final aim was to propose solutions on how Citizen Science data could be integrated in the Global Earth Observation System of Systems (GEOSS). The solution is necessarily a combination of technical and networking components, being the first ones the focus of this work. The applications of international geospatial standards in current Citizen Science and citizen observatory projects to improve interoperability and foster innovation is one of the main tasks in the IE.\r\n\r\nThe main result of the activity was to demonstrate that Sensor Observing Services can be used for Citizen Science data (as proposed in the Open Geospatial Consortium (OGC) Sensor Web Enablement for Citizen Science (SWE4CS) Discussion Paper) by implementing SWE4CS in several clients and servers that have been combined to show Citizen Science observations. In addition, an authentication server was used to create a federation between three projects. This federated approach is part of the proposed solution for GEOSS that can be found in the last chapter. Many open issues have been identified and are expected to be addressed in the second phase of the experiment, including the use of a definitions server." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10327,35 +10306,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-069r4" + "@value": "19-083" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Features - Part 1: Core corrigendum" + "@value": "OGC Citizen Science Interoperability Experiment Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-146r2", + "@id": "http://www.opengis.net/def/docs/16-140r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-05-11" + "@value": "2017-06-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Kyoung-Sook KIM, Hirotaka OGAWA" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/sap" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10365,27 +10344,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=48553" + "@id": "https://docs.ogc.org/bp/16-140r1/16-140r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-146r2" + "@value": "OGC Moving Features Encoding Extension - JSON" }, { "@language": "en", - "@value": "Coverage Implementation Schema" + "@value": "16-140r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/sap" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies a GML coverage structure extending the definition of GML 3.2.1 [07-036] in a compatible way.\r\n\r\nMain change over GML is the addition of one mandatory component, rangeType, to the Coverage definition of GML 3.2.1 to provide a concise description of the coverage range\r\nvalue definition. Further, handling of format encodings different from GML are established.\r\n\r\nThis enhanced coverage type is used, for example, by the Web Coverage Service (WCS) Standard [1] version 2.0 and higher, but is independent from WCS service. This augmented\r\ncoverage structure can serve a wide range of coverage application domains and service types, thereby contributing to harmonization and interoperability." + "@value": "This document proposes a JavaScript Object Notation (JSON) encoding representation of movement of geographic features as an encoding extension of OGC Moving Features ([OGC 14-083r2] and [OGC 14-084r2]). A moving feature, typically a vehicle and pedestrian, can be expressed as a temporal geometry whose location continuously changes over time and contains dynamic non-spatial attributes whose values vary with time. This Best Practice describes how to share moving feature data based on JSON and GeoJSON (a JSON format for encoding geographic data structures). In addition, this document provides an example of RESTful approaches as a Feature Service Interface that has the potential for simplicity, scalability, and resilience with respect to exchange of moving feature data across the Web." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10396,35 +10375,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-146r2" + "@value": "16-140r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Coverage Implementation Schema" + "@value": "OGC Moving Features Encoding Extension - JSON" } ] }, { - "@id": "http://www.opengis.net/def/docs/00-117", + "@id": "http://www.opengis.net/def/docs/17-083r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2000-05-15" + "@value": "2019-10-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman" + "@value": "Joan Masó" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10434,27 +10413,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=988" + "@id": "https://docs.ogc.org/is/17-083r2/17-083r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 17 - Location Based Mobile Services" + "@value": "Two Dimensional Tile Matrix Set" }, { "@language": "en", - "@value": "00-117" + "@value": "17-083r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Draft Abstract Spec for Location Based Services. Never formally adopted" + "@value": "The OGC Tile Matrix Set standard defines the rules and requirements for a tile matrix set as a way to index space based on a set of regular grids defining a domain (tile matrix) for a limited list of scales in a Coordinate Reference System (CRS) as defined in [OGC 08-015r2] Abstract Specification Topic 2: Spatial Referencing by Coordinates. Each tile matrix is divided into regular tiles. In a tile matrix set, a tile can be univocally identified by a tile column a tile row and a tile matrix identifier. This document presents a data structure defining the properties of the tile matrix set in both UML diagrams and in tabular form. This document also presents a data structure to define a subset of a tile matrix set called tile matrix set limits. XML and JSON encodings are suggested both for tile matrix sets and tile matrix set limits. Finally, the document offers practical examples of tile matrix sets both for common global projections and for specific regions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10465,35 +10444,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "00-117" + "@value": "17-083r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 17 - Location Based Mobile Services" + "@value": "OGC Two Dimensional Tile Matrix Set" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-101", + "@id": "http://www.opengis.net/def/docs/06-050r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-04-30" + "@value": "2006-07-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/can" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10503,27 +10482,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-101.html" + "@id": "https://portal.ogc.org/files/?artifact_id=15755" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Vector Tiles Pilot Extension Engineering Report" + "@value": "GeoRSS, An Introduction to" }, { "@language": "en", - "@value": "18-101" + "@value": "06-050r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/can" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The purpose of the OGC Vector Tiles Pilot Extension (VTPExt) was to address portrayal and style encoding concerns that were discovered in the initial phase of the Vector Tiles Pilot (VTP). During the VTPExt, participants selected a common baseline style used by all participants and in some cases created additional style offerings. The work conducted during the VTPExt has adhered to the established findings from the initial VTP documented in the VTP Summary Engineering Report (ER) [1].\r\n\r\nThis document describes the following:\r\n\r\nthe research and evaluation to determine approach(es) to apply styling to Mapbox and GeoJSON Tiled Feature Data through Web Feature Service (WFS) 3.0, Web Map Tile Service (WMTS) 1.0, and GeoPackage (GPKG) 1.2,\r\n\r\nthe styling approach, challenges, and interoperability considerations discovered during the initiative, and\r\n\r\nany extensions required or best practices recommended to facilitate development, encoding, offering, and exchange of styles. This includes how styles are offered from servers, how the desired style offering can be selected by the client from multiple server style offerings (e.g. GetStyles request), and how clients can apply their own styles." + "@value": "GeoRSS is simple proposal for geo-enabling, or tagging, really simple syndication (RSS) feeds with location information. GeoRSS proposes a standardized way in which location is encoded with enough simplicity and descriptive power to satisfy most needs to describe the location of Web content. GeoRSS may not work for every use, but it should serve as an easy-to-use geotagging encoding that is brief and simple with useful defaults but extensible and upwardly-compatible with more sophisticated encoding standards such as the OGC (Open Geospatial Consortium) GML (Geography Markup Language)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10534,35 +10513,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-101" + "@value": "06-050r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Vector Tiles Pilot Extension Engineering Report" + "@value": "GeoRSS, An Introduction to" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-107", + "@id": "http://www.opengis.net/def/docs/10-032r8", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-03-31" + "@value": "2014-04-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman" + "@value": "Pedro Gonçalves" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10572,27 +10551,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=892" + "@id": "https://portal.ogc.org/files/?artifact_id=56866" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 07 - Earth Imagery" + "@value": "OpenSearch Geo and Time Extensions" }, { "@language": "en", - "@value": "99-107" + "@value": "10-032r8" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Topic Volume will provide essential and abstract models for technology that is already used widely (but not interoperably) across the GIS landscape. This technology properly depends on the more general technology that supports Coverages." + "@value": "

This OGC standard specifies the Geo and Time extensions to the OpenSearch query protocol. OpenSearch is a collection of simple formats for the sharing of search results.

\r\n

The OpenSearch description document format can be used to describe a search engine so that it can be used by search client applications. The OpenSearch description format allows the use of extensions that allow search engines to request a specific and contextual query parameter from search clients.

\r\n

The OpenSearch response elements can be used to extend existing syndication formats, such as RSS and Atom, with the extra metadata needed to return search results.\r\nServices that support the OpenSearch Specification, the Geo and Time extensions defined in this document are called OpenSearch GeoTemporal Services.

\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10603,41 +10582,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-107" + "@value": "10-032r8" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 7 - Earth Imagery" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-isc", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/12-128r11" - }, - { - "@id": "http://www.opengis.net/def/docs/06-189" + "@value": "OGC® OpenSearch Geo and Time Extensions" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-158", + "@id": "http://www.opengis.net/def/docs/07-166r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-01-02" + "@value": "2008-08-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "R" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -10652,17 +10620,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=25280" + "@id": "https://portal.ogc.org/files/?artifact_id=27052" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-158" + "@value": "07-166r2" }, { "@language": "en", - "@value": "Wrapping OGC HTTP-GET/POST Services with SOAP" + "@value": "OWS-5 Engineering Report on WCPS" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -10672,7 +10640,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Discussion of how to wrap OGC HTTP-GET/POST Services with SOAP" + "@value": "This document represents the Engineering Report for the WCPS activity within the OWS-5 SWE thread. It summarizes tasks and outcomes." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10683,35 +10651,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-158" + "@value": "07-166r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Wrapping OGC HTTP-GET/POST Services with SOAP" + "@value": "OGC OWS-5 Engineering Report on WCPS" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-000", + "@id": "http://www.opengis.net/def/docs/15-005r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-03-28" + "@value": "2016-02-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis, Johannes Echterhoff" + "@value": "Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10721,27 +10689,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=38478" + "@id": "https://portal.ogc.org/files/?artifact_id=66933" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Sensor Planning Service Implementation Standard" + "@value": "15-005r1" }, { "@language": "en", - "@value": "09-000" + "@value": "DGIWG - Web Feature Service 2.0 Profile" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Sensor Planning Service Interface Standard (SPS) defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor planning request; to submit and reserve/commit such a request; to inquire about the status of such a request; to update or cancel such a request; and to request information about other OGC Web services that provide access to the data collected by the requested task. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards." + "@value": "This document defines the DGIWG profile for the ISO\r\n19142:2010 - Web Feature Service (WFS) including changes\r\nmade in the OpenGIS Web Feature Service 2.0 Interface\r\nStandard - Corrigendum. The Web Feature Service provides\r\naccess to geospatial features in a manner independent of the\r\nunderlying data store." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10752,35 +10720,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-000" + "@value": "15-005r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Sensor Planning Service Implementation Standard" + "@value": "DGIWG - Web Feature Service 2.0 Profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-085r5", + "@id": "http://www.opengis.net/def/docs/15-057r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-04-07" + "@value": "2015-11-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lucio Colaiacomo, Joan Masó, Emmanuel Devys " + "@value": "Matthes Rieke, Simon Jirka, Stephane Fellah" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10790,27 +10758,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/08-085r5/08-085r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=64353" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-085r5" + "@value": "Testbed-11 Incorporating Social Media in Emergency Response Engineering Report" }, { "@language": "en", - "@value": "GML in JPEG 2000 (GMLJP2) Encoding StandardPart 1: Core" + "@value": "15-057r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard applies to the encoding and decoding of JPEG 2000 images that contain GML for use with geographic imagery.\r\nThis document specifies the use of the Geography Markup Language (GML) within the XML boxes of the JPEG 2000 data format and provides an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations. The document also specifies the encoding and packaging rules for GML use in JPEG 2000.\r\n" + "@value": "This OGC Engineering Report (ER) was created as a deliverable for the OGC Testbed 11 initiative of the OGC Interoperability Program. This ER describes an approach for incorporating Social Media for Emergency Response applications that use spatial data infrastructures. This document also reports on findings about the advancements using Social Media and VGI resources. The ER includes ideas on improving the architecture, service change recommendations (primarily concerning the OGC Sensor Observation Service (SOS) 2.0 interface), and lessons learned." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10821,35 +10789,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-085r5" + "@value": "15-057r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GML in JPEG 2000 (GMLJP2) Encoding StandardPart 1: Core" + "@value": "OGC® Testbed-11 Incorporating Social Media in Emergency Response Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-047r3", + "@id": "http://www.opengis.net/def/docs/08-126", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-07" + "@value": "2009-01-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Eugene Genong Yu, Liping Di" + "@value": "Cliff Kottman, Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10859,27 +10827,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-047r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=29536" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-047r3" + "@value": "Topic 05 - Features" }, { "@language": "en", - "@value": "Swath Coverage Engineering Report" + "@value": "08-126" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) presents a summary, description and findings of the Swath Coverage task conducted by the OGC Testbed-14 initiative." + "@value": "From ISO 19101, “A feature is an abstraction of a real world phenomenon”; it is a geographic feature if it is associated with a location relative to the Earth. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10890,35 +10858,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-047r3" + "@value": "08-126" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Swath Coverage Engineering Report" + "@value": "Topic 5 - Features" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-025r1", + "@id": "http://www.opengis.net/def/docs/18-008r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-08-05" + "@value": "2019-02-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Robert Thomas, Terry Idol" + "@value": "Christiaan Lemmen, Peter van Oosterom, Mohsen Kalantari, Eva-Maria Unger, Cornelis de Zeeuw" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10928,27 +10896,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=88037" + "@id": "https://docs.ogc.org/wp/18-008r1/18-008r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-025r1" + "@value": "18-008r1" }, { "@language": "en", - "@value": "Development of Spatial Data Infrastructures for Marine Data Management" + "@value": "White Paper on Land Administration" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report presents the results of a concept development study on a\r\nMarine Spatial Data Infrastructure (SDI), sponsored by the National Geospatial-\r\nIntelligence Agency (NGA) - Maritime Safety Office (MSO), on behalf of the\r\nInternational Hydrographic Organization (IHO) and the IHO MSDI Working Group\r\n(MSDIWG), and executed by the Open Geospatial Consortium (OGC). The goal of\r\nthis study was to demonstrate to stakeholders the diversity, richness and value of a\r\nMarine SDI – specifically data, analysis, interoperability and associated IT services\r\n- including web services - in addressing needs of the marine domain." + "@value": "This white paper provides an overview of the land administration domain and proposes actions needed for design and develop implementation standards this domain. A close cooperation between the Open Geospatial Consortium (OGC) and ISO is expected to accelerate those developments.\r\n\r\nA huge task is waiting: the establishment of land rights for all: young and old, rich and poor, male and female. Data on many millions of parcels, spatial units, (use-) rights, persons, and parties have to be collected, linked, maintained, and published. Land Administration Systems (LAS) should be designed for maintenance of the dynamic relations between people and land. Existing land administrations require extensions: such as 3D and 4D functionality and datasets, blockchain for transparent transactions, generic processes and integration with remote sensing, and processes to support conversion from social to legal tenure.\r\n\r\nA broad range of geospatial technologies and applications are available. They range from satellite and drone imaging and mapping, to geodesy, precise positioning, geo‐information science, cartography, spatial data infrastructure, and many surveying sub‐disciplines. The scientific and professional disciplines in the geospatial community design, develop, and apply those technologies. Apart from this technical component, a land administration also has a social and legal component. This makes land administration an arena where, apart from the geospatial community, many different scientific and professional disciplines meet. Depending on the stage of development and the level of societal acceptance of the land administration, those disciplines involved may be different." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -10959,35 +10927,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-025r1" + "@value": "18-008r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Development of Spatial Data Infrastructures for Marine Data Management" + "@value": "OGC White Paper on Land Administration" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-105r2", + "@id": "http://www.opengis.net/def/docs/15-050r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-03-24" + "@value": "2016-01-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman" + "@value": "Jeff Harrison" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -10997,27 +10965,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=890" + "@id": "https://portal.ogc.org/files/?artifact_id=65421" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 05 - Features" + "@value": "15-050r3" }, { "@language": "en", - "@value": "99-105r2" + "@value": "Testbed-11 Test and Demonstration Results for NIEM using IC Data Encoding Specifications Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A feature object (in software) corresponds to a real world or abstract entity." + "@value": "The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community\r\n(IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0\r\narchitecture through the development, implementations, test, and robust demonstration\r\nmaking use of IC specifications, Geography Markup Language (GML), and NIEM in a\r\nsimulated “real-world” scenario. The demonstration scenario begins with NIEMconformant\r\nInformation Exchange Packages (IEPs) containing operational data and IC\r\nsecurity tags from the Information Security Marking (ISM) and Need-To-Know (NTK)\r\naccess control metadata, and the Trusted Data Format (TDF) for binding assertion\r\nmetadata with data resource(s). Those instance documents are deployed using Open\r\nGeospatial Consortium (OGC) standards enabled Web Services for use by client\r\napplications. Access control is based on attributes of the end-user and the instance data.\r\nRecommendations to update these information exchanges were provided to reflect NIEM\r\n3.0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment tested\r\nthis data encoding in OGC Web Feature Services (WFS) and Policy Enforcement Points\r\n(PEP) accessed by multiple client applications. Results from this task provided a\r\npreliminary architecture that was tested and demonstrated in Testbed 11, and summarized\r\nin other OGC Testbed 11 Engineering Reports. The demonstrations also highlighted how\r\nNIEM and IC data encodings together may support more agile and customer-centric\r\nframeworks driven by collaborative partnerships. This transformation is vital to\r\nconfronting the security challenges of the future." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11028,35 +10996,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-105r2" + "@value": "15-050r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 5 - Features" + "@value": "OGC Testbed-11 Test and Demonstration Results for NIEM using IC Data Encoding Specifications Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-120r4", + "@id": "http://www.opengis.net/def/docs/10-100r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-02-23" + "@value": "2011-05-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -11066,27 +11034,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=72711" + "@id": "https://portal.ogc.org/files/?artifact_id=42729" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure" + "@value": "Geography Markup Language (GML) simple features profile (with Corrigendum)" }, { "@language": "en", - "@value": "15-120r4" + "@value": "10-100r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The CDB standard defines a standardized model and structure for a single, “versionable”, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time.\r\nThe application of CDB to future simulation architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the High Level Architecture - -Federation Object Model (HLA/FOM) and DIS protocols, the application of the CDB standard provides a Common Environment to which inter-connected simulators share a common view of the simulated environment.\r\nThe CDB standard defines an open format for the storage, access and modification of a synthetic environment database. A synthetic environment is a computer simulation that represents activities at a high level of realism, from simulation of theaters of war to factories and manufacturing processes. These environments may be created within a single computer or a vast distributed network connected by local and wide area networks and augmented by super-realistic special effects and accurate behavioral models. SE allows visualization of and immersion into the environment being simulated . \r\nThis standard defines the organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The standard makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. A series of associated OGC Best Practice documents define rules and guidelines for data representation of real world features.\r\n" + "@value": "This approved OGC Implementation Standard defines a Simple Features profile of the Geography Markup Language version 3.2. This Simple Features Profile has been aligned with the OGC Simple Features standard for SQL version 1.2. Simple Features include: Point, Curve (LineString), Surface (Polygon), Geometry, MultiPoint, MultiCurve, MultiSurface, and MultiGeometry. The detailed abstract model for OGC features and geometry can be found in the OGC Abstract Specification, Topic Volume 1: Features (which is equivalent to ISO 19107).\r\n\r\nThis Simple Features profile of GML began as a product of OGC’s Interoperability Program: a global, collaborative, hands-on engineering and testing program designed to deliver prototype technologies and proven candidate standards into the OGC’s Specification Development Program. In OGC Interoperability Initiatives, international teams of technology providers work together to solve specific geo-processing interoperability problems posed by Initiative. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11097,35 +11065,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-120r4" + "@value": "10-100r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure" + "@value": "Geography Markup Language (GML) simple features profile (with Corrigendum)" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-050", + "@id": "http://www.opengis.net/def/docs/24-025", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-05-02" + "@value": "2024-07-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Tom Kralidis" + "@value": "Carsten Rönsdorf, Fabrice Servant, H.C. Gruler, Nick Giannias, Kyoungsook Kim, Zubran Soleiman, Dim" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -11135,27 +11103,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27286" + "@id": "https://docs.ogc.org/dp/24-025.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Map Context Documents Corrigendum 1" + "@value": "Urban Digital Twins: Integrating Infrastructure, natural environment and people" }, { "@language": "en", - "@value": "08-050" + "@value": "24-025" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the details for a corrigendum for the existing OpenGIS Standard for the Web Map Context Documents version 1.1.0 and does not modify that standard. The current OpenGIS IS that this document provides revision notes for is 05-005. This document is a corrigendum to 05-005." + "@value": "This position paper is aimed at city officials and domain professionals working in an urban data context. Its goal is to clarify the concept of Urban Digital Twins (UDT) and to position it in regards of Digital Twins in general as well as the emerging Metaverse. \r\n\r\nOverall, the UDT concept is an approach to understand characteristics and processes of the built environment at the scale of a city. Between climate change and various demographics, dynamic cities are facing challenges that are becoming more complex to solve. Most of the time solutions have to be imagined with a system of systems approach and cannot be solved in silos.\r\n\r\nThe paper represents the current state of the discussion about UDTs in the Open Geospatial Consortium (OGC), a geospatial community and standards organization. \r\n\r\nAround 3 use cases, climate change adaptation, urban transformation, and urban air mobility, this paper identifies benefits of using a UDT and explain the role of Geospatial Information (GI) and how it can contribute to an UDT.\r\n\r\nUDTs is a digital representation of the city where elected representatives and professional stakeholders can access and contribute to a common reference model to collaborate, achieving positive outcomes for the citizens. UDTs reveal insights at the intersection of the natural and built environments and human activities. They provide the means of enabling simulation scenarios and plan possible interventions as well as tracking measurable evidence of any changes in the real world. In a mature state, UDTs will establish effective feedback loops between the virtual and the true, physical environments. \r\n\r\nFrom discussions with elected representatives, professionals, and also based on OGC member experience on projects, it is acknowledged that the process of building an UDT might seem daunting (as outlined in the paper by [Lei, 2023]: Challenges of urban digital twins: A systematic review and a Delphi expert survey).\r\n\r\nThis paper presents a pragmatic approach based on OGC standards for each use case, building on location and GI as the foundation. This approach calls for an effective data strategy and suggests that a project-based approach with a vision of building a UDT is the most efficient path.\r\n\r\nThis concept of UDT, although often mentioned in the media, is still fairly new in practice and the governance of that type of platform is still a challenge. OGC is keen on supporting and collaborating on projects to help create the best practices on that matter." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11166,30 +11134,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-050" + "@value": "24-025" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Map Context Documents Corrigendum 1" + "@value": "Urban Digital Twins: Integrating Infrastructure, natural environment and people" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-007", + "@id": "http://www.opengis.net/def/docs/12-104r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-08-20" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -11204,17 +11172,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-007.html" + "@id": "https://portal.ogc.org/files/?artifact_id=52065" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CDB Vector Data in GeoPackage Interoperability Experiment" + "@value": "12-104r1" }, { "@language": "en", - "@value": "19-007" + "@value": "OWS-9 Engineering Report - CCI - Single Point of Entry Global Gazetteer" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -11224,7 +11192,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) documents the results of the CDB Vector Data in GeoPackage Interoperability Experiment (IE). The participants in this IE tested transforming CDB Shapefile vector data into one or more GeoPackage(s) and storing the result in a CDB data store. GeoPackage Version 1.2 and CDB Version 1.1 and related Best Practices were the standards baseline used for this experiment. The IE builds on the work described in the OGC CDB, Leveraging GeoPackage Discussion Paper.\r\n\r\nA primary objective of this IE was to agree and document possible change requests and/or best practices for storing vector data in a CDB data using encodings and/or containers other than Shapefiles. These suggested changes requests and/or best/practices will be used as the basis for CDB Standards Working Group (SWG) discussions related to possible revisions to the CDB standard." + "@value": "This document provides a technical description of the Single Point of Entry Global Gazetteer (SPEGG) implemented for the OWS9 test bed. The SPEGG integrates two gazetteers – a copy of the USGS gazetteers containing domestic names (hosted by CubeWerx Inc.) and the NGA gazetteer containing foreign names (originally hosted at NGA but currently hosted by Intergraph Corp.). Both integrated gazetteers and the SPEGG implement the Web Feature Service (WFS) standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11235,30 +11203,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-007" + "@value": "12-104r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC CDB Vector Data in GeoPackage Interoperability Experiment" + "@value": "OGC® OWS-9 Engineering Report - CCI - Single Point of Entry Global Gazetteer" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-025r2", + "@id": "http://www.opengis.net/def/docs/18-091r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-03-05" + "@value": "2019-02-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Aleksandar Balaban" + "@value": "Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -11273,17 +11241,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-025r2.html" + "@id": "https://docs.ogc.org/per/18-091r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-025r2" + "@value": "18-091r2" }, { "@language": "en", - "@value": "Testbed-13: Quality Assessment Service Engineering Report" + "@value": "Application Schemas and JSON Technologies Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -11293,7 +11261,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) has been produced in conjunction with two other engineering reports from the OGC Testbed 13, the Abstract Data Quality ER [4] and the Data Quality Specification ER [5] to capture status quo, discussions, and results in the context of requirements for data quality assessment for Quality of Service in the Aviation Domain. It will, in particular, provide a Data Quality Assessment Service Specification. Much of the ER is presented in the future tense, using terms such as 'shall', in order to express requirements and constraints on future Data Quality Assessment Service implementations. The service specification includes design patterns, extension mechanisms, and service interface considerations.\r\n\r\nIn recent years, the concept of data quality has generated a notable interest among System Wide Information Management (SWIM) [17] implementers, both organization-specific and global. In the context of SWIM — and Service Oriented Architecture (SOA) implementations in general — data quality pertains to two major use cases, service advertising and service validation:\r\n\r\nService advertising\r\na service makes known to a potential consumer the quality of the data provided by the service. Based on this information, the consumer can determine whether or not the service meets its needs.\r\n\r\nService validation\r\nassurance is given that the quality of the data provided by a service is consistent with the quality that is explicitly defined in a service contract or any kind of agreement that may exist between a service provider and service consumer.\r\n\r\nBoth use cases share two common preconditions:\r\n\r\nAn unambiguous definition of the concept of data quality exists.\r\n\r\nA set of measurable parameters that allow specifying data quality is defined.\r\n\r\nThese are tasks that were performed as part of Testbed 13. The findings of the tasks are documented in the Abstract Data Quality ER (FA001)[4] and the Data Quality Specification ER (FA002)[5]." + "@value": "This Engineering Report (ER) enhances the understanding of the relationships between data exchange based on Geography Markup Language (GML), JavaScript Object Notation (JSON), and Resource Description Framework (RDF) for future web services, e.g. Web Feature Service (WFS) 3.0. The work documented in this report:\r\n\r\ncontributes to the ability to bridge between technology-dependent alternate representations of “features” (real-world objects), and to consistently employ alternate encoding technologies (Extensible Markup Language (XML), JSON, RDF) to exchange information about “features”; and\r\n\r\ndetermines principled techniques for the development of JSON-based schemas from ISO 19109-conformant application schemas.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11304,35 +11272,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-025r2" + "@value": "18-091r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: Quality Assessment Service Engineering Report" + "@value": "OGC Testbed-14: Application Schemas and JSON Technologies Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-064r2", + "@id": "http://www.opengis.net/def/docs/09-010", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-09-11" + "@value": "2009-07-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "Kristin Stock" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -11342,27 +11310,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34147" + "@id": "http://portal.opengeospatial.org/files/?artifact_id=32620" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-6 Sensor Web Enablement (SWE) Engineering Report" + "@value": "OGC® Catalogue Services - OWL Application Profile of CSW" }, { "@language": "en", - "@value": "09-064r2" + "@value": "09-010" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document summarizes work completed in the OWS-6 Sensor Web Enablement (SWE) thread. " + "@value": "This document describes an Application Profile for the Web Ontology Language (OWL) [W3C OWL] for CSW. It is intended to define a specification for how ontologies built using RDF and OWL may be included within an OGC CSW catalogue to semantically-enable the catalogue." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11373,35 +11341,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-064r2" + "@value": "09-010" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 Sensor Web Enablement (SWE) Engineering Report" + "@value": "OGC® Catalogue Services - OWL Application Profile of CSW" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-056r10", + "@id": "http://www.opengis.net/def/docs/12-168r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-11-28" + "@value": "2016-06-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Stephen Smyth" + "@value": "Douglas Nebert, Uwe Voges, Lorenzo Bigagli" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is-draft" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -11411,27 +11379,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dis/21-056r10/21-056r10.html" + "@id": "https://docs.ogc.org/is/12-168r6/12-168r6.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC GeoPose 1.0 Data Exchange Draft Standard" + "@value": "12-168r6" }, { "@language": "en", - "@value": "21-056r10" + "@value": "Catalogue Services 3.0 - General Model" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is-draft" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "GeoPose 1.0 is an OGC Implementation Standard for exchanging the location and orientation of real or virtual geometric objects (“Poses”) within reference frames anchored to the earth’s surface (“Geo”) or within other astronomical coordinate systems.\r\n\r\nThe standard specifies two Basic forms with no configuration options for common use cases, an Advanced form with more flexibility for more complex applications, and five composite GeoPose structures that support time series plus chain and graph structures.\r\n\r\nThese eight Standardization Targets are independent. There are no dependencies between Targets and each may be implemented as needed to support a specific use case.\r\n\r\nThe Standardization Targets share an implementation-neutral Logical Model which establishes the structure and relationships between GeoPose components and also between GeoPose data objects themselves in composite structures. Not all of the classes and properties of the Logical Model are expressed in individual Standardization Targets nor in the specific concrete data objects defined by this standard. Those elements that are expressed are denoted as implementation-neutral Structural Data Units (SDUs). SDUs are aliases for elements of the Logical Model, isolated to facilitate specification of their use in encoded GeoPose data objects for a specific Standardization Target.\r\n\r\nFor each Standardization Target, each implementation technology and corresponding encoding format defines the encoding or serialization specified in a manner appropriate to that technology.\r\n\r\nGeoPose 1.0 specifies a single encoding in JSON format (IETF RFC 8259). Each Standardization Target has a JSON Schema (Internet-Draft draft-handrews-json-schema-02) encoding specification. The key standardization requirements specify that concrete JSON-encoded GeoPose data objects must conform to the corresponding JSON Schema definition. The individual elements identified in the encoding specification are composed of SDUs, tying the specifications back to the Logical Model.\r\n\r\nThe GeoPose 1.0 Standard makes no assumptions about the interpretation of external specifications, for example, of reference frames. Nor does it assume or constrain services or interfaces providing conversion between GeoPoses of difference types or relying on different external reference frame definitions.\r\n\r\n" + "@value": "OGC® Catalogue Services support the ability to publish and search collections of\r\ndescriptive information (metadata records) for geospatial data, services, and related\r\ninformation. Metadata in catalogues represent resource characteristics that can be queried\r\nand presented for evaluation and further processing by both humans and software.\r\nCatalogue services are required to support the discovery and binding to registered\r\ninformation resources within an information community.\r\nThis part of the Catalogue Services standard describes the common architecture for OGC\r\nCatalogue Services. This document abstractly specifies the interfaces between clients and\r\ncatalogue services, through the presentation of abstract models. This common\r\narchitecture is Distributed Computing Platform neutral and uses UML notation. Separate\r\n(Part) documents specify the protocol bindings for these Catalogue services, which build\r\nupon this document, for the HTTP (or CSW) and OpenSearch protocol bindings.\r\nAn Abstract Conformance Test Suite is not included in this document. Such Suites shall\r\nbe developed by protocol bindings and Application Profiles (see 8.5, ISO/IEC TR 10000-\r\n2:1998) that realize the conformance classes listed herein. An application profile\r\nconsists of a set of metadata elements, policies, and guidelines defined for a particular\r\napplication1.\r\nOGC document number 14-014r3 – HTTP Protocol Binding – Abstract Test Suite is\r\navailable to address conformance with the provisions of OGC document number 12-\r\n176r7 – HTTP Protocol Binding. All annexes to this document are informative." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11442,35 +11410,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-056r10" + "@value": "12-168r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoPose 1.0 Data Exchange Draft Standard" + "@value": "OGC® Catalogue Services 3.0 - General Model" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-152", + "@id": "http://www.opengis.net/def/docs/07-144r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-01-21" + "@value": "2009-02-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Corentin Guillo" + "@value": "Richard Martell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -11480,27 +11448,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=25184" + "@id": "https://portal.ogc.org/files/?artifact_id=31138" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-152" + "@value": "07-144r4" }, { "@language": "en", - "@value": "FedEO Pilot Engineering Report (07-152)" + "@value": "CSW-ebRIM Registry Service - Part 2: Basic extension package" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document was developed during the FedEO - GEO AIP initiative of the OGC. It was contributed by the organizations involved in the Earth Observation and Natural Resources and Environment Domain Working Group (EO/NRE DWG) in the OGC Specification Program. The document describes recommendation for architecture and specification that enables interoperability" + "@value": "Incorporates Corrigendum 1 (OGC 08-102r1)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11511,35 +11479,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-152" + "@value": "07-144r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "FedEO Pilot Engineering Report" + "@value": "CSW-ebRIM Registry Service - Part 2: Basic extension package" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-078r1", + "@id": "http://www.opengis.net/def/docs/08-053r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-07-08" + "@value": "2009-03-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/ts" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -11549,27 +11517,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=29029" + "@id": "https://portal.ogc.org/files/?artifact_id=32888" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-5 ER: GSIP Schema Processing" + "@value": "08-053r2" }, { "@language": "en", - "@value": "08-078r1" + "@value": "WCS Processing Extension (WCPS) Abstract Test Suite" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/ts" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document describes and discusses the OWS-5 enhancements in the process of creating application schemas in support of the NSG from NGA data based on the GEOINT Structure Implementation Profile (GSIP) which has been based on the NSG Application Schema and accompanying NSG Entity Catalog. " + "@value": "" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11580,35 +11548,105 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-078r1" + "@value": "08-053r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-5 ER: GSIP Schema Processing" + "@value": "WCS Processing Extension (WCPS) Abstract Test Suite" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-017r1", + "@id": "http://www.opengis.net/def/doc-type/cs/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Candidate Specification" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Candidate Specification" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/17-014r8" + }, + { + "@id": "http://www.opengis.net/def/docs/17-014r7" + }, + { + "@id": "http://www.opengis.net/def/docs/19-065" + }, + { + "@id": "http://www.opengis.net/def/docs/17-014r5" + }, + { + "@id": "http://www.opengis.net/def/docs/17-002r1" + }, + { + "@id": "http://www.opengis.net/def/docs/21-069r2" + }, + { + "@id": "http://www.opengis.net/def/docs/21-050r1" + }, + { + "@id": "http://www.opengis.net/def/docs/20-072r5" + }, + { + "@id": "http://www.opengis.net/def/docs/20-094" + }, + { + "@id": "http://www.opengis.net/def/docs/17-014r9" + }, + { + "@id": "http://www.opengis.net/def/docs/22-025r4" + }, + { + "@id": "http://www.opengis.net/def/docs/18-053r2" + }, + { + "@id": "http://www.opengis.net/def/docs/20-072r2" + }, + { + "@id": "http://www.opengis.net/def/docs/17-030r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Candidate Specification" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/11-092r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-08-24" + "@value": "2012-04-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff de La Beaujardiere" + "@value": "Johannes Echterhoff, Matthes Rieke" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -11618,27 +11656,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1118" + "@id": "https://portal.ogc.org/files/?artifact_id=46243" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "02-017r1" + "@value": "OWS-8 Report on Digital NOTAM Event Specification" }, { "@language": "en", - "@value": "WMS Part 2: XML for Requests using HTTP Post" + "@value": "11-092r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This part of the Web Map Service (WMS) specification applies to those clients and servers which allow operation request encodings that are more complex than those permitted by the basic keyword/value encoding defined in WMS Part 1 [17]. Part 2 only describes the encoding of the request messages using Extensible Markup Language (XML); all other aspects of the Web Map Service are fully defined in Part 1." + "@value": "This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 8 (OWS-8). It describes the results of the conceptual and schematron rule based validation of the Digital NOTAM Event Specification (DNES). Various conceptual aspects were identified which need clarification and/or revision. Schematron rules were developed for a number of the DNES scenarios. This document contains coverage tables which document normative statements from the DNES and indicate which of them can be tested with existing schematron rules.\r\nSee: http://dp.schemas.opengis.net/11-092r2" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11649,30 +11687,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-017r1" + "@value": "11-092r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "WMS Part 2: XML for Requests using HTTP Post" + "@value": "OWS-8 Report on Digital NOTAM Event Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-012r1", + "@id": "http://www.opengis.net/def/docs/16-056", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-12-17" + "@value": "2017-05-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Benjamin Pross" + "@value": "Jeff Harrison" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -11687,17 +11725,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-012r1.html" + "@id": "https://docs.ogc.org/per/16-056.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Delta Updates Engineering Report" + "@value": "Testbed-12 TopoJSON, GML Engineering Report" }, { "@language": "en", - "@value": "19-012r1" + "@value": "16-056" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -11707,7 +11745,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 15 Engineering Report (ER) documents the design of a service architecture that allows the delivery of prioritized updates of features to a client, possibly acting in a DDIL (Denied, Degraded, Intermitted or Limited Bandwidth) environment. Two different technical scenarios were investigated and tested:\r\n\r\nThe enhancement of Web Feature Service (WFS) instances to support updates on features sets.\r\n\r\nUtilizing a Web Processing Service (WPS) instance to access features, without the need to modify the downstream data service." + "@value": "This OGC document evaluates TopoJSON as an encoding that may be delivered across a common, standard OGC service interface such as WFS." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11718,35 +11756,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-012r1" + "@value": "16-056" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Delta Updates Engineering Report" + "@value": "Testbed-12 TopoJSON, GML Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-100r2", + "@id": "http://www.opengis.net/def/docs/09-082", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-08-16" + "@value": "2009-07-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Scarponcini" + "@value": "Hsu-Chun James Yu, Zhong-Hung Lee, Cai-Fang Ye, Lan-Kun Chung, Yao-Min Fang" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -11756,27 +11794,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=75117" + "@id": "https://portal.ogc.org/files/?artifact_id=34126" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard" + "@value": "Sensor Web Enablement Application for Debris Flow Monitoring System in Taiwan" }, { "@language": "en", - "@value": "16-100r2" + "@value": "09-082" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 0 addresses the Core Requirements Class from LandInfra." + "@value": "This application document describes:\r\n\r\n1)\tWhat is a Debris Flow Monitoring System.\r\n2)\tHow SWE implements in Debris Flow Monitoring System. \r\n3)\tTutorial for SWE developers.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11787,30 +11825,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-100r2" + "@value": "09-082" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard" + "@value": "Sensor Web Enablement Application for Debris Flow Monitoring System in Taiwan" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-021", + "@id": "http://www.opengis.net/def/docs/16-017", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-03-06" + "@value": "2017-04-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Matthes Rieke, Aleksandar Balaban" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -11825,17 +11863,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-021.html" + "@id": "https://docs.ogc.org/per/16-017.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-021" + "@value": "16-017" }, { "@language": "en", - "@value": "Next Generation APIs: Complex Feature Handling Engineering Report" + "@value": "Testbed-12 Asynchronous Messaging for Aviation" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -11845,7 +11883,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OGC Web Feature Service (WFS) 3.0 is a revision of the WFS standard that proposes a modernized service architecture, that follows the current Web architecture, has a focus on the developer experience, supports the OpenAPI specification, and modularizes WFS into building blocks for fine-grained access to spatial data that can be used by an Application Programming Interface (API) for data.\r\n\r\nThis document reviews the work that proposes a next generation of OGC web services (NextGen services or Next Generation APIs) from the perspective of supporting complex three-dimensional (3D) data or complex data schemas. The goal is to identify the best service solution for these particular needs, whether the results are WFS 3.0 extensions or other approaches. In this context the approach of the NextGen services is not of monolithic web services, but Web API building blocks. This is an important point. The same API should be able to support requirements that currently require separate OGC web services, e.g. a WFS and a 3D Portrayal Service (3DPS).\r\n\r\nThe purpose of this work is not to preempt other next-generation discussions taking place in OGC but rather to inform and complement that work.\r\n\r\nThe report includes proposals on how to extend the NextGen service architecture with API building blocks for complex data, complex queries and 3D portrayal. WFS 3.0, Part 1, is used as the starting point for the NextGen service architecture. The proposals are based on existing requirements and use cases as well as existing support for developers to simplify implementation.\r\n\r\nThe work has found no general issues with migrating current WFS, 3DPS, Web Map Tile Service (WMTS) and Web Map Service (WMS) capabilities to the NextGen architecture. On the contrary, the NextGen approach improves the consistency of the interface and removes redundancies (e.g., between the feature access in WFS and the feature info requests in the other standards)." + "@value": "The Asynchronous Messaging for Aviation Engineering Report (ER) focuses on the design of an architecture to create an Publish/Subscribe (PubSub) messaging layer between different Aviation components such as clients, data provider instances and Data Brokers. In order to achieve interoperability among these components, the OGC PubSub 1.0 standard forms the basis of this architecture. The design of this architecture will cover methods for subscribing for specific subsets of data (e.g. Flight Information Exchange Model (FIXM) Flights intersecting a given Airspace), managing such subscriptions as well as publishing data to the Asynchronous Messaging Server. Different delivery methods such as Advanced Message Queuing Protocol (AMQP) 1.0, Java Message Service (JMS) and OASIS WS-Notification are considered. In particular, their harmonization with OGC PubSub 1.0 is evaluated.\r\n\r\nThis report focuses on the interface design required to define an interoperable approach for Aviation using this OGC PubSub 1.0. Specific service level integrations (i.e., Federal Aviation Administration (FAA) System-Wide Information Management (SWIM) and Single European Sky ATM Research Programme (SESAR) SWIM) have been investigated but an implementation has not been fulfilled." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11856,35 +11894,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-021" + "@value": "16-017" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14 Next Generation APIs: Complex Feature Handling Engineering Report" + "@value": "Testbed-12 Asynchronous Messaging for Aviation" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-072r2", + "@id": "http://www.opengis.net/def/docs/19-078r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-01-25" + "@value": "2020-10-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Wenny Rahayu, Torab Torabi, Andrew Taylor-Harris, Florian Puersch" + "@value": "Joseph Abhayaratna, Linda van den Brink, Nicholas Car, Rob Atkinson, Timo Homburg, Frans Knibbe, Kri" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -11894,27 +11932,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46322" + "@id": "https://docs.ogc.org/wp/19-078r1/19-078r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-8 Aviation - WXXM Engineering Report" + "@value": "OGC Benefits of Representing Spatial Data Using Semantic and Graph Technologies" }, { "@language": "en", - "@value": "11-072r2" + "@value": "19-078r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC™ document specifies the advancement of WXXM and Weather Concepts in\r\nthe OWS-8 Aviation Thread. The focus is on investigating and demonstrating the\r\napplicability and suitability of WXXM in producing accurate, real-time aircraft weather\r\nradar data using OGC™ Web Coverage Services (WCS) to be used by meteorological\r\napplications and services supporting aviation. Such applications provide information\r\nwhich enhances safe and efficient tactical and" + "@value": "This paper does four things. Firstly, it describes the benefits of representing geospatial data using semantics, graph, and web technologies. Secondly, it gives an overview of the current capabilities of the GeoSPARQL standard, showing that many benefits of semantic and graph technologies are already within reach. Thirdly, it outlines some shortcomings of the existing GeoSPARQL implementation specification that, if addressed, would unlock its potential to a greater extent, and could significantly increase its user base. Finally, it identifies other related activities that are current at the time of editing this paper. In doing so, it establishes liaison’s between the different activities in an attempt to achieve alignment.\r\n\r\nThe purpose of this paper is to provoke further thought about a best course for further development of the GeoSPARQL standard, and to invite active involvement in that development. Particularly, the involvement of people and organizations that until now have not been able to put GeoSPARQL to good use, either because of perceived limitations or because of unfamiliarity with the standard, will be highly valued. Also, since one development under consideration is to make provisions for use of GeoSPARQL with non-geographic spatial data, those that see opportunities for using spatial data in a broad sense together with the aforementioned technologies are cordially invited to share their views." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11925,35 +11963,45 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-072r2" + "@value": "19-078r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 Aviation - WXXM Engineering Report" + "@value": "OGC Benefits of Representing Spatial Data Using Semantic and Graph Technologies" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-029", + "@id": "http://www.opengis.net/def/docs/11-122r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-10-22" + "@value": "2012-02-17" + }, + { + "@type": "xsd:date", + "@value": "2011-11-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Timothy Miller, Gil Trenum, Josh Lieberman" + "@value": "Jeff Harrison, Panagiotis (Peter) A. Vretanos" + }, + { + "@value": "Panagiotis (Peter) A. Vretanos, Jeff Harrison" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" + }, + { + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -11963,27 +12011,37 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-029.html" + "@id": "https://portal.ogc.org/files/?artifact_id=46964" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "3D Data Container Engineering Report" + "@value": "11-122r1" }, { "@language": "en", - "@value": "20-029" + "@value": "Gazetteer Service - Application Profile of the Web Feature Service Best Practice" + }, + { + "@language": "en", + "@value": "Gazetteer Service - Application Profile of the Web Feature Service Candidate Implementation Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report documents the goals, activities, experiences, and outcomes of the 3D Data Container and Tiles API Pilot. Participants in the Pilot cooperatively defined a GeoVolume (3D Geospatial Volume) resource and developed a GeoVolumes API based on the concept to provide access to different 2D and 3D geospatial dataset distributions organized by region of interest. Multiple client and server implementations of the GeoVolumes API successfully carried out technology interchange experiments that demonstrated the value of the API for improving interoperability between 3D geospatial data formats." + "@value": "This document defines a Gazetteer Service profile of the OGC Web Feature Service Standard. The OGC Gazetteer Service allows a client to search and retrieve elements of a georeferenced vocabulary of well-known place-names.\r\nThis profile extends the WFS interface in a way that a client is able to\r\n–\tDetermine if a WFS implementation is acting as a Gazetteer Service. \r\n–\tQuery the Gazetteer Service in order to retrieve place-name features without closer examination of the feature type definitions\r\n–\tAccess metadata about the gazetteer(s) provided by the service\r\n–\tUpdate place-name features using WFS transactions\r\n–\tFetch place-name features that have Parent-Child relationships and then follow those links\r\n" + }, + { + "@value": "Web Feature Service (WFS-G). Services compliant with this standard shall provide Location Instances derived from SI_LocationInstance. In Addition, they may support queries based on the (parent/child) relationships of feature instances, as defined in ISO 19112." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -11994,35 +12052,39 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-029" + "@value": "11-122r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "3D Data Container Engineering Report" + "@value": "Gazetteer Service - Application Profile of the Web Feature Service Best Practice" + }, + { + "@language": "en", + "@value": "Gazetteer Service - Application Profile of the Web Feature Service Candidate Implementation Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-014r8", + "@id": "http://www.opengis.net/def/docs/07-063", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-12-15" + "@value": "2007-08-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed, Tamrat Belayneh" + "@value": "Thomas H.G. Lankester" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12032,27 +12094,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/17-014r8/17-014r8.html" + "@id": "https://portal.ogc.org/files/?artifact_id=21742" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.2" + "@value": "07-063" }, { "@language": "en", - "@value": "17-014r8" + "@value": "Web Map Services - Application Profile for EO Products" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Indexed 3D Scene Layer (I3S) format is an open 3D content delivery format used to rapidly stream and distribute large volumes of 3D GIS data to mobile, web and desktop clients. I3S content can be shared across enterprise systems using both physical and cloud servers.\r\n\r\nA single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files.\r\n\r\nThe delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types.\r\n\r\nThe open community GitHub source for this Community Standard is here." + "@value": "This OGC document specifies a constrained, consistent interpretation of the WMS specification that is applicable to government, academic and commercial providers of EO products. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12063,35 +12125,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-014r8" + "@value": "07-063" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.2" + "@value": "Web Map Services - Application Profile for EO Products" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-026r2", + "@id": "http://www.opengis.net/def/docs/16-003r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-02-23" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus, Jan Herrmann" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12101,27 +12163,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=25218" + "@id": "https://docs.ogc.org/bp/16-003r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geospatial eXtensible Access Control Markup Language (GeoXACML)" + "@value": "Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values" }, { "@language": "en", - "@value": "07-026r2" + "@value": "16-003r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Geospatial eXtensible Access Control Markup Language Encoding Standard (GeoXACML) defines a geospatial extension to the OASIS standard “eXtensible Access Control Markup Language (XACML)” [www.oasis-open.org/committees/xacml/]. This extension incorporates spatial data types and spatial authorization decision functions based on the OGC Simple Features[http://www.opengeospatial.org/standards/sfa] and GML[http://www.opengeospatial.org/standards/gml] standards. GeoXACML is a policy language that supports the declaration and enforcement of access rights across jurisdictions and can be used to implement interoperable access control systems for geospatial applications such as Spatial Data Infrastructures. GeoXACML is not designed to be a rights expression language and is therefore not an extension of the OGC GeoDRM Reference Model (Topic 18 in the OpenGIS® Abstract Specification [http://www.opengeospatial.org/standards/as]). " + "@value": "This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids key words." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12132,55 +12194,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-026r2" + "@value": "16-003r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geospatial eXtensible Access Control Markup Language (GeoXACML)" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/ts", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/08-069r2" - }, - { - "@id": "http://www.opengis.net/def/docs/08-103r2" - }, - { - "@id": "http://www.opengis.net/def/docs/14-014r3" - }, - { - "@id": "http://www.opengis.net/def/docs/07-134r2" - }, - { - "@id": "http://www.opengis.net/def/docs/08-053r2" + "@value": "Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-064", + "@id": "http://www.opengis.net/def/docs/03-013", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-01-10" + "@value": "2003-01-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12190,27 +12232,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-064.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1338" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Disaster Pilot 2021 Engineering Report" + "@value": "Web Object Service Implementation Specification" }, { "@language": "en", - "@value": "21-064" + "@value": "03-013" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Disaster Pilot ’21 (DP21) Engineering Report summarizes work done in the Pilot to increase disaster awareness among a range of disaster management stakeholders. Pilot participants implemented components of a data flow ecosystem to leverage analysis-ready earth observations and other datasets (ARD) and produce decision ready indicators (DRI) according to collaboratively developed workflow recipes. DP21 focused on the hazards of flooding, landslides, and pandemic, as well as the interactions and complications between them, in three regions including the Piura and Rimac river basins in Peru; the Red River Basin in Manitoba, Canada; and the greater New Orleans area in Louisiana, United States. The Pilot also prototyped providing information to field practitioners in secure geopackage formats, as well as leveraging linked data and structured web page information to optimize public web searches for disaster information." + "@value": "There is a requirement to manage many different types of objects. These include styles, symbols and images. To satisfy this requirement, a repository interface is required. The intent of the Web Object Service interface is to provide a means to define this interface." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12221,35 +12263,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-064" + "@value": "03-013" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Disaster Pilot 2021 Engineering Report" + "@value": "Web Object Service Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-032", + "@id": "http://www.opengis.net/def/docs/07-118r8", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-10-22" + "@value": "2010-09-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Chris Little, Peng Yue, Steve Olson" + "@value": "P Denis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12259,27 +12301,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-032.html" + "@id": "https://portal.ogc.org/files/?artifact_id=40677" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-032" + "@value": "07-118r8" }, { "@language": "en", - "@value": "OGC API - Environmental Data Retrieval Sprint Engineering Report" + "@value": "User Management for Earth Observation Services" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The subject of this Engineering Report (ER) is a development Sprint that was held from March 18-20, 2020 to advance the Open Geospatial Consortium (OGC) Environmental Data Retrieval (EDR) Application Programming Interface (API) candidate standard. Due to the widespread of the virus, the Sprint was held virtually by using GoToMeeting teleconferencing facilities of OGC, email and GitHub." + "@value": "This document describes how user and identity management information may be included in the protocol specifications for OGC Services. The use cases addressed will make reference to EO (Earth Observation) services, for example catalogue access (EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 [OGC 06-131]), ordering (Ordering Services for Earth Observation Products [OGC 06-141r2]) and programming (OpenGIS Sensor Planning Service Application Profile for EO Sensors [OGC 07-018r2]). " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12290,35 +12332,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-032" + "@value": "07-118r8" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Environmental Data Retrieval Sprint Engineering Report" + "@value": "User Management for Earth Observation Services" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-078", + "@id": "http://www.opengis.net/def/docs/11-169", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-17" + "@value": "2011-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Harrison" + "@value": "Simon Jirka, Christoph Stasch, Arne Bröring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12328,27 +12370,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-078.html" + "@id": "https://portal.ogc.org/files/?artifact_id=46693" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-078" + "@value": "11-169" }, { "@language": "en", - "@value": "Concepts of Data and Standards for Mass Migration Engineering Report" + "@value": "Lightweight SOS Profile for Stationary In-Situ Sensors Discussion Paper" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The objective of the Mass Migration Source Integration effort in OGC Testbed 13 was to understand and document how interoperability tools and practices, including open geospatial and security standards, can enable information exchange on an international level for humanitarian relief and analysis of mass movement of populations.\r\n\r\nThis Engineering Report describes how Testbed 13 participants tested and demonstrated situational awareness using Internet and web technologies in a shared information exchange platform. The purpose of this platform was to help realize a Common Operational Picture (COP) for coordinating humanitarian relief activities among nations and organizations. In addition, the platform exercised security-enabled interoperable exchange of messages.\r\n\r\n" + "@value": "This Discussion Paper describes a lightweight SOS 2.0 profile for stationary in-situ sensors. Besides the SOS itself this document also addresses the data formats used by the SOS: Observations & Measurements 2.0 (O&M) for encoding measurement data and the Sensor Model Language 2.0 (SensorML) for encoding metadata. Other SWE standards which provide more specialized functionality are not part of this minimum lightweight SWE profile.\r\nThe aim of this document is to present a common minimum profile of the SOS. The profile is intended to reduce the complexity of the standard by omitting highly specific elements that are not necessary for the majority of use cases that occur in practice. At the same time, the profile is designed in such a way that all SOS implementations that conform to this profile are also compliant to the according OGC specifications." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12359,35 +12401,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-078" + "@value": "11-169" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: Concepts of Data and Standards for Mass Migration Engineering Report" + "@value": "Lightweight SOS Profile for Stationary In-Situ Sensors Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-037r1", + "@id": "http://www.opengis.net/def/docs/17-048", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-10-29" + "@value": "2017-08-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Josh Lieberman, Andy Ryan" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12397,27 +12439,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/18-037r1/18-037r1.html" + "@id": "https://docs.ogc.org/per/17-048.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GeoPackage / OWS Context Harmonization Discussion Paper" + "@value": "17-048" }, { "@language": "en", - "@value": "18-037r1" + "@value": "Underground Infrastructure Concept Study Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC discussion paper presents an approach to harmonize the OGC GeoPackage and OWS Context standards through a set of extensions. GeoPackage is an open, standards-based, platform-independent, portable, self-describing, compact format for storing and transferring geospatial data and information as part of an SQLite database. OWS Context is an open format linking geospatial web services and information. A draft standard has been produced and this Discussion Paper is designed to be a companion to that draft standard to assist in discussion. The draft standard contains extensions to both GeoPackage and OWS Context.\r\n\r\nThis document is the work of collaboration between the GeoPackage and OWS Context Standards Working Groups (SWGs)." + "@value": "This report documents the progress made to date by OGC and its members to build a complete picture of the present situation and develop a conceptual framework for action to improve underground infrastructure data interoperability. The report also identifies the most important steps to be taken next in order to develop the necessary data standards and foster their adoption." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12428,35 +12470,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-037r1" + "@value": "17-048" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GeoPackage / OWS Context Harmonization Discussion Paper" + "@value": "OGC Underground Infrastructure Concept Study Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-041", + "@id": "http://www.opengis.net/def/docs/14-121r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-02-22" + "@value": "2016-12-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stefano Cavazzi" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12466,27 +12508,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-041.html" + "@id": "https://portal.ogc.org/files/?artifact_id=72295" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-13: Vector Tiles Engineering Report" + "@value": "14-121r2" }, { "@language": "en", - "@value": "17-041" + "@value": "Web Query Service " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Open Geospatial Consortium (OGC) Engineering Report (ER) captures the requirements, solutions, and implementation experiences of the Vector Tiling work package in OGC Testbed-13 [Available at: http://www.opengeospatial.org/projects/initiatives/testbed13]. This ER describes the evaluation of existing vector tiling solutions. The evaluation was used to define a conceptual model that integrates elements from different approaches to vector tiling. This is followed by an overview of how the developed implementation integrates vector tiles containing World Geodetic System 1984 (WGS84), European Terrestrial Reference System 1989 (ETRS89) and British National Grid projection data, standards based tile schemas and moving features. Best practice guidelines for the use of Symbology Encoding (SE) and Styled Layer Descriptor (SLD) are also provided ensuring the service is optimized for analysis and low-bandwidth networks. The report concludes with an investigation on how existing OGC services may be extended with the necessary capabilities enabling the full range of geometry types and tiling strategies to support vector tiling." + "@value": "This OGC Web Query Service (WQS) defines a service interface for retrieving any kind of subset of information provided by the server addressed. WQS is com¬pletely agnostic of any semantics and, therefore, not bound to any predefined structures, such as coordinates, fea-tures, coverages, or metadata. This makes WQS particularly suitable for retrieval from heter-ogeneous data offerings combining features, coverages, and catalog information in some ap-plication-defined way. A second use case is selective retrieval from a Capabilities document to avoid downloading large such documents and performing extraction on client side.\r\nTo this end, the Query request type is defined which, based on an XPath expression as input, extracts the matching information from the service’s offering and returns it (currently: as an XML document).\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12497,35 +12539,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-041" + "@value": "14-121r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: Vector Tiles Engineering Report" + "@value": "OGC® Web Query Service " } ] }, { - "@id": "http://www.opengis.net/def/docs/17-043", + "@id": "http://www.opengis.net/def/docs/08-009r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-08" + "@value": "2008-02-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Nuno Oliveira" + "@value": "Bastian Schaeffer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12535,27 +12577,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-043.html" + "@id": "https://portal.ogc.org/files/?artifact_id=26521" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-043" + "@value": "08-009r1" }, { "@language": "en", - "@value": "Testbed-13: Executable Test Suites and Reference Implementations for NSG WMTS 1.0 and WFS 2.0 Profiles with Extension" + "@value": "OWS 5 SOAP/WSDL Common Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) describes the development of the compliance tests and implementation in GeoServer of the Web Feature Service (WFS) 2.0 and Web Map Tile Service (WMTS) 1.0 National System for Geospatial Intelligence (NSG) profiles. The NSG of the United States (US) National Geospatial Intelligence Agency (NGA) is the combination of technologies, policies, capabilities, doctrine, activities, people, data and communities needed to produce geospatial intelligence (GEOINT) in an integrated, multi-intelligence, multi-domain environment. The work can be grouped into four main topics:\r\n\r\ncritical review of the NSG profiles for WFS 2.0 and WMTS 1.0\r\n\r\nimplementation of the profiles in GeoServer\r\n\r\nvalidation of the implementation using OGC Compliance tests and tools\r\n\r\nlessons learn during the implementation of these profiles and their validation\r\n\r\nBoth NSG profiles are Class 2 profiles. WMTS profiles OGC WMTS 1.0. WFS profiles the DGIWG Profile of OGC WFS 2.0. The first topic provides a review of these profiles along with a description of the main extensions and restrictions introduced by them.\r\n\r\nThe second topic covers the implementation of the NSG profiles in GeoServer. It describes the software architecture and technical decisions, along with the deployment and configuration of the server.\r\n\r\nThe third topic covers the validation process of the implementation using OGC validation (sometimes referred to as CITE) tests and tools. It also covers how the tests can be run and how to configure GeoServer for these tests.\r\n\r\nThe last topic contains an evaluation of the work, reached goals, lessons learned and the best practices that can be applied in future work." + "@value": "This OGC document reports the results achieved in the OWS5 GPW-SOAP/WSDL thread which is focused on creating general recommendations and guidelines for WSDL/SOAP support to existing OGC Web Services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12566,35 +12608,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-043" + "@value": "08-009r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: Executable Test Suites and Reference Implementations for NSG WMTS 1.0 and WFS 2.0 Profiles with Extension" + "@value": "OWS 5 SOAP/WSDL Common Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-025r2", + "@id": "http://www.opengis.net/def/docs/03-026", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-08-19" + "@value": "2003-01-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff" + "@value": "Joshua Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12604,27 +12646,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=63793" + "@id": "https://portal.ogc.org/files/?artifact_id=1319" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-025r2" + "@value": "Service Information Model" }, { "@language": "en", - "@value": "Testbed 11 Aviation - Architecture Engineering Report" + "@value": "03-026" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document describes the architecture implemented in the OGC Testbed 11 Aviation thread." + "@value": "SIM specifies and discusses a common information model for OGC Web Services, also known variously or in part as service capabilities or service metadata." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12635,35 +12677,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-025r2" + "@value": "03-026" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 11 Aviation - Architecture Engineering Report" + "@value": "Service Information Model" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-103r1", + "@id": "http://www.opengis.net/def/docs/10-189r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-09-27" + "@value": "2012-06-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Simon Cox" + "@value": "Frédéric Houbie; Fabian Skivee" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pol-nts" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12673,27 +12715,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/pol/10-103r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=47409" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-103r1" + "@value": "10-189r2" }, { "@language": "en", - "@value": "OGC Name Type Specification - specification elements" + "@value": "Cataloguing Earth Observation Products for ebXML Registry Information Model 3.0 based Catalogues" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pol-nts" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The mission of the OGC Naming Authority (OGC-NA) is to provide the means through which OGC resources such as OGC documents, namespaces and ontologies can be controlled and managed such that they can provide clear and well-defined names and definitions. In the terminology defined in ISO 19135, OGC-NA is the Control Body for the register of OGC Names. This document specifies a rule for constructing OGC names that may be used for identifying specification elements defined in the OGC Specification Model – Modular Specification." + "@value": "This OGC® document specifies the Earth Observation Products Extension Package for ebXML Registry Information Model 3.0, based on the [OGC 10-157r1] Earth Observation Metadata profile of Observations and Measurements.\r\nIt enables CSW-ebRIM catalogues to handle a variety of metadata pertaining to earth observation p/roducts as defined in [OGC 10-157r1].\r\nThis proposed application profile document describes model and encodings required to discover, search and present metadata from catalogues of Earth Observation products. The profile presents a minimum specification for catalogue interoperability within the EO domain, with extensions for specific classes of metadata.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12704,35 +12746,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-103r1" + "@value": "10-189r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Name Type Specification - specification elements" + "@value": "Cataloguing Earth Observation Products for ebXML Registry Information Model 3.0 based Catalogues" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-008", + "@id": "http://www.opengis.net/def/docs/14-004r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-04-12" + "@value": "2014-10-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Angelos Tzotsos, Tom Kralidis, Martin Desruisseaux" + "@value": "Volker Andres, Simon Jirka , Michael Utech" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12742,27 +12784,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-008.html" + "@id": "https://docs.ogc.org/bp/14-004r1/14-004r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Joint OGC OSGeo ASF Code Sprint 2021 Summary Engineering Report" + "@value": "Sensor Observation Service 2.0 Hydrology Profile" }, { "@language": "en", - "@value": "21-008" + "@value": "14-004r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from 17 to 19 February 2021 to advance support of open geospatial standards within the developer community, whilst also advancing the standards themselves. The code sprint was hosted by the Open Geospatial Consortium (OGC), the Apache Software Foundation (ASF), and Open Source Geospatial Foundation (OSGeo). The event was sponsored by Ordnance Survey (OS) and GeoCat BV, and held as a completely virtual event." + "@value": "This OGC document defines an OGC Sensor Observation Service (SOS) 2.0 hydrology profile for SOS 2.0 implementations serving OGC WaterML 2.0. The development of this OGC Best Practice (BP) is based on previous activities and results (i.e. Hydrology Interoperability Experiments[1] as well as the European FP7 project GEOWOW[2]). The work is guided by the need to overcome semantic issues between different SOS instances serving hydrological data and the related client applications. Therefore, this profile focuses on how to use the entities and requests of the standards and defines the necessary technical details to implement the hydrology SOS profile." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12773,35 +12815,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-008" + "@value": "14-004r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Joint OGC OSGeo ASF Code Sprint 2021 Summary Engineering Report" + "@value": "OGC® Sensor Observation Service 2.0 Hydrology Profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-040", + "@id": "http://www.opengis.net/def/docs/10-036r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-09-16" + "@value": "2010-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "Stan Tillman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-orm" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12811,27 +12853,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=3836" + "@id": "https://portal.ogc.org/files/?artifact_id=40313" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Reference Model" + "@value": "OWS-7 Motion Video Change Detection" }, { "@language": "en", - "@value": "03-040" + "@value": "10-036r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-orm" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The ORM describes a framework for the ongoing work of the Open Geospatial Consortium and our specifications and implementing interoperable solutions and applications for geospatial services, data, and applications." + "@value": "This Engineering Report documents the development effort to build a Web Processing Service (WPS) to perform a change detection algorithm on two motion video streams. It will examine the WPS Motion Video Change Detection architecture from various viewpoints in order to describe its purpose, data models, functional decomposition, and interaction between distinct computational components. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12842,35 +12884,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-040" + "@value": "10-036r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Reference Model" + "@value": "OWS-7 Motion Video Change Detection" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-095", + "@id": "http://www.opengis.net/def/docs/06-141r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2007-08-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "James Gallagher, Peter Baumann" + "@value": "Daniele Marchionni" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12880,27 +12922,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=52783" + "@id": "https://portal.ogc.org/files/?artifact_id=22114" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-9 Innovation - Coverages: Coverage Access (OPeNDAP) Study" + "@value": "06-141r2" }, { "@language": "en", - "@value": "12-095" + "@value": "Ordering Services for Earth Observation Products" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document represents the OWS-9 OWS Innovations Coverage Access Study\r\nEngineering Report. It contributes knowledge based on the experience prototyping the\r\nWCS 2.0 Service – Access Innovations component, established in close collaboration\r\nwith the OPeNDAP group. To this end, accessing a variety of coverage data types\r\nconsidering WCS 2.0 and DAP 2.0 interfaces have been implemented and demonstrated.\r\nThe final result is a WCS 2.0 interface for the DAP 2.0 suite." + "@value": "This best practices document describes a profile to order Earth Observation data products. This document expands on the work presented in Best Practices for Earth Observation Products OGC-05-057r4, separating the order services from the catalogue services which are now presented in 06-079. The final goal being to agree to a coherent set of interfaces for ordering of EO products to support access to data from heterogeneous systems dealing with derived data products from satellite based measurements of the earth's surface and environment. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12911,35 +12953,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-095" + "@value": "06-141r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-9 Innovation - Coverages: Coverage Access (OPeNDAP) Study" + "@value": "Ordering Services for Earth Observation Products" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-002", + "@id": "http://www.opengis.net/def/docs/10-194r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-04-29" + "@value": "2011-03-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Rushforth" + "@value": "Boyan Brodaric, Nate Booth" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -12949,27 +12991,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=26610" + "@id": "https://portal.ogc.org/files/?artifact_id=43545" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CGDI WFS and GML Best Practices" + "@value": "Groundwater Interoperability Experiment FINAL REPORT" }, { "@language": "en", - "@value": "08-002" + "@value": "10-194r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document gives guidelines and recommendations for administrators, users and implementers of Web Feature Services serving Geography Markup Language encoded response documents. " + "@value": "This report describes the methods, results, issues and recommendations generated by the\r\nGroundwater Interoperability Experiment (GWIE). As an activity of the OGC Hydrology\r\nDomain Working Group (HDWG), the GWIE is designed to: (1) test the use of\r\nWaterML2 with the SOS interface, and Groundwater ML (GWML) with the WFS\r\ninterface, (2) test compatibility with software clients, and (3) facilitate sharing of massive\r\nvolumes of sensor-based water level observations and related water well features across\r\nthe Canada and United States border. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -12980,35 +13022,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-002" + "@value": "10-194r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Canadian Geospatial Data Infrastructure WFS and GML Best Practices" + "@value": "OGC® Groundwater Interoperability Experiment FINAL REPORT" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-032r2", + "@id": "http://www.opengis.net/def/docs/17-020r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-03-06" + "@value": "2018-01-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Boyan Brodaric" + "@value": "Johannes Echterhoff, Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -13018,27 +13060,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/16-032r2/16-032r2.html" + "@id": "https://docs.ogc.org/per/17-020r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-032r2" + "@value": "17-020r1" }, { "@language": "en", - "@value": "WaterML 2: Part 4 – GroundWaterML 2 (GWML2)" + "@value": "Testbed-13: NAS Profiling Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard describes a conceptual and logical model for the exchange of groundwater data, as well as a GML/XML encoding with examples." + "@value": "The National System for Geospatial-Intelligence (NSG) Application Schema (NAS) is an ISO 19109 compliant application schema that defines the conceptual model for identifying and encoding feature data in the U.S. National System for Geospatial-Intelligence (NSG). NGA utilizes the open source software tool ShapeChange as an integral piece in NAS development. This tool is used to take NAS-based UML models and create Extensible Markup Language (XML) and Resource Description Framework (RDF) based schemas. Testbed-12 began development of capabilities for extracting profiles supporting specific mission functions from the full NAS content. Testbed-13 further refined the approach to NAS Profiling by investigating how a specific profile (Urban Military Profile) can be processed in an automated way and used to derive implementation schemas for the OGC standards CDB and CityGML.\r\n\r\nThis OGC Engineering Report describes:\r\n\r\nThe specification of a NAS-based Military Urban Profile as a Unified Modeling Language (UML) model (chapter 5);\r\n\r\nHow mission-specific sub-profiles can be specified and maintained using ShapeChange and the new ShapeChange Profile Management Tool (chapter 6); and\r\n\r\nHow the model and profile information are processed to derive output for\r\n\r\na CDB data store (chapter 7, chapter 8) and\r\n\r\na CityGML Application Domain Extension (chapter 9).\r\n\r\nThis work provides insights into:\r\n\r\nThe requirements and constraints on managing profiles of complex ISO 19109 compliant application schemas such as the NAS; and\r\n\r\nUsing a model-driven approach to generate implementation schemas of an ISO 19109 compliant application schema profile for different environments.\r\n\r\nThe target audience of this document is anyone interested in these topics. The implementation environments discussed in this report are the OGC standards CDB and CityGML. The profiled application schema is the NAS.\r\n\r\nThis report assumes that readers are familiar with the key concepts and technologies discussed in this document. This document does not provide an introduction to them, but the table below provides a brief summary and pointers to more information." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13049,35 +13091,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-032r2" + "@value": "17-020r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC WaterML 2: Part 4 – GroundWaterML 2 (GWML2)" + "@value": "OGC Testbed-13: NAS Profiling Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-030r1", + "@id": "http://www.opengis.net/def/docs/09-034", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-03-01" + "@value": "2009-07-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "ASPRS" + "@value": "Genong (Eugene) Yu, Liping Di" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -13087,27 +13129,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=74523" + "@id": "https://portal.ogc.org/files/?artifact_id=33925" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "LAS Specification 1.4 OGC Community Standard" + "@value": "09-034" }, { "@language": "en", - "@value": "17-030r1" + "@value": "OWS-6 Georeferencable Imagery Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The LAS file is intended to contain LIDAR (or other) point cloud data records. The data will\r\ngenerally be put into this format from software (e.g. provided by LIDAR hardware vendors) which\r\ncombines GPS, IMU, and laser pulse range data to produce X, Y, and Z point data. The intention\r\nof the data format is to provide an open format that allows different LIDAR hardware and software\r\ntools to output data in a common format.\r\nThis document reflects the fourth revision of the LAS format specification since its initial version\r\n1.0 release." + "@value": "This document discusses considerations about and recommendations for approaches for georeferenceable imagery under the Sensor Web Enablement thread during OGC Web Services Phase 6. This is an extension to the work described in the previous engineering report number OGC 08-071 . Georeferencealbe imagery is “a referenceable grid that has information that can be used to transform grid coordinates to external coordinates, but the transformation shall not be required to be an affine transformation”. Geolocation of georeferenceable imagery refers to the techniques described in ISO 19130, such as sensor models, functional fit models, and spatial registration using control points." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13118,35 +13160,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-030r1" + "@value": "09-034" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "LAS Specification 1.4 OGC Community Standard" + "@value": "OWS-6 Georeferencable Imagery Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-139r3", + "@id": "http://www.opengis.net/def/docs/10-132", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-01-17" + "@value": "2010-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Demmy, Carl Reed" + "@value": "Bruno Simmenauer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -13156,27 +13198,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40537" + "@id": "https://portal.ogc.org/files/?artifact_id=40149" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "PDF Geo-registration Encoding Best Practice Version 2.2" + "@value": "OWS-7 Aviation - WXXM Assessment Engineering Report" }, { "@language": "en", - "@value": "08-139r3" + "@value": "10-132" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The intended audience of this document is a developer of software for creating and consuming geo=registered PDF documents that conform to PDF geo-registration 2.2. It specifies how to create the necessary PDF objects that identify a region of the PDF page as a map and describe the map’s coordinate systems. Map creation and rendering to a PDF page are not addressed. The underlying PDF file format is not addressed. The file format is specified in PDF Reference[1] ." + "@value": "The document describes the results of using OGC Web Services for accessing and using WXXM data, notably within aviation scenarios involving rerouting procedures motivated by the sudden closure of airspace areas caused by the eruption of a volcano. The focus of this document will be to evaluate the ability to encode and serve associated operational data with WXXM 1.1.1." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13187,35 +13229,43 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-139r3" + "@value": "10-132" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "PDF Geo-registration Encoding Best Practice Version 2.2" + "@value": "OWS-7 Aviation - WXXM Assessment Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-026r2", + "@id": "http://www.opengis.net/def/doc-type/is-draft", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/21-056r10" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/07-006r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-08-18" + "@value": "2007-04-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Doug Nebert, Arliss Whiteside, Peter Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -13225,27 +13275,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/09-026r2/09-026r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=20555" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-026r2" + "@value": "Catalogue Service Implementation Specification" }, { "@language": "en", - "@value": "Filter Encoding 2.0 Encoding Standard - With Corrigendum " + "@value": "07-006r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A fundamental operation performed on a set of data or resources is that of querying in order to obtain a subset of the data which contains certain desired information that satisfies some query criteria and which is also, perhaps, sorted in some specified manner.\r\n\r\nThis International Standard defines an abstract component, named AbstractQueryExpression, from which other specifications can subclass concrete query elements to implement query operations. This International Standard also defines an additional abstract query component, named AbstractAdhocQueryExpresison, which is derived from AbstractQueryExpression and from which other specifications can subclass concrete query elements which follow a query pattern composed of a list of resource types to query, a projection clause specifying the properties of those resources to present in the result, a projection clause composed of predicates that define the subset of resources or data in the result set and a sorting clause indicating to order in which the results should be presented. This pattern is referred to as an ad hoc query pattern since the server is not aware of the query until it is submitted for processing. This is in contrast to a stored query expression, which is stored and can be invoked by name or identifier.\r\n\r\nThis International Standard describes an XML and KVP encoding of a system-neutral syntax for expressing the projection, selection and sorting clauses of a query expression. The intent is that this neutral representation can be easly validated, parsed and then translated into some target query language such as SPARQL or SQL for processing." + "@value": "The OpenGIS® Catalogue Services Interface Standard (CAT) supports the ability to publish and search collections of descriptive information (metadata) about geospatial data, services and related resources. Providers of resources use catalogues to register metadata that conform to the provider's choice of an information model; such models include descriptions of spatial references and thematic information. Client applications can then search for geospatial data and services in very efficient ways. \r\nSee also the OGC Catalogue 2.0 Accessibility for OWS-3 Discussion Paper [http://www.opengeospatial.org/standards/dp], the OWS-4 CSW ebRIM Modelling Guidelines Interoperability Program Report (IPR) [www.opengeospatial.org/standards/dp] and the OpenGIS® Catalogue Service Interface Standard 2.0.1 - FGDC CSDGM Application Profile for CSW (Best Practice) [http://www.opengeospatial.org/standards/bp].\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13256,58 +13306,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-026r2" + "@value": "07-006r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Filter Encoding 2.0 Encoding Standard - With Corrigendum " - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/pol-nts", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/10-103r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-081" - }, - { - "@id": "http://www.opengis.net/def/docs/09-048r5" - }, - { - "@id": "http://www.opengis.net/def/docs/20-059r4" - }, - { - "@id": "http://www.opengis.net/def/docs/09-047r3" - }, - { - "@id": "http://www.opengis.net/def/docs/18-042r4" + "@value": "OpenGIS Catalogue Service Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-031r1", + "@id": "http://www.opengis.net/def/docs/16-011r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-16" + "@value": "2017-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas Everding" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -13317,27 +13344,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34118" + "@id": "https://portal.ogc.org/files/?artifact_id=72719" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-031r1" + "@value": "16-011r3" }, { "@language": "en", - "@value": "OWS-6 SWE Information Model Engineering Report" + "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document is an OGC Engineering Report for the “Harmonization of SWE Information Models” activity within the OWS-6 SWE thread.\r\nThe document discusses relations between OGC standards SensorML, SWE Common and GML and investigates solutions for increased synergy between these standards. This activity also created UML models of the data types used in SWE and GML.\r\nThis report shows how UncertML can be integrated into different SWE encodings, namely SWE Common and Observations and Measurements.\r\nThis report further discusses the integration of MathML and EML into the SWE environment with an emphasis on SensorML processes and processing.\r\nThis document does not discuss the SWE information model related aspects of catalog entries for sensor services and discovery. This topic is covered in a separate Engineering Report.\r\n" + "@value": "Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames. \r\nIn previous versions of the CDB standard, this CDB volume was Appendix K in CDB Version 3.2 as submitted to the OGC.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13348,35 +13375,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-031r1" + "@value": "16-011r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 SWE Information Model Engineering Report" + "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance" } ] }, { - "@id": "http://www.opengis.net/def/docs/00-115", + "@id": "http://www.opengis.net/def/docs/01-035", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2000-04-24" + "@value": "2001-03-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman, Arliss Whiteside" + "@value": "Jeff Lansing" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -13386,27 +13413,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7199" + "@id": "https://portal.ogc.org/files/?artifact_id=1040" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "00-115" + "@value": "Geoparser" }, { "@language": "en", - "@value": "Topic 15 - Image Exploitation Services" + "@value": "01-035" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Describes the categories and taxonomy of image exploitation services needed to support the use of images and certain related coverage types." + "@value": "*RETIRED* Geoparsing refers to the capability to process a textual document and identify key words and phrases that have a spatial context." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13417,35 +13444,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "00-115" + "@value": "01-035" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 15 - Image Exploitation Services" + "@value": "Geoparser" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-028", + "@id": "http://www.opengis.net/def/docs/24-008", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-04-19" + "@value": "2024-07-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Tom McCarty" + "@value": "Mickael Beaufils, Kathi Schleidt, Hylke van der Schaaf, Dan Ponti, Neil Chadwick, Derrick Dasenbrock" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/ipr" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -13455,27 +13482,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1141" + "@id": "https://docs.ogc.org/per/24-008.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Sensor Collection Service" + "@value": "OGC Geotech Interoperability Experiment Engineering Report" }, { "@language": "en", - "@value": "02-028" + "@value": "24-008" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/ipr" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The basic function of the Sensor Collection Service (SCS) is to provide a web-enabled interface to a sensor, collection of sensors or sensor proxy. Sensors are defined as devices that measure physical quantities. " + "@value": "This Engineering Report (ER) describes the outcomes of the Open Geospatial Consortium (OGC) Geotech Interoperability Experiment (IE). The objective of this IE was to develop a common conceptual model for describing geotechnical engineering data that bridges existing specifications for encoding those data and which could be integrated across OGC and buildingSMART International Standards,\r\n\r\nThis ER is directly imported from the project wiki found here: https://github.com/opengeospatial/Geotech/wiki." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13486,35 +13513,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-028" + "@value": "24-008" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Collection Service" + "@value": "OGC Geotech Interoperability Experiment Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-067", + "@id": "http://www.opengis.net/def/docs/16-003r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-11-19" + "@value": "2017-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona;Roger Brackin" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -13524,27 +13551,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=63663" + "@id": "https://portal.ogc.org/files/?artifact_id=72724" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-067" + "@value": "16-003r2" }, { "@language": "en", - "@value": "Testbed-11 Multi-dimensional GeoPackage Supporting Terrain and Routes Engineering Report" + "@value": "Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Routing is one of the most widely used functions of mobile applications. Routing often requires consideration of a variety of factors in order to provide reasonable estimations of journey time and the cost of travel. Another widely used function of mobile applications is the visualization of characteristics of terrain such as slope or viewsheds. The goal of this engineering report is to describe the work carried out in the OGC Testbed-11 for multidimensional terrain and routing support on SQLite databases that conform to the OGC GeoPackage standard. This OGC® Engineering Report (ER) describes an approach for the storage of routing and multidimensional terrain data in such databases. The ER also presents the results and lessons learnt from the experimentation conducted by the testbed." + "@value": "This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids key words." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13555,35 +13582,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-067" + "@value": "16-003r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed-11 Multi-dimensional GeoPackage Supporting Terrain and Routes Engineering Report" + "@value": "Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-124r1", + "@id": "http://www.opengis.net/def/docs/21-068", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-01-03" + "@value": "2022-09-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Luis Bermudez" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -13593,27 +13620,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=29535" + "@id": "https://docs.ogc.org/bp/21-068.pdf" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Ocean Science Interoperability Experiment Phase 1 Report " + "@value": "OGC Best Practice for using SensorThings API with Citizen Science" }, { "@language": "en", - "@value": "08-124r1" + "@value": "21-068" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering report details lessons learned and best practices defined as part of the Phase 1 Ocean Science Interoperability Experiment (Oceans IE). The Oceans IE was performed to investigate the use of OGC Web Feature Services (WFS) and OGC Sensor Observation Services (SOS) for representing and exchanging point data records from fixed in-situ marine platforms. The activity concluded that for the Oceans community use of in-situ sensors that the OGC Sensor Observation Services (SOS) was better suited than the use of OGC Web Feature Services (WFS) for this purpose." + "@value": "This document introduces an extension to the OGC SensorThings data model and discusses\r\nthe best practices for using such an extension in the context of Citizen Science.\r\nThe motivation for the introduced extension, referred to as “STAplus,” has been developed\r\nduring the EC H2020 project Cos4Cloud and is based on requirements from Citizen Science.\r\nWhereas the dominant use of the OGC SensorThings data model (and API) can be coined\r\nwith the use case “single authority provides sensor readings to consumers”, in Citizen\r\nScience there are many contributors (citizens) that – together – create the big “picture” with\r\ntheir observations.\r\nThe introduced extension STAplus supports the model that those observations are owned by\r\n(different) users that may express the license for re-use; we call this part of the contribution\r\nthe ownership concept. In addition to the ownership and license abilities, the introduced\r\nextension allows to express explicit relations between observations and to create group(s) of\r\nobservations to containerize observations that belong together. Relations can be created\r\namong any individual observations or observations of a group to support performant Linked\r\nData extraction and semantic queries, e.g., expressed in SPARQL.\r\nWe believe that the introduced extension is an important contribution towards the realization\r\nof the FAIR principles, perhaps not only in Citizen Science, as STAplus strengthens the “I”\r\n(Interoperability) through a common data model and API as well as the “R” (Reusability) by\r\nallowing to express standards-based queries that may consider licensing conditions, relevant\r\nfor reuse of other users’ observations. The STAplus Data Model and Business Logic also\r\nenriches existing deployments as the extension can be seamlessly added and thereby offer\r\nnew capabilities to create and manage the “big picture” with multi-user capabilities.\r\nThis document also illustrates best practices of using STAplus, evaluated with proof-ofconcept deployments based on the implementations by 52°North, Secure Dimensions, and\r\nCREAF." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13624,35 +13651,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-124r1" + "@value": "21-068" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Ocean Science Interoperability Experiment Phase 1 Report" + "@value": "OGC Best Practice for using SensorThings API with Citizen Science" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-102", + "@id": "http://www.opengis.net/def/docs/08-022r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-03-08" + "@value": "2008-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roel Nicolai" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/cr" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -13662,27 +13689,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1220" + "@id": "https://portal.ogc.org/files/?artifact_id=27697" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 02 - Spatial Referencing by Coordinates" + "@value": "08-022r1" }, { "@language": "en", - "@value": "02-102" + "@value": "Change Request - O&M Part 1 - Move extensions to new namespace" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/cr" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Describes modelling requirements for spatial referencing by coordinates. This document supplements and corrects ISO 19111. There has never been a motion to adopt 01-063r2. A motion was approved at the Dec 01 meeting in Vancouver to adopt 01-063r1" + "@value": "The XML Schema implementation of optional/informative elements of the Observation Schema was published in the om/1.0.0/extensions directory, in the same XML namespace as the base schema. Those OGC implementations that have a dependency on the Observation Schema (i.e. Sampling Features, SOS) the “all-components” document om.xsd. However, the all-components stub-schema document “om.xsd” does not include the extensions. Thus, any application which requires one of the dependent OGC schemas (Sampling Features, SOS) may not access the Observation Schema Extensions, since the of om.xsd clashes with any attempt to om_extended.xsd. This problem is a consequence of an error in the modularization strategy for optional elements, combined with the rules for schema document resolution used by standard processing environments." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13693,35 +13720,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-102" + "@value": "08-022r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 2 - Spatial Referencing by Coordinates" + "@value": "Change Request - O&M Part 1 - Move extensions to new namespace" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-042", + "@id": "http://www.opengis.net/def/docs/17-083r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-10-22" + "@value": "2022-09-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Pedro Gonçalves" + "@value": "Joan Masó, Jérôme Jacovella-St-Louis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -13731,27 +13758,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-042.html" + "@id": "https://docs.ogc.org/is/17-083r4/17-083r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-042" + "@value": "17-083r4" }, { "@language": "en", - "@value": "OGC Earth Observations Applications Pilot: Terradue Engineering Report" + "@value": "OGC Two Dimensional Tile Matrix Set and Tile Set Metadata" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) documents the findings and experiences resulting from Terradue Activities on the OGC Earth Observation Applications Pilot. More specifically, this ER provides a way forward for the implementation of the applications to the data paradigm in the context of Earth Observation (EO) satellite data processing and Cloud-based platforms to facilitate and standardize the access to Earth observation data and information." + "@value": "The OGC Two Dimensional Tile Matrix Set and Tile Set Metadata Standard defines the rules and requirements for a tile matrix set as a way to index space based on a set of regular grids defining a domain (tile matrix) for a limited list of scales in a Coordinate Reference System (CRS) as defined in OGC 18-005r5 Abstract Specification Topic 2: Referencing by Coordinates. This content was initially included in the OGC 07-057r7 OpenGIS Web Map Tile Service Implementation Standard (WMTS) and was separated out into the OGC 17-083r2 OGC Two Dimensional Tile Matrix Set Standard version 1.0, to support reusability in other data formats of services that need a tiling scheme. This document is a revision of the OGC 17-083r2 document and the general tile matrix set concept is inherited from it with small additions. In a tile matrix set, each tile matrix is divided into regular tiles. In a tile matrix set, a tile can be univocally identified by a tile column, a tile row, and a tile matrix identifier. The OGC Two Dimensional Tile Matrix Set and Tile Set Metadata Standard describes a data structure defining the properties of the tile matrix set in both Unified Modeling Language (UML) diagrams and in tabular form. This document also defines a new data structure, called tile set metadata, that can be used to describe a particular set of tiles following a tile matrix set. Extensible Markup Language (XML) and JavaScript Object Notation (JSON) encodings are described both for tile matrix sets and tile matrix set metadata. It includes tile matrix set limits, links to the tile matrix set, details of the original data represented by the tile set and a nice point of origin to start exploring the tile set. Finally, the document offers practical examples of tile matrix sets both for common global projections and for specific regions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13762,124 +13789,99 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-042" + "@value": "17-083r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Earth Observations Applications Pilot: Terradue Engineering Report" + "@value": "OGC Two Dimensional Tile Matrix Set and Tile Set Metadata" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/retired/collection", + "@id": "http://www.opengis.net/def/docs/12-019", "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" + "http://www.w3.org/2004/02/skos/core#Concept" ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "http://purl.org/dc/terms/created": [ { - "@value": "Documents of type Retired Specification" + "@type": "xsd:date", + "@value": "2012-04-04" } ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "http://purl.org/dc/terms/creator": [ { - "@value": "Documents of type Retired Specification" + "@value": "Gerhard Gröger, Thomas H. Kolbe, Claus Nagel, Karl-Heinz Häfele" } ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs" + "@id": "http://www.opengis.net/def/doc-type/is" } ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/04-086" - }, - { - "@id": "http://www.opengis.net/def/docs/03-061" - }, - { - "@id": "http://www.opengis.net/def/docs/03-055r1" - }, - { - "@id": "http://www.opengis.net/def/docs/04-085" - }, - { - "@id": "http://www.opengis.net/def/docs/06-010r6" - }, - { - "@id": "http://www.opengis.net/def/docs/01-004" - }, - { - "@id": "http://www.opengis.net/def/docs/03-062r1" - }, - { - "@id": "http://www.opengis.net/def/docs/99-114" - }, - { - "@id": "http://www.opengis.net/def/docs/01-037" - }, - { - "@id": "http://www.opengis.net/def/docs/04-087" - }, - { - "@id": "http://www.opengis.net/def/docs/03-003r10" - }, - { - "@id": "http://www.opengis.net/def/docs/05-110" - }, - { - "@id": "http://www.opengis.net/def/docs/01-026r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-064r10" - }, + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/99-103" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/03-063r1" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=47842" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/01-035" + "@language": "en", + "@value": "12-019" }, { - "@id": "http://www.opengis.net/def/docs/00-117" - }, + "@language": "en", + "@value": "City Geography Markup Language (CityGML) Encoding Standard" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/04-088" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/01-042" - }, + "@value": "CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211.\r\n\r\nThe aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. \r\n" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/05-036" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/99-104" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "12-019" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type Retired Specification" + "@language": "en", + "@value": "OGC City Geography Markup Language (CityGML) Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-038", + "@id": "http://www.opengis.net/def/docs/20-036", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-12" + "@value": "2021-01-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Chris Clark" + "@value": "Emeric Beaufays, C.J. Stanbridge, Rob Smith" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -13894,17 +13896,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-038.html" + "@id": "https://docs.ogc.org/per/20-036.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-038" + "@value": "20-036" }, { "@language": "en", - "@value": "Testbed-12 NSG GeoPackage Profile Assessment Engineering Report" + "@value": "Full Motion Video to Moving Features Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -13914,7 +13916,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The National System for Geospatial-Intelligence (NSG) GeoPackage Profile defines and tailors the implementable provisions prescribed for the NSG for a GeoPackage based on the OGC GeoPackage encoding standard. The profile provides detailed directions on how to use the clauses, options and parameters defined in the base GeoPackage standard. The goal is to ensure that NSG GeoPackages, GeoPackage SQLite Extensions, and supporting utilities and services fulfill their intended purposes and are fit for use.\r\n\r\nThe goal of this Engineering Report (ER) is to assess whether requirements as specified in the proposed profile are specific enough to allow for any two independent GeoPackage implementers to produce and consume interoperable NSG GeoPackages. Concerns with the profile are outlined and recommendations for improvement are provided. Thoughts on the viability of the profile approach and guidance on how the profile could apply to Vector Tiling are also provided." + "@value": "This OGC Testbed-16 Engineering Report (ER) evaluates the suitability of existing OGC standards for the generation of Moving Features from Full Motion Video (FMV) that has an embedded stream of detected moving objects.\r\n\r\nThis ER presents several proof of concept applications that accept FMVs, with multiple encoded Video Moving Target Indicators (VMTI), and combines the VMTIs into separate tracks that are then encoded to OGC Moving Features.\r\n\r\nIn addition, the ER explores the generation of records encoded according to OGC Sensor Model Language (SensorML) 2.0 standard describing the collection platform and relevant telemetry information from the key-value stream content encoded according to the MISB 0601 and 0903 specifications of the Motion Imagery Standards Board (MISB)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13925,35 +13927,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-038" + "@value": "20-036" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 NSG GeoPackage Profile Assessment Engineering Report" + "@value": "OGC Testbed-16: Full Motion Video to Moving Features Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-128", + "@id": "http://www.opengis.net/def/docs/10-127r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-10-22" + "@value": "2010-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Luis Bermudez" + "@value": "Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -13963,27 +13965,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41359" + "@id": "https://portal.ogc.org/files/?artifact_id=40134" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-128" + "@value": "10-127r1" }, { "@language": "en", - "@value": "OGC Compliance Testing White Paper" + "@value": "OWS-7 Engineering Report - Aviation Portrayal" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This white paper describes the OGC Compliance Testing Program. It provides\r\ninformation about:\r\n• The need for compliance testing to enable interoperability\r\n• How to obtain compliance certification\r\n• The difference between implementing and being certified\r\n• How compliance benefits providers and users of technology\r\n• The proper use of the “Certified OGC Compliant” mark\r\n• Suggested language for procurement documents\r\n• Trademark licensing fees\r\n• An example of an OGC compliance test " + "@value": "This document describes the requirements, design, technical implementation and technology trialed for the Feature Portrayal service chain used in OWS-7. This includes the interfaces to the OWS Data Services deployed, the feature portrayal servers, the interfaces to clients and the registry information model and interface." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -13994,66 +13996,104 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-128" + "@value": "10-127r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Compliance Testing White Paper" + "@value": "OWS-7 Engineering Report - Aviation Portrayal" } ] }, { - "@id": "http://www.opengis.net/def/docs", + "@id": "http://www.opengis.net/def/docs/20-038", "@type": [ - "http://www.w3.org/2004/02/skos/core#ConceptScheme" + "http://www.w3.org/2004/02/skos/core#Concept" ], - "http://purl.org/dc/terms/source": [ + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/entities/bodies/ogcna" + "@type": "xsd:date", + "@value": "2020-10-22" } ], - "http://www.opengis.net/def/metamodel/ogc-na/collectionView": [ + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/" + "@value": "Omar Barrilero, Adrian Luna" } ], - "http://www.w3.org/2004/02/skos/core#changeNote": [ + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@value": "loaded from https://portal.opengeospatial.org/public_ogc/api/docs.php?CITE=1" + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ + { + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + { + "@id": "https://docs.ogc.org/per/20-038.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ + { + "@language": "en", + "@value": "20-038" + }, + { + "@language": "en", + "@value": "OGC Earth Observation Applications Pilot: European Union Satellite Centre Engineering Report" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ + { + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OGC document register with annotations and links" + "@value": "This Engineering Report (ER) describes the achievements of the European Union Satellite Centre (SatCen) as an application provider in the OGC Earth Observation Applications Pilot and the lessons learned from the project." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ + { + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "20-038" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "OGC Documents" + "@language": "en", + "@value": "OGC Earth Observation Applications Pilot: European Union Satellite Centre Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-058", + "@id": "http://www.opengis.net/def/docs/07-014r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-11-02" + "@value": "2007-08-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clements Portele, Panagiotis (Peter) A. Vretanos" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -14063,27 +14103,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/18-058/18-058.html" + "@id": "https://portal.ogc.org/files/?artifact_id=23180" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-058" + "@value": "Sensor Planning Service Implementation Specification" }, { "@language": "en", - "@value": "OGC API - Features - Part 2: Coordinate Reference Systems by Reference" + "@value": "07-014r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks.\r\n\r\nOGC API Features provides API building blocks to create, modify and query features on the Web. OGC API Features is comprised of multiple parts, each of them is a separate standard.\r\n\r\nThis part extends the core capabilities specified in Part 1: Core with the ability to use coordinate reference system identifiers other than the defaults defined in the core." + "@value": "The OpenGIS® Sensor Planning Service Interface Standard (SPS) defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor planning request; to submit such a request; to inquire about the status of such a request; to update or cancel such a request; and to request information about other OGC Web services that provide access to the data collected by the requested task. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -14094,13 +14134,13 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-058" + "@value": "07-014r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Features - Part 2: Coordinate Reference Systems by Reference" + "@value": "OpenGIS Sensor Planning Service Implementation Specification" } ] }, @@ -14138,11 +14178,11 @@ "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-031" + "@value": "3D Data Container and Tiles API Pilot Summary Engineering Report" }, { "@language": "en", - "@value": "3D Data Container and Tiles API Pilot Summary Engineering Report" + "@value": "20-031" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -14174,24 +14214,24 @@ ] }, { - "@id": "http://www.opengis.net/def/docs/20-050", + "@id": "http://www.opengis.net/def/docs/22-024r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2023-06-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Sergio Taleisnik" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -14201,27 +14241,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/20-050/20-050.html" + "@id": "https://docs.ogc.org/per/22-024r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension)." + "@value": "22-024r2" }, { "@language": "en", - "@value": "20-050" + "@value": "Testbed-18: Filtering Service and Rule Set Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This optional OGC CDB extension defines the requirements and provides CDB specific guidance on using GeoPackage containers in a CDB data store. There is a companion CDB Best Practice document that provide rules and guidance for transforming CDB structured Shapefiles into CDB structure GeoPackages that are compliant with the requirements and conformance classes as defined in this document." + "@value": "This Testbed-18 (TB-18) Filtering Service and Rule Set Engineering Report (ER) documents best practices identified for features filtering and describes in detail how filtering can be decoupled from data services. Further, this ER describes how filtering rules can be provided to Filtering Services at runtime." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -14232,35 +14272,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-050" + "@value": "22-024r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension)." + "@value": "Testbed-18: Filtering Service and Rule Set Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-072r2", + "@id": "http://www.opengis.net/def/docs/21-056r10", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-08-13" + "@value": "2022-11-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Hugo Ledoux" + "@value": "Carl Stephen Smyth" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/is-draft" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -14270,27 +14310,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/20-072r2/20-072r2.html" + "@id": "https://docs.ogc.org/dis/21-056r10/21-056r10.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CityJSON Community Standard 1.0" + "@value": "OGC GeoPose 1.0 Data Exchange Draft Standard" }, { "@language": "en", - "@value": "20-072r2" + "@value": "21-056r10" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/is-draft" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "CityJSON is a JSON-based encoding for a well-documented subset of the OGC CityGML data model (version 2.0.0). CityJSON defines how to store digital 3D models of cities and landscapes. The aim of CityJSON is to offer an alternative to the GML encoding of CityGML, which can be verbose and complex to read and manipulate. CityJSON aims at being easy-to-use, both for reading datasets and for creating them. It was designed with programmers in mind, so that tools and APIs supporting it can be quickly built." + "@value": "GeoPose 1.0 is an OGC Implementation Standard for exchanging the location and orientation of real or virtual geometric objects (“Poses”) within reference frames anchored to the earth’s surface (“Geo”) or within other astronomical coordinate systems.\r\n\r\nThe standard specifies two Basic forms with no configuration options for common use cases, an Advanced form with more flexibility for more complex applications, and five composite GeoPose structures that support time series plus chain and graph structures.\r\n\r\nThese eight Standardization Targets are independent. There are no dependencies between Targets and each may be implemented as needed to support a specific use case.\r\n\r\nThe Standardization Targets share an implementation-neutral Logical Model which establishes the structure and relationships between GeoPose components and also between GeoPose data objects themselves in composite structures. Not all of the classes and properties of the Logical Model are expressed in individual Standardization Targets nor in the specific concrete data objects defined by this standard. Those elements that are expressed are denoted as implementation-neutral Structural Data Units (SDUs). SDUs are aliases for elements of the Logical Model, isolated to facilitate specification of their use in encoded GeoPose data objects for a specific Standardization Target.\r\n\r\nFor each Standardization Target, each implementation technology and corresponding encoding format defines the encoding or serialization specified in a manner appropriate to that technology.\r\n\r\nGeoPose 1.0 specifies a single encoding in JSON format (IETF RFC 8259). Each Standardization Target has a JSON Schema (Internet-Draft draft-handrews-json-schema-02) encoding specification. The key standardization requirements specify that concrete JSON-encoded GeoPose data objects must conform to the corresponding JSON Schema definition. The individual elements identified in the encoding specification are composed of SDUs, tying the specifications back to the Logical Model.\r\n\r\nThe GeoPose 1.0 Standard makes no assumptions about the interpretation of external specifications, for example, of reference frames. Nor does it assume or constrain services or interfaces providing conversion between GeoPoses of difference types or relying on different external reference frame definitions.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -14301,35 +14341,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-072r2" + "@value": "21-056r10" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC CityJSON Community Standard 1.0" + "@value": "OGC GeoPose 1.0 Data Exchange Draft Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-196r1", + "@id": "http://www.opengis.net/def/docs/09-025r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-03-28" + "@value": "2014-07-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "OGC Aviation Domain Working Group" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -14339,27 +14379,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41668" + "@id": "https://docs.ogc.org/is/09-025r2/09-025r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Guidance on the Aviation Metadata Profile" + "@value": "Web Feature Service 2.0 Interface Standard - With Corrigendum" }, { "@language": "en", - "@value": "10-196r1" + "@value": "09-025r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This paper explains how to map the Requirements for Aviation Metadata into a metadata profile." + "@value": "The Web Feature Service (WFS) represents a change in the way geographic information is created, modified and exchanged on the Internet. Rather than sharing geographic information at the file level using File Transfer Protocol (FTP), for example, the WFS offers direct fine-grained access to geographic information at the feature and feature property level.\r\n\r\nThis International Standard specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored, parameterized query expressions.\r\n\r\nDiscovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers.\r\n\r\nQuery operations allow features or values of feature properties to be retrieved from the underlying data store based upon constraints, defined by the client, on feature properties.\r\n\r\nLocking operations allow exclusive access to features for the purpose of modifying or deleting features.\r\n\r\nTransaction operations allow features to be created, changed, replaced and deleted from the underlying data store.\r\n\r\nStored query operations allow clients to create, drop, list and described parameterized query expressions that are stored by the server and can be repeatedly invoked using different parameter values.\r\n\r\nThis International Standard defines eleven operations:\r\n\r\nGetCapabilities (discovery operation)\r\nDescribeFeatureType (discovery operation)\r\nGetPropertyValue (query operation)\r\nGetFeature (query operation)\r\nGetFeatureWithLock (query & locking operation)\r\nLockFeature (locking operation)\r\nTransaction (transaction operation)\r\nCreateStoredQuery (stored query operation)\r\nDropStoredQuery (stored query operation)\r\nListStoredQueries (stored query operation)\r\nDescribeStoredQueries (stored query operation)\r\nIn the taxonomy of services defined in ISO 19119, the WFS is primarily a feature access service but also includes elements of a feature type service, a coordinate conversion/transformation service and geographic format conversion service." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -14370,30 +14410,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-196r1" + "@value": "09-025r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Guidance on the Aviation Metadata Profile" + "@value": "OGC® Web Feature Service 2.0 Interface Standard - With Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-008r2", + "@id": "http://www.opengis.net/def/docs/06-080r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-04-21" + "@value": "2007-02-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis, Andreas Wytzisk" + "@value": "Jerome Gasperi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -14408,17 +14448,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1367" + "@id": "https://portal.ogc.org/files/?artifact_id=19094" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Notification Service" + "@value": "GML Application Schema for EO Products" }, { "@language": "en", - "@value": "03-008r2" + "@value": "06-080r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -14428,7 +14468,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Web Notification Service (WNS) is the first asynchronous messaging service specified by OGC. At the moment, the WNS message schema is optimized to fulfil the needs of services supporting the use of sensors, like Sensor Planning Service. Future work activities should include the adaptation of the message schema to the needs of other services." + "@value": "This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGCTM Catalogue Services Specification v2.0.0 (with Corrigendum) [OGC 04-021r3]" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -14439,30 +14479,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-008r2" + "@value": "06-080r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Notification Service" + "@value": "GML Application Schema for EO Products" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-086r1", + "@id": "http://www.opengis.net/def/docs/17-027", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-01-25" + "@value": "2018-01-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jan Herrmann, Andreas Matheus" + "@value": "Robert Cass" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -14477,17 +14517,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46019" + "@id": "https://docs.ogc.org/per/17-027.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-086r1" + "@value": "17-027" }, { "@language": "en", - "@value": "OWS-8 Aviation Thread - Authoritative AIXM Data Source Engineering Report" + "@value": "Testbed-13: GeoPackage Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -14497,76 +14537,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report describes how to provide access control for WFS-T 2.0 instances\r\nin the OWS-8 Authoritative AIXM Data Source scenario." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ - { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-086r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@language": "en", - "@value": "OWS-8 Aviation Thread - Authoritative AIXM Data Source Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/00-106", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ - { - "@type": "xsd:date", - "@value": "2000-04-18" - } - ], - "http://purl.org/dc/terms/creator": [ - { - "@value": "Cliff Kottman, Charles Roswell" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ - { - "@id": "http://www.opengis.net/def/doc-type/d-as" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ - { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ - { - "@id": "https://portal.ogc.org/files/?artifact_id=7198" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ - { - "@language": "en", - "@value": "00-106" - }, - { - "@language": "en", - "@value": "Topic 06 - The Coverage Type" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ - { - "@id": "http://www.opengis.net/def/doc-type/d-as" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Incomplete. This document normatively references parts of the previous version of AS Topic 6, document 00-106. Need to be updated to include Roswell Change Proposal (01-011), which includes 19123 and retains material from Topic 6, v6." + "@value": "This Engineering Report details the processes and results related to generating GeoPackages developed to contain topographic vector features and supporting symbologies based on The National Map (TNM) product of the United States Geological Survey (USGS)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -14577,30 +14548,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "00-106" + "@value": "17-027" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 6 - The Coverage Type" + "@value": "OGC Testbed-13: GeoPackage Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-049r1", + "@id": "http://www.opengis.net/def/docs/15-112r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-09-21" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -14615,17 +14586,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/22-049r1/22-049r1.html" + "@id": "https://docs.ogc.org/is/15-112r4/15-112r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0" + "@value": "15-112r4" }, { "@language": "en", - "@value": "22-049r1" + "@value": "Volume 3: OGC CDB Terms and Definitions (Normative)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -14635,7 +14606,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 defines a geospatial extension to the OASIS eXtensible Access Control Markup Language (XACML) Version 3.0 Standard. GeoXACML 3.0 supports the interoperable definition of access rights including geographic conditions based on the XACML 3.0 language, processing model and policy schema. GeoXACML 3.0 provides improvements based on enhancements to the XACML Standard, primarily the support of access conditions spanning different XACML categories. This enhancement empowers GeoXACML 3.0 to be a powerful decision engine with support for spatiotemporal access conditions.\r\n\r\nAs a result of the XACML 3.0 deployment model and corresponding implementation flexibility, GeoXACML 3.0 can be operated as a traditional Policy Decision Point or as a cloud-native API gateway.\r\n\r\nThe OGC GeoXACML 3.0 Standard defines different conformance classes that supports flexible implementation conformance. Implementation of the Core conformance class supports the ISO 19125 geometry model including topological test (spatial relations) functions which enables the indexing of access conditions-based geometry. The Spatial Analysis conformance class extends the topological test functions for defining access conditions including the processing of geometries. To support condition evaluation for geometries encoded in different Coordinate Reference System (CRS), the CRS Transformation conformance class enables a compliant implementation to undertake dynamic CRS transformation during decision-making unless prohibited per request. Finally, the API conformance class enables operating a GeoXACML 3.0 compliant implementation as an OGC API conformant service (Policy Decision Point)." + "@value": "This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -14646,30 +14617,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-049r1" + "@value": "15-112r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0" + "@value": "Volume 3: OGC CDB Terms and Definitions (Normative)" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-022r1", + "@id": "http://www.opengis.net/def/docs/07-057r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-05-05" + "@value": "2007-10-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff de La Beaujardiere" + "@value": "Keith Pomakis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -14684,17 +14655,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1024" + "@id": "https://portal.ogc.org/files/?artifact_id=23206" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Basic Services Model" + "@value": "Tiled WMS Discussion Paper" }, { "@language": "en", - "@value": "01-022r1" + "@value": "07-057r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -14704,7 +14675,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Basic Services Model is an implementation of the ISO TC211 services architecture as found in ISO 19119 Geographic Information " + "@value": "The OpenGIS® Tiled Web Map Service Discussion Paper explains how the OpenGIS Web Map Service Standard (WMS) [http://www.opengeospatial.org/standards/wms] can be extended to allow fast response to a predefined set of tiled maps. It should be read in conjunction with the latest version WMS standard.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -14715,46 +14686,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-022r1" + "@value": "07-057r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Basic Services Model" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-atb", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/04-014r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-053r1" + "@value": "OpenGIS Tiled WMS Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-023r2", + "@id": "http://www.opengis.net/def/docs/17-014r9", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-16" + "@value": "2023-01-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Cote" + "@value": "Carl Reed, Tamrat Belayneh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -14764,27 +14724,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21622" + "@id": "https://docs.ogc.org/cs/17-014r9/17-014r9.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-023r2" + "@value": "17-014r9" }, { "@language": "en", - "@value": "OGC Web Services Architecture for CAD GIS and BIM" + "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document lists the design principles and requirements for future versions of a potential architecture for integrating workflows and information models from Computer Aided Design and Building Information Modelling with the principles of the OGC Web Services Architecture. " + "@value": "The Indexed 3D Scene Layer (I3S) format is an open 3D content delivery format used to rapidly stream and distribute large volumes of 3D GIS data to mobile, web and desktop clients. I3S content can be shared across enterprise systems using both physical and cloud servers.\r\n\r\nA single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files.\r\n\r\nThe delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -14795,35 +14755,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-023r2" + "@value": "17-014r9" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Services Architecture for CAD GIS and BIM" + "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.3" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-007", + "@id": "http://www.opengis.net/def/docs/18-050r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-01-24" + "@value": "2019-02-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Schut" + "@value": "Paulo Sacramento" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -14833,27 +14793,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8723" + "@id": "https://docs.ogc.org/per/18-050r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-007" + "@value": "ADES & EMS Results and Best Practices Engineering Report" }, { "@language": "en", - "@value": "Web Processing Service" + "@value": "18-050r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is the specification for a Web Processing Service (WPS). \r\nA Web Service Processing Service provides access to calculations or models which operate on spatially referenced data. The data required by the service can be available locally, or delivered across a network using data exchange standards such as Geography Markup Language (GML) or Geolinked Data Access Service (GDAS). \r\n " + "@value": "This Engineering Report (ER) describes best practices and results gathered through the work performed in the Exploitation Platforms Earth Observation Clouds (EOC) Thread of OGC Testbed-14 concerning the Application Deployment and Execution Service (ADES) and the Execution Management Service (EMS). Both the ADES and EMS were identified by the European Space Agency (ESA), beforehand, as essential elements of a Thematic Exploitation Platform (TEP).\r\n\r\nIn the context of a generic Earth Observation Exploitation Platform ecosystem, populated by TEPs and Mission Exploitation Platforms (MEPs), which make use of cloud computing resources for Earth Observation data processing, ESA has established two fundamental building blocks within a TEP, with different functions, the ADES and the EMS. Users interact with a TEP using a Web Client, and the TEP contains a EMS and a ADES. The EMS includes most of the control logic, required for deploying and executing applications in different MEPs and TEPs, the chaining thereof, and the overall coherence of the execution chain (e.g. gathering all outputs and enabling their presentation to the user by a client sensibly). The ADES instead is responsible for the single application deployment and execution on a specific platform. Therefore, it is expected that there are ADES instances both in a TEP and in the individual MEPs.\r\n\r\nThe Testbed-14 Participants have experimented with different options for what concerns the functionality allocated to each of the two components, the information required by each of them and the interface requirements between them in order to produce a consistent chain, compliant with ESA’s objectives (as the Sponsor). This report describes these experiments, providing their results and suggesting best practices on how the two services should be engineered in the Exploitation Platform context.\r\n\r\nThe OGC Web Processing Service (WPS) 2.0 standard is of particular relevance given that it is well-established in the OGC Web Service context, specifically that concerning processing, its interoperability value has been clearly demonstrated, and it therefore provides a useful mechanism for standardizing interfaces between components of heterogeneous provenance and implementation." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -14864,35 +14824,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-007" + "@value": "18-050r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Processing Service" + "@value": "OGC Testbed-14: ADES & EMS Results and Best Practices Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-029", + "@id": "http://www.opengis.net/def/docs/01-013r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-01-20" + "@value": "2001-02-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stephane Fellah, Steven Keens" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -14902,27 +14862,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1315" + "@id": "https://portal.ogc.org/files/?artifact_id=1006" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-029" + "@value": "01-013r1" }, { "@language": "en", - "@value": "OWS Messaging Framework" + "@value": "High-Level Ground Coordinate Transformation Interface" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines a messaging framework to conduct communications between the OGC web services. It is independent of any transport protocol and any messaging encoding. By using the framework, the service designer could focus only on the message definitions and messaging flows for every action supported by the service, without worry on the messaging transport and delivery. The framework should considerably simplify the implementations of the OGC web services and should enable service chaining." + "@value": "This document specifies a " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -14933,35 +14893,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-029" + "@value": "01-013r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS Messaging Framework" + "@value": "High-Level Ground Coordinate Transformation Interface" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-182r1", + "@id": "http://www.opengis.net/def/docs/17-046", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-06-06" + "@value": "2018-03-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steven Keens" + "@value": "Volker Coors" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -14971,27 +14931,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=19424" + "@id": "https://docs.ogc.org/per/17-046.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Discussions, findings, and use of WPS in OWS-4" + "@value": "17-046" }, { "@language": "en", - "@value": "06-182r1" + "@value": "Testbed-13: 3D Tiles and I3S Interoperability and Performance Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document reviews the material discussed during the OWS-4 project, describes the WPS processes deployed in the workflows, and offers suggestions to the OGC to move forward with the WPS. " + "@value": "This OGC Testbed 13 Engineering Report (ER) documents the overall architecture developed in the Interoperability of 3D Tiles and I3S using a 3D Portrayal Service and performance study of 3D tiling algorithms activity. The report also summarizes a proof-of-concept of the use of 3D Tiles and I3S as data delivery formats for the OGC 3D Portrayal Service interface standard. The report captures the results from the interoperability tests performed as part of the 3D Tiles and I3S testbed work package. Specifically, this OGC Testbed activity focused on the following tasks:\r\n\r\nCityGML files converted into Cesium 3D Tiles using Analytical Graphics (AGI’s) 3D Tiling Pipeline, and Cesium as the rendering client;\r\n\r\nAn OGC CDB data store converted into 3D Tiles using Compusult’s Streaming engine, Cesium and Ecere’s GNOSIS as rendering client;\r\n\r\nCityGML data store GeoRocket, 3DPS with 3D Tiles as data delivery format, and Cesium as rendering client;\r\n\r\nCityGML converted into I3S, 3DPS with I3S as data delivery format, and Cesium as rendering client;\r\n\r\nCityGML converted into I3S using ArcGIS and FME, 3DPS with I3S as data delivery format, and rendering in ArcGIS client;\r\n\r\nCityGML with application domain extension stored in GeoRocket, converted to 3D Tiles, and Cesium as the rendering client;\r\n\r\n3D Tiles (generated by all streaming engines visualized) from Ecere’s GNOSIS rendering client;\r\n\r\nCDB visualized directly from Ecere’s GNOSIS rendering client; and\r\n\r\nI3S visualized from Ecere’s GNOSIS rendering client.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -15002,35 +14962,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-182r1" + "@value": "17-046" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Discussions, findings, and use of WPS in OWS-4" + "@value": "OGC Testbed-13: 3D Tiles and I3S Interoperability and Performance Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-097", + "@id": "http://www.opengis.net/def/docs/07-092r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-11" + "@value": "2007-11-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Blodgett, Byron Cochrane, Rob Atkinson, Sylvain Grellet, Abdelfettah Feliachi, Alistair Ritchi" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -15040,27 +15000,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-097.html" + "@id": "https://portal.ogc.org/files/?artifact_id=24045" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Environmental Linked Features Interoperability Experiment Engineering Report" + "@value": "Definition identifier URNs in OGC namespace" }, { "@language": "en", - "@value": "18-097" + "@value": "07-092r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Systems that maintain and disseminate information representing and/or related to spatial features often lack mechanisms to describe or discover how features relate to each other, to other kinds of features, and to a wide variety of related information that may be relevant. The Environmental Linked Features Interoperability Experiment (ELFIE) explored Open Geospatial Consortium (OGC) and World Wide Web Consortium (W3C) standards with the goal of establishing a best practice for exposing cross-domain links between environmental domain and sampling features. The Interoperability Experiment (IE) focused on encoding relationships between cross-domain features and linking available observations data to sampled domain features. An approach that leverages the OGC service baseline, W3C data on the web best practices, and JavaScript Object Notation for Linked Data (JSON-LD) contexts was developed and evaluated. Outcomes of the experiment demonstrate that broadly accepted web technologies for linked data can be applied using OGC services and domain data models to fill important gaps in existing environmental data systems' capabilities. While solutions were found to be capable and promising, OGC services and domain model implementations have limited utility for use in linked data applications in their current state and the universe of persistent URIs that form the foundation of a linked data infrastructure is still small. In addition to improvement of the standards baseline and publication of linked data URIs, establishing conventions for URI dereferencing behavior and default content given multiple options for a resource remain for future work." + "@value": "This Best Practices Paper specifies Universal Resource Names (URNs) in the ogc URN namespace to be used for identifying definitions. This document specifies the formats used by these URNs, plus a set of specific URNs for specific definitions. These definitions should be used wherever applicable by implementations of various OGC Implementation Specifications, including GML, WMS, WFS, and WCS. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -15071,13 +15031,13 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-097" + "@value": "07-092r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Environmental Linked Features Interoperability Experiment Engineering Report" + "@value": "Definition identifier URNs in OGC namespace" } ] }, @@ -15151,24 +15111,24 @@ ] }, { - "@id": "http://www.opengis.net/def/docs/09-050r1", + "@id": "http://www.opengis.net/def/docs/01-044r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-27" + "@value": "2001-06-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Hans Schoebach" + "@value": "John Bobbitt" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -15178,27 +15138,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34032" + "@id": "https://portal.ogc.org/files/?artifact_id=1050" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-050r1" + "@value": "Units of Measure and Quantity Datatypes" }, { "@language": "en", - "@value": "OGC OWS-6-AIM Engineering Report" + "@value": "01-044r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report establishes a baseline for the technical architecture, its alternatives and issues for implementing the use cases as specified in the OWS-6 AIM thread RFQ including the temporal WFS supporting the temporal FE 2.0 operators, the Event Service Notification architecture and the client EFBs. " + "@value": "Common semantic for units of measurement to be used across all OGC specifications." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -15209,35 +15169,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-050r1" + "@value": "01-044r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC OWS-6-AIM Engineering Report" + "@value": "Units of Measure and Quantity Datatypes" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-010r4", + "@id": "http://www.opengis.net/def/docs/20-011", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-19" + "@value": "2020-05-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Sara Saeedi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -15247,27 +15207,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/16-010r4" + "@id": "https://docs.ogc.org/per/20-011.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2" + "@value": "20-011" }, { "@language": "en", - "@value": "16-010r4" + "@value": "SCIRA Pilot Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store.\r\nPlease note that the term “lineal” has been replaced with the term “line” or “linear” throughout this document\r\nPlease note that the term “areal” has been replaced with the term “polygon” throughout this document.\r\n" + "@value": "This engineering report (ER) captures Smart City Interoperability Reference Architecture (SCIRA) Pilot implementation outcomes and findings to demonstrate the risk mitigation and safety capability of the SCIRA interoperable and standard-based architecture. SCIRA Pilot is an OGC (Open Geospatial Consortium) Innovation Program project sponsored by the US Department of Homeland Security (DHS) Science & Technology (S&T) in collaboration with the city of St. Louis, Missouri. The purpose of this project is to advance standards for smart and safe cities and develop open, interoperable design patterns for incorporating the Internet of Things (IoT) sensors into city services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -15278,160 +15238,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-010r4" + "@value": "20-011" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-is", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/06-104r3" - }, - { - "@id": "http://www.opengis.net/def/docs/04-095c1" - }, - { - "@id": "http://www.opengis.net/def/docs/02-058" - }, - { - "@id": "http://www.opengis.net/def/docs/02-009" - }, - { - "@id": "http://www.opengis.net/def/docs/99-051" - }, - { - "@id": "http://www.opengis.net/def/docs/05-134" - }, - { - "@id": "http://www.opengis.net/def/docs/09-025r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-036r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-022r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-063r5" - }, - { - "@id": "http://www.opengis.net/def/docs/06-103r3" - }, - { - "@id": "http://www.opengis.net/def/docs/07-014r3" - }, - { - "@id": "http://www.opengis.net/def/docs/02-070" - }, - { - "@id": "http://www.opengis.net/def/docs/04-021r3" - }, - { - "@id": "http://www.opengis.net/def/docs/02-069" - }, - { - "@id": "http://www.opengis.net/def/docs/07-026r2" - }, - { - "@id": "http://www.opengis.net/def/docs/05-126" - }, - { - "@id": "http://www.opengis.net/def/docs/02-059" - }, - { - "@id": "http://www.opengis.net/def/docs/03-065r6" - }, - { - "@id": "http://www.opengis.net/def/docs/04-095" - }, - { - "@id": "http://www.opengis.net/def/docs/09-147r1" - }, - { - "@id": "http://www.opengis.net/def/docs/99-049" - }, - { - "@id": "http://www.opengis.net/def/docs/05-008c1" - }, - { - "@id": "http://www.opengis.net/def/docs/10-126r3" - }, - { - "@id": "http://www.opengis.net/def/docs/07-144r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-067r2" - }, - { - "@id": "http://www.opengis.net/def/docs/10-157r3" - }, - { - "@id": "http://www.opengis.net/def/docs/06-083r8" - }, - { - "@id": "http://www.opengis.net/def/docs/02-023r4" - }, - { - "@id": "http://www.opengis.net/def/docs/13-026r8" - }, - { - "@id": "http://www.opengis.net/def/docs/05-076" - }, - { - "@id": "http://www.opengis.net/def/docs/00-028" - }, - { - "@id": "http://www.opengis.net/def/docs/05-016" - }, - { - "@id": "http://www.opengis.net/def/docs/07-002r3" - }, - { - "@id": "http://www.opengis.net/def/docs/01-047r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-067r5" - }, - { - "@id": "http://www.opengis.net/def/docs/01-068r3" - }, - { - "@id": "http://www.opengis.net/def/docs/07-110r2" - }, - { - "@id": "http://www.opengis.net/def/docs/09-110r3" - }, - { - "@id": "http://www.opengis.net/def/docs/02-087r3" + "@value": "OGC SCIRA Pilot Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-012", + "@id": "http://www.opengis.net/def/docs/11-111", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-09-04" + "@value": "2012-01-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jennifer Marcus, Chuck Morris" + "@value": "Daniele Marchionni" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -15441,27 +15276,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20582" + "@id": "https://portal.ogc.org/files/?artifact_id=45124" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Compliance Test Engine Interoperability Program Report" + "@value": "Ordering Services for Earth Observation Products Adoption Voting Comments and Answers" }, { "@language": "en", - "@value": "07-012" + "@value": "11-111" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "As a work item in the OWS4/Conformance and Interoperability Test and Evaluation (CITE) project, Northrop Grumman Information Technology (NGIT) provided an open source web services compliance engine. NGIT refers to this engine as the Test Evaluation And Measurement (TEAM) Engine. It executes scripts written in Compliance Test Language (CTL), a grammar also developed by NGIT. This IPR describes TEAM Engine in detail and provides information on how it was used in OWS-4/CITE." + "@value": "This document lists the No votes received during the TC adoption vote (2011-05-03 - 2011-07-02) together with the responses from the OSEO SWG." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -15472,35 +15307,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-012" + "@value": "11-111" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Compliance Test Engine Interoperability Program Report" + "@value": "Ordering Services for Earth Observation Products Adoption Voting Comments and Answers" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-042", + "@id": "http://www.opengis.net/def/docs/11-157", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-07-05" + "@value": "2011-10-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sina Taghavikish" + "@value": "Jim Greenwood" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -15510,27 +15345,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-042.html" + "@id": "https://portal.ogc.org/files/?artifact_id=46435" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-042" + "@value": "Corrigendum 1 for OGC Web Services Common Standard v2.0.0 - Multilingual" }, { "@language": "en", - "@value": "OGC Testbed-19 — Non-Terrestrial Geospatial Engineering Report" + "@value": "11-157" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Testbed-18 explored the potential use of OGC Standards for non-terrestrial applications and was scoped as a paper study. Validation of the Testbed-18 recommendations has been left for Testbed-19. This OGC Engineering Report (ER) documents recommended changes to OGC Standards and the implementation experience to justify those changes.\r\n\r\nThe use of OGC Standards include geospatial applications for non-Earth planets as well as interplanetary spatiotemporal applications. Two Standards emerged as key: ISO 19111 (OGC Abstract Specification 2: Referencing by coordinates) and OGC 21-056r11 (OGC GeoPose 1.0 Data Exchange Standard). Extensions to ISO 19111 were identified which would support the representation of non-terrestrial planetary spatial reference systems as well as interplanetary spatiotemporal reference systems.\r\n\r\nThe GeoPose Standard (GeoPose) was explored as a mechanism to integrate the large number of reference systems and transformations needed to model the geometry of interplanetary spacetime.\r\n\r\nIn the context of the Double Asteroid Redirection Test (DART) scenario, positions and orientations in different coordinate reference systems and associated attributes such as velocities of non-terrestrial objects were encoded using two different approaches: as sequences of extended GeoPoses, and as OGC Moving Features JSON (MF-JSON). These encoded data were then used as the basis for a 3D visualization demonstration.\r\n\r\nThis work is not intended to replace the existing standards already used in astronomy such as the World Coordinate System (WCS). The recommendations provided in this ER are rather intended to improve interoperability by specifying how to export a subset of a WCS description as OGC/ISO data structures for consumption by GIS software or other geospatial technology applications.\r\n\r\nTestbed-18 also investigated how GeoPose could be integrated with mobile location-aware devices such as smartphones. Engineering Report OGC 22-016r3 (Testbed-18: Moving Features) concluded that GeoPose could enrich data with location and orientation information synchronized to video and other sensors and identified two suitable road network use cases for study using WebVMT in Testbed-19." + "@value": "This document being corrected specifies many of the aspects that are, or should be, common to all or multiple OWS interface Implementation Specifications. The Common Implementation Specification aspects specified by this document currently include:\r\na) Operation request and response contents, most partial\r\nb) Parameters and data structures included in operation requests and responses c) XML and KVP encoding of operation requests and responses" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -15541,35 +15376,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-042" + "@value": "11-157" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-19 — Non-Terrestrial Geospatial Engineering Report" + "@value": "Corrigendum 1 for OGC Web Services Common Standard v2.0.0 - Multilingual" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-063r1", + "@id": "http://www.opengis.net/def/docs/05-035r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-11-05" + "@value": "2006-01-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas H.G. Lankester" + "@value": "Jens Fitzke, Rob Atkinson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -15579,27 +15414,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=30912" + "@id": "https://portal.ogc.org/files/?artifact_id=13593" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-063r1" + "@value": "Gazetteer Service Profile of a WFS" }, { "@language": "en", - "@value": "Web Map Services - Application Profile for EO Products" + "@value": "05-035r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC document specifies a constrained, consistent interpretation of the WMS specification that is applicable to government, academic and commercial providers of EO products. " + "@value": "Provides web access to an authority for place names. Returns their associated feature representations" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -15610,35 +15445,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-063r1" + "@value": "05-035r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Map Services - Application Profile for EO Products" + "@value": "Gazetteer Service Profile of a WFS" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-042", + "@id": "http://www.opengis.net/def/docs/09-050r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-10-09" + "@value": "2009-07-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Tom Strickland" + "@value": "Hans Schoebach" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -15648,27 +15483,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1046" + "@id": "https://portal.ogc.org/files/?artifact_id=34032" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "01-042" + "@value": "09-050r1" }, { "@language": "en", - "@value": "Topic Domain 1 - Telecommunications Domain" + "@value": "OGC OWS-6-AIM Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Domain Model for telecommunications Networks" + "@value": "This report establishes a baseline for the technical architecture, its alternatives and issues for implementing the use cases as specified in the OWS-6 AIM thread RFQ including the temporal WFS supporting the temporal FE 2.0 operators, the Event Service Notification architecture and the client EFBs. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -15679,35 +15514,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-042" + "@value": "09-050r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic Domain 1 - Telecommunications Domain" + "@value": "OGC OWS-6-AIM Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-076r3", + "@id": "http://www.opengis.net/def/docs/04-038r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-09-14" + "@value": "2005-04-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Uwe Voges, Kristian Senkler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -15717,27 +15552,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=35042" + "@id": "https://portal.ogc.org/files/?artifact_id=8305" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Uses and summary of Topic 02 - Spatial referencing by coordinates" + "@value": "04-038r2" }, { "@language": "en", - "@value": "09-076r3" + "@value": "ISO19115/ISO19119 Application Profile for CSW 2.0 (CAT2 AP ISO19115/19)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document first discusses the uses for data sharing, and then provides a brief summary, of OGC Abstract Specification Topic 2: Spatial referencing by coordinates. Topic 2 is almost the same as ISO 19111:2007, but includes some corrections. This document includes some best practices for using Coordinate Reference Systems (CRSs)." + "@value": "This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -15748,30 +15583,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-076r3" + "@value": "04-038r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Uses and summary of Topic 2 - Spatial referencing by coordinates" + "@value": "ISO19115/ISO19119 Application Profile for CSW 2.0 (CAT2 AP ISO19115/19)" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-055", + "@id": "http://www.opengis.net/def/docs/15-027r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-11-23" + "@value": "2016-01-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steve Miller" + "@value": "Aleksandar Balaban" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -15786,17 +15621,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=44939" + "@id": "https://portal.ogc.org/files/?artifact_id=64141" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-055" + "@value": "15-027r1" }, { "@language": "en", - "@value": "OGC SAA Pilot Study Engineering Report" + "@value": "Testbed 11 Digital Notice to Airmen (NOTAM) Validation and Enrichment Service Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -15806,7 +15641,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document describes the architecture used for the implementation of the SAA Dissemination Pilot Study demonstrations. This includes an overview of the implemented components and workflows, and discussions of lessons learned." + "@value": "This OGC Engineering Report (ER) is a deliverable of the OGC Testbed 11. This ER describes the Digital Notice to Airmen (NOTAM) enrichment and validation services in the Testbed 11 Aviation thread, including:\r\n•\tA description of the architecture and architectural options.\r\n•\tAn overview of the implemented components and workflows followed by a short description of each component.\r\n•\tDocumentation of the issues, lessons learned as well as accomplishments and scenarios that were of general interest in the Aviation thread.\r\nMore detailed information on other specific aspects considered in OWS-11 Aviation may be found in the individual Aviation Engineering Reports.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -15817,35 +15652,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-055" + "@value": "15-027r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC SAA Pilot Study Engineering Report" + "@value": "OGC® Testbed 11 Digital Notice to Airmen (NOTAM) Validation and Enrichment Service Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-026r1", + "@id": "http://www.opengis.net/def/docs/16-003r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-11-22" + "@value": "2018-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -15855,27 +15690,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39968" + "@id": "https://portal.ogc.org/files/16-003r3" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Filter Encoding 2.0 Encoding Standard" + "@value": "16-003r3" }, { "@language": "en", - "@value": "09-026r1" + "@value": "Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This International Standard describes an XML and KVP encoding of a system neutral syntax for expressing projections, selection and sorting clauses collectively called a query expression.\r\nThese components are modular and intended to be used together or individually by other standards which reference this International Standard." + "@value": "This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids key words." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -15886,35 +15721,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-026r1" + "@value": "16-003r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Filter Encoding 2.0 Encoding Standard" + "@value": "Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-068r2", + "@id": "http://www.opengis.net/def/docs/01-061", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-08-19" + "@value": "2001-08-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona;Roger Brackin" + "@value": "Raj Singh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -15924,27 +15759,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64189" + "@id": "https://portal.ogc.org/files/?artifact_id=1072" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-068r2" + "@value": "01-061" }, { "@language": "en", - "@value": "Testbed 11 GeoPackaging Engineering Report" + "@value": "Web Terrain Server" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Mobile location based service applications and users have an increasing need for access to geospatial data from any place in the world, including locations with limited or intermittent connectivity to communications networks. Maintaining consistency between copies of the same data held by different mobile devices can be a significant challenge when connectivity is limited or intermittent. This OGC Engineering Report describes the work carried out in OGC Testbed-11 in relation to the creation and synchronization of SQLite databases that conform to the OGC GeoPackage standard . This Engineering Report describes an approach for the use of various standards to achieve such synchronization. The document also presents the results and lessons learnt from the experimentation conducted in the Testbed." + "@value": "The purpose of theWeb Terrain Server (WTS) is to produce perspective views of georeferenced data - typically 3-dimensional coverages." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -15955,35 +15790,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-068r2" + "@value": "01-061" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 11 GeoPackaging Engineering Report" + "@value": "Web Terrain Server" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-122r2", + "@id": "http://www.opengis.net/def/docs/11-064r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-04-08" + "@value": "2011-11-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthew Williams, Dan Cornford, Lucy Bastin & Edzer Pebesma" + "@value": "Clemens Portele, Reinhard Erstling" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -15993,27 +15828,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=33234" + "@id": "https://portal.ogc.org/files/?artifact_id=46324" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-122r2" + "@value": "OWS-8 CCI Schema Automation Engineering Report" }, { "@language": "en", - "@value": "Uncertainty Markup Language (UnCertML)" + "@value": "11-064r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Uncertainty Markup Language (UncertML) is an XML encoding for the transport and storage of information about uncertain quantities, with emphasis on quantitative representations based on probability theory. " + "@value": "This OGC® document specifies improvements to the processing of information represented in or referenced from an application schema in UML to create derived, implementation level resources, in particular:\r\n•\tXML Schema documents to represent types and their properties\r\n•\tSchematron schema documents to represent constraints\r\n•\tXSLT-Stylesheets to create KML instances of features\r\nThe documented improvements have been specified, implemented in the ShapeChange tool and tested in the context of schemas developed as part of the NGA's Topographic Data Store (TDS) schemas.\r\nThe work is a continuation of the work documented in OGC® document 10-088r2, the OWS-7 Schema Automation Engineering Report. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16024,35 +15859,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-122r2" + "@value": "11-064r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Uncertainty Markup Language (UnCertML)" + "@value": "OWS-8 CCI Schema Automation Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-025", + "@id": "http://www.opengis.net/def/docs/05-115", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-11-01" + "@value": "2006-03-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Joana Simoes, Tom Kralidis, Martin Desruisseaux, Angelos Tzotsos" + "@value": "Joe Lewis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -16062,27 +15897,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-025.html" + "@id": "https://portal.ogc.org/files/?artifact_id=12899" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "2023 Open Standards and Open Source Software Code Sprint Summary Engineering Report" + "@value": "05-115" }, { "@language": "en", - "@value": "23-025" + "@value": "Geo Video Web Service" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from the 25th to the 27th of April 2023 to advance support of open geospatial standards within the developer community, while also advancing the standards themselves. The code sprint was organized by the Open Geospatial Consortium (OGC), the Open Source Geospatial Foundation (OSGeo), and the Apache Software Foundation (ASF). The code sprint was sponsored by the Ordnance Survey and hosted by Camptocamp." + "@value": "A GeoVideo Web Service (GVS) is a web service that facilitates the viewing of live and/or archived feeds from video cameras. The feeds may be composed of:\r\n- A video stream\r\n- Textual data in a caption stream (e.g. GPS data, camera states and characteristics, custom XML data, such as SensorMLTML)\r\n- A combination of a video stream and associated textual data\r\nThe video streams of the feed may be viewed in the Windows Media Player. The textual data is extracted through scripting events that are generated as the caption stream is processed and displayed by the Windows Media Player." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16093,35 +15928,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-025" + "@value": "05-115" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "2023 Open Standards and Open Source Software Code Sprint Summary Engineering Report" + "@value": "Geo Video Web Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-005r4", + "@id": "http://www.opengis.net/def/docs/03-006r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2003-06-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Marwa Mabrouk" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -16131,27 +15966,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/16-005r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=3839" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-005r4" + "@value": "Location Services (OpenLS): Core Services [Parts 1-5]" }, { "@language": "en", - "@value": "Volume 2: OGC CDB Core Model and Physical Structure Annexes (Best Practice)" + "@value": "03-006r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the Annexes for the CDB Core: Model and Physical Structure Standard. The only exception is Annex A, Abstract Test Suite (ATS). The CDB ATS Annex is in Volume 1: Core document." + "@value": "OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16162,35 +15997,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-005r4" + "@value": "03-006r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 2: OGC CDB Core Model and Physical Structure Annexes (Best Practice)" + "@value": "OpenGIS Location Services (OpenLS): Core Services [Parts 1-5]" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-043", + "@id": "http://www.opengis.net/def/docs/11-053r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-03-10" + "@value": "2014-03-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Peter Baumann, Jinsongdi Yu" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -16200,27 +16035,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-043.html" + "@id": "https://portal.ogc.org/files/?artifact_id=54209" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Web Integration Service" + "@value": "Web Coverage Service Interface Standard - CRS Extension" }, { "@language": "en", - "@value": "16-043" + "@value": "11-053r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "For many years OGC has been developing a suite of standards defining web services interfaces and encodings for geospatial processing. The suite includes a Web Map Service (WMS), a Web Map Tiling Service (WMTS), a Web Feature Service (WFS), a Web Coverage Service (WCS), a Web Catalogue Service (CSW), the Sensor Web (SWE) suite of services, etc. These service interfaces and their implementations have, more or less, been developed independently of one another resulting in isolation and poor integration between them. For example, consider a map generated by a WMS. A client or user cannot easily determine which source data was used to create the map and how to download that source data though an OGC data service such as WFS or WCS. Furthermore when one considers the Publish-Find-Bind paradigm, OGC can only partially support the full potential of this paradigm. This is because OGC structured catalogues can only register services in isolation of other related services and cannot automatically determine the relationships among services and the resources they offer.\r\n\r\nIn order to achieve better integration between OGC web services and enhance the publish-find-bind paradigm, this OGC Engineering Report defines and discusses three key elements. These are:\r\n\r\nDefining a new service, called the Web Integration Service (WIS), which allows for the discovery and access to integrated sets of OGC web services deployed at an endpoint.\r\n\r\nSpecifying a means of discovering and describing associations between web resources (both OGC and non-OGC).\r\n\r\nDefining extensions to the OGC catalogue to allow the service to harvest and make discoverable a rich set of linked OGC and non-OGC resources.\r\n\r\nThe Web Integration Service (WIS) is an aggregation service whose only purpose is to provide a list of references to a suite of other, perhaps related OGC services available at an endpoint.\r\n\r\nA new operation, named GetAssociations, is defined as an extension such that existing OGC services (WMS, WFS, WCS, etc.) may implement this operation in order to support rich auto-discovery. This operation enables OGC web services to externalize their internal association knowledge about their content and relationships to other OGC and external resources. For example, a WMS would know if the source data for a layer it offers is a Shapefile, or a WFS feature type, or another WMS layer (i.e. cascading), or if a WMTS layer exists that renders the same information more efficiently. This internal knowledge can now be externalized via the GetAssociations operation.\r\n\r\nCurrently, OGC Catalogues Service instances can harvest the capabilities document of an OGC web service, register that service, register the existence of the individual offerings that the service offers and also register the association between the service and the content it offers. Thus, the entire harvesting process is focused on a single OGC web service and consequently offers a limited scope of discovery. In order to support rich discovery, a catalogue needs to be able to automatically register services found at an endpoint as well as register all known associations among those services, their offerings and other OGC and non-OGC resources. This involves harvesting a service’s capabilities document to determine what content the service offers but it also involves further interrogating the service to determine of what (if any) other associations it is aware. Populated with this enhanced knowledge a client may now use a catalogue to, for example, find the description of feature data and then be able to find the WFS that offer that data, a WMS that renders those features into a map, a WMTS that has a tiled representation of that data, etc. In order to support this kind of rich discovery, a new CSW-ebRIM package is specified that defines ebRIM object types, associations, classifications and stored queries that support the description of integrated OGC web service and their artifacts within the catalogue." + "@value": "This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request that allows a client, a service, or other application to specify the Coordinate Reference System (CRS) in which coverages are delivered. Note that the CRS of the input bounding box is already defined in the OGC WCS Core Implementation Standard [OGC 09-110r3]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16231,35 +16066,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-043" + "@value": "11-053r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Web Integration Service" + "@value": "OGC® Web Coverage Service Interface Standard - CRS Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-039r1", + "@id": "http://www.opengis.net/def/docs/10-099r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-07" + "@value": "2010-10-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -16269,27 +16104,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21469" + "@id": "https://portal.ogc.org/files/?artifact_id=39852" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "KML 2.1 Reference - An OGC Best Practice" + "@value": "10-099r2" }, { "@language": "en", - "@value": "07-039r1" + "@value": "Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "KML is a file format used to display geographic data in an Earth browser, such as Google Earth, Google Maps, and Google Maps for Mobile. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard." + "@value": "This document provides revision notes for version 2.0 of the OpenGIS® Implementation Specification Geography Markup Language (GML) simple feature profile." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16300,30 +16135,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-039r1" + "@value": "10-099r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "KML 2.1 Reference - An OGC Best Practice" + "@value": "Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-120r5", + "@id": "http://www.opengis.net/def/docs/07-118r9", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-19" + "@value": "2014-04-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "P. Denis, P. Jacques" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -16338,17 +16173,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=82376" + "@id": "https://portal.ogc.org/files/?artifact_id=54929" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-120r5" + "@value": "07-118r9" }, { "@language": "en", - "@value": "Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure" + "@value": "User Management Interfaces for Earth Observation Services" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -16358,7 +16193,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The CDB standard defines a standardized model and structure for a single, “versionable,” virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time." + "@value": "This OGC Best Practice describes how user and identity management information may be included in the protocol specifications for OGC Services. The proposed approach is applicable to the orchestration of EO services, to system of systems and federation scenarios. The approach is meant to be independent from the specific OGC service. The use cases potentially addressed are very wide and in general may cover geospatial services and not only EO (Earth Observation) services. The use cases may range from web map, feature or coverage services, web processing services, to catalogue services. Examples of EO specific use cases are: ordering (Ordering Services for Earth Observation Products [OGC 06-141r6]) and feasibility analysis (OpenGIS Sensor Planning Service Application Profile for EO Sensors [OGC 10 135]). \r\nThe document was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [OR1] and related projects.\r\nThis document is not an OGC standard. This document describes how existing specifications from W3C and OASIS can be used in combination to pass identity information to OGC Web services.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16369,35 +16204,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-120r5" + "@value": "07-118r9" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure" + "@value": "OGC User Management Interfaces for Earth Observation Services" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-015", + "@id": "http://www.opengis.net/def/docs/21-035r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-01-27" + "@value": "2022-03-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Barry Schlesinger" + "@value": "Ronald Tse, Nick Nicholas" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -16407,27 +16242,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8826" + "@id": "https://docs.ogc.org/per/21-035r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Imagery Metadata" + "@value": "21-035r1" }, { "@language": "en", - "@value": "05-015" + "@value": "OGC Testbed-17: Model-Driven Standards Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Special XML schemas have been created for individual data sets, based on ISO 19115 and a general schema for the RSE. However, a generalized metadata XML schema should be available where possible; it should not be necessary to create special schemas for each data set. ISO 19139 can serve as such a general XML implementation specification for 19115. This implementation needs to be tested in practice. In addition, the new ISO standards are incorporating much, if not all, of the metadata not in 19115 that the RSE contain. XML schemas for these metadata need to be developed that are based upon the abstract model in the ISO standards. All of these implementations need to be tested in practice. This Report describes such tests and the results. It also describes to what extent metadata on which the test metadata are based are supported by 19139, to what extent they are supported by metadata specified in the new ISO standards or the RSE, and to what extent new metadata elements are needed. " + "@value": "This OGC Testbed 17 Engineering Report is deliverable D022 of the OGC Testbed 17 initiative performed under the OGC Innovation Program, incorporating the D022, D143 and D144 tasks that have produced Model Driven Architecture (MDA) tools.\r\n\r\nThis ER:\r\n\r\ndetails state-of-the-art analyses of existing MDA tools with their capabilities and limits; and\r\n\r\nprovides clear recommendations on how model-driven design can be fully exploited in the context of rich data model and API design efforts.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16438,46 +16273,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-015" + "@value": "21-035r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Imagery Metadata" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/pc", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/06-111" - }, - { - "@id": "http://www.opengis.net/def/docs/06-113" + "@value": "OGC Testbed-17: Model-Driven Standards Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-086r5", + "@id": "http://www.opengis.net/def/docs/15-053r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-08-05" + "@value": "2015-08-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mark Burgoyne, David Blodgett, Charles Heazel, Chris Little" + "@value": "Joan Masó" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -16487,27 +16311,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/19-086r5/19-086r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=64595" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-086r5" + "@value": "15-053r1" }, { "@language": "en", - "@value": "OGC API - Environmental Data Retrieval Standard" + "@value": "Testbed 11 Implementing JSON/GeoJSON in an OGC Standard Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Environmental Data Retrieval (EDR) Application Programming Interface (API) provides a family of lightweight query interfaces to access spatio-temporal data resources by requesting data at a Position, within an Area, along a Trajectory or through a Corridor. A spatio-temporal data resource is a collection of spatio-temporal data that can be sampled using the EDR query pattern geometries. These patterns are described in the section describing the Core Requirements Class.\r\n\r\nThe goals of the EDR API are to make it easier to access a wide range of data through a uniform, well-defined simple Web interface, and to achieve data reduction to just the data needed by the user or client while hiding much of the data storage complexity. A major use case for the EDR API is to retrieve small subsets from large collections of environmental data, such as weather forecasts, though many other types of data can be accessed. The important aspect is that the data can be unambiguously specified by spatio-temporal coordinates.\r\n\r\nThe EDR API query patterns, such as Position, Area, Cube, Trajectory or Corridor, can be thought of as discrete sampling geometries, conceptually consistent with the feature of interest in the Sensor Observation Service (SOS) standard. A typical EDR data resource is a multidimensional dataset that could be accessed via an implementation of the Web Coverage Service (WCS) standard. In contrast to SOS and WCS, the EDR API implements the technical baseline of the OGC API family of standards and aims to provide a single set of simple-to-use query patterns. Use cases for EDR range from real or virtual time-series observation retrievals, to sub-setting 4-dimensional data cubes along user-supplied sampling geometries. These query patterns do not attempt to satisfy the full scope of either SOS or WCS, but provide useful building blocks to allow the composition of APIs that satisfy a wide range of geospatial data use cases. By defining a small set of query patterns (and no requirement to implement all of them), the EDR API should help to simplify the design of systems (as they can be performance tuned for the supported queries) making it easier to build robust and scalable infrastructure.\r\n\r\nWith the OGC API family of standards, the OGC community has extended its suite of standards to include Resource Oriented Architectures and Web Application Programming Interfaces (APIs). These standards are based on a shared foundation, specified in OGC API-Common, which defines the resources and access paths that are supported by all OGC APIs. The resources are listed in Table 1. This document extends that foundation to define the Environmental Data Retrieval API." + "@value": "In the OGC Testbed 11, the Cross-Community Interoperability (CCI) thread had a key objective of building on the work accomplished in the OGC 8, 9 and 10 Testbeds. The goal of the CCI threads is to increase interoperability between communities sharing geospatial data. This thread made advances in semantic mediation approaches for data discovery, access and use of heterogeneous data models and heterogeneous metadata models. This particular Engineering Report (ER) is part of the OGC efforts to advance the OGC Architecture with the adoption of REST interfaces and more encodings such as JSON." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16518,35 +16342,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-086r5" + "@value": "15-053r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Environmental Data Retrieval Standard" + "@value": "OGC® Testbed 11 Implementing JSON/GeoJSON in an OGC Standard Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-010r6", + "@id": "http://www.opengis.net/def/docs/20-037", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-07-02" + "@value": "2020-10-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steve Havens" + "@value": "Samantha Lavender" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -16556,27 +16380,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=19371" + "@id": "https://docs.ogc.org/per/20-037.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Transducer Markup Language" + "@value": "20-037" }, { "@language": "en", - "@value": "06-010r6" + "@value": "OGC Earth Observation Applications Pilot: Pixalytics Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*THIS STANDARD HAS BEEN RETIRED* \r\n\r\nThe OpenGIS® Transducer Markup Language Encoding Standard (TML) is an application and presentation layer communication protocol for exchanging live streaming or archived data to (i.e. control data) and/or sensor data from any sensor system. A sensor system can be one or more sensors, receivers, actuators, transmitters, and processes. A TML client can be capable of handling any TML enabled sensor system without prior knowledge of that system.\r\n \r\nThe protocol contains descriptions of both the sensor data and the sensor system itself. It is scalable, consistent, unambiguous, and usable with any sensor system incorporating any number sensors and actuators. It supports the precise spatial and temporal alignment of each data element. It also supports the registration, discovery and understanding of sensor systems and data, enabling users to ignore irrelevant data. It can adapt to highly dynamic and distributed environments in distributed net-centric operations.\r\n \r\nThe sensor system descriptions use common models and metadata and they describe the physical and semantic relationships of components, thus enabling sensor fusion.\r\n\r\nThis is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards.\r\n" + "@value": "This is an individual Engineering Report (ER) created by Pixalytics Ltd as part of the Earth Observation Applications Pilot. Pixalytics' role was that of an App developer, testing deployment to the OGC Earth Observation Applications Pilot architecture." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16587,35 +16411,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-010r6" + "@value": "20-037" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Transducer Markup Language *RETIRED*" + "@value": "OGC Earth Observation Applications Pilot: Pixalytics Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-093r1", + "@id": "http://www.opengis.net/def/docs/16-086r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-08-22" + "@value": "2018-04-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler, Ashley Antonides" + "@value": "Jürgen Seib, Marie-Françoise Voidrot-Martinez, Chris Little" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -16625,27 +16449,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-093r1.html" + "@id": "https://docs.ogc.org/bp/16-086r3/16-086r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GeoPackage Related Tables Extension Interoperability Experiment Engineering Report" + "@value": "16-086r3" }, { "@language": "en", - "@value": "17-093r1" + "@value": "Best Practice for using Web Map Services (WMS) with Ensembles of Forecast Data" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report describes the results of the OGC GeoPackage (GPKG) Related Tables Extension Interoperability Experiment (GPKG-RTE IE). This IE tested a proposed extension to the OGC GeoPackage Encoding Standard (12-128r14). The GPKG-RTE defines the rules and requirements for associating tables with existing feature or attribute tables in a GeoPackage data store. As part of this IE, the participants performed Technology Integration Experiments (TIEs) where they produced GeoPackages that used this extension, loaded them into GPKG-compliant software systems, and observed the results. As a result of this work, the IE participants agree that the extension is fit for use and consideration as a standard by OGC." + "@value": "This document proposes a set of best practices and guidelines for implementing and using the Open Geospatial Consortium (OGC) Web Map Service (WMS) to serve maps which are members of an ensemble of maps, each of which is a valid possible alternative for the same time and location. In the meteorological and oceanographic communities, it is Best Practice to produce a large number of simultaneous forecasts, whether for a short range of hours, a few days, seasonal or climatological predictions. These ensembles of forecasts indicate the probability distributions of specific outcomes. This document describes how to unambiguously specify an individual member of an ensemble, or one of a limited set of map products derived from a full ensemble. \r\nIn particular, clarifications and restrictions on the use of WMS are defined to allow unambiguous and safe interoperability between clients and servers, in the context of expert meteorological and oceanographic usage and non-expert usage in other communities. This Best Practice document applies specifically to WMS version 1.3, but many of the concepts and recommendations will be applicable to other versions of WMS or to other OGC services, such as the Web Coverage Service.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16656,35 +16480,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-093r1" + "@value": "16-086r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoPackage Related Tables Extension Interoperability Experiment Engineering Report" + "@value": "OGC Best Practice for using Web Map Services (WMS) with Ensembles of Forecast Data" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-007r1", + "@id": "http://www.opengis.net/def/docs/10-069r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-06-06" + "@value": "2010-08-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Watson" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -16694,27 +16518,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21821" + "@id": "https://portal.ogc.org/files/?artifact_id=39476" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS4 - Topology Quality Assessment Interoperability Program Report" + "@value": "OWS-7 Engineering Report - Geosynchronization service" }, { "@language": "en", - "@value": "07-007r1" + "@value": "10-069r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the purpose and function of the Topology Quality Assessment Service developed and deployed within the Geo-processing workflow thread of the OWS4 interoperability testbed." + "@value": "This candidate standard describes a service that allows data collectors to propose changes to be made to a data provider's features. A change proposal can be made to create new data or to modify/delete existing data. Proposed changes are reviewed (either manually or automatically) an are either accepted or rejected. Accepted changes are applied to the feature(s). The service also maintains a log of all changes applied to each feature that can be used for replication." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16725,30 +16549,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-007r1" + "@value": "10-069r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS4 - Topology Quality Assessment Interoperability Program Report" + "@value": "OWS-7 Engineering Report - Geosynchronization service" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-036", + "@id": "http://www.opengis.net/def/docs/10-002", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-01-21" + "@value": "2014-04-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Guy Schumann" + "@value": "Raj Singh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -16763,17 +16587,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-036.html" + "@id": "https://portal.ogc.org/files/?artifact_id=37839" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: Moving Features ER" + "@value": "10-002" }, { "@language": "en", - "@value": "21-036" + "@value": "Climate Challenge Integration Plugfest 2009 Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -16783,7 +16607,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Testbed-17 Moving Features (MF) task addressed the exchange of moving object detections, shared processing of detections for correlation and analysis, and visualization of moving objects within common operational pictures. This Engineering Report (ER) explores and describes an architecture for collaborative distributed object detection and analysis of multi-source motion imagery, supported by OGC MF standards. The ER presents the proposed architecture, identifies the necessary standards, describes all developed components, reports on the results of all TIE activities, and provides a description of recommended future work items." + "@value": "This OGC Engineering Report (ER) documents findings of the CCIP 2009 Plugfest, which was conducted via the public Internet to address requirements stated in the CCIP Call for Participation . It addresses concept development, specifications tested, and interoperability experiments conducted. The ER concludes with issues that arose, and provides recommendations for the refinement of OGC Specifications and the Plugfest process. Recommendations in this ER will be considered in the planning of future activities.\r\nOGC expresses thanks to the Australian Bureau of Meteorology and to CSIRO for sponsoring CCIP 2009.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16794,35 +16618,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-036" + "@value": "10-002" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: Moving Features ER" + "@value": "OGC® Climate Challenge Integration Plugfest 2009 Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-021r2", + "@id": "http://www.opengis.net/def/docs/03-007r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2003-06-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Aleksandar Balaban" + "@value": "Tom Bychowski" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -16832,27 +16656,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-021r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=3840" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: Data Centric Security Engineering Report" + "@value": "Location Services (OpenLS): Navigation Service [Part 6]" }, { "@language": "en", - "@value": "20-021r2" + "@value": "03-007r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Testbed-16 Data Centric Security Engineering Report (ER) continues the evaluation of a data-centric security (DCS) approach in a geospatial environment. In order to fully explore the potential of the DCS concept, this ER first specifies two advanced use case scenarios: Data Streaming and Offline Authorization for querying and consuming protected geospatial content. The ER then specifies the communication with a new architectural component called the Key Management Server (KMS) via an Application Programming Interface (API) created for this Testbed. The API was invoked to register keys used to encrypt data-centric protected content. Then clients called the same API to obtain those keys to perform the data verification/decryption.\r\n\r\n" + "@value": "OpenGIS " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16863,35 +16687,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-021r2" + "@value": "03-007r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: Data Centric Security Engineering Report" + "@value": "OpenGIS Location Services (OpenLS): Navigation Service [Part 6]" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-040", + "@id": "http://www.opengis.net/def/docs/00-029", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-02-17" + "@value": "2000-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Bill Lalonde" + "@value": "Ron Lake" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -16901,27 +16725,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7470" + "@id": "https://portal.ogc.org/files/?artifact_id=7197" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-040" + "@value": "00-029" }, { "@language": "en", - "@value": "Style Management Services for Emergency Mapping Symbology" + "@value": "Geography Markup Language" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the proposed system design for the OGC Style Management Service (SMS). \r\nThe SMS must manage distinct objects that represent styles and symbols and provide the means to discover, query, insert, update, and delete these objects. \r\nStyles provide the mapping from feature types and feature properties and constraints to parameterized Symbols used in drawing maps. Symbols are bundles of predefined graphical parameters and predefined fixed graphics.\r\n" + "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -16932,35 +16756,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-040" + "@value": "00-029" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Style Management Services for Emergency Mapping Symbology" + "@value": "Geography Markup Language" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-001r1", + "@id": "http://www.opengis.net/def/docs/06-141r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-01-09" + "@value": "2012-01-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lieven Raes, Danny Vandenbroucke, Tomas Reznik" + "@value": "Daniele Marchionni, Stefania Pappagallo " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -16970,27 +16794,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=82475" + "@id": "https://portal.ogc.org/files/?artifact_id=43928" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-001r1" + "@value": "06-141r6" }, { "@language": "en", - "@value": "GeoDCAT-AP" + "@value": "Ordering Services Framework for Earth Observation Products Interface Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Improving discoverability of open geo-data and information is vital to increasing the use of these data in- and outside the geospatial expert community. \r\nIn this document we start to compare existing metadata standards, e.g., Dublin Core, ISO 19115/57/19, and INSPIRE, in the geospatial- and open data context. We also describe related linked open data initiatives such as RDF, SPARQL, and metadata publication initiatives, e.g., schema.org and Atom feeds. GeoDCAT is an initiative with the potential to integrate DCAT metadata as they are used in the open data and e-government community with EN ISO 19115/57/19 standards and INSPIRE metadata as they are used in the Geospatial community. GeoDCAT has - because it is based on RDF- the ability to publish metadata directly on the web without open and geospatial data portals.\r\nTo respond to the interest of different communities to preserve geospatial metadata resources and to support the uptake of GeoDCAT-AP implementations, best practices from different countries were identified and studied. The best practice cases focus on four domains (focus areas): metadata input (manually or automatically harvested), metadata publication into an integrated geo/open data portal, publication of metadata as Linked Open Data (LOD), and information mapping (ISO 19115, INSPIRE, DCAT, etc.).\r\nGeoDCAT-AP is a mature solution for mapping metadata from the open data and geospatial domain. GeoDCAT helps to integrate and to publish metadata in data portals and directly on the world wide web. To conclude a GeoDCAT alignment exercise has been done with ISO 19115/19 and INSPIRE to improve the open data and geospatial metadata alignment in the future.\r\n" + "@value": "This OGC® standard specifies the interfaces, bindings, requirements, conformance classes, and a framework for implementing extensions that enable complete workflows for ordering of Earth Observation (EO) data products. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17001,35 +16825,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-001r1" + "@value": "06-141r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GeoDCAT-AP" + "@value": "Ordering Services Framework for Earth Observation Products Interface Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-122r2", + "@id": "http://www.opengis.net/def/docs/15-037", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-11-12" + "@value": "2015-10-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mike Botts, Simon Cox" + "@value": "George Percivall " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17039,27 +16863,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=24757" + "@id": "https://portal.ogc.org/files/?artifact_id=63334" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "SensorML Encoding Standard v 1.0 Schema Corregendum 1" + "@value": "15-037" }, { "@language": "en", - "@value": "07-122r2" + "@value": "OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Changes to the 1.0 schemas" + "@value": "Responding to an oil spill requires access to and understanding of many types of information. Effective, coordinated operations for the response are based on a shared, common picture of the situation. Interoperability provides shared situational awareness of the crisis and the response activities. What is needed is a common picture of reality for different organizations that have different views of the spill so that they all can deal with it collectively.\r\nRecent oil spills have provided lessons learned and recommendations on forming a Common Operating Picture for oil spill response. Through a joint project, industry is responding to the call, moving from recommendations to reusable best practices supported by open standards that can be deployed quickly in any region of the globe.\r\nThis architecture report is part of The International Association of Oil & Gas Producers and IPIECA Oil Spill Response - Joint Industry Project (IOGP–IPIECA OSR-JIP) to produce a recommended practice for GIS/mapping in support of oil spill response and for the use of GIS technology and geospatial information in forming a “Common Operating Picture” to support management of the response.\r\nInteroperability seems to be at first a technical topic, but in fact, it is about organization. Interoperability seems to be about the integration of information. What it’s really about is the coordination of organizational behavior. The Oil Spill Response Common Operating Picture (OSR COP) project seeks to facilitate the coordination of organizational response to any oil spill in the future." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17070,35 +16894,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-122r2" + "@value": "15-037" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS SensorML Encoding Standard v 1.0 Schema Corregendum 1" + "@value": "OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-128r11", + "@id": "http://www.opengis.net/def/docs/03-029", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-04-20" + "@value": "2003-01-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul daisey" + "@value": "Stephane Fellah, Steven Keens" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-isc" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17108,27 +16932,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=63378" + "@id": "https://portal.ogc.org/files/?artifact_id=1315" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GeoPackage Encoding Standard – With Corrigendum" + "@value": "03-029" }, { "@language": "en", - "@value": "12-128r11" + "@value": "OWS Messaging Framework" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-isc" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a “native” storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." + "@value": "This document defines a messaging framework to conduct communications between the OGC web services. It is independent of any transport protocol and any messaging encoding. By using the framework, the service designer could focus only on the message definitions and messaging flows for every action supported by the service, without worry on the messaging transport and delivery. The framework should considerably simplify the implementations of the OGC web services and should enable service chaining." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17139,35 +16963,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-128r11" + "@value": "03-029" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GeoPackage Encoding Standard – With Corrigendum" + "@value": "OWS Messaging Framework" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-088", + "@id": "http://www.opengis.net/def/docs/07-012", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-02-20" + "@value": "2007-09-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Lunceford,Steve Matney,Tom Huggins,Chuck Heazel" + "@value": "Jennifer Marcus, Chuck Morris" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17177,27 +17001,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7561" + "@id": "https://portal.ogc.org/files/?artifact_id=20582" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-088" + "@value": "07-012" }, { "@language": "en", - "@value": "EA-SIG Mediation White Paper" + "@value": "Compliance Test Engine Interoperability Program Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*RETIRED* This document focuses on the goals, objectives, capabilities and recommendation for the Mediation Core Enterprise\r\nService." + "@value": "As a work item in the OWS4/Conformance and Interoperability Test and Evaluation (CITE) project, Northrop Grumman Information Technology (NGIT) provided an open source web services compliance engine. NGIT refers to this engine as the Test Evaluation And Measurement (TEAM) Engine. It executes scripts written in Compliance Test Language (CTL), a grammar also developed by NGIT. This IPR describes TEAM Engine in detail and provides information on how it was used in OWS-4/CITE." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17208,35 +17032,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-088" + "@value": "07-012" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "EA-SIG Mediation White Paper" + "@value": "Compliance Test Engine Interoperability Program Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-043r3", + "@id": "http://www.opengis.net/def/docs/07-169", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-09-09" + "@value": "2008-09-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "James Tomkins, Dominic Lowe " + "@value": "Steven Keens" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17246,27 +17070,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/15-043r3/15-043r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=27047" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-043r3" + "@value": "OWS-5 WCS JPIP Coverage Subsetting Engineering Report" }, { "@language": "en", - "@value": "Timeseries Profile of Observations and Measurements " + "@value": "07-169" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Timeseries Profile of Observations and Measurements is a conceptual model for the representation of observations data as timeseries, with the intent of enabling the exchange of such data sets across information systems. This standard does not define an encoding for the conceptual model; however there is an accompanying OGC Standard which defines an XML encoding (OGC TimeseriesML 1.0 - XML Encoding of the Timeseries Profile of Observations and Measurements). Other encodings may be developed in future." + "@value": "This OGC document represents an OWS-5 SWE thread Engineering Report on sub-setting georeferencable imagery. It discusses how to handle georeferencable imagery in the JPEG2000 format as well as using JPIP within the WCS-T and the SWE set of services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17277,35 +17101,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-043r3" + "@value": "07-169" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Timeseries Profile of Observations and Measurements " + "@value": "OWS-5 WCS JPIP Coverage Subsetting Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-156r2", + "@id": "http://www.opengis.net/def/docs/02-007r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-01-04" + "@value": "2002-08-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Luis Bermudez" + "@value": "John Bobbitt" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17315,27 +17139,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=37373" + "@id": "https://portal.ogc.org/files/?artifact_id=11498" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Ocean Science Interoperability Experiment Phase II Report " + "@value": "02-007r4" }, { "@language": "en", - "@value": "09-156r2" + "@value": "Units of Measure Recommendation" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report documents the work performed by the participants of the Ocean Science Interoperability Experiment Phase II. This work is a follow-on to the OGC Oceans IE Phase 1 activity. Specifically, this IE addressed the following tasks:\r\n•\tAutomated metadata/software installation via PUCK protocol.\r\n•\tOffering of complex systems (e.g. observations systems containing other systems) such as collection of stations.\r\n•\tLinking data from SOS to out-of-band offerings.\r\n•\tSemantic Registry and Services.\r\n•\tCatalogue Service-Web Registry.\r\n•\tIEEE-1451/OGC-SWE harmonization\r\n\r\nAs a result of this experiment, a number of recommendations and conclusions were identified.\r\n" + "@value": "Common semantic for units of measurement to be used across all OGC specifications." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17346,35 +17170,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-156r2" + "@value": "02-007r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Ocean Science Interoperability Experiment Phase II Report " + "@value": "Units of Measure Recommendation" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-110r4", + "@id": "http://www.opengis.net/def/docs/03-025", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-07-12" + "@value": "2003-01-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Josh Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17384,27 +17208,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=48428" + "@id": "https://portal.ogc.org/files/?artifact_id=1320" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "WCS 2.0 Interface Standard- Core: Corrigendum " + "@value": "03-025" }, { "@language": "en", - "@value": "09-110r4" + "@value": "Web Services Architecture" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies how a Web Coverage Service (WCS) offers multi-dimensional cov-erage data for access over the Internet. This document specifies a core set of requirements that a WCS implementation must fulfil. WCS extension standards add further functionality to this core; some of these are required in addition to the core to obtain a complete implementa-tion. This document indicates which extensions, at a minimum, need to be considered in ad-dition to this core to allow for a complete WCS implementation.\r\nThis core does not prescribe support for any particular coverage encoding format. This also holds for GML as a coverage delivery format: while GML constitutes the canonical format for the definition of WCS, it is not required by this core that a concrete instance of a WCS service implements the GML coverage format. WCS extensions specifying use of data encod-ing formats in the context of WCS are designed in a way that the GML coverage information contents specified in this core is consistent with the contents of an encoded coverage.\r\n" + "@value": "Specifies and discusses a common architectural framework for OGC Web Services" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17415,35 +17239,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-110r4" + "@value": "03-025" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® WCS 2.0 Interface Standard- Core: Corrigendum " + "@value": "Web Services Architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-057r7", + "@id": "http://www.opengis.net/def/docs/20-040r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-04-06" + "@value": "2021-09-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó, Keith Pomakis, Núria Julià" + "@value": "Robert Gibb" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17453,27 +17277,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=35326" + "@id": "https://docs.ogc.org/as/20-040r3/20-040r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-057r7" + "@value": "20-040r3" }, { "@language": "en", - "@value": "Web Map Tile Service Implementation Standard" + "@value": "Topic 21 - Discrete Global Grid Systems - Part 1 Core Reference system and Operations and Equal Area Earth Reference System" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Web Map Tile Service (WMTS) Implementation Standard provides a standard based solution to serve digital maps using predefined image tiles. The service advertises the tiles it has available through a standardized declaration in the ServiceMetadata document common to all OGC web services. This declaration defines the tiles available in each layer (i.e. each type of content), in each graphical representation style, in each format, in each coordinate reference system, at each scale, and over each geographic fragment of the total covered area. The ServiceMetadata document also declares the communication protocols and encodings through which clients can interact with the server. Clients can interpret the ServiceMetadata document to request specific tiles." + "@value": "This Abstract Specification lays the foundations for Discrete Global Grid Systems (DGGS). It defines Common classes for spatio-temporal geometry, topology, and reference systems using identifiers, a DGGS Core Reference system as a reference system using zonal identifiers with structured geometry that may be spatio-temporal, a suite of DGGS Core Functions, and it specifies Equal-Area Earth DGGS. The OGC DGGS Abstract Specification supports the specification of standardized DGGS infrastructures that enable the integrated analysis of very large, multi-source, multi-resolution, multi-dimensional, distributed geospatial data. Interoperability between OGC DGGS implementations is anticipated through implementation standards, and extension interface encodings of OGC Web Services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17484,35 +17308,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-057r7" + "@value": "20-040r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Map Tile Service Implementation Standard" + "@value": "Topic 21 - Discrete Global Grid Systems - Part 1 Core Reference system and Operations and Equal Area Earth Reference System" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-105", + "@id": "http://www.opengis.net/def/docs/17-011r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2018-01-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó" + "@value": "Alex Robin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17522,27 +17346,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=52018" + "@id": "https://docs.ogc.org/bp/17-011r2/17-011r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-9 - OWS Context evaluation IP Engineering Report" + "@value": "JSON Encoding Rules SWE Common / SensorML" }, { "@language": "en", - "@value": "12-105" + "@value": "17-011r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report describes the results of the OWS-9 IP on OWS Context 1.0. OWS Context is a draft OGC candidate standard. The OWS Context activity tested and evaluated the relative benefits of different encoding methods prior to finalization of the candidate standard. OWS Context has been proposed with an Atom encoding, a JSON encoding and an HTML5 encoding. The encoding requirement seeks to understand the level of mass-market acceptance of these different encoding options and their ability to support mash-ups. Each encoding should be evaluated, including examples and recommendations to move forward. Recommendations should enable the OWS Context capability for OGC services while remaining cognizant of implementations using mass-market technologies." + "@value": "This document describes new JavaScript Object Notation (JSON) encodings for the Sensor Web Enablement (SWE) Common Data Model and the Sensor Model Language (SensorML). Rather than creating new JSON schemas, this document defines encoding rules that allow auto-generation of JSON instances that conform to the Unified Modeling Language (UML) models. Alternatively, the mappings given in the second part of the document can be used to convert bi-directionally between XML and JSON representations.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17553,35 +17377,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-105" + "@value": "17-011r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-9 - OWS Context evaluation IP Engineering Report" + "@value": "JSON Encoding Rules SWE Common / SensorML" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-104r1", + "@id": "http://www.opengis.net/def/docs/18-075", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2019-01-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17591,27 +17415,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=52065" + "@id": "https://docs.ogc.org/is/18-075/18-075.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-9 Engineering Report - CCI - Single Point of Entry Global Gazetteer" + "@value": "18-075" }, { "@language": "en", - "@value": "12-104r1" + "@value": "Moving Features Encoding Part I: XML Core" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides a technical description of the Single Point of Entry Global Gazetteer (SPEGG) implemented for the OWS9 test bed. The SPEGG integrates two gazetteers – a copy of the USGS gazetteers containing domestic names (hosted by CubeWerx Inc.) and the NGA gazetteer containing foreign names (originally hosted at NGA but currently hosted by Intergraph Corp.). Both integrated gazetteers and the SPEGG implement the Web Feature Service (WFS) standard." + "@value": "This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17622,35 +17446,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-104r1" + "@value": "18-075" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-9 Engineering Report - CCI - Single Point of Entry Global Gazetteer" + "@value": "OGC® Moving Features Encoding Part I: XML Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-050r1", + "@id": "http://www.opengis.net/def/docs/12-094", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-04-22" + "@value": "2013-02-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Philippe Duschene, Jerome Sonnet" + "@value": "Debbie Wilson, Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17660,27 +17484,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=9541" + "@id": "https://portal.ogc.org/files/?artifact_id=51807" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-050r1" + "@value": "Aviation: AIRM Derivation" }, { "@language": "en", - "@value": "WMS Change Request: Support for WSDL & SOAP" + "@value": "12-094" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This change proposal is an outcome of the Common Architecture thread of the OpenGIS Web Service 2 initiative. The aim is to add support for a standard WSDL description of the WMS interface in version 1.3.1." + "@value": "This report describes the architecture, rules and tools developed within the OWS-9 Aviation Thread AIRM Derivation task. These rules and tools were demonstrated by transforming the AIRM Meteorology package into a Weather Exchange Model (WXXM) and GML/JSON implementation schema. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17691,25 +17515,25 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-050r1" + "@value": "12-094" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "WMS Change Request: Support for WSDL & SOAP" + "@value": "OWS-9 Aviation: AIRM Derivation" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-144r4", + "@id": "http://www.opengis.net/def/docs/11-091", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-02-05" + "@value": "2012-02-09" } ], "http://purl.org/dc/terms/creator": [ @@ -17719,7 +17543,7 @@ ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17729,27 +17553,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=31138" + "@id": "https://portal.ogc.org/files/?artifact_id=46094" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CSW-ebRIM Registry Service - Part 2: Basic extension package" + "@value": "OWS-8 Review of the WXXS exchange schemas" }, { "@language": "en", - "@value": "07-144r4" + "@value": "11-091" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Incorporates Corrigendum 1 (OGC 08-102r1)." + "@value": "This aim of this review is to assess the the WXXS 1.1.1 exchange schemas for\r\ncompliance with ISO 19136:2007 (GML 3.2.1). This international standard stipulates\r\nrules and recommendations regarding the construction of GML application schemas;\r\nthese constraints are documented in the following clauses:\r\n(a) Clause 7.1: GML model and syntax\r\n(b) Clause 21: Rules for GML application schemas\r\n(c) Annex A.1: Abstract test suite for GML application schemas" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17760,35 +17584,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-144r4" + "@value": "11-091" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CSW-ebRIM Registry Service - Part 2: Basic extension package" + "@value": "OWS-8 Review of the WXXS exchange schemas" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-008r3", + "@id": "http://www.opengis.net/def/docs/23-040", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-09-19" + "@value": "2024-07-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peng Yue, Boyi Shangguan" + "@value": "Ronald Tse, Carsten Roensdorf, Allan Jamieson, Nick Nicholas, Jeffrey Lau" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17798,27 +17622,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/23-008r3/23-008r3.html" + "@id": "https://docs.ogc.org/dp/23-040.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Training Data Markup Language for Artificial Intelligence (TrainingDML-AI) Part 1: Conceptual Model Standard" + "@value": "23-040" }, { "@language": "en", - "@value": "23-008r3" + "@value": "OGC Guidance for the Development of Model-Driven Standards" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Training Data Markup Language for Artificial Intelligence (TrainingDML-AI) Standard aims to develop the UML model and encodings for geospatial machine learning training data. Training data plays a fundamental role in Earth Observation (EO) Artificial Intelligence Machine Learning (AI/ML), especially Deep Learning (DL). It is used to train, validate, and test AI/ML models. This Standard defines a UML model and encodings consistent with the OGC Standards baseline to exchange and retrieve the training data in the Web environment.\r\n\r\nThe TrainingDML-AI Standard provides detailed metadata for formalizing the information model of training data. This includes but is not limited to the following aspects:\r\n\r\nHow the training data is prepared, such as provenance or quality;\r\nHow to specify different metadata used for different ML tasks such as scene/object/pixel levels;\r\nHow to differentiate the high-level training data information model and extended information models specific to various ML applications; and\r\nHow to introduce external classification schemes and flexible means for representing ground truth labeling." + "@value": "This OGC Discussion Paper provides guidelines on how to create a specification of a conceptual model through use of a Unified Modeling Language (UML) editor and an AsciiDoc compiler. This document references Sparx Systems Enterprise Architect and the Metanorma AsciiDoc toolchain in examples that implement the OGC model-driven standards process, described in OGC 21-035r1." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17829,35 +17653,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-008r3" + "@value": "23-040" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Training Data Markup Language for Artificial Intelligence (TrainingDML-AI) Part 1: Conceptual Model Standard" + "@value": "OGC Guidance for the Development of Model-Driven Standards" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-128r19", + "@id": "http://www.opengis.net/def/docs/02-070", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-02-06" + "@value": "2002-08-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Bill Lalonde" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17867,27 +17691,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://www.geopackage.org/spec140/index.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1188" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GeoPackage Encoding Standard" + "@value": "02-070" }, { "@language": "en", - "@value": "12-128r19" + "@value": "Styled Layer Descriptor (SLD) Implementation Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." + "@value": "The SLD is an encoding for how the Web Map Server (WMS 1.0 & 1.1) specification can be extended to allow user-defined symbolization of feature data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17898,35 +17722,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-128r19" + "@value": "02-070" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GeoPackage Encoding Standard" + "@value": "OpenGIS Styled Layer Descriptor (SLD) Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-052", + "@id": "http://www.opengis.net/def/docs/18-001r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-07-12" + "@value": "2019-01-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Lieven Raes, Danny Vandenbroucke, Tomas Reznik" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -17936,27 +17760,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=48650" + "@id": "https://portal.ogc.org/files/?artifact_id=82475" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "WCS 2.0.1 Corrigendum Release Notes" + "@value": "18-001r1" }, { "@language": "en", - "@value": "12-052" + "@value": "GeoDCAT-AP" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document represents the release notes for the OGC Web Coverage Service (WCS) Interface Standard corrigendum 2.0.1. This corrigendum for WCS supersedes previous WCS versions." + "@value": "Improving discoverability of open geo-data and information is vital to increasing the use of these data in- and outside the geospatial expert community. \r\nIn this document we start to compare existing metadata standards, e.g., Dublin Core, ISO 19115/57/19, and INSPIRE, in the geospatial- and open data context. We also describe related linked open data initiatives such as RDF, SPARQL, and metadata publication initiatives, e.g., schema.org and Atom feeds. GeoDCAT is an initiative with the potential to integrate DCAT metadata as they are used in the open data and e-government community with EN ISO 19115/57/19 standards and INSPIRE metadata as they are used in the Geospatial community. GeoDCAT has - because it is based on RDF- the ability to publish metadata directly on the web without open and geospatial data portals.\r\nTo respond to the interest of different communities to preserve geospatial metadata resources and to support the uptake of GeoDCAT-AP implementations, best practices from different countries were identified and studied. The best practice cases focus on four domains (focus areas): metadata input (manually or automatically harvested), metadata publication into an integrated geo/open data portal, publication of metadata as Linked Open Data (LOD), and information mapping (ISO 19115, INSPIRE, DCAT, etc.).\r\nGeoDCAT-AP is a mature solution for mapping metadata from the open data and geospatial domain. GeoDCAT helps to integrate and to publish metadata in data portals and directly on the world wide web. To conclude a GeoDCAT alignment exercise has been done with ISO 19115/19 and INSPIRE to improve the open data and geospatial metadata alignment in the future.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -17967,30 +17791,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-052" + "@value": "18-001r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC WCS 2.0.1 Corrigendum Release Notes" + "@value": "GeoDCAT-AP" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-084", + "@id": "http://www.opengis.net/def/docs/05-116", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-05-09" + "@value": "2007-03-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Vincent Delfosse" + "@value": "Stan Tillman, Jody Garnett" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -18005,17 +17829,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12597" + "@id": "https://portal.ogc.org/files/?artifact_id=12911" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-084" + "@value": "OWS Integrated Client (GeoDSS Client)" }, { "@language": "en", - "@value": "Catalog 2.0 Accessibility for OWS3" + "@value": "05-116" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -18025,7 +17849,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Catalog-Web Profile is a complex specification that implies usage of many concepts, such as ressources, metadata, registry, registry information model, harvesting, etc. This document is a user-friendly introduction to these concepts. It will help the understanding of the Catalog specification in general and of the Catalog Web profile with ebRIM in particular." + "@value": "This Interoperability Program Report (IPR) provides an overview of the general requirements, architecture, and design considerations of " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18036,35 +17860,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-084" + "@value": "05-116" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Catalog 2.0 Accessibility for OWS3" + "@value": "OWS Integrated Client (GeoDSS Client)" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-115", + "@id": "http://www.opengis.net/def/docs/01-019", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-01-21" + "@value": "2001-02-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "John Evans" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18074,37 +17898,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/61188" - }, - { - "@id": "https://portal.ogc.org/files/?artifact_id=61188" + "@id": "https://portal.ogc.org/files/?artifact_id=1020" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Smart Cities Spatial Information Framework" - }, - { - "@language": "en", - "@value": "Smart Cities Spatial Information Framework" + "@value": "XML for Image and map Annotation" }, { "@language": "en", - "@value": "14-115" + "@value": "01-019" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This White Paper supports development of a Smart Cities Spatial Information Framework\r\nbased on these themes:\r\n- Smart Cities are high-density generators of innovation and information.\r\n- Location information is a major enabler of Smart City technology benefits.\r\n- Benefits of smart technology must be judged by benefits to residents.\r\n- Reuse and repurpose is vital to urban resilience\r\n- Open standards are needed for interoperability, efficiency, application innovation\r\nand cost effectiveness.\r\nDiscussion of these themes and this white paper will occur at the OGC Smart Cities\r\nLocation Powers Summit in Tokyo on December 2, 2014,1 the co-located OGC Technical\r\nCommittee meeting, and in many other forums in the future. As described in this paper,\r\nthere are many standards initiatives that focus on Smart Cities. Most Smart Cities use\r\ncases in some way involve indoor and/or outdoor location, and thus communication about\r\nlocation is an issue that cuts across the work programs most of the standards\r\norganizations that are involved with Smart Cities.\r\nThis white paper builds on the OGC - Directions Magazine webinar: “Making Location\r\nWork for Smart Cities – the Case for Location Standards”2." - }, - { - "@value": "This White Paper supports development of a Smart Cities Spatial Information Framework\r\nbased on these themes:\r\nK Smart Cities are high-density generators of innovation and information.\r\nK Location information is a major enabler of Smart City technology benefits.\r\nK Benefits of smart technology must be judged by benefits to residents.\r\nK Reuse and repurpose is vital to urban resilience\r\nK Open standards are needed for interoperability, efficiency, application innovation\r\nand cost effectiveness.\r\nDiscussion of these themes and this white paper will occur at the OGC Smart Cities\r\nLocation Powers Summit in Tokyo on December 2, 2014,\r\n1 the co-located OGC Technical\r\nCommittee meeting, and in many other forums in the future. As described in this paper,\r\nthere are many standards initiatives that focus on Smart Cities. Most Smart Cities use\r\ncases in some way involve indoor and/or outdoor location, and thus communication about\r\nlocation is an issue that cuts across the work programs most of the standards\r\norganizations that are involved with Smart Cities.\r\nThis white paper builds on the OGC - Directions Magazine webinar: “Making Location\r\nWork for Smart Cities – the Case for Location Standards”2." + "@value": "Defines an XML vocabulary to encode annotations on imagery, maps, and other geospatial data. This vocabulary draws on the Geography Markup Language (OpenGIS" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18115,30 +17929,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-115" + "@value": "01-019" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Smart Cities Spatial Information Framework" + "@value": "XML for Image and map Annotation" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-037", + "@id": "http://www.opengis.net/def/docs/18-046", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-16" + "@value": "2018-12-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas Forbes, Ballal Joglekar" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -18153,17 +17967,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=58956" + "@id": "https://docs.ogc.org/per/18-046.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 10 Flight Information Exchange Model GML Schema" + "@value": "Earth Observation Exploitation Platform Hackathon 2018 Engineering Report" }, { "@language": "en", - "@value": "14-037" + "@value": "18-046" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -18173,7 +17987,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report provides guidance for implementing the Flight Information Exchange Model (FIXM) using the same best practice as the Aeronautical Information Exchange Model (AIXM) and the Weather Information Exchange Model (WXXM) by adopting ISO and OGC standards.\r\nThe report is aimed at system and client developers that shall use the FIXM data encoding for the exchange of flight information.\r\nThis document is a deliverable for the OGC Testbed 10 (Testbed-10) testbed activity. OWS testbeds are part of OGC's Interoperability Program, a global, hands-on and collaborative prototyping program designed to rapidly develop, test and deliver proven candidate standards or revisions to existing standards into OGC's Standards Program, where they are formalized for public release. In OGC's Interoperability Initiatives, international teams of technology providers work together to solve specific geoprocessing interoperability problems posed by the Initiative's sponsoring organizations. OGC Interoperability Initiatives include testbeds, pilot projects, interoperability experiments and interoperability support services - all designed to encourage rapid development, testing, validation and adoption of OGC standards.\r\nThe Testbed-10 sponsors are organizations seeking open standard for their interoperability requirements. After analyzing their requirements, the OGC Interoperability Team recommends to the sponsors that the content of the Testbed-10 initiative be organized around the following threads:\r\n•\tCross-Community Interoperability (CCI)\r\n•\tOpen Mobility\r\n•\tAviation\r\nMore information about the Testbed-10 tested can be found at:\r\nhttp://www.opengeospatial.org/standards/requests/103\r\n" + "@value": "The Earth Observation Exploitation Platform Hackathon 2018 was conducted to evaluate the standards based architecture for deploying and executing arbitrary applications close to the physical location of the data in heterogeneous cloud environments. The Hackathon was very successful in demonstrating both efficiency and sustainability of the architecture developed in Testbed-13. Efficient, because it was possible to setup the full execution workflow of 128 Sentinel-1 images within the 1.5 days of the Hackathon in a multi-vendor environment. Sustainable, because the architectural approach provides sufficient flexibility to cater for possible extensions and exchange of cloud & container middleware.\r\n\r\nThe Hackathon produced a number of suggestions for future work items. These include new tools to facilitate the process of Application Package generation to make it even simpler for scientists to bring their applications to the market; a more detailed specification to further improve the level of interoperability; and a best practice document with lots of examples that illustrate the necessary steps to make applications available.\r\n\r\nHackathon participants highlighted that such a level of robustness, flexibility, and maturity of the application-to-the-cloud architecture has been developed in nine months only during Testbed-13. The participants recommend to continue interlacing major OGC Innovation Program activities, such as testbeds, with short term rapid prototyping initiatives such as hackathons. Almost all participants of the Hackathon had been new to the OGC Innovation Program. These participants emphasized that the Hackathon provided an outstanding opportunity for newcomers to get quickly familiar with the latest standardization efforts and helped tremendously in understanding investments and new market opportunities for applications-in-the-cloud." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18184,35 +17998,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-037" + "@value": "18-046" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 10 Flight Information Exchange Model GML Schema" + "@value": "OGC Earth Observation Exploitation Platform Hackathon 2018 Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-018", + "@id": "http://www.opengis.net/def/docs/20-088", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-02-06" + "@value": "2021-02-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Martin Klopfer" + "@value": "K. Navulur, M.C. Abrams" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18222,27 +18036,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-018.html" + "@id": "https://docs.ogc.org/dp/20-088.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-018" + "@value": "Standardizing a Framework for Spatial and Spectral Error Propagation" }, { "@language": "en", - "@value": "OGC Testbed-15: Open Portrayal Framework Engineering Report" + "@value": "20-088" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) describes the OGC Testbed-15 Open Portrayal Framework (OPF) Thread requirements, scenario, high-level architecture, and solutions. Main topics addressed in the OPF Thread include style changing and sharing, converting style encodings, client- / server-side rendering of vector- and raster data and data provision in denied, disrupted, intermittent, and limited bandwidth (DDIL) infrastructure situations. The work in the OPF Thread was focused on an OGC Application Programming Interface (API) oriented approach." + "@value": "This OGC Discussion Paper presents a proposal that recommends the development of Open Geospatial Consortium (OGC) standards that define a framework for location-based service metrics that inform the spatial, spectral, and temporal errors associated with various data sources. This paper discusses current industry practices on spatial errors, spectral errors, and error propagation. The paper also presents a proposed framework and a recommended study effort." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18253,35 +18067,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-018" + "@value": "20-088" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Open Portrayal Framework Engineering Report" + "@value": "Standardizing a Framework for Spatial and Spectral Error Propagation" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-055r1", + "@id": "http://www.opengis.net/def/docs/18-056", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-12" + "@value": "2018-12-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Steve Liang, Tania Khalafbeigi, Kan Luo" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18291,27 +18105,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=16081" + "@id": "https://portal.ogc.org/files/?artifact_id=79179" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-055r1" + "@value": "18-056" }, { "@language": "en", - "@value": "GML 3.2 image geopositioning metadata application schema" + "@value": "SensorThings API Tasking Core Discussion Paper" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies a GML 3.2 Application Schema for image geopositioning metadata, which is also an Application Schema of ISO 19139. This geopositioning metadata schema is used by the separately specified Image Geopositioning Service (IGS) interface that adjusts the georeferencing coordinate transformations of images." + "@value": "This discussion paper offers descriptions and provides JSON examples of TaskingCapabilities and Tasks for the SensorThings Application Programming Interface (API)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18322,35 +18136,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-055r1" + "@value": "18-056" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS GML 3.2 image geopositioning metadata application schema" + "@value": "OGC SensorThings API Tasking Core Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-050r3", + "@id": "http://www.opengis.net/def/docs/01-068r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-19" + "@value": "2002-04-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Jeff de La Beaujardiere" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/can" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18360,27 +18174,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=15755" + "@id": "https://portal.ogc.org/files/?artifact_id=1081&format=pdf" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-050r3" + "@value": "01-068r3" }, { "@language": "en", - "@value": "GeoRSS, An Introduction to" + "@value": "Web Map Service" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/can" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "GeoRSS is simple proposal for geo-enabling, or tagging, really simple syndication (RSS) feeds with location information. GeoRSS proposes a standardized way in which location is encoded with enough simplicity and descriptive power to satisfy most needs to describe the location of Web content. GeoRSS may not work for every use, but it should serve as an easy-to-use geotagging encoding that is brief and simple with useful defaults but extensible and upwardly-compatible with more sophisticated encoding standards such as the OGC (Open Geospatial Consortium) GML (Geography Markup Language)." + "@value": "Provides three operations protocols (GetCapabilities, GetMap, and GetFeatureInfo) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18391,35 +18205,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-050r3" + "@value": "01-068r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GeoRSS, An Introduction to" + "@value": "Web Map Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-129r1", + "@id": "http://www.opengis.net/def/docs/22-035", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-02-07" + "@value": "2023-09-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Jérôme Jacovella-St-Louis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18429,27 +18243,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46568" + "@id": "https://docs.ogc.org/per/22-035.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-129r1" + "@value": "22-035" }, { "@language": "en", - "@value": "Geography Markup Language (GML) - Extended schemas and encoding rules" + "@value": "Testbed-18: 3D+ Data Streaming Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Geography Markup Language (GML) is an XML encoding in compliance with ISO 19118 for the transport and storage of geographic information modelled in accordance with the conceptual modelling framework used in the ISO 19100 series of International Standards and including both the spatial and non-spatial properties of geographic features." + "@value": "This OGC Testbed 18 3D Plus Data Standards and Streaming Engineering Report (ER) reviews existing specifications that support interoperable descriptions of orbital and non-orbital space-based assets, objects, and observations as well as terrestrial observations. The ER suggests a framework consolidating these specifications as a foundation for modeling, representation, and serialization from space-based assets operating at any location in our solar system (3D+ data). This framework enables the streaming of 3D+ data to visualization devices (displays, AR, VR) for presentation.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18460,35 +18274,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-129r1" + "@value": "22-035" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Geography Markup Language (GML) - Extended schemas and encoding rules" + "@value": "Testbed-18: 3D+ Data Streaming Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-006r2", + "@id": "http://www.opengis.net/def/docs/08-058r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-06-20" + "@value": "2008-09-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Tatjana Kutzner, Carl Stephen Smyth, Claus Nagel, Volker Coors, Diego Vinasco-Alvarez, Nobuhiro Ishi" + "@value": "Stefan Falke" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18498,27 +18312,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/21-006r2/21-006r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=30061" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "City Geography Markup Language (CityGML) Part 2: GML Encoding Standard" + "@value": "OWS-5 Earth Observation Web Processing Services (WPS) Engineering Report" }, { "@language": "en", - "@value": "21-006r2" + "@value": "08-058r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Standard documents the OGC GML Implementation Specification (IS) for the CityGML 3.0 Conceptual Model. The CityGML 3.0 conceptual model is a Platform Independent Model (PIM). It defines concepts in a manner which is independent of any implementing technology. As such, the CityGML Conceptual Model cannot be implemented directly. Rather, it serves as the base for Platform Specific Models (PSM). A PSM adds to the PIM the technology-specific details needed to fully define the CityGML model for use with a specific technology. The PSM can then be used to generate the schema and other artifacts needed to build CityGML 3.0 implementations.\r\n\r\nThis standard defines the PSMs and schemas for the CityGML 3.0 Implementation Specification (IS) for Geography Markup Language (GML) implemenations. The GML schemas are explained in an overview and design decisions that have been made are documented as well.\r\n\r\n" + "@value": "This document serves to describe the use of web processing services and the OGC Web Processing Service (WPS) in earth observation (EO) applications. It provides an overview of web processing services and a description of developments related to earth observation implementations of OGC WPS in the OGC OWS-5 testbed." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18529,35 +18343,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-006r2" + "@value": "08-058r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC City Geography Markup Language (CityGML) Part 2: GML Encoding Standard" + "@value": "OWS-5 Earth Observation Web Processing Services (WPS) Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-113", + "@id": "http://www.opengis.net/def/docs/09-007", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-19" + "@value": "2009-10-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Scott Fairgrieve" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18567,27 +18381,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=16572" + "@id": "https://portal.ogc.org/files/?artifact_id=33355" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GML 3.1.1 common CRSs profile Corrigendum" + "@value": "09-007" }, { "@language": "en", - "@value": "06-113" + "@value": "OWS-6 Common CBRN Sensor Interface (CCSI)-Sensor Web Enablement (SWE) Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a corrigendum for OGC Document 05-095r1, titled GML 3.1.1 common CRSs profile. This corrigendum is based on change request OGC 06-041." + "@value": "This document outlines the concepts, best practices, and lessons learned gathered from integrating Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) standard-compliant sensors into an OGC Sensor Web Enablement (SWE)-based architecture. The document also specifies a web service interface for interacting with CCSI sensors and defines the basis for a profile that can be used to represent CCSI sensor definitions, data, and commands in SWE formats. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18598,35 +18412,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-113" + "@value": "09-007" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML 3.1.1 common CRSs profile Corrigendum" + "@value": "OWS-6 Common CBRN Sensor Interface (CCSI)-Sensor Web Enablement (SWE) Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-085r4", + "@id": "http://www.opengis.net/def/docs/16-005r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-09-23" + "@value": "2018-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lucio Colaiacomo, Joan Masó, Emmanuel Devys" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18636,27 +18450,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/08-085r4/08-085r4.html" + "@id": "https://portal.ogc.org/files/16-005r3" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core " + "@value": "16-005r3" }, { "@language": "en", - "@value": "08-085r4" + "@value": "Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard applies to the encoding and decoding of JPEG 2000 images that contain GML for use with geographic imagery.\r\n\r\nThis document specifies the use of the Geography Markup Language (GML) within the XML boxes of the JPEG 2000 data format and provides an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations. The document also specifies the encoding and packaging rules for GML use in JPEG 2000." + "@value": "This document provides the Annexes for the CDB Core: Model and Physical Structure standard. The only exception is Annex A, Abstract Test Suite. The CDB ATS Annex is in Volume 1: Core document." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18667,35 +18481,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-085r4" + "@value": "16-005r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core " + "@value": "Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-092r3", + "@id": "http://www.opengis.net/def/docs/16-104r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-01-15" + "@value": "2017-08-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Paul Scarponcini" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18705,27 +18519,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=30575" + "@id": "https://portal.ogc.org/files/?artifact_id=75121" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Definition identifier URNs in OGC namespace" + "@value": "InfraGML 1.0: Part 4 - LandInfra Roads - Encoding Standard" }, { "@language": "en", - "@value": "07-092r3" + "@value": "16-104r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies Universal Resource Names (URNs) in the “ogc” URN namespace to be used for identifying definitions. These definitions include definitions of Coordinate Reference Systems (CRSs) and related objects, as specified in OGC Abstract Specification Topic 2: Spatial referencing by coordinates, plus several other resource types for which standard identifiers are useful in OGC Web Services. This document specifies the formats used by these URNs, including formats that can reference definitions recorded in the EPSG database and by other authorities. This document also specifies URNs for some specific definitions for which OGC is the custodian." + "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 4 addresses the Road and RoadCrossSection Requirements Class from LandInfra." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18736,35 +18550,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-092r3" + "@value": "16-104r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Definition identifier URNs in OGC namespace" + "@value": "OGC InfraGML 1.0: Part 4 - LandInfra Roads - Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-025r4", + "@id": "http://www.opengis.net/def/docs/12-018r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-01-12" + "@value": "2012-08-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Patrick Cozzi, Sean Lilley" + "@value": "Peter Fitch" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18774,27 +18588,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/22-025r4/22-025r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=50166" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "3D Tiles Specification" + "@value": "Surface Water Interoperability Experiment FINAL REPORT " }, { "@language": "en", - "@value": "22-025r4" + "@value": "12-018r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the specification for 3D Tiles, an open standard for streaming massive heterogeneous 3D geospatial datasets." + "@value": "This report describes the methods, results, issues and recommendations generated by the Surface Water Interoperability Experiment (SW IE), carried out as an activity of the OGC Hydrology Domain Working Group (HDWG). The SW IE was designed to advance the development of WaterML 2.0 and test its use with various OGC service standards (SOS, WFS, WMS and CSW). A secondary aim was to contribute to the development of a hydrology domain feature model and vocabularies, which are essential for interoperability in the hydrology domain, although these are not the main focus for the IE. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18805,35 +18619,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-025r4" + "@value": "12-018r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "3D Tiles Specification" + "@value": "OGC® Surface Water Interoperability Experiment FINAL REPORT " } ] }, { - "@id": "http://www.opengis.net/def/docs/03-088r6", + "@id": "http://www.opengis.net/def/docs/16-004r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-01-19" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18843,27 +18657,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=4550" + "@id": "https://docs.ogc.org/bp/16-004r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-088r6" + "@value": "16-004r5" }, { "@language": "en", - "@value": "OGC Web Services Common" + "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models (Best Practice)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses." + "@value": "This CDB volume provides all of the information required to store Radar Cross Section (RCS) data within a conformant CDB data store.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18874,35 +18688,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-088r6" + "@value": "16-004r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Services Common" + "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models (Best Practice)" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-118r8", + "@id": "http://www.opengis.net/def/docs/16-071r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-09-08" + "@value": "2020-03-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "P Denis" + "@value": "Simon Cox, Chris Little" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18912,27 +18726,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40677" + "@id": "https://www.w3.org/TR/2020/CR-owl-time-20200326/" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "User Management for Earth Observation Services" + "@value": "Time Ontology in OWL" }, { "@language": "en", - "@value": "07-118r8" + "@value": "16-071r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes how user and identity management information may be included in the protocol specifications for OGC Services. The use cases addressed will make reference to EO (Earth Observation) services, for example catalogue access (EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 [OGC 06-131]), ordering (Ordering Services for Earth Observation Products [OGC 06-141r2]) and programming (OpenGIS Sensor Planning Service Application Profile for EO Sensors [OGC 07-018r2]). " + "@value": "OWL-Time is an OWL-2 DL ontology of temporal concepts, for describing the temporal properties of resources in the world or described in Web pages. The ontology provides a vocabulary for expressing facts about topological (ordering) relations among instants and intervals, together with information about durations, and about temporal position including date-time information. Time positions and durations may be expressed using either the conventional (Gregorian) calendar and clock, or using another temporal reference system such as Unix-time, geologic time, or different calendars.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -18943,35 +18757,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-118r8" + "@value": "16-071r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "User Management for Earth Observation Services" + "@value": "Time Ontology in OWL" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-015", + "@id": "http://www.opengis.net/def/docs/05-089r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-09-11" + "@value": "2005-12-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Craig Bruce" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -18981,27 +18795,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=33516" + "@id": "https://portal.ogc.org/files/?artifact_id=12971" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-015" + "@value": "05-089r1" }, { "@language": "en", - "@value": "OWS-6 Styled Layer Descriptor (SLD) Changes ER" + "@value": "Sensor Planning Service" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the extension of the OGC Styled Layer Descriptor (SLD) symbology format for improved capability and harmonization with ISO 19117 symbology, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology." + "@value": "The Sensor Planning Service (SPS) is intended to provide a standard interface to collection assets (i.e., sensors, and other information gathering assets) and to the support systems that surround them. \r\nThe SPS is designed to be flexible enough to handle a wide variety of configurations." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19012,35 +18826,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-015" + "@value": "05-089r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 Styled Layer Descriptor (SLD) Changes ER" + "@value": "Sensor Planning Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-036r1", + "@id": "http://www.opengis.net/def/docs/09-127r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-07" + "@value": "2012-01-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Benjamin Pross, Arnaud Cauchy" + "@value": "Tom O’Reilly " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -19050,27 +18864,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-036r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=47604" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "WPS-T Engineering Report" + "@value": "09-127r2" }, { "@language": "en", - "@value": "18-036r1" + "@value": "OGC® PUCK Protocol Standard " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report describes a proposed transactional extension for the OGC Web Processing Service (WPS) 2.0 standard including Key-Value Pair (KVP) and Extensible Markup Language (XML) bindings and recommendations for a process deployment profile for BPMN (Business Process Model and Notation)." + "@value": "This standard defines a protocol for RS232 and Ethernet connected instruments. PUCK addresses installation and configuration challenges for sensors by defining a standard instrument protocol to store and automatically retrieve metadata and other information from the instrument device itself." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19081,35 +18895,46 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-036r1" + "@value": "09-127r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: WPS-T Engineering Report" + "@value": "OGC® PUCK Protocol Standard " } ] }, { - "@id": "http://www.opengis.net/def/docs/18-005r5", + "@id": "http://www.opengis.net/def/doc-type/d-isc", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/12-128r11" + }, + { + "@id": "http://www.opengis.net/def/docs/06-189" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/16-126r8", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-07-02" + "@value": "2017-08-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Lott" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -19119,27 +18944,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/as/18-005r5/18-005r5.html" + "@id": "https://portal.ogc.org/files/16-126r8" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-005r5" + "@value": "16-126r8" }, { "@language": "en", - "@value": "Topic 02 - Referencing by coordinates Corrigendum" + "@value": "Release Notes for GeoPackage v1.2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is identical in normative content with the latest edition (2019) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2019]." + "@value": "This document provides the set of revision notes for the existing GeoPackage version 1.2 (OGC 12-\r\n128r13) and does not modify that standard.\r\nThis document was approved by the OGC membership on approval date. As a result of the OGC\r\nStandards Working Group (SWG) process, there were a number of edits and enhancements made to\r\nthis standard. This document provides the details of those edits, deficiency corrections, and\r\nenhancements. It also documents those items that have been deprecated. Finally, this document\r\nprovides implementations details related to issues of backwards compatibility." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19150,30 +18975,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-005r5" + "@value": "16-126r8" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 2 - Referencing by coordinates Corrigendum" + "@value": "Release Notes for GeoPackage v1.2" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-030", + "@id": "http://www.opengis.net/def/docs/19-030r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-04-08" + "@value": "2019-08-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mahnoush Alsadat Mohammadi Jahromi, Alex Robin" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -19188,17 +19013,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-030.html" + "@id": "https://docs.ogc.org/per/19-030r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: SIF Semantic Model Engineering Report" + "@value": "19-030r1" }, { "@language": "en", - "@value": "21-030" + "@value": "Mixed Reality to the Edge Concept Development Study" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -19208,7 +19033,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) presents an analysis of the semantic model of the Sensor Integration Framework (SIF). After reviewing the current SIF Semantic Model, existing related ontologies are reviewed. The ER discusses the results and includes all lessons learned from the experiments completed by the Sensor Integration thread of the OGC Testbed-17 initiative. The ER presents a series of recommendations based on the lessons learned." + "@value": "Mixed Reality (MR), also referred to as hybrid reality, is the merging of real and virtual worlds to produce new environments and visualizations where physical and digital objects co-exist and interact in real time. MR has great potential in enhancing situation awareness and otherwise augmenting the experiences and performance of humans on the go.\r\n\r\nThis OGC Engineering Report summarizes information and findings collected during the Mixed Reality at the Edge Concept Development Study (CDS). Specifically, this report presents the significant findings concerning the state-of-the-art and potential of employing MR in modern systems, with a focus on discussing the state of needed interoperability and standards.\r\n\r\nThe term mixed reality was originally introduced in a 1994 paper by Paul Milgram and Fumio Kishino, A Taxonomy of Mixed Reality Visual Displays. What is mixed reality?." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19219,30 +19044,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-030" + "@value": "19-030r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: SIF Semantic Model Engineering Report" + "@value": "OGC Mixed Reality to the Edge Concept Development Study" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-085r2", + "@id": "http://www.opengis.net/def/docs/05-118", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-10-13" + "@value": "2006-04-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Clemens Portele, Rafael Renkert" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -19257,17 +19082,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=35653" + "@id": "https://portal.ogc.org/files/?artifact_id=12894" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-085r2" + "@value": "OGC Web Services (OWS) 3 UGAS Tool" }, { "@language": "en", - "@value": "Grid coverage Coordinate Reference Systems (CRSs)" + "@value": "05-118" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -19277,7 +19102,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document summarizes the types of Coordinate Reference Systems (CRSs) that are recommended for use with grid (including image) coverages. This document specializes Best Practice Paper OGC 09-076r3 “Uses and Summary of Topic 2: Spatial referencing by coordinates” for grid coverages. Topic 2 is almost the same as ISO 19111:2007, but includes some corrections. This document includes some best practices for defining and using ImageCRSs and other CRSs for grid coverages." + "@value": "This document contains a description of the UGAS (UML Application Schema to GML ApplicationSchema conversion) tool development in the decision support services thread (GeoDSS) during the OWS-3 initiative." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19288,30 +19113,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-085r2" + "@value": "05-118" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Grid coverage Coordinate Reference Systems (CRSs)" + "@value": "OGC Web Services (OWS) 3 UGAS Tool" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-028r1", + "@id": "http://www.opengis.net/def/docs/19-026", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-19" + "@value": "2019-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas Disney" + "@value": "Pedro Gonçalves" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -19326,17 +19151,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-028r1.html" + "@id": "https://docs.ogc.org/per/19-026.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-028r1" + "@value": "OGC Testbed-15: Federated Clouds Analytics Engineering Report" }, { "@language": "en", - "@value": "Testbed-12 FIXM GML Engineering Report" + "@value": "19-026" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -19346,7 +19171,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The FAA and EUROCONTROL, in conjunction with multiple other international partners, are currently in the process of developing the Flight Information Exchange Model (FIXM). FIXM is an exchange model capturing Flight and Flow information that is globally standardized. The need for FIXM was identified by the International Civil Aviation Organization (ICAO) Air Traffic Management Requirements and Performance Panel (ATMRPP) in order to support the exchange of flight information as prescribed in Flight and Flow Information for a Collaborative Environment (FF-ICE).\r\n\r\nFIXM is the equivalent, for the Flight domain, of Aeronautical Information Exchange Model (AIXM) and Weather Information Exchange Model (WXXM), both of which were developed in order to achieve global interoperability for, respectively, Aeronautical Information Systems (AIS) and Meteorological Information (MET) exchange. FIXM is therefore part of a family of technology independent, harmonized and interoperable information exchange models designed to cover the information needs of Air Traffic Management. Previous OGC IP initiatives developed an architecture that supports the exchange of AIXM and WXXM data. This report shall describe the integration of Geography Markup Language (GML) profile elements into FIXM, specifically, the Feature, Time, Geometries and Units of Measure (UOM), into FIXM version 3.0.1 and drafts of FIXM 4.0. The purpose of this report is to provide recommendations and change requests (CR) on the implementation of GML elements for use by the FIXM development community." + "@value": "This OGC Engineering Report (ER) documents the results and experiences resulting from the Federated Cloud Analytics task of OGC Testbed-15. More specifically, this ER provides an analysis of:\r\n\r\nThe potential for the OGC Web Processing Service (WPS) Interface Standard as an Application Programming Interface (API) to a workflow automation service for managing job execution involving multiple containers in the Scale Data Center Environment;\r\n\r\nUsing an implementation of the OGC WPS standard as a general frontend to workflow automation with containers;\r\n\r\nThe suitability of the OGC WPS 2.0 standard as an API for Cloud analytics;\r\n\r\nUsing OGC Web Services (WS) as analytics data sources and sinks." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19357,35 +19182,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-028r1" + "@value": "19-026" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 FIXM GML Engineering Report" + "@value": "OGC Testbed-15: Federated Clouds Analytics Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-036", + "@id": "http://www.opengis.net/def/docs/10-028r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-10-05" + "@value": "2010-06-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Andrea Biancalana, Pier Giorgio Marchetti, Paul Smits" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -19395,27 +19220,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20509" + "@id": "https://portal.ogc.org/files/?artifact_id=39475" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geography Markup Language (GML) Encoding Standard" + "@value": "GIGAS Methodology for comparative analysis of information and data management systems" }, { "@language": "en", - "@value": "07-036" + "@value": "10-028r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Geography Markup Language Encoding Standard (GML) The Geography Markup Language (GML) is an XML grammar for expressing geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. As with most XML based grammars, there are two parts to the grammar – the schema that describes the document and the instance document that contains the actual data.\r\nA GML document is described using a GML Schema. This allows users and developers to describe generic geographic data sets that contain points, lines and polygons. However, the developers of GML envision communities working to define community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas] that are specialized extensions of GML. Using application schemas, users can refer to roads, highways, and bridges instead of points, lines and polygons. If everyone in a community agrees to use the same schemas they can exchange data easily and be sure that a road is still a road when they view it.\r\n\r\nClients and servers with interfaces that implement the OpenGIS® Web Feature Service Interface Standard[http://www.opengeospatial.org/standards/wfs] read and write GML data. GML is also an ISO standard (ISO 19136:2007) [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32554 ]. \r\nSee also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .\r\n" + "@value": "This document has been written on the basis of a methodology developed within the GIGAS Support Action financed by the European Commission in order to address the convergence of global initiatives like GEOSS and the European interoperability initiatives developed in the context of the GMES programme like HMA - Heterogeneous Missions Accessibility and the INSPIRE spatial data infrastructure legislation." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19426,35 +19251,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-036" + "@value": "10-028r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Geography Markup Language (GML) Encoding Standard" + "@value": "GIGAS Methodology for comparative analysis of information and data management systems" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-069r2", + "@id": "http://www.opengis.net/def/docs/09-041r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-03-25" + "@value": "2009-07-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Bastian Baranski" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/ts" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -19464,27 +19289,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=32314" + "@id": "https://portal.ogc.org/files/?artifact_id=34977" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-069r2" + "@value": "09-041r3" }, { "@language": "en", - "@value": "Web Coverage Processing Service (WCPS) Abstract Test Suite" + "@value": "OWS-6 WPS Grid Processing Profile Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/ts" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "" + "@value": "This OGC Engineering Report describes and reviews the Grid Computing related activity completed during the OGC OWS-6 Interoperability testbed. The document describes the WPS processes deployed in the different demonstration scenarios and offers recommendations to the OGC community as to how to better harmonize the standards work of the OGC with Grid Computing platforms and related concepts and technologies." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19495,35 +19320,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-069r2" + "@value": "09-041r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Coverage Processing Service (WCPS) Abstract Test Suite" + "@value": "OWS-6 WPS Grid Processing Profile Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-110r2", + "@id": "http://www.opengis.net/def/docs/16-012r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-11-02" + "@value": "2016-12-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Dimitri Sarafinof" + "@value": "Ki-Joune Li, Hyung-Gyu Ryu, Hak-Cheol Kim, Jun Hee Lee, Joo-Ho Lee" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -19533,27 +19358,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/14-110r2/14-110r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=68824" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GML Application Schema - Coverages JPEG2000/JPIP Coverage Encoding Extension" + "@value": "16-012r1" }, { "@language": "en", - "@value": "14-110r2" + "@value": "Comparing CityGML and IndoorGML based on a use case at Lotte World Mall" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Coverages represent space/time-varying phenomena, such as satellite imagery, digital elevation models, or digital aerial imagery. OGC Abstract Topic 6 [OGC 07-011] – which is identical to ISO 19123 – defines an abstract model of coverages. Coverage instances may be encoded using the GML Application Schema – Coverages – JPEG2000 Coverage Encoding Extension version 1.0 [OGC 12-108] which is based on the GML Application Schema – Coverages (GMLCOV) version 1.0 [OGC 09-146r2] which in turn is based on the Geography Markup Language (GML) version 3.2 [07-036], an XML grammar written in XML Schema for the description of application schemas as well as the transport and storage of geographic information.\r\n\r\nThis extension to the Web Coverage Service (WCS) 2.0 Interface Standard – Core (WCS) version 2.0 [OC 09-110r4] specifies the usage of the JPEG2000 coverage encoding and JPIP streaming capabilities with WCS. The approach is based on the authoritative GML Application Schema – Coverages – JPEG2000 Coverage Encoding Extension version 1.0 [OGC 12-108]." + "@value": "This OGC Discussion Paper provides a comparison between the OGC CityGML and IndoorGML standards. The goals and approaches of these two standards are different and they can be used in a complementary way. This discussion paper aims to compare the strengths and weakness of the standards, and explain how to integrate the standards to make useful applications. These comparative experiments are based on a real site: a shopping mall at Lotte World Mall in Seoul, South Korea." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19564,104 +19389,81 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-110r2" + "@value": "16-012r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GML Application Schema - Coverages JPEG2000/JPIP Coverage Encoding Extension" + "@value": "Comparing CityGML and IndoorGML based on a use case at Lotte World Mall" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-070r4", + "@id": "http://www.opengis.net/def/doc-type/pol-nts/collection", "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" + "http://www.w3.org/2004/02/skos/core#Collection" ], - "http://purl.org/dc/terms/created": [ + "http://www.w3.org/2000/01/rdf-schema#label": [ { - "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "Documents of type Name Type Specification" } ], - "http://purl.org/dc/terms/creator": [ + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Carl Reed" + "@value": "Documents of type Name Type Specification" } ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/docs" } ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "http://www.w3.org/2004/02/skos/core#member": [ { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/09-048r5" + }, { - "@id": "https://docs.ogc.org/bp/16-070r4.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/09-047r3" + }, { - "@language": "en", - "@value": "16-070r4" + "@id": "http://www.opengis.net/def/docs/18-042r4" }, { - "@language": "en", - "@value": "Volume 4: OGC CDB Rules for Encoding CDB Vector Data using Shapefiles (Best Practice)" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/12-081" + }, { - "@id": "http://www.opengis.net/def/doc-type/bp" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/10-103r1" + }, { - "@value": "This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ - { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-070r4" + "@id": "http://www.opengis.net/def/docs/20-059r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@language": "en", - "@value": "Volume 4: OGC CDB Rules for Encoding CDB Vector Data using Shapefiles (Best Practice)" + "@value": "Documents of type Name Type Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-120r6", + "@id": "http://www.opengis.net/def/docs/08-122r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2009-04-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Matthew Williams, Dan Cornford, Lucy Bastin & Edzer Pebesma" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -19671,27 +19473,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/15-120r6.html" + "@id": "https://portal.ogc.org/files/?artifact_id=33234" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Volume 0: OGC CDB Companion Primer for the CDB standard (Best Practice)" + "@value": "08-122r2" }, { "@language": "en", - "@value": "15-120r6" + "@value": "Uncertainty Markup Language (UnCertML)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The CDB standard defines a standardized model and structure for a single, “versionable,” virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time." + "@value": "The Uncertainty Markup Language (UncertML) is an XML encoding for the transport and storage of information about uncertain quantities, with emphasis on quantitative representations based on probability theory. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19702,30 +19504,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-120r6" + "@value": "08-122r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 0: OGC CDB Companion Primer for the CDB standard (Best Practice)" + "@value": "Uncertainty Markup Language (UnCertML)" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-097", + "@id": "http://www.opengis.net/def/docs/14-114r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-10-03" + "@value": "2014-12-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mohsen Kalantari" + "@value": "Peter Taylor " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -19740,17 +19542,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-097.html" + "@id": "https://portal.ogc.org/files/?artifact_id=61224" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-097" + "@value": "WaterML2.0 part 2 – rating tables, gauging observations and cross-sections: Interoperability Experiment Results" }, { "@language": "en", - "@value": "Future City Pilot 1: Using IFC/CityGML in Urban Planning Engineering Report" + "@value": "14-114r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -19760,7 +19562,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Numerous and diverse technologies push cities towards open and platform-independent information infrastructures to manage human, natural, and physical systems. The Future Cities Pilot 1 (FCP1), as an OGC Innovation Program initiative, demonstrated how cities can benefit from open standards when used in urban planning workflows. This report details the lessons learned of implementing both the OGC CityGML and the buildingSMART Industry Foundation Classes (IFC) standards for visualizing and processing 3D spatial data when used in urban planning processes." + "@value": "Part 1 of WaterML2.0 covers exchange of hydrological time-series data, the observational processes used to generate them, and information related to the monitoring points (stations/sites) where time-series data are typically collected. WaterML2.0 Part 2, is a candidate standard that defines how to exchange rating tables, gauging observations and cross-sections in an interoperable manner. \r\nThis engineering report outlines the design and results of an OGC Interoperability Experiment (IE) that implemented and tested the current WaterML2.0 part 2 information model. The OGC IE experiment ran was conducted from November 2013 to August 2014. The use case for the IE involved exchange of data in three scenarios in Australia, US and the UK. \r\nThis report describes the software requirements, design, deployments and challenges faced by the experiment. The results were used to improve the WaterML2.0 part 2 information model and provided the basis for the formation of an OGC Standards Working Group (SWG) in August 2014. This SWG is responsible for formalization of the candidate OGC standard, for submission in 2015. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19771,35 +19573,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-097" + "@value": "14-114r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Future City Pilot 1: Using IFC/CityGML in Urban Planning Engineering Report" + "@value": "WaterML2.0 part 2 – rating tables, gauging observations and cross-sections: Interoperability Experiment Results" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-034r1", + "@id": "http://www.opengis.net/def/docs/12-096", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-03-13" + "@value": "2013-02-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed, Tamrat Belayneh" + "@value": "Mike Botts" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -19809,27 +19611,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/17-014r7/19-034r1.pdf" + "@id": "https://portal.ogc.org/files/?artifact_id=52162" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-034r1" + "@value": "12-096" }, { "@language": "en", - "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification Version 1.1 Release Notes " + "@value": "OWS-9: Engineering Report: Use of SWE Common and SensorML for GPS Messaging " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the set of revision notes for OGC I3S Community Standard [OGC 17-014r5] and does not modify that standard.\r\nThis document provides the details of edits, deficiency corrections, and enhancements of the above-referenced standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility.\r\n" + "@value": "This document is an Engineering Report for the OWS-9 Interoperability Test Bed. The focus of the document is discussion and demonstration on the use of SWE Common Data 2.0 encodings to support an interoperable messaging description and encoding for the next generation GPS message streams into and out of the GPS navigation accuracy improvement services. The connection of SWE Common to SensorML 2.0 and the application of SensorML to describe the processing surrounding GPS navigation improvement will also be discussed." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19840,102 +19642,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-034r1" + "@value": "12-096" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification Version 1.1 Release Notes " - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-rp/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type Recommendation Paper - deprecated " - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Documents of type Recommendation Paper - deprecated " - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/02-066r1" - }, - { - "@id": "http://www.opengis.net/def/docs/02-024" - }, - { - "@id": "http://www.opengis.net/def/docs/03-010r9" - }, - { - "@id": "http://www.opengis.net/def/docs/04-016r3" - }, - { - "@id": "http://www.opengis.net/def/docs/03-022r3" - }, - { - "@id": "http://www.opengis.net/def/docs/03-064r5" - }, - { - "@id": "http://www.opengis.net/def/docs/03-088r6" - }, - { - "@id": "http://www.opengis.net/def/docs/01-029" - }, - { - "@id": "http://www.opengis.net/def/docs/00-029" - }, - { - "@id": "http://www.opengis.net/def/docs/03-109r1" - }, - { - "@id": "http://www.opengis.net/def/docs/01-014r5" - }, - { - "@id": "http://www.opengis.net/def/docs/03-010r7" - }, - { - "@id": "http://www.opengis.net/def/docs/04-019r2" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Documents of type Recommendation Paper - deprecated " + "@value": "OWS-9: Engineering Report: Use of SWE Common and SensorML for GPS Messaging " } ] }, { - "@id": "http://www.opengis.net/def/docs/05-117", + "@id": "http://www.opengis.net/def/docs/04-087", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-05-02" + "@value": "2004-02-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Matt Murray,Jeff Stollman,Shue-Jane Thompson,Terry Plymell,Eli Hertz,Chuck Heazel" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -19945,27 +19680,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12893" + "@id": "https://portal.ogc.org/files/?artifact_id=7562" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-117" + "@value": "EA-SIG Enterprise Service Management White Paper" }, { "@language": "en", - "@value": "Schema Maintenance and Tailoring" + "@value": "04-087" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Description of the schema tailoring process for the application schema development in the decision support services thread (GeoDSS) during the OWS-3 initiative" + "@value": "*RETIRED* This document focuses on the goals, objectives, capabilities and recommendation for the ESM Core Enterprise Service. The charter for this team was to address three fundamental questions:\r\n\r\n* What it Enterprise Service Management?\r\n* What can we buy or build today?\r\n* How should we invest for the future?\r\n\r\nThis paper responds to those questions by defining and describing ESM, discussing what is being done today, and what the group sees for the future of ESM?" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -19976,35 +19711,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-117" + "@value": "04-087" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Schema Maintenance and Tailoring" + "@value": "EA-SIG Enterprise Service Management White Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-024r2", + "@id": "http://www.opengis.net/def/docs/13-133r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-06-16" + "@value": "2016-08-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sergio Taleisnik" + "@value": "Aaron Braeckel, Lorenzo Bigagli" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -20014,27 +19749,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-024r2.html" + "@id": "https://docs.ogc.org/is/13-133r1/13-133r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-024r2" + "@value": "Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension" }, { "@language": "en", - "@value": "Testbed-18: Filtering Service and Rule Set Engineering Report" + "@value": "13-133r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Testbed-18 (TB-18) Filtering Service and Rule Set Engineering Report (ER) documents best practices identified for features filtering and describes in detail how filtering can be decoupled from data services. Further, this ER describes how filtering rules can be provided to Filtering Services at runtime." + "@value": "Publish/Subscribe 1.0 is an interface specification that supports the core components and concepts of the Publish/Subscribe message exchange pattern with OGC Web Services. The Publish/Subscribe pattern complements the Request/Reply pattern historically specified by many OGC Web Services. This specification may be used either in concert with, or independently of, existing OGC Web Services to publish data of interest to subscribers.\r\n\r\nPublish/Subscribe 1.0 primarily addresses subscription management capabilities such as creating a subscription, renewing a subscription, and unsubscribing. However, this standard also allows Publish/Subscribe services to advertise and describe the supported message delivery protocols such as SOAP messaging, ATOM, and AMQP. Message delivery protocols should be considered to be independent of the Publish/Subscribe 1.0 standard. Therefore OGC Publish/Subscribe only includes metadata relating to message delivery protocols in sufficient detail to allow for different implementations of Publish/Subscribe 1.0 to interoperate. \r\n\r\nThis specification defines an extension to the OGC Publish/Subscribe (PubSub) 1.0 Core to allow for Publish/Subscribe communications usingthe SOAP protocol." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20045,35 +19780,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-024r2" + "@value": "13-133r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-18: Filtering Service and Rule Set Engineering Report" + "@value": "OGC® Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-005r1", + "@id": "http://www.opengis.net/def/docs/21-006r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-02-01" + "@value": "2023-06-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey" + "@value": "Tatjana Kutzner, Carl Stephen Smyth, Claus Nagel, Volker Coors, Diego Vinasco-Alvarez, Nobuhiro Ishi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -20083,27 +19818,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=66933" + "@id": "https://docs.ogc.org/is/21-006r2/21-006r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "DGIWG - Web Feature Service 2.0 Profile" + "@value": "City Geography Markup Language (CityGML) Part 2: GML Encoding Standard" }, { "@language": "en", - "@value": "15-005r1" + "@value": "21-006r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines the DGIWG profile for the ISO\r\n19142:2010 - Web Feature Service (WFS) including changes\r\nmade in the OpenGIS Web Feature Service 2.0 Interface\r\nStandard - Corrigendum. The Web Feature Service provides\r\naccess to geospatial features in a manner independent of the\r\nunderlying data store." + "@value": "This Standard documents the OGC GML Implementation Specification (IS) for the CityGML 3.0 Conceptual Model. The CityGML 3.0 conceptual model is a Platform Independent Model (PIM). It defines concepts in a manner which is independent of any implementing technology. As such, the CityGML Conceptual Model cannot be implemented directly. Rather, it serves as the base for Platform Specific Models (PSM). A PSM adds to the PIM the technology-specific details needed to fully define the CityGML model for use with a specific technology. The PSM can then be used to generate the schema and other artifacts needed to build CityGML 3.0 implementations.\r\n\r\nThis standard defines the PSMs and schemas for the CityGML 3.0 Implementation Specification (IS) for Geography Markup Language (GML) implemenations. The GML schemas are explained in an overview and design decisions that have been made are documented as well.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20114,35 +19849,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-005r1" + "@value": "21-006r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "DGIWG - Web Feature Service 2.0 Profile" + "@value": "OGC City Geography Markup Language (CityGML) Part 2: GML Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-053r1", + "@id": "http://www.opengis.net/def/docs/11-111r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-05-22" + "@value": "2016-09-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed, George Percivall" + "@value": "ISO" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-atb" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -20152,27 +19887,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=3835" + "@id": "http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?csnumber=53798" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-053r1" + "@value": "Topic 11 - Metadata" }, { "@language": "en", - "@value": "OGC Technical Document Baseline" + "@value": "11-111r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-atb" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Spreadsheet of OGC Technical Document Baseline" + "@value": "Same as ISO 19115-1:2014. Abstract Specification Topic 11 was updated to the latest version of the ISO metadata standard on 21 September 2016. Prior to this date, this Topic was the same as ISO 19115:2003. Please note that many OGC standards and other related work normatively refer to the previous version of this Topic." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20183,30 +19918,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-053r1" + "@value": "11-111r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Technical Document Baseline" + "@value": "Topic 11 - Metadata" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-075r1", + "@id": "http://www.opengis.net/def/docs/11-095r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-08-05" + "@value": "2011-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arne Schilling" + "@value": "Stephan Meissl, Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -20221,17 +19956,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=33949" + "@id": "https://portal.ogc.org/files/?artifact_id=47826" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-075r1" + "@value": "11-095r1" }, { "@language": "en", - "@value": "OWS-6 3D Flythrough (W3DS) Engineering Report" + "@value": "OWS-8 WCS 2.0 Earth Observation Application Profile Compliance Tests Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -20241,7 +19976,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the 3D portrayal server components which were used in the OGC OWS-6 Decision Support Systems (DSS) thread. The objective pf this activity was to efficiently stream and display GML 3 content in internet or wireless networks with limited bandwidth, especially focusing on the CityGML application profile. The server for delivering landscape and city models is implemented as Web 3D Service (W3DS) that is designed as portrayal service. " + "@value": "This Engineering Report describes and evaluates the specification of EO-WCS ATS and the implementation of ETS for use within an OGC SOA processing chain." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20252,35 +19987,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-075r1" + "@value": "11-095r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 3D Flythrough (W3DS) Engineering Report" + "@value": "OWS-8 WCS 2.0 Earth Observation Application Profile Compliance Tests Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-028", + "@id": "http://www.opengis.net/def/docs/18-024r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-04-16" + "@value": "2018-12-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Michael Leedahl" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -20290,27 +20025,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-028.html" + "@id": "https://portal.ogc.org/files/18-024r1" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-028" + "@value": "18-024r1" }, { "@language": "en", - "@value": "OGC Testbed 19 Extraterrestrial GeoTIFF Engineering Report" + "@value": "Release Notes for OGC GeoPackage Encoding Standard v1.2.1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "With the growing number of space assets and missions, the space industry needs a way to locate extra-terrestrial objects within the captured imagery. The current GeoTIFF Standard provides the location of terrestrial objects using TIFF tags. However, objects in space are relative to the observer and the distance of the objects in the imagery are often at great distances from the observer. Multiple objects can exist within the imagery which are at different spacetime locations in four dimensions. To further complicate the definition of the location, from a planar perspective, the edges of the image fade into infinity. With the use of spherical and gridded coordinates an image can tag pixels along the edge of a sphere or the camera location. The Testbed 19 Engineering Report (ER) extends GeoTIFF to work for all images including both terrestrial and non-terrestrial observations within the image." + "@value": "This document provides the set of revision notes for the existing GeoPackage version 1.2.1 (OGC 12-128r15) and does not modify that standard.\r\n\r\nThis document was approved by the OGC membership on approval date. As a result of the OGC Standards Working Group (SWG) process, there were a number of edits and enhancements made to this standard. This document provides the details of those edits, deficiency corrections, and enhancements. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20321,35 +20056,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-028" + "@value": "18-024r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed 19 Extraterrestrial GeoTIFF Engineering Report" + "@value": "Release Notes for OGC GeoPackage Encoding Standard v1.2.1" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-124r2", + "@id": "http://www.opengis.net/def/docs/16-027", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-09-12" + "@value": "2017-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Chris Holmes" + "@value": "Johannes Echterhoff, Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -20359,27 +20094,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=28086" + "@id": "https://docs.ogc.org/per/16-027.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-5 KML Engineering Report" + "@value": "16-027" }, { "@language": "en", - "@value": "07-124r2" + "@value": "Testbed-12 Web Service Implementation Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion Paper is about the use of KML, an encoding used to express geographic annotation and visualization on existing or future web-based online maps (2d) and earth browsers (3d). KML uses a tag-based structure with nested elements and attributes and is based on the XML standard." + "@value": "This document is a deliverable of the OGC Testbed-12. It describes the results of analyzing the Testbed-12 web service implementations.\r\n\r\nOGC has been developing web service specifications since the OGC Web Mapping Testbed in 1999. In particular, the original OGC Web Map Service specification has been developed during that testbed. 17 years later most current OGC web service standards still follow the general approach that had been developed in 1999 (the capabilities document, the remote procedure call via HTTP paradigm, etc).\r\n\r\nOver time, the OGC web service approach has been amended and extended in different ways by different OGC standards and profiles. In addition, some of the more flexible mechanisms have been used in practice in different ways by different software vendors or communities. The OGC Web Service Common standard had been a response by OGC to these developments and aimed at maintaining a consistent approach across the different OGC web service standards. However, this effort has been only partially successful for several reasons, including shortcomings in the OWS Common standard, the existence of multiple incompatible OWS Common versions and a reluctance by working groups and communities to introduce incompatible changes to existing service types in order to harmonize. All attempts in recent years to continue the work on OWS Common have not seen much traction. While there seems to be general agreement that the current situation is not optimal and that consistency is desirable, it is unclear how to improve in a way that meets market demands.\r\n\r\nThis document summarizes information about the web service implementations in Testbed-12. It is not and should not be understood as a general analysis or assessment of the OGC web service architecture, but a low-key effort to gain some insights from looking at a significant number of web service implementations and their use in interoperability experiments and demos.\r\n\r\nDuring the years since 1999 not only the OGC standards baseline has evolved, but also the Web itself. The W3C has been working on identifying Best Practices for Data on the Web and W3C and OGC are jointly working on extending this with Best Practices for Spatial Data on the Web. The analysis also includes an assessment about the OGC approach to web services with respect to the draft best practices at the time of writing of this report.\r\n\r\nTo the extent possible, we draw conclusions and recommendations from the information that has been gathered. These fall into three categories:\r\n\r\nImproving the interoperability of OGC web services as they are today\r\n\r\nSupport for new requirements in a consistent way across service types\r\n\r\nImprovements to the standardization process\r\n\r\nIn addition, there is also a specific case that does not fit into these general categories." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20390,35 +20125,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-124r2" + "@value": "16-027" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-5 KML Engineering Report" + "@value": "Testbed-12 Web Service Implementation Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-020r29", + "@id": "http://www.opengis.net/def/docs/16-129", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-05-11" + "@value": "2017-03-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Scott Simmons" + "@value": "Ingo Simonis, Rob Atkinson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pol" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -20428,27 +20163,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/pol/05-020r29/05-020r29.html" + "@id": "https://portal.ogc.org/files/?artifact_id=70328" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Technical Committee Policies and Procedures" + "@value": "Standardized Information Models to Optimize Exchange, Reusability and Comparability of Citizen Science Data (SWE4CS)" }, { "@language": "en", - "@value": "05-020r29" + "@value": "16-129" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pol" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC provides a collaborative, consensus process for developing and approving open, international Standards and supporting content for the geospatial domain, collectively known as OGC Products. To guide the OGC Product development and approval process, a member-approved Policies and Procedures document for the Technical Committee (TC) is required.\r\n\r\nThis document describes the TC Policies and Procedures (TC PnP). The TC has been granted authority to operate by the OGC Bylaws. The TC is composed of individuals representing organizations that are duly recognized members in good standing of the OGC.\r\n\r\nAs the needs and purpose of the TC change, changes to these policies and procedures are approved by an electronic vote of the Voting Members of the OGC TC. These policies and procedures may be augmented or clarified by Policy Directives issued and approved by the TC or the Executive Planning Committee (EPC). Such directives are databased and hyperlinked to/from the appropriate portion of this document." + "@value": "This discussion paper describes a data model for the standardized exchange of citizen science sampling data. To do that it applies the Sensor Web Enablement (SWE) to Citizen Science (SWE4CS). In particular, exposes how Observations and Measurements (O&M) can be used to model the data of the Citizen Science project, in a way that can be retrieved using Sensor Observing System (SOS).This discussion paper is a result of the research project Citizen Observatory Web (COBWEB). COBWEB is supported by the European Commission through grant agreement 308513" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20459,35 +20194,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-020r29" + "@value": "16-129" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Technical Committee Policies and Procedures" + "@value": "Standardized Information Models to Optimize Exchange, Reusability and Comparability of Citizen Science Data (SWE4CS)" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-147r1", + "@id": "http://www.opengis.net/def/docs/04-050r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-10-27" + "@value": "2005-04-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Philippe Duschene, Jerome Sonnet" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -20497,27 +20232,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41439" + "@id": "https://portal.ogc.org/files/?artifact_id=9541" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension" + "@value": "04-050r1" }, { "@language": "en", - "@value": "09-147r1" + "@value": "WMS Change Request: Support for WSDL & SOAP" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies how Web Coverage Service (WCS) clients and servers can communicate over the Internet using HTTP GET with key/value pair (KVP) encoding." + "@value": "This change proposal is an outcome of the Common Architecture thread of the OpenGIS Web Service 2 initiative. The aim is to add support for a standard WSDL description of the WMS interface in version 1.3.1." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20528,35 +20263,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-147r1" + "@value": "04-050r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension" + "@value": "WMS Change Request: Support for WSDL & SOAP" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-007r7", + "@id": "http://www.opengis.net/def/docs/15-107", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-10-05" + "@value": "2017-09-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Schut" + "@value": "Jeremy Tandy, Linda van den Brink, Payam Barnaghi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -20566,27 +20301,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=24151" + "@id": "https://www.w3.org/TR/sdw-bp/" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Processing Service" + "@value": "15-107" }, { "@language": "en", - "@value": "05-007r7" + "@value": "Spatial Data on the Web Best Practices" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Web Processing Service (WPS) Interface Standard provides rules for standardizing how inputs and outputs (requests and responses) for geospatial processing services, such as polygon overlay. The standard also defines how a client can request the execution of a process, and how the output from the process is handled. It defines an interface that facilitates the publishing of geospatial processes and clients’ discovery of and binding to those processes. The data required by the WPS can be delivered across a network or they can be available at the server. " + "@value": "This document advises on best practices related to the publication of spatial data on the Web; the use of Web technologies as they may be applied to location. The best practices presented here are intended for practitioners, including Web developers and geospatial experts, and are compiled based on evidence of real-world application. These best practices suggest a significant change of emphasis from traditional Spatial Data Infrastructures by adopting an approach based on general Web standards. As location is often the common factor across multiple datasets, spatial data is an especially useful addition to the Web of data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20597,30 +20332,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-007r7" + "@value": "15-107" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Processing Service" + "@value": "Spatial Data on the Web Best Practices" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-091r2", + "@id": "http://www.opengis.net/def/docs/16-062", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-04" + "@value": "2017-05-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff" + "@value": "Gobe Hobona, Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -20635,17 +20370,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-091r2.html" + "@id": "https://docs.ogc.org/per/16-062.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Application Schemas and JSON Technologies Engineering Report" + "@value": "Testbed-12 Catalogue and SPARQL Engineering Report" }, { "@language": "en", - "@value": "18-091r2" + "@value": "16-062" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -20655,7 +20390,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) enhances the understanding of the relationships between data exchange based on Geography Markup Language (GML), JavaScript Object Notation (JSON), and Resource Description Framework (RDF) for future web services, e.g. Web Feature Service (WFS) 3.0. The work documented in this report:\r\n\r\ncontributes to the ability to bridge between technology-dependent alternate representations of “features” (real-world objects), and to consistently employ alternate encoding technologies (Extensible Markup Language (XML), JSON, RDF) to exchange information about “features”; and\r\n\r\ndetermines principled techniques for the development of JSON-based schemas from ISO 19109-conformant application schemas.\r\n\r\n" + "@value": "This engineering report has been produced by the OGC® Testbed-12 initiative.\r\nThe engineering report evaluates interoperability between a variety of\r\ncatalogues. The report presents a comparison of the catalogues, with the same\r\ndatasets uploaded. The catalogues discussed in the report include services\r\nconforming to Catalogue Service for Web (CSW) version 2.0.2 and 3.0, including\r\nservices based on the ebRIM profile of CSW 2.0.2 and an extension of CSW 3.0\r\nwith OpenSearch and SOAP. The engineering report presents results from tests\r\nusing a multi-catalogue client to interact with each service. The engineering\r\nreport also provides a comparison of CSW and services based on the Data\r\nCatalogue (DCAT) specification covering functionality, expressiveness and\r\nusability of CSW and DCAT. The comparison is supported by a discussion on the\r\nimplementation of a SPARQL / GeoSPARQL service." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20666,35 +20401,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-091r2" + "@value": "16-062" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Application Schemas and JSON Technologies Engineering Report" + "@value": "Testbed-12 Catalogue and SPARQL Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-028", + "@id": "http://www.opengis.net/def/docs/07-036r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-01-17" + "@value": "2018-04-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Josh Lieberman, Lou Reich, Peter Vretanos" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -20704,27 +20439,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1317" + "@id": "https://portal.ogc.org/files/?artifact_id=74183&version=2" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Web Services UDDI Experiment" + "@value": "07-036r1" }, { "@language": "en", - "@value": "03-028" + "@value": "Geography Markup Language (GML) Encoding Standard - with corrigendum" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document lists the design principles, requirements, and experimental results for future versions of a potential OGC - UDDI (Universal Discovery, Description, and Integration) profile of the OGC Catalog Implementation Specification. Specifically, it describes the usage scenarios, workplan, and experimental results for discovery of OGC services (including registries) through the UDDI interface using SOAP (Simple Object Access Protocol) messaging protocols. The baseline for this experiment is the specification for UDDI version 2 and use of private UDDI implementations. " + "@value": "The OpenGIS® Geography Markup Language Encoding Standard (GML) The Geography Markup Language (GML) is an XML grammar for expressing geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. As with most XML based grammars, there are two parts to the grammar – the schema that describes the document and the instance document that contains the actual data.\r\nA GML document is described using a GML Schema. This allows users and developers to describe generic geographic data sets that contain points, lines and polygons. However, the developers of GML envision communities working to define community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas] that are specialized extensions of GML. Using application schemas, users can refer to roads, highways, and bridges instead of points, lines and polygons. If everyone in a community agrees to use the same schemas they can exchange data easily and be sure that a road is still a road when they view it.\r\n\r\nClients and servers with interfaces that implement the OpenGIS® Web Feature Service Interface Standard[http://www.opengeospatial.org/standards/wfs] read and write GML data. GML is also an ISO standard (ISO 19136:2007) [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32554 ]. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20735,35 +20470,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-028" + "@value": "07-036r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Services UDDI Experiment" + "@value": "OpenGIS Geography Markup Language (GML) Encoding Standard - with corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-014", + "@id": "http://www.opengis.net/def/docs/08-139r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-01-31" + "@value": "2011-01-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "George Demmy, Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -20773,27 +20508,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8848" + "@id": "https://portal.ogc.org/files/?artifact_id=40537" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Image CRSs for IH4DS" + "@value": "PDF Geo-registration Encoding Best Practice Version 2.2" }, { "@language": "en", - "@value": "05-014" + "@value": "08-139r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion Paper specifies image coordinate reference system (CRS) definitions designed for possible use by WCTS and WCS servers and clients, initially in the IH4DS thread of the OWS 2 interoperability initiative. This report specifies image CRS definitions suitable for both ungeorectified and georectified images, where an ungeorectified image can be georeferenced or not." + "@value": "The intended audience of this document is a developer of software for creating and consuming geo=registered PDF documents that conform to PDF geo-registration 2.2. It specifies how to create the necessary PDF objects that identify a region of the PDF page as a map and describe the map’s coordinate systems. Map creation and rendering to a PDF page are not addressed. The underlying PDF file format is not addressed. The file format is specified in PDF Reference[1] ." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20804,35 +20539,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-014" + "@value": "08-139r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Image CRSs for IH4DS" + "@value": "PDF Geo-registration Encoding Best Practice Version 2.2" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-114r2", + "@id": "http://www.opengis.net/def/docs/01-014r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-04-15" + "@value": "2001-10-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Martin Desruisseaux" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -20842,27 +20577,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/16-114r2/16-114r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1012" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Moving Features Encoding Extension: netCDF" + "@value": "01-014r5" }, { "@language": "en", - "@value": "16-114r2" + "@value": "CT Definition Data for Coordinate Reference" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The netCDF Moving Features encoding extension is a summary of conventions that supports efficient exchange of simple moving features as binary files. This Discussion Paper is a complement to the Moving Features Encoding Part I: XML Core and an alternative to the Simple Comma Separated Values (CSV) extension. Compared to the CSV encoding, this netCDF encoding offers more compact storage and better performance at the cost of additional restrictions on the kinds of features that can be stored." + "@value": "A data model for coordinate reference systems to provide a common framework across all OGC specifications." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20873,30 +20608,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-114r2" + "@value": "01-014r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Moving Features Encoding Extension: netCDF" + "@value": "CT Definition Data for Coordinate Reference" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-023", + "@id": "http://www.opengis.net/def/docs/09-036r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-12-13" + "@value": "2009-07-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff, Julia Wagemann, Josh Lieberman" + "@value": "Jan Herrmann, Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -20911,17 +20646,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-023.html" + "@id": "https://portal.ogc.org/files/?artifact_id=34976" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Earth Observation Cloud Platform Concept Development Study Report" + "@value": "OWS-6 GeoXACML Engineering Report" }, { "@language": "en", - "@value": "21-023" + "@value": "09-036r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -20931,7 +20666,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Earth Observation Cloud Platform Concept Development Study (CDS) evaluates the readiness of satellite data providers and cloud service providers, as well as the maturity of their current systems, with regard to real-world deployment of the new “Applications-to-the-Data” paradigm, using cloud environments for EO data storage, processing, and retrieval." + "@value": "The aim of this OGC Engineering Report is to show how to provide access control for OGC Web Services (OWS). In the first part of this document we will briefly introduce the relevant details of XACML 2.0, OGC GeoXACML 1.0 and some related profiles. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -20942,35 +20677,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-023" + "@value": "09-036r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Earth Observation Cloud Platform Concept Development Study Report" + "@value": "OWS-6 GeoXACML Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-031r1", + "@id": "http://www.opengis.net/def/docs/15-113r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-12" + "@value": "2018-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -20980,27 +20715,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-031r1.html" + "@id": "https://portal.ogc.org/files/15-113r5" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 GeoPackage Change Request Evaluations" + "@value": "15-113r5" }, { "@language": "en", - "@value": "16-031r1" + "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Testbed 12 work has resulted in Change Requests (CRs) to the GeoPackage Encoding Standard. CRs have been submitted to the GeoPackage Standards Working Group (SWG) as GitHub issues. This engineering report (ER) summarizes the results of these activities." + "@value": "The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -21011,30 +20746,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-031r1" + "@value": "15-113r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 GeoPackage Change Request Evaluations" + "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-018", + "@id": "http://www.opengis.net/def/docs/22-038r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-15" + "@value": "2023-03-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Charles Chen" + "@value": "Martin Desruisseaux" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -21049,17 +20784,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-018.html" + "@id": "https://docs.ogc.org/per/22-038r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Aviation Architecture Engineering Report" + "@value": "22-038r2" }, { "@language": "en", - "@value": "16-018" + "@value": "Testbed-18: Reference Frame Transformation Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -21069,7 +20804,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Open Geospatial Consortium (OGC)® Engineering Report (ER) describes the architecture implemented in the OGC Testbed 12 Aviation thread. This report provides an overview of the technical architecture for the interoperable exchange of flight and aeronautical information using OGC services. The aviation architecture consists of multiple components developed by the Aviation thread, as well as specialized engineering reports per each work area. This report will provide an introduction to each work area and contain references to applicable reports. This report also describes the Aviation thread demonstration scenarios, outcomes, and benefits." + "@value": "Currently, most OGC standards focus on data that is observed on the ground or directly above planet Earth. Other standards, such as GeoSciML, provide a data model and transfer standard for geological data. Other projects have considered data models and exchange standards for the seas and oceans. Extra-terrestrial space and the exact location of remote spaceborne sensors has been less in focus. This OGC Testbed 18 Engineering Report (ER) starts with an evaluation of current standards and then proposes changes or extensions to those standards in order to describe objects in orbit around any celestial body or in free flight in our solar system with respect to their location, trajectory, and orientation. Finally standard-based mechanisms to transform a location within a reference frame to a location within another reference frame are examined." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -21080,35 +20815,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-018" + "@value": "22-038r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Aviation Architecture Engineering Report" + "@value": "Testbed-18: Reference Frame Transformation Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-053r1", + "@id": "http://www.opengis.net/def/docs/20-057", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-03-11" + "@value": "2022-11-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann, Jinsongdi Yu" + "@value": "Joan Masó, Jérôme Jacovella-St-Louis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -21118,27 +20853,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=54209" + "@id": "https://docs.ogc.org/is/20-057/20-057.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Service Interface Standard - CRS Extension" + "@value": "OGC API - Tiles - Part 1: Core" }, { "@language": "en", - "@value": "11-053r1" + "@value": "20-057" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request that allows a client, a service, or other application to specify the Coordinate Reference System (CRS) in which coverages are delivered. Note that the CRS of the input bounding box is already defined in the OGC WCS Core Implementation Standard [OGC 09-110r3]." + "@value": "OGC API — Tiles is a standard defining building blocks for creating Web APIs that support the retrieval of geospatial information as tiles. Different forms of geospatial information are supported, such as tiles of vector features (“vector tiles”), coverages, maps (or imagery) and other types of geospatial information. Although it can be used independently, the OGC API — Tiles building blocks can be combined with other OGC API Standards and draft specifications for additional capabilities or increasing interoperability for specific types of data. The OGC API — Tiles standard references the OGC Two Dimensional Tile Matrix Set (TMS) and Tileset Metadata standard, which defines logical models and encodings for specifying tile matrix sets and describing tile sets. A tile matrix set is a tiling scheme that enables an application to partition and index space based on a set of regular grids defined for multiple scales in a Coordinate Reference System (CRS).\r\n\r\nThis specification is a successor to the OGC’s Web Map Tile Service (WMTS) standard, focusing on simple reusable REST API building blocks which can be described using the OpenAPI specification. Whereas WMTS focused on map tiles, the OGC API — Tiles standard has been designed to support any form of tiled data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -21149,35 +20884,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-053r1" + "@value": "20-057" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Coverage Service Interface Standard - CRS Extension" + "@value": "OGC API - Tiles - Part 1: Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-169", + "@id": "http://www.opengis.net/def/docs/23-025", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-09-12" + "@value": "2023-11-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steven Keens" + "@value": "Gobe Hobona, Joana Simoes, Tom Kralidis, Martin Desruisseaux, Angelos Tzotsos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -21187,27 +20922,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27047" + "@id": "https://docs.ogc.org/per/23-025.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-5 WCS JPIP Coverage Subsetting Engineering Report" + "@value": "2023 Open Standards and Open Source Software Code Sprint Summary Engineering Report" }, { "@language": "en", - "@value": "07-169" + "@value": "23-025" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC document represents an OWS-5 SWE thread Engineering Report on sub-setting georeferencable imagery. It discusses how to handle georeferencable imagery in the JPEG2000 format as well as using JPIP within the WCS-T and the SWE set of services." + "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from the 25th to the 27th of April 2023 to advance support of open geospatial standards within the developer community, while also advancing the standards themselves. The code sprint was organized by the Open Geospatial Consortium (OGC), the Open Source Geospatial Foundation (OSGeo), and the Apache Software Foundation (ASF). The code sprint was sponsored by the Ordnance Survey and hosted by Camptocamp." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -21218,35 +20953,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-169" + "@value": "23-025" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-5 WCS JPIP Coverage Subsetting Engineering Report" + "@value": "2023 Open Standards and Open Source Software Code Sprint Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-096", + "@id": "http://www.opengis.net/def/docs/02-066r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-02-01" + "@value": "2002-08-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mike Botts" + "@value": "Jean-Philippe Humblet" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -21256,27 +20991,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=52162" + "@id": "https://portal.ogc.org/files/?artifact_id=1181" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-9: Engineering Report: Use of SWE Common and SensorML for GPS Messaging " + "@value": "Web Map Context Documents" }, { "@language": "en", - "@value": "12-096" + "@value": "02-066r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is an Engineering Report for the OWS-9 Interoperability Test Bed. The focus of the document is discussion and demonstration on the use of SWE Common Data 2.0 encodings to support an interoperable messaging description and encoding for the next generation GPS message streams into and out of the GPS navigation accuracy improvement services. The connection of SWE Common to SensorML 2.0 and the application of SensorML to describe the processing surrounding GPS navigation improvement will also be discussed." + "@value": "States how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent manner." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -21287,322 +21022,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-096" + "@value": "02-066r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-9: Engineering Report: Use of SWE Common and SensorML for GPS Messaging " - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/bp/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type Best Practices Document" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Documents of type Best Practices Document" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/15-005r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-037" - }, - { - "@id": "http://www.opengis.net/def/docs/12-066" - }, - { - "@id": "http://www.opengis.net/def/docs/14-003" - }, - { - "@id": "http://www.opengis.net/def/docs/16-114r3" - }, - { - "@id": "http://www.opengis.net/def/docs/17-084r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-169r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-129r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-066" - }, - { - "@id": "http://www.opengis.net/def/docs/16-004r4" - }, - { - "@id": "http://www.opengis.net/def/docs/16-010r5" - }, - { - "@id": "http://www.opengis.net/def/docs/21-068" - }, - { - "@id": "http://www.opengis.net/def/docs/13-015" - }, - { - "@id": "http://www.opengis.net/def/docs/14-106" - }, - { - "@id": "http://www.opengis.net/def/docs/06-142r1" - }, - { - "@id": "http://www.opengis.net/def/docs/13-043" - }, - { - "@id": "http://www.opengis.net/def/docs/06-126r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-018r2" - }, - { - "@id": "http://www.opengis.net/def/docs/20-089r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-010r4" - }, - { - "@id": "http://www.opengis.net/def/docs/08-167r2" - }, - { - "@id": "http://www.opengis.net/def/docs/12-032r2" - }, - { - "@id": "http://www.opengis.net/def/docs/16-070r4" - }, - { - "@id": "http://www.opengis.net/def/docs/07-092r3" - }, - { - "@id": "http://www.opengis.net/def/docs/12-111r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-011r5" - }, - { - "@id": "http://www.opengis.net/def/docs/17-011r2" - }, - { - "@id": "http://www.opengis.net/def/docs/16-004r5" - }, - { - "@id": "http://www.opengis.net/def/docs/16-003r4" - }, - { - "@id": "http://www.opengis.net/def/docs/09-102r3a" - }, - { - "@id": "http://www.opengis.net/def/docs/08-139r3" - }, - { - "@id": "http://www.opengis.net/def/docs/11-122r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-006r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-005r2" - }, - { - "@id": "http://www.opengis.net/def/docs/21-007" - }, - { - "@id": "http://www.opengis.net/def/docs/14-110r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-107r3" - }, - { - "@id": "http://www.opengis.net/def/docs/05-035r2" - }, - { - "@id": "http://www.opengis.net/def/docs/03-002r9" - }, - { - "@id": "http://www.opengis.net/def/docs/20-095" - }, - { - "@id": "http://www.opengis.net/def/docs/13-039" - }, - { - "@id": "http://www.opengis.net/def/docs/16-003r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-188r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-120r6" - }, - { - "@id": "http://www.opengis.net/def/docs/16-070r2" - }, - { - "@id": "http://www.opengis.net/def/docs/21-070" - }, - { - "@id": "http://www.opengis.net/def/docs/15-120r5" - }, - { - "@id": "http://www.opengis.net/def/docs/16-086r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-010r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-006r4" - }, - { - "@id": "http://www.opengis.net/def/docs/16-011r4" - }, - { - "@id": "http://www.opengis.net/def/docs/07-118r9" - }, - { - "@id": "http://www.opengis.net/def/docs/16-140r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-003r3" - }, - { - "@id": "http://www.opengis.net/def/docs/08-125r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-011r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-005r4" - }, - { - "@id": "http://www.opengis.net/def/docs/14-004r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-120r4" - }, - { - "@id": "http://www.opengis.net/def/docs/16-006r5" - }, - { - "@id": "http://www.opengis.net/def/docs/11-135r2" - }, - { - "@id": "http://www.opengis.net/def/docs/09-102" - }, - { - "@id": "http://www.opengis.net/def/docs/07-118r8" - }, - { - "@id": "http://www.opengis.net/def/docs/09-102r3" - }, - { - "@id": "http://www.opengis.net/def/docs/06-021r4" - }, - { - "@id": "http://www.opengis.net/def/docs/06-095" - }, - { - "@id": "http://www.opengis.net/def/docs/14-012r1" - }, - { - "@id": "http://www.opengis.net/def/docs/02-007r4" - }, - { - "@id": "http://www.opengis.net/def/docs/07-097" - }, - { - "@id": "http://www.opengis.net/def/docs/15-003" - }, - { - "@id": "http://www.opengis.net/def/docs/16-009r3" - }, - { - "@id": "http://www.opengis.net/def/docs/10-189r2" - }, - { - "@id": "http://www.opengis.net/def/docs/15-005r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-028r3" - }, - { - "@id": "http://www.opengis.net/def/docs/09-153r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-005r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-009r5" - }, - { - "@id": "http://www.opengis.net/def/docs/15-004" - }, - { - "@id": "http://www.opengis.net/def/docs/16-009r4" - }, - { - "@id": "http://www.opengis.net/def/docs/16-004r3" - }, - { - "@id": "http://www.opengis.net/def/docs/10-003r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-107" - }, - { - "@id": "http://www.opengis.net/def/docs/05-042r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-063r1" - }, - { - "@id": "http://www.opengis.net/def/docs/13-042" - }, - { - "@id": "http://www.opengis.net/def/docs/16-070r3" - }, - { - "@id": "http://www.opengis.net/def/docs/11-035r1" - }, - { - "@id": "http://www.opengis.net/def/docs/10-028r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Documents of type Best Practices Document" + "@value": "Web Map Context Documents" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-083r4", + "@id": "http://www.opengis.net/def/docs/11-017", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-09-09" + "@value": "2011-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó, Jérôme Jacovella-St-Louis" + "@value": "Andreas Matheus, Jan Herrmann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -21617,17 +21060,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/17-083r4/17-083r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=42734" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Two Dimensional Tile Matrix Set and Tile Set Metadata" + "@value": "Geospatial eXtensible Access Control Markup Language (GeoXACML) Version 1 Corrigendum" }, { "@language": "en", - "@value": "17-083r4" + "@value": "11-017" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -21637,7 +21080,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Two Dimensional Tile Matrix Set and Tile Set Metadata Standard defines the rules and requirements for a tile matrix set as a way to index space based on a set of regular grids defining a domain (tile matrix) for a limited list of scales in a Coordinate Reference System (CRS) as defined in OGC 18-005r5 Abstract Specification Topic 2: Referencing by Coordinates. This content was initially included in the OGC 07-057r7 OpenGIS Web Map Tile Service Implementation Standard (WMTS) and was separated out into the OGC 17-083r2 OGC Two Dimensional Tile Matrix Set Standard version 1.0, to support reusability in other data formats of services that need a tiling scheme. This document is a revision of the OGC 17-083r2 document and the general tile matrix set concept is inherited from it with small additions. In a tile matrix set, each tile matrix is divided into regular tiles. In a tile matrix set, a tile can be univocally identified by a tile column, a tile row, and a tile matrix identifier. The OGC Two Dimensional Tile Matrix Set and Tile Set Metadata Standard describes a data structure defining the properties of the tile matrix set in both Unified Modeling Language (UML) diagrams and in tabular form. This document also defines a new data structure, called tile set metadata, that can be used to describe a particular set of tiles following a tile matrix set. Extensible Markup Language (XML) and JavaScript Object Notation (JSON) encodings are described both for tile matrix sets and tile matrix set metadata. It includes tile matrix set limits, links to the tile matrix set, details of the original data represented by the tile set and a nice point of origin to start exploring the tile set. Finally, the document offers practical examples of tile matrix sets both for common global projections and for specific regions." + "@value": "The OpenGIS® Geospatial eXtensible Access Control Markup Language Encoding Standard (GeoXACML) defines a geospatial extension to the OASIS standard “eXtensible Access Control Markup Language (XACML)” [www.oasis-open.org/committees/xacml/]. This extension incorporates spatial data types and spatial authorization decision functions based on the OGC Simple Features[http://www.opengeospatial.org/standards/sfa] and GML[http://www.opengeospatial.org/standards/gml] standards. GeoXACML is a policy language that supports the declaration and enforcement of access rights across jurisdictions and can be used to implement interoperable access control systems for geospatial applications such as Spatial Data Infrastructures. GeoXACML is not designed to be a rights expression language and is therefore not an extension of the OGC GeoDRM Reference Model (Topic 18 in the OpenGIS® Abstract Specification [http://www.opengeospatial.org/standards/as]). " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -21648,35 +21091,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-083r4" + "@value": "11-017" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Two Dimensional Tile Matrix Set and Tile Set Metadata" + "@value": "Geospatial eXtensible Access Control Markup Language (GeoXACML) Version 1 Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-016r1", + "@id": "http://www.opengis.net/def/docs/09-146r8", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-12-19" + "@value": "2019-10-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Michael A. Leedahl" + "@value": "Peter Baumann, Eric Hirschorn, Joan Masó" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -21686,27 +21129,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-016r1.html" + "@id": "https://docs.ogc.org/is/09-146r8/09-146r8.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Data Centric Security" + "@value": "Coverage Implementation Schema with Corrigendum" }, { "@language": "en", - "@value": "19-016r1" + "@value": "09-146r8" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Testbed-15 Data Centric Security Engineering Report (ER) discusses the current state of security in protecting data in a geospatial environment. The ER examines the use of encrypted container formats such as NATO STANAG 4778 Information on standard Metadata Binding with metadata as defined in NATO STANAG 4774 Confidentiality Metadata Label Syntax in combination with geospatial data using the encoding for an OGC Web Feature Service (WFS) FeatureCollection structure. This report also makes a recommendation for the creation of new media types to support output container formats such as STANAG 4778. The report then discusses various implementation scenarios in which a STANAG 4778 (eXtensible Markup Language (XML) container maintains encrypted data from author to service to viewer. These implementations use the new OGC API - Features - Part 1: Core with features encrypted using keys supplied by feature authors and users." + "@value": "Coverages represent homogeneous collections of values located in space/time, such as spatio-temporal sensor, image, simulation, and statistics data. Common examples include 1-D timeseries, 2-D imagery, 3-D x/y/t image timeseries and x/y/z geophysical voxel models, as well as 4-D x/y/z/t climate and ocean data. Generally, coverages encompass multi-dimen­sional regular and irregular grids, point clouds, and general meshes.\r\n\r\nThis Coverage Implementation Schema (CIS) specifies the OGC coverage model by establishing a concrete, interoperable, conformance-testable coverage structure. It is based on the abstract concepts of OGC Abstract Topic 6 [1] (which is identical to ISO 19123) which spec­i­fies an abstract model which is not per se interoperable – in other words, many different and incompatible implementations of the abstract model are possible. CIS, on the other hand, is interoperable in the sense that coverages can be conformance tested, regardless of their data format encoding, down to the level of single “pixels” or “voxels.”\r\n\r\nCoverages can be encoded in any suitable format (such as GML, JSON, GeoTIFF, or Net­CDF) and can be partitioned, e.g., for a time-interleaved representation. Coverages are independent from service definitions and, therefore, can be accessed through a variety of OGC services types, such as the Web Coverage Service (WCS) Standard [8]. The coverage structure can serve a wide range of coverage application domains, thereby contributing to harmon­ization and interoperability between and across these domains." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -21717,35 +21160,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-016r1" + "@value": "09-146r8" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Data Centric Security" + "@value": "OGC Coverage Implementation Schema with Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-007r4", + "@id": "http://www.opengis.net/def/docs/12-000r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-09-16" + "@value": "2020-08-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Schut, Arliss Whiteside" + "@value": "Mike Botts, Alexandre Robin, Eric Hirschorn" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -21755,27 +21198,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12184" + "@id": "https://docs.ogc.org/is/12-000r2/12-000r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Processing Service" + "@value": "12-000r2" }, { "@language": "en", - "@value": "05-007r4" + "@value": "SensorML: Model and XML Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the interface to a Web Processing Service (WPS). A WPS can be configured to offer any sort of GIS functionality to clients across a network, including access to pre-programmed calculations and/or computation models that operate on spatially referenced data. A WPS may offer calculations as simple as subtracting one set of spatially referenced numbers from another (e.g., determining the difference in influenza cases between two different seasons), or as complicated as a global climate change model. The data required by the WPS can be delivered across a network, or available at the server." + "@value": "The primary focus of the Sensor Model Language (SensorML) is to provide a robust and semantically-tied means of defining processes and processing components associated with the measurement and post-measurement transformation of observations. This includes sensors and actuators as well as computational processes applied pre- and post-measurement.\r\n\r\nThe main objective is to enable interoperability, first at the syntactic level and later at the semantic level (by using ontologies and semantic mediation), so that sensors and processes can be better understood by machines, utilized automatically in complex workflows, and easily shared between intelligent sensor web nodes.\r\n\r\nThis standard is one of several implementation standards produced under OGC’s Sensor Web Enablement (SWE) activity. This standard is a revision of content that was previously integrated in the SensorML version 1.0 standard (OGC 07-000)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -21786,29 +21229,25 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-007r4" + "@value": "12-000r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Processing Service" + "@value": "OGC SensorML: Model and XML Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-035r1", + "@id": "http://www.opengis.net/def/docs/09-110r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-26" - }, - { - "@type": "xsd:date", - "@value": "2006-05-02" + "@value": "2010-10-27" } ], "http://purl.org/dc/terms/creator": [ @@ -21818,10 +21257,7 @@ ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -21831,40 +21267,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=14022" - }, - { - "@id": "https://portal.ogc.org/files/?artifact_id=14895" + "@id": "https://portal.ogc.org/files/?artifact_id=41437" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Processing Service (WCPS)" - }, - { - "@language": "en", - "@value": "06-035r1" + "@value": "WCS 2.0 Interface Standard - Core" }, { "@language": "en", - "@value": "Web Coverage Processing Service" + "@value": "09-110r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Web Coverage Processing Service (WCPS) supports retrieval and processing of geo-spatial coverage data. WCPS grounds on the coverage model of the OGC Web Coverage Service (WCS) Implementation Specification where coverages are defined as digital geospatial information representing space-varying phenomena, currently constrained to equally spaced grids." - }, - { - "@value": "The Web Coverage Processing Service (WCPS) supports retrieval and processing of geo-spatial coverage data. WCPS uses the coverage model of the OGC Web Coverage Service (WCS) Implementation Specification: coverages are defined as digital geo-spatial information representing space-varying phenomena, currently constrained to equally spaced grids." + "@value": "This document specifies how a Web Coverage Service (WCS) offers multi-dimensional coverage data for access over the Internet. This document specifies a core set of requirements that a WCS implementation must fulfil. WCS extension standards add further functionality to this core; some of these are required in addition to the core to obtain a complete implementation. This document indicates which extensions, at a minimum, need to be considered in addition to this core to allow for a complete WCS implementation." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -21875,34 +21298,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-035r1" + "@value": "09-110r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Coverage Processing Service (WCPS)" - }, - { - "@language": "en", - "@value": "Web Coverage Processing Service" + "@value": "OGC® WCS 2.0 Interface Standard - Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-139", + "@id": "http://www.opengis.net/def/docs/17-023", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-02-05" + "@value": "2018-01-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jan Herrmann, Andreas Matheus" + "@value": "Pedro Gonçalves" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -21917,17 +21336,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51833" + "@id": "https://docs.ogc.org/per/17-023.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-9: SSI Security Rules Service Engineering Report" + "@value": "17-023" }, { "@language": "en", - "@value": "12-139" + "@value": "Testbed-13: EP Application Package Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -21937,7 +21356,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "In this engineering report we describe how to administrate XACML v2.0, XACML v3.0 and GeoXACML v1.0.1 access control policies through a “Security Rules Service”. Following the XACML and ISO terminology this service plays the role of a Policy Administration Point (PAP) and is therefore called XACML Policy Administration Point (XACML PAP) or XACML Policy Administration Web Service (XACML PAWS). \r\nAfter introducing OWS-9’s Common Rule Encoding and motivating all components required to administrate (Geo)XACML policies, we describe the interface of a powerful XACML PAP on a conceptual level. This interface definition could serve as a baseline for a future OASIS or OGC XACML Policy Administration Web Service (e.g. OGC XACML PAWS) specification.\r\n" + "@value": "The Application Package OGC Engineering Report (ER) defines a data model and serialization for Thematic Exploitation Platforms (TEP) Application Packages. A TEP refers to a computing platform that follows a given set of scenarios for users, data and ICT provision aggregated around an Earth Science thematic area. This ER is part of the Testbed-13 Earth Observation Clouds (EOC) effort to support the development by the European Space Agency (ESA) of the TEP by exercising envisioned workflows for data integration, processing, and analytics based on algorithms developed by users that are deployed in multiple clouds.\r\n\r\nThe wide usage of virtualization and the possibility to start virtual environments within Cloud services significantly simplifies the creation of environments and provisioning of resources. However, it still leaves a problem of portability between infrastructures. This ER identifies a strategy for packaging an application in a Cloud environment that will be able to run in a predictable manner in different computing production environments. The application packaging specifies the elements that will ensure:\r\n\r\nScientific reproducibility,\r\n\r\nDependencies identification and management,\r\n\r\nMaintainability from an operational perspective and avoid version pilling,\r\n\r\nPortability in different Cloud providers\r\n\r\nThe ER proposes the use of containers, defining everything required to make a piece of software run packaged into isolated containers. Unlike a Virtual Machine (VM), a container does not bundle a full Operating System (OS) - only libraries and settings required to make the software work are needed. This makes for efficient, lightweight, self-contained systems and guarantees that software will always run the same, regardless of where it’s deployed. A discussion on application deployment and execution is presented in the separate OGC Testbed-13 Application Deployment and Execution Service ER [1].\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -21948,35 +21367,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-139" + "@value": "17-023" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-9: SSI Security Rules Service Engineering Report" + "@value": "OGC Testbed-13: EP Application Package Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-091r2", + "@id": "http://www.opengis.net/def/docs/20-073", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-11" + "@value": "2020-10-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas Gilbert, Carsten Rönsdorf, Jim Plume, Scott Simmons, Nick Nisbet, Hans-Christoph Gruler, Thom" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -21986,27 +21405,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=96354" + "@id": "https://docs.ogc.org/per/20-073.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-091r2" + "@value": "OGC Earth Observation Applications Pilot: Summary Engineering Report" }, { "@language": "en", - "@value": "Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra" + "@value": "20-073" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Demand for digital representations of built environments is accelerating and can only be satisfied through greater software interoperability and data integration. The objective of the Integrated Digital Built Environment (IDBE) joint working group is to address this challenge by bringing together experts from the Open Geospatial Consortium and buildingSMART to coordinate the development of the relevant data standards. This document is an output from IDBE in which we describe the state of three of the most prominent built environment standards – CityGML, IFC and LandInfra – and describe some of the problems that hinder their integration; finally, we propose actions points for overcoming these problems." + "@value": "This Engineering Report (ER) summarizes the main achievements of the OGC Innovation Program initiative Earth Observation Applications Pilot, conducted between December 2019 and July 2020." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -22017,35 +21436,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-091r2" + "@value": "20-073" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra" + "@value": "OGC Earth Observation Applications Pilot: Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-017", + "@id": "http://www.opengis.net/def/docs/08-008r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-04-25" + "@value": "2008-04-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthes Rieke, Aleksandar Balaban" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -22055,27 +21474,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-017.html" + "@id": "https://portal.ogc.org/files/?artifact_id=27711" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Asynchronous Messaging for Aviation" + "@value": "Proposed Topic 19 - General Reference Systems" }, { "@language": "en", - "@value": "16-017" + "@value": "08-008r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Asynchronous Messaging for Aviation Engineering Report (ER) focuses on the design of an architecture to create an Publish/Subscribe (PubSub) messaging layer between different Aviation components such as clients, data provider instances and Data Brokers. In order to achieve interoperability among these components, the OGC PubSub 1.0 standard forms the basis of this architecture. The design of this architecture will cover methods for subscribing for specific subsets of data (e.g. Flight Information Exchange Model (FIXM) Flights intersecting a given Airspace), managing such subscriptions as well as publishing data to the Asynchronous Messaging Server. Different delivery methods such as Advanced Message Queuing Protocol (AMQP) 1.0, Java Message Service (JMS) and OASIS WS-Notification are considered. In particular, their harmonization with OGC PubSub 1.0 is evaluated.\r\n\r\nThis report focuses on the interface design required to define an interoperable approach for Aviation using this OGC PubSub 1.0. Specific service level integrations (i.e., Federal Aviation Administration (FAA) System-Wide Information Management (SWIM) and Single European Sky ATM Research Programme (SESAR) SWIM) have been investigated but an implementation has not been fulfilled." + "@value": "This discussion paper is a draft new topic volume for the OGC Abstract Specification, which may also be used to propose a corresponding new standard to ISO/TC 211. This document proposes extensions to OGC Abstract Specification Topic 2 — Spatial referencing by coordinates, and thus to ISO 19111 — Spatial referencing by coordinates. This discussion paper is posted for comments on the contents. Revision of this draft is planned, to improve some details while supporting the same abilities." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -22086,148 +21505,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-017" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@language": "en", - "@value": "Testbed-12 Asynchronous Messaging for Aviation" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-rp", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/02-066r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-088r6" - }, - { - "@id": "http://www.opengis.net/def/docs/02-024" - }, - { - "@id": "http://www.opengis.net/def/docs/01-029" - }, - { - "@id": "http://www.opengis.net/def/docs/04-016r3" - }, - { - "@id": "http://www.opengis.net/def/docs/03-022r3" - }, - { - "@id": "http://www.opengis.net/def/docs/03-064r5" - }, - { - "@id": "http://www.opengis.net/def/docs/00-029" - }, - { - "@id": "http://www.opengis.net/def/docs/03-109r1" - }, - { - "@id": "http://www.opengis.net/def/docs/01-014r5" - }, - { - "@id": "http://www.opengis.net/def/docs/04-019r2" - }, - { - "@id": "http://www.opengis.net/def/docs/03-010r7" - }, - { - "@id": "http://www.opengis.net/def/docs/03-010r9" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/08-068r2", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ - { - "@type": "xsd:date", - "@value": "2009-03-25" - } - ], - "http://purl.org/dc/terms/creator": [ - { - "@value": "Peter Baumann" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ - { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ - { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ - { - "@id": "https://portal.ogc.org/files/?artifact_id=32319" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ - { - "@language": "en", - "@value": "Web Coverage Processing Service (WCPS) Language Interface Standard" - }, - { - "@language": "en", - "@value": "08-068r2" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ - { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "The OGC® Web Coverage Processing Service (WCPS) defines a protocol-independent language for the extraction, processing, and analysis of multi-dimensional coverages representing sensor, image, or statistics data." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ - { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-068r2" + "@value": "08-008r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Coverage Processing Service (WCPS) Language Interface Standard" + "@value": "OpenGIS® Abstract Specification Proposed Topic 19 - General Reference Systems" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-013r3", + "@id": "http://www.opengis.net/def/docs/04-016r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-11-10" + "@value": "2004-06-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sergio Taleisnik, Terry Idol, Ph.D." + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -22237,27 +21543,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-013r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=6324" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-013r3" + "@value": "04-016r3" }, { "@language": "en", - "@value": "Towards a Federated Marine SDI: IHO and OGC standards applied to Marine Protected Area Data Engineering Report" + "@value": "OWS Common Recomendation Paper" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) summarizes the demonstrations, findings, and recommendations that emerged from the second phase of the OGC Federated Marine Spatial Data Infrastructure (FMSDI) Pilot. The goal of this initiative was to further advance the interoperability and usage of Marine Protected Area (MPA) data through the implementation of the IHO standard S-122 and several OGC API standards.\r\n\r\nThis ER describes a solution architecture consisting of a collection of interoperable components developed to demonstrate technologies that helped to achieve the objectives of this Pilot’s phase. This document describes a server built to serve MPA data through an OGC API – Features endpoint and two servers that combined MPA data with additional datasets and served it through both an OGC API – Features and an OGC API — EDR endpoint. This document also describes the three clients built to consume under different scenarios the data offered by the aforementioned servers. Finally, this ER captures lessons learned and recommendations for IHO and OGC API standards, and recommendations for future work." + "@value": "This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -22268,30 +21574,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-013r3" + "@value": "04-016r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Towards a Federated Marine SDI: IHO and OGC standards applied to Marine Protected Area Data Engineering Report" + "@value": "OWS Common Recomendation Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-045", + "@id": "http://www.opengis.net/def/docs/18-078", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-03-07" + "@value": "2019-02-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Harrison, Panagiotis (Peter) A. Vretanos" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -22306,17 +21612,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-045.html" + "@id": "https://docs.ogc.org/per/18-078.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Next Generation Web APIs - WFS 3.0 Engineering Report" + "@value": "18-078" }, { "@language": "en", - "@value": "18-045" + "@value": "WFS 3.0 Vector Tiles Extension Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -22326,145 +21632,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The objective of the Next Generation APIs - WFS 3.0 effort in OGC Testbed-14 was to develop and test the Web Feature Service (WFS) version 3.0 candidate standard. The initiative assessed OpenAPI, security based on OpenID Connect and OAuth 2.0 and WFS 3.0 extensions. The effort also began to assess methods to ease geospatial enterprise transition to next generation Application Programming Interfaces (APIs).\r\n\r\nThe purpose of this effort was not to preempt other next generation work taking place in OGC, but rather to inform and complement that work.\r\n\r\nThis Engineering Report (ER) describes the implementations and experiments conducted by OGC Testbed-14 participants to test next generation Web APIs. It includes descriptions of APIs to simplify and secure access to geospatial feature resources, and was tested in a scenario that showed how WFS 3.0 can support humanitarian relief activities." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ - { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-045" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@language": "en", - "@value": "OGC Testbed-14: Next Generation Web APIs - WFS 3.0 Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/15-097r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ - { - "@type": "xsd:date", - "@value": "2016-12-22" - } - ], - "http://purl.org/dc/terms/creator": [ - { - "@value": "Joan Masó, Lucy Bastin " - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ - { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ - { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ - { - "@id": "https://docs.ogc.org/is/15-097r1/15-097r1.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ - { - "@language": "en", - "@value": "Geospatial User Feedback Standard: Conceptual Model" - }, - { - "@language": "en", - "@value": "15-097r1" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ - { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "This standard defines a conceptual Geospatial User Feedback (GUF) data model. Geospatial User Feedback is metadata that is predominantly produced by the consumers of geospatial data products as they use and gain experience with those products. This standard complements existing metadata conventions whereby documents recording dataset characteristics and production workflows are generated by the creator, publisher or curator of a data product. As a part of metadata, the GUF data model reuses some elements of ISO 19115-1:2014 (the updated version of the OGC Abstract Specification Topic 11) but not the general structure. This selective use of ISO metadata elements prioritizes future interoperability with developing ISO metadata models. This standard is designed to be used combination with an encoding standard. Initially an XML encoding following the ISO 19139 encoding rules is specified in a separate OGC implementation standard (OGC 15-098). In the future other encodings may be defined, including examples such as the use of JSON-LD based on parts of schema.org." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ - { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-097r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@language": "en", - "@value": "OGC® Geospatial User Feedback Standard: Conceptual Model" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/21-066r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ - { - "@type": "xsd:date", - "@value": "2022-09-09" - } - ], - "http://purl.org/dc/terms/creator": [ - { - "@value": "Joan Maso" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ - { - "@id": "http://www.opengis.net/def/doc-type/notes" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ - { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ - { - "@id": "https://docs.ogc.org/is/17-083r4/21-066r1.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ - { - "@language": "en", - "@value": "21-066r1" - }, - { - "@language": "en", - "@value": "Release Notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata v.2.0" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ - { - "@id": "http://www.opengis.net/def/doc-type/notes" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "This document provides the set of revision notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata [OGC 17-083r4] and does not modify that Standard." + "@value": "Feature data tiling, colloquially referred to as 'vector tiling', is a data delivery method that allows for large vector feature datasets to be systematically split into subsets or tiles [1]. This engineering report (ER) presents an extension specification for publishing of vector tiles data through an Application Programming Interface (API) that conforms to the emerging version 3.0 of the Web Feature Service (WFS) standard. The core of the WFS 3.0 standard offers direct fine-grained access to geospatial information at the feature level. The WFS standard specifies discovery and query operations for web services that publish feature data. Extensions to the WFS 3.0 Core API offer other capabilities such as transaction operations.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -22475,35 +21643,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-066r1" + "@value": "18-078" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Release Notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata v.2.0" + "@value": "OGC Vector Tiles Pilot: WFS 3.0 Vector Tiles Extension Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-038r2", + "@id": "http://www.opengis.net/def/docs/10-103r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-03-09" + "@value": "2021-09-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Martin Desruisseaux" + "@value": "Gobe Hobona, Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/pol-nts" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -22513,27 +21681,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-038r2.html" + "@id": "https://docs.ogc.org/pol/10-103r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-038r2" + "@value": "OGC Name Type Specification - specification elements" }, { "@language": "en", - "@value": "Testbed-18: Reference Frame Transformation Engineering Report" + "@value": "10-103r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/pol-nts" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Currently, most OGC standards focus on data that is observed on the ground or directly above planet Earth. Other standards, such as GeoSciML, provide a data model and transfer standard for geological data. Other projects have considered data models and exchange standards for the seas and oceans. Extra-terrestrial space and the exact location of remote spaceborne sensors has been less in focus. This OGC Testbed 18 Engineering Report (ER) starts with an evaluation of current standards and then proposes changes or extensions to those standards in order to describe objects in orbit around any celestial body or in free flight in our solar system with respect to their location, trajectory, and orientation. Finally standard-based mechanisms to transform a location within a reference frame to a location within another reference frame are examined." + "@value": "The mission of the OGC Naming Authority (OGC-NA) is to provide the means through which OGC resources such as OGC documents, namespaces and ontologies can be controlled and managed such that they can provide clear and well-defined names and definitions. In the terminology defined in ISO 19135, OGC-NA is the Control Body for the register of OGC Names. This document specifies a rule for constructing OGC names that may be used for identifying specification elements defined in the OGC Specification Model – Modular Specification." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -22544,35 +21712,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-038r2" + "@value": "10-103r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-18: Reference Frame Transformation Engineering Report" + "@value": "OGC Name Type Specification - specification elements" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-035r2", + "@id": "http://www.opengis.net/def/docs/06-055r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-09-08" + "@value": "2006-07-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Rosinger, Stan Tillman" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -22582,27 +21750,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40441" + "@id": "https://portal.ogc.org/files/?artifact_id=16081" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-7 Information Sharing Engineering Report" + "@value": "06-055r1" }, { "@language": "en", - "@value": "10-035r2" + "@value": "GML 3.2 image geopositioning metadata application schema" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report describes an investigation and evaluation of various methods of sharing information within a collaborative environment accomplished during the OGC Web Services Testbed, Phase 7 (OWS-7). The intent of the OWS-7 Information Sharing activity was to move toward a standardized method of sharing geospatial data between Integrated Clients and potentially catalogs. This report reviews past OGC work within this area, makes recommendations based on the best parts of previous collaboration techniques, and provides recommendations for encoding documents for use in information sharing." + "@value": "This document specifies a GML 3.2 Application Schema for image geopositioning metadata, which is also an Application Schema of ISO 19139. This geopositioning metadata schema is used by the separately specified Image Geopositioning Service (IGS) interface that adjusts the georeferencing coordinate transformations of images." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -22613,104 +21781,43 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-035r2" + "@value": "06-055r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-7 Information Sharing Engineering Report" + "@value": "OpenGIS GML 3.2 image geopositioning metadata application schema" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-094", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ - { - "@type": "xsd:date", - "@value": "2013-02-05" - } - ], - "http://purl.org/dc/terms/creator": [ - { - "@value": "Debbie Wilson, Clemens Portele" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ - { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ - { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ - { - "@id": "https://portal.ogc.org/files/?artifact_id=51807" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ - { - "@language": "en", - "@value": "Aviation: AIRM Derivation" - }, - { - "@language": "en", - "@value": "12-094" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ - { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "This report describes the architecture, rules and tools developed within the OWS-9 Aviation Thread AIRM Derivation task. These rules and tools were demonstrated by transforming the AIRM Meteorology package into a Weather Exchange Model (WXXM) and GML/JSON implementation schema. " - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ - { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-094" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/doc-type/can", + "http://www.w3.org/2004/02/skos/core#narrower": [ { - "@language": "en", - "@value": "OWS-9 Aviation: AIRM Derivation" + "@id": "http://www.opengis.net/def/docs/06-050r3" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-053r1", + "@id": "http://www.opengis.net/def/docs/22-020", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-24" + "@value": "2023-01-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Paul Churchyard, Ajay Gupta" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -22720,27 +21827,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55244" + "@id": "https://docs.ogc.org/per/22-020.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CHISP-1 Engineering Report" + "@value": "22-020" }, { "@language": "en", - "@value": "13-053r1" + "@value": "Testbed-18: Identifiers for Reproducible Science Summary Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides a technical description of the work completed for the Climatology-Hydrology Information Sharing Pilot, Phase 1 project. \r\nThis document describes a profile of SOS, the NRCan GIN SOS 2.0 profile, developed in order to define a baseline of interoperability among the sensor observation services used in the project.\r\nThis document describes the use cases used to drive the component development during the project. The first use case was a flood scenario that involved exchanging cross-border hydrologic data with a unified alert service. The second use case involved calculating nutrient loads to the Great Lakes, which also involved the cross-border exchange of analytic data.\r\nThis document describes each component developed during the project and the challenges encountered and overcome during the development. The newly developed components include a nutrient load calculation client, a SOS integrating water quality data form the U.S. and Canada, a nutrient load calculation service, an upstream gauge service, a subscription client, and an event notification service composed of a number of sub-components including a subscription broker, an observation harvester and a CAP alert client.\r\n" + "@value": "The OGC’s Testbed 18 initiative explored the following six tasks.\r\n\r\n1.) Advanced Interoperability for Building Energy\r\n2.) Secure Asynchronous Catalogs\r\n3.) Identifiers for Reproducible Science\r\n4.) Moving Features and Sensor Integration\r\n5.) 3D+ Data Standards and Streaming\r\n6.) Machine Learning Training Data\r\nTestbed 18 Task 3, Identifiers for Reproducible Science, explored and developed workflows demonstrating best practices at the intersection of Findable, Accessible, Interoperable, and Reusable (or FAIR) data and reproducible science.\r\n\r\nThe workflows developed in this Testbed included:\r\n\r\nthe development of a Whole Tail workflow for land cover classification (52 Degrees North);\r\nthe development of a reproducible workflow for a deep learning application for target detection (Arizona State University);\r\nthe implementation of reproducible workflows following the approach described in the OGC API Process Part 3: Workflows and Chaining for Modular OGC API Workflows (Ecere);\r\nthe development of a reproducible workflow that runs an OGC API — Process and Feature Server instance within a Whole Tale environment (GeoLabs); and\r\nthe development of a water body detection Application Package to cover the identifier assignment and reproducibility from code to several execution scenarios (local, Exploitation Platform, Whole Tale) (Terradue).\r\nTestbed 18 participants identified considerations and limitations for reproducible workflows and recommendations for future work to identify the benefits of reproducible science for healthcare use cases." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -22751,35 +21858,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-053r1" + "@value": "22-020" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® CHISP-1 Engineering Report" + "@value": "Testbed-18: Identifiers for Reproducible Science Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-048r1", + "@id": "http://www.opengis.net/def/docs/01-026r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-03-08" + "@value": "2001-03-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Howard Butler" + "@value": "Serge Margoulies" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -22789,27 +21896,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-048r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1031" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-048r1" + "@value": "01-026r1" }, { "@language": "en", - "@value": "Point Cloud Data Handling Engineering Report" + "@value": "Geocoder" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) describes requirements that a point cloud web service must satisfy to enable application developers to provide convenient remote access to point clouds. It provides a short contrast of five point cloud web service software approaches (Esri I3S, 3D Tiles, Greyhound, PotreeConverter, and Entwine) and their implementations available at the time of the report. A small industry survey about these requirements is also provided in support of the report’s discussion about formats, web service requirements, industry support, and industry desire on these topics.\r\n\r\n" + "@value": "*RETIRED* Geocoding is the process of linking words, terms and codes found in a text string to their applicable geospatial features, with known locations. (Locations are defined as geometry; usually points with x, y coordinates.)" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -22820,30 +21927,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-048r1" + "@value": "01-026r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Point Cloud Data Handling Engineering Report" + "@value": "Geocoder" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-127", + "@id": "http://www.opengis.net/def/docs/06-184r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-08-25" + "@value": "2007-08-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Christian Elfers, Roland M. Wagner" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -22858,17 +21965,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=29542" + "@id": "https://portal.ogc.org/files/?artifact_id=21285" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-127" + "@value": "GeoDRM Engineering Viewpoint and supporting Architecture" }, { "@language": "en", - "@value": "GML 3.2 implementation of XML schemas in 07-000" + "@value": "06-184r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -22878,7 +21985,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "" + "@value": "This GeoDRM engineering viewpoint document describes use cases and concepts for GeoDRM, as well as references to distributed computing concepts which are not GeoDRM sensu stricto but are required for any GeoDRM implementation. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -22889,29 +21996,29 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-127" + "@value": "06-184r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML 3.2 implementation of XML schemas in 07-000" + "@value": "GeoDRM Engineering Viewpoint and supporting Architecture" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/d-is/collection", + "@id": "http://www.opengis.net/def/doc-type/dp/collection", "@type": [ "http://www.w3.org/2004/02/skos/core#Collection" ], "http://www.w3.org/2000/01/rdf-schema#label": [ { - "@value": "Documents of type Implementation Specification - deprecated " + "@value": "Documents of type Discussion Paper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Documents of type Implementation Specification - deprecated " + "@value": "Documents of type Discussion Paper" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -22921,151 +22028,523 @@ ], "http://www.w3.org/2004/02/skos/core#member": [ { - "@id": "http://www.opengis.net/def/docs/04-095" + "@id": "http://www.opengis.net/def/docs/16-084" }, { - "@id": "http://www.opengis.net/def/docs/09-147r1" + "@id": "http://www.opengis.net/def/docs/07-160r1" }, { - "@id": "http://www.opengis.net/def/docs/12-063r5" + "@id": "http://www.opengis.net/def/docs/07-095r2" }, { - "@id": "http://www.opengis.net/def/docs/99-049" + "@id": "http://www.opengis.net/def/docs/02-017r1" }, { - "@id": "http://www.opengis.net/def/docs/10-126r3" + "@id": "http://www.opengis.net/def/docs/05-117" }, { - "@id": "http://www.opengis.net/def/docs/07-014r3" + "@id": "http://www.opengis.net/def/docs/09-112" }, { - "@id": "http://www.opengis.net/def/docs/07-144r2" + "@id": "http://www.opengis.net/def/docs/07-138r1" }, { - "@id": "http://www.opengis.net/def/docs/02-069" + "@id": "http://www.opengis.net/def/docs/06-182r1" }, { - "@id": "http://www.opengis.net/def/docs/07-026r2" + "@id": "http://www.opengis.net/def/docs/08-058r1" }, { - "@id": "http://www.opengis.net/def/docs/02-059" + "@id": "http://www.opengis.net/def/docs/08-054r1" }, { - "@id": "http://www.opengis.net/def/docs/07-067r2" + "@id": "http://www.opengis.net/def/docs/21-067" }, { - "@id": "http://www.opengis.net/def/docs/10-157r3" + "@id": "http://www.opengis.net/def/docs/05-102r1" }, { - "@id": "http://www.opengis.net/def/docs/02-023r4" + "@id": "http://www.opengis.net/def/docs/08-073r2" }, { - "@id": "http://www.opengis.net/def/docs/05-016" + "@id": "http://www.opengis.net/def/docs/13-068" }, { - "@id": "http://www.opengis.net/def/docs/05-008c1" + "@id": "http://www.opengis.net/def/docs/04-039" }, { - "@id": "http://www.opengis.net/def/docs/07-002r3" + "@id": "http://www.opengis.net/def/docs/08-001" }, { - "@id": "http://www.opengis.net/def/docs/01-047r2" + "@id": "http://www.opengis.net/def/docs/19-004" }, { - "@id": "http://www.opengis.net/def/docs/07-110r2" + "@id": "http://www.opengis.net/def/docs/06-045r1" }, { - "@id": "http://www.opengis.net/def/docs/09-110r3" + "@id": "http://www.opengis.net/def/docs/19-090r1" }, { - "@id": "http://www.opengis.net/def/docs/06-083r8" + "@id": "http://www.opengis.net/def/docs/06-155" }, { - "@id": "http://www.opengis.net/def/docs/13-026r8" + "@id": "http://www.opengis.net/def/docs/16-142" }, { - "@id": "http://www.opengis.net/def/docs/05-076" + "@id": "http://www.opengis.net/def/docs/12-027r3" }, { - "@id": "http://www.opengis.net/def/docs/00-028" + "@id": "http://www.opengis.net/def/docs/13-100" }, { - "@id": "http://www.opengis.net/def/docs/06-104r3" + "@id": "http://www.opengis.net/def/docs/20-088" }, { - "@id": "http://www.opengis.net/def/docs/07-067r5" + "@id": "http://www.opengis.net/def/docs/07-056r1" }, { - "@id": "http://www.opengis.net/def/docs/01-068r3" + "@id": "http://www.opengis.net/def/docs/03-014" }, { - "@id": "http://www.opengis.net/def/docs/02-058" + "@id": "http://www.opengis.net/def/docs/08-071" }, { - "@id": "http://www.opengis.net/def/docs/02-087r3" + "@id": "http://www.opengis.net/def/docs/08-079" }, { - "@id": "http://www.opengis.net/def/docs/09-025r1" + "@id": "http://www.opengis.net/def/docs/03-026" }, { - "@id": "http://www.opengis.net/def/docs/03-036r2" + "@id": "http://www.opengis.net/def/docs/21-077" }, { - "@id": "http://www.opengis.net/def/docs/04-095c1" + "@id": "http://www.opengis.net/def/docs/15-012r2" }, { - "@id": "http://www.opengis.net/def/docs/07-022r1" + "@id": "http://www.opengis.net/def/docs/06-140" }, { - "@id": "http://www.opengis.net/def/docs/02-009" + "@id": "http://www.opengis.net/def/docs/07-007r1" }, { - "@id": "http://www.opengis.net/def/docs/06-103r3" + "@id": "http://www.opengis.net/def/docs/07-023r2" }, { - "@id": "http://www.opengis.net/def/docs/99-051" + "@id": "http://www.opengis.net/def/docs/07-041r1" }, { - "@id": "http://www.opengis.net/def/docs/02-070" + "@id": "http://www.opengis.net/def/docs/18-041r1" }, { - "@id": "http://www.opengis.net/def/docs/04-021r3" + "@id": "http://www.opengis.net/def/docs/17-049" }, { - "@id": "http://www.opengis.net/def/docs/05-134" + "@id": "http://www.opengis.net/def/docs/15-100r1" }, { - "@id": "http://www.opengis.net/def/docs/05-126" + "@id": "http://www.opengis.net/def/docs/11-094" }, { - "@id": "http://www.opengis.net/def/docs/03-065r6" + "@id": "http://www.opengis.net/def/docs/11-163" + }, + { + "@id": "http://www.opengis.net/def/docs/08-127" + }, + { + "@id": "http://www.opengis.net/def/docs/13-101" + }, + { + "@id": "http://www.opengis.net/def/docs/10-134" + }, + { + "@id": "http://www.opengis.net/def/docs/05-029r4" + }, + { + "@id": "http://www.opengis.net/def/docs/08-122r2" + }, + { + "@id": "http://www.opengis.net/def/docs/17-059" + }, + { + "@id": "http://www.opengis.net/def/docs/10-001" + }, + { + "@id": "http://www.opengis.net/def/docs/07-169" + }, + { + "@id": "http://www.opengis.net/def/docs/05-084" + }, + { + "@id": "http://www.opengis.net/def/docs/03-025" + }, + { + "@id": "http://www.opengis.net/def/docs/18-001r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-088r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-171" + }, + { + "@id": "http://www.opengis.net/def/docs/15-074r2" + }, + { + "@id": "http://www.opengis.net/def/docs/21-041r2" + }, + { + "@id": "http://www.opengis.net/def/docs/10-191r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-018" + }, + { + "@id": "http://www.opengis.net/def/docs/04-071" + }, + { + "@id": "http://www.opengis.net/def/docs/05-111r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-010" + }, + { + "@id": "http://www.opengis.net/def/docs/05-017" + }, + { + "@id": "http://www.opengis.net/def/docs/05-101" + }, + { + "@id": "http://www.opengis.net/def/docs/15-116" + }, + { + "@id": "http://www.opengis.net/def/docs/05-014" + }, + { + "@id": "http://www.opengis.net/def/docs/08-009r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-154" + }, + { + "@id": "http://www.opengis.net/def/docs/16-145" + }, + { + "@id": "http://www.opengis.net/def/docs/11-039r3" + }, + { + "@id": "http://www.opengis.net/def/docs/06-107r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-129" + }, + { + "@id": "http://www.opengis.net/def/docs/04-052" + }, + { + "@id": "http://www.opengis.net/def/docs/09-163r2" + }, + { + "@id": "http://www.opengis.net/def/docs/23-022r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-012" + }, + { + "@id": "http://www.opengis.net/def/docs/03-029" + }, + { + "@id": "http://www.opengis.net/def/docs/04-060r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-122" + }, + { + "@id": "http://www.opengis.net/def/docs/08-077" + }, + { + "@id": "http://www.opengis.net/def/docs/09-123" + }, + { + "@id": "http://www.opengis.net/def/docs/20-092" + }, + { + "@id": "http://www.opengis.net/def/docs/16-114r2" + }, + { + "@id": "http://www.opengis.net/def/docs/16-012r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-124r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-037r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-163" + }, + { + "@id": "http://www.opengis.net/def/docs/04-050r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-166r2" + }, + { + "@id": "http://www.opengis.net/def/docs/07-124r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-084r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-158" + }, + { + "@id": "http://www.opengis.net/def/docs/11-058r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-195" + }, + { + "@id": "http://www.opengis.net/def/docs/08-076" + }, + { + "@id": "http://www.opengis.net/def/docs/04-100" + }, + { + "@id": "http://www.opengis.net/def/docs/08-000" + }, + { + "@id": "http://www.opengis.net/def/docs/06-079r1" + }, + { + "@id": "http://www.opengis.net/def/docs/14-121r2" + }, + { + "@id": "http://www.opengis.net/def/docs/06-173r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-031r2" + }, + { + "@id": "http://www.opengis.net/def/docs/19-047" + }, + { + "@id": "http://www.opengis.net/def/docs/23-040" + }, + { + "@id": "http://www.opengis.net/def/docs/07-009r3" + }, + { + "@id": "http://www.opengis.net/def/docs/12-028r1" + }, + { + "@id": "http://www.opengis.net/def/docs/03-028" + }, + { + "@id": "http://www.opengis.net/def/docs/09-018" + }, + { + "@id": "http://www.opengis.net/def/docs/16-079" + }, + { + "@id": "http://www.opengis.net/def/docs/09-082" + }, + { + "@id": "http://www.opengis.net/def/docs/20-054r1" + }, + { + "@id": "http://www.opengis.net/def/docs/20-000r1" + }, + { + "@id": "http://www.opengis.net/def/docs/18-077r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-104r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-184r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-076r3" + }, + { + "@id": "http://www.opengis.net/def/docs/23-013" + }, + { + "@id": "http://www.opengis.net/def/docs/15-096" + }, + { + "@id": "http://www.opengis.net/def/docs/08-132" + }, + { + "@id": "http://www.opengis.net/def/docs/12-117r1" + }, + { + "@id": "http://www.opengis.net/def/docs/15-074" + }, + { + "@id": "http://www.opengis.net/def/docs/13-021r3" + }, + { + "@id": "http://www.opengis.net/def/docs/23-056" + }, + { + "@id": "http://www.opengis.net/def/docs/05-050" + }, + { + "@id": "http://www.opengis.net/def/docs/01-061" + }, + { + "@id": "http://www.opengis.net/def/docs/07-004" + }, + { + "@id": "http://www.opengis.net/def/docs/06-187r1" + }, + { + "@id": "http://www.opengis.net/def/docs/04-010r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-152" + }, + { + "@id": "http://www.opengis.net/def/docs/07-172r1" + }, + { + "@id": "http://www.opengis.net/def/docs/15-039" + }, + { + "@id": "http://www.opengis.net/def/docs/01-019" + }, + { + "@id": "http://www.opengis.net/def/docs/07-055r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-112r1" + }, + { + "@id": "http://www.opengis.net/def/docs/19-042r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-125" + }, + { + "@id": "http://www.opengis.net/def/docs/07-166r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-029" + }, + { + "@id": "http://www.opengis.net/def/docs/05-116" + }, + { + "@id": "http://www.opengis.net/def/docs/07-027r1" + }, + { + "@id": "http://www.opengis.net/def/docs/15-122r1" + }, + { + "@id": "http://www.opengis.net/def/docs/04-051" + }, + { + "@id": "http://www.opengis.net/def/docs/24-025" + }, + { + "@id": "http://www.opengis.net/def/docs/05-015" + }, + { + "@id": "http://www.opengis.net/def/docs/21-010r2" + }, + { + "@id": "http://www.opengis.net/def/docs/13-099" + }, + { + "@id": "http://www.opengis.net/def/docs/18-056" + }, + { + "@id": "http://www.opengis.net/def/docs/19-091r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-002" + }, + { + "@id": "http://www.opengis.net/def/docs/08-078r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-022r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-084r1" + }, + { + "@id": "http://www.opengis.net/def/docs/21-037" + }, + { + "@id": "http://www.opengis.net/def/docs/07-032" + }, + { + "@id": "http://www.opengis.net/def/docs/09-085r2" + }, + { + "@id": "http://www.opengis.net/def/docs/10-196r1" + }, + { + "@id": "http://www.opengis.net/def/docs/19-077" + }, + { + "@id": "http://www.opengis.net/def/docs/04-011r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-002r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-132r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-118" + }, + { + "@id": "http://www.opengis.net/def/docs/07-001r3" + }, + { + "@id": "http://www.opengis.net/def/docs/08-133" + }, + { + "@id": "http://www.opengis.net/def/docs/15-075r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-140" + }, + { + "@id": "http://www.opengis.net/def/docs/09-042" + }, + { + "@id": "http://www.opengis.net/def/docs/05-115" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type Implementation Specification - deprecated " + "@value": "Documents of type Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-086", + "@id": "http://www.opengis.net/def/docs/16-005r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-11-21" + "@value": "2017-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mike Botts" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -23075,27 +22554,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12606" + "@id": "https://portal.ogc.org/files/?artifact_id=72713" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-086" + "@value": "Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes" }, { "@language": "en", - "@value": "Sensor Model Language (SensorML)" + "@value": "16-005r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The general models and XML encodings for sensors. " + "@value": "This document provides the Annexes for the CDB Core: Model and Physical Structure standard. The only exception is Annex A, Abstract Test Suite. The CDB ATS Annex is in Volume 1: Core document." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -23106,35 +22585,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-086" + "@value": "16-005r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Sensor Model Language (SensorML)" + "@value": "Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-118r1", + "@id": "http://www.opengis.net/def/docs/22-010r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-04-23" + "@value": "2024-04-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Jirka, Christoph Stasch" + "@value": "Chris Crook" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -23144,27 +22623,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/15-118r1.html" + "@id": "https://docs.ogc.org/as/22-010r4/22-010r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Incident Management Information Sharing Profile Recommendations for OGC Web Services Engineering Report" + "@value": "Topic 24 - Functional Model for Crustal Deformation" }, { "@language": "en", - "@value": "15-118r1" + "@value": "22-010r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives:\r\n\r\n• Apply OGC principles and practices for collaborative development to existing standards and technology to prototype an IoT approach to sensor use for incident management;\r\n\r\n• Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability;\r\n\r\n• Develop profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability; and\r\n\r\n• Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario.\r\n\r\nBased on the findings gathered during the implementation and work on these objectives, this Engineering Report describes recommendations on profiles for OGC Web services that shall be used to build IMIS systems." + "@value": "This OGC Abstract Specification (AS) defines a general parameterization of surface deformation models.\r\n\r\nAll objects on the surface of the Earth are moving. Apparently fixed features such as buildings are moving with the Earth’s crust, being subject to ongoing plate tectonic movement and episodic deformation events such as earthquakes.\r\n\r\nIncreasingly, applications and users rely on global positioning methods, such as Global Navigation Satellite Systems (GNSS) observations, to precisely determine the coordinates of features. The resulting coordinates are then stored in databases and used in a wide range of applications, such as Geographic Information Systems (GIS). However, the coordinates from GNSS are referenced to global reference frames and coordinate reference systems (CRSs). In these reference frames the coordinates of apparently fixed objects are continually changing.\r\n\r\nThis creates a challenge for the geospatial and positioning community: How to account for this movement when comparing data sets observed at different times, or how to locate an object observed in the past.\r\n\r\nThis problem is generally addressed in one of two ways:\r\n\r\nDefining a reference epoch for the CRS of coordinates held in the GIS, often by defining a CRS with a reference epoch, or\r\nUsing a CRS which is fixed relative to the surface of the Earth.\r\nIn practice there is little difference between these two approaches. Neither the position at a reference epoch, nor the coordinates in a static CRS, can be directly measured by global positioning methods.\r\n\r\nPropagating the observed coordinates to a reference epoch, or transforming to a static CRS, requires a deformation model — a mathematical model of the deformation of the Earth’s surface.\r\n\r\nCommon uses of a deformation model include:\r\n\r\nDetermining the current location of an object based on historic measurement of its location,\r\nPropagation of the current observed location of an object to the reference epoch of a static CRS,\r\nDetermining the spatial relationship of data sets observed at different times, and\r\nPredicting the location of an object at some future time.\r\nCurrently, many national geodetic agencies have developed or are planning to develop regional deformation models. However, the current models generally use customized formats and software developed by each agency.\r\n\r\nThis AS describes a way of parameterizing a deformation model such that it can be encoded into a data set and used in software for coordinate operations. The AS defines how to calculate the displacement of a point between two different epochs. It provides a common understanding between producers of deformation models and developers of software about what the deformation is and how it will be used.\r\n\r\nThis AS will allow users of compliant software applying a compliant deformation model to be confident that the model is being used as intended by its producers." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -23175,30 +22654,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-118r1" + "@value": "22-010r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Incident Management Information Sharing Profile Recommendations for OGC Web Services Engineering Report" + "@value": "Topic 24 - Functional Model for Crustal Deformation" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-061", + "@id": "http://www.opengis.net/def/docs/23-048", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-30" + "@value": "2024-07-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Timo Thomas, Aleksandar Balaban" + "@value": "Matthias Mohr" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -23213,17 +22692,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-061.html" + "@id": "https://docs.ogc.org/per/23-048.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Aviation SBVR Engineering Report" + "@value": "23-048" }, { "@language": "en", - "@value": "16-061" + "@value": "OGC Testbed 19 Draft API - Geodatacubes specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -23233,7 +22712,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report (ER) is a deliverable of the OGC Testbed 12. It advances previous work in the area of business rules for AIXM 5 based on SBVR. It evaluates the use of geo-spatial operators and constraints in SBVR, including a proof of concept for their automatic interpretation by software. It gives guidelines on how to deal with temporality aspects and how to extend the applicability of SBVR towards filtering expressions and it identifies limitations of the currently available vocabulary." + "@value": "This OGC Testbed 19 Engineering Report documents a draft OGC API — GeoDataCube Standard (aka GDC API). The OGC Member participants in this Testbed 19 activity developed, documented, and tested the draft OGC GDC API Standard. The draft will be submitted to the OGC GeoDataCube Standards Working Group (SWG) as a new standards work item.\r\n\r\nThe OGC GeoDataCube SWG was chartered to respond to the long-standing issue of establishing a standard that supports accessing and processing geospatial datacubes in an interoperable way. The draft OGC API — GeoDataCube that was developed in OGC Testbed 19 responds to this need and proposes a draft API specification.\r\n\r\nThe Testbed 19 GDC initiative targeted enhanced interoperability. The draft GDC API Standard was based on OGC API — Common, OGC API — Coverages Standard, OGC API — Processes Standard, the STAC API, and the openEO API. The Testbed 19 participants concentrated on server and client application development, and usability testing based on conformance classes and use cases. The draft GDC API is defined as an OpenAPI 3.0 document and provides endpoints for capabilities, data discovery/access, process discovery, and data processing. Notably, the draft GDI API Standard is extensible through additional implementations of OGC API Standards or openEO API parts. Documentation is available in machine-readable YAML and human-friendly HTML through a GitHub repository." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -23244,35 +22723,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-061" + "@value": "23-048" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Aviation SBVR Engineering Report" + "@value": "OGC Testbed 19 Draft API - Geodatacubes specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-107", + "@id": "http://www.opengis.net/def/docs/19-012r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-10-15" + "@value": "2019-12-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "Benjamin Pross" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -23282,27 +22761,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7467" + "@id": "https://docs.ogc.org/per/19-012r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 07 - Earth Imagery" + "@value": "OGC Testbed-15: Delta Updates Engineering Report" }, { "@language": "en", - "@value": "04-107" + "@value": "19-012r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Replaced previous material in Topic 7 with ISO 19101-2, Reference Model - Geographic Information - Imagery. Version 5 of OGC Topic 7 is identical with ISO 19101-2 Working Draft #3. Topic 7 will be updated jointly with the progress of ISO 19191-2. Appendix A of Topic 7, version 4 contained a White Paper on Earth Image Geometry Models. That white paper is now separate OGC Recommendation document. " + "@value": "This OGC Testbed 15 Engineering Report (ER) documents the design of a service architecture that allows the delivery of prioritized updates of features to a client, possibly acting in a DDIL (Denied, Degraded, Intermitted or Limited Bandwidth) environment. Two different technical scenarios were investigated and tested:\r\n\r\nThe enhancement of Web Feature Service (WFS) instances to support updates on features sets.\r\n\r\nUtilizing a Web Processing Service (WPS) instance to access features, without the need to modify the downstream data service." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -23313,35 +22792,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-107" + "@value": "19-012r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 7 - Earth Imagery" + "@value": "OGC Testbed-15: Delta Updates Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-026r1", + "@id": "http://www.opengis.net/def/docs/23-020r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-04-22" + "@value": "2024-01-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mike Botts" + "@value": "Guy Schumann, Albert Kettner, Nils Hempelmann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -23351,27 +22830,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1133" + "@id": "https://docs.ogc.org/per/23-020r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "SensorML" + "@value": "Engineering report for OGC Climate Resilience Pilot" }, { "@language": "en", - "@value": "02-026r1" + "@value": "23-020r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances." + "@value": "The OGC Climate Resilience Pilot marked the beginning of a series of enduring climate initiatives with the primary goal of evaluating the value chain encompassing raw data to climate information processes within Climate Resilience Information Systems. This includes the transformation of geospatial data into meaningful knowledge for various stakeholders, including decision-makers, scientists, policymakers, data providers, software developers, service providers, and emergency managers. The results of the OGC Climate Resilience Pilot support the location community to develop more powerful visualization and communication tools to accurately address ongoing climate threats such as heat, drought, floods, and wild-fires as well as supporting governments in meeting commitments for their climate strategies. This will be accomplished through evolving geospatial data, technologies, and other capabilities into valuable information for decision-makers, scientists, policymakers, data providers, software developers, and service providers so they can make valuable, informed decisions to improve climate action. One of the most significant challenges so far has been converting the outputs of global and regional climate models into specific impacts and risks at the local level. The climate science community has adopted standards and there are now numerous climate resilience information systems available online, allowing experts to exchange and compare data effectively. However, professionals outside the weather and climate domain, such as planners and GIS analysts working for agencies dealing with climate change impacts, have limited familiarity with and capacity to utilize climate data.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -23382,30 +22861,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-026r1" + "@value": "23-020r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "SensorML" + "@value": "Engineering report for OGC Climate Resilience Pilot" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-045r2", + "@id": "http://www.opengis.net/def/docs/21-021", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-30" + "@value": "2022-01-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Daniel Balog, Robin Houtmeyers" + "@value": "Alan Leidner, Mark Reichardt, Josh Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -23420,17 +22899,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-045r2.html" + "@id": "https://docs.ogc.org/per/21-021.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Data Broker Engineering Report" + "@value": "Health Spatial Data Infrastructure Concept Development Study Engineering Report" }, { "@language": "en", - "@value": "16-045r2" + "@value": "21-021" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -23440,7 +22919,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "An important principle of a Service Oriented Architecture (SOA) is the notion of composing capabilities provided by individual services into complex behavior. A requester should be able to compose a solution using functionality or data offered by multiple services without worrying about underlying differences in those services.\r\n\r\nEach OGC service is designed to offer a specific type of data product via a service-specific interface. This Engineering Report (ER) describes a single service interface that allows access to multiple data sources, possibly heterogeneous with respect to the types of data provided.\r\n\r\nThis report advances the work started in OGC Testbed 11 with the addition of heterogeneous data sources, as well as several other enhancements." + "@value": "Experts agree that access to, sharing, and application of location-enabled information is a key component in addressing health related emergencies. While the present COVID-19 pandemic has underscored a range of successes in dealing with the COVID virus, many gaps in supporting local to global preparedness, forecasting, monitoring, and response have been identified when dealing with a health crisis at such an unprecedented level. This study considers how a common, standardized health geospatial data model, schema, and corresponding spatial data infrastructure (SDI) could establish a blueprint to better align the community for early warning, response to, and recovery from future health emergencies. Such a data model would help to improve support for critical functions and use cases." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -23451,35 +22930,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-045r2" + "@value": "21-021" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Data Broker Engineering Report" + "@value": "Health Spatial Data Infrastructure Concept Development Study Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-016", + "@id": "http://www.opengis.net/def/docs/06-024r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-15" + "@value": "2008-09-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arne Bröring;Simon Jirka;Matthes Rieke, Benjamin Pross" + "@value": "CS Smyth" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -23489,27 +22968,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=58925" + "@id": "https://portal.ogc.org/files/?artifact_id=25487" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-016" + "@value": "Location Services: Tracking Service Interface Standard" }, { "@language": "en", - "@value": "Testbed-10 CCI VGI Engineering Report" + "@value": "06-024r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report was created as a deliverable for the OGC Testbed 10 (Testbed-\r\n10) initiative of the OGC Interoperability Program. This report describes an approach for\r\nintegrating Volunteered Geographic Information (VGI) into a spatial data infrastructure\r\nand reports on findings about the advancements using VGI resources. It includes\r\noptimization ideas, service change recommendations, and lessons learned.\r\nThis is not a normative document." + "@value": "The OpenGIS Tracking Service Interface Standard supports a very simple functionality allowing a collection of movable objects to be tracked as they move and change orientation. The standard addresses the absolute minimum in functionality in order to address the need for a simple, robust, and easy-to-implement open standard for geospatial tracking." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -23520,35 +22999,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-016" + "@value": "06-024r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed-10 CCI VGI Engineering Report" + "@value": "OGC Location Services (OpenLS): Tracking Service Interface Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-037", + "@id": "http://www.opengis.net/def/docs/10-192", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-07-02" + "@value": "2011-01-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Josh Lieberman" + "@value": "Jeff Harrison" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -23558,27 +23037,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/21-037.html" + "@id": "https://portal.ogc.org/files/?artifact_id=41734" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-037" + "@value": "Authentication IE Enginerring Report " }, { "@language": "en", - "@value": "OGC Technical Paper on the Standards Landscape for Building Data" + "@value": "10-192" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Data about buildings and building structures play roles at scales from neighborhoods to nations in creating, protecting, regulating, and understanding the built environment. This report examines standards which may be useful in defining the structure and content of building data at a national scale, a national building layer. Standard models, schemas, and encodings may be especially useful for supporting an extensible building dataset with an efficient core definition, but the ability to encompass more detailed or specialized data as needed in as seamless and compatible a manner as possible. Standards compiled and described in this document range from generic geographic data encodings to models and specifications for specific building perspectives such as land parcel improvements, facility ownership, footprint / roofline extractions, residency affordances, envelope characteristics, and so on. They provide potential source material for a modular and multi-platform building layer definition which can be applied to a reasonably wide set of use cases. This definition may in turn be a standardization candidate for adoption by other national geographic data collections." + "@value": "Results of the Auth IE are presented in this Engineering Report document and serve as guidance to both implementers and organizations deploying solutions that involve basic authentication. It is the belief of the Auth IE participants that if such a document is made available to the community more OGC implementing products will natively support authentication. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -23589,100 +23068,99 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-037" + "@value": "10-192" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Technical Paper on the Standards Landscape for Building Data" + "@value": "Authentication IE Enginerring Report " } ] }, { - "@id": "http://www.opengis.net/def/doc-type/cs/collection", + "@id": "http://www.opengis.net/def/docs/10-100r2", "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" + "http://www.w3.org/2004/02/skos/core#Concept" ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "http://purl.org/dc/terms/created": [ { - "@value": "Documents of type Candidate Specification" + "@type": "xsd:date", + "@value": "2010-10-07" } ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "http://purl.org/dc/terms/creator": [ { - "@value": "Documents of type Candidate Specification" + "@value": "Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos" } ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs" + "@id": "http://www.opengis.net/def/doc-type/d-profile" } ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/17-014r8" - }, - { - "@id": "http://www.opengis.net/def/docs/21-069r2" - }, - { - "@id": "http://www.opengis.net/def/docs/17-014r7" - }, - { - "@id": "http://www.opengis.net/def/docs/17-014r5" - }, - { - "@id": "http://www.opengis.net/def/docs/17-002r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-030r1" - }, + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/18-053r2" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/22-025r4" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=39853" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/20-072r5" + "@language": "en", + "@value": "10-100r2" }, { - "@id": "http://www.opengis.net/def/docs/20-094" - }, + "@language": "en", + "@value": "Geography Markup Language (GML) simple features profile" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/21-050r1" - }, + "@id": "http://www.opengis.net/def/doc-type/d-profile" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/19-065" - }, + "@value": "This approved OpenGIS® Implementation Standard defines a Simple Features profile of the Geography Markup Language version 3.2. This Simple Features Profile has been aligned with the OGC Simple Features standard for SQL version 1.2. Simple Features include: Point, Curve (LineString), Surface (Polygon), Geometry, MultiPoint, MultiCurve, MultiSurface, and MultiGeometry. The detailed abstract model for OGC features and geometry can be found in the OGC Abstract Specification, Topic Volume 1: Features (which is equivalent to ISO 19107)." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/17-014r9" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/20-072r2" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "10-100r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type Candidate Specification" + "@language": "en", + "@value": "Geography Markup Language (GML) simple features profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-057r2", + "@id": "http://www.opengis.net/def/docs/17-078", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-11-18" + "@value": "2018-01-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthes Rieke, Simon Jirka, Stephane Fellah" + "@value": "Jeff Harrison" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -23697,17 +23175,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64353" + "@id": "https://docs.ogc.org/per/17-078.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-057r2" + "@value": "17-078" }, { "@language": "en", - "@value": "Testbed-11 Incorporating Social Media in Emergency Response Engineering Report" + "@value": "Concepts of Data and Standards for Mass Migration Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -23717,7 +23195,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) was created as a deliverable for the OGC Testbed 11 initiative of the OGC Interoperability Program. This ER describes an approach for incorporating Social Media for Emergency Response applications that use spatial data infrastructures. This document also reports on findings about the advancements using Social Media and VGI resources. The ER includes ideas on improving the architecture, service change recommendations (primarily concerning the OGC Sensor Observation Service (SOS) 2.0 interface), and lessons learned." + "@value": "The objective of the Mass Migration Source Integration effort in OGC Testbed 13 was to understand and document how interoperability tools and practices, including open geospatial and security standards, can enable information exchange on an international level for humanitarian relief and analysis of mass movement of populations.\r\n\r\nThis Engineering Report describes how Testbed 13 participants tested and demonstrated situational awareness using Internet and web technologies in a shared information exchange platform. The purpose of this platform was to help realize a Common Operational Picture (COP) for coordinating humanitarian relief activities among nations and organizations. In addition, the platform exercised security-enabled interoperable exchange of messages.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -23728,35 +23206,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-057r2" + "@value": "17-078" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed-11 Incorporating Social Media in Emergency Response Engineering Report" + "@value": "OGC Testbed-13: Concepts of Data and Standards for Mass Migration Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-035", + "@id": "http://www.opengis.net/def/docs/08-059r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-08" + "@value": "2009-03-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Charles Chen" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -23766,27 +23244,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-035.html" + "@id": "https://portal.ogc.org/files/?artifact_id=32416" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-13: Cloud ER" + "@value": "Web Coverage Service (WCS) - Processing Extension (WCPS)" }, { "@language": "en", - "@value": "17-035" + "@value": "08-059r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) will describe the use of OGC Web Processing Service (WPS) for cloud architecture in the OGC Testbed 13 Earth Observation Cloud (EOC) Thread. This report is intended to address issues in lack of interoperability and portability of cloud computing architectures which cause difficulty in managing the efficient use of virtual infrastructure such as in cloud migration, storage transference, quantifying resource metrics, and unified billing and invoicing. This engineering report will describe the current state of affairs in cloud computing architectures and describe the participant architectures based on use case scenarios from sponsor organizations.\r\n\r\nCloud computing is paving the way for future scalable computing infrastructures and is being used for processing digital earth observation data. In this EOC thread effort, data is stored in various storage resources in the cloud and accessed by an OGC Web Processing Service. The methods in which these processes are deployed and managed must be made interoperable to mitigate or avoid the complexities of administrative effort for the scientific community. In other words, the intent of this effort is to develop a way for scientists to acquire, process, and consume earth observation data without needing to administer computing cloud resources." + "@value": "The OpenGIS® Web Coverage Service Interface Standard (WCS) defines a protocol-independent language for the extraction, processing, and analysis of multi-dimensional gridded [[http://www.opengeospatial.org/ogc/glossary/c | coverages]] representing sensor, image, or statistics data. Services implementing this language provide access to original or derived sets of geospatial coverage information, in forms that are useful for client-side rendering, input into scientific models, and other client applications.\r\n\r\nFurther information about WPCS can be found at the [[http://www.ogcnetwork.net/wcps | WCPS Service]] page of the OGC Network." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -23797,30 +23275,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-035" + "@value": "08-059r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: Cloud ER" + "@value": "OpenGIS Web Coverage Service (WCS) - Processing Extension (WCPS)" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-055", + "@id": "http://www.opengis.net/def/docs/23-027", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-11-29" + "@value": "2024-04-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Joana Simoes" + "@value": "Glenn Laughlin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -23835,17 +23313,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-055.html" + "@id": "https://docs.ogc.org/per/23-027.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "July 2021 OGC API Code Sprint Summary Engineering Report" + "@value": "23-027" }, { "@language": "en", - "@value": "21-055" + "@value": "OGC Federated Marine Spatial Data Infrastructure Pilot 2023 - Connecting Land and Sea for Global Awareness" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -23855,7 +23333,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The subject of this Engineering Report (ER) is a virtual code sprint that was held from July 21st to July 23rd, 2021 to advance the development of the OGC API - Processes draft standard, OGC API - Records draft standard, and the OGC API – Coverages draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016)." + "@value": "Rising sea levels together with increasing storm surges are amongst the most challenging issues for coastal communities in the context of global warming. The retreating ice sheets of the Circumpolar Arctic are a key contributor to sea level rise with consequences felt around the world.\r\n\r\nThe Federated Marine Spatial Data Infrastructure (FMSDI) initiative is a key component of OGC and the Marine Domain Working Group. The program is designed to engage with stakeholders from the marine dataspace to identify opportunities to assist, improve, and scale out core business processes complemented by the OGC suite of standards and best practices. The FMSDI-2023 pilot represents the fourth phase of the program with a focus on the interface between land and sea. A primary goal of this pilot is to advance the FMSDI concept to increasing threats posed by climate change.\r\n\r\nThe project is divided into three threads, each with application to distinct geographies.\r\n\r\nThread 1: Digital Twin of Land and Sea Interfaces — Singapore\r\nWith approximately 30% of Singapore’s land mass being less than 5m above sea level, the seamless integration of land and marine data is integral to Singapore’s focus on coastal protection and climate resilience. The management of land and water is separated organizationally between the Singapore Land Authority (SLA) and the Maritime & Port Authority (MPA), respectively. Each agency is responsible for data assets specific to their jurisdiction presenting a challenge for cross-organizational concerns. This theme addresses the geospatial integration requirements through the development of a multi-dimensional Digital Twin of the Singapore coastline.\r\n\r\nThread 2: Digital Arctic Connecting Land and Sea — Canada\r\nThis thread addresses the data integration issues in the context of Digital Twins for the Canadian Arctic. With the loss of sea ice, continuing ocean warming, stronger winds and currents, and accelerated shoreline erosion affecting Arctic communities, efficient data usage and analysis is of the utmost importance for Canada.\r\nFigure 1\r\n\r\nThread 3: Integrating Land & Sea for Various Use Cases — Caribbean\r\nThis thread investigates how data developed primarily for navigation at sea can be used to better understand the opportunities in the Caribbean to support local capacity building and the application of marine data in expanded sea-land contexts.\r\n\r\nApproach\r\n\r\nThe FMSDI 2023 pilot is managed through the OGC Collaborative Solutions and Innovation (COSI) Program. Each thread is a distinct project with a set of participants tackling specific use cases and scenarios important to the respective project sponsor.\r\n\r\nWeekly project meetings are scheduled to encourage collaboration between the participants and sponsors and provide checkpoints to ensure the project scope meets the sponsor’s expectations.\r\n\r\nThe FMSDI 2023 pilot also features a series of persistent demonstrators as one of its outputs. These demonstrators are workflows and applications that stakeholders can access for outreach, testing, and experimentation purposes. The demonstrators will be available even after the project is completed and are therefore referenced as persistent, but will only be available until December 2024. These demonstrators showcase how geospatial data can be used in an operational context or highlight the gaps in the resources available online, including data sources, metadata, access processes, and standards. As each participant has a unique solution platform, each has taken different approaches, all of which are available for review by stakeholders. Security concerns, such as authentication and authorization, are unique to each participant and have been communicated to stakeholders and participant contacts. For further details and access to the demonstrators, please refer to the link provided.\r\n\r\nCommon across the three threads is the application of the OGC FAIR principles — Findable, Accessible, Interoperable, and Reusable. Underpinning the use of the FAIR principles is the role of the core OGC Standards and Best Practices. Previous work products related to FMSDI form the core information model while the OGC standards, enhanced through the alignment and support of industry standards such as the IHO S-100 standard, address many of the requirements central to each thread.\r\n\r\nAttention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.\r\n\r\nRecipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which the recipients may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -23866,35 +23344,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-055" + "@value": "23-027" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "July 2021 OGC API Code Sprint Summary Engineering Report" + "@value": "OGC Federated Marine Spatial Data Infrastructure Pilot 2023 - Connecting Land and Sea for Global Awareness" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-046r2", + "@id": "http://www.opengis.net/def/docs/22-047r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-24" + "@value": "2024-01-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lew Leinenweber" + "@value": "Nicholas J. Car" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -23904,27 +23382,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55432" + "@id": "https://docs.ogc.org/is/22-047r1/22-047r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CHISP-1 Summary Engineering Report" + "@value": "OGC GeoSPARQL - A Geographic Query Language for RDF Data" }, { "@language": "en", - "@value": "13-046r2" + "@value": "22-047r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report summarizes the results of OGC’s Climatology-Hydrology Information Sharing Pilot, Phase 1 (CHISP-1). The objective of this initiative was to develop an inter-disciplinary, inter-agency and international virtual observatory system for water resources information from observations in the U.S. and Canada, building on current networks and capabilities.\r\nThe CHISP-1 Initiative was designed to support these Use Case functions:\r\n•\tHydrologic modeling for historical and current stream flow and groundwater conditions\r\n•\tModeling and assessment of nutrient load into the Great Lakes\r\n" + "@value": "GeoSPARQL contains a small spatial domain OWL ontology that allow literal representations of geometries to be associated with spatial features and for features to be associated with other features using spatial relations.\r\n\r\nGeoSPARQL also contains SPARQL extension function definitions that can be used to calculate relations between spatial objects.\r\n\r\nSeveral other supporting assets are also contained within GeoSPARQL such as vocabularies of Simple Feature types and data validators.\r\n\r\nThe namespace for the GeoSPARQL ontology is http://www.opengis.net/ont/geosparql#\r\n\r\nThe suggested prefix for this namespace is geo\r\n\r\nThe namespace for the GeoSPARQL functions is http://www.opengis.net/def/function/geosparql/\r\n\r\nThe suggested prefix for this namespace is geof\r\n\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -23935,35 +23413,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-046r2" + "@value": "22-047r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC CHISP-1 Summary Engineering Report" + "@value": "OGC GeoSPARQL - A Geographic Query Language for RDF Data" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-091", + "@id": "http://www.opengis.net/def/docs/04-049r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-02-09" + "@value": "2005-04-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Richard Martell" + "@value": "Philippe Duschene, Jerome Sonnet" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -23973,27 +23451,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46094" + "@id": "https://portal.ogc.org/files/?artifact_id=9540" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-8 Review of the WXXS exchange schemas" + "@value": "04-049r1" }, { "@language": "en", - "@value": "11-091" + "@value": "WCS Change Request: Support for WSDL & SOAP" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This aim of this review is to assess the the WXXS 1.1.1 exchange schemas for\r\ncompliance with ISO 19136:2007 (GML 3.2.1). This international standard stipulates\r\nrules and recommendations regarding the construction of GML application schemas;\r\nthese constraints are documented in the following clauses:\r\n(a) Clause 7.1: GML model and syntax\r\n(b) Clause 21: Rules for GML application schemas\r\n(c) Annex A.1: Abstract test suite for GML application schemas" + "@value": "The OpenGIS has been a precursor in Web Services matter, nevertheless, the pattern that has been used is not recognized by the industry as a standard XML Web Services. The work done during the the OpenGIS Web Service 2 initiative has provided the OpenGIS with interfaces that use the XML-related technologies supported by the industry, as SOAP for the communication protocol, WSDL for the interface description language, and UDDI for registering and searching services.\r\n\r\nThis change proposal present the required change to the WCS specification to interoperate with the industry standards.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24004,35 +23482,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-091" + "@value": "04-049r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 Review of the WXXS exchange schemas" + "@value": "WCS Change Request: Support for WSDL & SOAP" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-004", + "@id": "http://www.opengis.net/def/docs/17-035", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-01-12" + "@value": "2018-01-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Louis Burry" + "@value": "Charles Chen" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -24042,27 +23520,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=6628" + "@id": "https://docs.ogc.org/per/17-035.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "01-004" + "@value": "Testbed-13: Cloud ER" }, { "@language": "en", - "@value": "Grid Coverage Service Implementation Specification" + "@value": "17-035" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "**This document has been retired. It is not supported. You should consider using Web Coverage Service.**\r\n\r\n This specification was designed to promote interoperability between software implementations by data vendors and software vendors providing grid analysis and processing capabilities." + "@value": "This OGC Engineering Report (ER) will describe the use of OGC Web Processing Service (WPS) for cloud architecture in the OGC Testbed 13 Earth Observation Cloud (EOC) Thread. This report is intended to address issues in lack of interoperability and portability of cloud computing architectures which cause difficulty in managing the efficient use of virtual infrastructure such as in cloud migration, storage transference, quantifying resource metrics, and unified billing and invoicing. This engineering report will describe the current state of affairs in cloud computing architectures and describe the participant architectures based on use case scenarios from sponsor organizations.\r\n\r\nCloud computing is paving the way for future scalable computing infrastructures and is being used for processing digital earth observation data. In this EOC thread effort, data is stored in various storage resources in the cloud and accessed by an OGC Web Processing Service. The methods in which these processes are deployed and managed must be made interoperable to mitigate or avoid the complexities of administrative effort for the scientific community. In other words, the intent of this effort is to develop a way for scientists to acquire, process, and consume earth observation data without needing to administer computing cloud resources." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24073,35 +23551,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-004" + "@value": "17-035" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Grid Coverage Service Implementation Specification" + "@value": "OGC Testbed-13: Cloud ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-049", + "@id": "http://www.opengis.net/def/docs/22-040", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-03-02" + "@value": "2023-03-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "C. Mitchell, M. Gordon, T. Kralidis" + "@value": "David Blodgett, J. Michael Johnson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -24111,27 +23589,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=77148" + "@id": "https://docs.ogc.org/per/22-040.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-049" + "@value": "22-040" }, { "@language": "en", - "@value": "Ensuring Quality of User Experience with OGC Web Mapping Services - Discussion Paper" + "@value": "Hydrologic Modeling and River Corridor Applications of HY_Features Concepts" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This paper is intended to identify usability issues associated with use of OGC web\r\nmapping services that affect the quality of experience a user may have when accessing\r\nand using OGC web services and discuss potential solutions and guidance to address\r\nthese issues. Additionally, guidance on evaluating and self-assessing the Quality of\r\nExperience of Spatial Data Services will also be discussed and addressed with a proposal\r\nfor common assessment criteria and common practices for improving the user experience\r\nwhen viewing, layering or querying OGC web mapping services." + "@value": "Hydrologic geospatial data products contain geometries that represent features such as river segments and incremental catchments. The combination of these provides a 2D (XY) geospatial fabric (hydrofabic) that discretizes the landscape and flow network into hydrologically relevant features at a defined level of scale, resolution, or organization. Hydrofabrics have been created at the national and continental scale in many parts of the world. This engineering report presents progress on formalizing a hydrofabric for drainage basins that adheres to HY_Features concepts with a focus on the use of the concepts in modeling hydrologic processes. Furthermore, this report documents efforts to integrate river corridor data with the traditionally 2D hydrofabric representations. River corridors include the channel and adjacent land required to maintain or restore a dynamic geomorphic equilibrium." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24142,35 +23620,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-049" + "@value": "22-040" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Ensuring Quality of User Experience with OGC Web Mapping Services - Discussion Paper" + "@value": "Hydrologic Modeling and River Corridor Applications of HY_Features Concepts" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-167r1", + "@id": "http://www.opengis.net/def/docs/06-154", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-16" + "@value": "2007-08-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Patrick Maué" + "@value": "David S. Burggraf, Ron Lake, Darko Androsevic" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -24180,27 +23658,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34916" + "@id": "https://portal.ogc.org/files/?artifact_id=19580" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-167r1" + "@value": "06-154" }, { "@language": "en", - "@value": "Semantic annotations in OGC standards" + "@value": "WFS Temporal Investigation" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Annotation of Web Services or data compliant to OGC standards refers to the task of attaching meaningful descriptions to the service and the served geospatial data or processes. In this discussion paper we try to extend the expressiveness of such annotations by including more sophisticated (semantic) descriptions." + "@value": "The objective of the proposed temporal extensions to the WFS is to enable temporal/geospatial queries using the GML temporal types against GML dynamic features employing either the snapshot or time history model (time slices). " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24211,35 +23689,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-167r1" + "@value": "06-154" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Semantic annotations in OGC standards" + "@value": "OWS 4 WFS Temporal Investigation" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-007r2", + "@id": "http://www.opengis.net/def/docs/03-028", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-06-17" + "@value": "2003-01-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Schut" + "@value": "Josh Lieberman, Lou Reich, Peter Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -24249,27 +23727,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=10634" + "@id": "https://portal.ogc.org/files/?artifact_id=1317" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-007r2" + "@value": "OGC Web Services UDDI Experiment" }, { "@language": "en", - "@value": "Web Processing Service" + "@value": "03-028" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A Web Service Processing Service provides access to calculations or models which operate on spatially referenced data. The data required by the service can be available locally, or delivered across a network using data exchange standards such as Geography Markup Language (GML) or Geolinked Data Access Service (GDAS). The calculation can be as simple as subtracting one set of spatially referenced numbers from another (e.g. determining the difference in influenza cases between two different seasons), or as complicated as a global climate change model. \r\n \r\nThis specification is intended to provide a mechanism to identify the spatially-referenced data required by the calculation, initiate the calculation, and manage the output from the calculation so that it can be accessed by the client. The Web Processing Service is targeted at both vector and raster data based processing. \r\n" + "@value": "This document lists the design principles, requirements, and experimental results for future versions of a potential OGC - UDDI (Universal Discovery, Description, and Integration) profile of the OGC Catalog Implementation Specification. Specifically, it describes the usage scenarios, workplan, and experimental results for discovery of OGC services (including registries) through the UDDI interface using SOAP (Simple Object Access Protocol) messaging protocols. The baseline for this experiment is the specification for UDDI version 2 and use of private UDDI implementations. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24280,35 +23758,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-007r2" + "@value": "03-028" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Processing Service" + "@value": "OGC Web Services UDDI Experiment" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-011r5", + "@id": "http://www.opengis.net/def/docs/10-171", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2010-10-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Simon Jirka, Daniel Nüst" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -24318,27 +23796,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/16-011r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=40609" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-011r5" + "@value": "10-171" }, { "@language": "en", - "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance" + "@value": "Sensor Instance Registry Discussion Paper " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames.\r\n\r\n" + "@value": "This Discussion paper introduces the Sensor Instance Registry (SIR), a web service interface for managing the metadata and status information of sensors. Furthermore this service is capable of automatically harvesting sensor metadata, transforming the collected metadata sets into a data model compatible to OGC Catalogs and to push harvested metadata into OGC Catalog instances." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24349,35 +23827,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-011r5" + "@value": "10-171" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance" + "@value": "Sensor Instance Registry Discussion Paper " } ] }, { - "@id": "http://www.opengis.net/def/docs/16-006r5", + "@id": "http://www.opengis.net/def/docs/10-157r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2012-06-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Jerome Gasperi, Frédéric Houbie, Andrew Woolf, Steven Smolders" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -24387,27 +23865,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/16-006r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=47040" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-006r5" + "@value": "Earth Observation Metadata profile of Observations & Measurements" }, { "@language": "en", - "@value": "Volume 10: OGC CDB Implementation Guidance" + "@value": "10-157r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store.\r\n\r\n" + "@value": "This OGC Implementation Standard defines a profile of Observations and Measurements (ISO 19156) for describing Earth Observation products (EO products).\r\nAlthough this standard has been developed in the context of the Heterogeneous Mission Accessibility (HMA) project initiated by European Space Agency (ESA), the content is generic to Earth Observation product description. The metadata model described in this document is structured to follow the different types of products (Optical, Radar, …) which are not HMA specific.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24418,35 +23896,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-006r5" + "@value": "10-157r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 10: OGC CDB Implementation Guidance" + "@value": "Earth Observation Metadata profile of Observations & Measurements" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-025r1", + "@id": "http://www.opengis.net/def/docs/11-063r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-03-22" + "@value": "2011-11-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Gobe Hobona, Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -24456,27 +23934,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41510" + "@id": "https://portal.ogc.org/files/?artifact_id=46342" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-025r1" + "@value": "OWS-8 Cross Community Interoperability (CCI) Semantic Mediation Engineering Report" }, { "@language": "en", - "@value": "Observations and Measurements - XML Implementation" + "@value": "11-063r6" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard specifies an XML implementation for the OGC and ISO Observations and Measurements (O&M) conceptual model (OGC Observations and Measurements v2.0 also published as ISO/DIS 19156), including a schema for Sampling Features. This encoding is an essential dependency for the OGC Sensor Observation Service (SOS) Interface Standard.\r\nMore specifically, this standard defines XML schemas for observations, and for features involved in sampling when making observations. These provide document models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities." + "@value": "The OWS-8 Cross Community Interoperability (CCI) thread built on progress made in the recent OWS-7 initiative to cover key technology areas that could not be addressed within the scope of that initiative. The OWS-8 CCI thread aimed to increase interoperability within communities sharing geospatial data, including advancing of interoperability among heterogeneous data models, advancing strategies to share styles to provide a more common and automated use of symbology, improvement of KML, and advancing schema automation allowing communities to better share their information artefacts. This OGC engineering report aims to present findings from CCI thread activities towards advancement of semantic mediation involving data retrieved from heterogeneous data models that are available through web services conformant to OGC standards. \r\nThe engineering report will briefly introduce relevant details of the semantic web and mediation. The document will make recommendations on establishing a semantic mediation architecture that uses OGC web services and emerging practice from the semantic web community. Based on the scenario adopted by the CCI thread, the document will also discuss the pros and cons of adopting relevant standards. The engineering report will offer recommendations on how specific OGC standards may be adopted or modified in order to support semantic mediation.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24487,30 +23965,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-025r1" + "@value": "11-063r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Observations and Measurements - XML Implementation" + "@value": "OWS-8 Cross Community Interoperability (CCI) Semantic Mediation Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-030r1", + "@id": "http://www.opengis.net/def/docs/14-111r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-01-19" + "@value": "2018-01-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Kuan-Mei Chen, Carl Reed" + "@value": "David Blodgett, Irina Dornblut" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -24525,17 +24003,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=44146" + "@id": "https://docs.ogc.org/is/14-111r6/14-111r6.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-030r1" + "@value": "14-111r6" }, { "@language": "en", - "@value": "Open GeoSMS Standard - Core" + "@value": "WaterML 2: Part 3 - Surface Hydrology Features (HY_Features) - Conceptual Model" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -24545,7 +24023,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Open GeoSMS standard defines an encoding for location enabling a text message to be communicated using a Short Messages System (SMS). " + "@value": "The OGC Surface Hydrology Features (HY_Features) standard defines a common conceptual information model for identification of specific hydrologic features independent of their geometric representation and scale. The model describes types of surface hydrologic features by defining fundamental relationships among various components of the hydrosphere. This includes relationships such as hierarchies of catchments, segmentation of rivers and lakes, and the hydrologically determined topological connectivity of features such as catchments and waterbodies. The standard also defines normative requirements for HY_Features implementation schemas and mappings to meet in order to be conformant with the conceptual model.\r\n\r\nThe HY_Features model is based on an abstract catchment feature type that can have multiple alternate hydrology-specific realizations and geometric representations. It supports referencing information about a hydrologic feature across disparate information systems or products to help improve data integration within and among organizations. The model can be applied to cataloging of observations, model results, or other study information involving hydrologic features. The ability to represent the same catchment, river, or other hydrologic feature in several ways is critical for aggregation of cross-referenced or related features into integrated data sets and data products on global, regional, or basin scales." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24556,35 +24034,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-030r1" + "@value": "14-111r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC®: Open GeoSMS Standard - Core" + "@value": "OGC® WaterML 2: Part 3 - Surface Hydrology Features (HY_Features) - Conceptual Model" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-088r1", + "@id": "http://www.opengis.net/def/docs/06-002r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-01-18" + "@value": "2006-08-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arthur Na, Mark Priest" + "@value": "Joshua Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -24594,27 +24072,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12846" + "@id": "https://portal.ogc.org/files/?artifact_id=15198" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-088r1" + "@value": "Geospatial Semantic Web Interoperabiltiy Experiment Report" }, { "@language": "en", - "@value": "Sensor Observation Service" + "@value": "06-002r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A Sensor Observation Service provides an API for managing deployed sensors and retrieving sensor data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today. " + "@value": "The Semantic Web seeks to make the meaning as accessible as the material, by enabling connections - which are both logical and (machine) actionable - between concepts which a user presently understands and those which may be new and foreign. The Geospatial Semantic Web extends this capability to both content and concepts that are specifically spatial, temporal, and geographic in nature, giving both people and machines true access to a wider range of knowledge." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24625,35 +24103,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-088r1" + "@value": "06-002r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Observation Service" + "@value": "Geospatial Semantic Web Interoperabiltiy Experiment Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-041", + "@id": "http://www.opengis.net/def/docs/18-088", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-13" + "@value": "2021-08-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Maso" + "@value": "Steve Liang, Tania Khalafbeigi, Hylke van der Schaaf" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -24663,27 +24141,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-041.html" + "@id": "https://docs.ogc.org/is/18-088/18-088.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Analysis Ready Data Engineering Report" + "@value": "SensorThings API Part 1: Sensing" }, { "@language": "en", - "@value": "20-041" + "@value": "18-088" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Committee on Earth Observation Satellites (CEOS) defines Analysis Ready Data (ARD) for Land (CARD4L) as satellite data that have been processed to a minimum set of requirements and organized into a form that allows immediate analysis with a minimum of additional user effort and interoperability both through time and with other datasets.\r\n\r\nThis OGC Testbed 16 Engineering Report (ER) generalizes the ARD concept and studies its implications for the OGC Standards baseline. In particular, the ER analyses how modern federated data processing architectures applying data cubes and Docker packages can take advantage of the existence of ARD. Architectures for ARD should minimize data transmission and allow and favor code transmission and remote execution. This ER also considers a workflow in which new processes are triggered as soon as new data becomes available. This is part of the event driven discussion." + "@value": "The OGC SensorThings API provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the web. At a high level the OGC SensorThings API provides two main functionalities and each function is handled by a part. The two parts are the Sensing part and the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. This document is version 1.1 and it is extending the first version of Sensing part." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24694,35 +24172,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-041" + "@value": "18-088" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: Analysis Ready Data Engineering Report" + "@value": "OGC SensorThings API Part 1: Sensing Version 1.1" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-021", + "@id": "http://www.opengis.net/def/docs/12-128r15", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-12-17" + "@value": "2018-09-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Esther Kok, Stephane Fellah" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -24732,27 +24210,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-021.html" + "@id": "https://portal.ogc.org/files/?artifact_id=80678" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-021" + "@value": "OGC® GeoPackage Encoding Standard - with Corrigendum" }, { "@language": "en", - "@value": "OGC Testbed-15: Semantic Web Link Builder and Triple Generator" + "@value": "12-128r15" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 15 Engineering Report (ER) describes a generalized approach towards performing data fusion from multiple heterogeneous geospatial linked data sources. The specific use case is semantic enrichment of hydrographic features provided by Natural Resources Canada (NRCan). The ER attempts to define and formalize the integration pipeline necessary to perform a fusion process for producing semantically coherent fused entities." + "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24763,35 +24241,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-021" + "@value": "12-128r15" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Semantic Web Link Builder and Triple Generator" + "@value": "OGC® GeoPackage Encoding Standard - with Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-068r4", + "@id": "http://www.opengis.net/def/docs/03-055r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-16" + "@value": "2003-06-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Daniel Balog, Robin Houtmeyers" + "@value": "Louis Rose" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -24801,27 +24279,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-068r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1282" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-068r4" + "@value": "Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint" }, { "@language": "en", - "@value": "Testbed-12 Vector Tiling Engineering Report" + "@value": "03-055r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 12 Engineering Report discusses the topic of vector tiling.\r\n\r\nWhile tiling and the use of multiple levels of details are a proven technique for raster data, it is relatively new for vector data. This is due to the increased complexity for tiling vector data compared to raster tiling. Further, there is a lack of standardization on the topic. Yet vector tiles can provide the same benefits as for raster tiles:\r\n\r\nServices can easily cache tiles and return them upon request, without the need for any additional pre/post processing (assuming no geometry construction is needed in the server). Consequently, clients can request and receive tiles quickly, ensuring better user experience.\r\n\r\nDue to tiled, multileveled data representations, clients can better access the data most suitable for their current map location and scale. This avoids the need to load too much data, which can cause both excessive memory usage and network traffic resulting in reduced overall performance.\r\n\r\nAn example of vector tiling that illustrates the impact of these benefits is the OpenStreetMap (OSM) data store, which includes over 30 GB of data with worldwide coverage consisting of millions of vector features. Loading and visualizing all the OSM data into an application would either result in a memory shortage or unacceptable performance. By means of vector tiling and the generation of multiple levels of detail, apps using OSM data can load such data sets very efficiently into applications.\r\n\r\nThis Engineering Report (ER) focuses on the general aspects of vector tiling. One of the main goals is to characterize what vector tiling is and how it can be approached. Highlighted topics include tiling approaches and strategies, tiling schemes, data coherence, simplification, scalability and styling. With respect to tiling schemes, existing standards material related to raster tiling schemes is incorporated to align both topics and to maximize interoperability. This includes the Defence Geospatial Information Working Group (DGIWG) Web Map Tiling Standard (WMTS) profile and the National System for Geospatial-Intelligence (NSG) WMTS profile as defined by the U.S. National Geospatial-Intelligence Agency (NGA).\r\n\r\nThe topic of implementing vector tiles using a tile encoding / storage format is not covered. A study of implementing vector tiles in OGC GeoPackage is part of a separate Engineering Report, OGC 16-067, that builds on the results of this ER.\r\n\r\n" + "@value": "*RETIRED* specifies the Engineering Viewpoint for the Critical Infrastructure Collaborative Environment (CICE). This open, distributed processing environment crosses organizational boundaries and includes a variety of components deployed within multiple communities. The CICE leverages OGC Web Services the publication of the availability of critical infrastructure services and data; the registration and categorization of published service and data providers; and the discovery and use of needed critical infrastructure services and data" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24832,35 +24310,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-068r4" + "@value": "03-055r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Vector Tiling Engineering Report" + "@value": "Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-046r3", + "@id": "http://www.opengis.net/def/docs/18-038r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-02-11" + "@value": "2019-02-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Lott" + "@value": "Tom Landry" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -24870,27 +24348,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=6716" + "@id": "https://docs.ogc.org/per/18-038r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-046r3" + "@value": "18-038r2" }, { "@language": "en", - "@value": "Topic 02 - Spatial Referencing by Coordinates" + "@value": "Machine Learning Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Describes modelling requirements for spatial referencing by coordinates." + "@value": "This OGC Engineering Report (ER) describes the application and use of OGC Web Services (OWS) for integrating Machine Learning (ML), Deep Learning (DL) and Artificial Intelligence (AI) in the OGC Testbed-14 Modeling, Portrayal, and Quality of Service (MoPoQ) Thread. This report is intended to present a holistic approach on how to support and integrate emerging AI and ML tools using OWS, as well as publishing their input and outputs. This approach should seek efficiency and effectiveness of knowledge sharing.\r\n\r\nThis engineering report will describe: experiences, lessons learned, best practices for workflows, service interaction patterns, application schemas, and use of controlled vocabularies. It is expected that the description of workflows for geospatial feature extraction will be more complex than the implementations found in the deliverables." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -24901,1249 +24379,1345 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-046r3" + "@value": "18-038r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 2 - Spatial Referencing by Coordinates" + "@value": "OGC Testbed-14: Machine Learning Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/per", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/18-034r3" - }, + "@id": "http://www.opengis.net/def/docs/22-016r3", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/16-037" - }, + "@type": "xsd:date", + "@value": "2023-06-26" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/19-021" - }, + "@value": "Brittany Eaton" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/22-017" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/16-045r2" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/19-025r1" - }, + "@id": "https://docs.ogc.org/per/22-016r3.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/20-039r2" + "@language": "en", + "@value": "Testbed-18: Moving Features Engineering Report" }, { - "@id": "http://www.opengis.net/def/docs/16-046r1" - }, + "@language": "en", + "@value": "22-016r3" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/21-025" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/16-063" - }, + "@value": "This OGC Testbed-18 (TB-18) Engineering Report (ER) is based on previous OGC Moving Features and Sensor Integration (MFSI) activities. The OGC TB-18 MFSI task addressed the interoperability between sensors and between sensing systems as well as the exchange of multiple sources of detected moving objects into one common analytic client. This ER describes the architecture framework for multi-source moving object detection into the client supported by OGC MFSI Standards and describes challenges of multi-sensor integration in the context of Moving Features data." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/17-018" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/12-147" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "22-016r3" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/16-062" - }, + "@language": "en", + "@value": "Testbed-18: Moving Features Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/15-026", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/17-037" - }, + "@type": "xsd:date", + "@value": "2015-10-30" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/15-010r4" - }, + "@value": "Thomas Forbes, Alberto Olivares, Richard Rombouts" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/09-035" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/19-007" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/16-056" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=63306" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/18-074" + "@language": "en", + "@value": "Testbed-11 Aviation Feature Schema Recommendations Engineering Report" }, { - "@id": "http://www.opengis.net/def/docs/12-018r1" - }, + "@language": "en", + "@value": "15-026" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/16-097" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/09-041r3" - }, + "@value": "Developed by EUROCONTROL, the Aviation Feature Schema (AFX) is a template for\r\napplication schemas to implement by adding their operational attributes. For example, the\r\nAirport Mapping format can be implemented by extending AFX. The AFX defines\r\nconcepts of geometry and temporality through predefined classes and properties.\r\nTherefore, these elements need not be redefined by application schemas. This means\r\nimplementations of the AFX abide by the same structure, therefore aiding interoperability\r\nand allowing the rapid development of schemas. The AFX schema is designed to be\r\ngeneric and easily reusable and it is not intended to replace the standard aviation models\r\nsuch as WXXM and AIXM.\r\nThis Engineering Report assesses the suitability of the AFX as a template for lowering\r\nthe GIS entry level for aviation data, providing recommendations of suitability and areas\r\nof improvement. The report is aimed at system and client developers that shall use AFX." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/14-013r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/10-131r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "15-026" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/16-024r2" - }, + "@language": "en", + "@value": "OGC® Testbed-11 Aviation Feature Schema Recommendations Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/19-023r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/12-118" - }, + "@type": "xsd:date", + "@value": "2019-12-11" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/20-031" - }, + "@value": "Andrea Aime" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/17-026r1" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/12-095" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/14-021r2" - }, + "@id": "https://docs.ogc.org/per/19-023r1.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/18-097" + "@language": "en", + "@value": "OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report" }, { - "@id": "http://www.opengis.net/def/docs/17-046" - }, + "@language": "en", + "@value": "19-023r1" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/20-013r4" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/15-053r1" - }, + "@value": "This OGC Testbed 15 Engineering Report (ER) describes a style encoding and metadata conceptual model that provides information for understanding styles intended usage, availability, compatibility with existing layers, and supporting style search. A style is a sequence of rules of symbolizing instructions to be applied by a rendering engine on one or more features and/or coverages" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/17-038" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/10-035r2" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "19-023r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/09-016" - }, + "@language": "en", + "@value": "OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/12-118", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/19-081" - }, + "@type": "xsd:date", + "@value": "2013-02-06" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/08-176r1" - }, + "@value": "Andreas Matheus" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/20-083r2" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/11-097" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/15-073r2" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=51806" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/09-032" + "@language": "en", + "@value": "OWS-9 Security Engineering Report " }, { - "@id": "http://www.opengis.net/def/docs/16-068r4" - }, + "@language": "en", + "@value": "12-118" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/20-087" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/22-004" - }, + "@value": "This Engineering Report describes the approaches to security taken in the OWS-9 initiative. This document presents the results of the work within the OWS-9 Security and Services Interoperability (SSI) thread and results from CCI and Innovations Cross Thread activities. \r\nThe report also describes the various tasks and their results regarding interoperability between different security components provided by different participants.\r\n" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/22-018" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/10-194r3" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "12-118" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/20-029" - }, + "@language": "en", + "@value": "OWS-9 Security Engineering Report " + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/16-068r4", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/15-057r2" - }, + "@type": "xsd:date", + "@value": "2017-06-16" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/15-118r1" - }, + "@value": "Daniel Balog, Robin Houtmeyers" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/16-040r1" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/17-023" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/21-017r1" - }, + "@id": "https://docs.ogc.org/per/16-068r4.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/16-098" + "@language": "en", + "@value": "16-068r4" }, { - "@id": "http://www.opengis.net/def/docs/18-032r2" - }, + "@language": "en", + "@value": "Testbed-12 Vector Tiling Engineering Report" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/19-027r2" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/14-029r2" - }, + "@value": "This OGC Testbed 12 Engineering Report discusses the topic of vector tiling.\r\n\r\nWhile tiling and the use of multiple levels of details are a proven technique for raster data, it is relatively new for vector data. This is due to the increased complexity for tiling vector data compared to raster tiling. Further, there is a lack of standardization on the topic. Yet vector tiles can provide the same benefits as for raster tiles:\r\n\r\nServices can easily cache tiles and return them upon request, without the need for any additional pre/post processing (assuming no geometry construction is needed in the server). Consequently, clients can request and receive tiles quickly, ensuring better user experience.\r\n\r\nDue to tiled, multileveled data representations, clients can better access the data most suitable for their current map location and scale. This avoids the need to load too much data, which can cause both excessive memory usage and network traffic resulting in reduced overall performance.\r\n\r\nAn example of vector tiling that illustrates the impact of these benefits is the OpenStreetMap (OSM) data store, which includes over 30 GB of data with worldwide coverage consisting of millions of vector features. Loading and visualizing all the OSM data into an application would either result in a memory shortage or unacceptable performance. By means of vector tiling and the generation of multiple levels of detail, apps using OSM data can load such data sets very efficiently into applications.\r\n\r\nThis Engineering Report (ER) focuses on the general aspects of vector tiling. One of the main goals is to characterize what vector tiling is and how it can be approached. Highlighted topics include tiling approaches and strategies, tiling schemes, data coherence, simplification, scalability and styling. With respect to tiling schemes, existing standards material related to raster tiling schemes is incorporated to align both topics and to maximize interoperability. This includes the Defence Geospatial Information Working Group (DGIWG) Web Map Tiling Standard (WMTS) profile and the National System for Geospatial-Intelligence (NSG) WMTS profile as defined by the U.S. National Geospatial-Intelligence Agency (NGA).\r\n\r\nThe topic of implementing vector tiles using a tile encoding / storage format is not covered. A study of implementing vector tiles in OGC GeoPackage is part of a separate Engineering Report, OGC 16-067, that builds on the results of this ER.\r\n\r\n" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/12-163" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/17-028" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "16-068r4" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/16-052" - }, + "@language": "en", + "@value": "Testbed-12 Vector Tiling Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/08-124r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/23-044" - }, + "@type": "xsd:date", + "@value": "2011-01-03" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/12-146" - }, + "@value": "Luis Bermudez" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/12-159" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/16-039r2" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/22-038r2" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=29535" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/16-047r1" + "@language": "en", + "@value": "Ocean Science Interoperability Experiment Phase 1 Report " }, { - "@id": "http://www.opengis.net/def/docs/16-137r2" - }, + "@language": "en", + "@value": "08-124r1" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/20-045" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/18-089" - }, + "@value": "This OGC Engineering report details lessons learned and best practices defined as part of the Phase 1 Ocean Science Interoperability Experiment (Oceans IE). The Oceans IE was performed to investigate the use of OGC Web Feature Services (WFS) and OGC Sensor Observation Services (SOS) for representing and exchanging point data records from fixed in-situ marine platforms. The activity concluded that for the Oceans community use of in-situ sensors that the OGC Sensor Observation Services (SOS) was better suited than the use of OGC Web Feature Services (WFS) for this purpose." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/19-020r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/11-106r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "08-124r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/14-038r1" - }, + "@language": "en", + "@value": "Ocean Science Interoperability Experiment Phase 1 Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/11-114", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/15-056" - }, - { - "@id": "http://www.opengis.net/def/docs/09-156r2" - }, + "@type": "xsd:date", + "@value": "2011-11-16" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/20-036" - }, + "@value": "David Danko, Lance Shipman, Paul Ramsey" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/16-064r1" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/21-029" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/19-046r1" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=45754" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/12-144" + "@language": "en", + "@value": "11-114" }, { - "@id": "http://www.opengis.net/def/docs/16-093r1" - }, + "@language": "en", + "@value": "OWS-8 Bulk Geodata Transfer with File Geodatabase" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/19-015" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/16-088r1" - }, + "@value": "This document provides an overview of the File Geodatabase API and documents the testing performed in the OWS 8 Testbed." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/11-089r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/14-001" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "11-114" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/21-013" - }, + "@language": "en", + "@value": "OWS-8 Bulk Geodata Transfer with File Geodatabase" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/17-093r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/20-034" - }, + "@type": "xsd:date", + "@value": "2018-08-22" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/15-050r3" - }, + "@value": "Jeff Yutzler, Ashley Antonides" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/18-083" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/14-039" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/18-087r5" - }, + "@id": "https://docs.ogc.org/per/17-093r1.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/18-023r1" + "@language": "en", + "@value": "GeoPackage Related Tables Extension Interoperability Experiment Engineering Report" }, { - "@id": "http://www.opengis.net/def/docs/20-020" - }, + "@language": "en", + "@value": "17-093r1" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/15-051r3" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/13-032" - }, + "@value": "This OGC Engineering Report describes the results of the OGC GeoPackage (GPKG) Related Tables Extension Interoperability Experiment (GPKG-RTE IE). This IE tested a proposed extension to the OGC GeoPackage Encoding Standard (12-128r14). The GPKG-RTE defines the rules and requirements for associating tables with existing feature or attribute tables in a GeoPackage data store. As part of this IE, the participants performed Technology Integration Experiments (TIEs) where they produced GeoPackages that used this extension, loaded them into GPKG-compliant software systems, and observed the results. As a result of this work, the IE participants agree that the extension is fit for use and consideration as a standard by OGC." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/16-028r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/18-048r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "17-093r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/09-075r1" - }, + "@language": "en", + "@value": "OGC GeoPackage Related Tables Extension Interoperability Experiment Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/15-054", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/12-160r1" - }, + "@type": "xsd:date", + "@value": "2015-11-18" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/11-073r2" - }, + "@value": "Stephane Fellah" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/16-033r1" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/15-066r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/19-023r1" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=64405" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/14-017" + "@language": "en", + "@value": "Testbed-11 Implementing Linked Data and Semantically Enabling OGC Services Engineering Report" }, { - "@id": "http://www.opengis.net/def/docs/16-022" - }, + "@language": "en", + "@value": "15-054" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/19-018" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/10-002" - }, + "@value": "This OGC® Engineering Report (ER) summarizes the approaches, findings and the results\r\nof the Linked Data and Semantic Enablement of OGC Web Services sub-thread activities\r\nof the OGC Testbed-11 Cross Community Interoperability (CCI) Thread. This report\r\nprovides an overview of existing standards for geosemantics, outlines the approaches\r\nadopted during the testbed, describes the conceptual semantic models and services\r\ndeveloped during this testbed to leverage Linked Data and semantic enabled OGC web\r\nservices." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/11-139r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/12-096" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "15-054" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/10-132" - }, + "@language": "en", + "@value": "OGC® Testbed-11 Implementing Linked Data and Semantically Enabling OGC Services Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/07-056r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/17-032r2" - }, + "@type": "xsd:date", + "@value": "2007-07-23" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/15-082" - }, + "@value": "John Herring, OAB, Architecture WG" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/11-091" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/11-095r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/22-054r1" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=21976" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/15-054" + "@language": "en", + "@value": "The Specification Model -- Structuring an OGC specification to encourage implementation" }, { - "@id": "http://www.opengis.net/def/docs/17-019" - }, + "@language": "en", + "@value": "07-056r1" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/14-028r1" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/16-044" - }, + "@value": "This standard specifies some desirable characteristics of a standards specification that will encourage implementations by minimizing difficulty and optimizing usability and interoperability. " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/16-041r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/15-058" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "07-056r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/23-025" - }, + "@language": "en", + "@value": "The Specification Model -- Structuring an OGC specification to encourage implementation" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/17-014r7", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/12-155" - }, + "@type": "xsd:date", + "@value": "2020-02-08" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/16-094r3" - }, + "@value": "Carl Reed, Tamrat Belayneh" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/18-025" - }, + "@id": "http://www.opengis.net/def/doc-type/cs" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/16-115" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/11-086r1" - }, + "@id": "https://docs.ogc.org/cs/17-014r7/17-014r7.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/11-116" + "@language": "en", + "@value": "Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification" }, { - "@id": "http://www.opengis.net/def/docs/17-061" - }, + "@language": "en", + "@value": "17-014r7" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/23-020r2" - }, + "@id": "http://www.opengis.net/def/doc-type/cs" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/16-030" - }, + "@value": "A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data.Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files.\r\n\r\nThe delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types.\r\n\r\nThe open community GitHub version of this standard is here: https://github.com/Esri/i3s-spec [2]." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/10-127r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/09-038r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "17-014r7" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/19-003" - }, + "@language": "en", + "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification" + } + ] + }, + { + "@id": "http://www.opengis.net/def/doc-type/as", + "http://www.w3.org/2004/02/skos/core#narrower": [ { - "@id": "http://www.opengis.net/def/docs/09-138" + "@id": "http://www.opengis.net/def/docs/06-004r4" }, { - "@id": "http://www.opengis.net/def/docs/19-083" + "@id": "http://www.opengis.net/def/docs/18-005r8" }, { - "@id": "http://www.opengis.net/def/docs/23-043" + "@id": "http://www.opengis.net/def/docs/99-108r2" }, { - "@id": "http://www.opengis.net/def/docs/09-053r5" + "@id": "http://www.opengis.net/def/docs/17-087r13" }, { - "@id": "http://www.opengis.net/def/docs/18-046" + "@id": "http://www.opengis.net/def/docs/00-116" }, { - "@id": "http://www.opengis.net/def/docs/15-052r1" + "@id": "http://www.opengis.net/def/docs/21-060r2" }, { - "@id": "http://www.opengis.net/def/docs/18-049r1" + "@id": "http://www.opengis.net/def/docs/02-112" }, { - "@id": "http://www.opengis.net/def/docs/18-030" + "@id": "http://www.opengis.net/def/docs/07-011" }, { - "@id": "http://www.opengis.net/def/docs/10-061r1" + "@id": "http://www.opengis.net/def/docs/20-082r4" }, { - "@id": "http://www.opengis.net/def/docs/23-048" + "@id": "http://www.opengis.net/def/docs/19-014r3" }, { - "@id": "http://www.opengis.net/def/docs/17-088r1" + "@id": "http://www.opengis.net/def/docs/20-040r3" }, { - "@id": "http://www.opengis.net/def/docs/20-043" + "@id": "http://www.opengis.net/def/docs/10-030" }, { - "@id": "http://www.opengis.net/def/docs/20-035" + "@id": "http://www.opengis.net/def/docs/04-084r4" }, { - "@id": "http://www.opengis.net/def/docs/16-017" + "@id": "http://www.opengis.net/def/docs/99-110" }, { - "@id": "http://www.opengis.net/def/docs/15-026" + "@id": "http://www.opengis.net/def/docs/00-115" }, { - "@id": "http://www.opengis.net/def/docs/20-042" + "@id": "http://www.opengis.net/def/docs/08-126" }, { - "@id": "http://www.opengis.net/def/docs/10-060r1" + "@id": "http://www.opengis.net/def/docs/21-053r1" }, { - "@id": "http://www.opengis.net/def/docs/15-030r3" + "@id": "http://www.opengis.net/def/docs/04-107" }, { - "@id": "http://www.opengis.net/def/docs/11-019r2" + "@id": "http://www.opengis.net/def/docs/99-113" }, { - "@id": "http://www.opengis.net/def/docs/20-030" + "@id": "http://www.opengis.net/def/docs/22-010r4" }, { - "@id": "http://www.opengis.net/def/docs/16-034" - }, + "@id": "http://www.opengis.net/def/docs/11-111r1" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r12a", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/17-022" - }, + "@type": "xsd:date", + "@value": "2015-04-20" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/20-018" - }, + "@value": "Paul Daisey" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/10-087" - }, + "@id": "http://www.opengis.net/def/doc-type/isc" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/15-067" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/21-039r1" - }, + "@id": "https://www.geopackage.org/spec" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/09-015" + "@language": "en", + "@value": "12-128r12a" }, { - "@id": "http://www.opengis.net/def/docs/23-027" - }, + "@language": "en", + "@value": "GeoPackage Encoding Standard - With Corrigendum" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/12-075" - }, + "@id": "http://www.opengis.net/def/doc-type/isc" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/16-036r1" - }, + "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a “native” storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/20-037" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/16-092r2" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "12-128r12a" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/15-025r2" - }, - { - "@id": "http://www.opengis.net/def/docs/14-000" - }, - { - "@id": "http://www.opengis.net/def/docs/18-021" - }, - { - "@id": "http://www.opengis.net/def/docs/15-022" - }, - { - "@id": "http://www.opengis.net/def/docs/19-082r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-048r3" - }, - { - "@id": "http://www.opengis.net/def/docs/12-154" - }, - { - "@id": "http://www.opengis.net/def/docs/14-016" - }, - { - "@id": "http://www.opengis.net/def/docs/23-059" - }, - { - "@id": "http://www.opengis.net/def/docs/17-094r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-030r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-067r2" - }, - { - "@id": "http://www.opengis.net/def/docs/14-057" - }, - { - "@id": "http://www.opengis.net/def/docs/19-070" - }, - { - "@id": "http://www.opengis.net/def/docs/21-031" - }, - { - "@id": "http://www.opengis.net/def/docs/12-104r1" - }, - { - "@id": "http://www.opengis.net/def/docs/20-091" - }, - { - "@id": "http://www.opengis.net/def/docs/16-031r1" - }, - { - "@id": "http://www.opengis.net/def/docs/18-050r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-043" - }, - { - "@id": "http://www.opengis.net/def/docs/18-090r2" - }, - { - "@id": "http://www.opengis.net/def/docs/12-119r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-114" - }, - { - "@id": "http://www.opengis.net/def/docs/10-088r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-021r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-038" - }, - { - "@id": "http://www.opengis.net/def/docs/12-018r2" - }, - { - "@id": "http://www.opengis.net/def/docs/12-151" - }, - { - "@id": "http://www.opengis.net/def/docs/21-023" - }, - { - "@id": "http://www.opengis.net/def/docs/21-044" - }, - { - "@id": "http://www.opengis.net/def/docs/16-027" - }, - { - "@id": "http://www.opengis.net/def/docs/20-015r2" - }, - { - "@id": "http://www.opengis.net/def/docs/22-031r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-156" - }, - { - "@id": "http://www.opengis.net/def/docs/15-046r2" - }, - { - "@id": "http://www.opengis.net/def/docs/11-107" - }, - { - "@id": "http://www.opengis.net/def/docs/13-080r3" - }, - { - "@id": "http://www.opengis.net/def/docs/18-047r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-014r2" - }, - { - "@id": "http://www.opengis.net/def/docs/17-025r2" - }, - { - "@id": "http://www.opengis.net/def/docs/19-073r1" - }, - { - "@id": "http://www.opengis.net/def/docs/18-086r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-020r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-053r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-032" - }, - { - "@id": "http://www.opengis.net/def/docs/15-077r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-108" - }, - { - "@id": "http://www.opengis.net/def/docs/21-058" - }, - { - "@id": "http://www.opengis.net/def/docs/12-105" - }, - { - "@id": "http://www.opengis.net/def/docs/16-023r3" - }, - { - "@id": "http://www.opengis.net/def/docs/20-067" - }, - { - "@id": "http://www.opengis.net/def/docs/21-018" - }, - { - "@id": "http://www.opengis.net/def/docs/22-014" - }, - { - "@id": "http://www.opengis.net/def/docs/14-044" - }, - { - "@id": "http://www.opengis.net/def/docs/09-007" - }, - { - "@id": "http://www.opengis.net/def/docs/17-021" - }, - { - "@id": "http://www.opengis.net/def/docs/09-129" - }, - { - "@id": "http://www.opengis.net/def/docs/21-030" - }, - { - "@id": "http://www.opengis.net/def/docs/21-019" - }, - { - "@id": "http://www.opengis.net/def/docs/22-035" - }, - { - "@id": "http://www.opengis.net/def/docs/16-042r1" - }, - { - "@id": "http://www.opengis.net/def/docs/18-022r1" - }, - { - "@id": "http://www.opengis.net/def/docs/10-079r3" - }, - { - "@id": "http://www.opengis.net/def/docs/23-042" - }, - { - "@id": "http://www.opengis.net/def/docs/10-074" - }, - { - "@id": "http://www.opengis.net/def/docs/17-043" - }, - { - "@id": "http://www.opengis.net/def/docs/21-054" - }, - { - "@id": "http://www.opengis.net/def/docs/14-002" - }, - { - "@id": "http://www.opengis.net/def/docs/24-008" - }, - { - "@id": "http://www.opengis.net/def/docs/22-040" - }, - { - "@id": "http://www.opengis.net/def/docs/18-085" - }, - { - "@id": "http://www.opengis.net/def/docs/22-016r3" - }, - { - "@id": "http://www.opengis.net/def/docs/19-010r2" - }, - { - "@id": "http://www.opengis.net/def/docs/14-079r1" - }, - { - "@id": "http://www.opengis.net/def/docs/20-032" - }, - { - "@id": "http://www.opengis.net/def/docs/21-008" - }, - { - "@id": "http://www.opengis.net/def/docs/23-033" - }, - { - "@id": "http://www.opengis.net/def/docs/20-016" - }, - { - "@id": "http://www.opengis.net/def/docs/12-094" - }, - { - "@id": "http://www.opengis.net/def/docs/16-035" - }, - { - "@id": "http://www.opengis.net/def/docs/09-140r2" - }, - { - "@id": "http://www.opengis.net/def/docs/18-028r2" - }, - { - "@id": "http://www.opengis.net/def/docs/20-012" - }, - { - "@id": "http://www.opengis.net/def/docs/20-073" - }, - { - "@id": "http://www.opengis.net/def/docs/23-011r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-035" - }, - { - "@id": "http://www.opengis.net/def/docs/10-059r2" - }, - { - "@id": "http://www.opengis.net/def/docs/19-088r2" - }, - { - "@id": "http://www.opengis.net/def/docs/21-027" - }, - { - "@id": "http://www.opengis.net/def/docs/19-024r1" - }, - { - "@id": "http://www.opengis.net/def/docs/21-075r2" - }, - { - "@id": "http://www.opengis.net/def/docs/09-182r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-024" - }, - { - "@id": "http://www.opengis.net/def/docs/11-063r6" - }, - { - "@id": "http://www.opengis.net/def/docs/14-086r1" - }, - { - "@id": "http://www.opengis.net/def/docs/23-028" - }, - { - "@id": "http://www.opengis.net/def/docs/15-028" - }, - { - "@id": "http://www.opengis.net/def/docs/14-049" - }, - { - "@id": "http://www.opengis.net/def/docs/11-061r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-018" - }, - { - "@id": "http://www.opengis.net/def/docs/16-055" - }, - { - "@id": "http://www.opengis.net/def/docs/20-011" - }, - { - "@id": "http://www.opengis.net/def/docs/16-051" - }, - { - "@id": "http://www.opengis.net/def/docs/11-096" - }, - { - "@id": "http://www.opengis.net/def/docs/15-027r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-050r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-041" - }, - { - "@id": "http://www.opengis.net/def/docs/22-023r2" - }, - { - "@id": "http://www.opengis.net/def/docs/17-045" - }, - { - "@id": "http://www.opengis.net/def/docs/19-026" - }, - { - "@id": "http://www.opengis.net/def/docs/20-019r1" - }, - { - "@id": "http://www.opengis.net/def/docs/10-155" - }, - { - "@id": "http://www.opengis.net/def/docs/15-047r3" - }, - { - "@id": "http://www.opengis.net/def/docs/18-045" - }, - { - "@id": "http://www.opengis.net/def/docs/18-094r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-033" - }, - { - "@id": "http://www.opengis.net/def/docs/21-074r2" - }, - { - "@id": "http://www.opengis.net/def/docs/12-162r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-064r3" - }, - { - "@id": "http://www.opengis.net/def/docs/11-062r2" - }, - { - "@id": "http://www.opengis.net/def/docs/16-067r4" - }, - { - "@id": "http://www.opengis.net/def/docs/13-046r2" - }, - { - "@id": "http://www.opengis.net/def/docs/09-006" - }, - { - "@id": "http://www.opengis.net/def/docs/19-075r1" - }, - { - "@id": "http://www.opengis.net/def/docs/10-086r1" - }, - { - "@id": "http://www.opengis.net/def/docs/18-026r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-061" - }, - { - "@id": "http://www.opengis.net/def/docs/14-009r1" - }, - { - "@id": "http://www.opengis.net/def/docs/22-041" - }, - { - "@id": "http://www.opengis.net/def/docs/19-084" - }, - { - "@id": "http://www.opengis.net/def/docs/20-027" - }, - { - "@id": "http://www.opengis.net/def/docs/18-009" - }, - { - "@id": "http://www.opengis.net/def/docs/19-012r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-097" - }, - { - "@id": "http://www.opengis.net/def/docs/10-073r1" - }, - { - "@id": "http://www.opengis.net/def/docs/20-025r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-063" - }, - { - "@id": "http://www.opengis.net/def/docs/12-152r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-031r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-093" - }, - { - "@id": "http://www.opengis.net/def/docs/09-012" - }, - { - "@id": "http://www.opengis.net/def/docs/12-103r3" - }, - { - "@id": "http://www.opengis.net/def/docs/09-072" - }, - { - "@id": "http://www.opengis.net/def/docs/18-076" - }, - { - "@id": "http://www.opengis.net/def/docs/17-090r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-093r1" - }, - { - "@id": "http://www.opengis.net/def/docs/08-124r1" - }, - { - "@id": "http://www.opengis.net/def/docs/13-011" - }, - { - "@id": "http://www.opengis.net/def/docs/09-034" - }, - { - "@id": "http://www.opengis.net/def/docs/11-092r2" - }, - { - "@id": "http://www.opengis.net/def/docs/21-020r1" - }, - { - "@id": "http://www.opengis.net/def/docs/20-021r2" - }, - { - "@id": "http://www.opengis.net/def/docs/09-064r2" - }, - { - "@id": "http://www.opengis.net/def/docs/21-028" - }, - { - "@id": "http://www.opengis.net/def/docs/12-157" - }, - { - "@id": "http://www.opengis.net/def/docs/16-099" - }, - { - "@id": "http://www.opengis.net/def/docs/17-036" - }, - { - "@id": "http://www.opengis.net/def/docs/14-037" - }, - { - "@id": "http://www.opengis.net/def/docs/18-038r2" - }, - { - "@id": "http://www.opengis.net/def/docs/11-013r6" - }, - { - "@id": "http://www.opengis.net/def/docs/21-055" - }, - { - "@id": "http://www.opengis.net/def/docs/16-020" - }, - { - "@id": "http://www.opengis.net/def/docs/16-029r1" - }, - { - "@id": "http://www.opengis.net/def/docs/21-042" - }, - { - "@id": "http://www.opengis.net/def/docs/18-035" - }, + "@language": "en", + "@value": "OGC® GeoPackage Encoding Standard - With Corrigendum" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/03-105r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/17-048" - }, + "@type": "xsd:date", + "@value": "2004-04-19" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/18-091r2" - }, + "@value": "Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/12-133" - }, + "@id": "http://www.opengis.net/def/doc-type/d-bp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/13-054r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/10-192" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=4700" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/09-073" + "@language": "en", + "@value": "03-105r1" }, { - "@id": "http://www.opengis.net/def/docs/18-084" - }, + "@language": "en", + "@value": "Geography Markup Language (GML) Encoding Specification" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/21-022" - }, + "@id": "http://www.opengis.net/def/doc-type/d-bp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/19-069" - }, + "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/11-093r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/21-064" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "03-105r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/17-027" - }, + "@language": "en", + "@value": "OpenGIS Geography Markup Language (GML) Encoding Specification" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/15-052r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/11-085r1" - }, + "@type": "xsd:date", + "@value": "2016-01-18" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/21-032" - }, + "@value": "Frédéric Houbie" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/18-036r1" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/17-029r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/19-040" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=64860" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/22-020r1" + "@language": "en", + "@value": "15-052r1" }, { - "@id": "http://www.opengis.net/def/docs/10-069r2" - }, + "@language": "en", + "@value": "Testbed 11 REST Interface Engineering Report" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/21-021" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/13-053r1" - }, + "@value": "REST architectural principles are associated with optimal functioning of the Web but their manifestation in geospatial Web services standards is not straightforward. This OGC Engineering Report (ER) examines their use both in existing OGC Services standards and in new or revised service standard proposals, some of which were implemented during OGC Testbed 11. The ER then defines possible uniform practices for developing bindings or interaction styles for OGC Web services that appropriately leverage REST principles." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/15-065r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/11-113r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "15-052r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/19-062" - }, + "@language": "en", + "@value": "OGC® Testbed 11 REST Interface Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/06-121r3", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/14-007" - }, + "@type": "xsd:date", + "@value": "2007-04-03" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/19-019" - }, + "@value": "Arliss Whiteside" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/15-024r2" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/18-101" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/22-043r1" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=20040" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/22-013r3" + "@language": "en", + "@value": "06-121r3" }, { - "@id": "http://www.opengis.net/def/docs/20-090" - }, + "@language": "en", + "@value": "Web Service Common Implementation Specification" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/21-036" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/14-048" - }, + "@value": "The OpenGIS® Web Services Common (WS-Common) Interface Standard specifies parameters and data structures that are common to all OGC Web Service (OWS) Standards. The standard normalizes the ways in which operation requests and responses handle such elements as bounding boxes, exception processing, URL requests, URN expressions, and key value encoding. Among its uses, this document serves as a normative reference for other OGC Web Service standards, including the OpenGIS Web Map Service (WMS) [http://www.opengeospatial.org/standards/wms], Web Feature Service (WFS) [http://www.opengeospatial.org/standards/wfs], and Web Coverage Service (WCS) [http://www.opengeospatial.org/standards/wcs] standards. Rather than continuing to repeat this material in each such standard, each standard will normatively reference parts of this document." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/12-139" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/19-041r3" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "06-121r3" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/11-072r2" - }, + "@language": "en", + "@value": "OpenGIS Web Service Common Implementation Specification" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/08-131r3", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/18-078" - }, + "@type": "xsd:date", + "@value": "2009-10-19" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/21-035r1" - }, + "@value": "Policy SWG" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/18-029" - }, + "@id": "http://www.opengis.net/def/doc-type/pol" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/16-048r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/17-078" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=34762&version=2" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/23-050" + "@language": "en", + "@value": "The Specification Model - Standard for Modular specifications" }, { - "@id": "http://www.opengis.net/def/docs/17-040" - }, + "@language": "en", + "@value": "08-131r3" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/16-059" - }, + "@id": "http://www.opengis.net/def/doc-type/pol" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/12-158" - }, + "@value": "This standard contains requirements for writing standards to be used for any document whose\r\neventual purpose is the specification of requirements for software, services or data structures. " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/15-011r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/10-184" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "08-131r3" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/18-090r1" - }, + "@language": "en", + "@value": "The Specification Model - Standard for Modular specifications" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/14-003", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/10-036r2" - }, + "@type": "xsd:date", + "@value": "2014-12-02" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/14-006r1" - }, + "@value": "Simon J D Cox, Bruce A Simons" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/20-041" - }, + "@id": "http://www.opengis.net/def/doc-type/bp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/19-016r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/18-057" - }, + "@id": "https://docs.ogc.org/bp/14-003/14-003.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/10-130" + "@language": "en", + "@value": "14-003" }, { - "@id": "http://www.opengis.net/def/docs/20-038" - }, + "@language": "en", + "@value": "WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/22-024r2" - }, + "@id": "http://www.opengis.net/def/doc-type/bp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/19-022r1" - }, + "@value": "This Best Practice describes how to configure XML documents for single and time series water quality measurements. In addition to stating the rules for using the O&M and WML 2 standards, along with the appropriate content ontologies, this Best Practice provides guidance through examples. This document is intended to complement WaterML 2.0 as part of a suite of standards for water observation data." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/17-042" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/09-037r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "14-003" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/11-055" - }, + "@language": "en", + "@value": "WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/09-047r3", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/23-010" - }, + "@type": "xsd:date", + "@value": "2011-03-01" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/20-033" - }, + "@value": "Simon Cox" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/14-114r1" - }, + "@id": "http://www.opengis.net/def/doc-type/pol-nts" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/16-050" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/14-008" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=41774" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/10-094" + "@language": "en", + "@value": "OGC-NA Name type specification - documents" }, { - "@id": "http://www.opengis.net/def/docs/16-049r1" - }, + "@language": "en", + "@value": "09-047r3" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/14-073r1" - }, + "@id": "http://www.opengis.net/def/doc-type/pol-nts" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/11-134" - }, + "@value": "This document specifies a rule for constructing OGC names that may be used for identifying documents and elements within a document." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/09-036r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/23-047" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "09-047r3" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/15-068r2" + "@language": "en", + "@value": "OGC-NA Name type specification - documents" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-029", + "@id": "http://www.opengis.net/def/docs/10-001", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-03-31" + "@value": "2010-03-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sara Saeedi" + "@value": "Stuart E. Middleton" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -26153,27 +25727,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-029.html" + "@id": "https://portal.ogc.org/files/?artifact_id=37139" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-029" + "@value": "10-001" }, { "@language": "en", - "@value": "OGC Testbed 17: MASBUS Integration Engineering Report" + "@value": "SANY Fusion and Modelling Architecture" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 17 Engineering Report (ER) analyses the Measures and Signatures Intelligence Enterprise Service Bus (MASBUS) pilot software and the efforts to integrate with OGC SensorThings API resources. After introducing MASBUS, a server implementation is designed to digest sensor data and demonstrate the SensorThings MQTT (Message Queuing Telemetry Transport) extension of the MASBUS software. To show the SensorThings MQTT extension of the MASBUS software, a MASBUS client implementation is also presented. This ER discusses the results of the MASBUS integration, including all lessons learned from the experiments completed during the OGC Testbed 17 Sensor Integration thread and concludes with a set of optimum recommendations.\r\n\r\n" + "@value": "This document reports the considered SANY best practice for using OGC standards to provide generic fusion processing services. Concrete case studies are documented and a detailed appendix is provided with example of XML request and responses." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -26184,35 +25758,38 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-029" + "@value": "10-001" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed 17: MASBUS Integration Engineering Report" + "@value": "SANY Fusion and Modelling Architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-014r3", + "@id": "http://www.opengis.net/def/docs/07-165r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-10-22" + "@value": "2013-04-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Mike Botts, George Percivall, Carl Reed, John Davidson" + }, + { + "@value": "Carl Reed, Mike Botts, George Percivall, John Davidson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -26222,27 +25799,34 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/as/19-014r3/19-014r3.html" + "@id": "https://docs.ogc.org/wp/07-165r1/" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-014r3" + "@value": "OGC Sensor Web Enablement: Overview and High Level Architecture" + }, + { + "@language": "en", + "@value": "Sensor Web Enablement: Overview And High Level Architecture" }, { "@language": "en", - "@value": "Topic 22 - Core Tiling Conceptual and Logical Models for 2D Euclidean Space" + "@value": "07-165r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Abstract Specification (AS) defines:\r\n\r\nA conceptual model for tiling space in any dimension and;\r\n\r\nA logical model for 2D tiled structures and by extension tiling. The logical model is based on the conceptual model.\r\n\r\nThe conceptual model specified in this Abstract Specification could be a sub-class in a more comprehensive Spatial Partitioning Conceptual Model. Additional Parts may be added to this AS for other dimensions, such as 3D, or other uses cases." + "@value": "This OGC White Paper provides a high-level overview of and architecture for the Open Geospatial\r\nConsortium (OGC) standards activities that focus on sensors, sensor networks, and a concept called the\r\n“Sensor Web”. This OGC focus area is known as Sensor Web Enablement (SWE)." + }, + { + "@value": "A sensor network is a computer accessible network of many, spatially distributed devices using sensors to monitor conditions at different locations, such as temperature, sound, vibration, pressure, motion or pollutants[1]. A Sensor Web refers to web accessible sensor networks and archived sensor data that can be discovered and accessed using standard protocols and application program interfaces (APIs)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -26253,35 +25837,39 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-014r3" + "@value": "07-165r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 22 - Core Tiling Conceptual and Logical Models for 2D Euclidean Space" + "@value": "OGC Sensor Web Enablement: Overview and High Level Architecture" + }, + { + "@language": "en", + "@value": "OGC® Sensor Web Enablement: Overview And High Level Architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-067", + "@id": "http://www.opengis.net/def/docs/06-004r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-10-07" + "@value": "2007-01-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "Graham Vowles" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -26291,27 +25879,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/21-067.html" + "@id": "https://portal.ogc.org/files/?artifact_id=17802" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-067" + "@value": "06-004r4" }, { "@language": "en", - "@value": "OGC: Towards Data Cube Interoperability" + "@value": "Topic 18 - Geospatial Digital Rights Management Reference Model (GeoDRM RM)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Data cubes, multidimensional arrays of data, are used frequently these days, but differences in design, interfaces, and handling of temporal characteristics are causing interoperability challenges for anyone interacting with more than one solution. To address these challenges, the Open Geospatial Consortium (OGC) and the Group on Earth Observation (GEO) invited global data cube experts to discuss state-of-the-art and way forward at the “Towards Data Cube Interoperability” workshop. The two-day workshop, conducted in late April 2021, started with a series of pre-recorded position statements by data cube providers and data cube users. These videos served as the entry points for intense discussions that not only produced a new definition of the term ‘data cube’ (by condensing and shifting emphasize on what is known as the six faces model), but also pointed out a wide variety of expectations with regards to data cube behaviour and characteristics as well as data cube usage patterns. This report summarizes the various perspectives and discusses the next steps towards efficient usage of data cubes. It starts with the new definition of the term Data Cube, as this new understanding drives several recommendations discussed later in this report. The report includes further discussion that followed the actual workshop, mainly conducted in the context of the Geo Data Cube task in OGC Testbed-17." + "@value": "This document is a reference model for digital rights management (DRM) functionality for geospatial resources (GeoDRM). As such, it is connected to the general DRM market in that geospatial resources must be treated as nearly as possible like other digital resources, such as music, text, or services. It is not the intention here to reinvent a market that already exists and is thriving, but to make sure that a larger market has access to geospatial resources through a mechanism that it understands and that is similar to the ones already in use." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -26322,30 +25910,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-067" + "@value": "06-004r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC: Towards Data Cube Interoperability" + "@value": "Topic 18 - Geospatial Digital Rights Management Reference Model (GeoDRM RM)" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-093r2", + "@id": "http://www.opengis.net/def/docs/12-093", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-12-19" + "@value": "2013-02-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -26360,17 +25948,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46242" + "@id": "https://portal.ogc.org/files/?artifact_id=51784" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-093r2" + "@value": "12-093" }, { "@language": "en", - "@value": "OWS-8 Aviation Architecture Engineering Report" + "@value": "OWS-9: UML-to-GML-Application-Schema (UGAS) Conversion Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -26380,7 +25968,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document describes the architecture implemented in the OWS-8 Aviation thread, including general workflows. The document contains a summary description of the various components within the architecture. An introduction to the Access Control System is provided. Furthermore, the document describes relevant aspects of handling events and notifications. Lessons learned – for example regarding the AIXM Temporality Model – as well as scenarios and accomplishments are documented as well." + "@value": "The main scope of the schema automation activities in the OWS-9 initiative was twofold:\r\n•\tSupport for the SWE Common 2.0 XML Schema encoding rule\r\n•\tDevelopment of and support for an encoding rule for JSON instance data\r\nIn both cases the scope includes implementation of the encoding rules in ShapeChange.\r\nIn addition, an initial analysis of the possibilities for generating SWE Common 2.0 record descriptions from schemas in UML has been conducted and the results are described in this document.\r\nThe approach and results to both work items are described and discussed in this engineering report. This Engineering Report has been prepared as part of the OGC Web Services Phase 9 (OWS-9) initiative.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -26391,30 +25979,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-093r2" + "@value": "12-093" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 Aviation Architecture Engineering Report" + "@value": "OWS-9: UML-to-GML-Application-Schema (UGAS) Conversion Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-016r3", + "@id": "http://www.opengis.net/def/docs/10-130", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-06-26" + "@value": "2010-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Brittany Eaton" + "@value": "Debbie Wilson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -26429,17 +26017,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-016r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=40114" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-016r3" + "@value": "10-130" }, { "@language": "en", - "@value": "Testbed-18: Moving Features Engineering Report" + "@value": "OWS-7 Aviation - FUSE Deployment Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -26449,7 +26037,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed-18 (TB-18) Engineering Report (ER) is based on previous OGC Moving Features and Sensor Integration (MFSI) activities. The OGC TB-18 MFSI task addressed the interoperability between sensors and between sensing systems as well as the exchange of multiple sources of detected moving objects into one common analytic client. This ER describes the architecture framework for multi-source moving object detection into the client supported by OGC MFSI Standards and describes challenges of multi-sensor integration in the context of Moving Features data." + "@value": "This document describes the integration results of deploying OGC Web Services on the FAA chosen Enterprise Service Bus (ESB) - FUSE. Snowflake Software were commissioned to evaluate the impacts of the FAA SWIM security requirements for both secure messaging and user authentication and gain an understanding of the requirements for deploying OGC web services into the Apache FUSE Enterprise Service Bus (ESB)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -26460,35 +26048,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-016r3" + "@value": "10-130" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-18: Moving Features Engineering Report" + "@value": "OWS-7 Aviation - FUSE Deployment Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-032", + "@id": "http://www.opengis.net/def/docs/06-131r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-06-06" + "@value": "2010-02-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Frédéric Houbie, Lorenzo Bigagli" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -26498,27 +26086,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20586" + "@id": "https://portal.ogc.org/files/?artifact_id=35528" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-032" + "@value": "Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products" }, { "@language": "en", - "@value": "Frame image geopositioning metadata GML 3.2 application schema" + "@value": "06-131r6" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies a GML 3.2 Application Schema for frame image geopositioning metadata, for XML encoding of the georeferencing coordinate transformation parameters of an unrectified frame image. A frame image is one whose entire two-dimensional extent was collected at one time. A georeferencing coordinate transformation can transform position coordinates between a specific ground-based (or object) Coordinate Reference System (CRS) and the image CRS." + "@value": "This document describes the mapping of Earth Observation Products – defined in the OGC® GML 3.1.1 Application schema for Earth Observation products [OGC 06-080r4] (version 0.9.3) – to an ebRIM structure within an OGC® Catalogue 2.0.2 (Corrigendum 2 Release) [OGC 07-006r1] implementing the CSW-ebRIM Registry Service – part 1: ebRIM profile of CSW [OGC 07-110r4]. This standard defines the way Earth Observation products metadata resources are organized and implemented in the Catalogue for discovery, retrieval and management." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -26529,35 +26117,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-032" + "@value": "06-131r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Frame image geopositioning metadata GML 3.2 application schema" + "@value": "OGC® Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-069", + "@id": "http://www.opengis.net/def/docs/09-083r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-08-19" + "@value": "2011-04-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ron Lake" + "@value": "Adrian Custer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -26567,27 +26155,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=11339" + "@id": "https://portal.ogc.org/files/?artifact_id=39397" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "02-069" + "@value": "GeoAPI 3.0 Implementation Standard" }, { "@language": "en", - "@value": "Geography Markup Language" + "@value": "09-083r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features." + "@value": "The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be used for the manipulation of geographic information structured following the specifications adopted by the Technical Committee211 of the International Organization for Standardization (ISO) and by the Open Geospatial Consortium (OGC). This standard standardizes the informatics contract between the client code which manipulates normalized data structures of geographic information based on the published API and the library code able both to instantiate and operate on these data structures according to the rules required by the published API and by the ISO and OGC standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -26598,106 +26186,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-069" + "@value": "09-083r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geography Markup Language" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/retired", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/03-003r10" - }, - { - "@id": "http://www.opengis.net/def/docs/05-110" - }, - { - "@id": "http://www.opengis.net/def/docs/03-064r10" - }, - { - "@id": "http://www.opengis.net/def/docs/99-103" - }, - { - "@id": "http://www.opengis.net/def/docs/03-063r1" - }, - { - "@id": "http://www.opengis.net/def/docs/01-035" - }, - { - "@id": "http://www.opengis.net/def/docs/00-117" - }, - { - "@id": "http://www.opengis.net/def/docs/04-088" - }, - { - "@id": "http://www.opengis.net/def/docs/01-042" - }, - { - "@id": "http://www.opengis.net/def/docs/01-004" - }, - { - "@id": "http://www.opengis.net/def/docs/05-036" - }, - { - "@id": "http://www.opengis.net/def/docs/99-104" - }, - { - "@id": "http://www.opengis.net/def/docs/03-062r1" - }, - { - "@id": "http://www.opengis.net/def/docs/04-086" - }, - { - "@id": "http://www.opengis.net/def/docs/03-061" - }, - { - "@id": "http://www.opengis.net/def/docs/01-037" - }, - { - "@id": "http://www.opengis.net/def/docs/03-055r1" - }, - { - "@id": "http://www.opengis.net/def/docs/04-085" - }, - { - "@id": "http://www.opengis.net/def/docs/06-010r6" - }, - { - "@id": "http://www.opengis.net/def/docs/04-087" - }, - { - "@id": "http://www.opengis.net/def/docs/99-114" - }, - { - "@id": "http://www.opengis.net/def/docs/01-026r1" + "@value": "GeoAPI 3.0 Implementation Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-066r1", + "@id": "http://www.opengis.net/def/docs/10-091r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-04" + "@value": "2011-04-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Ben Domenico" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/primer" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -26707,27 +26224,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/12-128r17/18-066r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=43733" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Release Notes for OGC GeoPackage Encoding Standard v1.3.0" + "@value": "CF-netCDF Core and Extensions Primer" }, { "@language": "en", - "@value": "18-066r1" + "@value": "10-091r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/primer" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the set of revision notes for the existing GeoPackage version 1.3.0 (OGC 12-128r17) and does not modify that standard.\r\n\r\nThis document was approved by the OGC membership on 2020-11-26. As a result of the OGC Standards Working Group (SWG) process, there were a number of edits and enhancements made to this standard. This document provides the details of those edits, deficiency corrections, and enhancements. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility." + "@value": "This OGC primer provides an overview of the OGC CF-netCDF standards suite by describ-ing the CF-netCDF core and extensions. The CF-netCDF standard defines how to encode digital geospatial information representing space/time-varying phenomena" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -26738,35 +26255,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-066r1" + "@value": "10-091r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Release Notes for OGC GeoPackage Encoding Standard v1.3.0" + "@value": "CF-netCDF Core and Extensions Primer" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-084r1", + "@id": "http://www.opengis.net/def/docs/08-068r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-04-21" + "@value": "2009-03-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Y. Coene, U. Voges, O. Barois" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -26776,27 +26293,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/17-084r1/17-084r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=32319" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "EO Collection GeoJSON(-LD) Encoding" + "@value": "Web Coverage Processing Service (WCPS) Language Interface Standard" }, { "@language": "en", - "@value": "17-084r1" + "@value": "08-068r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "JavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. GeoJSON [NR2] is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. This OGC Best Practice describes a GeoJSON [NR2] and JSON-LD [NR13] encoding for Earth Observation (EO) metadata for collections (dataset series). This standard can be applied to encode metadata based on the OGC 11-035r1 [OR20] or ISO19139 [OR27], ISO19139-2 [OR28] specifications, or as an encoding of the Unified Metadata Model for Collections (UMM-C) conceptual model [OR2].\r\n\r\nThe GeoJSON encoding defined in this document is defined as a compaction1 through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF/XML [OR11] and RDF Turtle [OR12].\r\n\r\nThis document makes no assumptions as to the “service” interfaces through which the metadata are accessed and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful Architecture.\r\n\r\nGeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features.\r\n\r\nJSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR7] which allows validation of instances against these schemas." + "@value": "The OGC® Web Coverage Processing Service (WCPS) defines a protocol-independent language for the extraction, processing, and analysis of multi-dimensional coverages representing sensor, image, or statistics data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -26807,35 +26324,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-084r1" + "@value": "08-068r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "EO Collection GeoJSON(-LD) Encoding" + "@value": "OpenGIS Web Coverage Processing Service (WCPS) Language Interface Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-074", + "@id": "http://www.opengis.net/def/docs/09-015", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-09-08" + "@value": "2009-09-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Marwa Mabrouk" + "@value": "Craig Bruce" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -26845,27 +26362,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=22122" + "@id": "https://portal.ogc.org/files/?artifact_id=33516" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Location Service (OpenLS) Implementation Specification: Core Services" + "@value": "OWS-6 Styled Layer Descriptor (SLD) Changes ER" }, { "@language": "en", - "@value": "07-074" + "@value": "09-015" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OpenGIS Interface Standard defines OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform." + "@value": "This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the extension of the OGC Styled Layer Descriptor (SLD) symbology format for improved capability and harmonization with ISO 19117 symbology, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -26876,35 +26393,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-074" + "@value": "09-015" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Location Service (OpenLS) Implementation Specification: Core Services" + "@value": "OWS-6 Styled Layer Descriptor (SLD) Changes ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-089r1", + "@id": "http://www.opengis.net/def/docs/07-061", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-11-23" + "@value": "2008-02-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Daniel Tagesson" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -26914,27 +26431,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46228" + "@id": "https://portal.ogc.org/files/?artifact_id=26765" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-8 Engineering Report - Guidelines for International Civil Aviation Organization (ICAO) portrayal using SLD/SE" + "@value": "Revision Notes for OpenGIS® Implementation Specification: Geographic information - Geography Markup Language Version 3.2.1" }, { "@language": "en", - "@value": "11-089r1" + "@value": "07-061" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document gives guidelines to portrayal of AIXM according to ICAO aviation symbology using SLD/SE. " + "@value": "This document provides revision notes for version 3.2.1 of the OpenGIS® Implementation Specification Geographic information – Geography Markup Language (GML)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -26945,35 +26462,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-089r1" + "@value": "07-061" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 Engineering Report - Guidelines for International Civil Aviation Organization (ICAO) portrayal using SLD/SE" + "@value": "Revision Notes for OpenGIS® Implementation Specification: Geographic information - Geography Markup Language Version 3.2.1" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-087", + "@id": "http://www.opengis.net/def/docs/11-039r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-26" + "@value": "2014-02-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Leonard Daly, Scott Serich" + "@value": "Irina Dornblut, Rob Atkinson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -26983,27 +26500,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-087.html" + "@id": "https://portal.ogc.org/files/?artifact_id=55157" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-087" + "@value": "11-039r3" }, { "@language": "en", - "@value": "Interoperable Simulation and Gaming Sprint Engineering Report" + "@value": "HY_Features: a Common Hydrologic Feature Model" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Interoperable Simulation and Gaming Sprint advanced the use of relevant OGC and Khronos standards in the modeling and simulation community through practical exercise and testing of the GeoVolumes API draft specification produced by the 3D Data Container and Tiles API Pilot. Of particular interest was the handling and integration of glTF models coming from multiple sources, but the sprint also examined the specification’s implementability, consistency, completeness, and maturity." + "@value": "Common semantics support the reference of features to the concept they represent and the integration of data proceed using the semantic framework such mappings provide. However there is no standard conceptual model for hydrologic feature identification. Different models of hydrologic processes, and different scales of detail, lead to a variety of information models to describe these features, and to different and mostly incompatible sets of feature identifiers. \r\nThis document describes requirements and a proposed design for a domain model of hydrologic features as a set of interrelated Application Schemas using the ISO 19109 General Feature Model, \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -27014,35 +26531,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-087" + "@value": "11-039r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Interoperable Simulation and Gaming Sprint Engineering Report" + "@value": "OGC HY_Features: a Common Hydrologic Feature Model" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-088r2", + "@id": "http://www.opengis.net/def/docs/08-167r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-07-07" + "@value": "2009-07-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Terry Idol" + "@value": "Patrick Maué" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -27052,27 +26569,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-088r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=34916" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-088r2" + "@value": "08-167r1" }, { "@language": "en", - "@value": "Vector Tiles Pilot 2: Summary Engineering Report" + "@value": "Semantic annotations in OGC standards" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) provides a summary of the research and findings from Phase 2 of the OGC Vector Tiles Pilot (VTP2). The goal of VTP2 was to deliver a consistent, interoperable online/offline architecture for vector tiles based on feature and tile servers, as well as GeoPackage. All Application Programming Interface (API) implementations and service types deployed in the pilot were implemented to support the prototype vector tile metadata model and filtering language. These were two essential work items of VTP2. The feature and tile servers included implementations of the OGC API – Features standard and the draft OGC API – Tiles specification. The feature and tile servers provided support for a variety of Coordinate Reference Systems (CRS). This ER provides an overview of each of the components, their implementation decisions and the challenges faced.\r\n\r\nThe VTP2 participants intend to use the results of the work in VTP2 to inform the development of OGC APIs, GeoPackage, and web service standards to enable consistent use both online and offline, particularly in DDIL environments. Such consistent use of tiled feature data online and offline will improve interoperability and usability of geospatial applications. Therefore, the value of the VTP2 work to organizations is expected to be in the efficiencies and productivity that comes from greater interoperability and usability." + "@value": "Annotation of Web Services or data compliant to OGC standards refers to the task of attaching meaningful descriptions to the service and the served geospatial data or processes. In this discussion paper we try to extend the expressiveness of such annotations by including more sophisticated (semantic) descriptions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -27083,35 +26600,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-088r2" + "@value": "08-167r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Vector Tiles Pilot 2: Summary Engineering Report" + "@value": "Semantic annotations in OGC standards" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-129", + "@id": "http://www.opengis.net/def/docs/12-157", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-03-31" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis, Rob Atkinson" + "@value": "Joan Masó" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -27121,27 +26638,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=70328" + "@id": "https://portal.ogc.org/files/?artifact_id=52757" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Standardized Information Models to Optimize Exchange, Reusability and Comparability of Citizen Science Data (SWE4CS)" + "@value": "12-157" }, { "@language": "en", - "@value": "16-129" + "@value": "OWS-9 Engineering Report - OWS Innovations - Map Tiling Methods Harmonization" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This discussion paper describes a data model for the standardized exchange of citizen science sampling data. To do that it applies the Sensor Web Enablement (SWE) to Citizen Science (SWE4CS). In particular, exposes how Observations and Measurements (O&M) can be used to model the data of the Citizen Science project, in a way that can be retrieved using Sensor Observing System (SOS).This discussion paper is a result of the research project Citizen Observatory Web (COBWEB). COBWEB is supported by the European Commission through grant agreement 308513" + "@value": "This engineering report proposes a profile for WMTS that limits the flexibility or the standard and mimics what some other tile initiatives are doing. It also proposes some improvements in WMTS to accommodate the need for requesting several tiles of a region at different scales that has been identified by the GeoPackage team. These recommendations help to better harmonize OSGeo tile standards and mass-market technologies." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -27152,311 +26669,327 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-129" + "@value": "12-157" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Standardized Information Models to Optimize Exchange, Reusability and Comparability of Citizen Science Data (SWE4CS)" + "@value": "OGC® OWS-9 Engineering Report - OWS Innovations - Map Tiling Methods Harmonization" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-035r1", + "@id": "http://www.opengis.net/def/doc-type/bp/collection", "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" + "http://www.w3.org/2004/02/skos/core#Collection" ], - "http://purl.org/dc/terms/created": [ + "http://www.w3.org/2000/01/rdf-schema#label": [ { - "@type": "xsd:date", - "@value": "2022-03-31" + "@value": "Documents of type Best Practices Document" } ], - "http://purl.org/dc/terms/creator": [ + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Ronald Tse, Nick Nicholas" + "@value": "Documents of type Best Practices Document" } ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/docs" } ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "http://www.w3.org/2004/02/skos/core#member": [ { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/16-004r5" + }, { - "@id": "https://docs.ogc.org/per/21-035r1.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/16-009r3" + }, { - "@language": "en", - "@value": "OGC Testbed-17: Model-Driven Standards Engineering Report" + "@id": "http://www.opengis.net/def/docs/15-005r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-018r2" + }, + { + "@id": "http://www.opengis.net/def/docs/21-007" + }, + { + "@id": "http://www.opengis.net/def/docs/17-084r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-125r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-035r2" + }, + { + "@id": "http://www.opengis.net/def/docs/20-089r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-107r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-003r4" + }, + { + "@id": "http://www.opengis.net/def/docs/12-111r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-102r3a" + }, + { + "@id": "http://www.opengis.net/def/docs/16-003r2" + }, + { + "@id": "http://www.opengis.net/def/docs/20-095" + }, + { + "@id": "http://www.opengis.net/def/docs/15-120r6" + }, + { + "@id": "http://www.opengis.net/def/docs/07-097" + }, + { + "@id": "http://www.opengis.net/def/docs/16-086r3" + }, + { + "@id": "http://www.opengis.net/def/docs/10-189r2" + }, + { + "@id": "http://www.opengis.net/def/docs/07-118r9" + }, + { + "@id": "http://www.opengis.net/def/docs/16-011r5" + }, + { + "@id": "http://www.opengis.net/def/docs/10-003r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-139r3" + }, + { + "@id": "http://www.opengis.net/def/docs/11-122r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-028r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-032r2" + }, + { + "@id": "http://www.opengis.net/def/docs/14-003" + }, + { + "@id": "http://www.opengis.net/def/docs/16-009r5" + }, + { + "@id": "http://www.opengis.net/def/docs/16-004r4" + }, + { + "@id": "http://www.opengis.net/def/docs/09-102" + }, + { + "@id": "http://www.opengis.net/def/docs/15-120r5" + }, + { + "@id": "http://www.opengis.net/def/docs/02-007r4" + }, + { + "@id": "http://www.opengis.net/def/docs/15-003" + }, + { + "@id": "http://www.opengis.net/def/docs/07-092r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-010r5" + }, + { + "@id": "http://www.opengis.net/def/docs/07-118r8" + }, + { + "@id": "http://www.opengis.net/def/docs/06-095" + }, + { + "@id": "http://www.opengis.net/def/docs/05-042r2" + }, + { + "@id": "http://www.opengis.net/def/docs/16-005r3" + }, + { + "@id": "http://www.opengis.net/def/docs/21-068" + }, + { + "@id": "http://www.opengis.net/def/docs/08-167r2" + }, + { + "@id": "http://www.opengis.net/def/docs/13-015" + }, + { + "@id": "http://www.opengis.net/def/docs/16-006r5" + }, + { + "@id": "http://www.opengis.net/def/docs/09-102r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-009r4" + }, + { + "@id": "http://www.opengis.net/def/docs/16-003r3" + }, + { + "@id": "http://www.opengis.net/def/docs/15-037" }, { - "@language": "en", - "@value": "21-035r1" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/13-042" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/12-066" + }, { - "@value": "This OGC Testbed 17 Engineering Report is deliverable D022 of the OGC Testbed 17 initiative performed under the OGC Innovation Program, incorporating the D022, D143 and D144 tasks that have produced Model Driven Architecture (MDA) tools.\r\n\r\nThis ER:\r\n\r\ndetails state-of-the-art analyses of existing MDA tools with their capabilities and limits; and\r\n\r\nprovides clear recommendations on how model-driven design can be fully exploited in the context of rich data model and API design efforts.\r\n\r\n" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/16-070r4" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/16-114r3" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-035r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/19-066" + }, { - "@language": "en", - "@value": "OGC Testbed-17: Model-Driven Standards Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/18-041r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/11-169r1" + }, { - "@type": "xsd:date", - "@value": "2018-10-09" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/14-110r2" + }, { - "@value": "Gobe Hobona, Bart De Lathouwer" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/15-005r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/dp" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/15-107" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/07-063r1" + }, { - "@id": "https://docs.ogc.org/dp/18-041r1/18-041r1.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/16-010r4" + }, { - "@language": "en", - "@value": "18-041r1" + "@id": "http://www.opengis.net/def/docs/15-004" }, { - "@language": "en", - "@value": "Geospatial Standardization of Distributed Ledger Technologies" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/16-004r3" + }, { - "@id": "http://www.opengis.net/def/doc-type/dp" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/06-142r1" + }, { - "@value": "This discussion paper is organized as follows.\r\n\r\nBackground: This section introduces DLT and blockchain, as well as the structure of blocks.\r\n\r\nCase Studies: This section presents an overview of example projects that use or are studying blockchain within a geospatial context.\r\n\r\nCurrent Standardization Initiatives: This section presents an overview of a selection of standardization initiatives involving blockchain and geospatial data." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/13-043" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/15-120r4" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-041r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/06-129r1" + }, { - "@language": "en", - "@value": "Geospatial Standardization of Distributed Ledger Technologies" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/16-105r2", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/13-039" + }, { - "@type": "xsd:date", - "@value": "2017-08-16" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/16-006r4" + }, { - "@value": "Peter Axelsson, Lars Wikström" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/16-006r3" + }, { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/03-002r9" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/06-021r4" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=75122" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/21-070" + }, { - "@language": "en", - "@value": "InfraGML 1.0: Part 5 - Railways - Encoding Standard" + "@id": "http://www.opengis.net/def/docs/16-011r3" }, { - "@language": "en", - "@value": "16-105r2" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/16-070r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/14-106" + }, { - "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 5 addresses the Railway Requirements Class from LandInfra." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/06-188r1" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/16-070r3" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-105r2" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/16-005r2" + }, { - "@language": "en", - "@value": "OGC InfraGML 1.0: Part 5 - Railways - Encoding Standard" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/18-025", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/11-035r1" + }, { - "@type": "xsd:date", - "@value": "2019-03-07" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/14-004r1" + }, { - "@value": "Jérôme Jacovella-St-Louis" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/16-011r4" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/09-153r1" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/06-126r2" + }, { - "@id": "https://docs.ogc.org/per/18-025.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/16-140r1" + }, { - "@language": "en", - "@value": " CityGML and AR Engineering Report" + "@id": "http://www.opengis.net/def/docs/16-010r3" }, { - "@language": "en", - "@value": "18-025" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/14-012r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/11-135r2" + }, { - "@value": "This OGC Testbed-14 Engineering Report (ER) describes the results of the Augmented Reality (AR) work performed in the Testbed-14 CityGML and Augmented Reality work package which was part of the Next Generation Services thread.\r\n\r\nBy integrating information available from urban models within a view of the real world through a mobile device, this testbed activity explored the possibilities offered by AR in a geospatial context. The ER additionally discusses the approach used to bring in these urban models from various data sources. The experiments also covered to some extent Virtual Reality (VR) where any city can be explored freely from a computer display or potentially within a VR headset.\r\n\r\nA continuation of these experiments would have looked at a combination of Augmented and Virtual Reality (Mixed Reality). The portrayal of AR and three-dimensional (3D) content through extending a common conceptual model to style classic geospatial features (as explored in the Testbed-14 Portrayal work) is also touched upon. The efficient transmission of 3D content is also a subject of this document through the use of a simple 3D transmission format developed during the initiative.\r\n\r\nThis ER provides many insights that showcase what is now made possible by the combination of AR, VR and integrated urban models.\r\n\r\nThe testbed work shines light on the benefits of applying a common portrayal approach to AR, bridging the gap between AR applications and traditional Geographic Information Systems and services.\r\n\r\nThe ER introduces a new, simple approach and conceptual model for transmitting 3D geospatial content which could be the basis to define simple profiles for the I3S and 3D Tiles community standards. It could also inform enhancements to the 3D Portrayal Service (3DPS) and/or next generation services (e.g., WFS 3.0) for delivering 3D contents in a format agnostic manner.\r\n\r\nFinally, the ER covers methods to bring in different types of geospatial content from various sources for integration into AR applications.\r\n\r\nDuring Testbed-14, the participants demonstrated AR experiences with geospatial datasets providing integrated views of urban spaces. Two clients and two services were shown to be interoperable, streaming AR content through a simple 3D transmission format, leveraging either GeoJSON or GNOSIS Map Tiles, as well as E3D 3D model specifications.\r\n\r\nThe feasibility of extending a classic portrayal conceptual model for AR was also shown. In order to serve them to the clients in the supported transmission formats, geospatial data sets of various types and in various formats were successfully imported for consumption by the services." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/06-028r3" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/16-005r4" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-025" + "@id": "http://www.opengis.net/def/docs/17-011r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@language": "en", - "@value": "OGC Testbed-14: CityGML and AR Engineering Report" + "@value": "Documents of type Best Practices Document" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-022r1", + "@id": "http://www.opengis.net/def/docs/07-041r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-09-23" + "@value": "2007-05-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Ilya Zaslavsky, David Valentine, Tim Whiteaker" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -27466,27 +26999,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/22-022r1/22-022r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=21743" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC SensorThings API Extension: STAplus 1.0" + "@value": "07-041r1" }, { "@language": "en", - "@value": "22-022r1" + "@value": "CUAHSI WaterML" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC SensorThings API Extension: STAplus 1.0 Standard specifies a backwards-compatible extension to the OGC Standard SensorThings API Part 1: Sensing and Sensing 1.1 data model.\r\n\r\nThe motivation for specifying this STAplus extension is based on requirements from the Citizen Science community.\r\n\r\nThe dominant use for the OGC SensorThings API data model and API can be coined with the use case “single authority provides sensor readings to consumers.” However, in Citizen Science there are many contributors (citizens) who – together – create the big picture with their observations.\r\n\r\nThe STAplus extension is designed to support a model in which observations are owned by different users. This results in requirements for the ownership concept. In addition to the ownership, users may express a license for ensuring proper re-use of their observations. The STAplus extension also supports expressing explicit relations between observations as well as between observations and external resources. Relations can enrich observations to enable future extensions supporting Linked Data, RDF and SPARQL. Observation group(s) allow the grouping of observations that belong together.\r\n\r\nThe STAplus extension is believed to be an important contribution towards the realization of the FAIR principles as STAplus strengthens the “I” (Interoperability) through a common data model and API as well as the “R” (Re-usability) by allowing expressing standards-based queries that may consider licensing conditions which is relevant for reuse of other users’ observations.\r\n\r\nThe STAplus Data Model and Business Logic also enriches existing deployments as the extension can be seamlessly added and thereby offers new capabilities to create and manage the “big picture” with multi-user capabilities.\r\n\r\nThe key work for crafting this OGC Standard was undertaken in the Co-designed Citizen Observatories Services for the EOS-Cloud (Cos4Cloud) project, which received funding from the European Union’s Horizon 2020 research and innovation program and the Enhancing Citizen Observatories for healthy, sustainable, resilient and inclusive cities (CitiObs) project, which received funding from the European Union’s Horizon Europe research and innovation program. Testing of this extension was done with data from the Framework biodiversity project, which received funding from the European Union’s Horizon 2020 research and innovation program." + "@value": "This document describes the initial version of the WaterML messaging schema as implemented in version 1 of WaterOneFlow web services. It also lays out strategies for harmonizing WaterML with OGC specifications, the Observations and Measurement specification in particular." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -27497,35 +27030,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-022r1" + "@value": "07-041r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC SensorThings API Extension: STAplus 1.0" + "@value": "CUAHSI WaterML" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-115", + "@id": "http://www.opengis.net/def/docs/06-121r9", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-03-28" + "@value": "2010-04-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joe Lewis" + "@value": "Arliss Whiteside, Jim Greenwood " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -27535,27 +27068,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12899" + "@id": "https://portal.ogc.org/files/?artifact_id=38867" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-115" + "@value": "06-121r9" }, { "@language": "en", - "@value": "Geo Video Web Service" + "@value": "Web Service Common Implementation Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A GeoVideo Web Service (GVS) is a web service that facilitates the viewing of live and/or archived feeds from video cameras. The feeds may be composed of:\r\n- A video stream\r\n- Textual data in a caption stream (e.g. GPS data, camera states and characteristics, custom XML data, such as SensorMLTML)\r\n- A combination of a video stream and associated textual data\r\nThe video streams of the feed may be viewed in the Windows Media Player. The textual data is extracted through scripting events that are generated as the caption stream is processed and displayed by the Windows Media Player." + "@value": "This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Standards. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Standard must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -27566,35 +27099,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-115" + "@value": "06-121r9" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geo Video Web Service" + "@value": "OGC Web Service Common Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-108r2", + "@id": "http://www.opengis.net/def/docs/16-067r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-03-26" + "@value": "2017-05-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman" + "@value": "Daniel Balog, Robin Houtmeyers" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -27604,27 +27137,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=894" + "@id": "https://docs.ogc.org/per/16-067r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 08 - Relationships Between Features" + "@value": "Testbed-12 Vector Tiling Implementation Engineering Report" }, { "@language": "en", - "@value": "99-108r2" + "@value": "16-067r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Topic introduces an abstraction for the relationships between entities in the real world. This abstraction is modeled as relationships between the features introduced in Topic 5." + "@value": "This OGC Testbed 12 Engineering Report (ER) discusses the topic of implementing vector tiles in an OGC GeoPackage. This report builds on the general topic of vector tiling discussed in OGC Testbed 12 Engineering Report [OGC 16-068r4].\r\n\r\nSince its public release in 2012, OGC GeoPackage has been getting increasingly popular within the geospatial industry for a variety of use cases, such as a means to package geospatial data for use on a mobile device and as a means to exchange geospatial data between two systems.\r\n\r\nThe OGC GeoPackage standard currently specifies requirements (rules) for storing raster tiles and vector (simple) features. This Engineering Report proposes an extension to the supported data types by introducing an implementation for vector tiles.\r\n\r\nWhile tiling and the use of multiple levels of details are a proven technique for accessing and visualizing raster data, it is less commonly applied for vector data. This is due to the increased complexity compared to raster tiling and lack of standardization on the topic. Yet, implementing vector tiles can provide the same benefits as for using raster tiles.\r\n\r\nServices can easily cache tiles and return them instantly upon request, without the need for any additional pre/post processing. Consequently, clients can get tiles very fast, ensuring fast and responsive maps.\r\n\r\nUsing tiled, multileveled data representations, clients can always access the data most suitable for their current map location and scale. This avoids the need to load too much data, which can cause excessive memory usage and reduce overall performance.\r\n\r\nThe goal is to enable systems to use OGC GeoPackage as a means to store and access vector tiles in an efficient way, similar to raster tiles.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -27635,38 +27168,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-108r2" + "@value": "16-067r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 8 - Relationships Between Features" + "@value": "Testbed-12 Vector Tiling Implementation Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-058", + "@id": "http://www.opengis.net/def/docs/09-084r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-05-17" + "@value": "2009-10-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Vretanos" + "@value": "Jo Walsh, Pedro Gonçalves, Andrew Turner" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-sap" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -27676,34 +27206,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7176" + "@id": "https://portal.ogc.org/files/?artifact_id=35983" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Feature Service (Transactional)" - }, - { - "@language": "en", - "@value": "02-058" + "@value": "OpenSearch Geospatial Extensions Draft Implementation Standard" }, { "@language": "en", - "@value": "Web Feature Service" + "@value": "09-084r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-sap" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The purpose of the Web Feature Server Interface Specification (WFS) is to describe data manipulation operations on OpenGIS" + "@value": "The OpenSearch specification originates in a community effort built around Amazon's A9.com. It was intended to allow syndication of search results that could then be aggregated by one large index. The OpenSearch specification is made available under the Creative Commons Attribution-Sharealike 2.5 license. In addition, the OASIS Search Web Services group is publishing an Abstract Protocol Definition of the interface or “binding”, which coincides with the community specification published at http://opensearch.org. In 2007, Andrew Turner proposed a set of geospatial extensions through OpenSearch.org." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -27714,39 +27237,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-058" + "@value": "09-084r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Feature Service (Transactional)" - }, - { - "@language": "en", - "@value": "Web Feature Service" + "@value": "OpenSearch Geospatial Extensions Draft Implementation Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-097", + "@id": "http://www.opengis.net/def/docs/09-000", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-10-05" + "@value": "2011-03-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas Uslander (Ed.)" + "@value": "Ingo Simonis, Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -27756,27 +27275,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=23286" + "@id": "https://portal.ogc.org/files/?artifact_id=38478" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Reference Model for the ORCHESTRA Architecture" + "@value": "Sensor Planning Service Implementation Standard" }, { "@language": "en", - "@value": "07-097" + "@value": "09-000" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It is an extension of the OGC Reference Model and contains a specification framework for the design of geospatial service-oriented architectures and service networks. The RM-OA comprises the generic aspects of service-oriented architectures, i.e., those aspects that are independent of the risk management domain and thus applicable to other application domains. " + "@value": "The OpenGIS® Sensor Planning Service Interface Standard (SPS) defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor planning request; to submit and reserve/commit such a request; to inquire about the status of such a request; to update or cancel such a request; and to request information about other OGC Web services that provide access to the data collected by the requested task. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -27787,157 +27306,29 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-097" + "@value": "09-000" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Reference Model for the ORCHESTRA Architecture" - } - ] - }, - { - "@id": "_:na0b8f31574254c9abc9f1c931387ca28b1", - "@type": [ - "http://www.w3.org/ns/prov#Activity" - ], - "http://www.w3.org/ns/prov#endedAtTime": [ - { - "@type": "http://www.w3.org/2001/XMLSchema#dateTime", - "@value": "2024-07-30T10:34:05.928276" - } - ], - "http://www.w3.org/ns/prov#startedAtTime": [ - { - "@type": "http://www.w3.org/2001/XMLSchema#dateTime", - "@value": "2024-07-30T10:34:04.883138" - } - ], - "http://www.w3.org/ns/prov#used": [ - { - "@id": "_:na0b8f31574254c9abc9f1c931387ca28b2" - } - ], - "http://www.w3.org/ns/prov#wasAssociatedWith": [ - { - "@id": "_:na0b8f31574254c9abc9f1c931387ca28b3" - } - ], - "http://www.w3.org/ns/prov#wasInformedBy": [ - { - "@id": "_:na0b8f31574254c9abc9f1c931387ca28b4" - } - ] - }, - { - "@id": "_:na0b8f31574254c9abc9f1c931387ca28b2", - "@type": [ - "http://www.w3.org/ns/prov#Entity" - ], - "http://purl.org/dc/terms/format": [ - { - "@value": "application/json" - } - ], - "http://purl.org/dc/terms/hasVersion": [ - { - "@value": "git:3852709b7dabb312dcd088bac852ed1baee222e3" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ - { - "@id": "file:///home/runner/work/NamingAuthority/NamingAuthority/definitions/docs/docs.json" - } - ] - }, - { - "@id": "_:na0b8f31574254c9abc9f1c931387ca28b3", - "@type": [ - "https://schema.org/SoftwareApplication", - "http://www.w3.org/ns/prov#Agent" - ], - "http://purl.org/dc/terms/hasVersion": [ - { - "@value": "0.3.49" - } - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "OGC-NA tools" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ - { - "@id": "https://github.com/opengeospatial/ogc-na-tools" - } - ] - }, - { - "@id": "_:na0b8f31574254c9abc9f1c931387ca28b4", - "http://purl.org/dc/terms/identifier": [ - { - "@value": "3f4259fb-9ac8-43cf-95e7-9e11bf5969d9" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/is-draft", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/21-056r10" + "@value": "OGC® Sensor Planning Service Implementation Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-011", + "@id": "http://www.opengis.net/def/doc-type/ug/collection", "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ - { - "@type": "xsd:date", - "@value": "2007-12-28" - } - ], - "http://purl.org/dc/terms/creator": [ - { - "@value": "OGC" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ - { - "@id": "http://www.opengis.net/def/doc-type/as" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ - { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ - { - "@id": "https://portal.ogc.org/files/?artifact_id=19820" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ - { - "@language": "en", - "@value": "Topic 06 - Schema for coverage geometry and functions" - }, - { - "@language": "en", - "@value": "07-011" - } + "http://www.w3.org/2004/02/skos/core#Collection" ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "http://www.w3.org/2000/01/rdf-schema#label": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@value": "Documents of type User Guide" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This International Standard defines a conceptual schema for the spatial characteristics of coverages. Coverages support mapping from a spatial, temporal or spatiotemporal domain to feature attribute values where feature attribute types are common to all geographic positions within the domain. A coverage domain consists of a collection of direct positions in a coordinate space that may be defined in terms of up to three spatial dimensions as well as a temporal dimension." + "@value": "Documents of type User Guide" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -27945,38 +27336,48 @@ "@id": "http://www.opengis.net/def/docs" } ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "http://www.w3.org/2004/02/skos/core#member": [ { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-011" + "@id": "http://www.opengis.net/def/docs/20-071" + }, + { + "@id": "http://www.opengis.net/def/docs/20-066" + }, + { + "@id": "http://www.opengis.net/def/docs/21-075" + }, + { + "@id": "http://www.opengis.net/def/docs/22-000" + }, + { + "@id": "http://www.opengis.net/def/docs/21-074" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@language": "en", - "@value": "Topic 6 - Schema for coverage geometry and functions" + "@value": "Documents of type User Guide" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-070r2", + "@id": "http://www.opengis.net/def/docs/12-105", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-02-23" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Joan Masó" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -27986,27 +27387,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=72715" + "@id": "https://portal.ogc.org/files/?artifact_id=52018" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-070r2" + "@value": "OWS-9 - OWS Context evaluation IP Engineering Report" }, { "@language": "en", - "@value": "Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage" + "@value": "12-105" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features." + "@value": "This OGC Engineering Report describes the results of the OWS-9 IP on OWS Context 1.0. OWS Context is a draft OGC candidate standard. The OWS Context activity tested and evaluated the relative benefits of different encoding methods prior to finalization of the candidate standard. OWS Context has been proposed with an Atom encoding, a JSON encoding and an HTML5 encoding. The encoding requirement seeks to understand the level of mass-market acceptance of these different encoding options and their ability to support mash-ups. Each encoding should be evaluated, including examples and recommendations to move forward. Recommendations should enable the OWS Context capability for OGC services while remaining cognizant of implementations using mass-market technologies." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28017,35 +27418,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-070r2" + "@value": "12-105" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage" + "@value": "OGC® OWS-9 - OWS Context evaluation IP Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-134", + "@id": "http://www.opengis.net/def/docs/16-019r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-11-30" + "@value": "2017-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Keith Ryden" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28055,27 +27456,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13228" + "@id": "https://docs.ogc.org/wp/16-019r4/16-019r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option" + "@value": "Open Geospatial APIs - White Paper" }, { "@language": "en", - "@value": "05-134" + "@value": "16-019r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This part of OpenGIS" + "@value": "OGC defines interfaces that enable interoperability of geospatial applications. API’s are a popular method to implement interfaces for accessing spatial data. This White Paper provides a discussion of Application Programming Interfaces (APIs) to support discussion of possible actions in the Open Geospatial Consortium (OGC)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28086,35 +27487,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-134" + "@value": "16-019r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access -" + "@value": "OGC® Open Geospatial APIs - White Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-113r5", + "@id": "http://www.opengis.net/def/docs/14-073r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-19" + "@value": "2014-11-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "George Wilber, Johannes Echterhoff, Matt de Ris, Joshua Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28124,27 +27525,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/15-113r5" + "@id": "https://portal.ogc.org/files/60175" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure" + "@value": "14-073r1" }, { "@language": "en", - "@value": "15-113r5" + "@value": "Aircraft Access to SWIM (AAtS) Harmonization Architecture Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time." + "@value": "This OGC® document describes the Aircraft Access to SWIM (AAtS) harmonization \r\narchitecture developed by a team funded by the FAA and led by the Open Geospatial \r\nConsortium (OGC). " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28155,35 +27556,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-113r5" + "@value": "14-073r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure" + "@value": "OGC® Aircraft Access to SWIM (AAtS) Harmonization Architecture Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-047r3", + "@id": "http://www.opengis.net/def/docs/20-042", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-01-20" + "@value": "2020-10-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Martin Kyle, David Burggraf, Sean Forde, Ron Lake" + "@value": "Pedro Gonçalves" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28193,27 +27594,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13252" + "@id": "https://docs.ogc.org/per/20-042.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-047r3" + "@value": "20-042" }, { "@language": "en", - "@value": "GML in JPEG 2000 for Geographic Imagery Encoding Specification" + "@value": "OGC Earth Observations Applications Pilot: Terradue Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® GML in JPEG 2000 for Geographic Imagery Encoding Standard defines the means by which the OpenGIS® Geography Markup Language (GML) Standard http://www.opengeospatial.org/standards/gml is used within JPEG 2000 http://www.jpeg.org/jpeg2000/ images for geographic imagery. The standard also provides packaging mechanisms for including GML within JPEG 2000 data files and specific GML application schemas to support the encoding of images within JPEG 2000 data files. JPEG 2000 is a wavelet-based image compression standard that provides the ability to include XML data for description of the image within the JPEG 2000 data file. \r\nSee also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .\r\n" + "@value": "This OGC Engineering Report (ER) documents the findings and experiences resulting from Terradue Activities on the OGC Earth Observation Applications Pilot. More specifically, this ER provides a way forward for the implementation of the applications to the data paradigm in the context of Earth Observation (EO) satellite data processing and Cloud-based platforms to facilitate and standardize the access to Earth observation data and information." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28224,35 +27625,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-047r3" + "@value": "20-042" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS GML in JPEG 2000 for Geographic Imagery Encoding Specification" + "@value": "OGC Earth Observations Applications Pilot: Terradue Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-086r6", + "@id": "http://www.opengis.net/def/docs/16-050", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-07-27" + "@value": "2017-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mark Burgoyne, David Blodgett, Charles Heazel, Chris Little" + "@value": "Joan Masó and Alaitz Zabala" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28262,27 +27663,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/19-086r6/19-086r6.html" + "@id": "https://docs.ogc.org/per/16-050.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC API - Environmental Data Retrieval Standard" + "@value": "Testbed-12 Imagery Quality and Accuracy Engineering Report" }, { "@language": "en", - "@value": "19-086r6" + "@value": "16-050" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC API — Environmental Data Retrieval (EDR) standard provides a family of lightweight query interfaces to access spatiotemporal data resources by requesting data at a Position, within an Area, along a Trajectory or through a Corridor. A spatio-temporal data resource is a collection of spatio-temporal data that can be sampled using the EDR query pattern geometries. These patterns are described in the section describing the Core Requirements Class.\r\n\r\nThe goals of the EDR Application Programming Interface (API) that is specified by this standard are to:\r\n\r\nMake it easier to access a wide range of data through a uniform, well-defined simple Web interface;\r\n\r\nTo achieve data reduction to just the data needed by the user or client while hiding much of the data storage complexity.\r\n\r\nA major use case for the EDR API is to retrieve small subsets from large collections of environmental data, such as weather forecasts, though many other types of data can be accessed. The important aspect is that the requested data can be unambiguously specified by spatio-temporal coordinates.\r\n\r\nThe EDR API query patterns — Position, Area, Cube, Trajectory or Corridor — can be thought of as discrete sampling geometries, conceptually consistent with the feature of interest in the Sensor Observation Service (SOS) standard. A typical data resource accessed by an EDR API instance is a multidimensional dataset that could be accessed via an implementation of the Web Coverage Service (WCS) standard. In contrast to SOS and WCS, the EDR API is fully consistent with the patterns of the OGC API family of standards and aims to provide a single set of simple-to-use query patterns. Use cases for EDR range from real or virtual time-series observation retrievals, to sub-setting 4-dimensional data cubes along user-supplied sampling geometries. These query patterns do not attempt to satisfy the full scope of either SOS or WCS, but instead provide useful building blocks to enable the composition of APIs that satisfy a wide range of geospatial data use cases. By defining a small set of query patterns (and no requirement to implement all of them), the EDR API should help to simplify the design of systems (as they can be performance tuned for the supported queries) making it easier to build robust and scalable infrastructures.\r\n\r\nWith the OGC API family of standards, the OGC community has extended its suite of standards to include Resource Oriented Architectures and Web Application Programming Interfaces (APIs). These standards are based on a shared foundation, specified in OGC API-Common, which defines the resources and access paths that are supported by all OGC APIs. The resources are listed in Table 1. This document extends that foundation to define the EDR API." + "@value": "The scenario of rapidly growing geodata catalogues requires tools focused on facilitating users the choice of products. Having populated quality fields in metadata allows the users to rank and then select the best fit-for-purpose products. For example, decision-makers would be able to find quality and uncertainty measures to take the best decisions as well as to perform dataset intercomparison. In addition, it allows other components (such as visualization, discovery, or comparison tools) to be quality-aware and interoperable.\r\n\r\nThis ER deals with completeness, logical consistency, positional accuracy, temporal accuracy and thematic accuracy issues to improve quality description in the metadata for imagery. Based on ISO 19157, UncertML and QualityML standardized measures, this ER describes how to encode quality measures in order to allow datasets comparison. Moreover, description of pixel-level quality measures is also included. Finally, alternatives to communicate tile level quality as well as mosaic products quality are proposed." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28293,35 +27694,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-086r6" + "@value": "16-050" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Environmental Data Retrieval Standard" + "@value": "Testbed-12 Imagery Quality and Accuracy Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-092", + "@id": "http://www.opengis.net/def/docs/99-109r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-08-05" + "@value": "1999-03-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Graham, Carl Reed" + "@value": "Cliff Kottman, Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28331,27 +27732,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/20-092.html" + "@id": "https://portal.ogc.org/files/?artifact_id=896" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-092" + "@value": "Topic 9 - Accuracy" }, { "@language": "en", - "@value": "CDB X Conceptual Model with Prototyping Examples and Recommendations" + "@value": "99-109r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion Paper documents the results and recommendations of the rapid prototyping activities conducted during the 3D Geospatial Series Tech Sprint II - OGC CDB 2.0 (aka CDB X). This activity was performed in support of Special Operations Forces (SOF) Future Concepts. This effort hopes to accelerate evolution of the OGC CDB standard to meet the needs of planning, rehearsal, and Mission Command systems providing decision support to Special Operations Forces and enabling SOF tactical and operational advantage. OGC industry standards enable interoperability of geospatial data across systems and applications that SOF Operators and analysts use across warfighting functions.\r\n\r\nShort summary of CDB X goal: Meeting the requirements for tactical GEOINT that can be used across warfighting functions." + "@value": "Topic 9 has been combined into AS Topic 11" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28362,35 +27763,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-092" + "@value": "99-109r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CDB X Conceptual Model with Prototyping Examples and Recommendations" + "@value": "Topic 9 - Accuracy" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-047r3", + "@id": "http://www.opengis.net/def/docs/20-090", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-03-01" + "@value": "2021-01-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Gobe Hobona" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pol-nts" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28400,27 +27801,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41774" + "@id": "https://docs.ogc.org/per/20-090.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC-NA Name type specification - documents" + "@value": "OGC API – Maps Sprint 2020: Summary Engineering Report" }, { "@language": "en", - "@value": "09-047r3" + "@value": "20-090" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pol-nts" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies a rule for constructing OGC names that may be used for identifying documents and elements within a document." + "@value": "This OGC Engineering Report (ER) documents the results and recommendations from a code sprint that was held from 28 to 29 July 2020 to advance the development of the draft OGC API – Maps Standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application, or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The OGC API - Maps Sprint was an online virtual event. The sprint was sponsored by Ordnance Survey." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28431,35 +27832,46 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-047r3" + "@value": "20-090" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC-NA Name type specification - documents" + "@value": "OGC API – Maps Sprint 2020: Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-027r1", + "@id": "http://www.opengis.net/def/doc-type/ipr", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/02-019r1" + }, + { + "@id": "http://www.opengis.net/def/docs/02-028" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/21-037", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-01-18" + "@value": "2021-07-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Aleksandar Balaban" + "@value": "Josh Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28469,27 +27881,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64141" + "@id": "https://docs.ogc.org/dp/21-037.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 11 Digital Notice to Airmen (NOTAM) Validation and Enrichment Service Engineering Report" + "@value": "21-037" }, { "@language": "en", - "@value": "15-027r1" + "@value": "OGC Technical Paper on the Standards Landscape for Building Data" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) is a deliverable of the OGC Testbed 11. This ER describes the Digital Notice to Airmen (NOTAM) enrichment and validation services in the Testbed 11 Aviation thread, including:\r\n•\tA description of the architecture and architectural options.\r\n•\tAn overview of the implemented components and workflows followed by a short description of each component.\r\n•\tDocumentation of the issues, lessons learned as well as accomplishments and scenarios that were of general interest in the Aviation thread.\r\nMore detailed information on other specific aspects considered in OWS-11 Aviation may be found in the individual Aviation Engineering Reports.\r\n" + "@value": "Data about buildings and building structures play roles at scales from neighborhoods to nations in creating, protecting, regulating, and understanding the built environment. This report examines standards which may be useful in defining the structure and content of building data at a national scale, a national building layer. Standard models, schemas, and encodings may be especially useful for supporting an extensible building dataset with an efficient core definition, but the ability to encompass more detailed or specialized data as needed in as seamless and compatible a manner as possible. Standards compiled and described in this document range from generic geographic data encodings to models and specifications for specific building perspectives such as land parcel improvements, facility ownership, footprint / roofline extractions, residency affordances, envelope characteristics, and so on. They provide potential source material for a modular and multi-platform building layer definition which can be applied to a reasonably wide set of use cases. This definition may in turn be a standardization candidate for adoption by other national geographic data collections." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28500,35 +27912,43 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-027r1" + "@value": "21-037" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 11 Digital Notice to Airmen (NOTAM) Validation and Enrichment Service Engineering Report" + "@value": "OGC Technical Paper on the Standards Landscape for Building Data" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-032r2", + "@id": "http://www.opengis.net/def/doc-type/cp", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/18-095r7" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/07-045r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-26" + "@value": "2018-03-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Anneley McMillan, Sam Meek" + "@value": "Uwe Voges, Kristian Senkler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28538,27 +27958,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-032r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=77949" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-032r2" + "@value": "Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum" }, { "@language": "en", - "@value": "Testbed-13: Aviation Abstract Quality Model Engineering Report" + "@value": "07-045r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Engineering Report (ER) describes an Abstract Quality Model (AQM) for data in the aviation domain. Requirements for data quality in aviation are stringent, as the data is often used for safety critical purposes. The services considered are those that serve aeronautical information, flight information and weather forecasting. The model is built upon recognized standards of the International Organization for Standardization (ISO) with extensions and additions made according to the requirements of the domain. These requirements include an ability for the model to record information about the precision of measurements and an understanding of the timeliness of a piece of data, as information utility degrades with time. The result is an ISO compliant data quality model with the required extensions included." + "@value": "Catalogue services are the key technology for locating, managing and maintaining\r\ndistributed geo-resources (i.e. geospatial data, applications and services). With OGC\r\ncatalogue services, client applications are capable of searching for geo-resources in a\r\nstandardized way (i.e. through standardized interfaces and operations) and, ideally, they\r\nare based on a well-known information model, which includes spatial references and\r\nfurther descriptive (thematic) information that enables client applications to search for\r\ngeo-resources in very efficient ways.\r\nWhereas interfaces and operations of OGC catalogue services are well defined, it is left\r\nup to the developer of the system to define a specific information model which a\r\ncatalogue service instance provides. This includes, but is not limited to, the information\r\nwhich can be inserted in the catalog, supported query languages, available search terms,\r\nresponse/result sets, etc. This point is of major importance with respect to interoperability\r\nbetween different catalogue service instances.\r\nIn Europe, running catalogue instances result from work being done within different SDI\r\ninitiatives (e.g. SDI NRW Initiative1, Germany/Netherlands cross-border initiative, JRC\r\nEU Portal, EUROSTAT, Inspire, German SDI initiative). Members of these initiatives\r\nhave developed an ISO-based application profile for ISO19115 metadata for\r\ngeodata/geospatial applications and ISO19119-based metadata for tightly and looselycoupled\r\ngeospatial services. The foundations of this profile were the OGC catalogue\r\nspecification (1.1.1), the OGC Web Registry Server (WRS) 0.0.2, OGC Web Services\r\nStateless Catalogue Profile (StCS) 0.0.6 and ISO 19115/19119 for content description.\r\nOGC's catalogue revision working group (CS-RWG) has revised and integrated the\r\ncatalogue implementation specification v1.1.1 that have resulted in CS 2.0.2. One part of\r\nthis OGC specification comprises the definition of application profiles according to ISO\r\n19106 (Geographic information – Profiles). The overall goal of these profiles is to\r\nimprove interoperability between systems conforming to a specific profile. Experience\r\nhas shown that the need for application profiles results from the fact that in practice, there\r\nis no single solution for catalogue services that fits every user’s needs. As stated in CS\r\n2.0.2, a base profile that provides a basic set of information objects has to be supported\r\nby each catalogue instance; in addition, application profiles for different information\r\ncommunities can be specified.\r\nHence, this document specifies an application profile for ISO 19115:2003/ISO\r\n19119:2005 metadata with support for XML encoding per ISO/TS19139:2007 [ISO/TS19139]2 and HTTP protocol binding. It relies on requirements coming from the\r\nCS/CSW 2.0 specification (OGC CS 2.0.2, OGC document 07-006). The application\r\nprofile will form the basis of conformance tests and reference implementations." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28569,30 +27989,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-032r2" + "@value": "07-045r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: Aviation Abstract Quality Model Engineering Report" + "@value": "OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-116", + "@id": "http://www.opengis.net/def/docs/21-020r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-12-19" + "@value": "2022-01-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Aleksandar Balaban, Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -28607,17 +28027,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46793" + "@id": "https://docs.ogc.org/per/21-020r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-116" + "@value": "21-020r1" }, { "@language": "en", - "@value": "OWS-8 Geoprocessing for Earth Observations Engineering Report" + "@value": "OGC Testbed-17: Data Centric Security ER" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -28627,7 +28047,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Ad-hoc processing of Earth Observation (EO) data available through online resources is\r\ngaining more and more attention. Expected benefits include\r\n- More versatile EO data access\r\n- More convenient EO data access\r\n- Consequently, broadened use and exploitation of EO data\r\n- An important step towards integration of EO data into automatic chaining and\r\norchestration\r\n- More efficient EO data access: indicating the exact desired result and evaluating\r\nprocessing code close to the coverage data source (i.e., on the server) minimizes\r\nnetwork traffic, one of today’s critical performance limiting factors." + "@value": "This OGC Testbed-17 Engineering Report (ER) documents the enhancement of applying Data Centric Security (DCS) to OGC API Features, OGC API Maps (draft), and OGC API Tiles (draft).\r\n\r\nAs organizations move to the cloud, it is important to incorporate DCS into the design of the new cloud infrastructure, enabling the use of cloud computing, even for sensitive geospatial data sets. The ER documents the applicability of Zero Trust through a Data Centric security approach (DCS) when applied to vector and binary geospatial data sets (Maps, Tiles, GeoPackage containers) and OGC APIs.\r\n\r\nThe defined architecture extends the typical Zero Trust Domain component by introducing a Key Management System (KMS) to support key registration and the management of access conditions for key retrieval. The prototype implementations (DCS Client, DCS Server and KMS) demonstrate how to request encrypted geospatial data as JSON for encrypted vector data, HTTP Multipart for encrypted map data or GeoPackage with encrypted content; how to obtain decryption key(s) and how to decrypt and display the protected data in a mobile application on Android." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28638,35 +28058,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-116" + "@value": "21-020r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 Geoprocessing for Earth Observations Engineering Report" + "@value": "OGC Testbed-17: Data Centric Security ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-005r8", + "@id": "http://www.opengis.net/def/docs/16-046r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-09-05" + "@value": "2017-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Lott" + "@value": "Martin Klopfer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28676,27 +28096,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/as/18-005r8/18-005r8.pdf" + "@id": "https://docs.ogc.org/per/16-046r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 02 - Referencing by coordinates" + "@value": "16-046r1" }, { "@language": "en", - "@value": "18-005r8" + "@value": "Testbed-12 Semantic Enablement Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is consistent with the third edition (2019) of ISO 19111, Geographic Information - Referencing by coordinates including its amendments 1 and 2. ISO 19111:2019 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics, in close collaboration with the Open Geospatial Consortium (OGC). It replaces the second edition, ISO 19111:2007 and also ISO 19111-2:2009, OGC documents 08-015r2 and 10-020. This OGC document, 18-005r5, incorporates three editorial corrections made in ISO 19111:2019 amendment 1 of 2021." + "@value": "The requirement for capabilities supporting semantic understanding and reasoning in geospatial intelligence (GEOINT) is an all-encompassing paradigm shift from the past. Standards play a critical role in ensuring this is accomplished in a consistent and repeatable manner. Semantic standards and services supporting semantic capabilities are at a relatively early stage of development. Interoperability between semantic standards for encoding relationships and Web based services for discovery, access, retrieval and visualization of those relationships requires more testing and evaluation. This engineering report (ER) highlights the key findings and discussions from Testbed-12 that enable semantic interoperability, including semantic mediation, schema registries, and SPARQL endpoints. It references key findings from the Semantic Portrayal ER and helps to understand the current OGC discussion on semantics in general." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28707,35 +28127,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-005r8" + "@value": "16-046r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 2 - Referencing by coordinates (Including corrigendum 1 and corrigendum\t2)" + "@value": "Testbed-12 Semantic Enablement Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-028", + "@id": "http://www.opengis.net/def/docs/19-003", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-04-05" + "@value": "2019-09-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "Tom Landry, David Byrns" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28745,27 +28165,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13921" + "@id": "https://docs.ogc.org/per/19-003.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Sensor Alert Service" + "@value": "Earth System Grid Federation (ESGF) Compute Challenge" }, { "@language": "en", - "@value": "06-028" + "@value": "19-003" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A service providing active (push-based) access to sensor data." + "@value": "This Open Geospatial Consortium (OGC) Engineering Report (ER) will describe the advancement of an Execution Management System (EMS) to support Web Processing Service (WPS) climate processes deployed on the Earth System Grid Federation (ESGF). The report introduces climate data, processes and applications into Common Workflow Language (CWL) workflows with the intent of advancing: application packaging, deployment and execution in clouds; interoperability of services in federated cyberinfrastructures; and geospatial workflows towards standardization. Work presented in this report is a direct continuation of the Earth Observation & Clouds (EOC) thread of Testbed-14. This report is expected to be of relevance to Testbed-15, both to the Earth Observation Process and Application Discovery (EOPAD) task and the Machine Learning task. This engineering report will describe: relevant work conducted in OGC Testbed-14; ESGF and its compute challenge; adaptations of existing climate processes into workflows; interoperability experiments with ESGF endpoints conforming to a common API." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28776,35 +28196,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-028" + "@value": "19-003" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Alert Service" + "@value": "Earth System Grid Federation (ESGF) Compute Challenge" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-056r1", + "@id": "http://www.opengis.net/def/docs/16-100r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-07-23" + "@value": "2017-08-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Herring, OAB, Architecture WG" + "@value": "Paul Scarponcini" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28814,27 +28234,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21976" + "@id": "https://portal.ogc.org/files/?artifact_id=75117" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "The Specification Model -- Structuring an OGC specification to encourage implementation" + "@value": "16-100r2" }, { "@language": "en", - "@value": "07-056r1" + "@value": "InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard specifies some desirable characteristics of a standards specification that will encourage implementations by minimizing difficulty and optimizing usability and interoperability. " + "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 0 addresses the Core Requirements Class from LandInfra." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28845,35 +28265,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-056r1" + "@value": "16-100r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "The Specification Model -- Structuring an OGC specification to encourage implementation" + "@value": "OGC InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-020", + "@id": "http://www.opengis.net/def/docs/07-134r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-13" + "@value": "2008-04-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sergio Taleisnik" + "@value": "Richard Martell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/ts" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28883,27 +28303,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-020.html" + "@id": "https://portal.ogc.org/files/?artifact_id=27811" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-020" + "@value": "KML 2.2 - Abstract Test Suite" }, { "@language": "en", - "@value": "Aviation Engineering Report" + "@value": "07-134r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/ts" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Testbed-16 Aviation Engineering Report (ER) summarizes the implementations, findings and recommendations that emerged from the efforts of further advancing interoperability and usage of Linked Data within the Federal Aviation Administration (FAA) System Wide Information Management (SWIM) context. The goal of this effort was to experiment with OpenAPI and Linked Data to explore new ways for locating and retrieving SWIM data in order to enable consumers to consume SWIM data more easily in their business applications, and enable the discovery of additional relevant information for their needs.\r\n\r\nSpecifically, this ER documents the possibility of querying and accessing data (and its metadata) using Semantic Web Technologies as well as interlinking heterogeneous semantic data sources available on the Web. Together with an analysis on the potential for using OpenAPI-based Application Programming Interface (API) definitions to simplify access to geospatial information, an exploration of solutions for data distribution that complement those currently used by SWIM is presented." + "@value": "This document is an abstract test suite (ATS): a compendium of abstract test cases that provide a basis for verifying the structure and content of OGC KML 2.2 instance documents. Three conformance levels are defined; each level builds on the preceding ones:\r\n\r\n *\r\n\r\n Level 1 - includes test cases covering all requirements to be satisfied by a minimally conformant KML document;\r\n *\r\n\r\n Level 2 - as for Level 1, plus test cases addressing recommended requirements;\r\n *\r\n\r\n Level 3 - as for Level 2, plus test cases covering suggested constraints that are informative in nature." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28914,35 +28334,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-020" + "@value": "07-134r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: Aviation Engineering Report" + "@value": "OGC KML 2.2 -Abstract Test Suite" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-073r1", + "@id": "http://www.opengis.net/def/docs/09-148r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-06-30" + "@value": "2010-10-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Scott Fairgrieve" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -28952,27 +28372,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39728" + "@id": "https://portal.ogc.org/files/?artifact_id=41440" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-7 CCSI-SWE Best Practices Engineering Report" + "@value": "09-148r1" }, { "@language": "en", - "@value": "10-073r1" + "@value": "Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document seeks to define the Best Practices for integrating Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) compliant and potentially other CBRN-based sensors into an OGC Sensor Web Enablement (SWE)-based environment. The document focuses on the practical application of SWE services and encodings for describing and interacting with CCSI sensors and data and draws heavily from and expands upon work performed in the OGC Web Services Phase 6 (OWS-6) testbed to define methodologies for integrating CCSI sensors into a SWE-based environment both now, by building upon the OWS-6 work, and in the future, by defining CCSI profiles of the SWE specifications." + "@value": "This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using HTTP POST with XML encoding." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -28983,35 +28403,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-073r1" + "@value": "09-148r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-7 CCSI-SWE Best Practices Engineering Report" + "@value": "OGC® Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-037r1", + "@id": "http://www.opengis.net/def/docs/08-000", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-20" + "@value": "2008-04-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Raj SIngh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29021,27 +28441,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34098" + "@id": "https://portal.ogc.org/files/?artifact_id=26608" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-037r1" + "@value": "Canadian Geospatial Data Infrastructure Summary Report" }, { "@language": "en", - "@value": "OWS-6 UTDS-CityGML Implementation Profile" + "@value": "08-000" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC document specifies a CityGML-based application schema for a subset of an Urban Topographic Data Store (UTDS) as specified by the US National Geospatial-Intelligence Agency (NGA).\r\nThe particular focus of this implementation profile was to test the applicability of CityGML to UTDS data. \r\nThis document specifies the implementation profile as well as the findings.\r\n" + "@value": "This report summarizes the work performed under the Canadian Geospatial Data Infrastructure Pilot. The purpose of this pilot was to test the utility of certain OGC standards, in particular the Geography Markup Language (GML) and Web Feature Service (WFS), in the implementation of a spatial data infrastructure. OGC documents 08-001 and 08-002 are more technical companions to this document." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29052,69 +28472,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-037r1" + "@value": "08-000" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 UTDS-CityGML Implementation Profile" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-atb/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type Technical Baseline - deprecated " - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Documents of type Technical Baseline - deprecated " - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/04-014r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-053r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Documents of type Technical Baseline - deprecated " + "@value": "OGC® Canadian Geospatial Data Infrastructure Summary Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-032", + "@id": "http://www.opengis.net/def/docs/16-006r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-07-30" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steven Chau & Mohsen Kalantari" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29124,27 +28510,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-032.html" + "@id": "https://docs.ogc.org/bp/16-006r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Indoor Mapping and Navigation Pilot: Public Safety Features CityGML ADE ER" + "@value": "16-006r5" }, { "@language": "en", - "@value": "19-032" + "@value": "Volume 10: OGC CDB Implementation Guidance" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines an Application Domain Extension (ADE) of CityGML for public safety use cases. The ADE has been developed as part of OGC’s Indoor Mapping and Modeling Pilot project sponsored by the National Institute of Standards and Technology (NIST), Communications Technology Laboratory (CTL), Public Safety Communications Research (PSCR) Division. The ADE has been developed primarily based on reference preplan symbology created by the National Alliance for Public Safety GIS (NAPSG) Foundation. NAPSG is a 501 (C) (3) not-for-profit organization that was established in 2005 to overcome challenges faced by Federal, tribal, state, and local public safety agencies in the United States. NAPSG focuses on using GIS technology to resolve challenges that occur. In the definition of the ADE, public safety requirements that were not explicit in NAPSG have also been considered. This Engineering Report (ER) provides the methodology of the ADE development, details the implementation of the ADE and its structure and the application of the ADE in the context of public safety use cases.\r\n\r\nThe findings include:\r\n\r\nA methodology to transform NAPSG symbology to data elements;\r\n\r\nA need for an extension of a reference to four existing CityGML classes; and\r\n\r\nThe creation of seven new CityGML classes that are critical for public safety use cases." + "@value": "This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29155,35 +28541,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-032" + "@value": "16-006r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Indoor Mapping and Navigation Pilot: Public Safety Features CityGML ADE ER" + "@value": "Volume 10: OGC CDB Implementation Guidance" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-033", + "@id": "http://www.opengis.net/def/docs/08-128", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-29" + "@value": "2009-03-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Jirka, Arne Bröring" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29193,27 +28579,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=33284" + "@id": "https://portal.ogc.org/files/?artifact_id=29543" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-6 SensorML Profile for Discovery Engineering Report" + "@value": "GML 3.2 implementation of XML schemas in 07-022r1" }, { "@language": "en", - "@value": "09-033" + "@value": "08-128" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines a basic SensorML profile for discovery purposes. Besides a minimum set of metadata also the structure of according SensorML documents is defined in order to ensure a consistent metadata description. This goal is achieved by a set of Schematron rules that can be used to validate if a given SensorML document complies with the profile described in this engineering report." + "@value": "" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29224,35 +28610,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-033" + "@value": "08-128" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 SensorML Profile for Discovery Engineering Report" + "@value": "GML 3.2 implementation of XML schemas in 07-022r1" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-067r2", + "@id": "http://www.opengis.net/def/docs/08-062r7", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-10-09" + "@value": "2011-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Akiko Sato, Nobuhiro Ishimaru, Guo Tao, Masaaki Tanizaki" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/orm" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29262,27 +28648,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=35334" + "@id": "https://portal.ogc.org/files/?artifact_id=47245" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-067r2" + "@value": "OGC Reference Model" }, { "@language": "en", - "@value": "OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report" + "@value": "08-062r7" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/orm" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document described the Outdoor and Indoor 3D Routing and Services which are used in the OGC OWS-6 Decision Support Systems (DSS) thread. The objective is to enhance a network topology for the current CityGML specification based on the knowledge acquired through the development and experimental evaluation of this project. " + "@value": "The OGC Reference Model (ORM) describes the OGC Standards Baseline focusing on relationships between the baseline documents. The OGC Standards Baseline (SB) consists of the approved OGC Abstract and Implementation Standards (Interface, Encoding, Profile, and Application Schema – normative documents) and OGC Best Practice documents (informative documents)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29293,35 +28679,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-067r2" + "@value": "08-062r7" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report" + "@value": "OGC Reference Model" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-058r1", + "@id": "http://www.opengis.net/def/docs/20-012", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-09-12" + "@value": "2021-01-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stefan Falke" + "@value": "Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29331,27 +28717,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=30061" + "@id": "https://docs.ogc.org/per/20-012.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-058r1" + "@value": "UML-to-GML Application Schema Pilot (UGAS-2020) Engineering Report" }, { "@language": "en", - "@value": "OWS-5 Earth Observation Web Processing Services (WPS) Engineering Report" + "@value": "20-012" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document serves to describe the use of web processing services and the OGC Web Processing Service (WPS) in earth observation (EO) applications. It provides an overview of web processing services and a description of developments related to earth observation implementations of OGC WPS in the OGC OWS-5 testbed." + "@value": "During UGAS-2020 emerging technology requirements for NAS employment in the NSG, and with general applicability for the wider geospatial community, were investigated and solutions developed in four areas.\r\n\r\nTo enable a wide variety of analytic tradecrafts in the NSG to consistently and interoperably exchange data, the NAS defines an NSG-wide standard UML-based application schema in accordance with the ISO 19109 General Feature Model. In light of continuing technology evolution in the commercial marketplace it is desirable to be able to employ (NAS-conformant) JSON-based data exchanges alongside existing (NAS-conformant) XML-based data exchanges. A prototype design and implementation of UML Application Schema to JSON Schema rules (see the OWS-9 SSI UGAS Conversion Engineering Report) was reviewed and revised based on the final draft IETF JSON Schema standard “draft 2019-09.” The revised implementation was evaluated using NAS Baseline X-3. This work is reported in section UML to JSON Schema Encoding Rule.\r\n\r\nTo maximize cross-community data interoperability the NAS employs conceptual data schemas developed by communities external to the NSG, for example as defined by the ISO 19100-series standards. At the present time there are no defined JSON-based encodings for those conceptual schemas. A JSON-based core profile was developed for key external community conceptual schemas, particularly components of those ISO 19100-series standards used to enable data discovery, access, control, and use in data exchange in general, including in the NSG. This work is reported in section Features Core Profile of Key Community Conceptual Schemas.\r\n\r\nThe Features Core Profile and its JSON encoding have been specified with a broader scope than the NAS. It builds on the widely used GeoJSON standard and extends it with minimal extensions to support additional concepts that are important for the wider geospatial community and the OGC API standards, including support for solids, coordinate reference systems, and time intervals. These extensions have been kept minimal to keep implementation efforts as low as possible. If there is interest in the OGC membership, the JSON encoding of the Core Profile could be a starting point for a JSON encoding standard for features in the OGC. A new Standards Working Group for a standard OGC Features and Geometries JSON has been proposed.\r\n\r\nLinked data is increasingly important in enabling “connect the dots” correlation and alignment among diverse, distributed data sources and data repositories. Validation of both data content and link-based data relationships is critical to ensuring that the resulting virtual data assemblage has logical integrity and thus constitutes meaningful information. SHACL, a language for describing and validating RDF graphs, appears to offer significant as yet unrealized potential for enabling robust data validation in a linked-data environment. The results of evaluating that potential – with emphasis on deriving SHACL from a UML-based application schema - are reported in section Using SHACL for Validation of Linked Data.\r\n\r\nThe OpenAPI initiative is gaining traction in the commercial marketplace as a next-generation approach to defining machine-readable specifications for RESTful APIs in web-based environments. The OGC is currently shifting towards interface specifications based on the OpenAPI 3.1 specification. That specification defines both the interface (interactions between the client and service) and the structure of data payloads (content) offered by that service. It is desirable to be able to efficiently model the service interface using UML and then automatically derive the physical expression of that interface (for example, as a JSON file) using Model Driven Engineering (MDE) techniques alongside the derivation of JSON Schema defining data content. A preliminary analysis and design based on the OGC API Features standard, parts 1 and 2, for sections other than for content schemas, is reported in section Generating OpenAPI definitions from an application schema in UML.\r\n\r\nAll ShapeChange enhancements developed within the UGAS-2020 Pilot have been publicly released as a component of ShapeChange v2.10.0. https://shapechange.net has been updated to document the enhancements." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29362,30 +28748,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-058r1" + "@value": "20-012" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-5 Earth Observation Web Processing Services (WPS) Engineering Report" + "@value": "UML-to-GML Application Schema Pilot (UGAS-2020) Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-073", + "@id": "http://www.opengis.net/def/docs/16-029r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-10-26" + "@value": "2017-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -29400,17 +28786,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-073.html" + "@id": "https://docs.ogc.org/per/16-029r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-073" + "@value": "Testbed-12 GeoPackage Routing and Symbology Engineering Report" }, { "@language": "en", - "@value": "OGC Earth Observation Applications Pilot: Summary Engineering Report" + "@value": "16-029r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -29420,7 +28806,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) summarizes the main achievements of the OGC Innovation Program initiative Earth Observation Applications Pilot, conducted between December 2019 and July 2020." + "@value": "This OGC Engineering Report (ER) describes the results of experiments in OGC Testbed 12 designed to potentially enhance capabilities for symbology and routing [1] as extensions to the OGC GeoPackage standard. These experiments focused on 1.) methods for providing mounted and/or dismounted (off-road) routing within GeoPackage and 2.) mechanisms for providing user-defined map symbology for features in a GeoPackage structured data store. This ER documents the different approaches considered, design decisions and rationales, limitations, and issues encountered during prototype implementation.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29431,35 +28817,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-073" + "@value": "16-029r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Earth Observation Applications Pilot: Summary Engineering Report" + "@value": "Testbed-12 GeoPackage Routing and Symbology Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-135r1", + "@id": "http://www.opengis.net/def/docs/20-035", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-01-29" + "@value": "2021-01-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Christophe Noël" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29469,27 +28855,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=17566" + "@id": "https://docs.ogc.org/per/20-035.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-135r1" + "@value": "20-035" }, { "@language": "en", - "@value": "Specification best practices" + "@value": "Earth Observation Application Packages with Jupyter Notebooks" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes a variety of Best Practices and Specification development guidance that the Members have discussed and approved over the years. These Best Practices have not been captured in other formal OGC documents other than meeting notes." + "@value": "This OGC Testbed-16 Engineering Report (ER) describes all results and experiences from the “Earth Observation Application Packages with Jupyter Notebook” thread of OGC Testbed-16. The aim of this thread was to extend the Earth Observation Applications architecture developed in OGC Testbeds 13, 14, and 15 with support for shared and remotely executed Jupyter Notebooks. The Notebooks make use of the Data Access and Processing API (DAPA) developed in the Testbed-16 Data Access and Processing API (DAPA) for Geospatial Data task and tested in joint Technology Integration Experiments." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29500,35 +28886,46 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-135r1" + "@value": "20-035" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Specification best practices" + "@value": "OGC Testbed-16: Earth Observation Application Packages with Jupyter Notebooks" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-024r2", + "@id": "http://www.opengis.net/def/doc-type/d-atb", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/03-053r1" + }, + { + "@id": "http://www.opengis.net/def/docs/04-014r1" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/05-099r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-15" + "@value": "2006-07-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "R. Martell" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29538,27 +28935,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-024r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=13206" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-024r2" + "@value": "05-099r2" }, { "@language": "en", - "@value": "Testbed-12 — Catalog Services for Aviation" + "@value": "GML 3.1.1 simple dictionary profile" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) presents guidance concerning the use of OGC® catalog services in the aviation domain. A wide variety of metadata resources can be readily published and discovered using the OGC CSW-ebRIM application profile, which marries the CSW catalog interface to the OASIS ebXML registry information model (ebRIM). However, existing SWIM registries currently under development by the FAA and Eurocontrol do not implement any OGC standards. This report explores the prospects for enhancing SWIM registries by a) integrating OGC catalog functionality, and b) accommodating OGC service descriptions." + "@value": "This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding simple dictionaries. This profile can be used without a GML Application Schema, and such use is assumed in this document." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29569,35 +28966,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-024r2" + "@value": "05-099r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 — Catalog Services for Aviation" + "@value": "GML 3.1.1 simple dictionary profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-113r6", + "@id": "http://www.opengis.net/def/docs/15-104r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2017-08-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": " Carl Reed" + "@value": "Matthew Purss" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29607,27 +29004,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/15-113r6/15-113r6.html" + "@id": "https://docs.ogc.org/as/15-104r5/15-104r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-113r6" + "@value": "15-104r5" }, { "@language": "en", - "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure" + "@value": "Topic 21 - Discrete Global Grid Systems Abstract Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time." + "@value": "This document specifies the core Abstract Specification and extension mechanisms for Discrete Global Grid Systems (DGGS). A DGGS is a spatial reference system that uses a hierarchical tessellation of cells to partition and address the globe. DGGS are characterized by the properties of their cell structure, geo-encoding, quantization strategy and associated mathematical functions.The OGC DGGS Abstract Specification supports the specification of standardized DGGS infrastructures that enable the integrated analysis of very large, multi-source, multi-resolution, multi-dimensional, distributed geospatial data. Interoperability between OGC DGGS implementations is anticipated through implementation standards, and extension interface encodings of OGC Web Services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29638,35 +29035,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-113r6" + "@value": "15-104r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure" + "@value": "Topic 21 - Discrete Global Grid Systems Abstract Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-063r5", + "@id": "http://www.opengis.net/def/docs/09-016", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-05-01" + "@value": "2009-09-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Lott" + "@value": "Craig Bruce" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29676,27 +29073,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/12-063r5/12-063r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=33515" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Well known text representation of coordinate reference systems" + "@value": "OWS-6 Symbology Encoding (SE) Changes ER" }, { "@language": "en", - "@value": "12-063r5" + "@value": "09-016" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2007 and ISO 19111-2:2009. It extends the earlier WKT to allow for the description of coordinate operations. This International Standard defines the structure and content of well-known text strings. It does not prescribe how implementations should read or write these strings.\r\nThe jointly developed draft has also been submitted by ISO TC211 for publication as an International Standard document. The version incorporates comments made during both the OGC Public Comment Period as well as the ISO ballot for DIS (ISO TC211 document N3750). \r\n" + "@value": "This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the extension of the OGC Symbology Encoding (SE) symbology format for improved capability and harmonization with ISO 19117 symbology, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29707,35 +29104,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-063r5" + "@value": "09-016" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geographic information — Well known text representation of coordinate reference systems" + "@value": "OWS-6 Symbology Encoding (SE) Changes ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-099r2", + "@id": "http://www.opengis.net/def/docs/16-083r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-10-07" + "@value": "2017-06-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Eric Hirschorn" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29745,27 +29142,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39852" + "@id": "https://docs.ogc.org/is/16-083r2/16-083r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-099r2" + "@value": "Coverage Implementation Schema - ReferenceableGridCoverage Extension" }, { "@language": "en", - "@value": "Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0" + "@value": "16-083r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides revision notes for version 2.0 of the OpenGIS® Implementation Specification Geography Markup Language (GML) simple feature profile." + "@value": "The OGC GML Application Schema - Coverages (“GMLCOV”) version 1.0 [OGC 09-146r2], recently renamed the OGC Coverage Implementation Schema version 1.0, provides a ReferenceableGridCoverage element for representing coverages on a referenceable grid. However, GMLCOV provides no instantiable subtypes of a critical sub-element of ReferenceableGridCoverage, GMLCOV::AbstractReferenceableGrid. To make use of ReferenceableGridCoverage, an extension deriving from GMLCOV would need to be developed. GML 3.3 is not such an extension of GMLCOV, as it is built independently from GMLCOV. Use of the instantiable referenceable grid elements of GML 3.3 with ReferenceableGridCoverage violates Requirement 14 of GMLCOV 1.0 and Requirement 24 of the OGC Modular Specification[1].\r\n\r\nThis OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension provides a set of referenceable grid elements for use as sub-elements of ReferenceableGridCoverage. Three of these elements have been adapted from GML 3.3, while a fourth emerged from work on a Testbed-11 Engineering Report[2]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29776,35 +29173,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-099r2" + "@value": "16-083r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0" + "@value": "OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-142r1", + "@id": "http://www.opengis.net/def/docs/11-145", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-17" + "@value": "2014-05-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed, PhD. and Martin Thomson" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29814,27 +29211,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21630" + "@id": "https://portal.ogc.org/files/?artifact_id=46388" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-142r1" + "@value": "11-145" }, { "@language": "en", - "@value": "GML PIDF-LO Geometry Shape Application Schema for use in the IETF" + "@value": "Cyberarchitecture for Geosciences White Paper" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for XML encoding of various geometric shapes required in the Presence Information Description Format (IETF RFC 3863) Location Object extension - A Presence-based GEOPRIV Location Object Format (RFC 4119)." + "@value": "The National Science Foundation (NSF) is developing EarthCube” - Towards a National Data Infrastructure for Earth System Science . In a new partnership between GEO and the NSF Office of Cyberinfrastructure, NSF seeks transformative concepts and approaches to create a sustained, integrated data management infrastructure spanning the Geosciences. Meeting the challenges in geoscience research requires innovation and paradigm shifts in cyberinfrastructure. Information technology must advance to meet the emerging approaches to science. A cyber-architecture identifies repeatable patterns, reusable components, and open standards that provide starting point for innovative developments.\r\nThis white paper was written by Open Geospatial Consortium (OGC) members and associates to contribute to development of the NSF EarthCube. This document does not represent an official position of the OGC. However, the discussions in this document could very well lead to NSF developments and subsequent OGC documents. Recipients of this document are invited to reply to the authors’ with notification of any relevant patent rights of which they are aware and to provide supporting documentation.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29845,35 +29242,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-142r1" + "@value": "11-145" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML PIDF-LO Geometry Shape Application Schema for use in the IETF" + "@value": "Cyberarchitecture for Geosciences White Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-083r3", + "@id": "http://www.opengis.net/def/docs/14-005r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-04-25" + "@value": "2018-03-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Adrian Custer" + "@value": "Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29883,27 +29280,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39397" + "@id": "https://docs.ogc.org/is/14-005r5/14-005r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-083r3" + "@value": "OGC® IndoorGML - with Corrigendum" }, { "@language": "en", - "@value": "GeoAPI 3.0 Implementation Standard" + "@value": "14-005r5" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be used for the manipulation of geographic information structured following the specifications adopted by the Technical Committee211 of the International Organization for Standardization (ISO) and by the Open Geospatial Consortium (OGC). This standard standardizes the informatics contract between the client code which manipulates normalized data structures of geographic information based on the published API and the library code able both to instantiate and operate on these data structures according to the rules required by the published API and by the ISO and OGC standards." + "@value": "This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29914,35 +29311,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-083r3" + "@value": "14-005r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GeoAPI 3.0 Implementation Standard" + "@value": "OGC® IndoorGML - with Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-084", + "@id": "http://www.opengis.net/def/docs/18-005r8", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-07-08" + "@value": "2023-09-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andrea Aime" + "@value": "Roger Lott" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -29952,27 +29349,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-084.html" + "@id": "https://docs.ogc.org/as/18-005r8/18-005r8.pdf" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-084" + "@value": "18-005r8" }, { "@language": "en", - "@value": "Vector Tiles Pilot 2: Vector Tiles Filtering Language Engineering Report" + "@value": "Topic 02 - Referencing by coordinates" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Vector Tiles Pilot 2: Vector Tiles Filtering Language Engineering Report (ER) defines a filter language for vector data delivered as tiles (also known as vector tiles). The language applies to vector tiles served through implementations of the OGC API – Features standard and the draft OGC API - Tiles specification, but can be generally applied on all services supporting filtering by attributes.\r\n\r\nThe ER further includes an assessment of filter languages, styles and online/offline symbol sharing for GeoPackages, OGC API - Features and OGC API - Tiles implementations for accuracy and completeness in applications that render vector tiles at local to regional scales." + "@value": "This document is consistent with the third edition (2019) of ISO 19111, Geographic Information - Referencing by coordinates including its amendments 1 and 2. ISO 19111:2019 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics, in close collaboration with the Open Geospatial Consortium (OGC). It replaces the second edition, ISO 19111:2007 and also ISO 19111-2:2009, OGC documents 08-015r2 and 10-020. This OGC document, 18-005r5, incorporates three editorial corrections made in ISO 19111:2019 amendment 1 of 2021." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -29983,35 +29380,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-084" + "@value": "18-005r8" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Vector Tiles Pilot 2: Vector Tiles Filtering Language Engineering Report" + "@value": "Topic 2 - Referencing by coordinates (Including corrigendum 1 and corrigendum\t2)" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-007r3", + "@id": "http://www.opengis.net/def/docs/04-021r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-02-23" + "@value": "2004-08-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sara Saeedi" + "@value": "Doug Nebert" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -30021,27 +29418,31 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=72723" + "@id": "https://portal.ogc.org/files/?artifact_id=5929" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Volume 11: OGC CDB Core Standard Conceptual Model" + "@value": "Catalogue Service Implementation Specification [Catalogue Service for the Web]" }, { "@language": "en", - "@value": "16-007r3" + "@value": "Catalogue Service Implementation Specification" + }, + { + "@language": "en", + "@value": "04-021r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB 1.0 Standard. The objective of this document is to provide an abstract core conceptual model for a CDB data store (repository). The model is represented using UML (unified modeling language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering a UML model and documentation from the OGC CDB standard as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113]." + "@value": "The OpenGIS Catalogue Services Specification defines common interfaces to discover, browse, and query metadata about data, services, and other potential resources." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30052,30 +29453,34 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-007r3" + "@value": "04-021r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 11: OGC CDB Core Standard Conceptual Model" + "@value": "OpenGIS Catalogue Service Implementation Specification" + }, + { + "@language": "en", + "@value": "OpenGIS Catalogue Service Implementation Specification [Catalogue Service for the Web]" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-074", + "@id": "http://www.opengis.net/def/docs/07-027r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-07-22" + "@value": "2007-05-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Frans Knibbe, Alejandro Llaves" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -30090,17 +29495,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/15-074/15-074.html" + "@id": "https://portal.ogc.org/files/?artifact_id=21702" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Spatial Data on the Web Use Cases & Requirements" + "@value": "Local MSD Implementation Profile (GML 3.2.1)" }, { "@language": "en", - "@value": "15-074" + "@value": "07-027r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -30110,7 +29515,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC. " + "@value": "This document contains a data content specification for Local Mission Specific Data (MSD) and is based on the GEOINT Structure Implementation Profile (GSIP) developed by the NGA. This document defines the GML 3.2.1 (ISO 19136) encoding requirements for Local MSD. The structure of the document is based on ISO/DIS 19131 (Geographic Information " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30121,30 +29526,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-074" + "@value": "07-027r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Spatial Data on the Web Use Cases & Requirements" + "@value": "Local MSD Implementation Profile (GML 3.2.1)" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-030", + "@id": "http://www.opengis.net/def/docs/10-131r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-15" + "@value": "2010-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Debbie Wilson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -30159,17 +29564,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-030.html" + "@id": "https://portal.ogc.org/files/?artifact_id=40502" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-030" + "@value": "OWS-7 Aviation - AIXM Assessment Report" }, { "@language": "en", - "@value": "Testbed-12 Testbed-12 GeoPackage Mobile Apps Integration Engineering Report" + "@value": "10-131r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -30179,7 +29584,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Testbed 12 work evaluates the interoperability of the Common Map API tool with commercial vendor tools supporting GeoPackage. Ideally data can be shared and exchanged between apps on a single device via GeoPackage. The demonstration will show the vector and/or routing data being used by disparate applications." + "@value": "This report shall focus on evaluating the ability to: \r\n\r\n- Serve, filter and update AIXM 5.1 data via the OGC WFS-T 2.0 interface \r\n- Recommend guidelines or cross-walks for interpreting the new AIXM 5.1 schedules in conjunction with the Timeslice model in a web services environment" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30190,35 +29595,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-030" + "@value": "10-131r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Testbed-12 GeoPackage Mobile Apps Integration Engineering Report" + "@value": "OWS-7 Aviation - AIXM Assessment Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-049r1", + "@id": "http://www.opengis.net/def/docs/22-022r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-05-08" + "@value": "2023-09-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Vretanos" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-profile" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -30228,27 +29633,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=15201" + "@id": "https://docs.ogc.org/is/22-022r1/22-022r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-049r1" + "@value": "OGC SensorThings API Extension: STAplus 1.0" }, { "@language": "en", - "@value": "GML 3.1.1 simple features profile" + "@value": "22-022r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-profile" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® GML 3.1.1 Simple Features Profile (GML for Simple Features) is a restricted subset of GML (Geography Markup Language)[http://www.opengeospatial.org/standards/gml] and XML Schema [www.w3.org/XML/Schema] that supports the XML encoding of geographic features with simple geometric property types (Points, Line and Polygons). The profile defines three conformance classes that define three different levels of complexity. \r\n\r\nSee also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .\r\n" + "@value": "The OGC SensorThings API Extension: STAplus 1.0 Standard specifies a backwards-compatible extension to the OGC Standard SensorThings API Part 1: Sensing and Sensing 1.1 data model.\r\n\r\nThe motivation for specifying this STAplus extension is based on requirements from the Citizen Science community.\r\n\r\nThe dominant use for the OGC SensorThings API data model and API can be coined with the use case “single authority provides sensor readings to consumers.” However, in Citizen Science there are many contributors (citizens) who – together – create the big picture with their observations.\r\n\r\nThe STAplus extension is designed to support a model in which observations are owned by different users. This results in requirements for the ownership concept. In addition to the ownership, users may express a license for ensuring proper re-use of their observations. The STAplus extension also supports expressing explicit relations between observations as well as between observations and external resources. Relations can enrich observations to enable future extensions supporting Linked Data, RDF and SPARQL. Observation group(s) allow the grouping of observations that belong together.\r\n\r\nThe STAplus extension is believed to be an important contribution towards the realization of the FAIR principles as STAplus strengthens the “I” (Interoperability) through a common data model and API as well as the “R” (Re-usability) by allowing expressing standards-based queries that may consider licensing conditions which is relevant for reuse of other users’ observations.\r\n\r\nThe STAplus Data Model and Business Logic also enriches existing deployments as the extension can be seamlessly added and thereby offers new capabilities to create and manage the “big picture” with multi-user capabilities.\r\n\r\nThe key work for crafting this OGC Standard was undertaken in the Co-designed Citizen Observatories Services for the EOS-Cloud (Cos4Cloud) project, which received funding from the European Union’s Horizon 2020 research and innovation program and the Enhancing Citizen Observatories for healthy, sustainable, resilient and inclusive cities (CitiObs) project, which received funding from the European Union’s Horizon Europe research and innovation program. Testing of this extension was done with data from the Framework biodiversity project, which received funding from the European Union’s Horizon 2020 research and innovation program." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30259,35 +29664,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-049r1" + "@value": "22-022r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML 3.1.1 simple features profile" + "@value": "OGC SensorThings API Extension: STAplus 1.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-100r2", + "@id": "http://www.opengis.net/def/docs/16-114r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-11-18" + "@value": "2018-04-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ben Domenico, Stefano Nativi" + "@value": "Martin Desruisseaux" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -30297,27 +29702,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/14-100r2/14-100r2.html" + "@id": "https://docs.ogc.org/dp/16-114r2/16-114r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CF-netCDF 3.0 encoding using GML Coverage Application Schema" + "@value": "16-114r2" }, { "@language": "en", - "@value": "14-100r2" + "@value": "Moving Features Encoding Extension: netCDF" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC CF-netCDF data model supports multi-dimensional gridded data and multidimensional multi-point data, representing space and time-varying phenomena. In particular, this extension standard is limited to multi-point, and regular and warped grids.\r\nThis standard specifies the CF-netCDF data model encoding using the OGC GML 3.2.1 coverage application schema, as well as CF-netCDF data exchange format and protocol encoding.\r\nThis standard specifies: (a) the CF-netCDF GML encoding to be used by OGC standards; (b) the CF-netCDF data format exchanged using OGC standards; (c) the Internet protocol characteristics to effectively exchange CF-netCDF data.\r\nAs per the GML 3.3. standard, GML 3.3 imports the 3.2 schema. The canonical location of the 3.2 all components schema document for 3.3 is\r\nhttp://schemas.opengis.net/gml/3.2.1/gml.xsd" + "@value": "The netCDF Moving Features encoding extension is a summary of conventions that supports efficient exchange of simple moving features as binary files. This Discussion Paper is a complement to the Moving Features Encoding Part I: XML Core and an alternative to the Simple Comma Separated Values (CSV) extension. Compared to the CSV encoding, this netCDF encoding offers more compact storage and better performance at the cost of additional restrictions on the kinds of features that can be stored." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30328,35 +29733,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-100r2" + "@value": "16-114r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® CF-netCDF 3.0 encoding using GML Coverage Application Schema" + "@value": "OGC Moving Features Encoding Extension: netCDF" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-160r1", + "@id": "http://www.opengis.net/def/docs/05-036", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2005-06-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jon Blower, Xiaoyu Yang, Joan Masó and Simon Thum" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -30366,27 +29771,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=52884" + "@id": "https://portal.ogc.org/files/?artifact_id=10471&version=2" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-160r1" + "@value": "GeoXACML, a spatial extension to XACML" }, { "@language": "en", - "@value": "OWS 9 Data Quality and Web Mapping Engineering Report" + "@value": "05-036" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report specifies conventions for conveying information about data\r\nquality through the OGC Web Map Service Standard (known hereafter as the “WMS-Q\r\nconventions”), OGC Web Map Tile Service Standard (known hereafter as the “WMTS-Q\r\nconventions”), OGC KML (known hereafter as the “KML-Q conventions”) and OGC\r\nAugmented Reality Markup Language." + "@value": "This OGC document proposes one possible solution for the declaration and enforcement of access\r\nrestrictions for object-oriented geodata, available through a Service-based Geo Data Infrastructure. It is the\r\nintension of the author to motivate the requirement for such an access control, give a problem statement,\r\ndiscuss an alternative approach and describe the solution, based on GeoXACML." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30397,40 +29802,33 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-160r1" + "@value": "05-036" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS 9 Data Quality and Web Mapping Engineering Report" + "@value": "GeoXACML, a spatial extension to XACML" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-079", + "@id": "http://www.opengis.net/def/docs/15-075r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-07-10" - }, - { - "@type": "xsd:date", - "@value": "2017-09-23" + "@value": "2015-11-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Armin Haller, Krzysztof Janowicz, Simon Cox, Danh Le Phuoc, Kerry Taylor, Maxime Lefrançois" + "@value": "Ki-Joune Li, Hyung-Gyu Ryu, Taehoon Kim, and Hack-Cheol Kim" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ - { - "@id": "http://www.opengis.net/def/doc-type/is" - }, { "@id": "http://www.opengis.net/def/doc-type/dp" } @@ -30442,36 +29840,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://www.w3.org/TR/vocab-ssn/" - }, - { - "@id": "https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/" + "@id": "https://portal.ogc.org/files/?artifact_id=64644" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Semantic Sensor Network Ontology" + "@value": "A Use-Case for Mobile Location Services with IndoorGML - Indoor Navigation for Visually Impaired People" }, { "@language": "en", - "@value": "16-079" + "@value": "15-075r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ - { - "@id": "http://www.opengis.net/def/doc-type/is" - }, { "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Semantic Sensor Network (SSN) ontology is an ontology for describing sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties, as well as actuators. SSN follows a horizontal and vertical modularization architecture by including a lightweight but self-contained core ontology called SOSA (Sensor, Observation, Sample, and Actuator) for its elementary classes and properties. With their different scope and different degrees of axiomatization, SSN and SOSA are able to support a wide range of applications and use cases, including satellite imagery, large-scale scientific monitoring, industrial and household infrastructures, social sensing, citizen science, observation-driven ontology engineering, and the Web of Things. Both ontologies are described below, and examples of their usage are given.\r\n\r\nThe namespace for SSN terms is http://www.w3.org/ns/ssn/. \r\nThe namespace for SOSA terms is http://www.w3.org/ns/sosa/.\r\n\r\nThe suggested prefix for the SSN namespace is ssn.\r\nThe suggested prefix for the SOSA namespace is sosa.\r\n\r\nThe SSN ontology is available at http://www.w3.org/ns/ssn/. \r\nThe SOSA ontology is available at http://www.w3.org/ns/sosa/." - }, - { - "@value": "The Semantic Sensor Network (SSN) ontology is an ontology for describing sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties, as well as actuators. SSN follows a horizontal and vertical modularization architecture by including a lightweight but self-contained core ontology called SOSA (Sensor, Observation, Sample, and Actuator) for its elementary classes and properties. With their different scope and different degrees of axiomatization, SSN and SOSA are able to support a wide range of applications and use cases, including satellite imagery, large-scale scientific monitoring, industrial and household infrastructures, social sensing, citizen science, observation-driven ontology engineering, and the Web of Things. Both ontologies are described below, and examples of their usage are given." + "@value": "This OGC Discussion Paper provides a navigation use-case for the use of IndoorGML for mobile location services (MLS). In particular, the Discussion Paper explains how the OGC IndoorGML standard can be applied to a MLS application for visually impaired people in indoor space. Finally, a prototype development of the application on Android smart phone is described in this report." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30482,35 +29871,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-079" + "@value": "15-075r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Semantic Sensor Network Ontology" + "@value": "A Use-Case for Mobile Location Services with IndoorGML - Indoor Navigation for Visually Impaired People" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-017", + "@id": "http://www.opengis.net/def/docs/05-126", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-03-09" + "@value": "2005-11-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sam Lavender, Kate Williams, Caitlin Adams, Ivana Ivánová " + "@value": "Keith Ryden" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -30520,27 +29909,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-017.html" + "@id": "https://portal.ogc.org/files/?artifact_id=13227" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-18: Machine Learning Training Data ER" + "@value": "Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture" }, { "@language": "en", - "@value": "22-017" + "@value": "05-126" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 18 Engineering Report (ER) documents work to develop a foundation for future standardization of Training Datasets (TDS) for Earth Observation (EO) applications. The work performed in the Testbed 18 activity is based on previous OGC Machine Learning (ML) activities. TDS are essential to ML models, supporting accurate predictions in performing the desired task. However, a historical absence of standards has resulted in inconsistent and heterogeneous TDSs with limited discoverability and interoperability. Therefore, there is a need for best practices and guidelines for generating, structuring, describing, and curating TDSs that would include developing example software/packages to support these activities. Community and parallel OGC activities are working on these topics. This ER reviews those activities in parallel with making recommendations." + "@value": "This part of OpenGIS" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30551,35 +29940,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-017" + "@value": "05-126" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-18: Machine Learning Training Data ER" + "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architectu" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-045r2", + "@id": "http://www.opengis.net/def/docs/17-049", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-08-19" + "@value": "2018-03-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Uwe Voges, Kristian Senkler" + "@value": "C. Mitchell, M. Gordon, T. Kralidis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -30589,27 +29978,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/80534" + "@id": "https://portal.ogc.org/files/?artifact_id=77148" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum" + "@value": "Ensuring Quality of User Experience with OGC Web Mapping Services - Discussion Paper" }, { "@language": "en", - "@value": "07-045r2" + "@value": "17-049" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Catalogue services are the key technology for locating, managing and maintaining\r\ndistributed geo-resources (i.e. geospatial data, applications and services). With OGC\r\ncatalogue services, client applications are capable of searching for geo-resources in a\r\nstandardized way (i.e. through standardized interfaces and operations) and, ideally, they\r\nare based on a well-known information model, which includes spatial references and\r\nfurther descriptive (thematic) information that enables client applications to search for\r\ngeo-resources in very efficient ways.\r\nWhereas interfaces and operations of OGC catalogue services are well defined, it is left\r\nup to the developer of the system to define a specific information model which a\r\ncatalogue service instance provides. This includes, but is not limited to, the information\r\nwhich can be inserted in the catalog, supported query languages, available search terms,\r\nresponse/result sets, etc. This point is of major importance with respect to interoperability\r\nbetween different catalogue service instances.\r\nIn Europe, running catalogue instances result from work being done within different SDI\r\ninitiatives (e.g. SDI NRW Initiative1, Germany/Netherlands cross-border initiative, JRC\r\nEU Portal, EUROSTAT, Inspire, German SDI initiative). Members of these initiatives\r\nhave developed an ISO-based application profile for ISO19115 metadata for\r\ngeodata/geospatial applications and ISO19119-based metadata for tightly and looselycoupled\r\ngeospatial services. The foundations of this profile were the OGC catalogue\r\nspecification (1.1.1), the OGC Web Registry Server (WRS) 0.0.2, OGC Web Services\r\nStateless Catalogue Profile (StCS) 0.0.6 and ISO 19115/19119 for content description.\r\nOGC's catalogue revision working group (CS-RWG) has revised and integrated the\r\ncatalogue implementation specification v1.1.1 that have resulted in CS 2.0.2. One part of\r\nthis OGC specification comprises the definition of application profiles according to ISO\r\n19106 (Geographic information – Profiles). The overall goal of these profiles is to\r\nimprove interoperability between systems conforming to a specific profile. Experience\r\nhas shown that the need for application profiles results from the fact that in practice, there\r\nis no single solution for catalogue services that fits every user’s needs. As stated in CS\r\n2.0.2, a base profile that provides a basic set of information objects has to be supported\r\nby each catalogue instance; in addition, application profiles for different information\r\ncommunities can be specified.\r\nHence, this document specifies an application profile for ISO 19115:2003/ISO\r\n19119:2005 metadata with support for XML encoding per ISO/TS19139:2007 [ISO/TS19139]2 and HTTP protocol binding. It relies on requirements coming from the\r\nCS/CSW 2.0 specification (OGC CS 2.0.2, OGC document 07-006). The application\r\nprofile will form the basis of conformance tests and reference implementations." + "@value": "This paper is intended to identify usability issues associated with use of OGC web\r\nmapping services that affect the quality of experience a user may have when accessing\r\nand using OGC web services and discuss potential solutions and guidance to address\r\nthese issues. Additionally, guidance on evaluating and self-assessing the Quality of\r\nExperience of Spatial Data Services will also be discussed and addressed with a proposal\r\nfor common assessment criteria and common practices for improving the user experience\r\nwhen viewing, layering or querying OGC web mapping services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30620,35 +30009,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-045r2" + "@value": "17-049" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum" + "@value": "Ensuring Quality of User Experience with OGC Web Mapping Services - Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-066r2", + "@id": "http://www.opengis.net/def/docs/07-045r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-05-02" + "@value": "2022-08-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Uwe Voges, Kristian Senkler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -30658,27 +30047,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/17-066r2/17-066r2.html" + "@id": "https://portal.ogc.org/files/80534" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-066r2" + "@value": "OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum" }, { "@language": "en", - "@value": "OGC GeoPackage Extension for Tiled Gridded Coverage Data" + "@value": "07-045r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The GeoPackage Extension for Tiled Gridded Coverage Data” (TGCE) extension (previously titled Elevation Extension) defines how to encode and store tiled regular gridded data, such as a digital elevation model, in a GeoPackage. The tiles contain values, such as elevation, temperature or pressure, and the extension defines two encodings. The PNG encoding uses PNG files to store 16-bit integer values and a scale and offset may be applied to fine-tune the coverage range. To support 32-bit floating point data or binary data, the extension also defines a TIFF encoding. In this encoding, TIFF files are used to store IEEE floating point or a binary data type where the SampleFormat has a value of either 1 (unsigned integer) or 2 (signed integer) AND the BitsPerSample is either 8, 16, or 32. To simplify development, this encoding constrains many of the TIFF options to the minimal set needed to meet the floating-point requirement. The extension also defines two ancillary data tables: one for regular gridded coverages and one for tiles.\r\n\r\n" + "@value": "Catalogue services are the key technology for locating, managing and maintaining\r\ndistributed geo-resources (i.e. geospatial data, applications and services). With OGC\r\ncatalogue services, client applications are capable of searching for geo-resources in a\r\nstandardized way (i.e. through standardized interfaces and operations) and, ideally, they\r\nare based on a well-known information model, which includes spatial references and\r\nfurther descriptive (thematic) information that enables client applications to search for\r\ngeo-resources in very efficient ways.\r\nWhereas interfaces and operations of OGC catalogue services are well defined, it is left\r\nup to the developer of the system to define a specific information model which a\r\ncatalogue service instance provides. This includes, but is not limited to, the information\r\nwhich can be inserted in the catalog, supported query languages, available search terms,\r\nresponse/result sets, etc. This point is of major importance with respect to interoperability\r\nbetween different catalogue service instances.\r\nIn Europe, running catalogue instances result from work being done within different SDI\r\ninitiatives (e.g. SDI NRW Initiative1, Germany/Netherlands cross-border initiative, JRC\r\nEU Portal, EUROSTAT, Inspire, German SDI initiative). Members of these initiatives\r\nhave developed an ISO-based application profile for ISO19115 metadata for\r\ngeodata/geospatial applications and ISO19119-based metadata for tightly and looselycoupled\r\ngeospatial services. The foundations of this profile were the OGC catalogue\r\nspecification (1.1.1), the OGC Web Registry Server (WRS) 0.0.2, OGC Web Services\r\nStateless Catalogue Profile (StCS) 0.0.6 and ISO 19115/19119 for content description.\r\nOGC's catalogue revision working group (CS-RWG) has revised and integrated the\r\ncatalogue implementation specification v1.1.1 that have resulted in CS 2.0.2. One part of\r\nthis OGC specification comprises the definition of application profiles according to ISO\r\n19106 (Geographic information – Profiles). The overall goal of these profiles is to\r\nimprove interoperability between systems conforming to a specific profile. Experience\r\nhas shown that the need for application profiles results from the fact that in practice, there\r\nis no single solution for catalogue services that fits every user’s needs. As stated in CS\r\n2.0.2, a base profile that provides a basic set of information objects has to be supported\r\nby each catalogue instance; in addition, application profiles for different information\r\ncommunities can be specified.\r\nHence, this document specifies an application profile for ISO 19115:2003/ISO\r\n19119:2005 metadata with support for XML encoding per ISO/TS19139:2007 [ISO/TS19139]2 and HTTP protocol binding. It relies on requirements coming from the\r\nCS/CSW 2.0 specification (OGC CS 2.0.2, OGC document 07-006). The application\r\nprofile will form the basis of conformance tests and reference implementations." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30689,35 +30078,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-066r2" + "@value": "07-045r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoPackage Extension for Tiled Gridded Coverage Data" + "@value": "OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-091r1", + "@id": "http://www.opengis.net/def/docs/18-021", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-03-18" + "@value": "2019-03-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas Gilbert, Carsten Rönsdorf, Jim Plume, Scott Simmons, Nick Nisbet, Hans-Christoph Gruler, Thom" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -30727,27 +30116,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=92634" + "@id": "https://docs.ogc.org/per/18-021.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra" + "@value": "Next Generation APIs: Complex Feature Handling Engineering Report" }, { "@language": "en", - "@value": "19-091r1" + "@value": "18-021" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Demand for digital representations of built environments is accelerating and can only be satisfied through greater software interoperability and data integration. The objective of the Integrated Digital Built Environment (IDBE) joint working group is to address this challenge by bringing together experts from the Open Geospatial Consortium and buildingSMART to coordinate the development of the relevant data standards. This document is an output from IDBE in which we describe the state of three of the most prominent built environment standards – CityGML, IFC and LandInfra – and describe some of the problems that hinder their integration; finally, we propose actions points for overcoming these problems." + "@value": "OGC Web Feature Service (WFS) 3.0 is a revision of the WFS standard that proposes a modernized service architecture, that follows the current Web architecture, has a focus on the developer experience, supports the OpenAPI specification, and modularizes WFS into building blocks for fine-grained access to spatial data that can be used by an Application Programming Interface (API) for data.\r\n\r\nThis document reviews the work that proposes a next generation of OGC web services (NextGen services or Next Generation APIs) from the perspective of supporting complex three-dimensional (3D) data or complex data schemas. The goal is to identify the best service solution for these particular needs, whether the results are WFS 3.0 extensions or other approaches. In this context the approach of the NextGen services is not of monolithic web services, but Web API building blocks. This is an important point. The same API should be able to support requirements that currently require separate OGC web services, e.g. a WFS and a 3D Portrayal Service (3DPS).\r\n\r\nThe purpose of this work is not to preempt other next-generation discussions taking place in OGC but rather to inform and complement that work.\r\n\r\nThe report includes proposals on how to extend the NextGen service architecture with API building blocks for complex data, complex queries and 3D portrayal. WFS 3.0, Part 1, is used as the starting point for the NextGen service architecture. The proposals are based on existing requirements and use cases as well as existing support for developers to simplify implementation.\r\n\r\nThe work has found no general issues with migrating current WFS, 3DPS, Web Map Tile Service (WMTS) and Web Map Service (WMS) capabilities to the NextGen architecture. On the contrary, the NextGen approach improves the consistency of the interface and removes redundancies (e.g., between the feature access in WFS and the feature info requests in the other standards)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30758,35 +30147,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-091r1" + "@value": "18-021" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra" + "@value": "OGC Testbed-14 Next Generation APIs: Complex Feature Handling Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-101", + "@id": "http://www.opengis.net/def/docs/05-086", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-11-06" + "@value": "2005-11-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Mike Botts" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -30796,27 +30185,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55232" + "@id": "https://portal.ogc.org/files/?artifact_id=12606" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 GML 3.2.1 Encoding Extension" + "@value": "Sensor Model Language (SensorML)" }, { "@language": "en", - "@value": "13-101" + "@value": "05-086" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard defines the version 3.0 of a valid GML 3.2.1 geometry encoding as defined in Geography Markup Language (GML) simple features profile (with Corrigendum) to be used with the GeoXACML 3.0 Core standard.\r\nThe use of this encoding extension to GeoXACML 3.0 Core enables the direct use of GML 3.2.1 encoded geometries into a GeoXACML 3.0 Policy, an Authorization Decision Request or in an Authorization Decision’s Obligation element. It thereby improves the performance of deriving access control decisions, where geometries are involved as existing GML 3.2.1 geometry encodings must not be transformed to Well Known Text (WKT) as supported by GeoXACML 3.0 Core. Furthermore, the use of this encoding extension simplifies the implementation of a Policy Enforcement Point as it must not provide the transformation functions from GML to WKT and vice versa.\r\nThis encoding extension has its normative base in Geography Markup Language (GML) simple features profile (with Corrigendum).\r\n" + "@value": "The general models and XML encodings for sensors. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30827,35 +30216,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-101" + "@value": "05-086" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 GML 3.2.1 Encoding Extension" + "@value": "OpenGIS Sensor Model Language (SensorML)" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-051", + "@id": "http://www.opengis.net/def/docs/15-074r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-12" + "@value": "2016-10-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó" + "@value": "Frans Knibbe, Alejandro Llaves" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -30865,27 +30254,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-051.html" + "@id": "https://docs.ogc.org/dp/15-074r2/15-074r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-051" + "@value": "Spatial Data on the Web Use Cases & Requirements" }, { "@language": "en", - "@value": "Testbed-12 Javascript-JSON-JSON-LD Engineering Report" + "@value": "15-074r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Testbed-11 deliverable OGC 15-053 Implementing JSON/GeoJSON in an OGC Standard ER enumerated strategies for implementing JSON in OGC services and OGC encodings. Previously, a mechanism to migrate XML into JSON was proposed by Pedro Gonçalves in 14-009r1 OGC Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context. In contrast, this engineering report (ER) proposes a mechanism to derive JSON and JSON-LD encodings from UML modeling without using XML as an intermediate step. The rules provided can be divided into rules for JSON instances and rules for JSON schemas.\r\n\r\nThese rules have been applied to the UML diagrams in OWS common 2.0 to derive JSON encodings for them. In practice this ER evaluates how to provide service metadata in the derived JSON. JSON schemas and @context documents for independent validation of the four main sections of the ServiceMetadata are provided. This activity is done in connection with the OGC 16-052 OWS Context / Capabilities ER. The rules are applied to WMS to provide a full JSON encoding for the WMS 1.4 standard candidate.\r\n\r\nFinally, this ER discusses the applicability to data geospatial formats, both for coverage formats (compared to the CIS standard) and feature formats (compared to GeoJSON).\r\n\r\nReaders unfamiliar with JSON, JSON-LD and JSON Schema should first read OGC 16-122 (Geo)JSON User Guide. OGC 16-122 includes guidelines and recommendations for the use of JSON and JSON-LD in OGC data encodings and services." + "@value": "This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30896,30 +30285,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-051" + "@value": "15-074r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Javascript-JSON-JSON-LD Engineering Report" + "@value": "Spatial Data on the Web Use Cases & Requirements" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-036r2", + "@id": "http://www.opengis.net/def/docs/21-039r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-08-18" + "@value": "2022-01-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stan Tillman" + "@value": "Sergio Taleisnik" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -30934,17 +30323,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40313" + "@id": "https://docs.ogc.org/per/21-039r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-7 Motion Video Change Detection" + "@value": "21-039r1" }, { "@language": "en", - "@value": "10-036r2" + "@value": "OGC Testbed-17: Aviation API ER" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -30954,7 +30343,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report documents the development effort to build a Web Processing Service (WPS) to perform a change detection algorithm on two motion video streams. It will examine the WPS Motion Video Change Detection architecture from various viewpoints in order to describe its purpose, data models, functional decomposition, and interaction between distinct computational components. " + "@value": "This Testbed-17 (TB-17) Aviation API Engineering Report (ER) summarizes the implementations, findings and recommendations that emerged from the efforts of building a definition for an Aviation API compliant with the requirements of the OGC Standards Program, and the exploration of the potential of aviation data fusion.\r\n\r\nThis ER describes the nine façades built to interface SWIM services and serve aviation data through OGC APIs, the two services built to consume SWIM data and fuse it to generate richer datasets while serving the fused data through OGC APIs, the client application built to display data retrieved from the façades and fusion services, and the development client built to focus on functionality and experimentation.\r\n\r\nFinally, this ER discusses the potential of OGC APIs to help standardize the access to aviation data within the context of the System Wide Information Management (SWIM) program." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -30965,35 +30354,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-036r2" + "@value": "21-039r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-7 Motion Video Change Detection" + "@value": "OGC Testbed-17: Aviation API ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-065r6", + "@id": "http://www.opengis.net/def/docs/07-095r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-10-16" + "@value": "2007-11-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Evans" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -31003,27 +30392,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=3837" + "@id": "https://portal.ogc.org/files/?artifact_id=23979" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Service (WCS) Implementation Specification" + "@value": "07-095r2" }, { "@language": "en", - "@value": "03-065r6" + "@value": "Web Services Summaries" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Extends the Web Map Server (WMS) interface to allow access to geospatial coverages that represent values or properties of geographic locations, rather than WMS generated maps (pictures)." + "@value": "This document provides brief and consistent summaries of several OGC Web Service interface specifications that serve data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -31034,35 +30423,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-065r6" + "@value": "07-095r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Coverage Service (WCS) Implementation Specification" + "@value": "OGC Web Services Summaries" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-054", + "@id": "http://www.opengis.net/def/docs/11-039r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-01-05" + "@value": "2012-04-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sergio Taleisnik" + "@value": "Rob Atkinson, Irina Dornblut" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -31072,27 +30461,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-054.html" + "@id": "https://portal.ogc.org/files/?artifact_id=47831" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Disaster Pilot JSON-LD Structured Data Engineering Report" + "@value": "HY_Features: a Common Hydrologic Feature Model Discussion Paper" }, { "@language": "en", - "@value": "21-054" + "@value": "11-039r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Disaster Pilot JSON-LD Structured Data Engineering Report documents the analysis, discussions, results, and recommendations that emerge from the efforts carried out regarding the use of JSON-LD with OGC APIs to generate structured web page data for search engine optimization of disaster related information.\r\n\r\nThis ER provides the practical experience and lessons learned on the usage of Linked Data within OGC APIs with the objective of enhancing the web search and finding up-to-date conditions, observations, and predictions associated with well-known local geography. Upcoming initiatives should use the findings documented in this ER to further develop applications that make geospatial data and information more easily findable, accessible, interoperable, and reusable, which will increase the efficiency of disaster response. This ER could also be used as a case study of Linked Data to help other industries understand its value and implement it within their domains, or it could serve as a baseline for adding Linked Data support to one or several OGC API standards." + "@value": "This document describes a conceptual model for the identification of hydrologic features independent from geometric representation. This model allows common reference to hydrologic features across scientific sub-disciplines in hydrology. The Hydrologic Feature Model, HY_Features, is designed as a set of interrelated Application Schemas using ISO 19103 Conceptual Schema Language and ISO 19109 General Feature Model. It is factored into relatively simple components that can be reviewed, tested and extended independently." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -31103,30 +30492,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-054" + "@value": "11-039r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Disaster Pilot JSON-LD Structured Data Engineering Report" + "@value": "HY_Features: a Common Hydrologic Feature Model Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-030", + "@id": "http://www.opengis.net/def/docs/18-025", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-10-22" + "@value": "2019-03-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Timothy Miller and Gil Trenum" + "@value": "Jérôme Jacovella-St-Louis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -31141,17 +30530,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-030.html" + "@id": "https://docs.ogc.org/per/18-025.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC API - Tiles - 3D (GeoVolumes) Engineering Report" + "@value": "18-025" }, { "@language": "en", - "@value": "20-030" + "@value": " CityGML and AR Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -31161,7 +30550,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report documents the draft specification for a three-dimensional (3D) geodata Application Programming Interface (API) that organizes access to a variety of 2D / 3D datasets and their distributions according to a nested hierarchy of 3D geospatial volumes (GeoVolumes). The GeoVolumes (initially Tiles-3D / 3D Container) API specification is consistent with OGC API - Common and supports both link-follow and bbox query methods of access to resources of interest." + "@value": "This OGC Testbed-14 Engineering Report (ER) describes the results of the Augmented Reality (AR) work performed in the Testbed-14 CityGML and Augmented Reality work package which was part of the Next Generation Services thread.\r\n\r\nBy integrating information available from urban models within a view of the real world through a mobile device, this testbed activity explored the possibilities offered by AR in a geospatial context. The ER additionally discusses the approach used to bring in these urban models from various data sources. The experiments also covered to some extent Virtual Reality (VR) where any city can be explored freely from a computer display or potentially within a VR headset.\r\n\r\nA continuation of these experiments would have looked at a combination of Augmented and Virtual Reality (Mixed Reality). The portrayal of AR and three-dimensional (3D) content through extending a common conceptual model to style classic geospatial features (as explored in the Testbed-14 Portrayal work) is also touched upon. The efficient transmission of 3D content is also a subject of this document through the use of a simple 3D transmission format developed during the initiative.\r\n\r\nThis ER provides many insights that showcase what is now made possible by the combination of AR, VR and integrated urban models.\r\n\r\nThe testbed work shines light on the benefits of applying a common portrayal approach to AR, bridging the gap between AR applications and traditional Geographic Information Systems and services.\r\n\r\nThe ER introduces a new, simple approach and conceptual model for transmitting 3D geospatial content which could be the basis to define simple profiles for the I3S and 3D Tiles community standards. It could also inform enhancements to the 3D Portrayal Service (3DPS) and/or next generation services (e.g., WFS 3.0) for delivering 3D contents in a format agnostic manner.\r\n\r\nFinally, the ER covers methods to bring in different types of geospatial content from various sources for integration into AR applications.\r\n\r\nDuring Testbed-14, the participants demonstrated AR experiences with geospatial datasets providing integrated views of urban spaces. Two clients and two services were shown to be interoperable, streaming AR content through a simple 3D transmission format, leveraging either GeoJSON or GNOSIS Map Tiles, as well as E3D 3D model specifications.\r\n\r\nThe feasibility of extending a classic portrayal conceptual model for AR was also shown. In order to serve them to the clients in the supported transmission formats, geospatial data sets of various types and in various formats were successfully imported for consumption by the services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -31172,30 +30561,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-030" + "@value": "18-025" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Tiles - 3D (GeoVolumes) Engineering Report" + "@value": "OGC Testbed-14: CityGML and AR Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-031r1", + "@id": "http://www.opengis.net/def/docs/11-072r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-01-03" + "@value": "2012-01-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Pedro Gonçalves" + "@value": "Wenny Rahayu, Torab Torabi, Andrew Taylor-Harris, Florian Puersch" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -31210,17 +30599,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-031r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=46322" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-031r1" + "@value": "OWS-8 Aviation - WXXM Engineering Report" }, { "@language": "en", - "@value": "Testbed-18: Reproducible FAIR Best Practices Engineering Report" + "@value": "11-072r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -31230,7 +30619,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Testbed-18 initiative included a discussion exploring the future of open science and building energy interoperability with the task of developing a set of best practices to make the data processing services of Exploitation Platforms both reproducible and follow the FAIR data principles.\r\n\r\nPortability and reproducibility are key factors for the long-term scientific impact of Earth Observation (EO) data processing applications provided by Exploitations Platforms. The EO application developers lack the tools and guidance to preserve all the elements, algorithms, software, and data resources used to produce the results. Without these elements, reproducibility becomes resubmission within the platform and only while the same platform resources such as data are preserved and available.\r\n\r\nThis Testbed 18 Engineering Report defines a list of requirements and respective best practices to support reproducible Earth Observation science covering the different resources of the Earth Observation Exploitation Platforms such as publications, data, services, products, information, software, or computing environments.\r\n\r\n" + "@value": "This OGC™ document specifies the advancement of WXXM and Weather Concepts in\r\nthe OWS-8 Aviation Thread. The focus is on investigating and demonstrating the\r\napplicability and suitability of WXXM in producing accurate, real-time aircraft weather\r\nradar data using OGC™ Web Coverage Services (WCS) to be used by meteorological\r\napplications and services supporting aviation. Such applications provide information\r\nwhich enhances safe and efficient tactical and" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -31241,35 +30630,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-031r1" + "@value": "11-072r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-18: Reproducible FAIR Best Practices Engineering Report" + "@value": "OWS-8 Aviation - WXXM Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-068r3", + "@id": "http://www.opengis.net/def/docs/08-176r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-06-15" + "@value": "2009-07-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -31279,27 +30668,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/08-068r3/08-068r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=34273" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-068r3" + "@value": "08-176r1" }, { "@language": "en", - "@value": "Web Coverage Processing Service (WCPS) Language Interface Standard" + "@value": "OWS-6 Secure Sensor Web Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Web Coverage Processing Service (WCPS) defines a protocol-independent language for on-demand extraction, processing, and analysis of multi-dimensional gridded coverages (datacubes) representing among others spatio-temporal sensor, image, simulation, or statistics data." + "@value": "The main purpose of this Engineering Report is to introduce standards-based security solutions for making the existing OGC Sensor Web Services, as described in the OWS-6 SWE baseline, ready towards the handling of sensors in the intelligence domain." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -31310,35 +30699,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-068r3" + "@value": "08-176r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Coverage Processing Service (WCPS) Language Interface Standard" + "@value": "OWS-6 Secure Sensor Web Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-046", + "@id": "http://www.opengis.net/def/docs/06-173r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-20" + "@value": "2007-01-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "John Herring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -31348,27 +30737,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-046.html" + "@id": "https://portal.ogc.org/files/?artifact_id=19054" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-046" + "@value": "Geographic information - Rights expression language for geographic information - Part xx: GeoREL" }, { "@language": "en", - "@value": "Earth Observation Exploitation Platform Hackathon 2018 Engineering Report" + "@value": "06-173r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Earth Observation Exploitation Platform Hackathon 2018 was conducted to evaluate the standards based architecture for deploying and executing arbitrary applications close to the physical location of the data in heterogeneous cloud environments. The Hackathon was very successful in demonstrating both efficiency and sustainability of the architecture developed in Testbed-13. Efficient, because it was possible to setup the full execution workflow of 128 Sentinel-1 images within the 1.5 days of the Hackathon in a multi-vendor environment. Sustainable, because the architectural approach provides sufficient flexibility to cater for possible extensions and exchange of cloud & container middleware.\r\n\r\nThe Hackathon produced a number of suggestions for future work items. These include new tools to facilitate the process of Application Package generation to make it even simpler for scientists to bring their applications to the market; a more detailed specification to further improve the level of interoperability; and a best practice document with lots of examples that illustrate the necessary steps to make applications available.\r\n\r\nHackathon participants highlighted that such a level of robustness, flexibility, and maturity of the application-to-the-cloud architecture has been developed in nine months only during Testbed-13. The participants recommend to continue interlacing major OGC Innovation Program activities, such as testbeds, with short term rapid prototyping initiatives such as hackathons. Almost all participants of the Hackathon had been new to the OGC Innovation Program. These participants emphasized that the Hackathon provided an outstanding opportunity for newcomers to get quickly familiar with the latest standardization efforts and helped tremendously in understanding investments and new market opportunities for applications-in-the-cloud." + "@value": " This document extends the rights expression language (REL) to encompass the concerns of holders of geographic data and service resources to equally ensure their protection. This allows the geographic information market to operate with minimal constraints derived from need for the protection of intellectual property." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -31379,35 +30768,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-046" + "@value": "06-173r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Earth Observation Exploitation Platform Hackathon 2018 Engineering Report" + "@value": "Geographic information - Rights expression language for geographic information - Part xx: GeoREL" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-009", + "@id": "http://www.opengis.net/def/docs/04-060r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-01-14" + "@value": "2005-02-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ron Lake" + "@value": "Jerome Sonnett" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -31417,27 +30806,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1108" + "@id": "https://portal.ogc.org/files/?artifact_id=8348" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "02-009" + "@value": "OWS 2 Common Architecture: WSDL SOAP UDDI" }, { "@language": "en", - "@value": "Geography Markup Language" + "@value": "04-060r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features." + "@value": "This OGC document reports the work that occurred in the OWS2 Test Bed Common Architecture thread. This thread focused on the use of UDDI/WSDL/SOAP in the OGC Web Services architecture. It also provides guidelines for the use of these technologies. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -31448,35 +30837,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-009" + "@value": "04-060r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geography Markup Language" + "@value": "OWS 2 Common Architecture: WSDL SOAP UDDI" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-007r4", + "@id": "http://www.opengis.net/def/docs/17-094r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-19" + "@value": "2018-10-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sara Saeedi" + "@value": "Jeff Yutzler, Rob Cass" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -31486,27 +30875,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/16-007r4" + "@id": "https://docs.ogc.org/per/17-094r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-007r4" + "@value": "17-094r1" }, { "@language": "en", - "@value": "Volume 11: OGC CDB Core Standard Conceptual Model" + "@value": "Portrayal Concept Development Study" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB Standard. The objective of this document is to provide an abstract core conceptual model for a CDB data store (repository). The model is represented using UML (unified modeling language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering the UML diagrams and documentation from the original CDB submission as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113r5].\r\n\r\nNOTE: The simulation community uses the term “synthetic environment data” to mean all the digital data stored in some database or structured data store that is required for use by simulation clients. From the geospatial community perspective, these data are essentially the same as GIS data but with, in some cases, special attributes, such as radar reflectivity.\r\n" + "@value": "The main goal of this CDS is to advance the standards and guidance that will allow production of high-quality digital maps over the web from existing vector data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -31517,35 +30906,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-007r4" + "@value": "17-094r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 11: OGC CDB Core Standard Conceptual Model" + "@value": "OGC Portrayal Concept Development Study" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-064r5", + "@id": "http://www.opengis.net/def/docs/06-126", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-06-25" + "@value": "2006-10-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Eric Bertel" + "@value": "Chuck Morris" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -31555,27 +30944,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=5936" + "@id": "https://portal.ogc.org/files/?artifact_id=16860" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-064r5" + "@value": "Compliance Test Language (CTL) Discussion Paper" }, { "@language": "en", - "@value": "GO-1 Application Objects" + "@value": "06-126" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The GO-1 Application Objects specification defines a set of core packages that support a small set of Geometries, a basic set of renderable Graphics that correspond to those Geometries, 2D device abstractions (displays, mouse, keyboard, etc.), and supporting classes. Implementation of these APIs will support the needs of many users of geospatial and graphic information. These APIs support the rendering of geospatial datasets, provide fine-grained symbolization of geometries, and support dynamic, event and user driven animation of geo-registered graphics." + "@value": "This document establishes Compliance Test Language, an XML grammar for documenting and scripting suites of tests for verifying that an implementation of a specification complies with the specification." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -31586,35 +30975,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-064r5" + "@value": "06-126" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GO-1 Application Objects" + "@value": "Compliance Test Language (CTL) Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-035", + "@id": "http://www.opengis.net/def/docs/09-147r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-09-01" + "@value": "2010-10-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jérôme Jacovella-St-Louis" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -31624,27 +31013,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-035.html" + "@id": "https://portal.ogc.org/files/?artifact_id=41439" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-18: 3D+ Data Streaming Engineering Report" + "@value": "09-147r1" }, { "@language": "en", - "@value": "22-035" + "@value": "Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 18 3D Plus Data Standards and Streaming Engineering Report (ER) reviews existing specifications that support interoperable descriptions of orbital and non-orbital space-based assets, objects, and observations as well as terrestrial observations. The ER suggests a framework consolidating these specifications as a foundation for modeling, representation, and serialization from space-based assets operating at any location in our solar system (3D+ data). This framework enables the streaming of 3D+ data to visualization devices (displays, AR, VR) for presentation.\r\n\r\n" + "@value": "This document specifies how Web Coverage Service (WCS) clients and servers can communicate over the Internet using HTTP GET with key/value pair (KVP) encoding." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -31655,2103 +31044,1244 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-035" + "@value": "09-147r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-18: 3D+ Data Streaming Engineering Report" + "@value": "OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/is", + "@id": "http://www.opengis.net/def/doc-type/per", "http://www.w3.org/2004/02/skos/core#narrower": [ { - "@id": "http://www.opengis.net/def/docs/15-098r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-097r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-120r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-102r2" - }, - { - "@id": "http://www.opengis.net/def/docs/15-042r5" - }, - { - "@id": "http://www.opengis.net/def/docs/12-000" - }, - { - "@id": "http://www.opengis.net/def/docs/17-069r4" - }, - { - "@id": "http://www.opengis.net/def/docs/20-050" - }, - { - "@id": "http://www.opengis.net/def/docs/12-168r6" - }, - { - "@id": "http://www.opengis.net/def/docs/18-067r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-008" - }, - { - "@id": "http://www.opengis.net/def/docs/18-058r1" - }, - { - "@id": "http://www.opengis.net/def/docs/22-049r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-099r1" - }, - { - "@id": "http://www.opengis.net/def/docs/08-028r7" - }, - { - "@id": "http://www.opengis.net/def/docs/12-006" - }, - { - "@id": "http://www.opengis.net/def/docs/17-089r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-007r7" - }, - { - "@id": "http://www.opengis.net/def/docs/17-083r4" - }, - { - "@id": "http://www.opengis.net/def/docs/01-009" - }, - { - "@id": "http://www.opengis.net/def/docs/09-000" - }, - { - "@id": "http://www.opengis.net/def/docs/16-060r2" - }, - { - "@id": "http://www.opengis.net/def/docs/15-111r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-086r6" - }, - { - "@id": "http://www.opengis.net/def/docs/11-017" - }, - { - "@id": "http://www.opengis.net/def/docs/23-024" - }, - { - "@id": "http://www.opengis.net/def/docs/22-022r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-000" - }, - { - "@id": "http://www.opengis.net/def/docs/17-066r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-147r2" - }, - { - "@id": "http://www.opengis.net/def/docs/17-007r1" - }, - { - "@id": "http://www.opengis.net/def/docs/13-057r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-024r4" - }, - { - "@id": "http://www.opengis.net/def/docs/14-083r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-131r6" - }, - { - "@id": "http://www.opengis.net/def/docs/10-126r4" - }, - { - "@id": "http://www.opengis.net/def/docs/15-113r5" - }, - { - "@id": "http://www.opengis.net/def/docs/10-032r8" - }, - { - "@id": "http://www.opengis.net/def/docs/15-108r3" - }, - { - "@id": "http://www.opengis.net/def/docs/08-068r2" - }, - { - "@id": "http://www.opengis.net/def/docs/20-057" - }, - { - "@id": "http://www.opengis.net/def/docs/16-007r3" + "@id": "http://www.opengis.net/def/docs/18-057" }, { - "@id": "http://www.opengis.net/def/docs/15-112r3" + "@id": "http://www.opengis.net/def/docs/16-039r2" }, { - "@id": "http://www.opengis.net/def/docs/19-079r2" + "@id": "http://www.opengis.net/def/docs/15-050r3" }, { - "@id": "http://www.opengis.net/def/docs/10-070r2" + "@id": "http://www.opengis.net/def/docs/09-016" }, { - "@id": "http://www.opengis.net/def/docs/18-062r2" + "@id": "http://www.opengis.net/def/docs/10-002" }, { - "@id": "http://www.opengis.net/def/docs/10-140r2" + "@id": "http://www.opengis.net/def/docs/20-029" }, { - "@id": "http://www.opengis.net/def/docs/16-007r5" + "@id": "http://www.opengis.net/def/docs/10-060r1" }, { - "@id": "http://www.opengis.net/def/docs/19-011r4" + "@id": "http://www.opengis.net/def/docs/10-036r2" }, { - "@id": "http://www.opengis.net/def/docs/15-113r3" + "@id": "http://www.opengis.net/def/docs/18-022r1" }, { - "@id": "http://www.opengis.net/def/docs/05-078r4" + "@id": "http://www.opengis.net/def/docs/09-032" }, { - "@id": "http://www.opengis.net/def/docs/19-086r4" + "@id": "http://www.opengis.net/def/docs/14-008" }, { - "@id": "http://www.opengis.net/def/docs/16-032r2" + "@id": "http://www.opengis.net/def/docs/14-038r1" }, { - "@id": "http://www.opengis.net/def/docs/15-113r6" + "@id": "http://www.opengis.net/def/docs/17-026r1" }, { - "@id": "http://www.opengis.net/def/docs/11-052r4" + "@id": "http://www.opengis.net/def/docs/23-025" }, { - "@id": "http://www.opengis.net/def/docs/09-083r3" + "@id": "http://www.opengis.net/def/docs/11-095r1" }, { - "@id": "http://www.opengis.net/def/docs/09-149r1" + "@id": "http://www.opengis.net/def/docs/12-152r1" }, { - "@id": "http://www.opengis.net/def/docs/18-010r7" + "@id": "http://www.opengis.net/def/docs/16-031r1" }, { - "@id": "http://www.opengis.net/def/docs/17-079r1" + "@id": "http://www.opengis.net/def/docs/19-070" }, { - "@id": "http://www.opengis.net/def/docs/21-006r2" + "@id": "http://www.opengis.net/def/docs/15-118r1" }, { - "@id": "http://www.opengis.net/def/docs/09-001" + "@id": "http://www.opengis.net/def/docs/18-089" }, { - "@id": "http://www.opengis.net/def/docs/22-047r1" + "@id": "http://www.opengis.net/def/docs/18-049r1" }, { - "@id": "http://www.opengis.net/def/docs/18-088" + "@id": "http://www.opengis.net/def/docs/20-038" }, { - "@id": "http://www.opengis.net/def/docs/14-100r2" + "@id": "http://www.opengis.net/def/docs/18-085" }, { - "@id": "http://www.opengis.net/def/docs/18-058" + "@id": "http://www.opengis.net/def/docs/20-020" }, { - "@id": "http://www.opengis.net/def/docs/14-005r3" + "@id": "http://www.opengis.net/def/docs/10-088r3" }, { - "@id": "http://www.opengis.net/def/docs/06-009r6" + "@id": "http://www.opengis.net/def/docs/20-015r2" }, { - "@id": "http://www.opengis.net/def/docs/06-042" + "@id": "http://www.opengis.net/def/docs/16-030" }, { - "@id": "http://www.opengis.net/def/docs/16-103r2" + "@id": "http://www.opengis.net/def/docs/21-055" }, { - "@id": "http://www.opengis.net/def/docs/16-105r2" + "@id": "http://www.opengis.net/def/docs/10-069r2" }, { - "@id": "http://www.opengis.net/def/docs/18-073r2" + "@id": "http://www.opengis.net/def/docs/09-015" }, { - "@id": "http://www.opengis.net/def/docs/15-001r4" + "@id": "http://www.opengis.net/def/docs/15-010r4" }, { - "@id": "http://www.opengis.net/def/docs/17-003r2" + "@id": "http://www.opengis.net/def/docs/12-097" }, { - "@id": "http://www.opengis.net/def/docs/05-005" + "@id": "http://www.opengis.net/def/docs/14-049" }, { - "@id": "http://www.opengis.net/def/docs/21-057" + "@id": "http://www.opengis.net/def/docs/22-024r2" }, { - "@id": "http://www.opengis.net/def/docs/16-079" + "@id": "http://www.opengis.net/def/docs/18-074" }, { - "@id": "http://www.opengis.net/def/docs/21-026" + "@id": "http://www.opengis.net/def/docs/19-010r2" }, { - "@id": "http://www.opengis.net/def/docs/09-148r1" + "@id": "http://www.opengis.net/def/docs/12-096" }, { - "@id": "http://www.opengis.net/def/docs/09-026r1" + "@id": "http://www.opengis.net/def/docs/16-093r1" }, { - "@id": "http://www.opengis.net/def/docs/99-054" + "@id": "http://www.opengis.net/def/docs/17-088r1" }, { - "@id": "http://www.opengis.net/def/docs/19-086r5" + "@id": "http://www.opengis.net/def/docs/21-028" }, { - "@id": "http://www.opengis.net/def/docs/07-068r4" + "@id": "http://www.opengis.net/def/docs/16-033r1" }, { - "@id": "http://www.opengis.net/def/docs/12-084r2" + "@id": "http://www.opengis.net/def/docs/11-113r1" }, { - "@id": "http://www.opengis.net/def/docs/06-141r6" + "@id": "http://www.opengis.net/def/docs/15-068r2" }, { - "@id": "http://www.opengis.net/def/docs/15-043r3" + "@id": "http://www.opengis.net/def/docs/11-073r2" }, { - "@id": "http://www.opengis.net/def/docs/10-090r3" + "@id": "http://www.opengis.net/def/docs/18-086r1" }, { - "@id": "http://www.opengis.net/def/docs/12-128r17" + "@id": "http://www.opengis.net/def/docs/12-118" }, { - "@id": "http://www.opengis.net/def/docs/22-051r7" + "@id": "http://www.opengis.net/def/docs/23-020r2" }, { - "@id": "http://www.opengis.net/def/docs/15-042r6" + "@id": "http://www.opengis.net/def/docs/09-012" }, { - "@id": "http://www.opengis.net/def/docs/17-080r2" + "@id": "http://www.opengis.net/def/docs/18-048r1" }, { - "@id": "http://www.opengis.net/def/docs/15-018r2" + "@id": "http://www.opengis.net/def/docs/12-093" }, { - "@id": "http://www.opengis.net/def/docs/12-128r18" + "@id": "http://www.opengis.net/def/docs/21-025" }, { - "@id": "http://www.opengis.net/def/docs/19-008r4" + "@id": "http://www.opengis.net/def/docs/15-025r2" }, { - "@id": "http://www.opengis.net/def/docs/99-050" + "@id": "http://www.opengis.net/def/docs/12-018r1" }, { - "@id": "http://www.opengis.net/def/docs/08-085r4" + "@id": "http://www.opengis.net/def/docs/21-035r1" }, { - "@id": "http://www.opengis.net/def/docs/08-094r1" + "@id": "http://www.opengis.net/def/docs/19-015" }, { - "@id": "http://www.opengis.net/def/docs/16-007r4" + "@id": "http://www.opengis.net/def/docs/14-029r2" }, { - "@id": "http://www.opengis.net/def/docs/12-128r14" + "@id": "http://www.opengis.net/def/docs/21-008" }, { - "@id": "http://www.opengis.net/def/docs/16-106r2" + "@id": "http://www.opengis.net/def/docs/19-027r2" }, { - "@id": "http://www.opengis.net/def/docs/06-121r3" + "@id": "http://www.opengis.net/def/docs/18-021" }, { - "@id": "http://www.opengis.net/def/docs/12-128r19" + "@id": "http://www.opengis.net/def/docs/18-029" }, { - "@id": "http://www.opengis.net/def/docs/09-127r2" + "@id": "http://www.opengis.net/def/docs/19-046r1" }, { - "@id": "http://www.opengis.net/def/docs/13-026r8" + "@id": "http://www.opengis.net/def/docs/20-032" }, { - "@id": "http://www.opengis.net/def/docs/16-008r1" + "@id": "http://www.opengis.net/def/docs/17-042" }, { - "@id": "http://www.opengis.net/def/docs/22-050r1" + "@id": "http://www.opengis.net/def/docs/18-090r2" }, { - "@id": "http://www.opengis.net/def/docs/17-069r3" + "@id": "http://www.opengis.net/def/docs/19-083" }, { - "@id": "http://www.opengis.net/def/docs/10-129r1" + "@id": "http://www.opengis.net/def/docs/20-073" }, { - "@id": "http://www.opengis.net/def/docs/17-066r1" + "@id": "http://www.opengis.net/def/docs/13-053r1" }, { - "@id": "http://www.opengis.net/def/docs/16-107r2" + "@id": "http://www.opengis.net/def/docs/17-036" }, { - "@id": "http://www.opengis.net/def/docs/12-000r2" + "@id": "http://www.opengis.net/def/docs/19-032" }, { - "@id": "http://www.opengis.net/def/docs/15-112r4" + "@id": "http://www.opengis.net/def/docs/24-008" }, { - "@id": "http://www.opengis.net/def/docs/08-007r1" + "@id": "http://www.opengis.net/def/docs/19-040" }, { - "@id": "http://www.opengis.net/def/docs/12-100r1" + "@id": "http://www.opengis.net/def/docs/14-114r1" }, { - "@id": "http://www.opengis.net/def/docs/12-007r2" + "@id": "http://www.opengis.net/def/docs/16-063" }, { - "@id": "http://www.opengis.net/def/docs/07-144r4" + "@id": "http://www.opengis.net/def/docs/20-037" }, { - "@id": "http://www.opengis.net/def/docs/11-014r3" + "@id": "http://www.opengis.net/def/docs/16-041r1" }, { - "@id": "http://www.opengis.net/def/docs/12-132r4" + "@id": "http://www.opengis.net/def/docs/11-061r1" }, { - "@id": "http://www.opengis.net/def/docs/11-030r1" + "@id": "http://www.opengis.net/def/docs/09-041r3" }, { - "@id": "http://www.opengis.net/def/docs/17-083r2" + "@id": "http://www.opengis.net/def/docs/18-038r2" }, { - "@id": "http://www.opengis.net/def/docs/15-045r7" + "@id": "http://www.opengis.net/def/docs/14-044" }, { - "@id": "http://www.opengis.net/def/docs/14-111r6" + "@id": "http://www.opengis.net/def/docs/14-039" }, { - "@id": "http://www.opengis.net/def/docs/23-008r3" + "@id": "http://www.opengis.net/def/docs/21-039r1" }, { - "@id": "http://www.opengis.net/def/docs/16-083r2" + "@id": "http://www.opengis.net/def/docs/09-129" }, { - "@id": "http://www.opengis.net/def/docs/16-071r3" + "@id": "http://www.opengis.net/def/docs/18-028r2" }, { - "@id": "http://www.opengis.net/def/docs/17-047r1" + "@id": "http://www.opengis.net/def/docs/11-091" }, { - "@id": "http://www.opengis.net/def/docs/15-078r6" + "@id": "http://www.opengis.net/def/docs/21-021" }, { - "@id": "http://www.opengis.net/def/docs/14-055r2" + "@id": "http://www.opengis.net/def/docs/08-176r1" }, { - "@id": "http://www.opengis.net/def/docs/07-110r4" + "@id": "http://www.opengis.net/def/docs/10-194r3" }, { - "@id": "http://www.opengis.net/def/docs/16-100r2" + "@id": "http://www.opengis.net/def/docs/19-016r1" }, { - "@id": "http://www.opengis.net/def/docs/07-057r7" + "@id": "http://www.opengis.net/def/docs/17-027" }, { - "@id": "http://www.opengis.net/def/docs/17-086r3" + "@id": "http://www.opengis.net/def/docs/09-035" }, { - "@id": "http://www.opengis.net/def/docs/21-056r11" + "@id": "http://www.opengis.net/def/docs/16-064r1" }, { - "@id": "http://www.opengis.net/def/docs/13-131r1" + "@id": "http://www.opengis.net/def/docs/22-041" }, { - "@id": "http://www.opengis.net/def/docs/12-128r12" + "@id": "http://www.opengis.net/def/docs/19-023r1" }, { - "@id": "http://www.opengis.net/def/docs/15-042r3" + "@id": "http://www.opengis.net/def/docs/16-062" }, { - "@id": "http://www.opengis.net/def/docs/05-077r4" + "@id": "http://www.opengis.net/def/docs/22-023r2" }, { - "@id": "http://www.opengis.net/def/docs/11-038R2" + "@id": "http://www.opengis.net/def/docs/16-020" }, { - "@id": "http://www.opengis.net/def/docs/07-006r1" + "@id": "http://www.opengis.net/def/docs/21-064" }, { - "@id": "http://www.opengis.net/def/docs/07-074" + "@id": "http://www.opengis.net/def/docs/19-012r1" }, { - "@id": "http://www.opengis.net/def/docs/08-059r3" + "@id": "http://www.opengis.net/def/docs/17-021" }, { - "@id": "http://www.opengis.net/def/docs/10-157r4" + "@id": "http://www.opengis.net/def/docs/11-139r2" }, { - "@id": "http://www.opengis.net/def/docs/09-146r6" + "@id": "http://www.opengis.net/def/docs/09-053r5" }, { - "@id": "http://www.opengis.net/def/docs/08-085r8" + "@id": "http://www.opengis.net/def/docs/14-017" }, { - "@id": "http://www.opengis.net/def/docs/09-110r4" + "@id": "http://www.opengis.net/def/docs/20-034" }, { - "@id": "http://www.opengis.net/def/docs/18-043r3" + "@id": "http://www.opengis.net/def/docs/23-027" }, { - "@id": "http://www.opengis.net/def/docs/07-036" + "@id": "http://www.opengis.net/def/docs/16-021r1" }, { - "@id": "http://www.opengis.net/def/docs/18-000" + "@id": "http://www.opengis.net/def/docs/10-155" }, { - "@id": "http://www.opengis.net/def/docs/16-101r2" + "@id": "http://www.opengis.net/def/docs/16-037" }, { - "@id": "http://www.opengis.net/def/docs/14-065" + "@id": "http://www.opengis.net/def/docs/17-032r2" }, { - "@id": "http://www.opengis.net/def/docs/12-128r10" + "@id": "http://www.opengis.net/def/docs/18-032r2" }, { - "@id": "http://www.opengis.net/def/docs/09-025r2" + "@id": "http://www.opengis.net/def/docs/17-045" }, { - "@id": "http://www.opengis.net/def/docs/06-104r4" + "@id": "http://www.opengis.net/def/docs/20-036" }, { - "@id": "http://www.opengis.net/def/docs/14-084r2" + "@id": "http://www.opengis.net/def/docs/21-042" }, { - "@id": "http://www.opengis.net/def/docs/12-080r2" + "@id": "http://www.opengis.net/def/docs/15-065r1" }, { - "@id": "http://www.opengis.net/def/docs/06-121r9" + "@id": "http://www.opengis.net/def/docs/09-006" }, { - "@id": "http://www.opengis.net/def/docs/05-047r3" + "@id": "http://www.opengis.net/def/docs/22-043r1" }, { - "@id": "http://www.opengis.net/def/docs/15-112r2" + "@id": "http://www.opengis.net/def/docs/12-162r1" }, { - "@id": "http://www.opengis.net/def/docs/10-025r1" + "@id": "http://www.opengis.net/def/docs/11-116" }, { - "@id": "http://www.opengis.net/def/docs/07-098r1" + "@id": "http://www.opengis.net/def/docs/15-048r3" }, { - "@id": "http://www.opengis.net/def/docs/12-019" + "@id": "http://www.opengis.net/def/docs/16-043" }, { - "@id": "http://www.opengis.net/def/docs/13-133r1" + "@id": "http://www.opengis.net/def/docs/13-046r2" }, { - "@id": "http://www.opengis.net/def/docs/06-103r4" + "@id": "http://www.opengis.net/def/docs/18-026r1" }, { - "@id": "http://www.opengis.net/def/docs/08-085r5" + "@id": "http://www.opengis.net/def/docs/21-029" }, { - "@id": "http://www.opengis.net/def/docs/16-104r2" + "@id": "http://www.opengis.net/def/docs/11-055" }, { - "@id": "http://www.opengis.net/def/docs/19-045r3" + "@id": "http://www.opengis.net/def/docs/14-016" }, { - "@id": "http://www.opengis.net/def/docs/20-010" + "@id": "http://www.opengis.net/def/docs/19-025r1" }, { - "@id": "http://www.opengis.net/def/docs/08-068r3" + "@id": "http://www.opengis.net/def/docs/18-094r1" }, { - "@id": "http://www.opengis.net/def/docs/16-032r3" + "@id": "http://www.opengis.net/def/docs/23-050" }, { - "@id": "http://www.opengis.net/def/docs/21-065r2" + "@id": "http://www.opengis.net/def/docs/11-107" }, { - "@id": "http://www.opengis.net/def/docs/04-094" + "@id": "http://www.opengis.net/def/docs/23-028" }, { - "@id": "http://www.opengis.net/def/docs/12-176r7" + "@id": "http://www.opengis.net/def/docs/16-115" }, { - "@id": "http://www.opengis.net/def/docs/11-165r2" + "@id": "http://www.opengis.net/def/docs/17-024" }, { - "@id": "http://www.opengis.net/def/docs/19-072" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/18-009", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ - { - "@type": "xsd:date", - "@value": "2020-02-24" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/11-093r2" + }, { - "@value": "P S Acharya, Scott Simmons, A Kaushal, M K Munshi " - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/21-054" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/09-036r2" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/09-072" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=77858" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/16-052" + }, { - "@language": "en", - "@value": "OGC India Plugfest - 2017 (OIP-2017) Engineering Report" + "@id": "http://www.opengis.net/def/docs/16-028r1" }, { - "@language": "en", - "@value": "18-009" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/16-053r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/10-132" + }, { - "@value": "The Open Geospatial Consortium (OGC) and the Department of Science & Technology (DST) under the Government of India conducted the OGC India Plugfest 2017 (OIP-2017). The OIP-2017 was targeted at enhancing the interoperability among geospatial products and web services based on OGC standards within the Indian Geospatial Information (GI) community. The successful conclusion of OIP-2017 will assist National Spatial Data Infrastructure (NSDI) under DST to provide guidance on best practices using OGC standards for development of applications in several important & flagship schemes/programmes of the Government such as Smart Cities, Atal Mission for Rejuvenation through Urban Trasnformation (AMRUT); National Land Records Moderinisation Programme (NLRMP); Clean India (Swatchh Bharat – Urban & Rural); National Mission on Clean Ganga; Compensatory Afforestation Fund Management & Planning Authority (CAMPA); State SDIs; Digital India, and others.\r\nThis engineering report written jointly by OGC and DST is addressed to both the domestic (Indian) and international audiences.\r\nOIP-2017 was funded by the OGC India Foundation with supporting OGC staff resources from the OGC Innovation Program.\r\n" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/17-029r1" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/16-094r3" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-009" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/17-048" + }, { - "@language": "en", - "@value": "OGC India Plugfest - 2017 (OIP-2017) Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/12-032r2", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/21-027" + }, { - "@type": "xsd:date", - "@value": "2012-12-05" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/18-009" + }, { - "@value": "Rahul Thakkar, Michael Maraist" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/14-009r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/bp" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/10-059r2" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/15-057r2" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=50486" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/18-087r5" + }, { - "@language": "en", - "@value": "WAMI Services: Dissemination Services for Wide Area Motion Imagery - Best Practice" + "@id": "http://www.opengis.net/def/docs/17-041" }, { - "@language": "en", - "@value": "12-032r2" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/17-037" + }, { - "@id": "http://www.opengis.net/def/doc-type/bp" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/19-007" + }, { - "@value": "This OGC Best Practice (BP) describes web interface specifications for the access and dissemination of Wide Area Motion Imagery (WAMI) products and metadata. This BP also describes a framework and interface specifications common to all WAMI services. A WAMI - Primer has been developed to help you implement this Best Practice." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/12-018r2" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/11-072r2" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-032r2" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/18-046" + }, { - "@language": "en", - "@value": "WAMI Services: Dissemination Services for Wide Area Motion Imagery - Best Practice" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/16-047r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/16-092r2" + }, { - "@type": "xsd:date", - "@value": "2017-05-12" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/19-030r1" + }, { - "@value": "Martin Klopfer" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/19-081" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/20-012" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/15-058" + }, { - "@id": "https://docs.ogc.org/per/16-047r1.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/20-042" + }, { - "@language": "en", - "@value": "Testbed-12 General Feature Model Engineering Report" + "@id": "http://www.opengis.net/def/docs/10-094" }, { - "@language": "en", - "@value": "16-047r1" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/19-018" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/20-091" + }, { - "@value": "With a growing requirement to carry out complex analysis in large multi-disciplinary, heterogeneous data collections, an approach is required to extract equivalent information from dissimilar content. The more information can be normalized, the easier it will be to correlate the content. Given that almost all data has a spatio-temporal component, this ER will look into the idea of defining a Spatial-Temporal Service and analyze which collection of data types, operations and architecture patterns would be necessary to spatial-temporal enable any content. This OGC® document reviews the General Feature Model and gives guidelines for necessary modifications to broaden its scope, so that it can be re-used for non-geospatial centric applications and extended as necessary into a general model for all object types." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/18-050r1" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/12-147" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-047r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/16-048r1" + }, { - "@language": "en", - "@value": "Testbed-12 General Feature Model Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/14-083r2", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/14-086r1" + }, { - "@type": "xsd:date", - "@value": "2015-02-17" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/21-032" + }, { - "@value": "Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/17-025r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/12-103r3" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/19-075r1" + }, { - "@id": "https://docs.ogc.org/is/14-083r2/14-083r2.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/11-085r1" + }, { - "@language": "en", - "@value": "Moving Features Encoding Part I: XML Core" + "@id": "http://www.opengis.net/def/docs/23-047" }, { - "@language": "en", - "@value": "14-083r2" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/14-001" + }, { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/20-090" + }, { - "@value": "This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/22-017" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/12-094" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-083r2" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/09-138" + }, { - "@language": "en", - "@value": "OGC® Moving Features Encoding Part I: XML Core" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/11-158", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/09-033" + }, { - "@type": "xsd:date", - "@value": "2011-10-18" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/16-014r2" + }, { - "@value": "Jim Greenwood" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/08-124r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/isc" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/18-025" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/18-047r3" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=46436" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/14-007" + }, { - "@language": "en", - "@value": "11-158" + "@id": "http://www.opengis.net/def/docs/20-041" }, { - "@language": "en", - "@value": "Corrigendum 2 for OGC Web Services Common Specification v 1.1.0 - Exception Report" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/11-013r6" + }, { - "@id": "http://www.opengis.net/def/doc-type/isc" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/18-083" + }, { - "@value": "This document defines the corrigendum change notes for NOTE: WMS 1.3 and ISO 19128 are the same documents." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36111,35 +34409,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-042r6" + "@value": "06-042" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC TimeseriesML 1.3 – XML Encoding of the Timeseries Profile of Observations and Measurements" + "@value": "OpenGIS Web Map Service (WMS) Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-057r3", + "@id": "http://www.opengis.net/def/docs/07-124r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-02-09" + "@value": "2008-09-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jolyon Martin" + "@value": "Chris Holmes" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -36149,27 +34447,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13885" + "@id": "https://portal.ogc.org/files/?artifact_id=28086" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Minimal Application Profile for EO Products" + "@value": "OWS-5 KML Engineering Report" }, { "@language": "en", - "@value": "05-057r3" + "@value": "07-124r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The services proposed in this profile are intended to support the identification and subsequent ordering of\r\nEO data products from previously identified data collections. The intent of this initial profile is to\r\ndescribe a minimum interface that can be supported by many data providers (satellite operators, data\r\ndistributors " + "@value": "This Discussion Paper is about the use of KML, an encoding used to express geographic annotation and visualization on existing or future web-based online maps (2d) and earth browsers (3d). KML uses a tag-based structure with nested elements and attributes and is based on the XML standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36180,35 +34478,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-057r3" + "@value": "07-124r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Minimal Application Profile for EO Products" + "@value": "OWS-5 KML Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-093", + "@id": "http://www.opengis.net/def/docs/09-149r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-10-24" + "@value": "2010-10-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas H.G. Lankester" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -36218,27 +34516,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=16075" + "@id": "https://portal.ogc.org/files/?artifact_id=41441" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Map Services - Application Profile for EO Products" + "@value": "Web Coverage Service 2.0 Interface Standard - XML/SOAP Protocol Binding Extension" }, { "@language": "en", - "@value": "06-093" + "@value": "09-149r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The WMS configuration proposed in this profile is intended to support the interactive visualization and evaluation of Earth Observation (EO) data products. The profile sets out to describe a consistent Web Map Server (WMS) configuration that can be supported by many data providers (satellite operators, data distributors...), most of whom have existing (and relatively complex) facilities for the management of these data." + "@value": "This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using SOAP with XML encoding." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36249,35 +34547,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-093" + "@value": "09-149r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Map Services - Application Profile for EO Products" + "@value": "OGC® Web Coverage Service 2.0 Interface Standard - XML/SOAP Protocol Binding Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-018", + "@id": "http://www.opengis.net/def/docs/16-007r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-01-05" + "@value": "2018-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Yves Coene, Christophe Noel" + "@value": "Sara Saeedi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -36287,27 +34585,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-018.html" + "@id": "https://portal.ogc.org/files/16-007r4" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-018" + "@value": "16-007r4" }, { "@language": "en", - "@value": "Testbed-18: Secure Asynchronous Catalog Engineering Report" + "@value": "Volume 11: OGC CDB Core Standard Conceptual Model" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed-18 Engineering Report (ER) describes the results of the Secure, Asynchronous Catalogs Task in the Testbed-18 Catalogs, Filtering, and Moving Features (CMF) thread. This task explored the following.\r\n\r\nHow search processes that are supported in a classical OGC Catalogue Service for the Web (CSW)/ISO 19115 environment can be supported through tailoring of the OGC API-Records specification.\r\nHow an asynchronous catalog scenario can be supported in which metadata publishers push new data to catalog instances that lead to new or updated catalog entries and how subscribers are informed about these updates.\r\nHow Data Centric Security (DCS) can be applied in combination with OGC API-Records to allow encrypted delivery and access of catalog metadata between communication partners." + "@value": "This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB Standard. The objective of this document is to provide an abstract core conceptual model for a CDB data store (repository). The model is represented using UML (unified modeling language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering the UML diagrams and documentation from the original CDB submission as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113r5].\r\n\r\nNOTE: The simulation community uses the term “synthetic environment data” to mean all the digital data stored in some database or structured data store that is required for use by simulation clients. From the geospatial community perspective, these data are essentially the same as GIS data but with, in some cases, special attributes, such as radar reflectivity.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36318,30 +34616,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-018" + "@value": "16-007r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-18: Secure Asynchronous Catalog Engineering Report" + "@value": "Volume 11: OGC CDB Core Standard Conceptual Model" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-159", + "@id": "http://www.opengis.net/def/docs/10-128", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-10-19" + "@value": "2010-10-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Maidment, Ben Domenico, Alastair Gemmell, Kerstin Lehnert, David Tarboton, Ilya Zaslavsky" + "@value": "Luis Bermudez" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -36356,17 +34654,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46471&version=1" + "@id": "https://portal.ogc.org/files/?artifact_id=41359" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-159" + "@value": "OGC Compliance Testing White Paper" }, { "@language": "en", - "@value": "The Open Geospatial Consortium and EarthCube" + "@value": "10-128" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -36376,7 +34674,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "EarthCube aims to create an integrated system to access, analyze and share information that is\r\nused by the entire geosciences community. The Open Geospatial Consortium (OGC) is an\r\norganization of which more than four hundred companies and agencies are members, whose\r\npurpose is to create open source standards for sharing geospatial and observational information.\r\nThe authors of this paper are users of OGC standards in our work in hydrology, meteorology,\r\nclimatology, oceanography and in the solid earth sciences, in other words, in key disciplinary\r\nfields that contribute to the Geosciences. Moreover, the OGC has an effective process for\r\nengaging individuals from many countries in standards development and interoperability testing\r\nthat encourages them to set aside the roles they play in their home organizations and instead\r\nfocus just on what is needed to share a particular class of information across the globe. This\r\npaper examines the hypothesis that an OGC-like process could be useful for broader sharing of\r\ninformation in the geosciences." + "@value": "This white paper describes the OGC Compliance Testing Program. It provides\r\ninformation about:\r\n• The need for compliance testing to enable interoperability\r\n• How to obtain compliance certification\r\n• The difference between implementing and being certified\r\n• How compliance benefits providers and users of technology\r\n• The proper use of the “Certified OGC Compliant” mark\r\n• Suggested language for procurement documents\r\n• Trademark licensing fees\r\n• An example of an OGC compliance test " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36387,35 +34685,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-159" + "@value": "10-128" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "The Open Geospatial Consortium and EarthCube" + "@value": "OGC Compliance Testing White Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-077r2", + "@id": "http://www.opengis.net/def/docs/04-038r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-01-20" + "@value": "2004-10-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jay Freeman, Kevin Bentley, Ronald Moore, Samuel Chambers, Glen Quesenberry" + "@value": "Uwe Voges, Kristian Senkler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -36425,27 +34723,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=82553" + "@id": "https://portal.ogc.org/files/?artifact_id=6495" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CDB, Leveraging GeoPackage Discussion Paper" + "@value": "ISO19115/ISO19119 Application Profile for CSW 2.0" }, { "@language": "en", - "@value": "18-077r2" + "@value": "04-038r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This paper offers the results of research, design, and prototype efforts to present the OGC standards working group an approach to creating “GeoCDB”—a technology mashing of GeoPackage and OGC CDB—as a deterministic repository of easily read data geospatial datasets suitable for storage, runtime access, and dissemination for live, virtual, constructive, gaming, and mission command (MC) systems." + "@value": "This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36456,35 +34754,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-077r2" + "@value": "04-038r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC CDB, Leveraging GeoPackage Discussion Paper" + "@value": "ISO19115/ISO19119 Application Profile for CSW 2.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-039r3", + "@id": "http://www.opengis.net/def/docs/16-055", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-24" + "@value": "2017-05-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Irina Dornblut, Rob Atkinson" + "@value": "Jeff Harrison" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -36494,27 +34792,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55157" + "@id": "https://docs.ogc.org/per/16-055.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "HY_Features: a Common Hydrologic Feature Model" + "@value": "16-055" }, { "@language": "en", - "@value": "11-039r3" + "@value": "Testbed-12 Compression Techniques Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Common semantics support the reference of features to the concept they represent and the integration of data proceed using the semantic framework such mappings provide. However there is no standard conceptual model for hydrologic feature identification. Different models of hydrologic processes, and different scales of detail, lead to a variety of information models to describe these features, and to different and mostly incompatible sets of feature identifiers. \r\nThis document describes requirements and a proposed design for a domain model of hydrologic features as a set of interrelated Application Schemas using the ISO 19109 General Feature Model, \r\n" + "@value": "This Open Geospatial Consortium (OGC) document provides an analysis of the prototype implementations, approaches and performance aspects of data size reduction and compression techniques explored in OGC Testbed 12. Specifically, it describes work done during Testbed 12 investigating compression for geospatial data sets on OGC Web Feature Service (WFS) using W3C Efficient XML Interchange (EXI) Format 1.0 (Second Edition).\r\n\r\nThe investigation focused on extending WFS with EXI output formats, and the associated performance aspects of data size reduction and compression techniques. EXI is a compact representation for the Extensible Markup Language (XML) Information Set. EXI is intended to simultaneously optimize performance and the utilization of computational resources. From a practical viewpoint, EXI is designed to reduce the size of XML data exchanged between computer systems.\r\n\r\nEXI uses a grammar-driven approach designed to achieve efficient encodings using an encoding algorithm and a small set of datatype representations. Consequently, EXI processors are described by the W3C as ‘relatively simple’ and ‘can be implemented on devices with limited capacity.’ An EXI processor is used by application programs to encode their structured data into EXI streams and/or to decode EXI to make the structured data accessible." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36525,30 +34823,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-039r3" + "@value": "16-055" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC HY_Features: a Common Hydrologic Feature Model" + "@value": "Testbed-12 Compression Techniques Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-094r3", + "@id": "http://www.opengis.net/def/docs/16-030", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-08-18" + "@value": "2017-05-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Micah Brachman" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -36563,17 +34861,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=70051" + "@id": "https://docs.ogc.org/per/16-030.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-094r3" + "@value": "16-030" }, { "@language": "en", - "@value": "GeoPackage Elevation Extension Interoperability Experiment Engineering Report" + "@value": "Testbed-12 Testbed-12 GeoPackage Mobile Apps Integration Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -36583,7 +34881,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "his OGC Engineering Report (ER) describes the setup, experiments, results and issues generated by the GeoPackage Elevation Extension Interoperability Experiment (GPKG-EE IE). The goal of the GPKG-EE IE was to implement and test a proposed elevation extension to the OGC GeoPackage Encoding Standard (12-128r1). The proposed elevation extension was successfully implemented by several IE participants and was demonstrated using both 2-Dimensional (2D) and 3-Dimensional (3D) software clients at the Washington, DC OGC Technical Committee (TC) meeting in [March 9, 2016]. This ER concludes with several recommendations for addressing remaining technical issues that must be resolved in order to complete a candidate GeoPackage Elevation Extension standard." + "@value": "Testbed 12 work evaluates the interoperability of the Common Map API tool with commercial vendor tools supporting GeoPackage. Ideally data can be shared and exchanged between apps on a single device via GeoPackage. The demonstration will show the vector and/or routing data being used by disparate applications." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36594,35 +34892,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-094r3" + "@value": "16-030" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoPackage Elevation Extension Interoperability Experiment Engineering Report" + "@value": "Testbed-12 Testbed-12 GeoPackage Mobile Apps Integration Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-140", + "@id": "http://www.opengis.net/def/docs/15-042r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-03-30" + "@value": "2016-09-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Yves Coene" + "@value": "James Tomkins, Dominic Lowe" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -36632,27 +34930,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13916" + "@id": "https://docs.ogc.org/is/15-042r3/15-042r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-140" + "@value": "TimeseriesML 1.0 – XML Encoding of the Timeseries Profile of Observations and Measurements" }, { "@language": "en", - "@value": "OWS-3 Imagery Workflow Experiments: Enhanced Service Infrastructure Technology Architecture and Standards in the OWS-3 Testbe" + "@value": "15-042r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the results of an experiment addressing issues relating to the application workflow processing incorporating a variety of OGC specifications. It details the inputs provided to the Open Geospatial Consortium's (OGC) OWS-3 Testbed and the architecture of the testbed related to the ESA Service Support Environment (SSE). \r\nIt is a formal deliverable of work package 6610 of the Enhanced Service Infrastructure Technology (ESIT) project and is a joint Spacebel and Spot Image document.\r\n" + "@value": "TimeseriesML 1.0 defines an XML encoding that implements the OGC Timeseries Profile of Observations and Measurements [OGC 15-043r3], with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of data exchange requirements." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36663,35 +34961,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-140" + "@value": "15-042r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-3 Imagery Workflow Experiments: Enhanced Service Infrastructure Technology Architecture and Standards in the OWS-3 Testbe" + "@value": "TimeseriesML 1.0 – XML Encoding of the Timeseries Profile of Observations and Measurements" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-146r1", + "@id": "http://www.opengis.net/def/docs/16-142", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-10-27" + "@value": "2020-09-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Rob Atkinson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-sap" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -36701,27 +34999,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41438" + "@id": "https://www.w3.org/TR/qb4st/" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-146r1" + "@value": "QB4ST: RDF Data Cube extensions for spatio-temporal components" }, { "@language": "en", - "@value": "GML Application Schema - Coverages" + "@value": "16-142" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-sap" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the GML coverage structure to be used by OGC standards." + "@value": "This document describes an extension to the existing RDF Data Cube ontology to support specification of key metadata required to interpret spatio-temporal data. The RDF Data Cube defines CodedProperties, which relate to a reference system based on a list of terms, QB4ST provides generalized support for numeric and other ordered references systems, particularly Spatial Reference Systems and Temporal Reference Systems. Although RDF Data Cube supports AttributeProperties for metadata of individual observations, the requirement is to specify such metadata per property, rather than for each observation, and thus allow different properties to use different spatial or temporal reference systems. QB4ST also provides for such properties to be defined for a ComponentProperty, or defined at the time of referencing that ComponentProperty in a ComponentSpecification. QB4ST is thus aimed at improving the scope and consistency of dataset metadata, and hence discovery and interpretation of spatio-temporal data through its spatio-temporal reference system and bounding values." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36732,25 +35030,59 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-146r1" + "@value": "16-142" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GML Application Schema - Coverages" + "@value": "QB4ST: RDF Data Cube extensions for spatio-temporal components" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-026", + "@id": "http://www.opengis.net/def/doc-type/d-isc/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Implementation Specification Corrigendum - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Implementation Specification Corrigendum - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/06-189" + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r11" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Implementation Specification Corrigendum - deprecated " + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/21-064", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-04-18" + "@value": "2023-01-10" } ], "http://purl.org/dc/terms/creator": [ @@ -36760,7 +35092,7 @@ ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -36770,27 +35102,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47848" + "@id": "https://docs.ogc.org/per/21-064.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Architecture of an Access Management Federation for Spatial Data and Services in Germany" + "@value": "OGC Disaster Pilot 2021 Engineering Report" }, { "@language": "en", - "@value": "12-026" + "@value": "21-064" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "An Access Management Federation (AMF) is a network of organizations that trust each other for the\r\nmeans of sharing protected resources among each other. Worldwide, many academic AMFs are\r\navailable for the purpose of sharing information and services between academic institutions such\r\nas Universities and Research Organizations. In the academia, some of the well known AMFs are UK\r\nAccess Management Federation (United Kingdom http://www.ukfederation.org.uk/), In Common\r\n(USA http://www.incommon.org/) and DFN-AAI (Germany https://www.aai.dfn.de)." + "@value": "This OGC Disaster Pilot ’21 (DP21) Engineering Report summarizes work done in the Pilot to increase disaster awareness among a range of disaster management stakeholders. Pilot participants implemented components of a data flow ecosystem to leverage analysis-ready earth observations and other datasets (ARD) and produce decision ready indicators (DRI) according to collaboratively developed workflow recipes. DP21 focused on the hazards of flooding, landslides, and pandemic, as well as the interactions and complications between them, in three regions including the Piura and Rimac river basins in Peru; the Red River Basin in Manitoba, Canada; and the greater New Orleans area in Louisiana, United States. The Pilot also prototyped providing information to field practitioners in secure geopackage formats, as well as leveraging linked data and structured web page information to optimize public web searches for disaster information." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36801,30 +35133,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-026" + "@value": "21-064" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Architecture of an Access Management Federation for Spatial Data and Services in Germany" + "@value": "OGC Disaster Pilot 2021 Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-026", + "@id": "http://www.opengis.net/def/docs/23-059", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-10-30" + "@value": "2024-04-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas Forbes, Alberto Olivares, Richard Rombouts" + "@value": "Gobe Hobona, Joana Simoes" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -36839,17 +35171,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=63306" + "@id": "https://docs.ogc.org/per/23-059.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-026" + "@value": "23-059" }, { "@language": "en", - "@value": "Testbed-11 Aviation Feature Schema Recommendations Engineering Report" + "@value": "2023 Open Standards Code Sprint Summary Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -36859,7 +35191,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Developed by EUROCONTROL, the Aviation Feature Schema (AFX) is a template for\r\napplication schemas to implement by adding their operational attributes. For example, the\r\nAirport Mapping format can be implemented by extending AFX. The AFX defines\r\nconcepts of geometry and temporality through predefined classes and properties.\r\nTherefore, these elements need not be redefined by application schemas. This means\r\nimplementations of the AFX abide by the same structure, therefore aiding interoperability\r\nand allowing the rapid development of schemas. The AFX schema is designed to be\r\ngeneric and easily reusable and it is not intended to replace the standard aviation models\r\nsuch as WXXM and AIXM.\r\nThis Engineering Report assesses the suitability of the AFX as a template for lowering\r\nthe GIS entry level for aviation data, providing recommendations of suitability and areas\r\nof improvement. The report is aimed at system and client developers that shall use AFX." + "@value": "Advances in computing, storage, sensing, and other technology areas continue to find a place in the geospatial ecosystem that makes location information findable, accessible, interoperable, and reusable. To enable geospatial standards to meet the likely interoperability needs of future technologies, it is necessary for Standards Development Organizations (SDOs) such as OGC to continue to innovate. Such innovation relies on the ability to develop new standards and improve existing ones to better address emerging interoperability challenges. Code sprints are one of a number of initiative types that OGC conducts to accelerate such innovation. A code sprint is a collaborative and inclusive event driven by innovative and rapid programming with minimal process and organization constraints to support the development of new applications and candidate standards.\r\n\r\nThe focus of this Engineering Report (ER) is a code sprint that was held from October 30th to November 1st, 2023. The code sprint was organized by the Open Geospatial Consortium (OGC) and hosted by Geovation in London, England. The code sprint was sponsored by Ordnance Survey (OS) at the Gold-level, as well as the European Union Satellite Centre (SatCen), US National Geospatial Intelligence Agency (NGA), and the UK Defence Science and Technology Laboratory (Dstl) at the Silver-level. As with previous OGC Code Sprints, a key goal of the October 2023 Open Standards Code Sprint was the acceleration of the development of OGC Standards and their implementation in software products.\r\n\r\nStandards in focus for this code sprint included several OGC API, data model, and encoding standards. In addition to OGC Standards, the code sprint also included a thread focusing on the “GEOINT Imagery Media for ISR” (GIMI) profile of the ISO Base Media File Format (ISOBMFF) and the High Efficiency Image Format (HEIF). The engineering report concludes that the code sprint met all of its objectives and achieved its goal of accelerating the development of OGC Standards and their implementation in software products.\r\n\r\nIn relation to emerging extensions to OGC API Standards, the engineering report concludes that the Publish/Subscribe (PubSub), Security, and Schemas capabilities examined in this code sprint could potentially support other OGC API Standards. Regarding GIMI, the engineering report concludes that with minor changes to popular open-source base libraries a wide range of software can quickly make use of GIMI capabilities.\r\n\r\nRegarding the Model for Underground Data Definition and Integration (MUDDI), the engineering report concludes that the MUDDI Conceptual Model is implementable and could easily be used as the basis for a logical model that can be encoded in a variety of formats including GML, GeoJSON, and Geopackage. As for JSON-FG, the engineering report concludes that due to the evident increase in adoption across the developer community, there is an increasing need to offer validators so that developers can check for compliance more easily.\r\n\r\nThe sprint participants made the following recommendations for future work items on OGC API Standards.\r\n\r\nExtension of OGC API — Records to support faceting and federated search.\r\nUse case experimentation to examine how the Publish/Subscribe approach can support various OGC API standards workflows.\r\nPrototyping and specification on an OpenAPI definition document for the OGC SensorThings API Standard.\r\nAdditional support for multiband raster data in OGC API — Maps/Tiles/Coverages (e.g., multispectral imagery, etc).\r\nThe sprint participants made the following recommendations for future work items on OGC Encoding Standards.\r\n\r\nTiled complex, signed, and floating-point data in multiband raster data.\r\nPerformance benchmarking between various imagery formats, for a variety of use cases.\r\nExtraction of the conceptual model of GMLJP2 to make it applicable to any ISOBMFF profile.\r\nDevelopment of an Implementation Standard for the logical model and encoding of data that conforms to the MUDDI.\r\nUse of the MUDDI logical schema as a template for MUDDI compliance.\r\nThe sprint participants made the following recommendations for future work items on GIMI.\r\n\r\nExtension of open-source base libraries used by several other products for creation and modification of GIMI files.\r\nPrototype streaming of large images from client applications to servers for storage through OGC API — Processes.\r\nPrototyping of a JavaScript Object Notation (JSON) encoded alternative to Key-Length-Value (KLV) metadata for use in GIMI files." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36870,30 +35202,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-026" + "@value": "23-059" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed-11 Aviation Feature Schema Recommendations Engineering Report" + "@value": "2023 Open Standards Code Sprint Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-148r1", + "@id": "http://www.opengis.net/def/docs/12-128r14", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-10-27" + "@value": "2017-08-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -36908,17 +35240,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41440" + "@id": "https://portal.ogc.org/files/?artifact_id=74225" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-148r1" + "@value": "12-128r14" }, { "@language": "en", - "@value": "Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension" + "@value": "GeoPackage Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -36928,7 +35260,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using HTTP POST with XML encoding." + "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -36939,30 +35271,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-148r1" + "@value": "12-128r14" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension" + "@value": "OGC® GeoPackage Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-166r2", + "@id": "http://www.opengis.net/def/docs/08-127", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-02-01" + "@value": "2008-08-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Benjamin Hagedorn" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -36977,17 +35309,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=37257" + "@id": "https://portal.ogc.org/files/?artifact_id=29542" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-166r2" + "@value": "08-127" }, { "@language": "en", - "@value": "Web View Service Discussion Paper" + "@value": "GML 3.2 implementation of XML schemas in 07-000" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -36997,7 +35329,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Web View Service (WVS) is an extendable, interactive, image-based portrayal service for complex three-dimensional geodata such as 3D landscape and city models. 3D geodata is delivered as finally rendered images. Besides color images, relevant thematic and geometrical information such as object identity information or depth data is provided. Additionally, the WVS supports interaction with the portrayed 3D environment, e.g., information retrieval, spatial analysis, and 3D navigation. " + "@value": "" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37008,35 +35340,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-166r2" + "@value": "08-127" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web View Service Discussion Paper" + "@value": "GML 3.2 implementation of XML schemas in 07-000" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-037", + "@id": "http://www.opengis.net/def/docs/14-048", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-10-01" + "@value": "2014-07-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall " + "@value": "Genong (Eugene) Yu, Liping Di" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -37046,27 +35378,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=63334" + "@id": "https://portal.ogc.org/files/?artifact_id=58944" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response" + "@value": "Testbed 10 Cross Community Interoperability (CCI) Hydro Model Interoperability Engineering Report" }, { "@language": "en", - "@value": "15-037" + "@value": "14-048" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Responding to an oil spill requires access to and understanding of many types of information. Effective, coordinated operations for the response are based on a shared, common picture of the situation. Interoperability provides shared situational awareness of the crisis and the response activities. What is needed is a common picture of reality for different organizations that have different views of the spill so that they all can deal with it collectively.\r\nRecent oil spills have provided lessons learned and recommendations on forming a Common Operating Picture for oil spill response. Through a joint project, industry is responding to the call, moving from recommendations to reusable best practices supported by open standards that can be deployed quickly in any region of the globe.\r\nThis architecture report is part of The International Association of Oil & Gas Producers and IPIECA Oil Spill Response - Joint Industry Project (IOGP–IPIECA OSR-JIP) to produce a recommended practice for GIS/mapping in support of oil spill response and for the use of GIS technology and geospatial information in forming a “Common Operating Picture” to support management of the response.\r\nInteroperability seems to be at first a technical topic, but in fact, it is about organization. Interoperability seems to be about the integration of information. What it’s really about is the coordination of organizational behavior. The Oil Spill Response Common Operating Picture (OSR COP) project seeks to facilitate the coordination of organizational response to any oil spill in the future." + "@value": "This OGC® document gives guidelines for enabling interoperability among different hydro data models and services. The demonstration specifically gives out best practices for supporting interoperability among the National Hydrographic Network (NHN) of Canada, the National Hydrographic Dataset Plus (NHD+) of United States, and the OGC HY_Features model developed and proposed by the World Meteorological Organization (WMO). The discussed version of OGC HY_Features was adopted as the mediation bridge model to exchange information among heterogeneous hydrological models." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37077,35 +35409,66 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-037" + "@value": "14-048" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response" + "@value": "OGC® Testbed 10 Cross Community Interoperability (CCI) Hydro Model Interoperability Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-131r3", + "@id": "http://www.opengis.net/def/docs", + "@type": [ + "http://www.w3.org/2004/02/skos/core#ConceptScheme" + ], + "http://purl.org/dc/terms/source": [ + { + "@id": "http://www.opengis.net/def/entities/bodies/ogcna" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/collectionView": [ + { + "@id": "http://www.opengis.net/def/docs/" + } + ], + "http://www.w3.org/2004/02/skos/core#changeNote": [ + { + "@value": "loaded from https://portal.opengeospatial.org/public_ogc/api/docs.php?CITE=1" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "OGC document register with annotations and links" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "OGC Documents" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/03-061", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-10-19" + "@value": "2003-05-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Policy SWG" + "@value": "Geoffrey Ehler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pol" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -37115,27 +35478,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34762&version=2" + "@id": "https://portal.ogc.org/files/?artifact_id=1273" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "The Specification Model - Standard for Modular specifications" + "@value": "03-061" }, { "@language": "en", - "@value": "08-131r3" + "@value": "Critical Infrastructure Collaborative Environment Architecture: Enterprise Viewpoint" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pol" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard contains requirements for writing standards to be used for any document whose\r\neventual purpose is the specification of requirements for software, services or data structures. " + "@value": "*RETIRED* specifies the Enterprise viewpoint for the Critical Infrastructure Collaborative Environment (CICE)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37146,35 +35509,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-131r3" + "@value": "03-061" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "The Specification Model - Standard for Modular specifications" + "@value": "Critical Infrastructure Collaborative Environment Architecture: Enterprise Viewpoint" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-070r3", + "@id": "http://www.opengis.net/def/docs/02-059", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-19" + "@value": "2001-05-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Peter Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -37184,27 +35547,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/16-070r3" + "@id": "https://portal.ogc.org/files/?artifact_id=1171" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-070r3" + "@value": "02-059" }, { "@language": "en", - "@value": "Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage" + "@value": "Filter Encoding" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features." + "@value": "A filter is a construct used to describe constraints on properties of a feature class for the purpose of identifying a subset of feature instances to be operated upon in some way." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37215,35 +35578,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-070r3" + "@value": "02-059" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage" + "@value": "Filter Encoding" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-022r1", + "@id": "http://www.opengis.net/def/docs/05-011", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-01-08" + "@value": "2005-01-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Alexander Lais" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -37253,27 +35616,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-022r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=8837" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-022r1" + "@value": "05-011" }, { "@language": "en", - "@value": "OGC Testbed-15: Scaling Units of Work (EOC, Scale, SEED)" + "@value": "Recommended XML/GML 3.1.1 encoding of common CRS definitions" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed-15 Engineering Report (ER) presents a thorough analysis of the work produced by the Earth Observation Clouds (EOC) threads in OGC Testbeds 13 and 14 in relation to the Scale environment. Scale provides management of automated processing on a cluster of machines and the SEED specification to aid in the discovery and consumption of a discrete unit of work contained within a Docker image. Scale and SEED were both developed for the National Geospatial Intelligence Agency (NGA) of the United States.\r\n\r\nThe ER attempts to explain how the OGC Testbed-13 and OGC Testbed-14 research results of bringing applications/users to the data relate to Scale and SEED.\r\n\r\nChiefly, while comparing the two approaches, the report identifies and describes:\r\n\r\nOpportunities for harmonization or standardization;\r\n\r\nFeatures which must remain separate and the rationale for this;\r\n\r\nThe hard problems which will require additional work; and\r\n\r\nOpportunities which should be examined in future initiatives.\r\n\r\nFor developers, the ER constitutes a technical reference supporting the comparison of the two approaches, thereby enabling developers to make informed choices, understand trade-offs, identify relevant standards and clarify misunderstandings." + "@value": "This document recommends standard XML encodings of data defining some commonly-used coordinate reference systems, including geographic, projected, and vertical CRSs. These recommended encodings are based on GML 3.1.1. These common CRS definitions will often be referenced in data transferred between client and server software that implements various standardised interfaces. This specified definition data encoding is expected to be used by multiple OGC Implementation Specifications. That is, each of these specifications is expected to use a subset and/or superset of this recommended definition data.\r\n\r\nThe position or location of a point can be described using coordinates. Such coordinates are unambiguous only when the coordinate reference system on which those coordinates are based is fully defined. Each position is described by a set of coordinates based on a specified coordinate reference system. Coordinates are often used in datasets in which all coordinates belong to the same coordinate reference system. This paper specifies XML encoding of data defining some coordinate reference systems.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37284,35 +35647,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-022r1" + "@value": "05-011" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Scaling Units of Work (EOC, Scale, SEED)" + "@value": "Recommended XML/GML 3.1.1 encoding of common CRS definitions" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-109r1", + "@id": "http://www.opengis.net/def/docs/16-018", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-03-30" + "@value": "2017-06-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman, Arliss Whiteside" + "@value": "Charles Chen" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -37322,27 +35685,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=896" + "@id": "https://docs.ogc.org/per/16-018.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "99-109r1" + "@value": "Testbed-12 Aviation Architecture Engineering Report" }, { "@language": "en", - "@value": "Topic 9 - Accuracy" + "@value": "16-018" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Topic 9 has been combined into AS Topic 11" + "@value": "This Open Geospatial Consortium (OGC)® Engineering Report (ER) describes the architecture implemented in the OGC Testbed 12 Aviation thread. This report provides an overview of the technical architecture for the interoperable exchange of flight and aeronautical information using OGC services. The aviation architecture consists of multiple components developed by the Aviation thread, as well as specialized engineering reports per each work area. This report will provide an introduction to each work area and contain references to applicable reports. This report also describes the Aviation thread demonstration scenarios, outcomes, and benefits." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37353,35 +35716,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-109r1" + "@value": "16-018" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 9 - Accuracy" + "@value": "Testbed-12 Aviation Architecture Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-042", + "@id": "http://www.opengis.net/def/docs/06-155", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-11" + "@value": "2007-06-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sara Saeedi" + "@value": "Tim Wilson, Renato Primavera, Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -37391,27 +35754,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-042.html" + "@id": "https://portal.ogc.org/files/?artifact_id=20430" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-042" + "@value": "06-155" }, { "@language": "en", - "@value": "Testbed-13: CDB Engineering Report" + "@value": "OWS-4 CSW ebRIM Modelling Guidelines IPR" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) summarizes the CDB sub-thread work in Testbed 13. The document is structured in three phases and includes a feasibility study; the implementation of data models and schemas mapping that are based on the feasibility study results; and a set of OGC web services that implement the CDB in the form of WFS and WCS (Web Coverage Service) instances.\r\n\r\nThis Engineering Report describes:\r\n\r\nThe conceptual model of an OGC CDB 1.0 datastore as a UML (Unified Modeling Language) diagram to show different datasets (the 3D models, vector features and coverages) structure;\r\n\r\nHow to process and use a NAS-based Profile as a CDB feature/attribute data model or a GML-SF0 application schema;\r\n\r\nHow to access, navigate and visualize a CDB dataset using OGC web services (such as WFS and WCS).\r\n\r\nThis work provides insights into:\r\n\r\nThe in-depth study of the OGC CDB 1.0 feature data dictionary and attribution schema;\r\n\r\nThe requirements and constraints for extending the CDB feature data dictionary (FDD) and attribute schemas;\r\n\r\nThe development and prototyping of the WFS and WCS access to the CDB datastore for a NAS based urban military scenario." + "@value": "The OWS-4 CSW ebRIM Modelling Guidelines Interoperability Program Report (IPR) provides guidance for creating a standard methodology for mapping geospatial domain information models to ebRIM [www.oasis-open.org/committees/regrep/documents/2.0/specs/ebrim.pdf]. It also presents the results of mapping specific Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] and Feature Catalog domain models to ebRIM for use with OpenGIS Catalog Service Standard [http://www.opengeospatial.org/standards/cat] implementations in the OWS-4 Initiative [http://www.opengeospatial.org/projects/initiatives/ows-4]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37422,35 +35785,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-042" + "@value": "06-155" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: CDB Engineering Report" + "@value": "OWS-4 CSW ebRIM Modelling Guidelines IPR" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-057r1", + "@id": "http://www.opengis.net/def/docs/12-128r11", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-11-17" + "@value": "2015-04-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Paul daisey" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -37460,27 +35823,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/13-057r1/13-057r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=63378" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "13-057r1" + "@value": "GeoPackage Encoding Standard – With Corrigendum" }, { "@language": "en", - "@value": "Web Coverage Service Interface Standard – Transaction Extension" + "@value": "12-128r11" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Web Coverage Service (WCS) – Transaction Extension (in short: WCS Transaction) defines an extension to the WCS Core [OGC 09-110] for updating coverage offer­ings on a server.\r\n\r\nThis WCS Transaction standard defines three requests:\r\n\r\nInsertCoverage for adding a coverage provided as parameter to the WCS server’s cov­erage offering. After successful completion of the insert request, this coverage will be accessible for all WCS operations.\r\nDeleteCoverage for entirely removing a coverage. The coverage is identified by its coverage id passed in the request, from the WCS server’s coverage offering. After successful completion of this request, this coverage will not be accessible through any WCS operation. However, subsequently a new coverage may be created using the same identifier; such a coverage will bear no relation to the one previously deleted.\r\nUpdateCoverage for modifying parts of a coverage existing in a WCS server’s coverage offering. The coverage is identified by its coverage id passed in the request. As per the OGC Coverage Implementation Schema [OGC 09-146r2], all updates must maintain internal consistency of the coverage.\r\nAll requests defined in this Transaction Extension adhere to the ACID[1] (atomicity, consistency, isolation, durability) concepts of database transactions.\r\n\r\nThe extension name, Transaction, traces back to the database concept of transactions, which has been adopted here." + "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a “native” storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37491,35 +35854,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-057r1" + "@value": "12-128r11" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Coverage Service Interface Standard – Transaction Extension" + "@value": "OGC® GeoPackage Encoding Standard – With Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-021r1", + "@id": "http://www.opengis.net/def/docs/08-071", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-12" + "@value": "2008-09-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Benjamin Pross" + "@value": "Mike Botts" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -37529,27 +35892,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-021r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=29466" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Low Bandwidth & Generalization Engineering Report" + "@value": "08-071" }, { "@language": "en", - "@value": "16-021r1" + "@value": "OWS 5 Engineering Report: Supporting Georeferenceable Imagery" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "For delivering of data that is offered by OGC services over (very) low bandwidth, two options may be considered: On the one hand, the geospatial features remain the same, but compression techniques are used to reduce the size of the data that needs to be transferred. On the other hand, generalization techniques may be used by reducing the details of geometries and/or attributes in order to reduce the amount of data. The aim of this ER is to summarize the results of implementing sample services using compression techniques for DGIWG WFS (U002) and providing generalization processes using WPS (U003). The ER compares the results of the different approaches and infers recommendations and best practices for supporting data delivery of standard data and complex 3D data from OGC services over low and very low bandwidth." + "@value": "The scope of this document is to capture considerations and recommendations on approaches for supporting georeferenceable imagery within the OGC encodings and web services. Georeferenceable imagery is typically imagery coming from a remote sensor that has not been previously geo-rectified, resampled, or regridded. Georeferenceable imagery must be accompanied with information sufficient to allow georectification of the imagery.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37560,35 +35923,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-021r1" + "@value": "08-071" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Low Bandwidth & Generalization Engineering Report" + "@value": "OWS 5 Engineering Report: Supporting Georeferenceable Imagery" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-070r2", + "@id": "http://www.opengis.net/def/docs/18-101", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-11-22" + "@value": "2019-04-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Schut" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -37598,27 +35961,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40095" + "@id": "https://docs.ogc.org/per/18-101.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Georeferenced Table Joining Service Implementation Standard" + "@value": "Vector Tiles Pilot Extension Engineering Report" }, { "@language": "en", - "@value": "10-070r2" + "@value": "18-101" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is the specification for a Table Joining Service (TJS). This OGC standard defines a simple way to describe and exchange tabular data that contains information about geographic objects." + "@value": "The purpose of the OGC Vector Tiles Pilot Extension (VTPExt) was to address portrayal and style encoding concerns that were discovered in the initial phase of the Vector Tiles Pilot (VTP). During the VTPExt, participants selected a common baseline style used by all participants and in some cases created additional style offerings. The work conducted during the VTPExt has adhered to the established findings from the initial VTP documented in the VTP Summary Engineering Report (ER) [1].\r\n\r\nThis document describes the following:\r\n\r\nthe research and evaluation to determine approach(es) to apply styling to Mapbox and GeoJSON Tiled Feature Data through Web Feature Service (WFS) 3.0, Web Map Tile Service (WMTS) 1.0, and GeoPackage (GPKG) 1.2,\r\n\r\nthe styling approach, challenges, and interoperability considerations discovered during the initiative, and\r\n\r\nany extensions required or best practices recommended to facilitate development, encoding, offering, and exchange of styles. This includes how styles are offered from servers, how the desired style offering can be selected by the client from multiple server style offerings (e.g. GetStyles request), and how clients can apply their own styles." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37629,30 +35992,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-070r2" + "@value": "18-101" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS® Georeferenced Table Joining Service Implementation Standard" + "@value": "Vector Tiles Pilot Extension Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-090r1", + "@id": "http://www.opengis.net/def/docs/09-038r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-03-05" + "@value": "2009-08-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Dr. Craig A. Lee" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -37667,17 +36030,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-090r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=34099" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Federated Clouds Engineering Report" + "@value": "OWS-6 GML Profile Validation Tool ER" }, { "@language": "en", - "@value": "18-090r1" + "@value": "09-038r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -37687,7 +36050,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The geospatial community has had an on-going challenge with being able to share data and compute resources in dynamic, collaborative environments that span different administrative domains. For these types of requirements, the concept of federation has been developed. The near-term goal of the Federated Cloud task in OGC Testbed-14 is to demonstrate a specific data-sharing scenario among two or more administrative domains using existing security tooling, e.g., OpenID Connect and OAuth. The main details of this work are reported as part of the OGC Testbed-14 Security Engineering Report (ER) cite:[SecurityER]. This Federated Cloud Engineering Report (ER) dovetails with the Security ER to:\r\n\r\nCoordinate across all federation-related tasks in Testbed-14, including the Earth Observation Cloud and Workflow tasks,\r\n\r\nUnderstand the overall federation design space,\r\n\r\nAnalyze and critique the scope, trade-offs and limitations of the federation capabilities being built and demonstrated in Testbed-14,\r\n\r\nIdentify and prioritize possible incremental development tasks for subsequent testbeds, and\r\n\r\nLiaison with groups external to OGC, such as the National Institute of Standards and Technology (NIST)/Institute of Electrical and Electronics Engineers (IEEE) Joint Working Group on Federated Cloud, to promote the further development and adoption of federated capabilities, and ultimately international standards.\r\n\r\n" + "@value": "This document outlines an approach for validating data accessed from a Web Feature Service. Two types of validation are supported:\r\n•\tXML Schema validation against the GML application schema\r\n•\tValidation of additional constraints encoded in Schematron\r\nThis report describes the validation tool, the types of constraints that have been tested and documents the results.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37698,35 +36061,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-090r1" + "@value": "09-038r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Federated Clouds Engineering Report" + "@value": "OWS-6 GML Profile Validation Tool ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-059", + "@id": "http://www.opengis.net/def/docs/18-042r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-04-18" + "@value": "2019-10-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Joana Simoes" + "@value": "Gobe Hobona, Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/pol-nts" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -37736,27 +36099,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-059.html" + "@id": "https://docs.ogc.org/pol/18-042r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "2023 Open Standards Code Sprint Summary Engineering Report" + "@value": "18-042r4" }, { "@language": "en", - "@value": "23-059" + "@value": "Name Type Specification - Sensor Models and Parameters" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/pol-nts" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Advances in computing, storage, sensing, and other technology areas continue to find a place in the geospatial ecosystem that makes location information findable, accessible, interoperable, and reusable. To enable geospatial standards to meet the likely interoperability needs of future technologies, it is necessary for Standards Development Organizations (SDOs) such as OGC to continue to innovate. Such innovation relies on the ability to develop new standards and improve existing ones to better address emerging interoperability challenges. Code sprints are one of a number of initiative types that OGC conducts to accelerate such innovation. A code sprint is a collaborative and inclusive event driven by innovative and rapid programming with minimal process and organization constraints to support the development of new applications and candidate standards.\r\n\r\nThe focus of this Engineering Report (ER) is a code sprint that was held from October 30th to November 1st, 2023. The code sprint was organized by the Open Geospatial Consortium (OGC) and hosted by Geovation in London, England. The code sprint was sponsored by Ordnance Survey (OS) at the Gold-level, as well as the European Union Satellite Centre (SatCen), US National Geospatial Intelligence Agency (NGA), and the UK Defence Science and Technology Laboratory (Dstl) at the Silver-level. As with previous OGC Code Sprints, a key goal of the October 2023 Open Standards Code Sprint was the acceleration of the development of OGC Standards and their implementation in software products.\r\n\r\nStandards in focus for this code sprint included several OGC API, data model, and encoding standards. In addition to OGC Standards, the code sprint also included a thread focusing on the “GEOINT Imagery Media for ISR” (GIMI) profile of the ISO Base Media File Format (ISOBMFF) and the High Efficiency Image Format (HEIF). The engineering report concludes that the code sprint met all of its objectives and achieved its goal of accelerating the development of OGC Standards and their implementation in software products.\r\n\r\nIn relation to emerging extensions to OGC API Standards, the engineering report concludes that the Publish/Subscribe (PubSub), Security, and Schemas capabilities examined in this code sprint could potentially support other OGC API Standards. Regarding GIMI, the engineering report concludes that with minor changes to popular open-source base libraries a wide range of software can quickly make use of GIMI capabilities.\r\n\r\nRegarding the Model for Underground Data Definition and Integration (MUDDI), the engineering report concludes that the MUDDI Conceptual Model is implementable and could easily be used as the basis for a logical model that can be encoded in a variety of formats including GML, GeoJSON, and Geopackage. As for JSON-FG, the engineering report concludes that due to the evident increase in adoption across the developer community, there is an increasing need to offer validators so that developers can check for compliance more easily.\r\n\r\nThe sprint participants made the following recommendations for future work items on OGC API Standards.\r\n\r\nExtension of OGC API — Records to support faceting and federated search.\r\nUse case experimentation to examine how the Publish/Subscribe approach can support various OGC API standards workflows.\r\nPrototyping and specification on an OpenAPI definition document for the OGC SensorThings API Standard.\r\nAdditional support for multiband raster data in OGC API — Maps/Tiles/Coverages (e.g., multispectral imagery, etc).\r\nThe sprint participants made the following recommendations for future work items on OGC Encoding Standards.\r\n\r\nTiled complex, signed, and floating-point data in multiband raster data.\r\nPerformance benchmarking between various imagery formats, for a variety of use cases.\r\nExtraction of the conceptual model of GMLJP2 to make it applicable to any ISOBMFF profile.\r\nDevelopment of an Implementation Standard for the logical model and encoding of data that conforms to the MUDDI.\r\nUse of the MUDDI logical schema as a template for MUDDI compliance.\r\nThe sprint participants made the following recommendations for future work items on GIMI.\r\n\r\nExtension of open-source base libraries used by several other products for creation and modification of GIMI files.\r\nPrototype streaming of large images from client applications to servers for storage through OGC API — Processes.\r\nPrototyping of a JavaScript Object Notation (JSON) encoded alternative to Key-Length-Value (KLV) metadata for use in GIMI files." + "@value": "This document specifies a rule for constructing OGC names that may be used for identifying definitions of sensor models and their parameters. This document is formally a profile of the OGC policy 'OGC-NA Name type specification - definitions: Part 1 - basic name' (OGC 09-048r5)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37767,30 +36130,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-059" + "@value": "18-042r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "2023 Open Standards Code Sprint Summary Engineering Report" + "@value": "OGC Name Type Specification - Sensor Models and Parameters" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-152r1", + "@id": "http://www.opengis.net/def/docs/11-086r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2012-01-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Luis Bermudez" + "@value": "Jan Herrmann, Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -37805,17 +36168,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=52112" + "@id": "https://portal.ogc.org/files/?artifact_id=46019" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-152r1" + "@value": "OWS-8 Aviation Thread - Authoritative AIXM Data Source Engineering Report" }, { "@language": "en", - "@value": "OWS-9 CITE Help Guide Engineering Report" + "@value": "11-086r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -37825,7 +36188,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report was created as a deliverable of the CITE Thread as part of the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. This OGC® Engineering Report describes how to execute the CITE tests, how to select the conformance classes, how to access and download the TEAM Engine, Test Scripts and Reference Implementations, how to insert your own data and/or schemas along with a section that provides other community help resources.\r\nThis is not a normative document.\r\n" + "@value": "This engineering report describes how to provide access control for WFS-T 2.0 instances\r\nin the OWS-8 Authoritative AIXM Data Source scenario." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37836,35 +36199,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-152r1" + "@value": "11-086r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-9 CITE Help Guide Engineering Report" + "@value": "OWS-8 Aviation Thread - Authoritative AIXM Data Source Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-014r3", + "@id": "http://www.opengis.net/def/docs/09-073", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-10" + "@value": "2009-08-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "James Ressler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -37874,27 +36237,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=23180" + "@id": "https://portal.ogc.org/files/?artifact_id=34145" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-014r3" + "@value": "09-073" }, { "@language": "en", - "@value": "Sensor Planning Service Implementation Specification" + "@value": "OWS-6 SWE PulseNet™ Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Sensor Planning Service Interface Standard (SPS) defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor planning request; to submit such a request; to inquire about the status of such a request; to update or cancel such a request; and to request information about other OGC Web services that provide access to the data collected by the requested task. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards." + "@value": "This document summarizes work delivered on the Sensor Web Enablement (SWE) thread of OWS-6. In particular, Northrop Grumman’s contribution from PulseNet™ to the Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) standard-compliant sensors into an OGC SWE-based architecture." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37905,35 +36268,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-014r3" + "@value": "09-073" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Sensor Planning Service Implementation Specification" + "@value": "OWS-6 SWE PulseNet™ Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-078r4", + "@id": "http://www.opengis.net/def/docs/06-027r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-14" + "@value": "2006-08-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Markus Lupp" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -37943,27 +36306,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=22364" + "@id": "https://portal.ogc.org/files/?artifact_id=14145" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Styled Layer Descriptor Profile of the Web Map Service Implementation Specification" + "@value": "06-027r1" }, { "@language": "en", - "@value": "05-078r4" + "@value": "Web Feature Service (WFS) Implementation Specification (Corrigendum)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Styled Layer Descriptor (SLD) Profile of the OpenGIS® Web Map Service (WMS) Encoding Standard [http://www.opengeospatial.org/standards/wms ] defines an encoding that extends the WMS standard to allow user-defined symbolization and coloring of geographic feature[http://www.opengeospatial.org/ogc/glossary/f ] and coverage[http://www.opengeospatial.org/ogc/glossary/c ] data. \r\n\r\nSLD addresses the need for users and software to be able to control the visual portrayal of the geospatial data. The ability to define styling rules requires a styling language that the client and server can both understand. The OpenGIS® Symbology Encoding Standard (SE) [http://www.opengeospatial.org/standards/symbol] provides this language, while the SLD profile of WMS enables application of SE to WMS layers using extensions of WMS operations. Additionally, SLD defines an operation for standardized access to legend symbols.\r\n\r\n" + "@value": "This document is a corrigendum for OGC Document 04-094. Specifically, this document corrects the files referenced in ANNEX A and found in the OGC schema repository." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -37974,35 +36337,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-078r4" + "@value": "06-027r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification" + "@value": "OpenGIS Web Feature Service (WFS) Implementation Specification (Corrigendum)" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-028", + "@id": "http://www.opengis.net/def/docs/12-084r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-08-19" + "@value": "2014-01-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Daniel Balog" + "@value": "Roger Brackin, Pedro Gonçalves " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38012,27 +36375,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=63281" + "@id": "https://portal.ogc.org/files/?artifact_id=55183" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 11 Data Broker Specifications Engineering Report" + "@value": "OWS Context Atom Encoding Standard" }, { "@language": "en", - "@value": "15-028" + "@value": "12-084r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a deliverable of the OGC Testbed 11 Interoperability initiative. The report’s contents cover the summary of the interoperability work regarding the Aviation Data Broker concept. This data broker concept enables the setup of cascading OGC Web Feature Server (WFS) servers to form a data source chain, in which one service is capable of providing information coming from one or more other services. The objectives of this document are to research the feasibility of this concept and to investigate a number of specific Data Broker responsibilities and use cases, such as provenance and lineage, conflation, caching, scalability and flexible management of data sources." + "@value": "This standard describes the Atom encoding of the OWC Context conceptual model. The goal of this standard is to provide a definition of how to encode a context document, which can be extended to allow a context referencing a fully configured service set to be defined and consistently interpreted by clients.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38043,35 +36406,238 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-028" + "@value": "12-084r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 11 Data Broker Specifications Engineering Report" + "@value": "OGC OWS Context Atom Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-111r1", + "@id": "http://www.opengis.net/def/doc-type/d-dp", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/05-025r3" + }, + { + "@id": "http://www.opengis.net/def/docs/06-080r1" + }, + { + "@id": "http://www.opengis.net/def/docs/01-013r1" + }, + { + "@id": "http://www.opengis.net/def/docs/02-061r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-019" + }, + { + "@id": "http://www.opengis.net/def/docs/12-028" + }, + { + "@id": "http://www.opengis.net/def/docs/08-128" + }, + { + "@id": "http://www.opengis.net/def/docs/03-021" + }, + { + "@id": "http://www.opengis.net/def/docs/11-039r2" + }, + { + "@id": "http://www.opengis.net/def/docs/05-035r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-013" + }, + { + "@id": "http://www.opengis.net/def/docs/06-080" + }, + { + "@id": "http://www.opengis.net/def/docs/06-131" + }, + { + "@id": "http://www.opengis.net/def/docs/05-089r1" + }, + { + "@id": "http://www.opengis.net/def/docs/02-026r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-057r2" + }, + { + "@id": "http://www.opengis.net/def/docs/19-091r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-167r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-166" + }, + { + "@id": "http://www.opengis.net/def/docs/06-057r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-007" + }, + { + "@id": "http://www.opengis.net/def/docs/07-024" + }, + { + "@id": "http://www.opengis.net/def/docs/12-066" + }, + { + "@id": "http://www.opengis.net/def/docs/04-017r1" + }, + { + "@id": "http://www.opengis.net/def/docs/04-038r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-107" + }, + { + "@id": "http://www.opengis.net/def/docs/02-027" + }, + { + "@id": "http://www.opengis.net/def/docs/12-027r2" + }, + { + "@id": "http://www.opengis.net/def/docs/05-077" + }, + { + "@id": "http://www.opengis.net/def/docs/03-064r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-028r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-057r3" + }, + { + "@id": "http://www.opengis.net/def/docs/06-093" + }, + { + "@id": "http://www.opengis.net/def/docs/11-169" + }, + { + "@id": "http://www.opengis.net/def/docs/09-142r1" + }, + { + "@id": "http://www.opengis.net/def/docs/03-008r2" + }, + { + "@id": "http://www.opengis.net/def/docs/05-112" + }, + { + "@id": "http://www.opengis.net/def/docs/05-087r3" + }, + { + "@id": "http://www.opengis.net/def/docs/02-039r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-038" + }, + { + "@id": "http://www.opengis.net/def/docs/05-109r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-035r1" + }, + { + "@id": "http://www.opengis.net/def/docs/01-044r2" + }, + { + "@id": "http://www.opengis.net/def/docs/03-002r8" + }, + { + "@id": "http://www.opengis.net/def/docs/05-088r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-018" + }, + { + "@id": "http://www.opengis.net/def/docs/08-008r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-054r1" + }, + { + "@id": "http://www.opengis.net/def/docs/03-088r1" + }, + { + "@id": "http://www.opengis.net/def/docs/04-013r4" + }, + { + "@id": "http://www.opengis.net/def/docs/04-040" + }, + { + "@id": "http://www.opengis.net/def/docs/03-013" + }, + { + "@id": "http://www.opengis.net/def/docs/04-049r1" + }, + { + "@id": "http://www.opengis.net/def/docs/02-026r4" + }, + { + "@id": "http://www.opengis.net/def/docs/14-004" + }, + { + "@id": "http://www.opengis.net/def/docs/01-022r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-055r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-126" + }, + { + "@id": "http://www.opengis.net/def/docs/03-031" + }, + { + "@id": "http://www.opengis.net/def/docs/01-024r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-129" + }, + { + "@id": "http://www.opengis.net/def/docs/05-078" + }, + { + "@id": "http://www.opengis.net/def/docs/06-028" + }, + { + "@id": "http://www.opengis.net/def/docs/05-007r2" + }, + { + "@id": "http://www.opengis.net/def/docs/01-036" + }, + { + "@id": "http://www.opengis.net/def/docs/15-074r1" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/15-046r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-12-20" + "@value": "2016-01-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Scarponcini" + "@value": "Eugene G. Yu, Liping Di, Ranjay Shrestha" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38081,27 +36647,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/15-111r1/15-111r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=64174" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Land and Infrastructure Conceptual Model Standard (LandInfra)" + "@value": "Testbed-11 High Resolution Flood Information Scenario Engineering Report" }, { "@language": "en", - "@value": "15-111r1" + "@value": "15-046r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Land and Infrastructure Conceptual Model Standard presents the implementation-independent concepts supporting land and civil engineering infrastructure facilities. Conceptual model subject areas include facilities, projects, alignment, road, rail, survey, land features, land division, and wet infrastructure (storm drainage, wastewater, and water distribution systems). The initial release of this standard includes all of these subject areas except wet infrastructure, which is anticipated to be released as a future extension. \r\nThis standard assumes the reader has a basic understanding of surveying and civil engineering concepts.\r\n" + "@value": "This OGC Engineering Report describes the high-resolution flood information scenario carried out under the Urban Climate Resilience Thread of the Testbed 11 Initiative. The scenario was developed for two areas of interest: the San Francisco Bay Area and in Mozambique. The scenarios for these two locations demonstrate the interoperation and capabilities of open geospatial standards in supporting data and processing services. The prototype High Resolution Flood Information System addresses access and control of simulation models and high-resolution data in an open, worldwide, collaborative Web environment. The scenarios were designed to help testbed participants examine the feasibility and capability of using existing OGC geospatial Web Service standards in supporting the on-demand, dynamic serving of flood information from models with forecasting capacity. Change requests to OGC standards have also been identified through the Testbed activity." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38112,35 +36678,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-111r1" + "@value": "15-046r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Land and Infrastructure Conceptual Model Standard (LandInfra)" + "@value": "OGC® Testbed-11 High Resolution Flood Information Scenario Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-006r4", + "@id": "http://www.opengis.net/def/docs/06-083r8", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-19" + "@value": "2007-02-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "John Evans" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38150,27 +36716,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/16-006r4" + "@id": "https://portal.ogc.org/files/?artifact_id=18153" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-006r4" + "@value": "06-083r8" }, { "@language": "en", - "@value": "Volume 10: OGC CDB Implementation Guidance" + "@value": "Web Coverage Service (WCS) Implementation Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. " + "@value": "The Web Coverage Service (WCS) supports electronic retrieval of geospatial data as coverages " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38181,35 +36747,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-006r4" + "@value": "06-083r8" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 10: OGC CDB Implementation Guidance" + "@value": "OpenGIS Web Coverage Service (WCS) Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-110r4", + "@id": "http://www.opengis.net/def/docs/19-070", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-02-05" + "@value": "2020-01-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Richard Martell" + "@value": "Joan Maso Pau" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38219,27 +36785,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=31137" + "@id": "https://docs.ogc.org/per/19-070.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-110r4" + "@value": "OGC Testbed-15:Images and ChangesSet API Engineering Report" }, { "@language": "en", - "@value": "CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW" + "@value": "19-070" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0.2 specification; it qualifies as a ‘Class 2’ profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards." + "@value": "The OGC API – Images and Changeset draft specification addresses the use case of an OGC API tile server that serves image tiles and a client that portrays the result as a set of images. The tile server uses a set of images (e.g. a set of remote sensing satellite scenes or a set of drone pictures) in the backend and they are also accessible by an API - Images. The source images can be updated and therefore the tile server also needs to be able to deliver only the tiles that have changed. The draft specification is divided into two independent parts that can be used in broader scenarios:\r\n\r\nThe OGC API – Images: Enables managing (retrieving, creating and updating) sets of images that are georeferenced. The images does not follow any tile scheme, and can partiallyor totally overlap. The API enables a mosaicking use case (where the imagery is combined in a single bigger “picture”) but could also serve a use case in which a moving camera is taking pictures at locations along a route and then stores the images as a single collection.\r\n\r\nThe Changeset filter: Enables filtering a request to a data service in a way that only recent changes are delivered. It can be applied to OGC API that provide access to data and in particular to the OGC API tiles." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38250,35 +36816,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-110r4" + "@value": "19-070" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW" + "@value": "OGC Testbed-15:Images and ChangesSet API Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-016r1", + "@id": "http://www.opengis.net/def/docs/05-007r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-19" + "@value": "2005-06-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Peter Schut" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38288,27 +36854,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/18-016r1" + "@id": "https://portal.ogc.org/files/?artifact_id=10634" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": " CDB Version 1.1 Release Notes" + "@value": "Web Processing Service" }, { "@language": "en", - "@value": "18-016r1" + "@value": "05-007r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides release notes for version 1.1 of the CDB Standard and related Best Practices." + "@value": "A Web Service Processing Service provides access to calculations or models which operate on spatially referenced data. The data required by the service can be available locally, or delivered across a network using data exchange standards such as Geography Markup Language (GML) or Geolinked Data Access Service (GDAS). The calculation can be as simple as subtracting one set of spatially referenced numbers from another (e.g. determining the difference in influenza cases between two different seasons), or as complicated as a global climate change model. \r\n \r\nThis specification is intended to provide a mechanism to identify the spatially-referenced data required by the calculation, initiate the calculation, and manage the output from the calculation so that it can be accessed by the client. The Web Processing Service is targeted at both vector and raster data based processing. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38319,35 +36885,46 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-016r1" + "@value": "05-007r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC CDB Version 1.1 Release Notes" + "@value": "Web Processing Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-010r2", + "@id": "http://www.opengis.net/def/doc-type/primer", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/12-077r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-091r3" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/08-079", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-12-12" + "@value": "2008-09-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "John Herring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38357,27 +36934,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-010r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=28176" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-010r2" + "@value": "08-079" }, { "@language": "en", - "@value": "OGC Testbed-15: Styles API Engineering Report" + "@value": "OWS5: OGC Web feature service, core and extensions" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a proof of concept of a draft specification of the OGC Styles Application Programming Interface (API) that defines a Web API that enables map servers and clients as well as visual style editors to manage and fetch styles.\r\n\r\nWeb APIs are software interfaces that use an architectural style that is founded on the technologies of the Web. Styles consist of symbolizing instructions that are applied by a rendering engine on features and/or coverages.\r\n\r\nThe Styles API supports several types of consumers, mainly:\r\n\r\nVisual style editors that create, update and delete styles for datasets that are shared by other Web APIs implementing the OGC API - Features - Part 1: Core standard or the draft OGC API - Coverages or draft OGC API - Tiles specifications;\r\n\r\nWeb APIs implementing the draft OGC API - Maps specification fetch styles and render spatial data (features or coverages) on the server;\r\n\r\nMap clients that fetch styles and render spatial data (features or coverages) on the client.\r\n\r\nFeature data is either accessed directly or organized into spatial partitions such as a tiled data store (aka vector tiles).\r\n\r\nThe Styles API is consistent with the emerging OGC API family of standards.\r\n\r\nThe Styles API implements the conceptual model for style encodings and style metadata as documented in chapter 6 of the OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report.\r\n\r\nThe model defines three main concepts:\r\n\r\nThe style is the main resource.\r\n\r\nEach style is available in one or more stylesheets - the representation of a style in an encoding like OGC SLD 1.0 or Mapbox Style. Clients will use the stylesheet of a style that fits best based on the capabilities of available tools and their preferences.\r\n\r\nFor each style there is style metadata available, with general descriptive information about the style, structural information (e.g., layers and attributes), and so forth to allow users to discover and select existing styles for their data." + "@value": "This standard specifies the behavior of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations and transaction operations. Discovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers. Retrieval operations allow features to be retrieved from the opaque underlying data store based upon constraints on spatial and non-spatial feature properties defined by the client. Transaction operations allow features to be created, changed and deleted from the opaque underlying data store." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38388,30 +36965,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-010r2" + "@value": "08-079" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Styles API Engineering Report" + "@value": "OWS5: OGC Web feature service, core and extensions" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-108r3", + "@id": "http://www.opengis.net/def/docs/11-052r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-03-22" + "@value": "2012-06-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Trevelyan, Paul Hershberg, Steve Olson" + "@value": "Matthew Perry, John Herring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -38426,17 +37003,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/15-108r3/15-108r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=47664" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "MetOcean Application profile for WCS2.1: Part 1 MetOcean GetCorridor Extension" + "@value": "GeoSPARQL - A Geographic Query Language for RDF Data" }, { "@language": "en", - "@value": "15-108r3" + "@value": "11-052r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -38446,7 +37023,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The purpose of the GetCorridor operation is to extract a corridor based on a trajectory from a multidimensional coverage. The need for the getCorridor operation stems from active members of the OGC MetOcean Domain Working Group (DWG) who saw a manifest need for extraction of such information from gridded datasets. This work has been done by members of the OGC MetOcean Domain Working Group." + "@value": "This standard defines a set of SPARQL extension functions [W3C SPARQL], a set of RIF rules [W3C RIF Core], and a core RDF/OWL vocabulary for geographic information based on the General Feature Model, Simple Features [ISO 19125-1], Feature Geometry and SQL MM." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38457,35 +37034,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-108r3" + "@value": "11-052r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC MetOcean Application profile for WCS2.1: Part 1 MetOcean GetCorridor Extension" + "@value": "OGC GeoSPARQL - A Geographic Query Language for RDF Data" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-007r2", + "@id": "http://www.opengis.net/def/docs/17-028", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-08-04" + "@value": "2018-01-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Burggraf" + "@value": "Benjamin Pross, Christoph Stasch" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38495,27 +37072,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/12-007r2/12-007r2.html" + "@id": "https://docs.ogc.org/per/17-028.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "KML 2.3" + "@value": "Testbed-13:Asynchronous Services ER" }, { "@language": "en", - "@value": "12-007r2" + "@value": "17-028" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "KML is an XML grammar used to encode and transport representations of geographic data for display in an earth browser. Put simply: KML encodes what to show in an earth browser, and how to show it. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard.\r\n\r\nThe KML community is wide and varied. Casual users create KML Placemarks to identify their homes, describe journeys, and plan cross-country hikes and cycling ventures. Scientists use KML to provide detailed mappings of resources, models, and trends such as volcanic eruptions, weather patterns, earthquake activity, and mineral deposits. Real estate professionals, architects, and city development agencies use KML to propose construction and visualize plans. Students and teachers use KML to explore people, places, and events, both historic and current. Organizations such as National Geographic, UNESCO, and the Smithsonian have all used KML to display their rich sets of global data.\r\n\r\nKML documents and their related images (if any) may be compressed using the ZIP format into KMZ archives. KML documents and KMZ archives may be shared by e‑mail, hosted locally for sharing within a private internet, or hosted on a web server." + "@value": "The goal of this ER is to summarize and compare the results from the activities dealing with asynchronous WFS responses in Testbed 13. Special focus will be given to the specific requirement for automatic notification of users if new or updated information becomes available and to the software components addressing these requirements, i.e. two asynchronous Web Feature Services (NG119 and NG120)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38526,30 +37103,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-007r2" + "@value": "17-028" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC KML 2.3" + "@value": "OGC Testbed-13: Asynchronous Services ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-023r2", + "@id": "http://www.opengis.net/def/docs/19-041r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-07-14" + "@value": "2020-01-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sergio Taleisnik" + "@value": "Sam Meek, Theo Brown, Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -38564,17 +37141,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-023r2.html" + "@id": "https://docs.ogc.org/per/19-041r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-023r2" + "@value": "Routing Pilot ER" }, { "@language": "en", - "@value": "Testbed-18: Features Filtering Summary Engineering Report" + "@value": "19-041r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -38584,7 +37161,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed-18 (TB-18) Features Filtering Summary Engineering Report (ER) summarizes the implementations, findings, and recommendations that emerged from the efforts to better understand the current OGC API-Features filtering capabilities and limitations and how filtering can be decoupled from data services.\r\n\r\nThis ER describes:\r\n\r\n*\ttwo façades built to interface SWIM services and serve aviation data through APIs (built with OGC API Standards) including basic filtering capabilities;\r\n*\tthe two filtering services built to consume SWIM data and serve it through OGC based APIs featuring advanced filtering mechanism;\r\n*\tthe client application built to interface with the filtering services; and\r\n*\tthe developer client built to define filter statements that can be expressed in a machine-readable way and exchanged with the filtering service." + "@value": "The goal of this OGC Routing Pilot Engineering Report (ER) is to document the proof of concept of an Application Programming Interface (API) conforming to a profile of the draft OGC API - Processes specification that allows implementation of vector routing across one or more routing engines. The components implemented in the OGC Open Routing API Pilot 2019 included two clients, interfacing with three implementations of the draft OGC API - Processes specification that in turn communicated with three routing engines. This work resulted in the definition of a proposed common interface and data exchange model supported by all components for requesting, generating and returning routes." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38595,35 +37172,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-023r2" + "@value": "19-041r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-18: Features Filtering Summary Engineering Report" + "@value": "OGC® Routing Pilot ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-104r3", + "@id": "http://www.opengis.net/def/docs/21-066r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-01-29" + "@value": "2022-09-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Herring" + "@value": "Joan Maso" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38633,27 +37210,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=18242" + "@id": "https://docs.ogc.org/is/17-083r4/21-066r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option" + "@value": "21-066r1" }, { "@language": "en", - "@value": "06-104r3" + "@value": "Release Notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata v.2.0" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. \r\n\r\nPart 1 “Common Architecture supplies the common feature model for use by applications that will use the Simple Features data stores and access interfaces. \r\n\r\nPart 2 provides a standard SQL implementation of the abstract model in Part 1. (Note: The OpenGIS® Simple Features Interface Standards for OLE/COM and CORBA are no longer current and are not provided here.) \r\n\r\nThe corresponding standard for the Web is the OpenGIS® Web Feature Service Interface Standard http://www.opengeospatial.org/standards/wfs.\r\n" + "@value": "This document provides the set of revision notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata [OGC 17-083r4] and does not modify that Standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38664,35 +37241,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-104r3" + "@value": "21-066r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option" + "@value": "Release Notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata v.2.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-058", + "@id": "http://www.opengis.net/def/docs/11-169r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-11-18" + "@value": "2014-02-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stephane Fellah" + "@value": "Simon Jirka, Christoph Stasch, Arne Bröring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38702,27 +37279,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64385" + "@id": "https://portal.ogc.org/files/?artifact_id=52803" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-11 Symbology Mediation" + "@value": "Best Practice for Sensor Web Enablement Lightweight SOS Profile for Stationary In-Situ Sensors" }, { "@language": "en", - "@value": "15-058" + "@value": "11-169r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Engineering Report (ER) summarizes the approaches, findings and the results of the Symbology Mediation sub-thread activities of the OGC Testbed-11 Cross Community Interoperability (CCI) Thread. The ER:\r\n•\t Provides an overview of existing standards relevant to symbology mediation, \r\n•\tOutlines the approaches adopted during the testbed, \r\n•\tDescribes the conceptual models and services developed during the testbed to address semantic mediation and portrayal of feature information related to Emergency Management and to some extent to the Aviation domain. \r\n" + "@value": "This Best Practice document describes a lightweight SOS 2.0 profile for stationary in-situ\r\nsensors. Besides the SOS itself this document also addresses the data formats used by the\r\nSOS: Observations & Measurements 2.0 (O&M) for encoding measurement data and the\r\nSensor Model Language 2.0 (SensorML) for encoding metadata. Other SWE standards\r\nwhich provide more specialized functionality are not part of this minimum lightweight\r\nSWE profile.\r\nThe aim of this document is to present a common minimum profile of the SOS. The\r\nprofile is intended to reduce the complexity of the standard by omitting highly specific\r\nelements that are not necessary for the majority of use cases that occur in practice. At the\r\nsame time, the profile is designed in such a way that all SOS implementations that\r\nconform to this profile are also compliant to the according OGC specifications." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38733,35 +37310,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-058" + "@value": "11-169r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed-11 Symbology Mediation" + "@value": "OGC® Best Practice for Sensor Web Enablement Lightweight SOS Profile for Stationary In-Situ Sensors" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-050r1", + "@id": "http://www.opengis.net/def/docs/06-021r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-08" + "@value": "2008-07-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paulo Sacramento" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38771,27 +37348,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-050r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=27775" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-050r1" + "@value": "OGC® Sensor Web Enablement Architecture" }, { "@language": "en", - "@value": "ADES & EMS Results and Best Practices Engineering Report" + "@value": "06-021r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) describes best practices and results gathered through the work performed in the Exploitation Platforms Earth Observation Clouds (EOC) Thread of OGC Testbed-14 concerning the Application Deployment and Execution Service (ADES) and the Execution Management Service (EMS). Both the ADES and EMS were identified by the European Space Agency (ESA), beforehand, as essential elements of a Thematic Exploitation Platform (TEP).\r\n\r\nIn the context of a generic Earth Observation Exploitation Platform ecosystem, populated by TEPs and Mission Exploitation Platforms (MEPs), which make use of cloud computing resources for Earth Observation data processing, ESA has established two fundamental building blocks within a TEP, with different functions, the ADES and the EMS. Users interact with a TEP using a Web Client, and the TEP contains a EMS and a ADES. The EMS includes most of the control logic, required for deploying and executing applications in different MEPs and TEPs, the chaining thereof, and the overall coherence of the execution chain (e.g. gathering all outputs and enabling their presentation to the user by a client sensibly). The ADES instead is responsible for the single application deployment and execution on a specific platform. Therefore, it is expected that there are ADES instances both in a TEP and in the individual MEPs.\r\n\r\nThe Testbed-14 Participants have experimented with different options for what concerns the functionality allocated to each of the two components, the information required by each of them and the interface requirements between them in order to produce a consistent chain, compliant with ESA’s objectives (as the Sponsor). This report describes these experiments, providing their results and suggesting best practices on how the two services should be engineered in the Exploitation Platform context.\r\n\r\nThe OGC Web Processing Service (WPS) 2.0 standard is of particular relevance given that it is well-established in the OGC Web Service context, specifically that concerning processing, its interoperability value has been clearly demonstrated, and it therefore provides a useful mechanism for standardizing interfaces between components of heterogeneous provenance and implementation." + "@value": "This document describes the architecture implemented by Open Geospatial Consortium’s (OGC) Sensor Web Enablement Initiative (SWE). In contrast to other OGC SWE stan-dards, this document is not an implementation standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38802,35 +37379,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-050r1" + "@value": "06-021r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: ADES & EMS Results and Best Practices Engineering Report" + "@value": "Sensor Web Enablement Architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-163", + "@id": "http://www.opengis.net/def/docs/16-036r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-01-17" + "@value": "2017-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lorenzo Bigagli, StefanoNativi" + "@value": "Christian Autermann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38840,27 +37417,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46702" + "@id": "https://docs.ogc.org/per/16-036r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-163" + "@value": "16-036r1" }, { "@language": "en", - "@value": "NetCDF Uncertainty Conventions " + "@value": "Testbed-12 Big Data Database Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion Paperproposes a set of conventions for managing uncertainty information within the netCDF3 data model and format: the NetCDF Uncertainty Conventions (NetCDF-U)." + "@value": "The amount of (geospatial) data collected and transferred is rapidly increasing. The purpose of this ER is to describe options and recommendations for the delivery of large amounts of data as database delivery. This ER therefore describes and evaluates different aspects of this challenge:\r\n\r\nData management: How to organize large amounts of data so that it can be efficiently accessed through OGC service interfaces?\r\n\r\nEncoding: Transferring large amounts of vector data in XML based formats (e.g. GML, O&M) leads to specific challenges as the parsing of large XML files is often problematic.\r\n\r\nAvailable implementation: Several software packages exist to handle large amounts of geospatial data. We will investigate to which these approaches are in-line with OGC standards or how standards compliance could be achieved.\r\n\r\nThe evaluation and findings in the related Big Data Tile Database Implementation are documented in this ER as well. The objective of this ER is to provide recommendations of how the delivery of large amounts of raster data as database delivery can be considered within OGC specifications and future activities." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38871,35 +37448,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-163" + "@value": "16-036r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "NetCDF Uncertainty Conventions " + "@value": "Testbed-12 Big Data Database Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-088r1", + "@id": "http://www.opengis.net/def/docs/13-032", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-10-16" + "@value": "2013-09-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38909,27 +37486,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=11519" + "@id": "https://portal.ogc.org/files/?artifact_id=53823" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-088r1" + "@value": "13-032" }, { "@language": "en", - "@value": "OGC Web Services Common" + "@value": "SWE Implementation Maturity Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses." + "@value": "This report summarizes the outcomes of a process to assess the maturity of implementations based on SWE standards. This report covers the following areas:\r\n•\tSWE standards overview\r\n•\tImplementations of SWE in major systems\r\n•\tSWE software implementations and compliance\r\n•\tSWE implementations in IP\r\n•\tRecommendations and Observations\r\nA main outcome is the summary assessment of the SWE Implementation Maturity as presented in the Preface based on the body of the report.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -38940,35 +37517,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-088r1" + "@value": "13-032" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Services Common" + "@value": "OGC® SWE Implementation Maturity Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-021", + "@id": "http://www.opengis.net/def/docs/10-129r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-01-24" + "@value": "2012-02-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Alan Leidner, Mark Reichardt, Josh Lieberman" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -38978,27 +37555,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-021.html" + "@id": "https://portal.ogc.org/files/?artifact_id=46568" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-021" + "@value": "Geography Markup Language (GML) - Extended schemas and encoding rules" }, { "@language": "en", - "@value": "Health Spatial Data Infrastructure Concept Development Study Engineering Report" + "@value": "10-129r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Experts agree that access to, sharing, and application of location-enabled information is a key component in addressing health related emergencies. While the present COVID-19 pandemic has underscored a range of successes in dealing with the COVID virus, many gaps in supporting local to global preparedness, forecasting, monitoring, and response have been identified when dealing with a health crisis at such an unprecedented level. This study considers how a common, standardized health geospatial data model, schema, and corresponding spatial data infrastructure (SDI) could establish a blueprint to better align the community for early warning, response to, and recovery from future health emergencies. Such a data model would help to improve support for critical functions and use cases." + "@value": "The Geography Markup Language (GML) is an XML encoding in compliance with ISO 19118 for the transport and storage of geographic information modelled in accordance with the conceptual modelling framework used in the ISO 19100 series of International Standards and including both the spatial and non-spatial properties of geographic features." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39009,30 +37586,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-021" + "@value": "10-129r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Health Spatial Data Infrastructure Concept Development Study Engineering Report" + "@value": "OGC® Geography Markup Language (GML) - Extended schemas and encoding rules" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-114r3", + "@id": "http://www.opengis.net/def/docs/16-070r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-18" + "@value": "2017-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Martin Desruisseaux" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -39047,17 +37624,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/16-114r3/16-114r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=72715" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-114r3" + "@value": "Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage" }, { "@language": "en", - "@value": "Moving Features Encoding Extension: netCDF" + "@value": "16-070r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -39067,7 +37644,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The netCDF Moving Features encoding extension is a summary of conventions that supports efficient exchange of simple moving features as binary files. This Best Practice is a complement to the Moving Features Encoding Part I: XML Core and an alternative to the Simple Comma Separated Values (CSV) extension. Compared to the CSV encoding, this netCDF encoding offers more compact storage and better performance at the cost of additional restrictions on the kinds of features that can be stored." + "@value": "This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39078,30 +37655,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-114r3" + "@value": "16-070r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Moving Features Encoding Extension: netCDF" + "@value": "Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-061r1", + "@id": "http://www.opengis.net/def/docs/16-115", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-02-09" + "@value": "2017-10-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Burggraf" + "@value": "Guy Schumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -39116,17 +37693,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=45380" + "@id": "https://docs.ogc.org/per/16-115.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-8 AIXM Metadata Guidelines Engineering Report" + "@value": "Future City Pilot 1 - Recommendations on Serving IFC via WFS" }, { "@language": "en", - "@value": "11-061r1" + "@value": "16-115" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -39136,7 +37713,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Engineering Report provides guidelines for ISO metadata usage in AIXM 5.1\r\nconformant to the requirements of OGC 10-195 (Requirements for Aviation Metadata)\r\nand the recommendations of OGC 10-196r1 (Guidance on the Aviation Metadata\r\nProfile), with the exception of non-ISO metadata elements listed in these documents." + "@value": "This Engineering Report (ER) gives recommendations on serving IFC via WFS and discusses related issues. It was decided that the focus of this ER is to summarize issues and give recommendations for future work and discuss the nature of such work. In other words, this ER should be viewed as an initial set of discussion points on the topic of serving IFC via WFS." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39147,35 +37724,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-061r1" + "@value": "16-115" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 AIXM Metadata Guidelines Engineering Report" + "@value": "Future City Pilot 1 - Recommendations on Serving IFC via WFS" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-085r8", + "@id": "http://www.opengis.net/def/docs/19-076", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-08-27" + "@value": "2020-03-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lucio Colaiacomo, Joan Masó, Emmanuel Devys, Eric Hirschorn" + "@value": "Ajay Gupta, Luis Bermudez, Eddie Oldfield, Scott Serich" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -39185,27 +37762,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/08-085r8/08-085r8.html" + "@id": "https://docs.ogc.org/wp/19-076.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GML in JPEG 2000 (GMLJP2) Encoding Standard" + "@value": "19-076" }, { "@language": "en", - "@value": "08-085r8" + "@value": "Health Spatial Data Infrastructure: Application Areas, Recommendations, and Architecture" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC GML in JPEG 2000 (GMLJP2) Encoding Standard defines how the OGC/ISO Geography Markup Language (GML) standard is used within JPEG 2000 images and other gridded coverage data for adding geospatial content to imagery. Specifically, this OGC standard defines requirements for the encoding and decoding of JPEG 2000 images and other gridded coverage data that contain XML documents that use GML and GML-based schema.\r\nThis document defines the use of GML within the XML boxes of the JP2 and JPX file format for JPEG 2000 (extending the JP2 file format, as specified in [ISO 15444-1] and [ISO 15444-2] in Annexes M and N). Further, an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations is specified. The document also specifies the encoding and packaging rules for GML use in JPEG 2000.\r\n" + "@value": "This Health Spatial Data Infrastructure white paper provides a discussion about the collection, exchange, integration, analysis, and visualization of health and non-health data to support health applications. Applications that address health issues at global and population level scale as well as at the local, individual patient scale are presented. The paper identifies opportunities to advance OGC Standards towards building a framework to support Health Spatial Data Infrastructures (SDIs)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39216,99 +37793,157 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-085r8" + "@value": "19-076" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard" + "@value": "Health Spatial Data Infrastructure: Application Areas, Recommendations, and Architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-004", + "@id": "http://www.opengis.net/def/docs/", "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" + "http://www.w3.org/2004/02/skos/core#Collection" ], - "http://purl.org/dc/terms/created": [ + "http://purl.org/dc/terms/provenance": [ { - "@type": "xsd:date", - "@value": "2014-04-15" + "@value": "Generated by the OGC Definitions Server to support integration of the elements of this ConceptScheme into bigger collections. ogc_skos_profile_entailements.ttl" } ], - "http://purl.org/dc/terms/creator": [ + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "GEOWOW Consortium" + "@value": "Collection hierarchy for this ConceptScheme" } ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/docs" } ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "http://www.w3.org/2004/02/skos/core#member": [ { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/doc-type/d-rp/collection" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=57327" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/doc-type/pc/collection" + }, { - "@language": "en", - "@value": "Sensor Observation Service 2.0 Hydrology Profile" + "@id": "http://www.opengis.net/def/doc-type/d-is/collection" }, { - "@language": "en", - "@value": "14-004" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/doc-type/bp/collection" + }, { - "@id": "http://www.opengis.net/def/doc-type/d-dp" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/doc-type/ug/collection" + }, { - "@value": "This document an interoperable hydrology profile for OGC Sensor Observation Service (SOS) 2.0 implementations serving OGC WaterML 2.0. This development is based on previous activities and results (i.e. Hydrology Interoperability Experiments as well as the European FP7 project GEOWOW). It is guided by the need to overcome mostly semantic issues between different SOS instances serving hydrological data and the according clients. Therefore, this profile focuses on how to use the entities and requests of the standards and covers the necessary technical details. " - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/doc-type/d-sap/collection" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/doc-type/dp-draft/collection" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-004" + "@id": "http://www.opengis.net/def/doc-type/rfc/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-as/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/as/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/sap/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/isc/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/cs/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/per/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/notes/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/pol-nts/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/profile/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-dp/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/dp/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/isx/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/ipr/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-isc/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-atb/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/is-draft/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-bp/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/retired/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-profile/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/is/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/orm/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-rfc/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/ts/collection" + }, + { + "@id": "http://www.opengis.net/def/doc-type/pol/collection" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@language": "en", - "@value": "OGC Sensor Observation Service 2.0 Hydrology Profile" + "@value": "Concepts in OGC Documents" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-011r2", + "@id": "http://www.opengis.net/def/docs/19-025r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-01-28" + "@value": "2019-08-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Robert Thomas, Terry Idol" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -39323,17 +37958,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=66906" + "@id": "https://portal.ogc.org/files/?artifact_id=88037" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-11 Multiple WFS-T Interoperability" + "@value": "19-025r1" }, { "@language": "en", - "@value": "15-011r2" + "@value": "Development of Spatial Data Infrastructures for Marine Data Management" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -39343,7 +37978,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the work done in the OGC Testbest-11 to support multiple WFS-T instance interoperability by way of a transaction scenario involving the interaction between clients and multiple WFS-T servers as well as the interaction between the servers themselves, especially in the use case of enterprise-to-enterprise data synchronization.\r\nThe document presents an overview of the transaction scenario, the components used to implement the scenario in the OGC Testbed-11 demo and the new capabilities added to the WFS-T server to support the scenario.\r\n" + "@value": "This engineering report presents the results of a concept development study on a\r\nMarine Spatial Data Infrastructure (SDI), sponsored by the National Geospatial-\r\nIntelligence Agency (NGA) - Maritime Safety Office (MSO), on behalf of the\r\nInternational Hydrographic Organization (IHO) and the IHO MSDI Working Group\r\n(MSDIWG), and executed by the Open Geospatial Consortium (OGC). The goal of\r\nthis study was to demonstrate to stakeholders the diversity, richness and value of a\r\nMarine SDI – specifically data, analysis, interoperability and associated IT services\r\n- including web services - in addressing needs of the marine domain." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39354,35 +37989,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-011r2" + "@value": "19-025r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-11 Multiple WFS-T Interoperability" + "@value": "Development of Spatial Data Infrastructures for Marine Data Management" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-048", + "@id": "http://www.opengis.net/def/docs/11-018", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-16" + "@value": "2011-03-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Genong (Eugene) Yu, Liping Di" + "@value": "Rüdiger Gartmann, Bastian Schäffer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -39392,27 +38027,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=58944" + "@id": "https://portal.ogc.org/files/?artifact_id=42735" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 10 Cross Community Interoperability (CCI) Hydro Model Interoperability Engineering Report" + "@value": "11-018" }, { "@language": "en", - "@value": "14-048" + "@value": "License-Based Access Control" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document gives guidelines for enabling interoperability among different hydro data models and services. The demonstration specifically gives out best practices for supporting interoperability among the National Hydrographic Network (NHN) of Canada, the National Hydrographic Dataset Plus (NHD+) of United States, and the OGC HY_Features model developed and proposed by the World Meteorological Organization (WMO). The discussed version of OGC HY_Features was adopted as the mediation bridge model to exchange information among heterogeneous hydrological models." + "@value": "This Discussion Paper proposes model for license-based access control to SOAP services, based on OASIS SAML 2.0. This approach is a potential solution for license-based access control, which requires the possession of a valid license for getting access to a service. Use of digital licenses allow users to act on or with web services to which they are associated\r\n\r\nThis document re-uses content produced by the OGC GeoRM Common 1.0 Standards Working Group and combined that with the document OGC 10-125, which was posted to an internal OGC document archive (Pending Documents) but is not publicly available.\r\nThis document does not claim compliance to the GeoDRM reference model (ISO 19153), although the authors are not yet aware of any conflicts to it.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39423,35 +38058,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-048" + "@value": "11-018" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 10 Cross Community Interoperability (CCI) Hydro Model Interoperability Engineering Report" + "@value": "License-Based Access Control" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-009r3", + "@id": "http://www.opengis.net/def/docs/21-055", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-13" + "@value": "2021-11-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Shayne Urbanowski" + "@value": "Gobe Hobona, Joana Simoes" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -39461,27 +38096,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=22873" + "@id": "https://docs.ogc.org/per/21-055.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-009r3" + "@value": "21-055" }, { "@language": "en", - "@value": "OGC Web Services Architectural Profile for the NSG" + "@value": "July 2021 OGC API Code Sprint Summary Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The purpose of this document is to generally describe how the various OGC specifications may be used to address the needs of a large enterprise system. It highlights the key elements of the OWS-4 effort as they relate to web service architecture implementation at NGA and in the NSG. The goal is that this document will enable organization that interface with the NSG to understand how to produce and consume data and services in an interoperable environment. " + "@value": "The subject of this Engineering Report (ER) is a virtual code sprint that was held from July 21st to July 23rd, 2021 to advance the development of the OGC API - Processes draft standard, OGC API - Records draft standard, and the OGC API – Coverages draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39492,35 +38127,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-009r3" + "@value": "21-055" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Services Architectural Profile for the NSG" + "@value": "July 2021 OGC API Code Sprint Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-176r7", + "@id": "http://www.opengis.net/def/docs/17-021", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-06-10" + "@value": "2018-01-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Doug Nebert, Uwe Voges, Panagiotis Vretanos, Lorenzo Bigagli, Bruce Westcott" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -39530,27 +38165,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/12-176r7/12-176r7.html" + "@id": "https://docs.ogc.org/per/17-021.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Catalogue Services 3.0 Specification - HTTP Protocol Binding" + "@value": "17-021" }, { "@language": "en", - "@value": "12-176r7" + "@value": "Testbed-13: Security Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the HTTP profile of the CSW General Model part (see OGC 12-\r\n168r6). The General Model specifies the abstract interfaces between clients and catalogue\r\nservices. This standard specifies the mappingof the Catalogue abstract model interface\r\ninto the HTTP protocol binding.\r\nIn this HTTP protocol binding, operation requests and responses are sent between clients\r\nand servers using the HTTP GET and/or HTTP POST methods. Two equivalent request\r\nencodings are defined in this standard. The first using keyword-value pairs (KVP)\r\nwhich is suitable for use with the HTTP GET method. The second using XML which is\r\nsuitable for use with the HTTP POST method.\r\nThis standard defines operations that allow a client to get a service description document\r\nfor the catalogue (i.e. GetCapabilities); operations that allow a client to, at runtime,\r\ninterrogate the service about the kinds of data available (i.e. GetDomain); operations that\r\nallow a client to retrieve records from the catalogue (i.e. GetRecordById and\r\nGetRecords); operations that allow a client to add, modify and remove records from the\r\ncatalogue service (i.e. Transaction, Harvest, UnHarvest)." + "@value": "The Security Engineering Report (ER) covers two Testbed 13 topics:\r\n\r\nThe implementation of authentication and authorization plugins for the QGIS open source desktop GIS client and\r\n\r\nthe implementation of secured workflow.\r\n\r\nThe authentication plugins implement the SAML2 ECP with PAOS binding and IdP discovery from the SAML2 federation metadata URL. The access right delegation plugin implements applicable OAuth2 grant types.\r\n\r\nRegarding the first topic, this ER discusses the fit for purpose aspects for the OAuth2 and SAML2 in the context of an open source desktop application. It also covers the QGIS development as well as building and deployment aspects. Most of the work related to this topic was provided by Secure Dimensions.\r\n\r\nRegarding the second topic, this ER outlines the architecture approach and the implications to implementations for security in OGC service workflows as well as the implementation approach itself. Most of the work related to this topic was provided by 52°North." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39561,30 +38196,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-176r7" + "@value": "17-021" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding" + "@value": "OGC Testbed-13: Security Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-016", + "@id": "http://www.opengis.net/def/docs/21-022", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-13" + "@value": "2022-01-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Alex Robin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -39599,17 +38234,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-016.html" + "@id": "https://docs.ogc.org/per/21-022.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": " Data Access and Processing Engineering Report" + "@value": "21-022" }, { "@language": "en", - "@value": "20-016" + "@value": "OGC Testbed-17: Sensor Integration Framework Assessment ER" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -39619,7 +38254,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed-16 Engineering Report (ER) describes the work performed in the Data Access and Processing API (DAPA) thread.\r\n\r\nThe primary goal of the DAPA thread is to develop methods and apparatus that simplify access to, processing of, and exchange of environmental and Earth Observation (EO) data from an end-user perspective. This ER presents:\r\n\r\nThe use cases participants proposed to guide the development of the client and server components deployed during the testbed.\r\n\r\nAn abstract description of a resource model that binds a specific function to specific data and also provides a means of expressing valid combinations of data and processes.\r\n\r\nA description of each DAPA endpoint developed and deployed during the testbed.\r\n\r\nA description of the client components that interact with the deployed DAPA endpoints.\r\n\r\nEnd-user (i.e. data scientist) feedback concerning the ease-of-use of the" + "@value": "This OGC Testbed 17 Engineering Report (ER) documents the outcomes of a review and implementation of the Sensor Integration Framework Standards Profile (SIF-SP) v1.0.1, published by the National Center for Geospatial Intelligence Standards (NCGIS).\r\n\r\nThe Sensor Integration Framework Standard Profiles (SIF-SP) authors rightly acknowledge that sensing systems and the environments they operate in (e.g. hardware platform, computing resources, connectivity, ease of deployment, etc.) are very heterogeneous and that there will never be a single suite of technology or standards that can support the goal of providing unified access to sensor deployments employed in complex applications.\r\n\r\nInstead, rather than trying to impose a single standard or suite of standards, the SIF-SP approach defines common conceptual models that can be mapped to existing and future standards, thus allowing integration of all these standards in a single framework.\r\n\r\nThis approach is fully compatible with the OGC Sensor Web Enablement (SWE) suite of standards that were designed for this type of integration. Thus, existing and upcoming SWE standards defined in the OGC can be used as the central pillar of a SIF implementation. The test implementation developed in this testbed, and based on OpenSensorHub, focused on demonstrating this aspect.\r\n\r\nIn addition to a thorough review of the SIF material — including standards documents, UML models and ontologies — a prototype implementation of the SIF standards was created during the Testbed using OpenSensorHub. This allowed the testbed participants to check the practical feasibility of fulfilling the SIF requirements using the OGC SWE suite of standards. Details and feedback regarding this implementation are also provided in this ER.\r\n\r\nSuggestions to improve SIF-SP and make it an integral part of the OGC standard baseline are also provided.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39630,35 +38265,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-016" + "@value": "21-022" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: Data Access and Processing Engineering Report" + "@value": "OGC Testbed-17: Sensor Integration Framework Assessment ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-070", + "@id": "http://www.opengis.net/def/docs/05-076", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-01-08" + "@value": "2006-03-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Maso Pau" + "@value": "John Evans" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -39668,27 +38303,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-070.html" + "@id": "https://portal.ogc.org/files/?artifact_id=12582" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-070" + "@value": "Web Coverage Service (WCS) Implementation Specification (Corrigendum)" }, { "@language": "en", - "@value": "OGC Testbed-15:Images and ChangesSet API Engineering Report" + "@value": "05-076" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC API – Images and Changeset draft specification addresses the use case of an OGC API tile server that serves image tiles and a client that portrays the result as a set of images. The tile server uses a set of images (e.g. a set of remote sensing satellite scenes or a set of drone pictures) in the backend and they are also accessible by an API - Images. The source images can be updated and therefore the tile server also needs to be able to deliver only the tiles that have changed. The draft specification is divided into two independent parts that can be used in broader scenarios:\r\n\r\nThe OGC API – Images: Enables managing (retrieving, creating and updating) sets of images that are georeferenced. The images does not follow any tile scheme, and can partiallyor totally overlap. The API enables a mosaicking use case (where the imagery is combined in a single bigger “picture”) but could also serve a use case in which a moving camera is taking pictures at locations along a route and then stores the images as a single collection.\r\n\r\nThe Changeset filter: Enables filtering a request to a data service in a way that only recent changes are delivered. It can be applied to OGC API that provide access to data and in particular to the OGC API tiles." + "@value": "Extends the Web Map Server (WMS) interface to allow access to geospatial coverages that represent values or properties of geographic locations, rather than WMS generated maps (pictures).\r\n\r\nThe original document is available at: http://portal.opengeospatial.org/files/?artifact_id=3837" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39699,46 +38334,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-070" + "@value": "05-076" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15:Images and ChangesSet API Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-sap", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/02-058" - }, - { - "@id": "http://www.opengis.net/def/docs/09-146r1" + "@value": "OpenGIS Web Coverage Service (WCS) Implementation Specification (Corrigendum)" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-040", + "@id": "http://www.opengis.net/def/docs/05-077", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-07-01" + "@value": "2006-04-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ronald Tse, Carsten Roensdorf, Allan Jamieson, Nick Nicholas, Jeffrey Lau" + "@value": "Dr. Markus M" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -39748,27 +38372,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/23-040.html" + "@id": "https://portal.ogc.org/files/?artifact_id=12636" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-040" + "@value": "05-077" }, { "@language": "en", - "@value": "OGC Guidance for the Development of Model-Driven Standards" + "@value": "Symbology Encoding Implementation Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Discussion Paper provides guidelines on how to create a specification of a conceptual model through use of a Unified Modeling Language (UML) editor and an AsciiDoc compiler. This document references Sparx Systems Enterprise Architect and the Metanorma AsciiDoc toolchain in examples that implement the OGC model-driven standards process, described in OGC 21-035r1." + "@value": "This Specification defines Symbology Encoding, an XML language for styling information that can be applied to digital Feature and Coverage data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39779,30 +38403,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-040" + "@value": "05-077" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Guidance for the Development of Model-Driven Standards" + "@value": "Symbology Encoding Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-013r4", + "@id": "http://www.opengis.net/def/docs/18-028r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-07-29" + "@value": "2019-02-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jonathan Pritchard" + "@value": "Guy Schumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -39817,17 +38441,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-013r4.html" + "@id": "https://docs.ogc.org/per/18-028r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Maritime Limits and Boundaries Pilot: Engineering Report" + "@value": "18-028r2" }, { "@language": "en", - "@value": "20-013r4" + "@value": "WMS QoSE Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -39837,7 +38461,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document comprises the Engineering Report (ER) and documents the activities under Phase 1 and Phase 2 of the OGC Maritime Limits and Boundaries (MLB) Pilot.\r\n\r\nThis Engineering Report details the activities undertaken by participants in the pilot, the data supplied, transformed, and used to demonstrate the pilot’s objectives, and the results of the various interoperability tests performed within the pilot. Also documented here are the various outputs from the pilot activities, where they are directed, and where updates or clarifications are recommended to external standards or other elements of the broader ecosystem.\r\n\r\nThe ER documents the journey taken within the project, from its origins as an architectural statement of intent, through to the definition of its core elements (the GML application schema which lends a common language to the data) and the implementation of that schema within COTS, open source and bespoke software elements. The engineering report also summarizes the outputs from the process, any unresolved issues, and potential enhancements for the future." + "@value": "Quality of Service (QoS) and Quality of Experience (QoE) as they are intended and described at the OGC are two related concepts which require very specific treatment and characterization. Citing the definitions provided by the Domain Working Group (DWG) charter document:\r\n\r\nQuality of Service: Technical reliability and performance of a network service. Typically measured using metrics like error rates, throughput, availability and delay or request response time. This Engineering Report (ER) attempts to handle QoS aspects such as service availability, scalability and speed.\r\n\r\nQuality of (User) Experience: A holistic, qualitative measure of the customers' experience of the application or service. It encompasses both the user experience and the customer support experience of the evaluated applications and/or services.\r\n\r\nQoE focuses on the usability of the information that is conceived via OGC services to end users or other client application and therefore is concerned more with qualitative aspects of such services like presence of metadata, proper and descriptive namings, appropriate styling and so on (a more thorough treatment is present in the QoE discussion paper OGC 17-049 entitled Ensuring Quality of User Experience with OGC Web Mapping Services available at https://portal.ogc.org/files/?artifact_id=74403&version=1).\r\n\r\nQoS focuses on providing reliable (i.e. quantitative ) measures of spatial data service metrics which can be used to characterize how a service ( one or more specific datasets exposed by a certain service) is performing both in near real-time as well as historically. It touches concepts like availability, scalability (also known as capacity), absolute performance (i.e. speed) and can be used to assess also perceived performance by final clients. As mentioned above, it is typically measured using metrics like error rates, throughput, availability and delay or request response time.\r\n\r\nQuite often the QoS and QoE aspects of spatial data services are underestimated if not simply ignored due to lack of resources as well as lack of awareness, resulting in services which are difficult to exploit (i.e. QoE very low) and/or unstable or very slow (i.e. QoS very low). The result is that few users end up using them after the initial launch and this is especially true for services targeting end users who are used to interact with services a-la Google Maps which delivers extreme performance and scalability as well as bullet-proof usability.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39848,35 +38472,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-013r4" + "@value": "18-028r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Maritime Limits and Boundaries Pilot: Engineering Report" + "@value": "OGC Testbed-14: WMS QoSE Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-038", + "@id": "http://www.opengis.net/def/docs/06-043r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-10-22" + "@value": "2007-05-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Omar Barrilero, Adrian Luna" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/cr" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -39886,27 +38510,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-038.html" + "@id": "https://portal.ogc.org/files/?artifact_id=17909" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Earth Observation Applications Pilot: European Union Satellite Centre Engineering Report" + "@value": "06-043r3" }, { "@language": "en", - "@value": "20-038" + "@value": "WCS: Add Transaction operation" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/cr" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) describes the achievements of the European Union Satellite Centre (SatCen) as an application provider in the OGC Earth Observation Applications Pilot and the lessons learned from the project." + "@value": "Specify an additional optional " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39917,35 +38541,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-038" + "@value": "06-043r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Earth Observation Applications Pilot: European Union Satellite Centre Engineering Report" + "@value": "Change Request: WCS: Add Transaction operation" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-045r3", + "@id": "http://www.opengis.net/def/docs/09-067r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-05-21" + "@value": "2009-10-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Kyoung-Sook KIM, Nobuhiro ISHIMARU" + "@value": "Akiko Sato, Nobuhiro Ishimaru, Guo Tao, Masaaki Tanizaki" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -39955,27 +38579,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/19-045r3/19-045r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=35334" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Moving Features Encoding Extension - JSON" + "@value": "OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report" }, { "@language": "en", - "@value": "19-045r3" + "@value": "09-067r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard defines how to encode and share the various movements of geographic features by using JavaScript Object Notation (JSON). It provides an alternative encoding for OGC Moving Features instead of that provided in the XML Core [OGC 14-083r2] and Simple CSV [OGC 14-084r2] standards. A moving feature, for instance a vehicle or a pedestrian, contains a temporal geometry whose location continuously changes over time and dynamic non-spatial attributes whose values vary with time. This Moving Features JSON encoding defines a set of keywords to implement the conceptual schema of moving features defined in ISO 19141:2008 [ISO 19141:2008], accompanied with IETF GeoJSON Format [IETF RFC 7946]." + "@value": "This document described the Outdoor and Indoor 3D Routing and Services which are used in the OGC OWS-6 Decision Support Systems (DSS) thread. The objective is to enhance a network topology for the current CityGML specification based on the knowledge acquired through the development and experimental evaluation of this project. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -39986,35 +38610,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-045r3" + "@value": "09-067r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Moving Features Encoding Extension - JSON" + "@value": "OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-126", + "@id": "http://www.opengis.net/def/docs/12-176r7", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-10-18" + "@value": "2016-06-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Chuck Morris" + "@value": "Doug Nebert, Uwe Voges, Panagiotis Vretanos, Lorenzo Bigagli, Bruce Westcott" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -40024,27 +38648,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=16860" + "@id": "https://docs.ogc.org/is/12-176r7/12-176r7.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Compliance Test Language (CTL) Discussion Paper" + "@value": "12-176r7" }, { "@language": "en", - "@value": "06-126" + "@value": "Catalogue Services 3.0 Specification - HTTP Protocol Binding" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document establishes Compliance Test Language, an XML grammar for documenting and scripting suites of tests for verifying that an implementation of a specification complies with the specification." + "@value": "This document specifies the HTTP profile of the CSW General Model part (see OGC 12-\r\n168r6). The General Model specifies the abstract interfaces between clients and catalogue\r\nservices. This standard specifies the mappingof the Catalogue abstract model interface\r\ninto the HTTP protocol binding.\r\nIn this HTTP protocol binding, operation requests and responses are sent between clients\r\nand servers using the HTTP GET and/or HTTP POST methods. Two equivalent request\r\nencodings are defined in this standard. The first using keyword-value pairs (KVP)\r\nwhich is suitable for use with the HTTP GET method. The second using XML which is\r\nsuitable for use with the HTTP POST method.\r\nThis standard defines operations that allow a client to get a service description document\r\nfor the catalogue (i.e. GetCapabilities); operations that allow a client to, at runtime,\r\ninterrogate the service about the kinds of data available (i.e. GetDomain); operations that\r\nallow a client to retrieve records from the catalogue (i.e. GetRecordById and\r\nGetRecords); operations that allow a client to add, modify and remove records from the\r\ncatalogue service (i.e. Transaction, Harvest, UnHarvest)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40055,35 +38679,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-126" + "@value": "12-176r7" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Compliance Test Language (CTL) Discussion Paper" + "@value": "OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-007", + "@id": "http://www.opengis.net/def/docs/13-080r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-11-16" + "@value": "2013-10-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "DGIWG" + "@value": "Frank Klucznik, Matthew Weber, Robin Houtmeyers, Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -40093,27 +38717,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/21-007/21-007.pdf" + "@id": "https://portal.ogc.org/files/?artifact_id=55252" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-007" + "@value": "13-080r3" }, { "@language": "en", - "@value": "Defence Geospatial Information Working Group (DGIWG) GMLJP2/JP2 Profile for Imagery & Gridded Data 2.1.2" + "@value": "Military Operations Geospatial Interoperability Experiment (MOGIE)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides a profile for JPEG 2000 for use as a\r\ncompression format for raster imagery. JPEG 2000 uses\r\ndiscrete wavelet transform (DWT) for compressing raster data,\r\nas opposed to the JPEG standard, which uses discrete cosine\r\ntransform (DCT). It is a compression technology which is best\r\nsuited for continuous raster data, such as satellite imagery and\r\naerial photography. This version adds support for\r\nReferenceable imagery." + "@value": "experiment demonstrated that GML content can be embedded in NIEM conformant XML and be exploited by commercial and open source tools without loss of precision (e.g., right number of bits) or accuracy (e.g., physical location on a map). Embedding GML in NIEM conformant XML was accomplished in MOGIE using the NIEM adapter." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40124,35 +38748,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-007" + "@value": "13-080r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Defence Geospatial Information Working Group (DGIWG) GMLJP2/JP2 Profile for Imagery & Gridded Data 2.1.2" + "@value": "OGC® Military Operations Geospatial Interoperability Experiment (MOGIE)" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-025", + "@id": "http://www.opengis.net/def/docs/19-091r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-02-08" + "@value": "2020-03-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Maso" + "@value": "Thomas Gilbert, Carsten Rönsdorf, Jim Plume, Scott Simmons, Nick Nisbet, Hans-Christoph Gruler, Thom" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -40162,27 +38786,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-025.html" + "@id": "https://portal.ogc.org/files/?artifact_id=92634" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-025" + "@value": "19-091r1" }, { "@language": "en", - "@value": "Cloud Optimized GeoTIFF specification Engineering Report" + "@value": "Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Cloud Optimized GeoTIFF (COG) is a new approach in using existing standards to accelerate distribution and analysis of 2D regular grid coverage data on the web. COG combines the use of the TIFF format with data structured internally in tiles and low resolutions subfiles (also called overviews). The main subfile is georeferenced using GeoTIFF tags and the lower resolution subfiles inherit the same georeferencing. This organization allows for retrieving only the part of the data needed for presentation or analysis. This capability is possible not only in the file system but also over the web if the HTTP range header is supported by the servers.\r\n\r\nThis OGC Testbed 17 Engineering Report (ER) discusses the COG approach, describes how GeoTIFF is used for the lower resolution subfiles, and proposes a different path forward that integrates COG with the OGC Tile Matrix Set Standard (http://docs.opengeospatial.org/is/17-083r2/17-083r2.html). The ER includes a chapter that formalizes the draft COG specification with clear requirements.\r\n\r\nOne of the common use cases for COG is the provision of multispectral remote sensing data. The increase in spatial and spectral resolution combined with more accurate sensors that require more than 8 bits per pixel results in big files that can exceed the 4 Gbyte limit of the original TIFF format. Having an OGC standard formally specifying this approach would be useful. Therefore, this ER includes a chapter that formalizes a draft BigTIFF specification, defining clear requirements.\r\n\r\nThe objective is to be able to reference BigTIFF from the GeoTIFF and the COG standards." + "@value": "Demand for digital representations of built environments is accelerating and can only be satisfied through greater software interoperability and data integration. The objective of the Integrated Digital Built Environment (IDBE) joint working group is to address this challenge by bringing together experts from the Open Geospatial Consortium and buildingSMART to coordinate the development of the relevant data standards. This document is an output from IDBE in which we describe the state of three of the most prominent built environment standards – CityGML, IFC and LandInfra – and describe some of the problems that hinder their integration; finally, we propose actions points for overcoming these problems." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40193,35 +38817,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-025" + "@value": "19-091r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: Cloud Optimized GeoTIFF specification Engineering Report" + "@value": "Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-094", + "@id": "http://www.opengis.net/def/docs/09-044r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-05-03" + "@value": "2012-07-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Vretanos " + "@value": "George Percivall, Raj Singh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -40231,27 +38855,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8339" + "@id": "https://portal.ogc.org/files/?artifact_id=49321" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Feature Service (WFS) Implementation Specification" + "@value": "09-044r3" }, { "@language": "en", - "@value": "04-094" + "@value": "Geospatial Business Intelligence (GeoBI)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS Web Feature Service Interface Standard (WFS) defines an interface[http://www.opengeospatial.org/ogc/glossary/i] for specifying requests for retrieving geographic features [http://www.opengeospatial.org/ogc/glossary/g] across the Web using platform-independent calls. The WFS standard defines interfaces and operations for data access and manipulation on a set of geographic features, including: \r\n•\tGet or Query features based on spatial and non-spatial constraints\r\n•\tCreate a new feature instance \r\n•\tGet a description of the properties of features\r\n•\tDelete a feature instance \r\n•\tUpdate a feature instance \r\n•\tLock a feature instance \r\n\r\nThe specified feature encoding for input and output is the Geography Markup Language (GML) [http://www.opengeospatial.org/standards/gml] although other encodings may be used. \r\n" + "@value": "BI is an umbrella term for a major component of IT infrastructure. It encompasses Data\r\nWarehouses, Business Analytics, Dashboards and Scorecards. This IT infrastructure is associated\r\nwith C-level decision-making in an organization. These decision-making tools have typically\r\nincluded location as a dumb attribute (coded sales zones as opposed to sales zones as geographic\r\nboundaries). At this point in the BI lifecycle, customers are looking to derive additional business\r\nbenefit / return on investment from intelligent location data; data discovery and unstructured data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40262,103 +38886,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-094" + "@value": "09-044r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Feature Service (WFS) Implementation Specification" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/as", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/99-108r2" - }, - { - "@id": "http://www.opengis.net/def/docs/99-110" - }, - { - "@id": "http://www.opengis.net/def/docs/07-011" - }, - { - "@id": "http://www.opengis.net/def/docs/10-030" - }, - { - "@id": "http://www.opengis.net/def/docs/08-126" - }, - { - "@id": "http://www.opengis.net/def/docs/06-004r4" - }, - { - "@id": "http://www.opengis.net/def/docs/18-005r8" - }, - { - "@id": "http://www.opengis.net/def/docs/99-113" - }, - { - "@id": "http://www.opengis.net/def/docs/22-010r4" - }, - { - "@id": "http://www.opengis.net/def/docs/20-082r4" - }, - { - "@id": "http://www.opengis.net/def/docs/04-084r4" - }, - { - "@id": "http://www.opengis.net/def/docs/21-053r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-111r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-087r13" - }, - { - "@id": "http://www.opengis.net/def/docs/02-112" - }, - { - "@id": "http://www.opengis.net/def/docs/00-115" - }, - { - "@id": "http://www.opengis.net/def/docs/00-116" - }, - { - "@id": "http://www.opengis.net/def/docs/04-107" - }, - { - "@id": "http://www.opengis.net/def/docs/20-040r3" - }, - { - "@id": "http://www.opengis.net/def/docs/19-014r3" - }, - { - "@id": "http://www.opengis.net/def/docs/21-060r2" + "@value": "Geospatial Business Intelligence (GeoBI)" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-017", + "@id": "http://www.opengis.net/def/docs/10-087", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-02-10" + "@value": "2010-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Wenli Yang, Arliss Whiteside" + "@value": "Wenli Yang, Liping Di" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -40368,27 +38924,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8981" + "@id": "https://portal.ogc.org/files/?artifact_id=40139" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-017" + "@value": "10-087" }, { "@language": "en", - "@value": "Web Image Classification Service (WICS)" + "@value": "OWS-7 Motion Imagery Discovery and Retrieval Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Web Image Classification Service (WICS) supports classification of digital images. A digital image is composed of pixel values organized into one or more two-dimensional arrays. The two dimensions of an image represent two axes in space based on a spatial coordinate reference system. The dimensions of the different 2-D arrays comprising an image must be the same and represent exactly the same spatial locations." + "@value": "This Motion Imagery Discovery and Retrieval Engineering Report (ER) documents the metadata used to tag geolocation of Motion Imagery (MI) for discovery, retrieval and linkage with other data sources over the same location, especially the metadata information required to geometrically co-register multiple motion images at pixel level so that data recorded at different times (e.g., different days) and/or by different providers for common or overlapped FOVs can be compared and pixel level changes among the different images can be accurately detected and delineated. This ER reflects one of the achievements during the OWS 7 Sensor Fusion Enablement (SFE) thread, which builds on the OGC Sensor Web Enablement framework that has achieved a degree of maturity through previous OWS interoperability initiatives and deployments worldwide. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40399,35 +38955,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-017" + "@value": "10-087" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Image Classification Service (WICS)" + "@value": "OWS-7 Motion Imagery Discovery and Retrieval Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-054r1", + "@id": "http://www.opengis.net/def/docs/08-078r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-11-07" + "@value": "2008-07-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Richard Martell" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -40437,27 +38993,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55342" + "@id": "https://portal.ogc.org/files/?artifact_id=29029" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Summary and Recommendations of the Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Interoperabi" + "@value": "OWS-5 ER: GSIP Schema Processing" }, { "@language": "en", - "@value": "13-054r1" + "@value": "08-078r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Geospatial information technologies are increasingly a foundation for supporting Information Sharing Environment (ISE), homeland security (HLS), homeland defense (HLD), law enforcement (LE), emergency management (EM) and public safety missions in the US. The inability to transport, deliver and exchange geospatial information for critical geospatial assets increases the risk to the nation.\r\nMany ISE HLS/HDS/LE mission partners have developed stand-alone geospatial information systems (GIS) or Common Operating Picture (COP) applications to support their stakeholder communities during incidents and for daily operational support. While different missions, these GIS/COP capabilities rely upon much of the same data or generate specific data during an event. The data are often stove-piped and not exposed to a broader community that could benefit from these data, resulting in duplication and delayed or incorrect decisions. While mission partners do not need to use the same GIS/COP tools, they could benefit from shared access to the common operating data and services used within these systems if they were exposed and exchanged using open standards.\r\nUnder the auspices of the Program Manager for the Information Sharing Environment (PM-ISE), an identified government-wide information sharing shortfall will be resolved by funding work to enhance the National Information Exchange Model (NIEM). The focus of this work is to further enhance the framework’s geospatial exchange capability in light of guidelines and standards issued by the Open Geospatial Consortium (OGC) so as to significantly improve inter-government information sharing.\r\n" + "@value": "This OGC® document describes and discusses the OWS-5 enhancements in the process of creating application schemas in support of the NSG from NGA data based on the GEOINT Structure Implementation Profile (GSIP) which has been based on the NSG Application Schema and accompanying NSG Entity Catalog. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40468,35 +39024,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-054r1" + "@value": "08-078r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Summary and Recommendations of the Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Interoperabi" + "@value": "OGC® OWS-5 ER: GSIP Schema Processing" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-035r1", + "@id": "http://www.opengis.net/def/docs/09-124r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-03-26" + "@value": "2010-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Frédéric Houbie, Steven Smolders" + "@value": "Peter Taylor" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -40506,27 +39062,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=53276" + "@id": "https://portal.ogc.org/files/?artifact_id=39090" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "EO Product Collection, Service and Sensor Discovery using the CS-W ebRIM Catalogue" + "@value": "Harmonising Standards for Water Observation Data - Discussion Paper " }, { "@language": "en", - "@value": "11-035r1" + "@value": "09-124r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This is an OGC Best Practice document describing the relations that exist between several metadata conceptual models (EO Product, EO Product Collections, Sensors and Services). The specification of the linking between different artifacts is important for the process of cataloguing and discovering those artifacts." + "@value": "This document investigates the potential for harmonisation of water data standards, with the goal of developing an OGC compliant standard for the exchange of water observation data. The work will be based on OGC‘s Observations and Measurements abstract model [10-004r2] . The goal is to create an O&M profile for the water domain. Development of the OGC compliant O&M profile will begin by examining the content and structure of existing standards and suggesting future methodology for developing a harmonised model for observation data. This approach will make use of existing standards where possible.\r\n\r\nThe focus of this document is in-situ style observations (which are generally related to water quantity). Ex-situ measurements, such as those common to measuring water quality, will be addressed in future work.\r\n2 Normative" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40537,35 +39093,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-035r1" + "@value": "09-124r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "EO Product Collection, Service and Sensor Discovery using the CS-W ebRIM Catalogue" + "@value": "Harmonising Standards for Water Observation Data - Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-004r1", + "@id": "http://www.opengis.net/def/docs/19-007", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-10-20" + "@value": "2019-08-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Volker Andres, Simon Jirka , Michael Utech" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -40575,27 +39131,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/14-004r1/14-004r1.html" + "@id": "https://docs.ogc.org/per/19-007.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-004r1" + "@value": "19-007" }, { "@language": "en", - "@value": "Sensor Observation Service 2.0 Hydrology Profile" + "@value": "CDB Vector Data in GeoPackage Interoperability Experiment" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC document defines an OGC Sensor Observation Service (SOS) 2.0 hydrology profile for SOS 2.0 implementations serving OGC WaterML 2.0. The development of this OGC Best Practice (BP) is based on previous activities and results (i.e. Hydrology Interoperability Experiments[1] as well as the European FP7 project GEOWOW[2]). The work is guided by the need to overcome semantic issues between different SOS instances serving hydrological data and the related client applications. Therefore, this profile focuses on how to use the entities and requests of the standards and defines the necessary technical details to implement the hydrology SOS profile." + "@value": "This OGC Engineering Report (ER) documents the results of the CDB Vector Data in GeoPackage Interoperability Experiment (IE). The participants in this IE tested transforming CDB Shapefile vector data into one or more GeoPackage(s) and storing the result in a CDB data store. GeoPackage Version 1.2 and CDB Version 1.1 and related Best Practices were the standards baseline used for this experiment. The IE builds on the work described in the OGC CDB, Leveraging GeoPackage Discussion Paper.\r\n\r\nA primary objective of this IE was to agree and document possible change requests and/or best practices for storing vector data in a CDB data using encodings and/or containers other than Shapefiles. These suggested changes requests and/or best/practices will be used as the basis for CDB Standards Working Group (SWG) discussions related to possible revisions to the CDB standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40606,30 +39162,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-004r1" + "@value": "19-007" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Sensor Observation Service 2.0 Hydrology Profile" + "@value": "OGC CDB Vector Data in GeoPackage Interoperability Experiment" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-019", + "@id": "http://www.opengis.net/def/docs/16-022", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-02-07" + "@value": "2017-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Martin Klopfer" + "@value": "Benjamin Pross" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -40644,17 +39200,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-019.html" + "@id": "https://docs.ogc.org/per/16-022.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Portrayal Summary ER" + "@value": "16-022" }, { "@language": "en", - "@value": "19-019" + "@value": "Testbed-12 WPS Conflation Service Profile Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -40664,7 +39220,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report provides an executive summary of the Open Portrayal Framework (OPF) Thread in OGC Testbed-15. The work in this testbed occurred between April and November 2019. Full details of the requirements, high-level architecture, and solutions are provided in the following Engineering Reports:\r\n\r\nOGC Testbed-15: Styles API Draft Specification Engineering Report\r\n\r\nOGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report\r\n\r\nOGC Testbed-15: Maps and Tiles API Draft Specification Engineering Report\r\n\r\nOGC Testbed-15: Images and Change Sets Draft Specification Engineering Report\r\n\r\nOGC Testbed-15: Open Portrayal Framework Engineering Report" + "@value": "One practical purpose of this ER will be to describe how a conflation tool such as the Hootenanny software can be used for conflation tasks using the Web Processing Service interface. The developed WPS REST (conflation) Service will be described in detail. Special focus will be laid on more complex conflation tasks that include user interaction. During earlier testbeds, we connected different conflation tools to the WPS and performed different conflation tasks (see [1] and [2]). The experiences gathered there together with the ones gathered in the Testbed 12 will be captured in the ER. As the WPS REST (Conflation) Service will be RESTful, this ER could be the basis for a REST binding extension for WPS 2.0. Service profiles are an important aspect of the WPS 2.0 standard. We will investigate how a WPS 2.0 Conflation Profile could look like in the hierarchical profiling approach of WPS 2.0." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40675,30 +39231,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-019" + "@value": "16-022" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Portrayal Summary ER" + "@value": "Testbed-12 WPS Conflation Service Profile Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-061", + "@id": "http://www.opengis.net/def/docs/16-098", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-05-12" + "@value": "2017-10-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Terry Idol" + "@value": "Kanishk Chaturvedi, Thomas H. Kolbe" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -40713,17 +39269,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/17-061" + "@id": "https://docs.ogc.org/per/16-098.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "FGDC OGC Application Programming Interface Interoperability Assessment" + "@value": "Future City Pilot 1 Engineering Report" }, { "@language": "en", - "@value": "17-061" + "@value": "16-098" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -40733,7 +39289,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Federal Geographic Data Committee (FGDC) Application Programming Interface (API) assessment was conducted under the OGC Innovation Program with the goal to develop an in-depth understanding of all the components necessary to enable increased coordination and effectiveness of APIs as applied to geospatial information. FGDC customers have been invited to share their experiences with the use of APIs. From those descriptions, recommendations have been derived that help FGDC to better understand how APIs are currently being generated and if using a more standardized approach to APIs might enable a more robust and optimized service offering. " + "@value": "The Future City Pilot Phase 1 (FCP1) is an OGC Interoperability Program initiative in collaboration with buildingSMART International (bSI). The pilot aimed at demonstrating and enhancing the ability of spatial data infrastructures to support quality of life, civic initiatives, and urban resilience. During the pilot, multiple scenarios were set up based on real-world requirements and were put forward by the pilot sponsors: Sant Cugat del Vallès (Barcelona, Spain), Ordnance Survey Great Britain (UK), virtualcitySYSTEMS GmbH (Germany), and Institut National de l’Information Géographique et Forestière - IGN (France). The scenarios were focused on (i) the interoperability between the two international standards: Industry Foundation Classes (IFC) and CityGML; (ii) city flood modeling; and (iii) supporting real-time sensor readings and other time-dependent properties within semantic 3D city models. The solutions for the respective scenarios were developed by the pilot participants: University of Melbourne (Australia), Remote Sensing Solutions, Inc. (U.S.A), and Technical University of Munich (Germany). This Engineering Report (ER) focuses on the third scenario requiring the support of real-time sensors and other time-dependent properties within semantic 3D city models based on the CityGML standard. It highlights a new concept 'Dynamizer', which allows representation of highly dynamic data in different and generic ways and providing a method for injecting dynamic variations of city object properties into the static representations. It also establishes explicit links between sensor/observation data and the respective properties of city model objects that are measured by them. The Dynamizer concept has been implemented as an Application Domain Extension (ADE) of the CityGML standard. This implementation allows to use new dynamizer features with the current version of the CityGML standard (CityGML 2.0). The advantage with this approach is that it allows for selected properties of city models to become dynamic without changing the original CityGML data model. If an application does not support dynamic data, it simply does not allow/include these special types of features. The details and results of the pilot are mentioned in the following YouTube video: https://youtu.be/aSQFIPwf2oM" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40744,35 +39300,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-061" + "@value": "16-098" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "FGDC OGC Application Programming Interface Interoperability Assessment" + "@value": "Future City Pilot 1 Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-007r5", + "@id": "http://www.opengis.net/def/docs/05-117", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2006-05-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sara Saeedi" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -40782,27 +39338,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/16-007r5/16-007r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=12893" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-007r5" + "@value": "Schema Maintenance and Tailoring" }, { "@language": "en", - "@value": "Volume 11: OGC CDB Core Standard Conceptual Model" + "@value": "05-117" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB Standard. The objective of this document is to provide an core conceptual model for a CDB data store (repository). The model is represented using UML (Unified Modeling Language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering the UML diagrams and documentation from the original CDB submission OGC Common DataBase Volume 1 Best Practice, 2015 as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113r5]." + "@value": "Description of the schema tailoring process for the application schema development in the decision support services thread (GeoDSS) during the OWS-3 initiative" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40813,35 +39369,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-007r5" + "@value": "05-117" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 11: OGC CDB Core Standard Conceptual Model" + "@value": "Schema Maintenance and Tailoring" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-131r1", + "@id": "http://www.opengis.net/def/docs/21-025", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-08-22" + "@value": "2022-02-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Aaron Braeckel , Lorenzo Bigagli , Johannes Echterhoff" + "@value": "Joan Maso" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -40851,27 +39407,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/13-131r1/13-131r1.html" + "@id": "https://docs.ogc.org/per/21-025.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "13-131r1" + "@value": "Cloud Optimized GeoTIFF specification Engineering Report" }, { "@language": "en", - "@value": "Publish/Subscribe Interface Standard 1.0 - Core" + "@value": "21-025" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Publish/Subscribe 1.0 is an interface specification that supports the core components and concepts of the Publish/Subscribe message exchange pattern with OGC Web Services. The Publish/Subscribe pattern complements the Request/Reply pattern specified by many existing OGC Web Services. This specification may be used either in concert with, or independently of, existing OGC Web Services to publish data of interest to interested Subscribers.\r\n\r\nPublish/Subscribe 1.0 primarily addresses subscription management capabilities such as creating a subscription, renewing a subscription, and unsubscribing. However, this standard also allows Publish/Subscribe services to advertise and describe the supported message delivery protocols such as SOAP messaging, ATOM, and AMQP. Message delivery protocols should be considered to be independent of the Publish/Subscribe 1.0 standard. Therefore, OGC Publish/Subscribe only includes metadata relating to message delivery protocols in sufficient detail to allow for different implementations of Publish/Subscribe 1.0 to interoperate. \r\n\r\nThis specification defines Publish/Subscribe functionality independently of the binding technology (e.g., KVP, SOAP, REST). Extensions to this specification may realize these core concepts with specific binding technologies." + "@value": "Cloud Optimized GeoTIFF (COG) is a new approach in using existing standards to accelerate distribution and analysis of 2D regular grid coverage data on the web. COG combines the use of the TIFF format with data structured internally in tiles and low resolutions subfiles (also called overviews). The main subfile is georeferenced using GeoTIFF tags and the lower resolution subfiles inherit the same georeferencing. This organization allows for retrieving only the part of the data needed for presentation or analysis. This capability is possible not only in the file system but also over the web if the HTTP range header is supported by the servers.\r\n\r\nThis OGC Testbed 17 Engineering Report (ER) discusses the COG approach, describes how GeoTIFF is used for the lower resolution subfiles, and proposes a different path forward that integrates COG with the OGC Tile Matrix Set Standard (http://docs.opengeospatial.org/is/17-083r2/17-083r2.html). The ER includes a chapter that formalizes the draft COG specification with clear requirements.\r\n\r\nOne of the common use cases for COG is the provision of multispectral remote sensing data. The increase in spatial and spectral resolution combined with more accurate sensors that require more than 8 bits per pixel results in big files that can exceed the 4 Gbyte limit of the original TIFF format. Having an OGC standard formally specifying this approach would be useful. Therefore, this ER includes a chapter that formalizes a draft BigTIFF specification, defining clear requirements.\r\n\r\nThe objective is to be able to reference BigTIFF from the GeoTIFF and the COG standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40882,30 +39438,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-131r1" + "@value": "21-025" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Publish/Subscribe Interface Standard 1.0 - Core" + "@value": "OGC Testbed-17: Cloud Optimized GeoTIFF specification Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-083", + "@id": "http://www.opengis.net/def/docs/16-049r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-11" + "@value": "2017-06-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Joan Masó" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -40920,17 +39476,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-083.html" + "@id": "https://docs.ogc.org/per/16-049r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "WMTS Vector Tiles Extension Engineering Report" + "@value": "Testbed-12 Multi-Tile Retrieval ER" }, { "@language": "en", - "@value": "18-083" + "@value": "16-049r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -40940,7 +39496,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The tiling of feature data is an approach that can be used to optimize the delivery vector feature data over the web to create maps. The approach provides a pre-defined shape (i.e. tile) to package vector data. Tiling of vector data enables faster map loads (due to reduced size) and offer flexible styling on the client side with modern, easy-to-use tools.\r\n\r\nThis Engineering Report (ER) describes the work done by participants during the Vector Tiles Pilot (VTP) to add Mapbox and GeoJSON vector tile support to Web Map Tile Servers. A summary of other work done in the VTP is presented in the VTP Summary Engineering Report [1].\r\n\r\nNOTE\r\nThis engineering report interchangeably uses both 'tiled feature data' and the colloquial term 'vector tiles'." + "@value": "With the consolidation of tiling services and the increasing number of instances implementing the WMTS standard, there is a need for having a way to transfer a collection of tiles from one service to another. This might also be useful to transfer all necessary tiles from a WMTS service to a GeoPackage. Currently the only available solution is a client that is able to resolve the identifiers of the tiles needed and that builds a WMTS independent request for each tile. This ER explores different solutions that are more appropriate depending on how many tiles we need to move and the final application of them. Some of the proposed solutions involve changes in the WMTS standard and the use of a WPS. The WPS standard also shows some limitations and extensions that should be addressed.\r\n\r\nIn essence all solutions should describe two things: A request that contains a filter to a collection of tiles filling regions of the space and a multipart response that contains the tiles preferably in a single package. Depending on the proposed architecture, these tasks are done directly in the client, in the WMTS server or in an intermediate WPS." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -40951,35 +39507,69 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-083" + "@value": "16-049r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Vector Tiles Pilot: WMTS Vector Tiles Extension Engineering Report" + "@value": "Testbed-12 Multi-Tile Retrieval ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-027r1", + "@id": "http://www.opengis.net/def/doc-type/d-sap/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Specification Application Profile - deprecated" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Specification Application Profile - deprecated" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/02-058" + }, + { + "@id": "http://www.opengis.net/def/docs/09-146r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Specification Application Profile - deprecated" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/16-006r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-25" + "@value": "2017-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -40989,27 +39579,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21702" + "@id": "https://portal.ogc.org/files/?artifact_id=72722" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-027r1" + "@value": "16-006r3" }, { "@language": "en", - "@value": "Local MSD Implementation Profile (GML 3.2.1)" + "@value": "Volume 10: OGC CDB Implementation Guidance" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document contains a data content specification for Local Mission Specific Data (MSD) and is based on the GEOINT Structure Implementation Profile (GSIP) developed by the NGA. This document defines the GML 3.2.1 (ISO 19136) encoding requirements for Local MSD. The structure of the document is based on ISO/DIS 19131 (Geographic Information " + "@value": "This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41020,35 +39610,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-027r1" + "@value": "16-006r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Local MSD Implementation Profile (GML 3.2.1)" + "@value": "Volume 10: OGC CDB Implementation Guidance" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-104", + "@id": "http://www.opengis.net/def/docs/05-057r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-03-30" + "@value": "2006-03-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman" + "@value": "Jolyon Martin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -41058,27 +39648,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=887" + "@id": "https://portal.ogc.org/files/?artifact_id=14443" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "99-104" + "@value": "Catalogue Services - Best Practices for for Earth Observation Products" }, { "@language": "en", - "@value": "Topic 04 - Stored Functions and Interpolation" + "@value": "05-057r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Topic Volume provides essential and abstract models for technology that is used widely across the GIS landscape. Its first heavy use is expected to occur in support of Coverage specifications (see Topic 6, The Coverage Type)." + "@value": "The services proposed in this profile are intended to support the identification and subsequent ordering of EO data products from previously identified data collections. The intent of this initial profile is to describe a minimum interface that can be supported by many data providers (satellite operators, data distributors...), most of whom have existing (and relatively complex) facilities for the management of these data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41089,35 +39679,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-104" + "@value": "05-057r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 4 - Stored Functions and Interpolation" + "@value": "OpenGIS Catalogue Services - Best Practices for for Earth Observation Products" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-020", + "@id": "http://www.opengis.net/def/docs/99-105r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-04-04" + "@value": "1999-03-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff" + "@value": "Cliff Kottman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -41127,27 +39717,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-020.html" + "@id": "https://portal.ogc.org/files/?artifact_id=890" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 ShapeChange Engineering Report" + "@value": "Topic 05 - Features" }, { "@language": "en", - "@value": "16-020" + "@value": "99-105r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a deliverable of the OGC Testbed 12. It describes the results of enhancing the tool ShapeChange in the following areas of processing an ISO 19109 conformant application schema:\r\n\r\nCreating a schema profile - to support implementations that focus on a subset of the use cases in scope of the original application schema.\r\n\r\nDeriving an ontology representation of the application schema (using RDF(S)/SKOS/OWL) - to support Semantic Web / Linked Data implementations." + "@value": "A feature object (in software) corresponds to a real world or abstract entity." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41158,35 +39748,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-020" + "@value": "99-105r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 ShapeChange Engineering Report" + "@value": "Topic 5 - Features" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-033", + "@id": "http://www.opengis.net/def/docs/15-098r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-13" + "@value": "2016-12-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sam Meek" + "@value": "Joan Masó, Lucy Bastin " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -41196,27 +39786,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-033.html" + "@id": "https://docs.ogc.org/is/15-098r1/15-098r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-033" + "@value": "15-098r1" }, { "@language": "en", - "@value": "OpenAPI Engineering Report" + "@value": "Geospatial User Feedback Standard: XML Encoding Extension" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 16 Engineering Report (ER) documents the two major aspects of the Testbed 16 OpenAPI Thread. These are:\r\n\r\nA Unified Modeling Language (UML) metamodel that describes OpenAPI and a profile of that model to describe OGC API - Features - Part 1: Core;\r\n\r\nAn implementation of a transformation procedure in the ShapeChange open source software. This procedure was designed to transform a UML representation of the OGC API - Features - Part 1: Core model into an OpenAPI 3.0 document.\r\n\r\nThe process for creating the model and doing the transformation relied upon the Model Driven Architecture (MDA) approach. MDA takes a platform independent model (PIM) and transforms that model into a platform specific model (PSM)." + "@value": "The Geospatial User Feedback XML encoding standard is based on the OGC Geospatial User Feedback conceptual model [OGC 15-097]. Geospatial User Feedback (GUF) is metadata that is predominantly produced by the consumers of geospatial data products based on their use and experience with those products. This standard complements the existing metadata conventions whereby documents recording dataset characteristics and production workflows are generated by the creator, publisher, or curator of a data product. As a part of metadata, the GUF data model internally reuses some elements of ISO 19115-1 (the updated version of the OGC Abstract Specification Topic 11) but not the general structure. This selective use of ISO metadata elements prioritizes future interoperability with developing ISO metadata models.\r\nThis standard can be used in combination with the OGC 15-097 Conceptual Model Standard. In the future, other encodings may be considered, being an alternative using the JSON-LD encoding based on parts of schema.org.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41227,35 +39817,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-033" + "@value": "15-098r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: OpenAPI Engineering Report" + "@value": "OGC® Geospatial User Feedback Standard: XML Encoding Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-074r1", + "@id": "http://www.opengis.net/def/docs/19-090r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-12-17" + "@value": "2020-04-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Frans Knibbe, Alejandro Llaves" + "@value": "Ki-Joune Li, Sung-Hwan Kim, Yong-Bok Choi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -41265,27 +39855,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/15-074r1/15-074r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=92039" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Spatial Data on the Web Use Cases & Requirements" + "@value": "An Experiment to Link Geo-Referenced Multimedia and CityGML Features" }, { "@language": "en", - "@value": "15-074r1" + "@value": "19-090r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC. " + "@value": "In this paper, we present an experiment on linking geo-referenced images and videos with CityGML objects. Data models are proposed with XML schema from two viewpoints: one for linking features in 2D images or videos with 3D CityGML objects and the other for camera FoV (Field of View). In order to validate the proposed data models, we developed an authoring tool for building XML documents to link geo-referenced images and videos with CityGML objects and a web environment for processing queries based on the linking data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41296,30 +39886,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-074r1" + "@value": "19-090r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Spatial Data on the Web Use Cases & Requirements" + "@value": "An Experiment to Link Geo-Referenced Multimedia and CityGML Features" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-073r1", + "@id": "http://www.opengis.net/def/docs/22-018", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-07-29" + "@value": "2023-01-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Volker Coors" + "@value": "Yves Coene, Christophe Noel" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -41334,17 +39924,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-073r1.html" + "@id": "https://docs.ogc.org/per/22-018.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "3D-IoT Platform for Smart Cities Engineering Report" + "@value": "22-018" }, { "@language": "en", - "@value": "19-073r1" + "@value": "Testbed-18: Secure Asynchronous Catalog Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -41354,7 +39944,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Recent years have seen a significant increase in the use of three-dimensional (3D) data in the Internet of Things (IoT). The goal of the 3D IoT Platform for Smart Cities Pilot was to advance the use of open standards for integrating environmental, building, and IoT data in Smart Cities. Under this initiative a proof of concept (PoC) has been conducted to better understand the capabilities to be supported by a 3D IoT Smart City Platform under the following standards: CityGML, IndoorGML, SensorThings API, 3D Portrayal Service, and 3D Tiles." + "@value": "This OGC Testbed-18 Engineering Report (ER) describes the results of the Secure, Asynchronous Catalogs Task in the Testbed-18 Catalogs, Filtering, and Moving Features (CMF) thread. This task explored the following.\r\n\r\nHow search processes that are supported in a classical OGC Catalogue Service for the Web (CSW)/ISO 19115 environment can be supported through tailoring of the OGC API-Records specification.\r\nHow an asynchronous catalog scenario can be supported in which metadata publishers push new data to catalog instances that lead to new or updated catalog entries and how subscribers are informed about these updates.\r\nHow Data Centric Security (DCS) can be applied in combination with OGC API-Records to allow encrypted delivery and access of catalog metadata between communication partners." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41365,35 +39955,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-073r1" + "@value": "22-018" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC 3D-IoT Platform for Smart Cities Engineering Report" + "@value": "Testbed-18: Secure Asynchronous Catalog Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-095", + "@id": "http://www.opengis.net/def/docs/14-083r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-05-03" + "@value": "2015-02-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Vretanos" + "@value": "Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -41403,27 +39993,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8340" + "@id": "https://docs.ogc.org/is/14-083r2/14-083r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-095" + "@value": "Moving Features Encoding Part I: XML Core" }, { "@language": "en", - "@value": "Filter Encoding Implementation Specification" + "@value": "14-083r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Filter Encoding Standard (FES) defines an XML encoding for filter expressions. A filter expression logically combines constraints on the\r\nproperties of a feature in order to identify a particular subset of features to be operated upon. For example, a subset of features might be identified to render them in a particular color or convert them into a user-specified format. Constraints can be specified on values of spatial, temporal and scalar properties. An example of a filter is: Find all the properties in Omstead County owned by Peter Vretanos.\r\n\r\nThis standard is used by a number of OGC Web Services, including the Web Feature Service [http://www.opengeospatial.org/standards/wfs], the Catalogue Service [http://www.opengeospatial.org/standards/cat] and the Styled Layer Descriptor Standard [http://www.opengeospatial.org/standards/sld]. \r\n" + "@value": "This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41434,30 +40024,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-095" + "@value": "14-083r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Filter Encoding Implementation Specification" + "@value": "OGC® Moving Features Encoding Part I: XML Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-007", + "@id": "http://www.opengis.net/def/docs/12-147", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-15" + "@value": "2013-02-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthes Rieke" + "@value": "Claude Speed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -41472,17 +40062,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=58931" + "@id": "https://portal.ogc.org/files/?artifact_id=51823" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-007" + "@value": "12-147" }, { "@language": "en", - "@value": "Testbed 10 Report on Aviation Binding AIXM to Development Tools" + "@value": "OWS-9 Aviation Architecture Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -41492,7 +40082,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a deliverable of the OGC Testbed 10 (Testbed-10). Its contents cover the summary of the work carried out regarding the creation and evaluation of generated data bindings for the Aeronautical Information Exchange Model (AIXM) for established programming languages.\r\nSuggested additions, changes, and comments on this draft report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document.\r\n" + "@value": "This OGC® document describes the architecture implemented in the OWS-9 Aviation thread, including:\r\n•\tA description of the architecture used for the implementation of the OWS-9 Aviation Use Cases.\r\n•\tAn overview of the implemented components and workflows followed by a short description of each component. \r\n•\tA discussion about discovery and registry methods and practices.\r\n•\tDocumentation of the issues, lessons learned as well as accomplishments and scenarios that were of general interest in the Aviation thread.\r\nMore detailed information on specific aspects considered in OWS-9 Aviation may be found in the individual Aviation Engineering Reports.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41503,35 +40093,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-007" + "@value": "12-147" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 10 Report on Aviation Binding AIXM to Development Tools" + "@value": "OWS-9 Aviation Architecture Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-075", + "@id": "http://www.opengis.net/def/docs/02-061r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-08-22" + "@value": "2002-09-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arne Schilling, Benjamin Hagedorn, Volker Coors " + "@value": "Andreas Poth, Markus Muller" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -41541,27 +40131,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=49068" + "@id": "https://portal.ogc.org/files/?artifact_id=1174" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-075" + "@value": "02-061r1" }, { "@language": "en", - "@value": "3D Portrayal Interoperability Experiment FINAL REPORT " + "@value": "Web Coordinate Transformation Service" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the results of an OGC Interoperability Experiment (IE) on the portrayal of 3D geospatial information. It contains technical details on processing 3D information in an OGC service environment as well as best practices on how to portray large data sets in urban planning scenarios, taking into account architectures and capabilities of interactive 3D graphics. Especially Web 3D Service and Web View Service, two draft standards (published as OGC discussions paper), have been in the focus of 3DPIE. " + "@value": "This document specifies the transformations of geo-spatial coordinates from one Coordinate Reference System (CRS) into another by means of a Web Service" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41572,30 +40162,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-075" + "@value": "02-061r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC 3D Portrayal Interoperability Experiment FINAL REPORT " + "@value": "Web Coordinate Transformation Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-077r1", + "@id": "http://www.opengis.net/def/docs/20-020", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-02-03" + "@value": "2021-01-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "Sergio Taleisnik" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -41610,17 +40200,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64406" + "@id": "https://docs.ogc.org/per/20-020.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-077r1" + "@value": "Aviation Engineering Report" }, { "@language": "en", - "@value": "Testbed-11 SOAP Interface Engineering Report: Comparison on the Usage of SOAP Across OGC Web service interfaces" + "@value": "20-020" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -41630,7 +40220,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A number of OGC service interface standards define SOAP bindings. Despite the current hype around REST or RESTful interfaces, SOAP services are still used intensively, in particular in security-critical environments. A number of OGC Web service interfaces support SOAP bindings (see chapter 6). Unfortunately, those bindings are not fully consistent across the suite of OGC service standards. Differences can be found in terms of SOAP versions, used namespaces, error handling, capabilities documentation, or transport of non-XML data; i.e. aspects that should be harmonized by a cross-standard working group. \r\nThis document seeks to provide an overview of the current situation and guidance on future SOAP harmonization across all OGC Web services. A number of change requests have been developed during the development process for this document. Though this document provides recommendations in chapter 8, it is highly recommended to either form a new SOAP working group, or preferably to assign the development of SOAP best practices to reduce the risk of missed requirements and architecture arguments to the newly reformed OWS Common SWG. The best practices could then be applied to all OGC service standards that offer SOAP bindings.\r\n" + "@value": "This Testbed-16 Aviation Engineering Report (ER) summarizes the implementations, findings and recommendations that emerged from the efforts of further advancing interoperability and usage of Linked Data within the Federal Aviation Administration (FAA) System Wide Information Management (SWIM) context. The goal of this effort was to experiment with OpenAPI and Linked Data to explore new ways for locating and retrieving SWIM data in order to enable consumers to consume SWIM data more easily in their business applications, and enable the discovery of additional relevant information for their needs.\r\n\r\nSpecifically, this ER documents the possibility of querying and accessing data (and its metadata) using Semantic Web Technologies as well as interlinking heterogeneous semantic data sources available on the Web. Together with an analysis on the potential for using OpenAPI-based Application Programming Interface (API) definitions to simplify access to geospatial information, an exploration of solutions for data distribution that complement those currently used by SWIM is presented." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41641,35 +40231,43 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-077r1" + "@value": "20-020" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed-11 SOAP Interface Engineering Report: Comparison on the Usage of SOAP Across OGC Web service interfaces" + "@value": "OGC Testbed-16: Aviation Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-043", + "@id": "http://www.opengis.net/def/doc-type/d-per", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/22-020" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/22-049r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-07-05" + "@value": "2023-09-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Liping Di, David J. Meyer,r Eugene Yu" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -41679,27 +40277,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-043.html" + "@id": "https://docs.ogc.org/is/22-049r1/22-049r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-043" + "@value": "OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0" }, { "@language": "en", - "@value": "OGC Testbed 19 Analysis Ready Data Engineering Report" + "@value": "22-049r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Implementations of the Analysis Ready Data (ARD) concept are consistent with the FAIR principles of finding, accessing, interoperating, and reusing physical, social, and applied science data with ease. The goal of this Testbed 19 OGC Engineering Report (ER) is to advance the provision of geospatial information by creating, developing, identifying, and implementing ARD definitions and capabilities. Specifically, this ER aims to increase the ease of use of ARD through improved backend standardization and varied application scenarios. Additionally, this work seeks to inform ARD implementers and users about standards and workflows to enhance the capabilities and operations of ARD. Ultimately, the goal of the work described in this ER is to maximize ARD capabilities and operations and contribute to the enhancement of geospatial information provision.\r\n\r\nFour distinct scenarios – gentrification, synthetic data, coverage analysis, and coastal studies – are explored to reveal both the strengths and limitations of the current ARD framework. The gentrification scenario, which utilizes existing Committee on Earth Observation Satellites (CEOS) ARD data, highlights the need to expand ARD’s scope beyond Earth Observation (EO) data. The integration of diverse data types, such as building footprints and socio-economic statistics, is crucial for comprehensive analysis. The synthetic data scenario explores the potential of simulated EO imagery to enhance data availability and diversity for machine learning applications. However, challenges in standardization and quality assessment require further investigation. The analysis of coverages for ARD reveals the importance of clear pixel interpretation (“pixel-is-point” vs. “pixel-is-area”) and standardized units of measure for seamless integration and analysis. Additionally, enriching the metadata structure with defined extensions is crucial for efficient data discovery and understanding. The coastal study scenario, where in-situ data needs to be elevated to ARD, emphasizes the need for flexible levels of readiness. Different analytical tasks may require distinct data properties, necessitating adaptable standards that cater to temporal emphasis, spatial alignment, and non-GIS applications like machine learning.\r\n\r\nThis work identified several key areas for improvement:\r\n\r\nencompassing non-EO data such as building footprints, socio-economic statistics, synthetic data, and in-situ measurements;\r\nestablishing guidelines and quality controls for incorporating diverse data types;\r\ntailoring data specifications to accommodate different analytical needs, including temporal emphasis and non-GIS applications; and\r\nimplementing structured metadata with defined extensions for enhanced data discovery, understanding, and provenance tracking.\r\nIn addition to the above recommendations, the interoperability and support of ARD in wider communities warrants further exploration and implementation. Additionally, areas such as uniform evaluation and compliance certification could be further investigated to ensure consistency in data readiness across various hierarchies and application domains." + "@value": "The Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 defines a geospatial extension to the OASIS eXtensible Access Control Markup Language (XACML) Version 3.0 Standard. GeoXACML 3.0 supports the interoperable definition of access rights including geographic conditions based on the XACML 3.0 language, processing model and policy schema. GeoXACML 3.0 provides improvements based on enhancements to the XACML Standard, primarily the support of access conditions spanning different XACML categories. This enhancement empowers GeoXACML 3.0 to be a powerful decision engine with support for spatiotemporal access conditions.\r\n\r\nAs a result of the XACML 3.0 deployment model and corresponding implementation flexibility, GeoXACML 3.0 can be operated as a traditional Policy Decision Point or as a cloud-native API gateway.\r\n\r\nThe OGC GeoXACML 3.0 Standard defines different conformance classes that supports flexible implementation conformance. Implementation of the Core conformance class supports the ISO 19125 geometry model including topological test (spatial relations) functions which enables the indexing of access conditions-based geometry. The Spatial Analysis conformance class extends the topological test functions for defining access conditions including the processing of geometries. To support condition evaluation for geometries encoded in different Coordinate Reference System (CRS), the CRS Transformation conformance class enables a compliant implementation to undertake dynamic CRS transformation during decision-making unless prohibited per request. Finally, the API conformance class enables operating a GeoXACML 3.0 compliant implementation as an OGC API conformant service (Policy Decision Point)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41710,30 +40308,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-043" + "@value": "22-049r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed 19 Analysis Ready Data Engineering Report" + "@value": "OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-095", + "@id": "http://www.opengis.net/def/docs/09-102", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-25" + "@value": "2009-09-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "DGIWG" + "@value": "Cyril Minoux" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -41748,17 +40346,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/95763" + "@id": "https://portal.ogc.org/files/?artifact_id=34833" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Defence Geospatial Information Working Group (DGIWG) GeoTIFF/TIFF Profile for Imagery & Gridded Data 2.3.1" + "@value": "DGIWG WMS 1.3 Profile and systems requirements for interoperability for use within a military environment" }, { "@language": "en", - "@value": "20-095" + "@value": "09-102" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -41768,7 +40366,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Best Practice was developed by the Defence Geospatial Information Working Group to address defense and intelligence user community requirements. As such, the Best Practice utilizes standardized military Coordinate Reference System (CRS) definitions, which may not be applicable to other user communities.\r\nThis Best Practice also defines a GEO_METADATA tag, which may be of more general interest.\r\n" + "@value": "This document specifies requirements for systems providing maps using OGC Web Map Service. The document defines a profile of OGC WMS 1.3 implementation standard [WMS1.3], a list of normative system requirements and a list of non-normative recommendations. The Defence Geospatial Information Working Group (DGIWG) performed the work as part of through the S05 Web Data Access Service Project of the Services & Interfaces Technical Panel." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41779,35 +40377,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-095" + "@value": "09-102" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Defence Geospatial Information Working Group (DGIWG) GeoTIFF/TIFF Profile for Imagery & Gridded Data 2.3.1" + "@value": "DGIWG WMS 1.3 Profile and systems requirements for interoperability for use within a military environment" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-043r1", + "@id": "http://www.opengis.net/def/docs/05-087r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-12-16" + "@value": "2006-10-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Joana Simoes" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -41817,27 +40415,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-043r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=17038" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-043r1" + "@value": "Observations and Measurements" }, { "@language": "en", - "@value": "Joint OGC and ISO Code Sprint 2022 Summary Engineering Report" + "@value": "05-087r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from the 14th to the 16th of September 2022 to advance open standards that relate to geospatial metadata and catalogues. The code sprint was hosted by the Open Geospatial Consortium (OGC) and the International Organization for Standardization (ISO). The code sprint was sponsored by Ordnance Survey (OS) and Geonovum, and held as a hybrid event with the face-to-face element hosted at the Geovation Hub in London, United Kingdom." + "@value": "The general models and XML encodings for observations and measurements, including but not restricted to those using sensors." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41848,41 +40446,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-043r1" + "@value": "05-087r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Joint OGC and ISO Code Sprint 2022 Summary Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/primer", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/12-077r1" - }, - { - "@id": "http://www.opengis.net/def/docs/10-091r3" + "@value": "Observations and Measurements" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-069r2", + "@id": "http://www.opengis.net/def/docs/23-042", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-08-02" + "@value": "2024-07-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Sina Taghavikish" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -41897,17 +40484,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39476" + "@id": "https://docs.ogc.org/per/23-042.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-7 Engineering Report - Geosynchronization service" + "@value": "23-042" }, { "@language": "en", - "@value": "10-069r2" + "@value": "OGC Testbed-19 — Non-Terrestrial Geospatial Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -41917,7 +40504,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This candidate standard describes a service that allows data collectors to propose changes to be made to a data provider's features. A change proposal can be made to create new data or to modify/delete existing data. Proposed changes are reviewed (either manually or automatically) an are either accepted or rejected. Accepted changes are applied to the feature(s). The service also maintains a log of all changes applied to each feature that can be used for replication." + "@value": "Testbed-18 explored the potential use of OGC Standards for non-terrestrial applications and was scoped as a paper study. Validation of the Testbed-18 recommendations has been left for Testbed-19. This OGC Engineering Report (ER) documents recommended changes to OGC Standards and the implementation experience to justify those changes.\r\n\r\nThe use of OGC Standards include geospatial applications for non-Earth planets as well as interplanetary spatiotemporal applications. Two Standards emerged as key: ISO 19111 (OGC Abstract Specification 2: Referencing by coordinates) and OGC 21-056r11 (OGC GeoPose 1.0 Data Exchange Standard). Extensions to ISO 19111 were identified which would support the representation of non-terrestrial planetary spatial reference systems as well as interplanetary spatiotemporal reference systems.\r\n\r\nThe GeoPose Standard (GeoPose) was explored as a mechanism to integrate the large number of reference systems and transformations needed to model the geometry of interplanetary spacetime.\r\n\r\nIn the context of the Double Asteroid Redirection Test (DART) scenario, positions and orientations in different coordinate reference systems and associated attributes such as velocities of non-terrestrial objects were encoded using two different approaches: as sequences of extended GeoPoses, and as OGC Moving Features JSON (MF-JSON). These encoded data were then used as the basis for a 3D visualization demonstration.\r\n\r\nThis work is not intended to replace the existing standards already used in astronomy such as the World Coordinate System (WCS). The recommendations provided in this ER are rather intended to improve interoperability by specifying how to export a subset of a WCS description as OGC/ISO data structures for consumption by GIS software or other geospatial technology applications.\r\n\r\nTestbed-18 also investigated how GeoPose could be integrated with mobile location-aware devices such as smartphones. Engineering Report OGC 22-016r3 (Testbed-18: Moving Features) concluded that GeoPose could enrich data with location and orientation information synchronized to video and other sensors and identified two suitable road network use cases for study using WebVMT in Testbed-19." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41928,30 +40515,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-069r2" + "@value": "23-042" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-7 Engineering Report - Geosynchronization service" + "@value": "OGC Testbed-19 — Non-Terrestrial Geospatial Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-006r1", + "@id": "http://www.opengis.net/def/docs/10-035r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-15" + "@value": "2010-09-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Daniel Balog" + "@value": "David Rosinger, Stan Tillman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -41966,17 +40553,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=59793" + "@id": "https://portal.ogc.org/files/?artifact_id=40441" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 10 Recommendations for Exchange of Terrain Data" + "@value": "10-035r2" }, { "@language": "en", - "@value": "14-006r1" + "@value": "OWS-7 Information Sharing Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -41986,7 +40573,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a deliverable of the OGC Testbed 10 (Testbed-10). Its contents cover the summary of the work carried out regarding the recommendations for the exchange of terrain data.\r\nSuggested additions, changes, and comments on this draft report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document.\r\nThe changes made in this document version, relative to the previous version, are tracked by Microsoft Word, and can be viewed if desired. If you choose to submit suggested changes by editing this document, please first accept all the current changes, and then make your suggested changes with change tracking on.\r\n" + "@value": "This Engineering Report describes an investigation and evaluation of various methods of sharing information within a collaborative environment accomplished during the OGC Web Services Testbed, Phase 7 (OWS-7). The intent of the OWS-7 Information Sharing activity was to move toward a standardized method of sharing geospatial data between Integrated Clients and potentially catalogs. This report reviews past OGC work within this area, makes recommendations based on the best parts of previous collaboration techniques, and provides recommendations for encoding documents for use in information sharing." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -41997,35 +40584,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-006r1" + "@value": "10-035r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 10 Recommendations for Exchange of Terrain Data" + "@value": "OWS-7 Information Sharing Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-022r1", + "@id": "http://www.opengis.net/def/docs/15-112r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-08-22" + "@value": "2018-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Hsiao-Yuan (Samuel) Yin, Yi-Chia (Vincent) Lin, Chih-Wei (Will) Kuan, Cheng-Yan Tsai, Lok-Man (Lawre" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -42035,27 +40622,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/23-022r1.pdf" + "@id": "https://portal.ogc.org/files/15-112r3" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-022r1" + "@value": "15-112r3" }, { "@language": "en", - "@value": "Establishing the Framework of Disaster Early Warning Mechanisms - A Case Study of Slope Disaster" + "@value": "Volume 3: OGC CDB Terms and Definitions" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The impact of global climate change has led to a rise in the frequency of natural\r\ndisasters in numerous countries resulting in substantial losses in terms of both human lives and the global economy. The establishment of a robust disaster early-warning mechanism is recommended that will empower communities to proactively engage in disaster reduction and prevention measures before such calamities occur, thereby effectively reducing losses.\r\nThe Common Alerting Protocol (CAP) is an internationally recognized digital\r\nmessage format and protocol for all types of alarms and early warning notifications. It was officially adopted by The Federal Emergency Management Agency (FEMA) in 2010 for its Integrated Public Alert and Warning System (IPAWS). It has also been successfully implemented in Taiwan for many years. However, different countries may employ other color-coded warning systems to indicate varying degrees of disaster severity. This disparity in warning standards can cause public confusion during emergencies, leading to increased costs in disaster management. This paper proposes a framework that utilizes red and yellow warning lights for issuing alerts. Adopting a standardized approach will mitigate confusion and enhance the efficiency of disaster response and management.\r\nThis study proposes a framework that uses red and yellow warning mechanisms for\r\nissuing alerts such as the disaster early warning for debris flows and large-scale\r\nlandslides established by the Soil and Water Conservation Bureau (SWCB). This\r\ninvestigation will explore the feasibility of standardizing yellow and red warning\r\npublishing rules." + "@value": "This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -42066,112 +40653,104 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-022r1" + "@value": "15-112r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Establishing the Framework of Disaster Early Warning Mechanisms - A Case Study of Slope Disaster" + "@value": "Volume 3: OGC CDB Terms and Definitions" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/isc", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/14-065r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-122r2" - }, - { - "@id": "http://www.opengis.net/def/docs/08-050" - }, - { - "@id": "http://www.opengis.net/def/docs/11-157" - }, - { - "@id": "http://www.opengis.net/def/docs/18-075" - }, - { - "@id": "http://www.opengis.net/def/docs/09-083r4" - }, - { - "@id": "http://www.opengis.net/def/docs/07-045r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-027r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-026r2" - }, - { - "@id": "http://www.opengis.net/def/docs/14-005r5" - }, - { - "@id": "http://www.opengis.net/def/docs/07-036r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-128r12a" - }, - { - "@id": "http://www.opengis.net/def/docs/18-010r11" - }, + "@id": "http://www.opengis.net/def/docs/12-028r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/09-146r8" - }, + "@type": "xsd:date", + "@value": "2016-03-24" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/14-065r2" - }, + "@value": "OGC Aviation Domain Working Group" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/12-128r15" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/09-147r3" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/07-010" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=62061" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/11-158" + "@language": "en", + "@value": "12-028r1" }, { - "@id": "http://www.opengis.net/def/docs/14-005r4" - }, + "@language": "en", + "@value": "Use of Geography Markup Language (GML) for Aviation Data" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/07-045r1" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/08-091r6" - }, + "@value": "The document provides guidelines for the use of GML and a GML profile description in the\r\nscope of aeronautical data encoding, in particular when using the Aeronautical Information\r\nExchange Model (AIXM). In the future, the applicability of the guidelines contained in this\r\ndocument might be enlarged to cover other related domains, such as aeronautical weather data\r\nand flight data." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/16-083r3" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/04-094r1" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "12-028r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@language": "en", + "@value": "Use of Geography Markup Language (GML) for Aviation Data" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-128r12a", + "@id": "http://www.opengis.net/def/docs/14-037", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-04-20" + "@value": "2014-07-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Daisey" + "@value": "Thomas Forbes, Ballal Joglekar" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -42181,27 +40760,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://www.geopackage.org/spec" + "@id": "https://portal.ogc.org/files/?artifact_id=58956" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-128r12a" + "@value": "Testbed 10 Flight Information Exchange Model GML Schema" }, { "@language": "en", - "@value": "GeoPackage Encoding Standard - With Corrigendum" + "@value": "14-037" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a “native” storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." + "@value": "This report provides guidance for implementing the Flight Information Exchange Model (FIXM) using the same best practice as the Aeronautical Information Exchange Model (AIXM) and the Weather Information Exchange Model (WXXM) by adopting ISO and OGC standards.\r\nThe report is aimed at system and client developers that shall use the FIXM data encoding for the exchange of flight information.\r\nThis document is a deliverable for the OGC Testbed 10 (Testbed-10) testbed activity. OWS testbeds are part of OGC's Interoperability Program, a global, hands-on and collaborative prototyping program designed to rapidly develop, test and deliver proven candidate standards or revisions to existing standards into OGC's Standards Program, where they are formalized for public release. In OGC's Interoperability Initiatives, international teams of technology providers work together to solve specific geoprocessing interoperability problems posed by the Initiative's sponsoring organizations. OGC Interoperability Initiatives include testbeds, pilot projects, interoperability experiments and interoperability support services - all designed to encourage rapid development, testing, validation and adoption of OGC standards.\r\nThe Testbed-10 sponsors are organizations seeking open standard for their interoperability requirements. After analyzing their requirements, the OGC Interoperability Team recommends to the sponsors that the content of the Testbed-10 initiative be organized around the following threads:\r\n•\tCross-Community Interoperability (CCI)\r\n•\tOpen Mobility\r\n•\tAviation\r\nMore information about the Testbed-10 tested can be found at:\r\nhttp://www.opengeospatial.org/standards/requests/103\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -42212,30 +40791,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-128r12a" + "@value": "14-037" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GeoPackage Encoding Standard - With Corrigendum" + "@value": "OGC® Testbed 10 Flight Information Exchange Model GML Schema" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-094", + "@id": "http://www.opengis.net/def/docs/16-024r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-10-22" + "@value": "2017-06-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Arctur" + "@value": "R. Martell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -42250,17 +40829,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40840" + "@id": "https://docs.ogc.org/per/16-024r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-7: Summary of the OGC Web Services, Phase 7 (OWS-7) Interoperability Testbed" + "@value": "16-024r2" }, { "@language": "en", - "@value": "10-094" + "@value": "Testbed-12 — Catalog Services for Aviation" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -42270,7 +40849,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Web Services, Phase 7 (OWS-7) Testbed was an initiative of OGC’s Interoperability Program to collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. " + "@value": "This Engineering Report (ER) presents guidance concerning the use of OGC® catalog services in the aviation domain. A wide variety of metadata resources can be readily published and discovered using the OGC CSW-ebRIM application profile, which marries the CSW catalog interface to the OASIS ebXML registry information model (ebRIM). However, existing SWIM registries currently under development by the FAA and Eurocontrol do not implement any OGC standards. This report explores the prospects for enhancing SWIM registries by a) integrating OGC catalog functionality, and b) accommodating OGC service descriptions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -42281,298 +40860,114 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-094" + "@value": "16-024r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-7: Summary of the OGC Web Services, Phase 7 (OWS-7) Interoperability Testbed" + "@value": "Testbed-12 — Catalog Services for Aviation" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/bp", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/21-068" - }, - { - "@id": "http://www.opengis.net/def/docs/13-015" - }, - { - "@id": "http://www.opengis.net/def/docs/14-110r2" - }, - { - "@id": "http://www.opengis.net/def/docs/14-106" - }, - { - "@id": "http://www.opengis.net/def/docs/06-142r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-107r3" - }, - { - "@id": "http://www.opengis.net/def/docs/06-126r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-018r2" - }, - { - "@id": "http://www.opengis.net/def/docs/05-035r2" - }, - { - "@id": "http://www.opengis.net/def/docs/08-167r2" - }, - { - "@id": "http://www.opengis.net/def/docs/16-070r2" - }, - { - "@id": "http://www.opengis.net/def/docs/12-032r2" - }, - { - "@id": "http://www.opengis.net/def/docs/15-120r5" - }, - { - "@id": "http://www.opengis.net/def/docs/16-070r4" - }, - { - "@id": "http://www.opengis.net/def/docs/12-111r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-011r5" - }, - { - "@id": "http://www.opengis.net/def/docs/17-011r2" - }, - { - "@id": "http://www.opengis.net/def/docs/16-004r5" - }, - { - "@id": "http://www.opengis.net/def/docs/16-003r4" - }, - { - "@id": "http://www.opengis.net/def/docs/09-102r3a" - }, - { - "@id": "http://www.opengis.net/def/docs/08-139r3" - }, - { - "@id": "http://www.opengis.net/def/docs/11-122r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-006r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-005r2" - }, - { - "@id": "http://www.opengis.net/def/docs/21-007" - }, - { - "@id": "http://www.opengis.net/def/docs/03-002r9" - }, - { - "@id": "http://www.opengis.net/def/docs/20-095" - }, - { - "@id": "http://www.opengis.net/def/docs/13-039" - }, - { - "@id": "http://www.opengis.net/def/docs/16-003r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-188r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-120r6" - }, - { - "@id": "http://www.opengis.net/def/docs/21-070" - }, - { - "@id": "http://www.opengis.net/def/docs/16-086r3" - }, - { - "@id": "http://www.opengis.net/def/docs/14-012r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-010r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-006r4" - }, - { - "@id": "http://www.opengis.net/def/docs/16-011r4" - }, - { - "@id": "http://www.opengis.net/def/docs/10-189r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-118r9" - }, - { - "@id": "http://www.opengis.net/def/docs/16-140r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-003r3" - }, - { - "@id": "http://www.opengis.net/def/docs/08-125r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-011r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-005r4" - }, - { - "@id": "http://www.opengis.net/def/docs/14-004r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-028r3" - }, - { - "@id": "http://www.opengis.net/def/docs/15-120r4" - }, - { - "@id": "http://www.opengis.net/def/docs/15-004" - }, - { - "@id": "http://www.opengis.net/def/docs/16-006r5" - }, - { - "@id": "http://www.opengis.net/def/docs/11-135r2" - }, - { - "@id": "http://www.opengis.net/def/docs/09-102" - }, - { - "@id": "http://www.opengis.net/def/docs/16-009r4" - }, - { - "@id": "http://www.opengis.net/def/docs/10-003r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-118r8" - }, - { - "@id": "http://www.opengis.net/def/docs/15-107" - }, - { - "@id": "http://www.opengis.net/def/docs/09-102r3" - }, - { - "@id": "http://www.opengis.net/def/docs/06-021r4" - }, - { - "@id": "http://www.opengis.net/def/docs/06-095" - }, - { - "@id": "http://www.opengis.net/def/docs/02-007r4" - }, - { - "@id": "http://www.opengis.net/def/docs/07-097" - }, - { - "@id": "http://www.opengis.net/def/docs/15-003" - }, - { - "@id": "http://www.opengis.net/def/docs/16-009r3" - }, - { - "@id": "http://www.opengis.net/def/docs/15-005r2" - }, - { - "@id": "http://www.opengis.net/def/docs/10-028r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-153r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-005r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-009r5" - }, - { - "@id": "http://www.opengis.net/def/docs/16-114r3" - }, - { - "@id": "http://www.opengis.net/def/docs/17-084r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-004r3" - }, + "@id": "http://www.opengis.net/def/doc-type/profile/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ { - "@id": "http://www.opengis.net/def/docs/05-042r2" - }, + "@value": "Documents of type Approved Specification Profile" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/07-063r1" - }, + "@value": "Documents of type Approved Specification Profile" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/16-010r5" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ { - "@id": "http://www.opengis.net/def/docs/13-042" + "@id": "http://www.opengis.net/def/docs/10-100r3" }, { - "@id": "http://www.opengis.net/def/docs/16-070r3" + "@id": "http://www.opengis.net/def/docs/13-082r2" }, { - "@id": "http://www.opengis.net/def/docs/13-043" + "@id": "http://www.opengis.net/def/docs/05-095r1" }, { - "@id": "http://www.opengis.net/def/docs/11-035r1" + "@id": "http://www.opengis.net/def/docs/05-094r1" }, { - "@id": "http://www.opengis.net/def/docs/20-089r1" + "@id": "http://www.opengis.net/def/docs/10-140r1" }, { - "@id": "http://www.opengis.net/def/docs/16-010r4" + "@id": "http://www.opengis.net/def/docs/05-096r1" }, { - "@id": "http://www.opengis.net/def/docs/15-005r1" - }, + "@id": "http://www.opengis.net/def/docs/05-099r2" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/15-037" - }, + "@value": "Documents of type Approved Specification Profile" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/14-008", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/12-066" - }, + "@type": "xsd:date", + "@value": "2014-07-15" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/07-092r3" - }, + "@value": "Matthes Rieke" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/14-003" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/11-169r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/06-129r1" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=58927" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/19-066" + "@language": "en", + "@value": "Testbed 10 Report on Aviation Architecture" }, { - "@id": "http://www.opengis.net/def/docs/16-004r4" + "@language": "en", + "@value": "14-008" } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-sap/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@value": "Documents of type Specification Application Profile - deprecated" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Documents of type Specification Application Profile - deprecated" + "@value": "This document is a deliverable of the OGC Testbed 10 (Testbed-10). This document describes the\r\narchitecture that was implemented in the Testbed-10 Aviation thread. Additionally, it provides\r\ndescriptions of all software components involved in the Aviation architecture as well as a\r\ndedicated chapter focusing on the evaluation and design of FIXM 2.0. Here, a special focus lies\r\non the integration into the data provisioning components, namely the Web Feature and Event\r\nServices." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -42580,39 +40975,38 @@ "@id": "http://www.opengis.net/def/docs" } ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/02-058" - }, + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/09-146r1" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "14-008" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type Specification Application Profile - deprecated" + "@language": "en", + "@value": "OGC® Testbed 10 Report on Aviation Architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-089r1", + "@id": "http://www.opengis.net/def/docs/09-048r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-12-14" + "@value": "2019-10-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Pedro Gonçalves" + "@value": "Simon Cox, Gobe Hobona" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/pol-nts" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -42622,27 +41016,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/20-089r1.html" + "@id": "https://docs.ogc.org/pol/09-048r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Best Practice for Earth Observation Application Package" + "@value": "Name Type Specification - definitions - part 1 – basic name" }, { "@language": "en", - "@value": "20-089r1" + "@value": "09-048r5" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/pol-nts" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Platforms for the exploitation of Earth Observation (EO) data have been developed by public and private companies in order to foster the usage of EO data and expand the market of Earth Observation-derived information. A fundamental principle of the platform operations concept is to move the EO data processing service’s user to the data and tools, as opposed to downloading, replicating, and exploiting data ‘at home’. In this scope, previous OGC activities initiated the development of an architecture to allow the ad-hoc deployment and execution of applications close to the physical location of the source data with the goal to minimize data transfer between data repositories and application processes.\r\n\r\nThis document defines the Best Practice to package and deploy Earth Observation Applications in an Exploitation Platform. The document is targeting the implementation, packaging and deployment of EO Applications in support of collaborative work processes between developers and platform owners.\r\n\r\nThe Best Practice includes recommendations for the application design patterns, package encoding, container and data interfaces for data stage-in and stage-out strategies focusing on three main viewpoints: Application, Package and Platform." + "@value": "This document specifies a rule for constructing OGC names that may be used for identifying definitions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -42653,30 +41047,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-089r1" + "@value": "09-048r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Best Practice for Earth Observation Application Package" + "@value": "OGC Name Type Specification - definitions - part 1 – basic name" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-030r1", + "@id": "http://www.opengis.net/def/docs/15-068r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-08-20" + "@value": "2015-08-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Gobe Hobona;Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -42691,17 +41085,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-030r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=64189" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-030r1" + "@value": "Testbed 11 GeoPackaging Engineering Report" }, { "@language": "en", - "@value": "Mixed Reality to the Edge Concept Development Study" + "@value": "15-068r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -42711,7 +41105,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Mixed Reality (MR), also referred to as hybrid reality, is the merging of real and virtual worlds to produce new environments and visualizations where physical and digital objects co-exist and interact in real time. MR has great potential in enhancing situation awareness and otherwise augmenting the experiences and performance of humans on the go.\r\n\r\nThis OGC Engineering Report summarizes information and findings collected during the Mixed Reality at the Edge Concept Development Study (CDS). Specifically, this report presents the significant findings concerning the state-of-the-art and potential of employing MR in modern systems, with a focus on discussing the state of needed interoperability and standards.\r\n\r\nThe term mixed reality was originally introduced in a 1994 paper by Paul Milgram and Fumio Kishino, A Taxonomy of Mixed Reality Visual Displays. What is mixed reality?." + "@value": "Mobile location based service applications and users have an increasing need for access to geospatial data from any place in the world, including locations with limited or intermittent connectivity to communications networks. Maintaining consistency between copies of the same data held by different mobile devices can be a significant challenge when connectivity is limited or intermittent. This OGC Engineering Report describes the work carried out in OGC Testbed-11 in relation to the creation and synchronization of SQLite databases that conform to the OGC GeoPackage standard . This Engineering Report describes an approach for the use of various standards to achieve such synchronization. The document also presents the results and lessons learnt from the experimentation conducted in the Testbed." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -42722,35 +41116,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-030r1" + "@value": "15-068r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Mixed Reality to the Edge Concept Development Study" + "@value": "OGC® Testbed 11 GeoPackaging Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-039", + "@id": "http://www.opengis.net/def/docs/15-066r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-26" + "@value": "2015-10-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann, Jinsongdi Yu" + "@value": "Gobe Hobona;Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -42760,27 +41154,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=54504" + "@id": "https://portal.ogc.org/files/?artifact_id=64173" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Service Interface Standard - Scaling Extension" + "@value": "Use of Semantic Linked Data with RDF for National Map NHD and Gazetteer Data Engineering Report " }, { "@language": "en", - "@value": "12-039" + "@value": "15-066r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request which allow scaling of a coverage during its server-side processing in a GetCoverage request." + "@value": "Over the past few years there has been an increase in the number, size and complexity of databases across government sectors. This has undoubtedly created challenges relating to the discovery and access of information and services on multiple databases across static and deployed networks. Linked Data has been suggested as a method able to tackle those challenges. The aim of the Hydrographic Linked Data activity in the OGC Testbed 11 was to advance the use of Linked Data for hydrographic data by building on the achievements of the previous testbeds and to improve the understanding of how to better build relations between hydro features and non-hydro features (e.g., stream gauge measurement/location vs bridge or other built features upstream or downstream). This aspect of the testbed focused on the National Hydrography Dataset (NHD) which is published by the United States Geological Survey (USGS). This OGC Engineering Report provides guidelines on the publication of hydrographic and hydrological data serialized as Resource Description Framework (RDF) using Linked Data principles and technologies based on OGC standards. The document also presents the experimentation conducted by Testbed 11 in order to identify those guidelines." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -42791,111 +41185,98 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-039" + "@value": "15-066r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Coverage Service Interface Standard - Scaling Extension" + "@value": "OGC® Testbed 11 Use of Semantic Linked Data with RDF for National Map NHD and Gazetteer Data Engineering Report " } ] }, { - "@id": "http://www.opengis.net/def/doc-type/pol/collection", + "@id": "http://www.opengis.net/def/docs/16-106r2", "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" + "http://www.w3.org/2004/02/skos/core#Concept" ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "http://purl.org/dc/terms/created": [ { - "@value": "Documents of type Policy Document" + "@type": "xsd:date", + "@value": "2017-08-16" } ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "http://purl.org/dc/terms/creator": [ { - "@value": "Documents of type Policy Document" + "@value": "Hans-Christoph Gruler" } ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs" + "@id": "http://www.opengis.net/def/doc-type/is" } ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/09-046r5" - }, - { - "@id": "http://www.opengis.net/def/docs/08-134r11" - }, - { - "@id": "http://www.opengis.net/def/docs/09-046r6" - }, - { - "@id": "http://www.opengis.net/def/docs/05-020r29" - }, - { - "@id": "http://www.opengis.net/def/docs/09-144r2" - }, + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/08-131r3" + "@id": "http://www.opengis.net/def/status/valid" } ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@value": "Documents of type Policy Document" + "@id": "https://portal.ogc.org/files/?artifact_id=75123" } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/22-041", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" ], - "http://purl.org/dc/terms/created": [ + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@type": "xsd:date", - "@value": "2023-08-16" + "@language": "en", + "@value": "InfraGML 1.0: Part 6 – LandInfra Survey - Encoding Standard" + }, + { + "@language": "en", + "@value": "16-106r2" } ], - "http://purl.org/dc/terms/creator": [ + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@value": "Leigh St. Hilaire, Aidan Brookson" + "@id": "http://www.opengis.net/def/doc-type/is" } ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 6 addresses the Survey, Equipment, Observations and Survey Results Requirements Classes from LandInfra." } ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/status/valid" + "@id": "http://www.opengis.net/def/docs" } ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "https://docs.ogc.org/per/22-041.html" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "16-106r2" } ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ - { - "@language": "en", - "@value": "Testbed-18: Building Energy Data Interoperability Engineering Report" - }, + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "22-041" + "@value": "OGC InfraGML 1.0: Part 6 – LandInfra Survey - Encoding Standard" } + ] + }, + { + "@id": "http://www.opengis.net/def/doc-type/ts/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "http://www.w3.org/2000/01/rdf-schema#label": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@value": "Documents of type test suite" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed-18 Engineering Report (ER) represents deliverable D012 and D013 for the Building Energy Data Interoperability task." + "@value": "Documents of type test suite" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -42903,38 +41284,65 @@ "@id": "http://www.opengis.net/def/docs" } ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "http://www.w3.org/2004/02/skos/core#member": [ { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-041" + "@id": "http://www.opengis.net/def/docs/07-134r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-053r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-103r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-069r2" + }, + { + "@id": "http://www.opengis.net/def/docs/14-014r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@language": "en", - "@value": "Testbed-18: Building Energy Data Interoperability Engineering Report" + "@value": "Documents of type test suite" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-169", + "@id": "http://www.opengis.net/def/doc-type/sap", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/09-146r2" + }, + { + "@id": "http://www.opengis.net/def/docs/06-080r4" + }, + { + "@id": "http://www.opengis.net/def/docs/01-009a" + }, + { + "@id": "http://www.opengis.net/def/docs/07-045" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/16-060r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-12-19" + "@value": "2018-11-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Jirka, Christoph Stasch, Arne Bröring" + "@value": "Daniel Lee" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -42944,27 +41352,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46693" + "@id": "https://docs.ogc.org/is/16-060r2/16-060r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Lightweight SOS Profile for Stationary In-Situ Sensors Discussion Paper" + "@value": "GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile" }, { "@language": "en", - "@value": "11-169" + "@value": "16-060r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion Paper describes a lightweight SOS 2.0 profile for stationary in-situ sensors. Besides the SOS itself this document also addresses the data formats used by the SOS: Observations & Measurements 2.0 (O&M) for encoding measurement data and the Sensor Model Language 2.0 (SensorML) for encoding metadata. Other SWE standards which provide more specialized functionality are not part of this minimum lightweight SWE profile.\r\nThe aim of this document is to present a common minimum profile of the SOS. The profile is intended to reduce the complexity of the standard by omitting highly specific elements that are not necessary for the majority of use cases that occur in practice. At the same time, the profile is designed in such a way that all SOS implementations that conform to this profile are also compliant to the according OGC specifications." + "@value": "This OGC standard is a profile of the OGC GML Application Schema - Coverages version 1.0 [OC 09-146r2]. That document was renamed OGC Coverage Implementation Schema (CIS) for clarification in version 1.1. This standard specifies the usage of the GRIB2 data format for the encoding of OGC coverages. The GRIB2 specification is maintained by the World Meteorological Organization (WMO) and is the standard encoding for the exchange and storage of general regularly distributed information expressed in binary form." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -42975,35 +41383,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-169" + "@value": "16-060r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Lightweight SOS Profile for Stationary In-Situ Sensors Discussion Paper" + "@value": "OGC GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-015r2", + "@id": "http://www.opengis.net/def/docs/16-010r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-04-27" + "@value": "2017-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Lott" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -43013,27 +41421,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39049" + "@id": "https://portal.ogc.org/files/?artifact_id=72718" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 2 - Spatial referencing by coordinates" + "@value": "16-010r3" }, { "@language": "en", - "@value": "08-015r2" + "@value": "Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is consistent with the second edition (2007) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2007]" + "@value": "This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store.\r\nPlease note that the term “lineal” has been replaced with the term “line” or “linear” throughout this document\r\nPlease note that the term “areal” has been replaced with the term “polygon” throughout this document.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43044,35 +41452,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-015r2" + "@value": "16-010r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 2 - Spatial referencing by coordinates" + "@value": "Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-074", + "@id": "http://www.opengis.net/def/docs/15-108r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-05-06" + "@value": "2021-03-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Samantha Lavender, Andrew Lavender" + "@value": "Peter Trevelyan, Paul Hershberg, Steve Olson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/ug" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -43082,27 +41490,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/guides/21-074.html" + "@id": "https://docs.ogc.org/is/15-108r3/15-108r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Disaster Pilot: User Readiness Guide" + "@value": "15-108r3" }, { "@language": "en", - "@value": "21-074" + "@value": "MetOcean Application profile for WCS2.1: Part 1 MetOcean GetCorridor Extension" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/ug" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Disaster Pilot 2021 initiative brought differing technologies together through multiple participants, allowing the future development of a robust solution with no single-point weaknesses. This Guide supports data providers in preparing and coordinating with others to leverage standards-based cloud computing platforms to support disaster management and response efforts. Geospatial data is acquired from multiple sources, including Earth Observation satellites, and converted to Decision Ready Information and indicators (DRI) from Analysis Ready Data and datasets (ARD) alongside recipes." + "@value": "The purpose of the GetCorridor operation is to extract a corridor based on a trajectory from a multidimensional coverage. The need for the getCorridor operation stems from active members of the OGC MetOcean Domain Working Group (DWG) who saw a manifest need for extraction of such information from gridded datasets. This work has been done by members of the OGC MetOcean Domain Working Group." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43113,35 +41521,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-074" + "@value": "15-108r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Disaster Pilot: User Readiness Guide" + "@value": "OGC MetOcean Application profile for WCS2.1: Part 1 MetOcean GetCorridor Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-084r1", + "@id": "http://www.opengis.net/def/docs/15-097r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-08-20" + "@value": "2016-12-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jen Marcus" + "@value": "Joan Masó, Lucy Bastin " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -43151,27 +41559,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=29505" + "@id": "https://docs.ogc.org/is/15-097r1/15-097r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CITE Summary Engineering Report" + "@value": "Geospatial User Feedback Standard: Conceptual Model" }, { "@language": "en", - "@value": "08-084r1" + "@value": "15-097r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document summarizes work completed in the OWS5 Compliance & Interoperability Test & Evaluation thread. This document is applicable to the OGC Compliance Test Program." + "@value": "This standard defines a conceptual Geospatial User Feedback (GUF) data model. Geospatial User Feedback is metadata that is predominantly produced by the consumers of geospatial data products as they use and gain experience with those products. This standard complements existing metadata conventions whereby documents recording dataset characteristics and production workflows are generated by the creator, publisher or curator of a data product. As a part of metadata, the GUF data model reuses some elements of ISO 19115-1:2014 (the updated version of the OGC Abstract Specification Topic 11) but not the general structure. This selective use of ISO metadata elements prioritizes future interoperability with developing ISO metadata models. This standard is designed to be used combination with an encoding standard. Initially an XML encoding following the ISO 19139 encoding rules is specified in a separate OGC implementation standard (OGC 15-098). In the future other encodings may be defined, including examples such as the use of JSON-LD based on parts of schema.org." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43182,30 +41590,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-084r1" + "@value": "15-097r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-5 CITE Summary Engineering Report" + "@value": "OGC® Geospatial User Feedback Standard: Conceptual Model" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-100r1", + "@id": "http://www.opengis.net/def/docs/18-073r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-05-28" + "@value": "2019-08-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stephan Meissl" + "@value": "John Tisdale" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -43220,17 +41628,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=54813" + "@id": "https://docs.ogc.org/is/18-073r2/18-073r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile" + "@value": "18-073r2" }, { "@language": "en", - "@value": "12-100r1" + "@value": "OGC PipelineML Conceptual and Encoding Model Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -43240,7 +41648,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Interface Standard is a profile of the OGC® GML Application Schema –Coverages version 1.0 [OC 09-146r2]. This document specifies the usage of the GeoTIFF data format for the encoding of GML coverages. This encoding is used by several OGC services like the Web Coverage Service (WCS) 2.0 Interface Standard – Core [OGC 09-110r4]." + "@value": "The OGC PipelineML Conceptual and Encoding Model Standard defines concepts supporting the interoperable interchange of data pertaining to oil and gas pipeline systems. PipelineML supports the common exchange of oil and gas pipeline information. This initial release of the PipelineML Core addresses two critical business use cases that are specific to the pipeline industry: new construction surveys and pipeline rehabilitation. This standard defines the individual pipeline components with support for lightweight aggregation. Additional aggregation requirements such as right-of-way and land management will utilize the OGC LandInfra standards with utility extensions in the future. Future extensions to PipelineML Core will include (non-limitative): cathodic protection, facility and safety. PipelineML was advanced by an international team of contributors from the US, Canada, Belgium, Norway, Netherlands, UK, Germany, Australia, Brazil, and Korea.\r\n\r\nThis standard assumes the reader has a basic understanding of oil and gas pipeline industry concepts." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43251,30 +41659,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-100r1" + "@value": "18-073r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile" + "@value": "OGC PipelineML Conceptual and Encoding Model Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-040", + "@id": "http://www.opengis.net/def/docs/16-097", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-03-06" + "@value": "2017-10-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Blodgett, J. Michael Johnson" + "@value": "Mohsen Kalantari" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -43289,17 +41697,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-040.html" + "@id": "https://docs.ogc.org/per/16-097.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Hydrologic Modeling and River Corridor Applications of HY_Features Concepts" + "@value": "16-097" }, { "@language": "en", - "@value": "22-040" + "@value": "Future City Pilot 1: Using IFC/CityGML in Urban Planning Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -43309,7 +41717,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Hydrologic geospatial data products contain geometries that represent features such as river segments and incremental catchments. The combination of these provides a 2D (XY) geospatial fabric (hydrofabic) that discretizes the landscape and flow network into hydrologically relevant features at a defined level of scale, resolution, or organization. Hydrofabrics have been created at the national and continental scale in many parts of the world. This engineering report presents progress on formalizing a hydrofabric for drainage basins that adheres to HY_Features concepts with a focus on the use of the concepts in modeling hydrologic processes. Furthermore, this report documents efforts to integrate river corridor data with the traditionally 2D hydrofabric representations. River corridors include the channel and adjacent land required to maintain or restore a dynamic geomorphic equilibrium." + "@value": "Numerous and diverse technologies push cities towards open and platform-independent information infrastructures to manage human, natural, and physical systems. The Future Cities Pilot 1 (FCP1), as an OGC Innovation Program initiative, demonstrated how cities can benefit from open standards when used in urban planning workflows. This report details the lessons learned of implementing both the OGC CityGML and the buildingSMART Industry Foundation Classes (IFC) standards for visualizing and processing 3D spatial data when used in urban planning processes." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43320,35 +41728,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-040" + "@value": "16-097" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Hydrologic Modeling and River Corridor Applications of HY_Features Concepts" + "@value": "Future City Pilot 1: Using IFC/CityGML in Urban Planning Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-088r1", + "@id": "http://www.opengis.net/def/docs/07-010", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-11-23" + "@value": "2007-06-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff, Thomas Everding" + "@value": "Doug Nebert" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -43358,27 +41766,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=45850" + "@id": "https://portal.ogc.org/files/?artifact_id=20561" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Event Service - Review and Current State" + "@value": "Revision Notes for Corrigendum for OpenGIS 07-006: Catalogue Services, Version 2.0.2" }, { "@language": "en", - "@value": "11-088r1" + "@value": "07-010" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion Paper provides information on what has so far been called “Event Service” at OGC.\r\nThe presented work is supported by the European Commission through the ESS project (integrated project, contract number 217951) and the GENESIS project (integrated project, contract number 223996) .\r\n" + "@value": "This document is a corrigendum for OGC Document 04-021r3. All changes described herein are published in OGC Document 07-006r1." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43389,35 +41797,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-088r1" + "@value": "07-010" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Event Service - Review and Current State" + "@value": "Revision Notes for Corrigendum for OpenGIS 07-006: Catalogue Services, Version 2.0.2" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-008c1", + "@id": "http://www.opengis.net/def/docs/04-100", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-05-03" + "@value": "2005-04-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -43427,27 +41835,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8798" + "@id": "https://portal.ogc.org/files/?artifact_id=8071" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Service Common Implementation Specification" + "@value": "OWS-2 Application Schema Development" }, { "@language": "en", - "@value": "05-008c1" + "@value": "04-100" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies many of the aspects that are, or should be, common to all or multiple OWS interface Implementation Specifications. Those specifications currently include the Web Map Service (WMS), Web Feature Service (WFS), and Web Coverage Service (WCS). These common aspects include: operation request and response contents; parameters included in operation requests and responses; and encoding of operation requests and responses." + "@value": "The OWS-2 Application Schema Development Discussion Paper describes the process for creating ISO 19109:2005 Application Schemas [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=39891] in UML. It also describes the process used during the OWS-2 Initiative [http://www.opengeospatial.org/projects/initiatives/ows-2] for creating GML [http://www.opengeospatial.org/standards/gml] Application Schemas from ISO 19109:2005 Application Schemas.\r\n\r\nSee also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43458,35 +41866,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-008c1" + "@value": "04-100" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Service Common Implementation Specification" + "@value": "OWS-2 Application Schema Development" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-109r1", + "@id": "http://www.opengis.net/def/docs/18-094r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-05-09" + "@value": "2019-02-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos, Rento Primavera" + "@value": "Stephane Fellah" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -43496,27 +41904,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=14143" + "@id": "https://docs.ogc.org/per/18-094r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-109r1" + "@value": "18-094r1" }, { "@language": "en", - "@value": "Catalog 2.0 IPR for ebRIM" + "@value": "Characterization of RDF Application Profiles for Simple Linked Data Application and Complex Analytic Applications Engineering" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The purpose of this document is to show how to map the various types of metadata documents to be used in the OWS3 project into the ebRIM." + "@value": "This Engineering Report (ER) enhances the understanding of the concept of application profiles (AP) for ontologies based on the Web Ontology Language (OWL) and used by Linked Data (LD) applications. The concept of an Application Profile for Unified Modeling Language (UML) and Extensible Markup Language (XML) schemas, in particular Geographic Markup Language (GML) application profiles, is pretty well-defined and understood within the communities of Open Geospatial Consortium (OGC) and International Organization for Standardization (ISO). Moreover, in the context of Linked Data and ontologies, the term is still ill-defined, as ontologies are defined using an Open World Assumption (OWA), as well as classes and properties are first-class modeling objects in ontology modeling. The work documented in this report includes:\r\n\r\nDefinition and characterization of Resource Description Framework (RDF) application profiles for simple linked data applications and complex analytic linked data applications.\r\n\r\nDetermination of preliminary techniques for the development of subsets of ontologies to support different types of applications (simple linked data and complex analytic)\r\n\r\nAn initial model for defining metadata about application profiles, so they can be searched and discovered by agents." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43527,35 +41935,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-109r1" + "@value": "18-094r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Catalog 2.0 IPR for ebRIM" + "@value": "OGC Testbed-14: Characterization of RDF Application Profiles for Simple Linked Data Application and Complex Analytic Applicat" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-062", + "@id": "http://www.opengis.net/def/docs/19-079r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-14" + "@value": "2024-07-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gerhard Gr" + "@value": "Panagiotis (Peter) A. Vretanos, Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -43565,27 +41973,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=22120" + "@id": "https://docs.ogc.org/is/19-079r2/19-079r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-062" + "@value": "19-079r2" }, { "@language": "en", - "@value": "City Geography Markup Language" + "@value": "OGC API - Features - Part 3: Filtering" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "CityGML is designed as an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is implemented as an application schema of the Geography Markup Language 3 (GML3), the extendible international standard for spatial data exchange and encoding issued by the Open Geospatial Consortium (OGC) and the ISO TC211. " + "@value": "OGC API Standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks.\r\n\r\nOGC API - Features provides API building blocks to create, modify and query features on the Web. OGC API - Features is comprised of multiple parts. Each part is a separate standard.\r\n\r\nA fundamental operation performed on a collection of features is that of filtering in order to obtain a subset of the data which contains feature instances that satisfy some filtering criteria. Part three of the OGC API - Features Standard defines query parameters (filter, filter-lang, filter-crs) to specify filter criteria in a request to an API and the Queryables resource that declares the properties of data in a collection that can be used in filter expressions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43596,30 +42004,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-062" + "@value": "19-079r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "City Geography Markup Language" + "@value": "OGC API - Features - Part 3: Filtering" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-036", + "@id": "http://www.opengis.net/def/docs/11-110", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-04-07" + "@value": "2011-08-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lance McKee, Carl Reed, Steven Ramage" + "@value": "Arnulf Christl and Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -43634,17 +42042,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=43743" + "@id": "https://portal.ogc.org/files/?artifact_id=45126" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-036" + "@value": "Open Source and Open Standards" }, { "@language": "en", - "@value": "OGC Standards and Cloud Computing" + "@value": "11-110" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -43654,7 +42062,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC White Paper discusses cloud computing from the perspective of OGC’s\r\ngeospatial standards development activities and standards baseline. The paper begins\r\nwith a discussion of what the cloud and cloud computing are. Unfortunately, there is still\r\nconsiderable misunderstanding in the geospatial technology community regarding cloud\r\ncomputing. The paper then discusses how standards figure into the options, benefits and\r\nrisks of cloud computing for users and providers of geospatial data and software. This\r\nperspective is important not only for those immersed in geospatial technology, but also for\r\ncloud service providers, customers and technology partners who may be unfamiliar with\r\nthe basic issues surrounding geospatial technology. This white paper does not discuss\r\nvendor specific cloud computing platforms." + "@value": "This article is a White Paper jointly published by OGC and OSGeo. It was approved as an official joint OSGeo and OGC White Paper by the OSGeo Board of Directors in their 2011-05-05 Board meeting. \r\nThe text was collaboratively edited, reviewed and finalized by more than a a dozen active OSGeo and OGC members. Thanks especially to Gavin Fleming, Lance McKee, Markus Neteler, Athina Trakas, Michael Gerlek, Adrian Custer, Jeff McKenna, Cameron Shorter, Carl Reed, Frank Warmerdam, Steven Ramage, Daniel Morissette, Arnulf Christl and others for their contributions.\r\nPlease feel free to add comments, criticisms, links to other concise definitions on the associated Talk page: http://wiki.osgeo.org/wiki/Open_Source_and_Open_Standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43665,35 +42073,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-036" + "@value": "11-110" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Standards and Cloud Computing" + "@value": "Open Source and Open Standards" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-104r1", + "@id": "http://www.opengis.net/def/docs/12-039", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-01-20" + "@value": "2014-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arne Schilling, Thomas H. Kolbe" + "@value": "Peter Baumann, Jinsongdi Yu" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -43703,27 +42111,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=36390" + "@id": "https://portal.ogc.org/files/?artifact_id=54504" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Draft for Candidate OpenGIS® Web 3D Service Interface Standard" + "@value": "12-039" }, { "@language": "en", - "@value": "09-104r1" + "@value": "Web Coverage Service Interface Standard - Scaling Extension" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A Web 3D Service (W3DS) is a portrayal service for three-dimensional geodata, such as landscape models, city models, textured building models, vegetation objects, and street furniture. Geodata is delivered as scenes that are comprised of display elements, optimized for efficient real time rendering at high frame rates." + "@value": "This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request which allow scaling of a coverage during its server-side processing in a GetCoverage request." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43734,29 +42142,29 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-104r1" + "@value": "12-039" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Draft for Candidate OpenGIS® Web 3D Service Interface Standard" + "@value": "OGC® Web Coverage Service Interface Standard - Scaling Extension" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/d-as/collection", + "@id": "http://www.opengis.net/def/doc-type/isc/collection", "@type": [ "http://www.w3.org/2004/02/skos/core#Collection" ], "http://www.w3.org/2000/01/rdf-schema#label": [ { - "@value": "Documents of type Abstract Specification - deprecated " + "@value": "Documents of type OGC Implementation Specification Corrigendum" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Documents of type Abstract Specification - deprecated " + "@value": "Documents of type OGC Implementation Specification Corrigendum" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43766,82 +42174,103 @@ ], "http://www.w3.org/2004/02/skos/core#member": [ { - "@id": "http://www.opengis.net/def/docs/99-105r2" + "@id": "http://www.opengis.net/def/docs/04-094r1" }, { - "@id": "http://www.opengis.net/def/docs/99-100r1" + "@id": "http://www.opengis.net/def/docs/14-005r5" }, { - "@id": "http://www.opengis.net/def/docs/15-104r5" + "@id": "http://www.opengis.net/def/docs/07-122r2" }, { - "@id": "http://www.opengis.net/def/docs/10-020" + "@id": "http://www.opengis.net/def/docs/07-045r2" }, { - "@id": "http://www.opengis.net/def/docs/01-111" + "@id": "http://www.opengis.net/def/docs/07-045r1" }, { - "@id": "http://www.opengis.net/def/docs/04-084" + "@id": "http://www.opengis.net/def/docs/07-010" }, { - "@id": "http://www.opengis.net/def/docs/18-005r5" + "@id": "http://www.opengis.net/def/docs/18-010r11" }, { - "@id": "http://www.opengis.net/def/docs/02-102" + "@id": "http://www.opengis.net/def/docs/14-065r1" }, { - "@id": "http://www.opengis.net/def/docs/10-004r3" + "@id": "http://www.opengis.net/def/docs/09-147r3" }, { - "@id": "http://www.opengis.net/def/docs/08-015r2" + "@id": "http://www.opengis.net/def/docs/18-075" }, { - "@id": "http://www.opengis.net/def/docs/00-106" + "@id": "http://www.opengis.net/def/docs/08-050" }, { - "@id": "http://www.opengis.net/def/docs/01-101" + "@id": "http://www.opengis.net/def/docs/16-083r3" }, { - "@id": "http://www.opengis.net/def/docs/99-107" + "@id": "http://www.opengis.net/def/docs/12-128r12a" }, { - "@id": "http://www.opengis.net/def/docs/18-005r4" + "@id": "http://www.opengis.net/def/docs/09-083r4" }, { - "@id": "http://www.opengis.net/def/docs/03-073r1" + "@id": "http://www.opengis.net/def/docs/14-005r4" }, { - "@id": "http://www.opengis.net/def/docs/99-109r1" + "@id": "http://www.opengis.net/def/docs/06-027r1" }, { - "@id": "http://www.opengis.net/def/docs/04-046r3" + "@id": "http://www.opengis.net/def/docs/07-036r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-158" + }, + { + "@id": "http://www.opengis.net/def/docs/09-026r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r15" + }, + { + "@id": "http://www.opengis.net/def/docs/11-157" + }, + { + "@id": "http://www.opengis.net/def/docs/08-091r6" + }, + { + "@id": "http://www.opengis.net/def/docs/14-065r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-146r8" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type Abstract Specification - deprecated " + "@value": "Documents of type OGC Implementation Specification Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-083r2", + "@id": "http://www.opengis.net/def/docs/10-060r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-10-06" + "@value": "2010-08-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó" + "@value": "Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -43851,27 +42280,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/17-083r2/17-083r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=39509" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Two Dimensional Tile Matrix Set" + "@value": "OWS-7 Event Architecture Engineering Report" }, { "@language": "en", - "@value": "17-083r2" + "@value": "10-060r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Tile Matrix Set standard defines the rules and requirements for a tile matrix set as a way to index space based on a set of regular grids defining a domain (tile matrix) for a limited list of scales in a Coordinate Reference System (CRS) as defined in [OGC 08-015r2] Abstract Specification Topic 2: Spatial Referencing by Coordinates. Each tile matrix is divided into regular tiles. In a tile matrix set, a tile can be univocally identified by a tile column a tile row and a tile matrix identifier. This document presents a data structure defining the properties of the tile matrix set in both UML diagrams and in tabular form. This document also presents a data structure to define a subset of a tile matrix set called tile matrix set limits. XML and JSON encodings are suggested both for tile matrix sets and tile matrix set limits. Finally, the document offers practical examples of tile matrix sets both for common global projections and for specific regions." + "@value": "This document is applicable to use cases in which event-driven architecture principles are applied in Spatial Data Infrastructures.\r\n\r\nThe document specifies publish/subscribe functionality for OGC web services. This is done by first defining an abstract publish / subscribe model and then deriving functional requirements from this model." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43882,35 +42311,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-083r2" + "@value": "10-060r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Two Dimensional Tile Matrix Set" + "@value": "OWS-7 Event Architecture Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-004r3", + "@id": "http://www.opengis.net/def/docs/09-025r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-02-23" + "@value": "2010-11-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -43920,27 +42349,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=72716" + "@id": "https://portal.ogc.org/files/?artifact_id=39967" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-004r3" + "@value": "09-025r1" }, { "@language": "en", - "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models" + "@value": "Web Feature Service 2.0 Interface Standard (also ISO 19142)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "(RCS) data within a conformant CDB data store. \r\nPlease note that the current CDB standard only provides encoding rules for using Esri ShapeFiles for storing RCS models. However, this Best Practice has been modified to change most of the ShapeFile references to “vector data sets” or “vector attributes” and “Point Shapes” to “Point geometries”. This was done in recognition that future versions of the CDB standard and related Best Practices will provide guidance on using other encodings/formats, such as OGC GML.\r\n" + "@value": "This International Standard specifies the behaviour of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored parameterized query expressions.\r\nDiscovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers.\r\nQuery operations allow features or values of feature properties to be retrieved from the underlying data store based upon constraints, defined by the client, on feature properties.\r\nLocking operations allow exclusive access to features for the purpose of modifying or deleting features.\r\nTransaction operations allow features to be created, changed, replaced and deleted from the underlying data store.\r\nStored query operations allow clients to create, drop, list and described parameterized query expressions that are stored by the server and can be repeatedly invoked using different parameter values." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -43951,126 +42380,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-004r3" + "@value": "09-025r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/as/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type OGC Abstract Specification" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Documents of type OGC Abstract Specification" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/10-030" - }, - { - "@id": "http://www.opengis.net/def/docs/08-126" - }, - { - "@id": "http://www.opengis.net/def/docs/06-004r4" - }, - { - "@id": "http://www.opengis.net/def/docs/21-053r1" - }, - { - "@id": "http://www.opengis.net/def/docs/18-005r8" - }, - { - "@id": "http://www.opengis.net/def/docs/99-113" - }, - { - "@id": "http://www.opengis.net/def/docs/22-010r4" - }, - { - "@id": "http://www.opengis.net/def/docs/20-082r4" - }, - { - "@id": "http://www.opengis.net/def/docs/04-084r4" - }, - { - "@id": "http://www.opengis.net/def/docs/11-111r1" - }, - { - "@id": "http://www.opengis.net/def/docs/00-116" - }, - { - "@id": "http://www.opengis.net/def/docs/17-087r13" - }, - { - "@id": "http://www.opengis.net/def/docs/02-112" - }, - { - "@id": "http://www.opengis.net/def/docs/00-115" - }, - { - "@id": "http://www.opengis.net/def/docs/04-107" - }, - { - "@id": "http://www.opengis.net/def/docs/20-040r3" - }, - { - "@id": "http://www.opengis.net/def/docs/19-014r3" - }, - { - "@id": "http://www.opengis.net/def/docs/99-110" - }, - { - "@id": "http://www.opengis.net/def/docs/21-060r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-011" - }, - { - "@id": "http://www.opengis.net/def/docs/99-108r2" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Documents of type OGC Abstract Specification" + "@value": "OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142)" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-131r6", + "@id": "http://www.opengis.net/def/docs/06-126r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-02-10" + "@value": "2009-07-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Frédéric Houbie, Lorenzo Bigagli" + "@value": "Chuck Morris" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -44080,27 +42418,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=35528" + "@id": "https://portal.ogc.org/files/?artifact_id=33085" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-131r6" + "@value": "06-126r2" }, { "@language": "en", - "@value": "Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products" + "@value": "Compliance Test Language (CTL) Best Practice" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the mapping of Earth Observation Products – defined in the OGC® GML 3.1.1 Application schema for Earth Observation products [OGC 06-080r4] (version 0.9.3) – to an ebRIM structure within an OGC® Catalogue 2.0.2 (Corrigendum 2 Release) [OGC 07-006r1] implementing the CSW-ebRIM Registry Service – part 1: ebRIM profile of CSW [OGC 07-110r4]. This standard defines the way Earth Observation products metadata resources are organized and implemented in the Catalogue for discovery, retrieval and management." + "@value": "This document establishes Compliance Test Language, an XML grammar for documenting and scripting suites of tests for verifying that an implementation of a specification complies with the specification." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -44111,35 +42449,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-131r6" + "@value": "06-126r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products" + "@value": "Compliance Test Language (CTL) Best Practice" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-032r8", + "@id": "http://www.opengis.net/def/docs/19-091r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-04-14" + "@value": "2021-02-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Pedro Gonçalves" + "@value": "Thomas Gilbert, Carsten Rönsdorf, Jim Plume, Scott Simmons, Nick Nisbet, Hans-Christoph Gruler, Thom" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -44149,27 +42487,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=56866" + "@id": "https://portal.ogc.org/files/?artifact_id=96354" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OpenSearch Geo and Time Extensions" + "@value": "19-091r2" }, { "@language": "en", - "@value": "10-032r8" + "@value": "Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "

This OGC standard specifies the Geo and Time extensions to the OpenSearch query protocol. OpenSearch is a collection of simple formats for the sharing of search results.

\r\n

The OpenSearch description document format can be used to describe a search engine so that it can be used by search client applications. The OpenSearch description format allows the use of extensions that allow search engines to request a specific and contextual query parameter from search clients.

\r\n

The OpenSearch response elements can be used to extend existing syndication formats, such as RSS and Atom, with the extra metadata needed to return search results.\r\nServices that support the OpenSearch Specification, the Geo and Time extensions defined in this document are called OpenSearch GeoTemporal Services.

\r\n" + "@value": "Demand for digital representations of built environments is accelerating and can only be satisfied through greater software interoperability and data integration. The objective of the Integrated Digital Built Environment (IDBE) joint working group is to address this challenge by bringing together experts from the Open Geospatial Consortium and buildingSMART to coordinate the development of the relevant data standards. This document is an output from IDBE in which we describe the state of three of the most prominent built environment standards – CityGML, IFC and LandInfra – and describe some of the problems that hinder their integration; finally, we propose actions points for overcoming these problems." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -44180,35 +42518,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-032r8" + "@value": "19-091r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OpenSearch Geo and Time Extensions" + "@value": "Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-036", + "@id": "http://www.opengis.net/def/docs/16-009r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-03-15" + "@value": "2018-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Rob Atkinson" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -44218,27 +42556,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1041" + "@id": "https://portal.ogc.org/files/16-009r4" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Gazetteer" + "@value": "Volume 6: OGC CDB Rules for Encoding Data using OpenFlight" }, { "@language": "en", - "@value": "01-036" + "@value": "16-009r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "An authority for place names. Returns their associated geometries" + "@value": "This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of that document for a general overview." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -44249,35 +42587,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-036" + "@value": "16-009r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Gazetteer" + "@value": "Volume 6: OGC CDB Rules for Encoding Data using OpenFlight" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-062", + "@id": "http://www.opengis.net/def/docs/02-087r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-15" + "@value": "2002-12-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Roger Brackin" + "@value": "Doug Nebert" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -44287,27 +42625,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-062.html" + "@id": "https://portal.ogc.org/files/?artifact_id=3843" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-062" + "@value": "02-087r3" }, { "@language": "en", - "@value": "Testbed-12 Catalogue and SPARQL Engineering Report" + "@value": "Catalog Interface" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report has been produced by the OGC® Testbed-12 initiative.\r\nThe engineering report evaluates interoperability between a variety of\r\ncatalogues. The report presents a comparison of the catalogues, with the same\r\ndatasets uploaded. The catalogues discussed in the report include services\r\nconforming to Catalogue Service for Web (CSW) version 2.0.2 and 3.0, including\r\nservices based on the ebRIM profile of CSW 2.0.2 and an extension of CSW 3.0\r\nwith OpenSearch and SOAP. The engineering report presents results from tests\r\nusing a multi-catalogue client to interact with each service. The engineering\r\nreport also provides a comparison of CSW and services based on the Data\r\nCatalogue (DCAT) specification covering functionality, expressiveness and\r\nusability of CSW and DCAT. The comparison is supported by a discussion on the\r\nimplementation of a SPARQL / GeoSPARQL service." + "@value": "Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -44318,35 +42656,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-062" + "@value": "02-087r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Catalogue and SPARQL Engineering Report" + "@value": "Catalog Interface" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-083", + "@id": "http://www.opengis.net/def/docs/07-001r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-02-13" + "@value": "2007-05-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -44356,27 +42694,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-083.html" + "@id": "https://portal.ogc.org/files/?artifact_id=21352" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-083" + "@value": "07-001r3" }, { "@language": "en", - "@value": "Citizen Science Interoperability Experiment Engineering Report" + "@value": "Requirements for some specific simple solid, plane and line geometry types" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering report describes the first phase of the Citizen Science (CS) Interoperability Experiment (IE) organized by the EU H2020 WeObserve project under the OGC Innovation Program and supported by the four H2020 Citizen Observatories projects (SCENT, GROW, LandSense, and GroundTruth 2.0) as well as the EU H2020 NEXTGEOSS project. The activity covered aspects of data sharing architectures for Citizen Science data, data quality, data definitions and user authentication.\r\n\r\nThe final aim was to propose solutions on how Citizen Science data could be integrated in the Global Earth Observation System of Systems (GEOSS). The solution is necessarily a combination of technical and networking components, being the first ones the focus of this work. The applications of international geospatial standards in current Citizen Science and citizen observatory projects to improve interoperability and foster innovation is one of the main tasks in the IE.\r\n\r\nThe main result of the activity was to demonstrate that Sensor Observing Services can be used for Citizen Science data (as proposed in the Open Geospatial Consortium (OGC) Sensor Web Enablement for Citizen Science (SWE4CS) Discussion Paper) by implementing SWE4CS in several clients and servers that have been combined to show Citizen Science observations. In addition, an authentication server was used to create a federation between three projects. This federated approach is part of the proposed solution for GEOSS that can be found in the last chapter. Many open issues have been identified and are expected to be addressed in the second phase of the experiment, including the use of a definitions server." + "@value": "This specification describes requirements for specific geometry types, including some simple solids, and planes and lines defined using an implicit parameterization." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -44387,30 +42725,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-083" + "@value": "07-001r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Citizen Science Interoperability Experiment Engineering Report" + "@value": "Requirements for some specific simple solid, plane and line geometry types" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-063", + "@id": "http://www.opengis.net/def/docs/20-027", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-03-08" + "@value": "2021-01-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stefano Cavazzi, Roger Brackin" + "@value": "Craig A. Lee" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -44425,17 +42763,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-063.html" + "@id": "https://docs.ogc.org/per/20-027.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Arctic Spatial Data Infrastructure Engineering Report" + "@value": "OGC Testbed-16: Federated Security" }, { "@language": "en", - "@value": "16-063" + "@value": "20-027" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -44445,7 +42783,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report captures use cases representative of the vision of the Arctic Spatial Data Infrastructure (ArcticSDI). The ArcticSDI is a cooperative initiative established between the eight National Mapping Agencies of Canada, Finland, Iceland, Norway, Russia, Sweden, USA and Denmark, with the aim of providing governments, policy makers, scientists, private enterprises and citizens in the Arctic with access to geographically related Arctic data, digital maps, and tools to facilitate monitoring and decision-making. The initiative will achieve this aim by providing a framework of spatial information resources, organizational structures, technologies of creation, processing and exchange of spatial data, that provides broad access and efficient use of spatial data for the Arctic. The engineering report provides a review of the policy drivers supporting the establishment of spatial data infrastructure (SDI) in each Arctic nation in order to improve understanding of the use cases, user groups and the impact an ArcticSDI may have on their day-to-day business. The engineering report presents lessons learnt along each of the components of SDI, for example, users, data, technology, standards, policy and others. A discussion is presented on how the technologies and standards already in use by the national mapping agencies relate to the technologies and standards implemented by the testbed, as well as how emerging geospatial standards could benefit the ArcticSDI." + "@value": "This OGC Testbed 16 Engineering Report (ER) examines all aspects of security and trust in federated computing environments as defined in the NIST Cloud Federation Reference Architecture [1]. The security and trust requirements are identified. Then possible approaches for achieving security and trust are examined. These approaches range from traditional methods for securing just the basic communications among federated entities to the use of emerging security technologies including federated roots of trust, trust frameworks, blockchain, data-centric security, and zero trust architectures." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -44456,35 +42794,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-063" + "@value": "20-027" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Arctic Spatial Data Infrastructure Engineering Report" + "@value": "OGC Testbed-16: Federated Security" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-107", + "@id": "http://www.opengis.net/def/docs/07-055r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-09-28" + "@value": "2007-10-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeremy Tandy, Linda van den Brink, Payam Barnaghi" + "@value": "Arliss Whiteside, Markus U. M" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -44494,27 +42832,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://www.w3.org/TR/sdw-bp/" + "@id": "https://portal.ogc.org/files/?artifact_id=24314" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-107" + "@value": "Web Coordinate Transformation Service" }, { "@language": "en", - "@value": "Spatial Data on the Web Best Practices" + "@value": "07-055r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document advises on best practices related to the publication of spatial data on the Web; the use of Web technologies as they may be applied to location. The best practices presented here are intended for practitioners, including Web developers and geospatial experts, and are compiled based on evidence of real-world application. These best practices suggest a significant change of emphasis from traditional Spatial Data Infrastructures by adopting an approach based on general Web standards. As location is often the common factor across multiple datasets, spatial data is an especially useful addition to the Web of data." + "@value": "This Discussion Paper describes an interface specification for a web coordinate transformation service that now builds on version 1.1 of the OWS Common Specification [OGC 06-121r3]. All versions of this document specify an " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -44525,82 +42863,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-107" + "@value": "07-055r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Spatial Data on the Web Best Practices" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/cs", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/17-014r8" - }, - { - "@id": "http://www.opengis.net/def/docs/19-065" - }, - { - "@id": "http://www.opengis.net/def/docs/17-014r9" - }, - { - "@id": "http://www.opengis.net/def/docs/20-072r2" - }, - { - "@id": "http://www.opengis.net/def/docs/21-069r2" - }, - { - "@id": "http://www.opengis.net/def/docs/17-002r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-014r7" - }, - { - "@id": "http://www.opengis.net/def/docs/17-014r5" - }, - { - "@id": "http://www.opengis.net/def/docs/17-030r1" - }, - { - "@id": "http://www.opengis.net/def/docs/18-053r2" - }, - { - "@id": "http://www.opengis.net/def/docs/20-072r5" - }, - { - "@id": "http://www.opengis.net/def/docs/21-050r1" - }, - { - "@id": "http://www.opengis.net/def/docs/22-025r4" - }, - { - "@id": "http://www.opengis.net/def/docs/20-094" + "@value": "Web Coordinate Transformation Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-052r4", + "@id": "http://www.opengis.net/def/docs/04-084", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-06-12" + "@value": "2005-06-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthew Perry, John Herring" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -44610,27 +42901,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47664" + "@id": "https://portal.ogc.org/files/?artifact_id=7560" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GeoSPARQL - A Geographic Query Language for RDF Data" + "@value": "Topic 0 - Overview" }, { "@language": "en", - "@value": "11-052r4" + "@value": "04-084" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard defines a set of SPARQL extension functions [W3C SPARQL], a set of RIF rules [W3C RIF Core], and a core RDF/OWL vocabulary for geographic information based on the General Feature Model, Simple Features [ISO 19125-1], Feature Geometry and SQL MM." + "@value": "Introduction and roadmap to the Abstract specification. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -44641,35 +42932,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-052r4" + "@value": "04-084" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoSPARQL - A Geographic Query Language for RDF Data" + "@value": "Topic 0 - Overview" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-031", + "@id": "http://www.opengis.net/def/docs/15-100r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-01-20" + "@value": "2015-12-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "William Lalonde" + "@value": "Simon J D Cox, Peter Taylor " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -44679,27 +42970,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1313" + "@id": "https://portal.ogc.org/files/?artifact_id=64910" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-031" + "@value": "15-100r1" }, { "@language": "en", - "@value": "Style Management Service" + "@value": "Observations and Measurements – JSON implementation" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the proposed system design for the OGC Style Management Service (SMS).\r\nThe SMS must manage distinct objects that represent styles and symbols and provide the means to discover, query, insert, update, and delete these objects.\r\nStyles provide the mapping from feature types and feature properties and constraints to parameterized Symbols used in drawing maps. Symbols are bundles of predefined graphical parameters and predefined fixed graphic images." + "@value": "This Discussion Paper specifies a potential OGC Candidate Standard for a JSON implementation of the OGC and ISO Observations and Measurements (O&M) conceptual model (OGC Observations and Measurements v2.0 also published as ISO/DIS 19156). This encoding is expected to be useful in RESTful implementations of observation services. \r\nMore specifically, this Discussion Paper defines JSON schemas for observations, and for features involved in sampling when making observations. These provide document models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -44710,35 +43001,42 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-031" + "@value": "15-100r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Style Management Service" + "@value": "OGC Observations and Measurements – JSON implementation" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-008r1", + "@id": "http://www.opengis.net/def/docs/13-026r8", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-12" + "@value": "2019-11-25" + }, + { + "@type": "xsd:date", + "@value": "2016-12-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Christiaan Lemmen, Peter van Oosterom, Mohsen Kalantari, Eva-Maria Unger, Cornelis de Zeeuw" + "@value": "Pedro Gonçalves, Uwe Voges" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/is" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -44748,27 +43046,34 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/wp/18-008r1/18-008r1.html" + "@id": "https://docs.ogc.org/is/13-026r8/13-026r8.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "White Paper on Land Administration" + "@value": "OGC OpenSearch Extension for Earth Observation" }, { "@language": "en", - "@value": "18-008r1" + "@value": "OpenSearch Extension for Earth Observation" + }, + { + "@language": "en", + "@value": "13-026r8" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/is" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This white paper provides an overview of the land administration domain and proposes actions needed for design and develop implementation standards this domain. A close cooperation between the Open Geospatial Consortium (OGC) and ISO is expected to accelerate those developments.\r\n\r\nA huge task is waiting: the establishment of land rights for all: young and old, rich and poor, male and female. Data on many millions of parcels, spatial units, (use-) rights, persons, and parties have to be collected, linked, maintained, and published. Land Administration Systems (LAS) should be designed for maintenance of the dynamic relations between people and land. Existing land administrations require extensions: such as 3D and 4D functionality and datasets, blockchain for transparent transactions, generic processes and integration with remote sensing, and processes to support conversion from social to legal tenure.\r\n\r\nA broad range of geospatial technologies and applications are available. They range from satellite and drone imaging and mapping, to geodesy, precise positioning, geo‐information science, cartography, spatial data infrastructure, and many surveying sub‐disciplines. The scientific and professional disciplines in the geospatial community design, develop, and apply those technologies. Apart from this technical component, a land administration also has a social and legal component. This makes land administration an arena where, apart from the geospatial community, many different scientific and professional disciplines meet. Depending on the stage of development and the level of societal acceptance of the land administration, those disciplines involved may be different." + "@value": "This document is the specification for the OpenSearch extension for Earth Observation collections and products search.\r\n\r\nThis standard is intended to provide a very simple way to make queries to a repository that contains Earth Observation information and to allow syndication of repositories." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -44779,35 +43084,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-008r1" + "@value": "13-026r8" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC White Paper on Land Administration" + "@value": "OGC® OpenSearch Extension for Earth Observation" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-036", + "@id": "http://www.opengis.net/def/docs/07-000", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-06-17" + "@value": "2007-07-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Mike Botts" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -44817,27 +43122,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=10471&version=2" + "@id": "https://portal.ogc.org/files/?artifact_id=21273" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-036" + "@value": "07-000" }, { "@language": "en", - "@value": "GeoXACML, a spatial extension to XACML" + "@value": "Sensor Model Language (SensorML)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC document proposes one possible solution for the declaration and enforcement of access\r\nrestrictions for object-oriented geodata, available through a Service-based Geo Data Infrastructure. It is the\r\nintension of the author to motivate the requirement for such an access control, give a problem statement,\r\ndiscuss an alternative approach and describe the solution, based on GeoXACML." + "@value": "The OpenGIS® Sensor Model Language Encoding Standard (SensorML) specifies models and XML encoding that provide a framework within which the geometric, dynamic, and observational characteristics of sensors and sensor systems can be defined. There are many different sensor types, from simple visual thermometers to complex electron microscopes and earth observing satellites. These can all be supported through the definition of atomic process models and process chains. Within SensorML, all processes and components are encoded as application schema of the Feature model in the Geographic Markup Language (GML) Version 3.1.1. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. For additional information on SensorML, see http://www.botts-inc.net/vast.html\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -44848,45 +43153,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-036" + "@value": "07-000" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GeoXACML, a spatial extension to XACML" + "@value": "OpenGIS Sensor Model Language (SensorML)" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-122r1", + "@id": "http://www.opengis.net/def/docs/99-110", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-02-17" - }, - { - "@type": "xsd:date", - "@value": "2011-11-30" + "@value": "1999-04-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos, Jeff Harrison" - }, - { - "@value": "Jeff Harrison, Panagiotis (Peter) A. Vretanos" + "@value": "Cliff Kottman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -44896,37 +43191,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46964" + "@id": "https://portal.ogc.org/files/?artifact_id=897" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-122r1" - }, - { - "@language": "en", - "@value": "Gazetteer Service - Application Profile of the Web Feature Service Candidate Implementation Standard" + "@value": "Topic 10 - Feature Collections" }, { "@language": "en", - "@value": "Gazetteer Service - Application Profile of the Web Feature Service Best Practice" + "@value": "99-110" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines a Gazetteer Service profile of the OGC Web Feature Service Standard. The OGC Gazetteer Service allows a client to search and retrieve elements of a georeferenced vocabulary of well-known place-names.\r\nThis profile extends the WFS interface in a way that a client is able to\r\n–\tDetermine if a WFS implementation is acting as a Gazetteer Service. \r\n–\tQuery the Gazetteer Service in order to retrieve place-name features without closer examination of the feature type definitions\r\n–\tAccess metadata about the gazetteer(s) provided by the service\r\n–\tUpdate place-name features using WFS transactions\r\n–\tFetch place-name features that have Parent-Child relationships and then follow those links\r\n" - }, - { - "@value": "Web Feature Service (WFS-G). Services compliant with this standard shall provide Location Instances derived from SI_LocationInstance. In Addition, they may support queries based on the (parent/child) relationships of feature instances, as defined in ISO 19112." + "@value": "An OpenGIS Feature Collection is an abstract object consisting of Feature Instances, their Feature Schema, and Project Schema." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -44937,39 +43222,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-122r1" + "@value": "99-110" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Gazetteer Service - Application Profile of the Web Feature Service Candidate Implementation Standard" - }, - { - "@language": "en", - "@value": "Gazetteer Service - Application Profile of the Web Feature Service Best Practice" + "@value": "Topic 10 - Feature Collections" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-068r4", + "@id": "http://www.opengis.net/def/docs/07-063r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-01-15" + "@value": "2009-11-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Thomas H.G. Lankester" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -44979,27 +43260,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=28506" + "@id": "https://portal.ogc.org/files/?artifact_id=30912" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-068r4" + "@value": "07-063r1" }, { "@language": "en", - "@value": "Web Coverage Service (WCS) - Transaction operation extension" + "@value": "Web Map Services - Application Profile for EO Products" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This extension of the WCS standard specifies an additional Transaction operation that may optionally be implemented by WCS servers. This Transaction operation allows clients to add, modify, and delete grid coverages that are available from a WCS server. The Transaction operation request references or includes the new or modified coverage data, including all needed coverage metadata. " + "@value": "This OGC document specifies a constrained, consistent interpretation of the WMS specification that is applicable to government, academic and commercial providers of EO products. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -45010,35 +43291,58 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-068r4" + "@value": "07-063r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Coverage Service (WCS) - Transaction operation extension" + "@value": "Web Map Services - Application Profile for EO Products" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-091r3", + "@id": "http://www.opengis.net/def/doc-type/pol-nts", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/09-047r3" + }, + { + "@id": "http://www.opengis.net/def/docs/18-042r4" + }, + { + "@id": "http://www.opengis.net/def/docs/12-081" + }, + { + "@id": "http://www.opengis.net/def/docs/20-059r4" + }, + { + "@id": "http://www.opengis.net/def/docs/10-103r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-048r5" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/99-113", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-04-05" + "@value": "1999-03-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ben Domenico" + "@value": "Cliff Kottman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/primer" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -45048,27 +43352,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=43733" + "@id": "https://portal.ogc.org/files/?artifact_id=901" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-091r3" + "@value": "99-113" }, { "@language": "en", - "@value": "CF-netCDF Core and Extensions Primer" + "@value": "Topic 13 - Catalog Services" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/primer" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC primer provides an overview of the OGC CF-netCDF standards suite by describ-ing the CF-netCDF core and extensions. The CF-netCDF standard defines how to encode digital geospatial information representing space/time-varying phenomena" + "@value": "Covers the Geospatial Information Access Services" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -45079,35 +43383,129 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-091r3" + "@value": "99-113" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CF-netCDF Core and Extensions Primer" + "@value": "Topic 13 - Catalog Services" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-096", + "@id": "http://www.opengis.net/def/doc-type/retired/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Retired Specification" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Retired Specification" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/01-042" + }, + { + "@id": "http://www.opengis.net/def/docs/01-037" + }, + { + "@id": "http://www.opengis.net/def/docs/01-026r1" + }, + { + "@id": "http://www.opengis.net/def/docs/03-003r10" + }, + { + "@id": "http://www.opengis.net/def/docs/01-004" + }, + { + "@id": "http://www.opengis.net/def/docs/99-103" + }, + { + "@id": "http://www.opengis.net/def/docs/03-055r1" + }, + { + "@id": "http://www.opengis.net/def/docs/00-117" + }, + { + "@id": "http://www.opengis.net/def/docs/05-036" + }, + { + "@id": "http://www.opengis.net/def/docs/03-063r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-110" + }, + { + "@id": "http://www.opengis.net/def/docs/04-088" + }, + { + "@id": "http://www.opengis.net/def/docs/99-114" + }, + { + "@id": "http://www.opengis.net/def/docs/06-010r6" + }, + { + "@id": "http://www.opengis.net/def/docs/01-035" + }, + { + "@id": "http://www.opengis.net/def/docs/03-061" + }, + { + "@id": "http://www.opengis.net/def/docs/99-104" + }, + { + "@id": "http://www.opengis.net/def/docs/04-085" + }, + { + "@id": "http://www.opengis.net/def/docs/03-064r10" + }, + { + "@id": "http://www.opengis.net/def/docs/04-087" + }, + { + "@id": "http://www.opengis.net/def/docs/03-062r1" + }, + { + "@id": "http://www.opengis.net/def/docs/04-086" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Retired Specification" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/00-117", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-01-18" + "@value": "2000-05-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Akinori Asahara, Hideki Hayashi, Carl Reed" + "@value": "Cliff Kottman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -45117,27 +43515,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64623" + "@id": "https://portal.ogc.org/files/?artifact_id=988" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-096" + "@value": "Topic 17 - Location Based Mobile Services" }, { "@language": "en", - "@value": "Use Cases and Applications of the OGC Moving Features Standard: The Requirements for a Moving Feature API" + "@value": "00-117" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Discussion Paper provides examples of some actual and potential geospatial applications using the OGC Moving Features encoding. These applications can be used to define the next steps in the development of the OGC Moving Features Standard: The definition of a “Moving Features API”. As a conclusion, the Moving Features SWG recommends that a new Moving Features API standard should target the following three kinds of operations: retrieval of feature information, operations between a trajectory and a geometric object, and operations between two trajectories. Additionally, the Moving Features SWG recommends establishing an abstract specification for these three kinds of operations because only a part of operations for trajectories is defined by ISO 19141:2008 - Schema for moving features." + "@value": "Draft Abstract Spec for Location Based Services. Never formally adopted" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -45148,35 +43546,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-096" + "@value": "00-117" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Use Cases and Applications of the OGC Moving Features Standard: The Requirements for a Moving Feature API" + "@value": "Topic 17 - Location Based Mobile Services" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-114", + "@id": "http://www.opengis.net/def/docs/11-062r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-04-04" + "@value": "2011-11-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman" + "@value": "David Burggraf, Ron Lake" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -45186,27 +43584,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=902" + "@id": "https://portal.ogc.org/files/?artifact_id=46548" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 14 - Semantics and Information Communities" + "@value": "OWS-8 CCI Portrayal Registries Engineering Report" }, { "@language": "en", - "@value": "99-114" + "@value": "11-062r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS notion of Information Communities was devised to enable groups such as ecologists and civil engineers to efficiently manage the semantics (or feature schema mismatches) of their own geodata collections and get maximum benefit from each other's geodata collections, despite semantic differences." + "@value": "The OWS-8 Cross Community Interoperability (CCI) thread was built on progress made in the recent OWS-7 initiative to cover key technology areas that could not be addressed within the scope of that initiative. The OWS-8 CCI thread aimed to increase interoperability within communities sharing geospatial data, including advancing of interoperability among heterogeneous data models, advancing strategies to share styles to provide a more common and automated use of symbology, improvement of KML, and advancing schema automation allowing communities to better share their information artifacts. This OGC engineering report aims to present findings from the portrayal registries as part of the CCI subthread" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -45217,35 +43615,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-114" + "@value": "11-062r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 14 - Semantics and Information Communities" + "@value": "OWS-8 CCI Portrayal Registries Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-010", + "@id": "http://www.opengis.net/def/docs/16-051", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-27" + "@value": "2017-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Kristin Stock" + "@value": "Joan Masó" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -45255,27 +43653,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://portal.opengeospatial.org/files/?artifact_id=32620" + "@id": "https://docs.ogc.org/per/16-051.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC® Catalogue Services - OWL Application Profile of CSW" + "@value": "16-051" }, { "@language": "en", - "@value": "09-010" + "@value": "Testbed-12 Javascript-JSON-JSON-LD Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes an Application Profile for the Web Ontology Language (OWL) [W3C OWL] for CSW. It is intended to define a specification for how ontologies built using RDF and OWL may be included within an OGC CSW catalogue to semantically-enable the catalogue." + "@value": "The Testbed-11 deliverable OGC 15-053 Implementing JSON/GeoJSON in an OGC Standard ER enumerated strategies for implementing JSON in OGC services and OGC encodings. Previously, a mechanism to migrate XML into JSON was proposed by Pedro Gonçalves in 14-009r1 OGC Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context. In contrast, this engineering report (ER) proposes a mechanism to derive JSON and JSON-LD encodings from UML modeling without using XML as an intermediate step. The rules provided can be divided into rules for JSON instances and rules for JSON schemas.\r\n\r\nThese rules have been applied to the UML diagrams in OWS common 2.0 to derive JSON encodings for them. In practice this ER evaluates how to provide service metadata in the derived JSON. JSON schemas and @context documents for independent validation of the four main sections of the ServiceMetadata are provided. This activity is done in connection with the OGC 16-052 OWS Context / Capabilities ER. The rules are applied to WMS to provide a full JSON encoding for the WMS 1.4 standard candidate.\r\n\r\nFinally, this ER discusses the applicability to data geospatial formats, both for coverage formats (compared to the CIS standard) and feature formats (compared to GeoJSON).\r\n\r\nReaders unfamiliar with JSON, JSON-LD and JSON Schema should first read OGC 16-122 (Geo)JSON User Guide. OGC 16-122 includes guidelines and recommendations for the use of JSON and JSON-LD in OGC data encodings and services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -45286,35 +43684,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-010" + "@value": "16-051" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Catalogue Services - OWL Application Profile of CSW" + "@value": "Testbed-12 Javascript-JSON-JSON-LD Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-009", + "@id": "http://www.opengis.net/def/docs/18-034r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-01-12" + "@value": "2019-02-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Martin Daly" + "@value": "Andrea Aime, Emanuele Tajariol, Simone Giannecchini" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -45324,27 +43722,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=999" + "@id": "https://docs.ogc.org/per/18-034r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "01-009" + "@value": "18-034r3" }, { "@language": "en", - "@value": "Coordinate Transformation Service Implementation Specification" + "@value": "Compliance Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Coordinate Transformation Service Standard (CTS) provides a standard way for software to specify and access coordinate transformation services for use on specified spatial data. This standard addresses a key requirement for overlaying views of geodata (“maps”) from diverse sources: the ability to perform coordinate transformation in such a way that all spatial data are defined relative to the same spatial reference system. " + "@value": "The OGC Compliance Program provides a free online testing facility based on TeamEngine and a set of test suites dedicated to specific protocols and versions, as well as specification profiles and extension.\r\n\r\nThis document reviews the work that has been carried out as part of the Testbed-14 compliance activity, in particular covering the development of:\r\n\r\nA Web Feature Service (WFS) 3 core test suite, covering both the tests and the reference implementation servers\r\n\r\nA Defence Geospatial Information Working Group CATalog (DGIWG CAT) 2.0 extension for the Catalog Services for the Web 2.0.2 (CSW) test suite and server reference implementation\r\n\r\nThe WFS 3.0 protocol is the next iteration of the WFS specification, focusing on open specification, ease of implementation, and modern Representational State Transfer (REST) Application Program Interface (API) approaches.\r\n\r\nThe DGIWG CAT is an application profile of the CSW, which allows to query and get metadata following the DGIWG application profile of the ISO19139 standard, which augments the metadata elements to include information relevant to the defense organizations.\r\n\r\nBoth the test suites are meant to be run by the Test, Evaluation, And Measurement (TEAM) Engine and eventually land on the OGC beta compliance test engine (availability on the primary site is subject to the WFS 3.0 specification being finalized and the tests being adapted to it)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -45355,35 +43753,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-009" + "@value": "18-034r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Coordinate Transformation Service Implementation Specification" + "@value": "OGC Testbed-14: Compliance Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-118", + "@id": "http://www.opengis.net/def/docs/17-086r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-04-28" + "@value": "2021-03-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele, Rafael Renkert" + "@value": "Peter Trevelyan, Paul Hershberg, Steve Olson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -45393,27 +43791,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12894" + "@id": "https://docs.ogc.org/is/17-086r3/17-086r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Web Services (OWS) 3 UGAS Tool" + "@value": "17-086r3" }, { "@language": "en", - "@value": "05-118" + "@value": "MetOcean Application profile for WCS2.1: Part 2 MetOcean GetPolygon Extension" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document contains a description of the UGAS (UML Application Schema to GML ApplicationSchema conversion) tool development in the decision support services thread (GeoDSS) during the OWS-3 initiative." + "@value": "The purpose of the GetPolygon operation is to extract data contained within a polygon defined either by a set of points or the radius and position of a circle point. The need for the GetPolygon operation stems from active members of the OGC MetOcean Domain Working Group (DWG) who saw a manifest need for extraction of such information from gridded datasets.\r\n\r\nThis work has been done by members of the OGC MetOcean Domain Working Group." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -45424,35 +43822,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-118" + "@value": "17-086r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Services (OWS) 3 UGAS Tool" + "@value": "OGC MetOcean Application profile for WCS2.1: Part 2 MetOcean GetPolygon Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-027", + "@id": "http://www.opengis.net/def/docs/17-030r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-06" + "@value": "2018-03-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Craig A. Lee" + "@value": "ASPRS" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -45462,27 +43860,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-027.html" + "@id": "https://portal.ogc.org/files/?artifact_id=74523" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-027" + "@value": "17-030r1" }, { "@language": "en", - "@value": "OGC Testbed-16: Federated Security" + "@value": "LAS Specification 1.4 OGC Community Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 16 Engineering Report (ER) examines all aspects of security and trust in federated computing environments as defined in the NIST Cloud Federation Reference Architecture [1]. The security and trust requirements are identified. Then possible approaches for achieving security and trust are examined. These approaches range from traditional methods for securing just the basic communications among federated entities to the use of emerging security technologies including federated roots of trust, trust frameworks, blockchain, data-centric security, and zero trust architectures." + "@value": "The LAS file is intended to contain LIDAR (or other) point cloud data records. The data will\r\ngenerally be put into this format from software (e.g. provided by LIDAR hardware vendors) which\r\ncombines GPS, IMU, and laser pulse range data to produce X, Y, and Z point data. The intention\r\nof the data format is to provide an open format that allows different LIDAR hardware and software\r\ntools to output data in a common format.\r\nThis document reflects the fourth revision of the LAS format specification since its initial version\r\n1.0 release." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -45493,35 +43891,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-027" + "@value": "17-030r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: Federated Security" + "@value": "LAS Specification 1.4 OGC Community Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-147r3", + "@id": "http://www.opengis.net/def/docs/03-003r10", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-03-26" + "@value": "2004-05-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Peter Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -45531,27 +43929,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=50140" + "@id": "https://portal.ogc.org/files/?artifact_id=4347" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - Corrigendum " + "@value": "03-003r10" }, { "@language": "en", - "@value": "09-147r3" + "@value": "Level 0 Profile of GML3 for WFS" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies an extension to the OGC Web Coverage Service (WCS) 2.0 core to allow for client/server communication using HTTP GET with key/value pair (KVP) encod-ing. " + "@value": "*RETIRED* This is a GML application profile known as Level 0 - also known as Simple GML." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -45562,35 +43960,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-147r3" + "@value": "03-003r10" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - Corrigendum " + "@value": "Level 0 Profile of GML3 for WFS" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-018", + "@id": "http://www.opengis.net/def/docs/15-074", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-26" + "@value": "2015-07-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Alaitz Zabala, Joan Maso" + "@value": "Frans Knibbe, Alejandro Llaves" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -45600,27 +43998,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-018.html" + "@id": "https://docs.ogc.org/dp/15-074/15-074.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-018" + "@value": "15-074" }, { "@language": "en", - "@value": "Testbed-13: Data Quality Specification Engineering Report" + "@value": "Spatial Data on the Web Use Cases & Requirements" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OGC 17-018 (Testbed-13 Data Quality Specification Engineering Report) provides methods to quantify the quality concepts defined in OGC 17-032 and a way to include the quantifications in service descriptions. It extends QualityML quality metrics (that already includes ISO 19157) into the aviation domain. It lists a set of quantitative and conformance measurements that are specified in terms of quality measures, domains, and metrics (value types and units) and are appropriated for each quality type and data type. Secondly, it extends the SDCM to be able to encode and include the above mentioned quality information for each service in a interoperable way." + "@value": "This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -45631,228 +44029,575 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-018" + "@value": "15-074" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@language": "en", - "@value": "OGC Testbed-13: Data Quality Specification Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-dp", - "http://www.w3.org/2004/02/skos/core#narrower": [ + "@language": "en", + "@value": "Spatial Data on the Web Use Cases & Requirements" + } + ] + }, + { + "@id": "http://www.opengis.net/def/doc-type/is/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type OGC Implementation Specification" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type OGC Implementation Specification" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/05-005" + }, + { + "@id": "http://www.opengis.net/def/docs/17-047r1" + }, + { + "@id": "http://www.opengis.net/def/docs/14-084r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-000r2" + }, + { + "@id": "http://www.opengis.net/def/docs/14-100r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-019" + }, + { + "@id": "http://www.opengis.net/def/docs/12-132r4" + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r10" + }, + { + "@id": "http://www.opengis.net/def/docs/07-036" + }, + { + "@id": "http://www.opengis.net/def/docs/99-050" + }, + { + "@id": "http://www.opengis.net/def/docs/17-066r2" + }, + { + "@id": "http://www.opengis.net/def/docs/06-131r6" + }, + { + "@id": "http://www.opengis.net/def/docs/08-059r3" + }, + { + "@id": "http://www.opengis.net/def/docs/11-014r3" + }, + { + "@id": "http://www.opengis.net/def/docs/07-006r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-100r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-000" + }, + { + "@id": "http://www.opengis.net/def/docs/21-006r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-026r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-085r5" + }, + { + "@id": "http://www.opengis.net/def/docs/16-103r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-006" + }, + { + "@id": "http://www.opengis.net/def/docs/15-042r3" + }, + { + "@id": "http://www.opengis.net/def/docs/15-042r5" + }, + { + "@id": "http://www.opengis.net/def/docs/07-099r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-165r2" + }, + { + "@id": "http://www.opengis.net/def/docs/16-105r2" + }, + { + "@id": "http://www.opengis.net/def/docs/17-089r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-007r2" + }, + { + "@id": "http://www.opengis.net/def/docs/06-121r9" + }, + { + "@id": "http://www.opengis.net/def/docs/06-141r6" + }, + { + "@id": "http://www.opengis.net/def/docs/06-009r6" + }, + { + "@id": "http://www.opengis.net/def/docs/09-146r6" + }, + { + "@id": "http://www.opengis.net/def/docs/15-113r6" + }, + { + "@id": "http://www.opengis.net/def/docs/13-133r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-025r2" + }, + { + "@id": "http://www.opengis.net/def/docs/15-113r3" + }, + { + "@id": "http://www.opengis.net/def/docs/19-011r4" + }, + { + "@id": "http://www.opengis.net/def/docs/99-054" + }, + { + "@id": "http://www.opengis.net/def/docs/16-083r2" + }, + { + "@id": "http://www.opengis.net/def/docs/07-110r4" + }, + { + "@id": "http://www.opengis.net/def/docs/15-018r2" + }, + { + "@id": "http://www.opengis.net/def/docs/17-086r3" + }, + { + "@id": "http://www.opengis.net/def/docs/08-085r8" + }, + { + "@id": "http://www.opengis.net/def/docs/19-086r4" + }, + { + "@id": "http://www.opengis.net/def/docs/07-057r7" + }, + { + "@id": "http://www.opengis.net/def/docs/20-058" + }, + { + "@id": "http://www.opengis.net/def/docs/11-038R2" + }, + { + "@id": "http://www.opengis.net/def/docs/15-042r6" + }, + { + "@id": "http://www.opengis.net/def/docs/14-083r2" + }, + { + "@id": "http://www.opengis.net/def/docs/16-120r3" + }, + { + "@id": "http://www.opengis.net/def/docs/23-024" + }, + { + "@id": "http://www.opengis.net/def/docs/12-100r1" + }, + { + "@id": "http://www.opengis.net/def/docs/18-010r7" + }, + { + "@id": "http://www.opengis.net/def/docs/01-009" + }, + { + "@id": "http://www.opengis.net/def/docs/05-077r4" + }, + { + "@id": "http://www.opengis.net/def/docs/05-007r7" + }, + { + "@id": "http://www.opengis.net/def/docs/08-068r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-094r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-168r6" + }, + { + "@id": "http://www.opengis.net/def/docs/12-176r7" + }, + { + "@id": "http://www.opengis.net/def/docs/16-101r2" + }, + { + "@id": "http://www.opengis.net/def/docs/15-112r2" + }, + { + "@id": "http://www.opengis.net/def/docs/05-047r3" + }, + { + "@id": "http://www.opengis.net/def/docs/22-050r1" + }, + { + "@id": "http://www.opengis.net/def/docs/20-050" + }, + { + "@id": "http://www.opengis.net/def/docs/12-084r2" + }, + { + "@id": "http://www.opengis.net/def/docs/23-008r3" + }, + { + "@id": "http://www.opengis.net/def/docs/14-005r3" + }, + { + "@id": "http://www.opengis.net/def/docs/18-058r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-000" + }, + { + "@id": "http://www.opengis.net/def/docs/21-056r11" + }, + { + "@id": "http://www.opengis.net/def/docs/15-098r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-121r3" + }, + { + "@id": "http://www.opengis.net/def/docs/10-090r3" + }, + { + "@id": "http://www.opengis.net/def/docs/17-080r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-001" + }, + { + "@id": "http://www.opengis.net/def/docs/10-157r4" + }, + { + "@id": "http://www.opengis.net/def/docs/16-032r3" + }, + { + "@id": "http://www.opengis.net/def/docs/22-049r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-007r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-147r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-043r3" + }, + { + "@id": "http://www.opengis.net/def/docs/15-111r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-127r2" + }, + { + "@id": "http://www.opengis.net/def/docs/16-060r2" + }, + { + "@id": "http://www.opengis.net/def/docs/21-065r2" + }, + { + "@id": "http://www.opengis.net/def/docs/17-069r4" + }, + { + "@id": "http://www.opengis.net/def/docs/16-007r5" + }, + { + "@id": "http://www.opengis.net/def/docs/13-057r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r18" + }, + { + "@id": "http://www.opengis.net/def/docs/07-098r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-008r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-144r4" + }, + { + "@id": "http://www.opengis.net/def/docs/16-102r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-080r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-068r3" + }, + { + "@id": "http://www.opengis.net/def/docs/21-057" + }, + { + "@id": "http://www.opengis.net/def/docs/09-110r4" + }, + { + "@id": "http://www.opengis.net/def/docs/13-131r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-000" + }, + { + "@id": "http://www.opengis.net/def/docs/15-112r3" + }, + { + "@id": "http://www.opengis.net/def/docs/14-055r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-088" + }, + { + "@id": "http://www.opengis.net/def/docs/16-106r2" + }, + { + "@id": "http://www.opengis.net/def/docs/16-071r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-007r3" + }, + { + "@id": "http://www.opengis.net/def/docs/07-000" + }, { - "@id": "http://www.opengis.net/def/docs/05-077" + "@id": "http://www.opengis.net/def/docs/18-058" }, { - "@id": "http://www.opengis.net/def/docs/01-044r2" + "@id": "http://www.opengis.net/def/docs/11-017" }, { - "@id": "http://www.opengis.net/def/docs/07-057r2" + "@id": "http://www.opengis.net/def/docs/09-083r3" }, { - "@id": "http://www.opengis.net/def/docs/03-031" + "@id": "http://www.opengis.net/def/docs/19-086r5" }, { - "@id": "http://www.opengis.net/def/docs/07-024" + "@id": "http://www.opengis.net/def/docs/06-042" }, { - "@id": "http://www.opengis.net/def/docs/05-007" + "@id": "http://www.opengis.net/def/docs/15-045r7" }, { - "@id": "http://www.opengis.net/def/docs/01-013r1" + "@id": "http://www.opengis.net/def/docs/10-126r4" }, { - "@id": "http://www.opengis.net/def/docs/05-007r2" + "@id": "http://www.opengis.net/def/docs/18-062r2" }, { - "@id": "http://www.opengis.net/def/docs/02-026r1" + "@id": "http://www.opengis.net/def/docs/18-067r3" }, { - "@id": "http://www.opengis.net/def/docs/05-057r3" + "@id": "http://www.opengis.net/def/docs/16-079" }, { - "@id": "http://www.opengis.net/def/docs/07-028r1" + "@id": "http://www.opengis.net/def/docs/15-043r3" }, { - "@id": "http://www.opengis.net/def/docs/06-028" + "@id": "http://www.opengis.net/def/docs/13-026r8" }, { - "@id": "http://www.opengis.net/def/docs/06-054r1" + "@id": "http://www.opengis.net/def/docs/15-001r4" }, { - "@id": "http://www.opengis.net/def/docs/03-013" + "@id": "http://www.opengis.net/def/docs/15-078r6" }, { - "@id": "http://www.opengis.net/def/docs/06-057r1" + "@id": "http://www.opengis.net/def/docs/16-104r2" }, { - "@id": "http://www.opengis.net/def/docs/07-018" + "@id": "http://www.opengis.net/def/docs/04-094" }, { - "@id": "http://www.opengis.net/def/docs/03-008r2" + "@id": "http://www.opengis.net/def/docs/22-022r1" }, { - "@id": "http://www.opengis.net/def/docs/05-019" + "@id": "http://www.opengis.net/def/docs/08-085r4" }, { - "@id": "http://www.opengis.net/def/docs/04-017r1" + "@id": "http://www.opengis.net/def/docs/16-107r2" }, { - "@id": "http://www.opengis.net/def/docs/02-039r1" + "@id": "http://www.opengis.net/def/docs/10-032r8" }, { - "@id": "http://www.opengis.net/def/docs/06-093" + "@id": "http://www.opengis.net/def/docs/17-003r2" }, { - "@id": "http://www.opengis.net/def/docs/02-026r4" + "@id": "http://www.opengis.net/def/docs/10-129r1" }, { - "@id": "http://www.opengis.net/def/docs/11-039r2" + "@id": "http://www.opengis.net/def/docs/11-052r4" }, { - "@id": "http://www.opengis.net/def/docs/08-167r1" + "@id": "http://www.opengis.net/def/docs/22-047r1" }, { - "@id": "http://www.opengis.net/def/docs/07-038" + "@id": "http://www.opengis.net/def/docs/21-026" }, { - "@id": "http://www.opengis.net/def/docs/08-129" + "@id": "http://www.opengis.net/def/docs/06-104r4" }, { - "@id": "http://www.opengis.net/def/docs/04-049r1" + "@id": "http://www.opengis.net/def/docs/19-045r3" }, { - "@id": "http://www.opengis.net/def/docs/05-109r1" + "@id": "http://www.opengis.net/def/docs/15-113r5" }, { - "@id": "http://www.opengis.net/def/docs/05-035r1" + "@id": "http://www.opengis.net/def/docs/17-007r1" }, { - "@id": "http://www.opengis.net/def/docs/04-038r1" + "@id": "http://www.opengis.net/def/docs/12-128r12" }, { - "@id": "http://www.opengis.net/def/docs/12-027r2" + "@id": "http://www.opengis.net/def/docs/17-069r3" }, { - "@id": "http://www.opengis.net/def/docs/04-013r4" + "@id": "http://www.opengis.net/def/docs/20-057" }, { - "@id": "http://www.opengis.net/def/docs/09-142r1" + "@id": "http://www.opengis.net/def/docs/19-079r2" }, { - "@id": "http://www.opengis.net/def/docs/06-131" + "@id": "http://www.opengis.net/def/docs/12-128r17" }, { - "@id": "http://www.opengis.net/def/docs/02-061r1" + "@id": "http://www.opengis.net/def/docs/05-078r4" }, { - "@id": "http://www.opengis.net/def/docs/05-089r1" + "@id": "http://www.opengis.net/def/docs/07-068r4" }, { - "@id": "http://www.opengis.net/def/docs/01-022r1" + "@id": "http://www.opengis.net/def/docs/19-086r6" }, { - "@id": "http://www.opengis.net/def/docs/19-091r1" + "@id": "http://www.opengis.net/def/docs/10-025r1" }, { - "@id": "http://www.opengis.net/def/docs/05-078" + "@id": "http://www.opengis.net/def/docs/06-024r4" }, { - "@id": "http://www.opengis.net/def/docs/01-024r1" + "@id": "http://www.opengis.net/def/docs/16-007r4" }, { - "@id": "http://www.opengis.net/def/docs/01-036" + "@id": "http://www.opengis.net/def/docs/16-008" }, { - "@id": "http://www.opengis.net/def/docs/06-126" + "@id": "http://www.opengis.net/def/docs/17-083r2" }, { - "@id": "http://www.opengis.net/def/docs/05-107" + "@id": "http://www.opengis.net/def/docs/22-051r7" }, { - "@id": "http://www.opengis.net/def/docs/08-128" + "@id": "http://www.opengis.net/def/docs/10-070r2" }, { - "@id": "http://www.opengis.net/def/docs/04-040" + "@id": "http://www.opengis.net/def/docs/20-010" }, { - "@id": "http://www.opengis.net/def/docs/06-055r1" + "@id": "http://www.opengis.net/def/docs/14-111r6" }, { - "@id": "http://www.opengis.net/def/docs/05-025r3" + "@id": "http://www.opengis.net/def/docs/18-073r2" }, { - "@id": "http://www.opengis.net/def/docs/03-064r1" + "@id": "http://www.opengis.net/def/docs/16-032r2" }, { - "@id": "http://www.opengis.net/def/docs/05-112" + "@id": "http://www.opengis.net/def/docs/10-140r2" }, { - "@id": "http://www.opengis.net/def/docs/06-080r1" + "@id": "http://www.opengis.net/def/docs/12-128r14" }, { - "@id": "http://www.opengis.net/def/docs/08-008r1" + "@id": "http://www.opengis.net/def/docs/19-072" }, { - "@id": "http://www.opengis.net/def/docs/02-027" + "@id": "http://www.opengis.net/def/docs/09-148r1" }, { - "@id": "http://www.opengis.net/def/docs/03-021" + "@id": "http://www.opengis.net/def/docs/11-030r1" }, { - "@id": "http://www.opengis.net/def/docs/05-013" + "@id": "http://www.opengis.net/def/docs/12-128r19" }, { - "@id": "http://www.opengis.net/def/docs/12-028" + "@id": "http://www.opengis.net/def/docs/07-074" }, { - "@id": "http://www.opengis.net/def/docs/14-004" + "@id": "http://www.opengis.net/def/docs/15-108r3" }, { - "@id": "http://www.opengis.net/def/docs/05-088r1" + "@id": "http://www.opengis.net/def/docs/14-065" }, { - "@id": "http://www.opengis.net/def/docs/03-088r1" + "@id": "http://www.opengis.net/def/docs/15-112r4" }, { - "@id": "http://www.opengis.net/def/docs/05-087r3" + "@id": "http://www.opengis.net/def/docs/06-103r4" }, { - "@id": "http://www.opengis.net/def/docs/12-066" + "@id": "http://www.opengis.net/def/docs/17-066r1" }, { - "@id": "http://www.opengis.net/def/docs/15-074r1" + "@id": "http://www.opengis.net/def/docs/19-008r4" }, { - "@id": "http://www.opengis.net/def/docs/11-169" + "@id": "http://www.opengis.net/def/docs/17-083r4" }, { - "@id": "http://www.opengis.net/def/docs/06-080" + "@id": "http://www.opengis.net/def/docs/08-028r7" }, { - "@id": "http://www.opengis.net/def/docs/03-002r8" + "@id": "http://www.opengis.net/def/docs/15-097r1" }, { - "@id": "http://www.opengis.net/def/docs/06-035r1" + "@id": "http://www.opengis.net/def/docs/17-079r1" }, { - "@id": "http://www.opengis.net/def/docs/06-166" + "@id": "http://www.opengis.net/def/docs/09-149r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type OGC Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-083r8", + "@id": "http://www.opengis.net/def/docs/03-065r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-02-06" + "@value": "2003-10-16" } ], "http://purl.org/dc/terms/creator": [ @@ -45872,13 +44617,13 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=18153" + "@id": "https://portal.ogc.org/files/?artifact_id=3837" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-083r8" + "@value": "03-065r6" }, { "@language": "en", @@ -45892,7 +44637,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Web Coverage Service (WCS) supports electronic retrieval of geospatial data as coverages " + "@value": "Extends the Web Map Server (WMS) interface to allow access to geospatial coverages that represent values or properties of geographic locations, rather than WMS generated maps (pictures)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -45903,7 +44648,7 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-083r8" + "@value": "03-065r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ @@ -45914,14 +44659,83 @@ ] }, { - "@id": "http://www.opengis.net/def/docs/16-006r3", + "@id": "http://www.opengis.net/def/docs/03-064r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-02-23" + "@value": "2003-06-12" + } + ], + "http://purl.org/dc/terms/creator": [ + { + "@value": "Phillip C. Dibner" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + { + "@id": "http://www.opengis.net/def/doc-type/d-dp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ + { + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + { + "@id": "https://portal.ogc.org/files/?artifact_id=1267" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ + { + "@language": "en", + "@value": "03-064r1" + }, + { + "@language": "en", + "@value": "GO-1 Application Objects Report" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ + { + "@id": "http://www.opengis.net/def/doc-type/d-dp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "This document is a draft of the OpenGIS" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ + { + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "03-064r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@language": "en", + "@value": "GO-1 Application Objects Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/17-066r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ + { + "@type": "xsd:date", + "@value": "2018-03-07" } ], "http://purl.org/dc/terms/creator": [ @@ -45931,7 +44745,7 @@ ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -45941,27 +44755,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=72722" + "@id": "https://docs.ogc.org/is/17-066r1/17-066r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-006r3" + "@value": "17-066r1" }, { "@language": "en", - "@value": "Volume 10: OGC CDB Implementation Guidance" + "@value": "GeoPackage Extension for Tiled Gridded Coverage Data" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. " + "@value": "The “GeoPackage Extension for Tiled Gridded Coverage Data” extension (previously titled Elevation Extension) defines how to encode and store tiled regular gridded data, such as a digital elevation model, in a GeoPackage. In the ISO 19123 Schema for Coverage Geometry standard and in the OGC Coverage Implementation Schema, this type of regular gridded data is classed as grid-regular[1]. The tiles contain values, such as elevation, temperature or pressure, and may be stored as 16-bit PNG files or 32-bit TIFF files. The extension defines two ancillary data tables: one for regular gridded coverages and one for tiles. When using the PNG encoding, a scale and offset may be applied. The extension also allows for a TIFF encoding but constrains many of the TIFF options that are available to simplify development." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -45972,35 +44786,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-006r3" + "@value": "17-066r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 10: OGC CDB Implementation Guidance" + "@value": "OGC GeoPackage Extension for Tiled Gridded Coverage Data" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-027", + "@id": "http://www.opengis.net/def/docs/05-020r29", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-04-26" + "@value": "2023-05-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Glenn Laughlin" + "@value": "Scott Simmons" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/pol" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -46010,27 +44824,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-027.html" + "@id": "https://docs.ogc.org/pol/05-020r29/05-020r29.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-027" + "@value": "Technical Committee Policies and Procedures" }, { "@language": "en", - "@value": "OGC Federated Marine Spatial Data Infrastructure Pilot 2023 - Connecting Land and Sea for Global Awareness" + "@value": "05-020r29" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/pol" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Rising sea levels together with increasing storm surges are amongst the most challenging issues for coastal communities in the context of global warming. The retreating ice sheets of the Circumpolar Arctic are a key contributor to sea level rise with consequences felt around the world.\r\n\r\nThe Federated Marine Spatial Data Infrastructure (FMSDI) initiative is a key component of OGC and the Marine Domain Working Group. The program is designed to engage with stakeholders from the marine dataspace to identify opportunities to assist, improve, and scale out core business processes complemented by the OGC suite of standards and best practices. The FMSDI-2023 pilot represents the fourth phase of the program with a focus on the interface between land and sea. A primary goal of this pilot is to advance the FMSDI concept to increasing threats posed by climate change.\r\n\r\nThe project is divided into three threads, each with application to distinct geographies.\r\n\r\nThread 1: Digital Twin of Land and Sea Interfaces — Singapore\r\nWith approximately 30% of Singapore’s land mass being less than 5m above sea level, the seamless integration of land and marine data is integral to Singapore’s focus on coastal protection and climate resilience. The management of land and water is separated organizationally between the Singapore Land Authority (SLA) and the Maritime & Port Authority (MPA), respectively. Each agency is responsible for data assets specific to their jurisdiction presenting a challenge for cross-organizational concerns. This theme addresses the geospatial integration requirements through the development of a multi-dimensional Digital Twin of the Singapore coastline.\r\n\r\nThread 2: Digital Arctic Connecting Land and Sea — Canada\r\nThis thread addresses the data integration issues in the context of Digital Twins for the Canadian Arctic. With the loss of sea ice, continuing ocean warming, stronger winds and currents, and accelerated shoreline erosion affecting Arctic communities, efficient data usage and analysis is of the utmost importance for Canada.\r\nFigure 1\r\n\r\nThread 3: Integrating Land & Sea for Various Use Cases — Caribbean\r\nThis thread investigates how data developed primarily for navigation at sea can be used to better understand the opportunities in the Caribbean to support local capacity building and the application of marine data in expanded sea-land contexts.\r\n\r\nApproach\r\n\r\nThe FMSDI 2023 pilot is managed through the OGC Collaborative Solutions and Innovation (COSI) Program. Each thread is a distinct project with a set of participants tackling specific use cases and scenarios important to the respective project sponsor.\r\n\r\nWeekly project meetings are scheduled to encourage collaboration between the participants and sponsors and provide checkpoints to ensure the project scope meets the sponsor’s expectations.\r\n\r\nThe FMSDI 2023 pilot also features a series of persistent demonstrators as one of its outputs. These demonstrators are workflows and applications that stakeholders can access for outreach, testing, and experimentation purposes. The demonstrators will be available even after the project is completed and are therefore referenced as persistent, but will only be available until December 2024. These demonstrators showcase how geospatial data can be used in an operational context or highlight the gaps in the resources available online, including data sources, metadata, access processes, and standards. As each participant has a unique solution platform, each has taken different approaches, all of which are available for review by stakeholders. Security concerns, such as authentication and authorization, are unique to each participant and have been communicated to stakeholders and participant contacts. For further details and access to the demonstrators, please refer to the link provided.\r\n\r\nCommon across the three threads is the application of the OGC FAIR principles — Findable, Accessible, Interoperable, and Reusable. Underpinning the use of the FAIR principles is the role of the core OGC Standards and Best Practices. Previous work products related to FMSDI form the core information model while the OGC standards, enhanced through the alignment and support of industry standards such as the IHO S-100 standard, address many of the requirements central to each thread.\r\n\r\nAttention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights.\r\n\r\nRecipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which the recipients may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation." + "@value": "The OGC provides a collaborative, consensus process for developing and approving open, international Standards and supporting content for the geospatial domain, collectively known as OGC Products. To guide the OGC Product development and approval process, a member-approved Policies and Procedures document for the Technical Committee (TC) is required.\r\n\r\nThis document describes the TC Policies and Procedures (TC PnP). The TC has been granted authority to operate by the OGC Bylaws. The TC is composed of individuals representing organizations that are duly recognized members in good standing of the OGC.\r\n\r\nAs the needs and purpose of the TC change, changes to these policies and procedures are approved by an electronic vote of the Voting Members of the OGC TC. These policies and procedures may be augmented or clarified by Policy Directives issued and approved by the TC or the Executive Planning Committee (EPC). Such directives are databased and hyperlinked to/from the appropriate portion of this document." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46041,35 +44855,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-027" + "@value": "05-020r29" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Federated Marine Spatial Data Infrastructure Pilot 2023 - Connecting Land and Sea for Global Awareness" + "@value": "Technical Committee Policies and Procedures" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-059r4", + "@id": "http://www.opengis.net/def/docs/04-010r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-28" + "@value": "2004-05-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona" + "@value": "Peter Schut" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pol-nts" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -46079,27 +44893,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/pol/20-059r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=5858" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Naming of OGC API Standards, Repositories & Specification Elements" + "@value": "Geolinked Data Access Service" }, { "@language": "en", - "@value": "20-059r4" + "@value": "04-010r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pol-nts" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a policy of the OGC Naming Authority (OGC-NA), a sub-committee of the OGC Technical Committee. The document defines a series of policy requirements for OGC API standards, repositories, definitions, and specification elements. The policy document is intended to be a specialization of the OGC-NA policy on naming specification elements (OGC 10-103)." + "@value": "A Geolinked Data Access Service (GDAS) provides a way to publish and access data that refers to spatial features (e.g. population data for countries). A GDAS can expose data from non-GIS databases so that it can be manipulated and mapped with the aid of a Geolinking Service." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46110,30 +44924,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-059r4" + "@value": "04-010r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Naming of OGC API Standards, Repositories & Specification Elements" + "@value": "Geolinked Data Access Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-003r10", + "@id": "http://www.opengis.net/def/docs/04-088", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-05-10" + "@value": "2004-02-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Vretanos" + "@value": "Paul Lunceford,Steve Matney,Tom Huggins,Chuck Heazel" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -46148,17 +44962,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=4347" + "@id": "https://portal.ogc.org/files/?artifact_id=7561" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-003r10" + "@value": "EA-SIG Mediation White Paper" }, { "@language": "en", - "@value": "Level 0 Profile of GML3 for WFS" + "@value": "04-088" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -46168,7 +44982,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*RETIRED* This is a GML application profile known as Level 0 - also known as Simple GML." + "@value": "*RETIRED* This document focuses on the goals, objectives, capabilities and recommendation for the Mediation Core Enterprise\r\nService." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46179,35 +44993,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-003r10" + "@value": "04-088" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Level 0 Profile of GML3 for WFS" + "@value": "EA-SIG Mediation White Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-020", + "@id": "http://www.opengis.net/def/docs/06-104r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-01-03" + "@value": "2007-01-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Churchyard, Ajay Gupta" + "@value": "John Herring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -46217,27 +45031,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-020.html" + "@id": "https://portal.ogc.org/files/?artifact_id=18242" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-020" + "@value": "Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option" }, { "@language": "en", - "@value": "Testbed-18: Identifiers for Reproducible Science Summary Engineering Report" + "@value": "06-104r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC’s Testbed 18 initiative explored the following six tasks.\r\n\r\n1.) Advanced Interoperability for Building Energy\r\n2.) Secure Asynchronous Catalogs\r\n3.) Identifiers for Reproducible Science\r\n4.) Moving Features and Sensor Integration\r\n5.) 3D+ Data Standards and Streaming\r\n6.) Machine Learning Training Data\r\nTestbed 18 Task 3, Identifiers for Reproducible Science, explored and developed workflows demonstrating best practices at the intersection of Findable, Accessible, Interoperable, and Reusable (or FAIR) data and reproducible science.\r\n\r\nThe workflows developed in this Testbed included:\r\n\r\nthe development of a Whole Tail workflow for land cover classification (52 Degrees North);\r\nthe development of a reproducible workflow for a deep learning application for target detection (Arizona State University);\r\nthe implementation of reproducible workflows following the approach described in the OGC API Process Part 3: Workflows and Chaining for Modular OGC API Workflows (Ecere);\r\nthe development of a reproducible workflow that runs an OGC API — Process and Feature Server instance within a Whole Tale environment (GeoLabs); and\r\nthe development of a water body detection Application Package to cover the identifier assignment and reproducibility from code to several execution scenarios (local, Exploitation Platform, Whole Tale) (Terradue).\r\nTestbed 18 participants identified considerations and limitations for reproducible workflows and recommendations for future work to identify the benefits of reproducible science for healthcare use cases." + "@value": "The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. \r\n\r\nPart 1 “Common Architecture supplies the common feature model for use by applications that will use the Simple Features data stores and access interfaces. \r\n\r\nPart 2 provides a standard SQL implementation of the abstract model in Part 1. (Note: The OpenGIS® Simple Features Interface Standards for OLE/COM and CORBA are no longer current and are not provided here.) \r\n\r\nThe corresponding standard for the Web is the OpenGIS® Web Feature Service Interface Standard http://www.opengeospatial.org/standards/wfs.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46248,35 +45062,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-020" + "@value": "06-104r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-18: Identifiers for Reproducible Science Summary Engineering Report" + "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-065r1", + "@id": "http://www.opengis.net/def/docs/13-042", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-10-05" + "@value": "2014-04-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthias Mueller" + "@value": "Daniele Marchionni" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -46286,27 +45100,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/14-065/14-065r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=55209" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-065r1" + "@value": "13-042" }, { "@language": "en", - "@value": "WPS 2.0.1 Interface Standard: Corrigendum 1" + "@value": "RESTful Encoding of Ordering Services Framework For Earth Observation Products" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "In many cases geospatial or location data, including data from sensors, must be processed before the information can be used effectively. The OGC Web Processing Service (WPS) Interface Standard provides a standard interface that simplifies the task of making simple or complex computational processing services accessible via web services. Such services include well-known processes found in GIS software as well as specialized processes for spatio-temporal modeling and simulation. While the OGC WPS standard was designed with spatial processing in mind, it can also be used to readily insert non-spatial processing tasks into a web services environment.\r\n\r\nThe WPS standard provides a robust, interoperable, and versatile protocol for process execution on web services. It supports both immediate processing for computational tasks that take little time and asynchronous processing for more complex and time consuming tasks. Moreover, the WPS standard defines a general process model that is designed to provide an interoperable description of processing functions. It is intended to support process cataloguing and discovery in a distributed environment.\r\n\r\n" + "@value": "This OGC Best Practices document specifies the interfaces, bindings, requirements, conformance classes that enable complete workflows for ordering Earth Observation (EO) data products. In fact it provides the interfaces for supporting the following EO Product ordering scenarios:\r\n•\tOrdering products from EO Catalogues\r\n•\tSubscribing to automatic delivery of EO products\r\n•\tBulk EO Product orders\r\nThe EO products orders can be delivered on file via different online protocols (e.g. ftp, sftp, ftps, etc.).\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46317,30 +45131,99 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-065r1" + "@value": "13-042" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® WPS 2.0.1 Interface Standard: Corrigendum 1" + "@value": "OGC RESTful Encoding of Ordering Services Framework For Earth Observation Products" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-034", + "@id": "http://www.opengis.net/def/docs/01-009", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-03-09" + "@value": "2001-01-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Jirka, Arne de Wall, Christoph Stasch" + "@value": "Martin Daly" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + { + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ + { + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + { + "@id": "https://portal.ogc.org/files/?artifact_id=999" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ + { + "@language": "en", + "@value": "01-009" + }, + { + "@language": "en", + "@value": "Coordinate Transformation Service Implementation Specification" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ + { + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "The OpenGIS® Coordinate Transformation Service Standard (CTS) provides a standard way for software to specify and access coordinate transformation services for use on specified spatial data. This standard addresses a key requirement for overlaying views of geodata (“maps”) from diverse sources: the ability to perform coordinate transformation in such a way that all spatial data are defined relative to the same spatial reference system. " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ + { + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "01-009" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@language": "en", + "@value": "OpenGIS Coordinate Transformation Service Implementation Specification" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/12-163", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ + { + "@type": "xsd:date", + "@value": "2013-06-18" + } + ], + "http://purl.org/dc/terms/creator": [ + { + "@value": "Thibault Dacla; Eriza Hafid Fazli; Charles Chen; Stuart Wilson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -46355,17 +45238,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-034.html" + "@id": "https://portal.ogc.org/files/?artifact_id=51812" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 LiDAR Streaming Engineering Report" + "@value": "OWS-9 Data Transmission Management" }, { "@language": "en", - "@value": "16-034" + "@value": "12-163" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -46375,7 +45258,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report describes how developments of the Community Sensor Model Working Group (CSMW) can be harmonized with the latest SWE specifications and developments in order to support streaming of LiDAR data with SWE technologies. The report will therefore provide an overview on both initiatives and then describe different options how to integrate LiDAR data streams and SWE technologies. In particular, the ER will consider the results of the activities SOS Compression (LiDAR) Server (A012) and LiDAR Streaming Client (A010) and infer recommendations for future developments." + "@value": "This OWS-9 Engineering Report documents investigations, findings, lessons learned and\r\nproposed future work for the Data Transmission Management unit, invented and\r\nprototyped in OWS-9.\r\nThe purpose of the Data Transmission Management unit is to optimize, customize and\r\nmake reliable the information exchange between the aircraft and the different web\r\nservices on the ground." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46386,35 +45269,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-034" + "@value": "12-163" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 LiDAR Streaming Engineering Report" + "@value": "OGC® OWS-9 Data Transmission Management" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-042r4", + "@id": "http://www.opengis.net/def/docs/16-039r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-10-31" + "@value": "2017-06-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Simon Cox" + "@value": "Aleksandar Balaban" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pol-nts" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -46424,27 +45307,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/pol/18-042r4.html" + "@id": "https://docs.ogc.org/per/16-039r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Name Type Specification - Sensor Models and Parameters" + "@value": "Testbed-12 Aviation Semantics Engineering Report" }, { "@language": "en", - "@value": "18-042r4" + "@value": "16-039r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pol-nts" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies a rule for constructing OGC names that may be used for identifying definitions of sensor models and their parameters. This document is formally a profile of the OGC policy 'OGC-NA Name type specification - definitions: Part 1 - basic name' (OGC 09-048r5)." + "@value": "This engineering report examines the role of geospatial semantic technology in the domain of civil aviation. Many aeronautical services (providing information on request or processing the data) are based on OGC Web Service specifications. A number of aeronautical services possess geospatial attributes. The aviation services follow OWS Common Service requirements but also have domain specific capabilities. Services metadata is often very relevant for service consumption, especially in the SOA environment of aviation’s System Wide Information Management (SWIM). Therefore, it shall be exposed to consumer stakeholders for either design or runtime service discovery in an efficient, standardized way.\r\n\r\nThis ER starts introducing the WSDOM service ontology developed by FAA for semantic service discovery. It proposes several extensions useful for OWS compatible, geospatial aviation services. It combines GeoSPARQL with WSDOM ontology and FAA service classification taxonomies and elaborates the interoperability between ontology based WSDOM and OWS compatible service descriptions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46455,30 +45338,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-042r4" + "@value": "16-039r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Name Type Specification - Sensor Models and Parameters" + "@value": "Testbed-12 Aviation Semantics Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-086r1", + "@id": "http://www.opengis.net/def/docs/22-004", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-11-03" + "@value": "2022-11-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Josh Lieberman, Johannes Echterhoff, Matt de Ris, George Wilber" + "@value": "Gobe Hobona, Joana Simoes, Angelos Tzotsos, Tom Kralidis, Martin Desruisseaux" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -46493,17 +45376,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/60176" + "@id": "https://docs.ogc.org/per/22-004.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-086r1" + "@value": "Joint OGC OSGeo ASF Code Sprint 2022 Summary Engineering Report" }, { "@language": "en", - "@value": "Aircraft Access to SWIM (AAtS) Harmonization Project Summary Report" + "@value": "22-004" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -46513,7 +45396,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document summarizes the Aircraft Access to SWIM (AAtS) Harmonization activity developed by a team funded by the FAA and led by the Open Geospatial Consortium (OGC). The activity involved assembling a core team of industry participant experts to analyze and harmonize four standards suites and/or standards-based architectures relevant to air-ground information exchange:\r\n•\tThe Aircraft Access to SWIM (AAtS) concept, \r\n•\tRTCA aeronautical information services (AIS) and meteorological (MET) information data link service committee’s (SC-206) concepts and standards, \r\n•\tAir-Ground Information Exchange A830 (AGIE) standard and \r\n•\tOGC standards and architectural perspectives. \r\nElements of this effort have included:\r\n•\tCreation and public release of a Request for Information\r\n•\tAnalysis of the fits and overlaps between the four standards suites\r\n•\tEngagement with ongoing standards development efforts to reduce incompatibilities\r\n" + "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from the 8th to the 10th of March 2022 to advance support of open geospatial standards within the developer community, whilst also advancing the standards themselves. The code sprint was hosted by the Open Geospatial Consortium (OGC), the Apache Software Foundation (ASF), and Open Source Geospatial Foundation (OSGeo). The code sprint was sponsored by Ordnance Survey (OS), and held as a completely virtual event." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46524,35 +45407,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-086r1" + "@value": "22-004" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Aircraft Access to SWIM (AAtS) Harmonization Project Summary Report" + "@value": "Joint OGC OSGeo ASF Code Sprint 2022 Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-077", + "@id": "http://www.opengis.net/def/docs/07-099r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-05-04" + "@value": "2008-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -46562,27 +45445,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/19-077.html" + "@id": "https://portal.ogc.org/files/?artifact_id=25220" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Body of Knowledge " + "@value": "07-099r1" }, { "@language": "en", - "@value": "19-077" + "@value": "GeoXACML Implementation Specification - Extension B (GML3) Encoding" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Body of Knowledge is a structured collection of concepts and related resources that can be found in the OGC library. It is, in effect, a view of explicit knowledge available from the OGC Virtual Knowledge Store and related components such as the OGC Definitions Server and the OGC Glossary of Terms. The OGC Body of Knowledge is intended to provide a reference for users and developers of geospatial software. This discussion paper describes the approach taken to develop the OGC Body of Knowledge and presents the results of the approach. It is intended to encourage and facilitate discussion within the OGC membership and wider geospatial community." + "@value": "This specification is a normative extension to the GeoXACML core Implementation Specification. It defines the GML3 encoding for geometries." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46593,35 +45476,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-077" + "@value": "07-099r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Body of Knowledge - Version 0.1 - Discussion Paper" + "@value": "GeoXACML Implementation Specification - Extension B (GML3) Encoding" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-054", + "@id": "http://www.opengis.net/def/docs/07-007r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-06-02" + "@value": "2007-06-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Ladstaetter" + "@value": "Paul Watson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -46631,27 +45514,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=834" + "@id": "https://portal.ogc.org/files/?artifact_id=21821" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Simple Features Implementation Specification for CORBA" + "@value": "07-007r1" }, { "@language": "en", - "@value": "99-054" + "@value": "OWS4 - Topology Quality Assessment Interoperability Program Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc)." + "@value": "This document describes the purpose and function of the Topology Quality Assessment Service developed and deployed within the Geo-processing workflow thread of the OWS4 interoperability testbed." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46662,69 +45545,103 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-054" + "@value": "07-007r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Simple Features Implementation Specification for CORBA" + "@value": "OWS4 - Topology Quality Assessment Interoperability Program Report" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/d-profile/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "@id": "http://www.opengis.net/def/doc-type/d-bp", + "http://www.w3.org/2004/02/skos/core#narrower": [ { - "@value": "Documents of type Specification Profile - deprecated " - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/05-027r1" + }, { - "@value": "Documents of type Specification Profile - deprecated " - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/05-086" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ + "@id": "http://www.opengis.net/def/docs/06-131r4" + }, { - "@id": "http://www.opengis.net/def/docs/10-100r2" + "@id": "http://www.opengis.net/def/docs/07-018r1" }, { - "@id": "http://www.opengis.net/def/docs/06-049r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/06-035r1" + }, { - "@value": "Documents of type Specification Profile - deprecated " + "@id": "http://www.opengis.net/def/docs/05-010" + }, + { + "@id": "http://www.opengis.net/def/docs/06-141r2" + }, + { + "@id": "http://www.opengis.net/def/docs/06-135r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-113r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-011" + }, + { + "@id": "http://www.opengis.net/def/docs/06-021r2" + }, + { + "@id": "http://www.opengis.net/def/docs/05-087r4" + }, + { + "@id": "http://www.opengis.net/def/docs/07-063" + }, + { + "@id": "http://www.opengis.net/def/docs/06-080r2" + }, + { + "@id": "http://www.opengis.net/def/docs/07-092r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-062" + }, + { + "@id": "http://www.opengis.net/def/docs/07-039r1" + }, + { + "@id": "http://www.opengis.net/def/docs/03-105r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-023r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-057r4" + }, + { + "@id": "http://www.opengis.net/def/docs/04-038r2" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-032r2", + "@id": "http://www.opengis.net/def/docs/01-009a", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-04" + "@value": "2001-01-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff" + "@value": "Martin Daly" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/sap" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -46734,27 +45651,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-032r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=999" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-032r2" + "@value": "Coordinate Transformation Services - OLE/COM" }, { "@language": "en", - "@value": "Application Schema-based Ontology Development Engineering Report" + "@value": "01-009a" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/sap" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report enhances the understanding of the relationships between application schemas based on the Unified Modeling Language (UML) and ontologies based on the Web Ontology Language (OWL). The work documented in this report provides and improves tools and principled techniques for the development of Resource Description Framework (RDF) based schemas from ISO 19109-conformant application schemas." + "@value": "Provides interfaces for general positioning, coordinate systems, and coordinate transformations." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46765,35 +45682,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-032r2" + "@value": "01-009a" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Application Schema-based Ontology Development Engineering Report" + "@value": "Coordinate Transformation Services - OLE/COM" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-047", + "@id": "http://www.opengis.net/def/docs/08-054r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-07-22" + "@value": "2008-08-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Alexander Jacob" + "@value": "Max Martinez" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -46803,27 +45720,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-047.html" + "@id": "https://portal.ogc.org/files/?artifact_id=29406" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-047" + "@value": "08-054r1" }, { "@language": "en", - "@value": "OGC Testbed-19 GeoDataCubes Engineering Report" + "@value": "OWS-5 Considerations for the WCTS Extension of WPS" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OGC Testbed-19 has continued and furthered an ongoing discussion about how to interact with GeoDataCubes (GDC) in the most interoperable way (see Chapter 1 for more Introduction). Testbed 19 participants produced a draft OGC GDC API standard that incorporates the most relevant developments in the field in and outside of OGC. This work advanced the common understanding of available solutions while discovering to a much better degree the advantages and drawbacks of current solutions. Testbed 19 participants produced prototypes of five back-end implementations and six client implementations as well as an automated test suite, which are described in full detail in Chapter 4. Many of the researched solutions are also available as open source and hence offer a perfect starting point for further GDC activities.\r\n\r\nThe main technologies that were evaluated in Testbed 19 included the OGC API Standards suite1, the openEO API2 and the Spatiotemporal Asset Catalog3 (STAC) specification. Based on cross walk comparisons (see Chapter 2), a unified draft GDC API was developed integrating as much as possible the existing solutions. openEO is largely compliant with the OGC API- Common Standard. As such, the openEO API specification provided the foundation for defining a draft OGC GDC API draft standard. During the Testbed 19 period, more building blocks from the OCG API were incorporated into the draft GDC API document. These building blocks included parts of OGC API — Common, OGC API — Coverages, and OGC API – Processes. There is also future potential for visualization services through maps or tiles or even including components or elements of the OGC Web Services suite of Standards, such as WMS, WMTS, WCS, etc.\r\n\r\nThe current version of the draft GDC API, described in D71 of T19, supports different scenarios enabling implementations of the draft standard to offer only minimal support for data access with minimal manipulation of the data. Minimal manipulation is in terms of subsetting and reprojecting or including more advanced processing capabilities by incorporating building blocks from the openEO specification or from the OGC API — Processes – Part 1: Core Standard. Chapter 3 gives an overview of the draft standard.\r\n\r\nThe interaction capabilities between the different servers and clients developed are described in Chapter 5 and first impressions on usability in Chapter 6.\r\n\r\nFuture work could include the ability to link two processing options into one “integrated” option that supports either submitting openEO process graphs to a OGC API – Processes endpoint (extending and working on Processes — Part 3), or supports integration of an OGC API – Processes process in the process graph of openEO through an extended concept of user defined functions in openEO. Further discussion is also needed on the pros and cons of including authentication in the draft standard. More details about lessons learned and suggestions can be found in Chapters 7 and 8 of this ER." + "@value": "This document details considerations for using the WPS specification to define a standard coordinate transformation service." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46834,35 +45751,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-047" + "@value": "08-054r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-19 GeoDataCubes Engineering Report" + "@value": "OWS-5 Considerations for the WCTS Extension of WPS" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-052r1", + "@id": "http://www.opengis.net/def/docs/11-038R2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-01-18" + "@value": "2012-10-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Frédéric Houbie" + "@value": "Ben Domenico" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -46872,27 +45789,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64860" + "@id": "https://portal.ogc.org/files/?artifact_id=50294" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-052r1" + "@value": "11-038R2" }, { "@language": "en", - "@value": "Testbed 11 REST Interface Engineering Report" + "@value": "OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "REST architectural principles are associated with optimal functioning of the Web but their manifestation in geospatial Web services standards is not straightforward. This OGC Engineering Report (ER) examines their use both in existing OGC Services standards and in new or revised service standard proposals, some of which were implemented during OGC Testbed 11. The ER then defines possible uniform practices for developing bindings or interaction styles for OGC Web services that appropriately leverage REST principles." + "@value": "This standard deals with enhancements to the netCDF (Network Common Data Form) data model for array-oriented scientific data..\r\nTwo important data models for netCDF are:\r\n- the “classic” netCDF model, used for netCDF-3 and earlier versions\r\n- an enhanced data model, used in netCDF-4 and later versions.\r\nThe netCDF classic data model is defined in OGC 10-091r3, “NetCDF Core.”\r\nThis document specifies a netCDF extension standard for the enhanced data model. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space- and time-varying phenomena.\r\nNetCDF (network Common Data Form) is a data model for array-oriented scientific data. The netCDF classic data model is specified in the netCDF core specification. This standard specifies the enhanced data model. A freely distributed collection of access libraries implementing support for that data model in a machine-independent format are available. Together, the interfaces, libraries, and format support the creation, access, and sharing of multi-dimensional scientific data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46903,35 +45820,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-052r1" + "@value": "11-038R2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 11 REST Interface Engineering Report" + "@value": "OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-060r2", + "@id": "http://www.opengis.net/def/docs/12-095", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-11-27" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Daniel Lee" + "@value": "James Gallagher, Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -46941,27 +45858,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/16-060r2/16-060r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=52783" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile" + "@value": "12-095" }, { "@language": "en", - "@value": "16-060r2" + "@value": "OWS-9 Innovation - Coverages: Coverage Access (OPeNDAP) Study" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC standard is a profile of the OGC GML Application Schema - Coverages version 1.0 [OC 09-146r2]. That document was renamed OGC Coverage Implementation Schema (CIS) for clarification in version 1.1. This standard specifies the usage of the GRIB2 data format for the encoding of OGC coverages. The GRIB2 specification is maintained by the World Meteorological Organization (WMO) and is the standard encoding for the exchange and storage of general regularly distributed information expressed in binary form." + "@value": "This document represents the OWS-9 OWS Innovations Coverage Access Study\r\nEngineering Report. It contributes knowledge based on the experience prototyping the\r\nWCS 2.0 Service – Access Innovations component, established in close collaboration\r\nwith the OPeNDAP group. To this end, accessing a variety of coverage data types\r\nconsidering WCS 2.0 and DAP 2.0 interfaces have been implemented and demonstrated.\r\nThe final result is a WCS 2.0 interface for the DAP 2.0 suite." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -46972,98 +45889,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-060r2" + "@value": "12-095" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-bp", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/07-018r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-023r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-087r4" - }, - { - "@id": "http://www.opengis.net/def/docs/05-027r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-086" - }, - { - "@id": "http://www.opengis.net/def/docs/07-092r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-105r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-141r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-113r1" - }, - { - "@id": "http://www.opengis.net/def/docs/04-038r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-035r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-080r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-135r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-062" - }, - { - "@id": "http://www.opengis.net/def/docs/07-063" - }, - { - "@id": "http://www.opengis.net/def/docs/05-057r4" - }, - { - "@id": "http://www.opengis.net/def/docs/05-010" - }, - { - "@id": "http://www.opengis.net/def/docs/07-039r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-011" - }, - { - "@id": "http://www.opengis.net/def/docs/06-021r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-131r4" + "@value": "OGC® OWS-9 Innovation - Coverages: Coverage Access (OPeNDAP) Study" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-079r1", + "@id": "http://www.opengis.net/def/docs/05-140", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-06-06" + "@value": "2006-03-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Marc Gilles" + "@value": "Yves Coene" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -47078,17 +45927,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=15547" + "@id": "https://portal.ogc.org/files/?artifact_id=13916" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "EO Application Profile for CSW 2.0" + "@value": "05-140" }, { "@language": "en", - "@value": "06-079r1" + "@value": "OWS-3 Imagery Workflow Experiments: Enhanced Service Infrastructure Technology Architecture and Standards in the OWS-3 Testbe" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -47098,7 +45947,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Explains how Catalogue Services based on the HMA (Heterogeneous Earth Observation Missions Accessibility) Application Profile for the OGC Catalogue Services Specification v2.0.1 [OGC 04-021r3] are organized and implemented for the discovery, retrieval and management of Earth Observation products metadata." + "@value": "This document describes the results of an experiment addressing issues relating to the application workflow processing incorporating a variety of OGC specifications. It details the inputs provided to the Open Geospatial Consortium's (OGC) OWS-3 Testbed and the architecture of the testbed related to the ESA Service Support Environment (SSE). \r\nIt is a formal deliverable of work package 6610 of the Enhanced Service Infrastructure Technology (ESIT) project and is a joint Spacebel and Spot Image document.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47109,43 +45958,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-079r1" + "@value": "05-140" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "EO Application Profile for CSW 2.0" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/dp-draft", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/06-021r1" + "@value": "OWS-3 Imagery Workflow Experiments: Enhanced Service Infrastructure Technology Architecture and Standards in the OWS-3 Testbe" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-073r2", + "@id": "http://www.opengis.net/def/docs/20-025r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-08-08" + "@value": "2021-01-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Tisdale" + "@value": "Luis Bermudez" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -47155,27 +45996,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/18-073r2/18-073r2.html" + "@id": "https://docs.ogc.org/per/20-025r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-073r2" + "@value": "20-025r1" }, { "@language": "en", - "@value": "OGC PipelineML Conceptual and Encoding Model Standard" + "@value": "Data Access and Processing API Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC PipelineML Conceptual and Encoding Model Standard defines concepts supporting the interoperable interchange of data pertaining to oil and gas pipeline systems. PipelineML supports the common exchange of oil and gas pipeline information. This initial release of the PipelineML Core addresses two critical business use cases that are specific to the pipeline industry: new construction surveys and pipeline rehabilitation. This standard defines the individual pipeline components with support for lightweight aggregation. Additional aggregation requirements such as right-of-way and land management will utilize the OGC LandInfra standards with utility extensions in the future. Future extensions to PipelineML Core will include (non-limitative): cathodic protection, facility and safety. PipelineML was advanced by an international team of contributors from the US, Canada, Belgium, Norway, Netherlands, UK, Germany, Australia, Brazil, and Korea.\r\n\r\nThis standard assumes the reader has a basic understanding of oil and gas pipeline industry concepts." + "@value": "This OGC Testbed 16 Engineering Report documents the advancement of an OGC Data Access and Processing API (DAPA)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47186,35 +46027,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-073r2" + "@value": "20-025r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC PipelineML Conceptual and Encoding Model Standard" + "@value": "OGC Testbed-16: Data Access and Processing API Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-018r2", + "@id": "http://www.opengis.net/def/docs/05-015", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-08-27" + "@value": "2005-01-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Fitch" + "@value": "Barry Schlesinger" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -47224,27 +46065,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=50166" + "@id": "https://portal.ogc.org/files/?artifact_id=8826" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Surface Water Interoperability Experiment FINAL REPORT " + "@value": "05-015" }, { "@language": "en", - "@value": "12-018r2" + "@value": "Imagery Metadata" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report describes the methods, results, issues and recommendations generated by the Surface Water Interoperability Experiment (SW IE), carried out as an activity of the OGC Hydrology Domain Working Group (HDWG). The SW IE was designed to advance the development of WaterML 2.0 and test its use with various OGC service standards (SOS, WFS, WMS and CSW). A secondary aim was to contribute to the development of a hydrology domain feature model and vocabularies, which are essential for interoperability in the hydrology domain, although these are not the main focus for the IE. " + "@value": "Special XML schemas have been created for individual data sets, based on ISO 19115 and a general schema for the RSE. However, a generalized metadata XML schema should be available where possible; it should not be necessary to create special schemas for each data set. ISO 19139 can serve as such a general XML implementation specification for 19115. This implementation needs to be tested in practice. In addition, the new ISO standards are incorporating much, if not all, of the metadata not in 19115 that the RSE contain. XML schemas for these metadata need to be developed that are based upon the abstract model in the ISO standards. All of these implementations need to be tested in practice. This Report describes such tests and the results. It also describes to what extent metadata on which the test metadata are based are supported by 19139, to what extent they are supported by metadata specified in the new ISO standards or the RSE, and to what extent new metadata elements are needed. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47255,35 +46096,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-018r2" + "@value": "05-015" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Surface Water Interoperability Experiment FINAL REPORT " + "@value": "Imagery Metadata" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-073r2", + "@id": "http://www.opengis.net/def/docs/19-018", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-09-12" + "@value": "2020-02-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jessica Cook, Raj Singh" + "@value": "Martin Klopfer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -47293,27 +46134,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=29426" + "@id": "https://docs.ogc.org/per/19-018.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-073r2" + "@value": "19-018" }, { "@language": "en", - "@value": "Summary of the OGC Web Services, Phase 5 (OWS-5) Interoperability Testbed" + "@value": "OGC Testbed-15: Open Portrayal Framework Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Web Services, Phase 5 (OWS-5) Testbed was an initiative of the OGC Interoperability Program (IP). The primary focus of an IP activity is to collaboratively extend and demonstrate OGC‘s baseline for geospatial interoperability." + "@value": "This Engineering Report (ER) describes the OGC Testbed-15 Open Portrayal Framework (OPF) Thread requirements, scenario, high-level architecture, and solutions. Main topics addressed in the OPF Thread include style changing and sharing, converting style encodings, client- / server-side rendering of vector- and raster data and data provision in denied, disrupted, intermittent, and limited bandwidth (DDIL) infrastructure situations. The work in the OPF Thread was focused on an OGC Application Programming Interface (API) oriented approach." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47324,30 +46165,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-073r2" + "@value": "19-018" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Summary of the OGC Web Services, Phase 5 (OWS-5) Interoperability Testbed" + "@value": "OGC Testbed-15: Open Portrayal Framework Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-038r1", + "@id": "http://www.opengis.net/def/docs/11-093r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-08-14" + "@value": "2011-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -47362,17 +46203,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34099" + "@id": "https://portal.ogc.org/files/?artifact_id=46242" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-6 GML Profile Validation Tool ER" + "@value": "OWS-8 Aviation Architecture Engineering Report" }, { "@language": "en", - "@value": "09-038r1" + "@value": "11-093r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -47382,7 +46223,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document outlines an approach for validating data accessed from a Web Feature Service. Two types of validation are supported:\r\n•\tXML Schema validation against the GML application schema\r\n•\tValidation of additional constraints encoded in Schematron\r\nThis report describes the validation tool, the types of constraints that have been tested and documents the results.\r\n" + "@value": "This OGC® document describes the architecture implemented in the OWS-8 Aviation thread, including general workflows. The document contains a summary description of the various components within the architecture. An introduction to the Access Control System is provided. Furthermore, the document describes relevant aspects of handling events and notifications. Lessons learned – for example regarding the AIXM Temporality Model – as well as scenarios and accomplishments are documented as well." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47393,30 +46234,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-038r1" + "@value": "11-093r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 GML Profile Validation Tool ER" + "@value": "OWS-8 Aviation Architecture Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-057", + "@id": "http://www.opengis.net/def/docs/14-017", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-03-26" + "@value": "2014-04-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Bart De Lathouwer, Peter Cotroneo, Paul Lacey" + "@value": "Gobe Hobona, Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -47431,17 +46272,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=61057" + "@id": "https://portal.ogc.org/files/?artifact_id=57334" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-057" + "@value": "Testbed 10 OWS Context in NIEM Engineering Report" }, { "@language": "en", - "@value": "UK Interoperability Assessment Plugfest (UKIAP) Engineering Report " + "@value": "14-017" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -47451,7 +46292,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Open Geospatial Consortium (OGC), the UK Ordnance Survey, AGI and Dstl conducted a first of a series of events called the United Kingdom Interoperability Assessment Plugfest (UKIAP) 2014. The purpose of UKIAP 2014 is to advance the interoperability of geospatial products and services based on OGC standards within the UK geospatial information (GI) community. The results of the Plugfest will allow Ordnance Survey to provide best practice guidance to those who want to consume or implement geospatial web services or products based on OGC standards. UKIAP 2014 is open to open- and closed source vendors and to all GI organizations in the UK to involve as many participants in the initiative as possible." + "@value": "This Engineering Report was prepared as a deliverable for OGC Testbed 10, an initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Open Mobility thread within the testbed.\r\nThe Engineering Report describes and evaluates options for integrating OWS Context documents in requests for information based on the National Information Exchange Model (NIEM).\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47462,30 +46303,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-057" + "@value": "14-017" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® and Ordnance Survey - UK Interoperability Assessment Plugfest (UKIAP) Engineering Report " + "@value": "OGC® Testbed 10 OWS Context in NIEM Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-064r3", + "@id": "http://www.opengis.net/def/docs/16-064r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-11-23" + "@value": "2016-08-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele, Reinhard Erstling" + "@value": "Detlev Wagner, Hugo Ledoux" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -47500,17 +46341,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46324" + "@id": "https://portal.ogc.org/files/?artifact_id=68821" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-064r3" + "@value": "16-064r1" }, { "@language": "en", - "@value": "OWS-8 CCI Schema Automation Engineering Report" + "@value": "CityGML Quality Interoperability Experiment" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -47520,7 +46361,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document specifies improvements to the processing of information represented in or referenced from an application schema in UML to create derived, implementation level resources, in particular:\r\n•\tXML Schema documents to represent types and their properties\r\n•\tSchematron schema documents to represent constraints\r\n•\tXSLT-Stylesheets to create KML instances of features\r\nThe documented improvements have been specified, implemented in the ShapeChange tool and tested in the context of schemas developed as part of the NGA's Topographic Data Store (TDS) schemas.\r\nThe work is a continuation of the work documented in OGC® document 10-088r2, the OWS-7 Schema Automation Engineering Report. \r\n" + "@value": "This OGC Engineering Report specifies the results and findings of the CityGML Quality\r\nInteroperability Experiment. Guidelines were developed for the following concepts:\r\n􀀀 Definition of data quality;\r\n􀀀 Data quality requirements and their specification;\r\n􀀀 Quality checking process of CityGML data; and\r\n􀀀 Description of validation results.\r\nThe desired outcomes of this Interoperability Experiment are to improve the\r\ninteroperability of CityGML data by removing some ambiguities from the current\r\nstandard and formally defining data quality requirements for a general CityGML data\r\nspecification. Further, the results of this work provides to the community (organizations\r\ninvested in capturing, procuring, or utilizing CityGML data) recommended\r\nimplementation guidance for 3D data and a suite of essential quality checking tools to\r\ncarry out quality assurance on CityGML data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47531,35 +46372,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-064r3" + "@value": "16-064r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 CCI Schema Automation Engineering Report" + "@value": "OGC® CityGML Quality Interoperability Experiment" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-044r2", + "@id": "http://www.opengis.net/def/docs/23-056", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-06-15" + "@value": "2024-01-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Bobbitt" + "@value": "Song WU, Mahmoud SAKR" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -47569,27 +46410,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1050" + "@id": "https://docs.ogc.org/dp/23-056.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Units of Measure and Quantity Datatypes" + "@value": "Mobility Data Science Discussion Paper" }, { "@language": "en", - "@value": "01-044r2" + "@value": "23-056" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Common semantic for units of measurement to be used across all OGC specifications." + "@value": "Almost every activity in our modern life leaves a digital trace, typically including location and time. Either captured by a sensor, manually input, or extracted from a social media post, the increase in the volume, variety, and velocity of spatiotemporal data is unprecedented. The ability to manage and analyze this data is important for many application domains, including smart cities, health, transportation, agriculture, sports, biodiversity, et cetera. It is critical to not only effectively manage and analyze the data but also to uphold privacy and ethical considerations. Since the civilian use of GPS was allowed in 1980, followed by the technological advances in other location tracking systems – wifi, RFID, bluetooth, etc., it is becoming more and more easy to track moving objects. The Mobility Data Science Summit was an opportunity to discuss the challenges of managing this data and making sense of it, with a focus on the tooling and standardization requirements." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47600,35 +46441,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-044r2" + "@value": "23-056" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Units of Measure and Quantity Datatypes" + "@value": "Mobility Data Science Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-090r1", + "@id": "http://www.opengis.net/def/docs/16-034", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-04-17" + "@value": "2017-03-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ki-Joune Li, Sung-Hwan Kim, Yong-Bok Choi" + "@value": "Simon Jirka, Arne de Wall, Christoph Stasch" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -47638,27 +46479,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=92039" + "@id": "https://docs.ogc.org/per/16-034.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "An Experiment to Link Geo-Referenced Multimedia and CityGML Features" + "@value": "Testbed-12 LiDAR Streaming Engineering Report" }, { "@language": "en", - "@value": "19-090r1" + "@value": "16-034" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "In this paper, we present an experiment on linking geo-referenced images and videos with CityGML objects. Data models are proposed with XML schema from two viewpoints: one for linking features in 2D images or videos with 3D CityGML objects and the other for camera FoV (Field of View). In order to validate the proposed data models, we developed an authoring tool for building XML documents to link geo-referenced images and videos with CityGML objects and a web environment for processing queries based on the linking data." + "@value": "This Engineering Report describes how developments of the Community Sensor Model Working Group (CSMW) can be harmonized with the latest SWE specifications and developments in order to support streaming of LiDAR data with SWE technologies. The report will therefore provide an overview on both initiatives and then describe different options how to integrate LiDAR data streams and SWE technologies. In particular, the ER will consider the results of the activities SOS Compression (LiDAR) Server (A012) and LiDAR Streaming Client (A010) and infer recommendations for future developments." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47669,35 +46510,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-090r1" + "@value": "16-034" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "An Experiment to Link Geo-Referenced Multimedia and CityGML Features" + "@value": "Testbed-12 LiDAR Streaming Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-104r5", + "@id": "http://www.opengis.net/def/docs/04-086", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-08-01" + "@value": "2004-02-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthew Purss" + "@value": "Jeff Harrison,A.J. Maren,Jeff Stohlman,Mike Meyer,Glenn Pruitt,John Clink,Hans Polzer,Mark Schiffner" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -47707,27 +46548,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/as/15-104r5/15-104r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=7563" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 21 - Discrete Global Grid Systems Abstract Specification" + "@value": "EA-SIG Discovery White Paper" }, { "@language": "en", - "@value": "15-104r5" + "@value": "04-086" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the core Abstract Specification and extension mechanisms for Discrete Global Grid Systems (DGGS). A DGGS is a spatial reference system that uses a hierarchical tessellation of cells to partition and address the globe. DGGS are characterized by the properties of their cell structure, geo-encoding, quantization strategy and associated mathematical functions.The OGC DGGS Abstract Specification supports the specification of standardized DGGS infrastructures that enable the integrated analysis of very large, multi-source, multi-resolution, multi-dimensional, distributed geospatial data. Interoperability between OGC DGGS implementations is anticipated through implementation standards, and extension interface encodings of OGC Web Services." + "@value": "*RETIRED* This document describes the role of Discovery Services in the net-centric enterprise. The network centric enterprise is an environment with an almost infinite variety of resources. In this rich environment, suitable resources can be found to support almost any operational need. The problem, however, is finding the appropriate resources when they are needed. Discovery services address this problem." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47738,75 +46579,104 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-104r5" + "@value": "04-086" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 21 - Discrete Global Grid Systems Abstract Specification" + "@value": "EA-SIG Discovery White Paper" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/sap/collection", + "@id": "http://www.opengis.net/def/docs/14-001", "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" + "http://www.w3.org/2004/02/skos/core#Concept" ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "http://purl.org/dc/terms/created": [ { - "@value": "Documents of type Specification Application Profile - Approved" + "@type": "xsd:date", + "@value": "2014-07-14" } ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "http://purl.org/dc/terms/creator": [ { - "@value": "Documents of type Specification Application Profile - Approved" + "@value": "Joan Masó, Guillem Closa Yolanda Gil and Benjamin Proß" } ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs" + "@id": "http://www.opengis.net/def/doc-type/per" } ], - "http://www.w3.org/2004/02/skos/core#member": [ + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/01-009a" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/06-080r4" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=58967" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/09-146r2" + "@language": "en", + "@value": "Testbed 10 Provenance Engineering Report" }, { - "@id": "http://www.opengis.net/def/docs/07-045" + "@language": "en", + "@value": "14-001" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ + { + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "The provenance activities reported in this document were part of the OGC Testbed 10\r\nCross Community Interoperability (CCI) thread. This OGC® document gives guidelines\r\nfor the capture and documentation of provenance information at dataset, feature and\r\nattribute level. It only considers vector features (mainly, points and lines) and does not\r\nelaborate on the coverage data model (so it does not talk about provenance of raster\r\ninformation). It proposes an approach to use the W3C PROV standard with geospatial\r\ninformation that can come from different sources and are integrated through different\r\nprocessing steps. It also reviews the applicability of ISO19115 and ISO19115-2 lineage." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ + { + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "14-001" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type Specification Application Profile - Approved" + "@language": "en", + "@value": "OGC® Testbed 10 Provenance Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-087r4", + "@id": "http://www.opengis.net/def/docs/11-163", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-10-11" + "@value": "2013-01-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Lorenzo Bigagli, StefanoNativi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -47816,27 +46686,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=17038" + "@id": "https://portal.ogc.org/files/?artifact_id=46702" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Observations and Measurements" + "@value": "NetCDF Uncertainty Conventions " }, { "@language": "en", - "@value": "05-087r4" + "@value": "11-163" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The general models and XML encodings for observations and measurements, including but not restricted to those using sensors." + "@value": "This Discussion Paperproposes a set of conventions for managing uncertainty information within the netCDF3 data model and format: the NetCDF Uncertainty Conventions (NetCDF-U)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47847,35 +46717,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-087r4" + "@value": "11-163" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Observations and Measurements" + "@value": "NetCDF Uncertainty Conventions " } ] }, { - "@id": "http://www.opengis.net/def/docs/17-011r2", + "@id": "http://www.opengis.net/def/docs/02-009", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-18" + "@value": "2002-01-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Alex Robin" + "@value": "Ron Lake" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -47885,27 +46755,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/17-011r2/17-011r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1108" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-011r2" + "@value": "Geography Markup Language" }, { "@language": "en", - "@value": "JSON Encoding Rules SWE Common / SensorML" + "@value": "02-009" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes new JavaScript Object Notation (JSON) encodings for the Sensor Web Enablement (SWE) Common Data Model and the Sensor Model Language (SensorML). Rather than creating new JSON schemas, this document defines encoding rules that allow auto-generation of JSON instances that conform to the Unified Modeling Language (UML) models. Alternatively, the mappings given in the second part of the document can be used to convert bi-directionally between XML and JSON representations.\r\n\r\n" + "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47916,35 +46786,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-011r2" + "@value": "02-009" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "JSON Encoding Rules SWE Common / SensorML" + "@value": "Geography Markup Language" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-117r1", + "@id": "http://www.opengis.net/def/docs/99-054", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-12-06" + "@value": "1999-06-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ryosuke Shibasaki" + "@value": "Peter Ladstaetter" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -47954,27 +46824,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51623" + "@id": "https://portal.ogc.org/files/?artifact_id=834" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-117r1" + "@value": "Simple Features Implementation Specification for CORBA" }, { "@language": "en", - "@value": "OGC Standard for Moving Features; Requirements" + "@value": "99-054" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Applications using moving feature data, typically on vehicles and pedestrians, have\r\nrecently been rapidly increasing. Innovative applications are expected to require the\r\noverlay and integration of moving feature data from different sources to create more\r\nsocial and business values. Efforts in this direction should be encouraged by ensuring\r\nsmoother data exchange because handling and integrating moving feature data will\r\nbroaden the market for geo-spatial information. This discussion paper provides an\r\noverview of some actual and potential geo-spatial applications using moving feature data\r\nand the existing international standards or specifications on moving feature data handling.\r\nIt also summarizes the requirements set on the standards for moving feature data, and\r\nfinally proposes the development of a new OGC standard for moving features." + "@value": "The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -47985,43 +46855,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-117r1" + "@value": "99-054" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Standard for Moving Features; Requirements" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/can", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/06-050r3" + "@value": "OpenGIS Simple Features Implementation Specification for CORBA" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-010r4", + "@id": "http://www.opengis.net/def/docs/19-072", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-01-28" + "@value": "2023-03-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Charles Heazel" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -48031,27 +46893,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=66905" + "@id": "https://docs.ogc.org/is/19-072/19-072.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-010r4" + "@value": "19-072" }, { "@language": "en", - "@value": "Testbed-11 WFS-T Information Exchange Architecture" + "@value": "OGC API - Common - Part 1: Core" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document presents an assessment of the conformance level, with respect to the WFS standard (OGC 09-025r2), of the web feature servers used in the OGC Testbed-11. Each server is accessed to determine if it conforms to the minimum requirements of the WFS standard. Each server is further accessed to determine whether the server offers additional, upcoming and complimentary capabilities just as support for the WFS REST API and GeoJSON.\r\nThis document offers recommendations to aid implementers of the WFS standard (OGC 09-025r2).\r\nThis document presents options available to WFS implementers for achieving interoperability between WFS clients and server at the schemas level.\r\nThis document includes a survey of available WFS clients and an assessment of their capabilities.\r\nThis document reviews tools and standards, such as the GeoSynchronization Service (OGC 10-069r3), that are complimentary components that may be used with a WFS to address requirements such as verification and notification, data and access security, exception handling and system hardening.\r\nFinally, this document includes a FAQ composed of questions raised during the OGC Testbed-11.\r\n" + "@value": "The OGC has extended its suite of Standards to include Resource Oriented Architectures and Web APIs. In the course of developing these Standards, some practices proved to be common across multiple OGC Web API Standards. These common practices are documented in the OGC API — Common Standard. The OGC API - Common Standard is a multi-part standard that specifies reusable building-blocks that can be used in the construction of OGC API Standards. This document presents Part 1, the Core, of the OGC API – Common Standard. Standards developers will use these building-blocks in the construction of other OGC Standards that relate to Web APIs. The result is a modular suite of coherent API standards which can be adapted by a system designer for the unique requirements of their system.\r\n\r\nThe purpose of the OGC API — Common — Part 1: Core Standard (API-Core) is to define those fundamental building blocks and requirements which are applicable to all OGC Web API Standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48062,35 +46924,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-010r4" + "@value": "19-072" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed-11 WFS-T Information Exchange Architecture" + "@value": "OGC API - Common - Part 1: Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-024r2", + "@id": "http://www.opengis.net/def/docs/12-063r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-08-19" + "@value": "2015-05-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff" + "@value": "Roger Lott" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -48100,27 +46962,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=63794" + "@id": "https://docs.ogc.org/is/12-063r5/12-063r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 11 Aviation - Guidance on Using Semantics of Business Vocabulary and Business Rules (SBVR) Engineering Report" + "@value": "Well known text representation of coordinate reference systems" }, { "@language": "en", - "@value": "15-024r2" + "@value": "12-063r5" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a deliverable of the OGC Testbed 11 . It describes the results of developing a tool to automatically derive Schematron code from SBVR constraints. It also documents a vocabulary with a profile of core geospatial terms and concepts, which can be used to express geospatial constraints in business rules." + "@value": "This Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2007 and ISO 19111-2:2009. It extends the earlier WKT to allow for the description of coordinate operations. This International Standard defines the structure and content of well-known text strings. It does not prescribe how implementations should read or write these strings.\r\nThe jointly developed draft has also been submitted by ISO TC211 for publication as an International Standard document. The version incorporates comments made during both the OGC Public Comment Period as well as the ISO ballot for DIS (ISO TC211 document N3750). \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48131,35 +46993,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-024r2" + "@value": "12-063r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 11 Aviation - Guidance on Using Semantics of Business Vocabulary and Business Rules (SBVR) Engineering Report" + "@value": "Geographic information — Well known text representation of coordinate reference systems" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-182r1", + "@id": "http://www.opengis.net/def/docs/01-047r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-02-16" + "@value": "2001-06-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Josh Lieberman" + "@value": "Jeff de La Beaujardiere" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -48169,27 +47031,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=36889" + "@id": "https://portal.ogc.org/files/?artifact_id=1058" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-182r1" + "@value": "Web Map Service" }, { "@language": "en", - "@value": "End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2" + "@value": "01-047r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Architecture Implementation Pilot, Phase 2 Engineering Report (AIP-2 ER) describes the practice of deploying, documenting, and registering contributed resources from the point of view of classes of GEOSS users who rely on GEOSS to support discovery and access to those resources. It emphasizes two paradigms for the GEOSS Common Infrastructure: 1) Service-oriented infrastructure for development of service-based community applications by technically advanced users; and 2) Content-oriented search facility and Web-based access mechanisms for end-users with a range of technical skills and domain knowledge. End-to-end here refers to the bidirectional connection between desired discovery practices and goals on the user end; and the required resource interfaces and documentation on the provider end." + "@value": "Provides four protocols (GetCapabilities, GetMap, GetFeatureInfo and DescribeLayer) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48200,35 +47062,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-182r1" + "@value": "01-047r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2" + "@value": "Web Map Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-012r1", + "@id": "http://www.opengis.net/def/docs/12-128r18", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-12-22" + "@value": "2021-11-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ki-Joune Li, Hyung-Gyu Ryu, Hak-Cheol Kim, Jun Hee Lee, Joo-Ho Lee" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -48238,27 +47100,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=68824" + "@id": "https://www.geopackage.org/spec131/index.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Comparing CityGML and IndoorGML based on a use case at Lotte World Mall" + "@value": "12-128r18" }, { "@language": "en", - "@value": "16-012r1" + "@value": "GeoPackage Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Discussion Paper provides a comparison between the OGC CityGML and IndoorGML standards. The goals and approaches of these two standards are different and they can be used in a complementary way. This discussion paper aims to compare the strengths and weakness of the standards, and explain how to integrate the standards to make useful applications. These comparative experiments are based on a real site: a shopping mall at Lotte World Mall in Seoul, South Korea." + "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48269,35 +47131,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-012r1" + "@value": "12-128r18" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Comparing CityGML and IndoorGML based on a use case at Lotte World Mall" + "@value": "OGC® GeoPackage Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-092r2", + "@id": "http://www.opengis.net/def/docs/04-084r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-18" + "@value": "2020-08-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Brackin" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -48307,27 +47169,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-092r2.html" + "@id": "https://docs.ogc.org/as/04-084r4/04-084r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-092r2" + "@value": "04-084r4" }, { "@language": "en", - "@value": "Incident Management Information Sharing (IMIS) Internet of Things (IoT) Extension Engineering Report" + "@value": "Topic 00 - Overview" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives.\r\n\r\n· Apply Open Geospatial Consortium (OGC) principles and practices for collaborative development to existing standards and technology in order to prototype an IoT approach to sensor use for incident management.\r\n\r\n· Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability.\r\n\r\n· Development of profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability.\r\n\r\n· Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario.\r\n\r\nThese principles continued through the IoT Pilot Extension, with additional objectives of:\r\n\r\n· Integration into the existing Next Generation First Responder (NGFR) Apex development program process as part of Spiral 1;\r\n\r\n· Defining steps to begin the integration of existing incident management infrastructure, e.g., pulling in National Institute of Emergency Management (NIEM) message feeds; and\r\n\r\n· Demonstration and experimentation in a ‘realistic’ incident environment using two physically separate sites–an incident site within an active first responder training facility (Fairfax County Lorton site), and a command center (DHS S&T Vermont Avenue facility).\r\n\r\nThe initial Pilot activity has been documented in three OGC public engineering reports. The present report describes and documents the additional activities and innovations undertaken in the Extension." + "@value": "This document (Topic 0) is an overview of the OGC Abstract Specification." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48338,35 +47200,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-092r2" + "@value": "04-084r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Incident Management Information Sharing (IMIS) Internet of Things (IoT) Extension Engineering Report" + "@value": "Topic 0 - Overview" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-047r2", + "@id": "http://www.opengis.net/def/docs/19-027r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-06-21" + "@value": "2019-12-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff de La Beaujardiere" + "@value": "Sam Meek" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -48376,27 +47238,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1058" + "@id": "https://docs.ogc.org/per/19-027r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "01-047r2" + "@value": "19-027r2" }, { "@language": "en", - "@value": "Web Map Service" + "@value": "OGC Testbed-15: Machine Learning Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Provides four protocols (GetCapabilities, GetMap, GetFeatureInfo and DescribeLayer) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. " + "@value": "The Machine Learning (ML) Engineering Report (ER) documents the results of the ML thread in OGC Testbed-15. This thread explores the ability of ML to interact with and use OGC web standards in the context of natural resources applications. The thread includes five scenarios utilizing seven ML models in a solution architecture that includes implementations of the OGC Web Processing Service (WPS), Web Feature Service (WFS) and Catalogue Service for the Web (CSW) standards. This ER includes thorough investigation and documentation of the experiences of the thread participants." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48407,29 +47269,65 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-047r2" + "@value": "19-027r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Map Service" + "@value": "OGC Testbed-15: Machine Learning Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/is-draft/collection", + "@id": "http://www.opengis.net/def/docs/07-158", "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" + "http://www.w3.org/2004/02/skos/core#Concept" ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "http://purl.org/dc/terms/created": [ { - "@value": "Documents of type Implementation Specification - Draft" + "@type": "xsd:date", + "@value": "2008-01-02" + } + ], + "http://purl.org/dc/terms/creator": [ + { + "@value": "R" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + { + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ + { + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + { + "@id": "https://portal.ogc.org/files/?artifact_id=25280" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ + { + "@language": "en", + "@value": "Wrapping OGC HTTP-GET/POST Services with SOAP" + }, + { + "@language": "en", + "@value": "07-158" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ + { + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Documents of type Implementation Specification - Draft" + "@value": "Discussion of how to wrap OGC HTTP-GET/POST Services with SOAP" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48437,36 +47335,38 @@ "@id": "http://www.opengis.net/def/docs" } ], - "http://www.w3.org/2004/02/skos/core#member": [ + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/21-056r10" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "07-158" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type Implementation Specification - Draft" + "@language": "en", + "@value": "Wrapping OGC HTTP-GET/POST Services with SOAP" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-011r4", + "@id": "http://www.opengis.net/def/docs/11-139r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-19" + "@value": "2011-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "David Arctur" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -48476,27 +47376,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/16-011r4" + "@id": "https://portal.ogc.org/files/?artifact_id=47018" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-011r4" + "@value": "Summary of the OGC Web Services, Phase 8 (OWS-8) Interoperability Testbed" }, { "@language": "en", - "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance" + "@value": "11-139r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames. \r\nIn previous versions of the CDB standard, this CDB volume was Appendix K in CDB Version 3.2 as submitted to the OGC.\r\n" + "@value": "The OGC Web Services, Phase 8 (OWS-8) Testbed was an initiative of OGC’s Interoperability Program to\r\ncollaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. The majority of work for\r\nOWS-8 was conducted from March to September 2011." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48507,35 +47407,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-011r4" + "@value": "11-139r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance" + "@value": "Summary of the OGC Web Services, Phase 8 (OWS-8) Interoperability Testbed" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-017", + "@id": "http://www.opengis.net/def/docs/11-035r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-05-12" + "@value": "2013-03-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus, Jan Herrmann" + "@value": "Frédéric Houbie, Steven Smolders" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -48545,27 +47445,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=42734" + "@id": "https://portal.ogc.org/files/?artifact_id=53276" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geospatial eXtensible Access Control Markup Language (GeoXACML) Version 1 Corrigendum" + "@value": "EO Product Collection, Service and Sensor Discovery using the CS-W ebRIM Catalogue" }, { "@language": "en", - "@value": "11-017" + "@value": "11-035r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Geospatial eXtensible Access Control Markup Language Encoding Standard (GeoXACML) defines a geospatial extension to the OASIS standard “eXtensible Access Control Markup Language (XACML)” [www.oasis-open.org/committees/xacml/]. This extension incorporates spatial data types and spatial authorization decision functions based on the OGC Simple Features[http://www.opengeospatial.org/standards/sfa] and GML[http://www.opengeospatial.org/standards/gml] standards. GeoXACML is a policy language that supports the declaration and enforcement of access rights across jurisdictions and can be used to implement interoperable access control systems for geospatial applications such as Spatial Data Infrastructures. GeoXACML is not designed to be a rights expression language and is therefore not an extension of the OGC GeoDRM Reference Model (Topic 18 in the OpenGIS® Abstract Specification [http://www.opengeospatial.org/standards/as]). " + "@value": "This is an OGC Best Practice document describing the relations that exist between several metadata conceptual models (EO Product, EO Product Collections, Sensors and Services). The specification of the linking between different artifacts is important for the process of cataloguing and discovering those artifacts." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48576,35 +47476,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-017" + "@value": "11-035r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geospatial eXtensible Access Control Markup Language (GeoXACML) Version 1 Corrigendum" + "@value": "EO Product Collection, Service and Sensor Discovery using the CS-W ebRIM Catalogue" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-054r1", + "@id": "http://www.opengis.net/def/docs/17-043", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-19" + "@value": "2018-01-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Kyoung-Sook Kim, Jiyeong Lee" + "@value": "Nuno Oliveira" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -48614,27 +47514,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/20-054r1.html" + "@id": "https://docs.ogc.org/per/17-043.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "An Extension Model to attach Points of Interest into IndoorGML" + "@value": "Testbed-13: Executable Test Suites and Reference Implementations for NSG WMTS 1.0 and WFS 2.0 Profiles with Extension" }, { "@language": "en", - "@value": "20-054r1" + "@value": "17-043" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The scope of this discussion paper is to investigate types of Point of Interest (POI) data in indoor space and propose a conceptual model to harmonize the POI information with the IndoorGML core and navigation modules. In particular, this document focuses on the management of spatial (and non-spatial) history of indoor POI features. The paper covers the following scope:\r\n\r\nPoints of Interest Feature Types;\r\n\r\nA Conceptual model to extend IndoorGML schema for indoor POI; and\r\n\r\nUse cases in home navigation and hospital facility management." + "@value": "This Engineering Report (ER) describes the development of the compliance tests and implementation in GeoServer of the Web Feature Service (WFS) 2.0 and Web Map Tile Service (WMTS) 1.0 National System for Geospatial Intelligence (NSG) profiles. The NSG of the United States (US) National Geospatial Intelligence Agency (NGA) is the combination of technologies, policies, capabilities, doctrine, activities, people, data and communities needed to produce geospatial intelligence (GEOINT) in an integrated, multi-intelligence, multi-domain environment. The work can be grouped into four main topics:\r\n\r\ncritical review of the NSG profiles for WFS 2.0 and WMTS 1.0\r\n\r\nimplementation of the profiles in GeoServer\r\n\r\nvalidation of the implementation using OGC Compliance tests and tools\r\n\r\nlessons learn during the implementation of these profiles and their validation\r\n\r\nBoth NSG profiles are Class 2 profiles. WMTS profiles OGC WMTS 1.0. WFS profiles the DGIWG Profile of OGC WFS 2.0. The first topic provides a review of these profiles along with a description of the main extensions and restrictions introduced by them.\r\n\r\nThe second topic covers the implementation of the NSG profiles in GeoServer. It describes the software architecture and technical decisions, along with the deployment and configuration of the server.\r\n\r\nThe third topic covers the validation process of the implementation using OGC validation (sometimes referred to as CITE) tests and tools. It also covers how the tests can be run and how to configure GeoServer for these tests.\r\n\r\nThe last topic contains an evaluation of the work, reached goals, lessons learned and the best practices that can be applied in future work." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48645,35 +47545,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-054r1" + "@value": "17-043" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "An Extension Model to attach Points of Interest into IndoorGML" + "@value": "OGC Testbed-13: Executable Test Suites and Reference Implementations for NSG WMTS 1.0 and WFS 2.0 Profiles with Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-004r1", + "@id": "http://www.opengis.net/def/docs/19-020r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-07-31" + "@value": "2019-12-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "Yves Coene" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -48683,27 +47583,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/wp/18-004r1/18-004r1.html" + "@id": "https://docs.ogc.org/per/19-020r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "The Role of Geospatial in Edge-Fog-Cloud Computing - An OGC White Paper" + "@value": "OGC Testbed-15: Catalogue and Discovery Engineering Report" }, { "@language": "en", - "@value": "18-004r1" + "@value": "19-020r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "“The cloud is dead – long live the cloud!” so begins an IEC White paper on Edge Intelligence.[1] The IEC White Paper continues that “Driven by the internet of things (IoT), a new computing model – edge-cloud computing – is currently evolving, which involves extending data processing to the edge of a network in addition to computing in a cloud or a central data centre. Edge-Fog-Cloud computing models operate both on premise and in public and private clouds, including via devices, base stations, edge servers, micro data centres and networks.” " + "@value": "This OGC Testbed-15 Engineering Report (ER) describes the results of the Earth Observation (EO) Process and Application (EOPAD) Task in the Cloud Processing and Portrayal (CPP) thread of OGC Testbed-15. The ER presents the data model and service interface of the catalogue service allowing for discovery of EO applications and related processing services for subsequent deployment and/or invocation in a distributed environment.\r\n\r\nThe ER also provides the architectural and implementation details of the software components that were developed as part of the activity and which interact through the described data model. These software components include catalogue clients, catalogue servers and transactional Web Processing Service (WPS-T) servers." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48714,30 +47614,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-004r1" + "@value": "19-020r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "The Role of Geospatial in Edge-Fog-Cloud Computing - An OGC White Paper" + "@value": "OGC Testbed-15: Catalogue and Discovery Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-055r1", + "@id": "http://www.opengis.net/def/docs/16-084", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-10-09" + "@value": "2016-08-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside, Markus U. M" + "@value": "Giuseppe Conti, Fabio Malabocchia, Ki-Joune Li, George Percivall, Kirk Burroughs, Stuart Strickland" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -48752,17 +47652,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=24314" + "@id": "https://portal.ogc.org/files/?artifact_id=68604" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-055r1" + "@value": "16-084" }, { "@language": "en", - "@value": "Web Coordinate Transformation Service" + "@value": "OGC Benefits of Indoor Location - Use Case Survey of Lessons Learned and Expectations " } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -48772,7 +47672,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion Paper describes an interface specification for a web coordinate transformation service that now builds on version 1.1 of the OWS Common Specification [OGC 06-121r3]. All versions of this document specify an " + "@value": "Indoor location technologies are enjoying and increasing market success. Technologies in the market have achieved maturity and have become a key driver for innovation and business activities in several value added scenarios, e.g. e-government services, eHealth, personal mobility, logistics, mobility, facility management, retail, to name but a few. This paper collects the results of a survey on the benefits of indoor location, which was jointly prepared and launched by OGC – the Open Geospatial Consortium, InLocation Alliance and i-locate project at the beginning of 2016. Overall, 153 survey responses were received from 33 countries. Responses were categorized in two areas: Client Organizations and Technology suppliers. The goal of the initiative was to acquire a broad view of the requirements and use cases emerging from the wider industrial and user community, beyond the memberships of the various organizations, in order to capture trends, challenges and opportunities, as well as trends and barriers to widespread use of indoor location technologies. This paper does not represent a view of the membership involved in the different organizations; instead, it provides the opportunity to capture recommendations of relevance for the industrial and standardization community these organizations represent. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48783,35 +47683,69 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-055r1" + "@value": "16-084" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Coordinate Transformation Service" + "@value": "OGC Benefits of Indoor Location - Use Case Survey of Lessons Learned and Expectations " } ] }, { - "@id": "http://www.opengis.net/def/docs/09-072", + "@id": "http://www.opengis.net/def/doc-type/d-profile/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Specification Profile - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Specification Profile - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/10-100r2" + }, + { + "@id": "http://www.opengis.net/def/docs/06-049r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Specification Profile - deprecated " + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/18-005r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-08-05" + "@value": "2021-07-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "James Ressler" + "@value": "Roger Lott" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -48821,27 +47755,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34146" + "@id": "https://docs.ogc.org/as/18-005r5/18-005r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-072" + "@value": "Topic 02 - Referencing by coordinates Corrigendum" }, { "@language": "en", - "@value": "OWS-6 CITE TEAM Engine Engineering Report" + "@value": "18-005r5" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document summarizes the work done on the TEAM compliance test engine and DGIWG Profile compliance test by Northrop Grumman for the CITE thread of OWS-6 in 2008-2009." + "@value": "This document is identical in normative content with the latest edition (2019) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2019]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48852,41 +47786,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-072" + "@value": "18-005r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 CITE TEAM Engine Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-profile", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/10-100r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-049r1" + "@value": "Topic 2 - Referencing by coordinates Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-054r1", + "@id": "http://www.opengis.net/def/docs/15-039", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-08-20" + "@value": "2015-08-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Max Martinez" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -48901,17 +47824,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=29406" + "@id": "https://portal.ogc.org/files/?artifact_id=63289" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-5 Considerations for the WCTS Extension of WPS" + "@value": "Envisioning a Tiled Elevation Extension for the OGC GeoPackage Encoding Standard" }, { "@language": "en", - "@value": "08-054r1" + "@value": "15-039" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -48921,7 +47844,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document details considerations for using the WPS specification to define a standard coordinate transformation service." + "@value": "The GeoPackage Standards Working Group (SWG) presents a vision for storing tiled gridded elevation data in a GeoPackage." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -48932,35 +47855,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-054r1" + "@value": "15-039" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-5 Considerations for the WCTS Extension of WPS" + "@value": "Envisioning a Tiled Elevation Extension for the OGC GeoPackage Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-188r1", + "@id": "http://www.opengis.net/def/docs/12-075", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-17" + "@value": "2012-08-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Arne Schilling, Benjamin Hagedorn, Volker Coors " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -48970,27 +47893,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20794" + "@id": "https://portal.ogc.org/files/?artifact_id=49068" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GML Encoding of Discrete Coverages (interleaved pattern)" + "@value": "3D Portrayal Interoperability Experiment FINAL REPORT " }, { "@language": "en", - "@value": "06-188r1" + "@value": "12-075" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This specification describes a GML encoding for discrete coverages. The encoding pattern is a variation from the standard GML Coverage, in that the values in the domain and range are effectively interleaved rather than represented as two blocks and encoded sequentially. " + "@value": "This document describes the results of an OGC Interoperability Experiment (IE) on the portrayal of 3D geospatial information. It contains technical details on processing 3D information in an OGC service environment as well as best practices on how to portray large data sets in urban planning scenarios, taking into account architectures and capabilities of interactive 3D graphics. Especially Web 3D Service and Web View Service, two draft standards (published as OGC discussions paper), have been in the focus of 3DPIE. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49001,35 +47924,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-188r1" + "@value": "12-075" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML Encoding of Discrete Coverages (interleaved pattern)" + "@value": "OGC 3D Portrayal Interoperability Experiment FINAL REPORT " } ] }, { - "@id": "http://www.opengis.net/def/docs/05-016", + "@id": "http://www.opengis.net/def/docs/14-002", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-05-02" + "@value": "2014-07-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Marwa Mabrouk" + "@value": "Joan Masó and Raj Singh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49039,27 +47962,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8836" + "@id": "https://portal.ogc.org/files/?artifact_id=58965" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-016" + "@value": "Testbed 10 Annotations Engineering Report" }, { "@language": "en", - "@value": "Location Service (OpenLS) Implementation Specification: Core Services" + "@value": "14-002" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Open Location Services Interface Standard (OpenLS) specifies interfaces that enable companies in the Location Based Services (LBS) value chain to “hook up” and provide their pieces of applications such as emergency response (E-911, for example), personal navigator, traffic information service, proximity service, location recall, mobile field service, travel directions, restaurant finder, corporate asset locator, concierge, routing, vector map portrayal and interaction, friend finder, and geography voice-graphics. These applications are enabled by interfaces that implement OpenLS services such as a Directory Service, Gateway Service, Geocoder Service, Presentation (Map Portrayal) Service and others.\r\n" + "@value": "This OGC Engineering Report provides guidelines for dealing with geospatial\r\nannotations in OGC standards. It proposes a generic data model and a set of mappings\r\ninto different popular encodings This OGC® document is applicable to OWS context,\r\nGMLJP2 and any other standards that can require annotations." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49070,35 +47993,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-016" + "@value": "14-002" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Location Service (OpenLS) Implementation Specification: Core Services" + "@value": "OGC® Testbed 10 Annotations Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/00-028", + "@id": "http://www.opengis.net/def/docs/20-015r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2000-04-19" + "@value": "2021-02-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Allan Doyle" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49108,27 +48031,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7196" + "@id": "https://docs.ogc.org/per/20-015r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "00-028" + "@value": "OGC Testbed-16: Machine Learning Engineering Report" }, { "@language": "en", - "@value": "Web Map Service" + "@value": "20-015r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Provides four protocols (GetCapabilities, GetMap, GetFeatureInfo and DescribeLayer) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. " + "@value": "This engineering report describes the work performed in the Machine Learning Thread of OGC’s Testbed-16 initiative.\r\n\r\nPrevious OGC testbed tasks concerned with Machine Learning (ML) concentrated on the methods and apparatus of training models to produce high quality results. The work reported in this ER, however, focuses less on the accuracy of machine models and more on how the entire machine learning processing chain from discovering training data to visualizing the results of a ML model run can be integrated into a standards-based data infrastructure specifically based on OGC interface standards.\r\n\r\nThe work performed in this thread consisted of:\r\n\r\nTraining ML models;\r\n\r\nDeploying trained ML models;\r\n\r\nMaking deployed ML models discoverable;\r\n\r\nExecuting an ML model;\r\n\r\nPublishing the results from executing a ML model;\r\n\r\nVisualizing the results from running a ML model.\r\n\r\nAt each step, the following OGC and related standards were integrated into the workflow to provide an infrastructure upon which the above activities were performed:\r\n\r\nOGC API - Features: Approved OGC Standard that provides API building blocks to create, retrieve, modify and query features on the Web.\r\n\r\nOGC API - Coverages: Draft OGC Standard that provides API building blocks to create, retrieve, modify and query coverages on the Web.\r\n\r\nOGC API - Records: Draft OGC Standard that provides API building block to create, modify and query catalogues on the Web.\r\n\r\nApplication Deployment and Execution Service: Draft OGC Standard that provides API building blocks to deploy, execute and retrieve results of processes on the Web.\r\n\r\nMapML is a specification that was published by the Maps For HTML Community Group. It extends the base HTML map element to handle the display and editing of interactive geographic maps and map data without the need of special plugins or JavaScript libraries. The Design of MapML resolves a Web Platform gap by combining map and map data semantics into a hypermedia format that is syntactically and architecturally compatible with and derived from HTML. It provides a standardized way for declarative HTML content to communicate with custom spatial server software (which currently use HTTP APIs based on multiple queries and responses). It allows map and map data semantics to be either included in HTML directly, or referred to at arbitrary URLs that describe stand-alone layers of map content, including hyper-linked annotations to further content.\r\n\r\nParticular emphasis was placed on using services based on the emerging OGC API Framework suite of API building blocks." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49139,35 +48062,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "00-028" + "@value": "20-015r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Map Service" + "@value": "OGC Testbed-16: Machine Learning Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-091r6", + "@id": "http://www.opengis.net/def/docs/08-132", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-09-16" + "@value": "2008-11-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Schut" + "@value": "Thomas Everding, Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49177,27 +48100,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=32766" + "@id": "https://portal.ogc.org/files/?artifact_id=29566" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0" + "@value": "Event Pattern Markup Language (EML)" }, { "@language": "en", - "@value": "08-091r6" + "@value": "08-132" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the details for a corrigendum for the existing OpenGIS Standard for the Web Processing Service version 1.0.0 and does not modify that standard. The current OpenGIS Implementation Standard that this document provides revision notes for is 05-007r7. " + "@value": "The Event Pattern Markup Language (EML) allows one to describe event patterns for event (stream) processing and analysis. It can be used to build multi stage filters for incoming events but also to derive higher information through combining and correlating multiple events. It can be applied on single events but is focused on handling of continuous event streams." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49208,35 +48131,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-091r6" + "@value": "08-132" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0" + "@value": "Event Pattern Markup Language (EML)" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-080r1", + "@id": "http://www.opengis.net/def/docs/16-032r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-02-05" + "@value": "2021-01-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jerome Gasperi" + "@value": "Boyan Brodaric" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49246,27 +48169,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=19094" + "@id": "https://docs.ogc.org/is/19-013/19-013.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-080r1" + "@value": "16-032r3" }, { "@language": "en", - "@value": "GML Application Schema for EO Products" + "@value": "OGC WaterML 2: Part 4 - GroundWaterML 2 (GWML2)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGCTM Catalogue Services Specification v2.0.0 (with Corrigendum) [OGC 04-021r3]" + "@value": "This standard describes a conceptual and logical model for the exchange of groundwater data, as well as a GML/XML encoding with examples." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49277,30 +48200,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-080r1" + "@value": "16-032r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML Application Schema for EO Products" + "@value": "OGC WaterML 2: Part 4 - GroundWaterML 2 (GWML2)" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-076", + "@id": "http://www.opengis.net/def/docs/16-093r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-11" + "@value": "2018-04-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jens Ingensand, Kalimar Maia" + "@value": "Steve Liang, Tania Khalafbeigi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -49315,17 +48238,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-076.html" + "@id": "https://docs.ogc.org/per/16-093r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Tiled Feature Data Conceptual Model Engineering Report" + "@value": "16-093r1" }, { "@language": "en", - "@value": "18-076" + "@value": "Incident Management Information Sharing Internet of Things Protocol Mapping Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -49335,7 +48258,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Feature data tiling, colloquially referred to as 'vector tiling', is a method that defines how large vector geospatial datasets can be systematically split into subsets or tiles [1]. Feature data tiling allows for a variety of use-cases, such as creating online maps, quickly accessing large vector data sets for geoprocessing and creating download-services. For instance, a map created from tiled feature data consists of one or more layers of vector data organized into tiles of features and rendered on the client-side using an associated style. In contrast, raster tiles are delivered as tiled images that have been rendered on the server-side.\r\n\r\nNOTE\r\nThis engineering report interchangeably uses both 'tiled feature data' and the colloquial term 'vector tiles'." + "@value": "This engineering report details Pilot experiences in connecting a variety of local communications protocols and message formats supported by low-cost sensor devices with OGC SWE Web services published globally over IP networks. It describes the Sensor Hub approach taken to support these connections and the mappings from one protocol to another required to develop integrated SWE-IoT networks." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49346,35 +48269,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-076" + "@value": "16-093r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Vector Tiles Pilot: Tiled Feature Data Conceptual Model Engineering Report" + "@value": "Incident Management Information Sharing Internet of Things Protocol Mapping Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-035r1", + "@id": "http://www.opengis.net/def/docs/10-140r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-01-12" + "@value": "2014-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jens Fitzke, Rob Atkinson" + "@value": "Peter Baumann, Stephan Meissl, Jinsongdi Yu" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49384,27 +48307,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13593" + "@id": "https://portal.ogc.org/files/?artifact_id=42722" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-035r1" + "@value": "Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile" }, { "@language": "en", - "@value": "Gazetteer Service Profile of a WFS" + "@value": "10-140r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Provides web access to an authority for place names. Returns their associated feature representations" + "@value": "The OGC Web Coverage Service (WCS) Application Profile – Earth Observation (EO-WCS), defines a profile of WCS 2.0 [OGC 09-110r4] for use on Earth Observation data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49415,35 +48338,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-035r1" + "@value": "10-140r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Gazetteer Service Profile of a WFS" + "@value": "OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-026", + "@id": "http://www.opengis.net/def/docs/06-188r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-01-17" + "@value": "2007-05-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joshua Lieberman" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49453,27 +48376,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1319" + "@id": "https://portal.ogc.org/files/?artifact_id=20794" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-026" + "@value": "GML Encoding of Discrete Coverages (interleaved pattern)" }, { "@language": "en", - "@value": "Service Information Model" + "@value": "06-188r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "SIM specifies and discusses a common information model for OGC Web Services, also known variously or in part as service capabilities or service metadata." + "@value": "This specification describes a GML encoding for discrete coverages. The encoding pattern is a variation from the standard GML Coverage, in that the values in the domain and range are effectively interleaved rather than represented as two blocks and encoded sequentially. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49484,35 +48407,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-026" + "@value": "06-188r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Service Information Model" + "@value": "GML Encoding of Discrete Coverages (interleaved pattern)" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-023r3", + "@id": "http://www.opengis.net/def/docs/05-134", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-30" + "@value": "2005-11-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Benjamin Pross" + "@value": "Keith Ryden" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49522,27 +48445,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-023r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=13228" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-023r3" + "@value": "05-134" }, { "@language": "en", - "@value": "Testbed-12 Implementing Asynchronous Services Response Engineering Report" + "@value": "Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Most of current OGC specifications define synchronous communication patterns, i.e. after sending a request to an OGC service, clients need to wait for the response. But several applications, e.g. delivery of information about events or executing complex environmental models with long runtime, need asynchronous client-server interaction pattern that do not require clients to keep the connection to the server continuously open in order to wait for responses. At the moment, there are several approaches how to add asynchronous communication to existing OGC services: One option is to use a WPS façade, as the WPS specification already defines asynchronous service responses. Another option is to add extensions to the different specifications and the third option is developed by the OGC Publish-Subscribe Working Group. This ER summarizes and compares the results from the different activities for asynchronous service responses and provides recommendations for future activities." + "@value": "This part of OpenGIS" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49553,35 +48476,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-023r3" + "@value": "05-134" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Implementing Asynchronous Services Response Engineering Report" + "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access -" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-039r2", + "@id": "http://www.opengis.net/def/docs/14-014r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-19" + "@value": "2016-06-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Aleksandar Balaban" + "@value": "Lorenzo Bigagli, Doug Nebert, Uwe Voges, Panagiotis Vretanos, Bruce Westcott" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/ts" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49591,27 +48514,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-039r2.html" + "@id": "https://docs.ogc.org/is/14-014r3/14-014r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Aviation Semantics Engineering Report" + "@value": "Catalogue Services Specification - HTTP protocol binding - Abstract Test Suite" }, { "@language": "en", - "@value": "16-039r2" + "@value": "14-014r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/ts" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report examines the role of geospatial semantic technology in the domain of civil aviation. Many aeronautical services (providing information on request or processing the data) are based on OGC Web Service specifications. A number of aeronautical services possess geospatial attributes. The aviation services follow OWS Common Service requirements but also have domain specific capabilities. Services metadata is often very relevant for service consumption, especially in the SOA environment of aviation’s System Wide Information Management (SWIM). Therefore, it shall be exposed to consumer stakeholders for either design or runtime service discovery in an efficient, standardized way.\r\n\r\nThis ER starts introducing the WSDOM service ontology developed by FAA for semantic service discovery. It proposes several extensions useful for OWS compatible, geospatial aviation services. It combines GeoSPARQL with WSDOM ontology and FAA service classification taxonomies and elaborates the interoperability between ontology based WSDOM and OWS compatible service descriptions." + "@value": "See OGC 12-176r7 -- OGC® Catalogue Services Specification - HTTP Protocol Binding." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49622,35 +48545,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-039r2" + "@value": "14-014r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Aviation Semantics Engineering Report" + "@value": "OGC® Catalogue Services Specification - HTTP protocol binding - Abstract Test Suite" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-067r2", + "@id": "http://www.opengis.net/def/docs/07-018r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-29" + "@value": "2007-08-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside, John Evans" + "@value": "Philippe M" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49660,27 +48583,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=22560" + "@id": "https://portal.ogc.org/files/?artifact_id=21465" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Service (WCS) Implementation Specification Corrigendum 1" + "@value": "Sensor Planning Service Application Profile for EO Sensors" }, { "@language": "en", - "@value": "07-067r2" + "@value": "07-018r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This version 1.1.1c1 of the Web Coverage Service (WCS) Specification supersedes previous\r\nversion 1.1.0 [OGC 06-083r8]. Technical changes from the version 1.0 include building on\r\nthe OGC Web Services Common Specification [OGC 06-121r3] and a substantially revised\r\nCapabilities schema; new schemas and syntax for operation requests (GetCoverage,\r\nDescribeCoverage); and integration with GML 3.1. The changes in WCS 1.1.1c1 from WCS\r\n1.1.0 are summarized in [OGC 07-066r2]." + "@value": "This SPS EO profile document specifies at a lower level the interfaces and parameters for requesting information describing the capabilities of a Sensor Planning Service dedicated to the EO Sensor domain, for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or cancelling such a request, and for requesting information about further OGC Web services that provide access to the data collected by the requested task." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49691,43 +48614,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-067r2" + "@value": "07-018r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Coverage Service (WCS) Implementation Specification Corrigendum 1" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/cp", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/18-095r7" + "@value": "OpenGIS Sensor Planning Service Application Profile for EO Sensors" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-006r1", + "@id": "http://www.opengis.net/def/docs/21-017r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-06-12" + "@value": "2022-02-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Marwa Mabrouk" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49737,27 +48652,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=3839" + "@id": "http://docs.ogc.org/per/21-017r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-006r1" + "@value": "OGC Features and Geometries JSON Engineering Report" }, { "@language": "en", - "@value": "Location Services (OpenLS): Core Services [Parts 1-5]" + "@value": "21-017r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform. " + "@value": "The OGC Testbed-17 Features and Geometries JSON task investigated proposals for how feature data could be encoded in JSON so that:\r\n\r\n* Different Coordinate Reference Systems (CRS) are supported and\r\n* Communities can build and formally specify profiles of the fully CRS-enabled JSON with limited sets of supported geometry types and with clear constraints for feature type definitions.\r\n\r\nGeoJSON, a standard of the Internet Engineering Task Force (IETF), was used as a starting point.\r\n\r\nThis Engineering Report (ER) captures the results and discussions, including material that was submitted to the https://github.com/opengeospatial/OGC-feat-geo-json[OGC Features and Geometries JSON Standards Working Group].\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49768,35 +48683,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-006r1" + "@value": "21-017r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Location Services (OpenLS): Core Services [Parts 1-5]" + "@value": "OGC Testbed-17: OGC Features and Geometries JSON Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-166", + "@id": "http://www.opengis.net/def/docs/18-005r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-01-30" + "@value": "2019-02-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Roger Lott" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49806,27 +48721,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=18747" + "@id": "https://docs.ogc.org/as/18-005r4/18-005r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-166" + "@value": "Topic 02 - Referencing by coordinates" }, { "@language": "en", - "@value": "A URN namespace for the Open Geospatial Consortium (OGC)" + "@value": "18-005r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": " This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC. The formal Namespace identifier (NID) is ogc.\r\n" + "@value": "This document is identical in normative content with the latest edition (2019) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2019]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49837,35 +48752,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-166" + "@value": "18-005r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "A URN namespace for the Open Geospatial Consortium (OGC)" + "@value": "Topic 2 - Referencing by coordinates" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-078", + "@id": "http://www.opengis.net/def/docs/19-065", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-04-21" + "@value": "2020-07-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Dr. Markus M" + "@value": "Steve Thompson " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49875,27 +48790,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12637" + "@id": "https://portal.ogc.org/files/?artifact_id=92038" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Styled Layer Descriptor Profile of the Web Map Service Implementation Specification" + "@value": "OpenFlight Scene Description Database Specification 16.0 Community Standard" }, { "@language": "en", - "@value": "05-078" + "@value": "19-065" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Document specifies how a Web Map Service can be extended to allow user-defined styling. Different modes for utilizing Symbology Encoding for this purpose are discussed." + "@value": "This document describes the OpenFlight Scene Description Database Specification, commonly\r\nreferred to as simply “OpenFlight”. OpenFlight is a 3D scene description file format that was\r\ncreated and is maintained by Presagis. While OpenFlight databases are typically created and edited\r\nusing Presagis software tools, the format is widely adopted and as a result, many tools exist\r\nto read and write OpenFlight database files.\r\nThe primary audience for this document includes software developers whose applications are\r\nintended to read and/or write OpenFlight database files. To this end, this document discusses\r\nconcepts incorporated in OpenFlight and contains a detailed description of the physical layout\r\nof OpenFlight files as represented on disk." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49906,35 +48821,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-078" + "@value": "19-065" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Styled Layer Descriptor Profile of the Web Map Service Implementation Specification" + "@value": "OGC OpenFlight Scene Description Database Specification 16.0 Community Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-189r2", + "@id": "http://www.opengis.net/def/docs/09-140r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-06-12" + "@value": "2010-07-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Frédéric Houbie; Fabian Skivee" + "@value": "Paul Daisey" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -49944,27 +48859,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47409" + "@id": "https://portal.ogc.org/files/?artifact_id=36336" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Cataloguing Earth Observation Products for ebXML Registry Information Model 3.0 based Catalogues" + "@value": "09-140r2" }, { "@language": "en", - "@value": "10-189r2" + "@value": "OGC® NSG Plugweek Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document specifies the Earth Observation Products Extension Package for ebXML Registry Information Model 3.0, based on the [OGC 10-157r1] Earth Observation Metadata profile of Observations and Measurements.\r\nIt enables CSW-ebRIM catalogues to handle a variety of metadata pertaining to earth observation p/roducts as defined in [OGC 10-157r1].\r\nThis proposed application profile document describes model and encodings required to discover, search and present metadata from catalogues of Earth Observation products. The profile presents a minimum specification for catalogue interoperability within the EO domain, with extensions for specific classes of metadata.\r\n" + "@value": "The Open Geospatial Consortium (OGC®) conducted a series of tests that examined the interoperability, suitability and performance of National System for Geospatial- Intelligence (NSG) Profiles provided by the National Geospatial-Intelligence Agency (NGA) of four OGC Standards, Web Map Service (WMS), Web Feature Service (WFS), Web Coverage Service (WCS), and Catalog Service (CAT). In the study, vendors, users, and other interested parties conducted Technology Integration Experiments (TIEs) and mutually refined clients, services, interfaces and protocols in the context of a hands-on engineering experience expected to shape the future NGA, NSG and Geospatial Intelligence (GEOINT) web based distribution." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -49975,35 +48890,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-189r2" + "@value": "09-140r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Cataloguing Earth Observation Products for ebXML Registry Information Model 3.0 based Catalogues" + "@value": "OGC® NSG Plugweek Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-067r3", + "@id": "http://www.opengis.net/def/docs/03-036r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-10-15" + "@value": "2003-06-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "" + "@value": "Jean-Philippe Humblet" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -50013,27 +48928,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/18-067r3/18-067r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=3841" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Symbology Conceptual Model: Core Part" + "@value": "Web Map Context Documents" }, { "@language": "en", - "@value": "18-067r3" + "@value": "03-036r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document presents the requirements for defining the Symbology Conceptual Core Model (SymCore), the conceptual basis to define symbology rules for the portrayal of geographical data. It is modular and extensible (one core model, many extensions), also encoding agnostic (one symbology model, many encodings). It contains a minimal set of abstract classes representing explicit extension points of the model." + "@value": "Create, store, and use state information from a WMS based client application" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50044,49 +48959,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-067r3" + "@value": "03-036r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Symbology Conceptual Model: Core Part" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/cr", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/06-043r3" - }, - { - "@id": "http://www.opengis.net/def/docs/08-022r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-098" + "@value": "Web Map Context Documents" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-082r2", + "@id": "http://www.opengis.net/def/docs/15-082", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-01-19" + "@value": "2016-04-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó" + "@value": "Boyan Brodaric" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/profile" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -50096,27 +48997,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/13-082r2/13-082r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=64688" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "13-082r2" + "@value": "15-082" }, { "@language": "en", - "@value": "Web Map Tile Service (WMTS) Simple Profile" + "@value": "GroundWaterML 2 – GW2IE FINAL REPORT" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/profile" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Web Map Tile Service (WMTS) Simple profile defines restrictions that limit the flexibility in implementing a WMTS instance. Adding additional requirements has the goal of simplifying the creation of services and clients. By implementing this profile, clients can more easily combine data coming from different services including from other WMTS instances and even from some tile implementations that are not OGC WMTS based, such as some current distributions of OSM. In fact, most of these tiling services are implicitly following most of the WMTS requirements. Many current WMTS services that implement this profile will have to undergo some changes on how tiles are exposed, and a client that is compatible with WMTS 1.0 will be immediately compatible with this profile. The aim is to align the WMTS standard to other popular tile initiatives which are less flexible but widely adopted." + "@value": "This document describes a conceptual model, logical model, and GML/XML encoding rules for the exchange of groundwater data. In addition, this document provides GML/XML encoding examples for guidance. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50127,30 +49028,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-082r2" + "@value": "15-082" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Map Tile Service (WMTS) Simple Profile" + "@value": "OGC GroundWaterML 2 – GW2IE FINAL REPORT" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-134", + "@id": "http://www.opengis.net/def/docs/13-099", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-06-30" + "@value": "2013-11-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arne Broering, Stefan Below" + "@value": "Jan Herrmann, Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -50165,17 +49066,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39664" + "@id": "https://portal.ogc.org/files/?artifact_id=55230" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Sensor Interface Descriptors" + "@value": "GeoXACML and XACML Policy Administration Web Service (PAWS)" }, { "@language": "en", - "@value": "10-134" + "@value": "13-099" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -50185,7 +49086,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document presents the Sensor Interface Descriptor (SID) schema that enables the declarative description of sensor interfaces, including the definition of the communication protocol, sensor commands, processing steps and metadata association. This schema is designed as a profile and extension of SensorML. Based on this schema, SID interpreters can be implemented, independently of particular sensor technology, which are able to translate between sensor protocol and SWE protocols. They establish the connection to a sensor and are able to communicate with it by using the sensor protocol definition of the SID. SID instances for particular sensor types can be reused in different scenarios and can be shared among user communities. The ability of an SID interpreter to connect sensors and Sensor Web services in an ad hoc manner based on the sensor’s SID instance is a next step towards realizing sensor plug & play within the Sensor Web." + "@value": "This specification defines the interfaces of the OGC (Geo)XACML Policy Administration Web Service (OGC (Geo)XACML PAWS or simply PAWS in the following) that supports the creation, modification, exchange, analysis, testing, transformation, encrypting and signing of XACML and GeoXACML encoded access control policies.\r\nThis draft specification was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. This document presents the results of the work within add-on project of the OWS-9 Security and Services Interoperability (SSI) thread. \r\nPlease note that currently the document only contains the definition of the mandatory operations i.e. the basic conformance class. The writing of the sections describing the optional operations is still a to do. These sections need to define the following operations:\r\n•\tAnalyzePolicyElement operation\r\n•\tOptimizePolicyElement operation \r\n•\tTransformPolicyElement operation\r\n•\tTestPolicyElement operation \r\n•\tEncryptPolicy operation\r\n•\tSignPolicy operation \r\nSuggested additions, changes, and comments on this report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50196,126 +49097,104 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-134" + "@value": "13-099" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Interface Descriptors" + "@value": "OGC GeoXACML and XACML Policy Administration Web Service (PAWS)" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/d-bp/collection", + "@id": "http://www.opengis.net/def/docs/17-040", "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" + "http://www.w3.org/2004/02/skos/core#Concept" ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "http://purl.org/dc/terms/created": [ { - "@value": "Documents of type Best Practice - deprecated " + "@type": "xsd:date", + "@value": "2018-01-08" } ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "http://purl.org/dc/terms/creator": [ { - "@value": "Documents of type Best Practice - deprecated " + "@value": "Stephen McCann, Roger Brackin, Gobe Hobona" } ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs" + "@id": "http://www.opengis.net/def/doc-type/per" } ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/07-113r1" - }, - { - "@id": "http://www.opengis.net/def/docs/04-038r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-035r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-080r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-135r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-062" - }, - { - "@id": "http://www.opengis.net/def/docs/07-063" - }, - { - "@id": "http://www.opengis.net/def/docs/05-057r4" - }, - { - "@id": "http://www.opengis.net/def/docs/05-011" - }, - { - "@id": "http://www.opengis.net/def/docs/05-010" - }, - { - "@id": "http://www.opengis.net/def/docs/07-018r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-039r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-021r2" - }, + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/06-131r4" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/03-105r1" - }, + "@id": "https://docs.ogc.org/per/17-040.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/06-023r1" + "@language": "en", + "@value": "Testbed-13: DCAT/SRIM Engineering Report" }, { - "@id": "http://www.opengis.net/def/docs/05-087r4" - }, + "@language": "en", + "@value": "17-040" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/05-027r1" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/05-086" - }, + "@value": "This engineering report captures the requirements, solutions, and implementation experiences of the Semantic Registry work package in Testbed-13. The engineering report describes the implementation of a RESTful Semantic Registry that supports the Semantic Registry Information Model (SRIM) which is based on the Data Catalog (DCAT) specification. A discussion of the applicability of the SRIM to the United States Geological Survey (USGS) and the National Geospatial Intelligence Agency (NGA) metadata is also presented, including an analysis of a set of controlled vocabularies from both organizations. Best Practice guidelines for the use of SRIM are also provided. The engineering report discusses the application of Shapes Constraint Language (SHACL) to aspects of Linked Data. Recognizing the benefits that asynchronous access has to offer web services, a description of the work undertaken by the testbed in implementing publish/subscribe functionality between a Semantic Registry and a Catalogue Service for the Web (CSW) is also presented." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/07-092r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/06-141r2" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "17-040" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type Best Practice - deprecated " + "@language": "en", + "@value": "OGC Testbed-13: DCAT/SRIM Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-096r1", + "@id": "http://www.opengis.net/def/docs/23-008r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-18" + "@value": "2023-09-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Peng Yue, Boyi Shangguan" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/profile" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -50325,27 +49204,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13205" + "@id": "https://docs.ogc.org/is/23-008r3/23-008r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-096r1" + "@value": "23-008r3" }, { "@language": "en", - "@value": "GML 3.1.1 grid CRSs profile" + "@value": "OGC Training Data Markup Language for Artificial Intelligence (TrainingDML-AI) Part 1: Conceptual Model Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/profile" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding definitions of grid coverage (including image) Coordinate Reference Systems (CRSs) plus related coordinate Transformations. This document also specifies some Universal Resource Names (URNs) for definitions in the ogc URN namespace, in addition to those specified in [OGC 05-010]. Additional specific URNs are defined for definitions of the datums, coordinate systems, and coordinate system axes which are often used in definitions of grid and image CRSs." + "@value": "The Training Data Markup Language for Artificial Intelligence (TrainingDML-AI) Standard aims to develop the UML model and encodings for geospatial machine learning training data. Training data plays a fundamental role in Earth Observation (EO) Artificial Intelligence Machine Learning (AI/ML), especially Deep Learning (DL). It is used to train, validate, and test AI/ML models. This Standard defines a UML model and encodings consistent with the OGC Standards baseline to exchange and retrieve the training data in the Web environment.\r\n\r\nThe TrainingDML-AI Standard provides detailed metadata for formalizing the information model of training data. This includes but is not limited to the following aspects:\r\n\r\nHow the training data is prepared, such as provenance or quality;\r\nHow to specify different metadata used for different ML tasks such as scene/object/pixel levels;\r\nHow to differentiate the high-level training data information model and extended information models specific to various ML applications; and\r\nHow to introduce external classification schemes and flexible means for representing ground truth labeling." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50356,35 +49235,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-096r1" + "@value": "23-008r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML 3.1.1 grid CRSs profile" + "@value": "OGC Training Data Markup Language for Artificial Intelligence (TrainingDML-AI) Part 1: Conceptual Model Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-009a", + "@id": "http://www.opengis.net/def/docs/12-027r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-01-12" + "@value": "2014-07-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Martin Daly" + "@value": "Timo Thomas" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/sap" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -50394,27 +49273,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=999" + "@id": "https://portal.ogc.org/files/?artifact_id=58922" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Coordinate Transformation Services - OLE/COM" + "@value": "Web Feature Service (WFS) Temporality Extension" }, { "@language": "en", - "@value": "01-009a" + "@value": "12-027r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/sap" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Provides interfaces for general positioning, coordinate systems, and coordinate transformations." + "@value": "This OGC discussion paper provides a proposal for a temporality extension for the WFS\r\n2.0 and FES 2.0 standard. It is based on the work of and experiences made in several\r\nOWS test beds, in particular OWS-7, OWS-8 and OWS-9, Aviation threads and\r\ndiscussions at the 2011 OGC TC meeting in Brussels, Belgium. It partially replaces and\r\nadvances the document “OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via\r\nan OGC WFS 2.0” [4]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50425,35 +49304,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-009a" + "@value": "12-027r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Coordinate Transformation Services - OLE/COM" + "@value": "OGC Web Feature Service (WFS) Temporality Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-019r1", + "@id": "http://www.opengis.net/def/docs/03-006r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-13" + "@value": "2004-01-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Marwa Mabrouk" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -50463,27 +49342,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-019r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=3418" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-019r1" + "@value": "Location Services (OpenLS): Core Services [Parts 1-5]" }, { "@language": "en", - "@value": "GeoPackage Engineering Report" + "@value": "03-006r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "In Testbed-16, participants researched ways to mitigate these limitations, particularly in the context of the Ordnance Survey (OS) MasterMap Topography datasets. The Testbed activity also made use of OS Open Zoomstack, a smaller, freely available, multi-scale dataset. To address the first two limitations, Testbed participants developed GeoPackage metadata profiles designed to advance the discoverability of the contents of a GeoPackage and exchange the OS portrayal styles and symbols. The metadata proved to be interoperable between the server and client implementation." + "@value": "OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50494,35 +49373,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-019r1" + "@value": "03-006r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: GeoPackage Engineering Report" + "@value": "OpenGIS Location Services (OpenLS): Core Services [Parts 1-5]" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-044", + "@id": "http://www.opengis.net/def/docs/04-085", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-04-08" + "@value": "2004-02-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Luis Bermudez" + "@value": "Richard Creps,Victor Brown,Bill Floyd,John Garcia,Jeff Grinstead,Robert Kraus,Steve Matney,Robert Qu" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -50532,27 +49411,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-044.html" + "@id": "https://portal.ogc.org/files/?artifact_id=7564" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-044" + "@value": "EA-SIG Collaboration White Paper" }, { "@language": "en", - "@value": "OGC Testbed 17: CITE Engineering Report" + "@value": "04-085" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 17 Engineering Report (ER) documents the result of the work performed in the CITE thread of the OGC Testbed-17 initiative. CITE is the Compliance Interoperability & Testing Evaluation Subcommittee that provides a forum for an open, consensus discussion regarding approaches and issues related to conformance and interoperability testing as part of the OGC standards process. This ER provides information about the development of a test suite for the OGC API — Processes Standard (OGC18-062r2) to be executed in the OGC Test Evaluation tool (TEAM Engine). The ER also documents an evaluation of an alternative environment for OGC compliance testing.\r\n\r\n" + "@value": "*RETIRED* The focus of collaboration services discussed in this white paper is on applications that directly support user interaction and on the applications that monitor, manage and control these interactive services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50563,35 +49442,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-044" + "@value": "04-085" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed 17: CITE Engineering Report" + "@value": "EA-SIG Collaboration White Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-094", + "@id": "http://www.opengis.net/def/docs/12-006", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-18" + "@value": "2012-04-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Apple Inc." + "@value": "Arne Bröring, Christoph Stasch, Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -50601,27 +49480,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/20-094/index.html" + "@id": "https://portal.ogc.org/files/?artifact_id=47599" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Indoor Mapping Data Format" + "@value": "12-006" }, { "@language": "en", - "@value": "20-094" + "@value": "Sensor Observation Service Interface Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Indoor Mapping Data Format (referenced throughout this document as IMDF) provides a generalized, yet comprehensive model for any indoor location, providing a basis for orientation, navigation and discovery. In this release there are also detailed instructions for modeling the spaces of an airport, a shopping mall, and a train station.\r\n\r\nThis release also has an extension model which enables a venue, organization, or even an industry to create valid features and validations not available in the current specification for private or public use\r\n\r\n" + "@value": "The SOS standard is applicable to use cases in which sensor data needs to be managed in an\r\ninteroperable way. This standard defines a Web service interface which allows querying\r\nobservations, sensor metadata, as well as representations of observed features. Further, this\r\nstandard defines means to register new sensors and to remove existing ones. Also, it defines\r\noperations to insert new sensor observations. This standard defines this functionality in a binding\r\nindependent way; two bindings are specified in this document: a KVP binding and a SOAP\r\nbinding." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50632,35 +49511,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-094" + "@value": "12-006" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Indoor Mapping Data Format" + "@value": "OGC® Sensor Observation Service Interface Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-134r2", + "@id": "http://www.opengis.net/def/docs/16-035", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-04-14" + "@value": "2017-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Richard Martell" + "@value": "Christoph Stasch, Simon Jirka" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/ts" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -50670,27 +49549,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27811" + "@id": "https://docs.ogc.org/per/16-035.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "KML 2.2 - Abstract Test Suite" + "@value": "Testbed-12 REST Architecture Engineering Report" }, { "@language": "en", - "@value": "07-134r2" + "@value": "16-035" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/ts" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is an abstract test suite (ATS): a compendium of abstract test cases that provide a basis for verifying the structure and content of OGC KML 2.2 instance documents. Three conformance levels are defined; each level builds on the preceding ones:\r\n\r\n *\r\n\r\n Level 1 - includes test cases covering all requirements to be satisfied by a minimally conformant KML document;\r\n *\r\n\r\n Level 2 - as for Level 1, plus test cases addressing recommended requirements;\r\n *\r\n\r\n Level 3 - as for Level 2, plus test cases covering suggested constraints that are informative in nature." + "@value": "REST interfaces facilitate the application of OGC standards in many novel application scenarios, e.g. implementing OGC clients on constrained devices, as they ease the implementation of service requests and simplify the interaction patterns. Thereby, REST serves as a complementary technology to the already existing SOAP/POX provided by most of the current OGC standards. This engineering report (ER) provides an overview on different REST service implementations in the Testbed-12 and in related activities. As a result, this ER can be used to develop recommendations on architecture guidelines for providing REST interfaces in the geospatial domain." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50701,35 +49580,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-134r2" + "@value": "16-035" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC KML 2.2 -Abstract Test Suite" + "@value": "Testbed-12 REST Architecture Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-027r2", + "@id": "http://www.opengis.net/def/docs/18-043r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2019-10-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Timo Thomas" + "@value": "Aleksandar Jelenak, Ted Habermann, Gerd Heber" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -50739,27 +49618,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51815" + "@id": "https://docs.ogc.org/is/18-043r3/18-043r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Web Feature Service (WFS) Temporality Extension " + "@value": "Hierarchical Data Format Version 5 (HDF5®) Core Standard" }, { "@language": "en", - "@value": "12-027r2" + "@value": "18-043r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Discussion Paper (DP) provides a proposal for a temporality extension for the WFS 2.0 and FES 2.0 standard. It is based on the work of and experiences made in several OWS test beds, in particular OWS-7 and OWS-8, Aviation threads and discussions at the 2011 OGC TC meeting in Brussels, Belgium. This DP partially replaces and advances the document OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0 [4]." + "@value": "Hierarchical Data Format Version 5 (HDF5®) is a data model, a programming interface, and a storage model for keeping and managing data. It supports an unlimited variety of data types, and is designed to be flexible and efficient for large and complex data. HDF5 is extensible via customizing data types, allowing communities and their applications to evolve in the use of HDF5.\r\n\r\nThis document describes the HDF5 data model as an encoding standard particularly suitable to scientific and engineering geospatial applications that employ multidimensional numeric arrays to describe temporally and spatially varying phenomena. The data model is simple yet versatile, capable of supporting complex data relationships and dependencies through its grouping and linking mechanisms. It is also self-describing by accommodating user-defined metadata." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50770,35 +49649,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-027r2" + "@value": "18-043r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Feature Service (WFS) Temporality Extension " + "@value": "OGC Hierarchical Data Format Version 5 (HDF5®) Core Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-129r1", + "@id": "http://www.opengis.net/def/docs/08-084r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-12-26" + "@value": "2008-08-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Patrick Neal, John Davidson, Bruce Westcott" + "@value": "Jen Marcus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -50808,27 +49687,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=16936" + "@id": "https://portal.ogc.org/files/?artifact_id=29505" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "FGDC CSDGM Application Profile for CSW 2.0" + "@value": "CITE Summary Engineering Report" }, { "@language": "en", - "@value": "06-129r1" + "@value": "08-084r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Catalogue Service Interface Standard 2.0.1 - FGDC CSDGM Application Profile for CSW 2.0 explains how Catalogue Services based on the FGDC Content Standard for Digital Geospatial Metadata (CSDGM) [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html] Application Profile for the OpenGIS® Catalogue Service Interface Standard v2.0.1 [http://www.opengeospatial.org/standards/cs] are organized and implemented for the discovery, retrieval and management of data metadata." + "@value": "This document summarizes work completed in the OWS5 Compliance & Interoperability Test & Evaluation thread. This document is applicable to the OGC Compliance Test Program." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50839,35 +49718,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-129r1" + "@value": "08-084r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "FGDC CSDGM Application Profile for CSW 2.0" + "@value": "OWS-5 CITE Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-006", + "@id": "http://www.opengis.net/def/docs/21-053r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-04-20" + "@value": "2023-06-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arne Bröring, Christoph Stasch, Johannes Echterhoff" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -50877,27 +49756,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47599" + "@id": "https://docs.ogc.org/as/21-053r1/21-053r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-006" + "@value": "21-053r1" }, { "@language": "en", - "@value": "Sensor Observation Service Interface Standard" + "@value": "Topic 23 - GeoPackage Conceptual and Logical Model" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The SOS standard is applicable to use cases in which sensor data needs to be managed in an\r\ninteroperable way. This standard defines a Web service interface which allows querying\r\nobservations, sensor metadata, as well as representations of observed features. Further, this\r\nstandard defines means to register new sensors and to remove existing ones. Also, it defines\r\noperations to insert new sensor observations. This standard defines this functionality in a binding\r\nindependent way; two bindings are specified in this document: a KVP binding and a SOAP\r\nbinding." + "@value": "This document presents the conceptual and logical models for version 1.x of the OGC GeoPackage Standard. The intent is that these models can be used to implement the GeoPackage standard using technology other than a SQLite database." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50908,35 +49787,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-006" + "@value": "21-053r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Sensor Observation Service Interface Standard" + "@value": "Topic 23 - GeoPackage Conceptual and Logical Model" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-040", + "@id": "http://www.opengis.net/def/docs/11-135r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-08" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stephen McCann, Roger Brackin, Gobe Hobona" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -50946,27 +49825,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-040.html" + "@id": "https://portal.ogc.org/files/?artifact_id=53819" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-13: DCAT/SRIM Engineering Report" + "@value": "11-135r2" }, { "@language": "en", - "@value": "17-040" + "@value": "Name Type Specification for Coordinate Reference Systems" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report captures the requirements, solutions, and implementation experiences of the Semantic Registry work package in Testbed-13. The engineering report describes the implementation of a RESTful Semantic Registry that supports the Semantic Registry Information Model (SRIM) which is based on the Data Catalog (DCAT) specification. A discussion of the applicability of the SRIM to the United States Geological Survey (USGS) and the National Geospatial Intelligence Agency (NGA) metadata is also presented, including an analysis of a set of controlled vocabularies from both organizations. Best Practice guidelines for the use of SRIM are also provided. The engineering report discusses the application of Shapes Constraint Language (SHACL) to aspects of Linked Data. Recognizing the benefits that asynchronous access has to offer web services, a description of the work undertaken by the testbed in implementing publish/subscribe functionality between a Semantic Registry and a Catalogue Service for the Web (CSW) is also presented." + "@value": "This document specifies a Name Type Specification (NTS) for predefined, combined, and parameterized Coordinate Reference System (CRS) definitions. This NTS augments the /def/ namespace with http URI definitions for CRSs. The NTS is based on the Name Type Specification – definitions – part 1 – basic name [OGC 09-048r3] and supersedes OGC document “Definition identifier URNs in OGC name¬space” [OGC 07-092r3].\r\nNTSs are maintained by the OGC Naming Authority (OGC-NA).\r\nThis document includes one Annex: a user guide to the OGC CRS resolver.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -50977,35 +49856,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-040" + "@value": "11-135r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: DCAT/SRIM Engineering Report" + "@value": "OGC® Name Type Specification for Coordinate Reference Systems" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-140r2", + "@id": "http://www.opengis.net/def/docs/22-025r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-07-30" + "@value": "2023-01-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Daisey" + "@value": "Patrick Cozzi, Sean Lilley" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -51015,27 +49894,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=36336" + "@id": "https://docs.ogc.org/cs/22-025r4/22-025r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-140r2" + "@value": "22-025r4" }, { "@language": "en", - "@value": "OGC® NSG Plugweek Engineering Report" + "@value": "3D Tiles Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Open Geospatial Consortium (OGC®) conducted a series of tests that examined the interoperability, suitability and performance of National System for Geospatial- Intelligence (NSG) Profiles provided by the National Geospatial-Intelligence Agency (NGA) of four OGC Standards, Web Map Service (WMS), Web Feature Service (WFS), Web Coverage Service (WCS), and Catalog Service (CAT). In the study, vendors, users, and other interested parties conducted Technology Integration Experiments (TIEs) and mutually refined clients, services, interfaces and protocols in the context of a hands-on engineering experience expected to shape the future NGA, NSG and Geospatial Intelligence (GEOINT) web based distribution." + "@value": "This document describes the specification for 3D Tiles, an open standard for streaming massive heterogeneous 3D geospatial datasets." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51046,35 +49925,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-140r2" + "@value": "22-025r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® NSG Plugweek Engineering Report" + "@value": "3D Tiles Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-060r1", + "@id": "http://www.opengis.net/def/docs/03-063r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-08-02" + "@value": "2003-06-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff" + "@value": "Joshua Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -51084,27 +49963,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39509" + "@id": "https://portal.ogc.org/files/?artifact_id=1269" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-060r1" + "@value": "Critical Infrastructure Collaborative Environment Architecture: Computational Viewpoint" }, { "@language": "en", - "@value": "OWS-7 Event Architecture Engineering Report" + "@value": "03-063r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is applicable to use cases in which event-driven architecture principles are applied in Spatial Data Infrastructures.\r\n\r\nThe document specifies publish/subscribe functionality for OGC web services. This is done by first defining an abstract publish / subscribe model and then deriving functional requirements from this model." + "@value": "*RETIRED* The objective of this document is to provide a vendor-neutral interoperable framework that enables collaborating communities to rapidly and collaboratively publish, discover, integrate and use geospatial information concerned with the protection of critical infrastructure systems in a range of sectors. Specifically, this document specifies a Computational Architecture viewpoint for a Critical Infrastructure Collaborative Environment (CICE)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51115,30 +49994,59 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-060r1" + "@value": "03-063r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-7 Event Architecture Engineering Report" + "@value": "Critical Infrastructure Collaborative Environment Architecture: Computational Viewpoint" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-022", + "@id": "http://www.opengis.net/def/doc-type/isx", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/13-084r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-049" + }, + { + "@id": "http://www.opengis.net/def/docs/12-040" + }, + { + "@id": "http://www.opengis.net/def/docs/11-053r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-135" + }, + { + "@id": "http://www.opengis.net/def/docs/12-039" + }, + { + "@id": "http://www.opengis.net/def/docs/10-092r3" + }, + { + "@id": "http://www.opengis.net/def/docs/08-059r4" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/17-088r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-30" + "@value": "2018-02-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Benjamin Pross" + "@value": "Luis Bermudez" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -51153,17 +50061,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-022.html" + "@id": "https://docs.ogc.org/per/17-088r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 WPS Conflation Service Profile Engineering Report" + "@value": "17-088r1" }, { "@language": "en", - "@value": "16-022" + "@value": "Strengthening Disaster Risk Reduction Across the Americas Summit - Simulated Exercise Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -51173,7 +50081,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "One practical purpose of this ER will be to describe how a conflation tool such as the Hootenanny software can be used for conflation tasks using the Web Processing Service interface. The developed WPS REST (conflation) Service will be described in detail. Special focus will be laid on more complex conflation tasks that include user interaction. During earlier testbeds, we connected different conflation tools to the WPS and performed different conflation tasks (see [1] and [2]). The experiences gathered there together with the ones gathered in the Testbed 12 will be captured in the ER. As the WPS REST (Conflation) Service will be RESTful, this ER could be the basis for a REST binding extension for WPS 2.0. Service profiles are an important aspect of the WPS 2.0 standard. We will investigate how a WPS 2.0 Conflation Profile could look like in the hierarchical profiling approach of WPS 2.0." + "@value": "Disasters are responsible for major socioeconomic damages. Global initiatives call for the improvement of information technology infrastructure to better share data and advance multinational collaboration.\r\n\r\nThe Strengthening Disaster Risk Reduction Across the Americas: A Regional Summit on the Contributions of Earth Observations held on September 3-8 in 2017 in Buenos Aires, Argentina strengthened the collective ability to share the many challenges of disaster risk reduction in Latin America and the Caribbean (LAC) while promoting the awareness and better use of earth observations (EO).\r\n\r\nA simulation exercise took place during the summit. The exercise brought together government, emergency managers, earth observation data providers, academics, non-governmental organizations, and commercial companies. The participants assessed the capabilities and needs of policymakers, regional and on-the-ground decision makers, and learned what information products can be produced, and when and how such products are available.\r\n\r\nThis ER describes the description and results of the simulated scenario including the post-exercise activity that captured the lessons learned from the participants.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51184,35 +50092,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-022" + "@value": "17-088r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 WPS Conflation Service Profile Engineering Report" + "@value": "Strengthening Disaster Risk Reduction Across the Americas Summit - Simulated Exercise Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-077r4", + "@id": "http://www.opengis.net/def/docs/06-079r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-01-18" + "@value": "2006-06-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Dr. Markus Mueller" + "@value": "Marc Gilles" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -51222,27 +50130,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=16700" + "@id": "https://portal.ogc.org/files/?artifact_id=15547" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Symbology Encoding Implementation Specification" + "@value": "06-079r1" }, { "@language": "en", - "@value": "05-077r4" + "@value": "EO Application Profile for CSW 2.0" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Symbology Encoding Standard (SES) defines an XML language for styling information that can be applied to digital geographic feature and coverage data. SE is independent of any OGC Web Services descriptions and could therefore be used to describe styling information in non-networked systems such as desktop geographic information systems. " + "@value": "Explains how Catalogue Services based on the HMA (Heterogeneous Earth Observation Missions Accessibility) Application Profile for the OGC Catalogue Services Specification v2.0.1 [OGC 04-021r3] are organized and implemented for the discovery, retrieval and management of Earth Observation products metadata." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51253,30 +50161,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-077r4" + "@value": "06-079r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Symbology Encoding Implementation Specification" + "@value": "EO Application Profile for CSW 2.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-056", + "@id": "http://www.opengis.net/def/docs/16-038", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-10-01" + "@value": "2017-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Wenwen Li, Sheng Wu" + "@value": "Chris Clark" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -51291,17 +50199,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64382" + "@id": "https://docs.ogc.org/per/16-038.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 11 Catalogue Service and Discovery Engineering Report" + "@value": "16-038" }, { "@language": "en", - "@value": "15-056" + "@value": "Testbed-12 NSG GeoPackage Profile Assessment Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -51311,7 +50219,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 11 Engineering Report provides a comprehensive review and comparison in terms of architecture, functionality, and usability of the OGC catalogue service standards CSW 2.0.2 and CSW 3.0. We are especially interested in how well the two standards provide support for open searches and federated distributed searches in current distributed computing paradigms. We also evaluated the support of semantic searches using different strategies, including (1) semantic mediation, a.k.a. ontology-based query expansion (Li et al. 2008; Li et al. 2011), (2) semantic association, which enables current catalogue information models to support semantic search (Li et al. 2014; Li et al. 2015), and (3) complete renovation of the CSW information model to be a triple store and utilize Semantic Web technology (Berner-Lee 2001) to support semantic query and data retrieval. Scenarios to search for hydrological data are developed to evaluate the performance of catalogue searching using the above strategies. Recommendations for adoption of CSW standards as well as tasks in advancing catalogue search and data discovery in future testbeds is also discussed. " + "@value": "The National System for Geospatial-Intelligence (NSG) GeoPackage Profile defines and tailors the implementable provisions prescribed for the NSG for a GeoPackage based on the OGC GeoPackage encoding standard. The profile provides detailed directions on how to use the clauses, options and parameters defined in the base GeoPackage standard. The goal is to ensure that NSG GeoPackages, GeoPackage SQLite Extensions, and supporting utilities and services fulfill their intended purposes and are fit for use.\r\n\r\nThe goal of this Engineering Report (ER) is to assess whether requirements as specified in the proposed profile are specific enough to allow for any two independent GeoPackage implementers to produce and consume interoperable NSG GeoPackages. Concerns with the profile are outlined and recommendations for improvement are provided. Thoughts on the viability of the profile approach and guidance on how the profile could apply to Vector Tiling are also provided." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51322,30 +50230,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-056" + "@value": "16-038" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 11 Catalogue Service and Discovery Engineering Report " + "@value": "Testbed-12 NSG GeoPackage Profile Assessment Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-058r1", + "@id": "http://www.opengis.net/def/docs/16-120r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-05-11" + "@value": "2017-03-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele, Panagiotis (Peter) A. Vretanos" + "@value": "Hideki Hayashi, Akinori Asahara, Kyoung-Sook Kim, Ryosuke Shibasaki, Nobuhiro Ishimaru" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -51360,17 +50268,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.opengeospatial.org/is/18-058r1/18-058r1.html" + "@id": "https://docs.ogc.org/is/16-120r3/16-120r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC API - Features - Part 2: Coordinate Reference Systems by Reference corrigendum" + "@value": "16-120r3" }, { "@language": "en", - "@value": "18-058r1" + "@value": "Moving Features Access" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -51380,7 +50288,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks.\r\n\r\nOGC API Features provides API building blocks to create, modify and query features on the Web. OGC API Features is comprised of multiple parts, each of them is a separate standard.\r\n\r\nThis part extends the core capabilities specified in Part 1: Core with the ability to use coordinate reference system identifiers other than the defaults defined in the core." + "@value": "This document defines Moving Features Access, i.e., access methods to moving feature data for retrieving feature attributes, information on a relation between a trajectory object and one or more geometry objects, and information on a relation between two trajectory objects from a database storing trajectory data of moving features.\r\n\r\nAbstract methods of accessing moving features data are defined in ISO 19141:2008 (Geographic information - Schema for moving features) [ISO 19141:2008]. However, the methods are insufficient to access a database storing moving feature data from multiple sources. If implementations for access to moving features data using various programming languages or protocols (e.g., SQL, Java, and HTTP) are developed without any standards, these implementations might be inconsistent with each other, resulting in poor interoperability. Therefore, methods to access a database storing moving feature data are necessary to improve interoperability.\r\n\r\nApplications using moving feature data, typically representing vehicles or pedestrians, are rapidly increasing. Innovative applications are expected to require the overlay and integration of moving feature data from different sources to create greater social and business value. Moreover, systems relying on single-source moving feature data are now evolving into more integrated systems. Integration of moving feature data from different sources is a key to developing more innovative and advanced applications.\r\n\r\nMoving Features Access ensures better data exchange by handling and integrating moving feature data to broaden the market for geo-spatial information such as Geospatial Big Data Analysis. OGC 14-083r2 (OGC® Moving Features Encoding Part I: XML Core) [OGC 14-083r2] and OGC 14-084r2 (OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV)) [OGC 14-084r2] are existing implementation standards. Moving Features Access uses these standards to encode moving features." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51391,35 +50299,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-058r1" + "@value": "16-120r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Features - Part 2: Coordinate Reference Systems by Reference corrigendum" + "@value": "OGC Moving Features Access" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-088", + "@id": "http://www.opengis.net/def/docs/06-028", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-08-04" + "@value": "2006-04-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steve Liang, Tania Khalafbeigi, Hylke van der Schaaf" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -51429,27 +50337,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/18-088/18-088.html" + "@id": "https://portal.ogc.org/files/?artifact_id=13921" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "SensorThings API Part 1: Sensing" + "@value": "06-028" }, { "@language": "en", - "@value": "18-088" + "@value": "Sensor Alert Service" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC SensorThings API provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the web. At a high level the OGC SensorThings API provides two main functionalities and each function is handled by a part. The two parts are the Sensing part and the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. This document is version 1.1 and it is extending the first version of Sensing part." + "@value": "A service providing active (push-based) access to sensor data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51460,39 +50368,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-088" + "@value": "06-028" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC SensorThings API Part 1: Sensing Version 1.1" + "@value": "Sensor Alert Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-095", + "@id": "http://www.opengis.net/def/docs/18-077r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-01-22" - }, - { - "@type": "xsd:date", - "@value": "2015-01-23" + "@value": "2019-01-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lance McKee" + "@value": "Jay Freeman, Kevin Bentley, Ronald Moore, Samuel Chambers, Glen Quesenberry" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -51502,37 +50406,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/60920" - }, - { - "@id": "https://portal.ogc.org/files/?artifact_id=60920" + "@id": "https://portal.ogc.org/files/?artifact_id=82553" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Information Technology Standards for Sustainable Development" - }, - { - "@language": "en", - "@value": "Information Technology Standards for Sustainable Development" + "@value": "CDB, Leveraging GeoPackage Discussion Paper" }, { "@language": "en", - "@value": "14-095" + "@value": "18-077r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Sustainable development, meeting the needs of the present without compromising the ability of future generations to meet their own needs, will be accomplished by balancing social, economic and environmental objectives. In this paper the authors explain that rigorous standards for communicating environmental data are absolutely essential to enable social and economic progress in the Age of the Environment – the Anthropocene Epoch – in which humanity's expanding footprint has become the main cause of change in the planet's geology, water bodies, atmosphere and biosphere. The authors argue for a concerted and ongoing global effort to 1) define data communication and system interoperability requirements for environmental science, business and policy, and then 2) develop and implement consensus-derived, free and open environmental Information Technology (IT) standards that meet those requirements and that co-evolve with the larger IT standards framework and advances in IT." - }, - { - "@value": "Sustainable development, meeting the needs of the present without compromising the\r\nability of future generations to meet their own needs,1\r\n will be accomplished by\r\nbalancing social, economic and environmental objectives. In this paper the authors\r\nexplain that rigorous standards for communicating environmental data are absolutely\r\nessential to enable social and economic progress in the Age of the Environment2 – the\r\nAnthropocene Epoch3 – in which humanity's expanding footprint has become the main\r\ncause of change in the planet's geology, water bodies, atmosphere and biosphere. The\r\nauthors argue for a concerted and ongoing global effort to 1) define data communication\r\nand system interoperability requirements for environmental science, business and policy,\r\nand then 2) develop and implement consensus-derived, free and open environmental\r\nInformation Technology (IT) standards that meet those requirements and that co-evolve\r\nwith the larger IT standards framework and advances in IT." + "@value": "This paper offers the results of research, design, and prototype efforts to present the OGC standards working group an approach to creating “GeoCDB”—a technology mashing of GeoPackage and OGC CDB—as a deterministic repository of easily read data geospatial datasets suitable for storage, runtime access, and dissemination for live, virtual, constructive, gaming, and mission command (MC) systems." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51543,35 +50437,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-095" + "@value": "18-077r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Information Technology Standards for Sustainable Development" + "@value": "OGC CDB, Leveraging GeoPackage Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-083r3", + "@id": "http://www.opengis.net/def/docs/04-095", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-01-20" + "@value": "2005-05-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Eric Hirschorn" + "@value": "Peter Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -51581,27 +50475,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/16-083r3/16-083r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=8340" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Coverage Implementation Schema - ReferenceableGridCoverage Extension with Corrigendum" + "@value": "04-095" }, { "@language": "en", - "@value": "16-083r3" + "@value": "Filter Encoding Implementation Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC GML Application Schema - Coverages (“GMLCOV”) version 1.0 [OGC 09-146r2], recently renamed the OGC Coverage Implementation Schema version 1.0, provides a ReferenceableGridCoverage element for representing coverages on a referenceable grid. However, GMLCOV provides no instantiable subtypes of a critical sub-element of ReferenceableGridCoverage, GMLCOV::AbstractReferenceableGrid. To make use of ReferenceableGridCoverage, an extension deriving from GMLCOV would need to be developed. GML 3.3 is not such an extension of GMLCOV, as it is built independently from GMLCOV. Use of the instantiable referenceable grid elements of GML 3.3 with ReferenceableGridCoverage violates Requirement 14 of GMLCOV 1.0 and Requirement 24 of the OGC Modular Specification[1].\r\n\r\nThis OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension provides a set of referenceable grid elements for use as sub-elements of ReferenceableGridCoverage. Three of these elements have been adapted from GML 3.3, while a fourth emerged from work on a Testbed-11 Engineering Report[2]." + "@value": "The OpenGIS® Filter Encoding Standard (FES) defines an XML encoding for filter expressions. A filter expression logically combines constraints on the\r\nproperties of a feature in order to identify a particular subset of features to be operated upon. For example, a subset of features might be identified to render them in a particular color or convert them into a user-specified format. Constraints can be specified on values of spatial, temporal and scalar properties. An example of a filter is: Find all the properties in Omstead County owned by Peter Vretanos.\r\n\r\nThis standard is used by a number of OGC Web Services, including the Web Feature Service [http://www.opengeospatial.org/standards/wfs], the Catalogue Service [http://www.opengeospatial.org/standards/cat] and the Styled Layer Descriptor Standard [http://www.opengeospatial.org/standards/sld]. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51612,30 +50506,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-083r3" + "@value": "04-095" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension with Corrigendum" + "@value": "OpenGIS Filter Encoding Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-047r3", + "@id": "http://www.opengis.net/def/docs/10-061r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-01-25" + "@value": "2010-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Harrison" + "@value": "Johannes Echterhoff, Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -51650,17 +50544,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=65418" + "@id": "https://portal.ogc.org/files/?artifact_id=39513" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-11 NIEM-IC Feature Processing API using OGC Web Services" + "@value": "OWS-7 Dynamic Sensor Notification Engineering Report" }, { "@language": "en", - "@value": "15-047r3" + "@value": "10-061r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -51670,7 +50564,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community (IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0 architecture through the development, implementations, test, and robust demonstration making use of IC specifications, Geography Markup Language (GML), and NIEM in a simulated “real-world” scenario. The demonstration scenario begins with NIEM-conformant Information Exchange Packages (IEPs) containing operational data and IC security tags from the Information Security Marking (ISM) and Need-To-Know (NTK) access control metadata, and the Trusted Data Format (TDF) for binding assertion metadata with data resource(s). Those instance documents are deployed on Open Geospatial Consortium (OGC) Web Services to be used by client applications. Access control is based on attributes of the end-user and the instance data. \r\nThe assessment included reviewing example IEPDs and performing test and demonstrations using OGC web services, such as Transactional Web Feature Services (WFS-T), Policy Enforcement Points (PEPs) and OGC Attribute Stores to process geographic feature with NIEM components and security tags. The Test and Demonstration included, but was not limited to feature retrieval and transactions. Recommendations to update these information exchanges were provided to reflect NIEM 3.0 architecture and security tags in a ‘NIEM/IC Feature Processing API’. Results from this task helped provide a preliminary architecture for Geo4NIEM in Testbed 11, summarized in other OGC Testbed 11 Engineering Reports. \r\nThis task also identified potential change requests to OGC WFS or other OGC Services for handling security information in a federated role-based access control environment. These changes may help the NIEM/IC transform into more agile and customer-centric frameworks driven by collaborative partnerships. This transformation is vital to confronting the security challenges of the future.\r\n" + "@value": "This document is applicable to scenarios where moving sensors need to be tracked and their entry into an area of interest needs to be detected.\r\n\r\nThe document presents a detailed discussion of different approaches for encoding tracked object position.\r\n\r\nTwo approaches for implementing dynamic sensor tracking and notification are described, one based on the Sensor Alert Service specification and the other based on the Sensor Event Service specification.\r\n\r\nAn overview of standards and specifications relevant for and related to dynamic sensor tracking and notification is provided.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51681,35 +50575,81 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-047r3" + "@value": "10-061r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-11 NIEM-IC Feature Processing API using OGC Web Services" + "@value": "OWS-7 Dynamic Sensor Notification Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-112", + "@id": "http://www.opengis.net/def/doc-type/pol/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Policy Document" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Policy Document" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/09-144r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-046r6" + }, + { + "@id": "http://www.opengis.net/def/docs/08-134r11" + }, + { + "@id": "http://www.opengis.net/def/docs/05-020r29" + }, + { + "@id": "http://www.opengis.net/def/docs/08-131r3" + }, + { + "@id": "http://www.opengis.net/def/docs/09-046r5" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Policy Document" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/19-075r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-09-14" + "@value": "2020-05-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "ISO" + "@value": "Sylvain Grellet, Eric Boisvert, Bruce Simons, Jean-François Rainaud, Henning Lorenz, Rainer Haener" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -51719,27 +50659,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1221" + "@id": "https://portal.ogc.org/files/19-075r1" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 12 - The OpenGIS Service Architecture" + "@value": "19-075r1" }, { "@language": "en", - "@value": "02-112" + "@value": "Borehole Interoperability Experiment Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Same as ISO 19119" + "@value": "This document describes a conceptual model, logical model, and GML/XML encoding schema for the exchange of borehole related data and especially all the elements that are positioned along a borehole trajectory. In addition, this document provides GML/XML encoding instances documents for guidance" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51750,30 +50690,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-112" + "@value": "19-075r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 12 - The OpenGIS Service Architecture" + "@value": "OGC Borehole Interoperability Experiment Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-016", + "@id": "http://www.opengis.net/def/docs/22-020r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-09-11" + "@value": "2023-03-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Craig Bruce" + "@value": "Paul Churchyard, Ajay Gupta" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -51788,17 +50728,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=33515" + "@id": "https://docs.ogc.org/per/22-020r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-6 Symbology Encoding (SE) Changes ER" + "@value": "22-020r1" }, { "@language": "en", - "@value": "09-016" + "@value": "Testbed-18: Identifiers for Reproducible Science Summary Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -51808,7 +50748,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the extension of the OGC Symbology Encoding (SE) symbology format for improved capability and harmonization with ISO 19117 symbology, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology." + "@value": "The OGC’s Testbed 18 initiative explored the following six tasks.\r\n\r\n1.) Advanced Interoperability for Building Energy\r\n2.) Secure Asynchronous Catalogs\r\n3.) Identifiers for Reproducible Science\r\n4.) Moving Features and Sensor Integration\r\n5.) 3D+ Data Standards and Streaming\r\n6.) Machine Learning Training Data\r\nTestbed 18 Task 3, Identifiers for Reproducible Science, explored and developed workflows demonstrating best practices at the intersection of Findable, Accessible, Interoperable, and Reusable (or FAIR) data and reproducible science.\r\n\r\nThe workflows developed in this Testbed included:\r\n\r\nthe development of a Whole Tail workflow for land cover classification (52 Degrees North);\r\nthe development of a reproducible workflow for a deep learning application for target detection (Arizona State University);\r\nthe implementation of reproducible workflows following the approach described in the OGC API Process Part 3: Workflows and Chaining for Modular OGC API Workflows (Ecere);\r\nthe development of a reproducible workflow that runs an OGC API — Process and Feature Server instance within a Whole Tale environment (GeoLabs); and\r\nthe development of a water body detection Application Package to cover the identifier assignment and reproducibility from code to several execution scenarios (local, Exploitation Platform, Whole Tale) (Terradue).\r\nTestbed 18 participants identified considerations and limitations for reproducible workflows and recommendations for future work to identify the benefits of reproducible science for healthcare use cases." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51819,30 +50759,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-016" + "@value": "22-020r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 Symbology Encoding (SE) Changes ER" + "@value": "Testbed-18: Identifiers for Reproducible Science Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-042", + "@id": "http://www.opengis.net/def/docs/15-096", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-10-13" + "@value": "2016-01-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steffen Neubauer, Alexander Zipf" + "@value": "Akinori Asahara, Hideki Hayashi, Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -51857,17 +50797,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=32904" + "@id": "https://portal.ogc.org/files/?artifact_id=64623" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "3D-Symbology Encoding Discussion Draft" + "@value": "Use Cases and Applications of the OGC Moving Features Standard: The Requirements for a Moving Feature API" }, { "@language": "en", - "@value": "09-042" + "@value": "15-096" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -51877,7 +50817,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document present an extension of the Symbology Encoding (SE) /Styled Layer Descriptor (SLD) specifications into 3D as a separate profile." + "@value": "This OGC Discussion Paper provides examples of some actual and potential geospatial applications using the OGC Moving Features encoding. These applications can be used to define the next steps in the development of the OGC Moving Features Standard: The definition of a “Moving Features API”. As a conclusion, the Moving Features SWG recommends that a new Moving Features API standard should target the following three kinds of operations: retrieval of feature information, operations between a trajectory and a geometric object, and operations between two trajectories. Additionally, the Moving Features SWG recommends establishing an abstract specification for these three kinds of operations because only a part of operations for trajectories is defined by ISO 19141:2008 - Schema for moving features." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51888,35 +50828,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-042" + "@value": "15-096" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "3D-Symbology Encoding Discussion Draft" + "@value": "Use Cases and Applications of the OGC Moving Features Standard: The Requirements for a Moving Feature API" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-068", + "@id": "http://www.opengis.net/def/docs/14-005r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-24" + "@value": "2016-08-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Pedro Gonçalves" + "@value": "Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -51926,27 +50866,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55219" + "@id": "http://docs.opengeospatial.org/is/14-005r4/14-005r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "13-068" + "@value": "14-005r4" }, { "@language": "en", - "@value": "OpenSearch Extension for Correlated Search" + "@value": "OGC® IndoorGML - with Corrigendum" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC discussion paper presents an OpenSearch query protocol extension for the\r\nexecution of correlation queries between different Search Feeds. Services that support the\r\nOpenSearch Specification and Correlation extension defined in this document are called\r\nOpenSearch Correlation Services. With the proposed extensions it will be possible to\r\nexecute distributed queries with correlation and search criteria defining the results\r\naggregation." + "@value": "This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -51957,35 +50897,40 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-068" + "@value": "14-005r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC OpenSearch Extension for Correlated Search" + "@value": "OGC® IndoorGML - with Corrigendum" + } + ], + "http://www.w3.org/ns/dcat#landingPage": [ + { + "@id": "http://docs.opengeospatial.org/is/14-005r4/14-005r4.html" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-105r1", + "@id": "http://www.opengis.net/def/docs/17-037", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-04-19" + "@value": "2018-01-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside" + "@value": "Jeff Harrison" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -51995,27 +50940,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=4700" + "@id": "https://docs.ogc.org/per/17-037.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-105r1" + "@value": "17-037" }, { "@language": "en", - "@value": "Geography Markup Language (GML) Encoding Specification" + "@value": "Testbed-13: SWAP Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features." + "@value": "This OGC document provides an analysis of the prototype implementations, approaches and performance aspects of data serialization techniques explored in OGC Testbed 13. Specifically, it describes work done during Testbed 13 investigating serialization for geospatial data sets on OGC Web Feature Service (WFS) using Google Protocol Buffers (Protobuf) and Apache Avro.\r\n\r\nProtocol buffers are Google’s language-neutral, platform-neutral, extensible mechanism for serializing structured data. They are described by Google in the following manner - 'think XML, but smaller, faster, and simpler'. With Protobuf Google indicates developers can define how they want their data to be structured once, then they can use special generated source code to easily write and read structured data to and from a variety of data streams and using a variety of languages. Apache Avro is described as a remote procedure call and data serialization framework developed within Apache’s Hadoop project. It uses JavaScript Object Notation(JSON) for defining data types and reportedly serializes data in a compact binary format." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52026,35 +50971,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-105r1" + "@value": "17-037" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Geography Markup Language (GML) Encoding Specification" + "@value": "OGC Testbed-13: SWAP Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-134r11", + "@id": "http://www.opengis.net/def/docs/07-022r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-06-28" + "@value": "2007-12-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pol" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52064,27 +51009,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/pol/08-134r11.html" + "@id": "https://portal.ogc.org/files/?artifact_id=22466" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Compliance Testing Program Policies & Procedures" + "@value": "Observations and Measurements - Part 1 - Observation schema" }, { "@language": "en", - "@value": "08-134r11" + "@value": "07-022r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pol" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the Open Geospatial Consortium (OGC) Compliance Testing Program. The document describes the roles and responsibilities, compliance testing procedures, development of test packaging, and policies for developing and releasing the software used for testing for compliance to OGC Standards." + "@value": "The OpenGIS® Observations and Measurements Encoding Standard (O&M) defines an abstract model and an XML schema [www.w3.org/XML/Schema] encoding for observations and it provides support for common sampling strategies. O&M also provides a general framework for systems that deal in technical measurements in science and engineering. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52095,35 +51040,42 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-134r11" + "@value": "07-022r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Compliance Testing Program Policies & Procedures" + "@value": "Observations and Measurements - Part 1 - Observation schema" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-131r2", + "@id": "http://www.opengis.net/def/docs/12-066", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-09-25" + "@value": "2014-01-31" + }, + { + "@type": "xsd:date", + "@value": "2012-07-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "Linda van den Brink, Jantien Stoter, Sisi Zlatanova" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/d-dp" + }, + { + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52133,27 +51085,33 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/wp/16-131r2/16-131r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=49000" + }, + { + "@id": "https://portal.ogc.org/files/?artifact_id=49000&version=2" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-131r2" + "@value": "Modeling an application domain extension of CityGML in UML" }, { "@language": "en", - "@value": "Big Geospatial Data – an OGC White Paper" + "@value": "12-066" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/d-dp" + }, + { + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This white paper is a survey of Big Geospatial Data with these main themes:\r\n\r\n Geospatial data is increasing in volume and variety;\r\n New Big Data computing techniques are being applied to geospatial data;\r\n Geospatial Big Data techniques benefit many applications; and\r\n Open standards are needed for interoperability, efficiency, innovation and cost effectiveness.\r\n \r\n\r\nThe main purpose of this White Paper is to identify activities to be undertaken in OGC Programs that advance the Big Data capabilities as applied to geospatial information.\r\n\r\nThis white paper was developed based on two Location Powers events:\r\n\r\n Location Powers: Big Data, Orlando, September 20th, 2016; and\r\n Location Powers: Big Linked Data, Delft, March 22nd, 2017.\r\nFor information on Location Powers: http://www.locationpowers.net/pastevents/" + "@value": "This paper presents key aspects of the development of a Dutch 3D standard IMGeo as a CityGML ADE. The new ADE is modeled using UML class diagrams. However the OGC CityGML specification does not provide clear rules on modeling an ADE in UML. This paper describes how the extension was built, which provides general insight how CityGML can be extended for a specific applications starting from the UML diagrams. Several alternatives for modeling ADEs in UML have been investigated and compared. The best suited for the 3D standard option is selected and applied. Open issues and challenges are discussed in the conclusions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52164,35 +51122,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-131r2" + "@value": "12-066" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Big Geospatial Data – an OGC White Paper" + "@value": "Modeling an application domain extension of CityGML in UML" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-079r1", + "@id": "http://www.opengis.net/def/docs/09-064r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-01-08" + "@value": "2009-09-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steve Liang, Tania Khalafbeigi" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52202,27 +51160,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/17-079r1/17-079r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=34147" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-079r1" + "@value": "09-064r2" }, { "@language": "en", - "@value": "SensorThings API Part 2 – Tasking Core" + "@value": "OWS-6 Sensor Web Enablement (SWE) Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC SensorThings API [OGC 15-078r6] provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the Web. At a high level, the OGC SensorThings API provides two main functions and each function is handled by the Sensing part or the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. The Tasking part provides a standard way for parameterizing - also called tasking - of taskable IoT devices, such as individual sensors and actuators, composite consumer / commercial / industrial / smart cities in-situ platforms, mobile and wearable devices, or even unmanned systems platforms such as drones, satellites, connected and autonomous vehicles, etc. This document specifies core of the SensorThings Tasking part." + "@value": "This OGC® document summarizes work completed in the OWS-6 Sensor Web Enablement (SWE) thread. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52233,35 +51191,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-079r1" + "@value": "09-064r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC SensorThings API Part 2 – Tasking Core" + "@value": "OWS-6 Sensor Web Enablement (SWE) Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-017r1", + "@id": "http://www.opengis.net/def/docs/06-057r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-02-08" + "@value": "2006-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Thomas Kolbe, Gerhard Groeger and Angela Czerwinski" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52271,27 +51229,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://docs.ogc.org/per/21-017r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=16675" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-017r1" + "@value": "City Geography Markup Language" }, { "@language": "en", - "@value": "OGC Features and Geometries JSON Engineering Report" + "@value": "06-057r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Testbed-17 Features and Geometries JSON task investigated proposals for how feature data could be encoded in JSON so that:\r\n\r\n* Different Coordinate Reference Systems (CRS) are supported and\r\n* Communities can build and formally specify profiles of the fully CRS-enabled JSON with limited sets of supported geometry types and with clear constraints for feature type definitions.\r\n\r\nGeoJSON, a standard of the Internet Engineering Task Force (IETF), was used as a starting point.\r\n\r\nThis Engineering Report (ER) captures the results and discussions, including material that was submitted to the https://github.com/opengeospatial/OGC-feat-geo-json[OGC Features and Geometries JSON Standards Working Group].\r\n" + "@value": "CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language 3 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52302,35 +51260,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-017r1" + "@value": "06-057r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: OGC Features and Geometries JSON Engineering Report" + "@value": "City Geography Markup Language" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-095c1", + "@id": "http://www.opengis.net/def/docs/21-065r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-05-03" + "@value": "2024-07-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Vretanos" + "@value": "Panagiotis (Peter) A. Vretanos, Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52340,27 +51298,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51130" + "@id": "https://docs.ogc.org/is/21-065r2/21-065r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-095c1" + "@value": "Common Query Language (CQL2)" }, { "@language": "en", - "@value": "Filter Encoding Implementation Specification Corrigendum 1" + "@value": "21-065r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Filter Encoding Standard (FES) defines an XML encoding for filter expressions. A filter expression logically combines constraints on the\r\nproperties of a feature in order to identify a particular subset of features to be operated upon. For example, a subset of features might be identified to render them in a particular color or convert them into a user-specified format. Constraints can be specified on values of spatial, temporal and scalar properties. An example of a filter is: Find all the properties in Omstead County owned by Peter Vretanos.\r\n\r\nThis standard is used by a number of OGC Web Services, including the Web Feature Service [http://www.opengeospatial.org/standards/wfs], the Catalogue Service [http://www.opengeospatial.org/standards/cat] and the Styled Layer Descriptor Standard [http://www.opengeospatial.org/standards/sld]. \r\n" + "@value": "A fundamental operation performed on a collection of features is that of filtering in order to obtain a subset of the data which contains feature instances that satisfy some filtering criteria. This document specifies\r\n\r\nA filter grammar called Common Query Language (CQL2);\r\n\r\nTwo encodings for CQL2 - a text and a JSON encoding.\r\n\r\nThe Common Query Language (CQL2) defined in this document is a generic filter grammar that can be used to specify how resource instances in a source collection of any item type, including features, can be filtered to identify a results set. Typically, CQL2 is used in query operations to identify the subset of resources, such as features, that should be included in a response document. However, CQL2 can also be used in other operations, such as updates, to identify the subset of resources that should be affected by an operation.\r\n\r\nEach resource instance in the source collection is evaluated against a filtering expression. The filter expression always evaluates to true, false or null. If the expression evaluates to true, the resource instance satisfies the expression and is marked as being in the result set. If the overall filter expression evaluates to false or null, the data instance is not in the result set. Thus, the net effect of evaluating a filter expression is a set of resources that satisfy the predicates in the expression.\r\n\r\nThe Common Query Language and its text encoding are not new, but this is the first time that the language is formally specified. The Common Query Language with the acronym CQL was originally created as a text encoding for use with implementations of the OGC Catalogue Service Implementation Specification. The language is based on the capabilities in the OGC Filter Encoding Standard, which was originally part of the Web Feature Service (WFS) Standard.\r\n\r\nThe Common Query Language as specified in this document is a revision of this earlier version. While the language design including the classification of operators are consistent with the earlier specification, there have been a number of changes and existing implementations of CQL will need to be updated to process filter expressions specified by this document. This document therefore uses the acronym CQL2 to refer to the current version of the Common Query Language." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52371,35 +51329,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-095c1" + "@value": "21-065r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Filter Encoding Implementation Specification Corrigendum 1" + "@value": "Common Query Language (CQL2)" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-080r2", + "@id": "http://www.opengis.net/def/docs/09-153r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-09-20" + "@value": "2012-01-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ryan Franz" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52409,27 +51367,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/17-080r2/17-080r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=46442" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CDB Multi-Spectral Imagery Extension" + "@value": "Web Coverage Service 2.0 Primer: Core and Extensions Overview" }, { "@language": "en", - "@value": "17-080r2" + "@value": "09-153r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The “Multi-Spectral Imagery” extension defines how to encode and store reflected electromagnetic radiation from the infrared wavelengths into a CDB. The portion of the spectrum targeted is between the visible spectrum (current imagery and texture in CDB), and longer wavelength infrared that is primarily emissive and can be simulated based on the material temperature. " + "@value": "This document provides an overview on the OGC Web Coverage Service (WCS) 2.0 suite by describing WCS core and extensions. \r\nIntended target audience are developers intending to implement WCS servers and/or clients. This document aims at providing an overview and giving useful hints and best practices beyond the pure standards texts. It is a "living document" which will evolve to reflect new developments and best practices.\r\nAs such, the contents of this document is informative and not of normative nature.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52440,35 +51398,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-080r2" + "@value": "09-153r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CDB Multi-Spectral Imagery Extension" + "@value": "OGC® Web Coverage Service 2.0 Primer: Core and Extensions Overview" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-087r13", + "@id": "http://www.opengis.net/def/docs/21-067", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-08-28" + "@value": "2021-10-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John R. Herring" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52478,27 +51436,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/as/17-087r13/17-087r13.html" + "@id": "https://docs.ogc.org/dp/21-067.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 01 - Spatial schema" + "@value": "21-067" }, { "@language": "en", - "@value": "17-087r13" + "@value": "OGC: Towards Data Cube Interoperability" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is the ISO 19107:2019 Standard and specifies conceptual schemas for describing the spatial characteristics of geographic entities, and a set of spatial operations consistent with these schemas. It treats vector geometry and topology." + "@value": "Data cubes, multidimensional arrays of data, are used frequently these days, but differences in design, interfaces, and handling of temporal characteristics are causing interoperability challenges for anyone interacting with more than one solution. To address these challenges, the Open Geospatial Consortium (OGC) and the Group on Earth Observation (GEO) invited global data cube experts to discuss state-of-the-art and way forward at the “Towards Data Cube Interoperability” workshop. The two-day workshop, conducted in late April 2021, started with a series of pre-recorded position statements by data cube providers and data cube users. These videos served as the entry points for intense discussions that not only produced a new definition of the term ‘data cube’ (by condensing and shifting emphasize on what is known as the six faces model), but also pointed out a wide variety of expectations with regards to data cube behaviour and characteristics as well as data cube usage patterns. This report summarizes the various perspectives and discusses the next steps towards efficient usage of data cubes. It starts with the new definition of the term Data Cube, as this new understanding drives several recommendations discussed later in this report. The report includes further discussion that followed the actual workshop, mainly conducted in the context of the Geo Data Cube task in OGC Testbed-17." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52509,42 +51467,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-087r13" + "@value": "21-067" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 1 - Spatial schema" + "@value": "OGC: Towards Data Cube Interoperability" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-026r8", + "@id": "http://www.opengis.net/def/docs/13-015", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-11-25" - }, - { - "@type": "xsd:date", - "@value": "2016-12-16" + "@value": "2014-02-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Pedro Gonçalves, Uwe Voges" + "@value": "EO2HEAVEN Consortium" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52554,34 +51505,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/13-026r8/13-026r8.html" + "@id": "https://portal.ogc.org/files/?artifact_id=52675" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC OpenSearch Extension for Earth Observation" - }, - { - "@language": "en", - "@value": "13-026r8" + "@value": "13-015" }, { "@language": "en", - "@value": "OpenSearch Extension for Earth Observation" + "@value": "Provision of Observations through an OGC Sensor Observation Service (SOS)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is the specification for the OpenSearch extension for Earth Observation collections and products search.\r\n\r\nThis standard is intended to provide a very simple way to make queries to a repository that contains Earth Observation information and to allow syndication of repositories." + "@value": "This document comprises experiences and recommendations when using\r\nSensor Web Enablement (SWE) concepts. This document focuses on\r\none basic issue: the provision of observations in an OGC SOS.\r\nThis includes the definition of a lightweight OGC SOS profile (OGC 11-\r\n169r1), an analysis of and contribution to the specification of the Sensor\r\nObservation Service (SOS) 2.0 as well as an approach how the data\r\nused within Earth observation (EO) applications can be integrated more\r\neasily into SOS instances.\r\nThese recommendations result from the work performed in 2010-2013\r\nas part of the research project EO2HEAVEN (Earth Observation and\r\nEnvironmental Modelling for the Mitigation of Health Risks), co-funded\r\nby the European Commission as part of the 7th Framework Programme\r\n(FP7) Environmental theme. EO2HEAVEN contributes to a better understanding\r\nof the complex relationships between environmental changes\r\nand their impact on human health. See http://www.eo2heaven.org/ .\r\nThe lightweight OGC SOS profile has been developed in close cooperation\r\nbetween the FP7 projects EO2HEAVEN and UncertWeb (see\r\nhttp://www.uncertweb.org/ )." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52592,35 +51536,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-026r8" + "@value": "13-015" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OpenSearch Extension for Earth Observation" + "@value": "OGC Best Practice for Sensor Web Enablement: Provision of Observations through an OGC Sensor Observation Service (SOS)" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-028r1", + "@id": "http://www.opengis.net/def/docs/11-113r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-03-24" + "@value": "2011-11-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "OGC Aviation Domain Working Group" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52630,27 +51574,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=62061" + "@id": "https://portal.ogc.org/files/?artifact_id=46171" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-028r1" + "@value": "11-113r1" }, { "@language": "en", - "@value": "Use of Geography Markup Language (GML) for Aviation Data" + "@value": "OWS-8 Information Model for Moving Target Indicators and Moving Object Bookmarks (Engineering Report)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The document provides guidelines for the use of GML and a GML profile description in the\r\nscope of aeronautical data encoding, in particular when using the Aeronautical Information\r\nExchange Model (AIXM). In the future, the applicability of the guidelines contained in this\r\ndocument might be enlarged to cover other related domains, such as aeronautical weather data\r\nand flight data." + "@value": "This report aims at providing an information model for the usage of video moving target indicator data (VMTI), ground moving target indicator (GMTI) and tracking information (STANAG 4676) in the context of standardized spatial data infrastructures compliant to OGC and ISO standards. If possible, precedence was given on using the OGC Sensor Web Enablement suite of standards, as this suite provides a homogeneous suite of standards to express sensor and sensor observation data in the context of OGC. This means that all encodings are based on Observation and Measurements version 2 (O&M) and implemented as an application schema according to the rules of Geography Markup Language version 3.2 (GML). An information model – so called ‘bookmark’ – to conserve the trace from a moving object back to the original base data is discussed briefly. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52661,35 +51605,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-028r1" + "@value": "11-113r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Use of Geography Markup Language (GML) for Aviation Data" + "@value": "OWS-8 Information Model for Moving Target Indicators and Moving Object Bookmarks (Engineering Report)" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-045r1", + "@id": "http://www.opengis.net/def/docs/10-030", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-27" + "@value": "2012-03-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Eric LaMar" + "@value": "Paul Scarponcini" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52699,27 +51643,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=14698" + "@id": "https://www.iso.org/standard/32566.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-045r1" + "@value": "Topic 19 - Geographic information - Linear referencing" }, { "@language": "en", - "@value": "WMS - Proposed Animation Service Extension" + "@value": "10-030" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document explains how the Web Map Server (WMS 1.0 [1] & 1.1 [2,3]) specification can be extended to allow map animations that move in space over time. It should be read in conjunction with the latest version WMS specification. " + "@value": "Same as ISO IS 19148: 2012. Download at http://www.iso.org" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52730,35 +51674,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-045r1" + "@value": "10-030" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "WMS - Proposed Animation Service Extension" + "@value": "Topic 19 - Geographic information - Linear referencing" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-063", + "@id": "http://www.opengis.net/def/docs/06-182r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-15" + "@value": "2007-06-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas H.G. Lankester" + "@value": "Steven Keens" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52768,27 +51712,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21742" + "@id": "https://portal.ogc.org/files/?artifact_id=19424" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Map Services - Application Profile for EO Products" + "@value": "06-182r1" }, { "@language": "en", - "@value": "07-063" + "@value": "Discussions, findings, and use of WPS in OWS-4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC document specifies a constrained, consistent interpretation of the WMS specification that is applicable to government, academic and commercial providers of EO products. " + "@value": "This document reviews the material discussed during the OWS-4 project, describes the WPS processes deployed in the workflows, and offers suggestions to the OGC to move forward with the WPS. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52799,35 +51743,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-063" + "@value": "06-182r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Map Services - Application Profile for EO Products" + "@value": "Discussions, findings, and use of WPS in OWS-4" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-018r1", + "@id": "http://www.opengis.net/def/docs/06-131", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-15" + "@value": "2006-10-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Philippe M" + "@value": "Renato Primavera" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52837,27 +51781,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21465" + "@id": "https://portal.ogc.org/files/?artifact_id=17689" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Sensor Planning Service Application Profile for EO Sensors" + "@value": "06-131" }, { "@language": "en", - "@value": "07-018r1" + "@value": "EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This SPS EO profile document specifies at a lower level the interfaces and parameters for requesting information describing the capabilities of a Sensor Planning Service dedicated to the EO Sensor domain, for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or cancelling such a request, and for requesting information about further OGC Web services that provide access to the data collected by the requested task." + "@value": "This document describes the Data Model of Earth Observation Products for the OGC" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52868,35 +51812,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-018r1" + "@value": "06-131" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Sensor Planning Service Application Profile for EO Sensors" + "@value": "EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-124r1", + "@id": "http://www.opengis.net/def/docs/19-015", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-07-15" + "@value": "2020-02-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Stephane Fellah" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52906,27 +51850,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39467" + "@id": "https://docs.ogc.org/per/19-015.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-124r1" + "@value": "19-015" }, { "@language": "en", - "@value": "OGC Identifiers - the case for http URIs" + "@value": "OGC Testbed-15: Federated Cloud Provenance ER" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC provides a large number of resources to support the construction of spatial\r\ndata infrastructures, including documents, specifications, schemas and concept\r\ndefinitions. When deployed, the infrastructures require persistent reference to these\r\nresources, enabled by persistent identifiers. This may be at various level of\r\ngranularity. " + "@value": "The emergence of Federated Cloud processing and ‘Big Data’ have raised many concerns over the use to which data is being put. This led to new requirements for methodologies, and capabilities which can address transparency and trust in data provenance in the Cloud. Distributed Ledger Technologies (DLTs) and more specifically blockchains, have been proposed as a possible platform to address provenance. This OGC Testbed 15 Engineering Report (ER) is a study of the application of DLTs for managing provenance information in Federated Clouds." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -52937,42 +51881,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-124r1" + "@value": "19-015" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Identifiers - the case for http URIs" + "@value": "OGC Testbed-15: Federated Cloud Provenance ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-066", + "@id": "http://www.opengis.net/def/docs/13-084r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-07-12" - }, - { - "@type": "xsd:date", - "@value": "2014-01-31" + "@value": "2014-04-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Linda van den Brink, Jantien Stoter, Sisi Zlatanova" + "@value": "Uwe Voges, Frédéric Houbie, Nicolas Lesage, Marie-Lise Vautier" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" - }, - { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -52982,33 +51919,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=49000" - }, - { - "@id": "https://portal.ogc.org/files/?artifact_id=49000&version=2" + "@id": "https://portal.ogc.org/files/?artifact_id=56905" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-066" + "@value": "I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0" }, { "@language": "en", - "@value": "Modeling an application domain extension of CityGML in UML" + "@value": "13-084r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" - }, - { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This paper presents key aspects of the development of a Dutch 3D standard IMGeo as a CityGML ADE. The new ADE is modeled using UML class diagrams. However the OGC CityGML specification does not provide clear rules on modeling an ADE in UML. This paper describes how the extension was built, which provides general insight how CityGML can be extended for a specific applications starting from the UML diagrams. Several alternatives for modeling ADEs in UML have been investigated and compared. The best suited for the 3D standard option is selected and applied. Open issues and challenges are discussed in the conclusions." + "@value": "The OGC Catalogue Services 2.0 specification (OGC 07-006r1) establishes a general framework for implementing catalogue services that can be applied to meet the needs of stakeholders in a wide variety of domains.\r\nThe ebRIM application profile (OGC 07-110r4) is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0 specification; it qualifies as a ‘Class 2’ profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards. The ebRIM application profile also includes a Basic extension package (OGC 07-144r4) of the OASIS ebXML Registry Information Model (ebRIM) providing artefacts of general utility in the geomatics domain.\r\nThis document provides an extension package aligned with the ebRIM application profile of CS-W for the cataloguing of ISO 19115, ISO19115-2 and ISO 19119 compliant metadata. It was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [HMA] and related projects. Some input came from the OGC OWS9 initiative.\r\nThis document supersedes the former document OGC Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W, OGC 07-038r3 (Version: 0.1.12).\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -53019,35 +51950,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-066" + "@value": "13-084r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Modeling an application domain extension of CityGML in UML" + "@value": "OGC I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-140", + "@id": "http://www.opengis.net/def/docs/10-020", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-06-08" + "@value": "2014-04-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Dr. Markus M" + "@value": "Paul Cooper" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -53057,27 +51988,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=19084" + "@id": "https://portal.ogc.org/files/?artifact_id=37761" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Feature Styling IPR" + "@value": "Topic 02.1 - Spatial Referencing by Coordinates - Extension for Parametric Values" }, { "@language": "en", - "@value": "06-140" + "@value": "10-020" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Feature Styling is based on a distributed computational platform that employs a number\r\nof standard interfaces and encodings to allow for flexible, scalable and interoperable\r\nmanagement of symbology (styles and symbols) in the process of producing maps from\r\ndifferent kinds of data, most important being source GML data.\r\n" + "@value": "" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -53088,35 +52019,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-140" + "@value": "10-020" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Feature Styling IPR" + "@value": "Topic 2.1 - Spatial Referencing by Coordinates - Extension for Parametric Values" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-048r3", + "@id": "http://www.opengis.net/def/docs/99-051", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-01-25" + "@value": "1999-07-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Harrison" + "@value": "Doug Nebert" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -53126,27 +52057,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=65420" + "@id": "https://portal.ogc.org/files/?artifact_id=831" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-048r3" + "@value": "99-051" }, { "@language": "en", - "@value": "Testbed-11 NIEM & IC Data Encoding Specification Assessment and Recommendations Engineering Report" + "@value": "Catalog Interface" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community\r\n(IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0\r\narchitecture through the development, implementations, test, and robust demonstration\r\nmaking use of IC specifications, Geography Markup Language (GML), and NIEM in a\r\nsimulated “real-world” scenario. The demonstration scenario begins with NIEMconformant\r\nInformation Exchange Packages (IEPs) containing operational data and IC\r\nsecurity tags from the Information Security Marking (ISM) and Need-To-Know (NTK)\r\naccess control metadata, and the Trusted Data Format (TDF) for binding assertion\r\nmetadata with data resource(s). Those instance documents are deployed on Open\r\nGeospatial Consortium (OGC) Web Services to be used by client applications. Access\r\ncontrol is based on attributes of the end-user and the instance data.\r\nRecommendations to update these information exchanges were provided to reflect NIEM\r\n3.0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment\r\nexercised this data encoding in OGC Web Feature Services (WFS) and Policy\r\nEnforcement Points (PEP) accessed by multiple client applications. Results from this task\r\nprovided a preliminary architecture that was tested and demonstrated in Testbed 11, and\r\nsummarized in other OGC Testbed 11 Engineering Reports." + "@value": "Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -53157,35 +52088,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-048r3" + "@value": "99-051" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-11 NIEM & IC Data Encoding Specification Assessment and Recommendations Engineering Report" + "@value": "Catalog Interface" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-010r1", + "@id": "http://www.opengis.net/def/docs/18-048r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-05-04" + "@value": "2019-03-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Schut" + "@value": "Howard Butler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -53195,27 +52126,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=5858" + "@id": "https://docs.ogc.org/per/18-048r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geolinked Data Access Service" + "@value": "Point Cloud Data Handling Engineering Report" }, { "@language": "en", - "@value": "04-010r1" + "@value": "18-048r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A Geolinked Data Access Service (GDAS) provides a way to publish and access data that refers to spatial features (e.g. population data for countries). A GDAS can expose data from non-GIS databases so that it can be manipulated and mapped with the aid of a Geolinking Service." + "@value": "This Engineering Report (ER) describes requirements that a point cloud web service must satisfy to enable application developers to provide convenient remote access to point clouds. It provides a short contrast of five point cloud web service software approaches (Esri I3S, 3D Tiles, Greyhound, PotreeConverter, and Entwine) and their implementations available at the time of the report. A small industry survey about these requirements is also provided in support of the report’s discussion about formats, web service requirements, industry support, and industry desire on these topics.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -53226,35 +52157,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-010r1" + "@value": "18-048r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geolinked Data Access Service" + "@value": "OGC Testbed-14: Point Cloud Data Handling Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-110", + "@id": "http://www.opengis.net/def/docs/16-007r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-04-07" + "@value": "2017-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman" + "@value": "Sara Saeedi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -53264,27 +52195,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=897" + "@id": "https://portal.ogc.org/files/?artifact_id=72723" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "99-110" + "@value": "16-007r3" }, { "@language": "en", - "@value": "Topic 10 - Feature Collections" + "@value": "Volume 11: OGC CDB Core Standard Conceptual Model" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "An OpenGIS Feature Collection is an abstract object consisting of Feature Instances, their Feature Schema, and Project Schema." + "@value": "This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB 1.0 Standard. The objective of this document is to provide an abstract core conceptual model for a CDB data store (repository). The model is represented using UML (unified modeling language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering a UML model and documentation from the OGC CDB standard as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -53295,35 +52226,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-110" + "@value": "16-007r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 10 - Feature Collections" + "@value": "Volume 11: OGC CDB Core Standard Conceptual Model" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-100", + "@id": "http://www.opengis.net/def/docs/13-053r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-11-06" + "@value": "2014-02-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus " + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -53333,27 +52264,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55231" + "@id": "https://portal.ogc.org/files/?artifact_id=55244" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "13-100" + "@value": "CHISP-1 Engineering Report" }, { "@language": "en", - "@value": "Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core" + "@value": "13-053r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard defines the version 3.0 of a geospatial extension to the OASIS eXtensible Access Control Markup Language (XACML) Version 3.0 standard. It thereby enables the interoperable definition of access rights / constraints using the XACML 3.0 language, processing model and policy schema but extends the ability to phrase conditions on geographic characteristics of subjects, resources and objects. \r\nIn that sense, a GeoXACML policy could restrict access to geospatial information, e.g. provided by OGC Web Services. However, a GeoXACML policy could also restrict access to non geospatial assets by stating restrictions for access based on the location of the user (or the mobile device used) trying to access the protected assets. Therefore, this standard applies to main stream IT.\r\nFor enabling processing of access control decisions based on geometry, Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core inherits by normative reference ISO 19125 which defines a geometry model and functions on geometry instances which enrich the XACML 3.0 specification. \r\n" + "@value": "This document provides a technical description of the work completed for the Climatology-Hydrology Information Sharing Pilot, Phase 1 project. \r\nThis document describes a profile of SOS, the NRCan GIN SOS 2.0 profile, developed in order to define a baseline of interoperability among the sensor observation services used in the project.\r\nThis document describes the use cases used to drive the component development during the project. The first use case was a flood scenario that involved exchanging cross-border hydrologic data with a unified alert service. The second use case involved calculating nutrient loads to the Great Lakes, which also involved the cross-border exchange of analytic data.\r\nThis document describes each component developed during the project and the challenges encountered and overcome during the development. The newly developed components include a nutrient load calculation client, a SOS integrating water quality data form the U.S. and Canada, a nutrient load calculation service, an upstream gauge service, a subscription client, and an event notification service composed of a number of sub-components including a subscription broker, an observation harvester and a CAP alert client.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -53364,35 +52295,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-100" + "@value": "13-053r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core" + "@value": "OGC® CHISP-1 Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-039", + "@id": "http://www.opengis.net/def/docs/16-008", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-09-22" + "@value": "2017-01-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Louis Rose" + "@value": "GeoSciML Modeling Team" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -53402,27 +52333,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=6669" + "@id": "https://docs.ogc.org/is/16-008/16-008.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-039" + "@value": "Geoscience Markup Language 4.1" }, { "@language": "en", - "@value": "Geospatial Portal Reference Architecture" + "@value": "16-008" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Guide has been developed by the members of the Open Geospatial Consortium, Inc. to assist the global geospatial technology community in implementing standards-based geospatial portal solutions that are compatible with Spatial Data Infrastructures in every nation. We offer this document as a resource for rapid development and informed acquisition of portals and portal-exploiting applications that can plug and play with geospatial data and services in your organization and other organizations in your community and around the world. " + "@value": "GeoSciML is a model of geological features commonly described and portrayed in geological maps, cross sections, geological reports and databases. The model was developed by the IUGS CGI (Commission for the Management and Application of Geoscience Information) and version 4.1 is the first version officially submitted as an OGC standard. This specification describes a logical model and GML/XML encoding rules for the exchange of geological map data, geological time scales, boreholes, and metadata for laboratory analyses. It includes a Lite model, used for simple map-based applications; a basic model, aligned on INSPIRE, for basic data exchange; and an extended model to address more complex scenarios. \r\n\r\nThe specification also provides patterns, profiles (most notably of Observations and Measurements - ISO19156), and best practices to deal with common geoscience use cases. \r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -53433,30 +52364,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-039" + "@value": "16-008" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geospatial Portal Reference Architecture" + "@value": "OGC Geoscience Markup Language 4.1 (GeoSciML)" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-065r1", + "@id": "http://www.opengis.net/def/docs/11-134", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-11-18" + "@value": "2012-05-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Eric Hirschorn, Peter Baumann" + "@value": "Rob Cass, Mark Simms" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -53471,17 +52402,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64145" + "@id": "https://portal.ogc.org/files/?artifact_id=46372" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed11 Referenceable Grid Harmonization Engineering Report" + "@value": "11-134" }, { "@language": "en", - "@value": "15-065r1" + "@value": "OWS-8 Tracking: Moving Target Indicator Process, Workflows and Implementation Results ER" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -53491,7 +52422,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report is a deliverable of the Testbed-11 Urban Climate Resilience (UCR) Thread. The UCR Thread responds to the urgent need to make climate information and related data readily available for the public and government decision makers to prepare for changes in the Earth’s climate. An important set of a data sources that will play an important role in detecting changes due to climate effects are a wide array of remote imaging systems." + "@value": "The scope of this report is to provide a description of services, data storage and data\r\nmovement within the OWS-8 Tracking sub-thread. The paper outlines the development\r\nof Sensor Observation Services (SOS), a Web Feature Service(WFS), a Notification\r\nService and a Web Processing Service (WPS) for generating track features. Additionally,\r\nimplemented encodings will be discussed as examples and in comparison to the\r\nencodings detailed in (Simonis, 2011)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -53502,142 +52433,557 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-065r1" + "@value": "11-134" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed11 Referenceable Grid Harmonization Engineering Report" + "@value": "OWS-8 Tracking: Moving Target Indicator Process, Workflows and Implementation Results ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-087", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/doc-type/is", + "http://www.w3.org/2004/02/skos/core#narrower": [ { - "@type": "xsd:date", - "@value": "2010-08-18" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/18-010r7" + }, + { + "@id": "http://www.opengis.net/def/docs/01-009" + }, + { + "@id": "http://www.opengis.net/def/docs/05-077r4" + }, + { + "@id": "http://www.opengis.net/def/docs/05-007r7" + }, + { + "@id": "http://www.opengis.net/def/docs/07-036" + }, + { + "@id": "http://www.opengis.net/def/docs/08-094r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-168r6" + }, + { + "@id": "http://www.opengis.net/def/docs/12-176r7" + }, + { + "@id": "http://www.opengis.net/def/docs/16-101r2" + }, + { + "@id": "http://www.opengis.net/def/docs/15-112r2" + }, + { + "@id": "http://www.opengis.net/def/docs/05-047r3" + }, + { + "@id": "http://www.opengis.net/def/docs/22-050r1" + }, + { + "@id": "http://www.opengis.net/def/docs/20-050" + }, + { + "@id": "http://www.opengis.net/def/docs/23-008r3" + }, + { + "@id": "http://www.opengis.net/def/docs/14-005r3" + }, + { + "@id": "http://www.opengis.net/def/docs/18-058r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-007r2" + }, + { + "@id": "http://www.opengis.net/def/docs/15-098r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-009r6" + }, + { + "@id": "http://www.opengis.net/def/docs/10-090r3" + }, + { + "@id": "http://www.opengis.net/def/docs/17-080r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-001" + }, + { + "@id": "http://www.opengis.net/def/docs/10-157r4" + }, + { + "@id": "http://www.opengis.net/def/docs/16-032r3" + }, + { + "@id": "http://www.opengis.net/def/docs/19-086r4" + }, + { + "@id": "http://www.opengis.net/def/docs/22-049r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-057r7" + }, + { + "@id": "http://www.opengis.net/def/docs/20-058" + }, + { + "@id": "http://www.opengis.net/def/docs/07-147r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-043r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-120r3" + }, + { + "@id": "http://www.opengis.net/def/docs/15-111r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-100r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-127r2" + }, + { + "@id": "http://www.opengis.net/def/docs/16-060r2" + }, + { + "@id": "http://www.opengis.net/def/docs/21-065r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-068r2" + }, + { + "@id": "http://www.opengis.net/def/docs/17-069r4" + }, + { + "@id": "http://www.opengis.net/def/docs/16-007r5" + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r18" + }, + { + "@id": "http://www.opengis.net/def/docs/07-098r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-008r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-144r4" + }, + { + "@id": "http://www.opengis.net/def/docs/16-102r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-080r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-068r3" + }, + { + "@id": "http://www.opengis.net/def/docs/21-057" + }, + { + "@id": "http://www.opengis.net/def/docs/09-110r4" + }, + { + "@id": "http://www.opengis.net/def/docs/13-131r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-084r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-000" + }, + { + "@id": "http://www.opengis.net/def/docs/09-000" + }, + { + "@id": "http://www.opengis.net/def/docs/21-056r11" + }, + { + "@id": "http://www.opengis.net/def/docs/15-112r3" + }, + { + "@id": "http://www.opengis.net/def/docs/14-055r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-088" + }, + { + "@id": "http://www.opengis.net/def/docs/06-121r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-106r2" + }, + { + "@id": "http://www.opengis.net/def/docs/16-071r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-007r3" + }, + { + "@id": "http://www.opengis.net/def/docs/07-000" + }, + { + "@id": "http://www.opengis.net/def/docs/18-058" + }, + { + "@id": "http://www.opengis.net/def/docs/11-017" + }, + { + "@id": "http://www.opengis.net/def/docs/09-083r3" + }, + { + "@id": "http://www.opengis.net/def/docs/08-007r1" + }, + { + "@id": "http://www.opengis.net/def/docs/19-086r5" + }, + { + "@id": "http://www.opengis.net/def/docs/06-042" + }, + { + "@id": "http://www.opengis.net/def/docs/15-045r7" + }, + { + "@id": "http://www.opengis.net/def/docs/10-126r4" + }, + { + "@id": "http://www.opengis.net/def/docs/18-062r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-067r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-079" + }, + { + "@id": "http://www.opengis.net/def/docs/15-043r3" + }, + { + "@id": "http://www.opengis.net/def/docs/13-057r1" + }, + { + "@id": "http://www.opengis.net/def/docs/13-026r8" + }, + { + "@id": "http://www.opengis.net/def/docs/15-001r4" + }, + { + "@id": "http://www.opengis.net/def/docs/15-078r6" + }, + { + "@id": "http://www.opengis.net/def/docs/16-104r2" + }, + { + "@id": "http://www.opengis.net/def/docs/04-094" + }, + { + "@id": "http://www.opengis.net/def/docs/22-022r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-085r4" + }, + { + "@id": "http://www.opengis.net/def/docs/16-107r2" + }, + { + "@id": "http://www.opengis.net/def/docs/10-032r8" + }, + { + "@id": "http://www.opengis.net/def/docs/17-003r2" + }, + { + "@id": "http://www.opengis.net/def/docs/10-129r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-052r4" + }, + { + "@id": "http://www.opengis.net/def/docs/22-047r1" + }, + { + "@id": "http://www.opengis.net/def/docs/21-026" + }, + { + "@id": "http://www.opengis.net/def/docs/06-104r4" + }, + { + "@id": "http://www.opengis.net/def/docs/19-045r3" + }, + { + "@id": "http://www.opengis.net/def/docs/15-113r5" + }, + { + "@id": "http://www.opengis.net/def/docs/17-007r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r12" + }, + { + "@id": "http://www.opengis.net/def/docs/17-069r3" + }, + { + "@id": "http://www.opengis.net/def/docs/19-079r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r17" + }, + { + "@id": "http://www.opengis.net/def/docs/05-078r4" + }, + { + "@id": "http://www.opengis.net/def/docs/07-068r4" + }, + { + "@id": "http://www.opengis.net/def/docs/19-086r6" + }, + { + "@id": "http://www.opengis.net/def/docs/10-025r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-024r4" + }, + { + "@id": "http://www.opengis.net/def/docs/16-007r4" + }, + { + "@id": "http://www.opengis.net/def/docs/16-008" + }, + { + "@id": "http://www.opengis.net/def/docs/17-083r2" + }, + { + "@id": "http://www.opengis.net/def/docs/22-051r7" + }, + { + "@id": "http://www.opengis.net/def/docs/10-070r2" + }, + { + "@id": "http://www.opengis.net/def/docs/20-010" + }, + { + "@id": "http://www.opengis.net/def/docs/14-111r6" + }, + { + "@id": "http://www.opengis.net/def/docs/18-073r2" + }, + { + "@id": "http://www.opengis.net/def/docs/16-032r2" + }, + { + "@id": "http://www.opengis.net/def/docs/10-140r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r14" + }, + { + "@id": "http://www.opengis.net/def/docs/19-072" + }, + { + "@id": "http://www.opengis.net/def/docs/09-148r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-030r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r19" + }, + { + "@id": "http://www.opengis.net/def/docs/07-074" + }, + { + "@id": "http://www.opengis.net/def/docs/15-108r3" + }, + { + "@id": "http://www.opengis.net/def/docs/14-065" + }, + { + "@id": "http://www.opengis.net/def/docs/15-112r4" + }, + { + "@id": "http://www.opengis.net/def/docs/06-103r4" + }, + { + "@id": "http://www.opengis.net/def/docs/17-066r1" + }, + { + "@id": "http://www.opengis.net/def/docs/19-008r4" + }, + { + "@id": "http://www.opengis.net/def/docs/17-083r4" + }, + { + "@id": "http://www.opengis.net/def/docs/08-028r7" + }, + { + "@id": "http://www.opengis.net/def/docs/17-079r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-149r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-005" + }, + { + "@id": "http://www.opengis.net/def/docs/17-047r1" + }, + { + "@id": "http://www.opengis.net/def/docs/14-084r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-000r2" + }, + { + "@id": "http://www.opengis.net/def/docs/14-100r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-019" + }, + { + "@id": "http://www.opengis.net/def/docs/12-132r4" + }, + { + "@id": "http://www.opengis.net/def/docs/20-057" + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r10" + }, + { + "@id": "http://www.opengis.net/def/docs/99-050" + }, + { + "@id": "http://www.opengis.net/def/docs/17-066r2" + }, + { + "@id": "http://www.opengis.net/def/docs/06-131r6" + }, + { + "@id": "http://www.opengis.net/def/docs/08-059r3" + }, + { + "@id": "http://www.opengis.net/def/docs/11-014r3" + }, + { + "@id": "http://www.opengis.net/def/docs/07-006r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-100r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-000" + }, + { + "@id": "http://www.opengis.net/def/docs/21-006r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-026r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-085r5" + }, + { + "@id": "http://www.opengis.net/def/docs/16-103r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-006" + }, + { + "@id": "http://www.opengis.net/def/docs/15-042r3" + }, + { + "@id": "http://www.opengis.net/def/docs/15-042r5" + }, + { + "@id": "http://www.opengis.net/def/docs/07-099r1" + }, { - "@value": "Wenli Yang, Liping Di" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/11-165r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/16-105r2" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/17-089r1" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=40139" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/06-121r9" + }, { - "@language": "en", - "@value": "OWS-7 Motion Imagery Discovery and Retrieval Engineering Report" + "@id": "http://www.opengis.net/def/docs/06-141r6" }, { - "@language": "en", - "@value": "10-087" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/09-146r6" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/15-113r6" + }, { - "@value": "This Motion Imagery Discovery and Retrieval Engineering Report (ER) documents the metadata used to tag geolocation of Motion Imagery (MI) for discovery, retrieval and linkage with other data sources over the same location, especially the metadata information required to geometrically co-register multiple motion images at pixel level so that data recorded at different times (e.g., different days) and/or by different providers for common or overlapped FOVs can be compared and pixel level changes among the different images can be accurately detected and delineated. This ER reflects one of the achievements during the OWS 7 Sensor Fusion Enablement (SFE) thread, which builds on the OGC Sensor Web Enablement framework that has achieved a degree of maturity through previous OWS interoperability initiatives and deployments worldwide. " - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/13-133r1" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/09-025r2" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-087" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/15-113r3" + }, { - "@language": "en", - "@value": "OWS-7 Motion Imagery Discovery and Retrieval Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/ug/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "@id": "http://www.opengis.net/def/docs/19-011r4" + }, { - "@value": "Documents of type User Guide" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/99-054" + }, { - "@value": "Documents of type User Guide" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/16-083r2" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ + "@id": "http://www.opengis.net/def/docs/07-110r4" + }, { - "@id": "http://www.opengis.net/def/docs/21-074" + "@id": "http://www.opengis.net/def/docs/15-097r1" }, { - "@id": "http://www.opengis.net/def/docs/22-000" + "@id": "http://www.opengis.net/def/docs/15-018r2" }, { - "@id": "http://www.opengis.net/def/docs/21-075" + "@id": "http://www.opengis.net/def/docs/17-086r3" }, { - "@id": "http://www.opengis.net/def/docs/20-066" + "@id": "http://www.opengis.net/def/docs/08-085r8" }, { - "@id": "http://www.opengis.net/def/docs/20-071" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/11-038R2" + }, { - "@value": "Documents of type User Guide" + "@id": "http://www.opengis.net/def/docs/15-042r6" + }, + { + "@id": "http://www.opengis.net/def/docs/14-083r2" + }, + { + "@id": "http://www.opengis.net/def/docs/23-024" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-146r6", + "@id": "http://www.opengis.net/def/docs/07-057r7", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-09-15" + "@value": "2010-04-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann, Eric Hirschorn, Joan Masó" + "@value": "Joan Masó, Keith Pomakis, Núria Julià" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -53652,17 +52998,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/09-146r6/09-146r6.html" + "@id": "https://portal.ogc.org/files/?artifact_id=35326" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Coverage Implementation Schema" + "@value": "07-057r7" }, { "@language": "en", - "@value": "09-146r6" + "@value": "Web Map Tile Service Implementation Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -53672,7 +53018,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Coverages represent homogeneous collections of values located in space/time, such as spatio-temporal sensor, image, simulation, and statistics data. Common examples include 1-D timeseries, 2-D imagery, 3-D x/y/t image timeseries and x/y/z geophysical voxel models, as well as 4-D x/y/z/t climate and ocean data. Generally, coverages encompass multi-dimen­sional regular and irregular grids, point clouds, and general meshes.\r\n\r\nThis Coverage Implementation Schema (CIS) specifies the OGC coverage model by establishing a concrete, interoperable, conformance-testable coverage structure. It is based on the abstract concepts of OGC Abstract Topic 6 [1] (which is identical to ISO 19123) which spec­i­fies an abstract model which is not per se interoperable – in other words, many different and incompatible implementations of the abstract model are possible. CIS, on the other hand, is interoperable in the sense that coverages can be conformance tested, regardless of their data format encoding, down to the level of single “pixels” or “voxels.”\r\n\r\nCoverages can be encoded in any suitable format (such as GML, JSON, GeoTIFF, or Net­CDF) and can be partitioned, e.g., for a time-interleaved representation. Coverages are independent from service definitions and, therefore, can be accessed through a variety of OGC services types, such as the Web Coverage Service (WCS) Standard [8]. The coverage structure can serve a wide range of coverage application domains, thereby contributing to harmon­ization and interoperability between and across these domains." + "@value": "This Web Map Tile Service (WMTS) Implementation Standard provides a standard based solution to serve digital maps using predefined image tiles. The service advertises the tiles it has available through a standardized declaration in the ServiceMetadata document common to all OGC web services. This declaration defines the tiles available in each layer (i.e. each type of content), in each graphical representation style, in each format, in each coordinate reference system, at each scale, and over each geographic fragment of the total covered area. The ServiceMetadata document also declares the communication protocols and encodings through which clients can interact with the server. Clients can interpret the ServiceMetadata document to request specific tiles." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -53683,104 +53029,55 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-146r6" + "@value": "07-057r7" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Coverage Implementation Schema" + "@value": "OpenGIS Web Map Tile Service Implementation Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-134", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ - { - "@type": "xsd:date", - "@value": "2012-05-15" - } - ], - "http://purl.org/dc/terms/creator": [ - { - "@value": "Rob Cass, Mark Simms" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ - { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ - { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ - { - "@id": "https://portal.ogc.org/files/?artifact_id=46372" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/doc-type/ug", + "http://www.w3.org/2004/02/skos/core#narrower": [ { - "@language": "en", - "@value": "11-134" + "@id": "http://www.opengis.net/def/docs/21-074" }, { - "@language": "en", - "@value": "OWS-8 Tracking: Moving Target Indicator Process, Workflows and Implementation Results ER" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ - { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "The scope of this report is to provide a description of services, data storage and data\r\nmovement within the OWS-8 Tracking sub-thread. The paper outlines the development\r\nof Sensor Observation Services (SOS), a Web Feature Service(WFS), a Notification\r\nService and a Web Processing Service (WPS) for generating track features. Additionally,\r\nimplemented encodings will be discussed as examples and in comparison to the\r\nencodings detailed in (Simonis, 2011)." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/20-066" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/20-071" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-134" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/21-075" + }, { - "@language": "en", - "@value": "OWS-8 Tracking: Moving Target Indicator Process, Workflows and Implementation Results ER" + "@id": "http://www.opengis.net/def/docs/22-000" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-050r1", + "@id": "http://www.opengis.net/def/docs/03-062r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-06-30" + "@value": "2003-06-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Zarr Developers" + "@value": "Richard Martell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -53790,27 +53087,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/100727" + "@id": "https://portal.ogc.org/files/?artifact_id=1271" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Zarr Storage Specification 2.0 Community Standard" + "@value": "03-062r1" }, { "@language": "en", - "@value": "21-050r1" + "@value": "Critical Infrastructure Collaborative Environment Architecture: Information Viewpoint" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Community Standard refers to the Zarr V2 Specification. The Zarr V2 Specification\r\nis hosted on the Zarr website at https://zarr.readthedocs.io/en/stable/spec/v2.html. The\r\nZarr V2 Specification is the OGC Community Standard. Everything that follows is a\r\nnon-normative, informal description of Zarr usage written for the benefit of the geospatial\r\ncommunity." + "@value": "*RETIRED* specifies the information viewpoint for the Critical Infrastructure Collaborative Environment (CICE)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -53821,35 +53118,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-050r1" + "@value": "03-062r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Zarr Storage Specification 2.0 Community Standard" + "@value": "Critical Infrastructure Collaborative Environment Architecture: Information Viewpoint" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-026r1", + "@id": "http://www.opengis.net/def/docs/06-131r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-03-28" + "@value": "2008-07-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Serge Margoulies" + "@value": "Renato Primavera" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -53859,27 +53156,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1031" + "@id": "https://portal.ogc.org/files/?artifact_id=28152" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "01-026r1" + "@value": "06-131r4" }, { "@language": "en", - "@value": "Geocoder" + "@value": "OGC® Catalogue Services Specification 2.0 Extension Package for ebRIM (ISO/TS 15000-3) Application Profile: Earth Observation" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*RETIRED* Geocoding is the process of linking words, terms and codes found in a text string to their applicable geospatial features, with known locations. (Locations are defined as geometry; usually points with x, y coordinates.)" + "@value": "This OGC® document specifies the Earth Observation Products Extension Package for ebRIM (ISO/TS 15000-3) Application Profile of CSW 2.0, based on the [OGC 06-080r3] OGC® GML Application Schema for EO Products." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -53890,35 +53187,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-026r1" + "@value": "06-131r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geocoder" + "@value": "EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-060r1", + "@id": "http://www.opengis.net/def/docs/15-022", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-02-17" + "@value": "2015-08-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jerome Sonnett" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -53928,27 +53225,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8348" + "@id": "https://portal.ogc.org/files/?artifact_id=63312" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS 2 Common Architecture: WSDL SOAP UDDI" + "@value": "Testbed 11 Engineering Report: Implementing Common Security Across the OGC Suite of Service Standards" }, { "@language": "en", - "@value": "04-060r1" + "@value": "15-022" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC document reports the work that occurred in the OWS2 Test Bed Common Architecture thread. This thread focused on the use of UDDI/WSDL/SOAP in the OGC Web Services architecture. It also provides guidelines for the use of these technologies. " + "@value": "This OGC Engineering Report (ER) focuses on describing Common Security for all OGC\r\nWeb Service Standards. This work was performed as part of the OGC Testbed 11\r\nactivity." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -53959,35 +53256,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-060r1" + "@value": "15-022" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS 2 Common Architecture: WSDL SOAP UDDI" + "@value": "OGC® Testbed 11 Engineering Report: Implementing Common Security Across the OGC Suite of Service Standards" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-140r1", + "@id": "http://www.opengis.net/def/docs/23-043", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-28" + "@value": "2024-07-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Kyoung-Sook KIM, Hirotaka OGAWA" + "@value": "Liping Di, David J. Meyer,r Eugene Yu" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -53997,27 +53294,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/16-140r1/16-140r1.html" + "@id": "https://docs.ogc.org/per/23-043.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-140r1" + "@value": "23-043" }, { "@language": "en", - "@value": "OGC Moving Features Encoding Extension - JSON" + "@value": "OGC Testbed 19 Analysis Ready Data Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document proposes a JavaScript Object Notation (JSON) encoding representation of movement of geographic features as an encoding extension of OGC Moving Features ([OGC 14-083r2] and [OGC 14-084r2]). A moving feature, typically a vehicle and pedestrian, can be expressed as a temporal geometry whose location continuously changes over time and contains dynamic non-spatial attributes whose values vary with time. This Best Practice describes how to share moving feature data based on JSON and GeoJSON (a JSON format for encoding geographic data structures). In addition, this document provides an example of RESTful approaches as a Feature Service Interface that has the potential for simplicity, scalability, and resilience with respect to exchange of moving feature data across the Web." + "@value": "Implementations of the Analysis Ready Data (ARD) concept are consistent with the FAIR principles of finding, accessing, interoperating, and reusing physical, social, and applied science data with ease. The goal of this Testbed 19 OGC Engineering Report (ER) is to advance the provision of geospatial information by creating, developing, identifying, and implementing ARD definitions and capabilities. Specifically, this ER aims to increase the ease of use of ARD through improved backend standardization and varied application scenarios. Additionally, this work seeks to inform ARD implementers and users about standards and workflows to enhance the capabilities and operations of ARD. Ultimately, the goal of the work described in this ER is to maximize ARD capabilities and operations and contribute to the enhancement of geospatial information provision.\r\n\r\nFour distinct scenarios – gentrification, synthetic data, coverage analysis, and coastal studies – are explored to reveal both the strengths and limitations of the current ARD framework. The gentrification scenario, which utilizes existing Committee on Earth Observation Satellites (CEOS) ARD data, highlights the need to expand ARD’s scope beyond Earth Observation (EO) data. The integration of diverse data types, such as building footprints and socio-economic statistics, is crucial for comprehensive analysis. The synthetic data scenario explores the potential of simulated EO imagery to enhance data availability and diversity for machine learning applications. However, challenges in standardization and quality assessment require further investigation. The analysis of coverages for ARD reveals the importance of clear pixel interpretation (“pixel-is-point” vs. “pixel-is-area”) and standardized units of measure for seamless integration and analysis. Additionally, enriching the metadata structure with defined extensions is crucial for efficient data discovery and understanding. The coastal study scenario, where in-situ data needs to be elevated to ARD, emphasizes the need for flexible levels of readiness. Different analytical tasks may require distinct data properties, necessitating adaptable standards that cater to temporal emphasis, spatial alignment, and non-GIS applications like machine learning.\r\n\r\nThis work identified several key areas for improvement:\r\n\r\nencompassing non-EO data such as building footprints, socio-economic statistics, synthetic data, and in-situ measurements;\r\nestablishing guidelines and quality controls for incorporating diverse data types;\r\ntailoring data specifications to accommodate different analytical needs, including temporal emphasis and non-GIS applications; and\r\nimplementing structured metadata with defined extensions for enhanced data discovery, understanding, and provenance tracking.\r\nIn addition to the above recommendations, the interoperability and support of ARD in wider communities warrants further exploration and implementation. Additionally, areas such as uniform evaluation and compliance certification could be further investigated to ensure consistency in data readiness across various hierarchies and application domains." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -54028,59 +53325,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-140r1" + "@value": "23-043" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Moving Features Encoding Extension - JSON" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/isx", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/11-053r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-049" - }, - { - "@id": "http://www.opengis.net/def/docs/12-039" - }, - { - "@id": "http://www.opengis.net/def/docs/12-040" - }, - { - "@id": "http://www.opengis.net/def/docs/08-059r4" - }, - { - "@id": "http://www.opengis.net/def/docs/10-092r3" - }, - { - "@id": "http://www.opengis.net/def/docs/13-084r2" - }, - { - "@id": "http://www.opengis.net/def/docs/10-135" + "@value": "OGC Testbed 19 Analysis Ready Data Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-056", + "@id": "http://www.opengis.net/def/docs/11-085r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-15" + "@value": "2011-11-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Harrison" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -54095,17 +53363,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-056.html" + "@id": "https://portal.ogc.org/files/?artifact_id=46679" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-056" + "@value": "11-085r1" }, { "@language": "en", - "@value": "Testbed-12 TopoJSON, GML Engineering Report" + "@value": "OWS-8 Bulk Geodata Transfer Using GML Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -54115,7 +53383,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC document evaluates TopoJSON as an encoding that may be delivered across a common, standard OGC service interface such as WFS." + "@value": "This document describes the work done during the OWS-8 test bed investigating methods and apparatus for distributing individual geospatial data sets and/or collections of data sets in a consistent manner between machines that may or may not be connected via a network. The investigation focuses on the initialization of a target WFS, from a source WFS, for the purpose of GeoSynchronization. Data, schema, metadata and/or topology are exported from a source WFS, transferred to a target WFS (either electronically or physically via some media) and then imported into the target WFS. From that point on, the two WFS's are maintained in synchrony using a Geosynchronization Service (see OGC 10-069r2)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -54126,35 +53394,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-056" + "@value": "11-085r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 TopoJSON, GML Engineering Report" + "@value": "OWS-8 Bulk Geodata Transfer Using GML Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-113r1", + "@id": "http://www.opengis.net/def/docs/18-000", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-11-23" + "@value": "2019-05-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -54164,27 +53432,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46171" + "@id": "https://docs.ogc.org/is/18-000/18-000.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-8 Information Model for Moving Target Indicators and Moving Object Bookmarks (Engineering Report)" + "@value": "GeoPackage Related Tables Extension" }, { "@language": "en", - "@value": "11-113r1" + "@value": "18-000" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report aims at providing an information model for the usage of video moving target indicator data (VMTI), ground moving target indicator (GMTI) and tracking information (STANAG 4676) in the context of standardized spatial data infrastructures compliant to OGC and ISO standards. If possible, precedence was given on using the OGC Sensor Web Enablement suite of standards, as this suite provides a homogeneous suite of standards to express sensor and sensor observation data in the context of OGC. This means that all encodings are based on Observation and Measurements version 2 (O&M) and implemented as an application schema according to the rules of Geography Markup Language version 3.2 (GML). An information model – so called ‘bookmark’ – to conserve the trace from a moving object back to the original base data is discussed briefly. " + "@value": "A GeoPackage [geopackage] is a platform-independent SQLite [sqlite] database file that contains GeoPackage data and metadata tables. GeoPackages, as described by the GeoPackage Encoding Standard [GPKG1_2] are designed to be extensible, including support for additional data types. This document defines the Related Tables Extension (RTE) for the GeoPackage Encoding Standard.\r\n\r\nThe RTE defines the rules and requirements for creating relationships in a GeoPackage data store between geospatial data tables and other tables that contain or reference related content such as attributes or media. Geospatial data tables (such as features or tiles tables) contain location information and/or geometries. There are many examples of where the RTE can be used including relating parcel (land lot) features to pictures of that parcel or linking census boundaries to the related demographic census data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -54195,35 +53463,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-113r1" + "@value": "18-000" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 Information Model for Moving Target Indicators and Moving Object Bookmarks (Engineering Report)" + "@value": "OGC GeoPackage Related Tables Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-147", + "@id": "http://www.opengis.net/def/docs/11-058r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-02-06" + "@value": "2011-07-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Claude Speed" + "@value": "Ingo Simonis, Chrsitian Malewski" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -54233,27 +53501,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51823" + "@id": "https://portal.ogc.org/files/?artifact_id=44438" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-9 Aviation Architecture Engineering Report" + "@value": "*FL Starfish Fungus Language for Sensor Description" }, { "@language": "en", - "@value": "12-147" + "@value": "11-058r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document describes the architecture implemented in the OWS-9 Aviation thread, including:\r\n•\tA description of the architecture used for the implementation of the OWS-9 Aviation Use Cases.\r\n•\tAn overview of the implemented components and workflows followed by a short description of each component. \r\n•\tA discussion about discovery and registry methods and practices.\r\n•\tDocumentation of the issues, lessons learned as well as accomplishments and scenarios that were of general interest in the Aviation thread.\r\nMore detailed information on specific aspects considered in OWS-9 Aviation may be found in the individual Aviation Engineering Reports.\r\n" + "@value": "The Starfish Fungus Language was developed in response to the high number of complaints addressing issues with the OGC standard Sensor Model Language, SensorML. Most complaints circled around the high flexibility of the language in combination with unnecessary abstractions of technical terms, e.g. every sensor is not a sensor but a process. Most beginners struggled with the composite pattern of those processes, as there is no well-defined rule what needs to be described where. As a beginner, it is almost impossible to write a simple sensor description without getting major guidance through the SensorML development team or other experts." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -54264,35 +53532,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-147" + "@value": "11-058r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-9 Aviation Architecture Engineering Report" + "@value": "*FL Starfish Fungus Language for Sensor Description " } ] }, { - "@id": "http://www.opengis.net/def/docs/08-103r2", + "@id": "http://www.opengis.net/def/docs/15-001r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-02-05" + "@value": "2017-09-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Richard Martell" + "@value": "Benjamin Hagedorn, Simon Thum, Thorsten Reitz, Voker Coors, Ralf Gutbell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/ts" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -54302,27 +53570,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=31139" + "@id": "https://docs.ogc.org/is/15-001r4/15-001r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CSW-ebRIM Registry Service - Part 3: Abstract Test Suite" + "@value": "3D Portrayal Service 1.0" }, { "@language": "en", - "@value": "08-103r2" + "@value": "15-001r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/ts" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is an abstract test suite (ATS): a compendium of abstract test cases pertaining to implementations of the CSW-ebRIM 1.0 catalogue profile. It provides a basis for developing an executable test suite (ETS) to verify that the implementation under test (IUT) conforms to all relevant functional specifications. While passing all of the conformance tests defined in this ATS provides some assurance of overall functional correctness, it cannot guarantee that an implementation is faultless." + "@value": "The 3D Portrayal Service Standard is a geospatial 3D content delivery implementation specification. It focuses on what is to be delivered in which manner to enable interoperable 3D portrayal.\r\n\r\nIt does not define or endorse particular content transmission formats, but specifies how geospatial 3D content is described, selected, and delivered. It does not prescribe how aforementioned content is to be organized and represented, but provides a framework to determine whether 3D content is interoperable at the content representation level. More details are available in Design of this standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -54333,35 +53601,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-103r2" + "@value": "15-001r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CSW-ebRIM Registry Service - Part 3: Abstract Test Suite" + "@value": "OGC® 3D Portrayal Service 1.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-053r2", + "@id": "http://www.opengis.net/def/docs/21-007", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-03-25" + "@value": "2021-11-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "DGIWG" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/ts" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -54371,27 +53639,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=32888" + "@id": "https://docs.ogc.org/bp/21-007/21-007.pdf" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-053r2" + "@value": "21-007" }, { "@language": "en", - "@value": "WCS Processing Extension (WCPS) Abstract Test Suite" + "@value": "Defence Geospatial Information Working Group (DGIWG) GMLJP2/JP2 Profile for Imagery & Gridded Data 2.1.2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/ts" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "" + "@value": "This document provides a profile for JPEG 2000 for use as a\r\ncompression format for raster imagery. JPEG 2000 uses\r\ndiscrete wavelet transform (DWT) for compressing raster data,\r\nas opposed to the JPEG standard, which uses discrete cosine\r\ntransform (DCT). It is a compression technology which is best\r\nsuited for continuous raster data, such as satellite imagery and\r\naerial photography. This version adds support for\r\nReferenceable imagery." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -54402,30 +53670,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-053r2" + "@value": "21-007" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "WCS Processing Extension (WCPS) Abstract Test Suite" + "@value": "Defence Geospatial Information Working Group (DGIWG) GMLJP2/JP2 Profile for Imagery & Gridded Data 2.1.2" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-030", + "@id": "http://www.opengis.net/def/docs/18-090r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-03-06" + "@value": "2019-10-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sara Saeedi" + "@value": "Craig A. Lee" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -54440,17 +53708,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-030.html" + "@id": "https://docs.ogc.org/per/18-090r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-030" + "@value": "18-090r2" }, { "@language": "en", - "@value": "Secure Client Test Engineering Report" + "@value": "Testbed-14: Federated Clouds Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -54460,7 +53728,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) describes the development of compliance tests and their implementation in the OGC Test, Evaluation, And Measurement (TEAM) Engine to validate a client’s ability to make secure requests according to the OGC Web Services Security Candidate Standard. The goal of the candidate standard is to allow the implementation of Information Assurance (IA) controls and to advertise their existence in an interoperable way with minimal impact to existing implementations using a backward-compatible approach.\r\n\r\nThis ER covers the following topics from OGC Testbed-14 Compliance Interoperability & Testing Evaluation (CITE) thread:\r\n\r\ndeveloping a client validator to test compliance of client software with the OGC Web Services Security Candidate Standard\r\n\r\ncapturing the results of two use cases with different authentication methods\r\n\r\nmaking recommendations to the OGC Web Services Security Standards Working Group (SWG) based on the experiences made while developing the validator\r\n\r\n" + "@value": "The geospatial community has had an on-going challenge with being able to share data and compute resources in dynamic, collaborative environments that span different administrative domains. For these types of requirements, the concept of federation has been developed. The near-term goal of the Federated Cloud task in Testbed-14 is to demonstrate a specific data-sharing scenario among two or more administrative domains using existing security tooling, e.g., OpenID Connect and OAuth. The main details of this work are reported as part of the Security Engineering Report (ER) [1]. This Federated Cloud ER will dovetail with the Security ER to:\r\n\r\nCoordinate across all federation-related tasks in Testbed-14, including the Earth Observation Cloud and Workflow tasks,\r\n\r\nUnderstand the overall federation design space,\r\n\r\nAnalyze and critique the scope, trade-offs and limitations of the federation capabilities being built and demonstrated in Testbed-14,\r\n\r\nIdentify and prioritize possible incremental development tasks for subsequent testbeds, and\r\n\r\nLiaison with groups external to OGC, such as the NIST/IEEE Joint WG on Federated Cloud, to promote the further development and adoption of federated capabilities, and ultimately international standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -54471,104 +53739,102 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-030" + "@value": "18-090r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Secure Client Test Engineering Report" + "@value": "OGC Testbed-14: Federated Clouds Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-019", + "@id": "http://www.opengis.net/def/doc-type/d-rp/collection", "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" + "http://www.w3.org/2004/02/skos/core#Collection" ], - "http://purl.org/dc/terms/created": [ + "http://www.w3.org/2000/01/rdf-schema#label": [ { - "@type": "xsd:date", - "@value": "2005-02-02" + "@value": "Documents of type Recommendation Paper - deprecated " } ], - "http://purl.org/dc/terms/creator": [ + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Udo Quadt, Thomas Kolbe" + "@value": "Documents of type Recommendation Paper - deprecated " } ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/docs" } ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "http://www.w3.org/2004/02/skos/core#member": [ { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/03-088r6" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=8869" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/00-029" + }, { - "@language": "en", - "@value": "Web 3D Service" + "@id": "http://www.opengis.net/def/docs/02-066r1" }, { - "@language": "en", - "@value": "05-019" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/02-024" + }, { - "@id": "http://www.opengis.net/def/doc-type/d-dp" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/01-014r5" + }, { - "@value": "The Web 3D Service is a portrayal service for three-dimensional geodata, delivering graphical elements from a given geographical area. In contrast to the OGC Web Mapping service (WMS) and the OGC Web terrain service (WTS) 3D scene graphs are produced. These scene graphs will be rendered by the client and can interactively be explored by the user. The W3DS merges different types (layers) of 3D data in one scene graph. " - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/01-029" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/03-010r9" + }, + { + "@id": "http://www.opengis.net/def/docs/04-019r2" + }, + { + "@id": "http://www.opengis.net/def/docs/04-016r3" + }, + { + "@id": "http://www.opengis.net/def/docs/03-109r1" + }, + { + "@id": "http://www.opengis.net/def/docs/03-064r5" + }, + { + "@id": "http://www.opengis.net/def/docs/03-022r3" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-019" + "@id": "http://www.opengis.net/def/docs/03-010r7" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@language": "en", - "@value": "Web 3D Service" + "@value": "Documents of type Recommendation Paper - deprecated " } ] }, { - "@id": "http://www.opengis.net/def/docs/17-014r9", + "@id": "http://www.opengis.net/def/docs/03-031", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-01-11" + "@value": "2003-01-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed, Tamrat Belayneh" + "@value": "William Lalonde" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -54578,27 +53844,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/17-014r9/17-014r9.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1313" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-014r9" + "@value": "03-031" }, { "@language": "en", - "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.3" + "@value": "Style Management Service" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Indexed 3D Scene Layer (I3S) format is an open 3D content delivery format used to rapidly stream and distribute large volumes of 3D GIS data to mobile, web and desktop clients. I3S content can be shared across enterprise systems using both physical and cloud servers.\r\n\r\nA single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files.\r\n\r\nThe delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types." + "@value": "This document describes the proposed system design for the OGC Style Management Service (SMS).\r\nThe SMS must manage distinct objects that represent styles and symbols and provide the means to discover, query, insert, update, and delete these objects.\r\nStyles provide the mapping from feature types and feature properties and constraints to parameterized Symbols used in drawing maps. Symbols are bundles of predefined graphical parameters and predefined fixed graphic images." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -54609,35 +53875,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-014r9" + "@value": "03-031" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.3" + "@value": "Style Management Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-165r2", + "@id": "http://www.opengis.net/def/docs/09-075r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-01-03" + "@value": "2009-08-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ben Domenico, Stefano Nativi " + "@value": "Arne Schilling" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -54647,27 +53913,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51908" + "@id": "https://portal.ogc.org/files/?artifact_id=33949" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CF-netCDF3 Data Model Extension standard" + "@value": "09-075r1" }, { "@language": "en", - "@value": "11-165r2" + "@value": "OWS-6 3D Flythrough (W3DS) Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC netCDF encoding supports electronic encoding of geospatial data, that is, digital geospatial information representing space and time-varying phenomena.\r\nThis standard specifies the CF-netCDF data model extension. \r\nThis standard specifies the CF-netCDF data model mapping onto the ISO 19123 coverage schema. \r\nThis standard deals with multi-dimensional gridded data and multi-dimensional multi-point data.\r\nIn particular, this extension standard encoding profile is limited to multi-point, and regular and warped grids; however, irregular grids are important in the CF-netCDF community and work is underway to expand the CF-netCDF to encompass other coverages types, including irregular gridded datasets.\r\n" + "@value": "This document describes the 3D portrayal server components which were used in the OGC OWS-6 Decision Support Systems (DSS) thread. The objective pf this activity was to efficiently stream and display GML 3 content in internet or wireless networks with limited bandwidth, especially focusing on the CityGML application profile. The server for delivering landscape and city models is implemented as Web 3D Service (W3DS) that is designed as portrayal service. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -54678,35 +53944,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-165r2" + "@value": "09-075r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CF-netCDF3 Data Model Extension standard" + "@value": "OWS-6 3D Flythrough (W3DS) Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-008r4", + "@id": "http://www.opengis.net/def/docs/11-073r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-09-14" + "@value": "2012-02-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Emmanuel Devys, Ted Habermann, Chuck Heazel, Roger Lott, Even Rouault" + "@value": "Debbie Wilson, Ian Painter " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -54716,27 +53982,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/19-008r4/19-008r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=46666" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-008r4" + "@value": "OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0" }, { "@language": "en", - "@value": "GeoTIFF Standard" + "@value": "11-073r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Standard defines the Geographic Tagged Image File Format (GeoTIFF) by specifying requirements and encoding rules for using the Tagged Image File Format (TIFF) for the exchange of georeferenced or geocoded imagery. The OGC GeoTIFF 1.1 standard formalizes the existing community GeoTIFF specification version 1.0 and aligns it with the continuing addition of data to the EPSG Geodetic Parameter Dataset." + "@value": "The scope of this guidelines report is to provide:\r\n1.\tOverview of the OGC WFS 2.0 standard\r\n2.\tRecommendations for a minimum set of operations and behaviours that should be supported to ensure consistency across software implementations. \r\n3.\tGuidance for configuring the WFS 2.0 to retrieve AIXM 5.1 data \r\n4.\tSummary of potential improvements to WFS/FE 2.0, GML and AIXM 5.1 specifications to better support aeronautical use cases\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -54747,104 +54013,91 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-008r4" + "@value": "11-073r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoTIFF Standard" + "@value": "OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-100r3", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/doc-type/d-as", + "http://www.w3.org/2004/02/skos/core#narrower": [ { - "@type": "xsd:date", - "@value": "2011-05-11" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/01-101" + }, { - "@value": "Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/99-107" + }, { - "@id": "http://www.opengis.net/def/doc-type/profile" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/99-100r1" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/99-109r1" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=42729" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/02-102" + }, { - "@language": "en", - "@value": "10-100r3" + "@id": "http://www.opengis.net/def/docs/99-105r2" }, { - "@language": "en", - "@value": "Geography Markup Language (GML) simple features profile (with Corrigendum)" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/15-104r5" + }, { - "@id": "http://www.opengis.net/def/doc-type/profile" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/08-015r2" + }, { - "@value": "This approved OGC Implementation Standard defines a Simple Features profile of the Geography Markup Language version 3.2. This Simple Features Profile has been aligned with the OGC Simple Features standard for SQL version 1.2. Simple Features include: Point, Curve (LineString), Surface (Polygon), Geometry, MultiPoint, MultiCurve, MultiSurface, and MultiGeometry. The detailed abstract model for OGC features and geometry can be found in the OGC Abstract Specification, Topic Volume 1: Features (which is equivalent to ISO 19107).\r\n\r\nThis Simple Features profile of GML began as a product of OGC’s Interoperability Program: a global, collaborative, hands-on engineering and testing program designed to deliver prototype technologies and proven candidate standards into the OGC’s Specification Development Program. In OGC Interoperability Initiatives, international teams of technology providers work together to solve specific geo-processing interoperability problems posed by Initiative. \r\n" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/10-004r3" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/00-106" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-100r3" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/04-046r3" + }, { - "@language": "en", - "@value": "Geography Markup Language (GML) simple features profile (with Corrigendum)" + "@id": "http://www.opengis.net/def/docs/18-005r5" + }, + { + "@id": "http://www.opengis.net/def/docs/18-005r4" + }, + { + "@id": "http://www.opengis.net/def/docs/04-084" + }, + { + "@id": "http://www.opengis.net/def/docs/01-111" + }, + { + "@id": "http://www.opengis.net/def/docs/03-073r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-020" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-039r1", + "@id": "http://www.opengis.net/def/docs/15-074r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-01-21" + "@value": "2015-12-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sergio Taleisnik" + "@value": "Frans Knibbe, Alejandro Llaves" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -54854,27 +54107,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-039r1.html" + "@id": "https://docs.ogc.org/dp/15-074r1/15-074r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-039r1" + "@value": "15-074r1" }, { "@language": "en", - "@value": "OGC Testbed-17: Aviation API ER" + "@value": "Spatial Data on the Web Use Cases & Requirements" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Testbed-17 (TB-17) Aviation API Engineering Report (ER) summarizes the implementations, findings and recommendations that emerged from the efforts of building a definition for an Aviation API compliant with the requirements of the OGC Standards Program, and the exploration of the potential of aviation data fusion.\r\n\r\nThis ER describes the nine façades built to interface SWIM services and serve aviation data through OGC APIs, the two services built to consume SWIM data and fuse it to generate richer datasets while serving the fused data through OGC APIs, the client application built to display data retrieved from the façades and fusion services, and the development client built to focus on functionality and experimentation.\r\n\r\nFinally, this ER discusses the potential of OGC APIs to help standardize the access to aviation data within the context of the System Wide Information Management (SWIM) program." + "@value": "This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -54885,30 +54138,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-039r1" + "@value": "15-074r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: Aviation API ER" + "@value": "Spatial Data on the Web Use Cases & Requirements" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-001r3", + "@id": "http://www.opengis.net/def/docs/09-112", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-02" + "@value": "2009-10-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Simon Jirka, Arne Bröring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -54923,17 +54176,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21352" + "@id": "https://portal.ogc.org/files/?artifact_id=35471" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-001r3" + "@value": "09-112" }, { "@language": "en", - "@value": "Requirements for some specific simple solid, plane and line geometry types" + "@value": "Sensor Observable Registry Discussion Paper" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -54943,7 +54196,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This specification describes requirements for specific geometry types, including some simple solids, and planes and lines defined using an implicit parameterization." + "@value": "This Discussion paper introduces the Sensor Observable Registry (SOR), a web service interface for managing the definitions of phenomena measured by sensors as well as exploring semantic relationships between these phenomena." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -54954,30 +54207,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-001r3" + "@value": "09-112" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Requirements for some specific simple solid, plane and line geometry types" + "@value": "Sensor Observable Registry Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-098r1", + "@id": "http://www.opengis.net/def/docs/20-058", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-02-23" + "@value": "2024-08-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Joan Masó, Jérôme Jacovella-St-Louis " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -54992,17 +54245,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=25219" + "@id": "https://docs.ogc.org/is/20-058/20-058.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GeoXACML Implementation Specification - Extension A (GML2) Encoding" + "@value": "OGC API - Maps - Part 1: Core" }, { "@language": "en", - "@value": "07-098r1" + "@value": "20-058" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -55012,7 +54265,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines an extension to the GeoXACML Implementation Specification, Verison 1.0 for the GML2 geometry encoding as specified in the GML2 standard." + "@value": "The OGC API — Maps — Part 1: Core Standard defines a Web API for requesting maps over the Web. A map is a portrayal of geographic information as a digital representation suitable for display on a rendering device (adapted from OGC 06-042/ISO 19128 OpenGIS® Web Map Server (WMS) Implementation Specification). Implementations of the OGC API — Maps Standard are designed for a client to easily:\r\n\r\nRequest a visual representation of one or more geospatial data layers in different styles;\r\nSelect by area, time and resolution of interest;\r\nChange parameters such as the background color and coordinate reference systems.\r\nA server that implements OGC API — Maps provides information about what maps are offered. OGC API — Maps addresses use cases similar to those addressed by the OGC 06-042/ISO 19128 OpenGIS® Web Map Server (WMS) Implementation Specification Standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55023,35 +54276,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-098r1" + "@value": "20-058" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GeoXACML Implementation Specification - Extension A (GML2) Encoding" + "@value": "OGC API - Maps - Part 1: Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-056", + "@id": "http://www.opengis.net/def/docs/05-010", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-01-29" + "@value": "2005-01-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Song WU, Mahmoud SAKR" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -55061,27 +54314,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/23-056.html" + "@id": "https://portal.ogc.org/files/?artifact_id=8814" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-056" + "@value": "URNs of definitions in ogc namespace" }, { "@language": "en", - "@value": "Mobility Data Science Discussion Paper" + "@value": "05-010" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Almost every activity in our modern life leaves a digital trace, typically including location and time. Either captured by a sensor, manually input, or extracted from a social media post, the increase in the volume, variety, and velocity of spatiotemporal data is unprecedented. The ability to manage and analyze this data is important for many application domains, including smart cities, health, transportation, agriculture, sports, biodiversity, et cetera. It is critical to not only effectively manage and analyze the data but also to uphold privacy and ethical considerations. Since the civilian use of GPS was allowed in 1980, followed by the technological advances in other location tracking systems – wifi, RFID, bluetooth, etc., it is becoming more and more easy to track moving objects. The Mobility Data Science Summit was an opportunity to discuss the challenges of managing this data and making sense of it, with a focus on the tooling and standardization requirements." + "@value": "*** Superceded by 06-023r1 - Definition identifier URNs in OGC namespace ***\r\nThis Recommendation Paper specifies Universal Resource Names (URNs) for definitions in the " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55092,65 +54345,29 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-056" + "@value": "05-010" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Mobility Data Science Discussion Paper" + "@value": "URNs of definitions in ogc namespace" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-005r2", + "@id": "http://www.opengis.net/def/doc-type/d-bp/collection", "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ - { - "@type": "xsd:date", - "@value": "2021-02-26" - } - ], - "http://purl.org/dc/terms/creator": [ - { - "@value": "DGIWG" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ - { - "@id": "http://www.opengis.net/def/doc-type/bp" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ - { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ - { - "@id": "https://portal.ogc.org/files/94152" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ - { - "@language": "en", - "@value": "15-005r2" - }, - { - "@language": "en", - "@value": "Defence Profile of OGC Web Feature Service 2.0" - } + "http://www.w3.org/2004/02/skos/core#Collection" ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "http://www.w3.org/2000/01/rdf-schema#label": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@value": "Documents of type Best Practice - deprecated " } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines the DGIWG profile for the ISO\r\n19142:2010 - Web Feature Service (WFS) including changes\r\nmade in the OpenGIS Web Feature Service 2.0 Interface\r\nStandard - Corrigendum. The Web Feature Service provides\r\naccess to geospatial features in a manner independent of the\r\nunderlying data store." + "@value": "Documents of type Best Practice - deprecated " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55158,169 +54375,96 @@ "@id": "http://www.opengis.net/def/docs" } ], - "http://www.w3.org/2004/02/skos/core#notation": [ - { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-005r2" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@language": "en", - "@value": "Defence Profile of OGC Web Feature Service 2.0" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/techpaper", - "http://www.w3.org/2004/02/skos/core#narrower": [ + "http://www.w3.org/2004/02/skos/core#member": [ { - "@id": "http://www.opengis.net/def/docs/19-076" + "@id": "http://www.opengis.net/def/docs/05-087r4" }, { - "@id": "http://www.opengis.net/def/docs/10-128" + "@id": "http://www.opengis.net/def/docs/07-063" }, { - "@id": "http://www.opengis.net/def/docs/11-036" + "@id": "http://www.opengis.net/def/docs/06-080r2" }, { - "@id": "http://www.opengis.net/def/docs/18-004r1" + "@id": "http://www.opengis.net/def/docs/07-092r1" }, { - "@id": "http://www.opengis.net/def/docs/19-078r1" + "@id": "http://www.opengis.net/def/docs/07-062" }, { - "@id": "http://www.opengis.net/def/docs/12-026" + "@id": "http://www.opengis.net/def/docs/07-039r1" }, { - "@id": "http://www.opengis.net/def/docs/16-019r4" + "@id": "http://www.opengis.net/def/docs/03-105r1" }, { - "@id": "http://www.opengis.net/def/docs/20-085r1" + "@id": "http://www.opengis.net/def/docs/06-023r1" }, { - "@id": "http://www.opengis.net/def/docs/07-165r1" + "@id": "http://www.opengis.net/def/docs/05-057r4" }, { - "@id": "http://www.opengis.net/def/docs/15-002r5" + "@id": "http://www.opengis.net/def/docs/04-038r2" }, { - "@id": "http://www.opengis.net/def/docs/18-008r1" + "@id": "http://www.opengis.net/def/docs/05-027r1" }, { - "@id": "http://www.opengis.net/def/docs/16-131r2" + "@id": "http://www.opengis.net/def/docs/05-086" }, { - "@id": "http://www.opengis.net/def/docs/14-095" + "@id": "http://www.opengis.net/def/docs/06-131r4" }, { - "@id": "http://www.opengis.net/def/docs/09-044r3" + "@id": "http://www.opengis.net/def/docs/07-018r1" }, { - "@id": "http://www.opengis.net/def/docs/11-110" + "@id": "http://www.opengis.net/def/docs/06-035r1" }, { - "@id": "http://www.opengis.net/def/docs/11-145" + "@id": "http://www.opengis.net/def/docs/06-021r2" }, { - "@id": "http://www.opengis.net/def/docs/10-124r1" + "@id": "http://www.opengis.net/def/docs/05-010" }, { - "@id": "http://www.opengis.net/def/docs/11-159" + "@id": "http://www.opengis.net/def/docs/06-141r2" }, { - "@id": "http://www.opengis.net/def/docs/14-115" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/18-026r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ - { - "@type": "xsd:date", - "@value": "2019-03-05" - } - ], - "http://purl.org/dc/terms/creator": [ - { - "@value": "Juan José Doval, Héctor Rodríguez" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ - { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ - { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ - { - "@id": "https://docs.ogc.org/per/18-026r1.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ - { - "@language": "en", - "@value": "18-026r1" + "@id": "http://www.opengis.net/def/docs/06-135r1" }, { - "@language": "en", - "@value": "Security Engineering Report" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ - { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "This Security Engineering Report (ER) covers several OGC Testbed-14 topics:\r\n\r\nBest practices for the integration of OAuth2.0/OpenID Connect services\r\n\r\nMediation services for different security environments\r\n\r\nFederated identity management\r\n\r\nSecuritization of workflows\r\n\r\nThe first two topics are the main focus of this ER. During this Testbed, a server that provides OAuth2.0 and OpenID Connect capabilities was extended with a mediation service that allows for a centralized security authority with users/clients that implement different security standards.\r\n\r\nThe remaining two topics will expand on the close relationship between Security, Workflows and Federated Clouds and the respective implementation challenges. On these specific topics, this ER also outlines and provides a proof-of-concept for a simplistic architecture approach that explores one of several Federated Clouds architectures." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/07-113r1" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-026r1" + "@id": "http://www.opengis.net/def/docs/05-011" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@language": "en", - "@value": "OGC Testbed-14: Security Engineering Report" + "@value": "Documents of type Best Practice - deprecated " } ] }, { - "@id": "http://www.opengis.net/def/docs/18-095r7", + "@id": "http://www.opengis.net/def/docs/23-010", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-10-14" + "@value": "2023-06-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall " + "@value": "Robert Thomas, Sara Saeedi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -55330,27 +54474,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/18-095r7" + "@id": "https://docs.ogc.org/per/23-010.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geospatial Coverages Data Cube Community Practice" + "@value": "Towards a Federated Marine SDI: Connecting Land and Sea to Protect the Arctic Environment Engineering Report" }, { "@language": "en", - "@value": "18-095r7" + "@value": "23-010" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Data cubes for geospatial information provide the means to integrate observations and other types of geospatial data for use in multiple applications through simplified access and efficient analytics. Using the Geospatial Coverages data structure, this Community Practice defines requirements for a geospatial coverages data cube infrastructure and guidelines for enhancements and extensions to the basic core." + "@value": "This Engineering Report (ER) summarizes the main achievements of the Federated Marine Spatial Data Infrastructure (FMSDI) Pilot Phase 3. It focused on a variety of aspects contributing to an overarching scenario to aid in the better understanding of both the challenges and potential opportunities for coastal communities, ecosystems, and economic activities in the Arctic region.\r\n\r\nThe sub-scenarios, i.e., those scenarios developed by each participant, address aspects of the changing Arctic landscape. These activities included the following.\r\n\r\nA sea-based, health and safety scenario incorporating the land/sea interface in the Arctic. This scenario demonstrates the technology and data used with OGC, IHO, and other community standards in response to a grounding event and the evacuation of an expedition cruise ship or research vessel in the Arctic. Demonstrating interoperability between land and marine data that is necessary to aid first responders and other stakeholders. This scenario incorporates, but is not be limited to:\r\n\r\nvoyage planning information (e.g., Arctic Voyage Planning Guide, Safety of Navigation products and services, Maritime Safety Information);\r\n\r\nland-based emergency services/resources (e.g., Coast Guard stations, transit times to emergency services or ports, medical facilities and resources, helicopter access);\r\n\r\ncoastal environmental/topographic/hydrographic/maintenance data (e.g., deposition and dredging of seafloor sediment, changes in coastline and bathymetry); and\r\n\r\nglobal maritime traffic data in the Arctic (e.g., to help assess likelihood of other ships in responding to a ship in distress).\r\n\r\nDemonstrating interoperability between land and marine data that is necessary to understand coastal erosion (e.g., ocean currents, geology, permafrost characteristics, etc.).\r\n\r\nGeneral sensitivity to climate change." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55361,30 +54505,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-095r7" + "@value": "23-010" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geospatial Coverages Data Cube Community Practice" + "@value": "Towards a Federated Marine SDI: Connecting Land and Sea to Protect the Arctic Environment Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-046r1", + "@id": "http://www.opengis.net/def/docs/15-030r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-12" + "@value": "2016-01-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Martin Klopfer" + "@value": "Scott Serich" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -55399,17 +54543,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-046r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=65451" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Semantic Enablement Engineering Report" + "@value": "15-030r3" }, { "@language": "en", - "@value": "16-046r1" + "@value": "Testbed 11 Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Round Trip Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -55419,7 +54563,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The requirement for capabilities supporting semantic understanding and reasoning in geospatial intelligence (GEOINT) is an all-encompassing paradigm shift from the past. Standards play a critical role in ensuring this is accomplished in a consistent and repeatable manner. Semantic standards and services supporting semantic capabilities are at a relatively early stage of development. Interoperability between semantic standards for encoding relationships and Web based services for discovery, access, retrieval and visualization of those relationships requires more testing and evaluation. This engineering report (ER) highlights the key findings and discussions from Testbed-12 that enable semantic interoperability, including semantic mediation, schema registries, and SPARQL endpoints. It references key findings from the Semantic Portrayal ER and helps to understand the current OGC discussion on semantics in general." + "@value": "The goal of the Geo4NIEM thread in OGC Testbed 11 was to gain Intelligence Community (IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0 architecture through the development, implementations, test, and robust demonstration making use of IC specifications, Geography Markup Language (GML), and NIEM in a simulated “real-world” scenario. The demonstration scenario begins with NIEM-conformant Information Exchange Packages (IEPs) containing operational data and IC security tags from the Information Security Marking (ISM) and Need-To-Know (NTK) access control metadata, and the Trusted Data Format (TDF) for binding assertion metadata with data resource(s). Those instance documents are deployed using Open Geospatial Consortium (OGC) enabled Web Services for access by client applications. Access control is based on attributes of the end-user and the instance data\r\nRecommendations to update these information exchanges were provided to reflect NIEM 3.0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment exercised this data encoding in OGC Web Feature Services (WFS) and Policy Enforcement Points (PEP) accessed by multiple client applications. The round-trip assessment also exercised the OGC Transactional Web Feature Services (WFS-T). Results from this task provided a preliminary architecture that was tested and demonstrated in Testbed 11, and summarized in other OGC Testbed 11 Engineering Reports.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55430,30 +54574,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-046r1" + "@value": "15-030r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Semantic Enablement Engineering Report" + "@value": "Testbed 11 Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Round Trip Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-002r1", + "@id": "http://www.opengis.net/def/docs/09-112r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-08-21" + "@value": "2010-10-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joshua Lieberman" + "@value": "Simon Jirka, Arne Bröring, Daniel Nüst" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -55468,17 +54612,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=15198" + "@id": "https://portal.ogc.org/files/?artifact_id=40571" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geospatial Semantic Web Interoperabiltiy Experiment Report" + "@value": "Sensor Observable Registry (SOR) Discussion Paper" }, { "@language": "en", - "@value": "06-002r1" + "@value": "09-112r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -55488,7 +54632,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Semantic Web seeks to make the meaning as accessible as the material, by enabling connections - which are both logical and (machine) actionable - between concepts which a user presently understands and those which may be new and foreign. The Geospatial Semantic Web extends this capability to both content and concepts that are specifically spatial, temporal, and geographic in nature, giving both people and machines true access to a wider range of knowledge." + "@value": "This Discussion paper introduces the Sensor Observable Registry (SOR), a web service interface for managing the definitions of phenomena measured by sensors as well as exploring semantic relationships between these phenomena." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55499,35 +54643,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-002r1" + "@value": "09-112r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geospatial Semantic Web Interoperabiltiy Experiment Report" + "@value": "Sensor Observable Registry (SOR) Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-111r1", + "@id": "http://www.opengis.net/def/docs/04-019r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-09-16" + "@value": "2004-11-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "ISO" + "@value": "Mike Botts" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -55537,27 +54681,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?csnumber=53798" + "@id": "https://portal.ogc.org/files/?artifact_id=7927" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-111r1" + "@value": "Sensor Model Language (SensorML) for In-situ and Remote Sensors" }, { "@language": "en", - "@value": "Topic 11 - Metadata" + "@value": "04-019r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Same as ISO 19115-1:2014. Abstract Specification Topic 11 was updated to the latest version of the ISO metadata standard on 21 September 2016. Prior to this date, this Topic was the same as ISO 19115:2003. Please note that many OGC standards and other related work normatively refer to the previous version of this Topic." + "@value": "The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55568,35 +54712,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-111r1" + "@value": "04-019r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 11 - Metadata" + "@value": "Sensor Model Language (SensorML) for In-situ and Remote Sensors" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-077", + "@id": "http://www.opengis.net/def/docs/09-156r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-07-02" + "@value": "2011-01-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Luis Bermudez" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -55606,27 +54750,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=28170" + "@id": "https://portal.ogc.org/files/?artifact_id=37373" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-077" + "@value": "09-156r2" }, { "@language": "en", - "@value": "OWS-5 Engineering Report: Local MSD Implementation Profile (GML 3.2.1)" + "@value": "Ocean Science Interoperability Experiment Phase II Report " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document contains a data content specification for Local Mission Specific Data (MSD) and is based on the GEOINT Structure Implementation Profile (GSIP) developed by the NGA. This document defines the GML 3.2.1 (ISO 19136) encoding requirements for Local MSD. The structure of the document is based on ISO 19131 (Geographic Information – Data Product Specification)." + "@value": "This OGC Engineering Report documents the work performed by the participants of the Ocean Science Interoperability Experiment Phase II. This work is a follow-on to the OGC Oceans IE Phase 1 activity. Specifically, this IE addressed the following tasks:\r\n•\tAutomated metadata/software installation via PUCK protocol.\r\n•\tOffering of complex systems (e.g. observations systems containing other systems) such as collection of stations.\r\n•\tLinking data from SOS to out-of-band offerings.\r\n•\tSemantic Registry and Services.\r\n•\tCatalogue Service-Web Registry.\r\n•\tIEEE-1451/OGC-SWE harmonization\r\n\r\nAs a result of this experiment, a number of recommendations and conclusions were identified.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55637,35 +54781,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-077" + "@value": "09-156r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-5 Engineering Report: Local MSD Implementation Profile (GML 3.2.1)" + "@value": "Ocean Science Interoperability Experiment Phase II Report " } ] }, { - "@id": "http://www.opengis.net/def/docs/16-008r1", + "@id": "http://www.opengis.net/def/docs/20-043", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-01-31" + "@value": "2020-10-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "GeoSciML Modeling Team " + "@value": "Stefan Achtsnit, Joachim Ungar, and Stephan Meißl (EOX), Anja Vrecko and Grega Milčinski (Sinergise)" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -55675,27 +54819,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/16-008/16-008r1.html" + "@id": "https://docs.ogc.org/per/20-043.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geoscience Markup Language 4.1 (GeoSciML) - with Corrigendum" + "@value": "20-043" }, { "@language": "en", - "@value": "16-008r1" + "@value": "OGC Earth Observation Applications Pilot: EOX-Sinergise-DLR-UVT-Terrasigna Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "GeoSciML is a model of geological features commonly described and portrayed in geological maps, cross sections, geological reports and databases. The model was developed by the IUGS CGI (Commission for the Management and Application of Geoscience Information) and version 4.1 is the first version officially submitted as an OGC standard. This specification describes a logical model and GML/XML encoding rules for the exchange of geological map data, geological time scales, boreholes, and metadata for laboratory analyses. It includes a Lite model, used for simple map-based applications; a basic model, aligned on INSPIRE, for basic data exchange; and an extended model to address more complex scenarios. \r\n\r\nThe specification also provides patterns, profiles (most notably of Observations and Measurements - ISO19156), and best practices to deal with common geoscience use cases. \r\n\r\n" + "@value": "This Engineering Report documents findings, achievements, and learnings gained through activities during the OGC Earth Observation (EO) Applications Pilot by the EOX team (EOX, DLR, UVT, Sinergise, and Terrasigna). Both perspectives, from application developer’s as well as from platform provider’s view, are represented here." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55706,30 +54850,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-008r1" + "@value": "20-043" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Geoscience Markup Language 4.1 (GeoSciML) - with Corrigendum" + "@value": "OGC Earth Observation Applications Pilot: EOX-Sinergise-DLR-UVT-Terrasigna Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-154", + "@id": "http://www.opengis.net/def/docs/09-163r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-14" + "@value": "2010-04-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David S. Burggraf, Ron Lake, Darko Androsevic" + "@value": "Frédéric Houbie, Fabian Skivée, Simon Jirka" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -55744,17 +54888,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=19580" + "@id": "https://portal.ogc.org/files/?artifact_id=37944" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "WFS Temporal Investigation" + "@value": "09-163r2" }, { "@language": "en", - "@value": "06-154" + "@value": "sensorML Extension Package for ebRIM Application Profile" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -55764,7 +54908,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The objective of the proposed temporal extensions to the WFS is to enable temporal/geospatial queries using the GML temporal types against GML dynamic features employing either the snapshot or time history model (time slices). " + "@value": "This document describes the mapping of description of sensors using SensorML specification 1.0 [OGC 07-000] to an ebRIM structure within an OGCTM Catalogue 2.0.2 (Corrigendum 2 Release) [OGC 07-006r1] implementing the CSW-ebRIM Registry Service – part 1: ebRIM profile of CSW [OGC 07-110r4].\r\nIn addition this document contains the definition of a SensorML profile for Discovery which defines a minimum set of metadata to be provided within SensorML documents as well as the structure this data shall possess. This profile is based on the OGC OWS- 6 SensorML Profile for Discovery Engineering Report [OGC 09-033].\r\nIt defines the way sensors metadata are organized and implemented in the Catalogue for discovery, retrieval and management." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55775,35 +54919,55 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-154" + "@value": "09-163r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS 4 WFS Temporal Investigation" + "@value": "sensorML Extension Package for ebRIM Application Profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/24-008", + "@id": "http://www.opengis.net/def/doc-type/ts", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/08-103r2" + }, + { + "@id": "http://www.opengis.net/def/docs/14-014r3" + }, + { + "@id": "http://www.opengis.net/def/docs/07-134r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-053r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-069r2" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/16-070r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-07-05" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mickael Beaufils, Kathi Schleidt, Hylke van der Schaaf, Dan Ponti, Neil Chadwick, Derrick Dasenbrock" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -55813,27 +54977,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/24-008.html" + "@id": "https://docs.ogc.org/bp/16-070r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Geotech Interoperability Experiment Engineering Report" + "@value": "16-070r4" }, { "@language": "en", - "@value": "24-008" + "@value": "Volume 4: OGC CDB Rules for Encoding CDB Vector Data using Shapefiles (Best Practice)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) describes the outcomes of the Open Geospatial Consortium (OGC) Geotech Interoperability Experiment (IE). The objective of this IE was to develop a common conceptual model for describing geotechnical engineering data that bridges existing specifications for encoding those data and which could be integrated across OGC and buildingSMART International Standards,\r\n\r\nThis ER is directly imported from the project wiki found here: https://github.com/opengeospatial/Geotech/wiki." + "@value": "This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55844,35 +55008,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "24-008" + "@value": "16-070r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Geotech Interoperability Experiment Engineering Report" + "@value": "Volume 4: OGC CDB Rules for Encoding CDB Vector Data using Shapefiles (Best Practice)" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-040r3", + "@id": "http://www.opengis.net/def/docs/21-018", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-09-23" + "@value": "2022-02-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Robert Gibb" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -55882,27 +55046,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/as/20-040r3/20-040r3.html" + "@id": "https://docs.ogc.org/per/21-018.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-040r3" + "@value": "21-018" }, { "@language": "en", - "@value": "Topic 21 - Discrete Global Grid Systems - Part 1 Core Reference system and Operations and Equal Area Earth Reference System" + "@value": "Features and Geometries JSON CRS Analysis of Alternatives Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Abstract Specification lays the foundations for Discrete Global Grid Systems (DGGS). It defines Common classes for spatio-temporal geometry, topology, and reference systems using identifiers, a DGGS Core Reference system as a reference system using zonal identifiers with structured geometry that may be spatio-temporal, a suite of DGGS Core Functions, and it specifies Equal-Area Earth DGGS. The OGC DGGS Abstract Specification supports the specification of standardized DGGS infrastructures that enable the integrated analysis of very large, multi-source, multi-resolution, multi-dimensional, distributed geospatial data. Interoperability between OGC DGGS implementations is anticipated through implementation standards, and extension interface encodings of OGC Web Services." + "@value": "One of the primary requirements for the OGC Testbed-17 Features and Geometries JSON task is to define an extension or profile of GeoJSON that supports encoding spatiotemporal data in Coordinate Reference Systems (CRS) other than the GeoJSON default of the World Geodetic System 1984 (WGS 84) datum, with longitude and latitude units of decimal degrees (CRS84).\r\n\r\nThis OGC Testbed 17 (TB17) Engineering Report (ER) presents the various alternatives considered for declaring CRS information in a Features and Geometries JSON (JSON-FG) file. JSON-FG is an OGC extension to GeoJSON that, among other things, adds support of coordinate reference systems other than the CRS84 default. One of the alternatives was selected to be the mechanism for declaring CRS information in a JSON-FG document and is fully described in the “OGC Testbed-17: OGC Features and Geometries JSON Engineering Report” (OGC 21-017r1).\r\n\r\nThis ER was submitted to the OGC Features and Geometries JSON Standards Working Group so that the work in TB17 can inform their task of developing and documenting a Features and Geometries JSON standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55913,35 +55077,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-040r3" + "@value": "21-018" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 21 - Discrete Global Grid Systems - Part 1 Core Reference system and Operations and Equal Area Earth Reference System" + "@value": "OGC Testbed-17: Features and Geometries JSON CRS Analysis of Alternatives Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-021r1", + "@id": "http://www.opengis.net/def/docs/16-011r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-03-27" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mike Botts, Alex Robin, John Davidson, Ingo Simonis" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp-draft" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -55951,27 +55115,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=14140" + "@id": "https://docs.ogc.org/bp/16-011r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-021r1" + "@value": "16-011r5" }, { "@language": "en", - "@value": "Sensor Web Enablement Architecture Document" + "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp-draft" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The aim of this document is to provide a overview description of the general architecture that applies to the Sensor Web Enablement (SWE). While this document provides a synopsis of the relevant encodings and web services, it does not contain interface descriptions of the components.\r\n\r\n" + "@value": "Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -55982,35 +55146,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-021r1" + "@value": "16-011r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Sensor Web Enablement Architecture Document" + "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-102", + "@id": "http://www.opengis.net/def/docs/15-077r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-09-02" + "@value": "2016-02-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cyril Minoux" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56020,27 +55184,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34833" + "@id": "https://portal.ogc.org/files/?artifact_id=64406" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-102" + "@value": "15-077r1" }, { "@language": "en", - "@value": "DGIWG WMS 1.3 Profile and systems requirements for interoperability for use within a military environment" + "@value": "Testbed-11 SOAP Interface Engineering Report: Comparison on the Usage of SOAP Across OGC Web service interfaces" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies requirements for systems providing maps using OGC Web Map Service. The document defines a profile of OGC WMS 1.3 implementation standard [WMS1.3], a list of normative system requirements and a list of non-normative recommendations. The Defence Geospatial Information Working Group (DGIWG) performed the work as part of through the S05 Web Data Access Service Project of the Services & Interfaces Technical Panel." + "@value": "A number of OGC service interface standards define SOAP bindings. Despite the current hype around REST or RESTful interfaces, SOAP services are still used intensively, in particular in security-critical environments. A number of OGC Web service interfaces support SOAP bindings (see chapter 6). Unfortunately, those bindings are not fully consistent across the suite of OGC service standards. Differences can be found in terms of SOAP versions, used namespaces, error handling, capabilities documentation, or transport of non-XML data; i.e. aspects that should be harmonized by a cross-standard working group. \r\nThis document seeks to provide an overview of the current situation and guidance on future SOAP harmonization across all OGC Web services. A number of change requests have been developed during the development process for this document. Though this document provides recommendations in chapter 8, it is highly recommended to either form a new SOAP working group, or preferably to assign the development of SOAP best practices to reduce the risk of missed requirements and architecture arguments to the newly reformed OWS Common SWG. The best practices could then be applied to all OGC service standards that offer SOAP bindings.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56051,35 +55215,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-102" + "@value": "15-077r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "DGIWG WMS 1.3 Profile and systems requirements for interoperability for use within a military environment" + "@value": "OGC® Testbed-11 SOAP Interface Engineering Report: Comparison on the Usage of SOAP Across OGC Web service interfaces" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-154", + "@id": "http://www.opengis.net/def/docs/13-131r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-02-05" + "@value": "2016-08-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Darko Androsevic" + "@value": "Aaron Braeckel , Lorenzo Bigagli , Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56089,27 +55253,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51889" + "@id": "https://docs.ogc.org/is/13-131r1/13-131r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-154" + "@value": "13-131r1" }, { "@language": "en", - "@value": "OWS-9 OWS Innovations GMLJP2 for National Imagery Transmission Format (NITF) Engineering Report " + "@value": "Publish/Subscribe Interface Standard 1.0 - Core" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document provides mapping of the national imagery transmission format (NITF) version 2.1 format and NITF tagged record extensions (TRE) to GMLJP2 v2.0 (draft) format.\r\nThis Engineering Report was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative. \r\nThis document further describes study results of analyses of NITF and NITF extensions (TRE) capabilities and how they can be supported by GMLJP2 2.0 (draft). This activity was a part of the OGC OWS-9 Innovations thread.\r\n" + "@value": "Publish/Subscribe 1.0 is an interface specification that supports the core components and concepts of the Publish/Subscribe message exchange pattern with OGC Web Services. The Publish/Subscribe pattern complements the Request/Reply pattern specified by many existing OGC Web Services. This specification may be used either in concert with, or independently of, existing OGC Web Services to publish data of interest to interested Subscribers.\r\n\r\nPublish/Subscribe 1.0 primarily addresses subscription management capabilities such as creating a subscription, renewing a subscription, and unsubscribing. However, this standard also allows Publish/Subscribe services to advertise and describe the supported message delivery protocols such as SOAP messaging, ATOM, and AMQP. Message delivery protocols should be considered to be independent of the Publish/Subscribe 1.0 standard. Therefore, OGC Publish/Subscribe only includes metadata relating to message delivery protocols in sufficient detail to allow for different implementations of Publish/Subscribe 1.0 to interoperate. \r\n\r\nThis specification defines Publish/Subscribe functionality independently of the binding technology (e.g., KVP, SOAP, REST). Extensions to this specification may realize these core concepts with specific binding technologies." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56120,35 +55284,114 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-154" + "@value": "13-131r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-9 OWS Innovations GMLJP2 for National Imagery Transmission Format (NITF) Engineering Report " + "@value": "OGC® Publish/Subscribe Interface Standard 1.0 - Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-107r2", + "@id": "http://www.opengis.net/def/doc-type/d-as/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Abstract Specification - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Abstract Specification - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/99-107" + }, + { + "@id": "http://www.opengis.net/def/docs/99-100r1" + }, + { + "@id": "http://www.opengis.net/def/docs/99-109r1" + }, + { + "@id": "http://www.opengis.net/def/docs/02-102" + }, + { + "@id": "http://www.opengis.net/def/docs/99-105r2" + }, + { + "@id": "http://www.opengis.net/def/docs/15-104r5" + }, + { + "@id": "http://www.opengis.net/def/docs/08-015r2" + }, + { + "@id": "http://www.opengis.net/def/docs/10-004r3" + }, + { + "@id": "http://www.opengis.net/def/docs/00-106" + }, + { + "@id": "http://www.opengis.net/def/docs/04-046r3" + }, + { + "@id": "http://www.opengis.net/def/docs/18-005r5" + }, + { + "@id": "http://www.opengis.net/def/docs/18-005r4" + }, + { + "@id": "http://www.opengis.net/def/docs/04-084" + }, + { + "@id": "http://www.opengis.net/def/docs/01-111" + }, + { + "@id": "http://www.opengis.net/def/docs/03-073r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-020" + }, + { + "@id": "http://www.opengis.net/def/docs/01-101" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Abstract Specification - deprecated " + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/12-028", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-09-22" + "@value": "2012-05-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Scarponcini " + "@value": "OGC Aviation Domain Working Group" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56158,27 +55401,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=75929" + "@id": "https://portal.ogc.org/files/?artifact_id=47859" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "InfraGML 1.0: Part 7 – LandInfra Land Division - Encoding Standard" + "@value": "Guidance and Profile of GML for use with Aviation Data" }, { "@language": "en", - "@value": "16-107r2" + "@value": "12-028" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 7 addresses the LandDivision and Condominium Requirements Classes from LandInfra.\r\n" + "@value": "The ISO 19107 spatial schema, which is implemented by GML, is very complex. ISO\r\n19107 defines an extensive list of geometries, geometric properties and operations –\r\nmany of which are not necessary for aeronautical information applications. In addition,\r\nthe ISO 19107 contains an exhaustive 3D geometry model that is probably not needed in\r\nits entirety for AIXM either. Therefore, a GML profile for AIXM needs to be defined.\r\nThe objective of this document is to identify the elements of the AIXM-GML profile and\r\nalso to provide guidelines for the use of GML constructs in AIXM data sets.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56189,35 +55432,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-107r2" + "@value": "12-028" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC InfraGML 1.0: Part 7 – LandInfra Land Division - Encoding Standard" + "@value": "Guidance and Profile of GML for use with Aviation Data" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-102r1", + "@id": "http://www.opengis.net/def/docs/05-096r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-05-09" + "@value": "2006-07-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Burggraf, Stan Tillman" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56227,27 +55470,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=14337" + "@id": "https://portal.ogc.org/files/?artifact_id=13205" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS3 GML Topology Investigation" + "@value": "GML 3.1.1 grid CRSs profile" }, { "@language": "en", - "@value": "05-102r1" + "@value": "05-096r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Part 1 of this investigation is conducted by Galdos Systems. In this part, the OWS3 MSD3 geometric description is extended to include a topology encoding as defined by the MSD3 schema. Part 2 (Clause 6.2) of this investigation is conducted by Intergraph Corp. and describes and discusses the impacts of encoding topology within the GML data. \r\n" + "@value": "This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding definitions of grid coverage (including image) Coordinate Reference Systems (CRSs) plus related coordinate Transformations. This document also specifies some Universal Resource Names (URNs) for definitions in the ogc URN namespace, in addition to those specified in [OGC 05-010]. Additional specific URNs are defined for definitions of the datums, coordinate systems, and coordinate system axes which are often used in definitions of grid and image CRSs." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56258,35 +55501,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-102r1" + "@value": "05-096r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS3 GML Topology Investigation" + "@value": "GML 3.1.1 grid CRSs profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-020", + "@id": "http://www.opengis.net/def/docs/16-103r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-04-16" + "@value": "2017-08-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Cooper" + "@value": "Paul Scarponcini" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56296,27 +55539,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=37761" + "@id": "https://portal.ogc.org/files/?artifact_id=75120" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 02.1 - Spatial Referencing by Coordinates - Extension for Parametric Values" + "@value": "InfraGML 1.0: Part 3 - Alignments - Encoding Standard" }, { "@language": "en", - "@value": "10-020" + "@value": "16-103r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "" + "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 3 addresses the Alignment Requirements Class from LandInfra." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56327,30 +55570,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-020" + "@value": "16-103r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 2.1 - Spatial Referencing by Coordinates - Extension for Parametric Values" + "@value": "OGC InfraGML 1.0: Part 3 - Alignments - Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-013r6", + "@id": "http://www.opengis.net/def/docs/12-155", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-07-14" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Luis Bermudez, David Arctur" + "@value": "Weiguo Han, Yuanzheng Shao, Liping Di" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -56365,17 +55608,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=44834" + "@id": "https://portal.ogc.org/files/?artifact_id=51891" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Water Information Services Concept Development Study" + "@value": "12-155" }, { "@language": "en", - "@value": "11-013r6" + "@value": "OWS-9 OWS Innovations WCS for LIDAR Engineering Report " } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -56385,7 +55628,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The purpose of this report is to recommend appropriate architectures and procedures for migrating the CUAHSI HIS to the OGC-based WaterML 2.0 encoding (profile of OGC O&M standard) and OGC web services such as Sensor Observation Service (SOS), Web Feature Service (WFS), Web Mapping Service (WMS), Web Coverage Service (WCS), and Catalogue Service for the Web (CSW). This report may be used as the basis for future OGC Interoperability Program initiatives." + "@value": "This Engineering Report is prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiatitive of the Innovations Coverages Sub-Thread. This document represents the OWS-9 OWS Innovations WCS for LIDAR Engineering Report. In this report, the implementation of WCS 2.0 service that serves the LIDAR data in NITF format is introduced. This service supports the JPEG 2000 output format along with GMLJP2 metadata description as well as the JPIP protocol to deliver the output JPEG2000 data. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56396,43 +55639,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-013r6" + "@value": "12-155" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Engineering Report: Water Information Services Concept Development Study" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/rfc", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/03-081r2" + "@value": "OGC® OWS-9 OWS Innovations WCS for LIDAR Engineering Report " } ] }, { - "@id": "http://www.opengis.net/def/docs/16-052", + "@id": "http://www.opengis.net/def/docs/12-000", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-22" + "@value": "2014-02-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó" + "@value": "Mike Botts, Alexandre Robin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56442,27 +55677,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-052.html" + "@id": "https://portal.ogc.org/files/?artifact_id=55939" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-052" + "@value": "12-000" }, { "@language": "en", - "@value": "Testbed-12 OWS Context / Capabilities Engineering Report" + "@value": "SensorML: Model and XML Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC service metadata document (sometimes also called capabilities document) is a key part in the service discovery. It describes the service and also the resources that the service expose. Resources are listed in the service metadata document inside a section named as Contents by OWS Common. There are two main limitations to the current Contents section approach:\r\n\r\nOWS Common offers flexibility for describing resources and it only proposes a very minimum set of metadata in figure 7 of OGC 06-121r9 called DatasetSummary that need to be sub-classed (i.e. extended) by any specific application. As a result, each standard proposes its own alternative for it. Integrated client developers need to implement them separately.\r\n\r\nIf the number of resources is very large or the service is highly dynamic, the Contents section can be too long or useless and neither the service nor the client can handle it efficiently.\r\n\r\nThis Engineering Report proposes a double solution to the Contents section of the service metadata documents: It proposes ways to encode the Contents section using the OWS Context encoding data types and it introduces the use OpenSearch as a way to request a subset of the resources that the service can provide access to. In that sense, the use of the OGC 10-032r8 OpenSearchGeo can provide the long time needed geospatial and temporal filter capabilities." + "@value": "The primary focus of the Sensor Model Language (SensorML) is to provide a robust and\r\nsemantically-tied means of defining processes and processing components associated\r\nwith the measurement and post-measurement transformation of observations. This\r\nincludes sensors and actuators as well as computational processes applied pre- and postmeasurement.\r\nThe main objective is to enable interoperability, first at the syntactic level and later at the\r\nsemantic level (by using ontologies and semantic mediation), so that sensors and\r\nprocesses can be better understood by machines, utilized automatically in complex\r\nworkflows, and easily shared between intelligent sensor web nodes.\r\nThis standard is one of several implementation standards produced under OGC’s Sensor\r\nWeb Enablement (SWE) activity. This standard is a revision of content that was\r\npreviously integrated in the SensorML version 1.0 standard (OGC 07-000)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56473,35 +55708,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-052" + "@value": "12-000" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 OWS Context / Capabilities Engineering Report" + "@value": "OGC® SensorML: Model and XML Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-023r1", + "@id": "http://www.opengis.net/def/docs/22-032r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-08-08" + "@value": "2023-01-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Carl Reed, PhD" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56511,27 +55746,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=16339" + "@id": "https://docs.ogc.org/cs/17-014r9/22-032r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Definition identifier URNs in OGC namespace" + "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Version 1.3 Release Notes" }, { "@language": "en", - "@value": "06-023r1" + "@value": "22-032r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*** Corrigendum - updated 2006-08-08 ***\r\n\r\nThis revised version of this document adds additional allowed authority and objectType values, plus specifies URNs for data types, as proposed in change requests OGC 05-091r2 and 05-060. In addition, corrections have been made to the XML documents listed in Annex A. The changes made in this version are tracked in the Microsoft Word (.doc) format of this document.

This Best Practices Paper specifies Universal Resource Names (URNs) in the ogc URN namespace to be used for identifying definitions. This document specifies the formats used by these URNs, plus a set of specific URNs for specific definitions. These definitions should be used wherever applicable by implementations of various OGC Implementation Specifications, including GML, WMS, WFS, and WCS." + "@value": "These I3S Release notes document changes incorporated into the OGC I3S Community Standard version 1.3." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56542,35 +55777,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-023r1" + "@value": "22-032r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Definition identifier URNs in OGC namespace" + "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Version 1.3 Release Notes" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-012r2", + "@id": "http://www.opengis.net/def/docs/15-058", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-08-19" + "@value": "2015-11-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Stephane Fellah" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56580,27 +55815,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=63285" + "@id": "https://portal.ogc.org/files/?artifact_id=64385" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GeoPackage Plugfest Discussion Paper" + "@value": "15-058" }, { "@language": "en", - "@value": "15-012r2" + "@value": "Testbed-11 Symbology Mediation" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC discussion paper presents the results of the GeoPackage Plugfest. In this\r\ninitiative, participants had the opportunity to evaluate the compliance and interoperability\r\nof software that produces and consumes GeoPackages containing tiled raster data." + "@value": "This OGC® Engineering Report (ER) summarizes the approaches, findings and the results of the Symbology Mediation sub-thread activities of the OGC Testbed-11 Cross Community Interoperability (CCI) Thread. The ER:\r\n•\t Provides an overview of existing standards relevant to symbology mediation, \r\n•\tOutlines the approaches adopted during the testbed, \r\n•\tDescribes the conceptual models and services developed during the testbed to address semantic mediation and portrayal of feature information related to Emergency Management and to some extent to the Aviation domain. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56611,35 +55846,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-012r2" + "@value": "15-058" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoPackage Plugfest Discussion Paper" + "@value": "OGC® Testbed-11 Symbology Mediation" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-138r1", + "@id": "http://www.opengis.net/def/docs/10-140r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-09-12" + "@value": "2018-10-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Michael Werling" + "@value": "Peter Baumann, Stephan Meissl, Jinsongdi Yu" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56649,27 +55884,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=30065" + "@id": "https://docs.ogc.org/is/10-140r2/10-140r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-5 GeoProcessing Workflow Architecture Engineering Report" + "@value": "10-140r2" }, { "@language": "en", - "@value": "07-138r1" + "@value": "Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document describes the Workflow Architecture developed in support of Geoprocessing Workflow and Sensor Web Enablement threads of OWS-5. This information includes the overall architecture description, concepts, and issues. It also provides detail on the Conflation Workflow created as an example implementation for geoprocessing in a workflow. This document establishes a sample architecture and associated lessons learned as general guidance." + "@value": "The OGC Web Coverage Service (WCS) Application Profile - Earth Observation (EO- WCS) defines a profile of WCS 2.0 [OGC 09-110r4] for use on Earth Observation data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56680,35 +55915,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-138r1" + "@value": "10-140r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-5 GeoProcessing Workflow Architecture Engineering Report" + "@value": "OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-111r6", + "@id": "http://www.opengis.net/def/docs/08-077", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-08" + "@value": "2008-07-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Blodgett, Irina Dornblut" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56718,27 +55953,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/14-111r6/14-111r6.html" + "@id": "https://portal.ogc.org/files/?artifact_id=28170" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-111r6" + "@value": "OWS-5 Engineering Report: Local MSD Implementation Profile (GML 3.2.1)" }, { "@language": "en", - "@value": "WaterML 2: Part 3 - Surface Hydrology Features (HY_Features) - Conceptual Model" + "@value": "08-077" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Surface Hydrology Features (HY_Features) standard defines a common conceptual information model for identification of specific hydrologic features independent of their geometric representation and scale. The model describes types of surface hydrologic features by defining fundamental relationships among various components of the hydrosphere. This includes relationships such as hierarchies of catchments, segmentation of rivers and lakes, and the hydrologically determined topological connectivity of features such as catchments and waterbodies. The standard also defines normative requirements for HY_Features implementation schemas and mappings to meet in order to be conformant with the conceptual model.\r\n\r\nThe HY_Features model is based on an abstract catchment feature type that can have multiple alternate hydrology-specific realizations and geometric representations. It supports referencing information about a hydrologic feature across disparate information systems or products to help improve data integration within and among organizations. The model can be applied to cataloging of observations, model results, or other study information involving hydrologic features. The ability to represent the same catchment, river, or other hydrologic feature in several ways is critical for aggregation of cross-referenced or related features into integrated data sets and data products on global, regional, or basin scales." + "@value": "This document contains a data content specification for Local Mission Specific Data (MSD) and is based on the GEOINT Structure Implementation Profile (GSIP) developed by the NGA. This document defines the GML 3.2.1 (ISO 19136) encoding requirements for Local MSD. The structure of the document is based on ISO 19131 (Geographic Information – Data Product Specification)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56749,35 +55984,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-111r6" + "@value": "08-077" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® WaterML 2: Part 3 - Surface Hydrology Features (HY_Features) - Conceptual Model" + "@value": "OGC® OWS-5 Engineering Report: Local MSD Implementation Profile (GML 3.2.1)" } ] }, { - "@id": "http://www.opengis.net/def/docs/00-029", + "@id": "http://www.opengis.net/def/docs/07-098r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2000-05-12" + "@value": "2008-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ron Lake" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56787,27 +56022,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7197" + "@id": "https://portal.ogc.org/files/?artifact_id=25219" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geography Markup Language" + "@value": "07-098r1" }, { "@language": "en", - "@value": "00-029" + "@value": "GeoXACML Implementation Specification - Extension A (GML2) Encoding" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features." + "@value": "This document defines an extension to the GeoXACML Implementation Specification, Verison 1.0 for the GML2 geometry encoding as specified in the GML2 standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56818,35 +56053,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "00-029" + "@value": "07-098r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geography Markup Language" + "@value": "GeoXACML Implementation Specification - Extension A (GML2) Encoding" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-074r2", + "@id": "http://www.opengis.net/def/docs/06-166", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-04-26" + "@value": "2007-01-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Samantha Lavender, Andrew Lavender" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56856,27 +56091,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-074r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=18747" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Disaster Pilot: Provider Readiness Guide" + "@value": "06-166" }, { "@language": "en", - "@value": "21-074r2" + "@value": "A URN namespace for the Open Geospatial Consortium (OGC)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Disasters are geographic events and, therefore, geospatial information, tools, and applications have the potential to support the management of, and response to, disaster scenarios to save lives and limit damage.\r\n\r\nThe use of geospatial data varies significantly across disaster and emergency communities, making the exploitation of geospatial information across a community more difficult. The issue is particularly noticeable when sharing between different organizations involved in disaster response.\r\n\r\nThis difficulty can be mitigated by establishing the right processes to enable data to be shared smoothly and efficiently within a disaster and emergency community. To do this requires the right partnerships, policies, standards, architecture, and technologies to be in place before the disaster strikes. Having such a set-up will enable the technological and human capabilities to quickly find, access, share, integrate, and visualize a range of actionable geospatial information, and provide this rapidly to disaster response managers and first responders.\r\n\r\nFor over 20 years, the Open Geospatial Consortium (OGC) has been working on the challenges of information sharing for emergency and disaster planning, management, and response. In Disaster Pilot 23 (DP23) the aims were to:\r\n\r\ndevelop flexible, scalable, timely and resilient information data workflows to support critical disaster management decisions, enabling stakeholder collaboration; and\r\nprovide applications and visualization tools to promote the wider understanding of how geospatial data can support emergency and disaster communities.\r\nThe Disaster Pilot Provider Guide describes the technical requirements, data structures, and operational standards required to implement the data flows or tools developed in DP23 and Disaster Pilot 21 (DP21) where participants have worked on disaster scenarios relating to the following.\r\n\r\nDroughts\r\nWildland Fires\r\nFlooding\r\nLandslides\r\nHealth & Earth Observation Data for Pandemic Response\r\nCase Studies have focused on the hazards of drought in Manitoba, Canada; wildland fires in the western United States; flooding in the Red River basin, Canada; landslides and flooding in Peru; and pandemic response in Louisiana, United States. The participants have developed a series of data specific workflows to generate either Analysis Ready Datasets (ARD) or Decision Ready Indicators (DRI) alongside a number of tools and applications to support data discovery, collection, or visualization.\r\n\r\nAnnex A describes the tools and applications developed within the Pilots along with technical details and the benefits offered similar to the data flows. The Guide finishes with details of future possibilities and where the Disaster Pilot initiatives could focus next. Annexes B to E give descriptions of the data flows developed, including technical details of input data, processing and transformations undertaken, standards applied, and outputs produced with details of the aspect of disaster management or response supported, benefits offered, and the type of decisions assisted with.\r\n\r\nThe Provider Guide is one of three Guides produced within DP23 together with the User Guide and the Operational Capacity Guide. While the Guides are separate individual documents, the Provider and User Guides work together, mirroring each other in terms of structure. The Operational Capacity Guide is a stand-alone document effectively underpinning the other two.\r\n\r\n" + "@value": " This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC. The formal Namespace identifier (NID) is ogc.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56887,30 +56122,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-074r2" + "@value": "06-166" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Disaster Pilot: Provider Readiness Guide" + "@value": "A URN namespace for the Open Geospatial Consortium (OGC)" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-012", + "@id": "http://www.opengis.net/def/docs/10-074", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-08-17" + "@value": "2010-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Craig Bruce" + "@value": "Theodor Foerster, Bastian Schäffer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -56925,17 +56160,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=33519" + "@id": "https://portal.ogc.org/files/?artifact_id=40311" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-6 Symbology-Encoding Harmonization ER" + "@value": "10-074" }, { "@language": "en", - "@value": "09-012" + "@value": "OWS-7 Feature and Statistical Analysis Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -56945,7 +56180,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the harmonization of OGC Styled Layer Descriptor (SLD) and Symbology Encoding (SE) symbology formats with ISO 19117 symbology format, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology." + "@value": "This Engineering Report (ER) is a deliverable for the OGC Web Service 7 testbed. The focus of this ER is using the OGC Web Processing Service (WPS) interface standard for Feature and Statistical Analysis (FSA). Specifically, the ER documents how to enhance interoperability of FSA processes that are hosted as WPS processes on the Web. This ER is coordinated with the Feature and Decision Fusion (FDF) WPS Profiling ER." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -56956,35 +56191,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-012" + "@value": "10-074" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 Symbology-Encoding Harmonization ER" + "@value": "OWS-7 Feature and Statistical Analysis Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-045r1", + "@id": "http://www.opengis.net/def/docs/11-108", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-03-09" + "@value": "2012-05-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Uwe Voges, Kristian Senkler" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -56994,27 +56229,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=77949" + "@id": "https://portal.ogc.org/files/?artifact_id=46170" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-045r1" + "@value": "OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report)" }, { "@language": "en", - "@value": "Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum" + "@value": "11-108" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Catalogue services are the key technology for locating, managing and maintaining\r\ndistributed geo-resources (i.e. geospatial data, applications and services). With OGC\r\ncatalogue services, client applications are capable of searching for geo-resources in a\r\nstandardized way (i.e. through standardized interfaces and operations) and, ideally, they\r\nare based on a well-known information model, which includes spatial references and\r\nfurther descriptive (thematic) information that enables client applications to search for\r\ngeo-resources in very efficient ways.\r\nWhereas interfaces and operations of OGC catalogue services are well defined, it is left\r\nup to the developer of the system to define a specific information model which a\r\ncatalogue service instance provides. This includes, but is not limited to, the information\r\nwhich can be inserted in the catalog, supported query languages, available search terms,\r\nresponse/result sets, etc. This point is of major importance with respect to interoperability\r\nbetween different catalogue service instances.\r\nIn Europe, running catalogue instances result from work being done within different SDI\r\ninitiatives (e.g. SDI NRW Initiative1, Germany/Netherlands cross-border initiative, JRC\r\nEU Portal, EUROSTAT, Inspire, German SDI initiative). Members of these initiatives\r\nhave developed an ISO-based application profile for ISO19115 metadata for\r\ngeodata/geospatial applications and ISO19119-based metadata for tightly and looselycoupled\r\ngeospatial services. The foundations of this profile were the OGC catalogue\r\nspecification (1.1.1), the OGC Web Registry Server (WRS) 0.0.2, OGC Web Services\r\nStateless Catalogue Profile (StCS) 0.0.6 and ISO 19115/19119 for content description.\r\nOGC's catalogue revision working group (CS-RWG) has revised and integrated the\r\ncatalogue implementation specification v1.1.1 that have resulted in CS 2.0.2. One part of\r\nthis OGC specification comprises the definition of application profiles according to ISO\r\n19106 (Geographic information – Profiles). The overall goal of these profiles is to\r\nimprove interoperability between systems conforming to a specific profile. Experience\r\nhas shown that the need for application profiles results from the fact that in practice, there\r\nis no single solution for catalogue services that fits every user’s needs. As stated in CS\r\n2.0.2, a base profile that provides a basic set of information objects has to be supported\r\nby each catalogue instance; in addition, application profiles for different information\r\ncommunities can be specified.\r\nHence, this document specifies an application profile for ISO 19115:2003/ISO\r\n19119:2005 metadata with support for XML encoding per ISO/TS19139:2007 [ISO/TS19139]2 and HTTP protocol binding. It relies on requirements coming from the\r\nCS/CSW 2.0 specification (OGC CS 2.0.2, OGC document 07-006). The application\r\nprofile will form the basis of conformance tests and reference implementations." + "@value": "This document describes the usability of OGC services and encodings to implement the\r\nOWS-8 observation fusion and tracking thread in an abstract way. The real deployment\r\nand an actual perspective on the engineering and technology viewpoint can be found in\r\nOWS-8 engineering report OGC 11-134, ‘OWS-8 Tracking: Moving Target Indicator\r\nProcess, Workflows and Implementation Results’. In addition, it describes an XMLSchema\r\nbased implementation of the UML information models defined in OWS-8\r\nengineering report “Information Model for Moving Target Indicators and Moving Object\r\nBookmarks” (OGC 11-113).\r\nThe report is also based on the results of the VMTI/GMTI and STANAG 4676 realization\r\nin the OGC concept of operations study; performed as part of OWS 8 and the EC cofunded\r\nresearch project Emergency Support System - ESS” (contract number 217951)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57025,30 +56260,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-045r1" + "@value": "11-108" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum" + "@value": "OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report)" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-155", + "@id": "http://www.opengis.net/def/docs/16-047r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2017-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Weiguo Han, Yuanzheng Shao, Liping Di" + "@value": "Martin Klopfer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -57063,17 +56298,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51891" + "@id": "https://docs.ogc.org/per/16-047r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-9 OWS Innovations WCS for LIDAR Engineering Report " + "@value": "16-047r1" }, { "@language": "en", - "@value": "12-155" + "@value": "Testbed-12 General Feature Model Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -57083,7 +56318,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report is prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiatitive of the Innovations Coverages Sub-Thread. This document represents the OWS-9 OWS Innovations WCS for LIDAR Engineering Report. In this report, the implementation of WCS 2.0 service that serves the LIDAR data in NITF format is introduced. This service supports the JPEG 2000 output format along with GMLJP2 metadata description as well as the JPIP protocol to deliver the output JPEG2000 data. " + "@value": "With a growing requirement to carry out complex analysis in large multi-disciplinary, heterogeneous data collections, an approach is required to extract equivalent information from dissimilar content. The more information can be normalized, the easier it will be to correlate the content. Given that almost all data has a spatio-temporal component, this ER will look into the idea of defining a Spatial-Temporal Service and analyze which collection of data types, operations and architecture patterns would be necessary to spatial-temporal enable any content. This OGC® document reviews the General Feature Model and gives guidelines for necessary modifications to broaden its scope, so that it can be re-used for non-geospatial centric applications and extended as necessary into a general model for all object types." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57094,35 +56329,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-155" + "@value": "16-047r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-9 OWS Innovations WCS for LIDAR Engineering Report " + "@value": "Testbed-12 General Feature Model Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-132r4", + "@id": "http://www.opengis.net/def/docs/03-002r9", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-02-24" + "@value": "2006-01-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Martin Lechner" + "@value": "Craig Bruce" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -57132,27 +56367,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=62168" + "@id": "https://portal.ogc.org/files/?artifact_id=13636" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-132r4" + "@value": "03-002r9" }, { "@language": "en", - "@value": "Augmented Reality Markup Language 2.0 (ARML 2.0) " + "@value": "Binary Extensible Markup Language (BXML) Encoding Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Standard defines the Augmented Reality Markup Language 2.0 (ARML 2.0). ARML 2.0 allows users to describe virtual objects in an Augmented Reality (AR) scene with their appearances and their anchors (a broader concept of a location) related to the real world. Additionally, ARML 2.0 defines ECMAScript bindings to dynamically modify the AR scene based on user behavior and user input." + "@value": "This OGC Best Practices document specifies a binary encoding format for the efficient representation of XML data, especially scientific data that is characterized by arrays of numbers. This encoding format is applicable to any application that uses XML format." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57163,35 +56398,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-132r4" + "@value": "03-002r9" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Augmented Reality Markup Language 2.0 (ARML 2.0)" + "@value": "Binary Extensible Markup Language (BXML) Encoding Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-157", + "@id": "http://www.opengis.net/def/docs/09-142r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-10-18" + "@value": "2010-02-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jim Greenwood" + "@value": "Chun-fu Lin, Zhong-Hung Lee, Jen-Chu Liu, Kuo-Yu Chuang" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -57201,27 +56436,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46435" + "@id": "https://portal.ogc.org/files/?artifact_id=36261" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-157" + "@value": "09-142r1" }, { "@language": "en", - "@value": "Corrigendum 1 for OGC Web Services Common Standard v2.0.0 - Multilingual" + "@value": "Open GeoSMS Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document being corrected specifies many of the aspects that are, or should be, common to all or multiple OWS interface Implementation Specifications. The Common Implementation Specification aspects specified by this document currently include:\r\na) Operation request and response contents, most partial\r\nb) Parameters and data structures included in operation requests and responses c) XML and KVP encoding of operation requests and responses" + "@value": "This standard specifies the location formats to be used by SMS for mobile phones and in other systems handling the SMS with location formats produced by mobile phones or LBS services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57232,35 +56467,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-157" + "@value": "09-142r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Corrigendum 1 for OGC Web Services Common Standard v2.0.0 - Multilingual" + "@value": "OGC®: Open GeoSMS Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-084r2", + "@id": "http://www.opengis.net/def/docs/09-147r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-04-28" + "@value": "2013-03-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Uwe Voges, Frédéric Houbie, Nicolas Lesage, Marie-Lise Vautier" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -57270,27 +56505,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=56905" + "@id": "https://portal.ogc.org/files/?artifact_id=50140" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "13-084r2" + "@value": "09-147r3" }, { "@language": "en", - "@value": "I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0" + "@value": "Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - Corrigendum " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Catalogue Services 2.0 specification (OGC 07-006r1) establishes a general framework for implementing catalogue services that can be applied to meet the needs of stakeholders in a wide variety of domains.\r\nThe ebRIM application profile (OGC 07-110r4) is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0 specification; it qualifies as a ‘Class 2’ profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards. The ebRIM application profile also includes a Basic extension package (OGC 07-144r4) of the OASIS ebXML Registry Information Model (ebRIM) providing artefacts of general utility in the geomatics domain.\r\nThis document provides an extension package aligned with the ebRIM application profile of CS-W for the cataloguing of ISO 19115, ISO19115-2 and ISO 19119 compliant metadata. It was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [HMA] and related projects. Some input came from the OGC OWS9 initiative.\r\nThis document supersedes the former document OGC Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W, OGC 07-038r3 (Version: 0.1.12).\r\n" + "@value": "This document specifies an extension to the OGC Web Coverage Service (WCS) 2.0 core to allow for client/server communication using HTTP GET with key/value pair (KVP) encod-ing. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57301,35 +56536,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-084r2" + "@value": "09-147r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0" + "@value": "OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - Corrigendum " } ] }, { - "@id": "http://www.opengis.net/def/docs/15-078r6", + "@id": "http://www.opengis.net/def/docs/21-074r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-07-26" + "@value": "2024-04-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steve Liang, Chih-Yuan Huang, Tania Khalafbeigi" + "@value": "Samantha Lavender, Andrew Lavender" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -57339,27 +56574,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/15-078r6/15-078r6.html" + "@id": "https://docs.ogc.org/per/21-074r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "SensorThings API Part 1: Sensing" + "@value": "OGC Disaster Pilot: Provider Readiness Guide" }, { "@language": "en", - "@value": "15-078r6" + "@value": "21-074r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC SensorThings API provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the Web. At a high level the OGC SensorThings API provides two main functionalities and each function is handled by a part. The two parts are the Sensing part and the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. The Tasking part is planned as a future work activity and will be defined in a separate document as the Part II of the SensorThings API." + "@value": "Disasters are geographic events and, therefore, geospatial information, tools, and applications have the potential to support the management of, and response to, disaster scenarios to save lives and limit damage.\r\n\r\nThe use of geospatial data varies significantly across disaster and emergency communities, making the exploitation of geospatial information across a community more difficult. The issue is particularly noticeable when sharing between different organizations involved in disaster response.\r\n\r\nThis difficulty can be mitigated by establishing the right processes to enable data to be shared smoothly and efficiently within a disaster and emergency community. To do this requires the right partnerships, policies, standards, architecture, and technologies to be in place before the disaster strikes. Having such a set-up will enable the technological and human capabilities to quickly find, access, share, integrate, and visualize a range of actionable geospatial information, and provide this rapidly to disaster response managers and first responders.\r\n\r\nFor over 20 years, the Open Geospatial Consortium (OGC) has been working on the challenges of information sharing for emergency and disaster planning, management, and response. In Disaster Pilot 23 (DP23) the aims were to:\r\n\r\ndevelop flexible, scalable, timely and resilient information data workflows to support critical disaster management decisions, enabling stakeholder collaboration; and\r\nprovide applications and visualization tools to promote the wider understanding of how geospatial data can support emergency and disaster communities.\r\nThe Disaster Pilot Provider Guide describes the technical requirements, data structures, and operational standards required to implement the data flows or tools developed in DP23 and Disaster Pilot 21 (DP21) where participants have worked on disaster scenarios relating to the following.\r\n\r\nDroughts\r\nWildland Fires\r\nFlooding\r\nLandslides\r\nHealth & Earth Observation Data for Pandemic Response\r\nCase Studies have focused on the hazards of drought in Manitoba, Canada; wildland fires in the western United States; flooding in the Red River basin, Canada; landslides and flooding in Peru; and pandemic response in Louisiana, United States. The participants have developed a series of data specific workflows to generate either Analysis Ready Datasets (ARD) or Decision Ready Indicators (DRI) alongside a number of tools and applications to support data discovery, collection, or visualization.\r\n\r\nAnnex A describes the tools and applications developed within the Pilots along with technical details and the benefits offered similar to the data flows. The Guide finishes with details of future possibilities and where the Disaster Pilot initiatives could focus next. Annexes B to E give descriptions of the data flows developed, including technical details of input data, processing and transformations undertaken, standards applied, and outputs produced with details of the aspect of disaster management or response supported, benefits offered, and the type of decisions assisted with.\r\n\r\nThe Provider Guide is one of three Guides produced within DP23 together with the User Guide and the Operational Capacity Guide. While the Guides are separate individual documents, the Provider and User Guides work together, mirroring each other in terms of structure. The Operational Capacity Guide is a stand-alone document effectively underpinning the other two.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57370,30 +56605,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-078r6" + "@value": "21-074r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC SensorThings API Part 1: Sensing" + "@value": "OGC Disaster Pilot: Provider Readiness Guide" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-038r2", + "@id": "http://www.opengis.net/def/docs/11-061r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-04" + "@value": "2012-02-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Tom Landry" + "@value": "David Burggraf" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -57408,17 +56643,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-038r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=45380" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-038r2" + "@value": "11-061r1" }, { "@language": "en", - "@value": "Machine Learning Engineering Report" + "@value": "OWS-8 AIXM Metadata Guidelines Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -57428,7 +56663,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) describes the application and use of OGC Web Services (OWS) for integrating Machine Learning (ML), Deep Learning (DL) and Artificial Intelligence (AI) in the OGC Testbed-14 Modeling, Portrayal, and Quality of Service (MoPoQ) Thread. This report is intended to present a holistic approach on how to support and integrate emerging AI and ML tools using OWS, as well as publishing their input and outputs. This approach should seek efficiency and effectiveness of knowledge sharing.\r\n\r\nThis engineering report will describe: experiences, lessons learned, best practices for workflows, service interaction patterns, application schemas, and use of controlled vocabularies. It is expected that the description of workflows for geospatial feature extraction will be more complex than the implementations found in the deliverables." + "@value": "This OGC® Engineering Report provides guidelines for ISO metadata usage in AIXM 5.1\r\nconformant to the requirements of OGC 10-195 (Requirements for Aviation Metadata)\r\nand the recommendations of OGC 10-196r1 (Guidance on the Aviation Metadata\r\nProfile), with the exception of non-ISO metadata elements listed in these documents." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57439,35 +56674,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-038r2" + "@value": "11-061r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Machine Learning Engineering Report" + "@value": "OWS-8 AIXM Metadata Guidelines Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-028r3", + "@id": "http://www.opengis.net/def/docs/16-007r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-16" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "Sara Saeedi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -57477,27 +56712,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=15588" + "@id": "https://docs.ogc.org/is/16-007r5/16-007r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Sensor Alert Service" + "@value": "Volume 11: OGC CDB Core Standard Conceptual Model" }, { "@language": "en", - "@value": "06-028r3" + "@value": "16-007r5" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Sensor Alert Service (SAS) can be compared with an event notification system. The sensor node is the object of interest. Each node has to advertise its publications at a SAS (advertise). " + "@value": "This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB Standard. The objective of this document is to provide an core conceptual model for a CDB data store (repository). The model is represented using UML (Unified Modeling Language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering the UML diagrams and documentation from the original CDB submission OGC Common DataBase Volume 1 Best Practice, 2015 as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113r5]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57508,35 +56743,97 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-028r3" + "@value": "16-007r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Alert Service" + "@value": "Volume 11: OGC CDB Core Standard Conceptual Model" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-111r1", + "@id": "http://www.opengis.net/def/doc-type/techpaper", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/18-008r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-131r2" + }, + { + "@id": "http://www.opengis.net/def/docs/19-078r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-110" + }, + { + "@id": "http://www.opengis.net/def/docs/11-159" + }, + { + "@id": "http://www.opengis.net/def/docs/07-165r1" + }, + { + "@id": "http://www.opengis.net/def/docs/14-115" + }, + { + "@id": "http://www.opengis.net/def/docs/11-145" + }, + { + "@id": "http://www.opengis.net/def/docs/14-095" + }, + { + "@id": "http://www.opengis.net/def/docs/15-002r5" + }, + { + "@id": "http://www.opengis.net/def/docs/10-124r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-128" + }, + { + "@id": "http://www.opengis.net/def/docs/19-076" + }, + { + "@id": "http://www.opengis.net/def/docs/09-044r3" + }, + { + "@id": "http://www.opengis.net/def/docs/18-004r1" + }, + { + "@id": "http://www.opengis.net/def/docs/20-085r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-036" + }, + { + "@id": "http://www.opengis.net/def/docs/16-019r4" + }, + { + "@id": "http://www.opengis.net/def/docs/12-026" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/23-022r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-04-14" + "@value": "2023-08-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Marie-Françoise Voidrot-Martinez, Chris Little, Jürgen Seib, Roy Ladner, Adrian Custer, Jeff de La B" + "@value": "Hsiao-Yuan (Samuel) Yin, Yi-Chia (Vincent) Lin, Chih-Wei (Will) Kuan, Cheng-Yan Tsai, Lok-Man (Lawre" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -57546,27 +56843,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=56394" + "@id": "https://docs.ogc.org/dp/23-022r1.pdf" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-111r1" + "@value": "Establishing the Framework of Disaster Early Warning Mechanisms - A Case Study of Slope Disaster" }, { "@language": "en", - "@value": "Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data" + "@value": "23-022r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document proposes a set of best practices and guidelines for implementing and using the Open Geospatial Consortium (OGC) Web Map Service (WMS) to serve maps which are time-dependent or elevation-dependent. In particular, clarifications and restrictions on the use of WMS are defined to allow unambiguous and safe interoperability between clients and servers, in the context of expert meteorological and oceanographic usage and non-expert usage in other communities. This Best Practice document applies specifically to WMS version 1.3, but many of the concepts and recommendations will be applicable to other versions of WMS or to other OGC services, such as the Web Coverage Service." + "@value": "The impact of global climate change has led to a rise in the frequency of natural\r\ndisasters in numerous countries resulting in substantial losses in terms of both human lives and the global economy. The establishment of a robust disaster early-warning mechanism is recommended that will empower communities to proactively engage in disaster reduction and prevention measures before such calamities occur, thereby effectively reducing losses.\r\nThe Common Alerting Protocol (CAP) is an internationally recognized digital\r\nmessage format and protocol for all types of alarms and early warning notifications. It was officially adopted by The Federal Emergency Management Agency (FEMA) in 2010 for its Integrated Public Alert and Warning System (IPAWS). It has also been successfully implemented in Taiwan for many years. However, different countries may employ other color-coded warning systems to indicate varying degrees of disaster severity. This disparity in warning standards can cause public confusion during emergencies, leading to increased costs in disaster management. This paper proposes a framework that utilizes red and yellow warning lights for issuing alerts. Adopting a standardized approach will mitigate confusion and enhance the efficiency of disaster response and management.\r\nThis study proposes a framework that uses red and yellow warning mechanisms for\r\nissuing alerts such as the disaster early warning for debris flows and large-scale\r\nlandslides established by the Soil and Water Conservation Bureau (SWCB). This\r\ninvestigation will explore the feasibility of standardizing yellow and red warning\r\npublishing rules." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57577,35 +56874,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-111r1" + "@value": "23-022r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data" + "@value": "Establishing the Framework of Disaster Early Warning Mechanisms - A Case Study of Slope Disaster" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-009r3", + "@id": "http://www.opengis.net/def/docs/14-016", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-02-23" + "@value": "2014-07-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Arne Bröring;Simon Jirka;Matthes Rieke, Benjamin Pross" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -57615,27 +56912,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=72717" + "@id": "https://portal.ogc.org/files/?artifact_id=58925" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-009r3" + "@value": "Testbed-10 CCI VGI Engineering Report" }, { "@language": "en", - "@value": "Volume 6: OGC CDB Rules for Encoding Data using OpenFlight" + "@value": "14-016" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of that document for a general overview." + "@value": "This Engineering Report was created as a deliverable for the OGC Testbed 10 (Testbed-\r\n10) initiative of the OGC Interoperability Program. This report describes an approach for\r\nintegrating Volunteered Geographic Information (VGI) into a spatial data infrastructure\r\nand reports on findings about the advancements using VGI resources. It includes\r\noptimization ideas, service change recommendations, and lessons learned.\r\nThis is not a normative document." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57646,35 +56943,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-009r3" + "@value": "14-016" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 6: OGC CDB Rules for Encoding Data using OpenFlight" + "@value": "OGC® Testbed-10 CCI VGI Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-038R2", + "@id": "http://www.opengis.net/def/docs/16-137r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-10-02" + "@value": "2017-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ben Domenico" + "@value": "Lorenzo Bigagli" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -57684,27 +56981,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=50294" + "@id": "https://docs.ogc.org/per/16-137r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard" + "@value": "16-137r2" }, { "@language": "en", - "@value": "11-038R2" + "@value": "Testbed-12 PubSub / Catalog Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard deals with enhancements to the netCDF (Network Common Data Form) data model for array-oriented scientific data..\r\nTwo important data models for netCDF are:\r\n- the “classic” netCDF model, used for netCDF-3 and earlier versions\r\n- an enhanced data model, used in netCDF-4 and later versions.\r\nThe netCDF classic data model is defined in OGC 10-091r3, “NetCDF Core.”\r\nThis document specifies a netCDF extension standard for the enhanced data model. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space- and time-varying phenomena.\r\nNetCDF (network Common Data Form) is a data model for array-oriented scientific data. The netCDF classic data model is specified in the netCDF core specification. This standard specifies the enhanced data model. A freely distributed collection of access libraries implementing support for that data model in a machine-independent format are available. Together, the interfaces, libraries, and format support the creation, access, and sharing of multi-dimensional scientific data." + "@value": "This document describes how the OGC PubSub standard can be used as a mechanism to automatically notify analysts of data availability for CSW and other OGC Web Services (e.g. WFS, WCS). In particular, this document proposes the following:\r\n\r\nSpecific PubSub 1.0 extensions for CSW 2.0.2 and 3.0, leveraging on standard functionalities, data models, and semantics to enable sending notifications based on user-specified area of interest and/or keywords;\r\n\r\nA general, basic mechanism for enabling PubSub for the generic OGC Web Service over the existing request/reply OWS’s, i.e. usual requests as filters, usual responses as appropriate updates/data pushes, existing semantics and syntax expressiveness.\r\n\r\nThis document is the result of activity performed within the Large-Scale Analytics (LSA) Thread of the OGC Testbed 12 Interoperability initiative, being identified as document deliverable A074 PubSub / Catalog Engineering Report. This document also captures lessons learnt from the implementation of component deliverable A016 CSW 2.0.2 with PubSub Core Support Server." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57715,35 +57012,112 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-038R2" + "@value": "16-137r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard" + "@value": "Testbed-12 PubSub / Catalog Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-162r1", + "@id": "http://www.opengis.net/def/doc-type/isc", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/07-045r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r12a" + }, + { + "@id": "http://www.opengis.net/def/docs/09-083r4" + }, + { + "@id": "http://www.opengis.net/def/docs/14-005r4" + }, + { + "@id": "http://www.opengis.net/def/docs/18-010r11" + }, + { + "@id": "http://www.opengis.net/def/docs/06-027r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-128r15" + }, + { + "@id": "http://www.opengis.net/def/docs/11-157" + }, + { + "@id": "http://www.opengis.net/def/docs/07-036r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-158" + }, + { + "@id": "http://www.opengis.net/def/docs/09-026r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-091r6" + }, + { + "@id": "http://www.opengis.net/def/docs/14-065r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-146r8" + }, + { + "@id": "http://www.opengis.net/def/docs/04-094r1" + }, + { + "@id": "http://www.opengis.net/def/docs/14-005r5" + }, + { + "@id": "http://www.opengis.net/def/docs/07-122r2" + }, + { + "@id": "http://www.opengis.net/def/docs/07-045r2" + }, + { + "@id": "http://www.opengis.net/def/docs/07-010" + }, + { + "@id": "http://www.opengis.net/def/docs/14-065r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-147r3" + }, + { + "@id": "http://www.opengis.net/def/docs/18-075" + }, + { + "@id": "http://www.opengis.net/def/docs/08-050" + }, + { + "@id": "http://www.opengis.net/def/docs/16-083r3" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/15-018r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "0000-00-00" + "@value": "2016-02-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jinsongdi Yu, Peter Baumann" + "@value": "Peter Taylor" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -57753,27 +57127,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51911" + "@id": "https://docs.ogc.org/is/15-018r2/15-018r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-9 WCS Conformance Testing Engineering Report" + "@value": "15-018r2" }, { "@language": "en", - "@value": "12-162r1" + "@value": "WaterML2.0: part 2 - Ratings, Gaugings and Sections" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report was prepared as a deliverable for the OGC Web Services, Phase\r\n9 (OWS-9) initiative of the OGC Interoperability Program. The document presents the\r\nwork completed with respect to the Conformance & Interoperability Testing &\r\nEvaluation sub-thread within OWS-9.\r\nThis Engineering Report describes and evaluates the specification of WCS 2.0 core\r\ncorrigenda and extensions’ Abstract Test Suite (ATS) and the implementation of ETS for\r\nuse within an OGC SOA processing chain." + "@value": "This standard defines an information model and XML encoding for exchanging the\r\nfollowing three hydrological information resources:\r\n1. Conversion tables, or conversion curves, that are used for the conversion of\r\nrelated hydrological phenomenon.\r\n2. Gauging observations – the observations performed to develop conversion table\r\nrelationships.\r\n3. Cross sections - survey observations made of the geometric structure of features,\r\nsuch as river channels, storages etc.\r\nMetadata and vocabularies are defined that together provide a means for parties to\r\nexchange these concepts using common semantics.\r\nThis standard is the second part of the WaterML2.0 suite of standards, building on part 1\r\nthat addresses the exchange of time series.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57784,35 +57158,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-162r1" + "@value": "15-018r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-9 WCS Conformance Testing Engineering Report" + "@value": "OGC WaterML2.0: part 2 - Ratings, Gaugings and Sections" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-007r1", + "@id": "http://www.opengis.net/def/docs/18-035", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-06-12" + "@value": "2019-02-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Tom Bychowski" + "@value": "Stephane Fellah" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -57822,27 +57196,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=3840" + "@id": "https://docs.ogc.org/per/18-035.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Location Services (OpenLS): Navigation Service [Part 6]" + "@value": "Semantically Enabled Aviation Data Models Engineering Report" }, { "@language": "en", - "@value": "03-007r1" + "@value": "18-035" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OpenGIS " + "@value": "This Engineering Report (ER) summarizes the OGC Testbed-14 findings and recommendations to “semantically enable” existing data and metadata models used in the aviation industry. Examples of such data and metadata models include Aeronautical Information Exchange Model (AIXM) [1], Weather Information Exchange Model (WXXM) [2], Flight Information Exchange Model (FIXM) [3],Web Service Description Document (WSDD), Service Description Conceptual Model (SDCM) [4]). These models use Linked Data standards to represent this information and aim to improve the search and discovery of services and information in the aviation domain using the System Wide Information Management (SWIM) environment. This report provides a review of the existing data models and explore different approaches to provide a semantic representation of the current metadata and data models used in the aviation domain. The ER also discusses the role and importance of the controlled vocabularies." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57853,35 +57227,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-007r1" + "@value": "18-035" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Location Services (OpenLS): Navigation Service [Part 6]" + "@value": "OGC Testbed-14: Semantically Enabled Aviation Data Models Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-014r1", + "@id": "http://www.opengis.net/def/docs/99-049", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-04-22" + "@value": "1999-05-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed, George Percivall" + "@value": "Keith Ryden" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-atb" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -57891,27 +57265,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=5393" + "@id": "https://portal.ogc.org/files/?artifact_id=829" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-014r1" + "@value": "99-049" }, { "@language": "en", - "@value": "OGC Technical Document Baseline" + "@value": "Simple Features Implementation Specification for SQL" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-atb" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Spreadsheet of OGC Technical Document Baseline" + "@value": "The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57922,30 +57296,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-014r1" + "@value": "99-049" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Technical Document Baseline" + "@value": "OpenGIS Simple Features Implementation Specification for SQL" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-006", + "@id": "http://www.opengis.net/def/docs/10-079r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-08-05" + "@value": "2010-09-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Keith Pomakis" + "@value": "Thomas Everding" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -57960,17 +57334,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=33269" + "@id": "https://portal.ogc.org/files/?artifact_id=40133" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-006" + "@value": "10-079r3" }, { "@language": "en", - "@value": "OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS" + "@value": "OWS-7 Aviation Architecture Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -57980,7 +57354,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the development of SOAP/XML and REST interfaces for the Web Map Tiling Service (WMTS)." + "@value": "The document describes the architecture that was implemented in the Aviation thread of OWS-7. The document provides an overview of the architecture and describes the implemented components. In addition it discusses “eventing” and notification techniques relevant for the aviation domain." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -57991,35 +57365,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-006" + "@value": "10-079r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS" + "@value": "OWS-7 Aviation Architecture Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-044", + "@id": "http://www.opengis.net/def/docs/05-111r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-03-09" + "@value": "2006-05-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Roland M. Wagner" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -58029,27 +57403,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-044.html" + "@id": "https://portal.ogc.org/files/?artifact_id=13958" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Web Feature Service Synchronization" + "@value": "Access Control & Terms of Use (ToU) \"Click-through\" IPR Management" }, { "@language": "en", - "@value": "16-044" + "@value": "05-111r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report describes a protocol for synchronizing data between two enterprise servers. While the protocol itself is generic, this engineering report describes its application to web feature servers.\r\n\r\nIn the simplest terms, the protocol involves each synchronization peer accessing the other’s Sync resource to get the set of changed objects since the last time the Sync resource was accessed. In the case of web feature servers, the objects are features. The requesting peer then compare that list of changed features with the identically identified features in its data store and performs any necessary changes so that the feature states match.\r\n\r\nContinuing the work done in Testbed-11, this engineering report describes the implementation of a Sync operation in a WFS server that:\r\n\r\nEnhances the Sync operation from Testbed-11 to include an abstract query element where each service type can then substitute their specific query syntax for identifying the specific sub-set of changed features to be synchronized. In the case of the WFS, several query syntaxes may be used including the wfs:Query element and a REST based feature type URI with query parameters.\r\n\r\nExtends the definition of the Sync operation with the addition of a resultType parameter to allow a client to obtain a hit count of the number of features that a Sync operation shall return.\r\n\r\nShall investigate the proper procedure for handling resource references. Implementing the resolvePath parameter alone is not sufficient to ensure complete data set synchronization.\r\n\r\nShall investigate concurrency and consistency issues." + "@value": "This document demonstrats a number of functional capabilities related to rights management (Terms-of-Use, Authentication, content services) that need to be described and chained. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58060,30 +57434,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-044" + "@value": "05-111r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Web Feature Service Synchronization" + "@value": "Access Control & Terms of Use (ToU) \"Click-through\" IPR Management" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-027r3", + "@id": "http://www.opengis.net/def/docs/09-132r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-16" + "@value": "2009-10-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Timo Thomas" + "@value": "Thomas Usländer (Ed.)" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -58098,17 +57472,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=58922" + "@id": "https://portal.ogc.org/files/?artifact_id=35888" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Feature Service (WFS) Temporality Extension" + "@value": "09-132r1" }, { "@language": "en", - "@value": "12-027r3" + "@value": "Specification of the Sensor Service Architecture (SensorSA)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -58118,7 +57492,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC discussion paper provides a proposal for a temporality extension for the WFS\r\n2.0 and FES 2.0 standard. It is based on the work of and experiences made in several\r\nOWS test beds, in particular OWS-7, OWS-8 and OWS-9, Aviation threads and\r\ndiscussions at the 2011 OGC TC meeting in Brussels, Belgium. It partially replaces and\r\nadvances the document “OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via\r\nan OGC WFS 2.0” [4]." + "@value": "Specification of a generic service-oriented architecture integrating the access to, the management and the processing of sensor-related information based upon the emerging standards of the Open geospatial Consortium (OGC), and resulting from the requirements analysis of diverse application domains such as maritime risk management, observation of geo-hazards and monitoring of air quality." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58129,30 +57503,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-027r3" + "@value": "09-132r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Feature Service (WFS) Temporality Extension" + "@value": "Specification of the Sensor Service Architecture (SensorSA)" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-082r1", + "@id": "http://www.opengis.net/def/docs/19-040", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-07-08" + "@value": "2020-01-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sergio Taleisnik" + "@value": "Christian Autermann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -58167,17 +57541,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-082r1.html" + "@id": "https://docs.ogc.org/per/19-040.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-082r1" + "@value": "19-040" }, { "@language": "en", - "@value": "Vector Tiles Pilot 2: Tile Set Metadata Engineering Report" + "@value": "WPS Routing API ER" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -58187,7 +57561,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Vector Tiles Pilot 2: Tile Set Metadata Engineering Report (ER) describes a conceptual model for Tile Set Metadata that provides information about the intended usage of a Tile Set as well as the origin, security level, tiling scheme, layers and feature properties contained within. In this ER, a tile set is a series of tiles containing data and following a common tiling scheme.\r\n\r\nThe metadata is intended to facilitate retrieval of tile sets and describes the major characteristics of tile sets without actually accessing the tiles nor the content contained in a tile. Such a process could be time consuming when there are a large number of tiles in a tile set.\r\n\r\nAdditionally, this ER summarizes the discussions about Tile Set Metadata among the VTP2 participants, and draws up conclusions and recommendations for future work on the subject.\r\n\r\nFinally, this ER describes the Technology Integration Experiments (TIEs) performed to test the prototype implementation of the proposed Tile Set Metadata Model on API endpoints, client applications, and GeoPackages." + "@value": "The goal of this OGC WPS Routing API Engineering Report (ER) is to document the specification of an Application Programming Interface (API) which supports geographic routing. The specification includes two alternative approaches to such an API, one based on the current draft of the OGC API - Processes draft specification and another based on the OGC API principles (and the OGC API - Common draft specification). Both approaches facilitate a common Route Exchange Model." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58198,30 +57572,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-082r1" + "@value": "19-040" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Vector Tiles Pilot 2: Tile Set Metadata Engineering Report" + "@value": "WPS Routing API ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-121r2", + "@id": "http://www.opengis.net/def/docs/09-018", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-12-22" + "@value": "2009-04-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Ben Domenico, Stefano Nativi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -58236,17 +57610,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=72295" + "@id": "https://portal.ogc.org/files/?artifact_id=32195" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-121r2" + "@value": "09-018" }, { "@language": "en", - "@value": "Web Query Service " + "@value": "Web Coverage Service (WCS) 1.1 extension for CF-netCDF 3.0 encoding" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -58256,7 +57630,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Web Query Service (WQS) defines a service interface for retrieving any kind of subset of information provided by the server addressed. WQS is com¬pletely agnostic of any semantics and, therefore, not bound to any predefined structures, such as coordinates, fea-tures, coverages, or metadata. This makes WQS particularly suitable for retrieval from heter-ogeneous data offerings combining features, coverages, and catalog information in some ap-plication-defined way. A second use case is selective retrieval from a Capabilities document to avoid downloading large such documents and performing extraction on client side.\r\nTo this end, the Query request type is defined which, based on an XPath expression as input, extracts the matching information from the service’s offering and returns it (currently: as an XML document).\r\n" + "@value": "This extension of the WCS standard specifies an Information Community data model with the related encoding that may optionally be implemented by WCS servers. This extension specification allows clients to evaluate, request and use data encoded in CF-netCDF3 format from a WCS server.\r\nThis document is an extension of the Web Coverage Service (WCS) 1.1 Corrigendum 2 (version 1.1.2) Implementation Standard [OGC 07-067r5]. With small changes, this extension is expected to also apply to WCS 1.2. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58267,35 +57641,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-121r2" + "@value": "09-018" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Query Service " + "@value": "Web Coverage Service (WCS) 1.1 extension for CF-netCDF 3.0 encoding" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-062", + "@id": "http://www.opengis.net/def/docs/09-042", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-11-14" + "@value": "2009-10-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona" + "@value": "Steffen Neubauer, Alexander Zipf" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -58305,27 +57679,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-062.html" + "@id": "https://portal.ogc.org/files/?artifact_id=32904" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC API Hackathon 2019 Engineering Report" + "@value": "3D-Symbology Encoding Discussion Draft" }, { "@language": "en", - "@value": "19-062" + "@value": "09-042" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The subject of this Engineering Report (ER) is a hackathon event that was held from 20 to 21 June 2019 to advance the development of OGC Application Programming Interface (API) specifications. An API is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The OGC API Hackathon 2019, as the event was called, was hosted by Geovation at its hub in London, United Kingdom. The event was sponsored by the European Space Agency (ESA) and Ordnance Survey." + "@value": "This document present an extension of the Symbology Encoding (SE) /Styled Layer Descriptor (SLD) specifications into 3D as a separate profile." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58336,30 +57710,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-062" + "@value": "09-042" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API Hackathon 2019 Engineering Report" + "@value": "3D-Symbology Encoding Discussion Draft" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-043", + "@id": "http://www.opengis.net/def/docs/18-022r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-10-22" + "@value": "2019-02-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stefan Achtsnit, Joachim Ungar, and Stephan Meißl (EOX), Anja Vrecko and Grega Milčinski (Sinergise)" + "@value": "Yann Le Franc" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -58374,17 +57748,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-043.html" + "@id": "https://docs.ogc.org/per/18-022r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Earth Observation Applications Pilot: EOX-Sinergise-DLR-UVT-Terrasigna Engineering Report" + "@value": "18-022r1" }, { "@language": "en", - "@value": "20-043" + "@value": "SWIM Information Registry Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -58394,7 +57768,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report documents findings, achievements, and learnings gained through activities during the OGC Earth Observation (EO) Applications Pilot by the EOX team (EOX, DLR, UVT, Sinergise, and Terrasigna). Both perspectives, from application developer’s as well as from platform provider’s view, are represented here." + "@value": "This Engineering Report (ER) summarizes the findings and recommendations for building an information registry working together with the existing Federal Aviation Administration (FAA) System Wide Information Management (SWIM) aviation service registries, the National Airspace System Service Registry and Repository (NSRR). This information registry should allow the different Air Traffic Management (ATM) stakeholders to retrieve the appropriate service registered in the NSRR using the semantic representation of real-life entities represented by the data served by the services (e.g. estimated departure time, estimated time of arrival, ”runway true bearing”…). To support the integration of this domain-specific information, the ER proposes different strategies based on the semantic annotation proposal made in OGC 08-167r2 [1] extended with a recent World Wide Web Consortium (W3C) recommendation, the Web Annotation data model [1]. In particular, the ER focuses on a solution using the W3C web annotation data model which adds semantics to the NSRR without changing the content of the database. This solution provides a low-cost, flexible and efficient alternative to add domain-specific semantics to NSRR content. The ER concludes with remarks on the elements necessary for implementing the information registry as a web annotation store as well as the necessity to build domain-specific knowledge models to support further interoperability and further service discoverability and the added-values of using the Data Catalog (DCAT) or Semantic Registry Information Model (SRIM) to better describe and retrieve ATM services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58405,35 +57779,261 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-043" + "@value": "18-022r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Earth Observation Applications Pilot: EOX-Sinergise-DLR-UVT-Terrasigna Engineering Report" + "@value": "OGC Testbed-14: SWIM Information Registry Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-157r4", + "@id": "http://www.opengis.net/def/doc-type/d-dp/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Discussion Paper - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Discussion Paper - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/05-078" + }, + { + "@id": "http://www.opengis.net/def/docs/05-035r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-013" + }, + { + "@id": "http://www.opengis.net/def/docs/06-080" + }, + { + "@id": "http://www.opengis.net/def/docs/05-089r1" + }, + { + "@id": "http://www.opengis.net/def/docs/02-026r1" + }, + { + "@id": "http://www.opengis.net/def/docs/19-091r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-167r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-166" + }, + { + "@id": "http://www.opengis.net/def/docs/06-057r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-080r1" + }, + { + "@id": "http://www.opengis.net/def/docs/01-013r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-007" + }, + { + "@id": "http://www.opengis.net/def/docs/07-024" + }, + { + "@id": "http://www.opengis.net/def/docs/12-066" + }, + { + "@id": "http://www.opengis.net/def/docs/04-017r1" + }, + { + "@id": "http://www.opengis.net/def/docs/04-038r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-131" + }, + { + "@id": "http://www.opengis.net/def/docs/05-107" + }, + { + "@id": "http://www.opengis.net/def/docs/02-027" + }, + { + "@id": "http://www.opengis.net/def/docs/07-057r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-027r2" + }, + { + "@id": "http://www.opengis.net/def/docs/03-064r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-028r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-057r3" + }, + { + "@id": "http://www.opengis.net/def/docs/11-169" + }, + { + "@id": "http://www.opengis.net/def/docs/03-008r2" + }, + { + "@id": "http://www.opengis.net/def/docs/05-112" + }, + { + "@id": "http://www.opengis.net/def/docs/02-039r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-038" + }, + { + "@id": "http://www.opengis.net/def/docs/05-077" + }, + { + "@id": "http://www.opengis.net/def/docs/06-035r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-093" + }, + { + "@id": "http://www.opengis.net/def/docs/01-044r2" + }, + { + "@id": "http://www.opengis.net/def/docs/03-002r8" + }, + { + "@id": "http://www.opengis.net/def/docs/05-088r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-142r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-018" + }, + { + "@id": "http://www.opengis.net/def/docs/08-008r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-054r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-087r3" + }, + { + "@id": "http://www.opengis.net/def/docs/03-088r1" + }, + { + "@id": "http://www.opengis.net/def/docs/04-013r4" + }, + { + "@id": "http://www.opengis.net/def/docs/04-040" + }, + { + "@id": "http://www.opengis.net/def/docs/03-013" + }, + { + "@id": "http://www.opengis.net/def/docs/02-026r4" + }, + { + "@id": "http://www.opengis.net/def/docs/14-004" + }, + { + "@id": "http://www.opengis.net/def/docs/05-109r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-126" + }, + { + "@id": "http://www.opengis.net/def/docs/03-031" + }, + { + "@id": "http://www.opengis.net/def/docs/08-129" + }, + { + "@id": "http://www.opengis.net/def/docs/06-028" + }, + { + "@id": "http://www.opengis.net/def/docs/05-007r2" + }, + { + "@id": "http://www.opengis.net/def/docs/01-036" + }, + { + "@id": "http://www.opengis.net/def/docs/15-074r1" + }, + { + "@id": "http://www.opengis.net/def/docs/04-049r1" + }, + { + "@id": "http://www.opengis.net/def/docs/01-022r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-025r3" + }, + { + "@id": "http://www.opengis.net/def/docs/06-055r1" + }, + { + "@id": "http://www.opengis.net/def/docs/02-061r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-019" + }, + { + "@id": "http://www.opengis.net/def/docs/12-028" + }, + { + "@id": "http://www.opengis.net/def/docs/01-024r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-128" + }, + { + "@id": "http://www.opengis.net/def/docs/03-021" + }, + { + "@id": "http://www.opengis.net/def/docs/11-039r2" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Discussion Paper - deprecated " + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/04-014r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-06-09" + "@value": "2004-04-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jerome Gasperi, Frédéric Houbie, Andrew Woolf, Steven Smolders " + "@value": "Carl Reed, George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-atb" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -58443,27 +58043,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/10-157r4/10-157r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=5393" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-157r4" + "@value": "04-014r1" }, { "@language": "en", - "@value": "Earth Observation Metadata profile of Observations & Measurements" + "@value": "OGC Technical Document Baseline" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-atb" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Implementation Standard defines a profile of Observations and Measurements (ISO 19156:2010 and OGC 10-025r1) for describing Earth Observation products (EO products).\r\nThis profile is intended to provide a standard schema for encoding Earth Observation product metadata to support the description and cataloguing of products from sensors aboard EO satellites. \r\nThe metadata being defined in this document is applicable in a number of places where EO product metadata is needed.\r\n1.\tIn the EO Product Extension Package for ebRIM (OGC 10-189). This extension package defines how to catalog Earth Observation product metadata described by this document. Using this metadata model and the Catalogue Service defined in OGC 10-189, client applications can provide the functionality to discover EO Products. Providing an efficient encoding for EO Product metadata cataloguing and discovery is the prime purpose of this specification.\r\n2.\tIn the EO Application Profile of WMS (OGC 07-063r1). The GetFeatureInfo operation on the outline (footprint layer) should return metadata following the Earth Observation Metadata profile of Observation and Measurements.\r\n3.\tIn a coverage downloaded via an EO WCS AP (OGC 10-140). In WCS 2.0 (OGC 10-084), the GetCoverage and DescribeCoverage response contains the metadata element intended to store metadata information about the coverage. The Earth Observation Application profile of WCS (OGC 10-140) specifies that the metadata format preferred for Earth Observation is defined by this document.\r\n4.\tPotentially enclosed within an actual product to describe georeferencing information as for instance within the JPEG2000 format using GMLJP2. GMLJP2 defines how to store GML coverage metadata inside a JP2 file. \r\nEarth Observation data products are generally managed within logical collections that are usually structured to contain data items derived from sensors onboard a satellite or series of satellites. The key characteristics differentiating products within the collections are date of acquisition, location as well as characteristics depending on the type of sensor, For example, key characteristics for optical imagery are the possible presence of cloud, haze, smokes or other atmospheric or on ground phenomena obscuring the image. \r\nThe common metadata used to distinguish EO products types are presented in this document for generic and thematic EO products (i.e optical, radar, atmospheric, altimetry, limb-looking and synthesis and systematic products). From these metadata the encodings are derived according to standard schemas. In addition, this document describes the mechanism used to extend these schemas to specific missions and for specific purposes such as long term data preservation. \r\n" + "@value": "Spreadsheet of OGC Technical Document Baseline" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58474,35 +58074,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-157r4" + "@value": "04-014r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Earth Observation Metadata profile of Observations & Measurements" + "@value": "OGC Technical Document Baseline" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-126r4", + "@id": "http://www.opengis.net/def/docs/15-116", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-24" + "@value": "2016-04-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Taylor" + "@value": "Giuseppe Conti, Fabio Roncato" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -58512,27 +58112,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=57222" + "@id": "https://portal.ogc.org/files/?artifact_id=68040" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-126r4" + "@value": "AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper" }, { "@language": "en", - "@value": "WaterML 2.0: Part 1- Timeseries" + "@value": "15-116" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "WaterML 2.0 is a standard information model for the representation of water observations data, with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of exchange requirements, some of which are described later in this document." + "@value": "This document provides a proposal for a new O&M (Observations and Measurements) profile focused on Active and Healthy Ageing, called AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper). This document introduces the overall need for such a profile and it discusses the measures which have been identified." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58543,30 +58143,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-126r4" + "@value": "15-116" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® WaterML 2.0: Part 1- Timeseries" + "@value": "AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-021r2", + "@id": "http://www.opengis.net/def/docs/14-086r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-04-28" + "@value": "2014-11-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Roger Brackin" + "@value": "Josh Lieberman, Johannes Echterhoff, Matt de Ris, George Wilber" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -58581,17 +58181,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=57336" + "@id": "https://portal.ogc.org/files/60176" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-021r2" + "@value": "14-086r1" }, { "@language": "en", - "@value": "Testbed 10 CCI Profile Interoperability Engineering Report" + "@value": "Aircraft Access to SWIM (AAtS) Harmonization Project Summary Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -58601,7 +58201,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report was prepared as a deliverable for OGC Testbed 10, an initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Cross Community Interoperability (CCI) thread within the testbed. The work has been commissioned in order to inform geospatial information frameworks of the Defence Geospatial Information Working Group (DGIWG), National System for Geospatial Intelligence (NSG) of the US National Geospatial Intelligence Agency (NGA) and the UK Ministry of Defence (MOD).\r\nThe Engineering Report presents an analysis and assessment of interoperability between DGIWG, NSG and UK MOD profiles of Web Map Service (WMS) and Web Feature Service (WFS) standards of the OGC. The engineering report also presents findings from the implementation of the reference profiles.\r\n" + "@value": "This OGC® document summarizes the Aircraft Access to SWIM (AAtS) Harmonization activity developed by a team funded by the FAA and led by the Open Geospatial Consortium (OGC). The activity involved assembling a core team of industry participant experts to analyze and harmonize four standards suites and/or standards-based architectures relevant to air-ground information exchange:\r\n•\tThe Aircraft Access to SWIM (AAtS) concept, \r\n•\tRTCA aeronautical information services (AIS) and meteorological (MET) information data link service committee’s (SC-206) concepts and standards, \r\n•\tAir-Ground Information Exchange A830 (AGIE) standard and \r\n•\tOGC standards and architectural perspectives. \r\nElements of this effort have included:\r\n•\tCreation and public release of a Request for Information\r\n•\tAnalysis of the fits and overlaps between the four standards suites\r\n•\tEngagement with ongoing standards development efforts to reduce incompatibilities\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58612,35 +58212,126 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-021r2" + "@value": "14-086r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 10 CCI Profile Interoperability Engineering Report" + "@value": "OGC® Aircraft Access to SWIM (AAtS) Harmonization Project Summary Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-000", + "@id": "http://www.opengis.net/def/doc-type/as/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type OGC Abstract Specification" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type OGC Abstract Specification" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/99-110" + }, + { + "@id": "http://www.opengis.net/def/docs/00-115" + }, + { + "@id": "http://www.opengis.net/def/docs/08-126" + }, + { + "@id": "http://www.opengis.net/def/docs/04-084r4" + }, + { + "@id": "http://www.opengis.net/def/docs/21-053r1" + }, + { + "@id": "http://www.opengis.net/def/docs/04-107" + }, + { + "@id": "http://www.opengis.net/def/docs/99-113" + }, + { + "@id": "http://www.opengis.net/def/docs/22-010r4" + }, + { + "@id": "http://www.opengis.net/def/docs/11-111r1" + }, + { + "@id": "http://www.opengis.net/def/docs/99-108r2" + }, + { + "@id": "http://www.opengis.net/def/docs/17-087r13" + }, + { + "@id": "http://www.opengis.net/def/docs/21-060r2" + }, + { + "@id": "http://www.opengis.net/def/docs/02-112" + }, + { + "@id": "http://www.opengis.net/def/docs/06-004r4" + }, + { + "@id": "http://www.opengis.net/def/docs/18-005r8" + }, + { + "@id": "http://www.opengis.net/def/docs/10-030" + }, + { + "@id": "http://www.opengis.net/def/docs/00-116" + }, + { + "@id": "http://www.opengis.net/def/docs/07-011" + }, + { + "@id": "http://www.opengis.net/def/docs/20-082r4" + }, + { + "@id": "http://www.opengis.net/def/docs/19-014r3" + }, + { + "@id": "http://www.opengis.net/def/docs/20-040r3" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type OGC Abstract Specification" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/10-094", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-04-29" + "@value": "2010-10-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Raj SIngh" + "@value": "David Arctur" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -58650,27 +58341,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=26608" + "@id": "https://portal.ogc.org/files/?artifact_id=40840" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-000" + "@value": "10-094" }, { "@language": "en", - "@value": "Canadian Geospatial Data Infrastructure Summary Report" + "@value": "OWS-7: Summary of the OGC Web Services, Phase 7 (OWS-7) Interoperability Testbed" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report summarizes the work performed under the Canadian Geospatial Data Infrastructure Pilot. The purpose of this pilot was to test the utility of certain OGC standards, in particular the Geography Markup Language (GML) and Web Feature Service (WFS), in the implementation of a spatial data infrastructure. OGC documents 08-001 and 08-002 are more technical companions to this document." + "@value": "The OGC Web Services, Phase 7 (OWS-7) Testbed was an initiative of OGC’s Interoperability Program to collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58681,35 +58372,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-000" + "@value": "10-094" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Canadian Geospatial Data Infrastructure Summary Report" + "@value": "OWS-7: Summary of the OGC Web Services, Phase 7 (OWS-7) Interoperability Testbed" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-057", + "@id": "http://www.opengis.net/def/docs/16-083r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-07" + "@value": "2019-01-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jérôme Gasperi" + "@value": "Eric Hirschorn" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -58719,27 +58410,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-057.html" + "@id": "https://docs.ogc.org/is/16-083r3/16-083r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Authorisation, Authentication, & Billing Engineering Report" + "@value": "16-083r3" }, { "@language": "en", - "@value": "18-057" + "@value": "Coverage Implementation Schema - ReferenceableGridCoverage Extension with Corrigendum" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "In the context of a generic Earth Observation Exploitation Platform ecosystem, populated by Thematic Exploitation Platforms (TEPs) and Mission Exploitation Platforms (MEPs), which make use of cloud computing resources for Earth Observation data processing, the European Space Agency (ESA) has established two fundamental building blocks within a TEP, with different functions, the Application Deployment and Execution Service (ADES) and the Execution Management Service (EMS). Users interact with a TEP using a Web Client and the TEP contains an EMS and an ADES. The EMS includes most of the control logic, required for deploying and executing applications in different MEPs and TEPs while the ADES instead is responsible for the single application deployment and execution on a specific platform (i.e. TEP and/or MEP).\r\n\r\nThe D009 - ADES and EMS Results and Best Practices Engineering Report describes how the two services should be engineered in the Exploitation Platform context.\r\n\r\nThis Engineering Report (ER) describes the work performed by the Participants in the Exploitation Platforms Earth Observation Clouds (EOC) Thread of OGC Testbed-14 concerning the interfaces proposed for the Authentication, Authorization, Billing and Quoting topics associated to the EMS and the ADES components." + "@value": "The OGC GML Application Schema - Coverages (“GMLCOV”) version 1.0 [OGC 09-146r2], recently renamed the OGC Coverage Implementation Schema version 1.0, provides a ReferenceableGridCoverage element for representing coverages on a referenceable grid. However, GMLCOV provides no instantiable subtypes of a critical sub-element of ReferenceableGridCoverage, GMLCOV::AbstractReferenceableGrid. To make use of ReferenceableGridCoverage, an extension deriving from GMLCOV would need to be developed. GML 3.3 is not such an extension of GMLCOV, as it is built independently from GMLCOV. Use of the instantiable referenceable grid elements of GML 3.3 with ReferenceableGridCoverage violates Requirement 14 of GMLCOV 1.0 and Requirement 24 of the OGC Modular Specification[1].\r\n\r\nThis OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension provides a set of referenceable grid elements for use as sub-elements of ReferenceableGridCoverage. Three of these elements have been adapted from GML 3.3, while a fourth emerged from work on a Testbed-11 Engineering Report[2]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58750,30 +58441,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-057" + "@value": "16-083r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Authorisation, Authentication, & Billing Engineering Report" + "@value": "OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension with Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-012", + "@id": "http://www.opengis.net/def/docs/18-026r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-18" + "@value": "2019-03-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff" + "@value": "Juan José Doval, Héctor Rodríguez" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -58788,17 +58479,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-012.html" + "@id": "https://docs.ogc.org/per/18-026r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-012" + "@value": "18-026r1" }, { "@language": "en", - "@value": "UML-to-GML Application Schema Pilot (UGAS-2020) Engineering Report" + "@value": "Security Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -58808,7 +58499,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "During UGAS-2020 emerging technology requirements for NAS employment in the NSG, and with general applicability for the wider geospatial community, were investigated and solutions developed in four areas.\r\n\r\nTo enable a wide variety of analytic tradecrafts in the NSG to consistently and interoperably exchange data, the NAS defines an NSG-wide standard UML-based application schema in accordance with the ISO 19109 General Feature Model. In light of continuing technology evolution in the commercial marketplace it is desirable to be able to employ (NAS-conformant) JSON-based data exchanges alongside existing (NAS-conformant) XML-based data exchanges. A prototype design and implementation of UML Application Schema to JSON Schema rules (see the OWS-9 SSI UGAS Conversion Engineering Report) was reviewed and revised based on the final draft IETF JSON Schema standard “draft 2019-09.” The revised implementation was evaluated using NAS Baseline X-3. This work is reported in section UML to JSON Schema Encoding Rule.\r\n\r\nTo maximize cross-community data interoperability the NAS employs conceptual data schemas developed by communities external to the NSG, for example as defined by the ISO 19100-series standards. At the present time there are no defined JSON-based encodings for those conceptual schemas. A JSON-based core profile was developed for key external community conceptual schemas, particularly components of those ISO 19100-series standards used to enable data discovery, access, control, and use in data exchange in general, including in the NSG. This work is reported in section Features Core Profile of Key Community Conceptual Schemas.\r\n\r\nThe Features Core Profile and its JSON encoding have been specified with a broader scope than the NAS. It builds on the widely used GeoJSON standard and extends it with minimal extensions to support additional concepts that are important for the wider geospatial community and the OGC API standards, including support for solids, coordinate reference systems, and time intervals. These extensions have been kept minimal to keep implementation efforts as low as possible. If there is interest in the OGC membership, the JSON encoding of the Core Profile could be a starting point for a JSON encoding standard for features in the OGC. A new Standards Working Group for a standard OGC Features and Geometries JSON has been proposed.\r\n\r\nLinked data is increasingly important in enabling “connect the dots” correlation and alignment among diverse, distributed data sources and data repositories. Validation of both data content and link-based data relationships is critical to ensuring that the resulting virtual data assemblage has logical integrity and thus constitutes meaningful information. SHACL, a language for describing and validating RDF graphs, appears to offer significant as yet unrealized potential for enabling robust data validation in a linked-data environment. The results of evaluating that potential – with emphasis on deriving SHACL from a UML-based application schema - are reported in section Using SHACL for Validation of Linked Data.\r\n\r\nThe OpenAPI initiative is gaining traction in the commercial marketplace as a next-generation approach to defining machine-readable specifications for RESTful APIs in web-based environments. The OGC is currently shifting towards interface specifications based on the OpenAPI 3.1 specification. That specification defines both the interface (interactions between the client and service) and the structure of data payloads (content) offered by that service. It is desirable to be able to efficiently model the service interface using UML and then automatically derive the physical expression of that interface (for example, as a JSON file) using Model Driven Engineering (MDE) techniques alongside the derivation of JSON Schema defining data content. A preliminary analysis and design based on the OGC API Features standard, parts 1 and 2, for sections other than for content schemas, is reported in section Generating OpenAPI definitions from an application schema in UML.\r\n\r\nAll ShapeChange enhancements developed within the UGAS-2020 Pilot have been publicly released as a component of ShapeChange v2.10.0. https://shapechange.net has been updated to document the enhancements." + "@value": "This Security Engineering Report (ER) covers several OGC Testbed-14 topics:\r\n\r\nBest practices for the integration of OAuth2.0/OpenID Connect services\r\n\r\nMediation services for different security environments\r\n\r\nFederated identity management\r\n\r\nSecuritization of workflows\r\n\r\nThe first two topics are the main focus of this ER. During this Testbed, a server that provides OAuth2.0 and OpenID Connect capabilities was extended with a mediation service that allows for a centralized security authority with users/clients that implement different security standards.\r\n\r\nThe remaining two topics will expand on the close relationship between Security, Workflows and Federated Clouds and the respective implementation challenges. On these specific topics, this ER also outlines and provides a proof-of-concept for a simplistic architecture approach that explores one of several Federated Clouds architectures." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58819,35 +58510,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-012" + "@value": "18-026r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "UML-to-GML Application Schema Pilot (UGAS-2020) Engineering Report" + "@value": "OGC Testbed-14: Security Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-107", + "@id": "http://www.opengis.net/def/docs/20-010", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-06-17" + "@value": "2021-09-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Rob Atkinson, James Groffen" + "@value": "Thomas H. Kolbe, Tatjana Kutzner, Carl Stephen Smyth, Claus Nagel, Carsten Roensdorf, Charles Heazel" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -58857,27 +58548,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/11-107" + "@id": "https://docs.ogc.org/is/20-010/20-010.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-8 Domain Modelling Cookbook" + "@value": "OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard" }, { "@language": "en", - "@value": "11-107" + "@value": "20-010" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGCTM document describes best practices for building and maintaining inter-related\r\ndomain models, which have dependencies upon multiple systems. It describes how to\r\nbuild interoperable, maintainable domain models, the challenges and pitfalls faced in\r\nbuilding these models, the techniques and patterns that should be applied, and specific\r\ntools that can be used. The theory of domain modelling is addressed, followed by\r\npractical step-by-step instructions on how to use of the tools. Examples are provided from\r\nAeronautical Information Exchange Model (AIXM) and Farm Markup Language\r\n(FarmML) as they were refined in the OGC’s OWS-8 testbed." + "@value": "This Standard defines the open CityGML Conceptual Model for the storage and exchange of virtual 3D city models. The CityGML Conceptual Model is defined by a Unified Modeling Language (UML) object model. This UML model builds on the ISO Technical Committee 211 (ISO/TC 211) conceptual model standards for spatial and temporal data. Building on the ISO foundation assures that the man-made features described in the city models share the same spatiotemporal universe as the surrounding countryside within which they reside.\r\n\r\nA key goal for the development of the CityGML Conceptual Model is to provide a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields.\r\n\r\nThe class models described in this standard are also available at https://github.com/opengeospatial/CityGML3-Workspace/tree/1.0/UML/CityGML" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58888,35 +58579,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-107" + "@value": "20-010" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC  OWS-8 Domain Modelling Cookbook" + "@value": "OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-102r3a", + "@id": "http://www.opengis.net/def/docs/06-135r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-01-29" + "@value": "2007-01-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -58926,27 +58617,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=66915" + "@id": "https://portal.ogc.org/files/?artifact_id=17566" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "DGIWG - Web Map Service 1.3 Profile - Revision" + "@value": "06-135r1" }, { "@language": "en", - "@value": "09-102r3a" + "@value": "Specification best practices" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines specific DGIWG requirements,\r\nrecommendations and guidelines for implementations of the\r\nISO and OGC Web Map Service standards; ISO 19128:2005\r\nWeb Map Server Interface and the OpenGIS Web Map Server\r\nImplementation Specification 1.3.0." + "@value": "This document describes a variety of Best Practices and Specification development guidance that the Members have discussed and approved over the years. These Best Practices have not been captured in other formal OGC documents other than meeting notes." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -58957,35 +58648,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-102r3a" + "@value": "06-135r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "DGIWG - Web Map Service 1.3 Profile - Revision" + "@value": "Specification best practices" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-089r1", + "@id": "http://www.opengis.net/def/docs/16-040r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-08-16" + "@value": "2017-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Aleksandar Balaban" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -58995,27 +58686,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/17-089r1/17-089r1.html" + "@id": "https://docs.ogc.org/per/16-040r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "WCS Core 2.1" + "@value": "Testbed-12 Aviation Security Engineering Report" }, { "@language": "en", - "@value": "17-089r1" + "@value": "16-040r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Web Coverage Service (WCS) supports electronic retrieval of geospatial data as coverages. Coverages are digital geospatial information representing space/time-varying phenomena, specifically spatio-temporal regular and irregular grids, point clouds, and general meshes.\r\nThis document specifies the WCS core. Every implementation of a WCS shall adhere to this standard. This standard defines core requirements. Extensions to the core define extensions to meet additional requirements, such as the response encoding. Additional extensions are required in order to completely specify a WCS for implementation.\r\nThis WCS 2.1 standard extends WCS 2.0 in a backwards compatible manner by accommodating coverages as per the OGC Coverage Implementation Schema (CIS) 1.1 in addition to CIS 1.0 coverages as addressed by WCS 2.0.\r\n" + "@value": "The information security is the state of being protected against the unauthorized use of information and services, or the measures taken to achieve that. This report has ben created as part of OGC Testbed 12 aviation thread and on behalf of sponsors from FAA. It gives the readers an overview into the topic of cyber security in the aviation domain, especially in conjunction with OGC compatible web services, which are today de facto standard for aeronautical traffic System Wide Information Management." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59026,35 +58717,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-089r1" + "@value": "16-040r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Coverage Service (WCS) 2.1 Interface Standard - Core" + "@value": "Testbed-12 Aviation Security Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-163", + "@id": "http://www.opengis.net/def/docs/21-069r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2023-08-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thibault Dacla; Eriza Hafid Fazli; Charles Chen; Stuart Wilson" + "@value": "Chris Little, Jon Blower, Maik Riechert " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -59064,27 +58755,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51812" + "@id": "https://docs.ogc.org/cs/21-069r2/21-069r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-163" + "@value": "OGC CoverageJSON Community Standard" }, { "@language": "en", - "@value": "OWS-9 Data Transmission Management" + "@value": "21-069r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OWS-9 Engineering Report documents investigations, findings, lessons learned and\r\nproposed future work for the Data Transmission Management unit, invented and\r\nprototyped in OWS-9.\r\nThe purpose of the Data Transmission Management unit is to optimize, customize and\r\nmake reliable the information exchange between the aircraft and the different web\r\nservices on the ground." + "@value": "Based on JavaScript Object Notation (JSON), CoverageJSON is a format for publishing spatiotemporal data to the Web. The primary design goals are simplicity, machine and human readability and efficiency. While other use cases are possible, the primary CoverageJSON use case is enabling the development of interactive visual websites that display and manipulate environmental data within a web browser.\r\n\r\nImplementation experience has shown that CoverageJSON is an effective, efficient format, friendly to web and application developers, and therefore consistent with the current OGC API developments. CoverageJSON supports the efficient transfer from big data stores of useful quantities of data to lightweight clients, such as browsers and mobile applications. This enables straightfoward local manipulation of the data, for example, by science researchers. Web developers often use and are familiar with JSON formats.\r\n\r\nCoverageJSON 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.\r\n\r\nRelatively 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.\r\n\r\nThe simplest and most common use case is to embed all the data values of all variables in a Coverage object within the CoverageJSON document, so that it is “self-contained”. Such a standalone document supports the use of very simple clients.\r\n\r\nThe next simplest use case is to put data values for each variable (parameter) in separate array objects in separate CoverageJSON documents which are linked from the Coverage object. This is useful for a multi-variable dataset, such as one with temperature, humidity, wind speed, etc., to be recorded in separate files. This allows the client to load only the variables of interest.\r\n\r\nA sophisticated use case is to use tiling objects, where the data values are partitioned spatially and temporally, so that a single variable’s data values would be split among several documents. A simple example of this use case is encoding each time step of a dataset into a separate file, but the tiles could also be divided spatially in a manner similar to a tiled map server." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59095,104 +58786,119 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-163" + "@value": "21-069r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-9 Data Transmission Management" + "@value": "OGC CoverageJSON Community Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-047r1", + "@id": "_:nb09404f615a5424abfd7f2fb95a2790bb1", "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" + "http://www.w3.org/ns/prov#Activity" ], - "http://purl.org/dc/terms/created": [ + "http://www.w3.org/ns/prov#endedAtTime": [ { - "@type": "xsd:date", - "@value": "2024-01-29" + "@type": "http://www.w3.org/2001/XMLSchema#dateTime", + "@value": "2024-08-10T10:33:53.521511" } ], - "http://purl.org/dc/terms/creator": [ + "http://www.w3.org/ns/prov#startedAtTime": [ { - "@value": "Nicholas J. Car" + "@type": "http://www.w3.org/2001/XMLSchema#dateTime", + "@value": "2024-08-10T10:33:52.467869" } ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "http://www.w3.org/ns/prov#used": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "_:nb09404f615a5424abfd7f2fb95a2790bb2" } ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "http://www.w3.org/ns/prov#wasAssociatedWith": [ { - "@id": "http://www.opengis.net/def/status/valid" + "@id": "_:nb09404f615a5424abfd7f2fb95a2790bb3" } ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "http://www.w3.org/ns/prov#wasInformedBy": [ { - "@id": "https://docs.ogc.org/is/22-047r1/22-047r1.html" + "@id": "_:nb09404f615a5424abfd7f2fb95a2790bb4" } + ] + }, + { + "@id": "_:nb09404f615a5424abfd7f2fb95a2790bb2", + "@type": [ + "http://www.w3.org/ns/prov#Entity" ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ - { - "@language": "en", - "@value": "22-047r1" - }, + "http://purl.org/dc/terms/format": [ { - "@language": "en", - "@value": "OGC GeoSPARQL - A Geographic Query Language for RDF Data" + "@value": "application/json" } ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "http://purl.org/dc/terms/hasVersion": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@value": "git:c89beb527ab5c15420e81e8661f606c28f76194f" } ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@value": "GeoSPARQL contains a small spatial domain OWL ontology that allow literal representations of geometries to be associated with spatial features and for features to be associated with other features using spatial relations.\r\n\r\nGeoSPARQL also contains SPARQL extension function definitions that can be used to calculate relations between spatial objects.\r\n\r\nSeveral other supporting assets are also contained within GeoSPARQL such as vocabularies of Simple Feature types and data validators.\r\n\r\nThe namespace for the GeoSPARQL ontology is http://www.opengis.net/ont/geosparql#\r\n\r\nThe suggested prefix for this namespace is geo\r\n\r\nThe namespace for the GeoSPARQL functions is http://www.opengis.net/def/function/geosparql/\r\n\r\nThe suggested prefix for this namespace is geof\r\n\r\n\r\n" + "@id": "file:///home/runner/work/NamingAuthority/NamingAuthority/definitions/docs/docs.json" + } + ] + }, + { + "@id": "_:nb09404f615a5424abfd7f2fb95a2790bb4", + "http://purl.org/dc/terms/identifier": [ + { + "@value": "5f5b05c3-a60e-424a-98dc-119698b7c563" } + ] + }, + { + "@id": "_:nb09404f615a5424abfd7f2fb95a2790bb3", + "@type": [ + "http://www.w3.org/ns/prov#Agent", + "https://schema.org/SoftwareApplication" ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "http://purl.org/dc/terms/hasVersion": [ { - "@id": "http://www.opengis.net/def/docs" + "@value": "0.3.49" } ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "http://www.w3.org/2000/01/rdf-schema#label": [ { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-047r1" + "@value": "OGC-NA tools" } ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@language": "en", - "@value": "OGC GeoSPARQL - A Geographic Query Language for RDF Data" + "@id": "https://github.com/opengeospatial/ogc-na-tools" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-036r2", + "@id": "http://www.opengis.net/def/docs/06-080", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-24" + "@value": "2006-07-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jan Herrmann, Andreas Matheus" + "@value": "Jerome Gasperi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -59202,27 +58908,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34976" + "@id": "https://portal.ogc.org/files/?artifact_id=15546" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-6 GeoXACML Engineering Report" + "@value": "GML Application Schema for EO Products" }, { "@language": "en", - "@value": "09-036r2" + "@value": "06-080" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The aim of this OGC Engineering Report is to show how to provide access control for OGC Web Services (OWS). In the first part of this document we will briefly introduce the relevant details of XACML 2.0, OGC GeoXACML 1.0 and some related profiles. " + "@value": "This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGCTM Catalogue Services Specification v2.0.0 (with Corrigendum) [OGC 04-021r3]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59233,35 +58939,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-036r2" + "@value": "06-080" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 GeoXACML Engineering Report" + "@value": "GML Application Schema for EO Products" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-126r8", + "@id": "http://www.opengis.net/def/docs/12-132r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-08-30" + "@value": "2015-02-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Martin Lechner" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -59271,27 +58977,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/16-126r8" + "@id": "https://portal.ogc.org/files/?artifact_id=62168" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Release Notes for GeoPackage v1.2" + "@value": "12-132r4" }, { "@language": "en", - "@value": "16-126r8" + "@value": "Augmented Reality Markup Language 2.0 (ARML 2.0) " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the set of revision notes for the existing GeoPackage version 1.2 (OGC 12-\r\n128r13) and does not modify that standard.\r\nThis document was approved by the OGC membership on approval date. As a result of the OGC\r\nStandards Working Group (SWG) process, there were a number of edits and enhancements made to\r\nthis standard. This document provides the details of those edits, deficiency corrections, and\r\nenhancements. It also documents those items that have been deprecated. Finally, this document\r\nprovides implementations details related to issues of backwards compatibility." + "@value": "This OGC® Standard defines the Augmented Reality Markup Language 2.0 (ARML 2.0). ARML 2.0 allows users to describe virtual objects in an Augmented Reality (AR) scene with their appearances and their anchors (a broader concept of a location) related to the real world. Additionally, ARML 2.0 defines ECMAScript bindings to dynamically modify the AR scene based on user behavior and user input." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59302,69 +59008,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-126r8" + "@value": "12-132r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Release Notes for GeoPackage v1.2" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/ipr/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type Interoperability Program Report" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Documents of type Interoperability Program Report" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/02-019r1" - }, - { - "@id": "http://www.opengis.net/def/docs/02-028" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Documents of type Interoperability Program Report" + "@value": "OGC Augmented Reality Markup Language 2.0 (ARML 2.0)" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-195", + "@id": "http://www.opengis.net/def/docs/11-089r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-03-28" + "@value": "2011-11-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "OGC Aviation Domain Working Group" + "@value": "Daniel Tagesson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -59374,27 +59046,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41667" + "@id": "https://portal.ogc.org/files/?artifact_id=46228" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-195" + "@value": "OWS-8 Engineering Report - Guidelines for International Civil Aviation Organization (ICAO) portrayal using SLD/SE" }, { "@language": "en", - "@value": "Requirements for Aviation Metadata" + "@value": "11-089r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Discussion Paper details the user requirements for metadata in the aviation domain. The requirements are at a high-level." + "@value": "This OGC® document gives guidelines to portrayal of AIXM according to ICAO aviation symbology using SLD/SE. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59405,35 +59077,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-195" + "@value": "11-089r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Requirements for Aviation Metadata" + "@value": "OWS-8 Engineering Report - Guidelines for International Civil Aviation Organization (ICAO) portrayal using SLD/SE" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-044", + "@id": "http://www.opengis.net/def/docs/23-024", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-02-02" + "@value": "2024-07-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lew Leinenweber" + "@value": "Alan Leidner, Andrew Hughes, Carsten Roensdorf, Neil Brammall, Liesbeth Rombouts, Joshua Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -59443,27 +59115,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=61108" + "@id": "https://docs.ogc.org/is/23-024/23-024.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-044" + "@value": "23-024" }, { "@language": "en", - "@value": "Testbed 10 Summary Engineering Report" + "@value": "OGC Model for Underground Data Definition and Integration (MUDDI) Part 1: Conceptual Model" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Testbed 10 was an initiative of OGC’s Interoperability Program to collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. The majority of work for Testbed 10 was conducted between October 2013 and April 2014." + "@value": "MUDDI stands for “Model for Underground Data Definition and Integration” and is an approach to make sub-surface data Findable, Accessible, Interoperable, and Re-Usable.\r\n\r\nThis document defines a Conceptual Model of classes that allows the integration of datasets from different types of information about the underground space, using different information models. These information models include models about elements such as utility infrastructure, transport infrastructure, soils, ground water, or environmental parameters. The Conceptual Model is a superset of classes representing Real-World Objects that can be found in the Underground." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59474,35 +59146,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-044" + "@value": "23-024" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 10 Summary Engineering Report" + "@value": "OGC Model for Underground Data Definition and Integration (MUDDI) Part 1: Conceptual Model" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-128r14", + "@id": "http://www.opengis.net/def/docs/19-042r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-08-25" + "@value": "2019-11-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Lewis John McGibbney" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -59512,27 +59184,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=74225" + "@id": "https://docs.ogc.org/dp/19-042r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-128r14" + "@value": "19-042r1" }, { "@language": "en", - "@value": "GeoPackage Encoding Standard" + "@value": "Discussion Paper - JSON Encodings for EO Coverages" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." + "@value": "This discussion paper documents and concludes one year (2018-2019) of work undertaken by a National Aeronautics and Space Administration (NASA) Earth Science Data System Working Group focused on exploring JSON Encodings in Earth Observation Coverages. The primary function of this paper is to ensure that the collective Working Group knowledge obtained from the year effort is not lost and consequently that it can be considered, debated and hopefully utilized in other forums outside of NASA with the aim of driving progress in this field. The covering statement (below) provides 10 questions which are meant to facilitate such discussion.\r\n\r\nThis discussion paper will be of particular interest to the following parties:\r\n\r\nWeb application developers tasked with designing and developing applications which consume Earth Observation spatial data encoded as JSON.\r\n\r\nParties (including standards bodies) interested in serving and consuming Spatial data on the Web e.g. World Wide Web Consortium (W3C), Open Geospatial Consortium (OGC) or developers of other data standards, etc." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59543,35 +59215,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-128r14" + "@value": "19-042r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GeoPackage Encoding Standard" + "@value": "Discussion Paper - JSON Encodings for EO Coverages" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-113", + "@id": "http://www.opengis.net/def/docs/17-014r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-03-31" + "@value": "2017-09-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman" + "@value": "Carl Reed, Tamrat Belayneh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -59581,27 +59253,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=901" + "@id": "https://docs.ogc.org/cs/17-014r5/17-014r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "99-113" + "@value": "17-014r5" }, { "@language": "en", - "@value": "Topic 13 - Catalog Services" + "@value": "Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Covers the Geospatial Information Access Services" + "@value": "A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files.\r\n\r\n \r\n\r\nThe delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3d datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59612,35 +59284,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-113" + "@value": "17-014r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 13 - Catalog Services" + "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-005", + "@id": "http://www.opengis.net/def/docs/08-103r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-05-03" + "@value": "2009-02-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jerome Sonnet" + "@value": "Richard Martell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/ts" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -59650,27 +59322,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8618" + "@id": "https://portal.ogc.org/files/?artifact_id=31139" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Map Context Implementation Specification" + "@value": "08-103r2" }, { "@language": "en", - "@value": "05-005" + "@value": "CSW-ebRIM Registry Service - Part 3: Abstract Test Suite" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/ts" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a companion specification to the OGC Web Map Service Interface Implementation Specification version 1.1.1 [4], hereinafter WMS 1.1.1. \r\nWMS 1.1.1 specifies how individual map servers describe and provide their map content. The present Context specification states how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent format for storage in a repository or for transmission between clients. This description is known as a Web Map Context Document, or simply a Context. Presently, context documents are primarily designed for WMS bindings. However, extensibility is envisioned for binding to other services.\r\nA Context document includes information about the server(s) providing layer(s) in the overall map, the bounding box and map projection shared by all the maps, sufficient operational metadata for Client software to reproduce the map, and ancillary metadata used to annotate or describe the maps and their provenance for the benefit of human viewers.\r\nA Context document is structured using eXtensible Markup Language (XML). Annex A of this specification contains the XML Schema against which Context XML can be validated.\r\n " + "@value": "This document is an abstract test suite (ATS): a compendium of abstract test cases pertaining to implementations of the CSW-ebRIM 1.0 catalogue profile. It provides a basis for developing an executable test suite (ETS) to verify that the implementation under test (IUT) conforms to all relevant functional specifications. While passing all of the conformance tests defined in this ATS provides some assurance of overall functional correctness, it cannot guarantee that an implementation is faultless." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59681,35 +59353,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-005" + "@value": "08-103r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Map Context Implementation Specification" + "@value": "CSW-ebRIM Registry Service - Part 3: Abstract Test Suite" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-061", + "@id": "http://www.opengis.net/def/docs/05-101", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-05-19" + "@value": "2006-04-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Geoffrey Ehler" + "@value": "David Burggraf" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -59719,27 +59391,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1273" + "@id": "https://portal.ogc.org/files/?artifact_id=13396" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-061" + "@value": "OWS 3 GML Investigations - Performance Experiment by Galdos Systems" }, { "@language": "en", - "@value": "Critical Infrastructure Collaborative Environment Architecture: Enterprise Viewpoint" + "@value": "05-101" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*RETIRED* specifies the Enterprise viewpoint for the Critical Infrastructure Collaborative Environment (CICE)." + "@value": "In this experiment, the retrieval time of GML features from a Web Feature Service (WFS) to a WFS client will be studied by varying certain control parameters including methods of encoding and compression. Four different control parameters including encoding format, data set size, bandwidth, and feature type will be varied to test the relative performance in each case." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59750,30 +59422,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-061" + "@value": "05-101" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Critical Infrastructure Collaborative Environment Architecture: Enterprise Viewpoint" + "@value": "OWS 3 GML Investigations - Performance Experiment by Galdos Systems" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-018", + "@id": "http://www.opengis.net/def/docs/13-101", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-03-30" + "@value": "2013-11-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Rüdiger Gartmann, Bastian Schäffer" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -59788,17 +59460,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=42735" + "@id": "https://portal.ogc.org/files/?artifact_id=55232" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-018" + "@value": "13-101" }, { "@language": "en", - "@value": "License-Based Access Control" + "@value": "Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 GML 3.2.1 Encoding Extension" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -59808,7 +59480,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion Paper proposes model for license-based access control to SOAP services, based on OASIS SAML 2.0. This approach is a potential solution for license-based access control, which requires the possession of a valid license for getting access to a service. Use of digital licenses allow users to act on or with web services to which they are associated\r\n\r\nThis document re-uses content produced by the OGC GeoRM Common 1.0 Standards Working Group and combined that with the document OGC 10-125, which was posted to an internal OGC document archive (Pending Documents) but is not publicly available.\r\nThis document does not claim compliance to the GeoDRM reference model (ISO 19153), although the authors are not yet aware of any conflicts to it.\r\n" + "@value": "This standard defines the version 3.0 of a valid GML 3.2.1 geometry encoding as defined in Geography Markup Language (GML) simple features profile (with Corrigendum) to be used with the GeoXACML 3.0 Core standard.\r\nThe use of this encoding extension to GeoXACML 3.0 Core enables the direct use of GML 3.2.1 encoded geometries into a GeoXACML 3.0 Policy, an Authorization Decision Request or in an Authorization Decision’s Obligation element. It thereby improves the performance of deriving access control decisions, where geometries are involved as existing GML 3.2.1 geometry encodings must not be transformed to Well Known Text (WKT) as supported by GeoXACML 3.0 Core. Furthermore, the use of this encoding extension simplifies the implementation of a Policy Enforcement Point as it must not provide the transformation functions from GML to WKT and vice versa.\r\nThis encoding extension has its normative base in Geography Markup Language (GML) simple features profile (with Corrigendum).\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59819,35 +59491,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-018" + "@value": "13-101" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "License-Based Access Control" + "@value": "OGC Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 GML 3.2.1 Encoding Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-000r2", + "@id": "http://www.opengis.net/def/docs/04-107", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-08-10" + "@value": "2004-10-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mike Botts, Alexandre Robin, Eric Hirschorn" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -59857,27 +59529,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/12-000r2/12-000r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=7467" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "SensorML: Model and XML Encoding Standard" + "@value": "04-107" }, { "@language": "en", - "@value": "12-000r2" + "@value": "Topic 07 - Earth Imagery" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The primary focus of the Sensor Model Language (SensorML) is to provide a robust and semantically-tied means of defining processes and processing components associated with the measurement and post-measurement transformation of observations. This includes sensors and actuators as well as computational processes applied pre- and post-measurement.\r\n\r\nThe main objective is to enable interoperability, first at the syntactic level and later at the semantic level (by using ontologies and semantic mediation), so that sensors and processes can be better understood by machines, utilized automatically in complex workflows, and easily shared between intelligent sensor web nodes.\r\n\r\nThis standard is one of several implementation standards produced under OGC’s Sensor Web Enablement (SWE) activity. This standard is a revision of content that was previously integrated in the SensorML version 1.0 standard (OGC 07-000)." + "@value": "Replaced previous material in Topic 7 with ISO 19101-2, Reference Model - Geographic Information - Imagery. Version 5 of OGC Topic 7 is identical with ISO 19101-2 Working Draft #3. Topic 7 will be updated jointly with the progress of ISO 19191-2. Appendix A of Topic 7, version 4 contained a White Paper on Earth Image Geometry Models. That white paper is now separate OGC Recommendation document. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59888,35 +59560,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-000r2" + "@value": "04-107" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC SensorML: Model and XML Encoding Standard" + "@value": "Topic 7 - Earth Imagery" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-022r1", + "@id": "http://www.opengis.net/def/docs/08-094r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-12-26" + "@value": "2011-01-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Alexandre Robin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -59926,27 +59598,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=22466" + "@id": "https://portal.ogc.org/files/?artifact_id=41157" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Observations and Measurements - Part 1 - Observation schema" + "@value": "08-094r1" }, { "@language": "en", - "@value": "07-022r1" + "@value": "SWE Common Data Model Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Observations and Measurements Encoding Standard (O&M) defines an abstract model and an XML schema [www.w3.org/XML/Schema] encoding for observations and it provides support for common sampling strategies. O&M also provides a general framework for systems that deal in technical measurements in science and engineering. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. " + "@value": "This standard defines low level data models for exchanging sensor related data between nodes of the OGC® Sensor Web Enablement (SWE) framework. These models allow applications and/or servers to structure, encode and transmit sensor datasets in a self describing and semantically enabled way." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -59957,30 +59629,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-022r1" + "@value": "08-094r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Observations and Measurements - Part 1 - Observation schema" + "@value": "OGC® SWE Common Data Model Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-035", + "@id": "http://www.opengis.net/def/docs/12-139", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-07" + "@value": "2013-02-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stephane Fellah" + "@value": "Jan Herrmann, Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -59995,17 +59667,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-035.html" + "@id": "https://portal.ogc.org/files/?artifact_id=51833" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-035" + "@value": "12-139" }, { "@language": "en", - "@value": "Semantically Enabled Aviation Data Models Engineering Report" + "@value": "OWS-9: SSI Security Rules Service Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -60015,7 +59687,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) summarizes the OGC Testbed-14 findings and recommendations to “semantically enable” existing data and metadata models used in the aviation industry. Examples of such data and metadata models include Aeronautical Information Exchange Model (AIXM) [1], Weather Information Exchange Model (WXXM) [2], Flight Information Exchange Model (FIXM) [3],Web Service Description Document (WSDD), Service Description Conceptual Model (SDCM) [4]). These models use Linked Data standards to represent this information and aim to improve the search and discovery of services and information in the aviation domain using the System Wide Information Management (SWIM) environment. This report provides a review of the existing data models and explore different approaches to provide a semantic representation of the current metadata and data models used in the aviation domain. The ER also discusses the role and importance of the controlled vocabularies." + "@value": "In this engineering report we describe how to administrate XACML v2.0, XACML v3.0 and GeoXACML v1.0.1 access control policies through a “Security Rules Service”. Following the XACML and ISO terminology this service plays the role of a Policy Administration Point (PAP) and is therefore called XACML Policy Administration Point (XACML PAP) or XACML Policy Administration Web Service (XACML PAWS). \r\nAfter introducing OWS-9’s Common Rule Encoding and motivating all components required to administrate (Geo)XACML policies, we describe the interface of a powerful XACML PAP on a conceptual level. This interface definition could serve as a baseline for a future OASIS or OGC XACML Policy Administration Web Service (e.g. OGC XACML PAWS) specification.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60026,30 +59698,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-035" + "@value": "12-139" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Semantically Enabled Aviation Data Models Engineering Report" + "@value": "OWS-9: SSI Security Rules Service Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-050r3", + "@id": "http://www.opengis.net/def/docs/18-097", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-01-25" + "@value": "2019-02-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Harrison" + "@value": "David Blodgett, Byron Cochrane, Rob Atkinson, Sylvain Grellet, Abdelfettah Feliachi, Alistair Ritchi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -60064,17 +59736,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=65421" + "@id": "https://docs.ogc.org/per/18-097.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-11 Test and Demonstration Results for NIEM using IC Data Encoding Specifications Engineering Report" + "@value": "18-097" }, { "@language": "en", - "@value": "15-050r3" + "@value": "Environmental Linked Features Interoperability Experiment Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -60084,7 +59756,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community\r\n(IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0\r\narchitecture through the development, implementations, test, and robust demonstration\r\nmaking use of IC specifications, Geography Markup Language (GML), and NIEM in a\r\nsimulated “real-world” scenario. The demonstration scenario begins with NIEMconformant\r\nInformation Exchange Packages (IEPs) containing operational data and IC\r\nsecurity tags from the Information Security Marking (ISM) and Need-To-Know (NTK)\r\naccess control metadata, and the Trusted Data Format (TDF) for binding assertion\r\nmetadata with data resource(s). Those instance documents are deployed using Open\r\nGeospatial Consortium (OGC) standards enabled Web Services for use by client\r\napplications. Access control is based on attributes of the end-user and the instance data.\r\nRecommendations to update these information exchanges were provided to reflect NIEM\r\n3.0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment tested\r\nthis data encoding in OGC Web Feature Services (WFS) and Policy Enforcement Points\r\n(PEP) accessed by multiple client applications. Results from this task provided a\r\npreliminary architecture that was tested and demonstrated in Testbed 11, and summarized\r\nin other OGC Testbed 11 Engineering Reports. The demonstrations also highlighted how\r\nNIEM and IC data encodings together may support more agile and customer-centric\r\nframeworks driven by collaborative partnerships. This transformation is vital to\r\nconfronting the security challenges of the future." + "@value": "Systems that maintain and disseminate information representing and/or related to spatial features often lack mechanisms to describe or discover how features relate to each other, to other kinds of features, and to a wide variety of related information that may be relevant. The Environmental Linked Features Interoperability Experiment (ELFIE) explored Open Geospatial Consortium (OGC) and World Wide Web Consortium (W3C) standards with the goal of establishing a best practice for exposing cross-domain links between environmental domain and sampling features. The Interoperability Experiment (IE) focused on encoding relationships between cross-domain features and linking available observations data to sampled domain features. An approach that leverages the OGC service baseline, W3C data on the web best practices, and JavaScript Object Notation for Linked Data (JSON-LD) contexts was developed and evaluated. Outcomes of the experiment demonstrate that broadly accepted web technologies for linked data can be applied using OGC services and domain data models to fill important gaps in existing environmental data systems' capabilities. While solutions were found to be capable and promising, OGC services and domain model implementations have limited utility for use in linked data applications in their current state and the universe of persistent URIs that form the foundation of a linked data infrastructure is still small. In addition to improvement of the standards baseline and publication of linked data URIs, establishing conventions for URI dereferencing behavior and default content given multiple options for a resource remain for future work." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60095,35 +59767,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-050r3" + "@value": "18-097" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-11 Test and Demonstration Results for NIEM using IC Data Encoding Specifications Engineering Report" + "@value": "OGC Environmental Linked Features Interoperability Experiment Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-003r3", + "@id": "http://www.opengis.net/def/docs/14-079r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-19" + "@value": "2015-02-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -60133,27 +59805,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/16-003r3" + "@id": "https://portal.ogc.org/files/?artifact_id=59983" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values" + "@value": "USGS OGC® Interoperability Assessment Report" }, { "@language": "en", - "@value": "16-003r3" + "@value": "14-079r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids key words." + "@value": "The USGS Interoperability assessment was conducted under the OGC Interoperability\r\nProgram with the goal to better understand how USGS customers make use of OGC\r\ncompliant Web services operated by USGS. For this assessment, USGS customers have\r\nbeen invited to share their experiences and to describe their use cases and experiences\r\nmade with USGS data services and products. From those descriptions, recommendations\r\nhave been derived that help USGS to better understand their user community and\r\noptimize their service offerings." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60164,35 +59836,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-003r3" + "@value": "14-079r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values" + "@value": "USGS OGC® Interoperability Assessment Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-014r3", + "@id": "http://www.opengis.net/def/docs/12-103r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-06-10" + "@value": "2013-02-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lorenzo Bigagli, Doug Nebert, Uwe Voges, Panagiotis Vretanos, Bruce Westcott" + "@value": "Gobe Hobona, Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/ts" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -60202,27 +59874,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/14-014r3/14-014r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=51840" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-014r3" + "@value": "OWS-9 CCI Semantic Mediation Engineering Report" }, { "@language": "en", - "@value": "Catalogue Services Specification - HTTP protocol binding - Abstract Test Suite" + "@value": "12-103r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/ts" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "See OGC 12-176r7 -- OGC® Catalogue Services Specification - HTTP Protocol Binding." + "@value": "The OWS-9 Cross Community Interoperability (CCI) thread built on progress made in the recent OWS-8 initiative by improving interoperability between communities sharing geospatial data through advances in semantic mediation approaches for data discovery, access and use of heterogeneous data models and heterogeneous metadata models. This OGC engineering report aims to present findings from CCI thread activities towards advancement of semantic mediation involving heterogeneous data models, gazetteers and aviation data available through web services conformant to OGC standards.\r\nThis Engineering Report was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Cross Community Interoperability thread within OWS-9.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60233,35 +59905,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-014r3" + "@value": "12-103r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Catalogue Services Specification - HTTP protocol binding - Abstract Test Suite" + "@value": "OWS-9 CCI Semantic Mediation Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-019", + "@id": "http://www.opengis.net/def/docs/07-110r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-11" + "@value": "2008-03-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Maso" + "@value": "Richard Martell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -60271,27 +59943,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-019.html" + "@id": "https://portal.ogc.org/files/?artifact_id=27092" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-13: MapML Engineering Report" + "@value": "07-110r2" }, { "@language": "en", - "@value": "17-019" + "@value": "CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report discusses the approach of Map Markup Language (MapML) and Map for HyperText Markup Language (Map4HTML) described in: https://github.com/Maps4HTML and supported by the community in https://www.w3.org/community/maps4html/. The objective of MapML is to define a hypermedia type for geospatial maps on the web that can be embedded in HyperText Markup Language (HTML) pages. MapML is needed because while Web browsers implement HTML and Scalable Vector Graphics (SVG), including the element, those implementations do not meet the requirements of the broader Web mapping community. The semantics of the HTML map element are incomplete or insufficient relative to modern Web maps and mapping in general. Currently, robust web maps are implemented by a variety of non-standard technologies. Web maps do not work without script support, making their creation a job beyond the realm of beginners' skill sets. In order to improve collaboration and integration of the mapping and Web communities, it is desirable to enhance or augment the functionality of the element in HTML to include the accessible user interface functions of modern web maps (e.g. panning, zooming, searching for, and zooming to, styling, identifying features’ properties, etc.), while maintaining a simple, declarative, accessible interface for HTML authors.\r\n\r\nThe objective of this Engineering Report is to explore how MapML can be harmonized with the OGC standards mainstream and contribute to the progress of the specification avoiding unnecessary duplication. In particular, the ER proposes Web Map Service (WMS) or Web Map Tile Service (WMTS) as services that can be used to deliver MapML documents with small modifications.\r\n\r\nAnother consideration on the ER is the inclusion of the time dimension and directions operation in MapML." + "@value": "This profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0.2 specification; it qualifies as a 'Class 2' profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60302,13 +59974,13 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-019" + "@value": "07-110r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: MapML Engineering Report" + "@value": "CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW" } ] }, @@ -60382,24 +60054,24 @@ ] }, { - "@id": "http://www.opengis.net/def/docs/08-001", + "@id": "http://www.opengis.net/def/docs/16-037", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-04-29" + "@value": "2017-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Raj Singh" + "@value": "Robert Cass" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -60409,27 +60081,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=26609" + "@id": "https://docs.ogc.org/per/16-037.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-001" + "@value": "16-037" }, { "@language": "en", - "@value": "Loosely Coupled Synchronization of Geographic Databases in the CGDI" + "@value": "Testbed-12 GeoPackage US Topo Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion Paper documents results from the Interoperability Program CGDI Pilot and describes a suite of services that enable the sharing of geographic information across organizations for the purposes of: geographic database synchronization in support of a spatial data infrastructure; geographic database modification suggestions from trusted and un-trusted sources; and the transmission of geographic information in emergency notification events.\r\n\r\nThese services are called the Update Feed Service; Feedback Feed Service; and Emergency Alert Service respectively. Their information encodings are all based on the Atom Syndication Format, extended with GML and WFS Filter encodings to support geospatial requirements, and were implemented in the Canadian Geospatial Data Infrastructure Pilot.\r\n" + "@value": "This OGC Engineering Report documents the outcome of the US Topo experiment. The focus of the US Topo experiment was to generate GeoPackages by combining USGS Topo Map Vector Data Products [1]; and the Topo TNM Style Template [2]. The output GeoPackages will contain both features and instructions for styling these features as well as orthoimagery, shaded relief raster tilesets, national wetlands raster tilesets and elevation data derived from USGS provide 1/9 arc second elevation imagery. The process used to generate the GeoPackage is explained. Problems and obstacles encountered decoding the source product and styles and converting these artifacts to a GeoPackage are explained with recommendations for improvements. Additionally, the experience applying the generated GeoPackage in two use cases proposed for this testbed will be evaluated. The introduction of symbolization for vector features will be articulated as a proposed extension for GeoPackage. Any issues related to encoding the TNM style template using the extension are documented." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60440,35 +60112,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-001" + "@value": "16-037" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Loosely Coupled Synchronization of Geographic Databases in the Canadian Geospatial Data Infrastructure Pilot" + "@value": "Testbed-12 GeoPackage US Topo Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-008", + "@id": "http://www.opengis.net/def/docs/16-131r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-15" + "@value": "2017-09-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthes Rieke" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -60478,27 +60150,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=58927" + "@id": "https://docs.ogc.org/wp/16-131r2/16-131r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 10 Report on Aviation Architecture" + "@value": "16-131r2" }, { "@language": "en", - "@value": "14-008" + "@value": "Big Geospatial Data – an OGC White Paper" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a deliverable of the OGC Testbed 10 (Testbed-10). This document describes the\r\narchitecture that was implemented in the Testbed-10 Aviation thread. Additionally, it provides\r\ndescriptions of all software components involved in the Aviation architecture as well as a\r\ndedicated chapter focusing on the evaluation and design of FIXM 2.0. Here, a special focus lies\r\non the integration into the data provisioning components, namely the Web Feature and Event\r\nServices." + "@value": "This white paper is a survey of Big Geospatial Data with these main themes:\r\n\r\n Geospatial data is increasing in volume and variety;\r\n New Big Data computing techniques are being applied to geospatial data;\r\n Geospatial Big Data techniques benefit many applications; and\r\n Open standards are needed for interoperability, efficiency, innovation and cost effectiveness.\r\n \r\n\r\nThe main purpose of this White Paper is to identify activities to be undertaken in OGC Programs that advance the Big Data capabilities as applied to geospatial information.\r\n\r\nThis white paper was developed based on two Location Powers events:\r\n\r\n Location Powers: Big Data, Orlando, September 20th, 2016; and\r\n Location Powers: Big Linked Data, Delft, March 22nd, 2017.\r\nFor information on Location Powers: http://www.locationpowers.net/pastevents/" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60509,35 +60181,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-008" + "@value": "16-131r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 10 Report on Aviation Architecture" + "@value": "Big Geospatial Data – an OGC White Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-131", + "@id": "http://www.opengis.net/def/docs/12-144", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-10-24" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Renato Primavera" + "@value": "David Burggraf" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -60547,27 +60219,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=17689" + "@id": "https://portal.ogc.org/files/?artifact_id=53255" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0" + "@value": "OWS-9 Architecture - Registry Engineering Report" }, { "@language": "en", - "@value": "06-131" + "@value": "12-144" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the Data Model of Earth Observation Products for the OGC" + "@value": "This OGC® Engineering Report provides guidelines for the harvest, registration and retrieval of aviation resources from an OGC web catalogue/registry service (OGC CSW-ebRIM), with particular emphasis on ISO metadata resources. Alternatives for selective and efficient retrieval of such resources are also described along with lessons learned. The OGC CSW-ebRIM registry interface is evaluated against SESAR registry requirements, documented as a gap analysis, to assess whether there are any obstacles to implementing SESAR registry with an OGC CSW-ebRIM interface." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60578,35 +60250,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-131" + "@value": "12-144" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0" + "@value": "OGC® OWS-9 Architecture - Registry Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-126", + "@id": "http://www.opengis.net/def/docs/15-051r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-01-15" + "@value": "2016-01-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman, Carl Reed" + "@value": "Jeff Harrison" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -60616,27 +60288,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=29536" + "@id": "https://portal.ogc.org/files/?artifact_id=65419" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-126" + "@value": "15-051r3" }, { "@language": "en", - "@value": "Topic 05 - Features" + "@value": "Testbed-11 OGC IP Engineering Report Geo4NIEM Architecture Design and Implementation Guidance and Fact Sheet " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "From ISO 19101, “A feature is an abstraction of a real world phenomenon”; it is a geographic feature if it is associated with a location relative to the Earth. " + "@value": "The goal of the Geo4NIEM thread in Testbed 11 was to assess the potential for the National Information Exchange Model (NIEM) to be combined with security tags from Intelligence Community (IC) Data Encoding Specifications for information exchange. The assessment included reviewing Information Exchange Package Documentation (IEPD) populated with relevant content and IC security tags – and then deploying these instance documents on Open Geospatial Consortium (OGC) standards enabled Web Services for testing. The security tags included Information Security Marking Metadata (ISM) and Need-to-Know (NTK) Metadata for secure information exchange. \r\nThe assessment included reviewing example IEPDs and performing tests and demonstrations using OGC web services, such as Transactional Web Feature Services (WFS-T), Policy Enforcement Points (PEPs) and OGC Attribute Stores to process geographic feature with NIEM components and security tags. The Test and Demonstration included, but was not limited to, feature retrieval and transactions. Results were documented in this task to provide a preliminary architecture for Geo4NIEM in Testbed 11, and were described in technical detail in other OGC Testbed 11 Engineering Reports. \r\nThis document describes background considerations – and an overview of the services, data encodings and access control frameworks that compose the Geo4NIEM Testbed 11 architecture. This document must be reviewed in conjunction with the following Testbed 11 Geo4NIEM ERs:\r\n•\t15-048 Testbed11_Engineering_Report_NIEM-IC Data Encoding Specification Assessment and Recommendations\r\n•\t15-047 Testbed11_Engineering_Report NIEM-IC Feature Processing API using OGC Web Services\r\n•\t15-050 Testbed11_Engineering_Report Test and Demonstration Results for NIEM using IC Data Encoding Specifications\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60647,35 +60319,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-126" + "@value": "15-051r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 5 - Features" + "@value": "Testbed-11 OGC IP Engineering Report Geo4NIEM Architecture Design and Implementation Guidance and Fact Sheet " } ] }, { - "@id": "http://www.opengis.net/def/docs/11-063r6", + "@id": "http://www.opengis.net/def/docs/04-039", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-11-23" + "@value": "2004-09-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Roger Brackin" + "@value": "Louis Rose" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -60685,27 +60357,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46342" + "@id": "https://portal.ogc.org/files/?artifact_id=6669" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-063r6" + "@value": "Geospatial Portal Reference Architecture" }, { "@language": "en", - "@value": "OWS-8 Cross Community Interoperability (CCI) Semantic Mediation Engineering Report" + "@value": "04-039" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OWS-8 Cross Community Interoperability (CCI) thread built on progress made in the recent OWS-7 initiative to cover key technology areas that could not be addressed within the scope of that initiative. The OWS-8 CCI thread aimed to increase interoperability within communities sharing geospatial data, including advancing of interoperability among heterogeneous data models, advancing strategies to share styles to provide a more common and automated use of symbology, improvement of KML, and advancing schema automation allowing communities to better share their information artefacts. This OGC engineering report aims to present findings from CCI thread activities towards advancement of semantic mediation involving data retrieved from heterogeneous data models that are available through web services conformant to OGC standards. \r\nThe engineering report will briefly introduce relevant details of the semantic web and mediation. The document will make recommendations on establishing a semantic mediation architecture that uses OGC web services and emerging practice from the semantic web community. Based on the scenario adopted by the CCI thread, the document will also discuss the pros and cons of adopting relevant standards. The engineering report will offer recommendations on how specific OGC standards may be adopted or modified in order to support semantic mediation.\r\n" + "@value": "This Guide has been developed by the members of the Open Geospatial Consortium, Inc. to assist the global geospatial technology community in implementing standards-based geospatial portal solutions that are compatible with Spatial Data Infrastructures in every nation. We offer this document as a resource for rapid development and informed acquisition of portals and portal-exploiting applications that can plug and play with geospatial data and services in your organization and other organizations in your community and around the world. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60716,35 +60388,160 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-063r6" + "@value": "04-039" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 Cross Community Interoperability (CCI) Semantic Mediation Engineering Report" + "@value": "Geospatial Portal Reference Architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-084", + "@id": "http://www.opengis.net/def/doc-type/d-is", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/07-002r3" + }, + { + "@id": "http://www.opengis.net/def/docs/02-069" + }, + { + "@id": "http://www.opengis.net/def/docs/10-157r3" + }, + { + "@id": "http://www.opengis.net/def/docs/00-028" + }, + { + "@id": "http://www.opengis.net/def/docs/02-023r4" + }, + { + "@id": "http://www.opengis.net/def/docs/04-021r3" + }, + { + "@id": "http://www.opengis.net/def/docs/01-047r2" + }, + { + "@id": "http://www.opengis.net/def/docs/07-067r5" + }, + { + "@id": "http://www.opengis.net/def/docs/05-008c1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-067r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-147r1" + }, + { + "@id": "http://www.opengis.net/def/docs/02-059" + }, + { + "@id": "http://www.opengis.net/def/docs/05-016" + }, + { + "@id": "http://www.opengis.net/def/docs/05-126" + }, + { + "@id": "http://www.opengis.net/def/docs/07-022r1" + }, + { + "@id": "http://www.opengis.net/def/docs/02-009" + }, + { + "@id": "http://www.opengis.net/def/docs/02-058" + }, + { + "@id": "http://www.opengis.net/def/docs/07-110r2" + }, + { + "@id": "http://www.opengis.net/def/docs/02-070" + }, + { + "@id": "http://www.opengis.net/def/docs/09-110r3" + }, + { + "@id": "http://www.opengis.net/def/docs/99-049" + }, + { + "@id": "http://www.opengis.net/def/docs/06-083r8" + }, + { + "@id": "http://www.opengis.net/def/docs/12-063r5" + }, + { + "@id": "http://www.opengis.net/def/docs/03-036r2" + }, + { + "@id": "http://www.opengis.net/def/docs/04-095c1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-103r3" + }, + { + "@id": "http://www.opengis.net/def/docs/07-026r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-025r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-014r3" + }, + { + "@id": "http://www.opengis.net/def/docs/10-126r3" + }, + { + "@id": "http://www.opengis.net/def/docs/13-026r8" + }, + { + "@id": "http://www.opengis.net/def/docs/06-104r3" + }, + { + "@id": "http://www.opengis.net/def/docs/99-051" + }, + { + "@id": "http://www.opengis.net/def/docs/05-076" + }, + { + "@id": "http://www.opengis.net/def/docs/07-144r2" + }, + { + "@id": "http://www.opengis.net/def/docs/04-095" + }, + { + "@id": "http://www.opengis.net/def/docs/03-065r6" + }, + { + "@id": "http://www.opengis.net/def/docs/05-134" + }, + { + "@id": "http://www.opengis.net/def/docs/01-068r3" + }, + { + "@id": "http://www.opengis.net/def/docs/02-087r3" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/23-033", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-06-27" + "@value": "2024-04-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Samantha Lavender, Trent Tinker" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -60754,27 +60551,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7560" + "@id": "https://docs.ogc.org/per/23-033.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-084" + "@value": "Testbed-19: Machine Learning Models Engineering Report" }, { "@language": "en", - "@value": "Topic 0 - Overview" + "@value": "23-033" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Introduction and roadmap to the Abstract specification. " + "@value": "The OGC Testbed 19 initiative explored six tasks including this task focused on Machine Learning: Transfer Learning for Geospatial Applications. \r\n\r\nThis OGC Testbed 19 Engineering Report (ER) documents work to develop the foundation for future standardization of Machine Learning models for transfer learning within geospatial, especially Earth Observation, applications. The ER reviews the findings of transfer learning experiments and makes recommendations about the next steps in terms of both the experiments conducted and broader implications for OGC." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60785,35 +60582,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-084" + "@value": "23-033" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 0 - Overview" + "@value": "Testbed-19: Machine Learning Models Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-062r7", + "@id": "http://www.opengis.net/def/docs/21-023", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-12-19" + "@value": "2021-12-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "Johannes Echterhoff, Julia Wagemann, Josh Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/orm" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -60823,27 +60620,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47245" + "@id": "https://docs.ogc.org/per/21-023.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-062r7" + "@value": "21-023" }, { "@language": "en", - "@value": "OGC Reference Model" + "@value": "Earth Observation Cloud Platform Concept Development Study Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/orm" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Reference Model (ORM) describes the OGC Standards Baseline focusing on relationships between the baseline documents. The OGC Standards Baseline (SB) consists of the approved OGC Abstract and Implementation Standards (Interface, Encoding, Profile, and Application Schema – normative documents) and OGC Best Practice documents (informative documents)." + "@value": "The Earth Observation Cloud Platform Concept Development Study (CDS) evaluates the readiness of satellite data providers and cloud service providers, as well as the maturity of their current systems, with regard to real-world deployment of the new “Applications-to-the-Data” paradigm, using cloud environments for EO data storage, processing, and retrieval." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60854,35 +60651,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-062r7" + "@value": "21-023" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Reference Model" + "@value": "Earth Observation Cloud Platform Concept Development Study Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-157r3", + "@id": "http://www.opengis.net/def/docs/06-010r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-06-12" + "@value": "2007-07-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jerome Gasperi, Frédéric Houbie, Andrew Woolf, Steven Smolders" + "@value": "Steve Havens" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -60892,27 +60689,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47040" + "@id": "https://portal.ogc.org/files/?artifact_id=19371" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-157r3" + "@value": "06-010r6" }, { "@language": "en", - "@value": "Earth Observation Metadata profile of Observations & Measurements" + "@value": "Transducer Markup Language" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Implementation Standard defines a profile of Observations and Measurements (ISO 19156) for describing Earth Observation products (EO products).\r\nAlthough this standard has been developed in the context of the Heterogeneous Mission Accessibility (HMA) project initiated by European Space Agency (ESA), the content is generic to Earth Observation product description. The metadata model described in this document is structured to follow the different types of products (Optical, Radar, …) which are not HMA specific.\r\n" + "@value": "*THIS STANDARD HAS BEEN RETIRED* \r\n\r\nThe OpenGIS® Transducer Markup Language Encoding Standard (TML) is an application and presentation layer communication protocol for exchanging live streaming or archived data to (i.e. control data) and/or sensor data from any sensor system. A sensor system can be one or more sensors, receivers, actuators, transmitters, and processes. A TML client can be capable of handling any TML enabled sensor system without prior knowledge of that system.\r\n \r\nThe protocol contains descriptions of both the sensor data and the sensor system itself. It is scalable, consistent, unambiguous, and usable with any sensor system incorporating any number sensors and actuators. It supports the precise spatial and temporal alignment of each data element. It also supports the registration, discovery and understanding of sensor systems and data, enabling users to ignore irrelevant data. It can adapt to highly dynamic and distributed environments in distributed net-centric operations.\r\n \r\nThe sensor system descriptions use common models and metadata and they describe the physical and semantic relationships of components, thus enabling sensor fusion.\r\n\r\nThis is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60923,35 +60720,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-157r3" + "@value": "06-010r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Earth Observation Metadata profile of Observations & Measurements" + "@value": "OpenGIS Transducer Markup Language *RETIRED*" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-004r4", + "@id": "http://www.opengis.net/def/docs/17-036", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-19" + "@value": "2018-01-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Charles Chen" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -60961,27 +60758,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/16-004r4" + "@id": "https://docs.ogc.org/per/17-036.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-004r4" + "@value": "17-036" }, { "@language": "en", - "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models" + "@value": "Testbed-13: Geospatial Taxonomies Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This CDB volume provides all of the information required to store Radar Cross Section (RCS) data within a conformant CDB data store. \r\nPlease note that the current CDB standard only provides encoding rules for using Esri ShapeFiles for storing RCS models. However, this Best Practice has been modified to change most of the ShapeFile references to “vector data sets” or “vector attributes” and “Point Shapes” to “Point geometries”. This was done in recognition that future versions of the CDB standard and related Best Practices will provide guidance on using other encodings/formats, such as OGC GML.\r\n" + "@value": "This Engineering Report (ER) documents the Geospatial Taxonomy research activities conducted by the Aviation (AVI) subthread of the Cross Community Interoperability (CCI) thread in OGC Testbed 13. One of the critical factors in the overall usability of services - and System Wide Information Management (SWIM) enabled services in particular - is the ability of a service to be discovered. The ability of a service to be discovered is assured by providing a uniformly interpretable set of service metadata that can be accessed by a service consumer through a retrieval mechanism (e.g., a service registry). Such a set of metadata (commonly referred to as a service description) has been defined by Federal Aviation Administration (FAA) and European Organization for the Safety of Air Navigation (EUROCONTROL) and formalized in a Service Description Conceptual Model (SDCM) [SDCM].\r\n\r\nThe SDCM is currently used in standard service description documents and service registries by both FAA and EUROCONTROL. As part of the effort of enhancing service discovery, both organizations also use a number of categories that can be associated with all services and are generally referred to as taxonomies. The current set of taxonomies used by both EUROCONTROL and FAA categorizes (i.e., meta tags) services based on their availability status, interface model, data product, etc. However, despite the increasing role of OGC services in the SWIM environment, no taxonomies for categorizing services based on geographical coverage or other geospatial characteristics have been defined. This ER documents the work conducted as part of Testbed 13 CCI thread and AVI subthread to identify and classify SWIM-enabled Service Oriented Architecture (SOA) services with geographical taxonomies and the integration thereof into SDCM." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -60992,35 +60789,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-004r4" + "@value": "17-036" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models" + "@value": "OGC Testbed-13: Geospatial Taxonomies Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-019r2", + "@id": "http://www.opengis.net/def/docs/11-097", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-11-02" + "@value": "2011-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mike Botts" + "@value": "Jérôme JANSOU, Thibault DACLA" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -61030,27 +60827,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7927" + "@id": "https://portal.ogc.org/files/?artifact_id=46394" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Sensor Model Language (SensorML) for In-situ and Remote Sensors" + "@value": "OWS-8 AIXM 5.1 Compression Benchmarking" }, { "@language": "en", - "@value": "04-019r2" + "@value": "11-097" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances." + "@value": "AIXM stands today for the de-facto standard for Aeronautical Information Publication, used by air control service providers from Europe, USA and Australia. With version 5.1, it reaches a level of maturity allowing the support of Digital NOTAMs, as the first official version of these messages was published this year.\r\nIn a near future, AIXM will be carried inside WFS requests but also into notification messages along WS event services. This last channel will be the one dedicated to D-NOTAMs. As D-NOTAM is aimed at aircrafts pilots, their transmission to the aircraft will use air/ground data link. Today, datalink communications lack bandwidth and future datalink will still have a limited capacity.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61061,35 +60858,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-019r2" + "@value": "11-097" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Model Language (SensorML) for In-situ and Remote Sensors" + "@value": "OWS-8 AIXM 5.1 Compression Benchmarking" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-013", + "@id": "http://www.opengis.net/def/docs/07-066r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-10-26" + "@value": "2008-04-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Tom Kralidis, Mark Burgoyne, Steve Olson, Shane Mill" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -61099,27 +60896,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/23-013.html" + "@id": "https://portal.ogc.org/files/?artifact_id=27298" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Discussion paper for Publish-Subscribe workflow in OGC APIs" + "@value": "Corrigendum 2 for the OGC Standard Web Coverage Service 1.1" }, { "@language": "en", - "@value": "23-013" + "@value": "07-066r5" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OGC APIs provide Web based capabilities which are typically based on polling for collection resource updates (new features/records items, coverages, maps, etc.). Depending on a collection’s temporal resolution or frequency of updates, an event-driven / Publish-Subscribe architecture provides a timely, efficient, and low latency approach for delivery of data updates. This paper provides recommendations on applying Publish-Subscribe architectural patterns to OGC APIs." + "@value": "This document provides the details of a corrigendum to an OpenGIS Implementation Standard and does not modify the base standard. The OGC Standard that this document provides revision notes for is Web Coverage Service Standard, Version 1.1 Corrigendum 2 [OGC 07-067r5]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61130,35 +60927,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-013" + "@value": "07-066r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Discussion paper for Publish-Subscribe workflow in OGC APIs" + "@value": "Corrigendum 2 for the OGC Standard Web Coverage Service 1.1" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-087", + "@id": "http://www.opengis.net/def/docs/09-035", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-02-20" + "@value": "2009-10-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matt Murray,Jeff Stollman,Shue-Jane Thompson,Terry Plymell,Eli Hertz,Chuck Heazel" + "@value": "Rüdiger Gartmann, Lewis Leinenweber" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -61168,27 +60965,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7562" + "@id": "https://portal.ogc.org/files/?artifact_id=35461" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "EA-SIG Enterprise Service Management White Paper" + "@value": "09-035" }, { "@language": "en", - "@value": "04-087" + "@value": "OWS-6 Security Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*RETIRED* This document focuses on the goals, objectives, capabilities and recommendation for the ESM Core Enterprise Service. The charter for this team was to address three fundamental questions:\r\n\r\n* What it Enterprise Service Management?\r\n* What can we buy or build today?\r\n* How should we invest for the future?\r\n\r\nThis paper responds to those questions by defining and describing ESM, discussing what is being done today, and what the group sees for the future of ESM?" + "@value": "This Engineering Report describes work accomplished during the OGC Web Services Testbed, Phase 6 (OWS 6) to investigate and implement security measures for OGC web services. This work was undertaken to address requirements stated in the OWS-6 RFQ/CFP originating from a number of sponsors, from OGC staff, and from OGC members. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61199,35 +60996,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-087" + "@value": "09-035" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "EA-SIG Enterprise Service Management White Paper" + "@value": "OWS-6 Security Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-103r3", + "@id": "http://www.opengis.net/def/docs/04-046r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-01-29" + "@value": "2004-02-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Herring" + "@value": "Roger Lott" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -61237,27 +61034,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=18241" + "@id": "https://portal.ogc.org/files/?artifact_id=6716" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-103r3" + "@value": "Topic 02 - Spatial Referencing by Coordinates" }, { "@language": "en", - "@value": "Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture" + "@value": "04-046r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. \r\n\r\nPart 1 “Common Architecture supplies the common feature model for use by applications that will use the Simple Features data stores and access interfaces. \r\n\r\nPart 2 provides a standard SQL implementation of the abstract model in Part 1. (Note: The OpenGIS® Simple Features Interface Standards for OLE/COM and CORBA are no longer current and are not provided here.) \r\n\r\nThe corresponding standard for the Web is the OpenGIS® Web Feature Service Interface Standard http://www.opengeospatial.org/standards/wfs.\r\n" + "@value": "Describes modelling requirements for spatial referencing by coordinates." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61268,35 +61065,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-103r3" + "@value": "04-046r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture" + "@value": "Topic 2 - Spatial Referencing by Coordinates" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-095r1", + "@id": "http://www.opengis.net/def/docs/12-128r10", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-12-19" + "@value": "2014-02-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stephan Meissl, Peter Baumann" + "@value": "Paul Daisey" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -61306,27 +61103,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47826" + "@id": "https://portal.ogc.org/files/?artifact_id=56357" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-8 WCS 2.0 Earth Observation Application Profile Compliance Tests Engineering Report" + "@value": "12-128r10" }, { "@language": "en", - "@value": "11-095r1" + "@value": "GeoPackage Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report describes and evaluates the specification of EO-WCS ATS and the implementation of ETS for use within an OGC SOA processing chain." + "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. \r\n

\r\nFor the online version of the standard and the developer resources, visit http://www.geopackage.org/" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61337,35 +61134,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-095r1" + "@value": "12-128r10" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 WCS 2.0 Earth Observation Application Profile Compliance Tests Engineering Report" + "@value": "OGC® GeoPackage Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-142r1", + "@id": "http://www.opengis.net/def/docs/02-024", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-02-01" + "@value": "2002-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Chun-fu Lin, Zhong-Hung Lee, Jen-Chu Liu, Kuo-Yu Chuang" + "@value": "John Evans" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -61375,27 +61172,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=36261" + "@id": "https://portal.ogc.org/files/?artifact_id=1131" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Open GeoSMS Specification" + "@value": "Web Coverage Service" }, { "@language": "en", - "@value": "09-142r1" + "@value": "02-024" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard specifies the location formats to be used by SMS for mobile phones and in other systems handling the SMS with location formats produced by mobile phones or LBS services." + "@value": "Extends the Web Map Server (WMS) interface to allow access to geospatial coverages that represent values or properties of geographic locations, rather than WMS generated maps (pictures)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61406,35 +61203,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-142r1" + "@value": "02-024" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC®: Open GeoSMS Specification" + "@value": "Web Coverage Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-059r4", + "@id": "http://www.opengis.net/def/docs/16-094r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-26" + "@value": "2017-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann, Jinsongdi Yu" + "@value": "Micah Brachman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -61444,27 +61241,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=54506" + "@id": "https://portal.ogc.org/files/?artifact_id=70051" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Service WCS Interface Standard - Processing Extension" + "@value": "GeoPackage Elevation Extension Interoperability Experiment Engineering Report" }, { "@language": "en", - "@value": "08-059r4" + "@value": "16-094r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Web Coverage Service (WCS)– Processing Extension defines an extension to the WCS Core [OGC 09-110], the ProcessCoverages request type, which allows clients to initi-ate server-side processing and filtering of coverages and to download the resulting coverage or value sets based on the query language defined in the Web Coverage Processing Service (WCPS) interface standard [OGC 08-068]." + "@value": "his OGC Engineering Report (ER) describes the setup, experiments, results and issues generated by the GeoPackage Elevation Extension Interoperability Experiment (GPKG-EE IE). The goal of the GPKG-EE IE was to implement and test a proposed elevation extension to the OGC GeoPackage Encoding Standard (12-128r1). The proposed elevation extension was successfully implemented by several IE participants and was demonstrated using both 2-Dimensional (2D) and 3-Dimensional (3D) software clients at the Washington, DC OGC Technical Committee (TC) meeting in [March 9, 2016]. This ER concludes with several recommendations for addressing remaining technical issues that must be resolved in order to complete a candidate GeoPackage Elevation Extension standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61475,35 +61272,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-059r4" + "@value": "16-094r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Coverage Service WCS Interface Standard - Processing Extension" + "@value": "OGC GeoPackage Elevation Extension Interoperability Experiment Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-168r6", + "@id": "http://www.opengis.net/def/docs/09-122", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-06-10" + "@value": "2009-10-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Douglas Nebert, Uwe Voges, Lorenzo Bigagli" + "@value": "Ben Domenico" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -61513,27 +61310,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/12-168r6/12-168r6.html" + "@id": "https://portal.ogc.org/files/?artifact_id=35505" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Catalogue Services 3.0 - General Model" + "@value": "CF-netCDF Encoding Specification" }, { "@language": "en", - "@value": "12-168r6" + "@value": "09-122" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OGC® Catalogue Services support the ability to publish and search collections of\r\ndescriptive information (metadata records) for geospatial data, services, and related\r\ninformation. Metadata in catalogues represent resource characteristics that can be queried\r\nand presented for evaluation and further processing by both humans and software.\r\nCatalogue services are required to support the discovery and binding to registered\r\ninformation resources within an information community.\r\nThis part of the Catalogue Services standard describes the common architecture for OGC\r\nCatalogue Services. This document abstractly specifies the interfaces between clients and\r\ncatalogue services, through the presentation of abstract models. This common\r\narchitecture is Distributed Computing Platform neutral and uses UML notation. Separate\r\n(Part) documents specify the protocol bindings for these Catalogue services, which build\r\nupon this document, for the HTTP (or CSW) and OpenSearch protocol bindings.\r\nAn Abstract Conformance Test Suite is not included in this document. Such Suites shall\r\nbe developed by protocol bindings and Application Profiles (see 8.5, ISO/IEC TR 10000-\r\n2:1998) that realize the conformance classes listed herein. An application profile\r\nconsists of a set of metadata elements, policies, and guidelines defined for a particular\r\napplication1.\r\nOGC document number 14-014r3 – HTTP Protocol Binding – Abstract Test Suite is\r\navailable to address conformance with the provisions of OGC document number 12-\r\n176r7 – HTTP Protocol Binding. All annexes to this document are informative." + "@value": "NetCDF (network Common Data Form) is a data model for array-oriented scientific data, a freely distributed collection of access libraries implementing support for that data model, and a machine-independent format. Together, the interfaces, libraries, and format support the creation, access, and sharing of scientific data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61544,35 +61341,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-168r6" + "@value": "09-122" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Catalogue Services 3.0 - General Model" + "@value": "CF-netCDF Encoding Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-061r1", + "@id": "http://www.opengis.net/def/docs/07-138r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-09-15" + "@value": "2008-09-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Poth, Markus Muller" + "@value": "Michael Werling" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -61582,27 +61379,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1174" + "@id": "https://portal.ogc.org/files/?artifact_id=30065" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coordinate Transformation Service" + "@value": "07-138r1" }, { "@language": "en", - "@value": "02-061r1" + "@value": "OWS-5 GeoProcessing Workflow Architecture Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the transformations of geo-spatial coordinates from one Coordinate Reference System (CRS) into another by means of a Web Service" + "@value": "This OGC® document describes the Workflow Architecture developed in support of Geoprocessing Workflow and Sensor Web Enablement threads of OWS-5. This information includes the overall architecture description, concepts, and issues. It also provides detail on the Conflation Workflow created as an example implementation for geoprocessing in a workflow. This document establishes a sample architecture and associated lessons learned as general guidance." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61613,82 +61410,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-061r1" + "@value": "07-138r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Coordinate Transformation Service" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-rfc/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type Request for Comment - deprecated " - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Documents of type Request for Comment - deprecated " - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/05-047r2" - }, - { - "@id": "http://www.opengis.net/def/docs/03-036" - }, - { - "@id": "http://www.opengis.net/def/docs/03-006r3" - }, - { - "@id": "http://www.opengis.net/def/docs/03-006r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-007r4" - }, - { - "@id": "http://www.opengis.net/def/docs/11-122r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-033r9" - }, - { - "@id": "http://www.opengis.net/def/docs/03-007r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Documents of type Request for Comment - deprecated " + "@value": "OWS-5 GeoProcessing Workflow Architecture Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-051r3", + "@id": "http://www.opengis.net/def/docs/16-059", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-01-25" + "@value": "2017-06-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Harrison" + "@value": "Stephane Fellah" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -61703,17 +61448,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=65419" + "@id": "https://docs.ogc.org/per/16-059.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-11 OGC IP Engineering Report Geo4NIEM Architecture Design and Implementation Guidance and Fact Sheet " + "@value": "Testbed-12 Semantic Portrayal, Registry and Mediation Engineering Report" }, { "@language": "en", - "@value": "15-051r3" + "@value": "16-059" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -61723,7 +61468,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The goal of the Geo4NIEM thread in Testbed 11 was to assess the potential for the National Information Exchange Model (NIEM) to be combined with security tags from Intelligence Community (IC) Data Encoding Specifications for information exchange. The assessment included reviewing Information Exchange Package Documentation (IEPD) populated with relevant content and IC security tags – and then deploying these instance documents on Open Geospatial Consortium (OGC) standards enabled Web Services for testing. The security tags included Information Security Marking Metadata (ISM) and Need-to-Know (NTK) Metadata for secure information exchange. \r\nThe assessment included reviewing example IEPDs and performing tests and demonstrations using OGC web services, such as Transactional Web Feature Services (WFS-T), Policy Enforcement Points (PEPs) and OGC Attribute Stores to process geographic feature with NIEM components and security tags. The Test and Demonstration included, but was not limited to, feature retrieval and transactions. Results were documented in this task to provide a preliminary architecture for Geo4NIEM in Testbed 11, and were described in technical detail in other OGC Testbed 11 Engineering Reports. \r\nThis document describes background considerations – and an overview of the services, data encodings and access control frameworks that compose the Geo4NIEM Testbed 11 architecture. This document must be reviewed in conjunction with the following Testbed 11 Geo4NIEM ERs:\r\n•\t15-048 Testbed11_Engineering_Report_NIEM-IC Data Encoding Specification Assessment and Recommendations\r\n•\t15-047 Testbed11_Engineering_Report NIEM-IC Feature Processing API using OGC Web Services\r\n•\t15-050 Testbed11_Engineering_Report Test and Demonstration Results for NIEM using IC Data Encoding Specifications\r\n" + "@value": "This engineering report documents the findings of the activities related to the Semantic Portrayal, Registry and Mediation components implemented during the OGC Testbed 12. This effort is a continuation of efforts initiated in the OGC Testbed 11. This report provides an analysis of the different standards considered during this effort, documents the rendering endpoints extension added to the Semantic Portrayal Service and the migration of the Portrayal metadata to the Semantic Registry, which is aligned with the DCAT REST Service API. We also discuss the integration of the CSW ebRIM for Application Schema with the Semantic Mediation Service, and document the improvements of the SPARQL Extensions, Portrayal and Semantic Mediation ontologies defined in the previous testbed.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61734,35 +61479,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-051r3" + "@value": "16-059" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-11 OGC IP Engineering Report Geo4NIEM Architecture Design and Implementation Guidance and Fact Sheet " + "@value": "Testbed-12 Semantic Portrayal, Registry and Mediation Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-110", + "@id": "http://www.opengis.net/def/docs/04-017r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-08-11" + "@value": "2004-10-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arnulf Christl and Carl Reed" + "@value": "Richard Martell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -61772,27 +61517,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=45126" + "@id": "https://portal.ogc.org/files/?artifact_id=7048" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Open Source and Open Standards" + "@value": "Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW" }, { "@language": "en", - "@value": "11-110" + "@value": "04-017r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This article is a White Paper jointly published by OGC and OSGeo. It was approved as an official joint OSGeo and OGC White Paper by the OSGeo Board of Directors in their 2011-05-05 Board meeting. \r\nThe text was collaboratively edited, reviewed and finalized by more than a a dozen active OSGeo and OGC members. Thanks especially to Gavin Fleming, Lance McKee, Markus Neteler, Athina Trakas, Michael Gerlek, Adrian Custer, Jeff McKenna, Cameron Shorter, Carl Reed, Frank Warmerdam, Steven Ramage, Daniel Morissette, Arnulf Christl and others for their contributions.\r\nPlease feel free to add comments, criticisms, links to other concise definitions on the associated Talk page: http://wiki.osgeo.org/wiki/Open_Source_and_Open_Standards." + "@value": "The OGC Catalogue Services 2.0 specification (OGC 04-021) establishes a framework for implementing catalogue services that can meet the needs of stakeholders in a wide variety of application domains. This application profile is based on the CSW schemas for web-based catalogues and it complies with the requirements of clause 11 in OGC 04-021." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61803,35 +61548,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-110" + "@value": "04-017r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Open Source and Open Standards" + "@value": "OGC Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-069r2", + "@id": "http://www.opengis.net/def/docs/17-047r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-08-22" + "@value": "2020-04-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Chris Little, Jon Blower, Maik Riechert " + "@value": "" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -61841,27 +61586,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/21-069r2/21-069r2.html" + "@id": "https://docs.ogc.org/is/17-047r1/17-047r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC CoverageJSON Community Standard" + "@value": "17-047r1" }, { "@language": "en", - "@value": "21-069r2" + "@value": "OpenSearch-EO GeoJSON(-LD) Response Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Based on JavaScript Object Notation (JSON), CoverageJSON is a format for publishing spatiotemporal data to the Web. The primary design goals are simplicity, machine and human readability and efficiency. While other use cases are possible, the primary CoverageJSON use case is enabling the development of interactive visual websites that display and manipulate environmental data within a web browser.\r\n\r\nImplementation experience has shown that CoverageJSON is an effective, efficient format, friendly to web and application developers, and therefore consistent with the current OGC API developments. CoverageJSON supports the efficient transfer from big data stores of useful quantities of data to lightweight clients, such as browsers and mobile applications. This enables straightfoward local manipulation of the data, for example, by science researchers. Web developers often use and are familiar with JSON formats.\r\n\r\nCoverageJSON 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.\r\n\r\nRelatively 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.\r\n\r\nThe simplest and most common use case is to embed all the data values of all variables in a Coverage object within the CoverageJSON document, so that it is “self-contained”. Such a standalone document supports the use of very simple clients.\r\n\r\nThe next simplest use case is to put data values for each variable (parameter) in separate array objects in separate CoverageJSON documents which are linked from the Coverage object. This is useful for a multi-variable dataset, such as one with temperature, humidity, wind speed, etc., to be recorded in separate files. This allows the client to load only the variables of interest.\r\n\r\nA sophisticated use case is to use tiling objects, where the data values are partitioned spatially and temporally, so that a single variable’s data values would be split among several documents. A simple example of this use case is encoding each time step of a dataset into a separate file, but the tiles could also be divided spatially in a manner similar to a tiled map server." + "@value": "The OpenSearch specification [NR3] is defined as a binding of the Abstract Protocol Definition (APD) for the searchRetrieve operation, one of a set of documents [NR4] for the OASIS Search Web Services (SWS) initiative [OR1]. The OpenSearch Description Document (OSDD) allows clients to retrieve service metadata from an OpenSearch implementation. The OSDD format allows the use of extensions that allow search engines to inform clients about specific and contextual query parameters and response formats. The OpenSearch extension for Earth Observation (EO) collections and products search is defined in [OR20]. The mandatory response format is based on Atom 1.0/XML [OR14].\r\n\r\nJavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. GeoJSON [NR2] is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. This OGC standard describes a GeoJSON [NR2] and JSON-LD [NR15] encoding for OpenSearch Response documents.\r\n\r\nThe GeoJSON encoding defined in this document is defined as a compaction[1] through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF/XML [OR11] and RDF Turtle [OR12].\r\n\r\nAlthough this document makes no assumptions as to the “service” interfaces through which the Search Response is obtained and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful architecture. The documented approach is mainly intended to be applied in combination with the following technologies:\r\n\r\nOGC OpenSearch extensions [OR19], [OR20], [NR3].\r\nGeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features.\r\n\r\nJSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR24] which allows validation of instances against these schemas." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61872,30 +61617,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-069r2" + "@value": "17-047r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC CoverageJSON Community Standard" + "@value": "OGC OpenSearch-EO GeoJSON(-LD) Response Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-024", + "@id": "http://www.opengis.net/def/docs/15-042r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-07-05" + "@value": "2023-06-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Alan Leidner, Andrew Hughes, Carsten Roensdorf, Neil Brammall, Liesbeth Rombouts, Joshua Lieberman" + "@value": "James Tomkins, Dominic Lowe, Paul Hershberg" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -61910,17 +61655,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/23-024/23-024.html" + "@id": "https://docs.ogc.org/is/15-042r6/15-042r6.pdf" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Model for Underground Data Definition and Integration (MUDDI) Part 1: Conceptual Model" + "@value": "OGC TimeseriesML 1.3 – XML Encoding of the Timeseries Profile of Observations and Measurements" }, { "@language": "en", - "@value": "23-024" + "@value": "15-042r6" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -61930,7 +61675,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "MUDDI stands for “Model for Underground Data Definition and Integration” and is an approach to make sub-surface data Findable, Accessible, Interoperable, and Re-Usable.\r\n\r\nThis document defines a Conceptual Model of classes that allows the integration of datasets from different types of information about the underground space, using different information models. These information models include models about elements such as utility infrastructure, transport infrastructure, soils, ground water, or environmental parameters. The Conceptual Model is a superset of classes representing Real-World Objects that can be found in the Underground." + "@value": "TimeseriesML 1.3 defines an XML encoding that implements the OGC Timeseries\r\nProfile of Observations and Measurements, with the intent of allowing the exchange of\r\nsuch data sets across information systems. Through the use of existing OGC standards, it\r\naims at being an interoperable exchange format that may be re-used to address a range of\r\ndata exchange requirements." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -61941,35 +61686,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-024" + "@value": "15-042r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Model for Underground Data Definition and Integration (MUDDI) Part 1: Conceptual Model" + "@value": "OGC TimeseriesML 1.3 – XML Encoding of the Timeseries Profile of Observations and Measurements" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-013", + "@id": "http://www.opengis.net/def/docs/19-016r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-01-15" + "@value": "2019-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Michael A. Leedahl" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -61979,27 +61724,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1338" + "@id": "https://docs.ogc.org/per/19-016r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Object Service Implementation Specification" + "@value": "19-016r1" }, { "@language": "en", - "@value": "03-013" + "@value": "OGC Testbed-15: Data Centric Security" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "There is a requirement to manage many different types of objects. These include styles, symbols and images. To satisfy this requirement, a repository interface is required. The intent of the Web Object Service interface is to provide a means to define this interface." + "@value": "The OGC Testbed-15 Data Centric Security Engineering Report (ER) discusses the current state of security in protecting data in a geospatial environment. The ER examines the use of encrypted container formats such as NATO STANAG 4778 Information on standard Metadata Binding with metadata as defined in NATO STANAG 4774 Confidentiality Metadata Label Syntax in combination with geospatial data using the encoding for an OGC Web Feature Service (WFS) FeatureCollection structure. This report also makes a recommendation for the creation of new media types to support output container formats such as STANAG 4778. The report then discusses various implementation scenarios in which a STANAG 4778 (eXtensible Markup Language (XML) container maintains encrypted data from author to service to viewer. These implementations use the new OGC API - Features - Part 1: Core with features encrypted using keys supplied by feature authors and users." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62010,35 +61755,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-013" + "@value": "19-016r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Object Service Implementation Specification" + "@value": "OGC Testbed-15: Data Centric Security" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-038r1", + "@id": "http://www.opengis.net/def/docs/06-104r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-10-05" + "@value": "2010-08-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Uwe Voges, Kristian Senkler" + "@value": "John Herring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -62048,27 +61793,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=6495" + "@id": "https://portal.ogc.org/files/?artifact_id=25354" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-038r1" + "@value": "06-104r4" }, { "@language": "en", - "@value": "ISO19115/ISO19119 Application Profile for CSW 2.0" + "@value": "Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS" + "@value": "The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62079,30 +61824,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-038r1" + "@value": "06-104r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "ISO19115/ISO19119 Application Profile for CSW 2.0" + "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-133r1", + "@id": "http://www.opengis.net/def/docs/12-007r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-08-22" + "@value": "2015-08-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Aaron Braeckel, Lorenzo Bigagli" + "@value": "David Burggraf" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -62117,17 +61862,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/13-133r1/13-133r1.html" + "@id": "https://docs.ogc.org/is/12-007r2/12-007r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension" + "@value": "12-007r2" }, { "@language": "en", - "@value": "13-133r1" + "@value": "KML 2.3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -62137,7 +61882,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Publish/Subscribe 1.0 is an interface specification that supports the core components and concepts of the Publish/Subscribe message exchange pattern with OGC Web Services. The Publish/Subscribe pattern complements the Request/Reply pattern historically specified by many OGC Web Services. This specification may be used either in concert with, or independently of, existing OGC Web Services to publish data of interest to subscribers.\r\n\r\nPublish/Subscribe 1.0 primarily addresses subscription management capabilities such as creating a subscription, renewing a subscription, and unsubscribing. However, this standard also allows Publish/Subscribe services to advertise and describe the supported message delivery protocols such as SOAP messaging, ATOM, and AMQP. Message delivery protocols should be considered to be independent of the Publish/Subscribe 1.0 standard. Therefore OGC Publish/Subscribe only includes metadata relating to message delivery protocols in sufficient detail to allow for different implementations of Publish/Subscribe 1.0 to interoperate. \r\n\r\nThis specification defines an extension to the OGC Publish/Subscribe (PubSub) 1.0 Core to allow for Publish/Subscribe communications usingthe SOAP protocol." + "@value": "KML is an XML grammar used to encode and transport representations of geographic data for display in an earth browser. Put simply: KML encodes what to show in an earth browser, and how to show it. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard.\r\n\r\nThe KML community is wide and varied. Casual users create KML Placemarks to identify their homes, describe journeys, and plan cross-country hikes and cycling ventures. Scientists use KML to provide detailed mappings of resources, models, and trends such as volcanic eruptions, weather patterns, earthquake activity, and mineral deposits. Real estate professionals, architects, and city development agencies use KML to propose construction and visualize plans. Students and teachers use KML to explore people, places, and events, both historic and current. Organizations such as National Geographic, UNESCO, and the Smithsonian have all used KML to display their rich sets of global data.\r\n\r\nKML documents and their related images (if any) may be compressed using the ZIP format into KMZ archives. KML documents and KMZ archives may be shared by e‑mail, hosted locally for sharing within a private internet, or hosted on a web server." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62148,35 +61893,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-133r1" + "@value": "12-007r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension" + "@value": "OGC KML 2.3" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-111", + "@id": "http://www.opengis.net/def/docs/21-075r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-06-08" + "@value": "2024-04-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "ISO" + "@value": "Andrew Lavender, Samantha Lavender" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -62186,27 +61931,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=26020" + "@id": "https://docs.ogc.org/per/21-075r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "01-111" + "@value": "OGC Disaster Pilot: User Readiness Guide" }, { "@language": "en", - "@value": "Topic 11 - Metadata" + "@value": "21-075r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "ISO 19115 was adopted as a replacement for OGC Abstract Specification Topics 9 and 11. In June 2001, a motion to include material in addition to ISO 19115 was adopted as document 01-111 Metadata AS. The approved addition to document 01-111 is contained in document 01-053r1, which normatively references parts of the old AS Topic 9, document 99-109r1. FGDC in conjunction with ANSI INCITS L1 are planning the migration of the FGDC Content Standard for Geospatial Metadata to be a profile of ISO 19115" + "@value": "Disasters are geographic events and therefore, geospatial information, tools and applications have the potential to support the management of, and response to, disaster scenarios.\r\n\r\nHowever, the use of geospatial data varies significantly across disaster and emergency communities. This can often make it difficult to share information between different organizations, and sometimes even within the same organization, involved in disaster response. This could mean that not everyone involved will have the same situational awareness information.\r\n\r\nThere are many reasons for why geospatial information is fully used and exploited, included a lack of awareness of what geospatial options are available, lack of geospatial technology and skills, lack of funding, etc. The Disaster Pilot User Guide aims to address some of these issues by providing a non-technical showcase of the workflows and tools developed by the Pilot participants demonstrating what opportunities there are for disaster and emergency management communities to use geospatial solutions in practice.\r\n\r\nFor over 20 years, the Open Geospatial Consortium (OGC) has been working on the challenges of information sharing for emergency and disaster planning, management, and response. In Disaster Pilot 23 (DP23) the aims were to:\r\n\r\nDevelop flexible, scalable, timely and resilient information data workflows to support critical disaster management decisions, enabling stakeholder collaboration, and\r\nProvide applications and visualization tools to promote the wider understanding of how geospatial data can support emergency and disaster communities.\r\nAs part of DP23, a trilogy of Guides were developed to improve knowledge and understanding of how geospatial data and tools and could support disaster and emergency communities. Alongside the User Guide is a Provider Guide giving all the detail technical details behind the work, and a companion Operational Capacity Guide describing the steps needed to develop geospatial readiness.\r\n\r\nThe User Guide contains a summary of the work undertaken in DP23, and Disaster Pilot 21 (DP21), where participants have worked on disaster scenarios relating to:\r\n\r\nDroughts\r\nWildland Fires\r\nFlooding\r\nLandslides\r\nHealth & Earth Observation Data for Pandemic Response\r\nCase Studies have focused on the hazards of drought in Manitoba, Canada; wildland fires in western United States; flooding in the Red River basin, Canada; landslides and flooding in Peru; and Pandemic response in Louisiana, United States. The participants have developed various data flows, alongside tools to support the collection, discovery, or visualization of data to support disaster management and response.\r\n\r\nAnnex A describes the tools and applications developed within the Pilots alongside the benefits these can offers. The Guide finishes with details of future possibilities, and where the Disaster Pilot initiative could focus next. Annexes B to E give descriptions of the data flows developed, including the aspects of disaster management or response the data flow relates to; together with the benefits it offers and the type of decisions it can support.\r\n\r\nThis document is for first responders, emergency managers, decision-makers, and anyone interested in encouraging disaster and emergency communities to realize the value of geospatial data to save lives and limit damage." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62217,35 +61962,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-111" + "@value": "21-075r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 11 - Metadata" + "@value": "OGC Disaster Pilot: User Readiness Guide" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-053r1", + "@id": "http://www.opengis.net/def/docs/16-004r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-16" + "@value": "2018-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -62255,27 +62000,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-053r1.html" + "@id": "https://portal.ogc.org/files/16-004r4" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 OWS Context: JSON, JSON-LD and HTML5 ER" + "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models" }, { "@language": "en", - "@value": "16-053r1" + "@value": "16-004r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "At the time of finalizing this ER the OGC TC has approved the OWS Context JSON encoding that is available here: http://www.opengeospatial.org/standards/owc This is the second encoding proposed for the OWS context standard precided by the Atom Encoding [OGC 12-084r2]. The OWS Context JSON enconding is based on the GeoJSON IETF standard [RFC7946]. The standard is a combination of two approaches:\r\n\r\nmapping between the OWS Context conceptual model [12-080r2] to the basic structure of a GeoJSON file.\r\n\r\na direct conversion of the rest of the atom keys and the specific OWS Context XML into JSON following OGC 14-009r1.\r\n\r\nThe conversion was designed with current GeoJSON viewers in mind (including the one embedded in GitHUB) and making possible that they can visualize a OWS Context GeoJSON file without any modifications.\r\n\r\nThis ER focus on describing another encoding (a 3rd alternative) that allows for exposing geospatial resources on the web in a way that web browsers and search engines can better understand. It is widely known that HTML was designed with the linking capacity in mind. Both, users reading HTML and automatic crawlers, transverse links constantly. HTML seems the natural selection for linking geospatial data on the web. The question is how to complement the linking mechanism with some additional metadata that search engines could use for indexing. A solution could come from a mechanism which web search engines already have agreed to use for better indexing: schema.org.\r\n\r\nSchemna.org proposes three enconding for their data model: Microdata, RDFa and JSON-LD. The reader might easily get confused by the fact that OGC approved a JSON encoding for OWS context and another JSON encoding emerges in this document. This ER is NOT proposing to replace or modify the currently approved JSON enconding for OWS context based on GeoJSON. The intention is to map the OWS Context model into the schema.org model to recognize that they are very similar and propose a encoding in HTML5 that can be done in the 3 alternative proposed by schema.org.\r\n\r\n" + "@value": "This CDB volume provides all of the information required to store Radar Cross Section (RCS) data within a conformant CDB data store. \r\nPlease note that the current CDB standard only provides encoding rules for using Esri ShapeFiles for storing RCS models. However, this Best Practice has been modified to change most of the ShapeFile references to “vector data sets” or “vector attributes” and “Point Shapes” to “Point geometries”. This was done in recognition that future versions of the CDB standard and related Best Practices will provide guidance on using other encodings/formats, such as OGC GML.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62286,35 +62031,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-053r1" + "@value": "16-004r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 OWS Context: JSON, JSON-LD and HTML5 ER" + "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-065r2", + "@id": "http://www.opengis.net/def/docs/01-036", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-02-16" + "@value": "2001-03-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthias Mueller" + "@value": "Rob Atkinson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -62324,27 +62069,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/14-065/14-065r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1041" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-065r2" + "@value": "01-036" }, { "@language": "en", - "@value": "WPS 2.0.2 Interface Standard: Corrigendum 2" + "@value": "Gazetteer" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "In many cases geospatial or location data, including data from sensors, must be processed before the information can be used effectively. The OGC Web Processing Service (WPS) Interface Standard provides a standard interface that simplifies the task of making simple or complex computational processing services accessible via web services. Such services include well-known processes found in GIS software as well as specialized processes for spatio-temporal modeling and simulation. While the OGC WPS standard was designed with spatial processing in mind, it can also be used to readily insert non-spatial processing tasks into a web services environment.\r\n\r\nThe WPS standard provides a robust, interoperable, and versatile protocol for process execution on web services. It supports both immediate processing for computational tasks that take little time and asynchronous processing for more complex and time consuming tasks. Moreover, the WPS standard defines a general process model that is designed to provide an interoperable description of processing functions. It is intended to support process cataloguing and discovery in a distributed environment.\r\n\r\n" + "@value": "An authority for place names. Returns their associated geometries" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62355,35 +62100,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-065r2" + "@value": "01-036" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® WPS 2.0.2 Interface Standard: Corrigendum 2" + "@value": "Gazetteer" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-067r4", + "@id": "http://www.opengis.net/def/docs/03-040", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-15" + "@value": "2003-09-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Daniel Balog, Robin Houtmeyers" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-orm" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -62393,27 +62138,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-067r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=3836" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Vector Tiling Implementation Engineering Report" + "@value": "OGC Reference Model" }, { "@language": "en", - "@value": "16-067r4" + "@value": "03-040" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-orm" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 12 Engineering Report (ER) discusses the topic of implementing vector tiles in an OGC GeoPackage. This report builds on the general topic of vector tiling discussed in OGC Testbed 12 Engineering Report [OGC 16-068r4].\r\n\r\nSince its public release in 2012, OGC GeoPackage has been getting increasingly popular within the geospatial industry for a variety of use cases, such as a means to package geospatial data for use on a mobile device and as a means to exchange geospatial data between two systems.\r\n\r\nThe OGC GeoPackage standard currently specifies requirements (rules) for storing raster tiles and vector (simple) features. This Engineering Report proposes an extension to the supported data types by introducing an implementation for vector tiles.\r\n\r\nWhile tiling and the use of multiple levels of details are a proven technique for accessing and visualizing raster data, it is less commonly applied for vector data. This is due to the increased complexity compared to raster tiling and lack of standardization on the topic. Yet, implementing vector tiles can provide the same benefits as for using raster tiles.\r\n\r\nServices can easily cache tiles and return them instantly upon request, without the need for any additional pre/post processing. Consequently, clients can get tiles very fast, ensuring fast and responsive maps.\r\n\r\nUsing tiled, multileveled data representations, clients can always access the data most suitable for their current map location and scale. This avoids the need to load too much data, which can cause excessive memory usage and reduce overall performance.\r\n\r\nThe goal is to enable systems to use OGC GeoPackage as a means to store and access vector tiles in an efficient way, similar to raster tiles.\r\n\r\n" + "@value": "The ORM describes a framework for the ongoing work of the Open Geospatial Consortium and our specifications and implementing interoperable solutions and applications for geospatial services, data, and applications." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62424,35 +62169,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-067r4" + "@value": "03-040" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Vector Tiling Implementation Engineering Report" + "@value": "OGC Reference Model" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-023r4", + "@id": "http://www.opengis.net/def/docs/06-129r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-01-29" + "@value": "2006-12-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside" + "@value": "Patrick Neal, John Davidson, Bruce Westcott" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -62462,27 +62207,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7174" + "@id": "https://portal.ogc.org/files/?artifact_id=16936" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geography Markup Language (GML) Encoding Specification" + "@value": "06-129r1" }, { "@language": "en", - "@value": "02-023r4" + "@value": "FGDC CSDGM Application Profile for CSW 2.0" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features." + "@value": "The OpenGIS® Catalogue Service Interface Standard 2.0.1 - FGDC CSDGM Application Profile for CSW 2.0 explains how Catalogue Services based on the FGDC Content Standard for Digital Geospatial Metadata (CSDGM) [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html] Application Profile for the OpenGIS® Catalogue Service Interface Standard v2.0.1 [http://www.opengeospatial.org/standards/cs] are organized and implemented for the discovery, retrieval and management of data metadata." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62493,35 +62238,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-023r4" + "@value": "06-129r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Geography Markup Language (GML) Encoding Specification" + "@value": "FGDC CSDGM Application Profile for CSW 2.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-047r1", + "@id": "http://www.opengis.net/def/docs/02-026r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-04-27" + "@value": "2002-04-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "" + "@value": "Mike Botts" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -62531,27 +62276,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/17-047r1/17-047r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1133" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OpenSearch-EO GeoJSON(-LD) Response Encoding Standard" + "@value": "SensorML" }, { "@language": "en", - "@value": "17-047r1" + "@value": "02-026r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenSearch specification [NR3] is defined as a binding of the Abstract Protocol Definition (APD) for the searchRetrieve operation, one of a set of documents [NR4] for the OASIS Search Web Services (SWS) initiative [OR1]. The OpenSearch Description Document (OSDD) allows clients to retrieve service metadata from an OpenSearch implementation. The OSDD format allows the use of extensions that allow search engines to inform clients about specific and contextual query parameters and response formats. The OpenSearch extension for Earth Observation (EO) collections and products search is defined in [OR20]. The mandatory response format is based on Atom 1.0/XML [OR14].\r\n\r\nJavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. GeoJSON [NR2] is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. This OGC standard describes a GeoJSON [NR2] and JSON-LD [NR15] encoding for OpenSearch Response documents.\r\n\r\nThe GeoJSON encoding defined in this document is defined as a compaction[1] through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF/XML [OR11] and RDF Turtle [OR12].\r\n\r\nAlthough this document makes no assumptions as to the “service” interfaces through which the Search Response is obtained and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful architecture. The documented approach is mainly intended to be applied in combination with the following technologies:\r\n\r\nOGC OpenSearch extensions [OR19], [OR20], [NR3].\r\nGeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features.\r\n\r\nJSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR24] which allows validation of instances against these schemas." + "@value": "The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62562,35 +62307,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-047r1" + "@value": "02-026r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC OpenSearch-EO GeoJSON(-LD) Response Encoding Standard" + "@value": "SensorML" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-135r2", + "@id": "http://www.opengis.net/def/docs/16-061", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2017-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Timo Thomas, Aleksandar Balaban" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -62600,27 +62345,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=53819" + "@id": "https://docs.ogc.org/per/16-061.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-135r2" + "@value": "Testbed-12 Aviation SBVR Engineering Report" }, { "@language": "en", - "@value": "Name Type Specification for Coordinate Reference Systems" + "@value": "16-061" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies a Name Type Specification (NTS) for predefined, combined, and parameterized Coordinate Reference System (CRS) definitions. This NTS augments the /def/ namespace with http URI definitions for CRSs. The NTS is based on the Name Type Specification – definitions – part 1 – basic name [OGC 09-048r3] and supersedes OGC document “Definition identifier URNs in OGC name¬space” [OGC 07-092r3].\r\nNTSs are maintained by the OGC Naming Authority (OGC-NA).\r\nThis document includes one Annex: a user guide to the OGC CRS resolver.\r\n" + "@value": "This engineering report (ER) is a deliverable of the OGC Testbed 12. It advances previous work in the area of business rules for AIXM 5 based on SBVR. It evaluates the use of geo-spatial operators and constraints in SBVR, including a proof of concept for their automatic interpretation by software. It gives guidelines on how to deal with temporality aspects and how to extend the applicability of SBVR towards filtering expressions and it identifies limitations of the currently available vocabulary." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62631,35 +62376,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-135r2" + "@value": "16-061" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Name Type Specification for Coordinate Reference Systems" + "@value": "Testbed-12 Aviation SBVR Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-039", + "@id": "http://www.opengis.net/def/docs/10-086r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-12-29" + "@value": "2010-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Nicolas Fanjeau, Sebastian Ulrich" + "@value": "Andrew Turner" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -62669,27 +62414,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/13-039/13-039.html" + "@id": "https://portal.ogc.org/files/?artifact_id=40334" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OpenSearch Extension for Earth Observation Satellite Tasking: Best Practice" + "@value": "OWS-7 - Authoritative Data Source Directory Engineering Report" }, { "@language": "en", - "@value": "13-039" + "@value": "10-086r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides a specification of an OpenSearch extension for Earth Observation Satellites Tasking.\r\n\r\nThis OGC Best Practice is intended to provide a very simple way to task Earth Observation (EO) satellites sensors, to allow simple syndication between, and to provide a basic federated query of related sensors, whereby a single client can query several instances and present a collection of future acquisition as one set.\r\n\r\nThis document is the result of work undertaken within the European Space Agency (ESA) Heterogeneous Mission Accessibility for Science (HMA-S) project funded by ESA the Long Term Data Preservation (LTDP) program.\r\n\r\nThe document was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative (see ‘Normative References’ section) related projects." + "@value": "This document presents the Authoritative Data Source Directory (ADSD) engineering suggestions and results of the OGC OWS-7 ADSD thread. This group focused on creating a workflow for geospatially referencing, finding, and federating data sources with associated authority and relevance." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62700,113 +62445,527 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-039" + "@value": "10-086r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OpenSearch Extension for Earth Observation Satellite Tasking: Best Practice" + "@value": "OWS-7 - Authoritative Data Source Directory Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-165r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/doc-type/dp", + "http://www.w3.org/2004/02/skos/core#narrower": [ { - "@type": "xsd:date", - "@value": "2013-04-02" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/07-138r1" + }, { - "@value": "Mike Botts, George Percivall, Carl Reed, John Davidson" + "@id": "http://www.opengis.net/def/docs/06-182r1" }, { - "@value": "Carl Reed, Mike Botts, George Percivall, John Davidson" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/08-058r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-116" + }, + { + "@id": "http://www.opengis.net/def/docs/21-067" + }, + { + "@id": "http://www.opengis.net/def/docs/05-102r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-073r2" + }, + { + "@id": "http://www.opengis.net/def/docs/04-051" + }, + { + "@id": "http://www.opengis.net/def/docs/13-068" + }, + { + "@id": "http://www.opengis.net/def/docs/08-001" + }, + { + "@id": "http://www.opengis.net/def/docs/21-010r2" + }, + { + "@id": "http://www.opengis.net/def/docs/19-091r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-002" + }, + { + "@id": "http://www.opengis.net/def/docs/09-084r1" + }, + { + "@id": "http://www.opengis.net/def/docs/19-090r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-032" + }, + { + "@id": "http://www.opengis.net/def/docs/12-027r3" + }, + { + "@id": "http://www.opengis.net/def/docs/20-088" + }, + { + "@id": "http://www.opengis.net/def/docs/03-014" + }, + { + "@id": "http://www.opengis.net/def/docs/08-071" + }, + { + "@id": "http://www.opengis.net/def/docs/03-026" + }, + { + "@id": "http://www.opengis.net/def/docs/09-132r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-001r3" + }, + { + "@id": "http://www.opengis.net/def/docs/21-077" + }, + { + "@id": "http://www.opengis.net/def/docs/15-012r2" + }, + { + "@id": "http://www.opengis.net/def/docs/05-140" + }, + { + "@id": "http://www.opengis.net/def/docs/06-140" + }, + { + "@id": "http://www.opengis.net/def/docs/05-115" + }, + { + "@id": "http://www.opengis.net/def/docs/07-160r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-041r1" + }, + { + "@id": "http://www.opengis.net/def/docs/15-100r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-094" + }, + { + "@id": "http://www.opengis.net/def/docs/11-163" + }, + { + "@id": "http://www.opengis.net/def/docs/08-127" + }, + { + "@id": "http://www.opengis.net/def/docs/09-112" + }, + { + "@id": "http://www.opengis.net/def/docs/13-101" + }, + { + "@id": "http://www.opengis.net/def/docs/10-134" + }, + { + "@id": "http://www.opengis.net/def/docs/08-054r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-029r4" + }, + { + "@id": "http://www.opengis.net/def/docs/04-039" + }, + { + "@id": "http://www.opengis.net/def/docs/08-122r2" + }, + { + "@id": "http://www.opengis.net/def/docs/17-059" + }, + { + "@id": "http://www.opengis.net/def/docs/07-169" + }, + { + "@id": "http://www.opengis.net/def/docs/19-004" + }, + { + "@id": "http://www.opengis.net/def/docs/05-084" + }, + { + "@id": "http://www.opengis.net/def/docs/06-045r1" + }, + { + "@id": "http://www.opengis.net/def/docs/03-025" + }, + { + "@id": "http://www.opengis.net/def/docs/18-001r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-088r1" + }, + { + "@id": "http://www.opengis.net/def/docs/21-041r2" + }, + { + "@id": "http://www.opengis.net/def/docs/10-191r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-018" + }, + { + "@id": "http://www.opengis.net/def/docs/04-071" + }, + { + "@id": "http://www.opengis.net/def/docs/06-155" + }, + { + "@id": "http://www.opengis.net/def/docs/16-142" + }, + { + "@id": "http://www.opengis.net/def/docs/05-111r2" + }, + { + "@id": "http://www.opengis.net/def/docs/13-100" + }, + { + "@id": "http://www.opengis.net/def/docs/09-010" + }, + { + "@id": "http://www.opengis.net/def/docs/05-017" + }, + { + "@id": "http://www.opengis.net/def/docs/07-056r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-101" + }, + { + "@id": "http://www.opengis.net/def/docs/15-116" + }, + { + "@id": "http://www.opengis.net/def/docs/08-079" + }, + { + "@id": "http://www.opengis.net/def/docs/05-014" + }, + { + "@id": "http://www.opengis.net/def/docs/08-009r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-154" + }, + { + "@id": "http://www.opengis.net/def/docs/16-145" + }, + { + "@id": "http://www.opengis.net/def/docs/11-039r3" + }, + { + "@id": "http://www.opengis.net/def/docs/07-007r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-023r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-041r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-163r2" + }, + { + "@id": "http://www.opengis.net/def/docs/17-049" + }, + { + "@id": "http://www.opengis.net/def/docs/23-022r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-012" + }, + { + "@id": "http://www.opengis.net/def/docs/04-060r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-122" + }, + { + "@id": "http://www.opengis.net/def/docs/08-077" + }, + { + "@id": "http://www.opengis.net/def/docs/09-123" + }, + { + "@id": "http://www.opengis.net/def/docs/16-114r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-124r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-037r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-001" + }, + { + "@id": "http://www.opengis.net/def/docs/04-050r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-124r2" + }, + { + "@id": "http://www.opengis.net/def/docs/10-171" + }, + { + "@id": "http://www.opengis.net/def/docs/15-074r2" + }, + { + "@id": "http://www.opengis.net/def/docs/07-158" + }, + { + "@id": "http://www.opengis.net/def/docs/11-058r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-195" + }, + { + "@id": "http://www.opengis.net/def/docs/08-076" + }, + { + "@id": "http://www.opengis.net/def/docs/08-000" + }, + { + "@id": "http://www.opengis.net/def/docs/06-079r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-173r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-031r2" + }, + { + "@id": "http://www.opengis.net/def/docs/19-047" + }, + { + "@id": "http://www.opengis.net/def/docs/06-107r1" + }, + { + "@id": "http://www.opengis.net/def/docs/23-040" + }, + { + "@id": "http://www.opengis.net/def/docs/16-129" + }, + { + "@id": "http://www.opengis.net/def/docs/04-052" + }, + { + "@id": "http://www.opengis.net/def/docs/12-028r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-079" + }, + { + "@id": "http://www.opengis.net/def/docs/09-082" + }, + { + "@id": "http://www.opengis.net/def/docs/03-029" + }, + { + "@id": "http://www.opengis.net/def/docs/20-000r1" + }, + { + "@id": "http://www.opengis.net/def/docs/18-077r2" + }, + { + "@id": "http://www.opengis.net/def/docs/20-092" + }, + { + "@id": "http://www.opengis.net/def/docs/23-013" + }, + { + "@id": "http://www.opengis.net/def/docs/16-012r1" + }, + { + "@id": "http://www.opengis.net/def/docs/15-096" + }, + { + "@id": "http://www.opengis.net/def/docs/08-132" + }, + { + "@id": "http://www.opengis.net/def/docs/07-163" + }, + { + "@id": "http://www.opengis.net/def/docs/12-117r1" + }, + { + "@id": "http://www.opengis.net/def/docs/15-074" + }, + { + "@id": "http://www.opengis.net/def/docs/13-021r3" + }, + { + "@id": "http://www.opengis.net/def/docs/09-166r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-084r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-004" + }, + { + "@id": "http://www.opengis.net/def/docs/06-187r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-152" + }, + { + "@id": "http://www.opengis.net/def/docs/04-100" + }, + { + "@id": "http://www.opengis.net/def/docs/07-172r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-055r1" + }, + { + "@id": "http://www.opengis.net/def/docs/14-121r2" + }, + { + "@id": "http://www.opengis.net/def/docs/19-042r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-125" + }, + { + "@id": "http://www.opengis.net/def/docs/07-166r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-029" + }, + { + "@id": "http://www.opengis.net/def/docs/07-009r3" + }, + { + "@id": "http://www.opengis.net/def/docs/07-027r1" + }, + { + "@id": "http://www.opengis.net/def/docs/15-122r1" + }, + { + "@id": "http://www.opengis.net/def/docs/03-028" + }, + { + "@id": "http://www.opengis.net/def/docs/09-018" + }, + { + "@id": "http://www.opengis.net/def/docs/24-025" + }, + { + "@id": "http://www.opengis.net/def/docs/05-015" + }, + { + "@id": "http://www.opengis.net/def/docs/20-054r1" + }, + { + "@id": "http://www.opengis.net/def/docs/13-099" + }, + { + "@id": "http://www.opengis.net/def/docs/18-056" + }, + { + "@id": "http://www.opengis.net/def/docs/09-104r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-184r2" + }, + { + "@id": "http://www.opengis.net/def/docs/08-078r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-076r3" + }, + { + "@id": "http://www.opengis.net/def/docs/06-022r1" + }, + { + "@id": "http://www.opengis.net/def/docs/21-037" + }, + { + "@id": "http://www.opengis.net/def/docs/09-085r2" + }, + { + "@id": "http://www.opengis.net/def/docs/23-056" + }, + { + "@id": "http://www.opengis.net/def/docs/10-196r1" + }, + { + "@id": "http://www.opengis.net/def/docs/19-077" + }, + { + "@id": "http://www.opengis.net/def/docs/05-050" + }, + { + "@id": "http://www.opengis.net/def/docs/04-011r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/techpaper" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/06-002r1" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/01-061" + }, { - "@id": "https://docs.ogc.org/wp/07-165r1/" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/05-118" + }, { - "@language": "en", - "@value": "Sensor Web Enablement: Overview And High Level Architecture" + "@id": "http://www.opengis.net/def/docs/08-133" }, { - "@language": "en", - "@value": "OGC Sensor Web Enablement: Overview and High Level Architecture" + "@id": "http://www.opengis.net/def/docs/04-010r1" }, { - "@language": "en", - "@value": "07-165r1" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/15-075r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/techpaper" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/09-042" + }, { - "@value": "A sensor network is a computer accessible network of many, spatially distributed devices using sensors to monitor conditions at different locations, such as temperature, sound, vibration, pressure, motion or pollutants[1]. A Sensor Web refers to web accessible sensor networks and archived sensor data that can be discovered and accessed using standard protocols and application program interfaces (APIs)." + "@id": "http://www.opengis.net/def/docs/15-039" }, { - "@value": "This OGC White Paper provides a high-level overview of and architecture for the Open Geospatial\r\nConsortium (OGC) standards activities that focus on sensors, sensor networks, and a concept called the\r\n“Sensor Web”. This OGC focus area is known as Sensor Web Enablement (SWE)." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/01-019" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/16-084" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-165r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/07-095r2" + }, { - "@language": "en", - "@value": "OGC® Sensor Web Enablement: Overview And High Level Architecture" + "@id": "http://www.opengis.net/def/docs/02-017r1" }, { - "@language": "en", - "@value": "OGC Sensor Web Enablement: Overview and High Level Architecture" + "@id": "http://www.opengis.net/def/docs/09-112r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-117" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-083r2", + "@id": "http://www.opengis.net/def/docs/09-129", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-05-10" + "@value": "2010-02-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Josh Lieberman" + "@value": "Nadine Alameh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -62821,17 +62980,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-083r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=35634" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-083r2" + "@value": "09-129" }, { "@language": "en", - "@value": "Building Energy Mapping and Analytics: Concept Development Study Report" + "@value": "AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -62841,7 +63000,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report details the results of the OGC Building Energy Mapping and Analysis Concept Development Study (BEMA CDS). Sponsored by NRCan and drawing on numerous previous studies, the CDS released a Request for Information on building energy data and applications. The responses were presented and validated in 3 public workshops and form the basis for an Energy SDI notional architecture." + "@value": "This AIP-2 Engineering Report (ER) describes a set of transverse technology Use Cases developed and applied in the GEOSS Architecture Implementation Pilot Phase 2 (AIP-2). Such Use Cases define reusable activities within a service-oriented architecture, tailored for the GEOSS environment. This report contains the general Use Cases that were specialized by community Working Groups to implement several specific Societal Benefit Area (SBA) Scenarios in AIP-2. The SBA Scenarios and specialized use cases are defined in separate AIP-2 ERs. This AIP-2 ER will be offered for consideration by the GEOSS Best Practice Registry editors and to OGC Technical Committee for consideration as a Best Practice." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62852,35 +63011,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-083r2" + "@value": "09-129" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Building Energy Mapping and Analytics: Concept Development Study Report" + "@value": "AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-096", + "@id": "http://www.opengis.net/def/docs/14-110r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-11-23" + "@value": "2016-11-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stephan Meissl, Peter Baumann" + "@value": "Dimitri Sarafinof" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -62890,27 +63049,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=45404" + "@id": "https://docs.ogc.org/bp/14-110r2/14-110r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-8 WCS 2.0 Earth Observation Application Profile Engineering Report" + "@value": "14-110r2" }, { "@language": "en", - "@value": "11-096" + "@value": "GML Application Schema - Coverages JPEG2000/JPIP Coverage Encoding Extension" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report describes progress on EO-WCS in the course of OWS-8." + "@value": "Coverages represent space/time-varying phenomena, such as satellite imagery, digital elevation models, or digital aerial imagery. OGC Abstract Topic 6 [OGC 07-011] – which is identical to ISO 19123 – defines an abstract model of coverages. Coverage instances may be encoded using the GML Application Schema – Coverages – JPEG2000 Coverage Encoding Extension version 1.0 [OGC 12-108] which is based on the GML Application Schema – Coverages (GMLCOV) version 1.0 [OGC 09-146r2] which in turn is based on the Geography Markup Language (GML) version 3.2 [07-036], an XML grammar written in XML Schema for the description of application schemas as well as the transport and storage of geographic information.\r\n\r\nThis extension to the Web Coverage Service (WCS) 2.0 Interface Standard – Core (WCS) version 2.0 [OC 09-110r4] specifies the usage of the JPEG2000 coverage encoding and JPIP streaming capabilities with WCS. The approach is based on the authoritative GML Application Schema – Coverages – JPEG2000 Coverage Encoding Extension version 1.0 [OGC 12-108]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62921,35 +63080,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-096" + "@value": "14-110r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 WCS 2.0 Earth Observation Application Profile Engineering Report" + "@value": "OGC® GML Application Schema - Coverages JPEG2000/JPIP Coverage Encoding Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-041r3", + "@id": "http://www.opengis.net/def/docs/05-025r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-01-08" + "@value": "2006-10-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sam Meek, Theo Brown, Clemens Portele" + "@value": "Richard Martell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -62959,27 +63118,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-041r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=12604" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Routing Pilot ER" + "@value": "Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW" }, { "@language": "en", - "@value": "19-041r3" + "@value": "05-025r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The goal of this OGC Routing Pilot Engineering Report (ER) is to document the proof of concept of an Application Programming Interface (API) conforming to a profile of the draft OGC API - Processes specification that allows implementation of vector routing across one or more routing engines. The components implemented in the OGC Open Routing API Pilot 2019 included two clients, interfacing with three implementations of the draft OGC API - Processes specification that in turn communicated with three routing engines. This work resulted in the definition of a proposed common interface and data exchange model supported by all components for requesting, generating and returning routes." + "@value": "The OGC Catalogue Services 2.0 specification (OGC 04-021r3) establishes a general framework for implementing catalogue services that can be applied to meet the needs of stakeholders in a wide variety of domains. This application profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0 specification; it qualifies as a Class 2 profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -62990,35 +63149,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-041r3" + "@value": "05-025r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Routing Pilot ER" + "@value": "OpenGIS Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-092r1", + "@id": "http://www.opengis.net/def/docs/20-095", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-11-14" + "@value": "2021-02-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "DGIWG" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -63028,27 +63187,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=24045" + "@id": "https://portal.ogc.org/files/95763" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Definition identifier URNs in OGC namespace" + "@value": "20-095" }, { "@language": "en", - "@value": "07-092r1" + "@value": "Defence Geospatial Information Working Group (DGIWG) GeoTIFF/TIFF Profile for Imagery & Gridded Data 2.3.1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Best Practices Paper specifies Universal Resource Names (URNs) in the ogc URN namespace to be used for identifying definitions. This document specifies the formats used by these URNs, plus a set of specific URNs for specific definitions. These definitions should be used wherever applicable by implementations of various OGC Implementation Specifications, including GML, WMS, WFS, and WCS. " + "@value": "This OGC Best Practice was developed by the Defence Geospatial Information Working Group to address defense and intelligence user community requirements. As such, the Best Practice utilizes standardized military Coordinate Reference System (CRS) definitions, which may not be applicable to other user communities.\r\nThis Best Practice also defines a GEO_METADATA tag, which may be of more general interest.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63059,35 +63218,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-092r1" + "@value": "20-095" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Definition identifier URNs in OGC namespace" + "@value": "Defence Geospatial Information Working Group (DGIWG) GeoTIFF/TIFF Profile for Imagery & Gridded Data 2.3.1" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-003r2", + "@id": "http://www.opengis.net/def/docs/10-195", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-02-14" + "@value": "2011-03-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Y. Coene, U. Voges, O. Barois" + "@value": "OGC Aviation Domain Working Group" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -63097,27 +63256,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/17-003r2/17-003r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=41667" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-003r2" + "@value": "10-195" }, { "@language": "en", - "@value": "EO Dataset Metadata GeoJSON(-LD) Encoding Standard" + "@value": "Requirements for Aviation Metadata" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "JavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. This OGC standard describes a GeoJSON [NR2] and JSON-LD [NR3] encoding for Earth Observation (EO) metadata for datasets (granules). This standard can be applied to encode metadata based on the Earth Observation Metadata Profile of Observations and Measurements (O&M) OGC 10-157r4 [OR1] or as an encoding of the Unified Metadata Model for Granules (UMM-G) conceptual model [OR2].\r\n\r\nThe GeoJSON encoding defined in this document is defined as a compaction[1] through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF XML [OR11] and RDF Turtle [OR12].\r\n\r\nThis document makes no assumptions as to the “service” interfaces through which the metadata are accessed and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful Architecture. The documented approach can be applied in combination with the following technologies:\r\n\r\nOGC OpenSearch extensions [OR19], [OR20], [OR25],\r\nW3C Linked Data Platform [OR21], [OR22],\r\nOASIS searchRetrieve [OR23],\r\nOASIS OData [OR24].\r\nGeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features.\r\n\r\nJSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR18] which allows validation of instances against these schemas." + "@value": "This OGC Discussion Paper details the user requirements for metadata in the aviation domain. The requirements are at a high-level." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63128,35 +63287,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-003r2" + "@value": "10-195" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard" + "@value": "Requirements for Aviation Metadata" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-029", + "@id": "http://www.opengis.net/def/docs/02-017r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-02-20" + "@value": "2002-08-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ron Lake" + "@value": "Jeff de La Beaujardiere" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -63166,27 +63325,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1034" + "@id": "https://portal.ogc.org/files/?artifact_id=1118" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "01-029" + "@value": "02-017r1" }, { "@language": "en", - "@value": "Geography Markup Language" + "@value": "WMS Part 2: XML for Requests using HTTP Post" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features." + "@value": "This part of the Web Map Service (WMS) specification applies to those clients and servers which allow operation request encodings that are more complex than those permitted by the basic keyword/value encoding defined in WMS Part 1 [17]. Part 2 only describes the encoding of the request messages using Extensible Markup Language (XML); all other aspects of the Web Map Service are fully defined in Part 1." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63197,30 +63356,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-029" + "@value": "02-017r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geography Markup Language" + "@value": "WMS Part 2: XML for Requests using HTTP Post" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-149r1", + "@id": "http://www.opengis.net/def/docs/05-077r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-10-27" + "@value": "2007-01-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Dr. Markus Mueller" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -63235,17 +63394,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41441" + "@id": "https://portal.ogc.org/files/?artifact_id=16700" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-149r1" + "@value": "05-077r4" }, { "@language": "en", - "@value": "Web Coverage Service 2.0 Interface Standard - XML/SOAP Protocol Binding Extension" + "@value": "Symbology Encoding Implementation Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -63255,7 +63414,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using SOAP with XML encoding." + "@value": "The OpenGIS® Symbology Encoding Standard (SES) defines an XML language for styling information that can be applied to digital geographic feature and coverage data. SE is independent of any OGC Web Services descriptions and could therefore be used to describe styling information in non-networked systems such as desktop geographic information systems. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63266,35 +63425,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-149r1" + "@value": "05-077r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Coverage Service 2.0 Interface Standard - XML/SOAP Protocol Binding Extension" + "@value": "OpenGIS Symbology Encoding Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-076", + "@id": "http://www.opengis.net/def/docs/11-055", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-09-12" + "@value": "2011-11-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Rüdiger Gartmann" + "@value": "Steve Miller" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -63304,27 +63463,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=28162" + "@id": "https://portal.ogc.org/files/?artifact_id=44939" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-076" + "@value": "OGC SAA Pilot Study Engineering Report" }, { "@language": "en", - "@value": "OWS-5 GeoRM License Broker Discussion Paper" + "@value": "11-055" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes a License Broker Service (LB-Service) as specified and implemented in the OWS-5 test bed. The LB-Service provides configurable license models, which may contain configuration parameters to be defined by the licensee. The setting of these parameters affects the actual license to be created by the LB-Service. " + "@value": "This OGC® document describes the architecture used for the implementation of the SAA Dissemination Pilot Study demonstrations. This includes an overview of the implemented components and workflows, and discussions of lessons learned." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63335,35 +63494,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-076" + "@value": "11-055" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-5 GeoRM License Broker Discussion Paper" + "@value": "OGC SAA Pilot Study Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-057r4", + "@id": "http://www.opengis.net/def/docs/17-041", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-03-20" + "@value": "2018-02-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jolyon Martin" + "@value": "Stefano Cavazzi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -63373,27 +63532,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=14443" + "@id": "https://docs.ogc.org/per/17-041.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Catalogue Services - Best Practices for for Earth Observation Products" + "@value": "17-041" }, { "@language": "en", - "@value": "05-057r4" + "@value": "Testbed-13: Vector Tiles Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The services proposed in this profile are intended to support the identification and subsequent ordering of EO data products from previously identified data collections. The intent of this initial profile is to describe a minimum interface that can be supported by many data providers (satellite operators, data distributors...), most of whom have existing (and relatively complex) facilities for the management of these data." + "@value": "This Open Geospatial Consortium (OGC) Engineering Report (ER) captures the requirements, solutions, and implementation experiences of the Vector Tiling work package in OGC Testbed-13 [Available at: http://www.opengeospatial.org/projects/initiatives/testbed13]. This ER describes the evaluation of existing vector tiling solutions. The evaluation was used to define a conceptual model that integrates elements from different approaches to vector tiling. This is followed by an overview of how the developed implementation integrates vector tiles containing World Geodetic System 1984 (WGS84), European Terrestrial Reference System 1989 (ETRS89) and British National Grid projection data, standards based tile schemas and moving features. Best practice guidelines for the use of Symbology Encoding (SE) and Styled Layer Descriptor (SLD) are also provided ensuring the service is optimized for analysis and low-bandwidth networks. The report concludes with an investigation on how existing OGC services may be extended with the necessary capabilities enabling the full range of geometry types and tiling strategies to support vector tiling." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63404,30 +63563,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-057r4" + "@value": "17-041" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Catalogue Services - Best Practices for for Earth Observation Products" + "@value": "OGC Testbed-13: Vector Tiles Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-120r3", + "@id": "http://www.opengis.net/def/docs/07-147r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-03-12" + "@value": "2008-04-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Hideki Hayashi, Akinori Asahara, Kyoung-Sook Kim, Ryosuke Shibasaki, Nobuhiro Ishimaru" + "@value": "Tim Wilson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -63442,17 +63601,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/16-120r3/16-120r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=27810" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Moving Features Access" + "@value": "07-147r2" }, { "@language": "en", - "@value": "16-120r3" + "@value": "KML" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -63462,7 +63621,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines Moving Features Access, i.e., access methods to moving feature data for retrieving feature attributes, information on a relation between a trajectory object and one or more geometry objects, and information on a relation between two trajectory objects from a database storing trajectory data of moving features.\r\n\r\nAbstract methods of accessing moving features data are defined in ISO 19141:2008 (Geographic information - Schema for moving features) [ISO 19141:2008]. However, the methods are insufficient to access a database storing moving feature data from multiple sources. If implementations for access to moving features data using various programming languages or protocols (e.g., SQL, Java, and HTTP) are developed without any standards, these implementations might be inconsistent with each other, resulting in poor interoperability. Therefore, methods to access a database storing moving feature data are necessary to improve interoperability.\r\n\r\nApplications using moving feature data, typically representing vehicles or pedestrians, are rapidly increasing. Innovative applications are expected to require the overlay and integration of moving feature data from different sources to create greater social and business value. Moreover, systems relying on single-source moving feature data are now evolving into more integrated systems. Integration of moving feature data from different sources is a key to developing more innovative and advanced applications.\r\n\r\nMoving Features Access ensures better data exchange by handling and integrating moving feature data to broaden the market for geo-spatial information such as Geospatial Big Data Analysis. OGC 14-083r2 (OGC® Moving Features Encoding Part I: XML Core) [OGC 14-083r2] and OGC 14-084r2 (OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV)) [OGC 14-084r2] are existing implementation standards. Moving Features Access uses these standards to encode moving features." + "@value": "KML is an XML language focused on geographic visualization, including annotation of maps and images. Geographic visualization includes not only the presentation of graphical data on the globe, but also the control of the user's navigation in the sense of where to go and where to look." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63473,35 +63632,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-120r3" + "@value": "07-147r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Moving Features Access" + "@value": "OGC KML" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-082r4", + "@id": "http://www.opengis.net/def/docs/16-101r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-05-26" + "@value": "2017-08-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Katharina Schleidt, Ilkka Rinne" + "@value": "Paul Scarponcini" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -63511,27 +63670,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/as/20-082r4/20-082r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=75118" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-082r4" + "@value": "16-101r2" }, { "@language": "en", - "@value": "Topic 20 - Observations, measurements and samples" + "@value": "InfraGML 1.0: Part 1 – LandInfra Land Features - Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines a conceptual schema for observations, for features involved in the observation process, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities.\r\n\r\nObservations commonly involve sampling of an ultimate feature-of-interest. This document defines a common set of sample types according to their spatial, material (for ex situ observations) or statistical nature. The schema includes relationships between sample features (sub-sampling, derived samples).\r\n\r\nThis document concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation." + "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 1 addresses the LandFeature Requirements Class from LandInfra." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63542,35 +63701,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-082r4" + "@value": "16-101r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 20 - Observations, measurements and samples" + "@value": "OGC InfraGML 1.0: Part 1 – LandInfra Land Features - Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-028r2", + "@id": "http://www.opengis.net/def/docs/09-076r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-15" + "@value": "2009-09-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Guy Schumann" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -63580,27 +63739,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-028r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=35042" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-028r2" + "@value": "Uses and summary of Topic 02 - Spatial referencing by coordinates" }, { "@language": "en", - "@value": "WMS QoSE Engineering Report" + "@value": "09-076r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Quality of Service (QoS) and Quality of Experience (QoE) as they are intended and described at the OGC are two related concepts which require very specific treatment and characterization. Citing the definitions provided by the Domain Working Group (DWG) charter document:\r\n\r\nQuality of Service: Technical reliability and performance of a network service. Typically measured using metrics like error rates, throughput, availability and delay or request response time. This Engineering Report (ER) attempts to handle QoS aspects such as service availability, scalability and speed.\r\n\r\nQuality of (User) Experience: A holistic, qualitative measure of the customers' experience of the application or service. It encompasses both the user experience and the customer support experience of the evaluated applications and/or services.\r\n\r\nQoE focuses on the usability of the information that is conceived via OGC services to end users or other client application and therefore is concerned more with qualitative aspects of such services like presence of metadata, proper and descriptive namings, appropriate styling and so on (a more thorough treatment is present in the QoE discussion paper OGC 17-049 entitled Ensuring Quality of User Experience with OGC Web Mapping Services available at https://portal.ogc.org/files/?artifact_id=74403&version=1).\r\n\r\nQoS focuses on providing reliable (i.e. quantitative ) measures of spatial data service metrics which can be used to characterize how a service ( one or more specific datasets exposed by a certain service) is performing both in near real-time as well as historically. It touches concepts like availability, scalability (also known as capacity), absolute performance (i.e. speed) and can be used to assess also perceived performance by final clients. As mentioned above, it is typically measured using metrics like error rates, throughput, availability and delay or request response time.\r\n\r\nQuite often the QoS and QoE aspects of spatial data services are underestimated if not simply ignored due to lack of resources as well as lack of awareness, resulting in services which are difficult to exploit (i.e. QoE very low) and/or unstable or very slow (i.e. QoS very low). The result is that few users end up using them after the initial launch and this is especially true for services targeting end users who are used to interact with services a-la Google Maps which delivers extreme performance and scalability as well as bullet-proof usability.\r\n\r\n" + "@value": "This document first discusses the uses for data sharing, and then provides a brief summary, of OGC Abstract Specification Topic 2: Spatial referencing by coordinates. Topic 2 is almost the same as ISO 19111:2007, but includes some corrections. This document includes some best practices for using Coordinate Reference Systems (CRSs)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63611,55 +63770,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-028r2" + "@value": "09-076r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: WMS QoSE Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/ug", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/22-000" - }, - { - "@id": "http://www.opengis.net/def/docs/20-066" - }, - { - "@id": "http://www.opengis.net/def/docs/20-071" - }, - { - "@id": "http://www.opengis.net/def/docs/21-074" - }, - { - "@id": "http://www.opengis.net/def/docs/21-075" + "@value": "Uses and summary of Topic 2 - Spatial referencing by coordinates" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-001", + "@id": "http://www.opengis.net/def/docs/09-102r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-14" + "@value": "2021-02-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó, Guillem Closa Yolanda Gil and Benjamin Proß" + "@value": "DGIWG" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -63669,27 +63808,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=58967" + "@id": "https://portal.ogc.org/files/94151" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 10 Provenance Engineering Report" + "@value": "09-102r3" }, { "@language": "en", - "@value": "14-001" + "@value": "Defence Profile of OGC Web Map Service 1.3 Revision" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The provenance activities reported in this document were part of the OGC Testbed 10\r\nCross Community Interoperability (CCI) thread. This OGC® document gives guidelines\r\nfor the capture and documentation of provenance information at dataset, feature and\r\nattribute level. It only considers vector features (mainly, points and lines) and does not\r\nelaborate on the coverage data model (so it does not talk about provenance of raster\r\ninformation). It proposes an approach to use the W3C PROV standard with geospatial\r\ninformation that can come from different sources and are integrated through different\r\nprocessing steps. It also reviews the applicability of ISO19115 and ISO19115-2 lineage." + "@value": "This document defines specific DGIWG requirements,\r\nrecommendations and guidelines for implementations of the\r\nISO and OGC Web Map Service standards; ISO 19128:2005\r\nWeb Map Server Interface and the OpenGIS Web Map Server\r\nImplementation Specification 1.3.0." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63700,35 +63839,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-001" + "@value": "09-102r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 10 Provenance Engineering Report" + "@value": "Defence Profile of OGC Web Map Service 1.3 Revision" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-024", + "@id": "http://www.opengis.net/def/docs/17-069r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-11" + "@value": "2019-10-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Pedro Gonçalves" + "@value": "Clemens Portele, Panagiotis (Peter) A. Vretanos, Charles Heazel" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -63738,27 +63877,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-024.html" + "@id": "https://docs.ogc.org/is/17-069r3/17-069r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-024" + "@value": "OGC API - Features - Part 1: Core" }, { "@language": "en", - "@value": "Testbed-13: Application Deployment and Execution Service Engineering Report" + "@value": "17-069r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Testbed-13 Earth Observation Clouds (EOC) effort supports the development of ESA’s Thematic Exploitation Platforms (TEP) by exercising envisioned workflows for data integration and processing that are deployed in multiple clouds. The Application Deployment & Execution Service OGC Engineering Report (ER) identifies the Application Programming Interface (API) for delivering all functionality provided to realize the testbed scenario.\r\n\r\nThis ER will list the requirements fulfilled by Cloud APIs in order to allow an automation of the application package deployment and execution workflow and capture implementation process experiences.\r\n\r\n" + "@value": "OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks.\r\n\r\nThe OGC API family of standards is organized by resource type. This standard specifies the fundamental API building blocks for interacting with features. The spatial data community uses the term 'feature' for things in the real world that are of interest." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63769,30 +63908,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-024" + "@value": "17-069r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: Application Deployment and Execution Service Engineering Report" + "@value": "OGC API - Features - Part 1: Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-068r3", + "@id": "http://www.opengis.net/def/docs/05-008c1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-04-18" + "@value": "2005-05-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff de La Beaujardiere" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -63807,17 +63946,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1081&format=pdf" + "@id": "https://portal.ogc.org/files/?artifact_id=8798" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Map Service" + "@value": "05-008c1" }, { "@language": "en", - "@value": "01-068r3" + "@value": "Web Service Common Implementation Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -63827,7 +63966,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Provides three operations protocols (GetCapabilities, GetMap, and GetFeatureInfo) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. " + "@value": "This document specifies many of the aspects that are, or should be, common to all or multiple OWS interface Implementation Specifications. Those specifications currently include the Web Map Service (WMS), Web Feature Service (WFS), and Web Coverage Service (WCS). These common aspects include: operation request and response contents; parameters included in operation requests and responses; and encoding of operation requests and responses." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63838,35 +63977,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-068r3" + "@value": "05-008c1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Map Service" + "@value": "OpenGIS Web Service Common Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-028", + "@id": "http://www.opengis.net/def/docs/16-009r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-08" + "@value": "2017-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Benjamin Pross, Christoph Stasch" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -63876,27 +64015,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-028.html" + "@id": "https://portal.ogc.org/files/?artifact_id=72717" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-13:Asynchronous Services ER" + "@value": "16-009r3" }, { "@language": "en", - "@value": "17-028" + "@value": "Volume 6: OGC CDB Rules for Encoding Data using OpenFlight" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The goal of this ER is to summarize and compare the results from the activities dealing with asynchronous WFS responses in Testbed 13. Special focus will be given to the specific requirement for automatic notification of users if new or updated information becomes available and to the software components addressing these requirements, i.e. two asynchronous Web Feature Services (NG119 and NG120)." + "@value": "This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of that document for a general overview." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63907,30 +64046,38 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-028" + "@value": "16-009r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: Asynchronous Services ER" + "@value": "Volume 6: OGC CDB Rules for Encoding Data using OpenFlight" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-038r1", + "@id": "http://www.opengis.net/def/doc-type/rfc", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/03-081r2" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/18-083", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "0000-00-00" + "@value": "2019-02-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mark Hughes" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -63945,17 +64092,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=58117" + "@id": "https://docs.ogc.org/per/18-083.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-038r1" + "@value": "18-083" }, { "@language": "en", - "@value": "Testbed 10 Engineering Report: Aviation Dissemination of Weather Data" + "@value": "WMTS Vector Tiles Extension Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -63965,7 +64112,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC document provides an analysis of the mapping between the NOAA Web Gridded Document Service (WGDS) and the OGC Web Coverage Service (WCS) and describes an adapter which translates WCS 2.0 requests to WGDS requests and then translates WGDS responses to WCS 2.0 responses.\r\nThis Engineering Report was prepared as a deliverable for the OGC Testbed 10 (Testbed-10) initiative, specifically the Testbed 10 Aviation Thread.\r\n" + "@value": "The tiling of feature data is an approach that can be used to optimize the delivery vector feature data over the web to create maps. The approach provides a pre-defined shape (i.e. tile) to package vector data. Tiling of vector data enables faster map loads (due to reduced size) and offer flexible styling on the client side with modern, easy-to-use tools.\r\n\r\nThis Engineering Report (ER) describes the work done by participants during the Vector Tiles Pilot (VTP) to add Mapbox and GeoJSON vector tile support to Web Map Tile Servers. A summary of other work done in the VTP is presented in the VTP Summary Engineering Report [1].\r\n\r\nNOTE\r\nThis engineering report interchangeably uses both 'tiled feature data' and the colloquial term 'vector tiles'." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -63976,35 +64123,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-038r1" + "@value": "18-083" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 10 Engineering Report: Aviation Dissemination of Weather Data" + "@value": "OGC Vector Tiles Pilot: WMTS Vector Tiles Extension Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-102r3", + "@id": "http://www.opengis.net/def/docs/20-030", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-25" + "@value": "2020-10-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "DGIWG" + "@value": "Timothy Miller and Gil Trenum" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -64014,27 +64161,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/94151" + "@id": "https://docs.ogc.org/per/20-030.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-102r3" + "@value": "20-030" }, { "@language": "en", - "@value": "Defence Profile of OGC Web Map Service 1.3 Revision" + "@value": "OGC API - Tiles - 3D (GeoVolumes) Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines specific DGIWG requirements,\r\nrecommendations and guidelines for implementations of the\r\nISO and OGC Web Map Service standards; ISO 19128:2005\r\nWeb Map Server Interface and the OpenGIS Web Map Server\r\nImplementation Specification 1.3.0." + "@value": "This Engineering Report documents the draft specification for a three-dimensional (3D) geodata Application Programming Interface (API) that organizes access to a variety of 2D / 3D datasets and their distributions according to a nested hierarchy of 3D geospatial volumes (GeoVolumes). The GeoVolumes (initially Tiles-3D / 3D Container) API specification is consistent with OGC API - Common and supports both link-follow and bbox query methods of access to resources of interest." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64045,35 +64192,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-102r3" + "@value": "20-030" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Defence Profile of OGC Web Map Service 1.3 Revision" + "@value": "OGC API - Tiles - 3D (GeoVolumes) Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-027", + "@id": "http://www.opengis.net/def/docs/07-067r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-04-08" + "@value": "2007-08-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jérôme Jacovella-St-Louis" + "@value": "Arliss Whiteside, John Evans" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -64083,60 +64230,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-027.html" + "@id": "https://portal.ogc.org/files/?artifact_id=22560" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: Geo Data Cube API Engineering Report" + "@value": "07-067r2" }, { "@language": "en", - "@value": "21-027" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ - { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "This OGC Testbed 17 Engineering Report (ER) documents the results and recommendations of the Geo Data Cube API task. The ER defines a draft specification for an interoperable Geo Data Cube (GDC) API leveraging OGC API building blocks, details implementation of the draft API, and explores various aspects including data retrieval and discovery, cloud computing and Machine Learning. Implementations of the draft GDC API are demonstrated with use cases including the integration of terrestrial and marine elevation data and forestry information for Canadian wetlands.\r\n\r\n" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ - { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-027" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@language": "en", - "@value": "OGC Testbed-17: Geo Data Cube API Engineering Report" + "@value": "Web Coverage Service (WCS) Implementation Specification Corrigendum 1" } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/notes/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@value": "Documents of type Release Notes" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Documents of type Release Notes" + "@value": "This version 1.1.1c1 of the Web Coverage Service (WCS) Specification supersedes previous\r\nversion 1.1.0 [OGC 06-083r8]. Technical changes from the version 1.0 include building on\r\nthe OGC Web Services Common Specification [OGC 06-121r3] and a substantially revised\r\nCapabilities schema; new schemas and syntax for operation requests (GetCoverage,\r\nDescribeCoverage); and integration with GML 3.1. The changes in WCS 1.1.1c1 from WCS\r\n1.1.0 are summarized in [OGC 07-066r2]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64144,84 +64258,38 @@ "@id": "http://www.opengis.net/def/docs" } ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/18-066r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-126r8" - }, - { - "@id": "http://www.opengis.net/def/docs/21-004" - }, - { - "@id": "http://www.opengis.net/def/docs/19-034r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-123r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-044" - }, - { - "@id": "http://www.opengis.net/def/docs/18-016r1" - }, - { - "@id": "http://www.opengis.net/def/docs/18-024r1" - }, - { - "@id": "http://www.opengis.net/def/docs/21-066r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-066r5" - }, - { - "@id": "http://www.opengis.net/def/docs/20-006" - }, - { - "@id": "http://www.opengis.net/def/docs/23-018r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-111" - }, - { - "@id": "http://www.opengis.net/def/docs/10-099r2" - }, - { - "@id": "http://www.opengis.net/def/docs/22-032r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-052" - }, + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/07-061" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "07-067r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type Release Notes" + "@language": "en", + "@value": "OpenGIS Web Coverage Service (WCS) Implementation Specification Corrigendum 1" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-010", + "@id": "http://www.opengis.net/def/docs/16-045r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-01-26" + "@value": "2017-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Daniel Balog, Robin Houtmeyers" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -64231,27 +64299,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8814" + "@id": "https://docs.ogc.org/per/16-045r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-010" + "@value": "16-045r2" }, { "@language": "en", - "@value": "URNs of definitions in ogc namespace" + "@value": "Testbed-12 Data Broker Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*** Superceded by 06-023r1 - Definition identifier URNs in OGC namespace ***\r\nThis Recommendation Paper specifies Universal Resource Names (URNs) for definitions in the " + "@value": "An important principle of a Service Oriented Architecture (SOA) is the notion of composing capabilities provided by individual services into complex behavior. A requester should be able to compose a solution using functionality or data offered by multiple services without worrying about underlying differences in those services.\r\n\r\nEach OGC service is designed to offer a specific type of data product via a service-specific interface. This Engineering Report (ER) describes a single service interface that allows access to multiple data sources, possibly heterogeneous with respect to the types of data provided.\r\n\r\nThis report advances the work started in OGC Testbed 11 with the addition of heterogeneous data sources, as well as several other enhancements." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64262,35 +64330,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-010" + "@value": "16-045r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "URNs of definitions in ogc namespace" + "@value": "Testbed-12 Data Broker Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-024r1", + "@id": "http://www.opengis.net/def/docs/07-028r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-18" + "@value": "2007-05-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -64300,27 +64368,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/18-024r1" + "@id": "https://portal.ogc.org/files/?artifact_id=21628" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-024r1" + "@value": "07-028r1" }, { "@language": "en", - "@value": "Release Notes for OGC GeoPackage Encoding Standard v1.2.1" + "@value": "GEOINT Structure Implementation Profile Schema Processing" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the set of revision notes for the existing GeoPackage version 1.2.1 (OGC 12-128r15) and does not modify that standard.\r\n\r\nThis document was approved by the OGC membership on approval date. As a result of the OGC Standards Working Group (SWG) process, there were a number of edits and enhancements made to this standard. This document provides the details of those edits, deficiency corrections, and enhancements. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility." + "@value": "This document contains a description of the schema tailoring process for application schema development based on the U.S. National System for Geospatial-Intelligence (NSG) GEOINT Structure Implementation Profile (GSIP) as developed in conjuction with the Open Geospatial Consortium Interoperability Program initiative OWS-4." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64331,46 +64399,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-024r1" + "@value": "07-028r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Release Notes for OGC GeoPackage Encoding Standard v1.2.1" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/ipr", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/02-019r1" - }, - { - "@id": "http://www.opengis.net/def/docs/02-028" + "@value": "GEOINT Structure Implementation Profile Schema Processing" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-042", + "@id": "http://www.opengis.net/def/docs/16-008r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-04-28" + "@value": "2017-01-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Daniele Marchionni" + "@value": "GeoSciML Modeling Team " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -64380,27 +64437,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55209" + "@id": "https://docs.ogc.org/is/16-008/16-008r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "13-042" + "@value": "16-008r1" }, { "@language": "en", - "@value": "RESTful Encoding of Ordering Services Framework For Earth Observation Products" + "@value": "Geoscience Markup Language 4.1 (GeoSciML) - with Corrigendum" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Best Practices document specifies the interfaces, bindings, requirements, conformance classes that enable complete workflows for ordering Earth Observation (EO) data products. In fact it provides the interfaces for supporting the following EO Product ordering scenarios:\r\n•\tOrdering products from EO Catalogues\r\n•\tSubscribing to automatic delivery of EO products\r\n•\tBulk EO Product orders\r\nThe EO products orders can be delivered on file via different online protocols (e.g. ftp, sftp, ftps, etc.).\r\n" + "@value": "GeoSciML is a model of geological features commonly described and portrayed in geological maps, cross sections, geological reports and databases. The model was developed by the IUGS CGI (Commission for the Management and Application of Geoscience Information) and version 4.1 is the first version officially submitted as an OGC standard. This specification describes a logical model and GML/XML encoding rules for the exchange of geological map data, geological time scales, boreholes, and metadata for laboratory analyses. It includes a Lite model, used for simple map-based applications; a basic model, aligned on INSPIRE, for basic data exchange; and an extended model to address more complex scenarios. \r\n\r\nThe specification also provides patterns, profiles (most notably of Observations and Measurements - ISO19156), and best practices to deal with common geoscience use cases. \r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64411,35 +64468,46 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-042" + "@value": "16-008r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC RESTful Encoding of Ordering Services Framework For Earth Observation Products" + "@value": "OGC Geoscience Markup Language 4.1 (GeoSciML) - with Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-046r5", + "@id": "http://www.opengis.net/def/doc-type/d-sap", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/09-146r1" + }, + { + "@id": "http://www.opengis.net/def/docs/02-058" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/22-041", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-10-31" + "@value": "2023-08-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox, Gobe Hobona" + "@value": "Leigh St. Hilaire, Aidan Brookson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pol" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -64449,27 +64517,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/pol/09-046r5.html" + "@id": "https://docs.ogc.org/per/22-041.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-046r5" + "@value": "22-041" }, { "@language": "en", - "@value": "OGC Naming Authority – Policies and Procedures " + "@value": "Testbed-18: Building Energy Data Interoperability Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pol" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the procedures used by the OGC Naming Authority for the assignment and registration of OGC names." + "@value": "This OGC Testbed-18 Engineering Report (ER) represents deliverable D012 and D013 for the Building Energy Data Interoperability task." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64480,30 +64548,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-046r5" + "@value": "22-041" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Naming Authority – Policies and Procedures " + "@value": "Testbed-18: Building Energy Data Interoperability Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-133", + "@id": "http://www.opengis.net/def/docs/18-090r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-08-22" + "@value": "2019-03-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Hudson" + "@value": "Dr. Craig A. Lee" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -64518,17 +64586,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51178" + "@id": "https://docs.ogc.org/per/18-090r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Services Facade for OGC IP Engineering Report" + "@value": "Federated Clouds Engineering Report" }, { "@language": "en", - "@value": "12-133" + "@value": "18-090r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -64538,7 +64606,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the Web Services Façade which was developed by LISAsoft as part of the OWS-9 testbed. The document also includes discussions about lessons learned during the development, and suggestions for future development.\r\nThis Engineering Report documents the Web Services Façade work done within OWS-9 as an extensible, open source tool, which supports translations between different protocols for a specific web service. For the OWS-9 testbed, it has been set up to translate between POST and SOAP services for a Web Feature Service. However, it can be configured to support translations between multiple protocols, such as REST, SOAP, KVP, JSON, as well as supporting multiple web services.\r\nThe Web Services Façade is an extensible, open source tool, which supports translations between different protocols for a specific web service. For the OWS-9 testbed, it has been set up to translate between POST and SOAP services for a Web Feature Service. However, it can be configured to support translations between multiple protocols, such as REST, SOAP, KVP, JSON, as well as supporting multiple web services.\r\n" + "@value": "The geospatial community has had an on-going challenge with being able to share data and compute resources in dynamic, collaborative environments that span different administrative domains. For these types of requirements, the concept of federation has been developed. The near-term goal of the Federated Cloud task in OGC Testbed-14 is to demonstrate a specific data-sharing scenario among two or more administrative domains using existing security tooling, e.g., OpenID Connect and OAuth. The main details of this work are reported as part of the OGC Testbed-14 Security Engineering Report (ER) cite:[SecurityER]. This Federated Cloud Engineering Report (ER) dovetails with the Security ER to:\r\n\r\nCoordinate across all federation-related tasks in Testbed-14, including the Earth Observation Cloud and Workflow tasks,\r\n\r\nUnderstand the overall federation design space,\r\n\r\nAnalyze and critique the scope, trade-offs and limitations of the federation capabilities being built and demonstrated in Testbed-14,\r\n\r\nIdentify and prioritize possible incremental development tasks for subsequent testbeds, and\r\n\r\nLiaison with groups external to OGC, such as the National Institute of Standards and Technology (NIST)/Institute of Electrical and Electronics Engineers (IEEE) Joint Working Group on Federated Cloud, to promote the further development and adoption of federated capabilities, and ultimately international standards.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64549,35 +64617,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-133" + "@value": "18-090r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Services Facade for OGC IP Engineering Report" + "@value": "OGC Testbed-14: Federated Clouds Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-086r1", + "@id": "http://www.opengis.net/def/docs/13-082r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-08-18" + "@value": "2016-01-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andrew Turner" + "@value": "Joan Masó" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -64587,27 +64655,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40334" + "@id": "https://docs.ogc.org/is/13-082r2/13-082r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-086r1" + "@value": "13-082r2" }, { "@language": "en", - "@value": "OWS-7 - Authoritative Data Source Directory Engineering Report" + "@value": "Web Map Tile Service (WMTS) Simple Profile" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document presents the Authoritative Data Source Directory (ADSD) engineering suggestions and results of the OGC OWS-7 ADSD thread. This group focused on creating a workflow for geospatially referencing, finding, and federating data sources with associated authority and relevance." + "@value": "The Web Map Tile Service (WMTS) Simple profile defines restrictions that limit the flexibility in implementing a WMTS instance. Adding additional requirements has the goal of simplifying the creation of services and clients. By implementing this profile, clients can more easily combine data coming from different services including from other WMTS instances and even from some tile implementations that are not OGC WMTS based, such as some current distributions of OSM. In fact, most of these tiling services are implicitly following most of the WMTS requirements. Many current WMTS services that implement this profile will have to undergo some changes on how tiles are exposed, and a client that is compatible with WMTS 1.0 will be immediately compatible with this profile. The aim is to align the WMTS standard to other popular tile initiatives which are less flexible but widely adopted." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64618,35 +64686,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-086r1" + "@value": "13-082r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-7 - Authoritative Data Source Directory Engineering Report" + "@value": "OGC® Web Map Tile Service (WMTS) Simple Profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-057r2", + "@id": "http://www.opengis.net/def/docs/11-036", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-10-10" + "@value": "2011-04-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Keith Pomakis" + "@value": "Lance McKee, Carl Reed, Steven Ramage" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -64656,27 +64724,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=23206" + "@id": "https://portal.ogc.org/files/?artifact_id=43743" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Tiled WMS Discussion Paper" + "@value": "OGC Standards and Cloud Computing" }, { "@language": "en", - "@value": "07-057r2" + "@value": "11-036" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Tiled Web Map Service Discussion Paper explains how the OpenGIS Web Map Service Standard (WMS) [http://www.opengeospatial.org/standards/wms] can be extended to allow fast response to a predefined set of tiled maps. It should be read in conjunction with the latest version WMS standard.\r\n" + "@value": "This OGC White Paper discusses cloud computing from the perspective of OGC’s\r\ngeospatial standards development activities and standards baseline. The paper begins\r\nwith a discussion of what the cloud and cloud computing are. Unfortunately, there is still\r\nconsiderable misunderstanding in the geospatial technology community regarding cloud\r\ncomputing. The paper then discusses how standards figure into the options, benefits and\r\nrisks of cloud computing for users and providers of geospatial data and software. This\r\nperspective is important not only for those immersed in geospatial technology, but also for\r\ncloud service providers, customers and technology partners who may be unfamiliar with\r\nthe basic issues surrounding geospatial technology. This white paper does not discuss\r\nvendor specific cloud computing platforms." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64687,35 +64755,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-057r2" + "@value": "11-036" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Tiled WMS Discussion Paper" + "@value": "OGC Standards and Cloud Computing" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-049r1", + "@id": "http://www.opengis.net/def/docs/12-031r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-16" + "@value": "2012-07-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó" + "@value": "Doug Palmer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -64725,27 +64793,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-049r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=49025" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Multi-Tile Retrieval ER" + "@value": "12-031r2" }, { "@language": "en", - "@value": "16-049r1" + "@value": "WaterML 2.0 - Timeseries - NetCDF Discussion Paper" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "With the consolidation of tiling services and the increasing number of instances implementing the WMTS standard, there is a need for having a way to transfer a collection of tiles from one service to another. This might also be useful to transfer all necessary tiles from a WMTS service to a GeoPackage. Currently the only available solution is a client that is able to resolve the identifiers of the tiles needed and that builds a WMTS independent request for each tile. This ER explores different solutions that are more appropriate depending on how many tiles we need to move and the final application of them. Some of the proposed solutions involve changes in the WMTS standard and the use of a WPS. The WPS standard also shows some limitations and extensions that should be addressed.\r\n\r\nIn essence all solutions should describe two things: A request that contains a filter to a collection of tiles filling regions of the space and a multipart response that contains the tiles preferably in a single package. Depending on the proposed architecture, these tasks are done directly in the client, in the WMTS server or in an intermediate WPS." + "@value": "This discussion paper investigates the possible uses of NetCDF as a representation of WaterML timeseries data. The work is largely based on the WaterML 2.0 standard for timeseries, the NetCDF core and extensions standards and the CF-NetCDF and ADCC conventions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64756,35 +64824,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-049r1" + "@value": "12-031r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Multi-Tile Retrieval ER" + "@value": "WaterML 2.0 - Timeseries - NetCDF Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-029r4", + "@id": "http://www.opengis.net/def/docs/14-005r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-08-29" + "@value": "2014-12-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ron Lake, Carl Reed, George Percivall" + "@value": "Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -64794,27 +64862,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=11606" + "@id": "https://docs.ogc.org/is/14-005r3/14-005r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GML Point Profile" + "@value": "IndoorGML" }, { "@language": "en", - "@value": "05-029r4" + "@value": "14-005r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines a profile of the Geography Markup Language (GML) for a point geometry. Attention is drawn to the fact that this is a profile of GML version 3.1.1. " + "@value": "This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64825,35 +64893,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-029r4" + "@value": "14-005r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML Point Profile" + "@value": "OGC® IndoorGML" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-090r2", + "@id": "http://www.opengis.net/def/docs/00-115", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-10-23" + "@value": "2000-04-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Craig A. Lee" + "@value": "Cliff Kottman, Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -64863,27 +64931,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-090r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=7199" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-090r2" + "@value": "00-115" }, { "@language": "en", - "@value": "Testbed-14: Federated Clouds Engineering Report" + "@value": "Topic 15 - Image Exploitation Services" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The geospatial community has had an on-going challenge with being able to share data and compute resources in dynamic, collaborative environments that span different administrative domains. For these types of requirements, the concept of federation has been developed. The near-term goal of the Federated Cloud task in Testbed-14 is to demonstrate a specific data-sharing scenario among two or more administrative domains using existing security tooling, e.g., OpenID Connect and OAuth. The main details of this work are reported as part of the Security Engineering Report (ER) [1]. This Federated Cloud ER will dovetail with the Security ER to:\r\n\r\nCoordinate across all federation-related tasks in Testbed-14, including the Earth Observation Cloud and Workflow tasks,\r\n\r\nUnderstand the overall federation design space,\r\n\r\nAnalyze and critique the scope, trade-offs and limitations of the federation capabilities being built and demonstrated in Testbed-14,\r\n\r\nIdentify and prioritize possible incremental development tasks for subsequent testbeds, and\r\n\r\nLiaison with groups external to OGC, such as the NIST/IEEE Joint WG on Federated Cloud, to promote the further development and adoption of federated capabilities, and ultimately international standards." + "@value": "Describes the categories and taxonomy of image exploitation services needed to support the use of images and certain related coverage types." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64894,35 +64962,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-090r2" + "@value": "00-115" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Federated Clouds Engineering Report" + "@value": "Topic 15 - Image Exploitation Services" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-086r3", + "@id": "http://www.opengis.net/def/docs/10-059r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-04-05" + "@value": "2010-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jürgen Seib, Marie-Françoise Voidrot-Martinez, Chris Little" + "@value": "Christian Kiehle, Theodor Foerster" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -64932,27 +65000,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/16-086r3/16-086r3.html" + "@id": "https://portal.ogc.org/files/?artifact_id=40310" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-086r3" + "@value": "OWS-7 Web Processing Service Profiling Engineering Report" }, { "@language": "en", - "@value": "Best Practice for using Web Map Services (WMS) with Ensembles of Forecast Data" + "@value": "10-059r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document proposes a set of best practices and guidelines for implementing and using the Open Geospatial Consortium (OGC) Web Map Service (WMS) to serve maps which are members of an ensemble of maps, each of which is a valid possible alternative for the same time and location. In the meteorological and oceanographic communities, it is Best Practice to produce a large number of simultaneous forecasts, whether for a short range of hours, a few days, seasonal or climatological predictions. These ensembles of forecasts indicate the probability distributions of specific outcomes. This document describes how to unambiguously specify an individual member of an ensemble, or one of a limited set of map products derived from a full ensemble. \r\nIn particular, clarifications and restrictions on the use of WMS are defined to allow unambiguous and safe interoperability between clients and servers, in the context of expert meteorological and oceanographic usage and non-expert usage in other communities. This Best Practice document applies specifically to WMS version 1.3, but many of the concepts and recommendations will be applicable to other versions of WMS or to other OGC services, such as the Web Coverage Service.\r\n" + "@value": "The overall scope of this OWS-7 Engineering Report is to clarify how to write and register a WPS profile. WPS profiles enable clients to search and identify equivalent WPS-based processes distributed on the web. Therefore, this ER provides guidelines for designing WPS Profiles based on WPS interface specification 1.0.0." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -64963,35 +65031,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-086r3" + "@value": "10-059r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Best Practice for using Web Map Services (WMS) with Ensembles of Forecast Data" + "@value": "OWS-7 Web Processing Service Profiling Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-095r1", + "@id": "http://www.opengis.net/def/docs/07-113r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-18" + "@value": "2007-11-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Google, Galdos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/profile" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65001,27 +65069,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13204" + "@id": "https://portal.ogc.org/files/?artifact_id=23689" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-095r1" + "@value": "07-113r1" }, { "@language": "en", - "@value": "GML 3.1.1 common CRSs profile" + "@value": "KML 2.2 Reference - An OGC Best Practice" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/profile" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding definitions of commonly-used Coordinate Reference Systems (CRSs) plus related coordinate Conversions." + "@value": "KML is a file format used to display geographic data in an Earth browser, such as Google Earth, Google Maps, and Google Maps for Mobile. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65032,43 +65100,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-095r1" + "@value": "07-113r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML 3.1.1 common CRSs profile" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-per", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/22-020" + "@value": "KML 2.2 Reference - An OGC Best Practice" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-112", + "@id": "http://www.opengis.net/def/docs/14-044", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-10-13" + "@value": "2015-02-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Jirka, Arne Bröring" + "@value": "Lew Leinenweber" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65078,27 +65138,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=35471" + "@id": "https://portal.ogc.org/files/?artifact_id=61108" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-112" + "@value": "14-044" }, { "@language": "en", - "@value": "Sensor Observable Registry Discussion Paper" + "@value": "Testbed 10 Summary Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion paper introduces the Sensor Observable Registry (SOR), a web service interface for managing the definitions of phenomena measured by sensors as well as exploring semantic relationships between these phenomena." + "@value": "The OGC Testbed 10 was an initiative of OGC’s Interoperability Program to collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. The majority of work for Testbed 10 was conducted between October 2013 and April 2014." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65109,35 +65169,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-112" + "@value": "14-044" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Observable Registry Discussion Paper" + "@value": "OGC® Testbed 10 Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-025r3", + "@id": "http://www.opengis.net/def/docs/19-004", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-10-24" + "@value": "2019-12-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Richard Martell" + "@value": "Kyoung-Sook Kim, Jiyeong Lee" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65147,27 +65207,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12604" + "@id": "https://docs.ogc.org/dp/19-004.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-025r3" + "@value": "Anchor Node Extension in IndoorGML - Seamless Navigation between Indoor and Outdoor Space" }, { "@language": "en", - "@value": "Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW" + "@value": "19-004" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Catalogue Services 2.0 specification (OGC 04-021r3) establishes a general framework for implementing catalogue services that can be applied to meet the needs of stakeholders in a wide variety of domains. This application profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0 specification; it qualifies as a Class 2 profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards." + "@value": "This OGC discussion paper provides an extension module of OGC Indoor Geography Markup Language (IndoorGML) for the seamless navigation between indoor and outdoor spaces. The OGC IndoorGML standard has an issue on the data model that affects the connection of indoor and outdoor spaces via an “Anchor Node,” which is a conceptual part for connecting indoor and outdoor spaces. This discussion paper aims to show use cases of how IndoorGML can connect with other geospatial standards that represent outdoor spaces (and road networks), such as OGC City Geography Markup Language (CityGML) and version 5.0 of the Geographic Data Files (GDF) format." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65178,30 +65238,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-025r3" + "@value": "19-004" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW" + "@value": "Anchor Node Extension in IndoorGML - Seamless Navigation between Indoor and Outdoor Space" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-103r3", + "@id": "http://www.opengis.net/def/docs/09-032", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-02-05" + "@value": "2009-07-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona, Roger Brackin" + "@value": "Thomas Everding, Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -65216,17 +65276,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51840" + "@id": "https://portal.ogc.org/files/?artifact_id=33347" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-9 CCI Semantic Mediation Engineering Report" + "@value": "OWS-6 SWE Event Architecture Engineering Report" }, { "@language": "en", - "@value": "12-103r3" + "@value": "09-032" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -65236,7 +65296,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OWS-9 Cross Community Interoperability (CCI) thread built on progress made in the recent OWS-8 initiative by improving interoperability between communities sharing geospatial data through advances in semantic mediation approaches for data discovery, access and use of heterogeneous data models and heterogeneous metadata models. This OGC engineering report aims to present findings from CCI thread activities towards advancement of semantic mediation involving heterogeneous data models, gazetteers and aviation data available through web services conformant to OGC standards.\r\nThis Engineering Report was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Cross Community Interoperability thread within OWS-9.\r\n" + "@value": "The document describes an abstract event architecture for service oriented architectures. Furthermore various techniques for implementing an event architecture and working with events are discussed." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65247,35 +65307,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-103r3" + "@value": "09-032" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-9 CCI Semantic Mediation Engineering Report" + "@value": "OWS-6 SWE Event Architecture Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-002r9", + "@id": "http://www.opengis.net/def/docs/08-015r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-01-18" + "@value": "2010-04-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Craig Bruce" + "@value": "Roger Lott" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65285,27 +65345,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13636" + "@id": "https://portal.ogc.org/files/?artifact_id=39049" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Binary Extensible Markup Language (BXML) Encoding Specification" + "@value": "Topic 2 - Spatial referencing by coordinates" }, { "@language": "en", - "@value": "03-002r9" + "@value": "08-015r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Best Practices document specifies a binary encoding format for the efficient representation of XML data, especially scientific data that is characterized by arrays of numbers. This encoding format is applicable to any application that uses XML format." + "@value": "This document is consistent with the second edition (2007) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2007]" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65316,35 +65376,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-002r9" + "@value": "08-015r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Binary Extensible Markup Language (BXML) Encoding Specification" + "@value": "Topic 2 - Spatial referencing by coordinates" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-080r2", + "@id": "http://www.opengis.net/def/docs/07-018", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-16" + "@value": "2007-05-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jerome Gasperi" + "@value": "Philippe M" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65354,27 +65414,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=22161" + "@id": "https://portal.ogc.org/files/?artifact_id=20583" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-080r2" + "@value": "Sensor Planning Service Application Profile for EO Sensors" }, { "@language": "en", - "@value": "GML Application Schema for EO Products" + "@value": "07-018" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGC" + "@value": "This Discussion Paper explains how a Sensor Planning Service is organised and implemented for the Earth Observation domain." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65385,35 +65445,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-080r2" + "@value": "07-018" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML Application Schema for EO Products" + "@value": "OpenGIS Sensor Planning Service Application Profile for EO Sensors" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-041r1", + "@id": "http://www.opengis.net/def/docs/18-053r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-30" + "@value": "2019-01-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ilya Zaslavsky, David Valentine, Tim Whiteaker" + "@value": "Patrick Cozzi, Sean Lilley, Gabby Getz" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65423,27 +65483,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21743" + "@id": "https://docs.ogc.org/cs/18-053r2/18-053r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-041r1" + "@value": "18-053r2" }, { "@language": "en", - "@value": "CUAHSI WaterML" + "@value": "3D Tiles Specification 1.0" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the initial version of the WaterML messaging schema as implemented in version 1 of WaterOneFlow web services. It also lays out strategies for harmonizing WaterML with OGC specifications, the Observations and Measurement specification in particular." + "@value": "3D Tiles is designed for streaming and rendering massive 3D geospatial content such as Photogrammetry, 3D Buildings, BIM/CAD, Instanced Features, and Point Clouds. It defines a hierarchical data structure and a set of tile formats which deliver renderable content. 3D Tiles does not define explicit rules for visualization of the content; a client may visualize 3D Tiles data however it sees fit.\r\n\r\nA 3D Tiles data set, called a tileset, contains 3D data organized into a spatial data structure. The primary format for delivering the 3D data is glTF 2.0. Additional formats for geospatial tile data are also specified in this document. These tile formats include Batched 3D Models, Instanced 3D Models, Point Clouds and Composite tiles.\r\n\r\nThis document specifies the following elements of a tileset:\r\n\r\nThe core data structures for tilesets\r\nTile formats for delivering 3D data\r\nAn implicit representation of tilesets that are organized in quadtrees or octrees\r\nMetadata that may be associated to elements of a tileset on different levels of granularity\r\nDeclarative styling which may be applied to tilesets for their visualization\r\nThe 3D Tiles specification for tilesets, associated tile formats, metadata, and the associated styling specification are open formats that are not dependent on any vendor-specific solution, technology, or products.\r\n\r\nThe majority of the content in this OGC document is a direct copy of the content contained at the 1.1 tag of the 3d-tiles repo. No normative changes have been made to the content. This OGC document does contain content not contained in the 1.1 tag of the 3d-tiles repo.\r\n\r\nCesium has published the 3D Tiles 1.1 Reference Card as an approachable and concise guide to learning about the main concepts in 3D Tiles, intended to jumpstart developers in adopting 3D Tiles." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65454,35 +65514,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-041r1" + "@value": "18-053r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CUAHSI WaterML" + "@value": "OGC 3D Tiles Specification 1.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-112r3", + "@id": "http://www.opengis.net/def/docs/07-163", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-19" + "@value": "2008-05-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "David Rosinger, Stan Tillman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65492,27 +65552,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/15-112r3" + "@id": "https://portal.ogc.org/files/?artifact_id=27330" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Volume 3: OGC CDB Terms and Definitions" + "@value": "07-163" }, { "@language": "en", - "@value": "15-112r3" + "@value": "Data View Architecture Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice." + "@value": "This OGC document presents a summary of the Data View Architecture experiment conducted as part of the Geo-Processing Workflow (GPW) thread in the OWS-5 test bed. The main activities in this experiment were the storage of Data Views in an ebRIM Catalog and the discovery and use of those Data Views by an Integrated Client." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65523,35 +65583,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-112r3" + "@value": "07-163" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 3: OGC CDB Terms and Definitions" + "@value": "OWS-5 Data View Architecture Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-101", + "@id": "http://www.opengis.net/def/docs/05-007r7", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-04-19" + "@value": "2007-10-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Burggraf" + "@value": "Peter Schut" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65561,27 +65621,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13396" + "@id": "https://portal.ogc.org/files/?artifact_id=24151" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS 3 GML Investigations - Performance Experiment by Galdos Systems" + "@value": "05-007r7" }, { "@language": "en", - "@value": "05-101" + "@value": "Web Processing Service" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "In this experiment, the retrieval time of GML features from a Web Feature Service (WFS) to a WFS client will be studied by varying certain control parameters including methods of encoding and compression. Four different control parameters including encoding format, data set size, bandwidth, and feature type will be varied to test the relative performance in each case." + "@value": "The OpenGIS® Web Processing Service (WPS) Interface Standard provides rules for standardizing how inputs and outputs (requests and responses) for geospatial processing services, such as polygon overlay. The standard also defines how a client can request the execution of a process, and how the output from the process is handled. It defines an interface that facilitates the publishing of geospatial processes and clients’ discovery of and binding to those processes. The data required by the WPS can be delivered across a network or they can be available at the server. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65592,35 +65652,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-101" + "@value": "05-007r7" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS 3 GML Investigations - Performance Experiment by Galdos Systems" + "@value": "Web Processing Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-176r1", + "@id": "http://www.opengis.net/def/docs/99-114", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-29" + "@value": "1999-04-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Cliff Kottman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65630,27 +65690,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34273" + "@id": "https://portal.ogc.org/files/?artifact_id=902" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-176r1" + "@value": "Topic 14 - Semantics and Information Communities" }, { "@language": "en", - "@value": "OWS-6 Secure Sensor Web Engineering Report" + "@value": "99-114" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The main purpose of this Engineering Report is to introduce standards-based security solutions for making the existing OGC Sensor Web Services, as described in the OWS-6 SWE baseline, ready towards the handling of sensors in the intelligence domain." + "@value": "The OpenGIS notion of Information Communities was devised to enable groups such as ecologists and civil engineers to efficiently manage the semantics (or feature schema mismatches) of their own geodata collections and get maximum benefit from each other's geodata collections, despite semantic differences." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65661,35 +65721,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-176r1" + "@value": "99-114" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 Secure Sensor Web Engineering Report" + "@value": "Topic 14 - Semantics and Information Communities" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-022", + "@id": "http://www.opengis.net/def/docs/09-104r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-08-19" + "@value": "2010-01-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Arne Schilling, Thomas H. Kolbe" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65699,27 +65759,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=63312" + "@id": "https://portal.ogc.org/files/?artifact_id=36390" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 11 Engineering Report: Implementing Common Security Across the OGC Suite of Service Standards" + "@value": "09-104r1" }, { "@language": "en", - "@value": "15-022" + "@value": "Draft for Candidate OpenGIS® Web 3D Service Interface Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) focuses on describing Common Security for all OGC\r\nWeb Service Standards. This work was performed as part of the OGC Testbed 11\r\nactivity." + "@value": "A Web 3D Service (W3DS) is a portrayal service for three-dimensional geodata, such as landscape models, city models, textured building models, vegetation objects, and street furniture. Geodata is delivered as scenes that are comprised of display elements, optimized for efficient real time rendering at high frame rates." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65730,30 +65790,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-022" + "@value": "09-104r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 11 Engineering Report: Implementing Common Security Across the OGC Suite of Service Standards" + "@value": "Draft for Candidate OpenGIS® Web 3D Service Interface Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-039r1", + "@id": "http://www.opengis.net/def/docs/06-054r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-10-18" + "@value": "2006-07-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roland Wagner" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -65768,17 +65828,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=11500" + "@id": "https://portal.ogc.org/files/?artifact_id=16080" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "02-039r1" + "@value": "Image Geopostioning Service" }, { "@language": "en", - "@value": "Web Pricing and Ordering" + "@value": "06-054r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -65788,7 +65848,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This specification covers all standard geo-eBusiness processes like pricing, ordering and online delivery for spatial products." + "@value": "This document specifies the interface to an Image Geopositioning Service that adjusts the georeferencing coordinate transformations of multiple images. This adjustment is normally done using a photogrammetric triangulation process, although other methods could be used. Such triangulation adjusts the parameter values of the image georeferencing coordinate transformations using a least-squares fitting process to measured image positions with known error statistics." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65799,35 +65859,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-039r1" + "@value": "06-054r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Pricing and Ordering" + "@value": "OpenGIS Image Geopostioning Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-074", + "@id": "http://www.opengis.net/def/docs/99-104", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-08-18" + "@value": "1999-03-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Theodor Foerster, Bastian Schäffer" + "@value": "Cliff Kottman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65837,27 +65897,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40311" + "@id": "https://portal.ogc.org/files/?artifact_id=887" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-7 Feature and Statistical Analysis Engineering Report" + "@value": "99-104" }, { "@language": "en", - "@value": "10-074" + "@value": "Topic 04 - Stored Functions and Interpolation" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) is a deliverable for the OGC Web Service 7 testbed. The focus of this ER is using the OGC Web Processing Service (WPS) interface standard for Feature and Statistical Analysis (FSA). Specifically, the ER documents how to enhance interoperability of FSA processes that are hosted as WPS processes on the Web. This ER is coordinated with the Feature and Decision Fusion (FDF) WPS Profiling ER." + "@value": "This Topic Volume provides essential and abstract models for technology that is used widely across the GIS landscape. Its first heavy use is expected to occur in support of Coverage specifications (see Topic 6, The Coverage Type)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65868,35 +65928,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-074" + "@value": "99-104" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-7 Feature and Statistical Analysis Engineering Report" + "@value": "Topic 4 - Stored Functions and Interpolation" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-068", + "@id": "http://www.opengis.net/def/docs/22-031r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-09-29" + "@value": "2023-01-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Pedro Gonçalves" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65906,27 +65966,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/21-068.pdf" + "@id": "https://docs.ogc.org/per/22-031r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Best Practice for using SensorThings API with Citizen Science" + "@value": "22-031r1" }, { "@language": "en", - "@value": "21-068" + "@value": "Testbed-18: Reproducible FAIR Best Practices Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document introduces an extension to the OGC SensorThings data model and discusses\r\nthe best practices for using such an extension in the context of Citizen Science.\r\nThe motivation for the introduced extension, referred to as “STAplus,” has been developed\r\nduring the EC H2020 project Cos4Cloud and is based on requirements from Citizen Science.\r\nWhereas the dominant use of the OGC SensorThings data model (and API) can be coined\r\nwith the use case “single authority provides sensor readings to consumers”, in Citizen\r\nScience there are many contributors (citizens) that – together – create the big “picture” with\r\ntheir observations.\r\nThe introduced extension STAplus supports the model that those observations are owned by\r\n(different) users that may express the license for re-use; we call this part of the contribution\r\nthe ownership concept. In addition to the ownership and license abilities, the introduced\r\nextension allows to express explicit relations between observations and to create group(s) of\r\nobservations to containerize observations that belong together. Relations can be created\r\namong any individual observations or observations of a group to support performant Linked\r\nData extraction and semantic queries, e.g., expressed in SPARQL.\r\nWe believe that the introduced extension is an important contribution towards the realization\r\nof the FAIR principles, perhaps not only in Citizen Science, as STAplus strengthens the “I”\r\n(Interoperability) through a common data model and API as well as the “R” (Reusability) by\r\nallowing to express standards-based queries that may consider licensing conditions, relevant\r\nfor reuse of other users’ observations. The STAplus Data Model and Business Logic also\r\nenriches existing deployments as the extension can be seamlessly added and thereby offer\r\nnew capabilities to create and manage the “big picture” with multi-user capabilities.\r\nThis document also illustrates best practices of using STAplus, evaluated with proof-ofconcept deployments based on the implementations by 52°North, Secure Dimensions, and\r\nCREAF." + "@value": "The OGC Testbed-18 initiative included a discussion exploring the future of open science and building energy interoperability with the task of developing a set of best practices to make the data processing services of Exploitation Platforms both reproducible and follow the FAIR data principles.\r\n\r\nPortability and reproducibility are key factors for the long-term scientific impact of Earth Observation (EO) data processing applications provided by Exploitations Platforms. The EO application developers lack the tools and guidance to preserve all the elements, algorithms, software, and data resources used to produce the results. Without these elements, reproducibility becomes resubmission within the platform and only while the same platform resources such as data are preserved and available.\r\n\r\nThis Testbed 18 Engineering Report defines a list of requirements and respective best practices to support reproducible Earth Observation science covering the different resources of the Earth Observation Exploitation Platforms such as publications, data, services, products, information, software, or computing environments.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -65937,35 +65997,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-068" + "@value": "22-031r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Best Practice for using SensorThings API with Citizen Science" + "@value": "Testbed-18: Reproducible FAIR Best Practices Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-138", + "@id": "http://www.opengis.net/def/docs/12-111r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-03-21" + "@value": "2014-04-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "Marie-Françoise Voidrot-Martinez, Chris Little, Jürgen Seib, Roy Ladner, Adrian Custer, Jeff de La B" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -65975,27 +66035,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=36177" + "@id": "https://portal.ogc.org/files/?artifact_id=56394" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC® Fusion Standards Study Engineering Report" + "@value": "12-111r1" }, { "@language": "en", - "@value": "09-138" + "@value": "Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) provides discussions and recommendations for information fusion, with a focus on geospatial information. In this ER, fusion is discussed in three categories: sensor fusion, object/feature fusion, and decision fusion. Recommendations in this ER will be considered in the planning of future activities including the OWS-7 Testbed." + "@value": "This document proposes a set of best practices and guidelines for implementing and using the Open Geospatial Consortium (OGC) Web Map Service (WMS) to serve maps which are time-dependent or elevation-dependent. In particular, clarifications and restrictions on the use of WMS are defined to allow unambiguous and safe interoperability between clients and servers, in the context of expert meteorological and oceanographic usage and non-expert usage in other communities. This Best Practice document applies specifically to WMS version 1.3, but many of the concepts and recommendations will be applicable to other versions of WMS or to other OGC services, such as the Web Coverage Service." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66006,35 +66066,106 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-138" + "@value": "12-111r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Fusion Standards Study Engineering Report" + "@value": "OGC Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-063", + "@id": "http://www.opengis.net/def/doc-type/retired", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/05-110" + }, + { + "@id": "http://www.opengis.net/def/docs/04-087" + }, + { + "@id": "http://www.opengis.net/def/docs/99-114" + }, + { + "@id": "http://www.opengis.net/def/docs/06-010r6" + }, + { + "@id": "http://www.opengis.net/def/docs/03-061" + }, + { + "@id": "http://www.opengis.net/def/docs/03-064r10" + }, + { + "@id": "http://www.opengis.net/def/docs/03-062r1" + }, + { + "@id": "http://www.opengis.net/def/docs/01-037" + }, + { + "@id": "http://www.opengis.net/def/docs/01-026r1" + }, + { + "@id": "http://www.opengis.net/def/docs/04-086" + }, + { + "@id": "http://www.opengis.net/def/docs/01-004" + }, + { + "@id": "http://www.opengis.net/def/docs/01-042" + }, + { + "@id": "http://www.opengis.net/def/docs/03-055r1" + }, + { + "@id": "http://www.opengis.net/def/docs/00-117" + }, + { + "@id": "http://www.opengis.net/def/docs/03-003r10" + }, + { + "@id": "http://www.opengis.net/def/docs/99-103" + }, + { + "@id": "http://www.opengis.net/def/docs/05-036" + }, + { + "@id": "http://www.opengis.net/def/docs/04-088" + }, + { + "@id": "http://www.opengis.net/def/docs/01-035" + }, + { + "@id": "http://www.opengis.net/def/docs/03-063r1" + }, + { + "@id": "http://www.opengis.net/def/docs/99-104" + }, + { + "@id": "http://www.opengis.net/def/docs/04-085" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/11-094", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-09-11" + "@value": "2011-11-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lewis Leinenweber" + "@value": "Bastian Baranski" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66044,27 +66175,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34127" + "@id": "https://portal.ogc.org/files/?artifact_id=45403" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-6 GeoProcessing Workflow Thread Summary ER" + "@value": "WS-Agreement Application Profile for OGC Web Services" }, { "@language": "en", - "@value": "09-063" + "@value": "11-094" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document summarizes work completed in the GeoProcessing Workflow thread of the OWS-6 Testbed, it is applicable to the OGC Interoperability Program testbed.\r\n" + "@value": "This document specifies a) XML schemas for providing functional and non-functional service descriptions of OGC Web Services (OWS), b) an URN namespace for identifying exposed and measurable service properties of OWS and c) a DSL for defining and evaluating service level guarantees." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66075,35 +66206,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-063" + "@value": "11-094" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 GeoProcessing Workflow Thread Summary ER" + "@value": "WS-Agreement Application Profile for OGC Web Services" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-018r1", + "@id": "http://www.opengis.net/def/docs/19-046r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-02-06" + "@value": "2020-01-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Scott Serich" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66113,27 +66244,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/12-128r19/23-018r1.html" + "@id": "https://docs.ogc.org/per/19-046r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Release Notes for OGC GeoPackage 1.4.0" + "@value": "OGC Testbed-15: Quebec Model MapML Engineering Report" }, { "@language": "en", - "@value": "23-018r1" + "@value": "19-046r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the set of revision notes for OGC® GeoPackage Encoding Standard, version 1.4.0 [OGC 12-128r19] and does not modify that Standard.\r\n\r\nThis document provides the details of edits, deficiency corrections, and enhancements of the above-referenced Standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility." + "@value": "This OGC Testbed-15 Engineering Report (ER) describes the Map Markup Language (MapML) enabled client component implementation for the Quebec Lake-River Differentiation Model in the Machine Learning (ML) task of Open Geospatial Consortium (OGC) Testbed-15 (T-15). This ER presents the MapML parsing capabilities that were developed to illustrate the outputs of a ML model to delineate lake and river features from an undifferentiated waterbody vector dataset in Québec, Canada. Client data was accessed through an OGC Web Processing Service (WPS) interface in coordination with an OGC API - Features implementation." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66144,35 +66275,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-018r1" + "@value": "19-046r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Release Notes for OGC GeoPackage 1.4.0" + "@value": "OGC Testbed-15: Quebec Model MapML Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-081r2", + "@id": "http://www.opengis.net/def/docs/13-011", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-11-07" + "@value": "2013-04-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joshua Lieberman" + "@value": "Nadine Alameh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/rfc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66182,27 +66313,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=11499" + "@id": "https://portal.ogc.org/files/?artifact_id=53036" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Terrain Service RFC" + "@value": "13-011" }, { "@language": "en", - "@value": "03-081r2" + "@value": "OWS-9: Summary of the OGC Web Services, Phase 9 (OWS-9) Interoperability Testbed" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/rfc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a companion specification to the OpenGIS Web Map Service Interface Implementation Specification version 1.1.1 [4], hereinafter WMS 1.1.1. \r\nWMS 1.1.1 specifies how individual map servers describe and provide their map content. The present Web Terrain Service specification describes a new operation, GetView, and extended Capabilities which allow a 3D terrain view image to be requested, given a map composition, a terrain model on which to drape the map, and a 3D viewpoint from which to render the terrain view. A simple attempt is also made to reconcile 2D and 3D viewpoints by allowing the requested 3D area of view to be approximated with a WMS 1.1.1 bounding box" + "@value": "This report summarizes the results of OGC Web Services Initiative, Phase 9 (OWS-9)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66213,35 +66344,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-081r2" + "@value": "13-011" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Terrain Service RFC" + "@value": "OWS-9: Summary of the OGC Web Services, Phase 9 (OWS-9) Interoperability Testbed" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-082", + "@id": "http://www.opengis.net/def/docs/20-066", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-27" + "@value": "2021-09-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Hsu-Chun James Yu, Zhong-Hung Lee, Cai-Fang Ye, Lan-Kun Chung, Yao-Min Fang" + "@value": "Charles Heazel" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/ug" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66251,27 +66382,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34126" + "@id": "https://docs.ogc.org/guides/20-066.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-082" + "@value": "20-066" }, { "@language": "en", - "@value": "Sensor Web Enablement Application for Debris Flow Monitoring System in Taiwan" + "@value": "City Geography Markup Language (CityGML) 3.0 Conceptual Model Users Guide" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/ug" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This application document describes:\r\n\r\n1)\tWhat is a Debris Flow Monitoring System.\r\n2)\tHow SWE implements in Debris Flow Monitoring System. \r\n3)\tTutorial for SWE developers.\r\n" + "@value": "CityGML is an open conceptual data model for the storage and exchange of virtual 3D city models. It is defined through a Unified Modeling Language (UML) object model. This UML model extends the ISO Technical Committee 211 (TC211) conceptual model standards for spatial and temporal data. Building on the ISO foundation assures that the man-made features described in the City Models share the same spatial-temporal universe as the surrounding countryside within which they reside. The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields.\r\n\r\nThis Users Guide provides extended explanations and examples for the individual concepts that are defined in the CityGML 3.0 Conceptual Model Standard. Both documents, the Conceptual Model Standard and the Users Guide, are mutually linked to facilitate navigation between corresponding sections in these documents." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66282,35 +66413,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-082" + "@value": "20-066" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Web Enablement Application for Debris Flow Monitoring System in Taiwan" + "@value": "OGC City Geography Markup Language (CityGML) 3.0 Conceptual Model Users Guide" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-123", + "@id": "http://www.opengis.net/def/docs/09-046r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-10-13" + "@value": "2021-09-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roland M. Wagner" + "@value": "Gobe Hobona, Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/pol" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66320,27 +66451,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=35516" + "@id": "https://docs.ogc.org/pol/09-046r6.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-123" + "@value": "09-046r6" }, { "@language": "en", - "@value": "GeoRM Role Model" + "@value": "OGC Naming Authority - Procedures" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/pol" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The scope of this document is the update and the definition of GeoRM roles as a sub model of the GDI.NRW reference model (process model and architecture model). Key relationships are defined between these roles." + "@value": "The mission of the OGC Naming Authority (OGC-NA) is to provide the means through which OGC resources such as OGC documents, namespaces and ontologies can be controlled and managed such that they can provide clear and well-defined names and definitions. In the terminology defined in ISO 19135, OGC-NA is the Control Body for the register of OGC Names. This document describes the framework of documents, registers and other resources required for OGC-NA to execute that role." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66351,35 +66482,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-123" + "@value": "09-046r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GeoRM Role Model" + "@value": "OGC Naming Authority - Procedures" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-076", + "@id": "http://www.opengis.net/def/docs/16-042r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-03-31" + "@value": "2017-06-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Evans" + "@value": "Lingjun Kang, Liping Di, Eugene Yu" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66389,27 +66520,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12582" + "@id": "https://docs.ogc.org/per/16-042r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Service (WCS) Implementation Specification (Corrigendum)" + "@value": "Testbed-12 WMS/WMTS Enhanced Engineering Report" }, { "@language": "en", - "@value": "05-076" + "@value": "16-042r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Extends the Web Map Server (WMS) interface to allow access to geospatial coverages that represent values or properties of geographic locations, rather than WMS generated maps (pictures).\r\n\r\nThe original document is available at: http://portal.opengeospatial.org/files/?artifact_id=3837" + "@value": "This Engineering Report (ER) describes requirements, challenges and solutions regarding improving multidimensional Earth Observation (EO) data access, discovery and visualization through Web Map Service (WMS), Web Map Tile Service (WMTS), and corresponding extensions. The ER will highlight solutions and recommendations of following main topics.\r\n1) WMTS enhancements for time-varying layer access/discovery\r\n\r\n2) WMS enhancements for NetCDF\r\n\r\n3) WMTS enhancements for multidimensional domain discovery\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66420,35 +66551,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-076" + "@value": "16-042r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Coverage Service (WCS) Implementation Specification (Corrigendum)" + "@value": "Testbed-12 WMS/WMTS Enhanced Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-088r3", + "@id": "http://www.opengis.net/def/docs/02-027", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-04-15" + "@value": "2002-05-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66458,27 +66589,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=50438" + "@id": "https://portal.ogc.org/files/?artifact_id=1137" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-7 Schema Automation Engineering Report" + "@value": "02-027" }, { "@language": "en", - "@value": "10-088r3" + "@value": "Observations and Measurements" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The capabilities of OGC’s KML 2.2 as a format for exchange and visualization of U.S. National System for Geospatial Intelligence (NSG) Application Schema (NAS) data is explored." + "@value": "This document describes a framework and encoding for measurements and observations." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66489,35 +66620,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-088r3" + "@value": "02-027" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-7 Schema Automation Engineering Report" + "@value": "Observations and Measurements" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-082", + "@id": "http://www.opengis.net/def/docs/11-088r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-04-27" + "@value": "2011-11-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Boyan Brodaric" + "@value": "Johannes Echterhoff, Thomas Everding" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66527,27 +66658,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64688" + "@id": "https://portal.ogc.org/files/?artifact_id=45850" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-082" + "@value": "11-088r1" }, { "@language": "en", - "@value": "GroundWaterML 2 – GW2IE FINAL REPORT" + "@value": "Event Service - Review and Current State" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes a conceptual model, logical model, and GML/XML encoding rules for the exchange of groundwater data. In addition, this document provides GML/XML encoding examples for guidance. " + "@value": "This Discussion Paper provides information on what has so far been called “Event Service” at OGC.\r\nThe presented work is supported by the European Commission through the ESS project (integrated project, contract number 217951) and the GENESIS project (integrated project, contract number 223996) .\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66558,35 +66689,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-082" + "@value": "11-088r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GroundWaterML 2 – GW2IE FINAL REPORT" + "@value": "OGC® Event Service - Review and Current State" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-051", + "@id": "http://www.opengis.net/def/docs/15-005r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-09-26" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "DGIWG" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66596,27 +66727,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=6621" + "@id": "https://portal.ogc.org/files/94152" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS1.2 Image Handling Design" + "@value": "15-005r2" }, { "@language": "en", - "@value": "04-051" + "@value": "Defence Profile of OGC Web Feature Service 2.0" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Image Handling is a thread in the OGC Web Services 1.2 (OWS1.2). This document defines the system design for Image Handling in OWS1.2. The system design responds to the requirements in OWS 1.2 Image Handling Requirements. The system design specifies two main services: Image Archive Service and Image Catalogue Service. Interfaces for these two services are defined using previously defined OWS service interfaces. " + "@value": "This document defines the DGIWG profile for the ISO\r\n19142:2010 - Web Feature Service (WFS) including changes\r\nmade in the OpenGIS Web Feature Service 2.0 Interface\r\nStandard - Corrigendum. The Web Feature Service provides\r\naccess to geospatial features in a manner independent of the\r\nunderlying data store." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66627,25 +66758,25 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-051" + "@value": "15-005r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS1.2 Image Handling Design" + "@value": "Defence Profile of OGC Web Feature Service 2.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-052", + "@id": "http://www.opengis.net/def/docs/05-014", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-09-26" + "@value": "2005-01-31" } ], "http://purl.org/dc/terms/creator": [ @@ -66665,17 +66796,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=6660" + "@id": "https://portal.ogc.org/files/?artifact_id=8848" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS1.2 Image Handling Requirements" + "@value": "05-014" }, { "@language": "en", - "@value": "04-052" + "@value": "Image CRSs for IH4DS" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -66685,7 +66816,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document was developed as part of the Image Handling Thread of the OGC Web Services Initiative Phase 1 Thread Set 2 (OWS 1.2). This document specified the requirements for the image handling functions to be supported by draft specifications prepared under that thread. " + "@value": "This Discussion Paper specifies image coordinate reference system (CRS) definitions designed for possible use by WCTS and WCS servers and clients, initially in the IH4DS thread of the OWS 2 interoperability initiative. This report specifies image CRS definitions suitable for both ungeorectified and georectified images, where an ungeorectified image can be georeferenced or not." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66696,35 +66827,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-052" + "@value": "05-014" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS1.2 Image Handling Requirements" + "@value": "Image CRSs for IH4DS" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-025r1", + "@id": "http://www.opengis.net/def/docs/12-128r19", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-06" + "@value": "2024-02-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Luis Bermudez" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66734,27 +66865,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-025r1.html" + "@id": "https://www.geopackage.org/spec140/index.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-025r1" + "@value": "GeoPackage Encoding Standard" }, { "@language": "en", - "@value": "Data Access and Processing API Engineering Report" + "@value": "12-128r19" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 16 Engineering Report documents the advancement of an OGC Data Access and Processing API (DAPA)." + "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66765,35 +66896,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-025r1" + "@value": "12-128r19" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: Data Access and Processing API Engineering Report" + "@value": "OGC® GeoPackage Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-050", + "@id": "http://www.opengis.net/def/docs/08-059r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-12" + "@value": "2014-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó and Alaitz Zabala" + "@value": "Peter Baumann, Jinsongdi Yu" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66803,27 +66934,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-050.html" + "@id": "https://portal.ogc.org/files/?artifact_id=54506" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-050" + "@value": "08-059r4" }, { "@language": "en", - "@value": "Testbed-12 Imagery Quality and Accuracy Engineering Report" + "@value": "Web Coverage Service WCS Interface Standard - Processing Extension" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The scenario of rapidly growing geodata catalogues requires tools focused on facilitating users the choice of products. Having populated quality fields in metadata allows the users to rank and then select the best fit-for-purpose products. For example, decision-makers would be able to find quality and uncertainty measures to take the best decisions as well as to perform dataset intercomparison. In addition, it allows other components (such as visualization, discovery, or comparison tools) to be quality-aware and interoperable.\r\n\r\nThis ER deals with completeness, logical consistency, positional accuracy, temporal accuracy and thematic accuracy issues to improve quality description in the metadata for imagery. Based on ISO 19157, UncertML and QualityML standardized measures, this ER describes how to encode quality measures in order to allow datasets comparison. Moreover, description of pixel-level quality measures is also included. Finally, alternatives to communicate tile level quality as well as mosaic products quality are proposed." + "@value": "The OGC Web Coverage Service (WCS)– Processing Extension defines an extension to the WCS Core [OGC 09-110], the ProcessCoverages request type, which allows clients to initi-ate server-side processing and filtering of coverages and to download the resulting coverage or value sets based on the query language defined in the Web Coverage Processing Service (WCPS) interface standard [OGC 08-068]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66834,35 +66965,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-050" + "@value": "08-059r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Imagery Quality and Accuracy Engineering Report" + "@value": "OGC® Web Coverage Service WCS Interface Standard - Processing Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-123r1", + "@id": "http://www.opengis.net/def/docs/14-000", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-02-16" + "@value": "2014-07-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "R. Martell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66872,27 +67003,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=67120" + "@id": "https://portal.ogc.org/files/?artifact_id=58995" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-123r1" + "@value": "14-000" }, { "@language": "en", - "@value": "Geopackage Release Notes" + "@value": "Testbed 10 Engineering Report: GML for Aviation Conformance Testing" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the set of revision notes for the existing OGC Implementation Standard GeoPackage version 1.1 (OGC 12-128r12) and does not modify that standard.\r\nThis document was approved by the OGC membership on . As a result of the OGC Standards Working Group (SWG) process, there were a number of edits and enhancements made to this standard. This document provides the details of those edits, deficiency corrections, and enhancements. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility.\r\n" + "@value": "This activity is part of OGC Testbed 10. The aviation thread was focused on developing\r\nand demonstrating the use of the Aeronautical Information Exchange Model (AIXM) and\r\nthe Flight Information Exchange Model (FIXM), building on the work accomplished in\r\nprior testbeds to advance the applications of OGC Web Services standards in next generation\r\nair traffic management systems to support European and US aviation modernization\r\nprograms\r\nThis document summarizes technical work relating to the enhancement of the GML 3.2.1\r\nconformance test suite in accord with the requirements in the OWS-10 RFQ, Annex B1,\r\nsection 6.3.6: “GML for Aviation Compliance Test Suite + GML for Aviation Conformance\r\nTesting ER”. The essential aim is to advance compliance with respect to the use of\r\nGML geometry representations in aviation (AIXM) data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -66903,35 +67034,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-123r1" + "@value": "14-000" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geopackage Release Notes" + "@value": "Testbed 10 Engineering Report: GML for Aviation Conformance Testing" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-000", + "@id": "http://www.opengis.net/def/docs/11-158", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-14" + "@value": "2011-10-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "R. Martell" + "@value": "Jim Greenwood" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -66941,27 +67072,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=58995" + "@id": "https://portal.ogc.org/files/?artifact_id=46436" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-000" + "@value": "Corrigendum 2 for OGC Web Services Common Specification v 1.1.0 - Exception Report" }, { "@language": "en", - "@value": "Testbed 10 Engineering Report: GML for Aviation Conformance Testing" + "@value": "11-158" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This activity is part of OGC Testbed 10. The aviation thread was focused on developing\r\nand demonstrating the use of the Aeronautical Information Exchange Model (AIXM) and\r\nthe Flight Information Exchange Model (FIXM), building on the work accomplished in\r\nprior testbeds to advance the applications of OGC Web Services standards in next generation\r\nair traffic management systems to support European and US aviation modernization\r\nprograms\r\nThis document summarizes technical work relating to the enhancement of the GML 3.2.1\r\nconformance test suite in accord with the requirements in the OWS-10 RFQ, Annex B1,\r\nsection 6.3.6: “GML for Aviation Compliance Test Suite + GML for Aviation Conformance\r\nTesting ER”. The essential aim is to advance compliance with respect to the use of\r\nGML geometry representations in aviation (AIXM) data." + "@value": "This document defines the corrigendum change notes for > The OGC API - Processes<> is adopted as the base API for standardizing and developing the HPGC API. A Python client library is developed to demonstrate the process of client generation by leveraging the OpenAPI client stub/model automatic generation capability<>. Typical use cases and scenarios are demonstrated and scripted in Jupyter Notebooks." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -67524,35 +67655,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-007" + "@value": "23-044" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 Common CBRN Sensor Interface (CCSI)-Sensor Web Enablement (SWE) Engineering Report" + "@value": "OGC Testbed 19 High Performance Geospatial Computing Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-032r1", + "@id": "http://www.opengis.net/def/docs/23-013", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-01-11" + "@value": "2023-10-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed, PhD" + "@value": "Tom Kralidis, Mark Burgoyne, Steve Olson, Shane Mill" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -67562,27 +67693,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/17-014r9/22-032r1.html" + "@id": "https://docs.ogc.org/dp/23-013.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-032r1" + "@value": "23-013" }, { "@language": "en", - "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Version 1.3 Release Notes" + "@value": "Discussion paper for Publish-Subscribe workflow in OGC APIs" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "These I3S Release notes document changes incorporated into the OGC I3S Community Standard version 1.3." + "@value": "OGC APIs provide Web based capabilities which are typically based on polling for collection resource updates (new features/records items, coverages, maps, etc.). Depending on a collection’s temporal resolution or frequency of updates, an event-driven / Publish-Subscribe architecture provides a timely, efficient, and low latency approach for delivery of data updates. This paper provides recommendations on applying Publish-Subscribe architectural patterns to OGC APIs." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -67593,35 +67724,43 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-032r1" + "@value": "23-013" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Version 1.3 Release Notes" + "@value": "Discussion paper for Publish-Subscribe workflow in OGC APIs" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-048r5", + "@id": "http://www.opengis.net/def/doc-type/orm", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/08-062r7" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/14-029r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-10-31" + "@value": "2014-07-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox, Gobe Hobona" + "@value": "Martin Klopfer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/pol-nts" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -67631,27 +67770,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/pol/09-048r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=59336" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-048r5" + "@value": "14-029r2" }, { "@language": "en", - "@value": "Name Type Specification - definitions - part 1 – basic name" + "@value": "Testbed 10 Virtual Global Gazetteer Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/pol-nts" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies a rule for constructing OGC names that may be used for identifying definitions." + "@value": "This document provides a technical description of the Virtual Global Gazetteer implemented for OGC Testbed 10. \r\nThe Virtual Global Gazetteer integrates two gazetteers – a copy of the USGS gazetteer containing domestic names and a copy of the NGA gazetteer containing non-domestic names (hosted by Interactive Instruments) and provides the capability to link to additional local gazetteers and linked data information, allowing a user to retrieve extended information on locations selected from either of the initial gazetteers. The access to linked data information provided by these gazetteers was achieved by GeoSPARQL enabling these gazetteers using semantic mapping components\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -67662,35 +67801,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-048r5" + "@value": "14-029r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Name Type Specification - definitions - part 1 – basic name" + "@value": "OGC® Testbed 10 Virtual Global Gazetteer Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-153r1", + "@id": "http://www.opengis.net/def/docs/10-124r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-01-25" + "@value": "2010-07-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -67700,27 +67839,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46442" + "@id": "https://portal.ogc.org/files/?artifact_id=39467" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Service 2.0 Primer: Core and Extensions Overview" + "@value": "10-124r1" }, { "@language": "en", - "@value": "09-153r1" + "@value": "OGC Identifiers - the case for http URIs" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides an overview on the OGC Web Coverage Service (WCS) 2.0 suite by describing WCS core and extensions. \r\nIntended target audience are developers intending to implement WCS servers and/or clients. This document aims at providing an overview and giving useful hints and best practices beyond the pure standards texts. It is a "living document" which will evolve to reflect new developments and best practices.\r\nAs such, the contents of this document is informative and not of normative nature.\r\n" + "@value": "The OGC provides a large number of resources to support the construction of spatial\r\ndata infrastructures, including documents, specifications, schemas and concept\r\ndefinitions. When deployed, the infrastructures require persistent reference to these\r\nresources, enabled by persistent identifiers. This may be at various level of\r\ngranularity. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -67731,30 +67870,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-153r1" + "@value": "10-124r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Coverage Service 2.0 Primer: Core and Extensions Overview" + "@value": "OGC Identifiers - the case for http URIs" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-102r2", + "@id": "http://www.opengis.net/def/docs/20-050", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-08-16" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Scarponcini" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -67769,17 +67908,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=75119" + "@id": "https://docs.ogc.org/is/20-050/20-050.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-102r2" + "@value": "20-050" }, { "@language": "en", - "@value": "InfraGML 1.0: Part 2 - LandInfra Facilities and Projects - Encoding Standard" + "@value": "Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension)." } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -67789,7 +67928,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 2 addresses the Facility and Project Requirements Classes from LandInfra." + "@value": "This optional OGC CDB extension defines the requirements and provides CDB specific guidance on using GeoPackage containers in a CDB data store. There is a companion CDB Best Practice document that provide rules and guidance for transforming CDB structured Shapefiles into CDB structure GeoPackages that are compliant with the requirements and conformance classes as defined in this document." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -67800,35 +67939,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-102r2" + "@value": "20-050" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC InfraGML 1.0: Part 2 - LandInfra Facilities and Projects - Encoding Standard" + "@value": "Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension)." } ] }, { - "@id": "http://www.opengis.net/def/docs/15-074r2", + "@id": "http://www.opengis.net/def/docs/14-039", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-10-25" + "@value": "2014-07-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Frans Knibbe, Alejandro Llaves" + "@value": "Thibault Dacla, Daniel Balog" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -67838,27 +67977,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/15-074r2/15-074r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=58929" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-074r2" + "@value": "Testbed 10 Aviation Human Factor Based Portrayal of Digital NOTAMs ER" }, { "@language": "en", - "@value": "Spatial Data on the Web Use Cases & Requirements" + "@value": "14-039" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC." + "@value": "This activity is part of OGC Testbed 10. The aviation thread was focused on developing and demonstrating the use of the Aeronautical Information Exchange Model (AIXM) and the Flight Information Exchange Model (FIXM), building on the work accomplished in prior testbeds to advance the applications of OGC Web Services standards in next generation air traffic management systems to support European and US aviation modernization programs.\r\nThis document provides the result of the Testbed 10 to assess the compliance between the OGC standards and the guidelines provided by the SAE in their latest published document regarding portraying of NOTAMs. Specifically, the Human Based Portrayal of DNOTAM work attempts to fulfill the high level requirements identified in the OGC Testbed-10 RFQ Annex B .\r\nThe purpose of this investigation was to analyze the recommendations of the SAE comity and to evaluate the feasibility of their application using OGC standards for portraying, namely the Symbology Encoding standard, version 1.1.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -67869,35 +68008,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-074r2" + "@value": "14-039" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Spatial Data on the Web Use Cases & Requirements" + "@value": "OGC® Testbed 10 Aviation Human Factor Based Portrayal of Digital NOTAMs ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-173r2", + "@id": "http://www.opengis.net/def/docs/12-152r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-01-25" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Herring" + "@value": "Luis Bermudez" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -67907,27 +68046,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=19054" + "@id": "https://portal.ogc.org/files/?artifact_id=52112" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-173r2" + "@value": "12-152r1" }, { "@language": "en", - "@value": "Geographic information - Rights expression language for geographic information - Part xx: GeoREL" + "@value": "OWS-9 CITE Help Guide Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": " This document extends the rights expression language (REL) to encompass the concerns of holders of geographic data and service resources to equally ensure their protection. This allows the geographic information market to operate with minimal constraints derived from need for the protection of intellectual property." + "@value": "This Engineering Report was created as a deliverable of the CITE Thread as part of the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. This OGC® Engineering Report describes how to execute the CITE tests, how to select the conformance classes, how to access and download the TEAM Engine, Test Scripts and Reference Implementations, how to insert your own data and/or schemas along with a section that provides other community help resources.\r\nThis is not a normative document.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -67938,35 +68077,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-173r2" + "@value": "12-152r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geographic information - Rights expression language for geographic information - Part xx: GeoREL" + "@value": "OGC® OWS-9 CITE Help Guide Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-064r1", + "@id": "http://www.opengis.net/def/docs/04-094", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-08-01" + "@value": "2005-05-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Detlev Wagner, Hugo Ledoux" + "@value": "Peter Vretanos " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -67976,27 +68115,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=68821" + "@id": "https://portal.ogc.org/files/?artifact_id=8339" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-064r1" + "@value": "Web Feature Service (WFS) Implementation Specification" }, { "@language": "en", - "@value": "CityGML Quality Interoperability Experiment" + "@value": "04-094" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report specifies the results and findings of the CityGML Quality\r\nInteroperability Experiment. Guidelines were developed for the following concepts:\r\n􀀀 Definition of data quality;\r\n􀀀 Data quality requirements and their specification;\r\n􀀀 Quality checking process of CityGML data; and\r\n􀀀 Description of validation results.\r\nThe desired outcomes of this Interoperability Experiment are to improve the\r\ninteroperability of CityGML data by removing some ambiguities from the current\r\nstandard and formally defining data quality requirements for a general CityGML data\r\nspecification. Further, the results of this work provides to the community (organizations\r\ninvested in capturing, procuring, or utilizing CityGML data) recommended\r\nimplementation guidance for 3D data and a suite of essential quality checking tools to\r\ncarry out quality assurance on CityGML data." + "@value": "The OpenGIS Web Feature Service Interface Standard (WFS) defines an interface[http://www.opengeospatial.org/ogc/glossary/i] for specifying requests for retrieving geographic features [http://www.opengeospatial.org/ogc/glossary/g] across the Web using platform-independent calls. The WFS standard defines interfaces and operations for data access and manipulation on a set of geographic features, including: \r\n•\tGet or Query features based on spatial and non-spatial constraints\r\n•\tCreate a new feature instance \r\n•\tGet a description of the properties of features\r\n•\tDelete a feature instance \r\n•\tUpdate a feature instance \r\n•\tLock a feature instance \r\n\r\nThe specified feature encoding for input and output is the Geography Markup Language (GML) [http://www.opengeospatial.org/standards/gml] although other encodings may be used. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68007,30 +68146,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-064r1" + "@value": "04-094" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® CityGML Quality Interoperability Experiment" + "@value": "OpenGIS Web Feature Service (WFS) Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-084", + "@id": "http://www.opengis.net/def/docs/18-076", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-01-20" + "@value": "2019-02-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Luis Bermudez" + "@value": "Jens Ingensand, Kalimar Maia" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -68045,17 +68184,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-084.html" + "@id": "https://docs.ogc.org/per/18-076.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-084" + "@value": "18-076" }, { "@language": "en", - "@value": "Geospatial to the Edge Plugfest Engineering Report" + "@value": "Tiled Feature Data Conceptual Model Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -68065,7 +68204,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Geospatial to the Edge Interoperability Plugfest, co-sponsored by the Army Geospatial Center and the National Geospatial-Intelligence Agency (NGA/CIO&T), brought together technology implementers and data providers to advance the interoperability of geospatial products and services based on profiles of OGC standards. Specifically, servers and data available via GeoPackage, Web Feature Service (WFS), Web Map Service (WMS), and Web Map Tile Service (WMTS), all following National System for Geospatial Intelligence (NSG) profiles, were exercised and improved in various clients. Compliance Tests were executed and advanced based on feedback from the participants." + "@value": "Feature data tiling, colloquially referred to as 'vector tiling', is a method that defines how large vector geospatial datasets can be systematically split into subsets or tiles [1]. Feature data tiling allows for a variety of use-cases, such as creating online maps, quickly accessing large vector data sets for geoprocessing and creating download-services. For instance, a map created from tiled feature data consists of one or more layers of vector data organized into tiles of features and rendered on the client-side using an associated style. In contrast, raster tiles are delivered as tiled images that have been rendered on the server-side.\r\n\r\nNOTE\r\nThis engineering report interchangeably uses both 'tiled feature data' and the colloquial term 'vector tiles'." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68076,35 +68215,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-084" + "@value": "18-076" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Geospatial to the Edge Plugfest Engineering Report" + "@value": "OGC Vector Tiles Pilot: Tiled Feature Data Conceptual Model Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-086r1", + "@id": "http://www.opengis.net/def/docs/08-167r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-15" + "@value": "2012-10-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sam Meek" + "@value": "Frédéric Houbie, Philippe Duchesne, Patrick Maué" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -68114,27 +68253,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-086r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=47857" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Vector Tiles Pilot: Summary Engineering Report" + "@value": "Semantic annotations in OGC standards" }, { "@language": "en", - "@value": "18-086r1" + "@value": "08-167r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) provides the summary findings resulting from completion of the OGC Vector Tiles Pilot (VTP or Pilot). The requirements for the Pilot were generated from a combination of sponsor input and analysis of typical use cases for tiling of vector feature data across the OGC Standards Baseline and related standards. The driving use case for this activity was the visualization of feature data on a client. The three main scenarios considered were consumption of tiled feature data by a web client, a desktop client and a mobile client. As a standards body, the OGC already has standards that fit these use cases. These are; Web Map Tile Service 1.0 (WMTS) for a web client, and GeoPackage 1.2 for a mobile client. Web Feature Service (WFS) 3.0 is suitable for a desktop client and has an in-built method to support tiling, but not specifically for tiled feature data such as that explored in the VTP. One of the purposes of the Pilot was to produce demonstration implementations to support tiled feature data using WFS 3.0, WMTS 1.0 and GeoPackage 1.2 that can be validated by Technology Integration Experiments (TIEs). The draft extension to these standards helped define a draft Conceptual Model for tiled feature data in support of visualization. The Conceptual Model formally captures the requirements for component implementations and rationalizes them into a model documented in the Unified Modeling Language (UML).\r\n\r\nThe ER provides an overview of each of the components, their implementation decisions and the challenges faced. The components are presented as draft extensions to existing standards. The WFS standard is currently in a major revision cycle and is transitioning away from services to a resource-oriented architecture. This transition has implications for access to tiled feature data. This offers options of access to pre-rendered tiles, or to tiles created using WFS 3.0 query functionality. The current WMTS standard only offers access to the pre-rendered tiles and much of the work is therefore about defining and supporting tiled feature data as a media type. The OGC GeoPackage standard is more complex as it attempts to ship all of the tiled feature data in a self-contained package aimed at environments that have Denied, Degraded, Intermittent or Limited (DDIL) bandwidth. DDIL is an important use case for GeoPackage as most normal web services do not function without connectivity. The military, first responders and other groups who work in challenging operational environments require a capability to ship, store and distribute geospatial data in an efficient, modern manner. The combination of GeoPackage and tiled feature data offers the means to supply detailed geospatial data in a portable fashion to satisfy many DDIL use cases. GeoPackage also offers the majority of the future work as it attempts to store information such as styling and attribution separately to the geometries to take advantage of a relational database structure.\r\n\r\nWhen this project was initiated, the term vector tiles was used throughout. However, as the project progressed, the participants agreed that the term tiled feature data was more appropriate than the colloquial term of vector tiles. This engineering report therefore interchangeably uses both tiled feature data and vector tiles to refer to the approach of tiling vector feature data.\r\n\r\n" + "@value": "In this OGC Best Practice, the concept of semantic annotations is introduced. Annotation of Web Services or data compliant to OGC standards refers to the task of attaching meaningful descriptions to the service and the served geospatial data or processes." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68145,35 +68284,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-086r1" + "@value": "08-167r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Vector Tiles Pilot: Summary Engineering Report" + "@value": "Semantic annotations in OGC standards" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-012r1", + "@id": "http://www.opengis.net/def/docs/12-133", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-17" + "@value": "2014-08-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Nicolas FANJEAU, Sebastian ULRICH" + "@value": "John Hudson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -68183,27 +68322,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=57203" + "@id": "https://portal.ogc.org/files/?artifact_id=51178" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-012r1" + "@value": "Web Services Facade for OGC IP Engineering Report" }, { "@language": "en", - "@value": "RESTful encoding of OGC Sensor Planning Service for Earth Observation satellite Tasking" + "@value": "12-133" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Best Practices document specifies the interfaces, bindings, requirements and conformance classes that enable complete workflows for the tasking of sensor planning services for Earth Observation (EO) satellites. In fact it provides the interfaces for supporting the following EO sensor planning scenarios:\r\n•\tPlanning future acquisitions with feasibility study,\r\n•\tDirect planning of future acquisitions,\r\n•\tReservation of planning for future acquisitions.\r\nThis specification includes a comprehensive list of sensor options and tasking options derived from the parent specification OGC 10-135 [NR22] which gathered inputs from several Satellite Agencies and Operators:\r\n•\tESA\r\n•\tEUMETSAT\r\n•\tCNES\r\n•\tDLR\r\n•\tCSA\r\n•\tAirbus Defence & Space\r\nThis document is based on the standard:\r\nOGC 10-135, Sensor Planning Service Interface Standard 2.0 Earth Observation \r\nSatellite Tasking Extension, version 2.0. 2011.\r\n\r\nwhich was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [OR1] and related projects.\r\nWith respect to the parent specification this Best Practice document proposes the following changes:\r\n•\tReplaces SOAP with REST for service encoding. This affects not only the way the service is implemented but also the way the standard is presented and described. In fact, basing the standard on REST implies that the service has to be described in terms of resources and methods applied on them whilst in SOAP services, the description is focusing on operations and in fact the OGC 10-135[NR22] is structured in Web Service operations.\r\n•\tUsage of OpenSearch Description Documents as an alternate method for describing sensors and tasking Options (§7.3.2). This specification uses the sensors and tasking options model already described in the OGC 10-135 [NR22] standard but defines an additional method for describing sensors and tasking options within OpenSearch Description Documents based on the OGC 13-039 [NR23]. Actually this part of the specification refers to the OpenSearch Extension for Earth Observation Satellite Tasking.\r\n \r\n" + "@value": "This document describes the Web Services Façade which was developed by LISAsoft as part of the OWS-9 testbed. The document also includes discussions about lessons learned during the development, and suggestions for future development.\r\nThis Engineering Report documents the Web Services Façade work done within OWS-9 as an extensible, open source tool, which supports translations between different protocols for a specific web service. For the OWS-9 testbed, it has been set up to translate between POST and SOAP services for a Web Feature Service. However, it can be configured to support translations between multiple protocols, such as REST, SOAP, KVP, JSON, as well as supporting multiple web services.\r\nThe Web Services Façade is an extensible, open source tool, which supports translations between different protocols for a specific web service. For the OWS-9 testbed, it has been set up to translate between POST and SOAP services for a Web Feature Service. However, it can be configured to support translations between multiple protocols, such as REST, SOAP, KVP, JSON, as well as supporting multiple web services.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68214,35 +68353,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-012r1" + "@value": "12-133" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC RESTful encoding of OGC Sensor Planning Service for Earth Observation satellite Tasking" + "@value": "OGC® Web Services Facade for OGC IP Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-003r4", + "@id": "http://www.opengis.net/def/docs/20-083r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2021-05-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Josh Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -68252,27 +68391,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/16-003r4.html" + "@id": "https://docs.ogc.org/per/20-083r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-003r4" + "@value": "20-083r2" }, { "@language": "en", - "@value": "Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values" + "@value": "Building Energy Mapping and Analytics: Concept Development Study Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids key words." + "@value": "This report details the results of the OGC Building Energy Mapping and Analysis Concept Development Study (BEMA CDS). Sponsored by NRCan and drawing on numerous previous studies, the CDS released a Request for Information on building energy data and applications. The responses were presented and validated in 3 public workshops and form the basis for an Energy SDI notional architecture." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68283,35 +68422,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-003r4" + "@value": "20-083r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values" + "@value": "Building Energy Mapping and Analytics: Concept Development Study Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-000", + "@id": "http://www.opengis.net/def/docs/16-092r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-07-24" + "@value": "2018-01-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mike Botts" + "@value": "Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -68321,27 +68460,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=21273" + "@id": "https://docs.ogc.org/per/16-092r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Sensor Model Language (SensorML)" + "@value": "16-092r2" }, { "@language": "en", - "@value": "07-000" + "@value": "Incident Management Information Sharing (IMIS) Internet of Things (IoT) Extension Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Sensor Model Language Encoding Standard (SensorML) specifies models and XML encoding that provide a framework within which the geometric, dynamic, and observational characteristics of sensors and sensor systems can be defined. There are many different sensor types, from simple visual thermometers to complex electron microscopes and earth observing satellites. These can all be supported through the definition of atomic process models and process chains. Within SensorML, all processes and components are encoded as application schema of the Feature model in the Geographic Markup Language (GML) Version 3.1.1. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. For additional information on SensorML, see http://www.botts-inc.net/vast.html\r\n" + "@value": "The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives.\r\n\r\n· Apply Open Geospatial Consortium (OGC) principles and practices for collaborative development to existing standards and technology in order to prototype an IoT approach to sensor use for incident management.\r\n\r\n· Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability.\r\n\r\n· Development of profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability.\r\n\r\n· Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario.\r\n\r\nThese principles continued through the IoT Pilot Extension, with additional objectives of:\r\n\r\n· Integration into the existing Next Generation First Responder (NGFR) Apex development program process as part of Spiral 1;\r\n\r\n· Defining steps to begin the integration of existing incident management infrastructure, e.g., pulling in National Institute of Emergency Management (NIEM) message feeds; and\r\n\r\n· Demonstration and experimentation in a ‘realistic’ incident environment using two physically separate sites–an incident site within an active first responder training facility (Fairfax County Lorton site), and a command center (DHS S&T Vermont Avenue facility).\r\n\r\nThe initial Pilot activity has been documented in three OGC public engineering reports. The present report describes and documents the additional activities and innovations undertaken in the Extension." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68352,35 +68491,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-000" + "@value": "16-092r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Sensor Model Language (SensorML)" + "@value": "Incident Management Information Sharing (IMIS) Internet of Things (IoT) Extension Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-028r1", + "@id": "http://www.opengis.net/def/docs/15-010r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-06-04" + "@value": "2016-01-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andrea Biancalana, Pier Giorgio Marchetti, Paul Smits" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -68390,27 +68529,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39475" + "@id": "https://portal.ogc.org/files/?artifact_id=66905" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GIGAS Methodology for comparative analysis of information and data management systems" + "@value": "Testbed-11 WFS-T Information Exchange Architecture" }, { "@language": "en", - "@value": "10-028r1" + "@value": "15-010r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document has been written on the basis of a methodology developed within the GIGAS Support Action financed by the European Commission in order to address the convergence of global initiatives like GEOSS and the European interoperability initiatives developed in the context of the GMES programme like HMA - Heterogeneous Missions Accessibility and the INSPIRE spatial data infrastructure legislation." + "@value": "This document presents an assessment of the conformance level, with respect to the WFS standard (OGC 09-025r2), of the web feature servers used in the OGC Testbed-11. Each server is accessed to determine if it conforms to the minimum requirements of the WFS standard. Each server is further accessed to determine whether the server offers additional, upcoming and complimentary capabilities just as support for the WFS REST API and GeoJSON.\r\nThis document offers recommendations to aid implementers of the WFS standard (OGC 09-025r2).\r\nThis document presents options available to WFS implementers for achieving interoperability between WFS clients and server at the schemas level.\r\nThis document includes a survey of available WFS clients and an assessment of their capabilities.\r\nThis document reviews tools and standards, such as the GeoSynchronization Service (OGC 10-069r3), that are complimentary components that may be used with a WFS to address requirements such as verification and notification, data and access security, exception handling and system hardening.\r\nFinally, this document includes a FAQ composed of questions raised during the OGC Testbed-11.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68421,35 +68560,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-028r1" + "@value": "15-010r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GIGAS Methodology for comparative analysis of information and data management systems" + "@value": "OGC® Testbed-11 WFS-T Information Exchange Architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-038r2", + "@id": "http://www.opengis.net/def/docs/18-029", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-04-27" + "@value": "2019-03-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Uwe Voges, Kristian Senkler" + "@value": "Sara Saeedi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -68459,27 +68598,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8305" + "@id": "https://docs.ogc.org/per/18-029.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "ISO19115/ISO19119 Application Profile for CSW 2.0 (CAT2 AP ISO19115/19)" + "@value": "18-029" }, { "@language": "en", - "@value": "04-038r2" + "@value": "Symbology Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS" + "@value": "The portrayal and visualization of geospatial information is a critical task for facilitating decision making, situational awareness, and spatial analysis. However, despite its importance, various local, national, and international agencies continue to use different symbols and terminology for the same event, feature, or entity. This approach prevents interoperability from being extended to the semantic level, which in turn makes it difficult to share, reuse, and mediate unambiguous portrayal information between agencies.\r\n\r\nThis Engineering Report (ER) captures the requirements, solutions, models, and implementations of the Open Geospatial Consortium (OGC) Testbed-14 Portrayal thread. This effort leverages the work of the Portrayal Ontology development and the Semantic Portrayal Service conducted during Testbed 10, 11, 12 and 13. Thus far the emphasis for developing the portrayal ontologies (Testbeds 12 and 13) has been on modeling and representing portrayal information for feature data. The objective of Testbed-14 is to extend the portrayal ontology to accommodate more complex symbols (e.g., composite symbols) and to provide clear recommendations on how to best proceed with portrayal information encodings." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68490,35 +68629,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-038r2" + "@value": "18-029" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "ISO19115/ISO19119 Application Profile for CSW 2.0 (CAT2 AP ISO19115/19)" + "@value": "OGC Testbed-14: Symbology Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-116", + "@id": "http://www.opengis.net/def/docs/15-042r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-03-08" + "@value": "2018-12-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stan Tillman, Jody Garnett" + "@value": "James Tomkins, Dominic Lowe" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -68528,27 +68667,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12911" + "@id": "https://docs.ogc.org/is/15-042r5/15-042r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS Integrated Client (GeoDSS Client)" + "@value": "15-042r5" }, { "@language": "en", - "@value": "05-116" + "@value": "TimeseriesML 1.2 – XML Encoding of the Timeseries Profile of Observations and Measurements" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Interoperability Program Report (IPR) provides an overview of the general requirements, architecture, and design considerations of " + "@value": "TimeseriesML 1.2 defines an XML encoding that implements the OGC Timeseries Profile of Observations and Measurements, with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of data exchange requirements." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68559,35 +68698,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-116" + "@value": "15-042r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS Integrated Client (GeoDSS Client)" + "@value": "OGC TimeseriesML 1.2 – XML Encoding of the Timeseries Profile of Observations and Measurements" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-141r6", + "@id": "http://www.opengis.net/def/docs/09-053r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-01-09" + "@value": "2009-10-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Daniele Marchionni, Stefania Pappagallo " + "@value": "Bastian Schäffer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -68597,27 +68736,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=43928" + "@id": "https://portal.ogc.org/files/?artifact_id=34968" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Ordering Services Framework for Earth Observation Products Interface Standard" + "@value": "09-053r5" }, { "@language": "en", - "@value": "06-141r6" + "@value": "OWS-6 Geoprocessing Workflow Architecture Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® standard specifies the interfaces, bindings, requirements, conformance classes, and a framework for implementing extensions that enable complete workflows for ordering of Earth Observation (EO) data products. " + "@value": "This document covers Geoprocessing Workflow best practices and methods in a SOA environment. A RESTful approach was also conducted in this testbed, but no specific implementation details were available to be included in this ER; also, the RESTful workflow approaches and technology used in this testbed was essentially same as that used in OWS-5." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68628,35 +68767,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-141r6" + "@value": "09-053r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Ordering Services Framework for Earth Observation Products Interface Standard" + "@value": "OWS-6 Geoprocessing Workflow Architecture Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-022r1", + "@id": "http://www.opengis.net/def/docs/21-056r11", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-11" + "@value": "2023-09-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Yann Le Franc" + "@value": "Carl Stephen Smyth" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -68666,27 +68805,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-022r1.html" + "@id": "https://docs.ogc.org/is/21-056r11/21-056r11.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "SWIM Information Registry Engineering Report" + "@value": "OGC GeoPose 1.0 Data Exchange Standard" }, { "@language": "en", - "@value": "18-022r1" + "@value": "21-056r11" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) summarizes the findings and recommendations for building an information registry working together with the existing Federal Aviation Administration (FAA) System Wide Information Management (SWIM) aviation service registries, the National Airspace System Service Registry and Repository (NSRR). This information registry should allow the different Air Traffic Management (ATM) stakeholders to retrieve the appropriate service registered in the NSRR using the semantic representation of real-life entities represented by the data served by the services (e.g. estimated departure time, estimated time of arrival, ”runway true bearing”…). To support the integration of this domain-specific information, the ER proposes different strategies based on the semantic annotation proposal made in OGC 08-167r2 [1] extended with a recent World Wide Web Consortium (W3C) recommendation, the Web Annotation data model [1]. In particular, the ER focuses on a solution using the W3C web annotation data model which adds semantics to the NSRR without changing the content of the database. This solution provides a low-cost, flexible and efficient alternative to add domain-specific semantics to NSRR content. The ER concludes with remarks on the elements necessary for implementing the information registry as a web annotation store as well as the necessity to build domain-specific knowledge models to support further interoperability and further service discoverability and the added-values of using the Data Catalog (DCAT) or Semantic Registry Information Model (SRIM) to better describe and retrieve ATM services." + "@value": "GeoPose 1.0 is an OGC Implementation Standard for exchanging the location and orientation of real or virtual geometric objects (“Poses”) within reference frames anchored to the earth’s surface (“Geo”) or within other astronomical coordinate systems.\r\n\r\nThe standard specifies two Basic forms with no configuration options for common use cases, an Advanced form with more flexibility for more complex applications, and five composite GeoPose structures that support time series plus chain and graph structures.\r\n\r\nThese eight Standardization Targets are independent. There are no dependencies between Targets and each may be implemented as needed to support a specific use case.\r\n\r\nThe Standardization Targets share an implementation-neutral Logical Model which establishes the structure and relationships between GeoPose components and also between GeoPose data objects themselves in composite structures. Not all of the classes and properties of the Logical Model are expressed in individual Standardization Targets nor in the specific concrete data objects defined by this standard. Those elements that are expressed are denoted as implementation-neutral Structural Data Units (SDUs). SDUs are aliases for elements of the Logical Model, isolated to facilitate specification of their use in encoded GeoPose data objects for a specific Standardization Target.\r\n\r\nFor each Standardization Target, each implementation technology and corresponding encoding format defines the encoding or serialization specified in a manner appropriate to that technology.\r\n\r\nGeoPose 1.0 specifies a single encoding in JSON format (IETF RFC 8259). Each Standardization Target has a JSON Schema (Internet-Draft draft-handrews-json-schema-02) encoding specification. The key standardization requirements specify that concrete JSON-encoded GeoPose data objects must conform to the corresponding JSON Schema definition. The individual elements identified in the encoding specification are composed of SDUs, tying the specifications back to the Logical Model.\r\n\r\nThe GeoPose 1.0 Standard makes no assumptions about the interpretation of external specifications, for example, of reference frames. Nor does it assume or constrain services or interfaces providing conversion between GeoPoses of difference types or relying on different external reference frame definitions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68697,35 +68836,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-022r1" + "@value": "21-056r11" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: SWIM Information Registry Engineering Report" + "@value": "OGC GeoPose 1.0 Data Exchange Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-042", + "@id": "http://www.opengis.net/def/docs/15-003", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-03-15" + "@value": "2015-07-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff de La Beaujardiere" + "@value": "David Graham" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -68735,27 +68874,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=14416" + "@id": "https://portal.ogc.org/files/?artifact_id=61935" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-042" + "@value": "Common DataBase Volume 1 Main Body" }, { "@language": "en", - "@value": "Web Map Service (WMS) Implementation Specification" + "@value": "15-003" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Web Map Service Interface Standard (WMS) provides a simple HTTP interface for requesting geo-registered map images from one or more distributed geospatial databases. A WMS request defines the geographic layer(s) and area of interest to be processed. The response to the request is one or more geo-registered map images (returned as JPEG, PNG, etc) that can be displayed in a browser application. The interface also supports the ability to specify whether the returned images should be transparent so that layers from multiple servers can be combined or not.

NOTE: WMS 1.3 and ISO 19128 are the same documents." + "@value": "The Common DataBase (CDB) Specification provides the means for a single, versionable, simulation-rich, synthetic representation of the earth. A database that conforms to this Specification is referred to as a Common DataBase or CDB. A CDB provides for a synthetic environment repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB can be used as a common on-line (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks; in this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time.\r\nThe application of CDB to future simulator architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the HLA/FOM and DIS protocols, the application of the CDB Specification provides a Common Environment to which inter-connected simulators share a common view of the simulated environment.\r\nThe CDB Specification is an open format Specification for the storage, access and modification of a synthetic environment database. The Specification defines the data representation, organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The Specification makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry.\r\nThe CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. It encompasses the terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the synthetic environment includes the specific attributes of the synthetic environment data as well as their relationships.\r\nA CDB contains datasets organized in layers, tiles and levels-of-detail; together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB is specifically tailored for real-time applications. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68766,30 +68905,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-042" + "@value": "15-003" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Map Service (WMS) Implementation Specification" + "@value": "OGC Common DataBase Volume 1 Main Body" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-043r3", + "@id": "http://www.opengis.net/def/docs/17-007r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-10-28" + "@value": "2019-01-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Aleksandar Jelenak, Ted Habermann, Gerd Heber" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -68804,17 +68943,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/18-043r3/18-043r3.html" + "@id": "https://docs.ogc.org/is/17-007r1/17-007r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Hierarchical Data Format Version 5 (HDF5®) Core Standard" + "@value": "Web Services Security" }, { "@language": "en", - "@value": "18-043r3" + "@value": "17-007r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -68824,7 +68963,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Hierarchical Data Format Version 5 (HDF5®) is a data model, a programming interface, and a storage model for keeping and managing data. It supports an unlimited variety of data types, and is designed to be flexible and efficient for large and complex data. HDF5 is extensible via customizing data types, allowing communities and their applications to evolve in the use of HDF5.\r\n\r\nThis document describes the HDF5 data model as an encoding standard particularly suitable to scientific and engineering geospatial applications that employ multidimensional numeric arrays to describe temporally and spatially varying phenomena. The data model is simple yet versatile, capable of supporting complex data relationships and dependencies through its grouping and linking mechanisms. It is also self-describing by accommodating user-defined metadata." + "@value": "This standard applies to a deployed OGC Web Service instance for which the protocol scheme of all operation endpoint URLs, exposed in the Capabilities document, is ‘https’ as defined in RFC 7230, section 2.7.2.\r\n\r\nA security-annotated Capabilities document is one which uses the element(s) to express the existence of security controls on the operation of the service instance or support for a particular security feature. Applying the tests as defined in the Annexes can validate compliance for a service, the client and the OGC management process. Basically, a service can be described by a Capabilities document that includes security annotations as defined in this standard. A client loading these Capabilities and parse for the element(s) can determine the security controls implemented for each operation of the service instance. The string value of this element’s name attribute contains the identifier of the implemented requirements class.\r\n\r\nHow the client obtains the security-annotated capabilities is out of scope for this standard.\r\n\r\nThis standard defines one common abstract Requirements Class and three Capabilities document structure specific Requirements Classes. The structure specific classes address how the requirements are implemented for WMS 1.1.1, WMS 1.3 and OWS Common based service Capabilities documents.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68835,25 +68974,25 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-043r3" + "@value": "17-007r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Hierarchical Data Format Version 5 (HDF5®) Core Standard" + "@value": "OGC Web Services Security" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-043r3", + "@id": "http://www.opengis.net/def/docs/06-023r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-10" + "@value": "2006-08-08" } ], "http://purl.org/dc/terms/creator": [ @@ -68863,7 +69002,7 @@ ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cr" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -68873,27 +69012,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=17909" + "@id": "https://portal.ogc.org/files/?artifact_id=16339" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-043r3" + "@value": "06-023r1" }, { "@language": "en", - "@value": "WCS: Add Transaction operation" + "@value": "Definition identifier URNs in OGC namespace" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cr" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Specify an additional optional " + "@value": "*** Corrigendum - updated 2006-08-08 ***\r\n\r\nThis revised version of this document adds additional allowed authority and objectType values, plus specifies URNs for data types, as proposed in change requests OGC 05-091r2 and 05-060. In addition, corrections have been made to the XML documents listed in Annex A. The changes made in this version are tracked in the Microsoft Word (.doc) format of this document.

This Best Practices Paper specifies Universal Resource Names (URNs) in the ogc URN namespace to be used for identifying definitions. This document specifies the formats used by these URNs, plus a set of specific URNs for specific definitions. These definitions should be used wherever applicable by implementations of various OGC Implementation Specifications, including GML, WMS, WFS, and WCS." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68904,35 +69043,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-043r3" + "@value": "06-023r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Change Request: WCS: Add Transaction operation" + "@value": "Definition identifier URNs in OGC namespace" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-065", + "@id": "http://www.opengis.net/def/docs/19-008r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-07-09" + "@value": "2019-09-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steve Thompson " + "@value": "Emmanuel Devys, Ted Habermann, Chuck Heazel, Roger Lott, Even Rouault" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -68942,27 +69081,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=92038" + "@id": "https://docs.ogc.org/is/19-008r4/19-008r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OpenFlight Scene Description Database Specification 16.0 Community Standard" + "@value": "GeoTIFF Standard" }, { "@language": "en", - "@value": "19-065" + "@value": "19-008r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the OpenFlight Scene Description Database Specification, commonly\r\nreferred to as simply “OpenFlight”. OpenFlight is a 3D scene description file format that was\r\ncreated and is maintained by Presagis. While OpenFlight databases are typically created and edited\r\nusing Presagis software tools, the format is widely adopted and as a result, many tools exist\r\nto read and write OpenFlight database files.\r\nThe primary audience for this document includes software developers whose applications are\r\nintended to read and/or write OpenFlight database files. To this end, this document discusses\r\nconcepts incorporated in OpenFlight and contains a detailed description of the physical layout\r\nof OpenFlight files as represented on disk." + "@value": "This OGC Standard defines the Geographic Tagged Image File Format (GeoTIFF) by specifying requirements and encoding rules for using the Tagged Image File Format (TIFF) for the exchange of georeferenced or geocoded imagery. The OGC GeoTIFF 1.1 standard formalizes the existing community GeoTIFF specification version 1.0 and aligns it with the continuing addition of data to the EPSG Geodetic Parameter Dataset." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -68973,35 +69112,42 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-065" + "@value": "19-008r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC OpenFlight Scene Description Database Specification 16.0 Community Standard" + "@value": "OGC GeoTIFF Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-029r1", + "@id": "http://www.opengis.net/def/docs/06-035r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-08" + "@value": "2006-05-02" + }, + { + "@type": "xsd:date", + "@value": "2006-07-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Benjamin Pross, Christoph Stasch" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -69011,27 +69157,40 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-029r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=14895" + }, + { + "@id": "https://portal.ogc.org/files/?artifact_id=14022" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-13: Workflows ER" + "@value": "Web Coverage Processing Service" }, { "@language": "en", - "@value": "17-029r1" + "@value": "Web Coverage Processing Service (WCPS)" + }, + { + "@language": "en", + "@value": "06-035r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) addresses the development of a consistent, flexible, adaptable workflow that will run behind the scenes. A user should be able to discover existing workflows via a catalog and execute them using their own datasets. An expert should be able to create workflows and to publish them. Previous OGC Testbed initiatives investigated workflows in the geospatial domain:\r\n\r\nOWS 3 Imagery Workflow Experiments\r\n\r\nOWS 4 WPS IPR Workflow descriptions and lessons learned\r\n\r\nOWS 4 Topology Quality Assessment Interoperability Program Report\r\n\r\nOWS 5 Data View Architecture Engineering Report\r\n\r\nOWS 6 Geoprocessing Workflow Architecture Engineering Report\r\n\r\nThese initiatives mostly favored Business Processing Execution Language (BPEL) as the workflow execution language. More recent studies ([6], [7]) were performed using BPMN as a means for describing and executing workflows comprised of OGC Web services. This ER will give an overview about existing approaches to compose and execute geospatial workflows and will describe the approach taken in Testbed-13, taking into account security aspects." + "@value": "The Web Coverage Processing Service (WCPS) supports retrieval and processing of geo-spatial coverage data. WCPS grounds on the coverage model of the OGC Web Coverage Service (WCS) Implementation Specification where coverages are defined as digital geospatial information representing space-varying phenomena, currently constrained to equally spaced grids." + }, + { + "@value": "The Web Coverage Processing Service (WCPS) supports retrieval and processing of geo-spatial coverage data. WCPS uses the coverage model of the OGC Web Coverage Service (WCS) Implementation Specification: coverages are defined as digital geo-spatial information representing space-varying phenomena, currently constrained to equally spaced grids." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69042,18 +69201,22 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-029r1" + "@value": "06-035r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: Workflows ER" + "@value": "Web Coverage Processing Service" + }, + { + "@language": "en", + "@value": "Web Coverage Processing Service (WCPS)" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-157", + "@id": "http://www.opengis.net/def/docs/13-021r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], @@ -69065,12 +69228,12 @@ ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó" + "@value": "Peter Taylor" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -69080,27 +69243,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=52757" + "@id": "https://portal.ogc.org/files/?artifact_id=54423" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-9 Engineering Report - OWS Innovations - Map Tiling Methods Harmonization" + "@value": "13-021r3" }, { "@language": "en", - "@value": "12-157" + "@value": "WaterML2.0 - part 2: Ratings, Gaugings and Sections Discussion Paper" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report proposes a profile for WMTS that limits the flexibility or the standard and mimics what some other tile initiatives are doing. It also proposes some improvements in WMTS to accommodate the need for requesting several tiles of a region at different scales that has been identified by the GeoPackage team. These recommendations help to better harmonize OSGeo tile standards and mass-market technologies." + "@value": "This document describes an information model for exchanging rating tables, or rating\r\ncurves, that are used for the conversion of related hydrological phenomenon. It also\r\ndescribes a model describing the observations that are used to develop such relationships,\r\noften referred to as gauging observations.\r\nThe information model is proposed as a second part of the WaterML2.0 suite of\r\nstandards, building on part 1 that addresses the exchange of time series1." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69111,35 +69274,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-157" + "@value": "13-021r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-9 Engineering Report - OWS Innovations - Map Tiling Methods Harmonization" + "@value": "WaterML2.0 - part 2: Ratings, Gaugings and Sections Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-010", + "@id": "http://www.opengis.net/def/docs/12-128r12", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-06-14" + "@value": "2015-08-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Robert Thomas, Sara Saeedi" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -69149,27 +69312,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-010.html" + "@id": "https://portal.ogc.org/files/?artifact_id=64506" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-010" + "@value": "GeoPackage Encoding Standard" }, { "@language": "en", - "@value": "Towards a Federated Marine SDI: Connecting Land and Sea to Protect the Arctic Environment Engineering Report" + "@value": "12-128r12" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report (ER) summarizes the main achievements of the Federated Marine Spatial Data Infrastructure (FMSDI) Pilot Phase 3. It focused on a variety of aspects contributing to an overarching scenario to aid in the better understanding of both the challenges and potential opportunities for coastal communities, ecosystems, and economic activities in the Arctic region.\r\n\r\nThe sub-scenarios, i.e., those scenarios developed by each participant, address aspects of the changing Arctic landscape. These activities included the following.\r\n\r\nA sea-based, health and safety scenario incorporating the land/sea interface in the Arctic. This scenario demonstrates the technology and data used with OGC, IHO, and other community standards in response to a grounding event and the evacuation of an expedition cruise ship or research vessel in the Arctic. Demonstrating interoperability between land and marine data that is necessary to aid first responders and other stakeholders. This scenario incorporates, but is not be limited to:\r\n\r\nvoyage planning information (e.g., Arctic Voyage Planning Guide, Safety of Navigation products and services, Maritime Safety Information);\r\n\r\nland-based emergency services/resources (e.g., Coast Guard stations, transit times to emergency services or ports, medical facilities and resources, helicopter access);\r\n\r\ncoastal environmental/topographic/hydrographic/maintenance data (e.g., deposition and dredging of seafloor sediment, changes in coastline and bathymetry); and\r\n\r\nglobal maritime traffic data in the Arctic (e.g., to help assess likelihood of other ships in responding to a ship in distress).\r\n\r\nDemonstrating interoperability between land and marine data that is necessary to understand coastal erosion (e.g., ocean currents, geology, permafrost characteristics, etc.).\r\n\r\nGeneral sensitivity to climate change." + "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector\r\ngeospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access\r\nand update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that\r\nguarantees data model and data set integrity and identical access and update results in response to identical requests from different\r\nclient applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly\r\nuseful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69180,30 +69343,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-010" + "@value": "12-128r12" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Towards a Federated Marine SDI: Connecting Land and Sea to Protect the Arctic Environment Engineering Report" + "@value": "OGC® GeoPackage Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-018r2", + "@id": "http://www.opengis.net/def/docs/16-004r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-01-21" + "@value": "2017-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Philippe M" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -69218,17 +69381,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=25199" + "@id": "https://portal.ogc.org/files/?artifact_id=72716" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Sensor Planning Service Application Profile for EO Sensors" + "@value": "16-004r3" }, { "@language": "en", - "@value": "07-018r2" + "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -69238,7 +69401,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The SPS configuration proposed in this profile is intended to support the programming process of Earth Observation (EO) sensors system. This profile describes a consistent SPS configuration that can be supported by many satellite data providers, most of whom have existing facilities for the management of these programming requests." + "@value": "(RCS) data within a conformant CDB data store. \r\nPlease note that the current CDB standard only provides encoding rules for using Esri ShapeFiles for storing RCS models. However, this Best Practice has been modified to change most of the ShapeFile references to “vector data sets” or “vector attributes” and “Point Shapes” to “Point geometries”. This was done in recognition that future versions of the CDB standard and related Best Practices will provide guidance on using other encodings/formats, such as OGC GML.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69249,35 +69412,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-018r2" + "@value": "16-004r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Sensor Planning Service Application Profile for EO Sensors" + "@value": "Volume 5: OGC CDB Radar Cross Section (RCS) Models" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-080r2", + "@id": "http://www.opengis.net/def/docs/16-052", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-01-22" + "@value": "2017-05-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Brackin, Pedro Gonçalves " + "@value": "Joan Masó" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -69287,27 +69450,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55182" + "@id": "https://docs.ogc.org/per/16-052.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-080r2" + "@value": "16-052" }, { "@language": "en", - "@value": "OWS Context Conceptual Model" + "@value": "Testbed-12 OWS Context / Capabilities Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard describes the use cases, requirements and conceptual model for the OWS Context encoding standard. The goal of this standard is to provide a core model, which is extended and encoded as defined in extensions to this standard. A ‘context document’ specifies a fully configured service set which can be exchanged (with a consistent interpretation) among clients supporting the standard.\r\nThe OGC Web Services Context Document (OWS Context) was created to allow a set of configured information resources (service set) to be passed between applications primarily as a collection of services. OWS Context is developed to support in-line content as well. The goal is to support use cases such as the distribution of search results, the exchange of a set of resources such as OGC Web Feature Service (WFS), Web Map Service (WMS), Web Map Tile Service (WMTS), Web Coverage Service (WCS) and others in a ‘common operating picture’. Additionally OWS Context can deliver a set of configured processing services (Web Processing Service (WPS)) parameters to allow the processing to be reproduced on different nodes.\r\nOWS Context is aimed at replacing previous OGC attempts at providing such a capability (the Web Map Context WMC) which was reasonably successful but limited to WMS. Other work on the ‘Location Organizer Folder (LOF)’ was also taken into consideration. The concept of OWS Context, and the first prototype document was produced as part of OGC testbed OWS-7. See OGC 10-035r1, Information Sharing Engineering Report. In order to achieve mass market appeal, as well as being useful to a wider community, the use of OWS Context support to other existing standards was considered. Multiple encoding formats for OWS Context have been developed (ATOM, JSON). Each of these is described in a separate OWS Context Extensions to the Core model.\r\nThis document concentrates on describing the OWS Context Model in abstract terms using UML. The document defines requirements and use cases. It also includes an abstract test suite to verify that encodings are compliant with the core specification. The intent of OWS Context is to allow many types of OGC Data Delivery service to be referenced and therefore exploited (for example, not just WMS but also WFS, WCS and WPS) but it does not explicitly define the encoding of these services in the core (only the general approach to be used for different types of service interface). Service explicit encodings are defined within the extension documents for ATOM and JSON.\r\nThe abbreviation owc is used throughout this document for OWS Context.\r\n" + "@value": "The OGC service metadata document (sometimes also called capabilities document) is a key part in the service discovery. It describes the service and also the resources that the service expose. Resources are listed in the service metadata document inside a section named as Contents by OWS Common. There are two main limitations to the current Contents section approach:\r\n\r\nOWS Common offers flexibility for describing resources and it only proposes a very minimum set of metadata in figure 7 of OGC 06-121r9 called DatasetSummary that need to be sub-classed (i.e. extended) by any specific application. As a result, each standard proposes its own alternative for it. Integrated client developers need to implement them separately.\r\n\r\nIf the number of resources is very large or the service is highly dynamic, the Contents section can be too long or useless and neither the service nor the client can handle it efficiently.\r\n\r\nThis Engineering Report proposes a double solution to the Contents section of the service metadata documents: It proposes ways to encode the Contents section using the OWS Context encoding data types and it introduces the use OpenSearch as a way to request a subset of the resources that the service can provide access to. In that sense, the use of the OGC 10-032r8 OpenSearchGeo can provide the long time needed geospatial and temporal filter capabilities." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69318,30 +69481,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-080r2" + "@value": "16-052" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC OWS Context Conceptual Model" + "@value": "Testbed-12 OWS Context / Capabilities Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-027r2", + "@id": "http://www.opengis.net/def/docs/17-061", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-12-20" + "@value": "2020-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sam Meek" + "@value": "Terry Idol" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -69356,17 +69519,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-027r2.html" + "@id": "https://portal.ogc.org/files/17-061" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-027r2" + "@value": "17-061" }, { "@language": "en", - "@value": "OGC Testbed-15: Machine Learning Engineering Report" + "@value": "FGDC OGC Application Programming Interface Interoperability Assessment" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -69376,7 +69539,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Machine Learning (ML) Engineering Report (ER) documents the results of the ML thread in OGC Testbed-15. This thread explores the ability of ML to interact with and use OGC web standards in the context of natural resources applications. The thread includes five scenarios utilizing seven ML models in a solution architecture that includes implementations of the OGC Web Processing Service (WPS), Web Feature Service (WFS) and Catalogue Service for the Web (CSW) standards. This ER includes thorough investigation and documentation of the experiences of the thread participants." + "@value": "The Federal Geographic Data Committee (FGDC) Application Programming Interface (API) assessment was conducted under the OGC Innovation Program with the goal to develop an in-depth understanding of all the components necessary to enable increased coordination and effectiveness of APIs as applied to geospatial information. FGDC customers have been invited to share their experiences with the use of APIs. From those descriptions, recommendations have been derived that help FGDC to better understand how APIs are currently being generated and if using a more standardized approach to APIs might enable a more robust and optimized service offering. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69387,35 +69550,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-027r2" + "@value": "17-061" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Machine Learning Engineering Report" + "@value": "FGDC OGC Application Programming Interface Interoperability Assessment" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-015", + "@id": "http://www.opengis.net/def/docs/05-095r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-25" + "@value": "2006-07-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "EO2HEAVEN Consortium" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -69425,27 +69588,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=52675" + "@id": "https://portal.ogc.org/files/?artifact_id=13204" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "13-015" + "@value": "GML 3.1.1 common CRSs profile" }, { "@language": "en", - "@value": "Provision of Observations through an OGC Sensor Observation Service (SOS)" + "@value": "05-095r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document comprises experiences and recommendations when using\r\nSensor Web Enablement (SWE) concepts. This document focuses on\r\none basic issue: the provision of observations in an OGC SOS.\r\nThis includes the definition of a lightweight OGC SOS profile (OGC 11-\r\n169r1), an analysis of and contribution to the specification of the Sensor\r\nObservation Service (SOS) 2.0 as well as an approach how the data\r\nused within Earth observation (EO) applications can be integrated more\r\neasily into SOS instances.\r\nThese recommendations result from the work performed in 2010-2013\r\nas part of the research project EO2HEAVEN (Earth Observation and\r\nEnvironmental Modelling for the Mitigation of Health Risks), co-funded\r\nby the European Commission as part of the 7th Framework Programme\r\n(FP7) Environmental theme. EO2HEAVEN contributes to a better understanding\r\nof the complex relationships between environmental changes\r\nand their impact on human health. See http://www.eo2heaven.org/ .\r\nThe lightweight OGC SOS profile has been developed in close cooperation\r\nbetween the FP7 projects EO2HEAVEN and UncertWeb (see\r\nhttp://www.uncertweb.org/ )." + "@value": "This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding definitions of commonly-used Coordinate Reference Systems (CRSs) plus related coordinate Conversions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69456,30 +69619,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-015" + "@value": "05-095r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Best Practice for Sensor Web Enablement: Provision of Observations through an OGC Sensor Observation Service (SOS)" + "@value": "GML 3.1.1 common CRSs profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-021", + "@id": "http://www.opengis.net/def/docs/17-045", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-11" + "@value": "2018-03-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Stephane Fellah" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -69494,17 +69657,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-021.html" + "@id": "https://docs.ogc.org/per/17-045.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-13: Security Engineering Report" + "@value": "17-045" }, { "@language": "en", - "@value": "17-021" + "@value": "Testbed-13: Portrayal Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -69514,7 +69677,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Security Engineering Report (ER) covers two Testbed 13 topics:\r\n\r\nThe implementation of authentication and authorization plugins for the QGIS open source desktop GIS client and\r\n\r\nthe implementation of secured workflow.\r\n\r\nThe authentication plugins implement the SAML2 ECP with PAOS binding and IdP discovery from the SAML2 federation metadata URL. The access right delegation plugin implements applicable OAuth2 grant types.\r\n\r\nRegarding the first topic, this ER discusses the fit for purpose aspects for the OAuth2 and SAML2 in the context of an open source desktop application. It also covers the QGIS development as well as building and deployment aspects. Most of the work related to this topic was provided by Secure Dimensions.\r\n\r\nRegarding the second topic, this ER outlines the architecture approach and the implications to implementations for security in OGC service workflows as well as the implementation approach itself. Most of the work related to this topic was provided by 52°North." + "@value": "Portrayal of geospatial information plays a crucial role in situation awareness, analysis and decision-making. Visualizing geospatial information often requires one to portray the information using symbology or cartographic presentation rules from a community or organization. For example, among those in the law enforcement, fire and rescue community, various local, national and international agencies use different symbols and terminology for the same event, location and building, employing syntactic, structural-based and document-centric data models (e.g., eXtensible Markup Language (XML) schemas and Style Layer Descriptors (SLD)). With this approach, interoperability does not extend to the semantic level, which makes it difficult to share, reuse and mediate unambiguous portrayal information between agencies.\r\n\r\nThis Engineering Report (ER) captures the requirements, solutions, models and implementations of the Testbed 13 Portrayal Package. This effort leverages the work on Portrayal Ontology development and Semantic Portrayal Service conducted during Testbed 10, 11 and 12. The objective of this Testbed 13 is to identify and complete the gaps in the latest version of the portrayal ontology defined in Testbed 12, complete the implementation of the Semantic Portrayal Service by adding rendering capabilities and performing a demonstration of the portrayal service that showcases the benefits of the proposed semantic-based approach." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69525,30 +69688,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-021" + "@value": "17-045" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: Security Engineering Report" + "@value": "OGC Testbed-13: Portrayal Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-065", + "@id": "http://www.opengis.net/def/docs/17-066r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-03-05" + "@value": "2022-05-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthias Mueller" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -69563,17 +69726,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/14-065/14-065r0.html" + "@id": "https://docs.ogc.org/is/17-066r2/17-066r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "WPS 2.0 Interface Standard" + "@value": "17-066r2" }, { "@language": "en", - "@value": "14-065" + "@value": "OGC GeoPackage Extension for Tiled Gridded Coverage Data" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -69583,7 +69746,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "" + "@value": "The GeoPackage Extension for Tiled Gridded Coverage Data” (TGCE) extension (previously titled Elevation Extension) defines how to encode and store tiled regular gridded data, such as a digital elevation model, in a GeoPackage. The tiles contain values, such as elevation, temperature or pressure, and the extension defines two encodings. The PNG encoding uses PNG files to store 16-bit integer values and a scale and offset may be applied to fine-tune the coverage range. To support 32-bit floating point data or binary data, the extension also defines a TIFF encoding. In this encoding, TIFF files are used to store IEEE floating point or a binary data type where the SampleFormat has a value of either 1 (unsigned integer) or 2 (signed integer) AND the BitsPerSample is either 8, 16, or 32. To simplify development, this encoding constrains many of the TIFF options to the minimal set needed to meet the floating-point requirement. The extension also defines two ancillary data tables: one for regular gridded coverages and one for tiles.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69594,35 +69757,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-065" + "@value": "17-066r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® WPS 2.0 Interface Standard" + "@value": "OGC GeoPackage Extension for Tiled Gridded Coverage Data" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-022", + "@id": "http://www.opengis.net/def/docs/15-120r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-01-21" + "@value": "2018-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Alex Robin" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -69632,27 +69795,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-022.html" + "@id": "https://portal.ogc.org/files/?artifact_id=82376" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-022" + "@value": "15-120r5" }, { "@language": "en", - "@value": "OGC Testbed-17: Sensor Integration Framework Assessment ER" + "@value": "Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 17 Engineering Report (ER) documents the outcomes of a review and implementation of the Sensor Integration Framework Standards Profile (SIF-SP) v1.0.1, published by the National Center for Geospatial Intelligence Standards (NCGIS).\r\n\r\nThe Sensor Integration Framework Standard Profiles (SIF-SP) authors rightly acknowledge that sensing systems and the environments they operate in (e.g. hardware platform, computing resources, connectivity, ease of deployment, etc.) are very heterogeneous and that there will never be a single suite of technology or standards that can support the goal of providing unified access to sensor deployments employed in complex applications.\r\n\r\nInstead, rather than trying to impose a single standard or suite of standards, the SIF-SP approach defines common conceptual models that can be mapped to existing and future standards, thus allowing integration of all these standards in a single framework.\r\n\r\nThis approach is fully compatible with the OGC Sensor Web Enablement (SWE) suite of standards that were designed for this type of integration. Thus, existing and upcoming SWE standards defined in the OGC can be used as the central pillar of a SIF implementation. The test implementation developed in this testbed, and based on OpenSensorHub, focused on demonstrating this aspect.\r\n\r\nIn addition to a thorough review of the SIF material — including standards documents, UML models and ontologies — a prototype implementation of the SIF standards was created during the Testbed using OpenSensorHub. This allowed the testbed participants to check the practical feasibility of fulfilling the SIF requirements using the OGC SWE suite of standards. Details and feedback regarding this implementation are also provided in this ER.\r\n\r\nSuggestions to improve SIF-SP and make it an integral part of the OGC standard baseline are also provided.\r\n\r\n" + "@value": "The CDB standard defines a standardized model and structure for a single, “versionable,” virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69663,35 +69826,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-022" + "@value": "15-120r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: Sensor Integration Framework Assessment ER" + "@value": "Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-132", + "@id": "http://www.opengis.net/def/docs/21-070", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-11-05" + "@value": "2022-07-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas Everding, Johannes Echterhoff" + "@value": "Steve Liang" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -69701,27 +69864,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=29566" + "@id": "https://docs.ogc.org/bp/21-070/21-070.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Event Pattern Markup Language (EML)" + "@value": "21-070" }, { "@language": "en", - "@value": "08-132" + "@value": "OGC Integrated Methane Sensor Web for Emissions Management Best Practice - Part I - Fugitive Emissions Management based on AE" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Event Pattern Markup Language (EML) allows one to describe event patterns for event (stream) processing and analysis. It can be used to build multi stage filters for incoming events but also to derive higher information through combining and correlating multiple events. It can be applied on single events but is focused on handling of continuous event streams." + "@value": "Methane (CH4) is one of the most potent greenhouse gases, and the comparative impact of methane is 25 times greater than CO2 over a 100-year period. Methane is an invisible and odorless gas, and it is very labor intensive and time consuming in order to detect and repair leaks. Regulations play a critical role in methane emissions reduction, and how methane emissions are detected, repaired, and managed is highly dependent on local regulations. This OGC Best Practice document defines a SensorThings API for fugitive methane emissions management." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69732,35 +69895,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-132" + "@value": "21-070" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Event Pattern Markup Language (EML)" + "@value": "OGC Integrated Methane Sensor Web for Emissions Management Best Practice - Part I - Fugitive Emissions Management based on AE" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-066r1", + "@id": "http://www.opengis.net/def/docs/12-081", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-08-29" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jean-Philippe Humblet" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/pol-nts" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -69770,27 +69933,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1181" + "@id": "https://portal.ogc.org/files/?artifact_id=51856" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "02-066r1" + "@value": "Name type specification – ontology resources" }, { "@language": "en", - "@value": "Web Map Context Documents" + "@value": "12-081" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/pol-nts" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "States how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent manner." + "@value": "An OGC name is required for ontology resources published by OGC. This includes OWL\r\nontologies, classes and properties." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69801,35 +69964,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-066r1" + "@value": "12-081" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Map Context Documents" + "@value": "Name type specification – ontology resources" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-029r1", + "@id": "http://www.opengis.net/def/docs/01-004", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-12" + "@value": "2001-01-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Louis Burry" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -69839,27 +70002,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-029r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=6628" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 GeoPackage Routing and Symbology Engineering Report" + "@value": "Grid Coverage Service Implementation Specification" }, { "@language": "en", - "@value": "16-029r1" + "@value": "01-004" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) describes the results of experiments in OGC Testbed 12 designed to potentially enhance capabilities for symbology and routing [1] as extensions to the OGC GeoPackage standard. These experiments focused on 1.) methods for providing mounted and/or dismounted (off-road) routing within GeoPackage and 2.) mechanisms for providing user-defined map symbology for features in a GeoPackage structured data store. This ER documents the different approaches considered, design decisions and rationales, limitations, and issues encountered during prototype implementation.\r\n\r\n" + "@value": "**This document has been retired. It is not supported. You should consider using Web Coverage Service.**\r\n\r\n This specification was designed to promote interoperability between software implementations by data vendors and software vendors providing grid analysis and processing capabilities." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69870,35 +70033,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-029r1" + "@value": "01-004" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 GeoPackage Routing and Symbology Engineering Report" + "@value": "OpenGIS Grid Coverage Service Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-010r7", + "@id": "http://www.opengis.net/def/docs/19-010r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-05-21" + "@value": "2019-12-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -69908,27 +70071,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1345" + "@id": "https://docs.ogc.org/per/19-010r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Recommended XML Encoding of CRS Definitions" + "@value": "19-010r2" }, { "@language": "en", - "@value": "03-010r7" + "@value": "OGC Testbed-15: Styles API Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OpenGIS Recommendation Paper specifies basic XML encoding of data defining coordinate reference systems and coordinate operations. This encoding is expected to be adapted and used by multiple OGC\r\nImplementation Specifications, by the separate specification of Application Schemas. This document is a Recommendation Paper because the specified encoding is more general\r\nthan an OpenGIS Implementation Specification and more specific than the OpenGIS Abstract Specification." + "@value": "This document is a proof of concept of a draft specification of the OGC Styles Application Programming Interface (API) that defines a Web API that enables map servers and clients as well as visual style editors to manage and fetch styles.\r\n\r\nWeb APIs are software interfaces that use an architectural style that is founded on the technologies of the Web. Styles consist of symbolizing instructions that are applied by a rendering engine on features and/or coverages.\r\n\r\nThe Styles API supports several types of consumers, mainly:\r\n\r\nVisual style editors that create, update and delete styles for datasets that are shared by other Web APIs implementing the OGC API - Features - Part 1: Core standard or the draft OGC API - Coverages or draft OGC API - Tiles specifications;\r\n\r\nWeb APIs implementing the draft OGC API - Maps specification fetch styles and render spatial data (features or coverages) on the server;\r\n\r\nMap clients that fetch styles and render spatial data (features or coverages) on the client.\r\n\r\nFeature data is either accessed directly or organized into spatial partitions such as a tiled data store (aka vector tiles).\r\n\r\nThe Styles API is consistent with the emerging OGC API family of standards.\r\n\r\nThe Styles API implements the conceptual model for style encodings and style metadata as documented in chapter 6 of the OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report.\r\n\r\nThe model defines three main concepts:\r\n\r\nThe style is the main resource.\r\n\r\nEach style is available in one or more stylesheets - the representation of a style in an encoding like OGC SLD 1.0 or Mapbox Style. Clients will use the stylesheet of a style that fits best based on the capabilities of available tools and their preferences.\r\n\r\nFor each style there is style metadata available, with general descriptive information about the style, structural information (e.g., layers and attributes), and so forth to allow users to discover and select existing styles for their data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -69939,35 +70102,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-010r7" + "@value": "19-010r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Recommended XML Encoding of CRS Definitions" + "@value": "OGC Testbed-15: Styles API Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-100r1", + "@id": "http://www.opengis.net/def/docs/14-007", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-06-23" + "@value": "2014-07-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cliff Kottman" + "@value": "Matthes Rieke" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -69977,27 +70140,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=11496" + "@id": "https://portal.ogc.org/files/?artifact_id=58931" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "99-100r1" + "@value": "14-007" }, { "@language": "en", - "@value": "Topic 0 - Overview" + "@value": "Testbed 10 Report on Aviation Binding AIXM to Development Tools" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Introduction and roadmap to the Abstract specification." + "@value": "This document is a deliverable of the OGC Testbed 10 (Testbed-10). Its contents cover the summary of the work carried out regarding the creation and evaluation of generated data bindings for the Aeronautical Information Exchange Model (AIXM) for established programming languages.\r\nSuggested additions, changes, and comments on this draft report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70008,35 +70171,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-100r1" + "@value": "14-007" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 0 - Overview" + "@value": "OGC® Testbed 10 Report on Aviation Binding AIXM to Development Tools" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-133", + "@id": "http://www.opengis.net/def/docs/15-113r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-10-10" + "@value": "2017-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff, Thomas Everding" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70046,27 +70209,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=29576" + "@id": "https://portal.ogc.org/files/?artifact_id=72712" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-133" + "@value": "15-113r3" }, { "@language": "en", - "@value": "Sensor Event Service Interface Specification" + "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Sensor Event Service (SES) provides operations to register sensors at the service application and let clients subscribe for observations available at the service. The service performs filtering of sensor data (streams) based upon the filter criteria defined in these subscriptions. Filters can be applied on single observations but also on observation streams, potentially aggregating observations into higher-level information (which itself can be regarded as observation data). Whenever matches are discovered, a notification is sent to the subscriber, using asynchronous, push-based communication mechanisms." + "@value": "The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time.\r\nThe application of CDB to future simulation architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the High Level Architecture - -Federation Object Model (HLA/FOM) and DIS protocols, the application of the CDB standard provides a Common Environment to which inter-connected simulators share a common view of the simulated environment.\r\nThe CDB standard defines an open format for the storage, access and modification of a synthetic environment database. A synthetic environment is a computer simulation that represents activities at a high level of realism, from simulation of theaters of war to factories and manufacturing processes. These environments may be created within a single computer or a vast distributed network connected by local and wide area networks and augmented by super-realistic special effects and accurate behavioral models. SE allows visualization of and immersion into the environment being simulated . \r\nThis standard defines the organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The standard makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. A series of associated OGC Best Practice documents define rules and guidelines for data representation of real world features.\r\nThe CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. A CDB data store can include terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the data store can includes the specific attributes of the synthetic environment data as well as their relationships.\r\nThe associated CDB Standard Best Practice documents provide a description of a data schema for Synthetic Environmental information (i.e. it merely describes data) for use in simulation. The CDB Standard provides a rigorous definition of the semantic meaning for each dataset, each attribute and establishes the structure/organization of that data as a schema comprised of a folder hierarchy and files with internal (industry-standard) formats.\r\nA CDB conformant data store contains datasets organized in layers, tiles and levels-of-detail. Together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB compliant data store is specifically tailored for real-time applications.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70077,35 +70240,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-133" + "@value": "15-113r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS® Sensor Event Service Interface Specification" + "@value": "Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-002r5", + "@id": "http://www.opengis.net/def/docs/11-019r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-04-20" + "@value": "2012-04-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Luis Bermudez" + "@value": "Chris Higgins" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70115,27 +70278,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://docs.opengeospatial.org/wp/15-002r5/15-002r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=47852" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-002r5" + "@value": "11-019r2" }, { "@language": "en", - "@value": "OGC Compliance Overview - Guide for Software Acquisition" + "@value": "Engineering Report for the OWS Shibboleth Interoperability Experiment" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Open Geospatial Consortium (OGC®) provides international standards that are implemented worldwide in thousands of applications that use location information. To reduce the risk of applications not implementing a standard correctly, the OGC provides a compliance process for testing and certifying implementations. OGC certification provides substantial evidence that an implementation that is claimed to have implemented an OGC standard will interoperate as specified and in the same manner as other compliant implementations, regardless of who developed them. This white paper provides guidance regarding language to specify requirements for OGC compliant and implementing products in software acquisition (procurement) documents." + "@value": "This document reports on outcomes from the OGC Web Services Shibboleth Interoperability Experiment (OSI). The main objective of OSI was to advance the use of Shibboleth (an open source implementation of SAML) as a means of protecting OWS. In the process, OSI helped develop further understanding of this approach to establishing trusted federations of OWS. This report documents these findings and is intended to be of use to those interested in how Shibboleth/SAML access management federations may function as an organisational model for operational Spatial Data Infrastructure." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70146,40 +70309,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-002r5" + "@value": "11-019r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Compliance Overview - Guide for Software Acquisition" - } - ], - "http://www.w3.org/ns/dcat#landingPage": [ - { - "@id": "http://docs.opengeospatial.org/wp/15-002r5/15-002r5.html" + "@value": "OGC® Engineering Report for the OWS Shibboleth Interoperability Experiment" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-112r4", + "@id": "http://www.opengis.net/def/docs/05-019", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2005-02-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Udo Quadt, Thomas Kolbe" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70189,27 +70347,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/15-112r4/15-112r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=8869" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Volume 3: OGC CDB Terms and Definitions (Normative)" + "@value": "Web 3D Service" }, { "@language": "en", - "@value": "15-112r4" + "@value": "05-019" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice." + "@value": "The Web 3D Service is a portrayal service for three-dimensional geodata, delivering graphical elements from a given geographical area. In contrast to the OGC Web Mapping service (WMS) and the OGC Web terrain service (WTS) 3D scene graphs are produced. These scene graphs will be rendered by the client and can interactively be explored by the user. The W3DS merges different types (layers) of 3D data in one scene graph. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70220,35 +70378,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-112r4" + "@value": "05-019" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 3: OGC CDB Terms and Definitions (Normative)" + "@value": "Web 3D Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-100", + "@id": "http://www.opengis.net/def/docs/18-023r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-04-13" + "@value": "2019-03-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele" + "@value": "Joan Masó" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70258,27 +70416,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8071" + "@id": "https://docs.ogc.org/per/18-023r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-2 Application Schema Development" + "@value": "18-023r1" }, { "@language": "en", - "@value": "04-100" + "@value": "MapML Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OWS-2 Application Schema Development Discussion Paper describes the process for creating ISO 19109:2005 Application Schemas [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=39891] in UML. It also describes the process used during the OWS-2 Initiative [http://www.opengeospatial.org/projects/initiatives/ows-2] for creating GML [http://www.opengeospatial.org/standards/gml] Application Schemas from ISO 19109:2005 Application Schemas.\r\n\r\nSee also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .\r\n" + "@value": "This is the second Engineering Report (ER) about the Map Markup Language (MapML) cite:[Rushforth2018] resulting from OGC Testbed initiatives. To find an introduction of MapML and how it works, please, refer to the previous ER OGC 17-019 cite:[Maso2018]. MapML is a new media type that can be included in a element of a section, in a Hypertext Markup Language (HTML) page. This document is mainly focused on the description of the MapML media type and its evolutions. In particular, it considers issues about the Coordinate Reference System (CRS) types in MapML, feature and properties encoding, Cascading Style Sheets (CSS) symbolization, multidimensional data etc.\r\n\r\nThis document describes two implementations done in OGC Testbed-14: a Cloud-based Proxy (cascade) for MapML done by CubeWerx and a ServiceWorker Proxy for MapML done by George Mason University (GMU).\r\n\r\nFinally, this document reviews how the next generation of OGC services can integrate MapML files as part of the designing of use cases and discusses how MapML can be used by social media.\r\n\r\nThis document proposals increases functionality in MapML and makes proposals for increasing the interoperability of the proposed encoding with the OGC standards baseline and future generations of OGC standards for maps and tiles." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70289,35 +70447,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-100" + "@value": "18-023r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-2 Application Schema Development" + "@value": "OGC Testbed-14: MapML Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-049", + "@id": "http://www.opengis.net/def/docs/21-029", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-26" + "@value": "2022-03-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann, Jinsongdi Yu" + "@value": "Sara Saeedi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70327,27 +70485,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=54502" + "@id": "https://docs.ogc.org/per/21-029.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coverage Service Interface Standard - Interpolation Extension" + "@value": "OGC Testbed 17: MASBUS Integration Engineering Report" }, { "@language": "en", - "@value": "12-049" + "@value": "21-029" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC standard specifies parameters to the OGC Web Coverage Service (WCS) GetCov-erage request which give control over interpolation of a coverage during its server-side pro-cessing. This allows the client (user) to control and specify the interpolation mechanism to be applied to a coverage during server processing.\r\nThis WCS Interpolation extension relies on WCS Core [OGC 09-110r4] and the GML Appli-cation Schema for Coverages [OGC 09-146r2].\r\n" + "@value": "This OGC Testbed 17 Engineering Report (ER) analyses the Measures and Signatures Intelligence Enterprise Service Bus (MASBUS) pilot software and the efforts to integrate with OGC SensorThings API resources. After introducing MASBUS, a server implementation is designed to digest sensor data and demonstrate the SensorThings MQTT (Message Queuing Telemetry Transport) extension of the MASBUS software. To show the SensorThings MQTT extension of the MASBUS software, a MASBUS client implementation is also presented. This ER discusses the results of the MASBUS integration, including all lessons learned from the experiments completed during the OGC Testbed 17 Sensor Integration thread and concludes with a set of optimum recommendations.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70358,35 +70516,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-049" + "@value": "21-029" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Coverage Service Interface Standard - Interpolation Extension" + "@value": "OGC Testbed 17: MASBUS Integration Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-146r8", + "@id": "http://www.opengis.net/def/docs/03-010r7", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-10-28" + "@value": "2003-05-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann, Eric Hirschorn, Joan Masó" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70396,27 +70554,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/09-146r8/09-146r8.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1345" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Coverage Implementation Schema with Corrigendum" + "@value": "03-010r7" }, { "@language": "en", - "@value": "09-146r8" + "@value": "Recommended XML Encoding of CRS Definitions" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Coverages represent homogeneous collections of values located in space/time, such as spatio-temporal sensor, image, simulation, and statistics data. Common examples include 1-D timeseries, 2-D imagery, 3-D x/y/t image timeseries and x/y/z geophysical voxel models, as well as 4-D x/y/z/t climate and ocean data. Generally, coverages encompass multi-dimen­sional regular and irregular grids, point clouds, and general meshes.\r\n\r\nThis Coverage Implementation Schema (CIS) specifies the OGC coverage model by establishing a concrete, interoperable, conformance-testable coverage structure. It is based on the abstract concepts of OGC Abstract Topic 6 [1] (which is identical to ISO 19123) which spec­i­fies an abstract model which is not per se interoperable – in other words, many different and incompatible implementations of the abstract model are possible. CIS, on the other hand, is interoperable in the sense that coverages can be conformance tested, regardless of their data format encoding, down to the level of single “pixels” or “voxels.”\r\n\r\nCoverages can be encoded in any suitable format (such as GML, JSON, GeoTIFF, or Net­CDF) and can be partitioned, e.g., for a time-interleaved representation. Coverages are independent from service definitions and, therefore, can be accessed through a variety of OGC services types, such as the Web Coverage Service (WCS) Standard [8]. The coverage structure can serve a wide range of coverage application domains, thereby contributing to harmon­ization and interoperability between and across these domains." + "@value": "This OpenGIS Recommendation Paper specifies basic XML encoding of data defining coordinate reference systems and coordinate operations. This encoding is expected to be adapted and used by multiple OGC\r\nImplementation Specifications, by the separate specification of Application Schemas. This document is a Recommendation Paper because the specified encoding is more general\r\nthan an OpenGIS Implementation Specification and more specific than the OpenGIS Abstract Specification." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70427,35 +70585,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-146r8" + "@value": "03-010r7" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Coverage Implementation Schema with Corrigendum" + "@value": "Recommended XML Encoding of CRS Definitions" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-128r17", + "@id": "http://www.opengis.net/def/docs/20-089r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-04" + "@value": "2021-12-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Pedro Gonçalves" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70465,27 +70623,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/12-128r17/12-128r17.html" + "@id": "https://docs.ogc.org/bp/20-089r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GeoPackage Encoding Standard" + "@value": "20-089r1" }, { "@language": "en", - "@value": "12-128r17" + "@value": "Best Practice for Earth Observation Application Package" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." + "@value": "Platforms for the exploitation of Earth Observation (EO) data have been developed by public and private companies in order to foster the usage of EO data and expand the market of Earth Observation-derived information. A fundamental principle of the platform operations concept is to move the EO data processing service’s user to the data and tools, as opposed to downloading, replicating, and exploiting data ‘at home’. In this scope, previous OGC activities initiated the development of an architecture to allow the ad-hoc deployment and execution of applications close to the physical location of the source data with the goal to minimize data transfer between data repositories and application processes.\r\n\r\nThis document defines the Best Practice to package and deploy Earth Observation Applications in an Exploitation Platform. The document is targeting the implementation, packaging and deployment of EO Applications in support of collaborative work processes between developers and platform owners.\r\n\r\nThe Best Practice includes recommendations for the application design patterns, package encoding, container and data interfaces for data stage-in and stage-out strategies focusing on three main viewpoints: Application, Package and Platform." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70496,35 +70654,58 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-128r17" + "@value": "20-089r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GeoPackage Encoding Standard" + "@value": "OGC Best Practice for Earth Observation Application Package" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-013", + "@id": "http://www.opengis.net/def/doc-type/pol", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/09-144r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-046r6" + }, + { + "@id": "http://www.opengis.net/def/docs/08-134r11" + }, + { + "@id": "http://www.opengis.net/def/docs/05-020r29" + }, + { + "@id": "http://www.opengis.net/def/docs/08-131r3" + }, + { + "@id": "http://www.opengis.net/def/docs/09-046r5" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/13-100", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-04-13" + "@value": "2013-11-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside, Markus U. M" + "@value": "Andreas Matheus " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70534,27 +70715,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=8847" + "@id": "https://portal.ogc.org/files/?artifact_id=55231" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Coordinate Transformation Service" + "@value": "13-100" }, { "@language": "en", - "@value": "05-013" + "@value": "Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the interface to a Web Coordinate Transformation Service (WCTS), which can be used by geospatial applications and other services. Transformation of geospatial data from one coordinate reference system (CRS) to another is frequently required when using data from different sources in one application. That is, geospatial data are often stored in different coordinate reference systems (CRSs). To use together data stored in different CRSs, such data must be transformed or converted into the same CRS. Not all applications or services are capable of directly performing such transformations. \r\n\r\nThis document specifies an OGC Web Service type of interface to a service that performs coordinate transformations. Such transformations include all the types of coordinate operations, including both transformations and conversions. This service inputs digital features or coverages in one CRS and outputs the same features in a different CRS. The service inputs include identifications of the input and output CRSs, and optionally the coordinate transformation between these CRSs.\r\n" + "@value": "This standard defines the version 3.0 of a geospatial extension to the OASIS eXtensible Access Control Markup Language (XACML) Version 3.0 standard. It thereby enables the interoperable definition of access rights / constraints using the XACML 3.0 language, processing model and policy schema but extends the ability to phrase conditions on geographic characteristics of subjects, resources and objects. \r\nIn that sense, a GeoXACML policy could restrict access to geospatial information, e.g. provided by OGC Web Services. However, a GeoXACML policy could also restrict access to non geospatial assets by stating restrictions for access based on the location of the user (or the mobile device used) trying to access the protected assets. Therefore, this standard applies to main stream IT.\r\nFor enabling processing of access control decisions based on geometry, Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core inherits by normative reference ISO 19125 which defines a geometry model and functions on geometry instances which enrich the XACML 3.0 specification. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70565,35 +70746,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-013" + "@value": "13-100" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Coordinate Transformation Service" + "@value": "OGC Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-087r3", + "@id": "http://www.opengis.net/def/docs/23-028", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-04-05" + "@value": "2024-04-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Michael Leedahl" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70603,27 +70784,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=14034" + "@id": "https://docs.ogc.org/per/23-028.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-087r3" + "@value": "OGC Testbed 19 Extraterrestrial GeoTIFF Engineering Report" }, { "@language": "en", - "@value": "Observations and Measurements" + "@value": "23-028" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The general models and XML encodings for observations and measurements, including but not restricted to those using sensors." + "@value": "With the growing number of space assets and missions, the space industry needs a way to locate extra-terrestrial objects within the captured imagery. The current GeoTIFF Standard provides the location of terrestrial objects using TIFF tags. However, objects in space are relative to the observer and the distance of the objects in the imagery are often at great distances from the observer. Multiple objects can exist within the imagery which are at different spacetime locations in four dimensions. To further complicate the definition of the location, from a planar perspective, the edges of the image fade into infinity. With the use of spherical and gridded coordinates an image can tag pixels along the edge of a sphere or the camera location. The Testbed 19 Engineering Report (ER) extends GeoTIFF to work for all images including both terrestrial and non-terrestrial observations within the image." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70634,35 +70815,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-087r3" + "@value": "23-028" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Observations and Measurements" + "@value": "OGC Testbed 19 Extraterrestrial GeoTIFF Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-066", + "@id": "http://www.opengis.net/def/docs/99-107", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-09-13" + "@value": "1999-03-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Charles Heazel" + "@value": "Cliff Kottman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/ug" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70672,27 +70853,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/guides/20-066.html" + "@id": "https://portal.ogc.org/files/?artifact_id=892" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "City Geography Markup Language (CityGML) 3.0 Conceptual Model Users Guide" + "@value": "Topic 07 - Earth Imagery" }, { "@language": "en", - "@value": "20-066" + "@value": "99-107" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/ug" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "CityGML is an open conceptual data model for the storage and exchange of virtual 3D city models. It is defined through a Unified Modeling Language (UML) object model. This UML model extends the ISO Technical Committee 211 (TC211) conceptual model standards for spatial and temporal data. Building on the ISO foundation assures that the man-made features described in the City Models share the same spatial-temporal universe as the surrounding countryside within which they reside. The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields.\r\n\r\nThis Users Guide provides extended explanations and examples for the individual concepts that are defined in the CityGML 3.0 Conceptual Model Standard. Both documents, the Conceptual Model Standard and the Users Guide, are mutually linked to facilitate navigation between corresponding sections in these documents." + "@value": "This Topic Volume will provide essential and abstract models for technology that is already used widely (but not interoperably) across the GIS landscape. This technology properly depends on the more general technology that supports Coverages." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70703,35 +70884,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-066" + "@value": "99-107" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC City Geography Markup Language (CityGML) 3.0 Conceptual Model Users Guide" + "@value": "Topic 7 - Earth Imagery" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-011", + "@id": "http://www.opengis.net/def/docs/06-111", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-05-04" + "@value": "2006-07-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sara Saeedi" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/pc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70741,27 +70922,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-011.html" + "@id": "https://portal.ogc.org/files/?artifact_id=16571" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-011" + "@value": "GML 3.1.1 grid CRSs Profile Corrigendum" }, { "@language": "en", - "@value": "SCIRA Pilot Engineering Report" + "@value": "06-111" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/pc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report (ER) captures Smart City Interoperability Reference Architecture (SCIRA) Pilot implementation outcomes and findings to demonstrate the risk mitigation and safety capability of the SCIRA interoperable and standard-based architecture. SCIRA Pilot is an OGC (Open Geospatial Consortium) Innovation Program project sponsored by the US Department of Homeland Security (DHS) Science & Technology (S&T) in collaboration with the city of St. Louis, Missouri. The purpose of this project is to advance standards for smart and safe cities and develop open, interoperable design patterns for incorporating the Internet of Things (IoT) sensors into city services." + "@value": "This document is a corrigendum for OGC Document 05-096r1, titled GML 3.1.1 grid CRSs profile. This corrigendum is based on change request OGC 06-041." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70772,35 +70953,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-011" + "@value": "06-111" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC SCIRA Pilot Engineering Report" + "@value": "GML 3.1.1 grid CRSs Profile Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-127r1", + "@id": "http://www.opengis.net/def/docs/03-109r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-08-18" + "@value": "2004-02-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Brackin" + "@value": "Jeff de La Beaujardiere" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70810,27 +70991,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40134" + "@id": "https://portal.ogc.org/files/?artifact_id=4756" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-127r1" + "@value": "Web Map Service (Recommendation Paper)" }, { "@language": "en", - "@value": "OWS-7 Engineering Report - Aviation Portrayal" + "@value": "03-109r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the requirements, design, technical implementation and technology trialed for the Feature Portrayal service chain used in OWS-7. This includes the interfaces to the OWS Data Services deployed, the feature portrayal servers, the interfaces to clients and the registry information model and interface." + "@value": "Provides three operations (GetCapabilities, GetMap, and GetFeatureInfo) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70841,35 +71022,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-127r1" + "@value": "03-109r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-7 Engineering Report - Aviation Portrayal" + "@value": "Web Map Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-006", + "@id": "http://www.opengis.net/def/docs/06-080r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-26" + "@value": "2007-08-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Jerome Gasperi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70879,27 +71060,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/note/20-006.html" + "@id": "https://portal.ogc.org/files/?artifact_id=22161" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-006" + "@value": "GML Application Schema for EO Products" }, { "@language": "en", - "@value": "OGC CDB Version 1.2 Release Notes" + "@value": "06-080r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the set of revision notes for the CDB Standard, version 1.2 [OGC ]> and does not modify that standard." + "@value": "This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGC" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70910,35 +71091,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-006" + "@value": "06-080r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC CDB Version 1.2 Release Notes" + "@value": "GML Application Schema for EO Products" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-049", + "@id": "http://www.opengis.net/def/docs/06-103r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-16" + "@value": "2011-05-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis, Stephane Fellah" + "@value": "John Herring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -70948,27 +71129,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=58974" + "@id": "https://portal.ogc.org/files/?artifact_id=25355" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 10 Cross Community Interoperability (CCI) Ontology Engineering Report" + "@value": "06-103r4" }, { "@language": "en", - "@value": "14-049" + "@value": "Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Testbed 10 ontology work focused on:\r\n•\tA general examination of ontologies in the context of OGC data modeling, handling, and organization. Testbed-10 has started to define a consistent set of ontologies implementing solid theoretical foundations and semantics. \r\n•\tThe definition of a core ontologies for representing incident information used by Incident Management Systems (IMS) and mapping symbologies used in the emergency and disaster management domain with the goal to improve interoperability between different IMS symbology sets used across multi-level jurisdiction. \r\n•\tAddressed ontology mapping between hydrology feature models using SPARQL and OWL2.\r\n" + "@value": "The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -70979,35 +71160,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-049" + "@value": "06-103r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 10 Cross Community Interoperability (CCI) Ontology Engineering Report" + "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-048", + "@id": "http://www.opengis.net/def/docs/10-092r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-08-31" + "@value": "2011-04-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Josh Lieberman, Andy Ryan" + "@value": "Ben Domenico" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -71017,27 +71198,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-048.html" + "@id": "https://portal.ogc.org/files/?artifact_id=43734" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Underground Infrastructure Concept Study Engineering Report" + "@value": "10-092r3" }, { "@language": "en", - "@value": "17-048" + "@value": "NetCDF Binary Encoding Extension Standard: NetCDF Classic and 64-bit Offset Format" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report documents the progress made to date by OGC and its members to build a complete picture of the present situation and develop a conceptual framework for action to improve underground infrastructure data interoperability. The report also identifies the most important steps to be taken next in order to develop the necessary data standards and foster their adoption." + "@value": "This document defines an OGC® Standard for encoding binary representations of space-time varying geo-referenced data. Specifically, this standard specifies the netCDF classic and 64-bit offset file binary encoding formats. This standard specifies a set of requirements that every netCDF classic or 64-bit offset binary encoding must fulfil." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71048,35 +71229,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-048" + "@value": "10-092r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Underground Infrastructure Concept Study Engineering Report" + "@value": "NetCDF Binary Encoding Extension Standard: NetCDF Classic and 64-bit Offset Format" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-006r3", + "@id": "http://www.opengis.net/def/docs/16-032r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-01-16" + "@value": "2017-03-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Marwa Mabrouk" + "@value": "Boyan Brodaric" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -71086,27 +71267,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=3418" + "@id": "https://docs.ogc.org/is/16-032r2/16-032r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-006r3" + "@value": "WaterML 2: Part 4 – GroundWaterML 2 (GWML2)" }, { "@language": "en", - "@value": "Location Services (OpenLS): Core Services [Parts 1-5]" + "@value": "16-032r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform. " + "@value": "This standard describes a conceptual and logical model for the exchange of groundwater data, as well as a GML/XML encoding with examples." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71117,43 +71298,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-006r3" + "@value": "16-032r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Location Services (OpenLS): Core Services [Parts 1-5]" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-orm", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/03-040" + "@value": "OGC WaterML 2: Part 4 – GroundWaterML 2 (GWML2)" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-003", + "@id": "http://www.opengis.net/def/docs/13-057r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-07-22" + "@value": "2016-11-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Graham" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -71163,27 +71336,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=61935" + "@id": "https://docs.ogc.org/is/13-057r1/13-057r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-003" + "@value": "13-057r1" }, { "@language": "en", - "@value": "Common DataBase Volume 1 Main Body" + "@value": "Web Coverage Service Interface Standard – Transaction Extension" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Common DataBase (CDB) Specification provides the means for a single, versionable, simulation-rich, synthetic representation of the earth. A database that conforms to this Specification is referred to as a Common DataBase or CDB. A CDB provides for a synthetic environment repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB can be used as a common on-line (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks; in this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time.\r\nThe application of CDB to future simulator architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the HLA/FOM and DIS protocols, the application of the CDB Specification provides a Common Environment to which inter-connected simulators share a common view of the simulated environment.\r\nThe CDB Specification is an open format Specification for the storage, access and modification of a synthetic environment database. The Specification defines the data representation, organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The Specification makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry.\r\nThe CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. It encompasses the terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the synthetic environment includes the specific attributes of the synthetic environment data as well as their relationships.\r\nA CDB contains datasets organized in layers, tiles and levels-of-detail; together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB is specifically tailored for real-time applications. \r\n" + "@value": "This OGC Web Coverage Service (WCS) – Transaction Extension (in short: WCS Transaction) defines an extension to the WCS Core [OGC 09-110] for updating coverage offer­ings on a server.\r\n\r\nThis WCS Transaction standard defines three requests:\r\n\r\nInsertCoverage for adding a coverage provided as parameter to the WCS server’s cov­erage offering. After successful completion of the insert request, this coverage will be accessible for all WCS operations.\r\nDeleteCoverage for entirely removing a coverage. The coverage is identified by its coverage id passed in the request, from the WCS server’s coverage offering. After successful completion of this request, this coverage will not be accessible through any WCS operation. However, subsequently a new coverage may be created using the same identifier; such a coverage will bear no relation to the one previously deleted.\r\nUpdateCoverage for modifying parts of a coverage existing in a WCS server’s coverage offering. The coverage is identified by its coverage id passed in the request. As per the OGC Coverage Implementation Schema [OGC 09-146r2], all updates must maintain internal consistency of the coverage.\r\nAll requests defined in this Transaction Extension adhere to the ACID[1] (atomicity, consistency, isolation, durability) concepts of database transactions.\r\n\r\nThe extension name, Transaction, traces back to the database concept of transactions, which has been adopted here." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71194,30 +71367,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-003" + "@value": "13-057r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Common DataBase Volume 1 Main Body" + "@value": "OGC Web Coverage Service Interface Standard – Transaction Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-144", + "@id": "http://www.opengis.net/def/docs/14-049", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2014-07-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Burggraf" + "@value": "Ingo Simonis, Stephane Fellah" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -71232,17 +71405,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=53255" + "@id": "https://portal.ogc.org/files/?artifact_id=58974" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-144" + "@value": "Testbed 10 Cross Community Interoperability (CCI) Ontology Engineering Report" }, { "@language": "en", - "@value": "OWS-9 Architecture - Registry Engineering Report" + "@value": "14-049" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -71252,7 +71425,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Engineering Report provides guidelines for the harvest, registration and retrieval of aviation resources from an OGC web catalogue/registry service (OGC CSW-ebRIM), with particular emphasis on ISO metadata resources. Alternatives for selective and efficient retrieval of such resources are also described along with lessons learned. The OGC CSW-ebRIM registry interface is evaluated against SESAR registry requirements, documented as a gap analysis, to assess whether there are any obstacles to implementing SESAR registry with an OGC CSW-ebRIM interface." + "@value": "Testbed 10 ontology work focused on:\r\n•\tA general examination of ontologies in the context of OGC data modeling, handling, and organization. Testbed-10 has started to define a consistent set of ontologies implementing solid theoretical foundations and semantics. \r\n•\tThe definition of a core ontologies for representing incident information used by Incident Management Systems (IMS) and mapping symbologies used in the emergency and disaster management domain with the goal to improve interoperability between different IMS symbology sets used across multi-level jurisdiction. \r\n•\tAddressed ontology mapping between hydrology feature models using SPARQL and OWL2.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71263,35 +71436,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-144" + "@value": "14-049" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-9 Architecture - Registry Engineering Report" + "@value": "OGC® Testbed 10 Cross Community Interoperability (CCI) Ontology Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-076", + "@id": "http://www.opengis.net/def/docs/09-026r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-03-30" + "@value": "2010-11-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ajay Gupta, Luis Bermudez, Eddie Oldfield, Scott Serich" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -71301,27 +71474,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/wp/19-076.html" + "@id": "https://portal.ogc.org/files/?artifact_id=39968" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-076" + "@value": "Filter Encoding 2.0 Encoding Standard" }, { "@language": "en", - "@value": "Health Spatial Data Infrastructure: Application Areas, Recommendations, and Architecture" + "@value": "09-026r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Health Spatial Data Infrastructure white paper provides a discussion about the collection, exchange, integration, analysis, and visualization of health and non-health data to support health applications. Applications that address health issues at global and population level scale as well as at the local, individual patient scale are presented. The paper identifies opportunities to advance OGC Standards towards building a framework to support Health Spatial Data Infrastructures (SDIs)." + "@value": "This International Standard describes an XML and KVP encoding of a system neutral syntax for expressing projections, selection and sorting clauses collectively called a query expression.\r\nThese components are modular and intended to be used together or individually by other standards which reference this International Standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71332,59 +71505,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-076" + "@value": "09-026r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Health Spatial Data Infrastructure: Application Areas, Recommendations, and Architecture" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-rfc", - "http://www.w3.org/2004/02/skos/core#narrower": [ - { - "@id": "http://www.opengis.net/def/docs/05-033r9" - }, - { - "@id": "http://www.opengis.net/def/docs/05-007r4" - }, - { - "@id": "http://www.opengis.net/def/docs/11-122r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-007r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-036" - }, - { - "@id": "http://www.opengis.net/def/docs/05-047r2" - }, - { - "@id": "http://www.opengis.net/def/docs/03-006r3" - }, - { - "@id": "http://www.opengis.net/def/docs/03-006r1" + "@value": "OpenGIS Filter Encoding 2.0 Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-114", + "@id": "http://www.opengis.net/def/docs/15-025r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-11-16" + "@value": "2015-08-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Danko, Lance Shipman, Paul Ramsey" + "@value": "Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -71399,17 +71543,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=45754" + "@id": "https://portal.ogc.org/files/?artifact_id=63793" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-114" + "@value": "Testbed 11 Aviation - Architecture Engineering Report" }, { "@language": "en", - "@value": "OWS-8 Bulk Geodata Transfer with File Geodatabase" + "@value": "15-025r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -71419,7 +71563,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides an overview of the File Geodatabase API and documents the testing performed in the OWS 8 Testbed." + "@value": "This OGC® document describes the architecture implemented in the OGC Testbed 11 Aviation thread." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71430,35 +71574,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-114" + "@value": "15-025r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 Bulk Geodata Transfer with File Geodatabase" + "@value": "OGC® Testbed 11 Aviation - Architecture Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-069", + "@id": "http://www.opengis.net/def/docs/07-152", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-01-08" + "@value": "2008-01-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Maso Pau" + "@value": "Corentin Guillo" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -71468,27 +71612,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-069.html" + "@id": "https://portal.ogc.org/files/?artifact_id=25184" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Maps and Tiles API Engineering Report" + "@value": "07-152" }, { "@language": "en", - "@value": "19-069" + "@value": "FedEO Pilot Engineering Report (07-152)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "In 2017 the OGC began a focused effort to develop Application Programming Interface (API) standards that support the Resource Oriented Architecture and make use of the OpenAPI specification. As part of this effort, this OGC Testbed 15 Engineering Report (ER) defines a proof-of-concept of an API specification for maps and tiles.\r\n\r\nThe OGC API Maps and Tiles draft specification described in this ER builds on the precedent of the OGC API - Features - Part 1: Core standard. The OGC API - Tiles draft specification describes a service that retrieves data representations as tiles, which are generally small compared with the geographic extent of the data. In the draft specification, the assumption is that tiles are organized into Tile Matrix Sets consisting of regular tile matrices available at different scales or resolutions. The OGC API – Tiles draft specification is described as a building block that can be plugged into an OGC API - Features service to retrieve tiled feature data (sometimes called vector tiles) or to an OGC API – Maps implementation to retrieve rendered tiles (sometimes called map tiles). In the future, the OGC API - Tiles draft specification could extend other specifications, one possible candidate being the emerging OGC API – Coverages draft specification.\r\n\r\nThe OGC API - Maps draft specification describes an API that presents data as maps by applying a style. These maps can be retrieved in a tiled structure (if OGC API - Tiles is approved as an OGC Implementation Standard) or as maps of any size generated on-the-fly. The OGC API - Maps draft specification implements some functionality, specified in the Web Map Tile Service (WMTS) 1.0 standard, related to the use of styles by using the Styles API draft specification that was developed in the Testbed-15 Open Portrayal Framework thread.\r\n\r\nThe draft Maps and Tiles API specifications are designed in a modular way. With the exception of the core requirements, the other conformance classes describe functionality that can be considered optional characteristics that can be combined by server implementations at will.\r\n\r\nAt the beginning of Testbed-15, the original proposed title for this ER was OGC Testbed-15: Web Map Tiling Service Draft Specification Engineering Report but in the course of the Testbed-15 that title was changed to better represent the content." + "@value": "This document was developed during the FedEO - GEO AIP initiative of the OGC. It was contributed by the organizations involved in the Earth Observation and Natural Resources and Environment Domain Working Group (EO/NRE DWG) in the OGC Specification Program. The document describes recommendation for architecture and specification that enables interoperability" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71498,36 +71642,88 @@ ], "http://www.w3.org/2004/02/skos/core#notation": [ { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-069" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "07-152" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@language": "en", + "@value": "FedEO Pilot Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-rfc/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Request for Comment - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Request for Comment - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/03-007r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-007r4" + }, + { + "@id": "http://www.opengis.net/def/docs/03-006r3" + }, + { + "@id": "http://www.opengis.net/def/docs/03-006r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-122r1" + }, + { + "@id": "http://www.opengis.net/def/docs/03-036" + }, + { + "@id": "http://www.opengis.net/def/docs/05-033r9" + }, + { + "@id": "http://www.opengis.net/def/docs/05-047r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@language": "en", - "@value": "OGC Testbed-15: Maps and Tiles API Engineering Report" + "@value": "Documents of type Request for Comment - deprecated " } ] }, { - "@id": "http://www.opengis.net/def/docs/17-002r1", + "@id": "http://www.opengis.net/def/docs/10-196r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-08-18" + "@value": "2011-03-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "OGC Aviation Domain Working Group" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -71537,27 +71733,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/17-002r1/17-002r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=41668" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GeoRSS Encoding Standard" + "@value": "Guidance on the Aviation Metadata Profile" }, { "@language": "en", - "@value": "17-002r1" + "@value": "10-196r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "GeoRSS is designed as a lightweight, community driven way to extend existing RSS feeds with simple geographic information. The GeoRSS standard provides for encoding location in an interoperable manner so that applications can request, aggregate, share and map geographically tag feeds." + "@value": "This paper explains how to map the Requirements for Aviation Metadata into a metadata profile." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71568,35 +71764,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-002r1" + "@value": "10-196r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoRSS Encoding Standard" + "@value": "Guidance on the Aviation Metadata Profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-064r1", + "@id": "http://www.opengis.net/def/docs/20-071", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-06-12" + "@value": "2023-03-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Phillip C. Dibner" + "@value": "Charles Heazel" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/ug" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -71606,27 +71802,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1267" + "@id": "https://docs.ogc.org/guides/20-071.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GO-1 Application Objects Report" + "@value": "OGC API - Common - Users Guide" }, { "@language": "en", - "@value": "03-064r1" + "@value": "20-071" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/ug" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a draft of the OpenGIS" + "@value": "The OGC API — Common Standard is a multi-part Standard that specifies reusable building-blocks that can be used in the construction of OGC API Standards. The OGC API — Common — Users Guide presents information useful to developers or users of implementations of the OGC API — Common Standard. The information in the Users Guide is not normative. That is, it is not mandatory. However, it may prove essential to fully understand the normative text in the OGC API — Common Standard. The Users Guide is therefore intended to serve as an aid to developers and users." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71637,35 +71833,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-064r1" + "@value": "20-071" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GO-1 Application Objects Report" + "@value": "OGC API - Common - Users Guide" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-037", + "@id": "http://www.opengis.net/def/docs/10-126r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-12" + "@value": "2014-02-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Robert Cass" + "@value": "Peter Taylor" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -71675,27 +71871,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-037.html" + "@id": "https://portal.ogc.org/files/?artifact_id=57222" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-037" + "@value": "WaterML 2.0: Part 1- Timeseries" }, { "@language": "en", - "@value": "Testbed-12 GeoPackage US Topo Engineering Report" + "@value": "10-126r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report documents the outcome of the US Topo experiment. The focus of the US Topo experiment was to generate GeoPackages by combining USGS Topo Map Vector Data Products [1]; and the Topo TNM Style Template [2]. The output GeoPackages will contain both features and instructions for styling these features as well as orthoimagery, shaded relief raster tilesets, national wetlands raster tilesets and elevation data derived from USGS provide 1/9 arc second elevation imagery. The process used to generate the GeoPackage is explained. Problems and obstacles encountered decoding the source product and styles and converting these artifacts to a GeoPackage are explained with recommendations for improvements. Additionally, the experience applying the generated GeoPackage in two use cases proposed for this testbed will be evaluated. The introduction of symbolization for vector features will be articulated as a proposed extension for GeoPackage. Any issues related to encoding the TNM style template using the extension are documented." + "@value": "WaterML 2.0 is a standard information model for the representation of water observations data, with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of exchange requirements, some of which are described later in this document." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71706,69 +71902,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-037" + "@value": "10-126r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 GeoPackage US Topo Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-isc/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type Implementation Specification Corrigendum - deprecated " - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Documents of type Implementation Specification Corrigendum - deprecated " - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/12-128r11" - }, - { - "@id": "http://www.opengis.net/def/docs/06-189" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Documents of type Implementation Specification Corrigendum - deprecated " + "@value": "OGC® WaterML 2.0: Part 1- Timeseries" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-050r1", + "@id": "http://www.opengis.net/def/docs/01-042", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-09-21" + "@value": "2001-10-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Tom Strickland" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -71778,27 +71940,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/22-050r1/22-050r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1046" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-050r1" + "@value": "01-042" }, { "@language": "en", - "@value": "OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 JSON Profile v1.0" + "@value": "Topic Domain 1 - Telecommunications Domain" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 JSON Profile v1.0 (GeoXACML 3.0 JSON Profile) Standard defines an extension to the JSON Profile of XACML 3.0 Version 1.1 for supporting GeoXACML Authorization Decision Requests and Authorization Decision encoded in JSON. This ensures an easy uptake in environments where JSON is the preferred encoding.\r\n\r\nFor supporting Geometry as defined by the GeoXACML 3.0 Core conformance class, this profile extends the Attribute DataType definition from JSON Profile of XACML 3.0 Version 1.1 with the geometry data-type urn:ogc:def:geoxacml:3.0:data-type:geometry\r\n\r\nThe GeoXACML 3.0 JSON Profile Standard supports the Attribute value to use Well-Known-Text (WKT), Well-Known-Binary (WKB) hex-encoding or GeoJSON as an encoding alternative for the geometry data-type defined in GeoXACML 3.0.\r\n\r\nTo support the use of the GeoXACML 3.0 specific attributes SRID, Precision, Encoding, and AllowTransformation, this profile extends the default JSON schema definition from JSON Profile of XACML 3.0 Version 1.1 accordingly." + "@value": "Domain Model for telecommunications Networks" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71809,35 +71971,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-050r1" + "@value": "01-042" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 JSON Profile v1.0" + "@value": "Topic Domain 1 - Telecommunications Domain" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-053r1", + "@id": "http://www.opengis.net/def/docs/04-013r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-08-19" + "@value": "2004-09-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -71847,27 +72009,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64595" + "@id": "https://portal.ogc.org/files/?artifact_id=6944" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 11 Implementing JSON/GeoJSON in an OGC Standard Engineering Report" + "@value": "A URN namespace for the Open Geospatial Consortium (OGC)" }, { "@language": "en", - "@value": "15-053r1" + "@value": "04-013r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "In the OGC Testbed 11, the Cross-Community Interoperability (CCI) thread had a key objective of building on the work accomplished in the OGC 8, 9 and 10 Testbeds. The goal of the CCI threads is to increase interoperability between communities sharing geospatial data. This thread made advances in semantic mediation approaches for data discovery, access and use of heterogeneous data models and heterogeneous metadata models. This particular Engineering Report (ER) is part of the OGC efforts to advance the OGC Architecture with the adoption of REST interfaces and more encodings such as JSON." + "@value": "This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC (such as OGC Standards, XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other documents). The formal Namespace identifier (NID) is ogc.\r\n " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71878,35 +72040,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-053r1" + "@value": "04-013r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 11 Implementing JSON/GeoJSON in an OGC Standard Engineering Report" + "@value": "A URN namespace for the Open Geospatial Consortium (OGC)" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-004", + "@id": "http://www.opengis.net/def/docs/21-027", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-07-22" + "@value": "2022-04-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Graham" + "@value": "Jérôme Jacovella-St-Louis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -71916,27 +72078,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=61936" + "@id": "https://docs.ogc.org/per/21-027.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Common DataBase Volume 2 Appendices" + "@value": "21-027" }, { "@language": "en", - "@value": "15-004" + "@value": "OGC Testbed-17: Geo Data Cube API Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Common DataBase (CDB) Specification provides the means for a single, versionable, simulation-rich, synthetic representation of the earth. A database that conforms to this Specification is referred to as a Common DataBase or CDB. A CDB provides for a synthetic environment repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB can be used as a common on-line (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks; in this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time.\r\nThe application of CDB to future simulator architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the HLA/FOM and DIS protocols, the application of the CDB Specification provides a Common Environment to which inter-connected simulators share a common view of the simulated environment.\r\nThe CDB Specification is an open format Specification for the storage, access and modification of a synthetic environment database. The Specification defines the data representation, organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The Specification makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry.\r\nThe CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. It encompasses the terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the synthetic environment includes the specific attributes of the synthetic environment data as well as their relationships.\r\nA CDB contains datasets organized in layers, tiles and levels-of-detail; together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB is specifically tailored for real-time applications. \r\n" + "@value": "This OGC Testbed 17 Engineering Report (ER) documents the results and recommendations of the Geo Data Cube API task. The ER defines a draft specification for an interoperable Geo Data Cube (GDC) API leveraging OGC API building blocks, details implementation of the draft API, and explores various aspects including data retrieval and discovery, cloud computing and Machine Learning. Implementations of the draft GDC API are demonstrated with use cases including the integration of terrestrial and marine elevation data and forestry information for Canadian wetlands.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -71947,35 +72109,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-004" + "@value": "21-027" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Common DataBase Volume 2 Appendices" + "@value": "OGC Testbed-17: Geo Data Cube API Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-031r2", + "@id": "http://www.opengis.net/def/docs/11-106r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-07-12" + "@value": "2011-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Doug Palmer" + "@value": "Rob Atkinson, James Groffen" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -71985,27 +72147,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=49025" + "@id": "https://portal.ogc.org/files/?artifact_id=46227" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "WaterML 2.0 - Timeseries - NetCDF Discussion Paper" + "@value": "11-106r1" }, { "@language": "en", - "@value": "12-031r2" + "@value": "OWS-8 Digital NOTAM Refactor" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This discussion paper investigates the possible uses of NetCDF as a representation of WaterML timeseries data. The work is largely based on the WaterML 2.0 standard for timeseries, the NetCDF core and extensions standards and the CF-NetCDF and ADCC conventions." + "@value": "AIXM is a GML Application Schema described in UML using the relevant ISO / OGC standards from the 19100 series. The Digital NOTAM Events Specification (DNES) is an extension of AIXM that can describe notices to airmen using the AIXM standard. \r\nThis document has been produced in conjunction with the Domain Modelling Cookbook - a practical guide to domain modelling following a series of best practices developed by the CSIRO and other OGC members.\r\nWhere possible, documentation of the refactor effort for Digital NOTAM to be compatible with these practices is incorporated into the domain modelling cookbook. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72016,30 +72178,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-031r2" + "@value": "11-106r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "WaterML 2.0 - Timeseries - NetCDF Discussion Paper" + "@value": "OWS-8 Digital NOTAM Refactor" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-004", + "@id": "http://www.opengis.net/def/docs/06-022r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-07" + "@value": "2006-04-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "James Resler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -72054,17 +72216,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20431" + "@id": "https://portal.ogc.org/files/?artifact_id=14898" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-004" + "@value": "Temporal Standard Recommendations" }, { "@language": "en", - "@value": "GeoDDS Mass Market" + "@value": "06-022r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -72074,7 +72236,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OpenGIS(r) document describes the API for two web services capable of generating several simplified data formats including GeoRSS and the Basic XML Feature Schema\r\n(BXFS). \r\n" + "@value": "This document summarizes recommendations for extending geospatial standards with regard to time-varying information. These proposals are the result of the National Technology Alliance program called Temporal Evaluation and Assessment (TEA). " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72085,35 +72247,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-004" + "@value": "06-022r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GeoDDS Mass Market (formerly GeoRSS) Interoperability Program Report" + "@value": "Temporal Standard Recommendations" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-005r2", + "@id": "http://www.opengis.net/def/docs/17-025r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-02-23" + "@value": "2018-03-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Aleksandar Balaban" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -72123,27 +72285,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=72713" + "@id": "https://docs.ogc.org/per/17-025r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes" + "@value": "17-025r2" }, { "@language": "en", - "@value": "16-005r2" + "@value": "Testbed-13: Quality Assessment Service Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the Annexes for the CDB Core: Model and Physical Structure standard. The only exception is Annex A, Abstract Test Suite. The CDB ATS Annex is in Volume 1: Core document." + "@value": "This Engineering Report (ER) has been produced in conjunction with two other engineering reports from the OGC Testbed 13, the Abstract Data Quality ER [4] and the Data Quality Specification ER [5] to capture status quo, discussions, and results in the context of requirements for data quality assessment for Quality of Service in the Aviation Domain. It will, in particular, provide a Data Quality Assessment Service Specification. Much of the ER is presented in the future tense, using terms such as 'shall', in order to express requirements and constraints on future Data Quality Assessment Service implementations. The service specification includes design patterns, extension mechanisms, and service interface considerations.\r\n\r\nIn recent years, the concept of data quality has generated a notable interest among System Wide Information Management (SWIM) [17] implementers, both organization-specific and global. In the context of SWIM — and Service Oriented Architecture (SOA) implementations in general — data quality pertains to two major use cases, service advertising and service validation:\r\n\r\nService advertising\r\na service makes known to a potential consumer the quality of the data provided by the service. Based on this information, the consumer can determine whether or not the service meets its needs.\r\n\r\nService validation\r\nassurance is given that the quality of the data provided by a service is consistent with the quality that is explicitly defined in a service contract or any kind of agreement that may exist between a service provider and service consumer.\r\n\r\nBoth use cases share two common preconditions:\r\n\r\nAn unambiguous definition of the concept of data quality exists.\r\n\r\nA set of measurable parameters that allow specifying data quality is defined.\r\n\r\nThese are tasks that were performed as part of Testbed 13. The findings of the tasks are documented in the Abstract Data Quality ER (FA001)[4] and the Data Quality Specification ER (FA002)[5]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72154,35 +72316,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-005r2" + "@value": "17-025r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes" + "@value": "OGC Testbed-13: Quality Assessment Service Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-020r1", + "@id": "http://www.opengis.net/def/docs/05-094r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-01-21" + "@value": "2006-07-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Aleksandar Balaban, Andreas Matheus" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -72192,27 +72354,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-020r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=13203" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: Data Centric Security ER" + "@value": "05-094r1" }, { "@language": "en", - "@value": "21-020r1" + "@value": "GML 3.1.1 CRS support profile" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/profile" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed-17 Engineering Report (ER) documents the enhancement of applying Data Centric Security (DCS) to OGC API Features, OGC API Maps (draft), and OGC API Tiles (draft).\r\n\r\nAs organizations move to the cloud, it is important to incorporate DCS into the design of the new cloud infrastructure, enabling the use of cloud computing, even for sensitive geospatial data sets. The ER documents the applicability of Zero Trust through a Data Centric security approach (DCS) when applied to vector and binary geospatial data sets (Maps, Tiles, GeoPackage containers) and OGC APIs.\r\n\r\nThe defined architecture extends the typical Zero Trust Domain component by introducing a Key Management System (KMS) to support key registration and the management of access conditions for key retrieval. The prototype implementations (DCS Client, DCS Server and KMS) demonstrate how to request encrypted geospatial data as JSON for encrypted vector data, HTTP Multipart for encrypted map data or GeoPackage with encrypted content; how to obtain decryption key(s) and how to decrypt and display the protected data in a mobile application on Android." + "@value": "This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for supporting other profiles for encoding definitions of Coordinate Reference Systems (CRSs) and Coordinate Operations. This profile can be used without a GML Application Schema, and such use is assumed in this document." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72223,81 +72385,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-020r1" + "@value": "05-094r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: Data Centric Security ER" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/pol-nts/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type Name Type Specification" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Documents of type Name Type Specification" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/09-048r5" - }, - { - "@id": "http://www.opengis.net/def/docs/09-047r3" - }, - { - "@id": "http://www.opengis.net/def/docs/18-042r4" - }, - { - "@id": "http://www.opengis.net/def/docs/10-103r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-081" - }, - { - "@id": "http://www.opengis.net/def/docs/20-059r4" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Documents of type Name Type Specification" + "@value": "GML 3.1.1 CRS support profile" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-071", + "@id": "http://www.opengis.net/def/docs/10-090r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-10-04" + "@value": "2011-04-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Ben Domenico" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -72307,27 +72423,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7257" + "@id": "https://portal.ogc.org/files/?artifact_id=43732" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-071" + "@value": "10-090r3" }, { "@language": "en", - "@value": "Some image geometry models" + "@value": "Network Common Data Form (NetCDF) Core Encoding Standard version 1.0" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This discussion paper contains the material that is still relevant from Section 6 (or Appendix A) of the previous version 4 (document OGC 99-107) of OGC Abstract Specification Topic 7, titled The Earth Imagery Case. That version of Topic 7 has now been superseded by a new version with the same title.\r\nIn addition, some terminology has been revised to be consistent with the terminology now used in Topic 16: Image Coordinate Transformation Services. Specifically, the previous term real-time image geometry model has been changed to approximate image geometry model. Also, the previous name Universal Real-Time Image Geometry Model has been changed to Universal Image Geometry Model.\r\n" + "@value": "This document specifies the network Common Data Form (netCDF) core standard and extension mechanisms. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space and time-varying phenomena.\r\nNetCDF is a data model for array-oriented scientific data. A freely distributed collection of access libraries implementing support for that data model, and a machine-independent format are available. Together, the interfaces, libraries, and format support the crea-tion, access, and sharing of multi-dimensional scientific data.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72338,35 +72454,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-071" + "@value": "10-090r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Some image geometry models" + "@value": "OGC Network Common Data Form (NetCDF) Core Encoding Standard version 1.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-059", + "@id": "http://www.opengis.net/def/docs/05-107", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-16" + "@value": "2006-01-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stephane Fellah" + "@value": "Thomas Uslander (Ed.)" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -72376,27 +72492,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-059.html" + "@id": "https://portal.ogc.org/files/?artifact_id=12574" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Semantic Portrayal, Registry and Mediation Engineering Report" + "@value": "Reference Model for the ORCHESTRA Architecture" }, { "@language": "en", - "@value": "16-059" + "@value": "05-107" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report documents the findings of the activities related to the Semantic Portrayal, Registry and Mediation components implemented during the OGC Testbed 12. This effort is a continuation of efforts initiated in the OGC Testbed 11. This report provides an analysis of the different standards considered during this effort, documents the rendering endpoints extension added to the Semantic Portrayal Service and the migration of the Portrayal metadata to the Semantic Registry, which is aligned with the DCAT REST Service API. We also discuss the integration of the CSW ebRIM for Application Schema with the Semantic Mediation Service, and document the improvements of the SPARQL Extensions, Portrayal and Semantic Mediation ontologies defined in the previous testbed.\r\n\r\n" + "@value": "This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It contains a specification framework for the design of ORCHESTRA-compliant service networks and provides a platform-neutral specification of its information and service viewpoints." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72407,29 +72523,29 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-059" + "@value": "05-107" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Semantic Portrayal, Registry and Mediation Engineering Report" + "@value": "Reference Model for the ORCHESTRA Architecture" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/ts/collection", + "@id": "http://www.opengis.net/def/doc-type/dp-draft/collection", "@type": [ "http://www.w3.org/2004/02/skos/core#Collection" ], "http://www.w3.org/2000/01/rdf-schema#label": [ { - "@value": "Documents of type test suite" + "@value": "Documents of type Discussion Paper - draft" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Documents of type test suite" + "@value": "Documents of type Discussion Paper - draft" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72439,46 +72555,34 @@ ], "http://www.w3.org/2004/02/skos/core#member": [ { - "@id": "http://www.opengis.net/def/docs/08-069r2" - }, - { - "@id": "http://www.opengis.net/def/docs/08-103r2" - }, - { - "@id": "http://www.opengis.net/def/docs/14-014r3" - }, - { - "@id": "http://www.opengis.net/def/docs/07-134r2" - }, - { - "@id": "http://www.opengis.net/def/docs/08-053r2" + "@id": "http://www.opengis.net/def/docs/06-021r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type test suite" + "@value": "Documents of type Discussion Paper - draft" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-024", + "@id": "http://www.opengis.net/def/docs/09-166r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-06-30" + "@value": "2010-02-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Evans" + "@value": "Benjamin Hagedorn" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -72488,27 +72592,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1131" + "@id": "https://portal.ogc.org/files/?artifact_id=37257" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "02-024" + "@value": "09-166r2" }, { "@language": "en", - "@value": "Web Coverage Service" + "@value": "Web View Service Discussion Paper" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Extends the Web Map Server (WMS) interface to allow access to geospatial coverages that represent values or properties of geographic locations, rather than WMS generated maps (pictures)." + "@value": "The Web View Service (WVS) is an extendable, interactive, image-based portrayal service for complex three-dimensional geodata such as 3D landscape and city models. 3D geodata is delivered as finally rendered images. Besides color images, relevant thematic and geometrical information such as object identity information or depth data is provided. Additionally, the WVS supports interaction with the portrayed 3D environment, e.g., information retrieval, spatial analysis, and 3D navigation. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72519,35 +72623,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-024" + "@value": "09-166r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Coverage Service" + "@value": "Web View Service Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-167r2", + "@id": "http://www.opengis.net/def/docs/19-086r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-10-10" + "@value": "2023-07-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Frédéric Houbie, Philippe Duchesne, Patrick Maué" + "@value": "Mark Burgoyne, David Blodgett, Charles Heazel, Chris Little" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -72557,27 +72661,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47857" + "@id": "https://docs.ogc.org/is/19-086r6/19-086r6.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Semantic annotations in OGC standards" + "@value": "19-086r6" }, { "@language": "en", - "@value": "08-167r2" + "@value": "OGC API - Environmental Data Retrieval Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "In this OGC Best Practice, the concept of semantic annotations is introduced. Annotation of Web Services or data compliant to OGC standards refers to the task of attaching meaningful descriptions to the service and the served geospatial data or processes." + "@value": "The OGC API — Environmental Data Retrieval (EDR) standard provides a family of lightweight query interfaces to access spatiotemporal data resources by requesting data at a Position, within an Area, along a Trajectory or through a Corridor. A spatio-temporal data resource is a collection of spatio-temporal data that can be sampled using the EDR query pattern geometries. These patterns are described in the section describing the Core Requirements Class.\r\n\r\nThe goals of the EDR Application Programming Interface (API) that is specified by this standard are to:\r\n\r\nMake it easier to access a wide range of data through a uniform, well-defined simple Web interface;\r\n\r\nTo achieve data reduction to just the data needed by the user or client while hiding much of the data storage complexity.\r\n\r\nA major use case for the EDR API is to retrieve small subsets from large collections of environmental data, such as weather forecasts, though many other types of data can be accessed. The important aspect is that the requested data can be unambiguously specified by spatio-temporal coordinates.\r\n\r\nThe EDR API query patterns — Position, Area, Cube, Trajectory or Corridor — can be thought of as discrete sampling geometries, conceptually consistent with the feature of interest in the Sensor Observation Service (SOS) standard. A typical data resource accessed by an EDR API instance is a multidimensional dataset that could be accessed via an implementation of the Web Coverage Service (WCS) standard. In contrast to SOS and WCS, the EDR API is fully consistent with the patterns of the OGC API family of standards and aims to provide a single set of simple-to-use query patterns. Use cases for EDR range from real or virtual time-series observation retrievals, to sub-setting 4-dimensional data cubes along user-supplied sampling geometries. These query patterns do not attempt to satisfy the full scope of either SOS or WCS, but instead provide useful building blocks to enable the composition of APIs that satisfy a wide range of geospatial data use cases. By defining a small set of query patterns (and no requirement to implement all of them), the EDR API should help to simplify the design of systems (as they can be performance tuned for the supported queries) making it easier to build robust and scalable infrastructures.\r\n\r\nWith the OGC API family of standards, the OGC community has extended its suite of standards to include Resource Oriented Architectures and Web Application Programming Interfaces (APIs). These standards are based on a shared foundation, specified in OGC API-Common, which defines the resources and access paths that are supported by all OGC APIs. The resources are listed in Table 1. This document extends that foundation to define the EDR API." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72588,61 +72692,104 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-167r2" + "@value": "19-086r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Semantic annotations in OGC standards" + "@value": "OGC API - Environmental Data Retrieval Standard" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/profile", - "http://www.w3.org/2004/02/skos/core#narrower": [ + "@id": "http://www.opengis.net/def/docs/21-058", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/10-140r1" - }, + "@type": "xsd:date", + "@value": "2021-11-08" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/10-100r3" - }, + "@value": "Leonard Daly, Rollin Phillips" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/13-082r2" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/05-095r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/05-099r2" - }, + "@id": "https://docs.ogc.org/per/21-058.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/05-096r1" + "@language": "en", + "@value": "21-058" }, { - "@id": "http://www.opengis.net/def/docs/05-094r1" + "@language": "en", + "@value": "Interoperable Simulation and Gaming Sprint Year 2 Engineering Report" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ + { + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "The OGC Interoperable Simulation and Gaming Year 2 Sprint advanced the use of relevant OGC and Khronos Group [1] standards in the modeling, simulation, and training communities through capability development, compatibility testing, and gap analysis. Of particular interest was the use of glTF models, game engines, and 3rd-party mobile device libraries for the display and interaction with data using OGC APIs." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ + { + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "21-058" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@language": "en", + "@value": "Interoperable Simulation and Gaming Sprint Year 2 Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-028r1", + "@id": "http://www.opengis.net/def/docs/16-107r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-10-14" + "@value": "2017-09-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Edric Keighan, Benjamin Pross, Hervé Caumont" + "@value": "Paul Scarponcini " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -72652,27 +72799,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=59618" + "@id": "https://portal.ogc.org/files/?artifact_id=75929" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed 10 Performance of OGC® Services in the Cloud: The WMS, WMTS, and WPS cases" + "@value": "16-107r2" }, { "@language": "en", - "@value": "14-028r1" + "@value": "InfraGML 1.0: Part 7 – LandInfra Land Division - Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document characterizes the performance and scalability of OGC data services in the Cloud. Three use cases highlighting different geo-processing aspects of OGC data services have been developed, implemented, and benchmarked. Each use case is presented in a separate section of this document with performance results and discussions. " + "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 7 addresses the LandDivision and Condominium Requirements Classes from LandInfra.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72683,30 +72830,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-028r1" + "@value": "16-107r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed 10 Performance of OGC® Services in the Cloud: The WMS, WMTS, and WPS cases" + "@value": "OGC InfraGML 1.0: Part 7 – LandInfra Land Division - Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-107r1", + "@id": "http://www.opengis.net/def/docs/18-037r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-05-07" + "@value": "2018-10-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Cristian Opincaru" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -72721,17 +72868,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20859" + "@id": "https://docs.ogc.org/dp/18-037r1/18-037r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Trusted Geo Services IPR" + "@value": "18-037r1" }, { "@language": "en", - "@value": "06-107r1" + "@value": "GeoPackage / OWS Context Harmonization Discussion Paper" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -72741,7 +72888,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Trusted Geo Services Interoperability Program Report (IPR) provides guidance for the exchange of trusted messages between OGC Web Services and clients for these services. It describes a trust model based on the exchange and brokering of security tokens, as proposed by the OASIS WS-Trust specification [http://docs.oasis-open.org/ws-sx/ws-trust/200512]. " + "@value": "This OGC discussion paper presents an approach to harmonize the OGC GeoPackage and OWS Context standards through a set of extensions. GeoPackage is an open, standards-based, platform-independent, portable, self-describing, compact format for storing and transferring geospatial data and information as part of an SQLite database. OWS Context is an open format linking geospatial web services and information. A draft standard has been produced and this Discussion Paper is designed to be a companion to that draft standard to assist in discussion. The draft standard contains extensions to both GeoPackage and OWS Context.\r\n\r\nThis document is the work of collaboration between the GeoPackage and OWS Context Standards Working Groups (SWGs)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72752,30 +72899,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-107r1" + "@value": "18-037r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Trusted Geo Services IPR" + "@value": "GeoPackage / OWS Context Harmonization Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-067", + "@id": "http://www.opengis.net/def/docs/17-032r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-10-22" + "@value": "2018-01-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Blodgett" + "@value": "Anneley McMillan, Sam Meek" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -72790,17 +72937,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-067.html" + "@id": "https://docs.ogc.org/per/17-032r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Second Environmental Linked Features Experiment" + "@value": "17-032r2" }, { "@language": "en", - "@value": "20-067" + "@value": "Testbed-13: Aviation Abstract Quality Model Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -72810,7 +72957,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report documents the Second Environmental Linked Features Interoperability Experiment (SELFIE). SELFIE evaluated a proposed Web resource model and HTTP behavior for linked data about and among environmental features. The outcomes are building blocks to establish a system of real-world feature identifiers and landing pages that document them. OGC API - Features was found to be a useful component for systems implementing both landing content and representations of linked-features. More work is needed to establish best practices related to negotiation between varied representations of a feature, observations related to a feature, and for expressing and mediating between varied content from a given resource. These technical / meta-model details were found to be difficult to evaluate given the small number of example implementations and limited number of domain-feature models available for use with linked data." + "@value": "This OGC® Engineering Report (ER) describes an Abstract Quality Model (AQM) for data in the aviation domain. Requirements for data quality in aviation are stringent, as the data is often used for safety critical purposes. The services considered are those that serve aeronautical information, flight information and weather forecasting. The model is built upon recognized standards of the International Organization for Standardization (ISO) with extensions and additions made according to the requirements of the domain. These requirements include an ability for the model to record information about the precision of measurements and an understanding of the timeliness of a piece of data, as information utility degrades with time. The result is an ISO compliant data quality model with the required extensions included." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72821,30 +72968,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-067" + "@value": "17-032r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Second Environmental Linked Features Experiment" + "@value": "OGC Testbed-13: Aviation Abstract Quality Model Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-054", + "@id": "http://www.opengis.net/def/docs/14-028r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-11-18" + "@value": "2014-10-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stephane Fellah" + "@value": "Edric Keighan, Benjamin Pross, Hervé Caumont" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -72859,17 +73006,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64405" + "@id": "https://portal.ogc.org/files/?artifact_id=59618" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-11 Implementing Linked Data and Semantically Enabling OGC Services Engineering Report" + "@value": "14-028r1" }, { "@language": "en", - "@value": "15-054" + "@value": "Testbed 10 Performance of OGC® Services in the Cloud: The WMS, WMTS, and WPS cases" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -72879,7 +73026,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Engineering Report (ER) summarizes the approaches, findings and the results\r\nof the Linked Data and Semantic Enablement of OGC Web Services sub-thread activities\r\nof the OGC Testbed-11 Cross Community Interoperability (CCI) Thread. This report\r\nprovides an overview of existing standards for geosemantics, outlines the approaches\r\nadopted during the testbed, describes the conceptual semantic models and services\r\ndeveloped during this testbed to leverage Linked Data and semantic enabled OGC web\r\nservices." + "@value": "This document characterizes the performance and scalability of OGC data services in the Cloud. Three use cases highlighting different geo-processing aspects of OGC data services have been developed, implemented, and benchmarked. Each use case is presented in a separate section of this document with performance results and discussions. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -72890,582 +73037,242 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-054" + "@value": "14-028r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed-11 Implementing Linked Data and Semantically Enabling OGC Services Engineering Report" + "@value": "Testbed 10 Performance of OGC® Services in the Cloud: The WMS, WMTS, and WPS cases" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/is/collection", + "@id": "http://www.opengis.net/def/docs/05-088r1", "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" + "http://www.w3.org/2004/02/skos/core#Concept" ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "http://purl.org/dc/terms/created": [ { - "@value": "Documents of type OGC Implementation Specification" + "@type": "xsd:date", + "@value": "2006-01-18" } ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "http://purl.org/dc/terms/creator": [ { - "@value": "Documents of type OGC Implementation Specification" + "@value": "Arthur Na, Mark Priest" } ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/17-003r2" - }, - { - "@id": "http://www.opengis.net/def/docs/05-005" - }, - { - "@id": "http://www.opengis.net/def/docs/21-057" - }, - { - "@id": "http://www.opengis.net/def/docs/16-079" - }, - { - "@id": "http://www.opengis.net/def/docs/21-026" - }, - { - "@id": "http://www.opengis.net/def/docs/09-148r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-026r1" - }, - { - "@id": "http://www.opengis.net/def/docs/99-054" - }, - { - "@id": "http://www.opengis.net/def/docs/19-086r5" - }, - { - "@id": "http://www.opengis.net/def/docs/07-068r4" - }, - { - "@id": "http://www.opengis.net/def/docs/12-084r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-141r6" - }, - { - "@id": "http://www.opengis.net/def/docs/15-043r3" - }, - { - "@id": "http://www.opengis.net/def/docs/10-090r3" - }, - { - "@id": "http://www.opengis.net/def/docs/12-128r17" - }, - { - "@id": "http://www.opengis.net/def/docs/22-051r7" - }, - { - "@id": "http://www.opengis.net/def/docs/15-042r6" - }, - { - "@id": "http://www.opengis.net/def/docs/17-080r2" - }, - { - "@id": "http://www.opengis.net/def/docs/15-018r2" - }, - { - "@id": "http://www.opengis.net/def/docs/12-128r18" - }, - { - "@id": "http://www.opengis.net/def/docs/19-008r4" - }, - { - "@id": "http://www.opengis.net/def/docs/99-050" - }, - { - "@id": "http://www.opengis.net/def/docs/08-085r4" - }, - { - "@id": "http://www.opengis.net/def/docs/08-094r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-007r4" - }, - { - "@id": "http://www.opengis.net/def/docs/12-128r12" - }, - { - "@id": "http://www.opengis.net/def/docs/12-128r14" - }, - { - "@id": "http://www.opengis.net/def/docs/16-106r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-121r3" - }, - { - "@id": "http://www.opengis.net/def/docs/12-128r19" - }, - { - "@id": "http://www.opengis.net/def/docs/09-127r2" - }, - { - "@id": "http://www.opengis.net/def/docs/13-026r8" - }, - { - "@id": "http://www.opengis.net/def/docs/16-008r1" - }, - { - "@id": "http://www.opengis.net/def/docs/22-050r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-069r3" - }, - { - "@id": "http://www.opengis.net/def/docs/10-129r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-066r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-107r2" - }, - { - "@id": "http://www.opengis.net/def/docs/12-000r2" - }, - { - "@id": "http://www.opengis.net/def/docs/15-112r4" - }, - { - "@id": "http://www.opengis.net/def/docs/08-007r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-100r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-007r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-144r4" - }, - { - "@id": "http://www.opengis.net/def/docs/11-014r3" - }, - { - "@id": "http://www.opengis.net/def/docs/12-132r4" - }, - { - "@id": "http://www.opengis.net/def/docs/11-030r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-083r2" - }, - { - "@id": "http://www.opengis.net/def/docs/15-045r7" - }, - { - "@id": "http://www.opengis.net/def/docs/14-111r6" - }, - { - "@id": "http://www.opengis.net/def/docs/23-008r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-083r2" - }, - { - "@id": "http://www.opengis.net/def/docs/16-071r3" - }, - { - "@id": "http://www.opengis.net/def/docs/17-047r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-078r6" - }, - { - "@id": "http://www.opengis.net/def/docs/14-055r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-110r4" - }, - { - "@id": "http://www.opengis.net/def/docs/07-057r7" - }, - { - "@id": "http://www.opengis.net/def/docs/16-100r2" - }, - { - "@id": "http://www.opengis.net/def/docs/17-086r3" - }, - { - "@id": "http://www.opengis.net/def/docs/21-056r11" - }, - { - "@id": "http://www.opengis.net/def/docs/13-131r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-042r3" - }, - { - "@id": "http://www.opengis.net/def/docs/05-077r4" - }, - { - "@id": "http://www.opengis.net/def/docs/11-038R2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-006r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-074" - }, - { - "@id": "http://www.opengis.net/def/docs/08-059r3" - }, - { - "@id": "http://www.opengis.net/def/docs/10-157r4" - }, - { - "@id": "http://www.opengis.net/def/docs/09-146r6" - }, - { - "@id": "http://www.opengis.net/def/docs/08-085r8" - }, - { - "@id": "http://www.opengis.net/def/docs/09-110r4" - }, - { - "@id": "http://www.opengis.net/def/docs/18-043r3" - }, - { - "@id": "http://www.opengis.net/def/docs/07-036" - }, - { - "@id": "http://www.opengis.net/def/docs/18-000" - }, - { - "@id": "http://www.opengis.net/def/docs/16-101r2" - }, - { - "@id": "http://www.opengis.net/def/docs/14-065" - }, - { - "@id": "http://www.opengis.net/def/docs/12-128r10" - }, - { - "@id": "http://www.opengis.net/def/docs/18-067r3" - }, - { - "@id": "http://www.opengis.net/def/docs/09-025r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-104r4" - }, - { - "@id": "http://www.opengis.net/def/docs/14-084r2" - }, - { - "@id": "http://www.opengis.net/def/docs/12-080r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-121r9" - }, - { - "@id": "http://www.opengis.net/def/docs/05-047r3" - }, - { - "@id": "http://www.opengis.net/def/docs/15-112r2" - }, - { - "@id": "http://www.opengis.net/def/docs/10-025r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-098r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-019" - }, - { - "@id": "http://www.opengis.net/def/docs/13-133r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-103r4" - }, - { - "@id": "http://www.opengis.net/def/docs/08-085r5" - }, - { - "@id": "http://www.opengis.net/def/docs/16-104r2" - }, - { - "@id": "http://www.opengis.net/def/docs/19-045r3" - }, - { - "@id": "http://www.opengis.net/def/docs/20-010" - }, - { - "@id": "http://www.opengis.net/def/docs/08-068r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-032r3" - }, - { - "@id": "http://www.opengis.net/def/docs/21-065r2" - }, - { - "@id": "http://www.opengis.net/def/docs/04-094" - }, - { - "@id": "http://www.opengis.net/def/docs/12-176r7" - }, - { - "@id": "http://www.opengis.net/def/docs/11-165r2" - }, - { - "@id": "http://www.opengis.net/def/docs/19-072" - }, - { - "@id": "http://www.opengis.net/def/docs/15-098r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-097r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-120r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-102r2" - }, - { - "@id": "http://www.opengis.net/def/docs/15-042r5" - }, - { - "@id": "http://www.opengis.net/def/docs/12-000" - }, - { - "@id": "http://www.opengis.net/def/docs/17-069r4" - }, - { - "@id": "http://www.opengis.net/def/docs/20-050" - }, - { - "@id": "http://www.opengis.net/def/docs/12-168r6" - }, - { - "@id": "http://www.opengis.net/def/docs/16-008" - }, - { - "@id": "http://www.opengis.net/def/docs/18-058r1" - }, - { - "@id": "http://www.opengis.net/def/docs/22-049r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-099r1" - }, - { - "@id": "http://www.opengis.net/def/docs/08-028r7" - }, - { - "@id": "http://www.opengis.net/def/docs/12-006" - }, - { - "@id": "http://www.opengis.net/def/docs/17-089r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-007r7" - }, - { - "@id": "http://www.opengis.net/def/docs/17-083r4" - }, - { - "@id": "http://www.opengis.net/def/docs/01-009" - }, - { - "@id": "http://www.opengis.net/def/docs/09-000" - }, - { - "@id": "http://www.opengis.net/def/docs/16-060r2" - }, - { - "@id": "http://www.opengis.net/def/docs/15-111r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-086r6" - }, - { - "@id": "http://www.opengis.net/def/docs/11-017" - }, - { - "@id": "http://www.opengis.net/def/docs/23-024" - }, - { - "@id": "http://www.opengis.net/def/docs/22-022r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-000" - }, - { - "@id": "http://www.opengis.net/def/docs/17-066r2" - }, - { - "@id": "http://www.opengis.net/def/docs/07-147r2" - }, - { - "@id": "http://www.opengis.net/def/docs/17-007r1" - }, - { - "@id": "http://www.opengis.net/def/docs/13-057r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-024r4" - }, - { - "@id": "http://www.opengis.net/def/docs/14-083r2" - }, - { - "@id": "http://www.opengis.net/def/docs/06-131r6" - }, - { - "@id": "http://www.opengis.net/def/docs/10-126r4" - }, - { - "@id": "http://www.opengis.net/def/docs/15-113r5" - }, - { - "@id": "http://www.opengis.net/def/docs/10-032r8" - }, - { - "@id": "http://www.opengis.net/def/docs/15-108r3" - }, - { - "@id": "http://www.opengis.net/def/docs/08-068r2" - }, + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/20-057" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/16-007r3" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=12846" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/15-112r3" + "@language": "en", + "@value": "05-088r1" }, { - "@id": "http://www.opengis.net/def/docs/19-079r2" - }, + "@language": "en", + "@value": "Sensor Observation Service" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/10-070r2" - }, + "@id": "http://www.opengis.net/def/doc-type/d-dp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/18-062r2" - }, + "@value": "A Sensor Observation Service provides an API for managing deployed sensors and retrieving sensor data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today. " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/10-140r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/16-007r5" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "05-088r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/19-011r4" - }, + "@language": "en", + "@value": "Sensor Observation Service" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/19-062", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/15-113r3" - }, + "@type": "xsd:date", + "@value": "2019-11-14" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/05-078r4" - }, + "@value": "Gobe Hobona" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/19-086r4" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/16-032r2" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/15-113r6" - }, + "@id": "https://docs.ogc.org/per/19-062.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/11-052r4" + "@language": "en", + "@value": "OGC API Hackathon 2019 Engineering Report" }, { - "@id": "http://www.opengis.net/def/docs/09-083r3" - }, + "@language": "en", + "@value": "19-062" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/09-149r1" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/18-010r7" - }, + "@value": "The subject of this Engineering Report (ER) is a hackathon event that was held from 20 to 21 June 2019 to advance the development of OGC Application Programming Interface (API) specifications. An API is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The OGC API Hackathon 2019, as the event was called, was hosted by Geovation at its hub in London, United Kingdom. The event was sponsored by the European Space Agency (ESA) and Ordnance Survey." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/17-079r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/21-006r2" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "19-062" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/09-001" - }, + "@language": "en", + "@value": "OGC API Hackathon 2019 Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/13-043", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/22-047r1" - }, + "@type": "xsd:date", + "@value": "2014-01-31" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/18-088" - }, + "@value": "Daniele Marchionni, Raul Cafini" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/14-100r2" - }, + "@id": "http://www.opengis.net/def/doc-type/bp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/18-058" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/14-005r3" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=55210" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/06-009r6" + "@language": "en", + "@value": "Download Service for Earth Observation Products Best Practice" }, { - "@id": "http://www.opengis.net/def/docs/06-042" - }, + "@language": "en", + "@value": "13-043" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/16-103r2" - }, + "@id": "http://www.opengis.net/def/doc-type/bp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/16-105r2" - }, + "@value": "This OGC® Best Practices document specifies the interfaces, bindings, requirements,\r\nconformance classes for online download of Earth Observation products. This protocol\r\ncovers several scenarios implemented by European Space Agency - ESA for providing its\r\nproducts to users:\r\n- The EO Product to be downloaded is already available and can be downloaded as\r\nit is.\r\n- The EO Product is not online available but is stored in a near online archive.\r\n- The EO Product is advertised in a Catalogue, but it is not physically available and\r\nit has to be generated on the fly by a processing facility.\r\n- The EO product is archived in several distributed online archives and it can be\r\ndownloaded in parallel.\r\nThe basic scenarios can be simply supported by Web Browsers, the most complex ones\r\nneed a dedicated client (download manager) supporting Metalink and multisource\r\ndownload.\r\nThis Best Practice document has been prepared basing on the work performed in the\r\nframe of ESA’s Next Generation Earth Observation user services and it was initially\r\nproduced during the ESA" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/18-073r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/15-001r4" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "13-043" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type OGC Implementation Specification" + "@language": "en", + "@value": "OGC Download Service for Earth Observation Products Best Practice" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-097", + "@id": "http://www.opengis.net/def/docs/20-082r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-12-19" + "@value": "2023-05-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jérôme JANSOU, Thibault DACLA" + "@value": "Katharina Schleidt, Ilkka Rinne" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -73475,27 +73282,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46394" + "@id": "https://docs.ogc.org/as/20-082r4/20-082r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-097" + "@value": "20-082r4" }, { "@language": "en", - "@value": "OWS-8 AIXM 5.1 Compression Benchmarking" + "@value": "Topic 20 - Observations, measurements and samples" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "AIXM stands today for the de-facto standard for Aeronautical Information Publication, used by air control service providers from Europe, USA and Australia. With version 5.1, it reaches a level of maturity allowing the support of Digital NOTAMs, as the first official version of these messages was published this year.\r\nIn a near future, AIXM will be carried inside WFS requests but also into notification messages along WS event services. This last channel will be the one dedicated to D-NOTAMs. As D-NOTAM is aimed at aircrafts pilots, their transmission to the aircraft will use air/ground data link. Today, datalink communications lack bandwidth and future datalink will still have a limited capacity.\r\n" + "@value": "This document defines a conceptual schema for observations, for features involved in the observation process, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities.\r\n\r\nObservations commonly involve sampling of an ultimate feature-of-interest. This document defines a common set of sample types according to their spatial, material (for ex situ observations) or statistical nature. The schema includes relationships between sample features (sub-sampling, derived samples).\r\n\r\nThis document concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -73506,35 +73313,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-097" + "@value": "20-082r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 AIXM 5.1 Compression Benchmarking" + "@value": "Topic 20 - Observations, measurements and samples" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-099", + "@id": "http://www.opengis.net/def/docs/20-092", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-10-20" + "@value": "2022-08-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mohsen Kalantari" + "@value": "David Graham, Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -73544,27 +73351,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-099.html" + "@id": "https://docs.ogc.org/dp/20-092.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-099" + "@value": "20-092" }, { "@language": "en", - "@value": "Future City Pilot 1 - Automating Urban Planning Using Web Processing Service Engineering Report" + "@value": "CDB X Conceptual Model with Prototyping Examples and Recommendations" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Numerous and diverse technologies push cities towards open and platform-independent information infrastructures to manage human, natural, and physical systems. Future Cities Pilot 1 is an OGC interoperability initiative that aims to demonstrate how cities can begin to reap the benefits of open standards. This document reports how Web Processing Standard (WPS) of OGC was successfully used in automating urban planning processes. This document details the implementation of urban planning processes and rules concerning urban development approval processes." + "@value": "This Discussion Paper documents the results and recommendations of the rapid prototyping activities conducted during the 3D Geospatial Series Tech Sprint II - OGC CDB 2.0 (aka CDB X). This activity was performed in support of Special Operations Forces (SOF) Future Concepts. This effort hopes to accelerate evolution of the OGC CDB standard to meet the needs of planning, rehearsal, and Mission Command systems providing decision support to Special Operations Forces and enabling SOF tactical and operational advantage. OGC industry standards enable interoperability of geospatial data across systems and applications that SOF Operators and analysts use across warfighting functions.\r\n\r\nShort summary of CDB X goal: Meeting the requirements for tactical GEOINT that can be used across warfighting functions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -73575,30 +73382,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-099" + "@value": "20-092" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Future City Pilot 1 - Automating Urban Planning Using Web Processing Service Engineering Report" + "@value": "CDB X Conceptual Model with Prototyping Examples and Recommendations" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-053r1", + "@id": "http://www.opengis.net/def/docs/19-014r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-06-29" + "@value": "2020-10-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -73613,17 +73420,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/as/21-053r1/21-053r1.html" + "@id": "https://docs.ogc.org/as/19-014r3/19-014r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-053r1" + "@value": "Topic 22 - Core Tiling Conceptual and Logical Models for 2D Euclidean Space" }, { "@language": "en", - "@value": "Topic 23 - GeoPackage Conceptual and Logical Model" + "@value": "19-014r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -73633,7 +73440,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document presents the conceptual and logical models for version 1.x of the OGC GeoPackage Standard. The intent is that these models can be used to implement the GeoPackage standard using technology other than a SQLite database." + "@value": "This OGC Abstract Specification (AS) defines:\r\n\r\nA conceptual model for tiling space in any dimension and;\r\n\r\nA logical model for 2D tiled structures and by extension tiling. The logical model is based on the conceptual model.\r\n\r\nThe conceptual model specified in this Abstract Specification could be a sub-class in a more comprehensive Spatial Partitioning Conceptual Model. Additional Parts may be added to this AS for other dimensions, such as 3D, or other uses cases." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -73644,35 +73451,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-053r1" + "@value": "19-014r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 23 - GeoPackage Conceptual and Logical Model" + "@value": "Topic 22 - Core Tiling Conceptual and Logical Models for 2D Euclidean Space" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-086r4", + "@id": "http://www.opengis.net/def/docs/06-142r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-08-13" + "@value": "2007-05-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mark Burgoyne, Dave Blodgett, Chuck Heazel, Chris Little" + "@value": "Carl Reed, PhD. and Martin Thomson" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -73682,27 +73489,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/19-086r4/19-086r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=21630" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC API - Environmental Data Retrieval Standard" + "@value": "GML PIDF-LO Geometry Shape Application Schema for use in the IETF" }, { "@language": "en", - "@value": "19-086r4" + "@value": "06-142r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Environmental Data Retrieval (EDR) Application Programming Interface (API) provides a family of lightweight query interfaces to access spatio-temporal data resources by requesting data at a Position, within an Area, along a Trajectory or through a Corridor. A spatio-temporal data resource is a collection of spatio-temporal data that can be sampled using the EDR query pattern geometries. These patterns are described in the section describing the Core Requirements Class.\r\n\r\nThe goals of the EDR API are to make it easier to access a wide range of data through a uniform, well-defined simple Web interface, and to achieve data reduction to just the data needed by the user or client while hiding much of the data storage complexity. A major use case for the EDR API is to retrieve small subsets from large collections of environmental data, such as weather forecasts, though many other types of data can be accessed. The important aspect is that the data can be unambiguously specified by spatio-temporal coordinates.\r\n\r\nThe EDR API query patterns, such as Position, Area, Cube, Trajectory or Corridor, can be thought of as discrete sampling geometries, conceptually consistent with the feature of interest in the Sensor Observation Service (SOS) standard. A typical EDR data resource is a multidimensional dataset that could be accessed via an implementation of the Web Coverage Service (WCS) standard. In contrast to SOS and WCS, EDR implements the technical baseline of the OGC API family of standards and aims to provide a single set of simple-to-use query patterns. Use cases for EDR range from real or virtual time-series observation retrievals, to sub-setting 4-dimensional data cubes along user-supplied sampling geometries. These query patterns do not attempt to satisfy the full scope of either SOS or WCS, but provide useful building blocks to allow the composition of APIs that satisfy a wide range of geospatial data use cases. By defining a small set of query patterns (and no requirement to implement all of them), the EDR API should help to simplify the design of systems (as they can be performance tuned for the supported queries) making it easier to build robust and scalable infrastructure.\r\n\r\nWith the OGC API family of standards, the OGC community has extended its suite of standards to include Resource Oriented Architectures and Web Application Programming Interfaces (APIs). These standards are based on a shared foundation, specified in OGC API-Common, which defines the resources and access paths that are supported by all OGC APIs. The resources are listed in Table 1. This document extends that foundation to define the Environmental Data Retrieval API." + "@value": "This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for XML encoding of various geometric shapes required in the Presence Information Description Format (IETF RFC 3863) Location Object extension - A Presence-based GEOPRIV Location Object Format (RFC 4119)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -73713,35 +73520,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-086r4" + "@value": "06-142r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Environmental Data Retrieval Standard" + "@value": "GML PIDF-LO Geometry Shape Application Schema for use in the IETF" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-014r7", + "@id": "http://www.opengis.net/def/docs/15-024r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-02-08" + "@value": "2015-08-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed, Tamrat Belayneh" + "@value": "Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -73751,27 +73558,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/17-014r7/17-014r7.html" + "@id": "https://portal.ogc.org/files/?artifact_id=63794" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification" + "@value": "15-024r2" }, { "@language": "en", - "@value": "17-014r7" + "@value": "Testbed 11 Aviation - Guidance on Using Semantics of Business Vocabulary and Business Rules (SBVR) Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data.Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files.\r\n\r\nThe delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types.\r\n\r\nThe open community GitHub version of this standard is here: https://github.com/Esri/i3s-spec [2]." + "@value": "This document is a deliverable of the OGC Testbed 11 . It describes the results of developing a tool to automatically derive Schematron code from SBVR constraints. It also documents a vocabulary with a profile of core geospatial terms and concepts, which can be used to express geospatial constraints in business rules." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -73782,35 +73589,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-014r7" + "@value": "15-024r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification" + "@value": "OGC® Testbed 11 Aviation - Guidance on Using Semantics of Business Vocabulary and Business Rules (SBVR) Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-159", + "@id": "http://www.opengis.net/def/docs/08-133", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-02-05" + "@value": "2008-10-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthes Rieke, Benjamin Pross" + "@value": "Johannes Echterhoff, Thomas Everding" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -73820,27 +73627,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51818" + "@id": "https://portal.ogc.org/files/?artifact_id=29576" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-9 CCI Conflation with Provenance Engineering Report" + "@value": "Sensor Event Service Interface Specification" }, { "@language": "en", - "@value": "12-159" + "@value": "08-133" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Engineering Report describes the architecture of a WPS capable of conflating two datasets while capturing provenance information about the process. The report also provides information about defining and encoding conflation rules and about encoding provenance information. \r\nThis Engineering Report was created as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program.\r\n" + "@value": "The Sensor Event Service (SES) provides operations to register sensors at the service application and let clients subscribe for observations available at the service. The service performs filtering of sensor data (streams) based upon the filter criteria defined in these subscriptions. Filters can be applied on single observations but also on observation streams, potentially aggregating observations into higher-level information (which itself can be regarded as observation data). Whenever matches are discovered, a notification is sent to the subscriber, using asynchronous, push-based communication mechanisms." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -73851,35 +73658,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-159" + "@value": "08-133" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-9 CCI Conflation with Provenance Engineering Report" + "@value": "OpenGIS® Sensor Event Service Interface Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-146", + "@id": "http://www.opengis.net/def/docs/15-112r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2017-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Timo Thomas" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -73889,27 +73696,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51811" + "@id": "https://portal.ogc.org/files/?artifact_id=72714" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-146" + "@value": "15-112r2" }, { "@language": "en", - "@value": "OWS-9 Web Feature Service Temporality Extension Engineering Report" + "@value": "Volume 3: OGC CDB Terms and Definitions" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 9 (OWS-9). This Engineering Report summarizes the OWS-9 activity regarding the extension of the Web Feature Service (WFS) and Filter Encoding (FE) standards to support dynamic feature data.\r\nSpecifically this document describes the result work performed in OWS 9 on the WFS Temporality Extension. The technical specification including background is discussed and defined in the OGC Discussion Paper 12-027r1. This document gives a summary about issues, lessons learned, recommendations, accomplishments and benefits for the Aviation Architecture. It also gives an outlook on future work items and change requests. \r\n" + "@value": "This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -73920,30 +73727,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-146" + "@value": "15-112r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-9 Web Feature Service Temporality Extension Engineering Report" + "@value": "Volume 3: OGC CDB Terms and Definitions" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-022", + "@id": "http://www.opengis.net/def/docs/20-091", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-11" + "@value": "2021-02-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Guy Schumann" + "@value": "Gobe Hobona" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -73958,17 +73765,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-022.html" + "@id": "https://docs.ogc.org/per/20-091.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-022" + "@value": "20-091" }, { "@language": "en", - "@value": "Testbed-13: NA001 Climate Data Accessibility for Adaptation Planning" + "@value": "OGC API – Common and OGC API – Features Sprint 2020: Summary Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -73978,7 +73785,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report describes all Testbed-13 activities relating to the Climate Data Accessibility for Adaptation Planning requirements of the National Aeronautics and Space Administration (NASA). It discusses relevant experiences made during implementation including recommendations to the sponsor, and provides resulting standards change requests to the appropriate working groups. Additionally, it develops best practices for data and model integration and serves as a guidance document to work with NASA Earth Science Data System (ESDS) working groups and externally provided data. The added value of this Engineering Report is to improve interoperability and to advance location-based technologies and realize innovations with regards to NASA Climate Data and NASA ESDS objectives." + "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from 29 to 30 September 2020 to advance the development of the OGC API - Common - Part 2: Geospatial Data draft standard and the OGC API – Features – Part 4: Simple Transactions draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The code sprint was hosted online. The event was sponsored by Ordnance Survey (OS)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -73989,30 +73796,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-022" + "@value": "20-091" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: NA001 Climate Data Accessibility for Adaptation Planning" + "@value": "OGC API – Common and OGC API – Features Sprint 2020: Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-085r1", + "@id": "http://www.opengis.net/def/docs/18-089", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-11-07" + "@value": "2019-10-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Charles Chen" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -74027,17 +73834,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46679" + "@id": "https://docs.ogc.org/per/18-089.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-085r1" + "@value": "18-089" }, { "@language": "en", - "@value": "OWS-8 Bulk Geodata Transfer Using GML Engineering Report" + "@value": "Indoor Mapping and Navigation Pilot Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -74047,7 +73854,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the work done during the OWS-8 test bed investigating methods and apparatus for distributing individual geospatial data sets and/or collections of data sets in a consistent manner between machines that may or may not be connected via a network. The investigation focuses on the initialization of a target WFS, from a source WFS, for the purpose of GeoSynchronization. Data, schema, metadata and/or topology are exported from a source WFS, transferred to a target WFS (either electronically or physically via some media) and then imported into the target WFS. From that point on, the two WFS's are maintained in synchrony using a Geosynchronization Service (see OGC 10-069r2)." + "@value": "The OGC Indoor Mapping and Navigation Pilot Initiative was sponsored by the National Institute of Standards and Technology (NIST) Public Safety Communications Research (PSCR) Division. This initiative addressed key challenges related to indoor mapping and navigation for the purpose of supporting first responders in fields such as fire-fighting. The focus of this initiative was on developing the capabilities and workflows required for pre-planning operations. This included scanning each building to produce a point cloud dataset and converting this source data into various intermediate forms to support the generation of indoor navigation routes. This Engineering Report (ER) describes the work conducted in this initiative, the lessons learned captured by participants, and future recommendations to support the public safety efforts and interoperability of the standards. It is expected that future OGC initiatives will address the real-time, event-driven aspects of indoor mapping and navigation for first response situations.\r\n\r\nFirst responders typically survey high-risk facilities in their jurisdiction at least once per year as part of a pre-planning process. Pre-planning outputs are often in the form of reports, and first responders may generate their own hand-drawn maps during the process or annotate available floor plans (e.g., from computer-aided design models). Pre-planning is time-consuming, inefficient, and inherently complex considering the information and level of detail that should or could be captured, the lack of automation, and the difficulty identifying notable changes to facilities and infrastructure during successive pre-planning surveys.\r\n\r\nMobile three-dimensional (3D) Light Detection and Ranging (LiDAR) has been identified as a potentially transformational technology for first responders. Using LiDAR and 360-degree camera imagery, coupled with advanced software processing, first responders could efficiently capture 3D point clouds and a wealth of other information, both observed and derived, while walking through buildings as part of routine pre-planning operations. The use of 3D LiDAR and imagery has many potential upsides beyond just creating point clouds for visualization and mapping (e.g., use in localization, object classification, integration with virtual/augmented reality solutions, change detection, etc.)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74058,35 +73865,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-085r1" + "@value": "18-089" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-8 Bulk Geodata Transfer Using GML Engineering Report" + "@value": "OGC Indoor Mapping and Navigation Pilot Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-042r1", + "@id": "http://www.opengis.net/def/docs/22-051r7", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-11-11" + "@value": "2024-04-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Lewis John McGibbney" + "@value": "Roger Lott" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74096,27 +73903,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/19-042r1.html" + "@id": "https://docs.ogc.org/is/22-051r7/22-051r7.pdf" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Discussion Paper - JSON Encodings for EO Coverages" + "@value": "OGC GGXF geodetic data grid exchange format" }, { "@language": "en", - "@value": "19-042r1" + "@value": "22-051r7" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This discussion paper documents and concludes one year (2018-2019) of work undertaken by a National Aeronautics and Space Administration (NASA) Earth Science Data System Working Group focused on exploring JSON Encodings in Earth Observation Coverages. The primary function of this paper is to ensure that the collective Working Group knowledge obtained from the year effort is not lost and consequently that it can be considered, debated and hopefully utilized in other forums outside of NASA with the aim of driving progress in this field. The covering statement (below) provides 10 questions which are meant to facilitate such discussion.\r\n\r\nThis discussion paper will be of particular interest to the following parties:\r\n\r\nWeb application developers tasked with designing and developing applications which consume Earth Observation spatial data encoded as JSON.\r\n\r\nParties (including standards bodies) interested in serving and consuming Spatial data on the Web e.g. World Wide Web Consortium (W3C), Open Geospatial Consortium (OGC) or developers of other data standards, etc." + "@value": "The Geodetic data Grid eXchange Format (GGXF) is designed to be a single file format that may be used\r\nfor a wide range of geodetic applications requiring interpolation of regularly gridded data, including (but\r\nnot limited to):\r\n• Transformation of latitude and longitude coordinates from one geodetic coordinate reference\r\nsystem to another;\r\n• Transformation of gravity-related heights from one vertical coordinate reference system to\r\nanother;\r\n• Reduction of ellipsoid heights to the geoid, quasi-geoid or a surface of a vertical reference frame;\r\nand\r\n• The description of coordinate changes due to deformation.\r\nThe GGXF format has been designed specifically for carrying gridded geodetic parameters supporting\r\ncoordinate transformations and point motion operations but has no restriction on the type of content\r\nthat may be included." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74127,35 +73934,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-042r1" + "@value": "22-051r7" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Discussion Paper - JSON Encodings for EO Coverages" + "@value": "OGC GGXF geodetic data grid exchange format" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-126r2", + "@id": "http://www.opengis.net/def/docs/08-028r7", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-21" + "@value": "2008-09-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Chuck Morris" + "@value": "Gil Fuchs" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74165,27 +73972,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=33085" + "@id": "https://portal.ogc.org/files/?artifact_id=28493" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-126r2" + "@value": "08-028r7" }, { "@language": "en", - "@value": "Compliance Test Language (CTL) Best Practice" + "@value": "Location Services (OpenLS): Part 6 - Navigation Service" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document establishes Compliance Test Language, an XML grammar for documenting and scripting suites of tests for verifying that an implementation of a specification complies with the specification." + "@value": "This OpenGIS Implementation Standard defines the interfaces for OpenGIS Location Services (OpenLS): Part 6 - Navigation Service (formerly the Full Profile of the Route Determination Service), which is part of the GeoMobility Server (GMS), an open location services platform. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74196,35 +74003,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-126r2" + "@value": "08-028r7" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Compliance Test Language (CTL) Best Practice" + "@value": "OpenGIS Location Services (OpenLS): Part 6 - Navigation Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-001", + "@id": "http://www.opengis.net/def/docs/15-078r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-03-22" + "@value": "2016-07-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stuart E. Middleton" + "@value": "Steve Liang, Chih-Yuan Huang, Tania Khalafbeigi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74234,27 +74041,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=37139" + "@id": "https://docs.ogc.org/is/15-078r6/15-078r6.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "SANY Fusion and Modelling Architecture" + "@value": "SensorThings API Part 1: Sensing" }, { "@language": "en", - "@value": "10-001" + "@value": "15-078r6" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document reports the considered SANY best practice for using OGC standards to provide generic fusion processing services. Concrete case studies are documented and a detailed appendix is provided with example of XML request and responses." + "@value": "The OGC SensorThings API provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the Web. At a high level the OGC SensorThings API provides two main functionalities and each function is handled by a part. The two parts are the Sensing part and the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. The Tasking part is planned as a future work activity and will be defined in a separate document as the Part II of the SensorThings API." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74265,35 +74072,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-001" + "@value": "15-078r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "SANY Fusion and Modelling Architecture" + "@value": "OGC SensorThings API Part 1: Sensing" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-087r3", + "@id": "http://www.opengis.net/def/docs/17-089r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-12-13" + "@value": "2018-08-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Doug Nebert" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74303,27 +74110,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=3843" + "@id": "https://docs.ogc.org/is/17-089r1/17-089r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Catalog Interface" + "@value": "17-089r1" }, { "@language": "en", - "@value": "02-087r3" + "@value": "WCS Core 2.1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers." + "@value": "The OGC Web Coverage Service (WCS) supports electronic retrieval of geospatial data as coverages. Coverages are digital geospatial information representing space/time-varying phenomena, specifically spatio-temporal regular and irregular grids, point clouds, and general meshes.\r\nThis document specifies the WCS core. Every implementation of a WCS shall adhere to this standard. This standard defines core requirements. Extensions to the core define extensions to meet additional requirements, such as the response encoding. Additional extensions are required in order to completely specify a WCS for implementation.\r\nThis WCS 2.1 standard extends WCS 2.0 in a backwards compatible manner by accommodating coverages as per the OGC Coverage Implementation Schema (CIS) 1.1 in addition to CIS 1.0 coverages as addressed by WCS 2.0.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74334,35 +74141,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-087r3" + "@value": "17-089r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Catalog Interface" + "@value": "OGC Web Coverage Service (WCS) 2.1 Interface Standard - Core" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-071", + "@id": "http://www.opengis.net/def/docs/03-081r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-09-12" + "@value": "2003-11-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mike Botts" + "@value": "Joshua Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/rfc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74372,27 +74179,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=29466" + "@id": "https://portal.ogc.org/files/?artifact_id=11499" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS 5 Engineering Report: Supporting Georeferenceable Imagery" + "@value": "Web Terrain Service RFC" }, { "@language": "en", - "@value": "08-071" + "@value": "03-081r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/rfc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The scope of this document is to capture considerations and recommendations on approaches for supporting georeferenceable imagery within the OGC encodings and web services. Georeferenceable imagery is typically imagery coming from a remote sensor that has not been previously geo-rectified, resampled, or regridded. Georeferenceable imagery must be accompanied with information sufficient to allow georectification of the imagery.\r\n" + "@value": "This document is a companion specification to the OpenGIS Web Map Service Interface Implementation Specification version 1.1.1 [4], hereinafter WMS 1.1.1. \r\nWMS 1.1.1 specifies how individual map servers describe and provide their map content. The present Web Terrain Service specification describes a new operation, GetView, and extended Capabilities which allow a 3D terrain view image to be requested, given a map composition, a terrain model on which to drape the map, and a 3D viewpoint from which to render the terrain view. A simple attempt is also made to reconcile 2D and 3D viewpoints by allowing the requested 3D area of view to be approximated with a WMS 1.1.1 bounding box" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74403,35 +74210,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-071" + "@value": "03-081r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS 5 Engineering Report: Supporting Georeferenceable Imagery" + "@value": "OpenGIS Web Terrain Service RFC" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-095", + "@id": "http://www.opengis.net/def/docs/02-039r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-01-25" + "@value": "2002-10-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis, Johannes Echterhoff" + "@value": "Roland Wagner" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74441,27 +74248,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=18776" + "@id": "https://portal.ogc.org/files/?artifact_id=11500" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-095" + "@value": "02-039r1" }, { "@language": "en", - "@value": "Web Notification Service" + "@value": "Web Pricing and Ordering" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": " A service by which a client may conduct asynchronous dialogues (message interchanges) with one or more other services. This service is useful when many collaborating services are required to satisfy a client request, and/or when significant delays are involved is satisfying the request. This service was defined under OWS 1.2 in support of SPS operations. WNS has broad applicability in many such multi-service applications. It is now used in several SWE scenarios." + "@value": "This specification covers all standard geo-eBusiness processes like pricing, ordering and online delivery for spatial products." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74472,35 +74279,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-095" + "@value": "02-039r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Notification Service" + "@value": "Web Pricing and Ordering" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-019r1", + "@id": "http://www.opengis.net/def/docs/20-041", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-02-28" + "@value": "2021-01-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Lansing" + "@value": "Joan Maso" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/ipr" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74510,27 +74317,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1121" + "@id": "https://docs.ogc.org/per/20-041.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Coverage Portrayal Service" + "@value": "20-041" }, { "@language": "en", - "@value": "02-019r1" + "@value": "Analysis Ready Data Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/ipr" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Coverage Portrayal Service (CPS) IPR proposes a standard interface for producing visual pictures from coverage data." + "@value": "The Committee on Earth Observation Satellites (CEOS) defines Analysis Ready Data (ARD) for Land (CARD4L) as satellite data that have been processed to a minimum set of requirements and organized into a form that allows immediate analysis with a minimum of additional user effort and interoperability both through time and with other datasets.\r\n\r\nThis OGC Testbed 16 Engineering Report (ER) generalizes the ARD concept and studies its implications for the OGC Standards baseline. In particular, the ER analyses how modern federated data processing architectures applying data cubes and Docker packages can take advantage of the existence of ARD. Architectures for ARD should minimize data transmission and allow and favor code transmission and remote execution. This ER also considers a workflow in which new processes are triggered as soon as new data becomes available. This is part of the event driven discussion." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74541,35 +74348,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-019r1" + "@value": "20-041" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Coverage Portrayal Service" + "@value": "OGC Testbed-16: Analysis Ready Data Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-026", + "@id": "http://www.opengis.net/def/docs/04-071", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-07-14" + "@value": "2004-10-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Maso" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74579,27 +74386,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/21-026/21-026.html" + "@id": "https://portal.ogc.org/files/?artifact_id=7257" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-026" + "@value": "04-071" }, { "@language": "en", - "@value": "OGC Cloud Optimized GeoTIFF Standard" + "@value": "Some image geometry models" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Cloud Optimized GeoTIFF (COG) relies on two characteristics of the TIFF v6 format (tiles and reduced resolution subfiles), GeoTIFF keys for georeference, and the HTTP range, which allows for efficient downloading of parts of imagery and grid coverage data on the web and to make fast data visualization of TIFF or BigTIFF files and fast geospatial processing workflows possible. COG-aware applications can download only the information they need to visualize or process the data on the web. Numerous remote sensing datasets are available in cloud storage facilities that can benefit from optimized visualization and processing. This standard formalizes the requirements for a TIFF file to become a COG file and for the HTTP server to make COG files available in a fast fashion on the web.\r\n\r\nThe key work for crafting this OGC Standard was undertaken in the Open-Earth-Monitor Cyberinfrastructure (OEMC) project, which received funding from the European Union’s Horizon Europe research and innovation program under grant agreement number 101059548 and in the All Data 4 Green Deal - An Integrated, FAIR Approach for the Common European Data Space (AD4GD) project, which received funding from the European Union’s Horizon Europe research and innovation program under grant agreement number 101061001." + "@value": "This discussion paper contains the material that is still relevant from Section 6 (or Appendix A) of the previous version 4 (document OGC 99-107) of OGC Abstract Specification Topic 7, titled The Earth Imagery Case. That version of Topic 7 has now been superseded by a new version with the same title.\r\nIn addition, some terminology has been revised to be consistent with the terminology now used in Topic 16: Image Coordinate Transformation Services. Specifically, the previous term real-time image geometry model has been changed to approximate image geometry model. Also, the previous name Universal Real-Time Image Geometry Model has been changed to Universal Image Geometry Model.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74610,35 +74417,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-026" + "@value": "04-071" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Cloud Optimized GeoTIFF Standard" + "@value": "Some image geometry models" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-099r2", + "@id": "http://www.opengis.net/def/docs/21-008", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-18" + "@value": "2021-04-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Gobe Hobona, Angelos Tzotsos, Tom Kralidis, Martin Desruisseaux" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/profile" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74648,27 +74455,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13206" + "@id": "https://docs.ogc.org/per/21-008.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-099r2" + "@value": "Joint OGC OSGeo ASF Code Sprint 2021 Summary Engineering Report" }, { "@language": "en", - "@value": "GML 3.1.1 simple dictionary profile" + "@value": "21-008" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/profile" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding simple dictionaries. This profile can be used without a GML Application Schema, and such use is assumed in this document." + "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from 17 to 19 February 2021 to advance support of open geospatial standards within the developer community, whilst also advancing the standards themselves. The code sprint was hosted by the Open Geospatial Consortium (OGC), the Apache Software Foundation (ASF), and Open Source Geospatial Foundation (OSGeo). The event was sponsored by Ordnance Survey (OS) and GeoCat BV, and held as a completely virtual event." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74679,35 +74486,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-099r2" + "@value": "21-008" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML 3.1.1 simple dictionary profile" + "@value": "Joint OGC OSGeo ASF Code Sprint 2021 Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-032", + "@id": "http://www.opengis.net/def/docs/20-072r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-09-11" + "@value": "2023-10-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "Hugo Ledoux, Balázs Dukai" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74717,27 +74524,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=53823" + "@id": "https://docs.ogc.org/cs/20-072r5/20-072r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "13-032" + "@value": "CityJSON Community Standard 2.0" }, { "@language": "en", - "@value": "SWE Implementation Maturity Engineering Report" + "@value": "20-072r5" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report summarizes the outcomes of a process to assess the maturity of implementations based on SWE standards. This report covers the following areas:\r\n•\tSWE standards overview\r\n•\tImplementations of SWE in major systems\r\n•\tSWE software implementations and compliance\r\n•\tSWE implementations in IP\r\n•\tRecommendations and Observations\r\nA main outcome is the summary assessment of the SWE Implementation Maturity as presented in the Preface based on the body of the report.\r\n" + "@value": "CityJSON is a data exchange format for digital 3D models of cities and landscapes. It aims at being easy-to-use (for reading, processing, and creating datasets), and it was designed with programmers in mind, so that tools and APIs supporting it can be quickly built. The JSON-based encoding of CityJSON implements a subset of the OGC CityGML data model (version 3.0) and includes a JSON-specific extension mechanism. Using JSON instead of GML allows us to compress files by a factor 6 and at the same time to simplify greatly the structure of the files." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74748,66 +74555,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-032" + "@value": "20-072r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® SWE Implementation Maturity Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/dp-draft/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type Discussion Paper - draft" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Documents of type Discussion Paper - draft" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/06-021r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Documents of type Discussion Paper - draft" + "@value": "CityJSON Community Standard 2.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-129", + "@id": "http://www.opengis.net/def/docs/11-044", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-02-16" + "@value": "2011-05-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Nadine Alameh" + "@value": "Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74817,27 +74593,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=35634" + "@id": "https://portal.ogc.org/files/?artifact_id=43999" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report" + "@value": "OGC Geography Markup Language (GML) simple features profile Technical Note" }, { "@language": "en", - "@value": "09-129" + "@value": "11-044" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This AIP-2 Engineering Report (ER) describes a set of transverse technology Use Cases developed and applied in the GEOSS Architecture Implementation Pilot Phase 2 (AIP-2). Such Use Cases define reusable activities within a service-oriented architecture, tailored for the GEOSS environment. This report contains the general Use Cases that were specialized by community Working Groups to implement several specific Societal Benefit Area (SBA) Scenarios in AIP-2. The SBA Scenarios and specialized use cases are defined in separate AIP-2 ERs. This AIP-2 ER will be offered for consideration by the GEOSS Best Practice Registry editors and to OGC Technical Committee for consideration as a Best Practice." + "@value": "This technical note enhances the OGC GML simple features profile to include circles, circular arc, and corrects the annex numbering, and clarifies how to specify conformance classes." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74848,35 +74624,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-129" + "@value": "11-044" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report" + "@value": "OGC Geography Markup Language (GML) simple features profile Technical Note" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-099", + "@id": "http://www.opengis.net/def/docs/18-087r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-11-06" + "@value": "2018-12-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jan Herrmann, Andreas Matheus" + "@value": "Terry Idol, Robert Thomas" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74886,27 +74662,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55230" + "@id": "https://portal.ogc.org/files/18-087r5" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "13-099" + "@value": "Development of Disaster Spatial Data Infrastructures for Disaster Resilience" }, { "@language": "en", - "@value": "GeoXACML and XACML Policy Administration Web Service (PAWS)" + "@value": "18-087r5" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This specification defines the interfaces of the OGC (Geo)XACML Policy Administration Web Service (OGC (Geo)XACML PAWS or simply PAWS in the following) that supports the creation, modification, exchange, analysis, testing, transformation, encrypting and signing of XACML and GeoXACML encoded access control policies.\r\nThis draft specification was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. This document presents the results of the work within add-on project of the OWS-9 Security and Services Interoperability (SSI) thread. \r\nPlease note that currently the document only contains the definition of the mandatory operations i.e. the basic conformance class. The writing of the sections describing the optional operations is still a to do. These sections need to define the following operations:\r\n•\tAnalyzePolicyElement operation\r\n•\tOptimizePolicyElement operation \r\n•\tTransformPolicyElement operation\r\n•\tTestPolicyElement operation \r\n•\tEncryptPolicy operation\r\n•\tSignPolicy operation \r\nSuggested additions, changes, and comments on this report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document.\r\n" + "@value": "This report presents the results of a concept development study on Disasters Interoperability, sponsored by US Geological Survey (USGS) and Federal Geographic Data Committee (FGDC), and Department of Homeland Security (DHS), and executed by the Open Geospatial Consortium (OGC). The focus of this study was to understand how to best support the development of, or combination of SDI(s) for the use in disasters, to advance the understanding of stakeholder issues, and serve stakeholders’ needs. The study included stakeholder engagements, workshops and open Request for Information (RFI) that gathered external international positions and opinions on the optimal setup and design of an SDI for disasters. The outflow of this report will guide a series of interoperability pilots to address priority challenges identified by the community in this study. The report follows the format and document of the OGC Arctic Spatial Data Pilot; Phase 1 Report: Spatial Data Sharing for the Arctic. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74917,35 +74693,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-099" + "@value": "18-087r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoXACML and XACML Policy Administration Web Service (PAWS)" + "@value": "OGC Development of Disaster Spatial Data Infrastructures for Disaster Resilience" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-192", + "@id": "http://www.opengis.net/def/docs/12-029", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-01-03" + "@value": "2012-04-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Harrison" + "@value": "Bastian Schäffer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -74955,27 +74731,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=41734" + "@id": "https://portal.ogc.org/files/?artifact_id=47860" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Authentication IE Enginerring Report " + "@value": "12-029" }, { "@language": "en", - "@value": "10-192" + "@value": "Web Processing Service Best Practices Discussion Paper" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Results of the Auth IE are presented in this Engineering Report document and serve as guidance to both implementers and organizations deploying solutions that involve basic authentication. It is the belief of the Auth IE participants that if such a document is made available to the community more OGC implementing products will natively support authentication. " + "@value": "The following document contains best practices for identifying input data formats for the OGC WPS 1.0.0. It was created due to a lack of interoperability between different WPS implementation based on non-standardized input identifiers." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -74986,35 +74762,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-192" + "@value": "12-029" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Authentication IE Enginerring Report " + "@value": "Web Processing Service Best Practices Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-051r7", + "@id": "http://www.opengis.net/def/docs/17-014r8", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-04-29" + "@value": "2021-12-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Lott" + "@value": "Carl Reed, Tamrat Belayneh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75024,27 +74800,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/22-051r7/22-051r7.pdf" + "@id": "https://docs.ogc.org/cs/17-014r8/17-014r8.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC GGXF geodetic data grid exchange format" + "@value": "17-014r8" }, { "@language": "en", - "@value": "22-051r7" + "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Geodetic data Grid eXchange Format (GGXF) is designed to be a single file format that may be used\r\nfor a wide range of geodetic applications requiring interpolation of regularly gridded data, including (but\r\nnot limited to):\r\n• Transformation of latitude and longitude coordinates from one geodetic coordinate reference\r\nsystem to another;\r\n• Transformation of gravity-related heights from one vertical coordinate reference system to\r\nanother;\r\n• Reduction of ellipsoid heights to the geoid, quasi-geoid or a surface of a vertical reference frame;\r\nand\r\n• The description of coordinate changes due to deformation.\r\nThe GGXF format has been designed specifically for carrying gridded geodetic parameters supporting\r\ncoordinate transformations and point motion operations but has no restriction on the type of content\r\nthat may be included." + "@value": "The Indexed 3D Scene Layer (I3S) format is an open 3D content delivery format used to rapidly stream and distribute large volumes of 3D GIS data to mobile, web and desktop clients. I3S content can be shared across enterprise systems using both physical and cloud servers.\r\n\r\nA single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files.\r\n\r\nThe delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types.\r\n\r\nThe open community GitHub source for this Community Standard is here." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75055,30 +74831,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-051r7" + "@value": "17-014r8" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GGXF geodetic data grid exchange format" + "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.2" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-053r5", + "@id": "http://www.opengis.net/def/docs/14-021r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-10-09" + "@value": "2014-04-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Bastian Schäffer" + "@value": "Gobe Hobona, Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -75093,17 +74869,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34968" + "@id": "https://portal.ogc.org/files/?artifact_id=57336" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-053r5" + "@value": "14-021r2" }, { "@language": "en", - "@value": "OWS-6 Geoprocessing Workflow Architecture Engineering Report" + "@value": "Testbed 10 CCI Profile Interoperability Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -75113,7 +74889,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document covers Geoprocessing Workflow best practices and methods in a SOA environment. A RESTful approach was also conducted in this testbed, but no specific implementation details were available to be included in this ER; also, the RESTful workflow approaches and technology used in this testbed was essentially same as that used in OWS-5." + "@value": "This Engineering Report was prepared as a deliverable for OGC Testbed 10, an initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Cross Community Interoperability (CCI) thread within the testbed. The work has been commissioned in order to inform geospatial information frameworks of the Defence Geospatial Information Working Group (DGIWG), National System for Geospatial Intelligence (NSG) of the US National Geospatial Intelligence Agency (NGA) and the UK Ministry of Defence (MOD).\r\nThe Engineering Report presents an analysis and assessment of interoperability between DGIWG, NSG and UK MOD profiles of Web Map Service (WMS) and Web Feature Service (WFS) standards of the OGC. The engineering report also presents findings from the implementation of the reference profiles.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75124,35 +74900,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-053r5" + "@value": "14-021r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 Geoprocessing Workflow Architecture Engineering Report" + "@value": "OGC® Testbed 10 CCI Profile Interoperability Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-058r1", + "@id": "http://www.opengis.net/def/docs/99-108r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-07-08" + "@value": "1999-03-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis, Chrsitian Malewski" + "@value": "Cliff Kottman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75162,27 +74938,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=44438" + "@id": "https://portal.ogc.org/files/?artifact_id=894" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-058r1" + "@value": "Topic 08 - Relationships Between Features" }, { "@language": "en", - "@value": "*FL Starfish Fungus Language for Sensor Description" + "@value": "99-108r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Starfish Fungus Language was developed in response to the high number of complaints addressing issues with the OGC standard Sensor Model Language, SensorML. Most complaints circled around the high flexibility of the language in combination with unnecessary abstractions of technical terms, e.g. every sensor is not a sensor but a process. Most beginners struggled with the composite pattern of those processes, as there is no well-defined rule what needs to be described where. As a beginner, it is almost impossible to write a simple sensor description without getting major guidance through the SensorML development team or other experts." + "@value": "This Topic introduces an abstraction for the relationships between entities in the real world. This abstraction is modeled as relationships between the features introduced in Topic 5." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75193,35 +74969,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-058r1" + "@value": "99-108r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "*FL Starfish Fungus Language for Sensor Description " + "@value": "Topic 8 - Relationships Between Features" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-013r1", + "@id": "http://www.opengis.net/def/docs/01-037", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-02-27" + "@value": "2001-03-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Ron Lake" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75231,27 +75007,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1006" + "@id": "https://portal.ogc.org/files/?artifact_id=1042" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "01-013r1" + "@value": "01-037" }, { "@language": "en", - "@value": "High-Level Ground Coordinate Transformation Interface" + "@value": "Location Organizer Folder" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies a " + "@value": "*RETIRED* The Location Organizer Folder (LOF) is a GML document that provides a structure for organizing the information related to a particular event or events of interest." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75262,35 +75038,46 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-013r1" + "@value": "01-037" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "High-Level Ground Coordinate Transformation Interface" + "@value": "Location Organizer Folder" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-081", + "@id": "http://www.opengis.net/def/doc-type/pc", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/06-113" + }, + { + "@id": "http://www.opengis.net/def/docs/06-111" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/18-016r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-03-23" + "@value": "2018-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Josh Lieberman" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75300,27 +75087,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-081.html" + "@id": "https://portal.ogc.org/files/18-016r1" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "MUDDI v1.1 (Model for Underground Data Definition and Integration) Engineering Report" + "@value": "18-016r1" }, { "@language": "en", - "@value": "19-081" + "@value": " CDB Version 1.1 Release Notes" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Underground Infrastructure Concept Development Study (UICDS) Engineering Report [1] examined the present state of underground infrastructure information (UGII), costs and benefits of that state, as well as future opportunities for an improved state. That report describes a number of candidate models for UGII and recommends a number of follow-on activities, including development of a prototype UGII integration model to support subsequent UGII integration and exchange initiatives. A follow-up workshop and model development effort resulted in another engineering report describing an initial (1.0) version of the conceptual UGII integration model MUDDI (Model for Underground Data Definition and Interchange) [2]. The present updated report describes MUDDI version 1.1. The goal of MUDDI is to serve as the basis for integration of datasets from different models, at the levels of detail required to address application use cases described in [1]. MUDDI as described here is a conceptual model which will serve as the basis for one or more conformant and interchangeable logical and physical implementations such as GML (Geographic Markup Language) or SFS (Simple Features SQL). The current version 1.1 of MUDDI has been updated and refined from the initial version 1.0, but is still intended to serve as an input to the proposed OGC Underground Infrastructure Pilot as well as similar implementations and deployments in realistic application scenarios. The present model is also suitable as input to begin development of a formal conceptual model standard." + "@value": "This document provides release notes for version 1.1 of the CDB Standard and related Best Practices." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75331,35 +75118,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-081" + "@value": "18-016r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "MUDDI v1.1 (Model for Underground Data Definition and Integration) Engineering Report" + "@value": "OGC CDB Version 1.1 Release Notes" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-059", + "@id": "http://www.opengis.net/def/docs/12-146", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-05-01" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Vretanos" + "@value": "Timo Thomas" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75369,27 +75156,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1171" + "@id": "https://portal.ogc.org/files/?artifact_id=51811" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "02-059" + "@value": "OWS-9 Web Feature Service Temporality Extension Engineering Report" }, { "@language": "en", - "@value": "Filter Encoding" + "@value": "12-146" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A filter is a construct used to describe constraints on properties of a feature class for the purpose of identifying a subset of feature instances to be operated upon in some way." + "@value": "This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 9 (OWS-9). This Engineering Report summarizes the OWS-9 activity regarding the extension of the Web Feature Service (WFS) and Filter Encoding (FE) standards to support dynamic feature data.\r\nSpecifically this document describes the result work performed in OWS 9 on the WFS Temporality Extension. The technical specification including background is discussed and defined in the OGC Discussion Paper 12-027r1. This document gives a summary about issues, lessons learned, recommendations, accomplishments and benefits for the Aviation Architecture. It also gives an outlook on future work items and change requests. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75400,35 +75187,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-059" + "@value": "12-146" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Filter Encoding" + "@value": "OGC® OWS-9 Web Feature Service Temporality Extension Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-055r2", + "@id": "http://www.opengis.net/def/docs/15-002r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-04-07" + "@value": "2015-04-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Pedro Gonçalves, Roger Brackin" + "@value": "Luis Bermudez" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75438,27 +75225,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=68826" + "@id": "http://docs.opengeospatial.org/wp/15-002r5/15-002r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS Context GeoJSON Encoding Standard" + "@value": "15-002r5" }, { "@language": "en", - "@value": "14-055r2" + "@value": "OGC Compliance Overview - Guide for Software Acquisition" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard describes the GeoJSON encoding of the OGC Web Services (OWS) Context conceptual model. This standard defines how to encode an OWS context document that 1.) can be extended to allow a context referencing a fully configured service set, and 2.) can be defined and consistently interpreted by clients.\r\nThe OWS Context Document standard (OWS Context) was created to allow a set of configured information resources to be passed between applications primarily as a collection of services (but also potentially in-line content). The objective is to support use cases such as the distribution of search results, the exchange of a set of resources in a Common Operating Picture (COP), or delivery of a set of configured processing services to allow the processing to be reproduced on different processing nodes.\r\nThe goal for OWS Context is to replace previous OGC standards and best practices that provide similar capability. Web Map Context (WMC) has been reasonably successful but is limited to working with only Web Map Service (WMS) instances. Other work on the Location Organizer Folder1 (LOF) was also taken into consideration. The concept of OWS Context and the first prototype document was produced as part of OWS Testbed 7 and documented in [OGC10-035r1], Information Sharing Engineering Report.\r\nA principal goal of the OWS Context SWG was to develop encodings that would appeal for use in mass market applications yet also provide facilities for more advanced uses. OWS-7 originally considered the application of existing encoding standards for OWS Context. The OGC Standards Working Group (SWG) has concluded that this standard can have multiple encoding formats and that each encoding format will be described in a separate OGC Extension to the Core model.\r\n" + "@value": "The Open Geospatial Consortium (OGC®) provides international standards that are implemented worldwide in thousands of applications that use location information. To reduce the risk of applications not implementing a standard correctly, the OGC provides a compliance process for testing and certifying implementations. OGC certification provides substantial evidence that an implementation that is claimed to have implemented an OGC standard will interoperate as specified and in the same manner as other compliant implementations, regardless of who developed them. This white paper provides guidance regarding language to specify requirements for OGC compliant and implementing products in software acquisition (procurement) documents." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75469,35 +75256,40 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-055r2" + "@value": "15-002r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC OWS Context GeoJSON Encoding Standard" + "@value": "OGC Compliance Overview - Guide for Software Acquisition" + } + ], + "http://www.w3.org/ns/dcat#landingPage": [ + { + "@id": "http://docs.opengeospatial.org/wp/15-002r5/15-002r5.html" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-024r4", + "@id": "http://www.opengis.net/def/docs/04-052", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-09-08" + "@value": "2004-09-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "CS Smyth" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75507,27 +75299,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=25487" + "@id": "https://portal.ogc.org/files/?artifact_id=6660" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-024r4" + "@value": "04-052" }, { "@language": "en", - "@value": "Location Services: Tracking Service Interface Standard" + "@value": "OWS1.2 Image Handling Requirements" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS Tracking Service Interface Standard supports a very simple functionality allowing a collection of movable objects to be tracked as they move and change orientation. The standard addresses the absolute minimum in functionality in order to address the need for a simple, robust, and easy-to-implement open standard for geospatial tracking." + "@value": "This document was developed as part of the Image Handling Thread of the OGC Web Services Initiative Phase 1 Thread Set 2 (OWS 1.2). This document specified the requirements for the image handling functions to be supported by draft specifications prepared under that thread. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75538,35 +75330,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-024r4" + "@value": "04-052" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Location Services (OpenLS): Tracking Service Interface Standard" + "@value": "OWS1.2 Image Handling Requirements" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-010r7", + "@id": "http://www.opengis.net/def/docs/12-027r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-08-13" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Lott" + "@value": "Timo Thomas" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75576,27 +75368,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/18-010r7/18-010r7.html" + "@id": "https://portal.ogc.org/files/?artifact_id=51815" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Geographic information — Well-known text representation of coordinate reference systems" + "@value": "12-027r2" }, { "@language": "en", - "@value": "18-010r7" + "@value": "OGC Web Feature Service (WFS) Temporality Extension " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Standard defines the structure and content of well-known text strings describing coordinate reference systems (CRSs) and coordinate operations between coordinate reference systems. It does not prescribe how implementations should read or write these strings.\r\n\r\nThis Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2019. It extends the WKT in OGC document 12-063r5 (ISO 19162) which was based on ISO 19111:2007 and ISO 19111-2:2009. That version consolidated several disparate versions of earlier WKT (so-called WKT1) and added the description of coordinate operations.\r\n\r\nThis jointly developed draft has been submitted by ISO TC211 for circulation as a Draft International Standard (DIS). This version incorporates comments made during the ISO TC211 New Work Item Proposal acceptance ballot." + "@value": "This OGC Discussion Paper (DP) provides a proposal for a temporality extension for the WFS 2.0 and FES 2.0 standard. It is based on the work of and experiences made in several OWS test beds, in particular OWS-7 and OWS-8, Aviation threads and discussions at the 2011 OGC TC meeting in Brussels, Belgium. This DP partially replaces and advances the document OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0 [4]." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75607,35 +75399,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-010r7" + "@value": "12-027r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Geographic information — Well-known text representation of coordinate reference systems" + "@value": "OGC Web Feature Service (WFS) Temporality Extension " } ] }, { - "@id": "http://www.opengis.net/def/docs/11-145", + "@id": "http://www.opengis.net/def/docs/07-018r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-05-20" + "@value": "2008-01-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "Philippe M" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75645,27 +75437,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=46388" + "@id": "https://portal.ogc.org/files/?artifact_id=25199" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-145" + "@value": "07-018r2" }, { "@language": "en", - "@value": "Cyberarchitecture for Geosciences White Paper" + "@value": "Sensor Planning Service Application Profile for EO Sensors" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/techpaper" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The National Science Foundation (NSF) is developing EarthCube” - Towards a National Data Infrastructure for Earth System Science . In a new partnership between GEO and the NSF Office of Cyberinfrastructure, NSF seeks transformative concepts and approaches to create a sustained, integrated data management infrastructure spanning the Geosciences. Meeting the challenges in geoscience research requires innovation and paradigm shifts in cyberinfrastructure. Information technology must advance to meet the emerging approaches to science. A cyber-architecture identifies repeatable patterns, reusable components, and open standards that provide starting point for innovative developments.\r\nThis white paper was written by Open Geospatial Consortium (OGC) members and associates to contribute to development of the NSF EarthCube. This document does not represent an official position of the OGC. However, the discussions in this document could very well lead to NSF developments and subsequent OGC documents. Recipients of this document are invited to reply to the authors’ with notification of any relevant patent rights of which they are aware and to provide supporting documentation.\r\n" + "@value": "The SPS configuration proposed in this profile is intended to support the programming process of Earth Observation (EO) sensors system. This profile describes a consistent SPS configuration that can be supported by many satellite data providers, most of whom have existing facilities for the management of these programming requests." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75676,35 +75468,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-145" + "@value": "07-018r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Cyberarchitecture for Geosciences White Paper" + "@value": "OpenGIS Sensor Planning Service Application Profile for EO Sensors" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-007r1", + "@id": "http://www.opengis.net/def/docs/06-095", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-01-28" + "@value": "2007-01-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Ingo Simonis, Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75714,27 +75506,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/17-007r1/17-007r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=18776" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-007r1" + "@value": "Web Notification Service" }, { "@language": "en", - "@value": "Web Services Security" + "@value": "06-095" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard applies to a deployed OGC Web Service instance for which the protocol scheme of all operation endpoint URLs, exposed in the Capabilities document, is ‘https’ as defined in RFC 7230, section 2.7.2.\r\n\r\nA security-annotated Capabilities document is one which uses the element(s) to express the existence of security controls on the operation of the service instance or support for a particular security feature. Applying the tests as defined in the Annexes can validate compliance for a service, the client and the OGC management process. Basically, a service can be described by a Capabilities document that includes security annotations as defined in this standard. A client loading these Capabilities and parse for the element(s) can determine the security controls implemented for each operation of the service instance. The string value of this element’s name attribute contains the identifier of the implemented requirements class.\r\n\r\nHow the client obtains the security-annotated capabilities is out of scope for this standard.\r\n\r\nThis standard defines one common abstract Requirements Class and three Capabilities document structure specific Requirements Classes. The structure specific classes address how the requirements are implemented for WMS 1.1.1, WMS 1.3 and OWS Common based service Capabilities documents.\r\n\r\n" + "@value": " A service by which a client may conduct asynchronous dialogues (message interchanges) with one or more other services. This service is useful when many collaborating services are required to satisfy a client request, and/or when significant delays are involved is satisfying the request. This service was defined under OWS 1.2 in support of SPS operations. WNS has broad applicability in many such multi-service applications. It is now used in several SWE scenarios." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75745,35 +75537,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-007r1" + "@value": "06-095" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Services Security" + "@value": "Web Notification Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-135", + "@id": "http://www.opengis.net/def/docs/06-107r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-03-28" + "@value": "2007-05-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Alexandre Robin, Philippe Mérigot" + "@value": "Cristian Opincaru" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75783,27 +75575,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40185" + "@id": "https://portal.ogc.org/files/?artifact_id=20859" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-135" + "@value": "06-107r1" }, { "@language": "en", - "@value": "Earth Observation Satellite Tasking Extension for SPS 2.0" + "@value": "Trusted Geo Services IPR" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The SPS 2.0 Earth Observation Satellite Tasking Extension Standard specifies extensions to the OGC Sensor Planning Service (SPS) 2.0 Interface Standard. The SPS configuration proposed in this extension is intended to support the programming process of Earth Observation (EO) sensor systems. This standard describes a consistent SPS configuration that can be supported by many satellite data providers, most of whom have existing facilities for the management of these programming requests. The resulting extended web service interface can be used for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or canceling such a request, and for requesting information on means of obtaining the data collected by the requested task." + "@value": "The OGC Trusted Geo Services Interoperability Program Report (IPR) provides guidance for the exchange of trusted messages between OGC Web Services and clients for these services. It describes a trust model based on the exchange and brokering of security tokens, as proposed by the OASIS WS-Trust specification [http://docs.oasis-open.org/ws-sx/ws-trust/200512]. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75814,35 +75606,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-135" + "@value": "06-107r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Sensor Planning Service Interface Standard 2.0 Earth Observation Satellite Tasking ExtensionOGC® Sensor Planning Service" + "@value": "Trusted Geo Services IPR" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-060r2", + "@id": "http://www.opengis.net/def/docs/14-013r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-07-05" + "@value": "2014-05-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann " + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75852,27 +75644,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/as/21-060r2/21-060r2.pdf" + "@id": "https://portal.ogc.org/files/?artifact_id=58892" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-060r2" + "@value": "Testbed-10 Service Integration Engineering Report" }, { "@language": "en", - "@value": "OGC Abstract Specification Topic 6: Schema for Coverage Geometry and Functions – Part 3: Processing Fundamentals" + "@value": "14-013r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines, at a high, implementation-independent level, operations on coverages - i.e., digital representations of space-time varying geographic phenomena - as defined in ISO 19123-1. Specifically, regular and irregular grid coverages are addressed. Future versions will additionally support further axis types as well as further coverage types from ISO19123-1, such as point clouds and meshes in particular. While the core functionality is expected to be generic and applicable for any coverage, there may be special functionality for particular coverage types." + "@value": "This document specifies technical changes to the OGC web service architecture baseline to support better integration among the services. Although integration may be achieve in a number of ways and using a number of other technologies, the goal of this document is to achieve this integration within the current OGC service framework in order to leverage existing investments in OGC web services infrastructure." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75883,35 +75675,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-060r2" + "@value": "14-013r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 6.3 - Schema for Coverage Geometry and Functions – Part 3: Processing Fundamentals" + "@value": "OGC® Testbed-10 Service Integration Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-100r1", + "@id": "http://www.opengis.net/def/docs/21-032", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-12-09" + "@value": "2022-01-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon J D Cox, Peter Taylor " + "@value": "Giovanni Giacco, Mauro Manente, Pedro Gonçalves, Martin Desruisseaux, Even Rouault" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75921,27 +75713,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64910" + "@id": "https://docs.ogc.org/per/21-032.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Observations and Measurements – JSON implementation" + "@value": "21-032" }, { "@language": "en", - "@value": "15-100r1" + "@value": "OGC Testbed 17: COG/Zarr Evaluation Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion Paper specifies a potential OGC Candidate Standard for a JSON implementation of the OGC and ISO Observations and Measurements (O&M) conceptual model (OGC Observations and Measurements v2.0 also published as ISO/DIS 19156). This encoding is expected to be useful in RESTful implementations of observation services. \r\nMore specifically, this Discussion Paper defines JSON schemas for observations, and for features involved in sampling when making observations. These provide document models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities.\r\n" + "@value": "The subject of this Engineering Report (ER) is the evaluation of Cloud Optimized GeoTIFF (COG) and Zarr data container implementations. The ER aims to:\r\n\r\n Describe the use cases adopted for the evaluation (with existing implementation and with Testbed-17 implementation);\r\n Identify the opportunity of proposing that COG and Zarr become OGC standards;\r\n Describe all components developed during the Testbed; and\r\n Provide an executive summary and a description of recommended future work items." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -75952,35 +75744,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-100r1" + "@value": "21-032" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Observations and Measurements – JSON implementation" + "@value": "OGC Testbed 17: COG/Zarr Evaluation Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-155", + "@id": "http://www.opengis.net/def/docs/16-021r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-06-06" + "@value": "2017-05-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Tim Wilson, Renato Primavera, Panagiotis (Peter) A. Vretanos" + "@value": "Benjamin Pross" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -75990,27 +75782,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20430" + "@id": "https://docs.ogc.org/per/16-021r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-155" + "@value": "16-021r1" }, { "@language": "en", - "@value": "OWS-4 CSW ebRIM Modelling Guidelines IPR" + "@value": "Testbed-12 Low Bandwidth & Generalization Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OWS-4 CSW ebRIM Modelling Guidelines Interoperability Program Report (IPR) provides guidance for creating a standard methodology for mapping geospatial domain information models to ebRIM [www.oasis-open.org/committees/regrep/documents/2.0/specs/ebrim.pdf]. It also presents the results of mapping specific Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] and Feature Catalog domain models to ebRIM for use with OpenGIS Catalog Service Standard [http://www.opengeospatial.org/standards/cat] implementations in the OWS-4 Initiative [http://www.opengeospatial.org/projects/initiatives/ows-4]." + "@value": "For delivering of data that is offered by OGC services over (very) low bandwidth, two options may be considered: On the one hand, the geospatial features remain the same, but compression techniques are used to reduce the size of the data that needs to be transferred. On the other hand, generalization techniques may be used by reducing the details of geometries and/or attributes in order to reduce the amount of data. The aim of this ER is to summarize the results of implementing sample services using compression techniques for DGIWG WFS (U002) and providing generalization processes using WPS (U003). The ER compares the results of the different approaches and infers recommendations and best practices for supporting data delivery of standard data and complex 3D data from OGC services over low and very low bandwidth." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76021,35 +75813,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-155" + "@value": "16-021r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-4 CSW ebRIM Modelling Guidelines IPR" + "@value": "Testbed-12 Low Bandwidth & Generalization Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-046r2", + "@id": "http://www.opengis.net/def/docs/10-157r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-01-18" + "@value": "2016-06-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Eugene G. Yu, Liping Di, Ranjay Shrestha" + "@value": "Jerome Gasperi, Frédéric Houbie, Andrew Woolf, Steven Smolders " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -76059,27 +75851,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64174" + "@id": "https://docs.ogc.org/is/10-157r4/10-157r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-11 High Resolution Flood Information Scenario Engineering Report" + "@value": "Earth Observation Metadata profile of Observations & Measurements" }, { "@language": "en", - "@value": "15-046r2" + "@value": "10-157r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report describes the high-resolution flood information scenario carried out under the Urban Climate Resilience Thread of the Testbed 11 Initiative. The scenario was developed for two areas of interest: the San Francisco Bay Area and in Mozambique. The scenarios for these two locations demonstrate the interoperation and capabilities of open geospatial standards in supporting data and processing services. The prototype High Resolution Flood Information System addresses access and control of simulation models and high-resolution data in an open, worldwide, collaborative Web environment. The scenarios were designed to help testbed participants examine the feasibility and capability of using existing OGC geospatial Web Service standards in supporting the on-demand, dynamic serving of flood information from models with forecasting capacity. Change requests to OGC standards have also been identified through the Testbed activity." + "@value": "This OGC Implementation Standard defines a profile of Observations and Measurements (ISO 19156:2010 and OGC 10-025r1) for describing Earth Observation products (EO products).\r\nThis profile is intended to provide a standard schema for encoding Earth Observation product metadata to support the description and cataloguing of products from sensors aboard EO satellites. \r\nThe metadata being defined in this document is applicable in a number of places where EO product metadata is needed.\r\n1.\tIn the EO Product Extension Package for ebRIM (OGC 10-189). This extension package defines how to catalog Earth Observation product metadata described by this document. Using this metadata model and the Catalogue Service defined in OGC 10-189, client applications can provide the functionality to discover EO Products. Providing an efficient encoding for EO Product metadata cataloguing and discovery is the prime purpose of this specification.\r\n2.\tIn the EO Application Profile of WMS (OGC 07-063r1). The GetFeatureInfo operation on the outline (footprint layer) should return metadata following the Earth Observation Metadata profile of Observation and Measurements.\r\n3.\tIn a coverage downloaded via an EO WCS AP (OGC 10-140). In WCS 2.0 (OGC 10-084), the GetCoverage and DescribeCoverage response contains the metadata element intended to store metadata information about the coverage. The Earth Observation Application profile of WCS (OGC 10-140) specifies that the metadata format preferred for Earth Observation is defined by this document.\r\n4.\tPotentially enclosed within an actual product to describe georeferencing information as for instance within the JPEG2000 format using GMLJP2. GMLJP2 defines how to store GML coverage metadata inside a JP2 file. \r\nEarth Observation data products are generally managed within logical collections that are usually structured to contain data items derived from sensors onboard a satellite or series of satellites. The key characteristics differentiating products within the collections are date of acquisition, location as well as characteristics depending on the type of sensor, For example, key characteristics for optical imagery are the possible presence of cloud, haze, smokes or other atmospheric or on ground phenomena obscuring the image. \r\nThe common metadata used to distinguish EO products types are presented in this document for generic and thematic EO products (i.e optical, radar, atmospheric, altimetry, limb-looking and synthesis and systematic products). From these metadata the encodings are derived according to standard schemas. In addition, this document describes the mechanism used to extend these schemas to specific missions and for specific purposes such as long term data preservation. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76090,35 +75882,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-046r2" + "@value": "10-157r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed-11 High Resolution Flood Information Scenario Engineering Report" + "@value": "OGC® Earth Observation Metadata profile of Observations & Measurements" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-011r3", + "@id": "http://www.opengis.net/def/docs/07-068r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-02-23" + "@value": "2009-01-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -76128,27 +75920,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=72719" + "@id": "https://portal.ogc.org/files/?artifact_id=28506" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-011r3" + "@value": "Web Coverage Service (WCS) - Transaction operation extension" }, { "@language": "en", - "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance" + "@value": "07-068r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames. \r\nIn previous versions of the CDB standard, this CDB volume was Appendix K in CDB Version 3.2 as submitted to the OGC.\r\n" + "@value": "This extension of the WCS standard specifies an additional Transaction operation that may optionally be implemented by WCS servers. This Transaction operation allows clients to add, modify, and delete grid coverages that are available from a WCS server. The Transaction operation request references or includes the new or modified coverage data, including all needed coverage metadata. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76159,35 +75951,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-011r3" + "@value": "07-068r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 8: CDB Spatial and Coordinate Reference Systems Guidance" + "@value": "Web Coverage Service (WCS) - Transaction operation extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-040", + "@id": "http://www.opengis.net/def/docs/02-023r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-26" + "@value": "2003-01-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann, Jinsongdi Yu" + "@value": "Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -76197,27 +75989,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=54503" + "@id": "https://portal.ogc.org/files/?artifact_id=7174" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-040" + "@value": "Geography Markup Language (GML) Encoding Specification" }, { "@language": "en", - "@value": "Web Coverage Service Interface Standard - Range Subsetting Extension" + "@value": "02-023r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isx" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request which allow extraction of specific fields, according to the range type specification, from the range set of a coverage during server-side processing of a coverage in a GetCover-age request." + "@value": "The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76228,30 +76020,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-040" + "@value": "02-023r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Coverage Service Interface Standard - Range Subsetting Extension" + "@value": "OpenGIS Geography Markup Language (GML) Encoding Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/13-080r3", + "@id": "http://www.opengis.net/def/docs/16-033r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-10-25" + "@value": "2017-04-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Frank Klucznik, Matthew Weber, Robin Houtmeyers, Roger Brackin" + "@value": "Ranjay Shrestha, Liping Di, Eugene G. Yu" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -76266,17 +76058,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55252" + "@id": "https://docs.ogc.org/per/16-033r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "13-080r3" + "@value": "16-033r1" }, { "@language": "en", - "@value": "Military Operations Geospatial Interoperability Experiment (MOGIE)" + "@value": "Testbed-12 WCS Profile Update Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -76286,7 +76078,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "experiment demonstrated that GML content can be embedded in NIEM conformant XML and be exploited by commercial and open source tools without loss of precision (e.g., right number of bits) or accuracy (e.g., physical location on a map). Embedding GML in NIEM conformant XML was accomplished in MOGIE using the NIEM adapter." + "@value": "This engineering report capture the work to extend the existing Web Coverage Service (WCS) profiles, particularly the Earth Observation Application Profile (EO-WCS [OGC 10-140r1]) to support multi-dimensional subsetting of 3D space and 1D time. The updated EO-WCS (EO-WCS1.1 [OGC 10-140r2]) have removed the requirement for the 2D coverages so that it can explicitly allow coverages with more dimensions as long as they have geographic footprint. Furthermore it also clarified the use of rangeType when non-NCNAME characters are present in a band identifier. The example of GetCapabilites, DescribeEOCoverageSet, and _GetCoverage request in the updated EO-WCS1.1 is shown with use case on fire emission data in San Francisco.\r\n\r\nFollowing the recommendation for EO-WCS to fully embrace the N-D, multi-dimensional, concept of Coverages as a function of time and other coordinates alongside the geospatial ones, the proposed recommendations/changes in the extension for WCS DescribeCoverage, EO-WCS DescribeEOCoverageSet, and WCS GetCoverage are discussed with use case example using National Centers for Environmental Prediction (NCEP) Global 0.25 deg wind data. Based on the mutual recommendation from the US National Aeronautics and Space Administration (NASA) and Baart et. al (2012), Network Common Data Form (NetCDF) was the output format due to presence of its libraries in multiple languages to lower the burden in changing on developers of WCS-compliant servers and clients.\r\n\r\nFor the extension of the WCS DescribeCoverage, it is recommended that CIS1.1 should be considered adopting a scheme for transmitting coordinates similar to the _cis:rangeSet where data are referred to as an attached Multipurpose Internet Mail Extensions (MIME) part. Time, as much as possible, be treated as just another coordinates dimension so that it could be access with the same tools used for other coordinate dimensions. To tackle the issue on order of coordinate dimensions, it is recommended to add implementation note to the EO-WCS specifications so that implementers are aware of the mismatches between dataset coordinate reference systems (CRSs) and actual axis order.\r\n\r\nFor the extension of EO_WCS DescribeEOCoverageSet, the issue on missing range of results API needed to be resolved by adding a request mechanism for requesting a range of matching results. It is also recommended that DescribeEOCoverageSet activity might be of more use to the client if the client need to supply only the subset conditions, and not a list of identifiers.\r\n\r\nFor the extension of WCS GetCoverage, it was discovered that for the GetCoverage operation for higher dimensioned datasets, existing WCS-2.0 request interface provided adequate syntax for subsetting higher dimensional data. Scaling (re-gridding) operation appears to be a natural fit for the EO-WCS subsetting, specifically SCALEEXTENT activity, however simpler explanation might be needed to fully understand its use as it appears other scaling and subsetting commands may be more than adequate for the desired outcomes. Additionally allowing SlicePoint subsetting is also recommended.\r\n\r\nAfter performing the testing in the client side, there were few potential recommendations for improvements. More information on whether the coverage is 2D or 3D form the GetCapalilites request might be helpful to client so it can limit the number of DescribeCoverage requests to construct a list of available coverage on the server. Furthermore additional metadata information for displaying meaningful native gird coordinates is also recommended for clarification. Finally automatic detection of lat/lon axes along with clear treatment of XY and lat/lon axes ordering would be an improvement in the existing operations." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76297,84 +76089,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "13-080r3" + "@value": "16-033r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Military Operations Geospatial Interoperability Experiment (MOGIE)" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/profile/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type Approved Specification Profile" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Documents of type Approved Specification Profile" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/05-095r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-096r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-099r2" - }, - { - "@id": "http://www.opengis.net/def/docs/13-082r2" - }, - { - "@id": "http://www.opengis.net/def/docs/05-094r1" - }, - { - "@id": "http://www.opengis.net/def/docs/10-140r1" - }, - { - "@id": "http://www.opengis.net/def/docs/10-100r3" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Documents of type Approved Specification Profile" + "@value": "Testbed-12 WCS Profile Update Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-101r2", + "@id": "http://www.opengis.net/def/docs/08-073r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-08-16" + "@value": "2008-09-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Scarponcini" + "@value": "Jessica Cook, Raj Singh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -76384,27 +76127,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=75118" + "@id": "https://portal.ogc.org/files/?artifact_id=29426" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-101r2" + "@value": "Summary of the OGC Web Services, Phase 5 (OWS-5) Interoperability Testbed" }, { "@language": "en", - "@value": "InfraGML 1.0: Part 1 – LandInfra Land Features - Encoding Standard" + "@value": "08-073r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 1 addresses the LandFeature Requirements Class from LandInfra." + "@value": "The OGC Web Services, Phase 5 (OWS-5) Testbed was an initiative of the OGC Interoperability Program (IP). The primary focus of an IP activity is to collaboratively extend and demonstrate OGC‘s baseline for geospatial interoperability." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76415,35 +76158,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-101r2" + "@value": "08-073r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC InfraGML 1.0: Part 1 – LandInfra Land Features - Encoding Standard" + "@value": "Summary of the OGC Web Services, Phase 5 (OWS-5) Interoperability Testbed" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-040r1", + "@id": "http://www.opengis.net/def/docs/07-122r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-30" + "@value": "2007-11-12" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Aleksandar Balaban" + "@value": "Mike Botts, Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -76453,27 +76196,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-040r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=24757" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-040r1" + "@value": "SensorML Encoding Standard v 1.0 Schema Corregendum 1" }, { "@language": "en", - "@value": "Testbed-12 Aviation Security Engineering Report" + "@value": "07-122r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The information security is the state of being protected against the unauthorized use of information and services, or the measures taken to achieve that. This report has ben created as part of OGC Testbed 12 aviation thread and on behalf of sponsors from FAA. It gives the readers an overview into the topic of cyber security in the aviation domain, especially in conjunction with OGC compatible web services, which are today de facto standard for aeronautical traffic System Wide Information Management." + "@value": "Changes to the 1.0 schemas" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76484,35 +76227,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-040r1" + "@value": "07-122r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Aviation Security Engineering Report" + "@value": "OpenGIS SensorML Encoding Standard v 1.0 Schema Corregendum 1" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-125r1", + "@id": "http://www.opengis.net/def/docs/12-160r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-02-04" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Tim Wilson, David Burggraf" + "@value": "Jon Blower, Xiaoyu Yang, Joan Masó and Simon Thum" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -76522,27 +76265,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=30203" + "@id": "https://portal.ogc.org/files/?artifact_id=52884" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-125r1" + "@value": "OWS 9 Data Quality and Web Mapping Engineering Report" }, { "@language": "en", - "@value": "KML Standard Development Best Practices" + "@value": "12-160r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Best Practices Document provides guidelines for developing the OGC KML standard in a manner that best serves and supports the KML application developer and user communities. It applies to the extension of KML by application developers and the subsequent enhancement of the KML standard by the OGC." + "@value": "This Engineering Report specifies conventions for conveying information about data\r\nquality through the OGC Web Map Service Standard (known hereafter as the “WMS-Q\r\nconventions”), OGC Web Map Tile Service Standard (known hereafter as the “WMTS-Q\r\nconventions”), OGC KML (known hereafter as the “KML-Q conventions”) and OGC\r\nAugmented Reality Markup Language." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76553,30 +76296,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-125r1" + "@value": "12-160r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® KML Standard Development Best Practices" + "@value": "OGC® OWS 9 Data Quality and Web Mapping Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-010r2", + "@id": "http://www.opengis.net/def/docs/21-041r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-05-06" + "@value": "2022-01-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Taehoon Kim, Kyoung-Sook Kim, Jiyeong Lee, Ki-Joune Li" + "@value": "Sam Meek" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -76591,17 +76334,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/21-010r2.html" + "@id": "https://docs.ogc.org/dp/21-041r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-010r2" + "@value": "OGC Conceptual Modeling Discussion Paper" }, { "@language": "en", - "@value": "Extensions of IndoorGML 1.1 - Indoor Affordance Spaces" + "@value": "21-041r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -76611,7 +76354,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC IndoorGML standard provides a fundamental data model for representing indoor spaces as spatial, topological, and semantic features. The IndoorGML core module allows applications to extend the model with their semantic considerations. For example, the IndoorGML navigation module classifies the basic class of indoor spaces, cell spaces, into navigable or non-navigable spaces. Navigable spaces, in which users can move freely, are specified in two subclasses: transfer spaces (e.g. doors, entrances, hallways) and general spaces (e.g. rooms, terraces, lobbies), based on indoor navigation requirements. This discussion paper proposes an extension to the OGC IndoorGML core module to support new types of location-based services, such as autonomous driving robots, personal experience augmentation with augmented reality (AR) / virtual reality (VR), and facilities management, to understand activities and needs in indoor spaces. The proposed extension consists of three new indoor spaces to represent affordance spaces with structural, functional, and sensory characteristics by leveraging the multi-layered space representation of IndoorGML." + "@value": "Historically, conceptual modeling was utilized sporadically within the Open Geospatial Consortium (OGC). Models were used in OGC standards both informatively and normatively to describe the structure of the information within a standard for a particular domain. As independent standards-development organizations, OGC and alliance partners such as ISO / TC211 did not always develop common models. There are several examples of conceptual models in OGC’s Abstract Specifications, many of which have become ISO / TC211 standards since their publication. Outside of Abstract Specifications, there are fewer examples of conceptual models in Implementation Standards. Logical Models and Physical Models tend to be specified more in Implementation Standards.\r\n\r\nThe need for conceptual models in Implementation Standards has become apparent since the OGC is moving towards resource based architecture through the development of the OGC Application Programming Interface (API) suite of standards. In the previous ways of working, standards and encodings mapped 1:1, as many OGC standards were based on the Extensible Markup Language (XML) and a standard described a particular set of XML documents to support a domain. The move to OGC API has led towards a separation of an information model represented in a standard from encodings, which is the way that the information models are expressed in a given technology. In other words, the move to OGC API has led to a clearer separation of the logical model from the physical model.\r\n\r\nThe utilization of conceptual modeling practices may be employed to manage, track, or govern the use of concepts and terms within different standards. The OGC should adopt conceptual modeling where suitable with a new group to support the working groups with the modeling effort that may otherwise have not been completed because a lack of expertise or value recognition. Taking the concept one step further, Model Driven Architecture (MDA) is a transformation process to create a platform specific model, or implementation from a logical, platform-independent model. This process could be implemented to enable quick production of standards into different target technologies or for the creation of new standards entirely. This paper does not suggest making MDA and associated mandatory for future standards generation." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76622,35 +76365,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-010r2" + "@value": "21-041r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Extensions of IndoorGML 1.1 - Indoor Affordance Spaces" + "@value": "OGC Conceptual Modeling Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-010", + "@id": "http://www.opengis.net/def/docs/19-034r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-09-13" + "@value": "2023-03-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas H. Kolbe, Tatjana Kutzner, Carl Stephen Smyth, Claus Nagel, Carsten Roensdorf, Charles Heazel" + "@value": "Carl Reed, Tamrat Belayneh" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -76660,27 +76403,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/20-010/20-010.html" + "@id": "https://docs.ogc.org/cs/17-014r7/19-034r1.pdf" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard" + "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification Version 1.1 Release Notes " }, { "@language": "en", - "@value": "20-010" + "@value": "19-034r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Standard defines the open CityGML Conceptual Model for the storage and exchange of virtual 3D city models. The CityGML Conceptual Model is defined by a Unified Modeling Language (UML) object model. This UML model builds on the ISO Technical Committee 211 (ISO/TC 211) conceptual model standards for spatial and temporal data. Building on the ISO foundation assures that the man-made features described in the city models share the same spatiotemporal universe as the surrounding countryside within which they reside.\r\n\r\nA key goal for the development of the CityGML Conceptual Model is to provide a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields.\r\n\r\nThe class models described in this standard are also available at https://github.com/opengeospatial/CityGML3-Workspace/tree/1.0/UML/CityGML" + "@value": "This document provides the set of revision notes for OGC I3S Community Standard [OGC 17-014r5] and does not modify that standard.\r\nThis document provides the details of edits, deficiency corrections, and enhancements of the above-referenced standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76691,35 +76434,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-010" + "@value": "19-034r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard" + "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification Version 1.1 Release Notes " } ] }, { - "@id": "http://www.opengis.net/def/docs/16-008", + "@id": "http://www.opengis.net/def/docs/06-113", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-01-31" + "@value": "2006-07-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "GeoSciML Modeling Team" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/pc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -76729,27 +76472,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/16-008/16-008.html" + "@id": "https://portal.ogc.org/files/?artifact_id=16572" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-008" + "@value": "06-113" }, { "@language": "en", - "@value": "Geoscience Markup Language 4.1" + "@value": "GML 3.1.1 common CRSs profile Corrigendum" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/pc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "GeoSciML is a model of geological features commonly described and portrayed in geological maps, cross sections, geological reports and databases. The model was developed by the IUGS CGI (Commission for the Management and Application of Geoscience Information) and version 4.1 is the first version officially submitted as an OGC standard. This specification describes a logical model and GML/XML encoding rules for the exchange of geological map data, geological time scales, boreholes, and metadata for laboratory analyses. It includes a Lite model, used for simple map-based applications; a basic model, aligned on INSPIRE, for basic data exchange; and an extended model to address more complex scenarios. \r\n\r\nThe specification also provides patterns, profiles (most notably of Observations and Measurements - ISO19156), and best practices to deal with common geoscience use cases. \r\n\r\n" + "@value": "This document is a corrigendum for OGC Document 05-095r1, titled GML 3.1.1 common CRSs profile. This corrigendum is based on change request OGC 06-041." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76760,35 +76503,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-008" + "@value": "06-113" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Geoscience Markup Language 4.1 (GeoSciML)" + "@value": "GML 3.1.1 common CRSs profile Corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-036", + "@id": "http://www.opengis.net/def/docs/05-050", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-13" + "@value": "2006-05-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Emeric Beaufays, C.J. Stanbridge, Rob Smith" + "@value": "Craig Bruce" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -76798,27 +76541,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-036.html" + "@id": "https://portal.ogc.org/files/?artifact_id=12983" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Full Motion Video to Moving Features Engineering Report" + "@value": "05-050" }, { "@language": "en", - "@value": "20-036" + "@value": "GML Performance Investigations by CubeWerx" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed-16 Engineering Report (ER) evaluates the suitability of existing OGC standards for the generation of Moving Features from Full Motion Video (FMV) that has an embedded stream of detected moving objects.\r\n\r\nThis ER presents several proof of concept applications that accept FMVs, with multiple encoded Video Moving Target Indicators (VMTI), and combines the VMTIs into separate tracks that are then encoded to OGC Moving Features.\r\n\r\nIn addition, the ER explores the generation of records encoded according to OGC Sensor Model Language (SensorML) 2.0 standard describing the collection platform and relevant telemetry information from the key-value stream content encoded according to the MISB 0601 and 0903 specifications of the Motion Imagery Standards Board (MISB)." + "@value": "This report proposes and executes methods to evaluate the performance of the use of the Geography Markup Language (GML) as encoded in various ways." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76829,30 +76572,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-036" + "@value": "05-050" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: Full Motion Video to Moving Features Engineering Report" + "@value": "GML Performance Investigations by CubeWerx" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-023", + "@id": "http://www.opengis.net/def/docs/18-032r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-30" + "@value": "2019-02-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Pedro Gonçalves" + "@value": "Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -76867,17 +76610,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-023.html" + "@id": "https://docs.ogc.org/per/18-032r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-13: EP Application Package Engineering Report" + "@value": "18-032r2" }, { "@language": "en", - "@value": "17-023" + "@value": "Application Schema-based Ontology Development Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -76887,7 +76630,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Application Package OGC Engineering Report (ER) defines a data model and serialization for Thematic Exploitation Platforms (TEP) Application Packages. A TEP refers to a computing platform that follows a given set of scenarios for users, data and ICT provision aggregated around an Earth Science thematic area. This ER is part of the Testbed-13 Earth Observation Clouds (EOC) effort to support the development by the European Space Agency (ESA) of the TEP by exercising envisioned workflows for data integration, processing, and analytics based on algorithms developed by users that are deployed in multiple clouds.\r\n\r\nThe wide usage of virtualization and the possibility to start virtual environments within Cloud services significantly simplifies the creation of environments and provisioning of resources. However, it still leaves a problem of portability between infrastructures. This ER identifies a strategy for packaging an application in a Cloud environment that will be able to run in a predictable manner in different computing production environments. The application packaging specifies the elements that will ensure:\r\n\r\nScientific reproducibility,\r\n\r\nDependencies identification and management,\r\n\r\nMaintainability from an operational perspective and avoid version pilling,\r\n\r\nPortability in different Cloud providers\r\n\r\nThe ER proposes the use of containers, defining everything required to make a piece of software run packaged into isolated containers. Unlike a Virtual Machine (VM), a container does not bundle a full Operating System (OS) - only libraries and settings required to make the software work are needed. This makes for efficient, lightweight, self-contained systems and guarantees that software will always run the same, regardless of where it’s deployed. A discussion on application deployment and execution is presented in the separate OGC Testbed-13 Application Deployment and Execution Service ER [1].\r\n\r\n" + "@value": "This report enhances the understanding of the relationships between application schemas based on the Unified Modeling Language (UML) and ontologies based on the Web Ontology Language (OWL). The work documented in this report provides and improves tools and principled techniques for the development of Resource Description Framework (RDF) based schemas from ISO 19109-conformant application schemas." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76898,35 +76641,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-023" + "@value": "18-032r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: EP Application Package Engineering Report" + "@value": "OGC Testbed-14: Application Schema-based Ontology Development Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-013", + "@id": "http://www.opengis.net/def/docs/07-062", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-05-27" + "@value": "2007-08-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Robert Thomas, Josh Lieberman" + "@value": "Gerhard Gr" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -76936,27 +76679,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-013.html" + "@id": "https://portal.ogc.org/files/?artifact_id=22120" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-013" + "@value": "07-062" }, { "@language": "en", - "@value": "Modernizing SDI: Enabling Data Interoperability for Regional Assessments and Cumulative Effects CDS" + "@value": "City Geography Markup Language" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report (ER) presents the results of a Concept Development Study (CDS) on Modernizing Spatial Data Infrastructure (SDI), sponsored by Natural Resources Canada, executed by the Open Geospatial Consortium (OGC). The focus of this study was to understand how to best support the modernization of SDI(s) by enabling increased data interoperability for Regional Assessments (RA) and Cumulative Effects (CE), to advance the understanding of stakeholder issues, and serve stakeholders’ needs in these contexts. The study was completed through stakeholder engagements including an open Request for Information (RFI) that gathered external international positions and opinions on the optimal setup and design of a modernized SDI. In addition, a stakeholder Modernizing SDI Workshop was also employed providing in depth information on requirements and issues related to stakeholders, architecture, data, and standards of current and future SDI.\r\n\r\nThe RFI and workshop also gathered information and provided insight on the current state of SDIs to better support governments, agencies, non-governmental organizations and citizens, unlocking the full societal and economic potential of the wealth of data at national, regional and/or local levels.\r\n\r\nThe ER presents an analysis of the RFI and Modernizing SDI Workshop responses and interactions, providing in-depth information on requirements and issues related to stakeholders, architecture, data, standards of current and possible future SDI modernization. All RFI and workshop responses will contribute to SDI modernization efforts moving forward and help to assess interoperability, availability and usability of geospatial Web services and tools across different types of spatial data uses. In addition, the report identifies gaps, and defines core components of a possible future SDI.\r\n\r\nThe outflow of this report may be used to help define reference use-cases and scenarios for possible future research and follow-on OGC Innovation Program activities." + "@value": "CityGML is designed as an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is implemented as an application schema of the Geography Markup Language 3 (GML3), the extendible international standard for spatial data exchange and encoding issued by the Open Geospatial Consortium (OGC) and the ISO TC211. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -76967,35 +76710,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-013" + "@value": "07-062" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Modernizing SDI: Enabling Data Interoperability for Regional Assessments and Cumulative Effects CDS" + "@value": "City Geography Markup Language" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-103r2", + "@id": "http://www.opengis.net/def/docs/12-159", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-08-16" + "@value": "2013-02-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Scarponcini" + "@value": "Matthes Rieke, Benjamin Pross" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -77005,27 +76748,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=75120" + "@id": "https://portal.ogc.org/files/?artifact_id=51818" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "InfraGML 1.0: Part 3 - Alignments - Encoding Standard" + "@value": "OWS-9 CCI Conflation with Provenance Engineering Report" }, { "@language": "en", - "@value": "16-103r2" + "@value": "12-159" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 3 addresses the Alignment Requirements Class from LandInfra." + "@value": "This OGC® Engineering Report describes the architecture of a WPS capable of conflating two datasets while capturing provenance information about the process. The report also provides information about defining and encoding conflation rules and about encoding provenance information. \r\nThis Engineering Report was created as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77036,35 +76779,66 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-103r2" + "@value": "12-159" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC InfraGML 1.0: Part 3 - Alignments - Encoding Standard" + "@value": "OWS-9 CCI Conflation with Provenance Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-070", + "@id": "http://www.opengis.net/def/doc-type/orm/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type OpenGIS Reference Model" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type OpenGIS Reference Model" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/08-062r7" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type OpenGIS Reference Model" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/19-088r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-08-19" + "@value": "2020-07-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Bill Lalonde" + "@value": "Gobe Hobona, Terry Idol" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -77074,27 +76848,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1188" + "@id": "https://docs.ogc.org/per/19-088r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Styled Layer Descriptor (SLD) Implementation Specification" + "@value": "Vector Tiles Pilot 2: Summary Engineering Report" }, { "@language": "en", - "@value": "02-070" + "@value": "19-088r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The SLD is an encoding for how the Web Map Server (WMS 1.0 & 1.1) specification can be extended to allow user-defined symbolization of feature data." + "@value": "This OGC Engineering Report (ER) provides a summary of the research and findings from Phase 2 of the OGC Vector Tiles Pilot (VTP2). The goal of VTP2 was to deliver a consistent, interoperable online/offline architecture for vector tiles based on feature and tile servers, as well as GeoPackage. All Application Programming Interface (API) implementations and service types deployed in the pilot were implemented to support the prototype vector tile metadata model and filtering language. These were two essential work items of VTP2. The feature and tile servers included implementations of the OGC API – Features standard and the draft OGC API – Tiles specification. The feature and tile servers provided support for a variety of Coordinate Reference Systems (CRS). This ER provides an overview of each of the components, their implementation decisions and the challenges faced.\r\n\r\nThe VTP2 participants intend to use the results of the work in VTP2 to inform the development of OGC APIs, GeoPackage, and web service standards to enable consistent use both online and offline, particularly in DDIL environments. Such consistent use of tiled feature data online and offline will improve interoperability and usability of geospatial applications. Therefore, the value of the VTP2 work to organizations is expected to be in the efficiencies and productivity that comes from greater interoperability and usability." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77105,35 +76879,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-070" + "@value": "19-088r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Styled Layer Descriptor (SLD) Implementation Specification" + "@value": "OGC Vector Tiles Pilot 2: Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-041r1", + "@id": "http://www.opengis.net/def/docs/07-172r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-30" + "@value": "2008-05-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Liping Di, Eugene G. Yu, Md Shahinoor Rahman, Ranjay Shrestha" + "@value": "Kristin Stock" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -77143,27 +76917,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-041r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=26730" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 WPS ISO Data Quality Service Profile Engineering Report" + "@value": "Feature Type Catalogue Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0" }, { "@language": "en", - "@value": "16-041r1" + "@value": "07-172r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Data Quality Engineering Report describes data quality handling requirements, challenges and solutions. One focus is on data quality in general that needs to be communicated from one service to another. In addition, it discusses WPS data quality solutions. The ultimate goal is for it to be nominated as a WPS ISO Data Quality Service Profile. ISO 19139 is used as the base to encode the data quality. WPS and workflows are used to streamline and standardize the process of data quality assurance and quality control. The main topics include: (1) generalized summary and description of the design and best practices for analyzing data quality of all feature data sources used in the Citizen Observatory WEB (COBWEB) project, (2) solutions and recommendations for enabling provenance of data quality transparent to end users when the data is processed through a WPS, (3) best practices and recommendations for designing and prototyping the WPS profile to support data quality service conformant to the NSG Metadata Framework, and (4) general solution for data quality fit for both raster-based imageries and vector-based features." + "@value": "This document describes a Feature Type Catalogue extension package for the OGC® ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 [OGC 05-025r3]. It defines the way an ISO 19110 [ISO 19110:2005] Feature Type Catalogue is included within a Registry, and provides an information model and stored queries for such an inclusion." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77174,35 +76948,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-041r1" + "@value": "07-172r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 WPS ISO Data Quality Service Profile Engineering Report" + "@value": "Feature Type Catalogue Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-071r3", + "@id": "http://www.opengis.net/def/docs/15-028", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-03-26" + "@value": "2015-08-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox, Chris Little" + "@value": "Daniel Balog" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -77212,27 +76986,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://www.w3.org/TR/2020/CR-owl-time-20200326/" + "@id": "https://portal.ogc.org/files/?artifact_id=63281" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Time Ontology in OWL" + "@value": "15-028" }, { "@language": "en", - "@value": "16-071r3" + "@value": "Testbed 11 Data Broker Specifications Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OWL-Time is an OWL-2 DL ontology of temporal concepts, for describing the temporal properties of resources in the world or described in Web pages. The ontology provides a vocabulary for expressing facts about topological (ordering) relations among instants and intervals, together with information about durations, and about temporal position including date-time information. Time positions and durations may be expressed using either the conventional (Gregorian) calendar and clock, or using another temporal reference system such as Unix-time, geologic time, or different calendars.\r\n\r\n" + "@value": "This document is a deliverable of the OGC Testbed 11 Interoperability initiative. The report’s contents cover the summary of the interoperability work regarding the Aviation Data Broker concept. This data broker concept enables the setup of cascading OGC Web Feature Server (WFS) servers to form a data source chain, in which one service is capable of providing information coming from one or more other services. The objectives of this document are to research the feasibility of this concept and to investigate a number of specific Data Broker responsibilities and use cases, such as provenance and lineage, conflation, caching, scalability and flexible management of data sources." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77243,30 +77017,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-071r3" + "@value": "15-028" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Time Ontology in OWL" + "@value": "OGC® Testbed 11 Data Broker Specifications Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/23-033", + "@id": "http://www.opengis.net/def/docs/14-006r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-04-26" + "@value": "2014-07-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Samantha Lavender, Trent Tinker" + "@value": "Daniel Balog" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -77281,17 +77055,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/23-033.html" + "@id": "https://portal.ogc.org/files/?artifact_id=59793" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "23-033" + "@value": "14-006r1" }, { "@language": "en", - "@value": "Testbed-19: Machine Learning Models Engineering Report" + "@value": "Testbed 10 Recommendations for Exchange of Terrain Data" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -77301,7 +77075,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Testbed 19 initiative explored six tasks including this task focused on Machine Learning: Transfer Learning for Geospatial Applications. \r\n\r\nThis OGC Testbed 19 Engineering Report (ER) documents work to develop the foundation for future standardization of Machine Learning models for transfer learning within geospatial, especially Earth Observation, applications. The ER reviews the findings of transfer learning experiments and makes recommendations about the next steps in terms of both the experiments conducted and broader implications for OGC." + "@value": "This document is a deliverable of the OGC Testbed 10 (Testbed-10). Its contents cover the summary of the work carried out regarding the recommendations for the exchange of terrain data.\r\nSuggested additions, changes, and comments on this draft report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document.\r\nThe changes made in this document version, relative to the previous version, are tracked by Microsoft Word, and can be viewed if desired. If you choose to submit suggested changes by editing this document, please first accept all the current changes, and then make your suggested changes with change tracking on.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77312,35 +77086,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "23-033" + "@value": "14-006r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-19: Machine Learning Models Engineering Report" + "@value": "OGC® Testbed 10 Recommendations for Exchange of Terrain Data" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-005r3", + "@id": "http://www.opengis.net/def/docs/16-028r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-12-02" + "@value": "2017-06-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker" + "@value": "Thomas Disney" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -77350,27 +77124,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/14-005r3/14-005r3.html" + "@id": "https://docs.ogc.org/per/16-028r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "IndoorGML" + "@value": "16-028r1" }, { "@language": "en", - "@value": "14-005r3" + "@value": "Testbed-12 FIXM GML Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes." + "@value": "The FAA and EUROCONTROL, in conjunction with multiple other international partners, are currently in the process of developing the Flight Information Exchange Model (FIXM). FIXM is an exchange model capturing Flight and Flow information that is globally standardized. The need for FIXM was identified by the International Civil Aviation Organization (ICAO) Air Traffic Management Requirements and Performance Panel (ATMRPP) in order to support the exchange of flight information as prescribed in Flight and Flow Information for a Collaborative Environment (FF-ICE).\r\n\r\nFIXM is the equivalent, for the Flight domain, of Aeronautical Information Exchange Model (AIXM) and Weather Information Exchange Model (WXXM), both of which were developed in order to achieve global interoperability for, respectively, Aeronautical Information Systems (AIS) and Meteorological Information (MET) exchange. FIXM is therefore part of a family of technology independent, harmonized and interoperable information exchange models designed to cover the information needs of Air Traffic Management. Previous OGC IP initiatives developed an architecture that supports the exchange of AIXM and WXXM data. This report shall describe the integration of Geography Markup Language (GML) profile elements into FIXM, specifically, the Feature, Time, Geometries and Units of Measure (UOM), into FIXM version 3.0.1 and drafts of FIXM 4.0. The purpose of this report is to provide recommendations and change requests (CR) on the implementation of GML elements for use by the FIXM development community." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77381,35 +77155,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-005r3" + "@value": "16-028r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® IndoorGML" + "@value": "Testbed-12 FIXM GML Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-042r5", + "@id": "http://www.opengis.net/def/docs/00-116", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-18" + "@value": "2000-04-24" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "James Tomkins, Dominic Lowe" + "@value": "Cliff Kottman, Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -77419,27 +77193,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/15-042r5/15-042r5.html" + "@id": "https://portal.ogc.org/files/?artifact_id=7200" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-042r5" + "@value": "Topic 16 - Image Coordinate Transformation Services" }, { "@language": "en", - "@value": "TimeseriesML 1.2 – XML Encoding of the Timeseries Profile of Observations and Measurements" + "@value": "00-116" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "TimeseriesML 1.2 defines an XML encoding that implements the OGC Timeseries Profile of Observations and Measurements, with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of data exchange requirements." + "@value": "Covers image coordinate conversion services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77450,35 +77224,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-042r5" + "@value": "00-116" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC TimeseriesML 1.2 – XML Encoding of the Timeseries Profile of Observations and Measurements" + "@value": "Topic 16 - Image Coordinate Transformation Services" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-163", + "@id": "http://www.opengis.net/def/docs/10-184", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-05-02" + "@value": "2010-12-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "David Rosinger, Stan Tillman" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -77488,27 +77262,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27330" + "@id": "https://portal.ogc.org/files/?artifact_id=41573" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-163" + "@value": "10-184" }, { "@language": "en", - "@value": "Data View Architecture Engineering Report" + "@value": "OGC Fusion Standards Study, Phase 2 Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC document presents a summary of the Data View Architecture experiment conducted as part of the Geo-Processing Workflow (GPW) thread in the OWS-5 test bed. The main activities in this experiment were the storage of Data Views in an ebRIM Catalog and the discovery and use of those Data Views by an Integrated Client." + "@value": "This Engineering Report summarizes two phases of the Open Geospatial Consortium (OGC®) Fusion Standards study and of the fusion prototypes developed during the OWS-7 Testbed which occurred between the two study phases. Recommendations from the first phase of the study were implemented in OWS-7. Based upon the results of OWS-7, responses to two Requests for Information and a multi-day workshop, this report provides a cumulative set of recommendations for advancing fusion based on open standards. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77519,30 +77293,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-163" + "@value": "10-184" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-5 Data View Architecture Engineering Report" + "@value": "OGC Fusion Standards Study, Phase 2 Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-028", + "@id": "http://www.opengis.net/def/docs/09-033", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-01-18" + "@value": "2009-07-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Dean Younge" + "@value": "Simon Jirka, Arne Bröring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -77557,17 +77331,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-028.html" + "@id": "https://portal.ogc.org/files/?artifact_id=33284" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-028" + "@value": "OWS-6 SensorML Profile for Discovery Engineering Report" }, { "@language": "en", - "@value": "OGC Testbed-17: OGC API - Moving Features Engineering Report" + "@value": "09-033" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -77577,7 +77351,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Testbed-17 Moving Features thread conducted an interoperability feasibility study that examined specific scenarios that could be supported by a Moving Features Application Programming Interface (API). The use cases considered tracking objects based on motion imagery, analytical processing and visualization. This Engineering Report presents a specification of a prototype Moving Features API, that could serve as the foundation for a future draft OGC API — Moving Features standard.\r\n\r\n" + "@value": "This document defines a basic SensorML profile for discovery purposes. Besides a minimum set of metadata also the structure of according SensorML documents is defined in order to ensure a consistent metadata description. This goal is achieved by a set of Schematron rules that can be used to validate if a given SensorML document complies with the profile described in this engineering report." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77588,35 +77362,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-028" + "@value": "09-033" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: OGC API - Moving Features Engineering Report" + "@value": "OWS-6 SensorML Profile for Discovery Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-022r1", + "@id": "http://www.opengis.net/def/docs/05-047r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-05-12" + "@value": "2005-03-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Ron Lake" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cr" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -77626,27 +77400,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27697" + "@id": "https://portal.ogc.org/files/?artifact_id=11418" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Change Request - O&M Part 1 - Move extensions to new namespace" + "@value": "GML in JPEG 2000 for Geographic Imagery" }, { "@language": "en", - "@value": "08-022r1" + "@value": "05-047r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cr" + "@id": "http://www.opengis.net/def/doc-type/d-rfc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The XML Schema implementation of optional/informative elements of the Observation Schema was published in the om/1.0.0/extensions directory, in the same XML namespace as the base schema. Those OGC implementations that have a dependency on the Observation Schema (i.e. Sampling Features, SOS) the “all-components” document om.xsd. However, the all-components stub-schema document “om.xsd” does not include the extensions. Thus, any application which requires one of the dependent OGC schemas (Sampling Features, SOS) may not access the Observation Schema Extensions, since the of om.xsd clashes with any attempt to om_extended.xsd. This problem is a consequence of an error in the modularization strategy for optional elements, combined with the rules for schema document resolution used by standard processing environments." + "@value": "The GML (Geography Markup Language) is an XML grammar for the encoding geographic information including geographic features, coverages, observations, topology, geometry, coordinate reference systems, units of measure, time, and value objects.\r\nJPEG 2000 is a wavelet based encoding for imagery that provides the ability to include XML data for description of the image within the JPEG 2000 data file.\r\nThis specification defines the means by which GML is to be used within JPEG 2000 images for geographic imagery. This includes the following:\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77657,35 +77431,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-022r1" + "@value": "05-047r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Change Request - O&M Part 1 - Move extensions to new namespace" + "@value": "GML in JPEG 2000 for Geographic Imagery" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-073", + "@id": "http://www.opengis.net/def/docs/01-111", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-08-05" + "@value": "2001-06-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "James Ressler" + "@value": "ISO" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -77695,27 +77469,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=34145" + "@id": "http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=26020" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-6 SWE PulseNet™ Engineering Report" + "@value": "Topic 11 - Metadata" }, { "@language": "en", - "@value": "09-073" + "@value": "01-111" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document summarizes work delivered on the Sensor Web Enablement (SWE) thread of OWS-6. In particular, Northrop Grumman’s contribution from PulseNet™ to the Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) standard-compliant sensors into an OGC SWE-based architecture." + "@value": "ISO 19115 was adopted as a replacement for OGC Abstract Specification Topics 9 and 11. In June 2001, a motion to include material in addition to ISO 19115 was adopted as document 01-111 Metadata AS. The approved addition to document 01-111 is contained in document 01-053r1, which normatively references parts of the old AS Topic 9, document 99-109r1. FGDC in conjunction with ANSI INCITS L1 are planning the migration of the FGDC Content Standard for Geospatial Metadata to be a profile of ISO 19115" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77726,160 +77500,304 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-073" + "@value": "01-111" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 SWE PulseNet™ Engineering Report" + "@value": "Topic 11 - Metadata" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/d-as", + "@id": "http://www.opengis.net/def/doc-type/bp", "http://www.w3.org/2004/02/skos/core#narrower": [ { - "@id": "http://www.opengis.net/def/docs/03-073r1" + "@id": "http://www.opengis.net/def/docs/19-066" }, { - "@id": "http://www.opengis.net/def/docs/04-046r3" + "@id": "http://www.opengis.net/def/docs/06-021r4" }, { - "@id": "http://www.opengis.net/def/docs/99-107" + "@id": "http://www.opengis.net/def/docs/16-011r3" }, { - "@id": "http://www.opengis.net/def/docs/18-005r4" + "@id": "http://www.opengis.net/def/docs/16-070r2" }, { - "@id": "http://www.opengis.net/def/docs/99-109r1" + "@id": "http://www.opengis.net/def/docs/14-106" }, { - "@id": "http://www.opengis.net/def/docs/99-100r1" + "@id": "http://www.opengis.net/def/docs/06-188r1" }, { - "@id": "http://www.opengis.net/def/docs/15-104r5" + "@id": "http://www.opengis.net/def/docs/16-070r3" }, { - "@id": "http://www.opengis.net/def/docs/10-020" + "@id": "http://www.opengis.net/def/docs/16-005r2" }, { - "@id": "http://www.opengis.net/def/docs/99-105r2" + "@id": "http://www.opengis.net/def/docs/11-035r1" }, { - "@id": "http://www.opengis.net/def/docs/01-111" + "@id": "http://www.opengis.net/def/docs/14-004r1" }, { - "@id": "http://www.opengis.net/def/docs/18-005r5" + "@id": "http://www.opengis.net/def/docs/09-153r1" }, { - "@id": "http://www.opengis.net/def/docs/02-102" + "@id": "http://www.opengis.net/def/docs/06-126r2" }, { - "@id": "http://www.opengis.net/def/docs/04-084" + "@id": "http://www.opengis.net/def/docs/16-140r1" }, { - "@id": "http://www.opengis.net/def/docs/10-004r3" + "@id": "http://www.opengis.net/def/docs/13-043" }, { - "@id": "http://www.opengis.net/def/docs/08-015r2" + "@id": "http://www.opengis.net/def/docs/15-120r4" }, { - "@id": "http://www.opengis.net/def/docs/00-106" + "@id": "http://www.opengis.net/def/docs/16-010r3" }, { - "@id": "http://www.opengis.net/def/docs/01-101" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/15-045r7", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/13-039" + }, { - "@type": "xsd:date", - "@value": "2021-03-22" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/14-012r1" + }, { - "@value": "Peter Trevelyan, Paul Hershberg, Steve Olson" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/11-135r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/06-028r3" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/16-005r4" + }, { - "@id": "https://docs.ogc.org/is/15-045r7/15-045r7.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/16-006r4" + }, { - "@language": "en", - "@value": "15-045r7" + "@id": "http://www.opengis.net/def/docs/03-002r9" }, { - "@language": "en", - "@value": "MetOcean Application profile for WCS2.1: Part 0 MetOcean Metadata" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/17-011r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/16-004r5" + }, { - "@value": "The purpose of this Met Ocean profile of WCS2.1 is to define the metadata returned in the response documents resulting from the WCS2.1 operations: GetCapabilities, and DescribeCoverage; for use within the meteorological and oceanographic communities. It also defines the new operation DescribeCoverageCollection.\r\n\r\nThis work has been done by members of the OGC MetOcean Domain Working Group." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/16-009r3" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/15-005r1" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-045r7" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/07-018r2" + }, { - "@language": "en", - "@value": "OGC MetOcean Application profile for WCS2.1: Part 0 MetOcean Metadata" + "@id": "http://www.opengis.net/def/docs/21-070" + }, + { + "@id": "http://www.opengis.net/def/docs/17-084r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-125r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-035r2" + }, + { + "@id": "http://www.opengis.net/def/docs/07-107r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-011r4" + }, + { + "@id": "http://www.opengis.net/def/docs/16-003r4" + }, + { + "@id": "http://www.opengis.net/def/docs/12-111r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-102r3a" + }, + { + "@id": "http://www.opengis.net/def/docs/16-003r2" + }, + { + "@id": "http://www.opengis.net/def/docs/20-095" + }, + { + "@id": "http://www.opengis.net/def/docs/15-120r6" + }, + { + "@id": "http://www.opengis.net/def/docs/16-086r3" + }, + { + "@id": "http://www.opengis.net/def/docs/10-189r2" + }, + { + "@id": "http://www.opengis.net/def/docs/10-003r1" + }, + { + "@id": "http://www.opengis.net/def/docs/08-139r3" + }, + { + "@id": "http://www.opengis.net/def/docs/11-122r1" + }, + { + "@id": "http://www.opengis.net/def/docs/21-007" + }, + { + "@id": "http://www.opengis.net/def/docs/12-032r2" + }, + { + "@id": "http://www.opengis.net/def/docs/14-003" + }, + { + "@id": "http://www.opengis.net/def/docs/16-009r5" + }, + { + "@id": "http://www.opengis.net/def/docs/16-004r4" + }, + { + "@id": "http://www.opengis.net/def/docs/09-102" + }, + { + "@id": "http://www.opengis.net/def/docs/02-007r4" + }, + { + "@id": "http://www.opengis.net/def/docs/20-089r1" + }, + { + "@id": "http://www.opengis.net/def/docs/15-003" + }, + { + "@id": "http://www.opengis.net/def/docs/16-010r5" + }, + { + "@id": "http://www.opengis.net/def/docs/07-118r8" + }, + { + "@id": "http://www.opengis.net/def/docs/07-097" + }, + { + "@id": "http://www.opengis.net/def/docs/06-095" + }, + { + "@id": "http://www.opengis.net/def/docs/07-118r9" + }, + { + "@id": "http://www.opengis.net/def/docs/16-011r5" + }, + { + "@id": "http://www.opengis.net/def/docs/05-042r2" + }, + { + "@id": "http://www.opengis.net/def/docs/16-005r3" + }, + { + "@id": "http://www.opengis.net/def/docs/21-068" + }, + { + "@id": "http://www.opengis.net/def/docs/08-167r2" + }, + { + "@id": "http://www.opengis.net/def/docs/10-028r1" + }, + { + "@id": "http://www.opengis.net/def/docs/13-015" + }, + { + "@id": "http://www.opengis.net/def/docs/16-006r5" + }, + { + "@id": "http://www.opengis.net/def/docs/09-102r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-003r3" + }, + { + "@id": "http://www.opengis.net/def/docs/15-120r5" + }, + { + "@id": "http://www.opengis.net/def/docs/15-037" + }, + { + "@id": "http://www.opengis.net/def/docs/07-092r3" + }, + { + "@id": "http://www.opengis.net/def/docs/13-042" + }, + { + "@id": "http://www.opengis.net/def/docs/12-066" + }, + { + "@id": "http://www.opengis.net/def/docs/16-070r4" + }, + { + "@id": "http://www.opengis.net/def/docs/16-114r3" + }, + { + "@id": "http://www.opengis.net/def/docs/11-169r1" + }, + { + "@id": "http://www.opengis.net/def/docs/14-110r2" + }, + { + "@id": "http://www.opengis.net/def/docs/15-005r2" + }, + { + "@id": "http://www.opengis.net/def/docs/15-107" + }, + { + "@id": "http://www.opengis.net/def/docs/07-063r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-010r4" + }, + { + "@id": "http://www.opengis.net/def/docs/15-004" + }, + { + "@id": "http://www.opengis.net/def/docs/16-004r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-009r4" + }, + { + "@id": "http://www.opengis.net/def/docs/06-142r1" + }, + { + "@id": "http://www.opengis.net/def/docs/06-129r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-006r3" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-171", + "@id": "http://www.opengis.net/def/docs/20-006", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-10-12" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Jirka, Daniel Nüst" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -77889,27 +77807,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40609" + "@id": "https://docs.ogc.org/note/20-006.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Sensor Instance Registry Discussion Paper " + "@value": "20-006" }, { "@language": "en", - "@value": "10-171" + "@value": "OGC CDB Version 1.2 Release Notes" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion paper introduces the Sensor Instance Registry (SIR), a web service interface for managing the metadata and status information of sensors. Furthermore this service is capable of automatically harvesting sensor metadata, transforming the collected metadata sets into a data model compatible to OGC Catalogs and to push harvested metadata into OGC Catalog instances." + "@value": "This document provides the set of revision notes for the CDB Standard, version 1.2 [OGC ]> and does not modify that standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77920,35 +77838,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-171" + "@value": "20-006" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Instance Registry Discussion Paper " + "@value": "OGC CDB Version 1.2 Release Notes" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-018", + "@id": "http://www.opengis.net/def/docs/14-009r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-04-08" + "@value": "2014-04-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ben Domenico, Stefano Nativi" + "@value": "Pedro Gonçalves" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -77958,27 +77876,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=32195" + "@id": "https://portal.ogc.org/files/?artifact_id=57477" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-018" + "@value": "14-009r1" }, { "@language": "en", - "@value": "Web Coverage Service (WCS) 1.1 extension for CF-netCDF 3.0 encoding" + "@value": "Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This extension of the WCS standard specifies an Information Community data model with the related encoding that may optionally be implemented by WCS servers. This extension specification allows clients to evaluate, request and use data encoded in CF-netCDF3 format from a WCS server.\r\nThis document is an extension of the Web Coverage Service (WCS) 1.1 Corrigendum 2 (version 1.1.2) Implementation Standard [OGC 07-067r5]. With small changes, this extension is expected to also apply to WCS 1.2. \r\n" + "@value": "This document identifies the generic rules for obtaining JSON documents directly from existing XML documents and schemas elements. It is primordially targeting the OWS Context JSON Encoding design, but is presented in a generic approach. Such generic approach can offer the guidelines for other OGC services, when defining and using JSON encodings." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -77989,30 +77907,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-018" + "@value": "14-009r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Coverage Service (WCS) 1.1 extension for CF-netCDF 3.0 encoding" + "@value": "OGC® Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-112r1", + "@id": "http://www.opengis.net/def/docs/06-140", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-10-12" + "@value": "2007-06-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Jirka, Arne Bröring, Daniel Nüst" + "@value": "Dr. Markus M" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -78027,17 +77945,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=40571" + "@id": "https://portal.ogc.org/files/?artifact_id=19084" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-112r1" + "@value": "Feature Styling IPR" }, { "@language": "en", - "@value": "Sensor Observable Registry (SOR) Discussion Paper" + "@value": "06-140" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -78047,7 +77965,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Discussion paper introduces the Sensor Observable Registry (SOR), a web service interface for managing the definitions of phenomena measured by sensors as well as exploring semantic relationships between these phenomena." + "@value": "Feature Styling is based on a distributed computational platform that employs a number\r\nof standard interfaces and encodings to allow for flexible, scalable and interoperable\r\nmanagement of symbology (styles and symbols) in the process of producing maps from\r\ndifferent kinds of data, most important being source GML data.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78058,35 +77976,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-112r1" + "@value": "06-140" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Observable Registry (SOR) Discussion Paper" + "@value": "Feature Styling IPR" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-045", + "@id": "http://www.opengis.net/def/docs/09-146r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-10-26" + "@value": "2012-05-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Tom Landry" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/sap" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -78096,27 +78014,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-045.html" + "@id": "https://portal.ogc.org/files/?artifact_id=48553" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-045" + "@value": "09-146r2" }, { "@language": "en", - "@value": "OGC Earth Observation Applications Pilot: CRIM Engineering Report" + "@value": "Coverage Implementation Schema" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/sap" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report documents experiments conducted by CRIM in OGC’s Earth Observation Applications Pilot project, sponsored by the European Space Agency (ESA) and Natural Resources Canada (NRCan), with support from Telespazio VEGA UK. Remote sensing, machine learning and climate informatics applications were reused, adapted and matured in a common architecture. These applications were deployed in a number of interoperable data and processing platforms hosted in three Canadian provinces, in Europe and in the United States." + "@value": "This document specifies a GML coverage structure extending the definition of GML 3.2.1 [07-036] in a compatible way.\r\n\r\nMain change over GML is the addition of one mandatory component, rangeType, to the Coverage definition of GML 3.2.1 to provide a concise description of the coverage range\r\nvalue definition. Further, handling of format encodings different from GML are established.\r\n\r\nThis enhanced coverage type is used, for example, by the Web Coverage Service (WCS) Standard [1] version 2.0 and higher, but is independent from WCS service. This augmented\r\ncoverage structure can serve a wide range of coverage application domains and service types, thereby contributing to harmonization and interoperability." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78127,35 +78045,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-045" + "@value": "09-146r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Earth Observation Applications Pilot: CRIM Engineering Report" + "@value": "OGC® Coverage Implementation Schema" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-049", + "@id": "http://www.opengis.net/def/docs/19-077", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-05-05" + "@value": "2020-05-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Keith Ryden" + "@value": "Gobe Hobona" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -78165,27 +78083,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=829" + "@id": "https://docs.ogc.org/dp/19-077.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "99-049" + "@value": "19-077" }, { "@language": "en", - "@value": "Simple Features Implementation Specification for SQL" + "@value": "OGC Body of Knowledge " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc)." + "@value": "The OGC Body of Knowledge is a structured collection of concepts and related resources that can be found in the OGC library. It is, in effect, a view of explicit knowledge available from the OGC Virtual Knowledge Store and related components such as the OGC Definitions Server and the OGC Glossary of Terms. The OGC Body of Knowledge is intended to provide a reference for users and developers of geospatial software. This discussion paper describes the approach taken to develop the OGC Body of Knowledge and presents the results of the approach. It is intended to encourage and facilitate discussion within the OGC membership and wider geospatial community." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78196,35 +78114,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-049" + "@value": "19-077" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Simple Features Implementation Specification for SQL" + "@value": "OGC Body of Knowledge - Version 0.1 - Discussion Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-065r2", + "@id": "http://www.opengis.net/def/docs/11-116", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-07-26" + "@value": "2011-12-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos, Clemens Portele" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -78234,27 +78152,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/21-065r2/21-065r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=46793" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-065r2" + "@value": "OWS-8 Geoprocessing for Earth Observations Engineering Report" }, { "@language": "en", - "@value": "Common Query Language (CQL2)" + "@value": "11-116" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A fundamental operation performed on a collection of features is that of filtering in order to obtain a subset of the data which contains feature instances that satisfy some filtering criteria. This document specifies\r\n\r\nA filter grammar called Common Query Language (CQL2);\r\n\r\nTwo encodings for CQL2 - a text and a JSON encoding.\r\n\r\nThe Common Query Language (CQL2) defined in this document is a generic filter grammar that can be used to specify how resource instances in a source collection of any item type, including features, can be filtered to identify a results set. Typically, CQL2 is used in query operations to identify the subset of resources, such as features, that should be included in a response document. However, CQL2 can also be used in other operations, such as updates, to identify the subset of resources that should be affected by an operation.\r\n\r\nEach resource instance in the source collection is evaluated against a filtering expression. The filter expression always evaluates to true, false or null. If the expression evaluates to true, the resource instance satisfies the expression and is marked as being in the result set. If the overall filter expression evaluates to false or null, the data instance is not in the result set. Thus, the net effect of evaluating a filter expression is a set of resources that satisfy the predicates in the expression.\r\n\r\nThe Common Query Language and its text encoding are not new, but this is the first time that the language is formally specified. The Common Query Language with the acronym CQL was originally created as a text encoding for use with implementations of the OGC Catalogue Service Implementation Specification. The language is based on the capabilities in the OGC Filter Encoding Standard, which was originally part of the Web Feature Service (WFS) Standard.\r\n\r\nThe Common Query Language as specified in this document is a revision of this earlier version. While the language design including the classification of operators are consistent with the earlier specification, there have been a number of changes and existing implementations of CQL will need to be updated to process filter expressions specified by this document. This document therefore uses the acronym CQL2 to refer to the current version of the Common Query Language." + "@value": "Ad-hoc processing of Earth Observation (EO) data available through online resources is\r\ngaining more and more attention. Expected benefits include\r\n- More versatile EO data access\r\n- More convenient EO data access\r\n- Consequently, broadened use and exploitation of EO data\r\n- An important step towards integration of EO data into automatic chaining and\r\norchestration\r\n- More efficient EO data access: indicating the exact desired result and evaluating\r\nprocessing code close to the coverage data source (i.e., on the server) minimizes\r\nnetwork traffic, one of today’s critical performance limiting factors." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78265,35 +78183,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-065r2" + "@value": "11-116" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Common Query Language (CQL2)" + "@value": "OWS-8 Geoprocessing for Earth Observations Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-066r1", + "@id": "http://www.opengis.net/def/docs/06-021r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-10-01" + "@value": "2006-03-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona;Roger Brackin" + "@value": "Mike Botts, Alex Robin, John Davidson, Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp-draft" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -78303,27 +78221,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64173" + "@id": "https://portal.ogc.org/files/?artifact_id=14140" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-066r1" + "@value": "06-021r1" }, { "@language": "en", - "@value": "Use of Semantic Linked Data with RDF for National Map NHD and Gazetteer Data Engineering Report " + "@value": "Sensor Web Enablement Architecture Document" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp-draft" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Over the past few years there has been an increase in the number, size and complexity of databases across government sectors. This has undoubtedly created challenges relating to the discovery and access of information and services on multiple databases across static and deployed networks. Linked Data has been suggested as a method able to tackle those challenges. The aim of the Hydrographic Linked Data activity in the OGC Testbed 11 was to advance the use of Linked Data for hydrographic data by building on the achievements of the previous testbeds and to improve the understanding of how to better build relations between hydro features and non-hydro features (e.g., stream gauge measurement/location vs bridge or other built features upstream or downstream). This aspect of the testbed focused on the National Hydrography Dataset (NHD) which is published by the United States Geological Survey (USGS). This OGC Engineering Report provides guidelines on the publication of hydrographic and hydrological data serialized as Resource Description Framework (RDF) using Linked Data principles and technologies based on OGC standards. The document also presents the experimentation conducted by Testbed 11 in order to identify those guidelines." + "@value": "The aim of this document is to provide a overview description of the general architecture that applies to the Sensor Web Enablement (SWE). While this document provides a synopsis of the relevant encodings and web services, it does not contain interface descriptions of the components.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78334,35 +78252,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-066r1" + "@value": "06-021r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 11 Use of Semantic Linked Data with RDF for National Map NHD and Gazetteer Data Engineering Report " + "@value": "OpenGIS Sensor Web Enablement Architecture Document" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-084r4", + "@id": "http://www.opengis.net/def/docs/04-095c1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-08-27" + "@value": "2005-05-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "Peter Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -78372,27 +78290,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/as/04-084r4/04-084r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=51130" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Topic 00 - Overview" + "@value": "Filter Encoding Implementation Specification Corrigendum 1" }, { "@language": "en", - "@value": "04-084r4" + "@value": "04-095c1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document (Topic 0) is an overview of the OGC Abstract Specification." + "@value": "The OpenGIS® Filter Encoding Standard (FES) defines an XML encoding for filter expressions. A filter expression logically combines constraints on the\r\nproperties of a feature in order to identify a particular subset of features to be operated upon. For example, a subset of features might be identified to render them in a particular color or convert them into a user-specified format. Constraints can be specified on values of spatial, temporal and scalar properties. An example of a filter is: Find all the properties in Omstead County owned by Peter Vretanos.\r\n\r\nThis standard is used by a number of OGC Web Services, including the Web Feature Service [http://www.opengeospatial.org/standards/wfs], the Catalogue Service [http://www.opengeospatial.org/standards/cat] and the Styled Layer Descriptor Standard [http://www.opengeospatial.org/standards/sld]. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78403,35 +78321,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-084r4" + "@value": "04-095c1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 0 - Overview" + "@value": "Filter Encoding Implementation Specification Corrigendum 1" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-019r2", + "@id": "http://www.opengis.net/def/docs/09-146r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-04-06" + "@value": "2010-10-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Chris Higgins" + "@value": "Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-sap" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -78441,27 +78359,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47852" + "@id": "https://portal.ogc.org/files/?artifact_id=41438" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-019r2" + "@value": "09-146r1" }, { "@language": "en", - "@value": "Engineering Report for the OWS Shibboleth Interoperability Experiment" + "@value": "GML Application Schema - Coverages" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-sap" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document reports on outcomes from the OGC Web Services Shibboleth Interoperability Experiment (OSI). The main objective of OSI was to advance the use of Shibboleth (an open source implementation of SAML) as a means of protecting OWS. In the process, OSI helped develop further understanding of this approach to establishing trusted federations of OWS. This report documents these findings and is intended to be of use to those interested in how Shibboleth/SAML access management federations may function as an organisational model for operational Spatial Data Infrastructure." + "@value": "This document specifies the GML coverage structure to be used by OGC standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78472,35 +78390,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-019r2" + "@value": "09-146r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Engineering Report for the OWS Shibboleth Interoperability Experiment" + "@value": "OGC® GML Application Schema - Coverages" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-121r3", + "@id": "http://www.opengis.net/def/docs/13-054r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-04-03" + "@value": "2013-11-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Richard Martell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -78510,27 +78428,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20040" + "@id": "https://portal.ogc.org/files/?artifact_id=55342" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-121r3" + "@value": "13-054r1" }, { "@language": "en", - "@value": "Web Service Common Implementation Specification" + "@value": "Summary and Recommendations of the Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Interoperabi" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Web Services Common (WS-Common) Interface Standard specifies parameters and data structures that are common to all OGC Web Service (OWS) Standards. The standard normalizes the ways in which operation requests and responses handle such elements as bounding boxes, exception processing, URL requests, URN expressions, and key value encoding. Among its uses, this document serves as a normative reference for other OGC Web Service standards, including the OpenGIS Web Map Service (WMS) [http://www.opengeospatial.org/standards/wms], Web Feature Service (WFS) [http://www.opengeospatial.org/standards/wfs], and Web Coverage Service (WCS) [http://www.opengeospatial.org/standards/wcs] standards. Rather than continuing to repeat this material in each such standard, each standard will normatively reference parts of this document." + "@value": "Geospatial information technologies are increasingly a foundation for supporting Information Sharing Environment (ISE), homeland security (HLS), homeland defense (HLD), law enforcement (LE), emergency management (EM) and public safety missions in the US. The inability to transport, deliver and exchange geospatial information for critical geospatial assets increases the risk to the nation.\r\nMany ISE HLS/HDS/LE mission partners have developed stand-alone geospatial information systems (GIS) or Common Operating Picture (COP) applications to support their stakeholder communities during incidents and for daily operational support. While different missions, these GIS/COP capabilities rely upon much of the same data or generate specific data during an event. The data are often stove-piped and not exposed to a broader community that could benefit from these data, resulting in duplication and delayed or incorrect decisions. While mission partners do not need to use the same GIS/COP tools, they could benefit from shared access to the common operating data and services used within these systems if they were exposed and exchanged using open standards.\r\nUnder the auspices of the Program Manager for the Information Sharing Environment (PM-ISE), an identified government-wide information sharing shortfall will be resolved by funding work to enhance the National Information Exchange Model (NIEM). The focus of this work is to further enhance the framework’s geospatial exchange capability in light of guidelines and standards issued by the Open Geospatial Consortium (OGC) so as to significantly improve inter-government information sharing.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78541,35 +78459,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-121r3" + "@value": "13-054r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web Service Common Implementation Specification" + "@value": "Summary and Recommendations of the Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Interoperabi" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-094r1", + "@id": "http://www.opengis.net/def/docs/05-042r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-10-09" + "@value": "2005-11-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler, Rob Cass" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -78579,27 +78497,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-094r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=13140" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-094r1" + "@value": "Web services architecture description" }, { "@language": "en", - "@value": "Portrayal Concept Development Study" + "@value": "05-042r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The main goal of this CDS is to advance the standards and guidance that will allow production of high-quality digital maps over the web from existing vector data." + "@value": "This document summarizes the most significant aspects of the Open Geospatial Consortium (OGC) web services architecture, which the OGC is currently developing. This architecture is a service-oriented architecture, with all components providing one or more services to other services or to clients." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78610,35 +78528,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-094r1" + "@value": "05-042r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Portrayal Concept Development Study" + "@value": "OpenGIS Web services architecture description" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-039", + "@id": "http://www.opengis.net/def/docs/21-060r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-08-19" + "@value": "2024-07-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "Peter Baumann " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -78648,27 +78566,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=63289" + "@id": "https://docs.ogc.org/as/21-060r2/21-060r2.pdf" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Envisioning a Tiled Elevation Extension for the OGC GeoPackage Encoding Standard" + "@value": "OGC Abstract Specification Topic 6: Schema for Coverage Geometry and Functions – Part 3: Processing Fundamentals" }, { "@language": "en", - "@value": "15-039" + "@value": "21-060r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The GeoPackage Standards Working Group (SWG) presents a vision for storing tiled gridded elevation data in a GeoPackage." + "@value": "This document defines, at a high, implementation-independent level, operations on coverages - i.e., digital representations of space-time varying geographic phenomena - as defined in ISO 19123-1. Specifically, regular and irregular grid coverages are addressed. Future versions will additionally support further axis types as well as further coverage types from ISO19123-1, such as point clouds and meshes in particular. While the core functionality is expected to be generic and applicable for any coverage, there may be special functionality for particular coverage types." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78679,35 +78597,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-039" + "@value": "21-060r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Envisioning a Tiled Elevation Extension for the OGC GeoPackage Encoding Standard" + "@value": "Topic 6.3 - Schema for Coverage Geometry and Functions – Part 3: Processing Fundamentals" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-009r4", + "@id": "http://www.opengis.net/def/docs/99-100r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-12-19" + "@value": "1999-06-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Cliff Kottman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -78717,27 +78635,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/16-009r4" + "@id": "https://portal.ogc.org/files/?artifact_id=11496" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-009r4" + "@value": "99-100r1" }, { "@language": "en", - "@value": "Volume 6: OGC CDB Rules for Encoding Data using OpenFlight" + "@value": "Topic 0 - Overview" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of that document for a general overview." + "@value": "Introduction and roadmap to the Abstract specification." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78748,35 +78666,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-009r4" + "@value": "99-100r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 6: OGC CDB Rules for Encoding Data using OpenFlight" + "@value": "Topic 0 - Overview" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-160r1", + "@id": "http://www.opengis.net/def/docs/05-057r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-09-12" + "@value": "2006-02-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Pete Brennen" + "@value": "Jolyon Martin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -78786,27 +78704,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=30064" + "@id": "https://portal.ogc.org/files/?artifact_id=13885" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-160r1" + "@value": "05-057r3" }, { "@language": "en", - "@value": "OWS-5 Conflation Engineering Report" + "@value": "Minimal Application Profile for EO Products" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report describes the process of conflation, outlines a framework for conflation and conflation rules services within a service oriented architecture, and describes the implementation of conflation services during the OGC OWS-5 testbed." + "@value": "The services proposed in this profile are intended to support the identification and subsequent ordering of\r\nEO data products from previously identified data collections. The intent of this initial profile is to\r\ndescribe a minimum interface that can be supported by many data providers (satellite operators, data\r\ndistributors " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78817,30 +78735,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-160r1" + "@value": "05-057r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-5 Conflation Engineering Report" + "@value": "Minimal Application Profile for EO Products" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-029", + "@id": "http://www.opengis.net/def/docs/15-056", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-03-15" + "@value": "2015-10-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sara Saeedi" + "@value": "Wenwen Li, Sheng Wu" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -78855,17 +78773,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-029.html" + "@id": "https://portal.ogc.org/files/?artifact_id=64382" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-029" + "@value": "Testbed 11 Catalogue Service and Discovery Engineering Report" }, { "@language": "en", - "@value": "Symbology Engineering Report" + "@value": "15-056" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -78875,7 +78793,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The portrayal and visualization of geospatial information is a critical task for facilitating decision making, situational awareness, and spatial analysis. However, despite its importance, various local, national, and international agencies continue to use different symbols and terminology for the same event, feature, or entity. This approach prevents interoperability from being extended to the semantic level, which in turn makes it difficult to share, reuse, and mediate unambiguous portrayal information between agencies.\r\n\r\nThis Engineering Report (ER) captures the requirements, solutions, models, and implementations of the Open Geospatial Consortium (OGC) Testbed-14 Portrayal thread. This effort leverages the work of the Portrayal Ontology development and the Semantic Portrayal Service conducted during Testbed 10, 11, 12 and 13. Thus far the emphasis for developing the portrayal ontologies (Testbeds 12 and 13) has been on modeling and representing portrayal information for feature data. The objective of Testbed-14 is to extend the portrayal ontology to accommodate more complex symbols (e.g., composite symbols) and to provide clear recommendations on how to best proceed with portrayal information encodings." + "@value": "This OGC Testbed 11 Engineering Report provides a comprehensive review and comparison in terms of architecture, functionality, and usability of the OGC catalogue service standards CSW 2.0.2 and CSW 3.0. We are especially interested in how well the two standards provide support for open searches and federated distributed searches in current distributed computing paradigms. We also evaluated the support of semantic searches using different strategies, including (1) semantic mediation, a.k.a. ontology-based query expansion (Li et al. 2008; Li et al. 2011), (2) semantic association, which enables current catalogue information models to support semantic search (Li et al. 2014; Li et al. 2015), and (3) complete renovation of the CSW information model to be a triple store and utilize Semantic Web technology (Berner-Lee 2001) to support semantic query and data retrieval. Scenarios to search for hydrological data are developed to evaluate the performance of catalogue searching using the above strategies. Recommendations for adoption of CSW standards as well as tasks in advancing catalogue search and data discovery in future testbeds is also discussed. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -78886,162 +78804,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-029" + "@value": "15-056" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-14: Symbology Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://purl.org/dc/terms/provenance": [ - { - "@value": "Generated by the OGC Definitions Server to support integration of the elements of this ConceptScheme into bigger collections. ogc_skos_profile_entailements.ttl" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ - { - "@value": "Collection hierarchy for this ConceptScheme" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ - { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/doc-type/d-isc/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-sap/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/ipr/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/is-draft/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/ts/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-rfc/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-is/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/retired/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/sap/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/bp/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-atb/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/" - }, - { - "@id": "http://www.opengis.net/def/doc-type/is/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-bp/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-dp/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-rp/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/pc/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/isc/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-profile/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/pol/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/notes/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/d-as/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/cs/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/dp/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/per/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/profile/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/isx/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/as/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/orm/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/pol-nts/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/dp-draft/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/ug/collection" - }, - { - "@id": "http://www.opengis.net/def/doc-type/rfc/collection" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ - { - "@value": "Concepts in OGC Documents" + "@value": "OGC® Testbed 11 Catalogue Service and Discovery Engineering Report " } ] }, { - "@id": "http://www.opengis.net/def/docs/04-086", + "@id": "http://www.opengis.net/def/docs/03-064r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-02-20" + "@value": "2004-06-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Harrison,A.J. Maren,Jeff Stohlman,Mike Meyer,Glenn Pruitt,John Clink,Hans Polzer,Mark Schiffner" + "@value": "Eric Bertel" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -79051,27 +78842,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=7563" + "@id": "https://portal.ogc.org/files/?artifact_id=5936" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-086" + "@value": "03-064r5" }, { "@language": "en", - "@value": "EA-SIG Discovery White Paper" + "@value": "GO-1 Application Objects" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*RETIRED* This document describes the role of Discovery Services in the net-centric enterprise. The network centric enterprise is an environment with an almost infinite variety of resources. In this rich environment, suitable resources can be found to support almost any operational need. The problem, however, is finding the appropriate resources when they are needed. Discovery services address this problem." + "@value": "The GO-1 Application Objects specification defines a set of core packages that support a small set of Geometries, a basic set of renderable Graphics that correspond to those Geometries, 2D device abstractions (displays, mouse, keyboard, etc.), and supporting classes. Implementation of these APIs will support the needs of many users of geospatial and graphic information. These APIs support the rendering of geospatial datasets, provide fine-grained symbolization of geometries, and support dynamic, event and user driven animation of geo-registered graphics." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79082,30 +78873,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-086" + "@value": "03-064r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "EA-SIG Discovery White Paper" + "@value": "GO-1 Application Objects" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-078", + "@id": "http://www.opengis.net/def/docs/19-032", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-11" + "@value": "2020-07-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Steven Chau & Mohsen Kalantari" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -79120,17 +78911,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-078.html" + "@id": "https://docs.ogc.org/per/19-032.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-078" + "@value": "19-032" }, { "@language": "en", - "@value": "WFS 3.0 Vector Tiles Extension Engineering Report" + "@value": "Indoor Mapping and Navigation Pilot: Public Safety Features CityGML ADE ER" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -79140,7 +78931,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Feature data tiling, colloquially referred to as 'vector tiling', is a data delivery method that allows for large vector feature datasets to be systematically split into subsets or tiles [1]. This engineering report (ER) presents an extension specification for publishing of vector tiles data through an Application Programming Interface (API) that conforms to the emerging version 3.0 of the Web Feature Service (WFS) standard. The core of the WFS 3.0 standard offers direct fine-grained access to geospatial information at the feature level. The WFS standard specifies discovery and query operations for web services that publish feature data. Extensions to the WFS 3.0 Core API offer other capabilities such as transaction operations.\r\n\r\n" + "@value": "This document defines an Application Domain Extension (ADE) of CityGML for public safety use cases. The ADE has been developed as part of OGC’s Indoor Mapping and Modeling Pilot project sponsored by the National Institute of Standards and Technology (NIST), Communications Technology Laboratory (CTL), Public Safety Communications Research (PSCR) Division. The ADE has been developed primarily based on reference preplan symbology created by the National Alliance for Public Safety GIS (NAPSG) Foundation. NAPSG is a 501 (C) (3) not-for-profit organization that was established in 2005 to overcome challenges faced by Federal, tribal, state, and local public safety agencies in the United States. NAPSG focuses on using GIS technology to resolve challenges that occur. In the definition of the ADE, public safety requirements that were not explicit in NAPSG have also been considered. This Engineering Report (ER) provides the methodology of the ADE development, details the implementation of the ADE and its structure and the application of the ADE in the context of public safety use cases.\r\n\r\nThe findings include:\r\n\r\nA methodology to transform NAPSG symbology to data elements;\r\n\r\nA need for an extension of a reference to four existing CityGML classes; and\r\n\r\nThe creation of seven new CityGML classes that are critical for public safety use cases." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79151,35 +78942,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-078" + "@value": "19-032" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Vector Tiles Pilot: WFS 3.0 Vector Tiles Extension Engineering Report" + "@value": "OGC Indoor Mapping and Navigation Pilot: Public Safety Features CityGML ADE ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-036", + "@id": "http://www.opengis.net/def/docs/07-107r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-01-21" + "@value": "2008-05-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jean-Philippe Humblet" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -79189,27 +78980,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1306" + "@id": "https://portal.ogc.org/files/?artifact_id=27357" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-036" + "@value": "07-107r3" }, { "@language": "en", - "@value": "Web Map Context Documents" + "@value": "A URN namespace for the Open Geospatial Consortium (OGC)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rfc" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Create, store, and use state information from a WMS based client application" + "@value": " This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC. The formal Namespace identifier (NID) is ogc." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79220,35 +79011,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-036" + "@value": "07-107r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Map Context Documents" + "@value": "A URN namespace for the Open Geospatial Consortium (OGC)" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-037", + "@id": "http://www.opengis.net/def/docs/03-010r9", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-01" + "@value": "2003-10-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Harrison" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -79258,27 +79049,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-037.html" + "@id": "https://portal.ogc.org/files/?artifact_id=11517" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-037" + "@value": "Recommended XML Encoding of CRS Definitions" }, { "@language": "en", - "@value": "Testbed-13: SWAP Engineering Report" + "@value": "03-010r9" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-rp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC document provides an analysis of the prototype implementations, approaches and performance aspects of data serialization techniques explored in OGC Testbed 13. Specifically, it describes work done during Testbed 13 investigating serialization for geospatial data sets on OGC Web Feature Service (WFS) using Google Protocol Buffers (Protobuf) and Apache Avro.\r\n\r\nProtocol buffers are Google’s language-neutral, platform-neutral, extensible mechanism for serializing structured data. They are described by Google in the following manner - 'think XML, but smaller, faster, and simpler'. With Protobuf Google indicates developers can define how they want their data to be structured once, then they can use special generated source code to easily write and read structured data to and from a variety of data streams and using a variety of languages. Apache Avro is described as a remote procedure call and data serialization framework developed within Apache’s Hadoop project. It uses JavaScript Object Notation(JSON) for defining data types and reportedly serializes data in a compact binary format." + "@value": "This OpenGIS Recommendation Paper specifies basic XML encoding of data defining coordinate reference systems and coordinate operations. This encoding is expected to be adapted and used by multiple OGC Implementation Specifications, by the separate specification of Application Schemas. This document is a Recommendation Paper because the specified encoding is more general than an OpenGIS Implementation Specification and more specific than the OpenGIS Abstract Specification." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79289,35 +79080,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-037" + "@value": "03-010r9" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: SWAP Engineering Report" + "@value": "Recommended XML Encoding of CRS Definitions" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-104r4", + "@id": "http://www.opengis.net/def/docs/03-008r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-08-04" + "@value": "2003-04-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Herring" + "@value": "Ingo Simonis, Andreas Wytzisk" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -79327,27 +79118,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=25354" + "@id": "https://portal.ogc.org/files/?artifact_id=1367" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-104r4" + "@value": "Web Notification Service" }, { "@language": "en", - "@value": "Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option" + "@value": "03-008r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. " + "@value": "The Web Notification Service (WNS) is the first asynchronous messaging service specified by OGC. At the moment, the WNS message schema is optimized to fulfil the needs of services supporting the use of sensors, like Sensor Planning Service. Future work activities should include the adaptation of the message schema to the needs of other services." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79358,35 +79149,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-104r4" + "@value": "03-008r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option" + "@value": "Web Notification Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-094", + "@id": "http://www.opengis.net/def/docs/12-162r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-11-24" + "@value": "0000-00-00" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Bastian Baranski" + "@value": "Jinsongdi Yu, Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -79396,27 +79187,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=45403" + "@id": "https://portal.ogc.org/files/?artifact_id=51911" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-094" + "@value": "OWS-9 WCS Conformance Testing Engineering Report" }, { "@language": "en", - "@value": "WS-Agreement Application Profile for OGC Web Services" + "@value": "12-162r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies a) XML schemas for providing functional and non-functional service descriptions of OGC Web Services (OWS), b) an URN namespace for identifying exposed and measurable service properties of OWS and c) a DSL for defining and evaluating service level guarantees." + "@value": "This Engineering Report was prepared as a deliverable for the OGC Web Services, Phase\r\n9 (OWS-9) initiative of the OGC Interoperability Program. The document presents the\r\nwork completed with respect to the Conformance & Interoperability Testing &\r\nEvaluation sub-thread within OWS-9.\r\nThis Engineering Report describes and evaluates the specification of WCS 2.0 core\r\ncorrigenda and extensions’ Abstract Test Suite (ATS) and the implementation of ETS for\r\nuse within an OGC SOA processing chain." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79427,35 +79218,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-094" + "@value": "12-162r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "WS-Agreement Application Profile for OGC Web Services" + "@value": "OWS-9 WCS Conformance Testing Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-126r3", + "@id": "http://www.opengis.net/def/docs/17-024", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-08-30" + "@value": "2018-01-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Taylor" + "@value": "Pedro Gonçalves" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -79465,27 +79256,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=48531" + "@id": "https://docs.ogc.org/per/17-024.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-126r3" + "@value": "17-024" }, { "@language": "en", - "@value": "WaterML 2.0: Part 1- Timeseries" + "@value": "Testbed-13: Application Deployment and Execution Service Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is an OGC® Encoding Standard for the representation of hydrological observations data with a specific focus on time series structures. WaterML2.0 is implemented as an application schema of the Geography Markup Language version 3.2.1, making use of the OGC Observations & Measurements standards.\r\nWaterML2.0 is designed as an extensible schema to allow encoding of data to be used in a variety of exchange scenarios. Example areas of usage are: exchange of data for operational hydrological monitoring programs; supporting operation of infrastructure (e.g. dams, supply systems); cross-border exchange of observational data; release of data for public dissemination; enhancing disaster management through data exchange; and exchange in support of national reporting. \r\nThe core aspect of the model is in the correct, precise description of time series. Interpretation of time series relies on understanding the nature of the process that generated them. This standard provides the framework under which time series can be exchanged with appropriate metadata to allow correct machine interpretation and thus correct use for further analysis. Existing systems should be able to use this model as a conceptual 'bridge' between existing schema or systems, allowing consistency of the data to maintained.\r\n" + "@value": "The Testbed-13 Earth Observation Clouds (EOC) effort supports the development of ESA’s Thematic Exploitation Platforms (TEP) by exercising envisioned workflows for data integration and processing that are deployed in multiple clouds. The Application Deployment & Execution Service OGC Engineering Report (ER) identifies the Application Programming Interface (API) for delivering all functionality provided to realize the testbed scenario.\r\n\r\nThis ER will list the requirements fulfilled by Cloud APIs in order to allow an automation of the application package deployment and execution workflow and capture implementation process experiences.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79496,35 +79287,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-126r3" + "@value": "17-024" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® WaterML 2.0: Part 1- Timeseries" + "@value": "OGC Testbed-13: Application Deployment and Execution Service Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-069r3", + "@id": "http://www.opengis.net/def/docs/21-013", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-10-07" + "@value": "2021-05-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Clemens Portele, Panagiotis (Peter) A. Vretanos, Charles Heazel" + "@value": "Robert Thomas, Josh Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -79534,27 +79325,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/17-069r3/17-069r3.html" + "@id": "https://docs.ogc.org/per/21-013.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-069r3" + "@value": "Modernizing SDI: Enabling Data Interoperability for Regional Assessments and Cumulative Effects CDS" }, { "@language": "en", - "@value": "OGC API - Features - Part 1: Core" + "@value": "21-013" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks.\r\n\r\nThe OGC API family of standards is organized by resource type. This standard specifies the fundamental API building blocks for interacting with features. The spatial data community uses the term 'feature' for things in the real world that are of interest." + "@value": "This engineering report (ER) presents the results of a Concept Development Study (CDS) on Modernizing Spatial Data Infrastructure (SDI), sponsored by Natural Resources Canada, executed by the Open Geospatial Consortium (OGC). The focus of this study was to understand how to best support the modernization of SDI(s) by enabling increased data interoperability for Regional Assessments (RA) and Cumulative Effects (CE), to advance the understanding of stakeholder issues, and serve stakeholders’ needs in these contexts. The study was completed through stakeholder engagements including an open Request for Information (RFI) that gathered external international positions and opinions on the optimal setup and design of a modernized SDI. In addition, a stakeholder Modernizing SDI Workshop was also employed providing in depth information on requirements and issues related to stakeholders, architecture, data, and standards of current and future SDI.\r\n\r\nThe RFI and workshop also gathered information and provided insight on the current state of SDIs to better support governments, agencies, non-governmental organizations and citizens, unlocking the full societal and economic potential of the wealth of data at national, regional and/or local levels.\r\n\r\nThe ER presents an analysis of the RFI and Modernizing SDI Workshop responses and interactions, providing in-depth information on requirements and issues related to stakeholders, architecture, data, standards of current and possible future SDI modernization. All RFI and workshop responses will contribute to SDI modernization efforts moving forward and help to assess interoperability, availability and usability of geospatial Web services and tools across different types of spatial data uses. In addition, the report identifies gaps, and defines core components of a possible future SDI.\r\n\r\nThe outflow of this report may be used to help define reference use-cases and scenarios for possible future research and follow-on OGC Innovation Program activities." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79565,35 +79356,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-069r3" + "@value": "21-013" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Features - Part 1: Core" + "@value": "Modernizing SDI: Enabling Data Interoperability for Regional Assessments and Cumulative Effects CDS" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-058", + "@id": "http://www.opengis.net/def/docs/05-078r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-11-08" + "@value": "2007-08-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Leonard Daly, Rollin Phillips" + "@value": "Markus Lupp" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -79603,27 +79394,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-058.html" + "@id": "https://portal.ogc.org/files/?artifact_id=22364" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-058" + "@value": "05-078r4" }, { "@language": "en", - "@value": "Interoperable Simulation and Gaming Sprint Year 2 Engineering Report" + "@value": "Styled Layer Descriptor Profile of the Web Map Service Implementation Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Interoperable Simulation and Gaming Year 2 Sprint advanced the use of relevant OGC and Khronos Group [1] standards in the modeling, simulation, and training communities through capability development, compatibility testing, and gap analysis. Of particular interest was the use of glTF models, game engines, and 3rd-party mobile device libraries for the display and interaction with data using OGC APIs." + "@value": "The OpenGIS® Styled Layer Descriptor (SLD) Profile of the OpenGIS® Web Map Service (WMS) Encoding Standard [http://www.opengeospatial.org/standards/wms ] defines an encoding that extends the WMS standard to allow user-defined symbolization and coloring of geographic feature[http://www.opengeospatial.org/ogc/glossary/f ] and coverage[http://www.opengeospatial.org/ogc/glossary/c ] data. \r\n\r\nSLD addresses the need for users and software to be able to control the visual portrayal of the geospatial data. The ability to define styling rules requires a styling language that the client and server can both understand. The OpenGIS® Symbology Encoding Standard (SE) [http://www.opengeospatial.org/standards/symbol] provides this language, while the SLD profile of WMS enables application of SE to WMS layers using extensions of WMS operations. Additionally, SLD defines an operation for standardized access to legend symbols.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79634,35 +79425,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-058" + "@value": "05-078r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Interoperable Simulation and Gaming Sprint Year 2 Engineering Report" + "@value": "OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-122", + "@id": "http://www.opengis.net/def/docs/21-074", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-10-13" + "@value": "2022-05-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ben Domenico" + "@value": "Samantha Lavender, Andrew Lavender" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/ug" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -79672,27 +79463,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=35505" + "@id": "https://docs.ogc.org/guides/21-074.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CF-netCDF Encoding Specification" + "@value": "OGC Disaster Pilot: User Readiness Guide" }, { "@language": "en", - "@value": "09-122" + "@value": "21-074" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/ug" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "NetCDF (network Common Data Form) is a data model for array-oriented scientific data, a freely distributed collection of access libraries implementing support for that data model, and a machine-independent format. Together, the interfaces, libraries, and format support the creation, access, and sharing of scientific data." + "@value": "The OGC Disaster Pilot 2021 initiative brought differing technologies together through multiple participants, allowing the future development of a robust solution with no single-point weaknesses. This Guide supports data providers in preparing and coordinating with others to leverage standards-based cloud computing platforms to support disaster management and response efforts. Geospatial data is acquired from multiple sources, including Earth Observation satellites, and converted to Decision Ready Information and indicators (DRI) from Analysis Ready Data and datasets (ARD) alongside recipes." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79703,30 +79494,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-122" + "@value": "21-074" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CF-netCDF Encoding Specification" + "@value": "OGC Disaster Pilot: User Readiness Guide" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-142", + "@id": "http://www.opengis.net/def/docs/21-077", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-09-17" + "@value": "2022-05-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Rob Atkinson" + "@value": "Taehoon Kim, Wijae Cho, Kyoung-Sook Kim" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -79741,17 +79532,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://www.w3.org/TR/qb4st/" + "@id": "https://docs.ogc.org/dp/21-077.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-142" + "@value": "The HDF5 profile for labeled point cloud data" }, { "@language": "en", - "@value": "QB4ST: RDF Data Cube extensions for spatio-temporal components" + "@value": "21-077" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -79761,7 +79552,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes an extension to the existing RDF Data Cube ontology to support specification of key metadata required to interpret spatio-temporal data. The RDF Data Cube defines CodedProperties, which relate to a reference system based on a list of terms, QB4ST provides generalized support for numeric and other ordered references systems, particularly Spatial Reference Systems and Temporal Reference Systems. Although RDF Data Cube supports AttributeProperties for metadata of individual observations, the requirement is to specify such metadata per property, rather than for each observation, and thus allow different properties to use different spatial or temporal reference systems. QB4ST also provides for such properties to be defined for a ComponentProperty, or defined at the time of referencing that ComponentProperty in a ComponentSpecification. QB4ST is thus aimed at improving the scope and consistency of dataset metadata, and hence discovery and interpretation of spatio-temporal data through its spatio-temporal reference system and bounding values." + "@value": "Point cloud data are unstructured three-dimensional sample points to express the basic shape of objects and spaces. However, it is challenging to automatically generate continuous surfaces and infer semantic structures, such as cars, trees, buildings and roads, from a dataset of point clouds generated by a sensor. The understanding of the semantic structures is essential for recording geospatial information. Despite the good performance of deep learning-based approaches in understanding point clouds, their target coverage is still limited by the lack of training datasets that include semantic labels. This discussion paper addresses data formats to share a Labeled Point Cloud (LPC), in which point-level semantic information is annotated to each point.\r\n\r\nCreating LPCs manually or semi-manually is a time-consuming task. Therefore, sharing LPCs in an open standard format is becoming increasingly important for the development of more advanced deep learning algorithms for object detection, semantic segmentation, and instance segmentation. Even though several data formats are used to distribute LPC, there is a variety to represent the semantic information depending on distributors or domains. This discussion paper analyzes three popular formats of ASCII text, PLY, and LAS, for supporting LPC and finally proposes a practice to effectively apply HDF5 to facilitate the sharing and importing of LPC datasets." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79772,35 +79563,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-142" + "@value": "21-077" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "QB4ST: RDF Data Cube extensions for spatio-temporal components" + "@value": "The HDF5 profile for labeled point cloud data" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-113r1", + "@id": "http://www.opengis.net/def/docs/05-084", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-11-23" + "@value": "2006-05-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Google, Galdos" + "@value": "Vincent Delfosse" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -79810,27 +79601,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=23689" + "@id": "https://portal.ogc.org/files/?artifact_id=12597" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "KML 2.2 Reference - An OGC Best Practice" + "@value": "05-084" }, { "@language": "en", - "@value": "07-113r1" + "@value": "Catalog 2.0 Accessibility for OWS3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "KML is a file format used to display geographic data in an Earth browser, such as Google Earth, Google Maps, and Google Maps for Mobile. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard." + "@value": "The OGC Catalog-Web Profile is a complex specification that implies usage of many concepts, such as ressources, metadata, registry, registry information model, harvesting, etc. This document is a user-friendly introduction to these concepts. It will help the understanding of the Catalog specification in general and of the Catalog Web profile with ebRIM in particular." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79841,35 +79632,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-113r1" + "@value": "05-084" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "KML 2.2 Reference - An OGC Best Practice" + "@value": "Catalog 2.0 Accessibility for OWS3" } ] }, { - "@id": "http://www.opengis.net/def/docs/24-025", + "@id": "http://www.opengis.net/def/docs/22-023r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-07-02" + "@value": "2023-07-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carsten Rönsdorf, Fabrice Servant, H.C. Gruler, Nick Giannias, Kyoungsook Kim, Zubran Soleiman, Dim" + "@value": "Sergio Taleisnik" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -79879,27 +79670,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/24-025.html" + "@id": "https://docs.ogc.org/per/22-023r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "24-025" + "@value": "22-023r2" }, { "@language": "en", - "@value": "Urban Digital Twins: Integrating Infrastructure, natural environment and people" + "@value": "Testbed-18: Features Filtering Summary Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This position paper is aimed at city officials and domain professionals working in an urban data context. Its goal is to clarify the concept of Urban Digital Twins (UDT) and to position it in regards of Digital Twins in general as well as the emerging Metaverse. \r\n\r\nOverall, the UDT concept is an approach to understand characteristics and processes of the built environment at the scale of a city. Between climate change and various demographics, dynamic cities are facing challenges that are becoming more complex to solve. Most of the time solutions have to be imagined with a system of systems approach and cannot be solved in silos.\r\n\r\nThe paper represents the current state of the discussion about UDTs in the Open Geospatial Consortium (OGC), a geospatial community and standards organization. \r\n\r\nAround 3 use cases, climate change adaptation, urban transformation, and urban air mobility, this paper identifies benefits of using a UDT and explain the role of Geospatial Information (GI) and how it can contribute to an UDT.\r\n\r\nUDTs is a digital representation of the city where elected representatives and professional stakeholders can access and contribute to a common reference model to collaborate, achieving positive outcomes for the citizens. UDTs reveal insights at the intersection of the natural and built environments and human activities. They provide the means of enabling simulation scenarios and plan possible interventions as well as tracking measurable evidence of any changes in the real world. In a mature state, UDTs will establish effective feedback loops between the virtual and the true, physical environments. \r\n\r\nFrom discussions with elected representatives, professionals, and also based on OGC member experience on projects, it is acknowledged that the process of building an UDT might seem daunting (as outlined in the paper by [Lei, 2023]: Challenges of urban digital twins: A systematic review and a Delphi expert survey).\r\n\r\nThis paper presents a pragmatic approach based on OGC standards for each use case, building on location and GI as the foundation. This approach calls for an effective data strategy and suggests that a project-based approach with a vision of building a UDT is the most efficient path.\r\n\r\nThis concept of UDT, although often mentioned in the media, is still fairly new in practice and the governance of that type of platform is still a challenge. OGC is keen on supporting and collaborating on projects to help create the best practices on that matter." + "@value": "This OGC Testbed-18 (TB-18) Features Filtering Summary Engineering Report (ER) summarizes the implementations, findings, and recommendations that emerged from the efforts to better understand the current OGC API-Features filtering capabilities and limitations and how filtering can be decoupled from data services.\r\n\r\nThis ER describes:\r\n\r\n*\ttwo façades built to interface SWIM services and serve aviation data through APIs (built with OGC API Standards) including basic filtering capabilities;\r\n*\tthe two filtering services built to consume SWIM data and serve it through OGC based APIs featuring advanced filtering mechanism;\r\n*\tthe client application built to interface with the filtering services; and\r\n*\tthe developer client built to define filter statements that can be expressed in a machine-readable way and exchanged with the filtering service." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79910,35 +79701,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "24-025" + "@value": "22-023r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Urban Digital Twins: Integrating Infrastructure, natural environment and people" + "@value": "Testbed-18: Features Filtering Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-002r8", + "@id": "http://www.opengis.net/def/docs/13-039", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-05-07" + "@value": "2014-12-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Craig Bruce" + "@value": "Nicolas Fanjeau, Sebastian Ulrich" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -79948,27 +79739,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1386" + "@id": "https://docs.ogc.org/bp/13-039/13-039.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "03-002r8" + "@value": "OpenSearch Extension for Earth Observation Satellite Tasking: Best Practice" }, { "@language": "en", - "@value": "Binary-XML Encoding Specification" + "@value": "13-039" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies a binary encoding format for the efficient representation of XML data, especially scientific data that is characterized by arrays of numbers. This encoding format is applicable to any application that uses XML format." + "@value": "This document provides a specification of an OpenSearch extension for Earth Observation Satellites Tasking.\r\n\r\nThis OGC Best Practice is intended to provide a very simple way to task Earth Observation (EO) satellites sensors, to allow simple syndication between, and to provide a basic federated query of related sensors, whereby a single client can query several instances and present a collection of future acquisition as one set.\r\n\r\nThis document is the result of work undertaken within the European Space Agency (ESA) Heterogeneous Mission Accessibility for Science (HMA-S) project funded by ESA the Long Term Data Preservation (LTDP) program.\r\n\r\nThe document was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative (see ‘Normative References’ section) related projects." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -79979,35 +79770,69 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-002r8" + "@value": "13-039" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Binary-XML Encoding Specification" + "@value": "OGC® OpenSearch Extension for Earth Observation Satellite Tasking: Best Practice" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-010", + "@id": "http://www.opengis.net/def/doc-type/pc/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Profile Corrigendum - Approved" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Profile Corrigendum - Approved" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/06-111" + }, + { + "@id": "http://www.opengis.net/def/docs/06-113" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Profile Corrigendum - Approved" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/18-036r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-06-19" + "@value": "2019-02-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Doug Nebert" + "@value": "Benjamin Pross, Arnaud Cauchy" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -80017,27 +79842,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20561" + "@id": "https://docs.ogc.org/per/18-036r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-010" + "@value": "WPS-T Engineering Report" }, { "@language": "en", - "@value": "Revision Notes for Corrigendum for OpenGIS 07-006: Catalogue Services, Version 2.0.2" + "@value": "18-036r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a corrigendum for OGC Document 04-021r3. All changes described herein are published in OGC Document 07-006r1." + "@value": "This Engineering Report describes a proposed transactional extension for the OGC Web Processing Service (WPS) 2.0 standard including Key-Value Pair (KVP) and Extensible Markup Language (XML) bindings and recommendations for a process deployment profile for BPMN (Business Process Model and Notation)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -80048,35 +79873,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-010" + "@value": "18-036r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Revision Notes for Corrigendum for OpenGIS 07-006: Catalogue Services, Version 2.0.2" + "@value": "OGC Testbed-14: WPS-T Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-014r5", + "@id": "http://www.opengis.net/def/docs/19-011r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-09-05" + "@value": "2020-11-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed, Tamrat Belayneh" + "@value": "Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker, Hye-Young Kan" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -80086,27 +79911,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/17-014r5/17-014r5.html" + "@id": "https://docs.ogc.org/is/19-011r4/19-011r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-014r5" + "@value": "OGC® IndoorGML 1.1" }, { "@language": "en", - "@value": "Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification" + "@value": "19-011r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files.\r\n\r\n \r\n\r\nThe delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3d datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types." + "@value": "This OGC® IndoorGML standard specifies an open data model and XML schema of indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modeling indoor spaces for navigation purposes." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -80117,35 +79942,69 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-014r5" + "@value": "19-011r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification" + "@value": "OGC® IndoorGML 1.1" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-025r2", + "@id": "http://www.opengis.net/def/doc-type/ipr/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Interoperability Program Report" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Interoperability Program Report" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/02-028" + }, + { + "@id": "http://www.opengis.net/def/docs/02-019r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Interoperability Program Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/10-155", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-10" + "@value": "2010-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos" + "@value": "Andreas Matheus" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -80155,27 +80014,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/09-025r2/09-025r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=40144" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-025r2" + "@value": "OWS-7 - Towards secure interconnection of OGC Web Services with SWIM" }, { "@language": "en", - "@value": "Web Feature Service 2.0 Interface Standard - With Corrigendum" + "@value": "10-155" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Web Feature Service (WFS) represents a change in the way geographic information is created, modified and exchanged on the Internet. Rather than sharing geographic information at the file level using File Transfer Protocol (FTP), for example, the WFS offers direct fine-grained access to geographic information at the feature and feature property level.\r\n\r\nThis International Standard specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored, parameterized query expressions.\r\n\r\nDiscovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers.\r\n\r\nQuery operations allow features or values of feature properties to be retrieved from the underlying data store based upon constraints, defined by the client, on feature properties.\r\n\r\nLocking operations allow exclusive access to features for the purpose of modifying or deleting features.\r\n\r\nTransaction operations allow features to be created, changed, replaced and deleted from the underlying data store.\r\n\r\nStored query operations allow clients to create, drop, list and described parameterized query expressions that are stored by the server and can be repeatedly invoked using different parameter values.\r\n\r\nThis International Standard defines eleven operations:\r\n\r\nGetCapabilities (discovery operation)\r\nDescribeFeatureType (discovery operation)\r\nGetPropertyValue (query operation)\r\nGetFeature (query operation)\r\nGetFeatureWithLock (query & locking operation)\r\nLockFeature (locking operation)\r\nTransaction (transaction operation)\r\nCreateStoredQuery (stored query operation)\r\nDropStoredQuery (stored query operation)\r\nListStoredQueries (stored query operation)\r\nDescribeStoredQueries (stored query operation)\r\nIn the taxonomy of services defined in ISO 19119, the WFS is primarily a feature access service but also includes elements of a feature type service, a coordinate conversion/transformation service and geographic format conversion service." + "@value": "This Engineering Report provides guidance and generate action items for the OGC standardization effort to properly enable security in the near future such that a seamless, interoperable but secure interconnection between OGC Web Services and FUSE ESB technology stack as selected by use in the System Wide Information Management (SWIM) System of the US Federal Aviation Administration (FAA) can be achieved." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -80186,35 +80045,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-025r2" + "@value": "10-155" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Web Feature Service 2.0 Interface Standard - With Corrigendum" + "@value": "OWS-7 - Towards secure interconnection of OGC Web Services with SWIM" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-046r1", + "@id": "http://www.opengis.net/def/docs/16-009r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-01-08" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Scott Serich" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -80224,27 +80083,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-046r1.html" + "@id": "https://docs.ogc.org/bp/16-009r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-046r1" + "@value": "16-009r5" }, { "@language": "en", - "@value": "OGC Testbed-15: Quebec Model MapML Engineering Report" + "@value": "Volume 6: OGC CDB Rules for Encoding Data using OpenFlight" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed-15 Engineering Report (ER) describes the Map Markup Language (MapML) enabled client component implementation for the Quebec Lake-River Differentiation Model in the Machine Learning (ML) task of Open Geospatial Consortium (OGC) Testbed-15 (T-15). This ER presents the MapML parsing capabilities that were developed to illustrate the outputs of a ML model to delineate lake and river features from an undifferentiated waterbody vector dataset in Québec, Canada. Client data was accessed through an OGC Web Processing Service (WPS) interface in coordination with an OGC API - Features implementation." + "@value": "This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of that document for a general overview." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -80255,35 +80114,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-046r1" + "@value": "16-009r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Quebec Model MapML Engineering Report" + "@value": "Volume 6: OGC CDB Rules for Encoding Data using OpenFlight" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-132r1", + "@id": "http://www.opengis.net/def/docs/17-038", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-10-02" + "@value": "2018-01-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas Usländer (Ed.)" + "@value": "Jeff Harrison" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -80293,27 +80152,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=35888" + "@id": "https://docs.ogc.org/per/17-038.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Specification of the Sensor Service Architecture (SensorSA)" + "@value": "Testbed-13: Fit-for-Purpose Engineering Report" }, { "@language": "en", - "@value": "09-132r1" + "@value": "17-038" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Specification of a generic service-oriented architecture integrating the access to, the management and the processing of sensor-related information based upon the emerging standards of the Open geospatial Consortium (OGC), and resulting from the requirements analysis of diverse application domains such as maritime risk management, observation of geo-hazards and monitoring of air quality." + "@value": "The objective of the Fit for Purpose (FFP) effort in Testbed 13 was to develop and test filters and encodings in a platform that can ease the work of end-users, especially those who are not expert in dealing with geospatial data and satellite imagery. The platform was demonstrated in a scenario that showed how these filters can enable information exchange for humanitarian relief and analysis of mass movement of populations.\r\n\r\nThis section provides a summary of the interoperability tools and practices used by Testbed 13 participants in this platform. It includes descriptions and testing results of filters and encodings to help simplify access to satellite imagery. This technology was tested in a scenario that showed how OGC-based services, encodings, filters and applications can help coordinate humanitarian relief activities among nations and organizations." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -80324,35 +80183,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-132r1" + "@value": "17-038" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Specification of the Sensor Service Architecture (SensorSA)" + "@value": "OGC Testbed-13: Fit-for-Purpose Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-021", + "@id": "http://www.opengis.net/def/docs/18-004r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-01-20" + "@value": "2018-07-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -80362,27 +80221,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1328" + "@id": "https://docs.ogc.org/wp/18-004r1/18-004r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Integrated Client for Multiple OGC-compliant Services" + "@value": "The Role of Geospatial in Edge-Fog-Cloud Computing - An OGC White Paper" }, { "@language": "en", - "@value": "03-021" + "@value": "18-004r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/techpaper" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Provides an overview of the requirements, architecture, and design of Integrated Clients developed during the OGC Open Web Services" + "@value": "“The cloud is dead – long live the cloud!” so begins an IEC White paper on Edge Intelligence.[1] The IEC White Paper continues that “Driven by the internet of things (IoT), a new computing model – edge-cloud computing – is currently evolving, which involves extending data processing to the edge of a network in addition to computing in a cloud or a central data centre. Edge-Fog-Cloud computing models operate both on premise and in public and private clouds, including via devices, base stations, edge servers, micro data centres and networks.” " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -80393,35 +80252,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-021" + "@value": "18-004r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Integrated Client for Multiple OGC-compliant Services" + "@value": "The Role of Geospatial in Edge-Fog-Cloud Computing - An OGC White Paper" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-030", + "@id": "http://www.opengis.net/def/docs/16-010r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-03-20" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Scarponcini" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -80431,27 +80290,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://www.iso.org/standard/32566.html" + "@id": "https://docs.ogc.org/bp/16-010r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-030" + "@value": "16-010r5" }, { "@language": "en", - "@value": "Topic 19 - Geographic information - Linear referencing" + "@value": "Volume 7: OGC CDB Data Model Guidance (Best Practice)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/as" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Same as ISO IS 19148: 2012. Download at http://www.iso.org" + "@value": "This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -80462,256 +80321,99 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-030" + "@value": "16-010r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 19 - Geographic information - Linear referencing" + "@value": "Volume 7: OGC CDB Data Model Guidance (Best Practice)" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/d-dp/collection", + "@id": "http://www.opengis.net/def/docs/16-048r1", "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ - { - "@value": "Documents of type Discussion Paper - deprecated " - } + "http://www.w3.org/2004/02/skos/core#Concept" ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "http://purl.org/dc/terms/created": [ { - "@value": "Documents of type Discussion Paper - deprecated " + "@type": "xsd:date", + "@value": "2017-03-10" } ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs" + "@value": "Andreas Matheus" } ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/08-129" - }, - { - "@id": "http://www.opengis.net/def/docs/04-049r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-109r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-028" - }, - { - "@id": "http://www.opengis.net/def/docs/06-054r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-013" - }, - { - "@id": "http://www.opengis.net/def/docs/04-038r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-027r2" - }, - { - "@id": "http://www.opengis.net/def/docs/04-013r4" - }, - { - "@id": "http://www.opengis.net/def/docs/09-142r1" - }, - { - "@id": "http://www.opengis.net/def/docs/07-018" - }, - { - "@id": "http://www.opengis.net/def/docs/05-019" - }, - { - "@id": "http://www.opengis.net/def/docs/06-093" - }, - { - "@id": "http://www.opengis.net/def/docs/06-131" - }, - { - "@id": "http://www.opengis.net/def/docs/02-061r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-089r1" - }, - { - "@id": "http://www.opengis.net/def/docs/01-022r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-091r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-078" - }, - { - "@id": "http://www.opengis.net/def/docs/01-036" - }, - { - "@id": "http://www.opengis.net/def/docs/05-035r1" - }, - { - "@id": "http://www.opengis.net/def/docs/06-126" - }, - { - "@id": "http://www.opengis.net/def/docs/05-107" - }, - { - "@id": "http://www.opengis.net/def/docs/08-128" - }, - { - "@id": "http://www.opengis.net/def/docs/06-055r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-025r3" - }, - { - "@id": "http://www.opengis.net/def/docs/03-064r1" - }, - { - "@id": "http://www.opengis.net/def/docs/08-008r1" - }, - { - "@id": "http://www.opengis.net/def/docs/01-024r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-088r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-088r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-066" - }, - { - "@id": "http://www.opengis.net/def/docs/15-074r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-169" - }, - { - "@id": "http://www.opengis.net/def/docs/04-040" - }, - { - "@id": "http://www.opengis.net/def/docs/05-112" - }, - { - "@id": "http://www.opengis.net/def/docs/06-080r1" - }, - { - "@id": "http://www.opengis.net/def/docs/02-027" - }, - { - "@id": "http://www.opengis.net/def/docs/06-035r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-021" - }, - { - "@id": "http://www.opengis.net/def/docs/05-013" - }, - { - "@id": "http://www.opengis.net/def/docs/01-044r2" - }, - { - "@id": "http://www.opengis.net/def/docs/12-028" - }, - { - "@id": "http://www.opengis.net/def/docs/07-057r2" - }, - { - "@id": "http://www.opengis.net/def/docs/03-031" - }, - { - "@id": "http://www.opengis.net/def/docs/14-004" - }, - { - "@id": "http://www.opengis.net/def/docs/05-087r3" - }, - { - "@id": "http://www.opengis.net/def/docs/05-007" - }, - { - "@id": "http://www.opengis.net/def/docs/01-013r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-007r2" - }, - { - "@id": "http://www.opengis.net/def/docs/02-026r1" - }, - { - "@id": "http://www.opengis.net/def/docs/05-057r3" - }, - { - "@id": "http://www.opengis.net/def/docs/06-080" - }, - { - "@id": "http://www.opengis.net/def/docs/07-028r1" - }, - { - "@id": "http://www.opengis.net/def/docs/03-002r8" - }, - { - "@id": "http://www.opengis.net/def/docs/06-166" - }, - { - "@id": "http://www.opengis.net/def/docs/06-057r1" - }, + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/05-077" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/03-008r2" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/04-017r1" - }, + "@id": "https://docs.ogc.org/per/16-048r1.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/02-039r1" + "@language": "en", + "@value": "16-048r1" }, { - "@id": "http://www.opengis.net/def/docs/07-024" - }, + "@language": "en", + "@value": "Testbed-12 OWS Common Security Extension ER" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/02-026r4" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/11-039r2" - }, + "@value": "The OGC suite of standards address the interoperable exchange of geographic information. The Web Service Implementation Standards define the discovery, delivery, and processing services that make information exchange possible. Common aspects of those Web Service standards have been collected into the OGC Web Services Common standard. While there are multiple versions of OWS Common, and flexibility in how it is applied, this combination of standards does enable interoperability.\r\n\r\nHowever, OWS Common neglected to address security. As soon as a service endpoint (an OGC Web Service instance) is secured, there is no guarantee of interoperability.\r\n\r\nThe OWS Common - Security Standards Working Group (SWG) was approved by the TC in September 2015 (http://www.opengeospatial.org/projects/groups/comsecurityswg). It held its first meeting during the December 2015 TC meetings. The objective of this SWG to define an extension to the existing OWS Common to ensure interoperability between a secured service instance and client. This OWS Common Security Extension adds content to the standard regarding the implementation of security controls in such a way as to preserve interoperability. These additions will be in two areas. The first extension will provide more detail on the use of the HTTP protocol, particularly as it related to security controls. The second extension will address discovery and negotiation of security controls. This will provide an annotation model for the Capabilities document to enable a service provider to specify the security implemented at a service instance (endpoint).\r\n\r\nThis ER shall serve as the technical background to the OWS Common - Security SWG to ensure that the standard that is to be created is comprehensive and suitable for all OGC Web Services standards, to overcome the interoperability hurdle, and - at the same time - maintain backwards compatibility.\r\n\r\n" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/08-167r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/07-038" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "16-048r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type Discussion Paper - deprecated " + "@language": "en", + "@value": "Testbed-12 OWS Common Security Extension ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-036r1", + "@id": "http://www.opengis.net/def/docs/18-074", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-06-30" + "@value": "2019-02-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Christian Autermann" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -80726,17 +80428,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-036r1.html" + "@id": "https://docs.ogc.org/per/18-074.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-036r1" + "@value": "GeoPackage 1.2 Vector Tiles Extensions Engineering Report" }, { "@language": "en", - "@value": "Testbed-12 Big Data Database Engineering Report" + "@value": "18-074" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -80746,7 +80448,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The amount of (geospatial) data collected and transferred is rapidly increasing. The purpose of this ER is to describe options and recommendations for the delivery of large amounts of data as database delivery. This ER therefore describes and evaluates different aspects of this challenge:\r\n\r\nData management: How to organize large amounts of data so that it can be efficiently accessed through OGC service interfaces?\r\n\r\nEncoding: Transferring large amounts of vector data in XML based formats (e.g. GML, O&M) leads to specific challenges as the parsing of large XML files is often problematic.\r\n\r\nAvailable implementation: Several software packages exist to handle large amounts of geospatial data. We will investigate to which these approaches are in-line with OGC standards or how standards compliance could be achieved.\r\n\r\nThe evaluation and findings in the related Big Data Tile Database Implementation are documented in this ER as well. The objective of this ER is to provide recommendations of how the delivery of large amounts of raster data as database delivery can be considered within OGC specifications and future activities." + "@value": "Tiled feature data, colloquially referred to as 'vector tiles', can be used to optimize the delivery of vector data over the web. This data may subsequently be used to support visualization (particularly through maps) as well as limited analysis activities. One goal of the OGC Vector Tiles Pilot was to define candidate extensions to existing OGC standards as a way to advance the use of vector tiles technology as part of the OGC baseline. This Engineering Report (ER) describes a set of possible extensions to GeoPackage 1.2 that documents the mechanism to store and retrieve vector tiles in a GeoPackage. These extensions work together to enable a GeoPackage to act as a container format that can support visualization and analysis activities, even in a Denied, Degraded, Intermittent, or Limited Bandwidth (DDIL) environment.\r\n\r\nThe GeoPackage Vector Tiles extensions define the rules and requirements for encoding vector tiles in a GeoPackage data store. There are five draft extensions:\r\n\r\nThe Vector Tiles Extension provides vector tiles support through the GeoPackage tiles option.\r\n\r\nThe Mapbox Vector Tiles Extension allows the content of a tile Binary Large OBject (BLOB) to be a Mapbox Vector Tile as per version 2.1 of the Mapbox Vector Tile (MVT) specification [1].\r\n\r\nThe GeoJSON Vector Tiles Extension allows the content of each tile BLOB to be a GeoJSON file.\r\n\r\nThe OGC Web Services (OWS) Context Extension provides a way to store information describing a list of geospatial resources, including but not limited to maps, their layers, and the styles of those layers.\r\n\r\nThe Vector Tiles Attributes Extension allows attribute information for each feature to be stored in relational tables for more convenient querying.\r\n\r\nTo support vector tiles, a minimum of at least two extensions is required. The first extension enables vector tiles support. However, to be usable, an encoding format must be declared via either the second or third extension. The other extensions are purely optional.\r\n\r\nThese extensions, like all GeoPackage extensions, are intended to be transparent and to not interfere with GeoPackage-compliant, but non-supporting, software packages." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -80757,35 +80459,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-036r1" + "@value": "18-074" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Big Data Database Engineering Report" + "@value": "OGC Vector Tiles Pilot: GeoPackage 1.2 Vector Tiles Extensions Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-107", + "@id": "http://www.opengis.net/def/docs/07-144r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-01-31" + "@value": "2008-03-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas Uslander (Ed.)" + "@value": "Richard Martell" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -80795,27 +80497,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12574" + "@id": "https://portal.ogc.org/files/?artifact_id=27093" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-107" + "@value": "07-144r2" }, { "@language": "en", - "@value": "Reference Model for the ORCHESTRA Architecture" + "@value": "CSW-ebRIM Registry Service - Part 2: Basic extension package" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It contains a specification framework for the design of ORCHESTRA-compliant service networks and provides a platform-neutral specification of its information and service viewpoints." + "@value": "This OGC® document is a companion to the CSW-ebRIM catalogue profile (OGC 07-110r2). It specifies the content of the Basic extension package that shall be supported by all conforming services. The package includes extension elements of general utility that may be used to characterize a wide variety of geographic information resources, with a focus on service-oriented metadata management." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -80826,35 +80528,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-107" + "@value": "07-144r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Reference Model for the ORCHESTRA Architecture" + "@value": "CSW-ebRIM Registry Service - Part 2: Basic extension package" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-022r3", + "@id": "http://www.opengis.net/def/docs/16-105r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-02-04" + "@value": "2017-08-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Peter Axelsson, Lars Wikström" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -80864,27 +80566,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1324" + "@id": "https://portal.ogc.org/files/?artifact_id=75122" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Observations and Measurements" + "@value": "InfraGML 1.0: Part 5 - Railways - Encoding Standard" }, { "@language": "en", - "@value": "03-022r3" + "@value": "16-105r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes a framework and encoding for measurements and observations." + "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 5 addresses the Railway Requirements Class from LandInfra." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -80895,35 +80597,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-022r3" + "@value": "16-105r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Observations and Measurements" + "@value": "OGC InfraGML 1.0: Part 5 - Railways - Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-049r1", + "@id": "http://www.opengis.net/def/docs/19-069", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-04-22" + "@value": "2020-01-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Philippe Duschene, Jerome Sonnet" + "@value": "Joan Maso Pau" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -80933,27 +80635,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=9540" + "@id": "https://docs.ogc.org/per/19-069.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-049r1" + "@value": "19-069" }, { "@language": "en", - "@value": "WCS Change Request: Support for WSDL & SOAP" + "@value": "OGC Testbed-15: Maps and Tiles API Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS has been a precursor in Web Services matter, nevertheless, the pattern that has been used is not recognized by the industry as a standard XML Web Services. The work done during the the OpenGIS Web Service 2 initiative has provided the OpenGIS with interfaces that use the XML-related technologies supported by the industry, as SOAP for the communication protocol, WSDL for the interface description language, and UDDI for registering and searching services.\r\n\r\nThis change proposal present the required change to the WCS specification to interoperate with the industry standards.\r\n" + "@value": "In 2017 the OGC began a focused effort to develop Application Programming Interface (API) standards that support the Resource Oriented Architecture and make use of the OpenAPI specification. As part of this effort, this OGC Testbed 15 Engineering Report (ER) defines a proof-of-concept of an API specification for maps and tiles.\r\n\r\nThe OGC API Maps and Tiles draft specification described in this ER builds on the precedent of the OGC API - Features - Part 1: Core standard. The OGC API - Tiles draft specification describes a service that retrieves data representations as tiles, which are generally small compared with the geographic extent of the data. In the draft specification, the assumption is that tiles are organized into Tile Matrix Sets consisting of regular tile matrices available at different scales or resolutions. The OGC API – Tiles draft specification is described as a building block that can be plugged into an OGC API - Features service to retrieve tiled feature data (sometimes called vector tiles) or to an OGC API – Maps implementation to retrieve rendered tiles (sometimes called map tiles). In the future, the OGC API - Tiles draft specification could extend other specifications, one possible candidate being the emerging OGC API – Coverages draft specification.\r\n\r\nThe OGC API - Maps draft specification describes an API that presents data as maps by applying a style. These maps can be retrieved in a tiled structure (if OGC API - Tiles is approved as an OGC Implementation Standard) or as maps of any size generated on-the-fly. The OGC API - Maps draft specification implements some functionality, specified in the Web Map Tile Service (WMTS) 1.0 standard, related to the use of styles by using the Styles API draft specification that was developed in the Testbed-15 Open Portrayal Framework thread.\r\n\r\nThe draft Maps and Tiles API specifications are designed in a modular way. With the exception of the core requirements, the other conformance classes describe functionality that can be considered optional characteristics that can be combined by server implementations at will.\r\n\r\nAt the beginning of Testbed-15, the original proposed title for this ER was OGC Testbed-15: Web Map Tiling Service Draft Specification Engineering Report but in the course of the Testbed-15 that title was changed to better represent the content." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -80964,35 +80666,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-049r1" + "@value": "19-069" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "WCS Change Request: Support for WSDL & SOAP" + "@value": "OGC Testbed-15: Maps and Tiles API Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-044", + "@id": "http://www.opengis.net/def/docs/09-083r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-05-11" + "@value": "2018-04-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos" + "@value": "Adrian Custer" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81002,27 +80704,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=43999" + "@id": "https://portal.ogc.org/files/?artifact_id=71648" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-044" + "@value": "GeoAPI 3.0 Implementation Standard with corrigendum" }, { "@language": "en", - "@value": "OGC Geography Markup Language (GML) simple features profile Technical Note" + "@value": "09-083r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This technical note enhances the OGC GML simple features profile to include circles, circular arc, and corrects the annex numbering, and clarifies how to specify conformance classes." + "@value": "The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be used for the manipulation of geographic information structured following the specifications adopted by the Technical Committee211 of the International Organization for Standardization (ISO) and by the Open Geospatial Consortium (OGC). This standard standardizes the informatics contract between the client code which manipulates normalized data structures of geographic information based on the published API and the library code able both to instantiate and operate on these data structures according to the rules required by the published API and by the ISO and OGC standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81033,35 +80735,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-044" + "@value": "09-083r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Geography Markup Language (GML) simple features profile Technical Note" + "@value": "GeoAPI 3.0 Implementation Standard with corrigendum" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-156", + "@id": "http://www.opengis.net/def/docs/18-010r11", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-02-19" + "@value": "2023-08-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "George Percivall" + "@value": "Roger Lott" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81071,27 +80773,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51842" + "@id": "https://docs.ogc.org/is/18-010r11/18-010r11.pdf" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-156" + "@value": "Geographic information — Well-known text representation of coordinate reference systems" }, { "@language": "en", - "@value": "OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report" + "@value": "18-010r11" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Reference Architecture Profiler (RAP) Advisor™ is a web based application that\r\nrecommends OGC Standards and OGC Reference Model (ORM) Sections that are\r\nrelevant to a system development; such that a community of interest could derive and\r\nbuild a profile of suitable OGC standards to meet their specific needs. This Engineering\r\nReport contains the requirements, conceptual design, development methodology, and\r\nimplementation of the RAP Advisor.\r\nInitial development of the RAP Advisor™ was concurrent with the OGC Web Services\r\nTestbed, Phase 9 (OWS-9) with NGA sponsorship. During OWS-9 timeframe, key\r\nconcepts of the RAP Advisor were confirmed through prototyping. Future development\r\nis required to complete the functions and content of the Advisor." + "@value": "This Standard defines the structure and content of well-known text strings describing coordinate reference systems (CRSs) and coordinate operations between coordinate reference systems. It does not prescribe how implementations should read or write these strings.\r\nThis Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2019 including its amendments 1 and 2. It extends the WKT in OGC document 12-063r5 (ISO 19162) which was based on ISO 19111:2007 and ISO 19111-2:2009. That version consolidated several disparate versions of earlier WKT (so-called WKT1) and added the description of coordinate operations. \r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81102,35 +80804,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-156" + "@value": "18-010r11" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report" + "@value": "Geographic information — Well-known text representation of coordinate reference systems" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-089r1", + "@id": "http://www.opengis.net/def/docs/12-158", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-12-01" + "@value": "2013-06-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "Matthes Rieke" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81140,27 +80842,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12971" + "@id": "https://portal.ogc.org/files/?artifact_id=51817" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-089r1" + "@value": "12-158" }, { "@language": "en", - "@value": "Sensor Planning Service" + "@value": "OWS-9 Report on Aviation Performance Study" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Sensor Planning Service (SPS) is intended to provide a standard interface to collection assets (i.e., sensors, and other information gathering assets) and to the support systems that surround them. \r\nThe SPS is designed to be flexible enough to handle a wide variety of configurations." + "@value": "This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 9 (OWS-9). The report summarizes the work carried out regarding performance and endurance testing of data provision services, namely Web Feature Service and Event Service. More specifically, the report deals with the performance and endurance testing of data provision services commonly used within OWS Aviation testbeds. Test runs have been evaluated on the basis of well-defined, service-specific test models and the results are documented in detail. Furthermore, a description of the service test environment is documented in alignment with the overall OWS-9 service architecture" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81171,35 +80873,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-089r1" + "@value": "12-158" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Planning Service" + "@value": "OGC® OWS-9 Report on Aviation Performance Study" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-084", + "@id": "http://www.opengis.net/def/docs/06-028r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-08-01" + "@value": "2007-05-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Giuseppe Conti, Fabio Malabocchia, Ki-Joune Li, George Percivall, Kirk Burroughs, Stuart Strickland" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81209,27 +80911,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=68604" + "@id": "https://portal.ogc.org/files/?artifact_id=15588" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Benefits of Indoor Location - Use Case Survey of Lessons Learned and Expectations " + "@value": "06-028r3" }, { "@language": "en", - "@value": "16-084" + "@value": "Sensor Alert Service" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Indoor location technologies are enjoying and increasing market success. Technologies in the market have achieved maturity and have become a key driver for innovation and business activities in several value added scenarios, e.g. e-government services, eHealth, personal mobility, logistics, mobility, facility management, retail, to name but a few. This paper collects the results of a survey on the benefits of indoor location, which was jointly prepared and launched by OGC – the Open Geospatial Consortium, InLocation Alliance and i-locate project at the beginning of 2016. Overall, 153 survey responses were received from 33 countries. Responses were categorized in two areas: Client Organizations and Technology suppliers. The goal of the initiative was to acquire a broad view of the requirements and use cases emerging from the wider industrial and user community, beyond the memberships of the various organizations, in order to capture trends, challenges and opportunities, as well as trends and barriers to widespread use of indoor location technologies. This paper does not represent a view of the membership involved in the different organizations; instead, it provides the opportunity to capture recommendations of relevance for the industrial and standardization community these organizations represent. " + "@value": "The Sensor Alert Service (SAS) can be compared with an event notification system. The sensor node is the object of interest. Each node has to advertise its publications at a SAS (advertise). " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81240,35 +80942,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-084" + "@value": "06-028r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Benefits of Indoor Location - Use Case Survey of Lessons Learned and Expectations " + "@value": "Sensor Alert Service" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-014r3", + "@id": "http://www.opengis.net/def/docs/12-097", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-05-26" + "@value": "2013-03-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Stanislav Vanecek, Roger Moore" + "@value": "Jeff Harrison" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81278,27 +80980,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=59022" + "@id": "https://portal.ogc.org/files/?artifact_id=51998" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-014r3" + "@value": "OWS-9 Engineering Report - SSI - Bulk Data Transfer (GML Streaming)" }, { "@language": "en", - "@value": "Open Modelling Interface Interface Standard" + "@value": "12-097" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "

The purpose of the Open Modelling Interface (OpenMI) is to enable the runtime exchange of data between process simulation models and also between models and other modelling tools such as databases and analytical and visualization applications. Its creation has been driven by the need to understand how processes interact and to predict the likely outcomes of those interactions under given conditions. A key design aim has been to bring about interoperability between independently developed modelling components, where those components may originate from any discipline or supplier. The ultimate aim is to transform integrated modelling into an operational tool accessible to all and so open up the potential opportunities created by integrated modelling for innovation and wealth creation. \r\n

\r\n

\r\nThis document defines the requirements that a component must meet to achieve OpenMI compliance. These comprise: 1) a very thin core set of requirements covering the information and functions needed to establish a link and make an exchange between two components and 2) a set of optional extensions for handling more complex situations. The document does not describe how to implement the standard. This information together with a range of software tools for creating and running OpenMI-­‐compliant components are provided by the OpenMI Association and third-­‐party software vendors – visit www.openmi.org for further documentation.

\r\n

\r\npdf
\r\ndocx\r\n

" + "@value": "This document provides a description of the Bulk Data Transfer investigations related to Geography Markup Language (GML) streaming and feature data transportation implemented in the OGC OWS-9 test bed. \r\n\r\nThis document extends the concept of Bulk Data Transfer to the dissemination of large payloads consisting of geospatial data sets and/or collections of data sets between machines that are connected via a network.\r\n\r\nThis document also describes the delivery of large payloads consisting of geospatial data sets and/or collections of data sets to SpatiaLite/SQLite to store the data for use by mobile applications.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81309,35 +81011,183 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-014r3" + "@value": "12-097" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Open Modelling Interface Interface Standard" + "@value": "OWS-9 Engineering Report - SSI - Bulk Data Transfer (GML Streaming)" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-003r2", + "@id": "http://www.opengis.net/def/doc-type/d-is/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Implementation Specification - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Implementation Specification - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/99-049" + }, + { + "@id": "http://www.opengis.net/def/docs/06-083r8" + }, + { + "@id": "http://www.opengis.net/def/docs/04-095" + }, + { + "@id": "http://www.opengis.net/def/docs/03-065r6" + }, + { + "@id": "http://www.opengis.net/def/docs/05-134" + }, + { + "@id": "http://www.opengis.net/def/docs/06-103r3" + }, + { + "@id": "http://www.opengis.net/def/docs/01-068r3" + }, + { + "@id": "http://www.opengis.net/def/docs/07-026r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-025r1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-014r3" + }, + { + "@id": "http://www.opengis.net/def/docs/13-026r8" + }, + { + "@id": "http://www.opengis.net/def/docs/06-104r3" + }, + { + "@id": "http://www.opengis.net/def/docs/99-051" + }, + { + "@id": "http://www.opengis.net/def/docs/05-076" + }, + { + "@id": "http://www.opengis.net/def/docs/07-144r2" + }, + { + "@id": "http://www.opengis.net/def/docs/10-157r3" + }, + { + "@id": "http://www.opengis.net/def/docs/00-028" + }, + { + "@id": "http://www.opengis.net/def/docs/02-023r4" + }, + { + "@id": "http://www.opengis.net/def/docs/07-067r5" + }, + { + "@id": "http://www.opengis.net/def/docs/05-008c1" + }, + { + "@id": "http://www.opengis.net/def/docs/07-067r2" + }, + { + "@id": "http://www.opengis.net/def/docs/02-087r3" + }, + { + "@id": "http://www.opengis.net/def/docs/02-059" + }, + { + "@id": "http://www.opengis.net/def/docs/07-002r3" + }, + { + "@id": "http://www.opengis.net/def/docs/02-069" + }, + { + "@id": "http://www.opengis.net/def/docs/05-126" + }, + { + "@id": "http://www.opengis.net/def/docs/02-009" + }, + { + "@id": "http://www.opengis.net/def/docs/04-021r3" + }, + { + "@id": "http://www.opengis.net/def/docs/01-047r2" + }, + { + "@id": "http://www.opengis.net/def/docs/09-147r1" + }, + { + "@id": "http://www.opengis.net/def/docs/02-070" + }, + { + "@id": "http://www.opengis.net/def/docs/05-016" + }, + { + "@id": "http://www.opengis.net/def/docs/07-022r1" + }, + { + "@id": "http://www.opengis.net/def/docs/02-058" + }, + { + "@id": "http://www.opengis.net/def/docs/07-110r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-063r5" + }, + { + "@id": "http://www.opengis.net/def/docs/03-036r2" + }, + { + "@id": "http://www.opengis.net/def/docs/04-095c1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-110r3" + }, + { + "@id": "http://www.opengis.net/def/docs/10-126r3" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Implementation Specification - deprecated " + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/09-046r5", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-02-23" + "@value": "2019-10-31" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Simon Cox, Gobe Hobona" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/pol" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81347,27 +81197,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=72724" + "@id": "https://docs.ogc.org/pol/09-046r5.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-003r2" + "@value": "09-046r5" }, { "@language": "en", - "@value": "Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values" + "@value": "OGC Naming Authority – Policies and Procedures " } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/pol" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids key words." + "@value": "This document describes the procedures used by the OGC Naming Authority for the assignment and registration of OGC names." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81378,30 +81228,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-003r2" + "@value": "09-046r5" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values" + "@value": "OGC Naming Authority – Policies and Procedures " } ] }, { - "@id": "http://www.opengis.net/def/docs/10-090r3", + "@id": "http://www.opengis.net/def/docs/08-085r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-04-05" + "@value": "2014-09-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ben Domenico" + "@value": "Lucio Colaiacomo, Joan Masó, Emmanuel Devys" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -81416,17 +81266,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=43732" + "@id": "https://docs.ogc.org/is/08-085r4/08-085r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "10-090r3" + "@value": "GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core " }, { "@language": "en", - "@value": "Network Common Data Form (NetCDF) Core Encoding Standard version 1.0" + "@value": "08-085r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -81436,7 +81286,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the network Common Data Form (netCDF) core standard and extension mechanisms. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space and time-varying phenomena.\r\nNetCDF is a data model for array-oriented scientific data. A freely distributed collection of access libraries implementing support for that data model, and a machine-independent format are available. Together, the interfaces, libraries, and format support the crea-tion, access, and sharing of multi-dimensional scientific data.\r\n" + "@value": "This standard applies to the encoding and decoding of JPEG 2000 images that contain GML for use with geographic imagery.\r\n\r\nThis document specifies the use of the Geography Markup Language (GML) within the XML boxes of the JPEG 2000 data format and provides an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations. The document also specifies the encoding and packaging rules for GML use in JPEG 2000." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81447,35 +81297,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-090r3" + "@value": "08-085r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Network Common Data Form (NetCDF) Core Encoding Standard version 1.0" + "@value": "OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core " } ] }, { - "@id": "http://www.opengis.net/def/docs/01-037", + "@id": "http://www.opengis.net/def/docs/01-101", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-03-30" + "@value": "2001-05-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ron Lake" + "@value": "John Herring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81485,27 +81335,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1042" + "@id": "https://www.iso.org/standard/26012.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Location Organizer Folder" + "@value": "01-101" }, { "@language": "en", - "@value": "01-037" + "@value": "Topic 01 - Feature Geometry" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/d-as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "*RETIRED* The Location Organizer Folder (LOF) is a GML document that provides a structure for organizing the information related to a particular event or events of interest." + "@value": "Same as ISO 19107, available at http://www.iso.org." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81516,35 +81366,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-037" + "@value": "01-101" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Location Organizer Folder" + "@value": "Topic 1 - Feature Geometry" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-005r4", + "@id": "http://www.opengis.net/def/docs/08-134r11", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-02-08" + "@value": "2022-06-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Roger Lott" + "@value": "Gobe Hobona" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/pol" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81554,27 +81404,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/as/18-005r4/18-005r4.html" + "@id": "https://docs.ogc.org/pol/08-134r11.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "18-005r4" + "@value": "08-134r11" }, { "@language": "en", - "@value": "Topic 02 - Referencing by coordinates" + "@value": "Compliance Testing Program Policies & Procedures" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-as" + "@id": "http://www.opengis.net/def/doc-type/pol" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is identical in normative content with the latest edition (2019) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2019]." + "@value": "This document describes the Open Geospatial Consortium (OGC) Compliance Testing Program. The document describes the roles and responsibilities, compliance testing procedures, development of test packaging, and policies for developing and releasing the software used for testing for compliance to OGC Standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81585,35 +81435,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-005r4" + "@value": "08-134r11" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Topic 2 - Referencing by coordinates" + "@value": "Compliance Testing Program Policies & Procedures" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-002", + "@id": "http://www.opengis.net/def/docs/08-085r8", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-07-15" + "@value": "2018-08-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó and Raj Singh" + "@value": "Lucio Colaiacomo, Joan Masó, Emmanuel Devys, Eric Hirschorn" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81623,27 +81473,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=58965" + "@id": "https://docs.ogc.org/is/08-085r8/08-085r8.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "14-002" + "@value": "08-085r8" }, { "@language": "en", - "@value": "Testbed 10 Annotations Engineering Report" + "@value": "GML in JPEG 2000 (GMLJP2) Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report provides guidelines for dealing with geospatial\r\nannotations in OGC standards. It proposes a generic data model and a set of mappings\r\ninto different popular encodings This OGC® document is applicable to OWS context,\r\nGMLJP2 and any other standards that can require annotations." + "@value": "This OGC GML in JPEG 2000 (GMLJP2) Encoding Standard defines how the OGC/ISO Geography Markup Language (GML) standard is used within JPEG 2000 images and other gridded coverage data for adding geospatial content to imagery. Specifically, this OGC standard defines requirements for the encoding and decoding of JPEG 2000 images and other gridded coverage data that contain XML documents that use GML and GML-based schema.\r\nThis document defines the use of GML within the XML boxes of the JP2 and JPX file format for JPEG 2000 (extending the JP2 file format, as specified in [ISO 15444-1] and [ISO 15444-2] in Annexes M and N). Further, an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations is specified. The document also specifies the encoding and packaging rules for GML use in JPEG 2000.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81654,35 +81504,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-002" + "@value": "08-085r8" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed 10 Annotations Engineering Report" + "@value": "OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-013r4", + "@id": "http://www.opengis.net/def/docs/10-088r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-09-20" + "@value": "2014-04-15" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Reed" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81692,27 +81542,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=6944" + "@id": "https://portal.ogc.org/files/?artifact_id=50438" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-013r4" + "@value": "OWS-7 Schema Automation Engineering Report" }, { "@language": "en", - "@value": "A URN namespace for the Open Geospatial Consortium (OGC)" + "@value": "10-088r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC (such as OGC Standards, XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other documents). The formal Namespace identifier (NID) is ogc.\r\n " + "@value": "The capabilities of OGC’s KML 2.2 as a format for exchange and visualization of U.S. National System for Geospatial Intelligence (NSG) Application Schema (NAS) data is explored." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81723,35 +81573,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-013r4" + "@value": "10-088r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "A URN namespace for the Open Geospatial Consortium (OGC)" + "@value": "OGC® OWS-7 Schema Automation Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-042r3", + "@id": "http://www.opengis.net/def/docs/17-019", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-09-09" + "@value": "2018-01-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "James Tomkins, Dominic Lowe" + "@value": "Joan Maso" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81761,27 +81611,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/15-042r3/15-042r3.html" + "@id": "https://docs.ogc.org/per/17-019.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-042r3" + "@value": "Testbed-13: MapML Engineering Report" }, { "@language": "en", - "@value": "TimeseriesML 1.0 – XML Encoding of the Timeseries Profile of Observations and Measurements" + "@value": "17-019" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "TimeseriesML 1.0 defines an XML encoding that implements the OGC Timeseries Profile of Observations and Measurements [OGC 15-043r3], with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of data exchange requirements." + "@value": "This Engineering Report discusses the approach of Map Markup Language (MapML) and Map for HyperText Markup Language (Map4HTML) described in: https://github.com/Maps4HTML and supported by the community in https://www.w3.org/community/maps4html/. The objective of MapML is to define a hypermedia type for geospatial maps on the web that can be embedded in HyperText Markup Language (HTML) pages. MapML is needed because while Web browsers implement HTML and Scalable Vector Graphics (SVG), including the element, those implementations do not meet the requirements of the broader Web mapping community. The semantics of the HTML map element are incomplete or insufficient relative to modern Web maps and mapping in general. Currently, robust web maps are implemented by a variety of non-standard technologies. Web maps do not work without script support, making their creation a job beyond the realm of beginners' skill sets. In order to improve collaboration and integration of the mapping and Web communities, it is desirable to enhance or augment the functionality of the element in HTML to include the accessible user interface functions of modern web maps (e.g. panning, zooming, searching for, and zooming to, styling, identifying features’ properties, etc.), while maintaining a simple, declarative, accessible interface for HTML authors.\r\n\r\nThe objective of this Engineering Report is to explore how MapML can be harmonized with the OGC standards mainstream and contribute to the progress of the specification avoiding unnecessary duplication. In particular, the ER proposes Web Map Service (WMS) or Web Map Tile Service (WMTS) as services that can be used to deliver MapML documents with small modifications.\r\n\r\nAnother consideration on the ER is the inclusion of the time dimension and directions operation in MapML." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81792,35 +81642,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-042r3" + "@value": "17-019" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "TimeseriesML 1.0 – XML Encoding of the Timeseries Profile of Observations and Measurements" + "@value": "OGC Testbed-13: MapML Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-020r1", + "@id": "http://www.opengis.net/def/docs/09-001", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-01-26" + "@value": "2011-03-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Johannes Echterhoff, Clemens Portele" + "@value": "Johannes Echterhoff" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81830,27 +81680,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-020r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=38476" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-13: NAS Profiling Engineering Report" + "@value": "SWE Service Model Implementation Standard" }, { "@language": "en", - "@value": "17-020r1" + "@value": "09-001" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The National System for Geospatial-Intelligence (NSG) Application Schema (NAS) is an ISO 19109 compliant application schema that defines the conceptual model for identifying and encoding feature data in the U.S. National System for Geospatial-Intelligence (NSG). NGA utilizes the open source software tool ShapeChange as an integral piece in NAS development. This tool is used to take NAS-based UML models and create Extensible Markup Language (XML) and Resource Description Framework (RDF) based schemas. Testbed-12 began development of capabilities for extracting profiles supporting specific mission functions from the full NAS content. Testbed-13 further refined the approach to NAS Profiling by investigating how a specific profile (Urban Military Profile) can be processed in an automated way and used to derive implementation schemas for the OGC standards CDB and CityGML.\r\n\r\nThis OGC Engineering Report describes:\r\n\r\nThe specification of a NAS-based Military Urban Profile as a Unified Modeling Language (UML) model (chapter 5);\r\n\r\nHow mission-specific sub-profiles can be specified and maintained using ShapeChange and the new ShapeChange Profile Management Tool (chapter 6); and\r\n\r\nHow the model and profile information are processed to derive output for\r\n\r\na CDB data store (chapter 7, chapter 8) and\r\n\r\na CityGML Application Domain Extension (chapter 9).\r\n\r\nThis work provides insights into:\r\n\r\nThe requirements and constraints on managing profiles of complex ISO 19109 compliant application schemas such as the NAS; and\r\n\r\nUsing a model-driven approach to generate implementation schemas of an ISO 19109 compliant application schema profile for different environments.\r\n\r\nThe target audience of this document is anyone interested in these topics. The implementation environments discussed in this report are the OGC standards CDB and CityGML. The profiled application schema is the NAS.\r\n\r\nThis report assumes that readers are familiar with the key concepts and technologies discussed in this document. This document does not provide an introduction to them, but the table below provides a brief summary and pointers to more information." + "@value": "This standard currently defines eight packages with data types for common use across OGC Sensor Web Enablement (SWE) services. Five of these packages define operation request and response types. The packages are: 1.) Contents – Defines data types that can be used in specific services that provide (access to) sensors; 2.) Notification – Defines the data types that support provision of metadata about the notification capabilities of a service as well as the definition and encoding of SWES events; 3.) Common - Defines data types common to other packages; 4.) Common Codes –Defines commonly used lists of codes with special semantics; 5.) DescribeSensor – Defines the request and response types of an operation used to retrieve metadata about a given sensor; 6.) UpdateSensorDescription –Defines the request and response types of an operation used to modify the description of a given sensor; 7.) InsertSensor – Defines the request and response types of an operation used to insert a new sensor instance at a service; 8.) DeleteSensor – Defines the request and response types of an operation used to remove a sensor from a service. These packages use data types specified in other standards. Those data types are normatively referenced herein, instead of being repeated in this standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81861,35 +81711,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-020r1" + "@value": "09-001" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-13: NAS Profiling Engineering Report" + "@value": "OpenGIS® SWE Service Model Implementation Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-021r2", + "@id": "http://www.opengis.net/def/docs/14-038r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-07-08" + "@value": "0000-00-00" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ingo Simonis" + "@value": "Mark Hughes" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81899,27 +81749,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27775" + "@id": "https://portal.ogc.org/files/?artifact_id=58117" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC® Sensor Web Enablement Architecture" + "@value": "14-038r1" }, { "@language": "en", - "@value": "06-021r2" + "@value": "Testbed 10 Engineering Report: Aviation Dissemination of Weather Data" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes the architecture implemented by Open Geospatial Consortium’s (OGC) Sensor Web Enablement Initiative (SWE). In contrast to other OGC SWE stan-dards, this document is not an implementation standard." + "@value": "This OGC document provides an analysis of the mapping between the NOAA Web Gridded Document Service (WGDS) and the OGC Web Coverage Service (WCS) and describes an adapter which translates WCS 2.0 requests to WGDS requests and then translates WGDS responses to WCS 2.0 responses.\r\nThis Engineering Report was prepared as a deliverable for the OGC Testbed 10 (Testbed-10) initiative, specifically the Testbed 10 Aviation Thread.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81930,35 +81780,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-021r2" + "@value": "14-038r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Web Enablement Architecture" + "@value": "OGC® Testbed 10 Engineering Report: Aviation Dissemination of Weather Data" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-028", + "@id": "http://www.opengis.net/def/docs/14-065r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-05-15" + "@value": "2015-10-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "OGC Aviation Domain Working Group" + "@value": "Matthias Mueller" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -81968,27 +81818,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=47859" + "@id": "https://docs.ogc.org/is/14-065/14-065r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-028" + "@value": "14-065r1" }, { "@language": "en", - "@value": "Guidance and Profile of GML for use with Aviation Data" + "@value": "WPS 2.0.1 Interface Standard: Corrigendum 1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The ISO 19107 spatial schema, which is implemented by GML, is very complex. ISO\r\n19107 defines an extensive list of geometries, geometric properties and operations –\r\nmany of which are not necessary for aeronautical information applications. In addition,\r\nthe ISO 19107 contains an exhaustive 3D geometry model that is probably not needed in\r\nits entirety for AIXM either. Therefore, a GML profile for AIXM needs to be defined.\r\nThe objective of this document is to identify the elements of the AIXM-GML profile and\r\nalso to provide guidelines for the use of GML constructs in AIXM data sets.\r\n" + "@value": "In many cases geospatial or location data, including data from sensors, must be processed before the information can be used effectively. The OGC Web Processing Service (WPS) Interface Standard provides a standard interface that simplifies the task of making simple or complex computational processing services accessible via web services. Such services include well-known processes found in GIS software as well as specialized processes for spatio-temporal modeling and simulation. While the OGC WPS standard was designed with spatial processing in mind, it can also be used to readily insert non-spatial processing tasks into a web services environment.\r\n\r\nThe WPS standard provides a robust, interoperable, and versatile protocol for process execution on web services. It supports both immediate processing for computational tasks that take little time and asynchronous processing for more complex and time consuming tasks. Moreover, the WPS standard defines a general process model that is designed to provide an interoperable description of processing functions. It is intended to support process cataloguing and discovery in a distributed environment.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -81999,35 +81849,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-028" + "@value": "14-065r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Guidance and Profile of GML for use with Aviation Data" + "@value": "OGC® WPS 2.0.1 Interface Standard: Corrigendum 1" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-077r1", + "@id": "http://www.opengis.net/def/docs/17-087r13", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2012-12-05" + "@value": "2020-08-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Rahul Thakkar" + "@value": "John R. Herring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/primer" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -82037,27 +81887,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=50485" + "@id": "https://docs.ogc.org/as/17-087r13/17-087r13.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-077r1" + "@value": "Topic 01 - Spatial schema" }, { "@language": "en", - "@value": "A Primer for Dissemination Services for Wide Area Motion Imagery " + "@value": "17-087r13" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/primer" + "@id": "http://www.opengis.net/def/doc-type/as" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The reason for developing this specification was a WAMI community requirement to deliver high performance web services and disseminate WAMI products. While existing web services can be combined or modified to deliver some of the functionality of the services described in this document, by design, they cannot deliver the desired performance. " + "@value": "This document is the ISO 19107:2019 Standard and specifies conceptual schemas for describing the spatial characteristics of geographic entities, and a set of spatial operations consistent with these schemas. It treats vector geometry and topology." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82068,30 +81918,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-077r1" + "@value": "17-087r13" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "A Primer for Dissemination Services for Wide Area Motion Imagery " + "@value": "Topic 1 - Spatial schema" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-073r2", + "@id": "http://www.opengis.net/def/docs/22-054r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-11-18" + "@value": "2023-06-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "E. Devys, L.Colaiacomo, P. Baumann" + "@value": "Gobe Hobona, Joana Simoes " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -82106,17 +81956,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=65887" + "@id": "https://docs.ogc.org/per/22-054r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-073r2" + "@value": "22-054r1" }, { "@language": "en", - "@value": "Testbed-11 DGIWG GMLJP2 testing results Engineering Report" + "@value": "2022 Web Mapping Code Sprint Summary Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -82126,7 +81976,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) describes work done in OGC Testbed 11 to test\r\nGMLJP2 in terms of defining a DGIWG GMLJP2 version 1 profile.\r\nThe requirements for a DGIWG profile of GMLJP2 have been documented in the\r\nDGIWG GMLJP2 version 1 profile. The Imagery WG inside DGIWG has developed a\r\nfilter to map the files produced using the previous GMLJP2 schema into the GMLJP2\r\nversion 2 schema and is about to submit a GMLJP2 2.0 profile to DGIWG.\r\nThe DGIWG implementation of the GMLJP2 profile is based on the OGC GMLJP2 v2\r\nand other requirements are coming directly from the adoption inside the DGIWG of the\r\nnew OGC GMLJP2 version 2.\r\nThis Testbed 11 activity is a response to the need of harmonization between DGIWG and\r\nOGC." + "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from November 29th to December 1st, 2022 to advance OGC API Standards that relate to web mapping, and others that relate to styling and symbology encoding standards. The code sprint was hosted by the Open Geospatial Consortium (OGC) and EuroGeographics. The code sprint was sponsored by Ordnance Survey (OS), and was held as a hybrid event with the face-to-face element hosted at the Mundo Madou centre in Brussels, Belgium." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82137,35 +81987,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-073r2" + "@value": "22-054r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Testbed-11 DGIWG GMLJP2 testing results Engineering Report" + "@value": "2022 Web Mapping Code Sprint Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-128r15", + "@id": "http://www.opengis.net/def/docs/09-138", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2018-09-06" + "@value": "2010-03-21" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Yutzler" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -82175,27 +82025,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=80678" + "@id": "https://portal.ogc.org/files/?artifact_id=36177" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC® GeoPackage Encoding Standard - with Corrigendum" + "@value": "OGC® Fusion Standards Study Engineering Report" }, { "@language": "en", - "@value": "12-128r15" + "@value": "09-138" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." + "@value": "This OGC Engineering Report (ER) provides discussions and recommendations for information fusion, with a focus on geospatial information. In this ER, fusion is discussed in three categories: sensor fusion, object/feature fusion, and decision fusion. Recommendations in this ER will be considered in the planning of future activities including the OWS-7 Testbed." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82206,30 +82056,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-128r15" + "@value": "09-138" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® GeoPackage Encoding Standard - with Corrigendum" + "@value": "Fusion Standards Study Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-057", + "@id": "http://www.opengis.net/def/docs/14-084r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-11-10" + "@value": "2015-02-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Joan Masó, Jérôme Jacovella-St-Louis" + "@value": "Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -82244,17 +82094,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/20-057/20-057.html" + "@id": "https://docs.ogc.org/is/14-084r2/14-084r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC API - Tiles - Part 1: Core" + "@value": "14-084r2" }, { "@language": "en", - "@value": "20-057" + "@value": "Moving Features Encoding Extension: Simple Comma Separated Values (CSV)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -82264,7 +82114,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OGC API — Tiles is a standard defining building blocks for creating Web APIs that support the retrieval of geospatial information as tiles. Different forms of geospatial information are supported, such as tiles of vector features (“vector tiles”), coverages, maps (or imagery) and other types of geospatial information. Although it can be used independently, the OGC API — Tiles building blocks can be combined with other OGC API Standards and draft specifications for additional capabilities or increasing interoperability for specific types of data. The OGC API — Tiles standard references the OGC Two Dimensional Tile Matrix Set (TMS) and Tileset Metadata standard, which defines logical models and encodings for specifying tile matrix sets and describing tile sets. A tile matrix set is a tiling scheme that enables an application to partition and index space based on a set of regular grids defined for multiple scales in a Coordinate Reference System (CRS).\r\n\r\nThis specification is a successor to the OGC’s Web Map Tile Service (WMTS) standard, focusing on simple reusable REST API building blocks which can be described using the OpenAPI specification. Whereas WMTS focused on map tiles, the OGC API — Tiles standard has been designed to support any form of tiled data." + "@value": "This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82275,35 +82125,75 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-057" + "@value": "14-084r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Tiles - Part 1: Core" + "@value": "OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV)" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-026r4", + "@id": "http://www.opengis.net/def/doc-type/sap/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Specification Application Profile - Approved" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Specification Application Profile - Approved" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/01-009a" + }, + { + "@id": "http://www.opengis.net/def/docs/07-045" + }, + { + "@id": "http://www.opengis.net/def/docs/09-146r2" + }, + { + "@id": "http://www.opengis.net/def/docs/06-080r4" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Specification Application Profile - Approved" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/17-059", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-12-20" + "@value": "2017-10-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mike Botts" + "@value": "Lars Schylberg, Lubos Belka" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -82313,27 +82203,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=11516" + "@id": "https://docs.ogc.org/dp/17-059/17-059.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Sensor Model Language (SensorML) for In-situ and Remote Sensors" + "@value": "Technical report from the DGIWG Portrayal Technical Panel testing of SLD (1.1.0) for OGC" }, { "@language": "en", - "@value": "02-026r4" + "@value": "17-059" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances." + "@value": "The DGIWG Portrayal Technical Panel (DPTP) has been investigating how to standardize the portrayal of military context symbology within Web Services. The team sought to use version 1.1.0 of OGC Style Layer Descriptor standard and version 1.1.0 of Symbology Encoding (SLD and SE) standard to achieve this.\r\nThe team sought to apply military-specific symbology to military-specific topographic feature vector datasets within a number of software products.\r\nThe testing and experimentation highlighted a number of deficiencies in the SLD and SE standards which result in a barrier to interoperability. The ideal situation would be to have SLD and SE descriptors interoperable between all software products that implement the standard. This was found not to be the current situation.\r\nThis position paper describes the findings and outlines recommendations for a revised future version of the SLD and SE standards that resolves these issues.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82344,35 +82234,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-026r4" + "@value": "17-059" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Sensor Model Language (SensorML) for In-situ and Remote Sensors" + "@value": "Technical report from the DGIWG Portrayal Technical Panel testing of SLD (1.1.0) for OGC" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-003", + "@id": "http://www.opengis.net/def/docs/16-125", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-12-02" + "@value": "2020-09-17" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon J D Cox, Bruce A Simons" + "@value": "Dmitry Brizhinev, Sam Toyer, Kerry Taylor" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -82382,27 +82272,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/14-003/14-003.html" + "@id": "https://www.w3.org/TR/eo-qb/" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data" + "@value": "16-125" }, { "@language": "en", - "@value": "14-003" + "@value": "Publishing and Using Earth Observation Data with the RDF Data Cube and the Discrete Global Grid System" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Best Practice describes how to configure XML documents for single and time series water quality measurements. In addition to stating the rules for using the O&M and WML 2 standards, along with the appropriate content ontologies, this Best Practice provides guidance through examples. This document is intended to complement WaterML 2.0 as part of a suite of standards for water observation data." + "@value": "This document describes how dense geospatial raster data can be represented using the W3C RDF Data Cube (QB) ontology [vocab-data-cube] in concert with other popular ontologies including the W3C/OGC Semantic Sensor Network ontology (SSN) [vocab-ssn], the W3C/OGC Time ontology (Time) [owl-time], the W3C Simple Knowledge Organisation System (SKOS) [skos-reference], W3C PROV-O [prov-o] and the W3C/OGC QB4ST [qb4st]. It offers general methods supported by worked examples that focus on Earth observation imagery. Current triple stores, as the default database architecture for RDF, are not suitable for storing voluminous data like gridded coverages derived from Landsat satellite sensors. However we show here how SPARQL queries can be served through an OGC Discrete Global Grid System for observational data, coupled with a triple store for observational metadata. While the approach may also be suitable for other forms of coverage, we leave the application to such data as an exercise for the reader." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82413,35 +82303,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-003" + "@value": "16-125" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data" + "@value": "Publishing and Using Earth Observation Data with the RDF Data Cube and the Discrete Global Grid System" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-129", + "@id": "http://www.opengis.net/def/docs/18-045", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-03-06" + "@value": "2019-03-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Jeff Harrison, Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -82451,27 +82341,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=29544" + "@id": "https://docs.ogc.org/per/18-045.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-129" + "@value": "Next Generation Web APIs - WFS 3.0 Engineering Report" }, { "@language": "en", - "@value": "GML 3.2 implementation of XML schemas in 07-002r3" + "@value": "18-045" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "" + "@value": "The objective of the Next Generation APIs - WFS 3.0 effort in OGC Testbed-14 was to develop and test the Web Feature Service (WFS) version 3.0 candidate standard. The initiative assessed OpenAPI, security based on OpenID Connect and OAuth 2.0 and WFS 3.0 extensions. The effort also began to assess methods to ease geospatial enterprise transition to next generation Application Programming Interfaces (APIs).\r\n\r\nThe purpose of this effort was not to preempt other next generation work taking place in OGC, but rather to inform and complement that work.\r\n\r\nThis Engineering Report (ER) describes the implementations and experiments conducted by OGC Testbed-14 participants to test next generation Web APIs. It includes descriptions of APIs to simplify and secure access to geospatial feature resources, and was tested in a scenario that showed how WFS 3.0 can support humanitarian relief activities." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82482,35 +82372,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-129" + "@value": "18-045" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML 3.2 implementation of XML schemas in 07-002r3" + "@value": "OGC Testbed-14: Next Generation Web APIs - WFS 3.0 Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-070", + "@id": "http://www.opengis.net/def/docs/05-016", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-07-13" + "@value": "2005-05-02" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Steve Liang" + "@value": "Marwa Mabrouk" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -82520,27 +82410,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/bp/21-070/21-070.html" + "@id": "https://portal.ogc.org/files/?artifact_id=8836" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-070" + "@value": "Location Service (OpenLS) Implementation Specification: Core Services" }, { "@language": "en", - "@value": "OGC Integrated Methane Sensor Web for Emissions Management Best Practice - Part I - Fugitive Emissions Management based on AE" + "@value": "05-016" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Methane (CH4) is one of the most potent greenhouse gases, and the comparative impact of methane is 25 times greater than CO2 over a 100-year period. Methane is an invisible and odorless gas, and it is very labor intensive and time consuming in order to detect and repair leaks. Regulations play a critical role in methane emissions reduction, and how methane emissions are detected, repaired, and managed is highly dependent on local regulations. This OGC Best Practice document defines a SensorThings API for fugitive methane emissions management." + "@value": "The OpenGIS® Open Location Services Interface Standard (OpenLS) specifies interfaces that enable companies in the Location Based Services (LBS) value chain to “hook up” and provide their pieces of applications such as emergency response (E-911, for example), personal navigator, traffic information service, proximity service, location recall, mobile field service, travel directions, restaurant finder, corporate asset locator, concierge, routing, vector map portrayal and interaction, friend finder, and geography voice-graphics. These applications are enabled by interfaces that implement OpenLS services such as a Directory Service, Gateway Service, Geocoder Service, Presentation (Map Portrayal) Service and others.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82551,18 +82441,18 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-070" + "@value": "05-016" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Integrated Methane Sensor Web for Emissions Management Best Practice - Part I - Fugitive Emissions Management based on AE" + "@value": "OpenGIS Location Service (OpenLS) Implementation Specification: Core Services" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-077", + "@id": "http://www.opengis.net/def/docs/05-078", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], @@ -82589,17 +82479,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=12636" + "@id": "https://portal.ogc.org/files/?artifact_id=12637" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Symbology Encoding Implementation Specification" + "@value": "05-078" }, { "@language": "en", - "@value": "05-077" + "@value": "Styled Layer Descriptor Profile of the Web Map Service Implementation Specification" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -82609,7 +82499,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Specification defines Symbology Encoding, an XML language for styling information that can be applied to digital Feature and Coverage data." + "@value": "This Document specifies how a Web Map Service can be extended to allow user-defined styling. Different modes for utilizing Symbology Encoding for this purpose are discussed." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82620,30 +82510,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-077" + "@value": "05-078" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Symbology Encoding Implementation Specification" + "@value": "Styled Layer Descriptor Profile of the Web Map Service Implementation Specification" } ] }, { - "@id": "http://www.opengis.net/def/docs/22-020r1", + "@id": "http://www.opengis.net/def/docs/15-047r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-03-13" + "@value": "2016-01-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Paul Churchyard, Ajay Gupta" + "@value": "Jeff Harrison" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -82658,17 +82548,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/22-020r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=65418" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "22-020r1" + "@value": "15-047r3" }, { "@language": "en", - "@value": "Testbed-18: Identifiers for Reproducible Science Summary Engineering Report" + "@value": "Testbed-11 NIEM-IC Feature Processing API using OGC Web Services" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -82678,7 +82568,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC’s Testbed 18 initiative explored the following six tasks.\r\n\r\n1.) Advanced Interoperability for Building Energy\r\n2.) Secure Asynchronous Catalogs\r\n3.) Identifiers for Reproducible Science\r\n4.) Moving Features and Sensor Integration\r\n5.) 3D+ Data Standards and Streaming\r\n6.) Machine Learning Training Data\r\nTestbed 18 Task 3, Identifiers for Reproducible Science, explored and developed workflows demonstrating best practices at the intersection of Findable, Accessible, Interoperable, and Reusable (or FAIR) data and reproducible science.\r\n\r\nThe workflows developed in this Testbed included:\r\n\r\nthe development of a Whole Tail workflow for land cover classification (52 Degrees North);\r\nthe development of a reproducible workflow for a deep learning application for target detection (Arizona State University);\r\nthe implementation of reproducible workflows following the approach described in the OGC API Process Part 3: Workflows and Chaining for Modular OGC API Workflows (Ecere);\r\nthe development of a reproducible workflow that runs an OGC API — Process and Feature Server instance within a Whole Tale environment (GeoLabs); and\r\nthe development of a water body detection Application Package to cover the identifier assignment and reproducibility from code to several execution scenarios (local, Exploitation Platform, Whole Tale) (Terradue).\r\nTestbed 18 participants identified considerations and limitations for reproducible workflows and recommendations for future work to identify the benefits of reproducible science for healthcare use cases." + "@value": "The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community (IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0 architecture through the development, implementations, test, and robust demonstration making use of IC specifications, Geography Markup Language (GML), and NIEM in a simulated “real-world” scenario. The demonstration scenario begins with NIEM-conformant Information Exchange Packages (IEPs) containing operational data and IC security tags from the Information Security Marking (ISM) and Need-To-Know (NTK) access control metadata, and the Trusted Data Format (TDF) for binding assertion metadata with data resource(s). Those instance documents are deployed on Open Geospatial Consortium (OGC) Web Services to be used by client applications. Access control is based on attributes of the end-user and the instance data. \r\nThe assessment included reviewing example IEPDs and performing test and demonstrations using OGC web services, such as Transactional Web Feature Services (WFS-T), Policy Enforcement Points (PEPs) and OGC Attribute Stores to process geographic feature with NIEM components and security tags. The Test and Demonstration included, but was not limited to feature retrieval and transactions. Recommendations to update these information exchanges were provided to reflect NIEM 3.0 architecture and security tags in a ‘NIEM/IC Feature Processing API’. Results from this task helped provide a preliminary architecture for Geo4NIEM in Testbed 11, summarized in other OGC Testbed 11 Engineering Reports. \r\nThis task also identified potential change requests to OGC WFS or other OGC Services for handling security information in a federated role-based access control environment. These changes may help the NIEM/IC transform into more agile and customer-centric frameworks driven by collaborative partnerships. This transformation is vital to confronting the security challenges of the future.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82689,35 +82579,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-020r1" + "@value": "15-047r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-18: Identifiers for Reproducible Science Summary Engineering Report" + "@value": "Testbed-11 NIEM-IC Feature Processing API using OGC Web Services" } ] }, { - "@id": "http://www.opengis.net/def/docs/02-027", + "@id": "http://www.opengis.net/def/docs/18-085", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2002-05-31" + "@value": "2019-02-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Cox" + "@value": "Sam Meek" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -82727,27 +82617,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1137" + "@id": "https://docs.ogc.org/per/18-085.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Observations and Measurements" + "@value": "18-085" }, { "@language": "en", - "@value": "02-027" + "@value": " BPMN Workflow Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes a framework and encoding for measurements and observations." + "@value": "This Engineering Report (ER) presents the results of the D146 Business Process Modeling Notation (BPMN) Engine work item and provides a study covering technologies including Docker, Kubernetes and Cloud Foundry for Developer Operations (DevOps) processes and deployment orchestration. The document also provides the beginning of a best practices effort to assist implementers wishing to orchestrate OGC services using BPMN workflow engines. As with previous investigations into workflow engines, the implementation described within utilizes a helper class, which is a bespoke implementation of some of the best practices. Work in future testbeds on workflows should include a compelling use case to demonstrate the power of service orchestration." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82758,30 +82648,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "02-027" + "@value": "18-085" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Observations and Measurements" + "@value": "OGC Testbed-14: BPMN Workflow Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-033r1", + "@id": "http://www.opengis.net/def/docs/12-119r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-04-28" + "@value": "2013-02-01" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ranjay Shrestha, Liping Di, Eugene G. Yu" + "@value": "Ingo Simonis" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -82796,17 +82686,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-033r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=52272" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-033r1" + "@value": "OWS-9: OGC Mobile Apps: Definition, Requirements, and Information Architecture" }, { "@language": "en", - "@value": "Testbed-12 WCS Profile Update Engineering Report" + "@value": "12-119r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -82816,7 +82706,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report capture the work to extend the existing Web Coverage Service (WCS) profiles, particularly the Earth Observation Application Profile (EO-WCS [OGC 10-140r1]) to support multi-dimensional subsetting of 3D space and 1D time. The updated EO-WCS (EO-WCS1.1 [OGC 10-140r2]) have removed the requirement for the 2D coverages so that it can explicitly allow coverages with more dimensions as long as they have geographic footprint. Furthermore it also clarified the use of rangeType when non-NCNAME characters are present in a band identifier. The example of GetCapabilites, DescribeEOCoverageSet, and _GetCoverage request in the updated EO-WCS1.1 is shown with use case on fire emission data in San Francisco.\r\n\r\nFollowing the recommendation for EO-WCS to fully embrace the N-D, multi-dimensional, concept of Coverages as a function of time and other coordinates alongside the geospatial ones, the proposed recommendations/changes in the extension for WCS DescribeCoverage, EO-WCS DescribeEOCoverageSet, and WCS GetCoverage are discussed with use case example using National Centers for Environmental Prediction (NCEP) Global 0.25 deg wind data. Based on the mutual recommendation from the US National Aeronautics and Space Administration (NASA) and Baart et. al (2012), Network Common Data Form (NetCDF) was the output format due to presence of its libraries in multiple languages to lower the burden in changing on developers of WCS-compliant servers and clients.\r\n\r\nFor the extension of the WCS DescribeCoverage, it is recommended that CIS1.1 should be considered adopting a scheme for transmitting coordinates similar to the _cis:rangeSet where data are referred to as an attached Multipurpose Internet Mail Extensions (MIME) part. Time, as much as possible, be treated as just another coordinates dimension so that it could be access with the same tools used for other coordinate dimensions. To tackle the issue on order of coordinate dimensions, it is recommended to add implementation note to the EO-WCS specifications so that implementers are aware of the mismatches between dataset coordinate reference systems (CRSs) and actual axis order.\r\n\r\nFor the extension of EO_WCS DescribeEOCoverageSet, the issue on missing range of results API needed to be resolved by adding a request mechanism for requesting a range of matching results. It is also recommended that DescribeEOCoverageSet activity might be of more use to the client if the client need to supply only the subset conditions, and not a list of identifiers.\r\n\r\nFor the extension of WCS GetCoverage, it was discovered that for the GetCoverage operation for higher dimensioned datasets, existing WCS-2.0 request interface provided adequate syntax for subsetting higher dimensional data. Scaling (re-gridding) operation appears to be a natural fit for the EO-WCS subsetting, specifically SCALEEXTENT activity, however simpler explanation might be needed to fully understand its use as it appears other scaling and subsetting commands may be more than adequate for the desired outcomes. Additionally allowing SlicePoint subsetting is also recommended.\r\n\r\nAfter performing the testing in the client side, there were few potential recommendations for improvements. More information on whether the coverage is 2D or 3D form the GetCapalilites request might be helpful to client so it can limit the number of DescribeCoverage requests to construct a list of available coverage on the server. Furthermore additional metadata information for displaying meaningful native gird coordinates is also recommended for clarification. Finally automatic detection of lat/lon axes along with clear treatment of XY and lat/lon axes ordering would be an improvement in the existing operations." + "@value": "This engineering report represents the results of the OWS-9 innovations thread on mobile applications. Initially, the goal was to help understanding the requirements for developing standards-based geospatially-enabled mobile applications. The report describes how OGC Enabled Mobile Apps can be integrated into information architectures based on OGC standards. Particular emphasize has been put on the future work section, as it provides valuable recommendations for further standardization work (and, equally important, highlights aspects that could be excluded from standardization)" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82827,35 +82717,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-033r1" + "@value": "12-119r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 WCS Profile Update Engineering Report" + "@value": "OWS-9: OGC Mobile Apps: Definition, Requirements, and Information Architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-019", + "@id": "http://www.opengis.net/def/docs/05-109r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-01-21" + "@value": "2006-05-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Aleksandar Balaban" + "@value": "Panagiotis (Peter) A. Vretanos, Rento Primavera" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -82865,27 +82755,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-019.html" + "@id": "https://portal.ogc.org/files/?artifact_id=14143" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-019" + "@value": "05-109r1" }, { "@language": "en", - "@value": "OGC Testbed-17: Attracting Developers: Lowering the entry barrier for implementing OGC Web APIs" + "@value": "Catalog 2.0 IPR for ebRIM" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed 17 Engineering Report (ER) documents the work completed in the “Attracting Developers: Lowering the entry hurdle for OGC Web API experiments” task.\r\n\r\nOGC Web API Standards are being developed to make it easy to provide geospatial data over the web. These standards provide a certain level of formality to ensure high levels of interoperability. They rigorously define requirements and rules to reduce room for error during interpretation. This rigor sometimes makes the standard documents difficult to read and hence implement. Rather than direct examination of a standard, the majority of developers often prefer to start with implementation guidelines, sample code, and best practice documentation and then refer to the standards document for guidance and clarity.\r\n\r\nThe Testbed-17 (TB-17) API task served as a foundation for further development and exploration and delivers knowledge necessary for agile development, deployment, and executing OGC Standards-based applications following a “How-To” philosophy with hands-on experiments, examples, and instructions.\r\n\r\n" + "@value": "The purpose of this document is to show how to map the various types of metadata documents to be used in the OWS3 project into the ebRIM." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82896,35 +82786,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-019" + "@value": "05-109r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: Attracting Developers: Lowering the entry barrier for implementing OGC Web APIs" + "@value": "Catalog 2.0 IPR for ebRIM" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-072r5", + "@id": "http://www.opengis.net/def/docs/16-114r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-10-20" + "@value": "2018-12-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Hugo Ledoux, Balázs Dukai" + "@value": "Martin Desruisseaux" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -82934,27 +82824,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/cs/20-072r5/20-072r5.html" + "@id": "https://docs.ogc.org/bp/16-114r3/16-114r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "20-072r5" + "@value": "16-114r3" }, { "@language": "en", - "@value": "CityJSON Community Standard 2.0" + "@value": "Moving Features Encoding Extension: netCDF" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/cs" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "CityJSON is a data exchange format for digital 3D models of cities and landscapes. It aims at being easy-to-use (for reading, processing, and creating datasets), and it was designed with programmers in mind, so that tools and APIs supporting it can be quickly built. The JSON-based encoding of CityJSON implements a subset of the OGC CityGML data model (version 3.0) and includes a JSON-specific extension mechanism. Using JSON instead of GML allows us to compress files by a factor 6 and at the same time to simplify greatly the structure of the files." + "@value": "The netCDF Moving Features encoding extension is a summary of conventions that supports efficient exchange of simple moving features as binary files. This Best Practice is a complement to the Moving Features Encoding Part I: XML Core and an alternative to the Simple Comma Separated Values (CSV) extension. Compared to the CSV encoding, this netCDF encoding offers more compact storage and better performance at the cost of additional restrictions on the kinds of features that can be stored." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -82965,35 +82855,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-072r5" + "@value": "16-114r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CityJSON Community Standard 2.0" + "@value": "OGC Moving Features Encoding Extension: netCDF" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-066r5", + "@id": "http://www.opengis.net/def/docs/20-016", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-04-29" + "@value": "2021-01-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -83003,27 +82893,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27298" + "@id": "https://docs.ogc.org/per/20-016.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-066r5" + "@value": " Data Access and Processing Engineering Report" }, { "@language": "en", - "@value": "Corrigendum 2 for the OGC Standard Web Coverage Service 1.1" + "@value": "20-016" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/notes" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the details of a corrigendum to an OpenGIS Implementation Standard and does not modify the base standard. The OGC Standard that this document provides revision notes for is Web Coverage Service Standard, Version 1.1 Corrigendum 2 [OGC 07-067r5]." + "@value": "This OGC Testbed-16 Engineering Report (ER) describes the work performed in the Data Access and Processing API (DAPA) thread.\r\n\r\nThe primary goal of the DAPA thread is to develop methods and apparatus that simplify access to, processing of, and exchange of environmental and Earth Observation (EO) data from an end-user perspective. This ER presents:\r\n\r\nThe use cases participants proposed to guide the development of the client and server components deployed during the testbed.\r\n\r\nAn abstract description of a resource model that binds a specific function to specific data and also provides a means of expressing valid combinations of data and processes.\r\n\r\nA description of each DAPA endpoint developed and deployed during the testbed.\r\n\r\nA description of the client components that interact with the deployed DAPA endpoints.\r\n\r\nEnd-user (i.e. data scientist) feedback concerning the ease-of-use of the" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -83034,30 +82924,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-066r5" + "@value": "20-016" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Corrigendum 2 for the OGC Standard Web Coverage Service 1.1" + "@value": "OGC Testbed-16: Data Access and Processing Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-089", + "@id": "http://www.opengis.net/def/docs/16-023r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-10-23" + "@value": "2017-06-30" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Charles Chen" + "@value": "Benjamin Pross" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -83072,17 +82962,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/18-089.html" + "@id": "https://docs.ogc.org/per/16-023r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Indoor Mapping and Navigation Pilot Engineering Report" + "@value": "16-023r3" }, { "@language": "en", - "@value": "18-089" + "@value": "Testbed-12 Implementing Asynchronous Services Response Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -83092,7 +82982,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Indoor Mapping and Navigation Pilot Initiative was sponsored by the National Institute of Standards and Technology (NIST) Public Safety Communications Research (PSCR) Division. This initiative addressed key challenges related to indoor mapping and navigation for the purpose of supporting first responders in fields such as fire-fighting. The focus of this initiative was on developing the capabilities and workflows required for pre-planning operations. This included scanning each building to produce a point cloud dataset and converting this source data into various intermediate forms to support the generation of indoor navigation routes. This Engineering Report (ER) describes the work conducted in this initiative, the lessons learned captured by participants, and future recommendations to support the public safety efforts and interoperability of the standards. It is expected that future OGC initiatives will address the real-time, event-driven aspects of indoor mapping and navigation for first response situations.\r\n\r\nFirst responders typically survey high-risk facilities in their jurisdiction at least once per year as part of a pre-planning process. Pre-planning outputs are often in the form of reports, and first responders may generate their own hand-drawn maps during the process or annotate available floor plans (e.g., from computer-aided design models). Pre-planning is time-consuming, inefficient, and inherently complex considering the information and level of detail that should or could be captured, the lack of automation, and the difficulty identifying notable changes to facilities and infrastructure during successive pre-planning surveys.\r\n\r\nMobile three-dimensional (3D) Light Detection and Ranging (LiDAR) has been identified as a potentially transformational technology for first responders. Using LiDAR and 360-degree camera imagery, coupled with advanced software processing, first responders could efficiently capture 3D point clouds and a wealth of other information, both observed and derived, while walking through buildings as part of routine pre-planning operations. The use of 3D LiDAR and imagery has many potential upsides beyond just creating point clouds for visualization and mapping (e.g., use in localization, object classification, integration with virtual/augmented reality solutions, change detection, etc.)." + "@value": "Most of current OGC specifications define synchronous communication patterns, i.e. after sending a request to an OGC service, clients need to wait for the response. But several applications, e.g. delivery of information about events or executing complex environmental models with long runtime, need asynchronous client-server interaction pattern that do not require clients to keep the connection to the server continuously open in order to wait for responses. At the moment, there are several approaches how to add asynchronous communication to existing OGC services: One option is to use a WPS façade, as the WPS specification already defines asynchronous service responses. Another option is to add extensions to the different specifications and the third option is developed by the OGC Publish-Subscribe Working Group. This ER summarizes and compares the results from the different activities for asynchronous service responses and provides recommendations for future activities." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -83103,35 +82993,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-089" + "@value": "16-023r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Indoor Mapping and Navigation Pilot Engineering Report" + "@value": "Testbed-12 Implementing Asynchronous Services Response Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/03-010r9", + "@id": "http://www.opengis.net/def/docs/06-189", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2003-10-16" + "@value": "2007-08-27" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Chris Holmes" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/d-isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -83141,27 +83031,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=11517" + "@id": "https://portal.ogc.org/files/?artifact_id=19208" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Recommended XML Encoding of CRS Definitions" + "@value": "06-189" }, { "@language": "en", - "@value": "03-010r9" + "@value": "Corrigendum 1 (one) for OpenGIS Implementation Specification GML 2.1.2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-rp" + "@id": "http://www.opengis.net/def/doc-type/d-isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OpenGIS Recommendation Paper specifies basic XML encoding of data defining coordinate reference systems and coordinate operations. This encoding is expected to be adapted and used by multiple OGC Implementation Specifications, by the separate specification of Application Schemas. This document is a Recommendation Paper because the specified encoding is more general than an OpenGIS Implementation Specification and more specific than the OpenGIS Abstract Specification." + "@value": "This document provides the details for a corrigendum for the existing OpenGIS Implementation Specification for the Geography Markup Language version 2.1.2 and does not modify that implementation specification. The current OpenGIS Implementation Specification that this document provides revision notes for is 02-069. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -83172,33 +83062,40 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-010r9" + "@value": "06-189" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Recommended XML Encoding of CRS Definitions" + "@value": "Corrigendum 1 (one) for OpenGIS Implementation Specification GML 2.1.2" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-009r1", + "@id": "http://www.opengis.net/def/docs/16-079", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-02-21" + "@value": "2017-09-23" + }, + { + "@type": "xsd:date", + "@value": "2019-07-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Bastian Schaeffer" + "@value": "Armin Haller, Krzysztof Janowicz, Simon Cox, Danh Le Phuoc, Kerry Taylor, Maxime Lefrançois" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + { + "@id": "http://www.opengis.net/def/doc-type/is" + }, { "@id": "http://www.opengis.net/def/doc-type/dp" } @@ -83210,27 +83107,36 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=26521" + "@id": "https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/" + }, + { + "@id": "https://www.w3.org/TR/vocab-ssn/" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "08-009r1" + "@value": "16-079" }, { "@language": "en", - "@value": "OWS 5 SOAP/WSDL Common Engineering Report" + "@value": "Semantic Sensor Network Ontology" } ], "http://www.w3.org/2004/02/skos/core#broader": [ + { + "@id": "http://www.opengis.net/def/doc-type/is" + }, { "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC document reports the results achieved in the OWS5 GPW-SOAP/WSDL thread which is focused on creating general recommendations and guidelines for WSDL/SOAP support to existing OGC Web Services." + "@value": "The Semantic Sensor Network (SSN) ontology is an ontology for describing sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties, as well as actuators. SSN follows a horizontal and vertical modularization architecture by including a lightweight but self-contained core ontology called SOSA (Sensor, Observation, Sample, and Actuator) for its elementary classes and properties. With their different scope and different degrees of axiomatization, SSN and SOSA are able to support a wide range of applications and use cases, including satellite imagery, large-scale scientific monitoring, industrial and household infrastructures, social sensing, citizen science, observation-driven ontology engineering, and the Web of Things. Both ontologies are described below, and examples of their usage are given." + }, + { + "@value": "The Semantic Sensor Network (SSN) ontology is an ontology for describing sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties, as well as actuators. SSN follows a horizontal and vertical modularization architecture by including a lightweight but self-contained core ontology called SOSA (Sensor, Observation, Sample, and Actuator) for its elementary classes and properties. With their different scope and different degrees of axiomatization, SSN and SOSA are able to support a wide range of applications and use cases, including satellite imagery, large-scale scientific monitoring, industrial and household infrastructures, social sensing, citizen science, observation-driven ontology engineering, and the Web of Things. Both ontologies are described below, and examples of their usage are given.\r\n\r\nThe namespace for SSN terms is http://www.w3.org/ns/ssn/. \r\nThe namespace for SOSA terms is http://www.w3.org/ns/sosa/.\r\n\r\nThe suggested prefix for the SSN namespace is ssn.\r\nThe suggested prefix for the SOSA namespace is sosa.\r\n\r\nThe SSN ontology is available at http://www.w3.org/ns/ssn/. \r\nThe SOSA ontology is available at http://www.w3.org/ns/sosa/." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -83241,35 +83147,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-009r1" + "@value": "16-079" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS 5 SOAP/WSDL Common Engineering Report" + "@value": "Semantic Sensor Network Ontology" } ] }, { - "@id": "http://www.opengis.net/def/docs/14-005r4", + "@id": "http://www.opengis.net/def/docs/15-122r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-08-23" + "@value": "2016-04-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker" + "@value": "Randolph Gladish" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -83279,27 +83185,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://docs.opengeospatial.org/is/14-005r4/14-005r4.html" + "@id": "https://portal.ogc.org/files/?artifact_id=66606" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC® IndoorGML - with Corrigendum" + "@value": "Implications for an OGC GeoPackage Symbology Encoding Standard" }, { "@language": "en", - "@value": "14-005r4" + "@value": "15-122r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes.\r\n\r\n" + "@value": "The GeoPackage Standards Working Group (SWG) presents a discussion of symbology encapsulation for conveying presentation information for vector features contained within in a GeoPackage. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -83310,40 +83216,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "14-005r4" + "@value": "15-122r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® IndoorGML - with Corrigendum" - } - ], - "http://www.w3.org/ns/dcat#landingPage": [ - { - "@id": "http://docs.opengeospatial.org/is/14-005r4/14-005r4.html" + "@value": "Implications for an OGC GeoPackage Symbology Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-024", + "@id": "http://www.opengis.net/def/docs/09-102r3a", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-07-26" + "@value": "2016-01-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas Uslander (Ed.)" + "@value": "Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -83353,27 +83254,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=20300" + "@id": "https://portal.ogc.org/files/?artifact_id=66915" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Reference Model for the ORCHESTRA Architecture" + "@value": "DGIWG - Web Map Service 1.3 Profile - Revision" }, { "@language": "en", - "@value": "07-024" + "@value": "09-102r3a" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It contains a platform-neutral specification of the ORCHESTRA Architecture and a specification framework for the design of ORCHESTRA-compliant service networks across all viewpoints." + "@value": "This document defines specific DGIWG requirements,\r\nrecommendations and guidelines for implementations of the\r\nISO and OGC Web Map Service standards; ISO 19128:2005\r\nWeb Map Server Interface and the OpenGIS Web Map Server\r\nImplementation Specification 1.3.0." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -83384,35 +83285,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-024" + "@value": "09-102r3a" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Reference Model for the ORCHESTRA Architecture" + "@value": "DGIWG - Web Map Service 1.3 Profile - Revision" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-042r2", + "@id": "http://www.opengis.net/def/docs/21-010r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-11-21" + "@value": "2022-05-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Taehoon Kim, Kyoung-Sook Kim, Jiyeong Lee, Ki-Joune Li" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -83422,27 +83323,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13140" + "@id": "https://docs.ogc.org/dp/21-010r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-042r2" + "@value": "21-010r2" }, { "@language": "en", - "@value": "Web services architecture description" + "@value": "Extensions of IndoorGML 1.1 - Indoor Affordance Spaces" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document summarizes the most significant aspects of the Open Geospatial Consortium (OGC) web services architecture, which the OGC is currently developing. This architecture is a service-oriented architecture, with all components providing one or more services to other services or to clients." + "@value": "The OGC IndoorGML standard provides a fundamental data model for representing indoor spaces as spatial, topological, and semantic features. The IndoorGML core module allows applications to extend the model with their semantic considerations. For example, the IndoorGML navigation module classifies the basic class of indoor spaces, cell spaces, into navigable or non-navigable spaces. Navigable spaces, in which users can move freely, are specified in two subclasses: transfer spaces (e.g. doors, entrances, hallways) and general spaces (e.g. rooms, terraces, lobbies), based on indoor navigation requirements. This discussion paper proposes an extension to the OGC IndoorGML core module to support new types of location-based services, such as autonomous driving robots, personal experience augmentation with augmented reality (AR) / virtual reality (VR), and facilities management, to understand activities and needs in indoor spaces. The proposed extension consists of three new indoor spaces to represent affordance spaces with structural, functional, and sensory characteristics by leveraging the multi-layered space representation of IndoorGML." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -83453,35 +83354,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-042r2" + "@value": "21-010r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Web services architecture description" + "@value": "Extensions of IndoorGML 1.1 - Indoor Affordance Spaces" } ] }, { - "@id": "http://www.opengis.net/def/docs/99-051", + "@id": "http://www.opengis.net/def/docs/22-013r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "1999-07-16" + "@value": "2022-11-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Doug Nebert" + "@value": "Sergio Taleisnik, Terry Idol, Ph.D." } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -83491,27 +83392,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=831" + "@id": "https://docs.ogc.org/per/22-013r3.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "99-051" + "@value": "22-013r3" }, { "@language": "en", - "@value": "Catalog Interface" + "@value": "Towards a Federated Marine SDI: IHO and OGC standards applied to Marine Protected Area Data Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers." + "@value": "This Engineering Report (ER) summarizes the demonstrations, findings, and recommendations that emerged from the second phase of the OGC Federated Marine Spatial Data Infrastructure (FMSDI) Pilot. The goal of this initiative was to further advance the interoperability and usage of Marine Protected Area (MPA) data through the implementation of the IHO standard S-122 and several OGC API standards.\r\n\r\nThis ER describes a solution architecture consisting of a collection of interoperable components developed to demonstrate technologies that helped to achieve the objectives of this Pilot’s phase. This document describes a server built to serve MPA data through an OGC API – Features endpoint and two servers that combined MPA data with additional datasets and served it through both an OGC API – Features and an OGC API — EDR endpoint. This document also describes the three clients built to consume under different scenarios the data offered by the aforementioned servers. Finally, this ER captures lessons learned and recommendations for IHO and OGC API standards, and recommendations for future work." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -83522,25 +83423,25 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-051" + "@value": "22-013r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Catalog Interface" + "@value": "Towards a Federated Marine SDI: IHO and OGC standards applied to Marine Protected Area Data Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-018", + "@id": "http://www.opengis.net/def/docs/09-026r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-02-08" + "@value": "2014-08-18" } ], "http://purl.org/dc/terms/creator": [ @@ -83550,7 +83451,7 @@ ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -83560,27 +83461,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/21-018.html" + "@id": "https://docs.ogc.org/is/09-026r2/09-026r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Features and Geometries JSON CRS Analysis of Alternatives Engineering Report" + "@value": "Filter Encoding 2.0 Encoding Standard - With Corrigendum " }, { "@language": "en", - "@value": "21-018" + "@value": "09-026r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "One of the primary requirements for the OGC Testbed-17 Features and Geometries JSON task is to define an extension or profile of GeoJSON that supports encoding spatiotemporal data in Coordinate Reference Systems (CRS) other than the GeoJSON default of the World Geodetic System 1984 (WGS 84) datum, with longitude and latitude units of decimal degrees (CRS84).\r\n\r\nThis OGC Testbed 17 (TB17) Engineering Report (ER) presents the various alternatives considered for declaring CRS information in a Features and Geometries JSON (JSON-FG) file. JSON-FG is an OGC extension to GeoJSON that, among other things, adds support of coordinate reference systems other than the CRS84 default. One of the alternatives was selected to be the mechanism for declaring CRS information in a JSON-FG document and is fully described in the “OGC Testbed-17: OGC Features and Geometries JSON Engineering Report” (OGC 21-017r1).\r\n\r\nThis ER was submitted to the OGC Features and Geometries JSON Standards Working Group so that the work in TB17 can inform their task of developing and documenting a Features and Geometries JSON standard." + "@value": "A fundamental operation performed on a set of data or resources is that of querying in order to obtain a subset of the data which contains certain desired information that satisfies some query criteria and which is also, perhaps, sorted in some specified manner.\r\n\r\nThis International Standard defines an abstract component, named AbstractQueryExpression, from which other specifications can subclass concrete query elements to implement query operations. This International Standard also defines an additional abstract query component, named AbstractAdhocQueryExpresison, which is derived from AbstractQueryExpression and from which other specifications can subclass concrete query elements which follow a query pattern composed of a list of resource types to query, a projection clause specifying the properties of those resources to present in the result, a projection clause composed of predicates that define the subset of resources or data in the result set and a sorting clause indicating to order in which the results should be presented. This pattern is referred to as an ad hoc query pattern since the server is not aware of the query until it is submitted for processing. This is in contrast to a stored query expression, which is stored and can be invoked by name or identifier.\r\n\r\nThis International Standard describes an XML and KVP encoding of a system-neutral syntax for expressing the projection, selection and sorting clauses of a query expression. The intent is that this neutral representation can be easly validated, parsed and then translated into some target query language such as SPARQL or SQL for processing." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -83591,30 +83492,64 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-018" + "@value": "09-026r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-17: Features and Geometries JSON CRS Analysis of Alternatives Engineering Report" + "@value": "OGC Filter Encoding 2.0 Encoding Standard - With Corrigendum " } ] }, { - "@id": "http://www.opengis.net/def/docs/16-055", + "@id": "http://www.opengis.net/def/doc-type/d-atb/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Technical Baseline - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Technical Baseline - deprecated " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/03-053r1" + }, + { + "@id": "http://www.opengis.net/def/docs/04-014r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Technical Baseline - deprecated " + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/22-043r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-15" + "@value": "2022-12-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jeff Harrison" + "@value": "Gobe Hobona, Joana Simoes" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -83629,17 +83564,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-055.html" + "@id": "https://docs.ogc.org/per/22-043r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Testbed-12 Compression Techniques Engineering Report" + "@value": "Joint OGC and ISO Code Sprint 2022 Summary Engineering Report" }, { "@language": "en", - "@value": "16-055" + "@value": "22-043r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -83649,7 +83584,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Open Geospatial Consortium (OGC) document provides an analysis of the prototype implementations, approaches and performance aspects of data size reduction and compression techniques explored in OGC Testbed 12. Specifically, it describes work done during Testbed 12 investigating compression for geospatial data sets on OGC Web Feature Service (WFS) using W3C Efficient XML Interchange (EXI) Format 1.0 (Second Edition).\r\n\r\nThe investigation focused on extending WFS with EXI output formats, and the associated performance aspects of data size reduction and compression techniques. EXI is a compact representation for the Extensible Markup Language (XML) Information Set. EXI is intended to simultaneously optimize performance and the utilization of computational resources. From a practical viewpoint, EXI is designed to reduce the size of XML data exchanged between computer systems.\r\n\r\nEXI uses a grammar-driven approach designed to achieve efficient encodings using an encoding algorithm and a small set of datatype representations. Consequently, EXI processors are described by the W3C as ‘relatively simple’ and ‘can be implemented on devices with limited capacity.’ An EXI processor is used by application programs to encode their structured data into EXI streams and/or to decode EXI to make the structured data accessible." + "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from the 14th to the 16th of September 2022 to advance open standards that relate to geospatial metadata and catalogues. The code sprint was hosted by the Open Geospatial Consortium (OGC) and the International Organization for Standardization (ISO). The code sprint was sponsored by Ordnance Survey (OS) and Geonovum, and held as a hybrid event with the face-to-face element hosted at the Geovation Hub in London, United Kingdom." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -83660,35 +83595,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-055" + "@value": "22-043r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 Compression Techniques Engineering Report" + "@value": "Joint OGC and ISO Code Sprint 2022 Summary Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-021r3", + "@id": "http://www.opengis.net/def/docs/01-024r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2004-08-02" + "@value": "2001-01-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Doug Nebert" + "@value": "Louis Reich" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -83698,31 +83633,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=5929" + "@id": "https://portal.ogc.org/files/?artifact_id=1028" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Catalogue Service Implementation Specification [Catalogue Service for the Web]" - }, - { - "@language": "en", - "@value": "04-021r3" + "@value": "01-024r1" }, { "@language": "en", - "@value": "Catalogue Service Implementation Specification" + "@value": "Web Registry Server" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS Catalogue Services Specification defines common interfaces to discover, browse, and query metadata about data, services, and other potential resources." + "@value": "A Registry Service defines a common mechanism to classify, register, describe, search, maintain and access information about OGC Web resources. The OGC Service Registry provides the methods for managing a repository; a Registry Client is an application used to access the Registry." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -83733,1749 +83664,1272 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-021r3" + "@value": "01-024r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Catalogue Service Implementation Specification" - }, - { - "@language": "en", - "@value": "OpenGIS Catalogue Service Implementation Specification [Catalogue Service for the Web]" + "@value": "Web Registry Server" } ] }, { - "@id": "http://www.opengis.net/def/docs/18-085", + "@id": "http://www.opengis.net/def/doc-type/per/collection", "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" + "http://www.w3.org/2004/02/skos/core#Collection" ], - "http://purl.org/dc/terms/created": [ + "http://www.w3.org/2000/01/rdf-schema#label": [ { - "@type": "xsd:date", - "@value": "2019-02-11" + "@value": "Documents of type Public Engineering Report" } ], - "http://purl.org/dc/terms/creator": [ + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Sam Meek" + "@value": "Documents of type Public Engineering Report" } ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/docs" } ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "http://www.w3.org/2004/02/skos/core#member": [ { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/11-089r1" + }, { - "@id": "https://docs.ogc.org/per/18-085.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/11-097" + }, { - "@language": "en", - "@value": "18-085" + "@id": "http://www.opengis.net/def/docs/15-056" }, { - "@language": "en", - "@value": " BPMN Workflow Engineering Report" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/15-026" + }, + { + "@id": "http://www.opengis.net/def/docs/15-028" + }, + { + "@id": "http://www.opengis.net/def/docs/21-044" + }, + { + "@id": "http://www.opengis.net/def/docs/16-055" + }, + { + "@id": "http://www.opengis.net/def/docs/22-014" + }, + { + "@id": "http://www.opengis.net/def/docs/15-066r1" + }, + { + "@id": "http://www.opengis.net/def/docs/22-038r2" + }, + { + "@id": "http://www.opengis.net/def/docs/17-061" + }, + { + "@id": "http://www.opengis.net/def/docs/17-022" + }, + { + "@id": "http://www.opengis.net/def/docs/14-073r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-034" + }, + { + "@id": "http://www.opengis.net/def/docs/20-013r4" + }, + { + "@id": "http://www.opengis.net/def/docs/12-139" + }, + { + "@id": "http://www.opengis.net/def/docs/19-021" + }, + { + "@id": "http://www.opengis.net/def/docs/10-074" + }, + { + "@id": "http://www.opengis.net/def/docs/21-036" + }, + { + "@id": "http://www.opengis.net/def/docs/18-034r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-046r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-064r3" + }, + { + "@id": "http://www.opengis.net/def/docs/21-074r2" + }, + { + "@id": "http://www.opengis.net/def/docs/12-146" + }, + { + "@id": "http://www.opengis.net/def/docs/20-027" + }, + { + "@id": "http://www.opengis.net/def/docs/18-076" + }, + { + "@id": "http://www.opengis.net/def/docs/12-104r1" + }, + { + "@id": "http://www.opengis.net/def/docs/17-040" + }, + { + "@id": "http://www.opengis.net/def/docs/20-033" + }, + { + "@id": "http://www.opengis.net/def/docs/16-050" + }, + { + "@id": "http://www.opengis.net/def/docs/17-090r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-133" + }, + { + "@id": "http://www.opengis.net/def/docs/17-019" + }, + { + "@id": "http://www.opengis.net/def/docs/16-047r1" + }, + { + "@id": "http://www.opengis.net/def/docs/21-058" + }, + { + "@id": "http://www.opengis.net/def/docs/15-047r3" + }, + { + "@id": "http://www.opengis.net/def/docs/16-098" + }, + { + "@id": "http://www.opengis.net/def/docs/21-022" + }, + { + "@id": "http://www.opengis.net/def/docs/12-159" + }, + { + "@id": "http://www.opengis.net/def/docs/20-043" + }, + { + "@id": "http://www.opengis.net/def/docs/17-023" + }, + { + "@id": "http://www.opengis.net/def/docs/16-049r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-086r1" + }, + { + "@id": "http://www.opengis.net/def/docs/20-045" + }, + { + "@id": "http://www.opengis.net/def/docs/10-087" + }, + { + "@id": "http://www.opengis.net/def/docs/17-094r1" + }, + { + "@id": "http://www.opengis.net/def/docs/21-023" + }, + { + "@id": "http://www.opengis.net/def/docs/23-010" + }, + { + "@id": "http://www.opengis.net/def/docs/15-022" + }, + { + "@id": "http://www.opengis.net/def/docs/19-073r1" + }, + { + "@id": "http://www.opengis.net/def/docs/20-067" + }, + { + "@id": "http://www.opengis.net/def/docs/21-031" + }, + { + "@id": "http://www.opengis.net/def/docs/22-020r1" + }, + { + "@id": "http://www.opengis.net/def/docs/15-027r1" + }, + { + "@id": "http://www.opengis.net/def/docs/19-062" + }, + { + "@id": "http://www.opengis.net/def/docs/11-019r2" + }, + { + "@id": "http://www.opengis.net/def/docs/14-079r1" + }, + { + "@id": "http://www.opengis.net/def/docs/14-048" + }, + { + "@id": "http://www.opengis.net/def/docs/15-011r2" + }, + { + "@id": "http://www.opengis.net/def/docs/22-040" + }, + { + "@id": "http://www.opengis.net/def/docs/18-091r2" + }, + { + "@id": "http://www.opengis.net/def/docs/22-054r1" + }, + { + "@id": "http://www.opengis.net/def/docs/09-063" + }, + { + "@id": "http://www.opengis.net/def/docs/20-016" + }, + { + "@id": "http://www.opengis.net/def/docs/18-036r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-042r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-158" + }, + { + "@id": "http://www.opengis.net/def/docs/22-004" + }, + { + "@id": "http://www.opengis.net/def/docs/12-075" + }, + { + "@id": "http://www.opengis.net/def/docs/11-063r6" + }, + { + "@id": "http://www.opengis.net/def/docs/16-024r2" + }, + { + "@id": "http://www.opengis.net/def/docs/23-033" + }, + { + "@id": "http://www.opengis.net/def/docs/16-045r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-035" + }, + { + "@id": "http://www.opengis.net/def/docs/16-023r3" + }, + { + "@id": "http://www.opengis.net/def/docs/12-163" + }, + { + "@id": "http://www.opengis.net/def/docs/16-099" + }, + { + "@id": "http://www.opengis.net/def/docs/21-017r1" + }, + { + "@id": "http://www.opengis.net/def/docs/15-024r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-057" + }, + { + "@id": "http://www.opengis.net/def/docs/15-050r3" + }, + { + "@id": "http://www.opengis.net/def/docs/20-039r2" + }, + { + "@id": "http://www.opengis.net/def/docs/18-101" + }, + { + "@id": "http://www.opengis.net/def/docs/14-006r1" + }, + { + "@id": "http://www.opengis.net/def/docs/13-080r3" + }, + { + "@id": "http://www.opengis.net/def/docs/10-036r2" + }, + { + "@id": "http://www.opengis.net/def/docs/19-022r1" + }, + { + "@id": "http://www.opengis.net/def/docs/18-022r1" + }, + { + "@id": "http://www.opengis.net/def/docs/23-025" + }, + { + "@id": "http://www.opengis.net/def/docs/11-095r1" + }, + { + "@id": "http://www.opengis.net/def/docs/15-051r3" + }, + { + "@id": "http://www.opengis.net/def/docs/09-050r1" + }, + { + "@id": "http://www.opengis.net/def/docs/19-019" + }, + { + "@id": "http://www.opengis.net/def/docs/09-182r1" + }, + { + "@id": "http://www.opengis.net/def/docs/19-070" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/10-073r1" + }, { - "@value": "This Engineering Report (ER) presents the results of the D146 Business Process Modeling Notation (BPMN) Engine work item and provides a study covering technologies including Docker, Kubernetes and Cloud Foundry for Developer Operations (DevOps) processes and deployment orchestration. The document also provides the beginning of a best practices effort to assist implementers wishing to orchestrate OGC services using BPMN workflow engines. As with previous investigations into workflow engines, the implementation described within utilizes a helper class, which is a bespoke implementation of some of the best practices. Work in future testbeds on workflows should include a compelling use case to demonstrate the power of service orchestration." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/20-030" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/16-056" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-085" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/18-089" + }, { - "@language": "en", - "@value": "OGC Testbed-14: BPMN Workflow Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/22-054r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/20-021r2" + }, { - "@type": "xsd:date", - "@value": "2023-06-16" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/19-069" + }, { - "@value": "Gobe Hobona, Joana Simoes " - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/15-052r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/12-119r1" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/20-020" + }, { - "@id": "https://docs.ogc.org/per/22-054r1.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/10-088r3" + }, { - "@language": "en", - "@value": "2022 Web Mapping Code Sprint Summary Engineering Report" + "@id": "http://www.opengis.net/def/docs/11-108" }, { - "@language": "en", - "@value": "22-054r1" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/23-048" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/16-030" + }, { - "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from November 29th to December 1st, 2022 to advance OGC API Standards that relate to web mapping, and others that relate to styling and symbology encoding standards. The code sprint was hosted by the Open Geospatial Consortium (OGC) and EuroGeographics. The code sprint was sponsored by Ordnance Survey (OS), and was held as a hybrid event with the face-to-face element hosted at the Mundo Madou centre in Brussels, Belgium." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/16-059" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/21-055" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "22-054r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/15-010r4" + }, { - "@language": "en", - "@value": "2022 Web Mapping Code Sprint Summary Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/06-131r4", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/12-154" + }, { - "@type": "xsd:date", - "@value": "2008-07-08" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/14-049" + }, { - "@value": "Renato Primavera" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/22-024r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/d-bp" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/13-054r1" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/18-045" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=28152" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/12-160r1" + }, { - "@language": "en", - "@value": "OGC® Catalogue Services Specification 2.0 Extension Package for ebRIM (ISO/TS 15000-3) Application Profile: Earth Observation" + "@id": "http://www.opengis.net/def/docs/16-033r1" }, { - "@language": "en", - "@value": "06-131r4" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/11-113r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/d-bp" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/11-073r2" + }, { - "@value": "This OGC® document specifies the Earth Observation Products Extension Package for ebRIM (ISO/TS 15000-3) Application Profile of CSW 2.0, based on the [OGC 06-080r3] OGC® GML Application Schema for EO Products." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/18-086r1" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/23-020r2" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-131r4" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/09-012" + }, { - "@language": "en", - "@value": "EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/07-118r9", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/18-048r1" + }, { - "@type": "xsd:date", - "@value": "2014-04-28" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/10-192" + }, { - "@value": "P. Denis, P. Jacques" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/12-105" + }, { - "@id": "http://www.opengis.net/def/doc-type/bp" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/12-093" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/21-025" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=54929" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/12-018r1" + }, { - "@language": "en", - "@value": "User Management Interfaces for Earth Observation Services" + "@id": "http://www.opengis.net/def/docs/21-035r1" }, { - "@language": "en", - "@value": "07-118r9" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/16-038" + }, { - "@id": "http://www.opengis.net/def/doc-type/bp" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/19-015" + }, { - "@value": "This OGC Best Practice describes how user and identity management information may be included in the protocol specifications for OGC Services. The proposed approach is applicable to the orchestration of EO services, to system of systems and federation scenarios. The approach is meant to be independent from the specific OGC service. The use cases potentially addressed are very wide and in general may cover geospatial services and not only EO (Earth Observation) services. The use cases may range from web map, feature or coverage services, web processing services, to catalogue services. Examples of EO specific use cases are: ordering (Ordering Services for Earth Observation Products [OGC 06-141r6]) and feasibility analysis (OpenGIS Sensor Planning Service Application Profile for EO Sensors [OGC 10 135]). \r\nThe document was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [OR1] and related projects.\r\nThis document is not an OGC standard. This document describes how existing specifications from W3C and OASIS can be used in combination to pass identity information to OGC Web services.\r\n" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/14-029r2" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/11-062r2" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-118r9" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/12-095" + }, { - "@language": "en", - "@value": "OGC User Management Interfaces for Earth Observation Services" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/17-026r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/19-003" + }, { - "@type": "xsd:date", - "@value": "2018-02-22" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/09-067r2" + }, { - "@value": "Rob Cass" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/18-021" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/23-011r1" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/17-042" + }, { - "@id": "https://docs.ogc.org/per/17-026r1.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/18-090r2" + }, { - "@language": "en", - "@value": "Testbed-13: Disconnected Networks Engineering Report" + "@id": "http://www.opengis.net/def/docs/16-036r1" }, { - "@language": "en", - "@value": "17-026r1" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/13-053r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/16-097" + }, { - "@value": "The design of core OGC Web Services (OWS) does not entertain the possibility of network unavailability, internet unavailability, or disconnected clients and datastores. Deployments of these services, and the clients that consume them, often happen in networking environments that have limited bandwidth, sporadic connectivity and no connection to the internet. This Engineering Report (ER) focuses on situations of Denied, Degraded, Intermittent, or Limited Bandwidth (DDIL). Due to these DDIL networking limitations, OWS services and clients may not be capable of effective data exchange and interpretation due to a reliance on external resources and always-on networks.\r\n\r\nThis ER concerns the behavior of common OWS services when used in DDIL environments. The ER documents proposed practices/considerations for implementation of these services to support these environments. The ER also describes software modules or extensions that might mitigate the effects of these environments on both clients and services.\r\n\r\nThis ER intends to guide client and service implementation, as well as deployment strategies for these challenging environments.\r\n\r\n" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/17-036" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/19-032" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-026r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/16-034" + }, { - "@language": "en", - "@value": "OGC Testbed-13: Disconnected Networks Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/12-128r12", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/15-082" + }, { - "@type": "xsd:date", - "@value": "2015-08-04" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/24-008" + }, { - "@value": "Jeff Yutzler" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/14-002" + }, { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/20-037" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/16-041r1" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=64506" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/11-061r1" + }, { - "@language": "en", - "@value": "GeoPackage Encoding Standard" + "@id": "http://www.opengis.net/def/docs/09-041r3" }, { - "@language": "en", - "@value": "12-128r12" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/18-038r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/14-044" + }, { - "@value": "This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector\r\ngeospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access\r\nand update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that\r\nguarantees data model and data set integrity and identical access and update results in response to identical requests from different\r\nclient applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly\r\nuseful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/14-039" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/16-022" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-128r12" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/21-039r1" + }, { - "@language": "en", - "@value": "OGC® GeoPackage Encoding Standard" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/19-003", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/21-019" + }, { - "@type": "xsd:date", - "@value": "2019-09-24" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/11-086r1" + }, { - "@value": "Tom Landry, David Byrns" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/09-037r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/21-021" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/10-194r3" + }, { - "@id": "https://docs.ogc.org/per/19-003.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/18-023r1" + }, { - "@language": "en", - "@value": "19-003" + "@id": "http://www.opengis.net/def/docs/17-035" }, { - "@language": "en", - "@value": "Earth System Grid Federation (ESGF) Compute Challenge" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/19-023r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/19-026" + }, { - "@value": "This Open Geospatial Consortium (OGC) Engineering Report (ER) will describe the advancement of an Execution Management System (EMS) to support Web Processing Service (WPS) climate processes deployed on the Earth System Grid Federation (ESGF). The report introduces climate data, processes and applications into Common Workflow Language (CWL) workflows with the intent of advancing: application packaging, deployment and execution in clouds; interoperability of services in federated cyberinfrastructures; and geospatial workflows towards standardization. Work presented in this report is a direct continuation of the Earth Observation & Clouds (EOC) thread of Testbed-14. This report is expected to be of relevance to Testbed-15, both to the Earth Observation Process and Application Discovery (EOPAD) task and the Machine Learning task. This engineering report will describe: relevant work conducted in OGC Testbed-14; ESGF and its compute challenge; adaptations of existing climate processes into workflows; interoperability experiments with ESGF endpoints conforming to a common API." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/11-096" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/16-020" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-003" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/19-082r1" + }, { - "@language": "en", - "@value": "Earth System Grid Federation (ESGF) Compute Challenge" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/17-036", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/09-064r2" + }, { - "@type": "xsd:date", - "@value": "2018-01-11" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/17-021" + }, { - "@value": "Charles Chen" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/16-039r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/09-016" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/10-002" + }, { - "@id": "https://docs.ogc.org/per/17-036.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/09-053r5" + }, { - "@language": "en", - "@value": "Testbed-13: Geospatial Taxonomies Engineering Report" + "@id": "http://www.opengis.net/def/docs/20-029" }, { - "@language": "en", - "@value": "17-036" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/14-017" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/10-060r1" + }, { - "@value": "This Engineering Report (ER) documents the Geospatial Taxonomy research activities conducted by the Aviation (AVI) subthread of the Cross Community Interoperability (CCI) thread in OGC Testbed 13. One of the critical factors in the overall usability of services - and System Wide Information Management (SWIM) enabled services in particular - is the ability of a service to be discovered. The ability of a service to be discovered is assured by providing a uniformly interpretable set of service metadata that can be accessed by a service consumer through a retrieval mechanism (e.g., a service registry). Such a set of metadata (commonly referred to as a service description) has been defined by Federal Aviation Administration (FAA) and European Organization for the Safety of Air Navigation (EUROCONTROL) and formalized in a Service Description Conceptual Model (SDCM) [SDCM].\r\n\r\nThe SDCM is currently used in standard service description documents and service registries by both FAA and EUROCONTROL. As part of the effort of enhancing service discovery, both organizations also use a number of categories that can be associated with all services and are generally referred to as taxonomies. The current set of taxonomies used by both EUROCONTROL and FAA categorizes (i.e., meta tags) services based on their availability status, interface model, data product, etc. However, despite the increasing role of OGC services in the SWIM environment, no taxonomies for categorizing services based on geographical coverage or other geospatial characteristics have been defined. This ER documents the work conducted as part of Testbed 13 CCI thread and AVI subthread to identify and classify SWIM-enabled Service Oriented Architecture (SOA) services with geographical taxonomies and the integration thereof into SDCM." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/20-034" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/09-032" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-036" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/14-008" + }, { - "@language": "en", - "@value": "OGC Testbed-13: Geospatial Taxonomies Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/pol", - "http://www.w3.org/2004/02/skos/core#narrower": [ + "@id": "http://www.opengis.net/def/docs/23-027" + }, { - "@id": "http://www.opengis.net/def/docs/09-144r2" + "@id": "http://www.opengis.net/def/docs/14-038r1" }, { - "@id": "http://www.opengis.net/def/docs/08-131r3" + "@id": "http://www.opengis.net/def/docs/17-026r1" }, { - "@id": "http://www.opengis.net/def/docs/09-046r5" + "@id": "http://www.opengis.net/def/docs/12-152r1" }, { - "@id": "http://www.opengis.net/def/docs/09-046r6" + "@id": "http://www.opengis.net/def/docs/16-031r1" }, { - "@id": "http://www.opengis.net/def/docs/08-134r11" + "@id": "http://www.opengis.net/def/docs/15-118r1" }, { - "@id": "http://www.opengis.net/def/docs/05-020r29" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/03-109r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/18-032r2" + }, { - "@type": "xsd:date", - "@value": "2004-02-18" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/17-045" + }, { - "@value": "Jeff de La Beaujardiere" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/20-036" + }, { - "@id": "http://www.opengis.net/def/doc-type/d-rp" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/15-065r1" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/22-043r1" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=4756" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/18-049r1" + }, { - "@language": "en", - "@value": "Web Map Service (Recommendation Paper)" + "@id": "http://www.opengis.net/def/docs/11-116" }, { - "@language": "en", - "@value": "03-109r1" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/20-038" + }, { - "@id": "http://www.opengis.net/def/doc-type/d-rp" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/18-085" + }, { - "@value": "Provides three operations (GetCapabilities, GetMap, and GetFeatureInfo) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. " - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/13-046r2" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/18-026r1" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "03-109r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/20-015r2" + }, { - "@language": "en", - "@value": "Web Map Service" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/05-111r2", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/11-055" + }, { - "@type": "xsd:date", - "@value": "2006-05-09" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/10-069r2" + }, { - "@value": "Roland M. Wagner" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/09-015" + }, { - "@id": "http://www.opengis.net/def/doc-type/dp" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/19-025r1" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/18-094r1" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=13958" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/12-097" + }, { - "@language": "en", - "@value": "Access Control & Terms of Use (ToU) \"Click-through\" IPR Management" + "@id": "http://www.opengis.net/def/docs/18-074" }, { - "@language": "en", - "@value": "05-111r2" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/11-107" + }, { - "@id": "http://www.opengis.net/def/doc-type/dp" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/16-115" + }, { - "@value": "This document demonstrats a number of functional capabilities related to rights management (Terms-of-Use, Authentication, content services) that need to be described and chained. " - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/19-010r2" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/12-096" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-111r2" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/16-093r1" + }, { - "@language": "en", - "@value": "Access Control & Terms of Use (ToU) \"Click-through\" IPR Management" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/09-084r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/17-024" + }, { - "@type": "xsd:date", - "@value": "2009-10-13" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/17-088r1" + }, { - "@value": "Jo Walsh, Pedro Gonçalves, Andrew Turner" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/11-093r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/dp" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/21-028" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/21-054" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=35983" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/15-068r2" + }, { - "@language": "en", - "@value": "OpenSearch Geospatial Extensions Draft Implementation Standard" + "@id": "http://www.opengis.net/def/docs/09-036r2" }, { - "@language": "en", - "@value": "09-084r1" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/12-118" + }, { - "@id": "http://www.opengis.net/def/doc-type/dp" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/09-072" + }, { - "@value": "The OpenSearch specification originates in a community effort built around Amazon's A9.com. It was intended to allow syndication of search results that could then be aggregated by one large index. The OpenSearch specification is made available under the Creative Commons Attribution-Sharealike 2.5 license. In addition, the OASIS Search Web Services group is publishing an Abstract Protocol Definition of the interface or “binding”, which coincides with the community specification published at http://opensearch.org. In 2007, Andrew Turner proposed a set of geospatial extensions through OpenSearch.org." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/16-052" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/16-053r1" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-084r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/16-094r3" + }, { - "@language": "en", - "@value": "OpenSearch Geospatial Extensions Draft Implementation Standard" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/20-037", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/15-025r2" + }, { - "@type": "xsd:date", - "@value": "2020-10-22" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/21-027" + }, { - "@value": "Samantha Lavender" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/21-008" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/18-009" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/19-027r2" + }, { - "@id": "https://docs.ogc.org/per/20-037.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/18-029" + }, { - "@language": "en", - "@value": "OGC Earth Observation Applications Pilot: Pixalytics Engineering Report" + "@id": "http://www.opengis.net/def/docs/19-046r1" }, { - "@language": "en", - "@value": "20-037" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/14-009r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/10-059r2" + }, { - "@value": "This is an individual Engineering Report (ER) created by Pixalytics Ltd as part of the Earth Observation Applications Pilot. Pixalytics' role was that of an App developer, testing deployment to the OGC Earth Observation Applications Pilot architecture." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/20-032" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/15-057r2" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-037" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/18-087r5" + }, { - "@language": "en", - "@value": "OGC Earth Observation Applications Pilot: Pixalytics Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/18-049r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/17-041" + }, { - "@type": "xsd:date", - "@value": "2019-02-07" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/17-037" + }, { - "@value": "Paulo Sacramento" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/19-083" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/19-007" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/20-073" + }, { - "@id": "https://docs.ogc.org/per/18-049r1.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/12-018r2" + }, { - "@language": "en", - "@value": "18-049r1" + "@id": "http://www.opengis.net/def/docs/11-072r2" }, { - "@language": "en", - "@value": "Application Package Engineering Report" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/19-030r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/19-081" + }, { - "@value": "This Engineering Report (ER) describes the work performed by the Participants in the Exploitation Platforms Earth Observation Clouds (EOC) Thread of OGC Testbed-14 in regard to the Application Package (AP).\r\n\r\nThe AP serves as a means to convey different kinds of information describing a certain application - often, but not necessarily, an Earth Observation data processing algorithm - so that different elements of an ecosystem generically known as an Exploitation Platform can exchange information among themselves in a standard and interoperable way. The AP guarantees that, despite potentially very heterogeneous implementations and implementing entities, applications are treated equally. The AP also guarantees that the Earth Observation scientist who developed it on the one hand is shielded from infrastructure details and heterogeneity and on the other hand benefits from the ability to execute the same application on different infrastructure.\r\n\r\nGiven its suitability for conveying a Common Operating Picture (COP), in OGC Testbed-13 the OGC Web Services (OWS) Context standard had been chosen as the basic encoding for the Application Package. Despite serious consideration, and while acknowledging the advantages of that approach, the consensus among Participants was not to continue along this path in Testbed-14 but instead to opt for an AP encoding, consisting of a WPS-T (Transactional Web Processing Service (WPS)) DeployProcess message encoded in JSON (see Chapter 9 for the rationale). The information model conveyed in this manner does not differ significantly from the one that could be conveyed using OWS Context, and its main, common features can be briefly listed as:\r\n\r\na link to the application execution unit,\r\n\r\na description of the application’s inputs and outputs,\r\n\r\nlinks to required Earth Observation data catalogues,\r\n\r\nand the possibility to pass other auxiliary information.\r\n\r\nAn important difference in Testbed-14 with respect to Testbed-13 is that the application execution unit is not limited to a Docker container, but can also be a workflow described in Common Workflow Language (CWL), something which stems directly from one of the Sponsor requirements. Finally, it is important to note that this route does not preclude from embedding an OWS Context structure in the enclosing DeployProcess document if this is desired.\r\n\r\nStarting from the lessons learned and limitations identified in Testbed-13, and embracing the new and changed Sponsor requirements, this ER explains the trade-offs, decisions and conclusions taken by the Participants throughout the project." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/19-040" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/20-012" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "18-049r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/14-114r1" + }, { - "@language": "en", - "@value": "OGC Testbed-14: Application Package Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/10-061r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/16-063" + }, { - "@type": "xsd:date", - "@value": "2010-06-30" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/19-018" + }, + { + "@id": "http://www.opengis.net/def/docs/12-147" + }, + { + "@id": "http://www.opengis.net/def/docs/16-048r1" + }, + { + "@id": "http://www.opengis.net/def/docs/14-086r1" + }, + { + "@id": "http://www.opengis.net/def/docs/21-032" + }, { - "@value": "Johannes Echterhoff, Ingo Simonis" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/19-075r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/09-129" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/18-028r2" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=39513" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/23-047" + }, { - "@language": "en", - "@value": "OWS-7 Dynamic Sensor Notification Engineering Report" + "@id": "http://www.opengis.net/def/docs/11-091" }, { - "@language": "en", - "@value": "10-061r1" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/20-090" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/08-176r1" + }, { - "@value": "This document is applicable to scenarios where moving sensors need to be tracked and their entry into an area of interest needs to be detected.\r\n\r\nThe document presents a detailed discussion of different approaches for encoding tracked object position.\r\n\r\nTwo approaches for implementing dynamic sensor tracking and notification are described, one based on the Sensor Alert Service specification and the other based on the Sensor Event Service specification.\r\n\r\nAn overview of standards and specifications relevant for and related to dynamic sensor tracking and notification is provided.\r\n" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/19-016r1" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/17-027" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-061r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/09-035" + }, { - "@language": "en", - "@value": "OWS-7 Dynamic Sensor Notification Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/10-130", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/16-064r1" + }, { - "@type": "xsd:date", - "@value": "2010-08-18" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/22-041" + }, { - "@value": "Debbie Wilson" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/16-062" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/22-023r2" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/21-064" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=40114" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/19-012r1" + }, { - "@language": "en", - "@value": "10-130" + "@id": "http://www.opengis.net/def/docs/18-025" }, { - "@language": "en", - "@value": "OWS-7 Aviation - FUSE Deployment Engineering Report" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/11-139r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/14-007" + }, { - "@value": "This document describes the integration results of deploying OGC Web Services on the FAA chosen Enterprise Service Bus (ESB) - FUSE. Snowflake Software were commissioned to evaluate the impacts of the FAA SWIM security requirements for both secure messaging and user authentication and gain an understanding of the requirements for deploying OGC web services into the Apache FUSE Enterprise Service Bus (ESB)." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/20-041" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/11-013r6" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-130" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/18-083" + }, { - "@language": "en", - "@value": "OWS-7 Aviation - FUSE Deployment Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/21-032", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/16-021r1" + }, { - "@type": "xsd:date", - "@value": "2022-01-24" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/10-155" + }, { - "@value": "Giovanni Giacco, Mauro Manente, Pedro Gonçalves, Martin Desruisseaux, Even Rouault" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/16-037" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/11-114" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/16-068r4" + }, { - "@id": "https://docs.ogc.org/per/21-032.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/23-059" + }, { - "@language": "en", - "@value": "21-032" + "@id": "http://www.opengis.net/def/docs/17-032r2" }, { - "@language": "en", - "@value": "OGC Testbed 17: COG/Zarr Evaluation Engineering Report" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/18-084" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/20-083r2" + }, { - "@value": "The subject of this Engineering Report (ER) is the evaluation of Cloud Optimized GeoTIFF (COG) and Zarr data container implementations. The ER aims to:\r\n\r\n Describe the use cases adopted for the evaluation (with existing implementation and with Testbed-17 implementation);\r\n Identify the opportunity of proposing that COG and Zarr become OGC standards;\r\n Describe all components developed during the Testbed; and\r\n Provide an executive summary and a description of recommended future work items." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/12-157" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/18-030" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-032" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/12-144" + }, { - "@language": "en", - "@value": "OGC Testbed 17: COG/Zarr Evaluation Engineering Report" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/21-077", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/21-042" + }, { - "@type": "xsd:date", - "@value": "2022-05-06" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/09-006" + }, { - "@value": "Taehoon Kim, Wijae Cho, Kyoung-Sook Kim" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/12-162r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/dp" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/10-061r1" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/11-106r1" + }, { - "@id": "https://docs.ogc.org/dp/21-077.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/15-048r3" + }, { - "@language": "en", - "@value": "The HDF5 profile for labeled point cloud data" + "@id": "http://www.opengis.net/def/docs/16-043" }, { - "@language": "en", - "@value": "21-077" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/10-127r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/dp" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/09-007" + }, { - "@value": "Point cloud data are unstructured three-dimensional sample points to express the basic shape of objects and spaces. However, it is challenging to automatically generate continuous surfaces and infer semantic structures, such as cars, trees, buildings and roads, from a dataset of point clouds generated by a sensor. The understanding of the semantic structures is essential for recording geospatial information. Despite the good performance of deep learning-based approaches in understanding point clouds, their target coverage is still limited by the lack of training datasets that include semantic labels. This discussion paper addresses data formats to share a Labeled Point Cloud (LPC), in which point-level semantic information is annotated to each point.\r\n\r\nCreating LPCs manually or semi-manually is a time-consuming task. Therefore, sharing LPCs in an open standard format is becoming increasingly important for the development of more advanced deep learning algorithms for object detection, semantic segmentation, and instance segmentation. Even though several data formats are used to distribute LPC, there is a variety to represent the semantic information depending on distributors or domains. This discussion paper analyzes three popular formats of ASCII text, PLY, and LAS, for supporting LPC and finally proposes a practice to effectively apply HDF5 to facilitate the sharing and importing of LPC datasets." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/17-093r1" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/21-029" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-077" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/17-043" + }, { - "@language": "en", - "@value": "The HDF5 profile for labeled point cloud data" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/05-027r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/19-024r1" + }, { - "@type": "xsd:date", - "@value": "2005-04-13" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/14-016" + }, { - "@value": "Arliss Whiteside" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/20-019r1" + }, { - "@id": "http://www.opengis.net/def/doc-type/d-bp" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/23-050" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/09-075r1" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=10048" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/15-054" + }, { - "@language": "en", - "@value": "Recommended XML/GML 3.1.1 encoding of image CRS definitions" + "@id": "http://www.opengis.net/def/docs/23-028" }, { - "@language": "en", - "@value": "05-027r1" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/14-021r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/d-bp" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/09-140r2" + }, { - "@value": "This document recommends standard XML encodings of data defining monoscopic image coordinate reference systems. The scope of this encoding now includes unrectified and georectified images. The recommended CRSs for georectified images are recommended for multiple georectified images that are ready to be mosaicked together.\r\n\r\nThese recommended encodings are based on GML 3.1.1 and use XML Schemas. These image CRS definitions will often be referenced in data transferred between client and server software that implements various standardised interfaces. This specified definition data encoding is expected to be used by multiple OGC Implementation Specifications. That is, each of these specifications is expected to use a subset and/or superset of this recommended definition data.\r\n\r\nThe position or location of a point can be described using coordinates. Such coordinates are unambiguous only when the coordinate reference system on which those coordinates are based is fully defined. Each position is described by a set of coordinates based on a specified coordinate reference system. Coordinates are often used in datasets in which all coordinates belong to the same coordinate reference system. This paper specifies XML encoding of data defining image coordinate reference systems.\r\n" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/19-084" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/16-018" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-027r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/10-130" + }, { - "@language": "en", - "@value": "Recommended XML/GML 3.1.1 encoding of image CRS definitions" - } - ] - }, - { - "@id": "http://www.opengis.net/def/doc-type/isc/collection", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" - ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "@id": "http://www.opengis.net/def/docs/16-067r4" + }, { - "@value": "Documents of type OGC Implementation Specification Corrigendum" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/20-011" + }, { - "@value": "Documents of type OGC Implementation Specification Corrigendum" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/16-028r1" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#member": [ + "@id": "http://www.opengis.net/def/docs/10-079r3" + }, { - "@id": "http://www.opengis.net/def/docs/09-147r3" + "@id": "http://www.opengis.net/def/docs/15-073r2" }, { - "@id": "http://www.opengis.net/def/docs/07-010" + "@id": "http://www.opengis.net/def/docs/21-030" }, { - "@id": "http://www.opengis.net/def/docs/14-065r1" + "@id": "http://www.opengis.net/def/docs/10-132" }, { - "@id": "http://www.opengis.net/def/docs/07-122r2" + "@id": "http://www.opengis.net/def/docs/17-029r1" }, { - "@id": "http://www.opengis.net/def/docs/08-091r6" + "@id": "http://www.opengis.net/def/docs/17-048" }, { - "@id": "http://www.opengis.net/def/docs/16-083r3" + "@id": "http://www.opengis.net/def/docs/14-013r1" }, { - "@id": "http://www.opengis.net/def/docs/04-094r1" + "@id": "http://www.opengis.net/def/docs/10-184" }, { - "@id": "http://www.opengis.net/def/docs/08-050" + "@id": "http://www.opengis.net/def/docs/09-038r1" }, { - "@id": "http://www.opengis.net/def/docs/09-083r4" + "@id": "http://www.opengis.net/def/docs/22-018" }, { - "@id": "http://www.opengis.net/def/docs/11-157" + "@id": "http://www.opengis.net/def/docs/22-035" }, { - "@id": "http://www.opengis.net/def/docs/18-075" + "@id": "http://www.opengis.net/def/docs/18-046" }, { - "@id": "http://www.opengis.net/def/docs/07-045r2" + "@id": "http://www.opengis.net/def/docs/16-092r2" }, { - "@id": "http://www.opengis.net/def/docs/06-027r1" + "@id": "http://www.opengis.net/def/docs/10-131r1" }, { - "@id": "http://www.opengis.net/def/docs/09-026r2" + "@id": "http://www.opengis.net/def/docs/15-058" }, { - "@id": "http://www.opengis.net/def/docs/14-005r5" + "@id": "http://www.opengis.net/def/docs/20-042" }, { - "@id": "http://www.opengis.net/def/docs/07-036r1" + "@id": "http://www.opengis.net/def/docs/10-094" }, { - "@id": "http://www.opengis.net/def/docs/12-128r12a" + "@id": "http://www.opengis.net/def/docs/18-078" }, { - "@id": "http://www.opengis.net/def/docs/18-010r11" + "@id": "http://www.opengis.net/def/docs/21-013" }, { - "@id": "http://www.opengis.net/def/docs/09-146r8" + "@id": "http://www.opengis.net/def/docs/20-091" }, { - "@id": "http://www.opengis.net/def/docs/11-158" + "@id": "http://www.opengis.net/def/docs/12-156" }, { - "@id": "http://www.opengis.net/def/docs/14-005r4" + "@id": "http://www.opengis.net/def/docs/18-050r1" }, { - "@id": "http://www.opengis.net/def/docs/07-045r1" + "@id": "http://www.opengis.net/def/docs/17-025r2" }, { - "@id": "http://www.opengis.net/def/docs/14-065r2" + "@id": "http://www.opengis.net/def/docs/16-029r1" }, { - "@id": "http://www.opengis.net/def/docs/12-128r15" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/12-103r3" + }, { - "@value": "Documents of type OGC Implementation Specification Corrigendum" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/09-044r3", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/09-073" + }, { - "@type": "xsd:date", - "@value": "2012-07-12" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/19-041r3" + }, { - "@value": "George Percivall, Raj Singh" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/12-155" + }, { - "@id": "http://www.opengis.net/def/doc-type/techpaper" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/11-085r1" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/14-001" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=49321" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/22-017" + }, { - "@language": "en", - "@value": "Geospatial Business Intelligence (GeoBI)" + "@id": "http://www.opengis.net/def/docs/12-094" }, { - "@language": "en", - "@value": "09-044r3" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/09-138" + }, + { + "@id": "http://www.opengis.net/def/docs/12-151" + }, { - "@id": "http://www.opengis.net/def/doc-type/techpaper" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/09-033" + }, { - "@value": "BI is an umbrella term for a major component of IT infrastructure. It encompasses Data\r\nWarehouses, Business Analytics, Dashboards and Scorecards. This IT infrastructure is associated\r\nwith C-level decision-making in an organization. These decision-making tools have typically\r\nincluded location as a dumb attribute (coded sales zones as opposed to sales zones as geographic\r\nboundaries). At this point in the BI lifecycle, customers are looking to derive additional business\r\nbenefit / return on investment from intelligent location data; data discovery and unstructured data." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/16-014r2" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/08-124r1" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-044r3" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/16-017" + }, { - "@language": "en", - "@value": "Geospatial Business Intelligence (GeoBI)" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/99-050", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/16-051" + }, { - "@type": "xsd:date", - "@value": "1999-05-18" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/13-032" + }, { - "@value": "TC Chair" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/18-047r3" + }, { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/19-088r2" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/20-035" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=830" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/22-016r3" + }, { - "@language": "en", - "@value": "99-050" + "@id": "http://www.opengis.net/def/docs/17-018" }, { - "@language": "en", - "@value": "Simple Features Implementation Specification for OLE/COM" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/15-046r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/20-031" + }, { - "@value": "The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc)." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/17-078" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/15-053r1" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "99-050" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/16-044" + }, { - "@language": "en", - "@value": "OpenGIS Simple Features Implementation Specification for OLE/COM" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/16-106r2", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/21-020r1" + }, { - "@type": "xsd:date", - "@value": "2017-08-16" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/19-020r1" + }, { - "@value": "Hans-Christoph Gruler" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/20-087" + }, { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/16-040r1" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/09-031r1" + }, { - "@id": "https://portal.ogc.org/files/?artifact_id=75123" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/17-046" + }, { - "@language": "en", - "@value": "InfraGML 1.0: Part 6 – LandInfra Survey - Encoding Standard" + "@id": "http://www.opengis.net/def/docs/14-037" }, { - "@language": "en", - "@value": "16-106r2" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/11-134" + }, { - "@id": "http://www.opengis.net/def/doc-type/is" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/16-088r1" + }, { - "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 6 addresses the Survey, Equipment, Observations and Survey Results Requirements Classes from LandInfra." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/23-044" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/20-025r1" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-106r2" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/22-031r1" + }, { - "@language": "en", - "@value": "OGC InfraGML 1.0: Part 6 – LandInfra Survey - Encoding Standard" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/19-078r1", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/17-028" + }, { - "@type": "xsd:date", - "@value": "2020-10-05" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/18-090r1" + }, { - "@value": "Joseph Abhayaratna, Linda van den Brink, Nicholas Car, Rob Atkinson, Timo Homburg, Frans Knibbe, Kri" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/16-137r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/techpaper" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/16-027" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/16-035" + }, { - "@id": "https://docs.ogc.org/wp/19-078r1/19-078r1.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/14-000" + }, { - "@language": "en", - "@value": "19-078r1" + "@id": "http://www.opengis.net/def/docs/20-018" }, { - "@language": "en", - "@value": "OGC Benefits of Representing Spatial Data Using Semantic and Graph Technologies" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/16-061" + }, { - "@id": "http://www.opengis.net/def/doc-type/techpaper" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/09-156r2" + }, { - "@value": "This paper does four things. Firstly, it describes the benefits of representing geospatial data using semantics, graph, and web technologies. Secondly, it gives an overview of the current capabilities of the GeoSPARQL standard, showing that many benefits of semantic and graph technologies are already within reach. Thirdly, it outlines some shortcomings of the existing GeoSPARQL implementation specification that, if addressed, would unlock its potential to a greater extent, and could significantly increase its user base. Finally, it identifies other related activities that are current at the time of editing this paper. In doing so, it establishes liaison’s between the different activities in an attempt to achieve alignment.\r\n\r\nThe purpose of this paper is to provoke further thought about a best course for further development of the GeoSPARQL standard, and to invite active involvement in that development. Particularly, the involvement of people and organizations that until now have not been able to put GeoSPARQL to good use, either because of perceived limitations or because of unfamiliarity with the standard, will be highly valued. Also, since one development under consideration is to make provisions for use of GeoSPARQL with non-geographic spatial data, those that see opportunities for using spatial data in a broad sense together with the aforementioned technologies are cordially invited to share their views." - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/15-077r1" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/11-092r2" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-078r1" - } - ], - "http://www.w3.org/2004/02/skos/core#prefLabel": [ + "@id": "http://www.opengis.net/def/docs/14-028r1" + }, { - "@language": "en", - "@value": "OGC Benefits of Representing Spatial Data Using Semantic and Graph Technologies" - } - ] - }, - { - "@id": "http://www.opengis.net/def/docs/16-098", - "@type": [ - "http://www.w3.org/2004/02/skos/core#Concept" - ], - "http://purl.org/dc/terms/created": [ + "@id": "http://www.opengis.net/def/docs/15-030r3" + }, { - "@type": "xsd:date", - "@value": "2017-10-20" - } - ], - "http://purl.org/dc/terms/creator": [ + "@id": "http://www.opengis.net/def/docs/13-011" + }, { - "@value": "Kanishk Chaturvedi, Thomas H. Kolbe" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ + "@id": "http://www.opengis.net/def/docs/15-067" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.opengis.net/def/metamodel/ogc-na/status": [ + "@id": "http://www.opengis.net/def/docs/17-038" + }, { - "@id": "http://www.opengis.net/def/status/valid" - } - ], - "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + "@id": "http://www.opengis.net/def/docs/23-042" + }, { - "@id": "https://docs.ogc.org/per/16-098.html" - } - ], - "http://www.w3.org/2004/02/skos/core#altLabel": [ + "@id": "http://www.opengis.net/def/docs/21-018" + }, { - "@language": "en", - "@value": "Future City Pilot 1 Engineering Report" + "@id": "http://www.opengis.net/def/docs/23-043" }, { - "@language": "en", - "@value": "16-098" - } - ], - "http://www.w3.org/2004/02/skos/core#broader": [ + "@id": "http://www.opengis.net/def/docs/21-075r2" + }, { - "@id": "http://www.opengis.net/def/doc-type/per" - } - ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "@id": "http://www.opengis.net/def/docs/17-020r1" + }, { - "@value": "The Future City Pilot Phase 1 (FCP1) is an OGC Interoperability Program initiative in collaboration with buildingSMART International (bSI). The pilot aimed at demonstrating and enhancing the ability of spatial data infrastructures to support quality of life, civic initiatives, and urban resilience. During the pilot, multiple scenarios were set up based on real-world requirements and were put forward by the pilot sponsors: Sant Cugat del Vallès (Barcelona, Spain), Ordnance Survey Great Britain (UK), virtualcitySYSTEMS GmbH (Germany), and Institut National de l’Information Géographique et Forestière - IGN (France). The scenarios were focused on (i) the interoperability between the two international standards: Industry Foundation Classes (IFC) and CityGML; (ii) city flood modeling; and (iii) supporting real-time sensor readings and other time-dependent properties within semantic 3D city models. The solutions for the respective scenarios were developed by the pilot participants: University of Melbourne (Australia), Remote Sensing Solutions, Inc. (U.S.A), and Technical University of Munich (Germany). This Engineering Report (ER) focuses on the third scenario requiring the support of real-time sensors and other time-dependent properties within semantic 3D city models based on the CityGML standard. It highlights a new concept 'Dynamizer', which allows representation of highly dynamic data in different and generic ways and providing a method for injecting dynamic variations of city object properties into the static representations. It also establishes explicit links between sensor/observation data and the respective properties of city model objects that are measured by them. The Dynamizer concept has been implemented as an Application Domain Extension (ADE) of the CityGML standard. This implementation allows to use new dynamizer features with the current version of the CityGML standard (CityGML 2.0). The advantage with this approach is that it allows for selected properties of city models to become dynamic without changing the original CityGML data model. If an application does not support dynamic data, it simply does not allow/include these special types of features. The details and results of the pilot are mentioned in the following YouTube video: https://youtu.be/aSQFIPwf2oM" - } - ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "@id": "http://www.opengis.net/def/docs/18-097" + }, { - "@id": "http://www.opengis.net/def/docs" - } - ], - "http://www.w3.org/2004/02/skos/core#notation": [ + "@id": "http://www.opengis.net/def/docs/10-035r2" + }, { - "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-098" + "@id": "http://www.opengis.net/def/docs/14-057" + }, + { + "@id": "http://www.opengis.net/def/docs/22-013r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@language": "en", - "@value": "Future City Pilot 1 Engineering Report" + "@value": "Documents of type Public Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-194r3", + "@id": "http://www.opengis.net/def/docs/99-103", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-03-22" + "@value": "1999-03-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Boyan Brodaric, Nate Booth" + "@value": "Cliff Kottman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -85485,27 +84939,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=43545" + "@id": "https://portal.ogc.org/files/?artifact_id=886" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Groundwater Interoperability Experiment FINAL REPORT" + "@value": "99-103" }, { "@language": "en", - "@value": "10-194r3" + "@value": "Topic 03 - Locational Geometry Structures" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/retired" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This report describes the methods, results, issues and recommendations generated by the\r\nGroundwater Interoperability Experiment (GWIE). As an activity of the OGC Hydrology\r\nDomain Working Group (HDWG), the GWIE is designed to: (1) test the use of\r\nWaterML2 with the SOS interface, and Groundwater ML (GWML) with the WFS\r\ninterface, (2) test compatibility with software clients, and (3) facilitate sharing of massive\r\nvolumes of sensor-based water level observations and related water well features across\r\nthe Canada and United States border. " + "@value": "Provides essential and abstract models for GIS technology that is widely used." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -85516,35 +84970,46 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-194r3" + "@value": "99-103" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Groundwater Interoperability Experiment FINAL REPORT" + "@value": "Topic 3 - Locational Geometry Structures" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-118", + "@id": "http://www.opengis.net/def/doc-type/d-profile", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/10-100r2" + }, + { + "@id": "http://www.opengis.net/def/docs/06-049r1" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/20-059r4", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-02-06" + "@value": "2021-01-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Andreas Matheus" + "@value": "Gobe Hobona" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/pol-nts" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -85554,27 +85019,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51806" + "@id": "https://docs.ogc.org/pol/20-059r4.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-118" + "@value": "Naming of OGC API Standards, Repositories & Specification Elements" }, { "@language": "en", - "@value": "OWS-9 Security Engineering Report " + "@value": "20-059r4" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/pol-nts" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Engineering Report describes the approaches to security taken in the OWS-9 initiative. This document presents the results of the work within the OWS-9 Security and Services Interoperability (SSI) thread and results from CCI and Innovations Cross Thread activities. \r\nThe report also describes the various tasks and their results regarding interoperability between different security components provided by different participants.\r\n" + "@value": "This document is a policy of the OGC Naming Authority (OGC-NA), a sub-committee of the OGC Technical Committee. The document defines a series of policy requirements for OGC API standards, repositories, definitions, and specification elements. The policy document is intended to be a specialization of the OGC-NA policy on naming specification elements (OGC 10-103)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -85585,35 +85050,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-118" + "@value": "20-059r4" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-9 Security Engineering Report " + "@value": "Naming of OGC API Standards, Repositories & Specification Elements" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-035", + "@id": "http://www.opengis.net/def/docs/19-047", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2017-05-12" + "@value": "2019-11-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Christoph Stasch, Simon Jirka" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -85623,27 +85088,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/16-035.html" + "@id": "https://docs.ogc.org/dp/19-047.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-035" + "@value": "Proposed OGC GeoPackage Enhancements" }, { "@language": "en", - "@value": "Testbed-12 REST Architecture Engineering Report" + "@value": "19-047" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "REST interfaces facilitate the application of OGC standards in many novel application scenarios, e.g. implementing OGC clients on constrained devices, as they ease the implementation of service requests and simplify the interaction patterns. Thereby, REST serves as a complementary technology to the already existing SOAP/POX provided by most of the current OGC standards. This engineering report (ER) provides an overview on different REST service implementations in the Testbed-12 and in related activities. As a result, this ER can be used to develop recommendations on architecture guidelines for providing REST interfaces in the geospatial domain." + "@value": "The Open Geospatial Consortium (OGC) GeoPackage Encoding Standard was developed for the purpose of providing an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information. GeoPackage has proven to be an effective container mechanism for bundling and sharing geospatial data for a variety of operational use cases. However, GeoPackage stakeholders have observed persistent interoperability issues, particularly with regards to metadata, extensions, and portrayal.\r\n\r\nThis paper presents the operational need, proposed approach, and way ahead for addressing these interoperability issues. Section 6 presents three new enhancements (extensions) that are designed to improve the interoperability of GeoPackages in general and metadata in particular. Section 7 presents a vision for implementing an Open Portrayal Framework in GeoPackage. Annex A presents specifications for all of the GeoPackage extensions proposed in this paper. Annex B presents a JSON schema for the proposed encoding for application profiles presented in Section 6. In general, the GeoPackage Standards Working Group (SWG) looks to standardize extensions that address a clear use case, have a sound technical approach, and have a commitment to implementation by multiple organizations. As with the GeoPackage Tiled Gridded Coverage Extension and the GeoPackage Related Tables Extension, these new extensions would be tracked as separate documents from the core GeoPackage Encoding Standard.\r\n\r\nThe GeoPackage community will benefit from the increased interoperability of operational “mission-ready” GeoPackages that will result from this approach. Additionally, software will be able to quickly determine the validity and utility of a GeoPackage in target operational environments. This will help ensure that GeoPackage production-consumption lifecycles and supporting application tools and services are better aligned with stakeholder missions." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -85654,30 +85119,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-035" + "@value": "19-047" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Testbed-12 REST Architecture Engineering Report" + "@value": "Proposed OGC GeoPackage Enhancements" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-158", + "@id": "http://www.opengis.net/def/docs/11-096", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2013-06-18" + "@value": "2011-11-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Matthes Rieke" + "@value": "Stephan Meissl, Peter Baumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -85692,17 +85157,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=51817" + "@id": "https://portal.ogc.org/files/?artifact_id=45404" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-158" + "@value": "11-096" }, { "@language": "en", - "@value": "OWS-9 Report on Aviation Performance Study" + "@value": "OWS-8 WCS 2.0 Earth Observation Application Profile Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -85712,7 +85177,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 9 (OWS-9). The report summarizes the work carried out regarding performance and endurance testing of data provision services, namely Web Feature Service and Event Service. More specifically, the report deals with the performance and endurance testing of data provision services commonly used within OWS Aviation testbeds. Test runs have been evaluated on the basis of well-defined, service-specific test models and the results are documented in detail. Furthermore, a description of the service test environment is documented in alignment with the overall OWS-9 service architecture" + "@value": "This Engineering Report describes progress on EO-WCS in the course of OWS-8." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -85723,35 +85188,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-158" + "@value": "11-096" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® OWS-9 Report on Aviation Performance Study" + "@value": "OWS-8 WCS 2.0 Earth Observation Application Profile Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-094r1", + "@id": "http://www.opengis.net/def/docs/14-065r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-18" + "@value": "2018-02-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Matthias Mueller" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/profile" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -85761,27 +85226,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13203" + "@id": "https://docs.ogc.org/is/14-065/14-065r2.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-094r1" + "@value": "14-065r2" }, { "@language": "en", - "@value": "GML 3.1.1 CRS support profile" + "@value": "WPS 2.0.2 Interface Standard: Corrigendum 2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/profile" + "@id": "http://www.opengis.net/def/doc-type/isc" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for supporting other profiles for encoding definitions of Coordinate Reference Systems (CRSs) and Coordinate Operations. This profile can be used without a GML Application Schema, and such use is assumed in this document." + "@value": "In many cases geospatial or location data, including data from sensors, must be processed before the information can be used effectively. The OGC Web Processing Service (WPS) Interface Standard provides a standard interface that simplifies the task of making simple or complex computational processing services accessible via web services. Such services include well-known processes found in GIS software as well as specialized processes for spatio-temporal modeling and simulation. While the OGC WPS standard was designed with spatial processing in mind, it can also be used to readily insert non-spatial processing tasks into a web services environment.\r\n\r\nThe WPS standard provides a robust, interoperable, and versatile protocol for process execution on web services. It supports both immediate processing for computational tasks that take little time and asynchronous processing for more complex and time consuming tasks. Moreover, the WPS standard defines a general process model that is designed to provide an interoperable description of processing functions. It is intended to support process cataloguing and discovery in a distributed environment.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -85792,30 +85257,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-094r1" + "@value": "14-065r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML 3.1.1 CRS support profile" + "@value": "OGC® WPS 2.0.2 Interface Standard: Corrigendum 2" } ] }, { - "@id": "http://www.opengis.net/def/docs/12-000", + "@id": "http://www.opengis.net/def/docs/99-050", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-04" + "@value": "1999-05-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Mike Botts, Alexandre Robin" + "@value": "TC Chair" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -85830,17 +85295,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=55939" + "@id": "https://portal.ogc.org/files/?artifact_id=830" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "12-000" + "@value": "Simple Features Implementation Specification for OLE/COM" }, { "@language": "en", - "@value": "SensorML: Model and XML Encoding Standard" + "@value": "99-050" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -85850,7 +85315,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The primary focus of the Sensor Model Language (SensorML) is to provide a robust and\r\nsemantically-tied means of defining processes and processing components associated\r\nwith the measurement and post-measurement transformation of observations. This\r\nincludes sensors and actuators as well as computational processes applied pre- and postmeasurement.\r\nThe main objective is to enable interoperability, first at the syntactic level and later at the\r\nsemantic level (by using ontologies and semantic mediation), so that sensors and\r\nprocesses can be better understood by machines, utilized automatically in complex\r\nworkflows, and easily shared between intelligent sensor web nodes.\r\nThis standard is one of several implementation standards produced under OGC’s Sensor\r\nWeb Enablement (SWE) activity. This standard is a revision of content that was\r\npreviously integrated in the SensorML version 1.0 standard (OGC 07-000)." + "@value": "The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc)." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -85861,35 +85326,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "12-000" + "@value": "99-050" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® SensorML: Model and XML Encoding Standard" + "@value": "OpenGIS Simple Features Implementation Specification for OLE/COM" } ] }, { - "@id": "http://www.opengis.net/def/docs/11-169r1", + "@id": "http://www.opengis.net/def/docs/23-050", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-02-25" + "@value": "2024-04-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Simon Jirka, Christoph Stasch, Arne Bröring" + "@value": "Lucio Colaiacomo" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -85899,27 +85364,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=52803" + "@id": "https://docs.ogc.org/per/23-050.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "11-169r1" + "@value": "23-050" }, { "@language": "en", - "@value": "Best Practice for Sensor Web Enablement Lightweight SOS Profile for Stationary In-Situ Sensors" + "@value": "OGC Testbed-19 Agile Reference Architecture Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/bp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This Best Practice document describes a lightweight SOS 2.0 profile for stationary in-situ\r\nsensors. Besides the SOS itself this document also addresses the data formats used by the\r\nSOS: Observations & Measurements 2.0 (O&M) for encoding measurement data and the\r\nSensor Model Language 2.0 (SensorML) for encoding metadata. Other SWE standards\r\nwhich provide more specialized functionality are not part of this minimum lightweight\r\nSWE profile.\r\nThe aim of this document is to present a common minimum profile of the SOS. The\r\nprofile is intended to reduce the complexity of the standard by omitting highly specific\r\nelements that are not necessary for the majority of use cases that occur in practice. At the\r\nsame time, the profile is designed in such a way that all SOS implementations that\r\nconform to this profile are also compliant to the according OGC specifications." + "@value": "The concepts of agile architecture and reference architecture may not be new ideas in information or geospatial technologies, but what is meant by the term Agile Reference Architecture?\r\n\r\nAgile Reference Architecture is the long-term vision of the complex and changing nature of how problems will be solved in the future within the location-referenced and geospatial realms. This includes consideration of network availability, as containers integrated with Linked Data, and Application Programming Interfaces (APIs) serve data as secure, trusted, and self-describing resources.\r\n\r\nWhile the Open Geospatial Consortium (OGC) focuses on geospatial information and technologies, that community is also dependent on the overall state of information and communications technology (ICT), including developing cyber, cryptographic, and internet technologies.\r\n\r\nIn today’s infrastructures, the collection, exchange, and continuous processing of geospatial resources typically happens at pre-defined network endpoints of a spatial data infrastructure. Each participating operator hosts some capability at a network endpoint. Whereas some network operator endpoints may provide data access, other endpoints provide processing functionality and other endpoints may support the uploading of capabilities. In other words, such an infrastructure is not agile in the sense that it cannot adapt by itself to meet the needs of the moment. One of the biggest challenges resulting from the static characteristics is ensuring effective and efficient operations of the overall system and at the same time maintaining trust and provenance.\r\n\r\nThis OGC Testbed 19 Engineering Report (ER) outlines novel concepts for establishing a federated agile infrastructure of collaborative trusted systems (FACTS) that is capable of acting autonomously to ensure fit-for-purpose cooperation across the entire system. One of the key objectives is to not create a new data product, but instead a collaborative object is offered leveraging FACTS that allows for obtaining the data product via well-defined interfaces and functions provided by the collaborative object.\r\n\r\nTrust and assurance are two key aspects when operating a network of collaborative objects leveraging STANAG 4774/4778. STANAG 4774 outlines the metadata syntax required for a confidentiality label to better facilitate and protect sensitive information sharing. In addition, STANAG 4778 defines how a confidentiality label is bound to the data throughout its lifecycle and between the sharing parties.The agile aspect is achieved by the object’s ability to activate, deactivate, and order well-defined capabilities from other objects. These capabilities are encapsulated in building blocks. Each building block is well defined in terms of accessibility, functionality, and ordering options. This allows building blocks to roam around collaborative objects as needed to ensure a well-balanced network load and suitable processing power of individual nodes from the network.\r\n\r\nEqually trusted partners in the infrastructure participate in FACTS. They can collect data from other partners and create derived products via collaborative objects. The sharing of data products is only possible directly, meaning direct communication with data consumer and it is only possible via the objects. This guarantees that fundamental trust operations are applied to the data and provenance records are produced before the data product is made available to others. The use of Blockchain technology and Smart contracts is one example of how this fundamental behavior can be planted into collaborative objects. As in trusted networks that are using Evaluation Assurance Level (EAL) approved hardware and software components, the objects will have to undergo a similar assurance process.\r\n\r\nFor ensuring the acceptance and interoperability of an agile reference architecture, built on top of FACTS with collaborative objects and building blocks, standardization is a key aspect. In particular, the core (fundamental) requirements for FACTS as well as the interfaces and capabilities of the collaborative objects and pluggable building blocks should be standardized. The OGC provides a consensus based collaborative standardization environment fits these requirements very well." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -85930,35 +85395,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "11-169r1" + "@value": "23-050" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Best Practice for Sensor Web Enablement Lightweight SOS Profile for Stationary In-Situ Sensors" + "@value": "OGC Testbed-19 Agile Reference Architecture Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-147r2", + "@id": "http://www.opengis.net/def/docs/16-088r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-04-14" + "@value": "2016-07-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Tim Wilson" + "@value": "Alistair Ritchie" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -85968,27 +85433,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27810" + "@id": "https://portal.ogc.org/files/?artifact_id=69896" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "KML" + "@value": "16-088r1" }, { "@language": "en", - "@value": "07-147r2" + "@value": "Soil Data Interoperability Experiment" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "KML is an XML language focused on geographic visualization, including annotation of maps and images. Geographic visualization includes not only the presentation of graphical data on the globe, but also the control of the user's navigation in the sense of where to go and where to look." + "@value": "This engineering report describes the results of the Soil Data Interoperability Experiment\r\n(the IE) conducted under the auspices of the OGC Agriculture Domain Working Group in\r\n2015. Soil data exchange and analysis is compromised by the lack of a widely agreed\r\ninternational standard for the exchange of data describing soils and the sampling and\r\nanalytical activities relating to them. Previous modeling activities in Europe and\r\nAustralasia have not yielded models that satisfy many of the data needs of global soil\r\nscientists, data custodians and users. This IE evaluated existing models and proposed a\r\ncommon core model, including a GML/XML schema, which was tested through the\r\ndeployment of OGC web services and demonstration clients. IE time constraints and\r\nlimited participant resources precluded extensive modeling activities. However, the\r\nresulting model should form the core of a more comprehensive model to be developed by\r\na future OGC Soil Data Standards Working Group." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -85999,30 +85464,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-147r2" + "@value": "16-088r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC KML" + "@value": "OGC Soil Data Interoperability Experiment" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-018r2", + "@id": "http://www.opengis.net/def/docs/11-165r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-02-03" + "@value": "2013-01-03" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Taylor" + "@value": "Ben Domenico, Stefano Nativi " } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -86037,17 +85502,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/15-018r2/15-018r2.html" + "@id": "https://portal.ogc.org/files/?artifact_id=51908" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "WaterML2.0: part 2 - Ratings, Gaugings and Sections" + "@value": "11-165r2" }, { "@language": "en", - "@value": "15-018r2" + "@value": "CF-netCDF3 Data Model Extension standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -86057,7 +85522,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This standard defines an information model and XML encoding for exchanging the\r\nfollowing three hydrological information resources:\r\n1. Conversion tables, or conversion curves, that are used for the conversion of\r\nrelated hydrological phenomenon.\r\n2. Gauging observations – the observations performed to develop conversion table\r\nrelationships.\r\n3. Cross sections - survey observations made of the geometric structure of features,\r\nsuch as river channels, storages etc.\r\nMetadata and vocabularies are defined that together provide a means for parties to\r\nexchange these concepts using common semantics.\r\nThis standard is the second part of the WaterML2.0 suite of standards, building on part 1\r\nthat addresses the exchange of time series.\r\n" + "@value": "The OGC netCDF encoding supports electronic encoding of geospatial data, that is, digital geospatial information representing space and time-varying phenomena.\r\nThis standard specifies the CF-netCDF data model extension. \r\nThis standard specifies the CF-netCDF data model mapping onto the ISO 19123 coverage schema. \r\nThis standard deals with multi-dimensional gridded data and multi-dimensional multi-point data.\r\nIn particular, this extension standard encoding profile is limited to multi-point, and regular and warped grids; however, irregular grids are important in the CF-netCDF community and work is underway to expand the CF-netCDF to encompass other coverages types, including irregular gridded datasets.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86068,30 +85533,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-018r2" + "@value": "11-165r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC WaterML2.0: part 2 - Ratings, Gaugings and Sections" + "@value": "CF-netCDF3 Data Model Extension standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-035", + "@id": "http://www.opengis.net/def/docs/16-053r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-01-13" + "@value": "2017-06-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Christophe Noël" + "@value": "Joan Masó" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -86106,17 +85571,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-035.html" + "@id": "https://docs.ogc.org/per/16-053r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Earth Observation Application Packages with Jupyter Notebooks" + "@value": "Testbed-12 OWS Context: JSON, JSON-LD and HTML5 ER" }, { "@language": "en", - "@value": "20-035" + "@value": "16-053r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -86126,7 +85591,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed-16 Engineering Report (ER) describes all results and experiences from the “Earth Observation Application Packages with Jupyter Notebook” thread of OGC Testbed-16. The aim of this thread was to extend the Earth Observation Applications architecture developed in OGC Testbeds 13, 14, and 15 with support for shared and remotely executed Jupyter Notebooks. The Notebooks make use of the Data Access and Processing API (DAPA) developed in the Testbed-16 Data Access and Processing API (DAPA) for Geospatial Data task and tested in joint Technology Integration Experiments." + "@value": "At the time of finalizing this ER the OGC TC has approved the OWS Context JSON encoding that is available here: http://www.opengeospatial.org/standards/owc This is the second encoding proposed for the OWS context standard precided by the Atom Encoding [OGC 12-084r2]. The OWS Context JSON enconding is based on the GeoJSON IETF standard [RFC7946]. The standard is a combination of two approaches:\r\n\r\nmapping between the OWS Context conceptual model [12-080r2] to the basic structure of a GeoJSON file.\r\n\r\na direct conversion of the rest of the atom keys and the specific OWS Context XML into JSON following OGC 14-009r1.\r\n\r\nThe conversion was designed with current GeoJSON viewers in mind (including the one embedded in GitHUB) and making possible that they can visualize a OWS Context GeoJSON file without any modifications.\r\n\r\nThis ER focus on describing another encoding (a 3rd alternative) that allows for exposing geospatial resources on the web in a way that web browsers and search engines can better understand. It is widely known that HTML was designed with the linking capacity in mind. Both, users reading HTML and automatic crawlers, transverse links constantly. HTML seems the natural selection for linking geospatial data on the web. The question is how to complement the linking mechanism with some additional metadata that search engines could use for indexing. A solution could come from a mechanism which web search engines already have agreed to use for better indexing: schema.org.\r\n\r\nSchemna.org proposes three enconding for their data model: Microdata, RDFa and JSON-LD. The reader might easily get confused by the fact that OGC approved a JSON encoding for OWS context and another JSON encoding emerges in this document. This ER is NOT proposing to replace or modify the currently approved JSON enconding for OWS context based on GeoJSON. The intention is to map the OWS Context model into the schema.org model to recognize that they are very similar and propose a encoding in HTML5 that can be done in the 3 alternative proposed by schema.org.\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86137,35 +85602,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-035" + "@value": "16-053r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-16: Earth Observation Application Packages with Jupyter Notebooks" + "@value": "Testbed-12 OWS Context: JSON, JSON-LD and HTML5 ER" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-022r1", + "@id": "http://www.opengis.net/def/docs/07-002r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-04-21" + "@value": "2007-12-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "James Resler" + "@value": "Simon Cox" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -86175,27 +85640,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=14898" + "@id": "https://portal.ogc.org/files/?artifact_id=22467" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Temporal Standard Recommendations" + "@value": "Observations and Measurements - Part 2 - Sampling Features" }, { "@language": "en", - "@value": "06-022r1" + "@value": "07-002r3" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document summarizes recommendations for extending geospatial standards with regard to time-varying information. These proposals are the result of the National Technology Alliance program called Temporal Evaluation and Assessment (TEA). " + "@value": "The OpenGIS® Observations and Measurements Encoding Standard (O&M) defines an abstract model and an XML schema [www.w3.org/XML/Schema] encoding for observations and it provides support for common sampling strategies. O&M also provides a general framework for systems that deal in technical measurements in science and engineering. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86206,35 +85671,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-022r1" + "@value": "07-002r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Temporal Standard Recommendations" + "@value": "Observations and Measurements - Part 2 - Sampling Features" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-189", + "@id": "http://www.opengis.net/def/docs/20-067", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2007-08-27" + "@value": "2020-10-22" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Chris Holmes" + "@value": "David Blodgett" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -86244,27 +85709,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=19208" + "@id": "https://docs.ogc.org/per/20-067.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Corrigendum 1 (one) for OpenGIS Implementation Specification GML 2.1.2" + "@value": "20-067" }, { "@language": "en", - "@value": "06-189" + "@value": "Second Environmental Linked Features Experiment" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-isc" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document provides the details for a corrigendum for the existing OpenGIS Implementation Specification for the Geography Markup Language version 2.1.2 and does not modify that implementation specification. The current OpenGIS Implementation Specification that this document provides revision notes for is 02-069. " + "@value": "This report documents the Second Environmental Linked Features Interoperability Experiment (SELFIE). SELFIE evaluated a proposed Web resource model and HTTP behavior for linked data about and among environmental features. The outcomes are building blocks to establish a system of real-world feature identifiers and landing pages that document them. OGC API - Features was found to be a useful component for systems implementing both landing content and representations of linked-features. More work is needed to establish best practices related to negotiation between varied representations of a feature, observations related to a feature, and for expressing and mediating between varied content from a given resource. These technical / meta-model details were found to be difficult to evaluate given the small number of example implementations and limited number of domain-feature models available for use with linked data." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86275,35 +85740,61 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-189" + "@value": "20-067" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Corrigendum 1 (one) for OpenGIS Implementation Specification GML 2.1.2" + "@value": "Second Environmental Linked Features Experiment" } ] }, { - "@id": "http://www.opengis.net/def/docs/08-008r1", + "@id": "http://www.opengis.net/def/doc-type/profile", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/10-100r3" + }, + { + "@id": "http://www.opengis.net/def/docs/13-082r2" + }, + { + "@id": "http://www.opengis.net/def/docs/05-095r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-099r2" + }, + { + "@id": "http://www.opengis.net/def/docs/05-094r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-140r1" + }, + { + "@id": "http://www.opengis.net/def/docs/05-096r1" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/05-017", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-04-29" + "@value": "2005-02-10" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside" + "@value": "Wenli Yang, Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -86313,27 +85804,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27711" + "@id": "https://portal.ogc.org/files/?artifact_id=8981" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Proposed Topic 19 - General Reference Systems" + "@value": "05-017" }, { "@language": "en", - "@value": "08-008r1" + "@value": "Web Image Classification Service (WICS)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This discussion paper is a draft new topic volume for the OGC Abstract Specification, which may also be used to propose a corresponding new standard to ISO/TC 211. This document proposes extensions to OGC Abstract Specification Topic 2 — Spatial referencing by coordinates, and thus to ISO 19111 — Spatial referencing by coordinates. This discussion paper is posted for comments on the contents. Revision of this draft is planned, to improve some details while supporting the same abilities." + "@value": "The Web Image Classification Service (WICS) supports classification of digital images. A digital image is composed of pixel values organized into one or more two-dimensional arrays. The two dimensions of an image represent two axes in space based on a spatial coordinate reference system. The dimensions of the different 2-D arrays comprising an image must be the same and represent exactly the same spatial locations." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86344,35 +85835,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "08-008r1" + "@value": "05-017" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS® Abstract Specification Proposed Topic 19 - General Reference Systems" + "@value": "Web Image Classification Service (WICS)" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-032", + "@id": "http://www.opengis.net/def/docs/09-085r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2009-07-29" + "@value": "2009-10-13" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Thomas Everding, Johannes Echterhoff" + "@value": "Arliss Whiteside" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -86382,27 +85873,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=33347" + "@id": "https://portal.ogc.org/files/?artifact_id=35653" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-6 SWE Event Architecture Engineering Report" + "@value": "Grid coverage Coordinate Reference Systems (CRSs)" }, { "@language": "en", - "@value": "09-032" + "@value": "09-085r2" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The document describes an abstract event architecture for service oriented architectures. Furthermore various techniques for implementing an event architecture and working with events are discussed." + "@value": "This document summarizes the types of Coordinate Reference Systems (CRSs) that are recommended for use with grid (including image) coverages. This document specializes Best Practice Paper OGC 09-076r3 “Uses and Summary of Topic 2: Spatial referencing by coordinates” for grid coverages. Topic 2 is almost the same as ISO 19111:2007, but includes some corrections. This document includes some best practices for defining and using ImageCRSs and other CRSs for grid coverages." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86413,35 +85904,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-032" + "@value": "09-085r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OWS-6 SWE Event Architecture Engineering Report" + "@value": "Grid coverage Coordinate Reference Systems (CRSs)" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-166r2", + "@id": "http://www.opengis.net/def/docs/17-002r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-08-04" + "@value": "2017-08-18" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Baumann" + "@value": "Carl Reed" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -86451,27 +85942,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27052" + "@id": "https://docs.ogc.org/cs/17-002r1/17-002r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OWS-5 Engineering Report on WCPS" + "@value": "17-002r1" }, { "@language": "en", - "@value": "07-166r2" + "@value": "GeoRSS Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/cs" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document represents the Engineering Report for the WCPS activity within the OWS-5 SWE thread. It summarizes tasks and outcomes." + "@value": "GeoRSS is designed as a lightweight, community driven way to extend existing RSS feeds with simple geographic information. The GeoRSS standard provides for encoding location in an interoperable manner so that applications can request, aggregate, share and map geographically tag feeds." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86482,35 +85973,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-166r2" + "@value": "17-002r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC OWS-5 Engineering Report on WCPS" + "@value": "OGC GeoRSS Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-110", + "@id": "http://www.opengis.net/def/docs/12-049", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-04-19" + "@value": "2014-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Arliss Whiteside, Bill Woodward, co-editor" + "@value": "Peter Baumann, Jinsongdi Yu" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -86520,27 +86011,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13186" + "@id": "https://portal.ogc.org/files/?artifact_id=54502" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-110" + "@value": "Web Coverage Service Interface Standard - Interpolation Extension" }, { "@language": "en", - "@value": "Feature Portrayal Service" + "@value": "12-049" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/retired" + "@id": "http://www.opengis.net/def/doc-type/isx" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document specifies the interface to a Feature Portrayal Service (FPS), which applies styles to digital features to produce a map image. The styles applied are identified or specified by the client, and are applied to digital feature data retrieved from a Web Feature Service (WFS) identified by the client. " + "@value": "This OGC standard specifies parameters to the OGC Web Coverage Service (WCS) GetCov-erage request which give control over interpolation of a coverage during its server-side pro-cessing. This allows the client (user) to control and specify the interpolation mechanism to be applied to a coverage during server processing.\r\nThis WCS Interpolation extension relies on WCS Core [OGC 09-110r4] and the GML Appli-cation Schema for Coverages [OGC 09-146r2].\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86551,35 +86042,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-110" + "@value": "12-049" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Feature Portrayal Service" + "@value": "OGC® Web Coverage Service Interface Standard - Interpolation Extension" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-011r4", + "@id": "http://www.opengis.net/def/docs/18-066r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2020-11-05" + "@value": "2021-02-04" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker, Hye-Young Kan" + "@value": "Jeff Yutzler" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -86589,27 +86080,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/19-011r4/19-011r4.html" + "@id": "https://docs.ogc.org/is/12-128r17/18-066r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-011r4" + "@value": "18-066r1" }, { "@language": "en", - "@value": "OGC® IndoorGML 1.1" + "@value": "Release Notes for OGC GeoPackage Encoding Standard v1.3.0" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/notes" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® IndoorGML standard specifies an open data model and XML schema of indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modeling indoor spaces for navigation purposes." + "@value": "This document provides the set of revision notes for the existing GeoPackage version 1.3.0 (OGC 12-128r17) and does not modify that standard.\r\n\r\nThis document was approved by the OGC membership on 2020-11-26. As a result of the OGC Standards Working Group (SWG) process, there were a number of edits and enhancements made to this standard. This document provides the details of those edits, deficiency corrections, and enhancements. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86620,35 +86111,66 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-011r4" + "@value": "18-066r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® IndoorGML 1.1" + "@value": "Release Notes for OGC GeoPackage Encoding Standard v1.3.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/04-094r1", + "@id": "http://www.opengis.net/def/doc-type/is-draft/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Implementation Specification - Draft" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Implementation Specification - Draft" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/21-056r10" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Implementation Specification - Draft" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/19-066", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-10-26" + "@value": "2021-02-26" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis A. Vretanos" + "@value": "Michala Hill" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -86658,27 +86180,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/04-094r1/04-094r1.html" + "@id": "https://docs.ogc.org/bp/19-066.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "04-094r1" + "@value": "19-066" }, { "@language": "en", - "@value": "Web Feature Service Implementation Specification with Corrigendum" + "@value": "Volume 14 OGC CDB Guidance on Conversion of CDB Shapefiles into CDB GeoPackages (Best Practice)" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/isc" + "@id": "http://www.opengis.net/def/doc-type/bp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OGC Web Map Service allows a client to overlay map images for display served from multiple Web Map Services on the Internet. In a similar fashion, the OGC Web Feature Service allows a client to retrieve and update geospatial data encoded in Geography Markup Language (GML) from multiple Web Feature Services.\r\n\r\nThe requirements for a Web Feature Service are:\r\n\r\nThe interfaces must be defined in XML.\r\nGML must be used to express features within the interface.\r\nAt a minimum a WFS must be able to present features using GML.\r\nThe predicate or filter language will be defined in XML and be derived from CQL as defined in the OpenGIS Catalogue Interface Implementation Specification.\r\nThe datastore used to store geographic features should be opaque to client applications and their only view of the data should be through the WFS interface.\r\n The use of a subset of XPath expressions for referencing properties.\r\n" + "@value": "This OGC Best Practice (BP) document describes the conversion process for converting a CDB structured Shapefile into a CDB structured GeoPackage. This is the companion document to Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension). Volume 13 defines the requirements and provides CDB specific guidance on using GeoPackage containers in a CDB data store.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86689,30 +86211,86 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "04-094r1" + "@value": "19-066" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Web Feature Service Implementation Specification with Corrigendum" + "@value": "Volume 14 OGC CDB Guidance on Conversion of CDB Shapefiles into CDB GeoPackages (Best Practice)" } ] }, { - "@id": "http://www.opengis.net/def/docs/20-091", + "@id": "http://www.opengis.net/def/doc-type/notes", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/21-066r1" + }, + { + "@id": "http://www.opengis.net/def/docs/16-126r8" + }, + { + "@id": "http://www.opengis.net/def/docs/15-123r1" + }, + { + "@id": "http://www.opengis.net/def/docs/23-018r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-111" + }, + { + "@id": "http://www.opengis.net/def/docs/18-016r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-099r2" + }, + { + "@id": "http://www.opengis.net/def/docs/07-061" + }, + { + "@id": "http://www.opengis.net/def/docs/07-066r5" + }, + { + "@id": "http://www.opengis.net/def/docs/21-004" + }, + { + "@id": "http://www.opengis.net/def/docs/20-006" + }, + { + "@id": "http://www.opengis.net/def/docs/18-066r1" + }, + { + "@id": "http://www.opengis.net/def/docs/12-052" + }, + { + "@id": "http://www.opengis.net/def/docs/18-024r1" + }, + { + "@id": "http://www.opengis.net/def/docs/19-034r1" + }, + { + "@id": "http://www.opengis.net/def/docs/22-032r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-044" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/17-022", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2021-02-23" + "@value": "2018-01-11" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Gobe Hobona" + "@value": "Guy Schumann" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -86727,17 +86305,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/20-091.html" + "@id": "https://docs.ogc.org/per/17-022.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC API – Common and OGC API – Features Sprint 2020: Summary Engineering Report" + "@value": "Testbed-13: NA001 Climate Data Accessibility for Adaptation Planning" }, { "@language": "en", - "@value": "20-091" + "@value": "17-022" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -86747,7 +86325,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The subject of this Engineering Report (ER) is a code sprint that was held from 29 to 30 September 2020 to advance the development of the OGC API - Common - Part 2: Geospatial Data draft standard and the OGC API – Features – Part 4: Simple Transactions draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The code sprint was hosted online. The event was sponsored by Ordnance Survey (OS)." + "@value": "This Engineering Report describes all Testbed-13 activities relating to the Climate Data Accessibility for Adaptation Planning requirements of the National Aeronautics and Space Administration (NASA). It discusses relevant experiences made during implementation including recommendations to the sponsor, and provides resulting standards change requests to the appropriate working groups. Additionally, it develops best practices for data and model integration and serves as a guidance document to work with NASA Earth Science Data System (ESDS) working groups and externally provided data. The added value of this Engineering Report is to improve interoperability and to advance location-based technologies and realize innovations with regards to NASA Climate Data and NASA ESDS objectives." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86758,35 +86336,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "20-091" + "@value": "17-022" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API – Common and OGC API – Features Sprint 2020: Summary Engineering Report" + "@value": "OGC Testbed-13: NA001 Climate Data Accessibility for Adaptation Planning" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-056r11", + "@id": "http://www.opengis.net/def/docs/19-073r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2023-09-08" + "@value": "2020-07-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Carl Stephen Smyth" + "@value": "Volker Coors" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -86796,27 +86374,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/21-056r11/21-056r11.html" + "@id": "https://docs.ogc.org/per/19-073r1.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC GeoPose 1.0 Data Exchange Standard" + "@value": "3D-IoT Platform for Smart Cities Engineering Report" }, { "@language": "en", - "@value": "21-056r11" + "@value": "19-073r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "GeoPose 1.0 is an OGC Implementation Standard for exchanging the location and orientation of real or virtual geometric objects (“Poses”) within reference frames anchored to the earth’s surface (“Geo”) or within other astronomical coordinate systems.\r\n\r\nThe standard specifies two Basic forms with no configuration options for common use cases, an Advanced form with more flexibility for more complex applications, and five composite GeoPose structures that support time series plus chain and graph structures.\r\n\r\nThese eight Standardization Targets are independent. There are no dependencies between Targets and each may be implemented as needed to support a specific use case.\r\n\r\nThe Standardization Targets share an implementation-neutral Logical Model which establishes the structure and relationships between GeoPose components and also between GeoPose data objects themselves in composite structures. Not all of the classes and properties of the Logical Model are expressed in individual Standardization Targets nor in the specific concrete data objects defined by this standard. Those elements that are expressed are denoted as implementation-neutral Structural Data Units (SDUs). SDUs are aliases for elements of the Logical Model, isolated to facilitate specification of their use in encoded GeoPose data objects for a specific Standardization Target.\r\n\r\nFor each Standardization Target, each implementation technology and corresponding encoding format defines the encoding or serialization specified in a manner appropriate to that technology.\r\n\r\nGeoPose 1.0 specifies a single encoding in JSON format (IETF RFC 8259). Each Standardization Target has a JSON Schema (Internet-Draft draft-handrews-json-schema-02) encoding specification. The key standardization requirements specify that concrete JSON-encoded GeoPose data objects must conform to the corresponding JSON Schema definition. The individual elements identified in the encoding specification are composed of SDUs, tying the specifications back to the Logical Model.\r\n\r\nThe GeoPose 1.0 Standard makes no assumptions about the interpretation of external specifications, for example, of reference frames. Nor does it assume or constrain services or interfaces providing conversion between GeoPoses of difference types or relying on different external reference frame definitions." + "@value": "Recent years have seen a significant increase in the use of three-dimensional (3D) data in the Internet of Things (IoT). The goal of the 3D IoT Platform for Smart Cities Pilot was to advance the use of open standards for integrating environmental, building, and IoT data in Smart Cities. Under this initiative a proof of concept (PoC) has been conducted to better understand the capabilities to be supported by a 3D IoT Smart City Platform under the following standards: CityGML, IndoorGML, SensorThings API, 3D Portrayal Service, and 3D Tiles." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86827,35 +86405,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-056r11" + "@value": "19-073r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC GeoPose 1.0 Data Exchange Standard" + "@value": "OGC 3D-IoT Platform for Smart Cities Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-103r4", + "@id": "http://www.opengis.net/def/docs/15-048r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2011-05-28" + "@value": "2016-01-25" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "John Herring" + "@value": "Jeff Harrison" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -86865,27 +86443,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=25355" + "@id": "https://portal.ogc.org/files/?artifact_id=65420" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "06-103r4" + "@value": "15-048r3" }, { "@language": "en", - "@value": "Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture" + "@value": "Testbed-11 NIEM & IC Data Encoding Specification Assessment and Recommendations Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. " + "@value": "The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community\r\n(IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0\r\narchitecture through the development, implementations, test, and robust demonstration\r\nmaking use of IC specifications, Geography Markup Language (GML), and NIEM in a\r\nsimulated “real-world” scenario. The demonstration scenario begins with NIEMconformant\r\nInformation Exchange Packages (IEPs) containing operational data and IC\r\nsecurity tags from the Information Security Marking (ISM) and Need-To-Know (NTK)\r\naccess control metadata, and the Trusted Data Format (TDF) for binding assertion\r\nmetadata with data resource(s). Those instance documents are deployed on Open\r\nGeospatial Consortium (OGC) Web Services to be used by client applications. Access\r\ncontrol is based on attributes of the end-user and the instance data.\r\nRecommendations to update these information exchanges were provided to reflect NIEM\r\n3.0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment\r\nexercised this data encoding in OGC Web Feature Services (WFS) and Policy\r\nEnforcement Points (PEP) accessed by multiple client applications. Results from this task\r\nprovided a preliminary architecture that was tested and demonstrated in Testbed 11, and\r\nsummarized in other OGC Testbed 11 Engineering Reports." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86896,35 +86474,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-103r4" + "@value": "15-048r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture" + "@value": "OGC Testbed-11 NIEM & IC Data Encoding Specification Assessment and Recommendations Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-126", + "@id": "http://www.opengis.net/def/docs/21-054", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2005-11-30" + "@value": "2023-01-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Keith Ryden" + "@value": "Sergio Taleisnik" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -86934,27 +86512,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13227" + "@id": "https://docs.ogc.org/per/21-054.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture" + "@value": "21-054" }, { "@language": "en", - "@value": "05-126" + "@value": "OGC Disaster Pilot JSON-LD Structured Data Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This part of OpenGIS" + "@value": "This Disaster Pilot JSON-LD Structured Data Engineering Report documents the analysis, discussions, results, and recommendations that emerge from the efforts carried out regarding the use of JSON-LD with OGC APIs to generate structured web page data for search engine optimization of disaster related information.\r\n\r\nThis ER provides the practical experience and lessons learned on the usage of Linked Data within OGC APIs with the objective of enhancing the web search and finding up-to-date conditions, observations, and predictions associated with well-known local geography. Upcoming initiatives should use the findings documented in this ER to further develop applications that make geospatial data and information more easily findable, accessible, interoperable, and reusable, which will increase the efficiency of disaster response. This ER could also be used as a case study of Linked Data to help other industries understand its value and implement it within their domains, or it could serve as a baseline for adding Linked Data support to one or several OGC API standards." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -86965,30 +86543,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-126" + "@value": "21-054" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architectu" + "@value": "OGC Disaster Pilot JSON-LD Structured Data Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/17-090r1", + "@id": "http://www.opengis.net/def/docs/18-030", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-11-25" + "@value": "2019-03-06" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Josh Lieberman" + "@value": "Sara Saeedi" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -87003,17 +86581,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/17-090r1.html" + "@id": "https://docs.ogc.org/per/18-030.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "17-090r1" + "@value": "18-030" }, { "@language": "en", - "@value": "Model for Underground Data Definition and Integration (MUDDI) Engineering Report" + "@value": "Secure Client Test Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -87023,7 +86601,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The recently published Underground Infrastructure Concept Development Study (UICDS) Engineering Report [1] examines the present state of underground infrastructure information (UGII), costs and benefits of that state, as well as future opportunities for an improved state. That report describes a number of candidate models for UGII and recommends a number of follow-on activities, including development of a prototype UGII integration model to support subsequent UGII integration and exchange initiatives. The present report describes the design and development of conceptual UGII integration model MUDDI (Model for Underground Data Definition and Interchange). The goal of MUDDI is not to replace existing models but to serve as the basis for integration of datasets from different models, at the levels of detail required to address application use cases described in [1]. MUDDI as described here is a conceptual model which will serve as the basis for one or more conformant and interchangeable physical implementations such as GML (Geographic Markup Language) or SFS (Simple Features SQL). As a prototype model, the current version of MUDDI is also not intended to be final, but to serve as an input to the proposed OGC Underground Infrastructure Pilot and similar activities which will in turn serve to refine and improve the model through implementation and deployment in realistic application scenarios." + "@value": "This Engineering Report (ER) describes the development of compliance tests and their implementation in the OGC Test, Evaluation, And Measurement (TEAM) Engine to validate a client’s ability to make secure requests according to the OGC Web Services Security Candidate Standard. The goal of the candidate standard is to allow the implementation of Information Assurance (IA) controls and to advertise their existence in an interoperable way with minimal impact to existing implementations using a backward-compatible approach.\r\n\r\nThis ER covers the following topics from OGC Testbed-14 Compliance Interoperability & Testing Evaluation (CITE) thread:\r\n\r\ndeveloping a client validator to test compliance of client software with the OGC Web Services Security Candidate Standard\r\n\r\ncapturing the results of two use cases with different authentication methods\r\n\r\nmaking recommendations to the OGC Web Services Security Standards Working Group (SWG) based on the experiences made while developing the validator\r\n\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -87034,35 +86612,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "17-090r1" + "@value": "18-030" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Model for Underground Data Definition and Integration (MUDDI) Engineering Report" + "@value": "OGC Testbed-14: Secure Client Test Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-079r2", + "@id": "http://www.opengis.net/def/docs/16-099", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2024-07-26" + "@value": "2017-10-20" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Panagiotis (Peter) A. Vretanos, Clemens Portele" + "@value": "Mohsen Kalantari" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -87072,27 +86650,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/is/19-079r2/19-079r2.html" + "@id": "https://docs.ogc.org/per/16-099.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "19-079r2" + "@value": "Future City Pilot 1 - Automating Urban Planning Using Web Processing Service Engineering Report" }, { "@language": "en", - "@value": "OGC API - Features - Part 3: Filtering" + "@value": "16-099" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "OGC API Standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks.\r\n\r\nOGC API - Features provides API building blocks to create, modify and query features on the Web. OGC API - Features is comprised of multiple parts. Each part is a separate standard.\r\n\r\nA fundamental operation performed on a collection of features is that of filtering in order to obtain a subset of the data which contains feature instances that satisfy some filtering criteria. Part three of the OGC API - Features Standard defines query parameters (filter, filter-lang, filter-crs) to specify filter criteria in a request to an API and the Queryables resource that declares the properties of data in a collection that can be used in filter expressions." + "@value": "Numerous and diverse technologies push cities towards open and platform-independent information infrastructures to manage human, natural, and physical systems. Future Cities Pilot 1 is an OGC interoperability initiative that aims to demonstrate how cities can begin to reap the benefits of open standards. This document reports how Web Processing Standard (WPS) of OGC was successfully used in automating urban planning processes. This document details the implementation of urban planning processes and rules concerning urban development approval processes." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -87103,30 +86681,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-079r2" + "@value": "16-099" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC API - Features - Part 3: Filtering" + "@value": "Future City Pilot 1 - Automating Urban Planning Using Web Processing Service Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/10-002", + "@id": "http://www.opengis.net/def/docs/11-013r6", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2014-04-28" + "@value": "2011-07-14" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Raj Singh" + "@value": "Luis Bermudez, David Arctur" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -87141,17 +86719,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=37839" + "@id": "https://portal.ogc.org/files/?artifact_id=44834" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Climate Challenge Integration Plugfest 2009 Engineering Report" + "@value": "11-013r6" }, { "@language": "en", - "@value": "10-002" + "@value": "Water Information Services Concept Development Study" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -87161,7 +86739,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Engineering Report (ER) documents findings of the CCIP 2009 Plugfest, which was conducted via the public Internet to address requirements stated in the CCIP Call for Participation . It addresses concept development, specifications tested, and interoperability experiments conducted. The ER concludes with issues that arose, and provides recommendations for the refinement of OGC Specifications and the Plugfest process. Recommendations in this ER will be considered in the planning of future activities.\r\nOGC expresses thanks to the Australian Bureau of Meteorology and to CSIRO for sponsoring CCIP 2009.\r\n" + "@value": "The purpose of this report is to recommend appropriate architectures and procedures for migrating the CUAHSI HIS to the OGC-based WaterML 2.0 encoding (profile of OGC O&M standard) and OGC web services such as Sensor Observation Service (SOS), Web Feature Service (WFS), Web Mapping Service (WMS), Web Coverage Service (WCS), and Catalogue Service for the Web (CSW). This report may be used as the basis for future OGC Interoperability Program initiatives." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -87172,30 +86750,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "10-002" + "@value": "11-013r6" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC® Climate Challenge Integration Plugfest 2009 Engineering Report" + "@value": "OGC® Engineering Report: Water Information Services Concept Development Study" } ] }, { - "@id": "http://www.opengis.net/def/docs/15-075r1", + "@id": "http://www.opengis.net/def/docs/06-187r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2015-11-19" + "@value": "2007-05-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Ki-Joune Li, Hyung-Gyu Ryu, Taehoon Kim, and Hack-Cheol Kim" + "@value": "Steven Keens" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -87210,17 +86788,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=64644" + "@id": "https://portal.ogc.org/files/?artifact_id=19778" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "15-075r1" + "@value": "Workflow Descriptions and Lessons Learned" }, { "@language": "en", - "@value": "A Use-Case for Mobile Location Services with IndoorGML - Indoor Navigation for Visually Impaired People" + "@value": "06-187r1" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -87230,7 +86808,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Discussion Paper provides a navigation use-case for the use of IndoorGML for mobile location services (MLS). In particular, the Discussion Paper explains how the OGC IndoorGML standard can be applied to a MLS application for visually impaired people in indoor space. Finally, a prototype development of the application on Android smart phone is described in this report." + "@value": "This document examines five workflows discussed during the course of the OWS-4 project. " } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -87241,35 +86819,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "15-075r1" + "@value": "06-187r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "A Use-Case for Mobile Location Services with IndoorGML - Indoor Navigation for Visually Impaired People" + "@value": "OWS-4 Workflow IPR" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-080r4", + "@id": "http://www.opengis.net/def/docs/07-036", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-02-25" + "@value": "2007-10-05" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jerome Gasperi" + "@value": "Clemens Portele" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/sap" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -87279,27 +86857,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=31065" + "@id": "https://portal.ogc.org/files/?artifact_id=20509" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GML 3.1.1 Application Schema for EO products" + "@value": "07-036" }, { "@language": "en", - "@value": "06-080r4" + "@value": "Geography Markup Language (GML) Encoding Standard" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/sap" + "@id": "http://www.opengis.net/def/doc-type/is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGC" + "@value": "The OpenGIS® Geography Markup Language Encoding Standard (GML) The Geography Markup Language (GML) is an XML grammar for expressing geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. As with most XML based grammars, there are two parts to the grammar – the schema that describes the document and the instance document that contains the actual data.\r\nA GML document is described using a GML Schema. This allows users and developers to describe generic geographic data sets that contain points, lines and polygons. However, the developers of GML envision communities working to define community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas] that are specialized extensions of GML. Using application schemas, users can refer to roads, highways, and bridges instead of points, lines and polygons. If everyone in a community agrees to use the same schemas they can exchange data easily and be sure that a road is still a road when they view it.\r\n\r\nClients and servers with interfaces that implement the OpenGIS® Web Feature Service Interface Standard[http://www.opengeospatial.org/standards/wfs] read and write GML data. GML is also an ISO standard (ISO 19136:2007) [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32554 ]. \r\nSee also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -87310,35 +86888,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-080r4" + "@value": "07-036" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML 3.1.1 Application Schema for EO products" + "@value": "OpenGIS Geography Markup Language (GML) Encoding Standard" } ] }, { - "@id": "http://www.opengis.net/def/docs/06-080", + "@id": "http://www.opengis.net/def/docs/06-103r3", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-07-27" + "@value": "2007-01-29" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Jerome Gasperi" + "@value": "John Herring" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -87348,27 +86926,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=15546" + "@id": "https://portal.ogc.org/files/?artifact_id=18241" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "GML Application Schema for EO Products" + "@value": "06-103r3" }, { "@language": "en", - "@value": "06-080" + "@value": "Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/d-is" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGCTM Catalogue Services Specification v2.0.0 (with Corrigendum) [OGC 04-021r3]." + "@value": "The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. \r\n\r\nPart 1 “Common Architecture supplies the common feature model for use by applications that will use the Simple Features data stores and access interfaces. \r\n\r\nPart 2 provides a standard SQL implementation of the abstract model in Part 1. (Note: The OpenGIS® Simple Features Interface Standards for OLE/COM and CORBA are no longer current and are not provided here.) \r\n\r\nThe corresponding standard for the Web is the OpenGIS® Web Feature Service Interface Standard http://www.opengeospatial.org/standards/wfs.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -87379,35 +86957,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "06-080" + "@value": "06-103r3" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "GML Application Schema for EO Products" + "@value": "OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture" } ] }, { - "@id": "http://www.opengis.net/def/docs/01-061", + "@id": "http://www.opengis.net/def/docs/09-031r1", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2001-08-24" + "@value": "2009-07-16" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Raj Singh" + "@value": "Thomas Everding" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -87417,27 +86995,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=1072" + "@id": "https://portal.ogc.org/files/?artifact_id=34118" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "Web Terrain Server" + "@value": "09-031r1" }, { "@language": "en", - "@value": "01-061" + "@value": "OWS-6 SWE Information Model Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "The purpose of theWeb Terrain Server (WTS) is to produce perspective views of georeferenced data - typically 3-dimensional coverages." + "@value": "This OGC® document is an OGC Engineering Report for the “Harmonization of SWE Information Models” activity within the OWS-6 SWE thread.\r\nThe document discusses relations between OGC standards SensorML, SWE Common and GML and investigates solutions for increased synergy between these standards. This activity also created UML models of the data types used in SWE and GML.\r\nThis report shows how UncertML can be integrated into different SWE encodings, namely SWE Common and Observations and Measurements.\r\nThis report further discusses the integration of MathML and EML into the SWE environment with an emphasis on SensorML processes and processing.\r\nThis document does not discuss the SWE information model related aspects of catalog entries for sensor services and discovery. This topic is covered in a separate Engineering Report.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -87448,35 +87026,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "01-061" + "@value": "09-031r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Web Terrain Server" + "@value": "OWS-6 SWE Information Model Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/19-024r1", + "@id": "http://www.opengis.net/def/docs/03-002r8", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2019-12-20" + "@value": "2003-05-07" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Hector Rodriguez" + "@value": "Craig Bruce" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -87486,27 +87064,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/per/19-024r1.html" + "@id": "https://portal.ogc.org/files/?artifact_id=1386" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Federated Clouds Security Engineering Report" + "@value": "Binary-XML Encoding Specification" }, { "@language": "en", - "@value": "19-024r1" + "@value": "03-002r8" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/per" + "@id": "http://www.opengis.net/def/doc-type/d-dp" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC Testbed-15 Engineering Report (ER) documents the concept for different types of federation through the lens of security. The primary focus of the work documented in this ER is on analyzing how federated membership, resource and access policy management can be provided within a security environment, while also providing portability and interoperability to all stakeholders.\r\n\r\nIn the Testbed, a practical approach for providing this functionality was exercised and documented for two administrative domains: One based on a centralized entity (Federation Manager) and the other showcasing a distributed architecture." + "@value": "This document specifies a binary encoding format for the efficient representation of XML data, especially scientific data that is characterized by arrays of numbers. This encoding format is applicable to any application that uses XML format." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -87517,1272 +87095,1622 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "19-024r1" + "@value": "03-002r8" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Testbed-15: Federated Clouds Security Engineering Report" + "@value": "Binary-XML Encoding Specification" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/per/collection", + "@id": "http://www.opengis.net/def/docs/18-058", "@type": [ - "http://www.w3.org/2004/02/skos/core#Collection" + "http://www.w3.org/2004/02/skos/core#Concept" ], - "http://www.w3.org/2000/01/rdf-schema#label": [ + "http://purl.org/dc/terms/created": [ { - "@value": "Documents of type Public Engineering Report" + "@type": "xsd:date", + "@value": "2020-11-02" } ], - "http://www.w3.org/2004/02/skos/core#definition": [ + "http://purl.org/dc/terms/creator": [ { - "@value": "Documents of type Public Engineering Report" + "@value": "Clements Portele, Panagiotis (Peter) A. Vretanos" } ], - "http://www.w3.org/2004/02/skos/core#inScheme": [ + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs" + "@id": "http://www.opengis.net/def/doc-type/is" } ], - "http://www.w3.org/2004/02/skos/core#member": [ - { - "@id": "http://www.opengis.net/def/docs/20-020" - }, - { - "@id": "http://www.opengis.net/def/docs/18-034r3" - }, - { - "@id": "http://www.opengis.net/def/docs/15-051r3" - }, - { - "@id": "http://www.opengis.net/def/docs/19-021" - }, - { - "@id": "http://www.opengis.net/def/docs/13-032" - }, - { - "@id": "http://www.opengis.net/def/docs/22-017" - }, - { - "@id": "http://www.opengis.net/def/docs/16-045r2" - }, - { - "@id": "http://www.opengis.net/def/docs/19-025r1" - }, - { - "@id": "http://www.opengis.net/def/docs/21-025" - }, - { - "@id": "http://www.opengis.net/def/docs/16-063" - }, - { - "@id": "http://www.opengis.net/def/docs/18-048r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-075r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-062" - }, - { - "@id": "http://www.opengis.net/def/docs/17-037" - }, - { - "@id": "http://www.opengis.net/def/docs/16-033r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-007" - }, - { - "@id": "http://www.opengis.net/def/docs/15-066r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-018r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-041r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-024r2" - }, - { - "@id": "http://www.opengis.net/def/docs/12-118" - }, - { - "@id": "http://www.opengis.net/def/docs/12-095" - }, - { - "@id": "http://www.opengis.net/def/docs/17-026r1" - }, - { - "@id": "http://www.opengis.net/def/docs/14-021r2" - }, - { - "@id": "http://www.opengis.net/def/docs/20-013r4" - }, - { - "@id": "http://www.opengis.net/def/docs/15-053r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-038" - }, - { - "@id": "http://www.opengis.net/def/docs/09-016" - }, - { - "@id": "http://www.opengis.net/def/docs/08-176r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-095r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-054" - }, - { - "@id": "http://www.opengis.net/def/docs/20-083r2" - }, - { - "@id": "http://www.opengis.net/def/docs/17-019" - }, - { - "@id": "http://www.opengis.net/def/docs/11-097" - }, - { - "@id": "http://www.opengis.net/def/docs/09-032" - }, - { - "@id": "http://www.opengis.net/def/docs/15-058" - }, - { - "@id": "http://www.opengis.net/def/docs/20-087" - }, - { - "@id": "http://www.opengis.net/def/docs/12-155" - }, - { - "@id": "http://www.opengis.net/def/docs/16-094r3" - }, - { - "@id": "http://www.opengis.net/def/docs/18-025" - }, - { - "@id": "http://www.opengis.net/def/docs/10-194r3" - }, - { - "@id": "http://www.opengis.net/def/docs/16-115" - }, - { - "@id": "http://www.opengis.net/def/docs/11-086r1" - }, - { - "@id": "http://www.opengis.net/def/docs/15-057r2" - }, - { - "@id": "http://www.opengis.net/def/docs/11-116" - }, - { - "@id": "http://www.opengis.net/def/docs/15-118r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-038r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-003" - }, - { - "@id": "http://www.opengis.net/def/docs/09-138" - }, - { - "@id": "http://www.opengis.net/def/docs/21-017r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-083" - }, - { - "@id": "http://www.opengis.net/def/docs/23-043" - }, - { - "@id": "http://www.opengis.net/def/docs/18-032r2" - }, - { - "@id": "http://www.opengis.net/def/docs/19-027r2" - }, - { - "@id": "http://www.opengis.net/def/docs/09-053r5" - }, - { - "@id": "http://www.opengis.net/def/docs/12-163" - }, - { - "@id": "http://www.opengis.net/def/docs/17-028" - }, - { - "@id": "http://www.opengis.net/def/docs/18-030" - }, - { - "@id": "http://www.opengis.net/def/docs/23-044" - }, - { - "@id": "http://www.opengis.net/def/docs/23-048" - }, - { - "@id": "http://www.opengis.net/def/docs/12-159" - }, - { - "@id": "http://www.opengis.net/def/docs/17-088r1" - }, - { - "@id": "http://www.opengis.net/def/docs/20-043" - }, - { - "@id": "http://www.opengis.net/def/docs/16-039r2" - }, - { - "@id": "http://www.opengis.net/def/docs/20-035" - }, - { - "@id": "http://www.opengis.net/def/docs/20-042" - }, - { - "@id": "http://www.opengis.net/def/docs/20-045" - }, - { - "@id": "http://www.opengis.net/def/docs/18-089" - }, - { - "@id": "http://www.opengis.net/def/docs/11-106r1" - }, - { - "@id": "http://www.opengis.net/def/docs/14-038r1" - }, - { - "@id": "http://www.opengis.net/def/docs/09-156r2" - }, - { - "@id": "http://www.opengis.net/def/docs/16-034" - }, - { - "@id": "http://www.opengis.net/def/docs/17-022" - }, - { - "@id": "http://www.opengis.net/def/docs/16-064r1" - }, - { - "@id": "http://www.opengis.net/def/docs/10-087" - }, - { - "@id": "http://www.opengis.net/def/docs/19-046r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-089r1" - }, - { - "@id": "http://www.opengis.net/def/docs/20-037" - }, - { - "@id": "http://www.opengis.net/def/docs/16-092r2" - }, - { - "@id": "http://www.opengis.net/def/docs/21-013" - }, - { - "@id": "http://www.opengis.net/def/docs/15-025r2" - }, - { - "@id": "http://www.opengis.net/def/docs/20-034" - }, - { - "@id": "http://www.opengis.net/def/docs/15-048r3" - }, - { - "@id": "http://www.opengis.net/def/docs/15-050r3" - }, - { - "@id": "http://www.opengis.net/def/docs/18-083" - }, - { - "@id": "http://www.opengis.net/def/docs/18-023r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-154" - }, - { - "@id": "http://www.opengis.net/def/docs/14-016" - }, - { - "@id": "http://www.opengis.net/def/docs/17-094r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-030r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-028r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-104r1" - }, - { - "@id": "http://www.opengis.net/def/docs/20-091" - }, - { - "@id": "http://www.opengis.net/def/docs/16-031r1" - }, - { - "@id": "http://www.opengis.net/def/docs/12-160r1" - }, - { - "@id": "http://www.opengis.net/def/docs/11-073r2" - }, - { - "@id": "http://www.opengis.net/def/docs/11-114" - }, - { - "@id": "http://www.opengis.net/def/docs/10-088r3" - }, - { - "@id": "http://www.opengis.net/def/docs/19-023r1" - }, - { - "@id": "http://www.opengis.net/def/docs/14-017" - }, - { - "@id": "http://www.opengis.net/def/docs/16-022" - }, - { - "@id": "http://www.opengis.net/def/docs/19-018" - }, - { - "@id": "http://www.opengis.net/def/docs/10-002" - }, - { - "@id": "http://www.opengis.net/def/docs/11-139r2" - }, - { - "@id": "http://www.opengis.net/def/docs/12-096" - }, - { - "@id": "http://www.opengis.net/def/docs/10-132" - }, - { - "@id": "http://www.opengis.net/def/docs/12-151" - }, - { - "@id": "http://www.opengis.net/def/docs/17-032r2" - }, - { - "@id": "http://www.opengis.net/def/docs/15-082" - }, - { - "@id": "http://www.opengis.net/def/docs/11-091" - }, - { - "@id": "http://www.opengis.net/def/docs/21-044" - }, - { - "@id": "http://www.opengis.net/def/docs/22-031r1" - }, - { - "@id": "http://www.opengis.net/def/docs/13-080r3" - }, - { - "@id": "http://www.opengis.net/def/docs/22-054r1" - }, - { - "@id": "http://www.opengis.net/def/docs/18-047r3" - }, - { - "@id": "http://www.opengis.net/def/docs/14-028r1" - }, - { - "@id": "http://www.opengis.net/def/docs/19-073r1" - }, - { - "@id": "http://www.opengis.net/def/docs/16-044" - }, - { - "@id": "http://www.opengis.net/def/docs/16-041r1" - }, - { - "@id": "http://www.opengis.net/def/docs/17-020r1" - }, - { - "@id": "http://www.opengis.net/def/docs/23-025" - }, - { - "@id": "http://www.opengis.net/def/docs/16-023r3" - }, - { - "@id": "http://www.opengis.net/def/docs/20-067" - }, - { - "@id": "http://www.opengis.net/def/docs/22-014" - }, - { - "@id": "http://www.opengis.net/def/docs/17-061" - }, - { - "@id": "http://www.opengis.net/def/docs/23-020r2" - }, - { - "@id": "http://www.opengis.net/def/docs/16-030" - }, - { - "@id": "http://www.opengis.net/def/docs/10-127r1" - }, - { - "@id": "http://www.opengis.net/def/docs/21-030" - }, - { - "@id": "http://www.opengis.net/def/docs/18-046" - }, - { - "@id": "http://www.opengis.net/def/docs/15-052r1" - }, + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/23-042" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/18-049r1" - }, + "@id": "https://docs.ogc.org/is/18-058/18-058.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/10-074" + "@language": "en", + "@value": "OGC API - Features - Part 2: Coordinate Reference Systems by Reference" }, { - "@id": "http://www.opengis.net/def/docs/17-043" - }, + "@language": "en", + "@value": "18-058" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/21-054" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/10-061r1" - }, + "@value": "OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks.\r\n\r\nOGC API Features provides API building blocks to create, modify and query features on the Web. OGC API Features is comprised of multiple parts, each of them is a separate standard.\r\n\r\nThis part extends the core capabilities specified in Part 1: Core with the ability to use coordinate reference system identifiers other than the defaults defined in the core." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/18-085" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/19-010r2" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "18-058" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/16-017" - }, + "@language": "en", + "@value": "OGC API - Features - Part 2: Coordinate Reference Systems by Reference" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/21-030", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/15-026" - }, + "@type": "xsd:date", + "@value": "2022-04-08" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/10-060r1" - }, + "@value": "Mahnoush Alsadat Mohammadi Jahromi, Alex Robin" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/14-079r1" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/15-030r3" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/11-019r2" - }, + "@id": "https://docs.ogc.org/per/21-030.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/20-030" + "@language": "en", + "@value": "21-030" }, { - "@id": "http://www.opengis.net/def/docs/20-016" - }, + "@language": "en", + "@value": "OGC Testbed-17: SIF Semantic Model Engineering Report" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/16-035" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/20-018" - }, + "@value": "This Engineering Report (ER) presents an analysis of the semantic model of the Sensor Integration Framework (SIF). After reviewing the current SIF Semantic Model, existing related ontologies are reviewed. The ER discusses the results and includes all lessons learned from the experiments completed by the Sensor Integration thread of the OGC Testbed-17 initiative. The ER presents a series of recommendations based on the lessons learned." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/15-067" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/23-011r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "21-030" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/21-039r1" - }, + "@language": "en", + "@value": "OGC Testbed-17: SIF Semantic Model Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/20-013r4", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/09-015" - }, + "@type": "xsd:date", + "@value": "2020-07-29" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/23-027" - }, + "@value": "Jonathan Pritchard" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/12-075" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/10-059r2" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/19-088r2" - }, + "@id": "https://docs.ogc.org/per/20-013r4.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/19-024r1" + "@language": "en", + "@value": "20-013r4" }, { - "@id": "http://www.opengis.net/def/docs/16-036r1" - }, + "@language": "en", + "@value": "Maritime Limits and Boundaries Pilot: Engineering Report" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/21-075r2" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/14-000" - }, + "@value": "This document comprises the Engineering Report (ER) and documents the activities under Phase 1 and Phase 2 of the OGC Maritime Limits and Boundaries (MLB) Pilot.\r\n\r\nThis Engineering Report details the activities undertaken by participants in the pilot, the data supplied, transformed, and used to demonstrate the pilot’s objectives, and the results of the various interoperability tests performed within the pilot. Also documented here are the various outputs from the pilot activities, where they are directed, and where updates or clarifications are recommended to external standards or other elements of the broader ecosystem.\r\n\r\nThe ER documents the journey taken within the project, from its origins as an architectural statement of intent, through to the definition of its core elements (the GML application schema which lends a common language to the data) and the implementation of that schema within COTS, open source and bespoke software elements. The engineering report also summarizes the outputs from the process, any unresolved issues, and potential enhancements for the future." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/11-063r6" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/18-021" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "20-013r4" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/15-022" - }, + "@language": "en", + "@value": "OGC Maritime Limits and Boundaries Pilot: Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/16-102r2", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/19-082r1" - }, + "@type": "xsd:date", + "@value": "2017-08-16" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/23-028" - }, + "@value": "Paul Scarponcini" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/14-049" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/23-059" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/09-067r2" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=75119" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/14-057" + "@language": "en", + "@value": "16-102r2" }, { - "@id": "http://www.opengis.net/def/docs/20-011" - }, + "@language": "en", + "@value": "InfraGML 1.0: Part 2 - LandInfra Facilities and Projects - Encoding Standard" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/19-070" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/21-031" - }, + "@value": "This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums.\r\nInfraGML is published as a multi-part standard. This Part 2 addresses the Facility and Project Requirements Classes from LandInfra." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/18-050r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/09-050r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "16-102r2" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/17-041" - }, + "@language": "en", + "@value": "OGC InfraGML 1.0: Part 2 - LandInfra Facilities and Projects - Encoding Standard" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/21-031", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/22-023r2" - }, + "@type": "xsd:date", + "@value": "2022-02-08" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/16-043" - }, + "@value": "Sam Meek" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/18-090r2" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/12-119r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/19-026" - }, + "@id": "https://docs.ogc.org/per/21-031.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/16-021r1" + "@language": "en", + "@value": "UML Modeling Best Practice Engineering Report" }, { - "@id": "http://www.opengis.net/def/docs/10-155" - }, + "@language": "en", + "@value": "21-031" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/18-045" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/16-038" - }, + "@value": "This OGC Best Practice provides readers with guidance on how to use the Unified Modeling Language (UML) within the scope of OGC work. Recently there has been a move to a resource-based approach for OGC Application Programming Interface (API) definition through the OpenAPI Specification and away from the service-based approach specified in OGC Web Service (OWS) standards. Previously, the interface definitions were almost exclusively XML based, therefore models described using UML class diagrams and conceptual models in general simply mapped 1:1 to derive the XML schema. Using API resources has resulted in the possibility of deriving multiple target technologies from a single standard and therefore, UML model. An additional point of discussion within the OGC is the value added by conceptual modeling using UML. Models included in OGC Standards vary from diagrams only, to conceptual models and model fragments all the way through to Model Driven Architecture (MDA) where UML models are used to directly derive implementable artifacts such as schemas.\r\n\r\nUML has been the main modeling language of choice within the OGC, although up until now, there has been little guidance within the OGC on appropriate use of UML. These Best Practices do not seek to govern the use of UML within the OGC as it is recognized that UML is a flexible language that has applications beyond the current OGC doctrine. However, the practices seek to provide guidance to assist in adherence to the following principles:\r\n\r\n Correctness — Adherence to the Object Management Group (OMG) UML standard.\r\n Consistency — UML artifacts should be consistent across OGC Standards and with supporting standards such as those specified by ISO/TC 211.\r\n FAIRness — Findable, Accessible, Interoperable and Reusable models.\r\n Value — Any modeling done, UML or otherwise, should add value to the parent standard. That is, the modeling should do work for the community that is not done elsewhere.\r\nThe Practices are as follows:\r\n\r\n Practice 1: UML models should follow the OMG UML 2.5.1 Standard ratified in 2017.\r\n Practice 2: OGC Conceptual Models should be represented as UML Class diagrams.\r\n Practice 3: OGC Conceptual Models should be platform independent.\r\n Practice 4: OGC Conceptual Models should use concepts consistently across standards.\r\n Practice 5: OGC Standards should contain a UML model at least at the conceptual level of detail.\r\n Practice 6: UML models in OGC Standards should add value.\r\n Practice 7: UML models should describe structure in the engineering process.\r\n Practice 8: Modeling artifacts should be provided in full.\r\n Practice 9: UML models should at least be consistent with supporting text, but ideally normative.\r\n Practice 10: UML tooling should produce interoperable artifacts.\r\n Practice 11: UML can be used for modeling semantics, although there are other technologies that are more appropriate.\r\n Practice 12: OGC UML models should be machine readable (i.e. available in XMI format, in addition to the format of the UML Editor used to create the model)." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/18-094r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/12-018r2" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "21-031" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/21-023" - }, + "@language": "en", + "@value": "OGC Testbed-17: UML Modeling Best Practice Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/20-033", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/16-027" - }, + "@type": "xsd:date", + "@value": "2021-01-13" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/21-074r2" - }, + "@value": "Sam Meek" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/12-162r1" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/20-015r2" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/11-064r3" - }, + "@id": "https://docs.ogc.org/per/20-033.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/12-156" + "@language": "en", + "@value": "20-033" }, { - "@id": "http://www.opengis.net/def/docs/15-046r2" - }, + "@language": "en", + "@value": "OpenAPI Engineering Report" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/11-107" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/16-067r4" - }, + "@value": "This OGC Testbed 16 Engineering Report (ER) documents the two major aspects of the Testbed 16 OpenAPI Thread. These are:\r\n\r\nA Unified Modeling Language (UML) metamodel that describes OpenAPI and a profile of that model to describe OGC API - Features - Part 1: Core;\r\n\r\nAn implementation of a transformation procedure in the ShapeChange open source software. This procedure was designed to transform a UML representation of the OGC API - Features - Part 1: Core model into an OpenAPI 3.0 document.\r\n\r\nThe process for creating the model and doing the transformation relied upon the Model Driven Architecture (MDA) approach. MDA takes a platform independent model (PIM) and transforms that model into a platform specific model (PSM)." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/16-014r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/17-025r2" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "20-033" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/13-046r2" - }, + "@language": "en", + "@value": "OGC Testbed-16: OpenAPI Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/09-123", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/18-086r1" - }, + "@type": "xsd:date", + "@value": "2009-10-13" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/16-053r1" - }, + "@value": "Roland M. Wagner" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/15-077r1" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/19-032" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/10-086r1" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=35516" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/11-108" + "@language": "en", + "@value": "09-123" }, { - "@id": "http://www.opengis.net/def/docs/21-058" - }, + "@language": "en", + "@value": "GeoRM Role Model" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/12-105" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/21-018" - }, + "@value": "The scope of this document is the update and the definition of GeoRM roles as a sub model of the GDI.NRW reference model (process model and architecture model). Key relationships are defined between these roles." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/14-044" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/16-061" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "09-123" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/14-009r1" - }, + "@language": "en", + "@value": "GeoRM Role Model" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/18-047r3", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/09-007" - }, + "@type": "xsd:date", + "@value": "2019-02-07" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/19-084" - }, + "@value": "Eugene Genong Yu, Liping Di" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/18-009" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/17-021" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/09-129" - }, + "@id": "https://docs.ogc.org/per/18-047r3.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/21-019" + "@language": "en", + "@value": "Swath Coverage Engineering Report" }, { - "@id": "http://www.opengis.net/def/docs/22-035" - }, + "@language": "en", + "@value": "18-047r3" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/12-093" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/16-042r1" - }, + "@value": "This Engineering Report (ER) presents a summary, description and findings of the Swath Coverage task conducted by the OGC Testbed-14 initiative." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/18-022r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/10-079r3" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "18-047r3" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/12-103r3" - }, + "@language": "en", + "@value": "OGC Testbed-14: Swath Coverage Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/12-026", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/09-072" - }, + "@type": "xsd:date", + "@value": "2012-04-18" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/18-076" - }, + "@value": "Andreas Matheus" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/14-002" - }, + "@id": "http://www.opengis.net/def/doc-type/techpaper" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/17-090r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/24-008" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=47848" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/17-093r1" + "@language": "en", + "@value": "Architecture of an Access Management Federation for Spatial Data and Services in Germany" }, { - "@id": "http://www.opengis.net/def/docs/22-040" - }, + "@language": "en", + "@value": "12-026" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/13-011" - }, + "@id": "http://www.opengis.net/def/doc-type/techpaper" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/22-016r3" - }, + "@value": "An Access Management Federation (AMF) is a network of organizations that trust each other for the\r\nmeans of sharing protected resources among each other. Worldwide, many academic AMFs are\r\navailable for the purpose of sharing information and services between academic institutions such\r\nas Universities and Research Organizations. In the academia, some of the well known AMFs are UK\r\nAccess Management Federation (United Kingdom http://www.ukfederation.org.uk/), In Common\r\n(USA http://www.incommon.org/) and DFN-AAI (Germany https://www.aai.dfn.de)." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/09-034" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/11-092r2" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "12-026" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/21-020r1" - }, + "@language": "en", + "@value": "Architecture of an Access Management Federation for Spatial Data and Services in Germany" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/08-068r3", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/09-064r2" - }, + "@type": "xsd:date", + "@value": "2021-06-15" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/20-032" - }, + "@value": "Peter Baumann" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/21-028" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/21-008" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/23-033" - }, + "@id": "https://docs.ogc.org/is/08-068r3/08-068r3.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/12-094" + "@language": "en", + "@value": "08-068r3" }, { - "@id": "http://www.opengis.net/def/docs/09-140r2" - }, + "@language": "en", + "@value": "Web Coverage Processing Service (WCPS) Language Interface Standard" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/18-028r2" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/17-036" - }, + "@value": "The OGC Web Coverage Processing Service (WCPS) defines a protocol-independent language for on-demand extraction, processing, and analysis of multi-dimensional gridded coverages (datacubes) representing among others spatio-temporal sensor, image, simulation, or statistics data." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/20-012" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/20-073" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "08-068r3" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/14-037" - }, + "@language": "en", + "@value": "Web Coverage Processing Service (WCPS) Language Interface Standard" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/08-001", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/18-038r2" - }, + "@type": "xsd:date", + "@value": "2008-04-29" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/17-035" - }, + "@value": "Raj Singh" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/21-027" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/09-182r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/17-024" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=26609" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/14-086r1" + "@language": "en", + "@value": "Loosely Coupled Synchronization of Geographic Databases in the CGDI" }, { - "@id": "http://www.opengis.net/def/docs/10-192" - }, + "@language": "en", + "@value": "08-001" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/15-028" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/11-061r1" - }, + "@value": "This Discussion Paper documents results from the Interoperability Program CGDI Pilot and describes a suite of services that enable the sharing of geographic information across organizations for the purposes of: geographic database synchronization in support of a spatial data infrastructure; geographic database modification suggestions from trusted and un-trusted sources; and the transmission of geographic information in emergency notification events.\r\n\r\nThese services are called the Update Feed Service; Feedback Feed Service; and Emergency Alert Service respectively. Their information encodings are all based on the Atom Syndication Format, extended with GML and WFS Filter encodings to support geospatial requirements, and were implemented in the Canadian Geospatial Data Infrastructure Pilot.\r\n" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/16-018" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/16-055" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "08-001" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/16-051" - }, + "@language": "en", + "@value": "OGC® Loosely Coupled Synchronization of Geographic Databases in the Canadian Geospatial Data Infrastructure Pilot" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/08-007r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/11-096" - }, + "@type": "xsd:date", + "@value": "2008-08-20" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/11-093r2" - }, + "@value": "Gerhard Gröger, Thomas H. Kolbe, Angela Czerwinski, Claus Nagel" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/15-027r1" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/21-064" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/17-027" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=28802" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/21-032" + "@language": "en", + "@value": "08-007r1" }, { - "@id": "http://www.opengis.net/def/docs/18-036r1" - }, + "@language": "en", + "@value": "City Geography Markup Language (CityGML) Encoding Standard" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/17-045" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/22-020r1" - }, + "@value": "CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211.\r\n\r\nThe aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. \r\n" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/20-019r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/21-021" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "08-007r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/15-047r3" - }, + "@language": "en", + "@value": "OpenGIS® City Geography Markup Language (CityGML) Encoding Standard" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/12-100r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/13-053r1" - }, + "@type": "xsd:date", + "@value": "2014-05-28" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/09-033" - }, + "@value": "Stephan Meissl" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/11-113r1" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/19-062" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/15-024r2" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=54813" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/22-043r1" + "@language": "en", + "@value": "12-100r1" }, { - "@id": "http://www.opengis.net/def/docs/22-013r3" - }, + "@language": "en", + "@value": "GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/11-062r2" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/12-139" - }, + "@value": "This Interface Standard is a profile of the OGC® GML Application Schema –Coverages version 1.0 [OC 09-146r2]. This document specifies the usage of the GeoTIFF data format for the encoding of GML coverages. This encoding is used by several OGC services like the Web Coverage Service (WCS) 2.0 Interface Standard – Core [OGC 09-110r4]." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/21-035r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/18-029" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "12-100r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/17-078" - }, + "@language": "en", + "@value": "OGC® GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/19-045r3", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/17-040" - }, + "@type": "xsd:date", + "@value": "2020-05-21" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/09-006" - }, + "@value": "Kyoung-Sook KIM, Nobuhiro ISHIMARU" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/16-059" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/19-075r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/18-026r1" - }, + "@id": "https://docs.ogc.org/is/19-045r3/19-045r3.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/15-011r2" + "@language": "en", + "@value": "Moving Features Encoding Extension - JSON" }, { - "@id": "http://www.opengis.net/def/docs/10-184" - }, + "@language": "en", + "@value": "19-045r3" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/18-090r1" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/22-041" - }, + "@value": "This standard defines how to encode and share the various movements of geographic features by using JavaScript Object Notation (JSON). It provides an alternative encoding for OGC Moving Features instead of that provided in the XML Core [OGC 14-083r2] and Simple CSV [OGC 14-084r2] standards. A moving feature, for instance a vehicle or a pedestrian, contains a temporal geometry whose location continuously changes over time and dynamic non-spatial attributes whose values vary with time. This Moving Features JSON encoding defines a set of keywords to implement the conceptual schema of moving features defined in ISO 19141:2008 [ISO 19141:2008], accompanied with IETF GeoJSON Format [IETF RFC 7946]." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/20-027" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/19-012r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "19-045r3" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/12-097" - }, + "@language": "en", + "@value": "OGC Moving Features Encoding Extension - JSON" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/19-086r4", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/10-073r1" - }, + "@type": "xsd:date", + "@value": "2021-08-13" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/20-025r1" - }, + "@value": "Mark Burgoyne, Dave Blodgett, Chuck Heazel, Chris Little" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/09-063" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/18-057" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/12-152r1" - }, + "@id": "https://docs.ogc.org/is/19-086r4/19-086r4.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/09-031r1" + "@language": "en", + "@value": "19-086r4" }, { - "@id": "http://www.opengis.net/def/docs/09-012" - }, + "@language": "en", + "@value": "OGC API - Environmental Data Retrieval Standard" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/20-038" - }, + "@id": "http://www.opengis.net/def/doc-type/is" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/08-124r1" - }, + "@value": "The Environmental Data Retrieval (EDR) Application Programming Interface (API) provides a family of lightweight query interfaces to access spatio-temporal data resources by requesting data at a Position, within an Area, along a Trajectory or through a Corridor. A spatio-temporal data resource is a collection of spatio-temporal data that can be sampled using the EDR query pattern geometries. These patterns are described in the section describing the Core Requirements Class.\r\n\r\nThe goals of the EDR API are to make it easier to access a wide range of data through a uniform, well-defined simple Web interface, and to achieve data reduction to just the data needed by the user or client while hiding much of the data storage complexity. A major use case for the EDR API is to retrieve small subsets from large collections of environmental data, such as weather forecasts, though many other types of data can be accessed. The important aspect is that the data can be unambiguously specified by spatio-temporal coordinates.\r\n\r\nThe EDR API query patterns, such as Position, Area, Cube, Trajectory or Corridor, can be thought of as discrete sampling geometries, conceptually consistent with the feature of interest in the Sensor Observation Service (SOS) standard. A typical EDR data resource is a multidimensional dataset that could be accessed via an implementation of the Web Coverage Service (WCS) standard. In contrast to SOS and WCS, EDR implements the technical baseline of the OGC API family of standards and aims to provide a single set of simple-to-use query patterns. Use cases for EDR range from real or virtual time-series observation retrievals, to sub-setting 4-dimensional data cubes along user-supplied sampling geometries. These query patterns do not attempt to satisfy the full scope of either SOS or WCS, but provide useful building blocks to allow the composition of APIs that satisfy a wide range of geospatial data use cases. By defining a small set of query patterns (and no requirement to implement all of them), the EDR API should help to simplify the design of systems (as they can be performance tuned for the supported queries) making it easier to build robust and scalable infrastructure.\r\n\r\nWith the OGC API family of standards, the OGC community has extended its suite of standards to include Resource Oriented Architectures and Web Application Programming Interfaces (APIs). These standards are based on a shared foundation, specified in OGC API-Common, which defines the resources and access paths that are supported by all OGC APIs. The resources are listed in Table 1. This document extends that foundation to define the Environmental Data Retrieval API." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/20-021r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/23-010" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "19-086r4" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/14-114r1" - }, + "@language": "en", + "@value": "OGC API - Environmental Data Retrieval Standard" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/06-049r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/10-094" - }, + "@type": "xsd:date", + "@value": "2006-05-08" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/11-134" - }, + "@value": "Peter Vretanos" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/23-047" - }, + "@id": "http://www.opengis.net/def/doc-type/d-profile" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/12-157" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/15-068r2" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=15201" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/16-099" + "@language": "en", + "@value": "GML 3.1.1 simple features profile" }, { - "@id": "http://www.opengis.net/def/docs/11-013r6" - }, + "@language": "en", + "@value": "06-049r1" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/16-037" - }, + "@id": "http://www.opengis.net/def/doc-type/d-profile" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/21-055" - }, + "@value": "The OpenGIS® GML 3.1.1 Simple Features Profile (GML for Simple Features) is a restricted subset of GML (Geography Markup Language)[http://www.opengeospatial.org/standards/gml] and XML Schema [www.w3.org/XML/Schema] that supports the XML encoding of geographic features with simple geometric property types (Points, Line and Polygons). The profile defines three conformance classes that define three different levels of complexity. \r\n\r\nSee also the GML pages on OGC Network: http://www.ogcnetwork.net/gml .\r\n" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/20-039r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/16-020" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "06-049r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/16-046r1" - }, + "@language": "en", + "@value": "GML 3.1.1 simple features profile" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/15-123r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/16-029r1" - }, + "@type": "xsd:date", + "@value": "2016-02-16" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/21-042" - }, + "@value": "Jeff Yutzler" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/18-035" - }, + "@id": "http://www.opengis.net/def/doc-type/notes" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/17-018" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/17-048" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=67120" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/12-147" + "@language": "en", + "@value": "Geopackage Release Notes" }, { - "@id": "http://www.opengis.net/def/docs/18-091r2" - }, + "@language": "en", + "@value": "15-123r1" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/12-133" - }, + "@id": "http://www.opengis.net/def/doc-type/notes" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/15-010r4" - }, + "@value": "This document provides the set of revision notes for the existing OGC Implementation Standard GeoPackage version 1.1 (OGC 12-128r12) and does not modify that standard.\r\nThis document was approved by the OGC membership on . As a result of the OGC Standards Working Group (SWG) process, there were a number of edits and enhancements made to this standard. This document provides the details of those edits, deficiency corrections, and enhancements. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility.\r\n" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/09-035" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/13-054r1" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "15-123r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/16-056" - }, + "@language": "en", + "@value": "Geopackage Release Notes" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/14-057", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/18-074" - }, + "@type": "xsd:date", + "@value": "2015-03-26" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/16-097" - }, + "@value": "Bart De Lathouwer, Peter Cotroneo, Paul Lacey" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/14-013r1" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/10-131r1" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/09-073" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=61057" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/20-031" + "@language": "en", + "@value": "UK Interoperability Assessment Plugfest (UKIAP) Engineering Report " }, { - "@id": "http://www.opengis.net/def/docs/18-084" - }, + "@language": "en", + "@value": "14-057" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/18-097" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/21-022" - }, + "@value": "The Open Geospatial Consortium (OGC), the UK Ordnance Survey, AGI and Dstl conducted a first of a series of events called the United Kingdom Interoperability Assessment Plugfest (UKIAP) 2014. The purpose of UKIAP 2014 is to advance the interoperability of geospatial products and services based on OGC standards within the UK geospatial information (GI) community. The results of the Plugfest will allow Ordnance Survey to provide best practice guidance to those who want to consume or implement geospatial web services or products based on OGC standards. UKIAP 2014 is open to open- and closed source vendors and to all GI organizations in the UK to involve as many participants in the initiative as possible." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/17-046" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/19-069" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "14-057" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/10-035r2" - }, + "@language": "en", + "@value": "OGC® and Ordnance Survey - UK Interoperability Assessment Plugfest (UKIAP) Engineering Report " + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/07-097", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/19-081" - }, + "@type": "xsd:date", + "@value": "2007-10-05" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/11-085r1" - }, + "@value": "Thomas Uslander (Ed.)" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/17-029r1" - }, + "@id": "http://www.opengis.net/def/doc-type/bp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/19-040" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/10-069r2" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=23286" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/15-073r2" + "@language": "en", + "@value": "Reference Model for the ORCHESTRA Architecture" }, { - "@id": "http://www.opengis.net/def/docs/16-068r4" - }, + "@language": "en", + "@value": "07-097" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/22-004" - }, + "@id": "http://www.opengis.net/def/doc-type/bp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/15-065r1" - }, + "@value": "This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It is an extension of the OGC Reference Model and contains a specification framework for the design of geospatial service-oriented architectures and service networks. The RM-OA comprises the generic aspects of service-oriented architectures, i.e., those aspects that are independent of the risk management domain and thus applicable to other application domains. " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/22-018" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/20-029" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "07-097" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/14-007" - }, + "@language": "en", + "@value": "Reference Model for the ORCHESTRA Architecture" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/08-076", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/19-019" - }, + "@type": "xsd:date", + "@value": "2008-09-12" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/18-101" - }, + "@value": "Rüdiger Gartmann" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/16-040r1" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/17-023" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/16-098" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=28162" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/20-090" + "@language": "en", + "@value": "OWS-5 GeoRM License Broker Discussion Paper" }, { - "@id": "http://www.opengis.net/def/docs/21-036" - }, + "@language": "en", + "@value": "08-076" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/14-048" - }, + "@id": "http://www.opengis.net/def/doc-type/dp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/19-041r3" - }, + "@value": "This document describes a License Broker Service (LB-Service) as specified and implemented in the OWS-5 test bed. The LB-Service provides configurable license models, which may contain configuration parameters to be defined by the licensee. The setting of these parameters affects the actual license to be created by the LB-Service. " + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/14-029r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/11-072r2" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "08-076" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/18-078" - }, + "@language": "en", + "@value": "OWS-5 GeoRM License Broker Discussion Paper" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/04-040", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/16-048r1" - }, + "@type": "xsd:date", + "@value": "2005-02-17" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/16-052" - }, + "@value": "Bill Lalonde" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/23-050" - }, + "@id": "http://www.opengis.net/def/doc-type/d-dp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/12-146" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/12-158" - }, + "@id": "https://portal.ogc.org/files/?artifact_id=7470" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/10-036r2" + "@language": "en", + "@value": "04-040" }, { - "@id": "http://www.opengis.net/def/docs/22-038r2" - }, + "@language": "en", + "@value": "Style Management Services for Emergency Mapping Symbology" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/14-006r1" - }, + "@id": "http://www.opengis.net/def/doc-type/d-dp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/16-047r1" - }, + "@value": "This document describes the proposed system design for the OGC Style Management Service (SMS). \r\nThe SMS must manage distinct objects that represent styles and symbols and provide the means to discover, query, insert, update, and delete these objects. \r\nStyles provide the mapping from feature types and feature properties and constraints to parameterized Symbols used in drawing maps. Symbols are bundles of predefined graphical parameters and predefined fixed graphics.\r\n" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/16-137r2" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/20-041" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "04-040" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/19-020r1" - }, + "@language": "en", + "@value": "Style Management Services for Emergency Mapping Symbology" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/18-084", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/19-016r1" - }, + "@type": "xsd:date", + "@value": "2019-01-20" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/15-056" - }, + "@value": "Luis Bermudez" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/20-036" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/10-130" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/21-029" - }, + "@id": "https://docs.ogc.org/per/18-084.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/22-024r2" + "@language": "en", + "@value": "Geospatial to the Edge Plugfest Engineering Report" }, { - "@id": "http://www.opengis.net/def/docs/19-022r1" - }, + "@language": "en", + "@value": "18-084" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/17-042" - }, + "@id": "http://www.opengis.net/def/doc-type/per" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/12-144" - }, + "@value": "The Geospatial to the Edge Interoperability Plugfest, co-sponsored by the Army Geospatial Center and the National Geospatial-Intelligence Agency (NGA/CIO&T), brought together technology implementers and data providers to advance the interoperability of geospatial products and services based on profiles of OGC standards. Specifically, servers and data available via GeoPackage, Web Feature Service (WFS), Web Map Service (WMS), and Web Map Tile Service (WMTS), all following National System for Geospatial Intelligence (NSG) profiles, were exercised and improved in various clients. Compliance Tests were executed and advanced based on feedback from the participants." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/16-093r1" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/19-015" - }, + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "18-084" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@id": "http://www.opengis.net/def/docs/09-037r1" - }, + "@language": "en", + "@value": "OGC Geospatial to the Edge Plugfest Engineering Report" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/23-018r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/11-055" - }, + "@type": "xsd:date", + "@value": "2024-02-06" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/16-088r1" - }, + "@value": "Jeff Yutzler" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/14-001" - }, + "@id": "http://www.opengis.net/def/doc-type/notes" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ { - "@id": "http://www.opengis.net/def/docs/20-033" - }, + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "http://www.opengis.net/def/docs/16-050" - }, + "@id": "https://docs.ogc.org/is/12-128r19/23-018r1.html" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ { - "@id": "http://www.opengis.net/def/docs/14-008" + "@language": "en", + "@value": "Release Notes for OGC GeoPackage 1.4.0" }, { - "@id": "http://www.opengis.net/def/docs/16-049r1" - }, + "@language": "en", + "@value": "23-018r1" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/docs/14-073r1" - }, + "@id": "http://www.opengis.net/def/doc-type/notes" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ { - "@id": "http://www.opengis.net/def/docs/09-036r2" - }, + "@value": "This document provides the set of revision notes for OGC® GeoPackage Encoding Standard, version 1.4.0 [OGC 12-128r19] and does not modify that Standard.\r\n\r\nThis document provides the details of edits, deficiency corrections, and enhancements of the above-referenced Standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ { - "@id": "http://www.opengis.net/def/docs/14-039" - }, + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ { - "@id": "http://www.opengis.net/def/docs/18-087r5" + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "23-018r1" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { - "@value": "Documents of type Public Engineering Report" + "@language": "en", + "@value": "Release Notes for OGC GeoPackage 1.4.0" } ] }, { - "@id": "http://www.opengis.net/def/docs/21-041r2", + "@id": "http://www.opengis.net/def/docs/16-044", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2022-01-24" + "@value": "2017-03-09" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Sam Meek" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -88792,27 +88720,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://docs.ogc.org/dp/21-041r2.html" + "@id": "https://docs.ogc.org/per/16-044.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "21-041r2" + "@value": "Testbed-12 Web Feature Service Synchronization" }, { "@language": "en", - "@value": "OGC Conceptual Modeling Discussion Paper" + "@value": "16-044" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "Historically, conceptual modeling was utilized sporadically within the Open Geospatial Consortium (OGC). Models were used in OGC standards both informatively and normatively to describe the structure of the information within a standard for a particular domain. As independent standards-development organizations, OGC and alliance partners such as ISO / TC211 did not always develop common models. There are several examples of conceptual models in OGC’s Abstract Specifications, many of which have become ISO / TC211 standards since their publication. Outside of Abstract Specifications, there are fewer examples of conceptual models in Implementation Standards. Logical Models and Physical Models tend to be specified more in Implementation Standards.\r\n\r\nThe need for conceptual models in Implementation Standards has become apparent since the OGC is moving towards resource based architecture through the development of the OGC Application Programming Interface (API) suite of standards. In the previous ways of working, standards and encodings mapped 1:1, as many OGC standards were based on the Extensible Markup Language (XML) and a standard described a particular set of XML documents to support a domain. The move to OGC API has led towards a separation of an information model represented in a standard from encodings, which is the way that the information models are expressed in a given technology. In other words, the move to OGC API has led to a clearer separation of the logical model from the physical model.\r\n\r\nThe utilization of conceptual modeling practices may be employed to manage, track, or govern the use of concepts and terms within different standards. The OGC should adopt conceptual modeling where suitable with a new group to support the working groups with the modeling effort that may otherwise have not been completed because a lack of expertise or value recognition. Taking the concept one step further, Model Driven Architecture (MDA) is a transformation process to create a platform specific model, or implementation from a logical, platform-independent model. This process could be implemented to enable quick production of standards into different target technologies or for the creation of new standards entirely. This paper does not suggest making MDA and associated mandatory for future standards generation." + "@value": "This engineering report describes a protocol for synchronizing data between two enterprise servers. While the protocol itself is generic, this engineering report describes its application to web feature servers.\r\n\r\nIn the simplest terms, the protocol involves each synchronization peer accessing the other’s Sync resource to get the set of changed objects since the last time the Sync resource was accessed. In the case of web feature servers, the objects are features. The requesting peer then compare that list of changed features with the identically identified features in its data store and performs any necessary changes so that the feature states match.\r\n\r\nContinuing the work done in Testbed-11, this engineering report describes the implementation of a Sync operation in a WFS server that:\r\n\r\nEnhances the Sync operation from Testbed-11 to include an abstract query element where each service type can then substitute their specific query syntax for identifying the specific sub-set of changed features to be synchronized. In the case of the WFS, several query syntaxes may be used including the wfs:Query element and a REST based feature type URI with query parameters.\r\n\r\nExtends the definition of the Sync operation with the addition of a resultType parameter to allow a client to obtain a hit count of the number of features that a Sync operation shall return.\r\n\r\nShall investigate the proper procedure for handling resource references. Implementing the resolvePath parameter alone is not sufficient to ensure complete data set synchronization.\r\n\r\nShall investigate concurrency and consistency issues." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -88823,35 +88751,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "21-041r2" + "@value": "16-044" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Conceptual Modeling Discussion Paper" + "@value": "Testbed-12 Web Feature Service Synchronization" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-144r2", + "@id": "http://www.opengis.net/def/docs/12-156", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-03-11" + "@value": "2013-02-19" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Richard Martell" + "@value": "George Percivall" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -88861,27 +88789,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27093" + "@id": "https://portal.ogc.org/files/?artifact_id=51842" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "CSW-ebRIM Registry Service - Part 2: Basic extension package" + "@value": "OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report" }, { "@language": "en", - "@value": "07-144r2" + "@value": "12-156" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This OGC® document is a companion to the CSW-ebRIM catalogue profile (OGC 07-110r2). It specifies the content of the Basic extension package that shall be supported by all conforming services. The package includes extension elements of general utility that may be used to characterize a wide variety of geographic information resources, with a focus on service-oriented metadata management." + "@value": "The Reference Architecture Profiler (RAP) Advisor™ is a web based application that\r\nrecommends OGC Standards and OGC Reference Model (ORM) Sections that are\r\nrelevant to a system development; such that a community of interest could derive and\r\nbuild a profile of suitable OGC standards to meet their specific needs. This Engineering\r\nReport contains the requirements, conceptual design, development methodology, and\r\nimplementation of the RAP Advisor.\r\nInitial development of the RAP Advisor™ was concurrent with the OGC Web Services\r\nTestbed, Phase 9 (OWS-9) with NGA sponsorship. During OWS-9 timeframe, key\r\nconcepts of the RAP Advisor were confirmed through prototyping. Future development\r\nis required to complete the functions and content of the Advisor." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -88892,30 +88820,30 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-144r2" + "@value": "12-156" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CSW-ebRIM Registry Service - Part 2: Basic extension package" + "@value": "OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/16-088r1", + "@id": "http://www.opengis.net/def/docs/19-084", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2016-07-26" + "@value": "2020-07-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Alistair Ritchie" + "@value": "Andrea Aime" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ @@ -88930,17 +88858,17 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=69896" + "@id": "https://docs.ogc.org/per/19-084.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "16-088r1" + "@value": "19-084" }, { "@language": "en", - "@value": "Soil Data Interoperability Experiment" + "@value": "Vector Tiles Pilot 2: Vector Tiles Filtering Language Engineering Report" } ], "http://www.w3.org/2004/02/skos/core#broader": [ @@ -88950,7 +88878,7 @@ ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This engineering report describes the results of the Soil Data Interoperability Experiment\r\n(the IE) conducted under the auspices of the OGC Agriculture Domain Working Group in\r\n2015. Soil data exchange and analysis is compromised by the lack of a widely agreed\r\ninternational standard for the exchange of data describing soils and the sampling and\r\nanalytical activities relating to them. Previous modeling activities in Europe and\r\nAustralasia have not yielded models that satisfy many of the data needs of global soil\r\nscientists, data custodians and users. This IE evaluated existing models and proposed a\r\ncommon core model, including a GML/XML schema, which was tested through the\r\ndeployment of OGC web services and demonstration clients. IE time constraints and\r\nlimited participant resources precluded extensive modeling activities. However, the\r\nresulting model should form the core of a more comprehensive model to be developed by\r\na future OGC Soil Data Standards Working Group." + "@value": "The OGC Vector Tiles Pilot 2: Vector Tiles Filtering Language Engineering Report (ER) defines a filter language for vector data delivered as tiles (also known as vector tiles). The language applies to vector tiles served through implementations of the OGC API – Features standard and the draft OGC API - Tiles specification, but can be generally applied on all services supporting filtering by attributes.\r\n\r\nThe ER further includes an assessment of filter languages, styles and online/offline symbol sharing for GeoPackages, OGC API - Features and OGC API - Tiles implementations for accuracy and completeness in applications that render vector tiles at local to regional scales." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -88961,35 +88889,35 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "16-088r1" + "@value": "19-084" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "OGC Soil Data Interoperability Experiment" + "@value": "OGC Vector Tiles Pilot 2: Vector Tiles Filtering Language Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/09-124r2", + "@id": "http://www.opengis.net/def/docs/19-081", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2010-06-30" + "@value": "2021-03-23" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Peter Taylor" + "@value": "Josh Lieberman" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -88999,27 +88927,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=39090" + "@id": "https://docs.ogc.org/per/19-081.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "09-124r2" + "@value": "MUDDI v1.1 (Model for Underground Data Definition and Integration) Engineering Report" }, { "@language": "en", - "@value": "Harmonising Standards for Water Observation Data - Discussion Paper " + "@value": "19-081" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document investigates the potential for harmonisation of water data standards, with the goal of developing an OGC compliant standard for the exchange of water observation data. The work will be based on OGC‘s Observations and Measurements abstract model [10-004r2] . The goal is to create an O&M profile for the water domain. Development of the OGC compliant O&M profile will begin by examining the content and structure of existing standards and suggesting future methodology for developing a harmonised model for observation data. This approach will make use of existing standards where possible.\r\n\r\nThe focus of this document is in-situ style observations (which are generally related to water quantity). Ex-situ measurements, such as those common to measuring water quality, will be addressed in future work.\r\n2 Normative" + "@value": "The Underground Infrastructure Concept Development Study (UICDS) Engineering Report [1] examined the present state of underground infrastructure information (UGII), costs and benefits of that state, as well as future opportunities for an improved state. That report describes a number of candidate models for UGII and recommends a number of follow-on activities, including development of a prototype UGII integration model to support subsequent UGII integration and exchange initiatives. A follow-up workshop and model development effort resulted in another engineering report describing an initial (1.0) version of the conceptual UGII integration model MUDDI (Model for Underground Data Definition and Interchange) [2]. The present updated report describes MUDDI version 1.1. The goal of MUDDI is to serve as the basis for integration of datasets from different models, at the levels of detail required to address application use cases described in [1]. MUDDI as described here is a conceptual model which will serve as the basis for one or more conformant and interchangeable logical and physical implementations such as GML (Geographic Markup Language) or SFS (Simple Features SQL). The current version 1.1 of MUDDI has been updated and refined from the initial version 1.0, but is still intended to serve as an input to the proposed OGC Underground Infrastructure Pilot as well as similar implementations and deployments in realistic application scenarios. The present model is also suitable as input to begin development of a formal conceptual model standard." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -89030,35 +88958,122 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "09-124r2" + "@value": "19-081" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Harmonising Standards for Water Observation Data - Discussion Paper" + "@value": "MUDDI v1.1 (Model for Underground Data Definition and Integration) Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/05-112", + "@id": "http://www.opengis.net/def/doc-type/notes/collection", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Collection" + ], + "http://www.w3.org/2000/01/rdf-schema#label": [ + { + "@value": "Documents of type Release Notes" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "Documents of type Release Notes" + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#member": [ + { + "@id": "http://www.opengis.net/def/docs/16-126r8" + }, + { + "@id": "http://www.opengis.net/def/docs/15-123r1" + }, + { + "@id": "http://www.opengis.net/def/docs/23-018r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-111" + }, + { + "@id": "http://www.opengis.net/def/docs/18-016r1" + }, + { + "@id": "http://www.opengis.net/def/docs/10-099r2" + }, + { + "@id": "http://www.opengis.net/def/docs/07-061" + }, + { + "@id": "http://www.opengis.net/def/docs/07-066r5" + }, + { + "@id": "http://www.opengis.net/def/docs/20-006" + }, + { + "@id": "http://www.opengis.net/def/docs/18-066r1" + }, + { + "@id": "http://www.opengis.net/def/docs/21-004" + }, + { + "@id": "http://www.opengis.net/def/docs/12-052" + }, + { + "@id": "http://www.opengis.net/def/docs/18-024r1" + }, + { + "@id": "http://www.opengis.net/def/docs/21-066r1" + }, + { + "@id": "http://www.opengis.net/def/docs/19-034r1" + }, + { + "@id": "http://www.opengis.net/def/docs/22-032r1" + }, + { + "@id": "http://www.opengis.net/def/docs/11-044" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@value": "Documents of type Release Notes" + } + ] + }, + { + "@id": "http://www.opengis.net/def/doc-type/d-orm", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/03-040" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/16-063", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2006-04-19" + "@value": "2017-03-08" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Milan Trninic" + "@value": "Stefano Cavazzi, Roger Brackin" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -89068,27 +89083,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=13285" + "@id": "https://docs.ogc.org/per/16-063.html" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "05-112" + "@value": "Testbed-12 Arctic Spatial Data Infrastructure Engineering Report" }, { "@language": "en", - "@value": "Symbology Management" + "@value": "16-063" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-dp" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This document describes Symbology Management System which is a system closely related to OpenGIS Style Management Services (SMS) (described in the document OGC 04-040). Having in mind their identical purpose, the system described in this document will also be referred to as SMS.\r\nThe SMS manages styles and symbols and defines their use in the process of producing maps from source GML data.\r\n" + "@value": "This engineering report captures use cases representative of the vision of the Arctic Spatial Data Infrastructure (ArcticSDI). The ArcticSDI is a cooperative initiative established between the eight National Mapping Agencies of Canada, Finland, Iceland, Norway, Russia, Sweden, USA and Denmark, with the aim of providing governments, policy makers, scientists, private enterprises and citizens in the Arctic with access to geographically related Arctic data, digital maps, and tools to facilitate monitoring and decision-making. The initiative will achieve this aim by providing a framework of spatial information resources, organizational structures, technologies of creation, processing and exchange of spatial data, that provides broad access and efficient use of spatial data for the Arctic. The engineering report provides a review of the policy drivers supporting the establishment of spatial data infrastructure (SDI) in each Arctic nation in order to improve understanding of the use cases, user groups and the impact an ArcticSDI may have on their day-to-day business. The engineering report presents lessons learnt along each of the components of SDI, for example, users, data, technology, standards, policy and others. A discussion is presented on how the technologies and standards already in use by the national mapping agencies relate to the technologies and standards implemented by the testbed, as well as how emerging geospatial standards could benefit the ArcticSDI." } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -89099,35 +89114,43 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "05-112" + "@value": "16-063" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "Symbology Management" + "@value": "Testbed-12 Arctic Spatial Data Infrastructure Engineering Report" } ] }, { - "@id": "http://www.opengis.net/def/docs/07-110r2", + "@id": "http://www.opengis.net/def/doc-type/dp-draft", + "http://www.w3.org/2004/02/skos/core#narrower": [ + { + "@id": "http://www.opengis.net/def/docs/06-021r1" + } + ] + }, + { + "@id": "http://www.opengis.net/def/docs/15-011r2", "@type": [ "http://www.w3.org/2004/02/skos/core#Concept" ], "http://purl.org/dc/terms/created": [ { "@type": "xsd:date", - "@value": "2008-03-11" + "@value": "2016-01-28" } ], "http://purl.org/dc/terms/creator": [ { - "@value": "Richard Martell" + "@value": "Panagiotis (Peter) A. Vretanos" } ], "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.opengis.net/def/metamodel/ogc-na/status": [ @@ -89137,27 +89160,27 @@ ], "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ { - "@id": "https://portal.ogc.org/files/?artifact_id=27092" + "@id": "https://portal.ogc.org/files/?artifact_id=66906" } ], "http://www.w3.org/2004/02/skos/core#altLabel": [ { "@language": "en", - "@value": "07-110r2" + "@value": "15-011r2" }, { "@language": "en", - "@value": "CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW" + "@value": "Testbed-11 Multiple WFS-T Interoperability" } ], "http://www.w3.org/2004/02/skos/core#broader": [ { - "@id": "http://www.opengis.net/def/doc-type/d-is" + "@id": "http://www.opengis.net/def/doc-type/per" } ], "http://www.w3.org/2004/02/skos/core#definition": [ { - "@value": "This profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0.2 specification; it qualifies as a 'Class 2' profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards." + "@value": "This document describes the work done in the OGC Testbest-11 to support multiple WFS-T instance interoperability by way of a transaction scenario involving the interaction between clients and multiple WFS-T servers as well as the interaction between the servers themselves, especially in the use case of enterprise-to-enterprise data synchronization.\r\nThe document presents an overview of the transaction scenario, the components used to implement the scenario in the OGC Testbed-11 demo and the new capabilities added to the WFS-T server to support the scenario.\r\n" } ], "http://www.w3.org/2004/02/skos/core#inScheme": [ @@ -89168,30 +89191,82 @@ "http://www.w3.org/2004/02/skos/core#notation": [ { "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", - "@value": "07-110r2" + "@value": "15-011r2" } ], "http://www.w3.org/2004/02/skos/core#prefLabel": [ { "@language": "en", - "@value": "CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW" + "@value": "OGC Testbed-11 Multiple WFS-T Interoperability" } ] }, { - "@id": "http://www.opengis.net/def/doc-type/sap", - "http://www.w3.org/2004/02/skos/core#narrower": [ + "@id": "http://www.opengis.net/def/docs/08-125r1", + "@type": [ + "http://www.w3.org/2004/02/skos/core#Concept" + ], + "http://purl.org/dc/terms/created": [ { - "@id": "http://www.opengis.net/def/docs/09-146r2" - }, + "@type": "xsd:date", + "@value": "2009-02-04" + } + ], + "http://purl.org/dc/terms/creator": [ { - "@id": "http://www.opengis.net/def/docs/07-045" - }, + "@value": "Tim Wilson, David Burggraf" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/doctype": [ { - "@id": "http://www.opengis.net/def/docs/01-009a" + "@id": "http://www.opengis.net/def/doc-type/bp" + } + ], + "http://www.opengis.net/def/metamodel/ogc-na/status": [ + { + "@id": "http://www.opengis.net/def/status/valid" + } + ], + "http://www.w3.org/2000/01/rdf-schema#seeAlso": [ + { + "@id": "https://portal.ogc.org/files/?artifact_id=30203" + } + ], + "http://www.w3.org/2004/02/skos/core#altLabel": [ + { + "@language": "en", + "@value": "08-125r1" }, { - "@id": "http://www.opengis.net/def/docs/06-080r4" + "@language": "en", + "@value": "KML Standard Development Best Practices" + } + ], + "http://www.w3.org/2004/02/skos/core#broader": [ + { + "@id": "http://www.opengis.net/def/doc-type/bp" + } + ], + "http://www.w3.org/2004/02/skos/core#definition": [ + { + "@value": "This OGC® Best Practices Document provides guidelines for developing the OGC KML standard in a manner that best serves and supports the KML application developer and user communities. It applies to the extension of KML by application developers and the subsequent enhancement of the KML standard by the OGC." + } + ], + "http://www.w3.org/2004/02/skos/core#inScheme": [ + { + "@id": "http://www.opengis.net/def/docs" + } + ], + "http://www.w3.org/2004/02/skos/core#notation": [ + { + "@type": "http://www.opengis.net/def/metamodel/ogc-na/doc_no", + "@value": "08-125r1" + } + ], + "http://www.w3.org/2004/02/skos/core#prefLabel": [ + { + "@language": "en", + "@value": "OGC® KML Standard Development Best Practices" } ] } diff --git a/definitions/docs/entailed/docs.rdf b/definitions/docs/entailed/docs.rdf index ed7e7dfb..532f7c52 100644 --- a/definitions/docs/entailed/docs.rdf +++ b/definitions/docs/entailed/docs.rdf @@ -8,23126 +8,23148 @@ xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns:skos="http://www.w3.org/2004/02/skos/core#" > - - 20-045 - - 20-045 - OGC Earth Observation Applications Pilot: CRIM Engineering Report + - OGC Earth Observation Applications Pilot: CRIM Engineering Report + 2020-07-08 - Tom Landry - This engineering report documents experiments conducted by CRIM in OGC’s Earth Observation Applications Pilot project, sponsored by the European Space Agency (ESA) and Natural Resources Canada (NRCan), with support from Telespazio VEGA UK. Remote sensing, machine learning and climate informatics applications were reused, adapted and matured in a common architecture. These applications were deployed in a number of interoperable data and processing platforms hosted in three Canadian provinces, in Europe and in the United States. + The OGC Vector Tiles Pilot 2: Tile Set Metadata Engineering Report (ER) describes a conceptual model for Tile Set Metadata that provides information about the intended usage of a Tile Set as well as the origin, security level, tiling scheme, layers and feature properties contained within. In this ER, a tile set is a series of tiles containing data and following a common tiling scheme. + +The metadata is intended to facilitate retrieval of tile sets and describes the major characteristics of tile sets without actually accessing the tiles nor the content contained in a tile. Such a process could be time consuming when there are a large number of tiles in a tile set. + +Additionally, this ER summarizes the discussions about Tile Set Metadata among the VTP2 participants, and draws up conclusions and recommendations for future work on the subject. + +Finally, this ER describes the Technology Integration Experiments (TIEs) performed to test the prototype implementation of the proposed Tile Set Metadata Model on API endpoints, client applications, and GeoPackages. + 19-082r1 + Vector Tiles Pilot 2: Tile Set Metadata Engineering Report + 19-082r1 + Sergio Taleisnik + OGC Vector Tiles Pilot 2: Tile Set Metadata Engineering Report - 2020-10-26 + - - OWS-7 Aviation - WXXM Assessment Engineering Report - 10-132 - OWS-7 Aviation - WXXM Assessment Engineering Report - Bruno Simmenauer - The document describes the results of using OGC Web Services for accessing and using WXXM data, notably within aviation scenarios involving rerouting procedures motivated by the sudden closure of airspace areas caused by the eruption of a volcano. The focus of this document will be to evaluate the ability to encode and serve associated operational data with WXXM 1.1.1. - 10-132 - 2010-08-18 - - + + + The OWS-2 Application Schema Development Discussion Paper describes the process for creating ISO 19109:2005 Application Schemas [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=39891] in UML. It also describes the process used during the OWS-2 Initiative [http://www.opengeospatial.org/projects/initiatives/ows-2] for creating GML [http://www.opengeospatial.org/standards/gml] Application Schemas from ISO 19109:2005 Application Schemas. + +See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml . + + 2005-04-13 + Clemens Portele + + + OWS-2 Application Schema Development + + + OWS-2 Application Schema Development + 04-100 + 04-100 + + + Stephen McCann, Roger Brackin, Gobe Hobona + 17-040 + 2018-01-08 + Testbed-13: DCAT/SRIM Engineering Report + 17-040 + + + OGC Testbed-13: DCAT/SRIM Engineering Report + + This engineering report captures the requirements, solutions, and implementation experiences of the Semantic Registry work package in Testbed-13. The engineering report describes the implementation of a RESTful Semantic Registry that supports the Semantic Registry Information Model (SRIM) which is based on the Data Catalog (DCAT) specification. A discussion of the applicability of the SRIM to the United States Geological Survey (USGS) and the National Geospatial Intelligence Agency (NGA) metadata is also presented, including an analysis of a set of controlled vocabularies from both organizations. Best Practice guidelines for the use of SRIM are also provided. The engineering report discusses the application of Shapes Constraint Language (SHACL) to aspects of Linked Data. Recognizing the benefits that asynchronous access has to offer web services, a description of the work undertaken by the testbed in implementing publish/subscribe functionality between a Semantic Registry and a Catalogue Service for the Web (CSW) is also presented. - - 2014-02-26 + + Location Services: Tracking Service Interface Standard + 06-024r4 + The OpenGIS Tracking Service Interface Standard supports a very simple functionality allowing a collection of movable objects to be tracked as they move and change orientation. The standard addresses the absolute minimum in functionality in order to address the need for a simple, robust, and easy-to-implement open standard for geospatial tracking. + 2008-09-08 + - OGC® Web Coverage Service WCS Interface Standard - Processing Extension - - Peter Baumann, Jinsongdi Yu - Web Coverage Service WCS Interface Standard - Processing Extension - 08-059r4 - - - The OGC Web Coverage Service (WCS)– Processing Extension defines an extension to the WCS Core [OGC 09-110], the ProcessCoverages request type, which allows clients to initi-ate server-side processing and filtering of coverages and to download the resulting coverage or value sets based on the query language defined in the Web Coverage Processing Service (WCPS) interface standard [OGC 08-068]. - 08-059r4 - + CS Smyth + OGC Location Services (OpenLS): Tracking Service Interface Standard + + + 06-024r4 + - - This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses. - - 03-088r6 - Arliss Whiteside + + + + 21-075 + OGC Disaster Pilot: User Readiness Guide + + + + 21-075 + OGC Disaster Pilot: User Readiness Guide + Improving the ability of key disaster decision makers and responders to discover, manage, access, transform, share, and exploit location-based and Earth Observation data will enhance decision making and, hopefully, save lives. The OGC Disaster Pilot 2021 has developed a number of prototype capabilities to demonstrate solutions for providing consistent, and reliable information to enable real-time actions to be taken using multiple technologies working together through pre-agreed standards. + +This User Guide describes how the solution works, how users can be part of it, and showcases what can be achieved if everyone is willing to work together and share data and knowledge to improve the information available to those responding to a disaster. + Andrew Lavender, Samantha Lavender + 2022-05-06 + + + OGC Moving Features Encoding Extension - JSON + 16-140r1 + + + 2017-06-28 - 03-088r6 - OGC Web Services Common - - OGC Web Services Common - 2004-01-19 - + + OGC Moving Features Encoding Extension - JSON + 16-140r1 + Kyoung-Sook KIM, Hirotaka OGAWA + + This document proposes a JavaScript Object Notation (JSON) encoding representation of movement of geographic features as an encoding extension of OGC Moving Features ([OGC 14-083r2] and [OGC 14-084r2]). A moving feature, typically a vehicle and pedestrian, can be expressed as a temporal geometry whose location continuously changes over time and contains dynamic non-spatial attributes whose values vary with time. This Best Practice describes how to share moving feature data based on JSON and GeoJSON (a JSON format for encoding geographic data structures). In addition, this document provides an example of RESTful approaches as a Feature Service Interface that has the potential for simplicity, scalability, and resilience with respect to exchange of moving feature data across the Web. - - - 2015-08-19 - Daniel Balog - Testbed 11 Data Broker Specifications Engineering Report - 15-028 - This document is a deliverable of the OGC Testbed 11 Interoperability initiative. The report’s contents cover the summary of the interoperability work regarding the Aviation Data Broker concept. This data broker concept enables the setup of cascading OGC Web Feature Server (WFS) servers to form a data source chain, in which one service is capable of providing information coming from one or more other services. The objectives of this document are to research the feasibility of this concept and to investigate a number of specific Data Broker responsibilities and use cases, such as provenance and lineage, conflation, caching, scalability and flexible management of data sources. - - OGC® Testbed 11 Data Broker Specifications Engineering Report - 15-028 - + + 16-007r3 + Volume 11: OGC CDB Core Standard Conceptual Model + + + Sara Saeedi + + + Volume 11: OGC CDB Core Standard Conceptual Model + 2017-02-23 + 16-007r3 + This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB 1.0 Standard. The objective of this document is to provide an abstract core conceptual model for a CDB data store (repository). The model is represented using UML (unified modeling language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering a UML model and documentation from the OGC CDB standard as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113]. + + + + Genong (Eugene) Yu, Liping Di + 2014-07-16 + + Testbed 10 Cross Community Interoperability (CCI) Hydro Model Interoperability Engineering Report + 14-048 + OGC® Testbed 10 Cross Community Interoperability (CCI) Hydro Model Interoperability Engineering Report + 14-048 + + + This OGC® document gives guidelines for enabling interoperability among different hydro data models and services. The demonstration specifically gives out best practices for supporting interoperability among the National Hydrographic Network (NHN) of Canada, the National Hydrographic Dataset Plus (NHD+) of United States, and the OGC HY_Features model developed and proposed by the World Meteorological Organization (WMO). The discussed version of OGC HY_Features was adopted as the mediation bridge model to exchange information among heterogeneous hydrological models. + - - 11-108 - OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report) - This document describes the usability of OGC services and encodings to implement the -OWS-8 observation fusion and tracking thread in an abstract way. The real deployment -and an actual perspective on the engineering and technology viewpoint can be found in -OWS-8 engineering report OGC 11-134, ‘OWS-8 Tracking: Moving Target Indicator -Process, Workflows and Implementation Results’. In addition, it describes an XMLSchema -based implementation of the UML information models defined in OWS-8 -engineering report “Information Model for Moving Target Indicators and Moving Object -Bookmarks” (OGC 11-113). -The report is also based on the results of the VMTI/GMTI and STANAG 4676 realization -in the OGC concept of operations study; performed as part of OWS 8 and the EC cofunded -research project Emergency Support System - ESS” (contract number 217951). - Ingo Simonis + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Generated by the OGC Definitions Server to support integration of the elements of this ConceptScheme into bigger collections. ogc_skos_profile_entailements.ttl + + Collection hierarchy for this ConceptScheme + + Concepts in OGC Documents + + + + Topic 9 - Accuracy + 99-109r1 + 1999-03-30 + + + + + Cliff Kottman, Arliss Whiteside + 99-109r1 + Topic 9 - Accuracy + Topic 9 has been combined into AS Topic 11 + + + 08-139r3 + + 2011-01-17 + George Demmy, Carl Reed + PDF Geo-registration Encoding Best Practice Version 2.2 + 08-139r3 - - 11-108 - - - OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report) - 2012-05-15 + + The intended audience of this document is a developer of software for creating and consuming geo=registered PDF documents that conform to PDF geo-registration 2.2. It specifies how to create the necessary PDF objects that identify a region of the PDF page as a map and describe the map’s coordinate systems. Map creation and rendering to a PDF page are not addressed. The underlying PDF file format is not addressed. The file format is specified in PDF Reference[1] . + + + PDF Geo-registration Encoding Best Practice Version 2.2 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 09-032 - The document describes an abstract event architecture for service oriented architectures. Furthermore various techniques for implementing an event architecture and working with events are discussed. - 2009-07-29 - Thomas Everding, Johannes Echterhoff - OWS-6 SWE Event Architecture Engineering Report - OWS-6 SWE Event Architecture Engineering Report - 09-032 + + Summary of the OGC Web Services, Phase 8 (OWS-8) Interoperability Testbed + 11-139r2 + Summary of the OGC Web Services, Phase 8 (OWS-8) Interoperability Testbed + 11-139r2 + The OGC Web Services, Phase 8 (OWS-8) Testbed was an initiative of OGC’s Interoperability Program to +collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. The majority of work for +OWS-8 was conducted from March to September 2011. + + 2011-12-19 + + David Arctur - - - OGC Web Coverage Service Interface Standard – Transaction Extension - 13-057r1 - Web Coverage Service Interface Standard – Transaction Extension - This OGC Web Coverage Service (WCS) – Transaction Extension (in short: WCS Transaction) defines an extension to the WCS Core [OGC 09-110] for updating coverage offer­ings on a server. - -This WCS Transaction standard defines three requests: + + 18-010r7 + Geographic information — Well-known text representation of coordinate reference systems + Roger Lott + 2019-08-13 + 18-010r7 + This Standard defines the structure and content of well-known text strings describing coordinate reference systems (CRSs) and coordinate operations between coordinate reference systems. It does not prescribe how implementations should read or write these strings. -InsertCoverage for adding a coverage provided as parameter to the WCS server’s cov­erage offering. After successful completion of the insert request, this coverage will be accessible for all WCS operations. -DeleteCoverage for entirely removing a coverage. The coverage is identified by its coverage id passed in the request, from the WCS server’s coverage offering. After successful completion of this request, this coverage will not be accessible through any WCS operation. However, subsequently a new coverage may be created using the same identifier; such a coverage will bear no relation to the one previously deleted. -UpdateCoverage for modifying parts of a coverage existing in a WCS server’s coverage offering. The coverage is identified by its coverage id passed in the request. As per the OGC Coverage Implementation Schema [OGC 09-146r2], all updates must maintain internal consistency of the coverage. -All requests defined in this Transaction Extension adhere to the ACID[1] (atomicity, consistency, isolation, durability) concepts of database transactions. +This Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2019. It extends the WKT in OGC document 12-063r5 (ISO 19162) which was based on ISO 19111:2007 and ISO 19111-2:2009. That version consolidated several disparate versions of earlier WKT (so-called WKT1) and added the description of coordinate operations. -The extension name, Transaction, traces back to the database concept of transactions, which has been adopted here. - +This jointly developed draft has been submitted by ISO TC211 for circulation as a Draft International Standard (DIS). This version incorporates comments made during the ISO TC211 New Work Item Proposal acceptance ballot. + - - Peter Baumann + + - - 13-057r1 - - 2016-11-17 + + Geographic information — Well-known text representation of coordinate reference systems - - - - - - - - - - - - - - - - - - - - - - - Documents of type OGC Abstract Specification - Documents of type OGC Abstract Specification - Documents of type OGC Abstract Specification - + + + - - - - - This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC. The formal Namespace identifier (NID) is ogc. - - Carl Reed - 07-107r3 - A URN namespace for the Open Geospatial Consortium (OGC) - 07-107r3 - - A URN namespace for the Open Geospatial Consortium (OGC) - - 2008-05-02 - - - 2019-10-06 - - Two Dimensional Tile Matrix Set - 17-083r2 - + 17-047r1 + 17-047r1 + OpenSearch-EO GeoJSON(-LD) Response Encoding Standard + OGC OpenSearch-EO GeoJSON(-LD) Response Encoding Standard - - Joan Masó - 17-083r2 - OGC Two Dimensional Tile Matrix Set - The OGC Tile Matrix Set standard defines the rules and requirements for a tile matrix set as a way to index space based on a set of regular grids defining a domain (tile matrix) for a limited list of scales in a Coordinate Reference System (CRS) as defined in [OGC 08-015r2] Abstract Specification Topic 2: Spatial Referencing by Coordinates. Each tile matrix is divided into regular tiles. In a tile matrix set, a tile can be univocally identified by a tile column a tile row and a tile matrix identifier. This document presents a data structure defining the properties of the tile matrix set in both UML diagrams and in tabular form. This document also presents a data structure to define a subset of a tile matrix set called tile matrix set limits. XML and JSON encodings are suggested both for tile matrix sets and tile matrix set limits. Finally, the document offers practical examples of tile matrix sets both for common global projections and for specific regions. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Documents of type OGC Implementation Specification - Documents of type OGC Implementation Specification - Documents of type OGC Implementation Specification - - - James Tomkins, Dominic Lowe, Paul Hershberg - TimeseriesML 1.3 defines an XML encoding that implements the OGC Timeseries -Profile of Observations and Measurements, with the intent of allowing the exchange of -such data sets across information systems. Through the use of existing OGC standards, it -aims at being an interoperable exchange format that may be re-used to address a range of -data exchange requirements. - OGC TimeseriesML 1.3 – XML Encoding of the Timeseries Profile of Observations and Measurements + The OpenSearch specification [NR3] is defined as a binding of the Abstract Protocol Definition (APD) for the searchRetrieve operation, one of a set of documents [NR4] for the OASIS Search Web Services (SWS) initiative [OR1]. The OpenSearch Description Document (OSDD) allows clients to retrieve service metadata from an OpenSearch implementation. The OSDD format allows the use of extensions that allow search engines to inform clients about specific and contextual query parameters and response formats. The OpenSearch extension for Earth Observation (EO) collections and products search is defined in [OR20]. The mandatory response format is based on Atom 1.0/XML [OR14]. + +JavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. GeoJSON [NR2] is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. This OGC standard describes a GeoJSON [NR2] and JSON-LD [NR15] encoding for OpenSearch Response documents. + +The GeoJSON encoding defined in this document is defined as a compaction[1] through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF/XML [OR11] and RDF Turtle [OR12]. + +Although this document makes no assumptions as to the “service” interfaces through which the Search Response is obtained and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful architecture. The documented approach is mainly intended to be applied in combination with the following technologies: + +OGC OpenSearch extensions [OR19], [OR20], [NR3]. +GeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features. + +JSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR24] which allows validation of instances against these schemas. + 2020-04-27 - 15-042r6 - OGC TimeseriesML 1.3 – XML Encoding of the Timeseries Profile of Observations and Measurements - - - - - - 15-042r6 - 2023-06-21 - - - Basic Services Model - 01-022r1 - 01-022r1 - - + + + + + + + + + + Documents of type Implementation Standard Extension - 2001-05-05 - The Basic Services Model is an implementation of the ISO TC211 services architecture as found in ISO 19119 Geographic Information - Jeff de La Beaujardiere - Basic Services Model - - - - - - - - This International Standard specifies the behaviour of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored parameterized query expressions. -Discovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers. -Query operations allow features or values of feature properties to be retrieved from the underlying data store based upon constraints, defined by the client, on feature properties. -Locking operations allow exclusive access to features for the purpose of modifying or deleting features. -Transaction operations allow features to be created, changed, replaced and deleted from the underlying data store. -Stored query operations allow clients to create, drop, list and described parameterized query expressions that are stored by the server and can be repeatedly invoked using different parameter values. - - Web Feature Service 2.0 Interface Standard (also ISO 19142) - 09-025r1 - OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142) - 2010-11-02 - 09-025r1 - - Panagiotis (Peter) A. Vretanos - - - - WaterML2.0: part 2 - Ratings, Gaugings and Sections - 15-018r2 - Peter Taylor - - - - - - - 15-018r2 - 2016-02-03 - OGC WaterML2.0: part 2 - Ratings, Gaugings and Sections - This standard defines an information model and XML encoding for exchanging the -following three hydrological information resources: -1. Conversion tables, or conversion curves, that are used for the conversion of -related hydrological phenomenon. -2. Gauging observations – the observations performed to develop conversion table -relationships. -3. Cross sections - survey observations made of the geometric structure of features, -such as river channels, storages etc. -Metadata and vocabularies are defined that together provide a means for parties to -exchange these concepts using common semantics. -This standard is the second part of the WaterML2.0 suite of standards, building on part 1 -that addresses the exchange of time series. - - - - 2011-11-23 - - - Daniel Tagesson - OWS-8 Engineering Report - Guidelines for International Civil Aviation Organization (ICAO) portrayal using SLD/SE - This OGC® document gives guidelines to portrayal of AIXM according to ICAO aviation symbology using SLD/SE. - - OWS-8 Engineering Report - Guidelines for International Civil Aviation Organization (ICAO) portrayal using SLD/SE - 11-089r1 - 11-089r1 - - - - - - - 17-030r1 - LAS Specification 1.4 OGC Community Standard - 17-030r1 - - The LAS file is intended to contain LIDAR (or other) point cloud data records. The data will -generally be put into this format from software (e.g. provided by LIDAR hardware vendors) which -combines GPS, IMU, and laser pulse range data to produce X, Y, and Z point data. The intention -of the data format is to provide an open format that allows different LIDAR hardware and software -tools to output data in a common format. -This document reflects the fourth revision of the LAS format specification since its initial version -1.0 release. - - - - - 2018-03-01 - ASPRS - LAS Specification 1.4 OGC Community Standard - - - The Environmental Data Retrieval (EDR) Application Programming Interface (API) provides a family of lightweight query interfaces to access spatio-temporal data resources by requesting data at a Position, within an Area, along a Trajectory or through a Corridor. A spatio-temporal data resource is a collection of spatio-temporal data that can be sampled using the EDR query pattern geometries. These patterns are described in the section describing the Core Requirements Class. - -The goals of the EDR API are to make it easier to access a wide range of data through a uniform, well-defined simple Web interface, and to achieve data reduction to just the data needed by the user or client while hiding much of the data storage complexity. A major use case for the EDR API is to retrieve small subsets from large collections of environmental data, such as weather forecasts, though many other types of data can be accessed. The important aspect is that the data can be unambiguously specified by spatio-temporal coordinates. - -The EDR API query patterns, such as Position, Area, Cube, Trajectory or Corridor, can be thought of as discrete sampling geometries, conceptually consistent with the feature of interest in the Sensor Observation Service (SOS) standard. A typical EDR data resource is a multidimensional dataset that could be accessed via an implementation of the Web Coverage Service (WCS) standard. In contrast to SOS and WCS, the EDR API implements the technical baseline of the OGC API family of standards and aims to provide a single set of simple-to-use query patterns. Use cases for EDR range from real or virtual time-series observation retrievals, to sub-setting 4-dimensional data cubes along user-supplied sampling geometries. These query patterns do not attempt to satisfy the full scope of either SOS or WCS, but provide useful building blocks to allow the composition of APIs that satisfy a wide range of geospatial data use cases. By defining a small set of query patterns (and no requirement to implement all of them), the EDR API should help to simplify the design of systems (as they can be performance tuned for the supported queries) making it easier to build robust and scalable infrastructure. - -With the OGC API family of standards, the OGC community has extended its suite of standards to include Resource Oriented Architectures and Web Application Programming Interfaces (APIs). These standards are based on a shared foundation, specified in OGC API-Common, which defines the resources and access paths that are supported by all OGC APIs. The resources are listed in Table 1. This document extends that foundation to define the Environmental Data Retrieval API. - Mark Burgoyne, David Blodgett, Charles Heazel, Chris Little - 19-086r5 - 2022-08-05 - - - - 19-086r5 - OGC API - Environmental Data Retrieval Standard - OGC API - Environmental Data Retrieval Standard - - - - - - 16-007r4 - Volume 11: OGC CDB Core Standard Conceptual Model - 16-007r4 - - - 2018-12-19 - - - - This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB Standard. The objective of this document is to provide an abstract core conceptual model for a CDB data store (repository). The model is represented using UML (unified modeling language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering the UML diagrams and documentation from the original CDB submission as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113r5]. - -NOTE: The simulation community uses the term “synthetic environment data” to mean all the digital data stored in some database or structured data store that is required for use by simulation clients. From the geospatial community perspective, these data are essentially the same as GIS data but with, in some cases, special attributes, such as radar reflectivity. - - Sara Saeedi - - Volume 11: OGC CDB Core Standard Conceptual Model - - - 16-009r3 - Volume 6: OGC CDB Rules for Encoding Data using OpenFlight - - Carl Reed - - - - This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of that document for a general overview. - Volume 6: OGC CDB Rules for Encoding Data using OpenFlight - 2017-02-23 - - - 16-009r3 - - - 2023-03-13 - - - - OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification Version 1.1 Release Notes - - This document provides the set of revision notes for OGC I3S Community Standard [OGC 17-014r5] and does not modify that standard. -This document provides the details of edits, deficiency corrections, and enhancements of the above-referenced standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility. - - 19-034r1 - - 19-034r1 - OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification Version 1.1 Release Notes - - Carl Reed, Tamrat Belayneh - - - 2010-08-18 - - - 10-127r1 - - - 10-127r1 - OWS-7 Engineering Report - Aviation Portrayal - - Roger Brackin - OWS-7 Engineering Report - Aviation Portrayal - - This document describes the requirements, design, technical implementation and technology trialed for the Feature Portrayal service chain used in OWS-7. This includes the interfaces to the OWS Data Services deployed, the feature portrayal servers, the interfaces to clients and the registry information model and interface. - - - Cataloguing Earth Observation Products for ebXML Registry Information Model 3.0 based Catalogues - 10-189r2 - 2012-06-12 - - - 10-189r2 - Cataloguing Earth Observation Products for ebXML Registry Information Model 3.0 based Catalogues - - Frédéric Houbie; Fabian Skivee - - - - This OGC® document specifies the Earth Observation Products Extension Package for ebXML Registry Information Model 3.0, based on the [OGC 10-157r1] Earth Observation Metadata profile of Observations and Measurements. -It enables CSW-ebRIM catalogues to handle a variety of metadata pertaining to earth observation p/roducts as defined in [OGC 10-157r1]. -This proposed application profile document describes model and encodings required to discover, search and present metadata from catalogues of Earth Observation products. The profile presents a minimum specification for catalogue interoperability within the EO domain, with extensions for specific classes of metadata. - - - - - - OGC Web Service Common Implementation Specification - - Arliss Whiteside, Jim Greenwood - This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Standards. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Standard must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses. - Web Service Common Implementation Specification - 06-121r9 - 06-121r9 - 2010-04-07 - - - - - - 09-050r1 - - Hans Schoebach - - - 2009-07-27 - OGC OWS-6-AIM Engineering Report - - 09-050r1 - OGC OWS-6-AIM Engineering Report - This report establishes a baseline for the technical architecture, its alternatives and issues for implementing the use cases as specified in the OWS-6 AIM thread RFQ including the temporal WFS supporting the temporal FE 2.0 operators, the Event Service Notification architecture and the client EFBs. - - - - - This document describes a conceptual model, logical model, and GML/XML encoding rules for the exchange of groundwater data. In addition, this document provides GML/XML encoding examples for guidance. - 15-082 - GroundWaterML 2 – GW2IE FINAL REPORT - OGC GroundWaterML 2 – GW2IE FINAL REPORT - 2016-04-27 - 15-082 - - - - - - - Boyan Brodaric - - - - 2020-10-22 - - OGC API - Tiles - 3D (GeoVolumes) Engineering Report - 20-030 - - - Timothy Miller and Gil Trenum - - This Engineering Report documents the draft specification for a three-dimensional (3D) geodata Application Programming Interface (API) that organizes access to a variety of 2D / 3D datasets and their distributions according to a nested hierarchy of 3D geospatial volumes (GeoVolumes). The GeoVolumes (initially Tiles-3D / 3D Container) API specification is consistent with OGC API - Common and supports both link-follow and bbox query methods of access to resources of interest. - OGC API - Tiles - 3D (GeoVolumes) Engineering Report - - 20-030 + + Documents of type Implementation Standard Extension + Documents of type Implementation Standard Extension - - 05-014 - - Image CRSs for IH4DS - 05-014 - - Image CRSs for IH4DS - 2005-01-31 - - - Arliss Whiteside - - This Discussion Paper specifies image coordinate reference system (CRS) definitions designed for possible use by WCTS and WCS servers and clients, initially in the IH4DS thread of the OWS 2 interoperability initiative. This report specifies image CRS definitions suitable for both ungeorectified and georectified images, where an ungeorectified image can be georeferenced or not. - - - - - - Sensor Alert Service - - - A service providing active (push-based) access to sensor data. - 06-028 - Sensor Alert Service - 06-028 - 2006-04-05 - Ingo Simonis - - - - - 06-131r4 - - - OGC® Catalogue Services Specification 2.0 Extension Package for ebRIM (ISO/TS 15000-3) Application Profile: Earth Observation - 06-131r4 - - - This OGC® document specifies the Earth Observation Products Extension Package for ebRIM (ISO/TS 15000-3) Application Profile of CSW 2.0, based on the [OGC 06-080r3] OGC® GML Application Schema for EO Products. - Renato Primavera - EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 - - 2008-07-08 - - - - - OpenGIS Filter Encoding Implementation Specification - - - - 04-095 - Filter Encoding Implementation Specification - - Peter Vretanos - The OpenGIS® Filter Encoding Standard (FES) defines an XML encoding for filter expressions. A filter expression logically combines constraints on the -properties of a feature in order to identify a particular subset of features to be operated upon. For example, a subset of features might be identified to render them in a particular color or convert them into a user-specified format. Constraints can be specified on values of spatial, temporal and scalar properties. An example of a filter is: Find all the properties in Omstead County owned by Peter Vretanos. - -This standard is used by a number of OGC Web Services, including the Web Feature Service [http://www.opengeospatial.org/standards/wfs], the Catalogue Service [http://www.opengeospatial.org/standards/cat] and the Styled Layer Descriptor Standard [http://www.opengeospatial.org/standards/sld]. - - 2005-05-03 - 04-095 - - - - - - 2009-10-13 - CF-netCDF Encoding Specification - 09-122 - 09-122 - - - - CF-netCDF Encoding Specification - Ben Domenico - - NetCDF (network Common Data Form) is a data model for array-oriented scientific data, a freely distributed collection of access libraries implementing support for that data model, and a machine-independent format. Together, the interfaces, libraries, and format support the creation, access, and sharing of scientific data. - - - Carl Reed - 16-010r3 - - - Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2 - 16-010r3 - 2017-02-23 - - - - Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2 - This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store. -Please note that the term “lineal” has been replaced with the term “line” or “linear” throughout this document -Please note that the term “areal” has been replaced with the term “polygon” throughout this document. - - - - - - Roel Nicolai - - Topic 2 - Spatial Referencing by Coordinates - 03-073r1 - 03-073r1 - - - Topic 2 - Spatial Referencing by Coordinates - - - 2003-10-16 - Describes modelling requirements for spatial referencing by coordinates. - - - The GeoPackage Standards Working Group (SWG) presents a discussion of symbology encapsulation for conveying presentation information for vector features contained within in a GeoPackage. - Randolph Gladish - - Implications for an OGC GeoPackage Symbology Encoding Standard - 15-122r1 - 15-122r1 - - - - Implications for an OGC GeoPackage Symbology Encoding Standard - - 2016-04-26 - - - - SensorML: Model and XML Encoding Standard - 12-000r2 - Mike Botts, Alexandre Robin, Eric Hirschorn - OGC SensorML: Model and XML Encoding Standard - 12-000r2 - - - - The primary focus of the Sensor Model Language (SensorML) is to provide a robust and semantically-tied means of defining processes and processing components associated with the measurement and post-measurement transformation of observations. This includes sensors and actuators as well as computational processes applied pre- and post-measurement. - -The main objective is to enable interoperability, first at the syntactic level and later at the semantic level (by using ontologies and semantic mediation), so that sensors and processes can be better understood by machines, utilized automatically in complex workflows, and easily shared between intelligent sensor web nodes. - -This standard is one of several implementation standards produced under OGC’s Sensor Web Enablement (SWE) activity. This standard is a revision of content that was previously integrated in the SensorML version 1.0 standard (OGC 07-000). - - - 2020-08-10 - - - - Craig A. Lee - 20-027 - OGC Testbed-16: Federated Security - 20-027 - - - - - - - 2021-01-06 - OGC Testbed-16: Federated Security - This OGC Testbed 16 Engineering Report (ER) examines all aspects of security and trust in federated computing environments as defined in the NIST Cloud Federation Reference Architecture [1]. The security and trust requirements are identified. Then possible approaches for achieving security and trust are examined. These approaches range from traditional methods for securing just the basic communications among federated entities to the use of emerging security technologies including federated roots of trust, trust frameworks, blockchain, data-centric security, and zero trust architectures. - - - - - - - - - - - - - - - - - Documents of type Candidate Specification - Documents of type Candidate Specification - Documents of type Candidate Specification - - - - - 2001-03-30 - Location Organizer Folder - 01-037 - *RETIRED* The Location Organizer Folder (LOF) is a GML document that provides a structure for organizing the information related to a particular event or events of interest. - Ron Lake - 01-037 - - - - - - - Location Organizer Folder - - - The DGIWG Portrayal Technical Panel (DPTP) has been investigating how to standardize the portrayal of military context symbology within Web Services. The team sought to use version 1.1.0 of OGC Style Layer Descriptor standard and version 1.1.0 of Symbology Encoding (SLD and SE) standard to achieve this. -The team sought to apply military-specific symbology to military-specific topographic feature vector datasets within a number of software products. -The testing and experimentation highlighted a number of deficiencies in the SLD and SE standards which result in a barrier to interoperability. The ideal situation would be to have SLD and SE descriptors interoperable between all software products that implement the standard. This was found not to be the current situation. -This position paper describes the findings and outlines recommendations for a revised future version of the SLD and SE standards that resolves these issues. - - 17-059 - - 17-059 - Technical report from the DGIWG Portrayal Technical Panel testing of SLD (1.1.0) for OGC - - Technical report from the DGIWG Portrayal Technical Panel testing of SLD (1.1.0) for OGC - - - Lars Schylberg, Lubos Belka - - - 2017-10-30 - - - - 09-149r1 - Web Coverage Service 2.0 Interface Standard - XML/SOAP Protocol Binding Extension - - Peter Baumann - - 2010-10-27 - This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using SOAP with XML encoding. - - OGC® Web Coverage Service 2.0 Interface Standard - XML/SOAP Protocol Binding Extension - - - 09-149r1 - - - Carl Reed - - - - 2021-02-26 - 16-011r5 - Volume 8: CDB Spatial and Coordinate Reference Systems Guidance - - Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames. - - - 16-011r5 - - Volume 8: CDB Spatial and Coordinate Reference Systems Guidance - - - - OGC Testbed-16: Data Centric Security Engineering Report - 20-021r2 - - - Aleksandar Balaban - The OGC Testbed-16 Data Centric Security Engineering Report (ER) continues the evaluation of a data-centric security (DCS) approach in a geospatial environment. In order to fully explore the potential of the DCS concept, this ER first specifies two advanced use case scenarios: Data Streaming and Offline Authorization for querying and consuming protected geospatial content. The ER then specifies the communication with a new architectural component called the Key Management Server (KMS) via an Application Programming Interface (API) created for this Testbed. The API was invoked to register keys used to encrypt data-centric protected content. Then clients called the same API to obtain those keys to perform the data verification/decryption. - - - - - 2021-02-26 - - 20-021r2 - - OGC Testbed-16: Data Centric Security Engineering Report - - - - Corrigendum 2 for OGC Web Services Common Specification v 1.1.0 - Exception Report - This document defines the corrigendum change notes for <OGC Web services Common Specification v1.1.0. This document was approved by the OGC membership on December 2010 . As a result of the Corrigendum process, there were edits and enhancements made to this standard to correct typographic errors, schema errors, or some deficiency that prevented proper use of this standard. This document provides the details of those edits, deficiency corrections, and other corrects. It also documents those items that have been deprecated. - - 11-158 - Corrigendum 2 for OGC Web Services Common Specification v 1.1.0 - Exception Report - - - - - 11-158 - Jim Greenwood - 2011-10-18 - - - Standardized Information Models to Optimize Exchange, Reusability and Comparability of Citizen Science Data (SWE4CS) - This discussion paper describes a data model for the standardized exchange of citizen science sampling data. To do that it applies the Sensor Web Enablement (SWE) to Citizen Science (SWE4CS). In particular, exposes how Observations and Measurements (O&M) can be used to model the data of the Citizen Science project, in a way that can be retrieved using Sensor Observing System (SOS).This discussion paper is a result of the research project Citizen Observatory Web (COBWEB). COBWEB is supported by the European Commission through grant agreement 308513 - - Standardized Information Models to Optimize Exchange, Reusability and Comparability of Citizen Science Data (SWE4CS) - 16-129 - 2017-03-31 - - Ingo Simonis, Rob Atkinson - - - - 16-129 - - - - 20-072r5 - - - Hugo Ledoux, Balázs Dukai - - - - 20-072r5 - CityJSON Community Standard 2.0 - CityJSON is a data exchange format for digital 3D models of cities and landscapes. It aims at being easy-to-use (for reading, processing, and creating datasets), and it was designed with programmers in mind, so that tools and APIs supporting it can be quickly built. The JSON-based encoding of CityJSON implements a subset of the OGC CityGML data model (version 3.0) and includes a JSON-specific extension mechanism. Using JSON instead of GML allows us to compress files by a factor 6 and at the same time to simplify greatly the structure of the files. - CityJSON Community Standard 2.0 - 2023-10-20 - - - - 06-022r1 - Temporal Standard Recommendations - 06-022r1 - James Resler - 2006-04-21 - - This document summarizes recommendations for extending geospatial standards with regard to time-varying information. These proposals are the result of the National Technology Alliance program called Temporal Evaluation and Assessment (TEA). - - Temporal Standard Recommendations - - - - - - - - - 2015-11-19 - 15-067 - 15-067 - Testbed-11 Multi-dimensional GeoPackage Supporting Terrain and Routes Engineering Report - OGC® Testbed-11 Multi-dimensional GeoPackage Supporting Terrain and Routes Engineering Report - - Gobe Hobona;Roger Brackin - Routing is one of the most widely used functions of mobile applications. Routing often requires consideration of a variety of factors in order to provide reasonable estimations of journey time and the cost of travel. Another widely used function of mobile applications is the visualization of characteristics of terrain such as slope or viewsheds. The goal of this engineering report is to describe the work carried out in the OGC Testbed-11 for multidimensional terrain and routing support on SQLite databases that conform to the OGC GeoPackage standard. This OGC® Engineering Report (ER) describes an approach for the storage of routing and multidimensional terrain data in such databases. The ER also presents the results and lessons learnt from the experimentation conducted by the testbed. - - - - - - - - Testbed-12 GeoPackage Routing and Symbology Engineering Report - Jeff Yutzler - Testbed-12 GeoPackage Routing and Symbology Engineering Report - 16-029r1 - - 2017-05-12 - - - This OGC Engineering Report (ER) describes the results of experiments in OGC Testbed 12 designed to potentially enhance capabilities for symbology and routing [1] as extensions to the OGC GeoPackage standard. These experiments focused on 1.) methods for providing mounted and/or dismounted (off-road) routing within GeoPackage and 2.) mechanisms for providing user-defined map symbology for features in a GeoPackage structured data store. This ER documents the different approaches considered, design decisions and rationales, limitations, and issues encountered during prototype implementation. - - - - 16-029r1 - - - 2015-05-01 - - This Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2007 and ISO 19111-2:2009. It extends the earlier WKT to allow for the description of coordinate operations. This International Standard defines the structure and content of well-known text strings. It does not prescribe how implementations should read or write these strings. -The jointly developed draft has also been submitted by ISO TC211 for publication as an International Standard document. The version incorporates comments made during both the OGC Public Comment Period as well as the ISO ballot for DIS (ISO TC211 document N3750). - - Well known text representation of coordinate reference systems - 12-063r5 - Roger Lott - 12-063r5 - - - - - - Geographic information — Well known text representation of coordinate reference systems - - - - OWS-7 Dynamic Sensor Notification Engineering Report - - - - - OWS-7 Dynamic Sensor Notification Engineering Report - 10-061r1 - 10-061r1 - - This document is applicable to scenarios where moving sensors need to be tracked and their entry into an area of interest needs to be detected. - -The document presents a detailed discussion of different approaches for encoding tracked object position. - -Two approaches for implementing dynamic sensor tracking and notification are described, one based on the Sensor Alert Service specification and the other based on the Sensor Event Service specification. - -An overview of standards and specifications relevant for and related to dynamic sensor tracking and notification is provided. - - Johannes Echterhoff, Ingo Simonis - 2010-06-30 - - - - 12-128r11 - - - 2015-04-20 - - OGC® GeoPackage Encoding Standard – With Corrigendum - GeoPackage Encoding Standard – With Corrigendum - 12-128r11 - This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a “native” storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. - - Paul daisey - - - - - - - 2021-02-15 - - This OGC Discussion Paper presents a proposal that recommends the development of Open Geospatial Consortium (OGC) standards that define a framework for location-based service metrics that inform the spatial, spectral, and temporal errors associated with various data sources. This paper discusses current industry practices on spatial errors, spectral errors, and error propagation. The paper also presents a proposed framework and a recommended study effort. - Standardizing a Framework for Spatial and Spectral Error Propagation - - 20-088 - Standardizing a Framework for Spatial and Spectral Error Propagation - K. Navulur, M.C. Abrams - - 20-088 - - - Binary Extensible Markup Language (BXML) Encoding Specification - - - Craig Bruce - - Binary Extensible Markup Language (BXML) Encoding Specification - 03-002r9 - 03-002r9 - - 2006-01-18 - - - This OGC Best Practices document specifies a binary encoding format for the efficient representation of XML data, especially scientific data that is characterized by arrays of numbers. This encoding format is applicable to any application that uses XML format. - - - - - Greg Reynolds - - 2005-05-04 - 03-064r10 - Geographic Objects Implementation Specification *RETIRED* - 03-064r10 - *THIS STANDARD HAS BEEN RETIRED* - -The OpenGIS® Geographic Objects Interface Standard (GOS) provides an open set of common, lightweight, language-independent abstractions for describing, managing, rendering, and manipulating geometric and geographic objects within an application programming environment. It provides both an abstract object standard (in UML) and a programming-language-specific profile (in Java). The language-specific bindings serve as an open Application Program Interface (API). - OpenGIS Geographic Objects Implementation Specification *RETIRED* - - - - - - 10-130 - OWS-7 Aviation - FUSE Deployment Engineering Report - This document describes the integration results of deploying OGC Web Services on the FAA chosen Enterprise Service Bus (ESB) - FUSE. Snowflake Software were commissioned to evaluate the impacts of the FAA SWIM security requirements for both secure messaging and user authentication and gain an understanding of the requirements for deploying OGC web services into the Apache FUSE Enterprise Service Bus (ESB). - 10-130 - Debbie Wilson - - 2010-08-18 - OWS-7 Aviation - FUSE Deployment Engineering Report - - - - - - - - OGC Earth Observation Applications Pilot: Spacebel Engineering Report - Christophe Noël - This Engineering Report (ER) describes the achievements of Spacebel as a Platform Provider in the OGC Earth Observation Applications (EO Apps) Pilot and the lessons learned from the project. - - 20-034 - OGC Earth Observation Applications Pilot: Spacebel Engineering Report - 20-034 - - - - - - 2020-10-22 - - - - Summary of the OGC Web Services, Phase 5 (OWS-5) Interoperability Testbed - Jessica Cook, Raj Singh - 08-073r2 - Summary of the OGC Web Services, Phase 5 (OWS-5) Interoperability Testbed - 08-073r2 - - The OGC Web Services, Phase 5 (OWS-5) Testbed was an initiative of the OGC Interoperability Program (IP). The primary focus of an IP activity is to collaboratively extend and demonstrate OGC‘s baseline for geospatial interoperability. - - - - - 2008-09-12 - - - 10-140r1 - OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile - - - - - - - The OGC Web Coverage Service (WCS) Application Profile – Earth Observation (EO-WCS), defines a profile of WCS 2.0 [OGC 09-110r4] for use on Earth Observation data. - 10-140r1 - Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile - Peter Baumann, Stephan Meissl, Jinsongdi Yu - 2014-02-26 - - - - This document summarizes the most significant aspects of the Open Geospatial Consortium (OGC) web services architecture, which the OGC is currently developing. This architecture is a service-oriented architecture, with all components providing one or more services to other services or to clients. - 05-042r2 - 05-042r2 - Web services architecture description - Arliss Whiteside - 2005-11-21 - - - OpenGIS Web services architecture description - - - - - - - 15-113r5 - - Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure - The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. - Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure - 15-113r5 - Carl Reed - - - 2018-12-19 - - - - - 21-070 - OGC Integrated Methane Sensor Web for Emissions Management Best Practice - Part I - Fugitive Emissions Management based on AE - 2022-07-13 - - - OGC Integrated Methane Sensor Web for Emissions Management Best Practice - Part I - Fugitive Emissions Management based on AE - - Methane (CH4) is one of the most potent greenhouse gases, and the comparative impact of methane is 25 times greater than CO2 over a 100-year period. Methane is an invisible and odorless gas, and it is very labor intensive and time consuming in order to detect and repair leaks. Regulations play a critical role in methane emissions reduction, and how methane emissions are detected, repaired, and managed is highly dependent on local regulations. This OGC Best Practice document defines a SensorThings API for fugitive methane emissions management. - - - - Steve Liang - 21-070 - - - - 11-064r3 - OWS-8 CCI Schema Automation Engineering Report - 11-064r3 - - This OGC® document specifies improvements to the processing of information represented in or referenced from an application schema in UML to create derived, implementation level resources, in particular: -• XML Schema documents to represent types and their properties -• Schematron schema documents to represent constraints -• XSLT-Stylesheets to create KML instances of features -The documented improvements have been specified, implemented in the ShapeChange tool and tested in the context of schemas developed as part of the NGA's Topographic Data Store (TDS) schemas. -The work is a continuation of the work documented in OGC® document 10-088r2, the OWS-7 Schema Automation Engineering Report. - - OWS-8 CCI Schema Automation Engineering Report - - - - - 2011-11-23 - Clemens Portele, Reinhard Erstling - - - - The provenance activities reported in this document were part of the OGC Testbed 10 -Cross Community Interoperability (CCI) thread. This OGC® document gives guidelines -for the capture and documentation of provenance information at dataset, feature and -attribute level. It only considers vector features (mainly, points and lines) and does not -elaborate on the coverage data model (so it does not talk about provenance of raster -information). It proposes an approach to use the W3C PROV standard with geospatial -information that can come from different sources and are integrated through different -processing steps. It also reviews the applicability of ISO19115 and ISO19115-2 lineage. - Joan Masó, Guillem Closa Yolanda Gil and Benjamin Proß - Testbed 10 Provenance Engineering Report - 14-001 - OGC® Testbed 10 Provenance Engineering Report - - 14-001 - - - - - 2014-07-14 - - - 07-004 - GeoDDS Mass Market - - This OpenGIS(r) document describes the API for two web services capable of generating several simplified data formats including GeoRSS and the Basic XML Feature Schema -(BXFS). - - Panagiotis (Peter) A. Vretanos - 07-004 - - - GeoDDS Mass Market (formerly GeoRSS) Interoperability Program Report - - - - 2007-05-07 - - - - 2016-08-22 - Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension - 13-133r1 - 13-133r1 - - - Aaron Braeckel, Lorenzo Bigagli - OGC® Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension - - Publish/Subscribe 1.0 is an interface specification that supports the core components and concepts of the Publish/Subscribe message exchange pattern with OGC Web Services. The Publish/Subscribe pattern complements the Request/Reply pattern historically specified by many OGC Web Services. This specification may be used either in concert with, or independently of, existing OGC Web Services to publish data of interest to subscribers. - -Publish/Subscribe 1.0 primarily addresses subscription management capabilities such as creating a subscription, renewing a subscription, and unsubscribing. However, this standard also allows Publish/Subscribe services to advertise and describe the supported message delivery protocols such as SOAP messaging, ATOM, and AMQP. Message delivery protocols should be considered to be independent of the Publish/Subscribe 1.0 standard. Therefore OGC Publish/Subscribe only includes metadata relating to message delivery protocols in sufficient detail to allow for different implementations of Publish/Subscribe 1.0 to interoperate. - -This specification defines an extension to the OGC Publish/Subscribe (PubSub) 1.0 Core to allow for Publish/Subscribe communications usingthe SOAP protocol. - - - - - 09-182r1 - - 09-182r1 - End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2 - Josh Lieberman - End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2 - 2010-02-16 - This Architecture Implementation Pilot, Phase 2 Engineering Report (AIP-2 ER) describes the practice of deploying, documenting, and registering contributed resources from the point of view of classes of GEOSS users who rely on GEOSS to support discovery and access to those resources. It emphasizes two paradigms for the GEOSS Common Infrastructure: 1) Service-oriented infrastructure for development of service-based community applications by technically advanced users; and 2) Content-oriented search facility and Web-based access mechanisms for end-users with a range of technical skills and domain knowledge. End-to-end here refers to the bidirectional connection between desired discovery practices and goals on the user end; and the required resource interfaces and documentation on the provider end. - - - - - - - - Ingo Simonis - 18-046 - - - 2018-12-20 - - - - OGC Earth Observation Exploitation Platform Hackathon 2018 Engineering Report - - 18-046 - Earth Observation Exploitation Platform Hackathon 2018 Engineering Report - The Earth Observation Exploitation Platform Hackathon 2018 was conducted to evaluate the standards based architecture for deploying and executing arbitrary applications close to the physical location of the data in heterogeneous cloud environments. The Hackathon was very successful in demonstrating both efficiency and sustainability of the architecture developed in Testbed-13. Efficient, because it was possible to setup the full execution workflow of 128 Sentinel-1 images within the 1.5 days of the Hackathon in a multi-vendor environment. Sustainable, because the architectural approach provides sufficient flexibility to cater for possible extensions and exchange of cloud & container middleware. - -The Hackathon produced a number of suggestions for future work items. These include new tools to facilitate the process of Application Package generation to make it even simpler for scientists to bring their applications to the market; a more detailed specification to further improve the level of interoperability; and a best practice document with lots of examples that illustrate the necessary steps to make applications available. - -Hackathon participants highlighted that such a level of robustness, flexibility, and maturity of the application-to-the-cloud architecture has been developed in nine months only during Testbed-13. The participants recommend to continue interlacing major OGC Innovation Program activities, such as testbeds, with short term rapid prototyping initiatives such as hackathons. Almost all participants of the Hackathon had been new to the OGC Innovation Program. These participants emphasized that the Hackathon provided an outstanding opportunity for newcomers to get quickly familiar with the latest standardization efforts and helped tremendously in understanding investments and new market opportunities for applications-in-the-cloud. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 23-011r1 - Testbed-18: 3D+ Data Space Object Engineering Report - Testbed-18: 3D+ Data Space Object Engineering Report - With the growing commercialization of space there is a need to look beyond the earth and explore the integration of sensors or assets in celestial orbits or in free flight in our solar system. Their exact tracking and localization are becoming increasingly important as space emerges as the newest area in need for standard-based mechanisms for streaming and for data integration from various sensors. - -This Open Geospatial Consortium (OGC) Testbed 18 3D+ Data Space Object Engineering Report (ER) describes existing standards in terms of their ability to represent a suite of multidimensional Coordinate Reference Systems (CRS) and associated geometries as well as identifies shortfalls in these standards. - 23-011r1 - 2023-06-26 - - Martin Desruisseaux, Logan Stark - - - - - - Common semantic for units of measurement to be used across all OGC specifications. - Units of Measure and Quantity Datatypes - 01-044r2 - 01-044r2 - 2001-06-15 - John Bobbitt - - Units of Measure and Quantity Datatypes - - - - - - - - 2020-10-14 - Geospatial Coverages Data Cube Community Practice - 18-095r7 - Geospatial Coverages Data Cube Community Practice - 18-095r7 - - - George Percivall - Data cubes for geospatial information provide the means to integrate observations and other types of geospatial data for use in multiple applications through simplified access and efficient analytics. Using the Geospatial Coverages data structure, this Community Practice defines requirements for a geospatial coverages data cube infrastructure and guidelines for enhancements and extensions to the basic core. - - - - - - - A URN namespace for the Open Geospatial Consortium (OGC) - - 04-013r4 - A URN namespace for the Open Geospatial Consortium (OGC) - - 2004-09-20 - This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC (such as OGC Standards, XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other documents). The formal Namespace identifier (NID) is ogc. - - 04-013r4 - Carl Reed - - - - - - Peter Schut - - 04-010r1 - - - Geolinked Data Access Service - 04-010r1 - - - Geolinked Data Access Service - 2004-05-04 - A Geolinked Data Access Service (GDAS) provides a way to publish and access data that refers to spatial features (e.g. population data for countries). A GDAS can expose data from non-GIS databases so that it can be manipulated and mapped with the aid of a Geolinking Service. - - - - - Testbed-18: Moving Features Engineering Report - - 22-016r3 - Testbed-18: Moving Features Engineering Report - - - - Brittany Eaton - This OGC Testbed-18 (TB-18) Engineering Report (ER) is based on previous OGC Moving Features and Sensor Integration (MFSI) activities. The OGC TB-18 MFSI task addressed the interoperability between sensors and between sensing systems as well as the exchange of multiple sources of detected moving objects into one common analytic client. This ER describes the architecture framework for multi-source moving object detection into the client supported by OGC MFSI Standards and describes challenges of multi-sensor integration in the context of Moving Features data. - 2023-06-26 - 22-016r3 - - - OGC® Web Coverage Service Interface Standard - CRS Extension - - - - 2014-03-11 - Peter Baumann, Jinsongdi Yu - Web Coverage Service Interface Standard - CRS Extension - 11-053r1 - This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request that allows a client, a service, or other application to specify the Coordinate Reference System (CRS) in which coverages are delivered. Note that the CRS of the input bounding box is already defined in the OGC WCS Core Implementation Standard [OGC 09-110r3]. - - 11-053r1 - - - - - 16-131r2 - Big Geospatial Data – an OGC White Paper - 16-131r2 - - Big Geospatial Data – an OGC White Paper - 2017-09-25 - - - - This white paper is a survey of Big Geospatial Data with these main themes: - - Geospatial data is increasing in volume and variety; - New Big Data computing techniques are being applied to geospatial data; - Geospatial Big Data techniques benefit many applications; and - Open standards are needed for interoperability, efficiency, innovation and cost effectiveness. - - -The main purpose of this White Paper is to identify activities to be undertaken in OGC Programs that advance the Big Data capabilities as applied to geospatial information. - -This white paper was developed based on two Location Powers events: - - Location Powers: Big Data, Orlando, September 20th, 2016; and - Location Powers: Big Linked Data, Delft, March 22nd, 2017. -For information on Location Powers: http://www.locationpowers.net/pastevents/ - - George Percivall - - - - - - - 2014-01-31 - - Download Service for Earth Observation Products Best Practice - 13-043 - - - 13-043 - Daniele Marchionni, Raul Cafini - OGC Download Service for Earth Observation Products Best Practice - This OGC® Best Practices document specifies the interfaces, bindings, requirements, -conformance classes for online download of Earth Observation products. This protocol -covers several scenarios implemented by European Space Agency - ESA for providing its -products to users: -- The EO Product to be downloaded is already available and can be downloaded as -it is. -- The EO Product is not online available but is stored in a near online archive. -- The EO Product is advertised in a Catalogue, but it is not physically available and -it has to be generated on the fly by a processing facility. -- The EO product is archived in several distributed online archives and it can be -downloaded in parallel. -The basic scenarios can be simply supported by Web Browsers, the most complex ones -need a dedicated client (download manager) supporting Metalink and multisource -download. -This Best Practice document has been prepared basing on the work performed in the -frame of ESA’s Next Generation Earth Observation user services and it was initially -produced during the ESA - - - 06-080 - This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGCTM Catalogue Services Specification v2.0.0 (with Corrigendum) [OGC 04-021r3]. - Jerome Gasperi - 2006-07-27 - - - - - - GML Application Schema for EO Products - - GML Application Schema for EO Products - 06-080 - - - - - - Roger Brackin, Pedro Gonçalves - - 12-080r2 - OWS Context Conceptual Model - This standard describes the use cases, requirements and conceptual model for the OWS Context encoding standard. The goal of this standard is to provide a core model, which is extended and encoded as defined in extensions to this standard. A ‘context document’ specifies a fully configured service set which can be exchanged (with a consistent interpretation) among clients supporting the standard. -The OGC Web Services Context Document (OWS Context) was created to allow a set of configured information resources (service set) to be passed between applications primarily as a collection of services. OWS Context is developed to support in-line content as well. The goal is to support use cases such as the distribution of search results, the exchange of a set of resources such as OGC Web Feature Service (WFS), Web Map Service (WMS), Web Map Tile Service (WMTS), Web Coverage Service (WCS) and others in a ‘common operating picture’. Additionally OWS Context can deliver a set of configured processing services (Web Processing Service (WPS)) parameters to allow the processing to be reproduced on different nodes. -OWS Context is aimed at replacing previous OGC attempts at providing such a capability (the Web Map Context WMC) which was reasonably successful but limited to WMS. Other work on the ‘Location Organizer Folder (LOF)’ was also taken into consideration. The concept of OWS Context, and the first prototype document was produced as part of OGC testbed OWS-7. See OGC 10-035r1, Information Sharing Engineering Report. In order to achieve mass market appeal, as well as being useful to a wider community, the use of OWS Context support to other existing standards was considered. Multiple encoding formats for OWS Context have been developed (ATOM, JSON). Each of these is described in a separate OWS Context Extensions to the Core model. -This document concentrates on describing the OWS Context Model in abstract terms using UML. The document defines requirements and use cases. It also includes an abstract test suite to verify that encodings are compliant with the core specification. The intent of OWS Context is to allow many types of OGC Data Delivery service to be referenced and therefore exploited (for example, not just WMS but also WFS, WCS and WPS) but it does not explicitly define the encoding of these services in the core (only the general approach to be used for different types of service interface). Service explicit encodings are defined within the extension documents for ATOM and JSON. -The abbreviation owc is used throughout this document for OWS Context. - - 12-080r2 - 2014-01-22 - OGC OWS Context Conceptual Model - - - - - - - An Experiment to Link Geo-Referenced Multimedia and CityGML Features - - An Experiment to Link Geo-Referenced Multimedia and CityGML Features - 19-090r1 - Ki-Joune Li, Sung-Hwan Kim, Yong-Bok Choi - - 19-090r1 - - - 2020-04-17 - In this paper, we present an experiment on linking geo-referenced images and videos with CityGML objects. Data models are proposed with XML schema from two viewpoints: one for linking features in 2D images or videos with 3D CityGML objects and the other for camera FoV (Field of View). In order to validate the proposed data models, we developed an authoring tool for building XML documents to link geo-referenced images and videos with CityGML objects and a web environment for processing queries based on the linking data. - - - Carl Reed, PhD - - - - 22-032r1 - OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Version 1.3 Release Notes - - - - OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Version 1.3 Release Notes - These I3S Release notes document changes incorporated into the OGC I3S Community Standard version 1.3. - 2023-01-11 - 22-032r1 - - - 08-068r2 - The OGC® Web Coverage Processing Service (WCPS) defines a protocol-independent language for the extraction, processing, and analysis of multi-dimensional coverages representing sensor, image, or statistics data. - - - - 2009-03-25 - Peter Baumann - - - - OpenGIS Web Coverage Processing Service (WCPS) Language Interface Standard - Web Coverage Processing Service (WCPS) Language Interface Standard - 08-068r2 - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Documents of type Public Engineering Report - Documents of type Public Engineering Report - - Documents of type Public Engineering Report - - - - - 2009-09-11 - OWS-6 GeoProcessing Workflow Thread Summary ER - 09-063 - - - Lewis Leinenweber - - 09-063 - This OGC® document summarizes work completed in the GeoProcessing Workflow thread of the OWS-6 Testbed, it is applicable to the OGC Interoperability Program testbed. - - OWS-6 GeoProcessing Workflow Thread Summary ER - - - - - - The OpenGIS® Web Services Common (WS-Common) Interface Standard specifies parameters and data structures that are common to all OGC Web Service (OWS) Standards. The standard normalizes the ways in which operation requests and responses handle such elements as bounding boxes, exception processing, URL requests, URN expressions, and key value encoding. Among its uses, this document serves as a normative reference for other OGC Web Service standards, including the OpenGIS Web Map Service (WMS) [http://www.opengeospatial.org/standards/wms], Web Feature Service (WFS) [http://www.opengeospatial.org/standards/wfs], and Web Coverage Service (WCS) [http://www.opengeospatial.org/standards/wcs] standards. Rather than continuing to repeat this material in each such standard, each standard will normatively reference parts of this document. - Arliss Whiteside - - - - - 06-121r3 - OpenGIS Web Service Common Implementation Specification - 06-121r3 - Web Service Common Implementation Specification - 2007-04-03 - - - - - - - - - - - - - OGC Testbed-17: Data Centric Security ER - - - Aleksandar Balaban, Andreas Matheus - OGC Testbed-17: Data Centric Security ER - 21-020r1 - - This OGC Testbed-17 Engineering Report (ER) documents the enhancement of applying Data Centric Security (DCS) to OGC API Features, OGC API Maps (draft), and OGC API Tiles (draft). - -As organizations move to the cloud, it is important to incorporate DCS into the design of the new cloud infrastructure, enabling the use of cloud computing, even for sensitive geospatial data sets. The ER documents the applicability of Zero Trust through a Data Centric security approach (DCS) when applied to vector and binary geospatial data sets (Maps, Tiles, GeoPackage containers) and OGC APIs. - -The defined architecture extends the typical Zero Trust Domain component by introducing a Key Management System (KMS) to support key registration and the management of access conditions for key retrieval. The prototype implementations (DCS Client, DCS Server and KMS) demonstrate how to request encrypted geospatial data as JSON for encrypted vector data, HTTP Multipart for encrypted map data or GeoPackage with encrypted content; how to obtain decryption key(s) and how to decrypt and display the protected data in a mobile application on Android. - - 2022-01-21 - 21-020r1 - - - - - 06-080r4 - This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGC - Jerome Gasperi - - GML 3.1.1 Application Schema for EO products - 06-080r4 - - - - GML 3.1.1 Application Schema for EO products - 2010-02-25 - - - - - 05-047r3 - GML in JPEG 2000 for Geographic Imagery Encoding Specification - OpenGIS GML in JPEG 2000 for Geographic Imagery Encoding Specification - 2006-01-20 - - Martin Kyle, David Burggraf, Sean Forde, Ron Lake - The OpenGIS® GML in JPEG 2000 for Geographic Imagery Encoding Standard defines the means by which the OpenGIS® Geography Markup Language (GML) Standard http://www.opengeospatial.org/standards/gml is used within JPEG 2000 http://www.jpeg.org/jpeg2000/ images for geographic imagery. The standard also provides packaging mechanisms for including GML within JPEG 2000 data files and specific GML application schemas to support the encoding of images within JPEG 2000 data files. JPEG 2000 is a wavelet-based image compression standard that provides the ability to include XML data for description of the image within the JPEG 2000 data file. -See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml . - - - - 05-047r3 - - - - - - 02-066r1 - Web Map Context Documents - States how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent manner. - 2002-08-29 - - 02-066r1 - - Jean-Philippe Humblet - - Web Map Context Documents - - - - - - - 02-019r1 - - 2002-02-28 - Coverage Portrayal Service - - Jeff Lansing - The Coverage Portrayal Service (CPS) IPR proposes a standard interface for producing visual pictures from coverage data. - Coverage Portrayal Service - 02-019r1 - - - - - - - - 2021-02-26 - - - 16-004r5 - Volume 5: OGC CDB Radar Cross Section (RCS) Models (Best Practice) - 16-004r5 - - - Volume 5: OGC CDB Radar Cross Section (RCS) Models (Best Practice) - Carl Reed - This CDB volume provides all of the information required to store Radar Cross Section (RCS) data within a conformant CDB data store. - - - - - 20-032 - OGC API - Environmental Data Retrieval Sprint Engineering Report - - OGC API - Environmental Data Retrieval Sprint Engineering Report - - - 2020-10-22 - The subject of this Engineering Report (ER) is a development Sprint that was held from March 18-20, 2020 to advance the Open Geospatial Consortium (OGC) Environmental Data Retrieval (EDR) Application Programming Interface (API) candidate standard. Due to the widespread of the virus, the Sprint was held virtually by using GoToMeeting teleconferencing facilities of OGC, email and GitHub. - Chris Little, Peng Yue, Steve Olson - 20-032 - - - - - - - Peter Baumann - - - - 2010-10-27 - This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using HTTP POST with XML encoding. - 09-148r1 - 09-148r1 - Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension - OGC® Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension - - - - - 2021-02-23 - OGC API – Common and OGC API – Features Sprint 2020: Summary Engineering Report - 20-091 - - The subject of this Engineering Report (ER) is a code sprint that was held from 29 to 30 September 2020 to advance the development of the OGC API - Common - Part 2: Geospatial Data draft standard and the OGC API – Features – Part 4: Simple Transactions draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The code sprint was hosted online. The event was sponsored by Ordnance Survey (OS). - OGC API – Common and OGC API – Features Sprint 2020: Summary Engineering Report - 20-091 - Gobe Hobona - - - - - - - - - - Web View Service Discussion Paper - The Web View Service (WVS) is an extendable, interactive, image-based portrayal service for complex three-dimensional geodata such as 3D landscape and city models. 3D geodata is delivered as finally rendered images. Besides color images, relevant thematic and geometrical information such as object identity information or depth data is provided. Additionally, the WVS supports interaction with the portrayed 3D environment, e.g., information retrieval, spatial analysis, and 3D navigation. - - 09-166r2 - Web View Service Discussion Paper - - 2010-02-01 - - 09-166r2 - Benjamin Hagedorn - - - - - This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding definitions of commonly-used Coordinate Reference Systems (CRSs) plus related coordinate Conversions. - 05-095r1 - 05-095r1 - GML 3.1.1 common CRSs profile - GML 3.1.1 common CRSs profile - Arliss Whiteside - - - - - - 2006-07-18 - - - - 20-082r4 - Topic 20 - Observations, measurements and samples - - - - - 2023-05-26 - Katharina Schleidt, Ilkka Rinne - This document defines a conceptual schema for observations, for features involved in the observation process, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities. - -Observations commonly involve sampling of an ultimate feature-of-interest. This document defines a common set of sample types according to their spatial, material (for ex situ observations) or statistical nature. The schema includes relationships between sample features (sub-sampling, derived samples). - -This document concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation. - Topic 20 - Observations, measurements and samples - 20-082r4 - - - - - - - Sensor Instance Registry Discussion Paper - 10-171 - - 2010-10-12 - Sensor Instance Registry Discussion Paper - 10-171 - - - This Discussion paper introduces the Sensor Instance Registry (SIR), a web service interface for managing the metadata and status information of sensors. Furthermore this service is capable of automatically harvesting sensor metadata, transforming the collected metadata sets into a data model compatible to OGC Catalogs and to push harvested metadata into OGC Catalog instances. - Simon Jirka, Daniel Nüst - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Documents of type Discussion Paper - deprecated - Documents of type Discussion Paper - deprecated - - - Documents of type Discussion Paper - deprecated - - - - OGC Testbed-17: OGC API - Moving Features Engineering Report - - The OGC Testbed-17 Moving Features thread conducted an interoperability feasibility study that examined specific scenarios that could be supported by a Moving Features Application Programming Interface (API). The use cases considered tracking objects based on motion imagery, analytical processing and visualization. This Engineering Report presents a specification of a prototype Moving Features API, that could serve as the foundation for a future draft OGC API — Moving Features standard. - - - - 21-028 - OGC Testbed-17: OGC API - Moving Features Engineering Report - 21-028 - - - Dean Younge - 2022-01-18 - - - - - OWS-6 Georeferencable Imagery Engineering Report - 09-034 - - 2009-07-29 - This document discusses considerations about and recommendations for approaches for georeferenceable imagery under the Sensor Web Enablement thread during OGC Web Services Phase 6. This is an extension to the work described in the previous engineering report number OGC 08-071 . Georeferencealbe imagery is “a referenceable grid that has information that can be used to transform grid coordinates to external coordinates, but the transformation shall not be required to be an affine transformation”. Geolocation of georeferenceable imagery refers to the techniques described in ISO 19130, such as sensor models, functional fit models, and spatial registration using control points. - OWS-6 Georeferencable Imagery Engineering Report - 09-034 - - - Genong (Eugene) Yu, Liping Di - - - - - 05-007r2 - Web Processing Service - Web Processing Service - 2005-06-17 - Peter Schut - - A Web Service Processing Service provides access to calculations or models which operate on spatially referenced data. The data required by the service can be available locally, or delivered across a network using data exchange standards such as Geography Markup Language (GML) or Geolinked Data Access Service (GDAS). The calculation can be as simple as subtracting one set of spatially referenced numbers from another (e.g. determining the difference in influenza cases between two different seasons), or as complicated as a global climate change model. - -This specification is intended to provide a mechanism to identify the spatially-referenced data required by the calculation, initiate the calculation, and manage the output from the calculation so that it can be accessed by the client. The Web Processing Service is targeted at both vector and raster data based processing. - - 05-007r2 - - - - - - - - This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the extension of the OGC Symbology Encoding (SE) symbology format for improved capability and harmonization with ISO 19117 symbology, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology. - OWS-6 Symbology Encoding (SE) Changes ER - 09-016 - 09-016 - 2009-09-11 - - - Craig Bruce - - OWS-6 Symbology Encoding (SE) Changes ER - - - - - - - 18-075 - - Moving Features Encoding Part I: XML Core - 18-075 - - This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange. - 2019-01-14 - Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf - - - - OGC® Moving Features Encoding Part I: XML Core - - - The OGC provides a collaborative, consensus process for developing and approving open, international Standards and supporting content for the geospatial domain, collectively known as OGC Products. To guide the OGC Product development and approval process, a member-approved Policies and Procedures document for the Technical Committee (TC) is required. - -This document describes the TC Policies and Procedures (TC PnP). The TC has been granted authority to operate by the OGC Bylaws. The TC is composed of individuals representing organizations that are duly recognized members in good standing of the OGC. - -As the needs and purpose of the TC change, changes to these policies and procedures are approved by an electronic vote of the Voting Members of the OGC TC. These policies and procedures may be augmented or clarified by Policy Directives issued and approved by the TC or the Executive Planning Committee (EPC). Such directives are databased and hyperlinked to/from the appropriate portion of this document. - - - - - Scott Simmons - - Technical Committee Policies and Procedures - - Technical Committee Policies and Procedures - 05-020r29 - 2023-05-11 - 05-020r29 - - - Release Notes for OGC GeoPackage 1.4.0 - 23-018r1 - 23-018r1 - - Release Notes for OGC GeoPackage 1.4.0 - - - - This document provides the set of revision notes for OGC® GeoPackage Encoding Standard, version 1.4.0 [OGC 12-128r19] and does not modify that Standard. - -This document provides the details of edits, deficiency corrections, and enhancements of the above-referenced Standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility. - - 2024-02-06 - - Jeff Yutzler - - - - Compliance Engineering Report - 18-034r3 - 18-034r3 - - - - The OGC Compliance Program provides a free online testing facility based on TeamEngine and a set of test suites dedicated to specific protocols and versions, as well as specification profiles and extension. - -This document reviews the work that has been carried out as part of the Testbed-14 compliance activity, in particular covering the development of: - -A Web Feature Service (WFS) 3 core test suite, covering both the tests and the reference implementation servers - -A Defence Geospatial Information Working Group CATalog (DGIWG CAT) 2.0 extension for the Catalog Services for the Web 2.0.2 (CSW) test suite and server reference implementation - -The WFS 3.0 protocol is the next iteration of the WFS specification, focusing on open specification, ease of implementation, and modern Representational State Transfer (REST) Application Program Interface (API) approaches. - -The DGIWG CAT is an application profile of the CSW, which allows to query and get metadata following the DGIWG application profile of the ISO19139 standard, which augments the metadata elements to include information relevant to the defense organizations. - -Both the test suites are meant to be run by the Test, Evaluation, And Measurement (TEAM) Engine and eventually land on the OGC beta compliance test engine (availability on the primary site is subject to the WFS 3.0 specification being finalized and the tests being adapted to it). - 2019-02-07 - - OGC Testbed-14: Compliance Engineering Report - Andrea Aime, Emanuele Tajariol, Simone Giannecchini - - - - Martin Klopfer - 19-018 - - - - - - - 2020-02-06 - OGC Testbed-15: Open Portrayal Framework Engineering Report - 19-018 - OGC Testbed-15: Open Portrayal Framework Engineering Report - This Engineering Report (ER) describes the OGC Testbed-15 Open Portrayal Framework (OPF) Thread requirements, scenario, high-level architecture, and solutions. Main topics addressed in the OPF Thread include style changing and sharing, converting style encodings, client- / server-side rendering of vector- and raster data and data provision in denied, disrupted, intermittent, and limited bandwidth (DDIL) infrastructure situations. The work in the OPF Thread was focused on an OGC Application Programming Interface (API) oriented approach. - - - DGIWG - - 2021-02-25 - Defence Geospatial Information Working Group (DGIWG) GeoTIFF/TIFF Profile for Imagery & Gridded Data 2.3.1 - - - 20-095 - Defence Geospatial Information Working Group (DGIWG) GeoTIFF/TIFF Profile for Imagery & Gridded Data 2.3.1 - 20-095 - - - This OGC Best Practice was developed by the Defence Geospatial Information Working Group to address defense and intelligence user community requirements. As such, the Best Practice utilizes standardized military Coordinate Reference System (CRS) definitions, which may not be applicable to other user communities. -This Best Practice also defines a GEO_METADATA tag, which may be of more general interest. - - - - - George Percivall - - - - The ORM describes a framework for the ongoing work of the Open Geospatial Consortium and our specifications and implementing interoperable solutions and applications for geospatial services, data, and applications. - OGC Reference Model - 03-040 - - OGC Reference Model - - - 03-040 - 2003-09-16 - - - Release Notes for OGC GeoPackage 1.3.1 - 21-004 - 21-004 - - - - - - This document provides the set of revision notes for Geopackage 1.3.1 and does not modify that Standard. - -This document provides the details of edits, deficiency corrections, and enhancements of the above-referenced Standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility. - 2023-03-24 - - Release Notes for OGC GeoPackage 1.3.1 - Jeff Yutzler - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Sara Saeedi - 18-029 - OGC Testbed-14: Symbology Engineering Report - 2019-03-15 - 18-029 - Symbology Engineering Report - - The portrayal and visualization of geospatial information is a critical task for facilitating decision making, situational awareness, and spatial analysis. However, despite its importance, various local, national, and international agencies continue to use different symbols and terminology for the same event, feature, or entity. This approach prevents interoperability from being extended to the semantic level, which in turn makes it difficult to share, reuse, and mediate unambiguous portrayal information between agencies. - -This Engineering Report (ER) captures the requirements, solutions, models, and implementations of the Open Geospatial Consortium (OGC) Testbed-14 Portrayal thread. This effort leverages the work of the Portrayal Ontology development and the Semantic Portrayal Service conducted during Testbed 10, 11, 12 and 13. Thus far the emphasis for developing the portrayal ontologies (Testbeds 12 and 13) has been on modeling and representing portrayal information for feature data. The objective of Testbed-14 is to extend the portrayal ontology to accommodate more complex symbols (e.g., composite symbols) and to provide clear recommendations on how to best proceed with portrayal information encodings. - - - - - Stephan Meissl, Peter Baumann - 2011-11-23 - This Engineering Report describes progress on EO-WCS in the course of OWS-8. - OWS-8 WCS 2.0 Earth Observation Application Profile Engineering Report - - - - 11-096 - - OWS-8 WCS 2.0 Earth Observation Application Profile Engineering Report - 11-096 - - - - This document describes the results of an OGC Interoperability Experiment (IE) on the portrayal of 3D geospatial information. It contains technical details on processing 3D information in an OGC service environment as well as best practices on how to portray large data sets in urban planning scenarios, taking into account architectures and capabilities of interactive 3D graphics. Especially Web 3D Service and Web View Service, two draft standards (published as OGC discussions paper), have been in the focus of 3DPIE. - - 12-075 - Arne Schilling, Benjamin Hagedorn, Volker Coors - 12-075 - 3D Portrayal Interoperability Experiment FINAL REPORT - 2012-08-22 - - - - - - OGC 3D Portrayal Interoperability Experiment FINAL REPORT - - - 15-066r1 - Use of Semantic Linked Data with RDF for National Map NHD and Gazetteer Data Engineering Report - 2015-10-01 - Gobe Hobona;Roger Brackin - Over the past few years there has been an increase in the number, size and complexity of databases across government sectors. This has undoubtedly created challenges relating to the discovery and access of information and services on multiple databases across static and deployed networks. Linked Data has been suggested as a method able to tackle those challenges. The aim of the Hydrographic Linked Data activity in the OGC Testbed 11 was to advance the use of Linked Data for hydrographic data by building on the achievements of the previous testbeds and to improve the understanding of how to better build relations between hydro features and non-hydro features (e.g., stream gauge measurement/location vs bridge or other built features upstream or downstream). This aspect of the testbed focused on the National Hydrography Dataset (NHD) which is published by the United States Geological Survey (USGS). This OGC Engineering Report provides guidelines on the publication of hydrographic and hydrological data serialized as Resource Description Framework (RDF) using Linked Data principles and technologies based on OGC standards. The document also presents the experimentation conducted by Testbed 11 in order to identify those guidelines. - OGC® Testbed 11 Use of Semantic Linked Data with RDF for National Map NHD and Gazetteer Data Engineering Report - - - - - - 15-066r1 - - - - - - - This Interface Standard is a profile of the OGC® GML Application Schema –Coverages version 1.0 [OC 09-146r2]. This document specifies the usage of the GeoTIFF data format for the encoding of GML coverages. This encoding is used by several OGC services like the Web Coverage Service (WCS) 2.0 Interface Standard – Core [OGC 09-110r4]. - OGC® GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile - 2014-05-28 - GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile - 12-100r1 - - Stephan Meissl - 12-100r1 - - - - - - - 04-086 - 04-086 - EA-SIG Discovery White Paper - Jeff Harrison,A.J. Maren,Jeff Stohlman,Mike Meyer,Glenn Pruitt,John Clink,Hans Polzer,Mark Schiffner - EA-SIG Discovery White Paper - 2004-02-20 - - - *RETIRED* This document describes the role of Discovery Services in the net-centric enterprise. The network centric enterprise is an environment with an almost infinite variety of resources. In this rich environment, suitable resources can be found to support almost any operational need. The problem, however, is finding the appropriate resources when they are needed. Discovery services address this problem. - - - - - Tom Kralidis, Mark Burgoyne, Steve Olson, Shane Mill - Discussion paper for Publish-Subscribe workflow in OGC APIs - 23-013 - - - - - 2023-10-26 - 23-013 - - OGC APIs provide Web based capabilities which are typically based on polling for collection resource updates (new features/records items, coverages, maps, etc.). Depending on a collection’s temporal resolution or frequency of updates, an event-driven / Publish-Subscribe architecture provides a timely, efficient, and low latency approach for delivery of data updates. This paper provides recommendations on applying Publish-Subscribe architectural patterns to OGC APIs. - - Discussion paper for Publish-Subscribe workflow in OGC APIs - - - The objective of the proposed temporal extensions to the WFS is to enable temporal/geospatial queries using the GML temporal types against GML dynamic features employing either the snapshot or time history model (time slices). - - - David S. Burggraf, Ron Lake, Darko Androsevic - - - 2007-08-14 - - 06-154 - - WFS Temporal Investigation - 06-154 - OWS 4 WFS Temporal Investigation - - - - - Jan Herrmann, Andreas Matheus - 13-099 - GeoXACML and XACML Policy Administration Web Service (PAWS) - OGC GeoXACML and XACML Policy Administration Web Service (PAWS) - This specification defines the interfaces of the OGC (Geo)XACML Policy Administration Web Service (OGC (Geo)XACML PAWS or simply PAWS in the following) that supports the creation, modification, exchange, analysis, testing, transformation, encrypting and signing of XACML and GeoXACML encoded access control policies. -This draft specification was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. This document presents the results of the work within add-on project of the OWS-9 Security and Services Interoperability (SSI) thread. -Please note that currently the document only contains the definition of the mandatory operations i.e. the basic conformance class. The writing of the sections describing the optional operations is still a to do. These sections need to define the following operations: -• AnalyzePolicyElement operation -• OptimizePolicyElement operation -• TransformPolicyElement operation -• TestPolicyElement operation -• EncryptPolicy operation -• SignPolicy operation -Suggested additions, changes, and comments on this report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document. - - - - - 2013-11-06 - 13-099 - - - - - Simon Jirka, Christoph Stasch - 2018-04-23 - Incident Management Information Sharing Profile Recommendations for OGC Web Services Engineering Report - 15-118r1 - The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives: - -• Apply OGC principles and practices for collaborative development to existing standards and technology to prototype an IoT approach to sensor use for incident management; - -• Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability; - -• Develop profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability; and - -• Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario. - -Based on the findings gathered during the implementation and work on these objectives, this Engineering Report describes recommendations on profiles for OGC Web services that shall be used to build IMIS systems. - - - - 15-118r1 - Incident Management Information Sharing Profile Recommendations for OGC Web Services Engineering Report - - - - - - CS Smyth - - - 06-024r4 - Location Services: Tracking Service Interface Standard - OGC Location Services (OpenLS): Tracking Service Interface Standard - 06-024r4 - - 2008-09-08 - - The OpenGIS Tracking Service Interface Standard supports a very simple functionality allowing a collection of movable objects to be tracked as they move and change orientation. The standard addresses the absolute minimum in functionality in order to address the need for a simple, robust, and easy-to-implement open standard for geospatial tracking. - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - Clemens Portele - - 2008-07-02 - - 08-077 - OWS-5 Engineering Report: Local MSD Implementation Profile (GML 3.2.1) - - 08-077 - OGC® OWS-5 Engineering Report: Local MSD Implementation Profile (GML 3.2.1) + + 2003-01-20 - - This document contains a data content specification for Local Mission Specific Data (MSD) and is based on the GEOINT Structure Implementation Profile (GSIP) developed by the NGA. This document defines the GML 3.2.1 (ISO 19136) encoding requirements for Local MSD. The structure of the document is based on ISO 19131 (Geographic Information – Data Product Specification). - - - - 05-134 - - - - Keith Ryden + William Lalonde + + + 03-031 + Style Management Service + This document describes the proposed system design for the OGC Style Management Service (SMS). +The SMS must manage distinct objects that represent styles and symbols and provide the means to discover, query, insert, update, and delete these objects. +Styles provide the mapping from feature types and feature properties and constraints to parameterized Symbols used in drawing maps. Symbols are bundles of predefined graphical parameters and predefined fixed graphic images. + Style Management Service + 03-031 + - Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option - 05-134 - 2005-11-30 - This part of OpenGIS - OpenGIS Implementation Specification for Geographic information - Simple feature access - - - - - - Web Terrain Service RFC - 03-081r2 - - Joshua Lieberman - - - OpenGIS Web Terrain Service RFC - 03-081r2 - This document is a companion specification to the OpenGIS Web Map Service Interface Implementation Specification version 1.1.1 [4], hereinafter WMS 1.1.1. -WMS 1.1.1 specifies how individual map servers describe and provide their map content. The present Web Terrain Service specification describes a new operation, GetView, and extended Capabilities which allow a 3D terrain view image to be requested, given a map composition, a terrain model on which to drape the map, and a 3D viewpoint from which to render the terrain view. A simple attempt is also made to reconcile 2D and 3D viewpoints by allowing the requested 3D area of view to be approximated with a WMS 1.1.1 bounding box - 2003-11-07 - - - - 20-031 - - + + Timo Thomas - 20-031 - 3D Data Container and Tiles API Pilot Summary Engineering Report - This Engineering Report summarizes the purpose and key results of the 3D Data Container and Tiles API Pilot, an OGC Innovation Program initiative conducted between October 2019 and July 2020. In the context of both existing and emerging 3D and 2D standards, the focus of the Pilot was on the exchange and visualization of 3D data using open standards. - 3D Data Container and Tiles API Pilot Summary Engineering Report - - - - 2020-10-22 - Tim Miller, Gil Trenum, Ingo Simonis - - - Sam Meek - 2022-01-24 - - - 21-041r2 - OGC Conceptual Modeling Discussion Paper - Historically, conceptual modeling was utilized sporadically within the Open Geospatial Consortium (OGC). Models were used in OGC standards both informatively and normatively to describe the structure of the information within a standard for a particular domain. As independent standards-development organizations, OGC and alliance partners such as ISO / TC211 did not always develop common models. There are several examples of conceptual models in OGC’s Abstract Specifications, many of which have become ISO / TC211 standards since their publication. Outside of Abstract Specifications, there are fewer examples of conceptual models in Implementation Standards. Logical Models and Physical Models tend to be specified more in Implementation Standards. - -The need for conceptual models in Implementation Standards has become apparent since the OGC is moving towards resource based architecture through the development of the OGC Application Programming Interface (API) suite of standards. In the previous ways of working, standards and encodings mapped 1:1, as many OGC standards were based on the Extensible Markup Language (XML) and a standard described a particular set of XML documents to support a domain. The move to OGC API has led towards a separation of an information model represented in a standard from encodings, which is the way that the information models are expressed in a given technology. In other words, the move to OGC API has led to a clearer separation of the logical model from the physical model. - -The utilization of conceptual modeling practices may be employed to manage, track, or govern the use of concepts and terms within different standards. The OGC should adopt conceptual modeling where suitable with a new group to support the working groups with the modeling effort that may otherwise have not been completed because a lack of expertise or value recognition. Taking the concept one step further, Model Driven Architecture (MDA) is a transformation process to create a platform specific model, or implementation from a logical, platform-independent model. This process could be implemented to enable quick production of standards into different target technologies or for the creation of new standards entirely. This paper does not suggest making MDA and associated mandatory for future standards generation. - 21-041r2 - - - - OGC Conceptual Modeling Discussion Paper - - + This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 9 (OWS-9). This Engineering Report summarizes the OWS-9 activity regarding the extension of the Web Feature Service (WFS) and Filter Encoding (FE) standards to support dynamic feature data. +Specifically this document describes the result work performed in OWS 9 on the WFS Temporality Extension. The technical specification including background is discussed and defined in the OGC Discussion Paper 12-027r1. This document gives a summary about issues, lessons learned, recommendations, accomplishments and benefits for the Aviation Architecture. It also gives an outlook on future work items and change requests. + + 12-146 + OWS-9 Web Feature Service Temporality Extension Engineering Report + 12-146 + 2013-06-18 + OGC® OWS-9 Web Feature Service Temporality Extension Engineering Report - OWS-6 Sensor Web Enablement (SWE) Engineering Report - This OGC® document summarizes work completed in the OWS-6 Sensor Web Enablement (SWE) thread. - OWS-6 Sensor Web Enablement (SWE) Engineering Report - 09-064r2 - 2009-09-11 - Ingo Simonis - - - - 09-064r2 + - - Hugo Ledoux - 20-072r2 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Documents of type Discussion Paper - deprecated - - CityJSON Community Standard 1.0 - 20-072r2 - OGC CityJSON Community Standard 1.0 - - - 2021-08-13 - CityJSON is a JSON-based encoding for a well-documented subset of the OGC CityGML data model (version 2.0.0). CityJSON defines how to store digital 3D models of cities and landscapes. The aim of CityJSON is to offer an alternative to the GML encoding of CityGML, which can be verbose and complex to read and manipulate. CityJSON aims at being easy-to-use, both for reading datasets and for creating them. It was designed with programmers in mind, so that tools and APIs supporting it can be quickly built. - - + + Documents of type Discussion Paper - deprecated + Documents of type Discussion Paper - deprecated - - 13-131r1 - Publish/Subscribe Interface Standard 1.0 - Core - 13-131r1 - - 2016-08-22 - + + Volume 11: OGC CDB Core Standard Conceptual Model + 16-007r5 + + 16-007r5 + Sara Saeedi + This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB Standard. The objective of this document is to provide an core conceptual model for a CDB data store (repository). The model is represented using UML (Unified Modeling Language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering the UML diagrams and documentation from the original CDB submission OGC Common DataBase Volume 1 Best Practice, 2015 as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113r5]. + 2021-02-26 - - - - Publish/Subscribe 1.0 is an interface specification that supports the core components and concepts of the Publish/Subscribe message exchange pattern with OGC Web Services. The Publish/Subscribe pattern complements the Request/Reply pattern specified by many existing OGC Web Services. This specification may be used either in concert with, or independently of, existing OGC Web Services to publish data of interest to interested Subscribers. - -Publish/Subscribe 1.0 primarily addresses subscription management capabilities such as creating a subscription, renewing a subscription, and unsubscribing. However, this standard also allows Publish/Subscribe services to advertise and describe the supported message delivery protocols such as SOAP messaging, ATOM, and AMQP. Message delivery protocols should be considered to be independent of the Publish/Subscribe 1.0 standard. Therefore, OGC Publish/Subscribe only includes metadata relating to message delivery protocols in sufficient detail to allow for different implementations of Publish/Subscribe 1.0 to interoperate. - -This specification defines Publish/Subscribe functionality independently of the binding technology (e.g., KVP, SOAP, REST). Extensions to this specification may realize these core concepts with specific binding technologies. - Aaron Braeckel , Lorenzo Bigagli , Johannes Echterhoff - OGC® Publish/Subscribe Interface Standard 1.0 - Core - - - - - Sustainable development, meeting the needs of the present without compromising the ability of future generations to meet their own needs, will be accomplished by balancing social, economic and environmental objectives. In this paper the authors explain that rigorous standards for communicating environmental data are absolutely essential to enable social and economic progress in the Age of the Environment – the Anthropocene Epoch – in which humanity's expanding footprint has become the main cause of change in the planet's geology, water bodies, atmosphere and biosphere. The authors argue for a concerted and ongoing global effort to 1) define data communication and system interoperability requirements for environmental science, business and policy, and then 2) develop and implement consensus-derived, free and open environmental Information Technology (IT) standards that meet those requirements and that co-evolve with the larger IT standards framework and advances in IT. - Sustainable development, meeting the needs of the present without compromising the -ability of future generations to meet their own needs,1 - will be accomplished by -balancing social, economic and environmental objectives. In this paper the authors -explain that rigorous standards for communicating environmental data are absolutely -essential to enable social and economic progress in the Age of the Environment2 – the -Anthropocene Epoch3 – in which humanity's expanding footprint has become the main -cause of change in the planet's geology, water bodies, atmosphere and biosphere. The -authors argue for a concerted and ongoing global effort to 1) define data communication -and system interoperability requirements for environmental science, business and policy, -and then 2) develop and implement consensus-derived, free and open environmental -Information Technology (IT) standards that meet those requirements and that co-evolve -with the larger IT standards framework and advances in IT. - OGC Information Technology Standards for Sustainable Development - 2015-01-22 - 2015-01-23 - Lance McKee - OGC Information Technology Standards for Sustainable Development - Information Technology Standards for Sustainable Development - 14-095 - - - - 14-095 + + + Volume 11: OGC CDB Core Standard Conceptual Model - - - + + 2014-07-14 + OGC® Testbed 10 Provenance Engineering Report + The provenance activities reported in this document were part of the OGC Testbed 10 +Cross Community Interoperability (CCI) thread. This OGC® document gives guidelines +for the capture and documentation of provenance information at dataset, feature and +attribute level. It only considers vector features (mainly, points and lines) and does not +elaborate on the coverage data model (so it does not talk about provenance of raster +information). It proposes an approach to use the W3C PROV standard with geospatial +information that can come from different sources and are integrated through different +processing steps. It also reviews the applicability of ISO19115 and ISO19115-2 lineage. + Joan Masó, Guillem Closa Yolanda Gil and Benjamin Proß + Testbed 10 Provenance Engineering Report + 14-001 + + - Peter Baumann + + + 14-001 - 2010-10-27 - - - OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - This document specifies how Web Coverage Service (WCS) clients and servers can communicate over the Internet using HTTP GET with key/value pair (KVP) encoding. - Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - 09-147r1 - 09-147r1 - - Web Coverage Processing Service (WCPS) - 06-035r1 - Web Coverage Processing Service - Peter Baumann - - - - + + 10-100r2 + Geography Markup Language (GML) simple features profile + Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos + + + + - 06-035r1 - - - - The Web Coverage Processing Service (WCPS) supports retrieval and processing of geo-spatial coverage data. WCPS grounds on the coverage model of the OGC Web Coverage Service (WCS) Implementation Specification where coverages are defined as digital geospatial information representing space-varying phenomena, currently constrained to equally spaced grids. - The Web Coverage Processing Service (WCPS) supports retrieval and processing of geo-spatial coverage data. WCPS uses the coverage model of the OGC Web Coverage Service (WCS) Implementation Specification: coverages are defined as digital geo-spatial information representing space-varying phenomena, currently constrained to equally spaced grids. - 2006-07-26 - 2006-05-02 - Web Coverage Processing Service (WCPS) - Web Coverage Processing Service + Geography Markup Language (GML) simple features profile + 10-100r2 + This approved OpenGIS® Implementation Standard defines a Simple Features profile of the Geography Markup Language version 3.2. This Simple Features Profile has been aligned with the OGC Simple Features standard for SQL version 1.2. Simple Features include: Point, Curve (LineString), Surface (Polygon), Geometry, MultiPoint, MultiCurve, MultiSurface, and MultiGeometry. The detailed abstract model for OGC features and geometry can be found in the OGC Abstract Specification, Topic Volume 1: Features (which is equivalent to ISO 19107). + 2010-10-07 - - - This document defines the DGIWG profile for the ISO -19142:2010 - Web Feature Service (WFS) including changes -made in the OpenGIS Web Feature Service 2.0 Interface -Standard - Corrigendum. The Web Feature Service provides -access to geospatial features in a manner independent of the -underlying data store. - DGIWG - Web Feature Service 2.0 Profile - DGIWG - Web Feature Service 2.0 Profile - 15-005r1 + + 12-095 + OWS-9 Innovation - Coverages: Coverage Access (OPeNDAP) Study - Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey + James Gallagher, Peter Baumann - - 2016-02-01 - - 15-005r1 + 2013-06-18 + This document represents the OWS-9 OWS Innovations Coverage Access Study +Engineering Report. It contributes knowledge based on the experience prototyping the +WCS 2.0 Service – Access Innovations component, established in close collaboration +with the OPeNDAP group. To this end, accessing a variety of coverage data types +considering WCS 2.0 and DAP 2.0 interfaces have been implemented and demonstrated. +The final result is a WCS 2.0 interface for the DAP 2.0 suite. + OGC® OWS-9 Innovation - Coverages: Coverage Access (OPeNDAP) Study + + 12-095 + + - + - OGC Moving Features Encoding Extension: netCDF - - The netCDF Moving Features encoding extension is a summary of conventions that supports efficient exchange of simple moving features as binary files. This Discussion Paper is a complement to the Moving Features Encoding Part I: XML Core and an alternative to the Simple Comma Separated Values (CSV) extension. Compared to the CSV encoding, this netCDF encoding offers more compact storage and better performance at the cost of additional restrictions on the kinds of features that can be stored. - 16-114r2 - Moving Features Encoding Extension: netCDF - 16-114r2 - - - - 2018-04-15 - Martin Desruisseaux + 2020-11-05 + + + This OGC® IndoorGML standard specifies an open data model and XML schema of indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modeling indoor spaces for navigation purposes. + + OGC® IndoorGML 1.1 + OGC® IndoorGML 1.1 + 19-011r4 + 19-011r4 + Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker, Hye-Young Kan + - - 2010-08-18 - 10-086r1 - Andrew Turner - This document presents the Authoritative Data Source Directory (ADSD) engineering suggestions and results of the OGC OWS-7 ADSD thread. This group focused on creating a workflow for geospatially referencing, finding, and federating data sources with associated authority and relevance. - - OWS-7 - Authoritative Data Source Directory Engineering Report - + + OWS-9 OWS Innovations GMLJP2 for National Imagery Transmission Format (NITF) Engineering Report + 12-154 + 2013-02-05 + + 12-154 + OWS-9 OWS Innovations GMLJP2 for National Imagery Transmission Format (NITF) Engineering Report + + + Darko Androsevic + This OGC® document provides mapping of the national imagery transmission format (NITF) version 2.1 format and NITF tagged record extensions (TRE) to GMLJP2 v2.0 (draft) format. +This Engineering Report was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative. +This document further describes study results of analyses of NITF and NITF extensions (TRE) capabilities and how they can be supported by GMLJP2 2.0 (draft). This activity was a part of the OGC OWS-9 Innovations thread. + + - - 10-086r1 - OWS-7 - Authoritative Data Source Directory Engineering Report - - - CSW-ebRIM Registry Service - Part 2: Basic extension package - 07-144r4 - 2009-02-05 - Incorporates Corrigendum 1 (OGC 08-102r1). - 07-144r4 - - CSW-ebRIM Registry Service - Part 2: Basic extension package - Richard Martell + + 06-126 + + Compliance Test Language (CTL) Discussion Paper + 06-126 + + This document establishes Compliance Test Language, an XML grammar for documenting and scripting suites of tests for verifying that an implementation of a specification complies with the specification. + Chuck Morris + - - + + 2006-10-18 + Compliance Test Language (CTL) Discussion Paper + + + + This document provides an overview of the File Geodatabase API and documents the testing performed in the OWS 8 Testbed. + + + 11-114 + + OWS-8 Bulk Geodata Transfer with File Geodatabase + 2011-11-16 + 11-114 + OWS-8 Bulk Geodata Transfer with File Geodatabase - - - + David Danko, Lance Shipman, Paul Ramsey - In many cases geospatial or location data, including data from sensors, must be processed before the information can be used effectively. The OGC Web Processing Service (WPS) Interface Standard provides a standard interface that simplifies the task of making simple or complex computational processing services accessible via web services. Such services include well-known processes found in GIS software as well as specialized processes for spatio-temporal modeling and simulation. While the OGC WPS standard was designed with spatial processing in mind, it can also be used to readily insert non-spatial processing tasks into a web services environment. - -The WPS standard provides a robust, interoperable, and versatile protocol for process execution on web services. It supports both immediate processing for computational tasks that take little time and asynchronous processing for more complex and time consuming tasks. Moreover, the WPS standard defines a general process model that is designed to provide an interoperable description of processing functions. It is intended to support process cataloguing and discovery in a distributed environment. - - - 14-065r2 - WPS 2.0.2 Interface Standard: Corrigendum 2 - - - - - Matthias Mueller - 2018-02-16 - OGC® WPS 2.0.2 Interface Standard: Corrigendum 2 - 14-065r2 - - OGC® OWS-9 Data Transmission Management - 12-163 - 12-163 - OWS-9 Data Transmission Management - - - - This OWS-9 Engineering Report documents investigations, findings, lessons learned and -proposed future work for the Data Transmission Management unit, invented and -prototyped in OWS-9. -The purpose of the Data Transmission Management unit is to optimize, customize and -make reliable the information exchange between the aircraft and the different web -services on the ground. + + 10-094 + 2010-10-22 + David Arctur + + + OWS-7: Summary of the OGC Web Services, Phase 7 (OWS-7) Interoperability Testbed + 10-094 + OWS-7: Summary of the OGC Web Services, Phase 7 (OWS-7) Interoperability Testbed + The OGC Web Services, Phase 7 (OWS-7) Testbed was an initiative of OGC’s Interoperability Program to collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. + - 2013-06-18 - Thibault Dacla; Eriza Hafid Fazli; Charles Chen; Stuart Wilson - + + 2019-11-25 + 2016-12-16 - - Carl Reed - - 2020-10-22 - + OGC OpenSearch Extension for Earth Observation + OpenSearch Extension for Earth Observation + 13-026r8 - Topic 22 - Core Tiling Conceptual and Logical Models for 2D Euclidean Space - 19-014r3 - 19-014r3 - Topic 22 - Core Tiling Conceptual and Logical Models for 2D Euclidean Space - This OGC Abstract Specification (AS) defines: - -A conceptual model for tiling space in any dimension and; - -A logical model for 2D tiled structures and by extension tiling. The logical model is based on the conceptual model. - -The conceptual model specified in this Abstract Specification could be a sub-class in a more comprehensive Spatial Partitioning Conceptual Model. Additional Parts may be added to this AS for other dimensions, such as 3D, or other uses cases. + + This document is the specification for the OpenSearch extension for Earth Observation collections and products search. + +This standard is intended to provide a very simple way to make queries to a repository that contains Earth Observation information and to allow syndication of repositories. + 13-026r8 + + + OGC® OpenSearch Extension for Earth Observation + + + Pedro Gonçalves, Uwe Voges - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Documents of type OGC Implementation Specification + + Documents of type OGC Implementation Specification - - - GO-1 Application Objects Report - This document is a draft of the OpenGIS - - 03-064r1 - GO-1 Application Objects Report - 03-064r1 - - 2003-06-12 - - Phillip C. Dibner + Documents of type OGC Implementation Specification - - 2017-09-22 - OGC InfraGML 1.0: Part 7 – LandInfra Land Division - Encoding Standard - - - Paul Scarponcini + + OGC® GeoPackage Encoding Standard + Jeff Yutzler - - This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. -InfraGML is published as a multi-part standard. This Part 7 addresses the LandDivision and Condominium Requirements Classes from LandInfra. - + 2015-08-04 + + 12-128r12 + + This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector +geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access +and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that +guarantees data model and data set integrity and identical access and update results in response to identical requests from different +client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly +useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. + GeoPackage Encoding Standard + 12-128r12 - 16-107r2 - InfraGML 1.0: Part 7 – LandInfra Land Division - Encoding Standard - 16-107r2 + - - CUAHSI WaterML + + 11-039r3 + HY_Features: a Common Hydrologic Feature Model + 11-039r3 - 2007-05-30 + OGC HY_Features: a Common Hydrologic Feature Model - Ilya Zaslavsky, David Valentine, Tim Whiteaker - 07-041r1 - - 07-041r1 - CUAHSI WaterML + + + 2014-02-24 + Irina Dornblut, Rob Atkinson + Common semantics support the reference of features to the concept they represent and the integration of data proceed using the semantic framework such mappings provide. However there is no standard conceptual model for hydrologic feature identification. Different models of hydrologic processes, and different scales of detail, lead to a variety of information models to describe these features, and to different and mostly incompatible sets of feature identifiers. +This document describes requirements and a proposed design for a domain model of hydrologic features as a set of interrelated Application Schemas using the ISO 19109 General Feature Model, + - This document describes the initial version of the WaterML messaging schema as implemented in version 1 of WaterOneFlow web services. It also lays out strategies for harmonizing WaterML with OGC specifications, the Observations and Measurement specification in particular. - - - OGC Testbed-13: 3D Tiles and I3S Interoperability and Performance Engineering Report - - Volker Coors - - - - 17-046 - 17-046 - Testbed-13: 3D Tiles and I3S Interoperability and Performance Engineering Report - This OGC Testbed 13 Engineering Report (ER) documents the overall architecture developed in the Interoperability of 3D Tiles and I3S using a 3D Portrayal Service and performance study of 3D tiling algorithms activity. The report also summarizes a proof-of-concept of the use of 3D Tiles and I3S as data delivery formats for the OGC 3D Portrayal Service interface standard. The report captures the results from the interoperability tests performed as part of the 3D Tiles and I3S testbed work package. Specifically, this OGC Testbed activity focused on the following tasks: - -CityGML files converted into Cesium 3D Tiles using Analytical Graphics (AGI’s) 3D Tiling Pipeline, and Cesium as the rendering client; - -An OGC CDB data store converted into 3D Tiles using Compusult’s Streaming engine, Cesium and Ecere’s GNOSIS as rendering client; - -CityGML data store GeoRocket, 3DPS with 3D Tiles as data delivery format, and Cesium as rendering client; - -CityGML converted into I3S, 3DPS with I3S as data delivery format, and Cesium as rendering client; - -CityGML converted into I3S using ArcGIS and FME, 3DPS with I3S as data delivery format, and rendering in ArcGIS client; - -CityGML with application domain extension stored in GeoRocket, converted to 3D Tiles, and Cesium as the rendering client; + + David Burggraf + + 12-007r2 + OGC KML 2.3 + KML is an XML grammar used to encode and transport representations of geographic data for display in an earth browser. Put simply: KML encodes what to show in an earth browser, and how to show it. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard. -3D Tiles (generated by all streaming engines visualized) from Ecere’s GNOSIS rendering client; +The KML community is wide and varied. Casual users create KML Placemarks to identify their homes, describe journeys, and plan cross-country hikes and cycling ventures. Scientists use KML to provide detailed mappings of resources, models, and trends such as volcanic eruptions, weather patterns, earthquake activity, and mineral deposits. Real estate professionals, architects, and city development agencies use KML to propose construction and visualize plans. Students and teachers use KML to explore people, places, and events, both historic and current. Organizations such as National Geographic, UNESCO, and the Smithsonian have all used KML to display their rich sets of global data. -CDB visualized directly from Ecere’s GNOSIS rendering client; and +KML documents and their related images (if any) may be compressed using the ZIP format into KMZ archives. KML documents and KMZ archives may be shared by e&#8209;mail, hosted locally for sharing within a private internet, or hosted on a web server. + + + + + + 2015-08-04 + 12-007r2 + KML 2.3 + + + + + + + Clemens Portele, Panagiotis (Peter) A. Vretanos, Charles Heazel + 17-069r4 + OGC API - Features - Part 1: Core corrigendum + 17-069r4 + + This document specifies the behavior of Web APIs that provide access to features in a dataset in a manner independent of the underlying data store. This standard defines discovery and query operations. -I3S visualized from Ecere’s GNOSIS rendering client. +Discovery operations enable clients to interrogate the API, including the API definition and metadata about the feature collections provided by the API, to determine the capabilities of the API and retrieve information about available distributions of the dataset. - - 2018-03-05 - +Query operations enable clients to retrieve features from the underlying data store based upon simple selection criteria, defined by the client. + 2022-05-11 + OGC API - Features - Part 1: Core corrigendum - - - - Cristian Opincaru - Trusted Geo Services IPR - 06-107r1 - The OGC Trusted Geo Services Interoperability Program Report (IPR) provides guidance for the exchange of trusted messages between OGC Web Services and clients for these services. It describes a trust model based on the exchange and brokering of security tokens, as proposed by the OASIS WS-Trust specification [http://docs.oasis-open.org/ws-sx/ws-trust/200512]. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Documents of type Discussion Paper + Documents of type Discussion Paper + - - - 06-107r1 - Trusted Geo Services IPR - 2007-05-07 - + Documents of type Discussion Paper - + + 23-008r3 + OGC Training Data Markup Language for Artificial Intelligence (TrainingDML-AI) Part 1: Conceptual Model Standard + + Peng Yue, Boyi Shangguan + 23-008r3 - - - 10-069r2 - OWS-7 Engineering Report - Geosynchronization service - - - This candidate standard describes a service that allows data collectors to propose changes to be made to a data provider's features. A change proposal can be made to create new data or to modify/delete existing data. Proposed changes are reviewed (either manually or automatically) an are either accepted or rejected. Accepted changes are applied to the feature(s). The service also maintains a log of all changes applied to each feature that can be used for replication. - OWS-7 Engineering Report - Geosynchronization service - 10-069r2 - Panagiotis (Peter) A. Vretanos - 2010-08-02 - - - - OGC® Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context - Pedro Gonçalves - Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context - 14-009r1 - - 2014-04-15 - + 2023-09-19 + + OGC Training Data Markup Language for Artificial Intelligence (TrainingDML-AI) Part 1: Conceptual Model Standard - - - This document identifies the generic rules for obtaining JSON documents directly from existing XML documents and schemas elements. It is primordially targeting the OWS Context JSON Encoding design, but is presented in a generic approach. Such generic approach can offer the guidelines for other OGC services, when defining and using JSON encodings. - 14-009r1 + + The Training Data Markup Language for Artificial Intelligence (TrainingDML-AI) Standard aims to develop the UML model and encodings for geospatial machine learning training data. Training data plays a fundamental role in Earth Observation (EO) Artificial Intelligence Machine Learning (AI/ML), especially Deep Learning (DL). It is used to train, validate, and test AI/ML models. This Standard defines a UML model and encodings consistent with the OGC Standards baseline to exchange and retrieve the training data in the Web environment. + +The TrainingDML-AI Standard provides detailed metadata for formalizing the information model of training data. This includes but is not limited to the following aspects: + +How the training data is prepared, such as provenance or quality; +How to specify different metadata used for different ML tasks such as scene/object/pixel levels; +How to differentiate the high-level training data information model and extended information models specific to various ML applications; and +How to introduce external classification schemes and flexible means for representing ground truth labeling. - - - Observations and Measurements - + - 02-027 - 2002-05-31 - Observations and Measurements - 02-027 - - This document describes a framework and encoding for measurements and observations. - - Simon Cox - - - - 09-110r3 + 2021-09-13 - - - - Peter Baumann - - - 2010-10-27 - 09-110r3 - WCS 2.0 Interface Standard - Core - OGC® WCS 2.0 Interface Standard - Core - This document specifies how a Web Coverage Service (WCS) offers multi-dimensional coverage data for access over the Internet. This document specifies a core set of requirements that a WCS implementation must fulfil. WCS extension standards add further functionality to this core; some of these are required in addition to the core to obtain a complete implementation. This document indicates which extensions, at a minimum, need to be considered in addition to this core to allow for a complete WCS implementation. - - - - Johannes Echterhoff - 10-060r1 + Thomas H. Kolbe, Tatjana Kutzner, Carl Stephen Smyth, Claus Nagel, Carsten Roensdorf, Charles Heazel + + 20-010 + + OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard + 20-010 - - 2010-08-02 - 10-060r1 - OWS-7 Event Architecture Engineering Report - - OWS-7 Event Architecture Engineering Report - - - This document is applicable to use cases in which event-driven architecture principles are applied in Spatial Data Infrastructures. + This Standard defines the open CityGML Conceptual Model for the storage and exchange of virtual 3D city models. The CityGML Conceptual Model is defined by a Unified Modeling Language (UML) object model. This UML model builds on the ISO Technical Committee 211 (ISO/TC 211) conceptual model standards for spatial and temporal data. Building on the ISO foundation assures that the man-made features described in the city models share the same spatiotemporal universe as the surrounding countryside within which they reside. -The document specifies publish/subscribe functionality for OGC web services. This is done by first defining an abstract publish / subscribe model and then deriving functional requirements from this model. - - - - application/json - git:3852709b7dabb312dcd088bac852ed1baee222e3 - +A key goal for the development of the CityGML Conceptual Model is to provide a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. + +The class models described in this standard are also available at https://github.com/opengeospatial/CityGML3-Workspace/tree/1.0/UML/CityGML + OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard + - - + + 16-004r3 + Volume 5: OGC CDB Radar Cross Section (RCS) Models + 16-004r3 + Volume 5: OGC CDB Radar Cross Section (RCS) Models - + + (RCS) data within a conformant CDB data store. +Please note that the current CDB standard only provides encoding rules for using Esri ShapeFiles for storing RCS models. However, this Best Practice has been modified to change most of the ShapeFile references to “vector data sets” or “vector attributes” and “Point Shapes” to “Point geometries”. This was done in recognition that future versions of the CDB standard and related Best Practices will provide guidance on using other encodings/formats, such as OGC GML. + - 06-104r4 - Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option - The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. - OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option - - 06-104r4 - 2010-08-04 - John Herring - - - - 2006-04-21 - Symbology Encoding Implementation Specification - 05-077 - - - - This Specification defines Symbology Encoding, an XML language for styling information that can be applied to digital Feature and Coverage data. - 05-077 - + + + Carl Reed + 2017-02-23 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Documents of type Best Practices Document + Documents of type Best Practices Document - Dr. Markus M - Symbology Encoding Implementation Specification + + Documents of type Best Practices Document - - Testbed-11 Implementing Linked Data and Semantically Enabling OGC Services Engineering Report - 15-054 - Stephane Fellah + + 2014-01-31 + Daniele Marchionni, Raul Cafini + + + Download Service for Earth Observation Products Best Practice + 13-043 + 13-043 + OGC Download Service for Earth Observation Products Best Practice + This OGC® Best Practices document specifies the interfaces, bindings, requirements, +conformance classes for online download of Earth Observation products. This protocol +covers several scenarios implemented by European Space Agency - ESA for providing its +products to users: +- The EO Product to be downloaded is already available and can be downloaded as +it is. +- The EO Product is not online available but is stored in a near online archive. +- The EO Product is advertised in a Catalogue, but it is not physically available and +it has to be generated on the fly by a processing facility. +- The EO product is archived in several distributed online archives and it can be +downloaded in parallel. +The basic scenarios can be simply supported by Web Browsers, the most complex ones +need a dedicated client (download manager) supporting Metalink and multisource +download. +This Best Practice document has been prepared basing on the work performed in the +frame of ESA’s Next Generation Earth Observation user services and it was initially +produced during the ESA + - - 15-054 - - This OGC® Engineering Report (ER) summarizes the approaches, findings and the results -of the Linked Data and Semantic Enablement of OGC Web Services sub-thread activities -of the OGC Testbed-11 Cross Community Interoperability (CCI) Thread. This report -provides an overview of existing standards for geosemantics, outlines the approaches -adopted during the testbed, describes the conceptual semantic models and services -developed during this testbed to leverage Linked Data and semantic enabled OGC web -services. - OGC® Testbed-11 Implementing Linked Data and Semantically Enabling OGC Services Engineering Report - 2015-11-18 - - - Testbed-18: 3D+ Data Streaming Engineering Report - 22-035 - - 2023-09-01 - 22-035 - Testbed-18: 3D+ Data Streaming Engineering Report - - - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Testbed-18: Identifiers for Reproducible Science Summary Engineering Report + - This OGC Testbed 18 3D Plus Data Standards and Streaming Engineering Report (ER) reviews existing specifications that support interoperable descriptions of orbital and non-orbital space-based assets, objects, and observations as well as terrestrial observations. The ER suggests a framework consolidating these specifications as a foundation for modeling, representation, and serialization from space-based assets operating at any location in our solar system (3D+ data). This framework enables the streaming of 3D+ data to visualization devices (displays, AR, VR) for presentation. + The OGC’s Testbed 18 initiative explored the following six tasks. - - Jérôme Jacovella-St-Louis - - - Testbed-12 Compression Techniques Engineering Report - 16-055 - 2017-05-15 - Jeff Harrison - This Open Geospatial Consortium (OGC) document provides an analysis of the prototype implementations, approaches and performance aspects of data size reduction and compression techniques explored in OGC Testbed 12. Specifically, it describes work done during Testbed 12 investigating compression for geospatial data sets on OGC Web Feature Service (WFS) using W3C Efficient XML Interchange (EXI) Format 1.0 (Second Edition). +1.) Advanced Interoperability for Building Energy +2.) Secure Asynchronous Catalogs +3.) Identifiers for Reproducible Science +4.) Moving Features and Sensor Integration +5.) 3D+ Data Standards and Streaming +6.) Machine Learning Training Data +Testbed 18 Task 3, Identifiers for Reproducible Science, explored and developed workflows demonstrating best practices at the intersection of Findable, Accessible, Interoperable, and Reusable (or FAIR) data and reproducible science. -The investigation focused on extending WFS with EXI output formats, and the associated performance aspects of data size reduction and compression techniques. EXI is a compact representation for the Extensible Markup Language (XML) Information Set. EXI is intended to simultaneously optimize performance and the utilization of computational resources. From a practical viewpoint, EXI is designed to reduce the size of XML data exchanged between computer systems. +The workflows developed in this Testbed included: -EXI uses a grammar-driven approach designed to achieve efficient encodings using an encoding algorithm and a small set of datatype representations. Consequently, EXI processors are described by the W3C as ‘relatively simple’ and ‘can be implemented on devices with limited capacity.’ An EXI processor is used by application programs to encode their structured data into EXI streams and/or to decode EXI to make the structured data accessible. - - Testbed-12 Compression Techniques Engineering Report - 16-055 - - - - +the development of a Whole Tail workflow for land cover classification (52 Degrees North); +the development of a reproducible workflow for a deep learning application for target detection (Arizona State University); +the implementation of reproducible workflows following the approach described in the OGC API Process Part 3: Workflows and Chaining for Modular OGC API Workflows (Ecere); +the development of a reproducible workflow that runs an OGC API — Process and Feature Server instance within a Whole Tale environment (GeoLabs); and +the development of a water body detection Application Package to cover the identifier assignment and reproducibility from code to several execution scenarios (local, Exploitation Platform, Whole Tale) (Terradue). +Testbed 18 participants identified considerations and limitations for reproducible workflows and recommendations for future work to identify the benefits of reproducible science for healthcare use cases. + 22-020 + Testbed-18: Identifiers for Reproducible Science Summary Engineering Report - - - - - Provides three operations (GetCapabilities, GetMap, and GetFeatureInfo) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. - Web Map Service (Recommendation Paper) - 03-109r1 - 03-109r1 + 22-020 + + 2023-01-03 - - Web Map Service - 2004-02-18 - - Jeff de La Beaujardiere - + Paul Churchyard, Ajay Gupta + - - 14-012r1 - RESTful encoding of OGC Sensor Planning Service for Earth Observation satellite Tasking - + + - OGC RESTful encoding of OGC Sensor Planning Service for Earth Observation satellite Tasking - - This OGC® Best Practices document specifies the interfaces, bindings, requirements and conformance classes that enable complete workflows for the tasking of sensor planning services for Earth Observation (EO) satellites. In fact it provides the interfaces for supporting the following EO sensor planning scenarios: -• Planning future acquisitions with feasibility study, -• Direct planning of future acquisitions, -• Reservation of planning for future acquisitions. -This specification includes a comprehensive list of sensor options and tasking options derived from the parent specification OGC 10-135 [NR22] which gathered inputs from several Satellite Agencies and Operators: -• ESA -• EUMETSAT -• CNES -• DLR -• CSA -• Airbus Defence & Space -This document is based on the standard: -OGC 10-135, Sensor Planning Service Interface Standard 2.0 Earth Observation -Satellite Tasking Extension, version 2.0. 2011. - -which was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [OR1] and related projects. -With respect to the parent specification this Best Practice document proposes the following changes: -• Replaces SOAP with REST for service encoding. This affects not only the way the service is implemented but also the way the standard is presented and described. In fact, basing the standard on REST implies that the service has to be described in terms of resources and methods applied on them whilst in SOAP services, the description is focusing on operations and in fact the OGC 10-135[NR22] is structured in Web Service operations. -• Usage of OpenSearch Description Documents as an alternate method for describing sensors and tasking Options (§7.3.2). This specification uses the sensors and tasking options model already described in the OGC 10-135 [NR22] standard but defines an additional method for describing sensors and tasking options within OpenSearch Description Documents based on the OGC 13-039 [NR23]. Actually this part of the specification refers to the OpenSearch Extension for Earth Observation Satellite Tasking. -&#8195; - + 2013-03-26 + + EO Product Collection, Service and Sensor Discovery using the CS-W ebRIM Catalogue + 11-035r1 + Frédéric Houbie, Steven Smolders + + This is an OGC Best Practice document describing the relations that exist between several metadata conceptual models (EO Product, EO Product Collections, Sensors and Services). The specification of the linking between different artifacts is important for the process of cataloguing and discovering those artifacts. + 11-035r1 - 2014-07-17 - 14-012r1 + EO Product Collection, Service and Sensor Discovery using the CS-W ebRIM Catalogue - - Nicolas FANJEAU, Sebastian ULRICH - - - - OWS-9: OGC Mobile Apps: Definition, Requirements, and Information Architecture - 12-119r1 + + The Open Geospatial Consortium (OGC), the UK Ordnance Survey, AGI and Dstl conducted a first of a series of events called the United Kingdom Interoperability Assessment Plugfest (UKIAP) 2014. The purpose of UKIAP 2014 is to advance the interoperability of geospatial products and services based on OGC standards within the UK geospatial information (GI) community. The results of the Plugfest will allow Ordnance Survey to provide best practice guidance to those who want to consume or implement geospatial web services or products based on OGC standards. UKIAP 2014 is open to open- and closed source vendors and to all GI organizations in the UK to involve as many participants in the initiative as possible. + UK Interoperability Assessment Plugfest (UKIAP) Engineering Report + 14-057 + + 2015-03-26 + + + + Bart De Lathouwer, Peter Cotroneo, Paul Lacey + 14-057 - - - 2013-02-01 - OWS-9: OGC Mobile Apps: Definition, Requirements, and Information Architecture - This engineering report represents the results of the OWS-9 innovations thread on mobile applications. Initially, the goal was to help understanding the requirements for developing standards-based geospatially-enabled mobile applications. The report describes how OGC Enabled Mobile Apps can be integrated into information architectures based on OGC standards. Particular emphasize has been put on the future work section, as it provides valuable recommendations for further standardization work (and, equally important, highlights aspects that could be excluded from standardization) - 12-119r1 - Ingo Simonis + OGC® and Ordnance Survey - UK Interoperability Assessment Plugfest (UKIAP) Engineering Report - - Testbed-12 Web Integration Service - 16-043 - 16-043 - For many years OGC has been developing a suite of standards defining web services interfaces and encodings for geospatial processing. The suite includes a Web Map Service (WMS), a Web Map Tiling Service (WMTS), a Web Feature Service (WFS), a Web Coverage Service (WCS), a Web Catalogue Service (CSW), the Sensor Web (SWE) suite of services, etc. These service interfaces and their implementations have, more or less, been developed independently of one another resulting in isolation and poor integration between them. For example, consider a map generated by a WMS. A client or user cannot easily determine which source data was used to create the map and how to download that source data though an OGC data service such as WFS or WCS. Furthermore when one considers the Publish-Find-Bind paradigm, OGC can only partially support the full potential of this paradigm. This is because OGC structured catalogues can only register services in isolation of other related services and cannot automatically determine the relationships among services and the resources they offer. - -In order to achieve better integration between OGC web services and enhance the publish-find-bind paradigm, this OGC Engineering Report defines and discusses three key elements. These are: - -Defining a new service, called the Web Integration Service (WIS), which allows for the discovery and access to integrated sets of OGC web services deployed at an endpoint. - -Specifying a means of discovering and describing associations between web resources (both OGC and non-OGC). - -Defining extensions to the OGC catalogue to allow the service to harvest and make discoverable a rich set of linked OGC and non-OGC resources. - -The Web Integration Service (WIS) is an aggregation service whose only purpose is to provide a list of references to a suite of other, perhaps related OGC services available at an endpoint. - -A new operation, named GetAssociations, is defined as an extension such that existing OGC services (WMS, WFS, WCS, etc.) may implement this operation in order to support rich auto-discovery. This operation enables OGC web services to externalize their internal association knowledge about their content and relationships to other OGC and external resources. For example, a WMS would know if the source data for a layer it offers is a Shapefile, or a WFS feature type, or another WMS layer (i.e. cascading), or if a WMTS layer exists that renders the same information more efficiently. This internal knowledge can now be externalized via the GetAssociations operation. - -Currently, OGC Catalogues Service instances can harvest the capabilities document of an OGC web service, register that service, register the existence of the individual offerings that the service offers and also register the association between the service and the content it offers. Thus, the entire harvesting process is focused on a single OGC web service and consequently offers a limited scope of discovery. In order to support rich discovery, a catalogue needs to be able to automatically register services found at an endpoint as well as register all known associations among those services, their offerings and other OGC and non-OGC resources. This involves harvesting a service’s capabilities document to determine what content the service offers but it also involves further interrogating the service to determine of what (if any) other associations it is aware. Populated with this enhanced knowledge a client may now use a catalogue to, for example, find the description of feature data and then be able to find the WFS that offer that data, a WMS that renders those features into a map, a WMTS that has a tiled representation of that data, etc. In order to support this kind of rich discovery, a new CSW-ebRIM package is specified that defines ebRIM object types, associations, classifications and stored queries that support the description of integrated OGC web service and their artifacts within the catalogue. - Panagiotis (Peter) A. Vretanos - + + This report provides guidance for implementing the Flight Information Exchange Model (FIXM) using the same best practice as the Aeronautical Information Exchange Model (AIXM) and the Weather Information Exchange Model (WXXM) by adopting ISO and OGC standards. +The report is aimed at system and client developers that shall use the FIXM data encoding for the exchange of flight information. +This document is a deliverable for the OGC Testbed 10 (Testbed-10) testbed activity. OWS testbeds are part of OGC's Interoperability Program, a global, hands-on and collaborative prototyping program designed to rapidly develop, test and deliver proven candidate standards or revisions to existing standards into OGC's Standards Program, where they are formalized for public release. In OGC's Interoperability Initiatives, international teams of technology providers work together to solve specific geoprocessing interoperability problems posed by the Initiative's sponsoring organizations. OGC Interoperability Initiatives include testbeds, pilot projects, interoperability experiments and interoperability support services - all designed to encourage rapid development, testing, validation and adoption of OGC standards. +The Testbed-10 sponsors are organizations seeking open standard for their interoperability requirements. After analyzing their requirements, the OGC Interoperability Team recommends to the sponsors that the content of the Testbed-10 initiative be organized around the following threads: +• Cross-Community Interoperability (CCI) +• Open Mobility +• Aviation +More information about the Testbed-10 tested can be found at: +http://www.opengeospatial.org/standards/requests/103 + + 2014-07-16 - + + 14-037 + Thomas Forbes, Ballal Joglekar + OGC® Testbed 10 Flight Information Exchange Model GML Schema + Testbed 10 Flight Information Exchange Model GML Schema + 14-037 + - Testbed-12 Web Integration Service - - 2017-03-10 + - - 2006-04-19 - - OWS 3 GML Investigations - Performance Experiment by Galdos Systems - 05-101 - - David Burggraf + + + 12-128r14 + + 2017-08-25 + 12-128r14 + GeoPackage Encoding Standard - 05-101 + OGC® GeoPackage Encoding Standard + This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. - - OWS 3 GML Investigations - Performance Experiment by Galdos Systems - - In this experiment, the retrieval time of GML features from a Web Feature Service (WFS) to a WFS client will be studied by varying certain control parameters including methods of encoding and compression. Four different control parameters including encoding format, data set size, bandwidth, and feature type will be varied to test the relative performance in each case. + Jeff Yutzler + + - + + + + + + + + + + + + + + + + + + + + + + + - Gobe Hobona - The OGC Body of Knowledge is a structured collection of concepts and related resources that can be found in the OGC library. It is, in effect, a view of explicit knowledge available from the OGC Virtual Knowledge Store and related components such as the OGC Definitions Server and the OGC Glossary of Terms. The OGC Body of Knowledge is intended to provide a reference for users and developers of geospatial software. This discussion paper describes the approach taken to develop the OGC Body of Knowledge and presents the results of the approach. It is intended to encourage and facilitate discussion within the OGC membership and wider geospatial community. - - OGC Body of Knowledge - 19-077 - - OGC Body of Knowledge - Version 0.1 - Discussion Paper - - 19-077 - - 2020-05-04 + OGC® IndoorGML - with Corrigendum + + 2018-03-09 + + OGC® IndoorGML - with Corrigendum + 14-005r5 + Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker + This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes. + + 14-005r5 - - The objective of the Mass Migration Source Integration effort in OGC Testbed 13 was to understand and document how interoperability tools and practices, including open geospatial and security standards, can enable information exchange on an international level for humanitarian relief and analysis of mass movement of populations. + + + 2016-08-22 + Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension + 13-133r1 + + 13-133r1 + OGC® Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension + Aaron Braeckel, Lorenzo Bigagli + + Publish/Subscribe 1.0 is an interface specification that supports the core components and concepts of the Publish/Subscribe message exchange pattern with OGC Web Services. The Publish/Subscribe pattern complements the Request/Reply pattern historically specified by many OGC Web Services. This specification may be used either in concert with, or independently of, existing OGC Web Services to publish data of interest to subscribers. -This Engineering Report describes how Testbed 13 participants tested and demonstrated situational awareness using Internet and web technologies in a shared information exchange platform. The purpose of this platform was to help realize a Common Operational Picture (COP) for coordinating humanitarian relief activities among nations and organizations. In addition, the platform exercised security-enabled interoperable exchange of messages. +Publish/Subscribe 1.0 primarily addresses subscription management capabilities such as creating a subscription, renewing a subscription, and unsubscribing. However, this standard also allows Publish/Subscribe services to advertise and describe the supported message delivery protocols such as SOAP messaging, ATOM, and AMQP. Message delivery protocols should be considered to be independent of the Publish/Subscribe 1.0 standard. Therefore OGC Publish/Subscribe only includes metadata relating to message delivery protocols in sufficient detail to allow for different implementations of Publish/Subscribe 1.0 to interoperate. - - OGC Testbed-13: Concepts of Data and Standards for Mass Migration Engineering Report - Jeff Harrison - 2018-01-17 - 17-078 - Concepts of Data and Standards for Mass Migration Engineering Report - - - 17-078 - - +This specification defines an extension to the OGC Publish/Subscribe (PubSub) 1.0 Core to allow for Publish/Subscribe communications usingthe SOAP protocol. - - - - Lucio Colaiacomo, Joan Masó, Emmanuel Devys - GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core - 08-085r4 - - 2014-09-23 - This standard applies to the encoding and decoding of JPEG 2000 images that contain GML for use with geographic imagery. - -This document specifies the use of the Geography Markup Language (GML) within the XML boxes of the JPEG 2000 data format and provides an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations. The document also specifies the encoding and packaging rules for GML use in JPEG 2000. - - 08-085r4 - - - OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core - - - - - - - - - - - - - - - - - - - - + - 21-021 - Experts agree that access to, sharing, and application of location-enabled information is a key component in addressing health related emergencies. While the present COVID-19 pandemic has underscored a range of successes in dealing with the COVID virus, many gaps in supporting local to global preparedness, forecasting, monitoring, and response have been identified when dealing with a health crisis at such an unprecedented level. This study considers how a common, standardized health geospatial data model, schema, and corresponding spatial data infrastructure (SDI) could establish a blueprint to better align the community for early warning, response to, and recovery from future health emergencies. Such a data model would help to improve support for critical functions and use cases. - - - Alan Leidner, Mark Reichardt, Josh Lieberman + + 13-054r1 + Summary and Recommendations of the Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Interoperabi + Richard Martell + + Summary and Recommendations of the Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Interoperabi - 21-021 - Health Spatial Data Infrastructure Concept Development Study Engineering Report - 2022-01-24 - Health Spatial Data Infrastructure Concept Development Study Engineering Report - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Documents of type Discussion Paper - Documents of type Discussion Paper - Documents of type Discussion Paper - - - 11-135r2 - Name Type Specification for Coordinate Reference Systems - - 11-135r2 - - 2013-06-18 - - This document specifies a Name Type Specification (NTS) for predefined, combined, and parameterized Coordinate Reference System (CRS) definitions. This NTS augments the /def/ namespace with http URI definitions for CRSs. The NTS is based on the Name Type Specification – definitions – part 1 – basic name [OGC 09-048r3] and supersedes OGC document “Definition identifier URNs in OGC name¬space” [OGC 07-092r3]. -NTSs are maintained by the OGC Naming Authority (OGC-NA). -This document includes one Annex: a user guide to the OGC CRS resolver. + 13-054r1 + Geospatial information technologies are increasingly a foundation for supporting Information Sharing Environment (ISE), homeland security (HLS), homeland defense (HLD), law enforcement (LE), emergency management (EM) and public safety missions in the US. The inability to transport, deliver and exchange geospatial information for critical geospatial assets increases the risk to the nation. +Many ISE HLS/HDS/LE mission partners have developed stand-alone geospatial information systems (GIS) or Common Operating Picture (COP) applications to support their stakeholder communities during incidents and for daily operational support. While different missions, these GIS/COP capabilities rely upon much of the same data or generate specific data during an event. The data are often stove-piped and not exposed to a broader community that could benefit from these data, resulting in duplication and delayed or incorrect decisions. While mission partners do not need to use the same GIS/COP tools, they could benefit from shared access to the common operating data and services used within these systems if they were exposed and exchanged using open standards. +Under the auspices of the Program Manager for the Information Sharing Environment (PM-ISE), an identified government-wide information sharing shortfall will be resolved by funding work to enhance the National Information Exchange Model (NIEM). The focus of this work is to further enhance the framework’s geospatial exchange capability in light of guidelines and standards issued by the Open Geospatial Consortium (OGC) so as to significantly improve inter-government information sharing. + 2013-11-07 + + + + GML simple features profile + 2005-07-04 + + This profile defines a restricted but useful subset of XML-Schema and GML to lower the + Peter Vretanos + + GML simple features profile + 05-033r9 + + + + 05-033r9 + + + 16-106r2 + + Hans-Christoph Gruler + 2017-08-16 - OGC® Name Type Specification for Coordinate Reference Systems - Peter Baumann + + + InfraGML 1.0: Part 6 – LandInfra Survey - Encoding Standard + 16-106r2 + This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. +InfraGML is published as a multi-part standard. This Part 6 addresses the Survey, Equipment, Observations and Survey Results Requirements Classes from LandInfra. + + OGC InfraGML 1.0: Part 6 – LandInfra Survey - Encoding Standard - + + + Dmitry Brizhinev, Sam Toyer, Kerry Taylor - 2021-02-26 - - OGC CDB Version 1.2 Release Notes - - 20-006 - This document provides the set of revision notes for the CDB Standard, version 1.2 [OGC <document number>]> and does not modify that standard. - 20-006 - OGC CDB Version 1.2 Release Notes + + + 2020-09-17 + This document describes how dense geospatial raster data can be represented using the W3C RDF Data Cube (QB) ontology [vocab-data-cube] in concert with other popular ontologies including the W3C/OGC Semantic Sensor Network ontology (SSN) [vocab-ssn], the W3C/OGC Time ontology (Time) [owl-time], the W3C Simple Knowledge Organisation System (SKOS) [skos-reference], W3C PROV-O [prov-o] and the W3C/OGC QB4ST [qb4st]. It offers general methods supported by worked examples that focus on Earth observation imagery. Current triple stores, as the default database architecture for RDF, are not suitable for storing voluminous data like gridded coverages derived from Landsat satellite sensors. However we show here how SPARQL queries can be served through an OGC Discrete Global Grid System for observational data, coupled with a triple store for observational metadata. While the approach may also be suitable for other forms of coverage, we leave the application to such data as an exercise for the reader. + + Publishing and Using Earth Observation Data with the RDF Data Cube and the Discrete Global Grid System + 16-125 + Publishing and Using Earth Observation Data with the RDF Data Cube and the Discrete Global Grid System + 16-125 + + + + + CF-netCDF Core and Extensions Primer + 10-091r3 + 10-091r3 + + This OGC primer provides an overview of the OGC CF-netCDF standards suite by describ-ing the CF-netCDF core and extensions. The CF-netCDF standard defines how to encode digital geospatial information representing space/time-varying phenomena + + Ben Domenico + + CF-netCDF Core and Extensions Primer + 2011-04-05 + + + + 2017-04-04 + This document is a deliverable of the OGC Testbed 12. It describes the results of enhancing the tool ShapeChange in the following areas of processing an ISO 19109 conformant application schema: + +Creating a schema profile - to support implementations that focus on a subset of the use cases in scope of the original application schema. + +Deriving an ontology representation of the application schema (using RDF(S)/SKOS/OWL) - to support Semantic Web / Linked Data implementations. + Testbed-12 ShapeChange Engineering Report + 16-020 + + + + 16-020 + Testbed-12 ShapeChange Engineering Report + - Carl Reed - + + Johannes Echterhoff - - + + Testbed-10 CCI VGI Engineering Report + 14-016 + + OGC® Testbed-10 CCI VGI Engineering Report + 2014-07-15 + + This Engineering Report was created as a deliverable for the OGC Testbed 10 (Testbed- +10) initiative of the OGC Interoperability Program. This report describes an approach for +integrating Volunteered Geographic Information (VGI) into a spatial data infrastructure +and reports on findings about the advancements using VGI resources. It includes +optimization ideas, service change recommendations, and lessons learned. +This is not a normative document. + Arne Bröring;Simon Jirka;Matthes Rieke, Benjamin Pross + 14-016 + - Testbed-12 Semantic Portrayal, Registry and Mediation Engineering Report - 16-059 - Stephane Fellah + + + + This Open Geospatial Consortium (OGC) Engineering Report (ER) will describe the advancement of an Execution Management System (EMS) to support Web Processing Service (WPS) climate processes deployed on the Earth System Grid Federation (ESGF). The report introduces climate data, processes and applications into Common Workflow Language (CWL) workflows with the intent of advancing: application packaging, deployment and execution in clouds; interoperability of services in federated cyberinfrastructures; and geospatial workflows towards standardization. Work presented in this report is a direct continuation of the Earth Observation & Clouds (EOC) thread of Testbed-14. This report is expected to be of relevance to Testbed-15, both to the Earth Observation Process and Application Discovery (EOPAD) task and the Machine Learning task. This engineering report will describe: relevant work conducted in OGC Testbed-14; ESGF and its compute challenge; adaptations of existing climate processes into workflows; interoperability experiments with ESGF endpoints conforming to a common API. + Tom Landry, David Byrns + Earth System Grid Federation (ESGF) Compute Challenge + 19-003 + + 19-003 + + + Earth System Grid Federation (ESGF) Compute Challenge + 2019-09-24 - This engineering report documents the findings of the activities related to the Semantic Portrayal, Registry and Mediation components implemented during the OGC Testbed 12. This effort is a continuation of efforts initiated in the OGC Testbed 11. This report provides an analysis of the different standards considered during this effort, documents the rendering endpoints extension added to the Semantic Portrayal Service and the migration of the Portrayal metadata to the Semantic Registry, which is aligned with the DCAT REST Service API. We also discuss the integration of the CSW ebRIM for Application Schema with the Semantic Mediation Service, and document the improvements of the SPARQL Extensions, Portrayal and Semantic Mediation ontologies defined in the previous testbed. - - - 16-059 - Testbed-12 Semantic Portrayal, Registry and Mediation Engineering Report - 2017-06-16 - - - 14-121r2 - 14-121r2 - Web Query Service - - - 2016-12-22 - This OGC Web Query Service (WQS) defines a service interface for retrieving any kind of subset of information provided by the server addressed. WQS is com¬pletely agnostic of any semantics and, therefore, not bound to any predefined structures, such as coordinates, fea-tures, coverages, or metadata. This makes WQS particularly suitable for retrieval from heter-ogeneous data offerings combining features, coverages, and catalog information in some ap-plication-defined way. A second use case is selective retrieval from a Capabilities document to avoid downloading large such documents and performing extraction on client side. -To this end, the Query request type is defined which, based on an XPath expression as input, extracts the matching information from the service’s offering and returns it (currently: as an XML document). - + + Gobe Hobona + - Peter Baumann - OGC® Web Query Service + 21-042 + May 2021 OGC API Code Sprint Summary Engineering Report - + May 2021 OGC API Code Sprint Summary Engineering Report + + The subject of this Engineering Report (ER) is a code sprint that was held from 26 to 28 May 2021 to advance the development of the OGC API - Maps draft standard, OGC API - Tiles draft standard, and the OGC API – Styles draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The code sprint was hosted online. The code sprint was sponsored by Ordnance Survey (OS) and Natural Resources Canada (NRCan). + + + 21-042 + 2021-11-29 - - This document outlines the concepts, best practices, and lessons learned gathered from integrating Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) standard-compliant sensors into an OGC Sensor Web Enablement (SWE)-based architecture. The document also specifies a web service interface for interacting with CCSI sensors and defines the basis for a profile that can be used to represent CCSI sensor definitions, data, and commands in SWE formats. - OWS-6 Common CBRN Sensor Interface (CCSI)-Sensor Web Enablement (SWE) Engineering Report - 09-007 - 09-007 - 2009-10-09 - + + + + + + + + + + + + + + + + + + + + + + + + + + + + 06-043r3 + WCS: Add Transaction operation + + + + + + Specify an additional optional + 06-043r3 + Change Request: WCS: Add Transaction operation + Arliss Whiteside + 2007-05-10 + + + 05-099r2 + 05-099r2 + GML 3.1.1 simple dictionary profile + + Arliss Whiteside + 2006-07-18 + GML 3.1.1 simple dictionary profile + This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding simple dictionaries. This profile can be used without a GML Application Schema, and such use is assumed in this document. + + + + + + + Well known text representation of coordinate reference systems + 12-063r5 + 12-063r5 + + + Roger Lott + This Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2007 and ISO 19111-2:2009. It extends the earlier WKT to allow for the description of coordinate operations. This International Standard defines the structure and content of well-known text strings. It does not prescribe how implementations should read or write these strings. +The jointly developed draft has also been submitted by ISO TC211 for publication as an International Standard document. The version incorporates comments made during both the OGC Public Comment Period as well as the ISO ballot for DIS (ISO TC211 document N3750). + + 2015-05-01 - - OWS-6 Common CBRN Sensor Interface (CCSI)-Sensor Web Enablement (SWE) Engineering Report - Scott Fairgrieve - + Geographic information — Well known text representation of coordinate reference systems + + + - - 14-039 - Testbed 10 Aviation Human Factor Based Portrayal of Digital NOTAMs ER - This activity is part of OGC Testbed 10. The aviation thread was focused on developing and demonstrating the use of the Aeronautical Information Exchange Model (AIXM) and the Flight Information Exchange Model (FIXM), building on the work accomplished in prior testbeds to advance the applications of OGC Web Services standards in next generation air traffic management systems to support European and US aviation modernization programs. -This document provides the result of the Testbed 10 to assess the compliance between the OGC standards and the guidelines provided by the SAE in their latest published document regarding portraying of NOTAMs. Specifically, the Human Based Portrayal of DNOTAM work attempts to fulfill the high level requirements identified in the OGC Testbed-10 RFQ Annex B . -The purpose of this investigation was to analyze the recommendations of the SAE comity and to evaluate the feasibility of their application using OGC standards for portraying, namely the Symbology Encoding standard, version 1.1. + + + + + 15-018r2 + 15-018r2 + WaterML2.0: part 2 - Ratings, Gaugings and Sections + + OGC WaterML2.0: part 2 - Ratings, Gaugings and Sections + This standard defines an information model and XML encoding for exchanging the +following three hydrological information resources: +1. Conversion tables, or conversion curves, that are used for the conversion of +related hydrological phenomenon. +2. Gauging observations – the observations performed to develop conversion table +relationships. +3. Cross sections - survey observations made of the geometric structure of features, +such as river channels, storages etc. +Metadata and vocabularies are defined that together provide a means for parties to +exchange these concepts using common semantics. +This standard is the second part of the WaterML2.0 suite of standards, building on part 1 +that addresses the exchange of time series. + + 2016-02-03 + Peter Taylor + + + + This document describes the requirements, design, technical implementation and technology trialed for the Feature Portrayal service chain used in OWS-7. This includes the interfaces to the OWS Data Services deployed, the feature portrayal servers, the interfaces to clients and the registry information model and interface. + + 10-127r1 + OWS-7 Engineering Report - Aviation Portrayal + 2010-08-18 + Roger Brackin - - - - Thibault Dacla, Daniel Balog - 14-039 - OGC® Testbed 10 Aviation Human Factor Based Portrayal of Digital NOTAMs ER - 2014-07-16 - - - 22-020 - Testbed-18: Identifiers for Reproducible Science Summary Engineering Report - - Paul Churchyard, Ajay Gupta + 10-127r1 + - 2023-01-03 - - Testbed-18: Identifiers for Reproducible Science Summary Engineering Report - - 22-020 - - The OGC’s Testbed 18 initiative explored the following six tasks. - -1.) Advanced Interoperability for Building Energy -2.) Secure Asynchronous Catalogs -3.) Identifiers for Reproducible Science -4.) Moving Features and Sensor Integration -5.) 3D+ Data Standards and Streaming -6.) Machine Learning Training Data -Testbed 18 Task 3, Identifiers for Reproducible Science, explored and developed workflows demonstrating best practices at the intersection of Findable, Accessible, Interoperable, and Reusable (or FAIR) data and reproducible science. - -The workflows developed in this Testbed included: - -the development of a Whole Tail workflow for land cover classification (52 Degrees North); -the development of a reproducible workflow for a deep learning application for target detection (Arizona State University); -the implementation of reproducible workflows following the approach described in the OGC API Process Part 3: Workflows and Chaining for Modular OGC API Workflows (Ecere); -the development of a reproducible workflow that runs an OGC API — Process and Feature Server instance within a Whole Tale environment (GeoLabs); and -the development of a water body detection Application Package to cover the identifier assignment and reproducibility from code to several execution scenarios (local, Exploitation Platform, Whole Tale) (Terradue). -Testbed 18 participants identified considerations and limitations for reproducible workflows and recommendations for future work to identify the benefits of reproducible science for healthcare use cases. - + OWS-7 Engineering Report - Aviation Portrayal - - Paul Scarponcini - Land and Infrastructure Conceptual Model Standard (LandInfra) - 15-111r1 - 2016-12-20 - This OGC Land and Infrastructure Conceptual Model Standard presents the implementation-independent concepts supporting land and civil engineering infrastructure facilities. Conceptual model subject areas include facilities, projects, alignment, road, rail, survey, land features, land division, and wet infrastructure (storm drainage, wastewater, and water distribution systems). The initial release of this standard includes all of these subject areas except wet infrastructure, which is anticipated to be released as a future extension. -This standard assumes the reader has a basic understanding of surveying and civil engineering concepts. - - - 15-111r1 - - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Documents of type Public Engineering Report + Documents of type Public Engineering Report - OGC® Land and Infrastructure Conceptual Model Standard (LandInfra) - - + + Documents of type Public Engineering Report - - - - - OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding - Catalogue Services 3.0 Specification - HTTP Protocol Binding - 12-176r7 - 12-176r7 - - 2016-06-10 - This document specifies the HTTP profile of the CSW General Model part (see OGC 12- -168r6). The General Model specifies the abstract interfaces between clients and catalogue -services. This standard specifies the mappingof the Catalogue abstract model interface -into the HTTP protocol binding. -In this HTTP protocol binding, operation requests and responses are sent between clients -and servers using the HTTP GET and/or HTTP POST methods. Two equivalent request -encodings are defined in this standard. The first using keyword-value pairs (KVP) -which is suitable for use with the HTTP GET method. The second using XML which is -suitable for use with the HTTP POST method. -This standard defines operations that allow a client to get a service description document -for the catalogue (i.e. GetCapabilities); operations that allow a client to, at runtime, -interrogate the service about the kinds of data available (i.e. GetDomain); operations that -allow a client to retrieve records from the catalogue (i.e. GetRecordById and -GetRecords); operations that allow a client to add, modify and remove records from the -catalogue service (i.e. Transaction, Harvest, UnHarvest). - Doug Nebert, Uwe Voges, Panagiotis Vretanos, Lorenzo Bigagli, Bruce Westcott - + + One of the primary requirements for the OGC Testbed-17 Features and Geometries JSON task is to define an extension or profile of GeoJSON that supports encoding spatiotemporal data in Coordinate Reference Systems (CRS) other than the GeoJSON default of the World Geodetic System 1984 (WGS 84) datum, with longitude and latitude units of decimal degrees (CRS84). + +This OGC Testbed 17 (TB17) Engineering Report (ER) presents the various alternatives considered for declaring CRS information in a Features and Geometries JSON (JSON-FG) file. JSON-FG is an OGC extension to GeoJSON that, among other things, adds support of coordinate reference systems other than the CRS84 default. One of the alternatives was selected to be the mechanism for declaring CRS information in a JSON-FG document and is fully described in the “OGC Testbed-17: OGC Features and Geometries JSON Engineering Report” (OGC 21-017r1). + +This ER was submitted to the OGC Features and Geometries JSON Standards Working Group so that the work in TB17 can inform their task of developing and documenting a Features and Geometries JSON standard. + + 21-018 + Features and Geometries JSON CRS Analysis of Alternatives Engineering Report + + + Panagiotis (Peter) A. Vretanos + 21-018 + 2022-02-08 + OGC Testbed-17: Features and Geometries JSON CRS Analysis of Alternatives Engineering Report + + - - + + 16-010r4 + Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2 + - 2008-09-12 - OWS 5 Engineering Report: Supporting Georeferenceable Imagery - The scope of this document is to capture considerations and recommendations on approaches for supporting georeferenceable imagery within the OGC encodings and web services. Georeferenceable imagery is typically imagery coming from a remote sensor that has not been previously geo-rectified, resampled, or regridded. Georeferenceable imagery must be accompanied with information sufficient to allow georectification of the imagery. + + This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store. +Please note that the term “lineal” has been replaced with the term “line” or “linear” throughout this document +Please note that the term “areal” has been replaced with the term “polygon” throughout this document. - 08-071 - - - - Mike Botts - OWS 5 Engineering Report: Supporting Georeferenceable Imagery - 08-071 - + + Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2 + 16-010r4 + + 2018-12-19 + + Carl Reed - + + OWS-7 Motion Video Change Detection + 10-036r2 - 11-058r1 - *FL Starfish Fungus Language for Sensor Description + 2010-08-18 - 2011-07-08 - Ingo Simonis, Chrsitian Malewski - *FL Starfish Fungus Language for Sensor Description - - 11-058r1 - - - The Starfish Fungus Language was developed in response to the high number of complaints addressing issues with the OGC standard Sensor Model Language, SensorML. Most complaints circled around the high flexibility of the language in combination with unnecessary abstractions of technical terms, e.g. every sensor is not a sensor but a process. Most beginners struggled with the composite pattern of those processes, as there is no well-defined rule what needs to be described where. As a beginner, it is almost impossible to write a simple sensor description without getting major guidance through the SensorML development team or other experts. - - - Indoor Mapping and Navigation Pilot Engineering Report - 18-089 - 2019-10-23 + This Engineering Report documents the development effort to build a Web Processing Service (WPS) to perform a change detection algorithm on two motion video streams. It will examine the WPS Motion Video Change Detection architecture from various viewpoints in order to describe its purpose, data models, functional decomposition, and interaction between distinct computational components. + Stan Tillman + OWS-7 Motion Video Change Detection + + 10-036r2 - - Charles Chen - OGC Indoor Mapping and Navigation Pilot Engineering Report - + + + + OGC Filter Encoding 2.0 Encoding Standard - With Corrigendum + 09-026r2 + 2014-08-18 + - The OGC Indoor Mapping and Navigation Pilot Initiative was sponsored by the National Institute of Standards and Technology (NIST) Public Safety Communications Research (PSCR) Division. This initiative addressed key challenges related to indoor mapping and navigation for the purpose of supporting first responders in fields such as fire-fighting. The focus of this initiative was on developing the capabilities and workflows required for pre-planning operations. This included scanning each building to produce a point cloud dataset and converting this source data into various intermediate forms to support the generation of indoor navigation routes. This Engineering Report (ER) describes the work conducted in this initiative, the lessons learned captured by participants, and future recommendations to support the public safety efforts and interoperability of the standards. It is expected that future OGC initiatives will address the real-time, event-driven aspects of indoor mapping and navigation for first response situations. + + Filter Encoding 2.0 Encoding Standard - With Corrigendum + 09-026r2 + A fundamental operation performed on a set of data or resources is that of querying in order to obtain a subset of the data which contains certain desired information that satisfies some query criteria and which is also, perhaps, sorted in some specified manner. -First responders typically survey high-risk facilities in their jurisdiction at least once per year as part of a pre-planning process. Pre-planning outputs are often in the form of reports, and first responders may generate their own hand-drawn maps during the process or annotate available floor plans (e.g., from computer-aided design models). Pre-planning is time-consuming, inefficient, and inherently complex considering the information and level of detail that should or could be captured, the lack of automation, and the difficulty identifying notable changes to facilities and infrastructure during successive pre-planning surveys. +This International Standard defines an abstract component, named AbstractQueryExpression, from which other specifications can subclass concrete query elements to implement query operations. This International Standard also defines an additional abstract query component, named AbstractAdhocQueryExpresison, which is derived from AbstractQueryExpression and from which other specifications can subclass concrete query elements which follow a query pattern composed of a list of resource types to query, a projection clause specifying the properties of those resources to present in the result, a projection clause composed of predicates that define the subset of resources or data in the result set and a sorting clause indicating to order in which the results should be presented. This pattern is referred to as an ad hoc query pattern since the server is not aware of the query until it is submitted for processing. This is in contrast to a stored query expression, which is stored and can be invoked by name or identifier. -Mobile three-dimensional (3D) Light Detection and Ranging (LiDAR) has been identified as a potentially transformational technology for first responders. Using LiDAR and 360-degree camera imagery, coupled with advanced software processing, first responders could efficiently capture 3D point clouds and a wealth of other information, both observed and derived, while walking through buildings as part of routine pre-planning operations. The use of 3D LiDAR and imagery has many potential upsides beyond just creating point clouds for visualization and mapping (e.g., use in localization, object classification, integration with virtual/augmented reality solutions, change detection, etc.). - 18-089 - - +This International Standard describes an XML and KVP encoding of a system-neutral syntax for expressing the projection, selection and sorting clauses of a query expression. The intent is that this neutral representation can be easly validated, parsed and then translated into some target query language such as SPARQL or SQL for processing. + + + Panagiotis (Peter) A. Vretanos + - - Carl Reed - This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features. - - - 16-070r3 - 2018-12-19 - - - - 16-070r3 - Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage - - Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - This engineering report examines the role of geospatial semantic technology in the domain of civil aviation. Many aeronautical services (providing information on request or processing the data) are based on OGC Web Service specifications. A number of aeronautical services possess geospatial attributes. The aviation services follow OWS Common Service requirements but also have domain specific capabilities. Services metadata is often very relevant for service consumption, especially in the SOA environment of aviation’s System Wide Information Management (SWIM). Therefore, it shall be exposed to consumer stakeholders for either design or runtime service discovery in an efficient, standardized way. + + + OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension with Corrigendum + Eric Hirschorn + 16-083r3 + Coverage Implementation Schema - ReferenceableGridCoverage Extension with Corrigendum + + 16-083r3 + + The OGC GML Application Schema - Coverages (“GMLCOV”) version 1.0 [OGC 09-146r2], recently renamed the OGC Coverage Implementation Schema version 1.0, provides a ReferenceableGridCoverage element for representing coverages on a referenceable grid. However, GMLCOV provides no instantiable subtypes of a critical sub-element of ReferenceableGridCoverage, GMLCOV::AbstractReferenceableGrid. To make use of ReferenceableGridCoverage, an extension deriving from GMLCOV would need to be developed. GML 3.3 is not such an extension of GMLCOV, as it is built independently from GMLCOV. Use of the instantiable referenceable grid elements of GML 3.3 with ReferenceableGridCoverage violates Requirement 14 of GMLCOV 1.0 and Requirement 24 of the OGC Modular Specification[1]. -This ER starts introducing the WSDOM service ontology developed by FAA for semantic service discovery. It proposes several extensions useful for OWS compatible, geospatial aviation services. It combines GeoSPARQL with WSDOM ontology and FAA service classification taxonomies and elaborates the interoperability between ontology based WSDOM and OWS compatible service descriptions. - - Testbed-12 Aviation Semantics Engineering Report - 16-039r2 - - +This OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension provides a set of referenceable grid elements for use as sub-elements of ReferenceableGridCoverage. Three of these elements have been adapted from GML 3.3, while a fourth emerged from work on a Testbed-11 Engineering Report[2]. + 2019-01-20 - 2017-06-19 - Testbed-12 Aviation Semantics Engineering Report - - Aleksandar Balaban - - 16-039r2 - - - 13-084r2 - 13-084r2 - I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0 - OGC I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0 - Uwe Voges, Frédéric Houbie, Nicolas Lesage, Marie-Lise Vautier - The OGC Catalogue Services 2.0 specification (OGC 07-006r1) establishes a general framework for implementing catalogue services that can be applied to meet the needs of stakeholders in a wide variety of domains. -The ebRIM application profile (OGC 07-110r4) is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0 specification; it qualifies as a ‘Class 2’ profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards. The ebRIM application profile also includes a Basic extension package (OGC 07-144r4) of the OASIS ebXML Registry Information Model (ebRIM) providing artefacts of general utility in the geomatics domain. -This document provides an extension package aligned with the ebRIM application profile of CS-W for the cataloguing of ISO 19115, ISO19115-2 and ISO 19119 compliant metadata. It was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [HMA] and related projects. Some input came from the OGC OWS9 initiative. -This document supersedes the former document OGC Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W, OGC 07-038r3 (Version: 0.1.12). - - - - - - 2014-04-28 - - OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform. - + - - 03-006r3 - - Marwa Mabrouk - - OpenGIS Location Services (OpenLS): Core Services [Parts 1-5] - - 03-006r3 - Location Services (OpenLS): Core Services [Parts 1-5] - 2004-01-16 - - - 15-074r2 - 15-074r2 - Spatial Data on the Web Use Cases & Requirements - - Spatial Data on the Web Use Cases & Requirements - - 2016-10-25 - + + Image CRSs for IH4DS + - Frans Knibbe, Alejandro Llaves - This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC. + 05-014 + Image CRSs for IH4DS + 2005-01-31 + This Discussion Paper specifies image coordinate reference system (CRS) definitions designed for possible use by WCTS and WCS servers and clients, initially in the IH4DS thread of the OWS 2 interoperability initiative. This report specifies image CRS definitions suitable for both ungeorectified and georectified images, where an ungeorectified image can be georeferenced or not. + Arliss Whiteside + 05-014 - - 2020-01-21 - - 19-040 - WPS Routing API ER - WPS Routing API ER - Christian Autermann + + + + Aviation Engineering Report + 20-020 - - - 19-040 - The goal of this OGC WPS Routing API Engineering Report (ER) is to document the specification of an Application Programming Interface (API) which supports geographic routing. The specification includes two alternative approaches to such an API, one based on the current draft of the OGC API - Processes draft specification and another based on the OGC API principles (and the OGC API - Common draft specification). Both approaches facilitate a common Route Exchange Model. + 2021-01-13 + This Testbed-16 Aviation Engineering Report (ER) summarizes the implementations, findings and recommendations that emerged from the efforts of further advancing interoperability and usage of Linked Data within the Federal Aviation Administration (FAA) System Wide Information Management (SWIM) context. The goal of this effort was to experiment with OpenAPI and Linked Data to explore new ways for locating and retrieving SWIM data in order to enable consumers to consume SWIM data more easily in their business applications, and enable the discovery of additional relevant information for their needs. + +Specifically, this ER documents the possibility of querying and accessing data (and its metadata) using Semantic Web Technologies as well as interlinking heterogeneous semantic data sources available on the Web. Together with an analysis on the potential for using OpenAPI-based Application Programming Interface (API) definitions to simplify access to geospatial information, an exploration of solutions for data distribution that complement those currently used by SWIM is presented. + 20-020 + + Sergio Taleisnik + OGC Testbed-16: Aviation Engineering Report - - 21-027 + + - OGC Testbed-17: Geo Data Cube API Engineering Report - Jérôme Jacovella-St-Louis - OGC Testbed-17: Geo Data Cube API Engineering Report - 21-027 - - This OGC Testbed 17 Engineering Report (ER) documents the results and recommendations of the Geo Data Cube API task. The ER defines a draft specification for an interoperable Geo Data Cube (GDC) API leveraging OGC API building blocks, details implementation of the draft API, and explores various aspects including data retrieval and discovery, cloud computing and Machine Learning. Implementations of the draft GDC API are demonstrated with use cases including the integration of terrestrial and marine elevation data and forestry information for Canadian wetlands. - - - - 2022-04-08 - + 2021-01-06 + 20-025r1 + Data Access and Processing API Engineering Report + Luis Bermudez - - - The OGC Disaster Pilot 2021 initiative brought differing technologies together through multiple participants, allowing the future development of a robust solution with no single-point weaknesses. This Guide supports data providers in preparing and coordinating with others to leverage standards-based cloud computing platforms to support disaster management and response efforts. Geospatial data is acquired from multiple sources, including Earth Observation satellites, and converted to Decision Ready Information and indicators (DRI) from Analysis Ready Data and datasets (ARD) alongside recipes. - - - OGC Disaster Pilot: User Readiness Guide - 2022-05-06 - - - OGC Disaster Pilot: User Readiness Guide - 21-074 - Samantha Lavender, Andrew Lavender - - 21-074 + OGC Testbed-16: Data Access and Processing API Engineering Report + This OGC Testbed 16 Engineering Report documents the advancement of an OGC Data Access and Processing API (DAPA). + + 20-025r1 - + + - 2024-04-26 - Eugene Yu, Liping Di - OGC Testbed 19 High Performance Geospatial Computing Engineering Report - - Large-scale geospatial analytical computation is critically needed for tackling a wide range of sustainability problems, such as climate change, disaster management, and food and water security. However, such computation often requires high-performance computing (HPC) resources that are not easily accessible or usable by geospatial researchers and practitioners from various domains. To address this challenge, there is a need for developing and standardizing tools and interfaces that can bridge the gap between user frontend and HPC backends and enable effective and efficient use of High-Performance Geospatial Computing (HPGC) resources for geospatial analytics. - -This OGC Testbed 19 Engineering Report (ER) presents the results of a testbed task that: - -* evaluated previous and current work in the application of HPC for geospatial analytics, and -* developed draft standards for HPGC resource definitions and processing interfaces. - -This ER provides an overview of the Testbed 19 motivation, objectives, scope, and methodology, as well as a summary of the main findings, recommendations, and future work directions. - -CyberGIS-Compute is reviewed and used as a reference to develop the HPGC API. “CyberGIS-Compute is an open-sourced geospatial middleware framework that provides integrated access to high-performance computing (HPC) resources through a Python-based SDK and core middleware services.”<<CyberGIS_definition>> The OGC API - Processes<<api_processes>> is adopted as the base API for standardizing and developing the HPGC API. A Python client library is developed to demonstrate the process of client generation by leveraging the OpenAPI client stub/model automatic generation capability<<openapi_generator>>. Typical use cases and scenarios are demonstrated and scripted in Jupyter Notebooks. - 23-044 - 23-044 - OGC Testbed 19 High Performance Geospatial Computing Engineering Report + Authentication IE Enginerring Report + 10-192 + + 10-192 + + 2011-01-03 + + Results of the Auth IE are presented in this Engineering Report document and serve as guidance to both implementers and organizations deploying solutions that involve basic authentication. It is the belief of the Auth IE participants that if such a document is made available to the community more OGC implementing products will natively support authentication. + + Jeff Harrison + Authentication IE Enginerring Report + + + + + 07-063 + Web Map Services - Application Profile for EO Products + + This OGC document specifies a constrained, consistent interpretation of the WMS specification that is applicable to government, academic and commercial providers of EO products. + Thomas H.G. Lankester + 2007-08-15 + Web Map Services - Application Profile for EO Products + 07-063 - - - GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile - 16-060r2 - Daniel Lee - - - - - This OGC standard is a profile of the OGC GML Application Schema - Coverages version 1.0 [OC 09-146r2]. That document was renamed OGC Coverage Implementation Schema (CIS) for clarification in version 1.1. This standard specifies the usage of the GRIB2 data format for the encoding of OGC coverages. The GRIB2 specification is maintained by the World Meteorological Organization (WMO) and is the standard encoding for the exchange and storage of general regularly distributed information expressed in binary form. - - - 16-060r2 - OGC GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile - 2018-11-27 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - - OGC API - Environmental Data Retrieval Standard - The OGC API — Environmental Data Retrieval (EDR) standard provides a family of lightweight query interfaces to access spatiotemporal data resources by requesting data at a Position, within an Area, along a Trajectory or through a Corridor. A spatio-temporal data resource is a collection of spatio-temporal data that can be sampled using the EDR query pattern geometries. These patterns are described in the section describing the Core Requirements Class. - -The goals of the EDR Application Programming Interface (API) that is specified by this standard are to: - -Make it easier to access a wide range of data through a uniform, well-defined simple Web interface; - -To achieve data reduction to just the data needed by the user or client while hiding much of the data storage complexity. - -A major use case for the EDR API is to retrieve small subsets from large collections of environmental data, such as weather forecasts, though many other types of data can be accessed. The important aspect is that the requested data can be unambiguously specified by spatio-temporal coordinates. - -The EDR API query patterns — Position, Area, Cube, Trajectory or Corridor — can be thought of as discrete sampling geometries, conceptually consistent with the feature of interest in the Sensor Observation Service (SOS) standard. A typical data resource accessed by an EDR API instance is a multidimensional dataset that could be accessed via an implementation of the Web Coverage Service (WCS) standard. In contrast to SOS and WCS, the EDR API is fully consistent with the patterns of the OGC API family of standards and aims to provide a single set of simple-to-use query patterns. Use cases for EDR range from real or virtual time-series observation retrievals, to sub-setting 4-dimensional data cubes along user-supplied sampling geometries. These query patterns do not attempt to satisfy the full scope of either SOS or WCS, but instead provide useful building blocks to enable the composition of APIs that satisfy a wide range of geospatial data use cases. By defining a small set of query patterns (and no requirement to implement all of them), the EDR API should help to simplify the design of systems (as they can be performance tuned for the supported queries) making it easier to build robust and scalable infrastructures. - -With the OGC API family of standards, the OGC community has extended its suite of standards to include Resource Oriented Architectures and Web Application Programming Interfaces (APIs). These standards are based on a shared foundation, specified in OGC API-Common, which defines the resources and access paths that are supported by all OGC APIs. The resources are listed in Table 1. This document extends that foundation to define the EDR API. - OGC API - Environmental Data Retrieval Standard - 19-086r6 - Mark Burgoyne, David Blodgett, Charles Heazel, Chris Little - - 2023-07-27 + + Incident Management Information Sharing Internet of Things Protocol Mapping Engineering Report + 16-093r1 + 2018-04-26 + + Steve Liang, Tania Khalafbeigi + 16-093r1 + Incident Management Information Sharing Internet of Things Protocol Mapping Engineering Report + This engineering report details Pilot experiences in connecting a variety of local communications protocols and message formats supported by low-cost sensor devices with OGC SWE Web services published globally over IP networks. It describes the Sensor Hub approach taken to support these connections and the mappings from one protocol to another required to develop integrated SWE-IoT networks. + + - - 19-086r6 - - - - - 2010-09-08 - User Management for Earth Observation Services + - - User Management for Earth Observation Services - 07-118r8 - - - This document describes how user and identity management information may be included in the protocol specifications for OGC Services. The use cases addressed will make reference to EO (Earth Observation) services, for example catalogue access (EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 [OGC 06-131]), ordering (Ordering Services for Earth Observation Products [OGC 06-141r2]) and programming (OpenGIS Sensor Planning Service Application Profile for EO Sensors [OGC 07-018r2]). - P Denis - 07-118r8 - - - 16-004r4 - Volume 5: OGC CDB Radar Cross Section (RCS) Models - Volume 5: OGC CDB Radar Cross Section (RCS) Models - Carl Reed - 2018-12-19 - - This CDB volume provides all of the information required to store Radar Cross Section (RCS) data within a conformant CDB data store. -Please note that the current CDB standard only provides encoding rules for using Esri ShapeFiles for storing RCS models. However, this Best Practice has been modified to change most of the ShapeFile references to “vector data sets” or “vector attributes” and “Point Shapes” to “Point geometries”. This was done in recognition that future versions of the CDB standard and related Best Practices will provide guidance on using other encodings/formats, such as OGC GML. - - - - - - 16-004r4 - - - Nicholas J. Car - 22-047r1 - OGC GeoSPARQL - A Geographic Query Language for RDF Data - - - GeoSPARQL contains a small spatial domain OWL ontology that allow literal representations of geometries to be associated with spatial features and for features to be associated with other features using spatial relations. - -GeoSPARQL also contains SPARQL extension function definitions that can be used to calculate relations between spatial objects. - -Several other supporting assets are also contained within GeoSPARQL such as vocabularies of Simple Feature types and data validators. - -The namespace for the GeoSPARQL ontology is http://www.opengis.net/ont/geosparql# - -The suggested prefix for this namespace is geo - -The namespace for the GeoSPARQL functions is http://www.opengis.net/def/function/geosparql/ - -The suggested prefix for this namespace is geof - + Jeff Harrison + 17-038 + The objective of the Fit for Purpose (FFP) effort in Testbed 13 was to develop and test filters and encodings in a platform that can ease the work of end-users, especially those who are not expert in dealing with geospatial data and satellite imagery. The platform was demonstrated in a scenario that showed how these filters can enable information exchange for humanitarian relief and analysis of mass movement of populations. - - 22-047r1 - - - - 2024-01-29 - OGC GeoSPARQL - A Geographic Query Language for RDF Data - - - - - Summary of the OGC Web Services, Phase 8 (OWS-8) Interoperability Testbed - 11-139r2 - Summary of the OGC Web Services, Phase 8 (OWS-8) Interoperability Testbed - 11-139r2 - The OGC Web Services, Phase 8 (OWS-8) Testbed was an initiative of OGC’s Interoperability Program to -collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. The majority of work for -OWS-8 was conducted from March to September 2011. +This section provides a summary of the interoperability tools and practices used by Testbed 13 participants in this platform. It includes descriptions and testing results of filters and encodings to help simplify access to satellite imagery. This technology was tested in a scenario that showed how OGC-based services, encodings, filters and applications can help coordinate humanitarian relief activities among nations and organizations. + Testbed-13: Fit-for-Purpose Engineering Report + 17-038 + OGC Testbed-13: Fit-for-Purpose Engineering Report + - 2011-12-19 - - David Arctur - - + + 2018-01-18 - - - - 18-000 - - 2019-05-08 - Jeff Yutzler - 18-000 - GeoPackage Related Tables Extension - OGC GeoPackage Related Tables Extension - - A GeoPackage [geopackage] is a platform-independent SQLite [sqlite] database file that contains GeoPackage data and metadata tables. GeoPackages, as described by the GeoPackage Encoding Standard [GPKG1_2] are designed to be extensible, including support for additional data types. This document defines the Related Tables Extension (RTE) for the GeoPackage Encoding Standard. - -The RTE defines the rules and requirements for creating relationships in a GeoPackage data store between geospatial data tables and other tables that contain or reference related content such as attributes or media. Geospatial data tables (such as features or tiles tables) contain location information and/or geometries. There are many examples of where the RTE can be used including relating parcel (land lot) features to pictures of that parcel or linking census boundaries to the related demographic census data. - + + + + + + + + + + + + + + + + + Documents of type Candidate Specification + Documents of type Candidate Specification + Documents of type Candidate Specification - - 17-007r1 - Web Services Security - 17-007r1 - - - This standard applies to a deployed OGC Web Service instance for which the protocol scheme of all operation endpoint URLs, exposed in the Capabilities document, is ‘https’ as defined in RFC 7230, section 2.7.2. - -A security-annotated Capabilities document is one which uses the <Constraint> element(s) to express the existence of security controls on the operation of the service instance or support for a particular security feature. Applying the tests as defined in the Annexes can validate compliance for a service, the client and the OGC management process. Basically, a service can be described by a Capabilities document that includes security annotations as defined in this standard. A client loading these Capabilities and parse for the <Constraint> element(s) can determine the security controls implemented for each operation of the service instance. The string value of this element’s name attribute contains the identifier of the implemented requirements class. - -How the client obtains the security-annotated capabilities is out of scope for this standard. + + 2018-12-20 + The Earth Observation Exploitation Platform Hackathon 2018 was conducted to evaluate the standards based architecture for deploying and executing arbitrary applications close to the physical location of the data in heterogeneous cloud environments. The Hackathon was very successful in demonstrating both efficiency and sustainability of the architecture developed in Testbed-13. Efficient, because it was possible to setup the full execution workflow of 128 Sentinel-1 images within the 1.5 days of the Hackathon in a multi-vendor environment. Sustainable, because the architectural approach provides sufficient flexibility to cater for possible extensions and exchange of cloud & container middleware. -This standard defines one common abstract Requirements Class and three Capabilities document structure specific Requirements Classes. The structure specific classes address how the requirements are implemented for WMS 1.1.1, WMS 1.3 and OWS Common based service Capabilities documents. +The Hackathon produced a number of suggestions for future work items. These include new tools to facilitate the process of Application Package generation to make it even simpler for scientists to bring their applications to the market; a more detailed specification to further improve the level of interoperability; and a best practice document with lots of examples that illustrate the necessary steps to make applications available. - - - 2019-01-28 - Andreas Matheus - OGC Web Services Security - - - - - - - <p>The purpose of the Open Modelling Interface (OpenMI) is to enable the runtime exchange of data between process simulation models and also between models and other modelling tools such as databases and analytical and visualization applications. Its creation has been driven by the need to understand how processes interact and to predict the likely outcomes of those interactions under given conditions. A key design aim has been to bring about interoperability between independently developed modelling components, where those components may originate from any discipline or supplier. The ultimate aim is to transform integrated modelling into an operational tool accessible to all and so open up the potential opportunities created by integrated modelling for innovation and wealth creation. -</p> -<p> -This document defines the requirements that a component must meet to achieve OpenMI compliance. These comprise: 1) a very thin core set of requirements covering the information and functions needed to establish a link and make an exchange between two components and 2) a set of optional extensions for handling more complex situations. The document does not describe how to implement the standard. This information together with a range of software tools for creating and running OpenMI-­&#8208;compliant components are provided by the OpenMI Association and third-­&#8208;party software vendors – visit www.openmi.org for further documentation.</p> -<p> -<a href=https://portal.ogc.org/files/?artifact_id=59022>pdf</a> <br> -<a href=https://portal.ogc.org/files/?artifact_id=59022&format=docx>docx</a> -</p> +Hackathon participants highlighted that such a level of robustness, flexibility, and maturity of the application-to-the-cloud architecture has been developed in nine months only during Testbed-13. The participants recommend to continue interlacing major OGC Innovation Program activities, such as testbeds, with short term rapid prototyping initiatives such as hackathons. Almost all participants of the Hackathon had been new to the OGC Innovation Program. These participants emphasized that the Hackathon provided an outstanding opportunity for newcomers to get quickly familiar with the latest standardization efforts and helped tremendously in understanding investments and new market opportunities for applications-in-the-cloud. + + 18-046 + + + Earth Observation Exploitation Platform Hackathon 2018 Engineering Report + 18-046 - OGC Open Modelling Interface Interface Standard - 11-014r3 - 11-014r3 - Open Modelling Interface Interface Standard - - 2014-05-26 - - + + Ingo Simonis - Stanislav Vanecek, Roger Moore + OGC Earth Observation Exploitation Platform Hackathon 2018 Engineering Report - - - Stan Tillman, Jody Garnett - - OWS Integrated Client (GeoDSS Client) - 05-116 - 2007-03-08 - - 05-116 - + + OGC Underground Infrastructure Concept Study Engineering Report + Josh Lieberman, Andy Ryan + + 17-048 + Underground Infrastructure Concept Study Engineering Report + This report documents the progress made to date by OGC and its members to build a complete picture of the present situation and develop a conceptual framework for action to improve underground infrastructure data interoperability. The report also identifies the most important steps to be taken next in order to develop the necessary data standards and foster their adoption. + + + 2017-08-31 + - This Interoperability Program Report (IPR) provides an overview of the general requirements, architecture, and design considerations of - OWS Integrated Client (GeoDSS Client) - + + 17-048 - - - - - - Peter Baumann, Eric Hirschorn, Joan Masó - Coverage Implementation Schema with Corrigendum - 09-146r8 - 2019-10-28 - OGC Coverage Implementation Schema with Corrigendum - Coverages represent homogeneous collections of values located in space/time, such as spatio-temporal sensor, image, simulation, and statistics data. Common examples include 1-D timeseries, 2-D imagery, 3-D x/y/t image timeseries and x/y/z geophysical voxel models, as well as 4-D x/y/z/t climate and ocean data. Generally, coverages encompass multi-dimen­sional regular and irregular grids, point clouds, and general meshes. + + 2017-09-23 + 2019-07-10 + Armin Haller, Krzysztof Janowicz, Simon Cox, Danh Le Phuoc, Kerry Taylor, Maxime Lefrançois + + + The Semantic Sensor Network (SSN) ontology is an ontology for describing sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties, as well as actuators. SSN follows a horizontal and vertical modularization architecture by including a lightweight but self-contained core ontology called SOSA (Sensor, Observation, Sample, and Actuator) for its elementary classes and properties. With their different scope and different degrees of axiomatization, SSN and SOSA are able to support a wide range of applications and use cases, including satellite imagery, large-scale scientific monitoring, industrial and household infrastructures, social sensing, citizen science, observation-driven ontology engineering, and the Web of Things. Both ontologies are described below, and examples of their usage are given. + The Semantic Sensor Network (SSN) ontology is an ontology for describing sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties, as well as actuators. SSN follows a horizontal and vertical modularization architecture by including a lightweight but self-contained core ontology called SOSA (Sensor, Observation, Sample, and Actuator) for its elementary classes and properties. With their different scope and different degrees of axiomatization, SSN and SOSA are able to support a wide range of applications and use cases, including satellite imagery, large-scale scientific monitoring, industrial and household infrastructures, social sensing, citizen science, observation-driven ontology engineering, and the Web of Things. Both ontologies are described below, and examples of their usage are given. -This Coverage Implementation Schema (CIS) specifies the OGC coverage model by establishing a concrete, interoperable, conformance-testable coverage structure. It is based on the abstract concepts of OGC Abstract Topic 6 [1] (which is identical to ISO 19123) which spec­i­fies an abstract model which is not per se interoperable – in other words, many different and incompatible implementations of the abstract model are possible. CIS, on the other hand, is interoperable in the sense that coverages can be conformance tested, regardless of their data format encoding, down to the level of single “pixels” or “voxels.” +The namespace for SSN terms is http://www.w3.org/ns/ssn/. +The namespace for SOSA terms is http://www.w3.org/ns/sosa/. -Coverages can be encoded in any suitable format (such as GML, JSON, GeoTIFF, or Net­CDF) and can be partitioned, e.g., for a time-interleaved representation. Coverages are independent from service definitions and, therefore, can be accessed through a variety of OGC services types, such as the Web Coverage Service (WCS) Standard [8]. The coverage structure can serve a wide range of coverage application domains, thereby contributing to harmon­ization and interoperability between and across these domains. - +The suggested prefix for the SSN namespace is ssn. +The suggested prefix for the SOSA namespace is sosa. + +The SSN ontology is available at http://www.w3.org/ns/ssn/. +The SOSA ontology is available at http://www.w3.org/ns/sosa/. + 16-079 - 09-146r8 - - - 01-009 - The OpenGIS® Coordinate Transformation Service Standard (CTS) provides a standard way for software to specify and access coordinate transformation services for use on specified spatial data. This standard addresses a key requirement for overlaying views of geodata (“maps”) from diverse sources: the ability to perform coordinate transformation in such a way that all spatial data are defined relative to the same spatial reference system. - - 01-009 - Coordinate Transformation Service Implementation Specification - - OpenGIS Coordinate Transformation Service Implementation Specification - - 2001-01-12 + Semantic Sensor Network Ontology + - Martin Daly - - - 15-078r6 - SensorThings API Part 1: Sensing - 15-078r6 - OGC SensorThings API Part 1: Sensing - - + 16-079 + Semantic Sensor Network Ontology - - - The OGC SensorThings API provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the Web. At a high level the OGC SensorThings API provides two main functionalities and each function is handled by a part. The two parts are the Sensing part and the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. The Tasking part is planned as a future work activity and will be defined in a separate document as the Part II of the SensorThings API. - 2016-07-26 - Steve Liang, Chih-Yuan Huang, Tania Khalafbeigi - - - - This OGC Discussion Paper details the user requirements for metadata in the aviation domain. The requirements are at a high-level. - - - 2011-03-28 - OGC Aviation Domain Working Group - 10-195 - Requirements for Aviation Metadata - - - - 10-195 - Requirements for Aviation Metadata - - OWS-2 Application Schema Development - - - + + Uwe Voges, Kristian Senkler + + 07-045 + + This document specifies an application profile for ISO 19115/ISO 19119 metadata with support for XML encoding per ISO/TS19139 and HTTP protocol binding. It relies on requirements coming from the CSW 2.0.2 specification (OGC document 07-006). + + 2007-08-07 + ISO Metadata Application Profile + 07-045 + OpenGIS Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile - 04-100 - OWS-2 Application Schema Development - 04-100 - Clemens Portele - 2005-04-13 - - The OWS-2 Application Schema Development Discussion Paper describes the process for creating ISO 19109:2005 Application Schemas [http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=39891] in UML. It also describes the process used during the OWS-2 Initiative [http://www.opengeospatial.org/projects/initiatives/ows-2] for creating GML [http://www.opengeospatial.org/standards/gml] Application Schemas from ISO 19109:2005 Application Schemas. - -See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml . - + - + + 04-040 + Style Management Services for Emergency Mapping Symbology + Style Management Services for Emergency Mapping Symbology + 2005-02-17 + - 2019-11-25 - Jeff Yutzler - The Open Geospatial Consortium (OGC) GeoPackage Encoding Standard was developed for the purpose of providing an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information. GeoPackage has proven to be an effective container mechanism for bundling and sharing geospatial data for a variety of operational use cases. However, GeoPackage stakeholders have observed persistent interoperability issues, particularly with regards to metadata, extensions, and portrayal. - -This paper presents the operational need, proposed approach, and way ahead for addressing these interoperability issues. Section 6 presents three new enhancements (extensions) that are designed to improve the interoperability of GeoPackages in general and metadata in particular. Section 7 presents a vision for implementing an Open Portrayal Framework in GeoPackage. Annex A presents specifications for all of the GeoPackage extensions proposed in this paper. Annex B presents a JSON schema for the proposed encoding for application profiles presented in Section 6. In general, the GeoPackage Standards Working Group (SWG) looks to standardize extensions that address a clear use case, have a sound technical approach, and have a commitment to implementation by multiple organizations. As with the GeoPackage Tiled Gridded Coverage Extension and the GeoPackage Related Tables Extension, these new extensions would be tracked as separate documents from the core GeoPackage Encoding Standard. - -The GeoPackage community will benefit from the increased interoperability of operational “mission-ready” GeoPackages that will result from this approach. Additionally, software will be able to quickly determine the validity and utility of a GeoPackage in target operational environments. This will help ensure that GeoPackage production-consumption lifecycles and supporting application tools and services are better aligned with stakeholder missions. - 19-047 - - - Proposed OGC GeoPackage Enhancements - - 19-047 - Proposed OGC GeoPackage Enhancements + + 04-040 + This document describes the proposed system design for the OGC Style Management Service (SMS). +The SMS must manage distinct objects that represent styles and symbols and provide the means to discover, query, insert, update, and delete these objects. +Styles provide the mapping from feature types and feature properties and constraints to parameterized Symbols used in drawing maps. Symbols are bundles of predefined graphical parameters and predefined fixed graphics. + + + Bill Lalonde - + + Martin Kyle, David Burggraf, Sean Forde, Ron Lake + The OpenGIS® GML in JPEG 2000 for Geographic Imagery Encoding Standard defines the means by which the OpenGIS® Geography Markup Language (GML) Standard http://www.opengeospatial.org/standards/gml is used within JPEG 2000 http://www.jpeg.org/jpeg2000/ images for geographic imagery. The standard also provides packaging mechanisms for including GML within JPEG 2000 data files and specific GML application schemas to support the encoding of images within JPEG 2000 data files. JPEG 2000 is a wavelet-based image compression standard that provides the ability to include XML data for description of the image within the JPEG 2000 data file. +See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml . + - 16-114r3 - Moving Features Encoding Extension: netCDF - - - 2018-12-18 - The netCDF Moving Features encoding extension is a summary of conventions that supports efficient exchange of simple moving features as binary files. This Best Practice is a complement to the Moving Features Encoding Part I: XML Core and an alternative to the Simple Comma Separated Values (CSV) extension. Compared to the CSV encoding, this netCDF encoding offers more compact storage and better performance at the cost of additional restrictions on the kinds of features that can be stored. - Martin Desruisseaux - - - OGC Moving Features Encoding Extension: netCDF - 16-114r3 + + 05-047r3 + OpenGIS GML in JPEG 2000 for Geographic Imagery Encoding Specification + + + + 05-047r3 + GML in JPEG 2000 for Geographic Imagery Encoding Specification + 2006-01-20 - - - - - - - - - - - - - - - - - - - Documents of type Release Notes - Documents of type Release Notes - - - Documents of type Release Notes - - - + + Ingo Simonis, Stephane Fellah - - + + + Testbed 10 ontology work focused on: +• A general examination of ontologies in the context of OGC data modeling, handling, and organization. Testbed-10 has started to define a consistent set of ontologies implementing solid theoretical foundations and semantics. +• The definition of a core ontologies for representing incident information used by Incident Management Systems (IMS) and mapping symbologies used in the emergency and disaster management domain with the goal to improve interoperability between different IMS symbology sets used across multi-level jurisdiction. +• Addressed ontology mapping between hydrology feature models using SPARQL and OWL2. + + Testbed 10 Cross Community Interoperability (CCI) Ontology Engineering Report + 14-049 - Testbed 10 Virtual Global Gazetteer Engineering Report - 14-029r2 + 14-049 + OGC® Testbed 10 Cross Community Interoperability (CCI) Ontology Engineering Report 2014-07-16 - Martin Klopfer - 14-029r2 - This document provides a technical description of the Virtual Global Gazetteer implemented for OGC Testbed 10. -The Virtual Global Gazetteer integrates two gazetteers – a copy of the USGS gazetteer containing domestic names and a copy of the NGA gazetteer containing non-domestic names (hosted by Interactive Instruments) and provides the capability to link to additional local gazetteers and linked data information, allowing a user to retrieve extended information on locations selected from either of the initial gazetteers. The access to linked data information provided by these gazetteers was achieved by GeoSPARQL enabling these gazetteers using semantic mapping components - - OGC® Testbed 10 Virtual Global Gazetteer Engineering Report + - - - - - - This document provides the Annexes for the CDB Core: Model and Physical Structure standard. The only exception is Annex A, Abstract Test Suite. The CDB ATS Annex is in Volume 1: Core document. - 16-005r3 - 16-005r3 - Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes - Carl Reed - Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes - 2018-12-19 - + + Paul Scarponcini - - - - 18-084 - Geospatial to the Edge Plugfest Engineering Report - 2019-01-20 - - The Geospatial to the Edge Interoperability Plugfest, co-sponsored by the Army Geospatial Center and the National Geospatial-Intelligence Agency (NGA/CIO&T), brought together technology implementers and data providers to advance the interoperability of geospatial products and services based on profiles of OGC standards. Specifically, servers and data available via GeoPackage, Web Feature Service (WFS), Web Map Service (WMS), and Web Map Tile Service (WMTS), all following National System for Geospatial Intelligence (NSG) profiles, were exercised and improved in various clients. Compliance Tests were executed and advanced based on feedback from the participants. - OGC Geospatial to the Edge Plugfest Engineering Report + - 18-084 - - Luis Bermudez - + 2017-08-16 + + OGC InfraGML 1.0: Part 1 – LandInfra Land Features - Encoding Standard + 16-101r2 + InfraGML 1.0: Part 1 – LandInfra Land Features - Encoding Standard + + This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. +InfraGML is published as a multi-part standard. This Part 1 addresses the LandFeature Requirements Class from LandInfra. + 16-101r2 - - Observations and Measurements - + - 05-087r4 + - - - Observations and Measurements - 05-087r4 - 2006-10-11 - The general models and XML encodings for observations and measurements, including but not restricted to those using sensors. - - Simon Cox + James Tomkins, Dominic Lowe, Paul Hershberg + + 15-042r6 + + + OGC TimeseriesML 1.3 – XML Encoding of the Timeseries Profile of Observations and Measurements + OGC TimeseriesML 1.3 – XML Encoding of the Timeseries Profile of Observations and Measurements + 15-042r6 + TimeseriesML 1.3 defines an XML encoding that implements the OGC Timeseries +Profile of Observations and Measurements, with the intent of allowing the exchange of +such data sets across information systems. Through the use of existing OGC standards, it +aims at being an interoperable exchange format that may be re-used to address a range of +data exchange requirements. + 2023-06-21 - + + Responding to an oil spill requires access to and understanding of many types of information. Effective, coordinated operations for the response are based on a shared, common picture of the situation. Interoperability provides shared situational awareness of the crisis and the response activities. What is needed is a common picture of reality for different organizations that have different views of the spill so that they all can deal with it collectively. +Recent oil spills have provided lessons learned and recommendations on forming a Common Operating Picture for oil spill response. Through a joint project, industry is responding to the call, moving from recommendations to reusable best practices supported by open standards that can be deployed quickly in any region of the globe. +This architecture report is part of The International Association of Oil & Gas Producers and IPIECA Oil Spill Response - Joint Industry Project (IOGP–IPIECA OSR-JIP) to produce a recommended practice for GIS/mapping in support of oil spill response and for the use of GIS technology and geospatial information in forming a “Common Operating Picture” to support management of the response. +Interoperability seems to be at first a technical topic, but in fact, it is about organization. Interoperability seems to be about the integration of information. What it’s really about is the coordination of organizational behavior. The Oil Spill Response Common Operating Picture (OSR COP) project seeks to facilitate the coordination of organizational response to any oil spill in the future. + OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response + 2015-10-01 - 00-028 - Web Map Service - - + 15-037 + OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response - Allan Doyle - - Web Map Service - 00-028 - 2000-04-19 - Provides four protocols (GetCapabilities, GetMap, GetFeatureInfo and DescribeLayer) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. + + George Percivall + 15-037 + + - - OpenGIS® Abstract Specification Proposed Topic 19 - General Reference Systems - 2008-04-29 - This discussion paper is a draft new topic volume for the OGC Abstract Specification, which may also be used to propose a corresponding new standard to ISO/TC 211. This document proposes extensions to OGC Abstract Specification Topic 2 — Spatial referencing by coordinates, and thus to ISO 19111 — Spatial referencing by coordinates. This discussion paper is posted for comments on the contents. Revision of this draft is planned, to improve some details while supporting the same abilities. - - Proposed Topic 19 - General Reference Systems - 08-008r1 - - + + OGC® WaterML 2.0: Part 1- Timeseries - Arliss Whiteside + + 10-126r3 + WaterML 2.0: Part 1- Timeseries - - 08-008r1 + 10-126r3 + 2012-08-30 + This document is an OGC® Encoding Standard for the representation of hydrological observations data with a specific focus on time series structures. WaterML2.0 is implemented as an application schema of the Geography Markup Language version 3.2.1, making use of the OGC Observations & Measurements standards. +WaterML2.0 is designed as an extensible schema to allow encoding of data to be used in a variety of exchange scenarios. Example areas of usage are: exchange of data for operational hydrological monitoring programs; supporting operation of infrastructure (e.g. dams, supply systems); cross-border exchange of observational data; release of data for public dissemination; enhancing disaster management through data exchange; and exchange in support of national reporting. +The core aspect of the model is in the correct, precise description of time series. Interpretation of time series relies on understanding the nature of the process that generated them. This standard provides the framework under which time series can be exchanged with appropriate metadata to allow correct machine interpretation and thus correct use for further analysis. Existing systems should be able to use this model as a conceptual 'bridge' between existing schema or systems, allowing consistency of the data to maintained. + + + Peter Taylor + + - - 05-057r3 - - + + This standard describes the Atom encoding of the OWC Context conceptual model. The goal of this standard is to provide a definition of how to encode a context document, which can be extended to allow a context referencing a fully configured service set to be defined and consistently interpreted by clients. + + OWS Context Atom Encoding Standard + 12-084r2 + OGC OWS Context Atom Encoding Standard + Roger Brackin, Pedro Gonçalves + 12-084r2 + + - - 2006-02-09 - Minimal Application Profile for EO Products - Minimal Application Profile for EO Products - 05-057r3 - Jolyon Martin - The services proposed in this profile are intended to support the identification and subsequent ordering of -EO data products from previously identified data collections. The intent of this initial profile is to -describe a minimum interface that can be supported by many data providers (satellite operators, data -distributors - + + 2014-01-14 + - - 2015-08-19 - Johannes Echterhoff - OGC® Testbed 11 Aviation - Guidance on Using Semantics of Business Vocabulary and Business Rules (SBVR) Engineering Report - Testbed 11 Aviation - Guidance on Using Semantics of Business Vocabulary and Business Rules (SBVR) Engineering Report - 15-024r2 - 15-024r2 - This document is a deliverable of the OGC Testbed 11 . It describes the results of developing a tool to automatically derive Schematron code from SBVR constraints. It also documents a vocabulary with a profile of core geospatial terms and concepts, which can be used to express geospatial constraints in business rules. - + + 04-051 + + + + Image Handling is a thread in the OGC Web Services 1.2 (OWS1.2). This document defines the system design for Image Handling in OWS1.2. The system design responds to the requirements in OWS 1.2 Image Handling Requirements. The system design specifies two main services: Image Archive Service and Image Catalogue Service. Interfaces for these two services are defined using previously defined OWS service interfaces. + George Percivall + OWS1.2 Image Handling Design + 04-051 + OWS1.2 Image Handling Design + 2004-09-26 - - - - David Danko, Lance Shipman, Paul Ramsey - OWS-8 Bulk Geodata Transfer with File Geodatabase - 11-114 - OWS-8 Bulk Geodata Transfer with File Geodatabase - 11-114 - - This document provides an overview of the File Geodatabase API and documents the testing performed in the OWS 8 Testbed. - + + 16-011r4 + Volume 8: CDB Spatial and Coordinate Reference Systems Guidance - - + Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames. +In previous versions of the CDB standard, this CDB volume was Appendix K in CDB Version 3.2 as submitted to the OGC. + + - 2011-11-16 - - + - - - 10-103r1 - OGC Name Type Specification - specification elements + Carl Reed + 16-011r4 + Volume 8: CDB Spatial and Coordinate Reference Systems Guidance + 2018-12-19 + + + + Uwe Voges, Kristian Senkler + 07-045r1 - 2021-09-27 - Gobe Hobona, Simon Cox - The mission of the OGC Naming Authority (OGC-NA) is to provide the means through which OGC resources such as OGC documents, namespaces and ontologies can be controlled and managed such that they can provide clear and well-defined names and definitions. In the terminology defined in ISO 19135, OGC-NA is the Control Body for the register of OGC Names. This document specifies a rule for constructing OGC names that may be used for identifying specification elements defined in the OGC Specification Model – Modular Specification. - OGC Name Type Specification - specification elements - 10-103r1 - - + 2018-03-09 + Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum + 07-045r1 + + + + OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum + Catalogue services are the key technology for locating, managing and maintaining +distributed geo-resources (i.e. geospatial data, applications and services). With OGC +catalogue services, client applications are capable of searching for geo-resources in a +standardized way (i.e. through standardized interfaces and operations) and, ideally, they +are based on a well-known information model, which includes spatial references and +further descriptive (thematic) information that enables client applications to search for +geo-resources in very efficient ways. +Whereas interfaces and operations of OGC catalogue services are well defined, it is left +up to the developer of the system to define a specific information model which a +catalogue service instance provides. This includes, but is not limited to, the information +which can be inserted in the catalog, supported query languages, available search terms, +response/result sets, etc. This point is of major importance with respect to interoperability +between different catalogue service instances. +In Europe, running catalogue instances result from work being done within different SDI +initiatives (e.g. SDI NRW Initiative1, Germany/Netherlands cross-border initiative, JRC +EU Portal, EUROSTAT, Inspire, German SDI initiative). Members of these initiatives +have developed an ISO-based application profile for ISO19115 metadata for +geodata/geospatial applications and ISO19119-based metadata for tightly and looselycoupled +geospatial services. The foundations of this profile were the OGC catalogue +specification (1.1.1), the OGC Web Registry Server (WRS) 0.0.2, OGC Web Services +Stateless Catalogue Profile (StCS) 0.0.6 and ISO 19115/19119 for content description. +OGC's catalogue revision working group (CS-RWG) has revised and integrated the +catalogue implementation specification v1.1.1 that have resulted in CS 2.0.2. One part of +this OGC specification comprises the definition of application profiles according to ISO +19106 (Geographic information – Profiles). The overall goal of these profiles is to +improve interoperability between systems conforming to a specific profile. Experience +has shown that the need for application profiles results from the fact that in practice, there +is no single solution for catalogue services that fits every user’s needs. As stated in CS +2.0.2, a base profile that provides a basic set of information objects has to be supported +by each catalogue instance; in addition, application profiles for different information +communities can be specified. +Hence, this document specifies an application profile for ISO 19115:2003/ISO +19119:2005 metadata with support for XML encoding per ISO/TS19139:2007 [ISO/TS19139]2 and HTTP protocol binding. It relies on requirements coming from the +CS/CSW 2.0 specification (OGC CS 2.0.2, OGC document 07-006). The application +profile will form the basis of conformance tests and reference implementations. + + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + 2017-08-30 + 16-126r8 + Release Notes for GeoPackage v1.2 + Release Notes for GeoPackage v1.2 + + + + + This document provides the set of revision notes for the existing GeoPackage version 1.2 (OGC 12- +128r13) and does not modify that standard. +This document was approved by the OGC membership on approval date. As a result of the OGC +Standards Working Group (SWG) process, there were a number of edits and enhancements made to +this standard. This document provides the details of those edits, deficiency corrections, and +enhancements. It also documents those items that have been deprecated. Finally, this document +provides implementations details related to issues of backwards compatibility. - Concepts in OGC Documents - Generated by the OGC Definitions Server to support integration of the elements of this ConceptScheme into bigger collections. ogc_skos_profile_entailements.ttl - Collection hierarchy for this ConceptScheme + 16-126r8 + Jeff Yutzler + + + + + + + + + + + + + + + + + + + + + + Documents of type Abstract Specification - deprecated + Documents of type Abstract Specification - deprecated + Documents of type Abstract Specification - deprecated - + + + + OWS-8 Aviation - WXXM Engineering Report + This OGC™ document specifies the advancement of WXXM and Weather Concepts in +the OWS-8 Aviation Thread. The focus is on investigating and demonstrating the +applicability and suitability of WXXM in producing accurate, real-time aircraft weather +radar data using OGC™ Web Coverage Services (WCS) to be used by meteorological +applications and services supporting aviation. Such applications provide information +which enhances safe and efficient tactical and + OWS-8 Aviation - WXXM Engineering Report + 11-072r2 - 16-030 - Testbed-12 Testbed-12 GeoPackage Mobile Apps Integration Engineering Report + Wenny Rahayu, Torab Torabi, Andrew Taylor-Harris, Florian Puersch - - Jeff Yutzler - Testbed-12 Testbed-12 GeoPackage Mobile Apps Integration Engineering Report - 2017-05-15 - - - 16-030 - Testbed 12 work evaluates the interoperability of the Common Map API tool with commercial vendor tools supporting GeoPackage. Ideally data can be shared and exchanged between apps on a single device via GeoPackage. The demonstration will show the vector and/or routing data being used by disparate applications. + + 2012-01-25 + 11-072r2 - - Alaitz Zabala, Joan Maso - 17-018 - Testbed-13: Data Quality Specification Engineering Report - OGC Testbed-13: Data Quality Specification Engineering Report - OGC 17-018 (Testbed-13 Data Quality Specification Engineering Report) provides methods to quantify the quality concepts defined in OGC 17-032 and a way to include the quantifications in service descriptions. It extends QualityML quality metrics (that already includes ISO 19157) into the aviation domain. It lists a set of quantitative and conformance measurements that are specified in terms of quality measures, domains, and metrics (value types and units) and are appropriated for each quality type and data type. Secondly, it extends the SDCM to be able to encode and include the above mentioned quality information for each service in a interoperable way. - 17-018 + + + + 16-010r5 + 2021-02-26 + + Carl Reed + Volume 7: OGC CDB Data Model Guidance (Best Practice) + 16-010r5 + Volume 7: OGC CDB Data Model Guidance (Best Practice) + This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store. + + - - - 2018-01-26 - - - - 09-000 + + + 2017-10-03 - - - - The OpenGIS® Sensor Planning Service Interface Standard (SPS) defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor planning request; to submit and reserve/commit such a request; to inquire about the status of such a request; to update or cancel such a request; and to request information about other OGC Web services that provide access to the data collected by the requested task. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. - Sensor Planning Service Implementation Standard - 09-000 - OGC® Sensor Planning Service Implementation Standard - - 2011-03-28 - Ingo Simonis, Johannes Echterhoff - - - - 18-049r1 - Application Package Engineering Report - OGC Testbed-14: Application Package Engineering Report - This Engineering Report (ER) describes the work performed by the Participants in the Exploitation Platforms Earth Observation Clouds (EOC) Thread of OGC Testbed-14 in regard to the Application Package (AP). - -The AP serves as a means to convey different kinds of information describing a certain application - often, but not necessarily, an Earth Observation data processing algorithm - so that different elements of an ecosystem generically known as an Exploitation Platform can exchange information among themselves in a standard and interoperable way. The AP guarantees that, despite potentially very heterogeneous implementations and implementing entities, applications are treated equally. The AP also guarantees that the Earth Observation scientist who developed it on the one hand is shielded from infrastructure details and heterogeneity and on the other hand benefits from the ability to execute the same application on different infrastructure. - -Given its suitability for conveying a Common Operating Picture (COP), in OGC Testbed-13 the OGC Web Services (OWS) Context standard had been chosen as the basic encoding for the Application Package. Despite serious consideration, and while acknowledging the advantages of that approach, the consensus among Participants was not to continue along this path in Testbed-14 but instead to opt for an AP encoding, consisting of a WPS-T (Transactional Web Processing Service (WPS)) DeployProcess message encoded in JSON (see Chapter 9 for the rationale). The information model conveyed in this manner does not differ significantly from the one that could be conveyed using OWS Context, and its main, common features can be briefly listed as: - -a link to the application execution unit, - -a description of the application’s inputs and outputs, - -links to required Earth Observation data catalogues, - -and the possibility to pass other auxiliary information. - -An important difference in Testbed-14 with respect to Testbed-13 is that the application execution unit is not limited to a Docker container, but can also be a workflow described in Common Workflow Language (CWL), something which stems directly from one of the Sponsor requirements. Finally, it is important to note that this route does not preclude from embedding an OWS Context structure in the enclosing DeployProcess document if this is desired. - -Starting from the lessons learned and limitations identified in Testbed-13, and embracing the new and changed Sponsor requirements, this ER explains the trade-offs, decisions and conclusions taken by the Participants throughout the project. + 16-097 + Future City Pilot 1: Using IFC/CityGML in Urban Planning Engineering Report + Mohsen Kalantari + Numerous and diverse technologies push cities towards open and platform-independent information infrastructures to manage human, natural, and physical systems. The Future Cities Pilot 1 (FCP1), as an OGC Innovation Program initiative, demonstrated how cities can benefit from open standards when used in urban planning workflows. This report details the lessons learned of implementing both the OGC CityGML and the buildingSMART Industry Foundation Classes (IFC) standards for visualizing and processing 3D spatial data when used in urban planning processes. - 18-049r1 - - 2019-02-07 - Paulo Sacramento - - - - 19-020r1 - - 19-020r1 - OGC Testbed-15: Catalogue and Discovery Engineering Report - - This OGC Testbed-15 Engineering Report (ER) describes the results of the Earth Observation (EO) Process and Application (EOPAD) Task in the Cloud Processing and Portrayal (CPP) thread of OGC Testbed-15. The ER presents the data model and service interface of the catalogue service allowing for discovery of EO applications and related processing services for subsequent deployment and/or invocation in a distributed environment. - -The ER also provides the architectural and implementation details of the software components that were developed as part of the activity and which interact through the described data model. These software components include catalogue clients, catalogue servers and transactional Web Processing Service (WPS-T) servers. - 2019-12-12 + 16-097 + Future City Pilot 1: Using IFC/CityGML in Urban Planning Engineering Report - - - - OGC Testbed-15: Catalogue and Discovery Engineering Report - Yves Coene - - WaterML 2.0 - Timeseries - NetCDF Discussion Paper - 12-031r2 - - - - This discussion paper investigates the possible uses of NetCDF as a representation of WaterML timeseries data. The work is largely based on the WaterML 2.0 standard for timeseries, the NetCDF core and extensions standards and the CF-NetCDF and ADCC conventions. - - WaterML 2.0 - Timeseries - NetCDF Discussion Paper + + 16-084 + - Doug Palmer - 12-031r2 - 2012-07-12 - - - - - 2018-12-19 - 15-112r3 - This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice. - Volume 3: OGC CDB Terms and Definitions - - Volume 3: OGC CDB Terms and Definitions - 15-112r3 - Carl Reed - - - - - - 1999-05-05 - The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc). - 99-049 - Simple Features Implementation Specification for SQL - - - - Keith Ryden - - - - OpenGIS Simple Features Implementation Specification for SQL - 99-049 - - - 2010-02-08 - 09-144r2 - Technical Committee Policies and Procedures: MIME Media Types for GML - - - - - MIME Media Types for GML - 09-144r2 - Clemens Portele - - This document provides guidance on GML MIME type specification. An Internet media type, originally called a MIME type after Multipurpose Internet Mail Extensions and sometimes a Content-type after the name of a header in several protocols whose value is such a type, is a two-part identifier for file formats on the Internet. The identifiers were originally defined in RFC 2046 for use in e-mail sent through SMTP, but their use has expanded to other protocols such as HTTP, RTP and SIP. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - 08-132 - Thomas Everding, Johannes Echterhoff - Event Pattern Markup Language (EML) - 08-132 - + OGC Benefits of Indoor Location - Use Case Survey of Lessons Learned and Expectations + Giuseppe Conti, Fabio Malabocchia, Ki-Joune Li, George Percivall, Kirk Burroughs, Stuart Strickland + 16-084 + OGC Benefits of Indoor Location - Use Case Survey of Lessons Learned and Expectations + Indoor location technologies are enjoying and increasing market success. Technologies in the market have achieved maturity and have become a key driver for innovation and business activities in several value added scenarios, e.g. e-government services, eHealth, personal mobility, logistics, mobility, facility management, retail, to name but a few. This paper collects the results of a survey on the benefits of indoor location, which was jointly prepared and launched by OGC – the Open Geospatial Consortium, InLocation Alliance and i-locate project at the beginning of 2016. Overall, 153 survey responses were received from 33 countries. Responses were categorized in two areas: Client Organizations and Technology suppliers. The goal of the initiative was to acquire a broad view of the requirements and use cases emerging from the wider industrial and user community, beyond the memberships of the various organizations, in order to capture trends, challenges and opportunities, as well as trends and barriers to widespread use of indoor location technologies. This paper does not represent a view of the membership involved in the different organizations; instead, it provides the opportunity to capture recommendations of relevance for the industrial and standardization community these organizations represent. + + 2016-08-01 + + + 2012-01-25 + This document provides an overview on the OGC Web Coverage Service (WCS) 2.0 suite by describing WCS core and extensions. +Intended target audience are developers intending to implement WCS servers and/or clients. This document aims at providing an overview and giving useful hints and best practices beyond the pure standards texts. It is a &quot;living document&quot; which will evolve to reflect new developments and best practices. +As such, the contents of this document is informative and not of normative nature. + + + Peter Baumann - 2008-11-05 - The Event Pattern Markup Language (EML) allows one to describe event patterns for event (stream) processing and analysis. It can be used to build multi stage filters for incoming events but also to derive higher information through combining and correlating multiple events. It can be applied on single events but is focused on handling of continuous event streams. + + + + + OGC® Web Coverage Service 2.0 Primer: Core and Extensions Overview + Web Coverage Service 2.0 Primer: Core and Extensions Overview + 09-153r1 + 09-153r1 + + + 07-009r3 + OGC Web Services Architectural Profile for the NSG + Shayne Urbanowski + 07-009r3 - Event Pattern Markup Language (EML) + + The purpose of this document is to generally describe how the various OGC specifications may be used to address the needs of a large enterprise system. It highlights the key elements of the OWS-4 effort as they relate to web service architecture implementation at NGA and in the NSG. The goal is that this document will enable organization that interface with the NSG to understand how to produce and consume data and services in an interoperable environment. + 2007-08-13 + + + + OGC Web Services Architectural Profile for the NSG - - Naming of OGC API Standards, Repositories & Specification Elements - 20-059r4 - Gobe Hobona - This document is a policy of the OGC Naming Authority (OGC-NA), a sub-committee of the OGC Technical Committee. The document defines a series of policy requirements for OGC API standards, repositories, definitions, and specification elements. The policy document is intended to be a specialization of the OGC-NA policy on naming specification elements (OGC 10-103). + + Sensor Alert Service + + Ingo Simonis + 06-028 + 06-028 + Sensor Alert Service - - - Naming of OGC API Standards, Repositories & Specification Elements - 2021-01-28 - - 20-059r4 - + + + + 2006-04-05 + A service providing active (push-based) access to sensor data. - - 06-009r6 - 2008-02-13 + + 16-114r3 + Moving Features Encoding Extension: netCDF + 2018-12-18 + + + 16-114r3 - OpenGIS Sensor Observation Service + + OGC Moving Features Encoding Extension: netCDF + + The netCDF Moving Features encoding extension is a summary of conventions that supports efficient exchange of simple moving features as binary files. This Best Practice is a complement to the Moving Features Encoding Part I: XML Core and an alternative to the Simple Comma Separated Values (CSV) extension. Compared to the CSV encoding, this netCDF encoding offers more compact storage and better performance at the cost of additional restrictions on the kinds of features that can be stored. + + Martin Desruisseaux + + + + Testbed-18: Filtering Service and Rule Set Engineering Report + 22-024r2 + Testbed-18: Filtering Service and Rule Set Engineering Report + This Testbed-18 (TB-18) Filtering Service and Rule Set Engineering Report (ER) documents best practices identified for features filtering and describes in detail how filtering can be decoupled from data services. Further, this ER describes how filtering rules can be provided to Filtering Services at runtime. + + Sergio Taleisnik + + 2023-06-16 - - 06-009r6 - Sensor Observation Service - The OpenGIS® Sensor Observation Service Interface Standard (SOS) provides an API for managing deployed sensors and retrieving sensor data and specifically “observation” data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. + + + 22-024r2 + + + + - Arthur Na, Mark Priest - + Mike Botts + OpenGIS Sensor Model Language (SensorML) + 07-000 + The OpenGIS® Sensor Model Language Encoding Standard (SensorML) specifies models and XML encoding that provide a framework within which the geometric, dynamic, and observational characteristics of sensors and sensor systems can be defined. There are many different sensor types, from simple visual thermometers to complex electron microscopes and earth observing satellites. These can all be supported through the definition of atomic process models and process chains. Within SensorML, all processes and components are encoded as application schema of the Feature model in the Geographic Markup Language (GML) Version 3.1.1. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. For additional information on SensorML, see http://www.botts-inc.net/vast.html +<!-- http://vast.uah.edu/SensorML.--> + 2007-07-24 + 07-000 + Sensor Model Language (SensorML) + + - + + Documents of type Name Type Specification + + + + + + - OWS-8 Domain Modelling Cookbook - 11-107 - - Rob Atkinson, James Groffen - 11-107 - OGC  OWS-8 Domain Modelling Cookbook - 2011-06-17 - - + Documents of type Name Type Specification + Documents of type Name Type Specification + + + + OWL-Time is an OWL-2 DL ontology of temporal concepts, for describing the temporal properties of resources in the world or described in Web pages. The ontology provides a vocabulary for expressing facts about topological (ordering) relations among instants and intervals, together with information about durations, and about temporal position including date-time information. Time positions and durations may be expressed using either the conventional (Gregorian) calendar and clock, or using another temporal reference system such as Unix-time, geologic time, or different calendars. + + + Time Ontology in OWL + Simon Cox, Chris Little + + Time Ontology in OWL + 16-071r3 - This OGCTM document describes best practices for building and maintaining inter-related -domain models, which have dependencies upon multiple systems. It describes how to -build interoperable, maintainable domain models, the challenges and pitfalls faced in -building these models, the techniques and patterns that should be applied, and specific -tools that can be used. The theory of domain modelling is addressed, followed by -practical step-by-step instructions on how to use of the tools. Examples are provided from -Aeronautical Information Exchange Model (AIXM) and Farm Markup Language -(FarmML) as they were refined in the OGC’s OWS-8 testbed. - + + + 2020-03-26 + 16-071r3 + + - + + 18-022r1 + SWIM Information Registry Engineering Report - OGC® OWS-9 Web Feature Service Temporality Extension Engineering Report - This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 9 (OWS-9). This Engineering Report summarizes the OWS-9 activity regarding the extension of the Web Feature Service (WFS) and Filter Encoding (FE) standards to support dynamic feature data. -Specifically this document describes the result work performed in OWS 9 on the WFS Temporality Extension. The technical specification including background is discussed and defined in the OGC Discussion Paper 12-027r1. This document gives a summary about issues, lessons learned, recommendations, accomplishments and benefits for the Aviation Architecture. It also gives an outlook on future work items and change requests. - - 12-146 + + + OGC Testbed-14: SWIM Information Registry Engineering Report + 2019-02-11 + Yann Le Franc + 18-022r1 + This Engineering Report (ER) summarizes the findings and recommendations for building an information registry working together with the existing Federal Aviation Administration (FAA) System Wide Information Management (SWIM) aviation service registries, the National Airspace System Service Registry and Repository (NSRR). This information registry should allow the different Air Traffic Management (ATM) stakeholders to retrieve the appropriate service registered in the NSRR using the semantic representation of real-life entities represented by the data served by the services (e.g. estimated departure time, estimated time of arrival, ”runway true bearing”…). To support the integration of this domain-specific information, the ER proposes different strategies based on the semantic annotation proposal made in OGC 08-167r2 [1] extended with a recent World Wide Web Consortium (W3C) recommendation, the Web Annotation data model [1]. In particular, the ER focuses on a solution using the W3C web annotation data model which adds semantics to the NSRR without changing the content of the database. This solution provides a low-cost, flexible and efficient alternative to add domain-specific semantics to NSRR content. The ER concludes with remarks on the elements necessary for implementing the information registry as a web annotation store as well as the necessity to build domain-specific knowledge models to support further interoperability and further service discoverability and the added-values of using the Data Catalog (DCAT) or Semantic Registry Information Model (SRIM) to better describe and retrieve ATM services. - 2013-06-18 - Timo Thomas - - 12-146 - OWS-9 Web Feature Service Temporality Extension Engineering Report - - - Testbed-18: Key Management Service Engineering Report - 22-014 - Andreas Matheus + + Arliss Whiteside - - + 2008-04-29 + Proposed Topic 19 - General Reference Systems + 08-008r1 + OpenGIS® Abstract Specification Proposed Topic 19 - General Reference Systems - - 22-014 - This OGC Testbed 18 Engineering Report describes the Data Model and API of a Key Management Service (KMS) that supports the flexible but secure exchange of cryptographic keys for applying confidentiality and integrity protection to geographic information. The described KMS is based on the design and implementation from previous OGC Testbeds 16 and 17. - 2023-01-05 - Testbed-18: Key Management Service Engineering Report + This discussion paper is a draft new topic volume for the OGC Abstract Specification, which may also be used to propose a corresponding new standard to ISO/TC 211. This document proposes extensions to OGC Abstract Specification Topic 2 — Spatial referencing by coordinates, and thus to ISO 19111 — Spatial referencing by coordinates. This discussion paper is posted for comments on the contents. Revision of this draft is planned, to improve some details while supporting the same abilities. + + + + 08-008r1 - - - 2014-05-19 - 14-013r1 - This document specifies technical changes to the OGC web service architecture baseline to support better integration among the services. Although integration may be achieve in a number of ways and using a number of other technologies, the goal of this document is to achieve this integration within the current OGC service framework in order to leverage existing investments in OGC web services infrastructure. + + 18-095r7 + + + + 18-095r7 + Geospatial Coverages Data Cube Community Practice + Geospatial Coverages Data Cube Community Practice + + + Data cubes for geospatial information provide the means to integrate observations and other types of geospatial data for use in multiple applications through simplified access and efficient analytics. Using the Geospatial Coverages data structure, this Community Practice defines requirements for a geospatial coverages data cube infrastructure and guidelines for enhancements and extensions to the basic core. + 2020-10-14 + George Percivall + + + + 0000-00-00 + OWS-9 WCS Conformance Testing Engineering Report + 12-162r1 + This Engineering Report was prepared as a deliverable for the OGC Web Services, Phase +9 (OWS-9) initiative of the OGC Interoperability Program. The document presents the +work completed with respect to the Conformance & Interoperability Testing & +Evaluation sub-thread within OWS-9. +This Engineering Report describes and evaluates the specification of WCS 2.0 core +corrigenda and extensions’ Abstract Test Suite (ATS) and the implementation of ETS for +use within an OGC SOA processing chain. + + Jinsongdi Yu, Peter Baumann + + 12-162r1 + OWS-9 WCS Conformance Testing Engineering Report - - 14-013r1 - Testbed-10 Service Integration Engineering Report - - OGC® Testbed-10 Service Integration Engineering Report - Panagiotis (Peter) A. Vretanos + + + + + + + Web Map Service + Provides four protocols (GetCapabilities, GetMap, GetFeatureInfo and DescribeLayer) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. + + 2001-06-21 + + Web Map Service + 01-047r2 + + Jeff de La Beaujardiere + 01-047r2 - + + + + 12-147 + OWS-9 Aviation Architecture Engineering Report - Carl Reed - 16-006r5 - Volume 10: OGC CDB Implementation Guidance - This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. - + This OGC® document describes the architecture implemented in the OWS-9 Aviation thread, including: +• A description of the architecture used for the implementation of the OWS-9 Aviation Use Cases. +• An overview of the implemented components and workflows followed by a short description of each component. +• A discussion about discovery and registry methods and practices. +• Documentation of the issues, lessons learned as well as accomplishments and scenarios that were of general interest in the Aviation thread. +More detailed information on specific aspects considered in OWS-9 Aviation may be found in the individual Aviation Engineering Reports. - 16-006r5 - Volume 10: OGC CDB Implementation Guidance + 2013-02-06 + - 2021-02-26 - - - + 12-147 + Claude Speed + OWS-9 Aviation Architecture Engineering Report - + + 15-005r2 + Defence Profile of OGC Web Feature Service 2.0 + + DGIWG + 15-005r2 + This document defines the DGIWG profile for the ISO +19142:2010 - Web Feature Service (WFS) including changes +made in the OpenGIS Web Feature Service 2.0 Interface +Standard - Corrigendum. The Web Feature Service provides +access to geospatial features in a manner independent of the +underlying data store. + + 2021-02-26 - 09-048r5 - Name Type Specification - definitions - part 1 – basic name - 09-048r5 - 2019-10-31 - OGC Name Type Specification - definitions - part 1 – basic name - Simon Cox, Gobe Hobona - - This document specifies a rule for constructing OGC names that may be used for identifying definitions. - - + Defence Profile of OGC Web Feature Service 2.0 + - - - This Engineering Report (ER) describes requirements that a point cloud web service must satisfy to enable application developers to provide convenient remote access to point clouds. It provides a short contrast of five point cloud web service software approaches (Esri I3S, 3D Tiles, Greyhound, PotreeConverter, and Entwine) and their implementations available at the time of the report. A small industry survey about these requirements is also provided in support of the report’s discussion about formats, web service requirements, industry support, and industry desire on these topics. - - + + 2005-01-26 + URNs of definitions in ogc namespace - - Howard Butler - 18-048r1 - Point Cloud Data Handling Engineering Report - 18-048r1 - OGC Testbed-14: Point Cloud Data Handling Engineering Report - + *** Superceded by 06-023r1 - Definition identifier URNs in OGC namespace *** +This Recommendation Paper specifies Universal Resource Names (URNs) for definitions in the + + URNs of definitions in ogc namespace + 05-010 + + 05-010 + Arliss Whiteside + - 2019-03-08 - - Geoparser - 01-035 - - - Jeff Lansing - - *RETIRED* Geoparsing refers to the capability to process a textual document and identify key words and phrases that have a spatial context. + + OGC Testbed-17: UML Modeling Best Practice Engineering Report + + 21-031 - 2001-03-27 - 01-035 - Geoparser - + This OGC Best Practice provides readers with guidance on how to use the Unified Modeling Language (UML) within the scope of OGC work. Recently there has been a move to a resource-based approach for OGC Application Programming Interface (API) definition through the OpenAPI Specification and away from the service-based approach specified in OGC Web Service (OWS) standards. Previously, the interface definitions were almost exclusively XML based, therefore models described using UML class diagrams and conceptual models in general simply mapped 1:1 to derive the XML schema. Using API resources has resulted in the possibility of deriving multiple target technologies from a single standard and therefore, UML model. An additional point of discussion within the OGC is the value added by conceptual modeling using UML. Models included in OGC Standards vary from diagrams only, to conceptual models and model fragments all the way through to Model Driven Architecture (MDA) where UML models are used to directly derive implementable artifacts such as schemas. + +UML has been the main modeling language of choice within the OGC, although up until now, there has been little guidance within the OGC on appropriate use of UML. These Best Practices do not seek to govern the use of UML within the OGC as it is recognized that UML is a flexible language that has applications beyond the current OGC doctrine. However, the practices seek to provide guidance to assist in adherence to the following principles: + + Correctness — Adherence to the Object Management Group (OMG) UML standard. + Consistency — UML artifacts should be consistent across OGC Standards and with supporting standards such as those specified by ISO/TC 211. + FAIRness — Findable, Accessible, Interoperable and Reusable models. + Value — Any modeling done, UML or otherwise, should add value to the parent standard. That is, the modeling should do work for the community that is not done elsewhere. +The Practices are as follows: + + Practice 1: UML models should follow the OMG UML 2.5.1 Standard ratified in 2017. + Practice 2: OGC Conceptual Models should be represented as UML Class diagrams. + Practice 3: OGC Conceptual Models should be platform independent. + Practice 4: OGC Conceptual Models should use concepts consistently across standards. + Practice 5: OGC Standards should contain a UML model at least at the conceptual level of detail. + Practice 6: UML models in OGC Standards should add value. + Practice 7: UML models should describe structure in the engineering process. + Practice 8: Modeling artifacts should be provided in full. + Practice 9: UML models should at least be consistent with supporting text, but ideally normative. + Practice 10: UML tooling should produce interoperable artifacts. + Practice 11: UML can be used for modeling semantics, although there are other technologies that are more appropriate. + Practice 12: OGC UML models should be machine readable (i.e. available in XMI format, in addition to the format of the UML Editor used to create the model). + 2022-02-08 + Sam Meek + + UML Modeling Best Practice Engineering Report + 21-031 + + - - OGC® OWS-9 Engineering Report - OWS Innovations - Map Tiling Methods Harmonization - 2013-06-18 - + + This OGC Engineering Report (ER) describes work done in OGC Testbed 11 to test +GMLJP2 in terms of defining a DGIWG GMLJP2 version 1 profile. +The requirements for a DGIWG profile of GMLJP2 have been documented in the +DGIWG GMLJP2 version 1 profile. The Imagery WG inside DGIWG has developed a +filter to map the files produced using the previous GMLJP2 schema into the GMLJP2 +version 2 schema and is about to submit a GMLJP2 2.0 profile to DGIWG. +The DGIWG implementation of the GMLJP2 profile is based on the OGC GMLJP2 v2 +and other requirements are coming directly from the adoption inside the DGIWG of the +new OGC GMLJP2 version 2. +This Testbed 11 activity is a response to the need of harmonization between DGIWG and +OGC. + Testbed-11 DGIWG GMLJP2 testing results Engineering Report + 15-073r2 + 2015-11-18 - 12-157 - Joan Masó - This engineering report proposes a profile for WMTS that limits the flexibility or the standard and mimics what some other tile initiatives are doing. It also proposes some improvements in WMTS to accommodate the need for requesting several tiles of a region at different scales that has been identified by the GeoPackage team. These recommendations help to better harmonize OSGeo tile standards and mass-market technologies. - OWS-9 Engineering Report - OWS Innovations - Map Tiling Methods Harmonization - 12-157 - - + OGC® Testbed-11 DGIWG GMLJP2 testing results Engineering Report + + 15-073r2 + + + E. Devys, L.Colaiacomo, P. Baumann - - + + + 99-113 + + 99-113 + Topic 13 - Catalog Services + + + Covers the Geospatial Information Access Services + Cliff Kottman + 1999-03-31 - OGC API - Common - Users Guide - 20-071 - 2023-03-28 - - The OGC API — Common Standard is a multi-part Standard that specifies reusable building-blocks that can be used in the construction of OGC API Standards. The OGC API — Common — Users Guide presents information useful to developers or users of implementations of the OGC API — Common Standard. The information in the Users Guide is not normative. That is, it is not mandatory. However, it may prove essential to fully understand the normative text in the OGC API — Common Standard. The Users Guide is therefore intended to serve as an aid to developers and users. - Charles Heazel - 20-071 - - - OGC API - Common - Users Guide + Topic 13 - Catalog Services - - OpenGIS SensorML Encoding Standard v 1.0 Schema Corregendum 1 - 07-122r2 - - Mike Botts, Simon Cox + + 09-072 + + OWS-6 CITE TEAM Engine Engineering Report + + 2009-08-05 + This document summarizes the work done on the TEAM compliance test engine and DGIWG Profile compliance test by Northrop Grumman for the CITE thread of OWS-6 in 2008-2009. + + OWS-6 CITE TEAM Engine Engineering Report + 09-072 - 2007-11-12 - Changes to the 1.0 schemas - - - SensorML Encoding Standard v 1.0 Schema Corregendum 1 - 07-122r2 - - - - - Michala Hill - - - This OGC Best Practice (BP) document describes the conversion process for converting a CDB structured Shapefile into a CDB structured GeoPackage. This is the companion document to Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension). Volume 13 defines the requirements and provides CDB specific guidance on using GeoPackage containers in a CDB data store. - - Volume 14 OGC CDB Guidance on Conversion of CDB Shapefiles into CDB GeoPackages (Best Practice) - 19-066 - 19-066 - Volume 14 OGC CDB Guidance on Conversion of CDB Shapefiles into CDB GeoPackages (Best Practice) - 2021-02-26 - + James Ressler - - - - - - Richard Creps,Victor Brown,Bill Floyd,John Garcia,Jeff Grinstead,Robert Kraus,Steve Matney,Robert Qu - EA-SIG Collaboration White Paper - 04-085 - 2004-02-20 + + 2018-03-05 + + This Engineering Report (ER) has been produced in conjunction with two other engineering reports from the OGC Testbed 13, the Abstract Data Quality ER [4] and the Data Quality Specification ER [5] to capture status quo, discussions, and results in the context of requirements for data quality assessment for Quality of Service in the Aviation Domain. It will, in particular, provide a Data Quality Assessment Service Specification. Much of the ER is presented in the future tense, using terms such as 'shall', in order to express requirements and constraints on future Data Quality Assessment Service implementations. The service specification includes design patterns, extension mechanisms, and service interface considerations. + +In recent years, the concept of data quality has generated a notable interest among System Wide Information Management (SWIM) [17] implementers, both organization-specific and global. In the context of SWIM — and Service Oriented Architecture (SOA) implementations in general — data quality pertains to two major use cases, service advertising and service validation: + +Service advertising +a service makes known to a potential consumer the quality of the data provided by the service. Based on this information, the consumer can determine whether or not the service meets its needs. + +Service validation +assurance is given that the quality of the data provided by a service is consistent with the quality that is explicitly defined in a service contract or any kind of agreement that may exist between a service provider and service consumer. + +Both use cases share two common preconditions: + +An unambiguous definition of the concept of data quality exists. + +A set of measurable parameters that allow specifying data quality is defined. + +These are tasks that were performed as part of Testbed 13. The findings of the tasks are documented in the Abstract Data Quality ER (FA001)[4] and the Data Quality Specification ER (FA002)[5]. + Aleksandar Balaban + + 17-025r2 + Testbed-13: Quality Assessment Service Engineering Report + + + - EA-SIG Collaboration White Paper - 04-085 - *RETIRED* The focus of collaboration services discussed in this white paper is on applications that directly support user interaction and on the applications that monitor, manage and control these interactive services. - - + 17-025r2 + OGC Testbed-13: Quality Assessment Service Engineering Report - - 2011-01-17 - - - PDF Geo-registration Encoding Best Practice Version 2.2 - George Demmy, Carl Reed - The intended audience of this document is a developer of software for creating and consuming geo=registered PDF documents that conform to PDF geo-registration 2.2. It specifies how to create the necessary PDF objects that identify a region of the PDF page as a map and describe the map’s coordinate systems. Map creation and rendering to a PDF page are not addressed. The underlying PDF file format is not addressed. The file format is specified in PDF Reference[1] . - PDF Geo-registration Encoding Best Practice Version 2.2 - 08-139r3 - + + OGC: Towards Data Cube Interoperability + 21-067 + OGC: Towards Data Cube Interoperability + 21-067 - 08-139r3 + 2021-10-07 - - - - - - - - - - - - - - - - - - - - - - - - + + Data cubes, multidimensional arrays of data, are used frequently these days, but differences in design, interfaces, and handling of temporal characteristics are causing interoperability challenges for anyone interacting with more than one solution. To address these challenges, the Open Geospatial Consortium (OGC) and the Group on Earth Observation (GEO) invited global data cube experts to discuss state-of-the-art and way forward at the “Towards Data Cube Interoperability” workshop. The two-day workshop, conducted in late April 2021, started with a series of pre-recorded position statements by data cube providers and data cube users. These videos served as the entry points for intense discussions that not only produced a new definition of the term ‘data cube’ (by condensing and shifting emphasize on what is known as the six faces model), but also pointed out a wide variety of expectations with regards to data cube behaviour and characteristics as well as data cube usage patterns. This report summarizes the various perspectives and discusses the next steps towards efficient usage of data cubes. It starts with the new definition of the term Data Cube, as this new understanding drives several recommendations discussed later in this report. The report includes further discussion that followed the actual workshop, mainly conducted in the context of the Geo Data Cube task in OGC Testbed-17. + + + + Ingo Simonis - - An OGC name is required for ontology resources published by OGC. This includes OWL -ontologies, classes and properties. - Name type specification – ontology resources - 12-081 - Name type specification – ontology resources - - + + + Location Services (OpenLS): Core Services [Parts 1-5] + 03-006r3 + Marwa Mabrouk + OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform. + 03-006r3 + OpenGIS Location Services (OpenLS): Core Services [Parts 1-5] + + + + + 2004-01-16 - + + - Simon Cox - 12-081 + + + Steven Chau & Mohsen Kalantari + 19-032 - 2013-06-18 + 19-032 + Indoor Mapping and Navigation Pilot: Public Safety Features CityGML ADE ER + This document defines an Application Domain Extension (ADE) of CityGML for public safety use cases. The ADE has been developed as part of OGC’s Indoor Mapping and Modeling Pilot project sponsored by the National Institute of Standards and Technology (NIST), Communications Technology Laboratory (CTL), Public Safety Communications Research (PSCR) Division. The ADE has been developed primarily based on reference preplan symbology created by the National Alliance for Public Safety GIS (NAPSG) Foundation. NAPSG is a 501 (C) (3) not-for-profit organization that was established in 2005 to overcome challenges faced by Federal, tribal, state, and local public safety agencies in the United States. NAPSG focuses on using GIS technology to resolve challenges that occur. In the definition of the ADE, public safety requirements that were not explicit in NAPSG have also been considered. This Engineering Report (ER) provides the methodology of the ADE development, details the implementation of the ADE and its structure and the application of the ADE in the context of public safety use cases. + +The findings include: + +A methodology to transform NAPSG symbology to data elements; + +A need for an extension of a reference to four existing CityGML classes; and + +The creation of seven new CityGML classes that are critical for public safety use cases. + OGC Indoor Mapping and Navigation Pilot: Public Safety Features CityGML ADE ER + + + 2020-07-30 - - OWS-8 AIXM Metadata Guidelines Engineering Report - 11-061r1 - 11-061r1 - 2012-02-09 - + + Interoperable Simulation and Gaming Sprint Engineering Report + 20-087 + 2021-01-26 + + Leonard Daly, Scott Serich - This OGC® Engineering Report provides guidelines for ISO metadata usage in AIXM 5.1 -conformant to the requirements of OGC 10-195 (Requirements for Aviation Metadata) -and the recommendations of OGC 10-196r1 (Guidance on the Aviation Metadata -Profile), with the exception of non-ISO metadata elements listed in these documents. + + + 20-087 + The OGC Interoperable Simulation and Gaming Sprint advanced the use of relevant OGC and Khronos standards in the modeling and simulation community through practical exercise and testing of the GeoVolumes API draft specification produced by the 3D Data Container and Tiles API Pilot. Of particular interest was the handling and integration of glTF models coming from multiple sources, but the sprint also examined the specification’s implementability, consistency, completeness, and maturity. + Interoperable Simulation and Gaming Sprint Engineering Report - David Burggraf - - OWS-8 AIXM Metadata Guidelines Engineering Report - - - - 1999-05-18 - OpenGIS Simple Features Implementation Specification for OLE/COM - TC Chair - 99-050 + + + + OpenGIS Simple Features Implementation Specification for OLE/COM + 1999-05-18 Simple Features Implementation Specification for OLE/COM - - The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc). - 99-050 + 99-050 + 99-050 + The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc). + - - Arliss Whiteside + + + CSW-ebRIM Registry Service - Part 2: Basic extension package + 07-144r2 + 07-144r2 + CSW-ebRIM Registry Service - Part 2: Basic extension package + + Richard Martell + This OGC® document is a companion to the CSW-ebRIM catalogue profile (OGC 07-110r2). It specifies the content of the Basic extension package that shall be supported by all conforming services. The package includes extension elements of general utility that may be used to characterize a wide variety of geographic information resources, with a focus on service-oriented metadata management. + + 2008-03-11 + - 2006-07-18 - 05-096r1 - GML 3.1.1 grid CRSs profile - 05-096r1 - - This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding definitions of grid coverage (including image) Coordinate Reference Systems (CRSs) plus related coordinate Transformations. This document also specifies some Universal Resource Names (URNs) for definitions in the ogc URN namespace, in addition to those specified in [OGC 05-010]. Additional specific URNs are defined for definitions of the datums, coordinate systems, and coordinate system axes which are often used in definitions of grid and image CRSs. - GML 3.1.1 grid CRSs profile - + + + Udo Quadt, Thomas Kolbe + The Web 3D Service is a portrayal service for three-dimensional geodata, delivering graphical elements from a given geographical area. In contrast to the OGC Web Mapping service (WMS) and the OGC Web terrain service (WTS) 3D scene graphs are produced. These scene graphs will be rendered by the client and can interactively be explored by the user. The W3DS merges different types (layers) of 3D data in one scene graph. + + + 2005-02-02 - + + 05-019 + Web 3D Service + + + Web 3D Service + 05-019 - + + Loosely Coupled Synchronization of Geographic Databases in the CGDI + 08-001 + 2008-04-29 + Raj Singh + 08-001 + OGC® Loosely Coupled Synchronization of Geographic Databases in the Canadian Geospatial Data Infrastructure Pilot - + - Greg Schumann, Josh Lieberman - - 16-014r2 + + + + This Discussion Paper documents results from the Interoperability Program CGDI Pilot and describes a suite of services that enable the sharing of geographic information across organizations for the purposes of: geographic database synchronization in support of a spatial data infrastructure; geographic database modification suggestions from trusted and un-trusted sources; and the transmission of geographic information in emergency notification events. + +These services are called the Update Feed Service; Feedback Feed Service; and Emergency Alert Service respectively. Their information encodings are all based on the Atom Syndication Format, extended with GML and WFS Filter encodings to support geospatial requirements, and were implemented in the Canadian Geospatial Data Infrastructure Pilot. + + + + This OWS-9 Engineering Report documents investigations, findings, lessons learned and +proposed future work for the Data Transmission Management unit, invented and +prototyped in OWS-9. +The purpose of the Data Transmission Management unit is to optimize, customize and +make reliable the information exchange between the aircraft and the different web +services on the ground. + + Thibault Dacla; Eriza Hafid Fazli; Charles Chen; Stuart Wilson - Incident Management Information Sharing (IMIS) Internet of Things (IoT) Architecture Engineering Report + OWS-9 Data Transmission Management + 12-163 - 2018-04-26 - The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives. -• Apply Open Geospatial Consortium (OGC) principles and practices for collaborative development to existing standards and technology to prototype an IoT approach to sensor use for incident management. -• Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability. -• Develop profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability. -• Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario. + + OGC® OWS-9 Data Transmission Management + + 12-163 + 2013-06-18 + + + + + 2020-02-24 + 18-009 + + + + The Open Geospatial Consortium (OGC) and the Department of Science & Technology (DST) under the Government of India conducted the OGC India Plugfest 2017 (OIP-2017). The OIP-2017 was targeted at enhancing the interoperability among geospatial products and web services based on OGC standards within the Indian Geospatial Information (GI) community. The successful conclusion of OIP-2017 will assist National Spatial Data Infrastructure (NSDI) under DST to provide guidance on best practices using OGC standards for development of applications in several important & flagship schemes/programmes of the Government such as Smart Cities, Atal Mission for Rejuvenation through Urban Trasnformation (AMRUT); National Land Records Moderinisation Programme (NLRMP); Clean India (Swatchh Bharat – Urban & Rural); National Mission on Clean Ganga; Compensatory Afforestation Fund Management & Planning Authority (CAMPA); State SDIs; Digital India, and others. +This engineering report written jointly by OGC and DST is addressed to both the domestic (Indian) and international audiences. +OIP-2017 was funded by the OGC India Foundation with supporting OGC staff resources from the OGC Innovation Program. - 16-014r2 - Incident Management Information Sharing (IMIS) Internet of Things (IoT) Architecture Engineering Report + 18-009 + OGC India Plugfest - 2017 (OIP-2017) Engineering Report + OGC India Plugfest - 2017 (OIP-2017) Engineering Report + + + P S Acharya, Scott Simmons, A Kaushal, M K Munshi - - 2021-07-02 + + Topic 20 - Observations and Measurements + Simon Cox + + Topic 20 - Observations and Measurements + 10-004r3 + 10-004r3 + 2013-09-17 - Roger Lott - - 18-005r5 - This document is identical in normative content with the latest edition (2019) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2019]. + + This International Standard defines a conceptual schema for observations, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities. +Observations commonly involve sampling of an ultimate feature of interest. This International Standard defines a common set of sampling feature types classified primarily by topological dimension, as well as samples for ex-situ observations. The schema includes relationships between sampling features (sub-sampling, derived samples). +This International Standard concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation. + - 18-005r5 - Topic 02 - Referencing by coordinates Corrigendum - Topic 2 - Referencing by coordinates Corrigendum - - - - OWS-5 WCS JPIP Coverage Subsetting Engineering Report - 07-169 - - - - 07-169 - + - This OGC document represents an OWS-5 SWE thread Engineering Report on sub-setting georeferencable imagery. It discusses how to handle georeferencable imagery in the JPEG2000 format as well as using JPIP within the WCS-T and the SWE set of services. - 2008-09-12 - OWS-5 WCS JPIP Coverage Subsetting Engineering Report - Steven Keens - - - - - - - The OpenGIS® Geospatial eXtensible Access Control Markup Language Encoding Standard (GeoXACML) defines a geospatial extension to the OASIS standard “eXtensible Access Control Markup Language (XACML)” [www.oasis-open.org/committees/xacml/]. This extension incorporates spatial data types and spatial authorization decision functions based on the OGC Simple Features[http://www.opengeospatial.org/standards/sfa] and GML[http://www.opengeospatial.org/standards/gml] standards. GeoXACML is a policy language that supports the declaration and enforcement of access rights across jurisdictions and can be used to implement interoperable access control systems for geospatial applications such as Spatial Data Infrastructures. GeoXACML is not designed to be a rights expression language and is therefore not an extension of the OGC GeoDRM Reference Model (Topic 18 in the OpenGIS® Abstract Specification [http://www.opengeospatial.org/standards/as]). - Geospatial eXtensible Access Control Markup Language (GeoXACML) Version 1 Corrigendum - 11-017 - Andreas Matheus, Jan Herrmann - - 2011-05-12 - Geospatial eXtensible Access Control Markup Language (GeoXACML) Version 1 Corrigendum - 11-017 + + 19-015 + OGC Testbed-15: Federated Cloud Provenance ER + 19-015 + 2020-02-12 + The emergence of Federated Cloud processing and ‘Big Data’ have raised many concerns over the use to which data is being put. This led to new requirements for methodologies, and capabilities which can address transparency and trust in data provenance in the Cloud. Distributed Ledger Technologies (DLTs) and more specifically blockchains, have been proposed as a possible platform to address provenance. This OGC Testbed 15 Engineering Report (ER) is a study of the application of DLTs for managing provenance information in Federated Clouds. + + + OGC Testbed-15: Federated Cloud Provenance ER + + Stephane Fellah - - OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV) + + 12-128r10 + + OGC® GeoPackage Encoding Standard - + + 2014-02-10 + - 2015-02-17 - 14-084r2 - This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange. - Moving Features Encoding Extension: Simple Comma Separated Values (CSV) - 14-084r2 - - Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf - + 12-128r10 + GeoPackage Encoding Standard + Paul Daisey + This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. +<br /><br /> +For the online version of the standard and the developer resources, visit <a href=http://www.geopackage.org/>http://www.geopackage.org/</a> - - The Specification Model - Standard for Modular specifications - 08-131r3 - + - 2009-10-19 - - 08-131r3 - This standard contains requirements for writing standards to be used for any document whose -eventual purpose is the specification of requirements for software, services or data structures. - + + This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of that document for a general overview. + Carl Reed + + 16-009r5 + Volume 6: OGC CDB Rules for Encoding Data using OpenFlight + Volume 6: OGC CDB Rules for Encoding Data using OpenFlight + 16-009r5 - The Specification Model - Standard for Modular specifications - Policy SWG + + 2021-02-26 - - 19-030r1 - Mixed Reality to the Edge Concept Development Study + + This OGC® document describes the architecture implemented in the OWS-8 Aviation thread, including general workflows. The document contains a summary description of the various components within the architecture. An introduction to the Access Control System is provided. Furthermore, the document describes relevant aspects of handling events and notifications. Lessons learned – for example regarding the AIXM Temporality Model – as well as scenarios and accomplishments are documented as well. - - - 19-030r1 + + Johannes Echterhoff + OWS-8 Aviation Architecture Engineering Report + 11-093r2 + 2011-12-19 - OGC Mixed Reality to the Edge Concept Development Study - - Mixed Reality (MR), also referred to as hybrid reality, is the merging of real and virtual worlds to produce new environments and visualizations where physical and digital objects co-exist and interact in real time. MR has great potential in enhancing situation awareness and otherwise augmenting the experiences and performance of humans on the go. - -This OGC Engineering Report summarizes information and findings collected during the Mixed Reality at the Edge Concept Development Study (CDS). Specifically, this report presents the significant findings concerning the state-of-the-art and potential of employing MR in modern systems, with a focus on discussing the state of needed interoperability and standards. - -The term mixed reality was originally introduced in a 1994 paper by Paul Milgram and Fumio Kishino, A Taxonomy of Mixed Reality Visual Displays. What is mixed reality?. - 2019-08-20 - Carl Reed - - - 14-007 - This document is a deliverable of the OGC Testbed 10 (Testbed-10). Its contents cover the summary of the work carried out regarding the creation and evaluation of generated data bindings for the Aeronautical Information Exchange Model (AIXM) for established programming languages. -Suggested additions, changes, and comments on this draft report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document. - - 14-007 - Testbed 10 Report on Aviation Binding AIXM to Development Tools - Matthes Rieke - 2014-07-15 - OGC® Testbed 10 Report on Aviation Binding AIXM to Development Tools + + 11-093r2 + OWS-8 Aviation Architecture Engineering Report + + + + + 2017-08-16 - - - + 16-102r2 + + OGC InfraGML 1.0: Part 2 - LandInfra Facilities and Projects - Encoding Standard + 16-102r2 + InfraGML 1.0: Part 2 - LandInfra Facilities and Projects - Encoding Standard + + This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. +InfraGML is published as a multi-part standard. This Part 2 addresses the Facility and Project Requirements Classes from LandInfra. + Paul Scarponcini - - Doug Nebert + + This document specifies the interface to an Image Geopositioning Service that adjusts the georeferencing coordinate transformations of multiple images. This adjustment is normally done using a photogrammetric triangulation process, although other methods could be used. Such triangulation adjusts the parameter values of the image georeferencing coordinate transformations using a least-squares fitting process to measured image positions with known error statistics. + Image Geopostioning Service + 06-054r1 + OpenGIS Image Geopostioning Service + Arliss Whiteside + + - - 07-010 - - - Revision Notes for Corrigendum for OpenGIS 07-006: Catalogue Services, Version 2.0.2 - 07-010 - Revision Notes for Corrigendum for OpenGIS 07-006: Catalogue Services, Version 2.0.2 - This document is a corrigendum for OGC Document 04-021r3. All changes described herein are published in OGC Document 07-006r1. - 2007-06-19 - + 2006-07-12 + 06-054r1 + + - + + Roland M. Wagner + 2009-10-13 + + + GeoRM Role Model + 09-123 + GeoRM Role Model + The scope of this document is the update and the definition of GeoRM roles as a sub model of the GDI.NRW reference model (process model and architecture model). Key relationships are defined between these roles. + + 09-123 - + + + + + GeoPackage Elevation Extension Interoperability Experiment Engineering Report + 16-094r3 + + + OGC GeoPackage Elevation Extension Interoperability Experiment Engineering Report + 2017-08-18 + Micah Brachman + his OGC Engineering Report (ER) describes the setup, experiments, results and issues generated by the GeoPackage Elevation Extension Interoperability Experiment (GPKG-EE IE). The goal of the GPKG-EE IE was to implement and test a proposed elevation extension to the OGC GeoPackage Encoding Standard (12-128r1). The proposed elevation extension was successfully implemented by several IE participants and was demonstrated using both 2-Dimensional (2D) and 3-Dimensional (3D) software clients at the Washington, DC OGC Technical Committee (TC) meeting in [March 9, 2016]. This ER concludes with several recommendations for addressing remaining technical issues that must be resolved in order to complete a candidate GeoPackage Elevation Extension standard. + - - 12-154 - OWS-9 OWS Innovations GMLJP2 for National Imagery Transmission Format (NITF) Engineering Report - 12-154 - OWS-9 OWS Innovations GMLJP2 for National Imagery Transmission Format (NITF) Engineering Report - Darko Androsevic - This OGC® document provides mapping of the national imagery transmission format (NITF) version 2.1 format and NITF tagged record extensions (TRE) to GMLJP2 v2.0 (draft) format. -This Engineering Report was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative. -This document further describes study results of analyses of NITF and NITF extensions (TRE) capabilities and how they can be supported by GMLJP2 2.0 (draft). This activity was a part of the OGC OWS-9 Innovations thread. - - 2013-02-05 + 16-094r3 - - Cliff Kottman - 99-100r1 - Topic 0 - Overview - Topic 0 - Overview - - + + + Doug Nebert, Arliss Whiteside, Peter Vretanos + Catalogue Service Implementation Specification + 07-006r1 + 07-006r1 + OpenGIS Catalogue Service Implementation Specification + 2007-04-20 + The OpenGIS® Catalogue Services Interface Standard (CAT) supports the ability to publish and search collections of descriptive information (metadata) about geospatial data, services and related resources. Providers of resources use catalogues to register metadata that conform to the provider's choice of an information model; such models include descriptions of spatial references and thematic information. Client applications can then search for geospatial data and services in very efficient ways. +See also the OGC Catalogue 2.0 Accessibility for OWS-3 Discussion Paper [http://www.opengeospatial.org/standards/dp], the OWS-4 CSW ebRIM Modelling Guidelines Interoperability Program Report (IPR) [www.opengeospatial.org/standards/dp] and the OpenGIS® Catalogue Service Interface Standard 2.0.1 - FGDC CSDGM Application Profile for CSW (Best Practice) [http://www.opengeospatial.org/standards/bp]. + - - 1999-06-23 - 99-100r1 - - Introduction and roadmap to the Abstract specification. - + + + + - - Gobe Hobona - OGC API – Maps Sprint 2020: Summary Engineering Report + + K. Navulur, M.C. Abrams + + Standardizing a Framework for Spatial and Spectral Error Propagation + 20-088 - 20-090 - OGC API – Maps Sprint 2020: Summary Engineering Report + This OGC Discussion Paper presents a proposal that recommends the development of Open Geospatial Consortium (OGC) standards that define a framework for location-based service metrics that inform the spatial, spectral, and temporal errors associated with various data sources. This paper discusses current industry practices on spatial errors, spectral errors, and error propagation. The paper also presents a proposed framework and a recommended study effort. + + 2021-02-15 + + 20-088 + Standardizing a Framework for Spatial and Spectral Error Propagation + + + + Paul Daisey + 09-140r2 + OGC® NSG Plugweek Engineering Report + + OGC® NSG Plugweek Engineering Report + The Open Geospatial Consortium (OGC®) conducted a series of tests that examined the interoperability, suitability and performance of National System for Geospatial- Intelligence (NSG) Profiles provided by the National Geospatial-Intelligence Agency (NGA) of four OGC Standards, Web Map Service (WMS), Web Feature Service (WFS), Web Coverage Service (WCS), and Catalog Service (CAT). In the study, vendors, users, and other interested parties conducted Technology Integration Experiments (TIEs) and mutually refined clients, services, interfaces and protocols in the context of a hands-on engineering experience expected to shape the future NGA, NSG and Geospatial Intelligence (GEOINT) web based distribution. + 2010-07-30 + + 09-140r2 - - This OGC Engineering Report (ER) documents the results and recommendations from a code sprint that was held from 28 to 29 July 2020 to advance the development of the draft OGC API – Maps Standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application, or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The OGC API - Maps Sprint was an online virtual event. The sprint was sponsored by Ordnance Survey. - 2021-01-18 - 20-090 - + + - - - Testbed-12 OWS Common Security Extension ER - 16-048r1 - - The OGC suite of standards address the interoperable exchange of geographic information. The Web Service Implementation Standards define the discovery, delivery, and processing services that make information exchange possible. Common aspects of those Web Service standards have been collected into the OGC Web Services Common standard. While there are multiple versions of OWS Common, and flexibility in how it is applied, this combination of standards does enable interoperability. + + Testbed-12 OWS Context: JSON, JSON-LD and HTML5 ER + 16-053r1 + At the time of finalizing this ER the OGC TC has approved the OWS Context JSON encoding that is available here: http://www.opengeospatial.org/standards/owc This is the second encoding proposed for the OWS context standard precided by the Atom Encoding [OGC 12-084r2]. The OWS Context JSON enconding is based on the GeoJSON IETF standard [RFC7946]. The standard is a combination of two approaches: -However, OWS Common neglected to address security. As soon as a service endpoint (an OGC Web Service instance) is secured, there is no guarantee of interoperability. +mapping between the OWS Context conceptual model [12-080r2] to the basic structure of a GeoJSON file. -The OWS Common - Security Standards Working Group (SWG) was approved by the TC in September 2015 (http://www.opengeospatial.org/projects/groups/comsecurityswg). It held its first meeting during the December 2015 TC meetings. The objective of this SWG to define an extension to the existing OWS Common to ensure interoperability between a secured service instance and client. This OWS Common Security Extension adds content to the standard regarding the implementation of security controls in such a way as to preserve interoperability. These additions will be in two areas. The first extension will provide more detail on the use of the HTTP protocol, particularly as it related to security controls. The second extension will address discovery and negotiation of security controls. This will provide an annotation model for the Capabilities document to enable a service provider to specify the security implemented at a service instance (endpoint). +a direct conversion of the rest of the atom keys and the specific OWS Context XML into JSON following OGC 14-009r1. -This ER shall serve as the technical background to the OWS Common - Security SWG to ensure that the standard that is to be created is comprehensive and suitable for all OGC Web Services standards, to overcome the interoperability hurdle, and - at the same time - maintain backwards compatibility. +The conversion was designed with current GeoJSON viewers in mind (including the one embedded in GitHUB) and making possible that they can visualize a OWS Context GeoJSON file without any modifications. + +This ER focus on describing another encoding (a 3rd alternative) that allows for exposing geospatial resources on the web in a way that web browsers and search engines can better understand. It is widely known that HTML was designed with the linking capacity in mind. Both, users reading HTML and automatic crawlers, transverse links constantly. HTML seems the natural selection for linking geospatial data on the web. The question is how to complement the linking mechanism with some additional metadata that search engines could use for indexing. A solution could come from a mechanism which web search engines already have agreed to use for better indexing: schema.org. + +Schemna.org proposes three enconding for their data model: Microdata, RDFa and JSON-LD. The reader might easily get confused by the fact that OGC approved a JSON encoding for OWS context and another JSON encoding emerges in this document. This ER is NOT proposing to replace or modify the currently approved JSON enconding for OWS context based on GeoJSON. The intention is to map the OWS Context model into the schema.org model to recognize that they are very similar and propose a encoding in HTML5 that can be done in the 3 alternative proposed by schema.org. - 2017-03-10 - 16-048r1 - Andreas Matheus + + 2017-06-16 + + Joan Masó + Testbed-12 OWS Context: JSON, JSON-LD and HTML5 ER + - - Testbed-12 OWS Common Security Extension ER + 16-053r1 - - 14-065r1 - WPS 2.0.1 Interface Standard: Corrigendum 1 + + 1999-04-04 + 99-114 - - 2015-10-05 - - 14-065r1 - OGC® WPS 2.0.1 Interface Standard: Corrigendum 1 - - - Matthias Mueller - In many cases geospatial or location data, including data from sensors, must be processed before the information can be used effectively. The OGC Web Processing Service (WPS) Interface Standard provides a standard interface that simplifies the task of making simple or complex computational processing services accessible via web services. Such services include well-known processes found in GIS software as well as specialized processes for spatio-temporal modeling and simulation. While the OGC WPS standard was designed with spatial processing in mind, it can also be used to readily insert non-spatial processing tasks into a web services environment. - -The WPS standard provides a robust, interoperable, and versatile protocol for process execution on web services. It supports both immediate processing for computational tasks that take little time and asynchronous processing for more complex and time consuming tasks. Moreover, the WPS standard defines a general process model that is designed to provide an interoperable description of processing functions. It is intended to support process cataloguing and discovery in a distributed environment. + Topic 14 - Semantics and Information Communities + 99-114 + + + Cliff Kottman + + The OpenGIS notion of Information Communities was devised to enable groups such as ecologists and civil engineers to efficiently manage the semantics (or feature schema mismatches) of their own geodata collections and get maximum benefit from each other's geodata collections, despite semantic differences. + Topic 14 - Semantics and Information Communities + + + + Feature data tiling, colloquially referred to as 'vector tiling', is a data delivery method that allows for large vector feature datasets to be systematically split into subsets or tiles [1]. This engineering report (ER) presents an extension specification for publishing of vector tiles data through an Application Programming Interface (API) that conforms to the emerging version 3.0 of the Web Feature Service (WFS) standard. The core of the WFS 3.0 standard offers direct fine-grained access to geospatial information at the feature level. The WFS standard specifies discovery and query operations for web services that publish feature data. Extensions to the WFS 3.0 Core API offer other capabilities such as transaction operations. - - - 16-038 + + Panagiotis (Peter) A. Vretanos + 18-078 + WFS 3.0 Vector Tiles Extension Engineering Report + OGC Vector Tiles Pilot: WFS 3.0 Vector Tiles Extension Engineering Report + + 2019-02-11 + 18-078 + - - - 16-038 - Testbed-12 NSG GeoPackage Profile Assessment Engineering Report - Testbed-12 NSG GeoPackage Profile Assessment Engineering Report - Chris Clark - 2017-05-12 - - The National System for Geospatial-Intelligence (NSG) GeoPackage Profile defines and tailors the implementable provisions prescribed for the NSG for a GeoPackage based on the OGC GeoPackage encoding standard. The profile provides detailed directions on how to use the clauses, options and parameters defined in the base GeoPackage standard. The goal is to ensure that NSG GeoPackages, GeoPackage SQLite Extensions, and supporting utilities and services fulfill their intended purposes and are fit for use. - -The goal of this Engineering Report (ER) is to assess whether requirements as specified in the proposed profile are specific enough to allow for any two independent GeoPackage implementers to produce and consume interoperable NSG GeoPackages. Concerns with the profile are outlined and recommendations for improvement are provided. Thoughts on the viability of the profile approach and guidance on how the profile could apply to Vector Tiling are also provided. - - This Discussion Paper describes an interface specification for a web coordinate transformation service that now builds on version 1.1 of the OWS Common Specification [OGC 06-121r3]. All versions of this document specify an - - - Web Coordinate Transformation Service - - Arliss Whiteside, Markus U. M - 07-055r1 - Web Coordinate Transformation Service - - 2007-10-09 + + This document describes a conceptual model, logical model, and GML/XML encoding schema for the exchange of borehole related data and especially all the elements that are positioned along a borehole trajectory. In addition, this document provides GML/XML encoding instances documents for guidance + 19-075r1 + Borehole Interoperability Experiment Engineering Report + 19-075r1 - - 07-055r1 - - - - - OWS-5 Engineering Report on WCPS - 07-166r2 - 2008-08-04 - OGC OWS-5 Engineering Report on WCPS + + 2020-05-06 + + Sylvain Grellet, Eric Boisvert, Bruce Simons, Jean-François Rainaud, Henning Lorenz, Rainer Haener + OGC Borehole Interoperability Experiment Engineering Report + + + + + 2017-02-23 + 16-009r3 + + 16-009r3 + Volume 6: OGC CDB Rules for Encoding Data using OpenFlight + Volume 6: OGC CDB Rules for Encoding Data using OpenFlight - Peter Baumann - - This document represents the Engineering Report for the WCPS activity within the OWS-5 SWE thread. It summarizes tasks and outcomes. - 07-166r2 + + + + This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of that document for a general overview. + Carl Reed - + - OpenSearch Geospatial Extensions Draft Implementation Standard - 09-084r1 - - Jo Walsh, Pedro Gonçalves, Andrew Turner - - - The OpenSearch specification originates in a community effort built around Amazon's A9.com. It was intended to allow syndication of search results that could then be aggregated by one large index. The OpenSearch specification is made available under the Creative Commons Attribution-Sharealike 2.5 license. In addition, the OASIS Search Web Services group is publishing an Abstract Protocol Definition of the interface or “binding”, which coincides with the community specification published at http://opensearch.org. In 2007, Andrew Turner proposed a set of geospatial extensions through OpenSearch.org. - OpenSearch Geospatial Extensions Draft Implementation Standard - 2009-10-13 - 09-084r1 + + + 15-004 + Common DataBase Volume 2 Appendices + The Common DataBase (CDB) Specification provides the means for a single, versionable, simulation-rich, synthetic representation of the earth. A database that conforms to this Specification is referred to as a Common DataBase or CDB. A CDB provides for a synthetic environment repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB can be used as a common on-line (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks; in this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. +The application of CDB to future simulator architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the HLA/FOM and DIS protocols, the application of the CDB Specification provides a Common Environment to which inter-connected simulators share a common view of the simulated environment. +The CDB Specification is an open format Specification for the storage, access and modification of a synthetic environment database. The Specification defines the data representation, organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The Specification makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. +The CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. It encompasses the terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the synthetic environment includes the specific attributes of the synthetic environment data as well as their relationships. +A CDB contains datasets organized in layers, tiles and levels-of-detail; together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB is specifically tailored for real-time applications. + + 2015-07-22 + David Graham + 15-004 + OGC Common DataBase Volume 2 Appendices + - - 2004-06-17 - OWS Common Recomendation Paper - 04-016r3 - This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses. + + The geospatial community has had an on-going challenge with being able to share data and compute resources in dynamic, collaborative environments that span different administrative domains. For these types of requirements, the concept of federation has been developed. The near-term goal of the Federated Cloud task in OGC Testbed-14 is to demonstrate a specific data-sharing scenario among two or more administrative domains using existing security tooling, e.g., OpenID Connect and OAuth. The main details of this work are reported as part of the OGC Testbed-14 Security Engineering Report (ER) cite:[SecurityER]. This Federated Cloud Engineering Report (ER) dovetails with the Security ER to: + +Coordinate across all federation-related tasks in Testbed-14, including the Earth Observation Cloud and Workflow tasks, + +Understand the overall federation design space, + +Analyze and critique the scope, trade-offs and limitations of the federation capabilities being built and demonstrated in Testbed-14, + +Identify and prioritize possible incremental development tasks for subsequent testbeds, and + +Liaison with groups external to OGC, such as the National Institute of Standards and Technology (NIST)/Institute of Electrical and Electronics Engineers (IEEE) Joint Working Group on Federated Cloud, to promote the further development and adoption of federated capabilities, and ultimately international standards. + + - - Arliss Whiteside + Federated Clouds Engineering Report + 18-090r1 - - 04-016r3 - - OWS Common Recomendation Paper + Dr. Craig A. Lee + 2019-03-05 + + + 18-090r1 + + OGC Testbed-14: Federated Clouds Engineering Report - - + + 16-010r3 + Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2 + + + + Carl Reed + 2017-02-23 + + Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2 + 16-010r3 + + This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store. +Please note that the term “lineal” has been replaced with the term “line” or “linear” throughout this document +Please note that the term “areal” has been replaced with the term “polygon” throughout this document. + + + + + Testbed-12 Catalogue and SPARQL Engineering Report + 16-062 + 2017-05-15 + 16-062 + + This engineering report has been produced by the OGC® Testbed-12 initiative. +The engineering report evaluates interoperability between a variety of +catalogues. The report presents a comparison of the catalogues, with the same +datasets uploaded. The catalogues discussed in the report include services +conforming to Catalogue Service for Web (CSW) version 2.0.2 and 3.0, including +services based on the ebRIM profile of CSW 2.0.2 and an extension of CSW 3.0 +with OpenSearch and SOAP. The engineering report presents results from tests +using a multi-catalogue client to interact with each service. The engineering +report also provides a comparison of CSW and services based on the Data +Catalogue (DCAT) specification covering functionality, expressiveness and +usability of CSW and DCAT. The comparison is supported by a discussion on the +implementation of a SPARQL / GeoSPARQL service. + Gobe Hobona, Roger Brackin - OGC Testbed-16: Aviation Engineering Report - Sergio Taleisnik - - This Testbed-16 Aviation Engineering Report (ER) summarizes the implementations, findings and recommendations that emerged from the efforts of further advancing interoperability and usage of Linked Data within the Federal Aviation Administration (FAA) System Wide Information Management (SWIM) context. The goal of this effort was to experiment with OpenAPI and Linked Data to explore new ways for locating and retrieving SWIM data in order to enable consumers to consume SWIM data more easily in their business applications, and enable the discovery of additional relevant information for their needs. - -Specifically, this ER documents the possibility of querying and accessing data (and its metadata) using Semantic Web Technologies as well as interlinking heterogeneous semantic data sources available on the Web. Together with an analysis on the potential for using OpenAPI-based Application Programming Interface (API) definitions to simplify access to geospatial information, an exploration of solutions for data distribution that complement those currently used by SWIM is presented. - 2021-01-13 - 20-020 - Aviation Engineering Report + + Testbed-12 Catalogue and SPARQL Engineering Report + + + + + Disasters are responsible for major socioeconomic damages. Global initiatives call for the improvement of information technology infrastructure to better share data and advance multinational collaboration. + +The Strengthening Disaster Risk Reduction Across the Americas: A Regional Summit on the Contributions of Earth Observations held on September 3-8 in 2017 in Buenos Aires, Argentina strengthened the collective ability to share the many challenges of disaster risk reduction in Latin America and the Caribbean (LAC) while promoting the awareness and better use of earth observations (EO). + +A simulation exercise took place during the summit. The exercise brought together government, emergency managers, earth observation data providers, academics, non-governmental organizations, and commercial companies. The participants assessed the capabilities and needs of policymakers, regional and on-the-ground decision makers, and learned what information products can be produced, and when and how such products are available. + +This ER describes the description and results of the simulated scenario including the post-exercise activity that captured the lessons learned from the participants. + + + 17-088r1 + Strengthening Disaster Risk Reduction Across the Americas Summit - Simulated Exercise Engineering Report + Strengthening Disaster Risk Reduction Across the Americas Summit - Simulated Exercise Engineering Report - 20-020 + Luis Bermudez + + + + 17-088r1 + + 2018-02-07 - - Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker, Hye-Young Kan + + Carl Reed + 16-005r3 + 2018-12-19 + This document provides the Annexes for the CDB Core: Model and Physical Structure standard. The only exception is Annex A, Abstract Test Suite. The CDB ATS Annex is in Volume 1: Core document. + Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes + - 19-011r4 - OGC® IndoorGML 1.1 - - This OGC® IndoorGML standard specifies an open data model and XML schema of indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modeling indoor spaces for navigation purposes. - 2020-11-05 - 19-011r4 - OGC® IndoorGML 1.1 - - + + 16-005r3 + Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes + - - + + + + Naming of OGC API Standards, Repositories & Specification Elements - - This Testbed-18 (TB-18) Filtering Service and Rule Set Engineering Report (ER) documents best practices identified for features filtering and describes in detail how filtering can be decoupled from data services. Further, this ER describes how filtering rules can be provided to Filtering Services at runtime. - 22-024r2 - 22-024r2 - Testbed-18: Filtering Service and Rule Set Engineering Report - - 2023-06-16 - Sergio Taleisnik - Testbed-18: Filtering Service and Rule Set Engineering Report + + 2021-01-28 + Naming of OGC API Standards, Repositories & Specification Elements + 20-059r4 + 20-059r4 + This document is a policy of the OGC Naming Authority (OGC-NA), a sub-committee of the OGC Technical Committee. The document defines a series of policy requirements for OGC API standards, repositories, definitions, and specification elements. The policy document is intended to be a specialization of the OGC-NA policy on naming specification elements (OGC 10-103). + Gobe Hobona - + + 15-118r1 + 15-118r1 + Incident Management Information Sharing Profile Recommendations for OGC Web Services Engineering Report - Describes modelling requirements for spatial referencing by coordinates. - 2004-02-11 - 04-046r3 - Topic 02 - Spatial Referencing by Coordinates - - 04-046r3 + - Roger Lott - - - - Topic 2 - Spatial Referencing by Coordinates - - - - + 2018-04-23 - 07-027r1 - Local MSD Implementation Profile (GML 3.2.1) - 07-027r1 - - This document contains a data content specification for Local Mission Specific Data (MSD) and is based on the GEOINT Structure Implementation Profile (GSIP) developed by the NGA. This document defines the GML 3.2.1 (ISO 19136) encoding requirements for Local MSD. The structure of the document is based on ISO/DIS 19131 (Geographic Information - - Clemens Portele - 2007-05-25 - Local MSD Implementation Profile (GML 3.2.1) - + Incident Management Information Sharing Profile Recommendations for OGC Web Services Engineering Report + + + The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives: + +• Apply OGC principles and practices for collaborative development to existing standards and technology to prototype an IoT approach to sensor use for incident management; + +• Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability; + +• Develop profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability; and + +• Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario. + +Based on the findings gathered during the implementation and work on these objectives, this Engineering Report describes recommendations on profiles for OGC Web services that shall be used to build IMIS systems. + Simon Jirka, Christoph Stasch - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + 09-025r1 + Web Feature Service 2.0 Interface Standard (also ISO 19142) + OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142) + - 2021-02-26 - 15-005r2 - Defence Profile of OGC Web Feature Service 2.0 - 15-005r2 - - This document defines the DGIWG profile for the ISO -19142:2010 - Web Feature Service (WFS) including changes -made in the OpenGIS Web Feature Service 2.0 Interface -Standard - Corrigendum. The Web Feature Service provides -access to geospatial features in a manner independent of the -underlying data store. - DGIWG - - - Defence Profile of OGC Web Feature Service 2.0 + 09-025r1 + 2010-11-02 + Panagiotis (Peter) A. Vretanos + This International Standard specifies the behaviour of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored parameterized query expressions. +Discovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers. +Query operations allow features or values of feature properties to be retrieved from the underlying data store based upon constraints, defined by the client, on feature properties. +Locking operations allow exclusive access to features for the purpose of modifying or deleting features. +Transaction operations allow features to be created, changed, replaced and deleted from the underlying data store. +Stored query operations allow clients to create, drop, list and described parameterized query expressions that are stored by the server and can be repeatedly invoked using different parameter values. + + + + + 2023-03-28 + OGC API - Common - Users Guide + 20-071 + + Charles Heazel + OGC API - Common - Users Guide + + + + 20-071 + + The OGC API — Common Standard is a multi-part Standard that specifies reusable building-blocks that can be used in the construction of OGC API Standards. The OGC API — Common — Users Guide presents information useful to developers or users of implementations of the OGC API — Common Standard. The information in the Users Guide is not normative. That is, it is not mandatory. However, it may prove essential to fully understand the normative text in the OGC API — Common Standard. The Users Guide is therefore intended to serve as an aid to developers and users. - + + + 2019-02-12 + OGC White Paper on Land Administration + 18-008r1 - - - CDB X Conceptual Model with Prototyping Examples and Recommendations - This Discussion Paper documents the results and recommendations of the rapid prototyping activities conducted during the 3D Geospatial Series Tech Sprint II - OGC CDB 2.0 (aka CDB X). This activity was performed in support of Special Operations Forces (SOF) Future Concepts. This effort hopes to accelerate evolution of the OGC CDB standard to meet the needs of planning, rehearsal, and Mission Command systems providing decision support to Special Operations Forces and enabling SOF tactical and operational advantage. OGC industry standards enable interoperability of geospatial data across systems and applications that SOF Operators and analysts use across warfighting functions. + + + + + Christiaan Lemmen, Peter van Oosterom, Mohsen Kalantari, Eva-Maria Unger, Cornelis de Zeeuw + 18-008r1 + White Paper on Land Administration + This white paper provides an overview of the land administration domain and proposes actions needed for design and develop implementation standards this domain. A close cooperation between the Open Geospatial Consortium (OGC) and ISO is expected to accelerate those developments. -Short summary of CDB X goal: Meeting the requirements for tactical GEOINT that can be used across warfighting functions. - - 2022-08-05 - 20-092 - 20-092 - CDB X Conceptual Model with Prototyping Examples and Recommendations +A huge task is waiting: the establishment of land rights for all: young and old, rich and poor, male and female. Data on many millions of parcels, spatial units, (use-) rights, persons, and parties have to be collected, linked, maintained, and published. Land Administration Systems (LAS) should be designed for maintenance of the dynamic relations between people and land. Existing land administrations require extensions: such as 3D and 4D functionality and datasets, blockchain for transparent transactions, generic processes and integration with remote sensing, and processes to support conversion from social to legal tenure. + +A broad range of geospatial technologies and applications are available. They range from satellite and drone imaging and mapping, to geodesy, precise positioning, geo‐information science, cartography, spatial data infrastructure, and many surveying sub‐disciplines. The scientific and professional disciplines in the geospatial community design, develop, and apply those technologies. Apart from this technical component, a land administration also has a social and legal component. This makes land administration an arena where, apart from the geospatial community, many different scientific and professional disciplines meet. Depending on the stage of development and the level of societal acceptance of the land administration, those disciplines involved may be different. + + + OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard + + + + This OGC GML in JPEG 2000 (GMLJP2) Encoding Standard defines how the OGC/ISO Geography Markup Language (GML) standard is used within JPEG 2000 images and other gridded coverage data for adding geospatial content to imagery. Specifically, this OGC standard defines requirements for the encoding and decoding of JPEG 2000 images and other gridded coverage data that contain XML documents that use GML and GML-based schema. +This document defines the use of GML within the XML boxes of the JP2 and JPX file format for JPEG 2000 (extending the JP2 file format, as specified in [ISO 15444-1] and [ISO 15444-2] in Annexes M and N). Further, an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations is specified. The document also specifies the encoding and packaging rules for GML use in JPEG 2000. + + 08-085r8 + GML in JPEG 2000 (GMLJP2) Encoding Standard + 2018-08-27 + 08-085r8 + Lucio Colaiacomo, Joan Masó, Emmanuel Devys, Eric Hirschorn - David Graham, Carl Reed - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + - - Testbed-13:Asynchronous Services ER - 17-028 - 17-028 - + + + Arliss Whiteside + 2005-01-28 + Recommended XML/GML 3.1.1 encoding of common CRS definitions + 05-011 + Recommended XML/GML 3.1.1 encoding of common CRS definitions + 05-011 + This document recommends standard XML encodings of data defining some commonly-used coordinate reference systems, including geographic, projected, and vertical CRSs. These recommended encodings are based on GML 3.1.1. These common CRS definitions will often be referenced in data transferred between client and server software that implements various standardised interfaces. This specified definition data encoding is expected to be used by multiple OGC Implementation Specifications. That is, each of these specifications is expected to use a subset and/or superset of this recommended definition data. + +The position or location of a point can be described using coordinates. Such coordinates are unambiguous only when the coordinate reference system on which those coordinates are based is fully defined. Each position is described by a set of coordinates based on a specified coordinate reference system. Coordinates are often used in datasets in which all coordinates belong to the same coordinate reference system. This paper specifies XML encoding of data defining some coordinate reference systems. + - - OGC Testbed-13: Asynchronous Services ER - + + - - 2018-01-08 - The goal of this ER is to summarize and compare the results from the activities dealing with asynchronous WFS responses in Testbed 13. Special focus will be given to the specific requirement for automatic notification of users if new or updated information becomes available and to the software components addressing these requirements, i.e. two asynchronous Web Feature Services (NG119 and NG120). - Benjamin Pross, Christoph Stasch + - - 2019-03-06 - OGC Testbed-14: Secure Client Test Engineering Report - 18-030 - Secure Client Test Engineering Report - - - + + OpenSearch Extension for Earth Observation Satellite Tasking: Best Practice + 13-039 + Nicolas Fanjeau, Sebastian Ulrich + 2014-12-29 + OGC® OpenSearch Extension for Earth Observation Satellite Tasking: Best Practice + 13-039 + - - - 18-030 - This Engineering Report (ER) describes the development of compliance tests and their implementation in the OGC Test, Evaluation, And Measurement (TEAM) Engine to validate a client’s ability to make secure requests according to the OGC Web Services Security Candidate Standard. The goal of the candidate standard is to allow the implementation of Information Assurance (IA) controls and to advertise their existence in an interoperable way with minimal impact to existing implementations using a backward-compatible approach. - -This ER covers the following topics from OGC Testbed-14 Compliance Interoperability & Testing Evaluation (CITE) thread: - -developing a client validator to test compliance of client software with the OGC Web Services Security Candidate Standard + + + This document provides a specification of an OpenSearch extension for Earth Observation Satellites Tasking. -capturing the results of two use cases with different authentication methods +This OGC Best Practice is intended to provide a very simple way to task Earth Observation (EO) satellites sensors, to allow simple syndication between, and to provide a basic federated query of related sensors, whereby a single client can query several instances and present a collection of future acquisition as one set. -making recommendations to the OGC Web Services Security Standards Working Group (SWG) based on the experiences made while developing the validator +This document is the result of work undertaken within the European Space Agency (ESA) Heterogeneous Mission Accessibility for Science (HMA-S) project funded by ESA the Long Term Data Preservation (LTDP) program. - - Sara Saeedi - - - 15-107 - Spatial Data on the Web Best Practices +The document was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative (see ‘Normative References’ section) related projects. + + + + + Jürgen Seib, Marie-Françoise Voidrot-Martinez, Chris Little + 16-086r3 + + OGC Best Practice for using Web Map Services (WMS) with Ensembles of Forecast Data + 16-086r3 + Best Practice for using Web Map Services (WMS) with Ensembles of Forecast Data - - Jeremy Tandy, Linda van den Brink, Payam Barnaghi + This document proposes a set of best practices and guidelines for implementing and using the Open Geospatial Consortium (OGC) Web Map Service (WMS) to serve maps which are members of an ensemble of maps, each of which is a valid possible alternative for the same time and location. In the meteorological and oceanographic communities, it is Best Practice to produce a large number of simultaneous forecasts, whether for a short range of hours, a few days, seasonal or climatological predictions. These ensembles of forecasts indicate the probability distributions of specific outcomes. This document describes how to unambiguously specify an individual member of an ensemble, or one of a limited set of map products derived from a full ensemble. +In particular, clarifications and restrictions on the use of WMS are defined to allow unambiguous and safe interoperability between clients and servers, in the context of expert meteorological and oceanographic usage and non-expert usage in other communities. This Best Practice document applies specifically to WMS version 1.3, but many of the concepts and recommendations will be applicable to other versions of WMS or to other OGC services, such as the Web Coverage Service. + - Spatial Data on the Web Best Practices - - 2017-09-28 + + 2018-04-05 - 15-107 - This document advises on best practices related to the publication of spatial data on the Web; the use of Web technologies as they may be applied to location. The best practices presented here are intended for practitioners, including Web developers and geospatial experts, and are compiled based on evidence of real-world application. These best practices suggest a significant change of emphasis from traditional Spatial Data Infrastructures by adopting an approach based on general Web standards. As location is often the common factor across multiple datasets, spatial data is an especially useful addition to the Web of data. - + - Johannes Echterhoff - + Testbed-12 Aviation Semantics Engineering Report + Aleksandar Balaban + This engineering report examines the role of geospatial semantic technology in the domain of civil aviation. Many aeronautical services (providing information on request or processing the data) are based on OGC Web Service specifications. A number of aeronautical services possess geospatial attributes. The aviation services follow OWS Common Service requirements but also have domain specific capabilities. Services metadata is often very relevant for service consumption, especially in the SOA environment of aviation’s System Wide Information Management (SWIM). Therefore, it shall be exposed to consumer stakeholders for either design or runtime service discovery in an efficient, standardized way. + +This ER starts introducing the WSDOM service ontology developed by FAA for semantic service discovery. It proposes several extensions useful for OWS compatible, geospatial aviation services. It combines GeoSPARQL with WSDOM ontology and FAA service classification taxonomies and elaborates the interoperability between ontology based WSDOM and OWS compatible service descriptions. + + Testbed-12 Aviation Semantics Engineering Report + 16-039r2 + 16-039r2 + + 2017-06-19 - - 2015-08-19 - 15-025r2 - Testbed 11 Aviation - Architecture Engineering Report - This OGC® document describes the architecture implemented in the OGC Testbed 11 Aviation thread. - 15-025r2 - - OGC® Testbed 11 Aviation - Architecture Engineering Report + - - - 2008-02-21 - - Bastian Schaeffer - 08-009r1 - OWS 5 SOAP/WSDL Common Engineering Report - OWS 5 SOAP/WSDL Common Engineering Report - This OGC document reports the results achieved in the OWS5 GPW-SOAP/WSDL thread which is focused on creating general recommendations and guidelines for WSDL/SOAP support to existing OGC Web Services. - + + Ingo Simonis + OWS-9: OGC Mobile Apps: Definition, Requirements, and Information Architecture + 12-119r1 + + 12-119r1 + + This engineering report represents the results of the OWS-9 innovations thread on mobile applications. Initially, the goal was to help understanding the requirements for developing standards-based geospatially-enabled mobile applications. The report describes how OGC Enabled Mobile Apps can be integrated into information architectures based on OGC standards. Particular emphasize has been put on the future work section, as it provides valuable recommendations for further standardization work (and, equally important, highlights aspects that could be excluded from standardization) + + + 2013-02-01 + + OWS-9: OGC Mobile Apps: Definition, Requirements, and Information Architecture + + + OGC Web Services (OWS) 3 UGAS Tool + Clemens Portele, Rafael Renkert + - 08-009r1 + + OGC Web Services (OWS) 3 UGAS Tool + 05-118 + 05-118 + + 2006-04-28 + + This document contains a description of the UGAS (UML Application Schema to GML ApplicationSchema conversion) tool development in the decision support services thread (GeoDSS) during the OWS-3 initiative. - + + Cliff Kottman, Arliss Whiteside + Topic 16 - Image Coordinate Transformation Services + Covers image coordinate conversion services. + 00-116 + + 2000-04-24 + + Topic 16 - Image Coordinate Transformation Services + 00-116 + - This document provides a description of the Bulk Data Transfer investigations related to Geography Markup Language (GML) streaming and feature data transportation implemented in the OGC OWS-9 test bed. - -This document extends the concept of Bulk Data Transfer to the dissemination of large payloads consisting of geospatial data sets and/or collections of data sets between machines that are connected via a network. - -This document also describes the delivery of large payloads consisting of geospatial data sets and/or collections of data sets to SpatiaLite/SQLite to store the data for use by mobile applications. - - - - - OWS-9 Engineering Report - SSI - Bulk Data Transfer (GML Streaming) - Jeff Harrison - 2013-03-26 - 12-097 - OWS-9 Engineering Report - SSI - Bulk Data Transfer (GML Streaming) - 12-097 - + - - - Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile - 10-140r2 - OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile - 10-140r2 - 2018-10-04 - The OGC Web Coverage Service (WCS) Application Profile - Earth Observation (EO- WCS) defines a profile of WCS 2.0 [OGC 09-110r4] for use on Earth Observation data. - - - + + 10-087 + OWS-7 Motion Imagery Discovery and Retrieval Engineering Report + + + + 2010-08-18 + This Motion Imagery Discovery and Retrieval Engineering Report (ER) documents the metadata used to tag geolocation of Motion Imagery (MI) for discovery, retrieval and linkage with other data sources over the same location, especially the metadata information required to geometrically co-register multiple motion images at pixel level so that data recorded at different times (e.g., different days) and/or by different providers for common or overlapped FOVs can be compared and pixel level changes among the different images can be accurately detected and delineated. This ER reflects one of the achievements during the OWS 7 Sensor Fusion Enablement (SFE) thread, which builds on the OGC Sensor Web Enablement framework that has achieved a degree of maturity through previous OWS interoperability initiatives and deployments worldwide. - Peter Baumann, Stephan Meissl, Jinsongdi Yu + 10-087 + OWS-7 Motion Imagery Discovery and Retrieval Engineering Report + Wenli Yang, Liping Di + - - Clemens Portele - - 05-117 - Description of the schema tailoring process for the application schema development in the decision support services thread (GeoDSS) during the OWS-3 initiative + + 08-122r2 + Uncertainty Markup Language (UnCertML) + The Uncertainty Markup Language (UncertML) is an XML encoding for the transport and storage of information about uncertain quantities, with emphasis on quantitative representations based on probability theory. + Matthew Williams, Dan Cornford, Lucy Bastin & Edzer Pebesma - Schema Maintenance and Tailoring - 2006-05-02 - 05-117 - Schema Maintenance and Tailoring - + + Uncertainty Markup Language (UnCertML) + + 08-122r2 - + 2009-04-08 + - - - 06-184r2 - - - GeoDRM Engineering Viewpoint and supporting Architecture - 06-184r2 - GeoDRM Engineering Viewpoint and supporting Architecture - This GeoDRM engineering viewpoint document describes use cases and concepts for GeoDRM, as well as references to distributed computing concepts which are not GeoDRM sensu stricto but are required for any GeoDRM implementation. - 2007-08-14 + + 16-023r3 + Testbed-12 Implementing Asynchronous Services Response Engineering Report + Testbed-12 Implementing Asynchronous Services Response Engineering Report + + Most of current OGC specifications define synchronous communication patterns, i.e. after sending a request to an OGC service, clients need to wait for the response. But several applications, e.g. delivery of information about events or executing complex environmental models with long runtime, need asynchronous client-server interaction pattern that do not require clients to keep the connection to the server continuously open in order to wait for responses. At the moment, there are several approaches how to add asynchronous communication to existing OGC services: One option is to use a WPS façade, as the WPS specification already defines asynchronous service responses. Another option is to add extensions to the different specifications and the third option is developed by the OGC Publish-Subscribe Working Group. This ER summarizes and compares the results from the different activities for asynchronous service responses and provides recommendations for future activities. + 16-023r3 + + - Christian Elfers, Roland M. Wagner + 2017-06-30 + Benjamin Pross - + + Luis Bermudez - - - Christian Kiehle, Theodor Foerster - OWS-7 Web Processing Service Profiling Engineering Report - 10-059r2 + 2011-01-03 - 10-059r2 - The overall scope of this OWS-7 Engineering Report is to clarify how to write and register a WPS profile. WPS profiles enable clients to search and identify equivalent WPS-based processes distributed on the web. Therefore, this ER provides guidelines for designing WPS Profiles based on WPS interface specification 1.0.0. - - OWS-7 Web Processing Service Profiling Engineering Report - 2010-08-18 + Ocean Science Interoperability Experiment Phase 1 Report + This OGC Engineering report details lessons learned and best practices defined as part of the Phase 1 Ocean Science Interoperability Experiment (Oceans IE). The Oceans IE was performed to investigate the use of OGC Web Feature Services (WFS) and OGC Sensor Observation Services (SOS) for representing and exchanging point data records from fixed in-situ marine platforms. The activity concluded that for the Oceans community use of in-situ sensors that the OGC Sensor Observation Services (SOS) was better suited than the use of OGC Web Feature Services (WFS) for this purpose. + + 08-124r1 + Ocean Science Interoperability Experiment Phase 1 Report + 08-124r1 + + - - Semantic annotations in OGC standards - 08-167r1 - Semantic annotations in OGC standards - - Patrick Maué - - - 08-167r1 + - - Annotation of Web Services or data compliant to OGC standards refers to the task of attaching meaningful descriptions to the service and the served geospatial data or processes. In this discussion paper we try to extend the expressiveness of such annotations by including more sophisticated (semantic) descriptions. + Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW + 04-017r1 + + 04-017r1 + OGC Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW + Richard Martell + The OGC Catalogue Services 2.0 specification (OGC 04-021) establishes a framework for implementing catalogue services that can meet the needs of stakeholders in a wide variety of application domains. This application profile is based on the CSW schemas for web-based catalogues and it complies with the requirements of clause 11 in OGC 04-021. + - 2009-07-16 + + + 2004-10-12 - - 18-062r2 - OGC API - Processes - Part 1: Core - 2021-12-20 - OGC API - Processes - Part 1: Core - 18-062r2 - + - The OGC API — Processes — Part 1: Core Standard supports the wrapping of computational tasks into executable processes that can be offered by a server through a Web API and be invoked by a client application. The standard specifies a processing interface to communicate over a RESTful protocol using JavaScript Object Notation (JSON) encodings. The standard leverages concepts from the OGC Web Processing Service (WPS) 2.0 Interface Standard but does not require implementation of a WPS. - -By way of background and context, in many cases geospatial or location data, including data from sensors, must be processed before the information can be effectively used. The WPS Standard provides a standard interface that simplifies the task of making simple or complex computational geospatial processing services accessible via web services. Such services include well-known processes found in Geographic Information Systems (GIS) as well as specialized processes for spatiotemporal modeling and simulation. While the WPS standard was designed with spatial processing in mind, the standard could also be used to readily insert non-spatial processing tasks into a web services environment. - -The OGC API — Processes Standard is a newer and more modern way of programming and interacting with resources over the web while allowing better integration into existing software packages. The OGC API — Processes Standard addresses all of the use cases that were addressed by the WPS Standard, while also leveraging the OpenAPI specification and a resource-oriented approach. - -The resources that are provided by a server implementing the OGC API — Processes Standard are listed in Table 1 below and include information about the server, the list of available processes (Process list and Process description), jobs (running processes) and results of process executions. - - Benjamin Pross, Panagiotis (Peter) A. Vretanos - + Catalogue Service Implementation Specification [Catalogue Service for the Web] + Catalogue Service Implementation Specification + 04-021r3 + Doug Nebert - - - - Thomas Forbes, Alberto Olivares, Richard Rombouts - OGC® Testbed-11 Aviation Feature Schema Recommendations Engineering Report + The OpenGIS Catalogue Services Specification defines common interfaces to discover, browse, and query metadata about data, services, and other potential resources. + 2004-08-02 + 04-021r3 + + + OpenGIS Catalogue Service Implementation Specification + OpenGIS Catalogue Service Implementation Specification [Catalogue Service for the Web] + - + + + Semantic annotations in OGC standards + 08-167r2 - 15-026 - Testbed-11 Aviation Feature Schema Recommendations Engineering Report - Developed by EUROCONTROL, the Aviation Feature Schema (AFX) is a template for -application schemas to implement by adding their operational attributes. For example, the -Airport Mapping format can be implemented by extending AFX. The AFX defines -concepts of geometry and temporality through predefined classes and properties. -Therefore, these elements need not be redefined by application schemas. This means -implementations of the AFX abide by the same structure, therefore aiding interoperability -and allowing the rapid development of schemas. The AFX schema is designed to be -generic and easily reusable and it is not intended to replace the standard aviation models -such as WXXM and AIXM. -This Engineering Report assesses the suitability of the AFX as a template for lowering -the GIS entry level for aviation data, providing recommendations of suitability and areas -of improvement. The report is aimed at system and client developers that shall use AFX. - 15-026 - 2015-10-30 - - + + + + Semantic annotations in OGC standards + 08-167r2 + + 2012-10-10 + Frédéric Houbie, Philippe Duchesne, Patrick Maué + In this OGC Best Practice, the concept of semantic annotations is introduced. Annotation of Web Services or data compliant to OGC standards refers to the task of attaching meaningful descriptions to the service and the served geospatial data or processes. - - - - - Testbed-13: NAS Profiling Engineering Report - 17-020r1 - 2018-01-26 - The National System for Geospatial-Intelligence (NSG) Application Schema (NAS) is an ISO 19109 compliant application schema that defines the conceptual model for identifying and encoding feature data in the U.S. National System for Geospatial-Intelligence (NSG). NGA utilizes the open source software tool ShapeChange as an integral piece in NAS development. This tool is used to take NAS-based UML models and create Extensible Markup Language (XML) and Resource Description Framework (RDF) based schemas. Testbed-12 began development of capabilities for extracting profiles supporting specific mission functions from the full NAS content. Testbed-13 further refined the approach to NAS Profiling by investigating how a specific profile (Urban Military Profile) can be processed in an automated way and used to derive implementation schemas for the OGC standards CDB and CityGML. - -This OGC Engineering Report describes: - -The specification of a NAS-based Military Urban Profile as a Unified Modeling Language (UML) model (chapter 5); - -How mission-specific sub-profiles can be specified and maintained using ShapeChange and the new ShapeChange Profile Management Tool (chapter 6); and - -How the model and profile information are processed to derive output for - -a CDB data store (chapter 7, chapter 8) and - -a CityGML Application Domain Extension (chapter 9). - -This work provides insights into: - -The requirements and constraints on managing profiles of complex ISO 19109 compliant application schemas such as the NAS; and - -Using a model-driven approach to generate implementation schemas of an ISO 19109 compliant application schema profile for different environments. - -The target audience of this document is anyone interested in these topics. The implementation environments discussed in this report are the OGC standards CDB and CityGML. The profiled application schema is the NAS. - -This report assumes that readers are familiar with the key concepts and technologies discussed in this document. This document does not provide an introduction to them, but the table below provides a brief summary and pointers to more information. - Johannes Echterhoff, Clemens Portele - OGC Testbed-13: NAS Profiling Engineering Report - - 17-020r1 - + + Mike Botts, George Percivall, Carl Reed, John Davidson + Carl Reed, Mike Botts, George Percivall, John Davidson + OGC Sensor Web Enablement: Overview and High Level Architecture + OGC® Sensor Web Enablement: Overview And High Level Architecture + 07-165r1 + + OGC Sensor Web Enablement: Overview and High Level Architecture + Sensor Web Enablement: Overview And High Level Architecture + 07-165r1 + This OGC White Paper provides a high-level overview of and architecture for the Open Geospatial +Consortium (OGC) standards activities that focus on sensors, sensor networks, and a concept called the +“Sensor Web”. This OGC focus area is known as Sensor Web Enablement (SWE). + A sensor network is a computer accessible network of many, spatially distributed devices using sensors to monitor conditions at different locations, such as temperature, sound, vibration, pressure, motion or pollutants[1]. A Sensor Web refers to web accessible sensor networks and archived sensor data that can be discovered and accessed using standard protocols and application program interfaces (APIs). + + 2013-04-02 + + + - + + 2005-05-03 + - - 16-086r3 - Best Practice for using Web Map Services (WMS) with Ensembles of Forecast Data - This document proposes a set of best practices and guidelines for implementing and using the Open Geospatial Consortium (OGC) Web Map Service (WMS) to serve maps which are members of an ensemble of maps, each of which is a valid possible alternative for the same time and location. In the meteorological and oceanographic communities, it is Best Practice to produce a large number of simultaneous forecasts, whether for a short range of hours, a few days, seasonal or climatological predictions. These ensembles of forecasts indicate the probability distributions of specific outcomes. This document describes how to unambiguously specify an individual member of an ensemble, or one of a limited set of map products derived from a full ensemble. -In particular, clarifications and restrictions on the use of WMS are defined to allow unambiguous and safe interoperability between clients and servers, in the context of expert meteorological and oceanographic usage and non-expert usage in other communities. This Best Practice document applies specifically to WMS version 1.3, but many of the concepts and recommendations will be applicable to other versions of WMS or to other OGC services, such as the Web Coverage Service. + The OpenGIS® Filter Encoding Standard (FES) defines an XML encoding for filter expressions. A filter expression logically combines constraints on the +properties of a feature in order to identify a particular subset of features to be operated upon. For example, a subset of features might be identified to render them in a particular color or convert them into a user-specified format. Constraints can be specified on values of spatial, temporal and scalar properties. An example of a filter is: Find all the properties in Omstead County owned by Peter Vretanos. + +This standard is used by a number of OGC Web Services, including the Web Feature Service [http://www.opengeospatial.org/standards/wfs], the Catalogue Service [http://www.opengeospatial.org/standards/cat] and the Styled Layer Descriptor Standard [http://www.opengeospatial.org/standards/sld]. - OGC Best Practice for using Web Map Services (WMS) with Ensembles of Forecast Data - 16-086r3 - - - - - Jürgen Seib, Marie-Françoise Voidrot-Martinez, Chris Little - 2018-04-05 + Filter Encoding Implementation Specification Corrigendum 1 + 04-095c1 + + + Peter Vretanos + Filter Encoding Implementation Specification Corrigendum 1 + 04-095c1 + + - - 19-079r2 - OGC API - Features - Part 3: Filtering - + + Introduction and roadmap to the Abstract specification. + + + + + Topic 0 - Overview + + Topic 0 - Overview + 04-084 + 2005-06-27 + Carl Reed + 04-084 + + - 19-079r2 - OGC API - Features - Part 3: Filtering + + OGC OpenSearch Extension for Correlated Search + OpenSearch Extension for Correlated Search + 13-068 + + + 2014-02-24 + This OGC discussion paper presents an OpenSearch query protocol extension for the +execution of correlation queries between different Search Feeds. Services that support the +OpenSearch Specification and Correlation extension defined in this document are called +OpenSearch Correlation Services. With the proposed extensions it will be possible to +execute distributed queries with correlation and search criteria defining the results +aggregation. - - 2024-07-26 - - OGC API Standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks. - -OGC API - Features provides API building blocks to create, modify and query features on the Web. OGC API - Features is comprised of multiple parts. Each part is a separate standard. - -A fundamental operation performed on a collection of features is that of filtering in order to obtain a subset of the data which contains feature instances that satisfy some filtering criteria. Part three of the OGC API - Features Standard defines query parameters (filter, filter-lang, filter-crs) to specify filter criteria in a request to an API and the Queryables resource that declares the properties of data in a collection that can be used in filter expressions. - Panagiotis (Peter) A. Vretanos, Clemens Portele + Pedro Gonçalves + 13-068 + - + + 2023-01-03 + + 22-031r1 + 22-031r1 + Testbed-18: Reproducible FAIR Best Practices Engineering Report - Sam Meek - OGC Testbed-17: UML Modeling Best Practice Engineering Report - - 21-031 - UML Modeling Best Practice Engineering Report - 21-031 - This OGC Best Practice provides readers with guidance on how to use the Unified Modeling Language (UML) within the scope of OGC work. Recently there has been a move to a resource-based approach for OGC Application Programming Interface (API) definition through the OpenAPI Specification and away from the service-based approach specified in OGC Web Service (OWS) standards. Previously, the interface definitions were almost exclusively XML based, therefore models described using UML class diagrams and conceptual models in general simply mapped 1:1 to derive the XML schema. Using API resources has resulted in the possibility of deriving multiple target technologies from a single standard and therefore, UML model. An additional point of discussion within the OGC is the value added by conceptual modeling using UML. Models included in OGC Standards vary from diagrams only, to conceptual models and model fragments all the way through to Model Driven Architecture (MDA) where UML models are used to directly derive implementable artifacts such as schemas. + Testbed-18: Reproducible FAIR Best Practices Engineering Report + + The OGC Testbed-18 initiative included a discussion exploring the future of open science and building energy interoperability with the task of developing a set of best practices to make the data processing services of Exploitation Platforms both reproducible and follow the FAIR data principles. -UML has been the main modeling language of choice within the OGC, although up until now, there has been little guidance within the OGC on appropriate use of UML. These Best Practices do not seek to govern the use of UML within the OGC as it is recognized that UML is a flexible language that has applications beyond the current OGC doctrine. However, the practices seek to provide guidance to assist in adherence to the following principles: +Portability and reproducibility are key factors for the long-term scientific impact of Earth Observation (EO) data processing applications provided by Exploitations Platforms. The EO application developers lack the tools and guidance to preserve all the elements, algorithms, software, and data resources used to produce the results. Without these elements, reproducibility becomes resubmission within the platform and only while the same platform resources such as data are preserved and available. - Correctness — Adherence to the Object Management Group (OMG) UML standard. - Consistency — UML artifacts should be consistent across OGC Standards and with supporting standards such as those specified by ISO/TC 211. - FAIRness — Findable, Accessible, Interoperable and Reusable models. - Value — Any modeling done, UML or otherwise, should add value to the parent standard. That is, the modeling should do work for the community that is not done elsewhere. -The Practices are as follows: +This Testbed 18 Engineering Report defines a list of requirements and respective best practices to support reproducible Earth Observation science covering the different resources of the Earth Observation Exploitation Platforms such as publications, data, services, products, information, software, or computing environments. - Practice 1: UML models should follow the OMG UML 2.5.1 Standard ratified in 2017. - Practice 2: OGC Conceptual Models should be represented as UML Class diagrams. - Practice 3: OGC Conceptual Models should be platform independent. - Practice 4: OGC Conceptual Models should use concepts consistently across standards. - Practice 5: OGC Standards should contain a UML model at least at the conceptual level of detail. - Practice 6: UML models in OGC Standards should add value. - Practice 7: UML models should describe structure in the engineering process. - Practice 8: Modeling artifacts should be provided in full. - Practice 9: UML models should at least be consistent with supporting text, but ideally normative. - Practice 10: UML tooling should produce interoperable artifacts. - Practice 11: UML can be used for modeling semantics, although there are other technologies that are more appropriate. - Practice 12: OGC UML models should be machine readable (i.e. available in XMI format, in addition to the format of the UML Editor used to create the model). - 2022-02-08 + + + Pedro Gonçalves - - - - 17-066r2 + + This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a “native” storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. + - - Carl Reed - 2022-05-02 - OGC GeoPackage Extension for Tiled Gridded Coverage Data - The GeoPackage Extension for Tiled Gridded Coverage Data” (TGCE) extension (previously titled Elevation Extension) defines how to encode and store tiled regular gridded data, such as a digital elevation model, in a GeoPackage. The tiles contain values, such as elevation, temperature or pressure, and the extension defines two encodings. The PNG encoding uses PNG files to store 16-bit integer values and a scale and offset may be applied to fine-tune the coverage range. To support 32-bit floating point data or binary data, the extension also defines a TIFF encoding. In this encoding, TIFF files are used to store IEEE floating point or a binary data type where the SampleFormat has a value of either 1 (unsigned integer) or 2 (signed integer) AND the BitsPerSample is either 8, 16, or 32. To simplify development, this encoding constrains many of the TIFF options to the minimal set needed to meet the floating-point requirement. The extension also defines two ancillary data tables: one for regular gridded coverages and one for tiles. - - - - - 17-066r2 - OGC GeoPackage Extension for Tiled Gridded Coverage Data - + 12-128r12a + GeoPackage Encoding Standard - With Corrigendum + OGC® GeoPackage Encoding Standard - With Corrigendum + + + Paul Daisey + 12-128r12a + + 2015-04-20 - - This profile defines a restricted but useful subset of XML-Schema and GML to lower the - - GML simple features profile - 05-033r9 - Peter Vretanos - - 05-033r9 - + + + This technical note enhances the OGC GML simple features profile to include circles, circular arc, and corrects the annex numbering, and clarifies how to specify conformance classes. + + OGC Geography Markup Language (GML) simple features profile Technical Note + 11-044 + Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos + + - GML simple features profile - - 2005-07-04 + 2011-05-11 + 11-044 + OGC Geography Markup Language (GML) simple features profile Technical Note - - 15-051r3 + + + - Testbed-11 OGC IP Engineering Report Geo4NIEM Architecture Design and Implementation Guidance and Fact Sheet - 2016-01-25 - Jeff Harrison - Testbed-11 OGC IP Engineering Report Geo4NIEM Architecture Design and Implementation Guidance and Fact Sheet - 15-051r3 - The goal of the Geo4NIEM thread in Testbed 11 was to assess the potential for the National Information Exchange Model (NIEM) to be combined with security tags from Intelligence Community (IC) Data Encoding Specifications for information exchange. The assessment included reviewing Information Exchange Package Documentation (IEPD) populated with relevant content and IC security tags – and then deploying these instance documents on Open Geospatial Consortium (OGC) standards enabled Web Services for testing. The security tags included Information Security Marking Metadata (ISM) and Need-to-Know (NTK) Metadata for secure information exchange. -The assessment included reviewing example IEPDs and performing tests and demonstrations using OGC web services, such as Transactional Web Feature Services (WFS-T), Policy Enforcement Points (PEPs) and OGC Attribute Stores to process geographic feature with NIEM components and security tags. The Test and Demonstration included, but was not limited to, feature retrieval and transactions. Results were documented in this task to provide a preliminary architecture for Geo4NIEM in Testbed 11, and were described in technical detail in other OGC Testbed 11 Engineering Reports. -This document describes background considerations – and an overview of the services, data encodings and access control frameworks that compose the Geo4NIEM Testbed 11 architecture. This document must be reviewed in conjunction with the following Testbed 11 Geo4NIEM ERs: -• 15-048 Testbed11_Engineering_Report_NIEM-IC Data Encoding Specification Assessment and Recommendations -• 15-047 Testbed11_Engineering_Report NIEM-IC Feature Processing API using OGC Web Services -• 15-050 Testbed11_Engineering_Report Test and Demonstration Results for NIEM using IC Data Encoding Specifications - - + + 16-059 + Testbed-12 Semantic Portrayal, Registry and Mediation Engineering Report + This engineering report documents the findings of the activities related to the Semantic Portrayal, Registry and Mediation components implemented during the OGC Testbed 12. This effort is a continuation of efforts initiated in the OGC Testbed 11. This report provides an analysis of the different standards considered during this effort, documents the rendering endpoints extension added to the Semantic Portrayal Service and the migration of the Portrayal metadata to the Semantic Registry, which is aligned with the DCAT REST Service API. We also discuss the integration of the CSW ebRIM for Application Schema with the Semantic Mediation Service, and document the improvements of the SPARQL Extensions, Portrayal and Semantic Mediation ontologies defined in the previous testbed. + + + Stephane Fellah + Testbed-12 Semantic Portrayal, Registry and Mediation Engineering Report + 16-059 + 2017-06-16 + + + + + + The document describes the architecture that was implemented in the Aviation thread of OWS-7. The document provides an overview of the architecture and describes the implemented components. In addition it discusses “eventing” and notification techniques relevant for the aviation domain. + 2010-09-09 + 10-079r3 + OWS-7 Aviation Architecture Engineering Report + OWS-7 Aviation Architecture Engineering Report + Thomas Everding + 10-079r3 + - + + OWS-5 ER: GSIP Schema Processing + 08-078r1 + This OGC® document describes and discusses the OWS-5 enhancements in the process of creating application schemas in support of the NSG from NGA data based on the GEOINT Structure Implementation Profile (GSIP) which has been based on the NSG Application Schema and accompanying NSG Entity Catalog. + + + 2008-07-08 + + OGC® OWS-5 ER: GSIP Schema Processing + 08-078r1 + + + + Clemens Portele + + + 07-068r4 + + Arliss Whiteside + Web Coverage Service (WCS) - Transaction operation extension + 07-068r4 + - - FGDC OGC Application Programming Interface Interoperability Assessment - 17-061 - - Terry Idol - 2020-05-12 - The Federal Geographic Data Committee (FGDC) Application Programming Interface (API) assessment was conducted under the OGC Innovation Program with the goal to develop an in-depth understanding of all the components necessary to enable increased coordination and effectiveness of APIs as applied to geospatial information. FGDC customers have been invited to share their experiences with the use of APIs. From those descriptions, recommendations have been derived that help FGDC to better understand how APIs are currently being generated and if using a more standardized approach to APIs might enable a more robust and optimized service offering. - - FGDC OGC Application Programming Interface Interoperability Assessment - 17-061 + + 2009-01-15 + Web Coverage Service (WCS) - Transaction operation extension + This extension of the WCS standard specifies an additional Transaction operation that may optionally be implemented by WCS servers. This Transaction operation allows clients to add, modify, and delete grid coverages that are available from a WCS server. The Transaction operation request references or includes the new or modified coverage data, including all needed coverage metadata. - - OGC® Aircraft Access to SWIM (AAtS) Harmonization Architecture Report - George Wilber, Johannes Echterhoff, Matt de Ris, Joshua Lieberman - 14-073r1 - - Aircraft Access to SWIM (AAtS) Harmonization Architecture Report - 14-073r1 - - This OGC® document describes the Aircraft Access to SWIM (AAtS) harmonization -architecture developed by a team funded by the FAA and led by the Open Geospatial -Consortium (OGC). + - + 16-061 + + 2017-06-30 + Testbed-12 Aviation SBVR Engineering Report + 16-061 - 2014-11-03 + This engineering report (ER) is a deliverable of the OGC Testbed 12. It advances previous work in the area of business rules for AIXM 5 based on SBVR. It evaluates the use of geo-spatial operators and constraints in SBVR, including a proof of concept for their automatic interpretation by software. It gives guidelines on how to deal with temporality aspects and how to extend the applicability of SBVR towards filtering expressions and it identifies limitations of the currently available vocabulary. + Testbed-12 Aviation SBVR Engineering Report + + Timo Thomas, Aleksandar Balaban + - - This standard defines the version 3.0 of a valid GML 3.2.1 geometry encoding as defined in Geography Markup Language (GML) simple features profile (with Corrigendum) to be used with the GeoXACML 3.0 Core standard. -The use of this encoding extension to GeoXACML 3.0 Core enables the direct use of GML 3.2.1 encoded geometries into a GeoXACML 3.0 Policy, an Authorization Decision Request or in an Authorization Decision’s Obligation element. It thereby improves the performance of deriving access control decisions, where geometries are involved as existing GML 3.2.1 geometry encodings must not be transformed to Well Known Text (WKT) as supported by GeoXACML 3.0 Core. Furthermore, the use of this encoding extension simplifies the implementation of a Policy Enforcement Point as it must not provide the transformation functions from GML to WKT and vice versa. -This encoding extension has its normative base in Geography Markup Language (GML) simple features profile (with Corrigendum). - + + 16-088r1 + Soil Data Interoperability Experiment + 2016-07-26 + + + + Alistair Ritchie + This engineering report describes the results of the Soil Data Interoperability Experiment +(the IE) conducted under the auspices of the OGC Agriculture Domain Working Group in +2015. Soil data exchange and analysis is compromised by the lack of a widely agreed +international standard for the exchange of data describing soils and the sampling and +analytical activities relating to them. Previous modeling activities in Europe and +Australasia have not yielded models that satisfy many of the data needs of global soil +scientists, data custodians and users. This IE evaluated existing models and proposed a +common core model, including a GML/XML schema, which was tested through the +deployment of OGC web services and demonstration clients. IE time constraints and +limited participant resources precluded extensive modeling activities. However, the +resulting model should form the core of a more comprehensive model to be developed by +a future OGC Soil Data Standards Working Group. + OGC Soil Data Interoperability Experiment - - OGC Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 GML 3.2.1 Encoding Extension - 2013-11-06 - - - - Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 GML 3.2.1 Encoding Extension - 13-101 - 13-101 - Andreas Matheus + + 16-088r1 - - Stan Tillman - OWS-7 Motion Video Change Detection - 10-036r2 - This Engineering Report documents the development effort to build a Web Processing Service (WPS) to perform a change detection algorithm on two motion video streams. It will examine the WPS Motion Video Change Detection architecture from various viewpoints in order to describe its purpose, data models, functional decomposition, and interaction between distinct computational components. - 2010-08-18 - OWS-7 Motion Video Change Detection - 10-036r2 + + OGC Testbed-15: Semantic Web Link Builder and Triple Generator + 2019-12-17 + This OGC Testbed 15 Engineering Report (ER) describes a generalized approach towards performing data fusion from multiple heterogeneous geospatial linked data sources. The specific use case is semantic enrichment of hydrographic features provided by Natural Resources Canada (NRCan). The ER attempts to define and formalize the integration pipeline necessary to perform a fusion process for producing semantically coherent fused entities. + 19-021 + OGC Testbed-15: Semantic Web Link Builder and Triple Generator + + + 19-021 + Esther Kok, Stephane Fellah - - - - - + + The Specification Model - Standard for Modular specifications - OGC® Catalogue Services support the ability to publish and search collections of -descriptive information (metadata records) for geospatial data, services, and related -information. Metadata in catalogues represent resource characteristics that can be queried -and presented for evaluation and further processing by both humans and software. -Catalogue services are required to support the discovery and binding to registered -information resources within an information community. -This part of the Catalogue Services standard describes the common architecture for OGC -Catalogue Services. This document abstractly specifies the interfaces between clients and -catalogue services, through the presentation of abstract models. This common -architecture is Distributed Computing Platform neutral and uses UML notation. Separate -(Part) documents specify the protocol bindings for these Catalogue services, which build -upon this document, for the HTTP (or CSW) and OpenSearch protocol bindings. -An Abstract Conformance Test Suite is not included in this document. Such Suites shall -be developed by protocol bindings and Application Profiles (see 8.5, ISO/IEC TR 10000- -2:1998) that realize the conformance classes listed herein. An application profile -consists of a set of metadata elements, policies, and guidelines defined for a particular -application1. -OGC document number 14-014r3 – HTTP Protocol Binding – Abstract Test Suite is -available to address conformance with the provisions of OGC document number 12- -176r7 – HTTP Protocol Binding. All annexes to this document are informative. - Catalogue Services 3.0 - General Model - 12-168r6 - - 12-168r6 - OGC® Catalogue Services 3.0 - General Model - 2016-06-10 + The Specification Model - Standard for Modular specifications + 08-131r3 - Douglas Nebert, Uwe Voges, Lorenzo Bigagli + + 2009-10-19 + Policy SWG + + + + 08-131r3 + This standard contains requirements for writing standards to be used for any document whose +eventual purpose is the specification of requirements for software, services or data structures. + + + Panagiotis (Peter) A. Vretanos, Clemens Portele + 2024-07-26 + 19-079r2 + OGC API - Features - Part 3: Filtering + 19-079r2 + OGC API - Features - Part 3: Filtering + OGC API Standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks. + +OGC API - Features provides API building blocks to create, modify and query features on the Web. OGC API - Features is comprised of multiple parts. Each part is a separate standard. + +A fundamental operation performed on a collection of features is that of filtering in order to obtain a subset of the data which contains feature instances that satisfy some filtering criteria. Part three of the OGC API - Features Standard defines query parameters (filter, filter-lang, filter-crs) to specify filter criteria in a request to an API and the Queryables resource that declares the properties of data in a collection that can be used in filter expressions. + + + + + - - + + The aim of this OGC Engineering Report is to show how to provide access control for OGC Web Services (OWS). In the first part of this document we will briefly introduce the relevant details of XACML 2.0, OGC GeoXACML 1.0 and some related profiles. + + OWS-6 GeoXACML Engineering Report + 09-036r2 + + + + OWS-6 GeoXACML Engineering Report + 09-036r2 + 2009-07-24 + + Jan Herrmann, Andreas Matheus - - 04-049r1 - WCS Change Request: Support for WSDL & SOAP + + + This document extends the ebRIM application profile of CS-W for the cataloguing of ISO 19115 and ISO 19119 compliant metadata. - The OpenGIS has been a precursor in Web Services matter, nevertheless, the pattern that has been used is not recognized by the industry as a standard XML Web Services. The work done during the the OpenGIS Web Service 2 initiative has provided the OpenGIS with interfaces that use the XML-related technologies supported by the industry, as SOAP for the communication protocol, WSDL for the interface description language, and UDDI for registering and searching services. - -This change proposal present the required change to the WCS specification to interoperate with the industry standards. - + + OGC Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W + Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W + 07-038 - 04-049r1 - Philippe Duschene, Jerome Sonnet - WCS Change Request: Support for WSDL & SOAP - 2005-04-22 - - - - 2022-11-10 - 22-013r3 - + 2007-06-06 + Nicolas Lesage, Marie-Lise Vautier + 07-038 + + + - This Engineering Report (ER) summarizes the demonstrations, findings, and recommendations that emerged from the second phase of the OGC Federated Marine Spatial Data Infrastructure (FMSDI) Pilot. The goal of this initiative was to further advance the interoperability and usage of Marine Protected Area (MPA) data through the implementation of the IHO standard S-122 and several OGC API standards. - -This ER describes a solution architecture consisting of a collection of interoperable components developed to demonstrate technologies that helped to achieve the objectives of this Pilot’s phase. This document describes a server built to serve MPA data through an OGC API – Features endpoint and two servers that combined MPA data with additional datasets and served it through both an OGC API – Features and an OGC API — EDR endpoint. This document also describes the three clients built to consume under different scenarios the data offered by the aforementioned servers. Finally, this ER captures lessons learned and recommendations for IHO and OGC API standards, and recommendations for future work. + + Jérôme JANSOU, Thibault DACLA + 2011-12-19 + OWS-8 AIXM 5.1 Compression Benchmarking + AIXM stands today for the de-facto standard for Aeronautical Information Publication, used by air control service providers from Europe, USA and Australia. With version 5.1, it reaches a level of maturity allowing the support of Digital NOTAMs, as the first official version of these messages was published this year. +In a near future, AIXM will be carried inside WFS requests but also into notification messages along WS event services. This last channel will be the one dedicated to D-NOTAMs. As D-NOTAM is aimed at aircrafts pilots, their transmission to the aircraft will use air/ground data link. Today, datalink communications lack bandwidth and future datalink will still have a limited capacity. + + + 11-097 + OWS-8 AIXM 5.1 Compression Benchmarking + 11-097 + - Towards a Federated Marine SDI: IHO and OGC standards applied to Marine Protected Area Data Engineering Report - Sergio Taleisnik, Terry Idol, Ph.D. - 22-013r3 - Towards a Federated Marine SDI: IHO and OGC standards applied to Marine Protected Area Data Engineering Report - - OpenGIS - OpenGIS Location Services (OpenLS): Navigation Service [Part 6] - Location Services (OpenLS): Navigation Service [Part 6] - 03-007r1 - - Tom Bychowski - + + Panagiotis (Peter) A. Vretanos + + 15-010r4 + Testbed-11 WFS-T Information Exchange Architecture + 15-010r4 + + + OGC® Testbed-11 WFS-T Information Exchange Architecture - 2003-06-12 - 03-007r1 - - - - - - Mike Botts - Sensor Model Language (SensorML) - 07-000 - - - - - OpenGIS Sensor Model Language (SensorML) - 07-000 - 2007-07-24 - The OpenGIS® Sensor Model Language Encoding Standard (SensorML) specifies models and XML encoding that provide a framework within which the geometric, dynamic, and observational characteristics of sensors and sensor systems can be defined. There are many different sensor types, from simple visual thermometers to complex electron microscopes and earth observing satellites. These can all be supported through the definition of atomic process models and process chains. Within SensorML, all processes and components are encoded as application schema of the Feature model in the Geographic Markup Language (GML) Version 3.1.1. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. For additional information on SensorML, see http://www.botts-inc.net/vast.html -<!-- http://vast.uah.edu/SensorML.--> + This document presents an assessment of the conformance level, with respect to the WFS standard (OGC 09-025r2), of the web feature servers used in the OGC Testbed-11. Each server is accessed to determine if it conforms to the minimum requirements of the WFS standard. Each server is further accessed to determine whether the server offers additional, upcoming and complimentary capabilities just as support for the WFS REST API and GeoJSON. +This document offers recommendations to aid implementers of the WFS standard (OGC 09-025r2). +This document presents options available to WFS implementers for achieving interoperability between WFS clients and server at the schemas level. +This document includes a survey of available WFS clients and an assessment of their capabilities. +This document reviews tools and standards, such as the GeoSynchronization Service (OGC 10-069r3), that are complimentary components that may be used with a WFS to address requirements such as verification and notification, data and access security, exception handling and system hardening. +Finally, this document includes a FAQ composed of questions raised during the OGC Testbed-11. + + 2016-01-28 - + + + + + + + OWS-7 - Authoritative Data Source Directory Engineering Report + 10-086r1 + + 10-086r1 + 2010-08-18 + Andrew Turner + + OWS-7 - Authoritative Data Source Directory Engineering Report - - 2019-12-20 - Sam Meek - The Machine Learning (ML) Engineering Report (ER) documents the results of the ML thread in OGC Testbed-15. This thread explores the ability of ML to interact with and use OGC web standards in the context of natural resources applications. The thread includes five scenarios utilizing seven ML models in a solution architecture that includes implementations of the OGC Web Processing Service (WPS), Web Feature Service (WFS) and Catalogue Service for the Web (CSW) standards. This ER includes thorough investigation and documentation of the experiences of the thread participants. - 19-027r2 - OGC Testbed-15: Machine Learning Engineering Report - - 19-027r2 - OGC Testbed-15: Machine Learning Engineering Report + This document presents the Authoritative Data Source Directory (ADSD) engineering suggestions and results of the OGC OWS-7 ADSD thread. This group focused on creating a workflow for geospatially referencing, finding, and federating data sources with associated authority and relevance. - - 2014-02-26 - - Peter Baumann, Jinsongdi Yu - Web Coverage Service Interface Standard - Scaling Extension - 12-039 - - 12-039 - - This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request which allow scaling of a coverage during its server-side processing in a GetCoverage request. - - OGC® Web Coverage Service Interface Standard - Scaling Extension - + + 08-000 + + Canadian Geospatial Data Infrastructure Summary Report + 08-000 + 2008-04-29 - - - 16-062 - This engineering report has been produced by the OGC® Testbed-12 initiative. -The engineering report evaluates interoperability between a variety of -catalogues. The report presents a comparison of the catalogues, with the same -datasets uploaded. The catalogues discussed in the report include services -conforming to Catalogue Service for Web (CSW) version 2.0.2 and 3.0, including -services based on the ebRIM profile of CSW 2.0.2 and an extension of CSW 3.0 -with OpenSearch and SOAP. The engineering report presents results from tests -using a multi-catalogue client to interact with each service. The engineering -report also provides a comparison of CSW and services based on the Data -Catalogue (DCAT) specification covering functionality, expressiveness and -usability of CSW and DCAT. The comparison is supported by a discussion on the -implementation of a SPARQL / GeoSPARQL service. - 16-062 - Testbed-12 Catalogue and SPARQL Engineering Report - - Gobe Hobona, Roger Brackin - 2017-05-15 - Testbed-12 Catalogue and SPARQL Engineering Report + Raj SIngh + This report summarizes the work performed under the Canadian Geospatial Data Infrastructure Pilot. The purpose of this pilot was to test the utility of certain OGC standards, in particular the Geography Markup Language (GML) and Web Feature Service (WFS), in the implementation of a spatial data infrastructure. OGC documents 08-001 and 08-002 are more technical companions to this document. + + OGC® Canadian Geospatial Data Infrastructure Summary Report + + + + + 10-073r1 + + OWS-7 CCSI-SWE Best Practices Engineering Report + This document seeks to define the Best Practices for integrating Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) compliant and potentially other CBRN-based sensors into an OGC Sensor Web Enablement (SWE)-based environment. The document focuses on the practical application of SWE services and encodings for describing and interacting with CCSI sensors and data and draws heavily from and expands upon work performed in the OGC Web Services Phase 6 (OWS-6) testbed to define methodologies for integrating CCSI sensors into a SWE-based environment both now, by building upon the OWS-6 work, and in the future, by defining CCSI profiles of the SWE specifications. + OWS-7 CCSI-SWE Best Practices Engineering Report + 10-073r1 + + 2010-06-30 + Scott Fairgrieve - + - - 2018-03-02 - + + + + WPS 2.0 Interface Standard + 14-065 + + - 17-049 - 17-049 - Ensuring Quality of User Experience with OGC Web Mapping Services - Discussion Paper - - C. Mitchell, M. Gordon, T. Kralidis - Ensuring Quality of User Experience with OGC Web Mapping Services - Discussion Paper + + + Matthias Mueller + 14-065 + OGC® WPS 2.0 Interface Standard + 2015-03-05 + + - This paper is intended to identify usability issues associated with use of OGC web -mapping services that affect the quality of experience a user may have when accessing -and using OGC web services and discuss potential solutions and guidance to address -these issues. Additionally, guidance on evaluating and self-assessing the Quality of -Experience of Spatial Data Services will also be discussed and addressed with a proposal -for common assessment criteria and common practices for improving the user experience -when viewing, layering or querying OGC web mapping services. + Ryosuke Shibasaki + + Applications using moving feature data, typically on vehicles and pedestrians, have +recently been rapidly increasing. Innovative applications are expected to require the +overlay and integration of moving feature data from different sources to create more +social and business values. Efforts in this direction should be encouraged by ensuring +smoother data exchange because handling and integrating moving feature data will +broaden the market for geo-spatial information. This discussion paper provides an +overview of some actual and potential geo-spatial applications using moving feature data +and the existing international standards or specifications on moving feature data handling. +It also summarizes the requirements set on the standards for moving feature data, and +finally proposes the development of a new OGC standard for moving features. + 12-117r1 + 2012-12-06 + OGC Standard for Moving Features; Requirements + + OGC Standard for Moving Features; Requirements + 12-117r1 + - + + + 2007-05-17 + + GML PIDF-LO Geometry Shape Application Schema for use in the IETF + 06-142r1 - 09-072 - OWS-6 CITE TEAM Engine Engineering Report + + Carl Reed, PhD. and Martin Thomson + + GML PIDF-LO Geometry Shape Application Schema for use in the IETF - 09-072 - - This document summarizes the work done on the TEAM compliance test engine and DGIWG Profile compliance test by Northrop Grumman for the CITE thread of OWS-6 in 2008-2009. - - - OWS-6 CITE TEAM Engine Engineering Report - - James Ressler - 2009-08-05 + 06-142r1 + This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for XML encoding of various geometric shapes required in the Presence Information Description Format (IETF RFC 3863) Location Object extension - A Presence-based GEOPRIV Location Object Format (RFC 4119). - + + 21-064 - 20-035 - + OGC Disaster Pilot 2021 Engineering Report + Andreas Matheus - Earth Observation Application Packages with Jupyter Notebooks - 20-035 + + OGC Disaster Pilot 2021 Engineering Report + 21-064 + + This OGC Disaster Pilot ’21 (DP21) Engineering Report summarizes work done in the Pilot to increase disaster awareness among a range of disaster management stakeholders. Pilot participants implemented components of a data flow ecosystem to leverage analysis-ready earth observations and other datasets (ARD) and produce decision ready indicators (DRI) according to collaboratively developed workflow recipes. DP21 focused on the hazards of flooding, landslides, and pandemic, as well as the interactions and complications between them, in three regions including the Piura and Rimac river basins in Peru; the Red River Basin in Manitoba, Canada; and the greater New Orleans area in Louisiana, United States. The Pilot also prototyped providing information to field practitioners in secure geopackage formats, as well as leveraging linked data and structured web page information to optimize public web searches for disaster information. + 2023-01-10 - - OGC Testbed-16: Earth Observation Application Packages with Jupyter Notebooks - 2021-01-13 - This OGC Testbed-16 Engineering Report (ER) describes all results and experiences from the “Earth Observation Application Packages with Jupyter Notebook” thread of OGC Testbed-16. The aim of this thread was to extend the Earth Observation Applications architecture developed in OGC Testbeds 13, 14, and 15 with support for shared and remotely executed Jupyter Notebooks. The Notebooks make use of the Data Access and Processing API (DAPA) developed in the Testbed-16 Data Access and Processing API (DAPA) for Geospatial Data task and tested in joint Technology Integration Experiments. - Christophe Noël - - - OGC InfraGML 1.0: Part 4 - LandInfra Roads - Encoding Standard - 16-104r2 - 16-104r2 - InfraGML 1.0: Part 4 - LandInfra Roads - Encoding Standard - - This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. -InfraGML is published as a multi-part standard. This Part 4 addresses the Road and RoadCrossSection Requirements Class from LandInfra. + - Paul Scarponcini + Open Modelling Interface Interface Standard + 11-014r3 - - - 2017-08-16 - - - + 11-014r3 + <p>The purpose of the Open Modelling Interface (OpenMI) is to enable the runtime exchange of data between process simulation models and also between models and other modelling tools such as databases and analytical and visualization applications. Its creation has been driven by the need to understand how processes interact and to predict the likely outcomes of those interactions under given conditions. A key design aim has been to bring about interoperability between independently developed modelling components, where those components may originate from any discipline or supplier. The ultimate aim is to transform integrated modelling into an operational tool accessible to all and so open up the potential opportunities created by integrated modelling for innovation and wealth creation. +</p> +<p> +This document defines the requirements that a component must meet to achieve OpenMI compliance. These comprise: 1) a very thin core set of requirements covering the information and functions needed to establish a link and make an exchange between two components and 2) a set of optional extensions for handling more complex situations. The document does not describe how to implement the standard. This information together with a range of software tools for creating and running OpenMI-­&#8208;compliant components are provided by the OpenMI Association and third-­&#8208;party software vendors – visit www.openmi.org for further documentation.</p> +<p> +<a href=https://portal.ogc.org/files/?artifact_id=59022>pdf</a> <br> +<a href=https://portal.ogc.org/files/?artifact_id=59022&format=docx>docx</a> +</p> - 18-024r1 - Release Notes for OGC GeoPackage Encoding Standard v1.2.1 + OGC Open Modelling Interface Interface Standard + 2014-05-26 - This document provides the set of revision notes for the existing GeoPackage version 1.2.1 (OGC 12-128r15) and does not modify that standard. - -This document was approved by the OGC membership on approval date. As a result of the OGC Standards Working Group (SWG) process, there were a number of edits and enhancements made to this standard. This document provides the details of those edits, deficiency corrections, and enhancements. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility. - - 18-024r1 - - Jeff Yutzler - 2018-12-18 - Release Notes for OGC GeoPackage Encoding Standard v1.2.1 + + Stanislav Vanecek, Roger Moore - - - - - - - GML 3.1.1 CRS support profile - Arliss Whiteside + - This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for supporting other profiles for encoding definitions of Coordinate Reference Systems (CRSs) and Coordinate Operations. This profile can be used without a GML Application Schema, and such use is assumed in this document. - 05-094r1 - GML 3.1.1 CRS support profile - 2006-07-18 - 05-094r1 - - - 2015-01-30 - Unified Geo-data Reference Model for Law Enforcement and Public Safety - 14-106 - - - Carl Reed, Jennifer Harne + Jeff Yutzler + 21-004 + Release Notes for OGC GeoPackage 1.3.1 + 2023-03-24 + + + + Release Notes for OGC GeoPackage 1.3.1 + This document provides the set of revision notes for Geopackage 1.3.1 and does not modify that Standard. + +This document provides the details of edits, deficiency corrections, and enhancements of the above-referenced Standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility. - This document provides an overview of the Unified Geo-data Reference Model for Law Enforcement and Public Safety (Unified Model). The Unified Model was originally developed by the GIS Center for Security (GIS CS), Abu Dhabi Police. The GIS CS was initiated based on a UAE Ministry of Interior issued decree to establish GIS CS with the core mission: “To geo-enable police services and applications using International standards and best practices.” In 2010, the GIS SC initiated a program to develop a Standardized GIS Environment (SGA). Part of this effort was to define and implement a standard data model for sharing Law Enforcement and Public Safety data. - - - 14-106 - Unified Geo-data Reference Model for Law Enforcement and Public Safety + 21-004 - + + 2012-01-25 + OWS-8 Aviation Thread - Authoritative AIXM Data Source Engineering Report + 11-086r1 + + This engineering report describes how to provide access control for WFS-T 2.0 instances +in the OWS-8 Authoritative AIXM Data Source scenario. - - - OWS-6 Secure Sensor Web Engineering Report - The main purpose of this Engineering Report is to introduce standards-based security solutions for making the existing OGC Sensor Web Services, as described in the OWS-6 SWE baseline, ready towards the handling of sensors in the intelligence domain. - 08-176r1 - OWS-6 Secure Sensor Web Engineering Report - - 2009-07-29 - Andreas Matheus - 08-176r1 + Jan Herrmann, Andreas Matheus + 11-086r1 + + OWS-8 Aviation Thread - Authoritative AIXM Data Source Engineering Report + - - Jeff de La Beaujardiere - 2002-08-24 - - 02-017r1 - WMS Part 2: XML for Requests using HTTP Post - - - WMS Part 2: XML for Requests using HTTP Post - This part of the Web Map Service (WMS) specification applies to those clients and servers which allow operation request encodings that are more complex than those permitted by the basic keyword/value encoding defined in WMS Part 1 [17]. Part 2 only describes the encoding of the request messages using Extensible Markup Language (XML); all other aspects of the Web Map Service are fully defined in Part 1. + + Geopackage Release Notes + 15-123r1 + 2016-02-16 + 15-123r1 + This document provides the set of revision notes for the existing OGC Implementation Standard GeoPackage version 1.1 (OGC 12-128r12) and does not modify that standard. +This document was approved by the OGC membership on <insert approval date here>. As a result of the OGC Standards Working Group (SWG) process, there were a number of edits and enhancements made to this standard. This document provides the details of those edits, deficiency corrections, and enhancements. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility. + + + Jeff Yutzler + + Geopackage Release Notes + + - - 02-017r1 - - OGC GeoPose 1.0 Data Exchange Standard - 21-056r11 - 21-056r11 - 2023-09-08 - Carl Stephen Smyth - + + + + OGC Testbed-16: Data Access and Processing Engineering Report + 20-016 - OGC GeoPose 1.0 Data Exchange Standard - + Data Access and Processing Engineering Report + 20-016 + + - - GeoPose 1.0 is an OGC Implementation Standard for exchanging the location and orientation of real or virtual geometric objects (“Poses”) within reference frames anchored to the earth’s surface (“Geo”) or within other astronomical coordinate systems. + 2021-01-13 + Panagiotis (Peter) A. Vretanos + This OGC Testbed-16 Engineering Report (ER) describes the work performed in the Data Access and Processing API (DAPA) thread. -The standard specifies two Basic forms with no configuration options for common use cases, an Advanced form with more flexibility for more complex applications, and five composite GeoPose structures that support time series plus chain and graph structures. +The primary goal of the DAPA thread is to develop methods and apparatus that simplify access to, processing of, and exchange of environmental and Earth Observation (EO) data from an end-user perspective. This ER presents: -These eight Standardization Targets are independent. There are no dependencies between Targets and each may be implemented as needed to support a specific use case. +The use cases participants proposed to guide the development of the client and server components deployed during the testbed. -The Standardization Targets share an implementation-neutral Logical Model which establishes the structure and relationships between GeoPose components and also between GeoPose data objects themselves in composite structures. Not all of the classes and properties of the Logical Model are expressed in individual Standardization Targets nor in the specific concrete data objects defined by this standard. Those elements that are expressed are denoted as implementation-neutral Structural Data Units (SDUs). SDUs are aliases for elements of the Logical Model, isolated to facilitate specification of their use in encoded GeoPose data objects for a specific Standardization Target. +An abstract description of a resource model that binds a specific function to specific data and also provides a means of expressing valid combinations of data and processes. -For each Standardization Target, each implementation technology and corresponding encoding format defines the encoding or serialization specified in a manner appropriate to that technology. +A description of each DAPA endpoint developed and deployed during the testbed. -GeoPose 1.0 specifies a single encoding in JSON format (IETF RFC 8259). Each Standardization Target has a JSON Schema (Internet-Draft draft-handrews-json-schema-02) encoding specification. The key standardization requirements specify that concrete JSON-encoded GeoPose data objects must conform to the corresponding JSON Schema definition. The individual elements identified in the encoding specification are composed of SDUs, tying the specifications back to the Logical Model. +A description of the client components that interact with the deployed DAPA endpoints. -The GeoPose 1.0 Standard makes no assumptions about the interpretation of external specifications, for example, of reference frames. Nor does it assume or constrain services or interfaces providing conversion between GeoPoses of difference types or relying on different external reference frame definitions. - +End-user (i.e. data scientist) feedback concerning the ease-of-use of the - - - George Percivall - - OGC® Open Geospatial APIs - White Paper - Open Geospatial APIs - White Paper - 16-019r4 - 16-019r4 - OGC defines interfaces that enable interoperability of geospatial applications. API’s are a popular method to implement interfaces for accessing spatial data. This White Paper provides a discussion of Application Programming Interfaces (APIs) to support discussion of possible actions in the Open Geospatial Consortium (OGC). + - + - 2017-02-23 - - - + OGC API – Maps Sprint 2020: Summary Engineering Report + 20-090 + 20-090 - Bastian Schäffer - 09-053r5 - OWS-6 Geoprocessing Workflow Architecture Engineering Report - 09-053r5 - OWS-6 Geoprocessing Workflow Architecture Engineering Report - - 2009-10-09 - This document covers Geoprocessing Workflow best practices and methods in a SOA environment. A RESTful approach was also conducted in this testbed, but no specific implementation details were available to be included in this ER; also, the RESTful workflow approaches and technology used in this testbed was essentially same as that used in OWS-5. - - - + + OGC API – Maps Sprint 2020: Summary Engineering Report + Gobe Hobona + This OGC Engineering Report (ER) documents the results and recommendations from a code sprint that was held from 28 to 29 July 2020 to advance the development of the draft OGC API – Maps Standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application, or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The OGC API - Maps Sprint was an online virtual event. The sprint was sponsored by Ordnance Survey. + 2021-01-18 - + + 06-042 + Web Map Service (WMS) Implementation Specification + 06-042 + + + 2006-03-15 + OpenGIS Web Map Service (WMS) Implementation Specification + + The OpenGIS® Web Map Service Interface Standard (WMS) provides a simple HTTP interface for requesting geo-registered map images from one or more distributed geospatial databases. A WMS request defines the geographic layer(s) and area of interest to be processed. The response to the request is one or more geo-registered map images (returned as JPEG, PNG, etc) that can be displayed in a browser application. The interface also supports the ability to specify whether the returned images should be transparent so that layers from multiple servers can be combined or not. <p>NOTE: WMS 1.3 and ISO 19128 are the same documents. - 16-010r5 - Volume 7: OGC CDB Data Model Guidance (Best Practice) - - - This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store. - - - - - 16-010r5 - Volume 7: OGC CDB Data Model Guidance (Best Practice) - Carl Reed - 2021-02-26 - - - - - 0000-00-00 + Jeff de La Beaujardiere - - Jinsongdi Yu, Peter Baumann - OWS-9 WCS Conformance Testing Engineering Report - 12-162r1 - This Engineering Report was prepared as a deliverable for the OGC Web Services, Phase -9 (OWS-9) initiative of the OGC Interoperability Program. The document presents the -work completed with respect to the Conformance & Interoperability Testing & -Evaluation sub-thread within OWS-9. -This Engineering Report describes and evaluates the specification of WCS 2.0 core -corrigenda and extensions’ Abstract Test Suite (ATS) and the implementation of ETS for -use within an OGC SOA processing chain. - OWS-9 WCS Conformance Testing Engineering Report - 12-162r1 - - - - 16-063 - Stefano Cavazzi, Roger Brackin - Testbed-12 Arctic Spatial Data Infrastructure Engineering Report - - 2017-03-08 - Testbed-12 Arctic Spatial Data Infrastructure Engineering Report - 16-063 - This engineering report captures use cases representative of the vision of the Arctic Spatial Data Infrastructure (ArcticSDI). The ArcticSDI is a cooperative initiative established between the eight National Mapping Agencies of Canada, Finland, Iceland, Norway, Russia, Sweden, USA and Denmark, with the aim of providing governments, policy makers, scientists, private enterprises and citizens in the Arctic with access to geographically related Arctic data, digital maps, and tools to facilitate monitoring and decision-making. The initiative will achieve this aim by providing a framework of spatial information resources, organizational structures, technologies of creation, processing and exchange of spatial data, that provides broad access and efficient use of spatial data for the Arctic. The engineering report provides a review of the policy drivers supporting the establishment of spatial data infrastructure (SDI) in each Arctic nation in order to improve understanding of the use cases, user groups and the impact an ArcticSDI may have on their day-to-day business. The engineering report presents lessons learnt along each of the components of SDI, for example, users, data, technology, standards, policy and others. A discussion is presented on how the technologies and standards already in use by the national mapping agencies relate to the technologies and standards implemented by the testbed, as well as how emerging geospatial standards could benefit the ArcticSDI. - + + The GO-1 Application Objects specification defines a set of core packages that support a small set of Geometries, a basic set of renderable Graphics that correspond to those Geometries, 2D device abstractions (displays, mouse, keyboard, etc.), and supporting classes. Implementation of these APIs will support the needs of many users of geospatial and graphic information. These APIs support the rendering of geospatial datasets, provide fine-grained symbolization of geometries, and support dynamic, event and user driven animation of geo-registered graphics. + Eric Bertel + 2004-06-25 + 03-064r5 + GO-1 Application Objects + GO-1 Application Objects + + 03-064r5 + - - - - - OWS-7 Feature and Statistical Analysis Engineering Report - 10-074 - 2010-08-18 - - - 10-074 - - OWS-7 Feature and Statistical Analysis Engineering Report - - Theodor Foerster, Bastian Schäffer - This Engineering Report (ER) is a deliverable for the OGC Web Service 7 testbed. The focus of this ER is using the OGC Web Processing Service (WPS) interface standard for Feature and Statistical Analysis (FSA). Specifically, the ER documents how to enhance interoperability of FSA processes that are hosted as WPS processes on the Web. This ER is coordinated with the Feature and Decision Fusion (FDF) WPS Profiling ER. - - - - - - - - - - - - Documents of type Name Type Specification - Documents of type Name Type Specification - Documents of type Name Type Specification + - + + + OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report + 12-156 - 08-053r2 - WCS Processing Extension (WCPS) Abstract Test Suite - 08-053r2 - - - - 2009-03-25 - WCS Processing Extension (WCPS) Abstract Test Suite - - Peter Baumann - + + 2013-02-19 + OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report + + 12-156 + + The Reference Architecture Profiler (RAP) Advisor™ is a web based application that +recommends OGC Standards and OGC Reference Model (ORM) Sections that are +relevant to a system development; such that a community of interest could derive and +build a profile of suitable OGC standards to meet their specific needs. This Engineering +Report contains the requirements, conceptual design, development methodology, and +implementation of the RAP Advisor. +Initial development of the RAP Advisor™ was concurrent with the OGC Web Services +Testbed, Phase 9 (OWS-9) with NGA sponsorship. During OWS-9 timeframe, key +concepts of the RAP Advisor were confirmed through prototyping. Future development +is required to complete the functions and content of the Advisor. + George Percivall - - 2015-08-04 + + 2012-02-09 + + OWS-8 Review of the WXXS exchange schemas + OWS-8 Review of the WXXS exchange schemas + 11-091 + + Richard Martell + + 11-091 + + This aim of this review is to assess the the WXXS 1.1.1 exchange schemas for +compliance with ISO 19136:2007 (GML 3.2.1). This international standard stipulates +rules and recommendations regarding the construction of GML application schemas; +these constraints are documented in the following clauses: +(a) Clause 7.1: GML model and syntax +(b) Clause 21: Rules for GML application schemas +(c) Annex A.1: Abstract test suite for GML application schemas - - GeoPackage Encoding Standard - 12-128r12 - - - Jeff Yutzler - 12-128r12 - - OGC® GeoPackage Encoding Standard - This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector -geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access -and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that -guarantees data model and data set integrity and identical access and update results in response to identical requests from different -client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly -useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. - + - 2020-07-29 + OWS-9 CCI Semantic Mediation Engineering Report + 12-103r3 + 2013-02-05 - 3D-IoT Platform for Smart Cities Engineering Report - 19-073r1 - OGC 3D-IoT Platform for Smart Cities Engineering Report - Volker Coors + - + The OWS-9 Cross Community Interoperability (CCI) thread built on progress made in the recent OWS-8 initiative by improving interoperability between communities sharing geospatial data through advances in semantic mediation approaches for data discovery, access and use of heterogeneous data models and heterogeneous metadata models. This OGC engineering report aims to present findings from CCI thread activities towards advancement of semantic mediation involving heterogeneous data models, gazetteers and aviation data available through web services conformant to OGC standards. +This Engineering Report was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Cross Community Interoperability thread within OWS-9. + - 19-073r1 - - Recent years have seen a significant increase in the use of three-dimensional (3D) data in the Internet of Things (IoT). The goal of the 3D IoT Platform for Smart Cities Pilot was to advance the use of open standards for integrating environmental, building, and IoT data in Smart Cities. Under this initiative a proof of concept (PoC) has been conducted to better understand the capabilities to be supported by a 3D IoT Smart City Platform under the following standards: CityGML, IndoorGML, SensorThings API, 3D Portrayal Service, and 3D Tiles. + + OWS-9 CCI Semantic Mediation Engineering Report + Gobe Hobona, Roger Brackin + 12-103r3 - - 2024-04-29 - 21-075r2 - Disasters are geographic events and therefore, geospatial information, tools and applications have the potential to support the management of, and response to, disaster scenarios. - -However, the use of geospatial data varies significantly across disaster and emergency communities. This can often make it difficult to share information between different organizations, and sometimes even within the same organization, involved in disaster response. This could mean that not everyone involved will have the same situational awareness information. - -There are many reasons for why geospatial information is fully used and exploited, included a lack of awareness of what geospatial options are available, lack of geospatial technology and skills, lack of funding, etc. The Disaster Pilot User Guide aims to address some of these issues by providing a non-technical showcase of the workflows and tools developed by the Pilot participants demonstrating what opportunities there are for disaster and emergency management communities to use geospatial solutions in practice. - -For over 20 years, the Open Geospatial Consortium (OGC) has been working on the challenges of information sharing for emergency and disaster planning, management, and response. In Disaster Pilot 23 (DP23) the aims were to: - -Develop flexible, scalable, timely and resilient information data workflows to support critical disaster management decisions, enabling stakeholder collaboration, and -Provide applications and visualization tools to promote the wider understanding of how geospatial data can support emergency and disaster communities. -As part of DP23, a trilogy of Guides were developed to improve knowledge and understanding of how geospatial data and tools and could support disaster and emergency communities. Alongside the User Guide is a Provider Guide giving all the detail technical details behind the work, and a companion Operational Capacity Guide describing the steps needed to develop geospatial readiness. - -The User Guide contains a summary of the work undertaken in DP23, and Disaster Pilot 21 (DP21), where participants have worked on disaster scenarios relating to: - -Droughts -Wildland Fires -Flooding -Landslides -Health & Earth Observation Data for Pandemic Response -Case Studies have focused on the hazards of drought in Manitoba, Canada; wildland fires in western United States; flooding in the Red River basin, Canada; landslides and flooding in Peru; and Pandemic response in Louisiana, United States. The participants have developed various data flows, alongside tools to support the collection, discovery, or visualization of data to support disaster management and response. - -Annex A describes the tools and applications developed within the Pilots alongside the benefits these can offers. The Guide finishes with details of future possibilities, and where the Disaster Pilot initiative could focus next. Annexes B to E give descriptions of the data flows developed, including the aspects of disaster management or response the data flow relates to; together with the benefits it offers and the type of decisions it can support. - -This document is for first responders, emergency managers, decision-makers, and anyone interested in encouraging disaster and emergency communities to realize the value of geospatial data to save lives and limit damage. - OGC Disaster Pilot: User Readiness Guide - - - OGC Disaster Pilot: User Readiness Guide - 21-075r2 + - - Andrew Lavender, Samantha Lavender + This report summarizes the results of OGC’s Climatology-Hydrology Information Sharing Pilot, Phase 1 (CHISP-1). The objective of this initiative was to develop an inter-disciplinary, inter-agency and international virtual observatory system for water resources information from observations in the U.S. and Canada, building on current networks and capabilities. +The CHISP-1 Initiative was designed to support these Use Case functions: +• Hydrologic modeling for historical and current stream flow and groundwater conditions +• Modeling and assessment of nutrient load into the Great Lakes + + + + Lew Leinenweber + 2014-02-24 + 13-046r2 + CHISP-1 Summary Engineering Report + 13-046r2 + + OGC CHISP-1 Summary Engineering Report - - - Critical Infrastructure Collaborative Environment Architecture: Information Viewpoint + + + 05-015 + Barry Schlesinger - 2003-06-27 + Special XML schemas have been created for individual data sets, based on ISO 19115 and a general schema for the RSE. However, a generalized metadata XML schema should be available where possible; it should not be necessary to create special schemas for each data set. ISO 19139 can serve as such a general XML implementation specification for 19115. This implementation needs to be tested in practice. In addition, the new ISO standards are incorporating much, if not all, of the metadata not in 19115 that the RSE contain. XML schemas for these metadata need to be developed that are based upon the abstract model in the ISO standards. All of these implementations need to be tested in practice. This Report describes such tests and the results. It also describes to what extent metadata on which the test metadata are based are supported by 19139, to what extent they are supported by metadata specified in the new ISO standards or the RSE, and to what extent new metadata elements are needed. + - 03-062r1 - Critical Infrastructure Collaborative Environment Architecture: Information Viewpoint - 03-062r1 - *RETIRED* specifies the information viewpoint for the Critical Infrastructure Collaborative Environment (CICE). - - - Richard Martell - - - - Thomas H.G. Lankester - - This OGC document specifies a constrained, consistent interpretation of the WMS specification that is applicable to government, academic and commercial providers of EO products. + Imagery Metadata + 05-015 + Imagery Metadata + 2005-01-27 - - Web Map Services - Application Profile for EO Products - - 07-063r1 - Web Map Services - Application Profile for EO Products - 07-063r1 - - 2009-11-05 - + - - - - - - - + + Summary of the OGC Web Services, Phase 5 (OWS-5) Interoperability Testbed + + 08-073r2 + + Jessica Cook, Raj Singh + + Summary of the OGC Web Services, Phase 5 (OWS-5) Interoperability Testbed + 08-073r2 + 2008-09-12 + The OGC Web Services, Phase 5 (OWS-5) Testbed was an initiative of the OGC Interoperability Program (IP). The primary focus of an IP activity is to collaboratively extend and demonstrate OGC‘s baseline for geospatial interoperability. - Documents of type User Guide - Documents of type User Guide - Documents of type User Guide + + - - OWS-6 GML Profile Validation Tool ER - + + 17-094r1 + Portrayal Concept Development Study - - 2009-08-14 - OWS-6 GML Profile Validation Tool ER - 09-038r1 + + 17-094r1 + Jeff Yutzler, Rob Cass + - - Clemens Portele - This document outlines an approach for validating data accessed from a Web Feature Service. Two types of validation are supported: -• XML Schema validation against the GML application schema -• Validation of additional constraints encoded in Schematron -This report describes the validation tool, the types of constraints that have been tested and documents the results. - - 09-038r1 + OGC Portrayal Concept Development Study + + 2018-10-09 + The main goal of this CDS is to advance the standards and guidance that will allow production of high-quality digital maps over the web from existing vector data. - - 2007-08-10 - - 07-014r3 - Sensor Planning Service Implementation Specification - The OpenGIS® Sensor Planning Service Interface Standard (SPS) defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor planning request; to submit such a request; to inquire about the status of such a request; to update or cancel such a request; and to request information about other OGC Web services that provide access to the data collected by the requested task. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. - Ingo Simonis + + + + 05-029r4 + GML Point Profile - OpenGIS Sensor Planning Service Implementation Specification + GML Point Profile + + + 05-029r4 + Ron Lake, Carl Reed, George Percivall + + This document defines a profile of the Geography Markup Language (GML) for a point geometry. Attention is drawn to the fact that this is a profile of GML version 3.1.1. + 2005-08-29 + + + OGC® Web Coverage Service Interface Standard - Interpolation Extension + Peter Baumann, Jinsongdi Yu + Web Coverage Service Interface Standard - Interpolation Extension + 12-049 + + 12-049 + + - - 07-014r3 + + 2014-02-26 - + This OGC standard specifies parameters to the OGC Web Coverage Service (WCS) GetCov-erage request which give control over interpolation of a coverage during its server-side pro-cessing. This allows the client (user) to control and specify the interpolation mechanism to be applied to a coverage during server processing. +This WCS Interpolation extension relies on WCS Core [OGC 09-110r4] and the GML Appli-cation Schema for Coverages [OGC 09-146r2]. + - - Paul Daisey - 2014-02-10 - OGC® GeoPackage Encoding Standard - - This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. -<br /><br /> -For the online version of the standard and the developer resources, visit <a href=http://www.geopackage.org/>http://www.geopackage.org/</a> - GeoPackage Encoding Standard - 12-128r10 - + + + + This document is a corrigendum for OGC Document 05-095r1, titled GML 3.1.1 common CRSs profile. This corrigendum is based on change request OGC 06-041. + GML 3.1.1 common CRSs profile Corrigendum + 06-113 + GML 3.1.1 common CRSs profile Corrigendum + + Arliss Whiteside + 2006-07-19 + 06-113 + + + + + OWS-6 GML Profile Validation Tool ER + 09-038r1 + + This document outlines an approach for validating data accessed from a Web Feature Service. Two types of validation are supported: +• XML Schema validation against the GML application schema +• Validation of additional constraints encoded in Schematron +This report describes the validation tool, the types of constraints that have been tested and documents the results. + + + Clemens Portele + 2009-08-14 - + + - 12-128r10 + OWS-6 GML Profile Validation Tool ER + 09-038r1 - - Mike Botts - - 02-026r1 - - The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances. - - + + + + The Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 defines a geospatial extension to the OASIS eXtensible Access Control Markup Language (XACML) Version 3.0 Standard. GeoXACML 3.0 supports the interoperable definition of access rights including geographic conditions based on the XACML 3.0 language, processing model and policy schema. GeoXACML 3.0 provides improvements based on enhancements to the XACML Standard, primarily the support of access conditions spanning different XACML categories. This enhancement empowers GeoXACML 3.0 to be a powerful decision engine with support for spatiotemporal access conditions. + +As a result of the XACML 3.0 deployment model and corresponding implementation flexibility, GeoXACML 3.0 can be operated as a traditional Policy Decision Point or as a cloud-native API gateway. + +The OGC GeoXACML 3.0 Standard defines different conformance classes that supports flexible implementation conformance. Implementation of the Core conformance class supports the ISO 19125 geometry model including topological test (spatial relations) functions which enables the indexing of access conditions-based geometry. The Spatial Analysis conformance class extends the topological test functions for defining access conditions including the processing of geometries. To support condition evaluation for geometries encoded in different Coordinate Reference System (CRS), the CRS Transformation conformance class enables a compliant implementation to undertake dynamic CRS transformation during decision-making unless prohibited per request. Finally, the API conformance class enables operating a GeoXACML 3.0 compliant implementation as an OGC API conformant service (Policy Decision Point). + + OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 + 22-049r1 + 22-049r1 + Andreas Matheus + - SensorML - 02-026r1 - 2002-04-22 - SensorML + 2023-09-21 + OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 - - - - - - - - - - - - - - - - - - - - - - - - - - Documents of type OGC Implementation Specification Corrigendum - Documents of type OGC Implementation Specification Corrigendum + + 2003-10-16 + + OpenGIS Web Coverage Service (WCS) Implementation Specification + + Extends the Web Map Server (WMS) interface to allow access to geospatial coverages that represent values or properties of geographic locations, rather than WMS generated maps (pictures). - - Documents of type OGC Implementation Specification Corrigendum + 03-065r6 + Web Coverage Service (WCS) Implementation Specification + + + + 03-065r6 + John Evans - + + Point cloud data are unstructured three-dimensional sample points to express the basic shape of objects and spaces. However, it is challenging to automatically generate continuous surfaces and infer semantic structures, such as cars, trees, buildings and roads, from a dataset of point clouds generated by a sensor. The understanding of the semantic structures is essential for recording geospatial information. Despite the good performance of deep learning-based approaches in understanding point clouds, their target coverage is still limited by the lack of training datasets that include semantic labels. This discussion paper addresses data formats to share a Labeled Point Cloud (LPC), in which point-level semantic information is annotated to each point. + +Creating LPCs manually or semi-manually is a time-consuming task. Therefore, sharing LPCs in an open standard format is becoming increasingly important for the development of more advanced deep learning algorithms for object detection, semantic segmentation, and instance segmentation. Even though several data formats are used to distribute LPC, there is a variety to represent the semantic information depending on distributors or domains. This discussion paper analyzes three popular formats of ASCII text, PLY, and LAS, for supporting LPC and finally proposes a practice to effectively apply HDF5 to facilitate the sharing and importing of LPC datasets. + The HDF5 profile for labeled point cloud data + 21-077 - - 15-042r5 - OGC TimeseriesML 1.2 – XML Encoding of the Timeseries Profile of Observations and Measurements - 2018-12-18 - 15-042r5 - TimeseriesML 1.2 – XML Encoding of the Timeseries Profile of Observations and Measurements - TimeseriesML 1.2 defines an XML encoding that implements the OGC Timeseries Profile of Observations and Measurements, with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of data exchange requirements. - - James Tomkins, Dominic Lowe - - - - - 10-128 - OGC Compliance Testing White Paper - OGC Compliance Testing White Paper - - - - - - 10-128 - 2010-10-22 - This white paper describes the OGC Compliance Testing Program. It provides -information about: -• The need for compliance testing to enable interoperability -• How to obtain compliance certification -• The difference between implementing and being certified -• How compliance benefits providers and users of technology -• The proper use of the “Certified OGC Compliant” mark -• Suggested language for procurement documents -• Trademark licensing fees -• An example of an OGC compliance test - Luis Bermudez - - - George Percivall - 04-051 - OWS1.2 Image Handling Design - 04-051 + 21-077 - - Image Handling is a thread in the OGC Web Services 1.2 (OWS1.2). This document defines the system design for Image Handling in OWS1.2. The system design responds to the requirements in OWS 1.2 Image Handling Requirements. The system design specifies two main services: Image Archive Service and Image Catalogue Service. Interfaces for these two services are defined using previously defined OWS service interfaces. - OWS1.2 Image Handling Design - - - - 2004-09-26 + + Taehoon Kim, Wijae Cho, Kyoung-Sook Kim + 2022-05-06 + The HDF5 profile for labeled point cloud data - + + + This standard defines the version 3.0 of a geospatial extension to the OASIS eXtensible Access Control Markup Language (XACML) Version 3.0 standard. It thereby enables the interoperable definition of access rights / constraints using the XACML 3.0 language, processing model and policy schema but extends the ability to phrase conditions on geographic characteristics of subjects, resources and objects. +In that sense, a GeoXACML policy could restrict access to geospatial information, e.g. provided by OGC Web Services. However, a GeoXACML policy could also restrict access to non geospatial assets by stating restrictions for access based on the location of the user (or the mobile device used) trying to access the protected assets. Therefore, this standard applies to main stream IT. +For enabling processing of access control decisions based on geometry, Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core inherits by normative reference ISO 19125 which defines a geometry model and functions on geometry instances which enrich the XACML 3.0 specification. + + 13-100 + + 13-100 + Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core + 2013-11-06 - 15-068r2 - Testbed 11 GeoPackaging Engineering Report - 2015-08-19 - 15-068r2 - - OGC® Testbed 11 GeoPackaging Engineering Report - Mobile location based service applications and users have an increasing need for access to geospatial data from any place in the world, including locations with limited or intermittent connectivity to communications networks. Maintaining consistency between copies of the same data held by different mobile devices can be a significant challenge when connectivity is limited or intermittent. This OGC Engineering Report describes the work carried out in OGC Testbed-11 in relation to the creation and synchronization of SQLite databases that conform to the OGC GeoPackage standard . This Engineering Report describes an approach for the use of various standards to achieve such synchronization. The document also presents the results and lessons learnt from the experimentation conducted in the Testbed. - - Gobe Hobona;Roger Brackin - + Andreas Matheus + + OGC Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core - - + - - OpenGIS Web Feature Service (WFS) Implementation Specification (Corrigendum) - - Web Feature Service (WFS) Implementation Specification (Corrigendum) - 06-027r1 - - 2006-08-22 - This document is a corrigendum for OGC Document 04-094. Specifically, this document corrects the files referenced in ANNEX A and found in the OGC schema repository. - Panagiotis (Peter) A. Vretanos + + - 06-027r1 + Jerome Gasperi + 2007-02-05 + This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGCTM Catalogue Services Specification v2.0.0 (with Corrigendum) [OGC 04-021r3] + + GML Application Schema for EO Products + 06-080r1 + GML Application Schema for EO Products + 06-080r1 + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Documents of type Implementation Specification - deprecated + + + 15-100r1 + Observations and Measurements – JSON implementation + Simon J D Cox, Peter Taylor + - Documents of type Implementation Specification - deprecated - Documents of type Implementation Specification - deprecated + + 15-100r1 + OGC Observations and Measurements – JSON implementation + + This Discussion Paper specifies a potential OGC Candidate Standard for a JSON implementation of the OGC and ISO Observations and Measurements (O&M) conceptual model (OGC Observations and Measurements v2.0 also published as ISO/DIS 19156). This encoding is expected to be useful in RESTful implementations of observation services. +More specifically, this Discussion Paper defines JSON schemas for observations, and for features involved in sampling when making observations. These provide document models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities. + + 2015-12-09 + - + + Richard Martell + + 2009-02-05 + 07-110r4 + 07-110r4 + CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW + - This document describes the architecture implemented by Open Geospatial Consortium’s (OGC) Sensor Web Enablement Initiative (SWE). In contrast to other OGC SWE stan-dards, this document is not an implementation standard. + CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW - - 2008-07-08 - - - OGC® Sensor Web Enablement Architecture - 06-021r2 - 06-021r2 - Sensor Web Enablement Architecture - Ingo Simonis + + This profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0.2 specification; it qualifies as a ‘Class 2’ profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards. - - Testbed-12 GeoPackage US Topo Engineering Report - Robert Cass - 2017-05-12 - 16-037 - Testbed-12 GeoPackage US Topo Engineering Report - - - + + + 2014-02-26 + This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request which allow scaling of a coverage during its server-side processing in a GetCoverage request. + 12-039 + OGC® Web Coverage Service Interface Standard - Scaling Extension + 12-039 + Web Coverage Service Interface Standard - Scaling Extension + + Peter Baumann, Jinsongdi Yu + + - 16-037 - - This OGC Engineering Report documents the outcome of the US Topo experiment. The focus of the US Topo experiment was to generate GeoPackages by combining USGS Topo Map Vector Data Products [1]; and the Topo TNM Style Template [2]. The output GeoPackages will contain both features and instructions for styling these features as well as orthoimagery, shaded relief raster tilesets, national wetlands raster tilesets and elevation data derived from USGS provide 1/9 arc second elevation imagery. The process used to generate the GeoPackage is explained. Problems and obstacles encountered decoding the source product and styles and converting these artifacts to a GeoPackage are explained with recommendations for improvements. Additionally, the experience applying the generated GeoPackage in two use cases proposed for this testbed will be evaluated. The introduction of symbolization for vector features will be articulated as a proposed extension for GeoPackage. Any issues related to encoding the TNM style template using the extension are documented. + + + + + OpenGIS SensorML Encoding Standard v 1.0 Schema Corregendum 1 + + + SensorML Encoding Standard v 1.0 Schema Corregendum 1 + 07-122r2 + 2007-11-12 + 07-122r2 + + + Mike Botts, Simon Cox + Changes to the 1.0 schemas - - Marie-Françoise Voidrot-Martinez, Chris Little, Jürgen Seib, Roy Ladner, Adrian Custer, Jeff de La B + + A Geolinked Data Access Service (GDAS) provides a way to publish and access data that refers to spatial features (e.g. population data for countries). A GDAS can expose data from non-GIS databases so that it can be manipulated and mapped with the aid of a Geolinking Service. - 12-111r1 - Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data + Geolinked Data Access Service + + 04-010r1 + 2004-05-04 + Geolinked Data Access Service + 04-010r1 + + + Peter Schut - - 12-111r1 - - - 2014-04-14 - OGC Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data - This document proposes a set of best practices and guidelines for implementing and using the Open Geospatial Consortium (OGC) Web Map Service (WMS) to serve maps which are time-dependent or elevation-dependent. In particular, clarifications and restrictions on the use of WMS are defined to allow unambiguous and safe interoperability between clients and servers, in the context of expert meteorological and oceanographic usage and non-expert usage in other communities. This Best Practice document applies specifically to WMS version 1.3, but many of the concepts and recommendations will be applicable to other versions of WMS or to other OGC services, such as the Web Coverage Service. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + + + + Web Feature Service (Transactional) + Web Feature Service + + + 2002-05-17 + Web Feature Service + Web Feature Service (Transactional) + 02-058 + Peter Vretanos + + + + + The purpose of the Web Feature Server Interface Specification (WFS) is to describe data manipulation operations on OpenGIS + 02-058 - - Topic 6.3 - Schema for Coverage Geometry and Functions – Part 3: Processing Fundamentals - 21-060r2 + + + + The amount of (geospatial) data collected and transferred is rapidly increasing. The purpose of this ER is to describe options and recommendations for the delivery of large amounts of data as database delivery. This ER therefore describes and evaluates different aspects of this challenge: + +Data management: How to organize large amounts of data so that it can be efficiently accessed through OGC service interfaces? + +Encoding: Transferring large amounts of vector data in XML based formats (e.g. GML, O&M) leads to specific challenges as the parsing of large XML files is often problematic. + +Available implementation: Several software packages exist to handle large amounts of geospatial data. We will investigate to which these approaches are in-line with OGC standards or how standards compliance could be achieved. + +The evaluation and findings in the related Big Data Tile Database Implementation are documented in this ER as well. The objective of this ER is to provide recommendations of how the delivery of large amounts of raster data as database delivery can be considered within OGC specifications and future activities. + 16-036r1 + 2017-06-30 + Testbed-12 Big Data Database Engineering Report + - - This document defines, at a high, implementation-independent level, operations on coverages - i.e., digital representations of space-time varying geographic phenomena - as defined in ISO 19123-1. Specifically, regular and irregular grid coverages are addressed. Future versions will additionally support further axis types as well as further coverage types from ISO19123-1, such as point clouds and meshes in particular. While the core functionality is expected to be generic and applicable for any coverage, there may be special functionality for particular coverage types. - + + Christian Autermann + 16-036r1 + Testbed-12 Big Data Database Engineering Report + + + + + - Peter Baumann - 21-060r2 - OGC Abstract Specification Topic 6: Schema for Coverage Geometry and Functions – Part 3: Processing Fundamentals + 23-043 + OGC Testbed 19 Analysis Ready Data Engineering Report + Liping Di, David J. Meyer,r Eugene Yu + 23-043 + OGC Testbed 19 Analysis Ready Data Engineering Report 2024-07-05 - - - - GeoSciML is a model of geological features commonly described and portrayed in geological maps, cross sections, geological reports and databases. The model was developed by the IUGS CGI (Commission for the Management and Application of Geoscience Information) and version 4.1 is the first version officially submitted as an OGC standard. This specification describes a logical model and GML/XML encoding rules for the exchange of geological map data, geological time scales, boreholes, and metadata for laboratory analyses. It includes a Lite model, used for simple map-based applications; a basic model, aligned on INSPIRE, for basic data exchange; and an extended model to address more complex scenarios. + + + Implementations of the Analysis Ready Data (ARD) concept are consistent with the FAIR principles of finding, accessing, interoperating, and reusing physical, social, and applied science data with ease. The goal of this Testbed 19 OGC Engineering Report (ER) is to advance the provision of geospatial information by creating, developing, identifying, and implementing ARD definitions and capabilities. Specifically, this ER aims to increase the ease of use of ARD through improved backend standardization and varied application scenarios. Additionally, this work seeks to inform ARD implementers and users about standards and workflows to enhance the capabilities and operations of ARD. Ultimately, the goal of the work described in this ER is to maximize ARD capabilities and operations and contribute to the enhancement of geospatial information provision. -The specification also provides patterns, profiles (most notably of Observations and Measurements - ISO19156), and best practices to deal with common geoscience use cases. +Four distinct scenarios – gentrification, synthetic data, coverage analysis, and coastal studies – are explored to reveal both the strengths and limitations of the current ARD framework. The gentrification scenario, which utilizes existing Committee on Earth Observation Satellites (CEOS) ARD data, highlights the need to expand ARD’s scope beyond Earth Observation (EO) data. The integration of diverse data types, such as building footprints and socio-economic statistics, is crucial for comprehensive analysis. The synthetic data scenario explores the potential of simulated EO imagery to enhance data availability and diversity for machine learning applications. However, challenges in standardization and quality assessment require further investigation. The analysis of coverages for ARD reveals the importance of clear pixel interpretation (“pixel-is-point” vs. “pixel-is-area”) and standardized units of measure for seamless integration and analysis. Additionally, enriching the metadata structure with defined extensions is crucial for efficient data discovery and understanding. The coastal study scenario, where in-situ data needs to be elevated to ARD, emphasizes the need for flexible levels of readiness. Different analytical tasks may require distinct data properties, necessitating adaptable standards that cater to temporal emphasis, spatial alignment, and non-GIS applications like machine learning. + +This work identified several key areas for improvement: + +encompassing non-EO data such as building footprints, socio-economic statistics, synthetic data, and in-situ measurements; +establishing guidelines and quality controls for incorporating diverse data types; +tailoring data specifications to accommodate different analytical needs, including temporal emphasis and non-GIS applications; and +implementing structured metadata with defined extensions for enhanced data discovery, understanding, and provenance tracking. +In addition to the above recommendations, the interoperability and support of ARD in wider communities warrants further exploration and implementation. Additionally, areas such as uniform evaluation and compliance certification could be further investigated to ensure consistency in data readiness across various hierarchies and application domains. + + + 19-020r1 + OGC Testbed-15: Catalogue and Discovery Engineering Report + 19-020r1 + + + Yves Coene + + This OGC Testbed-15 Engineering Report (ER) describes the results of the Earth Observation (EO) Process and Application (EOPAD) Task in the Cloud Processing and Portrayal (CPP) thread of OGC Testbed-15. The ER presents the data model and service interface of the catalogue service allowing for discovery of EO applications and related processing services for subsequent deployment and/or invocation in a distributed environment. +The ER also provides the architectural and implementation details of the software components that were developed as part of the activity and which interact through the described data model. These software components include catalogue clients, catalogue servers and transactional Web Processing Service (WPS-T) servers. + + + 2019-12-12 + + OGC Testbed-15: Catalogue and Discovery Engineering Report + + + 2017-02-23 + + The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. +The application of CDB to future simulation architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the High Level Architecture - -Federation Object Model (HLA/FOM) and DIS protocols, the application of the CDB standard provides a Common Environment to which inter-connected simulators share a common view of the simulated environment. +The CDB standard defines an open format for the storage, access and modification of a synthetic environment database. A synthetic environment is a computer simulation that represents activities at a high level of realism, from simulation of theaters of war to factories and manufacturing processes. These environments may be created within a single computer or a vast distributed network connected by local and wide area networks and augmented by super-realistic special effects and accurate behavioral models. SE allows visualization of and immersion into the environment being simulated . +This standard defines the organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The standard makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. A series of associated OGC Best Practice documents define rules and guidelines for data representation of real world features. +The CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. A CDB data store can include terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the data store can includes the specific attributes of the synthetic environment data as well as their relationships. +The associated CDB Standard Best Practice documents provide a description of a data schema for Synthetic Environmental information (i.e. it merely describes data) for use in simulation. The CDB Standard provides a rigorous definition of the semantic meaning for each dataset, each attribute and establishes the structure/organization of that data as a schema comprised of a folder hierarchy and files with internal (industry-standard) formats. +A CDB conformant data store contains datasets organized in layers, tiles and levels-of-detail. Together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB compliant data store is specifically tailored for real-time applications. + + 15-113r3 + + Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure + + 15-113r3 + Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure + Carl Reed + + + + + Stephane Fellah, Steven Keens + + This document defines a messaging framework to conduct communications between the OGC web services. It is independent of any transport protocol and any messaging encoding. By using the framework, the service designer could focus only on the message definitions and messaging flows for every action supported by the service, without worry on the messaging transport and delivery. The framework should considerably simplify the implementations of the OGC web services and should enable service chaining. - 16-008 - Geoscience Markup Language 4.1 - OGC Geoscience Markup Language 4.1 (GeoSciML) - 2017-01-31 - - - GeoSciML Modeling Team - - 16-008 + + OWS Messaging Framework + 2003-01-20 + 03-029 + OWS Messaging Framework + + 03-029 - - 06-103r3 - - - John Herring + + Paulo Sacramento + ADES & EMS Results and Best Practices Engineering Report + 18-050r1 - OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture + - - 06-103r3 - Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture - 2007-01-29 - - The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. + This Engineering Report (ER) describes best practices and results gathered through the work performed in the Exploitation Platforms Earth Observation Clouds (EOC) Thread of OGC Testbed-14 concerning the Application Deployment and Execution Service (ADES) and the Execution Management Service (EMS). Both the ADES and EMS were identified by the European Space Agency (ESA), beforehand, as essential elements of a Thematic Exploitation Platform (TEP). -Part 1 “Common Architecture supplies the common feature model for use by applications that will use the Simple Features data stores and access interfaces. +In the context of a generic Earth Observation Exploitation Platform ecosystem, populated by TEPs and Mission Exploitation Platforms (MEPs), which make use of cloud computing resources for Earth Observation data processing, ESA has established two fundamental building blocks within a TEP, with different functions, the ADES and the EMS. Users interact with a TEP using a Web Client, and the TEP contains a EMS and a ADES. The EMS includes most of the control logic, required for deploying and executing applications in different MEPs and TEPs, the chaining thereof, and the overall coherence of the execution chain (e.g. gathering all outputs and enabling their presentation to the user by a client sensibly). The ADES instead is responsible for the single application deployment and execution on a specific platform. Therefore, it is expected that there are ADES instances both in a TEP and in the individual MEPs. -Part 2 provides a standard SQL implementation of the abstract model in Part 1. (Note: The OpenGIS® Simple Features Interface Standards for OLE/COM and CORBA are no longer current and are not provided here.) +The Testbed-14 Participants have experimented with different options for what concerns the functionality allocated to each of the two components, the information required by each of them and the interface requirements between them in order to produce a consistent chain, compliant with ESA’s objectives (as the Sponsor). This report describes these experiments, providing their results and suggesting best practices on how the two services should be engineered in the Exploitation Platform context. -The corresponding standard for the Web is the OpenGIS® Web Feature Service Interface Standard http://www.opengeospatial.org/standards/wfs. - - - - 20-011 - SCIRA Pilot Engineering Report +The OGC Web Processing Service (WPS) 2.0 standard is of particular relevance given that it is well-established in the OGC Web Service context, specifically that concerning processing, its interoperability value has been clearly demonstrated, and it therefore provides a useful mechanism for standardizing interfaces between components of heterogeneous provenance and implementation. + 18-050r1 + + + OGC Testbed-14: ADES & EMS Results and Best Practices Engineering Report + 2019-02-08 - - + + + OWS-8 Cross Community Interoperability (CCI) Semantic Mediation Engineering Report + 11-063r6 + + The OWS-8 Cross Community Interoperability (CCI) thread built on progress made in the recent OWS-7 initiative to cover key technology areas that could not be addressed within the scope of that initiative. The OWS-8 CCI thread aimed to increase interoperability within communities sharing geospatial data, including advancing of interoperability among heterogeneous data models, advancing strategies to share styles to provide a more common and automated use of symbology, improvement of KML, and advancing schema automation allowing communities to better share their information artefacts. This OGC engineering report aims to present findings from CCI thread activities towards advancement of semantic mediation involving data retrieved from heterogeneous data models that are available through web services conformant to OGC standards. +The engineering report will briefly introduce relevant details of the semantic web and mediation. The document will make recommendations on establishing a semantic mediation architecture that uses OGC web services and emerging practice from the semantic web community. Based on the scenario adopted by the CCI thread, the document will also discuss the pros and cons of adopting relevant standards. The engineering report will offer recommendations on how specific OGC standards may be adopted or modified in order to support semantic mediation. + + Gobe Hobona, Roger Brackin - OGC SCIRA Pilot Engineering Report - - Sara Saeedi - 2020-05-04 - This engineering report (ER) captures Smart City Interoperability Reference Architecture (SCIRA) Pilot implementation outcomes and findings to demonstrate the risk mitigation and safety capability of the SCIRA interoperable and standard-based architecture. SCIRA Pilot is an OGC (Open Geospatial Consortium) Innovation Program project sponsored by the US Department of Homeland Security (DHS) Science & Technology (S&T) in collaboration with the city of St. Louis, Missouri. The purpose of this project is to advance standards for smart and safe cities and develop open, interoperable design patterns for incorporating the Internet of Things (IoT) sensors into city services. - 20-011 - - - 2007-05-10 - - Change Request: WCS: Add Transaction operation - - - 06-043r3 - - 06-043r3 - WCS: Add Transaction operation - Specify an additional optional - Arliss Whiteside + 2011-11-23 + 11-063r6 + OWS-8 Cross Community Interoperability (CCI) Semantic Mediation Engineering Report + - - 12-006 - 12-006 - Sensor Observation Service Interface Standard - + + Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage + 2018-12-19 + Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage + 16-070r3 + 16-070r3 - - OGC® Sensor Observation Service Interface Standard - - The SOS standard is applicable to use cases in which sensor data needs to be managed in an -interoperable way. This standard defines a Web service interface which allows querying -observations, sensor metadata, as well as representations of observed features. Further, this -standard defines means to register new sensors and to remove existing ones. Also, it defines -operations to insert new sensor observations. This standard defines this functionality in a binding -independent way; two bindings are specified in this document: a KVP binding and a SOAP -binding. - Arne Bröring, Christoph Stasch, Johannes Echterhoff - 2012-04-20 - - - - Compliance Testing Program Policies & Procedures - - Compliance Testing Program Policies & Procedures - 08-134r11 - 2022-06-28 - Gobe Hobona - - This document describes the Open Geospatial Consortium (OGC) Compliance Testing Program. The document describes the roles and responsibilities, compliance testing procedures, development of test packaging, and policies for developing and releasing the software used for testing for compliance to OGC Standards. - 08-134r11 + This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features. + + + + Carl Reed + + + 06-184r2 + 2007-08-14 + Christian Elfers, Roland M. Wagner - + + GeoDRM Engineering Viewpoint and supporting Architecture + GeoDRM Engineering Viewpoint and supporting Architecture + 06-184r2 + + + This GeoDRM engineering viewpoint document describes use cases and concepts for GeoDRM, as well as references to distributed computing concepts which are not GeoDRM sensu stricto but are required for any GeoDRM implementation. + - - Jeff Yutzler - - 18-101 - Vector Tiles Pilot Extension Engineering Report + + 2007-10-09 + 07-055r1 + + + This Discussion Paper describes an interface specification for a web coordinate transformation service that now builds on version 1.1 of the OWS Common Specification [OGC 06-121r3]. All versions of this document specify an + Web Coordinate Transformation Service + + + Arliss Whiteside, Markus U. M + + Web Coordinate Transformation Service + 07-055r1 + + + + Yves Coene + 05-140 + OWS-3 Imagery Workflow Experiments: Enhanced Service Infrastructure Technology Architecture and Standards in the OWS-3 Testbe + 05-140 + + OWS-3 Imagery Workflow Experiments: Enhanced Service Infrastructure Technology Architecture and Standards in the OWS-3 Testbe + This document describes the results of an experiment addressing issues relating to the application workflow processing incorporating a variety of OGC specifications. It details the inputs provided to the Open Geospatial Consortium's (OGC) OWS-3 Testbed and the architecture of the testbed related to the ESA Service Support Environment (SSE). +It is a formal deliverable of work package 6610 of the Enhanced Service Infrastructure Technology (ESIT) project and is a joint Spacebel and Spot Image document. + - The purpose of the OGC Vector Tiles Pilot Extension (VTPExt) was to address portrayal and style encoding concerns that were discovered in the initial phase of the Vector Tiles Pilot (VTP). During the VTPExt, participants selected a common baseline style used by all participants and in some cases created additional style offerings. The work conducted during the VTPExt has adhered to the established findings from the initial VTP documented in the VTP Summary Engineering Report (ER) [1]. - -This document describes the following: - -the research and evaluation to determine approach(es) to apply styling to Mapbox and GeoJSON Tiled Feature Data through Web Feature Service (WFS) 3.0, Web Map Tile Service (WMTS) 1.0, and GeoPackage (GPKG) 1.2, - -the styling approach, challenges, and interoperability considerations discovered during the initiative, and - -any extensions required or best practices recommended to facilitate development, encoding, offering, and exchange of styles. This includes how styles are offered from servers, how the desired style offering can be selected by the client from multiple server style offerings (e.g. GetStyles request), and how clients can apply their own styles. - - Vector Tiles Pilot Extension Engineering Report - 18-101 + + 2006-03-30 + - - 2019-04-30 - - 05-126 - OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architectu - Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture - 05-126 - + - + 14-086r1 + Aircraft Access to SWIM (AAtS) Harmonization Project Summary Report + OGC® Aircraft Access to SWIM (AAtS) Harmonization Project Summary Report + + + 2014-11-03 + 14-086r1 + Josh Lieberman, Johannes Echterhoff, Matt de Ris, George Wilber + + This OGC® document summarizes the Aircraft Access to SWIM (AAtS) Harmonization activity developed by a team funded by the FAA and led by the Open Geospatial Consortium (OGC). The activity involved assembling a core team of industry participant experts to analyze and harmonize four standards suites and/or standards-based architectures relevant to air-ground information exchange: +• The Aircraft Access to SWIM (AAtS) concept, +• RTCA aeronautical information services (AIS) and meteorological (MET) information data link service committee’s (SC-206) concepts and standards, +• Air-Ground Information Exchange A830 (AGIE) standard and +• OGC standards and architectural perspectives. +Elements of this effort have included: +• Creation and public release of a Request for Information +• Analysis of the fits and overlaps between the four standards suites +• Engagement with ongoing standards development efforts to reduce incompatibilities + - - This part of OpenGIS - Keith Ryden - 2005-11-30 - - OGC® Canadian Geospatial Data Infrastructure WFS and GML Best Practices - CGDI WFS and GML Best Practices - 08-002 - - 08-002 - - - 2008-04-29 + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Documents of type Implementation Specification - deprecated + Documents of type Implementation Specification - deprecated + Documents of type Implementation Specification - deprecated + + - + 23-048 + OGC Testbed 19 Draft API - Geodatacubes specification - Peter Rushforth - This document gives guidelines and recommendations for administrators, users and implementers of Web Feature Services serving Geography Markup Language encoded response documents. - - - 23-043 - OGC Testbed 19 Analysis Ready Data Engineering Report - Implementations of the Analysis Ready Data (ARD) concept are consistent with the FAIR principles of finding, accessing, interoperating, and reusing physical, social, and applied science data with ease. The goal of this Testbed 19 OGC Engineering Report (ER) is to advance the provision of geospatial information by creating, developing, identifying, and implementing ARD definitions and capabilities. Specifically, this ER aims to increase the ease of use of ARD through improved backend standardization and varied application scenarios. Additionally, this work seeks to inform ARD implementers and users about standards and workflows to enhance the capabilities and operations of ARD. Ultimately, the goal of the work described in this ER is to maximize ARD capabilities and operations and contribute to the enhancement of geospatial information provision. - -Four distinct scenarios – gentrification, synthetic data, coverage analysis, and coastal studies – are explored to reveal both the strengths and limitations of the current ARD framework. The gentrification scenario, which utilizes existing Committee on Earth Observation Satellites (CEOS) ARD data, highlights the need to expand ARD’s scope beyond Earth Observation (EO) data. The integration of diverse data types, such as building footprints and socio-economic statistics, is crucial for comprehensive analysis. The synthetic data scenario explores the potential of simulated EO imagery to enhance data availability and diversity for machine learning applications. However, challenges in standardization and quality assessment require further investigation. The analysis of coverages for ARD reveals the importance of clear pixel interpretation (“pixel-is-point” vs. “pixel-is-area”) and standardized units of measure for seamless integration and analysis. Additionally, enriching the metadata structure with defined extensions is crucial for efficient data discovery and understanding. The coastal study scenario, where in-situ data needs to be elevated to ARD, emphasizes the need for flexible levels of readiness. Different analytical tasks may require distinct data properties, necessitating adaptable standards that cater to temporal emphasis, spatial alignment, and non-GIS applications like machine learning. + OGC Testbed 19 Draft API - Geodatacubes specification + 23-048 + + 2024-07-22 + Matthias Mohr + + + This OGC Testbed 19 Engineering Report documents a draft OGC API — GeoDataCube Standard (aka GDC API). The OGC Member participants in this Testbed 19 activity developed, documented, and tested the draft OGC GDC API Standard. The draft will be submitted to the OGC GeoDataCube Standards Working Group (SWG) as a new standards work item. -This work identified several key areas for improvement: +The OGC GeoDataCube SWG was chartered to respond to the long-standing issue of establishing a standard that supports accessing and processing geospatial datacubes in an interoperable way. The draft OGC API — GeoDataCube that was developed in OGC Testbed 19 responds to this need and proposes a draft API specification. -encompassing non-EO data such as building footprints, socio-economic statistics, synthetic data, and in-situ measurements; -establishing guidelines and quality controls for incorporating diverse data types; -tailoring data specifications to accommodate different analytical needs, including temporal emphasis and non-GIS applications; and -implementing structured metadata with defined extensions for enhanced data discovery, understanding, and provenance tracking. -In addition to the above recommendations, the interoperability and support of ARD in wider communities warrants further exploration and implementation. Additionally, areas such as uniform evaluation and compliance certification could be further investigated to ensure consistency in data readiness across various hierarchies and application domains. - Liping Di, David J. Meyer,r Eugene Yu - - +The Testbed 19 GDC initiative targeted enhanced interoperability. The draft GDC API Standard was based on OGC API — Common, OGC API — Coverages Standard, OGC API — Processes Standard, the STAC API, and the openEO API. The Testbed 19 participants concentrated on server and client application development, and usability testing based on conformance classes and use cases. The draft GDC API is defined as an OpenAPI 3.0 document and provides endpoints for capabilities, data discovery/access, process discovery, and data processing. Notably, the draft GDI API Standard is extensible through additional implementations of OGC API Standards or openEO API parts. Documentation is available in machine-readable YAML and human-friendly HTML through a GitHub repository. - - OGC Testbed 19 Analysis Ready Data Engineering Report - 23-043 - 2024-07-05 - - - - - + + 12-144 - - 11-072r2 - OWS-8 Aviation - WXXM Engineering Report - 11-072r2 - This OGC™ document specifies the advancement of WXXM and Weather Concepts in -the OWS-8 Aviation Thread. The focus is on investigating and demonstrating the -applicability and suitability of WXXM in producing accurate, real-time aircraft weather -radar data using OGC™ Web Coverage Services (WCS) to be used by meteorological -applications and services supporting aviation. Such applications provide information -which enhances safe and efficient tactical and - Wenny Rahayu, Torab Torabi, Andrew Taylor-Harris, Florian Puersch + + OWS-9 Architecture - Registry Engineering Report + 12-144 + OGC® OWS-9 Architecture - Registry Engineering Report + This OGC® Engineering Report provides guidelines for the harvest, registration and retrieval of aviation resources from an OGC web catalogue/registry service (OGC CSW-ebRIM), with particular emphasis on ISO metadata resources. Alternatives for selective and efficient retrieval of such resources are also described along with lessons learned. The OGC CSW-ebRIM registry interface is evaluated against SESAR registry requirements, documented as a gap analysis, to assess whether there are any obstacles to implementing SESAR registry with an OGC CSW-ebRIM interface. - OWS-8 Aviation - WXXM Engineering Report - 2012-01-25 + + + David Burggraf + 2013-06-18 - + + + 01-037 + 01-037 + Location Organizer Folder + + *RETIRED* The Location Organizer Folder (LOF) is a GML document that provides a structure for organizing the information related to a particular event or events of interest. + Location Organizer Folder - 3D Tiles Specification - 22-025r4 - Patrick Cozzi, Sean Lilley + - This document describes the specification for 3D Tiles, an open standard for streaming massive heterogeneous 3D geospatial datasets. - - 22-025r4 - 3D Tiles Specification - - - 2023-01-12 + 2001-03-30 + Ron Lake - - 22-000 - OGC GeoPose Reviewers Guide - The GeoPose Reviewers Guide is a public resource structured to provide quick answers to questions which a reviewer may have about the OGC GeoPose specification. This OGC document is provided to support professionals who need to understand OGC GeoPose and/or are reviewing the GeoPose draft standard but do not wish to implement it. - -GeoPose 1.0 is an OGC Implementation Standard for exchanging the position and orientation (Poses) of real or virtual geometric objects within reference frames anchored to the Earth’s surface (Geo) or within other astronomical coordinate systems. The standard specifies two Basic forms with no configuration options for common use cases, an Advanced form with more flexibility for more complex applications, and five composite GeoPose structures that support time series plus chain and graph structures. - - - - 22-000 + + + + + + + + + + + + + + + + + + + + + + + + Documents of type Retired Specification - OGC GeoPose Reviewers Guide - C. Perey, J.G. Morley, J. Lieberman, R. Smith, M. Salazar, C. Smyth - - 2023-09-08 - + + Documents of type Retired Specification + Documents of type Retired Specification - - + + Simon Cox + Requirements for some specific simple solid, plane and line geometry types - 06-050r3 - GeoRSS, An Introduction to - GeoRSS is simple proposal for geo-enabling, or tagging, really simple syndication (RSS) feeds with location information. GeoRSS proposes a standardized way in which location is encoded with enough simplicity and descriptive power to satisfy most needs to describe the location of Web content. GeoRSS may not work for every use, but it should serve as an easy-to-use geotagging encoding that is brief and simple with useful defaults but extensible and upwardly-compatible with more sophisticated encoding standards such as the OGC (Open Geospatial Consortium) GML (Geography Markup Language). - 06-050r3 - - - 2006-07-19 - GeoRSS, An Introduction to - Carl Reed - + + 07-001r3 + Requirements for some specific simple solid, plane and line geometry types + + This specification describes requirements for specific geometry types, including some simple solids, and planes and lines defined using an implicit parameterization. + 2007-05-02 + + 07-001r3 + - - - + + 11-085r1 + OWS-8 Bulk Geodata Transfer Using GML Engineering Report + 2011-11-07 + OWS-8 Bulk Geodata Transfer Using GML Engineering Report + Panagiotis (Peter) A. Vretanos + - 14-057 - UK Interoperability Assessment Plugfest (UKIAP) Engineering Report - The Open Geospatial Consortium (OGC), the UK Ordnance Survey, AGI and Dstl conducted a first of a series of events called the United Kingdom Interoperability Assessment Plugfest (UKIAP) 2014. The purpose of UKIAP 2014 is to advance the interoperability of geospatial products and services based on OGC standards within the UK geospatial information (GI) community. The results of the Plugfest will allow Ordnance Survey to provide best practice guidance to those who want to consume or implement geospatial web services or products based on OGC standards. UKIAP 2014 is open to open- and closed source vendors and to all GI organizations in the UK to involve as many participants in the initiative as possible. - + - Bart De Lathouwer, Peter Cotroneo, Paul Lacey - 14-057 - OGC® and Ordnance Survey - UK Interoperability Assessment Plugfest (UKIAP) Engineering Report - 2015-03-26 + + 11-085r1 + + This document describes the work done during the OWS-8 test bed investigating methods and apparatus for distributing individual geospatial data sets and/or collections of data sets in a consistent manner between machines that may or may not be connected via a network. The investigation focuses on the initialization of a target WFS, from a source WFS, for the purpose of GeoSynchronization. Data, schema, metadata and/or topology are exported from a source WFS, transferred to a target WFS (either electronically or physically via some media) and then imported into the target WFS. From that point on, the two WFS's are maintained in synchrony using a Geosynchronization Service (see OGC 10-069r2). + + + OGC Testbed-13: Security Engineering Report + + 2018-01-11 + 17-021 + The Security Engineering Report (ER) covers two Testbed 13 topics: + +The implementation of authentication and authorization plugins for the QGIS open source desktop GIS client and + +the implementation of secured workflow. + +The authentication plugins implement the SAML2 ECP with PAOS binding and IdP discovery from the SAML2 federation metadata URL. The access right delegation plugin implements applicable OAuth2 grant types. + +Regarding the first topic, this ER discusses the fit for purpose aspects for the OAuth2 and SAML2 in the context of an open source desktop application. It also covers the QGIS development as well as building and deployment aspects. Most of the work related to this topic was provided by Secure Dimensions. + +Regarding the second topic, this ER outlines the architecture approach and the implications to implementations for security in OGC service workflows as well as the implementation approach itself. Most of the work related to this topic was provided by 52°North. + + 17-021 + Testbed-13: Security Engineering Report + + Andreas Matheus + + - - - - OGC InfraGML 1.0: Part 6 – LandInfra Survey - Encoding Standard - 16-106r2 + + + 23-059 + 2024-04-18 + + + 23-059 + 2023 Open Standards Code Sprint Summary Engineering Report + Gobe Hobona, Joana Simoes - InfraGML 1.0: Part 6 – LandInfra Survey - Encoding Standard - 16-106r2 - This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. -InfraGML is published as a multi-part standard. This Part 6 addresses the Survey, Equipment, Observations and Survey Results Requirements Classes from LandInfra. + + + Advances in computing, storage, sensing, and other technology areas continue to find a place in the geospatial ecosystem that makes location information findable, accessible, interoperable, and reusable. To enable geospatial standards to meet the likely interoperability needs of future technologies, it is necessary for Standards Development Organizations (SDOs) such as OGC to continue to innovate. Such innovation relies on the ability to develop new standards and improve existing ones to better address emerging interoperability challenges. Code sprints are one of a number of initiative types that OGC conducts to accelerate such innovation. A code sprint is a collaborative and inclusive event driven by innovative and rapid programming with minimal process and organization constraints to support the development of new applications and candidate standards. + +The focus of this Engineering Report (ER) is a code sprint that was held from October 30th to November 1st, 2023. The code sprint was organized by the Open Geospatial Consortium (OGC) and hosted by Geovation in London, England. The code sprint was sponsored by Ordnance Survey (OS) at the Gold-level, as well as the European Union Satellite Centre (SatCen), US National Geospatial Intelligence Agency (NGA), and the UK Defence Science and Technology Laboratory (Dstl) at the Silver-level. As with previous OGC Code Sprints, a key goal of the October 2023 Open Standards Code Sprint was the acceleration of the development of OGC Standards and their implementation in software products. + +Standards in focus for this code sprint included several OGC API, data model, and encoding standards. In addition to OGC Standards, the code sprint also included a thread focusing on the “GEOINT Imagery Media for ISR” (GIMI) profile of the ISO Base Media File Format (ISOBMFF) and the High Efficiency Image Format (HEIF). The engineering report concludes that the code sprint met all of its objectives and achieved its goal of accelerating the development of OGC Standards and their implementation in software products. + +In relation to emerging extensions to OGC API Standards, the engineering report concludes that the Publish/Subscribe (PubSub), Security, and Schemas capabilities examined in this code sprint could potentially support other OGC API Standards. Regarding GIMI, the engineering report concludes that with minor changes to popular open-source base libraries a wide range of software can quickly make use of GIMI capabilities. + +Regarding the Model for Underground Data Definition and Integration (MUDDI), the engineering report concludes that the MUDDI Conceptual Model is implementable and could easily be used as the basis for a logical model that can be encoded in a variety of formats including GML, GeoJSON, and Geopackage. As for JSON-FG, the engineering report concludes that due to the evident increase in adoption across the developer community, there is an increasing need to offer validators so that developers can check for compliance more easily. + +The sprint participants made the following recommendations for future work items on OGC API Standards. + +Extension of OGC API — Records to support faceting and federated search. +Use case experimentation to examine how the Publish/Subscribe approach can support various OGC API standards workflows. +Prototyping and specification on an OpenAPI definition document for the OGC SensorThings API Standard. +Additional support for multiband raster data in OGC API — Maps/Tiles/Coverages (e.g., multispectral imagery, etc). +The sprint participants made the following recommendations for future work items on OGC Encoding Standards. + +Tiled complex, signed, and floating-point data in multiband raster data. +Performance benchmarking between various imagery formats, for a variety of use cases. +Extraction of the conceptual model of GMLJP2 to make it applicable to any ISOBMFF profile. +Development of an Implementation Standard for the logical model and encoding of data that conforms to the MUDDI. +Use of the MUDDI logical schema as a template for MUDDI compliance. +The sprint participants made the following recommendations for future work items on GIMI. + +Extension of open-source base libraries used by several other products for creation and modification of GIMI files. +Prototype streaming of large images from client applications to servers for storage through OGC API — Processes. +Prototyping of a JavaScript Object Notation (JSON) encoded alternative to Key-Length-Value (KLV) metadata for use in GIMI files. + 2023 Open Standards Code Sprint Summary Engineering Report + + + 12-052 + WCS 2.0.1 Corrigendum Release Notes + + Peter Baumann + + This document represents the release notes for the OGC Web Coverage Service (WCS) Interface Standard corrigendum 2.0.1. This corrigendum for WCS supersedes previous WCS versions. + 2012-07-12 + + 12-052 - Hans-Christoph Gruler - - - 2017-08-16 - - - 07-163 - Data View Architecture Engineering Report - - - - OWS-5 Data View Architecture Engineering Report + OGC WCS 2.0.1 Corrigendum Release Notes - 07-163 - - This OGC document presents a summary of the Data View Architecture experiment conducted as part of the Geo-Processing Workflow (GPW) thread in the OWS-5 test bed. The main activities in this experiment were the storage of Data Views in an ebRIM Catalog and the discovery and use of those Data Views by an Integrated Client. - David Rosinger, Stan Tillman - 2008-05-02 - - OWS-7 Information Sharing Engineering Report - 10-035r2 - + + - 10-035r2 - This Engineering Report describes an investigation and evaluation of various methods of sharing information within a collaborative environment accomplished during the OGC Web Services Testbed, Phase 7 (OWS-7). The intent of the OWS-7 Information Sharing activity was to move toward a standardized method of sharing geospatial data between Integrated Clients and potentially catalogs. This report reviews past OGC work within this area, makes recommendations based on the best parts of previous collaboration techniques, and provides recommendations for encoding documents for use in information sharing. - 2010-09-08 - - OWS-7 Information Sharing Engineering Report + 15-053r1 + Testbed 11 Implementing JSON/GeoJSON in an OGC Standard Engineering Report + OGC® Testbed 11 Implementing JSON/GeoJSON in an OGC Standard Engineering Report + + In the OGC Testbed 11, the Cross-Community Interoperability (CCI) thread had a key objective of building on the work accomplished in the OGC 8, 9 and 10 Testbeds. The goal of the CCI threads is to increase interoperability between communities sharing geospatial data. This thread made advances in semantic mediation approaches for data discovery, access and use of heterogeneous data models and heterogeneous metadata models. This particular Engineering Report (ER) is part of the OGC efforts to advance the OGC Architecture with the adoption of REST interfaces and more encodings such as JSON. - David Rosinger, Stan Tillman + 15-053r1 + Joan Masó + - + 2015-08-19 - - 20-040r3 - Topic 21 - Discrete Global Grid Systems - Part 1 Core Reference system and Operations and Equal Area Earth Reference System - This Abstract Specification lays the foundations for Discrete Global Grid Systems (DGGS). It defines Common classes for spatio-temporal geometry, topology, and reference systems using identifiers, a DGGS Core Reference system as a reference system using zonal identifiers with structured geometry that may be spatio-temporal, a suite of DGGS Core Functions, and it specifies Equal-Area Earth DGGS. The OGC DGGS Abstract Specification supports the specification of standardized DGGS infrastructures that enable the integrated analysis of very large, multi-source, multi-resolution, multi-dimensional, distributed geospatial data. Interoperability between OGC DGGS implementations is anticipated through implementation standards, and extension interface encodings of OGC Web Services. + + Jeff Yutzler - - - 2021-09-23 - Robert Gibb - 20-040r3 + + This OGC discussion paper presents the results of the GeoPackage Plugfest. In this +initiative, participants had the opportunity to evaluate the compliance and interoperability +of software that produces and consumes GeoPackages containing tiled raster data. + + 15-012r2 + + 15-012r2 + GeoPackage Plugfest Discussion Paper + OGC GeoPackage Plugfest Discussion Paper - - Topic 21 - Discrete Global Grid Systems - Part 1 Core Reference system and Operations and Equal Area Earth Reference System + 2015-08-19 - - + + This report summarizes the outcomes of a process to assess the maturity of implementations based on SWE standards. This report covers the following areas: +• SWE standards overview +• Implementations of SWE in major systems +• SWE software implementations and compliance +• SWE implementations in IP +• Recommendations and Observations +A main outcome is the summary assessment of the SWE Implementation Maturity as presented in the Preface based on the body of the report. + - - Coverage Implementation Schema - 09-146r6 - OGC Coverage Implementation Schema - 2017-09-15 - Peter Baumann, Eric Hirschorn, Joan Masó - - Coverages represent homogeneous collections of values located in space/time, such as spatio-temporal sensor, image, simulation, and statistics data. Common examples include 1-D timeseries, 2-D imagery, 3-D x/y/t image timeseries and x/y/z geophysical voxel models, as well as 4-D x/y/z/t climate and ocean data. Generally, coverages encompass multi-dimen­sional regular and irregular grids, point clouds, and general meshes. - -This Coverage Implementation Schema (CIS) specifies the OGC coverage model by establishing a concrete, interoperable, conformance-testable coverage structure. It is based on the abstract concepts of OGC Abstract Topic 6 [1] (which is identical to ISO 19123) which spec­i­fies an abstract model which is not per se interoperable – in other words, many different and incompatible implementations of the abstract model are possible. CIS, on the other hand, is interoperable in the sense that coverages can be conformance tested, regardless of their data format encoding, down to the level of single “pixels” or “voxels.” - -Coverages can be encoded in any suitable format (such as GML, JSON, GeoTIFF, or Net­CDF) and can be partitioned, e.g., for a time-interleaved representation. Coverages are independent from service definitions and, therefore, can be accessed through a variety of OGC services types, such as the Web Coverage Service (WCS) Standard [8]. The coverage structure can serve a wide range of coverage application domains, thereby contributing to harmon­ization and interoperability between and across these domains. - 09-146r6 - - - - Ocean Science Interoperability Experiment Phase 1 Report - 08-124r1 - + + + 13-032 + SWE Implementation Maturity Engineering Report + 13-032 + OGC® SWE Implementation Maturity Engineering Report + George Percivall + 2013-09-11 - 08-124r1 - Ocean Science Interoperability Experiment Phase 1 Report - 2011-01-03 - - - - Luis Bermudez - This OGC Engineering report details lessons learned and best practices defined as part of the Phase 1 Ocean Science Interoperability Experiment (Oceans IE). The Oceans IE was performed to investigate the use of OGC Web Feature Services (WFS) and OGC Sensor Observation Services (SOS) for representing and exchanging point data records from fixed in-situ marine platforms. The activity concluded that for the Oceans community use of in-situ sensors that the OGC Sensor Observation Services (SOS) was better suited than the use of OGC Web Feature Services (WFS) for this purpose. - - This standard defines the version 3.0 of a geospatial extension to the OASIS eXtensible Access Control Markup Language (XACML) Version 3.0 standard. It thereby enables the interoperable definition of access rights / constraints using the XACML 3.0 language, processing model and policy schema but extends the ability to phrase conditions on geographic characteristics of subjects, resources and objects. -In that sense, a GeoXACML policy could restrict access to geospatial information, e.g. provided by OGC Web Services. However, a GeoXACML policy could also restrict access to non geospatial assets by stating restrictions for access based on the location of the user (or the mobile device used) trying to access the protected assets. Therefore, this standard applies to main stream IT. -For enabling processing of access control decisions based on geometry, Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core inherits by normative reference ISO 19125 which defines a geometry model and functions on geometry instances which enrich the XACML 3.0 specification. - - 2013-11-06 - - OGC Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core - - 13-100 - Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core - - Andreas Matheus + + SensorThings API Part 1: Sensing + 18-088 + The OGC SensorThings API provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the web. At a high level the OGC SensorThings API provides two main functionalities and each function is handled by a part. The two parts are the Sensing part and the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. This document is version 1.1 and it is extending the first version of Sensing part. + + Steve Liang, Tania Khalafbeigi, Hylke van der Schaaf + OGC SensorThings API Part 1: Sensing Version 1.1 + + + + 18-088 + + 2021-08-04 + + + 2014-07-16 + - 13-100 + + This OGC discussion paper provides a proposal for a temporality extension for the WFS +2.0 and FES 2.0 standard. It is based on the work of and experiences made in several +OWS test beds, in particular OWS-7, OWS-8 and OWS-9, Aviation threads and +discussions at the 2011 OGC TC meeting in Brussels, Belgium. It partially replaces and +advances the document “OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via +an OGC WFS 2.0” [4]. + + Web Feature Service (WFS) Temporality Extension + 12-027r3 + OGC Web Feature Service (WFS) Temporality Extension + 12-027r3 + + Timo Thomas - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - Documents of type Best Practices Document - Documents of type Best Practices Document + + Feature Styling IPR + 06-140 + + - Documents of type Best Practices Document - - - OGC Testbed-15: Delta Updates Engineering Report - 19-012r1 + Dr. Markus M + 2007-06-08 + + Feature Styling is based on a distributed computational platform that employs a number +of standard interfaces and encodings to allow for flexible, scalable and interoperable +management of symbology (styles and symbols) in the process of producing maps from +different kinds of data, most important being source GML data. + + + 06-140 + Feature Styling IPR + + - This OGC Testbed 15 Engineering Report (ER) documents the design of a service architecture that allows the delivery of prioritized updates of features to a client, possibly acting in a DDIL (Denied, Degraded, Intermitted or Limited Bandwidth) environment. Two different technical scenarios were investigated and tested: + The OGC service metadata document (sometimes also called capabilities document) is a key part in the service discovery. It describes the service and also the resources that the service expose. Resources are listed in the service metadata document inside a section named as Contents by OWS Common. There are two main limitations to the current Contents section approach: -The enhancement of Web Feature Service (WFS) instances to support updates on features sets. +OWS Common offers flexibility for describing resources and it only proposes a very minimum set of metadata in figure 7 of OGC 06-121r9 called DatasetSummary that need to be sub-classed (i.e. extended) by any specific application. As a result, each standard proposes its own alternative for it. Integrated client developers need to implement them separately. -Utilizing a Web Processing Service (WPS) instance to access features, without the need to modify the downstream data service. - +If the number of resources is very large or the service is highly dynamic, the Contents section can be too long or useless and neither the service nor the client can handle it efficiently. + +This Engineering Report proposes a double solution to the Contents section of the service metadata documents: It proposes ways to encode the Contents section using the OWS Context encoding data types and it introduces the use OpenSearch as a way to request a subset of the resources that the service can provide access to. In that sense, the use of the OGC 10-032r8 OpenSearchGeo can provide the long time needed geospatial and temporal filter capabilities. + 16-052 + Testbed-12 OWS Context / Capabilities Engineering Report + + + 2017-05-22 + Testbed-12 OWS Context / Capabilities Engineering Report - - Benjamin Pross - OGC Testbed-15: Delta Updates Engineering Report - 2019-12-17 - 19-012r1 + 16-052 + Joan Masó + - - + + + 2022-05-06 - - May 2021 OGC API Code Sprint Summary Engineering Report - 2021-11-29 + OGC Disaster Pilot: User Readiness Guide + 21-074 + Samantha Lavender, Andrew Lavender + + + + OGC Disaster Pilot: User Readiness Guide + 21-074 + The OGC Disaster Pilot 2021 initiative brought differing technologies together through multiple participants, allowing the future development of a robust solution with no single-point weaknesses. This Guide supports data providers in preparing and coordinating with others to leverage standards-based cloud computing platforms to support disaster management and response efforts. Geospatial data is acquired from multiple sources, including Earth Observation satellites, and converted to Decision Ready Information and indicators (DRI) from Analysis Ready Data and datasets (ARD) alongside recipes. + + + 19-010r2 + OGC Testbed-15: Styles API Engineering Report + OGC Testbed-15: Styles API Engineering Report + - 21-042 - May 2021 OGC API Code Sprint Summary Engineering Report - The subject of this Engineering Report (ER) is a code sprint that was held from 26 to 28 May 2021 to advance the development of the OGC API - Maps draft standard, OGC API - Tiles draft standard, and the OGC API – Styles draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The code sprint was hosted online. The code sprint was sponsored by Ordnance Survey (OS) and Natural Resources Canada (NRCan). - 21-042 - Gobe Hobona - + + Clemens Portele + + + This document is a proof of concept of a draft specification of the OGC Styles Application Programming Interface (API) that defines a Web API that enables map servers and clients as well as visual style editors to manage and fetch styles. + +Web APIs are software interfaces that use an architectural style that is founded on the technologies of the Web. Styles consist of symbolizing instructions that are applied by a rendering engine on features and/or coverages. + +The Styles API supports several types of consumers, mainly: + +Visual style editors that create, update and delete styles for datasets that are shared by other Web APIs implementing the OGC API - Features - Part 1: Core standard or the draft OGC API - Coverages or draft OGC API - Tiles specifications; + +Web APIs implementing the draft OGC API - Maps specification fetch styles and render spatial data (features or coverages) on the server; + +Map clients that fetch styles and render spatial data (features or coverages) on the client. + +Feature data is either accessed directly or organized into spatial partitions such as a tiled data store (aka vector tiles). + +The Styles API is consistent with the emerging OGC API family of standards. + +The Styles API implements the conceptual model for style encodings and style metadata as documented in chapter 6 of the OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report. + +The model defines three main concepts: + +The style is the main resource. + +Each style is available in one or more stylesheets - the representation of a style in an encoding like OGC SLD 1.0 or Mapbox Style. Clients will use the stylesheet of a style that fits best based on the capabilities of available tools and their preferences. + +For each style there is style metadata available, with general descriptive information about the style, structural information (e.g., layers and attributes), and so forth to allow users to discover and select existing styles for their data. + 19-010r2 + 2019-12-12 + - - Peter Baumann - - 09-146r2 - Coverage Implementation Schema + + + Zarr Storage Specification 2.0 Community Standard - This document specifies a GML coverage structure extending the definition of GML 3.2.1 [07-036] in a compatible way. + + 2022-06-30 + 21-050r1 + Zarr Storage Specification 2.0 Community Standard + 21-050r1 + + This Community Standard refers to the Zarr V2 Specification. The Zarr V2 Specification +is hosted on the Zarr website at https://zarr.readthedocs.io/en/stable/spec/v2.html. The +Zarr V2 Specification is the OGC Community Standard. Everything that follows is a +non-normative, informal description of Zarr usage written for the benefit of the geospatial +community. + Zarr Developers + + + + + OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option + Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option + 06-104r3 + The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. -Main change over GML is the addition of one mandatory component, rangeType, to the Coverage definition of GML 3.2.1 to provide a concise description of the coverage range -value definition. Further, handling of format encodings different from GML are established. +Part 1 “Common Architecture supplies the common feature model for use by applications that will use the Simple Features data stores and access interfaces. -This enhanced coverage type is used, for example, by the Web Coverage Service (WCS) Standard [1] version 2.0 and higher, but is independent from WCS service. This augmented -coverage structure can serve a wide range of coverage application domains and service types, thereby contributing to harmonization and interoperability. - - - 09-146r2 - OGC® Coverage Implementation Schema +Part 2 provides a standard SQL implementation of the abstract model in Part 1. (Note: The OpenGIS® Simple Features Interface Standards for OLE/COM and CORBA are no longer current and are not provided here.) + +The corresponding standard for the Web is the OpenGIS® Web Feature Service Interface Standard http://www.opengeospatial.org/standards/wfs. + + John Herring + + + + 2007-01-29 + 06-104r3 + + + + + + Bastian Baranski + + + WS-Agreement Application Profile for OGC Web Services + 2011-11-24 + This document specifies a) XML schemas for providing functional and non-functional service descriptions of OGC Web Services (OWS), b) an URN namespace for identifying exposed and measurable service properties of OWS and c) a DSL for defining and evaluating service level guarantees. + 11-094 + WS-Agreement Application Profile for OGC Web Services + 11-094 + + + + + + 2010-10-07 + Panagiotis (Peter) A. Vretanos + + Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0 + This document provides revision notes for version 2.0 of the OpenGIS® Implementation Specification Geography Markup Language (GML) simple feature profile. + 10-099r2 + Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0 + + - 2012-05-11 + + + 10-099r2 - - Joan Maso - 21-025 - Cloud Optimized GeoTIFF specification Engineering Report - Cloud Optimized GeoTIFF (COG) is a new approach in using existing standards to accelerate distribution and analysis of 2D regular grid coverage data on the web. COG combines the use of the TIFF format with data structured internally in tiles and low resolutions subfiles (also called overviews). The main subfile is georeferenced using GeoTIFF tags and the lower resolution subfiles inherit the same georeferencing. This organization allows for retrieving only the part of the data needed for presentation or analysis. This capability is possible not only in the file system but also over the web if the HTTP range header is supported by the servers. - -This OGC Testbed 17 Engineering Report (ER) discusses the COG approach, describes how GeoTIFF is used for the lower resolution subfiles, and proposes a different path forward that integrates COG with the OGC Tile Matrix Set Standard (http://docs.opengeospatial.org/is/17-083r2/17-083r2.html). The ER includes a chapter that formalizes the draft COG specification with clear requirements. - -One of the common use cases for COG is the provision of multispectral remote sensing data. The increase in spatial and spectral resolution combined with more accurate sensors that require more than 8 bits per pixel results in big files that can exceed the 4 Gbyte limit of the original TIFF format. Having an OGC standard formally specifying this approach would be useful. Therefore, this ER includes a chapter that formalizes a draft BigTIFF specification, defining clear requirements. + + Thomas Everding, Johannes Echterhoff + + 08-132 + + Event Pattern Markup Language (EML) + + The Event Pattern Markup Language (EML) allows one to describe event patterns for event (stream) processing and analysis. It can be used to build multi stage filters for incoming events but also to derive higher information through combining and correlating multiple events. It can be applied on single events but is focused on handling of continuous event streams. + Event Pattern Markup Language (EML) + 08-132 + 2008-11-05 + + + + + + OWS 2 Common Architecture: WSDL SOAP UDDI + OWS 2 Common Architecture: WSDL SOAP UDDI + 04-060r1 + + + 04-060r1 + Jerome Sonnett + 2005-02-17 + + + + This OGC document reports the work that occurred in the OWS2 Test Bed Common Architecture thread. This thread focused on the use of UDDI/WSDL/SOAP in the OGC Web Services architecture. It also provides guidelines for the use of these technologies. + + + + Alan Leidner, Andrew Hughes, Carsten Roensdorf, Neil Brammall, Liesbeth Rombouts, Joshua Lieberman + + 2024-07-05 + + 23-024 + OGC Model for Underground Data Definition and Integration (MUDDI) Part 1: Conceptual Model + MUDDI stands for “Model for Underground Data Definition and Integration” and is an approach to make sub-surface data Findable, Accessible, Interoperable, and Re-Usable. -The objective is to be able to reference BigTIFF from the GeoTIFF and the COG standards. - OGC Testbed-17: Cloud Optimized GeoTIFF specification Engineering Report - 2022-02-08 - +This document defines a Conceptual Model of classes that allows the integration of datasets from different types of information about the underground space, using different information models. These information models include models about elements such as utility infrastructure, transport infrastructure, soils, ground water, or environmental parameters. The Conceptual Model is a superset of classes representing Real-World Objects that can be found in the Underground. + 23-024 + OGC Model for Underground Data Definition and Integration (MUDDI) Part 1: Conceptual Model + - 21-025 + + + + + R. Martell + 14-000 + Testbed 10 Engineering Report: GML for Aviation Conformance Testing + 2014-07-14 + Testbed 10 Engineering Report: GML for Aviation Conformance Testing + + + + This activity is part of OGC Testbed 10. The aviation thread was focused on developing +and demonstrating the use of the Aeronautical Information Exchange Model (AIXM) and +the Flight Information Exchange Model (FIXM), building on the work accomplished in +prior testbeds to advance the applications of OGC Web Services standards in next generation +air traffic management systems to support European and US aviation modernization +programs +This document summarizes technical work relating to the enhancement of the GML 3.2.1 +conformance test suite in accord with the requirements in the OWS-10 RFQ, Annex B1, +section 6.3.6: “GML for Aviation Compliance Test Suite + GML for Aviation Conformance +Testing ER”. The essential aim is to advance compliance with respect to the use of +GML geometry representations in aviation (AIXM) data. + 14-000 + - - - - + - OGC® IndoorGML - 2014-12-02 + 21-041r2 - IndoorGML - 14-005r3 - This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes. - Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker - - - - 14-005r3 - - - - 99-109r1 - Topic 9 - Accuracy - Cliff Kottman, Arliss Whiteside - - Topic 9 - Accuracy - 1999-03-30 + OGC Conceptual Modeling Discussion Paper + 2022-01-24 + + Sam Meek + OGC Conceptual Modeling Discussion Paper + 21-041r2 + + Historically, conceptual modeling was utilized sporadically within the Open Geospatial Consortium (OGC). Models were used in OGC standards both informatively and normatively to describe the structure of the information within a standard for a particular domain. As independent standards-development organizations, OGC and alliance partners such as ISO / TC211 did not always develop common models. There are several examples of conceptual models in OGC’s Abstract Specifications, many of which have become ISO / TC211 standards since their publication. Outside of Abstract Specifications, there are fewer examples of conceptual models in Implementation Standards. Logical Models and Physical Models tend to be specified more in Implementation Standards. + +The need for conceptual models in Implementation Standards has become apparent since the OGC is moving towards resource based architecture through the development of the OGC Application Programming Interface (API) suite of standards. In the previous ways of working, standards and encodings mapped 1:1, as many OGC standards were based on the Extensible Markup Language (XML) and a standard described a particular set of XML documents to support a domain. The move to OGC API has led towards a separation of an information model represented in a standard from encodings, which is the way that the information models are expressed in a given technology. In other words, the move to OGC API has led to a clearer separation of the logical model from the physical model. + +The utilization of conceptual modeling practices may be employed to manage, track, or govern the use of concepts and terms within different standards. The OGC should adopt conceptual modeling where suitable with a new group to support the working groups with the modeling effort that may otherwise have not been completed because a lack of expertise or value recognition. Taking the concept one step further, Model Driven Architecture (MDA) is a transformation process to create a platform specific model, or implementation from a logical, platform-independent model. This process could be implemented to enable quick production of standards into different target technologies or for the creation of new standards entirely. This paper does not suggest making MDA and associated mandatory for future standards generation. + + + + 04-011r1 + Geolinking Service + + + 2004-05-04 + + A Geolinking Service takes attribute data which refers to spatial features, and joins it to a geospatial dataset, so that it can be mapped by a WMS or used in a GIS. When a Geolinking Service uses data from a GDAS, and serves as a front end to a WMS, it enables real-time mapping of data stored in non-spatial databases. + 04-011r1 + + Geolinking Service + Peter Schut - Topic 9 has been combined into AS Topic 11 - 99-109r1 + + + + 17-032r2 + Testbed-13: Aviation Abstract Quality Model Engineering Report + OGC Testbed-13: Aviation Abstract Quality Model Engineering Report - + + 2018-01-26 + This OGC® Engineering Report (ER) describes an Abstract Quality Model (AQM) for data in the aviation domain. Requirements for data quality in aviation are stringent, as the data is often used for safety critical purposes. The services considered are those that serve aeronautical information, flight information and weather forecasting. The model is built upon recognized standards of the International Organization for Standardization (ISO) with extensions and additions made according to the requirements of the domain. These requirements include an ability for the model to record information about the precision of measurements and an understanding of the timeliness of a piece of data, as information utility degrades with time. The result is an ISO compliant data quality model with the required extensions included. + + 17-032r2 + + Anneley McMillan, Sam Meek + + - - Peter Schut - 05-007 - + + 11-092r2 + OWS-8 Report on Digital NOTAM Event Specification + 11-092r2 + + 2012-04-04 + + + Johannes Echterhoff, Matthes Rieke + OWS-8 Report on Digital NOTAM Event Specification + This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 8 (OWS-8). It describes the results of the conceptual and schematron rule based validation of the Digital NOTAM Event Specification (DNES). Various conceptual aspects were identified which need clarification and/or revision. Schematron rules were developed for a number of the DNES scenarios. This document contains coverage tables which document normative statements from the DNES and indicate which of them can be tested with existing schematron rules. +See: <a href=http://dp.schemas.opengis.net/11-092r2>http://dp.schemas.opengis.net/11-092r2</a> + + - 05-007 + + + 2007-10-05 + + The OpenGIS® Web Processing Service (WPS) Interface Standard provides rules for standardizing how inputs and outputs (requests and responses) for geospatial processing services, such as polygon overlay. The standard also defines how a client can request the execution of a process, and how the output from the process is handled. It defines an interface that facilitates the publishing of geospatial processes and clients’ discovery of and binding to those processes. The data required by the WPS can be delivered across a network or they can be available at the server. + + 05-007r7 + 05-007r7 Web Processing Service + Peter Schut - - - 2005-01-24 + + Web Processing Service - This document is the specification for a Web Processing Service (WPS). -A Web Service Processing Service provides access to calculations or models which operate on spatially referenced data. The data required by the service can be available locally, or delivered across a network using data exchange standards such as Geography Markup Language (GML) or Geolinked Data Access Service (GDAS). - - - Web Map Services - Application Profile for EO Products - 06-093 - - 06-093 - The WMS configuration proposed in this profile is intended to support the interactive visualization and evaluation of Earth Observation (EO) data products. The profile sets out to describe a consistent Web Map Server (WMS) configuration that can be supported by many data providers (satellite operators, data distributors...), most of whom have existing (and relatively complex) facilities for the management of these data. - 2006-10-24 - Thomas H.G. Lankester - - - - - OpenGIS Web Map Services - Application Profile for EO Products + + 05-110 + 05-110 + Feature Portrayal Service + This document specifies the interface to a Feature Portrayal Service (FPS), which applies styles to digital features to produce a map image. The styles applied are identified or specified by the client, and are applied to digital feature data retrieved from a Web Feature Service (WFS) identified by the client. + + + 2006-04-19 + Feature Portrayal Service + + + Arliss Whiteside, Bill Woodward, co-editor + - - Recommended XML Encoding of CRS Definitions - 03-010r7 + + 2012-06-12 - - Arliss Whiteside + This OGC® document specifies the Earth Observation Products Extension Package for ebXML Registry Information Model 3.0, based on the [OGC 10-157r1] Earth Observation Metadata profile of Observations and Measurements. +It enables CSW-ebRIM catalogues to handle a variety of metadata pertaining to earth observation p/roducts as defined in [OGC 10-157r1]. +This proposed application profile document describes model and encodings required to discover, search and present metadata from catalogues of Earth Observation products. The profile presents a minimum specification for catalogue interoperability within the EO domain, with extensions for specific classes of metadata. + + - This OpenGIS Recommendation Paper specifies basic XML encoding of data defining coordinate reference systems and coordinate operations. This encoding is expected to be adapted and used by multiple OGC -Implementation Specifications, by the separate specification of Application Schemas. This document is a Recommendation Paper because the specified encoding is more general -than an OpenGIS Implementation Specification and more specific than the OpenGIS Abstract Specification. - - - 03-010r7 - Recommended XML Encoding of CRS Definitions - 2003-05-21 + Frédéric Houbie; Fabian Skivee + + Cataloguing Earth Observation Products for ebXML Registry Information Model 3.0 based Catalogues + 10-189r2 + 10-189r2 + Cataloguing Earth Observation Products for ebXML Registry Information Model 3.0 based Catalogues + - - The aim of this OGC Engineering Report is to show how to provide access control for OGC Web Services (OWS). In the first part of this document we will briefly introduce the relevant details of XACML 2.0, OGC GeoXACML 1.0 and some related profiles. - OWS-6 GeoXACML Engineering Report - 09-036r2 - 09-036r2 - Jan Herrmann, Andreas Matheus - 2009-07-24 - - - + + 2022-11-10 + + 22-013r3 + Towards a Federated Marine SDI: IHO and OGC standards applied to Marine Protected Area Data Engineering Report + + + Sergio Taleisnik, Terry Idol, Ph.D. + This Engineering Report (ER) summarizes the demonstrations, findings, and recommendations that emerged from the second phase of the OGC Federated Marine Spatial Data Infrastructure (FMSDI) Pilot. The goal of this initiative was to further advance the interoperability and usage of Marine Protected Area (MPA) data through the implementation of the IHO standard S-122 and several OGC API standards. + +This ER describes a solution architecture consisting of a collection of interoperable components developed to demonstrate technologies that helped to achieve the objectives of this Pilot’s phase. This document describes a server built to serve MPA data through an OGC API – Features endpoint and two servers that combined MPA data with additional datasets and served it through both an OGC API – Features and an OGC API — EDR endpoint. This document also describes the three clients built to consume under different scenarios the data offered by the aforementioned servers. Finally, this ER captures lessons learned and recommendations for IHO and OGC API standards, and recommendations for future work. + 22-013r3 - OWS-6 GeoXACML Engineering Report + Towards a Federated Marine SDI: IHO and OGC standards applied to Marine Protected Area Data Engineering Report - - This standard describes a conceptual and logical model for the exchange of groundwater data, as well as a GML/XML encoding with examples. - 16-032r2 - WaterML 2: Part 4 – GroundWaterML 2 (GWML2) - OGC WaterML 2: Part 4 – GroundWaterML 2 (GWML2) - 16-032r2 - - - - - - Boyan Brodaric - - 2017-03-06 - - - - - Scott Fairgrieve - OWS-7 CCSI-SWE Best Practices Engineering Report - 2010-06-30 - - OWS-7 CCSI-SWE Best Practices Engineering Report - 10-073r1 - - This document seeks to define the Best Practices for integrating Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) compliant and potentially other CBRN-based sensors into an OGC Sensor Web Enablement (SWE)-based environment. The document focuses on the practical application of SWE services and encodings for describing and interacting with CCSI sensors and data and draws heavily from and expands upon work performed in the OGC Web Services Phase 6 (OWS-6) testbed to define methodologies for integrating CCSI sensors into a SWE-based environment both now, by building upon the OWS-6 work, and in the future, by defining CCSI profiles of the SWE specifications. - - 10-073r1 - + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - + + 21-070 + OGC Integrated Methane Sensor Web for Emissions Management Best Practice - Part I - Fugitive Emissions Management based on AE + Methane (CH4) is one of the most potent greenhouse gases, and the comparative impact of methane is 25 times greater than CO2 over a 100-year period. Methane is an invisible and odorless gas, and it is very labor intensive and time consuming in order to detect and repair leaks. Regulations play a critical role in methane emissions reduction, and how methane emissions are detected, repaired, and managed is highly dependent on local regulations. This OGC Best Practice document defines a SensorThings API for fugitive methane emissions management. + 2022-07-13 + Steve Liang - - Philippe Duschene, Jerome Sonnet - - 04-050r1 - WMS Change Request: Support for WSDL & SOAP - - This change proposal is an outcome of the Common Architecture thread of the OpenGIS Web Service 2 initiative. The aim is to add support for a standard WSDL description of the WMS interface in version 1.3.1. - WMS Change Request: Support for WSDL & SOAP - - 04-050r1 - 2005-04-22 - - - - Stefano Cavazzi - - 2018-02-22 - + + - - This Open Geospatial Consortium (OGC) Engineering Report (ER) captures the requirements, solutions, and implementation experiences of the Vector Tiling work package in OGC Testbed-13 [Available at: http://www.opengeospatial.org/projects/initiatives/testbed13]. This ER describes the evaluation of existing vector tiling solutions. The evaluation was used to define a conceptual model that integrates elements from different approaches to vector tiling. This is followed by an overview of how the developed implementation integrates vector tiles containing World Geodetic System 1984 (WGS84), European Terrestrial Reference System 1989 (ETRS89) and British National Grid projection data, standards based tile schemas and moving features. Best practice guidelines for the use of Symbology Encoding (SE) and Styled Layer Descriptor (SLD) are also provided ensuring the service is optimized for analysis and low-bandwidth networks. The report concludes with an investigation on how existing OGC services may be extended with the necessary capabilities enabling the full range of geometry types and tiling strategies to support vector tiling. - - Testbed-13: Vector Tiles Engineering Report - 17-041 - 17-041 - OGC Testbed-13: Vector Tiles Engineering Report + + 21-070 + OGC Integrated Methane Sensor Web for Emissions Management Best Practice - Part I - Fugitive Emissions Management based on AE - - - OGC Testbed-19 Agile Reference Architecture Engineering Report - 23-050 - 2024-04-26 - The concepts of agile architecture and reference architecture may not be new ideas in information or geospatial technologies, but what is meant by the term Agile Reference Architecture? - -Agile Reference Architecture is the long-term vision of the complex and changing nature of how problems will be solved in the future within the location-referenced and geospatial realms. This includes consideration of network availability, as containers integrated with Linked Data, and Application Programming Interfaces (APIs) serve data as secure, trusted, and self-describing resources. - -While the Open Geospatial Consortium (OGC) focuses on geospatial information and technologies, that community is also dependent on the overall state of information and communications technology (ICT), including developing cyber, cryptographic, and internet technologies. - -In today’s infrastructures, the collection, exchange, and continuous processing of geospatial resources typically happens at pre-defined network endpoints of a spatial data infrastructure. Each participating operator hosts some capability at a network endpoint. Whereas some network operator endpoints may provide data access, other endpoints provide processing functionality and other endpoints may support the uploading of capabilities. In other words, such an infrastructure is not agile in the sense that it cannot adapt by itself to meet the needs of the moment. One of the biggest challenges resulting from the static characteristics is ensuring effective and efficient operations of the overall system and at the same time maintaining trust and provenance. - -This OGC Testbed 19 Engineering Report (ER) outlines novel concepts for establishing a federated agile infrastructure of collaborative trusted systems (FACTS) that is capable of acting autonomously to ensure fit-for-purpose cooperation across the entire system. One of the key objectives is to not create a new data product, but instead a collaborative object is offered leveraging FACTS that allows for obtaining the data product via well-defined interfaces and functions provided by the collaborative object. - -Trust and assurance are two key aspects when operating a network of collaborative objects leveraging STANAG 4774/4778. STANAG 4774 outlines the metadata syntax required for a confidentiality label to better facilitate and protect sensitive information sharing. In addition, STANAG 4778 defines how a confidentiality label is bound to the data throughout its lifecycle and between the sharing parties.The agile aspect is achieved by the object’s ability to activate, deactivate, and order well-defined capabilities from other objects. These capabilities are encapsulated in building blocks. Each building block is well defined in terms of accessibility, functionality, and ordering options. This allows building blocks to roam around collaborative objects as needed to ensure a well-balanced network load and suitable processing power of individual nodes from the network. - -Equally trusted partners in the infrastructure participate in FACTS. They can collect data from other partners and create derived products via collaborative objects. The sharing of data products is only possible directly, meaning direct communication with data consumer and it is only possible via the objects. This guarantees that fundamental trust operations are applied to the data and provenance records are produced before the data product is made available to others. The use of Blockchain technology and Smart contracts is one example of how this fundamental behavior can be planted into collaborative objects. As in trusted networks that are using Evaluation Assurance Level (EAL) approved hardware and software components, the objects will have to undergo a similar assurance process. - -For ensuring the acceptance and interoperability of an agile reference architecture, built on top of FACTS with collaborative objects and building blocks, standardization is a key aspect. In particular, the core (fundamental) requirements for FACTS as well as the interfaces and capabilities of the collaborative objects and pluggable building blocks should be standardized. The OGC provides a consensus based collaborative standardization environment fits these requirements very well. - - 23-050 + - OGC Testbed-19 Agile Reference Architecture Engineering Report - - Lucio Colaiacomo - - - + 15-043r3 + Timeseries Profile of Observations and Measurements + James Tomkins, Dominic Lowe - The OpenGIS® Styled Layer Descriptor (SLD) Profile of the OpenGIS® Web Map Service (WMS) Encoding Standard [http://www.opengeospatial.org/standards/wms ] defines an encoding that extends the WMS standard to allow user-defined symbolization and coloring of geographic feature[http://www.opengeospatial.org/ogc/glossary/f ] and coverage[http://www.opengeospatial.org/ogc/glossary/c ] data. - -SLD addresses the need for users and software to be able to control the visual portrayal of the geospatial data. The ability to define styling rules requires a styling language that the client and server can both understand. The OpenGIS® Symbology Encoding Standard (SE) [http://www.opengeospatial.org/standards/symbol] provides this language, while the SLD profile of WMS enables application of SE to WMS layers using extensions of WMS operations. Additionally, SLD defines an operation for standardized access to legend symbols. - - - OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification - Styled Layer Descriptor Profile of the Web Map Service Implementation Specification - 05-078r4 - 05-078r4 - Markus Lupp - - - - - 2007-08-14 - - - - James Tomkins, Dominic Lowe - - TimeseriesML 1.0 defines an XML encoding that implements the OGC Timeseries Profile of Observations and Measurements [OGC 15-043r3], with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of data exchange requirements. - TimeseriesML 1.0 – XML Encoding of the Timeseries Profile of Observations and Measurements - 15-042r3 - TimeseriesML 1.0 – XML Encoding of the Timeseries Profile of Observations and Measurements - 15-042r3 - 2016-09-09 - - - + Timeseries Profile of Observations and Measurements + 2016-09-09 + The OGC Timeseries Profile of Observations and Measurements is a conceptual model for the representation of observations data as timeseries, with the intent of enabling the exchange of such data sets across information systems. This standard does not define an encoding for the conceptual model; however there is an accompanying OGC Standard which defines an XML encoding (OGC TimeseriesML 1.0 - XML Encoding of the Timeseries Profile of Observations and Measurements). Other encodings may be developed in future. + + 15-043r3 - - OWS-6 SensorML Profile for Discovery Engineering Report - 09-033 - - This document defines a basic SensorML profile for discovery purposes. Besides a minimum set of metadata also the structure of according SensorML documents is defined in order to ensure a consistent metadata description. This goal is achieved by a set of Schematron rules that can be used to validate if a given SensorML document complies with the profile described in this engineering report. - + + + + Wenli Yang, Arliss Whiteside + 05-017 - - 09-033 + 05-017 + Web Image Classification Service (WICS) - - Simon Jirka, Arne Bröring - OWS-6 SensorML Profile for Discovery Engineering Report - 2009-07-29 - - - CT Definition Data for Coordinate Reference - Arliss Whiteside - 01-014r5 - CT Definition Data for Coordinate Reference - 01-014r5 - - - - - 2001-10-10 - A data model for coordinate reference systems to provide a common framework across all OGC specifications. - + The Web Image Classification Service (WICS) supports classification of digital images. A digital image is composed of pixel values organized into one or more two-dimensional arrays. The two dimensions of an image represent two axes in space based on a spatial coordinate reference system. The dimensions of the different 2-D arrays comprising an image must be the same and represent exactly the same spatial locations. + + 2005-02-10 + Web Image Classification Service (WICS) - - OGC Earth Observation Applications Pilot: European Union Satellite Centre Engineering Report - 20-038 - 2020-10-22 - This Engineering Report (ER) describes the achievements of the European Union Satellite Centre (SatCen) as an application provider in the OGC Earth Observation Applications Pilot and the lessons learned from the project. + + + This document provides brief and consistent summaries of several OGC Web Service interface specifications that serve data. + + + 2007-11-14 + + 07-095r2 + Web Services Summaries + Arliss Whiteside + OGC Web Services Summaries + 07-095r2 + + + + OGC document register with annotations and links + loaded from https://portal.opengeospatial.org/public_ogc/api/docs.php?CITE=1 + + + OGC Documents + + + This document is a deliverable of the OGC Testbed 11 . It describes the results of developing a tool to automatically derive Schematron code from SBVR constraints. It also documents a vocabulary with a profile of core geospatial terms and concepts, which can be used to express geospatial constraints in business rules. + + + 15-024r2 + Testbed 11 Aviation - Guidance on Using Semantics of Business Vocabulary and Business Rules (SBVR) Engineering Report + 2015-08-19 - OGC Earth Observation Applications Pilot: European Union Satellite Centre Engineering Report - - - 20-038 - Omar Barrilero, Adrian Luna + 15-024r2 + + + OGC® Testbed 11 Aviation - Guidance on Using Semantics of Business Vocabulary and Business Rules (SBVR) Engineering Report + Johannes Echterhoff - - - Topic 1 - Spatial schema - This document is the ISO 19107:2019 Standard and specifies conceptual schemas for describing the spatial characteristics of geographic entities, and a set of spatial operations consistent with these schemas. It treats vector geometry and topology. - Topic 01 - Spatial schema - 17-087r13 + + + + 12-168r6 + 12-168r6 + Catalogue Services 3.0 - General Model + Douglas Nebert, Uwe Voges, Lorenzo Bigagli + + 2016-06-10 + OGC® Catalogue Services 3.0 - General Model - John R. Herring - - 17-087r13 - - - 2020-08-28 - - - 15-012r2 - - OGC GeoPackage Plugfest Discussion Paper - This OGC discussion paper presents the results of the GeoPackage Plugfest. In this -initiative, participants had the opportunity to evaluate the compliance and interoperability -of software that produces and consumes GeoPackages containing tiled raster data. - - - GeoPackage Plugfest Discussion Paper - 15-012r2 + OGC® Catalogue Services support the ability to publish and search collections of +descriptive information (metadata records) for geospatial data, services, and related +information. Metadata in catalogues represent resource characteristics that can be queried +and presented for evaluation and further processing by both humans and software. +Catalogue services are required to support the discovery and binding to registered +information resources within an information community. +This part of the Catalogue Services standard describes the common architecture for OGC +Catalogue Services. This document abstractly specifies the interfaces between clients and +catalogue services, through the presentation of abstract models. This common +architecture is Distributed Computing Platform neutral and uses UML notation. Separate +(Part) documents specify the protocol bindings for these Catalogue services, which build +upon this document, for the HTTP (or CSW) and OpenSearch protocol bindings. +An Abstract Conformance Test Suite is not included in this document. Such Suites shall +be developed by protocol bindings and Application Profiles (see 8.5, ISO/IEC TR 10000- +2:1998) that realize the conformance classes listed herein. An application profile +consists of a set of metadata elements, policies, and guidelines defined for a particular +application1. +OGC document number 14-014r3 – HTTP Protocol Binding – Abstract Test Suite is +available to address conformance with the provisions of OGC document number 12- +176r7 – HTTP Protocol Binding. All annexes to this document are informative. + + + 21-032 + OGC Testbed 17: COG/Zarr Evaluation Engineering Report + The subject of this Engineering Report (ER) is the evaluation of Cloud Optimized GeoTIFF (COG) and Zarr data container implementations. The ER aims to: + + Describe the use cases adopted for the evaluation (with existing implementation and with Testbed-17 implementation); + Identify the opportunity of proposing that COG and Zarr become OGC standards; + Describe all components developed during the Testbed; and + Provide an executive summary and a description of recommended future work items. + + Giovanni Giacco, Mauro Manente, Pedro Gonçalves, Martin Desruisseaux, Even Rouault + + 21-032 + + OGC Testbed 17: COG/Zarr Evaluation Engineering Report + 2022-01-24 - 2015-08-19 - Jeff Yutzler + - - 16-003r2 - Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values - - - This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids key words. - - 16-003r2 - Carl Reed - - Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values + + 11-064r3 + This OGC® document specifies improvements to the processing of information represented in or referenced from an application schema in UML to create derived, implementation level resources, in particular: +• XML Schema documents to represent types and their properties +• Schematron schema documents to represent constraints +• XSLT-Stylesheets to create KML instances of features +The documented improvements have been specified, implemented in the ShapeChange tool and tested in the context of schemas developed as part of the NGA's Topographic Data Store (TDS) schemas. +The work is a continuation of the work documented in OGC® document 10-088r2, the OWS-7 Schema Automation Engineering Report. + + + - 2017-02-23 + OWS-8 CCI Schema Automation Engineering Report + 11-064r3 + 2011-11-23 + OWS-8 CCI Schema Automation Engineering Report + + + Clemens Portele, Reinhard Erstling - + + 02-026r4 + The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances. + Mike Botts + Sensor Model Language (SensorML) for In-situ and Remote Sensors + 02-026r4 + Sensor Model Language (SensorML) for In-situ and Remote Sensors - 12-084r2 - OWS Context Atom Encoding Standard - OGC OWS Context Atom Encoding Standard - - This standard describes the Atom encoding of the OWC Context conceptual model. The goal of this standard is to provide a definition of how to encode a context document, which can be extended to allow a context referencing a fully configured service set to be defined and consistently interpreted by clients. - - Roger Brackin, Pedro Gonçalves - 12-084r2 - 2014-01-14 - - - + 2002-12-20 + + + + - - 21-053r1 - Topic 23 - GeoPackage Conceptual and Logical Model + + + + Leonard Daly, Rollin Phillips + Interoperable Simulation and Gaming Sprint Year 2 Engineering Report + + 21-058 + + 21-058 + Interoperable Simulation and Gaming Sprint Year 2 Engineering Report - Jeff Yutzler - 21-053r1 - This document presents the conceptual and logical models for version 1.x of the OGC GeoPackage Standard. The intent is that these models can be used to implement the GeoPackage standard using technology other than a SQLite database. - Topic 23 - GeoPackage Conceptual and Logical Model + 2021-11-08 - - - - 2023-06-29 - + The OGC Interoperable Simulation and Gaming Year 2 Sprint advanced the use of relevant OGC and Khronos Group [1] standards in the modeling, simulation, and training communities through capability development, compatibility testing, and gap analysis. Of particular interest was the use of glTF models, game engines, and 3rd-party mobile device libraries for the display and interaction with data using OGC APIs. - - 09-037r1 - OWS-6 UTDS-CityGML Implementation Profile + + 16-037 + Testbed-12 GeoPackage US Topo Engineering Report + This OGC Engineering Report documents the outcome of the US Topo experiment. The focus of the US Topo experiment was to generate GeoPackages by combining USGS Topo Map Vector Data Products [1]; and the Topo TNM Style Template [2]. The output GeoPackages will contain both features and instructions for styling these features as well as orthoimagery, shaded relief raster tilesets, national wetlands raster tilesets and elevation data derived from USGS provide 1/9 arc second elevation imagery. The process used to generate the GeoPackage is explained. Problems and obstacles encountered decoding the source product and styles and converting these artifacts to a GeoPackage are explained with recommendations for improvements. Additionally, the experience applying the generated GeoPackage in two use cases proposed for this testbed will be evaluated. The introduction of symbolization for vector features will be articulated as a proposed extension for GeoPackage. Any issues related to encoding the TNM style template using the extension are documented. + + Testbed-12 GeoPackage US Topo Engineering Report + + + Robert Cass + 16-037 - - This OGC document specifies a CityGML-based application schema for a subset of an Urban Topographic Data Store (UTDS) as specified by the US National Geospatial-Intelligence Agency (NGA). -The particular focus of this implementation profile was to test the applicability of CityGML to UTDS data. -This document specifies the implementation profile as well as the findings. - + 2017-05-12 - OWS-6 UTDS-CityGML Implementation Profile - - Clemens Portele - 2009-07-20 - 09-037r1 - - - - Claus Nagel, Thomas Becker, Robert Kaden, Ki-Joune Li, Jiyeong Lee, Thomas H. Kolbe + + OGC Cloud Optimized GeoTIFF Standard + 21-026 + 2023-07-14 + 21-026 + - Requirements and Space-Event Modeling for Indoor Navigation - 10-191r1 - + OGC Cloud Optimized GeoTIFF Standard - - 10-191r1 - - Requirements and Space-Event Modeling for Indoor Navigation - 2010-12-11 - This OpenGIS® Discussion Paper presents a Multilayered Space-Event Model for indoor navigation which simultaneously addresses route planning, multiple localization methods, navigation contexts, and different locomotion types. The paper contains the corresponding data models as well as their encoding in GML 3.1.1. + + The Cloud Optimized GeoTIFF (COG) relies on two characteristics of the TIFF v6 format (tiles and reduced resolution subfiles), GeoTIFF keys for georeference, and the HTTP range, which allows for efficient downloading of parts of imagery and grid coverage data on the web and to make fast data visualization of TIFF or BigTIFF files and fast geospatial processing workflows possible. COG-aware applications can download only the information they need to visualize or process the data on the web. Numerous remote sensing datasets are available in cloud storage facilities that can benefit from optimized visualization and processing. This standard formalizes the requirements for a TIFF file to become a COG file and for the HTTP server to make COG files available in a fast fashion on the web. + +The key work for crafting this OGC Standard was undertaken in the Open-Earth-Monitor Cyberinfrastructure (OEMC) project, which received funding from the European Union’s Horizon Europe research and innovation program under grant agreement number 101059548 and in the All Data 4 Green Deal - An Integrated, FAIR Approach for the Common European Data Space (AD4GD) project, which received funding from the European Union’s Horizon Europe research and innovation program under grant agreement number 101061001. + + + Joan Maso - - - - Corrigendum 1 for OGC Web Services Common Standard v2.0.0 - Multilingual - - Jim Greenwood - 2011-10-18 - 11-157 - Corrigendum 1 for OGC Web Services Common Standard v2.0.0 - Multilingual - This document being corrected specifies many of the aspects that are, or should be, common to all or multiple OWS interface Implementation Specifications. The Common Implementation Specification aspects specified by this document currently include: -a) Operation request and response contents, most partial -b) Parameters and data structures included in operation requests and responses c) XML and KVP encoding of operation requests and responses - 11-157 - + + + Markus Lupp + 05-078r4 + Styled Layer Descriptor Profile of the Web Map Service Implementation Specification + OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification + + 2007-08-14 + 05-078r4 + + The OpenGIS® Styled Layer Descriptor (SLD) Profile of the OpenGIS® Web Map Service (WMS) Encoding Standard [http://www.opengeospatial.org/standards/wms ] defines an encoding that extends the WMS standard to allow user-defined symbolization and coloring of geographic feature[http://www.opengeospatial.org/ogc/glossary/f ] and coverage[http://www.opengeospatial.org/ogc/glossary/c ] data. + +SLD addresses the need for users and software to be able to control the visual portrayal of the geospatial data. The ability to define styling rules requires a styling language that the client and server can both understand. The OpenGIS® Symbology Encoding Standard (SE) [http://www.opengeospatial.org/standards/symbol] provides this language, while the SLD profile of WMS enables application of SE to WMS layers using extensions of WMS operations. Additionally, SLD defines an operation for standardized access to legend symbols. + + + - + + - 17-079r1 - 2019-01-08 - The OGC SensorThings API [OGC 15-078r6] provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the Web. At a high level, the OGC SensorThings API provides two main functions and each function is handled by the Sensing part or the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. The Tasking part provides a standard way for parameterizing - also called tasking - of taskable IoT devices, such as individual sensors and actuators, composite consumer / commercial / industrial / smart cities in-situ platforms, mobile and wearable devices, or even unmanned systems platforms such as drones, satellites, connected and autonomous vehicles, etc. This document specifies core of the SensorThings Tasking part. - - OGC SensorThings API Part 2 – Tasking Core + GML 3.1.1 common CRSs profile + 05-095r1 + This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding definitions of commonly-used Coordinate Reference Systems (CRSs) plus related coordinate Conversions. + + Arliss Whiteside + 2006-07-18 + GML 3.1.1 common CRSs profile + 05-095r1 + - - 17-079r1 - SensorThings API Part 2 – Tasking Core - - Steve Liang, Tania Khalafbeigi - - - + + 12-111r1 + Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data + + 2014-04-14 + + Marie-Françoise Voidrot-Martinez, Chris Little, Jürgen Seib, Roy Ladner, Adrian Custer, Jeff de La B + + 12-111r1 - - This document describes the proposed system design for the OGC Style Management Service (SMS). -The SMS must manage distinct objects that represent styles and symbols and provide the means to discover, query, insert, update, and delete these objects. -Styles provide the mapping from feature types and feature properties and constraints to parameterized Symbols used in drawing maps. Symbols are bundles of predefined graphical parameters and predefined fixed graphics. - - Style Management Services for Emergency Mapping Symbology + + OGC Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data + This document proposes a set of best practices and guidelines for implementing and using the Open Geospatial Consortium (OGC) Web Map Service (WMS) to serve maps which are time-dependent or elevation-dependent. In particular, clarifications and restrictions on the use of WMS are defined to allow unambiguous and safe interoperability between clients and servers, in the context of expert meteorological and oceanographic usage and non-expert usage in other communities. This Best Practice document applies specifically to WMS version 1.3, but many of the concepts and recommendations will be applicable to other versions of WMS or to other OGC services, such as the Web Coverage Service. - - Bill Lalonde - 04-040 - 04-040 - Style Management Services for Emergency Mapping Symbology - 2005-02-17 - - - Topic 21 - Discrete Global Grid Systems Abstract Specification - - - Topic 21 - Discrete Global Grid Systems Abstract Specification - 15-104r5 + + This document characterizes the performance and scalability of OGC data services in the Cloud. Three use cases highlighting different geo-processing aspects of OGC data services have been developed, implemented, and benchmarked. Each use case is presented in a separate section of this document with performance results and discussions. + + 2014-10-14 + + + + Testbed 10 Performance of OGC® Services in the Cloud: The WMS, WMTS, and WPS cases + 14-028r1 + Testbed 10 Performance of OGC® Services in the Cloud: The WMS, WMTS, and WPS cases + Edric Keighan, Benjamin Pross, Hervé Caumont + + + 14-028r1 + + + Ordering Services for Earth Observation Products + 06-141r2 + Ordering Services for Earth Observation Products + + 2007-08-15 + 06-141r2 + + This best practices document describes a profile to order Earth Observation data products. This document expands on the work presented in Best Practices for Earth Observation Products OGC-05-057r4, separating the order services from the catalogue services which are now presented in 06-079. The final goal being to agree to a coherent set of interfaces for ordering of EO products to support access to data from heterogeneous systems dealing with derived data products from satellite based measurements of the earth's surface and environment. + - Matthew Purss + Daniele Marchionni + + + + 07-099r1 + 07-099r1 + GeoXACML Implementation Specification - Extension B (GML3) Encoding + Andreas Matheus + This specification is a normative extension to the GeoXACML core Implementation Specification. It defines the GML3 encoding for geometries. + + GeoXACML Implementation Specification - Extension B (GML3) Encoding + 2008-02-23 - This document specifies the core Abstract Specification and extension mechanisms for Discrete Global Grid Systems (DGGS). A DGGS is a spatial reference system that uses a hierarchical tessellation of cells to partition and address the globe. DGGS are characterized by the properties of their cell structure, geo-encoding, quantization strategy and associated mathematical functions.The OGC DGGS Abstract Specification supports the specification of standardized DGGS infrastructures that enable the integrated analysis of very large, multi-source, multi-resolution, multi-dimensional, distributed geospatial data. Interoperability between OGC DGGS implementations is anticipated through implementation standards, and extension interface encodings of OGC Web Services. - 2017-08-01 - 15-104r5 + + + + - - 1999-03-30 + + Testbed-12 Aviation Architecture Engineering Report + + Charles Chen + + 2017-06-15 + Testbed-12 Aviation Architecture Engineering Report + 16-018 + This Open Geospatial Consortium (OGC)® Engineering Report (ER) describes the architecture implemented in the OGC Testbed 12 Aviation thread. This report provides an overview of the technical architecture for the interoperable exchange of flight and aeronautical information using OGC services. The aviation architecture consists of multiple components developed by the Aviation thread, as well as specialized engineering reports per each work area. This report will provide an introduction to each work area and contain references to applicable reports. This report also describes the Aviation thread demonstration scenarios, outcomes, and benefits. + + 16-018 - - 99-104 - This Topic Volume provides essential and abstract models for technology that is used widely across the GIS landscape. Its first heavy use is expected to occur in support of Coverage specifications (see Topic 6, The Coverage Type). - 99-104 - Topic 04 - Stored Functions and Interpolation - Cliff Kottman - Topic 4 - Stored Functions and Interpolation - - - + - - 11-085r1 - OWS-8 Bulk Geodata Transfer Using GML Engineering Report - 2011-11-07 - Panagiotis (Peter) A. Vretanos - - - + + 2020-10-26 + + 20-045 + OGC Earth Observation Applications Pilot: CRIM Engineering Report - - 11-085r1 - This document describes the work done during the OWS-8 test bed investigating methods and apparatus for distributing individual geospatial data sets and/or collections of data sets in a consistent manner between machines that may or may not be connected via a network. The investigation focuses on the initialization of a target WFS, from a source WFS, for the purpose of GeoSynchronization. Data, schema, metadata and/or topology are exported from a source WFS, transferred to a target WFS (either electronically or physically via some media) and then imported into the target WFS. From that point on, the two WFS's are maintained in synchrony using a Geosynchronization Service (see OGC 10-069r2). - OWS-8 Bulk Geodata Transfer Using GML Engineering Report + + This engineering report documents experiments conducted by CRIM in OGC’s Earth Observation Applications Pilot project, sponsored by the European Space Agency (ESA) and Natural Resources Canada (NRCan), with support from Telespazio VEGA UK. Remote sensing, machine learning and climate informatics applications were reused, adapted and matured in a common architecture. These applications were deployed in a number of interoperable data and processing platforms hosted in three Canadian provinces, in Europe and in the United States. + + OGC Earth Observation Applications Pilot: CRIM Engineering Report + 20-045 + + Tom Landry - - 18-058r1 - OGC API - Features - Part 2: Coordinate Reference Systems by Reference corrigendum - 2022-05-11 - Clemens Portele, Panagiotis (Peter) A. Vretanos - OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks. - -OGC API Features provides API building blocks to create, modify and query features on the Web. OGC API Features is comprised of multiple parts, each of them is a separate standard. + + Arliss Whiteside + + 06-023r1 + Definition identifier URNs in OGC namespace + 06-023r1 + + + + 2006-08-08 + + *** Corrigendum - updated 2006-08-08 *** -This part extends the core capabilities specified in Part 1: Core with the ability to use coordinate reference system identifiers other than the defaults defined in the core. +This revised version of this document adds additional allowed authority and objectType values, plus specifies URNs for data types, as proposed in change requests OGC 05-091r2 and 05-060. In addition, corrections have been made to the XML documents listed in Annex A. The changes made in this version are tracked in the Microsoft Word (.doc) format of this document.<br/><br/>This Best Practices Paper specifies Universal Resource Names (URNs) in the ogc URN namespace to be used for identifying definitions. This document specifies the formats used by these URNs, plus a set of specific URNs for specific definitions. These definitions should be used wherever applicable by implementations of various OGC Implementation Specifications, including GML, WMS, WFS, and WCS. + Definition identifier URNs in OGC namespace + + + 20-091 + OGC API – Common and OGC API – Features Sprint 2020: Summary Engineering Report + + OGC API – Common and OGC API – Features Sprint 2020: Summary Engineering Report + Gobe Hobona - OGC API - Features - Part 2: Coordinate Reference Systems by Reference corrigendum - 18-058r1 - - + + 20-091 - - - - OGC Testbed-15: Portrayal Summary ER - - This OGC Engineering Report provides an executive summary of the Open Portrayal Framework (OPF) Thread in OGC Testbed-15. The work in this testbed occurred between April and November 2019. Full details of the requirements, high-level architecture, and solutions are provided in the following Engineering Reports: - -OGC Testbed-15: Styles API Draft Specification Engineering Report - -OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report - -OGC Testbed-15: Maps and Tiles API Draft Specification Engineering Report - -OGC Testbed-15: Images and Change Sets Draft Specification Engineering Report - -OGC Testbed-15: Open Portrayal Framework Engineering Report - Martin Klopfer - OGC Testbed-15: Portrayal Summary ER - 19-019 + 2021-02-23 + The subject of this Engineering Report (ER) is a code sprint that was held from 29 to 30 September 2020 to advance the development of the OGC API - Common - Part 2: Geospatial Data draft standard and the OGC API – Features – Part 4: Simple Transactions draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The code sprint was hosted online. The event was sponsored by Ordnance Survey (OS). + - 19-019 + + + 22-040 + Hydrologic Modeling and River Corridor Applications of HY_Features Concepts + Hydrologic Modeling and River Corridor Applications of HY_Features Concepts + + Hydrologic geospatial data products contain geometries that represent features such as river segments and incremental catchments. The combination of these provides a 2D (XY) geospatial fabric (hydrofabic) that discretizes the landscape and flow network into hydrologically relevant features at a defined level of scale, resolution, or organization. Hydrofabrics have been created at the national and continental scale in many parts of the world. This engineering report presents progress on formalizing a hydrofabric for drainage basins that adheres to HY_Features concepts with a focus on the use of the concepts in modeling hydrologic processes. Furthermore, this report documents efforts to integrate river corridor data with the traditionally 2D hydrofabric representations. River corridors include the channel and adjacent land required to maintain or restore a dynamic geomorphic equilibrium. + David Blodgett, J. Michael Johnson + 2023-03-06 - 2020-02-07 + + 22-040 - - - 09-146r1 + + Corrigendum 2 for the OGC Standard Web Coverage Service 1.1 + 07-066r5 + This document provides the details of a corrigendum to an OpenGIS Implementation Standard and does not modify the base standard. The OGC Standard that this document provides revision notes for is Web Coverage Service Standard, Version 1.1 Corrigendum 2 [OGC 07-067r5]. + + Arliss Whiteside + + 2008-04-29 + - OGC® GML Application Schema - Coverages - Peter Baumann - 09-146r1 - GML Application Schema - Coverages - This document specifies the GML coverage structure to be used by OGC standards. + Corrigendum 2 for the OGC Standard Web Coverage Service 1.1 + 07-066r5 - 2010-10-27 - - - - 2001-06-08 - + + Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW + 05-025r3 + + 05-025r3 + 2006-10-24 + + Richard Martell + OpenGIS Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW - 01-111 - Topic 11 - Metadata + - ISO - 01-111 - - - ISO 19115 was adopted as a replacement for OGC Abstract Specification Topics 9 and 11. In June 2001, a motion to include material in addition to ISO 19115 was adopted as document 01-111 Metadata AS. The approved addition to document 01-111 is contained in document 01-053r1, which normatively references parts of the old AS Topic 9, document 99-109r1. FGDC in conjunction with ANSI INCITS L1 are planning the migration of the FGDC Content Standard for Geospatial Metadata to be a profile of ISO 19115 - - Topic 11 - Metadata - - - The OpenGIS® Web Processing Service (WPS) Interface Standard provides rules for standardizing how inputs and outputs (requests and responses) for geospatial processing services, such as polygon overlay. The standard also defines how a client can request the execution of a process, and how the output from the process is handled. It defines an interface that facilitates the publishing of geospatial processes and clients’ discovery of and binding to those processes. The data required by the WPS can be delivered across a network or they can be available at the server. - Web Processing Service - 05-007r7 - Peter Schut - - - - - - 05-007r7 - 2007-10-05 - Web Processing Service + The OGC Catalogue Services 2.0 specification (OGC 04-021r3) establishes a general framework for implementing catalogue services that can be applied to meet the needs of stakeholders in a wide variety of domains. This application profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0 specification; it qualifies as a Class 2 profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards. - - The subject of this Engineering Report (ER) is a code sprint that was held from November 29th to December 1st, 2022 to advance OGC API Standards that relate to web mapping, and others that relate to styling and symbology encoding standards. The code sprint was hosted by the Open Geospatial Consortium (OGC) and EuroGeographics. The code sprint was sponsored by Ordnance Survey (OS), and was held as a hybrid event with the face-to-face element hosted at the Mundo Madou centre in Brussels, Belgium. - Gobe Hobona, Joana Simoes - 2022 Web Mapping Code Sprint Summary Engineering Report - 22-054r1 - - - - 2023-06-16 - + + + Jeff Lansing + Coverage Portrayal Service + 02-019r1 + + + 2002-02-28 + 02-019r1 + The Coverage Portrayal Service (CPS) IPR proposes a standard interface for producing visual pictures from coverage data. + Coverage Portrayal Service - 2022 Web Mapping Code Sprint Summary Engineering Report - - 22-054r1 + + - - CDB Vector Data in GeoPackage Interoperability Experiment - 19-007 - This OGC Engineering Report (ER) documents the results of the CDB Vector Data in GeoPackage Interoperability Experiment (IE). The participants in this IE tested transforming CDB Shapefile vector data into one or more GeoPackage(s) and storing the result in a CDB data store. GeoPackage Version 1.2 and CDB Version 1.1 and related Best Practices were the standards baseline used for this experiment. The IE builds on the work described in the OGC CDB, Leveraging GeoPackage Discussion Paper. - -A primary objective of this IE was to agree and document possible change requests and/or best practices for storing vector data in a CDB data using encodings and/or containers other than Shapefiles. These suggested changes requests and/or best/practices will be used as the basis for CDB Standards Working Group (SWG) discussions related to possible revisions to the CDB standard. - - - 2019-08-20 - Carl Reed + + Rob Atkinson + + An authority for place names. Returns their associated geometries + Gazetteer + 01-036 - OGC CDB Vector Data in GeoPackage Interoperability Experiment + + 2001-03-15 - - 19-007 + + 01-036 + Gazetteer + + + + This OGC discussion paper presents an approach to harmonize the OGC GeoPackage and OWS Context standards through a set of extensions. GeoPackage is an open, standards-based, platform-independent, portable, self-describing, compact format for storing and transferring geospatial data and information as part of an SQLite database. OWS Context is an open format linking geospatial web services and information. A draft standard has been produced and this Discussion Paper is designed to be a companion to that draft standard to assist in discussion. The draft standard contains extensions to both GeoPackage and OWS Context. + +This document is the work of collaboration between the GeoPackage and OWS Context Standards Working Groups (SWGs). + + + + 18-037r1 + 18-037r1 + GeoPackage / OWS Context Harmonization Discussion Paper + 2018-10-29 + GeoPackage / OWS Context Harmonization Discussion Paper + + Jeff Yutzler + + + + + - - + + 20-035 + 20-035 + Earth Observation Application Packages with Jupyter Notebooks + - This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. -InfraGML is published as a multi-part standard. This Part 1 addresses the LandFeature Requirements Class from LandInfra. - Paul Scarponcini - OGC InfraGML 1.0: Part 1 – LandInfra Land Features - Encoding Standard - 16-101r2 - InfraGML 1.0: Part 1 – LandInfra Land Features - Encoding Standard - 2017-08-16 - 16-101r2 - - + 2021-01-13 + + + Christophe Noël + OGC Testbed-16: Earth Observation Application Packages with Jupyter Notebooks + This OGC Testbed-16 Engineering Report (ER) describes all results and experiences from the “Earth Observation Application Packages with Jupyter Notebook” thread of OGC Testbed-16. The aim of this thread was to extend the Earth Observation Applications architecture developed in OGC Testbeds 13, 14, and 15 with support for shared and remotely executed Jupyter Notebooks. The Notebooks make use of the Data Access and Processing API (DAPA) developed in the Testbed-16 Data Access and Processing API (DAPA) for Geospatial Data task and tested in joint Technology Integration Experiments. - - 2019-01-20 - - + - CDB, Leveraging GeoPackage Discussion Paper - 18-077r2 - - - - Jay Freeman, Kevin Bentley, Ronald Moore, Samuel Chambers, Glen Quesenberry - OGC CDB, Leveraging GeoPackage Discussion Paper - This paper offers the results of research, design, and prototype efforts to present the OGC standards working group an approach to creating “GeoCDB”—a technology mashing of GeoPackage and OGC CDB—as a deterministic repository of easily read data geospatial datasets suitable for storage, runtime access, and dissemination for live, virtual, constructive, gaming, and mission command (MC) systems. - 18-077r2 - - - - - OGC-NA Name type specification - documents - 09-047r3 - Simon Cox + Sara Saeedi + 2018-01-11 + + 17-042 + Testbed-13: CDB Engineering Report - This document specifies a rule for constructing OGC names that may be used for identifying documents and elements within a document. - 09-047r3 - 2011-03-01 - - OGC-NA Name type specification - documents - - - - OGC Testbed-13: Aviation Abstract Quality Model Engineering Report - 17-032r2 - Testbed-13: Aviation Abstract Quality Model Engineering Report - This OGC® Engineering Report (ER) describes an Abstract Quality Model (AQM) for data in the aviation domain. Requirements for data quality in aviation are stringent, as the data is often used for safety critical purposes. The services considered are those that serve aeronautical information, flight information and weather forecasting. The model is built upon recognized standards of the International Organization for Standardization (ISO) with extensions and additions made according to the requirements of the domain. These requirements include an ability for the model to record information about the precision of measurements and an understanding of the timeliness of a piece of data, as information utility degrades with time. The result is an ISO compliant data quality model with the required extensions included. - - - 17-032r2 - + OGC Testbed-13: CDB Engineering Report + 17-042 - Anneley McMillan, Sam Meek - 2018-01-26 - - - - - This OGC Testbed 17 Engineering Report (ER) documents the outcomes of a review and implementation of the Sensor Integration Framework Standards Profile (SIF-SP) v1.0.1, published by the National Center for Geospatial Intelligence Standards (NCGIS). + + This Engineering Report (ER) summarizes the CDB sub-thread work in Testbed 13. The document is structured in three phases and includes a feasibility study; the implementation of data models and schemas mapping that are based on the feasibility study results; and a set of OGC web services that implement the CDB in the form of WFS and WCS (Web Coverage Service) instances. -The Sensor Integration Framework Standard Profiles (SIF-SP) authors rightly acknowledge that sensing systems and the environments they operate in (e.g. hardware platform, computing resources, connectivity, ease of deployment, etc.) are very heterogeneous and that there will never be a single suite of technology or standards that can support the goal of providing unified access to sensor deployments employed in complex applications. +This Engineering Report describes: -Instead, rather than trying to impose a single standard or suite of standards, the SIF-SP approach defines common conceptual models that can be mapped to existing and future standards, thus allowing integration of all these standards in a single framework. +The conceptual model of an OGC CDB 1.0 datastore as a UML (Unified Modeling Language) diagram to show different datasets (the 3D models, vector features and coverages) structure; -This approach is fully compatible with the OGC Sensor Web Enablement (SWE) suite of standards that were designed for this type of integration. Thus, existing and upcoming SWE standards defined in the OGC can be used as the central pillar of a SIF implementation. The test implementation developed in this testbed, and based on OpenSensorHub, focused on demonstrating this aspect. +How to process and use a NAS-based Profile as a CDB feature/attribute data model or a GML-SF0 application schema; -In addition to a thorough review of the SIF material — including standards documents, UML models and ontologies — a prototype implementation of the SIF standards was created during the Testbed using OpenSensorHub. This allowed the testbed participants to check the practical feasibility of fulfilling the SIF requirements using the OGC SWE suite of standards. Details and feedback regarding this implementation are also provided in this ER. +How to access, navigate and visualize a CDB dataset using OGC web services (such as WFS and WCS). -Suggestions to improve SIF-SP and make it an integral part of the OGC standard baseline are also provided. +This work provides insights into: - - 21-022 - OGC Testbed-17: Sensor Integration Framework Assessment ER - Alex Robin - OGC Testbed-17: Sensor Integration Framework Assessment ER - 21-022 - - - - 2022-01-21 - - - +The in-depth study of the OGC CDB 1.0 feature data dictionary and attribution schema; + +The requirements and constraints for extending the CDB feature data dictionary (FDD) and attribute schemas; + +The development and prototyping of the WFS and WCS access to the CDB datastore for a NAS based urban military scenario. - - - Summary and Recommendations of the Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Interoperabi - 13-054r1 + - - 2013-11-07 - - Geospatial information technologies are increasingly a foundation for supporting Information Sharing Environment (ISE), homeland security (HLS), homeland defense (HLD), law enforcement (LE), emergency management (EM) and public safety missions in the US. The inability to transport, deliver and exchange geospatial information for critical geospatial assets increases the risk to the nation. -Many ISE HLS/HDS/LE mission partners have developed stand-alone geospatial information systems (GIS) or Common Operating Picture (COP) applications to support their stakeholder communities during incidents and for daily operational support. While different missions, these GIS/COP capabilities rely upon much of the same data or generate specific data during an event. The data are often stove-piped and not exposed to a broader community that could benefit from these data, resulting in duplication and delayed or incorrect decisions. While mission partners do not need to use the same GIS/COP tools, they could benefit from shared access to the common operating data and services used within these systems if they were exposed and exchanged using open standards. -Under the auspices of the Program Manager for the Information Sharing Environment (PM-ISE), an identified government-wide information sharing shortfall will be resolved by funding work to enhance the National Information Exchange Model (NIEM). The focus of this work is to further enhance the framework’s geospatial exchange capability in light of guidelines and standards issued by the Open Geospatial Consortium (OGC) so as to significantly improve inter-government information sharing. - - Summary and Recommendations of the Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Interoperabi - Richard Martell - 13-054r1 - + Harmonising Standards for Water Observation Data - Discussion Paper + 09-124r2 + This document investigates the potential for harmonisation of water data standards, with the goal of developing an OGC compliant standard for the exchange of water observation data. The work will be based on OGC‘s Observations and Measurements abstract model [10-004r2] . The goal is to create an O&M profile for the water domain. Development of the OGC compliant O&M profile will begin by examining the content and structure of existing standards and suggesting future methodology for developing a harmonised model for observation data. This approach will make use of existing standards where possible. + +The focus of this document is in-situ style observations (which are generally related to water quantity). Ex-situ measurements, such as those common to measuring water quality, will be addressed in future work. +2 Normative + + + Harmonising Standards for Water Observation Data - Discussion Paper + Peter Taylor + 09-124r2 + 2010-06-30 - - - Draft for Candidate OpenGIS® Web 3D Service Interface Standard - 09-104r1 + + + + Best Practice for Sensor Web Enablement Lightweight SOS Profile for Stationary In-Situ Sensors + 11-169r1 + + + - 2010-01-20 - Arne Schilling, Thomas H. Kolbe - 09-104r1 - - Draft for Candidate OpenGIS® Web 3D Service Interface Standard - A Web 3D Service (W3DS) is a portrayal service for three-dimensional geodata, such as landscape models, city models, textured building models, vegetation objects, and street furniture. Geodata is delivered as scenes that are comprised of display elements, optimized for efficient real time rendering at high frame rates. - - + + Simon Jirka, Christoph Stasch, Arne Bröring + This Best Practice document describes a lightweight SOS 2.0 profile for stationary in-situ +sensors. Besides the SOS itself this document also addresses the data formats used by the +SOS: Observations & Measurements 2.0 (O&M) for encoding measurement data and the +Sensor Model Language 2.0 (SensorML) for encoding metadata. Other SWE standards +which provide more specialized functionality are not part of this minimum lightweight +SWE profile. +The aim of this document is to present a common minimum profile of the SOS. The +profile is intended to reduce the complexity of the standard by omitting highly specific +elements that are not necessary for the majority of use cases that occur in practice. At the +same time, the profile is designed in such a way that all SOS implementations that +conform to this profile are also compliant to the according OGC specifications. + 2014-02-25 + OGC® Best Practice for Sensor Web Enablement Lightweight SOS Profile for Stationary In-Situ Sensors + 11-169r1 - + + Ajay Gupta, Luis Bermudez, Eddie Oldfield, Scott Serich + 19-076 + Health Spatial Data Infrastructure: Application Areas, Recommendations, and Architecture + This Health Spatial Data Infrastructure white paper provides a discussion about the collection, exchange, integration, analysis, and visualization of health and non-health data to support health applications. Applications that address health issues at global and population level scale as well as at the local, individual patient scale are presented. The paper identifies opportunities to advance OGC Standards towards building a framework to support Health Spatial Data Infrastructures (SDIs). + - - 19-008r4 - GeoTIFF Standard - This OGC Standard defines the Geographic Tagged Image File Format (GeoTIFF) by specifying requirements and encoding rules for using the Tagged Image File Format (TIFF) for the exchange of georeferenced or geocoded imagery. The OGC GeoTIFF 1.1 standard formalizes the existing community GeoTIFF specification version 1.0 and aligns it with the continuing addition of data to the EPSG Geodetic Parameter Dataset. - OGC GeoTIFF Standard + + - 2019-09-14 - 19-008r4 - - Emmanuel Devys, Ted Habermann, Chuck Heazel, Roger Lott, Even Rouault - + Health Spatial Data Infrastructure: Application Areas, Recommendations, and Architecture + + 2020-03-30 + 19-076 + + + + + + Web Coverage Service (WCS) Implementation Standard + 07-067r5 + Web Coverage Service (WCS) Implementation Standard + Arliss Whiteside + + 2008-04-29 + 07-067r5 + + The OpenGIS® Web Coverage Service Interface Standard (WCS) defines a standard interface and operations that enables interoperable access to geospatial coverages [http://www.opengeospatial.org/ogc/glossary/c]. The term grid coverages typically refers to content such as satellite images, digital aerial photos, digital elevation data, and other phenomena represented by values at each measurement point. - - - 2016-01-18 - OGC® Testbed 11 Digital Notice to Airmen (NOTAM) Validation and Enrichment Service Engineering Report - - Aleksandar Balaban + + + 02-007r4 + Units of Measure Recommendation + + + + Common semantic for units of measurement to be used across all OGC specifications. + 2002-08-19 + 02-007r4 + + John Bobbitt + + Units of Measure Recommendation + + + + + + + + + + + + + + + + + + OWS 3 GML Investigations - Performance Experiment by Galdos Systems + 05-101 + David Burggraf + + 2006-04-19 + 05-101 + In this experiment, the retrieval time of GML features from a Web Feature Service (WFS) to a WFS client will be studied by varying certain control parameters including methods of encoding and compression. Four different control parameters including encoding format, data set size, bandwidth, and feature type will be varied to test the relative performance in each case. + + + OWS 3 GML Investigations - Performance Experiment by Galdos Systems - - 15-027r1 - Testbed 11 Digital Notice to Airmen (NOTAM) Validation and Enrichment Service Engineering Report - 15-027r1 - This OGC Engineering Report (ER) is a deliverable of the OGC Testbed 11. This ER describes the Digital Notice to Airmen (NOTAM) enrichment and validation services in the Testbed 11 Aviation thread, including: -• A description of the architecture and architectural options. -• An overview of the implemented components and workflows followed by a short description of each component. -• Documentation of the issues, lessons learned as well as accomplishments and scenarios that were of general interest in the Aviation thread. -More detailed information on other specific aspects considered in OWS-11 Aviation may be found in the individual Aviation Engineering Reports. - + + + + 11-169 + This Discussion Paper describes a lightweight SOS 2.0 profile for stationary in-situ sensors. Besides the SOS itself this document also addresses the data formats used by the SOS: Observations & Measurements 2.0 (O&M) for encoding measurement data and the Sensor Model Language 2.0 (SensorML) for encoding metadata. Other SWE standards which provide more specialized functionality are not part of this minimum lightweight SWE profile. +The aim of this document is to present a common minimum profile of the SOS. The profile is intended to reduce the complexity of the standard by omitting highly specific elements that are not necessary for the majority of use cases that occur in practice. At the same time, the profile is designed in such a way that all SOS implementations that conform to this profile are also compliant to the according OGC specifications. + + 11-169 + Lightweight SOS Profile for Stationary In-Situ Sensors Discussion Paper + + Lightweight SOS Profile for Stationary In-Situ Sensors Discussion Paper + 2011-12-19 + + + Simon Jirka, Christoph Stasch, Arne Bröring + - + + 2021-02-26 + Carl Reed + This document provides the set of revision notes for the CDB Standard, version 1.2 [OGC <document number>]> and does not modify that standard. + 20-006 + + + - Luis Bermudez - - 15-002r5 - OGC Compliance Overview - Guide for Software Acquisition + OGC CDB Version 1.2 Release Notes + 20-006 + OGC CDB Version 1.2 Release Notes - - 2015-04-20 - 15-002r5 - - The Open Geospatial Consortium (OGC®) provides international standards that are implemented worldwide in thousands of applications that use location information. To reduce the risk of applications not implementing a standard correctly, the OGC provides a compliance process for testing and certifying implementations. OGC certification provides substantial evidence that an implementation that is claimed to have implemented an OGC standard will interoperate as specified and in the same manner as other compliant implementations, regardless of who developed them. This white paper provides guidance regarding language to specify requirements for OGC compliant and implementing products in software acquisition (procurement) documents. - OGC Compliance Overview - Guide for Software Acquisition - - + + Recommended XML/GML 3.1.1 encoding of image CRS definitions + 05-027r1 + + + Arliss Whiteside + 2005-04-13 + 05-027r1 + + Recommended XML/GML 3.1.1 encoding of image CRS definitions + - This Engineering Report (ER) describes requirements, challenges and solutions regarding improving multidimensional Earth Observation (EO) data access, discovery and visualization through Web Map Service (WMS), Web Map Tile Service (WMTS), and corresponding extensions. The ER will highlight solutions and recommendations of following main topics. -1) WMTS enhancements for time-varying layer access/discovery + This document recommends standard XML encodings of data defining monoscopic image coordinate reference systems. The scope of this encoding now includes unrectified and georectified images. The recommended CRSs for georectified images are recommended for multiple georectified images that are ready to be mosaicked together. -2) WMS enhancements for NetCDF +These recommended encodings are based on GML 3.1.1 and use XML Schemas. These image CRS definitions will often be referenced in data transferred between client and server software that implements various standardised interfaces. This specified definition data encoding is expected to be used by multiple OGC Implementation Specifications. That is, each of these specifications is expected to use a subset and/or superset of this recommended definition data. -3) WMTS enhancements for multidimensional domain discovery +The position or location of a point can be described using coordinates. Such coordinates are unambiguous only when the coordinate reference system on which those coordinates are based is fully defined. Each position is described by a set of coordinates based on a specified coordinate reference system. Coordinates are often used in datasets in which all coordinates belong to the same coordinate reference system. This paper specifies XML encoding of data defining image coordinate reference systems. - Lingjun Kang, Liping Di, Eugene Yu - 2017-06-14 - - - - Testbed-12 WMS/WMTS Enhanced Engineering Report - 16-042r1 - Testbed-12 WMS/WMTS Enhanced Engineering Report - - 16-042r1 - - - 2008-09-12 - Rüdiger Gartmann - OWS-5 GeoRM License Broker Discussion Paper - - 08-076 - 08-076 - OWS-5 GeoRM License Broker Discussion Paper - - - This document describes a License Broker Service (LB-Service) as specified and implemented in the OWS-5 test bed. The LB-Service provides configurable license models, which may contain configuration parameters to be defined by the licensee. The setting of these parameters affects the actual license to be created by the LB-Service. + + + Nadine Alameh + 13-011 + OWS-9: Summary of the OGC Web Services, Phase 9 (OWS-9) Interoperability Testbed + + 13-011 + + 2013-04-02 + This report summarizes the results of OGC Web Services Initiative, Phase 9 (OWS-9). + OWS-9: Summary of the OGC Web Services, Phase 9 (OWS-9) Interoperability Testbed + - - Ocean Science Interoperability Experiment Phase II Report - 09-156r2 - 09-156r2 - Ocean Science Interoperability Experiment Phase II Report - This OGC Engineering Report documents the work performed by the participants of the Ocean Science Interoperability Experiment Phase II. This work is a follow-on to the OGC Oceans IE Phase 1 activity. Specifically, this IE addressed the following tasks: -• Automated metadata/software installation via PUCK protocol. -• Offering of complex systems (e.g. observations systems containing other systems) such as collection of stations. -• Linking data from SOS to out-of-band offerings. -• Semantic Registry and Services. -• Catalogue Service-Web Registry. -• IEEE-1451/OGC-SWE harmonization - -As a result of this experiment, a number of recommendations and conclusions were identified. - - 2011-01-04 - + + + The LAS file is intended to contain LIDAR (or other) point cloud data records. The data will +generally be put into this format from software (e.g. provided by LIDAR hardware vendors) which +combines GPS, IMU, and laser pulse range data to produce X, Y, and Z point data. The intention +of the data format is to provide an open format that allows different LIDAR hardware and software +tools to output data in a common format. +This document reflects the fourth revision of the LAS format specification since its initial version +1.0 release. + 17-030r1 + LAS Specification 1.4 OGC Community Standard + ASPRS - Luis Bermudez - - + - + LAS Specification 1.4 OGC Community Standard + 2018-03-01 + + 17-030r1 + - - 2019-02-11 - OGC Testbed-14: BPMN Workflow Engineering Report - - + + + + + + + Documents of type User Guide + Documents of type User Guide - - - 18-085 - BPMN Workflow Engineering Report - Sam Meek - - This Engineering Report (ER) presents the results of the D146 Business Process Modeling Notation (BPMN) Engine work item and provides a study covering technologies including Docker, Kubernetes and Cloud Foundry for Developer Operations (DevOps) processes and deployment orchestration. The document also provides the beginning of a best practices effort to assist implementers wishing to orchestrate OGC services using BPMN workflow engines. As with previous investigations into workflow engines, the implementation described within utilizes a helper class, which is a bespoke implementation of some of the best practices. Work in future testbeds on workflows should include a compelling use case to demonstrate the power of service orchestration. - 18-085 + + Documents of type User Guide - + + The OpenGIS® Observations and Measurements Encoding Standard (O&M) defines an abstract model and an XML schema [www.w3.org/XML/Schema] encoding for observations and it provides support for common sampling strategies. O&M also provides a general framework for systems that deal in technical measurements in science and engineering. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. + 07-002r3 + Observations and Measurements - Part 2 - Sampling Features + 07-002r3 + 2007-12-26 + Simon Cox + + + + Observations and Measurements - Part 2 - Sampling Features + + + + + Carl Reed + 2018-12-19 + 16-006r4 + Volume 10: OGC CDB Implementation Guidance + + 16-006r4 + + + + Volume 10: OGC CDB Implementation Guidance + This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. + + + + CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211. + +The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. + - WCS Core 2.1 - 17-089r1 - - Peter Baumann - OGC Web Coverage Service (WCS) 2.1 Interface Standard - Core + + OGC City Geography Markup Language (CityGML) Encoding Standard + + Gerhard Gröger, Thomas H. Kolbe, Claus Nagel, Karl-Heinz Häfele - 17-089r1 - 2018-08-16 - The OGC Web Coverage Service (WCS) supports electronic retrieval of geospatial data as coverages. Coverages are digital geospatial information representing space/time-varying phenomena, specifically spatio-temporal regular and irregular grids, point clouds, and general meshes. -This document specifies the WCS core. Every implementation of a WCS shall adhere to this standard. This standard defines core requirements. Extensions to the core define extensions to meet additional requirements, such as the response encoding. Additional extensions are required in order to completely specify a WCS for implementation. -This WCS 2.1 standard extends WCS 2.0 in a backwards compatible manner by accommodating coverages as per the OGC Coverage Implementation Schema (CIS) 1.1 in addition to CIS 1.0 coverages as addressed by WCS 2.0. - + + 12-019 + 2012-04-04 + 12-019 + City Geography Markup Language (CityGML) Encoding Standard - - OGC Geotech Interoperability Experiment Engineering Report - 24-008 + + Kanishk Chaturvedi, Thomas H. Kolbe + 16-098 + - Mickael Beaufils, Kathi Schleidt, Hylke van der Schaaf, Dan Ponti, Neil Chadwick, Derrick Dasenbrock - 2024-07-05 - 24-008 - - OGC Geotech Interoperability Experiment Engineering Report - This Engineering Report (ER) describes the outcomes of the Open Geospatial Consortium (OGC) Geotech Interoperability Experiment (IE). The objective of this IE was to develop a common conceptual model for describing geotechnical engineering data that bridges existing specifications for encoding those data and which could be integrated across OGC and buildingSMART International Standards, + + Future City Pilot 1 Engineering Report + 16-098 + + The Future City Pilot Phase 1 (FCP1) is an OGC Interoperability Program initiative in collaboration with buildingSMART International (bSI). The pilot aimed at demonstrating and enhancing the ability of spatial data infrastructures to support quality of life, civic initiatives, and urban resilience. During the pilot, multiple scenarios were set up based on real-world requirements and were put forward by the pilot sponsors: Sant Cugat del Vallès (Barcelona, Spain), Ordnance Survey Great Britain (UK), virtualcitySYSTEMS GmbH (Germany), and Institut National de l’Information Géographique et Forestière - IGN (France). The scenarios were focused on (i) the interoperability between the two international standards: Industry Foundation Classes (IFC) and CityGML; (ii) city flood modeling; and (iii) supporting real-time sensor readings and other time-dependent properties within semantic 3D city models. The solutions for the respective scenarios were developed by the pilot participants: University of Melbourne (Australia), Remote Sensing Solutions, Inc. (U.S.A), and Technical University of Munich (Germany). This Engineering Report (ER) focuses on the third scenario requiring the support of real-time sensors and other time-dependent properties within semantic 3D city models based on the CityGML standard. It highlights a new concept 'Dynamizer', which allows representation of highly dynamic data in different and generic ways and providing a method for injecting dynamic variations of city object properties into the static representations. It also establishes explicit links between sensor/observation data and the respective properties of city model objects that are measured by them. The Dynamizer concept has been implemented as an Application Domain Extension (ADE) of the CityGML standard. This implementation allows to use new dynamizer features with the current version of the CityGML standard (CityGML 2.0). The advantage with this approach is that it allows for selected properties of city models to become dynamic without changing the original CityGML data model. If an application does not support dynamic data, it simply does not allow/include these special types of features. The details and results of the pilot are mentioned in the following YouTube video: https://youtu.be/aSQFIPwf2oM + + + Future City Pilot 1 Engineering Report + 2017-10-20 + + + + + + + + + + + + + + + + + + + + + + + + + + + + OGC API - Features - Part 1: Core + Clemens Portele, Panagiotis (Peter) A. Vretanos, Charles Heazel + 17-069r3 + OGC API - Features - Part 1: Core + 17-069r3 + OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks. -This ER is directly imported from the project wiki found here: https://github.com/opengeospatial/Geotech/wiki. - +The OGC API family of standards is organized by resource type. This standard specifies the fundamental API building blocks for interacting with features. The spatial data community uses the term 'feature' for things in the real world that are of interest. + - + 2019-10-07 - - - 2019-10-31 - Simon Cox, Gobe Hobona - OGC Naming Authority – Policies and Procedures - 09-046r5 - - - 09-046r5 - OGC Naming Authority – Policies and Procedures - - - This document describes the procedures used by the OGC Naming Authority for the assignment and registration of OGC names. - - - + + 05-111r2 + This document demonstrats a number of functional capabilities related to rights management (Terms-of-Use, Authentication, content services) that need to be described and chained. + Access Control & Terms of Use (ToU) "Click-through" IPR Management + 05-111r2 - - GeoPackage Encoding Standard - 12-128r19 - Jeff Yutzler - 2024-02-06 - 12-128r19 - OGC® GeoPackage Encoding Standard - - This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. - - - - - Overview of the CoverageJSON format - 16-145 - 16-145 + Roland M. Wagner + - - This Note describes CoverageJSON, a data format for describing coverage data in JavaScript Object Notation (JSON), and provides an overview of its design and capabilities. The primary intended purpose of the format is to enable data transfer between servers and web browsers, to support the development of interactive, data-driven web applications. Coverage data is a term that encompasses many kinds of data whose properties vary with space, time and other dimensions, including (but not limited to) satellite imagery, weather forecasts and river gauge measurements. We describe the motivation and objectives of the format, and provide a high-level overview of its structure and semantics. We compare CoverageJSON with other coverage formats and data models and provide links to tools and libraries that can help users to produce and consume data in this format. This Note does not attempt to describe the full CoverageJSON specification in detail: this is available at the project website. - - - Overview of the CoverageJSON format - Jon Blower, Maik Riechert, Bill Roberts - 2020-09-17 + 2006-05-09 + + Access Control & Terms of Use (ToU) "Click-through" IPR Management - - - OGC Testbed-17: Moving Features ER - 21-036 - - 2022-01-21 - - - OGC Testbed-17: Moving Features ER - 21-036 - + - The OGC Testbed-17 Moving Features (MF) task addressed the exchange of moving object detections, shared processing of detections for correlation and analysis, and visualization of moving objects within common operational pictures. This Engineering Report (ER) explores and describes an architecture for collaborative distributed object detection and analysis of multi-source motion imagery, supported by OGC MF standards. The ER presents the proposed architecture, identifies the necessary standards, describes all developed components, reports on the results of all TIE activities, and provides a description of recommended future work items. - Guy Schumann - - - - Ben Domenico, Stefano Nativi - 09-018 - - This extension of the WCS standard specifies an Information Community data model with the related encoding that may optionally be implemented by WCS servers. This extension specification allows clients to evaluate, request and use data encoded in CF-netCDF3 format from a WCS server. -This document is an extension of the Web Coverage Service (WCS) 1.1 Corrigendum 2 (version 1.1.2) Implementation Standard [OGC 07-067r5]. With small changes, this extension is expected to also apply to WCS 1.2. - - - 09-018 - Web Coverage Service (WCS) 1.1 extension for CF-netCDF 3.0 encoding - - 2009-04-08 + 2009-07-24 - Web Coverage Service (WCS) 1.1 extension for CF-netCDF 3.0 encoding + 09-041r3 + OWS-6 WPS Grid Processing Profile Engineering Report + OWS-6 WPS Grid Processing Profile Engineering Report + + + 09-041r3 + This OGC Engineering Report describes and reviews the Grid Computing related activity completed during the OGC OWS-6 Interoperability testbed. The document describes the WPS processes deployed in the different demonstration scenarios and offers recommendations to the OGC community as to how to better harmonize the standards work of the OGC with Grid Computing platforms and related concepts and technologies. + Bastian Baranski + - + + 2021-01-13 + 20-033 + Sam Meek + 20-033 + OpenAPI Engineering Report + + + + This OGC Testbed 16 Engineering Report (ER) documents the two major aspects of the Testbed 16 OpenAPI Thread. These are: + +A Unified Modeling Language (UML) metamodel that describes OpenAPI and a profile of that model to describe OGC API - Features - Part 1: Core; + +An implementation of a transformation procedure in the ShapeChange open source software. This procedure was designed to transform a UML representation of the OGC API - Features - Part 1: Core model into an OpenAPI 3.0 document. + +The process for creating the model and doing the transformation relied upon the Model Driven Architecture (MDA) approach. MDA takes a platform independent model (PIM) and transforms that model into a platform specific model (PSM). - 16-009r4 - Volume 6: OGC CDB Rules for Encoding Data using OpenFlight - - This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of that document for a general overview. - - 16-009r4 - Carl Reed - - Volume 6: OGC CDB Rules for Encoding Data using OpenFlight - 2018-12-19 - + + OGC Testbed-16: OpenAPI Engineering Report - + + OGC 17-018 (Testbed-13 Data Quality Specification Engineering Report) provides methods to quantify the quality concepts defined in OGC 17-032 and a way to include the quantifications in service descriptions. It extends QualityML quality metrics (that already includes ISO 19157) into the aviation domain. It lists a set of quantitative and conformance measurements that are specified in terms of quality measures, domains, and metrics (value types and units) and are appropriated for each quality type and data type. Secondly, it extends the SDCM to be able to encode and include the above mentioned quality information for each service in a interoperable way. + OGC Testbed-13: Data Quality Specification Engineering Report + + 2018-01-26 + Alaitz Zabala, Joan Maso + 17-018 + + 17-018 + Testbed-13: Data Quality Specification Engineering Report + - 23-028 - OGC Testbed 19 Extraterrestrial GeoTIFF Engineering Report - 2024-04-16 - Michael Leedahl - - 23-028 - OGC Testbed 19 Extraterrestrial GeoTIFF Engineering Report - - With the growing number of space assets and missions, the space industry needs a way to locate extra-terrestrial objects within the captured imagery. The current GeoTIFF Standard provides the location of terrestrial objects using TIFF tags. However, objects in space are relative to the observer and the distance of the objects in the imagery are often at great distances from the observer. Multiple objects can exist within the imagery which are at different spacetime locations in four dimensions. To further complicate the definition of the location, from a planar perspective, the edges of the image fade into infinity. With the use of spherical and gridded coordinates an image can tag pixels along the edge of a sphere or the camera location. The Testbed 19 Engineering Report (ER) extends GeoTIFF to work for all images including both terrestrial and non-terrestrial observations within the image. - - - Web Coverage Service (WCS) Implementation Specification - 03-065r6 - + + 12-094 + + Aviation: AIRM Derivation + 12-094 + + This report describes the architecture, rules and tools developed within the OWS-9 Aviation Thread AIRM Derivation task. These rules and tools were demonstrated by transforming the AIRM Meteorology package into a Weather Exchange Model (WXXM) and GML/JSON implementation schema. + + OWS-9 Aviation: AIRM Derivation - Extends the Web Map Server (WMS) interface to allow access to geospatial coverages that represent values or properties of geographic locations, rather than WMS generated maps (pictures). - 2003-10-16 + 2013-02-05 + + Debbie Wilson, Clemens Portele - - - - 03-065r6 - John Evans - OpenGIS Web Coverage Service (WCS) Implementation Specification - - - Ingo Simonis, Johannes Echterhoff + - - 06-095 - Web Notification Service - Web Notification Service - - A service by which a client may conduct asynchronous dialogues (message interchanges) with one or more other services. This service is useful when many collaborating services are required to satisfy a client request, and/or when significant delays are involved is satisfying the request. This service was defined under OWS 1.2 in support of SPS operations. WNS has broad applicability in many such multi-service applications. It is now used in several SWE scenarios. - 2007-01-25 - - 06-095 - - - - This document describes an extension to the existing RDF Data Cube ontology to support specification of key metadata required to interpret spatio-temporal data. The RDF Data Cube defines CodedProperties, which relate to a reference system based on a list of terms, QB4ST provides generalized support for numeric and other ordered references systems, particularly Spatial Reference Systems and Temporal Reference Systems. Although RDF Data Cube supports AttributeProperties for metadata of individual observations, the requirement is to specify such metadata per property, rather than for each observation, and thus allow different properties to use different spatial or temporal reference systems. QB4ST also provides for such properties to be defined for a ComponentProperty, or defined at the time of referencing that ComponentProperty in a ComponentSpecification. QB4ST is thus aimed at improving the scope and consistency of dataset metadata, and hence discovery and interpretation of spatio-temporal data through its spatio-temporal reference system and bounding values. - 16-142 - QB4ST: RDF Data Cube extensions for spatio-temporal components - Rob Atkinson + 09-132r1 + Specification of the Sensor Service Architecture (SensorSA) + Thomas Usländer (Ed.) + + Specification of the Sensor Service Architecture (SensorSA) + + Specification of a generic service-oriented architecture integrating the access to, the management and the processing of sensor-related information based upon the emerging standards of the Open geospatial Consortium (OGC), and resulting from the requirements analysis of diverse application domains such as maritime risk management, observation of geo-hazards and monitoring of air quality. + 09-132r1 + 2009-10-02 + + + + + 2023-03-13 - QB4ST: RDF Data Cube extensions for spatio-temporal components - 16-142 - + - - 2020-09-17 + Paul Churchyard, Ajay Gupta + + 22-020r1 + + 22-020r1 + Testbed-18: Identifiers for Reproducible Science Summary Engineering Report + Testbed-18: Identifiers for Reproducible Science Summary Engineering Report + The OGC’s Testbed 18 initiative explored the following six tasks. + +1.) Advanced Interoperability for Building Energy +2.) Secure Asynchronous Catalogs +3.) Identifiers for Reproducible Science +4.) Moving Features and Sensor Integration +5.) 3D+ Data Standards and Streaming +6.) Machine Learning Training Data +Testbed 18 Task 3, Identifiers for Reproducible Science, explored and developed workflows demonstrating best practices at the intersection of Findable, Accessible, Interoperable, and Reusable (or FAIR) data and reproducible science. + +The workflows developed in this Testbed included: + +the development of a Whole Tail workflow for land cover classification (52 Degrees North); +the development of a reproducible workflow for a deep learning application for target detection (Arizona State University); +the implementation of reproducible workflows following the approach described in the OGC API Process Part 3: Workflows and Chaining for Modular OGC API Workflows (Ecere); +the development of a reproducible workflow that runs an OGC API — Process and Feature Server instance within a Whole Tale environment (GeoLabs); and +the development of a water body detection Application Package to cover the identifier assignment and reproducibility from code to several execution scenarios (local, Exploitation Platform, Whole Tale) (Terradue). +Testbed 18 participants identified considerations and limitations for reproducible workflows and recommendations for future work to identify the benefits of reproducible science for healthcare use cases. - - - GML 3.2 implementation of XML schemas in 07-002r3 + + + 01-022r1 + Basic Services Model + 01-022r1 + The Basic Services Model is an implementation of the ISO TC211 services architecture as found in ISO 19119 Geographic Information + - Simon Cox - 2009-03-06 - - - + 2001-05-05 + + Basic Services Model + Jeff de La Beaujardiere - 08-129 - GML 3.2 implementation of XML schemas in 07-002r3 - 08-129 - - - Portrayal of geospatial information plays a crucial role in situation awareness, analysis and decision-making. Visualizing geospatial information often requires one to portray the information using symbology or cartographic presentation rules from a community or organization. For example, among those in the law enforcement, fire and rescue community, various local, national and international agencies use different symbols and terminology for the same event, location and building, employing syntactic, structural-based and document-centric data models (e.g., eXtensible Markup Language (XML) schemas and Style Layer Descriptors (SLD)). With this approach, interoperability does not extend to the semantic level, which makes it difficult to share, reuse and mediate unambiguous portrayal information between agencies. - -This Engineering Report (ER) captures the requirements, solutions, models and implementations of the Testbed 13 Portrayal Package. This effort leverages the work on Portrayal Ontology development and Semantic Portrayal Service conducted during Testbed 10, 11 and 12. The objective of this Testbed 13 is to identify and complete the gaps in the latest version of the portrayal ontology defined in Testbed 12, complete the implementation of the Semantic Portrayal Service by adding rendering capabilities and performing a demonstration of the portrayal service that showcases the benefits of the proposed semantic-based approach. - 17-045 - Testbed-13: Portrayal Engineering Report - - - 17-045 - 2018-03-05 + - Stephane Fellah - OGC Testbed-13: Portrayal Engineering Report + OpenGIS Web Coverage Processing Service (WCPS) Language Interface Standard + Web Coverage Processing Service (WCPS) Language Interface Standard + 08-068r2 + + 08-068r2 + The OGC® Web Coverage Processing Service (WCPS) defines a protocol-independent language for the extraction, processing, and analysis of multi-dimensional coverages representing sensor, image, or statistics data. + Peter Baumann + + 2009-03-25 + - + - + + OGC Best Practice for using SensorThings API with Citizen Science + This document introduces an extension to the OGC SensorThings data model and discusses +the best practices for using such an extension in the context of Citizen Science. +The motivation for the introduced extension, referred to as “STAplus,” has been developed +during the EC H2020 project Cos4Cloud and is based on requirements from Citizen Science. +Whereas the dominant use of the OGC SensorThings data model (and API) can be coined +with the use case “single authority provides sensor readings to consumers”, in Citizen +Science there are many contributors (citizens) that – together – create the big “picture” with +their observations. +The introduced extension STAplus supports the model that those observations are owned by +(different) users that may express the license for re-use; we call this part of the contribution +the ownership concept. In addition to the ownership and license abilities, the introduced +extension allows to express explicit relations between observations and to create group(s) of +observations to containerize observations that belong together. Relations can be created +among any individual observations or observations of a group to support performant Linked +Data extraction and semantic queries, e.g., expressed in SPARQL. +We believe that the introduced extension is an important contribution towards the realization +of the FAIR principles, perhaps not only in Citizen Science, as STAplus strengthens the “I” +(Interoperability) through a common data model and API as well as the “R” (Reusability) by +allowing to express standards-based queries that may consider licensing conditions, relevant +for reuse of other users’ observations. The STAplus Data Model and Business Logic also +enriches existing deployments as the extension can be seamlessly added and thereby offer +new capabilities to create and manage the “big picture” with multi-user capabilities. +This document also illustrates best practices of using STAplus, evaluated with proof-ofconcept deployments based on the implementations by 52°North, Secure Dimensions, and +CREAF. + + OGC Best Practice for using SensorThings API with Citizen Science + 21-068 + Andreas Matheus + 21-068 - OWS-7 - Towards secure interconnection of OGC Web Services with SWIM - - - This Engineering Report provides guidance and generate action items for the OGC standardization effort to properly enable security in the near future such that a seamless, interoperable but secure interconnection between OGC Web Services and FUSE ESB technology stack as selected by use in the System Wide Information Management (SWIM) System of the US Federal Aviation Administration (FAA) can be achieved. - 10-155 - - OWS-7 - Towards secure interconnection of OGC Web Services with SWIM - 10-155 - 2010-08-18 - Andreas Matheus - - - - - 07-158 - Discussion of how to wrap OGC HTTP-GET/POST Services with SOAP - 2008-01-02 - Wrapping OGC HTTP-GET/POST Services with SOAP + + 2022-09-29 + + + + 2011-08-11 + 11-110 + + Open Source and Open Standards + Arnulf Christl and Carl Reed + Open Source and Open Standards + 11-110 - R + - - 07-158 - Wrapping OGC HTTP-GET/POST Services with SOAP - + + + This article is a White Paper jointly published by OGC and OSGeo. It was approved as an official joint OSGeo and OGC White Paper by the OSGeo Board of Directors in their 2011-05-05 Board meeting. +The text was collaboratively edited, reviewed and finalized by more than a a dozen active OSGeo and OGC members. Thanks especially to Gavin Fleming, Lance McKee, Markus Neteler, Athina Trakas, Michael Gerlek, Adrian Custer, Jeff McKenna, Cameron Shorter, Carl Reed, Frank Warmerdam, Steven Ramage, Daniel Morissette, Arnulf Christl and others for their contributions. +Please feel free to add comments, criticisms, links to other concise definitions on the associated Talk page: http://wiki.osgeo.org/wiki/Open_Source_and_Open_Standards. - - OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension + + Sina Taghavikish - - - - - 16-083r2 - Coverage Implementation Schema - ReferenceableGridCoverage Extension - 16-083r2 - The OGC GML Application Schema - Coverages (“GMLCOV”) version 1.0 [OGC 09-146r2], recently renamed the OGC Coverage Implementation Schema version 1.0, provides a ReferenceableGridCoverage element for representing coverages on a referenceable grid. However, GMLCOV provides no instantiable subtypes of a critical sub-element of ReferenceableGridCoverage, GMLCOV::AbstractReferenceableGrid. To make use of ReferenceableGridCoverage, an extension deriving from GMLCOV would need to be developed. GML 3.3 is not such an extension of GMLCOV, as it is built independently from GMLCOV. Use of the instantiable referenceable grid elements of GML 3.3 with ReferenceableGridCoverage violates Requirement 14 of GMLCOV 1.0 and Requirement 24 of the OGC Modular Specification[1]. + Testbed-18 explored the potential use of OGC Standards for non-terrestrial applications and was scoped as a paper study. Validation of the Testbed-18 recommendations has been left for Testbed-19. This OGC Engineering Report (ER) documents recommended changes to OGC Standards and the implementation experience to justify those changes. -This OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension provides a set of referenceable grid elements for use as sub-elements of ReferenceableGridCoverage. Three of these elements have been adapted from GML 3.3, while a fourth emerged from work on a Testbed-11 Engineering Report[2]. - 2017-06-15 - Eric Hirschorn - - - OWS-9 OWS Innovations WCS for LIDAR Engineering Report - 12-155 - - Weiguo Han, Yuanzheng Shao, Liping Di - - - - OGC® OWS-9 OWS Innovations WCS for LIDAR Engineering Report +The use of OGC Standards include geospatial applications for non-Earth planets as well as interplanetary spatiotemporal applications. Two Standards emerged as key: ISO 19111 (OGC Abstract Specification 2: Referencing by coordinates) and OGC 21-056r11 (OGC GeoPose 1.0 Data Exchange Standard). Extensions to ISO 19111 were identified which would support the representation of non-terrestrial planetary spatial reference systems as well as interplanetary spatiotemporal reference systems. + +The GeoPose Standard (GeoPose) was explored as a mechanism to integrate the large number of reference systems and transformations needed to model the geometry of interplanetary spacetime. + +In the context of the Double Asteroid Redirection Test (DART) scenario, positions and orientations in different coordinate reference systems and associated attributes such as velocities of non-terrestrial objects were encoded using two different approaches: as sequences of extended GeoPoses, and as OGC Moving Features JSON (MF-JSON). These encoded data were then used as the basis for a 3D visualization demonstration. + +This work is not intended to replace the existing standards already used in astronomy such as the World Coordinate System (WCS). The recommendations provided in this ER are rather intended to improve interoperability by specifying how to export a subset of a WCS description as OGC/ISO data structures for consumption by GIS software or other geospatial technology applications. + +Testbed-18 also investigated how GeoPose could be integrated with mobile location-aware devices such as smartphones. Engineering Report OGC 22-016r3 (Testbed-18: Moving Features) concluded that GeoPose could enrich data with location and orientation information synchronized to video and other sensors and identified two suitable road network use cases for study using WebVMT in Testbed-19. - This Engineering Report is prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiatitive of the Innovations Coverages Sub-Thread. This document represents the OWS-9 OWS Innovations WCS for LIDAR Engineering Report. In this report, the implementation of WCS 2.0 service that serves the LIDAR data in NITF format is introduced. This service supports the JPEG 2000 output format along with GMLJP2 metadata description as well as the JPIP protocol to deliver the output JPEG2000 data. + + OGC Testbed-19 — Non-Terrestrial Geospatial Engineering Report + 2024-07-05 + 23-042 + OGC Testbed-19 — Non-Terrestrial Geospatial Engineering Report + 23-042 + - 2013-06-18 - 12-155 - - Sergio Taleisnik - OGC Testbed-17: Aviation API ER + - - 21-039r1 - OGC Testbed-17: Aviation API ER - - 21-039r1 - 2022-01-21 - This Testbed-17 (TB-17) Aviation API Engineering Report (ER) summarizes the implementations, findings and recommendations that emerged from the efforts of building a definition for an Aviation API compliant with the requirements of the OGC Standards Program, and the exploration of the potential of aviation data fusion. - -This ER describes the nine façades built to interface SWIM services and serve aviation data through OGC APIs, the two services built to consume SWIM data and fuse it to generate richer datasets while serving the fused data through OGC APIs, the client application built to display data retrieved from the façades and fusion services, and the development client built to focus on functionality and experimentation. - -Finally, this ER discusses the potential of OGC APIs to help standardize the access to aviation data within the context of the System Wide Information Management (SWIM) program. - + 13-042 + + Daniele Marchionni + OGC RESTful Encoding of Ordering Services Framework For Earth Observation Products + + 13-042 + RESTful Encoding of Ordering Services Framework For Earth Observation Products + + 2014-04-28 + This OGC Best Practices document specifies the interfaces, bindings, requirements, conformance classes that enable complete workflows for ordering Earth Observation (EO) data products. In fact it provides the interfaces for supporting the following EO Product ordering scenarios: +• Ordering products from EO Catalogues +• Subscribing to automatic delivery of EO products +• Bulk EO Product orders +The EO products orders can be delivered on file via different online protocols (e.g. ftp, sftp, ftps, etc.). + - + + Steve Miller - + This OGC® document describes the architecture used for the implementation of the SAA Dissemination Pilot Study demonstrations. This includes an overview of the implemented components and workflows, and discussions of lessons learned. - OWS-7 Motion Imagery Discovery and Retrieval Engineering Report - Wenli Yang, Liping Di - 2010-08-18 - 10-087 - This Motion Imagery Discovery and Retrieval Engineering Report (ER) documents the metadata used to tag geolocation of Motion Imagery (MI) for discovery, retrieval and linkage with other data sources over the same location, especially the metadata information required to geometrically co-register multiple motion images at pixel level so that data recorded at different times (e.g., different days) and/or by different providers for common or overlapped FOVs can be compared and pixel level changes among the different images can be accurately detected and delineated. This ER reflects one of the achievements during the OWS 7 Sensor Fusion Enablement (SFE) thread, which builds on the OGC Sensor Web Enablement framework that has achieved a degree of maturity through previous OWS interoperability initiatives and deployments worldwide. - OWS-7 Motion Imagery Discovery and Retrieval Engineering Report - 10-087 - + 11-055 + + OGC SAA Pilot Study Engineering Report - - - - Future City Pilot 1 Engineering Report - 16-098 - 16-098 - 2017-10-20 - + OGC SAA Pilot Study Engineering Report + 11-055 + 2011-11-23 - The Future City Pilot Phase 1 (FCP1) is an OGC Interoperability Program initiative in collaboration with buildingSMART International (bSI). The pilot aimed at demonstrating and enhancing the ability of spatial data infrastructures to support quality of life, civic initiatives, and urban resilience. During the pilot, multiple scenarios were set up based on real-world requirements and were put forward by the pilot sponsors: Sant Cugat del Vallès (Barcelona, Spain), Ordnance Survey Great Britain (UK), virtualcitySYSTEMS GmbH (Germany), and Institut National de l’Information Géographique et Forestière - IGN (France). The scenarios were focused on (i) the interoperability between the two international standards: Industry Foundation Classes (IFC) and CityGML; (ii) city flood modeling; and (iii) supporting real-time sensor readings and other time-dependent properties within semantic 3D city models. The solutions for the respective scenarios were developed by the pilot participants: University of Melbourne (Australia), Remote Sensing Solutions, Inc. (U.S.A), and Technical University of Munich (Germany). This Engineering Report (ER) focuses on the third scenario requiring the support of real-time sensors and other time-dependent properties within semantic 3D city models based on the CityGML standard. It highlights a new concept 'Dynamizer', which allows representation of highly dynamic data in different and generic ways and providing a method for injecting dynamic variations of city object properties into the static representations. It also establishes explicit links between sensor/observation data and the respective properties of city model objects that are measured by them. The Dynamizer concept has been implemented as an Application Domain Extension (ADE) of the CityGML standard. This implementation allows to use new dynamizer features with the current version of the CityGML standard (CityGML 2.0). The advantage with this approach is that it allows for selected properties of city models to become dynamic without changing the original CityGML data model. If an application does not support dynamic data, it simply does not allow/include these special types of features. The details and results of the pilot are mentioned in the following YouTube video: https://youtu.be/aSQFIPwf2oM - - Future City Pilot 1 Engineering Report - Kanishk Chaturvedi, Thomas H. Kolbe - + + + 16-022 + + 2017-06-30 + Testbed-12 WPS Conflation Service Profile Engineering Report + 16-022 + Testbed-12 WPS Conflation Service Profile Engineering Report + + + One practical purpose of this ER will be to describe how a conflation tool such as the Hootenanny software can be used for conflation tasks using the Web Processing Service interface. The developed WPS REST (conflation) Service will be described in detail. Special focus will be laid on more complex conflation tasks that include user interaction. During earlier testbeds, we connected different conflation tools to the WPS and performed different conflation tasks (see [1] and [2]). The experiences gathered there together with the ones gathered in the Testbed 12 will be captured in the ER. As the WPS REST (Conflation) Service will be RESTful, this ER could be the basis for a REST binding extension for WPS 2.0. Service profiles are an important aspect of the WPS 2.0 standard. We will investigate how a WPS 2.0 Conflation Profile could look like in the hierarchical profiling approach of WPS 2.0. + Benjamin Pross + + - + + + Clemens Portele + + - - OGC® IndoorGML - with Corrigendum - 14-005r4 - This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes. + + + OWS-5 Engineering Report: Local MSD Implementation Profile (GML 3.2.1) + 08-077 + 08-077 + OGC® OWS-5 Engineering Report: Local MSD Implementation Profile (GML 3.2.1) + This document contains a data content specification for Local Mission Specific Data (MSD) and is based on the GEOINT Structure Implementation Profile (GSIP) developed by the NGA. This document defines the GML 3.2.1 (ISO 19136) encoding requirements for Local MSD. The structure of the document is based on ISO 19131 (Geographic Information – Data Product Specification). + 2008-07-02 + + + Volume 11: OGC CDB Core Standard Conceptual Model + 16-007r4 + Volume 11: OGC CDB Core Standard Conceptual Model + This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB Standard. The objective of this document is to provide an abstract core conceptual model for a CDB data store (repository). The model is represented using UML (unified modeling language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering the UML diagrams and documentation from the original CDB submission as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113r5]. +NOTE: The simulation community uses the term “synthetic environment data” to mean all the digital data stored in some database or structured data store that is required for use by simulation clients. From the geospatial community perspective, these data are essentially the same as GIS data but with, in some cases, special attributes, such as radar reflectivity. - 2016-08-23 - Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker - - - OGC® IndoorGML - with Corrigendum - - - 14-005r4 + Sara Saeedi + + 16-007r4 + + + + + 2018-12-19 - - + - 14-005r5 - OGC® IndoorGML - with Corrigendum + 10-140r2 + Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile + OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile + + The OGC Web Coverage Service (WCS) Application Profile - Earth Observation (EO- WCS) defines a profile of WCS 2.0 [OGC 09-110r4] for use on Earth Observation data. + + Peter Baumann, Stephan Meissl, Jinsongdi Yu + 10-140r2 + + 2018-10-04 - 14-005r5 - Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker - OGC® IndoorGML - with Corrigendum - 2018-03-09 - - - This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes. - - This document specifies the interface to a Web Coordinate Transformation Service (WCTS), which can be used by geospatial applications and other services. Transformation of geospatial data from one coordinate reference system (CRS) to another is frequently required when using data from different sources in one application. That is, geospatial data are often stored in different coordinate reference systems (CRSs). To use together data stored in different CRSs, such data must be transformed or converted into the same CRS. Not all applications or services are capable of directly performing such transformations. - -This document specifies an OGC Web Service type of interface to a service that performs coordinate transformations. Such transformations include all the types of coordinate operations, including both transformations and conversions. This service inputs digital features or coverages in one CRS and outputs the same features in a different CRS. The service inputs include identifications of the input and output CRSs, and optionally the coordinate transformation between these CRSs. + + Tiled WMS Discussion Paper + 07-057r2 + 07-057r2 + + The OpenGIS® Tiled Web Map Service Discussion Paper explains how the OpenGIS Web Map Service Standard (WMS) [http://www.opengeospatial.org/standards/wms] can be extended to allow fast response to a predefined set of tiled maps. It should be read in conjunction with the latest version WMS standard. - Web Coordinate Transformation Service - 2005-04-13 - + 2007-10-10 + - Web Coordinate Transformation Service - 05-013 - - - 05-013 - - Arliss Whiteside, Markus U. M - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + Keith Pomakis + + + OpenGIS Tiled WMS Discussion Paper - - - 06-021r4 - Sensor Web Enablement Architecture - OGC® Sensor Web Enablement Architecture - 06-021r4 - 2008-08-20 - Ingo Simonis - - + + + + Sensor Interface Descriptors + 10-134 + - This document describes the architecture implemented by Open Geospatial Consortium’s (OGC) Sensor Web Enablement Initiative (SWE). In contrast to other OGC SWE stan-dards, this document is not an implementation standard. + + Sensor Interface Descriptors + 10-134 + 2010-06-30 + Arne Broering, Stefan Below + + This document presents the Sensor Interface Descriptor (SID) schema that enables the declarative description of sensor interfaces, including the definition of the communication protocol, sensor commands, processing steps and metadata association. This schema is designed as a profile and extension of SensorML. Based on this schema, SID interpreters can be implemented, independently of particular sensor technology, which are able to translate between sensor protocol and SWE protocols. They establish the connection to a sensor and are able to communicate with it by using the sensor protocol definition of the SID. SID instances for particular sensor types can be reused in different scenarios and can be shared among user communities. The ability of an SID interpreter to connect sensors and Sensor Web services in an ad hoc manner based on the sensor’s SID instance is a next step towards realizing sensor plug & play within the Sensor Web. + + + + 16-005r4 + 16-005r4 + Volume 2: OGC CDB Core Model and Physical Structure Annexes (Best Practice) + + This document provides the Annexes for the CDB Core: Model and Physical Structure Standard. The only exception is Annex A, Abstract Test Suite (ATS). The CDB ATS Annex is in Volume 1: Core document. + 2021-02-26 + + Volume 2: OGC CDB Core Model and Physical Structure Annexes (Best Practice) + + Carl Reed - - - 17-011r2 - JSON Encoding Rules SWE Common / SensorML - Alex Robin - JSON Encoding Rules SWE Common / SensorML - - This document describes new JavaScript Object Notation (JSON) encodings for the Sensor Web Enablement (SWE) Common Data Model and the Sensor Model Language (SensorML). Rather than creating new JSON schemas, this document defines encoding rules that allow auto-generation of JSON instances that conform to the Unified Modeling Language (UML) models. Alternatively, the mappings given in the second part of the document can be used to convert bi-directionally between XML and JSON representations. + + + + Portrayal of geospatial information plays a crucial role in situation awareness, analysis and decision-making. Visualizing geospatial information often requires one to portray the information using symbology or cartographic presentation rules from a community or organization. For example, among those in the law enforcement, fire and rescue community, various local, national and international agencies use different symbols and terminology for the same event, location and building, employing syntactic, structural-based and document-centric data models (e.g., eXtensible Markup Language (XML) schemas and Style Layer Descriptors (SLD)). With this approach, interoperability does not extend to the semantic level, which makes it difficult to share, reuse and mediate unambiguous portrayal information between agencies. - - - 2018-01-18 +This Engineering Report (ER) captures the requirements, solutions, models and implementations of the Testbed 13 Portrayal Package. This effort leverages the work on Portrayal Ontology development and Semantic Portrayal Service conducted during Testbed 10, 11 and 12. The objective of this Testbed 13 is to identify and complete the gaps in the latest version of the portrayal ontology defined in Testbed 12, complete the implementation of the Semantic Portrayal Service by adding rendering capabilities and performing a demonstration of the portrayal service that showcases the benefits of the proposed semantic-based approach. + + OGC Testbed-13: Portrayal Engineering Report + Stephane Fellah - - - 17-011r2 - - - July 2021 OGC API Code Sprint Summary Engineering Report - 21-055 - - 2021-11-29 + 17-045 + Testbed-13: Portrayal Engineering Report + + 2018-03-05 + 17-045 + + + 2018-08-16 + Peter Baumann + + 17-089r1 + WCS Core 2.1 + OGC Web Coverage Service (WCS) 2.1 Interface Standard - Core + The OGC Web Coverage Service (WCS) supports electronic retrieval of geospatial data as coverages. Coverages are digital geospatial information representing space/time-varying phenomena, specifically spatio-temporal regular and irregular grids, point clouds, and general meshes. +This document specifies the WCS core. Every implementation of a WCS shall adhere to this standard. This standard defines core requirements. Extensions to the core define extensions to meet additional requirements, such as the response encoding. Additional extensions are required in order to completely specify a WCS for implementation. +This WCS 2.1 standard extends WCS 2.0 in a backwards compatible manner by accommodating coverages as per the OGC Coverage Implementation Schema (CIS) 1.1 in addition to CIS 1.0 coverages as addressed by WCS 2.0. + - - July 2021 OGC API Code Sprint Summary Engineering Report - 21-055 - - Gobe Hobona, Joana Simoes - The subject of this Engineering Report (ER) is a virtual code sprint that was held from July 21st to July 23rd, 2021 to advance the development of the OGC API - Processes draft standard, OGC API - Records draft standard, and the OGC API – Coverages draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). - - - 12-132r4 - Augmented Reality Markup Language 2.0 (ARML 2.0) - Martin Lechner - 12-132r4 - - 2015-02-24 - + 17-089r1 + + + + 19-019 + OGC Testbed-15: Portrayal Summary ER + + OGC Testbed-15: Portrayal Summary ER + + 19-019 + - OGC Augmented Reality Markup Language 2.0 (ARML 2.0) - - This OGC® Standard defines the Augmented Reality Markup Language 2.0 (ARML 2.0). ARML 2.0 allows users to describe virtual objects in an Augmented Reality (AR) scene with their appearances and their anchors (a broader concept of a location) related to the real world. Additionally, ARML 2.0 defines ECMAScript bindings to dynamically modify the AR scene based on user behavior and user input. + + + Martin Klopfer + This OGC Engineering Report provides an executive summary of the Open Portrayal Framework (OPF) Thread in OGC Testbed-15. The work in this testbed occurred between April and November 2019. Full details of the requirements, high-level architecture, and solutions are provided in the following Engineering Reports: + +OGC Testbed-15: Styles API Draft Specification Engineering Report + +OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report + +OGC Testbed-15: Maps and Tiles API Draft Specification Engineering Report + +OGC Testbed-15: Images and Change Sets Draft Specification Engineering Report + +OGC Testbed-15: Open Portrayal Framework Engineering Report + 2020-02-07 - - - 15-113r6 - Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure + + 15-028 + Daniel Balog + + OGC® Testbed 11 Data Broker Specifications Engineering Report + 15-028 + Testbed 11 Data Broker Specifications Engineering Report + - - Carl Reed + - 2021-02-26 - The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. - + 2015-08-19 - 15-113r6 - Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure + This document is a deliverable of the OGC Testbed 11 Interoperability initiative. The report’s contents cover the summary of the interoperability work regarding the Aviation Data Broker concept. This data broker concept enables the setup of cascading OGC Web Feature Server (WFS) servers to form a data source chain, in which one service is capable of providing information coming from one or more other services. The objectives of this document are to research the feasibility of this concept and to investigate a number of specific Data Broker responsibilities and use cases, such as provenance and lineage, conflation, caching, scalability and flexible management of data sources. - - Alexandre Robin - SWE Common Data Model Encoding Standard - 08-094r1 - 2011-01-04 - 08-094r1 + + Web Coverage Service (WCS) Implementation Specification (Corrigendum) + 05-076 + - - This standard defines low level data models for exchanging sensor related data between nodes of the OGC® Sensor Web Enablement (SWE) framework. These models allow applications and/or servers to structure, encode and transmit sensor datasets in a self describing and semantically enabled way. - OGC® SWE Common Data Model Encoding Standard - + John Evans + 2006-03-31 + - + OpenGIS Web Coverage Service (WCS) Implementation Specification (Corrigendum) + + 05-076 + Extends the Web Map Server (WMS) interface to allow access to geospatial coverages that represent values or properties of geographic locations, rather than WMS generated maps (pictures). + +The original document is available at: http://portal.opengeospatial.org/files/?artifact_id=3837 - - 09-006 - OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS - 09-006 - This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the development of SOAP/XML and REST interfaces for the Web Map Tiling Service (WMTS). - 2009-08-05 - + + 11-061r1 + 11-061r1 + OWS-8 AIXM Metadata Guidelines Engineering Report + - + + 2012-02-09 - + David Burggraf + OWS-8 AIXM Metadata Guidelines Engineering Report - Keith Pomakis - OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS + + This OGC® Engineering Report provides guidelines for ISO metadata usage in AIXM 5.1 +conformant to the requirements of OGC 10-195 (Requirements for Aviation Metadata) +and the recommendations of OGC 10-196r1 (Guidance on the Aviation Metadata +Profile), with the exception of non-ISO metadata elements listed in these documents. - - - + + 08-091r6 + 08-091r6 + Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0 - - David Graham - - 15-004 - OGC Common DataBase Volume 2 Appendices - 2015-07-22 - - Common DataBase Volume 2 Appendices - 15-004 - The Common DataBase (CDB) Specification provides the means for a single, versionable, simulation-rich, synthetic representation of the earth. A database that conforms to this Specification is referred to as a Common DataBase or CDB. A CDB provides for a synthetic environment repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB can be used as a common on-line (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks; in this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. -The application of CDB to future simulator architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the HLA/FOM and DIS protocols, the application of the CDB Specification provides a Common Environment to which inter-connected simulators share a common view of the simulated environment. -The CDB Specification is an open format Specification for the storage, access and modification of a synthetic environment database. The Specification defines the data representation, organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The Specification makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. -The CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. It encompasses the terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the synthetic environment includes the specific attributes of the synthetic environment data as well as their relationships. -A CDB contains datasets organized in layers, tiles and levels-of-detail; together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB is specifically tailored for real-time applications. - - - - OpenSearch Extension for Earth Observation Satellite Tasking: Best Practice - 13-039 - - - - 13-039 - OGC® OpenSearch Extension for Earth Observation Satellite Tasking: Best Practice - 2014-12-29 - - This document provides a specification of an OpenSearch extension for Earth Observation Satellites Tasking. - -This OGC Best Practice is intended to provide a very simple way to task Earth Observation (EO) satellites sensors, to allow simple syndication between, and to provide a basic federated query of related sensors, whereby a single client can query several instances and present a collection of future acquisition as one set. - -This document is the result of work undertaken within the European Space Agency (ESA) Heterogeneous Mission Accessibility for Science (HMA-S) project funded by ESA the Long Term Data Preservation (LTDP) program. - -The document was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative (see ‘Normative References’ section) related projects. - Nicolas Fanjeau, Sebastian Ulrich - + + + + + 2009-09-16 + Peter Schut + Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0 + This document provides the details for a corrigendum for the existing OpenGIS Standard for the Web Processing Service version 1.0.0 and does not modify that standard. The current OpenGIS Implementation Standard that this document provides revision notes for is 05-007r7. - - John Herring + + + Vector Tiles Pilot Extension Engineering Report + - - 2007-01-29 - The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. + Jeff Yutzler + + Vector Tiles Pilot Extension Engineering Report + 18-101 + The purpose of the OGC Vector Tiles Pilot Extension (VTPExt) was to address portrayal and style encoding concerns that were discovered in the initial phase of the Vector Tiles Pilot (VTP). During the VTPExt, participants selected a common baseline style used by all participants and in some cases created additional style offerings. The work conducted during the VTPExt has adhered to the established findings from the initial VTP documented in the VTP Summary Engineering Report (ER) [1]. -Part 1 “Common Architecture supplies the common feature model for use by applications that will use the Simple Features data stores and access interfaces. +This document describes the following: -Part 2 provides a standard SQL implementation of the abstract model in Part 1. (Note: The OpenGIS® Simple Features Interface Standards for OLE/COM and CORBA are no longer current and are not provided here.) +the research and evaluation to determine approach(es) to apply styling to Mapbox and GeoJSON Tiled Feature Data through Web Feature Service (WFS) 3.0, Web Map Tile Service (WMTS) 1.0, and GeoPackage (GPKG) 1.2, -The corresponding standard for the Web is the OpenGIS® Web Feature Service Interface Standard http://www.opengeospatial.org/standards/wfs. - - Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option - 06-104r3 - 06-104r3 - OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option - - +the styling approach, challenges, and interoperability considerations discovered during the initiative, and + +any extensions required or best practices recommended to facilitate development, encoding, offering, and exchange of styles. This includes how styles are offered from servers, how the desired style offering can be selected by the client from multiple server style offerings (e.g. GetStyles request), and how clients can apply their own styles. + - + 2019-04-30 + 18-101 - + + - + + OGC OWS Context GeoJSON Encoding Standard + OWS Context GeoJSON Encoding Standard + 14-055r2 + 14-055r2 + - GeoSciML is a model of geological features commonly described and portrayed in geological maps, cross sections, geological reports and databases. The model was developed by the IUGS CGI (Commission for the Management and Application of Geoscience Information) and version 4.1 is the first version officially submitted as an OGC standard. This specification describes a logical model and GML/XML encoding rules for the exchange of geological map data, geological time scales, boreholes, and metadata for laboratory analyses. It includes a Lite model, used for simple map-based applications; a basic model, aligned on INSPIRE, for basic data exchange; and an extended model to address more complex scenarios. + + 2017-04-07 + This standard describes the GeoJSON encoding of the OGC Web Services (OWS) Context conceptual model. This standard defines how to encode an OWS context document that 1.) can be extended to allow a context referencing a fully configured service set, and 2.) can be defined and consistently interpreted by clients. +The OWS Context Document standard (OWS Context) was created to allow a set of configured information resources to be passed between applications primarily as a collection of services (but also potentially in-line content). The objective is to support use cases such as the distribution of search results, the exchange of a set of resources in a Common Operating Picture (COP), or delivery of a set of configured processing services to allow the processing to be reproduced on different processing nodes. +The goal for OWS Context is to replace previous OGC standards and best practices that provide similar capability. Web Map Context (WMC) has been reasonably successful but is limited to working with only Web Map Service (WMS) instances. Other work on the Location Organizer Folder1 (LOF) was also taken into consideration. The concept of OWS Context and the first prototype document was produced as part of OWS Testbed 7 and documented in [OGC10-035r1], Information Sharing Engineering Report. +A principal goal of the OWS Context SWG was to develop encodings that would appeal for use in mass market applications yet also provide facilities for more advanced uses. OWS-7 originally considered the application of existing encoding standards for OWS Context. The OGC Standards Working Group (SWG) has concluded that this standard can have multiple encoding formats and that each encoding format will be described in a separate OGC Extension to the Core model. + + Pedro Gonçalves, Roger Brackin + + + OGC Testbed-15: Federated Clouds Analytics Engineering Report + 19-026 + 2019-12-19 + This OGC Engineering Report (ER) documents the results and experiences resulting from the Federated Cloud Analytics task of OGC Testbed-15. More specifically, this ER provides an analysis of: -The specification also provides patterns, profiles (most notably of Observations and Measurements - ISO19156), and best practices to deal with common geoscience use cases. +The potential for the OGC Web Processing Service (WPS) Interface Standard as an Application Programming Interface (API) to a workflow automation service for managing job execution involving multiple containers in the Scale Data Center Environment; - +Using an implementation of the OGC WPS standard as a general frontend to workflow automation with containers; + +The suitability of the OGC WPS 2.0 standard as an API for Cloud analytics; + +Using OGC Web Services (WS) as analytics data sources and sinks. + + + + + Pedro Gonçalves + 19-026 - - Geoscience Markup Language 4.1 (GeoSciML) - with Corrigendum - 16-008r1 - GeoSciML Modeling Team - OGC Geoscience Markup Language 4.1 (GeoSciML) - with Corrigendum - 2017-01-31 - 16-008r1 + OGC Testbed-15: Federated Clouds Analytics Engineering Report - + + + 2006-12-26 + The OpenGIS® Catalogue Service Interface Standard 2.0.1 - FGDC CSDGM Application Profile for CSW 2.0 explains how Catalogue Services based on the FGDC Content Standard for Digital Geospatial Metadata (CSDGM) [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html] Application Profile for the OpenGIS® Catalogue Service Interface Standard v2.0.1 [http://www.opengeospatial.org/standards/cs] are organized and implemented for the discovery, retrieval and management of data metadata. + 06-129r1 + FGDC CSDGM Application Profile for CSW 2.0 + + FGDC CSDGM Application Profile for CSW 2.0 + Patrick Neal, John Davidson, Bruce Westcott + 06-129r1 - 2010-06-04 - The Architecture, Engineering, Construction, Owner Operator, Phase 1 (AECOO-1) Testbed developed and implemented methods to streamline communications between parties in the conceptual design phase to get an early understanding of the tradeoffs between construction cost and energy efficiency. To that end, the project developed the interoperability components required for these analyses in collaborative team settings. These were Information Delivery Manuals (IDMs) for quantity takeoffs and energy analysis business processes, and used these to define Model View Definitions (MVDs)—standards-based subsets of Industry Foundation Classes (IFCs). AECOO-1 was conducted in response the felt need that overall productivity loss and fragmentation in the capital facilities development industries is no longer tolerable. All stakeholders need to practice the best way they know, and practice profitably; software interoperability problems must not hold them back. Non-interoperable software and data is cause for loss of competition across the market. - - Summary of the Architecture, Engineering, Construction, Owner Operator Phase 1 (AECOO-1) Joint Testbed - 10-003r1 - Summary of the Architecture, Engineering, Construction, Owner Operator Phase 1 (AECOO-1) Joint Testbed - 10-003r1 - Louis Hecht, Jr., Raj Singh - - - 13-011 - OWS-9: Summary of the OGC Web Services, Phase 9 (OWS-9) Interoperability Testbed - - This report summarizes the results of OGC Web Services Initiative, Phase 9 (OWS-9). - Nadine Alameh - + + 22-025r4 + 3D Tiles Specification + + 22-025r4 + + 2023-01-12 + + Patrick Cozzi, Sean Lilley - - OWS-9: Summary of the OGC Web Services, Phase 9 (OWS-9) Interoperability Testbed - 13-011 - - 2013-04-02 - - - - Clemens Portele, Rafael Renkert - OGC Web Services (OWS) 3 UGAS Tool - This document contains a description of the UGAS (UML Application Schema to GML ApplicationSchema conversion) tool development in the decision support services thread (GeoDSS) during the OWS-3 initiative. + 3D Tiles Specification - - - - 2006-04-28 - OGC Web Services (OWS) 3 UGAS Tool - 05-118 - - 05-118 + This document describes the specification for 3D Tiles, an open standard for streaming massive heterogeneous 3D geospatial datasets. - - This document reviews the material discussed during the OWS-4 project, describes the WPS processes deployed in the workflows, and offers suggestions to the OGC to move forward with the WPS. - - 06-182r1 - 2007-06-06 - Discussions, findings, and use of WPS in OWS-4 - 06-182r1 - Steven Keens - - - - Discussions, findings, and use of WPS in OWS-4 + + This document specifies a rule for constructing OGC names that may be used for identifying definitions of sensor models and their parameters. This document is formally a profile of the OGC policy 'OGC-NA Name type specification - definitions: Part 1 - basic name' (OGC 09-048r5). + OGC Name Type Specification - Sensor Models and Parameters + + Gobe Hobona, Simon Cox + 2019-10-31 + 18-042r4 + Name Type Specification - Sensor Models and Parameters + + + + 18-042r4 - - This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 8 (OWS-8). It describes the results of the conceptual and schematron rule based validation of the Digital NOTAM Event Specification (DNES). Various conceptual aspects were identified which need clarification and/or revision. Schematron rules were developed for a number of the DNES scenarios. This document contains coverage tables which document normative statements from the DNES and indicate which of them can be tested with existing schematron rules. -See: <a href=http://dp.schemas.opengis.net/11-092r2>http://dp.schemas.opengis.net/11-092r2</a> - - OWS-8 Report on Digital NOTAM Event Specification - 11-092r2 - 11-092r2 - OWS-8 Report on Digital NOTAM Event Specification - Johannes Echterhoff, Matthes Rieke + - - + 2011-07-14 + 11-013r6 + Water Information Services Concept Development Study + + 11-013r6 + OGC® Engineering Report: Water Information Services Concept Development Study + + The purpose of this report is to recommend appropriate architectures and procedures for migrating the CUAHSI HIS to the OGC-based WaterML 2.0 encoding (profile of OGC O&M standard) and OGC web services such as Sensor Observation Service (SOS), Web Feature Service (WFS), Web Mapping Service (WMS), Web Coverage Service (WCS), and Catalogue Service for the Web (CSW). This report may be used as the basis for future OGC Interoperability Program initiatives. - 2012-04-04 + Luis Bermudez, David Arctur + - - 10-025r1 - Observations and Measurements - XML Implementation + + + + + + + Minimal Application Profile for EO Products + 05-057r3 + Minimal Application Profile for EO Products + 2006-02-09 + The services proposed in this profile are intended to support the identification and subsequent ordering of +EO data products from previously identified data collections. The intent of this initial profile is to +describe a minimum interface that can be supported by many data providers (satellite operators, data +distributors + 05-057r3 + Jolyon Martin - + + + 2007-08-27 + + 06-189 - 2011-03-22 - Simon Cox - - This standard specifies an XML implementation for the OGC and ISO Observations and Measurements (O&M) conceptual model (OGC Observations and Measurements v2.0 also published as ISO/DIS 19156), including a schema for Sampling Features. This encoding is an essential dependency for the OGC Sensor Observation Service (SOS) Interface Standard. -More specifically, this standard defines XML schemas for observations, and for features involved in sampling when making observations. These provide document models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities. - - 10-025r1 - Observations and Measurements - XML Implementation + + This document provides the details for a corrigendum for the existing OpenGIS Implementation Specification for the Geography Markup Language version 2.1.2 and does not modify that implementation specification. The current OpenGIS Implementation Specification that this document provides revision notes for is 02-069. + 06-189 + Corrigendum 1 (one) for OpenGIS Implementation Specification GML 2.1.2 + Corrigendum 1 (one) for OpenGIS Implementation Specification GML 2.1.2 + Chris Holmes + + - - Terry Idol, Robert Thomas - Development of Disaster Spatial Data Infrastructures for Disaster Resilience - 18-087r5 - + + + OGC Testbed-14: MapML Engineering Report - 18-087r5 - + + 2019-03-06 + This is the second Engineering Report (ER) about the Map Markup Language (MapML) cite:[Rushforth2018] resulting from OGC Testbed initiatives. To find an introduction of MapML and how it works, please, refer to the previous ER OGC 17-019 cite:[Maso2018]. MapML is a new media type that can be included in a <layer> element of a <map> section, in a Hypertext Markup Language (HTML) page. This document is mainly focused on the description of the MapML media type and its evolutions. In particular, it considers issues about the Coordinate Reference System (CRS) types in MapML, feature and properties encoding, Cascading Style Sheets (CSS) symbolization, multidimensional data etc. + +This document describes two implementations done in OGC Testbed-14: a Cloud-based Proxy (cascade) for MapML done by CubeWerx and a ServiceWorker Proxy for MapML done by George Mason University (GMU). + +Finally, this document reviews how the next generation of OGC services can integrate MapML files as part of the designing of use cases and discusses how MapML can be used by social media. + +This document proposals increases functionality in MapML and makes proposals for increasing the interoperability of the proposed encoding with the OGC standards baseline and future generations of OGC standards for maps and tiles. + 18-023r1 + MapML Engineering Report + 18-023r1 - 2018-12-18 - - OGC Development of Disaster Spatial Data Infrastructures for Disaster Resilience - This report presents the results of a concept development study on Disasters Interoperability, sponsored by US Geological Survey (USGS) and Federal Geographic Data Committee (FGDC), and Department of Homeland Security (DHS), and executed by the Open Geospatial Consortium (OGC). The focus of this study was to understand how to best support the development of, or combination of SDI(s) for the use in disasters, to advance the understanding of stakeholder issues, and serve stakeholders’ needs. The study included stakeholder engagements, workshops and open Request for Information (RFI) that gathered external international positions and opinions on the optimal setup and design of an SDI for disasters. The outflow of this report will guide a series of interoperability pilots to address priority challenges identified by the community in this study. The report follows the format and document of the OGC Arctic Spatial Data Pilot; Phase 1 Report: Spatial Data Sharing for the Arctic. + Joan Masó + - - 03-053r1 - OGC Technical Document Baseline - Spreadsheet of OGC Technical Document Baseline - OGC Technical Document Baseline - 2003-05-22 - - Carl Reed, George Percivall + + 07-152 + FedEO Pilot Engineering Report (07-152) + + + 07-152 + 2008-01-21 + FedEO Pilot Engineering Report + This document was developed during the FedEO - GEO AIP initiative of the OGC. It was contributed by the organizations involved in the Earth Observation and Natural Resources and Environment Domain Working Group (EO/NRE DWG) in the OGC Specification Program. The document describes recommendation for architecture and specification that enables interoperability + Corentin Guillo + + - + + + 09-166r2 + Web View Service Discussion Paper + + + + Web View Service Discussion Paper - 03-053r1 - + + Benjamin Hagedorn + 09-166r2 + 2010-02-01 + + The Web View Service (WVS) is an extendable, interactive, image-based portrayal service for complex three-dimensional geodata such as 3D landscape and city models. 3D geodata is delivered as finally rendered images. Besides color images, relevant thematic and geometrical information such as object identity information or depth data is provided. Additionally, the WVS supports interaction with the portrayed 3D environment, e.g., information retrieval, spatial analysis, and 3D navigation. - - 2022-08-19 - OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum - 07-045r2 - Catalogue services are the key technology for locating, managing and maintaining -distributed geo-resources (i.e. geospatial data, applications and services). With OGC -catalogue services, client applications are capable of searching for geo-resources in a -standardized way (i.e. through standardized interfaces and operations) and, ideally, they -are based on a well-known information model, which includes spatial references and -further descriptive (thematic) information that enables client applications to search for -geo-resources in very efficient ways. -Whereas interfaces and operations of OGC catalogue services are well defined, it is left -up to the developer of the system to define a specific information model which a -catalogue service instance provides. This includes, but is not limited to, the information -which can be inserted in the catalog, supported query languages, available search terms, -response/result sets, etc. This point is of major importance with respect to interoperability -between different catalogue service instances. -In Europe, running catalogue instances result from work being done within different SDI -initiatives (e.g. SDI NRW Initiative1, Germany/Netherlands cross-border initiative, JRC -EU Portal, EUROSTAT, Inspire, German SDI initiative). Members of these initiatives -have developed an ISO-based application profile for ISO19115 metadata for -geodata/geospatial applications and ISO19119-based metadata for tightly and looselycoupled -geospatial services. The foundations of this profile were the OGC catalogue -specification (1.1.1), the OGC Web Registry Server (WRS) 0.0.2, OGC Web Services -Stateless Catalogue Profile (StCS) 0.0.6 and ISO 19115/19119 for content description. -OGC's catalogue revision working group (CS-RWG) has revised and integrated the -catalogue implementation specification v1.1.1 that have resulted in CS 2.0.2. One part of -this OGC specification comprises the definition of application profiles according to ISO -19106 (Geographic information – Profiles). The overall goal of these profiles is to -improve interoperability between systems conforming to a specific profile. Experience -has shown that the need for application profiles results from the fact that in practice, there -is no single solution for catalogue services that fits every user’s needs. As stated in CS -2.0.2, a base profile that provides a basic set of information objects has to be supported -by each catalogue instance; in addition, application profiles for different information -communities can be specified. -Hence, this document specifies an application profile for ISO 19115:2003/ISO -19119:2005 metadata with support for XML encoding per ISO/TS19139:2007 [ISO/TS19139]2 and HTTP protocol binding. It relies on requirements coming from the -CS/CSW 2.0 specification (OGC CS 2.0.2, OGC document 07-006). The application -profile will form the basis of conformance tests and reference implementations. - + + + The OGC Catalogue Services 2.0 specification (OGC 07-006r1) establishes a general framework for implementing catalogue services that can be applied to meet the needs of stakeholders in a wide variety of domains. +The ebRIM application profile (OGC 07-110r4) is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0 specification; it qualifies as a ‘Class 2’ profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards. The ebRIM application profile also includes a Basic extension package (OGC 07-144r4) of the OASIS ebXML Registry Information Model (ebRIM) providing artefacts of general utility in the geomatics domain. +This document provides an extension package aligned with the ebRIM application profile of CS-W for the cataloguing of ISO 19115, ISO19115-2 and ISO 19119 compliant metadata. It was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [HMA] and related projects. Some input came from the OGC OWS9 initiative. +This document supersedes the former document OGC Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W, OGC 07-038r3 (Version: 0.1.12). + + I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0 + 13-084r2 + Uwe Voges, Frédéric Houbie, Nicolas Lesage, Marie-Lise Vautier + 2014-04-28 + 13-084r2 + - Uwe Voges, Kristian Senkler - OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum - - - 07-045r2 + + OGC I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0 - - 2020-03-26 - Time Ontology in OWL - 16-071r3 - + + 2002-04-18 + 01-068r3 - 16-071r3 - - - + + Web Map Service + 01-068r3 + Web Map Service - Simon Cox, Chris Little - Time Ontology in OWL - OWL-Time is an OWL-2 DL ontology of temporal concepts, for describing the temporal properties of resources in the world or described in Web pages. The ontology provides a vocabulary for expressing facts about topological (ordering) relations among instants and intervals, together with information about durations, and about temporal position including date-time information. Time positions and durations may be expressed using either the conventional (Gregorian) calendar and clock, or using another temporal reference system such as Unix-time, geologic time, or different calendars. - - + Provides three operations protocols (GetCapabilities, GetMap, and GetFeatureInfo) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. + + + + Jeff de La Beaujardiere - - - Peter Taylor - WaterML2.0 - part 2: Ratings, Gaugings and Sections Discussion Paper - 13-021r3 + + OGC Aviation Domain Working Group + Guidance on the Aviation Metadata Profile + 10-196r1 + 10-196r1 + 2011-03-28 - This document describes an information model for exchanging rating tables, or rating -curves, that are used for the conversion of related hydrological phenomenon. It also -describes a model describing the observations that are used to develop such relationships, -often referred to as gauging observations. -The information model is proposed as a second part of the WaterML2.0 suite of -standards, building on part 1 that addresses the exchange of time series1. - 2013-06-18 - + - 13-021r3 - WaterML2.0 - part 2: Ratings, Gaugings and Sections Discussion Paper + Guidance on the Aviation Metadata Profile + This paper explains how to map the Requirements for Aviation Metadata into a metadata profile. + - - - 18-074 - GeoPackage 1.2 Vector Tiles Extensions Engineering Report - 18-074 - Tiled feature data, colloquially referred to as 'vector tiles', can be used to optimize the delivery of vector data over the web. This data may subsequently be used to support visualization (particularly through maps) as well as limited analysis activities. One goal of the OGC Vector Tiles Pilot was to define candidate extensions to existing OGC standards as a way to advance the use of vector tiles technology as part of the OGC baseline. This Engineering Report (ER) describes a set of possible extensions to GeoPackage 1.2 that documents the mechanism to store and retrieve vector tiles in a GeoPackage. These extensions work together to enable a GeoPackage to act as a container format that can support visualization and analysis activities, even in a Denied, Degraded, Intermittent, or Limited Bandwidth (DDIL) environment. - -The GeoPackage Vector Tiles extensions define the rules and requirements for encoding vector tiles in a GeoPackage data store. There are five draft extensions: - -The Vector Tiles Extension provides vector tiles support through the GeoPackage tiles option. - -The Mapbox Vector Tiles Extension allows the content of a tile Binary Large OBject (BLOB) to be a Mapbox Vector Tile as per version 2.1 of the Mapbox Vector Tile (MVT) specification [1]. - -The GeoJSON Vector Tiles Extension allows the content of each tile BLOB to be a GeoJSON file. - -The OGC Web Services (OWS) Context Extension provides a way to store information describing a list of geospatial resources, including but not limited to maps, their layers, and the styles of those layers. - -The Vector Tiles Attributes Extension allows attribute information for each feature to be stored in relational tables for more convenient querying. - -To support vector tiles, a minimum of at least two extensions is required. The first extension enables vector tiles support. However, to be usable, an encoding format must be declared via either the second or third extension. The other extensions are purely optional. - -These extensions, like all GeoPackage extensions, are intended to be transparent and to not interfere with GeoPackage-compliant, but non-supporting, software packages. + + + 17-079r1 + SensorThings API Part 2 – Tasking Core + Steve Liang, Tania Khalafbeigi + 17-079r1 + + 2019-01-08 + OGC SensorThings API Part 2 – Tasking Core + The OGC SensorThings API [OGC 15-078r6] provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the Web. At a high level, the OGC SensorThings API provides two main functions and each function is handled by the Sensing part or the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. The Tasking part provides a standard way for parameterizing - also called tasking - of taskable IoT devices, such as individual sensors and actuators, composite consumer / commercial / industrial / smart cities in-situ platforms, mobile and wearable devices, or even unmanned systems platforms such as drones, satellites, connected and autonomous vehicles, etc. This document specifies core of the SensorThings Tasking part. - - - - OGC Vector Tiles Pilot: GeoPackage 1.2 Vector Tiles Extensions Engineering Report - 2019-02-15 - Jeff Yutzler - - + - - This document describes the 3D portrayal server components which were used in the OGC OWS-6 Decision Support Systems (DSS) thread. The objective pf this activity was to efficiently stream and display GML 3 content in internet or wireless networks with limited bandwidth, especially focusing on the CityGML application profile. The server for delivering landscape and city models is implemented as Web 3D Service (W3DS) that is designed as portrayal service. + + + Web Coverage Service + 02-024 + + 02-024 + 2002-06-30 + + - 09-075r1 - OWS-6 3D Flythrough (W3DS) Engineering Report - - - Arne Schilling - OWS-6 3D Flythrough (W3DS) Engineering Report - - 09-075r1 - 2009-08-05 + John Evans + + Extends the Web Map Server (WMS) interface to allow access to geospatial coverages that represent values or properties of geographic locations, rather than WMS generated maps (pictures). + + Web Coverage Service - - Benjamin Pross - 2017-05-12 - Testbed-12 Low Bandwidth & Generalization Engineering Report - 16-021r1 + + 2005-06-17 + + 05-036 + + GeoXACML, a spatial extension to XACML + 05-036 + + This OGC document proposes one possible solution for the declaration and enforcement of access +restrictions for object-oriented geodata, available through a Service-based Geo Data Infrastructure. It is the +intension of the author to motivate the requirement for such an access control, give a problem statement, +discuss an alternative approach and describe the solution, based on GeoXACML. + + Andreas Matheus + GeoXACML, a spatial extension to XACML - - 16-021r1 - - - - For delivering of data that is offered by OGC services over (very) low bandwidth, two options may be considered: On the one hand, the geospatial features remain the same, but compression techniques are used to reduce the size of the data that needs to be transferred. On the other hand, generalization techniques may be used by reducing the details of geometries and/or attributes in order to reduce the amount of data. The aim of this ER is to summarize the results of implementing sample services using compression techniques for DGIWG WFS (U002) and providing generalization processes using WPS (U003). The ER compares the results of the different approaches and infers recommendations and best practices for supporting data delivery of standard data and complex 3D data from OGC services over low and very low bandwidth. - Testbed-12 Low Bandwidth & Generalization Engineering Report - - - - - - - - - - - - - - - - - - - - - - - + + 04-088 + EA-SIG Mediation White Paper + + Paul Lunceford,Steve Matney,Tom Huggins,Chuck Heazel + *RETIRED* This document focuses on the goals, objectives, capabilities and recommendation for the Mediation Core Enterprise +Service. + EA-SIG Mediation White Paper + 04-088 + + + 2004-02-20 - Documents of type Retired Specification - Documents of type Retired Specification - Documents of type Retired Specification - + + - - - 2013-09-11 - George Percivall + + Simon Cox + Name type specification – ontology resources + 12-081 + + - 13-032 - SWE Implementation Maturity Engineering Report - This report summarizes the outcomes of a process to assess the maturity of implementations based on SWE standards. This report covers the following areas: -• SWE standards overview -• Implementations of SWE in major systems -• SWE software implementations and compliance -• SWE implementations in IP -• Recommendations and Observations -A main outcome is the summary assessment of the SWE Implementation Maturity as presented in the Preface based on the body of the report. - - + + 12-081 + Name type specification – ontology resources + 2013-06-18 + An OGC name is required for ontology resources published by OGC. This includes OWL +ontologies, classes and properties. + + + - - 13-032 - OGC® SWE Implementation Maturity Engineering Report + WCS 2.0 Interface Standard - Core + 09-110r3 + + 09-110r3 + + OGC® WCS 2.0 Interface Standard - Core + 2010-10-27 + + This document specifies how a Web Coverage Service (WCS) offers multi-dimensional coverage data for access over the Internet. This document specifies a core set of requirements that a WCS implementation must fulfil. WCS extension standards add further functionality to this core; some of these are required in addition to the core to obtain a complete implementation. This document indicates which extensions, at a minimum, need to be considered in addition to this core to allow for a complete WCS implementation. + Peter Baumann + + - - Sensor Collection Service - 02-028 - 2002-04-19 - The basic function of the Sensor Collection Service (SCS) is to provide a web-enabled interface to a sensor, collection of sensors or sensor proxy. Sensors are defined as devices that measure physical quantities. + + This document provides an overview of the portrayal work within the OWS-9 Aviation thread. Using open standards, a web services architecture was designed and prototyped to enable the retrieval of static airport maps in support of an ePIB. An ePIB, or Digitally Enhanced Pre-Flight Information Bulletin, provides the pilot with an easy-to-interpret representation of any relevant aeronautical and meteorological events that are likely to affect the flight, expressed as Digital NOTAMs. The static airport maps are an important part of an ePIB and should provide a graphical representation of the status of departure and arrival airports, showing only NOTAMs relevant to the particular context and represented geographically so that the effect of the NOTAM is clear. This approach avoids the pilot scanning through pages of textual description for potentially relevant NOTAMs, reducing the workload and the risk of missing a critical piece of information. + OWS-9 Aviation Portrayal Engineering Report + + + Daniel Balog, Roger Brackin, Robin Houtmeyers + + OWS-9 Aviation Portrayal Engineering Report + 12-151 + 12-151 - - 02-028 - - - Sensor Collection Service - - Tom McCarty + + 2013-02-06 - - Topic 00 - Overview - 04-084r4 - - 2020-08-27 - This document (Topic 0) is an overview of the OGC Abstract Specification. + - + Topic 11 - Metadata + + 11-111r1 + Same as ISO 19115-1:2014. Abstract Specification Topic 11 was updated to the latest version of the ISO metadata standard on 21 September 2016. Prior to this date, this Topic was the same as ISO 19115:2003. Please note that many OGC standards and other related work normatively refer to the previous version of this Topic. - 04-084r4 + + Topic 11 - Metadata + 11-111r1 + + 2016-09-16 + ISO - George Percivall - - Topic 0 - Overview - - This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the extension of the OGC Styled Layer Descriptor (SLD) symbology format for improved capability and harmonization with ISO 19117 symbology, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology. - OWS-6 Styled Layer Descriptor (SLD) Changes ER - 09-015 - OWS-6 Styled Layer Descriptor (SLD) Changes ER + + 10-191r1 + Requirements and Space-Event Modeling for Indoor Navigation + + - - Craig Bruce + Claus Nagel, Thomas Becker, Robert Kaden, Ki-Joune Li, Jiyeong Lee, Thomas H. Kolbe + 10-191r1 + + This OpenGIS® Discussion Paper presents a Multilayered Space-Event Model for indoor navigation which simultaneously addresses route planning, multiple localization methods, navigation contexts, and different locomotion types. The paper contains the corresponding data models as well as their encoding in GML 3.1.1. + + + Requirements and Space-Event Modeling for Indoor Navigation + 2010-12-11 + + + + + 2016-03-24 + 12-028r1 + The document provides guidelines for the use of GML and a GML profile description in the +scope of aeronautical data encoding, in particular when using the Aeronautical Information +Exchange Model (AIXM). In the future, the applicability of the guidelines contained in this +document might be enlarged to cover other related domains, such as aeronautical weather data +and flight data. + + + Use of Geography Markup Language (GML) for Aviation Data + 12-028r1 + Use of Geography Markup Language (GML) for Aviation Data - - 2009-09-11 + OGC Aviation Domain Working Group - - 09-015 - - 14-115 - 2015-01-21 - This White Paper supports development of a Smart Cities Spatial Information Framework -based on these themes: -- Smart Cities are high-density generators of innovation and information. -- Location information is a major enabler of Smart City technology benefits. -- Benefits of smart technology must be judged by benefits to residents. -- Reuse and repurpose is vital to urban resilience -- Open standards are needed for interoperability, efficiency, application innovation -and cost effectiveness. -Discussion of these themes and this white paper will occur at the OGC Smart Cities -Location Powers Summit in Tokyo on December 2, 2014,1 the co-located OGC Technical -Committee meeting, and in many other forums in the future. As described in this paper, -there are many standards initiatives that focus on Smart Cities. Most Smart Cities use -cases in some way involve indoor and/or outdoor location, and thus communication about -location is an issue that cuts across the work programs most of the standards -organizations that are involved with Smart Cities. -This white paper builds on the OGC - Directions Magazine webinar: “Making Location -Work for Smart Cities – the Case for Location Standards”2. - This White Paper supports development of a Smart Cities Spatial Information Framework -based on these themes: -K Smart Cities are high-density generators of innovation and information. -K Location information is a major enabler of Smart City technology benefits. -K Benefits of smart technology must be judged by benefits to residents. -K Reuse and repurpose is vital to urban resilience -K Open standards are needed for interoperability, efficiency, application innovation -and cost effectiveness. -Discussion of these themes and this white paper will occur at the OGC Smart Cities -Location Powers Summit in Tokyo on December 2, 2014, -1 the co-located OGC Technical -Committee meeting, and in many other forums in the future. As described in this paper, -there are many standards initiatives that focus on Smart Cities. Most Smart Cities use -cases in some way involve indoor and/or outdoor location, and thus communication about -location is an issue that cuts across the work programs most of the standards -organizations that are involved with Smart Cities. -This white paper builds on the OGC - Directions Magazine webinar: “Making Location -Work for Smart Cities – the Case for Location Standards”2. - - + - OGC Smart Cities Spatial Information Framework - Smart Cities Spatial Information Framework - 14-115 + + This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for supporting other profiles for encoding definitions of Coordinate Reference Systems (CRSs) and Coordinate Operations. This profile can be used without a GML Application Schema, and such use is assumed in this document. + GML 3.1.1 CRS support profile + 05-094r1 + GML 3.1.1 CRS support profile + 05-094r1 + Arliss Whiteside + 2006-07-18 + + - - George Percivall - - OGC Smart Cities Spatial Information Framework - - - OGC® PUCK Protocol Standard - 09-127r2 - 2012-01-25 + + 99-104 - 09-127r2 - Tom O’Reilly + 99-104 + Topic 04 - Stored Functions and Interpolation + + + 1999-03-30 + Cliff Kottman + + This Topic Volume provides essential and abstract models for technology that is used widely across the GIS landscape. Its first heavy use is expected to occur in support of Coverage specifications (see Topic 6, The Coverage Type). - This standard defines a protocol for RS232 and Ethernet connected instruments. PUCK addresses installation and configuration challenges for sensors by defining a standard instrument protocol to store and automatically retrieve metadata and other information from the instrument device itself. - OGC® PUCK Protocol Standard - - + Topic 4 - Stored Functions and Interpolation - + + 16-068r4 + Testbed-12 Vector Tiling Engineering Report + Testbed-12 Vector Tiling Engineering Report + + - The OGC Testbed 10 was an initiative of OGC’s Interoperability Program to collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. The majority of work for Testbed 10 was conducted between October 2013 and April 2014. - 2015-02-02 - 14-044 - 14-044 - Testbed 10 Summary Engineering Report - Lew Leinenweber - OGC® Testbed 10 Summary Engineering Report - - - + This OGC Testbed 12 Engineering Report discusses the topic of vector tiling. + +While tiling and the use of multiple levels of details are a proven technique for raster data, it is relatively new for vector data. This is due to the increased complexity for tiling vector data compared to raster tiling. Further, there is a lack of standardization on the topic. Yet vector tiles can provide the same benefits as for raster tiles: + +Services can easily cache tiles and return them upon request, without the need for any additional pre/post processing (assuming no geometry construction is needed in the server). Consequently, clients can request and receive tiles quickly, ensuring better user experience. + +Due to tiled, multileveled data representations, clients can better access the data most suitable for their current map location and scale. This avoids the need to load too much data, which can cause both excessive memory usage and network traffic resulting in reduced overall performance. + +An example of vector tiling that illustrates the impact of these benefits is the OpenStreetMap (OSM) data store, which includes over 30 GB of data with worldwide coverage consisting of millions of vector features. Loading and visualizing all the OSM data into an application would either result in a memory shortage or unacceptable performance. By means of vector tiling and the generation of multiple levels of detail, apps using OSM data can load such data sets very efficiently into applications. + +This Engineering Report (ER) focuses on the general aspects of vector tiling. One of the main goals is to characterize what vector tiling is and how it can be approached. Highlighted topics include tiling approaches and strategies, tiling schemes, data coherence, simplification, scalability and styling. With respect to tiling schemes, existing standards material related to raster tiling schemes is incorporated to align both topics and to maximize interoperability. This includes the Defence Geospatial Information Working Group (DGIWG) Web Map Tiling Standard (WMTS) profile and the National System for Geospatial-Intelligence (NSG) WMTS profile as defined by the U.S. National Geospatial-Intelligence Agency (NGA). + +The topic of implementing vector tiles using a tile encoding / storage format is not covered. A study of implementing vector tiles in OGC GeoPackage is part of a separate Engineering Report, OGC 16-067, that builds on the results of this ER. + + + 2017-06-16 + 16-068r4 + Daniel Balog, Robin Houtmeyers + - + + Christoph Stasch, Simon Jirka + Testbed-12 REST Architecture Engineering Report + 16-035 + 16-035 + REST interfaces facilitate the application of OGC standards in many novel application scenarios, e.g. implementing OGC clients on constrained devices, as they ease the implementation of service requests and simplify the interaction patterns. Thereby, REST serves as a complementary technology to the already existing SOAP/POX provided by most of the current OGC standards. This engineering report (ER) provides an overview on different REST service implementations in the Testbed-12 and in related activities. As a result, this ER can be used to develop recommendations on architecture guidelines for providing REST interfaces in the geospatial domain. - 18-035 - Semantically Enabled Aviation Data Models Engineering Report - This Engineering Report (ER) summarizes the OGC Testbed-14 findings and recommendations to “semantically enable” existing data and metadata models used in the aviation industry. Examples of such data and metadata models include Aeronautical Information Exchange Model (AIXM) [1], Weather Information Exchange Model (WXXM) [2], Flight Information Exchange Model (FIXM) [3],Web Service Description Document (WSDD), Service Description Conceptual Model (SDCM) [4]). These models use Linked Data standards to represent this information and aim to improve the search and discovery of services and information in the aviation domain using the System Wide Information Management (SWIM) environment. This report provides a review of the existing data models and explore different approaches to provide a semantic representation of the current metadata and data models used in the aviation domain. The ER also discusses the role and importance of the controlled vocabularies. - - 2019-02-07 - OGC Testbed-14: Semantically Enabled Aviation Data Models Engineering Report + + Testbed-12 REST Architecture Engineering Report + + 2017-05-12 + + + + Explains how Catalogue Services based on the HMA (Heterogeneous Earth Observation Missions Accessibility) Application Profile for the OGC Catalogue Services Specification v2.0.1 [OGC 04-021r3] are organized and implemented for the discovery, retrieval and management of Earth Observation products metadata. - Stephane Fellah + + Marc Gilles + + 2006-06-06 + + + 06-079r1 + EO Application Profile for CSW 2.0 + 06-079r1 + + EO Application Profile for CSW 2.0 + + + Glenn Laughlin + + + + + 23-027 + OGC Federated Marine Spatial Data Infrastructure Pilot 2023 - Connecting Land and Sea for Global Awareness + 23-027 + OGC Federated Marine Spatial Data Infrastructure Pilot 2023 - Connecting Land and Sea for Global Awareness + Rising sea levels together with increasing storm surges are amongst the most challenging issues for coastal communities in the context of global warming. The retreating ice sheets of the Circumpolar Arctic are a key contributor to sea level rise with consequences felt around the world. + +The Federated Marine Spatial Data Infrastructure (FMSDI) initiative is a key component of OGC and the Marine Domain Working Group. The program is designed to engage with stakeholders from the marine dataspace to identify opportunities to assist, improve, and scale out core business processes complemented by the OGC suite of standards and best practices. The FMSDI-2023 pilot represents the fourth phase of the program with a focus on the interface between land and sea. A primary goal of this pilot is to advance the FMSDI concept to increasing threats posed by climate change. + +The project is divided into three threads, each with application to distinct geographies. + +Thread 1: Digital Twin of Land and Sea Interfaces — Singapore +With approximately 30% of Singapore’s land mass being less than 5m above sea level, the seamless integration of land and marine data is integral to Singapore’s focus on coastal protection and climate resilience. The management of land and water is separated organizationally between the Singapore Land Authority (SLA) and the Maritime & Port Authority (MPA), respectively. Each agency is responsible for data assets specific to their jurisdiction presenting a challenge for cross-organizational concerns. This theme addresses the geospatial integration requirements through the development of a multi-dimensional Digital Twin of the Singapore coastline. + +Thread 2: Digital Arctic Connecting Land and Sea — Canada +This thread addresses the data integration issues in the context of Digital Twins for the Canadian Arctic. With the loss of sea ice, continuing ocean warming, stronger winds and currents, and accelerated shoreline erosion affecting Arctic communities, efficient data usage and analysis is of the utmost importance for Canada. +Figure 1 + +Thread 3: Integrating Land & Sea for Various Use Cases — Caribbean +This thread investigates how data developed primarily for navigation at sea can be used to better understand the opportunities in the Caribbean to support local capacity building and the application of marine data in expanded sea-land contexts. + +Approach + +The FMSDI 2023 pilot is managed through the OGC Collaborative Solutions and Innovation (COSI) Program. Each thread is a distinct project with a set of participants tackling specific use cases and scenarios important to the respective project sponsor. + +Weekly project meetings are scheduled to encourage collaboration between the participants and sponsors and provide checkpoints to ensure the project scope meets the sponsor’s expectations. + +The FMSDI 2023 pilot also features a series of persistent demonstrators as one of its outputs. These demonstrators are workflows and applications that stakeholders can access for outreach, testing, and experimentation purposes. The demonstrators will be available even after the project is completed and are therefore referenced as persistent, but will only be available until December 2024. These demonstrators showcase how geospatial data can be used in an operational context or highlight the gaps in the resources available online, including data sources, metadata, access processes, and standards. As each participant has a unique solution platform, each has taken different approaches, all of which are available for review by stakeholders. Security concerns, such as authentication and authorization, are unique to each participant and have been communicated to stakeholders and participant contacts. For further details and access to the demonstrators, please refer to the link provided. + +Common across the three threads is the application of the OGC FAIR principles — Findable, Accessible, Interoperable, and Reusable. Underpinning the use of the FAIR principles is the role of the core OGC Standards and Best Practices. Previous work products related to FMSDI form the core information model while the OGC standards, enhanced through the alignment and support of industry standards such as the IHO S-100 standard, address many of the requirements central to each thread. + +Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights. + +Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which the recipients may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation. + 2024-04-26 + - 18-035 - - - - 2009-09-16 - Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0 - 08-091r6 - Peter Schut - This document provides the details for a corrigendum for the existing OpenGIS Standard for the Web Processing Service version 1.0.0 and does not modify that standard. The current OpenGIS Implementation Standard that this document provides revision notes for is 05-007r7. - 08-091r6 - + + Uwe Voges, Kristian Senkler + + 2005-04-27 + + + 04-038r2 + ISO19115/ISO19119 Application Profile for CSW 2.0 (CAT2 AP ISO19115/19) + 04-038r2 + ISO19115/ISO19119 Application Profile for CSW 2.0 (CAT2 AP ISO19115/19) + This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS - - Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0 + - + + Coverage Implementation Schema - ReferenceableGridCoverage Extension + 16-083r2 + + - OGC Testbed-15:Images and ChangesSet API Engineering Report - 2020-01-08 - 19-070 - OGC Testbed-15:Images and ChangesSet API Engineering Report - The OGC API – Images and Changeset draft specification addresses the use case of an OGC API tile server that serves image tiles and a client that portrays the result as a set of images. The tile server uses a set of images (e.g. a set of remote sensing satellite scenes or a set of drone pictures) in the backend and they are also accessible by an API - Images. The source images can be updated and therefore the tile server also needs to be able to deliver only the tiles that have changed. The draft specification is divided into two independent parts that can be used in broader scenarios: - -The OGC API – Images: Enables managing (retrieving, creating and updating) sets of images that are georeferenced. The images does not follow any tile scheme, and can partiallyor totally overlap. The API enables a mosaicking use case (where the imagery is combined in a single bigger “picture”) but could also serve a use case in which a moving camera is taking pictures at locations along a route and then stores the images as a single collection. + + Eric Hirschorn + 2017-06-15 + + + 16-083r2 + OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension + The OGC GML Application Schema - Coverages (“GMLCOV”) version 1.0 [OGC 09-146r2], recently renamed the OGC Coverage Implementation Schema version 1.0, provides a ReferenceableGridCoverage element for representing coverages on a referenceable grid. However, GMLCOV provides no instantiable subtypes of a critical sub-element of ReferenceableGridCoverage, GMLCOV::AbstractReferenceableGrid. To make use of ReferenceableGridCoverage, an extension deriving from GMLCOV would need to be developed. GML 3.3 is not such an extension of GMLCOV, as it is built independently from GMLCOV. Use of the instantiable referenceable grid elements of GML 3.3 with ReferenceableGridCoverage violates Requirement 14 of GMLCOV 1.0 and Requirement 24 of the OGC Modular Specification[1]. -The Changeset filter: Enables filtering a request to a data service in a way that only recent changes are delivered. It can be applied to OGC API that provide access to data and in particular to the OGC API tiles. - 19-070 - Joan Maso Pau - +This OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension provides a set of referenceable grid elements for use as sub-elements of ReferenceableGridCoverage. Three of these elements have been adapted from GML 3.3, while a fourth emerged from work on a Testbed-11 Engineering Report[2]. + + - + 20-019r1 - - + - MetOcean Application profile for WCS2.1: Part 1 MetOcean GetCorridor Extension - 15-108r3 - - + Jeff Yutzler + 2021-01-13 + 20-019r1 + GeoPackage Engineering Report + + In Testbed-16, participants researched ways to mitigate these limitations, particularly in the context of the Ordnance Survey (OS) MasterMap Topography datasets. The Testbed activity also made use of OS Open Zoomstack, a smaller, freely available, multi-scale dataset. To address the first two limitations, Testbed participants developed GeoPackage metadata profiles designed to advance the discoverability of the contents of a GeoPackage and exchange the OS portrayal styles and symbols. The metadata proved to be interoperable between the server and client implementation. + OGC Testbed-16: GeoPackage Engineering Report + + + + + Documents of type Interoperability Program Report + Documents of type Interoperability Program Report + - 2021-03-22 - 15-108r3 - - The purpose of the GetCorridor operation is to extract a corridor based on a trajectory from a multidimensional coverage. The need for the getCorridor operation stems from active members of the OGC MetOcean Domain Working Group (DWG) who saw a manifest need for extraction of such information from gridded datasets. This work has been done by members of the OGC MetOcean Domain Working Group. - OGC MetOcean Application profile for WCS2.1: Part 1 MetOcean GetCorridor Extension - Peter Trevelyan, Paul Hershberg, Steve Olson - + Documents of type Interoperability Program Report - - 2014-04-14 - OpenSearch Geo and Time Extensions - 10-032r8 - <p>This OGC standard specifies the Geo and Time extensions to the OpenSearch query protocol. OpenSearch is a collection of simple formats for the sharing of search results.</p> -<p>The OpenSearch description document format can be used to describe a search engine so that it can be used by search client applications. The OpenSearch description format allows the use of extensions that allow search engines to request a specific and contextual query parameter from search clients.</p> -<p>The OpenSearch response elements can be used to extend existing syndication formats, such as RSS and Atom, with the extra metadata needed to return search results. -Services that support the OpenSearch Specification, the Geo and Time extensions defined in this document are called OpenSearch GeoTemporal Services.</p> - - Pedro Gonçalves - 10-032r8 - - - + + 06-050r3 + GeoRSS, An Introduction to + 2006-07-19 + GeoRSS is simple proposal for geo-enabling, or tagging, really simple syndication (RSS) feeds with location information. GeoRSS proposes a standardized way in which location is encoded with enough simplicity and descriptive power to satisfy most needs to describe the location of Web content. GeoRSS may not work for every use, but it should serve as an easy-to-use geotagging encoding that is brief and simple with useful defaults but extensible and upwardly-compatible with more sophisticated encoding standards such as the OGC (Open Geospatial Consortium) GML (Geography Markup Language). - OGC® OpenSearch Geo and Time Extensions - + GeoRSS, An Introduction to + 06-050r3 + - - - This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 9 (OWS-9). The report summarizes the work carried out regarding performance and endurance testing of data provision services, namely Web Feature Service and Event Service. More specifically, the report deals with the performance and endurance testing of data provision services commonly used within OWS Aviation testbeds. Test runs have been evaluated on the basis of well-defined, service-specific test models and the results are documented in detail. Furthermore, a description of the service test environment is documented in alignment with the overall OWS-9 service architecture - OGC® OWS-9 Report on Aviation Performance Study + + + Carl Reed + + + + + 18-067r3 + OGC Symbology Conceptual Model: Core Part + + + + This document presents the requirements for defining the Symbology Conceptual Core Model (SymCore), the conceptual basis to define symbology rules for the portrayal of geographical data. It is modular and extensible (one core model, many extensions), also encoding agnostic (one symbology model, many encodings). It contains a minimal set of abstract classes representing explicit extension points of the model. + 18-067r3 + OGC Symbology Conceptual Model: Core Part + 2020-10-15 + + + 17-090r1 + Josh Lieberman + Model for Underground Data Definition and Integration (MUDDI) Engineering Report + 17-090r1 + 2019-11-25 - 2013-06-18 - - 12-158 - 12-158 - OWS-9 Report on Aviation Performance Study - Matthes Rieke - - - - - 99-103 - Topic 03 - Locational Geometry Structures - Topic 3 - Locational Geometry Structures - - 1999-03-18 - - - 99-103 - Provides essential and abstract models for GIS technology that is widely used. - Cliff Kottman - - - Create, store, and use state information from a WMS based client application - + The recently published Underground Infrastructure Concept Development Study (UICDS) Engineering Report [1] examines the present state of underground infrastructure information (UGII), costs and benefits of that state, as well as future opportunities for an improved state. That report describes a number of candidate models for UGII and recommends a number of follow-on activities, including development of a prototype UGII integration model to support subsequent UGII integration and exchange initiatives. The present report describes the design and development of conceptual UGII integration model MUDDI (Model for Underground Data Definition and Interchange). The goal of MUDDI is not to replace existing models but to serve as the basis for integration of datasets from different models, at the levels of detail required to address application use cases described in [1]. MUDDI as described here is a conceptual model which will serve as the basis for one or more conformant and interchangeable physical implementations such as GML (Geographic Markup Language) or SFS (Simple Features SQL). As a prototype model, the current version of MUDDI is also not intended to be final, but to serve as an input to the proposed OGC Underground Infrastructure Pilot and similar activities which will in turn serve to refine and improve the model through implementation and deployment in realistic application scenarios. + - - - Web Map Context Documents - 03-036r2 - 03-036r2 - Jean-Philippe Humblet + Model for Underground Data Definition and Integration (MUDDI) Engineering Report + + + + 07-018 + 2007-05-17 + OpenGIS Sensor Planning Service Application Profile for EO Sensors + Sensor Planning Service Application Profile for EO Sensors + 07-018 + - 2003-06-12 - Web Map Context Documents + + + + This Discussion Paper explains how a Sensor Planning Service is organised and implemented for the Earth Observation domain. + Philippe M - - - Advancing the Interoperability of Geospatial Intelligence Tradecraft with 3D Modeling, Simulation, and Game Engines - 20-085r1 + - - 20-085r1 + Change Request - O&M Part 1 - Move extensions to new namespace - The objectives of this MS&G -Technical Paper are focused on identifying technology trends -that are influencing the convergence of GEOINT and M&S -tradecraft. The purpose is to advance ideas and techniques, -such as reality modeling of 3D environments, which increase -the knowledge-base and capacity of the geospatial analyst -community writ large. - USGIF & OGC - - - 2021-03-08 - Advancing the Interoperability of Geospatial Intelligence Tradecraft with 3D Modeling, Simulation, and Game Engines + 08-022r1 + Change Request - O&M Part 1 - Move extensions to new namespace + + + The XML Schema implementation of optional/informative elements of the Observation Schema was published in the om/1.0.0/extensions directory, in the same XML namespace as the base schema. Those OGC implementations that have a dependency on the Observation Schema (i.e. Sampling Features, SOS) <import> the “all-components” document om.xsd. However, the all-components stub-schema document “om.xsd” does not include the extensions. Thus, any application which requires one of the dependent OGC schemas (Sampling Features, SOS) may not access the Observation Schema Extensions, since the <import> of om.xsd clashes with any attempt to <import> om_extended.xsd. This problem is a consequence of an error in the modularization strategy for optional elements, combined with the rules for schema document resolution used by standard processing environments. + Simon Cox + 2008-05-12 + 08-022r1 + + - - - 2011-03-30 - This Discussion Paper proposes model for license-based access control to SOAP services, based on OASIS SAML 2.0. This approach is a potential solution for license-based access control, which requires the possession of a valid license for getting access to a service. Use of digital licenses allow users to act on or with web services to which they are associated - -This document re-uses content produced by the OGC GeoRM Common 1.0 Standards Working Group and combined that with the document OGC 10-125, which was posted to an internal OGC document archive (Pending Documents) but is not publicly available. -This document does not claim compliance to the GeoDRM reference model (ISO 19153), although the authors are not yet aware of any conflicts to it. - - 11-018 - License-Based Access Control + + Geographic information - Rights expression language for geographic information - Part xx: GeoREL + + + Geographic information - Rights expression language for geographic information - Part xx: GeoREL + 06-173r2 + This document extends the rights expression language (REL) to encompass the concerns of holders of geographic data and service resources to equally ensure their protection. This allows the geographic information market to operate with minimal constraints derived from need for the protection of intellectual property. + + John Herring + + 06-173r2 + 2007-01-25 + + + + + 21-025 + Joan Maso + Cloud Optimized GeoTIFF specification Engineering Report + 21-025 + + + Cloud Optimized GeoTIFF (COG) is a new approach in using existing standards to accelerate distribution and analysis of 2D regular grid coverage data on the web. COG combines the use of the TIFF format with data structured internally in tiles and low resolutions subfiles (also called overviews). The main subfile is georeferenced using GeoTIFF tags and the lower resolution subfiles inherit the same georeferencing. This organization allows for retrieving only the part of the data needed for presentation or analysis. This capability is possible not only in the file system but also over the web if the HTTP range header is supported by the servers. + +This OGC Testbed 17 Engineering Report (ER) discusses the COG approach, describes how GeoTIFF is used for the lower resolution subfiles, and proposes a different path forward that integrates COG with the OGC Tile Matrix Set Standard (http://docs.opengeospatial.org/is/17-083r2/17-083r2.html). The ER includes a chapter that formalizes the draft COG specification with clear requirements. + +One of the common use cases for COG is the provision of multispectral remote sensing data. The increase in spatial and spectral resolution combined with more accurate sensors that require more than 8 bits per pixel results in big files that can exceed the 4 Gbyte limit of the original TIFF format. Having an OGC standard formally specifying this approach would be useful. Therefore, this ER includes a chapter that formalizes a draft BigTIFF specification, defining clear requirements. + +The objective is to be able to reference BigTIFF from the GeoTIFF and the COG standards. + 2022-02-08 + + + OGC Testbed-17: Cloud Optimized GeoTIFF specification Engineering Report + + - License-Based Access Control - Rüdiger Gartmann, Bastian Schäffer - - 11-018 + + 08-133 + OpenGIS® Sensor Event Service Interface Specification - - - This Engineering Report documents findings, achievements, and learnings gained through activities during the OGC Earth Observation (EO) Applications Pilot by the EOX team (EOX, DLR, UVT, Sinergise, and Terrasigna). Both perspectives, from application developer’s as well as from platform provider’s view, are represented here. - OGC Earth Observation Applications Pilot: EOX-Sinergise-DLR-UVT-Terrasigna Engineering Report - 20-043 - - - 2020-10-22 + Sensor Event Service Interface Specification + 08-133 + The Sensor Event Service (SES) provides operations to register sensors at the service application and let clients subscribe for observations available at the service. The service performs filtering of sensor data (streams) based upon the filter criteria defined in these subscriptions. Filters can be applied on single observations but also on observation streams, potentially aggregating observations into higher-level information (which itself can be regarded as observation data). Whenever matches are discovered, a notification is sent to the subscriber, using asynchronous, push-based communication mechanisms. + + 2008-10-10 + + Johannes Echterhoff, Thomas Everding + + + 21-053r1 + Topic 23 - GeoPackage Conceptual and Logical Model + 21-053r1 + 2023-06-29 + + This document presents the conceptual and logical models for version 1.x of the OGC GeoPackage Standard. The intent is that these models can be used to implement the GeoPackage standard using technology other than a SQLite database. - 20-043 - - OGC Earth Observation Applications Pilot: EOX-Sinergise-DLR-UVT-Terrasigna Engineering Report - Stefan Achtsnit, Joachim Ungar, and Stephan Meißl (EOX), Anja Vrecko and Grega Milčinski (Sinergise) + Topic 23 - GeoPackage Conceptual and Logical Model + Jeff Yutzler + + + - - - Recommended XML/GML 3.1.1 encoding of common CRS definitions - 05-011 - 2005-01-28 - This document recommends standard XML encodings of data defining some commonly-used coordinate reference systems, including geographic, projected, and vertical CRSs. These recommended encodings are based on GML 3.1.1. These common CRS definitions will often be referenced in data transferred between client and server software that implements various standardised interfaces. This specified definition data encoding is expected to be used by multiple OGC Implementation Specifications. That is, each of these specifications is expected to use a subset and/or superset of this recommended definition data. + + + 2021-09-13 + + OGC City Geography Markup Language (CityGML) 3.0 Conceptual Model Users Guide + 20-066 + CityGML is an open conceptual data model for the storage and exchange of virtual 3D city models. It is defined through a Unified Modeling Language (UML) object model. This UML model extends the ISO Technical Committee 211 (TC211) conceptual model standards for spatial and temporal data. Building on the ISO foundation assures that the man-made features described in the City Models share the same spatial-temporal universe as the surrounding countryside within which they reside. The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. -The position or location of a point can be described using coordinates. Such coordinates are unambiguous only when the coordinate reference system on which those coordinates are based is fully defined. Each position is described by a set of coordinates based on a specified coordinate reference system. Coordinates are often used in datasets in which all coordinates belong to the same coordinate reference system. This paper specifies XML encoding of data defining some coordinate reference systems. - - 05-011 +This Users Guide provides extended explanations and examples for the individual concepts that are defined in the CityGML 3.0 Conceptual Model Standard. Both documents, the Conceptual Model Standard and the Users Guide, are mutually linked to facilitate navigation between corresponding sections in these documents. + Charles Heazel + + 20-066 + City Geography Markup Language (CityGML) 3.0 Conceptual Model Users Guide + - Recommended XML/GML 3.1.1 encoding of common CRS definitions - Arliss Whiteside + + + + OGC® Web Map Tile Service (WMTS) Simple Profile + 13-082r2 + Web Map Tile Service (WMTS) Simple Profile + Joan Masó + 2016-01-19 + The Web Map Tile Service (WMTS) Simple profile defines restrictions that limit the flexibility in implementing a WMTS instance. Adding additional requirements has the goal of simplifying the creation of services and clients. By implementing this profile, clients can more easily combine data coming from different services including from other WMTS instances and even from some tile implementations that are not OGC WMTS based, such as some current distributions of OSM. In fact, most of these tiling services are implicitly following most of the WMTS requirements. Many current WMTS services that implement this profile will have to undergo some changes on how tiles are exposed, and a client that is compatible with WMTS 1.0 will be immediately compatible with this profile. The aim is to align the WMTS standard to other popular tile initiatives which are less flexible but widely adopted. + 13-082r2 - + + - + + - + + Panagiotis (Peter) A. Vretanos + Web Object Service Implementation Specification + 03-013 + + 2003-01-15 + Web Object Service Implementation Specification + 03-013 + + + There is a requirement to manage many different types of objects. These include styles, symbols and images. To satisfy this requirement, a repository interface is required. The intent of the Web Object Service interface is to provide a means to define this interface. - 2006-05-09 - 05-109r1 - Catalog 2.0 IPR for ebRIM - Catalog 2.0 IPR for ebRIM - 05-109r1 - - Panagiotis (Peter) A. Vretanos, Rento Primavera - The purpose of this document is to show how to map the various types of metadata documents to be used in the OWS3 project into the ebRIM. - - - - - 2017-10-20 - Future City Pilot 1 - Automating Urban Planning Using Web Processing Service Engineering Report - 16-099 + + + 2012-05-15 - Mohsen Kalantari - 16-099 - Future City Pilot 1 - Automating Urban Planning Using Web Processing Service Engineering Report - + OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report) + 11-108 + - - - Numerous and diverse technologies push cities towards open and platform-independent information infrastructures to manage human, natural, and physical systems. Future Cities Pilot 1 is an OGC interoperability initiative that aims to demonstrate how cities can begin to reap the benefits of open standards. This document reports how Web Processing Standard (WPS) of OGC was successfully used in automating urban planning processes. This document details the implementation of urban planning processes and rules concerning urban development approval processes. - - - Provides an overview of the requirements, architecture, and design of Integrated Clients developed during the OGC Open Web Services - - 03-021 - Integrated Client for Multiple OGC-compliant Services - 2003-01-20 - - + Ingo Simonis - Integrated Client for Multiple OGC-compliant Services - 03-021 - - Jeff Yutzler + OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report) + This document describes the usability of OGC services and encodings to implement the +OWS-8 observation fusion and tracking thread in an abstract way. The real deployment +and an actual perspective on the engineering and technology viewpoint can be found in +OWS-8 engineering report OGC 11-134, ‘OWS-8 Tracking: Moving Target Indicator +Process, Workflows and Implementation Results’. In addition, it describes an XMLSchema +based implementation of the UML information models defined in OWS-8 +engineering report “Information Model for Moving Target Indicators and Moving Object +Bookmarks” (OGC 11-113). +The report is also based on the results of the VMTI/GMTI and STANAG 4676 realization +in the OGC concept of operations study; performed as part of OWS 8 and the EC cofunded +research project Emergency Support System - ESS” (contract number 217951). + 11-108 - - + + 14-005r4 - 10-157r4 - Earth Observation Metadata profile of Observations & Measurements - - 10-157r4 - Jerome Gasperi, Frédéric Houbie, Andrew Woolf, Steven Smolders - OGC® Earth Observation Metadata profile of Observations & Measurements - - 2016-06-09 - - This OGC Implementation Standard defines a profile of Observations and Measurements (ISO 19156:2010 and OGC 10-025r1) for describing Earth Observation products (EO products). -This profile is intended to provide a standard schema for encoding Earth Observation product metadata to support the description and cataloguing of products from sensors aboard EO satellites. -The metadata being defined in this document is applicable in a number of places where EO product metadata is needed. -1. In the EO Product Extension Package for ebRIM (OGC 10-189). This extension package defines how to catalog Earth Observation product metadata described by this document. Using this metadata model and the Catalogue Service defined in OGC 10-189, client applications can provide the functionality to discover EO Products. Providing an efficient encoding for EO Product metadata cataloguing and discovery is the prime purpose of this specification. -2. In the EO Application Profile of WMS (OGC 07-063r1). The GetFeatureInfo operation on the outline (footprint layer) should return metadata following the Earth Observation Metadata profile of Observation and Measurements. -3. In a coverage downloaded via an EO WCS AP (OGC 10-140). In WCS 2.0 (OGC 10-084), the GetCoverage and DescribeCoverage response contains the metadata element intended to store metadata information about the coverage. The Earth Observation Application profile of WCS (OGC 10-140) specifies that the metadata format preferred for Earth Observation is defined by this document. -4. Potentially enclosed within an actual product to describe georeferencing information as for instance within the JPEG2000 format using GMLJP2. GMLJP2 defines how to store GML coverage metadata inside a JP2 file. -Earth Observation data products are generally managed within logical collections that are usually structured to contain data items derived from sensors onboard a satellite or series of satellites. The key characteristics differentiating products within the collections are date of acquisition, location as well as characteristics depending on the type of sensor, For example, key characteristics for optical imagery are the possible presence of cloud, haze, smokes or other atmospheric or on ground phenomena obscuring the image. -The common metadata used to distinguish EO products types are presented in this document for generic and thematic EO products (i.e optical, radar, atmospheric, altimetry, limb-looking and synthesis and systematic products). From these metadata the encodings are derived according to standard schemas. In addition, this document describes the mechanism used to extend these schemas to specific missions and for specific purposes such as long term data preservation. - + - - + This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes. + + + 2016-08-23 + 14-005r4 + OGC® IndoorGML - with Corrigendum + + + OGC® IndoorGML - with Corrigendum + + Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker + + + This document specifies a + High-Level Ground Coordinate Transformation Interface + + + 01-013r1 + Arliss Whiteside + 2001-02-27 + + 01-013r1 + High-Level Ground Coordinate Transformation Interface + - The Testbed-11 deliverable OGC 15-053 Implementing JSON/GeoJSON in an OGC Standard ER enumerated strategies for implementing JSON in OGC services and OGC encodings. Previously, a mechanism to migrate XML into JSON was proposed by Pedro Gonçalves in 14-009r1 OGC Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context. In contrast, this engineering report (ER) proposes a mechanism to derive JSON and JSON-LD encodings from UML modeling without using XML as an intermediate step. The rules provided can be divided into rules for JSON instances and rules for JSON schemas. - -These rules have been applied to the UML diagrams in OWS common 2.0 to derive JSON encodings for them. In practice this ER evaluates how to provide service metadata in the derived JSON. JSON schemas and @context documents for independent validation of the four main sections of the ServiceMetadata are provided. This activity is done in connection with the OGC 16-052 OWS Context / Capabilities ER. The rules are applied to WMS to provide a full JSON encoding for the WMS 1.4 standard candidate. - -Finally, this ER discusses the applicability to data geospatial formats, both for coverage formats (compared to the CIS standard) and feature formats (compared to GeoJSON). - -Readers unfamiliar with JSON, JSON-LD and JSON Schema should first read OGC 16-122 (Geo)JSON User Guide. OGC 16-122 includes guidelines and recommendations for the use of JSON and JSON-LD in OGC data encodings and services. - Joan Masó - 16-051 - 16-051 - Testbed-12 Javascript-JSON-JSON-LD Engineering Report + + + + + Joan Maso Pau + 2020-01-08 + OGC Testbed-15:Images and ChangesSet API Engineering Report + 19-070 - - 2017-05-12 - Testbed-12 Javascript-JSON-JSON-LD Engineering Report + - - - 19-042r1 - Discussion Paper - JSON Encodings for EO Coverages - 19-042r1 - This discussion paper documents and concludes one year (2018-2019) of work undertaken by a National Aeronautics and Space Administration (NASA) Earth Science Data System Working Group focused on exploring JSON Encodings in Earth Observation Coverages. The primary function of this paper is to ensure that the collective Working Group knowledge obtained from the year effort is not lost and consequently that it can be considered, debated and hopefully utilized in other forums outside of NASA with the aim of driving progress in this field. The covering statement (below) provides 10 questions which are meant to facilitate such discussion. - -This discussion paper will be of particular interest to the following parties: + 19-070 + OGC Testbed-15:Images and ChangesSet API Engineering Report + The OGC API – Images and Changeset draft specification addresses the use case of an OGC API tile server that serves image tiles and a client that portrays the result as a set of images. The tile server uses a set of images (e.g. a set of remote sensing satellite scenes or a set of drone pictures) in the backend and they are also accessible by an API - Images. The source images can be updated and therefore the tile server also needs to be able to deliver only the tiles that have changed. The draft specification is divided into two independent parts that can be used in broader scenarios: -Web application developers tasked with designing and developing applications which consume Earth Observation spatial data encoded as JSON. +The OGC API – Images: Enables managing (retrieving, creating and updating) sets of images that are georeferenced. The images does not follow any tile scheme, and can partiallyor totally overlap. The API enables a mosaicking use case (where the imagery is combined in a single bigger “picture”) but could also serve a use case in which a moving camera is taking pictures at locations along a route and then stores the images as a single collection. -Parties (including standards bodies) interested in serving and consuming Spatial data on the Web e.g. World Wide Web Consortium (W3C), Open Geospatial Consortium (OGC) or developers of other data standards, etc. - - 2019-11-11 - - +The Changeset filter: Enables filtering a request to a data service in a way that only recent changes are delivered. It can be applied to OGC API that provide access to data and in particular to the OGC API tiles. + + + + + Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture + 05-126 + 2005-11-30 - Discussion Paper - JSON Encodings for EO Coverages - Lewis John McGibbney + This part of OpenGIS + Keith Ryden + 05-126 + OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architectu + + - + + + - 12-027r3 - Web Feature Service (WFS) Temporality Extension - 12-027r3 + 2007-12-28 + This International Standard defines a conceptual schema for the spatial characteristics of coverages. Coverages support mapping from a spatial, temporal or spatiotemporal domain to feature attribute values where feature attribute types are common to all geographic positions within the domain. A coverage domain consists of a collection of direct positions in a coordinate space that may be defined in terms of up to three spatial dimensions as well as a temporal dimension. + + 07-011 + Topic 06 - Schema for coverage geometry and functions + + Topic 6 - Schema for coverage geometry and functions + OGC - - - 2014-07-16 - Timo Thomas - - OGC Web Feature Service (WFS) Temporality Extension - - This OGC discussion paper provides a proposal for a temporality extension for the WFS -2.0 and FES 2.0 standard. It is based on the work of and experiences made in several -OWS test beds, in particular OWS-7, OWS-8 and OWS-9, Aviation threads and -discussions at the 2011 OGC TC meeting in Brussels, Belgium. It partially replaces and -advances the document “OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via -an OGC WFS 2.0” [4]. + 07-011 - - OWS-8 Information Model for Moving Target Indicators and Moving Object Bookmarks (Engineering Report) - Ingo Simonis - - OWS-8 Information Model for Moving Target Indicators and Moving Object Bookmarks (Engineering Report) - 11-113r1 + + This OGC Testbed 17 Engineering Report (ER) documents the work completed in the “Attracting Developers: Lowering the entry hurdle for OGC Web API experiments” task. + +OGC Web API Standards are being developed to make it easy to provide geospatial data over the web. These standards provide a certain level of formality to ensure high levels of interoperability. They rigorously define requirements and rules to reduce room for error during interpretation. This rigor sometimes makes the standard documents difficult to read and hence implement. Rather than direct examination of a standard, the majority of developers often prefer to start with implementation guidelines, sample code, and best practice documentation and then refer to the standards document for guidance and clarity. + +The Testbed-17 (TB-17) API task served as a foundation for further development and exploration and delivers knowledge necessary for agile development, deployment, and executing OGC Standards-based applications following a “How-To” philosophy with hands-on experiments, examples, and instructions. + + - This report aims at providing an information model for the usage of video moving target indicator data (VMTI), ground moving target indicator (GMTI) and tracking information (STANAG 4676) in the context of standardized spatial data infrastructures compliant to OGC and ISO standards. If possible, precedence was given on using the OGC Sensor Web Enablement suite of standards, as this suite provides a homogeneous suite of standards to express sensor and sensor observation data in the context of OGC. This means that all encodings are based on Observation and Measurements version 2 (O&M) and implemented as an application schema according to the rules of Geography Markup Language version 3.2 (GML). An information model – so called ‘bookmark’ – to conserve the trace from a moving object back to the original base data is discussed briefly. - + OGC Testbed-17: Attracting Developers: Lowering the entry barrier for implementing OGC Web APIs + 21-019 + - 11-113r1 - 2011-11-23 + Aleksandar Balaban + 21-019 + + OGC Testbed-17: Attracting Developers: Lowering the entry barrier for implementing OGC Web APIs + 2022-01-21 - - Topic 07 - Earth Imagery - 04-107 - - - - 04-107 + - - Topic 7 - Earth Imagery - George Percivall - - 2004-10-15 - Replaced previous material in Topic 7 with ISO 19101-2, Reference Model - Geographic Information - Imagery. Version 5 of OGC Topic 7 is identical with ISO 19101-2 Working Draft #3. Topic 7 will be updated jointly with the progress of ISO 19191-2. Appendix A of Topic 7, version 4 contained a White Paper on Earth Image Geometry Models. That white paper is now separate OGC Recommendation document. - - - - 07-006r1 - Catalogue Service Implementation Specification - 07-006r1 - Doug Nebert, Arliss Whiteside, Peter Vretanos + This specification defines the interfaces of the OGC (Geo)XACML Policy Administration Web Service (OGC (Geo)XACML PAWS or simply PAWS in the following) that supports the creation, modification, exchange, analysis, testing, transformation, encrypting and signing of XACML and GeoXACML encoded access control policies. +This draft specification was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. This document presents the results of the work within add-on project of the OWS-9 Security and Services Interoperability (SSI) thread. +Please note that currently the document only contains the definition of the mandatory operations i.e. the basic conformance class. The writing of the sections describing the optional operations is still a to do. These sections need to define the following operations: +• AnalyzePolicyElement operation +• OptimizePolicyElement operation +• TransformPolicyElement operation +• TestPolicyElement operation +• EncryptPolicy operation +• SignPolicy operation +Suggested additions, changes, and comments on this report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document. + + Jan Herrmann, Andreas Matheus + OGC GeoXACML and XACML Policy Administration Web Service (PAWS) - - 2007-04-20 - OpenGIS Catalogue Service Implementation Specification - The OpenGIS® Catalogue Services Interface Standard (CAT) supports the ability to publish and search collections of descriptive information (metadata) about geospatial data, services and related resources. Providers of resources use catalogues to register metadata that conform to the provider's choice of an information model; such models include descriptions of spatial references and thematic information. Client applications can then search for geospatial data and services in very efficient ways. -See also the OGC Catalogue 2.0 Accessibility for OWS-3 Discussion Paper [http://www.opengeospatial.org/standards/dp], the OWS-4 CSW ebRIM Modelling Guidelines Interoperability Program Report (IPR) [www.opengeospatial.org/standards/dp] and the OpenGIS® Catalogue Service Interface Standard 2.0.1 - FGDC CSDGM Application Profile for CSW (Best Practice) [http://www.opengeospatial.org/standards/bp]. + GeoXACML and XACML Policy Administration Web Service (PAWS) + 13-099 + + + + 2013-11-06 + 13-099 + + + + The OGC Testbed-16 Data Centric Security Engineering Report (ER) continues the evaluation of a data-centric security (DCS) approach in a geospatial environment. In order to fully explore the potential of the DCS concept, this ER first specifies two advanced use case scenarios: Data Streaming and Offline Authorization for querying and consuming protected geospatial content. The ER then specifies the communication with a new architectural component called the Key Management Server (KMS) via an Application Programming Interface (API) created for this Testbed. The API was invoked to register keys used to encrypt data-centric protected content. Then clients called the same API to obtain those keys to perform the data verification/decryption. + + + + 20-021r2 + OGC Testbed-16: Data Centric Security Engineering Report + - - - - This document defines an OGC® Standard for encoding binary representations of space-time varying geo-referenced data. Specifically, this standard specifies the netCDF classic and 64-bit offset file binary encoding formats. This standard specifies a set of requirements that every netCDF classic or 64-bit offset binary encoding must fulfil. - Ben Domenico - 2011-04-05 - - - 10-092r3 - NetCDF Binary Encoding Extension Standard: NetCDF Classic and 64-bit Offset Format - - NetCDF Binary Encoding Extension Standard: NetCDF Classic and 64-bit Offset Format - 10-092r3 - - + 2021-02-26 + 20-021r2 + OGC Testbed-16: Data Centric Security Engineering Report + Aleksandar Balaban - - Eugene G. Yu, Liping Di, Ranjay Shrestha + + 16-137r2 + This document describes how the OGC PubSub standard can be used as a mechanism to automatically notify analysts of data availability for CSW and other OGC Web Services (e.g. WFS, WCS). In particular, this document proposes the following: + +Specific PubSub 1.0 extensions for CSW 2.0.2 and 3.0, leveraging on standard functionalities, data models, and semantics to enable sending notifications based on user-specified area of interest and/or keywords; + +A general, basic mechanism for enabling PubSub for the generic OGC Web Service over the existing request/reply OWS’s, i.e. usual requests as filters, usual responses as appropriate updates/data pushes, existing semantics and syntax expressiveness. + +This document is the result of activity performed within the Large-Scale Analytics (LSA) Thread of the OGC Testbed 12 Interoperability initiative, being identified as document deliverable A074 PubSub / Catalog Engineering Report. This document also captures lessons learnt from the implementation of component deliverable A016 CSW 2.0.2 with PubSub Core Support Server. + 16-137r2 + Testbed-12 PubSub / Catalog Engineering Report + - 2016-01-18 - OGC® Testbed-11 High Resolution Flood Information Scenario Engineering Report - Testbed-11 High Resolution Flood Information Scenario Engineering Report - 15-046r2 + + + Testbed-12 PubSub / Catalog Engineering Report + 2017-05-12 + Lorenzo Bigagli + + + + + OGC® Sensor Observation Service Interface Standard + 12-006 + Sensor Observation Service Interface Standard + The SOS standard is applicable to use cases in which sensor data needs to be managed in an +interoperable way. This standard defines a Web service interface which allows querying +observations, sensor metadata, as well as representations of observed features. Further, this +standard defines means to register new sensors and to remove existing ones. Also, it defines +operations to insert new sensor observations. This standard defines this functionality in a binding +independent way; two bindings are specified in this document: a KVP binding and a SOAP +binding. - This OGC Engineering Report describes the high-resolution flood information scenario carried out under the Urban Climate Resilience Thread of the Testbed 11 Initiative. The scenario was developed for two areas of interest: the San Francisco Bay Area and in Mozambique. The scenarios for these two locations demonstrate the interoperation and capabilities of open geospatial standards in supporting data and processing services. The prototype High Resolution Flood Information System addresses access and control of simulation models and high-resolution data in an open, worldwide, collaborative Web environment. The scenarios were designed to help testbed participants examine the feasibility and capability of using existing OGC geospatial Web Service standards in supporting the on-demand, dynamic serving of flood information from models with forecasting capacity. Change requests to OGC standards have also been identified through the Testbed activity. + + - - - 15-046r2 + 12-006 + 2012-04-20 + Arne Bröring, Christoph Stasch, Johannes Echterhoff + - - OGC Reference Model - 2011-12-19 + + This OGC document specifies a CityGML-based application schema for a subset of an Urban Topographic Data Store (UTDS) as specified by the US National Geospatial-Intelligence Agency (NGA). +The particular focus of this implementation profile was to test the applicability of CityGML to UTDS data. +This document specifies the implementation profile as well as the findings. + + OWS-6 UTDS-CityGML Implementation Profile + 09-037r1 - - - 08-062r7 - OGC Reference Model - George Percivall - - 08-062r7 - - The OGC Reference Model (ORM) describes the OGC Standards Baseline focusing on relationships between the baseline documents. The OGC Standards Baseline (SB) consists of the approved OGC Abstract and Implementation Standards (Interface, Encoding, Profile, and Application Schema – normative documents) and OGC Best Practice documents (informative documents). - - - - 22-010r4 - - - 22-010r4 - Topic 24 - Functional Model for Crustal Deformation - - 2024-04-29 - Chris Crook - Topic 24 - Functional Model for Crustal Deformation - This OGC Abstract Specification (AS) defines a general parameterization of surface deformation models. - -All objects on the surface of the Earth are moving. Apparently fixed features such as buildings are moving with the Earth’s crust, being subject to ongoing plate tectonic movement and episodic deformation events such as earthquakes. - -Increasingly, applications and users rely on global positioning methods, such as Global Navigation Satellite Systems (GNSS) observations, to precisely determine the coordinates of features. The resulting coordinates are then stored in databases and used in a wide range of applications, such as Geographic Information Systems (GIS). However, the coordinates from GNSS are referenced to global reference frames and coordinate reference systems (CRSs). In these reference frames the coordinates of apparently fixed objects are continually changing. - -This creates a challenge for the geospatial and positioning community: How to account for this movement when comparing data sets observed at different times, or how to locate an object observed in the past. - -This problem is generally addressed in one of two ways: - -Defining a reference epoch for the CRS of coordinates held in the GIS, often by defining a CRS with a reference epoch, or -Using a CRS which is fixed relative to the surface of the Earth. -In practice there is little difference between these two approaches. Neither the position at a reference epoch, nor the coordinates in a static CRS, can be directly measured by global positioning methods. - -Propagating the observed coordinates to a reference epoch, or transforming to a static CRS, requires a deformation model — a mathematical model of the deformation of the Earth’s surface. - -Common uses of a deformation model include: - -Determining the current location of an object based on historic measurement of its location, -Propagation of the current observed location of an object to the reference epoch of a static CRS, -Determining the spatial relationship of data sets observed at different times, and -Predicting the location of an object at some future time. -Currently, many national geodetic agencies have developed or are planning to develop regional deformation models. However, the current models generally use customized formats and software developed by each agency. - -This AS describes a way of parameterizing a deformation model such that it can be encoded into a data set and used in software for coordinate operations. The AS defines how to calculate the displacement of a point between two different epochs. It provides a common understanding between producers of deformation models and developers of software about what the deformation is and how it will be used. - -This AS will allow users of compliant software applying a compliant deformation model to be confident that the model is being used as intended by its producers. - + 2009-07-20 + + + 09-037r1 + Clemens Portele + + OWS-6 UTDS-CityGML Implementation Profile - + + 2014-07-15 + 14-006r1 + + + 14-006r1 + Testbed 10 Recommendations for Exchange of Terrain Data - OWS5: OGC Web feature service, core and extensions - 08-079 - John Herring + - 2008-09-12 - This standard specifies the behavior of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations and transaction operations. Discovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers. Retrieval operations allow features to be retrieved from the opaque underlying data store based upon constraints on spatial and non-spatial feature properties defined by the client. Transaction operations allow features to be created, changed and deleted from the opaque underlying data store. - - - - 08-079 - OWS5: OGC Web feature service, core and extensions + OGC® Testbed 10 Recommendations for Exchange of Terrain Data + This document is a deliverable of the OGC Testbed 10 (Testbed-10). Its contents cover the summary of the work carried out regarding the recommendations for the exchange of terrain data. +Suggested additions, changes, and comments on this draft report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document. +The changes made in this document version, relative to the previous version, are tracked by Microsoft Word, and can be viewed if desired. If you choose to submit suggested changes by editing this document, please first accept all the current changes, and then make your suggested changes with change tracking on. + + Daniel Balog - - OWS-7 Schema Automation Engineering Report - 10-088r3 - - 2014-04-15 + + Thomas Everding + 09-031r1 + 2009-07-16 + OWS-6 SWE Information Model Engineering Report + 09-031r1 + OWS-6 SWE Information Model Engineering Report - - Clemens Portele - 10-088r3 - The capabilities of OGC’s KML 2.2 as a format for exchange and visualization of U.S. National System for Geospatial Intelligence (NSG) Application Schema (NAS) data is explored. + - OGC® OWS-7 Schema Automation Engineering Report + This OGC® document is an OGC Engineering Report for the “Harmonization of SWE Information Models” activity within the OWS-6 SWE thread. +The document discusses relations between OGC standards SensorML, SWE Common and GML and investigates solutions for increased synergy between these standards. This activity also created UML models of the data types used in SWE and GML. +This report shows how UncertML can be integrated into different SWE encodings, namely SWE Common and Observations and Measurements. +This report further discusses the integration of MathML and EML into the SWE environment with an emphasis on SensorML processes and processing. +This document does not discuss the SWE information model related aspects of catalog entries for sensor services and discovery. This topic is covered in a separate Engineering Report. + + - + + Cyril Minoux - Peter Baumann + 2009-09-02 + This document specifies requirements for systems providing maps using OGC Web Map Service. The document defines a profile of OGC WMS 1.3 implementation standard [WMS1.3], a list of normative system requirements and a list of non-normative recommendations. The Defence Geospatial Information Working Group (DGIWG) performed the work as part of through the S05 Web Data Access Service Project of the Services & Interfaces Technical Panel. + + DGIWG WMS 1.3 Profile and systems requirements for interoperability for use within a military environment + 09-102 + 09-102 - - - Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - Corrigendum - 09-147r3 - - This document specifies an extension to the OGC Web Coverage Service (WCS) 2.0 core to allow for client/server communication using HTTP GET with key/value pair (KVP) encod-ing. - OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - Corrigendum - 09-147r3 - 2013-03-26 + + DGIWG WMS 1.3 Profile and systems requirements for interoperability for use within a military environment + - - OGC® Engineering Report for the OWS Shibboleth Interoperability Experiment - 11-019r2 - 11-019r2 - Engineering Report for the OWS Shibboleth Interoperability Experiment + + + Joint OGC OSGeo ASF Code Sprint 2022 Summary Engineering Report + The subject of this Engineering Report (ER) is a code sprint that was held from the 8th to the 10th of March 2022 to advance support of open geospatial standards within the developer community, whilst also advancing the standards themselves. The code sprint was hosted by the Open Geospatial Consortium (OGC), the Apache Software Foundation (ASF), and Open Source Geospatial Foundation (OSGeo). The code sprint was sponsored by Ordnance Survey (OS), and held as a completely virtual event. + Gobe Hobona, Joana Simoes, Angelos Tzotsos, Tom Kralidis, Martin Desruisseaux + Joint OGC OSGeo ASF Code Sprint 2022 Summary Engineering Report + 22-004 + 2022-11-10 + + 22-004 + + + + + The following document contains best practices for identifying input data formats for the OGC WPS 1.0.0. It was created due to a lack of interoperability between different WPS implementation based on non-standardized input identifiers. + Bastian Schäffer + 12-029 + Web Processing Service Best Practices Discussion Paper + + + Web Processing Service Best Practices Discussion Paper + - This document reports on outcomes from the OGC Web Services Shibboleth Interoperability Experiment (OSI). The main objective of OSI was to advance the use of Shibboleth (an open source implementation of SAML) as a means of protecting OWS. In the process, OSI helped develop further understanding of this approach to establishing trusted federations of OWS. This report documents these findings and is intended to be of use to those interested in how Shibboleth/SAML access management federations may function as an organisational model for operational Spatial Data Infrastructure. + + 12-029 + + 2012-04-04 + + + 09-050r1 + + + 2009-07-27 + This report establishes a baseline for the technical architecture, its alternatives and issues for implementing the use cases as specified in the OWS-6 AIM thread RFQ including the temporal WFS supporting the temporal FE 2.0 operators, the Event Service Notification architecture and the client EFBs. + + OGC OWS-6-AIM Engineering Report + - Chris Higgins - - 2012-04-06 + 09-050r1 + OGC OWS-6-AIM Engineering Report + Hans Schoebach - - This report summarizes the work performed under the Canadian Geospatial Data Infrastructure Pilot. The purpose of this pilot was to test the utility of certain OGC standards, in particular the Geography Markup Language (GML) and Web Feature Service (WFS), in the implementation of a spatial data infrastructure. OGC documents 08-001 and 08-002 are more technical companions to this document. + + + + + 05-008c1 + Web Service Common Implementation Specification + Arliss Whiteside + + OpenGIS Web Service Common Implementation Specification + + 2005-05-03 + This document specifies many of the aspects that are, or should be, common to all or multiple OWS interface Implementation Specifications. Those specifications currently include the Web Map Service (WMS), Web Feature Service (WFS), and Web Coverage Service (WCS). These common aspects include: operation request and response contents; parameters included in operation requests and responses; and encoding of operation requests and responses. + 05-008c1 + + + 2001-05-01 + 02-059 + Filter Encoding + + Filter Encoding + + 02-059 + + + Peter Vretanos + + A filter is a construct used to describe constraints on properties of a feature class for the purpose of identifying a subset of feature instances to be operated upon in some way. + + + - 08-000 - Canadian Geospatial Data Infrastructure Summary Report - OGC® Canadian Geospatial Data Infrastructure Summary Report - Raj SIngh - - + + 2009-07-27 + Kristin Stock + This document describes an Application Profile for the Web Ontology Language (OWL) [W3C OWL] for CSW. It is intended to define a specification for how ontologies built using RDF and OWL may be included within an OGC CSW catalogue to semantically-enable the catalogue. - 2008-04-29 - 08-000 + OGC® Catalogue Services - OWL Application Profile of CSW + 09-010 + + 09-010 + + OGC® Catalogue Services - OWL Application Profile of CSW - - This Engineering Report describes how developments of the Community Sensor Model Working Group (CSMW) can be harmonized with the latest SWE specifications and developments in order to support streaming of LiDAR data with SWE technologies. The report will therefore provide an overview on both initiatives and then describe different options how to integrate LiDAR data streams and SWE technologies. In particular, the ER will consider the results of the activities SOS Compression (LiDAR) Server (A012) and LiDAR Streaming Client (A010) and infer recommendations for future developments. - Testbed-12 LiDAR Streaming Engineering Report - - Simon Jirka, Arne de Wall, Christoph Stasch - 2017-03-09 + + 16-145 + Overview of the CoverageJSON format + 2020-09-17 + + + + Jon Blower, Maik Riechert, Bill Roberts + This Note describes CoverageJSON, a data format for describing coverage data in JavaScript Object Notation (JSON), and provides an overview of its design and capabilities. The primary intended purpose of the format is to enable data transfer between servers and web browsers, to support the development of interactive, data-driven web applications. Coverage data is a term that encompasses many kinds of data whose properties vary with space, time and other dimensions, including (but not limited to) satellite imagery, weather forecasts and river gauge measurements. We describe the motivation and objectives of the format, and provide a high-level overview of its structure and semantics. We compare CoverageJSON with other coverage formats and data models and provide links to tools and libraries that can help users to produce and consume data in this format. This Note does not attempt to describe the full CoverageJSON specification in detail: this is available at the project website. - - 16-034 - - Testbed-12 LiDAR Streaming Engineering Report - 16-034 + Overview of the CoverageJSON format + 16-145 - - The OWS-8 Cross Community Interoperability (CCI) thread was built on progress made in the recent OWS-7 initiative to cover key technology areas that could not be addressed within the scope of that initiative. The OWS-8 CCI thread aimed to increase interoperability within communities sharing geospatial data, including advancing of interoperability among heterogeneous data models, advancing strategies to share styles to provide a more common and automated use of symbology, improvement of KML, and advancing schema automation allowing communities to better share their information artifacts. This OGC engineering report aims to present findings from the portrayal registries as part of the CCI subthread - OWS-8 CCI Portrayal Registries Engineering Report - 11-062r2 - 11-062r2 - David Burggraf, Ron Lake - - + + 06-107r1 - - 2011-11-17 + + + 06-107r1 + Trusted Geo Services IPR + + Trusted Geo Services IPR - OWS-8 CCI Portrayal Registries Engineering Report - + + Cristian Opincaru + 2007-05-07 + The OGC Trusted Geo Services Interoperability Program Report (IPR) provides guidance for the exchange of trusted messages between OGC Web Services and clients for these services. It describes a trust model based on the exchange and brokering of security tokens, as proposed by the OASIS WS-Trust specification [http://docs.oasis-open.org/ws-sx/ws-trust/200512]. - - 2011-12-19 - - - - 11-169 - This Discussion Paper describes a lightweight SOS 2.0 profile for stationary in-situ sensors. Besides the SOS itself this document also addresses the data formats used by the SOS: Observations & Measurements 2.0 (O&M) for encoding measurement data and the Sensor Model Language 2.0 (SensorML) for encoding metadata. Other SWE standards which provide more specialized functionality are not part of this minimum lightweight SWE profile. -The aim of this document is to present a common minimum profile of the SOS. The profile is intended to reduce the complexity of the standard by omitting highly specific elements that are not necessary for the majority of use cases that occur in practice. At the same time, the profile is designed in such a way that all SOS implementations that conform to this profile are also compliant to the according OGC specifications. - Lightweight SOS Profile for Stationary In-Situ Sensors Discussion Paper - Lightweight SOS Profile for Stationary In-Situ Sensors Discussion Paper - 11-169 - Simon Jirka, Christoph Stasch, Arne Bröring - - + + + 03-064r10 + Geographic Objects Implementation Specification *RETIRED* + 2005-05-04 + 03-064r10 + Greg Reynolds + *THIS STANDARD HAS BEEN RETIRED* + +The OpenGIS® Geographic Objects Interface Standard (GOS) provides an open set of common, lightweight, language-independent abstractions for describing, managing, rendering, and manipulating geometric and geographic objects within an application programming environment. It provides both an abstract object standard (in UML) and a programming-language-specific profile (in Java). The language-specific bindings serve as an open Application Program Interface (API). - - - 09-012 - OWS-6 Symbology-Encoding Harmonization ER - 09-012 - - This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the harmonization of OGC Styled Layer Descriptor (SLD) and Symbology Encoding (SE) symbology formats with ISO 19117 symbology format, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology. - 2009-08-17 - OWS-6 Symbology-Encoding Harmonization ER + OpenGIS Geographic Objects Implementation Specification *RETIRED* + + + + + - + + 02-061r1 + 02-061r1 + Web Coordinate Transformation Service + Web Coordinate Transformation Service - - Craig Bruce + + + + This document specifies the transformations of geo-spatial coordinates from one Coordinate Reference System (CRS) into another by means of a Web Service + Andreas Poth, Markus Muller + 2002-09-15 - - Kuan-Mei Chen, Carl Reed - 11-030r1 - Open GeoSMS Standard - Core - 2012-01-19 - - OGC®: Open GeoSMS Standard - Core - + - - + - 11-030r1 - The OpenGIS® Open GeoSMS standard defines an encoding for location enabling a text message to be communicated using a Short Messages System (SMS). + 11-058r1 + *FL Starfish Fungus Language for Sensor Description + Ingo Simonis, Chrsitian Malewski + + *FL Starfish Fungus Language for Sensor Description + 11-058r1 + + + The Starfish Fungus Language was developed in response to the high number of complaints addressing issues with the OGC standard Sensor Model Language, SensorML. Most complaints circled around the high flexibility of the language in combination with unnecessary abstractions of technical terms, e.g. every sensor is not a sensor but a process. Most beginners struggled with the composite pattern of those processes, as there is no well-defined rule what needs to be described where. As a beginner, it is almost impossible to write a simple sensor description without getting major guidance through the SensorML development team or other experts. + 2011-07-08 - - Testbed-12 Semantic Enablement Engineering Report - 16-046r1 - 2017-05-12 - - Martin Klopfer - + + 2024-07-01 + 23-040 + OGC Guidance for the Development of Model-Driven Standards + OGC Guidance for the Development of Model-Driven Standards + 23-040 + - - Testbed-12 Semantic Enablement Engineering Report - 16-046r1 - The requirement for capabilities supporting semantic understanding and reasoning in geospatial intelligence (GEOINT) is an all-encompassing paradigm shift from the past. Standards play a critical role in ensuring this is accomplished in a consistent and repeatable manner. Semantic standards and services supporting semantic capabilities are at a relatively early stage of development. Interoperability between semantic standards for encoding relationships and Web based services for discovery, access, retrieval and visualization of those relationships requires more testing and evaluation. This engineering report (ER) highlights the key findings and discussions from Testbed-12 that enable semantic interoperability, including semantic mediation, schema registries, and SPARQL endpoints. It references key findings from the Semantic Portrayal ER and helps to understand the current OGC discussion on semantics in general. - + + Ronald Tse, Carsten Roensdorf, Allan Jamieson, Nick Nicholas, Jeffrey Lau + + This OGC Discussion Paper provides guidelines on how to create a specification of a conceptual model through use of a Unified Modeling Language (UML) editor and an AsciiDoc compiler. This document references Sparx Systems Enterprise Architect and the Metanorma AsciiDoc toolchain in examples that implement the OGC model-driven standards process, described in OGC 21-035r1. + - - 08-059r3 - Web Coverage Service (WCS) - Processing Extension (WCPS) - 08-059r3 - 2009-03-25 - The OpenGIS® Web Coverage Service Interface Standard (WCS) defines a protocol-independent language for the extraction, processing, and analysis of multi-dimensional gridded [[http://www.opengeospatial.org/ogc/glossary/c | coverages]] representing sensor, image, or statistics data. Services implementing this language provide access to original or derived sets of geospatial coverage information, in forms that are useful for client-side rendering, input into scientific models, and other client applications. + + + With the consolidation of tiling services and the increasing number of instances implementing the WMTS standard, there is a need for having a way to transfer a collection of tiles from one service to another. This might also be useful to transfer all necessary tiles from a WMTS service to a GeoPackage. Currently the only available solution is a client that is able to resolve the identifiers of the tiles needed and that builds a WMTS independent request for each tile. This ER explores different solutions that are more appropriate depending on how many tiles we need to move and the final application of them. Some of the proposed solutions involve changes in the WMTS standard and the use of a WPS. The WPS standard also shows some limitations and extensions that should be addressed. -Further information about WPCS can be found at the [[http://www.ogcnetwork.net/wcps | WCPS Service]] page of the OGC Network. - - +In essence all solutions should describe two things: A request that contains a filter to a collection of tiles filling regions of the space and a multipart response that contains the tiles preferably in a single package. Depending on the proposed architecture, these tasks are done directly in the client, in the WMTS server or in an intermediate WPS. - Peter Baumann - - - - OpenGIS Web Coverage Service (WCS) - Processing Extension (WCPS) - - - 20-083r2 - 2021-05-10 - Josh Lieberman - This report details the results of the OGC Building Energy Mapping and Analysis Concept Development Study (BEMA CDS). Sponsored by NRCan and drawing on numerous previous studies, the CDS released a Request for Information on building energy data and applications. The responses were presented and validated in 3 public workshops and form the basis for an Energy SDI notional architecture. - 20-083r2 - Building Energy Mapping and Analytics: Concept Development Study Report - Building Energy Mapping and Analytics: Concept Development Study Report + Testbed-12 Multi-Tile Retrieval ER + 16-049r1 - - + + Testbed-12 Multi-Tile Retrieval ER - + 2017-06-16 + Joan Masó + 16-049r1 - - 09-085r2 - Grid coverage Coordinate Reference Systems (CRSs) - - 09-085r2 - - 2009-10-13 - Grid coverage Coordinate Reference Systems (CRSs) - Arliss Whiteside + + 2010-03-22 + 10-001 - - - This document summarizes the types of Coordinate Reference Systems (CRSs) that are recommended for use with grid (including image) coverages. This document specializes Best Practice Paper OGC 09-076r3 “Uses and Summary of Topic 2: Spatial referencing by coordinates” for grid coverages. Topic 2 is almost the same as ISO 19111:2007, but includes some corrections. This document includes some best practices for defining and using ImageCRSs and other CRSs for grid coverages. - - - + SANY Fusion and Modelling Architecture + This document reports the considered SANY best practice for using OGC standards to provide generic fusion processing services. Concrete case studies are documented and a detailed appendix is provided with example of XML request and responses. + + Stuart E. Middleton + 10-001 + SANY Fusion and Modelling Architecture + - 2024-04-26 - OGC Disaster Pilot: Provider Readiness Guide - 21-074r2 - Disasters are geographic events and, therefore, geospatial information, tools, and applications have the potential to support the management of, and response to, disaster scenarios to save lives and limit damage. - -The use of geospatial data varies significantly across disaster and emergency communities, making the exploitation of geospatial information across a community more difficult. The issue is particularly noticeable when sharing between different organizations involved in disaster response. + + + + + This OGC Engineering Report (ER) describes the application and use of OGC Web Services (OWS) for integrating Machine Learning (ML), Deep Learning (DL) and Artificial Intelligence (AI) in the OGC Testbed-14 Modeling, Portrayal, and Quality of Service (MoPoQ) Thread. This report is intended to present a holistic approach on how to support and integrate emerging AI and ML tools using OWS, as well as publishing their input and outputs. This approach should seek efficiency and effectiveness of knowledge sharing. -This difficulty can be mitigated by establishing the right processes to enable data to be shared smoothly and efficiently within a disaster and emergency community. To do this requires the right partnerships, policies, standards, architecture, and technologies to be in place before the disaster strikes. Having such a set-up will enable the technological and human capabilities to quickly find, access, share, integrate, and visualize a range of actionable geospatial information, and provide this rapidly to disaster response managers and first responders. +This engineering report will describe: experiences, lessons learned, best practices for workflows, service interaction patterns, application schemas, and use of controlled vocabularies. It is expected that the description of workflows for geospatial feature extraction will be more complex than the implementations found in the deliverables. + 18-038r2 + 18-038r2 + Machine Learning Engineering Report + + + + OGC Testbed-14: Machine Learning Engineering Report + 2019-02-04 + Tom Landry + + + + + 18-026r1 + + This Security Engineering Report (ER) covers several OGC Testbed-14 topics: -For over 20 years, the Open Geospatial Consortium (OGC) has been working on the challenges of information sharing for emergency and disaster planning, management, and response. In Disaster Pilot 23 (DP23) the aims were to: +Best practices for the integration of OAuth2.0/OpenID Connect services -develop flexible, scalable, timely and resilient information data workflows to support critical disaster management decisions, enabling stakeholder collaboration; and -provide applications and visualization tools to promote the wider understanding of how geospatial data can support emergency and disaster communities. -The Disaster Pilot Provider Guide describes the technical requirements, data structures, and operational standards required to implement the data flows or tools developed in DP23 and Disaster Pilot 21 (DP21) where participants have worked on disaster scenarios relating to the following. +Mediation services for different security environments -Droughts -Wildland Fires -Flooding -Landslides -Health & Earth Observation Data for Pandemic Response -Case Studies have focused on the hazards of drought in Manitoba, Canada; wildland fires in the western United States; flooding in the Red River basin, Canada; landslides and flooding in Peru; and pandemic response in Louisiana, United States. The participants have developed a series of data specific workflows to generate either Analysis Ready Datasets (ARD) or Decision Ready Indicators (DRI) alongside a number of tools and applications to support data discovery, collection, or visualization. +Federated identity management -Annex A describes the tools and applications developed within the Pilots along with technical details and the benefits offered similar to the data flows. The Guide finishes with details of future possibilities and where the Disaster Pilot initiatives could focus next. Annexes B to E give descriptions of the data flows developed, including technical details of input data, processing and transformations undertaken, standards applied, and outputs produced with details of the aspect of disaster management or response supported, benefits offered, and the type of decisions assisted with. +Securitization of workflows -The Provider Guide is one of three Guides produced within DP23 together with the User Guide and the Operational Capacity Guide. While the Guides are separate individual documents, the Provider and User Guides work together, mirroring each other in terms of structure. The Operational Capacity Guide is a stand-alone document effectively underpinning the other two. +The first two topics are the main focus of this ER. During this Testbed, a server that provides OAuth2.0 and OpenID Connect capabilities was extended with a mediation service that allows for a centralized security authority with users/clients that implement different security standards. - - +The remaining two topics will expand on the close relationship between Security, Workflows and Federated Clouds and the respective implementation challenges. On these specific topics, this ER also outlines and provides a proof-of-concept for a simplistic architecture approach that explores one of several Federated Clouds architectures. + + + 18-026r1 + Security Engineering Report + Juan José Doval, Héctor Rodríguez + - OGC Disaster Pilot: Provider Readiness Guide - Samantha Lavender, Andrew Lavender - - 21-074r2 + OGC Testbed-14: Security Engineering Report + 2019-03-05 - + + Topic 2 - Spatial referencing by coordinates + 08-015r2 + Roger Lott + + + 08-015r2 + - - - - Testbed-12 Asynchronous Messaging for Aviation - 2017-04-25 - Matthes Rieke, Aleksandar Balaban - The Asynchronous Messaging for Aviation Engineering Report (ER) focuses on the design of an architecture to create an Publish/Subscribe (PubSub) messaging layer between different Aviation components such as clients, data provider instances and Data Brokers. In order to achieve interoperability among these components, the OGC PubSub 1.0 standard forms the basis of this architecture. The design of this architecture will cover methods for subscribing for specific subsets of data (e.g. Flight Information Exchange Model (FIXM) Flights intersecting a given Airspace), managing such subscriptions as well as publishing data to the Asynchronous Messaging Server. Different delivery methods such as Advanced Message Queuing Protocol (AMQP) 1.0, Java Message Service (JMS) and OASIS WS-Notification are considered. In particular, their harmonization with OGC PubSub 1.0 is evaluated. - -This report focuses on the interface design required to define an interoperable approach for Aviation using this OGC PubSub 1.0. Specific service level integrations (i.e., Federal Aviation Administration (FAA) System-Wide Information Management (SWIM) and Single European Sky ATM Research Programme (SESAR) SWIM) have been investigated but an implementation has not been fulfilled. - Testbed-12 Asynchronous Messaging for Aviation - 16-017 - - 16-017 - - - - KML 2.3 - 12-007r2 - KML is an XML grammar used to encode and transport representations of geographic data for display in an earth browser. Put simply: KML encodes what to show in an earth browser, and how to show it. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard. - -The KML community is wide and varied. Casual users create KML Placemarks to identify their homes, describe journeys, and plan cross-country hikes and cycling ventures. Scientists use KML to provide detailed mappings of resources, models, and trends such as volcanic eruptions, weather patterns, earthquake activity, and mineral deposits. Real estate professionals, architects, and city development agencies use KML to propose construction and visualize plans. Students and teachers use KML to explore people, places, and events, both historic and current. Organizations such as National Geographic, UNESCO, and the Smithsonian have all used KML to display their rich sets of global data. - -KML documents and their related images (if any) may be compressed using the ZIP format into KMZ archives. KML documents and KMZ archives may be shared by e&#8209;mail, hosted locally for sharing within a private internet, or hosted on a web server. - - - 2015-08-04 - 12-007r2 - David Burggraf - - OGC KML 2.3 - + Topic 2 - Spatial referencing by coordinates + 2010-04-27 + This document is consistent with the second edition (2007) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2007] - - - - - Topic 02.1 - Spatial Referencing by Coordinates - Extension for Parametric Values - 10-020 - Paul Cooper - 10-020 + + + + Web Coverage Service (WCS) - Processing Extension (WCPS) + 08-059r3 + OpenGIS Web Coverage Service (WCS) - Processing Extension (WCPS) + + 08-059r3 + + Peter Baumann + 2009-03-25 - 2014-04-16 - - Topic 2.1 - Spatial Referencing by Coordinates - Extension for Parametric Values + The OpenGIS® Web Coverage Service Interface Standard (WCS) defines a protocol-independent language for the extraction, processing, and analysis of multi-dimensional gridded [[http://www.opengeospatial.org/ogc/glossary/c | coverages]] representing sensor, image, or statistics data. Services implementing this language provide access to original or derived sets of geospatial coverage information, in forms that are useful for client-side rendering, input into scientific models, and other client applications. + +Further information about WPCS can be found at the [[http://www.ogcnetwork.net/wcps | WCPS Service]] page of the OGC Network. + + + 2012-04-06 + + OGC® Engineering Report for the OWS Shibboleth Interoperability Experiment + This document reports on outcomes from the OGC Web Services Shibboleth Interoperability Experiment (OSI). The main objective of OSI was to advance the use of Shibboleth (an open source implementation of SAML) as a means of protecting OWS. In the process, OSI helped develop further understanding of this approach to establishing trusted federations of OWS. This report documents these findings and is intended to be of use to those interested in how Shibboleth/SAML access management federations may function as an organisational model for operational Spatial Data Infrastructure. + + 11-019r2 + Engineering Report for the OWS Shibboleth Interoperability Experiment - - - - - OGC Web Services UDDI Experiment - 03-028 - Josh Lieberman, Lou Reich, Peter Vretanos - - 03-028 - 2003-01-17 - This document lists the design principles, requirements, and experimental results for future versions of a potential OGC - UDDI (Universal Discovery, Description, and Integration) profile of the OGC Catalog Implementation Specification. Specifically, it describes the usage scenarios, workplan, and experimental results for discovery of OGC services (including registries) through the UDDI interface using SOAP (Simple Object Access Protocol) messaging protocols. The baseline for this experiment is the specification for UDDI version 2 and use of private UDDI implementations. - - OGC Web Services UDDI Experiment - + Chris Higgins + + + 11-019r2 - - 16-007r5 - - Volume 11: OGC CDB Core Standard Conceptual Model - + + + OGC® Fusion Standards Study Engineering Report + 09-138 + + + 2010-03-21 + George Percivall + + - 2021-02-26 - 16-007r5 - Volume 11: OGC CDB Core Standard Conceptual Model + This OGC Engineering Report (ER) provides discussions and recommendations for information fusion, with a focus on geospatial information. In this ER, fusion is discussed in three categories: sensor fusion, object/feature fusion, and decision fusion. Recommendations in this ER will be considered in the planning of future activities including the OWS-7 Testbed. + 09-138 + Fusion Standards Study Engineering Report + + + 2003-06-27 - - This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB Standard. The objective of this document is to provide an core conceptual model for a CDB data store (repository). The model is represented using UML (Unified Modeling Language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering the UML diagrams and documentation from the original CDB submission OGC Common DataBase Volume 1 Best Practice, 2015 as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113r5]. - Sara Saeedi + Critical Infrastructure Collaborative Environment Architecture: Information Viewpoint - - - 15-120r6 - The CDB standard defines a standardized model and structure for a single, “versionable,” virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. - Volume 0: OGC CDB Companion Primer for the CDB standard (Best Practice) - Carl Reed + + 03-062r1 + Critical Infrastructure Collaborative Environment Architecture: Information Viewpoint + + Richard Martell + + 03-062r1 + *RETIRED* specifies the information viewpoint for the Critical Infrastructure Collaborative Environment (CICE). + + + Units of Measure and Quantity Datatypes + 01-044r2 + Common semantic for units of measurement to be used across all OGC specifications. + 2001-06-15 + - Volume 0: OGC CDB Companion Primer for the CDB standard (Best Practice) - 15-120r6 + John Bobbitt + 01-044r2 + - 2021-02-26 - - - + + + Units of Measure and Quantity Datatypes - - + + 2019-10-23 + 18-089 + Indoor Mapping and Navigation Pilot Engineering Report + OGC Indoor Mapping and Navigation Pilot Engineering Report + - - Guy Schumann, Albert Kettner, Nils Hempelmann - Engineering report for OGC Climate Resilience Pilot - The OGC Climate Resilience Pilot marked the beginning of a series of enduring climate initiatives with the primary goal of evaluating the value chain encompassing raw data to climate information processes within Climate Resilience Information Systems. This includes the transformation of geospatial data into meaningful knowledge for various stakeholders, including decision-makers, scientists, policymakers, data providers, software developers, service providers, and emergency managers. The results of the OGC Climate Resilience Pilot support the location community to develop more powerful visualization and communication tools to accurately address ongoing climate threats such as heat, drought, floods, and wild-fires as well as supporting governments in meeting commitments for their climate strategies. This will be accomplished through evolving geospatial data, technologies, and other capabilities into valuable information for decision-makers, scientists, policymakers, data providers, software developers, and service providers so they can make valuable, informed decisions to improve climate action. One of the most significant challenges so far has been converting the outputs of global and regional climate models into specific impacts and risks at the local level. The climate science community has adopted standards and there are now numerous climate resilience information systems available online, allowing experts to exchange and compare data effectively. However, professionals outside the weather and climate domain, such as planners and GIS analysts working for agencies dealing with climate change impacts, have limited familiarity with and capacity to utilize climate data. + The OGC Indoor Mapping and Navigation Pilot Initiative was sponsored by the National Institute of Standards and Technology (NIST) Public Safety Communications Research (PSCR) Division. This initiative addressed key challenges related to indoor mapping and navigation for the purpose of supporting first responders in fields such as fire-fighting. The focus of this initiative was on developing the capabilities and workflows required for pre-planning operations. This included scanning each building to produce a point cloud dataset and converting this source data into various intermediate forms to support the generation of indoor navigation routes. This Engineering Report (ER) describes the work conducted in this initiative, the lessons learned captured by participants, and future recommendations to support the public safety efforts and interoperability of the standards. It is expected that future OGC initiatives will address the real-time, event-driven aspects of indoor mapping and navigation for first response situations. - - Engineering report for OGC Climate Resilience Pilot - 23-020r2 - 2024-01-29 - - 23-020r2 +First responders typically survey high-risk facilities in their jurisdiction at least once per year as part of a pre-planning process. Pre-planning outputs are often in the form of reports, and first responders may generate their own hand-drawn maps during the process or annotate available floor plans (e.g., from computer-aided design models). Pre-planning is time-consuming, inefficient, and inherently complex considering the information and level of detail that should or could be captured, the lack of automation, and the difficulty identifying notable changes to facilities and infrastructure during successive pre-planning surveys. + +Mobile three-dimensional (3D) Light Detection and Ranging (LiDAR) has been identified as a potentially transformational technology for first responders. Using LiDAR and 360-degree camera imagery, coupled with advanced software processing, first responders could efficiently capture 3D point clouds and a wealth of other information, both observed and derived, while walking through buildings as part of routine pre-planning operations. The use of 3D LiDAR and imagery has many potential upsides beyond just creating point clouds for visualization and mapping (e.g., use in localization, object classification, integration with virtual/augmented reality solutions, change detection, etc.). + 18-089 + Charles Chen + + - + + + This document represents the Engineering Report for the WCPS activity within the OWS-5 SWE thread. It summarizes tasks and outcomes. + 07-166r2 + OWS-5 Engineering Report on WCPS + + OGC OWS-5 Engineering Report on WCPS + + Peter Baumann + 2008-08-04 - + + 07-166r2 - + + + Peter Schut + 2005-06-17 + - OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report - Akiko Sato, Nobuhiro Ishimaru, Guo Tao, Masaaki Tanizaki - 09-067r2 - OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report - - This document described the Outdoor and Indoor 3D Routing and Services which are used in the OGC OWS-6 Decision Support Systems (DSS) thread. The objective is to enhance a network topology for the current CityGML specification based on the knowledge acquired through the development and experimental evaluation of this project. - 2009-10-09 - 09-067r2 + Web Processing Service + + + 05-007r2 + + A Web Service Processing Service provides access to calculations or models which operate on spatially referenced data. The data required by the service can be available locally, or delivered across a network using data exchange standards such as Geography Markup Language (GML) or Geolinked Data Access Service (GDAS). The calculation can be as simple as subtracting one set of spatially referenced numbers from another (e.g. determining the difference in influenza cases between two different seasons), or as complicated as a global climate change model. + +This specification is intended to provide a mechanism to identify the spatially-referenced data required by the calculation, initiate the calculation, and manage the output from the calculation so that it can be accessed by the client. The Web Processing Service is targeted at both vector and raster data based processing. + + Web Processing Service + 05-007r2 + - - This OGC document provides an analysis of the prototype implementations, approaches and performance aspects of data serialization techniques explored in OGC Testbed 13. Specifically, it describes work done during Testbed 13 investigating serialization for geospatial data sets on OGC Web Feature Service (WFS) using Google Protocol Buffers (Protobuf) and Apache Avro. + + OGC API - Features - Part 2: Coordinate Reference Systems by Reference + + OGC API - Features - Part 2: Coordinate Reference Systems by Reference + 18-058 + + 2020-11-02 + OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks. -Protocol buffers are Google’s language-neutral, platform-neutral, extensible mechanism for serializing structured data. They are described by Google in the following manner - 'think XML, but smaller, faster, and simpler'. With Protobuf Google indicates developers can define how they want their data to be structured once, then they can use special generated source code to easily write and read structured data to and from a variety of data streams and using a variety of languages. Apache Avro is described as a remote procedure call and data serialization framework developed within Apache’s Hadoop project. It uses JavaScript Object Notation(JSON) for defining data types and reportedly serializes data in a compact binary format. - 17-037 - Testbed-13: SWAP Engineering Report - - OGC Testbed-13: SWAP Engineering Report - 2018-01-01 - Jeff Harrison - 17-037 +OGC API Features provides API building blocks to create, modify and query features on the Web. OGC API Features is comprised of multiple parts, each of them is a separate standard. + +This part extends the core capabilities specified in Part 1: Core with the ability to use coordinate reference system identifiers other than the defaults defined in the core. - + Clements Portele, Panagiotis (Peter) A. Vretanos + 18-058 - + - - 04-014r1 - OGC Technical Document Baseline - 2004-04-22 - - - + + Anchor Node Extension in IndoorGML - Seamless Navigation between Indoor and Outdoor Space + 19-004 + + 19-004 + Kyoung-Sook Kim, Jiyeong Lee + 2019-12-11 + This OGC discussion paper provides an extension module of OGC Indoor Geography Markup Language (IndoorGML) for the seamless navigation between indoor and outdoor spaces. The OGC IndoorGML standard has an issue on the data model that affects the connection of indoor and outdoor spaces via an “Anchor Node,” which is a conceptual part for connecting indoor and outdoor spaces. This discussion paper aims to show use cases of how IndoorGML can connect with other geospatial standards that represent outdoor spaces (and road networks), such as OGC City Geography Markup Language (CityGML) and version 5.0 of the Geographic Data Files (GDF) format. - + + Anchor Node Extension in IndoorGML - Seamless Navigation between Indoor and Outdoor Space - Spreadsheet of OGC Technical Document Baseline - 04-014r1 - OGC Technical Document Baseline - Carl Reed, George Percivall + + - + + Modernizing SDI: Enabling Data Interoperability for Regional Assessments and Cumulative Effects CDS + Robert Thomas, Josh Lieberman + 21-013 + 2021-05-27 + + + Modernizing SDI: Enabling Data Interoperability for Regional Assessments and Cumulative Effects CDS + 21-013 + This engineering report (ER) presents the results of a Concept Development Study (CDS) on Modernizing Spatial Data Infrastructure (SDI), sponsored by Natural Resources Canada, executed by the Open Geospatial Consortium (OGC). The focus of this study was to understand how to best support the modernization of SDI(s) by enabling increased data interoperability for Regional Assessments (RA) and Cumulative Effects (CE), to advance the understanding of stakeholder issues, and serve stakeholders’ needs in these contexts. The study was completed through stakeholder engagements including an open Request for Information (RFI) that gathered external international positions and opinions on the optimal setup and design of a modernized SDI. In addition, a stakeholder Modernizing SDI Workshop was also employed providing in depth information on requirements and issues related to stakeholders, architecture, data, and standards of current and future SDI. + +The RFI and workshop also gathered information and provided insight on the current state of SDIs to better support governments, agencies, non-governmental organizations and citizens, unlocking the full societal and economic potential of the wealth of data at national, regional and/or local levels. + +The ER presents an analysis of the RFI and Modernizing SDI Workshop responses and interactions, providing in-depth information on requirements and issues related to stakeholders, architecture, data, standards of current and possible future SDI modernization. All RFI and workshop responses will contribute to SDI modernization efforts moving forward and help to assess interoperability, availability and usability of geospatial Web services and tools across different types of spatial data uses. In addition, the report identifies gaps, and defines core components of a possible future SDI. + +The outflow of this report may be used to help define reference use-cases and scenarios for possible future research and follow-on OGC Innovation Program activities. - 19-065 - Steve Thompson - OpenFlight Scene Description Database Specification 16.0 Community Standard - 19-065 - This document describes the OpenFlight Scene Description Database Specification, commonly -referred to as simply “OpenFlight”. OpenFlight is a 3D scene description file format that was -created and is maintained by Presagis. While OpenFlight databases are typically created and edited -using Presagis software tools, the format is widely adopted and as a result, many tools exist -to read and write OpenFlight database files. -The primary audience for this document includes software developers whose applications are -intended to read and/or write OpenFlight database files. To this end, this document discusses -concepts incorporated in OpenFlight and contains a detailed description of the physical layout -of OpenFlight files as represented on disk. - - + - OGC OpenFlight Scene Description Database Specification 16.0 Community Standard - - 2020-07-09 - - Taehoon Kim, Kyoung-Sook Kim, Jiyeong Lee, Ki-Joune Li - Extensions of IndoorGML 1.1 - Indoor Affordance Spaces - - - - 2022-05-06 - The OGC IndoorGML standard provides a fundamental data model for representing indoor spaces as spatial, topological, and semantic features. The IndoorGML core module allows applications to extend the model with their semantic considerations. For example, the IndoorGML navigation module classifies the basic class of indoor spaces, cell spaces, into navigable or non-navigable spaces. Navigable spaces, in which users can move freely, are specified in two subclasses: transfer spaces (e.g. doors, entrances, hallways) and general spaces (e.g. rooms, terraces, lobbies), based on indoor navigation requirements. This discussion paper proposes an extension to the OGC IndoorGML core module to support new types of location-based services, such as autonomous driving robots, personal experience augmentation with augmented reality (AR) / virtual reality (VR), and facilities management, to understand activities and needs in indoor spaces. The proposed extension consists of three new indoor spaces to represent affordance spaces with structural, functional, and sensory characteristics by leveraging the multi-layered space representation of IndoorGML. - 21-010r2 - Extensions of IndoorGML 1.1 - Indoor Affordance Spaces - 21-010r2 + + + OWS Context Conceptual Model + 12-080r2 + + This standard describes the use cases, requirements and conceptual model for the OWS Context encoding standard. The goal of this standard is to provide a core model, which is extended and encoded as defined in extensions to this standard. A ‘context document’ specifies a fully configured service set which can be exchanged (with a consistent interpretation) among clients supporting the standard. +The OGC Web Services Context Document (OWS Context) was created to allow a set of configured information resources (service set) to be passed between applications primarily as a collection of services. OWS Context is developed to support in-line content as well. The goal is to support use cases such as the distribution of search results, the exchange of a set of resources such as OGC Web Feature Service (WFS), Web Map Service (WMS), Web Map Tile Service (WMTS), Web Coverage Service (WCS) and others in a ‘common operating picture’. Additionally OWS Context can deliver a set of configured processing services (Web Processing Service (WPS)) parameters to allow the processing to be reproduced on different nodes. +OWS Context is aimed at replacing previous OGC attempts at providing such a capability (the Web Map Context WMC) which was reasonably successful but limited to WMS. Other work on the ‘Location Organizer Folder (LOF)’ was also taken into consideration. The concept of OWS Context, and the first prototype document was produced as part of OGC testbed OWS-7. See OGC 10-035r1, Information Sharing Engineering Report. In order to achieve mass market appeal, as well as being useful to a wider community, the use of OWS Context support to other existing standards was considered. Multiple encoding formats for OWS Context have been developed (ATOM, JSON). Each of these is described in a separate OWS Context Extensions to the Core model. +This document concentrates on describing the OWS Context Model in abstract terms using UML. The document defines requirements and use cases. It also includes an abstract test suite to verify that encodings are compliant with the core specification. The intent of OWS Context is to allow many types of OGC Data Delivery service to be referenced and therefore exploited (for example, not just WMS but also WFS, WCS and WPS) but it does not explicitly define the encoding of these services in the core (only the general approach to be used for different types of service interface). Service explicit encodings are defined within the extension documents for ATOM and JSON. +The abbreviation owc is used throughout this document for OWS Context. + + Roger Brackin, Pedro Gonçalves + + 2014-01-22 - + 12-080r2 + OGC OWS Context Conceptual Model + - - 22-049r1 - OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 - 22-049r1 - Andreas Matheus - - The Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 defines a geospatial extension to the OASIS eXtensible Access Control Markup Language (XACML) Version 3.0 Standard. GeoXACML 3.0 supports the interoperable definition of access rights including geographic conditions based on the XACML 3.0 language, processing model and policy schema. GeoXACML 3.0 provides improvements based on enhancements to the XACML Standard, primarily the support of access conditions spanning different XACML categories. This enhancement empowers GeoXACML 3.0 to be a powerful decision engine with support for spatiotemporal access conditions. - -As a result of the XACML 3.0 deployment model and corresponding implementation flexibility, GeoXACML 3.0 can be operated as a traditional Policy Decision Point or as a cloud-native API gateway. + + OGC API - Tiles - Part 1: Core + 20-057 + + OGC API — Tiles is a standard defining building blocks for creating Web APIs that support the retrieval of geospatial information as tiles. Different forms of geospatial information are supported, such as tiles of vector features (“vector tiles”), coverages, maps (or imagery) and other types of geospatial information. Although it can be used independently, the OGC API — Tiles building blocks can be combined with other OGC API Standards and draft specifications for additional capabilities or increasing interoperability for specific types of data. The OGC API — Tiles standard references the OGC Two Dimensional Tile Matrix Set (TMS) and Tileset Metadata standard, which defines logical models and encodings for specifying tile matrix sets and describing tile sets. A tile matrix set is a tiling scheme that enables an application to partition and index space based on a set of regular grids defined for multiple scales in a Coordinate Reference System (CRS). -The OGC GeoXACML 3.0 Standard defines different conformance classes that supports flexible implementation conformance. Implementation of the Core conformance class supports the ISO 19125 geometry model including topological test (spatial relations) functions which enables the indexing of access conditions-based geometry. The Spatial Analysis conformance class extends the topological test functions for defining access conditions including the processing of geometries. To support condition evaluation for geometries encoded in different Coordinate Reference System (CRS), the CRS Transformation conformance class enables a compliant implementation to undertake dynamic CRS transformation during decision-making unless prohibited per request. Finally, the API conformance class enables operating a GeoXACML 3.0 compliant implementation as an OGC API conformant service (Policy Decision Point). - +This specification is a successor to the OGC’s Web Map Tile Service (WMTS) standard, focusing on simple reusable REST API building blocks which can be described using the OpenAPI specification. Whereas WMTS focused on map tiles, the OGC API — Tiles standard has been designed to support any form of tiled data. - 2023-09-21 - + + 20-057 + - OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 + Joan Masó, Jérôme Jacovella-St-Louis + OGC API - Tiles - Part 1: Core + 2022-11-10 - - 2005-05-03 - 04-095c1 - Filter Encoding Implementation Specification Corrigendum 1 - The OpenGIS® Filter Encoding Standard (FES) defines an XML encoding for filter expressions. A filter expression logically combines constraints on the -properties of a feature in order to identify a particular subset of features to be operated upon. For example, a subset of features might be identified to render them in a particular color or convert them into a user-specified format. Constraints can be specified on values of spatial, temporal and scalar properties. An example of a filter is: Find all the properties in Omstead County owned by Peter Vretanos. + + + 17-066r2 + OGC GeoPackage Extension for Tiled Gridded Coverage Data + 2022-05-02 + + The GeoPackage Extension for Tiled Gridded Coverage Data” (TGCE) extension (previously titled Elevation Extension) defines how to encode and store tiled regular gridded data, such as a digital elevation model, in a GeoPackage. The tiles contain values, such as elevation, temperature or pressure, and the extension defines two encodings. The PNG encoding uses PNG files to store 16-bit integer values and a scale and offset may be applied to fine-tune the coverage range. To support 32-bit floating point data or binary data, the extension also defines a TIFF encoding. In this encoding, TIFF files are used to store IEEE floating point or a binary data type where the SampleFormat has a value of either 1 (unsigned integer) or 2 (signed integer) AND the BitsPerSample is either 8, 16, or 32. To simplify development, this encoding constrains many of the TIFF options to the minimal set needed to meet the floating-point requirement. The extension also defines two ancillary data tables: one for regular gridded coverages and one for tiles. -This standard is used by a number of OGC Web Services, including the Web Feature Service [http://www.opengeospatial.org/standards/wfs], the Catalogue Service [http://www.opengeospatial.org/standards/cat] and the Styled Layer Descriptor Standard [http://www.opengeospatial.org/standards/sld]. - 04-095c1 - Filter Encoding Implementation Specification Corrigendum 1 - - - - - - Peter Vretanos + 17-066r2 + + Carl Reed + + OGC GeoPackage Extension for Tiled Gridded Coverage Data + - - Testbed-12 Multi-Tile Retrieval ER - 16-049r1 - - + + Milan Trninic - Testbed-12 Multi-Tile Retrieval ER - 16-049r1 - + Symbology Management + 05-112 - - 2017-06-16 - Joan Masó - With the consolidation of tiling services and the increasing number of instances implementing the WMTS standard, there is a need for having a way to transfer a collection of tiles from one service to another. This might also be useful to transfer all necessary tiles from a WMTS service to a GeoPackage. Currently the only available solution is a client that is able to resolve the identifiers of the tiles needed and that builds a WMTS independent request for each tile. This ER explores different solutions that are more appropriate depending on how many tiles we need to move and the final application of them. Some of the proposed solutions involve changes in the WMTS standard and the use of a WPS. The WPS standard also shows some limitations and extensions that should be addressed. - -In essence all solutions should describe two things: A request that contains a filter to a collection of tiles filling regions of the space and a multipart response that contains the tiles preferably in a single package. Depending on the proposed architecture, these tasks are done directly in the client, in the WMTS server or in an intermediate WPS. + + 05-112 + + + This document describes Symbology Management System which is a system closely related to OpenGIS Style Management Services (SMS) (described in the document OGC 04-040). Having in mind their identical purpose, the system described in this document will also be referred to as SMS. +The SMS manages styles and symbols and defines their use in the process of producing maps from source GML data. + + 2006-04-19 + + Symbology Management - + - Results of the Auth IE are presented in this Engineering Report document and serve as guidance to both implementers and organizations deploying solutions that involve basic authentication. It is the belief of the Auth IE participants that if such a document is made available to the community more OGC implementing products will natively support authentication. - - Authentication IE Enginerring Report + Incident Management Information Sharing (IMIS) Internet of Things (IoT) Architecture Engineering Report + 16-014r2 - - Authentication IE Enginerring Report - 10-192 - 2011-01-03 - 10-192 - Jeff Harrison - + 16-014r2 + Greg Schumann, Josh Lieberman + 2018-04-26 + The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives. +• Apply Open Geospatial Consortium (OGC) principles and practices for collaborative development to existing standards and technology to prototype an IoT approach to sensor use for incident management. +• Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability. +• Develop profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability. +• Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario. + + + + + Incident Management Information Sharing (IMIS) Internet of Things (IoT) Architecture Engineering Report - - 10-070r2 - This document is the specification for a Table Joining Service (TJS). This OGC standard defines a simple way to describe and exchange tabular data that contains information about geographic objects. - 2010-11-22 - - Georeferenced Table Joining Service Implementation Standard - 10-070r2 - OpenGIS® Georeferenced Table Joining Service Implementation Standard - Peter Schut - + + A Use-Case for Mobile Location Services with IndoorGML - Indoor Navigation for Visually Impaired People + + A Use-Case for Mobile Location Services with IndoorGML - Indoor Navigation for Visually Impaired People + 15-075r1 - - + This OGC Discussion Paper provides a navigation use-case for the use of IndoorGML for mobile location services (MLS). In particular, the Discussion Paper explains how the OGC IndoorGML standard can be applied to a MLS application for visually impaired people in indoor space. Finally, a prototype development of the application on Android smart phone is described in this report. + + Ki-Joune Li, Hyung-Gyu Ryu, Taehoon Kim, and Hack-Cheol Kim + + 15-075r1 + + 2015-11-19 - - - Web Map Service - 01-068r3 - Provides three operations protocols (GetCapabilities, GetMap, and GetFeatureInfo) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. + + Local MSD Implementation Profile (GML 3.2.1) + + Local MSD Implementation Profile (GML 3.2.1) + 07-027r1 + 2007-05-25 + Clemens Portele + This document contains a data content specification for Local Mission Specific Data (MSD) and is based on the GEOINT Structure Implementation Profile (GSIP) developed by the NGA. This document defines the GML 3.2.1 (ISO 19136) encoding requirements for Local MSD. The structure of the document is based on ISO/DIS 19131 (Geographic Information - Web Map Service - 2002-04-18 - + 07-027r1 - - - 01-068r3 - Jeff de La Beaujardiere + + + - - - - 14-017 - - This Engineering Report was prepared as a deliverable for OGC Testbed 10, an initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Open Mobility thread within the testbed. -The Engineering Report describes and evaluates options for integrating OWS Context documents in requests for information based on the National Information Exchange Model (NIEM). - - OGC® Testbed 10 OWS Context in NIEM Engineering Report + + This OGC document provides an analysis of the prototype implementations, approaches and performance aspects of data serialization techniques explored in OGC Testbed 13. Specifically, it describes work done during Testbed 13 investigating serialization for geospatial data sets on OGC Web Feature Service (WFS) using Google Protocol Buffers (Protobuf) and Apache Avro. + +Protocol buffers are Google’s language-neutral, platform-neutral, extensible mechanism for serializing structured data. They are described by Google in the following manner - 'think XML, but smaller, faster, and simpler'. With Protobuf Google indicates developers can define how they want their data to be structured once, then they can use special generated source code to easily write and read structured data to and from a variety of data streams and using a variety of languages. Apache Avro is described as a remote procedure call and data serialization framework developed within Apache’s Hadoop project. It uses JavaScript Object Notation(JSON) for defining data types and reportedly serializes data in a compact binary format. + + OGC Testbed-13: SWAP Engineering Report + 17-037 + Testbed-13: SWAP Engineering Report + + 2018-01-01 + 17-037 - Testbed 10 OWS Context in NIEM Engineering Report - 14-017 - Gobe Hobona, Roger Brackin - 2014-04-28 - - - - GML Application Schema for EO Products - 06-080r2 - GML Application Schema for EO Products - 06-080r2 - - - - - This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGC - Jerome Gasperi - 2007-08-16 + Jeff Harrison - - This OGC Testbed-18 (TB-18) Features Filtering Summary Engineering Report (ER) summarizes the implementations, findings, and recommendations that emerged from the efforts to better understand the current OGC API-Features filtering capabilities and limitations and how filtering can be decoupled from data services. - -This ER describes: - -* two façades built to interface SWIM services and serve aviation data through APIs (built with OGC API Standards) including basic filtering capabilities; -* the two filtering services built to consume SWIM data and serve it through OGC based APIs featuring advanced filtering mechanism; -* the client application built to interface with the filtering services; and -* the developer client built to define filter statements that can be expressed in a machine-readable way and exchanged with the filtering service. - - 22-023r2 - 22-023r2 - Testbed-18: Features Filtering Summary Engineering Report + + + + + + + + + + + + + + + + + + + + + + + + + + Documents of type OGC Implementation Specification Corrigendum + Documents of type OGC Implementation Specification Corrigendum + Documents of type OGC Implementation Specification Corrigendum + + + + - Testbed-18: Features Filtering Summary Engineering Report + Web Processing Service + + + This document specifies the interface to a Web Processing Service (WPS). A WPS can be configured to offer any sort of GIS functionality to clients across a network, including access to pre-programmed calculations and/or computation models that operate on spatially referenced data. A WPS may offer calculations as simple as subtracting one set of spatially referenced numbers from another (e.g., determining the difference in influenza cases between two different seasons), or as complicated as a global climate change model. The data required by the WPS can be delivered across a network, or available at the server. + Web Processing Service + 05-007r4 + + Peter Schut, Arliss Whiteside + + 2005-09-16 + 05-007r4 + + - Sergio Taleisnik + 16-047r1 + 16-047r1 + Testbed-12 General Feature Model Engineering Report + + + 2017-05-12 + + Martin Klopfer + Testbed-12 General Feature Model Engineering Report + With a growing requirement to carry out complex analysis in large multi-disciplinary, heterogeneous data collections, an approach is required to extract equivalent information from dissimilar content. The more information can be normalized, the easier it will be to correlate the content. Given that almost all data has a spatio-temporal component, this ER will look into the idea of defining a Spatial-Temporal Service and analyze which collection of data types, operations and architecture patterns would be necessary to spatial-temporal enable any content. This OGC® document reviews the General Feature Model and gives guidelines for necessary modifications to broaden its scope, so that it can be re-used for non-geospatial centric applications and extended as necessary into a general model for all object types. - 2023-07-14 - - OGC MetOcean Application profile for WCS2.1: Part 2 MetOcean GetPolygon Extension - - - 17-086r3 - The purpose of the GetPolygon operation is to extract data contained within a polygon defined either by a set of points or the radius and position of a circle point. The need for the GetPolygon operation stems from active members of the OGC MetOcean Domain Working Group (DWG) who saw a manifest need for extraction of such information from gridded datasets. + + + 17-014r8 + OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.2 + + + The Indexed 3D Scene Layer (I3S) format is an open 3D content delivery format used to rapidly stream and distribute large volumes of 3D GIS data to mobile, web and desktop clients. I3S content can be shared across enterprise systems using both physical and cloud servers. -This work has been done by members of the OGC MetOcean Domain Working Group. - - - 17-086r3 - MetOcean Application profile for WCS2.1: Part 2 MetOcean GetPolygon Extension +A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files. + +The delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types. + +The open community GitHub source for this Community Standard is here. + + Carl Reed, Tamrat Belayneh + 17-014r8 + 2021-12-15 + OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.2 - - 2021-03-22 - Peter Trevelyan, Paul Hershberg, Steve Olson - - - - 05-047r2 - GML in JPEG 2000 for Geographic Imagery + + + OWS-7 Web Processing Service Profiling Engineering Report + 10-059r2 + Christian Kiehle, Theodor Foerster + + + 2010-08-18 + + OWS-7 Web Processing Service Profiling Engineering Report + The overall scope of this OWS-7 Engineering Report is to clarify how to write and register a WPS profile. WPS profiles enable clients to search and identify equivalent WPS-based processes distributed on the web. Therefore, this ER provides guidelines for designing WPS Profiles based on WPS interface specification 1.0.0. + - The GML (Geography Markup Language) is an XML grammar for the encoding geographic information including geographic features, coverages, observations, topology, geometry, coordinate reference systems, units of measure, time, and value objects. -JPEG 2000 is a wavelet based encoding for imagery that provides the ability to include XML data for description of the image within the JPEG 2000 data file. -This specification defines the means by which GML is to be used within JPEG 2000 images for geographic imagery. This includes the following: - - GML in JPEG 2000 for Geographic Imagery - 05-047r2 - 2005-03-28 - - - Ron Lake + 10-059r2 - - 2006-07-19 - 06-111 - GML 3.1.1 grid CRSs Profile Corrigendum - 06-111 - Arliss Whiteside - + - GML 3.1.1 grid CRSs Profile Corrigendum + + GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core + 08-085r4 + OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core + + + + 08-085r4 + This standard applies to the encoding and decoding of JPEG 2000 images that contain GML for use with geographic imagery. + +This document specifies the use of the Geography Markup Language (GML) within the XML boxes of the JPEG 2000 data format and provides an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations. The document also specifies the encoding and packaging rules for GML use in JPEG 2000. + 2014-09-23 + Lucio Colaiacomo, Joan Masó, Emmanuel Devys - - - - This document is a corrigendum for OGC Document 05-096r1, titled GML 3.1.1 grid CRSs profile. This corrigendum is based on change request OGC 06-041. - - 11-163 - - NetCDF Uncertainty Conventions + + 08-125r1 + KML Standard Development Best Practices + Tim Wilson, David Burggraf + 2009-02-04 + 08-125r1 + OGC® KML Standard Development Best Practices + - - Lorenzo Bigagli, StefanoNativi + - 11-163 - NetCDF Uncertainty Conventions - - - 2013-01-17 - This Discussion Paperproposes a set of conventions for managing uncertainty information within the netCDF3 data model and format: the NetCDF Uncertainty Conventions (NetCDF-U). + + + This OGC® Best Practices Document provides guidelines for developing the OGC KML standard in a manner that best serves and supports the KML application developer and user communities. It applies to the extension of KML by application developers and the subsequent enhancement of the KML standard by the OGC. - - + + OGC® Testbed11 Referenceable Grid Harmonization Engineering Report + 15-065r1 + Testbed11 Referenceable Grid Harmonization Engineering Report + + 2015-11-18 - Testbed-13: DCAT/SRIM Engineering Report - 17-040 + Eric Hirschorn, Peter Baumann + This Engineering Report is a deliverable of the Testbed-11 Urban Climate Resilience (UCR) Thread. The UCR Thread responds to the urgent need to make climate information and related data readily available for the public and government decision makers to prepare for changes in the Earth’s climate. An important set of a data sources that will play an important role in detecting changes due to climate effects are a wide array of remote imaging systems. + 15-065r1 + - - 2018-01-08 - Stephen McCann, Roger Brackin, Gobe Hobona - - This engineering report captures the requirements, solutions, and implementation experiences of the Semantic Registry work package in Testbed-13. The engineering report describes the implementation of a RESTful Semantic Registry that supports the Semantic Registry Information Model (SRIM) which is based on the Data Catalog (DCAT) specification. A discussion of the applicability of the SRIM to the United States Geological Survey (USGS) and the National Geospatial Intelligence Agency (NGA) metadata is also presented, including an analysis of a set of controlled vocabularies from both organizations. Best Practice guidelines for the use of SRIM are also provided. The engineering report discusses the application of Shapes Constraint Language (SHACL) to aspects of Linked Data. Recognizing the benefits that asynchronous access has to offer web services, a description of the work undertaken by the testbed in implementing publish/subscribe functionality between a Semantic Registry and a Catalogue Service for the Web (CSW) is also presented. - 17-040 - OGC Testbed-13: DCAT/SRIM Engineering Report + - + + + - 19-021 - + OGC GGXF geodetic data grid exchange format + 22-051r7 + + + 22-051r7 + The Geodetic data Grid eXchange Format (GGXF) is designed to be a single file format that may be used +for a wide range of geodetic applications requiring interpolation of regularly gridded data, including (but +not limited to): +• Transformation of latitude and longitude coordinates from one geodetic coordinate reference +system to another; +• Transformation of gravity-related heights from one vertical coordinate reference system to +another; +• Reduction of ellipsoid heights to the geoid, quasi-geoid or a surface of a vertical reference frame; +and +• The description of coordinate changes due to deformation. +The GGXF format has been designed specifically for carrying gridded geodetic parameters supporting +coordinate transformations and point motion operations but has no restriction on the type of content +that may be included. + 2024-04-29 + + Roger Lott + OGC GGXF geodetic data grid exchange format + + + This OpenGIS Recommendation Paper specifies basic XML encoding of data defining coordinate reference systems and coordinate operations. This encoding is expected to be adapted and used by multiple OGC +Implementation Specifications, by the separate specification of Application Schemas. This document is a Recommendation Paper because the specified encoding is more general +than an OpenGIS Implementation Specification and more specific than the OpenGIS Abstract Specification. + Recommended XML Encoding of CRS Definitions + 03-010r7 + + Arliss Whiteside + + 03-010r7 + Recommended XML Encoding of CRS Definitions + - - This OGC Testbed 15 Engineering Report (ER) describes a generalized approach towards performing data fusion from multiple heterogeneous geospatial linked data sources. The specific use case is semantic enrichment of hydrographic features provided by Natural Resources Canada (NRCan). The ER attempts to define and formalize the integration pipeline necessary to perform a fusion process for producing semantically coherent fused entities. - 2019-12-17 - OGC Testbed-15: Semantic Web Link Builder and Triple Generator - Esther Kok, Stephane Fellah - - 19-021 - OGC Testbed-15: Semantic Web Link Builder and Triple Generator + 2003-05-21 + - - Cliff Kottman - - A feature object (in software) corresponds to a real world or abstract entity. - 99-105r2 - Topic 05 - Features - 99-105r2 + + + + Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf + + This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange. + 18-075 + Moving Features Encoding Part I: XML Core + + OGC® Moving Features Encoding Part I: XML Core + 18-075 + + 2019-01-14 + + + 05-088r1 + Arthur Na, Mark Priest + + 05-088r1 + Sensor Observation Service - 1999-03-24 - Topic 5 - Features + + A Sensor Observation Service provides an API for managing deployed sensors and retrieving sensor data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today. - - + 2006-01-18 + + Sensor Observation Service + - - The Web Image Classification Service (WICS) supports classification of digital images. A digital image is composed of pixel values organized into one or more two-dimensional arrays. The two dimensions of an image represent two axes in space based on a spatial coordinate reference system. The dimensions of the different 2-D arrays comprising an image must be the same and represent exactly the same spatial locations. - 05-017 - Web Image Classification Service (WICS) - 2005-02-10 - Wenli Yang, Arliss Whiteside + + + 06-141r6 + Ordering Services Framework for Earth Observation Products Interface Standard + Ordering Services Framework for Earth Observation Products Interface Standard + + This OGC® standard specifies the interfaces, bindings, requirements, conformance classes, and a framework for implementing extensions that enable complete workflows for ordering of Earth Observation (EO) data products. + + 2012-01-09 + 06-141r6 + + Daniele Marchionni, Stefania Pappagallo + + + + Jérôme Jacovella-St-Louis + + - 05-017 - Web Image Classification Service (WICS) - - - - - - 2019-03-06 - This is the second Engineering Report (ER) about the Map Markup Language (MapML) cite:[Rushforth2018] resulting from OGC Testbed initiatives. To find an introduction of MapML and how it works, please, refer to the previous ER OGC 17-019 cite:[Maso2018]. MapML is a new media type that can be included in a <layer> element of a <map> section, in a Hypertext Markup Language (HTML) page. This document is mainly focused on the description of the MapML media type and its evolutions. In particular, it considers issues about the Coordinate Reference System (CRS) types in MapML, feature and properties encoding, Cascading Style Sheets (CSS) symbolization, multidimensional data etc. + 18-025 + OGC Testbed-14: CityGML and AR Engineering Report + 18-025 + CityGML and AR Engineering Report + + This OGC Testbed-14 Engineering Report (ER) describes the results of the Augmented Reality (AR) work performed in the Testbed-14 CityGML and Augmented Reality work package which was part of the Next Generation Services thread. -This document describes two implementations done in OGC Testbed-14: a Cloud-based Proxy (cascade) for MapML done by CubeWerx and a ServiceWorker Proxy for MapML done by George Mason University (GMU). +By integrating information available from urban models within a view of the real world through a mobile device, this testbed activity explored the possibilities offered by AR in a geospatial context. The ER additionally discusses the approach used to bring in these urban models from various data sources. The experiments also covered to some extent Virtual Reality (VR) where any city can be explored freely from a computer display or potentially within a VR headset. -Finally, this document reviews how the next generation of OGC services can integrate MapML files as part of the designing of use cases and discusses how MapML can be used by social media. +A continuation of these experiments would have looked at a combination of Augmented and Virtual Reality (Mixed Reality). The portrayal of AR and three-dimensional (3D) content through extending a common conceptual model to style classic geospatial features (as explored in the Testbed-14 Portrayal work) is also touched upon. The efficient transmission of 3D content is also a subject of this document through the use of a simple 3D transmission format developed during the initiative. -This document proposals increases functionality in MapML and makes proposals for increasing the interoperability of the proposed encoding with the OGC standards baseline and future generations of OGC standards for maps and tiles. - - - - MapML Engineering Report - 18-023r1 - Joan Masó - +This ER provides many insights that showcase what is now made possible by the combination of AR, VR and integrated urban models. + +The testbed work shines light on the benefits of applying a common portrayal approach to AR, bridging the gap between AR applications and traditional Geographic Information Systems and services. + +The ER introduces a new, simple approach and conceptual model for transmitting 3D geospatial content which could be the basis to define simple profiles for the I3S and 3D Tiles community standards. It could also inform enhancements to the 3D Portrayal Service (3DPS) and/or next generation services (e.g., WFS 3.0) for delivering 3D contents in a format agnostic manner. + +Finally, the ER covers methods to bring in different types of geospatial content from various sources for integration into AR applications. + +During Testbed-14, the participants demonstrated AR experiences with geospatial datasets providing integrated views of urban spaces. Two clients and two services were shown to be interoperable, streaming AR content through a simple 3D transmission format, leveraging either GeoJSON or GNOSIS Map Tiles, as well as E3D 3D model specifications. + +The feasibility of extending a classic portrayal conceptual model for AR was also shown. In order to serve them to the clients in the supported transmission formats, geospatial data sets of various types and in various formats were successfully imported for consumption by the services. - OGC Testbed-14: MapML Engineering Report - - 18-023r1 + 2019-03-07 - - 09-129 - - - AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report - 09-129 - + + EA-SIG Collaboration White Paper + 04-085 - AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report - - 2010-02-16 - Nadine Alameh + + + 04-085 + Richard Creps,Victor Brown,Bill Floyd,John Garcia,Jeff Grinstead,Robert Kraus,Steve Matney,Robert Qu + + 2004-02-20 - This AIP-2 Engineering Report (ER) describes a set of transverse technology Use Cases developed and applied in the GEOSS Architecture Implementation Pilot Phase 2 (AIP-2). Such Use Cases define reusable activities within a service-oriented architecture, tailored for the GEOSS environment. This report contains the general Use Cases that were specialized by community Working Groups to implement several specific Societal Benefit Area (SBA) Scenarios in AIP-2. The SBA Scenarios and specialized use cases are defined in separate AIP-2 ERs. This AIP-2 ER will be offered for consideration by the GEOSS Best Practice Registry editors and to OGC Technical Committee for consideration as a Best Practice. - - - 16-061 - This engineering report (ER) is a deliverable of the OGC Testbed 12. It advances previous work in the area of business rules for AIXM 5 based on SBVR. It evaluates the use of geo-spatial operators and constraints in SBVR, including a proof of concept for their automatic interpretation by software. It gives guidelines on how to deal with temporality aspects and how to extend the applicability of SBVR towards filtering expressions and it identifies limitations of the currently available vocabulary. - - 2017-06-30 - Testbed-12 Aviation SBVR Engineering Report - 16-061 - Timo Thomas, Aleksandar Balaban + EA-SIG Collaboration White Paper + *RETIRED* The focus of collaboration services discussed in this white paper is on applications that directly support user interaction and on the applications that monitor, manage and control these interactive services. - - + + + Sara Saeedi + 20-011 + SCIRA Pilot Engineering Report - Testbed-12 Aviation SBVR Engineering Report + + + This engineering report (ER) captures Smart City Interoperability Reference Architecture (SCIRA) Pilot implementation outcomes and findings to demonstrate the risk mitigation and safety capability of the SCIRA interoperable and standard-based architecture. SCIRA Pilot is an OGC (Open Geospatial Consortium) Innovation Program project sponsored by the US Department of Homeland Security (DHS) Science & Technology (S&T) in collaboration with the city of St. Louis, Missouri. The purpose of this project is to advance standards for smart and safe cities and develop open, interoperable design patterns for incorporating the Internet of Things (IoT) sensors into city services. + + OGC SCIRA Pilot Engineering Report + 20-011 + 2020-05-04 + - - - Testbed-13: Cloud ER - 17-035 - Charles Chen + + + OGC GeoPose Reviewers Guide + 22-000 + - - - OGC Testbed-13: Cloud ER - This OGC Engineering Report (ER) will describe the use of OGC Web Processing Service (WPS) for cloud architecture in the OGC Testbed 13 Earth Observation Cloud (EOC) Thread. This report is intended to address issues in lack of interoperability and portability of cloud computing architectures which cause difficulty in managing the efficient use of virtual infrastructure such as in cloud migration, storage transference, quantifying resource metrics, and unified billing and invoicing. This engineering report will describe the current state of affairs in cloud computing architectures and describe the participant architectures based on use case scenarios from sponsor organizations. + + + OGC GeoPose Reviewers Guide + 22-000 + The GeoPose Reviewers Guide is a public resource structured to provide quick answers to questions which a reviewer may have about the OGC GeoPose specification. This OGC document is provided to support professionals who need to understand OGC GeoPose and/or are reviewing the GeoPose draft standard but do not wish to implement it. -Cloud computing is paving the way for future scalable computing infrastructures and is being used for processing digital earth observation data. In this EOC thread effort, data is stored in various storage resources in the cloud and accessed by an OGC Web Processing Service. The methods in which these processes are deployed and managed must be made interoperable to mitigate or avoid the complexities of administrative effort for the scientific community. In other words, the intent of this effort is to develop a way for scientists to acquire, process, and consume earth observation data without needing to administer computing cloud resources. - - - 2018-01-08 - 17-035 +GeoPose 1.0 is an OGC Implementation Standard for exchanging the position and orientation (Poses) of real or virtual geometric objects within reference frames anchored to the Earth’s surface (Geo) or within other astronomical coordinate systems. The standard specifies two Basic forms with no configuration options for common use cases, an Advanced form with more flexibility for more complex applications, and five composite GeoPose structures that support time series plus chain and graph structures. + 2023-09-08 + + C. Perey, J.G. Morley, J. Lieberman, R. Smith, M. Salazar, C. Smyth - - 2007-12-28 - Topic 06 - Schema for coverage geometry and functions - 07-011 - - This International Standard defines a conceptual schema for the spatial characteristics of coverages. Coverages support mapping from a spatial, temporal or spatiotemporal domain to feature attribute values where feature attribute types are common to all geographic positions within the domain. A coverage domain consists of a collection of direct positions in a coordinate space that may be defined in terms of up to three spatial dimensions as well as a temporal dimension. - + + 15-027r1 + - - Topic 6 - Schema for coverage geometry and functions + + + 15-027r1 + Testbed 11 Digital Notice to Airmen (NOTAM) Validation and Enrichment Service Engineering Report - - OGC - 07-011 + This OGC Engineering Report (ER) is a deliverable of the OGC Testbed 11. This ER describes the Digital Notice to Airmen (NOTAM) enrichment and validation services in the Testbed 11 Aviation thread, including: +• A description of the architecture and architectural options. +• An overview of the implemented components and workflows followed by a short description of each component. +• Documentation of the issues, lessons learned as well as accomplishments and scenarios that were of general interest in the Aviation thread. +More detailed information on other specific aspects considered in OWS-11 Aviation may be found in the individual Aviation Engineering Reports. + + + 2016-01-18 + Aleksandar Balaban + OGC® Testbed 11 Digital Notice to Airmen (NOTAM) Validation and Enrichment Service Engineering Report - - - Barry Schlesinger - Special XML schemas have been created for individual data sets, based on ISO 19115 and a general schema for the RSE. However, a generalized metadata XML schema should be available where possible; it should not be necessary to create special schemas for each data set. ISO 19139 can serve as such a general XML implementation specification for 19115. This implementation needs to be tested in practice. In addition, the new ISO standards are incorporating much, if not all, of the metadata not in 19115 that the RSE contain. XML schemas for these metadata need to be developed that are based upon the abstract model in the ISO standards. All of these implementations need to be tested in practice. This Report describes such tests and the results. It also describes to what extent metadata on which the test metadata are based are supported by 19139, to what extent they are supported by metadata specified in the new ISO standards or the RSE, and to what extent new metadata elements are needed. - Imagery Metadata - + + 2017-05-15 + Testbed-12 TopoJSON, GML Engineering Report + 16-056 + This OGC document evaluates TopoJSON as an encoding that may be delivered across a common, standard OGC service interface such as WFS. + + 16-056 + - Imagery Metadata - 05-015 + + Testbed-12 TopoJSON, GML Engineering Report - 05-015 - 2005-01-27 - - + + Jeff Harrison - - - Web Terrain Server - 01-061 - - The purpose of theWeb Terrain Server (WTS) is to produce perspective views of georeferenced data - typically 3-dimensional coverages. - 01-061 + - - 2001-08-24 - Raj Singh - Web Terrain Server - - - - This OGC Engineering Report (ER) describes the application and use of OGC Web Services (OWS) for integrating Machine Learning (ML), Deep Learning (DL) and Artificial Intelligence (AI) in the OGC Testbed-14 Modeling, Portrayal, and Quality of Service (MoPoQ) Thread. This report is intended to present a holistic approach on how to support and integrate emerging AI and ML tools using OWS, as well as publishing their input and outputs. This approach should seek efficiency and effectiveness of knowledge sharing. + + Sam Meek + + OGC Vector Tiles Pilot: Summary Engineering Report + 18-086r1 + OGC Vector Tiles Pilot: Summary Engineering Report + 2019-02-15 + This OGC Engineering Report (ER) provides the summary findings resulting from completion of the OGC Vector Tiles Pilot (VTP or Pilot). The requirements for the Pilot were generated from a combination of sponsor input and analysis of typical use cases for tiling of vector feature data across the OGC Standards Baseline and related standards. The driving use case for this activity was the visualization of feature data on a client. The three main scenarios considered were consumption of tiled feature data by a web client, a desktop client and a mobile client. As a standards body, the OGC already has standards that fit these use cases. These are; Web Map Tile Service 1.0 (WMTS) for a web client, and GeoPackage 1.2 for a mobile client. Web Feature Service (WFS) 3.0 is suitable for a desktop client and has an in-built method to support tiling, but not specifically for tiled feature data such as that explored in the VTP. One of the purposes of the Pilot was to produce demonstration implementations to support tiled feature data using WFS 3.0, WMTS 1.0 and GeoPackage 1.2 that can be validated by Technology Integration Experiments (TIEs). The draft extension to these standards helped define a draft Conceptual Model for tiled feature data in support of visualization. The Conceptual Model formally captures the requirements for component implementations and rationalizes them into a model documented in the Unified Modeling Language (UML). -This engineering report will describe: experiences, lessons learned, best practices for workflows, service interaction patterns, application schemas, and use of controlled vocabularies. It is expected that the description of workflows for geospatial feature extraction will be more complex than the implementations found in the deliverables. - 18-038r2 - Machine Learning Engineering Report - 2019-02-04 +The ER provides an overview of each of the components, their implementation decisions and the challenges faced. The components are presented as draft extensions to existing standards. The WFS standard is currently in a major revision cycle and is transitioning away from services to a resource-oriented architecture. This transition has implications for access to tiled feature data. This offers options of access to pre-rendered tiles, or to tiles created using WFS 3.0 query functionality. The current WMTS standard only offers access to the pre-rendered tiles and much of the work is therefore about defining and supporting tiled feature data as a media type. The OGC GeoPackage standard is more complex as it attempts to ship all of the tiled feature data in a self-contained package aimed at environments that have Denied, Degraded, Intermittent or Limited (DDIL) bandwidth. DDIL is an important use case for GeoPackage as most normal web services do not function without connectivity. The military, first responders and other groups who work in challenging operational environments require a capability to ship, store and distribute geospatial data in an efficient, modern manner. The combination of GeoPackage and tiled feature data offers the means to supply detailed geospatial data in a portable fashion to satisfy many DDIL use cases. GeoPackage also offers the majority of the future work as it attempts to store information such as styling and attribution separately to the geometries to take advantage of a relational database structure. + +When this project was initiated, the term vector tiles was used throughout. However, as the project progressed, the participants agreed that the term tiled feature data was more appropriate than the colloquial term of vector tiles. This engineering report therefore interchangeably uses both tiled feature data and vector tiles to refer to the approach of tiling vector feature data. + + + + + 18-086r1 + + - + 18-097 + Environmental Linked Features Interoperability Experiment Engineering Report + OGC Environmental Linked Features Interoperability Experiment Engineering Report + + - Tom Landry + David Blodgett, Byron Cochrane, Rob Atkinson, Sylvain Grellet, Abdelfettah Feliachi, Alistair Ritchi - OGC Testbed-14: Machine Learning Engineering Report - - - 18-038r2 - - - 07-012 - As a work item in the OWS4/Conformance and Interoperability Test and Evaluation (CITE) project, Northrop Grumman Information Technology (NGIT) provided an open source web services compliance engine. NGIT refers to this engine as the Test Evaluation And Measurement (TEAM) Engine. It executes scripts written in Compliance Test Language (CTL), a grammar also developed by NGIT. This IPR describes TEAM Engine in detail and provides information on how it was used in OWS-4/CITE. - Compliance Test Engine Interoperability Program Report - Jennifer Marcus, Chuck Morris - - Compliance Test Engine Interoperability Program Report - 07-012 - + Systems that maintain and disseminate information representing and/or related to spatial features often lack mechanisms to describe or discover how features relate to each other, to other kinds of features, and to a wide variety of related information that may be relevant. The Environmental Linked Features Interoperability Experiment (ELFIE) explored Open Geospatial Consortium (OGC) and World Wide Web Consortium (W3C) standards with the goal of establishing a best practice for exposing cross-domain links between environmental domain and sampling features. The Interoperability Experiment (IE) focused on encoding relationships between cross-domain features and linking available observations data to sampled domain features. An approach that leverages the OGC service baseline, W3C data on the web best practices, and JavaScript Object Notation for Linked Data (JSON-LD) contexts was developed and evaluated. Outcomes of the experiment demonstrate that broadly accepted web technologies for linked data can be applied using OGC services and domain data models to fill important gaps in existing environmental data systems' capabilities. While solutions were found to be capable and promising, OGC services and domain model implementations have limited utility for use in linked data applications in their current state and the universe of persistent URIs that form the foundation of a linked data infrastructure is still small. In addition to improvement of the standards baseline and publication of linked data URIs, establishing conventions for URI dereferencing behavior and default content given multiple options for a resource remain for future work. + 2019-02-11 + 18-097 + + + 03-088r6 + OGC Web Services Common - - - 2007-09-04 + + OGC Web Services Common + 03-088r6 + Arliss Whiteside + + + This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses. + + 2004-01-19 + - + + + + This Engineering Report (ER) summarizes the main achievements of the Federated Marine Spatial Data Infrastructure (FMSDI) Pilot Phase 3. It focused on a variety of aspects contributing to an overarching scenario to aid in the better understanding of both the challenges and potential opportunities for coastal communities, ecosystems, and economic activities in the Arctic region. + +The sub-scenarios, i.e., those scenarios developed by each participant, address aspects of the changing Arctic landscape. These activities included the following. + +A sea-based, health and safety scenario incorporating the land/sea interface in the Arctic. This scenario demonstrates the technology and data used with OGC, IHO, and other community standards in response to a grounding event and the evacuation of an expedition cruise ship or research vessel in the Arctic. Demonstrating interoperability between land and marine data that is necessary to aid first responders and other stakeholders. This scenario incorporates, but is not be limited to: + +voyage planning information (e.g., Arctic Voyage Planning Guide, Safety of Navigation products and services, Maritime Safety Information); + +land-based emergency services/resources (e.g., Coast Guard stations, transit times to emergency services or ports, medical facilities and resources, helicopter access); + +coastal environmental/topographic/hydrographic/maintenance data (e.g., deposition and dredging of seafloor sediment, changes in coastline and bathymetry); and + +global maritime traffic data in the Arctic (e.g., to help assess likelihood of other ships in responding to a ship in distress). + +Demonstrating interoperability between land and marine data that is necessary to understand coastal erosion (e.g., ocean currents, geology, permafrost characteristics, etc.). + +General sensitivity to climate change. + Towards a Federated Marine SDI: Connecting Land and Sea to Protect the Arctic Environment Engineering Report + 23-010 + Robert Thomas, Sara Saeedi + 2023-06-14 + 23-010 - - - Fusion Standards Study Engineering Report - OGC® Fusion Standards Study Engineering Report - 09-138 - George Percivall - 09-138 - 2010-03-21 - This OGC Engineering Report (ER) provides discussions and recommendations for information fusion, with a focus on geospatial information. In this ER, fusion is discussed in three categories: sensor fusion, object/feature fusion, and decision fusion. Recommendations in this ER will be considered in the planning of future activities including the OWS-7 Testbed. + Towards a Federated Marine SDI: Connecting Land and Sea to Protect the Arctic Environment Engineering Report - - Gerhard Gr + + + 20-018 + Machine Learning Training Data ER + 20-018 + + + - 2007-08-14 - - - - - City Geography Markup Language - 07-062 - City Geography Markup Language - 07-062 - CityGML is designed as an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is implemented as an application schema of the Geography Markup Language 3 (GML3), the extendible international standard for spatial data exchange and encoding issued by the Open Geospatial Consortium (OGC) and the ISO TC211. + 2021-01-13 + The OGC Testbed-16 Machine Learning (ML) Training Data Engineering Report (ER) describes training data used for developing a Wildfire Response application. Within the context of the application, this ER discusses the challenges and makes a set of recommendations. The two scenarios for the wildfire use case include fuel load estimation and water body identification. The ML training data described in this ER are based on these two scenarios. Suggestions are also made for future work on a model for ML training dataset metadata, which is intended to provide vital information on the data and therefore facilitate the uptake of training data by the ML community. Additionally, this ER summarizes the discussions and issues about ML training data among the Testbed-16 ML thread participants and draws conclusions and recommendations for future work on the subject. Finally, this ER also links to current Analysis Ready Data (ARD) principles and efforts, in particular in the Earth Observation (EO) community. + OGC Testbed-16: Machine Learning Training Data ER + Guy Schumann - - 01-042 - Topic Domain 1 - Telecommunications Domain - - Domain Model for telecommunications Networks - Topic Domain 1 - Telecommunications Domain - - + - Tom Strickland + 2016-04-07 - 2001-10-09 - 01-042 + + Lucio Colaiacomo, Joan Masó, Emmanuel Devys + 08-085r5 + GML in JPEG 2000 (GMLJP2) Encoding StandardPart 1: Core + + 08-085r5 + OGC GML in JPEG 2000 (GMLJP2) Encoding StandardPart 1: Core + This standard applies to the encoding and decoding of JPEG 2000 images that contain GML for use with geographic imagery. +This document specifies the use of the Geography Markup Language (GML) within the XML boxes of the JPEG 2000 data format and provides an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations. The document also specifies the encoding and packaging rules for GML use in JPEG 2000. + + - - The OGC GML Application Schema - Coverages (“GMLCOV”) version 1.0 [OGC 09-146r2], recently renamed the OGC Coverage Implementation Schema version 1.0, provides a ReferenceableGridCoverage element for representing coverages on a referenceable grid. However, GMLCOV provides no instantiable subtypes of a critical sub-element of ReferenceableGridCoverage, GMLCOV::AbstractReferenceableGrid. To make use of ReferenceableGridCoverage, an extension deriving from GMLCOV would need to be developed. GML 3.3 is not such an extension of GMLCOV, as it is built independently from GMLCOV. Use of the instantiable referenceable grid elements of GML 3.3 with ReferenceableGridCoverage violates Requirement 14 of GMLCOV 1.0 and Requirement 24 of the OGC Modular Specification[1]. - -This OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension provides a set of referenceable grid elements for use as sub-elements of ReferenceableGridCoverage. Three of these elements have been adapted from GML 3.3, while a fourth emerged from work on a Testbed-11 Engineering Report[2]. - 16-083r3 - Eric Hirschorn - - Coverage Implementation Schema - ReferenceableGridCoverage Extension with Corrigendum - 16-083r3 + + + 06-083r8 + Web Coverage Service (WCS) Implementation Specification + 2007-02-06 + John Evans + OpenGIS Web Coverage Service (WCS) Implementation Specification - - - 2019-01-20 - OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension with Corrigendum - + + + 06-083r8 + The Web Coverage Service (WCS) supports electronic retrieval of geospatial data as coverages + - - 2009-02-05 - 08-103r2 - - Richard Martell - This document is an abstract test suite (ATS): a compendium of abstract test cases pertaining to implementations of the CSW-ebRIM 1.0 catalogue profile. It provides a basis for developing an executable test suite (ETS) to verify that the implementation under test (IUT) conforms to all relevant functional specifications. While passing all of the conformance tests defined in this ATS provides some assurance of overall functional correctness, it cannot guarantee that an implementation is faultless. - - - CSW-ebRIM Registry Service - Part 3: Abstract Test Suite - + + + 07-056r1 + The Specification Model -- Structuring an OGC specification to encourage implementation + This standard specifies some desirable characteristics of a standards specification that will encourage implementations by minimizing difficulty and optimizing usability and interoperability. + John Herring, OAB, Architecture WG - CSW-ebRIM Registry Service - Part 3: Abstract Test Suite - 08-103r2 + + + The Specification Model -- Structuring an OGC specification to encourage implementation + 07-056r1 + 2007-07-23 + - - + + David Graham, Carl Reed + CDB X Conceptual Model with Prototyping Examples and Recommendations + 20-092 + CDB X Conceptual Model with Prototyping Examples and Recommendations + 20-092 - 15-010r4 - Testbed-11 WFS-T Information Exchange Architecture - - - This document presents an assessment of the conformance level, with respect to the WFS standard (OGC 09-025r2), of the web feature servers used in the OGC Testbed-11. Each server is accessed to determine if it conforms to the minimum requirements of the WFS standard. Each server is further accessed to determine whether the server offers additional, upcoming and complimentary capabilities just as support for the WFS REST API and GeoJSON. -This document offers recommendations to aid implementers of the WFS standard (OGC 09-025r2). -This document presents options available to WFS implementers for achieving interoperability between WFS clients and server at the schemas level. -This document includes a survey of available WFS clients and an assessment of their capabilities. -This document reviews tools and standards, such as the GeoSynchronization Service (OGC 10-069r3), that are complimentary components that may be used with a WFS to address requirements such as verification and notification, data and access security, exception handling and system hardening. -Finally, this document includes a FAQ composed of questions raised during the OGC Testbed-11. - - OGC® Testbed-11 WFS-T Information Exchange Architecture - 15-010r4 - 2016-01-28 - Panagiotis (Peter) A. Vretanos - - - - 06-173r2 - Geographic information - Rights expression language for geographic information - Part xx: GeoREL - 06-173r2 - Geographic information - Rights expression language for geographic information - Part xx: GeoREL - John Herring - - - 2007-01-25 - - + This Discussion Paper documents the results and recommendations of the rapid prototyping activities conducted during the 3D Geospatial Series Tech Sprint II - OGC CDB 2.0 (aka CDB X). This activity was performed in support of Special Operations Forces (SOF) Future Concepts. This effort hopes to accelerate evolution of the OGC CDB standard to meet the needs of planning, rehearsal, and Mission Command systems providing decision support to Special Operations Forces and enabling SOF tactical and operational advantage. OGC industry standards enable interoperability of geospatial data across systems and applications that SOF Operators and analysts use across warfighting functions. + +Short summary of CDB X goal: Meeting the requirements for tactical GEOINT that can be used across warfighting functions. - This document extends the rights expression language (REL) to encompass the concerns of holders of geographic data and service resources to equally ensure their protection. This allows the geographic information market to operate with minimal constraints derived from need for the protection of intellectual property. + + + 2022-08-05 - - 08-068r3 - Web Coverage Processing Service (WCPS) Language Interface Standard - 08-068r3 - - The OGC Web Coverage Processing Service (WCPS) defines a protocol-independent language for on-demand extraction, processing, and analysis of multi-dimensional gridded coverages (datacubes) representing among others spatio-temporal sensor, image, simulation, or statistics data. - - 2021-06-15 - + + OGC Name Type Specification - specification elements + 2021-09-27 + - Peter Baumann - - Web Coverage Processing Service (WCPS) Language Interface Standard - - - - 99-051 - Catalog Interface - 99-051 - Catalog Interface + Gobe Hobona, Simon Cox + - - 1999-07-16 - - Doug Nebert - - - Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers. + 10-103r1 + + OGC Name Type Specification - specification elements + 10-103r1 + The mission of the OGC Naming Authority (OGC-NA) is to provide the means through which OGC resources such as OGC documents, namespaces and ontologies can be controlled and managed such that they can provide clear and well-defined names and definitions. In the terminology defined in ISO 19135, OGC-NA is the Control Body for the register of OGC Names. This document specifies a rule for constructing OGC names that may be used for identifying specification elements defined in the OGC Specification Model – Modular Specification. - - 05-005 - Jerome Sonnet - OpenGIS Web Map Context Implementation Specification - Web Map Context Implementation Specification - 05-005 - This document is a companion specification to the OGC Web Map Service Interface Implementation Specification version 1.1.1 [4], hereinafter WMS 1.1.1. -WMS 1.1.1 specifies how individual map servers describe and provide their map content. The present Context specification states how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent format for storage in a repository or for transmission between clients. This description is known as a Web Map Context Document, or simply a Context. Presently, context documents are primarily designed for WMS bindings. However, extensibility is envisioned for binding to other services. -A Context document includes information about the server(s) providing layer(s) in the overall map, the bounding box and map projection shared by all the maps, sufficient operational metadata for Client software to reproduce the map, and ancillary metadata used to annotate or describe the maps and their provenance for the benefit of human viewers. -A Context document is structured using eXtensible Markup Language (XML). Annex A of this specification contains the XML Schema against which Context XML can be validated. - - 2005-05-03 - + + + + + + + + + + + + + + + + + + + + + + + + + + The purpose of theWeb Terrain Server (WTS) is to produce perspective views of georeferenced data - typically 3-dimensional coverages. + 2001-08-24 + 01-061 + + Web Terrain Server + Raj Singh + 01-061 + Web Terrain Server - - + - + + - - - - 2007-08-07 - Uwe Voges, Kristian Senkler - - 07-045 - - OpenGIS Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile - ISO Metadata Application Profile - 07-045 - This document specifies an application profile for ISO 19115/ISO 19119 metadata with support for XML encoding per ISO/TS19139 and HTTP protocol binding. It relies on requirements coming from the CSW 2.0.2 specification (OGC document 07-006). + + + 07-067r2 + Arliss Whiteside, John Evans + OpenGIS Web Coverage Service (WCS) Implementation Specification Corrigendum 1 + + + 07-067r2 + Web Coverage Service (WCS) Implementation Specification Corrigendum 1 + + This version 1.1.1c1 of the Web Coverage Service (WCS) Specification supersedes previous +version 1.1.0 [OGC 06-083r8]. Technical changes from the version 1.0 include building on +the OGC Web Services Common Specification [OGC 06-121r3] and a substantially revised +Capabilities schema; new schemas and syntax for operation requests (GetCoverage, +DescribeCoverage); and integration with GML 3.1. The changes in WCS 1.1.1c1 from WCS +1.1.0 are summarized in [OGC 07-066r2]. + 2007-08-29 - - HY_Features: a Common Hydrologic Feature Model - 11-039r3 - - - - 11-039r3 - OGC HY_Features: a Common Hydrologic Feature Model - - - Irina Dornblut, Rob Atkinson - 2014-02-24 + + Ingo Simonis - Common semantics support the reference of features to the concept they represent and the integration of data proceed using the semantic framework such mappings provide. However there is no standard conceptual model for hydrologic feature identification. Different models of hydrologic processes, and different scales of detail, lead to a variety of information models to describe these features, and to different and mostly incompatible sets of feature identifiers. -This document describes requirements and a proposed design for a domain model of hydrologic features as a set of interrelated Application Schemas using the ISO 19109 General Feature Model, + 15-077r1 + Testbed-11 SOAP Interface Engineering Report: Comparison on the Usage of SOAP Across OGC Web service interfaces + A number of OGC service interface standards define SOAP bindings. Despite the current hype around REST or RESTful interfaces, SOAP services are still used intensively, in particular in security-critical environments. A number of OGC Web service interfaces support SOAP bindings (see chapter 6). Unfortunately, those bindings are not fully consistent across the suite of OGC service standards. Differences can be found in terms of SOAP versions, used namespaces, error handling, capabilities documentation, or transport of non-XML data; i.e. aspects that should be harmonized by a cross-standard working group. +This document seeks to provide an overview of the current situation and guidance on future SOAP harmonization across all OGC Web services. A number of change requests have been developed during the development process for this document. Though this document provides recommendations in chapter 8, it is highly recommended to either form a new SOAP working group, or preferably to assign the development of SOAP best practices to reduce the risk of missed requirements and architecture arguments to the newly reformed OWS Common SWG. The best practices could then be applied to all OGC service standards that offer SOAP bindings. - - - - Simon Jirka, Arne Bröring, Daniel Nüst + 2016-02-03 + + + 15-077r1 + - 09-112r1 - Sensor Observable Registry (SOR) Discussion Paper - - 2010-10-12 - - - Sensor Observable Registry (SOR) Discussion Paper - 09-112r1 - - This Discussion paper introduces the Sensor Observable Registry (SOR), a web service interface for managing the definitions of phenomena measured by sensors as well as exploring semantic relationships between these phenomena. + + OGC® Testbed-11 SOAP Interface Engineering Report: Comparison on the Usage of SOAP Across OGC Web service interfaces - + + Hugo Ledoux + + CityJSON Community Standard 1.0 + 20-072r2 + OGC CityJSON Community Standard 1.0 - - - Joshua Lieberman - Geospatial Semantic Web Interoperabiltiy Experiment Report - 06-002r1 - - - 2006-08-21 - Geospatial Semantic Web Interoperabiltiy Experiment Report - 06-002r1 - The Semantic Web seeks to make the meaning as accessible as the material, by enabling connections - which are both logical and (machine) actionable - between concepts which a user presently understands and those which may be new and foreign. The Geospatial Semantic Web extends this capability to both content and concepts that are specifically spatial, temporal, and geographic in nature, giving both people and machines true access to a wider range of knowledge. + 20-072r2 + + 2021-08-13 + CityJSON is a JSON-based encoding for a well-documented subset of the OGC CityGML data model (version 2.0.0). CityJSON defines how to store digital 3D models of cities and landscapes. The aim of CityJSON is to offer an alternative to the GML encoding of CityGML, which can be verbose and complex to read and manipulate. CityJSON aims at being easy-to-use, both for reading datasets and for creating them. It was designed with programmers in mind, so that tools and APIs supporting it can be quickly built. + + - + + This document specifies the HTTP profile of the CSW General Model part (see OGC 12- +168r6). The General Model specifies the abstract interfaces between clients and catalogue +services. This standard specifies the mappingof the Catalogue abstract model interface +into the HTTP protocol binding. +In this HTTP protocol binding, operation requests and responses are sent between clients +and servers using the HTTP GET and/or HTTP POST methods. Two equivalent request +encodings are defined in this standard. The first using keyword-value pairs (KVP) +which is suitable for use with the HTTP GET method. The second using XML which is +suitable for use with the HTTP POST method. +This standard defines operations that allow a client to get a service description document +for the catalogue (i.e. GetCapabilities); operations that allow a client to, at runtime, +interrogate the service about the kinds of data available (i.e. GetDomain); operations that +allow a client to retrieve records from the catalogue (i.e. GetRecordById and +GetRecords); operations that allow a client to add, modify and remove records from the +catalogue service (i.e. Transaction, Harvest, UnHarvest). + + Doug Nebert, Uwe Voges, Panagiotis Vretanos, Lorenzo Bigagli, Bruce Westcott - 16-041r1 - - Testbed-12 WPS ISO Data Quality Service Profile Engineering Report - Testbed-12 WPS ISO Data Quality Service Profile Engineering Report - 16-041r1 - Liping Di, Eugene G. Yu, Md Shahinoor Rahman, Ranjay Shrestha - This Data Quality Engineering Report describes data quality handling requirements, challenges and solutions. One focus is on data quality in general that needs to be communicated from one service to another. In addition, it discusses WPS data quality solutions. The ultimate goal is for it to be nominated as a WPS ISO Data Quality Service Profile. ISO 19139 is used as the base to encode the data quality. WPS and workflows are used to streamline and standardize the process of data quality assurance and quality control. The main topics include: (1) generalized summary and description of the design and best practices for analyzing data quality of all feature data sources used in the Citizen Observatory WEB (COBWEB) project, (2) solutions and recommendations for enabling provenance of data quality transparent to end users when the data is processed through a WPS, (3) best practices and recommendations for designing and prototyping the WPS profile to support data quality service conformant to the NSG Metadata Framework, and (4) general solution for data quality fit for both raster-based imageries and vector-based features. - - - 2017-06-30 - + + + 2016-06-10 + + 12-176r7 + 12-176r7 + Catalogue Services 3.0 Specification - HTTP Protocol Binding + OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding - + + 22-041 + Testbed-18: Building Energy Data Interoperability Engineering Report + 2023-08-16 + This OGC Testbed-18 Engineering Report (ER) represents deliverable D012 and D013 for the Building Energy Data Interoperability task. + Leigh St. Hilaire, Aidan Brookson + 22-041 - Gobe Hobona, Joana Simoes - 23-059 - - 2023 Open Standards Code Sprint Summary Engineering Report - - 2023 Open Standards Code Sprint Summary Engineering Report - 23-059 - Advances in computing, storage, sensing, and other technology areas continue to find a place in the geospatial ecosystem that makes location information findable, accessible, interoperable, and reusable. To enable geospatial standards to meet the likely interoperability needs of future technologies, it is necessary for Standards Development Organizations (SDOs) such as OGC to continue to innovate. Such innovation relies on the ability to develop new standards and improve existing ones to better address emerging interoperability challenges. Code sprints are one of a number of initiative types that OGC conducts to accelerate such innovation. A code sprint is a collaborative and inclusive event driven by innovative and rapid programming with minimal process and organization constraints to support the development of new applications and candidate standards. - -The focus of this Engineering Report (ER) is a code sprint that was held from October 30th to November 1st, 2023. The code sprint was organized by the Open Geospatial Consortium (OGC) and hosted by Geovation in London, England. The code sprint was sponsored by Ordnance Survey (OS) at the Gold-level, as well as the European Union Satellite Centre (SatCen), US National Geospatial Intelligence Agency (NGA), and the UK Defence Science and Technology Laboratory (Dstl) at the Silver-level. As with previous OGC Code Sprints, a key goal of the October 2023 Open Standards Code Sprint was the acceleration of the development of OGC Standards and their implementation in software products. - -Standards in focus for this code sprint included several OGC API, data model, and encoding standards. In addition to OGC Standards, the code sprint also included a thread focusing on the “GEOINT Imagery Media for ISR” (GIMI) profile of the ISO Base Media File Format (ISOBMFF) and the High Efficiency Image Format (HEIF). The engineering report concludes that the code sprint met all of its objectives and achieved its goal of accelerating the development of OGC Standards and their implementation in software products. - -In relation to emerging extensions to OGC API Standards, the engineering report concludes that the Publish/Subscribe (PubSub), Security, and Schemas capabilities examined in this code sprint could potentially support other OGC API Standards. Regarding GIMI, the engineering report concludes that with minor changes to popular open-source base libraries a wide range of software can quickly make use of GIMI capabilities. - -Regarding the Model for Underground Data Definition and Integration (MUDDI), the engineering report concludes that the MUDDI Conceptual Model is implementable and could easily be used as the basis for a logical model that can be encoded in a variety of formats including GML, GeoJSON, and Geopackage. As for JSON-FG, the engineering report concludes that due to the evident increase in adoption across the developer community, there is an increasing need to offer validators so that developers can check for compliance more easily. - -The sprint participants made the following recommendations for future work items on OGC API Standards. - -Extension of OGC API — Records to support faceting and federated search. -Use case experimentation to examine how the Publish/Subscribe approach can support various OGC API standards workflows. -Prototyping and specification on an OpenAPI definition document for the OGC SensorThings API Standard. -Additional support for multiband raster data in OGC API — Maps/Tiles/Coverages (e.g., multispectral imagery, etc). -The sprint participants made the following recommendations for future work items on OGC Encoding Standards. - -Tiled complex, signed, and floating-point data in multiband raster data. -Performance benchmarking between various imagery formats, for a variety of use cases. -Extraction of the conceptual model of GMLJP2 to make it applicable to any ISOBMFF profile. -Development of an Implementation Standard for the logical model and encoding of data that conforms to the MUDDI. -Use of the MUDDI logical schema as a template for MUDDI compliance. -The sprint participants made the following recommendations for future work items on GIMI. - -Extension of open-source base libraries used by several other products for creation and modification of GIMI files. -Prototype streaming of large images from client applications to servers for storage through OGC API — Processes. -Prototyping of a JavaScript Object Notation (JSON) encoded alternative to Key-Length-Value (KLV) metadata for use in GIMI files. - 2024-04-18 + Testbed-18: Building Energy Data Interoperability Engineering Report + + - - CDB Multi-Spectral Imagery Extension - 17-080r2 + + 2015-11-18 + + + OGC® Testbed-11 Implementing Linked Data and Semantically Enabling OGC Services Engineering Report - 2018-09-20 - - CDB Multi-Spectral Imagery Extension - Ryan Franz + + + Testbed-11 Implementing Linked Data and Semantically Enabling OGC Services Engineering Report + 15-054 + Stephane Fellah + 15-054 + This OGC® Engineering Report (ER) summarizes the approaches, findings and the results +of the Linked Data and Semantic Enablement of OGC Web Services sub-thread activities +of the OGC Testbed-11 Cross Community Interoperability (CCI) Thread. This report +provides an overview of existing standards for geosemantics, outlines the approaches +adopted during the testbed, describes the conceptual semantic models and services +developed during this testbed to leverage Linked Data and semantic enabled OGC web +services. + + + - - 17-080r2 - The “Multi-Spectral Imagery” extension defines how to encode and store reflected electromagnetic radiation from the infrared wavelengths into a CDB. The portion of the spectrum targeted is between the visible spectrum (current imagery and texture in CDB), and longer wavelength infrared that is primarily emissive and can be simulated based on the material temperature. + + + OpenGIS® Georeferenced Table Joining Service Implementation Standard + + Georeferenced Table Joining Service Implementation Standard + 10-070r2 + This document is the specification for a Table Joining Service (TJS). This OGC standard defines a simple way to describe and exchange tabular data that contains information about geographic objects. + 10-070r2 + Peter Schut + 2010-11-22 - - - - - Topic 08 - Relationships Between Features - 99-108r2 - This Topic introduces an abstraction for the relationships between entities in the real world. This abstraction is modeled as relationships between the features introduced in Topic 5. - Topic 8 - Relationships Between Features - Cliff Kottman - 1999-03-26 - 99-108r2 + + OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard + 17-003r2 + EO Dataset Metadata GeoJSON(-LD) Encoding Standard + + JavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. This OGC standard describes a GeoJSON [NR2] and JSON-LD [NR3] encoding for Earth Observation (EO) metadata for datasets (granules). This standard can be applied to encode metadata based on the Earth Observation Metadata Profile of Observations and Measurements (O&M) OGC 10-157r4 [OR1] or as an encoding of the Unified Metadata Model for Granules (UMM-G) conceptual model [OR2]. + +The GeoJSON encoding defined in this document is defined as a compaction[1] through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF XML [OR11] and RDF Turtle [OR12]. + +This document makes no assumptions as to the “service” interfaces through which the metadata are accessed and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful Architecture. The documented approach can be applied in combination with the following technologies: + +OGC OpenSearch extensions [OR19], [OR20], [OR25], +W3C Linked Data Platform [OR21], [OR22], +OASIS searchRetrieve [OR23], +OASIS OData [OR24]. +GeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features. + +JSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR18] which allows validation of instances against these schemas. - + 2020-02-14 - - - - - 21-037 - OGC Technical Paper on the Standards Landscape for Building Data - OGC Technical Paper on the Standards Landscape for Building Data - 21-037 - Data about buildings and building structures play roles at scales from neighborhoods to nations in creating, protecting, regulating, and understanding the built environment. This report examines standards which may be useful in defining the structure and content of building data at a national scale, a national building layer. Standard models, schemas, and encodings may be especially useful for supporting an extensible building dataset with an efficient core definition, but the ability to encompass more detailed or specialized data as needed in as seamless and compatible a manner as possible. Standards compiled and described in this document range from generic geographic data encodings to models and specifications for specific building perspectives such as land parcel improvements, facility ownership, footprint / roofline extractions, residency affordances, envelope characteristics, and so on. They provide potential source material for a modular and multi-platform building layer definition which can be applied to a reasonably wide set of use cases. This definition may in turn be a standardization candidate for adoption by other national geographic data collections. - + Y. Coene, U. Voges, O. Barois + - - - Josh Lieberman - 2021-07-02 + 17-003r2 + - - This standard specifies some desirable characteristics of a standards specification that will encourage implementations by minimizing difficulty and optimizing usability and interoperability. - - The Specification Model -- Structuring an OGC specification to encourage implementation - 07-056r1 - - - 2007-07-23 + + Chuck Morris + + 06-126r2 + Compliance Test Language (CTL) Best Practice - John Herring, OAB, Architecture WG - + 2009-07-21 - 07-056r1 - The Specification Model -- Structuring an OGC specification to encourage implementation - - - OGC Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW - 2004-10-12 - The OGC Catalogue Services 2.0 specification (OGC 04-021) establishes a framework for implementing catalogue services that can meet the needs of stakeholders in a wide variety of application domains. This application profile is based on the CSW schemas for web-based catalogues and it complies with the requirements of clause 11 in OGC 04-021. - - 04-017r1 - Richard Martell - - 04-017r1 - Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW + - - - + 06-126r2 + Compliance Test Language (CTL) Best Practice + This document establishes Compliance Test Language, an XML grammar for documenting and scripting suites of tests for verifying that an implementation of a specification complies with the specification. + - - 21-058 - + + OWS-5 KML Engineering Report + 07-124r2 - - - - Interoperable Simulation and Gaming Sprint Year 2 Engineering Report - The OGC Interoperable Simulation and Gaming Year 2 Sprint advanced the use of relevant OGC and Khronos Group [1] standards in the modeling, simulation, and training communities through capability development, compatibility testing, and gap analysis. Of particular interest was the use of glTF models, game engines, and 3rd-party mobile device libraries for the display and interaction with data using OGC APIs. - 21-058 - Interoperable Simulation and Gaming Sprint Year 2 Engineering Report - 2021-11-08 - Leonard Daly, Rollin Phillips - - - - - Eric Bertel - 03-064r5 - GO-1 Application Objects - The GO-1 Application Objects specification defines a set of core packages that support a small set of Geometries, a basic set of renderable Graphics that correspond to those Geometries, 2D device abstractions (displays, mouse, keyboard, etc.), and supporting classes. Implementation of these APIs will support the needs of many users of geospatial and graphic information. These APIs support the rendering of geospatial datasets, provide fine-grained symbolization of geometries, and support dynamic, event and user driven animation of geo-registered graphics. - GO-1 Application Objects - 2004-06-25 - - - + 2008-09-12 - 03-064r5 + + 07-124r2 + + OWS-5 KML Engineering Report + + This Discussion Paper is about the use of KML, an encoding used to express geographic annotation and visualization on existing or future web-based online maps (2d) and earth browsers (3d). KML uses a tag-based structure with nested elements and attributes and is based on the XML standard. + Chris Holmes - - - Definition identifier URNs in OGC namespace - 06-023r1 - *** Corrigendum - updated 2006-08-08 *** - -This revised version of this document adds additional allowed authority and objectType values, plus specifies URNs for data types, as proposed in change requests OGC 05-091r2 and 05-060. In addition, corrections have been made to the XML documents listed in Annex A. The changes made in this version are tracked in the Microsoft Word (.doc) format of this document.<br/><br/>This Best Practices Paper specifies Universal Resource Names (URNs) in the ogc URN namespace to be used for identifying definitions. This document specifies the formats used by these URNs, plus a set of specific URNs for specific definitions. These definitions should be used wherever applicable by implementations of various OGC Implementation Specifications, including GML, WMS, WFS, and WCS. - - - 2006-08-08 - Arliss Whiteside - - - Definition identifier URNs in OGC namespace + + SWE Service Model Implementation Standard + 09-001 + This standard currently defines eight packages with data types for common use across OGC Sensor Web Enablement (SWE) services. Five of these packages define operation request and response types. The packages are: 1.) Contents – Defines data types that can be used in specific services that provide (access to) sensors; 2.) Notification – Defines the data types that support provision of metadata about the notification capabilities of a service as well as the definition and encoding of SWES events; 3.) Common - Defines data types common to other packages; 4.) Common Codes –Defines commonly used lists of codes with special semantics; 5.) DescribeSensor – Defines the request and response types of an operation used to retrieve metadata about a given sensor; 6.) UpdateSensorDescription –Defines the request and response types of an operation used to modify the description of a given sensor; 7.) InsertSensor – Defines the request and response types of an operation used to insert a new sensor instance at a service; 8.) DeleteSensor – Defines the request and response types of an operation used to remove a sensor from a service. These packages use data types specified in other standards. Those data types are normatively referenced herein, instead of being repeated in this standard. + Johannes Echterhoff - 06-023r1 + + + + + 09-001 + OpenGIS® SWE Service Model Implementation Standard + + 2011-03-21 - - 2014-07-16 - Testbed 10 Flight Information Exchange Model GML Schema - 14-037 - OGC® Testbed 10 Flight Information Exchange Model GML Schema - Thomas Forbes, Ballal Joglekar - 14-037 + + Web Coverage Service (WCS) 1.1 extension for CF-netCDF 3.0 encoding + - + 2009-04-08 + 09-018 + Web Coverage Service (WCS) 1.1 extension for CF-netCDF 3.0 encoding + Ben Domenico, Stefano Nativi + - This report provides guidance for implementing the Flight Information Exchange Model (FIXM) using the same best practice as the Aeronautical Information Exchange Model (AIXM) and the Weather Information Exchange Model (WXXM) by adopting ISO and OGC standards. -The report is aimed at system and client developers that shall use the FIXM data encoding for the exchange of flight information. -This document is a deliverable for the OGC Testbed 10 (Testbed-10) testbed activity. OWS testbeds are part of OGC's Interoperability Program, a global, hands-on and collaborative prototyping program designed to rapidly develop, test and deliver proven candidate standards or revisions to existing standards into OGC's Standards Program, where they are formalized for public release. In OGC's Interoperability Initiatives, international teams of technology providers work together to solve specific geoprocessing interoperability problems posed by the Initiative's sponsoring organizations. OGC Interoperability Initiatives include testbeds, pilot projects, interoperability experiments and interoperability support services - all designed to encourage rapid development, testing, validation and adoption of OGC standards. -The Testbed-10 sponsors are organizations seeking open standard for their interoperability requirements. After analyzing their requirements, the OGC Interoperability Team recommends to the sponsors that the content of the Testbed-10 initiative be organized around the following threads: -• Cross-Community Interoperability (CCI) -• Open Mobility -• Aviation -More information about the Testbed-10 tested can be found at: -http://www.opengeospatial.org/standards/requests/103 + This extension of the WCS standard specifies an Information Community data model with the related encoding that may optionally be implemented by WCS servers. This extension specification allows clients to evaluate, request and use data encoded in CF-netCDF3 format from a WCS server. +This document is an extension of the Web Coverage Service (WCS) 1.1 Corrigendum 2 (version 1.1.2) Implementation Standard [OGC 07-067r5]. With small changes, this extension is expected to also apply to WCS 1.2. - - - + 09-018 + + - - 20-073 - OGC Earth Observation Applications Pilot: Summary Engineering Report - - This Engineering Report (ER) summarizes the main achievements of the OGC Innovation Program initiative Earth Observation Applications Pilot, conducted between December 2019 and July 2020. - 2020-10-26 - Ingo Simonis - OGC Earth Observation Applications Pilot: Summary Engineering Report + - - 20-073 + Andrea Aime, Emanuele Tajariol, Simone Giannecchini + 18-034r3 + Compliance Engineering Report + 2019-02-07 + OGC Testbed-14: Compliance Engineering Report + 18-034r3 + The OGC Compliance Program provides a free online testing facility based on TeamEngine and a set of test suites dedicated to specific protocols and versions, as well as specification profiles and extension. + +This document reviews the work that has been carried out as part of the Testbed-14 compliance activity, in particular covering the development of: + +A Web Feature Service (WFS) 3 core test suite, covering both the tests and the reference implementation servers + +A Defence Geospatial Information Working Group CATalog (DGIWG CAT) 2.0 extension for the Catalog Services for the Web 2.0.2 (CSW) test suite and server reference implementation + +The WFS 3.0 protocol is the next iteration of the WFS specification, focusing on open specification, ease of implementation, and modern Representational State Transfer (REST) Application Program Interface (API) approaches. + +The DGIWG CAT is an application profile of the CSW, which allows to query and get metadata following the DGIWG application profile of the ISO19139 standard, which augments the metadata elements to include information relevant to the defense organizations. + +Both the test suites are meant to be run by the Test, Evaluation, And Measurement (TEAM) Engine and eventually land on the OGC beta compliance test engine (availability on the primary site is subject to the WFS 3.0 specification being finalized and the tests being adapted to it). + + - - The subject of this Engineering Report (ER) is a code sprint that was held from the 14th to the 16th of September 2022 to advance open standards that relate to geospatial metadata and catalogues. The code sprint was hosted by the Open Geospatial Consortium (OGC) and the International Organization for Standardization (ISO). The code sprint was sponsored by Ordnance Survey (OS) and Geonovum, and held as a hybrid event with the face-to-face element hosted at the Geovation Hub in London, United Kingdom. - 22-043r1 - 22-043r1 - Joint OGC and ISO Code Sprint 2022 Summary Engineering Report - - Gobe Hobona, Joana Simoes + + 2006-07-12 + 06-055r1 + + 06-055r1 + GML 3.2 image geopositioning metadata application schema + OpenGIS GML 3.2 image geopositioning metadata application schema + This document specifies a GML 3.2 Application Schema for image geopositioning metadata, which is also an Application Schema of ISO 19139. This geopositioning metadata schema is used by the separately specified Image Geopositioning Service (IGS) interface that adjusts the georeferencing coordinate transformations of images. + Arliss Whiteside + + + + + + + This standard describes a conceptual and logical model for the exchange of groundwater data, as well as a GML/XML encoding with examples. + 2017-03-06 - - - 2022-12-16 - Joint OGC and ISO Code Sprint 2022 Summary Engineering Report + WaterML 2: Part 4 – GroundWaterML 2 (GWML2) + 16-032r2 + 16-032r2 + + + Boyan Brodaric + OGC WaterML 2: Part 4 – GroundWaterML 2 (GWML2) + + - - OWS-5 GeoProcessing Workflow Architecture Engineering Report - 07-138r1 + + This Web Map Tile Service (WMTS) Implementation Standard provides a standard based solution to serve digital maps using predefined image tiles. The service advertises the tiles it has available through a standardized declaration in the ServiceMetadata document common to all OGC web services. This declaration defines the tiles available in each layer (i.e. each type of content), in each graphical representation style, in each format, in each coordinate reference system, at each scale, and over each geographic fragment of the total covered area. The ServiceMetadata document also declares the communication protocols and encodings through which clients can interact with the server. Clients can interpret the ServiceMetadata document to request specific tiles. + - 07-138r1 - This OGC® document describes the Workflow Architecture developed in support of Geoprocessing Workflow and Sensor Web Enablement threads of OWS-5. This information includes the overall architecture description, concepts, and issues. It also provides detail on the Conflation Workflow created as an example implementation for geoprocessing in a workflow. This document establishes a sample architecture and associated lessons learned as general guidance. + + 07-057r7 + Web Map Tile Service Implementation Standard + + OpenGIS Web Map Tile Service Implementation Standard + 07-057r7 + Joan Masó, Keith Pomakis, Núria Julià + 2010-04-06 - Michael Werling - 2008-09-12 + + + + + This document details considerations for using the WPS specification to define a standard coordinate transformation service. - OWS-5 GeoProcessing Workflow Architecture Engineering Report + + 2008-08-20 + + Max Martinez + + 08-054r1 + OWS-5 Considerations for the WCTS Extension of WPS + OWS-5 Considerations for the WCTS Extension of WPS + 08-054r1 - - - + + + OGC GeoTIFF Standard + 2019-09-14 + 19-008r4 - 18-036r1 - OGC Testbed-14: WPS-T Engineering Report - - - WPS-T Engineering Report - 18-036r1 - 2019-02-07 - Benjamin Pross, Arnaud Cauchy - This Engineering Report describes a proposed transactional extension for the OGC Web Processing Service (WPS) 2.0 standard including Key-Value Pair (KVP) and Extensible Markup Language (XML) bindings and recommendations for a process deployment profile for BPMN (Business Process Model and Notation). - - + GeoTIFF Standard + 19-008r4 + + + + Emmanuel Devys, Ted Habermann, Chuck Heazel, Roger Lott, Even Rouault + This OGC Standard defines the Geographic Tagged Image File Format (GeoTIFF) by specifying requirements and encoding rules for using the Tagged Image File Format (TIFF) for the exchange of georeferenced or geocoded imagery. The OGC GeoTIFF 1.1 standard formalizes the existing community GeoTIFF specification version 1.0 and aligns it with the continuing addition of data to the EPSG Geodetic Parameter Dataset. - - + + 00-029 + Geography Markup Language + + Ron Lake - Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure - 15-120r4 - 2017-02-23 - - The CDB standard defines a standardized model and structure for a single, “versionable”, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. -The application of CDB to future simulation architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the High Level Architecture - -Federation Object Model (HLA/FOM) and DIS protocols, the application of the CDB standard provides a Common Environment to which inter-connected simulators share a common view of the simulated environment. -The CDB standard defines an open format for the storage, access and modification of a synthetic environment database. A synthetic environment is a computer simulation that represents activities at a high level of realism, from simulation of theaters of war to factories and manufacturing processes. These environments may be created within a single computer or a vast distributed network connected by local and wide area networks and augmented by super-realistic special effects and accurate behavioral models. SE allows visualization of and immersion into the environment being simulated . -This standard defines the organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The standard makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. A series of associated OGC Best Practice documents define rules and guidelines for data representation of real world features. - - - - Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure - 15-120r4 - Carl Reed + + 2000-05-12 + The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features. + 00-029 + + Geography Markup Language + - - Marwa Mabrouk - Location Service (OpenLS) Implementation Specification: Core Services - 07-074 - OpenGIS Location Service (OpenLS) Implementation Specification: Core Services - 07-074 - - - This OpenGIS Interface Standard defines OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform. + + + 04-084r4 + Topic 00 - Overview + George Percivall - 2008-09-08 - - + 04-084r4 + + + This document (Topic 0) is an overview of the OGC Abstract Specification. + Topic 0 - Overview + + 2020-08-27 - - + - - OGC Moving Features Encoding Extension - JSON - 2020-05-21 - Moving Features Encoding Extension - JSON - 19-045r3 - This standard defines how to encode and share the various movements of geographic features by using JavaScript Object Notation (JSON). It provides an alternative encoding for OGC Moving Features instead of that provided in the XML Core [OGC 14-083r2] and Simple CSV [OGC 14-084r2] standards. A moving feature, for instance a vehicle or a pedestrian, contains a temporal geometry whose location continuously changes over time and dynamic non-spatial attributes whose values vary with time. This Moving Features JSON encoding defines a set of keywords to implement the conceptual schema of moving features defined in ISO 19141:2008 [ISO 19141:2008], accompanied with IETF GeoJSON Format [IETF RFC 7946]. - 19-045r3 - - Kyoung-Sook KIM, Nobuhiro ISHIMARU + + The OpenGIS® Sensor Observation Service Interface Standard (SOS) provides an API for managing deployed sensors and retrieving sensor data and specifically “observation” data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. + + + 06-009r6 + 2008-02-13 + OpenGIS Sensor Observation Service + Arthur Na, Mark Priest + Sensor Observation Service + 06-009r6 - - Testbed-19: Machine Learning Models Engineering Report - - The OGC Testbed 19 initiative explored six tasks including this task focused on Machine Learning: Transfer Learning for Geospatial Applications. - -This OGC Testbed 19 Engineering Report (ER) documents work to develop the foundation for future standardization of Machine Learning models for transfer learning within geospatial, especially Earth Observation, applications. The ER reviews the findings of transfer learning experiments and makes recommendations about the next steps in terms of both the experiments conducted and broader implications for OGC. - 23-033 - Testbed-19: Machine Learning Models Engineering Report - - 23-033 - - + - Samantha Lavender, Trent Tinker - - 2024-04-26 - - - OGC Web Services Common - 03-088r1 - OGC Web Services Common - 03-088r1 - This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses. - - + + Vector Tiles Pilot 2: Summary Engineering Report + 19-088r2 + - 2003-10-16 - - Arliss Whiteside + + 19-088r2 - + 2020-07-07 + This OGC Engineering Report (ER) provides a summary of the research and findings from Phase 2 of the OGC Vector Tiles Pilot (VTP2). The goal of VTP2 was to deliver a consistent, interoperable online/offline architecture for vector tiles based on feature and tile servers, as well as GeoPackage. All Application Programming Interface (API) implementations and service types deployed in the pilot were implemented to support the prototype vector tile metadata model and filtering language. These were two essential work items of VTP2. The feature and tile servers included implementations of the OGC API – Features standard and the draft OGC API – Tiles specification. The feature and tile servers provided support for a variety of Coordinate Reference Systems (CRS). This ER provides an overview of each of the components, their implementation decisions and the challenges faced. + +The VTP2 participants intend to use the results of the work in VTP2 to inform the development of OGC APIs, GeoPackage, and web service standards to enable consistent use both online and offline, particularly in DDIL environments. Such consistent use of tiled feature data online and offline will improve interoperability and usability of geospatial applications. Therefore, the value of the VTP2 work to organizations is expected to be in the efficiencies and productivity that comes from greater interoperability and usability. + Gobe Hobona, Terry Idol + OGC Vector Tiles Pilot 2: Summary Engineering Report - - OGC Testbed-13: Security Engineering Report - The Security Engineering Report (ER) covers two Testbed 13 topics: + + + 2014-07-10 + OGC® Web Feature Service 2.0 Interface Standard - With Corrigendum + Panagiotis (Peter) A. Vretanos + + + The Web Feature Service (WFS) represents a change in the way geographic information is created, modified and exchanged on the Internet. Rather than sharing geographic information at the file level using File Transfer Protocol (FTP), for example, the WFS offers direct fine-grained access to geographic information at the feature and feature property level. -The implementation of authentication and authorization plugins for the QGIS open source desktop GIS client and +This International Standard specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored, parameterized query expressions. -the implementation of secured workflow. +Discovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers. -The authentication plugins implement the SAML2 ECP with PAOS binding and IdP discovery from the SAML2 federation metadata URL. The access right delegation plugin implements applicable OAuth2 grant types. +Query operations allow features or values of feature properties to be retrieved from the underlying data store based upon constraints, defined by the client, on feature properties. -Regarding the first topic, this ER discusses the fit for purpose aspects for the OAuth2 and SAML2 in the context of an open source desktop application. It also covers the QGIS development as well as building and deployment aspects. Most of the work related to this topic was provided by Secure Dimensions. +Locking operations allow exclusive access to features for the purpose of modifying or deleting features. -Regarding the second topic, this ER outlines the architecture approach and the implications to implementations for security in OGC service workflows as well as the implementation approach itself. Most of the work related to this topic was provided by 52°North. - - - - - Testbed-13: Security Engineering Report - 17-021 - 2018-01-11 - - 17-021 - Andreas Matheus - - - - “The cloud is dead – long live the cloud!” so begins an IEC White paper on Edge Intelligence.[1] The IEC White Paper continues that “Driven by the internet of things (IoT), a new computing model – edge-cloud computing – is currently evolving, which involves extending data processing to the edge of a network in addition to computing in a cloud or a central data centre. Edge-Fog-Cloud computing models operate both on premise and in public and private clouds, including via devices, base stations, edge servers, micro data centres and networks.” - The Role of Geospatial in Edge-Fog-Cloud Computing - An OGC White Paper - 18-004r1 +Transaction operations allow features to be created, changed, replaced and deleted from the underlying data store. + +Stored query operations allow clients to create, drop, list and described parameterized query expressions that are stored by the server and can be repeatedly invoked using different parameter values. + +This International Standard defines eleven operations: + +GetCapabilities (discovery operation) +DescribeFeatureType (discovery operation) +GetPropertyValue (query operation) +GetFeature (query operation) +GetFeatureWithLock (query & locking operation) +LockFeature (locking operation) +Transaction (transaction operation) +CreateStoredQuery (stored query operation) +DropStoredQuery (stored query operation) +ListStoredQueries (stored query operation) +DescribeStoredQueries (stored query operation) +In the taxonomy of services defined in ISO 19119, the WFS is primarily a feature access service but also includes elements of a feature type service, a coordinate conversion/transformation service and geographic format conversion service. - - 18-004r1 - - The Role of Geospatial in Edge-Fog-Cloud Computing - An OGC White Paper - - - 2018-07-31 - George Percivall - - - This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids key words. - 16-003r4 - Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values - 16-003r4 - Carl Reed + Web Feature Service 2.0 Interface Standard - With Corrigendum + 09-025r2 + 09-025r2 - 2021-02-26 - Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values - - - - - - - Catalogue Service Implementation Specification [Catalogue Service for the Web] - 04-021r3 - Catalogue Service Implementation Specification - OpenGIS Catalogue Service Implementation Specification - OpenGIS Catalogue Service Implementation Specification [Catalogue Service for the Web] - 04-021r3 - - + + + Information Technology Standards for Sustainable Development + OGC Information Technology Standards for Sustainable Development + 14-095 + + 2015-01-22 + 2015-01-23 + 14-095 + + + OGC Information Technology Standards for Sustainable Development + Lance McKee + Sustainable development, meeting the needs of the present without compromising the ability of future generations to meet their own needs, will be accomplished by balancing social, economic and environmental objectives. In this paper the authors explain that rigorous standards for communicating environmental data are absolutely essential to enable social and economic progress in the Age of the Environment – the Anthropocene Epoch – in which humanity's expanding footprint has become the main cause of change in the planet's geology, water bodies, atmosphere and biosphere. The authors argue for a concerted and ongoing global effort to 1) define data communication and system interoperability requirements for environmental science, business and policy, and then 2) develop and implement consensus-derived, free and open environmental Information Technology (IT) standards that meet those requirements and that co-evolve with the larger IT standards framework and advances in IT. + Sustainable development, meeting the needs of the present without compromising the +ability of future generations to meet their own needs,1 + will be accomplished by +balancing social, economic and environmental objectives. In this paper the authors +explain that rigorous standards for communicating environmental data are absolutely +essential to enable social and economic progress in the Age of the Environment2 – the +Anthropocene Epoch3 – in which humanity's expanding footprint has become the main +cause of change in the planet's geology, water bodies, atmosphere and biosphere. The +authors argue for a concerted and ongoing global effort to 1) define data communication +and system interoperability requirements for environmental science, business and policy, +and then 2) develop and implement consensus-derived, free and open environmental +Information Technology (IT) standards that meet those requirements and that co-evolve +with the larger IT standards framework and advances in IT. + - - Doug Nebert - - The OpenGIS Catalogue Services Specification defines common interfaces to discover, browse, and query metadata about data, services, and other potential resources. - 2004-08-02 - - - 19-091r2 - + + This document summarizes the most significant aspects of the Open Geospatial Consortium (OGC) web services architecture, which the OGC is currently developing. This architecture is a service-oriented architecture, with all components providing one or more services to other services or to clients. + Web services architecture description + 05-042r2 + Arliss Whiteside - 19-091r2 - Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra - - 2021-02-11 - Thomas Gilbert, Carsten Rönsdorf, Jim Plume, Scott Simmons, Nick Nisbet, Hans-Christoph Gruler, Thom - + OpenGIS Web services architecture description - Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra - Demand for digital representations of built environments is accelerating and can only be satisfied through greater software interoperability and data integration. The objective of the Integrated Digital Built Environment (IDBE) joint working group is to address this challenge by bringing together experts from the Open Geospatial Consortium and buildingSMART to coordinate the development of the relevant data standards. This document is an output from IDBE in which we describe the state of three of the most prominent built environment standards – CityGML, IFC and LandInfra – and describe some of the problems that hinder their integration; finally, we propose actions points for overcoming these problems. + + 2005-11-21 + + + + 05-042r2 - - - This document provides the Annexes for the CDB Core: Model and Physical Structure Standard. The only exception is Annex A, Abstract Test Suite (ATS). The CDB ATS Annex is in Volume 1: Core document. + + This document describes the Web Services Façade which was developed by LISAsoft as part of the OWS-9 testbed. The document also includes discussions about lessons learned during the development, and suggestions for future development. +This Engineering Report documents the Web Services Façade work done within OWS-9 as an extensible, open source tool, which supports translations between different protocols for a specific web service. For the OWS-9 testbed, it has been set up to translate between POST and SOAP services for a Web Feature Service. However, it can be configured to support translations between multiple protocols, such as REST, SOAP, KVP, JSON, as well as supporting multiple web services. +The Web Services Façade is an extensible, open source tool, which supports translations between different protocols for a specific web service. For the OWS-9 testbed, it has been set up to translate between POST and SOAP services for a Web Feature Service. However, it can be configured to support translations between multiple protocols, such as REST, SOAP, KVP, JSON, as well as supporting multiple web services. + + OGC® Web Services Facade for OGC IP Engineering Report + 12-133 + + + 2014-08-22 + Web Services Facade for OGC IP Engineering Report + 12-133 + + + John Hudson - 2021-02-26 - - Volume 2: OGC CDB Core Model and Physical Structure Annexes (Best Practice) - 16-005r4 - - - 16-005r4 - Volume 2: OGC CDB Core Model and Physical Structure Annexes (Best Practice) - Carl Reed - + + 2019-08-20 + + This OGC Engineering Report (ER) documents the results of the CDB Vector Data in GeoPackage Interoperability Experiment (IE). The participants in this IE tested transforming CDB Shapefile vector data into one or more GeoPackage(s) and storing the result in a CDB data store. GeoPackage Version 1.2 and CDB Version 1.1 and related Best Practices were the standards baseline used for this experiment. The IE builds on the work described in the OGC CDB, Leveraging GeoPackage Discussion Paper. + +A primary objective of this IE was to agree and document possible change requests and/or best practices for storing vector data in a CDB data using encodings and/or containers other than Shapefiles. These suggested changes requests and/or best/practices will be used as the basis for CDB Standards Working Group (SWG) discussions related to possible revisions to the CDB standard. + 19-007 - 2013-02-19 - 12-156 - OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report + OGC CDB Vector Data in GeoPackage Interoperability Experiment + Carl Reed + 19-007 + CDB Vector Data in GeoPackage Interoperability Experiment - 12-156 - George Percivall - - OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report - The Reference Architecture Profiler (RAP) Advisor™ is a web based application that -recommends OGC Standards and OGC Reference Model (ORM) Sections that are -relevant to a system development; such that a community of interest could derive and -build a profile of suitable OGC standards to meet their specific needs. This Engineering -Report contains the requirements, conceptual design, development methodology, and -implementation of the RAP Advisor. -Initial development of the RAP Advisor™ was concurrent with the OGC Web Services -Testbed, Phase 9 (OWS-9) with NGA sponsorship. During OWS-9 timeframe, key -concepts of the RAP Advisor were confirmed through prototyping. Future development -is required to complete the functions and content of the Advisor. - + - - - 19-016r1 - OGC Testbed-15: Data Centric Security + - + OGC Coverage Implementation Schema + 09-146r6 + Coverage Implementation Schema - - Michael A. Leedahl - 2019-12-19 - OGC Testbed-15: Data Centric Security - 19-016r1 - The OGC Testbed-15 Data Centric Security Engineering Report (ER) discusses the current state of security in protecting data in a geospatial environment. The ER examines the use of encrypted container formats such as NATO STANAG 4778 Information on standard Metadata Binding with metadata as defined in NATO STANAG 4774 Confidentiality Metadata Label Syntax in combination with geospatial data using the encoding for an OGC Web Feature Service (WFS) FeatureCollection structure. This report also makes a recommendation for the creation of new media types to support output container formats such as STANAG 4778. The report then discusses various implementation scenarios in which a STANAG 4778 (eXtensible Markup Language (XML) container maintains encrypted data from author to service to viewer. These implementations use the new OGC API - Features - Part 1: Core with features encrypted using keys supplied by feature authors and users. + + Peter Baumann, Eric Hirschorn, Joan Masó + + 09-146r6 + + 2017-09-15 + Coverages represent homogeneous collections of values located in space/time, such as spatio-temporal sensor, image, simulation, and statistics data. Common examples include 1-D timeseries, 2-D imagery, 3-D x/y/t image timeseries and x/y/z geophysical voxel models, as well as 4-D x/y/z/t climate and ocean data. Generally, coverages encompass multi-dimen­sional regular and irregular grids, point clouds, and general meshes. + +This Coverage Implementation Schema (CIS) specifies the OGC coverage model by establishing a concrete, interoperable, conformance-testable coverage structure. It is based on the abstract concepts of OGC Abstract Topic 6 [1] (which is identical to ISO 19123) which spec­i­fies an abstract model which is not per se interoperable – in other words, many different and incompatible implementations of the abstract model are possible. CIS, on the other hand, is interoperable in the sense that coverages can be conformance tested, regardless of their data format encoding, down to the level of single “pixels” or “voxels.” + +Coverages can be encoded in any suitable format (such as GML, JSON, GeoTIFF, or Net­CDF) and can be partitioned, e.g., for a time-interleaved representation. Coverages are independent from service definitions and, therefore, can be accessed through a variety of OGC services types, such as the Web Coverage Service (WCS) Standard [8]. The coverage structure can serve a wide range of coverage application domains, thereby contributing to harmon­ization and interoperability between and across these domains. - - + + + OGC Testbed-17: OGC API - Moving Features Engineering Report + 21-028 + Dean Younge + The OGC Testbed-17 Moving Features thread conducted an interoperability feasibility study that examined specific scenarios that could be supported by a Moving Features Application Programming Interface (API). The use cases considered tracking objects based on motion imagery, analytical processing and visualization. This Engineering Report presents a specification of a prototype Moving Features API, that could serve as the foundation for a future draft OGC API — Moving Features standard. + + + - OGC API Hackathon 2019 Engineering Report - 19-062 + 21-028 + 2022-01-18 - - The subject of this Engineering Report (ER) is a hackathon event that was held from 20 to 21 June 2019 to advance the development of OGC Application Programming Interface (API) specifications. An API is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The OGC API Hackathon 2019, as the event was called, was hosted by Geovation at its hub in London, United Kingdom. The event was sponsored by the European Space Agency (ESA) and Ordnance Survey. - - OGC API Hackathon 2019 Engineering Report - Gobe Hobona - 2019-11-14 - 19-062 - - - - Paul Lunceford,Steve Matney,Tom Huggins,Chuck Heazel - - - *RETIRED* This document focuses on the goals, objectives, capabilities and recommendation for the Mediation Core Enterprise -Service. - 04-088 - EA-SIG Mediation White Paper - - 2004-02-20 - - 04-088 - EA-SIG Mediation White Paper - + OGC Testbed-17: OGC API - Moving Features Engineering Report + - - 2011-04-05 - 10-091r3 - CF-netCDF Core and Extensions Primer - 10-091r3 - - + + Geospatial User Feedback Standard: Conceptual Model + 15-097r1 + OGC® Geospatial User Feedback Standard: Conceptual Model + + This standard defines a conceptual Geospatial User Feedback (GUF) data model. Geospatial User Feedback is metadata that is predominantly produced by the consumers of geospatial data products as they use and gain experience with those products. This standard complements existing metadata conventions whereby documents recording dataset characteristics and production workflows are generated by the creator, publisher or curator of a data product. As a part of metadata, the GUF data model reuses some elements of ISO 19115-1:2014 (the updated version of the OGC Abstract Specification Topic 11) but not the general structure. This selective use of ISO metadata elements prioritizes future interoperability with developing ISO metadata models. This standard is designed to be used combination with an encoding standard. Initially an XML encoding following the ISO 19139 encoding rules is specified in a separate OGC implementation standard (OGC 15-098). In the future other encodings may be defined, including examples such as the use of JSON-LD based on parts of schema.org. - - This OGC primer provides an overview of the OGC CF-netCDF standards suite by describ-ing the CF-netCDF core and extensions. The CF-netCDF standard defines how to encode digital geospatial information representing space/time-varying phenomena + + 2016-12-22 + Joan Masó, Lucy Bastin - CF-netCDF Core and Extensions Primer - - Ben Domenico + 15-097r1 + + - - - 2020-07-07 - 19-088r2 - Vector Tiles Pilot 2: Summary Engineering Report - Gobe Hobona, Terry Idol - This OGC Engineering Report (ER) provides a summary of the research and findings from Phase 2 of the OGC Vector Tiles Pilot (VTP2). The goal of VTP2 was to deliver a consistent, interoperable online/offline architecture for vector tiles based on feature and tile servers, as well as GeoPackage. All Application Programming Interface (API) implementations and service types deployed in the pilot were implemented to support the prototype vector tile metadata model and filtering language. These were two essential work items of VTP2. The feature and tile servers included implementations of the OGC API – Features standard and the draft OGC API – Tiles specification. The feature and tile servers provided support for a variety of Coordinate Reference Systems (CRS). This ER provides an overview of each of the components, their implementation decisions and the challenges faced. - -The VTP2 participants intend to use the results of the work in VTP2 to inform the development of OGC APIs, GeoPackage, and web service standards to enable consistent use both online and offline, particularly in DDIL environments. Such consistent use of tiled feature data online and offline will improve interoperability and usability of geospatial applications. Therefore, the value of the VTP2 work to organizations is expected to be in the efficiencies and productivity that comes from greater interoperability and usability. - OGC Vector Tiles Pilot 2: Summary Engineering Report - 19-088r2 - + + - - + + Topic 2 - Referencing by coordinates + + 18-005r4 + Topic 02 - Referencing by coordinates + 18-005r4 + Roger Lott + 2019-02-08 + This document is identical in normative content with the latest edition (2019) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2019]. + - - 2019-01-09 - - GeoDCAT-AP - 18-001r1 - GeoDCAT-AP - - 18-001r1 + + This OGC® IndoorGML standard specifies an open data model and XML schema for indoor spatial information. IndoorGML is an application schema of OGC® GML 3.2.1. While there are several 3D building modelling standards such as CityGML, KML, and IFC, which deal with interior space of buildings from geometric, cartographic, and semantic viewpoints, IndoorGML intentionally focuses on modelling indoor spaces for navigation purposes. + 2014-12-02 + 14-005r3 + OGC® IndoorGML + + - Lieven Raes, Danny Vandenbroucke, Tomas Reznik - - - Improving discoverability of open geo-data and information is vital to increasing the use of these data in- and outside the geospatial expert community. -In this document we start to compare existing metadata standards, e.g., Dublin Core, ISO 19115/57/19, and INSPIRE, in the geospatial- and open data context. We also describe related linked open data initiatives such as RDF, SPARQL, and metadata publication initiatives, e.g., schema.org and Atom feeds. GeoDCAT is an initiative with the potential to integrate DCAT metadata as they are used in the open data and e-government community with EN ISO 19115/57/19 standards and INSPIRE metadata as they are used in the Geospatial community. GeoDCAT has - because it is based on RDF- the ability to publish metadata directly on the web without open and geospatial data portals. -To respond to the interest of different communities to preserve geospatial metadata resources and to support the uptake of GeoDCAT-AP implementations, best practices from different countries were identified and studied. The best practice cases focus on four domains (focus areas): metadata input (manually or automatically harvested), metadata publication into an integrated geo/open data portal, publication of metadata as Linked Open Data (LOD), and information mapping (ISO 19115, INSPIRE, DCAT, etc.). -GeoDCAT-AP is a mature solution for mapping metadata from the open data and geospatial domain. GeoDCAT helps to integrate and to publish metadata in data portals and directly on the world wide web. To conclude a GeoDCAT alignment exercise has been done with ISO 19115/19 and INSPIRE to improve the open data and geospatial metadata alignment in the future. - + + + IndoorGML + 14-005r3 + Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker + + + + + + + + + + + + + + + + + + + + Documents of type Release Notes + + + Documents of type Release Notes + Documents of type Release Notes - - + + + Clemens Portele + OGC® Geography Markup Language (GML) - Extended schemas and encoding rules + - Aleksandar Jelenak, Ted Habermann, Gerd Heber - Hierarchical Data Format Version 5 (HDF5®) Core Standard - 18-043r3 - Hierarchical Data Format Version 5 (HDF5®) is a data model, a programming interface, and a storage model for keeping and managing data. It supports an unlimited variety of data types, and is designed to be flexible and efficient for large and complex data. HDF5 is extensible via customizing data types, allowing communities and their applications to evolve in the use of HDF5. - -This document describes the HDF5 data model as an encoding standard particularly suitable to scientific and engineering geospatial applications that employ multidimensional numeric arrays to describe temporally and spatially varying phenomena. The data model is simple yet versatile, capable of supporting complex data relationships and dependencies through its grouping and linking mechanisms. It is also self-describing by accommodating user-defined metadata. - 18-043r3 - 2019-10-28 - OGC Hierarchical Data Format Version 5 (HDF5®) Core Standard - - + 10-129r1 + The Geography Markup Language (GML) is an XML encoding in compliance with ISO 19118 for the transport and storage of geographic information modelled in accordance with the conceptual modelling framework used in the ISO 19100 series of International Standards and including both the spatial and non-spatial properties of geographic features. + + Geography Markup Language (GML) - Extended schemas and encoding rules + 10-129r1 + 2012-02-07 - - - - - - - - - - - - - - - - - - - - - - 2009-10-13 - 09-123 - GeoRM Role Model - + + - Roland M. Wagner - 09-123 - The scope of this document is the update and the definition of GeoRM roles as a sub model of the GDI.NRW reference model (process model and architecture model). Key relationships are defined between these roles. - GeoRM Role Model + - - - - 12-152r1 - OWS-9 CITE Help Guide Engineering Report - - - Luis Bermudez - This Engineering Report was created as a deliverable of the CITE Thread as part of the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. This OGC® Engineering Report describes how to execute the CITE tests, how to select the conformance classes, how to access and download the TEAM Engine, Test Scripts and Reference Implementations, how to insert your own data and/or schemas along with a section that provides other community help resources. -This is not a normative document. + OGC® Web Query Service + Peter Baumann + 14-121r2 + Web Query Service + + 14-121r2 + This OGC Web Query Service (WQS) defines a service interface for retrieving any kind of subset of information provided by the server addressed. WQS is com¬pletely agnostic of any semantics and, therefore, not bound to any predefined structures, such as coordinates, fea-tures, coverages, or metadata. This makes WQS particularly suitable for retrieval from heter-ogeneous data offerings combining features, coverages, and catalog information in some ap-plication-defined way. A second use case is selective retrieval from a Capabilities document to avoid downloading large such documents and performing extraction on client side. +To this end, the Query request type is defined which, based on an XPath expression as input, extracts the matching information from the service’s offering and returns it (currently: as an XML document). + 2016-12-22 + + + 09-129 + AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report + Nadine Alameh - - - 12-152r1 - 2013-06-18 - OGC® OWS-9 CITE Help Guide Engineering Report + 09-129 + 2010-02-16 + + + AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report + + This AIP-2 Engineering Report (ER) describes a set of transverse technology Use Cases developed and applied in the GEOSS Architecture Implementation Pilot Phase 2 (AIP-2). Such Use Cases define reusable activities within a service-oriented architecture, tailored for the GEOSS environment. This report contains the general Use Cases that were specialized by community Working Groups to implement several specific Societal Benefit Area (SBA) Scenarios in AIP-2. The SBA Scenarios and specialized use cases are defined in separate AIP-2 ERs. This AIP-2 ER will be offered for consideration by the GEOSS Best Practice Registry editors and to OGC Technical Committee for consideration as a Best Practice. + - - 2007-02-06 - The Web Coverage Service (WCS) supports electronic retrieval of geospatial data as coverages - - John Evans - 06-083r8 - Web Coverage Service (WCS) Implementation Specification + + + 05-134 + Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option + + 05-134 + Keith Ryden + This part of OpenGIS + + 2005-11-30 - 06-083r8 + OpenGIS Implementation Specification for Geographic information - Simple feature access - + + + + + + Marwa Mabrouk + Location Services (OpenLS): Core Services [Parts 1-5] + 03-006r1 + OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform. + 2003-06-12 + OpenGIS Location Services (OpenLS): Core Services [Parts 1-5] + + 03-006r1 - - OpenGIS Web Coverage Service (WCS) Implementation Specification + - - 2019-02-11 + + 06-027r1 + Web Feature Service (WFS) Implementation Specification (Corrigendum) + 06-027r1 + 2006-08-22 Panagiotis (Peter) A. Vretanos + + + This document is a corrigendum for OGC Document 04-094. Specifically, this document corrects the files referenced in ANNEX A and found in the OGC schema repository. + + OpenGIS Web Feature Service (WFS) Implementation Specification (Corrigendum) + + + + - Feature data tiling, colloquially referred to as 'vector tiling', is a data delivery method that allows for large vector feature datasets to be systematically split into subsets or tiles [1]. This engineering report (ER) presents an extension specification for publishing of vector tiles data through an Application Programming Interface (API) that conforms to the emerging version 3.0 of the Web Feature Service (WFS) standard. The core of the WFS 3.0 standard offers direct fine-grained access to geospatial information at the feature level. The WFS standard specifies discovery and query operations for web services that publish feature data. Extensions to the WFS 3.0 Core API offer other capabilities such as transaction operations. + GeoPose 1.0 is an OGC Implementation Standard for exchanging the location and orientation of real or virtual geometric objects (“Poses”) within reference frames anchored to the earth’s surface (“Geo”) or within other astronomical coordinate systems. + +The standard specifies two Basic forms with no configuration options for common use cases, an Advanced form with more flexibility for more complex applications, and five composite GeoPose structures that support time series plus chain and graph structures. + +These eight Standardization Targets are independent. There are no dependencies between Targets and each may be implemented as needed to support a specific use case. + +The Standardization Targets share an implementation-neutral Logical Model which establishes the structure and relationships between GeoPose components and also between GeoPose data objects themselves in composite structures. Not all of the classes and properties of the Logical Model are expressed in individual Standardization Targets nor in the specific concrete data objects defined by this standard. Those elements that are expressed are denoted as implementation-neutral Structural Data Units (SDUs). SDUs are aliases for elements of the Logical Model, isolated to facilitate specification of their use in encoded GeoPose data objects for a specific Standardization Target. + +For each Standardization Target, each implementation technology and corresponding encoding format defines the encoding or serialization specified in a manner appropriate to that technology. + +GeoPose 1.0 specifies a single encoding in JSON format (IETF RFC 8259). Each Standardization Target has a JSON Schema (Internet-Draft draft-handrews-json-schema-02) encoding specification. The key standardization requirements specify that concrete JSON-encoded GeoPose data objects must conform to the corresponding JSON Schema definition. The individual elements identified in the encoding specification are composed of SDUs, tying the specifications back to the Logical Model. + +The GeoPose 1.0 Standard makes no assumptions about the interpretation of external specifications, for example, of reference frames. Nor does it assume or constrain services or interfaces providing conversion between GeoPoses of difference types or relying on different external reference frame definitions. - - - OGC Vector Tiles Pilot: WFS 3.0 Vector Tiles Extension Engineering Report - - 18-078 - 18-078 - WFS 3.0 Vector Tiles Extension Engineering Report - - - From ISO 19101, “A feature is an abstraction of a real world phenomenon”; it is a geographic feature if it is associated with a location relative to the Earth. - 08-126 - Topic 05 - Features - - 08-126 - Cliff Kottman, Carl Reed - Topic 5 - Features - - - - 2009-01-15 - + OGC GeoPose 1.0 Data Exchange Draft Standard + + + Carl Stephen Smyth + 2022-11-28 + + OGC GeoPose 1.0 Data Exchange Draft Standard + 21-056r10 + 21-056r10 - - 18-067r3 - This document presents the requirements for defining the Symbology Conceptual Core Model (SymCore), the conceptual basis to define symbology rules for the portrayal of geographical data. It is modular and extensible (one core model, many extensions), also encoding agnostic (one symbology model, many encodings). It contains a minimal set of abstract classes representing explicit extension points of the model. - + + OWS-6 Common CBRN Sensor Interface (CCSI)-Sensor Web Enablement (SWE) Engineering Report + + This document outlines the concepts, best practices, and lessons learned gathered from integrating Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) standard-compliant sensors into an OGC Sensor Web Enablement (SWE)-based architecture. The document also specifies a web service interface for interacting with CCSI sensors and defines the basis for a profile that can be used to represent CCSI sensor definitions, data, and commands in SWE formats. + + 09-007 + OWS-6 Common CBRN Sensor Interface (CCSI)-Sensor Web Enablement (SWE) Engineering Report - OGC Symbology Conceptual Model: Core Part - 18-067r3 - - - 2020-10-15 + 09-007 + Scott Fairgrieve - - - OGC Symbology Conceptual Model: Core Part + 2009-10-09 + + - + + OGC GeoPackage Related Tables Extension Interoperability Experiment Engineering Report - - OWS-9 Innovation - Coverages: Coverage Access (OPeNDAP) Study - 12-095 - 2013-06-18 - OGC® OWS-9 Innovation - Coverages: Coverage Access (OPeNDAP) Study - 12-095 - - James Gallagher, Peter Baumann - - This document represents the OWS-9 OWS Innovations Coverage Access Study -Engineering Report. It contributes knowledge based on the experience prototyping the -WCS 2.0 Service – Access Innovations component, established in close collaboration -with the OPeNDAP group. To this end, accessing a variety of coverage data types -considering WCS 2.0 and DAP 2.0 interfaces have been implemented and demonstrated. -The final result is a WCS 2.0 interface for the DAP 2.0 suite. + GeoPackage Related Tables Extension Interoperability Experiment Engineering Report + 17-093r1 + + + This OGC Engineering Report describes the results of the OGC GeoPackage (GPKG) Related Tables Extension Interoperability Experiment (GPKG-RTE IE). This IE tested a proposed extension to the OGC GeoPackage Encoding Standard (12-128r14). The GPKG-RTE defines the rules and requirements for associating tables with existing feature or attribute tables in a GeoPackage data store. As part of this IE, the participants performed Technology Integration Experiments (TIEs) where they produced GeoPackages that used this extension, loaded them into GPKG-compliant software systems, and observed the results. As a result of this work, the IE participants agree that the extension is fit for use and consideration as a standard by OGC. + 2018-08-22 + 17-093r1 + Jeff Yutzler, Ashley Antonides + - - ISO19115/ISO19119 Application Profile for CSW 2.0 (CAT2 AP ISO19115/19) - 04-038r2 - This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS - 2005-04-27 + + This OGC® document describes the Workflow Architecture developed in support of Geoprocessing Workflow and Sensor Web Enablement threads of OWS-5. This information includes the overall architecture description, concepts, and issues. It also provides detail on the Conflation Workflow created as an example implementation for geoprocessing in a workflow. This document establishes a sample architecture and associated lessons learned as general guidance. + + 07-138r1 + OWS-5 GeoProcessing Workflow Architecture Engineering Report + 2008-09-12 + + + 07-138r1 + OWS-5 GeoProcessing Workflow Architecture Engineering Report + Michael Werling + + + + + + + Philippe M + 2008-01-21 + 07-018r2 + + 07-018r2 + Sensor Planning Service Application Profile for EO Sensors + The SPS configuration proposed in this profile is intended to support the programming process of Earth Observation (EO) sensors system. This profile describes a consistent SPS configuration that can be supported by many satellite data providers, most of whom have existing facilities for the management of these programming requests. + - - - - ISO19115/ISO19119 Application Profile for CSW 2.0 (CAT2 AP ISO19115/19) - - 04-038r2 - Uwe Voges, Kristian Senkler + OpenGIS Sensor Planning Service Application Profile for EO Sensors + - + + + + Observations and Measurements + + 02-027 + Observations and Measurements + + Simon Cox + 02-027 + 2002-05-31 + + This document describes a framework and encoding for measurements and observations. - *RETIRED* This document focuses on the goals, objectives, capabilities and recommendation for the ESM Core Enterprise Service. The charter for this team was to address three fundamental questions: - -* What it Enterprise Service Management? -* What can we buy or build today? -* How should we invest for the future? - -This paper responds to those questions by defining and describing ESM, discussing what is being done today, and what the group sees for the future of ESM? - EA-SIG Enterprise Service Management White Paper - 04-087 - 04-087 + + + + OWS 4 WFS Temporal Investigation + David S. Burggraf, Ron Lake, Darko Androsevic + + 06-154 + WFS Temporal Investigation + 06-154 + + 2007-08-14 - Matt Murray,Jeff Stollman,Shue-Jane Thompson,Terry Plymell,Eli Hertz,Chuck Heazel - - EA-SIG Enterprise Service Management White Paper - - - 2004-02-20 + + The objective of the proposed temporal extensions to the WFS is to enable temporal/geospatial queries using the GML temporal types against GML dynamic features employing either the snapshot or time history model (time slices). - - 2014-02-24 + + 3D Data Container Engineering Report + + 3D Data Container Engineering Report + 20-029 + 20-029 + + 2020-10-22 + Timothy Miller, Gil Trenum, Josh Lieberman + + This OGC Engineering Report documents the goals, activities, experiences, and outcomes of the 3D Data Container and Tiles API Pilot. Participants in the Pilot cooperatively defined a GeoVolume (3D Geospatial Volume) resource and developed a GeoVolumes API based on the concept to provide access to different 2D and 3D geospatial dataset distributions organized by region of interest. Multiple client and server implementations of the GeoVolumes API successfully carried out technology interchange experiments that demonstrated the value of the API for improving interoperability between 3D geospatial data formats. + + + + OGC Testbed-15: Delta Updates Engineering Report + 2019-12-17 + OGC Testbed-15: Delta Updates Engineering Report + 19-012r1 + - This report summarizes the results of OGC’s Climatology-Hydrology Information Sharing Pilot, Phase 1 (CHISP-1). The objective of this initiative was to develop an inter-disciplinary, inter-agency and international virtual observatory system for water resources information from observations in the U.S. and Canada, building on current networks and capabilities. -The CHISP-1 Initiative was designed to support these Use Case functions: -• Hydrologic modeling for historical and current stream flow and groundwater conditions -• Modeling and assessment of nutrient load into the Great Lakes - + This OGC Testbed 15 Engineering Report (ER) documents the design of a service architecture that allows the delivery of prioritized updates of features to a client, possibly acting in a DDIL (Denied, Degraded, Intermitted or Limited Bandwidth) environment. Two different technical scenarios were investigated and tested: + +The enhancement of Web Feature Service (WFS) instances to support updates on features sets. + +Utilizing a Web Processing Service (WPS) instance to access features, without the need to modify the downstream data service. + 19-012r1 - OGC CHISP-1 Summary Engineering Report - CHISP-1 Summary Engineering Report - 13-046r2 - Lew Leinenweber - - 13-046r2 - - - Steve Liang, Tania Khalafbeigi, Hylke van der Schaaf - - SensorThings API Part 1: Sensing - 18-088 - OGC SensorThings API Part 1: Sensing Version 1.1 + - The OGC SensorThings API provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the web. At a high level the OGC SensorThings API provides two main functionalities and each function is handled by a part. The two parts are the Sensing part and the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. This document is version 1.1 and it is extending the first version of Sensing part. + Benjamin Pross + + + 05-007 + Web Processing Service + Web Processing Service + + + + + + This document is the specification for a Web Processing Service (WPS). +A Web Service Processing Service provides access to calculations or models which operate on spatially referenced data. The data required by the service can be available locally, or delivered across a network using data exchange standards such as Geography Markup Language (GML) or Geolinked Data Access Service (GDAS). + + Peter Schut + 05-007 + 2005-01-24 + + - 18-088 - - 2021-08-04 + + 07-074 + + Marwa Mabrouk + Location Service (OpenLS) Implementation Specification: Core Services + 07-074 + 2008-09-08 + OpenGIS Location Service (OpenLS) Implementation Specification: Core Services + This OpenGIS Interface Standard defines OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform. + + - - CF-netCDF3 Data Model Extension standard - 11-165r2 + + Web Map Context Documents + 03-036 + Web Map Context Documents + 03-036 + - - - + 2003-01-21 - Ben Domenico, Stefano Nativi - 11-165r2 - - 2013-01-03 - The OGC netCDF encoding supports electronic encoding of geospatial data, that is, digital geospatial information representing space and time-varying phenomena. -This standard specifies the CF-netCDF data model extension. -This standard specifies the CF-netCDF data model mapping onto the ISO 19123 coverage schema. -This standard deals with multi-dimensional gridded data and multi-dimensional multi-point data. -In particular, this extension standard encoding profile is limited to multi-point, and regular and warped grids; however, irregular grids are important in the CF-netCDF community and work is underway to expand the CF-netCDF to encompass other coverages types, including irregular gridded datasets. - - CF-netCDF3 Data Model Extension standard + + + Jean-Philippe Humblet + Create, store, and use state information from a WMS based client application + - - Pedro Gonçalves + + + + 06-131r4 + 2008-07-08 - 2021-12-14 + Renato Primavera + EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 + This OGC® document specifies the Earth Observation Products Extension Package for ebRIM (ISO/TS 15000-3) Application Profile of CSW 2.0, based on the [OGC 06-080r3] OGC® GML Application Schema for EO Products. + 06-131r4 + OGC® Catalogue Services Specification 2.0 Extension Package for ebRIM (ISO/TS 15000-3) Application Profile: Earth Observation - OGC Best Practice for Earth Observation Application Package - - - Best Practice for Earth Observation Application Package - 20-089r1 - Platforms for the exploitation of Earth Observation (EO) data have been developed by public and private companies in order to foster the usage of EO data and expand the market of Earth Observation-derived information. A fundamental principle of the platform operations concept is to move the EO data processing service’s user to the data and tools, as opposed to downloading, replicating, and exploiting data ‘at home’. In this scope, previous OGC activities initiated the development of an architecture to allow the ad-hoc deployment and execution of applications close to the physical location of the source data with the goal to minimize data transfer between data repositories and application processes. - -This document defines the Best Practice to package and deploy Earth Observation Applications in an Exploitation Platform. The document is targeting the implementation, packaging and deployment of EO Applications in support of collaborative work processes between developers and platform owners. - -The Best Practice includes recommendations for the application design patterns, package encoding, container and data interfaces for data stage-in and stage-out strategies focusing on three main viewpoints: Application, Package and Platform. - 20-089r1 - + - - Benjamin Pross, Christoph Stasch - Testbed-13: Workflows ER - 17-029r1 - - OGC Testbed-13: Workflows ER - 17-029r1 + + 16-064r1 + CityGML Quality Interoperability Experiment - + OGC® CityGML Quality Interoperability Experiment + - + 2016-08-01 + 16-064r1 - 2018-01-08 - This Engineering Report (ER) addresses the development of a consistent, flexible, adaptable workflow that will run behind the scenes. A user should be able to discover existing workflows via a catalog and execute them using their own datasets. An expert should be able to create workflows and to publish them. Previous OGC Testbed initiatives investigated workflows in the geospatial domain: - -OWS 3 Imagery Workflow Experiments - -OWS 4 WPS IPR Workflow descriptions and lessons learned - -OWS 4 Topology Quality Assessment Interoperability Program Report - -OWS 5 Data View Architecture Engineering Report - -OWS 6 Geoprocessing Workflow Architecture Engineering Report - -These initiatives mostly favored Business Processing Execution Language (BPEL) as the workflow execution language. More recent studies ([6], [7]) were performed using BPMN as a means for describing and executing workflows comprised of OGC Web services. This ER will give an overview about existing approaches to compose and execute geospatial workflows and will describe the approach taken in Testbed-13, taking into account security aspects. + This OGC Engineering Report specifies the results and findings of the CityGML Quality +Interoperability Experiment. Guidelines were developed for the following concepts: +&#1048576; Definition of data quality; +&#1048576; Data quality requirements and their specification; +&#1048576; Quality checking process of CityGML data; and +&#1048576; Description of validation results. +The desired outcomes of this Interoperability Experiment are to improve the +interoperability of CityGML data by removing some ambiguities from the current +standard and formally defining data quality requirements for a general CityGML data +specification. Further, the results of this work provides to the community (organizations +invested in capturing, procuring, or utilizing CityGML data) recommended +implementation guidance for 3D data and a suite of essential quality checking tools to +carry out quality assurance on CityGML data. + + + Detlev Wagner, Hugo Ledoux - + + Provides four protocols (GetCapabilities, GetMap, GetFeatureInfo and DescribeLayer) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. + 00-028 + Web Map Service + + + + Allan Doyle + 2000-04-19 + + 00-028 - - - 03-105r1 - Geography Markup Language (GML) Encoding Specification - 2004-04-19 - 03-105r1 - OpenGIS Geography Markup Language (GML) Encoding Specification - The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features. - - - Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside + Web Map Service - - Observations and Measurements - Part 1 - Observation schema - 07-022r1 - - Observations and Measurements - Part 1 - Observation schema - 07-022r1 + + 15-112r4 + Volume 3: OGC CDB Terms and Definitions (Normative) - - 2007-12-26 - - Simon Cox - The OpenGIS® Observations and Measurements Encoding Standard (O&M) defines an abstract model and an XML schema [www.w3.org/XML/Schema] encoding for observations and it provides support for common sampling strategies. O&M also provides a general framework for systems that deal in technical measurements in science and engineering. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. + 2021-02-26 + + + + Volume 3: OGC CDB Terms and Definitions (Normative) + Carl Reed + This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice. + 15-112r4 - - 05-084 - Catalog 2.0 Accessibility for OWS3 - Vincent Delfosse - The OGC Catalog-Web Profile is a complex specification that implies usage of many concepts, such as ressources, metadata, registry, registry information model, harvesting, etc. This document is a user-friendly introduction to these concepts. It will help the understanding of the Catalog specification in general and of the Catalog Web profile with ebRIM in particular. + + + Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure + 15-120r4 + + + 15-120r4 + Carl Reed + The CDB standard defines a standardized model and structure for a single, “versionable”, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. +The application of CDB to future simulation architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the High Level Architecture - -Federation Object Model (HLA/FOM) and DIS protocols, the application of the CDB standard provides a Common Environment to which inter-connected simulators share a common view of the simulated environment. +The CDB standard defines an open format for the storage, access and modification of a synthetic environment database. A synthetic environment is a computer simulation that represents activities at a high level of realism, from simulation of theaters of war to factories and manufacturing processes. These environments may be created within a single computer or a vast distributed network connected by local and wide area networks and augmented by super-realistic special effects and accurate behavioral models. SE allows visualization of and immersion into the environment being simulated . +This standard defines the organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The standard makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. A series of associated OGC Best Practice documents define rules and guidelines for data representation of real world features. + + 2017-02-23 + Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure - 05-084 - - 2006-05-09 - - - Catalog 2.0 Accessibility for OWS3 - + - - 2014-07-16 - Ingo Simonis, Stephane Fellah - 14-049 - Testbed 10 Cross Community Interoperability (CCI) Ontology Engineering Report - 14-049 - Testbed 10 ontology work focused on: -• A general examination of ontologies in the context of OGC data modeling, handling, and organization. Testbed-10 has started to define a consistent set of ontologies implementing solid theoretical foundations and semantics. -• The definition of a core ontologies for representing incident information used by Incident Management Systems (IMS) and mapping symbologies used in the emergency and disaster management domain with the goal to improve interoperability between different IMS symbology sets used across multi-level jurisdiction. -• Addressed ontology mapping between hydrology feature models using SPARQL and OWL2. - - + + + OGC® Earth Observation Metadata profile of Observations & Measurements + + + Jerome Gasperi, Frédéric Houbie, Andrew Woolf, Steven Smolders + 10-157r4 + + Earth Observation Metadata profile of Observations & Measurements + 10-157r4 + 2016-06-09 + This OGC Implementation Standard defines a profile of Observations and Measurements (ISO 19156:2010 and OGC 10-025r1) for describing Earth Observation products (EO products). +This profile is intended to provide a standard schema for encoding Earth Observation product metadata to support the description and cataloguing of products from sensors aboard EO satellites. +The metadata being defined in this document is applicable in a number of places where EO product metadata is needed. +1. In the EO Product Extension Package for ebRIM (OGC 10-189). This extension package defines how to catalog Earth Observation product metadata described by this document. Using this metadata model and the Catalogue Service defined in OGC 10-189, client applications can provide the functionality to discover EO Products. Providing an efficient encoding for EO Product metadata cataloguing and discovery is the prime purpose of this specification. +2. In the EO Application Profile of WMS (OGC 07-063r1). The GetFeatureInfo operation on the outline (footprint layer) should return metadata following the Earth Observation Metadata profile of Observation and Measurements. +3. In a coverage downloaded via an EO WCS AP (OGC 10-140). In WCS 2.0 (OGC 10-084), the GetCoverage and DescribeCoverage response contains the metadata element intended to store metadata information about the coverage. The Earth Observation Application profile of WCS (OGC 10-140) specifies that the metadata format preferred for Earth Observation is defined by this document. +4. Potentially enclosed within an actual product to describe georeferencing information as for instance within the JPEG2000 format using GMLJP2. GMLJP2 defines how to store GML coverage metadata inside a JP2 file. +Earth Observation data products are generally managed within logical collections that are usually structured to contain data items derived from sensors onboard a satellite or series of satellites. The key characteristics differentiating products within the collections are date of acquisition, location as well as characteristics depending on the type of sensor, For example, key characteristics for optical imagery are the possible presence of cloud, haze, smokes or other atmospheric or on ground phenomena obscuring the image. +The common metadata used to distinguish EO products types are presented in this document for generic and thematic EO products (i.e optical, radar, atmospheric, altimetry, limb-looking and synthesis and systematic products). From these metadata the encodings are derived according to standard schemas. In addition, this document describes the mechanism used to extend these schemas to specific missions and for specific purposes such as long term data preservation. + - - OGC® Testbed 10 Cross Community Interoperability (CCI) Ontology Engineering Report - - - - OGC Testbed-16: Full Motion Video to Moving Features Engineering Report - - + + + - Full Motion Video to Moving Features Engineering Report - 20-036 - - This OGC Testbed-16 Engineering Report (ER) evaluates the suitability of existing OGC standards for the generation of Moving Features from Full Motion Video (FMV) that has an embedded stream of detected moving objects. + City Geography Markup Language (CityGML) Part 2: GML Encoding Standard + 21-006r2 + This Standard documents the OGC GML Implementation Specification (IS) for the CityGML 3.0 Conceptual Model. The CityGML 3.0 conceptual model is a Platform Independent Model (PIM). It defines concepts in a manner which is independent of any implementing technology. As such, the CityGML Conceptual Model cannot be implemented directly. Rather, it serves as the base for Platform Specific Models (PSM). A PSM adds to the PIM the technology-specific details needed to fully define the CityGML model for use with a specific technology. The PSM can then be used to generate the schema and other artifacts needed to build CityGML 3.0 implementations. -This ER presents several proof of concept applications that accept FMVs, with multiple encoded Video Moving Target Indicators (VMTI), and combines the VMTIs into separate tracks that are then encoded to OGC Moving Features. +This standard defines the PSMs and schemas for the CityGML 3.0 Implementation Specification (IS) for Geography Markup Language (GML) implemenations. The GML schemas are explained in an overview and design decisions that have been made are documented as well. -In addition, the ER explores the generation of records encoded according to OGC Sensor Model Language (SensorML) 2.0 standard describing the collection platform and relevant telemetry information from the key-value stream content encoded according to the MISB 0601 and 0903 specifications of the Motion Imagery Standards Board (MISB). - - 2021-01-13 - - Emeric Beaufays, C.J. Stanbridge, Rob Smith - 20-036 - - - 2019-07-10 - 2017-09-23 - - - Semantic Sensor Network Ontology - 16-079 + + + Tatjana Kutzner, Carl Stephen Smyth, Claus Nagel, Volker Coors, Diego Vinasco-Alvarez, Nobuhiro Ishi + + 2023-06-20 + OGC City Geography Markup Language (CityGML) Part 2: GML Encoding Standard + 21-006r2 + + + + + + 11-018 + - The Semantic Sensor Network (SSN) ontology is an ontology for describing sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties, as well as actuators. SSN follows a horizontal and vertical modularization architecture by including a lightweight but self-contained core ontology called SOSA (Sensor, Observation, Sample, and Actuator) for its elementary classes and properties. With their different scope and different degrees of axiomatization, SSN and SOSA are able to support a wide range of applications and use cases, including satellite imagery, large-scale scientific monitoring, industrial and household infrastructures, social sensing, citizen science, observation-driven ontology engineering, and the Web of Things. Both ontologies are described below, and examples of their usage are given. - -The namespace for SSN terms is http://www.w3.org/ns/ssn/. -The namespace for SOSA terms is http://www.w3.org/ns/sosa/. - -The suggested prefix for the SSN namespace is ssn. -The suggested prefix for the SOSA namespace is sosa. + This Discussion Paper proposes model for license-based access control to SOAP services, based on OASIS SAML 2.0. This approach is a potential solution for license-based access control, which requires the possession of a valid license for getting access to a service. Use of digital licenses allow users to act on or with web services to which they are associated -The SSN ontology is available at http://www.w3.org/ns/ssn/. -The SOSA ontology is available at http://www.w3.org/ns/sosa/. - The Semantic Sensor Network (SSN) ontology is an ontology for describing sensors and their observations, the involved procedures, the studied features of interest, the samples used to do so, and the observed properties, as well as actuators. SSN follows a horizontal and vertical modularization architecture by including a lightweight but self-contained core ontology called SOSA (Sensor, Observation, Sample, and Actuator) for its elementary classes and properties. With their different scope and different degrees of axiomatization, SSN and SOSA are able to support a wide range of applications and use cases, including satellite imagery, large-scale scientific monitoring, industrial and household infrastructures, social sensing, citizen science, observation-driven ontology engineering, and the Web of Things. Both ontologies are described below, and examples of their usage are given. - - - +This document re-uses content produced by the OGC GeoRM Common 1.0 Standards Working Group and combined that with the document OGC 10-125, which was posted to an internal OGC document archive (Pending Documents) but is not publicly available. +This document does not claim compliance to the GeoDRM reference model (ISO 19153), although the authors are not yet aware of any conflicts to it. + - Armin Haller, Krzysztof Janowicz, Simon Cox, Danh Le Phuoc, Kerry Taylor, Maxime Lefrançois + 2011-03-30 + 11-018 + License-Based Access Control + License-Based Access Control + Rüdiger Gartmann, Bastian Schäffer + + + Joshua Lieberman - Semantic Sensor Network Ontology - 16-079 + 03-063r1 + + Critical Infrastructure Collaborative Environment Architecture: Computational Viewpoint + 03-063r1 + + + 2003-06-02 + + *RETIRED* The objective of this document is to provide a vendor-neutral interoperable framework that enables collaborating communities to rapidly and collaboratively publish, discover, integrate and use geospatial information concerned with the protection of critical infrastructure systems in a range of sectors. Specifically, this document specifies a Computational Architecture viewpoint for a Critical Infrastructure Collaborative Environment (CICE). + + Critical Infrastructure Collaborative Environment Architecture: Computational Viewpoint - - Stephan Meissl, Peter Baumann - OWS-8 WCS 2.0 Earth Observation Application Profile Compliance Tests Engineering Report - 11-095r1 - This Engineering Report describes and evaluates the specification of EO-WCS ATS and the implementation of ETS for use within an OGC SOA processing chain. + - 2011-12-19 - + + OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV) + 14-084r2 + Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf + 14-084r2 + Moving Features Encoding Extension: Simple Comma Separated Values (CSV) + This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange. + + + + 2015-02-17 + + + 2017-10-20 + Future City Pilot 1 - Automating Urban Planning Using Web Processing Service Engineering Report + 16-099 + Mohsen Kalantari + + + Numerous and diverse technologies push cities towards open and platform-independent information infrastructures to manage human, natural, and physical systems. Future Cities Pilot 1 is an OGC interoperability initiative that aims to demonstrate how cities can begin to reap the benefits of open standards. This document reports how Web Processing Standard (WPS) of OGC was successfully used in automating urban planning processes. This document details the implementation of urban planning processes and rules concerning urban development approval processes. + Future City Pilot 1 - Automating Urban Planning Using Web Processing Service Engineering Report + - 11-095r1 - - OWS-8 WCS 2.0 Earth Observation Application Profile Compliance Tests Engineering Report + + 16-099 - - 00-117 - Draft Abstract Spec for Location Based Services. Never formally adopted - Topic 17 - Location Based Mobile Services - Cliff Kottman - 2000-05-15 - - Topic 17 - Location Based Mobile Services - 00-117 - - + + Arliss Whiteside, Jim Greenwood + This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Standards. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Standard must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses. + 2010-04-07 + 06-121r9 + Web Service Common Implementation Specification + OGC Web Service Common Implementation Specification + + + + + + + 06-121r9 + + + 13-080r3 + Military Operations Geospatial Interoperability Experiment (MOGIE) + + + OGC® Military Operations Geospatial Interoperability Experiment (MOGIE) + Frank Klucznik, Matthew Weber, Robin Houtmeyers, Roger Brackin + 13-080r3 + 2013-10-25 + experiment demonstrated that GML content can be embedded in NIEM conformant XML and be exploited by commercial and open source tools without loss of precision (e.g., right number of bits) or accuracy (e.g., physical location on a map). Embedding GML in NIEM conformant XML was accomplished in MOGIE using the NIEM adapter. + + + + + + + 2023 Open Standards and Open Source Software Code Sprint Summary Engineering Report + 23-025 + + 2023 Open Standards and Open Source Software Code Sprint Summary Engineering Report + 23-025 + + + Gobe Hobona, Joana Simoes, Tom Kralidis, Martin Desruisseaux, Angelos Tzotsos + The subject of this Engineering Report (ER) is a code sprint that was held from the 25th to the 27th of April 2023 to advance support of open geospatial standards within the developer community, while also advancing the standards themselves. The code sprint was organized by the Open Geospatial Consortium (OGC), the Open Source Geospatial Foundation (OSGeo), and the Apache Software Foundation (ASF). The code sprint was sponsored by the Ordnance Survey and hosted by Camptocamp. + 2023-11-01 - + + Philippe Duschene, Jerome Sonnet - 12-117r1 - + 2005-04-22 - Ryosuke Shibasaki - OGC Standard for Moving Features; Requirements - Applications using moving feature data, typically on vehicles and pedestrians, have -recently been rapidly increasing. Innovative applications are expected to require the -overlay and integration of moving feature data from different sources to create more -social and business values. Efforts in this direction should be encouraged by ensuring -smoother data exchange because handling and integrating moving feature data will -broaden the market for geo-spatial information. This discussion paper provides an -overview of some actual and potential geo-spatial applications using moving feature data -and the existing international standards or specifications on moving feature data handling. -It also summarizes the requirements set on the standards for moving feature data, and -finally proposes the development of a new OGC standard for moving features. - 2012-12-06 - + This change proposal is an outcome of the Common Architecture thread of the OpenGIS Web Service 2 initiative. The aim is to add support for a standard WSDL description of the WMS interface in version 1.3.1. + WMS Change Request: Support for WSDL & SOAP + 04-050r1 + + 04-050r1 + WMS Change Request: Support for WSDL & SOAP + - 12-117r1 - OGC Standard for Moving Features; Requirements - - Volume 8: CDB Spatial and Coordinate Reference Systems Guidance - 16-011r4 - 16-011r4 - Volume 8: CDB Spatial and Coordinate Reference Systems Guidance - Carl Reed + + + An OpenGIS Feature Collection is an abstract object consisting of Feature Instances, their Feature Schema, and Project Schema. + Topic 10 - Feature Collections + 99-110 - 2018-12-19 - - - - - Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames. -In previous versions of the CDB standard, this CDB volume was Appendix K in CDB Version 3.2 as submitted to the OGC. - - - - 12-066 - Modeling an application domain extension of CityGML in UML - - - - - - This paper presents key aspects of the development of a Dutch 3D standard IMGeo as a CityGML ADE. The new ADE is modeled using UML class diagrams. However the OGC CityGML specification does not provide clear rules on modeling an ADE in UML. This paper describes how the extension was built, which provides general insight how CityGML can be extended for a specific applications starting from the UML diagrams. Several alternatives for modeling ADEs in UML have been investigated and compared. The best suited for the 3D standard option is selected and applied. Open issues and challenges are discussed in the conclusions. - 12-066 - 2012-07-12 - 2014-01-31 - - - Linda van den Brink, Jantien Stoter, Sisi Zlatanova - - Modeling an application domain extension of CityGML in UML + 99-110 + + Topic 10 - Feature Collections + Cliff Kottman + 1999-04-07 + - - OGC Testbed-16: Machine Learning Engineering Report - 20-015r2 - OGC Testbed-16: Machine Learning Engineering Report - 20-015r2 - - - This engineering report describes the work performed in the Machine Learning Thread of OGC’s Testbed-16 initiative. - -Previous OGC testbed tasks concerned with Machine Learning (ML) concentrated on the methods and apparatus of training models to produce high quality results. The work reported in this ER, however, focuses less on the accuracy of machine models and more on how the entire machine learning processing chain from discovering training data to visualizing the results of a ML model run can be integrated into a standards-based data infrastructure specifically based on OGC interface standards. - -The work performed in this thread consisted of: - -Training ML models; - -Deploying trained ML models; - -Making deployed ML models discoverable; - -Executing an ML model; - -Publishing the results from executing a ML model; - -Visualizing the results from running a ML model. - -At each step, the following OGC and related standards were integrated into the workflow to provide an infrastructure upon which the above activities were performed: - -OGC API - Features: Approved OGC Standard that provides API building blocks to create, retrieve, modify and query features on the Web. - -OGC API - Coverages: Draft OGC Standard that provides API building blocks to create, retrieve, modify and query coverages on the Web. - -OGC API - Records: Draft OGC Standard that provides API building block to create, modify and query catalogues on the Web. - -Application Deployment and Execution Service: Draft OGC Standard that provides API building blocks to deploy, execute and retrieve results of processes on the Web. - -MapML is a specification that was published by the Maps For HTML Community Group. It extends the base HTML map element to handle the display and editing of interactive geographic maps and map data without the need of special plugins or JavaScript libraries. The Design of MapML resolves a Web Platform gap by combining map and map data semantics into a hypermedia format that is syntactically and architecturally compatible with and derived from HTML. It provides a standardized way for declarative HTML content to communicate with custom spatial server software (which currently use HTTP APIs based on multiple queries and responses). It allows map and map data semantics to be either included in HTML directly, or referred to at arbitrary URLs that describe stand-alone layers of map content, including hyper-linked annotations to further content. - -Particular emphasis was placed on using services based on the emerging OGC API Framework suite of API building blocks. + + 06-098 + Proposal for WCS Transactional - WCS-T + 06-098 + 2007-08-13 + Version 1.0 of the Web Coverage Service (WCS) Specification does not address how coverage data gets added to or deleted from a server; it is assumed that some implementation-specific process exists for handling this, likely on the back end (server-side). One of the goals of OWS-4 was to extend WCS to support these operations, generally referred to as + Change Request: WCS: Proposal for WCS Transactional - WCS-T - - Panagiotis (Peter) A. Vretanos - 2021-02-15 + Michael Gerlek + - + + + - - Observations and Measurements - 03-022r3 - - 2003-02-04 - 03-022r3 - This document describes a framework and encoding for measurements and observations. - Simon Cox - Observations and Measurements - - + + + The GeoPackage Standards Working Group (SWG) presents a discussion of symbology encapsulation for conveying presentation information for vector features contained within in a GeoPackage. + 2016-04-26 + Implications for an OGC GeoPackage Symbology Encoding Standard + 15-122r1 + 15-122r1 + + + + Randolph Gladish + Implications for an OGC GeoPackage Symbology Encoding Standard - - - 2018-01-11 - Charles Chen - Testbed-13: Geospatial Taxonomies Engineering Report - 17-036 + + Feature Type Catalogue Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 + 07-172r1 + + 07-172r1 + + + 2008-05-13 + This document describes a Feature Type Catalogue extension package for the OGC® ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 [OGC 05-025r3]. It defines the way an ISO 19110 [ISO 19110:2005] Feature Type Catalogue is included within a Registry, and provides an information model and stored queries for such an inclusion. + + Feature Type Catalogue Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 + Kristin Stock - This Engineering Report (ER) documents the Geospatial Taxonomy research activities conducted by the Aviation (AVI) subthread of the Cross Community Interoperability (CCI) thread in OGC Testbed 13. One of the critical factors in the overall usability of services - and System Wide Information Management (SWIM) enabled services in particular - is the ability of a service to be discovered. The ability of a service to be discovered is assured by providing a uniformly interpretable set of service metadata that can be accessed by a service consumer through a retrieval mechanism (e.g., a service registry). Such a set of metadata (commonly referred to as a service description) has been defined by Federal Aviation Administration (FAA) and European Organization for the Safety of Air Navigation (EUROCONTROL) and formalized in a Service Description Conceptual Model (SDCM) [SDCM]. + + + + + Coverage Implementation Schema with Corrigendum + 09-146r8 + 09-146r8 + Coverages represent homogeneous collections of values located in space/time, such as spatio-temporal sensor, image, simulation, and statistics data. Common examples include 1-D timeseries, 2-D imagery, 3-D x/y/t image timeseries and x/y/z geophysical voxel models, as well as 4-D x/y/z/t climate and ocean data. Generally, coverages encompass multi-dimen­sional regular and irregular grids, point clouds, and general meshes. -The SDCM is currently used in standard service description documents and service registries by both FAA and EUROCONTROL. As part of the effort of enhancing service discovery, both organizations also use a number of categories that can be associated with all services and are generally referred to as taxonomies. The current set of taxonomies used by both EUROCONTROL and FAA categorizes (i.e., meta tags) services based on their availability status, interface model, data product, etc. However, despite the increasing role of OGC services in the SWIM environment, no taxonomies for categorizing services based on geographical coverage or other geospatial characteristics have been defined. This ER documents the work conducted as part of Testbed 13 CCI thread and AVI subthread to identify and classify SWIM-enabled Service Oriented Architecture (SOA) services with geographical taxonomies and the integration thereof into SDCM. - 17-036 +This Coverage Implementation Schema (CIS) specifies the OGC coverage model by establishing a concrete, interoperable, conformance-testable coverage structure. It is based on the abstract concepts of OGC Abstract Topic 6 [1] (which is identical to ISO 19123) which spec­i­fies an abstract model which is not per se interoperable – in other words, many different and incompatible implementations of the abstract model are possible. CIS, on the other hand, is interoperable in the sense that coverages can be conformance tested, regardless of their data format encoding, down to the level of single “pixels” or “voxels.” + +Coverages can be encoded in any suitable format (such as GML, JSON, GeoTIFF, or Net­CDF) and can be partitioned, e.g., for a time-interleaved representation. Coverages are independent from service definitions and, therefore, can be accessed through a variety of OGC services types, such as the Web Coverage Service (WCS) Standard [8]. The coverage structure can serve a wide range of coverage application domains, thereby contributing to harmon­ization and interoperability between and across these domains. - - OGC Testbed-13: Geospatial Taxonomies Engineering Report - + + OGC Coverage Implementation Schema with Corrigendum + - + Peter Baumann, Eric Hirschorn, Joan Masó + + 2019-10-28 - - 20-000r1 + + + - + Describes modelling requirements for spatial referencing by coordinates. This document supplements and corrects ISO 19111. There has never been a motion to adopt 01-063r2. A motion was approved at the Dec 01 meeting in Vancouver to adopt 01-063r1 - - 20-000r1 - CityGML Urban Planning ADE for i-Urban Revitalization - Nobuhiro Ishimaru, Chikako Kurokawa, Yuichi Tanaka, Tomohisa Oishi, Kentaro Akahoshi, Tatjana Kutzne - - - This OGC Discussion Paper introduces the CityGML Urban Planning Application Domain Extension (ADE) published by the Japanese government for the i-Urban Revitalization (i-UR). -The i-UR is an information infrastructure dedicated for urban planning to contribute to data-driven urban development and urban revitalization. OGC KML has been utilized more than 10 years for i-UR, however, there were huge requirements for use of application-specific semantics information for urban planning and multi-scale structured information by LOD (Levels of Detail). -By using CityGML ADE mechanism, the Urban Planning ADE provides application-specific semantics information integrating with 3D geometry data to visualize and analyze the urban situation. Additionally, the Urban Planning ADE introduces newly extended LOD, LOD-1 (minus one) for nationwide city models and LOD-2 (minus two) for a worldwide city model to visualize global urban activities and study urban structure by integrating geospatial information and statistical grid information. -This paper describes a brief introduction of i-Urban Revitalization, data model of the Urban Planning ADE and data experiment examples to discuss further utilization of the Urban Planning ADE in urban planning applications. - - CityGML Urban Planning ADE for i-Urban Revitalization - 2020-04-17 + 02-102 + Topic 02 - Spatial Referencing by Coordinates + + Roel Nicolai + Topic 2 - Spatial Referencing by Coordinates + 2002-03-08 + 02-102 + - - Christoph Stasch, Simon Jirka - 16-035 - 2017-05-12 - 16-035 - Testbed-12 REST Architecture Engineering Report + + 06-080r4 + GML 3.1.1 Application Schema for EO products + GML 3.1.1 Application Schema for EO products + 06-080r4 + This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGC + + 2010-02-25 + + + + + Jerome Gasperi + + + + Simon Cox + + Observations and Measurements + 05-087r4 + The general models and XML encodings for observations and measurements, including but not restricted to those using sensors. + 05-087r4 - + + 2006-10-11 - - - REST interfaces facilitate the application of OGC standards in many novel application scenarios, e.g. implementing OGC clients on constrained devices, as they ease the implementation of service requests and simplify the interaction patterns. Thereby, REST serves as a complementary technology to the already existing SOAP/POX provided by most of the current OGC standards. This engineering report (ER) provides an overview on different REST service implementations in the Testbed-12 and in related activities. As a result, this ER can be used to develop recommendations on architecture guidelines for providing REST interfaces in the geospatial domain. - Testbed-12 REST Architecture Engineering Report + + Observations and Measurements - - The scenario of rapidly growing geodata catalogues requires tools focused on facilitating users the choice of products. Having populated quality fields in metadata allows the users to rank and then select the best fit-for-purpose products. For example, decision-makers would be able to find quality and uncertainty measures to take the best decisions as well as to perform dataset intercomparison. In addition, it allows other components (such as visualization, discovery, or comparison tools) to be quality-aware and interoperable. - -This ER deals with completeness, logical consistency, positional accuracy, temporal accuracy and thematic accuracy issues to improve quality description in the metadata for imagery. Based on ISO 19157, UncertML and QualityML standardized measures, this ER describes how to encode quality measures in order to allow datasets comparison. Moreover, description of pixel-level quality measures is also included. Finally, alternatives to communicate tile level quality as well as mosaic products quality are proposed. - - 16-050 - Testbed-12 Imagery Quality and Accuracy Engineering Report + + This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. +InfraGML is published as a multi-part standard. This Part 0 addresses the Core Requirements Class from LandInfra. + OGC InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard + 16-100r2 + InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard + Paul Scarponcini + 16-100r2 - + 2017-08-16 - - 16-050 - Testbed-12 Imagery Quality and Accuracy Engineering Report - Joan Masó and Alaitz Zabala - - 2017-05-12 + + + + - - OWS3 GML Topology Investigation - 05-102r1 + + + + 2014-02-24 + + WaterML 2.0: Part 1- Timeseries + 10-126r4 + Peter Taylor + + OGC® WaterML 2.0: Part 1- Timeseries + 10-126r4 - 2006-05-09 - 05-102r1 - Part 1 of this investigation is conducted by Galdos Systems. In this part, the OWS3 MSD3 geometric description is extended to include a topology encoding as defined by the MSD3 schema. Part 2 (Clause 6.2) of this investigation is conducted by Intergraph Corp. and describes and discusses the impacts of encoding topology within the GML data. - - - - OWS3 GML Topology Investigation - - - David Burggraf, Stan Tillman + WaterML 2.0 is a standard information model for the representation of water observations data, with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of exchange requirements, some of which are described later in this document. - - OGC EO Dataset Metadata GeoJSON(-LD) Encoding Standard - Y. Coene, U. Voges, O. Barois - 2020-02-14 - 17-003r2 - JavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. This OGC standard describes a GeoJSON [NR2] and JSON-LD [NR3] encoding for Earth Observation (EO) metadata for datasets (granules). This standard can be applied to encode metadata based on the Earth Observation Metadata Profile of Observations and Measurements (O&M) OGC 10-157r4 [OR1] or as an encoding of the Unified Metadata Model for Granules (UMM-G) conceptual model [OR2]. - -The GeoJSON encoding defined in this document is defined as a compaction[1] through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF XML [OR11] and RDF Turtle [OR12]. - -This document makes no assumptions as to the “service” interfaces through which the metadata are accessed and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful Architecture. The documented approach can be applied in combination with the following technologies: - -OGC OpenSearch extensions [OR19], [OR20], [OR25], -W3C Linked Data Platform [OR21], [OR22], -OASIS searchRetrieve [OR23], -OASIS OData [OR24]. -GeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features. - -JSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR18] which allows validation of instances against these schemas. - - + + OGC API - Maps - Part 1: Core + 20-058 + - - 17-003r2 - EO Dataset Metadata GeoJSON(-LD) Encoding Standard + - + + The OGC API — Maps — Part 1: Core Standard defines a Web API for requesting maps over the Web. A map is a portrayal of geographic information as a digital representation suitable for display on a rendering device (adapted from OGC 06-042/ISO 19128 OpenGIS® Web Map Server (WMS) Implementation Specification). Implementations of the OGC API — Maps Standard are designed for a client to easily: + +Request a visual representation of one or more geospatial data layers in different styles; +Select by area, time and resolution of interest; +Change parameters such as the background color and coordinate reference systems. +A server that implements OGC API — Maps provides information about what maps are offered. OGC API — Maps addresses use cases similar to those addressed by the OGC 06-042/ISO 19128 OpenGIS® Web Map Server (WMS) Implementation Specification Standard. + 20-058 + 2024-08-09 + + OGC API - Maps - Part 1: Core + Joan Masó, Jérôme Jacovella-St-Louis - - - 07-045r1 - Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum - + + 2004-02-18 + + + + Jeff de La Beaujardiere + Provides three operations (GetCapabilities, GetMap, and GetFeatureInfo) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. - 07-045r1 - - Catalogue services are the key technology for locating, managing and maintaining -distributed geo-resources (i.e. geospatial data, applications and services). With OGC -catalogue services, client applications are capable of searching for geo-resources in a -standardized way (i.e. through standardized interfaces and operations) and, ideally, they -are based on a well-known information model, which includes spatial references and -further descriptive (thematic) information that enables client applications to search for -geo-resources in very efficient ways. -Whereas interfaces and operations of OGC catalogue services are well defined, it is left -up to the developer of the system to define a specific information model which a -catalogue service instance provides. This includes, but is not limited to, the information -which can be inserted in the catalog, supported query languages, available search terms, -response/result sets, etc. This point is of major importance with respect to interoperability -between different catalogue service instances. -In Europe, running catalogue instances result from work being done within different SDI -initiatives (e.g. SDI NRW Initiative1, Germany/Netherlands cross-border initiative, JRC -EU Portal, EUROSTAT, Inspire, German SDI initiative). Members of these initiatives -have developed an ISO-based application profile for ISO19115 metadata for -geodata/geospatial applications and ISO19119-based metadata for tightly and looselycoupled -geospatial services. The foundations of this profile were the OGC catalogue -specification (1.1.1), the OGC Web Registry Server (WRS) 0.0.2, OGC Web Services -Stateless Catalogue Profile (StCS) 0.0.6 and ISO 19115/19119 for content description. -OGC's catalogue revision working group (CS-RWG) has revised and integrated the -catalogue implementation specification v1.1.1 that have resulted in CS 2.0.2. One part of -this OGC specification comprises the definition of application profiles according to ISO -19106 (Geographic information – Profiles). The overall goal of these profiles is to -improve interoperability between systems conforming to a specific profile. Experience -has shown that the need for application profiles results from the fact that in practice, there -is no single solution for catalogue services that fits every user’s needs. As stated in CS -2.0.2, a base profile that provides a basic set of information objects has to be supported -by each catalogue instance; in addition, application profiles for different information -communities can be specified. -Hence, this document specifies an application profile for ISO 19115:2003/ISO -19119:2005 metadata with support for XML encoding per ISO/TS19139:2007 [ISO/TS19139]2 and HTTP protocol binding. It relies on requirements coming from the -CS/CSW 2.0 specification (OGC CS 2.0.2, OGC document 07-006). The application -profile will form the basis of conformance tests and reference implementations. - 2018-03-09 - - Uwe Voges, Kristian Senkler - OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum + Web Map Service + Web Map Service (Recommendation Paper) + 03-109r1 + 03-109r1 + - - This Engineering Report specifies conventions for conveying information about data -quality through the OGC Web Map Service Standard (known hereafter as the “WMS-Q -conventions”), OGC Web Map Tile Service Standard (known hereafter as the “WMTS-Q -conventions”), OGC KML (known hereafter as the “KML-Q conventions”) and OGC -Augmented Reality Markup Language. - + + Catalog Interface + 02-087r3 + Catalog Interface + + + Doug Nebert - 12-160r1 - OWS 9 Data Quality and Web Mapping Engineering Report - OGC® OWS 9 Data Quality and Web Mapping Engineering Report + Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers. + 02-087r3 + + 2002-12-13 + + + + + 18-066r1 + + 2021-02-04 + + This document provides the set of revision notes for the existing GeoPackage version 1.3.0 (OGC 12-128r17) and does not modify that standard. + +This document was approved by the OGC membership on 2020-11-26. As a result of the OGC Standards Working Group (SWG) process, there were a number of edits and enhancements made to this standard. This document provides the details of those edits, deficiency corrections, and enhancements. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility. + + Release Notes for OGC GeoPackage Encoding Standard v1.3.0 + - - 12-160r1 + 18-066r1 + Release Notes for OGC GeoPackage Encoding Standard v1.3.0 + + Jeff Yutzler + + + 2009-07-29 + OWS-6 Georeferencable Imagery Engineering Report + This document discusses considerations about and recommendations for approaches for georeferenceable imagery under the Sensor Web Enablement thread during OGC Web Services Phase 6. This is an extension to the work described in the previous engineering report number OGC 08-071 . Georeferencealbe imagery is “a referenceable grid that has information that can be used to transform grid coordinates to external coordinates, but the transformation shall not be required to be an affine transformation”. Geolocation of georeferenceable imagery refers to the techniques described in ISO 19130, such as sensor models, functional fit models, and spatial registration using control points. + 09-034 + OWS-6 Georeferencable Imagery Engineering Report - 2013-06-18 - Jon Blower, Xiaoyu Yang, Joan Masó and Simon Thum + + Genong (Eugene) Yu, Liping Di + + + + 09-034 - - Feature Styling IPR - 06-140 - Dr. Markus M - Feature Styling is based on a distributed computational platform that employs a number -of standard interfaces and encodings to allow for flexible, scalable and interoperable -management of symbology (styles and symbols) in the process of producing maps from -different kinds of data, most important being source GML data. - - - - - Feature Styling IPR + + - 06-140 - 2007-06-08 - + Volume 3: OGC CDB Terms and Definitions + + This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice. + 15-112r2 + Carl Reed + 2017-02-23 + 15-112r2 + Volume 3: OGC CDB Terms and Definitions + + - - 16-009r5 - Volume 6: OGC CDB Rules for Encoding Data using OpenFlight - This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of that document for a general overview. + - Volume 6: OGC CDB Rules for Encoding Data using OpenFlight - 2021-02-26 - - - - 16-009r5 + + 3D Data Container and Tiles API Pilot Summary Engineering Report + 20-031 + 2020-10-22 + 20-031 + + Tim Miller, Gil Trenum, Ingo Simonis + - Carl Reed - + This Engineering Report summarizes the purpose and key results of the 3D Data Container and Tiles API Pilot, an OGC Innovation Program initiative conducted between October 2019 and July 2020. In the context of both existing and emerging 3D and 2D standards, the focus of the Pilot was on the exchange and visualization of 3D data using open standards. + 3D Data Container and Tiles API Pilot Summary Engineering Report + - - + + + This document specifies an extension to the OGC Web Coverage Service (WCS) 2.0 core to allow for client/server communication using HTTP GET with key/value pair (KVP) encod-ing. + 09-147r3 + Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - Corrigendum + + Peter Baumann + - Carl Reed - 16-004r3 - (RCS) data within a conformant CDB data store. -Please note that the current CDB standard only provides encoding rules for using Esri ShapeFiles for storing RCS models. However, this Best Practice has been modified to change most of the ShapeFile references to “vector data sets” or “vector attributes” and “Point Shapes” to “Point geometries”. This was done in recognition that future versions of the CDB standard and related Best Practices will provide guidance on using other encodings/formats, such as OGC GML. - - 16-004r3 - Volume 5: OGC CDB Radar Cross Section (RCS) Models - Volume 5: OGC CDB Radar Cross Section (RCS) Models + 09-147r3 + OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - Corrigendum - 2017-02-23 - - - + + 2013-03-26 - + + + Simon Jirka, Arne Bröring - Anchor Node Extension in IndoorGML - Seamless Navigation between Indoor and Outdoor Space - - 2019-12-11 + This Discussion paper introduces the Sensor Observable Registry (SOR), a web service interface for managing the definitions of phenomena measured by sensors as well as exploring semantic relationships between these phenomena. + 09-112 + + Sensor Observable Registry Discussion Paper + + 09-112 + Sensor Observable Registry Discussion Paper + + 2009-10-13 + + - Anchor Node Extension in IndoorGML - Seamless Navigation between Indoor and Outdoor Space - 19-004 - This OGC discussion paper provides an extension module of OGC Indoor Geography Markup Language (IndoorGML) for the seamless navigation between indoor and outdoor spaces. The OGC IndoorGML standard has an issue on the data model that affects the connection of indoor and outdoor spaces via an “Anchor Node,” which is a conceptual part for connecting indoor and outdoor spaces. This discussion paper aims to show use cases of how IndoorGML can connect with other geospatial standards that represent outdoor spaces (and road networks), such as OGC City Geography Markup Language (CityGML) and version 5.0 of the Geographic Data Files (GDF) format. + + Citizen Science Interoperability Experiment Engineering Report + 19-083 + - Kyoung-Sook Kim, Jiyeong Lee - 19-004 - + OGC Citizen Science Interoperability Experiment Engineering Report + 2020-02-13 + 19-083 + + This Engineering report describes the first phase of the Citizen Science (CS) Interoperability Experiment (IE) organized by the EU H2020 WeObserve project under the OGC Innovation Program and supported by the four H2020 Citizen Observatories projects (SCENT, GROW, LandSense, and GroundTruth 2.0) as well as the EU H2020 NEXTGEOSS project. The activity covered aspects of data sharing architectures for Citizen Science data, data quality, data definitions and user authentication. + +The final aim was to propose solutions on how Citizen Science data could be integrated in the Global Earth Observation System of Systems (GEOSS). The solution is necessarily a combination of technical and networking components, being the first ones the focus of this work. The applications of international geospatial standards in current Citizen Science and citizen observatory projects to improve interoperability and foster innovation is one of the main tasks in the IE. + +The main result of the activity was to demonstrate that Sensor Observing Services can be used for Citizen Science data (as proposed in the Open Geospatial Consortium (OGC) Sensor Web Enablement for Citizen Science (SWE4CS) Discussion Paper) by implementing SWE4CS in several clients and servers that have been combined to show Citizen Science observations. In addition, an authentication server was used to create a federation between three projects. This federated approach is part of the proposed solution for GEOSS that can be found in the last chapter. Many open issues have been identified and are expected to be addressed in the second phase of the experiment, including the use of a definitions server. + + Joan Masó - - - Web Processing Service Best Practices Discussion Paper - 12-029 - - 12-029 - Bastian Schäffer + + Lewis Leinenweber + + 2009-09-11 + + + 09-063 + + OWS-6 GeoProcessing Workflow Thread Summary ER + 09-063 + OWS-6 GeoProcessing Workflow Thread Summary ER + This OGC® document summarizes work completed in the GeoProcessing Workflow thread of the OWS-6 Testbed, it is applicable to the OGC Interoperability Program testbed. + + + + + The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community +(IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0 +architecture through the development, implementations, test, and robust demonstration +making use of IC specifications, Geography Markup Language (GML), and NIEM in a +simulated “real-world” scenario. The demonstration scenario begins with NIEMconformant +Information Exchange Packages (IEPs) containing operational data and IC +security tags from the Information Security Marking (ISM) and Need-To-Know (NTK) +access control metadata, and the Trusted Data Format (TDF) for binding assertion +metadata with data resource(s). Those instance documents are deployed on Open +Geospatial Consortium (OGC) Web Services to be used by client applications. Access +control is based on attributes of the end-user and the instance data. +Recommendations to update these information exchanges were provided to reflect NIEM +3.0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment +exercised this data encoding in OGC Web Feature Services (WFS) and Policy +Enforcement Points (PEP) accessed by multiple client applications. Results from this task +provided a preliminary architecture that was tested and demonstrated in Testbed 11, and +summarized in other OGC Testbed 11 Engineering Reports. + 15-048r3 + Testbed-11 NIEM & IC Data Encoding Specification Assessment and Recommendations Engineering Report + + + 2016-01-25 + Jeff Harrison - Web Processing Service Best Practices Discussion Paper - The following document contains best practices for identifying input data formats for the OGC WPS 1.0.0. It was created due to a lack of interoperability between different WPS implementation based on non-standardized input identifiers. - 2012-04-04 - + 15-048r3 + + + OGC Testbed-11 NIEM & IC Data Encoding Specification Assessment and Recommendations Engineering Report - + + 17-046 + Testbed-13: 3D Tiles and I3S Interoperability and Performance Engineering Report + + 2018-03-05 + + + Volker Coors + This OGC Testbed 13 Engineering Report (ER) documents the overall architecture developed in the Interoperability of 3D Tiles and I3S using a 3D Portrayal Service and performance study of 3D tiling algorithms activity. The report also summarizes a proof-of-concept of the use of 3D Tiles and I3S as data delivery formats for the OGC 3D Portrayal Service interface standard. The report captures the results from the interoperability tests performed as part of the 3D Tiles and I3S testbed work package. Specifically, this OGC Testbed activity focused on the following tasks: + +CityGML files converted into Cesium 3D Tiles using Analytical Graphics (AGI’s) 3D Tiling Pipeline, and Cesium as the rendering client; + +An OGC CDB data store converted into 3D Tiles using Compusult’s Streaming engine, Cesium and Ecere’s GNOSIS as rendering client; + +CityGML data store GeoRocket, 3DPS with 3D Tiles as data delivery format, and Cesium as rendering client; + +CityGML converted into I3S, 3DPS with I3S as data delivery format, and Cesium as rendering client; + +CityGML converted into I3S using ArcGIS and FME, 3DPS with I3S as data delivery format, and rendering in ArcGIS client; + +CityGML with application domain extension stored in GeoRocket, converted to 3D Tiles, and Cesium as the rendering client; + +3D Tiles (generated by all streaming engines visualized) from Ecere’s GNOSIS rendering client; + +CDB visualized directly from Ecere’s GNOSIS rendering client; and + +I3S visualized from Ecere’s GNOSIS rendering client. + + + 17-046 + + + OGC Testbed-13: 3D Tiles and I3S Interoperability and Performance Engineering Report + + + 17-020r1 + Johannes Echterhoff, Clemens Portele + 17-020r1 + Testbed-13: NAS Profiling Engineering Report + 2018-01-26 + + + OGC Testbed-13: NAS Profiling Engineering Report + The National System for Geospatial-Intelligence (NSG) Application Schema (NAS) is an ISO 19109 compliant application schema that defines the conceptual model for identifying and encoding feature data in the U.S. National System for Geospatial-Intelligence (NSG). NGA utilizes the open source software tool ShapeChange as an integral piece in NAS development. This tool is used to take NAS-based UML models and create Extensible Markup Language (XML) and Resource Description Framework (RDF) based schemas. Testbed-12 began development of capabilities for extracting profiles supporting specific mission functions from the full NAS content. Testbed-13 further refined the approach to NAS Profiling by investigating how a specific profile (Urban Military Profile) can be processed in an automated way and used to derive implementation schemas for the OGC standards CDB and CityGML. + +This OGC Engineering Report describes: + +The specification of a NAS-based Military Urban Profile as a Unified Modeling Language (UML) model (chapter 5); + +How mission-specific sub-profiles can be specified and maintained using ShapeChange and the new ShapeChange Profile Management Tool (chapter 6); and + +How the model and profile information are processed to derive output for + +a CDB data store (chapter 7, chapter 8) and + +a CityGML Application Domain Extension (chapter 9). + +This work provides insights into: + +The requirements and constraints on managing profiles of complex ISO 19109 compliant application schemas such as the NAS; and + +Using a model-driven approach to generate implementation schemas of an ISO 19109 compliant application schema profile for different environments. + +The target audience of this document is anyone interested in these topics. The implementation environments discussed in this report are the OGC standards CDB and CityGML. The profiled application schema is the NAS. + +This report assumes that readers are familiar with the key concepts and technologies discussed in this document. This document does not provide an introduction to them, but the table below provides a brief summary and pointers to more information. - EO Product Collection, Service and Sensor Discovery using the CS-W ebRIM Catalogue - 11-035r1 - Frédéric Houbie, Steven Smolders - + - - - 11-035r1 - 2013-03-26 - EO Product Collection, Service and Sensor Discovery using the CS-W ebRIM Catalogue - This is an OGC Best Practice document describing the relations that exist between several metadata conceptual models (EO Product, EO Product Collections, Sensors and Services). The specification of the linking between different artifacts is important for the process of cataloguing and discovering those artifacts. + - - 2007-10-05 - Reference Model for the ORCHESTRA Architecture - 07-097 - This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It is an extension of the OGC Reference Model and contains a specification framework for the design of geospatial service-oriented architectures and service networks. The RM-OA comprises the generic aspects of service-oriented architectures, i.e., those aspects that are independent of the risk management domain and thus applicable to other application domains. + + 21-007 + Defence Geospatial Information Working Group (DGIWG) GMLJP2/JP2 Profile for Imagery & Gridded Data 2.1.2 + + 2021-11-16 + DGIWG + Defence Geospatial Information Working Group (DGIWG) GMLJP2/JP2 Profile for Imagery & Gridded Data 2.1.2 - 07-097 + + 21-007 - - - - Thomas Uslander (Ed.) - Reference Model for the ORCHESTRA Architecture + + This document provides a profile for JPEG 2000 for use as a +compression format for raster imagery. JPEG 2000 uses +discrete wavelet transform (DWT) for compressing raster data, +as opposed to the JPEG standard, which uses discrete cosine +transform (DCT). It is a compression technology which is best +suited for continuous raster data, such as satellite imagery and +aerial photography. This version adds support for +Referenceable imagery. - - 22-020r1 - Paul Churchyard, Ajay Gupta - 22-020r1 - Testbed-18: Identifiers for Reproducible Science Summary Engineering Report + + 12-077r1 + A Primer for Dissemination Services for Wide Area Motion Imagery + 12-077r1 + 2012-12-05 + - Testbed-18: Identifiers for Reproducible Science Summary Engineering Report + Rahul Thakkar + + + A Primer for Dissemination Services for Wide Area Motion Imagery + + The reason for developing this specification was a WAMI community requirement to deliver high performance web services and disseminate WAMI products. While existing web services can be combined or modified to deliver some of the functionality of the services described in this document, by design, they cannot deliver the desired performance. + + + + Mike Botts, Alexandre Robin, Eric Hirschorn + + - 2023-03-13 - - The OGC’s Testbed 18 initiative explored the following six tasks. - -1.) Advanced Interoperability for Building Energy -2.) Secure Asynchronous Catalogs -3.) Identifiers for Reproducible Science -4.) Moving Features and Sensor Integration -5.) 3D+ Data Standards and Streaming -6.) Machine Learning Training Data -Testbed 18 Task 3, Identifiers for Reproducible Science, explored and developed workflows demonstrating best practices at the intersection of Findable, Accessible, Interoperable, and Reusable (or FAIR) data and reproducible science. + 12-000r2 + SensorML: Model and XML Encoding Standard + The primary focus of the Sensor Model Language (SensorML) is to provide a robust and semantically-tied means of defining processes and processing components associated with the measurement and post-measurement transformation of observations. This includes sensors and actuators as well as computational processes applied pre- and post-measurement. -The workflows developed in this Testbed included: +The main objective is to enable interoperability, first at the syntactic level and later at the semantic level (by using ontologies and semantic mediation), so that sensors and processes can be better understood by machines, utilized automatically in complex workflows, and easily shared between intelligent sensor web nodes. -the development of a Whole Tail workflow for land cover classification (52 Degrees North); -the development of a reproducible workflow for a deep learning application for target detection (Arizona State University); -the implementation of reproducible workflows following the approach described in the OGC API Process Part 3: Workflows and Chaining for Modular OGC API Workflows (Ecere); -the development of a reproducible workflow that runs an OGC API — Process and Feature Server instance within a Whole Tale environment (GeoLabs); and -the development of a water body detection Application Package to cover the identifier assignment and reproducibility from code to several execution scenarios (local, Exploitation Platform, Whole Tale) (Terradue). -Testbed 18 participants identified considerations and limitations for reproducible workflows and recommendations for future work to identify the benefits of reproducible science for healthcare use cases. - - - - - - 09-001 - SWE Service Model Implementation Standard +This standard is one of several implementation standards produced under OGC’s Sensor Web Enablement (SWE) activity. This standard is a revision of content that was previously integrated in the SensorML version 1.0 standard (OGC 07-000). + 2020-08-10 + OGC SensorML: Model and XML Encoding Standard + 12-000r2 - - - - Johannes Echterhoff - 2011-03-21 - This standard currently defines eight packages with data types for common use across OGC Sensor Web Enablement (SWE) services. Five of these packages define operation request and response types. The packages are: 1.) Contents – Defines data types that can be used in specific services that provide (access to) sensors; 2.) Notification – Defines the data types that support provision of metadata about the notification capabilities of a service as well as the definition and encoding of SWES events; 3.) Common - Defines data types common to other packages; 4.) Common Codes –Defines commonly used lists of codes with special semantics; 5.) DescribeSensor – Defines the request and response types of an operation used to retrieve metadata about a given sensor; 6.) UpdateSensorDescription –Defines the request and response types of an operation used to modify the description of a given sensor; 7.) InsertSensor – Defines the request and response types of an operation used to insert a new sensor instance at a service; 8.) DeleteSensor – Defines the request and response types of an operation used to remove a sensor from a service. These packages use data types specified in other standards. Those data types are normatively referenced herein, instead of being repeated in this standard. - OpenGIS® SWE Service Model Implementation Standard - 09-001 - + - - 02-069 - Geography Markup Language - - + + 09-147r1 - + OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension + 2010-10-27 + 09-147r1 + Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension + + This document specifies how Web Coverage Service (WCS) clients and servers can communicate over the Internet using HTTP GET with key/value pair (KVP) encoding. + Peter Baumann - Geography Markup Language - The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features. - - Ron Lake - 02-069 - 2002-08-19 - - - - 11-111r1 - 11-111r1 - Topic 11 - Metadata - Topic 11 - Metadata - Same as ISO 19115-1:2014. Abstract Specification Topic 11 was updated to the latest version of the ISO metadata standard on 21 September 2016. Prior to this date, this Topic was the same as ISO 19115:2003. Please note that many OGC standards and other related work normatively refer to the previous version of this Topic. - - - - 2016-09-16 + - ISO - + + 16-011r3 + + + 2017-02-23 - Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames. -In previous versions of the CDB standard, this CDB volume was Appendix K in CDB Version 3.2 as submitted to the OGC. - Volume 8: CDB Spatial and Coordinate Reference Systems Guidance - - Carl Reed - - 16-011r3 Volume 8: CDB Spatial and Coordinate Reference Systems Guidance + + Carl Reed + Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames. +In previous versions of the CDB standard, this CDB volume was Appendix K in CDB Version 3.2 as submitted to the OGC. + - 2017-02-23 - - 16-011r3 + - + - 2020-02-12 - - OGC Testbed-15: Federated Cloud Provenance ER - The emergence of Federated Cloud processing and ‘Big Data’ have raised many concerns over the use to which data is being put. This led to new requirements for methodologies, and capabilities which can address transparency and trust in data provenance in the Cloud. Distributed Ledger Technologies (DLTs) and more specifically blockchains, have been proposed as a possible platform to address provenance. This OGC Testbed 15 Engineering Report (ER) is a study of the application of DLTs for managing provenance information in Federated Clouds. - - 19-015 - OGC Testbed-15: Federated Cloud Provenance ER - 19-015 - - - Stephane Fellah - - - - - 02-102 - 2002-03-08 + 2018-02-22 + 17-041 - Topic 2 - Spatial Referencing by Coordinates + This Open Geospatial Consortium (OGC) Engineering Report (ER) captures the requirements, solutions, and implementation experiences of the Vector Tiling work package in OGC Testbed-13 [Available at: http://www.opengeospatial.org/projects/initiatives/testbed13]. This ER describes the evaluation of existing vector tiling solutions. The evaluation was used to define a conceptual model that integrates elements from different approaches to vector tiling. This is followed by an overview of how the developed implementation integrates vector tiles containing World Geodetic System 1984 (WGS84), European Terrestrial Reference System 1989 (ETRS89) and British National Grid projection data, standards based tile schemas and moving features. Best practice guidelines for the use of Symbology Encoding (SE) and Styled Layer Descriptor (SLD) are also provided ensuring the service is optimized for analysis and low-bandwidth networks. The report concludes with an investigation on how existing OGC services may be extended with the necessary capabilities enabling the full range of geometry types and tiling strategies to support vector tiling. - Topic 02 - Spatial Referencing by Coordinates - 02-102 - Roel Nicolai - Describes modelling requirements for spatial referencing by coordinates. This document supplements and corrects ISO 19111. There has never been a motion to adopt 01-063r2. A motion was approved at the Dec 01 meeting in Vancouver to adopt 01-063r1 - + + 17-041 + Testbed-13: Vector Tiles Engineering Report + Stefano Cavazzi + OGC Testbed-13: Vector Tiles Engineering Report - - + + Unified Geo-data Reference Model for Law Enforcement and Public Safety + 14-106 + Unified Geo-data Reference Model for Law Enforcement and Public Safety + - Louis Rose - 2003-06-02 - Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint - *RETIRED* specifies the Engineering Viewpoint for the Critical Infrastructure Collaborative Environment (CICE). This open, distributed processing environment crosses organizational boundaries and includes a variety of components deployed within multiple communities. The CICE leverages OGC Web Services the publication of the availability of critical infrastructure services and data; the registration and categorization of published service and data providers; and the discovery and use of needed critical infrastructure services and data - 03-055r1 - Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint - 03-055r1 - - - - - - + This document provides an overview of the Unified Geo-data Reference Model for Law Enforcement and Public Safety (Unified Model). The Unified Model was originally developed by the GIS Center for Security (GIS CS), Abu Dhabi Police. The GIS CS was initiated based on a UAE Ministry of Interior issued decree to establish GIS CS with the core mission: “To geo-enable police services and applications using International standards and best practices.” In 2010, the GIS SC initiated a program to develop a Standardized GIS Environment (SGA). Part of this effort was to define and implement a standard data model for sharing Law Enforcement and Public Safety data. + - WMS - Proposed Animation Service Extension + 14-106 + 2015-01-30 + + Carl Reed, Jennifer Harne - Eric LaMar - 06-045r1 - WMS - Proposed Animation Service Extension - - 06-045r1 - - - - 2006-07-27 - This document explains how the Web Map Server (WMS 1.0 [1] & 1.1 [2,3]) specification can be extended to allow map animations that move in space over time. It should be read in conjunction with the latest version WMS specification. - + + OGC Testbed-14: WPS-T Engineering Report + WPS-T Engineering Report + 18-036r1 + 2019-02-07 + This Engineering Report describes a proposed transactional extension for the OGC Web Processing Service (WPS) 2.0 standard including Key-Value Pair (KVP) and Extensible Markup Language (XML) bindings and recommendations for a process deployment profile for BPMN (Business Process Model and Notation). + + + 18-036r1 - - - Micah Brachman - 16-094r3 - GeoPackage Elevation Extension Interoperability Experiment Engineering Report - 16-094r3 - his OGC Engineering Report (ER) describes the setup, experiments, results and issues generated by the GeoPackage Elevation Extension Interoperability Experiment (GPKG-EE IE). The goal of the GPKG-EE IE was to implement and test a proposed elevation extension to the OGC GeoPackage Encoding Standard (12-128r1). The proposed elevation extension was successfully implemented by several IE participants and was demonstrated using both 2-Dimensional (2D) and 3-Dimensional (3D) software clients at the Washington, DC OGC Technical Committee (TC) meeting in [March 9, 2016]. This ER concludes with several recommendations for addressing remaining technical issues that must be resolved in order to complete a candidate GeoPackage Elevation Extension standard. - OGC GeoPackage Elevation Extension Interoperability Experiment Engineering Report - 2017-08-18 + + + Benjamin Pross, Arnaud Cauchy + + + Web Coverage Processing Service + Web Coverage Processing Service (WCPS) + The Web Coverage Processing Service (WCPS) supports retrieval and processing of geo-spatial coverage data. WCPS grounds on the coverage model of the OGC Web Coverage Service (WCS) Implementation Specification where coverages are defined as digital geospatial information representing space-varying phenomena, currently constrained to equally spaced grids. + The Web Coverage Processing Service (WCPS) supports retrieval and processing of geo-spatial coverage data. WCPS uses the coverage model of the OGC Web Coverage Service (WCS) Implementation Specification: coverages are defined as digital geo-spatial information representing space-varying phenomena, currently constrained to equally spaced grids. + 2006-05-02 + 2006-07-26 + + + + Web Coverage Processing Service + Web Coverage Processing Service (WCPS) + 06-035r1 + + + + 06-035r1 + + + Peter Baumann + + + + + CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211. + +The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. + + Gerhard Gröger, Thomas H. Kolbe, Angela Czerwinski, Claus Nagel + 08-007r1 + City Geography Markup Language (CityGML) Encoding Standard + 2008-08-20 + OpenGIS® City Geography Markup Language (CityGML) Encoding Standard + 08-007r1 + + + - - 09-031r1 - 09-031r1 - OWS-6 SWE Information Model Engineering Report + + Testbed-18: Key Management Service Engineering Report - + Andreas Matheus - This OGC® document is an OGC Engineering Report for the “Harmonization of SWE Information Models” activity within the OWS-6 SWE thread. -The document discusses relations between OGC standards SensorML, SWE Common and GML and investigates solutions for increased synergy between these standards. This activity also created UML models of the data types used in SWE and GML. -This report shows how UncertML can be integrated into different SWE encodings, namely SWE Common and Observations and Measurements. -This report further discusses the integration of MathML and EML into the SWE environment with an emphasis on SensorML processes and processing. -This document does not discuss the SWE information model related aspects of catalog entries for sensor services and discovery. This topic is covered in a separate Engineering Report. - - Thomas Everding + + 22-014 + Testbed-18: Key Management Service Engineering Report + 22-014 + 2023-01-05 - - 2009-07-16 - OWS-6 SWE Information Model Engineering Report + + This OGC Testbed 18 Engineering Report describes the Data Model and API of a Key Management Service (KMS) that supports the flexible but secure exchange of cryptographic keys for applying confidentiality and integrity protection to geographic information. The described KMS is based on the design and implementation from previous OGC Testbeds 16 and 17. - - Serge Margoulies - - - + + OGC Vector Tiles Pilot: Tiled Feature Data Conceptual Model Engineering Report + Feature data tiling, colloquially referred to as 'vector tiling', is a method that defines how large vector geospatial datasets can be systematically split into subsets or tiles [1]. Feature data tiling allows for a variety of use-cases, such as creating online maps, quickly accessing large vector data sets for geoprocessing and creating download-services. For instance, a map created from tiled feature data consists of one or more layers of vector data organized into tiles of features and rendered on the client-side using an associated style. In contrast, raster tiles are delivered as tiled images that have been rendered on the server-side. + +NOTE +This engineering report interchangeably uses both 'tiled feature data' and the colloquial term 'vector tiles'. + + + 18-076 + 2019-02-11 - Geocoder - 2001-03-28 - *RETIRED* Geocoding is the process of linking words, terms and codes found in a text string to their applicable geospatial features, with known locations. (Locations are defined as geometry; usually points with x, y coordinates.) - 01-026r1 - Geocoder + 18-076 + Tiled Feature Data Conceptual Model Engineering Report - 01-026r1 + Jens Ingensand, Kalimar Maia + - - The scope of this guidelines report is to provide: -1. Overview of the OGC WFS 2.0 standard -2. Recommendations for a minimum set of operations and behaviours that should be supported to ensure consistency across software implementations. -3. Guidance for configuring the WFS 2.0 to retrieve AIXM 5.1 data -4. Summary of potential improvements to WFS/FE 2.0, GML and AIXM 5.1 specifications to better support aeronautical use cases - + + 12-100r1 + GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile + + - 11-073r2 - - + + This Interface Standard is a profile of the OGC® GML Application Schema –Coverages version 1.0 [OC 09-146r2]. This document specifies the usage of the GeoTIFF data format for the encoding of GML coverages. This encoding is used by several OGC services like the Web Coverage Service (WCS) 2.0 Interface Standard – Core [OGC 09-110r4]. + + OGC® GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile + 12-100r1 + 2014-05-28 + Stephan Meissl + + + OWS-6 SWE Event Architecture Engineering Report + 09-032 + The document describes an abstract event architecture for service oriented architectures. Furthermore various techniques for implementing an event architecture and working with events are discussed. + + Thomas Everding, Johannes Echterhoff + + 2009-07-29 + - 11-073r2 - OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0 - OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0 - 2012-02-09 - Debbie Wilson, Ian Painter + 09-032 + + OWS-6 SWE Event Architecture Engineering Report - - - - - - + + + Arliss Whiteside + Grid coverage Coordinate Reference Systems (CRSs) + + This document summarizes the types of Coordinate Reference Systems (CRSs) that are recommended for use with grid (including image) coverages. This document specializes Best Practice Paper OGC 09-076r3 “Uses and Summary of Topic 2: Spatial referencing by coordinates” for grid coverages. Topic 2 is almost the same as ISO 19111:2007, but includes some corrections. This document includes some best practices for defining and using ImageCRSs and other CRSs for grid coverages. + 09-085r2 + + + + Grid coverage Coordinate Reference Systems (CRSs) + 09-085r2 + 2009-10-13 + - - Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside + + Pedro Gonçalves + + OpenSearch Geo and Time Extensions + 10-032r8 - 02-023r4 + 10-032r8 + + 2014-04-14 + + OGC® OpenSearch Geo and Time Extensions + + <p>This OGC standard specifies the Geo and Time extensions to the OpenSearch query protocol. OpenSearch is a collection of simple formats for the sharing of search results.</p> +<p>The OpenSearch description document format can be used to describe a search engine so that it can be used by search client applications. The OpenSearch description format allows the use of extensions that allow search engines to request a specific and contextual query parameter from search clients.</p> +<p>The OpenSearch response elements can be used to extend existing syndication formats, such as RSS and Atom, with the extra metadata needed to return search results. +Services that support the OpenSearch Specification, the Geo and Time extensions defined in this document are called OpenSearch GeoTemporal Services.</p> + - - - - - Geography Markup Language (GML) Encoding Specification - 02-023r4 - OpenGIS Geography Markup Language (GML) Encoding Specification - 2003-01-29 - The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features. - - OpenGIS Web Feature Service (WFS) Implementation Specification - Web Feature Service (WFS) Implementation Specification - 04-094 - Peter Vretanos - The OpenGIS Web Feature Service Interface Standard (WFS) defines an interface[http://www.opengeospatial.org/ogc/glossary/i] for specifying requests for retrieving geographic features [http://www.opengeospatial.org/ogc/glossary/g] across the Web using platform-independent calls. The WFS standard defines interfaces and operations for data access and manipulation on a set of geographic features, including: -• Get or Query features based on spatial and non-spatial constraints -• Create a new feature instance -• Get a description of the properties of features -• Delete a feature instance -• Update a feature instance -• Lock a feature instance + + OGC Testbed-14: Symbology Engineering Report + 2019-03-15 + 18-029 + Symbology Engineering Report + The portrayal and visualization of geospatial information is a critical task for facilitating decision making, situational awareness, and spatial analysis. However, despite its importance, various local, national, and international agencies continue to use different symbols and terminology for the same event, feature, or entity. This approach prevents interoperability from being extended to the semantic level, which in turn makes it difficult to share, reuse, and mediate unambiguous portrayal information between agencies. -The specified feature encoding for input and output is the Geography Markup Language (GML) [http://www.opengeospatial.org/standards/gml] although other encodings may be used. - - 04-094 - - 2005-05-03 - - +This Engineering Report (ER) captures the requirements, solutions, models, and implementations of the Open Geospatial Consortium (OGC) Testbed-14 Portrayal thread. This effort leverages the work of the Portrayal Ontology development and the Semantic Portrayal Service conducted during Testbed 10, 11, 12 and 13. Thus far the emphasis for developing the portrayal ontologies (Testbeds 12 and 13) has been on modeling and representing portrayal information for feature data. The objective of Testbed-14 is to extend the portrayal ontology to accommodate more complex symbols (e.g., composite symbols) and to provide clear recommendations on how to best proceed with portrayal information encodings. + + + 18-029 + - - - - Topic 2 - Referencing by coordinates + Sara Saeedi + + + 2024-02-06 + Release Notes for OGC GeoPackage 1.4.0 + 23-018r1 + Jeff Yutzler + This document provides the set of revision notes for OGC® GeoPackage Encoding Standard, version 1.4.0 [OGC 12-128r19] and does not modify that Standard. + +This document provides the details of edits, deficiency corrections, and enhancements of the above-referenced Standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility. + 23-018r1 + + + - 18-005r4 - 18-005r4 - Topic 02 - Referencing by coordinates - + + Release Notes for OGC GeoPackage 1.4.0 - This document is identical in normative content with the latest edition (2019) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2019]. - - - 2019-02-08 - Roger Lott - - - Feature Type Catalogue Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 - - 2008-05-13 - - Feature Type Catalogue Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 - 07-172r1 - This document describes a Feature Type Catalogue extension package for the OGC® ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 [OGC 05-025r3]. It defines the way an ISO 19110 [ISO 19110:2005] Feature Type Catalogue is included within a Registry, and provides an information model and stored queries for such an inclusion. - 07-172r1 - Kristin Stock + + 2014-02-25 + 13-015 + + This document comprises experiences and recommendations when using +Sensor Web Enablement (SWE) concepts. This document focuses on +one basic issue: the provision of observations in an OGC SOS. +This includes the definition of a lightweight OGC SOS profile (OGC 11- +169r1), an analysis of and contribution to the specification of the Sensor +Observation Service (SOS) 2.0 as well as an approach how the data +used within Earth observation (EO) applications can be integrated more +easily into SOS instances. +These recommendations result from the work performed in 2010-2013 +as part of the research project EO2HEAVEN (Earth Observation and +Environmental Modelling for the Mitigation of Health Risks), co-funded +by the European Commission as part of the 7th Framework Programme +(FP7) Environmental theme. EO2HEAVEN contributes to a better understanding +of the complex relationships between environmental changes +and their impact on human health. See http://www.eo2heaven.org/ . +The lightweight OGC SOS profile has been developed in close cooperation +between the FP7 projects EO2HEAVEN and UncertWeb (see +http://www.uncertweb.org/ ). + 13-015 + Provision of Observations through an OGC Sensor Observation Service (SOS) + + + + + EO2HEAVEN Consortium + OGC Best Practice for Sensor Web Enablement: Provision of Observations through an OGC Sensor Observation Service (SOS) + + + + + + + 16-131r2 + 16-131r2 + Big Geospatial Data – an OGC White Paper + + Big Geospatial Data – an OGC White Paper + 2017-09-25 + This white paper is a survey of Big Geospatial Data with these main themes: + + Geospatial data is increasing in volume and variety; + New Big Data computing techniques are being applied to geospatial data; + Geospatial Big Data techniques benefit many applications; and + Open standards are needed for interoperability, efficiency, innovation and cost effectiveness. + + +The main purpose of this White Paper is to identify activities to be undertaken in OGC Programs that advance the Big Data capabilities as applied to geospatial information. + +This white paper was developed based on two Location Powers events: + + Location Powers: Big Data, Orlando, September 20th, 2016; and + Location Powers: Big Linked Data, Delft, March 22nd, 2017. +For information on Location Powers: http://www.locationpowers.net/pastevents/ + George Percivall + + + 2016-01-25 + Scott Serich + + + 15-030r3 + + + 15-030r3 + Testbed 11 Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Round Trip Engineering Report + Testbed 11 Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Round Trip Engineering Report + + The goal of the Geo4NIEM thread in OGC Testbed 11 was to gain Intelligence Community (IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0 architecture through the development, implementations, test, and robust demonstration making use of IC specifications, Geography Markup Language (GML), and NIEM in a simulated “real-world” scenario. The demonstration scenario begins with NIEM-conformant Information Exchange Packages (IEPs) containing operational data and IC security tags from the Information Security Marking (ISM) and Need-To-Know (NTK) access control metadata, and the Trusted Data Format (TDF) for binding assertion metadata with data resource(s). Those instance documents are deployed using Open Geospatial Consortium (OGC) enabled Web Services for access by client applications. Access control is based on attributes of the end-user and the instance data +Recommendations to update these information exchanges were provided to reflect NIEM 3.0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment exercised this data encoding in OGC Web Feature Services (WFS) and Policy Enforcement Points (PEP) accessed by multiple client applications. The round-trip assessment also exercised the OGC Transactional Web Feature Services (WFS-T). Results from this task provided a preliminary architecture that was tested and demonstrated in Testbed 11, and summarized in other OGC Testbed 11 Engineering Reports. + - - + - 15-075r1 - A Use-Case for Mobile Location Services with IndoorGML - Indoor Navigation for Visually Impaired People + + 06-022r1 + Temporal Standard Recommendations + 06-022r1 - - 2015-11-19 - A Use-Case for Mobile Location Services with IndoorGML - Indoor Navigation for Visually Impaired People - Ki-Joune Li, Hyung-Gyu Ryu, Taehoon Kim, and Hack-Cheol Kim - This OGC Discussion Paper provides a navigation use-case for the use of IndoorGML for mobile location services (MLS). In particular, the Discussion Paper explains how the OGC IndoorGML standard can be applied to a MLS application for visually impaired people in indoor space. Finally, a prototype development of the application on Android smart phone is described in this report. + James Resler - 15-075r1 + This document summarizes recommendations for extending geospatial standards with regard to time-varying information. These proposals are the result of the National Technology Alliance program called Temporal Evaluation and Assessment (TEA). + 2006-04-21 + Temporal Standard Recommendations + - - - 23-047 - OGC Testbed-19 GeoDataCubes Engineering Report + + Gobe Hobona, Simon Cox + + + The mission of the OGC Naming Authority (OGC-NA) is to provide the means through which OGC resources such as OGC documents, namespaces and ontologies can be controlled and managed such that they can provide clear and well-defined names and definitions. In the terminology defined in ISO 19135, OGC-NA is the Control Body for the register of OGC Names. This document describes the framework of documents, registers and other resources required for OGC-NA to execute that role. + OGC Naming Authority - Procedures + 09-046r6 + OGC Naming Authority - Procedures - 23-047 - OGC Testbed-19 GeoDataCubes Engineering Report - OGC Testbed-19 has continued and furthered an ongoing discussion about how to interact with GeoDataCubes (GDC) in the most interoperable way (see Chapter 1 for more Introduction). Testbed 19 participants produced a draft OGC GDC API standard that incorporates the most relevant developments in the field in and outside of OGC. This work advanced the common understanding of available solutions while discovering to a much better degree the advantages and drawbacks of current solutions. Testbed 19 participants produced prototypes of five back-end implementations and six client implementations as well as an automated test suite, which are described in full detail in Chapter 4. Many of the researched solutions are also available as open source and hence offer a perfect starting point for further GDC activities. - -The main technologies that were evaluated in Testbed 19 included the OGC API Standards suite1, the openEO API2 and the Spatiotemporal Asset Catalog3 (STAC) specification. Based on cross walk comparisons (see Chapter 2), a unified draft GDC API was developed integrating as much as possible the existing solutions. openEO is largely compliant with the OGC API- Common Standard. As such, the openEO API specification provided the foundation for defining a draft OGC GDC API draft standard. During the Testbed 19 period, more building blocks from the OCG API were incorporated into the draft GDC API document. These building blocks included parts of OGC API — Common, OGC API — Coverages, and OGC API – Processes. There is also future potential for visualization services through maps or tiles or even including components or elements of the OGC Web Services suite of Standards, such as WMS, WMTS, WCS, etc. - -The current version of the draft GDC API, described in D71 of T19, supports different scenarios enabling implementations of the draft standard to offer only minimal support for data access with minimal manipulation of the data. Minimal manipulation is in terms of subsetting and reprojecting or including more advanced processing capabilities by incorporating building blocks from the openEO specification or from the OGC API — Processes – Part 1: Core Standard. Chapter 3 gives an overview of the draft standard. + + + 2021-09-27 + + 09-046r6 + + + 04-016r3 + OWS Common Recomendation Paper + + OWS Common Recomendation Paper + + This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses. + + + 2004-06-17 + 04-016r3 + + Arliss Whiteside + + + + Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification + 17-014r7 + 17-014r7 + 2020-02-08 + A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data.Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files. -The interaction capabilities between the different servers and clients developed are described in Chapter 5 and first impressions on usability in Chapter 6. +The delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types. -Future work could include the ability to link two processing options into one “integrated” option that supports either submitting openEO process graphs to a OGC API – Processes endpoint (extending and working on Processes — Part 3), or supports integration of an OGC API – Processes process in the process graph of openEO through an extended concept of user defined functions in openEO. Further discussion is also needed on the pros and cons of including authentication in the draft standard. More details about lessons learned and suggestions can be found in Chapters 7 and 8 of this ER. - 2024-07-22 - +The open community GitHub version of this standard is here: https://github.com/Esri/i3s-spec [2]. + + + Carl Reed, Tamrat Belayneh + + + OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification - - Alexander Jacob - - 06-021r1 - Sensor Web Enablement Architecture Document - 06-021r1 - 2006-03-27 - Mike Botts, Alex Robin, John Davidson, Ingo Simonis - + - + OGC® Sensor Web Enablement Architecture + 06-021r2 + + 06-021r2 + Sensor Web Enablement Architecture + + + Ingo Simonis + This document describes the architecture implemented by Open Geospatial Consortium’s (OGC) Sensor Web Enablement Initiative (SWE). In contrast to other OGC SWE stan-dards, this document is not an implementation standard. + 2008-07-08 - - - OpenGIS Sensor Web Enablement Architecture Document - The aim of this document is to provide a overview description of the general architecture that applies to the Sensor Web Enablement (SWE). While this document provides a synopsis of the relevant encodings and web services, it does not contain interface descriptions of the components. - - + - - Web Services Architecture + + 2019-11-25 - 03-025 - Web Services Architecture - Josh Lieberman - 03-025 - 2003-01-18 - - Specifies and discusses a common architectural framework for OGC Web Services - + Jeff Yutzler + The Open Geospatial Consortium (OGC) GeoPackage Encoding Standard was developed for the purpose of providing an open, standards-based, platform-independent, portable, self-describing, compact format for transferring geospatial information. GeoPackage has proven to be an effective container mechanism for bundling and sharing geospatial data for a variety of operational use cases. However, GeoPackage stakeholders have observed persistent interoperability issues, particularly with regards to metadata, extensions, and portrayal. + +This paper presents the operational need, proposed approach, and way ahead for addressing these interoperability issues. Section 6 presents three new enhancements (extensions) that are designed to improve the interoperability of GeoPackages in general and metadata in particular. Section 7 presents a vision for implementing an Open Portrayal Framework in GeoPackage. Annex A presents specifications for all of the GeoPackage extensions proposed in this paper. Annex B presents a JSON schema for the proposed encoding for application profiles presented in Section 6. In general, the GeoPackage Standards Working Group (SWG) looks to standardize extensions that address a clear use case, have a sound technical approach, and have a commitment to implementation by multiple organizations. As with the GeoPackage Tiled Gridded Coverage Extension and the GeoPackage Related Tables Extension, these new extensions would be tracked as separate documents from the core GeoPackage Encoding Standard. + +The GeoPackage community will benefit from the increased interoperability of operational “mission-ready” GeoPackages that will result from this approach. Additionally, software will be able to quickly determine the validity and utility of a GeoPackage in target operational environments. This will help ensure that GeoPackage production-consumption lifecycles and supporting application tools and services are better aligned with stakeholder missions. + 19-047 + Proposed OGC GeoPackage Enhancements + + + Proposed OGC GeoPackage Enhancements + 19-047 - - - - 18-056 - SensorThings API Tasking Core Discussion Paper - Steve Liang, Tania Khalafbeigi, Kan Luo - OGC SensorThings API Tasking Core Discussion Paper + + + Peter Baumann + + 2009-03-25 + 08-069r2 + + + + Web Coverage Processing Service (WCPS) Abstract Test Suite + 08-069r2 + Web Coverage Processing Service (WCPS) Abstract Test Suite + + + + - This discussion paper offers descriptions and provides JSON examples of TaskingCapabilities and Tasks for the SensorThings Application Programming Interface (API). - - 18-056 + + + 06-182r1 + Discussions, findings, and use of WPS in OWS-4 - 2018-12-18 + 2007-06-06 + 06-182r1 + + This document reviews the material discussed during the OWS-4 project, describes the WPS processes deployed in the workflows, and offers suggestions to the OGC to move forward with the WPS. + Discussions, findings, and use of WPS in OWS-4 + Steven Keens - - An important principle of a Service Oriented Architecture (SOA) is the notion of composing capabilities provided by individual services into complex behavior. A requester should be able to compose a solution using functionality or data offered by multiple services without worrying about underlying differences in those services. - -Each OGC service is designed to offer a specific type of data product via a service-specific interface. This Engineering Report (ER) describes a single service interface that allows access to multiple data sources, possibly heterogeneous with respect to the types of data provided. - -This report advances the work started in OGC Testbed 11 with the addition of heterogeneous data sources, as well as several other enhancements. - Daniel Balog, Robin Houtmeyers + + + + 2021-02-26 + This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids key words. + + Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values + Carl Reed + + Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values + 16-003r4 + 16-003r4 - 16-045r2 - - + + + Wrapping OGC HTTP-GET/POST Services with SOAP + 07-158 + 2008-01-02 + + + Wrapping OGC HTTP-GET/POST Services with SOAP + + R + + Discussion of how to wrap OGC HTTP-GET/POST Services with SOAP + + 07-158 - Testbed-12 Data Broker Engineering Report - - 2017-06-30 - Testbed-12 Data Broker Engineering Report - 16-045r2 + + 03-061 Critical Infrastructure Collaborative Environment Architecture: Enterprise Viewpoint - - 2003-05-19 - - *RETIRED* specifies the Enterprise viewpoint for the Critical Infrastructure Collaborative Environment (CICE). Geoffrey Ehler - - - 03-061 + + + Critical Infrastructure Collaborative Environment Architecture: Enterprise Viewpoint + *RETIRED* specifies the Enterprise viewpoint for the Critical Infrastructure Collaborative Environment (CICE). + 03-061 + 2003-05-19 + + + + Documents of type Discussion Paper - draft + Documents of type Discussion Paper - draft + + Documents of type Discussion Paper - draft - - This report documents the progress made to date by OGC and its members to build a complete picture of the present situation and develop a conceptual framework for action to improve underground infrastructure data interoperability. The report also identifies the most important steps to be taken next in order to develop the necessary data standards and foster their adoption. - 17-048 - - Josh Lieberman, Andy Ryan + + 2021-02-26 + Volume 0: OGC CDB Companion Primer for the CDB standard (Best Practice) + 15-120r6 + + - OGC Underground Infrastructure Concept Study Engineering Report + + 15-120r6 + The CDB standard defines a standardized model and structure for a single, “versionable,” virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. + Carl Reed + + Volume 0: OGC CDB Companion Primer for the CDB standard (Best Practice) + + + + Part 1 of this investigation is conducted by Galdos Systems. In this part, the OWS3 MSD3 geometric description is extended to include a topology encoding as defined by the MSD3 schema. Part 2 (Clause 6.2) of this investigation is conducted by Intergraph Corp. and describes and discusses the impacts of encoding topology within the GML data. + + 05-102r1 + 05-102r1 + OWS3 GML Topology Investigation + David Burggraf, Stan Tillman - + + OWS3 GML Topology Investigation - Underground Infrastructure Concept Study Engineering Report - 17-048 - - 2017-08-31 + + 2006-05-09 + + - - OGC® Web Feature Service 2.0 Interface Standard - With Corrigendum - Panagiotis (Peter) A. Vretanos + + Testbed-12 Aviation Security Engineering Report + 16-040r1 - - - 09-025r2 + 2017-06-30 - 09-025r2 - Web Feature Service 2.0 Interface Standard - With Corrigendum - 2014-07-10 - - The Web Feature Service (WFS) represents a change in the way geographic information is created, modified and exchanged on the Internet. Rather than sharing geographic information at the file level using File Transfer Protocol (FTP), for example, the WFS offers direct fine-grained access to geographic information at the feature and feature property level. - -This International Standard specifies discovery operations, query operations, locking operations, transaction operations and operations to manage stored, parameterized query expressions. - -Discovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers. - -Query operations allow features or values of feature properties to be retrieved from the underlying data store based upon constraints, defined by the client, on feature properties. - -Locking operations allow exclusive access to features for the purpose of modifying or deleting features. - -Transaction operations allow features to be created, changed, replaced and deleted from the underlying data store. - -Stored query operations allow clients to create, drop, list and described parameterized query expressions that are stored by the server and can be repeatedly invoked using different parameter values. - -This International Standard defines eleven operations: - -GetCapabilities (discovery operation) -DescribeFeatureType (discovery operation) -GetPropertyValue (query operation) -GetFeature (query operation) -GetFeatureWithLock (query & locking operation) -LockFeature (locking operation) -Transaction (transaction operation) -CreateStoredQuery (stored query operation) -DropStoredQuery (stored query operation) -ListStoredQueries (stored query operation) -DescribeStoredQueries (stored query operation) -In the taxonomy of services defined in ISO 19119, the WFS is primarily a feature access service but also includes elements of a feature type service, a coordinate conversion/transformation service and geographic format conversion service. + + Aleksandar Balaban + 16-040r1 + Testbed-12 Aviation Security Engineering Report + + + The information security is the state of being protected against the unauthorized use of information and services, or the measures taken to achieve that. This report has ben created as part of OGC Testbed 12 aviation thread and on behalf of sponsors from FAA. It gives the readers an overview into the topic of cyber security in the aviation domain, especially in conjunction with OGC compatible web services, which are today de facto standard for aeronautical traffic System Wide Information Management. - - - Testbed-12 ShapeChange Engineering Report - 16-020 + + + OGC® Coverage Implementation Schema - + + 09-146r2 - - 16-020 - Johannes Echterhoff - - This document is a deliverable of the OGC Testbed 12. It describes the results of enhancing the tool ShapeChange in the following areas of processing an ISO 19109 conformant application schema: + + + 09-146r2 + Coverage Implementation Schema + 2012-05-11 + This document specifies a GML coverage structure extending the definition of GML 3.2.1 [07-036] in a compatible way. -Creating a schema profile - to support implementations that focus on a subset of the use cases in scope of the original application schema. +Main change over GML is the addition of one mandatory component, rangeType, to the Coverage definition of GML 3.2.1 to provide a concise description of the coverage range +value definition. Further, handling of format encodings different from GML are established. -Deriving an ontology representation of the application schema (using RDF(S)/SKOS/OWL) - to support Semantic Web / Linked Data implementations. - 2017-04-04 - Testbed-12 ShapeChange Engineering Report +This enhanced coverage type is used, for example, by the Web Coverage Service (WCS) Standard [1] version 2.0 and higher, but is independent from WCS service. This augmented +coverage structure can serve a wide range of coverage application domains and service types, thereby contributing to harmonization and interoperability. + Peter Baumann - - 2012-08-27 - + + 99-108r2 + + + Cliff Kottman + 1999-03-26 + Topic 8 - Relationships Between Features + + Topic 08 - Relationships Between Features + 99-108r2 + + This Topic introduces an abstraction for the relationships between entities in the real world. This abstraction is modeled as relationships between the features introduced in Topic 5. + + + + 11-089r1 + OWS-8 Engineering Report - Guidelines for International Civil Aviation Organization (ICAO) portrayal using SLD/SE + 11-089r1 + + This OGC® document gives guidelines to portrayal of AIXM according to ICAO aviation symbology using SLD/SE. - - Surface Water Interoperability Experiment FINAL REPORT - 12-018r2 - This report describes the methods, results, issues and recommendations generated by the Surface Water Interoperability Experiment (SW IE), carried out as an activity of the OGC Hydrology Domain Working Group (HDWG). The SW IE was designed to advance the development of WaterML 2.0 and test its use with various OGC service standards (SOS, WFS, WMS and CSW). A secondary aim was to contribute to the development of a hydrology domain feature model and vocabularies, which are essential for interoperability in the hydrology domain, although these are not the main focus for the IE. + Daniel Tagesson + + + + 2011-11-23 + OWS-8 Engineering Report - Guidelines for International Civil Aviation Organization (ICAO) portrayal using SLD/SE - - Peter Fitch - OGC® Surface Water Interoperability Experiment FINAL REPORT - 12-018r2 - + + + Testbed-12 Vector Tiling Implementation Engineering Report + 16-067r4 + + + 16-067r4 + 2017-05-15 - - Indoor Mapping and Navigation Pilot: Public Safety Features CityGML ADE ER - 19-032 - This document defines an Application Domain Extension (ADE) of CityGML for public safety use cases. The ADE has been developed as part of OGC’s Indoor Mapping and Modeling Pilot project sponsored by the National Institute of Standards and Technology (NIST), Communications Technology Laboratory (CTL), Public Safety Communications Research (PSCR) Division. The ADE has been developed primarily based on reference preplan symbology created by the National Alliance for Public Safety GIS (NAPSG) Foundation. NAPSG is a 501 (C) (3) not-for-profit organization that was established in 2005 to overcome challenges faced by Federal, tribal, state, and local public safety agencies in the United States. NAPSG focuses on using GIS technology to resolve challenges that occur. In the definition of the ADE, public safety requirements that were not explicit in NAPSG have also been considered. This Engineering Report (ER) provides the methodology of the ADE development, details the implementation of the ADE and its structure and the application of the ADE in the context of public safety use cases. + This OGC Testbed 12 Engineering Report (ER) discusses the topic of implementing vector tiles in an OGC GeoPackage. This report builds on the general topic of vector tiling discussed in OGC Testbed 12 Engineering Report [OGC 16-068r4]. -The findings include: +Since its public release in 2012, OGC GeoPackage has been getting increasingly popular within the geospatial industry for a variety of use cases, such as a means to package geospatial data for use on a mobile device and as a means to exchange geospatial data between two systems. -A methodology to transform NAPSG symbology to data elements; +The OGC GeoPackage standard currently specifies requirements (rules) for storing raster tiles and vector (simple) features. This Engineering Report proposes an extension to the supported data types by introducing an implementation for vector tiles. -A need for an extension of a reference to four existing CityGML classes; and +While tiling and the use of multiple levels of details are a proven technique for accessing and visualizing raster data, it is less commonly applied for vector data. This is due to the increased complexity compared to raster tiling and lack of standardization on the topic. Yet, implementing vector tiles can provide the same benefits as for using raster tiles. -The creation of seven new CityGML classes that are critical for public safety use cases. - 19-032 - Steven Chau & Mohsen Kalantari - - - 2020-07-30 - OGC Indoor Mapping and Navigation Pilot: Public Safety Features CityGML ADE ER - - - - - - - - 2019-08-13 - Geographic information — Well-known text representation of coordinate reference systems - Roger Lott - Geographic information — Well-known text representation of coordinate reference systems - 18-010r7 - - This Standard defines the structure and content of well-known text strings describing coordinate reference systems (CRSs) and coordinate operations between coordinate reference systems. It does not prescribe how implementations should read or write these strings. +Services can easily cache tiles and return them instantly upon request, without the need for any additional pre/post processing. Consequently, clients can get tiles very fast, ensuring fast and responsive maps. -This Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2019. It extends the WKT in OGC document 12-063r5 (ISO 19162) which was based on ISO 19111:2007 and ISO 19111-2:2009. That version consolidated several disparate versions of earlier WKT (so-called WKT1) and added the description of coordinate operations. +Using tiled, multileveled data representations, clients can always access the data most suitable for their current map location and scale. This avoids the need to load too much data, which can cause excessive memory usage and reduce overall performance. -This jointly developed draft has been submitted by ISO TC211 for circulation as a Draft International Standard (DIS). This version incorporates comments made during the ISO TC211 New Work Item Proposal acceptance ballot. - 18-010r7 +The goal is to enable systems to use OGC GeoPackage as a means to store and access vector tiles in an efficient way, similar to raster tiles. + + + Testbed-12 Vector Tiling Implementation Engineering Report + Daniel Balog, Robin Houtmeyers - - OWS-6 SWE PulseNet™ Engineering Report - 09-073 - - James Ressler - 09-073 - 2009-08-05 - - - + + + 2023-07-27 + Mark Burgoyne, David Blodgett, Charles Heazel, Chris Little - OWS-6 SWE PulseNet™ Engineering Report - - This document summarizes work delivered on the Sensor Web Enablement (SWE) thread of OWS-6. In particular, Northrop Grumman’s contribution from PulseNet™ to the Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) standard-compliant sensors into an OGC SWE-based architecture. - - - OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard - 20-010 - 2021-09-13 - - OGC City Geography Markup Language (CityGML) Part 1: Conceptual Model Standard - 20-010 - Thomas H. Kolbe, Tatjana Kutzner, Carl Stephen Smyth, Claus Nagel, Carsten Roensdorf, Charles Heazel - - - - - This Standard defines the open CityGML Conceptual Model for the storage and exchange of virtual 3D city models. The CityGML Conceptual Model is defined by a Unified Modeling Language (UML) object model. This UML model builds on the ISO Technical Committee 211 (ISO/TC 211) conceptual model standards for spatial and temporal data. Building on the ISO foundation assures that the man-made features described in the city models share the same spatiotemporal universe as the surrounding countryside within which they reside. + The OGC API — Environmental Data Retrieval (EDR) standard provides a family of lightweight query interfaces to access spatiotemporal data resources by requesting data at a Position, within an Area, along a Trajectory or through a Corridor. A spatio-temporal data resource is a collection of spatio-temporal data that can be sampled using the EDR query pattern geometries. These patterns are described in the section describing the Core Requirements Class. -A key goal for the development of the CityGML Conceptual Model is to provide a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. +The goals of the EDR Application Programming Interface (API) that is specified by this standard are to: -The class models described in this standard are also available at https://github.com/opengeospatial/CityGML3-Workspace/tree/1.0/UML/CityGML - - - - This document provides an overview of the portrayal work within the OWS-9 Aviation thread. Using open standards, a web services architecture was designed and prototyped to enable the retrieval of static airport maps in support of an ePIB. An ePIB, or Digitally Enhanced Pre-Flight Information Bulletin, provides the pilot with an easy-to-interpret representation of any relevant aeronautical and meteorological events that are likely to affect the flight, expressed as Digital NOTAMs. The static airport maps are an important part of an ePIB and should provide a graphical representation of the status of departure and arrival airports, showing only NOTAMs relevant to the particular context and represented geographically so that the effect of the NOTAM is clear. This approach avoids the pilot scanning through pages of textual description for potentially relevant NOTAMs, reducing the workload and the risk of missing a critical piece of information. - OWS-9 Aviation Portrayal Engineering Report - 12-151 - 2013-02-06 - - - Daniel Balog, Roger Brackin, Robin Houtmeyers - - - 12-151 - - OWS-9 Aviation Portrayal Engineering Report - - - - - - - - - - - - - This paper does four things. Firstly, it describes the benefits of representing geospatial data using semantics, graph, and web technologies. Secondly, it gives an overview of the current capabilities of the GeoSPARQL standard, showing that many benefits of semantic and graph technologies are already within reach. Thirdly, it outlines some shortcomings of the existing GeoSPARQL implementation specification that, if addressed, would unlock its potential to a greater extent, and could significantly increase its user base. Finally, it identifies other related activities that are current at the time of editing this paper. In doing so, it establishes liaison’s between the different activities in an attempt to achieve alignment. +Make it easier to access a wide range of data through a uniform, well-defined simple Web interface; -The purpose of this paper is to provoke further thought about a best course for further development of the GeoSPARQL standard, and to invite active involvement in that development. Particularly, the involvement of people and organizations that until now have not been able to put GeoSPARQL to good use, either because of perceived limitations or because of unfamiliarity with the standard, will be highly valued. Also, since one development under consideration is to make provisions for use of GeoSPARQL with non-geographic spatial data, those that see opportunities for using spatial data in a broad sense together with the aforementioned technologies are cordially invited to share their views. - OGC Benefits of Representing Spatial Data Using Semantic and Graph Technologies - +To achieve data reduction to just the data needed by the user or client while hiding much of the data storage complexity. + +A major use case for the EDR API is to retrieve small subsets from large collections of environmental data, such as weather forecasts, though many other types of data can be accessed. The important aspect is that the requested data can be unambiguously specified by spatio-temporal coordinates. + +The EDR API query patterns — Position, Area, Cube, Trajectory or Corridor — can be thought of as discrete sampling geometries, conceptually consistent with the feature of interest in the Sensor Observation Service (SOS) standard. A typical data resource accessed by an EDR API instance is a multidimensional dataset that could be accessed via an implementation of the Web Coverage Service (WCS) standard. In contrast to SOS and WCS, the EDR API is fully consistent with the patterns of the OGC API family of standards and aims to provide a single set of simple-to-use query patterns. Use cases for EDR range from real or virtual time-series observation retrievals, to sub-setting 4-dimensional data cubes along user-supplied sampling geometries. These query patterns do not attempt to satisfy the full scope of either SOS or WCS, but instead provide useful building blocks to enable the composition of APIs that satisfy a wide range of geospatial data use cases. By defining a small set of query patterns (and no requirement to implement all of them), the EDR API should help to simplify the design of systems (as they can be performance tuned for the supported queries) making it easier to build robust and scalable infrastructures. + +With the OGC API family of standards, the OGC community has extended its suite of standards to include Resource Oriented Architectures and Web Application Programming Interfaces (APIs). These standards are based on a shared foundation, specified in OGC API-Common, which defines the resources and access paths that are supported by all OGC APIs. The resources are listed in Table 1. This document extends that foundation to define the EDR API. + OGC API - Environmental Data Retrieval Standard + + 19-086r6 + OGC API - Environmental Data Retrieval Standard + + 19-086r6 - 19-078r1 - OGC Benefits of Representing Spatial Data Using Semantic and Graph Technologies + + + BI is an umbrella term for a major component of IT infrastructure. It encompasses Data +Warehouses, Business Analytics, Dashboards and Scorecards. This IT infrastructure is associated +with C-level decision-making in an organization. These decision-making tools have typically +included location as a dumb attribute (coded sales zones as opposed to sales zones as geographic +boundaries). At this point in the BI lifecycle, customers are looking to derive additional business +benefit / return on investment from intelligent location data; data discovery and unstructured data. + 2012-07-12 + 09-044r3 + Geospatial Business Intelligence (GeoBI) + Geospatial Business Intelligence (GeoBI) + + 09-044r3 - 19-078r1 + - - Joseph Abhayaratna, Linda van den Brink, Nicholas Car, Rob Atkinson, Timo Homburg, Frans Knibbe, Kri - 2020-10-05 - - - The tiling of feature data is an approach that can be used to optimize the delivery vector feature data over the web to create maps. The approach provides a pre-defined shape (i.e. tile) to package vector data. Tiling of vector data enables faster map loads (due to reduced size) and offer flexible styling on the client side with modern, easy-to-use tools. - -This Engineering Report (ER) describes the work done by participants during the Vector Tiles Pilot (VTP) to add Mapbox and GeoJSON vector tile support to Web Map Tile Servers. A summary of other work done in the VTP is presented in the VTP Summary Engineering Report [1]. - -NOTE -This engineering report interchangeably uses both 'tiled feature data' and the colloquial term 'vector tiles'. - - OGC Vector Tiles Pilot: WMTS Vector Tiles Extension Engineering Report - 2019-02-11 - Panagiotis (Peter) A. Vretanos - 18-083 - WMTS Vector Tiles Extension Engineering Report - 18-083 + George Percivall, Raj Singh - - - - - - - - GeoAPI 3.0 Implementation Standard with corrigendum - The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be used for the manipulation of geographic information structured following the specifications adopted by the Technical Committee211 of the International Organization for Standardization (ISO) and by the Open Geospatial Consortium (OGC). This standard standardizes the informatics contract between the client code which manipulates normalized data structures of geographic information based on the published API and the library code able both to instantiate and operate on these data structures according to the rules required by the published API and by the ISO and OGC standards. - 09-083r4 - GeoAPI 3.0 Implementation Standard with corrigendum - 2018-04-15 - 09-083r4 - + - Adrian Custer + + 2021-02-26 - - - - This OGC Testbed 17 Engineering Report (ER) analyses the Measures and Signatures Intelligence Enterprise Service Bus (MASBUS) pilot software and the efforts to integrate with OGC SensorThings API resources. After introducing MASBUS, a server implementation is designed to digest sensor data and demonstrate the SensorThings MQTT (Message Queuing Telemetry Transport) extension of the MASBUS software. To show the SensorThings MQTT extension of the MASBUS software, a MASBUS client implementation is also presented. This ER discusses the results of the MASBUS integration, including all lessons learned from the experiments completed during the OGC Testbed 17 Sensor Integration thread and concludes with a set of optimum recommendations. + + + + 16-011r5 + Carl Reed + 16-011r5 + Volume 8: CDB Spatial and Coordinate Reference Systems Guidance + Volume 8: CDB Spatial and Coordinate Reference Systems Guidance + Volume 8 of the CDB standard defines the conceptual model and the methodologies that allow the description, and transformation or conversion, of geometric properties within a set of spatial reference frames supported by the CDB standard. The CDB Spatial Reference Model (SRM) supports an unambiguous specification of the positions, directions, and distances associated with spatial information. This document also defines algorithms for precise transformation of positions, directions and distances among different spatial reference frames. - OGC Testbed 17: MASBUS Integration Engineering Report - 2022-03-31 - + + + + OpenGIS Location Services (OpenLS): Part 6 - Navigation Service + 2008-09-04 + 08-028r7 + Location Services (OpenLS): Part 6 - Navigation Service - - 21-029 - OGC Testbed 17: MASBUS Integration Engineering Report - Sara Saeedi - 21-029 - + - - - + 08-028r7 - - + + This OpenGIS Implementation Standard defines the interfaces for OpenGIS Location Services (OpenLS): Part 6 - Navigation Service (formerly the Full Profile of the Route Determination Service), which is part of the GeoMobility Server (GMS), an open location services platform. + Gil Fuchs + + + OGC OpenFlight Scene Description Database Specification 16.0 Community Standard + + Steve Thompson + + 19-065 + OpenFlight Scene Description Database Specification 16.0 Community Standard + 19-065 + + This document describes the OpenFlight Scene Description Database Specification, commonly +referred to as simply “OpenFlight”. OpenFlight is a 3D scene description file format that was +created and is maintained by Presagis. While OpenFlight databases are typically created and edited +using Presagis software tools, the format is widely adopted and as a result, many tools exist +to read and write OpenFlight database files. +The primary audience for this document includes software developers whose applications are +intended to read and/or write OpenFlight database files. To this end, this document discusses +concepts incorporated in OpenFlight and contains a detailed description of the physical layout +of OpenFlight files as represented on disk. - - 19-046r1 - OGC Testbed-15: Quebec Model MapML Engineering Report - Scott Serich - OGC Testbed-15: Quebec Model MapML Engineering Report - - 2020-01-08 - 19-046r1 - This OGC Testbed-15 Engineering Report (ER) describes the Map Markup Language (MapML) enabled client component implementation for the Quebec Lake-River Differentiation Model in the Machine Learning (ML) task of Open Geospatial Consortium (OGC) Testbed-15 (T-15). This ER presents the MapML parsing capabilities that were developed to illustrate the outputs of a ML model to delineate lake and river features from an undifferentiated waterbody vector dataset in Québec, Canada. Client data was accessed through an OGC Web Processing Service (WPS) interface in coordination with an OGC API - Features implementation. + + 2020-07-09 + - - - Gazetteer + + Lorenzo Bigagli, Doug Nebert, Uwe Voges, Panagiotis Vretanos, Bruce Westcott + OGC® Catalogue Services Specification - HTTP protocol binding - Abstract Test Suite + 14-014r3 + See OGC 12-176r7 -- OGC® Catalogue Services Specification - HTTP Protocol Binding. + 2016-06-10 + + - + Catalogue Services Specification - HTTP protocol binding - Abstract Test Suite + 14-014r3 + + + + + + + AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper + 15-116 + This document provides a proposal for a new O&M (Observations and Measurements) profile focused on Active and Healthy Ageing, called AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper). This document introduces the overall need for such a profile and it discusses the measures which have been identified. - + + 15-116 - Gazetteer - 01-036 - An authority for place names. Returns their associated geometries - 01-036 - Rob Atkinson - 2001-03-15 + Giuseppe Conti, Fabio Roncato + AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper + + 2016-04-26 + - - 03-002r8 - Binary-XML Encoding Specification - - - Craig Bruce + + + OWS1.2 Image Handling Requirements + + 04-052 + OWS1.2 Image Handling Requirements + 2004-09-26 + + Arliss Whiteside - - This document specifies a binary encoding format for the efficient representation of XML data, especially scientific data that is characterized by arrays of numbers. This encoding format is applicable to any application that uses XML format. + + This document was developed as part of the Image Handling Thread of the OGC Web Services Initiative Phase 1 Thread Set 2 (OWS 1.2). This document specified the requirements for the image handling functions to be supported by draft specifications prepared under that thread. + 04-052 - - Binary-XML Encoding Specification - 2003-05-07 - 03-002r8 - + - Peng Yue, Boyi Shangguan - - OGC Training Data Markup Language for Artificial Intelligence (TrainingDML-AI) Part 1: Conceptual Model Standard - 23-008r3 - - The Training Data Markup Language for Artificial Intelligence (TrainingDML-AI) Standard aims to develop the UML model and encodings for geospatial machine learning training data. Training data plays a fundamental role in Earth Observation (EO) Artificial Intelligence Machine Learning (AI/ML), especially Deep Learning (DL). It is used to train, validate, and test AI/ML models. This Standard defines a UML model and encodings consistent with the OGC Standards baseline to exchange and retrieve the training data in the Web environment. - -The TrainingDML-AI Standard provides detailed metadata for formalizing the information model of training data. This includes but is not limited to the following aspects: - -How the training data is prepared, such as provenance or quality; -How to specify different metadata used for different ML tasks such as scene/object/pixel levels; -How to differentiate the high-level training data information model and extended information models specific to various ML applications; and -How to introduce external classification schemes and flexible means for representing ground truth labeling. - OGC Training Data Markup Language for Artificial Intelligence (TrainingDML-AI) Part 1: Conceptual Model Standard - - - - 23-008r3 - 2023-09-19 - - - - - 2009-03-06 + Guidance and Profile of GML for use with Aviation Data + + 2012-05-15 + 12-028 + Guidance and Profile of GML for use with Aviation Data + 12-028 + OGC Aviation Domain Working Group + - 08-128 - GML 3.2 implementation of XML schemas in 07-022r1 - GML 3.2 implementation of XML schemas in 07-022r1 - - - Simon Cox - 08-128 + The ISO 19107 spatial schema, which is implemented by GML, is very complex. ISO +19107 defines an extensive list of geometries, geometric properties and operations – +many of which are not necessary for aeronautical information applications. In addition, +the ISO 19107 contains an exhaustive 3D geometry model that is probably not needed in +its entirety for AIXM either. Therefore, a GML profile for AIXM needs to be defined. +The objective of this document is to identify the elements of the AIXM-GML profile and +also to provide guidelines for the use of GML constructs in AIXM data sets. + - - - 2023-01-05 - 22-018 - Testbed-18: Secure Asynchronous Catalog Engineering Report - 22-018 - Yves Coene, Christophe Noel - Testbed-18: Secure Asynchronous Catalog Engineering Report - + + Replaced previous material in Topic 7 with ISO 19101-2, Reference Model - Geographic Information - Imagery. Version 5 of OGC Topic 7 is identical with ISO 19101-2 Working Draft #3. Topic 7 will be updated jointly with the progress of ISO 19191-2. Appendix A of Topic 7, version 4 contained a White Paper on Earth Image Geometry Models. That white paper is now separate OGC Recommendation document. + 2004-10-15 + + + 04-107 + 04-107 + Topic 07 - Earth Imagery + + + Topic 7 - Earth Imagery + George Percivall + + + + 2010-08-02 + OWS-7 Engineering Report - Geosynchronization service + 10-069r2 + + OWS-7 Engineering Report - Geosynchronization service + Panagiotis (Peter) A. Vretanos - - This OGC Testbed-18 Engineering Report (ER) describes the results of the Secure, Asynchronous Catalogs Task in the Testbed-18 Catalogs, Filtering, and Moving Features (CMF) thread. This task explored the following. - -How search processes that are supported in a classical OGC Catalogue Service for the Web (CSW)/ISO 19115 environment can be supported through tailoring of the OGC API-Records specification. -How an asynchronous catalog scenario can be supported in which metadata publishers push new data to catalog instances that lead to new or updated catalog entries and how subscribers are informed about these updates. -How Data Centric Security (DCS) can be applied in combination with OGC API-Records to allow encrypted delivery and access of catalog metadata between communication partners. - - - + 10-069r2 + This candidate standard describes a service that allows data collectors to propose changes to be made to a data provider's features. A change proposal can be made to create new data or to modify/delete existing data. Proposed changes are reviewed (either manually or automatically) an are either accepted or rejected. Accepted changes are applied to the feature(s). The service also maintains a log of all changes applied to each feature that can be used for replication. - Sensor Alert Service + - The Sensor Alert Service (SAS) can be compared with an event notification system. The sensor node is the object of interest. Each node has to advertise its publications at a SAS (advertise). - Sensor Alert Service - 06-028r3 - - 06-028r3 - - - 2007-05-16 - Ingo Simonis - + + + This standard specifies the location formats to be used by SMS for mobile phones and in other systems handling the SMS with location formats produced by mobile phones or LBS services. + OGC®: Open GeoSMS Specification + 09-142r1 + 2010-02-01 + 09-142r1 + Open GeoSMS Specification + Chun-fu Lin, Zhong-Hung Lee, Jen-Chu Liu, Kuo-Yu Chuang + + + + + + + OGC Development of Disaster Spatial Data Infrastructures for Disaster Resilience + + 2018-12-18 + Development of Disaster Spatial Data Infrastructures for Disaster Resilience + 18-087r5 + + Terry Idol, Robert Thomas + This report presents the results of a concept development study on Disasters Interoperability, sponsored by US Geological Survey (USGS) and Federal Geographic Data Committee (FGDC), and Department of Homeland Security (DHS), and executed by the Open Geospatial Consortium (OGC). The focus of this study was to understand how to best support the development of, or combination of SDI(s) for the use in disasters, to advance the understanding of stakeholder issues, and serve stakeholders’ needs. The study included stakeholder engagements, workshops and open Request for Information (RFI) that gathered external international positions and opinions on the optimal setup and design of an SDI for disasters. The outflow of this report will guide a series of interoperability pilots to address priority challenges identified by the community in this study. The report follows the format and document of the OGC Arctic Spatial Data Pilot; Phase 1 Report: Spatial Data Sharing for the Arctic. - CityGML and AR Engineering Report - 18-025 - - Jérôme Jacovella-St-Louis - 18-025 - 2019-03-07 - This OGC Testbed-14 Engineering Report (ER) describes the results of the Augmented Reality (AR) work performed in the Testbed-14 CityGML and Augmented Reality work package which was part of the Next Generation Services thread. - -By integrating information available from urban models within a view of the real world through a mobile device, this testbed activity explored the possibilities offered by AR in a geospatial context. The ER additionally discusses the approach used to bring in these urban models from various data sources. The experiments also covered to some extent Virtual Reality (VR) where any city can be explored freely from a computer display or potentially within a VR headset. - -A continuation of these experiments would have looked at a combination of Augmented and Virtual Reality (Mixed Reality). The portrayal of AR and three-dimensional (3D) content through extending a common conceptual model to style classic geospatial features (as explored in the Testbed-14 Portrayal work) is also touched upon. The efficient transmission of 3D content is also a subject of this document through the use of a simple 3D transmission format developed during the initiative. - -This ER provides many insights that showcase what is now made possible by the combination of AR, VR and integrated urban models. - -The testbed work shines light on the benefits of applying a common portrayal approach to AR, bridging the gap between AR applications and traditional Geographic Information Systems and services. - -The ER introduces a new, simple approach and conceptual model for transmitting 3D geospatial content which could be the basis to define simple profiles for the I3S and 3D Tiles community standards. It could also inform enhancements to the 3D Portrayal Service (3DPS) and/or next generation services (e.g., WFS 3.0) for delivering 3D contents in a format agnostic manner. - -Finally, the ER covers methods to bring in different types of geospatial content from various sources for integration into AR applications. - -During Testbed-14, the participants demonstrated AR experiences with geospatial datasets providing integrated views of urban spaces. Two clients and two services were shown to be interoperable, streaming AR content through a simple 3D transmission format, leveraging either GeoJSON or GNOSIS Map Tiles, as well as E3D 3D model specifications. - -The feasibility of extending a classic portrayal conceptual model for AR was also shown. In order to serve them to the clients in the supported transmission formats, geospatial data sets of various types and in various formats were successfully imported for consumption by the services. - - OGC Testbed-14: CityGML and AR Engineering Report - - - OWS-4 CSW ebRIM Modelling Guidelines IPR - Tim Wilson, Renato Primavera, Panagiotis (Peter) A. Vretanos + 18-087r5 - 2007-06-06 - - The OWS-4 CSW ebRIM Modelling Guidelines Interoperability Program Report (IPR) provides guidance for creating a standard methodology for mapping geospatial domain information models to ebRIM [www.oasis-open.org/committees/regrep/documents/2.0/specs/ebrim.pdf]. It also presents the results of mapping specific Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] and Feature Catalog domain models to ebRIM for use with OpenGIS Catalog Service Standard [http://www.opengeospatial.org/standards/cat] implementations in the OWS-4 Initiative [http://www.opengeospatial.org/projects/initiatives/ows-4]. - 06-155 - 06-155 - OWS-4 CSW ebRIM Modelling Guidelines IPR - - - - - - Harmonising Standards for Water Observation Data - Discussion Paper - 09-124r2 + - + This discussion paper investigates the possible uses of NetCDF as a representation of WaterML timeseries data. The work is largely based on the WaterML 2.0 standard for timeseries, the NetCDF core and extensions standards and the CF-NetCDF and ADCC conventions. + WaterML 2.0 - Timeseries - NetCDF Discussion Paper - 2010-06-30 - 09-124r2 - Harmonising Standards for Water Observation Data - Discussion Paper - Peter Taylor - This document investigates the potential for harmonisation of water data standards, with the goal of developing an OGC compliant standard for the exchange of water observation data. The work will be based on OGC‘s Observations and Measurements abstract model [10-004r2] . The goal is to create an O&M profile for the water domain. Development of the OGC compliant O&M profile will begin by examining the content and structure of existing standards and suggesting future methodology for developing a harmonised model for observation data. This approach will make use of existing standards where possible. - -The focus of this document is in-situ style observations (which are generally related to water quantity). Ex-situ measurements, such as those common to measuring water quality, will be addressed in future work. -2 Normative - - - - + 12-031r2 + 2012-07-12 + 12-031r2 + WaterML 2.0 - Timeseries - NetCDF Discussion Paper + + Doug Palmer - - - OGC Testbed-16: Analysis Ready Data Engineering Report - - - Joan Maso - Analysis Ready Data Engineering Report - 20-041 - 2021-01-13 - 20-041 - The Committee on Earth Observation Satellites (CEOS) defines Analysis Ready Data (ARD) for Land (CARD4L) as satellite data that have been processed to a minimum set of requirements and organized into a form that allows immediate analysis with a minimum of additional user effort and interoperability both through time and with other datasets. - -This OGC Testbed 16 Engineering Report (ER) generalizes the ARD concept and studies its implications for the OGC Standards baseline. In particular, the ER analyses how modern federated data processing architectures applying data cubes and Docker packages can take advantage of the existence of ARD. Architectures for ARD should minimize data transmission and allow and favor code transmission and remote execution. This ER also considers a workflow in which new processes are triggered as soon as new data becomes available. This is part of the event driven discussion. - - - 11-111 - Ordering Services for Earth Observation Products Adoption Voting Comments and Answers - Ordering Services for Earth Observation Products Adoption Voting Comments and Answers - This document lists the No votes received during the TC adoption vote (2011-05-03 - 2011-07-02) together with the responses from the OSEO SWG. - 11-111 - - + + Matthes Rieke + 2014-07-15 + + OGC® Testbed 10 Report on Aviation Binding AIXM to Development Tools + 14-007 + Testbed 10 Report on Aviation Binding AIXM to Development Tools + + + This document is a deliverable of the OGC Testbed 10 (Testbed-10). Its contents cover the summary of the work carried out regarding the creation and evaluation of generated data bindings for the Aeronautical Information Exchange Model (AIXM) for established programming languages. +Suggested additions, changes, and comments on this draft report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document. + + 14-007 - Daniele Marchionni - - 2012-01-25 + - + + 2020-09-17 - - 2007-01-29 - Specification best practices - This document describes a variety of Best Practices and Specification development guidance that the Members have discussed and approved over the years. These Best Practices have not been captured in other formal OGC documents other than meeting notes. - 06-135r1 - Carl Reed - 06-135r1 - Specification best practices + QB4ST: RDF Data Cube extensions for spatio-temporal components + + QB4ST: RDF Data Cube extensions for spatio-temporal components + 16-142 + + Rob Atkinson + 16-142 + - - + This document describes an extension to the existing RDF Data Cube ontology to support specification of key metadata required to interpret spatio-temporal data. The RDF Data Cube defines CodedProperties, which relate to a reference system based on a list of terms, QB4ST provides generalized support for numeric and other ordered references systems, particularly Spatial Reference Systems and Temporal Reference Systems. Although RDF Data Cube supports AttributeProperties for metadata of individual observations, the requirement is to specify such metadata per property, rather than for each observation, and thus allow different properties to use different spatial or temporal reference systems. QB4ST also provides for such properties to be defined for a ComponentProperty, or defined at the time of referencing that ComponentProperty in a ComponentSpecification. QB4ST is thus aimed at improving the scope and consistency of dataset metadata, and hence discovery and interpretation of spatio-temporal data through its spatio-temporal reference system and bounding values. - + + OWS-5 Earth Observation Web Processing Services (WPS) Engineering Report + + + OWS-5 Earth Observation Web Processing Services (WPS) Engineering Report + 08-058r1 + Stefan Falke + This document serves to describe the use of web processing services and the OGC Web Processing Service (WPS) in earth observation (EO) applications. It provides an overview of web processing services and a description of developments related to earth observation implementations of OGC WPS in the OGC OWS-5 testbed. + 08-058r1 + 2008-09-12 - - - Joan Masó - OGC Citizen Science Interoperability Experiment Engineering Report - 19-083 - - 19-083 - Citizen Science Interoperability Experiment Engineering Report - 2020-02-13 - This Engineering report describes the first phase of the Citizen Science (CS) Interoperability Experiment (IE) organized by the EU H2020 WeObserve project under the OGC Innovation Program and supported by the four H2020 Citizen Observatories projects (SCENT, GROW, LandSense, and GroundTruth 2.0) as well as the EU H2020 NEXTGEOSS project. The activity covered aspects of data sharing architectures for Citizen Science data, data quality, data definitions and user authentication. + + + + + + Panagiotis (Peter) A. Vretanos, Clemens Portele + A fundamental operation performed on a collection of features is that of filtering in order to obtain a subset of the data which contains feature instances that satisfy some filtering criteria. This document specifies -The final aim was to propose solutions on how Citizen Science data could be integrated in the Global Earth Observation System of Systems (GEOSS). The solution is necessarily a combination of technical and networking components, being the first ones the focus of this work. The applications of international geospatial standards in current Citizen Science and citizen observatory projects to improve interoperability and foster innovation is one of the main tasks in the IE. +A filter grammar called Common Query Language (CQL2); -The main result of the activity was to demonstrate that Sensor Observing Services can be used for Citizen Science data (as proposed in the Open Geospatial Consortium (OGC) Sensor Web Enablement for Citizen Science (SWE4CS) Discussion Paper) by implementing SWE4CS in several clients and servers that have been combined to show Citizen Science observations. In addition, an authentication server was used to create a federation between three projects. This federated approach is part of the proposed solution for GEOSS that can be found in the last chapter. Many open issues have been identified and are expected to be addressed in the second phase of the experiment, including the use of a definitions server. +Two encodings for CQL2 - a text and a JSON encoding. + +The Common Query Language (CQL2) defined in this document is a generic filter grammar that can be used to specify how resource instances in a source collection of any item type, including features, can be filtered to identify a results set. Typically, CQL2 is used in query operations to identify the subset of resources, such as features, that should be included in a response document. However, CQL2 can also be used in other operations, such as updates, to identify the subset of resources that should be affected by an operation. + +Each resource instance in the source collection is evaluated against a filtering expression. The filter expression always evaluates to true, false or null. If the expression evaluates to true, the resource instance satisfies the expression and is marked as being in the result set. If the overall filter expression evaluates to false or null, the data instance is not in the result set. Thus, the net effect of evaluating a filter expression is a set of resources that satisfy the predicates in the expression. + +The Common Query Language and its text encoding are not new, but this is the first time that the language is formally specified. The Common Query Language with the acronym CQL was originally created as a text encoding for use with implementations of the OGC Catalogue Service Implementation Specification. The language is based on the capabilities in the OGC Filter Encoding Standard, which was originally part of the Web Feature Service (WFS) Standard. + +The Common Query Language as specified in this document is a revision of this earlier version. While the language design including the classification of operators are consistent with the earlier specification, there have been a number of changes and existing implementations of CQL will need to be updated to process filter expressions specified by this document. This document therefore uses the acronym CQL2 to refer to the current version of the Common Query Language. + 2024-07-26 + Common Query Language (CQL2) + 21-065r2 + + + Common Query Language (CQL2) + 21-065r2 + + - - - Testbed 10 Recommendations for Exchange of Terrain Data - 14-006r1 + + 2011-03-28 + + + + Earth Observation Satellite Tasking Extension for SPS 2.0 + 10-135 + 10-135 + OGC® Sensor Planning Service Interface Standard 2.0 Earth Observation Satellite Tasking ExtensionOGC® Sensor Planning Service + Alexandre Robin, Philippe Mérigot + The SPS 2.0 Earth Observation Satellite Tasking Extension Standard specifies extensions to the OGC Sensor Planning Service (SPS) 2.0 Interface Standard. The SPS configuration proposed in this extension is intended to support the programming process of Earth Observation (EO) sensor systems. This standard describes a consistent SPS configuration that can be supported by many satellite data providers, most of whom have existing facilities for the management of these programming requests. The resulting extended web service interface can be used for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or canceling such a request, and for requesting information on means of obtaining the data collected by the requested task. + + + + + + 05-047r2 + Ron Lake + - This document is a deliverable of the OGC Testbed 10 (Testbed-10). Its contents cover the summary of the work carried out regarding the recommendations for the exchange of terrain data. -Suggested additions, changes, and comments on this draft report are welcome and encouraged. Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document. -The changes made in this document version, relative to the previous version, are tracked by Microsoft Word, and can be viewed if desired. If you choose to submit suggested changes by editing this document, please first accept all the current changes, and then make your suggested changes with change tracking on. + + GML in JPEG 2000 for Geographic Imagery + 05-047r2 + + 2005-03-28 + The GML (Geography Markup Language) is an XML grammar for the encoding geographic information including geographic features, coverages, observations, topology, geometry, coordinate reference systems, units of measure, time, and value objects. +JPEG 2000 is a wavelet based encoding for imagery that provides the ability to include XML data for description of the image within the JPEG 2000 data file. +This specification defines the means by which GML is to be used within JPEG 2000 images for geographic imagery. This includes the following: - - 2014-07-15 - - + GML in JPEG 2000 for Geographic Imagery - 14-006r1 - OGC® Testbed 10 Recommendations for Exchange of Terrain Data - Daniel Balog - - - OGC: Towards Data Cube Interoperability - 21-067 - OGC: Towards Data Cube Interoperability - - - 2021-10-07 - Ingo Simonis - + + + 2020-04-17 + - Data cubes, multidimensional arrays of data, are used frequently these days, but differences in design, interfaces, and handling of temporal characteristics are causing interoperability challenges for anyone interacting with more than one solution. To address these challenges, the Open Geospatial Consortium (OGC) and the Group on Earth Observation (GEO) invited global data cube experts to discuss state-of-the-art and way forward at the “Towards Data Cube Interoperability” workshop. The two-day workshop, conducted in late April 2021, started with a series of pre-recorded position statements by data cube providers and data cube users. These videos served as the entry points for intense discussions that not only produced a new definition of the term ‘data cube’ (by condensing and shifting emphasize on what is known as the six faces model), but also pointed out a wide variety of expectations with regards to data cube behaviour and characteristics as well as data cube usage patterns. This report summarizes the various perspectives and discusses the next steps towards efficient usage of data cubes. It starts with the new definition of the term Data Cube, as this new understanding drives several recommendations discussed later in this report. The report includes further discussion that followed the actual workshop, mainly conducted in the context of the Geo Data Cube task in OGC Testbed-17. - 21-067 + + + An Experiment to Link Geo-Referenced Multimedia and CityGML Features + An Experiment to Link Geo-Referenced Multimedia and CityGML Features + 19-090r1 + Ki-Joune Li, Sung-Hwan Kim, Yong-Bok Choi + 19-090r1 + In this paper, we present an experiment on linking geo-referenced images and videos with CityGML objects. Data models are proposed with XML schema from two viewpoints: one for linking features in 2D images or videos with 3D CityGML objects and the other for camera FoV (Field of View). In order to validate the proposed data models, we developed an authoring tool for building XML documents to link geo-referenced images and videos with CityGML objects and a web environment for processing queries based on the linking data. + - - 2019-09-24 - 19-003 - Earth System Grid Federation (ESGF) Compute Challenge - - This Open Geospatial Consortium (OGC) Engineering Report (ER) will describe the advancement of an Execution Management System (EMS) to support Web Processing Service (WPS) climate processes deployed on the Earth System Grid Federation (ESGF). The report introduces climate data, processes and applications into Common Workflow Language (CWL) workflows with the intent of advancing: application packaging, deployment and execution in clouds; interoperability of services in federated cyberinfrastructures; and geospatial workflows towards standardization. Work presented in this report is a direct continuation of the Earth Observation & Clouds (EOC) thread of Testbed-14. This report is expected to be of relevance to Testbed-15, both to the Earth Observation Process and Application Discovery (EOPAD) task and the Machine Learning task. This engineering report will describe: relevant work conducted in OGC Testbed-14; ESGF and its compute challenge; adaptations of existing climate processes into workflows; interoperability experiments with ESGF endpoints conforming to a common API. - - + + Schema Maintenance and Tailoring - Tom Landry, David Byrns - 19-003 + + + 05-117 + - - Earth System Grid Federation (ESGF) Compute Challenge + Schema Maintenance and Tailoring + 05-117 + + Description of the schema tailoring process for the application schema development in the decision support services thread (GeoDSS) during the OWS-3 initiative + Clemens Portele + 2006-05-02 - - The OGC Timeseries Profile of Observations and Measurements is a conceptual model for the representation of observations data as timeseries, with the intent of enabling the exchange of such data sets across information systems. This standard does not define an encoding for the conceptual model; however there is an accompanying OGC Standard which defines an XML encoding (OGC TimeseriesML 1.0 - XML Encoding of the Timeseries Profile of Observations and Measurements). Other encodings may be developed in future. - 15-043r3 - Timeseries Profile of Observations and Measurements - 2016-09-09 - 15-043r3 - Timeseries Profile of Observations and Measurements + - - + Web Coverage Service 2.0 Interface Standard - XML/SOAP Protocol Binding Extension + 09-149r1 + Peter Baumann + 09-149r1 + This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using SOAP with XML encoding. + - - - James Tomkins, Dominic Lowe - - - Frédéric Houbie, Philippe Duchesne, Patrick Maué - - - + OGC® Web Coverage Service 2.0 Interface Standard - XML/SOAP Protocol Binding Extension - In this OGC Best Practice, the concept of semantic annotations is introduced. Annotation of Web Services or data compliant to OGC standards refers to the task of attaching meaningful descriptions to the service and the served geospatial data or processes. - Semantic annotations in OGC standards - - Semantic annotations in OGC standards - 08-167r2 - 08-167r2 - 2012-10-10 + 2010-10-27 + - - - - 05-029r4 - GML Point Profile - This document defines a profile of the Geography Markup Language (GML) for a point geometry. Attention is drawn to the fact that this is a profile of GML version 3.1.1. - - 2005-08-29 - - GML Point Profile - 05-029r4 + + - - Ron Lake, Carl Reed, George Percivall - - - - 17-014r9 - 2023-01-11 - Carl Reed, Tamrat Belayneh - - The Indexed 3D Scene Layer (I3S) format is an open 3D content delivery format used to rapidly stream and distribute large volumes of 3D GIS data to mobile, web and desktop clients. I3S content can be shared across enterprise systems using both physical and cloud servers. - -A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files. - -The delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types. - OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.3 + + 08-103r2 + 08-103r2 + CSW-ebRIM Registry Service - Part 3: Abstract Test Suite + + CSW-ebRIM Registry Service - Part 3: Abstract Test Suite + 2009-02-05 + Richard Martell - + + This document is an abstract test suite (ATS): a compendium of abstract test cases pertaining to implementations of the CSW-ebRIM 1.0 catalogue profile. It provides a basis for developing an executable test suite (ETS) to verify that the implementation under test (IUT) conforms to all relevant functional specifications. While passing all of the conformance tests defined in this ATS provides some assurance of overall functional correctness, it cannot guarantee that an implementation is faultless. + + + Topic 05 - Features + 99-105r2 + Cliff Kottman + Topic 5 - Features + + 99-105r2 + 1999-03-24 + A feature object (in software) corresponds to a real world or abstract entity. + - 17-014r9 - OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.3 - + + + - - This discussion paper is organized as follows. + + 17-026r1 + Testbed-13: Disconnected Networks Engineering Report + The design of core OGC Web Services (OWS) does not entertain the possibility of network unavailability, internet unavailability, or disconnected clients and datastores. Deployments of these services, and the clients that consume them, often happen in networking environments that have limited bandwidth, sporadic connectivity and no connection to the internet. This Engineering Report (ER) focuses on situations of Denied, Degraded, Intermittent, or Limited Bandwidth (DDIL). Due to these DDIL networking limitations, OWS services and clients may not be capable of effective data exchange and interpretation due to a reliance on external resources and always-on networks. -Background: This section introduces DLT and blockchain, as well as the structure of blocks. +This ER concerns the behavior of common OWS services when used in DDIL environments. The ER documents proposed practices/considerations for implementation of these services to support these environments. The ER also describes software modules or extensions that might mitigate the effects of these environments on both clients and services. -Case Studies: This section presents an overview of example projects that use or are studying blockchain within a geospatial context. +This ER intends to guide client and service implementation, as well as deployment strategies for these challenging environments. -Current Standardization Initiatives: This section presents an overview of a selection of standardization initiatives involving blockchain and geospatial data. - 2018-10-09 - Geospatial Standardization of Distributed Ledger Technologies - - - 18-041r1 - Geospatial Standardization of Distributed Ledger Technologies + + OGC Testbed-13: Disconnected Networks Engineering Report + + + 2018-02-22 + 17-026r1 + + Rob Cass - Gobe Hobona, Bart De Lathouwer - - 18-041r1 - + - - - 2012-06-12 - 10-157r3 - Earth Observation Metadata profile of Observations & Measurements - Earth Observation Metadata profile of Observations & Measurements - - + + 2003-01-15 + 03-014 + OGC Web Services SOAP Experiment Report - + + 03-014 + OGC Web Services SOAP Experiment Report - This OGC Implementation Standard defines a profile of Observations and Measurements (ISO 19156) for describing Earth Observation products (EO products). -Although this standard has been developed in the context of the Heterogeneous Mission Accessibility (HMA) project initiated by European Space Agency (ESA), the content is generic to Earth Observation product description. The metadata model described in this document is structured to follow the different types of products (Optical, Radar, …) which are not HMA specific. - - Jerome Gasperi, Frédéric Houbie, Andrew Woolf, Steven Smolders - 10-157r3 + This document will discuss how OWS services can be ported to Web Services and highlight various issues/problems that have been discovered and need further discussion. + + + + J - + + Gobe Hobona + 19-077 + 19-077 + OGC Body of Knowledge - Geospatial User Feedback Standard: XML Encoding Extension - 15-098r1 - The Geospatial User Feedback XML encoding standard is based on the OGC Geospatial User Feedback conceptual model [OGC 15-097]. Geospatial User Feedback (GUF) is metadata that is predominantly produced by the consumers of geospatial data products based on their use and experience with those products. This standard complements the existing metadata conventions whereby documents recording dataset characteristics and production workflows are generated by the creator, publisher, or curator of a data product. As a part of metadata, the GUF data model internally reuses some elements of ISO 19115-1 (the updated version of the OGC Abstract Specification Topic 11) but not the general structure. This selective use of ISO metadata elements prioritizes future interoperability with developing ISO metadata models. -This standard can be used in combination with the OGC 15-097 Conceptual Model Standard. In the future, other encodings may be considered, being an alternative using the JSON-LD encoding based on parts of schema.org. - - 2016-12-22 + OGC Body of Knowledge - Version 0.1 - Discussion Paper - - 15-098r1 - OGC® Geospatial User Feedback Standard: XML Encoding Extension - + The OGC Body of Knowledge is a structured collection of concepts and related resources that can be found in the OGC library. It is, in effect, a view of explicit knowledge available from the OGC Virtual Knowledge Store and related components such as the OGC Definitions Server and the OGC Glossary of Terms. The OGC Body of Knowledge is intended to provide a reference for users and developers of geospatial software. This discussion paper describes the approach taken to develop the OGC Body of Knowledge and presents the results of the approach. It is intended to encourage and facilitate discussion within the OGC membership and wider geospatial community. + - Joan Masó, Lucy Bastin - + + + 2020-05-04 - - - - 2010-10-07 - 10-099r2 - 10-099r2 - Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0 - - Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0 - Panagiotis (Peter) A. Vretanos - This document provides revision notes for version 2.0 of the OpenGIS® Implementation Specification Geography Markup Language (GML) simple feature profile. - + + 2010-10-12 + + 10-171 + Sensor Instance Registry Discussion Paper + + This Discussion paper introduces the Sensor Instance Registry (SIR), a web service interface for managing the metadata and status information of sensors. Furthermore this service is capable of automatically harvesting sensor metadata, transforming the collected metadata sets into a data model compatible to OGC Catalogs and to push harvested metadata into OGC Catalog instances. + Sensor Instance Registry Discussion Paper + + 10-171 + Simon Jirka, Daniel Nüst - - - This report shall focus on evaluating the ability to: - -- Serve, filter and update AIXM 5.1 data via the OGC WFS-T 2.0 interface -- Recommend guidelines or cross-walks for interpreting the new AIXM 5.1 schedules in conjunction with the Timeslice model in a web services environment - - 2010-08-18 + + - + Samantha Lavender + + 2020-10-22 + OGC Earth Observation Applications Pilot: Pixalytics Engineering Report + - 10-131r1 - 10-131r1 - OWS-7 Aviation - AIXM Assessment Report - OWS-7 Aviation - AIXM Assessment Report - Debbie Wilson + This is an individual Engineering Report (ER) created by Pixalytics Ltd as part of the Earth Observation Applications Pilot. Pixalytics' role was that of an App developer, testing deployment to the OGC Earth Observation Applications Pilot architecture. + 20-037 + OGC Earth Observation Applications Pilot: Pixalytics Engineering Report + + 20-037 - + + + 16-027 + Testbed-12 Web Service Implementation Engineering Report - + 2017-05-12 + Testbed-12 Web Service Implementation Engineering Report + Johannes Echterhoff, Clemens Portele + This document is a deliverable of the OGC Testbed-12. It describes the results of analyzing the Testbed-12 web service implementations. + +OGC has been developing web service specifications since the OGC Web Mapping Testbed in 1999. In particular, the original OGC Web Map Service specification has been developed during that testbed. 17 years later most current OGC web service standards still follow the general approach that had been developed in 1999 (the capabilities document, the remote procedure call via HTTP paradigm, etc). + +Over time, the OGC web service approach has been amended and extended in different ways by different OGC standards and profiles. In addition, some of the more flexible mechanisms have been used in practice in different ways by different software vendors or communities. The OGC Web Service Common standard had been a response by OGC to these developments and aimed at maintaining a consistent approach across the different OGC web service standards. However, this effort has been only partially successful for several reasons, including shortcomings in the OWS Common standard, the existence of multiple incompatible OWS Common versions and a reluctance by working groups and communities to introduce incompatible changes to existing service types in order to harmonize. All attempts in recent years to continue the work on OWS Common have not seen much traction. While there seems to be general agreement that the current situation is not optimal and that consistency is desirable, it is unclear how to improve in a way that meets market demands. + +This document summarizes information about the web service implementations in Testbed-12. It is not and should not be understood as a general analysis or assessment of the OGC web service architecture, but a low-key effort to gain some insights from looking at a significant number of web service implementations and their use in interoperability experiments and demos. + +During the years since 1999 not only the OGC standards baseline has evolved, but also the Web itself. The W3C has been working on identifying Best Practices for Data on the Web and W3C and OGC are jointly working on extending this with Best Practices for Spatial Data on the Web. The analysis also includes an assessment about the OGC approach to web services with respect to the draft best practices at the time of writing of this report. + +To the extent possible, we draw conclusions and recommendations from the information that has been gathered. These fall into three categories: + +Improving the interoperability of OGC web services as they are today + +Support for new requirements in a consistent way across service types + +Improvements to the standardization process + +In addition, there is also a specific case that does not fit into these general categories. + 16-027 + + - 2002-10-18 - 02-039r1 - Web Pricing and Ordering - - This specification covers all standard geo-eBusiness processes like pricing, ordering and online delivery for spatial products. - Roland Wagner - 02-039r1 - Web Pricing and Ordering - - - CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW - 07-110r2 - CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW - Richard Martell - 07-110r2 - 2008-03-11 + + OpenGIS Geography Markup Language (GML) Encoding Standard - with corrigendum + 2018-04-14 + 07-036r1 + Geography Markup Language (GML) Encoding Standard - with corrigendum + Clemens Portele - - This profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0.2 specification; it qualifies as a 'Class 2' profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards. - - + 07-036r1 + + + + The OpenGIS® Geography Markup Language Encoding Standard (GML) The Geography Markup Language (GML) is an XML grammar for expressing geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. As with most XML based grammars, there are two parts to the grammar – the schema that describes the document and the instance document that contains the actual data. +A GML document is described using a GML Schema. This allows users and developers to describe generic geographic data sets that contain points, lines and polygons. However, the developers of GML envision communities working to define community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas] that are specialized extensions of GML. Using application schemas, users can refer to roads, highways, and bridges instead of points, lines and polygons. If everyone in a community agrees to use the same schemas they can exchange data easily and be sure that a road is still a road when they view it. + +Clients and servers with interfaces that implement the OpenGIS® Web Feature Service Interface Standard[http://www.opengeospatial.org/standards/wfs] read and write GML data. GML is also an ISO standard (ISO 19136:2007) [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32554 ]. + - - Sensor Planning Service Application Profile for EO Sensors - 07-018r1 - - - 2007-08-15 + + 2023-05-11 + + Technical Committee Policies and Procedures - 07-018r1 - OpenGIS Sensor Planning Service Application Profile for EO Sensors - This SPS EO profile document specifies at a lower level the interfaces and parameters for requesting information describing the capabilities of a Sensor Planning Service dedicated to the EO Sensor domain, for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or cancelling such a request, and for requesting information about further OGC Web services that provide access to the data collected by the requested task. - - Philippe M - + Technical Committee Policies and Procedures + 05-020r29 + + The OGC provides a collaborative, consensus process for developing and approving open, international Standards and supporting content for the geospatial domain, collectively known as OGC Products. To guide the OGC Product development and approval process, a member-approved Policies and Procedures document for the Technical Committee (TC) is required. + +This document describes the TC Policies and Procedures (TC PnP). The TC has been granted authority to operate by the OGC Bylaws. The TC is composed of individuals representing organizations that are duly recognized members in good standing of the OGC. + +As the needs and purpose of the TC change, changes to these policies and procedures are approved by an electronic vote of the Voting Members of the OGC TC. These policies and procedures may be augmented or clarified by Policy Directives issued and approved by the TC or the Executive Planning Committee (EPC). Such directives are databased and hyperlinked to/from the appropriate portion of this document. + + 05-020r29 + + Scott Simmons - - 2021-01-13 - OGC Testbed-16: DGGS and DGGS API Engineering Report - Robert Gibb, Byron Cochrane, Matthew Purss - 20-039r2 - - 20-039r2 - DGGS and DGGS API Engineering Report + + + OGC® GeoPackage Encoding Standard - with Corrigendum + 12-128r15 + 12-128r15 + This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. + - + 2018-09-06 + Jeff Yutzler - This OGC Testbed-16 Engineering Report (ER) documents the needs and key requirements for drafting an OGC Discrete Global Grid Systems (DGGS) Application Programming Interface (API) standard. The draft DGGS API is defined using the OpenAPI 3.0 specification. The work documented in this ER represents the beginning of a multi-initiative process to fully realize the benefits of standards compliant DGGS implementations and to help drive adoption of DGGS as a key element in advanced Spatial Data Architectures. The Testbed participants investigated a Client-Server DGGS architecture involving one (or more) DGGS Server implementations, DGGS-enabled Data Sources and a simple front-end DGGS Client. DGGS API functionality will be tested using one (or more) simple use case scenarios focusing on the two-way translation between geographic locations and DGGS Zonal Identifiers. + OGC® GeoPackage Encoding Standard - with Corrigendum + + + + + + Geospatial to the Edge Plugfest Engineering Report + 18-084 + The Geospatial to the Edge Interoperability Plugfest, co-sponsored by the Army Geospatial Center and the National Geospatial-Intelligence Agency (NGA/CIO&T), brought together technology implementers and data providers to advance the interoperability of geospatial products and services based on profiles of OGC standards. Specifically, servers and data available via GeoPackage, Web Feature Service (WFS), Web Map Service (WMS), and Web Map Tile Service (WMTS), all following National System for Geospatial Intelligence (NSG) profiles, were exercised and improved in various clients. Compliance Tests were executed and advanced based on feedback from the participants. + + + OGC Geospatial to the Edge Plugfest Engineering Report + Luis Bermudez + + 18-084 + 2019-01-20 - - This document details considerations for using the WPS specification to define a standard coordinate transformation service. - - OWS-5 Considerations for the WCTS Extension of WPS - - 2008-08-20 - 08-054r1 - Max Martinez + + 2022-08-19 + Catalogue services are the key technology for locating, managing and maintaining +distributed geo-resources (i.e. geospatial data, applications and services). With OGC +catalogue services, client applications are capable of searching for geo-resources in a +standardized way (i.e. through standardized interfaces and operations) and, ideally, they +are based on a well-known information model, which includes spatial references and +further descriptive (thematic) information that enables client applications to search for +geo-resources in very efficient ways. +Whereas interfaces and operations of OGC catalogue services are well defined, it is left +up to the developer of the system to define a specific information model which a +catalogue service instance provides. This includes, but is not limited to, the information +which can be inserted in the catalog, supported query languages, available search terms, +response/result sets, etc. This point is of major importance with respect to interoperability +between different catalogue service instances. +In Europe, running catalogue instances result from work being done within different SDI +initiatives (e.g. SDI NRW Initiative1, Germany/Netherlands cross-border initiative, JRC +EU Portal, EUROSTAT, Inspire, German SDI initiative). Members of these initiatives +have developed an ISO-based application profile for ISO19115 metadata for +geodata/geospatial applications and ISO19119-based metadata for tightly and looselycoupled +geospatial services. The foundations of this profile were the OGC catalogue +specification (1.1.1), the OGC Web Registry Server (WRS) 0.0.2, OGC Web Services +Stateless Catalogue Profile (StCS) 0.0.6 and ISO 19115/19119 for content description. +OGC's catalogue revision working group (CS-RWG) has revised and integrated the +catalogue implementation specification v1.1.1 that have resulted in CS 2.0.2. One part of +this OGC specification comprises the definition of application profiles according to ISO +19106 (Geographic information – Profiles). The overall goal of these profiles is to +improve interoperability between systems conforming to a specific profile. Experience +has shown that the need for application profiles results from the fact that in practice, there +is no single solution for catalogue services that fits every user’s needs. As stated in CS +2.0.2, a base profile that provides a basic set of information objects has to be supported +by each catalogue instance; in addition, application profiles for different information +communities can be specified. +Hence, this document specifies an application profile for ISO 19115:2003/ISO +19119:2005 metadata with support for XML encoding per ISO/TS19139:2007 [ISO/TS19139]2 and HTTP protocol binding. It relies on requirements coming from the +CS/CSW 2.0 specification (OGC CS 2.0.2, OGC document 07-006). The application +profile will form the basis of conformance tests and reference implementations. + OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum + + + Uwe Voges, Kristian Senkler + 07-045r2 + OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum + 07-045r2 + + + + + + David Blodgett, Irina Dornblut + OGC® WaterML 2: Part 3 - Surface Hydrology Features (HY_Features) - Conceptual Model + The OGC Surface Hydrology Features (HY_Features) standard defines a common conceptual information model for identification of specific hydrologic features independent of their geometric representation and scale. The model describes types of surface hydrologic features by defining fundamental relationships among various components of the hydrosphere. This includes relationships such as hierarchies of catchments, segmentation of rivers and lakes, and the hydrologically determined topological connectivity of features such as catchments and waterbodies. The standard also defines normative requirements for HY_Features implementation schemas and mappings to meet in order to be conformant with the conceptual model. + +The HY_Features model is based on an abstract catchment feature type that can have multiple alternate hydrology-specific realizations and geometric representations. It supports referencing information about a hydrologic feature across disparate information systems or products to help improve data integration within and among organizations. The model can be applied to cataloging of observations, model results, or other study information involving hydrologic features. The ability to represent the same catchment, river, or other hydrologic feature in several ways is critical for aggregation of cross-referenced or related features into integrated data sets and data products on global, regional, or basin scales. + 14-111r6 + WaterML 2: Part 3 - Surface Hydrology Features (HY_Features) - Conceptual Model + 2018-01-08 - - OWS-5 Considerations for the WCTS Extension of WPS - 08-054r1 + 14-111r6 + + + + - - Stephane Fellah - - - Testbed-11 Symbology Mediation - 15-058 - 15-058 - OGC® Testbed-11 Symbology Mediation - This OGC® Engineering Report (ER) summarizes the approaches, findings and the results of the Symbology Mediation sub-thread activities of the OGC Testbed-11 Cross Community Interoperability (CCI) Thread. The ER: -• Provides an overview of existing standards relevant to symbology mediation, -• Outlines the approaches adopted during the testbed, -• Describes the conceptual models and services developed during the testbed to address semantic mediation and portrayal of feature information related to Emergency Management and to some extent to the Aviation domain. - - - 2015-11-18 + + This document describes the Open Geospatial Consortium (OGC) Compliance Testing Program. The document describes the roles and responsibilities, compliance testing procedures, development of test packaging, and policies for developing and releasing the software used for testing for compliance to OGC Standards. + 2022-06-28 + 08-134r11 + Compliance Testing Program Policies & Procedures + 08-134r11 + + + Compliance Testing Program Policies & Procedures + Gobe Hobona - - - - - + - - OGC® Moving Features Encoding Part I: XML Core - 2015-02-17 - Moving Features Encoding Part I: XML Core - 14-083r2 - This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange. - 14-083r2 - Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf - - - - The purpose of this Met Ocean profile of WCS2.1 is to define the metadata returned in the response documents resulting from the WCS2.1 operations: GetCapabilities, and DescribeCoverage; for use within the meteorological and oceanographic communities. It also defines the new operation DescribeCoverageCollection. - -This work has been done by members of the OGC MetOcean Domain Working Group. - OGC MetOcean Application profile for WCS2.1: Part 0 MetOcean Metadata - Peter Trevelyan, Paul Hershberg, Steve Olson - - 15-045r7 - + + + + 20-043 + OGC Earth Observation Applications Pilot: EOX-Sinergise-DLR-UVT-Terrasigna Engineering Report + + Stefan Achtsnit, Joachim Ungar, and Stephan Meißl (EOX), Anja Vrecko and Grega Milčinski (Sinergise) - + This Engineering Report documents findings, achievements, and learnings gained through activities during the OGC Earth Observation (EO) Applications Pilot by the EOX team (EOX, DLR, UVT, Sinergise, and Terrasigna). Both perspectives, from application developer’s as well as from platform provider’s view, are represented here. - 15-045r7 - MetOcean Application profile for WCS2.1: Part 0 MetOcean Metadata - 2021-03-22 + 2020-10-22 + 20-043 + OGC Earth Observation Applications Pilot: EOX-Sinergise-DLR-UVT-Terrasigna Engineering Report - - - 10-126r3 - WaterML 2.0: Part 1- Timeseries + + + Raj Singh + + 2014-04-28 + 10-002 + Climate Challenge Integration Plugfest 2009 Engineering Report + 10-002 + - This document is an OGC® Encoding Standard for the representation of hydrological observations data with a specific focus on time series structures. WaterML2.0 is implemented as an application schema of the Geography Markup Language version 3.2.1, making use of the OGC Observations & Measurements standards. -WaterML2.0 is designed as an extensible schema to allow encoding of data to be used in a variety of exchange scenarios. Example areas of usage are: exchange of data for operational hydrological monitoring programs; supporting operation of infrastructure (e.g. dams, supply systems); cross-border exchange of observational data; release of data for public dissemination; enhancing disaster management through data exchange; and exchange in support of national reporting. -The core aspect of the model is in the correct, precise description of time series. Interpretation of time series relies on understanding the nature of the process that generated them. This standard provides the framework under which time series can be exchanged with appropriate metadata to allow correct machine interpretation and thus correct use for further analysis. Existing systems should be able to use this model as a conceptual 'bridge' between existing schema or systems, allowing consistency of the data to maintained. + + This OGC Engineering Report (ER) documents findings of the CCIP 2009 Plugfest, which was conducted via the public Internet to address requirements stated in the CCIP Call for Participation . It addresses concept development, specifications tested, and interoperability experiments conducted. The ER concludes with issues that arose, and provides recommendations for the refinement of OGC Specifications and the Plugfest process. Recommendations in this ER will be considered in the planning of future activities. +OGC expresses thanks to the Australian Bureau of Meteorology and to CSIRO for sponsoring CCIP 2009. - 10-126r3 + OGC® Climate Challenge Integration Plugfest 2009 Engineering Report + + + Earth Observation Metadata profile of Observations & Measurements + Jerome Gasperi, Frédéric Houbie, Andrew Woolf, Steven Smolders + + 10-157r3 + Earth Observation Metadata profile of Observations & Measurements + 10-157r3 + + This OGC Implementation Standard defines a profile of Observations and Measurements (ISO 19156) for describing Earth Observation products (EO products). +Although this standard has been developed in the context of the Heterogeneous Mission Accessibility (HMA) project initiated by European Space Agency (ESA), the content is generic to Earth Observation product description. The metadata model described in this document is structured to follow the different types of products (Optical, Radar, …) which are not HMA specific. + - - OGC® WaterML 2.0: Part 1- Timeseries - 2012-08-30 - Peter Taylor - - + 2012-06-12 - Testbed-11 Test and Demonstration Results for NIEM using IC Data Encoding Specifications Engineering Report - 15-050r3 - 15-050r3 - OGC Testbed-11 Test and Demonstration Results for NIEM using IC Data Encoding Specifications Engineering Report - 2016-01-25 - Jeff Harrison - - - The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community -(IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0 -architecture through the development, implementations, test, and robust demonstration -making use of IC specifications, Geography Markup Language (GML), and NIEM in a -simulated “real-world” scenario. The demonstration scenario begins with NIEMconformant -Information Exchange Packages (IEPs) containing operational data and IC -security tags from the Information Security Marking (ISM) and Need-To-Know (NTK) -access control metadata, and the Trusted Data Format (TDF) for binding assertion -metadata with data resource(s). Those instance documents are deployed using Open -Geospatial Consortium (OGC) standards enabled Web Services for use by client -applications. Access control is based on attributes of the end-user and the instance data. -Recommendations to update these information exchanges were provided to reflect NIEM -3.0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment tested -this data encoding in OGC Web Feature Services (WFS) and Policy Enforcement Points -(PEP) accessed by multiple client applications. Results from this task provided a -preliminary architecture that was tested and demonstrated in Testbed 11, and summarized -in other OGC Testbed 11 Engineering Reports. The demonstrations also highlighted how -NIEM and IC data encodings together may support more agile and customer-centric -frameworks driven by collaborative partnerships. This transformation is vital to -confronting the security challenges of the future. - - - - 18-005r8 - Roger Lott - This document is consistent with the third edition (2019) of ISO 19111, Geographic Information - Referencing by coordinates including its amendments 1 and 2. ISO 19111:2019 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics, in close collaboration with the Open Geospatial Consortium (OGC). It replaces the second edition, ISO 19111:2007 and also ISO 19111-2:2009, OGC documents 08-015r2 and 10-020. This OGC document, 18-005r5, incorporates three editorial corrections made in ISO 19111:2019 amendment 1 of 2021. - + + + Thomas H.G. Lankester + OpenGIS Web Map Services - Application Profile for EO Products + 06-093 + Web Map Services - Application Profile for EO Products + 06-093 + - Topic 2 - Referencing by coordinates (Including corrigendum 1 and corrigendum 2) - Topic 02 - Referencing by coordinates - 18-005r8 - - 2023-09-05 - + + 2006-10-24 + The WMS configuration proposed in this profile is intended to support the interactive visualization and evaluation of Earth Observation (EO) data products. The profile sets out to describe a consistent Web Map Server (WMS) configuration that can be supported by many data providers (satellite operators, data distributors...), most of whom have existing (and relatively complex) facilities for the management of these data. - - 2014-12-30 - Peter Taylor - - WaterML2.0 part 2 – rating tables, gauging observations and cross-sections: Interoperability Experiment Results - 14-114r1 - 14-114r1 - WaterML2.0 part 2 – rating tables, gauging observations and cross-sections: Interoperability Experiment Results - + + 22-023r2 + Testbed-18: Features Filtering Summary Engineering Report + + + This OGC Testbed-18 (TB-18) Features Filtering Summary Engineering Report (ER) summarizes the implementations, findings, and recommendations that emerged from the efforts to better understand the current OGC API-Features filtering capabilities and limitations and how filtering can be decoupled from data services. + +This ER describes: + +* two façades built to interface SWIM services and serve aviation data through APIs (built with OGC API Standards) including basic filtering capabilities; +* the two filtering services built to consume SWIM data and serve it through OGC based APIs featuring advanced filtering mechanism; +* the client application built to interface with the filtering services; and +* the developer client built to define filter statements that can be expressed in a machine-readable way and exchanged with the filtering service. + 2023-07-14 + 22-023r2 + + + Testbed-18: Features Filtering Summary Engineering Report + Sergio Taleisnik - + + + Topic 2.1 - Spatial Referencing by Coordinates - Extension for Parametric Values + + 2014-04-16 + Topic 02.1 - Spatial Referencing by Coordinates - Extension for Parametric Values + 10-020 + + + 10-020 + Paul Cooper + + + - Part 1 of WaterML2.0 covers exchange of hydrological time-series data, the observational processes used to generate them, and information related to the monitoring points (stations/sites) where time-series data are typically collected. WaterML2.0 Part 2, is a candidate standard that defines how to exchange rating tables, gauging observations and cross-sections in an interoperable manner. -This engineering report outlines the design and results of an OGC Interoperability Experiment (IE) that implemented and tested the current WaterML2.0 part 2 information model. The OGC IE experiment ran was conducted from November 2013 to August 2014. The use case for the IE involved exchange of data in three scenarios in Australia, US and the UK. -This report describes the software requirements, design, deployments and challenges faced by the experiment. The results were used to improve the WaterML2.0 part 2 information model and provided the basis for the formation of an OGC Standards Working Group (SWG) in August 2014. This SWG is responsible for formalization of the candidate OGC standard, for submission in 2015. - - + + 11-157 + Jim Greenwood + + 2011-10-18 + + Corrigendum 1 for OGC Web Services Common Standard v2.0.0 - Multilingual + + This document being corrected specifies many of the aspects that are, or should be, common to all or multiple OWS interface Implementation Specifications. The Common Implementation Specification aspects specified by this document currently include: +a) Operation request and response contents, most partial +b) Parameters and data structures included in operation requests and responses c) XML and KVP encoding of operation requests and responses + + Corrigendum 1 for OGC Web Services Common Standard v2.0.0 - Multilingual + 11-157 - - + + + - 15-113r3 - Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure - 2017-02-23 - 15-113r3 - Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure - The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. -The application of CDB to future simulation architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the High Level Architecture - -Federation Object Model (HLA/FOM) and DIS protocols, the application of the CDB standard provides a Common Environment to which inter-connected simulators share a common view of the simulated environment. -The CDB standard defines an open format for the storage, access and modification of a synthetic environment database. A synthetic environment is a computer simulation that represents activities at a high level of realism, from simulation of theaters of war to factories and manufacturing processes. These environments may be created within a single computer or a vast distributed network connected by local and wide area networks and augmented by super-realistic special effects and accurate behavioral models. SE allows visualization of and immersion into the environment being simulated . -This standard defines the organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The standard makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. A series of associated OGC Best Practice documents define rules and guidelines for data representation of real world features. -The CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. A CDB data store can include terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the data store can includes the specific attributes of the synthetic environment data as well as their relationships. -The associated CDB Standard Best Practice documents provide a description of a data schema for Synthetic Environmental information (i.e. it merely describes data) for use in simulation. The CDB Standard provides a rigorous definition of the semantic meaning for each dataset, each attribute and establishes the structure/organization of that data as a schema comprised of a folder hierarchy and files with internal (industry-standard) formats. -A CDB conformant data store contains datasets organized in layers, tiles and levels-of-detail. Together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB compliant data store is specifically tailored for real-time applications. - - - Carl Reed + + + + + Ben Domenico + 2012-10-02 + 11-038R2 + 11-038R2 + OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard + OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard + This standard deals with enhancements to the netCDF (Network Common Data Form) data model for array-oriented scientific data.. +Two important data models for netCDF are: +- the “classic” netCDF model, used for netCDF-3 and earlier versions +- an enhanced data model, used in netCDF-4 and later versions. +The netCDF classic data model is defined in OGC 10-091r3, “NetCDF Core.” +This document specifies a netCDF extension standard for the enhanced data model. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space- and time-varying phenomena. +NetCDF (network Common Data Form) is a data model for array-oriented scientific data. The netCDF classic data model is specified in the netCDF core specification. This standard specifies the enhanced data model. A freely distributed collection of access libraries implementing support for that data model in a machine-independent format are available. Together, the interfaces, libraries, and format support the creation, access, and sharing of multi-dimensional scientific data. - - Tatjana Kutzner, Carl Stephen Smyth, Claus Nagel, Volker Coors, Diego Vinasco-Alvarez, Nobuhiro Ishi - City Geography Markup Language (CityGML) Part 2: GML Encoding Standard - 21-006r2 - This Standard documents the OGC GML Implementation Specification (IS) for the CityGML 3.0 Conceptual Model. The CityGML 3.0 conceptual model is a Platform Independent Model (PIM). It defines concepts in a manner which is independent of any implementing technology. As such, the CityGML Conceptual Model cannot be implemented directly. Rather, it serves as the base for Platform Specific Models (PSM). A PSM adds to the PIM the technology-specific details needed to fully define the CityGML model for use with a specific technology. The PSM can then be used to generate the schema and other artifacts needed to build CityGML 3.0 implementations. - -This standard defines the PSMs and schemas for the CityGML 3.0 Implementation Specification (IS) for Geography Markup Language (GML) implemenations. The GML schemas are explained in an overview and design decisions that have been made are documented as well. - + + 18-001r1 + GeoDCAT-AP + Improving discoverability of open geo-data and information is vital to increasing the use of these data in- and outside the geospatial expert community. +In this document we start to compare existing metadata standards, e.g., Dublin Core, ISO 19115/57/19, and INSPIRE, in the geospatial- and open data context. We also describe related linked open data initiatives such as RDF, SPARQL, and metadata publication initiatives, e.g., schema.org and Atom feeds. GeoDCAT is an initiative with the potential to integrate DCAT metadata as they are used in the open data and e-government community with EN ISO 19115/57/19 standards and INSPIRE metadata as they are used in the Geospatial community. GeoDCAT has - because it is based on RDF- the ability to publish metadata directly on the web without open and geospatial data portals. +To respond to the interest of different communities to preserve geospatial metadata resources and to support the uptake of GeoDCAT-AP implementations, best practices from different countries were identified and studied. The best practice cases focus on four domains (focus areas): metadata input (manually or automatically harvested), metadata publication into an integrated geo/open data portal, publication of metadata as Linked Open Data (LOD), and information mapping (ISO 19115, INSPIRE, DCAT, etc.). +GeoDCAT-AP is a mature solution for mapping metadata from the open data and geospatial domain. GeoDCAT helps to integrate and to publish metadata in data portals and directly on the world wide web. To conclude a GeoDCAT alignment exercise has been done with ISO 19115/19 and INSPIRE to improve the open data and geospatial metadata alignment in the future. - + 2019-01-09 + 18-001r1 - - - 21-006r2 + - - OGC City Geography Markup Language (CityGML) Part 2: GML Encoding Standard - 2023-06-20 + Lieven Raes, Danny Vandenbroucke, Tomas Reznik + + + + GeoDCAT-AP - - OWS-7: Summary of the OGC Web Services, Phase 7 (OWS-7) Interoperability Testbed - 10-094 - David Arctur + + + + 2020-08-28 + 17-087r13 + + + + This document is the ISO 19107:2019 Standard and specifies conceptual schemas for describing the spatial characteristics of geographic entities, and a set of spatial operations consistent with these schemas. It treats vector geometry and topology. + Topic 01 - Spatial schema + 17-087r13 + Topic 1 - Spatial schema + John R. Herring + + + + Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes - 10-094 - - The OGC Web Services, Phase 7 (OWS-7) Testbed was an initiative of OGC’s Interoperability Program to collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. - - - OWS-7: Summary of the OGC Web Services, Phase 7 (OWS-7) Interoperability Testbed - 2010-10-22 + 16-005r2 + + + Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes + 16-005r2 + + Carl Reed + 2017-02-23 + This document provides the Annexes for the CDB Core: Model and Physical Structure standard. The only exception is Annex A, Abstract Test Suite. The CDB ATS Annex is in Volume 1: Core document. - - OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.2 - 17-014r8 + - - 2021-12-15 - 17-014r8 - - The Indexed 3D Scene Layer (I3S) format is an open 3D content delivery format used to rapidly stream and distribute large volumes of 3D GIS data to mobile, web and desktop clients. I3S content can be shared across enterprise systems using both physical and cloud servers. - -A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files. - -The delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types. - -The open community GitHub source for this Community Standard is here. - - Carl Reed, Tamrat Belayneh - OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.2 + A GeoVideo Web Service (GVS) is a web service that facilitates the viewing of live and/or archived feeds from video cameras. The feeds may be composed of: +- A video stream +- Textual data in a caption stream (e.g. GPS data, camera states and characteristics, custom XML data, such as SensorMLTML) +- A combination of a video stream and associated textual data +The video streams of the feed may be viewed in the Windows Media Player. The textual data is extracted through scripting events that are generated as the caption stream is processed and displayed by the Windows Media Player. + Geo Video Web Service + 05-115 + + + + 05-115 + Geo Video Web Service + 2006-03-28 + Joe Lewis - - - - - - - - - - + + + This document defines an extension to the GeoXACML Implementation Specification, Verison 1.0 for the GML2 geometry encoding as specified in the GML2 standard. + 2008-02-23 + Andreas Matheus + GeoXACML Implementation Specification - Extension A (GML2) Encoding + + 07-098r1 + GeoXACML Implementation Specification - Extension A (GML2) Encoding + + + 07-098r1 - Documents of type Implementation Standard Extension - Documents of type Implementation Standard Extension - Documents of type Implementation Standard Extension + - + + 12-066 + + 2014-01-31 + 2012-07-12 + Modeling an application domain extension of CityGML in UML + This paper presents key aspects of the development of a Dutch 3D standard IMGeo as a CityGML ADE. The new ADE is modeled using UML class diagrams. However the OGC CityGML specification does not provide clear rules on modeling an ADE in UML. This paper describes how the extension was built, which provides general insight how CityGML can be extended for a specific applications starting from the UML diagrams. Several alternatives for modeling ADEs in UML have been investigated and compared. The best suited for the 3D standard option is selected and applied. Open issues and challenges are discussed in the conclusions. + - OpenGIS Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW - 05-025r3 - Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW - 05-025r3 - - 2006-10-24 - Richard Martell + - - The OGC Catalogue Services 2.0 specification (OGC 04-021r3) establishes a general framework for implementing catalogue services that can be applied to meet the needs of stakeholders in a wide variety of domains. This application profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0 specification; it qualifies as a Class 2 profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards. - + + + + Modeling an application domain extension of CityGML in UML + 12-066 + Linda van den Brink, Jantien Stoter, Sisi Zlatanova - - 23-025 - 2023 Open Standards and Open Source Software Code Sprint Summary Engineering Report - 23-025 - + + This approved OGC Implementation Standard defines a Simple Features profile of the Geography Markup Language version 3.2. This Simple Features Profile has been aligned with the OGC Simple Features standard for SQL version 1.2. Simple Features include: Point, Curve (LineString), Surface (Polygon), Geometry, MultiPoint, MultiCurve, MultiSurface, and MultiGeometry. The detailed abstract model for OGC features and geometry can be found in the OGC Abstract Specification, Topic Volume 1: Features (which is equivalent to ISO 19107). + +This Simple Features profile of GML began as a product of OGC’s Interoperability Program: a global, collaborative, hands-on engineering and testing program designed to deliver prototype technologies and proven candidate standards into the OGC’s Specification Development Program. In OGC Interoperability Initiatives, international teams of technology providers work together to solve specific geo-processing interoperability problems posed by Initiative. + + Geography Markup Language (GML) simple features profile (with Corrigendum) + 10-100r3 + 10-100r3 + Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos + 2011-05-11 + - - The subject of this Engineering Report (ER) is a code sprint that was held from the 25th to the 27th of April 2023 to advance support of open geospatial standards within the developer community, while also advancing the standards themselves. The code sprint was organized by the Open Geospatial Consortium (OGC), the Open Source Geospatial Foundation (OSGeo), and the Apache Software Foundation (ASF). The code sprint was sponsored by the Ordnance Survey and hosted by Camptocamp. - - Gobe Hobona, Joana Simoes, Tom Kralidis, Martin Desruisseaux, Angelos Tzotsos - - 2023-11-01 - 2023 Open Standards and Open Source Software Code Sprint Summary Engineering Report + + Geography Markup Language (GML) simple features profile (with Corrigendum) + + - - - Currently, most OGC standards focus on data that is observed on the ground or directly above planet Earth. Other standards, such as GeoSciML, provide a data model and transfer standard for geological data. Other projects have considered data models and exchange standards for the seas and oceans. Extra-terrestrial space and the exact location of remote spaceborne sensors has been less in focus. This OGC Testbed 18 Engineering Report (ER) starts with an evaluation of current standards and then proposes changes or extensions to those standards in order to describe objects in orbit around any celestial body or in free flight in our solar system with respect to their location, trajectory, and orientation. Finally standard-based mechanisms to transform a location within a reference frame to a location within another reference frame are examined. - - 2023-03-09 + + 2011-03-22 + 10-194r3 + This report describes the methods, results, issues and recommendations generated by the +Groundwater Interoperability Experiment (GWIE). As an activity of the OGC Hydrology +Domain Working Group (HDWG), the GWIE is designed to: (1) test the use of +WaterML2 with the SOS interface, and Groundwater ML (GWML) with the WFS +interface, (2) test compatibility with software clients, and (3) facilitate sharing of massive +volumes of sensor-based water level observations and related water well features across +the Canada and United States border. + + OGC® Groundwater Interoperability Experiment FINAL REPORT - 22-038r2 - Testbed-18: Reference Frame Transformation Engineering Report - 22-038r2 - Testbed-18: Reference Frame Transformation Engineering Report - Martin Desruisseaux + Groundwater Interoperability Experiment FINAL REPORT + 10-194r3 + + Boyan Brodaric, Nate Booth - - 17-084r1 - - EO Collection GeoJSON(-LD) Encoding - 17-084r1 - JavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. GeoJSON [NR2] is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. This OGC Best Practice describes a GeoJSON [NR2] and JSON-LD [NR13] encoding for Earth Observation (EO) metadata for collections (dataset series). This standard can be applied to encode metadata based on the OGC 11-035r1 [OR20] or ISO19139 [OR27], ISO19139-2 [OR28] specifications, or as an encoding of the Unified Metadata Model for Collections (UMM-C) conceptual model [OR2]. - -The GeoJSON encoding defined in this document is defined as a compaction1 through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF/XML [OR11] and RDF Turtle [OR12]. - -This document makes no assumptions as to the “service” interfaces through which the metadata are accessed and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful Architecture. - -GeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features. - -JSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR7] which allows validation of instances against these schemas. - Y. Coene, U. Voges, O. Barois + + 2021-12-13 + Johannes Echterhoff, Julia Wagemann, Josh Lieberman + 21-023 + Earth Observation Cloud Platform Concept Development Study Report - - 2021-04-21 - - EO Collection GeoJSON(-LD) Encoding + 21-023 + + Earth Observation Cloud Platform Concept Development Study Report + + + The Earth Observation Cloud Platform Concept Development Study (CDS) evaluates the readiness of satellite data providers and cloud service providers, as well as the maturity of their current systems, with regard to real-world deployment of the new “Applications-to-the-Data” paradigm, using cloud environments for EO data storage, processing, and retrieval. - - - - OGC Testbed-15: Federated Clouds Analytics Engineering Report - 19-026 - This OGC Engineering Report (ER) documents the results and experiences resulting from the Federated Cloud Analytics task of OGC Testbed-15. More specifically, this ER provides an analysis of: - -The potential for the OGC Web Processing Service (WPS) Interface Standard as an Application Programming Interface (API) to a workflow automation service for managing job execution involving multiple containers in the Scale Data Center Environment; - -Using an implementation of the OGC WPS standard as a general frontend to workflow automation with containers; - -The suitability of the OGC WPS 2.0 standard as an API for Cloud analytics; - -Using OGC Web Services (WS) as analytics data sources and sinks. - Pedro Gonçalves - - - 2019-12-19 + + + 04-013r4 + A URN namespace for the Open Geospatial Consortium (OGC) + 04-013r4 + - - - OGC Testbed-15: Federated Clouds Analytics Engineering Report - 19-026 + + + 2004-09-20 + This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC (such as OGC Standards, XML (Extensible Markup Language) Document Type Definitions, XML Schemas, Namespaces, Stylesheets, and other documents). The formal Namespace identifier (NID) is ogc. + + + + Carl Reed + A URN namespace for the Open Geospatial Consortium (OGC) - + + This document covers Geoprocessing Workflow best practices and methods in a SOA environment. A RESTful approach was also conducted in this testbed, but no specific implementation details were available to be included in this ER; also, the RESTful workflow approaches and technology used in this testbed was essentially same as that used in OWS-5. + + 09-053r5 + + OWS-6 Geoprocessing Workflow Architecture Engineering Report - - This OpenGIS Implementation Standard defines the interfaces for OpenGIS Location Services (OpenLS): Part 6 - Navigation Service (formerly the Full Profile of the Route Determination Service), which is part of the GeoMobility Server (GMS), an open location services platform. - + Bastian Schäffer - - 08-028r7 - Location Services (OpenLS): Part 6 - Navigation Service - 08-028r7 - Gil Fuchs - 2008-09-04 - OpenGIS Location Services (OpenLS): Part 6 - Navigation Service + 09-053r5 + OWS-6 Geoprocessing Workflow Architecture Engineering Report + 2009-10-09 + - - - - This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice. - - Volume 3: OGC CDB Terms and Definitions (Normative) - - 2021-02-26 + + Arliss Whiteside + + 01-014r5 + CT Definition Data for Coordinate Reference + + 2001-10-10 - 15-112r4 - Volume 3: OGC CDB Terms and Definitions (Normative) - 15-112r4 - Carl Reed - - - - An Extension Model to attach Points of Interest into IndoorGML - 20-054r1 - Kyoung-Sook Kim, Jiyeong Lee + - - - - An Extension Model to attach Points of Interest into IndoorGML - 20-054r1 - - 2021-01-19 - The scope of this discussion paper is to investigate types of Point of Interest (POI) data in indoor space and propose a conceptual model to harmonize the POI information with the IndoorGML core and navigation modules. In particular, this document focuses on the management of spatial (and non-spatial) history of indoor POI features. The paper covers the following scope: + 01-014r5 + A data model for coordinate reference systems to provide a common framework across all OGC specifications. + CT Definition Data for Coordinate Reference + + + The OGC Testbed-17 Features and Geometries JSON task investigated proposals for how feature data could be encoded in JSON so that: -Points of Interest Feature Types; +* Different Coordinate Reference Systems (CRS) are supported and +* Communities can build and formally specify profiles of the fully CRS-enabled JSON with limited sets of supported geometry types and with clear constraints for feature type definitions. -A Conceptual model to extend IndoorGML schema for indoor POI; and +GeoJSON, a standard of the Internet Engineering Task Force (IETF), was used as a starting point. -Use cases in home navigation and hospital facility management. - - - This document provides the details for a corrigendum for the existing OpenGIS Standard for the Web Map Context Documents version 1.1.0 and does not modify that standard. The current OpenGIS IS that this document provides revision notes for is 05-005. This document is a corrigendum to 05-005. - OpenGIS Web Map Context Documents Corrigendum 1 - - - Web Map Context Documents Corrigendum 1 - 08-050 - - - - Tom Kralidis - 08-050 - 2008-05-02 - - - - - - - - +This Engineering Report (ER) captures the results and discussions, including material that was submitted to the https://github.com/opengeospatial/OGC-feat-geo-json[OGC Features and Geometries JSON Standards Working Group]. + - Peter Ladstaetter - OpenGIS Simple Features Implementation Specification for CORBA - 1999-06-02 - Simple Features Implementation Specification for CORBA - 99-054 - The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc). - 99-054 - - - 2010-04-02 - - 09-163r2 - sensorML Extension Package for ebRIM Application Profile - Fre&#769;de&#769;ric Houbie, Fabian Skive&#769;e, Simon Jirka - sensorML Extension Package for ebRIM Application Profile - - - This document describes the mapping of description of sensors using SensorML specification 1.0 [OGC 07-000] to an ebRIM structure within an OGCTM Catalogue 2.0.2 (Corrigendum 2 Release) [OGC 07-006r1] implementing the CSW-ebRIM Registry Service – part 1: ebRIM profile of CSW [OGC 07-110r4]. -In addition this document contains the definition of a SensorML profile for Discovery which defines a minimum set of metadata to be provided within SensorML documents as well as the structure this data shall possess. This profile is based on the OGC OWS- 6 SensorML Profile for Discovery Engineering Report [OGC 09-033]. -It defines the way sensors metadata are organized and implemented in the Catalogue for discovery, retrieval and management. - - - 09-163r2 - - - 21-064 - 2023-01-10 - Andreas Matheus - OGC Disaster Pilot 2021 Engineering Report - 21-064 - - + OGC Features and Geometries JSON Engineering Report + 21-017r1 + 21-017r1 + 2022-02-08 + - + OGC Testbed-17: OGC Features and Geometries JSON Engineering Report - OGC Disaster Pilot 2021 Engineering Report - This OGC Disaster Pilot ’21 (DP21) Engineering Report summarizes work done in the Pilot to increase disaster awareness among a range of disaster management stakeholders. Pilot participants implemented components of a data flow ecosystem to leverage analysis-ready earth observations and other datasets (ARD) and produce decision ready indicators (DRI) according to collaboratively developed workflow recipes. DP21 focused on the hazards of flooding, landslides, and pandemic, as well as the interactions and complications between them, in three regions including the Piura and Rimac river basins in Peru; the Red River Basin in Manitoba, Canada; and the greater New Orleans area in Louisiana, United States. The Pilot also prototyped providing information to field practitioners in secure geopackage formats, as well as leveraging linked data and structured web page information to optimize public web searches for disaster information. + Clemens Portele - + - 15-003 - - David Graham - 15-003 - Common DataBase Volume 1 Main Body - 2015-07-22 - - OGC Common DataBase Volume 1 Main Body - - The Common DataBase (CDB) Specification provides the means for a single, versionable, simulation-rich, synthetic representation of the earth. A database that conforms to this Specification is referred to as a Common DataBase or CDB. A CDB provides for a synthetic environment repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB can be used as a common on-line (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks; in this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. -The application of CDB to future simulator architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the HLA/FOM and DIS protocols, the application of the CDB Specification provides a Common Environment to which inter-connected simulators share a common view of the simulated environment. -The CDB Specification is an open format Specification for the storage, access and modification of a synthetic environment database. The Specification defines the data representation, organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The Specification makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. -The CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. It encompasses the terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the synthetic environment includes the specific attributes of the synthetic environment data as well as their relationships. -A CDB contains datasets organized in layers, tiles and levels-of-detail; together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB is specifically tailored for real-time applications. - + OGC GeoSPARQL - A Geographic Query Language for RDF Data + 22-047r1 + Nicholas J. Car + + GeoSPARQL contains a small spatial domain OWL ontology that allow literal representations of geometries to be associated with spatial features and for features to be associated with other features using spatial relations. + +GeoSPARQL also contains SPARQL extension function definitions that can be used to calculate relations between spatial objects. + +Several other supporting assets are also contained within GeoSPARQL such as vocabularies of Simple Feature types and data validators. + +The namespace for the GeoSPARQL ontology is http://www.opengis.net/ont/geosparql# + +The suggested prefix for this namespace is geo + +The namespace for the GeoSPARQL functions is http://www.opengis.net/def/function/geosparql/ + +The suggested prefix for this namespace is geof + + + + + + OGC GeoSPARQL - A Geographic Query Language for RDF Data + 22-047r1 + 2024-01-29 - - This report proposes and executes methods to evaluate the performance of the use of the Geography Markup Language (GML) as encoded in various ways. - - 05-050 - GML Performance Investigations by CubeWerx - - GML Performance Investigations by CubeWerx - 2006-05-02 - - 05-050 - - Craig Bruce + + + Cliff Kottman + + Topic 17 - Location Based Mobile Services + Topic 17 - Location Based Mobile Services + 00-117 - - - Keith Pomakis - Tiled WMS Discussion Paper - 07-057r2 - 07-057r2 - OpenGIS Tiled WMS Discussion Paper - The OpenGIS® Tiled Web Map Service Discussion Paper explains how the OpenGIS Web Map Service Standard (WMS) [http://www.opengeospatial.org/standards/wms] can be extended to allow fast response to a predefined set of tiled maps. It should be read in conjunction with the latest version WMS standard. - - - - - 2007-10-10 + Draft Abstract Spec for Location Based Services. Never formally adopted + 00-117 + 2000-05-15 + + + + + OWS-7 Dynamic Sensor Notification Engineering Report + 10-061r1 + 10-061r1 + + Johannes Echterhoff, Ingo Simonis + This document is applicable to scenarios where moving sensors need to be tracked and their entry into an area of interest needs to be detected. + +The document presents a detailed discussion of different approaches for encoding tracked object position. + +Two approaches for implementing dynamic sensor tracking and notification are described, one based on the Sensor Alert Service specification and the other based on the Sensor Event Service specification. + +An overview of standards and specifications relevant for and related to dynamic sensor tracking and notification is provided. + + OWS-7 Dynamic Sensor Notification Engineering Report + + + 2010-06-30 - + + + - 15-048r3 - Testbed-11 NIEM & IC Data Encoding Specification Assessment and Recommendations Engineering Report - 2016-01-25 - Jeff Harrison - 15-048r3 - OGC Testbed-11 NIEM & IC Data Encoding Specification Assessment and Recommendations Engineering Report - - - The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community -(IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0 -architecture through the development, implementations, test, and robust demonstration -making use of IC specifications, Geography Markup Language (GML), and NIEM in a -simulated “real-world” scenario. The demonstration scenario begins with NIEMconformant -Information Exchange Packages (IEPs) containing operational data and IC -security tags from the Information Security Marking (ISM) and Need-To-Know (NTK) -access control metadata, and the Trusted Data Format (TDF) for binding assertion -metadata with data resource(s). Those instance documents are deployed on Open -Geospatial Consortium (OGC) Web Services to be used by client applications. Access -control is based on attributes of the end-user and the instance data. -Recommendations to update these information exchanges were provided to reflect NIEM -3.0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment -exercised this data encoding in OGC Web Feature Services (WFS) and Policy -Enforcement Points (PEP) accessed by multiple client applications. Results from this task -provided a preliminary architecture that was tested and demonstrated in Testbed 11, and -summarized in other OGC Testbed 11 Engineering Reports. + DGGS and DGGS API Engineering Report + 20-039r2 - - - - - OGC Aviation Domain Working Group - Guidance on the Aviation Metadata Profile - 10-196r1 - 2011-03-28 - + OGC Testbed-16: DGGS and DGGS API Engineering Report - 10-196r1 - - Guidance on the Aviation Metadata Profile - - This paper explains how to map the Requirements for Aviation Metadata into a metadata profile. - + 2021-01-13 + This OGC Testbed-16 Engineering Report (ER) documents the needs and key requirements for drafting an OGC Discrete Global Grid Systems (DGGS) Application Programming Interface (API) standard. The draft DGGS API is defined using the OpenAPI 3.0 specification. The work documented in this ER represents the beginning of a multi-initiative process to fully realize the benefits of standards compliant DGGS implementations and to help drive adoption of DGGS as a key element in advanced Spatial Data Architectures. The Testbed participants investigated a Client-Server DGGS architecture involving one (or more) DGGS Server implementations, DGGS-enabled Data Sources and a simple front-end DGGS Client. DGGS API functionality will be tested using one (or more) simple use case scenarios focusing on the two-way translation between geographic locations and DGGS Zonal Identifiers. + 20-039r2 + Robert Gibb, Byron Cochrane, Matthew Purss - - 19-076 - This Health Spatial Data Infrastructure white paper provides a discussion about the collection, exchange, integration, analysis, and visualization of health and non-health data to support health applications. Applications that address health issues at global and population level scale as well as at the local, individual patient scale are presented. The paper identifies opportunities to advance OGC Standards towards building a framework to support Health Spatial Data Infrastructures (SDIs). - 19-076 - Health Spatial Data Infrastructure: Application Areas, Recommendations, and Architecture - Health Spatial Data Infrastructure: Application Areas, Recommendations, and Architecture - Ajay Gupta, Luis Bermudez, Eddie Oldfield, Scott Serich - + + + Geoparser + + Geoparser + 01-035 + 2001-03-27 + *RETIRED* Geoparsing refers to the capability to process a textual document and identify key words and phrases that have a spatial context. + 01-035 + + + + Jeff Lansing + + - 2020-03-30 + 03-010r9 + Recommended XML Encoding of CRS Definitions + 03-010r9 + This OpenGIS Recommendation Paper specifies basic XML encoding of data defining coordinate reference systems and coordinate operations. This encoding is expected to be adapted and used by multiple OGC Implementation Specifications, by the separate specification of Application Schemas. This document is a Recommendation Paper because the specified encoding is more general than an OpenGIS Implementation Specification and more specific than the OpenGIS Abstract Specification. - - + + + Arliss Whiteside + + 2003-10-16 + Recommended XML Encoding of CRS Definitions + - - Gobe Hobona, Roger Brackin - OWS-9 CCI Semantic Mediation Engineering Report - 12-103r3 - 12-103r3 + + + Development of Spatial Data Infrastructures for Marine Data Management + + 19-025r1 + Development of Spatial Data Infrastructures for Marine Data Management + + This engineering report presents the results of a concept development study on a +Marine Spatial Data Infrastructure (SDI), sponsored by the National Geospatial- +Intelligence Agency (NGA) - Maritime Safety Office (MSO), on behalf of the +International Hydrographic Organization (IHO) and the IHO MSDI Working Group +(MSDIWG), and executed by the Open Geospatial Consortium (OGC). The goal of +this study was to demonstrate to stakeholders the diversity, richness and value of a +Marine SDI – specifically data, analysis, interoperability and associated IT services +- including web services - in addressing needs of the marine domain. + - 2013-02-05 + Robert Thomas, Terry Idol - The OWS-9 Cross Community Interoperability (CCI) thread built on progress made in the recent OWS-8 initiative by improving interoperability between communities sharing geospatial data through advances in semantic mediation approaches for data discovery, access and use of heterogeneous data models and heterogeneous metadata models. This OGC engineering report aims to present findings from CCI thread activities towards advancement of semantic mediation involving heterogeneous data models, gazetteers and aviation data available through web services conformant to OGC standards. -This Engineering Report was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Cross Community Interoperability thread within OWS-9. - + 19-025r1 + 2019-08-05 + + + Rob Atkinson, James Groffen + + OGC  OWS-8 Domain Modelling Cookbook + + This OGCTM document describes best practices for building and maintaining inter-related +domain models, which have dependencies upon multiple systems. It describes how to +build interoperable, maintainable domain models, the challenges and pitfalls faced in +building these models, the techniques and patterns that should be applied, and specific +tools that can be used. The theory of domain modelling is addressed, followed by +practical step-by-step instructions on how to use of the tools. Examples are provided from +Aeronautical Information Exchange Model (AIXM) and Farm Markup Language +(FarmML) as they were refined in the OGC’s OWS-8 testbed. + + + 11-107 + OWS-8 Domain Modelling Cookbook - - - OWS-9 CCI Semantic Mediation Engineering Report + 2011-06-17 + 11-107 - - An Access Management Federation (AMF) is a network of organizations that trust each other for the -means of sharing protected resources among each other. Worldwide, many academic AMFs are -available for the purpose of sharing information and services between academic institutions such -as Universities and Research Organizations. In the academia, some of the well known AMFs are UK -Access Management Federation (United Kingdom http://www.ukfederation.org.uk/), In Common -(USA http://www.incommon.org/) and DFN-AAI (Germany https://www.aai.dfn.de). + + Mike Botts + 02-026r1 + SensorML + 02-026r1 + + + + SensorML + + 2002-04-22 + + The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances. + + + 10-130 + OWS-7 Aviation - FUSE Deployment Engineering Report + This document describes the integration results of deploying OGC Web Services on the FAA chosen Enterprise Service Bus (ESB) - FUSE. Snowflake Software were commissioned to evaluate the impacts of the FAA SWIM security requirements for both secure messaging and user authentication and gain an understanding of the requirements for deploying OGC web services into the Apache FUSE Enterprise Service Bus (ESB). + OWS-7 Aviation - FUSE Deployment Engineering Report + 10-130 + + Debbie Wilson + 2010-08-18 + + + - - 12-026 - Architecture of an Access Management Federation for Spatial Data and Services in Germany - 12-026 - - 2012-04-18 - - Andreas Matheus - Architecture of an Access Management Federation for Spatial Data and Services in Germany - - + + - John Bobbitt - - Units of Measure Recommendation - 2002-08-19 - Units of Measure Recommendation - 02-007r4 + + Establishing the Framework of Disaster Early Warning Mechanisms - A Case Study of Slope Disaster + + The impact of global climate change has led to a rise in the frequency of natural +disasters in numerous countries resulting in substantial losses in terms of both human lives and the global economy. The establishment of a robust disaster early-warning mechanism is recommended that will empower communities to proactively engage in disaster reduction and prevention measures before such calamities occur, thereby effectively reducing losses. +The Common Alerting Protocol (CAP) is an internationally recognized digital +message format and protocol for all types of alarms and early warning notifications. It was officially adopted by The Federal Emergency Management Agency (FEMA) in 2010 for its Integrated Public Alert and Warning System (IPAWS). It has also been successfully implemented in Taiwan for many years. However, different countries may employ other color-coded warning systems to indicate varying degrees of disaster severity. This disparity in warning standards can cause public confusion during emergencies, leading to increased costs in disaster management. This paper proposes a framework that utilizes red and yellow warning lights for issuing alerts. Adopting a standardized approach will mitigate confusion and enhance the efficiency of disaster response and management. +This study proposes a framework that uses red and yellow warning mechanisms for +issuing alerts such as the disaster early warning for debris flows and large-scale +landslides established by the Soil and Water Conservation Bureau (SWCB). This +investigation will explore the feasibility of standardizing yellow and red warning +publishing rules. + 23-022r1 + 2023-08-22 + Establishing the Framework of Disaster Early Warning Mechanisms - A Case Study of Slope Disaster + 23-022r1 + Hsiao-Yuan (Samuel) Yin, Yi-Chia (Vincent) Lin, Chih-Wei (Will) Kuan, Cheng-Yan Tsai, Lok-Man (Lawre - - - Common semantic for units of measurement to be used across all OGC specifications. - 02-007r4 + - - 02-009 - 2002-01-14 - - 02-009 - Geography Markup Language + + + + 06-166 + Carl Reed + A URN namespace for the Open Geospatial Consortium (OGC) + 06-166 + A URN namespace for the Open Geospatial Consortium (OGC) + 2007-01-30 + - Geography Markup Language - The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features. - Ron Lake - - - + This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC. The formal Namespace identifier (NID) is ogc. + + - - 12-118 - OWS-9 Security Engineering Report - This Engineering Report describes the approaches to security taken in the OWS-9 initiative. This document presents the results of the work within the OWS-9 Security and Services Interoperability (SSI) thread and results from CCI and Innovations Cross Thread activities. -The report also describes the various tasks and their results regarding interoperability between different security components provided by different participants. - - 2013-02-06 + + + This white paper describes the OGC Compliance Testing Program. It provides +information about: +• The need for compliance testing to enable interoperability +• How to obtain compliance certification +• The difference between implementing and being certified +• How compliance benefits providers and users of technology +• The proper use of the “Certified OGC Compliant” mark +• Suggested language for procurement documents +• Trademark licensing fees +• An example of an OGC compliance test + OGC Compliance Testing White Paper + 10-128 + 10-128 + + Luis Bermudez + OGC Compliance Testing White Paper + 2010-10-22 + + + - Andreas Matheus + + + Standardized Information Models to Optimize Exchange, Reusability and Comparability of Citizen Science Data (SWE4CS) + Ingo Simonis, Rob Atkinson + + + 2017-03-31 + Standardized Information Models to Optimize Exchange, Reusability and Comparability of Citizen Science Data (SWE4CS) + 16-129 - - OWS-9 Security Engineering Report - 12-118 - + 16-129 + This discussion paper describes a data model for the standardized exchange of citizen science sampling data. To do that it applies the Sensor Web Enablement (SWE) to Citizen Science (SWE4CS). In particular, exposes how Observations and Measurements (O&M) can be used to model the data of the Citizen Science project, in a way that can be retrieved using Sensor Observing System (SOS).This discussion paper is a result of the research project Citizen Observatory Web (COBWEB). COBWEB is supported by the European Commission through grant agreement 308513 - + + - - Documents of type test suite + + Marwa Mabrouk + + 05-016 + Location Service (OpenLS) Implementation Specification: Core Services + 05-016 + + + 2005-05-02 + The OpenGIS® Open Location Services Interface Standard (OpenLS) specifies interfaces that enable companies in the Location Based Services (LBS) value chain to “hook up” and provide their pieces of applications such as emergency response (E-911, for example), personal navigator, traffic information service, proximity service, location recall, mobile field service, travel directions, restaurant finder, corporate asset locator, concierge, routing, vector map portrayal and interaction, friend finder, and geography voice-graphics. These applications are enabled by interfaces that implement OpenLS services such as a Directory Service, Gateway Service, Geocoder Service, Presentation (Map Portrayal) Service and others. + - Documents of type test suite - - - - - - Documents of type test suite - + OpenGIS Location Service (OpenLS) Implementation Specification: Core Services + + - - - WPS 2.0 Interface Standard - 14-065 - - + + + This OGC Engineering Report describes the process of conflation, outlines a framework for conflation and conflation rules services within a service oriented architecture, and describes the implementation of conflation services during the OGC OWS-5 testbed. + 07-160r1 + OWS-5 Conflation Engineering Report + 07-160r1 + + OWS-5 Conflation Engineering Report + 2008-09-12 - + + Pete Brennen - 14-065 - Matthias Mueller - 2015-03-05 - OGC® WPS 2.0 Interface Standard - - Documents of type Abstract Specification - deprecated - - - - - - - - - - - - - - - - - + + + 09-046r5 + OGC Naming Authority – Policies and Procedures + + + 2019-10-31 - Documents of type Abstract Specification - deprecated - - Documents of type Abstract Specification - deprecated + This document describes the procedures used by the OGC Naming Authority for the assignment and registration of OGC names. + + + OGC Naming Authority – Policies and Procedures + Simon Cox, Gobe Hobona + 09-046r5 - - Gobe Hobona, Roger Brackin - OWS-8 Cross Community Interoperability (CCI) Semantic Mediation Engineering Report - 11-063r6 - The OWS-8 Cross Community Interoperability (CCI) thread built on progress made in the recent OWS-7 initiative to cover key technology areas that could not be addressed within the scope of that initiative. The OWS-8 CCI thread aimed to increase interoperability within communities sharing geospatial data, including advancing of interoperability among heterogeneous data models, advancing strategies to share styles to provide a more common and automated use of symbology, improvement of KML, and advancing schema automation allowing communities to better share their information artefacts. This OGC engineering report aims to present findings from CCI thread activities towards advancement of semantic mediation involving data retrieved from heterogeneous data models that are available through web services conformant to OGC standards. -The engineering report will briefly introduce relevant details of the semantic web and mediation. The document will make recommendations on establishing a semantic mediation architecture that uses OGC web services and emerging practice from the semantic web community. Based on the scenario adopted by the CCI thread, the document will also discuss the pros and cons of adopting relevant standards. The engineering report will offer recommendations on how specific OGC standards may be adopted or modified in order to support semantic mediation. - + - 11-063r6 - OWS-8 Cross Community Interoperability (CCI) Semantic Mediation Engineering Report - - - + Terry Idol + The Federal Geographic Data Committee (FGDC) Application Programming Interface (API) assessment was conducted under the OGC Innovation Program with the goal to develop an in-depth understanding of all the components necessary to enable increased coordination and effectiveness of APIs as applied to geospatial information. FGDC customers have been invited to share their experiences with the use of APIs. From those descriptions, recommendations have been derived that help FGDC to better understand how APIs are currently being generated and if using a more standardized approach to APIs might enable a more robust and optimized service offering. + 17-061 + FGDC OGC Application Programming Interface Interoperability Assessment + 17-061 - 2011-11-23 + + FGDC OGC Application Programming Interface Interoperability Assessment + + 2020-05-12 + - + - - - 16-006r4 - Volume 10: OGC CDB Implementation Guidance - This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. - Carl Reed - 16-006r4 - - 2018-12-19 - Volume 10: OGC CDB Implementation Guidance - + Testbed-11 Aviation Feature Schema Recommendations Engineering Report + 15-026 - - - The information security is the state of being protected against the unauthorized use of information and services, or the measures taken to achieve that. This report has ben created as part of OGC Testbed 12 aviation thread and on behalf of sponsors from FAA. It gives the readers an overview into the topic of cyber security in the aviation domain, especially in conjunction with OGC compatible web services, which are today de facto standard for aeronautical traffic System Wide Information Management. - - 16-040r1 - 2017-06-30 + 15-026 - - Testbed-12 Aviation Security Engineering Report - + Developed by EUROCONTROL, the Aviation Feature Schema (AFX) is a template for +application schemas to implement by adding their operational attributes. For example, the +Airport Mapping format can be implemented by extending AFX. The AFX defines +concepts of geometry and temporality through predefined classes and properties. +Therefore, these elements need not be redefined by application schemas. This means +implementations of the AFX abide by the same structure, therefore aiding interoperability +and allowing the rapid development of schemas. The AFX schema is designed to be +generic and easily reusable and it is not intended to replace the standard aviation models +such as WXXM and AIXM. +This Engineering Report assesses the suitability of the AFX as a template for lowering +the GIS entry level for aviation data, providing recommendations of suitability and areas +of improvement. The report is aimed at system and client developers that shall use AFX. + + Thomas Forbes, Alberto Olivares, Richard Rombouts + OGC® Testbed-11 Aviation Feature Schema Recommendations Engineering Report - 16-040r1 - Testbed-12 Aviation Security Engineering Report - Aleksandar Balaban + 2015-10-30 - - DGIWG WMS 1.3 Profile and systems requirements for interoperability for use within a military environment - 09-102 - 09-102 - DGIWG WMS 1.3 Profile and systems requirements for interoperability for use within a military environment + + OGC Testbed-14: Application Schema-based Ontology Development Engineering Report + + + + Johannes Echterhoff + + 18-032r2 + + 18-032r2 + Application Schema-based Ontology Development Engineering Report + 2019-02-04 + This report enhances the understanding of the relationships between application schemas based on the Unified Modeling Language (UML) and ontologies based on the Web Ontology Language (OWL). The work documented in this report provides and improves tools and principled techniques for the development of Resource Description Framework (RDF) based schemas from ISO 19109-conformant application schemas. + + - Cyril Minoux + 20-040r3 + Topic 21 - Discrete Global Grid Systems - Part 1 Core Reference system and Operations and Equal Area Earth Reference System + 20-040r3 + - 2009-09-02 - - This document specifies requirements for systems providing maps using OGC Web Map Service. The document defines a profile of OGC WMS 1.3 implementation standard [WMS1.3], a list of normative system requirements and a list of non-normative recommendations. The Defence Geospatial Information Working Group (DGIWG) performed the work as part of through the S05 Web Data Access Service Project of the Services & Interfaces Technical Panel. - - + + 2021-09-23 + Robert Gibb + + This Abstract Specification lays the foundations for Discrete Global Grid Systems (DGGS). It defines Common classes for spatio-temporal geometry, topology, and reference systems using identifiers, a DGGS Core Reference system as a reference system using zonal identifiers with structured geometry that may be spatio-temporal, a suite of DGGS Core Functions, and it specifies Equal-Area Earth DGGS. The OGC DGGS Abstract Specification supports the specification of standardized DGGS infrastructures that enable the integrated analysis of very large, multi-source, multi-resolution, multi-dimensional, distributed geospatial data. Interoperability between OGC DGGS implementations is anticipated through implementation standards, and extension interface encodings of OGC Web Services. + Topic 21 - Discrete Global Grid Systems - Part 1 Core Reference system and Operations and Equal Area Earth Reference System + - - 12-139 - - In this engineering report we describe how to administrate XACML v2.0, XACML v3.0 and GeoXACML v1.0.1 access control policies through a “Security Rules Service”. Following the XACML and ISO terminology this service plays the role of a Policy Administration Point (PAP) and is therefore called XACML Policy Administration Point (XACML PAP) or XACML Policy Administration Web Service (XACML PAWS). -After introducing OWS-9’s Common Rule Encoding and motivating all components required to administrate (Geo)XACML policies, we describe the interface of a powerful XACML PAP on a conceptual level. This interface definition could serve as a baseline for a future OASIS or OGC XACML Policy Administration Web Service (e.g. OGC XACML PAWS) specification. - - OWS-9: SSI Security Rules Service Engineering Report - 12-139 - Jan Herrmann, Andreas Matheus + + The primary focus of the Sensor Model Language (SensorML) is to provide a robust and +semantically-tied means of defining processes and processing components associated +with the measurement and post-measurement transformation of observations. This +includes sensors and actuators as well as computational processes applied pre- and postmeasurement. +The main objective is to enable interoperability, first at the syntactic level and later at the +semantic level (by using ontologies and semantic mediation), so that sensors and +processes can be better understood by machines, utilized automatically in complex +workflows, and easily shared between intelligent sensor web nodes. +This standard is one of several implementation standards produced under OGC’s Sensor +Web Enablement (SWE) activity. This standard is a revision of content that was +previously integrated in the SensorML version 1.0 standard (OGC 07-000). + + + 2014-02-04 + Mike Botts, Alexandre Robin + OGC® SensorML: Model and XML Encoding Standard + 12-000 + + 12-000 + SensorML: Model and XML Encoding Standard + + + + + + 24-008 + OGC Geotech Interoperability Experiment Engineering Report + 24-008 + + Mickael Beaufils, Kathi Schleidt, Hylke van der Schaaf, Dan Ponti, Neil Chadwick, Derrick Dasenbrock + This Engineering Report (ER) describes the outcomes of the Open Geospatial Consortium (OGC) Geotech Interoperability Experiment (IE). The objective of this IE was to develop a common conceptual model for describing geotechnical engineering data that bridges existing specifications for encoding those data and which could be integrated across OGC and buildingSMART International Standards, + +This ER is directly imported from the project wiki found here: https://github.com/opengeospatial/Geotech/wiki. + 2024-07-05 - 2013-02-05 + OGC Geotech Interoperability Experiment Engineering Report + + + + Jeff Harrison, Panagiotis (Peter) A. Vretanos + Panagiotis (Peter) A. Vretanos, Jeff Harrison + This document defines a Gazetteer Service profile of the OGC Web Feature Service Standard. The OGC Gazetteer Service allows a client to search and retrieve elements of a georeferenced vocabulary of well-known place-names. +This profile extends the WFS interface in a way that a client is able to +– Determine if a WFS implementation is acting as a Gazetteer Service. +– Query the Gazetteer Service in order to retrieve place-name features without closer examination of the feature type definitions +– Access metadata about the gazetteer(s) provided by the service +– Update place-name features using WFS transactions +– Fetch place-name features that have Parent-Child relationships and then follow those links + + Web Feature Service (WFS-G). Services compliant with this standard shall provide Location Instances derived from SI_LocationInstance. In Addition, they may support queries based on the (parent/child) relationships of feature instances, as defined in ISO 19112. + 11-122r1 - OWS-9: SSI Security Rules Service Engineering Report + Gazetteer Service - Application Profile of the Web Feature Service Best Practice + Gazetteer Service - Application Profile of the Web Feature Service Candidate Implementation Standard + + 2012-02-17 + 2011-11-30 + 11-122r1 + Gazetteer Service - Application Profile of the Web Feature Service Best Practice + Gazetteer Service - Application Profile of the Web Feature Service Candidate Implementation Standard + + + + + + - - + + + 14-065r2 + WPS 2.0.2 Interface Standard: Corrigendum 2 + + 2018-02-16 + OGC® WPS 2.0.2 Interface Standard: Corrigendum 2 + + + Matthias Mueller + - 2019-02-04 - - Johannes Echterhoff - This Engineering Report (ER) enhances the understanding of the relationships between data exchange based on Geography Markup Language (GML), JavaScript Object Notation (JSON), and Resource Description Framework (RDF) for future web services, e.g. Web Feature Service (WFS) 3.0. The work documented in this report: - -contributes to the ability to bridge between technology-dependent alternate representations of “features” (real-world objects), and to consistently employ alternate encoding technologies (Extensible Markup Language (XML), JSON, RDF) to exchange information about “features”; and + In many cases geospatial or location data, including data from sensors, must be processed before the information can be used effectively. The OGC Web Processing Service (WPS) Interface Standard provides a standard interface that simplifies the task of making simple or complex computational processing services accessible via web services. Such services include well-known processes found in GIS software as well as specialized processes for spatio-temporal modeling and simulation. While the OGC WPS standard was designed with spatial processing in mind, it can also be used to readily insert non-spatial processing tasks into a web services environment. -determines principled techniques for the development of JSON-based schemas from ISO 19109-conformant application schemas. +The WPS standard provides a robust, interoperable, and versatile protocol for process execution on web services. It supports both immediate processing for computational tasks that take little time and asynchronous processing for more complex and time consuming tasks. Moreover, the WPS standard defines a general process model that is designed to provide an interoperable description of processing functions. It is intended to support process cataloguing and discovery in a distributed environment. - Application Schemas and JSON Technologies Engineering Report - 18-091r2 - OGC Testbed-14: Application Schemas and JSON Technologies Engineering Report - + 14-065r2 + + + + 2017-05-12 + - 18-091r2 - + + Jeff Yutzler + + 16-031r1 + Testbed-12 GeoPackage Change Request Evaluations + Testbed-12 GeoPackage Change Request Evaluations + Testbed 12 work has resulted in Change Requests (CRs) to the GeoPackage Encoding Standard. CRs have been submitted to the GeoPackage Standards Working Group (SWG) as GitHub issues. This engineering report (ER) summarizes the results of these activities. + + 16-031r1 - - - Jens Fitzke, Rob Atkinson + + 09-148r1 + Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension + This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using HTTP POST with XML encoding. + + 09-148r1 + + + + + 2010-10-27 + OGC® Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension + Peter Baumann + + + Topic 05 - Features + 08-126 + 2009-01-15 + + + + 08-126 + Topic 5 - Features - Gazetteer Service Profile of a WFS + From ISO 19101, “A feature is an abstraction of a real world phenomenon”; it is a geographic feature if it is associated with a location relative to the Earth. + + Cliff Kottman, Carl Reed - 05-035r1 - Gazetteer Service Profile of a WFS - - 05-035r1 - - Provides web access to an authority for place names. Returns their associated feature representations - 2006-01-12 - - OGC Benefits of Indoor Location - Use Case Survey of Lessons Learned and Expectations - 16-084 - 16-084 - - 2016-08-01 - - Indoor location technologies are enjoying and increasing market success. Technologies in the market have achieved maturity and have become a key driver for innovation and business activities in several value added scenarios, e.g. e-government services, eHealth, personal mobility, logistics, mobility, facility management, retail, to name but a few. This paper collects the results of a survey on the benefits of indoor location, which was jointly prepared and launched by OGC – the Open Geospatial Consortium, InLocation Alliance and i-locate project at the beginning of 2016. Overall, 153 survey responses were received from 33 countries. Responses were categorized in two areas: Client Organizations and Technology suppliers. The goal of the initiative was to acquire a broad view of the requirements and use cases emerging from the wider industrial and user community, beyond the memberships of the various organizations, in order to capture trends, challenges and opportunities, as well as trends and barriers to widespread use of indoor location technologies. This paper does not represent a view of the membership involved in the different organizations; instead, it provides the opportunity to capture recommendations of relevance for the industrial and standardization community these organizations represent. - + + Integrated Client for Multiple OGC-compliant Services + 03-021 + Provides an overview of the requirements, architecture, and design of Integrated Clients developed during the OGC Open Web Services + + Jeff Yutzler + 2003-01-20 - OGC Benefits of Indoor Location - Use Case Survey of Lessons Learned and Expectations + 03-021 + + Integrated Client for Multiple OGC-compliant Services + + + + + + The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community +(IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0 +architecture through the development, implementations, test, and robust demonstration +making use of IC specifications, Geography Markup Language (GML), and NIEM in a +simulated “real-world” scenario. The demonstration scenario begins with NIEMconformant +Information Exchange Packages (IEPs) containing operational data and IC +security tags from the Information Security Marking (ISM) and Need-To-Know (NTK) +access control metadata, and the Trusted Data Format (TDF) for binding assertion +metadata with data resource(s). Those instance documents are deployed using Open +Geospatial Consortium (OGC) standards enabled Web Services for use by client +applications. Access control is based on attributes of the end-user and the instance data. +Recommendations to update these information exchanges were provided to reflect NIEM +3.0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment tested +this data encoding in OGC Web Feature Services (WFS) and Policy Enforcement Points +(PEP) accessed by multiple client applications. Results from this task provided a +preliminary architecture that was tested and demonstrated in Testbed 11, and summarized +in other OGC Testbed 11 Engineering Reports. The demonstrations also highlighted how +NIEM and IC data encodings together may support more agile and customer-centric +frameworks driven by collaborative partnerships. This transformation is vital to +confronting the security challenges of the future. + Jeff Harrison + 15-050r3 + Testbed-11 Test and Demonstration Results for NIEM using IC Data Encoding Specifications Engineering Report + + OGC Testbed-11 Test and Demonstration Results for NIEM using IC Data Encoding Specifications Engineering Report + 2016-01-25 + + - Giuseppe Conti, Fabio Malabocchia, Ki-Joune Li, George Percivall, Kirk Burroughs, Stuart Strickland + 15-050r3 + - + + + The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be used for the manipulation of geographic information structured following the specifications adopted by the Technical Committee211 of the International Organization for Standardization (ISO) and by the Open Geospatial Consortium (OGC). This standard standardizes the informatics contract between the client code which manipulates normalized data structures of geographic information based on the published API and the library code able both to instantiate and operate on these data structures according to the rules required by the published API and by the ISO and OGC standards. + GeoAPI 3.0 Implementation Standard with corrigendum + 09-083r4 + + 09-083r4 - 04-094r1 + GeoAPI 3.0 Implementation Standard with corrigendum + Adrian Custer - OGC Web Feature Service Implementation Specification with Corrigendum - 04-094r1 - Web Feature Service Implementation Specification with Corrigendum - The OGC Web Map Service allows a client to overlay map images for display served from multiple Web Map Services on the Internet. In a similar fashion, the OGC Web Feature Service allows a client to retrieve and update geospatial data encoded in Geography Markup Language (GML) from multiple Web Feature Services. - -The requirements for a Web Feature Service are: - -The interfaces must be defined in XML. -GML must be used to express features within the interface. -At a minimum a WFS must be able to present features using GML. -The predicate or filter language will be defined in XML and be derived from CQL as defined in the OpenGIS Catalogue Interface Implementation Specification. -The datastore used to store geographic features should be opaque to client applications and their only view of the data should be through the WFS interface. - The use of a subset of XPath expressions for referencing properties. - - Panagiotis A. Vretanos - - - - 2016-10-26 + 2018-04-15 + - - + + - + This International Standard describes an XML and KVP encoding of a system neutral syntax for expressing projections, selection and sorting clauses collectively called a query expression. +These components are modular and intended to be used together or individually by other standards which reference this International Standard. + 09-026r1 + OpenGIS Filter Encoding 2.0 Encoding Standard + Panagiotis (Peter) A. Vretanos + Filter Encoding 2.0 Encoding Standard + 09-026r1 + + 2010-11-22 - 2011-12-19 + + + + + + + + + + + + + + + 21-054 + OGC Disaster Pilot JSON-LD Structured Data Engineering Report + - OWS-8 Aviation Architecture Engineering Report + Sergio Taleisnik - Johannes Echterhoff - 11-093r2 - 11-093r2 - OWS-8 Aviation Architecture Engineering Report - This OGC® document describes the architecture implemented in the OWS-8 Aviation thread, including general workflows. The document contains a summary description of the various components within the architecture. An introduction to the Access Control System is provided. Furthermore, the document describes relevant aspects of handling events and notifications. Lessons learned – for example regarding the AIXM Temporality Model – as well as scenarios and accomplishments are documented as well. - - - - + OGC Disaster Pilot JSON-LD Structured Data Engineering Report + This Disaster Pilot JSON-LD Structured Data Engineering Report documents the analysis, discussions, results, and recommendations that emerge from the efforts carried out regarding the use of JSON-LD with OGC APIs to generate structured web page data for search engine optimization of disaster related information. + +This ER provides the practical experience and lessons learned on the usage of Linked Data within OGC APIs with the objective of enhancing the web search and finding up-to-date conditions, observations, and predictions associated with well-known local geography. Upcoming initiatives should use the findings documented in this ER to further develop applications that make geospatial data and information more easily findable, accessible, interoperable, and reusable, which will increase the efficiency of disaster response. This ER could also be used as a case study of Linked Data to help other industries understand its value and implement it within their domains, or it could serve as a baseline for adding Linked Data support to one or several OGC API standards. + + 2023-01-05 + 21-054 - Documents of type Interoperability Program Report - Documents of type Interoperability Program Report - Documents of type Interoperability Program Report - - - - - This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS - + + + + + + + + + + + + + + + + + + + + + + Two Dimensional Tile Matrix Set + 17-083r2 + Joan Masó + + 2019-10-06 - 2004-10-05 - ISO19115/ISO19119 Application Profile for CSW 2.0 - - 04-038r1 - ISO19115/ISO19119 Application Profile for CSW 2.0 - Uwe Voges, Kristian Senkler - 04-038r1 + + + 17-083r2 + OGC Two Dimensional Tile Matrix Set + + The OGC Tile Matrix Set standard defines the rules and requirements for a tile matrix set as a way to index space based on a set of regular grids defining a domain (tile matrix) for a limited list of scales in a Coordinate Reference System (CRS) as defined in [OGC 08-015r2] Abstract Specification Topic 2: Spatial Referencing by Coordinates. Each tile matrix is divided into regular tiles. In a tile matrix set, a tile can be univocally identified by a tile column a tile row and a tile matrix identifier. This document presents a data structure defining the properties of the tile matrix set in both UML diagrams and in tabular form. This document also presents a data structure to define a subset of a tile matrix set called tile matrix set limits. XML and JSON encodings are suggested both for tile matrix sets and tile matrix set limits. Finally, the document offers practical examples of tile matrix sets both for common global projections and for specific regions. - - USGS OGC® Interoperability Assessment Report - 14-079r1 - - Ingo Simonis + + + OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Version 1.3 Release Notes + 22-032r1 + + 2023-01-11 + + 22-032r1 + These I3S Release notes document changes incorporated into the OGC I3S Community Standard version 1.3. + OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Version 1.3 Release Notes + + + Carl Reed, PhD + + + + - USGS OGC® Interoperability Assessment Report + 09-156r2 + Ocean Science Interoperability Experiment Phase II Report + + 2011-01-04 + 09-156r2 + Ocean Science Interoperability Experiment Phase II Report + This OGC Engineering Report documents the work performed by the participants of the Ocean Science Interoperability Experiment Phase II. This work is a follow-on to the OGC Oceans IE Phase 1 activity. Specifically, this IE addressed the following tasks: +• Automated metadata/software installation via PUCK protocol. +• Offering of complex systems (e.g. observations systems containing other systems) such as collection of stations. +• Linking data from SOS to out-of-band offerings. +• Semantic Registry and Services. +• Catalogue Service-Web Registry. +• IEEE-1451/OGC-SWE harmonization + +As a result of this experiment, a number of recommendations and conclusions were identified. + - The USGS Interoperability assessment was conducted under the OGC Interoperability -Program with the goal to better understand how USGS customers make use of OGC -compliant Web services operated by USGS. For this assessment, USGS customers have -been invited to share their experiences and to describe their use cases and experiences -made with USGS data services and products. From those descriptions, recommendations -have been derived that help USGS to better understand their user community and -optimize their service offerings. - - 14-079r1 - 2015-02-02 + Luis Bermudez - - OGC Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W - - + + + + 2015-11-18 + Testbed-11 Incorporating Social Media in Emergency Response Engineering Report + 15-057r2 + This OGC Engineering Report (ER) was created as a deliverable for the OGC Testbed 11 initiative of the OGC Interoperability Program. This ER describes an approach for incorporating Social Media for Emergency Response applications that use spatial data infrastructures. This document also reports on findings about the advancements using Social Media and VGI resources. The ER includes ideas on improving the architecture, service change recommendations (primarily concerning the OGC Sensor Observation Service (SOS) 2.0 interface), and lessons learned. + + Matthes Rieke, Simon Jirka, Stephane Fellah + 15-057r2 + OGC® Testbed-11 Incorporating Social Media in Emergency Response Engineering Report - - Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W - 07-038 - + - Nicolas Lesage, Marie-Lise Vautier - 2007-06-06 - This document extends the ebRIM application profile of CS-W for the cataloguing of ISO 19115 and ISO 19119 compliant metadata. - 07-038 - - Web Object Service Implementation Specification - 03-013 - - Panagiotis (Peter) A. Vretanos - + + Joan Masó + + + + 2013-06-18 - + + 12-157 + OWS-9 Engineering Report - OWS Innovations - Map Tiling Methods Harmonization + OGC® OWS-9 Engineering Report - OWS Innovations - Map Tiling Methods Harmonization + 12-157 + This engineering report proposes a profile for WMTS that limits the flexibility or the standard and mimics what some other tile initiatives are doing. It also proposes some improvements in WMTS to accommodate the need for requesting several tiles of a region at different scales that has been identified by the GeoPackage team. These recommendations help to better harmonize OSGeo tile standards and mass-market technologies. + + + Topic 6.3 - Schema for Coverage Geometry and Functions – Part 3: Processing Fundamentals + + + OGC Abstract Specification Topic 6: Schema for Coverage Geometry and Functions – Part 3: Processing Fundamentals + 21-060r2 + 2024-07-05 + 21-060r2 + Peter Baumann + This document defines, at a high, implementation-independent level, operations on coverages - i.e., digital representations of space-time varying geographic phenomena - as defined in ISO 19123-1. Specifically, regular and irregular grid coverages are addressed. Future versions will additionally support further axis types as well as further coverage types from ISO19123-1, such as point clouds and meshes in particular. While the core functionality is expected to be generic and applicable for any coverage, there may be special functionality for particular coverage types. + - Web Object Service Implementation Specification - 03-013 - There is a requirement to manage many different types of objects. These include styles, symbols and images. To satisfy this requirement, a repository interface is required. The intent of the Web Object Service interface is to provide a means to define this interface. - 2003-01-15 + + - + + Testbed-18: Moving Features Engineering Report + 22-016r3 + 2023-06-26 - - - - + 22-016r3 - 2018-01-26 - 17-027 - Testbed-13: GeoPackage Engineering Report - OGC Testbed-13: GeoPackage Engineering Report - Robert Cass - 17-027 - This Engineering Report details the processes and results related to generating GeoPackages developed to contain topographic vector features and supporting symbologies based on The National Map (TNM) product of the United States Geological Survey (USGS). - - + Brittany Eaton + - 11-134 - OWS-8 Tracking: Moving Target Indicator Process, Workflows and Implementation Results ER + Testbed-18: Moving Features Engineering Report - - + This OGC Testbed-18 (TB-18) Engineering Report (ER) is based on previous OGC Moving Features and Sensor Integration (MFSI) activities. The OGC TB-18 MFSI task addressed the interoperability between sensors and between sensing systems as well as the exchange of multiple sources of detected moving objects into one common analytic client. This ER describes the architecture framework for multi-source moving object detection into the client supported by OGC MFSI Standards and describes challenges of multi-sensor integration in the context of Moving Features data. - 2012-05-15 - The scope of this report is to provide a description of services, data storage and data -movement within the OWS-8 Tracking sub-thread. The paper outlines the development -of Sensor Observation Services (SOS), a Web Feature Service(WFS), a Notification -Service and a Web Processing Service (WPS) for generating track features. Additionally, -implemented encodings will be discussed as examples and in comparison to the -encodings detailed in (Simonis, 2011). - - OWS-8 Tracking: Moving Target Indicator Process, Workflows and Implementation Results ER - Rob Cass, Mark Simms - 11-134 - - 2010-07-15 - 10-124r1 - - Simon Cox + + + 01-026r1 + + Geocoder + Serge Margoulies + + 01-026r1 + Geocoder + + + 2001-03-28 + *RETIRED* Geocoding is the process of linking words, terms and codes found in a text string to their applicable geospatial features, with known locations. (Locations are defined as geometry; usually points with x, y coordinates.) + + - OGC Identifiers - the case for http URIs - 10-124r1 - OGC Identifiers - the case for http URIs - + CityJSON Community Standard 2.0 + 20-072r5 + Hugo Ledoux, Balázs Dukai - - The OGC provides a large number of resources to support the construction of spatial -data infrastructures, including documents, specifications, schemas and concept -definitions. When deployed, the infrastructures require persistent reference to these -resources, enabled by persistent identifiers. This may be at various level of -granularity. + + 20-072r5 + 2023-10-20 + + + CityJSON is a data exchange format for digital 3D models of cities and landscapes. It aims at being easy-to-use (for reading, processing, and creating datasets), and it was designed with programmers in mind, so that tools and APIs supporting it can be quickly built. The JSON-based encoding of CityJSON implements a subset of the OGC CityGML data model (version 3.0) and includes a JSON-specific extension mechanism. Using JSON instead of GML allows us to compress files by a factor 6 and at the same time to simplify greatly the structure of the files. + CityJSON Community Standard 2.0 + - - + + + Extensions of IndoorGML 1.1 - Indoor Affordance Spaces + + 21-010r2 + Taehoon Kim, Kyoung-Sook Kim, Jiyeong Lee, Ki-Joune Li + 21-010r2 + Extensions of IndoorGML 1.1 - Indoor Affordance Spaces + + 2022-05-06 - 11-036 + The OGC IndoorGML standard provides a fundamental data model for representing indoor spaces as spatial, topological, and semantic features. The IndoorGML core module allows applications to extend the model with their semantic considerations. For example, the IndoorGML navigation module classifies the basic class of indoor spaces, cell spaces, into navigable or non-navigable spaces. Navigable spaces, in which users can move freely, are specified in two subclasses: transfer spaces (e.g. doors, entrances, hallways) and general spaces (e.g. rooms, terraces, lobbies), based on indoor navigation requirements. This discussion paper proposes an extension to the OGC IndoorGML core module to support new types of location-based services, such as autonomous driving robots, personal experience augmentation with augmented reality (AR) / virtual reality (VR), and facilities management, to understand activities and needs in indoor spaces. The proposed extension consists of three new indoor spaces to represent affordance spaces with structural, functional, and sensory characteristics by leveraging the multi-layered space representation of IndoorGML. - - - Lance McKee, Carl Reed, Steven Ramage - 11-036 - OGC Standards and Cloud Computing - OGC Standards and Cloud Computing - 2011-04-07 - This OGC White Paper discusses cloud computing from the perspective of OGC’s -geospatial standards development activities and standards baseline. The paper begins -with a discussion of what the cloud and cloud computing are. Unfortunately, there is still -considerable misunderstanding in the geospatial technology community regarding cloud -computing. The paper then discusses how standards figure into the options, benefits and -risks of cloud computing for users and providers of geospatial data and software. This -perspective is important not only for those immersed in geospatial technology, but also for -cloud service providers, customers and technology partners who may be unfamiliar with -the basic issues surrounding geospatial technology. This white paper does not discuss -vendor specific cloud computing platforms. - - 2017-06-30 - 16-023r3 - Testbed-12 Implementing Asynchronous Services Response Engineering Report + + + 20-030 + 2020-10-22 + + 20-030 + OGC API - Tiles - 3D (GeoVolumes) Engineering Report + OGC API - Tiles - 3D (GeoVolumes) Engineering Report + Timothy Miller and Gil Trenum + + This Engineering Report documents the draft specification for a three-dimensional (3D) geodata Application Programming Interface (API) that organizes access to a variety of 2D / 3D datasets and their distributions according to a nested hierarchy of 3D geospatial volumes (GeoVolumes). The GeoVolumes (initially Tiles-3D / 3D Container) API specification is consistent with OGC API - Common and supports both link-follow and bbox query methods of access to resources of interest. + - - Testbed-12 Implementing Asynchronous Services Response Engineering Report - 16-023r3 + + + + + + + + + + 16-028r1 + Testbed-12 FIXM GML Engineering Report - Most of current OGC specifications define synchronous communication patterns, i.e. after sending a request to an OGC service, clients need to wait for the response. But several applications, e.g. delivery of information about events or executing complex environmental models with long runtime, need asynchronous client-server interaction pattern that do not require clients to keep the connection to the server continuously open in order to wait for responses. At the moment, there are several approaches how to add asynchronous communication to existing OGC services: One option is to use a WPS façade, as the WPS specification already defines asynchronous service responses. Another option is to add extensions to the different specifications and the third option is developed by the OGC Publish-Subscribe Working Group. This ER summarizes and compares the results from the different activities for asynchronous service responses and provides recommendations for future activities. - Benjamin Pross - - - - - 07-018r2 - OpenGIS Sensor Planning Service Application Profile for EO Sensors + Thomas Disney + + 2017-06-19 - - 2008-01-21 - - Philippe M - - The SPS configuration proposed in this profile is intended to support the programming process of Earth Observation (EO) sensors system. This profile describes a consistent SPS configuration that can be supported by many satellite data providers, most of whom have existing facilities for the management of these programming requests. - Sensor Planning Service Application Profile for EO Sensors - 07-018r2 + 16-028r1 + Testbed-12 FIXM GML Engineering Report + The FAA and EUROCONTROL, in conjunction with multiple other international partners, are currently in the process of developing the Flight Information Exchange Model (FIXM). FIXM is an exchange model capturing Flight and Flow information that is globally standardized. The need for FIXM was identified by the International Civil Aviation Organization (ICAO) Air Traffic Management Requirements and Performance Panel (ATMRPP) in order to support the exchange of flight information as prescribed in Flight and Flow Information for a Collaborative Environment (FF-ICE). + +FIXM is the equivalent, for the Flight domain, of Aeronautical Information Exchange Model (AIXM) and Weather Information Exchange Model (WXXM), both of which were developed in order to achieve global interoperability for, respectively, Aeronautical Information Systems (AIS) and Meteorological Information (MET) exchange. FIXM is therefore part of a family of technology independent, harmonized and interoperable information exchange models designed to cover the information needs of Air Traffic Management. Previous OGC IP initiatives developed an architecture that supports the exchange of AIXM and WXXM data. This report shall describe the integration of Geography Markup Language (GML) profile elements into FIXM, specifically, the Feature, Time, Geometries and Units of Measure (UOM), into FIXM version 3.0.1 and drafts of FIXM 4.0. The purpose of this report is to provide recommendations and change requests (CR) on the implementation of GML elements for use by the FIXM development community. + - - 19-023r1 - OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report - 19-023r1 - - This OGC Testbed 15 Engineering Report (ER) describes a style encoding and metadata conceptual model that provides information for understanding styles intended usage, availability, compatibility with existing layers, and supporting style search. A style is a sequence of rules of symbolizing instructions to be applied by a rendering engine on one or more features and/or coverages - 2019-12-11 - - - OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report - - Andrea Aime + + + 16-042r1 + + Testbed-12 WMS/WMTS Enhanced Engineering Report + 16-042r1 + 2017-06-14 + This Engineering Report (ER) describes requirements, challenges and solutions regarding improving multidimensional Earth Observation (EO) data access, discovery and visualization through Web Map Service (WMS), Web Map Tile Service (WMTS), and corresponding extensions. The ER will highlight solutions and recommendations of following main topics. +1) WMTS enhancements for time-varying layer access/discovery + +2) WMS enhancements for NetCDF + +3) WMTS enhancements for multidimensional domain discovery + + + Testbed-12 WMS/WMTS Enhanced Engineering Report + Lingjun Kang, Liping Di, Eugene Yu + - - 2017-03-12 - - - Hideki Hayashi, Akinori Asahara, Kyoung-Sook Kim, Ryosuke Shibasaki, Nobuhiro Ishimaru + - - This document defines Moving Features Access, i.e., access methods to moving feature data for retrieving feature attributes, information on a relation between a trajectory object and one or more geometry objects, and information on a relation between two trajectory objects from a database storing trajectory data of moving features. + Topic 22 - Core Tiling Conceptual and Logical Models for 2D Euclidean Space + Topic 22 - Core Tiling Conceptual and Logical Models for 2D Euclidean Space + 19-014r3 + + + 19-014r3 + + 2020-10-22 + This OGC Abstract Specification (AS) defines: -Abstract methods of accessing moving features data are defined in ISO 19141:2008 (Geographic information - Schema for moving features) [ISO 19141:2008]. However, the methods are insufficient to access a database storing moving feature data from multiple sources. If implementations for access to moving features data using various programming languages or protocols (e.g., SQL, Java, and HTTP) are developed without any standards, these implementations might be inconsistent with each other, resulting in poor interoperability. Therefore, methods to access a database storing moving feature data are necessary to improve interoperability. +A conceptual model for tiling space in any dimension and; -Applications using moving feature data, typically representing vehicles or pedestrians, are rapidly increasing. Innovative applications are expected to require the overlay and integration of moving feature data from different sources to create greater social and business value. Moreover, systems relying on single-source moving feature data are now evolving into more integrated systems. Integration of moving feature data from different sources is a key to developing more innovative and advanced applications. +A logical model for 2D tiled structures and by extension tiling. The logical model is based on the conceptual model. -Moving Features Access ensures better data exchange by handling and integrating moving feature data to broaden the market for geo-spatial information such as Geospatial Big Data Analysis. OGC 14-083r2 (OGC® Moving Features Encoding Part I: XML Core) [OGC 14-083r2] and OGC 14-084r2 (OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV)) [OGC 14-084r2] are existing implementation standards. Moving Features Access uses these standards to encode moving features. - - Moving Features Access - 16-120r3 - - 16-120r3 - OGC Moving Features Access +The conceptual model specified in this Abstract Specification could be a sub-class in a more comprehensive Spatial Partitioning Conceptual Model. Additional Parts may be added to this AS for other dimensions, such as 3D, or other uses cases. + Carl Reed + + - - Leigh St. Hilaire, Aidan Brookson - Testbed-18: Building Energy Data Interoperability Engineering Report - 22-041 - - This OGC Testbed-18 Engineering Report (ER) represents deliverable D012 and D013 for the Building Energy Data Interoperability task. - 2023-08-16 - - + + + + This document provides release notes for version 1.1 of the CDB Standard and related Best Practices. + OGC CDB Version 1.1 Release Notes + - 22-041 - - Testbed-18: Building Energy Data Interoperability Engineering Report + 18-016r1 + CDB Version 1.1 Release Notes + + Carl Reed + 2018-12-19 + 18-016r1 - - Joan Masó - 2013-06-18 - OWS-9 - OWS Context evaluation IP Engineering Report - 12-105 - + + + 2017-03-10 + Testbed-12 Web Integration Service + 16-043 + Panagiotis (Peter) A. Vretanos + + Testbed-12 Web Integration Service + 16-043 - 12-105 + For many years OGC has been developing a suite of standards defining web services interfaces and encodings for geospatial processing. The suite includes a Web Map Service (WMS), a Web Map Tiling Service (WMTS), a Web Feature Service (WFS), a Web Coverage Service (WCS), a Web Catalogue Service (CSW), the Sensor Web (SWE) suite of services, etc. These service interfaces and their implementations have, more or less, been developed independently of one another resulting in isolation and poor integration between them. For example, consider a map generated by a WMS. A client or user cannot easily determine which source data was used to create the map and how to download that source data though an OGC data service such as WFS or WCS. Furthermore when one considers the Publish-Find-Bind paradigm, OGC can only partially support the full potential of this paradigm. This is because OGC structured catalogues can only register services in isolation of other related services and cannot automatically determine the relationships among services and the resources they offer. + +In order to achieve better integration between OGC web services and enhance the publish-find-bind paradigm, this OGC Engineering Report defines and discusses three key elements. These are: + +Defining a new service, called the Web Integration Service (WIS), which allows for the discovery and access to integrated sets of OGC web services deployed at an endpoint. + +Specifying a means of discovering and describing associations between web resources (both OGC and non-OGC). + +Defining extensions to the OGC catalogue to allow the service to harvest and make discoverable a rich set of linked OGC and non-OGC resources. + +The Web Integration Service (WIS) is an aggregation service whose only purpose is to provide a list of references to a suite of other, perhaps related OGC services available at an endpoint. + +A new operation, named GetAssociations, is defined as an extension such that existing OGC services (WMS, WFS, WCS, etc.) may implement this operation in order to support rich auto-discovery. This operation enables OGC web services to externalize their internal association knowledge about their content and relationships to other OGC and external resources. For example, a WMS would know if the source data for a layer it offers is a Shapefile, or a WFS feature type, or another WMS layer (i.e. cascading), or if a WMTS layer exists that renders the same information more efficiently. This internal knowledge can now be externalized via the GetAssociations operation. + +Currently, OGC Catalogues Service instances can harvest the capabilities document of an OGC web service, register that service, register the existence of the individual offerings that the service offers and also register the association between the service and the content it offers. Thus, the entire harvesting process is focused on a single OGC web service and consequently offers a limited scope of discovery. In order to support rich discovery, a catalogue needs to be able to automatically register services found at an endpoint as well as register all known associations among those services, their offerings and other OGC and non-OGC resources. This involves harvesting a service’s capabilities document to determine what content the service offers but it also involves further interrogating the service to determine of what (if any) other associations it is aware. Populated with this enhanced knowledge a client may now use a catalogue to, for example, find the description of feature data and then be able to find the WFS that offer that data, a WMS that renders those features into a map, a WMTS that has a tiled representation of that data, etc. In order to support this kind of rich discovery, a new CSW-ebRIM package is specified that defines ebRIM object types, associations, classifications and stored queries that support the description of integrated OGC web service and their artifacts within the catalogue. - This OGC Engineering Report describes the results of the OWS-9 IP on OWS Context 1.0. OWS Context is a draft OGC candidate standard. The OWS Context activity tested and evaluated the relative benefits of different encoding methods prior to finalization of the candidate standard. OWS Context has been proposed with an Atom encoding, a JSON encoding and an HTML5 encoding. The encoding requirement seeks to understand the level of mass-market acceptance of these different encoding options and their ability to support mash-ups. Each encoding should be evaluated, including examples and recommendations to move forward. Recommendations should enable the OWS Context capability for OGC services while remaining cognizant of implementations using mass-market technologies. - - - OGC® OWS-9 - OWS Context evaluation IP Engineering Report + - - 17-090r1 - Model for Underground Data Definition and Integration (MUDDI) Engineering Report - - + + + GeoAPI 3.0 Implementation Standard + + 2011-04-25 + + GeoAPI 3.0 Implementation Standard + 09-083r3 + Adrian Custer + The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be used for the manipulation of geographic information structured following the specifications adopted by the Technical Committee211 of the International Organization for Standardization (ISO) and by the Open Geospatial Consortium (OGC). This standard standardizes the informatics contract between the client code which manipulates normalized data structures of geographic information based on the published API and the library code able both to instantiate and operate on these data structures according to the rules required by the published API and by the ISO and OGC standards. + 09-083r3 - 17-090r1 - Model for Underground Data Definition and Integration (MUDDI) Engineering Report - 2019-11-25 - - The recently published Underground Infrastructure Concept Development Study (UICDS) Engineering Report [1] examines the present state of underground infrastructure information (UGII), costs and benefits of that state, as well as future opportunities for an improved state. That report describes a number of candidate models for UGII and recommends a number of follow-on activities, including development of a prototype UGII integration model to support subsequent UGII integration and exchange initiatives. The present report describes the design and development of conceptual UGII integration model MUDDI (Model for Underground Data Definition and Interchange). The goal of MUDDI is not to replace existing models but to serve as the basis for integration of datasets from different models, at the levels of detail required to address application use cases described in [1]. MUDDI as described here is a conceptual model which will serve as the basis for one or more conformant and interchangeable physical implementations such as GML (Geographic Markup Language) or SFS (Simple Features SQL). As a prototype model, the current version of MUDDI is also not intended to be final, but to serve as an input to the proposed OGC Underground Infrastructure Pilot and similar activities which will in turn serve to refine and improve the model through implementation and deployment in realistic application scenarios. + - - Josh Lieberman - - OGC Web Feature Service (WFS) Temporality Extension - 2013-06-18 - - Timo Thomas - OGC Web Feature Service (WFS) Temporality Extension - 12-027r2 - 12-027r2 - - + + Testbed-12 LiDAR Streaming Engineering Report + 16-034 + + + 2017-03-09 + + This Engineering Report describes how developments of the Community Sensor Model Working Group (CSMW) can be harmonized with the latest SWE specifications and developments in order to support streaming of LiDAR data with SWE technologies. The report will therefore provide an overview on both initiatives and then describe different options how to integrate LiDAR data streams and SWE technologies. In particular, the ER will consider the results of the activities SOS Compression (LiDAR) Server (A012) and LiDAR Streaming Client (A010) and infer recommendations for future developments. + Simon Jirka, Arne de Wall, Christoph Stasch + Testbed-12 LiDAR Streaming Engineering Report - This OGC Discussion Paper (DP) provides a proposal for a temporality extension for the WFS 2.0 and FES 2.0 standard. It is based on the work of and experiences made in several OWS test beds, in particular OWS-7 and OWS-8, Aviation threads and discussions at the 2011 OGC TC meeting in Brussels, Belgium. This DP partially replaces and advances the document OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0 [4]. - + 16-034 + - + + + 14-044 + Testbed 10 Summary Engineering Report - - - OpenGIS Catalogue Services - Best Practices for for Earth Observation Products - Catalogue Services - Best Practices for for Earth Observation Products - 05-057r4 - The services proposed in this profile are intended to support the identification and subsequent ordering of EO data products from previously identified data collections. The intent of this initial profile is to describe a minimum interface that can be supported by many data providers (satellite operators, data distributors...), most of whom have existing (and relatively complex) facilities for the management of these data. - - 05-057r4 - - Jolyon Martin - 2006-03-20 + + 14-044 + The OGC Testbed 10 was an initiative of OGC’s Interoperability Program to collaboratively extend and demonstrate OGC’s baseline for geospatial interoperability. The majority of work for Testbed 10 was conducted between October 2013 and April 2014. + OGC® Testbed 10 Summary Engineering Report + + 2015-02-02 + Lew Leinenweber + - - A number of OGC service interface standards define SOAP bindings. Despite the current hype around REST or RESTful interfaces, SOAP services are still used intensively, in particular in security-critical environments. A number of OGC Web service interfaces support SOAP bindings (see chapter 6). Unfortunately, those bindings are not fully consistent across the suite of OGC service standards. Differences can be found in terms of SOAP versions, used namespaces, error handling, capabilities documentation, or transport of non-XML data; i.e. aspects that should be harmonized by a cross-standard working group. -This document seeks to provide an overview of the current situation and guidance on future SOAP harmonization across all OGC Web services. A number of change requests have been developed during the development process for this document. Though this document provides recommendations in chapter 8, it is highly recommended to either form a new SOAP working group, or preferably to assign the development of SOAP best practices to reduce the risk of missed requirements and architecture arguments to the newly reformed OWS Common SWG. The best practices could then be applied to all OGC service standards that offer SOAP bindings. - - 15-077r1 - Testbed-11 SOAP Interface Engineering Report: Comparison on the Usage of SOAP Across OGC Web service interfaces - 15-077r1 - Ingo Simonis + + 2023-03-09 + + + 22-017 + 22-017 + Testbed-18: Machine Learning Training Data ER + Testbed-18: Machine Learning Training Data ER + + Sam Lavender, Kate Williams, Caitlin Adams, Ivana Ivánová + + This OGC Testbed 18 Engineering Report (ER) documents work to develop a foundation for future standardization of Training Datasets (TDS) for Earth Observation (EO) applications. The work performed in the Testbed 18 activity is based on previous OGC Machine Learning (ML) activities. TDS are essential to ML models, supporting accurate predictions in performing the desired task. However, a historical absence of standards has resulted in inconsistent and heterogeneous TDSs with limited discoverability and interoperability. Therefore, there is a need for best practices and guidelines for generating, structuring, describing, and curating TDSs that would include developing example software/packages to support these activities. Community and parallel OGC activities are working on these topics. This ER reviews those activities in parallel with making recommendations. + + + + + + Carl Reed + 2018-12-19 + The CDB standard defines a standardized model and structure for a single, “versionable,” virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. + 15-120r5 + Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure + Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure - - + - - 2016-02-03 - OGC® Testbed-11 SOAP Interface Engineering Report: Comparison on the Usage of SOAP Across OGC Web service interfaces + + 15-120r5 - + + - 15-039 + OGC® Routing Pilot ER + 19-041r3 + Routing Pilot ER + 19-041r3 - Envisioning a Tiled Elevation Extension for the OGC GeoPackage Encoding Standard - 15-039 - 2015-08-19 - - Jeff Yutzler - - The GeoPackage Standards Working Group (SWG) presents a vision for storing tiled gridded elevation data in a GeoPackage. - Envisioning a Tiled Elevation Extension for the OGC GeoPackage Encoding Standard - + Sam Meek, Theo Brown, Clemens Portele + The goal of this OGC Routing Pilot Engineering Report (ER) is to document the proof of concept of an Application Programming Interface (API) conforming to a profile of the draft OGC API - Processes specification that allows implementation of vector routing across one or more routing engines. The components implemented in the OGC Open Routing API Pilot 2019 included two clients, interfacing with three implementations of the draft OGC API - Processes specification that in turn communicated with three routing engines. This work resulted in the definition of a proposed common interface and data exchange model supported by all components for requesting, generating and returning routes. + + 2020-01-08 + - - Ordering Services Framework for Earth Observation Products Interface Standard - 06-141r6 - + - + + + 21-057 + OGC GeoPackage WKT for Coordinate Reference Systems Extension + + 21-057 + 2022-10-14 - 2012-01-09 + + This document is a revision to the GeoPackage WKT for Coordinate Reference Systems Extension that previously was published as Annex F.10 of the GeoPackage Encoding Standard 1.3.0 (OGC 12-128r17). This document replaces Annex F.10. The extension defines how to encode coordinate reference systems (CRS) in GeoPackages using the ISO/OGC Well-known text representation of coordinate reference systems [2019] (CRS WKT2) Standard. Specifically, this revision adds coordinate epochs to the encoding of coordinate reference systems in a GeoPackage. + Jeff Yutzler + OGC GeoPackage WKT for Coordinate Reference Systems Extension + + + + + + + + + + + + + + + + + + + + + + + + Documents of type OGC Abstract Specification - - This OGC® standard specifies the interfaces, bindings, requirements, conformance classes, and a framework for implementing extensions that enable complete workflows for ordering of Earth Observation (EO) data products. - 06-141r6 - Ordering Services Framework for Earth Observation Products Interface Standard - Daniele Marchionni, Stefania Pappagallo + + Documents of type OGC Abstract Specification + Documents of type OGC Abstract Specification - - 2019-02-07 - - OGC Testbed-14: Authorisation, Authentication, & Billing Engineering Report - + + 23-044 + + 23-044 + OGC Testbed 19 High Performance Geospatial Computing Engineering Report - - 18-057 - - OGC Testbed-14: Authorisation, Authentication, & Billing Engineering Report - 18-057 - In the context of a generic Earth Observation Exploitation Platform ecosystem, populated by Thematic Exploitation Platforms (TEPs) and Mission Exploitation Platforms (MEPs), which make use of cloud computing resources for Earth Observation data processing, the European Space Agency (ESA) has established two fundamental building blocks within a TEP, with different functions, the Application Deployment and Execution Service (ADES) and the Execution Management Service (EMS). Users interact with a TEP using a Web Client and the TEP contains an EMS and an ADES. The EMS includes most of the control logic, required for deploying and executing applications in different MEPs and TEPs while the ADES instead is responsible for the single application deployment and execution on a specific platform (i.e. TEP and/or MEP). + + Large-scale geospatial analytical computation is critically needed for tackling a wide range of sustainability problems, such as climate change, disaster management, and food and water security. However, such computation often requires high-performance computing (HPC) resources that are not easily accessible or usable by geospatial researchers and practitioners from various domains. To address this challenge, there is a need for developing and standardizing tools and interfaces that can bridge the gap between user frontend and HPC backends and enable effective and efficient use of High-Performance Geospatial Computing (HPGC) resources for geospatial analytics. -The D009 - ADES and EMS Results and Best Practices Engineering Report describes how the two services should be engineered in the Exploitation Platform context. +This OGC Testbed 19 Engineering Report (ER) presents the results of a testbed task that: -This Engineering Report (ER) describes the work performed by the Participants in the Exploitation Platforms Earth Observation Clouds (EOC) Thread of OGC Testbed-14 concerning the interfaces proposed for the Authentication, Authorization, Billing and Quoting topics associated to the EMS and the ADES components. +* evaluated previous and current work in the application of HPC for geospatial analytics, and +* developed draft standards for HPGC resource definitions and processing interfaces. + +This ER provides an overview of the Testbed 19 motivation, objectives, scope, and methodology, as well as a summary of the main findings, recommendations, and future work directions. + +CyberGIS-Compute is reviewed and used as a reference to develop the HPGC API. “CyberGIS-Compute is an open-sourced geospatial middleware framework that provides integrated access to high-performance computing (HPC) resources through a Python-based SDK and core middleware services.”<<CyberGIS_definition>> The OGC API - Processes<<api_processes>> is adopted as the base API for standardizing and developing the HPGC API. A Python client library is developed to demonstrate the process of client generation by leveraging the OpenAPI client stub/model automatic generation capability<<openapi_generator>>. Typical use cases and scenarios are demonstrated and scripted in Jupyter Notebooks. + - Jérôme Gasperi + 2024-04-26 + + Eugene Yu, Liping Di + OGC Testbed 19 High Performance Geospatial Computing Engineering Report - - OGC® Best Practice for Sensor Web Enablement Lightweight SOS Profile for Stationary In-Situ Sensors - This Best Practice document describes a lightweight SOS 2.0 profile for stationary in-situ -sensors. Besides the SOS itself this document also addresses the data formats used by the -SOS: Observations & Measurements 2.0 (O&M) for encoding measurement data and the -Sensor Model Language 2.0 (SensorML) for encoding metadata. Other SWE standards -which provide more specialized functionality are not part of this minimum lightweight -SWE profile. -The aim of this document is to present a common minimum profile of the SOS. The -profile is intended to reduce the complexity of the standard by omitting highly specific -elements that are not necessary for the majority of use cases that occur in practice. At the -same time, the profile is designed in such a way that all SOS implementations that -conform to this profile are also compliant to the according OGC specifications. - Simon Jirka, Christoph Stasch, Arne Bröring + + George Percivall + OGC Smart Cities Spatial Information Framework + Smart Cities Spatial Information Framework + 14-115 + + + - 11-169r1 + + 2015-01-21 + + + This White Paper supports development of a Smart Cities Spatial Information Framework +based on these themes: +K Smart Cities are high-density generators of innovation and information. +K Location information is a major enabler of Smart City technology benefits. +K Benefits of smart technology must be judged by benefits to residents. +K Reuse and repurpose is vital to urban resilience +K Open standards are needed for interoperability, efficiency, application innovation +and cost effectiveness. +Discussion of these themes and this white paper will occur at the OGC Smart Cities +Location Powers Summit in Tokyo on December 2, 2014, +1 the co-located OGC Technical +Committee meeting, and in many other forums in the future. As described in this paper, +there are many standards initiatives that focus on Smart Cities. Most Smart Cities use +cases in some way involve indoor and/or outdoor location, and thus communication about +location is an issue that cuts across the work programs most of the standards +organizations that are involved with Smart Cities. +This white paper builds on the OGC - Directions Magazine webinar: “Making Location +Work for Smart Cities – the Case for Location Standards”2. + This White Paper supports development of a Smart Cities Spatial Information Framework +based on these themes: +- Smart Cities are high-density generators of innovation and information. +- Location information is a major enabler of Smart City technology benefits. +- Benefits of smart technology must be judged by benefits to residents. +- Reuse and repurpose is vital to urban resilience +- Open standards are needed for interoperability, efficiency, application innovation +and cost effectiveness. +Discussion of these themes and this white paper will occur at the OGC Smart Cities +Location Powers Summit in Tokyo on December 2, 2014,1 the co-located OGC Technical +Committee meeting, and in many other forums in the future. As described in this paper, +there are many standards initiatives that focus on Smart Cities. Most Smart Cities use +cases in some way involve indoor and/or outdoor location, and thus communication about +location is an issue that cuts across the work programs most of the standards +organizations that are involved with Smart Cities. +This white paper builds on the OGC - Directions Magazine webinar: “Making Location +Work for Smart Cities – the Case for Location Standards”2. + OGC Smart Cities Spatial Information Framework + 14-115 + + + 16-003r3 + Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values + + Carl Reed + 2018-12-19 + 16-003r3 + - 11-169r1 - Best Practice for Sensor Web Enablement Lightweight SOS Profile for Stationary In-Situ Sensors - + + This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids key words. + Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values - - 2014-02-25 - - 22-004 - Joint OGC OSGeo ASF Code Sprint 2022 Summary Engineering Report - 2022-11-10 - 22-004 - Joint OGC OSGeo ASF Code Sprint 2022 Summary Engineering Report - - - - The subject of this Engineering Report (ER) is a code sprint that was held from the 8th to the 10th of March 2022 to advance support of open geospatial standards within the developer community, whilst also advancing the standards themselves. The code sprint was hosted by the Open Geospatial Consortium (OGC), the Apache Software Foundation (ASF), and Open Source Geospatial Foundation (OSGeo). The code sprint was sponsored by Ordnance Survey (OS), and held as a completely virtual event. - + - - Gobe Hobona, Joana Simoes, Angelos Tzotsos, Tom Kralidis, Martin Desruisseaux - - - Reference Model for the ORCHESTRA Architecture - 07-024 - 07-024 - - - - - 2007-07-26 - - This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It contains a platform-neutral specification of the ORCHESTRA Architecture and a specification framework for the design of ORCHESTRA-compliant service networks across all viewpoints. - Thomas Uslander (Ed.) - Reference Model for the ORCHESTRA Architecture - - + 99-049 + Simple Features Implementation Specification for SQL + 1999-05-05 + Keith Ryden - - - GeoRSS is designed as a lightweight, community driven way to extend existing RSS feeds with simple geographic information. The GeoRSS standard provides for encoding location in an interoperable manner so that applications can request, aggregate, share and map geographically tag feeds. - - - 17-002r1 - - OGC GeoRSS Encoding Standard - 2017-08-18 - GeoRSS Encoding Standard - 17-002r1 - Carl Reed - - - 05-107 - Reference Model for the ORCHESTRA Architecture - Reference Model for the ORCHESTRA Architecture - This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It contains a specification framework for the design of ORCHESTRA-compliant service networks and provides a platform-neutral specification of its information and service viewpoints. - - Thomas Uslander (Ed.) - 2006-01-31 + 99-049 + + OpenGIS Simple Features Implementation Specification for SQL + The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc). + + + + + + - - 05-107 - + 05-077 + Symbology Encoding Implementation Specification + 2006-04-21 + 05-077 + + Symbology Encoding Implementation Specification + Dr. Markus M + This Specification defines Symbology Encoding, an XML language for styling information that can be applied to digital Feature and Coverage data. - - Proposal for WCS Transactional - WCS-T - 06-098 - - 2007-08-13 - - - - - 06-098 - Change Request: WCS: Proposal for WCS Transactional - WCS-T - Michael Gerlek + + 2012-04-06 + HY_Features: a Common Hydrologic Feature Model Discussion Paper + 11-039r2 + Rob Atkinson, Irina Dornblut - Version 1.0 of the Web Coverage Service (WCS) Specification does not address how coverage data gets added to or deleted from a server; it is assumed that some implementation-specific process exists for handling this, likely on the back end (server-side). One of the goals of OWS-4 was to extend WCS to support these operations, generally referred to as - - - OpenGIS Geography Markup Language (GML) Encoding Standard - 2007-10-05 - Geography Markup Language (GML) Encoding Standard - 07-036 - - The OpenGIS® Geography Markup Language Encoding Standard (GML) The Geography Markup Language (GML) is an XML grammar for expressing geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. As with most XML based grammars, there are two parts to the grammar – the schema that describes the document and the instance document that contains the actual data. -A GML document is described using a GML Schema. This allows users and developers to describe generic geographic data sets that contain points, lines and polygons. However, the developers of GML envision communities working to define community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas] that are specialized extensions of GML. Using application schemas, users can refer to roads, highways, and bridges instead of points, lines and polygons. If everyone in a community agrees to use the same schemas they can exchange data easily and be sure that a road is still a road when they view it. - -Clients and servers with interfaces that implement the OpenGIS® Web Feature Service Interface Standard[http://www.opengeospatial.org/standards/wfs] read and write GML data. GML is also an ISO standard (ISO 19136:2007) [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32554 ]. -See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml . - - - - 07-036 - Clemens Portele - - + + + + 11-039r2 + + HY_Features: a Common Hydrologic Feature Model Discussion Paper + This document describes a conceptual model for the identification of hydrologic features independent from geometric representation. This model allows common reference to hydrologic features across scientific sub-disciplines in hydrology. The Hydrologic Feature Model, HY_Features, is designed as a set of interrelated Application Schemas using ISO 19103 Conceptual Schema Language and ISO 19109 General Feature Model. It is factored into relatively simple components that can be reviewed, tested and extended independently. - - 2018-01-08 - 17-043 - Testbed-13: Executable Test Suites and Reference Implementations for NSG WMTS 1.0 and WFS 2.0 Profiles with Extension - - This Engineering Report (ER) describes the development of the compliance tests and implementation in GeoServer of the Web Feature Service (WFS) 2.0 and Web Map Tile Service (WMTS) 1.0 National System for Geospatial Intelligence (NSG) profiles. The NSG of the United States (US) National Geospatial Intelligence Agency (NGA) is the combination of technologies, policies, capabilities, doctrine, activities, people, data and communities needed to produce geospatial intelligence (GEOINT) in an integrated, multi-intelligence, multi-domain environment. The work can be grouped into four main topics: - -critical review of the NSG profiles for WFS 2.0 and WMTS 1.0 - -implementation of the profiles in GeoServer - -validation of the implementation using OGC Compliance tests and tools - -lessons learn during the implementation of these profiles and their validation - -Both NSG profiles are Class 2 profiles. WMTS profiles OGC WMTS 1.0. WFS profiles the DGIWG Profile of OGC WFS 2.0. The first topic provides a review of these profiles along with a description of the main extensions and restrictions introduced by them. - -The second topic covers the implementation of the NSG profiles in GeoServer. It describes the software architecture and technical decisions, along with the deployment and configuration of the server. - -The third topic covers the validation process of the implementation using OGC validation (sometimes referred to as CITE) tests and tools. It also covers how the tests can be run and how to configure GeoServer for these tests. - -The last topic contains an evaluation of the work, reached goals, lessons learned and the best practices that can be applied in future work. - OGC Testbed-13: Executable Test Suites and Reference Implementations for NSG WMTS 1.0 and WFS 2.0 Profiles with Extension + + OGC® Sensor Web Enablement Architecture + 06-021r4 + + 2008-08-20 + + Sensor Web Enablement Architecture + + 06-021r4 - + Ingo Simonis + This document describes the architecture implemented by Open Geospatial Consortium’s (OGC) Sensor Web Enablement Initiative (SWE). In contrast to other OGC SWE stan-dards, this document is not an implementation standard. - - 17-043 - Nuno Oliveira - - This OGC document provides an analysis of the mapping between the NOAA Web Gridded Document Service (WGDS) and the OGC Web Coverage Service (WCS) and describes an adapter which translates WCS 2.0 requests to WGDS requests and then translates WGDS responses to WCS 2.0 responses. -This Engineering Report was prepared as a deliverable for the OGC Testbed 10 (Testbed-10) initiative, specifically the Testbed 10 Aviation Thread. - - - 0000-00-00 + + 22-018 + Testbed-18: Secure Asynchronous Catalog Engineering Report + + This OGC Testbed-18 Engineering Report (ER) describes the results of the Secure, Asynchronous Catalogs Task in the Testbed-18 Catalogs, Filtering, and Moving Features (CMF) thread. This task explored the following. + +How search processes that are supported in a classical OGC Catalogue Service for the Web (CSW)/ISO 19115 environment can be supported through tailoring of the OGC API-Records specification. +How an asynchronous catalog scenario can be supported in which metadata publishers push new data to catalog instances that lead to new or updated catalog entries and how subscribers are informed about these updates. +How Data Centric Security (DCS) can be applied in combination with OGC API-Records to allow encrypted delivery and access of catalog metadata between communication partners. + 2023-01-05 + Testbed-18: Secure Asynchronous Catalog Engineering Report + Yves Coene, Christophe Noel - + - Mark Hughes - - 14-038r1 - Testbed 10 Engineering Report: Aviation Dissemination of Weather Data - OGC® Testbed 10 Engineering Report: Aviation Dissemination of Weather Data - 14-038r1 + 22-018 + - - 07-063 - Web Map Services - Application Profile for EO Products - 07-063 - Thomas H.G. Lankester + + - 2007-08-15 + 07-004 + + 07-004 + GeoDDS Mass Market + Panagiotis (Peter) A. Vretanos + + This OpenGIS(r) document describes the API for two web services capable of generating several simplified data formats including GeoRSS and the Basic XML Feature Schema +(BXFS). + + 2007-05-07 + - - Web Map Services - Application Profile for EO Products - - This OGC document specifies a constrained, consistent interpretation of the WMS specification that is applicable to government, academic and commercial providers of EO products. - - + GeoDDS Mass Market (formerly GeoRSS) Interoperability Program Report - - 05-110 - Feature Portrayal Service - - This document specifies the interface to a Feature Portrayal Service (FPS), which applies styles to digital features to produce a map image. The styles applied are identified or specified by the client, and are applied to digital feature data retrieved from a Web Feature Service (WFS) identified by the client. - + + 03-064r1 + GO-1 Application Objects Report + This document is a draft of the OpenGIS + 03-064r1 + 2003-06-12 + GO-1 Application Objects Report - 2006-04-19 - - Feature Portrayal Service - 05-110 - Arliss Whiteside, Bill Woodward, co-editor - + + - - - 08-125r1 - KML Standard Development Best Practices - - 2009-02-04 - This OGC® Best Practices Document provides guidelines for developing the OGC KML standard in a manner that best serves and supports the KML application developer and user communities. It applies to the extension of KML by application developers and the subsequent enhancement of the KML standard by the OGC. - 08-125r1 + - Tim Wilson, David Burggraf - - - - OGC® KML Standard Development Best Practices - + Phillip C. Dibner - - CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211. - -The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. - - 12-019 - 12-019 - City Geography Markup Language (CityGML) Encoding Standard - - - OGC City Geography Markup Language (CityGML) Encoding Standard - - + + - Gerhard Gröger, Thomas H. Kolbe, Claus Nagel, Karl-Heinz Häfele - 2012-04-04 - - - - - - - - - - - - - - - - - - OGC CoverageJSON Community Standard - - 2023-08-22 - Based on JavaScript Object Notation (JSON), CoverageJSON is a format for publishing spatiotemporal data to the Web. The primary design goals are simplicity, machine and human readability and efficiency. While other use cases are possible, the primary CoverageJSON use case is enabling the development of interactive visual websites that display and manipulate environmental data within a web browser. - -Implementation experience has shown that CoverageJSON is an effective, efficient format, friendly to web and application developers, and therefore consistent with the current OGC API developments. CoverageJSON supports the efficient transfer from big data stores of useful quantities of data to lightweight clients, such as browsers and mobile applications. This enables straightfoward local manipulation of the data, for example, by science researchers. Web developers often use and are familiar with JSON formats. + OGC Testbed-14: Federated Clouds Engineering Report + Craig A. Lee + 18-090r2 + 2019-10-23 + + + + The geospatial community has had an on-going challenge with being able to share data and compute resources in dynamic, collaborative environments that span different administrative domains. For these types of requirements, the concept of federation has been developed. The near-term goal of the Federated Cloud task in Testbed-14 is to demonstrate a specific data-sharing scenario among two or more administrative domains using existing security tooling, e.g., OpenID Connect and OAuth. The main details of this work are reported as part of the Security Engineering Report (ER) [1]. This Federated Cloud ER will dovetail with the Security ER to: -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. +Coordinate across all federation-related tasks in Testbed-14, including the Earth Observation Cloud and Workflow tasks, -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. +Understand the overall federation design space, -The simplest and most common use case is to embed all the data values of all variables in a Coverage object within the CoverageJSON document, so that it is “self-contained”. Such a standalone document supports the use of very simple clients. +Analyze and critique the scope, trade-offs and limitations of the federation capabilities being built and demonstrated in Testbed-14, -The next simplest use case is to put data values for each variable (parameter) in separate array objects in separate CoverageJSON documents which are linked from the Coverage object. This is useful for a multi-variable dataset, such as one with temperature, humidity, wind speed, etc., to be recorded in separate files. This allows the client to load only the variables of interest. +Identify and prioritize possible incremental development tasks for subsequent testbeds, and -A sophisticated use case is to use tiling objects, where the data values are partitioned spatially and temporally, so that a single variable’s data values would be split among several documents. A simple example of this use case is encoding each time step of a dataset into a separate file, but the tiles could also be divided spatially in a manner similar to a tiled map server. - OGC CoverageJSON Community Standard - 21-069r2 +Liaison with groups external to OGC, such as the NIST/IEEE Joint WG on Federated Cloud, to promote the further development and adoption of federated capabilities, and ultimately international standards. + 18-090r2 + Testbed-14: Federated Clouds Engineering Report + + + + + + John Herring + 2001-05-10 + Topic 1 - Feature Geometry + 01-101 + Topic 01 - Feature Geometry + + + Same as ISO 19107, available at http://www.iso.org. + 01-101 + + + 17-086r3 + Peter Trevelyan, Paul Hershberg, Steve Olson + 2021-03-22 + The purpose of the GetPolygon operation is to extract data contained within a polygon defined either by a set of points or the radius and position of a circle point. The need for the GetPolygon operation stems from active members of the OGC MetOcean Domain Working Group (DWG) who saw a manifest need for extraction of such information from gridded datasets. + +This work has been done by members of the OGC MetOcean Domain Working Group. - 21-069r2 - - Chris Little, Jon Blower, Maik Riechert - + + + 17-086r3 + MetOcean Application profile for WCS2.1: Part 2 MetOcean GetPolygon Extension + OGC MetOcean Application profile for WCS2.1: Part 2 MetOcean GetPolygon Extension + + - + + 15-011r2 + Testbed-11 Multiple WFS-T Interoperability + + + OGC Testbed-11 Multiple WFS-T Interoperability - Adrian Custer + 2016-01-28 + + + Panagiotis (Peter) A. Vretanos + 15-011r2 + This document describes the work done in the OGC Testbest-11 to support multiple WFS-T instance interoperability by way of a transaction scenario involving the interaction between clients and multiple WFS-T servers as well as the interaction between the servers themselves, especially in the use case of enterprise-to-enterprise data synchronization. +The document presents an overview of the transaction scenario, the components used to implement the scenario in the OGC Testbed-11 demo and the new capabilities added to the WFS-T server to support the scenario. + + + + + + SensorThings API Part 1: Sensing + 15-078r6 + 2016-07-26 - + + Steve Liang, Chih-Yuan Huang, Tania Khalafbeigi + - GeoAPI 3.0 Implementation Standard - 09-083r3 - 09-083r3 - GeoAPI 3.0 Implementation Standard - The GeoAPI Implementation Standard defines, through the GeoAPI library, a Java language application programming interface (API) including a set of types and methods which can be used for the manipulation of geographic information structured following the specifications adopted by the Technical Committee211 of the International Organization for Standardization (ISO) and by the Open Geospatial Consortium (OGC). This standard standardizes the informatics contract between the client code which manipulates normalized data structures of geographic information based on the published API and the library code able both to instantiate and operate on these data structures according to the rules required by the published API and by the ISO and OGC standards. - 2011-04-25 - + The OGC SensorThings API provides an open, geospatial-enabled and unified way to interconnect the Internet of Things (IoT) devices, data, and applications over the Web. At a high level the OGC SensorThings API provides two main functionalities and each function is handled by a part. The two parts are the Sensing part and the Tasking part. The Sensing part provides a standard way to manage and retrieve observations and metadata from heterogeneous IoT sensor systems. The Tasking part is planned as a future work activity and will be defined in a separate document as the Part II of the SensorThings API. + 15-078r6 + OGC SensorThings API Part 1: Sensing - - 08-001 - Loosely Coupled Synchronization of Geographic Databases in the CGDI - 2008-04-29 - OGC® Loosely Coupled Synchronization of Geographic Databases in the Canadian Geospatial Data Infrastructure Pilot + + + OpenGIS Geography Markup Language (GML) Encoding Specification + 03-105r1 + Geography Markup Language (GML) Encoding Specification + + The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features. + + 2004-04-19 + + Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside + + 03-105r1 + + + 09-033 + + This document defines a basic SensorML profile for discovery purposes. Besides a minimum set of metadata also the structure of according SensorML documents is defined in order to ensure a consistent metadata description. This goal is achieved by a set of Schematron rules that can be used to validate if a given SensorML document complies with the profile described in this engineering report. + + OWS-6 SensorML Profile for Discovery Engineering Report + 09-033 + + 2009-07-29 + + Simon Jirka, Arne Bröring - This Discussion Paper documents results from the Interoperability Program CGDI Pilot and describes a suite of services that enable the sharing of geographic information across organizations for the purposes of: geographic database synchronization in support of a spatial data infrastructure; geographic database modification suggestions from trusted and un-trusted sources; and the transmission of geographic information in emergency notification events. - -These services are called the Update Feed Service; Feedback Feed Service; and Emergency Alert Service respectively. Their information encodings are all based on the Atom Syndication Format, extended with GML and WFS Filter encodings to support geospatial requirements, and were implemented in the Canadian Geospatial Data Infrastructure Pilot. - - Raj Singh - 08-001 - - - + OWS-6 SensorML Profile for Discovery Engineering Report - - OGC API - Common - Part 1: Core - 19-072 - 19-072 - The OGC has extended its suite of Standards to include Resource Oriented Architectures and Web APIs. In the course of developing these Standards, some practices proved to be common across multiple OGC Web API Standards. These common practices are documented in the OGC API — Common Standard. The OGC API - Common Standard is a multi-part standard that specifies reusable building-blocks that can be used in the construction of OGC API Standards. This document presents Part 1, the Core, of the OGC API – Common Standard. Standards developers will use these building-blocks in the construction of other OGC Standards that relate to Web APIs. The result is a modular suite of coherent API standards which can be adapted by a system designer for the unique requirements of their system. - -The purpose of the OGC API — Common — Part 1: Core Standard (API-Core) is to define those fundamental building blocks and requirements which are applicable to all OGC Web API Standards. + + + - 2023-03-28 + 10-028r1 + GIGAS Methodology for comparative analysis of information and data management systems + 10-028r1 + This document has been written on the basis of a methodology developed within the GIGAS Support Action financed by the European Commission in order to address the convergence of global initiatives like GEOSS and the European interoperability initiatives developed in the context of the GMES programme like HMA - Heterogeneous Missions Accessibility and the INSPIRE spatial data infrastructure legislation. + + Andrea Biancalana, Pier Giorgio Marchetti, Paul Smits + + 2010-06-04 + GIGAS Methodology for comparative analysis of information and data management systems - - + + + 18-045 + + OGC Testbed-14: Next Generation Web APIs - WFS 3.0 Engineering Report + + 2019-03-07 + Jeff Harrison, Panagiotis (Peter) A. Vretanos + Next Generation Web APIs - WFS 3.0 Engineering Report + 18-045 - Charles Heazel - OGC API - Common - Part 1: Core - + + + The objective of the Next Generation APIs - WFS 3.0 effort in OGC Testbed-14 was to develop and test the Web Feature Service (WFS) version 3.0 candidate standard. The initiative assessed OpenAPI, security based on OpenID Connect and OAuth 2.0 and WFS 3.0 extensions. The effort also began to assess methods to ease geospatial enterprise transition to next generation Application Programming Interfaces (APIs). + +The purpose of this effort was not to preempt other next generation work taking place in OGC, but rather to inform and complement that work. + +This Engineering Report (ER) describes the implementations and experiments conducted by OGC Testbed-14 participants to test next generation Web APIs. It includes descriptions of APIs to simplify and secure access to geospatial feature resources, and was tested in a scenario that showed how WFS 3.0 can support humanitarian relief activities. + - 2015-10-01 - 15-056 Testbed 11 Catalogue Service and Discovery Engineering Report 15-056 - - Wenwen Li, Sheng Wu - - - + + + Wenwen Li, Sheng Wu OGC® Testbed 11 Catalogue Service and Discovery Engineering Report - + 15-056 + + 2015-10-01 + + This OGC Testbed 11 Engineering Report provides a comprehensive review and comparison in terms of architecture, functionality, and usability of the OGC catalogue service standards CSW 2.0.2 and CSW 3.0. We are especially interested in how well the two standards provide support for open searches and federated distributed searches in current distributed computing paradigms. We also evaluated the support of semantic searches using different strategies, including (1) semantic mediation, a.k.a. ontology-based query expansion (Li et al. 2008; Li et al. 2011), (2) semantic association, which enables current catalogue information models to support semantic search (Li et al. 2014; Li et al. 2015), and (3) complete renovation of the CSW information model to be a triple store and utilize Semantic Web technology (Berner-Lee 2001) to support semantic query and data retrieval. Scenarios to search for hydrological data are developed to evaluate the performance of catalogue searching using the above strategies. Recommendations for adoption of CSW standards as well as tasks in advancing catalogue search and data discovery in future testbeds is also discussed. - - 01-029 - Geography Markup Language - - - Geography Markup Language - 2001-02-20 - 01-029 - The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features. - Ron Lake + + + OGC Benefits of Representing Spatial Data Using Semantic and Graph Technologies + 19-078r1 + + + 2020-10-05 + + + Joseph Abhayaratna, Linda van den Brink, Nicholas Car, Rob Atkinson, Timo Homburg, Frans Knibbe, Kri + This paper does four things. Firstly, it describes the benefits of representing geospatial data using semantics, graph, and web technologies. Secondly, it gives an overview of the current capabilities of the GeoSPARQL standard, showing that many benefits of semantic and graph technologies are already within reach. Thirdly, it outlines some shortcomings of the existing GeoSPARQL implementation specification that, if addressed, would unlock its potential to a greater extent, and could significantly increase its user base. Finally, it identifies other related activities that are current at the time of editing this paper. In doing so, it establishes liaison’s between the different activities in an attempt to achieve alignment. + +The purpose of this paper is to provoke further thought about a best course for further development of the GeoSPARQL standard, and to invite active involvement in that development. Particularly, the involvement of people and organizations that until now have not been able to put GeoSPARQL to good use, either because of perceived limitations or because of unfamiliarity with the standard, will be highly valued. Also, since one development under consideration is to make provisions for use of GeoSPARQL with non-geographic spatial data, those that see opportunities for using spatial data in a broad sense together with the aforementioned technologies are cordially invited to share their views. + OGC Benefits of Representing Spatial Data Using Semantic and Graph Technologies + 19-078r1 + + + Paul Watson + + + This document describes the purpose and function of the Topology Quality Assessment Service developed and deployed within the Geo-processing workflow thread of the OWS4 interoperability testbed. + 2007-06-06 + 07-007r1 + OWS4 - Topology Quality Assessment Interoperability Program Report + + OWS4 - Topology Quality Assessment Interoperability Program Report - + + 07-007r1 - - OGC City Geography Markup Language (CityGML) 3.0 Conceptual Model Users Guide - 20-066 - CityGML is an open conceptual data model for the storage and exchange of virtual 3D city models. It is defined through a Unified Modeling Language (UML) object model. This UML model extends the ISO Technical Committee 211 (TC211) conceptual model standards for spatial and temporal data. Building on the ISO foundation assures that the man-made features described in the City Models share the same spatial-temporal universe as the surrounding countryside within which they reside. The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. - -This Users Guide provides extended explanations and examples for the individual concepts that are defined in the CityGML 3.0 Conceptual Model Standard. Both documents, the Conceptual Model Standard and the Users Guide, are mutually linked to facilitate navigation between corresponding sections in these documents. - City Geography Markup Language (CityGML) 3.0 Conceptual Model Users Guide - 20-066 + + 2010-10-27 + 09-146r1 + This document specifies the GML coverage structure to be used by OGC standards. + Peter Baumann + 09-146r1 + GML Application Schema - Coverages + - - Charles Heazel - - - - 2021-09-13 - - - 3D Data Container Engineering Report - - 3D Data Container Engineering Report - 20-029 - This OGC Engineering Report documents the goals, activities, experiences, and outcomes of the 3D Data Container and Tiles API Pilot. Participants in the Pilot cooperatively defined a GeoVolume (3D Geospatial Volume) resource and developed a GeoVolumes API based on the concept to provide access to different 2D and 3D geospatial dataset distributions organized by region of interest. Multiple client and server implementations of the GeoVolumes API successfully carried out technology interchange experiments that demonstrated the value of the API for improving interoperability between 3D geospatial data formats. + + OGC® GML Application Schema - Coverages + + + + 03-002r9 + Binary Extensible Markup Language (BXML) Encoding Specification + Binary Extensible Markup Language (BXML) Encoding Specification + + 2006-01-18 + + Craig Bruce + + + This OGC Best Practices document specifies a binary encoding format for the efficient representation of XML data, especially scientific data that is characterized by arrays of numbers. This encoding format is applicable to any application that uses XML format. + + 03-002r9 + + + + Recent years have seen a significant increase in the use of three-dimensional (3D) data in the Internet of Things (IoT). The goal of the 3D IoT Platform for Smart Cities Pilot was to advance the use of open standards for integrating environmental, building, and IoT data in Smart Cities. Under this initiative a proof of concept (PoC) has been conducted to better understand the capabilities to be supported by a 3D IoT Smart City Platform under the following standards: CityGML, IndoorGML, SensorThings API, 3D Portrayal Service, and 3D Tiles. + - 20-029 - 2020-10-22 - Timothy Miller, Gil Trenum, Josh Lieberman + 3D-IoT Platform for Smart Cities Engineering Report + 19-073r1 + 19-073r1 + + OGC 3D-IoT Platform for Smart Cities Engineering Report + + 2020-07-29 - + Volker Coors - - OWS-5 CITE Summary Engineering Report - This document summarizes work completed in the OWS5 Compliance & Interoperability Test & Evaluation thread. This document is applicable to the OGC Compliance Test Program. - - + + - 08-084r1 - Jen Marcus + 2011-10-18 + Corrigendum 2 for OGC Web Services Common Specification v 1.1.0 - Exception Report + Corrigendum 2 for OGC Web Services Common Specification v 1.1.0 - Exception Report + 11-158 + Jim Greenwood - CITE Summary Engineering Report - 08-084r1 - - - 2008-08-20 - - - - + + 11-158 + This document defines the corrigendum change notes for <OGC Web services Common Specification v1.1.0. This document was approved by the OGC membership on December 2010 . As a result of the Corrigendum process, there were edits and enhancements made to this standard to correct typographic errors, schema errors, or some deficiency that prevented proper use of this standard. This document provides the details of those edits, deficiency corrections, and other corrects. It also documents those items that have been deprecated. + + - - - 07-001r3 - Requirements for some specific simple solid, plane and line geometry types - Requirements for some specific simple solid, plane and line geometry types - Simon Cox + + + + 07-063r1 + Thomas H.G. Lankester + This OGC document specifies a constrained, consistent interpretation of the WMS specification that is applicable to government, academic and commercial providers of EO products. + 2009-11-05 + Web Map Services - Application Profile for EO Products + 07-063r1 + Web Map Services - Application Profile for EO Products + - 07-001r3 + + + + + 10-195 + Requirements for Aviation Metadata + This OGC Discussion Paper details the user requirements for metadata in the aviation domain. The requirements are at a high-level. + Requirements for Aviation Metadata + 2011-03-28 + OGC Aviation Domain Working Group + - 2007-05-02 - - This specification describes requirements for specific geometry types, including some simple solids, and planes and lines defined using an implicit parameterization. + 10-195 + + - - - 2006-10-24 - EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 - 06-131 - - + + + 2018-01-18 + Roger Brackin - EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 - 06-131 - Renato Primavera - + + The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives. + +· Apply Open Geospatial Consortium (OGC) principles and practices for collaborative development to existing standards and technology in order to prototype an IoT approach to sensor use for incident management. + +· Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability. + +· Development of profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability. + +· Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario. + +These principles continued through the IoT Pilot Extension, with additional objectives of: + +· Integration into the existing Next Generation First Responder (NGFR) Apex development program process as part of Spiral 1; + +· Defining steps to begin the integration of existing incident management infrastructure, e.g., pulling in National Institute of Emergency Management (NIEM) message feeds; and + +· Demonstration and experimentation in a ‘realistic’ incident environment using two physically separate sites–an incident site within an active first responder training facility (Fairfax County Lorton site), and a command center (DHS S&T Vermont Avenue facility). + +The initial Pilot activity has been documented in three OGC public engineering reports. The present report describes and documents the additional activities and innovations undertaken in the Extension. - This document describes the Data Model of Earth Observation Products for the OGC + Incident Management Information Sharing (IMIS) Internet of Things (IoT) Extension Engineering Report + 16-092r2 + Incident Management Information Sharing (IMIS) Internet of Things (IoT) Extension Engineering Report + + 16-092r2 + - - Geospatial User Feedback Standard: Conceptual Model - 15-097r1 - OGC® Geospatial User Feedback Standard: Conceptual Model - This standard defines a conceptual Geospatial User Feedback (GUF) data model. Geospatial User Feedback is metadata that is predominantly produced by the consumers of geospatial data products as they use and gain experience with those products. This standard complements existing metadata conventions whereby documents recording dataset characteristics and production workflows are generated by the creator, publisher or curator of a data product. As a part of metadata, the GUF data model reuses some elements of ISO 19115-1:2014 (the updated version of the OGC Abstract Specification Topic 11) but not the general structure. This selective use of ISO metadata elements prioritizes future interoperability with developing ISO metadata models. This standard is designed to be used combination with an encoding standard. Initially an XML encoding following the ISO 19139 encoding rules is specified in a separate OGC implementation standard (OGC 15-098). In the future other encodings may be defined, including examples such as the use of JSON-LD based on parts of schema.org. - - + + + + 2016-01-25 + 15-051r3 + Testbed-11 OGC IP Engineering Report Geo4NIEM Architecture Design and Implementation Guidance and Fact Sheet + + + 15-051r3 + Testbed-11 OGC IP Engineering Report Geo4NIEM Architecture Design and Implementation Guidance and Fact Sheet - Joan Masó, Lucy Bastin - - 15-097r1 + The goal of the Geo4NIEM thread in Testbed 11 was to assess the potential for the National Information Exchange Model (NIEM) to be combined with security tags from Intelligence Community (IC) Data Encoding Specifications for information exchange. The assessment included reviewing Information Exchange Package Documentation (IEPD) populated with relevant content and IC security tags – and then deploying these instance documents on Open Geospatial Consortium (OGC) standards enabled Web Services for testing. The security tags included Information Security Marking Metadata (ISM) and Need-to-Know (NTK) Metadata for secure information exchange. +The assessment included reviewing example IEPDs and performing tests and demonstrations using OGC web services, such as Transactional Web Feature Services (WFS-T), Policy Enforcement Points (PEPs) and OGC Attribute Stores to process geographic feature with NIEM components and security tags. The Test and Demonstration included, but was not limited to, feature retrieval and transactions. Results were documented in this task to provide a preliminary architecture for Geo4NIEM in Testbed 11, and were described in technical detail in other OGC Testbed 11 Engineering Reports. +This document describes background considerations – and an overview of the services, data encodings and access control frameworks that compose the Geo4NIEM Testbed 11 architecture. This document must be reviewed in conjunction with the following Testbed 11 Geo4NIEM ERs: +• 15-048 Testbed11_Engineering_Report_NIEM-IC Data Encoding Specification Assessment and Recommendations +• 15-047 Testbed11_Engineering_Report NIEM-IC Feature Processing API using OGC Web Services +• 15-050 Testbed11_Engineering_Report Test and Demonstration Results for NIEM using IC Data Encoding Specifications + - - 2016-12-22 + Jeff Harrison - - - - - - - - - - - - - - - - - - - - - - + + + 21-035r1 + OGC Testbed-17: Model-Driven Standards Engineering Report + + + 21-035r1 + This OGC Testbed 17 Engineering Report is deliverable D022 of the OGC Testbed 17 initiative performed under the OGC Innovation Program, incorporating the D022, D143 and D144 tasks that have produced Model Driven Architecture (MDA) tools. + +This ER: + +details state-of-the-art analyses of existing MDA tools with their capabilities and limits; and + +provides clear recommendations on how model-driven design can be fully exploited in the context of rich data model and API design efforts. + + - Documents of type Best Practice - deprecated - Documents of type Best Practice - deprecated - - Documents of type Best Practice - deprecated + OGC Testbed-17: Model-Driven Standards Engineering Report + 2022-03-31 + + Ronald Tse, Nick Nicholas + - - 2020-07-08 - 19-084 - Vector Tiles Pilot 2: Vector Tiles Filtering Language Engineering Report - - Andrea Aime + + The services proposed in this profile are intended to support the identification and subsequent ordering of EO data products from previously identified data collections. The intent of this initial profile is to describe a minimum interface that can be supported by many data providers (satellite operators, data distributors...), most of whom have existing (and relatively complex) facilities for the management of these data. + 2006-03-20 + Catalogue Services - Best Practices for for Earth Observation Products + 05-057r4 - - The OGC Vector Tiles Pilot 2: Vector Tiles Filtering Language Engineering Report (ER) defines a filter language for vector data delivered as tiles (also known as vector tiles). The language applies to vector tiles served through implementations of the OGC API – Features standard and the draft OGC API - Tiles specification, but can be generally applied on all services supporting filtering by attributes. - -The ER further includes an assessment of filter languages, styles and online/offline symbol sharing for GeoPackages, OGC API - Features and OGC API - Tiles implementations for accuracy and completeness in applications that render vector tiles at local to regional scales. - OGC Vector Tiles Pilot 2: Vector Tiles Filtering Language Engineering Report - 19-084 - + + + OpenGIS Catalogue Services - Best Practices for for Earth Observation Products + 05-057r4 + + Jolyon Martin - + - - Arliss Whiteside, John Evans - - 2007-08-29 - 07-067r2 - - Web Coverage Service (WCS) Implementation Specification Corrigendum 1 - 07-067r2 - OpenGIS Web Coverage Service (WCS) Implementation Specification Corrigendum 1 - This version 1.1.1c1 of the Web Coverage Service (WCS) Specification supersedes previous -version 1.1.0 [OGC 06-083r8]. Technical changes from the version 1.0 include building on -the OGC Web Services Common Specification [OGC 06-121r3] and a substantially revised -Capabilities schema; new schemas and syntax for operation requests (GetCoverage, -DescribeCoverage); and integration with GML 3.1. The changes in WCS 1.1.1c1 from WCS -1.1.0 are summarized in [OGC 07-066r2]. + + OGC KML + + Tim Wilson + KML is an XML language focused on geographic visualization, including annotation of maps and images. Geographic visualization includes not only the presentation of graphical data on the globe, but also the control of the user's navigation in the sense of where to go and where to look. + 07-147r2 + 2008-04-14 + 07-147r2 + KML + + - - + - + + 12-104r1 + OWS-9 Engineering Report - CCI - Single Point of Entry Global Gazetteer + OGC® OWS-9 Engineering Report - CCI - Single Point of Entry Global Gazetteer + This document provides a technical description of the Single Point of Entry Global Gazetteer (SPEGG) implemented for the OWS9 test bed. The SPEGG integrates two gazetteers – a copy of the USGS gazetteers containing domestic names (hosted by CubeWerx Inc.) and the NGA gazetteer containing foreign names (originally hosted at NGA but currently hosted by Intergraph Corp.). Both integrated gazetteers and the SPEGG implement the Web Feature Service (WFS) standard. + + + 12-104r1 + 2013-06-18 Panagiotis (Peter) A. Vretanos - + - CHISP-1 Engineering Report - 13-053r1 - This document provides a technical description of the work completed for the Climatology-Hydrology Information Sharing Pilot, Phase 1 project. -This document describes a profile of SOS, the NRCan GIN SOS 2.0 profile, developed in order to define a baseline of interoperability among the sensor observation services used in the project. -This document describes the use cases used to drive the component development during the project. The first use case was a flood scenario that involved exchanging cross-border hydrologic data with a unified alert service. The second use case involved calculating nutrient loads to the Great Lakes, which also involved the cross-border exchange of analytic data. -This document describes each component developed during the project and the challenges encountered and overcome during the development. The newly developed components include a nutrient load calculation client, a SOS integrating water quality data form the U.S. and Canada, a nutrient load calculation service, an upstream gauge service, a subscription client, and an event notification service composed of a number of sub-components including a subscription broker, an observation harvester and a CAP alert client. - + + + + + + + Documents of type Specification Application Profile - deprecated + + + Documents of type Specification Application Profile - deprecated + Documents of type Specification Application Profile - deprecated + + + + 14-009r1 + Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context + 2014-04-15 + This document identifies the generic rules for obtaining JSON documents directly from existing XML documents and schemas elements. It is primordially targeting the OWS Context JSON Encoding design, but is presented in a generic approach. Such generic approach can offer the guidelines for other OGC services, when defining and using JSON encodings. + 14-009r1 - 13-053r1 - 2014-02-24 - - OGC® CHISP-1 Engineering Report + OGC® Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context + + Pedro Gonçalves + - + + + + + + + + + + + + + + + + + + + + + + Josh Lieberman, Lou Reich, Peter Vretanos + + 2003-01-17 + OGC Web Services UDDI Experiment + 03-028 + This document lists the design principles, requirements, and experimental results for future versions of a potential OGC - UDDI (Universal Discovery, Description, and Integration) profile of the OGC Catalog Implementation Specification. Specifically, it describes the usage scenarios, workplan, and experimental results for discovery of OGC services (including registries) through the UDDI interface using SOAP (Simple Object Access Protocol) messaging protocols. The baseline for this experiment is the specification for UDDI version 2 and use of private UDDI implementations. + + 03-028 + + + OGC Web Services UDDI Experiment + + + + Grid Coverage Service Implementation Specification + 01-004 + + 01-004 + Louis Burry - 2008-02-20 - Clemens Portele - - - Revision Notes for OpenGIS® Implementation Specification: Geographic information - Geography Markup Language Version 3.2.1 - 07-061 - + + OpenGIS Grid Coverage Service Implementation Specification + 2001-01-12 - This document provides revision notes for version 3.2.1 of the OpenGIS® Implementation Specification Geographic information – Geography Markup Language (GML). - 07-061 - Revision Notes for OpenGIS® Implementation Specification: Geographic information - Geography Markup Language Version 3.2.1 + **This document has been retired. It is not supported. You should consider using Web Coverage Service.** + + This specification was designed to promote interoperability between software implementations by data vendors and software vendors providing grid analysis and processing capabilities. + - - OGC Testbed-17: Model-Driven Standards Engineering Report - This OGC Testbed 17 Engineering Report is deliverable D022 of the OGC Testbed 17 initiative performed under the OGC Innovation Program, incorporating the D022, D143 and D144 tasks that have produced Model Driven Architecture (MDA) tools. + + 18-049r1 + Application Package Engineering Report + + + Paulo Sacramento + + 18-049r1 + + OGC Testbed-14: Application Package Engineering Report + + This Engineering Report (ER) describes the work performed by the Participants in the Exploitation Platforms Earth Observation Clouds (EOC) Thread of OGC Testbed-14 in regard to the Application Package (AP). -This ER: +The AP serves as a means to convey different kinds of information describing a certain application - often, but not necessarily, an Earth Observation data processing algorithm - so that different elements of an ecosystem generically known as an Exploitation Platform can exchange information among themselves in a standard and interoperable way. The AP guarantees that, despite potentially very heterogeneous implementations and implementing entities, applications are treated equally. The AP also guarantees that the Earth Observation scientist who developed it on the one hand is shielded from infrastructure details and heterogeneity and on the other hand benefits from the ability to execute the same application on different infrastructure. -details state-of-the-art analyses of existing MDA tools with their capabilities and limits; and +Given its suitability for conveying a Common Operating Picture (COP), in OGC Testbed-13 the OGC Web Services (OWS) Context standard had been chosen as the basic encoding for the Application Package. Despite serious consideration, and while acknowledging the advantages of that approach, the consensus among Participants was not to continue along this path in Testbed-14 but instead to opt for an AP encoding, consisting of a WPS-T (Transactional Web Processing Service (WPS)) DeployProcess message encoded in JSON (see Chapter 9 for the rationale). The information model conveyed in this manner does not differ significantly from the one that could be conveyed using OWS Context, and its main, common features can be briefly listed as: -provides clear recommendations on how model-driven design can be fully exploited in the context of rich data model and API design efforts. +a link to the application execution unit, - - - OGC Testbed-17: Model-Driven Standards Engineering Report - 21-035r1 - +a description of the application’s inputs and outputs, + +links to required Earth Observation data catalogues, + +and the possibility to pass other auxiliary information. + +An important difference in Testbed-14 with respect to Testbed-13 is that the application execution unit is not limited to a Docker container, but can also be a workflow described in Common Workflow Language (CWL), something which stems directly from one of the Sponsor requirements. Finally, it is important to note that this route does not preclude from embedding an OWS Context structure in the enclosing DeployProcess document if this is desired. + +Starting from the lessons learned and limitations identified in Testbed-13, and embracing the new and changed Sponsor requirements, this ER explains the trade-offs, decisions and conclusions taken by the Participants throughout the project. + + 2019-02-07 + + + Advancing the Interoperability of Geospatial Intelligence Tradecraft with 3D Modeling, Simulation, and Game Engines + 20-085r1 + USGIF & OGC + + 2021-03-08 - 2022-03-31 - + The objectives of this MS&G +Technical Paper are focused on identifying technology trends +that are influencing the convergence of GEOINT and M&S +tradecraft. The purpose is to advance ideas and techniques, +such as reality modeling of 3D environments, which increase +the knowledge-base and capacity of the geospatial analyst +community writ large. + + + Advancing the Interoperability of Geospatial Intelligence Tradecraft with 3D Modeling, Simulation, and Game Engines - Ronald Tse, Nick Nicholas - - 21-035r1 + 20-085r1 + - - - - OpenGIS Styled Layer Descriptor (SLD) Implementation Specification - Styled Layer Descriptor (SLD) Implementation Specification - 02-070 - Bill Lalonde - 02-070 - 2002-08-19 - The SLD is an encoding for how the Web Map Server (WMS 1.0 & 1.1) specification can be extended to allow user-defined symbolization of feature data. - + + 22-035 + Testbed-18: 3D+ Data Streaming Engineering Report + + + + Jérôme Jacovella-St-Louis + + 22-035 + This OGC Testbed 18 3D Plus Data Standards and Streaming Engineering Report (ER) reviews existing specifications that support interoperable descriptions of orbital and non-orbital space-based assets, objects, and observations as well as terrestrial observations. The ER suggests a framework consolidating these specifications as a foundation for modeling, representation, and serialization from space-based assets operating at any location in our solar system (3D+ data). This framework enables the streaming of 3D+ data to visualization devices (displays, AR, VR) for presentation. + + + + Testbed-18: 3D+ Data Streaming Engineering Report + 2023-09-01 + + + 2018-01-18 + Alex Robin + + JSON Encoding Rules SWE Common / SensorML + 17-011r2 + + + 17-011r2 + + This document describes new JavaScript Object Notation (JSON) encodings for the Sensor Web Enablement (SWE) Common Data Model and the Sensor Model Language (SensorML). Rather than creating new JSON schemas, this document defines encoding rules that allow auto-generation of JSON instances that conform to the Unified Modeling Language (UML) models. Alternatively, the mappings given in the second part of the document can be used to convert bi-directionally between XML and JSON representations. + + + JSON Encoding Rules SWE Common / SensorML - - - Catalog Interface - 02-087r3 + + Documents of type OpenGIS Reference Model + + + + Documents of type OpenGIS Reference Model + Documents of type OpenGIS Reference Model + + + + + + - + 14-021r2 + Testbed 10 CCI Profile Interoperability Engineering Report + + This Engineering Report was prepared as a deliverable for OGC Testbed 10, an initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Cross Community Interoperability (CCI) thread within the testbed. The work has been commissioned in order to inform geospatial information frameworks of the Defence Geospatial Information Working Group (DGIWG), National System for Geospatial Intelligence (NSG) of the US National Geospatial Intelligence Agency (NGA) and the UK Ministry of Defence (MOD). +The Engineering Report presents an analysis and assessment of interoperability between DGIWG, NSG and UK MOD profiles of Web Map Service (WMS) and Web Feature Service (WFS) standards of the OGC. The engineering report also presents findings from the implementation of the reference profiles. + + 2014-04-28 + Gobe Hobona, Roger Brackin + 14-021r2 + OGC® Testbed 10 CCI Profile Interoperability Engineering Report + + + + + 2010-08-18 + + OWS-7 - Towards secure interconnection of OGC Web Services with SWIM + Andreas Matheus + 10-155 - Doug Nebert + OWS-7 - Towards secure interconnection of OGC Web Services with SWIM + 10-155 + - 02-087r3 - - Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers. - 2002-12-13 - Catalog Interface + This Engineering Report provides guidance and generate action items for the OGC standardization effort to properly enable security in the near future such that a seamless, interoperable but secure interconnection between OGC Web Services and FUSE ESB technology stack as selected by use in the System Wide Information Management (SWIM) System of the US Federal Aviation Administration (FAA) can be achieved. - + - - OpenGIS Web Service Common Implementation Specification - 05-008c1 - Web Service Common Implementation Specification - 05-008c1 - 2005-05-03 - + Web Map Context Documents + Web Map Context Documents + 03-036r2 + - This document specifies many of the aspects that are, or should be, common to all or multiple OWS interface Implementation Specifications. Those specifications currently include the Web Map Service (WMS), Web Feature Service (WFS), and Web Coverage Service (WCS). These common aspects include: operation request and response contents; parameters included in operation requests and responses; and encoding of operation requests and responses. - - Arliss Whiteside + + 2003-06-12 + 03-036r2 + + Jean-Philippe Humblet + Create, store, and use state information from a WMS based client application - - Carl Reed, Tamrat Belayneh + + + 12-040 + + - Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification - 17-014r7 + 2014-02-26 + Web Coverage Service Interface Standard - Range Subsetting Extension + 12-040 + This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request which allow extraction of specific fields, according to the range type specification, from the range set of a coverage during server-side processing of a coverage in a GetCover-age request. + + OGC® Web Coverage Service Interface Standard - Range Subsetting Extension + + Peter Baumann, Jinsongdi Yu + + + 06-021r1 + Sensor Web Enablement Architecture Document + 2006-03-27 + + Mike Botts, Alex Robin, John Davidson, Ingo Simonis + + 06-021r1 + OpenGIS Sensor Web Enablement Architecture Document - 2020-02-08 - - - 17-014r7 - A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data.Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files. - -The delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types. + + + The aim of this document is to provide a overview description of the general architecture that applies to the Sensor Web Enablement (SWE). While this document provides a synopsis of the relevant encodings and web services, it does not contain interface descriptions of the components. -The open community GitHub version of this standard is here: https://github.com/Esri/i3s-spec [2]. - - OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification + - - - Joe Lewis - - 05-115 - Geo Video Web Service - - Geo Video Web Service - 05-115 - A GeoVideo Web Service (GVS) is a web service that facilitates the viewing of live and/or archived feeds from video cameras. The feeds may be composed of: -- A video stream -- Textual data in a caption stream (e.g. GPS data, camera states and characteristics, custom XML data, such as SensorMLTML) -- A combination of a video stream and associated textual data -The video streams of the feed may be viewed in the Windows Media Player. The textual data is extracted through scripting events that are generated as the caption stream is processed and displayed by the Windows Media Player. - - - 2006-03-28 + + Volume 5: OGC CDB Radar Cross Section (RCS) Models + 16-004r4 - - - OGC GGXF geodetic data grid exchange format - 22-051r7 - Roger Lott - - 22-051r7 - OGC GGXF geodetic data grid exchange format + + 2018-12-19 + Carl Reed + This CDB volume provides all of the information required to store Radar Cross Section (RCS) data within a conformant CDB data store. +Please note that the current CDB standard only provides encoding rules for using Esri ShapeFiles for storing RCS models. However, this Best Practice has been modified to change most of the ShapeFile references to “vector data sets” or “vector attributes” and “Point Shapes” to “Point geometries”. This was done in recognition that future versions of the CDB standard and related Best Practices will provide guidance on using other encodings/formats, such as OGC GML. + + 16-004r4 + Volume 5: OGC CDB Radar Cross Section (RCS) Models + + + + + + 19-027r2 + 2019-12-20 + + 19-027r2 + OGC Testbed-15: Machine Learning Engineering Report + OGC Testbed-15: Machine Learning Engineering Report + + - - The Geodetic data Grid eXchange Format (GGXF) is designed to be a single file format that may be used -for a wide range of geodetic applications requiring interpolation of regularly gridded data, including (but -not limited to): -• Transformation of latitude and longitude coordinates from one geodetic coordinate reference -system to another; -• Transformation of gravity-related heights from one vertical coordinate reference system to -another; -• Reduction of ellipsoid heights to the geoid, quasi-geoid or a surface of a vertical reference frame; -and -• The description of coordinate changes due to deformation. -The GGXF format has been designed specifically for carrying gridded geodetic parameters supporting -coordinate transformations and point motion operations but has no restriction on the type of content -that may be included. - - 2024-04-29 + + The Machine Learning (ML) Engineering Report (ER) documents the results of the ML thread in OGC Testbed-15. This thread explores the ability of ML to interact with and use OGC web standards in the context of natural resources applications. The thread includes five scenarios utilizing seven ML models in a solution architecture that includes implementations of the OGC Web Processing Service (WPS), Web Feature Service (WFS) and Catalogue Service for the Web (CSW) standards. This ER includes thorough investigation and documentation of the experiences of the thread participants. + Sam Meek - + + 19-084 + Vector Tiles Pilot 2: Vector Tiles Filtering Language Engineering Report + Andrea Aime + 19-084 - - - - 23-010 - 2023-06-14 - This Engineering Report (ER) summarizes the main achievements of the Federated Marine Spatial Data Infrastructure (FMSDI) Pilot Phase 3. It focused on a variety of aspects contributing to an overarching scenario to aid in the better understanding of both the challenges and potential opportunities for coastal communities, ecosystems, and economic activities in the Arctic region. - -The sub-scenarios, i.e., those scenarios developed by each participant, address aspects of the changing Arctic landscape. These activities included the following. - -A sea-based, health and safety scenario incorporating the land/sea interface in the Arctic. This scenario demonstrates the technology and data used with OGC, IHO, and other community standards in response to a grounding event and the evacuation of an expedition cruise ship or research vessel in the Arctic. Demonstrating interoperability between land and marine data that is necessary to aid first responders and other stakeholders. This scenario incorporates, but is not be limited to: - -voyage planning information (e.g., Arctic Voyage Planning Guide, Safety of Navigation products and services, Maritime Safety Information); - -land-based emergency services/resources (e.g., Coast Guard stations, transit times to emergency services or ports, medical facilities and resources, helicopter access); - -coastal environmental/topographic/hydrographic/maintenance data (e.g., deposition and dredging of seafloor sediment, changes in coastline and bathymetry); and + OGC Vector Tiles Pilot 2: Vector Tiles Filtering Language Engineering Report + The OGC Vector Tiles Pilot 2: Vector Tiles Filtering Language Engineering Report (ER) defines a filter language for vector data delivered as tiles (also known as vector tiles). The language applies to vector tiles served through implementations of the OGC API – Features standard and the draft OGC API - Tiles specification, but can be generally applied on all services supporting filtering by attributes. -global maritime traffic data in the Arctic (e.g., to help assess likelihood of other ships in responding to a ship in distress). +The ER further includes an assessment of filter languages, styles and online/offline symbol sharing for GeoPackages, OGC API - Features and OGC API - Tiles implementations for accuracy and completeness in applications that render vector tiles at local to regional scales. + + + + + 2020-07-08 + + + 2019-02-07 + 18-057 + + + + + + 18-057 + OGC Testbed-14: Authorisation, Authentication, & Billing Engineering Report + OGC Testbed-14: Authorisation, Authentication, & Billing Engineering Report + In the context of a generic Earth Observation Exploitation Platform ecosystem, populated by Thematic Exploitation Platforms (TEPs) and Mission Exploitation Platforms (MEPs), which make use of cloud computing resources for Earth Observation data processing, the European Space Agency (ESA) has established two fundamental building blocks within a TEP, with different functions, the Application Deployment and Execution Service (ADES) and the Execution Management Service (EMS). Users interact with a TEP using a Web Client and the TEP contains an EMS and an ADES. The EMS includes most of the control logic, required for deploying and executing applications in different MEPs and TEPs while the ADES instead is responsible for the single application deployment and execution on a specific platform (i.e. TEP and/or MEP). -Demonstrating interoperability between land and marine data that is necessary to understand coastal erosion (e.g., ocean currents, geology, permafrost characteristics, etc.). +The D009 - ADES and EMS Results and Best Practices Engineering Report describes how the two services should be engineered in the Exploitation Platform context. -General sensitivity to climate change. - Robert Thomas, Sara Saeedi - 23-010 - Towards a Federated Marine SDI: Connecting Land and Sea to Protect the Arctic Environment Engineering Report - - Towards a Federated Marine SDI: Connecting Land and Sea to Protect the Arctic Environment Engineering Report +This Engineering Report (ER) describes the work performed by the Participants in the Exploitation Platforms Earth Observation Clouds (EOC) Thread of OGC Testbed-14 concerning the interfaces proposed for the Authentication, Authorization, Billing and Quoting topics associated to the EMS and the ADES components. + Jérôme Gasperi + - - - OGC Filter Encoding 2.0 Encoding Standard - With Corrigendum - 09-026r2 - Filter Encoding 2.0 Encoding Standard - With Corrigendum - Panagiotis (Peter) A. Vretanos - A fundamental operation performed on a set of data or resources is that of querying in order to obtain a subset of the data which contains certain desired information that satisfies some query criteria and which is also, perhaps, sorted in some specified manner. - -This International Standard defines an abstract component, named AbstractQueryExpression, from which other specifications can subclass concrete query elements to implement query operations. This International Standard also defines an additional abstract query component, named AbstractAdhocQueryExpresison, which is derived from AbstractQueryExpression and from which other specifications can subclass concrete query elements which follow a query pattern composed of a list of resource types to query, a projection clause specifying the properties of those resources to present in the result, a projection clause composed of predicates that define the subset of resources or data in the result set and a sorting clause indicating to order in which the results should be presented. This pattern is referred to as an ad hoc query pattern since the server is not aware of the query until it is submitted for processing. This is in contrast to a stored query expression, which is stored and can be invoked by name or identifier. + + Engineering report for OGC Climate Resilience Pilot + + + + Guy Schumann, Albert Kettner, Nils Hempelmann + Engineering report for OGC Climate Resilience Pilot + 23-020r2 + 23-020r2 + The OGC Climate Resilience Pilot marked the beginning of a series of enduring climate initiatives with the primary goal of evaluating the value chain encompassing raw data to climate information processes within Climate Resilience Information Systems. This includes the transformation of geospatial data into meaningful knowledge for various stakeholders, including decision-makers, scientists, policymakers, data providers, software developers, service providers, and emergency managers. The results of the OGC Climate Resilience Pilot support the location community to develop more powerful visualization and communication tools to accurately address ongoing climate threats such as heat, drought, floods, and wild-fires as well as supporting governments in meeting commitments for their climate strategies. This will be accomplished through evolving geospatial data, technologies, and other capabilities into valuable information for decision-makers, scientists, policymakers, data providers, software developers, and service providers so they can make valuable, informed decisions to improve climate action. One of the most significant challenges so far has been converting the outputs of global and regional climate models into specific impacts and risks at the local level. The climate science community has adopted standards and there are now numerous climate resilience information systems available online, allowing experts to exchange and compare data effectively. However, professionals outside the weather and climate domain, such as planners and GIS analysts working for agencies dealing with climate change impacts, have limited familiarity with and capacity to utilize climate data. -This International Standard describes an XML and KVP encoding of a system-neutral syntax for expressing the projection, selection and sorting clauses of a query expression. The intent is that this neutral representation can be easly validated, parsed and then translated into some target query language such as SPARQL or SQL for processing. - 2014-08-18 + + + + + 2024-01-29 + + + Eric LaMar + WMS - Proposed Animation Service Extension + + + 06-045r1 + 06-045r1 + WMS - Proposed Animation Service Extension + + This document explains how the Web Map Server (WMS 1.0 [1] & 1.1 [2,3]) specification can be extended to allow map animations that move in space over time. It should be read in conjunction with the latest version WMS specification. + + + 2006-07-27 + + + Paul Scarponcini + OGC® Land and Infrastructure Conceptual Model Standard (LandInfra) + + This OGC Land and Infrastructure Conceptual Model Standard presents the implementation-independent concepts supporting land and civil engineering infrastructure facilities. Conceptual model subject areas include facilities, projects, alignment, road, rail, survey, land features, land division, and wet infrastructure (storm drainage, wastewater, and water distribution systems). The initial release of this standard includes all of these subject areas except wet infrastructure, which is anticipated to be released as a future extension. +This standard assumes the reader has a basic understanding of surveying and civil engineering concepts. + + + + + + 2016-12-20 + Land and Infrastructure Conceptual Model Standard (LandInfra) + 15-111r1 + 15-111r1 + + + + + + + Ensuring Quality of User Experience with OGC Web Mapping Services - Discussion Paper + 17-049 + 17-049 - - - 09-026r2 + + + + + + 2018-03-02 + This paper is intended to identify usability issues associated with use of OGC web +mapping services that affect the quality of experience a user may have when accessing +and using OGC web services and discuss potential solutions and guidance to address +these issues. Additionally, guidance on evaluating and self-assessing the Quality of +Experience of Spatial Data Services will also be discussed and addressed with a proposal +for common assessment criteria and common practices for improving the user experience +when viewing, layering or querying OGC web mapping services. + Ensuring Quality of User Experience with OGC Web Mapping Services - Discussion Paper + C. Mitchell, M. Gordon, T. Kralidis - - - Testbed11 Referenceable Grid Harmonization Engineering Report - 15-065r1 - 2015-11-18 + + + 07-062 + City Geography Markup Language + 2007-08-14 + CityGML is designed as an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is implemented as an application schema of the Geography Markup Language 3 (GML3), the extendible international standard for spatial data exchange and encoding issued by the Open Geospatial Consortium (OGC) and the ISO TC211. + - 15-065r1 - - OGC® Testbed11 Referenceable Grid Harmonization Engineering Report - - Eric Hirschorn, Peter Baumann - - This Engineering Report is a deliverable of the Testbed-11 Urban Climate Resilience (UCR) Thread. The UCR Thread responds to the urgent need to make climate information and related data readily available for the public and government decision makers to prepare for changes in the Earth’s climate. An important set of a data sources that will play an important role in detecting changes due to climate effects are a wide array of remote imaging systems. + City Geography Markup Language + Gerhard Gr + + 07-062 + - - GeoXACML Implementation Specification - Extension B (GML3) Encoding - 07-099r1 - Andreas Matheus - 07-099r1 + + + Tim Wilson, Renato Primavera, Panagiotis (Peter) A. Vretanos + + + 06-155 + OWS-4 CSW ebRIM Modelling Guidelines IPR + + 2007-06-06 + OWS-4 CSW ebRIM Modelling Guidelines IPR + 06-155 + The OWS-4 CSW ebRIM Modelling Guidelines Interoperability Program Report (IPR) provides guidance for creating a standard methodology for mapping geospatial domain information models to ebRIM [www.oasis-open.org/committees/regrep/documents/2.0/specs/ebrim.pdf]. It also presents the results of mapping specific Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] and Feature Catalog domain models to ebRIM for use with OpenGIS Catalog Service Standard [http://www.opengeospatial.org/standards/cat] implementations in the OWS-4 Initiative [http://www.opengeospatial.org/projects/initiatives/ows-4]. - 2008-02-23 - - - - - This specification is a normative extension to the GeoXACML core Implementation Specification. It defines the GML3 encoding for geometries. - GeoXACML Implementation Specification - Extension B (GML3) Encoding - - This OGC® document gives guidelines for enabling interoperability among different hydro data models and services. The demonstration specifically gives out best practices for supporting interoperability among the National Hydrographic Network (NHN) of Canada, the National Hydrographic Dataset Plus (NHD+) of United States, and the OGC HY_Features model developed and proposed by the World Meteorological Organization (WMO). The discussed version of OGC HY_Features was adopted as the mediation bridge model to exchange information among heterogeneous hydrological models. - 2014-07-16 + + Johannes Echterhoff - - Genong (Eugene) Yu, Liping Di - Testbed 10 Cross Community Interoperability (CCI) Hydro Model Interoperability Engineering Report - 14-048 - 14-048 + 10-060r1 + This document is applicable to use cases in which event-driven architecture principles are applied in Spatial Data Infrastructures. + +The document specifies publish/subscribe functionality for OGC web services. This is done by first defining an abstract publish / subscribe model and then deriving functional requirements from this model. + 2010-08-02 - - + OWS-7 Event Architecture Engineering Report + OWS-7 Event Architecture Engineering Report + 10-060r1 + + - OGC® Testbed 10 Cross Community Interoperability (CCI) Hydro Model Interoperability Engineering Report + - - 16-102r2 - InfraGML 1.0: Part 2 - LandInfra Facilities and Projects - Encoding Standard + + + + + + + + + + + + + + + + + + + + + + + + + + 21-027 - OGC InfraGML 1.0: Part 2 - LandInfra Facilities and Projects - Encoding Standard - - 16-102r2 + OGC Testbed-17: Geo Data Cube API Engineering Report + 21-027 + OGC Testbed-17: Geo Data Cube API Engineering Report + 2022-04-08 + This OGC Testbed 17 Engineering Report (ER) documents the results and recommendations of the Geo Data Cube API task. The ER defines a draft specification for an interoperable Geo Data Cube (GDC) API leveraging OGC API building blocks, details implementation of the draft API, and explores various aspects including data retrieval and discovery, cloud computing and Machine Learning. Implementations of the draft GDC API are demonstrated with use cases including the integration of terrestrial and marine elevation data and forestry information for Canadian wetlands. + + + + + Jérôme Jacovella-St-Louis + + + + Arliss Whiteside - This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. -InfraGML is published as a multi-part standard. This Part 2 addresses the Facility and Project Requirements Classes from LandInfra. - - Paul Scarponcini - - 2017-08-16 + 07-032 + Frame image geopositioning metadata GML 3.2 application schema + Frame image geopositioning metadata GML 3.2 application schema + + + This document specifies a GML 3.2 Application Schema for frame image geopositioning metadata, for XML encoding of the georeferencing coordinate transformation parameters of an unrectified frame image. A frame image is one whose entire two-dimensional extent was collected at one time. A georeferencing coordinate transformation can transform position coordinates between a specific ground-based (or object) Coordinate Reference System (CRS) and the image CRS. + 07-032 + 2007-06-06 + + + - - OGC InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard - 16-100r2 - This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. -InfraGML is published as a multi-part standard. This Part 0 addresses the Core Requirements Class from LandInfra. + + 06-131 + EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 + + - InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard - 16-100r2 + EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 + This document describes the Data Model of Earth Observation Products for the OGC + + 2006-10-24 + + Renato Primavera + 06-131 + + + + 07-061 + Revision Notes for OpenGIS® Implementation Specification: Geographic information - Geography Markup Language Version 3.2.1 + + Revision Notes for OpenGIS® Implementation Specification: Geographic information - Geography Markup Language Version 3.2.1 + 07-061 + + + Clemens Portele - - - + + This document provides revision notes for version 3.2.1 of the OpenGIS® Implementation Specification Geographic information – Geography Markup Language (GML). + 2008-02-20 - Paul Scarponcini - 2017-08-16 - - - - - - - - - - - - - - - - - - - - - - - - - - - - 15-096 - 15-096 - Use Cases and Applications of the OGC Moving Features Standard: The Requirements for a Moving Feature API + + + + OWS-7 Aviation - AIXM Assessment Report + 10-131r1 + + OWS-7 Aviation - AIXM Assessment Report + + Debbie Wilson + + 10-131r1 + 2010-08-18 + This report shall focus on evaluating the ability to: + +- Serve, filter and update AIXM 5.1 data via the OGC WFS-T 2.0 interface +- Recommend guidelines or cross-walks for interpreting the new AIXM 5.1 schedules in conjunction with the Timeslice model in a web services environment + + + + OGC Testbed-13: Application Deployment and Execution Service Engineering Report + + Pedro Gonçalves + The Testbed-13 Earth Observation Clouds (EOC) effort supports the development of ESA’s Thematic Exploitation Platforms (TEP) by exercising envisioned workflows for data integration and processing that are deployed in multiple clouds. The Application Deployment & Execution Service OGC Engineering Report (ER) identifies the Application Programming Interface (API) for delivering all functionality provided to realize the testbed scenario. + +This ER will list the requirements fulfilled by Cloud APIs in order to allow an automation of the application package deployment and execution workflow and capture implementation process experiences. + + + 17-024 + Testbed-13: Application Deployment and Execution Service Engineering Report + 2018-01-11 - 2016-01-18 - Akinori Asahara, Hideki Hayashi, Carl Reed - - Use Cases and Applications of the OGC Moving Features Standard: The Requirements for a Moving Feature API - - This OGC Discussion Paper provides examples of some actual and potential geospatial applications using the OGC Moving Features encoding. These applications can be used to define the next steps in the development of the OGC Moving Features Standard: The definition of a “Moving Features API”. As a conclusion, the Moving Features SWG recommends that a new Moving Features API standard should target the following three kinds of operations: retrieval of feature information, operations between a trajectory and a geometric object, and operations between two trajectories. Additionally, the Moving Features SWG recommends establishing an abstract specification for these three kinds of operations because only a part of operations for trajectories is defined by ISO 19141:2008 - Schema for moving features. - + + + 17-024 - + + + + + + + + + Pedro Gonçalves + The Application Package OGC Engineering Report (ER) defines a data model and serialization for Thematic Exploitation Platforms (TEP) Application Packages. A TEP refers to a computing platform that follows a given set of scenarios for users, data and ICT provision aggregated around an Earth Science thematic area. This ER is part of the Testbed-13 Earth Observation Clouds (EOC) effort to support the development by the European Space Agency (ESA) of the TEP by exercising envisioned workflows for data integration, processing, and analytics based on algorithms developed by users that are deployed in multiple clouds. + +The wide usage of virtualization and the possibility to start virtual environments within Cloud services significantly simplifies the creation of environments and provisioning of resources. However, it still leaves a problem of portability between infrastructures. This ER identifies a strategy for packaging an application in a Cloud environment that will be able to run in a predictable manner in different computing production environments. The application packaging specifies the elements that will ensure: + +Scientific reproducibility, + +Dependencies identification and management, + +Maintainability from an operational perspective and avoid version pilling, + +Portability in different Cloud providers + +The ER proposes the use of containers, defining everything required to make a piece of software run packaged into isolated containers. Unlike a Virtual Machine (VM), a container does not bundle a full Operating System (OS) - only libraries and settings required to make the software work are needed. This makes for efficient, lightweight, self-contained systems and guarantees that software will always run the same, regardless of where it’s deployed. A discussion on application deployment and execution is presented in the separate OGC Testbed-13 Application Deployment and Execution Service ER [1]. + + - 05-086 - Sensor Model Language (SensorML) - The general models and XML encodings for sensors. - 05-086 - OpenGIS Sensor Model Language (SensorML) - Mike Botts - 2005-11-21 - - - + + OGC Testbed-13: EP Application Package Engineering Report + 17-023 + 17-023 + Testbed-13: EP Application Package Engineering Report + 2018-01-30 + - + + 2020-10-22 + OGC Earth Observation Applications Pilot: European Union Satellite Centre Engineering Report + This Engineering Report (ER) describes the achievements of the European Union Satellite Centre (SatCen) as an application provider in the OGC Earth Observation Applications Pilot and the lessons learned from the project. + + 20-038 + OGC Earth Observation Applications Pilot: European Union Satellite Centre Engineering Report - Thomas Disney - 16-028r1 - Testbed-12 FIXM GML Engineering Report - 2017-06-19 + Omar Barrilero, Adrian Luna + + 20-038 - The FAA and EUROCONTROL, in conjunction with multiple other international partners, are currently in the process of developing the Flight Information Exchange Model (FIXM). FIXM is an exchange model capturing Flight and Flow information that is globally standardized. The need for FIXM was identified by the International Civil Aviation Organization (ICAO) Air Traffic Management Requirements and Performance Panel (ATMRPP) in order to support the exchange of flight information as prescribed in Flight and Flow Information for a Collaborative Environment (FF-ICE). - -FIXM is the equivalent, for the Flight domain, of Aeronautical Information Exchange Model (AIXM) and Weather Information Exchange Model (WXXM), both of which were developed in order to achieve global interoperability for, respectively, Aeronautical Information Systems (AIS) and Meteorological Information (MET) exchange. FIXM is therefore part of a family of technology independent, harmonized and interoperable information exchange models designed to cover the information needs of Air Traffic Management. Previous OGC IP initiatives developed an architecture that supports the exchange of AIXM and WXXM data. This report shall describe the integration of Geography Markup Language (GML) profile elements into FIXM, specifically, the Feature, Time, Geometries and Units of Measure (UOM), into FIXM version 3.0.1 and drafts of FIXM 4.0. The purpose of this report is to provide recommendations and change requests (CR) on the implementation of GML elements for use by the FIXM development community. - Testbed-12 FIXM GML Engineering Report - - 16-028r1 - - - - - + + This Open Geospatial Consortium (OGC) document provides an analysis of the prototype implementations, approaches and performance aspects of data size reduction and compression techniques explored in OGC Testbed 12. Specifically, it describes work done during Testbed 12 investigating compression for geospatial data sets on OGC Web Feature Service (WFS) using W3C Efficient XML Interchange (EXI) Format 1.0 (Second Edition). + +The investigation focused on extending WFS with EXI output formats, and the associated performance aspects of data size reduction and compression techniques. EXI is a compact representation for the Extensible Markup Language (XML) Information Set. EXI is intended to simultaneously optimize performance and the utilization of computational resources. From a practical viewpoint, EXI is designed to reduce the size of XML data exchanged between computer systems. + +EXI uses a grammar-driven approach designed to achieve efficient encodings using an encoding algorithm and a small set of datatype representations. Consequently, EXI processors are described by the W3C as ‘relatively simple’ and ‘can be implemented on devices with limited capacity.’ An EXI processor is used by application programs to encode their structured data into EXI streams and/or to decode EXI to make the structured data accessible. + + + - - 2006-03-15 - OpenGIS Web Map Service (WMS) Implementation Specification - The OpenGIS® Web Map Service Interface Standard (WMS) provides a simple HTTP interface for requesting geo-registered map images from one or more distributed geospatial databases. A WMS request defines the geographic layer(s) and area of interest to be processed. The response to the request is one or more geo-registered map images (returned as JPEG, PNG, etc) that can be displayed in a browser application. The interface also supports the ability to specify whether the returned images should be transparent so that layers from multiple servers can be combined or not. <p>NOTE: WMS 1.3 and ISO 19128 are the same documents. + Testbed-12 Compression Techniques Engineering Report - 06-042 - Web Map Service (WMS) Implementation Specification - Jeff de La Beaujardiere - 06-042 + + 16-055 + Testbed-12 Compression Techniques Engineering Report + 16-055 + 2017-05-15 + Jeff Harrison - - SWIM Information Registry Engineering Report - 18-022r1 - This Engineering Report (ER) summarizes the findings and recommendations for building an information registry working together with the existing Federal Aviation Administration (FAA) System Wide Information Management (SWIM) aviation service registries, the National Airspace System Service Registry and Repository (NSRR). This information registry should allow the different Air Traffic Management (ATM) stakeholders to retrieve the appropriate service registered in the NSRR using the semantic representation of real-life entities represented by the data served by the services (e.g. estimated departure time, estimated time of arrival, ”runway true bearing”…). To support the integration of this domain-specific information, the ER proposes different strategies based on the semantic annotation proposal made in OGC 08-167r2 [1] extended with a recent World Wide Web Consortium (W3C) recommendation, the Web Annotation data model [1]. In particular, the ER focuses on a solution using the W3C web annotation data model which adds semantics to the NSRR without changing the content of the database. This solution provides a low-cost, flexible and efficient alternative to add domain-specific semantics to NSRR content. The ER concludes with remarks on the elements necessary for implementing the information registry as a web annotation store as well as the necessity to build domain-specific knowledge models to support further interoperability and further service discoverability and the added-values of using the Data Catalog (DCAT) or Semantic Registry Information Model (SRIM) to better describe and retrieve ATM services. - 2019-02-11 - + + ISO + + Same as ISO 19119 + - - - OGC Testbed-14: SWIM Information Registry Engineering Report - - 18-022r1 - Yann Le Franc + Topic 12 - The OpenGIS Service Architecture + + + Topic 12 - The OpenGIS Service Architecture + 02-112 + 2001-09-14 + 02-112 - + - 23-022r1 - 23-022r1 - Establishing the Framework of Disaster Early Warning Mechanisms - A Case Study of Slope Disaster - Establishing the Framework of Disaster Early Warning Mechanisms - A Case Study of Slope Disaster - - - 2023-08-22 - - Hsiao-Yuan (Samuel) Yin, Yi-Chia (Vincent) Lin, Chih-Wei (Will) Kuan, Cheng-Yan Tsai, Lok-Man (Lawre - The impact of global climate change has led to a rise in the frequency of natural -disasters in numerous countries resulting in substantial losses in terms of both human lives and the global economy. The establishment of a robust disaster early-warning mechanism is recommended that will empower communities to proactively engage in disaster reduction and prevention measures before such calamities occur, thereby effectively reducing losses. -The Common Alerting Protocol (CAP) is an internationally recognized digital -message format and protocol for all types of alarms and early warning notifications. It was officially adopted by The Federal Emergency Management Agency (FEMA) in 2010 for its Integrated Public Alert and Warning System (IPAWS). It has also been successfully implemented in Taiwan for many years. However, different countries may employ other color-coded warning systems to indicate varying degrees of disaster severity. This disparity in warning standards can cause public confusion during emergencies, leading to increased costs in disaster management. This paper proposes a framework that utilizes red and yellow warning lights for issuing alerts. Adopting a standardized approach will mitigate confusion and enhance the efficiency of disaster response and management. -This study proposes a framework that uses red and yellow warning mechanisms for -issuing alerts such as the disaster early warning for debris flows and large-scale -landslides established by the Soil and Water Conservation Bureau (SWCB). This -investigation will explore the feasibility of standardizing yellow and red warning -publishing rules. - + 07-028r1 + 2007-05-17 + + 07-028r1 + GEOINT Structure Implementation Profile Schema Processing + + This document contains a description of the schema tailoring process for application schema development based on the U.S. National System for Geospatial-Intelligence (NSG) GEOINT Structure Implementation Profile (GSIP) as developed in conjuction with the Open Geospatial Consortium Interoperability Program initiative OWS-4. + + GEOINT Structure Implementation Profile Schema Processing + Clemens Portele + - - 21-068 - - OGC Best Practice for using SensorThings API with Citizen Science - OGC Best Practice for using SensorThings API with Citizen Science - 21-068 - Andreas Matheus + + OGC® Testbed 10 Engineering Report: Aviation Dissemination of Weather Data - + 0000-00-00 - This document introduces an extension to the OGC SensorThings data model and discusses -the best practices for using such an extension in the context of Citizen Science. -The motivation for the introduced extension, referred to as “STAplus,” has been developed -during the EC H2020 project Cos4Cloud and is based on requirements from Citizen Science. -Whereas the dominant use of the OGC SensorThings data model (and API) can be coined -with the use case “single authority provides sensor readings to consumers”, in Citizen -Science there are many contributors (citizens) that – together – create the big “picture” with -their observations. -The introduced extension STAplus supports the model that those observations are owned by -(different) users that may express the license for re-use; we call this part of the contribution -the ownership concept. In addition to the ownership and license abilities, the introduced -extension allows to express explicit relations between observations and to create group(s) of -observations to containerize observations that belong together. Relations can be created -among any individual observations or observations of a group to support performant Linked -Data extraction and semantic queries, e.g., expressed in SPARQL. -We believe that the introduced extension is an important contribution towards the realization -of the FAIR principles, perhaps not only in Citizen Science, as STAplus strengthens the “I” -(Interoperability) through a common data model and API as well as the “R” (Reusability) by -allowing to express standards-based queries that may consider licensing conditions, relevant -for reuse of other users’ observations. The STAplus Data Model and Business Logic also -enriches existing deployments as the extension can be seamlessly added and thereby offer -new capabilities to create and manage the “big picture” with multi-user capabilities. -This document also illustrates best practices of using STAplus, evaluated with proof-ofconcept deployments based on the implementations by 52°North, Secure Dimensions, and -CREAF. - 2022-09-29 - + Mark Hughes + 14-038r1 + Testbed 10 Engineering Report: Aviation Dissemination of Weather Data + 14-038r1 + + This OGC document provides an analysis of the mapping between the NOAA Web Gridded Document Service (WGDS) and the OGC Web Coverage Service (WCS) and describes an adapter which translates WCS 2.0 requests to WGDS requests and then translates WGDS responses to WCS 2.0 responses. +This Engineering Report was prepared as a deliverable for the OGC Testbed 10 (Testbed-10) initiative, specifically the Testbed 10 Aviation Thread. + + + - - 2011-05-11 - Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos - OGC Geography Markup Language (GML) simple features profile Technical Note - 11-044 - 11-044 - OGC Geography Markup Language (GML) simple features profile Technical Note - + + GeoPose 1.0 is an OGC Implementation Standard for exchanging the location and orientation of real or virtual geometric objects (“Poses”) within reference frames anchored to the earth’s surface (“Geo”) or within other astronomical coordinate systems. + +The standard specifies two Basic forms with no configuration options for common use cases, an Advanced form with more flexibility for more complex applications, and five composite GeoPose structures that support time series plus chain and graph structures. + +These eight Standardization Targets are independent. There are no dependencies between Targets and each may be implemented as needed to support a specific use case. + +The Standardization Targets share an implementation-neutral Logical Model which establishes the structure and relationships between GeoPose components and also between GeoPose data objects themselves in composite structures. Not all of the classes and properties of the Logical Model are expressed in individual Standardization Targets nor in the specific concrete data objects defined by this standard. Those elements that are expressed are denoted as implementation-neutral Structural Data Units (SDUs). SDUs are aliases for elements of the Logical Model, isolated to facilitate specification of their use in encoded GeoPose data objects for a specific Standardization Target. + +For each Standardization Target, each implementation technology and corresponding encoding format defines the encoding or serialization specified in a manner appropriate to that technology. + +GeoPose 1.0 specifies a single encoding in JSON format (IETF RFC 8259). Each Standardization Target has a JSON Schema (Internet-Draft draft-handrews-json-schema-02) encoding specification. The key standardization requirements specify that concrete JSON-encoded GeoPose data objects must conform to the corresponding JSON Schema definition. The individual elements identified in the encoding specification are composed of SDUs, tying the specifications back to the Logical Model. + +The GeoPose 1.0 Standard makes no assumptions about the interpretation of external specifications, for example, of reference frames. Nor does it assume or constrain services or interfaces providing conversion between GeoPoses of difference types or relying on different external reference frame definitions. - - This technical note enhances the OGC GML simple features profile to include circles, circular arc, and corrects the annex numbering, and clarifies how to specify conformance classes. - + 2023-09-08 + OGC GeoPose 1.0 Data Exchange Standard - + + Carl Stephen Smyth + + OGC GeoPose 1.0 Data Exchange Standard + 21-056r11 + + 21-056r11 + - - Guy Schumann - 2019-02-15 - 18-028r2 - WMS QoSE Engineering Report - 18-028r2 - OGC Testbed-14: WMS QoSE Engineering Report + + + 21-066r1 + Release Notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata v.2.0 + + Joan Maso + 2022-09-09 + + + This document provides the set of revision notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata [OGC 17-083r4] and does not modify that Standard. + Release Notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata v.2.0 + 21-066r1 + + + - - - - Quality of Service (QoS) and Quality of Experience (QoE) as they are intended and described at the OGC are two related concepts which require very specific treatment and characterization. Citing the definitions provided by the Domain Working Group (DWG) charter document: - -Quality of Service: Technical reliability and performance of a network service. Typically measured using metrics like error rates, throughput, availability and delay or request response time. This Engineering Report (ER) attempts to handle QoS aspects such as service availability, scalability and speed. - -Quality of (User) Experience: A holistic, qualitative measure of the customers' experience of the application or service. It encompasses both the user experience and the customer support experience of the evaluated applications and/or services. - -QoE focuses on the usability of the information that is conceived via OGC services to end users or other client application and therefore is concerned more with qualitative aspects of such services like presence of metadata, proper and descriptive namings, appropriate styling and so on (a more thorough treatment is present in the QoE discussion paper OGC 17-049 entitled Ensuring Quality of User Experience with OGC Web Mapping Services available at https://portal.ogc.org/files/?artifact_id=74403&version=1). + OGC API - Processes - Part 1: Core + + + 2021-12-20 + 18-062r2 + OGC API - Processes - Part 1: Core + 18-062r2 + + + Benjamin Pross, Panagiotis (Peter) A. Vretanos + + The OGC API — Processes — Part 1: Core Standard supports the wrapping of computational tasks into executable processes that can be offered by a server through a Web API and be invoked by a client application. The standard specifies a processing interface to communicate over a RESTful protocol using JavaScript Object Notation (JSON) encodings. The standard leverages concepts from the OGC Web Processing Service (WPS) 2.0 Interface Standard but does not require implementation of a WPS. -QoS focuses on providing reliable (i.e. quantitative ) measures of spatial data service metrics which can be used to characterize how a service ( one or more specific datasets exposed by a certain service) is performing both in near real-time as well as historically. It touches concepts like availability, scalability (also known as capacity), absolute performance (i.e. speed) and can be used to assess also perceived performance by final clients. As mentioned above, it is typically measured using metrics like error rates, throughput, availability and delay or request response time. +By way of background and context, in many cases geospatial or location data, including data from sensors, must be processed before the information can be effectively used. The WPS Standard provides a standard interface that simplifies the task of making simple or complex computational geospatial processing services accessible via web services. Such services include well-known processes found in Geographic Information Systems (GIS) as well as specialized processes for spatiotemporal modeling and simulation. While the WPS standard was designed with spatial processing in mind, the standard could also be used to readily insert non-spatial processing tasks into a web services environment. -Quite often the QoS and QoE aspects of spatial data services are underestimated if not simply ignored due to lack of resources as well as lack of awareness, resulting in services which are difficult to exploit (i.e. QoE very low) and/or unstable or very slow (i.e. QoS very low). The result is that few users end up using them after the initial launch and this is especially true for services targeting end users who are used to interact with services a-la Google Maps which delivers extreme performance and scalability as well as bullet-proof usability. +The OGC API — Processes Standard is a newer and more modern way of programming and interacting with resources over the web while allowing better integration into existing software packages. The OGC API — Processes Standard addresses all of the use cases that were addressed by the WPS Standard, while also leveraging the OpenAPI specification and a resource-oriented approach. - - +The resources that are provided by a server implementing the OGC API — Processes Standard are listed in Table 1 below and include information about the server, the list of available processes (Process list and Process description), jobs (running processes) and results of process executions. - - - - Geospatial Portal Reference Architecture - 04-039 - Geospatial Portal Reference Architecture - - + + - Louis Rose - 04-039 - This Guide has been developed by the members of the Open Geospatial Consortium, Inc. to assist the global geospatial technology community in implementing standards-based geospatial portal solutions that are compatible with Spatial Data Infrastructures in every nation. We offer this document as a resource for rapid development and informed acquisition of portals and portal-exploiting applications that can plug and play with geospatial data and services in your organization and other organizations in your community and around the world. - 2004-09-22 + Frédéric Houbie, Lorenzo Bigagli + 2010-02-10 + + This document describes the mapping of Earth Observation Products – defined in the OGC® GML 3.1.1 Application schema for Earth Observation products [OGC 06-080r4] (version 0.9.3) – to an ebRIM structure within an OGC® Catalogue 2.0.2 (Corrigendum 2 Release) [OGC 07-006r1] implementing the CSW-ebRIM Registry Service – part 1: ebRIM profile of CSW [OGC 07-110r4]. This standard defines the way Earth Observation products metadata resources are organized and implemented in the Catalogue for discovery, retrieval and management. + Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products + 06-131r6 + + + 06-131r6 + OGC® Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products - - OGC Model for Underground Data Definition and Integration (MUDDI) Part 1: Conceptual Model - 23-024 - 23-024 - MUDDI stands for “Model for Underground Data Definition and Integration” and is an approach to make sub-surface data Findable, Accessible, Interoperable, and Re-Usable. - -This document defines a Conceptual Model of classes that allows the integration of datasets from different types of information about the underground space, using different information models. These information models include models about elements such as utility infrastructure, transport infrastructure, soils, ground water, or environmental parameters. The Conceptual Model is a superset of classes representing Real-World Objects that can be found in the Underground. - - + + + 2012-01-19 + 11-030r1 + Open GeoSMS Standard - Core + + Kuan-Mei Chen, Carl Reed + OGC®: Open GeoSMS Standard - Core + The OpenGIS® Open GeoSMS standard defines an encoding for location enabling a text message to be communicated using a Short Messages System (SMS). + 11-030r1 + - - Alan Leidner, Andrew Hughes, Carsten Roensdorf, Neil Brammall, Liesbeth Rombouts, Joshua Lieberman - OGC Model for Underground Data Definition and Integration (MUDDI) Part 1: Conceptual Model - 2024-07-05 - - - 2017-09-05 - OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification - - Carl Reed, Tamrat Belayneh - A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files. - - - -The delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3d datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types. + + Roger Lott + Topic 2 - Referencing by coordinates (Including corrigendum 1 and corrigendum 2) - 17-014r5 - Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification + 18-005r8 + Topic 02 - Referencing by coordinates - + This document is consistent with the third edition (2019) of ISO 19111, Geographic Information - Referencing by coordinates including its amendments 1 and 2. ISO 19111:2019 was prepared by Technical Committee ISO/TC 211, Geographic information/Geomatics, in close collaboration with the Open Geospatial Consortium (OGC). It replaces the second edition, ISO 19111:2007 and also ISO 19111-2:2009, OGC documents 08-015r2 and 10-020. This OGC document, 18-005r5, incorporates three editorial corrections made in ISO 19111:2019 amendment 1 of 2021. - 17-014r5 + + 18-005r8 + + + 2023-09-05 - - Paul Cote - 07-023r2 - OGC Web Services Architecture for CAD GIS and BIM - - - 07-023r2 - OGC Web Services Architecture for CAD GIS and BIM + - 2007-05-16 - This document lists the design principles and requirements for future versions of a potential architecture for integrating workflows and information models from Computer Aided Design and Building Information Modelling with the principles of the OGC Web Services Architecture. - - + + Hsu-Chun James Yu, Zhong-Hung Lee, Cai-Fang Ye, Lan-Kun Chung, Yao-Min Fang + Sensor Web Enablement Application for Debris Flow Monitoring System in Taiwan + 2009-07-27 - - - KML is a file format used to display geographic data in an Earth browser, such as Google Earth, Google Maps, and Google Maps for Mobile. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard. - 07-039r1 - - KML 2.1 Reference - An OGC Best Practice - KML 2.1 Reference - An OGC Best Practice - 07-039r1 - Carl Reed - - + 09-082 - - 2007-05-07 + Sensor Web Enablement Application for Debris Flow Monitoring System in Taiwan + 09-082 + This application document describes: + +1) What is a Debris Flow Monitoring System. +2) How SWE implements in Debris Flow Monitoring System. +3) Tutorial for SWE developers. + + - + + + + 05-084 + The OGC Catalog-Web Profile is a complex specification that implies usage of many concepts, such as ressources, metadata, registry, registry information model, harvesting, etc. This document is a user-friendly introduction to these concepts. It will help the understanding of the Catalog specification in general and of the Catalog Web profile with ebRIM in particular. + Catalog 2.0 Accessibility for OWS3 + - Josh Lieberman, Johannes Echterhoff, Matt de Ris, George Wilber - - 14-086r1 - Aircraft Access to SWIM (AAtS) Harmonization Project Summary Report + 05-084 + Catalog 2.0 Accessibility for OWS3 + + Vincent Delfosse + 2006-05-09 + + + + Tom Strickland + + + + Topic Domain 1 - Telecommunications Domain + 01-042 + + 01-042 + Topic Domain 1 - Telecommunications Domain - - OGC® Aircraft Access to SWIM (AAtS) Harmonization Project Summary Report - 14-086r1 - 2014-11-03 - This OGC® document summarizes the Aircraft Access to SWIM (AAtS) Harmonization activity developed by a team funded by the FAA and led by the Open Geospatial Consortium (OGC). The activity involved assembling a core team of industry participant experts to analyze and harmonize four standards suites and/or standards-based architectures relevant to air-ground information exchange: -• The Aircraft Access to SWIM (AAtS) concept, -• RTCA aeronautical information services (AIS) and meteorological (MET) information data link service committee’s (SC-206) concepts and standards, -• Air-Ground Information Exchange A830 (AGIE) standard and -• OGC standards and architectural perspectives. -Elements of this effort have included: -• Creation and public release of a Request for Information -• Analysis of the fits and overlaps between the four standards suites -• Engagement with ongoing standards development efforts to reduce incompatibilities - - + 2001-10-09 + Domain Model for telecommunications Networks - - - - 2005-02-17 - Jerome Sonnett - OWS 2 Common Architecture: WSDL SOAP UDDI - 04-060r1 - 04-060r1 + + 17-084r1 + EO Collection GeoJSON(-LD) Encoding + 2021-04-21 + 17-084r1 + Y. Coene, U. Voges, O. Barois + + + EO Collection GeoJSON(-LD) Encoding + + - OWS 2 Common Architecture: WSDL SOAP UDDI + JavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. GeoJSON [NR2] is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. This OGC Best Practice describes a GeoJSON [NR2] and JSON-LD [NR13] encoding for Earth Observation (EO) metadata for collections (dataset series). This standard can be applied to encode metadata based on the OGC 11-035r1 [OR20] or ISO19139 [OR27], ISO19139-2 [OR28] specifications, or as an encoding of the Unified Metadata Model for Collections (UMM-C) conceptual model [OR2]. + +The GeoJSON encoding defined in this document is defined as a compaction1 through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF/XML [OR11] and RDF Turtle [OR12]. + +This document makes no assumptions as to the “service” interfaces through which the metadata are accessed and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful Architecture. + +GeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon, and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features. + +JSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR7] which allows validation of instances against these schemas. + + + + + 15-005r1 + DGIWG - Web Feature Service 2.0 Profile + + This document defines the DGIWG profile for the ISO +19142:2010 - Web Feature Service (WFS) including changes +made in the OpenGIS Web Feature Service 2.0 Interface +Standard - Corrigendum. The Web Feature Service provides +access to geospatial features in a manner independent of the +underlying data store. + 2016-02-01 + 15-005r1 + Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey - - This OGC document reports the work that occurred in the OWS2 Test Bed Common Architecture thread. This thread focused on the use of UDDI/WSDL/SOAP in the OGC Web Services architecture. It also provides guidelines for the use of these technologies. + DGIWG - Web Feature Service 2.0 Profile + + - - - - + + + 12-160r1 + + 2013-06-18 + Jon Blower, Xiaoyu Yang, Joan Masó and Simon Thum + OGC® OWS 9 Data Quality and Web Mapping Engineering Report + OWS 9 Data Quality and Web Mapping Engineering Report + 12-160r1 + + + + This Engineering Report specifies conventions for conveying information about data +quality through the OGC Web Map Service Standard (known hereafter as the “WMS-Q +conventions”), OGC Web Map Tile Service Standard (known hereafter as the “WMTS-Q +conventions”), OGC KML (known hereafter as the “KML-Q conventions”) and OGC +Augmented Reality Markup Language. + + + + + + Testbed-12 Arctic Spatial Data Infrastructure Engineering Report + 16-063 + 2017-03-08 + 16-063 + This engineering report captures use cases representative of the vision of the Arctic Spatial Data Infrastructure (ArcticSDI). The ArcticSDI is a cooperative initiative established between the eight National Mapping Agencies of Canada, Finland, Iceland, Norway, Russia, Sweden, USA and Denmark, with the aim of providing governments, policy makers, scientists, private enterprises and citizens in the Arctic with access to geographically related Arctic data, digital maps, and tools to facilitate monitoring and decision-making. The initiative will achieve this aim by providing a framework of spatial information resources, organizational structures, technologies of creation, processing and exchange of spatial data, that provides broad access and efficient use of spatial data for the Arctic. The engineering report provides a review of the policy drivers supporting the establishment of spatial data infrastructure (SDI) in each Arctic nation in order to improve understanding of the use cases, user groups and the impact an ArcticSDI may have on their day-to-day business. The engineering report presents lessons learnt along each of the components of SDI, for example, users, data, technology, standards, policy and others. A discussion is presented on how the technologies and standards already in use by the national mapping agencies relate to the technologies and standards implemented by the testbed, as well as how emerging geospatial standards could benefit the ArcticSDI. - Geography Markup Language (GML) simple features profile - 10-100r2 - 2010-10-07 - Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos - Geography Markup Language (GML) simple features profile - 10-100r2 - This approved OpenGIS® Implementation Standard defines a Simple Features profile of the Geography Markup Language version 3.2. This Simple Features Profile has been aligned with the OGC Simple Features standard for SQL version 1.2. Simple Features include: Point, Curve (LineString), Surface (Polygon), Geometry, MultiPoint, MultiCurve, MultiSurface, and MultiGeometry. The detailed abstract model for OGC features and geometry can be found in the OGC Abstract Specification, Topic Volume 1: Features (which is equivalent to ISO 19107). + + Stefano Cavazzi, Roger Brackin + Testbed-12 Arctic Spatial Data Infrastructure Engineering Report - - Sensor Web Enablement: Overview And High Level Architecture - OGC Sensor Web Enablement: Overview and High Level Architecture - 07-165r1 + + Sensor Observable Registry (SOR) Discussion Paper + 09-112r1 + - - Mike Botts, George Percivall, Carl Reed, John Davidson - Carl Reed, Mike Botts, George Percivall, John Davidson - OGC® Sensor Web Enablement: Overview And High Level Architecture - OGC Sensor Web Enablement: Overview and High Level Architecture - - 2013-04-02 - - 07-165r1 - A sensor network is a computer accessible network of many, spatially distributed devices using sensors to monitor conditions at different locations, such as temperature, sound, vibration, pressure, motion or pollutants[1]. A Sensor Web refers to web accessible sensor networks and archived sensor data that can be discovered and accessed using standard protocols and application program interfaces (APIs). - This OGC White Paper provides a high-level overview of and architecture for the Open Geospatial -Consortium (OGC) standards activities that focus on sensors, sensor networks, and a concept called the -“Sensor Web”. This OGC focus area is known as Sensor Web Enablement (SWE). - - - - 3D-Symbology Encoding Discussion Draft - 09-042 - + Sensor Observable Registry (SOR) Discussion Paper + 09-112r1 + + 2010-10-12 + This Discussion paper introduces the Sensor Observable Registry (SOR), a web service interface for managing the definitions of phenomena measured by sensors as well as exploring semantic relationships between these phenomena. - - 2009-10-13 - - 09-042 - - Steffen Neubauer, Alexander Zipf - - 3D-Symbology Encoding Discussion Draft - This document present an extension of the Symbology Encoding (SE) /Styled Layer Descriptor (SLD) specifications into 3D as a separate profile. + + Simon Jirka, Arne Bröring, Daniel Nüst - - GeoPackage / OWS Context Harmonization Discussion Paper - 18-037r1 - 18-037r1 - - - - This OGC discussion paper presents an approach to harmonize the OGC GeoPackage and OWS Context standards through a set of extensions. GeoPackage is an open, standards-based, platform-independent, portable, self-describing, compact format for storing and transferring geospatial data and information as part of an SQLite database. OWS Context is an open format linking geospatial web services and information. A draft standard has been produced and this Discussion Paper is designed to be a companion to that draft standard to assist in discussion. The draft standard contains extensions to both GeoPackage and OWS Context. - -This document is the work of collaboration between the GeoPackage and OWS Context Standards Working Groups (SWGs). + + 2008-04-29 - 2018-10-29 - Jeff Yutzler - + + + Peter Rushforth - GeoPackage / OWS Context Harmonization Discussion Paper + CGDI WFS and GML Best Practices + 08-002 + + 08-002 + + OGC® Canadian Geospatial Data Infrastructure WFS and GML Best Practices + This document gives guidelines and recommendations for administrators, users and implementers of Web Feature Services serving Geography Markup Language encoded response documents. - + + Web Services Security + 17-007r1 + Andreas Matheus + + This standard applies to a deployed OGC Web Service instance for which the protocol scheme of all operation endpoint URLs, exposed in the Capabilities document, is ‘https’ as defined in RFC 7230, section 2.7.2. + +A security-annotated Capabilities document is one which uses the <Constraint> element(s) to express the existence of security controls on the operation of the service instance or support for a particular security feature. Applying the tests as defined in the Annexes can validate compliance for a service, the client and the OGC management process. Basically, a service can be described by a Capabilities document that includes security annotations as defined in this standard. A client loading these Capabilities and parse for the <Constraint> element(s) can determine the security controls implemented for each operation of the service instance. The string value of this element’s name attribute contains the identifier of the implemented requirements class. + +How the client obtains the security-annotated capabilities is out of scope for this standard. + +This standard defines one common abstract Requirements Class and three Capabilities document structure specific Requirements Classes. The structure specific classes address how the requirements are implemented for WMS 1.1.1, WMS 1.3 and OWS Common based service Capabilities documents. + + - 2007-06-06 - 07-032 - - - - Frame image geopositioning metadata GML 3.2 application schema - 07-032 - Frame image geopositioning metadata GML 3.2 application schema - Arliss Whiteside - This document specifies a GML 3.2 Application Schema for frame image geopositioning metadata, for XML encoding of the georeferencing coordinate transformation parameters of an unrectified frame image. A frame image is one whose entire two-dimensional extent was collected at one time. A georeferencing coordinate transformation can transform position coordinates between a specific ground-based (or object) Coordinate Reference System (CRS) and the image CRS. + + 17-007r1 + + OGC Web Services Security + 2019-01-28 - + - - 14-016 - OGC® Testbed-10 CCI VGI Engineering Report - 14-016 - Testbed-10 CCI VGI Engineering Report - 2014-07-15 - This Engineering Report was created as a deliverable for the OGC Testbed 10 (Testbed- -10) initiative of the OGC Interoperability Program. This report describes an approach for -integrating Volunteered Geographic Information (VGI) into a spatial data infrastructure -and reports on findings about the advancements using VGI resources. It includes -optimization ideas, service change recommendations, and lessons learned. -This is not a normative document. - + 09-035 + 09-035 + OWS-6 Security Engineering Report + + + This Engineering Report describes work accomplished during the OGC Web Services Testbed, Phase 6 (OWS 6) to investigate and implement security measures for OGC web services. This work was undertaken to address requirements stated in the OWS-6 RFQ/CFP originating from a number of sponsors, from OGC staff, and from OGC members. + Rüdiger Gartmann, Lewis Leinenweber + OWS-6 Security Engineering Report - Arne Bröring;Simon Jirka;Matthes Rieke, Benjamin Pross + 2009-10-09 - - Corrigendum 2 for the OGC Standard Web Coverage Service 1.1 - 07-066r5 - Corrigendum 2 for the OGC Standard Web Coverage Service 1.1 - This document provides the details of a corrigendum to an OpenGIS Implementation Standard and does not modify the base standard. The OGC Standard that this document provides revision notes for is Web Coverage Service Standard, Version 1.1 Corrigendum 2 [OGC 07-067r5]. - 2008-04-29 - - Arliss Whiteside - + + + + + + + + Documents of type Policy Document - - 07-066r5 - - + Documents of type Policy Document + + Documents of type Policy Document - - 09-046r6 - - 09-046r6 - OGC Naming Authority - Procedures - - OGC Naming Authority - Procedures - - - - Gobe Hobona, Simon Cox - - 2021-09-27 - The mission of the OGC Naming Authority (OGC-NA) is to provide the means through which OGC resources such as OGC documents, namespaces and ontologies can be controlled and managed such that they can provide clear and well-defined names and definitions. In the terminology defined in ISO 19135, OGC-NA is the Control Body for the register of OGC Names. This document describes the framework of documents, registers and other resources required for OGC-NA to execute that role. + + + + + + + + + - - Volume 3: OGC CDB Terms and Definitions - 15-112r2 - Carl Reed - + + + + + + The OpenGIS® Geography Markup Language Encoding Standard (GML) The Geography Markup Language (GML) is an XML grammar for expressing geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. As with most XML based grammars, there are two parts to the grammar – the schema that describes the document and the instance document that contains the actual data. +A GML document is described using a GML Schema. This allows users and developers to describe generic geographic data sets that contain points, lines and polygons. However, the developers of GML envision communities working to define community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas] that are specialized extensions of GML. Using application schemas, users can refer to roads, highways, and bridges instead of points, lines and polygons. If everyone in a community agrees to use the same schemas they can exchange data easily and be sure that a road is still a road when they view it. + +Clients and servers with interfaces that implement the OpenGIS® Web Feature Service Interface Standard[http://www.opengeospatial.org/standards/wfs] read and write GML data. GML is also an ISO standard (ISO 19136:2007) [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32554 ]. +See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml . + - - - 2017-02-23 + 07-036 + Geography Markup Language (GML) Encoding Standard + 2007-10-05 - 15-112r2 + + Clemens Portele + 07-036 + + - This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice. - Volume 3: OGC CDB Terms and Definitions + OpenGIS Geography Markup Language (GML) Encoding Standard - - 20-025r1 - - - 2021-01-06 + + This report documents the Second Environmental Linked Features Interoperability Experiment (SELFIE). SELFIE evaluated a proposed Web resource model and HTTP behavior for linked data about and among environmental features. The outcomes are building blocks to establish a system of real-world feature identifiers and landing pages that document them. OGC API - Features was found to be a useful component for systems implementing both landing content and representations of linked-features. More work is needed to establish best practices related to negotiation between varied representations of a feature, observations related to a feature, and for expressing and mediating between varied content from a given resource. These technical / meta-model details were found to be difficult to evaluate given the small number of example implementations and limited number of domain-feature models available for use with linked data. + David Blodgett + + - 20-025r1 - Data Access and Processing API Engineering Report - - OGC Testbed-16: Data Access and Processing API Engineering Report - Luis Bermudez - This OGC Testbed 16 Engineering Report documents the advancement of an OGC Data Access and Processing API (DAPA). - - - - + Second Environmental Linked Features Experiment + 2020-10-22 + 20-067 + Second Environmental Linked Features Experiment + 20-067 + - - 2012-04-06 - Rob Atkinson, Irina Dornblut - - + + 09-073 + OWS-6 SWE PulseNet™ Engineering Report + - HY_Features: a Common Hydrologic Feature Model Discussion Paper - - 11-039r2 + OWS-6 SWE PulseNet™ Engineering Report + + This document summarizes work delivered on the Sensor Web Enablement (SWE) thread of OWS-6. In particular, Northrop Grumman’s contribution from PulseNet™ to the Common Chemical, Biological, Radiological, and Nuclear (CBRN) Sensor Interface (CCSI) standard-compliant sensors into an OGC SWE-based architecture. + 2009-08-05 + + + 09-073 - - This document describes a conceptual model for the identification of hydrologic features independent from geometric representation. This model allows common reference to hydrologic features across scientific sub-disciplines in hydrology. The Hydrologic Feature Model, HY_Features, is designed as a set of interrelated Application Schemas using ISO 19103 Conceptual Schema Language and ISO 19109 General Feature Model. It is factored into relatively simple components that can be reviewed, tested and extended independently. - 11-039r2 - HY_Features: a Common Hydrologic Feature Model Discussion Paper + James Ressler - - OGC WaterML 2: Part 4 - GroundWaterML 2 (GWML2) - Boyan Brodaric - OGC WaterML 2: Part 4 - GroundWaterML 2 (GWML2) - 16-032r3 - 2021-01-20 - - This standard describes a conceptual and logical model for the exchange of groundwater data, as well as a GML/XML encoding with examples. - 16-032r3 - + + Introduction and roadmap to the Abstract specification. + Cliff Kottman + + 1999-06-23 - - + + + Topic 0 - Overview + + 99-100r1 + 99-100r1 + Topic 0 - Overview - - 2007-11-23 - Google, Galdos - + + + + R. Martell + This Engineering Report (ER) presents guidance concerning the use of OGC® catalog services in the aviation domain. A wide variety of metadata resources can be readily published and discovered using the OGC CSW-ebRIM application profile, which marries the CSW catalog interface to the OASIS ebXML registry information model (ebRIM). However, existing SWIM registries currently under development by the FAA and Eurocontrol do not implement any OGC standards. This report explores the prospects for enhancing SWIM registries by a) integrating OGC catalog functionality, and b) accommodating OGC service descriptions. + 2017-06-15 + 16-024r2 + Testbed-12 — Catalog Services for Aviation + Testbed-12 — Catalog Services for Aviation + + 16-024r2 + + + + + 11-134 + OWS-8 Tracking: Moving Target Indicator Process, Workflows and Implementation Results ER - KML 2.2 Reference - An OGC Best Practice - 07-113r1 + + 11-134 - - 07-113r1 - - KML is a file format used to display geographic data in an Earth browser, such as Google Earth, Google Maps, and Google Maps for Mobile. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard. - KML 2.2 Reference - An OGC Best Practice + Rob Cass, Mark Simms + + + 2012-05-15 + + OWS-8 Tracking: Moving Target Indicator Process, Workflows and Implementation Results ER + The scope of this report is to provide a description of services, data storage and data +movement within the OWS-8 Tracking sub-thread. The paper outlines the development +of Sensor Observation Services (SOS), a Web Feature Service(WFS), a Notification +Service and a Web Processing Service (WPS) for generating track features. Additionally, +implemented encodings will be discussed as examples and in comparison to the +encodings detailed in (Simonis, 2011). - - Andrea Biancalana, Pier Giorgio Marchetti, Paul Smits - + - - GIGAS Methodology for comparative analysis of information and data management systems - 10-028r1 - This document has been written on the basis of a methodology developed within the GIGAS Support Action financed by the European Commission in order to address the convergence of global initiatives like GEOSS and the European interoperability initiatives developed in the context of the GMES programme like HMA - Heterogeneous Missions Accessibility and the INSPIRE spatial data infrastructure legislation. - 10-028r1 - + This document specifies the core Abstract Specification and extension mechanisms for Discrete Global Grid Systems (DGGS). A DGGS is a spatial reference system that uses a hierarchical tessellation of cells to partition and address the globe. DGGS are characterized by the properties of their cell structure, geo-encoding, quantization strategy and associated mathematical functions.The OGC DGGS Abstract Specification supports the specification of standardized DGGS infrastructures that enable the integrated analysis of very large, multi-source, multi-resolution, multi-dimensional, distributed geospatial data. Interoperability between OGC DGGS implementations is anticipated through implementation standards, and extension interface encodings of OGC Web Services. + Matthew Purss + 15-104r5 + + 15-104r5 + Topic 21 - Discrete Global Grid Systems Abstract Specification + Topic 21 - Discrete Global Grid Systems Abstract Specification + 2017-08-01 + - 2010-06-04 - GIGAS Methodology for comparative analysis of information and data management systems + - - 2011-11-23 - + + OGC SensorThings API Tasking Core Discussion Paper - Event Service - Review and Current State - 11-088r1 - - 11-088r1 - Johannes Echterhoff, Thomas Everding + 18-056 + SensorThings API Tasking Core Discussion Paper + - OGC® Event Service - Review and Current State - - This Discussion Paper provides information on what has so far been called “Event Service” at OGC. -The presented work is supported by the European Commission through the ESS project (integrated project, contract number 217951) and the GENESIS project (integrated project, contract number 223996) . + This discussion paper offers descriptions and provides JSON examples of TaskingCapabilities and Tasks for the SensorThings Application Programming Interface (API). + + 2018-12-18 + + Steve Liang, Tania Khalafbeigi, Kan Luo + 18-056 + + + + Howard Butler + This Engineering Report (ER) describes requirements that a point cloud web service must satisfy to enable application developers to provide convenient remote access to point clouds. It provides a short contrast of five point cloud web service software approaches (Esri I3S, 3D Tiles, Greyhound, PotreeConverter, and Entwine) and their implementations available at the time of the report. A small industry survey about these requirements is also provided in support of the report’s discussion about formats, web service requirements, industry support, and industry desire on these topics. + + + Point Cloud Data Handling Engineering Report + 18-048r1 + 2019-03-08 + + 18-048r1 + + + + OGC Testbed-14: Point Cloud Data Handling Engineering Report - - Bastian Baranski - OWS-6 WPS Grid Processing Profile Engineering Report - 09-041r3 - OWS-6 WPS Grid Processing Profile Engineering Report - This OGC Engineering Report describes and reviews the Grid Computing related activity completed during the OGC OWS-6 Interoperability testbed. The document describes the WPS processes deployed in the different demonstration scenarios and offers recommendations to the OGC community as to how to better harmonize the standards work of the OGC with Grid Computing platforms and related concepts and technologies. - 2009-07-24 + + + David Burggraf, Ron Lake + + 11-062r2 + The OWS-8 Cross Community Interoperability (CCI) thread was built on progress made in the recent OWS-7 initiative to cover key technology areas that could not be addressed within the scope of that initiative. The OWS-8 CCI thread aimed to increase interoperability within communities sharing geospatial data, including advancing of interoperability among heterogeneous data models, advancing strategies to share styles to provide a more common and automated use of symbology, improvement of KML, and advancing schema automation allowing communities to better share their information artifacts. This OGC engineering report aims to present findings from the portrayal registries as part of the CCI subthread + OWS-8 CCI Portrayal Registries Engineering Report + 11-062r2 + 2011-11-17 + - 09-041r3 - - - + OWS-8 CCI Portrayal Registries Engineering Report - - This OGC Best Practices document specifies the interfaces, bindings, requirements, conformance classes that enable complete workflows for ordering Earth Observation (EO) data products. In fact it provides the interfaces for supporting the following EO Product ordering scenarios: -• Ordering products from EO Catalogues -• Subscribing to automatic delivery of EO products -• Bulk EO Product orders -The EO products orders can be delivered on file via different online protocols (e.g. ftp, sftp, ftps, etc.). - - 2014-04-28 - 13-042 - OGC RESTful Encoding of Ordering Services Framework For Earth Observation Products + + + 08-129 + + + GML 3.2 implementation of XML schemas in 07-002r3 + 2009-03-06 + Simon Cox + GML 3.2 implementation of XML schemas in 07-002r3 + 08-129 + + - Daniele Marchionni - 13-042 - RESTful Encoding of Ordering Services Framework For Earth Observation Products - - - + + + 07-118r9 + + + 07-118r9 + User Management Interfaces for Earth Observation Services + OGC User Management Interfaces for Earth Observation Services + 2014-04-28 + This OGC Best Practice describes how user and identity management information may be included in the protocol specifications for OGC Services. The proposed approach is applicable to the orchestration of EO services, to system of systems and federation scenarios. The approach is meant to be independent from the specific OGC service. The use cases potentially addressed are very wide and in general may cover geospatial services and not only EO (Earth Observation) services. The use cases may range from web map, feature or coverage services, web processing services, to catalogue services. Examples of EO specific use cases are: ordering (Ordering Services for Earth Observation Products [OGC 06-141r6]) and feasibility analysis (OpenGIS Sensor Planning Service Application Profile for EO Sensors [OGC 10 135]). +The document was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [OR1] and related projects. +This document is not an OGC standard. This document describes how existing specifications from W3C and OASIS can be used in combination to pass identity information to OGC Web services. + + + P. Denis, P. Jacques + + - - The Testbed-13 Earth Observation Clouds (EOC) effort supports the development of ESA’s Thematic Exploitation Platforms (TEP) by exercising envisioned workflows for data integration and processing that are deployed in multiple clouds. The Application Deployment & Execution Service OGC Engineering Report (ER) identifies the Application Programming Interface (API) for delivering all functionality provided to realize the testbed scenario. + + The OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 JSON Profile v1.0 (GeoXACML 3.0 JSON Profile) Standard defines an extension to the JSON Profile of XACML 3.0 Version 1.1 for supporting GeoXACML Authorization Decision Requests and Authorization Decision encoded in JSON. This ensures an easy uptake in environments where JSON is the preferred encoding. -This ER will list the requirements fulfilled by Cloud APIs in order to allow an automation of the application package deployment and execution workflow and capture implementation process experiences. +For supporting Geometry as defined by the GeoXACML 3.0 Core conformance class, this profile extends the Attribute DataType definition from JSON Profile of XACML 3.0 Version 1.1 with the geometry data-type urn:ogc:def:geoxacml:3.0:data-type:geometry - - 17-024 - Testbed-13: Application Deployment and Execution Service Engineering Report - Pedro Gonçalves - OGC Testbed-13: Application Deployment and Execution Service Engineering Report - - 2018-01-11 - 17-024 +The GeoXACML 3.0 JSON Profile Standard supports the Attribute value to use Well-Known-Text (WKT), Well-Known-Binary (WKB) hex-encoding or GeoJSON as an encoding alternative for the geometry data-type defined in GeoXACML 3.0. + +To support the use of the GeoXACML 3.0 specific attributes SRID, Precision, Encoding, and AllowTransformation, this profile extends the default JSON schema definition from JSON Profile of XACML 3.0 Version 1.1 accordingly. + + 22-050r1 + + OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 JSON Profile v1.0 + OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 JSON Profile v1.0 + 22-050r1 + + + Andreas Matheus - - - + 2023-09-21 - - Volume 4: OGC CDB Rules for Encoding CDB Vector Data using Shapefiles (Best Practice) - Carl Reed - - + + 2021-02-11 + Demand for digital representations of built environments is accelerating and can only be satisfied through greater software interoperability and data integration. The objective of the Integrated Digital Built Environment (IDBE) joint working group is to address this challenge by bringing together experts from the Open Geospatial Consortium and buildingSMART to coordinate the development of the relevant data standards. This document is an output from IDBE in which we describe the state of three of the most prominent built environment standards – CityGML, IFC and LandInfra – and describe some of the problems that hinder their integration; finally, we propose actions points for overcoming these problems. + Thomas Gilbert, Carsten Rönsdorf, Jim Plume, Scott Simmons, Nick Nisbet, Hans-Christoph Gruler, Thom - 16-070r4 - Volume 4: OGC CDB Rules for Encoding CDB Vector Data using Shapefiles (Best Practice) + + 19-091r2 - 2021-02-26 - - - 16-070r4 - This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features. + Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra + + 19-091r2 + Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra + + - - This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. - Carl Reed + + + 2017-01-31 + + Geoscience Markup Language 4.1 + 16-008 + GeoSciML is a model of geological features commonly described and portrayed in geological maps, cross sections, geological reports and databases. The model was developed by the IUGS CGI (Commission for the Management and Application of Geoscience Information) and version 4.1 is the first version officially submitted as an OGC standard. This specification describes a logical model and GML/XML encoding rules for the exchange of geological map data, geological time scales, boreholes, and metadata for laboratory analyses. It includes a Lite model, used for simple map-based applications; a basic model, aligned on INSPIRE, for basic data exchange; and an extended model to address more complex scenarios. + +The specification also provides patterns, profiles (most notably of Observations and Measurements - ISO19156), and best practices to deal with common geoscience use cases. + + + GeoSciML Modeling Team + OGC Geoscience Markup Language 4.1 (GeoSciML) - 16-006r3 - - Volume 10: OGC CDB Implementation Guidance - 2017-02-23 - - 16-006r3 - Volume 10: OGC CDB Implementation Guidance - - + + + 16-008 - - This OGC Engineering Report (ER) documents the findings and experiences resulting from Terradue Activities on the OGC Earth Observation Applications Pilot. More specifically, this ER provides a way forward for the implementation of the applications to the data paradigm in the context of Earth Observation (EO) satellite data processing and Cloud-based platforms to facilitate and standardize the access to Earth observation data and information. - Pedro Gonçalves - 20-042 - OGC Earth Observations Applications Pilot: Terradue Engineering Report + + + + + + + + + + + + + + + Documents of type Recommendation Paper - deprecated + Documents of type Recommendation Paper - deprecated + + + Documents of type Recommendation Paper - deprecated + + + + + + + + + + + + + + + + + + - + + 14-114r1 + 2014-12-30 + WaterML2.0 part 2 – rating tables, gauging observations and cross-sections: Interoperability Experiment Results + Part 1 of WaterML2.0 covers exchange of hydrological time-series data, the observational processes used to generate them, and information related to the monitoring points (stations/sites) where time-series data are typically collected. WaterML2.0 Part 2, is a candidate standard that defines how to exchange rating tables, gauging observations and cross-sections in an interoperable manner. +This engineering report outlines the design and results of an OGC Interoperability Experiment (IE) that implemented and tested the current WaterML2.0 part 2 information model. The OGC IE experiment ran was conducted from November 2013 to August 2014. The use case for the IE involved exchange of data in three scenarios in Australia, US and the UK. +This report describes the software requirements, design, deployments and challenges faced by the experiment. The results were used to improve the WaterML2.0 part 2 information model and provided the basis for the formation of an OGC Standards Working Group (SWG) in August 2014. This SWG is responsible for formalization of the candidate OGC standard, for submission in 2015. + - 2020-10-22 + WaterML2.0 part 2 – rating tables, gauging observations and cross-sections: Interoperability Experiment Results + 14-114r1 - - 20-042 - OGC Earth Observations Applications Pilot: Terradue Engineering Report - - - 14-111r6 - WaterML 2: Part 3 - Surface Hydrology Features (HY_Features) - Conceptual Model - - 14-111r6 - - - - The OGC Surface Hydrology Features (HY_Features) standard defines a common conceptual information model for identification of specific hydrologic features independent of their geometric representation and scale. The model describes types of surface hydrologic features by defining fundamental relationships among various components of the hydrosphere. This includes relationships such as hierarchies of catchments, segmentation of rivers and lakes, and the hydrologically determined topological connectivity of features such as catchments and waterbodies. The standard also defines normative requirements for HY_Features implementation schemas and mappings to meet in order to be conformant with the conceptual model. - -The HY_Features model is based on an abstract catchment feature type that can have multiple alternate hydrology-specific realizations and geometric representations. It supports referencing information about a hydrologic feature across disparate information systems or products to help improve data integration within and among organizations. The model can be applied to cataloging of observations, model results, or other study information involving hydrologic features. The ability to represent the same catchment, river, or other hydrologic feature in several ways is critical for aggregation of cross-referenced or related features into integrated data sets and data products on global, regional, or basin scales. - David Blodgett, Irina Dornblut - OGC® WaterML 2: Part 3 - Surface Hydrology Features (HY_Features) - Conceptual Model - - 2018-01-08 + Peter Taylor - - The general models and XML encodings for observations and measurements, including but not restricted to those using sensors. - - + + + 06-121r3 + Web Service Common Implementation Specification + 2007-04-03 + + Arliss Whiteside + The OpenGIS® Web Services Common (WS-Common) Interface Standard specifies parameters and data structures that are common to all OGC Web Service (OWS) Standards. The standard normalizes the ways in which operation requests and responses handle such elements as bounding boxes, exception processing, URL requests, URN expressions, and key value encoding. Among its uses, this document serves as a normative reference for other OGC Web Service standards, including the OpenGIS Web Map Service (WMS) [http://www.opengeospatial.org/standards/wms], Web Feature Service (WFS) [http://www.opengeospatial.org/standards/wfs], and Web Coverage Service (WCS) [http://www.opengeospatial.org/standards/wcs] standards. Rather than continuing to repeat this material in each such standard, each standard will normatively reference parts of this document. + 06-121r3 - 05-087r3 - Observations and Measurements - - Simon Cox + + OpenGIS Web Service Common Implementation Specification + - Observations and Measurements - 05-087r3 - - 2006-04-05 - - Access Control & Terms of Use (ToU) "Click-through" IPR Management - 05-111r2 + + This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the extension of the OGC Styled Layer Descriptor (SLD) symbology format for improved capability and harmonization with ISO 19117 symbology, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology. + OWS-6 Styled Layer Descriptor (SLD) Changes ER + 09-015 + + 2009-09-11 + + 09-015 - + - 2006-05-09 - Access Control & Terms of Use (ToU) "Click-through" IPR Management - This document demonstrats a number of functional capabilities related to rights management (Terms-of-Use, Authentication, content services) that need to be described and chained. - - Roland M. Wagner - - 05-111r2 - - - - 2022-06-30 - This Community Standard refers to the Zarr V2 Specification. The Zarr V2 Specification -is hosted on the Zarr website at https://zarr.readthedocs.io/en/stable/spec/v2.html. The -Zarr V2 Specification is the OGC Community Standard. Everything that follows is a -non-normative, informal description of Zarr usage written for the benefit of the geospatial -community. - Zarr Storage Specification 2.0 Community Standard - 21-050r1 - Zarr Developers - - + OWS-6 Styled Layer Descriptor (SLD) Changes ER - 21-050r1 - Zarr Storage Specification 2.0 Community Standard - - - + Craig Bruce - - - OGC® Testbed 11 Implementing JSON/GeoJSON in an OGC Standard Engineering Report - In the OGC Testbed 11, the Cross-Community Interoperability (CCI) thread had a key objective of building on the work accomplished in the OGC 8, 9 and 10 Testbeds. The goal of the CCI threads is to increase interoperability between communities sharing geospatial data. This thread made advances in semantic mediation approaches for data discovery, access and use of heterogeneous data models and heterogeneous metadata models. This particular Engineering Report (ER) is part of the OGC efforts to advance the OGC Architecture with the adoption of REST interfaces and more encodings such as JSON. - + + Topic 2 - Spatial Referencing by Coordinates + - Testbed 11 Implementing JSON/GeoJSON in an OGC Standard Engineering Report - 15-053r1 - + + 2003-10-16 + + 03-073r1 + Topic 2 - Spatial Referencing by Coordinates + - 15-053r1 - - Joan Masó - 2015-08-19 + Roel Nicolai + Describes modelling requirements for spatial referencing by coordinates. + 03-073r1 - - 09-153r1 - Peter Baumann + - 2012-01-25 - - OGC® Web Coverage Service 2.0 Primer: Core and Extensions Overview + Simon J D Cox, Bruce A Simons + 2014-12-02 + + 14-003 + WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data - Web Coverage Service 2.0 Primer: Core and Extensions Overview - 09-153r1 - + WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data - This document provides an overview on the OGC Web Coverage Service (WCS) 2.0 suite by describing WCS core and extensions. -Intended target audience are developers intending to implement WCS servers and/or clients. This document aims at providing an overview and giving useful hints and best practices beyond the pure standards texts. It is a &quot;living document&quot; which will evolve to reflect new developments and best practices. -As such, the contents of this document is informative and not of normative nature. - + + This Best Practice describes how to configure XML documents for single and time series water quality measurements. In addition to stating the rules for using the O&M and WML 2 standards, along with the appropriate content ontologies, this Best Practice provides guidance through examples. This document is intended to complement WaterML 2.0 as part of a suite of standards for water observation data. + 14-003 - - CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language version 3.1.1 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211. + + + + 2024-04-29 + OGC Disaster Pilot: User Readiness Guide + 21-075r2 + + + + Disasters are geographic events and therefore, geospatial information, tools and applications have the potential to support the management of, and response to, disaster scenarios. -The aim of the development of CityGML is to reach a common definition of the basic entities, attributes, and relations of a 3D city model. This is especially important with respect to the cost-effective sustainable maintenance of 3D city models, allowing the reuse of the same data in different application fields. - - OpenGIS® City Geography Markup Language (CityGML) Encoding Standard - 08-007r1 - City Geography Markup Language (CityGML) Encoding Standard - 2008-08-20 +However, the use of geospatial data varies significantly across disaster and emergency communities. This can often make it difficult to share information between different organizations, and sometimes even within the same organization, involved in disaster response. This could mean that not everyone involved will have the same situational awareness information. + +There are many reasons for why geospatial information is fully used and exploited, included a lack of awareness of what geospatial options are available, lack of geospatial technology and skills, lack of funding, etc. The Disaster Pilot User Guide aims to address some of these issues by providing a non-technical showcase of the workflows and tools developed by the Pilot participants demonstrating what opportunities there are for disaster and emergency management communities to use geospatial solutions in practice. + +For over 20 years, the Open Geospatial Consortium (OGC) has been working on the challenges of information sharing for emergency and disaster planning, management, and response. In Disaster Pilot 23 (DP23) the aims were to: + +Develop flexible, scalable, timely and resilient information data workflows to support critical disaster management decisions, enabling stakeholder collaboration, and +Provide applications and visualization tools to promote the wider understanding of how geospatial data can support emergency and disaster communities. +As part of DP23, a trilogy of Guides were developed to improve knowledge and understanding of how geospatial data and tools and could support disaster and emergency communities. Alongside the User Guide is a Provider Guide giving all the detail technical details behind the work, and a companion Operational Capacity Guide describing the steps needed to develop geospatial readiness. + +The User Guide contains a summary of the work undertaken in DP23, and Disaster Pilot 21 (DP21), where participants have worked on disaster scenarios relating to: + +Droughts +Wildland Fires +Flooding +Landslides +Health & Earth Observation Data for Pandemic Response +Case Studies have focused on the hazards of drought in Manitoba, Canada; wildland fires in western United States; flooding in the Red River basin, Canada; landslides and flooding in Peru; and Pandemic response in Louisiana, United States. The participants have developed various data flows, alongside tools to support the collection, discovery, or visualization of data to support disaster management and response. + +Annex A describes the tools and applications developed within the Pilots alongside the benefits these can offers. The Guide finishes with details of future possibilities, and where the Disaster Pilot initiative could focus next. Annexes B to E give descriptions of the data flows developed, including the aspects of disaster management or response the data flow relates to; together with the benefits it offers and the type of decisions it can support. + +This document is for first responders, emergency managers, decision-makers, and anyone interested in encouraging disaster and emergency communities to realize the value of geospatial data to save lives and limit damage. + Andrew Lavender, Samantha Lavender + 21-075r2 + + OGC Disaster Pilot: User Readiness Guide + + + + Joint OGC and ISO Code Sprint 2022 Summary Engineering Report + 22-043r1 + 2022-12-16 + + + + + Gobe Hobona, Joana Simoes - + Joint OGC and ISO Code Sprint 2022 Summary Engineering Report + The subject of this Engineering Report (ER) is a code sprint that was held from the 14th to the 16th of September 2022 to advance open standards that relate to geospatial metadata and catalogues. The code sprint was hosted by the Open Geospatial Consortium (OGC) and the International Organization for Standardization (ISO). The code sprint was sponsored by Ordnance Survey (OS) and Geonovum, and held as a hybrid event with the face-to-face element hosted at the Geovation Hub in London, United Kingdom. + 22-043r1 + + + 07-024 + This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It contains a platform-neutral specification of the ORCHESTRA Architecture and a specification framework for the design of ORCHESTRA-compliant service networks across all viewpoints. + Reference Model for the ORCHESTRA Architecture + 07-024 + Reference Model for the ORCHESTRA Architecture - - + + - Gerhard Gröger, Thomas H. Kolbe, Angela Czerwinski, Claus Nagel - 08-007r1 + + 2007-07-26 + + Thomas Uslander (Ed.) - - 00-106 - Incomplete. This document normatively references parts of the previous version of AS Topic 6, document 00-106. Need to be updated to include Roswell Change Proposal (01-011), which includes 19123 and retains material from Topic 6, v6. - 00-106 - Topic 06 - The Coverage Type - - Topic 6 - The Coverage Type - Cliff Kottman, Charles Roswell + + OGC Earth Observation Applications Pilot: Spacebel Engineering Report + 20-034 + + + This Engineering Report (ER) describes the achievements of Spacebel as a Platform Provider in the OGC Earth Observation Applications (EO Apps) Pilot and the lessons learned from the project. + + 2020-10-22 + OGC Earth Observation Applications Pilot: Spacebel Engineering Report + Christophe Noël + + + 20-034 + + + 04-086 + EA-SIG Discovery White Paper + 04-086 + + 2004-02-20 + - 2000-04-18 - + Jeff Harrison,A.J. Maren,Jeff Stohlman,Mike Meyer,Glenn Pruitt,John Clink,Hans Polzer,Mark Schiffner - + + *RETIRED* This document describes the role of Discovery Services in the net-centric enterprise. The network centric enterprise is an environment with an almost infinite variety of resources. In this rich environment, suitable resources can be found to support almost any operational need. The problem, however, is finding the appropriate resources when they are needed. Discovery services address this problem. + EA-SIG Discovery White Paper + - - - - - - - - - + + + + + + + + - - Benjamin Pross - 2017-06-30 - Testbed-12 WPS Conflation Service Profile Engineering Report - 16-022 - 16-022 - + - - One practical purpose of this ER will be to describe how a conflation tool such as the Hootenanny software can be used for conflation tasks using the Web Processing Service interface. The developed WPS REST (conflation) Service will be described in detail. Special focus will be laid on more complex conflation tasks that include user interaction. During earlier testbeds, we connected different conflation tools to the WPS and performed different conflation tasks (see [1] and [2]). The experiences gathered there together with the ones gathered in the Testbed 12 will be captured in the ER. As the WPS REST (Conflation) Service will be RESTful, this ER could be the basis for a REST binding extension for WPS 2.0. Service profiles are an important aspect of the WPS 2.0 standard. We will investigate how a WPS 2.0 Conflation Profile could look like in the hierarchical profiling approach of WPS 2.0. + - - - Testbed-12 WPS Conflation Service Profile Engineering Report + + OGC-NA Name type specification - documents + 09-047r3 + + Simon Cox + 2011-03-01 + OGC-NA Name type specification - documents + 09-047r3 + This document specifies a rule for constructing OGC names that may be used for identifying documents and elements within a document. + - - + + Testbed-12 WCS Profile Update Engineering Report + 16-033r1 + Testbed-12 WCS Profile Update Engineering Report + 2017-04-28 - - 18-045 + 16-033r1 + + Ranjay Shrestha, Liping Di, Eugene G. Yu - Next Generation Web APIs - WFS 3.0 Engineering Report - 18-045 - - Jeff Harrison, Panagiotis (Peter) A. Vretanos - OGC Testbed-14: Next Generation Web APIs - WFS 3.0 Engineering Report - The objective of the Next Generation APIs - WFS 3.0 effort in OGC Testbed-14 was to develop and test the Web Feature Service (WFS) version 3.0 candidate standard. The initiative assessed OpenAPI, security based on OpenID Connect and OAuth 2.0 and WFS 3.0 extensions. The effort also began to assess methods to ease geospatial enterprise transition to next generation Application Programming Interfaces (APIs). + + + This engineering report capture the work to extend the existing Web Coverage Service (WCS) profiles, particularly the Earth Observation Application Profile (EO-WCS [OGC 10-140r1]) to support multi-dimensional subsetting of 3D space and 1D time. The updated EO-WCS (EO-WCS1.1 [OGC 10-140r2]) have removed the requirement for the 2D coverages so that it can explicitly allow coverages with more dimensions as long as they have geographic footprint. Furthermore it also clarified the use of rangeType when non-NCNAME characters are present in a band identifier. The example of GetCapabilites, DescribeEOCoverageSet, and _GetCoverage request in the updated EO-WCS1.1 is shown with use case on fire emission data in San Francisco. -The purpose of this effort was not to preempt other next generation work taking place in OGC, but rather to inform and complement that work. +Following the recommendation for EO-WCS to fully embrace the N-D, multi-dimensional, concept of Coverages as a function of time and other coordinates alongside the geospatial ones, the proposed recommendations/changes in the extension for WCS DescribeCoverage, EO-WCS DescribeEOCoverageSet, and WCS GetCoverage are discussed with use case example using National Centers for Environmental Prediction (NCEP) Global 0.25 deg wind data. Based on the mutual recommendation from the US National Aeronautics and Space Administration (NASA) and Baart et. al (2012), Network Common Data Form (NetCDF) was the output format due to presence of its libraries in multiple languages to lower the burden in changing on developers of WCS-compliant servers and clients. -This Engineering Report (ER) describes the implementations and experiments conducted by OGC Testbed-14 participants to test next generation Web APIs. It includes descriptions of APIs to simplify and secure access to geospatial feature resources, and was tested in a scenario that showed how WFS 3.0 can support humanitarian relief activities. - 2019-03-07 - - - - - - - - 03-063r1 - Critical Infrastructure Collaborative Environment Architecture: Computational Viewpoint - Joshua Lieberman - 03-063r1 - Critical Infrastructure Collaborative Environment Architecture: Computational Viewpoint - 2003-06-02 - *RETIRED* The objective of this document is to provide a vendor-neutral interoperable framework that enables collaborating communities to rapidly and collaboratively publish, discover, integrate and use geospatial information concerned with the protection of critical infrastructure systems in a range of sectors. Specifically, this document specifies a Computational Architecture viewpoint for a Critical Infrastructure Collaborative Environment (CICE). - +For the extension of the WCS DescribeCoverage, it is recommended that CIS1.1 should be considered adopting a scheme for transmitting coordinates similar to the _cis:rangeSet where data are referred to as an attached Multipurpose Internet Mail Extensions (MIME) part. Time, as much as possible, be treated as just another coordinates dimension so that it could be access with the same tools used for other coordinate dimensions. To tackle the issue on order of coordinate dimensions, it is recommended to add implementation note to the EO-WCS specifications so that implementers are aware of the mismatches between dataset coordinate reference systems (CRSs) and actual axis order. + +For the extension of EO_WCS DescribeEOCoverageSet, the issue on missing range of results API needed to be resolved by adding a request mechanism for requesting a range of matching results. It is also recommended that DescribeEOCoverageSet activity might be of more use to the client if the client need to supply only the subset conditions, and not a list of identifiers. + +For the extension of WCS GetCoverage, it was discovered that for the GetCoverage operation for higher dimensioned datasets, existing WCS-2.0 request interface provided adequate syntax for subsetting higher dimensional data. Scaling (re-gridding) operation appears to be a natural fit for the EO-WCS subsetting, specifically SCALEEXTENT activity, however simpler explanation might be needed to fully understand its use as it appears other scaling and subsetting commands may be more than adequate for the desired outcomes. Additionally allowing SlicePoint subsetting is also recommended. + +After performing the testing in the client side, there were few potential recommendations for improvements. More information on whether the coverage is 2D or 3D form the GetCapalilites request might be helpful to client so it can limit the number of DescribeCoverage requests to construct a list of available coverage on the server. Furthermore additional metadata information for displaying meaningful native gird coordinates is also recommended for clarification. Finally automatic detection of lat/lon axes along with clear treatment of XY and lat/lon axes ordering would be an improvement in the existing operations. - + - This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for XML encoding of various geometric shapes required in the Presence Information Description Format (IETF RFC 3863) Location Object extension - A Presence-based GEOPRIV Location Object Format (RFC 4119). - GML PIDF-LO Geometry Shape Application Schema for use in the IETF - - - 2007-05-17 - Carl Reed, PhD. and Martin Thomson - 06-142r1 - GML PIDF-LO Geometry Shape Application Schema for use in the IETF - 06-142r1 - + Carl Reed + 07-107r3 + A URN namespace for the Open Geospatial Consortium (OGC) + 2008-05-02 + A URN namespace for the Open Geospatial Consortium (OGC) + + + This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC. The formal Namespace identifier (NID) is ogc. + 07-107r3 + - - 02-026r4 - - Mike Botts - Sensor Model Language (SensorML) for In-situ and Remote Sensors - - - - Sensor Model Language (SensorML) for In-situ and Remote Sensors - 02-026r4 - The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances. + + + Documents of type Technical Baseline - deprecated - - 2002-12-20 + Documents of type Technical Baseline - deprecated + + + Documents of type Technical Baseline - deprecated - - Dr. Markus M - - This Document specifies how a Web Map Service can be extended to allow user-defined styling. Different modes for utilizing Symbology Encoding for this purpose are discussed. - Styled Layer Descriptor Profile of the Web Map Service Implementation Specification - 05-078 - 2006-04-21 - - 05-078 - - - + + 01-009a + Coordinate Transformation Services - OLE/COM + 01-009a + + Provides interfaces for general positioning, coordinate systems, and coordinate transformations. + Martin Daly + Coordinate Transformation Services - OLE/COM - Styled Layer Descriptor Profile of the Web Map Service Implementation Specification - - - - OGC® SensorML: Model and XML Encoding Standard - The primary focus of the Sensor Model Language (SensorML) is to provide a robust and -semantically-tied means of defining processes and processing components associated -with the measurement and post-measurement transformation of observations. This -includes sensors and actuators as well as computational processes applied pre- and postmeasurement. -The main objective is to enable interoperability, first at the syntactic level and later at the -semantic level (by using ontologies and semantic mediation), so that sensors and -processes can be better understood by machines, utilized automatically in complex -workflows, and easily shared between intelligent sensor web nodes. -This standard is one of several implementation standards produced under OGC’s Sensor -Web Enablement (SWE) activity. This standard is a revision of content that was -previously integrated in the SensorML version 1.0 standard (OGC 07-000). - Mike Botts, Alexandre Robin - - 12-000 - 2014-02-04 - 12-000 - SensorML: Model and XML Encoding Standard - - + + + 2001-01-12 + + + + Eugene Genong Yu, Liping Di + This Engineering Report (ER) presents a summary, description and findings of the Swath Coverage task conducted by the OGC Testbed-14 initiative. + Swath Coverage Engineering Report + 18-047r3 + OGC Testbed-14: Swath Coverage Engineering Report - - - - 10-129r1 - 10-129r1 - Geography Markup Language (GML) - Extended schemas and encoding rules - - - - - Clemens Portele - 2012-02-07 - The Geography Markup Language (GML) is an XML encoding in compliance with ISO 19118 for the transport and storage of geographic information modelled in accordance with the conceptual modelling framework used in the ISO 19100 series of International Standards and including both the spatial and non-spatial properties of geographic features. - OGC® Geography Markup Language (GML) - Extended schemas and encoding rules - - - - This standard deals with enhancements to the netCDF (Network Common Data Form) data model for array-oriented scientific data.. -Two important data models for netCDF are: -- the “classic” netCDF model, used for netCDF-3 and earlier versions -- an enhanced data model, used in netCDF-4 and later versions. -The netCDF classic data model is defined in OGC 10-091r3, “NetCDF Core.” -This document specifies a netCDF extension standard for the enhanced data model. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space- and time-varying phenomena. -NetCDF (network Common Data Form) is a data model for array-oriented scientific data. The netCDF classic data model is specified in the netCDF core specification. This standard specifies the enhanced data model. A freely distributed collection of access libraries implementing support for that data model in a machine-independent format are available. Together, the interfaces, libraries, and format support the creation, access, and sharing of multi-dimensional scientific data. - OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard - + 2019-02-07 + + 18-047r3 + + + + + + OGC Testbed-15: Quebec Model MapML Engineering Report + 19-046r1 + + Scott Serich + - Ben Domenico - OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard - 11-038R2 - 11-038R2 - 2012-10-02 - + This OGC Testbed-15 Engineering Report (ER) describes the Map Markup Language (MapML) enabled client component implementation for the Quebec Lake-River Differentiation Model in the Machine Learning (ML) task of Open Geospatial Consortium (OGC) Testbed-15 (T-15). This ER presents the MapML parsing capabilities that were developed to illustrate the outputs of a ML model to delineate lake and river features from an undifferentiated waterbody vector dataset in Québec, Canada. Client data was accessed through an OGC Web Processing Service (WPS) interface in coordination with an OGC API - Features implementation. + 19-046r1 + 2020-01-08 + OGC Testbed-15: Quebec Model MapML Engineering Report + - - This document represents the release notes for the OGC Web Coverage Service (WCS) Interface Standard corrigendum 2.0.1. This corrigendum for WCS supersedes previous WCS versions. - WCS 2.0.1 Corrigendum Release Notes - 12-052 + + + 17-059 - 2012-07-12 - Peter Baumann - OGC WCS 2.0.1 Corrigendum Release Notes - 12-052 + The DGIWG Portrayal Technical Panel (DPTP) has been investigating how to standardize the portrayal of military context symbology within Web Services. The team sought to use version 1.1.0 of OGC Style Layer Descriptor standard and version 1.1.0 of Symbology Encoding (SLD and SE) standard to achieve this. +The team sought to apply military-specific symbology to military-specific topographic feature vector datasets within a number of software products. +The testing and experimentation highlighted a number of deficiencies in the SLD and SE standards which result in a barrier to interoperability. The ideal situation would be to have SLD and SE descriptors interoperable between all software products that implement the standard. This was found not to be the current situation. +This position paper describes the findings and outlines recommendations for a revised future version of the SLD and SE standards that resolves these issues. + + 2017-10-30 + Technical report from the DGIWG Portrayal Technical Panel testing of SLD (1.1.0) for OGC + Lars Schylberg, Lubos Belka + Technical report from the DGIWG Portrayal Technical Panel testing of SLD (1.1.0) for OGC + 17-059 - - - + + - - 03-031 - 03-031 - Style Management Service - Style Management Service - William Lalonde - - - 2003-01-20 + + 06-080 + GML Application Schema for EO Products + 06-080 + This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGCTM Catalogue Services Specification v2.0.0 (with Corrigendum) [OGC 04-021r3]. + + - - This document describes the proposed system design for the OGC Style Management Service (SMS). -The SMS must manage distinct objects that represent styles and symbols and provide the means to discover, query, insert, update, and delete these objects. -Styles provide the mapping from feature types and feature properties and constraints to parameterized Symbols used in drawing maps. Symbols are bundles of predefined graphical parameters and predefined fixed graphic images. - + + + Jerome Gasperi + 2006-07-27 + GML Application Schema for EO Products - - - + + Platforms for the exploitation of Earth Observation (EO) data have been developed by public and private companies in order to foster the usage of EO data and expand the market of Earth Observation-derived information. A fundamental principle of the platform operations concept is to move the EO data processing service’s user to the data and tools, as opposed to downloading, replicating, and exploiting data ‘at home’. In this scope, previous OGC activities initiated the development of an architecture to allow the ad-hoc deployment and execution of applications close to the physical location of the source data with the goal to minimize data transfer between data repositories and application processes. + +This document defines the Best Practice to package and deploy Earth Observation Applications in an Exploitation Platform. The document is targeting the implementation, packaging and deployment of EO Applications in support of collaborative work processes between developers and platform owners. + +The Best Practice includes recommendations for the application design patterns, package encoding, container and data interfaces for data stage-in and stage-out strategies focusing on three main viewpoints: Application, Package and Platform. + OGC Best Practice for Earth Observation Application Package + 20-089r1 + Best Practice for Earth Observation Application Package - 2008-08-25 - - Simon Cox + + + Pedro Gonçalves + - GML 3.2 implementation of XML schemas in 07-000 - 08-127 - GML 3.2 implementation of XML schemas in 07-000 - 08-127 - - + 2021-12-14 + + 20-089r1 - - Claude Speed - This OGC® document describes the architecture implemented in the OWS-9 Aviation thread, including: -• A description of the architecture used for the implementation of the OWS-9 Aviation Use Cases. -• An overview of the implemented components and workflows followed by a short description of each component. -• A discussion about discovery and registry methods and practices. -• Documentation of the issues, lessons learned as well as accomplishments and scenarios that were of general interest in the Aviation thread. -More detailed information on specific aspects considered in OWS-9 Aviation may be found in the individual Aviation Engineering Reports. - - OWS-9 Aviation Architecture Engineering Report - 12-147 - - 2013-02-06 + + Martin Klopfer + 14-029r2 + Testbed 10 Virtual Global Gazetteer Engineering Report - - 12-147 + 2014-07-16 + 14-029r2 + + - OWS-9 Aviation Architecture Engineering Report - + This document provides a technical description of the Virtual Global Gazetteer implemented for OGC Testbed 10. +The Virtual Global Gazetteer integrates two gazetteers – a copy of the USGS gazetteer containing domestic names and a copy of the NGA gazetteer containing non-domestic names (hosted by Interactive Instruments) and provides the capability to link to additional local gazetteers and linked data information, allowing a user to retrieve extended information on locations selected from either of the initial gazetteers. The access to linked data information provided by these gazetteers was achieved by GeoSPARQL enabling these gazetteers using semantic mapping components + + + OGC® Testbed 10 Virtual Global Gazetteer Engineering Report - - Sara Saeedi - Volume 11: OGC CDB Core Standard Conceptual Model - This Open Geospatial Consortium (OGC) standard defines the conceptual model for the OGC CDB 1.0 Standard. The objective of this document is to provide an abstract core conceptual model for a CDB data store (repository). The model is represented using UML (unified modeling language). The conceptual model is comprised of concepts, schema, classes and categories as well as their relationships, which are used to understand, and/or represent an OGC CDB data store. This enables a comparison and description of the CDB data store structure on a more detailed level. This document was created by reverse-engineering a UML model and documentation from the OGC CDB standard as a basis for supporting OGC interoperability. One of the important roles of this conceptual model is to provide a UML model that is consistent with the other OGC standards and to identify functional gaps between the current CDB data store and the OGC standards baseline. This document references sections of Volume 1: OGC CDB Core Standard: Model and Physical Database Structure [OGC 15-113]. - - Volume 11: OGC CDB Core Standard Conceptual Model - 16-007r3 - - + - + Jeff Yutzler + The GeoPackage Standards Working Group (SWG) presents a vision for storing tiled gridded elevation data in a GeoPackage. + + Envisioning a Tiled Elevation Extension for the OGC GeoPackage Encoding Standard + + + Envisioning a Tiled Elevation Extension for the OGC GeoPackage Encoding Standard + 15-039 + 15-039 - 2017-02-23 - 16-007r3 + + 2015-08-19 - - DGIWG - Web Map Service 1.3 Profile - Revision - 09-102r3a + + 23-050 + OGC Testbed-19 Agile Reference Architecture Engineering Report + + + + The concepts of agile architecture and reference architecture may not be new ideas in information or geospatial technologies, but what is meant by the term Agile Reference Architecture? + +Agile Reference Architecture is the long-term vision of the complex and changing nature of how problems will be solved in the future within the location-referenced and geospatial realms. This includes consideration of network availability, as containers integrated with Linked Data, and Application Programming Interfaces (APIs) serve data as secure, trusted, and self-describing resources. + +While the Open Geospatial Consortium (OGC) focuses on geospatial information and technologies, that community is also dependent on the overall state of information and communications technology (ICT), including developing cyber, cryptographic, and internet technologies. + +In today’s infrastructures, the collection, exchange, and continuous processing of geospatial resources typically happens at pre-defined network endpoints of a spatial data infrastructure. Each participating operator hosts some capability at a network endpoint. Whereas some network operator endpoints may provide data access, other endpoints provide processing functionality and other endpoints may support the uploading of capabilities. In other words, such an infrastructure is not agile in the sense that it cannot adapt by itself to meet the needs of the moment. One of the biggest challenges resulting from the static characteristics is ensuring effective and efficient operations of the overall system and at the same time maintaining trust and provenance. + +This OGC Testbed 19 Engineering Report (ER) outlines novel concepts for establishing a federated agile infrastructure of collaborative trusted systems (FACTS) that is capable of acting autonomously to ensure fit-for-purpose cooperation across the entire system. One of the key objectives is to not create a new data product, but instead a collaborative object is offered leveraging FACTS that allows for obtaining the data product via well-defined interfaces and functions provided by the collaborative object. + +Trust and assurance are two key aspects when operating a network of collaborative objects leveraging STANAG 4774/4778. STANAG 4774 outlines the metadata syntax required for a confidentiality label to better facilitate and protect sensitive information sharing. In addition, STANAG 4778 defines how a confidentiality label is bound to the data throughout its lifecycle and between the sharing parties.The agile aspect is achieved by the object’s ability to activate, deactivate, and order well-defined capabilities from other objects. These capabilities are encapsulated in building blocks. Each building block is well defined in terms of accessibility, functionality, and ordering options. This allows building blocks to roam around collaborative objects as needed to ensure a well-balanced network load and suitable processing power of individual nodes from the network. + +Equally trusted partners in the infrastructure participate in FACTS. They can collect data from other partners and create derived products via collaborative objects. The sharing of data products is only possible directly, meaning direct communication with data consumer and it is only possible via the objects. This guarantees that fundamental trust operations are applied to the data and provenance records are produced before the data product is made available to others. The use of Blockchain technology and Smart contracts is one example of how this fundamental behavior can be planted into collaborative objects. As in trusted networks that are using Evaluation Assurance Level (EAL) approved hardware and software components, the objects will have to undergo a similar assurance process. + +For ensuring the acceptance and interoperability of an agile reference architecture, built on top of FACTS with collaborative objects and building blocks, standardization is a key aspect. In particular, the core (fundamental) requirements for FACTS as well as the interfaces and capabilities of the collaborative objects and pluggable building blocks should be standardized. The OGC provides a consensus based collaborative standardization environment fits these requirements very well. - Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey - 09-102r3a - + OGC Testbed-19 Agile Reference Architecture Engineering Report - - - This document defines specific DGIWG requirements, -recommendations and guidelines for implementations of the -ISO and OGC Web Map Service standards; ISO 19128:2005 -Web Map Server Interface and the OpenGIS Web Map Server -Implementation Specification 1.3.0. - - DGIWG - Web Map Service 1.3 Profile - Revision - 2016-01-29 - - - This document defines a Gazetteer Service profile of the OGC Web Feature Service Standard. The OGC Gazetteer Service allows a client to search and retrieve elements of a georeferenced vocabulary of well-known place-names. -This profile extends the WFS interface in a way that a client is able to -– Determine if a WFS implementation is acting as a Gazetteer Service. -– Query the Gazetteer Service in order to retrieve place-name features without closer examination of the feature type definitions -– Access metadata about the gazetteer(s) provided by the service -– Update place-name features using WFS transactions -– Fetch place-name features that have Parent-Child relationships and then follow those links - - Web Feature Service (WFS-G). Services compliant with this standard shall provide Location Instances derived from SI_LocationInstance. In Addition, they may support queries based on the (parent/child) relationships of feature instances, as defined in ISO 19112. - Gazetteer Service - Application Profile of the Web Feature Service Candidate Implementation Standard - Gazetteer Service - Application Profile of the Web Feature Service Best Practice - 11-122r1 - - 11-122r1 - Gazetteer Service - Application Profile of the Web Feature Service Candidate Implementation Standard - Gazetteer Service - Application Profile of the Web Feature Service Best Practice - 2012-02-17 - 2011-11-30 + Lucio Colaiacomo + 23-050 + 2024-04-26 + + + 2014-04-15 + OGC® OWS-7 Schema Automation Engineering Report + OWS-7 Schema Automation Engineering Report + 10-088r3 + + 10-088r3 + + Clemens Portele + + The capabilities of OGC’s KML 2.2 as a format for exchange and visualization of U.S. National System for Geospatial Intelligence (NSG) Application Schema (NAS) data is explored. - Panagiotis (Peter) A. Vretanos, Jeff Harrison - Jeff Harrison, Panagiotis (Peter) A. Vretanos - - - - - + + - - WS-Agreement Application Profile for OGC Web Services - Bastian Baranski - + + ISO19115/ISO19119 Application Profile for CSW 2.0 + 2004-10-05 + ISO19115/ISO19119 Application Profile for CSW 2.0 + 04-038r1 + This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS + 04-038r1 + + + - 11-094 - WS-Agreement Application Profile for OGC Web Services + + Uwe Voges, Kristian Senkler + + + + + 3D-Symbology Encoding Discussion Draft - 2011-11-24 - - 11-094 - This document specifies a) XML schemas for providing functional and non-functional service descriptions of OGC Web Services (OWS), b) an URN namespace for identifying exposed and measurable service properties of OWS and c) a DSL for defining and evaluating service level guarantees. + 3D-Symbology Encoding Discussion Draft + 09-042 + Steffen Neubauer, Alexander Zipf + 2009-10-13 + 09-042 + This document present an extension of the Symbology Encoding (SE) /Styled Layer Descriptor (SLD) specifications into 3D as a separate profile. + + - - GML 3.1.1 common CRSs profile Corrigendum - 06-113 - 2006-07-19 - Arliss Whiteside - + + OGC Moving Features Encoding Extension - JSON + 2020-05-21 - - This document is a corrigendum for OGC Document 05-095r1, titled GML 3.1.1 common CRSs profile. This corrigendum is based on change request OGC 06-041. - GML 3.1.1 common CRSs profile Corrigendum - - 06-113 - + + Kyoung-Sook KIM, Nobuhiro ISHIMARU + + + + This standard defines how to encode and share the various movements of geographic features by using JavaScript Object Notation (JSON). It provides an alternative encoding for OGC Moving Features instead of that provided in the XML Core [OGC 14-083r2] and Simple CSV [OGC 14-084r2] standards. A moving feature, for instance a vehicle or a pedestrian, contains a temporal geometry whose location continuously changes over time and dynamic non-spatial attributes whose values vary with time. This Moving Features JSON encoding defines a set of keywords to implement the conceptual schema of moving features defined in ISO 19141:2008 [ISO 19141:2008], accompanied with IETF GeoJSON Format [IETF RFC 7946]. + Moving Features Encoding Extension - JSON + 19-045r3 + 19-045r3 - - + + 12-155 + OWS-9 OWS Innovations WCS for LIDAR Engineering Report + + 12-155 + This Engineering Report is prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiatitive of the Innovations Coverages Sub-Thread. This document represents the OWS-9 OWS Innovations WCS for LIDAR Engineering Report. In this report, the implementation of WCS 2.0 service that serves the LIDAR data in NITF format is introduced. This service supports the JPEG 2000 output format along with GMLJP2 metadata description as well as the JPIP protocol to deliver the output JPEG2000 data. + + OGC® OWS-9 OWS Innovations WCS for LIDAR Engineering Report + + + + Weiguo Han, Yuanzheng Shao, Liping Di + + 2013-06-18 - - This document is a proof of concept of a draft specification of the OGC Styles Application Programming Interface (API) that defines a Web API that enables map servers and clients as well as visual style editors to manage and fetch styles. - -Web APIs are software interfaces that use an architectural style that is founded on the technologies of the Web. Styles consist of symbolizing instructions that are applied by a rendering engine on features and/or coverages. - -The Styles API supports several types of consumers, mainly: - -Visual style editors that create, update and delete styles for datasets that are shared by other Web APIs implementing the OGC API - Features - Part 1: Core standard or the draft OGC API - Coverages or draft OGC API - Tiles specifications; - -Web APIs implementing the draft OGC API - Maps specification fetch styles and render spatial data (features or coverages) on the server; - -Map clients that fetch styles and render spatial data (features or coverages) on the client. - -Feature data is either accessed directly or organized into spatial partitions such as a tiled data store (aka vector tiles). - -The Styles API is consistent with the emerging OGC API family of standards. - -The Styles API implements the conceptual model for style encodings and style metadata as documented in chapter 6 of the OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report. - -The model defines three main concepts: - -The style is the main resource. - -Each style is available in one or more stylesheets - the representation of a style in an encoding like OGC SLD 1.0 or Mapbox Style. Clients will use the stylesheet of a style that fits best based on the capabilities of available tools and their preferences. - -For each style there is style metadata available, with general descriptive information about the style, structural information (e.g., layers and attributes), and so forth to allow users to discover and select existing styles for their data. - OGC Testbed-15: Styles API Engineering Report - 19-010r2 - 19-010r2 - OGC Testbed-15: Styles API Engineering Report + + This document provides guidance on GML MIME type specification. An Internet media type, originally called a MIME type after Multipurpose Internet Mail Extensions and sometimes a Content-type after the name of a header in several protocols whose value is such a type, is a two-part identifier for file formats on the Internet. The identifiers were originally defined in RFC 2046 for use in e-mail sent through SMTP, but their use has expanded to other protocols such as HTTP, RTP and SIP. + 2010-02-08 + + Technical Committee Policies and Procedures: MIME Media Types for GML + + MIME Media Types for GML + 09-144r2 + + + Clemens Portele + 09-144r2 - + + + Joan Masó, Jérôme Jacovella-St-Louis + + OGC Two Dimensional Tile Matrix Set and Tile Set Metadata + 2022-09-09 - - - 2019-12-12 - Clemens Portele + + The OGC Two Dimensional Tile Matrix Set and Tile Set Metadata Standard defines the rules and requirements for a tile matrix set as a way to index space based on a set of regular grids defining a domain (tile matrix) for a limited list of scales in a Coordinate Reference System (CRS) as defined in OGC 18-005r5 Abstract Specification Topic 2: Referencing by Coordinates. This content was initially included in the OGC 07-057r7 OpenGIS Web Map Tile Service Implementation Standard (WMTS) and was separated out into the OGC 17-083r2 OGC Two Dimensional Tile Matrix Set Standard version 1.0, to support reusability in other data formats of services that need a tiling scheme. This document is a revision of the OGC 17-083r2 document and the general tile matrix set concept is inherited from it with small additions. In a tile matrix set, each tile matrix is divided into regular tiles. In a tile matrix set, a tile can be univocally identified by a tile column, a tile row, and a tile matrix identifier. The OGC Two Dimensional Tile Matrix Set and Tile Set Metadata Standard describes a data structure defining the properties of the tile matrix set in both Unified Modeling Language (UML) diagrams and in tabular form. This document also defines a new data structure, called tile set metadata, that can be used to describe a particular set of tiles following a tile matrix set. Extensible Markup Language (XML) and JavaScript Object Notation (JSON) encodings are described both for tile matrix sets and tile matrix set metadata. It includes tile matrix set limits, links to the tile matrix set, details of the original data represented by the tile set and a nice point of origin to start exploring the tile set. Finally, the document offers practical examples of tile matrix sets both for common global projections and for specific regions. + 17-083r4 + 17-083r4 + OGC Two Dimensional Tile Matrix Set and Tile Set Metadata + + + - - Kyoung-Sook KIM, Hirotaka OGAWA + - 16-140r1 - - This document proposes a JavaScript Object Notation (JSON) encoding representation of movement of geographic features as an encoding extension of OGC Moving Features ([OGC 14-083r2] and [OGC 14-084r2]). A moving feature, typically a vehicle and pedestrian, can be expressed as a temporal geometry whose location continuously changes over time and contains dynamic non-spatial attributes whose values vary with time. This Best Practice describes how to share moving feature data based on JSON and GeoJSON (a JSON format for encoding geographic data structures). In addition, this document provides an example of RESTful approaches as a Feature Service Interface that has the potential for simplicity, scalability, and resilience with respect to exchange of moving feature data across the Web. + 07-014r3 + + 2007-08-10 + + Sensor Planning Service Implementation Specification + 07-014r3 + OpenGIS Sensor Planning Service Implementation Specification - 16-140r1 - OGC Moving Features Encoding Extension - JSON - OGC Moving Features Encoding Extension - JSON - - - 2017-06-28 + The OpenGIS® Sensor Planning Service Interface Standard (SPS) defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor planning request; to submit such a request; to inquire about the status of such a request; to update or cancel such a request; and to request information about other OGC Web services that provide access to the data collected by the requested task. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. + + Ingo Simonis - - OGC Testbed-16: Data Access and Processing Engineering Report + + Louis Rose + 03-055r1 + + Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint + - Data Access and Processing Engineering Report - 20-016 + + Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint + 03-055r1 + *RETIRED* specifies the Engineering Viewpoint for the Critical Infrastructure Collaborative Environment (CICE). This open, distributed processing environment crosses organizational boundaries and includes a variety of components deployed within multiple communities. The CICE leverages OGC Web Services the publication of the availability of critical infrastructure services and data; the registration and categorization of published service and data providers; and the discovery and use of needed critical infrastructure services and data + + 2003-06-02 + + + + 16-114r2 + Martin Desruisseaux + 16-114r2 + Moving Features Encoding Extension: netCDF - This OGC Testbed-16 Engineering Report (ER) describes the work performed in the Data Access and Processing API (DAPA) thread. - -The primary goal of the DAPA thread is to develop methods and apparatus that simplify access to, processing of, and exchange of environmental and Earth Observation (EO) data from an end-user perspective. This ER presents: - -The use cases participants proposed to guide the development of the client and server components deployed during the testbed. - -An abstract description of a resource model that binds a specific function to specific data and also provides a means of expressing valid combinations of data and processes. - -A description of each DAPA endpoint developed and deployed during the testbed. - -A description of the client components that interact with the deployed DAPA endpoints. - -End-user (i.e. data scientist) feedback concerning the ease-of-use of the - - - Panagiotis (Peter) A. Vretanos - 20-016 + - - 2021-01-13 + OGC Moving Features Encoding Extension: netCDF + + + + 2018-04-15 + The netCDF Moving Features encoding extension is a summary of conventions that supports efficient exchange of simple moving features as binary files. This Discussion Paper is a complement to the Moving Features Encoding Part I: XML Core and an alternative to the Simple Comma Separated Values (CSV) extension. Compared to the CSV encoding, this netCDF encoding offers more compact storage and better performance at the cost of additional restrictions on the kinds of features that can be stored. - - 2017-06-16 - This OGC Testbed 12 Engineering Report discusses the topic of vector tiling. - -While tiling and the use of multiple levels of details are a proven technique for raster data, it is relatively new for vector data. This is due to the increased complexity for tiling vector data compared to raster tiling. Further, there is a lack of standardization on the topic. Yet vector tiles can provide the same benefits as for raster tiles: - -Services can easily cache tiles and return them upon request, without the need for any additional pre/post processing (assuming no geometry construction is needed in the server). Consequently, clients can request and receive tiles quickly, ensuring better user experience. - -Due to tiled, multileveled data representations, clients can better access the data most suitable for their current map location and scale. This avoids the need to load too much data, which can cause both excessive memory usage and network traffic resulting in reduced overall performance. - -An example of vector tiling that illustrates the impact of these benefits is the OpenStreetMap (OSM) data store, which includes over 30 GB of data with worldwide coverage consisting of millions of vector features. Loading and visualizing all the OSM data into an application would either result in a memory shortage or unacceptable performance. By means of vector tiling and the generation of multiple levels of detail, apps using OSM data can load such data sets very efficiently into applications. - -This Engineering Report (ER) focuses on the general aspects of vector tiling. One of the main goals is to characterize what vector tiling is and how it can be approached. Highlighted topics include tiling approaches and strategies, tiling schemes, data coherence, simplification, scalability and styling. With respect to tiling schemes, existing standards material related to raster tiling schemes is incorporated to align both topics and to maximize interoperability. This includes the Defence Geospatial Information Working Group (DGIWG) Web Map Tiling Standard (WMTS) profile and the National System for Geospatial-Intelligence (NSG) WMTS profile as defined by the U.S. National Geospatial-Intelligence Agency (NGA). - -The topic of implementing vector tiles using a tile encoding / storage format is not covered. A study of implementing vector tiles in OGC GeoPackage is part of a separate Engineering Report, OGC 16-067, that builds on the results of this ER. + + 06-049r1 + GML 3.1.1 simple features profile + The OpenGIS® GML 3.1.1 Simple Features Profile (GML for Simple Features) is a restricted subset of GML (Geography Markup Language)[http://www.opengeospatial.org/standards/gml] and XML Schema [www.w3.org/XML/Schema] that supports the XML encoding of geographic features with simple geometric property types (Points, Line and Polygons). The profile defines three conformance classes that define three different levels of complexity. +See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml . - Testbed-12 Vector Tiling Engineering Report - 16-068r4 - Testbed-12 Vector Tiling Engineering Report + + 2006-05-08 + Peter Vretanos + + GML 3.1.1 simple features profile + 06-049r1 + + + + + + + + 2017-05-12 + Testbed-12 GeoPackage Routing and Symbology Engineering Report + 16-029r1 + 16-029r1 - - Daniel Balog, Robin Houtmeyers - 16-068r4 - + - + Jeff Yutzler + Testbed-12 GeoPackage Routing and Symbology Engineering Report + This OGC Engineering Report (ER) describes the results of experiments in OGC Testbed 12 designed to potentially enhance capabilities for symbology and routing [1] as extensions to the OGC GeoPackage standard. These experiments focused on 1.) methods for providing mounted and/or dismounted (off-road) routing within GeoPackage and 2.) mechanisms for providing user-defined map symbology for features in a GeoPackage structured data store. This ER documents the different approaches considered, design decisions and rationales, limitations, and issues encountered during prototype implementation. + + + - - Name Type Specification - Sensor Models and Parameters - 18-042r4 - - OGC Name Type Specification - Sensor Models and Parameters - Gobe Hobona, Simon Cox - - - - 2019-10-31 - 18-042r4 + + + + Web Map Context Documents + 02-066r1 - This document specifies a rule for constructing OGC names that may be used for identifying definitions of sensor models and their parameters. This document is formally a profile of the OGC policy 'OGC-NA Name type specification - definitions: Part 1 - basic name' (OGC 09-048r5). + + Jean-Philippe Humblet + 02-066r1 + 2002-08-29 + Web Map Context Documents + States how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent manner. + - - - - - - - - - Carl Reed - - + + + OGC SensorThings API Extension: STAplus 1.0 - - 20-050 - Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension). - 20-050 - - 2021-02-26 - This optional OGC CDB extension defines the requirements and provides CDB specific guidance on using GeoPackage containers in a CDB data store. There is a companion CDB Best Practice document that provide rules and guidance for transforming CDB structured Shapefiles into CDB structure GeoPackages that are compliant with the requirements and conformance classes as defined in this document. - Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension). - - - The geospatial community has had an on-going challenge with being able to share data and compute resources in dynamic, collaborative environments that span different administrative domains. For these types of requirements, the concept of federation has been developed. The near-term goal of the Federated Cloud task in Testbed-14 is to demonstrate a specific data-sharing scenario among two or more administrative domains using existing security tooling, e.g., OpenID Connect and OAuth. The main details of this work are reported as part of the Security Engineering Report (ER) [1]. This Federated Cloud ER will dovetail with the Security ER to: + + The OGC SensorThings API Extension: STAplus 1.0 Standard specifies a backwards-compatible extension to the OGC Standard SensorThings API Part 1: Sensing and Sensing 1.1 data model. -Coordinate across all federation-related tasks in Testbed-14, including the Earth Observation Cloud and Workflow tasks, +The motivation for specifying this STAplus extension is based on requirements from the Citizen Science community. -Understand the overall federation design space, +The dominant use for the OGC SensorThings API data model and API can be coined with the use case “single authority provides sensor readings to consumers.” However, in Citizen Science there are many contributors (citizens) who – together – create the big picture with their observations. -Analyze and critique the scope, trade-offs and limitations of the federation capabilities being built and demonstrated in Testbed-14, +The STAplus extension is designed to support a model in which observations are owned by different users. This results in requirements for the ownership concept. In addition to the ownership, users may express a license for ensuring proper re-use of their observations. The STAplus extension also supports expressing explicit relations between observations as well as between observations and external resources. Relations can enrich observations to enable future extensions supporting Linked Data, RDF and SPARQL. Observation group(s) allow the grouping of observations that belong together. -Identify and prioritize possible incremental development tasks for subsequent testbeds, and +The STAplus extension is believed to be an important contribution towards the realization of the FAIR principles as STAplus strengthens the “I” (Interoperability) through a common data model and API as well as the “R” (Re-usability) by allowing expressing standards-based queries that may consider licensing conditions which is relevant for reuse of other users’ observations. -Liaison with groups external to OGC, such as the NIST/IEEE Joint WG on Federated Cloud, to promote the further development and adoption of federated capabilities, and ultimately international standards. - - 18-090r2 - Testbed-14: Federated Clouds Engineering Report - 2019-10-23 - - - - - - Craig A. Lee - 18-090r2 - OGC Testbed-14: Federated Clouds Engineering Report +The STAplus Data Model and Business Logic also enriches existing deployments as the extension can be seamlessly added and thereby offers new capabilities to create and manage the “big picture” with multi-user capabilities. + +The key work for crafting this OGC Standard was undertaken in the Co-designed Citizen Observatories Services for the EOS-Cloud (Cos4Cloud) project, which received funding from the European Union’s Horizon 2020 research and innovation program and the Enhancing Citizen Observatories for healthy, sustainable, resilient and inclusive cities (CitiObs) project, which received funding from the European Union’s Horizon Europe research and innovation program. Testing of this extension was done with data from the Framework biodiversity project, which received funding from the European Union’s Horizon 2020 research and innovation program. + OGC SensorThings API Extension: STAplus 1.0 + 22-022r1 + + + 22-022r1 + 2023-09-23 + Andreas Matheus - - - + + Mark Burgoyne, Dave Blodgett, Chuck Heazel, Chris Little - Geospatial eXtensible Access Control Markup Language (GeoXACML) - - - - The OpenGIS® Geospatial eXtensible Access Control Markup Language Encoding Standard (GeoXACML) defines a geospatial extension to the OASIS standard “eXtensible Access Control Markup Language (XACML)” [www.oasis-open.org/committees/xacml/]. This extension incorporates spatial data types and spatial authorization decision functions based on the OGC Simple Features[http://www.opengeospatial.org/standards/sfa] and GML[http://www.opengeospatial.org/standards/gml] standards. GeoXACML is a policy language that supports the declaration and enforcement of access rights across jurisdictions and can be used to implement interoperable access control systems for geospatial applications such as Spatial Data Infrastructures. GeoXACML is not designed to be a rights expression language and is therefore not an extension of the OGC GeoDRM Reference Model (Topic 18 in the OpenGIS® Abstract Specification [http://www.opengeospatial.org/standards/as]). - Geospatial eXtensible Access Control Markup Language (GeoXACML) - 07-026r2 - Andreas Matheus, Jan Herrmann - 2008-02-23 - 07-026r2 - - - A Primer for Dissemination Services for Wide Area Motion Imagery - 2012-12-05 - 12-077r1 - A Primer for Dissemination Services for Wide Area Motion Imagery - + 19-086r4 + OGC API - Environmental Data Retrieval Standard - The reason for developing this specification was a WAMI community requirement to deliver high performance web services and disseminate WAMI products. While existing web services can be combined or modified to deliver some of the functionality of the services described in this document, by design, they cannot deliver the desired performance. - - 12-077r1 + OGC API - Environmental Data Retrieval Standard - - Rahul Thakkar - + 2021-08-13 + + + 19-086r4 + + The Environmental Data Retrieval (EDR) Application Programming Interface (API) provides a family of lightweight query interfaces to access spatio-temporal data resources by requesting data at a Position, within an Area, along a Trajectory or through a Corridor. A spatio-temporal data resource is a collection of spatio-temporal data that can be sampled using the EDR query pattern geometries. These patterns are described in the section describing the Core Requirements Class. + +The goals of the EDR API are to make it easier to access a wide range of data through a uniform, well-defined simple Web interface, and to achieve data reduction to just the data needed by the user or client while hiding much of the data storage complexity. A major use case for the EDR API is to retrieve small subsets from large collections of environmental data, such as weather forecasts, though many other types of data can be accessed. The important aspect is that the data can be unambiguously specified by spatio-temporal coordinates. + +The EDR API query patterns, such as Position, Area, Cube, Trajectory or Corridor, can be thought of as discrete sampling geometries, conceptually consistent with the feature of interest in the Sensor Observation Service (SOS) standard. A typical EDR data resource is a multidimensional dataset that could be accessed via an implementation of the Web Coverage Service (WCS) standard. In contrast to SOS and WCS, EDR implements the technical baseline of the OGC API family of standards and aims to provide a single set of simple-to-use query patterns. Use cases for EDR range from real or virtual time-series observation retrievals, to sub-setting 4-dimensional data cubes along user-supplied sampling geometries. These query patterns do not attempt to satisfy the full scope of either SOS or WCS, but provide useful building blocks to allow the composition of APIs that satisfy a wide range of geospatial data use cases. By defining a small set of query patterns (and no requirement to implement all of them), the EDR API should help to simplify the design of systems (as they can be performance tuned for the supported queries) making it easier to build robust and scalable infrastructure. + +With the OGC API family of standards, the OGC community has extended its suite of standards to include Resource Oriented Architectures and Web Application Programming Interfaces (APIs). These standards are based on a shared foundation, specified in OGC API-Common, which defines the resources and access paths that are supported by all OGC APIs. The resources are listed in Table 1. This document extends that foundation to define the Environmental Data Retrieval API. - - Ingo Simonis, Andreas Wytzisk - Web Notification Service + + This Topic Volume will provide essential and abstract models for technology that is already used widely (but not interoperably) across the GIS landscape. This technology properly depends on the more general technology that supports Coverages. + 99-107 + Topic 07 - Earth Imagery + 99-107 + Topic 7 - Earth Imagery + Cliff Kottman - - 2003-04-21 - - - - Web Notification Service - 03-008r2 - 03-008r2 - The Web Notification Service (WNS) is the first asynchronous messaging service specified by OGC. At the moment, the WNS message schema is optimized to fulfil the needs of services supporting the use of sensors, like Sensor Planning Service. Future work activities should include the adaptation of the message schema to the needs of other services. - - - - 01-009a - Martin Daly - Coordinate Transformation Services - OLE/COM + + 1999-03-31 - - Provides interfaces for general positioning, coordinate systems, and coordinate transformations. - - Coordinate Transformation Services - OLE/COM - 01-009a - - 2001-01-12 - - - - - This document comprises experiences and recommendations when using -Sensor Web Enablement (SWE) concepts. This document focuses on -one basic issue: the provision of observations in an OGC SOS. -This includes the definition of a lightweight OGC SOS profile (OGC 11- -169r1), an analysis of and contribution to the specification of the Sensor -Observation Service (SOS) 2.0 as well as an approach how the data -used within Earth observation (EO) applications can be integrated more -easily into SOS instances. -These recommendations result from the work performed in 2010-2013 -as part of the research project EO2HEAVEN (Earth Observation and -Environmental Modelling for the Mitigation of Health Risks), co-funded -by the European Commission as part of the 7th Framework Programme -(FP7) Environmental theme. EO2HEAVEN contributes to a better understanding -of the complex relationships between environmental changes -and their impact on human health. See http://www.eo2heaven.org/ . -The lightweight OGC SOS profile has been developed in close cooperation -between the FP7 projects EO2HEAVEN and UncertWeb (see -http://www.uncertweb.org/ ). - 13-015 - Provision of Observations through an OGC Sensor Observation Service (SOS) + - - 2014-02-25 - - 13-015 - - - EO2HEAVEN Consortium - - OGC Best Practice for Sensor Web Enablement: Provision of Observations through an OGC Sensor Observation Service (SOS) + - - Web Coordinate Transformation Service - Andreas Poth, Markus Muller - - Web Coordinate Transformation Service - 02-061r1 - - This document specifies the transformations of geo-spatial coordinates from one Coordinate Reference System (CRS) into another by means of a Web Service - - 02-061r1 - - 2002-09-15 + + + + + + + + + + + + + + + + + + + + + + + Documents of type Best Practice - deprecated - + + Documents of type Best Practice - deprecated + Documents of type Best Practice - deprecated - + + 09-048r5 + OGC Name Type Specification - definitions - part 1 – basic name + Simon Cox, Gobe Hobona + 2019-10-31 + + + Name Type Specification - definitions - part 1 – basic name + 09-048r5 + + - The OpenGIS® Catalogue Service Interface Standard 2.0.1 - FGDC CSDGM Application Profile for CSW 2.0 explains how Catalogue Services based on the FGDC Content Standard for Digital Geospatial Metadata (CSDGM) [http://www.fgdc.gov/standards/projects/FGDC-standards-projects/metadata/base-metadata/index_html] Application Profile for the OpenGIS® Catalogue Service Interface Standard v2.0.1 [http://www.opengeospatial.org/standards/cs] are organized and implemented for the discovery, retrieval and management of data metadata. - FGDC CSDGM Application Profile for CSW 2.0 - FGDC CSDGM Application Profile for CSW 2.0 - 06-129r1 - - - - Patrick Neal, John Davidson, Bruce Westcott - - 2006-12-26 - 06-129r1 + This document specifies a rule for constructing OGC names that may be used for identifying definitions. - - This approved OGC Implementation Standard defines a Simple Features profile of the Geography Markup Language version 3.2. This Simple Features Profile has been aligned with the OGC Simple Features standard for SQL version 1.2. Simple Features include: Point, Curve (LineString), Surface (Polygon), Geometry, MultiPoint, MultiCurve, MultiSurface, and MultiGeometry. The detailed abstract model for OGC features and geometry can be found in the OGC Abstract Specification, Topic Volume 1: Features (which is equivalent to ISO 19107). - -This Simple Features profile of GML began as a product of OGC’s Interoperability Program: a global, collaborative, hands-on engineering and testing program designed to deliver prototype technologies and proven candidate standards into the OGC’s Specification Development Program. In OGC Interoperability Initiatives, international teams of technology providers work together to solve specific geo-processing interoperability problems posed by Initiative. - - 10-100r3 - - - 10-100r3 - Geography Markup Language (GML) simple features profile (with Corrigendum) - - Geography Markup Language (GML) simple features profile (with Corrigendum) - + + Documents of type Specification Application Profile - Approved + + + + + Documents of type Specification Application Profile - Approved + - - 2011-05-11 - Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos + Documents of type Specification Application Profile - Approved - - Jeff Yutzler - 2017-08-25 - 12-128r14 - GeoPackage Encoding Standard - 12-128r14 - OGC® GeoPackage Encoding Standard - - - - This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. - - + + Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension). + 20-050 + Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension). + - - - OWS-5 Earth Observation Web Processing Services (WPS) Engineering Report - 08-058r1 - OWS-5 Earth Observation Web Processing Services (WPS) Engineering Report - - - 08-058r1 - - This document serves to describe the use of web processing services and the OGC Web Processing Service (WPS) in earth observation (EO) applications. It provides an overview of web processing services and a description of developments related to earth observation implementations of OGC WPS in the OGC OWS-5 testbed. - 2008-09-12 - - Stefan Falke - + + 2021-02-26 + + + 20-050 + Carl Reed + This optional OGC CDB extension defines the requirements and provides CDB specific guidance on using GeoPackage containers in a CDB data store. There is a companion CDB Best Practice document that provide rules and guidance for transforming CDB structured Shapefiles into CDB structure GeoPackages that are compliant with the requirements and conformance classes as defined in this document. - - 05-089r1 + - 2005-12-01 - 05-089r1 - Sensor Planning Service - - Sensor Planning Service - - - The Sensor Planning Service (SPS) is intended to provide a standard interface to collection assets (i.e., sensors, and other information gathering assets) and to the support systems that surround them. -The SPS is designed to be flexible enough to handle a wide variety of configurations. - Ingo Simonis + Binary-XML Encoding Specification + 03-002r8 - - - 2021-11-16 - 12-128r18 - GeoPackage Encoding Standard - Jeff Yutzler - OGC® GeoPackage Encoding Standard - - This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. - + Craig Bruce - - 12-128r18 - - + 2003-05-07 + + 03-002r8 + This document specifies a binary encoding format for the efficient representation of XML data, especially scientific data that is characterized by arrays of numbers. This encoding format is applicable to any application that uses XML format. + Binary-XML Encoding Specification + - - - + + OGC Standards and Cloud Computing + OGC Standards and Cloud Computing + 11-036 - 2007-01-18 - - Dr. Markus Mueller + + + Lance McKee, Carl Reed, Steven Ramage - OpenGIS Symbology Encoding Implementation Specification - The OpenGIS® Symbology Encoding Standard (SES) defines an XML language for styling information that can be applied to digital geographic feature and coverage data. SE is independent of any OGC Web Services descriptions and could therefore be used to describe styling information in non-networked systems such as desktop geographic information systems. - Symbology Encoding Implementation Specification - 05-077r4 - - 05-077r4 + 2011-04-07 + + 11-036 + This OGC White Paper discusses cloud computing from the perspective of OGC’s +geospatial standards development activities and standards baseline. The paper begins +with a discussion of what the cloud and cloud computing are. Unfortunately, there is still +considerable misunderstanding in the geospatial technology community regarding cloud +computing. The paper then discusses how standards figure into the options, benefits and +risks of cloud computing for users and providers of geospatial data and software. This +perspective is important not only for those immersed in geospatial technology, but also for +cloud service providers, customers and technology partners who may be unfamiliar with +the basic issues surrounding geospatial technology. This white paper does not discuss +vendor specific cloud computing platforms. + - - OGC® GeoPackage Encoding Standard - With Corrigendum + + OGC Earth Observation Applications Pilot: Summary Engineering Report + 20-073 + Ingo Simonis - - This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a “native” storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. + OGC Earth Observation Applications Pilot: Summary Engineering Report + 20-073 - 12-128r12a - GeoPackage Encoding Standard - With Corrigendum - - 12-128r12a - - Paul Daisey - 2015-04-20 + This Engineering Report (ER) summarizes the main achievements of the OGC Innovation Program initiative Earth Observation Applications Pilot, conducted between December 2019 and July 2020. + + + 2020-10-26 + - + + + The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community (IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0 architecture through the development, implementations, test, and robust demonstration making use of IC specifications, Geography Markup Language (GML), and NIEM in a simulated “real-world” scenario. The demonstration scenario begins with NIEM-conformant Information Exchange Packages (IEPs) containing operational data and IC security tags from the Information Security Marking (ISM) and Need-To-Know (NTK) access control metadata, and the Trusted Data Format (TDF) for binding assertion metadata with data resource(s). Those instance documents are deployed on Open Geospatial Consortium (OGC) Web Services to be used by client applications. Access control is based on attributes of the end-user and the instance data. +The assessment included reviewing example IEPDs and performing test and demonstrations using OGC web services, such as Transactional Web Feature Services (WFS-T), Policy Enforcement Points (PEPs) and OGC Attribute Stores to process geographic feature with NIEM components and security tags. The Test and Demonstration included, but was not limited to feature retrieval and transactions. Recommendations to update these information exchanges were provided to reflect NIEM 3.0 architecture and security tags in a ‘NIEM/IC Feature Processing API’. Results from this task helped provide a preliminary architecture for Geo4NIEM in Testbed 11, summarized in other OGC Testbed 11 Engineering Reports. +This task also identified potential change requests to OGC WFS or other OGC Services for handling security information in a federated role-based access control environment. These changes may help the NIEM/IC transform into more agile and customer-centric frameworks driven by collaborative partnerships. This transformation is vital to confronting the security challenges of the future. + + + Testbed-11 NIEM-IC Feature Processing API using OGC Web Services - Chuck Morris - - Compliance Test Language (CTL) Best Practice - 06-126r2 - 06-126r2 - Compliance Test Language (CTL) Best Practice - - This document establishes Compliance Test Language, an XML grammar for documenting and scripting suites of tests for verifying that an implementation of a specification complies with the specification. - 2009-07-21 - - + Jeff Harrison + 15-047r3 + Testbed-11 NIEM-IC Feature Processing API using OGC Web Services + + 15-047r3 + + 2016-01-25 - - - 03-026 - - + + 2007-07-02 + *THIS STANDARD HAS BEEN RETIRED* + +The OpenGIS® Transducer Markup Language Encoding Standard (TML) is an application and presentation layer communication protocol for exchanging live streaming or archived data to (i.e. control data) and/or sensor data from any sensor system. A sensor system can be one or more sensors, receivers, actuators, transmitters, and processes. A TML client can be capable of handling any TML enabled sensor system without prior knowledge of that system. + +The protocol contains descriptions of both the sensor data and the sensor system itself. It is scalable, consistent, unambiguous, and usable with any sensor system incorporating any number sensors and actuators. It supports the precise spatial and temporal alignment of each data element. It also supports the registration, discovery and understanding of sensor systems and data, enabling users to ignore irrelevant data. It can adapt to highly dynamic and distributed environments in distributed net-centric operations. + +The sensor system descriptions use common models and metadata and they describe the physical and semantic relationships of components, thus enabling sensor fusion. + +This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. + + 06-010r6 + Transducer Markup Language + Steve Havens - Service Information Model - 03-026 - Service Information Model - 2003-01-17 - SIM specifies and discusses a common information model for OGC Web Services, also known variously or in part as service capabilities or service metadata. - Joshua Lieberman - - - - 21-066r1 + - This document provides the set of revision notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata [OGC 17-083r4] and does not modify that Standard. - - Release Notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata v.2.0 - - 21-066r1 - Release Notes for OGC Two Dimensional Tile Matrix Set and Tile Set Metadata v.2.0 - - 2022-09-09 - - - Joan Maso + OpenGIS Transducer Markup Language *RETIRED* + + 06-010r6 + - - 01-013r1 - High-Level Ground Coordinate Transformation Interface - - - + + + This document describes a conceptual model, logical model, and GML/XML encoding rules for the exchange of groundwater data. In addition, this document provides GML/XML encoding examples for guidance. - 01-013r1 - Arliss Whiteside + + 15-082 + GroundWaterML 2 – GW2IE FINAL REPORT + - 2001-02-27 - High-Level Ground Coordinate Transformation Interface - This document specifies a - + 2016-04-27 + Boyan Brodaric + + OGC GroundWaterML 2 – GW2IE FINAL REPORT + 15-082 - + + Samantha Lavender, Trent Tinker + + Testbed-19: Machine Learning Models Engineering Report + 23-033 + + + The OGC Testbed 19 initiative explored six tasks including this task focused on Machine Learning: Transfer Learning for Geospatial Applications. + +This OGC Testbed 19 Engineering Report (ER) documents work to develop the foundation for future standardization of Machine Learning models for transfer learning within geospatial, especially Earth Observation, applications. The ER reviews the findings of transfer learning experiments and makes recommendations about the next steps in terms of both the experiments conducted and broader implications for OGC. + 23-033 - - 23-056 - Mobility Data Science Discussion Paper - 2024-01-29 - - - 23-056 - Song WU, Mahmoud SAKR - Almost every activity in our modern life leaves a digital trace, typically including location and time. Either captured by a sensor, manually input, or extracted from a social media post, the increase in the volume, variety, and velocity of spatiotemporal data is unprecedented. The ability to manage and analyze this data is important for many application domains, including smart cities, health, transportation, agriculture, sports, biodiversity, et cetera. It is critical to not only effectively manage and analyze the data but also to uphold privacy and ethical considerations. Since the civilian use of GPS was allowed in 1980, followed by the technological advances in other location tracking systems – wifi, RFID, bluetooth, etc., it is becoming more and more easy to track moving objects. The Mobility Data Science Summit was an opportunity to discuss the challenges of managing this data and making sense of it, with a focus on the tooling and standardization requirements. - Mobility Data Science Discussion Paper + 2024-04-26 + Testbed-19: Machine Learning Models Engineering Report - - - This Engineering Report (ER) enhances the understanding of the concept of application profiles (AP) for ontologies based on the Web Ontology Language (OWL) and used by Linked Data (LD) applications. The concept of an Application Profile for Unified Modeling Language (UML) and Extensible Markup Language (XML) schemas, in particular Geographic Markup Language (GML) application profiles, is pretty well-defined and understood within the communities of Open Geospatial Consortium (OGC) and International Organization for Standardization (ISO). Moreover, in the context of Linked Data and ontologies, the term is still ill-defined, as ontologies are defined using an Open World Assumption (OWA), as well as classes and properties are first-class modeling objects in ontology modeling. The work documented in this report includes: - -Definition and characterization of Resource Description Framework (RDF) application profiles for simple linked data applications and complex analytic linked data applications. - -Determination of preliminary techniques for the development of subsets of ontologies to support different types of applications (simple linked data and complex analytic) - -An initial model for defining metadata about application profiles, so they can be searched and discovered by agents. - 18-094r1 - Characterization of RDF Application Profiles for Simple Linked Data Application and Complex Analytic Applications Engineering - 18-094r1 - 2019-02-04 - + + 16-115 + Future City Pilot 1 - Recommendations on Serving IFC via WFS - Stephane Fellah - OGC Testbed-14: Characterization of RDF Application Profiles for Simple Linked Data Application and Complex Analytic Applicat - + + Guy Schumann + 2017-10-20 + Future City Pilot 1 - Recommendations on Serving IFC via WFS + 16-115 + + + This Engineering Report (ER) gives recommendations on serving IFC via WFS and discusses related issues. It was decided that the focus of this ER is to summarize issues and give recommendations for future work and discuss the nature of such work. In other words, this ER should be viewed as an initial set of discussion points on the topic of serving IFC via WFS. - - - The OGC SensorThings API Extension: STAplus 1.0 Standard specifies a backwards-compatible extension to the OGC Standard SensorThings API Part 1: Sensing and Sensing 1.1 data model. - -The motivation for specifying this STAplus extension is based on requirements from the Citizen Science community. - -The dominant use for the OGC SensorThings API data model and API can be coined with the use case “single authority provides sensor readings to consumers.” However, in Citizen Science there are many contributors (citizens) who – together – create the big picture with their observations. - -The STAplus extension is designed to support a model in which observations are owned by different users. This results in requirements for the ownership concept. In addition to the ownership, users may express a license for ensuring proper re-use of their observations. The STAplus extension also supports expressing explicit relations between observations as well as between observations and external resources. Relations can enrich observations to enable future extensions supporting Linked Data, RDF and SPARQL. Observation group(s) allow the grouping of observations that belong together. + + This discussion paper is organized as follows. -The STAplus extension is believed to be an important contribution towards the realization of the FAIR principles as STAplus strengthens the “I” (Interoperability) through a common data model and API as well as the “R” (Re-usability) by allowing expressing standards-based queries that may consider licensing conditions which is relevant for reuse of other users’ observations. +Background: This section introduces DLT and blockchain, as well as the structure of blocks. -The STAplus Data Model and Business Logic also enriches existing deployments as the extension can be seamlessly added and thereby offers new capabilities to create and manage the “big picture” with multi-user capabilities. +Case Studies: This section presents an overview of example projects that use or are studying blockchain within a geospatial context. -The key work for crafting this OGC Standard was undertaken in the Co-designed Citizen Observatories Services for the EOS-Cloud (Cos4Cloud) project, which received funding from the European Union’s Horizon 2020 research and innovation program and the Enhancing Citizen Observatories for healthy, sustainable, resilient and inclusive cities (CitiObs) project, which received funding from the European Union’s Horizon Europe research and innovation program. Testing of this extension was done with data from the Framework biodiversity project, which received funding from the European Union’s Horizon 2020 research and innovation program. - - OGC SensorThings API Extension: STAplus 1.0 - 22-022r1 - 22-022r1 - 2023-09-23 - Andreas Matheus +Current Standardization Initiatives: This section presents an overview of a selection of standardization initiatives involving blockchain and geospatial data. + 18-041r1 + Geospatial Standardization of Distributed Ledger Technologies + 2018-10-09 + - OGC SensorThings API Extension: STAplus 1.0 - - + + 18-041r1 + + Geospatial Standardization of Distributed Ledger Technologies + Gobe Hobona, Bart De Lathouwer + - - 99-110 - Topic 10 - Feature Collections - - - - - 1999-04-07 - 99-110 + - - An OpenGIS Feature Collection is an abstract object consisting of Feature Instances, their Feature Schema, and Project Schema. - Cliff Kottman - Topic 10 - Feature Collections - - - Uses and summary of Topic 2 - Spatial referencing by coordinates - + WMS Part 2: XML for Requests using HTTP Post + 02-017r1 + WMS Part 2: XML for Requests using HTTP Post - This document first discusses the uses for data sharing, and then provides a brief summary, of OGC Abstract Specification Topic 2: Spatial referencing by coordinates. Topic 2 is almost the same as ISO 19111:2007, but includes some corrections. This document includes some best practices for using Coordinate Reference Systems (CRSs). - Uses and summary of Topic 02 - Spatial referencing by coordinates - 09-076r3 - Arliss Whiteside - + + 2002-08-24 + 02-017r1 + + This part of the Web Map Service (WMS) specification applies to those clients and servers which allow operation request encodings that are more complex than those permitted by the basic keyword/value encoding defined in WMS Part 1 [17]. Part 2 only describes the encoding of the request messages using Extensible Markup Language (XML); all other aspects of the Web Map Service are fully defined in Part 1. - - 2009-09-14 - - 09-076r3 + + Jeff de La Beaujardiere - - - - This specification describes a GML encoding for discrete coverages. The encoding pattern is a variation from the standard GML Coverage, in that the values in the domain and range are effectively interleaved rather than represented as two blocks and encoded sequentially. - 2007-05-17 - GML Encoding of Discrete Coverages (interleaved pattern) - 06-188r1 - Simon Cox - - GML Encoding of Discrete Coverages (interleaved pattern) - 06-188r1 + + OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report + 09-067r2 + This document described the Outdoor and Indoor 3D Routing and Services which are used in the OGC OWS-6 Decision Support Systems (DSS) thread. The objective is to enhance a network topology for the current CityGML specification based on the knowledge acquired through the development and experimental evaluation of this project. + + + 09-067r2 + 2009-10-09 + + Akiko Sato, Nobuhiro Ishimaru, Guo Tao, Masaaki Tanizaki + OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report - - Geospatial Business Intelligence (GeoBI) - 09-044r3 - - - 09-044r3 - - BI is an umbrella term for a major component of IT infrastructure. It encompasses Data -Warehouses, Business Analytics, Dashboards and Scorecards. This IT infrastructure is associated -with C-level decision-making in an organization. These decision-making tools have typically -included location as a dumb attribute (coded sales zones as opposed to sales zones as geographic -boundaries). At this point in the BI lifecycle, customers are looking to derive additional business -benefit / return on investment from intelligent location data; data discovery and unstructured data. + + OGC® OWS-9 - OWS Context evaluation IP Engineering Report + 2013-06-18 + OWS-9 - OWS Context evaluation IP Engineering Report + 12-105 + 12-105 + Joan Masó + + + - 2012-07-12 - Geospatial Business Intelligence (GeoBI) - George Percivall, Raj Singh - - - - - - - - Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values - 16-003r3 - This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids key words. - Carl Reed - 16-003r3 - 2018-12-19 - Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values - + This OGC Engineering Report describes the results of the OWS-9 IP on OWS Context 1.0. OWS Context is a draft OGC candidate standard. The OWS Context activity tested and evaluated the relative benefits of different encoding methods prior to finalization of the candidate standard. OWS Context has been proposed with an Atom encoding, a JSON encoding and an HTML5 encoding. The encoding requirement seeks to understand the level of mass-market acceptance of these different encoding options and their ability to support mash-ups. Each encoding should be evaluated, including examples and recommendations to move forward. Recommendations should enable the OWS Context capability for OGC services while remaining cognizant of implementations using mass-market technologies. - - 2007-11-14 - Arliss Whiteside + + 07-039r1 + KML 2.1 Reference - An OGC Best Practice + 07-039r1 + Carl Reed + + 2007-05-07 + + + + KML 2.1 Reference - An OGC Best Practice + KML is a file format used to display geographic data in an Earth browser, such as Google Earth, Google Maps, and Google Maps for Mobile. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard. - + + + + Geography Markup Language + 02-069 + 02-069 - Definition identifier URNs in OGC namespace - This Best Practices Paper specifies Universal Resource Names (URNs) in the ogc URN namespace to be used for identifying definitions. This document specifies the formats used by these URNs, plus a set of specific URNs for specific definitions. These definitions should be used wherever applicable by implementations of various OGC Implementation Specifications, including GML, WMS, WFS, and WCS. - Definition identifier URNs in OGC namespace - 07-092r1 - - 07-092r1 + Ron Lake + + + 2002-08-19 + + Geography Markup Language + The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features. - - 2001-01-26 - Louis Reich - Web Registry Server - 01-024r1 - - + + + + 17-002r1 - Web Registry Server - 01-024r1 - + + 2017-08-18 + 17-002r1 + GeoRSS Encoding Standard + + GeoRSS is designed as a lightweight, community driven way to extend existing RSS feeds with simple geographic information. The GeoRSS standard provides for encoding location in an interoperable manner so that applications can request, aggregate, share and map geographically tag feeds. + + OGC GeoRSS Encoding Standard + Carl Reed + + + 08-059r4 + Web Coverage Service WCS Interface Standard - Processing Extension + + Peter Baumann, Jinsongdi Yu + + - A Registry Service defines a common mechanism to classify, register, describe, search, maintain and access information about OGC Web resources. The OGC Service Registry provides the methods for managing a repository; a Registry Client is an application used to access the Registry. + 2014-02-26 + 08-059r4 + + The OGC Web Coverage Service (WCS)– Processing Extension defines an extension to the WCS Core [OGC 09-110], the ProcessCoverages request type, which allows clients to initi-ate server-side processing and filtering of coverages and to download the resulting coverage or value sets based on the query language defined in the Web Coverage Processing Service (WCPS) interface standard [OGC 08-068]. + OGC® Web Coverage Service WCS Interface Standard - Processing Extension - - - - - A filter is a construct used to describe constraints on properties of a feature class for the purpose of identifying a subset of feature instances to be operated upon in some way. + + + 2008-05-02 + Tom Kralidis + This document provides the details for a corrigendum for the existing OpenGIS Standard for the Web Map Context Documents version 1.1.0 and does not modify that standard. The current OpenGIS IS that this document provides revision notes for is 05-005. This document is a corrigendum to 05-005. + 08-050 + Web Map Context Documents Corrigendum 1 - - 02-059 - 02-059 - Filter Encoding - 2001-05-01 - Filter Encoding - Peter Vretanos - - - - This document examines five workflows discussed during the course of the OWS-4 project. - Workflow Descriptions and Lessons Learned - 06-187r1 - Steven Keens - - OWS-4 Workflow IPR + 08-050 - - - - 06-187r1 - 2007-05-07 + OpenGIS Web Map Context Documents Corrigendum 1 + + - - This CDB Volume provides Guidelines, Clarifications, Rationales, Primers, and additional information for the definition and use of various models that can be stored in a CDB compliant data store. -Please note that the term “lineal” has been replaced with the term “line” or “linear” throughout this document -Please note that the term “areal” has been replaced with the term “polygon” throughout this document. - - - + + + 2018-03-07 + OGC GeoPackage Extension for Tiled Gridded Coverage Data + - Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2 - 16-010r4 + 17-066r1 + GeoPackage Extension for Tiled Gridded Coverage Data + + 17-066r1 Carl Reed - 2018-12-19 - - - - 16-010r4 - Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2 + + The “GeoPackage Extension for Tiled Gridded Coverage Data” extension (previously titled Elevation Extension) defines how to encode and store tiled regular gridded data, such as a digital elevation model, in a GeoPackage. In the ISO 19123 Schema for Coverage Geometry standard and in the OGC Coverage Implementation Schema, this type of regular gridded data is classed as grid-regular[1]. The tiles contain values, such as elevation, temperature or pressure, and may be stored as 16-bit PNG files or 32-bit TIFF files. The extension defines two ancillary data tables: one for regular gridded coverages and one for tiles. When using the PNG encoding, a scale and offset may be applied. The extension also allows for a TIFF encoding but constrains many of the TIFF options that are available to simplify development. + - - - WAMI Services: Dissemination Services for Wide Area Motion Imagery - Best Practice - - WAMI Services: Dissemination Services for Wide Area Motion Imagery - Best Practice - 12-032r2 - This OGC Best Practice (BP) describes web interface specifications for the access and dissemination of Wide Area Motion Imagery (WAMI) products and metadata. This BP also describes a framework and interface specifications common to all WAMI services. A <a href=https://portal.ogc.org/files/?artifact_id=50485>WAMI - Primer</a> has been developed to help you implement this Best Practice. - - 2012-12-05 + - 12-032r2 + 2022-04-08 + + OGC Testbed 17: CITE Engineering Report + Luis Bermudez + This OGC Testbed 17 Engineering Report (ER) documents the result of the work performed in the CITE thread of the OGC Testbed-17 initiative. CITE is the Compliance Interoperability & Testing Evaluation Subcommittee that provides a forum for an open, consensus discussion regarding approaches and issues related to conformance and interoperability testing as part of the OGC standards process. This ER provides information about the development of a test suite for the OGC API — Processes Standard (OGC18-062r2) to be executed in the OGC Test Evaluation tool (TEAM Engine). The ER also documents an evaluation of an alternative environment for OGC compliance testing. + + - Rahul Thakkar, Michael Maraist + + 21-044 + OGC Testbed 17: CITE Engineering Report + 21-044 + - - 2022-02-08 - 21-017r1 - OGC Features and Geometries JSON Engineering Report - - The OGC Testbed-17 Features and Geometries JSON task investigated proposals for how feature data could be encoded in JSON so that: - -* Different Coordinate Reference Systems (CRS) are supported and -* Communities can build and formally specify profiles of the fully CRS-enabled JSON with limited sets of supported geometry types and with clear constraints for feature type definitions. + + 20-082r4 + + + 20-082r4 + Topic 20 - Observations, measurements and samples + Topic 20 - Observations, measurements and samples + 2023-05-26 + This document defines a conceptual schema for observations, for features involved in the observation process, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities. -GeoJSON, a standard of the Internet Engineering Task Force (IETF), was used as a starting point. +Observations commonly involve sampling of an ultimate feature-of-interest. This document defines a common set of sample types according to their spatial, material (for ex situ observations) or statistical nature. The schema includes relationships between sample features (sub-sampling, derived samples). -This Engineering Report (ER) captures the results and discussions, including material that was submitted to the https://github.com/opengeospatial/OGC-feat-geo-json[OGC Features and Geometries JSON Standards Working Group]. - +This document concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation. + Katharina Schleidt, Ilkka Rinne - OGC Testbed-17: OGC Features and Geometries JSON Engineering Report - - + + - - Clemens Portele - 21-017r1 - - Andreas Matheus - - - 2023-09-21 + + Hideki Hayashi, Akinori Asahara, Kyoung-Sook Kim, Ryosuke Shibasaki, Nobuhiro Ishimaru + + 16-120r3 + Moving Features Access + + OGC Moving Features Access + + 2017-03-12 + 16-120r3 - The OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 JSON Profile v1.0 (GeoXACML 3.0 JSON Profile) Standard defines an extension to the JSON Profile of XACML 3.0 Version 1.1 for supporting GeoXACML Authorization Decision Requests and Authorization Decision encoded in JSON. This ensures an easy uptake in environments where JSON is the preferred encoding. + + This document defines Moving Features Access, i.e., access methods to moving feature data for retrieving feature attributes, information on a relation between a trajectory object and one or more geometry objects, and information on a relation between two trajectory objects from a database storing trajectory data of moving features. -For supporting Geometry as defined by the GeoXACML 3.0 Core conformance class, this profile extends the Attribute DataType definition from JSON Profile of XACML 3.0 Version 1.1 with the geometry data-type urn:ogc:def:geoxacml:3.0:data-type:geometry +Abstract methods of accessing moving features data are defined in ISO 19141:2008 (Geographic information - Schema for moving features) [ISO 19141:2008]. However, the methods are insufficient to access a database storing moving feature data from multiple sources. If implementations for access to moving features data using various programming languages or protocols (e.g., SQL, Java, and HTTP) are developed without any standards, these implementations might be inconsistent with each other, resulting in poor interoperability. Therefore, methods to access a database storing moving feature data are necessary to improve interoperability. -The GeoXACML 3.0 JSON Profile Standard supports the Attribute value to use Well-Known-Text (WKT), Well-Known-Binary (WKB) hex-encoding or GeoJSON as an encoding alternative for the geometry data-type defined in GeoXACML 3.0. +Applications using moving feature data, typically representing vehicles or pedestrians, are rapidly increasing. Innovative applications are expected to require the overlay and integration of moving feature data from different sources to create greater social and business value. Moreover, systems relying on single-source moving feature data are now evolving into more integrated systems. Integration of moving feature data from different sources is a key to developing more innovative and advanced applications. -To support the use of the GeoXACML 3.0 specific attributes SRID, Precision, Encoding, and AllowTransformation, this profile extends the default JSON schema definition from JSON Profile of XACML 3.0 Version 1.1 accordingly. - - 22-050r1 - OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 JSON Profile v1.0 - OGC Geospatial eXtensible Access Control Markup Language (GeoXACML) 3.0 JSON Profile v1.0 - - 22-050r1 +Moving Features Access ensures better data exchange by handling and integrating moving feature data to broaden the market for geo-spatial information such as Geospatial Big Data Analysis. OGC 14-083r2 (OGC® Moving Features Encoding Part I: XML Core) [OGC 14-083r2] and OGC 14-084r2 (OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV)) [OGC 14-084r2] are existing implementation standards. Moving Features Access uses these standards to encode moving features. - - OGC Observations and Measurements – JSON implementation - - 15-100r1 - + + OGC® Open Geospatial APIs - White Paper + 16-019r4 + 2017-02-23 + Open Geospatial APIs - White Paper + 16-019r4 + + OGC defines interfaces that enable interoperability of geospatial applications. API’s are a popular method to implement interfaces for accessing spatial data. This White Paper provides a discussion of Application Programming Interfaces (APIs) to support discussion of possible actions in the Open Geospatial Consortium (OGC). + George Percivall - This Discussion Paper specifies a potential OGC Candidate Standard for a JSON implementation of the OGC and ISO Observations and Measurements (O&M) conceptual model (OGC Observations and Measurements v2.0 also published as ISO/DIS 19156). This encoding is expected to be useful in RESTful implementations of observation services. -More specifically, this Discussion Paper defines JSON schemas for observations, and for features involved in sampling when making observations. These provide document models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities. - - - Simon J D Cox, Peter Taylor - Observations and Measurements – JSON implementation - 15-100r1 - - 2015-12-09 - - - + - Christiaan Lemmen, Peter van Oosterom, Mohsen Kalantari, Eva-Maria Unger, Cornelis de Zeeuw - This white paper provides an overview of the land administration domain and proposes actions needed for design and develop implementation standards this domain. A close cooperation between the Open Geospatial Consortium (OGC) and ISO is expected to accelerate those developments. - -A huge task is waiting: the establishment of land rights for all: young and old, rich and poor, male and female. Data on many millions of parcels, spatial units, (use-) rights, persons, and parties have to be collected, linked, maintained, and published. Land Administration Systems (LAS) should be designed for maintenance of the dynamic relations between people and land. Existing land administrations require extensions: such as 3D and 4D functionality and datasets, blockchain for transparent transactions, generic processes and integration with remote sensing, and processes to support conversion from social to legal tenure. - -A broad range of geospatial technologies and applications are available. They range from satellite and drone imaging and mapping, to geodesy, precise positioning, geo‐information science, cartography, spatial data infrastructure, and many surveying sub‐disciplines. The scientific and professional disciplines in the geospatial community design, develop, and apply those technologies. Apart from this technical component, a land administration also has a social and legal component. This makes land administration an arena where, apart from the geospatial community, many different scientific and professional disciplines meet. Depending on the stage of development and the level of societal acceptance of the land administration, those disciplines involved may be different. - - 2019-02-12 - 18-008r1 - White Paper on Land Administration - 18-008r1 - OGC White Paper on Land Administration - - - - 2017-05-15 - This OGC Testbed 12 Engineering Report (ER) discusses the topic of implementing vector tiles in an OGC GeoPackage. This report builds on the general topic of vector tiling discussed in OGC Testbed 12 Engineering Report [OGC 16-068r4]. - -Since its public release in 2012, OGC GeoPackage has been getting increasingly popular within the geospatial industry for a variety of use cases, such as a means to package geospatial data for use on a mobile device and as a means to exchange geospatial data between two systems. - -The OGC GeoPackage standard currently specifies requirements (rules) for storing raster tiles and vector (simple) features. This Engineering Report proposes an extension to the supported data types by introducing an implementation for vector tiles. - -While tiling and the use of multiple levels of details are a proven technique for accessing and visualizing raster data, it is less commonly applied for vector data. This is due to the increased complexity compared to raster tiling and lack of standardization on the topic. Yet, implementing vector tiles can provide the same benefits as for using raster tiles. - -Services can easily cache tiles and return them instantly upon request, without the need for any additional pre/post processing. Consequently, clients can get tiles very fast, ensuring fast and responsive maps. + + Discussion Paper - JSON Encodings for EO Coverages + + 19-042r1 + 19-042r1 + Discussion Paper - JSON Encodings for EO Coverages + + This discussion paper documents and concludes one year (2018-2019) of work undertaken by a National Aeronautics and Space Administration (NASA) Earth Science Data System Working Group focused on exploring JSON Encodings in Earth Observation Coverages. The primary function of this paper is to ensure that the collective Working Group knowledge obtained from the year effort is not lost and consequently that it can be considered, debated and hopefully utilized in other forums outside of NASA with the aim of driving progress in this field. The covering statement (below) provides 10 questions which are meant to facilitate such discussion. -Using tiled, multileveled data representations, clients can always access the data most suitable for their current map location and scale. This avoids the need to load too much data, which can cause excessive memory usage and reduce overall performance. +This discussion paper will be of particular interest to the following parties: -The goal is to enable systems to use OGC GeoPackage as a means to store and access vector tiles in an efficient way, similar to raster tiles. +Web application developers tasked with designing and developing applications which consume Earth Observation spatial data encoded as JSON. - - Testbed-12 Vector Tiling Implementation Engineering Report - - - +Parties (including standards bodies) interested in serving and consuming Spatial data on the Web e.g. World Wide Web Consortium (W3C), Open Geospatial Consortium (OGC) or developers of other data standards, etc. + Lewis John McGibbney - - Daniel Balog, Robin Houtmeyers - Testbed-12 Vector Tiling Implementation Engineering Report - 16-067r4 - - 16-067r4 + + + + 2019-11-11 - - + + + + 2010-08-18 - Documents of type Discussion Paper - draft - Documents of type Discussion Paper - draft - - Documents of type Discussion Paper - draft + OWS-7 Feature and Statistical Analysis Engineering Report + Theodor Foerster, Bastian Schäffer + 10-074 + This Engineering Report (ER) is a deliverable for the OGC Web Service 7 testbed. The focus of this ER is using the OGC Web Processing Service (WPS) interface standard for Feature and Statistical Analysis (FSA). Specifically, the ER documents how to enhance interoperability of FSA processes that are hosted as WPS processes on the Web. This ER is coordinated with the Feature and Decision Fusion (FDF) WPS Profiling ER. + + 10-074 + OWS-7 Feature and Statistical Analysis Engineering Report + + - + + - Transducer Markup Language - 06-010r6 - 2007-07-02 - 06-010r6 + 18-073r2 + John Tisdale - Steve Havens - *THIS STANDARD HAS BEEN RETIRED* - -The OpenGIS® Transducer Markup Language Encoding Standard (TML) is an application and presentation layer communication protocol for exchanging live streaming or archived data to (i.e. control data) and/or sensor data from any sensor system. A sensor system can be one or more sensors, receivers, actuators, transmitters, and processes. A TML client can be capable of handling any TML enabled sensor system without prior knowledge of that system. - -The protocol contains descriptions of both the sensor data and the sensor system itself. It is scalable, consistent, unambiguous, and usable with any sensor system incorporating any number sensors and actuators. It supports the precise spatial and temporal alignment of each data element. It also supports the registration, discovery and understanding of sensor systems and data, enabling users to ignore irrelevant data. It can adapt to highly dynamic and distributed environments in distributed net-centric operations. - -The sensor system descriptions use common models and metadata and they describe the physical and semantic relationships of components, thus enabling sensor fusion. + + OGC PipelineML Conceptual and Encoding Model Standard + + 18-073r2 + OGC PipelineML Conceptual and Encoding Model Standard + The OGC PipelineML Conceptual and Encoding Model Standard defines concepts supporting the interoperable interchange of data pertaining to oil and gas pipeline systems. PipelineML supports the common exchange of oil and gas pipeline information. This initial release of the PipelineML Core addresses two critical business use cases that are specific to the pipeline industry: new construction surveys and pipeline rehabilitation. This standard defines the individual pipeline components with support for lightweight aggregation. Additional aggregation requirements such as right-of-way and land management will utilize the OGC LandInfra standards with utility extensions in the future. Future extensions to PipelineML Core will include (non-limitative): cathodic protection, facility and safety. PipelineML was advanced by an international team of contributors from the US, Canada, Belgium, Norway, Netherlands, UK, Germany, Australia, Brazil, and Korea. -This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. - - - - OpenGIS Transducer Markup Language *RETIRED* - +This standard assumes the reader has a basic understanding of oil and gas pipeline industry concepts. + 2019-08-08 - + + + Use Cases and Applications of the OGC Moving Features Standard: The Requirements for a Moving Feature API - 06-126 - 2006-10-18 - - - - Chuck Morris - Compliance Test Language (CTL) Discussion Paper + Akinori Asahara, Hideki Hayashi, Carl Reed + + Use Cases and Applications of the OGC Moving Features Standard: The Requirements for a Moving Feature API + 15-096 + 15-096 - Compliance Test Language (CTL) Discussion Paper - 06-126 - This document establishes Compliance Test Language, an XML grammar for documenting and scripting suites of tests for verifying that an implementation of a specification complies with the specification. - - - Yves Coene - This document describes the results of an experiment addressing issues relating to the application workflow processing incorporating a variety of OGC specifications. It details the inputs provided to the Open Geospatial Consortium's (OGC) OWS-3 Testbed and the architecture of the testbed related to the ESA Service Support Environment (SSE). -It is a formal deliverable of work package 6610 of the Enhanced Service Infrastructure Technology (ESIT) project and is a joint Spacebel and Spot Image document. - - 05-140 - 2006-03-30 - 05-140 - OWS-3 Imagery Workflow Experiments: Enhanced Service Infrastructure Technology Architecture and Standards in the OWS-3 Testbe - - OWS-3 Imagery Workflow Experiments: Enhanced Service Infrastructure Technology Architecture and Standards in the OWS-3 Testbe - - + This OGC Discussion Paper provides examples of some actual and potential geospatial applications using the OGC Moving Features encoding. These applications can be used to define the next steps in the development of the OGC Moving Features Standard: The definition of a “Moving Features API”. As a conclusion, the Moving Features SWG recommends that a new Moving Features API standard should target the following three kinds of operations: retrieval of feature information, operations between a trajectory and a geometric object, and operations between two trajectories. Additionally, the Moving Features SWG recommends establishing an abstract specification for these three kinds of operations because only a part of operations for trajectories is defined by ISO 19141:2008 - Schema for moving features. + 2016-01-18 + + + + 07-118r8 + User Management for Earth Observation Services + User Management for Earth Observation Services + This document describes how user and identity management information may be included in the protocol specifications for OGC Services. The use cases addressed will make reference to EO (Earth Observation) services, for example catalogue access (EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0 [OGC 06-131]), ordering (Ordering Services for Earth Observation Products [OGC 06-141r2]) and programming (OpenGIS Sensor Planning Service Application Profile for EO Sensors [OGC 07-018r2]). + + P Denis + 2010-09-08 + + 07-118r8 + - - - - + + + 09-104r1 + Draft for Candidate OpenGIS® Web 3D Service Interface Standard + 2010-01-20 + Arne Schilling, Thomas H. Kolbe + 09-104r1 + A Web 3D Service (W3DS) is a portrayal service for three-dimensional geodata, such as landscape models, city models, textured building models, vegetation objects, and street furniture. Geodata is delivered as scenes that are comprised of display elements, optimized for efficient real time rendering at high frame rates. + + + + + Draft for Candidate OpenGIS® Web 3D Service Interface Standard + - + + + 2024-08-10T10:33:53.521511 + 2024-08-10T10:33:52.467869 + + + + + + 2006-08-21 + Joshua Lieberman + Geospatial Semantic Web Interoperabiltiy Experiment Report + + + + The Semantic Web seeks to make the meaning as accessible as the material, by enabling connections - which are both logical and (machine) actionable - between concepts which a user presently understands and those which may be new and foreign. The Geospatial Semantic Web extends this capability to both content and concepts that are specifically spatial, temporal, and geographic in nature, giving both people and machines true access to a wider range of knowledge. + 06-002r1 + Geospatial Semantic Web Interoperabiltiy Experiment Report + 06-002r1 - 2001-02-06 - John Evans - XML for Image and map Annotation - 01-019 - Defines an XML vocabulary to encode annotations on imagery, maps, and other geospatial data. This vocabulary draws on the Geography Markup Language (OpenGIS - XML for Image and map Annotation - 01-019 + + + Peter Axelsson, Lars Wikström + InfraGML 1.0: Part 5 - Railways - Encoding Standard + 16-105r2 + 2017-08-16 + - + + OGC InfraGML 1.0: Part 5 - Railways - Encoding Standard + + This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. +InfraGML is published as a multi-part standard. This Part 5 addresses the Railway Requirements Class from LandInfra. + 16-105r2 + - - The subject of this Engineering Report (ER) is the evaluation of Cloud Optimized GeoTIFF (COG) and Zarr data container implementations. The ER aims to: - - Describe the use cases adopted for the evaluation (with existing implementation and with Testbed-17 implementation); - Identify the opportunity of proposing that COG and Zarr become OGC standards; - Describe all components developed during the Testbed; and - Provide an executive summary and a description of recommended future work items. - - + + Topic 19 - Geographic information - Linear referencing + 10-030 + Same as ISO IS 19148: 2012. Download at http://www.iso.org + Paul Scarponcini + 10-030 + 2012-03-20 + + + Topic 19 - Geographic information - Linear referencing + + + + + - 21-032 - OGC Testbed 17: COG/Zarr Evaluation Engineering Report + 22-038r2 + Testbed-18: Reference Frame Transformation Engineering Report + 2023-03-09 + 22-038r2 + Martin Desruisseaux + Currently, most OGC standards focus on data that is observed on the ground or directly above planet Earth. Other standards, such as GeoSciML, provide a data model and transfer standard for geological data. Other projects have considered data models and exchange standards for the seas and oceans. Extra-terrestrial space and the exact location of remote spaceborne sensors has been less in focus. This OGC Testbed 18 Engineering Report (ER) starts with an evaluation of current standards and then proposes changes or extensions to those standards in order to describe objects in orbit around any celestial body or in free flight in our solar system with respect to their location, trajectory, and orientation. Finally standard-based mechanisms to transform a location within a reference frame to a location within another reference frame are examined. - 21-032 - OGC Testbed 17: COG/Zarr Evaluation Engineering Report - Giovanni Giacco, Mauro Manente, Pedro Gonçalves, Martin Desruisseaux, Even Rouault - 2022-01-24 - - - - 2008-03-11 - - CSW-ebRIM Registry Service - Part 2: Basic extension package - 07-144r2 - - - - 07-144r2 - - This OGC® document is a companion to the CSW-ebRIM catalogue profile (OGC 07-110r2). It specifies the content of the Basic extension package that shall be supported by all conforming services. The package includes extension elements of general utility that may be used to characterize a wide variety of geographic information resources, with a focus on service-oriented metadata management. - CSW-ebRIM Registry Service - Part 2: Basic extension package - Richard Martell + + Testbed-18: Reference Frame Transformation Engineering Report + + - - This document reports the considered SANY best practice for using OGC standards to provide generic fusion processing services. Concrete case studies are documented and a detailed appendix is provided with example of XML request and responses. - + + + + OGC-NA tools + + 0.3.49 + + + + Testbed 10 Aviation Human Factor Based Portrayal of Digital NOTAMs ER + 14-039 + + OGC® Testbed 10 Aviation Human Factor Based Portrayal of Digital NOTAMs ER + This activity is part of OGC Testbed 10. The aviation thread was focused on developing and demonstrating the use of the Aeronautical Information Exchange Model (AIXM) and the Flight Information Exchange Model (FIXM), building on the work accomplished in prior testbeds to advance the applications of OGC Web Services standards in next generation air traffic management systems to support European and US aviation modernization programs. +This document provides the result of the Testbed 10 to assess the compliance between the OGC standards and the guidelines provided by the SAE in their latest published document regarding portraying of NOTAMs. Specifically, the Human Based Portrayal of DNOTAM work attempts to fulfill the high level requirements identified in the OGC Testbed-10 RFQ Annex B . +The purpose of this investigation was to analyze the recommendations of the SAE comity and to evaluate the feasibility of their application using OGC standards for portraying, namely the Symbology Encoding standard, version 1.1. + + + 2014-07-16 + + 14-039 + Thibault Dacla, Daniel Balog - Stuart E. Middleton - SANY Fusion and Modelling Architecture + + + + The purpose of the GetCorridor operation is to extract a corridor based on a trajectory from a multidimensional coverage. The need for the getCorridor operation stems from active members of the OGC MetOcean Domain Working Group (DWG) who saw a manifest need for extraction of such information from gridded datasets. This work has been done by members of the OGC MetOcean Domain Working Group. - 10-001 - - SANY Fusion and Modelling Architecture - 10-001 - - 2010-03-22 + 15-108r3 + MetOcean Application profile for WCS2.1: Part 1 MetOcean GetCorridor Extension + + + + OGC MetOcean Application profile for WCS2.1: Part 1 MetOcean GetCorridor Extension + Peter Trevelyan, Paul Hershberg, Steve Olson + 15-108r3 + 2021-03-22 + - + + Charles Chen + 17-035 + Testbed-13: Cloud ER + 17-035 + OGC Testbed-13: Cloud ER + + 2018-01-08 + + + This OGC Engineering Report (ER) will describe the use of OGC Web Processing Service (WPS) for cloud architecture in the OGC Testbed 13 Earth Observation Cloud (EOC) Thread. This report is intended to address issues in lack of interoperability and portability of cloud computing architectures which cause difficulty in managing the efficient use of virtual infrastructure such as in cloud migration, storage transference, quantifying resource metrics, and unified billing and invoicing. This engineering report will describe the current state of affairs in cloud computing architectures and describe the participant architectures based on use case scenarios from sponsor organizations. + +Cloud computing is paving the way for future scalable computing infrastructures and is being used for processing digital earth observation data. In this EOC thread effort, data is stored in various storage resources in the cloud and accessed by an OGC Web Processing Service. The methods in which these processes are deployed and managed must be made interoperable to mitigate or avoid the complexities of administrative effort for the scientific community. In other words, the intent of this effort is to develop a way for scientists to acquire, process, and consume earth observation data without needing to administer computing cloud resources. - 2011-07-14 - - The purpose of this report is to recommend appropriate architectures and procedures for migrating the CUAHSI HIS to the OGC-based WaterML 2.0 encoding (profile of OGC O&M standard) and OGC web services such as Sensor Observation Service (SOS), Web Feature Service (WFS), Web Mapping Service (WMS), Web Coverage Service (WCS), and Catalogue Service for the Web (CSW). This report may be used as the basis for future OGC Interoperability Program initiatives. - 11-013r6 - Water Information Services Concept Development Study - 11-013r6 - - OGC® Engineering Report: Water Information Services Concept Development Study - Luis Bermudez, David Arctur - - - Testbed 12 work has resulted in Change Requests (CRs) to the GeoPackage Encoding Standard. CRs have been submitted to the GeoPackage Standards Working Group (SWG) as GitHub issues. This engineering report (ER) summarizes the results of these activities. - Testbed-12 GeoPackage Change Request Evaluations - - 2017-05-12 - Jeff Yutzler + + 2024-07-22 + OGC Testbed-19 has continued and furthered an ongoing discussion about how to interact with GeoDataCubes (GDC) in the most interoperable way (see Chapter 1 for more Introduction). Testbed 19 participants produced a draft OGC GDC API standard that incorporates the most relevant developments in the field in and outside of OGC. This work advanced the common understanding of available solutions while discovering to a much better degree the advantages and drawbacks of current solutions. Testbed 19 participants produced prototypes of five back-end implementations and six client implementations as well as an automated test suite, which are described in full detail in Chapter 4. Many of the researched solutions are also available as open source and hence offer a perfect starting point for further GDC activities. + +The main technologies that were evaluated in Testbed 19 included the OGC API Standards suite1, the openEO API2 and the Spatiotemporal Asset Catalog3 (STAC) specification. Based on cross walk comparisons (see Chapter 2), a unified draft GDC API was developed integrating as much as possible the existing solutions. openEO is largely compliant with the OGC API- Common Standard. As such, the openEO API specification provided the foundation for defining a draft OGC GDC API draft standard. During the Testbed 19 period, more building blocks from the OCG API were incorporated into the draft GDC API document. These building blocks included parts of OGC API — Common, OGC API — Coverages, and OGC API – Processes. There is also future potential for visualization services through maps or tiles or even including components or elements of the OGC Web Services suite of Standards, such as WMS, WMTS, WCS, etc. + +The current version of the draft GDC API, described in D71 of T19, supports different scenarios enabling implementations of the draft standard to offer only minimal support for data access with minimal manipulation of the data. Minimal manipulation is in terms of subsetting and reprojecting or including more advanced processing capabilities by incorporating building blocks from the openEO specification or from the OGC API — Processes – Part 1: Core Standard. Chapter 3 gives an overview of the draft standard. + +The interaction capabilities between the different servers and clients developed are described in Chapter 5 and first impressions on usability in Chapter 6. + +Future work could include the ability to link two processing options into one “integrated” option that supports either submitting openEO process graphs to a OGC API – Processes endpoint (extending and working on Processes — Part 3), or supports integration of an OGC API – Processes process in the process graph of openEO through an extended concept of user defined functions in openEO. Further discussion is also needed on the pros and cons of including authentication in the draft standard. More details about lessons learned and suggestions can be found in Chapters 7 and 8 of this ER. + + 23-047 + OGC Testbed-19 GeoDataCubes Engineering Report + + Alexander Jacob + 23-047 - Testbed-12 GeoPackage Change Request Evaluations - 16-031r1 - - 16-031r1 + OGC Testbed-19 GeoDataCubes Engineering Report - + + + - 10-090r3 - Network Common Data Form (NetCDF) Core Encoding Standard version 1.0 + The National System for Geospatial-Intelligence (NSG) GeoPackage Profile defines and tailors the implementable provisions prescribed for the NSG for a GeoPackage based on the OGC GeoPackage encoding standard. The profile provides detailed directions on how to use the clauses, options and parameters defined in the base GeoPackage standard. The goal is to ensure that NSG GeoPackages, GeoPackage SQLite Extensions, and supporting utilities and services fulfill their intended purposes and are fit for use. + +The goal of this Engineering Report (ER) is to assess whether requirements as specified in the proposed profile are specific enough to allow for any two independent GeoPackage implementers to produce and consume interoperable NSG GeoPackages. Concerns with the profile are outlined and recommendations for improvement are provided. Thoughts on the viability of the profile approach and guidance on how the profile could apply to Vector Tiling are also provided. + 2017-05-12 - - - - This document specifies the network Common Data Form (netCDF) core standard and extension mechanisms. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space and time-varying phenomena. -NetCDF is a data model for array-oriented scientific data. A freely distributed collection of access libraries implementing support for that data model, and a machine-independent format are available. Together, the interfaces, libraries, and format support the crea-tion, access, and sharing of multi-dimensional scientific data. - - OGC Network Common Data Form (NetCDF) Core Encoding Standard version 1.0 - Ben Domenico - - 10-090r3 - 2011-04-05 + Testbed-12 NSG GeoPackage Profile Assessment Engineering Report + 16-038 + + 16-038 + Testbed-12 NSG GeoPackage Profile Assessment Engineering Report + Chris Clark + - - - 04-019r2 - 2004-11-02 - Mike Botts - Sensor Model Language (SensorML) for In-situ and Remote Sensors - Sensor Model Language (SensorML) for In-situ and Remote Sensors - 04-019r2 + + Reference Model for the ORCHESTRA Architecture + 07-097 + + + 2007-10-05 + Thomas Uslander (Ed.) + + 07-097 - The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances. - + Reference Model for the ORCHESTRA Architecture + This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It is an extension of the OGC Reference Model and contains a specification framework for the design of geospatial service-oriented architectures and service networks. The RM-OA comprises the generic aspects of service-oriented architectures, i.e., those aspects that are independent of the risk management domain and thus applicable to other application domains. - - - - - - 07-095r2 - Web Services Summaries - Arliss Whiteside + + Josh Lieberman + 2021-07-02 + + OGC Technical Paper on the Standards Landscape for Building Data + 21-037 + OGC Technical Paper on the Standards Landscape for Building Data + + Data about buildings and building structures play roles at scales from neighborhoods to nations in creating, protecting, regulating, and understanding the built environment. This report examines standards which may be useful in defining the structure and content of building data at a national scale, a national building layer. Standard models, schemas, and encodings may be especially useful for supporting an extensible building dataset with an efficient core definition, but the ability to encompass more detailed or specialized data as needed in as seamless and compatible a manner as possible. Standards compiled and described in this document range from generic geographic data encodings to models and specifications for specific building perspectives such as land parcel improvements, facility ownership, footprint / roofline extractions, residency affordances, envelope characteristics, and so on. They provide potential source material for a modular and multi-platform building layer definition which can be applied to a reasonably wide set of use cases. This definition may in turn be a standardization candidate for adoption by other national geographic data collections. - 07-095r2 - OGC Web Services Summaries - This document provides brief and consistent summaries of several OGC Web Service interface specifications that serve data. - 2007-11-14 + 21-037 + - - - **This document has been retired. It is not supported. You should consider using Web Coverage Service.** + + Panagiotis (Peter) A. Vretanos + This engineering report describes a protocol for synchronizing data between two enterprise servers. While the protocol itself is generic, this engineering report describes its application to web feature servers. - This specification was designed to promote interoperability between software implementations by data vendors and software vendors providing grid analysis and processing capabilities. - 01-004 - Grid Coverage Service Implementation Specification - 2001-01-12 - Louis Burry - +In the simplest terms, the protocol involves each synchronization peer accessing the other’s Sync resource to get the set of changed objects since the last time the Sync resource was accessed. In the case of web feature servers, the objects are features. The requesting peer then compare that list of changed features with the identically identified features in its data store and performs any necessary changes so that the feature states match. + +Continuing the work done in Testbed-11, this engineering report describes the implementation of a Sync operation in a WFS server that: + +Enhances the Sync operation from Testbed-11 to include an abstract query element where each service type can then substitute their specific query syntax for identifying the specific sub-set of changed features to be synchronized. In the case of the WFS, several query syntaxes may be used including the wfs:Query element and a REST based feature type URI with query parameters. + +Extends the definition of the Sync operation with the addition of a resultType parameter to allow a client to obtain a hit count of the number of features that a Sync operation shall return. + +Shall investigate the proper procedure for handling resource references. Implementing the resolvePath parameter alone is not sufficient to ensure complete data set synchronization. + +Shall investigate concurrency and consistency issues. + 2017-03-09 + Testbed-12 Web Feature Service Synchronization + + Testbed-12 Web Feature Service Synchronization + 16-044 + + + + + 16-044 + + + 01-111 + 2001-06-08 + ISO 19115 was adopted as a replacement for OGC Abstract Specification Topics 9 and 11. In June 2001, a motion to include material in addition to ISO 19115 was adopted as document 01-111 Metadata AS. The approved addition to document 01-111 is contained in document 01-053r1, which normatively references parts of the old AS Topic 9, document 99-109r1. FGDC in conjunction with ANSI INCITS L1 are planning the migration of the FGDC Content Standard for Geospatial Metadata to be a profile of ISO 19115 + Topic 11 - Metadata + 01-111 + + + + ISO + - OpenGIS Grid Coverage Service Implementation Specification - 01-004 - - + + Topic 11 - Metadata - + + 2006-04-05 + Observations and Measurements + + - - 2009-07-27 - This application document describes: - -1) What is a Debris Flow Monitoring System. -2) How SWE implements in Debris Flow Monitoring System. -3) Tutorial for SWE developers. - - Sensor Web Enablement Application for Debris Flow Monitoring System in Taiwan - 09-082 + + 05-087r3 + Observations and Measurements + 05-087r3 + + The general models and XML encodings for observations and measurements, including but not restricted to those using sensors. + Simon Cox + + - Hsu-Chun James Yu, Zhong-Hung Lee, Cai-Fang Ye, Lan-Kun Chung, Yao-Min Fang - - 09-082 - Sensor Web Enablement Application for Debris Flow Monitoring System in Taiwan + OWS-4 Workflow IPR + 2007-05-07 + 06-187r1 + + This document examines five workflows discussed during the course of the OWS-4 project. + + Workflow Descriptions and Lessons Learned + 06-187r1 + Steven Keens + + - - - - - - - - - - - - - - - - - - - - - - - - - + - Peter Baumann - - 2011-12-19 - 11-116 - - - OWS-8 Geoprocessing for Earth Observations Engineering Report - 11-116 - OWS-8 Geoprocessing for Earth Observations Engineering Report - Ad-hoc processing of Earth Observation (EO) data available through online resources is -gaining more and more attention. Expected benefits include -- More versatile EO data access -- More convenient EO data access -- Consequently, broadened use and exploitation of EO data -- An important step towards integration of EO data into automatic chaining and -orchestration -- More efficient EO data access: indicating the exact desired result and evaluating -processing code close to the coverage data source (i.e., on the server) minimizes -network traffic, one of today’s critical performance limiting factors. - + + + + GML 3.2 implementation of XML schemas in 07-022r1 + + Simon Cox + GML 3.2 implementation of XML schemas in 07-022r1 + 08-128 + 2009-03-06 + + 08-128 - - 23-048 - OGC Testbed 19 Draft API - Geodatacubes specification - OGC Testbed 19 Draft API - Geodatacubes specification - - + + Panagiotis (Peter) A. Vretanos + + Testbed-10 Service Integration Engineering Report + 14-013r1 + 2014-05-19 + OGC® Testbed-10 Service Integration Engineering Report - Matthias Mohr - - 23-048 - 2024-07-22 - This OGC Testbed 19 Engineering Report documents a draft OGC API — GeoDataCube Standard (aka GDC API). The OGC Member participants in this Testbed 19 activity developed, documented, and tested the draft OGC GDC API Standard. The draft will be submitted to the OGC GeoDataCube Standards Working Group (SWG) as a new standards work item. - -The OGC GeoDataCube SWG was chartered to respond to the long-standing issue of establishing a standard that supports accessing and processing geospatial datacubes in an interoperable way. The draft OGC API — GeoDataCube that was developed in OGC Testbed 19 responds to this need and proposes a draft API specification. - -The Testbed 19 GDC initiative targeted enhanced interoperability. The draft GDC API Standard was based on OGC API — Common, OGC API — Coverages Standard, OGC API — Processes Standard, the STAC API, and the openEO API. The Testbed 19 participants concentrated on server and client application development, and usability testing based on conformance classes and use cases. The draft GDC API is defined as an OpenAPI 3.0 document and provides endpoints for capabilities, data discovery/access, process discovery, and data processing. Notably, the draft GDI API Standard is extensible through additional implementations of OGC API Standards or openEO API parts. Documentation is available in machine-readable YAML and human-friendly HTML through a GitHub repository. - - - - - + - - Web Coverage Service (WCS) Implementation Specification (Corrigendum) - 05-076 - 05-076 - - - OpenGIS Web Coverage Service (WCS) Implementation Specification (Corrigendum) - John Evans - 2006-03-31 - Extends the Web Map Server (WMS) interface to allow access to geospatial coverages that represent values or properties of geographic locations, rather than WMS generated maps (pictures). - -The original document is available at: http://portal.opengeospatial.org/files/?artifact_id=3837 + This document specifies technical changes to the OGC web service architecture baseline to support better integration among the services. Although integration may be achieve in a number of ways and using a number of other technologies, the goal of this document is to achieve this integration within the current OGC service framework in order to leverage existing investments in OGC web services infrastructure. + + 14-013r1 - - - Defence Profile of OGC Web Map Service 1.3 Revision + + - DGIWG + 2016-01-29 + + 09-102r3a + DGIWG - Web Map Service 1.3 Profile - Revision + 09-102r3a + + + + Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey This document defines specific DGIWG requirements, recommendations and guidelines for implementations of the ISO and OGC Web Map Service standards; ISO 19128:2005 Web Map Server Interface and the OpenGIS Web Map Server Implementation Specification 1.3.0. - 09-102r3 - Defence Profile of OGC Web Map Service 1.3 Revision - 2021-02-25 - 09-102r3 - - - + DGIWG - Web Map Service 1.3 Profile - Revision + + + Documents of type Specification Profile - deprecated + + + + Documents of type Specification Profile - deprecated + Documents of type Specification Profile - deprecated - - OGC Earth Observation Applications Pilot: Pixalytics Engineering Report - 20-037 - - - 20-037 + + Jo Walsh, Pedro Gonçalves, Andrew Turner + OpenSearch Geospatial Extensions Draft Implementation Standard + 09-084r1 + + - - 2020-10-22 - - Samantha Lavender - OGC Earth Observation Applications Pilot: Pixalytics Engineering Report - This is an individual Engineering Report (ER) created by Pixalytics Ltd as part of the Earth Observation Applications Pilot. Pixalytics' role was that of an App developer, testing deployment to the OGC Earth Observation Applications Pilot architecture. + The OpenSearch specification originates in a community effort built around Amazon's A9.com. It was intended to allow syndication of search results that could then be aggregated by one large index. The OpenSearch specification is made available under the Creative Commons Attribution-Sharealike 2.5 license. In addition, the OASIS Search Web Services group is publishing an Abstract Protocol Definition of the interface or “binding”, which coincides with the community specification published at http://opensearch.org. In 2007, Andrew Turner proposed a set of geospatial extensions through OpenSearch.org. + OpenSearch Geospatial Extensions Draft Implementation Standard + 2009-10-13 + + 09-084r1 + - - Matthes Rieke, Simon Jirka, Stephane Fellah - 2015-11-18 - 15-057r2 + + 12-096 + + OWS-9: Engineering Report: Use of SWE Common and SensorML for GPS Messaging + Mike Botts + 12-096 + OWS-9: Engineering Report: Use of SWE Common and SensorML for GPS Messaging + 2013-02-01 + This document is an Engineering Report for the OWS-9 Interoperability Test Bed. The focus of the document is discussion and demonstration on the use of SWE Common Data 2.0 encodings to support an interoperable messaging description and encoding for the next generation GPS message streams into and out of the GPS navigation accuracy improvement services. The connection of SWE Common to SensorML 2.0 and the application of SensorML to describe the processing surrounding GPS navigation improvement will also be discussed. - OGC® Testbed-11 Incorporating Social Media in Emergency Response Engineering Report - 15-057r2 - Testbed-11 Incorporating Social Media in Emergency Response Engineering Report - This OGC Engineering Report (ER) was created as a deliverable for the OGC Testbed 11 initiative of the OGC Interoperability Program. This ER describes an approach for incorporating Social Media for Emergency Response applications that use spatial data infrastructures. This document also reports on findings about the advancements using Social Media and VGI resources. The ER includes ideas on improving the architecture, service change recommendations (primarily concerning the OGC Sensor Observation Service (SOS) 2.0 interface), and lessons learned. - - - - - Sergio Taleisnik - OGC Disaster Pilot JSON-LD Structured Data Engineering Report + + OGC Testbed 19 Extraterrestrial GeoTIFF Engineering Report + 23-028 + + With the growing number of space assets and missions, the space industry needs a way to locate extra-terrestrial objects within the captured imagery. The current GeoTIFF Standard provides the location of terrestrial objects using TIFF tags. However, objects in space are relative to the observer and the distance of the objects in the imagery are often at great distances from the observer. Multiple objects can exist within the imagery which are at different spacetime locations in four dimensions. To further complicate the definition of the location, from a planar perspective, the edges of the image fade into infinity. With the use of spherical and gridded coordinates an image can tag pixels along the edge of a sphere or the camera location. The Testbed 19 Engineering Report (ER) extends GeoTIFF to work for all images including both terrestrial and non-terrestrial observations within the image. + + + 23-028 + OGC Testbed 19 Extraterrestrial GeoTIFF Engineering Report + Michael Leedahl + - OGC Disaster Pilot JSON-LD Structured Data Engineering Report - 21-054 - + 2024-04-16 + + + UML-to-GML Application Schema Pilot (UGAS-2020) Engineering Report - This Disaster Pilot JSON-LD Structured Data Engineering Report documents the analysis, discussions, results, and recommendations that emerge from the efforts carried out regarding the use of JSON-LD with OGC APIs to generate structured web page data for search engine optimization of disaster related information. + During UGAS-2020 emerging technology requirements for NAS employment in the NSG, and with general applicability for the wider geospatial community, were investigated and solutions developed in four areas. -This ER provides the practical experience and lessons learned on the usage of Linked Data within OGC APIs with the objective of enhancing the web search and finding up-to-date conditions, observations, and predictions associated with well-known local geography. Upcoming initiatives should use the findings documented in this ER to further develop applications that make geospatial data and information more easily findable, accessible, interoperable, and reusable, which will increase the efficiency of disaster response. This ER could also be used as a case study of Linked Data to help other industries understand its value and implement it within their domains, or it could serve as a baseline for adding Linked Data support to one or several OGC API standards. - 21-054 - 2023-01-05 - - - WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data - 14-003 - Simon J D Cox, Bruce A Simons - This Best Practice describes how to configure XML documents for single and time series water quality measurements. In addition to stating the rules for using the O&M and WML 2 standards, along with the appropriate content ontologies, this Best Practice provides guidance through examples. This document is intended to complement WaterML 2.0 as part of a suite of standards for water observation data. - - +To enable a wide variety of analytic tradecrafts in the NSG to consistently and interoperably exchange data, the NAS defines an NSG-wide standard UML-based application schema in accordance with the ISO 19109 General Feature Model. In light of continuing technology evolution in the commercial marketplace it is desirable to be able to employ (NAS-conformant) JSON-based data exchanges alongside existing (NAS-conformant) XML-based data exchanges. A prototype design and implementation of UML Application Schema to JSON Schema rules (see the OWS-9 SSI UGAS Conversion Engineering Report) was reviewed and revised based on the final draft IETF JSON Schema standard “draft 2019-09.” The revised implementation was evaluated using NAS Baseline X-3. This work is reported in section UML to JSON Schema Encoding Rule. + +To maximize cross-community data interoperability the NAS employs conceptual data schemas developed by communities external to the NSG, for example as defined by the ISO 19100-series standards. At the present time there are no defined JSON-based encodings for those conceptual schemas. A JSON-based core profile was developed for key external community conceptual schemas, particularly components of those ISO 19100-series standards used to enable data discovery, access, control, and use in data exchange in general, including in the NSG. This work is reported in section Features Core Profile of Key Community Conceptual Schemas. + +The Features Core Profile and its JSON encoding have been specified with a broader scope than the NAS. It builds on the widely used GeoJSON standard and extends it with minimal extensions to support additional concepts that are important for the wider geospatial community and the OGC API standards, including support for solids, coordinate reference systems, and time intervals. These extensions have been kept minimal to keep implementation efforts as low as possible. If there is interest in the OGC membership, the JSON encoding of the Core Profile could be a starting point for a JSON encoding standard for features in the OGC. A new Standards Working Group for a standard OGC Features and Geometries JSON has been proposed. + +Linked data is increasingly important in enabling “connect the dots” correlation and alignment among diverse, distributed data sources and data repositories. Validation of both data content and link-based data relationships is critical to ensuring that the resulting virtual data assemblage has logical integrity and thus constitutes meaningful information. SHACL, a language for describing and validating RDF graphs, appears to offer significant as yet unrealized potential for enabling robust data validation in a linked-data environment. The results of evaluating that potential – with emphasis on deriving SHACL from a UML-based application schema - are reported in section Using SHACL for Validation of Linked Data. + +The OpenAPI initiative is gaining traction in the commercial marketplace as a next-generation approach to defining machine-readable specifications for RESTful APIs in web-based environments. The OGC is currently shifting towards interface specifications based on the OpenAPI 3.1 specification. That specification defines both the interface (interactions between the client and service) and the structure of data payloads (content) offered by that service. It is desirable to be able to efficiently model the service interface using UML and then automatically derive the physical expression of that interface (for example, as a JSON file) using Model Driven Engineering (MDE) techniques alongside the derivation of JSON Schema defining data content. A preliminary analysis and design based on the OGC API Features standard, parts 1 and 2, for sections other than for content schemas, is reported in section Generating OpenAPI definitions from an application schema in UML. + +All ShapeChange enhancements developed within the UGAS-2020 Pilot have been publicly released as a component of ShapeChange v2.10.0. https://shapechange.net has been updated to document the enhancements. + + + UML-to-GML Application Schema Pilot (UGAS-2020) Engineering Report + 20-012 + 20-012 + 2021-01-18 + Johannes Echterhoff + - 2014-12-02 + + + + 2017-02-23 + + 16-006r3 - 14-003 + + 16-006r3 + Volume 10: OGC CDB Implementation Guidance - WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data + + Volume 10: OGC CDB Implementation Guidance + This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. + Carl Reed - - - 05-099r2 - GML 3.1.1 simple dictionary profile - GML 3.1.1 simple dictionary profile - Arliss Whiteside - - - 05-099r2 - This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding simple dictionaries. This profile can be used without a GML Application Schema, and such use is assumed in this document. - - + - 2006-07-18 + sensorML Extension Package for ebRIM Application Profile + This document describes the mapping of description of sensors using SensorML specification 1.0 [OGC 07-000] to an ebRIM structure within an OGCTM Catalogue 2.0.2 (Corrigendum 2 Release) [OGC 07-006r1] implementing the CSW-ebRIM Registry Service – part 1: ebRIM profile of CSW [OGC 07-110r4]. +In addition this document contains the definition of a SensorML profile for Discovery which defines a minimum set of metadata to be provided within SensorML documents as well as the structure this data shall possess. This profile is based on the OGC OWS- 6 SensorML Profile for Discovery Engineering Report [OGC 09-033]. +It defines the way sensors metadata are organized and implemented in the Catalogue for discovery, retrieval and management. + 09-163r2 + sensorML Extension Package for ebRIM Application Profile + 09-163r2 + + + + 2010-04-02 + Fre&#769;de&#769;ric Houbie, Fabian Skive&#769;e, Simon Jirka + + - - + + + This Architecture Implementation Pilot, Phase 2 Engineering Report (AIP-2 ER) describes the practice of deploying, documenting, and registering contributed resources from the point of view of classes of GEOSS users who rely on GEOSS to support discovery and access to those resources. It emphasizes two paradigms for the GEOSS Common Infrastructure: 1) Service-oriented infrastructure for development of service-based community applications by technically advanced users; and 2) Content-oriented search facility and Web-based access mechanisms for end-users with a range of technical skills and domain knowledge. End-to-end here refers to the bidirectional connection between desired discovery practices and goals on the user end; and the required resource interfaces and documentation on the provider end. + End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2 + Josh Lieberman + + + 09-182r1 + 09-182r1 + End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2 + 2010-02-16 + - Documents of type OpenGIS Reference Model - - Documents of type OpenGIS Reference Model - Documents of type OpenGIS Reference Model + - - - The OpenSearch specification [NR3] is defined as a binding of the Abstract Protocol Definition (APD) for the searchRetrieve operation, one of a set of documents [NR4] for the OASIS Search Web Services (SWS) initiative [OR1]. The OpenSearch Description Document (OSDD) allows clients to retrieve service metadata from an OpenSearch implementation. The OSDD format allows the use of extensions that allow search engines to inform clients about specific and contextual query parameters and response formats. The OpenSearch extension for Earth Observation (EO) collections and products search is defined in [OR20]. The mandatory response format is based on Atom 1.0/XML [OR14]. - -JavaScript Object Notation (JSON) [NR1] has been gaining in popularity for encoding data in Web-based applications. JSON consists of sets of objects described by name/value pairs. GeoJSON [NR2] is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. This OGC standard describes a GeoJSON [NR2] and JSON-LD [NR15] encoding for OpenSearch Response documents. - -The GeoJSON encoding defined in this document is defined as a compaction[1] through a normative context, of the proposed JSON-LD encoding, with some extensions as presented in section 8 of this document. Therefore, the JSON-LD encoding can also be applied to other RDF [OR8] encodings including RDF/XML [OR11] and RDF Turtle [OR12]. - -Although this document makes no assumptions as to the “service” interfaces through which the Search Response is obtained and applies equally well to a Service Oriented Architecture as well as a Resource Oriented or RESTful architecture. The documented approach is mainly intended to be applied in combination with the following technologies: - -OGC OpenSearch extensions [OR19], [OR20], [NR3]. -GeoJSON is a format for encoding collections of simple geographical features along with their non-spatial attributes using JSON. GeoJSON objects may represent a geometry, a feature, or a collection of features. GeoJSON supports the following geometry types derived from the OGC Simple Features specification: Point, LineString, Polygon, MultiPoint, MultiLineString, MultiPolygon and GeometryCollection. Features in GeoJSON contain a geometry object and additional properties, and a feature collection represents a list of features. - -JSON is human readable and easily parseable. However, JSON is schemaless. JSON and GeoJSON documents do not include an explicit definition of the structure of the JSON objects contained in them. Therefore, this standard is based on a normative JSON-LD context which allows each property to be explicitly defined as a URI. Furthermore, the JSON encoding is defined using JSON Schema [OR24] which allows validation of instances against these schemas. - OpenSearch-EO GeoJSON(-LD) Response Encoding Standard - 17-047r1 + + + Topic 6 - The Coverage Type + + 00-106 + Topic 06 - The Coverage Type + + 2000-04-18 + + + Incomplete. This document normatively references parts of the previous version of AS Topic 6, document 00-106. Need to be updated to include Roswell Change Proposal (01-011), which includes 19123 and retains material from Topic 6, v6. + Cliff Kottman, Charles Roswell + 00-106 + + + CITE Summary Engineering Report + 08-084r1 + 08-084r1 - - + + OWS-5 CITE Summary Engineering Report + Jen Marcus - - OGC OpenSearch-EO GeoJSON(-LD) Response Encoding Standard - 2020-04-27 - 17-047r1 + This document summarizes work completed in the OWS5 Compliance & Interoperability Test & Evaluation thread. This document is applicable to the OGC Compliance Test Program. + 2008-08-20 + + + - - Carl Reed - 16-070r2 - Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage - This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features. + + + Geography Markup Language + 01-029 + - - 2017-02-23 - - 16-070r2 - - - Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage + Ron Lake + 2001-02-20 + + The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features. + Geography Markup Language + + 01-029 - - OGC OpenSearch Extension for Earth Observation - 13-026r8 - OpenSearch Extension for Earth Observation - 13-026r8 - - - - + + + 10-184 + 10-184 + OGC Fusion Standards Study, Phase 2 Engineering Report + OGC Fusion Standards Study, Phase 2 Engineering Report + 2010-12-13 - OGC® OpenSearch Extension for Earth Observation + + George Percivall + + This Engineering Report summarizes two phases of the Open Geospatial Consortium (OGC®) Fusion Standards study and of the fusion prototypes developed during the OWS-7 Testbed which occurred between the two study phases. Recommendations from the first phase of the study were implemented in OWS-7. Based upon the results of OWS-7, responses to two Requests for Information and a multi-day workshop, this report provides a cumulative set of recommendations for advancing fusion based on open standards. - - 2019-11-25 - 2016-12-16 - This document is the specification for the OpenSearch extension for Earth Observation collections and products search. - -This standard is intended to provide a very simple way to make queries to a repository that contains Earth Observation information and to allow syndication of repositories. - Pedro Gonçalves, Uwe Voges - - 2015-08-19 - Testbed 11 Engineering Report: Implementing Common Security Across the OGC Suite of Service Standards - 15-022 - This OGC Engineering Report (ER) focuses on describing Common Security for all OGC -Web Service Standards. This work was performed as part of the OGC Testbed 11 -activity. - - Andreas Matheus - + - - 15-022 + 12-026 + + 2012-04-18 + + Andreas Matheus + Architecture of an Access Management Federation for Spatial Data and Services in Germany - - OGC® Testbed 11 Engineering Report: Implementing Common Security Across the OGC Suite of Service Standards + + + Architecture of an Access Management Federation for Spatial Data and Services in Germany + 12-026 + An Access Management Federation (AMF) is a network of organizations that trust each other for the +means of sharing protected resources among each other. Worldwide, many academic AMFs are +available for the purpose of sharing information and services between academic institutions such +as Universities and Research Organizations. In the academia, some of the well known AMFs are UK +Access Management Federation (United Kingdom http://www.ukfederation.org.uk/), In Common +(USA http://www.incommon.org/) and DFN-AAI (Germany https://www.aai.dfn.de). - - Aviation: AIRM Derivation - 12-094 + + 2018-01-26 + + + + Robert Cass - Debbie Wilson, Clemens Portele + OGC Testbed-13: GeoPackage Engineering Report + 17-027 + Testbed-13: GeoPackage Engineering Report - 2013-02-05 - 12-094 - - OWS-9 Aviation: AIRM Derivation - - This report describes the architecture, rules and tools developed within the OWS-9 Aviation Thread AIRM Derivation task. These rules and tools were demonstrated by transforming the AIRM Meteorology package into a Weather Exchange Model (WXXM) and GML/JSON implementation schema. - + 17-027 + This Engineering Report details the processes and results related to generating GeoPackages developed to contain topographic vector features and supporting symbologies based on The National Map (TNM) product of the United States Geological Survey (USGS). - - - Change Request - O&M Part 1 - Move extensions to new namespace - 08-022r1 - - 08-022r1 - - Simon Cox + + This document describes a variety of Best Practices and Specification development guidance that the Members have discussed and approved over the years. These Best Practices have not been captured in other formal OGC documents other than meeting notes. + - - The XML Schema implementation of optional/informative elements of the Observation Schema was published in the om/1.0.0/extensions directory, in the same XML namespace as the base schema. Those OGC implementations that have a dependency on the Observation Schema (i.e. Sampling Features, SOS) <import> the “all-components” document om.xsd. However, the all-components stub-schema document “om.xsd” does not include the extensions. Thus, any application which requires one of the dependent OGC schemas (Sampling Features, SOS) may not access the Observation Schema Extensions, since the <import> of om.xsd clashes with any attempt to <import> om_extended.xsd. This problem is a consequence of an error in the modularization strategy for optional elements, combined with the rules for schema document resolution used by standard processing environments. - 2008-05-12 - Change Request - O&M Part 1 - Move extensions to new namespace + Carl Reed + Specification best practices + 06-135r1 + + + 06-135r1 + Specification best practices + + 2007-01-29 - - + + OGC® Testbed 11 GeoPackaging Engineering Report + 15-068r2 + Testbed 11 GeoPackaging Engineering Report + 15-068r2 + + Gobe Hobona;Roger Brackin + + Mobile location based service applications and users have an increasing need for access to geospatial data from any place in the world, including locations with limited or intermittent connectivity to communications networks. Maintaining consistency between copies of the same data held by different mobile devices can be a significant challenge when connectivity is limited or intermittent. This OGC Engineering Report describes the work carried out in OGC Testbed-11 in relation to the creation and synchronization of SQLite databases that conform to the OGC GeoPackage standard . This Engineering Report describes an approach for the use of various standards to achieve such synchronization. The document also presents the results and lessons learnt from the experimentation conducted in the Testbed. + + 2015-08-19 - - GeoPackage Encoding Standard - 12-128r17 - 12-128r17 - - - 2021-02-04 - Jeff Yutzler - OGC® GeoPackage Encoding Standard - This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. + - - + - OGC® Groundwater Interoperability Experiment FINAL REPORT - - - - 2011-03-22 - Boyan Brodaric, Nate Booth - This report describes the methods, results, issues and recommendations generated by the -Groundwater Interoperability Experiment (GWIE). As an activity of the OGC Hydrology -Domain Working Group (HDWG), the GWIE is designed to: (1) test the use of -WaterML2 with the SOS interface, and Groundwater ML (GWML) with the WFS -interface, (2) test compatibility with software clients, and (3) facilitate sharing of massive -volumes of sensor-based water level observations and related water well features across -the Canada and United States border. - Groundwater Interoperability Experiment FINAL REPORT - 10-194r3 - 10-194r3 + + + + 2006-01-12 + Jens Fitzke, Rob Atkinson + + Gazetteer Service Profile of a WFS + Provides web access to an authority for place names. Returns their associated feature representations + Gazetteer Service Profile of a WFS + 05-035r1 + 05-035r1 - - 2018-10-09 - The main goal of this CDS is to advance the standards and guidance that will allow production of high-quality digital maps over the web from existing vector data. - OGC Portrayal Concept Development Study - + + 20-015r2 + - - 17-094r1 - Portrayal Concept Development Study + + OGC Testbed-16: Machine Learning Engineering Report + This engineering report describes the work performed in the Machine Learning Thread of OGC’s Testbed-16 initiative. + +Previous OGC testbed tasks concerned with Machine Learning (ML) concentrated on the methods and apparatus of training models to produce high quality results. The work reported in this ER, however, focuses less on the accuracy of machine models and more on how the entire machine learning processing chain from discovering training data to visualizing the results of a ML model run can be integrated into a standards-based data infrastructure specifically based on OGC interface standards. + +The work performed in this thread consisted of: + +Training ML models; + +Deploying trained ML models; + +Making deployed ML models discoverable; + +Executing an ML model; + +Publishing the results from executing a ML model; + +Visualizing the results from running a ML model. + +At each step, the following OGC and related standards were integrated into the workflow to provide an infrastructure upon which the above activities were performed: + +OGC API - Features: Approved OGC Standard that provides API building blocks to create, retrieve, modify and query features on the Web. + +OGC API - Coverages: Draft OGC Standard that provides API building blocks to create, retrieve, modify and query coverages on the Web. + +OGC API - Records: Draft OGC Standard that provides API building block to create, modify and query catalogues on the Web. + +Application Deployment and Execution Service: Draft OGC Standard that provides API building blocks to deploy, execute and retrieve results of processes on the Web. + +MapML is a specification that was published by the Maps For HTML Community Group. It extends the base HTML map element to handle the display and editing of interactive geographic maps and map data without the need of special plugins or JavaScript libraries. The Design of MapML resolves a Web Platform gap by combining map and map data semantics into a hypermedia format that is syntactically and architecturally compatible with and derived from HTML. It provides a standardized way for declarative HTML content to communicate with custom spatial server software (which currently use HTTP APIs based on multiple queries and responses). It allows map and map data semantics to be either included in HTML directly, or referred to at arbitrary URLs that describe stand-alone layers of map content, including hyper-linked annotations to further content. + +Particular emphasis was placed on using services based on the emerging OGC API Framework suite of API building blocks. + OGC Testbed-16: Machine Learning Engineering Report + 20-015r2 - + 2021-02-15 + Panagiotis (Peter) A. Vretanos + - Jeff Yutzler, Rob Cass - 17-094r1 - + + An Extension Model to attach Points of Interest into IndoorGML + 20-054r1 + 20-054r1 + Kyoung-Sook Kim, Jiyeong Lee - 15-116 - AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper - + - - 15-116 - AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper - Giuseppe Conti, Fabio Roncato + 2021-01-19 + The scope of this discussion paper is to investigate types of Point of Interest (POI) data in indoor space and propose a conceptual model to harmonize the POI information with the IndoorGML core and navigation modules. In particular, this document focuses on the management of spatial (and non-spatial) history of indoor POI features. The paper covers the following scope: + +Points of Interest Feature Types; + +A Conceptual model to extend IndoorGML schema for indoor POI; and + +Use cases in home navigation and hospital facility management. + + An Extension Model to attach Points of Interest into IndoorGML - This document provides a proposal for a new O&M (Observations and Measurements) profile focused on Active and Healthy Ageing, called AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper). This document introduces the overall need for such a profile and it discusses the measures which have been identified. - 2016-04-26 - - Glenn Laughlin - 23-027 - 23-027 - OGC Federated Marine Spatial Data Infrastructure Pilot 2023 - Connecting Land and Sea for Global Awareness + + + OGC Testbed-14: BPMN Workflow Engineering Report + + - + 18-085 + BPMN Workflow Engineering Report + 2019-02-11 + 18-085 + + This Engineering Report (ER) presents the results of the D146 Business Process Modeling Notation (BPMN) Engine work item and provides a study covering technologies including Docker, Kubernetes and Cloud Foundry for Developer Operations (DevOps) processes and deployment orchestration. The document also provides the beginning of a best practices effort to assist implementers wishing to orchestrate OGC services using BPMN workflow engines. As with previous investigations into workflow engines, the implementation described within utilizes a helper class, which is a bespoke implementation of some of the best practices. Work in future testbeds on workflows should include a compelling use case to demonstrate the power of service orchestration. + Sam Meek + + + OWS-8 WCS 2.0 Earth Observation Application Profile Engineering Report + 11-096 + OWS-8 WCS 2.0 Earth Observation Application Profile Engineering Report + Stephan Meissl, Peter Baumann + 2011-11-23 + + + 11-096 + This Engineering Report describes progress on EO-WCS in the course of OWS-8. + + - Rising sea levels together with increasing storm surges are amongst the most challenging issues for coastal communities in the context of global warming. The retreating ice sheets of the Circumpolar Arctic are a key contributor to sea level rise with consequences felt around the world. + + + OGC Geoscience Markup Language 4.1 (GeoSciML) - with Corrigendum + + + 16-008r1 + 16-008r1 + Geoscience Markup Language 4.1 (GeoSciML) - with Corrigendum + GeoSciML is a model of geological features commonly described and portrayed in geological maps, cross sections, geological reports and databases. The model was developed by the IUGS CGI (Commission for the Management and Application of Geoscience Information) and version 4.1 is the first version officially submitted as an OGC standard. This specification describes a logical model and GML/XML encoding rules for the exchange of geological map data, geological time scales, boreholes, and metadata for laboratory analyses. It includes a Lite model, used for simple map-based applications; a basic model, aligned on INSPIRE, for basic data exchange; and an extended model to address more complex scenarios. -The Federated Marine Spatial Data Infrastructure (FMSDI) initiative is a key component of OGC and the Marine Domain Working Group. The program is designed to engage with stakeholders from the marine dataspace to identify opportunities to assist, improve, and scale out core business processes complemented by the OGC suite of standards and best practices. The FMSDI-2023 pilot represents the fourth phase of the program with a focus on the interface between land and sea. A primary goal of this pilot is to advance the FMSDI concept to increasing threats posed by climate change. +The specification also provides patterns, profiles (most notably of Observations and Measurements - ISO19156), and best practices to deal with common geoscience use cases. -The project is divided into three threads, each with application to distinct geographies. + + + GeoSciML Modeling Team + + 2017-01-31 + + + + + + Web Feature Service Implementation Specification with Corrigendum + 04-094r1 + + + 2016-10-26 + 04-094r1 + OGC Web Feature Service Implementation Specification with Corrigendum + + + Panagiotis A. Vretanos + + The OGC Web Map Service allows a client to overlay map images for display served from multiple Web Map Services on the Internet. In a similar fashion, the OGC Web Feature Service allows a client to retrieve and update geospatial data encoded in Geography Markup Language (GML) from multiple Web Feature Services. -Thread 1: Digital Twin of Land and Sea Interfaces — Singapore -With approximately 30% of Singapore’s land mass being less than 5m above sea level, the seamless integration of land and marine data is integral to Singapore’s focus on coastal protection and climate resilience. The management of land and water is separated organizationally between the Singapore Land Authority (SLA) and the Maritime & Port Authority (MPA), respectively. Each agency is responsible for data assets specific to their jurisdiction presenting a challenge for cross-organizational concerns. This theme addresses the geospatial integration requirements through the development of a multi-dimensional Digital Twin of the Singapore coastline. +The requirements for a Web Feature Service are: -Thread 2: Digital Arctic Connecting Land and Sea — Canada -This thread addresses the data integration issues in the context of Digital Twins for the Canadian Arctic. With the loss of sea ice, continuing ocean warming, stronger winds and currents, and accelerated shoreline erosion affecting Arctic communities, efficient data usage and analysis is of the utmost importance for Canada. -Figure 1 +The interfaces must be defined in XML. +GML must be used to express features within the interface. +At a minimum a WFS must be able to present features using GML. +The predicate or filter language will be defined in XML and be derived from CQL as defined in the OpenGIS Catalogue Interface Implementation Specification. +The datastore used to store geographic features should be opaque to client applications and their only view of the data should be through the WFS interface. + The use of a subset of XPath expressions for referencing properties. + + + + + + + Samantha Lavender, Andrew Lavender + OGC Disaster Pilot: Provider Readiness Guide + 21-074r2 + 2024-04-26 + Disasters are geographic events and, therefore, geospatial information, tools, and applications have the potential to support the management of, and response to, disaster scenarios to save lives and limit damage. -Thread 3: Integrating Land & Sea for Various Use Cases — Caribbean -This thread investigates how data developed primarily for navigation at sea can be used to better understand the opportunities in the Caribbean to support local capacity building and the application of marine data in expanded sea-land contexts. +The use of geospatial data varies significantly across disaster and emergency communities, making the exploitation of geospatial information across a community more difficult. The issue is particularly noticeable when sharing between different organizations involved in disaster response. -Approach +This difficulty can be mitigated by establishing the right processes to enable data to be shared smoothly and efficiently within a disaster and emergency community. To do this requires the right partnerships, policies, standards, architecture, and technologies to be in place before the disaster strikes. Having such a set-up will enable the technological and human capabilities to quickly find, access, share, integrate, and visualize a range of actionable geospatial information, and provide this rapidly to disaster response managers and first responders. -The FMSDI 2023 pilot is managed through the OGC Collaborative Solutions and Innovation (COSI) Program. Each thread is a distinct project with a set of participants tackling specific use cases and scenarios important to the respective project sponsor. +For over 20 years, the Open Geospatial Consortium (OGC) has been working on the challenges of information sharing for emergency and disaster planning, management, and response. In Disaster Pilot 23 (DP23) the aims were to: -Weekly project meetings are scheduled to encourage collaboration between the participants and sponsors and provide checkpoints to ensure the project scope meets the sponsor’s expectations. +develop flexible, scalable, timely and resilient information data workflows to support critical disaster management decisions, enabling stakeholder collaboration; and +provide applications and visualization tools to promote the wider understanding of how geospatial data can support emergency and disaster communities. +The Disaster Pilot Provider Guide describes the technical requirements, data structures, and operational standards required to implement the data flows or tools developed in DP23 and Disaster Pilot 21 (DP21) where participants have worked on disaster scenarios relating to the following. -The FMSDI 2023 pilot also features a series of persistent demonstrators as one of its outputs. These demonstrators are workflows and applications that stakeholders can access for outreach, testing, and experimentation purposes. The demonstrators will be available even after the project is completed and are therefore referenced as persistent, but will only be available until December 2024. These demonstrators showcase how geospatial data can be used in an operational context or highlight the gaps in the resources available online, including data sources, metadata, access processes, and standards. As each participant has a unique solution platform, each has taken different approaches, all of which are available for review by stakeholders. Security concerns, such as authentication and authorization, are unique to each participant and have been communicated to stakeholders and participant contacts. For further details and access to the demonstrators, please refer to the link provided. +Droughts +Wildland Fires +Flooding +Landslides +Health & Earth Observation Data for Pandemic Response +Case Studies have focused on the hazards of drought in Manitoba, Canada; wildland fires in the western United States; flooding in the Red River basin, Canada; landslides and flooding in Peru; and pandemic response in Louisiana, United States. The participants have developed a series of data specific workflows to generate either Analysis Ready Datasets (ARD) or Decision Ready Indicators (DRI) alongside a number of tools and applications to support data discovery, collection, or visualization. -Common across the three threads is the application of the OGC FAIR principles — Findable, Accessible, Interoperable, and Reusable. Underpinning the use of the FAIR principles is the role of the core OGC Standards and Best Practices. Previous work products related to FMSDI form the core information model while the OGC standards, enhanced through the alignment and support of industry standards such as the IHO S-100 standard, address many of the requirements central to each thread. +Annex A describes the tools and applications developed within the Pilots along with technical details and the benefits offered similar to the data flows. The Guide finishes with details of future possibilities and where the Disaster Pilot initiatives could focus next. Annexes B to E give descriptions of the data flows developed, including technical details of input data, processing and transformations undertaken, standards applied, and outputs produced with details of the aspect of disaster management or response supported, benefits offered, and the type of decisions assisted with. -Attention is drawn to the possibility that some of the elements of this document may be the subject of patent rights. The Open Geospatial Consortium shall not be held responsible for identifying any or all such patent rights. +The Provider Guide is one of three Guides produced within DP23 together with the User Guide and the Operational Capacity Guide. While the Guides are separate individual documents, the Provider and User Guides work together, mirroring each other in terms of structure. The Operational Capacity Guide is a stand-alone document effectively underpinning the other two. -Recipients of this document are requested to submit, with their comments, notification of any relevant patent claims or other intellectual property rights of which the recipients may be aware that might be infringed by any implementation of the standard set forth in this document, and to provide supporting documentation. - - OGC Federated Marine Spatial Data Infrastructure Pilot 2023 - Connecting Land and Sea for Global Awareness - 2024-04-26 + + 21-074r2 + + + OGC Disaster Pilot: Provider Readiness Guide + - + + KML 2.2 Reference - An OGC Best Practice + 07-113r1 + + 07-113r1 + KML 2.2 Reference - An OGC Best Practice + - OGC Testbed-15: Scaling Units of Work (EOC, Scale, SEED) + Google, Galdos + + 2007-11-23 + KML is a file format used to display geographic data in an Earth browser, such as Google Earth, Google Maps, and Google Maps for Mobile. KML uses a tag-based structure with nested elements and attributes and is based on the XML standard. + + + + + 08-079 + OWS5: OGC Web feature service, core and extensions + This standard specifies the behavior of a service that provides transactions on and access to geographic features in a manner independent of the underlying data store. It specifies discovery operations, query operations and transaction operations. Discovery operations allow the service to be interrogated to determine its capabilities and to retrieve the application schema that defines the feature types that the service offers. Retrieval operations allow features to be retrieved from the opaque underlying data store based upon constraints on spatial and non-spatial feature properties defined by the client. Transaction operations allow features to be created, changed and deleted from the opaque underlying data store. + 2008-09-12 + 08-079 + John Herring + + - 19-022r1 - OGC Testbed-15: Scaling Units of Work (EOC, Scale, SEED) - - This OGC Testbed-15 Engineering Report (ER) presents a thorough analysis of the work produced by the Earth Observation Clouds (EOC) threads in OGC Testbeds 13 and 14 in relation to the Scale environment. Scale provides management of automated processing on a cluster of machines and the SEED specification to aid in the discovery and consumption of a discrete unit of work contained within a Docker image. Scale and SEED were both developed for the National Geospatial Intelligence Agency (NGA) of the United States. - -The ER attempts to explain how the OGC Testbed-13 and OGC Testbed-14 research results of bringing applications/users to the data relate to Scale and SEED. - -Chiefly, while comparing the two approaches, the report identifies and describes: - -Opportunities for harmonization or standardization; - -Features which must remain separate and the rationale for this; - -The hard problems which will require additional work; and - -Opportunities which should be examined in future initiatives. + + + + OWS5: OGC Web feature service, core and extensions + + + OGC Testbed 17: MASBUS Integration Engineering Report + 21-029 + 2022-03-31 + + This OGC Testbed 17 Engineering Report (ER) analyses the Measures and Signatures Intelligence Enterprise Service Bus (MASBUS) pilot software and the efforts to integrate with OGC SensorThings API resources. After introducing MASBUS, a server implementation is designed to digest sensor data and demonstrate the SensorThings MQTT (Message Queuing Telemetry Transport) extension of the MASBUS software. To show the SensorThings MQTT extension of the MASBUS software, a MASBUS client implementation is also presented. This ER discusses the results of the MASBUS integration, including all lessons learned from the experiments completed during the OGC Testbed 17 Sensor Integration thread and concludes with a set of optimum recommendations. -For developers, the ER constitutes a technical reference supporting the comparison of the two approaches, thereby enabling developers to make informed choices, understand trade-offs, identify relevant standards and clarify misunderstandings. - 2020-01-08 + + + + + + Sara Saeedi + OGC Testbed 17: MASBUS Integration Engineering Report + 21-029 - - - Alexander Lais - 19-022r1 - + + 16-046r1 + Testbed-12 Semantic Enablement Engineering Report + 2017-05-12 + + + + Martin Klopfer + + Testbed-12 Semantic Enablement Engineering Report + + 16-046r1 + + The requirement for capabilities supporting semantic understanding and reasoning in geospatial intelligence (GEOINT) is an all-encompassing paradigm shift from the past. Standards play a critical role in ensuring this is accomplished in a consistent and repeatable manner. Semantic standards and services supporting semantic capabilities are at a relatively early stage of development. Interoperability between semantic standards for encoding relationships and Web based services for discovery, access, retrieval and visualization of those relationships requires more testing and evaluation. This engineering report (ER) highlights the key findings and discussions from Testbed-12 that enable semantic interoperability, including semantic mediation, schema registries, and SPARQL endpoints. It references key findings from the Semantic Portrayal ER and helps to understand the current OGC discussion on semantics in general. + + + Testbed-13: MapML Engineering Report + 17-019 + + OGC Testbed-13: MapML Engineering Report + + Joan Maso + + + 17-019 - 2008-10-10 - 08-133 - Sensor Event Service Interface Specification - - - - The Sensor Event Service (SES) provides operations to register sensors at the service application and let clients subscribe for observations available at the service. The service performs filtering of sensor data (streams) based upon the filter criteria defined in these subscriptions. Filters can be applied on single observations but also on observation streams, potentially aggregating observations into higher-level information (which itself can be regarded as observation data). Whenever matches are discovered, a notification is sent to the subscriber, using asynchronous, push-based communication mechanisms. - OpenGIS® Sensor Event Service Interface Specification - 08-133 - Johannes Echterhoff, Thomas Everding - + This Engineering Report discusses the approach of Map Markup Language (MapML) and Map for HyperText Markup Language (Map4HTML) described in: https://github.com/Maps4HTML and supported by the community in https://www.w3.org/community/maps4html/. The objective of MapML is to define a hypermedia type for geospatial maps on the web that can be embedded in HyperText Markup Language (HTML) pages. MapML is needed because while Web browsers implement HTML and Scalable Vector Graphics (SVG), including the <map> element, those implementations do not meet the requirements of the broader Web mapping community. The semantics of the HTML map element are incomplete or insufficient relative to modern Web maps and mapping in general. Currently, robust web maps are implemented by a variety of non-standard technologies. Web maps do not work without script support, making their creation a job beyond the realm of beginners' skill sets. In order to improve collaboration and integration of the mapping and Web communities, it is desirable to enhance or augment the functionality of the <map> element in HTML to include the accessible user interface functions of modern web maps (e.g. panning, zooming, searching for, and zooming to, styling, identifying features’ properties, etc.), while maintaining a simple, declarative, accessible interface for HTML authors. + +The objective of this Engineering Report is to explore how MapML can be harmonized with the OGC standards mainstream and contribute to the progress of the specification avoiding unnecessary duplication. In particular, the ER proposes Web Map Service (WMS) or Web Map Tile Service (WMTS) as services that can be used to deliver MapML documents with small modifications. + +Another consideration on the ER is the inclusion of the time dimension and directions operation in MapML. + 2018-01-11 - - - - 11-145 - George Percivall - 11-145 - Cyberarchitecture for Geosciences White Paper - 2014-05-20 - Cyberarchitecture for Geosciences White Paper - The National Science Foundation (NSF) is developing EarthCube” - Towards a National Data Infrastructure for Earth System Science . In a new partnership between GEO and the NSF Office of Cyberinfrastructure, NSF seeks transformative concepts and approaches to create a sustained, integrated data management infrastructure spanning the Geosciences. Meeting the challenges in geoscience research requires innovation and paradigm shifts in cyberinfrastructure. Information technology must advance to meet the emerging approaches to science. A cyber-architecture identifies repeatable patterns, reusable components, and open standards that provide starting point for innovative developments. -This white paper was written by Open Geospatial Consortium (OGC) members and associates to contribute to development of the NSF EarthCube. This document does not represent an official position of the OGC. However, the discussions in this document could very well lead to NSF developments and subsequent OGC documents. Recipients of this document are invited to reply to the authors’ with notification of any relevant patent rights of which they are aware and to provide supporting documentation. - - + + + + 09-012 + OWS-6 Symbology-Encoding Harmonization ER - + + This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the harmonization of OGC Styled Layer Descriptor (SLD) and Symbology Encoding (SE) symbology formats with ISO 19117 symbology format, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology. + 2009-08-17 + Craig Bruce + 09-012 + OWS-6 Symbology-Encoding Harmonization ER + - - + + + Testbed-11 High Resolution Flood Information Scenario Engineering Report + 15-046r2 - This OGC GML in JPEG 2000 (GMLJP2) Encoding Standard defines how the OGC/ISO Geography Markup Language (GML) standard is used within JPEG 2000 images and other gridded coverage data for adding geospatial content to imagery. Specifically, this OGC standard defines requirements for the encoding and decoding of JPEG 2000 images and other gridded coverage data that contain XML documents that use GML and GML-based schema. -This document defines the use of GML within the XML boxes of the JP2 and JPX file format for JPEG 2000 (extending the JP2 file format, as specified in [ISO 15444-1] and [ISO 15444-2] in Annexes M and N). Further, an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations is specified. The document also specifies the encoding and packaging rules for GML use in JPEG 2000. - - 08-085r8 - - Lucio Colaiacomo, Joan Masó, Emmanuel Devys, Eric Hirschorn - OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard - GML in JPEG 2000 (GMLJP2) Encoding Standard - 08-085r8 - 2018-08-27 - - + This OGC Engineering Report describes the high-resolution flood information scenario carried out under the Urban Climate Resilience Thread of the Testbed 11 Initiative. The scenario was developed for two areas of interest: the San Francisco Bay Area and in Mozambique. The scenarios for these two locations demonstrate the interoperation and capabilities of open geospatial standards in supporting data and processing services. The prototype High Resolution Flood Information System addresses access and control of simulation models and high-resolution data in an open, worldwide, collaborative Web environment. The scenarios were designed to help testbed participants examine the feasibility and capability of using existing OGC geospatial Web Service standards in supporting the on-demand, dynamic serving of flood information from models with forecasting capacity. Change requests to OGC standards have also been identified through the Testbed activity. + OGC® Testbed-11 High Resolution Flood Information Scenario Engineering Report + 2016-01-18 + Eugene G. Yu, Liping Di, Ranjay Shrestha + 15-046r2 + + + - - - - Panagiotis (Peter) A. Vretanos, Clemens Portele + + - 21-065r2 - - Common Query Language (CQL2) - 21-065r2 - Common Query Language (CQL2) - 2024-07-26 - + 03-003r10 + + Level 0 Profile of GML3 for WFS + 2004-05-10 + + Peter Vretanos + + + *RETIRED* This is a GML application profile known as Level 0 - also known as Simple GML. + 03-003r10 + Level 0 Profile of GML3 for WFS + + + + + Carl Reed, Tamrat Belayneh - A fundamental operation performed on a collection of features is that of filtering in order to obtain a subset of the data which contains feature instances that satisfy some filtering criteria. This document specifies - -A filter grammar called Common Query Language (CQL2); - -Two encodings for CQL2 - a text and a JSON encoding. - -The Common Query Language (CQL2) defined in this document is a generic filter grammar that can be used to specify how resource instances in a source collection of any item type, including features, can be filtered to identify a results set. Typically, CQL2 is used in query operations to identify the subset of resources, such as features, that should be included in a response document. However, CQL2 can also be used in other operations, such as updates, to identify the subset of resources that should be affected by an operation. - -Each resource instance in the source collection is evaluated against a filtering expression. The filter expression always evaluates to true, false or null. If the expression evaluates to true, the resource instance satisfies the expression and is marked as being in the result set. If the overall filter expression evaluates to false or null, the data instance is not in the result set. Thus, the net effect of evaluating a filter expression is a set of resources that satisfy the predicates in the expression. + OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification + + + + 2017-09-05 + 17-014r5 + Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification + 17-014r5 + A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files. -The Common Query Language and its text encoding are not new, but this is the first time that the language is formally specified. The Common Query Language with the acronym CQL was originally created as a text encoding for use with implementations of the OGC Catalogue Service Implementation Specification. The language is based on the capabilities in the OGC Filter Encoding Standard, which was originally part of the Web Feature Service (WFS) Standard. + -The Common Query Language as specified in this document is a revision of this earlier version. While the language design including the classification of operators are consistent with the earlier specification, there have been a number of changes and existing implementations of CQL will need to be updated to process filter expressions specified by this document. This document therefore uses the acronym CQL2 to refer to the current version of the Common Query Language. +The delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3d datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types. - + + Liping Di, Eugene G. Yu, Md Shahinoor Rahman, Ranjay Shrestha - OGC Testbed-17: Attracting Developers: Lowering the entry barrier for implementing OGC Web APIs - - 21-019 - OGC Testbed-17: Attracting Developers: Lowering the entry barrier for implementing OGC Web APIs - This OGC Testbed 17 Engineering Report (ER) documents the work completed in the “Attracting Developers: Lowering the entry hurdle for OGC Web API experiments” task. - -OGC Web API Standards are being developed to make it easy to provide geospatial data over the web. These standards provide a certain level of formality to ensure high levels of interoperability. They rigorously define requirements and rules to reduce room for error during interpretation. This rigor sometimes makes the standard documents difficult to read and hence implement. Rather than direct examination of a standard, the majority of developers often prefer to start with implementation guidelines, sample code, and best practice documentation and then refer to the standards document for guidance and clarity. - -The Testbed-17 (TB-17) API task served as a foundation for further development and exploration and delivers knowledge necessary for agile development, deployment, and executing OGC Standards-based applications following a “How-To” philosophy with hands-on experiments, examples, and instructions. - - - 21-019 - - - 2022-01-21 - - Aleksandar Balaban + Testbed-12 WPS ISO Data Quality Service Profile Engineering Report + 16-041r1 + + + 2017-06-30 + + This Data Quality Engineering Report describes data quality handling requirements, challenges and solutions. One focus is on data quality in general that needs to be communicated from one service to another. In addition, it discusses WPS data quality solutions. The ultimate goal is for it to be nominated as a WPS ISO Data Quality Service Profile. ISO 19139 is used as the base to encode the data quality. WPS and workflows are used to streamline and standardize the process of data quality assurance and quality control. The main topics include: (1) generalized summary and description of the design and best practices for analyzing data quality of all feature data sources used in the Citizen Observatory WEB (COBWEB) project, (2) solutions and recommendations for enabling provenance of data quality transparent to end users when the data is processed through a WPS, (3) best practices and recommendations for designing and prototyping the WPS profile to support data quality service conformant to the NSG Metadata Framework, and (4) general solution for data quality fit for both raster-based imageries and vector-based features. + + 16-041r1 + Testbed-12 WPS ISO Data Quality Service Profile Engineering Report - - 02-112 - 2001-09-14 - Same as ISO 19119 - Topic 12 - The OpenGIS Service Architecture - - ISO - - + + 2020-02-06 + 19-018 + OGC Testbed-15: Open Portrayal Framework Engineering Report + 19-018 + Martin Klopfer + OGC Testbed-15: Open Portrayal Framework Engineering Report + + This Engineering Report (ER) describes the OGC Testbed-15 Open Portrayal Framework (OPF) Thread requirements, scenario, high-level architecture, and solutions. Main topics addressed in the OPF Thread include style changing and sharing, converting style encodings, client- / server-side rendering of vector- and raster data and data provision in denied, disrupted, intermittent, and limited bandwidth (DDIL) infrastructure situations. The work in the OPF Thread was focused on an OGC Application Programming Interface (API) oriented approach. + - Topic 12 - The OpenGIS Service Architecture - 02-112 + - - EO Application Profile for CSW 2.0 - 06-079r1 - - - - 06-079r1 - Explains how Catalogue Services based on the HMA (Heterogeneous Earth Observation Missions Accessibility) Application Profile for the OGC Catalogue Services Specification v2.0.1 [OGC 04-021r3] are organized and implemented for the discovery, retrieval and management of Earth Observation products metadata. - - EO Application Profile for CSW 2.0 + + 14-012r1 + + OGC RESTful encoding of OGC Sensor Planning Service for Earth Observation satellite Tasking + This OGC® Best Practices document specifies the interfaces, bindings, requirements and conformance classes that enable complete workflows for the tasking of sensor planning services for Earth Observation (EO) satellites. In fact it provides the interfaces for supporting the following EO sensor planning scenarios: +• Planning future acquisitions with feasibility study, +• Direct planning of future acquisitions, +• Reservation of planning for future acquisitions. +This specification includes a comprehensive list of sensor options and tasking options derived from the parent specification OGC 10-135 [NR22] which gathered inputs from several Satellite Agencies and Operators: +• ESA +• EUMETSAT +• CNES +• DLR +• CSA +• Airbus Defence & Space +This document is based on the standard: +OGC 10-135, Sensor Planning Service Interface Standard 2.0 Earth Observation +Satellite Tasking Extension, version 2.0. 2011. + +which was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [OR1] and related projects. +With respect to the parent specification this Best Practice document proposes the following changes: +• Replaces SOAP with REST for service encoding. This affects not only the way the service is implemented but also the way the standard is presented and described. In fact, basing the standard on REST implies that the service has to be described in terms of resources and methods applied on them whilst in SOAP services, the description is focusing on operations and in fact the OGC 10-135[NR22] is structured in Web Service operations. +• Usage of OpenSearch Description Documents as an alternate method for describing sensors and tasking Options (§7.3.2). This specification uses the sensors and tasking options model already described in the OGC 10-135 [NR22] standard but defines an additional method for describing sensors and tasking options within OpenSearch Description Documents based on the OGC 13-039 [NR23]. Actually this part of the specification refers to the OpenSearch Extension for Earth Observation Satellite Tasking. +&#8195; + + Nicolas FANJEAU, Sebastian ULRICH + - 2006-06-06 - Marc Gilles + + + 14-012r1 + RESTful encoding of OGC Sensor Planning Service for Earth Observation satellite Tasking + 2014-07-17 - - Documents of type Recommendation Paper - deprecated - - - - - - - - - - - - - - Documents of type Recommendation Paper - deprecated - Documents of type Recommendation Paper - deprecated - + + 19-022r1 + Alexander Lais + + + OGC Testbed-15: Scaling Units of Work (EOC, Scale, SEED) - - - Modernizing SDI: Enabling Data Interoperability for Regional Assessments and Cumulative Effects CDS - - 21-013 - Modernizing SDI: Enabling Data Interoperability for Regional Assessments and Cumulative Effects CDS - This engineering report (ER) presents the results of a Concept Development Study (CDS) on Modernizing Spatial Data Infrastructure (SDI), sponsored by Natural Resources Canada, executed by the Open Geospatial Consortium (OGC). The focus of this study was to understand how to best support the modernization of SDI(s) by enabling increased data interoperability for Regional Assessments (RA) and Cumulative Effects (CE), to advance the understanding of stakeholder issues, and serve stakeholders’ needs in these contexts. The study was completed through stakeholder engagements including an open Request for Information (RFI) that gathered external international positions and opinions on the optimal setup and design of a modernized SDI. In addition, a stakeholder Modernizing SDI Workshop was also employed providing in depth information on requirements and issues related to stakeholders, architecture, data, and standards of current and future SDI. + + 2020-01-08 + 19-022r1 + OGC Testbed-15: Scaling Units of Work (EOC, Scale, SEED) + + This OGC Testbed-15 Engineering Report (ER) presents a thorough analysis of the work produced by the Earth Observation Clouds (EOC) threads in OGC Testbeds 13 and 14 in relation to the Scale environment. Scale provides management of automated processing on a cluster of machines and the SEED specification to aid in the discovery and consumption of a discrete unit of work contained within a Docker image. Scale and SEED were both developed for the National Geospatial Intelligence Agency (NGA) of the United States. -The RFI and workshop also gathered information and provided insight on the current state of SDIs to better support governments, agencies, non-governmental organizations and citizens, unlocking the full societal and economic potential of the wealth of data at national, regional and/or local levels. +The ER attempts to explain how the OGC Testbed-13 and OGC Testbed-14 research results of bringing applications/users to the data relate to Scale and SEED. -The ER presents an analysis of the RFI and Modernizing SDI Workshop responses and interactions, providing in-depth information on requirements and issues related to stakeholders, architecture, data, standards of current and possible future SDI modernization. All RFI and workshop responses will contribute to SDI modernization efforts moving forward and help to assess interoperability, availability and usability of geospatial Web services and tools across different types of spatial data uses. In addition, the report identifies gaps, and defines core components of a possible future SDI. +Chiefly, while comparing the two approaches, the report identifies and describes: + +Opportunities for harmonization or standardization; + +Features which must remain separate and the rationale for this; + +The hard problems which will require additional work; and + +Opportunities which should be examined in future initiatives. -The outflow of this report may be used to help define reference use-cases and scenarios for possible future research and follow-on OGC Innovation Program activities. - - +For developers, the ER constitutes a technical reference supporting the comparison of the two approaches, thereby enabling developers to make informed choices, understand trade-offs, identify relevant standards and clarify misunderstandings. - 21-013 - 2021-05-27 - - - Robert Thomas, Josh Lieberman - - - - - - - - Documents of type Policy Document - Documents of type Policy Document - Documents of type Policy Document - + + + + Benjamin Hagedorn, Simon Thum, Thorsten Reitz, Voker Coors, Ralf Gutbell + 2017-09-13 + + 15-001r4 + + + 3D Portrayal Service 1.0 + 15-001r4 + OGC® 3D Portrayal Service 1.0 + The 3D Portrayal Service Standard is a geospatial 3D content delivery implementation specification. It focuses on what is to be delivered in which manner to enable interoperable 3D portrayal. + +It does not define or endorse particular content transmission formats, but specifies how geospatial 3D content is described, selected, and delivered. It does not prescribe how aforementioned content is to be organized and represented, but provides a framework to determine whether 3D content is interoperable at the content representation level. More details are available in Design of this standard. - + + NetCDF Uncertainty Conventions + + NetCDF Uncertainty Conventions + 11-163 + Lorenzo Bigagli, StefanoNativi + - - 2000-04-24 - - - Topic 15 - Image Exploitation Services - 00-115 - Describes the categories and taxonomy of image exploitation services needed to support the use of images and certain related coverage types. + This Discussion Paperproposes a set of conventions for managing uncertainty information within the netCDF3 data model and format: the NetCDF Uncertainty Conventions (NetCDF-U). + 11-163 - 00-115 - Topic 15 - Image Exploitation Services - Cliff Kottman, Arliss Whiteside - + + 2013-01-17 + - - OGC India Plugfest - 2017 (OIP-2017) Engineering Report - - OGC India Plugfest - 2017 (OIP-2017) Engineering Report - 18-009 - + + 14-073r1 - P S Acharya, Scott Simmons, A Kaushal, M K Munshi - - 2020-02-24 + 14-073r1 + Aircraft Access to SWIM (AAtS) Harmonization Architecture Report + 2014-11-03 - - The Open Geospatial Consortium (OGC) and the Department of Science & Technology (DST) under the Government of India conducted the OGC India Plugfest 2017 (OIP-2017). The OIP-2017 was targeted at enhancing the interoperability among geospatial products and web services based on OGC standards within the Indian Geospatial Information (GI) community. The successful conclusion of OIP-2017 will assist National Spatial Data Infrastructure (NSDI) under DST to provide guidance on best practices using OGC standards for development of applications in several important & flagship schemes/programmes of the Government such as Smart Cities, Atal Mission for Rejuvenation through Urban Trasnformation (AMRUT); National Land Records Moderinisation Programme (NLRMP); Clean India (Swatchh Bharat – Urban & Rural); National Mission on Clean Ganga; Compensatory Afforestation Fund Management & Planning Authority (CAMPA); State SDIs; Digital India, and others. -This engineering report written jointly by OGC and DST is addressed to both the domestic (Indian) and international audiences. -OIP-2017 was funded by the OGC India Foundation with supporting OGC staff resources from the OGC Innovation Program. - - 18-009 - - - - - Web Feature Service (Transactional) - Web Feature Service - - - - - - Web Feature Service (Transactional) - 02-058 - Web Feature Service - 2002-05-17 - 02-058 - Peter Vretanos - The purpose of the Web Feature Server Interface Specification (WFS) is to describe data manipulation operations on OpenGIS - - - Publishing and Using Earth Observation Data with the RDF Data Cube and the Discrete Global Grid System - 16-125 - - Dmitry Brizhinev, Sam Toyer, Kerry Taylor - + OGC® Aircraft Access to SWIM (AAtS) Harmonization Architecture Report + George Wilber, Johannes Echterhoff, Matt de Ris, Joshua Lieberman - - 16-125 - 2020-09-17 - This document describes how dense geospatial raster data can be represented using the W3C RDF Data Cube (QB) ontology [vocab-data-cube] in concert with other popular ontologies including the W3C/OGC Semantic Sensor Network ontology (SSN) [vocab-ssn], the W3C/OGC Time ontology (Time) [owl-time], the W3C Simple Knowledge Organisation System (SKOS) [skos-reference], W3C PROV-O [prov-o] and the W3C/OGC QB4ST [qb4st]. It offers general methods supported by worked examples that focus on Earth observation imagery. Current triple stores, as the default database architecture for RDF, are not suitable for storing voluminous data like gridded coverages derived from Landsat satellite sensors. However we show here how SPARQL queries can be served through an OGC Discrete Global Grid System for observational data, coupled with a triple store for observational metadata. While the approach may also be suitable for other forms of coverage, we leave the application to such data as an exercise for the reader. - Publishing and Using Earth Observation Data with the RDF Data Cube and the Discrete Global Grid System - + + This OGC® document describes the Aircraft Access to SWIM (AAtS) harmonization +architecture developed by a team funded by the FAA and led by the Open Geospatial +Consortium (OGC). - - 09-035 - Rüdiger Gartmann, Lewis Leinenweber - - 09-035 - OWS-6 Security Engineering Report - OWS-6 Security Engineering Report - + + Building Energy Mapping and Analytics: Concept Development Study Report + + 20-083r2 + Building Energy Mapping and Analytics: Concept Development Study Report + This report details the results of the OGC Building Energy Mapping and Analysis Concept Development Study (BEMA CDS). Sponsored by NRCan and drawing on numerous previous studies, the CDS released a Request for Information on building energy data and applications. The responses were presented and validated in 3 public workshops and form the basis for an Energy SDI notional architecture. + + 2021-05-10 + - - This Engineering Report describes work accomplished during the OGC Web Services Testbed, Phase 6 (OWS 6) to investigate and implement security measures for OGC web services. This work was undertaken to address requirements stated in the OWS-6 RFQ/CFP originating from a number of sponsors, from OGC staff, and from OGC members. - 2009-10-09 + 20-083r2 + Josh Lieberman - - 18-032r2 - + + 2022-01-21 - - This report enhances the understanding of the relationships between application schemas based on the Unified Modeling Language (UML) and ontologies based on the Web Ontology Language (OWL). The work documented in this report provides and improves tools and principled techniques for the development of Resource Description Framework (RDF) based schemas from ISO 19109-conformant application schemas. - Johannes Echterhoff - + Aleksandar Balaban, Andreas Matheus + OGC Testbed-17: Data Centric Security ER + 21-020r1 + OGC Testbed-17: Data Centric Security ER + + + This OGC Testbed-17 Engineering Report (ER) documents the enhancement of applying Data Centric Security (DCS) to OGC API Features, OGC API Maps (draft), and OGC API Tiles (draft). + +As organizations move to the cloud, it is important to incorporate DCS into the design of the new cloud infrastructure, enabling the use of cloud computing, even for sensitive geospatial data sets. The ER documents the applicability of Zero Trust through a Data Centric security approach (DCS) when applied to vector and binary geospatial data sets (Maps, Tiles, GeoPackage containers) and OGC APIs. + +The defined architecture extends the typical Zero Trust Domain component by introducing a Key Management System (KMS) to support key registration and the management of access conditions for key retrieval. The prototype implementations (DCS Client, DCS Server and KMS) demonstrate how to request encrypted geospatial data as JSON for encrypted vector data, HTTP Multipart for encrypted map data or GeoPackage with encrypted content; how to obtain decryption key(s) and how to decrypt and display the protected data in a mobile application on Android. + 21-020r1 - 2019-02-04 - 18-032r2 - Application Schema-based Ontology Development Engineering Report - OGC Testbed-14: Application Schema-based Ontology Development Engineering Report + - + + + MetOcean Application profile for WCS2.1: Part 0 MetOcean Metadata + 15-045r7 + 2021-03-22 + Peter Trevelyan, Paul Hershberg, Steve Olson + OGC MetOcean Application profile for WCS2.1: Part 0 MetOcean Metadata + The purpose of this Met Ocean profile of WCS2.1 is to define the metadata returned in the response documents resulting from the WCS2.1 operations: GetCapabilities, and DescribeCoverage; for use within the meteorological and oceanographic communities. It also defines the new operation DescribeCoverageCollection. + +This work has been done by members of the OGC MetOcean Domain Working Group. - 02-024 - Extends the Web Map Server (WMS) interface to allow access to geospatial coverages that represent values or properties of geographic locations, rather than WMS generated maps (pictures). - Web Coverage Service - 02-024 - Web Coverage Service - - + - - 2002-06-30 - John Evans + + 15-045r7 - + + 08-127 + + 2008-08-25 + + - Corrigendum 1 (one) for OpenGIS Implementation Specification GML 2.1.2 - 06-189 + + GML 3.2 implementation of XML schemas in 07-000 - This document provides the details for a corrigendum for the existing OpenGIS Implementation Specification for the Geography Markup Language version 2.1.2 and does not modify that implementation specification. The current OpenGIS Implementation Specification that this document provides revision notes for is 02-069. + + 08-127 + GML 3.2 implementation of XML schemas in 07-000 + Simon Cox + + + WAMI Services: Dissemination Services for Wide Area Motion Imagery - Best Practice + This OGC Best Practice (BP) describes web interface specifications for the access and dissemination of Wide Area Motion Imagery (WAMI) products and metadata. This BP also describes a framework and interface specifications common to all WAMI services. A <a href=https://portal.ogc.org/files/?artifact_id=50485>WAMI - Primer</a> has been developed to help you implement this Best Practice. + 12-032r2 + - Chris Holmes - - - 06-189 - - 2007-08-27 - Corrigendum 1 (one) for OpenGIS Implementation Specification GML 2.1.2 + WAMI Services: Dissemination Services for Wide Area Motion Imagery - Best Practice + 12-032r2 + + 2012-12-05 + + + Rahul Thakkar, Michael Maraist + - - + + 18-000 + + + OGC GeoPackage Related Tables Extension + 2019-05-08 + GeoPackage Related Tables Extension + 18-000 + A GeoPackage [geopackage] is a platform-independent SQLite [sqlite] database file that contains GeoPackage data and metadata tables. GeoPackages, as described by the GeoPackage Encoding Standard [GPKG1_2] are designed to be extensible, including support for additional data types. This document defines the Related Tables Extension (RTE) for the GeoPackage Encoding Standard. + +The RTE defines the rules and requirements for creating relationships in a GeoPackage data store between geospatial data tables and other tables that contain or reference related content such as attributes or media. Geospatial data tables (such as features or tiles tables) contain location information and/or geometries. There are many examples of where the RTE can be used including relating parcel (land lot) features to pictures of that parcel or linking census boundaries to the related demographic census data. + Jeff Yutzler + + + + - - - Clemens Portele - 12-093 - The main scope of the schema automation activities in the OWS-9 initiative was twofold: -• Support for the SWE Common 2.0 XML Schema encoding rule -• Development of and support for an encoding rule for JSON instance data -In both cases the scope includes implementation of the encoding rules in ShapeChange. -In addition, an initial analysis of the possibilities for generating SWE Common 2.0 record descriptions from schemas in UML has been conducted and the results are described in this document. -The approach and results to both work items are described and discussed in this engineering report. This Engineering Report has been prepared as part of the OGC Web Services Phase 9 (OWS-9) initiative. - - OWS-9: UML-to-GML-Application-Schema (UGAS) Conversion Engineering Report + + Testbed-13:Asynchronous Services ER + 17-028 + Benjamin Pross, Christoph Stasch + + OGC Testbed-13: Asynchronous Services ER + - 2013-02-05 + The goal of this ER is to summarize and compare the results from the activities dealing with asynchronous WFS responses in Testbed 13. Special focus will be given to the specific requirement for automatic notification of users if new or updated information becomes available and to the software components addressing these requirements, i.e. two asynchronous Web Feature Services (NG119 and NG120). + 17-028 + 2018-01-08 + - 12-093 - OWS-9: UML-to-GML-Application-Schema (UGAS) Conversion Engineering Report - - - - - - 12-040 - - 12-040 - Web Coverage Service Interface Standard - Range Subsetting Extension + + OGC® GeoPackage Encoding Standard – With Corrigendum + This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a “native” storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. + Paul daisey + + 12-128r11 + GeoPackage Encoding Standard – With Corrigendum + 12-128r11 + + + + 2015-04-20 - OGC® Web Coverage Service Interface Standard - Range Subsetting Extension + + + + Geospatial Portal Reference Architecture + 04-039 + 04-039 + 2004-09-22 + + + This Guide has been developed by the members of the Open Geospatial Consortium, Inc. to assist the global geospatial technology community in implementing standards-based geospatial portal solutions that are compatible with Spatial Data Infrastructures in every nation. We offer this document as a resource for rapid development and informed acquisition of portals and portal-exploiting applications that can plug and play with geospatial data and services in your organization and other organizations in your community and around the world. + + Louis Rose + Geospatial Portal Reference Architecture - This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request which allow extraction of specific fields, according to the range type specification, from the range set of a coverage during server-side processing of a coverage in a GetCover-age request. - Peter Baumann, Jinsongdi Yu - 2014-02-26 + - + - - 17-019 - Testbed-13: MapML Engineering Report - 17-019 + + 15-074 + + + 15-074 + Spatial Data on the Web Use Cases & Requirements + This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC. + Frans Knibbe, Alejandro Llaves + Spatial Data on the Web Use Cases & Requirements + + + 2015-07-22 + + + + + Carl Reed, Tamrat Belayneh + 17-014r9 + OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.3 + + OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package (*.slpk) Format Community Standard Version 1.3 - - Joan Maso - - This Engineering Report discusses the approach of Map Markup Language (MapML) and Map for HyperText Markup Language (Map4HTML) described in: https://github.com/Maps4HTML and supported by the community in https://www.w3.org/community/maps4html/. The objective of MapML is to define a hypermedia type for geospatial maps on the web that can be embedded in HyperText Markup Language (HTML) pages. MapML is needed because while Web browsers implement HTML and Scalable Vector Graphics (SVG), including the <map> element, those implementations do not meet the requirements of the broader Web mapping community. The semantics of the HTML map element are incomplete or insufficient relative to modern Web maps and mapping in general. Currently, robust web maps are implemented by a variety of non-standard technologies. Web maps do not work without script support, making their creation a job beyond the realm of beginners' skill sets. In order to improve collaboration and integration of the mapping and Web communities, it is desirable to enhance or augment the functionality of the <map> element in HTML to include the accessible user interface functions of modern web maps (e.g. panning, zooming, searching for, and zooming to, styling, identifying features’ properties, etc.), while maintaining a simple, declarative, accessible interface for HTML authors. + + The Indexed 3D Scene Layer (I3S) format is an open 3D content delivery format used to rapidly stream and distribute large volumes of 3D GIS data to mobile, web and desktop clients. I3S content can be shared across enterprise systems using both physical and cloud servers. -The objective of this Engineering Report is to explore how MapML can be harmonized with the OGC standards mainstream and contribute to the progress of the specification avoiding unnecessary duplication. In particular, the ER proposes Web Map Service (WMS) or Web Map Tile Service (WMTS) as services that can be used to deliver MapML documents with small modifications. +A single I3S data set, referred to as a Scene Layer, is a container for arbitrarily large amounts of heterogeneously distributed 3D geographic data. Scene Layers are designed to be used in mobile, desktop, and server-based workflows and can be accessed over the web or as local files. -Another consideration on the ER is the inclusion of the time dimension and directions operation in MapML. - OGC Testbed-13: MapML Engineering Report - 2018-01-11 +The delivery format and persistence model for Scene Layers, referred to as Indexed 3d Scene Layer (I3S) and Scene Layer Package (SLPK) respectively, are specified in detail in this OGC Community Standard. Both formats are encoded using JSON and binary ArrayBuffers (ECMAScript 2015). I3S is designed to be cloud, web and mobile friendly. I3S is based on JSON, REST and modern web standards and is easy to handle, efficiently parse and render by Web and Mobile Clients. I3S is designed to stream large 3D datasets and is designed for performance and scalability. I3S is designed to support 3D geospatial content and supports the requisite coordinate reference systems and height models in conjunction with a rich set of layer types. + 2023-01-11 + 17-014r9 - - 2020-01-08 - OGC Testbed-15: Maps and Tiles API Engineering Report - 19-069 - 19-069 - In 2017 the OGC began a focused effort to develop Application Programming Interface (API) standards that support the Resource Oriented Architecture and make use of the OpenAPI specification. As part of this effort, this OGC Testbed 15 Engineering Report (ER) defines a proof-of-concept of an API specification for maps and tiles. + + Urban Digital Twins: Integrating Infrastructure, natural environment and people + 24-025 + + + + + 2024-07-02 + 24-025 + Carsten Rönsdorf, Fabrice Servant, H.C. Gruler, Nick Giannias, Kyoungsook Kim, Zubran Soleiman, Dim + + Urban Digital Twins: Integrating Infrastructure, natural environment and people + + This position paper is aimed at city officials and domain professionals working in an urban data context. Its goal is to clarify the concept of Urban Digital Twins (UDT) and to position it in regards of Digital Twins in general as well as the emerging Metaverse. -The OGC API Maps and Tiles draft specification described in this ER builds on the precedent of the OGC API - Features - Part 1: Core standard. The OGC API - Tiles draft specification describes a service that retrieves data representations as tiles, which are generally small compared with the geographic extent of the data. In the draft specification, the assumption is that tiles are organized into Tile Matrix Sets consisting of regular tile matrices available at different scales or resolutions. The OGC API – Tiles draft specification is described as a building block that can be plugged into an OGC API - Features service to retrieve tiled feature data (sometimes called vector tiles) or to an OGC API – Maps implementation to retrieve rendered tiles (sometimes called map tiles). In the future, the OGC API - Tiles draft specification could extend other specifications, one possible candidate being the emerging OGC API – Coverages draft specification. +Overall, the UDT concept is an approach to understand characteristics and processes of the built environment at the scale of a city. Between climate change and various demographics, dynamic cities are facing challenges that are becoming more complex to solve. Most of the time solutions have to be imagined with a system of systems approach and cannot be solved in silos. -The OGC API - Maps draft specification describes an API that presents data as maps by applying a style. These maps can be retrieved in a tiled structure (if OGC API - Tiles is approved as an OGC Implementation Standard) or as maps of any size generated on-the-fly. The OGC API - Maps draft specification implements some functionality, specified in the Web Map Tile Service (WMTS) 1.0 standard, related to the use of styles by using the Styles API draft specification that was developed in the Testbed-15 Open Portrayal Framework thread. +The paper represents the current state of the discussion about UDTs in the Open Geospatial Consortium (OGC), a geospatial community and standards organization. -The draft Maps and Tiles API specifications are designed in a modular way. With the exception of the core requirements, the other conformance classes describe functionality that can be considered optional characteristics that can be combined by server implementations at will. +Around 3 use cases, climate change adaptation, urban transformation, and urban air mobility, this paper identifies benefits of using a UDT and explain the role of Geospatial Information (GI) and how it can contribute to an UDT. -At the beginning of Testbed-15, the original proposed title for this ER was OGC Testbed-15: Web Map Tiling Service Draft Specification Engineering Report but in the course of the Testbed-15 that title was changed to better represent the content. - Joan Maso Pau - - - - - - - OGC Testbed-15: Maps and Tiles API Engineering Report - - - 2022-11-28 - - Carl Stephen Smyth - - - OGC GeoPose 1.0 Data Exchange Draft Standard - 21-056r10 - - - - 21-056r10 - OGC GeoPose 1.0 Data Exchange Draft Standard - GeoPose 1.0 is an OGC Implementation Standard for exchanging the location and orientation of real or virtual geometric objects (“Poses”) within reference frames anchored to the earth’s surface (“Geo”) or within other astronomical coordinate systems. +UDTs is a digital representation of the city where elected representatives and professional stakeholders can access and contribute to a common reference model to collaborate, achieving positive outcomes for the citizens. UDTs reveal insights at the intersection of the natural and built environments and human activities. They provide the means of enabling simulation scenarios and plan possible interventions as well as tracking measurable evidence of any changes in the real world. In a mature state, UDTs will establish effective feedback loops between the virtual and the true, physical environments. -The standard specifies two Basic forms with no configuration options for common use cases, an Advanced form with more flexibility for more complex applications, and five composite GeoPose structures that support time series plus chain and graph structures. +From discussions with elected representatives, professionals, and also based on OGC member experience on projects, it is acknowledged that the process of building an UDT might seem daunting (as outlined in the paper by [Lei, 2023]: Challenges of urban digital twins: A systematic review and a Delphi expert survey). -These eight Standardization Targets are independent. There are no dependencies between Targets and each may be implemented as needed to support a specific use case. +This paper presents a pragmatic approach based on OGC standards for each use case, building on location and GI as the foundation. This approach calls for an effective data strategy and suggests that a project-based approach with a vision of building a UDT is the most efficient path. -The Standardization Targets share an implementation-neutral Logical Model which establishes the structure and relationships between GeoPose components and also between GeoPose data objects themselves in composite structures. Not all of the classes and properties of the Logical Model are expressed in individual Standardization Targets nor in the specific concrete data objects defined by this standard. Those elements that are expressed are denoted as implementation-neutral Structural Data Units (SDUs). SDUs are aliases for elements of the Logical Model, isolated to facilitate specification of their use in encoded GeoPose data objects for a specific Standardization Target. +This concept of UDT, although often mentioned in the media, is still fairly new in practice and the governance of that type of platform is still a challenge. OGC is keen on supporting and collaborating on projects to help create the best practices on that matter. + + + + + OGC API - Environmental Data Retrieval Standard + 2022-08-05 + Mark Burgoyne, David Blodgett, Charles Heazel, Chris Little + + 19-086r5 + OGC API - Environmental Data Retrieval Standard + + + + 19-086r5 + The Environmental Data Retrieval (EDR) Application Programming Interface (API) provides a family of lightweight query interfaces to access spatio-temporal data resources by requesting data at a Position, within an Area, along a Trajectory or through a Corridor. A spatio-temporal data resource is a collection of spatio-temporal data that can be sampled using the EDR query pattern geometries. These patterns are described in the section describing the Core Requirements Class. -For each Standardization Target, each implementation technology and corresponding encoding format defines the encoding or serialization specified in a manner appropriate to that technology. +The goals of the EDR API are to make it easier to access a wide range of data through a uniform, well-defined simple Web interface, and to achieve data reduction to just the data needed by the user or client while hiding much of the data storage complexity. A major use case for the EDR API is to retrieve small subsets from large collections of environmental data, such as weather forecasts, though many other types of data can be accessed. The important aspect is that the data can be unambiguously specified by spatio-temporal coordinates. -GeoPose 1.0 specifies a single encoding in JSON format (IETF RFC 8259). Each Standardization Target has a JSON Schema (Internet-Draft draft-handrews-json-schema-02) encoding specification. The key standardization requirements specify that concrete JSON-encoded GeoPose data objects must conform to the corresponding JSON Schema definition. The individual elements identified in the encoding specification are composed of SDUs, tying the specifications back to the Logical Model. +The EDR API query patterns, such as Position, Area, Cube, Trajectory or Corridor, can be thought of as discrete sampling geometries, conceptually consistent with the feature of interest in the Sensor Observation Service (SOS) standard. A typical EDR data resource is a multidimensional dataset that could be accessed via an implementation of the Web Coverage Service (WCS) standard. In contrast to SOS and WCS, the EDR API implements the technical baseline of the OGC API family of standards and aims to provide a single set of simple-to-use query patterns. Use cases for EDR range from real or virtual time-series observation retrievals, to sub-setting 4-dimensional data cubes along user-supplied sampling geometries. These query patterns do not attempt to satisfy the full scope of either SOS or WCS, but provide useful building blocks to allow the composition of APIs that satisfy a wide range of geospatial data use cases. By defining a small set of query patterns (and no requirement to implement all of them), the EDR API should help to simplify the design of systems (as they can be performance tuned for the supported queries) making it easier to build robust and scalable infrastructure. -The GeoPose 1.0 Standard makes no assumptions about the interpretation of external specifications, for example, of reference frames. Nor does it assume or constrain services or interfaces providing conversion between GeoPoses of difference types or relying on different external reference frame definitions. +With the OGC API family of standards, the OGC community has extended its suite of standards to include Resource Oriented Architectures and Web Application Programming Interfaces (APIs). These standards are based on a shared foundation, specified in OGC API-Common, which defines the resources and access paths that are supported by all OGC APIs. The resources are listed in Table 1. This document extends that foundation to define the Environmental Data Retrieval API. + + + Testbed-18: 3D+ Data Space Object Engineering Report + 23-011r1 + + With the growing commercialization of space there is a need to look beyond the earth and explore the integration of sensors or assets in celestial orbits or in free flight in our solar system. Their exact tracking and localization are becoming increasingly important as space emerges as the newest area in need for standard-based mechanisms for streaming and for data integration from various sensors. - +This Open Geospatial Consortium (OGC) Testbed 18 3D+ Data Space Object Engineering Report (ER) describes existing standards in terms of their ability to represent a suite of multidimensional Coordinate Reference Systems (CRS) and associated geometries as well as identifies shortfalls in these standards. + + Martin Desruisseaux, Logan Stark + + 23-011r1 + + + + 2023-06-26 + Testbed-18: 3D+ Data Space Object Engineering Report - + + 15-098r1 + Geospatial User Feedback Standard: XML Encoding Extension + Joan Masó, Lucy Bastin - Arliss Whiteside - Web Coverage Service (WCS) Implementation Standard - 07-067r5 + + 15-098r1 + 2016-12-22 + The Geospatial User Feedback XML encoding standard is based on the OGC Geospatial User Feedback conceptual model [OGC 15-097]. Geospatial User Feedback (GUF) is metadata that is predominantly produced by the consumers of geospatial data products based on their use and experience with those products. This standard complements the existing metadata conventions whereby documents recording dataset characteristics and production workflows are generated by the creator, publisher, or curator of a data product. As a part of metadata, the GUF data model internally reuses some elements of ISO 19115-1 (the updated version of the OGC Abstract Specification Topic 11) but not the general structure. This selective use of ISO metadata elements prioritizes future interoperability with developing ISO metadata models. +This standard can be used in combination with the OGC 15-097 Conceptual Model Standard. In the future, other encodings may be considered, being an alternative using the JSON-LD encoding based on parts of schema.org. + + + + + + OGC® Geospatial User Feedback Standard: XML Encoding Extension + + + Catalog Interface + 1999-07-16 + + 99-051 + Catalog Interface + + 99-051 + Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers. + Doug Nebert - The OpenGIS® Web Coverage Service Interface Standard (WCS) defines a standard interface and operations that enables interoperable access to geospatial coverages [http://www.opengeospatial.org/ogc/glossary/c]. The term grid coverages typically refers to content such as satellite images, digital aerial photos, digital elevation data, and other phenomena represented by values at each measurement point. - 07-067r5 - - 2008-04-29 - Web Coverage Service (WCS) Implementation Standard - - - - - - - - - - This OGC Engineering Report specifies the results and findings of the CityGML Quality -Interoperability Experiment. Guidelines were developed for the following concepts: -&#1048576; Definition of data quality; -&#1048576; Data quality requirements and their specification; -&#1048576; Quality checking process of CityGML data; and -&#1048576; Description of validation results. -The desired outcomes of this Interoperability Experiment are to improve the -interoperability of CityGML data by removing some ambiguities from the current -standard and formally defining data quality requirements for a general CityGML data -specification. Further, the results of this work provides to the community (organizations -invested in capturing, procuring, or utilizing CityGML data) recommended -implementation guidance for 3D data and a suite of essential quality checking tools to -carry out quality assurance on CityGML data. + - 2016-08-01 - OGC® CityGML Quality Interoperability Experiment + + 2022 Web Mapping Code Sprint Summary Engineering Report - 16-064r1 - CityGML Quality Interoperability Experiment - Detlev Wagner, Hugo Ledoux - 16-064r1 + 2023-06-16 + Gobe Hobona, Joana Simoes + + + The subject of this Engineering Report (ER) is a code sprint that was held from November 29th to December 1st, 2022 to advance OGC API Standards that relate to web mapping, and others that relate to styling and symbology encoding standards. The code sprint was hosted by the Open Geospatial Consortium (OGC) and EuroGeographics. The code sprint was sponsored by Ordnance Survey (OS), and was held as a hybrid event with the face-to-face element hosted at the Mundo Madou centre in Brussels, Belgium. + 22-054r1 + 2022 Web Mapping Code Sprint Summary Engineering Report + 22-054r1 + - + + 18-024r1 + + + Release Notes for OGC GeoPackage Encoding Standard v1.2.1 - - + + 18-024r1 + Release Notes for OGC GeoPackage Encoding Standard v1.2.1 + This document provides the set of revision notes for the existing GeoPackage version 1.2.1 (OGC 12-128r15) and does not modify that standard. + +This document was approved by the OGC membership on approval date. As a result of the OGC Standards Working Group (SWG) process, there were a number of edits and enhancements made to this standard. This document provides the details of those edits, deficiency corrections, and enhancements. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility. + 2018-12-18 + - 16-024r2 - Testbed-12 — Catalog Services for Aviation + Jeff Yutzler + + + Testbed-12 Imagery Quality and Accuracy Engineering Report + Testbed-12 Imagery Quality and Accuracy Engineering Report + 16-050 + + 16-050 + + Joan Masó and Alaitz Zabala - Testbed-12 — Catalog Services for Aviation - 2017-06-15 - R. Martell - 16-024r2 - This Engineering Report (ER) presents guidance concerning the use of OGC® catalog services in the aviation domain. A wide variety of metadata resources can be readily published and discovered using the OGC CSW-ebRIM application profile, which marries the CSW catalog interface to the OASIS ebXML registry information model (ebRIM). However, existing SWIM registries currently under development by the FAA and Eurocontrol do not implement any OGC standards. This report explores the prospects for enhancing SWIM registries by a) integrating OGC catalog functionality, and b) accommodating OGC service descriptions. + + The scenario of rapidly growing geodata catalogues requires tools focused on facilitating users the choice of products. Having populated quality fields in metadata allows the users to rank and then select the best fit-for-purpose products. For example, decision-makers would be able to find quality and uncertainty measures to take the best decisions as well as to perform dataset intercomparison. In addition, it allows other components (such as visualization, discovery, or comparison tools) to be quality-aware and interoperable. + +This ER deals with completeness, logical consistency, positional accuracy, temporal accuracy and thematic accuracy issues to improve quality description in the metadata for imagery. Based on ISO 19157, UncertML and QualityML standardized measures, this ER describes how to encode quality measures in order to allow datasets comparison. Moreover, description of pixel-level quality measures is also included. Finally, alternatives to communicate tile level quality as well as mosaic products quality are proposed. + + 2017-05-12 - + + 20-036 + Full Motion Video to Moving Features Engineering Report + - - David Burggraf + This OGC Testbed-16 Engineering Report (ER) evaluates the suitability of existing OGC standards for the generation of Moving Features from Full Motion Video (FMV) that has an embedded stream of detected moving objects. + +This ER presents several proof of concept applications that accept FMVs, with multiple encoded Video Moving Target Indicators (VMTI), and combines the VMTIs into separate tracks that are then encoded to OGC Moving Features. + +In addition, the ER explores the generation of records encoded according to OGC Sensor Model Language (SensorML) 2.0 standard describing the collection platform and relevant telemetry information from the key-value stream content encoded according to the MISB 0601 and 0903 specifications of the Motion Imagery Standards Board (MISB). - 2013-06-18 + OGC Testbed-16: Full Motion Video to Moving Features Engineering Report - OGC® OWS-9 Architecture - Registry Engineering Report - - 12-144 - 12-144 - OWS-9 Architecture - Registry Engineering Report - This OGC® Engineering Report provides guidelines for the harvest, registration and retrieval of aviation resources from an OGC web catalogue/registry service (OGC CSW-ebRIM), with particular emphasis on ISO metadata resources. Alternatives for selective and efficient retrieval of such resources are also described along with lessons learned. The OGC CSW-ebRIM registry interface is evaluated against SESAR registry requirements, documented as a gap analysis, to assess whether there are any obstacles to implementing SESAR registry with an OGC CSW-ebRIM interface. - - - Recommended XML Encoding of CRS Definitions - 03-010r9 + 20-036 + 2021-01-13 + Emeric Beaufays, C.J. Stanbridge, Rob Smith + + + Discussion paper for Publish-Subscribe workflow in OGC APIs - 2003-10-16 - Arliss Whiteside + + 23-013 + Discussion paper for Publish-Subscribe workflow in OGC APIs - - This OpenGIS Recommendation Paper specifies basic XML encoding of data defining coordinate reference systems and coordinate operations. This encoding is expected to be adapted and used by multiple OGC Implementation Specifications, by the separate specification of Application Schemas. This document is a Recommendation Paper because the specified encoding is more general than an OpenGIS Implementation Specification and more specific than the OpenGIS Abstract Specification. - - 03-010r9 - - Recommended XML Encoding of CRS Definitions + + Tom Kralidis, Mark Burgoyne, Steve Olson, Shane Mill + 23-013 + + OGC APIs provide Web based capabilities which are typically based on polling for collection resource updates (new features/records items, coverages, maps, etc.). Depending on a collection’s temporal resolution or frequency of updates, an event-driven / Publish-Subscribe architecture provides a timely, efficient, and low latency approach for delivery of data updates. This paper provides recommendations on applying Publish-Subscribe architectural patterns to OGC APIs. + 2023-10-26 + - - 16-088r1 - 16-088r1 - Soil Data Interoperability Experiment - - + + + Jerome Sonnet + 2005-05-03 + 05-005 + + Web Map Context Implementation Specification + 05-005 + OpenGIS Web Map Context Implementation Specification + + + This document is a companion specification to the OGC Web Map Service Interface Implementation Specification version 1.1.1 [4], hereinafter WMS 1.1.1. +WMS 1.1.1 specifies how individual map servers describe and provide their map content. The present Context specification states how a specific grouping of one or more maps from one or more map servers can be described in a portable, platform-independent format for storage in a repository or for transmission between clients. This description is known as a Web Map Context Document, or simply a Context. Presently, context documents are primarily designed for WMS bindings. However, extensibility is envisioned for binding to other services. +A Context document includes information about the server(s) providing layer(s) in the overall map, the bounding box and map projection shared by all the maps, sufficient operational metadata for Client software to reproduce the map, and ancillary metadata used to annotate or describe the maps and their provenance for the benefit of human viewers. +A Context document is structured using eXtensible Markup Language (XML). Annex A of this specification contains the XML Schema against which Context XML can be validated. + - This engineering report describes the results of the Soil Data Interoperability Experiment -(the IE) conducted under the auspices of the OGC Agriculture Domain Working Group in -2015. Soil data exchange and analysis is compromised by the lack of a widely agreed -international standard for the exchange of data describing soils and the sampling and -analytical activities relating to them. Previous modeling activities in Europe and -Australasia have not yielded models that satisfy many of the data needs of global soil -scientists, data custodians and users. This IE evaluated existing models and proposed a -common core model, including a GML/XML schema, which was tested through the -deployment of OGC web services and demonstration clients. IE time constraints and -limited participant resources precluded extensive modeling activities. However, the -resulting model should form the core of a more comprehensive model to be developed by -a future OGC Soil Data Standards Working Group. - OGC Soil Data Interoperability Experiment - + + + + Web Feature Service (WFS) Implementation Specification + 04-094 - - Alistair Ritchie - 2016-07-26 + + 2005-05-03 + + + + OpenGIS Web Feature Service (WFS) Implementation Specification + The OpenGIS Web Feature Service Interface Standard (WFS) defines an interface[http://www.opengeospatial.org/ogc/glossary/i] for specifying requests for retrieving geographic features [http://www.opengeospatial.org/ogc/glossary/g] across the Web using platform-independent calls. The WFS standard defines interfaces and operations for data access and manipulation on a set of geographic features, including: +• Get or Query features based on spatial and non-spatial constraints +• Create a new feature instance +• Get a description of the properties of features +• Delete a feature instance +• Update a feature instance +• Lock a feature instance + +The specified feature encoding for input and output is the Geography Markup Language (GML) [http://www.opengeospatial.org/standards/gml] although other encodings may be used. + + + 04-094 + Peter Vretanos - - OGC Testbed-15: Federated Clouds Security Engineering Report - 19-024r1 - 19-024r1 - Hector Rodriguez - - + - 2019-12-20 - - This OGC Testbed-15 Engineering Report (ER) documents the concept for different types of federation through the lens of security. The primary focus of the work documented in this ER is on analyzing how federated membership, resource and access policy management can be provided within a security environment, while also providing portability and interoperability to all stakeholders. + + + 18-043r3 + Aleksandar Jelenak, Ted Habermann, Gerd Heber + Hierarchical Data Format Version 5 (HDF5®) is a data model, a programming interface, and a storage model for keeping and managing data. It supports an unlimited variety of data types, and is designed to be flexible and efficient for large and complex data. HDF5 is extensible via customizing data types, allowing communities and their applications to evolve in the use of HDF5. -In the Testbed, a practical approach for providing this functionality was exercised and documented for two administrative domains: One based on a centralized entity (Federation Manager) and the other showcasing a distributed architecture. - OGC Testbed-15: Federated Clouds Security Engineering Report - +This document describes the HDF5 data model as an encoding standard particularly suitable to scientific and engineering geospatial applications that employ multidimensional numeric arrays to describe temporally and spatially varying phenomena. The data model is simple yet versatile, capable of supporting complex data relationships and dependencies through its grouping and linking mechanisms. It is also self-describing by accommodating user-defined metadata. + + Hierarchical Data Format Version 5 (HDF5®) Core Standard + 18-043r3 + 2019-10-28 + OGC Hierarchical Data Format Version 5 (HDF5®) Core Standard + - - - 07-134r2 - KML 2.2 - Abstract Test Suite - 07-134r2 + - Richard Martell - 2008-04-14 + + 08-053r2 + Peter Baumann + + 2009-03-25 + 08-053r2 + WCS Processing Extension (WCPS) Abstract Test Suite + WCS Processing Extension (WCPS) Abstract Test Suite + + + + + + + 13-021r3 + WaterML2.0 - part 2: Ratings, Gaugings and Sections Discussion Paper + + This document describes an information model for exchanging rating tables, or rating +curves, that are used for the conversion of related hydrological phenomenon. It also +describes a model describing the observations that are used to develop such relationships, +often referred to as gauging observations. +The information model is proposed as a second part of the WaterML2.0 suite of +standards, building on part 1 that addresses the exchange of time series1. - OGC KML 2.2 -Abstract Test Suite - - This document is an abstract test suite (ATS): a compendium of abstract test cases that provide a basis for verifying the structure and content of OGC KML 2.2 instance documents. Three conformance levels are defined; each level builds on the preceding ones: - - * - - Level 1 - includes test cases covering all requirements to be satisfied by a minimally conformant KML document; - * - - Level 2 - as for Level 1, plus test cases addressing recommended requirements; - * - - Level 3 - as for Level 2, plus test cases covering suggested constraints that are informative in nature. + WaterML2.0 - part 2: Ratings, Gaugings and Sections Discussion Paper + 2013-06-18 + 13-021r3 + + + Peter Taylor - - - Apple Inc. - - Indoor Mapping Data Format - 20-094 - Indoor Mapping Data Format - 20-094 - 2021-02-18 - Indoor Mapping Data Format (referenced throughout this document as IMDF) provides a generalized, yet comprehensive model for any indoor location, providing a basis for orientation, navigation and discovery. In this release there are also detailed instructions for modeling the spaces of an airport, a shopping mall, and a train station. - -This release also has an extension model which enables a venue, organization, or even an industry to create valid features and validations not available in the current specification for private or public use - + + 2013-06-18 + 12-152r1 + 12-152r1 + OWS-9 CITE Help Guide Engineering Report + + OGC® OWS-9 CITE Help Guide Engineering Report + + + Luis Bermudez + This Engineering Report was created as a deliverable of the CITE Thread as part of the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. This OGC® Engineering Report describes how to execute the CITE tests, how to select the conformance classes, how to access and download the TEAM Engine, Test Scripts and Reference Implementations, how to insert your own data and/or schemas along with a section that provides other community help resources. +This is not a normative document. - - + - - Geographic information — Well-known text representation of coordinate reference systems - 18-010r11 - Roger Lott - 2023-08-16 - 18-010r11 - - This Standard defines the structure and content of well-known text strings describing coordinate reference systems (CRSs) and coordinate operations between coordinate reference systems. It does not prescribe how implementations should read or write these strings. -This Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2019 including its amendments 1 and 2. It extends the WKT in OGC document 12-063r5 (ISO 19162) which was based on ISO 19111:2007 and ISO 19111-2:2009. That version consolidated several disparate versions of earlier WKT (so-called WKT1) and added the description of coordinate operations. - + + 2006-05-02 - Geographic information — Well-known text representation of coordinate reference systems - - - + + 05-050 + 05-050 + GML Performance Investigations by CubeWerx + This report proposes and executes methods to evaluate the performance of the use of the Geography Markup Language (GML) as encoded in various ways. + Craig Bruce + + + + GML Performance Investigations by CubeWerx - + - This document provides a technical description of the Single Point of Entry Global Gazetteer (SPEGG) implemented for the OWS9 test bed. The SPEGG integrates two gazetteers – a copy of the USGS gazetteers containing domestic names (hosted by CubeWerx Inc.) and the NGA gazetteer containing foreign names (originally hosted at NGA but currently hosted by Intergraph Corp.). Both integrated gazetteers and the SPEGG implement the Web Feature Service (WFS) standard. - + + + Joan Maso + OGC Testbed-16: Analysis Ready Data Engineering Report - 2013-06-18 + The Committee on Earth Observation Satellites (CEOS) defines Analysis Ready Data (ARD) for Land (CARD4L) as satellite data that have been processed to a minimum set of requirements and organized into a form that allows immediate analysis with a minimum of additional user effort and interoperability both through time and with other datasets. + +This OGC Testbed 16 Engineering Report (ER) generalizes the ARD concept and studies its implications for the OGC Standards baseline. In particular, the ER analyses how modern federated data processing architectures applying data cubes and Docker packages can take advantage of the existence of ARD. Architectures for ARD should minimize data transmission and allow and favor code transmission and remote execution. This ER also considers a workflow in which new processes are triggered as soon as new data becomes available. This is part of the event driven discussion. + + 20-041 + Analysis Ready Data Engineering Report + 20-041 - OGC® OWS-9 Engineering Report - CCI - Single Point of Entry Global Gazetteer - - 12-104r1 - - OWS-9 Engineering Report - CCI - Single Point of Entry Global Gazetteer - 12-104r1 - Panagiotis (Peter) A. Vretanos + 2021-01-13 - - 2017-05-12 - 16-047r1 - Martin Klopfer - Testbed-12 General Feature Model Engineering Report - 16-047r1 - With a growing requirement to carry out complex analysis in large multi-disciplinary, heterogeneous data collections, an approach is required to extract equivalent information from dissimilar content. The more information can be normalized, the easier it will be to correlate the content. Given that almost all data has a spatio-temporal component, this ER will look into the idea of defining a Spatial-Temporal Service and analyze which collection of data types, operations and architecture patterns would be necessary to spatial-temporal enable any content. This OGC® document reviews the General Feature Model and gives guidelines for necessary modifications to broaden its scope, so that it can be re-used for non-geospatial centric applications and extended as necessary into a general model for all object types. + - - + OGC Earth Observations Applications Pilot: Terradue Engineering Report - - Testbed-12 General Feature Model Engineering Report - - - - Documents of type Approved Specification Profile - Documents of type Approved Specification Profile - - - - - - - - - Documents of type Approved Specification Profile - - - - - - + This OGC Engineering Report (ER) documents the findings and experiences resulting from Terradue Activities on the OGC Earth Observation Applications Pilot. More specifically, this ER provides a way forward for the implementation of the applications to the data paradigm in the context of Earth Observation (EO) satellite data processing and Cloud-based platforms to facilitate and standardize the access to Earth observation data and information. + 20-042 + OGC Earth Observations Applications Pilot: Terradue Engineering Report + Pedro Gonçalves + - Kristin Stock - This document describes an Application Profile for the Web Ontology Language (OWL) [W3C OWL] for CSW. It is intended to define a specification for how ontologies built using RDF and OWL may be included within an OGC CSW catalogue to semantically-enable the catalogue. - - OGC® Catalogue Services - OWL Application Profile of CSW - 2009-07-27 - OGC® Catalogue Services - OWL Application Profile of CSW - 09-010 - - 09-010 - - - 09-140r2 - OGC® NSG Plugweek Engineering Report - The Open Geospatial Consortium (OGC®) conducted a series of tests that examined the interoperability, suitability and performance of National System for Geospatial- Intelligence (NSG) Profiles provided by the National Geospatial-Intelligence Agency (NGA) of four OGC Standards, Web Map Service (WMS), Web Feature Service (WFS), Web Coverage Service (WCS), and Catalog Service (CAT). In the study, vendors, users, and other interested parties conducted Technology Integration Experiments (TIEs) and mutually refined clients, services, interfaces and protocols in the context of a hands-on engineering experience expected to shape the future NGA, NSG and Geospatial Intelligence (GEOINT) web based distribution. - 09-140r2 - - + 20-042 - - - 2010-07-30 - Paul Daisey - OGC® NSG Plugweek Engineering Report + 2020-10-22 - + + + + This Standard defines the structure and content of well-known text strings describing coordinate reference systems (CRSs) and coordinate operations between coordinate reference systems. It does not prescribe how implementations should read or write these strings. +This Standard provides an updated version of WKT representation of coordinate reference systems that follows the provisions of ISO 19111:2019 including its amendments 1 and 2. It extends the WKT in OGC document 12-063r5 (ISO 19162) which was based on ISO 19111:2007 and ISO 19111-2:2009. That version consolidated several disparate versions of earlier WKT (so-called WKT1) and added the description of coordinate operations. + + Roger Lott + + Geographic information — Well-known text representation of coordinate reference systems + 18-010r11 + 18-010r11 - The Uncertainty Markup Language (UncertML) is an XML encoding for the transport and storage of information about uncertain quantities, with emphasis on quantitative representations based on probability theory. - Matthew Williams, Dan Cornford, Lucy Bastin & Edzer Pebesma - 2009-04-08 - 08-122r2 - 08-122r2 - Uncertainty Markup Language (UnCertML) - Uncertainty Markup Language (UnCertML) - - - + 2023-08-16 + Geographic information — Well-known text representation of coordinate reference systems - - - 23-040 - OGC Guidance for the Development of Model-Driven Standards - + - 2024-07-01 - - OGC Guidance for the Development of Model-Driven Standards - Ronald Tse, Carsten Roensdorf, Allan Jamieson, Nick Nicholas, Jeffrey Lau - This OGC Discussion Paper provides guidelines on how to create a specification of a conceptual model through use of a Unified Modeling Language (UML) editor and an AsciiDoc compiler. This document references Sparx Systems Enterprise Architect and the Metanorma AsciiDoc toolchain in examples that implement the OGC model-driven standards process, described in OGC 21-035r1. - - - 23-040 - - - 12-018r1 - Surface Water Interoperability Experiment FINAL REPORT - Peter Fitch - This report describes the methods, results, issues and recommendations generated by -the Surfacewater Interoperability Experiment (SW IE), carried out as an activity of the -OGC Hydrology Domain Working Group (HDWG). The SW IE was designed to -advance the development of WaterML 2.0 and test its use with various OGC service -standards (SOS, WFS, WMS and CSW). A secondary aim was to contribute to the -development of a hydrology domain feature model and vocabularies, which are -essential for interoperability in the hydrology domain, although these are not the main -focus for the IE. - Surface Water Interoperability Experiment FINAL REPORT - + Andrea Aime + OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report + 19-023r1 + 19-023r1 + This OGC Testbed 15 Engineering Report (ER) describes a style encoding and metadata conceptual model that provides information for understanding styles intended usage, availability, compatibility with existing layers, and supporting style search. A style is a sequence of rules of symbolizing instructions to be applied by a rendering engine on one or more features and/or coverages + + 2019-12-11 + - - 12-018r1 - - 2012-05-15 + OGC Testbed-15: Encoding and Metadata Conceptual Model for Styles Engineering Report - - 99-114 - The OpenGIS notion of Information Communities was devised to enable groups such as ecologists and civil engineers to efficiently manage the semantics (or feature schema mismatches) of their own geodata collections and get maximum benefit from each other's geodata collections, despite semantic differences. - - Topic 14 - Semantics and Information Communities - 99-114 - - + + + + + + + + Documents of type test suite - Topic 14 - Semantics and Information Communities - - Cliff Kottman - 1999-04-04 - + Documents of type test suite + Documents of type test suite - - 12-028 - Guidance and Profile of GML for use with Aviation Data - 2012-05-15 - - OGC Aviation Domain Working Group - - - The ISO 19107 spatial schema, which is implemented by GML, is very complex. ISO -19107 defines an extensive list of geometries, geometric properties and operations – -many of which are not necessary for aeronautical information applications. In addition, -the ISO 19107 contains an exhaustive 3D geometry model that is probably not needed in -its entirety for AIXM either. Therefore, a GML profile for AIXM needs to be defined. -The objective of this document is to identify the elements of the AIXM-GML profile and -also to provide guidelines for the use of GML constructs in AIXM data sets. - + - Guidance and Profile of GML for use with Aviation Data - + 16-060r2 + + GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile + 16-060r2 + + 2018-11-27 - 12-028 - - + Daniel Lee + OGC GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile + + This OGC standard is a profile of the OGC GML Application Schema - Coverages version 1.0 [OC 09-146r2]. That document was renamed OGC Coverage Implementation Schema (CIS) for clarification in version 1.1. This standard specifies the usage of the GRIB2 data format for the encoding of OGC coverages. The GRIB2 specification is maintained by the World Meteorological Organization (WMO) and is the standard encoding for the exchange and storage of general regularly distributed information expressed in binary form. + + + GML Application Schema for EO Products + 06-080r2 + + 06-080r2 - Filter Encoding 2.0 Encoding Standard - 09-026r1 - 2010-11-22 - 09-026r1 - OpenGIS Filter Encoding 2.0 Encoding Standard + + + Jerome Gasperi + + GML Application Schema for EO Products + + 2007-08-16 + This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGC + + - - This International Standard describes an XML and KVP encoding of a system neutral syntax for expressing projections, selection and sorting clauses collectively called a query expression. -These components are modular and intended to be used together or individually by other standards which reference this International Standard. - + This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange. - Panagiotis (Peter) A. Vretanos + 2015-02-17 + OGC® Moving Features Encoding Part I: XML Core + 14-083r2 + Moving Features Encoding Part I: XML Core + 14-083r2 + Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf + + + + - - 14-110r2 - Dimitri Sarafinof - GML Application Schema - Coverages JPEG2000/JPIP Coverage Encoding Extension - 14-110r2 - 2016-11-02 + + 13-131r1 + Publish/Subscribe Interface Standard 1.0 - Core + 2016-08-22 + + + + Publish/Subscribe 1.0 is an interface specification that supports the core components and concepts of the Publish/Subscribe message exchange pattern with OGC Web Services. The Publish/Subscribe pattern complements the Request/Reply pattern specified by many existing OGC Web Services. This specification may be used either in concert with, or independently of, existing OGC Web Services to publish data of interest to interested Subscribers. + +Publish/Subscribe 1.0 primarily addresses subscription management capabilities such as creating a subscription, renewing a subscription, and unsubscribing. However, this standard also allows Publish/Subscribe services to advertise and describe the supported message delivery protocols such as SOAP messaging, ATOM, and AMQP. Message delivery protocols should be considered to be independent of the Publish/Subscribe 1.0 standard. Therefore, OGC Publish/Subscribe only includes metadata relating to message delivery protocols in sufficient detail to allow for different implementations of Publish/Subscribe 1.0 to interoperate. + +This specification defines Publish/Subscribe functionality independently of the binding technology (e.g., KVP, SOAP, REST). Extensions to this specification may realize these core concepts with specific binding technologies. + Aaron Braeckel , Lorenzo Bigagli , Johannes Echterhoff + OGC® Publish/Subscribe Interface Standard 1.0 - Core + 13-131r1 - - OGC® GML Application Schema - Coverages JPEG2000/JPIP Coverage Encoding Extension - - Coverages represent space/time-varying phenomena, such as satellite imagery, digital elevation models, or digital aerial imagery. OGC Abstract Topic 6 [OGC 07-011] – which is identical to ISO 19123 – defines an abstract model of coverages. Coverage instances may be encoded using the GML Application Schema – Coverages – JPEG2000 Coverage Encoding Extension version 1.0 [OGC 12-108] which is based on the GML Application Schema – Coverages (GMLCOV) version 1.0 [OGC 09-146r2] which in turn is based on the Geography Markup Language (GML) version 3.2 [07-036], an XML grammar written in XML Schema for the description of application schemas as well as the transport and storage of geographic information. - -This extension to the Web Coverage Service (WCS) 2.0 Interface Standard – Core (WCS) version 2.0 [OC 09-110r4] specifies the usage of the JPEG2000 coverage encoding and JPIP streaming capabilities with WCS. The approach is based on the authoritative GML Application Schema – Coverages – JPEG2000 Coverage Encoding Extension version 1.0 [OGC 12-108]. - - - WCS 2.0 Interface Standard- Core: Corrigendum - 09-110r4 - - OGC® WCS 2.0 Interface Standard- Core: Corrigendum - - - 2012-07-12 - Peter Baumann - + + 2008-04-14 + - This document specifies how a Web Coverage Service (WCS) offers multi-dimensional cov-erage data for access over the Internet. This document specifies a core set of requirements that a WCS implementation must fulfil. WCS extension standards add further functionality to this core; some of these are required in addition to the core to obtain a complete implementa-tion. This document indicates which extensions, at a minimum, need to be considered in ad-dition to this core to allow for a complete WCS implementation. -This core does not prescribe support for any particular coverage encoding format. This also holds for GML as a coverage delivery format: while GML constitutes the canonical format for the definition of WCS, it is not required by this core that a concrete instance of a WCS service implements the GML coverage format. WCS extensions specifying use of data encod-ing formats in the context of WCS are designed in a way that the GML coverage information contents specified in this core is consistent with the contents of an encoded coverage. - - 09-110r4 + KML 2.2 - Abstract Test Suite + 07-134r2 + + + OGC KML 2.2 -Abstract Test Suite + 07-134r2 + Richard Martell + + This document is an abstract test suite (ATS): a compendium of abstract test cases that provide a basis for verifying the structure and content of OGC KML 2.2 instance documents. Three conformance levels are defined; each level builds on the preceding ones: + + * + + Level 1 - includes test cases covering all requirements to be satisfied by a minimally conformant KML document; + * + + Level 2 - as for Level 1, plus test cases addressing recommended requirements; + * + + Level 3 - as for Level 2, plus test cases covering suggested constraints that are informative in nature. - - Testbed-11 NIEM-IC Feature Processing API using OGC Web Services - Testbed-11 NIEM-IC Feature Processing API using OGC Web Services - 15-047r3 - 2016-01-25 - 15-047r3 - Jeff Harrison - + + Ryan Franz + + The “Multi-Spectral Imagery” extension defines how to encode and store reflected electromagnetic radiation from the infrared wavelengths into a CDB. The portion of the spectrum targeted is between the visible spectrum (current imagery and texture in CDB), and longer wavelength infrared that is primarily emissive and can be simulated based on the material temperature. + 2018-09-20 + 17-080r2 + + CDB Multi-Spectral Imagery Extension + + CDB Multi-Spectral Imagery Extension + 17-080r2 + + + - The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community (IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0 architecture through the development, implementations, test, and robust demonstration making use of IC specifications, Geography Markup Language (GML), and NIEM in a simulated “real-world” scenario. The demonstration scenario begins with NIEM-conformant Information Exchange Packages (IEPs) containing operational data and IC security tags from the Information Security Marking (ISM) and Need-To-Know (NTK) access control metadata, and the Trusted Data Format (TDF) for binding assertion metadata with data resource(s). Those instance documents are deployed on Open Geospatial Consortium (OGC) Web Services to be used by client applications. Access control is based on attributes of the end-user and the instance data. -The assessment included reviewing example IEPDs and performing test and demonstrations using OGC web services, such as Transactional Web Feature Services (WFS-T), Policy Enforcement Points (PEPs) and OGC Attribute Stores to process geographic feature with NIEM components and security tags. The Test and Demonstration included, but was not limited to feature retrieval and transactions. Recommendations to update these information exchanges were provided to reflect NIEM 3.0 architecture and security tags in a ‘NIEM/IC Feature Processing API’. Results from this task helped provide a preliminary architecture for Geo4NIEM in Testbed 11, summarized in other OGC Testbed 11 Engineering Reports. -This task also identified potential change requests to OGC WFS or other OGC Services for handling security information in a federated role-based access control environment. These changes may help the NIEM/IC transform into more agile and customer-centric frameworks driven by collaborative partnerships. This transformation is vital to confronting the security challenges of the future. + Matthes Rieke, Benjamin Pross + OWS-9 CCI Conflation with Provenance Engineering Report + This OGC® Engineering Report describes the architecture of a WPS capable of conflating two datasets while capturing provenance information about the process. The report also provides information about defining and encoding conflation rules and about encoding provenance information. +This Engineering Report was created as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. - + + OWS-9 CCI Conflation with Provenance Engineering Report + 12-159 + 2013-02-05 + + + 12-159 + - - - 07-160r1 - OWS-5 Conflation Engineering Report - - Pete Brennen - 07-160r1 - OWS-5 Conflation Engineering Report - This OGC Engineering Report describes the process of conflation, outlines a framework for conflation and conflation rules services within a service oriented architecture, and describes the implementation of conflation services during the OGC OWS-5 testbed. - - 2008-09-12 + + OGC® PUCK Protocol Standard + + 09-127r2 + OGC® PUCK Protocol Standard + + Tom O’Reilly - + + 2012-01-25 + + 09-127r2 + This standard defines a protocol for RS232 and Ethernet connected instruments. PUCK addresses installation and configuration challenges for sensors by defining a standard instrument protocol to store and automatically retrieve metadata and other information from the instrument device itself. - - Arliss Whiteside + - - - *** Superceded by 06-023r1 - Definition identifier URNs in OGC namespace *** -This Recommendation Paper specifies Universal Resource Names (URNs) for definitions in the - 05-010 - - - 05-010 - URNs of definitions in ogc namespace - 2005-01-26 - URNs of definitions in ogc namespace + + Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile + 10-140r1 + + OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile + 2014-02-26 + + 10-140r1 + Peter Baumann, Stephan Meissl, Jinsongdi Yu + + The OGC Web Coverage Service (WCS) Application Profile – Earth Observation (EO-WCS), defines a profile of WCS 2.0 [OGC 09-110r4] for use on Earth Observation data. - - OWS Context GeoJSON Encoding Standard - 14-055r2 + + Observations and Measurements + 03-022r3 + Observations and Measurements + 2003-02-04 + Simon Cox + + + 03-022r3 + + + This document describes a framework and encoding for measurements and observations. + + + + 20-000r1 + CityGML Urban Planning ADE for i-Urban Revitalization + + - - - - - OGC OWS Context GeoJSON Encoding Standard - 14-055r2 - This standard describes the GeoJSON encoding of the OGC Web Services (OWS) Context conceptual model. This standard defines how to encode an OWS context document that 1.) can be extended to allow a context referencing a fully configured service set, and 2.) can be defined and consistently interpreted by clients. -The OWS Context Document standard (OWS Context) was created to allow a set of configured information resources to be passed between applications primarily as a collection of services (but also potentially in-line content). The objective is to support use cases such as the distribution of search results, the exchange of a set of resources in a Common Operating Picture (COP), or delivery of a set of configured processing services to allow the processing to be reproduced on different processing nodes. -The goal for OWS Context is to replace previous OGC standards and best practices that provide similar capability. Web Map Context (WMC) has been reasonably successful but is limited to working with only Web Map Service (WMS) instances. Other work on the Location Organizer Folder1 (LOF) was also taken into consideration. The concept of OWS Context and the first prototype document was produced as part of OWS Testbed 7 and documented in [OGC10-035r1], Information Sharing Engineering Report. -A principal goal of the OWS Context SWG was to develop encodings that would appeal for use in mass market applications yet also provide facilities for more advanced uses. OWS-7 originally considered the application of existing encoding standards for OWS Context. The OGC Standards Working Group (SWG) has concluded that this standard can have multiple encoding formats and that each encoding format will be described in a separate OGC Extension to the Core model. + 20-000r1 + This OGC Discussion Paper introduces the CityGML Urban Planning Application Domain Extension (ADE) published by the Japanese government for the i-Urban Revitalization (i-UR). +The i-UR is an information infrastructure dedicated for urban planning to contribute to data-driven urban development and urban revitalization. OGC KML has been utilized more than 10 years for i-UR, however, there were huge requirements for use of application-specific semantics information for urban planning and multi-scale structured information by LOD (Levels of Detail). +By using CityGML ADE mechanism, the Urban Planning ADE provides application-specific semantics information integrating with 3D geometry data to visualize and analyze the urban situation. Additionally, the Urban Planning ADE introduces newly extended LOD, LOD-1 (minus one) for nationwide city models and LOD-2 (minus two) for a worldwide city model to visualize global urban activities and study urban structure by integrating geospatial information and statistical grid information. +This paper describes a brief introduction of i-Urban Revitalization, data model of the Urban Planning ADE and data experiment examples to discuss further utilization of the Urban Planning ADE in urban planning applications. - Pedro Gonçalves, Roger Brackin - 2017-04-07 + + Nobuhiro Ishimaru, Chikako Kurokawa, Yuichi Tanaka, Tomohisa Oishi, Kentaro Akahoshi, Tatjana Kutzne + 2020-04-17 + + + CityGML Urban Planning ADE for i-Urban Revitalization - + - Testbed 10 Performance of OGC® Services in the Cloud: The WMS, WMTS, and WPS cases - + 17-036 + Testbed-13: Geospatial Taxonomies Engineering Report - Edric Keighan, Benjamin Pross, Hervé Caumont - This document characterizes the performance and scalability of OGC data services in the Cloud. Three use cases highlighting different geo-processing aspects of OGC data services have been developed, implemented, and benchmarked. Each use case is presented in a separate section of this document with performance results and discussions. + 2018-01-11 + Charles Chen + + 17-036 + + This Engineering Report (ER) documents the Geospatial Taxonomy research activities conducted by the Aviation (AVI) subthread of the Cross Community Interoperability (CCI) thread in OGC Testbed 13. One of the critical factors in the overall usability of services - and System Wide Information Management (SWIM) enabled services in particular - is the ability of a service to be discovered. The ability of a service to be discovered is assured by providing a uniformly interpretable set of service metadata that can be accessed by a service consumer through a retrieval mechanism (e.g., a service registry). Such a set of metadata (commonly referred to as a service description) has been defined by Federal Aviation Administration (FAA) and European Organization for the Safety of Air Navigation (EUROCONTROL) and formalized in a Service Description Conceptual Model (SDCM) [SDCM]. + +The SDCM is currently used in standard service description documents and service registries by both FAA and EUROCONTROL. As part of the effort of enhancing service discovery, both organizations also use a number of categories that can be associated with all services and are generally referred to as taxonomies. The current set of taxonomies used by both EUROCONTROL and FAA categorizes (i.e., meta tags) services based on their availability status, interface model, data product, etc. However, despite the increasing role of OGC services in the SWIM environment, no taxonomies for categorizing services based on geographical coverage or other geospatial characteristics have been defined. This ER documents the work conducted as part of Testbed 13 CCI thread and AVI subthread to identify and classify SWIM-enabled Service Oriented Architecture (SOA) services with geographical taxonomies and the integration thereof into SDCM. + OGC Testbed-13: Geospatial Taxonomies Engineering Report + - Testbed 10 Performance of OGC® Services in the Cloud: The WMS, WMTS, and WPS cases - 14-028r1 + + + 15-042r5 + TimeseriesML 1.2 – XML Encoding of the Timeseries Profile of Observations and Measurements + James Tomkins, Dominic Lowe + + 2018-12-18 + + 15-042r5 + TimeseriesML 1.2 defines an XML encoding that implements the OGC Timeseries Profile of Observations and Measurements, with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of data exchange requirements. + + + OGC TimeseriesML 1.2 – XML Encoding of the Timeseries Profile of Observations and Measurements + + + + + 10-092r3 + NetCDF Binary Encoding Extension Standard: NetCDF Classic and 64-bit Offset Format + + 10-092r3 + - - 2014-10-14 - 14-028r1 + + NetCDF Binary Encoding Extension Standard: NetCDF Classic and 64-bit Offset Format + + This document defines an OGC® Standard for encoding binary representations of space-time varying geo-referenced data. Specifically, this standard specifies the netCDF classic and 64-bit offset file binary encoding formats. This standard specifies a set of requirements that every netCDF classic or 64-bit offset binary encoding must fulfil. + + Ben Domenico + 2011-04-05 - - OWS-8 Digital NOTAM Refactor - AIXM is a GML Application Schema described in UML using the relevant ISO / OGC standards from the 19100 series. The Digital NOTAM Events Specification (DNES) is an extension of AIXM that can describe notices to airmen using the AIXM standard. -This document has been produced in conjunction with the Domain Modelling Cookbook - a practical guide to domain modelling following a series of best practices developed by the CSIRO and other OGC members. -Where possible, documentation of the refactor effort for Digital NOTAM to be compatible with these practices is incorporated into the domain modelling cookbook. - - OWS-8 Digital NOTAM Refactor - 11-106r1 + + + + Volume 10: OGC CDB Implementation Guidance + + 2021-02-26 + + Carl Reed + 16-006r5 + Volume 10: OGC CDB Implementation Guidance + This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. + + + 16-006r5 - 11-106r1 - Rob Atkinson, James Groffen - - 2011-12-19 + + + This Testbed-17 (TB-17) Aviation API Engineering Report (ER) summarizes the implementations, findings and recommendations that emerged from the efforts of building a definition for an Aviation API compliant with the requirements of the OGC Standards Program, and the exploration of the potential of aviation data fusion. + +This ER describes the nine façades built to interface SWIM services and serve aviation data through OGC APIs, the two services built to consume SWIM data and fuse it to generate richer datasets while serving the fused data through OGC APIs, the client application built to display data retrieved from the façades and fusion services, and the development client built to focus on functionality and experimentation. + +Finally, this ER discusses the potential of OGC APIs to help standardize the access to aviation data within the context of the System Wide Information Management (SWIM) program. + Sergio Taleisnik + OGC Testbed-17: Aviation API ER - - - Sam Lavender, Kate Williams, Caitlin Adams, Ivana Ivánová - This OGC Testbed 18 Engineering Report (ER) documents work to develop a foundation for future standardization of Training Datasets (TDS) for Earth Observation (EO) applications. The work performed in the Testbed 18 activity is based on previous OGC Machine Learning (ML) activities. TDS are essential to ML models, supporting accurate predictions in performing the desired task. However, a historical absence of standards has resulted in inconsistent and heterogeneous TDSs with limited discoverability and interoperability. Therefore, there is a need for best practices and guidelines for generating, structuring, describing, and curating TDSs that would include developing example software/packages to support these activities. Community and parallel OGC activities are working on these topics. This ER reviews those activities in parallel with making recommendations. + 2022-01-21 + 21-039r1 + OGC Testbed-17: Aviation API ER + + 21-039r1 + + - Testbed-18: Machine Learning Training Data ER - 22-017 + + + 11-145 + 2014-05-20 + 11-145 + Cyberarchitecture for Geosciences White Paper + George Percivall + - - 2023-03-09 + + + Cyberarchitecture for Geosciences White Paper + The National Science Foundation (NSF) is developing EarthCube” - Towards a National Data Infrastructure for Earth System Science . In a new partnership between GEO and the NSF Office of Cyberinfrastructure, NSF seeks transformative concepts and approaches to create a sustained, integrated data management infrastructure spanning the Geosciences. Meeting the challenges in geoscience research requires innovation and paradigm shifts in cyberinfrastructure. Information technology must advance to meet the emerging approaches to science. A cyber-architecture identifies repeatable patterns, reusable components, and open standards that provide starting point for innovative developments. +This white paper was written by Open Geospatial Consortium (OGC) members and associates to contribute to development of the NSF EarthCube. This document does not represent an official position of the OGC. However, the discussions in this document could very well lead to NSF developments and subsequent OGC documents. Recipients of this document are invited to reply to the authors’ with notification of any relevant patent rights of which they are aware and to provide supporting documentation. + - - - 22-017 - Testbed-18: Machine Learning Training Data ER - - - Testbed-12 Web Feature Service Synchronization - 16-044 - - Panagiotis (Peter) A. Vretanos - This engineering report describes a protocol for synchronizing data between two enterprise servers. While the protocol itself is generic, this engineering report describes its application to web feature servers. - -In the simplest terms, the protocol involves each synchronization peer accessing the other’s Sync resource to get the set of changed objects since the last time the Sync resource was accessed. In the case of web feature servers, the objects are features. The requesting peer then compare that list of changed features with the identically identified features in its data store and performs any necessary changes so that the feature states match. - -Continuing the work done in Testbed-11, this engineering report describes the implementation of a Sync operation in a WFS server that: - -Enhances the Sync operation from Testbed-11 to include an abstract query element where each service type can then substitute their specific query syntax for identifying the specific sub-set of changed features to be synchronized. In the case of the WFS, several query syntaxes may be used including the wfs:Query element and a REST based feature type URI with query parameters. - -Extends the definition of the Sync operation with the addition of a resultType parameter to allow a client to obtain a hit count of the number of features that a Sync operation shall return. - -Shall investigate the proper procedure for handling resource references. Implementing the resolvePath parameter alone is not sufficient to ensure complete data set synchronization. - -Shall investigate concurrency and consistency issues. + + + 2009-07-16 + Annotation of Web Services or data compliant to OGC standards refers to the task of attaching meaningful descriptions to the service and the served geospatial data or processes. In this discussion paper we try to extend the expressiveness of such annotations by including more sophisticated (semantic) descriptions. + 08-167r1 + Semantic annotations in OGC standards + + Semantic annotations in OGC standards - 2017-03-09 - - Testbed-12 Web Feature Service Synchronization - 16-044 + 08-167r1 + + - + + Patrick Maué - - Provides four protocols (GetCapabilities, GetMap, GetFeatureInfo and DescribeLayer) in support of the creation and display of registered and superimposed map-like views of information that come simultaneously from multiple sources that are both remote and heterogeneous. - 01-047r2 - Web Map Service - 2001-06-21 - - + + Testbed-13: NA001 Climate Data Accessibility for Adaptation Planning + 17-022 - + 2018-01-11 + This Engineering Report describes all Testbed-13 activities relating to the Climate Data Accessibility for Adaptation Planning requirements of the National Aeronautics and Space Administration (NASA). It discusses relevant experiences made during implementation including recommendations to the sponsor, and provides resulting standards change requests to the appropriate working groups. Additionally, it develops best practices for data and model integration and serves as a guidance document to work with NASA Earth Science Data System (ESDS) working groups and externally provided data. The added value of this Engineering Report is to improve interoperability and to advance location-based technologies and realize innovations with regards to NASA Climate Data and NASA ESDS objectives. + Guy Schumann + 17-022 + + + OGC Testbed-13: NA001 Climate Data Accessibility for Adaptation Planning + - Web Map Service - Jeff de La Beaujardiere - 01-047r2 - - - OGC® Web Map Tile Service (WMTS) Simple Profile - 13-082r2 - Web Map Tile Service (WMTS) Simple Profile - The Web Map Tile Service (WMTS) Simple profile defines restrictions that limit the flexibility in implementing a WMTS instance. Adding additional requirements has the goal of simplifying the creation of services and clients. By implementing this profile, clients can more easily combine data coming from different services including from other WMTS instances and even from some tile implementations that are not OGC WMTS based, such as some current distributions of OSM. In fact, most of these tiling services are implicitly following most of the WMTS requirements. Many current WMTS services that implement this profile will have to undergo some changes on how tiles are exposed, and a client that is compatible with WMTS 1.0 will be immediately compatible with this profile. The aim is to align the WMTS standard to other popular tile initiatives which are less flexible but widely adopted. - 13-082r2 - 2016-01-19 - - + + 2006-07-27 + Gazetteer Service - Application Profile of the Web Feature Service Implementation Specification + 05-035r2 - - Joan Masó + + Jens Fitzke, Rob Atkinson + + + + Gazetteer Service - Application Profile of the Web Feature Service Implementation Specification + This document defines a Gazetteer Service profile of the OGC Web Feature Service Specification. The OGC Gazetteer Service allows a client to search and retrieve elements of a georeferenced vocabulary of well-known place-names. + 05-035r2 - - OGC Testbed-14: Swath Coverage Engineering Report + + 2013-01-03 + 11-165r2 + CF-netCDF3 Data Model Extension standard + + 11-165r2 + + The OGC netCDF encoding supports electronic encoding of geospatial data, that is, digital geospatial information representing space and time-varying phenomena. +This standard specifies the CF-netCDF data model extension. +This standard specifies the CF-netCDF data model mapping onto the ISO 19123 coverage schema. +This standard deals with multi-dimensional gridded data and multi-dimensional multi-point data. +In particular, this extension standard encoding profile is limited to multi-point, and regular and warped grids; however, irregular grids are important in the CF-netCDF community and work is underway to expand the CF-netCDF to encompass other coverages types, including irregular gridded datasets. + + Ben Domenico, Stefano Nativi + + CF-netCDF3 Data Model Extension standard + - This Engineering Report (ER) presents a summary, description and findings of the Swath Coverage task conducted by the OGC Testbed-14 initiative. - 18-047r3 - - - 18-047r3 - Swath Coverage Engineering Report - - - Eugene Genong Yu, Liping Di - 2019-02-07 - - EarthCube aims to create an integrated system to access, analyze and share information that is -used by the entire geosciences community. The Open Geospatial Consortium (OGC) is an -organization of which more than four hundred companies and agencies are members, whose -purpose is to create open source standards for sharing geospatial and observational information. -The authors of this paper are users of OGC standards in our work in hydrology, meteorology, -climatology, oceanography and in the solid earth sciences, in other words, in key disciplinary -fields that contribute to the Geosciences. Moreover, the OGC has an effective process for -engaging individuals from many countries in standards development and interoperability testing -that encourages them to set aside the roles they play in their home organizations and instead -focus just on what is needed to share a particular class of information across the globe. This -paper examines the hypothesis that an OGC-like process could be useful for broader sharing of -information in the geosciences. - 11-159 - - The Open Geospatial Consortium and EarthCube - 11-159 - The Open Geospatial Consortium and EarthCube - - 2011-10-19 - + + + + 04-014r1 + - - David Maidment, Ben Domenico, Alastair Gemmell, Kerstin Lehnert, David Tarboton, Ilya Zaslavsky - - - - Matthes Rieke - Testbed 10 Report on Aviation Architecture - 14-008 - 14-008 - - OGC® Testbed 10 Report on Aviation Architecture - - This document is a deliverable of the OGC Testbed 10 (Testbed-10). This document describes the -architecture that was implemented in the Testbed-10 Aviation thread. Additionally, it provides -descriptions of all software components involved in the Aviation architecture as well as a -dedicated chapter focusing on the evaluation and design of FIXM 2.0. Here, a special focus lies -on the integration into the data provisioning components, namely the Web Feature and Event -Services. - - - 2014-07-15 - + Spreadsheet of OGC Technical Document Baseline + + Carl Reed, George Percivall + 2004-04-22 + 04-014r1 + OGC Technical Document Baseline + OGC Technical Document Baseline - - Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra - 19-091r1 - - Thomas Gilbert, Carsten Rönsdorf, Jim Plume, Scott Simmons, Nick Nisbet, Hans-Christoph Gruler, Thom - + + + Peter Baumann, Jinsongdi Yu + Web Coverage Service Interface Standard - CRS Extension + 11-053r1 + + + + 2014-03-11 + - + 11-053r1 + This document specifies parameters to the OGC Web Coverage Service (WCS) GetCoverage request that allows a client, a service, or other application to specify the Coordinate Reference System (CRS) in which coverages are delivered. Note that the CRS of the input bounding box is already defined in the OGC WCS Core Implementation Standard [OGC 09-110r3]. + OGC® Web Coverage Service Interface Standard - CRS Extension + + + Location Services (OpenLS): Navigation Service [Part 6] + 03-007r1 + + + OpenGIS + 03-007r1 - Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra - 2020-03-18 - Demand for digital representations of built environments is accelerating and can only be satisfied through greater software interoperability and data integration. The objective of the Integrated Digital Built Environment (IDBE) joint working group is to address this challenge by bringing together experts from the Open Geospatial Consortium and buildingSMART to coordinate the development of the relevant data standards. This document is an output from IDBE in which we describe the state of three of the most prominent built environment standards – CityGML, IFC and LandInfra – and describe some of the problems that hinder their integration; finally, we propose actions points for overcoming these problems. - 19-091r1 - - - OGC User Management Interfaces for Earth Observation Services - P. Denis, P. Jacques - 2014-04-28 - This OGC Best Practice describes how user and identity management information may be included in the protocol specifications for OGC Services. The proposed approach is applicable to the orchestration of EO services, to system of systems and federation scenarios. The approach is meant to be independent from the specific OGC service. The use cases potentially addressed are very wide and in general may cover geospatial services and not only EO (Earth Observation) services. The use cases may range from web map, feature or coverage services, web processing services, to catalogue services. Examples of EO specific use cases are: ordering (Ordering Services for Earth Observation Products [OGC 06-141r6]) and feasibility analysis (OpenGIS Sensor Planning Service Application Profile for EO Sensors [OGC 10 135]). -The document was initially produced during the ESA HMA (Heterogeneous Missions Accessibility) initiative [OR1] and related projects. -This document is not an OGC standard. This document describes how existing specifications from W3C and OASIS can be used in combination to pass identity information to OGC Web services. - + 2003-06-12 + OpenGIS Location Services (OpenLS): Navigation Service [Part 6] + + Tom Bychowski + + + 14-004 + Sensor Observation Service 2.0 Hydrology Profile + GEOWOW Consortium + OGC Sensor Observation Service 2.0 Hydrology Profile - User Management Interfaces for Earth Observation Services - 07-118r9 - - 07-118r9 - - - - - OWS-8 Review of the WXXS exchange schemas - 11-091 - - Richard Martell - 11-091 - OWS-8 Review of the WXXS exchange schemas - 2012-02-09 + This document an interoperable hydrology profile for OGC Sensor Observation Service (SOS) 2.0 implementations serving OGC WaterML 2.0. This development is based on previous activities and results (i.e. Hydrology Interoperability Experiments as well as the European FP7 project GEOWOW). It is guided by the need to overcome mostly semantic issues between different SOS instances serving hydrological data and the according clients. Therefore, this profile focuses on how to use the entities and requests of the standards and covers the necessary technical details. + + 14-004 + 2014-04-15 + + + + - This aim of this review is to assess the the WXXS 1.1.1 exchange schemas for -compliance with ISO 19136:2007 (GML 3.2.1). This international standard stipulates -rules and recommendations regarding the construction of GML application schemas; -these constraints are documented in the following clauses: -(a) Clause 7.1: GML model and syntax -(b) Clause 21: Rules for GML application schemas -(c) Annex A.1: Abstract test suite for GML application schemas - + + OpenGIS Sensor Planning Service Application Profile for EO Sensors - + This SPS EO profile document specifies at a lower level the interfaces and parameters for requesting information describing the capabilities of a Sensor Planning Service dedicated to the EO Sensor domain, for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or cancelling such a request, and for requesting information about further OGC Web services that provide access to the data collected by the requested task. + Sensor Planning Service Application Profile for EO Sensors + 07-018r1 + Philippe M + + 07-018r1 + 2007-08-15 + + - - - - OGC Disaster Pilot: User Readiness Guide - - 2022-05-06 + + OWS-5 GeoRM License Broker Discussion Paper + This document describes a License Broker Service (LB-Service) as specified and implemented in the OWS-5 test bed. The LB-Service provides configurable license models, which may contain configuration parameters to be defined by the licensee. The setting of these parameters affects the actual license to be created by the LB-Service. - OGC Disaster Pilot: User Readiness Guide - 21-075 - Improving the ability of key disaster decision makers and responders to discover, manage, access, transform, share, and exploit location-based and Earth Observation data will enhance decision making and, hopefully, save lives. The OGC Disaster Pilot 2021 has developed a number of prototype capabilities to demonstrate solutions for providing consistent, and reliable information to enable real-time actions to be taken using multiple technologies working together through pre-agreed standards. - -This User Guide describes how the solution works, how users can be part of it, and showcases what can be achieved if everyone is willing to work together and share data and knowledge to improve the information available to those responding to a disaster. + 08-076 + + 2008-09-12 - - 21-075 - Andrew Lavender, Samantha Lavender + OWS-5 GeoRM License Broker Discussion Paper + 08-076 + + + + Rüdiger Gartmann - - Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure - 15-120r5 - Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure - + + OGC CDB, Leveraging GeoPackage Discussion Paper + CDB, Leveraging GeoPackage Discussion Paper + 18-077r2 + Jay Freeman, Kevin Bentley, Ronald Moore, Samuel Chambers, Glen Quesenberry + This paper offers the results of research, design, and prototype efforts to present the OGC standards working group an approach to creating “GeoCDB”—a technology mashing of GeoPackage and OGC CDB—as a deterministic repository of easily read data geospatial datasets suitable for storage, runtime access, and dissemination for live, virtual, constructive, gaming, and mission command (MC) systems. + 2019-01-20 + 18-077r2 - Carl Reed + - 2018-12-19 - - The CDB standard defines a standardized model and structure for a single, “versionable,” virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. - - - 15-120r5 + + + - - 16-036r1 - Testbed-12 Big Data Database Engineering Report - The amount of (geospatial) data collected and transferred is rapidly increasing. The purpose of this ER is to describe options and recommendations for the delivery of large amounts of data as database delivery. This ER therefore describes and evaluates different aspects of this challenge: - -Data management: How to organize large amounts of data so that it can be efficiently accessed through OGC service interfaces? - -Encoding: Transferring large amounts of vector data in XML based formats (e.g. GML, O&M) leads to specific challenges as the parsing of large XML files is often problematic. - -Available implementation: Several software packages exist to handle large amounts of geospatial data. We will investigate to which these approaches are in-line with OGC standards or how standards compliance could be achieved. - -The evaluation and findings in the related Big Data Tile Database Implementation are documented in this ER as well. The objective of this ER is to provide recommendations of how the delivery of large amounts of raster data as database delivery can be considered within OGC specifications and future activities. - 16-036r1 - Testbed-12 Big Data Database Engineering Report - 2017-06-30 - Christian Autermann - + + Surface Water Interoperability Experiment FINAL REPORT + 12-018r2 + This report describes the methods, results, issues and recommendations generated by the Surface Water Interoperability Experiment (SW IE), carried out as an activity of the OGC Hydrology Domain Working Group (HDWG). The SW IE was designed to advance the development of WaterML 2.0 and test its use with various OGC service standards (SOS, WFS, WMS and CSW). A secondary aim was to contribute to the development of a hydrology domain feature model and vocabularies, which are essential for interoperability in the hydrology domain, although these are not the main focus for the IE. + + - + Peter Fitch + 2012-08-27 + 12-018r2 + OGC® Surface Water Interoperability Experiment FINAL REPORT - - Jeff Yutzler - - Release Notes for OGC GeoPackage Encoding Standard v1.3.0 - 18-066r1 - Release Notes for OGC GeoPackage Encoding Standard v1.3.0 - 18-066r1 - + + - + + Stephane Fellah - This document provides the set of revision notes for the existing GeoPackage version 1.3.0 (OGC 12-128r17) and does not modify that standard. - -This document was approved by the OGC membership on 2020-11-26. As a result of the OGC Standards Working Group (SWG) process, there were a number of edits and enhancements made to this standard. This document provides the details of those edits, deficiency corrections, and enhancements. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility. - 2021-02-04 - - - - - - - - 2024-07-30T10:34:05.928276 - 2024-07-30T10:34:04.883138 - - - - 03-029 - - OWS Messaging Framework - - 2003-01-20 - 03-029 - OWS Messaging Framework - This document defines a messaging framework to conduct communications between the OGC web services. It is independent of any transport protocol and any messaging encoding. By using the framework, the service designer could focus only on the message definitions and messaging flows for every action supported by the service, without worry on the messaging transport and delivery. The framework should considerably simplify the implementations of the OGC web services and should enable service chaining. - - Stephane Fellah, Steven Keens - + This OGC® Engineering Report (ER) summarizes the approaches, findings and the results of the Symbology Mediation sub-thread activities of the OGC Testbed-11 Cross Community Interoperability (CCI) Thread. The ER: +• Provides an overview of existing standards relevant to symbology mediation, +• Outlines the approaches adopted during the testbed, +• Describes the conceptual models and services developed during the testbed to address semantic mediation and portrayal of feature information related to Emergency Management and to some extent to the Aviation domain. + + + 15-058 + Testbed-11 Symbology Mediation + 15-058 + OGC® Testbed-11 Symbology Mediation + 2015-11-18 - - OGC 3D Tiles Specification 1.0 - 3D Tiles Specification 1.0 - 18-053r2 + + + + 03-081r2 + + 2003-11-07 + Joshua Lieberman + Web Terrain Service RFC + 03-081r2 - Patrick Cozzi, Sean Lilley, Gabby Getz - + OpenGIS Web Terrain Service RFC - 18-053r2 - - 3D Tiles is designed for streaming and rendering massive 3D geospatial content such as Photogrammetry, 3D Buildings, BIM/CAD, Instanced Features, and Point Clouds. It defines a hierarchical data structure and a set of tile formats which deliver renderable content. 3D Tiles does not define explicit rules for visualization of the content; a client may visualize 3D Tiles data however it sees fit. - -A 3D Tiles data set, called a tileset, contains 3D data organized into a spatial data structure. The primary format for delivering the 3D data is glTF 2.0. Additional formats for geospatial tile data are also specified in this document. These tile formats include Batched 3D Models, Instanced 3D Models, Point Clouds and Composite tiles. - -This document specifies the following elements of a tileset: - -The core data structures for tilesets -Tile formats for delivering 3D data -An implicit representation of tilesets that are organized in quadtrees or octrees -Metadata that may be associated to elements of a tileset on different levels of granularity -Declarative styling which may be applied to tilesets for their visualization -The 3D Tiles specification for tilesets, associated tile formats, metadata, and the associated styling specification are open formats that are not dependent on any vendor-specific solution, technology, or products. - -The majority of the content in this OGC document is a direct copy of the content contained at the 1.1 tag of the 3d-tiles repo. No normative changes have been made to the content. This OGC document does contain content not contained in the 1.1 tag of the 3d-tiles repo. - -Cesium has published the 3D Tiles 1.1 Reference Card as an approachable and concise guide to learning about the main concepts in 3D Tiles, intended to jumpstart developers in adopting 3D Tiles. - - - 2019-01-31 + + This document is a companion specification to the OpenGIS Web Map Service Interface Implementation Specification version 1.1.1 [4], hereinafter WMS 1.1.1. +WMS 1.1.1 specifies how individual map servers describe and provide their map content. The present Web Terrain Service specification describes a new operation, GetView, and extended Capabilities which allow a 3D terrain view image to be requested, given a map composition, a terrain model on which to drape the map, and a 3D viewpoint from which to render the terrain view. A simple attempt is also made to reconcile 2D and 3D viewpoints by allowing the requested 3D area of view to be approximated with a WMS 1.1.1 bounding box - + + + + + + + + + Documents of type Approved Specification Profile + Documents of type Approved Specification Profile + Documents of type Approved Specification Profile - Documents of type Implementation Specification - Draft - Documents of type Implementation Specification - Draft - - Documents of type Implementation Specification - Draft - - Sensor Interface Descriptors - 10-134 - + - Arne Broering, Stefan Below - This document presents the Sensor Interface Descriptor (SID) schema that enables the declarative description of sensor interfaces, including the definition of the communication protocol, sensor commands, processing steps and metadata association. This schema is designed as a profile and extension of SensorML. Based on this schema, SID interpreters can be implemented, independently of particular sensor technology, which are able to translate between sensor protocol and SWE protocols. They establish the connection to a sensor and are able to communicate with it by using the sensor protocol definition of the SID. SID instances for particular sensor types can be reused in different scenarios and can be shared among user communities. The ability of an SID interpreter to connect sensors and Sensor Web services in an ad hoc manner based on the sensor’s SID instance is a next step towards realizing sensor plug & play within the Sensor Web. + 11-095r1 + OWS-8 WCS 2.0 Earth Observation Application Profile Compliance Tests Engineering Report + OWS-8 WCS 2.0 Earth Observation Application Profile Compliance Tests Engineering Report + 2011-12-19 - - 2010-06-30 - - 10-134 - Sensor Interface Descriptors - - - - Pedro Gonçalves - - This OGC discussion paper presents an OpenSearch query protocol extension for the -execution of correlation queries between different Search Feeds. Services that support the -OpenSearch Specification and Correlation extension defined in this document are called -OpenSearch Correlation Services. With the proposed extensions it will be possible to -execute distributed queries with correlation and search criteria defining the results -aggregation. - - 2014-02-24 - 13-068 - OpenSearch Extension for Correlated Search - - OGC OpenSearch Extension for Correlated Search - - 13-068 - + Stephan Meissl, Peter Baumann + + + This Engineering Report describes and evaluates the specification of EO-WCS ATS and the implementation of ETS for use within an OGC SOA processing chain. + 11-095r1 + - - OWS-7 Aviation Architecture Engineering Report - 10-079r3 - 10-079r3 + + This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features. + Volume 4: OGC CDB Rules for Encoding CDB Vector Data using Shapefiles (Best Practice) - - The document describes the architecture that was implemented in the Aviation thread of OWS-7. The document provides an overview of the architecture and describes the implemented components. In addition it discusses “eventing” and notification techniques relevant for the aviation domain. + 2021-02-26 + 16-070r4 + Volume 4: OGC CDB Rules for Encoding CDB Vector Data using Shapefiles (Best Practice) + - - - Thomas Everding - OWS-7 Aviation Architecture Engineering Report - 2010-09-09 + 16-070r4 + + + Carl Reed - - - 07-018 - - - + + - Philippe M - OpenGIS Sensor Planning Service Application Profile for EO Sensors + + Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure + 15-113r5 + Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure - 07-018 - Sensor Planning Service Application Profile for EO Sensors - This Discussion Paper explains how a Sensor Planning Service is organised and implemented for the Earth Observation domain. - 2007-05-17 - - - 2019-10-07 - - OGC API - Features - Part 1: Core + The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. - Clemens Portele, Panagiotis (Peter) A. Vretanos, Charles Heazel - OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks. - -The OGC API family of standards is organized by resource type. This standard specifies the fundamental API building blocks for interacting with features. The spatial data community uses the term 'feature' for things in the real world that are of interest. - 17-069r3 - OGC API - Features - Part 1: Core - - - 17-069r3 - + Carl Reed + 15-113r5 + 2018-12-19 - - + - 99-113 - 99-113 - Topic 13 - Catalog Services - Cliff Kottman - 1999-03-31 - Covers the Geospatial Information Access Services + The OGC Testbed-15 Data Centric Security Engineering Report (ER) discusses the current state of security in protecting data in a geospatial environment. The ER examines the use of encrypted container formats such as NATO STANAG 4778 Information on standard Metadata Binding with metadata as defined in NATO STANAG 4774 Confidentiality Metadata Label Syntax in combination with geospatial data using the encoding for an OGC Web Feature Service (WFS) FeatureCollection structure. This report also makes a recommendation for the creation of new media types to support output container formats such as STANAG 4778. The report then discusses various implementation scenarios in which a STANAG 4778 (eXtensible Markup Language (XML) container maintains encrypted data from author to service to viewer. These implementations use the new OGC API - Features - Part 1: Core with features encrypted using keys supplied by feature authors and users. + 2019-12-19 + + OGC Testbed-15: Data Centric Security + 19-016r1 + 19-016r1 + OGC Testbed-15: Data Centric Security + Michael A. Leedahl - - - Topic 13 - Catalog Services + + - + + Jeff Yutzler + Testbed 12 work evaluates the interoperability of the Common Map API tool with commercial vendor tools supporting GeoPackage. Ideally data can be shared and exchanged between apps on a single device via GeoPackage. The demonstration will show the vector and/or routing data being used by disparate applications. + + + + 16-030 + Testbed-12 Testbed-12 GeoPackage Mobile Apps Integration Engineering Report + 16-030 + Testbed-12 Testbed-12 GeoPackage Mobile Apps Integration Engineering Report + - 05-036 - GeoXACML, a spatial extension to XACML - This OGC document proposes one possible solution for the declaration and enforcement of access -restrictions for object-oriented geodata, available through a Service-based Geo Data Infrastructure. It is the -intension of the author to motivate the requirement for such an access control, give a problem statement, -discuss an alternative approach and describe the solution, based on GeoXACML. - 2005-06-17 - - - - GeoXACML, a spatial extension to XACML - 05-036 + 2017-05-15 - Andreas Matheus - - - 03-036 - Web Map Context Documents - Jean-Philippe Humblet - 2003-01-21 - - - - + + + Sensor Planning Service Implementation Standard + 09-000 + OGC® Sensor Planning Service Implementation Standard + 09-000 + 2011-03-28 - Web Map Context Documents - 03-036 - Create, store, and use state information from a WMS based client application + Ingo Simonis, Johannes Echterhoff + The OpenGIS® Sensor Planning Service Interface Standard (SPS) defines interfaces for queries that provide information about the capabilities of a sensor and how to task the sensor. The standard is designed to support queries that have the following purposes: to determine the feasibility of a sensor planning request; to submit and reserve/commit such a request; to inquire about the status of such a request; to update or cancel such a request; and to request information about other OGC Web services that provide access to the data collected by the requested task. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. + + + - - Numerous and diverse technologies push cities towards open and platform-independent information infrastructures to manage human, natural, and physical systems. The Future Cities Pilot 1 (FCP1), as an OGC Innovation Program initiative, demonstrated how cities can benefit from open standards when used in urban planning workflows. This report details the lessons learned of implementing both the OGC CityGML and the buildingSMART Industry Foundation Classes (IFC) standards for visualizing and processing 3D spatial data when used in urban planning processes. - + + Stephane Fellah + - Future City Pilot 1: Using IFC/CityGML in Urban Planning Engineering Report + 18-094r1 + 18-094r1 + Characterization of RDF Application Profiles for Simple Linked Data Application and Complex Analytic Applications Engineering + OGC Testbed-14: Characterization of RDF Application Profiles for Simple Linked Data Application and Complex Analytic Applicat + + 2019-02-04 + + + This Engineering Report (ER) enhances the understanding of the concept of application profiles (AP) for ontologies based on the Web Ontology Language (OWL) and used by Linked Data (LD) applications. The concept of an Application Profile for Unified Modeling Language (UML) and Extensible Markup Language (XML) schemas, in particular Geographic Markup Language (GML) application profiles, is pretty well-defined and understood within the communities of Open Geospatial Consortium (OGC) and International Organization for Standardization (ISO). Moreover, in the context of Linked Data and ontologies, the term is still ill-defined, as ontologies are defined using an Open World Assumption (OWA), as well as classes and properties are first-class modeling objects in ontology modeling. The work documented in this report includes: + +Definition and characterization of Resource Description Framework (RDF) application profiles for simple linked data applications and complex analytic linked data applications. + +Determination of preliminary techniques for the development of subsets of ontologies to support different types of applications (simple linked data and complex analytic) + +An initial model for defining metadata about application profiles, so they can be searched and discovered by agents. + + + Panagiotis (Peter) A. Vretanos + OGC Vector Tiles Pilot: WMTS Vector Tiles Extension Engineering Report + + - 2017-10-03 + 18-083 + 18-083 + WMTS Vector Tiles Extension Engineering Report - 16-097 - Future City Pilot 1: Using IFC/CityGML in Urban Planning Engineering Report - 16-097 - - Mohsen Kalantari - - - 05-112 - - This document describes Symbology Management System which is a system closely related to OpenGIS Style Management Services (SMS) (described in the document OGC 04-040). Having in mind their identical purpose, the system described in this document will also be referred to as SMS. -The SMS manages styles and symbols and defines their use in the process of producing maps from source GML data. - - 2006-04-19 - 05-112 - Symbology Management - - Milan Trninic - - Symbology Management - - + + 2019-02-11 + The tiling of feature data is an approach that can be used to optimize the delivery vector feature data over the web to create maps. The approach provides a pre-defined shape (i.e. tile) to package vector data. Tiling of vector data enables faster map loads (due to reduced size) and offer flexible styling on the client side with modern, easy-to-use tools. + +This Engineering Report (ER) describes the work done by participants during the Vector Tiles Pilot (VTP) to add Mapbox and GeoJSON vector tile support to Web Map Tile Servers. A summary of other work done in the VTP is presented in the VTP Summary Engineering Report [1]. + +NOTE +This engineering report interchangeably uses both 'tiled feature data' and the colloquial term 'vector tiles'. - - 06-054r1 - Image Geopostioning Service - This document specifies the interface to an Image Geopositioning Service that adjusts the georeferencing coordinate transformations of multiple images. This adjustment is normally done using a photogrammetric triangulation process, although other methods could be used. Such triangulation adjusts the parameter values of the image georeferencing coordinate transformations using a least-squares fitting process to measured image positions with known error statistics. - - 06-054r1 - - 2006-07-12 - + + + 09-076r3 + Uses and summary of Topic 02 - Spatial referencing by coordinates + 09-076r3 Arliss Whiteside - OpenGIS Image Geopostioning Service - - + Uses and summary of Topic 2 - Spatial referencing by coordinates + 2009-09-14 + + This document first discusses the uses for data sharing, and then provides a brief summary, of OGC Abstract Specification Topic 2: Spatial referencing by coordinates. Topic 2 is almost the same as ISO 19111:2007, but includes some corrections. This document includes some best practices for using Coordinate Reference Systems (CRSs). + + + - - 2020-05-06 - This document describes a conceptual model, logical model, and GML/XML encoding schema for the exchange of borehole related data and especially all the elements that are positioned along a borehole trajectory. In addition, this document provides GML/XML encoding instances documents for guidance + + + + + 2008-02-23 + - OGC Borehole Interoperability Experiment Engineering Report - 19-075r1 - + The OpenGIS® Geospatial eXtensible Access Control Markup Language Encoding Standard (GeoXACML) defines a geospatial extension to the OASIS standard “eXtensible Access Control Markup Language (XACML)” [www.oasis-open.org/committees/xacml/]. This extension incorporates spatial data types and spatial authorization decision functions based on the OGC Simple Features[http://www.opengeospatial.org/standards/sfa] and GML[http://www.opengeospatial.org/standards/gml] standards. GeoXACML is a policy language that supports the declaration and enforcement of access rights across jurisdictions and can be used to implement interoperable access control systems for geospatial applications such as Spatial Data Infrastructures. GeoXACML is not designed to be a rights expression language and is therefore not an extension of the OGC GeoDRM Reference Model (Topic 18 in the OpenGIS® Abstract Specification [http://www.opengeospatial.org/standards/as]). + Geospatial eXtensible Access Control Markup Language (GeoXACML) + 07-026r2 + 07-026r2 + Geospatial eXtensible Access Control Markup Language (GeoXACML) + Andreas Matheus, Jan Herrmann + + + + OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0 + 11-073r2 + Debbie Wilson, Ian Painter + 11-073r2 + - 19-075r1 - Borehole Interoperability Experiment Engineering Report - Sylvain Grellet, Eric Boisvert, Bruce Simons, Jean-François Rainaud, Henning Lorenz, Rainer Haener + The scope of this guidelines report is to provide: +1. Overview of the OGC WFS 2.0 standard +2. Recommendations for a minimum set of operations and behaviours that should be supported to ensure consistency across software implementations. +3. Guidance for configuring the WFS 2.0 to retrieve AIXM 5.1 data +4. Summary of potential improvements to WFS/FE 2.0, GML and AIXM 5.1 specifications to better support aeronautical use cases + + 2012-02-09 + OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0 + - - 07-147r2 - OGC KML - Tim Wilson - KML is an XML language focused on geographic visualization, including annotation of maps and images. Geographic visualization includes not only the presentation of graphical data on the globe, but also the control of the user's navigation in the sense of where to go and where to look. - 2008-04-14 - + + 15-003 + David Graham + + Common DataBase Volume 1 Main Body + 15-003 + + OGC Common DataBase Volume 1 Main Body + + - KML - 07-147r2 - - - + The Common DataBase (CDB) Specification provides the means for a single, versionable, simulation-rich, synthetic representation of the earth. A database that conforms to this Specification is referred to as a Common DataBase or CDB. A CDB provides for a synthetic environment repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB can be used as a common on-line (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks; in this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. +The application of CDB to future simulator architectures will significantly reduce runtime-source level and algorithmic correlation errors, while reducing development, update and configuration management timelines. With the addition of the HLA/FOM and DIS protocols, the application of the CDB Specification provides a Common Environment to which inter-connected simulators share a common view of the simulated environment. +The CDB Specification is an open format Specification for the storage, access and modification of a synthetic environment database. The Specification defines the data representation, organization and storage structure of a worldwide synthetic representation of the earth as well as the conventions necessary to support all of the subsystems of a full-mission simulator. The Specification makes use of several commercial and simulation data formats endorsed by leaders of the database tools industry. +The CDB synthetic environment is a representation of the natural environment including external features such as man-made structures and systems. It encompasses the terrain relief, terrain imagery, three-dimensional (3D) models of natural and man-made cultural features, 3D models of dynamic vehicles, the ocean surface, and the ocean bottom, including features (both natural and man-made) on the ocean floor. In addition, the synthetic environment includes the specific attributes of the synthetic environment data as well as their relationships. +A CDB contains datasets organized in layers, tiles and levels-of-detail; together, these datasets represent the features of a synthetic environment for the purposes of distributed simulation applications. The organization of the synthetic environmental data in a CDB is specifically tailored for real-time applications. + + 2015-07-22 - - - 2018-01-11 - - 17-022 - Testbed-13: NA001 Climate Data Accessibility for Adaptation Planning + + + Hector Rodriguez + OGC Testbed-15: Federated Clouds Security Engineering Report + 19-024r1 + 2019-12-20 + + - - This Engineering Report describes all Testbed-13 activities relating to the Climate Data Accessibility for Adaptation Planning requirements of the National Aeronautics and Space Administration (NASA). It discusses relevant experiences made during implementation including recommendations to the sponsor, and provides resulting standards change requests to the appropriate working groups. Additionally, it develops best practices for data and model integration and serves as a guidance document to work with NASA Earth Science Data System (ESDS) working groups and externally provided data. The added value of this Engineering Report is to improve interoperability and to advance location-based technologies and realize innovations with regards to NASA Climate Data and NASA ESDS objectives. - Guy Schumann - 17-022 - OGC Testbed-13: NA001 Climate Data Accessibility for Adaptation Planning - - - - 18-026r1 - Security Engineering Report - OGC Testbed-14: Security Engineering Report - 2019-03-05 - + 19-024r1 + This OGC Testbed-15 Engineering Report (ER) documents the concept for different types of federation through the lens of security. The primary focus of the work documented in this ER is on analyzing how federated membership, resource and access policy management can be provided within a security environment, while also providing portability and interoperability to all stakeholders. + +In the Testbed, a practical approach for providing this functionality was exercised and documented for two administrative domains: One based on a centralized entity (Federation Manager) and the other showcasing a distributed architecture. + OGC Testbed-15: Federated Clouds Security Engineering Report + + + 21-036 + The OGC Testbed-17 Moving Features (MF) task addressed the exchange of moving object detections, shared processing of detections for correlation and analysis, and visualization of moving objects within common operational pictures. This Engineering Report (ER) explores and describes an architecture for collaborative distributed object detection and analysis of multi-source motion imagery, supported by OGC MF standards. The ER presents the proposed architecture, identifies the necessary standards, describes all developed components, reports on the results of all TIE activities, and provides a description of recommended future work items. - 18-026r1 - + + + + OGC Testbed-17: Moving Features ER + 21-036 + OGC Testbed-17: Moving Features ER + Guy Schumann - Juan José Doval, Héctor Rodríguez - This Security Engineering Report (ER) covers several OGC Testbed-14 topics: - -Best practices for the integration of OAuth2.0/OpenID Connect services - -Mediation services for different security environments - -Federated identity management - -Securitization of workflows - -The first two topics are the main focus of this ER. During this Testbed, a server that provides OAuth2.0 and OpenID Connect capabilities was extended with a mediation service that allows for a centralized security authority with users/clients that implement different security standards. - -The remaining two topics will expand on the close relationship between Security, Workflows and Federated Clouds and the respective implementation challenges. On these specific topics, this ER also outlines and provides a proof-of-concept for a simplistic architecture approach that explores one of several Federated Clouds architectures. + 2022-01-21 - - Topic 2 - Spatial referencing by coordinates + + 06-004r4 + Topic 18 - Geospatial Digital Rights Management Reference Model (GeoDRM RM) + + Graham Vowles + + + 06-004r4 + 2007-01-29 + + Topic 18 - Geospatial Digital Rights Management Reference Model (GeoDRM RM) + This document is a reference model for digital rights management (DRM) functionality for geospatial resources (GeoDRM). As such, it is connected to the general DRM market in that geospatial resources must be treated as nearly as possible like other digital resources, such as music, text, or services. It is not the intention here to reinvent a market that already exists and is thriving, but to make sure that a larger market has access to geospatial resources through a mechanism that it understands and that is similar to the ones already in use. - - Topic 2 - Spatial referencing by coordinates - 08-015r2 - - - This document is consistent with the second edition (2007) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2007] - 2010-04-27 - - Roger Lott - 08-015r2 - - - - - - - - - - Maritime Limits and Boundaries Pilot: Engineering Report - 20-013r4 - 2020-07-29 - Jonathan Pritchard - OGC Maritime Limits and Boundaries Pilot: Engineering Report - This document comprises the Engineering Report (ER) and documents the activities under Phase 1 and Phase 2 of the OGC Maritime Limits and Boundaries (MLB) Pilot. - -This Engineering Report details the activities undertaken by participants in the pilot, the data supplied, transformed, and used to demonstrate the pilot’s objectives, and the results of the various interoperability tests performed within the pilot. Also documented here are the various outputs from the pilot activities, where they are directed, and where updates or clarifications are recommended to external standards or other elements of the broader ecosystem. - -The ER documents the journey taken within the project, from its origins as an architectural statement of intent, through to the definition of its core elements (the GML application schema which lends a common language to the data) and the implementation of that schema within COTS, open source and bespoke software elements. The engineering report also summarizes the outputs from the process, any unresolved issues, and potential enhancements for the future. + + - - - 20-013r4 + OGC Testbed-13: Concepts of Data and Standards for Mass Migration Engineering Report + 2018-01-17 + 17-078 + 17-078 + Concepts of Data and Standards for Mass Migration Engineering Report - - - - The OGC Testbed-16 Machine Learning (ML) Training Data Engineering Report (ER) describes training data used for developing a Wildfire Response application. Within the context of the application, this ER discusses the challenges and makes a set of recommendations. The two scenarios for the wildfire use case include fuel load estimation and water body identification. The ML training data described in this ER are based on these two scenarios. Suggestions are also made for future work on a model for ML training dataset metadata, which is intended to provide vital information on the data and therefore facilitate the uptake of training data by the ML community. Additionally, this ER summarizes the discussions and issues about ML training data among the Testbed-16 ML thread participants and draws conclusions and recommendations for future work on the subject. Finally, this ER also links to current Analysis Ready Data (ARD) principles and efforts, in particular in the Earth Observation (EO) community. - Machine Learning Training Data ER - 20-018 - OGC Testbed-16: Machine Learning Training Data ER - - - - - 20-018 - - 2021-01-13 - Guy Schumann - - - Specification of a generic service-oriented architecture integrating the access to, the management and the processing of sensor-related information based upon the emerging standards of the Open geospatial Consortium (OGC), and resulting from the requirements analysis of diverse application domains such as maritime risk management, observation of geo-hazards and monitoring of air quality. - - Specification of the Sensor Service Architecture (SensorSA) - - - Specification of the Sensor Service Architecture (SensorSA) - 09-132r1 - 2009-10-02 - Thomas Usländer (Ed.) - 09-132r1 - - - - - 2018-04-14 - Geography Markup Language (GML) Encoding Standard - with corrigendum - 07-036r1 - - - The OpenGIS® Geography Markup Language Encoding Standard (GML) The Geography Markup Language (GML) is an XML grammar for expressing geographical features. GML serves as a modeling language for geographic systems as well as an open interchange format for geographic transactions on the Internet. As with most XML based grammars, there are two parts to the grammar – the schema that describes the document and the instance document that contains the actual data. -A GML document is described using a GML Schema. This allows users and developers to describe generic geographic data sets that contain points, lines and polygons. However, the developers of GML envision communities working to define community-specific application schemas [en.wikipedia.org/wiki/GML_Application_Schemas] that are specialized extensions of GML. Using application schemas, users can refer to roads, highways, and bridges instead of points, lines and polygons. If everyone in a community agrees to use the same schemas they can exchange data easily and be sure that a road is still a road when they view it. + The objective of the Mass Migration Source Integration effort in OGC Testbed 13 was to understand and document how interoperability tools and practices, including open geospatial and security standards, can enable information exchange on an international level for humanitarian relief and analysis of mass movement of populations. + +This Engineering Report describes how Testbed 13 participants tested and demonstrated situational awareness using Internet and web technologies in a shared information exchange platform. The purpose of this platform was to help realize a Common Operational Picture (COP) for coordinating humanitarian relief activities among nations and organizations. In addition, the platform exercised security-enabled interoperable exchange of messages. -Clients and servers with interfaces that implement the OpenGIS® Web Feature Service Interface Standard[http://www.opengeospatial.org/standards/wfs] read and write GML data. GML is also an ISO standard (ISO 19136:2007) [www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=32554 ]. - OpenGIS Geography Markup Language (GML) Encoding Standard - with corrigendum - 07-036r1 - - - Clemens Portele - - + Jeff Harrison - - 12-159 - Matthes Rieke, Benjamin Pross - - This OGC® Engineering Report describes the architecture of a WPS capable of conflating two datasets while capturing provenance information about the process. The report also provides information about defining and encoding conflation rules and about encoding provenance information. -This Engineering Report was created as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. - - OWS-9 CCI Conflation with Provenance Engineering Report - 2013-02-05 - + + + + XML for Image and map Annotation + 01-019 + + 2001-02-06 + + 01-019 + Defines an XML vocabulary to encode annotations on imagery, maps, and other geospatial data. This vocabulary draws on the Geography Markup Language (OpenGIS + XML for Image and map Annotation + John Evans + + + + 2021-11-29 + 21-055 + July 2021 OGC API Code Sprint Summary Engineering Report + + The subject of this Engineering Report (ER) is a virtual code sprint that was held from July 21st to July 23rd, 2021 to advance the development of the OGC API - Processes draft standard, OGC API - Records draft standard, and the OGC API – Coverages draft standard. An Application Programming Interface (API) is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). - OWS-9 CCI Conflation with Provenance Engineering Report - 12-159 + July 2021 OGC API Code Sprint Summary Engineering Report + + + - + Gobe Hobona, Joana Simoes + 21-055 - - OGC Testbed-16: OpenAPI Engineering Report - 20-033 + + This document lists the design principles and requirements for future versions of a potential architecture for integrating workflows and information models from Computer Aided Design and Building Information Modelling with the principles of the OGC Web Services Architecture. + + 2007-05-16 + OGC Web Services Architecture for CAD GIS and BIM + 07-023r2 + + 07-023r2 + + Paul Cote + + + OGC Web Services Architecture for CAD GIS and BIM + + + 19-040 + WPS Routing API ER - - - 2021-01-13 + WPS Routing API ER + + The goal of this OGC WPS Routing API Engineering Report (ER) is to document the specification of an Application Programming Interface (API) which supports geographic routing. The specification includes two alternative approaches to such an API, one based on the current draft of the OGC API - Processes draft specification and another based on the OGC API principles (and the OGC API - Common draft specification). Both approaches facilitate a common Route Exchange Model. - 20-033 - OpenAPI Engineering Report + Christian Autermann + 2020-01-21 + 19-040 + - Sam Meek - This OGC Testbed 16 Engineering Report (ER) documents the two major aspects of the Testbed 16 OpenAPI Thread. These are: - -A Unified Modeling Language (UML) metamodel that describes OpenAPI and a profile of that model to describe OGC API - Features - Part 1: Core; - -An implementation of a transformation procedure in the ShapeChange open source software. This procedure was designed to transform a UML representation of the OGC API - Features - Part 1: Core model into an OpenAPI 3.0 document. - -The process for creating the model and doing the transformation relied upon the Model Driven Architecture (MDA) approach. MDA takes a platform independent model (PIM) and transforms that model into a platform specific model (PSM). + - + + 2009-07-29 + 08-176r1 + OWS-6 Secure Sensor Web Engineering Report + The main purpose of this Engineering Report is to introduce standards-based security solutions for making the existing OGC Sensor Web Services, as described in the OWS-6 SWE baseline, ready towards the handling of sensors in the intelligence domain. + 08-176r1 + + Andreas Matheus + OWS-6 Secure Sensor Web Engineering Report - Testbed-12 Aviation Architecture Engineering Report - 16-018 - - 16-018 - 2017-06-15 - This Open Geospatial Consortium (OGC)® Engineering Report (ER) describes the architecture implemented in the OGC Testbed 12 Aviation thread. This report provides an overview of the technical architecture for the interoperable exchange of flight and aeronautical information using OGC services. The aviation architecture consists of multiple components developed by the Aviation thread, as well as specialized engineering reports per each work area. This report will provide an introduction to each work area and contain references to applicable reports. This report also describes the Aviation thread demonstration scenarios, outcomes, and benefits. - Charles Chen - Testbed-12 Aviation Architecture Engineering Report - + - - 12-096 - OWS-9: Engineering Report: Use of SWE Common and SensorML for GPS Messaging - This document is an Engineering Report for the OWS-9 Interoperability Test Bed. The focus of the document is discussion and demonstration on the use of SWE Common Data 2.0 encodings to support an interoperable messaging description and encoding for the next generation GPS message streams into and out of the GPS navigation accuracy improvement services. The connection of SWE Common to SensorML 2.0 and the application of SensorML to describe the processing surrounding GPS navigation improvement will also be discussed. + + + Mike Botts - + OpenGIS Sensor Model Language (SensorML) + + Sensor Model Language (SensorML) + 05-086 + 2005-11-21 + 05-086 + + + The general models and XML encodings for sensors. + + + OGC Testbed-16: Federated Security + 20-027 + + + 2021-01-06 + + This OGC Testbed 16 Engineering Report (ER) examines all aspects of security and trust in federated computing environments as defined in the NIST Cloud Federation Reference Architecture [1]. The security and trust requirements are identified. Then possible approaches for achieving security and trust are examined. These approaches range from traditional methods for securing just the basic communications among federated entities to the use of emerging security technologies including federated roots of trust, trust frameworks, blockchain, data-centric security, and zero trust architectures. + OGC Testbed-16: Federated Security - OWS-9: Engineering Report: Use of SWE Common and SensorML for GPS Messaging - 12-096 + 20-027 + Craig A. Lee - - 2013-02-01 - + - - - 2000-05-12 - Geography Markup Language - 00-029 - The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features. - Ron Lake + + + + Observations and Measurements - Part 1 - Observation schema + + The OpenGIS® Observations and Measurements Encoding Standard (O&M) defines an abstract model and an XML schema [www.w3.org/XML/Schema] encoding for observations and it provides support for common sampling strategies. O&M also provides a general framework for systems that deal in technical measurements in science and engineering. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. + 2007-12-26 + Simon Cox + 07-022r1 + + Observations and Measurements - Part 1 - Observation schema + 07-022r1 + + + + Joshua Lieberman + Service Information Model + 03-026 + 03-026 - 00-029 - - - Geography Markup Language - - - InfraGML 1.0: Part 5 - Railways - Encoding Standard - 16-105r2 + SIM specifies and discusses a common information model for OGC Web Services, also known variously or in part as service capabilities or service metadata. + + + 2003-01-17 + + Service Information Model + + + 10-035r2 + OWS-7 Information Sharing Engineering Report + + This Engineering Report describes an investigation and evaluation of various methods of sharing information within a collaborative environment accomplished during the OGC Web Services Testbed, Phase 7 (OWS-7). The intent of the OWS-7 Information Sharing activity was to move toward a standardized method of sharing geospatial data between Integrated Clients and potentially catalogs. This report reviews past OGC work within this area, makes recommendations based on the best parts of previous collaboration techniques, and provides recommendations for encoding documents for use in information sharing. + + + 2010-09-08 - 16-105r2 - This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. -InfraGML is published as a multi-part standard. This Part 5 addresses the Railway Requirements Class from LandInfra. - - Peter Axelsson, Lars Wikström - OGC InfraGML 1.0: Part 5 - Railways - Encoding Standard - + + 10-035r2 + David Rosinger, Stan Tillman - 2017-08-16 - + OWS-7 Information Sharing Engineering Report - - 19-081 - 2021-03-23 - MUDDI v1.1 (Model for Underground Data Definition and Integration) Engineering Report - The Underground Infrastructure Concept Development Study (UICDS) Engineering Report [1] examined the present state of underground infrastructure information (UGII), costs and benefits of that state, as well as future opportunities for an improved state. That report describes a number of candidate models for UGII and recommends a number of follow-on activities, including development of a prototype UGII integration model to support subsequent UGII integration and exchange initiatives. A follow-up workshop and model development effort resulted in another engineering report describing an initial (1.0) version of the conceptual UGII integration model MUDDI (Model for Underground Data Definition and Interchange) [2]. The present updated report describes MUDDI version 1.1. The goal of MUDDI is to serve as the basis for integration of datasets from different models, at the levels of detail required to address application use cases described in [1]. MUDDI as described here is a conceptual model which will serve as the basis for one or more conformant and interchangeable logical and physical implementations such as GML (Geographic Markup Language) or SFS (Simple Features SQL). The current version 1.1 of MUDDI has been updated and refined from the initial version 1.0, but is still intended to serve as an input to the proposed OGC Underground Infrastructure Pilot as well as similar implementations and deployments in realistic application scenarios. The present model is also suitable as input to begin development of a formal conceptual model standard. + + Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage + 16-070r2 + This CDB volume provides the information and guidance required to store vector data and attributes using the Esri Shapefile specification in a CDB data store. All shape types are supported to represent point, line, and polygon features. + + + + 16-070r2 + Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage + + + Carl Reed + 2017-02-23 + + + 00-115 + Topic 15 - Image Exploitation Services + - - MUDDI v1.1 (Model for Underground Data Definition and Integration) Engineering Report - 19-081 + - - Josh Lieberman - + Describes the categories and taxonomy of image exploitation services needed to support the use of images and certain related coverage types. + Cliff Kottman, Arliss Whiteside + + Topic 15 - Image Exploitation Services + 00-115 + + 2000-04-24 - - - - - + + OGC Web Services Common + 03-088r1 + + + 2003-10-16 + This document specifies many of the aspects that are, or should be, common to all or multiple OGC Web Service (OWS) interface Implementation Specifications. These common aspects are primarily some of the parameters and data structures used in operation requests and responses. Of course, each such Implementation Specification must specify the additional aspects of that interface, including specifying all additional parameters and data structures needed in all operation requests and responses. + + + + + OGC Web Services Common + 03-088r1 + Arliss Whiteside - - - Clemens Portele - - 18-021 - 2019-03-06 - OGC Testbed-14 Next Generation APIs: Complex Feature Handling Engineering Report - OGC Web Feature Service (WFS) 3.0 is a revision of the WFS standard that proposes a modernized service architecture, that follows the current Web architecture, has a focus on the developer experience, supports the OpenAPI specification, and modularizes WFS into building blocks for fine-grained access to spatial data that can be used by an Application Programming Interface (API) for data. - -This document reviews the work that proposes a next generation of OGC web services (NextGen services or Next Generation APIs) from the perspective of supporting complex three-dimensional (3D) data or complex data schemas. The goal is to identify the best service solution for these particular needs, whether the results are WFS 3.0 extensions or other approaches. In this context the approach of the NextGen services is not of monolithic web services, but Web API building blocks. This is an important point. The same API should be able to support requirements that currently require separate OGC web services, e.g. a WFS and a 3D Portrayal Service (3DPS). - -The purpose of this work is not to preempt other next-generation discussions taking place in OGC but rather to inform and complement that work. - -The report includes proposals on how to extend the NextGen service architecture with API building blocks for complex data, complex queries and 3D portrayal. WFS 3.0, Part 1, is used as the starting point for the NextGen service architecture. The proposals are based on existing requirements and use cases as well as existing support for developers to simplify implementation. - -The work has found no general issues with migrating current WFS, 3DPS, Web Map Tile Service (WMTS) and Web Map Service (WMS) capabilities to the NextGen architecture. On the contrary, the NextGen approach improves the consistency of the interface and removes redundancies (e.g., between the feature access in WFS and the feature info requests in the other standards). - 18-021 - Next Generation APIs: Complex Feature Handling Engineering Report + + OGC® WCS 2.0 Interface Standard- Core: Corrigendum + 09-110r4 + WCS 2.0 Interface Standard- Core: Corrigendum + + + + + This document specifies how a Web Coverage Service (WCS) offers multi-dimensional cov-erage data for access over the Internet. This document specifies a core set of requirements that a WCS implementation must fulfil. WCS extension standards add further functionality to this core; some of these are required in addition to the core to obtain a complete implementa-tion. This document indicates which extensions, at a minimum, need to be considered in ad-dition to this core to allow for a complete WCS implementation. +This core does not prescribe support for any particular coverage encoding format. This also holds for GML as a coverage delivery format: while GML constitutes the canonical format for the definition of WCS, it is not required by this core that a concrete instance of a WCS service implements the GML coverage format. WCS extensions specifying use of data encod-ing formats in the context of WCS are designed in a way that the GML coverage information contents specified in this core is consistent with the contents of an encoded coverage. + + 2012-07-12 + Peter Baumann + + 09-110r4 + + + Testbed 11 Engineering Report: Implementing Common Security Across the OGC Suite of Service Standards + 15-022 + + 15-022 + OGC® Testbed 11 Engineering Report: Implementing Common Security Across the OGC Suite of Service Standards + Andreas Matheus + + + This OGC Engineering Report (ER) focuses on describing Common Security for all OGC +Web Service Standards. This work was performed as part of the OGC Testbed 11 +activity. + 2015-08-19 - - InfraGML 1.0: Part 3 - Alignments - Encoding Standard - 16-103r2 - - OGC InfraGML 1.0: Part 3 - Alignments - Encoding Standard - - + + - 2017-08-16 - This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. -InfraGML is published as a multi-part standard. This Part 3 addresses the Alignment Requirements Class from LandInfra. + + + + + 05-078 + Styled Layer Descriptor Profile of the Web Map Service Implementation Specification + 2006-04-21 + Styled Layer Descriptor Profile of the Web Map Service Implementation Specification + This Document specifies how a Web Map Service can be extended to allow user-defined styling. Different modes for utilizing Symbology Encoding for this purpose are discussed. + 05-078 + Dr. Markus M + + + + 07-110r2 + Richard Martell + + This profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0.2 specification; it qualifies as a 'Class 2' profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards. + 2008-03-11 + CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW - - Paul Scarponcini - 16-103r2 + + 07-110r2 + CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW + + - - 16-056 - Testbed-12 TopoJSON, GML Engineering Report - Testbed-12 TopoJSON, GML Engineering Report - - 16-056 - Jeff Harrison - 2017-05-15 + + This document is a corrigendum for OGC Document 04-021r3. All changes described herein are published in OGC Document 07-006r1. + + 07-010 + + Revision Notes for Corrigendum for OpenGIS 07-006: Catalogue Services, Version 2.0.2 + 07-010 + 2007-06-19 - + + Doug Nebert - - This OGC document evaluates TopoJSON as an encoding that may be delivered across a common, standard OGC service interface such as WFS. + Revision Notes for Corrigendum for OpenGIS 07-006: Catalogue Services, Version 2.0.2 - - 17-025r2 - Testbed-13: Quality Assessment Service Engineering Report - 17-025r2 - OGC Testbed-13: Quality Assessment Service Engineering Report - 2018-03-05 - - - This Engineering Report (ER) has been produced in conjunction with two other engineering reports from the OGC Testbed 13, the Abstract Data Quality ER [4] and the Data Quality Specification ER [5] to capture status quo, discussions, and results in the context of requirements for data quality assessment for Quality of Service in the Aviation Domain. It will, in particular, provide a Data Quality Assessment Service Specification. Much of the ER is presented in the future tense, using terms such as 'shall', in order to express requirements and constraints on future Data Quality Assessment Service implementations. The service specification includes design patterns, extension mechanisms, and service interface considerations. + + Testbed-13: Executable Test Suites and Reference Implementations for NSG WMTS 1.0 and WFS 2.0 Profiles with Extension + 17-043 + + + This Engineering Report (ER) describes the development of the compliance tests and implementation in GeoServer of the Web Feature Service (WFS) 2.0 and Web Map Tile Service (WMTS) 1.0 National System for Geospatial Intelligence (NSG) profiles. The NSG of the United States (US) National Geospatial Intelligence Agency (NGA) is the combination of technologies, policies, capabilities, doctrine, activities, people, data and communities needed to produce geospatial intelligence (GEOINT) in an integrated, multi-intelligence, multi-domain environment. The work can be grouped into four main topics: -In recent years, the concept of data quality has generated a notable interest among System Wide Information Management (SWIM) [17] implementers, both organization-specific and global. In the context of SWIM — and Service Oriented Architecture (SOA) implementations in general — data quality pertains to two major use cases, service advertising and service validation: +critical review of the NSG profiles for WFS 2.0 and WMTS 1.0 -Service advertising -a service makes known to a potential consumer the quality of the data provided by the service. Based on this information, the consumer can determine whether or not the service meets its needs. +implementation of the profiles in GeoServer -Service validation -assurance is given that the quality of the data provided by a service is consistent with the quality that is explicitly defined in a service contract or any kind of agreement that may exist between a service provider and service consumer. +validation of the implementation using OGC Compliance tests and tools -Both use cases share two common preconditions: +lessons learn during the implementation of these profiles and their validation -An unambiguous definition of the concept of data quality exists. +Both NSG profiles are Class 2 profiles. WMTS profiles OGC WMTS 1.0. WFS profiles the DGIWG Profile of OGC WFS 2.0. The first topic provides a review of these profiles along with a description of the main extensions and restrictions introduced by them. -A set of measurable parameters that allow specifying data quality is defined. +The second topic covers the implementation of the NSG profiles in GeoServer. It describes the software architecture and technical decisions, along with the deployment and configuration of the server. -These are tasks that were performed as part of Testbed 13. The findings of the tasks are documented in the Abstract Data Quality ER (FA001)[4] and the Data Quality Specification ER (FA002)[5]. +The third topic covers the validation process of the implementation using OGC validation (sometimes referred to as CITE) tests and tools. It also covers how the tests can be run and how to configure GeoServer for these tests. + +The last topic contains an evaluation of the work, reached goals, lessons learned and the best practices that can be applied in future work. + 17-043 + 2018-01-08 + Nuno Oliveira - Aleksandar Balaban - - - - - - - - OGC Vector Tiles Pilot: Summary Engineering Report - 18-086r1 - Sam Meek - 2019-02-15 - OGC Vector Tiles Pilot: Summary Engineering Report - 18-086r1 - - This OGC Engineering Report (ER) provides the summary findings resulting from completion of the OGC Vector Tiles Pilot (VTP or Pilot). The requirements for the Pilot were generated from a combination of sponsor input and analysis of typical use cases for tiling of vector feature data across the OGC Standards Baseline and related standards. The driving use case for this activity was the visualization of feature data on a client. The three main scenarios considered were consumption of tiled feature data by a web client, a desktop client and a mobile client. As a standards body, the OGC already has standards that fit these use cases. These are; Web Map Tile Service 1.0 (WMTS) for a web client, and GeoPackage 1.2 for a mobile client. Web Feature Service (WFS) 3.0 is suitable for a desktop client and has an in-built method to support tiling, but not specifically for tiled feature data such as that explored in the VTP. One of the purposes of the Pilot was to produce demonstration implementations to support tiled feature data using WFS 3.0, WMTS 1.0 and GeoPackage 1.2 that can be validated by Technology Integration Experiments (TIEs). The draft extension to these standards helped define a draft Conceptual Model for tiled feature data in support of visualization. The Conceptual Model formally captures the requirements for component implementations and rationalizes them into a model documented in the Unified Modeling Language (UML). + OGC Testbed-13: Executable Test Suites and Reference Implementations for NSG WMTS 1.0 and WFS 2.0 Profiles with Extension + + + This OGC Abstract Specification (AS) defines a general parameterization of surface deformation models. -The ER provides an overview of each of the components, their implementation decisions and the challenges faced. The components are presented as draft extensions to existing standards. The WFS standard is currently in a major revision cycle and is transitioning away from services to a resource-oriented architecture. This transition has implications for access to tiled feature data. This offers options of access to pre-rendered tiles, or to tiles created using WFS 3.0 query functionality. The current WMTS standard only offers access to the pre-rendered tiles and much of the work is therefore about defining and supporting tiled feature data as a media type. The OGC GeoPackage standard is more complex as it attempts to ship all of the tiled feature data in a self-contained package aimed at environments that have Denied, Degraded, Intermittent or Limited (DDIL) bandwidth. DDIL is an important use case for GeoPackage as most normal web services do not function without connectivity. The military, first responders and other groups who work in challenging operational environments require a capability to ship, store and distribute geospatial data in an efficient, modern manner. The combination of GeoPackage and tiled feature data offers the means to supply detailed geospatial data in a portable fashion to satisfy many DDIL use cases. GeoPackage also offers the majority of the future work as it attempts to store information such as styling and attribution separately to the geometries to take advantage of a relational database structure. +All objects on the surface of the Earth are moving. Apparently fixed features such as buildings are moving with the Earth’s crust, being subject to ongoing plate tectonic movement and episodic deformation events such as earthquakes. -When this project was initiated, the term vector tiles was used throughout. However, as the project progressed, the participants agreed that the term tiled feature data was more appropriate than the colloquial term of vector tiles. This engineering report therefore interchangeably uses both tiled feature data and vector tiles to refer to the approach of tiling vector feature data. +Increasingly, applications and users rely on global positioning methods, such as Global Navigation Satellite Systems (GNSS) observations, to precisely determine the coordinates of features. The resulting coordinates are then stored in databases and used in a wide range of applications, such as Geographic Information Systems (GIS). However, the coordinates from GNSS are referenced to global reference frames and coordinate reference systems (CRSs). In these reference frames the coordinates of apparently fixed objects are continually changing. - - - - 07-152 - FedEO Pilot Engineering Report (07-152) - 07-152 - FedEO Pilot Engineering Report - - - - - - 2008-01-21 - This document was developed during the FedEO - GEO AIP initiative of the OGC. It was contributed by the organizations involved in the Earth Observation and Natural Resources and Environment Domain Working Group (EO/NRE DWG) in the OGC Specification Program. The document describes recommendation for architecture and specification that enables interoperability - - Corentin Guillo - - - OGC Testbed-17: Features and Geometries JSON CRS Analysis of Alternatives Engineering Report - Features and Geometries JSON CRS Analysis of Alternatives Engineering Report - 21-018 - - - - - - One of the primary requirements for the OGC Testbed-17 Features and Geometries JSON task is to define an extension or profile of GeoJSON that supports encoding spatiotemporal data in Coordinate Reference Systems (CRS) other than the GeoJSON default of the World Geodetic System 1984 (WGS 84) datum, with longitude and latitude units of decimal degrees (CRS84). +This creates a challenge for the geospatial and positioning community: How to account for this movement when comparing data sets observed at different times, or how to locate an object observed in the past. -This OGC Testbed 17 (TB17) Engineering Report (ER) presents the various alternatives considered for declaring CRS information in a Features and Geometries JSON (JSON-FG) file. JSON-FG is an OGC extension to GeoJSON that, among other things, adds support of coordinate reference systems other than the CRS84 default. One of the alternatives was selected to be the mechanism for declaring CRS information in a JSON-FG document and is fully described in the “OGC Testbed-17: OGC Features and Geometries JSON Engineering Report” (OGC 21-017r1). +This problem is generally addressed in one of two ways: -This ER was submitted to the OGC Features and Geometries JSON Standards Working Group so that the work in TB17 can inform their task of developing and documenting a Features and Geometries JSON standard. - 21-018 - - Panagiotis (Peter) A. Vretanos - 2022-02-08 - - - - Feature data tiling, colloquially referred to as 'vector tiling', is a method that defines how large vector geospatial datasets can be systematically split into subsets or tiles [1]. Feature data tiling allows for a variety of use-cases, such as creating online maps, quickly accessing large vector data sets for geoprocessing and creating download-services. For instance, a map created from tiled feature data consists of one or more layers of vector data organized into tiles of features and rendered on the client-side using an associated style. In contrast, raster tiles are delivered as tiled images that have been rendered on the server-side. +Defining a reference epoch for the CRS of coordinates held in the GIS, often by defining a CRS with a reference epoch, or +Using a CRS which is fixed relative to the surface of the Earth. +In practice there is little difference between these two approaches. Neither the position at a reference epoch, nor the coordinates in a static CRS, can be directly measured by global positioning methods. -NOTE -This engineering report interchangeably uses both 'tiled feature data' and the colloquial term 'vector tiles'. - 2019-02-11 - - - 18-076 - - Tiled Feature Data Conceptual Model Engineering Report - 18-076 - OGC Vector Tiles Pilot: Tiled Feature Data Conceptual Model Engineering Report - - - Jens Ingensand, Kalimar Maia - - - Open Source and Open Standards - - 11-110 - This article is a White Paper jointly published by OGC and OSGeo. It was approved as an official joint OSGeo and OGC White Paper by the OSGeo Board of Directors in their 2011-05-05 Board meeting. -The text was collaboratively edited, reviewed and finalized by more than a a dozen active OSGeo and OGC members. Thanks especially to Gavin Fleming, Lance McKee, Markus Neteler, Athina Trakas, Michael Gerlek, Adrian Custer, Jeff McKenna, Cameron Shorter, Carl Reed, Frank Warmerdam, Steven Ramage, Daniel Morissette, Arnulf Christl and others for their contributions. -Please feel free to add comments, criticisms, links to other concise definitions on the associated Talk page: http://wiki.osgeo.org/wiki/Open_Source_and_Open_Standards. - Open Source and Open Standards - 11-110 - - - Arnulf Christl and Carl Reed +Propagating the observed coordinates to a reference epoch, or transforming to a static CRS, requires a deformation model — a mathematical model of the deformation of the Earth’s surface. + +Common uses of a deformation model include: + +Determining the current location of an object based on historic measurement of its location, +Propagation of the current observed location of an object to the reference epoch of a static CRS, +Determining the spatial relationship of data sets observed at different times, and +Predicting the location of an object at some future time. +Currently, many national geodetic agencies have developed or are planning to develop regional deformation models. However, the current models generally use customized formats and software developed by each agency. + +This AS describes a way of parameterizing a deformation model such that it can be encoded into a data set and used in software for coordinate operations. The AS defines how to calculate the displacement of a point between two different epochs. It provides a common understanding between producers of deformation models and developers of software about what the deformation is and how it will be used. + +This AS will allow users of compliant software applying a compliant deformation model to be confident that the model is being used as intended by its producers. - - 2011-08-11 - - - - Topic 7 - Earth Imagery - - Topic 07 - Earth Imagery - 99-107 - - Cliff Kottman - This Topic Volume will provide essential and abstract models for technology that is already used widely (but not interoperably) across the GIS landscape. This technology properly depends on the more general technology that supports Coverages. - - 99-107 - 1999-03-31 - + Topic 24 - Functional Model for Crustal Deformation + 22-010r4 + + 22-010r4 + Chris Crook + + 2024-04-29 + + Topic 24 - Functional Model for Crustal Deformation - - 14-014r3 - Catalogue Services Specification - HTTP protocol binding - Abstract Test Suite - - See OGC 12-176r7 -- OGC® Catalogue Services Specification - HTTP Protocol Binding. - 2016-06-10 - - - OGC® Catalogue Services Specification - HTTP protocol binding - Abstract Test Suite + + 2007-01-18 + 05-077r4 + Symbology Encoding Implementation Specification + + The OpenGIS® Symbology Encoding Standard (SES) defines an XML language for styling information that can be applied to digital geographic feature and coverage data. SE is independent of any OGC Web Services descriptions and could therefore be used to describe styling information in non-networked systems such as desktop geographic information systems. + + Dr. Markus Mueller + 05-077r4 - - 14-014r3 + OpenGIS Symbology Encoding Implementation Specification + + - Lorenzo Bigagli, Doug Nebert, Uwe Voges, Panagiotis Vretanos, Bruce Westcott - + + + + REST architectural principles are associated with optimal functioning of the Web but their manifestation in geospatial Web services standards is not straightforward. This OGC Engineering Report (ER) examines their use both in existing OGC Services standards and in new or revised service standard proposals, some of which were implemented during OGC Testbed 11. The ER then defines possible uniform practices for developing bindings or interaction styles for OGC Web services that appropriately leverage REST principles. + 15-052r1 + OGC® Testbed 11 REST Interface Engineering Report + 15-052r1 + Testbed 11 REST Interface Engineering Report + Frédéric Houbie + + + 2016-01-18 + + + Joint OGC OSGeo ASF Code Sprint 2021 Summary Engineering Report + 21-008 + 21-008 + 2021-04-12 + - 05-019 - Web 3D Service - 05-019 - The Web 3D Service is a portrayal service for three-dimensional geodata, delivering graphical elements from a given geographical area. In contrast to the OGC Web Mapping service (WMS) and the OGC Web terrain service (WTS) 3D scene graphs are produced. These scene graphs will be rendered by the client and can interactively be explored by the user. The W3DS merges different types (layers) of 3D data in one scene graph. - - Web 3D Service - 2005-02-02 - Udo Quadt, Thomas Kolbe - - + + The subject of this Engineering Report (ER) is a code sprint that was held from 17 to 19 February 2021 to advance support of open geospatial standards within the developer community, whilst also advancing the standards themselves. The code sprint was hosted by the Open Geospatial Consortium (OGC), the Apache Software Foundation (ASF), and Open Source Geospatial Foundation (OSGeo). The event was sponsored by Ordnance Survey (OS) and GeoCat BV, and held as a completely virtual event. + Gobe Hobona, Angelos Tzotsos, Tom Kralidis, Martin Desruisseaux + Joint OGC OSGeo ASF Code Sprint 2021 Summary Engineering Report + + + - - - OGC® Testbed 10 CCI Profile Interoperability Engineering Report - This Engineering Report was prepared as a deliverable for OGC Testbed 10, an initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Cross Community Interoperability (CCI) thread within the testbed. The work has been commissioned in order to inform geospatial information frameworks of the Defence Geospatial Information Working Group (DGIWG), National System for Geospatial Intelligence (NSG) of the US National Geospatial Intelligence Agency (NGA) and the UK Ministry of Defence (MOD). -The Engineering Report presents an analysis and assessment of interoperability between DGIWG, NSG and UK MOD profiles of Web Map Service (WMS) and Web Feature Service (WFS) standards of the OGC. The engineering report also presents findings from the implementation of the reference profiles. - - Gobe Hobona, Roger Brackin - 2014-04-28 - 14-021r2 - Testbed 10 CCI Profile Interoperability Engineering Report - 14-021r2 + + 09-006 + OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS + + Keith Pomakis + OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS + 09-006 - - + 2009-08-05 + + + This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the development of SOAP/XML and REST interfaces for the Web Map Tiling Service (WMTS). - - 17-038 - Jeff Harrison - OGC Testbed-13: Fit-for-Purpose Engineering Report - The objective of the Fit for Purpose (FFP) effort in Testbed 13 was to develop and test filters and encodings in a platform that can ease the work of end-users, especially those who are not expert in dealing with geospatial data and satellite imagery. The platform was demonstrated in a scenario that showed how these filters can enable information exchange for humanitarian relief and analysis of mass movement of populations. - -This section provides a summary of the interoperability tools and practices used by Testbed 13 participants in this platform. It includes descriptions and testing results of filters and encodings to help simplify access to satellite imagery. This technology was tested in a scenario that showed how OGC-based services, encodings, filters and applications can help coordinate humanitarian relief activities among nations and organizations. - Testbed-13: Fit-for-Purpose Engineering Report - 17-038 + + 09-064r2 + OWS-6 Sensor Web Enablement (SWE) Engineering Report - + 2009-09-11 + + OWS-6 Sensor Web Enablement (SWE) Engineering Report + 09-064r2 - 2018-01-18 - - - - - 2015-07-22 - - - Spatial Data on the Web Use Cases & Requirements - 15-074 - Frans Knibbe, Alejandro Llaves - - This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC. - 15-074 + Ingo Simonis + This OGC® document summarizes work completed in the OWS-6 Sensor Web Enablement (SWE) thread. - - Spatial Data on the Web Use Cases & Requirements - - - - - - - - - + + 2012-05-15 + + + 12-018r1 + Surface Water Interoperability Experiment FINAL REPORT + 12-018r1 + + This report describes the methods, results, issues and recommendations generated by +the Surfacewater Interoperability Experiment (SW IE), carried out as an activity of the +OGC Hydrology Domain Working Group (HDWG). The SW IE was designed to +advance the development of WaterML 2.0 and test its use with various OGC service +standards (SOS, WFS, WMS and CSW). A secondary aim was to contribute to the +development of a hydrology domain feature model and vocabularies, which are +essential for interoperability in the hydrology domain, although these are not the main +focus for the IE. + - Documents of type Request for Comment - deprecated - Documents of type Request for Comment - deprecated - Documents of type Request for Comment - deprecated - - - - + Peter Fitch + Surface Water Interoperability Experiment FINAL REPORT - The design of core OGC Web Services (OWS) does not entertain the possibility of network unavailability, internet unavailability, or disconnected clients and datastores. Deployments of these services, and the clients that consume them, often happen in networking environments that have limited bandwidth, sporadic connectivity and no connection to the internet. This Engineering Report (ER) focuses on situations of Denied, Degraded, Intermittent, or Limited Bandwidth (DDIL). Due to these DDIL networking limitations, OWS services and clients may not be capable of effective data exchange and interpretation due to a reliance on external resources and always-on networks. - -This ER concerns the behavior of common OWS services when used in DDIL environments. The ER documents proposed practices/considerations for implementation of these services to support these environments. The ER also describes software modules or extensions that might mitigate the effects of these environments on both clients and services. - -This ER intends to guide client and service implementation, as well as deployment strategies for these challenging environments. - - + + - 2018-02-22 - Testbed-13: Disconnected Networks Engineering Report - 17-026r1 - OGC Testbed-13: Disconnected Networks Engineering Report + OGC® Testbed 10 OWS Context in NIEM Engineering Report + This Engineering Report was prepared as a deliverable for OGC Testbed 10, an initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Open Mobility thread within the testbed. +The Engineering Report describes and evaluates options for integrating OWS Context documents in requests for information based on the National Information Exchange Model (NIEM). + - Rob Cass + + Testbed 10 OWS Context in NIEM Engineering Report + 14-017 + 2014-04-28 + Gobe Hobona, Roger Brackin + 14-017 - 17-026r1 + - - The OGC Testbed-18 initiative included a discussion exploring the future of open science and building energy interoperability with the task of developing a set of best practices to make the data processing services of Exploitation Platforms both reproducible and follow the FAIR data principles. - -Portability and reproducibility are key factors for the long-term scientific impact of Earth Observation (EO) data processing applications provided by Exploitations Platforms. The EO application developers lack the tools and guidance to preserve all the elements, algorithms, software, and data resources used to produce the results. Without these elements, reproducibility becomes resubmission within the platform and only while the same platform resources such as data are preserved and available. - -This Testbed 18 Engineering Report defines a list of requirements and respective best practices to support reproducible Earth Observation science covering the different resources of the Earth Observation Exploitation Platforms such as publications, data, services, products, information, software, or computing environments. - - - 22-031r1 + + + OWS-6 Symbology Encoding (SE) Changes ER - 2023-01-03 - Testbed-18: Reproducible FAIR Best Practices Engineering Report - - Pedro Gonçalves - - 22-031r1 - Testbed-18: Reproducible FAIR Best Practices Engineering Report + Craig Bruce + OWS-6 Symbology Encoding (SE) Changes ER + 09-016 + 2009-09-11 + + 09-016 + This OGC® document reports the results achieved in the Decision Support Services (DSS) subtask of the OWS-6 testbed initiative as it relates to the extension of the OGC Symbology Encoding (SE) symbology format for improved capability and harmonization with ISO 19117 symbology, International Hydrographic Organization S-52 symbology, USGS Topomap symbology, and Homeland Security Emergency Management symbology. + + + + + OGC InfraGML 1.0: Part 4 - LandInfra Roads - Encoding Standard + Paul Scarponcini + This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. +InfraGML is published as a multi-part standard. This Part 4 addresses the Road and RoadCrossSection Requirements Class from LandInfra. + 2017-08-16 + 16-104r2 + InfraGML 1.0: Part 4 - LandInfra Roads - Encoding Standard + 16-104r2 - + + + + + - - Arthur Na, Mark Priest - + + 12-128r18 + GeoPackage Encoding Standard + + + 12-128r18 + OGC® GeoPackage Encoding Standard + + + + Jeff Yutzler + This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. + + 2021-11-16 + + + + + + Arne Schilling, Benjamin Hagedorn, Volker Coors + 2012-08-22 + 12-075 + 3D Portrayal Interoperability Experiment FINAL REPORT + 12-075 - Sensor Observation Service - 05-088r1 - - A Sensor Observation Service provides an API for managing deployed sensors and retrieving sensor data. Whether from in-situ sensors (e.g., water monitoring) or dynamic sensors (e.g., satellite imaging), measurements made from sensor systems contribute most of the geospatial data by volume used in geospatial systems today. - - 05-088r1 - Sensor Observation Service + This document describes the results of an OGC Interoperability Experiment (IE) on the portrayal of 3D geospatial information. It contains technical details on processing 3D information in an OGC service environment as well as best practices on how to portray large data sets in urban planning scenarios, taking into account architectures and capabilities of interactive 3D graphics. Especially Web 3D Service and Web View Service, two draft standards (published as OGC discussions paper), have been in the focus of 3DPIE. - 2006-01-18 + OGC 3D Portrayal Interoperability Experiment FINAL REPORT - - CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW - Richard Martell - - 07-110r4 - CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW - + + 13-057r1 + 13-057r1 + Web Coverage Service Interface Standard – Transaction Extension + - - This profile is based on the HTTP protocol binding described in Clause 10 of the Catalogue 2.0.2 specification; it qualifies as a ‘Class 2’ profile under the terms of ISO 19106 since it includes extensions permitted within the context of the base specifications, some of which are not part of the ISO 19100 series of geomatics standards. + - 2009-02-05 - 07-110r4 - + 2016-11-17 + OGC Web Coverage Service Interface Standard – Transaction Extension + + Peter Baumann + This OGC Web Coverage Service (WCS) – Transaction Extension (in short: WCS Transaction) defines an extension to the WCS Core [OGC 09-110] for updating coverage offer­ings on a server. + +This WCS Transaction standard defines three requests: + +InsertCoverage for adding a coverage provided as parameter to the WCS server’s cov­erage offering. After successful completion of the insert request, this coverage will be accessible for all WCS operations. +DeleteCoverage for entirely removing a coverage. The coverage is identified by its coverage id passed in the request, from the WCS server’s coverage offering. After successful completion of this request, this coverage will not be accessible through any WCS operation. However, subsequently a new coverage may be created using the same identifier; such a coverage will bear no relation to the one previously deleted. +UpdateCoverage for modifying parts of a coverage existing in a WCS server’s coverage offering. The coverage is identified by its coverage id passed in the request. As per the OGC Coverage Implementation Schema [OGC 09-146r2], all updates must maintain internal consistency of the coverage. +All requests defined in this Transaction Extension adhere to the ACID[1] (atomicity, consistency, isolation, durability) concepts of database transactions. + +The extension name, Transaction, traces back to the database concept of transactions, which has been adopted here. + - - 11-097 - OWS-8 AIXM 5.1 Compression Benchmarking - - - 11-097 - AIXM stands today for the de-facto standard for Aeronautical Information Publication, used by air control service providers from Europe, USA and Australia. With version 5.1, it reaches a level of maturity allowing the support of Digital NOTAMs, as the first official version of these messages was published this year. -In a near future, AIXM will be carried inside WFS requests but also into notification messages along WS event services. This last channel will be the one dedicated to D-NOTAMs. As D-NOTAM is aimed at aircrafts pilots, their transmission to the aircraft will use air/ground data link. Today, datalink communications lack bandwidth and future datalink will still have a limited capacity. - - - Jérôme JANSOU, Thibault DACLA - - 2011-12-19 + + Compliance Test Engine Interoperability Program Report + Jennifer Marcus, Chuck Morris - - OWS-8 AIXM 5.1 Compression Benchmarking - - - 11-086r1 - Jan Herrmann, Andreas Matheus - 11-086r1 - OWS-8 Aviation Thread - Authoritative AIXM Data Source Engineering Report - - OWS-8 Aviation Thread - Authoritative AIXM Data Source Engineering Report + 07-012 + Compliance Test Engine Interoperability Program Report + 2007-09-04 + + 07-012 + + + As a work item in the OWS4/Conformance and Interoperability Test and Evaluation (CITE) project, Northrop Grumman Information Technology (NGIT) provided an open source web services compliance engine. NGIT refers to this engine as the Test Evaluation And Measurement (TEAM) Engine. It executes scripts written in Compliance Test Language (CTL), a grammar also developed by NGIT. This IPR describes TEAM Engine in detail and provides information on how it was used in OWS-4/CITE. + + + 2019-02-04 - 2012-01-25 - This engineering report describes how to provide access control for WFS-T 2.0 instances -in the OWS-8 Authoritative AIXM Data Source scenario. - - - - Jeff Yutzler - This document provides the set of revision notes for the existing OGC Implementation Standard GeoPackage version 1.1 (OGC 12-128r12) and does not modify that standard. -This document was approved by the OGC membership on <insert approval date here>. As a result of the OGC Standards Working Group (SWG) process, there were a number of edits and enhancements made to this standard. This document provides the details of those edits, deficiency corrections, and enhancements. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility. - - 15-123r1 - Geopackage Release Notes + 18-091r2 + Application Schemas and JSON Technologies Engineering Report + - + Johannes Echterhoff + 18-091r2 - - - 2016-02-16 - 15-123r1 - Geopackage Release Notes + This Engineering Report (ER) enhances the understanding of the relationships between data exchange based on Geography Markup Language (GML), JavaScript Object Notation (JSON), and Resource Description Framework (RDF) for future web services, e.g. Web Feature Service (WFS) 3.0. The work documented in this report: + +contributes to the ability to bridge between technology-dependent alternate representations of “features” (real-world objects), and to consistently employ alternate encoding technologies (Extensible Markup Language (XML), JSON, RDF) to exchange information about “features”; and + +determines principled techniques for the development of JSON-based schemas from ISO 19109-conformant application schemas. + + + OGC Testbed-14: Application Schemas and JSON Technologies Engineering Report - - - + + 06-104r4 + Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option - This OGC Engineering Report provides guidelines for dealing with geospatial -annotations in OGC standards. It proposes a generic data model and a set of mappings -into different popular encodings This OGC® document is applicable to OWS context, -GMLJP2 and any other standards that can require annotations. - - - 14-002 - Joan Masó and Raj Singh - 14-002 - Testbed 10 Annotations Engineering Report - - 2014-07-15 - OGC® Testbed 10 Annotations Engineering Report - - - OGC GeoPackage WKT for Coordinate Reference Systems Extension - 21-057 - This document is a revision to the GeoPackage WKT for Coordinate Reference Systems Extension that previously was published as Annex F.10 of the GeoPackage Encoding Standard 1.3.0 (OGC 12-128r17). This document replaces Annex F.10. The extension defines how to encode coordinate reference systems (CRS) in GeoPackages using the ISO/OGC Well-known text representation of coordinate reference systems [2019] (CRS WKT2) Standard. Specifically, this revision adds coordinate epochs to the encoding of coordinate reference systems in a GeoPackage. + The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. - + OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option + 06-104r4 + + John Herring + 2010-08-04 + + + + GeoSPARQL - A Geographic Query Language for RDF Data + 11-052r4 + This standard defines a set of SPARQL extension functions [W3C SPARQL], a set of RIF rules [W3C RIF Core], and a core RDF/OWL vocabulary for geographic information based on the General Feature Model, Simple Features [ISO 19125-1], Feature Geometry and SQL MM. + Matthew Perry, John Herring + OGC GeoSPARQL - A Geographic Query Language for RDF Data + 2012-06-12 - 2022-10-14 - Jeff Yutzler - - 21-057 - OGC GeoPackage WKT for Coordinate Reference Systems Extension + + + + 11-052r4 + + - - - - 14-004r1 + Volker Andres, Simon Jirka , Michael Utech Sensor Observation Service 2.0 Hydrology Profile - This OGC document defines an OGC Sensor Observation Service (SOS) 2.0 hydrology profile for SOS 2.0 implementations serving OGC WaterML 2.0. The development of this OGC Best Practice (BP) is based on previous activities and results (i.e. Hydrology Interoperability Experiments[1] as well as the European FP7 project GEOWOW[2]). The work is guided by the need to overcome semantic issues between different SOS instances serving hydrological data and the related client applications. Therefore, this profile focuses on how to use the entities and requests of the standards and defines the necessary technical details to implement the hydrology SOS profile. + 14-004r1 - 14-004r1 - - - OGC® Sensor Observation Service 2.0 Hydrology Profile - 2014-10-20 - Volker Andres, Simon Jirka , Michael Utech - - - - - - - Hydrologic Modeling and River Corridor Applications of HY_Features Concepts - - 22-040 - Hydrologic Modeling and River Corridor Applications of HY_Features Concepts - 22-040 - 2023-03-06 - Hydrologic geospatial data products contain geometries that represent features such as river segments and incremental catchments. The combination of these provides a 2D (XY) geospatial fabric (hydrofabic) that discretizes the landscape and flow network into hydrologically relevant features at a defined level of scale, resolution, or organization. Hydrofabrics have been created at the national and continental scale in many parts of the world. This engineering report presents progress on formalizing a hydrofabric for drainage basins that adheres to HY_Features concepts with a focus on the use of the concepts in modeling hydrologic processes. Furthermore, this report documents efforts to integrate river corridor data with the traditionally 2D hydrofabric representations. River corridors include the channel and adjacent land required to maintain or restore a dynamic geomorphic equilibrium. - David Blodgett, J. Michael Johnson - - - Paulo Sacramento - This Engineering Report (ER) describes best practices and results gathered through the work performed in the Exploitation Platforms Earth Observation Clouds (EOC) Thread of OGC Testbed-14 concerning the Application Deployment and Execution Service (ADES) and the Execution Management Service (EMS). Both the ADES and EMS were identified by the European Space Agency (ESA), beforehand, as essential elements of a Thematic Exploitation Platform (TEP). - -In the context of a generic Earth Observation Exploitation Platform ecosystem, populated by TEPs and Mission Exploitation Platforms (MEPs), which make use of cloud computing resources for Earth Observation data processing, ESA has established two fundamental building blocks within a TEP, with different functions, the ADES and the EMS. Users interact with a TEP using a Web Client, and the TEP contains a EMS and a ADES. The EMS includes most of the control logic, required for deploying and executing applications in different MEPs and TEPs, the chaining thereof, and the overall coherence of the execution chain (e.g. gathering all outputs and enabling their presentation to the user by a client sensibly). The ADES instead is responsible for the single application deployment and execution on a specific platform. Therefore, it is expected that there are ADES instances both in a TEP and in the individual MEPs. - -The Testbed-14 Participants have experimented with different options for what concerns the functionality allocated to each of the two components, the information required by each of them and the interface requirements between them in order to produce a consistent chain, compliant with ESA’s objectives (as the Sponsor). This report describes these experiments, providing their results and suggesting best practices on how the two services should be engineered in the Exploitation Platform context. - -The OGC Web Processing Service (WPS) 2.0 standard is of particular relevance given that it is well-established in the OGC Web Service context, specifically that concerning processing, its interoperability value has been clearly demonstrated, and it therefore provides a useful mechanism for standardizing interfaces between components of heterogeneous provenance and implementation. - 18-050r1 - ADES & EMS Results and Best Practices Engineering Report + OGC® Sensor Observation Service 2.0 Hydrology Profile + + This OGC document defines an OGC Sensor Observation Service (SOS) 2.0 hydrology profile for SOS 2.0 implementations serving OGC WaterML 2.0. The development of this OGC Best Practice (BP) is based on previous activities and results (i.e. Hydrology Interoperability Experiments[1] as well as the European FP7 project GEOWOW[2]). The work is guided by the need to overcome semantic issues between different SOS instances serving hydrological data and the related client applications. Therefore, this profile focuses on how to use the entities and requests of the standards and defines the necessary technical details to implement the hydrology SOS profile. + - - - - 2019-02-08 - 18-050r1 - - - OGC Testbed-14: ADES & EMS Results and Best Practices Engineering Report + 2014-10-20 + + 14-004r1 - - 14-000 - Testbed 10 Engineering Report: GML for Aviation Conformance Testing - Testbed 10 Engineering Report: GML for Aviation Conformance Testing - - - 14-000 - This activity is part of OGC Testbed 10. The aviation thread was focused on developing -and demonstrating the use of the Aeronautical Information Exchange Model (AIXM) and -the Flight Information Exchange Model (FIXM), building on the work accomplished in -prior testbeds to advance the applications of OGC Web Services standards in next generation -air traffic management systems to support European and US aviation modernization -programs -This document summarizes technical work relating to the enhancement of the GML 3.2.1 -conformance test suite in accord with the requirements in the OWS-10 RFQ, Annex B1, -section 6.3.6: “GML for Aviation Compliance Test Suite + GML for Aviation Conformance -Testing ER”. The essential aim is to advance compliance with respect to the use of -GML geometry representations in aviation (AIXM) data. - - + - 2014-07-14 - - R. Martell - - - Jeff Yutzler - 20-019r1 - GeoPackage Engineering Report - OGC Testbed-16: GeoPackage Engineering Report - - 20-019r1 - In Testbed-16, participants researched ways to mitigate these limitations, particularly in the context of the Ordnance Survey (OS) MasterMap Topography datasets. The Testbed activity also made use of OS Open Zoomstack, a smaller, freely available, multi-scale dataset. To address the first two limitations, Testbed participants developed GeoPackage metadata profiles designed to advance the discoverability of the contents of a GeoPackage and exchange the OS portrayal styles and symbols. The metadata proved to be interoperable between the server and client implementation. - + The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. + 06-103r4 + Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture + + John Herring + 2011-05-28 + + 06-103r4 + + OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture - 2021-01-13 - - - - 15-052r1 - OGC® Testbed 11 REST Interface Engineering Report - 2016-01-18 + + OWS-9 Security Engineering Report + 12-118 + + + Andreas Matheus + + This Engineering Report describes the approaches to security taken in the OWS-9 initiative. This document presents the results of the work within the OWS-9 Security and Services Interoperability (SSI) thread and results from CCI and Innovations Cross Thread activities. +The report also describes the various tasks and their results regarding interoperability between different security components provided by different participants. + + 12-118 - Frédéric Houbie - - - 15-052r1 - Testbed 11 REST Interface Engineering Report - - - REST architectural principles are associated with optimal functioning of the Web but their manifestation in geospatial Web services standards is not straightforward. This OGC Engineering Report (ER) examines their use both in existing OGC Services standards and in new or revised service standard proposals, some of which were implemented during OGC Testbed 11. The ER then defines possible uniform practices for developing bindings or interaction styles for OGC Web services that appropriately leverage REST principles. + OWS-9 Security Engineering Report + 2013-02-06 + - - - Web Processing Service - 05-007r4 - - - This document specifies the interface to a Web Processing Service (WPS). A WPS can be configured to offer any sort of GIS functionality to clients across a network, including access to pre-programmed calculations and/or computation models that operate on spatially referenced data. A WPS may offer calculations as simple as subtracting one set of spatially referenced numbers from another (e.g., determining the difference in influenza cases between two different seasons), or as complicated as a global climate change model. The data required by the WPS can be delivered across a network, or available at the server. - - Peter Schut, Arliss Whiteside + + OGC Reference Model + + + 08-062r7 + The OGC Reference Model (ORM) describes the OGC Standards Baseline focusing on relationships between the baseline documents. The OGC Standards Baseline (SB) consists of the approved OGC Abstract and Implementation Standards (Interface, Encoding, Profile, and Application Schema – normative documents) and OGC Best Practice documents (informative documents). + OGC Reference Model + 08-062r7 + George Percivall + 2011-12-19 - Web Processing Service - 05-007r4 - 2005-09-16 + + - - 06-141r2 - 2007-08-15 - + - + - This best practices document describes a profile to order Earth Observation data products. This document expands on the work presented in Best Practices for Earth Observation Products OGC-05-057r4, separating the order services from the catalogue services which are now presented in 06-079. The final goal being to agree to a coherent set of interfaces for ordering of EO products to support access to data from heterogeneous systems dealing with derived data products from satellite based measurements of the earth's surface and environment. - - Daniele Marchionni - Ordering Services for Earth Observation Products - 06-141r2 - Ordering Services for Earth Observation Products - + + Web Coordinate Transformation Service + + + 05-013 + Arliss Whiteside, Markus U. M + Web Coordinate Transformation Service + 05-013 + This document specifies the interface to a Web Coordinate Transformation Service (WCTS), which can be used by geospatial applications and other services. Transformation of geospatial data from one coordinate reference system (CRS) to another is frequently required when using data from different sources in one application. That is, geospatial data are often stored in different coordinate reference systems (CRSs). To use together data stored in different CRSs, such data must be transformed or converted into the same CRS. Not all applications or services are capable of directly performing such transformations. + +This document specifies an OGC Web Service type of interface to a service that performs coordinate transformations. Such transformations include all the types of coordinate operations, including both transformations and conversions. This service inputs digital features or coverages in one CRS and outputs the same features in a different CRS. The service inputs include identifications of the input and output CRSs, and optionally the coordinate transformation between these CRSs. + + 2005-04-13 - + + This report aims at providing an information model for the usage of video moving target indicator data (VMTI), ground moving target indicator (GMTI) and tracking information (STANAG 4676) in the context of standardized spatial data infrastructures compliant to OGC and ISO standards. If possible, precedence was given on using the OGC Sensor Web Enablement suite of standards, as this suite provides a homogeneous suite of standards to express sensor and sensor observation data in the context of OGC. This means that all encodings are based on Observation and Measurements version 2 (O&M) and implemented as an application schema according to the rules of Geography Markup Language version 3.2 (GML). An information model – so called ‘bookmark’ – to conserve the trace from a moving object back to the original base data is discussed briefly. + + OWS-8 Information Model for Moving Target Indicators and Moving Object Bookmarks (Engineering Report) + + + + 11-113r1 + OWS-8 Information Model for Moving Target Indicators and Moving Object Bookmarks (Engineering Report) + Ingo Simonis + 2011-11-23 + + 11-113r1 + + + + - - 12-049 + + 2021-02-18 + Apple Inc. - Peter Baumann, Jinsongdi Yu - 2014-02-26 - OGC® Web Coverage Service Interface Standard - Interpolation Extension - Web Coverage Service Interface Standard - Interpolation Extension - 12-049 - - This OGC standard specifies parameters to the OGC Web Coverage Service (WCS) GetCov-erage request which give control over interpolation of a coverage during its server-side pro-cessing. This allows the client (user) to control and specify the interpolation mechanism to be applied to a coverage during server processing. -This WCS Interpolation extension relies on WCS Core [OGC 09-110r4] and the GML Appli-cation Schema for Coverages [OGC 09-146r2]. + Indoor Mapping Data Format (referenced throughout this document as IMDF) provides a generalized, yet comprehensive model for any indoor location, providing a basis for orientation, navigation and discovery. In this release there are also detailed instructions for modeling the spaces of an airport, a shopping mall, and a train station. + +This release also has an extension model which enables a venue, organization, or even an industry to create valid features and validations not available in the current specification for private or public use + - + Indoor Mapping Data Format + 20-094 + 20-094 + Indoor Mapping Data Format + - - This document describes a URN (Uniform Resource Name) namespace that is engineered by the Open Geospatial Consortium (OGC) for naming persistent resources published by the OGC. The formal Namespace identifier (NID) is ogc. - + + 07-144r4 + CSW-ebRIM Registry Service - Part 2: Basic extension package + 07-144r4 + + CSW-ebRIM Registry Service - Part 2: Basic extension package - + + + + Richard Martell + + 2009-02-05 + Incorporates Corrigendum 1 (OGC 08-102r1). + + - Carl Reed - + + 2004-11-02 + Sensor Model Language (SensorML) for In-situ and Remote Sensors + + + 04-019r2 - 06-166 - - A URN namespace for the Open Geospatial Consortium (OGC) - 06-166 - A URN namespace for the Open Geospatial Consortium (OGC) - 2007-01-30 + Sensor Model Language (SensorML) for In-situ and Remote Sensors + 04-019r2 + Mike Botts + The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances. + - - John Hudson - 12-133 - OGC® Web Services Facade for OGC IP Engineering Report - This document describes the Web Services Façade which was developed by LISAsoft as part of the OWS-9 testbed. The document also includes discussions about lessons learned during the development, and suggestions for future development. -This Engineering Report documents the Web Services Façade work done within OWS-9 as an extensible, open source tool, which supports translations between different protocols for a specific web service. For the OWS-9 testbed, it has been set up to translate between POST and SOAP services for a Web Feature Service. However, it can be configured to support translations between multiple protocols, such as REST, SOAP, KVP, JSON, as well as supporting multiple web services. -The Web Services Façade is an extensible, open source tool, which supports translations between different protocols for a specific web service. For the OWS-9 testbed, it has been set up to translate between POST and SOAP services for a Web Feature Service. However, it can be configured to support translations between multiple protocols, such as REST, SOAP, KVP, JSON, as well as supporting multiple web services. - - Web Services Facade for OGC IP Engineering Report - 12-133 - + + 2015-11-19 + Testbed-11 Multi-dimensional GeoPackage Supporting Terrain and Routes Engineering Report + 15-067 + 15-067 + + + Gobe Hobona;Roger Brackin + OGC® Testbed-11 Multi-dimensional GeoPackage Supporting Terrain and Routes Engineering Report + Routing is one of the most widely used functions of mobile applications. Routing often requires consideration of a variety of factors in order to provide reasonable estimations of journey time and the cost of travel. Another widely used function of mobile applications is the visualization of characteristics of terrain such as slope or viewsheds. The goal of this engineering report is to describe the work carried out in the OGC Testbed-11 for multidimensional terrain and routing support on SQLite databases that conform to the OGC GeoPackage standard. This OGC® Engineering Report (ER) describes an approach for the storage of routing and multidimensional terrain data in such databases. The ER also presents the results and lessons learnt from the experimentation conducted by the testbed. - - 2014-08-22 - - - - OGC Documents - - - loaded from https://portal.opengeospatial.org/public_ogc/api/docs.php?CITE=1 - OGC document register with annotations and links - - - - - - This document describes the purpose and function of the Topology Quality Assessment Service developed and deployed within the Geo-processing workflow thread of the OWS4 interoperability testbed. - OWS4 - Topology Quality Assessment Interoperability Program Report - 07-007r1 - - 2007-06-06 - 07-007r1 - - - OWS4 - Topology Quality Assessment Interoperability Program Report - Paul Watson - - - 01-101 - - Topic 1 - Feature Geometry - John Herring + + Ilya Zaslavsky, David Valentine, Tim Whiteaker + 07-041r1 + CUAHSI WaterML + 07-041r1 + - Same as ISO 19107, available at http://www.iso.org. - 2001-05-10 - Topic 01 - Feature Geometry - 01-101 - - + + 2007-05-30 + + + This document describes the initial version of the WaterML messaging schema as implemented in version 1 of WaterOneFlow web services. It also lays out strategies for harmonizing WaterML with OGC specifications, the Observations and Measurement specification in particular. + CUAHSI WaterML - - - - - - Documents of type Specification Application Profile - Approved - Documents of type Specification Application Profile - Approved - - - Documents of type Specification Application Profile - Approved + + 5f5b05c3-a60e-424a-98dc-119698b7c563 - - Robert Thomas, Terry Idol - This engineering report presents the results of a concept development study on a -Marine Spatial Data Infrastructure (SDI), sponsored by the National Geospatial- -Intelligence Agency (NGA) - Maritime Safety Office (MSO), on behalf of the -International Hydrographic Organization (IHO) and the IHO MSDI Working Group -(MSDIWG), and executed by the Open Geospatial Consortium (OGC). The goal of -this study was to demonstrate to stakeholders the diversity, richness and value of a -Marine SDI – specifically data, analysis, interoperability and associated IT services -- including web services - in addressing needs of the marine domain. - Development of Spatial Data Infrastructures for Marine Data Management - 2019-08-05 + + + + Mobility Data Science Discussion Paper + 2024-01-29 + + 23-056 + Mobility Data Science Discussion Paper + 23-056 + Almost every activity in our modern life leaves a digital trace, typically including location and time. Either captured by a sensor, manually input, or extracted from a social media post, the increase in the volume, variety, and velocity of spatiotemporal data is unprecedented. The ability to manage and analyze this data is important for many application domains, including smart cities, health, transportation, agriculture, sports, biodiversity, et cetera. It is critical to not only effectively manage and analyze the data but also to uphold privacy and ethical considerations. Since the civilian use of GPS was allowed in 1980, followed by the technological advances in other location tracking systems – wifi, RFID, bluetooth, etc., it is becoming more and more easy to track moving objects. The Mobility Data Science Summit was an opportunity to discuss the challenges of managing this data and making sense of it, with a focus on the tooling and standardization requirements. + + Song WU, Mahmoud SAKR + + + + OGC Web Feature Service (WFS) 3.0 is a revision of the WFS standard that proposes a modernized service architecture, that follows the current Web architecture, has a focus on the developer experience, supports the OpenAPI specification, and modularizes WFS into building blocks for fine-grained access to spatial data that can be used by an Application Programming Interface (API) for data. + +This document reviews the work that proposes a next generation of OGC web services (NextGen services or Next Generation APIs) from the perspective of supporting complex three-dimensional (3D) data or complex data schemas. The goal is to identify the best service solution for these particular needs, whether the results are WFS 3.0 extensions or other approaches. In this context the approach of the NextGen services is not of monolithic web services, but Web API building blocks. This is an important point. The same API should be able to support requirements that currently require separate OGC web services, e.g. a WFS and a 3D Portrayal Service (3DPS). + +The purpose of this work is not to preempt other next-generation discussions taking place in OGC but rather to inform and complement that work. + +The report includes proposals on how to extend the NextGen service architecture with API building blocks for complex data, complex queries and 3D portrayal. WFS 3.0, Part 1, is used as the starting point for the NextGen service architecture. The proposals are based on existing requirements and use cases as well as existing support for developers to simplify implementation. + +The work has found no general issues with migrating current WFS, 3DPS, Web Map Tile Service (WMTS) and Web Map Service (WMS) capabilities to the NextGen architecture. On the contrary, the NextGen approach improves the consistency of the interface and removes redundancies (e.g., between the feature access in WFS and the feature info requests in the other standards). + + Next Generation APIs: Complex Feature Handling Engineering Report + 18-021 + Clemens Portele - 19-025r1 + 18-021 + - - - 19-025r1 - Development of Spatial Data Infrastructures for Marine Data Management + OGC Testbed-14 Next Generation APIs: Complex Feature Handling Engineering Report + + 2019-03-06 - - 09-112 - Sensor Observable Registry Discussion Paper - - - 2009-10-13 - This Discussion paper introduces the Sensor Observable Registry (SOR), a web service interface for managing the definitions of phenomena measured by sensors as well as exploring semantic relationships between these phenomena. - 09-112 - + + EA-SIG Enterprise Service Management White Paper + 04-087 + 2004-02-20 + Matt Murray,Jeff Stollman,Shue-Jane Thompson,Terry Plymell,Eli Hertz,Chuck Heazel + + + + *RETIRED* This document focuses on the goals, objectives, capabilities and recommendation for the ESM Core Enterprise Service. The charter for this team was to address three fundamental questions: + +* What it Enterprise Service Management? +* What can we buy or build today? +* How should we invest for the future? + +This paper responds to those questions by defining and describing ESM, discussing what is being done today, and what the group sees for the future of ESM? + 04-087 + + EA-SIG Enterprise Service Management White Paper + + + + 2003-09-16 + + + 03-040 + OGC Reference Model + OGC Reference Model + 03-040 + The ORM describes a framework for the ongoing work of the Open Geospatial Consortium and our specifications and implementing interoperable solutions and applications for geospatial services, data, and applications. + George Percivall - Sensor Observable Registry Discussion Paper + - Simon Jirka, Arne Bröring - - - OWS-5 ER: GSIP Schema Processing - 08-078r1 + + + + 02-039r1 + Web Pricing and Ordering + Roland Wagner + 2002-10-18 + + - OGC® OWS-5 ER: GSIP Schema Processing - Clemens Portele - 2008-07-08 - - - 08-078r1 - - This OGC® document describes and discusses the OWS-5 enhancements in the process of creating application schemas in support of the NSG from NGA data based on the GEOINT Structure Implementation Profile (GSIP) which has been based on the NSG Application Schema and accompanying NSG Entity Catalog. + This specification covers all standard geo-eBusiness processes like pricing, ordering and online delivery for spatial products. + + Web Pricing and Ordering + 02-039r1 - - Marwa Mabrouk - 03-006r1 - Location Services (OpenLS): Core Services [Parts 1-5] - - OpenGIS Location Services (OpenLS): Core Services [Parts 1-5] - 2003-06-12 - - + + 2021-01-20 + OGC WaterML 2: Part 4 - GroundWaterML 2 (GWML2) + This standard describes a conceptual and logical model for the exchange of groundwater data, as well as a GML/XML encoding with examples. + 16-032r3 + OGC WaterML 2: Part 4 - GroundWaterML 2 (GWML2) - + + - OpenGIS Location Services (OpenLS): Core Services, Parts 1-5, which consists of the composite set of basic services comprising the OpenLS Platform. This platform is also referred to as the GeoMobility Server (GMS), an open location services platform. - 03-006r1 + + Boyan Brodaric + + 16-032r3 - - Simon Cox - - 2013-09-17 + + + 15-113r6 + Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure - This International Standard defines a conceptual schema for observations, and for features involved in sampling when making observations. These provide models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities. -Observations commonly involve sampling of an ultimate feature of interest. This International Standard defines a common set of sampling feature types classified primarily by topological dimension, as well as samples for ex-situ observations. The schema includes relationships between sampling features (sub-sampling, derived samples). -This International Standard concerns only externally visible interfaces and places no restriction on the underlying implementations other than what is needed to satisfy the interface specifications in the actual situation. - - 10-004r3 - Topic 20 - Observations and Measurements + + Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure + 2021-02-26 - - - - 10-004r3 - Topic 20 - Observations and Measurements + 15-113r6 + + The CDB standard defines a standardized model and structure for a single, versionable, virtual representation of the earth. A CDB structured data store provides for a geospatial content and model definition repository that is plug-and-play interoperable between database authoring workstations. Moreover, a CDB structured data store can be used as a common online (or runtime) repository from which various simulator client-devices can simultaneously retrieve and modify, in real-time, relevant information to perform their respective runtime simulation tasks. In this case, a CDB is plug-and-play interoperable between CDB-compliant simulators. A CDB can be readily used by existing simulation client-devices (legacy Image Generators, Radar simulator, Computer Generated Forces, etc.) through a data publishing process that is performed on-demand in real-time. + + Carl Reed - - UML-to-GML Application Schema Pilot (UGAS-2020) Engineering Report + + 20-095 + Defence Geospatial Information Working Group (DGIWG) GeoTIFF/TIFF Profile for Imagery & Gridded Data 2.3.1 + 20-095 + DGIWG + This OGC Best Practice was developed by the Defence Geospatial Information Working Group to address defense and intelligence user community requirements. As such, the Best Practice utilizes standardized military Coordinate Reference System (CRS) definitions, which may not be applicable to other user communities. +This Best Practice also defines a GEO_METADATA tag, which may be of more general interest. + + + Defence Geospatial Information Working Group (DGIWG) GeoTIFF/TIFF Profile for Imagery & Gridded Data 2.3.1 - 20-012 - UML-to-GML Application Schema Pilot (UGAS-2020) Engineering Report + - 20-012 - - 2021-01-18 - - Johannes Echterhoff + + 2021-02-25 - During UGAS-2020 emerging technology requirements for NAS employment in the NSG, and with general applicability for the wider geospatial community, were investigated and solutions developed in four areas. - -To enable a wide variety of analytic tradecrafts in the NSG to consistently and interoperably exchange data, the NAS defines an NSG-wide standard UML-based application schema in accordance with the ISO 19109 General Feature Model. In light of continuing technology evolution in the commercial marketplace it is desirable to be able to employ (NAS-conformant) JSON-based data exchanges alongside existing (NAS-conformant) XML-based data exchanges. A prototype design and implementation of UML Application Schema to JSON Schema rules (see the OWS-9 SSI UGAS Conversion Engineering Report) was reviewed and revised based on the final draft IETF JSON Schema standard “draft 2019-09.” The revised implementation was evaluated using NAS Baseline X-3. This work is reported in section UML to JSON Schema Encoding Rule. - -To maximize cross-community data interoperability the NAS employs conceptual data schemas developed by communities external to the NSG, for example as defined by the ISO 19100-series standards. At the present time there are no defined JSON-based encodings for those conceptual schemas. A JSON-based core profile was developed for key external community conceptual schemas, particularly components of those ISO 19100-series standards used to enable data discovery, access, control, and use in data exchange in general, including in the NSG. This work is reported in section Features Core Profile of Key Community Conceptual Schemas. - -The Features Core Profile and its JSON encoding have been specified with a broader scope than the NAS. It builds on the widely used GeoJSON standard and extends it with minimal extensions to support additional concepts that are important for the wider geospatial community and the OGC API standards, including support for solids, coordinate reference systems, and time intervals. These extensions have been kept minimal to keep implementation efforts as low as possible. If there is interest in the OGC membership, the JSON encoding of the Core Profile could be a starting point for a JSON encoding standard for features in the OGC. A new Standards Working Group for a standard OGC Features and Geometries JSON has been proposed. - -Linked data is increasingly important in enabling “connect the dots” correlation and alignment among diverse, distributed data sources and data repositories. Validation of both data content and link-based data relationships is critical to ensuring that the resulting virtual data assemblage has logical integrity and thus constitutes meaningful information. SHACL, a language for describing and validating RDF graphs, appears to offer significant as yet unrealized potential for enabling robust data validation in a linked-data environment. The results of evaluating that potential – with emphasis on deriving SHACL from a UML-based application schema - are reported in section Using SHACL for Validation of Linked Data. - -The OpenAPI initiative is gaining traction in the commercial marketplace as a next-generation approach to defining machine-readable specifications for RESTful APIs in web-based environments. The OGC is currently shifting towards interface specifications based on the OpenAPI 3.1 specification. That specification defines both the interface (interactions between the client and service) and the structure of data payloads (content) offered by that service. It is desirable to be able to efficiently model the service interface using UML and then automatically derive the physical expression of that interface (for example, as a JSON file) using Model Driven Engineering (MDE) techniques alongside the derivation of JSON Schema defining data content. A preliminary analysis and design based on the OGC API Features standard, parts 1 and 2, for sections other than for content schemas, is reported in section Generating OpenAPI definitions from an application schema in UML. - -All ShapeChange enhancements developed within the UGAS-2020 Pilot have been publicly released as a component of ShapeChange v2.10.0. https://shapechange.net has been updated to document the enhancements. - - - - 06-049r1 - GML 3.1.1 simple features profile - - The OpenGIS® GML 3.1.1 Simple Features Profile (GML for Simple Features) is a restricted subset of GML (Geography Markup Language)[http://www.opengeospatial.org/standards/gml] and XML Schema [www.w3.org/XML/Schema] that supports the XML encoding of geographic features with simple geometric property types (Points, Line and Polygons). The profile defines three conformance classes that define three different levels of complexity. + + Matthias Mueller + OGC® WPS 2.0.1 Interface Standard: Corrigendum 1 + + + + + In many cases geospatial or location data, including data from sensors, must be processed before the information can be used effectively. The OGC Web Processing Service (WPS) Interface Standard provides a standard interface that simplifies the task of making simple or complex computational processing services accessible via web services. Such services include well-known processes found in GIS software as well as specialized processes for spatio-temporal modeling and simulation. While the OGC WPS standard was designed with spatial processing in mind, it can also be used to readily insert non-spatial processing tasks into a web services environment. + +The WPS standard provides a robust, interoperable, and versatile protocol for process execution on web services. It supports both immediate processing for computational tasks that take little time and asynchronous processing for more complex and time consuming tasks. Moreover, the WPS standard defines a general process model that is designed to provide an interoperable description of processing functions. It is intended to support process cataloguing and discovery in a distributed environment. -See also the GML pages on OGC Network: http://www.ogcnetwork.net/gml . - 2006-05-08 + 2015-10-05 + 14-065r1 + + 14-065r1 + WPS 2.0.1 Interface Standard: Corrigendum 1 + + + + 2016-10-25 + + + + Frans Knibbe, Alejandro Llaves + + 15-074r2 + Spatial Data on the Web Use Cases & Requirements + + + Spatial Data on the Web Use Cases & Requirements + 15-074r2 + This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC. + + + + Bastian Schaeffer + 08-009r1 + OWS 5 SOAP/WSDL Common Engineering Report + OWS 5 SOAP/WSDL Common Engineering Report + This OGC document reports the results achieved in the OWS5 GPW-SOAP/WSDL thread which is focused on creating general recommendations and guidelines for WSDL/SOAP support to existing OGC Web Services. + 2008-02-21 + 08-009r1 + + + + + + OGC® GML Application Schema - Coverages JPEG2000/JPIP Coverage Encoding Extension + 14-110r2 + GML Application Schema - Coverages JPEG2000/JPIP Coverage Encoding Extension + 2016-11-02 + - 06-049r1 - - GML 3.1.1 simple features profile - Peter Vretanos + + + + Dimitri Sarafinof + + Coverages represent space/time-varying phenomena, such as satellite imagery, digital elevation models, or digital aerial imagery. OGC Abstract Topic 6 [OGC 07-011] – which is identical to ISO 19123 – defines an abstract model of coverages. Coverage instances may be encoded using the GML Application Schema – Coverages – JPEG2000 Coverage Encoding Extension version 1.0 [OGC 12-108] which is based on the GML Application Schema – Coverages (GMLCOV) version 1.0 [OGC 09-146r2] which in turn is based on the Geography Markup Language (GML) version 3.2 [07-036], an XML grammar written in XML Schema for the description of application schemas as well as the transport and storage of geographic information. + +This extension to the Web Coverage Service (WCS) 2.0 Interface Standard – Core (WCS) version 2.0 [OC 09-110r4] specifies the usage of the JPEG2000 coverage encoding and JPIP streaming capabilities with WCS. The approach is based on the authoritative GML Application Schema – Coverages – JPEG2000 Coverage Encoding Extension version 1.0 [OGC 12-108]. + 14-110r2 - + + 18-030 + Secure Client Test Engineering Report - Testbed-12 PubSub / Catalog Engineering Report - 16-137r2 - - Lorenzo Bigagli - 2017-05-12 - 16-137r2 - - Testbed-12 PubSub / Catalog Engineering Report - This document describes how the OGC PubSub standard can be used as a mechanism to automatically notify analysts of data availability for CSW and other OGC Web Services (e.g. WFS, WCS). In particular, this document proposes the following: + 18-030 + Sara Saeedi + + + + 2019-03-06 + OGC Testbed-14: Secure Client Test Engineering Report + This Engineering Report (ER) describes the development of compliance tests and their implementation in the OGC Test, Evaluation, And Measurement (TEAM) Engine to validate a client’s ability to make secure requests according to the OGC Web Services Security Candidate Standard. The goal of the candidate standard is to allow the implementation of Information Assurance (IA) controls and to advertise their existence in an interoperable way with minimal impact to existing implementations using a backward-compatible approach. -Specific PubSub 1.0 extensions for CSW 2.0.2 and 3.0, leveraging on standard functionalities, data models, and semantics to enable sending notifications based on user-specified area of interest and/or keywords; +This ER covers the following topics from OGC Testbed-14 Compliance Interoperability & Testing Evaluation (CITE) thread: -A general, basic mechanism for enabling PubSub for the generic OGC Web Service over the existing request/reply OWS’s, i.e. usual requests as filters, usual responses as appropriate updates/data pushes, existing semantics and syntax expressiveness. +developing a client validator to test compliance of client software with the OGC Web Services Security Candidate Standard -This document is the result of activity performed within the Large-Scale Analytics (LSA) Thread of the OGC Testbed 12 Interoperability initiative, being identified as document deliverable A074 PubSub / Catalog Engineering Report. This document also captures lessons learnt from the implementation of component deliverable A016 CSW 2.0.2 with PubSub Core Support Server. - +capturing the results of two use cases with different authentication methods + +making recommendations to the OGC Web Services Security Standards Working Group (SWG) based on the experiences made while developing the validator + + - - GeoSPARQL - A Geographic Query Language for RDF Data - 11-052r4 - 2012-06-12 - - OGC GeoSPARQL - A Geographic Query Language for RDF Data - Matthew Perry, John Herring - 11-052r4 - + + + + + + + + + + + Documents of type Request for Comment - deprecated + Documents of type Request for Comment - deprecated + Documents of type Request for Comment - deprecated - - - This standard defines a set of SPARQL extension functions [W3C SPARQL], a set of RIF rules [W3C RIF Core], and a core RDF/OWL vocabulary for geographic information based on the General Feature Model, Simple Features [ISO 19125-1], Feature Geometry and SQL MM. - - - OGC Sensor Observation Service 2.0 Hydrology Profile - Sensor Observation Service 2.0 Hydrology Profile - 14-004 - - - GEOWOW Consortium + + 2015-10-01 + Use of Semantic Linked Data with RDF for National Map NHD and Gazetteer Data Engineering Report + 15-066r1 + + OGC® Testbed 11 Use of Semantic Linked Data with RDF for National Map NHD and Gazetteer Data Engineering Report + + Gobe Hobona;Roger Brackin - 2014-04-15 - - - - This document an interoperable hydrology profile for OGC Sensor Observation Service (SOS) 2.0 implementations serving OGC WaterML 2.0. This development is based on previous activities and results (i.e. Hydrology Interoperability Experiments as well as the European FP7 project GEOWOW). It is guided by the need to overcome mostly semantic issues between different SOS instances serving hydrological data and the according clients. Therefore, this profile focuses on how to use the entities and requests of the standards and covers the necessary technical details. - 14-004 - - - 05-016 - Location Service (OpenLS) Implementation Specification: Core Services - - - - 05-016 + Over the past few years there has been an increase in the number, size and complexity of databases across government sectors. This has undoubtedly created challenges relating to the discovery and access of information and services on multiple databases across static and deployed networks. Linked Data has been suggested as a method able to tackle those challenges. The aim of the Hydrographic Linked Data activity in the OGC Testbed 11 was to advance the use of Linked Data for hydrographic data by building on the achievements of the previous testbeds and to improve the understanding of how to better build relations between hydro features and non-hydro features (e.g., stream gauge measurement/location vs bridge or other built features upstream or downstream). This aspect of the testbed focused on the National Hydrography Dataset (NHD) which is published by the United States Geological Survey (USGS). This OGC Engineering Report provides guidelines on the publication of hydrographic and hydrological data serialized as Resource Description Framework (RDF) using Linked Data principles and technologies based on OGC standards. The document also presents the experimentation conducted by Testbed 11 in order to identify those guidelines. + - OpenGIS Location Service (OpenLS) Implementation Specification: Core Services - 2005-05-02 - The OpenGIS® Open Location Services Interface Standard (OpenLS) specifies interfaces that enable companies in the Location Based Services (LBS) value chain to “hook up” and provide their pieces of applications such as emergency response (E-911, for example), personal navigator, traffic information service, proximity service, location recall, mobile field service, travel directions, restaurant finder, corporate asset locator, concierge, routing, vector map portrayal and interaction, friend finder, and geography voice-graphics. These applications are enabled by interfaces that implement OpenLS services such as a Directory Service, Gateway Service, Geocoder Service, Presentation (Map Portrayal) Service and others. - - Marwa Mabrouk - + 15-066r1 - - OGC® GeoPackage Encoding Standard - with Corrigendum - 12-128r15 - 12-128r15 + + + Jonathan Pritchard + 20-013r4 + Maritime Limits and Boundaries Pilot: Engineering Report + OGC Maritime Limits and Boundaries Pilot: Engineering Report + - - This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g. through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. - - - - OGC® GeoPackage Encoding Standard - with Corrigendum - Jeff Yutzler - 2018-09-06 - - - - - - - - Joan Maso - 21-026 - OGC Cloud Optimized GeoTIFF Standard - 21-026 - 2023-07-14 - The Cloud Optimized GeoTIFF (COG) relies on two characteristics of the TIFF v6 format (tiles and reduced resolution subfiles), GeoTIFF keys for georeference, and the HTTP range, which allows for efficient downloading of parts of imagery and grid coverage data on the web and to make fast data visualization of TIFF or BigTIFF files and fast geospatial processing workflows possible. COG-aware applications can download only the information they need to visualize or process the data on the web. Numerous remote sensing datasets are available in cloud storage facilities that can benefit from optimized visualization and processing. This standard formalizes the requirements for a TIFF file to become a COG file and for the HTTP server to make COG files available in a fast fashion on the web. + 2020-07-29 + + This document comprises the Engineering Report (ER) and documents the activities under Phase 1 and Phase 2 of the OGC Maritime Limits and Boundaries (MLB) Pilot. -The key work for crafting this OGC Standard was undertaken in the Open-Earth-Monitor Cyberinfrastructure (OEMC) project, which received funding from the European Union’s Horizon Europe research and innovation program under grant agreement number 101059548 and in the All Data 4 Green Deal - An Integrated, FAIR Approach for the Common European Data Space (AD4GD) project, which received funding from the European Union’s Horizon Europe research and innovation program under grant agreement number 101061001. - OGC Cloud Optimized GeoTIFF Standard +This Engineering Report details the activities undertaken by participants in the pilot, the data supplied, transformed, and used to demonstrate the pilot’s objectives, and the results of the various interoperability tests performed within the pilot. Also documented here are the various outputs from the pilot activities, where they are directed, and where updates or clarifications are recommended to external standards or other elements of the broader ecosystem. + +The ER documents the journey taken within the project, from its origins as an architectural statement of intent, through to the definition of its core elements (the GML application schema which lends a common language to the data) and the implementation of that schema within COTS, open source and bespoke software elements. The engineering report also summarizes the outputs from the process, any unresolved issues, and potential enhancements for the future. + 20-013r4 - - 16-093r1 - Incident Management Information Sharing Internet of Things Protocol Mapping Engineering Report - + + + OGC CoverageJSON Community Standard + + + 2023-08-22 - - 16-093r1 - This engineering report details Pilot experiences in connecting a variety of local communications protocols and message formats supported by low-cost sensor devices with OGC SWE Web services published globally over IP networks. It describes the Sensor Hub approach taken to support these connections and the mappings from one protocol to another required to develop integrated SWE-IoT networks. - + 21-069r2 - Incident Management Information Sharing Internet of Things Protocol Mapping Engineering Report - - Steve Liang, Tania Khalafbeigi - 2018-04-26 - - + Chris Little, Jon Blower, Maik Riechert + OGC CoverageJSON Community Standard + 21-069r2 - 21-023 - Johannes Echterhoff, Julia Wagemann, Josh Lieberman - - 2021-12-13 - - - - Earth Observation Cloud Platform Concept Development Study Report - - Earth Observation Cloud Platform Concept Development Study Report - 21-023 - The Earth Observation Cloud Platform Concept Development Study (CDS) evaluates the readiness of satellite data providers and cloud service providers, as well as the maturity of their current systems, with regard to real-world deployment of the new “Applications-to-the-Data” paradigm, using cloud environments for EO data storage, processing, and retrieval. + Based on JavaScript Object Notation (JSON), CoverageJSON is a format for publishing spatiotemporal data to the Web. The primary design goals are simplicity, machine and human readability and efficiency. While other use cases are possible, the primary CoverageJSON use case is enabling the development of interactive visual websites that display and manipulate environmental data within a web browser. + +Implementation experience has shown that CoverageJSON is an effective, efficient format, friendly to web and application developers, and therefore consistent with the current OGC API developments. CoverageJSON supports the efficient transfer from big data stores of useful quantities of data to lightweight clients, such as browsers and mobile applications. This enables straightfoward local manipulation of the data, for example, by science researchers. Web developers often use and are familiar with JSON formats. + +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. + +The simplest and most common use case is to embed all the data values of all variables in a Coverage object within the CoverageJSON document, so that it is “self-contained”. Such a standalone document supports the use of very simple clients. + +The next simplest use case is to put data values for each variable (parameter) in separate array objects in separate CoverageJSON documents which are linked from the Coverage object. This is useful for a multi-variable dataset, such as one with temperature, humidity, wind speed, etc., to be recorded in separate files. This allows the client to load only the variables of interest. + +A sophisticated use case is to use tiling objects, where the data values are partitioned spatially and temporally, so that a single variable’s data values would be split among several documents. A simple example of this use case is encoding each time step of a dataset into a separate file, but the tiles could also be divided spatially in a manner similar to a tiled map server. - - Climate Challenge Integration Plugfest 2009 Engineering Report - 10-002 - - + + OGC Compliance Overview - Guide for Software Acquisition + The Open Geospatial Consortium (OGC®) provides international standards that are implemented worldwide in thousands of applications that use location information. To reduce the risk of applications not implementing a standard correctly, the OGC provides a compliance process for testing and certifying implementations. OGC certification provides substantial evidence that an implementation that is claimed to have implemented an OGC standard will interoperate as specified and in the same manner as other compliant implementations, regardless of who developed them. This white paper provides guidance regarding language to specify requirements for OGC compliant and implementing products in software acquisition (procurement) documents. + Luis Bermudez + + + + 15-002r5 + OGC Compliance Overview - Guide for Software Acquisition + 2015-04-20 + - - This OGC Engineering Report (ER) documents findings of the CCIP 2009 Plugfest, which was conducted via the public Internet to address requirements stated in the CCIP Call for Participation . It addresses concept development, specifications tested, and interoperability experiments conducted. The ER concludes with issues that arose, and provides recommendations for the refinement of OGC Specifications and the Plugfest process. Recommendations in this ER will be considered in the planning of future activities. -OGC expresses thanks to the Australian Bureau of Meteorology and to CSIRO for sponsoring CCIP 2009. - - - 10-002 - Raj Singh - OGC® Climate Challenge Integration Plugfest 2009 Engineering Report - 2014-04-28 + 15-002r5 + - + + 15-042r3 + TimeseriesML 1.0 – XML Encoding of the Timeseries Profile of Observations and Measurements - - OGC GML in JPEG 2000 (GMLJP2) Encoding StandardPart 1: Core - - Lucio Colaiacomo, Joan Masó, Emmanuel Devys + 2016-09-09 + + TimeseriesML 1.0 – XML Encoding of the Timeseries Profile of Observations and Measurements + 15-042r3 + TimeseriesML 1.0 defines an XML encoding that implements the OGC Timeseries Profile of Observations and Measurements [OGC 15-043r3], with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of data exchange requirements. + James Tomkins, Dominic Lowe + + - - 08-085r5 - GML in JPEG 2000 (GMLJP2) Encoding StandardPart 1: Core - 08-085r5 - 2016-04-07 - This standard applies to the encoding and decoding of JPEG 2000 images that contain GML for use with geographic imagery. -This document specifies the use of the Geography Markup Language (GML) within the XML boxes of the JPEG 2000 data format and provides an application schema for JPEG 2000 that can be extended to include geometrical feature descriptions and annotations. The document also specifies the encoding and packaging rules for GML use in JPEG 2000. - - - 2017-05-22 + + 2003-01-18 + + + 03-025 + + Josh Lieberman + Specifies and discusses a common architectural framework for OGC Web Services + 03-025 + Web Services Architecture + Web Services Architecture + + + + + + 2007-05-17 + GML Encoding of Discrete Coverages (interleaved pattern) + 06-188r1 + + + + 06-188r1 + This specification describes a GML encoding for discrete coverages. The encoding pattern is a variation from the standard GML Coverage, in that the values in the domain and range are effectively interleaved rather than represented as two blocks and encoded sequentially. + Simon Cox + GML Encoding of Discrete Coverages (interleaved pattern) + + + Rob Atkinson, James Groffen + 11-106r1 + OWS-8 Digital NOTAM Refactor + AIXM is a GML Application Schema described in UML using the relevant ISO / OGC standards from the 19100 series. The Digital NOTAM Events Specification (DNES) is an extension of AIXM that can describe notices to airmen using the AIXM standard. +This document has been produced in conjunction with the Domain Modelling Cookbook - a practical guide to domain modelling following a series of best practices developed by the CSIRO and other OGC members. +Where possible, documentation of the refactor effort for Digital NOTAM to be compatible with these practices is incorporated into the domain modelling cookbook. - - Joan Masó - Testbed-12 OWS Context / Capabilities Engineering Report - The OGC service metadata document (sometimes also called capabilities document) is a key part in the service discovery. It describes the service and also the resources that the service expose. Resources are listed in the service metadata document inside a section named as Contents by OWS Common. There are two main limitations to the current Contents section approach: - -OWS Common offers flexibility for describing resources and it only proposes a very minimum set of metadata in figure 7 of OGC 06-121r9 called DatasetSummary that need to be sub-classed (i.e. extended) by any specific application. As a result, each standard proposes its own alternative for it. Integrated client developers need to implement them separately. - -If the number of resources is very large or the service is highly dynamic, the Contents section can be too long or useless and neither the service nor the client can handle it efficiently. - -This Engineering Report proposes a double solution to the Contents section of the service metadata documents: It proposes ways to encode the Contents section using the OWS Context encoding data types and it introduces the use OpenSearch as a way to request a subset of the resources that the service can provide access to. In that sense, the use of the OGC 10-032r8 OpenSearchGeo can provide the long time needed geospatial and temporal filter capabilities. - 16-052 - Testbed-12 OWS Context / Capabilities Engineering Report - 16-052 - - - - - + OWS-8 Digital NOTAM Refactor + + 2011-12-19 - Documents of type Specification Application Profile - deprecated - Documents of type Specification Application Profile - deprecated - Documents of type Specification Application Profile - deprecated + + + 11-106r1 - - 04-052 - OWS1.2 Image Handling Requirements - 04-052 - Arliss Whiteside - 2004-09-26 + + 12-132r4 + + + + OGC Augmented Reality Markup Language 2.0 (ARML 2.0) + 12-132r4 + Augmented Reality Markup Language 2.0 (ARML 2.0) + + 2015-02-24 + + This OGC® Standard defines the Augmented Reality Markup Language 2.0 (ARML 2.0). ARML 2.0 allows users to describe virtual objects in an Augmented Reality (AR) scene with their appearances and their anchors (a broader concept of a location) related to the real world. Additionally, ARML 2.0 defines ECMAScript bindings to dynamically modify the AR scene based on user behavior and user input. + Martin Lechner + + + OWS-9: UML-to-GML-Application-Schema (UGAS) Conversion Engineering Report + + 12-093 + + + 12-093 + OWS-9: UML-to-GML-Application-Schema (UGAS) Conversion Engineering Report + The main scope of the schema automation activities in the OWS-9 initiative was twofold: +• Support for the SWE Common 2.0 XML Schema encoding rule +• Development of and support for an encoding rule for JSON instance data +In both cases the scope includes implementation of the encoding rules in ShapeChange. +In addition, an initial analysis of the possibilities for generating SWE Common 2.0 record descriptions from schemas in UML has been conducted and the results are described in this document. +The approach and results to both work items are described and discussed in this engineering report. This Engineering Report has been prepared as part of the OGC Web Services Phase 9 (OWS-9) initiative. + + Clemens Portele + + 2013-02-05 - This document was developed as part of the Image Handling Thread of the OGC Web Services Initiative Phase 1 Thread Set 2 (OWS 1.2). This document specified the requirements for the image handling functions to be supported by draft specifications prepared under that thread. - OWS1.2 Image Handling Requirements - - - - - - - - Topic 0 - Overview - 04-084 - Topic 0 - Overview - - 2005-06-27 + + Web Notification Service + 06-095 + - Carl Reed - 04-084 + Ingo Simonis, Johannes Echterhoff + 06-095 - Introduction and roadmap to the Abstract specification. - - - OGC Testbed 17: CITE Engineering Report - 21-044 - 21-044 - OGC Testbed 17: CITE Engineering Report - This OGC Testbed 17 Engineering Report (ER) documents the result of the work performed in the CITE thread of the OGC Testbed-17 initiative. CITE is the Compliance Interoperability & Testing Evaluation Subcommittee that provides a forum for an open, consensus discussion regarding approaches and issues related to conformance and interoperability testing as part of the OGC standards process. This ER provides information about the development of a test suite for the OGC API — Processes Standard (OGC18-062r2) to be executed in the OGC Test Evaluation tool (TEAM Engine). The ER also documents an evaluation of an alternative environment for OGC compliance testing. - - + A service by which a client may conduct asynchronous dialogues (message interchanges) with one or more other services. This service is useful when many collaborating services are required to satisfy a client request, and/or when significant delays are involved is satisfying the request. This service was defined under OWS 1.2 in support of SPS operations. WNS has broad applicability in many such multi-service applications. It is now used in several SWE scenarios. - - 2022-04-08 - - Luis Bermudez + + + 2007-01-25 + Web Notification Service + + + 14-079r1 + 2015-02-02 + + USGS OGC® Interoperability Assessment Report + USGS OGC® Interoperability Assessment Report + 14-079r1 + Ingo Simonis + - - - - Arliss Whiteside - Recommended XML/GML 3.1.1 encoding of image CRS definitions - 05-027r1 - - + + The USGS Interoperability assessment was conducted under the OGC Interoperability +Program with the goal to better understand how USGS customers make use of OGC +compliant Web services operated by USGS. For this assessment, USGS customers have +been invited to share their experiences and to describe their use cases and experiences +made with USGS data services and products. From those descriptions, recommendations +have been derived that help USGS to better understand their user community and +optimize their service offerings. + + + 04-049r1 + WCS Change Request: Support for WSDL & SOAP - - This document recommends standard XML encodings of data defining monoscopic image coordinate reference systems. The scope of this encoding now includes unrectified and georectified images. The recommended CRSs for georectified images are recommended for multiple georectified images that are ready to be mosaicked together. - -These recommended encodings are based on GML 3.1.1 and use XML Schemas. These image CRS definitions will often be referenced in data transferred between client and server software that implements various standardised interfaces. This specified definition data encoding is expected to be used by multiple OGC Implementation Specifications. That is, each of these specifications is expected to use a subset and/or superset of this recommended definition data. + + + + + 2005-04-22 + 04-049r1 + WCS Change Request: Support for WSDL & SOAP + The OpenGIS has been a precursor in Web Services matter, nevertheless, the pattern that has been used is not recognized by the industry as a standard XML Web Services. The work done during the the OpenGIS Web Service 2 initiative has provided the OpenGIS with interfaces that use the XML-related technologies supported by the industry, as SOAP for the communication protocol, WSDL for the interface description language, and UDDI for registering and searching services. -The position or location of a point can be described using coordinates. Such coordinates are unambiguous only when the coordinate reference system on which those coordinates are based is fully defined. Each position is described by a set of coordinates based on a specified coordinate reference system. Coordinates are often used in datasets in which all coordinates belong to the same coordinate reference system. This paper specifies XML encoding of data defining image coordinate reference systems. +This change proposal present the required change to the WCS specification to interoperate with the industry standards. - - Recommended XML/GML 3.1.1 encoding of image CRS definitions - 2005-04-13 - 05-027r1 + Philippe Duschene, Jerome Sonnet + - + + Matthes Rieke + 2013-06-18 + + 12-158 + + + 12-158 + OWS-9 Report on Aviation Performance Study + This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 9 (OWS-9). The report summarizes the work carried out regarding performance and endurance testing of data provision services, namely Web Feature Service and Event Service. More specifically, the report deals with the performance and endurance testing of data provision services commonly used within OWS Aviation testbeds. Test runs have been evaluated on the basis of well-defined, service-specific test models and the results are documented in detail. Furthermore, a description of the service test environment is documented in alignment with the overall OWS-9 service architecture + - 2010-02-10 - 06-131r6 - Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products - - OGC® Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products - - 06-131r6 - - This document describes the mapping of Earth Observation Products – defined in the OGC® GML 3.1.1 Application schema for Earth Observation products [OGC 06-080r4] (version 0.9.3) – to an ebRIM structure within an OGC® Catalogue 2.0.2 (Corrigendum 2 Release) [OGC 07-006r1] implementing the CSW-ebRIM Registry Service – part 1: ebRIM profile of CSW [OGC 07-110r4]. This standard defines the way Earth Observation products metadata resources are organized and implemented in the Catalogue for discovery, retrieval and management. - Frédéric Houbie, Lorenzo Bigagli - + OGC® OWS-9 Report on Aviation Performance Study - - This extension of the WCS standard specifies an additional Transaction operation that may optionally be implemented by WCS servers. This Transaction operation allows clients to add, modify, and delete grid coverages that are available from a WCS server. The Transaction operation request references or includes the new or modified coverage data, including all needed coverage metadata. - - Arliss Whiteside - + + Tom McCarty + Sensor Collection Service + 02-028 - 07-068r4 - Web Coverage Service (WCS) - Transaction operation extension - 2009-01-15 - Web Coverage Service (WCS) - Transaction operation extension - 07-068r4 - - - - - - - Documents of type Profile Corrigendum - Approved - - - Documents of type Profile Corrigendum - Approved - Documents of type Profile Corrigendum - Approved - - - The HDF5 profile for labeled point cloud data - Taehoon Kim, Wijae Cho, Kyoung-Sook Kim - The HDF5 profile for labeled point cloud data - 21-077 - - - - Point cloud data are unstructured three-dimensional sample points to express the basic shape of objects and spaces. However, it is challenging to automatically generate continuous surfaces and infer semantic structures, such as cars, trees, buildings and roads, from a dataset of point clouds generated by a sensor. The understanding of the semantic structures is essential for recording geospatial information. Despite the good performance of deep learning-based approaches in understanding point clouds, their target coverage is still limited by the lack of training datasets that include semantic labels. This discussion paper addresses data formats to share a Labeled Point Cloud (LPC), in which point-level semantic information is annotated to each point. - -Creating LPCs manually or semi-manually is a time-consuming task. Therefore, sharing LPCs in an open standard format is becoming increasingly important for the development of more advanced deep learning algorithms for object detection, semantic segmentation, and instance segmentation. Even though several data formats are used to distribute LPC, there is a variety to represent the semantic information depending on distributors or domains. This discussion paper analyzes three popular formats of ASCII text, PLY, and LAS, for supporting LPC and finally proposes a practice to effectively apply HDF5 to facilitate the sharing and importing of LPC datasets. - 2022-05-06 + + + + 02-028 + The basic function of the Sensor Collection Service (SCS) is to provide a web-enabled interface to a sensor, collection of sensors or sensor proxy. Sensors are defined as devices that measure physical quantities. + Sensor Collection Service + 2002-04-19 + + + CHISP-1 Engineering Report + 13-053r1 + Panagiotis (Peter) A. Vretanos + 2014-02-24 + + + This document provides a technical description of the work completed for the Climatology-Hydrology Information Sharing Pilot, Phase 1 project. +This document describes a profile of SOS, the NRCan GIN SOS 2.0 profile, developed in order to define a baseline of interoperability among the sensor observation services used in the project. +This document describes the use cases used to drive the component development during the project. The first use case was a flood scenario that involved exchanging cross-border hydrologic data with a unified alert service. The second use case involved calculating nutrient loads to the Great Lakes, which also involved the cross-border exchange of analytic data. +This document describes each component developed during the project and the challenges encountered and overcome during the development. The newly developed components include a nutrient load calculation client, a SOS integrating water quality data form the U.S. and Canada, a nutrient load calculation service, an upstream gauge service, a subscription client, and an event notification service composed of a number of sub-components including a subscription broker, an observation harvester and a CAP alert client. + + OGC® CHISP-1 Engineering Report - 21-077 - - - - 10-126r4 - WaterML 2.0: Part 1- Timeseries - 10-126r4 - WaterML 2.0 is a standard information model for the representation of water observations data, with the intent of allowing the exchange of such data sets across information systems. Through the use of existing OGC standards, it aims at being an interoperable exchange format that may be re-used to address a range of exchange requirements, some of which are described later in this document. - - Peter Taylor - - 2014-02-24 - OGC® WaterML 2.0: Part 1- Timeseries - - + 13-053r1 + - - - This document provides the set of revision notes for the existing GeoPackage version 1.2 (OGC 12- -128r13) and does not modify that standard. -This document was approved by the OGC membership on approval date. As a result of the OGC -Standards Working Group (SWG) process, there were a number of edits and enhancements made to -this standard. This document provides the details of those edits, deficiency corrections, and -enhancements. It also documents those items that have been deprecated. Finally, this document -provides implementations details related to issues of backwards compatibility. - + + OWS 5 Engineering Report: Supporting Georeferenceable Imagery + 08-071 + OWS 5 Engineering Report: Supporting Georeferenceable Imagery + 2008-09-12 + - Release Notes for GeoPackage v1.2 - 16-126r8 - - 2017-08-30 - 16-126r8 - - Jeff Yutzler - Release Notes for GeoPackage v1.2 + The scope of this document is to capture considerations and recommendations on approaches for supporting georeferenceable imagery within the OGC encodings and web services. Georeferenceable imagery is typically imagery coming from a remote sensor that has not been previously geo-rectified, resampled, or regridded. Georeferenceable imagery must be accompanied with information sufficient to allow georectification of the imagery. + + 08-071 + + + + Mike Botts - - Second Environmental Linked Features Experiment - 20-067 - - - - 2020-10-22 - 20-067 - This report documents the Second Environmental Linked Features Interoperability Experiment (SELFIE). SELFIE evaluated a proposed Web resource model and HTTP behavior for linked data about and among environmental features. The outcomes are building blocks to establish a system of real-world feature identifiers and landing pages that document them. OGC API - Features was found to be a useful component for systems implementing both landing content and representations of linked-features. More work is needed to establish best practices related to negotiation between varied representations of a feature, observations related to a feature, and for expressing and mediating between varied content from a given resource. These technical / meta-model details were found to be difficult to evaluate given the small number of example implementations and limited number of domain-feature models available for use with linked data. + - - - Second Environmental Linked Features Experiment - David Blodgett - - - 2015-10-01 - OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response + 19-030r1 + Mixed Reality to the Edge Concept Development Study + Mixed Reality (MR), also referred to as hybrid reality, is the merging of real and virtual worlds to produce new environments and visualizations where physical and digital objects co-exist and interact in real time. MR has great potential in enhancing situation awareness and otherwise augmenting the experiences and performance of humans on the go. + +This OGC Engineering Report summarizes information and findings collected during the Mixed Reality at the Edge Concept Development Study (CDS). Specifically, this report presents the significant findings concerning the state-of-the-art and potential of employing MR in modern systems, with a focus on discussing the state of needed interoperability and standards. + +The term mixed reality was originally introduced in a 1994 paper by Paul Milgram and Fumio Kishino, A Taxonomy of Mixed Reality Visual Displays. What is mixed reality?. + 2019-08-20 - - - George Percivall - OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response - 15-037 - - - Responding to an oil spill requires access to and understanding of many types of information. Effective, coordinated operations for the response are based on a shared, common picture of the situation. Interoperability provides shared situational awareness of the crisis and the response activities. What is needed is a common picture of reality for different organizations that have different views of the spill so that they all can deal with it collectively. -Recent oil spills have provided lessons learned and recommendations on forming a Common Operating Picture for oil spill response. Through a joint project, industry is responding to the call, moving from recommendations to reusable best practices supported by open standards that can be deployed quickly in any region of the globe. -This architecture report is part of The International Association of Oil & Gas Producers and IPIECA Oil Spill Response - Joint Industry Project (IOGP–IPIECA OSR-JIP) to produce a recommended practice for GIS/mapping in support of oil spill response and for the use of GIS technology and geospatial information in forming a “Common Operating Picture” to support management of the response. -Interoperability seems to be at first a technical topic, but in fact, it is about organization. Interoperability seems to be about the integration of information. What it’s really about is the coordination of organizational behavior. The Oil Spill Response Common Operating Picture (OSR COP) project seeks to facilitate the coordination of organizational response to any oil spill in the future. - 15-037 + OGC Mixed Reality to the Edge Concept Development Study + + Carl Reed + + + 19-030r1 - - - - - - - + + + - - - Some image geometry models - - - 2004-10-04 - 04-071 - 04-071 - Some image geometry models + + An important principle of a Service Oriented Architecture (SOA) is the notion of composing capabilities provided by individual services into complex behavior. A requester should be able to compose a solution using functionality or data offered by multiple services without worrying about underlying differences in those services. + +Each OGC service is designed to offer a specific type of data product via a service-specific interface. This Engineering Report (ER) describes a single service interface that allows access to multiple data sources, possibly heterogeneous with respect to the types of data provided. + +This report advances the work started in OGC Testbed 11 with the addition of heterogeneous data sources, as well as several other enhancements. + Daniel Balog, Robin Houtmeyers + 16-045r2 + + 16-045r2 + Testbed-12 Data Broker Engineering Report - This discussion paper contains the material that is still relevant from Section 6 (or Appendix A) of the previous version 4 (document OGC 99-107) of OGC Abstract Specification Topic 7, titled The Earth Imagery Case. That version of Topic 7 has now been superseded by a new version with the same title. -In addition, some terminology has been revised to be consistent with the terminology now used in Topic 16: Image Coordinate Transformation Services. Specifically, the previous term real-time image geometry model has been changed to approximate image geometry model. Also, the previous name Universal Real-Time Image Geometry Model has been changed to Universal Image Geometry Model. - - Arliss Whiteside + + 2017-06-30 + Testbed-12 Data Broker Engineering Report + - - - 17-042 - Testbed-13: CDB Engineering Report + - - 17-042 - Sara Saeedi - This Engineering Report (ER) summarizes the CDB sub-thread work in Testbed 13. The document is structured in three phases and includes a feasibility study; the implementation of data models and schemas mapping that are based on the feasibility study results; and a set of OGC web services that implement the CDB in the form of WFS and WCS (Web Coverage Service) instances. + OWS-9 Engineering Report - SSI - Bulk Data Transfer (GML Streaming) + 12-097 + + + 12-097 + + This document provides a description of the Bulk Data Transfer investigations related to Geography Markup Language (GML) streaming and feature data transportation implemented in the OGC OWS-9 test bed. -This Engineering Report describes: +This document extends the concept of Bulk Data Transfer to the dissemination of large payloads consisting of geospatial data sets and/or collections of data sets between machines that are connected via a network. -The conceptual model of an OGC CDB 1.0 datastore as a UML (Unified Modeling Language) diagram to show different datasets (the 3D models, vector features and coverages) structure; +This document also describes the delivery of large payloads consisting of geospatial data sets and/or collections of data sets to SpatiaLite/SQLite to store the data for use by mobile applications. + + + OWS-9 Engineering Report - SSI - Bulk Data Transfer (GML Streaming) + + Jeff Harrison + 2013-03-26 + + + Quality of Service (QoS) and Quality of Experience (QoE) as they are intended and described at the OGC are two related concepts which require very specific treatment and characterization. Citing the definitions provided by the Domain Working Group (DWG) charter document: -How to process and use a NAS-based Profile as a CDB feature/attribute data model or a GML-SF0 application schema; +Quality of Service: Technical reliability and performance of a network service. Typically measured using metrics like error rates, throughput, availability and delay or request response time. This Engineering Report (ER) attempts to handle QoS aspects such as service availability, scalability and speed. -How to access, navigate and visualize a CDB dataset using OGC web services (such as WFS and WCS). +Quality of (User) Experience: A holistic, qualitative measure of the customers' experience of the application or service. It encompasses both the user experience and the customer support experience of the evaluated applications and/or services. -This work provides insights into: +QoE focuses on the usability of the information that is conceived via OGC services to end users or other client application and therefore is concerned more with qualitative aspects of such services like presence of metadata, proper and descriptive namings, appropriate styling and so on (a more thorough treatment is present in the QoE discussion paper OGC 17-049 entitled Ensuring Quality of User Experience with OGC Web Mapping Services available at https://portal.ogc.org/files/?artifact_id=74403&version=1). -The in-depth study of the OGC CDB 1.0 feature data dictionary and attribution schema; +QoS focuses on providing reliable (i.e. quantitative ) measures of spatial data service metrics which can be used to characterize how a service ( one or more specific datasets exposed by a certain service) is performing both in near real-time as well as historically. It touches concepts like availability, scalability (also known as capacity), absolute performance (i.e. speed) and can be used to assess also perceived performance by final clients. As mentioned above, it is typically measured using metrics like error rates, throughput, availability and delay or request response time. -The requirements and constraints for extending the CDB feature data dictionary (FDD) and attribute schemas; +Quite often the QoS and QoE aspects of spatial data services are underestimated if not simply ignored due to lack of resources as well as lack of awareness, resulting in services which are difficult to exploit (i.e. QoE very low) and/or unstable or very slow (i.e. QoS very low). The result is that few users end up using them after the initial launch and this is especially true for services targeting end users who are used to interact with services a-la Google Maps which delivers extreme performance and scalability as well as bullet-proof usability. -The development and prototyping of the WFS and WCS access to the CDB datastore for a NAS based urban military scenario. + + 2019-02-15 + + - - OGC Testbed-13: CDB Engineering Report - 2018-01-11 - - - 07-057r7 - Web Map Tile Service Implementation Standard - 07-057r7 - - OpenGIS Web Map Tile Service Implementation Standard - + 18-028r2 + WMS QoSE Engineering Report + Guy Schumann + + OGC Testbed-14: WMS QoSE Engineering Report + + 18-028r2 + + + + + Volume 3: OGC CDB Terms and Definitions + + + + + 2018-12-19 + 15-112r3 + Volume 3: OGC CDB Terms and Definitions + Carl Reed + This CDB Volume provides terms and definitions. Many of the terms and definitions are specific to the simulation industry. Other terms and definitions have been updated to be consistent with the ISO 19xxx (Geomatics) series of standards, specifically ISO 19111 Spatial referencing by Coordinates and ISO 19017 Spatial Schema. Some work still remains to make the terms and definitions completely consistent with current OGC and ISO best practice. + 15-112r3 + + + + + This OGC Discussion Paper (DP) provides a proposal for a temporality extension for the WFS 2.0 and FES 2.0 standard. It is based on the work of and experiences made in several OWS test beds, in particular OWS-7 and OWS-8, Aviation threads and discussions at the 2011 OGC TC meeting in Brussels, Belgium. This DP partially replaces and advances the document OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0 [4]. + + 2013-06-18 + + + OGC Web Feature Service (WFS) Temporality Extension + 12-027r2 + OGC Web Feature Service (WFS) Temporality Extension + + 12-027r2 + Timo Thomas + + + + 01-009 + 2001-01-12 + + + 01-009 + Coordinate Transformation Service Implementation Specification + + + + OpenGIS Coordinate Transformation Service Implementation Specification + The OpenGIS® Coordinate Transformation Service Standard (CTS) provides a standard way for software to specify and access coordinate transformation services for use on specified spatial data. This standard addresses a key requirement for overlaying views of geodata (“maps”) from diverse sources: the ability to perform coordinate transformation in such a way that all spatial data are defined relative to the same spatial reference system. + Martin Daly + + + + + + + + 2006-05-09 + The purpose of this document is to show how to map the various types of metadata documents to be used in the OWS3 project into the ebRIM. + Catalog 2.0 IPR for ebRIM + + 05-109r1 + Catalog 2.0 IPR for ebRIM + + + + 05-109r1 + + Panagiotis (Peter) A. Vretanos, Rento Primavera + + + This document defines specific DGIWG requirements, +recommendations and guidelines for implementations of the +ISO and OGC Web Map Service standards; ISO 19128:2005 +Web Map Server Interface and the OpenGIS Web Map Server +Implementation Specification 1.3.0. + 09-102r3 + Defence Profile of OGC Web Map Service 1.3 Revision + Defence Profile of OGC Web Map Service 1.3 Revision + + + 2021-02-25 + - 2010-04-06 + + 09-102r3 + + DGIWG + + + OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification Version 1.1 Release Notes + 19-034r1 + + Carl Reed, Tamrat Belayneh + 19-034r1 + - This Web Map Tile Service (WMTS) Implementation Standard provides a standard based solution to serve digital maps using predefined image tiles. The service advertises the tiles it has available through a standardized declaration in the ServiceMetadata document common to all OGC web services. This declaration defines the tiles available in each layer (i.e. each type of content), in each graphical representation style, in each format, in each coordinate reference system, at each scale, and over each geographic fragment of the total covered area. The ServiceMetadata document also declares the communication protocols and encodings through which clients can interact with the server. Clients can interpret the ServiceMetadata document to request specific tiles. - - Joan Masó, Keith Pomakis, Núria Julià + 2023-03-13 + + + OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification Version 1.1 Release Notes + This document provides the set of revision notes for OGC I3S Community Standard [OGC 17-014r5] and does not modify that standard. +This document provides the details of edits, deficiency corrections, and enhancements of the above-referenced standard. It also documents those items that have been deprecated. Finally, this document provides implementations details related to issues of backwards compatibility. + - - The OGC Vector Tiles Pilot 2: Tile Set Metadata Engineering Report (ER) describes a conceptual model for Tile Set Metadata that provides information about the intended usage of a Tile Set as well as the origin, security level, tiling scheme, layers and feature properties contained within. In this ER, a tile set is a series of tiles containing data and following a common tiling scheme. - -The metadata is intended to facilitate retrieval of tile sets and describes the major characteristics of tile sets without actually accessing the tiles nor the content contained in a tile. Such a process could be time consuming when there are a large number of tiles in a tile set. + + 18-058r1 + OGC API - Features - Part 2: Coordinate Reference Systems by Reference corrigendum + OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks. -Additionally, this ER summarizes the discussions about Tile Set Metadata among the VTP2 participants, and draws up conclusions and recommendations for future work on the subject. +OGC API Features provides API building blocks to create, modify and query features on the Web. OGC API Features is comprised of multiple parts, each of them is a separate standard. -Finally, this ER describes the Technology Integration Experiments (TIEs) performed to test the prototype implementation of the proposed Tile Set Metadata Model on API endpoints, client applications, and GeoPackages. - 19-082r1 - Vector Tiles Pilot 2: Tile Set Metadata Engineering Report +This part extends the core capabilities specified in Part 1: Core with the ability to use coordinate reference system identifiers other than the defaults defined in the core. + - + + OGC API - Features - Part 2: Coordinate Reference Systems by Reference corrigendum + + 2022-05-11 + + 18-058r1 + + Clemens Portele, Panagiotis (Peter) A. Vretanos + + + + + Documents of type Implementation Specification Corrigendum - deprecated + + + Documents of type Implementation Specification Corrigendum - deprecated + Documents of type Implementation Specification Corrigendum - deprecated + + - - Sergio Taleisnik - OGC Vector Tiles Pilot 2: Tile Set Metadata Engineering Report - 19-082r1 + Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside + + Geography Markup Language (GML) Encoding Specification + 02-023r4 - - 2020-07-08 + 02-023r4 + 2003-01-29 + + + The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features. + OpenGIS Geography Markup Language (GML) Encoding Specification + - - J - This document will discuss how OWS services can be ported to Web Services and highlight various issues/problems that have been discovered and need further discussion. + + + Ordering Services for Earth Observation Products Adoption Voting Comments and Answers + 11-111 + + 2012-01-25 + 11-111 + + This document lists the No votes received during the TC adoption vote (2011-05-03 - 2011-07-02) together with the responses from the OSEO SWG. - OGC Web Services SOAP Experiment Report - 03-014 - 2003-01-15 - + + + Daniele Marchionni + Ordering Services for Earth Observation Products Adoption Voting Comments and Answers + + + David Rosinger, Stan Tillman + 07-163 + + + + 07-163 + Data View Architecture Engineering Report + + This OGC document presents a summary of the Data View Architecture experiment conducted as part of the Geo-Processing Workflow (GPW) thread in the OWS-5 test bed. The main activities in this experiment were the storage of Data Views in an ebRIM Catalog and the discovery and use of those Data Views by an Integrated Client. - 03-014 - - OGC Web Services SOAP Experiment Report + OWS-5 Data View Architecture Engineering Report + 2008-05-02 + + + 04-095 + + + + Peter Vretanos + 04-095 + Filter Encoding Implementation Specification + OpenGIS Filter Encoding Implementation Specification + + 2005-05-03 + + The OpenGIS® Filter Encoding Standard (FES) defines an XML encoding for filter expressions. A filter expression logically combines constraints on the +properties of a feature in order to identify a particular subset of features to be operated upon. For example, a subset of features might be identified to render them in a particular color or convert them into a user-specified format. Constraints can be specified on values of spatial, temporal and scalar properties. An example of a filter is: Find all the properties in Omstead County owned by Peter Vretanos. + +This standard is used by a number of OGC Web Services, including the Web Feature Service [http://www.opengeospatial.org/standards/wfs], the Catalogue Service [http://www.opengeospatial.org/standards/cat] and the Styled Layer Descriptor Standard [http://www.opengeospatial.org/standards/sld]. + - - 2015-11-18 - OGC® CF-netCDF 3.0 encoding using GML Coverage Application Schema - The OGC CF-netCDF data model supports multi-dimensional gridded data and multidimensional multi-point data, representing space and time-varying phenomena. In particular, this extension standard is limited to multi-point, and regular and warped grids. -This standard specifies the CF-netCDF data model encoding using the OGC GML 3.2.1 coverage application schema, as well as CF-netCDF data exchange format and protocol encoding. -This standard specifies: (a) the CF-netCDF GML encoding to be used by OGC standards; (b) the CF-netCDF data format exchanged using OGC standards; (c) the Internet protocol characteristics to effectively exchange CF-netCDF data. -As per the GML 3.3. standard, GML 3.3 imports the 3.2 schema. The canonical location of the 3.2 all components schema document for 3.3 is -http://schemas.opengis.net/gml/3.2.1/gml.xsd + + 10-025r1 + Observations and Measurements - XML Implementation + This standard specifies an XML implementation for the OGC and ISO Observations and Measurements (O&M) conceptual model (OGC Observations and Measurements v2.0 also published as ISO/DIS 19156), including a schema for Sampling Features. This encoding is an essential dependency for the OGC Sensor Observation Service (SOS) Interface Standard. +More specifically, this standard defines XML schemas for observations, and for features involved in sampling when making observations. These provide document models for the exchange of information describing observation acts and their results, both within and between different scientific and technical communities. + Observations and Measurements - XML Implementation + + - CF-netCDF 3.0 encoding using GML Coverage Application Schema - 14-100r2 + 2011-03-22 - + 10-025r1 + - - - 14-100r2 - Ben Domenico, Stefano Nativi + Simon Cox - - Documents of type Specification Profile - deprecated - Documents of type Specification Profile - deprecated - Documents of type Specification Profile - deprecated - + + + Arliss Whiteside + Some image geometry models + This discussion paper contains the material that is still relevant from Section 6 (or Appendix A) of the previous version 4 (document OGC 99-107) of OGC Abstract Specification Topic 7, titled The Earth Imagery Case. That version of Topic 7 has now been superseded by a new version with the same title. +In addition, some terminology has been revised to be consistent with the terminology now used in Topic 16: Image Coordinate Transformation Services. Specifically, the previous term real-time image geometry model has been changed to approximate image geometry model. Also, the previous name Universal Real-Time Image Geometry Model has been changed to Universal Image Geometry Model. + + 04-071 + Some image geometry models + + - - + 04-071 + 2004-10-04 + + - - OGC CDB Version 1.1 Release Notes - Carl Reed - + - 2018-12-19 - - + + Testbed 10 Report on Aviation Architecture + 14-008 + Matthes Rieke + 2014-07-15 + This document is a deliverable of the OGC Testbed 10 (Testbed-10). This document describes the +architecture that was implemented in the Testbed-10 Aviation thread. Additionally, it provides +descriptions of all software components involved in the Aviation architecture as well as a +dedicated chapter focusing on the evaluation and design of FIXM 2.0. Here, a special focus lies +on the integration into the data provisioning components, namely the Web Feature and Event +Services. + + OGC® Testbed 10 Report on Aviation Architecture + - CDB Version 1.1 Release Notes - 18-016r1 - - This document provides release notes for version 1.1 of the CDB Standard and related Best Practices. - 18-016r1 + 14-008 + - - + + - OGC Testbed-17: SIF Semantic Model Engineering Report - 2022-04-08 - Mahnoush Alsadat Mohammadi Jahromi, Alex Robin - OGC Testbed-17: SIF Semantic Model Engineering Report - 21-030 - - 21-030 - This Engineering Report (ER) presents an analysis of the semantic model of the Sensor Integration Framework (SIF). After reviewing the current SIF Semantic Model, existing related ontologies are reviewed. The ER discusses the results and includes all lessons learned from the experiments completed by the Sensor Integration thread of the OGC Testbed-17 initiative. The ER presents a series of recommendations based on the lessons learned. - + Geography Markup Language + 02-009 + Ron Lake + + 02-009 + + 2002-01-14 + + Geography Markup Language + + The Geography Markup Language (GML) is an XML encoding for the transport and storage of geographic information, including both the geometry and properties of geographic features. + + + 2009-10-13 + Ben Domenico + CF-netCDF Encoding Specification + 09-122 + + NetCDF (network Common Data Form) is a data model for array-oriented scientific data, a freely distributed collection of access libraries implementing support for that data model, and a machine-independent format. Together, the interfaces, libraries, and format support the creation, access, and sharing of scientific data. + + + CF-netCDF Encoding Specification - - - - - 15-001r4 - OGC® 3D Portrayal Service 1.0 - The 3D Portrayal Service Standard is a geospatial 3D content delivery implementation specification. It focuses on what is to be delivered in which manner to enable interoperable 3D portrayal. - -It does not define or endorse particular content transmission formats, but specifies how geospatial 3D content is described, selected, and delivered. It does not prescribe how aforementioned content is to be organized and represented, but provides a framework to determine whether 3D content is interoperable at the content representation level. More details are available in Design of this standard. - - - 15-001r4 - 3D Portrayal Service 1.0 - 2017-09-13 - - Benjamin Hagedorn, Simon Thum, Thorsten Reitz, Voker Coors, Ralf Gutbell - - - + 09-122 + + + 05-089r1 + 2005-12-01 + 05-089r1 + Sensor Planning Service + Sensor Planning Service + The Sensor Planning Service (SPS) is intended to provide a standard interface to collection assets (i.e., sensors, and other information gathering assets) and to the support systems that surround them. +The SPS is designed to be flexible enough to handle a wide variety of configurations. + Ingo Simonis + + + - - 11-055 + + + + - - 11-055 - OGC SAA Pilot Study Engineering Report - 2011-11-23 - OGC SAA Pilot Study Engineering Report - This OGC® document describes the architecture used for the implementation of the SAA Dissemination Pilot Study demonstrations. This includes an overview of the implemented components and workflows, and discussions of lessons learned. - - Steve Miller + + The SLD is an encoding for how the Web Map Server (WMS 1.0 & 1.1) specification can be extended to allow user-defined symbolization of feature data. + 02-070 + Styled Layer Descriptor (SLD) Implementation Specification + + + Bill Lalonde + + 2002-08-19 + + OpenGIS Styled Layer Descriptor (SLD) Implementation Specification + 02-070 - - 06-103r4 - Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture - - The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. - 2011-05-28 + + + 2017-09-22 - John Herring - - OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture - 06-103r4 + 16-107r2 + InfraGML 1.0: Part 7 – LandInfra Land Division - Encoding Standard + + 16-107r2 + OGC InfraGML 1.0: Part 7 – LandInfra Land Division - Encoding Standard + + This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. +InfraGML is published as a multi-part standard. This Part 7 addresses the LandDivision and Condominium Requirements Classes from LandInfra. + - + Paul Scarponcini - - - - - Documents of type Implementation Specification Corrigendum - deprecated - Documents of type Implementation Specification Corrigendum - deprecated - Documents of type Implementation Specification Corrigendum - deprecated + + Peter Baumann + OWS-8 Geoprocessing for Earth Observations Engineering Report + 11-116 + + Ad-hoc processing of Earth Observation (EO) data available through online resources is +gaining more and more attention. Expected benefits include +- More versatile EO data access +- More convenient EO data access +- Consequently, broadened use and exploitation of EO data +- An important step towards integration of EO data into automatic chaining and +orchestration +- More efficient EO data access: indicating the exact desired result and evaluating +processing code close to the coverage data source (i.e., on the server) minimizes +network traffic, one of today’s critical performance limiting factors. + + 11-116 - - - 2006-07-27 - Jens Fitzke, Rob Atkinson + + 2011-12-19 + + OWS-8 Geoprocessing for Earth Observations Engineering Report + + + 20-032 + OGC API - Environmental Data Retrieval Sprint Engineering Report + + + + The subject of this Engineering Report (ER) is a development Sprint that was held from March 18-20, 2020 to advance the Open Geospatial Consortium (OGC) Environmental Data Retrieval (EDR) Application Programming Interface (API) candidate standard. Due to the widespread of the virus, the Sprint was held virtually by using GoToMeeting teleconferencing facilities of OGC, email and GitHub. - Gazetteer Service - Application Profile of the Web Feature Service Implementation Specification - 05-035r2 - Gazetteer Service - Application Profile of the Web Feature Service Implementation Specification - 05-035r2 - This document defines a Gazetteer Service profile of the OGC Web Feature Service Specification. The OGC Gazetteer Service allows a client to search and retrieve elements of a georeferenced vocabulary of well-known place-names. - - - + + 20-032 + 2020-10-22 + Chris Little, Peng Yue, Steve Olson + OGC API - Environmental Data Retrieval Sprint Engineering Report - - 16-027 - Testbed-12 Web Service Implementation Engineering Report - Johannes Echterhoff, Clemens Portele - - 2017-05-12 - This document is a deliverable of the OGC Testbed-12. It describes the results of analyzing the Testbed-12 web service implementations. - -OGC has been developing web service specifications since the OGC Web Mapping Testbed in 1999. In particular, the original OGC Web Map Service specification has been developed during that testbed. 17 years later most current OGC web service standards still follow the general approach that had been developed in 1999 (the capabilities document, the remote procedure call via HTTP paradigm, etc). - -Over time, the OGC web service approach has been amended and extended in different ways by different OGC standards and profiles. In addition, some of the more flexible mechanisms have been used in practice in different ways by different software vendors or communities. The OGC Web Service Common standard had been a response by OGC to these developments and aimed at maintaining a consistent approach across the different OGC web service standards. However, this effort has been only partially successful for several reasons, including shortcomings in the OWS Common standard, the existence of multiple incompatible OWS Common versions and a reluctance by working groups and communities to introduce incompatible changes to existing service types in order to harmonize. All attempts in recent years to continue the work on OWS Common have not seen much traction. While there seems to be general agreement that the current situation is not optimal and that consistency is desirable, it is unclear how to improve in a way that meets market demands. - -This document summarizes information about the web service implementations in Testbed-12. It is not and should not be understood as a general analysis or assessment of the OGC web service architecture, but a low-key effort to gain some insights from looking at a significant number of web service implementations and their use in interoperability experiments and demos. - -During the years since 1999 not only the OGC standards baseline has evolved, but also the Web itself. The W3C has been working on identifying Best Practices for Data on the Web and W3C and OGC are jointly working on extending this with Best Practices for Spatial Data on the Web. The analysis also includes an assessment about the OGC approach to web services with respect to the draft best practices at the time of writing of this report. - -To the extent possible, we draw conclusions and recommendations from the information that has been gathered. These fall into three categories: + + Andreas Matheus + The OGC suite of standards address the interoperable exchange of geographic information. The Web Service Implementation Standards define the discovery, delivery, and processing services that make information exchange possible. Common aspects of those Web Service standards have been collected into the OGC Web Services Common standard. While there are multiple versions of OWS Common, and flexibility in how it is applied, this combination of standards does enable interoperability. -Improving the interoperability of OGC web services as they are today +However, OWS Common neglected to address security. As soon as a service endpoint (an OGC Web Service instance) is secured, there is no guarantee of interoperability. -Support for new requirements in a consistent way across service types +The OWS Common - Security Standards Working Group (SWG) was approved by the TC in September 2015 (http://www.opengeospatial.org/projects/groups/comsecurityswg). It held its first meeting during the December 2015 TC meetings. The objective of this SWG to define an extension to the existing OWS Common to ensure interoperability between a secured service instance and client. This OWS Common Security Extension adds content to the standard regarding the implementation of security controls in such a way as to preserve interoperability. These additions will be in two areas. The first extension will provide more detail on the use of the HTTP protocol, particularly as it related to security controls. The second extension will address discovery and negotiation of security controls. This will provide an annotation model for the Capabilities document to enable a service provider to specify the security implemented at a service instance (endpoint). -Improvements to the standardization process +This ER shall serve as the technical background to the OWS Common - Security SWG to ensure that the standard that is to be created is comprehensive and suitable for all OGC Web Services standards, to overcome the interoperability hurdle, and - at the same time - maintain backwards compatibility. -In addition, there is also a specific case that does not fit into these general categories. - - 16-027 - + + - Testbed-12 Web Service Implementation Engineering Report + 16-048r1 + Testbed-12 OWS Common Security Extension ER + + + 2017-03-10 + Testbed-12 OWS Common Security Extension ER + 16-048r1 - - 12-028r1 + + Summary of the Architecture, Engineering, Construction, Owner Operator Phase 1 (AECOO-1) Joint Testbed - - 12-028r1 - Use of Geography Markup Language (GML) for Aviation Data - - The document provides guidelines for the use of GML and a GML profile description in the -scope of aeronautical data encoding, in particular when using the Aeronautical Information -Exchange Model (AIXM). In the future, the applicability of the guidelines contained in this -document might be enlarged to cover other related domains, such as aeronautical weather data -and flight data. - - 2016-03-24 - Use of Geography Markup Language (GML) for Aviation Data - - - OGC Aviation Domain Working Group - - - OGC API - Tiles - Part 1: Core - 2022-11-10 - 20-057 - - Joan Masó, Jérôme Jacovella-St-Louis + + Louis Hecht, Jr., Raj Singh + - - OGC API — Tiles is a standard defining building blocks for creating Web APIs that support the retrieval of geospatial information as tiles. Different forms of geospatial information are supported, such as tiles of vector features (“vector tiles”), coverages, maps (or imagery) and other types of geospatial information. Although it can be used independently, the OGC API — Tiles building blocks can be combined with other OGC API Standards and draft specifications for additional capabilities or increasing interoperability for specific types of data. The OGC API — Tiles standard references the OGC Two Dimensional Tile Matrix Set (TMS) and Tileset Metadata standard, which defines logical models and encodings for specifying tile matrix sets and describing tile sets. A tile matrix set is a tiling scheme that enables an application to partition and index space based on a set of regular grids defined for multiple scales in a Coordinate Reference System (CRS). - -This specification is a successor to the OGC’s Web Map Tile Service (WMTS) standard, focusing on simple reusable REST API building blocks which can be described using the OpenAPI specification. Whereas WMTS focused on map tiles, the OGC API — Tiles standard has been designed to support any form of tiled data. - OGC API - Tiles - Part 1: Core - 20-057 - - + Summary of the Architecture, Engineering, Construction, Owner Operator Phase 1 (AECOO-1) Joint Testbed + 10-003r1 + 10-003r1 + The Architecture, Engineering, Construction, Owner Operator, Phase 1 (AECOO-1) Testbed developed and implemented methods to streamline communications between parties in the conceptual design phase to get an early understanding of the tradeoffs between construction cost and energy efficiency. To that end, the project developed the interoperability components required for these analyses in collaborative team settings. These were Information Delivery Manuals (IDMs) for quantity takeoffs and energy analysis business processes, and used these to define Model View Definitions (MVDs)—standards-based subsets of Industry Foundation Classes (IFCs). AECOO-1 was conducted in response the felt need that overall productivity loss and fragmentation in the capital facilities development industries is no longer tolerable. All stakeholders need to practice the best way they know, and practice profitably; software interoperability problems must not hold them back. Non-interoperable software and data is cause for loss of competition across the market. + + 2010-06-04 - - 2012-03-20 - - - 10-030 - + + 2003-05-22 + 03-053r1 + OGC Technical Document Baseline + 03-053r1 + + Spreadsheet of OGC Technical Document Baseline - - Topic 19 - Geographic information - Linear referencing - 10-030 - Topic 19 - Geographic information - Linear referencing - Paul Scarponcini - - Same as ISO IS 19148: 2012. Download at http://www.iso.org - - - 17-066r1 - GeoPackage Extension for Tiled Gridded Coverage Data - The “GeoPackage Extension for Tiled Gridded Coverage Data” extension (previously titled Elevation Extension) defines how to encode and store tiled regular gridded data, such as a digital elevation model, in a GeoPackage. In the ISO 19123 Schema for Coverage Geometry standard and in the OGC Coverage Implementation Schema, this type of regular gridded data is classed as grid-regular[1]. The tiles contain values, such as elevation, temperature or pressure, and may be stored as 16-bit PNG files or 32-bit TIFF files. The extension defines two ancillary data tables: one for regular gridded coverages and one for tiles. When using the PNG encoding, a scale and offset may be applied. The extension also allows for a TIFF encoding but constrains many of the TIFF options that are available to simplify development. - Carl Reed - 2018-03-07 + + + Carl Reed, George Percivall + - + OGC Technical Document Baseline + + + + + + Thomas Kolbe, Gerhard Groeger and Angela Czerwinski - - OGC GeoPackage Extension for Tiled Gridded Coverage Data - + + City Geography Markup Language + 2006-08-18 + CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language 3 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211. - 17-066r1 - - - 06-080r1 - GML Application Schema for EO Products - - 2007-02-05 - GML Application Schema for EO Products - - - - 06-080r1 - This document defines an application schema of the Geography Markup Language (GML) version 3.1.1 for describing Earth Observation products (EO products) within the HMA (Heterogeneous EO Missions Accessibility) Application Profile for the OGCTM Catalogue Services Specification v2.0.0 (with Corrigendum) [OGC 04-021r3] - Jerome Gasperi + + 06-057r1 + City Geography Markup Language + 06-057r1 - - - + + 16-003r2 + Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values + + This OGC Best Practice, a volume of the CDB document set, provides a list and description of the instance-level attribution fields held in Navigation Dataset Instance Attribute files. Please refer to section 3.7 of the CDB Core Standard (Volume 1) for information on the tables that use the Navaids key words. + Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values - Documents of type Technical Baseline - deprecated - Documents of type Technical Baseline - deprecated - Documents of type Technical Baseline - deprecated - - - - - OGC API standards define modular API building blocks to spatially enable Web APIs in a consistent way. The OpenAPI specification is used to define the API building blocks. - -OGC API Features provides API building blocks to create, modify and query features on the Web. OGC API Features is comprised of multiple parts, each of them is a separate standard. - -This part extends the core capabilities specified in Part 1: Core with the ability to use coordinate reference system identifiers other than the defaults defined in the core. - - 18-058 - - - OGC API - Features - Part 2: Coordinate Reference Systems by Reference - - 2020-11-02 - 18-058 - OGC API - Features - Part 2: Coordinate Reference Systems by Reference - Clements Portele, Panagiotis (Peter) A. Vretanos - - + - 2011-03-28 + Carl Reed + + 2017-02-23 + 16-003r2 + + + Health Spatial Data Infrastructure Concept Development Study Engineering Report + 21-021 + + + Experts agree that access to, sharing, and application of location-enabled information is a key component in addressing health related emergencies. While the present COVID-19 pandemic has underscored a range of successes in dealing with the COVID virus, many gaps in supporting local to global preparedness, forecasting, monitoring, and response have been identified when dealing with a health crisis at such an unprecedented level. This study considers how a common, standardized health geospatial data model, schema, and corresponding spatial data infrastructure (SDI) could establish a blueprint to better align the community for early warning, response to, and recovery from future health emergencies. Such a data model would help to improve support for critical functions and use cases. + 21-021 + 2022-01-24 + Health Spatial Data Infrastructure Concept Development Study Engineering Report - - Alexandre Robin, Philippe Mérigot - The SPS 2.0 Earth Observation Satellite Tasking Extension Standard specifies extensions to the OGC Sensor Planning Service (SPS) 2.0 Interface Standard. The SPS configuration proposed in this extension is intended to support the programming process of Earth Observation (EO) sensor systems. This standard describes a consistent SPS configuration that can be supported by many satellite data providers, most of whom have existing facilities for the management of these programming requests. The resulting extended web service interface can be used for determining the feasibility of an intended sensor planning request, for submitting such a request, for inquiring about the status of such a request, for updating or canceling such a request, and for requesting information on means of obtaining the data collected by the requested task. + + + Alan Leidner, Mark Reichardt, Josh Lieberman - OGC® Sensor Planning Service Interface Standard 2.0 Earth Observation Satellite Tasking ExtensionOGC® Sensor Planning Service - 10-135 - 10-135 - Earth Observation Satellite Tasking Extension for SPS 2.0 - - - - + - Joint OGC OSGeo ASF Code Sprint 2021 Summary Engineering Report - 21-008 - - 2021-04-12 - - Joint OGC OSGeo ASF Code Sprint 2021 Summary Engineering Report - 21-008 - + 19-069 + OGC Testbed-15: Maps and Tiles API Engineering Report + OGC Testbed-15: Maps and Tiles API Engineering Report + 19-069 + + 2020-01-08 + Joan Maso Pau - Gobe Hobona, Angelos Tzotsos, Tom Kralidis, Martin Desruisseaux - The subject of this Engineering Report (ER) is a code sprint that was held from 17 to 19 February 2021 to advance support of open geospatial standards within the developer community, whilst also advancing the standards themselves. The code sprint was hosted by the Open Geospatial Consortium (OGC), the Apache Software Foundation (ASF), and Open Source Geospatial Foundation (OSGeo). The event was sponsored by Ordnance Survey (OS) and GeoCat BV, and held as a completely virtual event. - - - Spatial Data on the Web Use Cases & Requirements - 15-074r1 - 2015-12-17 - Frans Knibbe, Alejandro Llaves - 15-074r1 - - This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC. + In 2017 the OGC began a focused effort to develop Application Programming Interface (API) standards that support the Resource Oriented Architecture and make use of the OpenAPI specification. As part of this effort, this OGC Testbed 15 Engineering Report (ER) defines a proof-of-concept of an API specification for maps and tiles. + +The OGC API Maps and Tiles draft specification described in this ER builds on the precedent of the OGC API - Features - Part 1: Core standard. The OGC API - Tiles draft specification describes a service that retrieves data representations as tiles, which are generally small compared with the geographic extent of the data. In the draft specification, the assumption is that tiles are organized into Tile Matrix Sets consisting of regular tile matrices available at different scales or resolutions. The OGC API – Tiles draft specification is described as a building block that can be plugged into an OGC API - Features service to retrieve tiled feature data (sometimes called vector tiles) or to an OGC API – Maps implementation to retrieve rendered tiles (sometimes called map tiles). In the future, the OGC API - Tiles draft specification could extend other specifications, one possible candidate being the emerging OGC API – Coverages draft specification. + +The OGC API - Maps draft specification describes an API that presents data as maps by applying a style. These maps can be retrieved in a tiled structure (if OGC API - Tiles is approved as an OGC Implementation Standard) or as maps of any size generated on-the-fly. The OGC API - Maps draft specification implements some functionality, specified in the Web Map Tile Service (WMTS) 1.0 standard, related to the use of styles by using the Styles API draft specification that was developed in the Testbed-15 Open Portrayal Framework thread. + +The draft Maps and Tiles API specifications are designed in a modular way. With the exception of the core requirements, the other conformance classes describe functionality that can be considered optional characteristics that can be combined by server implementations at will. + +At the beginning of Testbed-15, the original proposed title for this ER was OGC Testbed-15: Web Map Tiling Service Draft Specification Engineering Report but in the course of the Testbed-15 that title was changed to better represent the content. - Spatial Data on the Web Use Cases & Requirements + - - - - - - This document contains a description of the schema tailoring process for application schema development based on the U.S. National System for Geospatial-Intelligence (NSG) GEOINT Structure Implementation Profile (GSIP) as developed in conjuction with the Open Geospatial Consortium Interoperability Program initiative OWS-4. - GEOINT Structure Implementation Profile Schema Processing - 07-028r1 - GEOINT Structure Implementation Profile Schema Processing - - + + + + OGC Testbed-13: Workflows ER + Benjamin Pross, Christoph Stasch + 2018-01-08 + + 17-029r1 + Testbed-13: Workflows ER - - Clemens Portele - 07-028r1 - 2007-05-17 - - - The Application Package OGC Engineering Report (ER) defines a data model and serialization for Thematic Exploitation Platforms (TEP) Application Packages. A TEP refers to a computing platform that follows a given set of scenarios for users, data and ICT provision aggregated around an Earth Science thematic area. This ER is part of the Testbed-13 Earth Observation Clouds (EOC) effort to support the development by the European Space Agency (ESA) of the TEP by exercising envisioned workflows for data integration, processing, and analytics based on algorithms developed by users that are deployed in multiple clouds. + + 17-029r1 + This Engineering Report (ER) addresses the development of a consistent, flexible, adaptable workflow that will run behind the scenes. A user should be able to discover existing workflows via a catalog and execute them using their own datasets. An expert should be able to create workflows and to publish them. Previous OGC Testbed initiatives investigated workflows in the geospatial domain: -The wide usage of virtualization and the possibility to start virtual environments within Cloud services significantly simplifies the creation of environments and provisioning of resources. However, it still leaves a problem of portability between infrastructures. This ER identifies a strategy for packaging an application in a Cloud environment that will be able to run in a predictable manner in different computing production environments. The application packaging specifies the elements that will ensure: +OWS 3 Imagery Workflow Experiments -Scientific reproducibility, +OWS 4 WPS IPR Workflow descriptions and lessons learned -Dependencies identification and management, +OWS 4 Topology Quality Assessment Interoperability Program Report -Maintainability from an operational perspective and avoid version pilling, +OWS 5 Data View Architecture Engineering Report -Portability in different Cloud providers +OWS 6 Geoprocessing Workflow Architecture Engineering Report -The ER proposes the use of containers, defining everything required to make a piece of software run packaged into isolated containers. Unlike a Virtual Machine (VM), a container does not bundle a full Operating System (OS) - only libraries and settings required to make the software work are needed. This makes for efficient, lightweight, self-contained systems and guarantees that software will always run the same, regardless of where it’s deployed. A discussion on application deployment and execution is presented in the separate OGC Testbed-13 Application Deployment and Execution Service ER [1]. +These initiatives mostly favored Business Processing Execution Language (BPEL) as the workflow execution language. More recent studies ([6], [7]) were performed using BPMN as a means for describing and executing workflows comprised of OGC Web services. This ER will give an overview about existing approaches to compose and execute geospatial workflows and will describe the approach taken in Testbed-13, taking into account security aspects. + + + + application/json + + git:c89beb527ab5c15420e81e8661f606c28f76194f + + + + Matthes Rieke, Aleksandar Balaban + + 2017-04-25 + The Asynchronous Messaging for Aviation Engineering Report (ER) focuses on the design of an architecture to create an Publish/Subscribe (PubSub) messaging layer between different Aviation components such as clients, data provider instances and Data Brokers. In order to achieve interoperability among these components, the OGC PubSub 1.0 standard forms the basis of this architecture. The design of this architecture will cover methods for subscribing for specific subsets of data (e.g. Flight Information Exchange Model (FIXM) Flights intersecting a given Airspace), managing such subscriptions as well as publishing data to the Asynchronous Messaging Server. Different delivery methods such as Advanced Message Queuing Protocol (AMQP) 1.0, Java Message Service (JMS) and OASIS WS-Notification are considered. In particular, their harmonization with OGC PubSub 1.0 is evaluated. - - 2018-01-30 - Testbed-13: EP Application Package Engineering Report - 17-023 - 17-023 - +This report focuses on the interface design required to define an interoperable approach for Aviation using this OGC PubSub 1.0. Specific service level integrations (i.e., Federal Aviation Administration (FAA) System-Wide Information Management (SWIM) and Single European Sky ATM Research Programme (SESAR) SWIM) have been investigated but an implementation has not been fulfilled. + Testbed-12 Asynchronous Messaging for Aviation + 16-017 + Testbed-12 Asynchronous Messaging for Aviation + + 16-017 - - Pedro Gonçalves + - OGC Testbed-13: EP Application Package Engineering Report - - - - - 2008-09-12 - Chris Holmes + - - This Discussion Paper is about the use of KML, an encoding used to express geographic annotation and visualization on existing or future web-based online maps (2d) and earth browsers (3d). KML uses a tag-based structure with nested elements and attributes and is based on the XML standard. - OWS-5 KML Engineering Report - 07-124r2 - - OWS-5 KML Engineering Report - 07-124r2 - + The OGC has extended its suite of Standards to include Resource Oriented Architectures and Web APIs. In the course of developing these Standards, some practices proved to be common across multiple OGC Web API Standards. These common practices are documented in the OGC API — Common Standard. The OGC API - Common Standard is a multi-part standard that specifies reusable building-blocks that can be used in the construction of OGC API Standards. This document presents Part 1, the Core, of the OGC API – Common Standard. Standards developers will use these building-blocks in the construction of other OGC Standards that relate to Web APIs. The result is a modular suite of coherent API standards which can be adapted by a system designer for the unique requirements of their system. + +The purpose of the OGC API — Common — Part 1: Core Standard (API-Core) is to define those fundamental building blocks and requirements which are applicable to all OGC Web API Standards. + + + 19-072 + + 19-072 + OGC API - Common - Part 1: Core + 2023-03-28 + OGC API - Common - Part 1: Core + + Charles Heazel - - Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes - + + 2017-08-16 + This OGC InfraGML Encoding Standard presents the implementation-dependent, GML encoding of concepts supporting land and civil engineering infrastructure facilities specified in the OGC Land and Infrastructure Conceptual Model Standard (LandInfra), OGC 15-111r1. Conceptual model subject areas include land features, facilities, projects, alignment, road, railway, survey (including equipment, observations, and survey results), land division, and condominiums. +InfraGML is published as a multi-part standard. This Part 3 addresses the Alignment Requirements Class from LandInfra. + 16-103r2 + Paul Scarponcini - Carl Reed - Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes - 16-005r2 - 16-005r2 - 2017-02-23 - - - This document provides the Annexes for the CDB Core: Model and Physical Structure standard. The only exception is Annex A, Abstract Test Suite. The CDB ATS Annex is in Volume 1: Core document. + + + InfraGML 1.0: Part 3 - Alignments - Encoding Standard + 16-103r2 + + OGC InfraGML 1.0: Part 3 - Alignments - Encoding Standard + + + 12-139 + + 12-139 + OWS-9: SSI Security Rules Service Engineering Report + + + In this engineering report we describe how to administrate XACML v2.0, XACML v3.0 and GeoXACML v1.0.1 access control policies through a “Security Rules Service”. Following the XACML and ISO terminology this service plays the role of a Policy Administration Point (PAP) and is therefore called XACML Policy Administration Point (XACML PAP) or XACML Policy Administration Web Service (XACML PAWS). +After introducing OWS-9’s Common Rule Encoding and motivating all components required to administrate (Geo)XACML policies, we describe the interface of a powerful XACML PAP on a conceptual level. This interface definition could serve as a baseline for a future OASIS or OGC XACML Policy Administration Web Service (e.g. OGC XACML PAWS) specification. + + + + Jan Herrmann, Andreas Matheus + + 2013-02-05 + OWS-9: SSI Security Rules Service Engineering Report - - 13-080r3 - 13-080r3 - Military Operations Geospatial Interoperability Experiment (MOGIE) - Frank Klucznik, Matthew Weber, Robin Houtmeyers, Roger Brackin - 2013-10-25 + + + 2022-01-21 + 21-022 + + Alex Robin - - - OGC® Military Operations Geospatial Interoperability Experiment (MOGIE) + OGC Testbed-17: Sensor Integration Framework Assessment ER - - experiment demonstrated that GML content can be embedded in NIEM conformant XML and be exploited by commercial and open source tools without loss of precision (e.g., right number of bits) or accuracy (e.g., physical location on a map). Embedding GML in NIEM conformant XML was accomplished in MOGIE using the NIEM adapter. - - - - This position paper is aimed at city officials and domain professionals working in an urban data context. Its goal is to clarify the concept of Urban Digital Twins (UDT) and to position it in regards of Digital Twins in general as well as the emerging Metaverse. - -Overall, the UDT concept is an approach to understand characteristics and processes of the built environment at the scale of a city. Between climate change and various demographics, dynamic cities are facing challenges that are becoming more complex to solve. Most of the time solutions have to be imagined with a system of systems approach and cannot be solved in silos. + + 21-022 + OGC Testbed-17: Sensor Integration Framework Assessment ER + This OGC Testbed 17 Engineering Report (ER) documents the outcomes of a review and implementation of the Sensor Integration Framework Standards Profile (SIF-SP) v1.0.1, published by the National Center for Geospatial Intelligence Standards (NCGIS). -The paper represents the current state of the discussion about UDTs in the Open Geospatial Consortium (OGC), a geospatial community and standards organization. +The Sensor Integration Framework Standard Profiles (SIF-SP) authors rightly acknowledge that sensing systems and the environments they operate in (e.g. hardware platform, computing resources, connectivity, ease of deployment, etc.) are very heterogeneous and that there will never be a single suite of technology or standards that can support the goal of providing unified access to sensor deployments employed in complex applications. -Around 3 use cases, climate change adaptation, urban transformation, and urban air mobility, this paper identifies benefits of using a UDT and explain the role of Geospatial Information (GI) and how it can contribute to an UDT. +Instead, rather than trying to impose a single standard or suite of standards, the SIF-SP approach defines common conceptual models that can be mapped to existing and future standards, thus allowing integration of all these standards in a single framework. -UDTs is a digital representation of the city where elected representatives and professional stakeholders can access and contribute to a common reference model to collaborate, achieving positive outcomes for the citizens. UDTs reveal insights at the intersection of the natural and built environments and human activities. They provide the means of enabling simulation scenarios and plan possible interventions as well as tracking measurable evidence of any changes in the real world. In a mature state, UDTs will establish effective feedback loops between the virtual and the true, physical environments. +This approach is fully compatible with the OGC Sensor Web Enablement (SWE) suite of standards that were designed for this type of integration. Thus, existing and upcoming SWE standards defined in the OGC can be used as the central pillar of a SIF implementation. The test implementation developed in this testbed, and based on OpenSensorHub, focused on demonstrating this aspect. -From discussions with elected representatives, professionals, and also based on OGC member experience on projects, it is acknowledged that the process of building an UDT might seem daunting (as outlined in the paper by [Lei, 2023]: Challenges of urban digital twins: A systematic review and a Delphi expert survey). +In addition to a thorough review of the SIF material — including standards documents, UML models and ontologies — a prototype implementation of the SIF standards was created during the Testbed using OpenSensorHub. This allowed the testbed participants to check the practical feasibility of fulfilling the SIF requirements using the OGC SWE suite of standards. Details and feedback regarding this implementation are also provided in this ER. -This paper presents a pragmatic approach based on OGC standards for each use case, building on location and GI as the foundation. This approach calls for an effective data strategy and suggests that a project-based approach with a vision of building a UDT is the most efficient path. +Suggestions to improve SIF-SP and make it an integral part of the OGC standard baseline are also provided. -This concept of UDT, although often mentioned in the media, is still fairly new in practice and the governance of that type of platform is still a challenge. OGC is keen on supporting and collaborating on projects to help create the best practices on that matter. - - - 24-025 - Urban Digital Twins: Integrating Infrastructure, natural environment and people + + + + Peter Baumann + + 08-068r3 + Web Coverage Processing Service (WCPS) Language Interface Standard + Web Coverage Processing Service (WCPS) Language Interface Standard - Urban Digital Twins: Integrating Infrastructure, natural environment and people + The OGC Web Coverage Processing Service (WCPS) defines a protocol-independent language for on-demand extraction, processing, and analysis of multi-dimensional gridded coverages (datacubes) representing among others spatio-temporal sensor, image, simulation, or statistics data. + - Carsten Rönsdorf, Fabrice Servant, H.C. Gruler, Nick Giannias, Kyoungsook Kim, Zubran Soleiman, Dim - 24-025 - 2024-07-02 - + 2021-06-15 + + + 08-068r3 - - Incident Management Information Sharing (IMIS) Internet of Things (IoT) Extension Engineering Report - The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives. - -· Apply Open Geospatial Consortium (OGC) principles and practices for collaborative development to existing standards and technology in order to prototype an IoT approach to sensor use for incident management. - -· Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability. - -· Development of profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability. - -· Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario. - -These principles continued through the IoT Pilot Extension, with additional objectives of: - -· Integration into the existing Next Generation First Responder (NGFR) Apex development program process as part of Spiral 1; - -· Defining steps to begin the integration of existing incident management infrastructure, e.g., pulling in National Institute of Emergency Management (NIEM) message feeds; and - -· Demonstration and experimentation in a ‘realistic’ incident environment using two physically separate sites–an incident site within an active first responder training facility (Fairfax County Lorton site), and a command center (DHS S&T Vermont Avenue facility). - -The initial Pilot activity has been documented in three OGC public engineering reports. The present report describes and documents the additional activities and innovations undertaken in the Extension. - 16-092r2 - 16-092r2 - Incident Management Information Sharing (IMIS) Internet of Things (IoT) Extension Engineering Report - + + + This OGC Discussion Paper provides a comparison between the OGC CityGML and IndoorGML standards. The goals and approaches of these two standards are different and they can be used in a complementary way. This discussion paper aims to compare the strengths and weakness of the standards, and explain how to integrate the standards to make useful applications. These comparative experiments are based on a real site: a shopping mall at Lotte World Mall in Seoul, South Korea. + + 16-012r1 + Comparing CityGML and IndoorGML based on a use case at Lotte World Mall + Ki-Joune Li, Hyung-Gyu Ryu, Hak-Cheol Kim, Jun Hee Lee, Joo-Ho Lee + + Comparing CityGML and IndoorGML based on a use case at Lotte World Mall + 16-012r1 + - - - - Roger Brackin - 2018-01-18 + 2016-12-22 - - 09-142r1 - Open GeoSMS Specification - 09-142r1 - OGC®: Open GeoSMS Specification - 2010-02-01 - - - - + - Chun-fu Lin, Zhong-Hung Lee, Jen-Chu Liu, Kuo-Yu Chuang + Definition identifier URNs in OGC namespace + 07-092r1 + - This standard specifies the location formats to be used by SMS for mobile phones and in other systems handling the SMS with location formats produced by mobile phones or LBS services. + This Best Practices Paper specifies Universal Resource Names (URNs) in the ogc URN namespace to be used for identifying definitions. This document specifies the formats used by these URNs, plus a set of specific URNs for specific definitions. These definitions should be used wherever applicable by implementations of various OGC Implementation Specifications, including GML, WMS, WFS, and WCS. + + 2007-11-14 + Definition identifier URNs in OGC namespace + + 07-092r1 + + Arliss Whiteside - - Testbed-12 WCS Profile Update Engineering Report - - - + + This document specifies Universal Resource Names (URNs) in the “ogc” URN namespace to be used for identifying definitions. These definitions include definitions of Coordinate Reference Systems (CRSs) and related objects, as specified in OGC Abstract Specification Topic 2: Spatial referencing by coordinates, plus several other resource types for which standard identifiers are useful in OGC Web Services. This document specifies the formats used by these URNs, including formats that can reference definitions recorded in the EPSG database and by other authorities. This document also specifies URNs for some specific definitions for which OGC is the custodian. + Arliss Whiteside + Definition identifier URNs in OGC namespace + 07-092r3 - - 16-033r1 - 16-033r1 - Testbed-12 WCS Profile Update Engineering Report - - This engineering report capture the work to extend the existing Web Coverage Service (WCS) profiles, particularly the Earth Observation Application Profile (EO-WCS [OGC 10-140r1]) to support multi-dimensional subsetting of 3D space and 1D time. The updated EO-WCS (EO-WCS1.1 [OGC 10-140r2]) have removed the requirement for the 2D coverages so that it can explicitly allow coverages with more dimensions as long as they have geographic footprint. Furthermore it also clarified the use of rangeType when non-NCNAME characters are present in a band identifier. The example of GetCapabilites, DescribeEOCoverageSet, and _GetCoverage request in the updated EO-WCS1.1 is shown with use case on fire emission data in San Francisco. - -Following the recommendation for EO-WCS to fully embrace the N-D, multi-dimensional, concept of Coverages as a function of time and other coordinates alongside the geospatial ones, the proposed recommendations/changes in the extension for WCS DescribeCoverage, EO-WCS DescribeEOCoverageSet, and WCS GetCoverage are discussed with use case example using National Centers for Environmental Prediction (NCEP) Global 0.25 deg wind data. Based on the mutual recommendation from the US National Aeronautics and Space Administration (NASA) and Baart et. al (2012), Network Common Data Form (NetCDF) was the output format due to presence of its libraries in multiple languages to lower the burden in changing on developers of WCS-compliant servers and clients. - -For the extension of the WCS DescribeCoverage, it is recommended that CIS1.1 should be considered adopting a scheme for transmitting coordinates similar to the _cis:rangeSet where data are referred to as an attached Multipurpose Internet Mail Extensions (MIME) part. Time, as much as possible, be treated as just another coordinates dimension so that it could be access with the same tools used for other coordinate dimensions. To tackle the issue on order of coordinate dimensions, it is recommended to add implementation note to the EO-WCS specifications so that implementers are aware of the mismatches between dataset coordinate reference systems (CRSs) and actual axis order. - -For the extension of EO_WCS DescribeEOCoverageSet, the issue on missing range of results API needed to be resolved by adding a request mechanism for requesting a range of matching results. It is also recommended that DescribeEOCoverageSet activity might be of more use to the client if the client need to supply only the subset conditions, and not a list of identifiers. - -For the extension of WCS GetCoverage, it was discovered that for the GetCoverage operation for higher dimensioned datasets, existing WCS-2.0 request interface provided adequate syntax for subsetting higher dimensional data. Scaling (re-gridding) operation appears to be a natural fit for the EO-WCS subsetting, specifically SCALEEXTENT activity, however simpler explanation might be needed to fully understand its use as it appears other scaling and subsetting commands may be more than adequate for the desired outcomes. Additionally allowing SlicePoint subsetting is also recommended. - -After performing the testing in the client side, there were few potential recommendations for improvements. More information on whether the coverage is 2D or 3D form the GetCapalilites request might be helpful to client so it can limit the number of DescribeCoverage requests to construct a list of available coverage on the server. Furthermore additional metadata information for displaying meaningful native gird coordinates is also recommended for clarification. Finally automatic detection of lat/lon axes along with clear treatment of XY and lat/lon axes ordering would be an improvement in the existing operations. - 2017-04-28 - Ranjay Shrestha, Liping Di, Eugene G. Yu + + + + + + 2009-01-15 + 07-092r3 + Definition identifier URNs in OGC namespace - - - - Clemens Portele, Panagiotis (Peter) A. Vretanos, Charles Heazel + + + This OGC document represents an OWS-5 SWE thread Engineering Report on sub-setting georeferencable imagery. It discusses how to handle georeferencable imagery in the JPEG2000 format as well as using JPIP within the WCS-T and the SWE set of services. + OWS-5 WCS JPIP Coverage Subsetting Engineering Report + 07-169 + 2008-09-12 + 07-169 + + Steven Keens + + + OWS-5 WCS JPIP Coverage Subsetting Engineering Report + + + + + OWS-7 Aviation - WXXM Assessment Engineering Report + 2010-08-18 + + 10-132 - 17-069r4 - OGC API - Features - Part 1: Core corrigendum - 17-069r4 - This document specifies the behavior of Web APIs that provide access to features in a dataset in a manner independent of the underlying data store. This standard defines discovery and query operations. - -Discovery operations enable clients to interrogate the API, including the API definition and metadata about the feature collections provided by the API, to determine the capabilities of the API and retrieve information about available distributions of the dataset. - -Query operations enable clients to retrieve features from the underlying data store based upon simple selection criteria, defined by the client. - - 2022-05-11 - OGC API - Features - Part 1: Core corrigendum + + Bruno Simmenauer + The document describes the results of using OGC Web Services for accessing and using WXXM data, notably within aviation scenarios involving rerouting procedures motivated by the sudden closure of airspace areas caused by the eruption of a volcano. The focus of this document will be to evaluate the ability to encode and serve associated operational data with WXXM 1.1.1. + + OWS-7 Aviation - WXXM Assessment Engineering Report + 10-132 - - 15-073r2 - 15-073r2 - Testbed-11 DGIWG GMLJP2 testing results Engineering Report - 2015-11-18 + - This OGC Engineering Report (ER) describes work done in OGC Testbed 11 to test -GMLJP2 in terms of defining a DGIWG GMLJP2 version 1 profile. -The requirements for a DGIWG profile of GMLJP2 have been documented in the -DGIWG GMLJP2 version 1 profile. The Imagery WG inside DGIWG has developed a -filter to map the files produced using the previous GMLJP2 schema into the GMLJP2 -version 2 schema and is about to submit a GMLJP2 2.0 profile to DGIWG. -The DGIWG implementation of the GMLJP2 profile is based on the OGC GMLJP2 v2 -and other requirements are coming directly from the adoption inside the DGIWG of the -new OGC GMLJP2 version 2. -This Testbed 11 activity is a response to the need of harmonization between DGIWG and -OGC. + 08-094r1 + + + + 2011-01-04 + This standard defines low level data models for exchanging sensor related data between nodes of the OGC® Sensor Web Enablement (SWE) framework. These models allow applications and/or servers to structure, encode and transmit sensor datasets in a self describing and semantically enabled way. + + 08-094r1 + SWE Common Data Model Encoding Standard + OGC® SWE Common Data Model Encoding Standard + Alexandre Robin + + + + + + + Documents of type Profile Corrigendum - Approved + Documents of type Profile Corrigendum - Approved + Documents of type Profile Corrigendum - Approved + + + 10-090r3 + + 10-090r3 + Network Common Data Form (NetCDF) Core Encoding Standard version 1.0 + - - OGC® Testbed-11 DGIWG GMLJP2 testing results Engineering Report - - - E. Devys, L.Colaiacomo, P. Baumann + OGC Network Common Data Form (NetCDF) Core Encoding Standard version 1.0 + + + Ben Domenico + This document specifies the network Common Data Form (netCDF) core standard and extension mechanisms. The OGC netCDF encoding supports electronic encoding of geospatial data, specifically digital geospatial information representing space and time-varying phenomena. +NetCDF is a data model for array-oriented scientific data. A freely distributed collection of access libraries implementing support for that data model, and a machine-independent format are available. Together, the interfaces, libraries, and format support the crea-tion, access, and sharing of multi-dimensional scientific data. + + + 2011-04-05 - - - David Blodgett, Byron Cochrane, Rob Atkinson, Sylvain Grellet, Abdelfettah Feliachi, Alistair Ritchi + + Arliss Whiteside + 2006-07-19 + + This document is a corrigendum for OGC Document 05-096r1, titled GML 3.1.1 grid CRSs profile. This corrigendum is based on change request OGC 06-041. - Systems that maintain and disseminate information representing and/or related to spatial features often lack mechanisms to describe or discover how features relate to each other, to other kinds of features, and to a wide variety of related information that may be relevant. The Environmental Linked Features Interoperability Experiment (ELFIE) explored Open Geospatial Consortium (OGC) and World Wide Web Consortium (W3C) standards with the goal of establishing a best practice for exposing cross-domain links between environmental domain and sampling features. The Interoperability Experiment (IE) focused on encoding relationships between cross-domain features and linking available observations data to sampled domain features. An approach that leverages the OGC service baseline, W3C data on the web best practices, and JavaScript Object Notation for Linked Data (JSON-LD) contexts was developed and evaluated. Outcomes of the experiment demonstrate that broadly accepted web technologies for linked data can be applied using OGC services and domain data models to fill important gaps in existing environmental data systems' capabilities. While solutions were found to be capable and promising, OGC services and domain model implementations have limited utility for use in linked data applications in their current state and the universe of persistent URIs that form the foundation of a linked data infrastructure is still small. In addition to improvement of the standards baseline and publication of linked data URIs, establishing conventions for URI dereferencing behavior and default content given multiple options for a resource remain for future work. - 2019-02-11 - 18-097 - OGC Environmental Linked Features Interoperability Experiment Engineering Report - Environmental Linked Features Interoperability Experiment Engineering Report - 18-097 - + + 06-111 - + + GML 3.1.1 grid CRSs Profile Corrigendum + GML 3.1.1 grid CRSs Profile Corrigendum + 06-111 - + - - - Testbed-12 OWS Context: JSON, JSON-LD and HTML5 ER - 16-053r1 - Joan Masó - + This Engineering Report (ER) presents an analysis of the semantic model of the Sensor Integration Framework (SIF). After reviewing the current SIF Semantic Model, existing related ontologies are reviewed. The ER discusses the results and includes all lessons learned from the experiments completed by the Sensor Integration thread of the OGC Testbed-17 initiative. The ER presents a series of recommendations based on the lessons learned. + OGC Testbed-17: SIF Semantic Model Engineering Report + 21-030 + OGC Testbed-17: SIF Semantic Model Engineering Report - At the time of finalizing this ER the OGC TC has approved the OWS Context JSON encoding that is available here: http://www.opengeospatial.org/standards/owc This is the second encoding proposed for the OWS context standard precided by the Atom Encoding [OGC 12-084r2]. The OWS Context JSON enconding is based on the GeoJSON IETF standard [RFC7946]. The standard is a combination of two approaches: - -mapping between the OWS Context conceptual model [12-080r2] to the basic structure of a GeoJSON file. - -a direct conversion of the rest of the atom keys and the specific OWS Context XML into JSON following OGC 14-009r1. - -The conversion was designed with current GeoJSON viewers in mind (including the one embedded in GitHUB) and making possible that they can visualize a OWS Context GeoJSON file without any modifications. - -This ER focus on describing another encoding (a 3rd alternative) that allows for exposing geospatial resources on the web in a way that web browsers and search engines can better understand. It is widely known that HTML was designed with the linking capacity in mind. Both, users reading HTML and automatic crawlers, transverse links constantly. HTML seems the natural selection for linking geospatial data on the web. The question is how to complement the linking mechanism with some additional metadata that search engines could use for indexing. A solution could come from a mechanism which web search engines already have agreed to use for better indexing: schema.org. - -Schemna.org proposes three enconding for their data model: Microdata, RDFa and JSON-LD. The reader might easily get confused by the fact that OGC approved a JSON encoding for OWS context and another JSON encoding emerges in this document. This ER is NOT proposing to replace or modify the currently approved JSON enconding for OWS context based on GeoJSON. The intention is to map the OWS Context model into the schema.org model to recognize that they are very similar and propose a encoding in HTML5 that can be done in the 3 alternative proposed by schema.org. - - - Testbed-12 OWS Context: JSON, JSON-LD and HTML5 ER - 16-053r1 - 2017-06-16 - - + + 2022-04-08 + + 21-030 + Mahnoush Alsadat Mohammadi Jahromi, Alex Robin + + + OWS Integrated Client (GeoDSS Client) + + + 2007-03-08 + OWS Integrated Client (GeoDSS Client) + 05-116 + - - Geolinking Service - 04-011r1 - 04-011r1 + This Interoperability Program Report (IPR) provides an overview of the general requirements, architecture, and design considerations of + 05-116 + Stan Tillman, Jody Garnett - 2004-05-04 - - Geolinking Service - Peter Schut - A Geolinking Service takes attribute data which refers to spatial features, and joins it to a geospatial dataset, so that it can be mapped by a WMS or used in a GIS. When a Geolinking Service uses data from a GDAS, and serves as a front end to a WMS, it enables real-time mapping of data stored in non-spatial databases. - - - + + + 05-107 - 23-042 - OGC Testbed-19 — Non-Terrestrial Geospatial Engineering Report - - OGC Testbed-19 — Non-Terrestrial Geospatial Engineering Report + Reference Model for the ORCHESTRA Architecture + + Reference Model for the ORCHESTRA Architecture + 05-107 + This document specifies the Reference Model for the ORCHESTRA Architecture (RM-OA). It contains a specification framework for the design of ORCHESTRA-compliant service networks and provides a platform-neutral specification of its information and service viewpoints. + + - Sina Taghavikish - 23-042 + + 2006-01-31 + Thomas Uslander (Ed.) + + + + - 2024-07-05 - - Testbed-18 explored the potential use of OGC Standards for non-terrestrial applications and was scoped as a paper study. Validation of the Testbed-18 recommendations has been left for Testbed-19. This OGC Engineering Report (ER) documents recommended changes to OGC Standards and the implementation experience to justify those changes. - -The use of OGC Standards include geospatial applications for non-Earth planets as well as interplanetary spatiotemporal applications. Two Standards emerged as key: ISO 19111 (OGC Abstract Specification 2: Referencing by coordinates) and OGC 21-056r11 (OGC GeoPose 1.0 Data Exchange Standard). Extensions to ISO 19111 were identified which would support the representation of non-terrestrial planetary spatial reference systems as well as interplanetary spatiotemporal reference systems. - -The GeoPose Standard (GeoPose) was explored as a mechanism to integrate the large number of reference systems and transformations needed to model the geometry of interplanetary spacetime. - -In the context of the Double Asteroid Redirection Test (DART) scenario, positions and orientations in different coordinate reference systems and associated attributes such as velocities of non-terrestrial objects were encoded using two different approaches: as sequences of extended GeoPoses, and as OGC Moving Features JSON (MF-JSON). These encoded data were then used as the basis for a 3D visualization demonstration. - -This work is not intended to replace the existing standards already used in astronomy such as the World Coordinate System (WCS). The recommendations provided in this ER are rather intended to improve interoperability by specifying how to export a subset of a WCS description as OGC/ISO data structures for consumption by GIS software or other geospatial technology applications. - -Testbed-18 also investigated how GeoPose could be integrated with mobile location-aware devices such as smartphones. Engineering Report OGC 22-016r3 (Testbed-18: Moving Features) concluded that GeoPose could enrich data with location and orientation information synchronized to video and other sensors and identified two suitable road network use cases for study using WebVMT in Testbed-19. + This Engineering Report (ER) summarizes the OGC Testbed-14 findings and recommendations to “semantically enable” existing data and metadata models used in the aviation industry. Examples of such data and metadata models include Aeronautical Information Exchange Model (AIXM) [1], Weather Information Exchange Model (WXXM) [2], Flight Information Exchange Model (FIXM) [3],Web Service Description Document (WSDD), Service Description Conceptual Model (SDCM) [4]). These models use Linked Data standards to represent this information and aim to improve the search and discovery of services and information in the aviation domain using the System Wide Information Management (SWIM) environment. This report provides a review of the existing data models and explore different approaches to provide a semantic representation of the current metadata and data models used in the aviation domain. The ER also discusses the role and importance of the controlled vocabularies. + Semantically Enabled Aviation Data Models Engineering Report + 18-035 + OGC Testbed-14: Semantically Enabled Aviation Data Models Engineering Report + + + + 18-035 + Stephane Fellah + 2019-02-07 - - - + + + + + + + - - Graham Vowles - 06-004r4 - Topic 18 - Geospatial Digital Rights Management Reference Model (GeoDRM RM) - - + + + + OGC 3D Tiles Specification 1.0 + Patrick Cozzi, Sean Lilley, Gabby Getz + 2019-01-31 - This document is a reference model for digital rights management (DRM) functionality for geospatial resources (GeoDRM). As such, it is connected to the general DRM market in that geospatial resources must be treated as nearly as possible like other digital resources, such as music, text, or services. It is not the intention here to reinvent a market that already exists and is thriving, but to make sure that a larger market has access to geospatial resources through a mechanism that it understands and that is similar to the ones already in use. - - 2007-01-29 - 06-004r4 - - Topic 18 - Geospatial Digital Rights Management Reference Model (GeoDRM RM) - - - OGC Testbed-14: Federated Clouds Engineering Report - Federated Clouds Engineering Report - 18-090r1 - - 18-090r1 - The geospatial community has had an on-going challenge with being able to share data and compute resources in dynamic, collaborative environments that span different administrative domains. For these types of requirements, the concept of federation has been developed. The near-term goal of the Federated Cloud task in OGC Testbed-14 is to demonstrate a specific data-sharing scenario among two or more administrative domains using existing security tooling, e.g., OpenID Connect and OAuth. The main details of this work are reported as part of the OGC Testbed-14 Security Engineering Report (ER) cite:[SecurityER]. This Federated Cloud Engineering Report (ER) dovetails with the Security ER to: + + + 18-053r2 + 3D Tiles Specification 1.0 + 18-053r2 + 3D Tiles is designed for streaming and rendering massive 3D geospatial content such as Photogrammetry, 3D Buildings, BIM/CAD, Instanced Features, and Point Clouds. It defines a hierarchical data structure and a set of tile formats which deliver renderable content. 3D Tiles does not define explicit rules for visualization of the content; a client may visualize 3D Tiles data however it sees fit. -Coordinate across all federation-related tasks in Testbed-14, including the Earth Observation Cloud and Workflow tasks, +A 3D Tiles data set, called a tileset, contains 3D data organized into a spatial data structure. The primary format for delivering the 3D data is glTF 2.0. Additional formats for geospatial tile data are also specified in this document. These tile formats include Batched 3D Models, Instanced 3D Models, Point Clouds and Composite tiles. -Understand the overall federation design space, +This document specifies the following elements of a tileset: -Analyze and critique the scope, trade-offs and limitations of the federation capabilities being built and demonstrated in Testbed-14, +The core data structures for tilesets +Tile formats for delivering 3D data +An implicit representation of tilesets that are organized in quadtrees or octrees +Metadata that may be associated to elements of a tileset on different levels of granularity +Declarative styling which may be applied to tilesets for their visualization +The 3D Tiles specification for tilesets, associated tile formats, metadata, and the associated styling specification are open formats that are not dependent on any vendor-specific solution, technology, or products. -Identify and prioritize possible incremental development tasks for subsequent testbeds, and +The majority of the content in this OGC document is a direct copy of the content contained at the 1.1 tag of the 3d-tiles repo. No normative changes have been made to the content. This OGC document does contain content not contained in the 1.1 tag of the 3d-tiles repo. -Liaison with groups external to OGC, such as the National Institute of Standards and Technology (NIST)/Institute of Electrical and Electronics Engineers (IEEE) Joint Working Group on Federated Cloud, to promote the further development and adoption of federated capabilities, and ultimately international standards. +Cesium has published the 3D Tiles 1.1 Reference Card as an approachable and concise guide to learning about the main concepts in 3D Tiles, intended to jumpstart developers in adopting 3D Tiles. + + + 2021-02-26 + + 16-004r5 + + + + + + 16-004r5 + Volume 5: OGC CDB Radar Cross Section (RCS) Models (Best Practice) + This CDB volume provides all of the information required to store Radar Cross Section (RCS) data within a conformant CDB data store. + Carl Reed + Volume 5: OGC CDB Radar Cross Section (RCS) Models (Best Practice) + + + Simple Features Implementation Specification for CORBA + 99-054 + + 1999-06-02 + + Peter Ladstaetter + 99-054 + OpenGIS Simple Features Implementation Specification for CORBA - Dr. Craig A. Lee - 2019-03-05 + + + + The Simple Feature Specification application programming interfaces (APIs) provide for publishing, storage, access, and simple operations on Simple Features (point, line, polygon, multi-point, etc). + + + Volume 14 OGC CDB Guidance on Conversion of CDB Shapefiles into CDB GeoPackages (Best Practice) + 2021-02-26 + + + 19-066 + + + + 19-066 + Volume 14 OGC CDB Guidance on Conversion of CDB Shapefiles into CDB GeoPackages (Best Practice) + + This OGC Best Practice (BP) document describes the conversion process for converting a CDB structured Shapefile into a CDB structured GeoPackage. This is the companion document to Volume 13: OGC CDB Rules for Encoding CDB Vector Data using GeoPackage (Normative, Optional Extension). Volume 13 defines the requirements and provides CDB specific guidance on using GeoPackage containers in a CDB data store. + + Michala Hill + + + 2021-03-23 + Josh Lieberman + MUDDI v1.1 (Model for Underground Data Definition and Integration) Engineering Report + + MUDDI v1.1 (Model for Underground Data Definition and Integration) Engineering Report + 19-081 + The Underground Infrastructure Concept Development Study (UICDS) Engineering Report [1] examined the present state of underground infrastructure information (UGII), costs and benefits of that state, as well as future opportunities for an improved state. That report describes a number of candidate models for UGII and recommends a number of follow-on activities, including development of a prototype UGII integration model to support subsequent UGII integration and exchange initiatives. A follow-up workshop and model development effort resulted in another engineering report describing an initial (1.0) version of the conceptual UGII integration model MUDDI (Model for Underground Data Definition and Interchange) [2]. The present updated report describes MUDDI version 1.1. The goal of MUDDI is to serve as the basis for integration of datasets from different models, at the levels of detail required to address application use cases described in [1]. MUDDI as described here is a conceptual model which will serve as the basis for one or more conformant and interchangeable logical and physical implementations such as GML (Geographic Markup Language) or SFS (Simple Features SQL). The current version 1.1 of MUDDI has been updated and refined from the initial version 1.0, but is still intended to serve as an input to the proposed OGC Underground Infrastructure Pilot as well as similar implementations and deployments in realistic application scenarios. The present model is also suitable as input to begin development of a formal conceptual model standard. + + 19-081 - - - - - 19-086r4 - - OGC API - Environmental Data Retrieval Standard - - Mark Burgoyne, Dave Blodgett, Chuck Heazel, Chris Little - - OGC API - Environmental Data Retrieval Standard - 19-086r4 - The Environmental Data Retrieval (EDR) Application Programming Interface (API) provides a family of lightweight query interfaces to access spatio-temporal data resources by requesting data at a Position, within an Area, along a Trajectory or through a Corridor. A spatio-temporal data resource is a collection of spatio-temporal data that can be sampled using the EDR query pattern geometries. These patterns are described in the section describing the Core Requirements Class. + + + Testbed-12 Javascript-JSON-JSON-LD Engineering Report + + 16-051 + Joan Masó + + + 16-051 + Testbed-12 Javascript-JSON-JSON-LD Engineering Report + The Testbed-11 deliverable OGC 15-053 Implementing JSON/GeoJSON in an OGC Standard ER enumerated strategies for implementing JSON in OGC services and OGC encodings. Previously, a mechanism to migrate XML into JSON was proposed by Pedro Gonçalves in 14-009r1 OGC Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context. In contrast, this engineering report (ER) proposes a mechanism to derive JSON and JSON-LD encodings from UML modeling without using XML as an intermediate step. The rules provided can be divided into rules for JSON instances and rules for JSON schemas. -The goals of the EDR API are to make it easier to access a wide range of data through a uniform, well-defined simple Web interface, and to achieve data reduction to just the data needed by the user or client while hiding much of the data storage complexity. A major use case for the EDR API is to retrieve small subsets from large collections of environmental data, such as weather forecasts, though many other types of data can be accessed. The important aspect is that the data can be unambiguously specified by spatio-temporal coordinates. +These rules have been applied to the UML diagrams in OWS common 2.0 to derive JSON encodings for them. In practice this ER evaluates how to provide service metadata in the derived JSON. JSON schemas and @context documents for independent validation of the four main sections of the ServiceMetadata are provided. This activity is done in connection with the OGC 16-052 OWS Context / Capabilities ER. The rules are applied to WMS to provide a full JSON encoding for the WMS 1.4 standard candidate. -The EDR API query patterns, such as Position, Area, Cube, Trajectory or Corridor, can be thought of as discrete sampling geometries, conceptually consistent with the feature of interest in the Sensor Observation Service (SOS) standard. A typical EDR data resource is a multidimensional dataset that could be accessed via an implementation of the Web Coverage Service (WCS) standard. In contrast to SOS and WCS, EDR implements the technical baseline of the OGC API family of standards and aims to provide a single set of simple-to-use query patterns. Use cases for EDR range from real or virtual time-series observation retrievals, to sub-setting 4-dimensional data cubes along user-supplied sampling geometries. These query patterns do not attempt to satisfy the full scope of either SOS or WCS, but provide useful building blocks to allow the composition of APIs that satisfy a wide range of geospatial data use cases. By defining a small set of query patterns (and no requirement to implement all of them), the EDR API should help to simplify the design of systems (as they can be performance tuned for the supported queries) making it easier to build robust and scalable infrastructure. +Finally, this ER discusses the applicability to data geospatial formats, both for coverage formats (compared to the CIS standard) and feature formats (compared to GeoJSON). -With the OGC API family of standards, the OGC community has extended its suite of standards to include Resource Oriented Architectures and Web Application Programming Interfaces (APIs). These standards are based on a shared foundation, specified in OGC API-Common, which defines the resources and access paths that are supported by all OGC APIs. The resources are listed in Table 1. This document extends that foundation to define the Environmental Data Retrieval API. - 2021-08-13 - - - +Readers unfamiliar with JSON, JSON-LD and JSON Schema should first read OGC 16-122 (Geo)JSON User Guide. OGC 16-122 includes guidelines and recommendations for the use of JSON and JSON-LD in OGC data encodings and services. + + + 2017-05-12 + + + Topic 2 - Referencing by coordinates Corrigendum + Roger Lott + 2021-07-02 + Topic 02 - Referencing by coordinates Corrigendum + 18-005r5 + This document is identical in normative content with the latest edition (2019) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2019]. + 18-005r5 + - 2006-07-12 - - - 06-055r1 - - Arliss Whiteside - OpenGIS GML 3.2 image geopositioning metadata application schema - 06-055r1 - GML 3.2 image geopositioning metadata application schema + + - This document specifies a GML 3.2 Application Schema for image geopositioning metadata, which is also an Application Schema of ISO 19139. This geopositioning metadata schema is used by the separately specified Image Geopositioning Service (IGS) interface that adjusts the georeferencing coordinate transformations of images. - - - - + - - GeoXACML Implementation Specification - Extension A (GML2) Encoding - 07-098r1 - 07-098r1 - Andreas Matheus - This document defines an extension to the GeoXACML Implementation Specification, Verison 1.0 for the GML2 geometry encoding as specified in the GML2 standard. - - 2008-02-23 - + + + 01-024r1 + Web Registry Server - - - GeoXACML Implementation Specification - Extension A (GML2) Encoding + Web Registry Server + Louis Reich + A Registry Service defines a common mechanism to classify, register, describe, search, maintain and access information about OGC Web resources. The OGC Service Registry provides the methods for managing a repository; a Registry Client is an application used to access the Registry. + + 01-024r1 + + + 2001-01-26 - + + 2011-05-12 - Interoperable Simulation and Gaming Sprint Engineering Report + 11-017 + Geospatial eXtensible Access Control Markup Language (GeoXACML) Version 1 Corrigendum + - 20-087 - Interoperable Simulation and Gaming Sprint Engineering Report + Geospatial eXtensible Access Control Markup Language (GeoXACML) Version 1 Corrigendum + 11-017 + The OpenGIS® Geospatial eXtensible Access Control Markup Language Encoding Standard (GeoXACML) defines a geospatial extension to the OASIS standard “eXtensible Access Control Markup Language (XACML)” [www.oasis-open.org/committees/xacml/]. This extension incorporates spatial data types and spatial authorization decision functions based on the OGC Simple Features[http://www.opengeospatial.org/standards/sfa] and GML[http://www.opengeospatial.org/standards/gml] standards. GeoXACML is a policy language that supports the declaration and enforcement of access rights across jurisdictions and can be used to implement interoperable access control systems for geospatial applications such as Spatial Data Infrastructures. GeoXACML is not designed to be a rights expression language and is therefore not an extension of the OGC GeoDRM Reference Model (Topic 18 in the OpenGIS® Abstract Specification [http://www.opengeospatial.org/standards/as]). + Andreas Matheus, Jan Herrmann + + + + + + This document describes the 3D portrayal server components which were used in the OGC OWS-6 Decision Support Systems (DSS) thread. The objective pf this activity was to efficiently stream and display GML 3 content in internet or wireless networks with limited bandwidth, especially focusing on the CityGML application profile. The server for delivering landscape and city models is implemented as Web 3D Service (W3DS) that is designed as portrayal service. - - Leonard Daly, Scott Serich - + - The OGC Interoperable Simulation and Gaming Sprint advanced the use of relevant OGC and Khronos standards in the modeling and simulation community through practical exercise and testing of the GeoVolumes API draft specification produced by the 3D Data Container and Tiles API Pilot. Of particular interest was the handling and integration of glTF models coming from multiple sources, but the sprint also examined the specification’s implementability, consistency, completeness, and maturity. - 2021-01-26 - 20-087 - - - - Defence Geospatial Information Working Group (DGIWG) GMLJP2/JP2 Profile for Imagery & Gridded Data 2.1.2 - This document provides a profile for JPEG 2000 for use as a -compression format for raster imagery. JPEG 2000 uses -discrete wavelet transform (DWT) for compressing raster data, -as opposed to the JPEG standard, which uses discrete cosine -transform (DCT). It is a compression technology which is best -suited for continuous raster data, such as satellite imagery and -aerial photography. This version adds support for -Referenceable imagery. + 2009-08-05 + Arne Schilling + 09-075r1 + OWS-6 3D Flythrough (W3DS) Engineering Report - 21-007 - Defence Geospatial Information Working Group (DGIWG) GMLJP2/JP2 Profile for Imagery & Gridded Data 2.1.2 - 2021-11-16 - 21-007 - - + + 09-075r1 + OWS-6 3D Flythrough (W3DS) Engineering Report - - DGIWG - - This document specifies Universal Resource Names (URNs) in the “ogc” URN namespace to be used for identifying definitions. These definitions include definitions of Coordinate Reference Systems (CRSs) and related objects, as specified in OGC Abstract Specification Topic 2: Spatial referencing by coordinates, plus several other resource types for which standard identifiers are useful in OGC Web Services. This document specifies the formats used by these URNs, including formats that can reference definitions recorded in the EPSG database and by other authorities. This document also specifies URNs for some specific definitions for which OGC is the custodian. - Definition identifier URNs in OGC namespace - - 2009-01-15 - - - Definition identifier URNs in OGC namespace - 07-092r3 - - 07-092r3 + + 2021-02-04 + + GeoPackage Encoding Standard + 12-128r17 - Arliss Whiteside + + OGC® GeoPackage Encoding Standard + + + 12-128r17 + Jeff Yutzler + This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. - - Peter Vretanos - 03-003r10 - Level 0 Profile of GML3 for WFS - - 2004-05-10 - - + + + Provides essential and abstract models for GIS technology that is widely used. - *RETIRED* This is a GML application profile known as Level 0 - also known as Simple GML. - 03-003r10 - - Level 0 Profile of GML3 for WFS + + 99-103 + Topic 03 - Locational Geometry Structures + 1999-03-18 + Topic 3 - Locational Geometry Structures + Cliff Kottman + 99-103 + + + + + + Web Notification Service + 03-008r2 + Ingo Simonis, Andreas Wytzisk + + + The Web Notification Service (WNS) is the first asynchronous messaging service specified by OGC. At the moment, the WNS message schema is optimized to fulfil the needs of services supporting the use of sensors, like Sensor Planning Service. Future work activities should include the adaptation of the message schema to the needs of other services. + + 2003-04-21 + + + 03-008r2 + Web Notification Service - - 17-093r1 - Jeff Yutzler, Ashley Antonides + + + 2018-07-31 + 18-004r1 + The Role of Geospatial in Edge-Fog-Cloud Computing - An OGC White Paper + George Percivall - GeoPackage Related Tables Extension Interoperability Experiment Engineering Report - 17-093r1 - 2018-08-22 + + The Role of Geospatial in Edge-Fog-Cloud Computing - An OGC White Paper + 18-004r1 + + “The cloud is dead – long live the cloud!” so begins an IEC White paper on Edge Intelligence.[1] The IEC White Paper continues that “Driven by the internet of things (IoT), a new computing model – edge-cloud computing – is currently evolving, which involves extending data processing to the edge of a network in addition to computing in a cloud or a central data centre. Edge-Fog-Cloud computing models operate both on premise and in public and private clouds, including via devices, base stations, edge servers, micro data centres and networks.” + + + + + + 2017-05-12 + Benjamin Pross + Testbed-12 Low Bandwidth & Generalization Engineering Report + 16-021r1 + Testbed-12 Low Bandwidth & Generalization Engineering Report + + For delivering of data that is offered by OGC services over (very) low bandwidth, two options may be considered: On the one hand, the geospatial features remain the same, but compression techniques are used to reduce the size of the data that needs to be transferred. On the other hand, generalization techniques may be used by reducing the details of geometries and/or attributes in order to reduce the amount of data. The aim of this ER is to summarize the results of implementing sample services using compression techniques for DGIWG WFS (U002) and providing generalization processes using WPS (U003). The ER compares the results of the different approaches and infers recommendations and best practices for supporting data delivery of standard data and complex 3D data from OGC services over low and very low bandwidth. + 16-021r1 - - - OGC GeoPackage Related Tables Extension Interoperability Experiment Engineering Report - This OGC Engineering Report describes the results of the OGC GeoPackage (GPKG) Related Tables Extension Interoperability Experiment (GPKG-RTE IE). This IE tested a proposed extension to the OGC GeoPackage Encoding Standard (12-128r14). The GPKG-RTE defines the rules and requirements for associating tables with existing feature or attribute tables in a GeoPackage data store. As part of this IE, the participants performed Technology Integration Experiments (TIEs) where they produced GeoPackages that used this extension, loaded them into GPKG-compliant software systems, and observed the results. As a result of this work, the IE participants agree that the extension is fit for use and consideration as a standard by OGC. + - - Cliff Kottman, Arliss Whiteside - Topic 16 - Image Coordinate Transformation Services - 00-116 - 00-116 - Topic 16 - Image Coordinate Transformation Services - 2000-04-24 - - Covers image coordinate conversion services. - + + Andreas Matheus + 2013-11-06 + + 13-101 + 13-101 + Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 GML 3.2.1 Encoding Extension - + OGC Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 GML 3.2.1 Encoding Extension - - - - Testbed 11 Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Round Trip Engineering Report - 15-030r3 - 2016-01-25 - The goal of the Geo4NIEM thread in OGC Testbed 11 was to gain Intelligence Community (IC) concurrence of the National Information Exchange Model (NIEM) Version 3.0 architecture through the development, implementations, test, and robust demonstration making use of IC specifications, Geography Markup Language (GML), and NIEM in a simulated “real-world” scenario. The demonstration scenario begins with NIEM-conformant Information Exchange Packages (IEPs) containing operational data and IC security tags from the Information Security Marking (ISM) and Need-To-Know (NTK) access control metadata, and the Trusted Data Format (TDF) for binding assertion metadata with data resource(s). Those instance documents are deployed using Open Geospatial Consortium (OGC) enabled Web Services for access by client applications. Access control is based on attributes of the end-user and the instance data -Recommendations to update these information exchanges were provided to reflect NIEM 3.0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment exercised this data encoding in OGC Web Feature Services (WFS) and Policy Enforcement Points (PEP) accessed by multiple client applications. The round-trip assessment also exercised the OGC Transactional Web Feature Services (WFS-T). Results from this task provided a preliminary architecture that was tested and demonstrated in Testbed 11, and summarized in other OGC Testbed 11 Engineering Reports. + + + This standard defines the version 3.0 of a valid GML 3.2.1 geometry encoding as defined in Geography Markup Language (GML) simple features profile (with Corrigendum) to be used with the GeoXACML 3.0 Core standard. +The use of this encoding extension to GeoXACML 3.0 Core enables the direct use of GML 3.2.1 encoded geometries into a GeoXACML 3.0 Policy, an Authorization Decision Request or in an Authorization Decision’s Obligation element. It thereby improves the performance of deriving access control decisions, where geometries are involved as existing GML 3.2.1 geometry encodings must not be transformed to Well Known Text (WKT) as supported by GeoXACML 3.0 Core. Furthermore, the use of this encoding extension simplifies the implementation of a Policy Enforcement Point as it must not provide the transformation functions from GML to WKT and vice versa. +This encoding extension has its normative base in Geography Markup Language (GML) simple features profile (with Corrigendum). + + + + OGC® Testbed 10 Annotations Engineering Report + 2014-07-15 + 14-002 - - - + Joan Masó and Raj Singh - Testbed 11 Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Round Trip Engineering Report - Scott Serich + Testbed 10 Annotations Engineering Report + 14-002 + + + + This OGC Engineering Report provides guidelines for dealing with geospatial +annotations in OGC standards. It proposes a generic data model and a set of mappings +into different popular encodings This OGC® document is applicable to OWS context, +GMLJP2 and any other standards that can require annotations. - 15-030r3 - - - OGC-NA tools - - - - 0.3.49 - - - - - Routing Pilot ER - 19-041r3 + + 2019-11-14 + 19-062 + OGC API Hackathon 2019 Engineering Report - - - 19-041r3 + The subject of this Engineering Report (ER) is a hackathon event that was held from 20 to 21 June 2019 to advance the development of OGC Application Programming Interface (API) specifications. An API is a standard set of documented and supported functions and procedures that expose the capabilities or data of an operating system, application or service to other applications (adapted from ISO/IEC TR 13066-2:2016). The OGC API Hackathon 2019, as the event was called, was hosted by Geovation at its hub in London, United Kingdom. The event was sponsored by the European Space Agency (ESA) and Ordnance Survey. + OGC API Hackathon 2019 Engineering Report + 19-062 - Sam Meek, Theo Brown, Clemens Portele + Gobe Hobona + - - 2020-01-08 - OGC® Routing Pilot ER - The goal of this OGC Routing Pilot Engineering Report (ER) is to document the proof of concept of an Application Programming Interface (API) conforming to a profile of the draft OGC API - Processes specification that allows implementation of vector routing across one or more routing engines. The components implemented in the OGC Open Routing API Pilot 2019 included two clients, interfacing with three implementations of the draft OGC API - Processes specification that in turn communicated with three routing engines. This work resulted in the definition of a proposed common interface and data exchange model supported by all components for requesting, generating and returning routes. + + - - + + + 11-135r2 + Name Type Specification for Coordinate Reference Systems + + 11-135r2 + OGC® Name Type Specification for Coordinate Reference Systems - Luis Bermudez + + 2013-06-18 + + + Peter Baumann + This document specifies a Name Type Specification (NTS) for predefined, combined, and parameterized Coordinate Reference System (CRS) definitions. This NTS augments the /def/ namespace with http URI definitions for CRSs. The NTS is based on the Name Type Specification – definitions – part 1 – basic name [OGC 09-048r3] and supersedes OGC document “Definition identifier URNs in OGC name¬space” [OGC 07-092r3]. +NTSs are maintained by the OGC Naming Authority (OGC-NA). +This document includes one Annex: a user guide to the OGC CRS resolver. + + + + + + + 06-103r3 + Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture + + + OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture + + 2007-01-29 - 17-088r1 - Strengthening Disaster Risk Reduction Across the Americas Summit - Simulated Exercise Engineering Report - + - 2018-02-07 - 17-088r1 - Strengthening Disaster Risk Reduction Across the Americas Summit - Simulated Exercise Engineering Report - - Disasters are responsible for major socioeconomic damages. Global initiatives call for the improvement of information technology infrastructure to better share data and advance multinational collaboration. - -The Strengthening Disaster Risk Reduction Across the Americas: A Regional Summit on the Contributions of Earth Observations held on September 3-8 in 2017 in Buenos Aires, Argentina strengthened the collective ability to share the many challenges of disaster risk reduction in Latin America and the Caribbean (LAC) while promoting the awareness and better use of earth observations (EO). + The OpenGIS® Simple Features Interface Standard (SFS) provides a well-defined and common way for applications to store and access feature data in relational or object-relational databases, so that the data can be used to support other applications through a common feature model, data store and information access interface. OpenGIS Simple Features are geospatial features described using vector data elements such as points, lines and polygons. -A simulation exercise took place during the summit. The exercise brought together government, emergency managers, earth observation data providers, academics, non-governmental organizations, and commercial companies. The participants assessed the capabilities and needs of policymakers, regional and on-the-ground decision makers, and learned what information products can be produced, and when and how such products are available. +Part 1 “Common Architecture supplies the common feature model for use by applications that will use the Simple Features data stores and access interfaces. -This ER describes the description and results of the simulated scenario including the post-exercise activity that captured the lessons learned from the participants. +Part 2 provides a standard SQL implementation of the abstract model in Part 1. (Note: The OpenGIS® Simple Features Interface Standards for OLE/COM and CORBA are no longer current and are not provided here.) +The corresponding standard for the Web is the OpenGIS® Web Feature Service Interface Standard http://www.opengeospatial.org/standards/wfs. + 06-103r3 + John Herring - - 16-115 - Future City Pilot 1 - Recommendations on Serving IFC via WFS + + GeoPackage Encoding Standard + 12-128r19 + OGC® GeoPackage Encoding Standard - This Engineering Report (ER) gives recommendations on serving IFC via WFS and discusses related issues. It was decided that the focus of this ER is to summarize issues and give recommendations for future work and discuss the nature of such work. In other words, this ER should be viewed as an initial set of discussion points on the topic of serving IFC via WFS. - - 16-115 - + 2024-02-06 + + + + + Jeff Yutzler + 12-128r19 + This OGC® Encoding Standard defines GeoPackages for exchange and GeoPackage SQLite Extensions for direct use of vector geospatial features and / or tile matrix sets of earth images and raster maps at various scales. Direct use means the ability to access and update data in a native storage format without intermediate format translations in an environment (e.g., through an API) that guarantees data model and data set integrity and identical access and update results in response to identical requests from different client applications. GeoPackages are interoperable across all enterprise and personal computing environments, and are particularly useful on mobile devices like cell phones and tablets in communications environments with limited connectivity and bandwidth. + + + - - Future City Pilot 1 - Recommendations on Serving IFC via WFS - Guy Schumann - 2017-10-20 + Testbed 11 Aviation - Architecture Engineering Report + 15-025r2 + + This OGC® document describes the architecture implemented in the OGC Testbed 11 Aviation thread. + + + 2015-08-19 + Johannes Echterhoff + + OGC® Testbed 11 Aviation - Architecture Engineering Report + 15-025r2 - - - OGC Web Services Architectural Profile for the NSG - - Shayne Urbanowski - 2007-08-13 - 07-009r3 - OGC Web Services Architectural Profile for the NSG - The purpose of this document is to generally describe how the various OGC specifications may be used to address the needs of a large enterprise system. It highlights the key elements of the OWS-4 effort as they relate to web service architecture implementation at NGA and in the NSG. The goal is that this document will enable organization that interface with the NSG to understand how to produce and consume data and services in an interoperable environment. + + + Ingo Simonis + + 06-028r3 + Sensor Alert Service - 07-009r3 + Sensor Alert Service + + 06-028r3 + + The Sensor Alert Service (SAS) can be compared with an event notification system. The sensor node is the object of interest. Each node has to advertise its publications at a SAS (advertise). + 2007-05-16 + + + 14-100r2 + CF-netCDF 3.0 encoding using GML Coverage Application Schema - + The OGC CF-netCDF data model supports multi-dimensional gridded data and multidimensional multi-point data, representing space and time-varying phenomena. In particular, this extension standard is limited to multi-point, and regular and warped grids. +This standard specifies the CF-netCDF data model encoding using the OGC GML 3.2.1 coverage application schema, as well as CF-netCDF data exchange format and protocol encoding. +This standard specifies: (a) the CF-netCDF GML encoding to be used by OGC standards; (b) the CF-netCDF data format exchanged using OGC standards; (c) the Internet protocol characteristics to effectively exchange CF-netCDF data. +As per the GML 3.3. standard, GML 3.3 imports the 3.2 schema. The canonical location of the 3.2 all components schema document for 3.3 is +http://schemas.opengis.net/gml/3.2.1/gml.xsd + + + + + 14-100r2 + OGC® CF-netCDF 3.0 encoding using GML Coverage Application Schema + 2015-11-18 + + Ben Domenico, Stefano Nativi - - + + GML 3.1.1 grid CRSs profile + Arliss Whiteside + 2006-07-18 + This document defines a profile of the Geography Markup Language (GML) version 3.1.1 for encoding definitions of grid coverage (including image) Coordinate Reference Systems (CRSs) plus related coordinate Transformations. This document also specifies some Universal Resource Names (URNs) for definitions in the ogc URN namespace, in addition to those specified in [OGC 05-010]. Additional specific URNs are defined for definitions of the datums, coordinate systems, and coordinate system axes which are often used in definitions of grid and image CRSs. + + GML 3.1.1 grid CRSs profile + 05-096r1 + 05-096r1 + + + + + - - 15-011r2 - - This document describes the work done in the OGC Testbest-11 to support multiple WFS-T instance interoperability by way of a transaction scenario involving the interaction between clients and multiple WFS-T servers as well as the interaction between the servers themselves, especially in the use case of enterprise-to-enterprise data synchronization. -The document presents an overview of the transaction scenario, the components used to implement the scenario in the OGC Testbed-11 demo and the new capabilities added to the WFS-T server to support the scenario. - - Panagiotis (Peter) A. Vretanos + + + + Volume 6: OGC CDB Rules for Encoding Data using OpenFlight + 16-009r4 + + + + This volume defines the OpenFlight implementation requirements for a CDB conformant data store. Please also see Volume 1 OGC CDB Core Standard: Model and Physical Structure for a general description of all of the industry standard formats specified by the CDB standard. Please read section 1.3.1 of that document for a general overview. + + 16-009r4 + 2018-12-19 + Carl Reed + Volume 6: OGC CDB Rules for Encoding Data using OpenFlight + + + 10-124r1 + OGC Identifiers - the case for http URIs + 10-124r1 + The OGC provides a large number of resources to support the construction of spatial +data infrastructures, including documents, specifications, schemas and concept +definitions. When deployed, the infrastructures require persistent reference to these +resources, enabled by persistent identifiers. This may be at various level of +granularity. + + + + + OGC Identifiers - the case for http URIs + + 2010-07-15 + + Simon Cox + + + + 15-107 + Jeremy Tandy, Linda van den Brink, Payam Barnaghi + 2017-09-28 + + This document advises on best practices related to the publication of spatial data on the Web; the use of Web technologies as they may be applied to location. The best practices presented here are intended for practitioners, including Web developers and geospatial experts, and are compiled based on evidence of real-world application. These best practices suggest a significant change of emphasis from traditional Spatial Data Infrastructures by adopting an approach based on general Web standards. As location is often the common factor across multiple datasets, spatial data is an especially useful addition to the Web of data. + - - Testbed-11 Multiple WFS-T Interoperability - 15-011r2 - 2016-01-28 - - OGC Testbed-11 Multiple WFS-T Interoperability - - - + Spatial Data on the Web Best Practices + 15-107 + Spatial Data on the Web Best Practices - - - 07-002r3 - Simon Cox - 07-002r3 - Observations and Measurements - Part 2 - Sampling Features - - + + Describes modelling requirements for spatial referencing by coordinates. + Topic 02 - Spatial Referencing by Coordinates + 04-046r3 + Roger Lott + Topic 2 - Spatial Referencing by Coordinates - The OpenGIS® Observations and Measurements Encoding Standard (O&M) defines an abstract model and an XML schema [www.w3.org/XML/Schema] encoding for observations and it provides support for common sampling strategies. O&M also provides a general framework for systems that deal in technical measurements in science and engineering. This is one of the OGC Sensor Web Enablement (SWE) [http://www.opengeospatial.org/ogc/markets-technologies/swe] suite of standards. + - 2007-12-26 - - Observations and Measurements - Part 2 - Sampling Features + + 04-046r3 + + 2004-02-11 + - - 06-057r1 - City Geography Markup Language - 2006-08-18 - CityGML is an open data model and XML-based format for the storage and exchange of virtual 3D city models. It is an application schema for the Geography Markup Language 3 (GML3), the extendible international standard for spatial data exchange issued by the Open Geospatial Consortium (OGC) and the ISO TC211. - Thomas Kolbe, Gerhard Groeger and Angela Czerwinski - - - + - 06-057r1 + 11-159 + The Open Geospatial Consortium and EarthCube + + - - City Geography Markup Language - - - - + EarthCube aims to create an integrated system to access, analyze and share information that is +used by the entire geosciences community. The Open Geospatial Consortium (OGC) is an +organization of which more than four hundred companies and agencies are members, whose +purpose is to create open source standards for sharing geospatial and observational information. +The authors of this paper are users of OGC standards in our work in hydrology, meteorology, +climatology, oceanography and in the solid earth sciences, in other words, in key disciplinary +fields that contribute to the Geosciences. Moreover, the OGC has an effective process for +engaging individuals from many countries in standards development and interoperability testing +that encourages them to set aside the roles they play in their home organizations and instead +focus just on what is needed to share a particular class of information across the globe. This +paper examines the hypothesis that an OGC-like process could be useful for broader sharing of +information in the geosciences. + 11-159 + + 2011-10-19 + + The Open Geospatial Consortium and EarthCube + David Maidment, Ben Domenico, Alastair Gemmell, Kerstin Lehnert, David Tarboton, Ilya Zaslavsky - - - Web Coverage Processing Service (WCPS) Abstract Test Suite - 08-069r2 - Web Coverage Processing Service (WCPS) Abstract Test Suite - - - - 2009-03-25 - Peter Baumann - - 08-069r2 + + + Documents of type Implementation Specification - Draft + Documents of type Implementation Specification - Draft - + + Documents of type Implementation Specification - Draft - - 10-184 - OGC Fusion Standards Study, Phase 2 Engineering Report + + 2019-02-15 - - + GeoPackage 1.2 Vector Tiles Extensions Engineering Report + 18-074 + Tiled feature data, colloquially referred to as 'vector tiles', can be used to optimize the delivery of vector data over the web. This data may subsequently be used to support visualization (particularly through maps) as well as limited analysis activities. One goal of the OGC Vector Tiles Pilot was to define candidate extensions to existing OGC standards as a way to advance the use of vector tiles technology as part of the OGC baseline. This Engineering Report (ER) describes a set of possible extensions to GeoPackage 1.2 that documents the mechanism to store and retrieve vector tiles in a GeoPackage. These extensions work together to enable a GeoPackage to act as a container format that can support visualization and analysis activities, even in a Denied, Degraded, Intermittent, or Limited Bandwidth (DDIL) environment. + +The GeoPackage Vector Tiles extensions define the rules and requirements for encoding vector tiles in a GeoPackage data store. There are five draft extensions: + +The Vector Tiles Extension provides vector tiles support through the GeoPackage tiles option. + +The Mapbox Vector Tiles Extension allows the content of a tile Binary Large OBject (BLOB) to be a Mapbox Vector Tile as per version 2.1 of the Mapbox Vector Tile (MVT) specification [1]. + +The GeoJSON Vector Tiles Extension allows the content of each tile BLOB to be a GeoJSON file. + +The OGC Web Services (OWS) Context Extension provides a way to store information describing a list of geospatial resources, including but not limited to maps, their layers, and the styles of those layers. + +The Vector Tiles Attributes Extension allows attribute information for each feature to be stored in relational tables for more convenient querying. + +To support vector tiles, a minimum of at least two extensions is required. The first extension enables vector tiles support. However, to be usable, an encoding format must be declared via either the second or third extension. The other extensions are purely optional. + +These extensions, like all GeoPackage extensions, are intended to be transparent and to not interfere with GeoPackage-compliant, but non-supporting, software packages. - George Percivall - This Engineering Report summarizes two phases of the Open Geospatial Consortium (OGC®) Fusion Standards study and of the fusion prototypes developed during the OWS-7 Testbed which occurred between the two study phases. Recommendations from the first phase of the study were implemented in OWS-7. Based upon the results of OWS-7, responses to two Requests for Information and a multi-day workshop, this report provides a cumulative set of recommendations for advancing fusion based on open standards. + + 18-074 - 2010-12-13 - 10-184 - OGC Fusion Standards Study, Phase 2 Engineering Report - + Jeff Yutzler + + + OGC Vector Tiles Pilot: GeoPackage 1.2 Vector Tiles Extensions Engineering Report - - - Comparing CityGML and IndoorGML based on a use case at Lotte World Mall - 16-012r1 - - Ki-Joune Li, Hyung-Gyu Ryu, Hak-Cheol Kim, Jun Hee Lee, Joo-Ho Lee - 2016-12-22 + + 2015-12-17 + + 15-074r1 + Spatial Data on the Web Use Cases & Requirements - This OGC Discussion Paper provides a comparison between the OGC CityGML and IndoorGML standards. The goals and approaches of these two standards are different and they can be used in a complementary way. This discussion paper aims to compare the strengths and weakness of the standards, and explain how to integrate the standards to make useful applications. These comparative experiments are based on a real site: a shopping mall at Lotte World Mall in Seoul, South Korea. - Comparing CityGML and IndoorGML based on a use case at Lotte World Mall - 16-012r1 - + 15-074r1 + + This document describes use cases that demand a combination of geospatial and non-geospatial data sources and techniques. It underpins the collaborative work of the Spatial Data on the Web Working Groups operated by both W3C and OGC. + Frans Knibbe, Alejandro Llaves + + Spatial Data on the Web Use Cases & Requirements - - 3f4259fb-9ac8-43cf-95e7-9e11bf5969d9 + + Demand for digital representations of built environments is accelerating and can only be satisfied through greater software interoperability and data integration. The objective of the Integrated Digital Built Environment (IDBE) joint working group is to address this challenge by bringing together experts from the Open Geospatial Consortium and buildingSMART to coordinate the development of the relevant data standards. This document is an output from IDBE in which we describe the state of three of the most prominent built environment standards – CityGML, IFC and LandInfra – and describe some of the problems that hinder their integration; finally, we propose actions points for overcoming these problems. + 2020-03-18 + + 19-091r1 + Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra + 19-091r1 + Built environment data standards and their integration: an analysis of IFC, CityGML and LandInfra + Thomas Gilbert, Carsten Rönsdorf, Jim Plume, Scott Simmons, Nick Nisbet, Hans-Christoph Gruler, Thom + + + + + - - 18-073r2 - OGC PipelineML Conceptual and Encoding Model Standard - OGC PipelineML Conceptual and Encoding Model Standard - The OGC PipelineML Conceptual and Encoding Model Standard defines concepts supporting the interoperable interchange of data pertaining to oil and gas pipeline systems. PipelineML supports the common exchange of oil and gas pipeline information. This initial release of the PipelineML Core addresses two critical business use cases that are specific to the pipeline industry: new construction surveys and pipeline rehabilitation. This standard defines the individual pipeline components with support for lightweight aggregation. Additional aggregation requirements such as right-of-way and land management will utilize the OGC LandInfra standards with utility extensions in the future. Future extensions to PipelineML Core will include (non-limitative): cathodic protection, facility and safety. PipelineML was advanced by an international team of contributors from the US, Canada, Belgium, Norway, Netherlands, UK, Germany, Australia, Brazil, and Korea. - -This standard assumes the reader has a basic understanding of oil and gas pipeline industry concepts. - John Tisdale - + + - - 18-073r2 - - 2019-08-08 + OGC® Event Service - Review and Current State + 11-088r1 + Johannes Echterhoff, Thomas Everding + 2011-11-23 + 11-088r1 + Event Service - Review and Current State + + + This Discussion Paper provides information on what has so far been called “Event Service” at OGC. +The presented work is supported by the European Commission through the ESS project (integrated project, contract number 217951) and the GENESIS project (integrated project, contract number 223996) . + - - + + + - - 17-083r4 - OGC Two Dimensional Tile Matrix Set and Tile Set Metadata - - Joan Masó, Jérôme Jacovella-St-Louis - - - OGC Two Dimensional Tile Matrix Set and Tile Set Metadata - 17-083r4 - - The OGC Two Dimensional Tile Matrix Set and Tile Set Metadata Standard defines the rules and requirements for a tile matrix set as a way to index space based on a set of regular grids defining a domain (tile matrix) for a limited list of scales in a Coordinate Reference System (CRS) as defined in OGC 18-005r5 Abstract Specification Topic 2: Referencing by Coordinates. This content was initially included in the OGC 07-057r7 OpenGIS Web Map Tile Service Implementation Standard (WMTS) and was separated out into the OGC 17-083r2 OGC Two Dimensional Tile Matrix Set Standard version 1.0, to support reusability in other data formats of services that need a tiling scheme. This document is a revision of the OGC 17-083r2 document and the general tile matrix set concept is inherited from it with small additions. In a tile matrix set, each tile matrix is divided into regular tiles. In a tile matrix set, a tile can be univocally identified by a tile column, a tile row, and a tile matrix identifier. The OGC Two Dimensional Tile Matrix Set and Tile Set Metadata Standard describes a data structure defining the properties of the tile matrix set in both Unified Modeling Language (UML) diagrams and in tabular form. This document also defines a new data structure, called tile set metadata, that can be used to describe a particular set of tiles following a tile matrix set. Extensible Markup Language (XML) and JavaScript Object Notation (JSON) encodings are described both for tile matrix sets and tile matrix set metadata. It includes tile matrix set limits, links to the tile matrix set, details of the original data represented by the tile set and a nice point of origin to start exploring the tile set. Finally, the document offers practical examples of tile matrix sets both for common global projections and for specific regions. - 2022-09-09 - - + + + + + + + Documents of type Request for Comment + Documents of type Request for Comment Documents of type Request for Comment - + + + + + + + + + + + + + + + + + + + + - - - - diff --git a/definitions/docs/entailed/docs.ttl b/definitions/docs/entailed/docs.ttl index 8caba257..6cc09446 100644 --- a/definitions/docs/entailed/docs.ttl +++ b/definitions/docs/entailed/docs.ttl @@ -737,6 +737,7 @@ , , , + , , , , @@ -18192,6 +18193,25 @@ This specification is a successor to the OGC’s Web Map Tile Service (WMTS) sta skos:notation "20-057"^^na:doc_no ; skos:prefLabel "OGC API - Tiles - Part 1: Core"@en . + a skos:Concept ; + dct:created "2024-08-09"^^ ; + dct:creator "Joan Masó, Jérôme Jacovella-St-Louis " ; + na:doctype doctype:is ; + na:status ; + rdfs:seeAlso ; + skos:altLabel "20-058"@en, + "OGC API - Maps - Part 1: Core"@en ; + skos:broader doctype:is ; + skos:definition """The OGC API — Maps — Part 1: Core Standard defines a Web API for requesting maps over the Web. A map is a portrayal of geographic information as a digital representation suitable for display on a rendering device (adapted from OGC 06-042/ISO 19128 OpenGIS® Web Map Server (WMS) Implementation Specification). Implementations of the OGC API — Maps Standard are designed for a client to easily:\r +\r +Request a visual representation of one or more geospatial data layers in different styles;\r +Select by area, time and resolution of interest;\r +Change parameters such as the background color and coordinate reference systems.\r +A server that implements OGC API — Maps provides information about what maps are offered. OGC API — Maps addresses use cases similar to those addressed by the OGC 06-042/ISO 19128 OpenGIS® Web Map Server (WMS) Implementation Specification Standard.""" ; + skos:inScheme ; + skos:notation "20-058"^^na:doc_no ; + skos:prefLabel "OGC API - Maps - Part 1: Core"@en . + a skos:Concept ; dct:created "2021-01-28"^^ ; dct:creator "Gobe Hobona" ; @@ -21437,6 +21457,7 @@ doctype:is skos:narrower , , , , + , , , , @@ -21864,16 +21885,16 @@ doctype:per skos:narrower , skos:prefLabel "OGC Documents" . [] a prov:Activity ; - prov:endedAtTime "2024-07-30T10:34:05.928276"^^xsd:dateTime ; - prov:startedAtTime "2024-07-30T10:34:04.883138"^^xsd:dateTime ; + prov:endedAtTime "2024-08-10T10:33:53.521511"^^xsd:dateTime ; + prov:startedAtTime "2024-08-10T10:33:52.467869"^^xsd:dateTime ; prov:used [ a prov:Entity ; dct:format "application/json" ; - dct:hasVersion "git:3852709b7dabb312dcd088bac852ed1baee222e3" ; + dct:hasVersion "git:c89beb527ab5c15420e81e8661f606c28f76194f" ; rdfs:seeAlso ] ; prov:wasAssociatedWith [ a prov:Agent, schema:SoftwareApplication ; rdfs:label "OGC-NA tools" ; dct:hasVersion "0.3.49" ; rdfs:seeAlso ] ; - prov:wasInformedBy [ dct:identifier "3f4259fb-9ac8-43cf-95e7-9e11bf5969d9" ] . + prov:wasInformedBy [ dct:identifier "5f5b05c3-a60e-424a-98dc-119698b7c563" ] .