relaton-ogc 0.1.0

checksums.yaml

@@ -0,0 +1,7 @@
+---
+SHA1:
+  metadata.gz: '080b4dc57871aeddaecc3a3638b35b881362c105'
+  data.tar.gz: 35477072663a80ad7e366e8dba5f186c02e79c36
+SHA512:
+  metadata.gz: 33e58ee68f5ebcb721461708d1d615e10732fc48436c47787fd34ad8c594d2f7fdb81dac132522d7d62d1d817eed55c9465b69d937abca94b8d9eee5c5055eac
+  data.tar.gz: b5245ba75b2f125c82e3635a67417a0bbdac9b82858bccbc913ce0561607738a35971295165f2b54fd0fec1e196e6bb10e1089e7a5a6cfe84f23b8140cc2a113

data/.gitignore

@@ -0,0 +1,13 @@
+/.bundle/
+/.yardoc
+/_yardoc/
+/coverage/
+/doc/
+/pkg/
+/spec/reports/
+/tmp/
+/.vscode/
+
+# rspec failure tracking
+.rspec_status
+.rubocop-https---raw-githubusercontent-com-riboseinc-oss-guides-master-ci-rubocop-yml

data/.rspec

@@ -0,0 +1,3 @@
+--format documentation
+--color
+--require spec_helper

data/.rubocop.yml

@@ -0,0 +1,10 @@
+# This project follows the Ribose OSS style guide.
+# https://github.com/riboseinc/oss-guides
+# All project-specific additions and overrides should be specified in this file.
+
+inherit_from:
+  - https://raw.githubusercontent.com/riboseinc/oss-guides/master/ci/rubocop.yml
+AllCops:
+  TargetRubyVersion: 2.3
+Rails:
+  Enabled: true

data/.travis.yml

@@ -0,0 +1,18 @@
+# Auto-generated !!! Do not edit it manually
+# use ci-master https://github.com/metanorma/metanorma-build-scripts
+language: ruby
+cache: bundler
+os:
+- linux
+- osx
+rvm:
+- 2.6
+- 2.5
+- 2.4
+- ruby-head
+before_install: 
+- gem install bundler -v "~> 2"
+- bundle update
+matrix:
+  allow_failures:
+    - rvm: ruby-head

data/Gemfile

@@ -0,0 +1,4 @@
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in relaton_ogc.gemspec
+gemspec

data/Gemfile.lock

@@ -0,0 +1,84 @@
+PATH
+  remote: .
+  specs:
+    relaton-ogc (0.1.0)
+      faraday
+      relaton-iso-bib (~> 0.3.0)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    addressable (2.7.0)
+      public_suffix (>= 2.0.2, < 5.0)
+    crack (0.4.3)
+      safe_yaml (~> 1.0.0)
+    debase (0.2.4)
+      debase-ruby_core_source (>= 0.10.2)
+    debase-ruby_core_source (0.10.5)
+    diff-lcs (1.3)
+    docile (1.3.2)
+    equivalent-xml (0.6.0)
+      nokogiri (>= 1.4.3)
+    faraday (0.15.4)
+      multipart-post (>= 1.2, < 3)
+    hashdiff (1.0.0)
+    isoics (0.1.7)
+    json (2.2.0)
+    mini_portile2 (2.4.0)
+    multipart-post (2.1.1)
+    nokogiri (1.10.4)
+      mini_portile2 (~> 2.4.0)
+    public_suffix (4.0.1)
+    rake (10.5.0)
+    relaton-bib (0.3.6)
+      addressable
+      nokogiri
+    relaton-iso-bib (0.3.5)
+      isoics (~> 0.1.6)
+      relaton-bib (~> 0.3.0)
+      ruby_deep_clone (~> 0.8.0)
+    rspec (3.8.0)
+      rspec-core (~> 3.8.0)
+      rspec-expectations (~> 3.8.0)
+      rspec-mocks (~> 3.8.0)
+    rspec-core (3.8.2)
+      rspec-support (~> 3.8.0)
+    rspec-expectations (3.8.4)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-mocks (3.8.1)
+      diff-lcs (>= 1.2.0, < 2.0)
+      rspec-support (~> 3.8.0)
+    rspec-support (3.8.2)
+    ruby-debug-ide (0.7.0)
+      rake (>= 0.8.1)
+    ruby_deep_clone (0.8.0)
+    safe_yaml (1.0.5)
+    simplecov (0.17.0)
+      docile (~> 1.1)
+      json (>= 1.8, < 3)
+      simplecov-html (~> 0.10.0)
+    simplecov-html (0.10.2)
+    vcr (5.0.0)
+    webmock (3.7.1)
+      addressable (>= 2.3.6)
+      crack (>= 0.3.2)
+      hashdiff (>= 0.4.0, < 2.0.0)
+
+PLATFORMS
+  ruby
+
+DEPENDENCIES
+  bundler (~> 2.0)
+  debase
+  equivalent-xml (~> 0.6)
+  rake (~> 10.0)
+  relaton-ogc!
+  rspec (~> 3.0)
+  ruby-debug-ide
+  simplecov
+  vcr
+  webmock
+
+BUNDLED WITH
+   2.0.1

data/LICENSE.txt

@@ -0,0 +1,21 @@
+The MIT License (MIT)
+
+Copyright (c) 2019 Andrei Kislichenko
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.adoc

@@ -0,0 +1,117 @@
+= RelatonOgc
+
+RelatonOgc is a Ruby gem that implements the https://github.com/metanorma/metanorma-model-iso#iso-bibliographic-item[IsoBibliographicItem model].
+
+You can use it to retrieve metadata of OGC Standards from https://raw.githubusercontent.com/opengeospatial/NamingAuthority/master/incubation/bibliography/bibliography.json, and access such metadata through the `IsoBibliographicItem` object.
+
+== Installation
+
+Add this line to your application's Gemfile:
+
+[source,ruby]
+----
+gem 'relaton_ogc'
+----
+
+And then execute:
+
+    $ bundle
+
+Or install it yourself as:
+
+    $ gem install relaton_ogc
+
+== Usage
+
+=== Search for a standard using keywords
+
+[source,ruby]
+----
+hits = RelatonOgc::OgcBibliography.search("OGC 19-025r1")
+=> [<RelatonOgc::Hit:0x007fcab6b9aab8 @text="OGC 19-025r1" @fetched="false" @fullIdentifier="" @title="">]
+
+tem = hits[0].fetch
+=> #<RelatonOgc::OgcBibliographicItem:0x007fcab3cb4758
+...
+----
+
+=== XML serialization
+[source,ruby]
+----
+item.to_xml
+=> "<bibitem id="19-025r1" type="standard">
+      <title type="title-main" format="text/plain" language="en" script="Latn">Development of Spatial Data Infrastructures for Marine Data Management</title>
+      <title type="main" format="text/plain" language="en" script="Latn">Development of Spatial Data Infrastructures for Marine Data Management</title>
+      <uri type="obp">https://portal.opengeospatial.org/files/?artifact_id=88037</uri>
+      <docidentifier type="OGC">19-025r1</docidentifier>
+      <date type="published">
+        <on>2019</on>
+      </date>
+      ...
+    </bibitem>"
+----
+With argument `bibdata: true` it ouputs XML wrapped by `bibdata` element and adds flavour `ext` element.
+[source,ruby]
+----
+item.to_xml bibdata: true
+=> "<bibdata type="standard">
+      <title type="title-main" format="text/plain" language="en" script="Latn">Development of Spatial Data Infrastructures for Marine Data Management</title>
+      <title type="main" format="text/plain" language="en" script="Latn">Development of Spatial Data Infrastructures for Marine Data Management</title>
+      <uri type="obp">https://portal.opengeospatial.org/files/?artifact_id=88037</uri>
+      <docidentifier type="OGC">19-025r1</docidentifier>
+      <date type="published\">
+        <on>2019</on>
+      </date>
+      ...
+      <ext>
+        <doctype>public-engineering-report</doctype>
+      </ext>
+    </bibdata>"
+----
+
+=== Get code, and year
+[source,ruby]
+----
+RelatonOgc::OgcBibliography.get "OGC 19-025r1", "2019", {}
+fetching OGC 19-025r1...
+=> #<RelatonOgc::OgcBibliographicItem:0x007fc322e9aba0
+...
+----
+
+=== Create bibliographic item from XML
+[source,ruby]
+----
+RelatonOgc::XMLParser.from_xml File.read('spec/fixtures/ogc_bib_item.xml')
+=> #<RelatonOgc::OgcBibliographicItem:0x007fc322ea82c8
+...
+----
+
+=== Create bibliographic item from YAML
+[source,ruby]
+----
+hash = YAML.load_file 'spec/fixtures/ogc_bib_item.yml'
+=> {"id"=>"19-025r1",
+...
+
+bib_hash = RelatonOgc::HashConverter.hash_to_bib hash
+=> {:id=>"19-025r1",
+...
+
+RelatonOgc::OgcBibliographicItem.new bib_hash
+=> #<RelatonOgc::OgcBibliographicItem:0x007fc322ef8548
+...
+----
+
+== Development
+
+After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake spec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.
+
+To install this gem onto your local machine, run `bundle exec rake install`. To release a new version, update the version number in `version.rb`, and then run `bundle exec rake release`, which will create a git tag for the version, push git commits and tags, and push the `.gem` file to [rubygems.org](https://rubygems.org).
+
+== Contributing
+
+Bug reports and pull requests are welcome on GitHub at https://github.com/[USERNAME]/relaton_ogc.
+
+== License
+
+The gem is available as open source under the terms of the [MIT License](https://opensource.org/licenses/MIT).

data/Rakefile

@@ -0,0 +1,6 @@
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/appveyor.yml

@@ -0,0 +1,37 @@
+# Auto-generated !!! Do not edit it manually
+# use ci-master https://github.com/metanorma/metanorma-build-scripts
+version: '{build}'
+
+cache:
+  - vendor/bundle
+
+environment:
+  matrix:
+    - RUBY_VERSION: 26
+    - RUBY_VERSION: 25
+    - RUBY_VERSION: 24
+    - RUBY_VERSION: _trunk
+
+matrix:
+  allow_failures:
+    - RUBY_VERSION: _trunk
+
+install:
+  - ps: . { iwr -useb https://raw.githubusercontent.com/metanorma/metanorma-build-scripts/master/appveyor.ps1 } | iex
+  - refreshenv
+
+build_script:
+  - set PATH=C:\Ruby%RUBY_VERSION%\bin;%PATH%
+  - set GIT_TERMINAL_PROMPT=0
+  - gem install bundler -v "~> 2"
+  - bundle config --local path vendor/bundle
+  - bundle update
+  - bundle install
+
+before_test:
+  - ruby -v
+  - gem -v
+  - bundle -v
+
+test_script:
+  - bundle exec rake

data/bin/console

@@ -0,0 +1,14 @@
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "relaton_ogc"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+require "irb"
+IRB.start(__FILE__)

data/bin/setup

@@ -0,0 +1,8 @@
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/lib/relaton_ogc.rb

@@ -0,0 +1,14 @@
+require "relaton_iso_bib"
+require "relaton_ogc/version"
+require "relaton_ogc/ogc_bibliographic_item"
+require "relaton_ogc/ogc_bibliography"
+require "relaton_ogc/hit_collection"
+require "relaton_ogc/scrapper"
+require "relaton_ogc/xml_parser"
+require "relaton_ogc/editorial_group"
+require "relaton_ogc/hash_converter"
+
+module RelatonOgc
+  class Error < StandardError; end
+  # Your code goes here...
+end

data/lib/relaton_ogc/data/bibliography.json

@@ -0,0 +1 @@
+{"1":{"title":"OGC PipelineML Conceptual and Encoding Model Standard","alternative":"OGC PipelineML Conceptual and Encoding Model Standard","URI":null,"identifier":"18-073r2","URL":"http://docs.opengeospatial.org/is/18-073r2/18-073r2.html","type":"IS","creator":"John Tisdale","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-08-08","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"2":{"title":"Development of Spatial Data Infrastructures for Marine Data Management","alternative":"Development of Spatial Data Infrastructures for Marine Data Management","URI":null,"identifier":"19-025r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=88037","type":"PER","creator":"Robert Thomas, Terry Idol","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-08-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"3":{"title":"Time Ontology in OWL","alternative":"Time Ontology in OWL","URI":null,"identifier":"16-071r2","URL":"https://www.w3.org/TR/2017/REC-owl-time-20171019/","type":"IS","creator":"Simon Cox, Chris Little","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-07-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"4":{"title":"Semantic Sensor Network Ontology","alternative":"Semantic Sensor Network Ontology","URI":null,"identifier":"16-079","URL":"https://www.w3.org/TR/2017/REC-vocab-ssn-20171019/","type":"IS","creator":"Armin Haller, Krzysztof Janowicz, Simon Cox, Danh Le Phuoc, Kerry Taylor, Maxime Lefrançois","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-07-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"5":{"title":"OGC GeoPackage Related Tables Extension","alternative":"GeoPackage Related Tables Extension","URI":null,"identifier":"18-000","URL":"http://docs.opengeospatial.org/is/18-000/18-000.html","type":"IS","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-05-08","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"6":{"title":"Vector Tiles Pilot Extension Engineering Report","alternative":"Vector Tiles Pilot Extension Engineering Report","URI":null,"identifier":"18-101","URL":"http://docs.opengeospatial.org/per/18-101.html","type":"PER","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-04-30","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"7":{"title":"OGC Testbed-14: Symbology Engineering Report","alternative":"Symbology Engineering Report","URI":null,"identifier":"18-029","URL":"https://docs.opengeospatial.org/per/18-029.html","type":"PER","creator":"Sara Saeedi","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-03-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"8":{"title":"OGC Testbed-14: Point Cloud Data Handling Engineering Report","alternative":"Point Cloud Data Handling Engineering Report","URI":null,"identifier":"18-048r1","URL":"http://docs.opengeospatial.org/per/18-048r1.html","type":"PER","creator":"Howard Butler","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-03-08","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"9":{"title":"OGC Testbed-14: CityGML and AR Engineering Report","alternative":" CityGML and AR Engineering Report","URI":null,"identifier":"18-025","URL":"http://docs.opengeospatial.org/per/18-025.html","type":"PER","creator":"Jérôme Jacovella-St-Louis","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-03-07","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"10":{"title":"OGC Testbed-14: Next Generation Web APIs - WFS 3.0 Engineering Report","alternative":"Next Generation Web APIs - WFS 3.0 Engineering Report","URI":null,"identifier":"18-045","URL":"https://docs.opengeospatial.org/per/18-045.html","type":"PER","creator":"Jeff Harrison, Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-03-07","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"11":{"title":"OGC Testbed-14: Secure Client Test Engineering Report","alternative":"Secure Client Test Engineering Report","URI":null,"identifier":"18-030","URL":"https://docs.opengeospatial.org/per/18-030.html","type":"PER","creator":"Sara Saeedi","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-03-06","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"12":{"title":"OGC Testbed-14 Next Generation APIs: Complex Feature Handling Engineering Report","alternative":"Next Generation APIs: Complex Feature Handling Engineering Report","URI":null,"identifier":"18-021","URL":"https://docs.opengeospatial.org/per/18-021.html","type":"PER","creator":"Clemens Portele","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-03-06","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"13":{"title":"OGC Testbed-14: MapML Engineering Report","alternative":"MapML Engineering Report","URI":null,"identifier":"18-023r1","URL":"https://docs.opengeospatial.org/per/18-023r1.html","type":"PER","creator":"Joan Masó","contributor":null,"description":"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.\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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-03-06","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"14":{"title":"OGC Testbed-14: Federated Clouds Engineering Report","alternative":"Federated Clouds Engineering Report","URI":null,"identifier":"18-090r1","URL":"http://docs.opengeospatial.org/per/18-090r1.html","type":"PER","creator":"Dr. Craig A. Lee","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-03-05","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"15":{"title":"OGC Testbed-14: Security Engineering Report","alternative":"Security Engineering Report","URI":null,"identifier":"18-026r1","URL":"https://docs.opengeospatial.org/per/18-026r1.html","type":"PER","creator":"Juan José Doval, Héctor Rodríguez","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-03-05","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"16":{"title":"OGC Vector Tiles Pilot: Summary Engineering Report","alternative":"OGC Vector Tiles Pilot: Summary Engineering Report","URI":null,"identifier":"18-086r1","URL":"https://docs.opengeospatial.org/per/18-086r1.html","type":"PER","creator":"Sam Meek","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"17":{"title":"OGC Vector Tiles Pilot: GeoPackage 1.2 Vector Tiles Extensions Engineering Report","alternative":"GeoPackage 1.2 Vector Tiles Extensions Engineering Report","URI":null,"identifier":"18-074","URL":"https://docs.opengeospatial.org/per/18-074.html","type":"PER","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"18":{"title":"OGC Testbed-14: WMS QoSE Engineering Report","alternative":"WMS QoSE Engineering Report","URI":null,"identifier":"18-028r2","URL":"https://docs.opengeospatial.org/per/18-028r2.html","type":"PER","creator":"Guy Schumann","contributor":null,"description":"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.opengeospatial.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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"19":{"title":"OGC White Paper on Land Administration","alternative":"White Paper on Land Administration","URI":null,"identifier":"18-008r1","URL":"http://docs.opengeospatial.org/wp/18-008r1/18-008r1.html","type":"WhitePaper","creator":"Christiaan Lemmen, Peter van Oosterom, Mohsen Kalantari, Eva-Maria Unger, Cornelis de Zeeuw","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"20":{"title":"OGC Environmental Linked Features Interoperability Experiment Engineering Report","alternative":"Environmental Linked Features Interoperability Experiment Engineering Report","URI":null,"identifier":"18-097","URL":"https://docs.opengeospatial.org/per/18-097.html","type":"PER","creator":"David Blodgett, Byron Cochrane, Rob Atkinson, Sylvain Grellet, Abdelfettah Feliachi, Alistair Ritchi","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-11","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"21":{"title":"OGC Testbed-14: BPMN Workflow Engineering Report","alternative":" BPMN Workflow Engineering Report","URI":null,"identifier":"18-085","URL":"https://docs.opengeospatial.org/per/18-085.html","type":"PER","creator":"Sam Meek","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-11","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"22":{"title":"OGC Testbed-14: SWIM Information Registry Engineering Report","alternative":"SWIM Information Registry Engineering Report","URI":null,"identifier":"18-022r1","URL":"https://docs.opengeospatial.org/per/18-022r1.html","type":"PER","creator":"Yann Le Franc","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-11","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"23":{"title":"OGC Vector Tiles Pilot: WMTS Vector Tiles Extension Engineering Report","alternative":"WMTS Vector Tiles Extension  Engineering Report","URI":null,"identifier":"18-083","URL":"https://docs.opengeospatial.org/per/18-083.html","type":"PER","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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'.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-11","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"24":{"title":"OGC Vector Tiles Pilot: Tiled Feature Data Conceptual Model Engineering Report","alternative":"Tiled Feature Data Conceptual Model Engineering Report","URI":null,"identifier":"18-076","URL":"https://docs.opengeospatial.org/per/18-076.html","type":"PER","creator":"Jens Ingensand, Kalimar Maia","contributor":null,"description":"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'.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-11","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"25":{"title":"OGC Vector Tiles Pilot: WFS 3.0 Vector Tiles Extension Engineering Report","alternative":"WFS 3.0 Vector Tiles Extension Engineering Report","URI":null,"identifier":"18-078","URL":"https://docs.opengeospatial.org/per/18-078.html","type":"PER","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-11","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"26":{"title":"OGC Testbed-14: ADES & EMS Results and Best Practices Engineering Report","alternative":"ADES & EMS Results and Best Practices Engineering Report","URI":null,"identifier":"18-050r1","URL":"https://docs.opengeospatial.org/per/18-050r1.html","type":"PER","creator":"Paulo Sacramento","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-08","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"27":{"title":"Topic 2: Referencing by coordinates","alternative":"Topic 2: Referencing by coordinates","URI":null,"identifier":"18-005r4","URL":"http://docs.opengeospatial.org/as/18-005r4/18-005r4.html","type":"AS","creator":"Roger Lott","contributor":null,"description":"This document is identical in normative content with the latest edition (2019) of ISO 19111, Geographic Information - Spatial referencing by coordinates [ISO 19111:2019].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"28":{"title":"OGC Testbed-14: Authorisation, Authentication, & Billing Engineering Report","alternative":"OGC Testbed-14: Authorisation, Authentication, & Billing Engineering Report","URI":null,"identifier":"18-057","URL":"http://docs.opengeospatial.org/per/18-057.html","type":"PER","creator":"Jérôme Gasperi","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-07","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"29":{"title":"OGC Testbed-14: Application Package Engineering Report","alternative":"Application Package Engineering Report","URI":null,"identifier":"18-049r1","URL":"http://docs.opengeospatial.org/per/18-049r1.html","type":"PER","creator":"Paulo Sacramento","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-07","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"30":{"title":"OGC Testbed-14: Swath Coverage Engineering Report","alternative":"Swath Coverage Engineering Report","URI":null,"identifier":"18-047r3","URL":"http://docs.opengeospatial.org/per/18-047r3.html","type":"PER","creator":"Eugene Genong Yu, Liping Di","contributor":null,"description":"This Engineering Report (ER) presents a summary, description and findings of the Swath Coverage task conducted by the OGC Testbed-14 initiative.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-07","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"31":{"title":"OGC Testbed-14: WPS-T Engineering Report","alternative":"WPS-T Engineering Report","URI":null,"identifier":"18-036r1","URL":"http://docs.opengeospatial.org/per/18-036r1.html","type":"PER","creator":"Benjamin Pross, Arnaud Cauchy","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-07","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"32":{"title":"OGC Testbed-14: Compliance Engineering Report","alternative":"Compliance Engineering Report","URI":null,"identifier":"18-034r3","URL":"http://docs.opengeospatial.org/per/18-034r3.html","type":"PER","creator":"Andrea Aime, Emanuele Tajariol, Simone Giannecchini","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-07","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"33":{"title":"OGC Testbed-14: Semantically Enabled Aviation Data Models Engineering Report","alternative":"Semantically Enabled Aviation Data Models Engineering Report","URI":null,"identifier":"18-035","URL":"http://docs.opengeospatial.org/per/18-035.html","type":"PER","creator":"Stephane Fellah","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-07","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"34":{"title":"OGC Testbed-14: Characterization of RDF Application Profiles for Simple Linked Data Application and Complex Analytic Applicat","alternative":"Characterization of RDF Application Profiles for Simple Linked Data Application and Complex Analytic Applications Engineering","URI":null,"identifier":"18-094r1","URL":"http://docs.opengeospatial.org/per/18-094r1.html","type":"PER","creator":"Stephane Fellah","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-04","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"35":{"title":"OGC Testbed-14: Application Schemas and JSON Technologies Engineering Report","alternative":"Application Schemas and JSON Technologies Engineering Report","URI":null,"identifier":"18-091r2","URL":"http://docs.opengeospatial.org/per/18-091r2.html","type":"PER","creator":"Johannes Echterhoff","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-04","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"36":{"title":"OGC Testbed-14: Machine Learning Engineering Report","alternative":"Machine Learning Engineering Report","URI":null,"identifier":"18-038r2","URL":"http://docs.opengeospatial.org/per/18-038r2.html","type":"PER","creator":"Tom Landry","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-04","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"37":{"title":"OGC Testbed-14: Application Schema-based Ontology Development Engineering Report","alternative":"Application Schema-based Ontology Development Engineering Report","URI":null,"identifier":"18-032r2","URL":"http://docs.opengeospatial.org/per/18-032r2.html","type":"PER","creator":"Johannes Echterhoff","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-02-04","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"38":{"title":"OGC 3D Tiles Specification 1.0","alternative":"3D Tiles Specification 1.0","URI":null,"identifier":"18-053r2","URL":"http://docs.opengeospatial.org/cs/18-053r2/18-053r2.html","type":"CS","creator":"Patrick Cozzi, Sean Lilley, Gabby Getz","contributor":null,"description":"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 any combination of tile formats organized into a spatial data structure.\r\n\r\n3D Tiles are declarative, extendable, and applicable to various types of 3D data. The following tile formats have been specified as part of this document:\r\n\r\nBatched 3D Model\r\nInstanced 3D Model\r\nPoint Cloud\r\nComposite\r\nThis document also describes 3D Tile Styles, a declarative styling specification which may be applied to tilesets.\r\n\r\nThe 3D Tiles specification for tilesets, associated tile formats, and the associated styling specification are open formats that are not dependent on any vendor-specific solution, technology, or products.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-01-31","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"39":{"title":"OGC Web Services Security","alternative":"Web Services Security","URI":null,"identifier":"17-007r1","URL":"http://docs.opengeospatial.org/is/17-007r1/17-007r1.html","type":"IS","creator":"Andreas Matheus","contributor":null,"description":"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 <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.\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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-01-28","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"40":{"title":"OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension with Corrigendum","alternative":"Coverage Implementation Schema - ReferenceableGridCoverage Extension with Corrigendum","URI":null,"identifier":"16-083r3","URL":"http://docs.opengeospatial.org/is/16-083r3/16-083r3.html","type":"ISC","creator":"Eric Hirschorn","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-01-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"41":{"title":"OGC CDB, Leveraging GeoPackage Discussion Paper","alternative":"CDB, Leveraging GeoPackage Discussion Paper","URI":null,"identifier":"18-0077r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=82553","type":"DP","creator":"Jay Freeman, Kevin Bentley, Ronald Moore, Samuel Chambers, Glen Quesenberry","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-01-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"42":{"title":"OGC Geospatial to the Edge Plugfest Engineering Report","alternative":"Geospatial to the Edge Plugfest Engineering Report","URI":null,"identifier":"18-084","URL":"https://docs.opengeospatial.org/per/18-084.html","type":"PER","creator":"Luis Bermudez","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-01-20","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"43":{"title":"OGC® Moving Features Encoding Part I: XML Core","alternative":"Moving Features Encoding Part I: XML Core","URI":null,"identifier":"18-075","URL":"http://docs.opengeospatial.org/is/18-075/18-075.html","type":"ISC","creator":"Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf","contributor":null,"description":"This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-01-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"44":{"title":"GeoDCAT-AP","alternative":"GeoDCAT-AP","URI":null,"identifier":"18-001r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=82475","type":"DP","creator":"Lieven Raes, Danny Vandenbroucke, Tomas Reznik","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-01-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"45":{"title":"OGC SensorThings API Part 2 – Tasking Core","alternative":"SensorThings API Part 2 – Tasking Core","URI":null,"identifier":"17-079r1","URL":"https://docs.opengeospatial.org/is/17-079r1/17-079r1.html","type":"IS","creator":"Steve Liang, Tania Khalafbeigi","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2019-01-08","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"46":{"title":"OGC Earth Observation Exploitation Platform Hackathon 2018 Engineering Report","alternative":"Earth Observation Exploitation Platform Hackathon 2018 Engineering Report","URI":null,"identifier":"18-046","URL":"http://docs.opengeospatial.org/per/18-046.html","type":"PER","creator":"Ingo Simonis","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-20","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"47":{"title":"OGC CDB Version 1.1 Release Notes","alternative":" CDB Version 1.1 Release Notes","URI":null,"identifier":"18-016r1","URL":"https://portal.opengeospatial.org/files/18-016r1","type":"Notes","creator":"Carl Reed","contributor":null,"description":"This document provides release notes for version 1.1 of the CDB Standard and related Best Practices.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"48":{"title":"Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values","alternative":"Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values","URI":null,"identifier":"16-003r3","URL":"https://portal.opengeospatial.org/files/16-003r3","type":"BP","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"49":{"title":"Volume 11: OGC CDB Core Standard Conceptual Model","alternative":"Volume 11: OGC CDB Core Standard Conceptual Model","URI":null,"identifier":"16-007r4","URL":"https://portal.opengeospatial.org/files/16-007r4","type":"IS","creator":"Sara Saeedi","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"50":{"title":"Volume 10: OGC CDB Implementation Guidance","alternative":"Volume 10: OGC CDB Implementation Guidance","URI":null,"identifier":"16-006r4","URL":"https://portal.opengeospatial.org/files/16-006r4","type":"BP","creator":"Carl Reed","contributor":null,"description":"This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"51":{"title":"Volume 8: CDB Spatial and Coordinate Reference Systems Guidance","alternative":"Volume 8: CDB Spatial and Coordinate Reference Systems Guidance","URI":null,"identifier":"16-011r4","URL":"https://portal.opengeospatial.org/files/16-011r4","type":"BP","creator":"Carl Reed","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"52":{"title":"Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2","alternative":"Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2","URI":null,"identifier":"16-010r4","URL":"https://portal.opengeospatial.org/files/16-010r4","type":"BP","creator":"Carl Reed","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"53":{"title":"Volume 6: OGC CDB Rules for Encoding Data using OpenFlight","alternative":"Volume 6: OGC CDB Rules for Encoding Data using OpenFlight","URI":null,"identifier":"16-009r4","URL":"https://portal.opengeospatial.org/files/16-009r4","type":"BP","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"54":{"title":"Volume 5: OGC CDB Radar Cross Section (RCS) Models","alternative":"Volume 5: OGC CDB Radar Cross Section (RCS) Models","URI":null,"identifier":"16-004r4","URL":"https://portal.opengeospatial.org/files/16-004r4","type":"BP","creator":"Carl Reed","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"55":{"title":"Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage","alternative":"Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage","URI":null,"identifier":"16-070r3","URL":"https://portal.opengeospatial.org/files/16-070r3","type":"BP","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"56":{"title":"Volume 3: OGC CDB Terms and Definitions","alternative":"Volume 3: OGC CDB Terms and Definitions","URI":null,"identifier":"15-112r3","URL":"https://portal.opengeospatial.org/files/15-112r3","type":"IS","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"57":{"title":"Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes","alternative":"Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes","URI":null,"identifier":"16-005r3","URL":"https://portal.opengeospatial.org/files/16-005r3","type":"BP","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"58":{"title":"Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure","alternative":"Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure","URI":null,"identifier":"15-113r5","URL":"https://portal.opengeospatial.org/files/15-113r5","type":"IS","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"59":{"title":"Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure","alternative":"Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure","URI":null,"identifier":"15-120r5","URL":"https://portal.opengeospatial.org/files/?artifact_id=82376","type":"BP","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"60":{"title":"OGC TimeseriesML 1.2 – XML Encoding of the Timeseries Profile of Observations and Measurements","alternative":"TimeseriesML 1.2 – XML Encoding of the Timeseries Profile of Observations and Measurements","URI":null,"identifier":"15-042r5","URL":"http://docs.opengeospatial.org/is/15-042r5/15-042r5.html","type":"IS","creator":"James Tomkins and Dominic Lowe","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-18","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"61":{"title":"Release Notes for OGC GeoPackage Encoding Standard v1.2.1","alternative":"Release Notes for OGC GeoPackage Encoding Standard v1.2.1","URI":null,"identifier":"18-024r1","URL":"https://portal.opengeospatial.org/files/18-024r1","type":"Notes","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"62":{"title":"OGC Development of Disaster Spatial Data Infrastructures for Disaster Resilience","alternative":"Development of Disaster Spatial Data Infrastructures for Disaster Resilience","URI":null,"identifier":"18-087r5","URL":"https://portal.opengeospatial.org/files/18-087r5","type":"PER","creator":"Terry Idol, Robert Thomas","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"63":{"title":"OGC Moving Features Encoding Extension: netCDF","alternative":"Moving Features Encoding Extension: netCDF","URI":null,"identifier":"16-114r3","URL":"http://docs.opengeospatial.org/bp/16-114r3/16-114r3.html","type":"BP","creator":"Martin Desruisseaux","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-18","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"64":{"title":"OGC SensorThings API Tasking Core Discussion Paper","alternative":"SensorThings API Tasking Core Discussion Paper","URI":null,"identifier":"18-056","URL":"https://portal.opengeospatial.org/files/?artifact_id=79179","type":"DP","creator":"Steve Liang, Tania Khalafbeigi, Kan Luo","contributor":null,"description":"This discussion paper offers descriptions and provides JSON examples of TaskingCapabilities and Tasks for the SensorThings Application Programming Interface (API).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-12-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"65":{"title":"OGC GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile","alternative":"GML Application Schema – Coverages : GRIB2 Coverage Encoding Profile","URI":null,"identifier":"16-060r2","URL":"http://docs.opengeospatial.org/is/16-060r2/16-060r2.html","type":"IS","creator":"Daniel Lee","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-11-27","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"66":{"title":"GeoPackage / OWS Context Harmonization Discussion Paper","alternative":"GeoPackage / OWS Context Harmonization Discussion Paper","URI":null,"identifier":"18-037r1","URL":"http://docs.opengeospatial.org/dp/18-037r1/18-037r1.html","type":"DP","creator":"Jeff Yutzler","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-10-29","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"67":{"title":"OGC Portrayal Concept Development Study","alternative":"Portrayal Concept Development Study","URI":null,"identifier":"17-094r1","URL":"http://docs.opengeospatial.org/per/17-094r1.html","type":"PER","creator":"Jeff Yutzler, Rob Cass","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-10-09","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"68":{"title":"Geospatial Standardization of Distributed Ledger Technologies","alternative":"Geospatial Standardization of Distributed Ledger Technologies","URI":null,"identifier":"18-041r1","URL":"http://docs.opengeospatial.org/dp/18-041r1/18-041r1.html","type":"DP","creator":"Gobe Hobona, Bart De Lathouwer","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-10-09","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"69":{"title":"OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile","alternative":"Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile","URI":null,"identifier":"10-140r2","URL":"http://docs.opengeospatial.org/is/10-140r2/10-140r2.html","type":"IS","creator":"Peter Baumann, Stephan Meissl, Jinsongdi Yu","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-10-04","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"70":{"title":"CDB Multi-Spectral Imagery Extension","alternative":"CDB Multi-Spectral Imagery Extension","URI":null,"identifier":"17-080r2","URL":"http://docs.opengeospatial.org/is/17-080r2/17-080r2.html","type":"IS","creator":"Ryan Franz","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-09-20","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"71":{"title":"OGC® GeoPackage Encoding Standard - with Corrigendum","alternative":"OGC® GeoPackage Encoding Standard - with Corrigendum","URI":null,"identifier":"12-128r15","URL":"https://portal.opengeospatial.org/files/?artifact_id=80678","type":"ISC","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-09-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"72":{"title":"OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard","alternative":"GML in JPEG 2000 (GMLJP2) Encoding Standard","URI":null,"identifier":"08-085r8","URL":"http://docs.opengeospatial.org/is/08-085r8/08-085r8.html","type":"IS","creator":"Lucio Colaiacomo, Joan Masó, Emmanuel Devys, Eric Hirschorn","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-08-27","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"73":{"title":"OGC GeoPackage Related Tables Extension Interoperability Experiment Engineering Report","alternative":"GeoPackage Related Tables Extension Interoperability Experiment Engineering Report","URI":null,"identifier":"17-093r1","URL":"http://docs.opengeospatial.org/per/17-093r1.html","type":"PER","creator":"Jeff Yutzler, Ashley Antonides","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-08-22","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"74":{"title":"OGC Web Coverage Service (WCS) 2.1 Interface Standard - Core","alternative":"WCS Core 2.1","URI":null,"identifier":"17-089r1","URL":"http://docs.opengeospatial.org/is/17-089r1/17-089r1.html","type":"IS","creator":"Peter Baumann","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-08-16","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"75":{"title":"The Role of Geospatial in Edge-Fog-Cloud Computing - An OGC White Paper","alternative":"The Role of Geospatial in Edge-Fog-Cloud Computing - An OGC White Paper","URI":null,"identifier":"18-004r1","URL":"http://docs.opengeospatial.org/wp/18-004r1/18-004r1.html","type":"WhitePaper","creator":"George Percivall","contributor":null,"description":"“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.” ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-07-31","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"76":{"title":"Incident Management Information Sharing (IMIS) Internet of Things (IoT) Architecture Engineering Report","alternative":"Incident Management Information Sharing (IMIS) Internet of Things (IoT) Architecture Engineering Report","URI":null,"identifier":"16-014r2","URL":"http://docs.opengeospatial.org/per/16-014r2.html","type":"PER","creator":"Greg Schumann, Josh Lieberman","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-04-26","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"77":{"title":"Incident Management Information Sharing Internet of Things Protocol Mapping Engineering Report","alternative":"Incident Management Information Sharing Internet of Things Protocol Mapping Engineering Report","URI":null,"identifier":"16-093r1","URL":"http://docs.opengeospatial.org/per/16-093r1.html","type":"PER","creator":"Steve Liang, Tania Khalafbeigi","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-04-26","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"78":{"title":"Incident Management Information Sharing Profile Recommendations for OGC Web Services Engineering Report","alternative":"Incident Management Information Sharing Profile Recommendations for OGC Web Services Engineering Report","URI":null,"identifier":"15-118r1","URL":"http://docs.opengeospatial.org/per/15-118r1.html","type":"PER","creator":"Simon Jirka, Christoph Stasch","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-04-23","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"79":{"title":"GeoAPI 3.0 Implementation Standard with corrigendum","alternative":"GeoAPI 3.0 Implementation Standard with corrigendum","URI":null,"identifier":"09-083r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=71648","type":"ISC","creator":"Adrian Custer","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-04-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"80":{"title":"OGC Moving Features Encoding Extension: netCDF","alternative":"Moving Features Encoding Extension: netCDF","URI":null,"identifier":"16-114r2","URL":"http://docs.opengeospatial.org/dp/16-114r2/16-114r2.html","type":"DP","creator":"Martin Desruisseaux","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-04-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"81":{"title":"OpenGIS Geography Markup Language (GML) Encoding Standard - with corrigendum","alternative":"Geography Markup Language (GML) Encoding Standard - with corrigendum","URI":null,"identifier":"07-036r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=74183&version=2","type":"ISC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-04-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"82":{"title":"OGC Geoscience Markup Language 4.1 (GeoSciML) - with Corrigendum","alternative":"Geoscience Markup Language 4.1 (GeoSciML) - with Corrigendum","URI":null,"identifier":"16-008r1","URL":"http://docs.opengeospatial.org/is/16-008/16-008r1.html","type":"IS","creator":"eoSciML Modeling Team ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-01-31","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"83":{"title":"OGC Best Practice for using Web Map Services (WMS) with Ensembles of Forecast Data","alternative":"Best Practice for using Web Map Services (WMS) with Ensembles of Forecast Data","URI":null,"identifier":"16-086r3","URL":"http://docs.opengeospatial.org/bp/16-086r3/16-086r3.html","type":"BP","creator":"Jürgen Seib, Marie-Françoise Voidrot-Martinez, Chris Little","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-04-05","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"84":{"title":"OGC® GeoPackage Encoding Standard: Tiled Gridded Elevation Data","alternative":"GeoPackage Encoding Standard: Tiled Gridded Elevation Data","URI":null,"identifier":"12-128r14","URL":"https://portal.opengeospatial.org/files/?artifact_id=74225","type":"CC","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"85":{"title":"OGC® GeoPackage Encoding Standard: WKT for Coordinate Reference Systems","alternative":"GeoPackage Encoding Standard: WKT for Coordinate Reference Systems","URI":null,"identifier":"12-128r14","URL":"https://portal.opengeospatial.org/files/?artifact_id=74225","type":"CC","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"86":{"title":"OGC® GeoPackage Encoding Standard: Schema","alternative":"GeoPackage Encoding Standard: Schema","URI":null,"identifier":"12-128r14","URL":"https://portal.opengeospatial.org/files/?artifact_id=74225","type":"CC","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"87":{"title":"OGC® GeoPackage Encoding Standard: Metadata","alternative":"GeoPackage Encoding Standard: Metadata","URI":null,"identifier":"12-128r14","URL":"https://portal.opengeospatial.org/files/?artifact_id=74225","type":"CC","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"88":{"title":"OGC® GeoPackage Encoding Standard: Tiles Encoding WebP","alternative":"GeoPackage Encoding Standard: Tiles Encoding WebP","URI":null,"identifier":"12-128r14","URL":"https://portal.opengeospatial.org/files/?artifact_id=74225","type":"CC","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"89":{"title":"OGC® GeoPackage Encoding Standard: RTree Spatial Indexes","alternative":"GeoPackage Encoding Standard: RTree Spatial Indexes","URI":null,"identifier":"12-128r14","URL":"https://portal.opengeospatial.org/files/?artifact_id=74225","type":"CC","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"90":{"title":"OGC® GeoPackage Encoding Standard: Non-Linear Geometry Types","alternative":"GeoPackage Encoding Standard: Non-Linear Geometry Types","URI":null,"identifier":"12-128r14","URL":"https://portal.opengeospatial.org/files/?artifact_id=74225","type":"CC","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"91":{"title":"OGC® GeoPackage Encoding Standard: Extension Mechanism","alternative":"GeoPackage Encoding Standard: Extension Mechanism","URI":null,"identifier":"12-128r14","URL":"https://portal.opengeospatial.org/files/?artifact_id=74225","type":"CC","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"92":{"title":"OGC® GeoPackage Encoding Standard: Attributes","alternative":"GeoPackage Encoding Standard: Attributes","URI":null,"identifier":"12-128r14","URL":"https://portal.opengeospatial.org/files/?artifact_id=74225","type":"CC","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"93":{"title":"OGC® GeoPackage Encoding Standard: Tiles","alternative":"GeoPackage Encoding Standard: Tiles","URI":null,"identifier":"12-128r14","URL":"https://portal.opengeospatial.org/files/?artifact_id=74225","type":"CC","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"94":{"title":"OGC® GeoPackage Encoding Standard: Features","alternative":"GeoPackage Encoding Standard: Features","URI":null,"identifier":"12-128r14","URL":"https://portal.opengeospatial.org/files/?artifact_id=74225","type":"CC","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"95":{"title":"OpenGIS® Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum","alternative":"Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile: Corrigendum","URI":null,"identifier":"07-045r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=77949","type":"ISC","creator":"Uwe Voges, Kristian Senkler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-03-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"96":{"title":"OGC GeoPackage Extension for Tiled Gridded Coverage Data","alternative":"GeoPackage Extension for Tiled Gridded Coverage Data","URI":null,"identifier":"17-066r1","URL":"http://docs.opengeospatial.org/is/17-066r1/17-066r1.html","type":"IS","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-03-07","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"97":{"title":"OGC Testbed-13: Quality Assessment Service Engineering Report","alternative":"Testbed-13: Quality Assessment Service Engineering Report","URI":null,"identifier":"17-025r2","URL":"http://docs.opengeospatial.org/per/17-025r2.html","type":"PER","creator":"Aleksandar Balaban","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-03-05","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"98":{"title":"OGC Testbed-13: Portrayal Engineering Report","alternative":"Testbed-13: Portrayal Engineering Report","URI":null,"identifier":"17-045","URL":"http://docs.opengeospatial.org/per/17-045.html","type":"PER","creator":"Stephane Fellah","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-03-05","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"99":{"title":"OGC Testbed-13: 3D Tiles and I3S Interoperability and Performance Engineering Report","alternative":"Testbed-13: 3D Tiles and I3S Interoperability and Performance Engineering Report","URI":null,"identifier":"17-046","URL":"http://docs.opengeospatial.org/per/17-046.html","type":"PER","creator":"Volker Coors","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-03-05","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"100":{"title":"Ensuring Quality of User Experience with OGC Web Mapping Services - Discussion Paper","alternative":"Ensuring Quality of User Experience with OGC Web Mapping Services - Discussion Paper","URI":null,"identifier":"17-049","URL":"https://portal.opengeospatial.org/files/?artifact_id=77148","type":"DP","creator":"C. Mitchell, M. Gordon, T. Kralidis","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-03-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"101":{"title":"LAS Specification 1.4 OGC Community Standard","alternative":"LAS Specification 1.4 OGC Community Standard","URI":null,"identifier":"17-030r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=74523","type":"CS","creator":"ASPRS","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-03-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"102":{"title":"OGC Testbed-13: Vector Tiles Engineering Report","alternative":"Testbed-13: Vector Tiles Engineering Report","URI":null,"identifier":"17-041","URL":"http://docs.opengeospatial.org/per/17-041.html","type":"PER","creator":"Stefano Cavazzi","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-02-22","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"103":{"title":"OGC Testbed-13: Disconnected Networks Engineering Report","alternative":"Testbed-13: Disconnected Networks Engineering Report","URI":null,"identifier":"17-026r1","URL":"http://docs.opengeospatial.org/per/17-026r1.html","type":"PER","creator":"Rob Cass","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-02-22","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"104":{"title":"OGC® WPS 2.0.2 Interface Standard: Corrigendum 2","alternative":"WPS 2.0.2 Interface Standard: Corrigendum 2","URI":null,"identifier":"14-065r2","URL":"http://docs.opengeospatial.org/is/14-065/14-065r2.html","type":"ISC","creator":"Matthias Mueller","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-02-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"105":{"title":"OGC® WPS 2.0.1 Interface Standard: Corrigendum 1","alternative":"WPS 2.0.1 Interface Standard: Corrigendum 1","URI":null,"identifier":"14-065r1","URL":"http://docs.opengeospatial.org/is/14-065/14-065r1.html","type":"ISC","creator":"Matthias Mueller","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"106":{"title":"Strengthening Disaster Risk Reduction Across the Americas Summit - Simulated Exercise Engineering Report","alternative":"Strengthening Disaster Risk Reduction Across the Americas Summit - Simulated Exercise Engineering Report","URI":null,"identifier":"17-088r1","URL":"http://docs.opengeospatial.org/per/17-088r1.html","type":"PER","creator":"Luis Bermudez","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-02-07","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"107":{"title":"OGC Testbed-13: EP Application Package Engineering Report","alternative":"Testbed-13: EP Application Package Engineering Report","URI":null,"identifier":"17-023","URL":"http://docs.opengeospatial.org/per/17-023.html","type":"PER","creator":"Pedro Gonçalves","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-30","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"108":{"title":"OGC Testbed-13: NAS Profiling Engineering Report","alternative":"Testbed-13: NAS Profiling Engineering Report","URI":null,"identifier":"17-020r1","URL":"http://docs.opengeospatial.org/per/17-020r1.html","type":"PER","creator":"Johannes Echterhoff, Clemens Portele","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-26","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"109":{"title":"OGC Testbed-13: GeoPackage Engineering Report","alternative":"Testbed-13: GeoPackage Engineering Report","URI":null,"identifier":"17-027","URL":"http://docs.opengeospatial.org/per/17-027.html","type":"PER","creator":"Robert Cass","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-26","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"110":{"title":"OGC Testbed-13: Aviation Abstract Quality Model Engineering Report","alternative":"Testbed-13: Aviation Abstract Quality Model Engineering Report","URI":null,"identifier":"17-032r2","URL":"http://docs.opengeospatial.org/per/17-032r2.html","type":"PER","creator":"Anneley McMillan, Sam Meek","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-26","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"111":{"title":"OGC Testbed-13: Data Quality Specification Engineering Report","alternative":"Testbed-13: Data Quality Specification Engineering Report","URI":null,"identifier":"17-018","URL":"http://docs.opengeospatial.org/per/17-018.html","type":"PER","creator":"Alaitz Zabala, Joan Maso","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-26","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"112":{"title":"OGC Testbed-13: Fit-for-Purpose Engineering Report","alternative":"Testbed-13: Fit-for-Purpose Engineering Report","URI":null,"identifier":"17-038","URL":"http://docs.opengeospatial.org/per/17-038.html","type":"PER","creator":"Jeff Harrison","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-18","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"113":{"title":"JSON Encoding Rules SWE Common / SensorML","alternative":"JSON Encoding Rules SWE Common / SensorML","URI":null,"identifier":"17-011r2","URL":"http://docs.opengeospatial.org/bp/17-011r2/17-011r2.html","type":"BP","creator":"Alex Robin","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-18","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"114":{"title":"Incident Management Information Sharing (IMIS) Internet of Things (IoT) Extension Engineering Report","alternative":"Incident Management Information Sharing (IMIS) Internet of Things (IoT) Extension Engineering Report","URI":null,"identifier":"16-092r2","URL":"http://docs.opengeospatial.org/per/16-092r2.html","type":"PER","creator":"Roger Brackin","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-18","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"115":{"title":"OGC Testbed-13: Concepts of Data and Standards for Mass Migration Engineering Report","alternative":"Concepts of Data and Standards for Mass Migration Engineering Report","URI":null,"identifier":"17-078","URL":"http://docs.opengeospatial.org/per/17-078.html","type":"PER","creator":"Jeff Harrison","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-17","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"116":{"title":"OGC Testbed-13: CDB Engineering Report","alternative":"Testbed-13: CDB Engineering Report","URI":null,"identifier":"17-042","URL":"http://docs.opengeospatial.org/per/17-042.html","type":"PER","creator":"Sara Saeedi","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-11","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"117":{"title":"OGC Testbed-13: NA001 Climate Data Accessibility for Adaptation Planning","alternative":"Testbed-13: NA001 Climate Data Accessibility for Adaptation Planning","URI":null,"identifier":"17-022","URL":"http://docs.opengeospatial.org/per/17-022.html","type":"PER","creator":"Guy Schumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-11","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"118":{"title":"OGC Testbed-13: Geospatial Taxonomies Engineering Report","alternative":"Testbed-13: Geospatial Taxonomies Engineering Report","URI":null,"identifier":"17-036","URL":"http://docs.opengeospatial.org/per/17-036.html","type":"PER","creator":"Charles Chen","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-11","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"119":{"title":"OGC Testbed-13: Application Deployment and Execution Service Engineering Report","alternative":"Testbed-13: Application Deployment and Execution Service Engineering Report","URI":null,"identifier":"17-024","URL":"http://docs.opengeospatial.org/per/17-024.html","type":"PER","creator":"Pedro Gonçalves","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-11","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"120":{"title":"OGC Testbed-13: Security Engineering Report","alternative":"Testbed-13: Security Engineering Report","URI":null,"identifier":"17-021","URL":"http://docs.opengeospatial.org/per/17-021.html","type":"PER","creator":"Andreas Matheus","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-11","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"121":{"title":"OGC Testbed-13: MapML Engineering Report","alternative":"Testbed-13: MapML Engineering Report","URI":null,"identifier":"17-019","URL":"http://docs.opengeospatial.org/per/17-019.html","type":"PER","creator":"Joan Maso","contributor":null,"description":"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.\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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-11","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"122":{"title":"OGC® WaterML 2: Part 3 - Surface Hydrology Features (HY_Features) - Conceptual Model","alternative":"WaterML 2: Part 3 - Surface Hydrology Features (HY_Features) - Conceptual Model","URI":null,"identifier":"14-111r6","URL":"http://docs.opengeospatial.org/is/14-111r6/14-111r6.html","type":"IS","creator":"David Blodgett, Irina Dornblut","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-08","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"123":{"title":"OGC Testbed-13: Workflows ER","alternative":"Testbed-13: Workflows ER","URI":null,"identifier":"17-029r1","URL":"http://docs.opengeospatial.org/per/17-029r1.html","type":"PER","creator":"Benjamin Pross, Christoph Stasch","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-08","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"124":{"title":"OGC Testbed-13: Executable Test Suites and Reference Implementations for NSG WMTS 1.0 and WFS 2.0 Profiles with Extension","alternative":"Testbed-13: Executable Test Suites and Reference Implementations for NSG WMTS 1.0 and WFS 2.0 Profiles with Extension","URI":null,"identifier":"17-043","URL":"http://docs.opengeospatial.org/per/17-043.html","type":"PER","creator":"Nuno Oliveira","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-08","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"125":{"title":"OGC Testbed-13: SWAP Engineering Report","alternative":"Testbed-13: SWAP Engineering Report","URI":null,"identifier":"17-037","URL":"http://docs.opengeospatial.org/per/17-037.html","type":"PER","creator":"Jeff Harrison","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-01","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"126":{"title":"OGC Testbed-13: DCAT/SRIM Engineering Report","alternative":"Testbed-13: DCAT/SRIM Engineering Report","URI":null,"identifier":"17-040","URL":"http://docs.opengeospatial.org/per/17-040.html","type":"PER","creator":"Stephen McCann, Roger Brackin, Gobe Hobona","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-08","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"127":{"title":"OGC Testbed-13: Cloud ER","alternative":"Testbed-13: Cloud ER","URI":null,"identifier":"17-035","URL":"http://docs.opengeospatial.org/per/17-035.html","type":"PER","creator":"Charles Chen","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-08","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"128":{"title":"OGC Testbed-13: Asynchronous Services ER","alternative":"Testbed-13:Asynchronous Services ER","URI":null,"identifier":"17-028","URL":"http://docs.opengeospatial.org/per/17-028.html","type":"PER","creator":"Benjamin Pross, Christoph Stasch","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2018-01-08","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"129":{"title":"Spatial Data on the Web Best Practices","alternative":"Spatial Data on the Web Best Practices","URI":null,"identifier":"15-107","URL":"https://www.w3.org/TR/sdw-bp/","type":"BP","creator":"Jeremy Tandy, Linda van den Brink, Payam Barnaghi","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-09-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"130":{"title":"Technical report from the DGIWG Portrayal Technical Panel testing of SLD (1.1.0) for OGC","alternative":"Technical report from the DGIWG Portrayal Technical Panel testing of SLD (1.1.0) for OGC","URI":null,"identifier":"17-059","URL":"http://docs.opengeospatial.org/dp/17-059/17-059.html","type":"DP","creator":"Lars Schylberg, Lubos Belka","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-10-30","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"131":{"title":"Future City Pilot 1 - Recommendations on Serving IFC via WFS","alternative":"Future City Pilot 1 - Recommendations on Serving IFC via WFS","URI":null,"identifier":"16-115","URL":"http://docs.opengeospatial.org/per/16-115.html","type":"PER","creator":"Guy Schumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-10-20","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"132":{"title":"Future City Pilot 1 - Automating Urban Planning Using Web Processing Service Engineering Report","alternative":"Future City Pilot 1 - Automating Urban Planning Using Web Processing Service Engineering Report","URI":null,"identifier":"16-099","URL":"http://docs.opengeospatial.org/per/16-099.html","type":"PER","creator":"Mohsen Kalantari","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-10-20","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"133":{"title":"Future City Pilot 1 Engineering Report","alternative":"Future City Pilot 1 Engineering Report","URI":null,"identifier":"16-098","URL":"http://docs.opengeospatial.org/per/16-098.html","type":"PER","creator":"Kanishk Chaturvedi, Thomas H. Kolbe","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-10-20","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"134":{"title":"Future City Pilot 1: Using IFC/CityGML in Urban Planning Engineering Report","alternative":"Future City Pilot 1: Using IFC/CityGML in Urban Planning Engineering Report","URI":null,"identifier":"16-097","URL":"http://docs.opengeospatial.org/per/16-097.html","type":"PER","creator":"Mohsen Kalantari","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-10-03","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"135":{"title":"Big Geospatial Data – an OGC White Paper","alternative":"Big Geospatial Data – an OGC White Paper","URI":null,"identifier":"16-131r2","URL":"http://docs.opengeospatial.org/wp/16-131r2/16-131r2.html","type":"WhitePaper","creator":"George Percivall","contributor":null,"description":"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/","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-09-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"136":{"title":"Semantic Sensor Network Ontology","alternative":"Semantic Sensor Network Ontology","URI":null,"identifier":"16-079","URL":"https://www.w3.org/TR/vocab-ssn/","type":"DP","creator":"Armin Haller, Krzysztof Janowicz, Simon Cox, Danh Le Phuoc, Kerry Taylor, Maxime Lefrançois","contributor":null,"description":"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/.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-09-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"137":{"title":"OGC InfraGML 1.0: Part 7 – LandInfra Land Division - Encoding Standard","alternative":"InfraGML 1.0: Part 7 – LandInfra Land Division - Encoding Standard","URI":null,"identifier":"16-107r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=75929","type":"IS","creator":"Paul Scarponcini  ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-09-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"138":{"title":"OGC Coverage Implementation Schema","alternative":"Coverage Implementation Schema","URI":null,"identifier":"09-146r6","URL":"http://docs.opengeospatial.org/is/09-146r6/09-146r6.html","type":"IS","creator":"Peter Baumann, Eric Hirschorn, Joan Masó","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-09-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"139":{"title":"OGC® 3D Portrayal Service 1.0","alternative":"3D Portrayal Service 1.0","URI":null,"identifier":"15-001r4","URL":"http://docs.opengeospatial.org/is/15-001r4/15-001r4.html","type":"IS","creator":"Benjamin Hagedorn, Simon Thum, Thorsten Reitz, Voker Coors, Ralf Gutbell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-09-13","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"140":{"title":"OGC GeoRSS Encoding Standard","alternative":"GeoRSS Encoding Standard","URI":null,"identifier":"17-002r1","URL":"http://docs.opengeospatial.org/cs/17-002r1/17-002r1.html","type":"CS","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"141":{"title":"OGC Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification","alternative":"Indexed 3d Scene Layer (I3S) and Scene Layer Package Format Specification","URI":null,"identifier":"17-014r5","URL":"http://docs.opengeospatial.org/cs/17-014r5/17-014r5.html","type":"CS","creator":"Carl Reed, Tamrat Belayneh","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-09-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"142":{"title":"OGC Underground Infrastructure Concept Study Engineering Report","alternative":"Underground Infrastructure Concept Study Engineering Report","URI":null,"identifier":"17-048","URL":"http://docs.opengeospatial.org/per/17-048.html","type":"PER","creator":"Josh Lieberman, Andy Ryan","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-31","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"143":{"title":"OGC® GeoPackage Encoding Standard","alternative":"GeoPackage Encoding Standard","URI":null,"identifier":"12-128r14","URL":"https://portal.opengeospatial.org/files/?artifact_id=74225","type":"IS","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"144":{"title":"OGC GeoPackage Elevation Extension Interoperability Experiment Engineering Report","alternative":"GeoPackage Elevation Extension Interoperability Experiment Engineering Report","URI":null,"identifier":"16-094r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=70051","type":"PER","creator":"Micah Brachman","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"145":{"title":"OGC InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard","alternative":"InfraGML 1.0: Part 0 – LandInfra Core - Encoding Standard","URI":null,"identifier":"16-100r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=75117","type":"IS","creator":"Paul Scarponcini","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"146":{"title":"OGC InfraGML 1.0: Part 1 – LandInfra Land Features - Encoding Standard","alternative":"InfraGML 1.0: Part 1 – LandInfra Land Features - Encoding Standard","URI":null,"identifier":"16-101r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=75118","type":"IS","creator":"Paul Scarponcini","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"147":{"title":"OGC InfraGML 1.0: Part 2 - LandInfra Facilities and Projects - Encoding Standard","alternative":"InfraGML 1.0: Part 2 - LandInfra Facilities and Projects - Encoding Standard","URI":null,"identifier":"16-102r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=75119","type":"IS","creator":"Paul Scarponcini","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"148":{"title":"OGC InfraGML 1.0: Part 3 - Alignments - Encoding Standard","alternative":"InfraGML 1.0: Part 3 - Alignments - Encoding Standard","URI":null,"identifier":"16-103r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=75120","type":"IS","creator":"Paul Scarponcini","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"149":{"title":"OGC InfraGML 1.0: Part 4 - LandInfra Roads - Encoding Standard","alternative":"InfraGML 1.0: Part 4 - LandInfra Roads - Encoding Standard","URI":null,"identifier":"16-104r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=75121","type":"IS","creator":"Paul Scarponcini","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"150":{"title":"OGC InfraGML 1.0: Part 5 - Railways - Encoding Standard","alternative":"InfraGML 1.0: Part 5 - Railways - Encoding Standard","URI":null,"identifier":"16-105r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=75122","type":"IS","creator":"Peter Axelsson, Lars Wikström","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"151":{"title":"OGC InfraGML 1.0: Part 6 – LandInfra Survey - Encoding Standard","alternative":"InfraGML 1.0: Part 6 – LandInfra Survey - Encoding Standard","URI":null,"identifier":"16-106r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=75123","type":"IS","creator":"Hans-Christoph Gruler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"152":{"title":"Topic 21: Discrete Global Grid Systems Abstract Specification","alternative":"Topic 21: Discrete Global Grid Systems Abstract Specification","URI":null,"identifier":"15-104r5","URL":"http://docs.opengeospatial.org/as/15-104r5/15-104r5.html","type":"AS","creator":"Matthew Purss","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-08-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"153":{"title":"Testbed-12 WPS ISO Data Quality Service Profile Engineering Report","alternative":"Testbed-12 WPS ISO Data Quality Service Profile Engineering Report","URI":null,"identifier":"16-041r1","URL":"http://docs.opengeospatial.org/per/16-041r1.html","type":"PER","creator":"Liping Di, Eugene G. Yu, Md Shahinoor Rahman, Ranjay Shrestha","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-30","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"154":{"title":"Testbed-12 Big Data Database Engineering Report","alternative":"Testbed-12 Big Data Database Engineering Report","URI":null,"identifier":"16-036r1","URL":"http://docs.opengeospatial.org/per/16-036r1.html","type":"PER","creator":"Christian Autermann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-30","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"155":{"title":"Testbed-12 Implementing Asynchronous Services Response Engineering Report","alternative":"Testbed-12 Implementing Asynchronous Services Response Engineering Report","URI":null,"identifier":"16-023r3","URL":"http://docs.opengeospatial.org/per/16-023r3.html","type":"PER","creator":"Benjamin Pross","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-30","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"156":{"title":"Testbed-12 Aviation SBVR Engineering Report","alternative":"Testbed-12 Aviation SBVR Engineering Report","URI":null,"identifier":"16-061","URL":"http://docs.opengeospatial.org/per/16-061.html","type":"PER","creator":"Timo Thomas, Aleksandar Balaban","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-30","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"157":{"title":"Testbed-12 WPS Conflation Service Profile Engineering Report","alternative":"Testbed-12 WPS Conflation Service Profile Engineering Report","URI":null,"identifier":"16-022","URL":"http://docs.opengeospatial.org/per/16-022.html","type":"PER","creator":"Benjamin Pross","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-30","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"158":{"title":"Testbed-12 Data Broker Engineering Report","alternative":"Testbed-12 Data Broker Engineering Report","URI":null,"identifier":"16-045r2","URL":"http://docs.opengeospatial.org/per/16-045r2.html","type":"PER","creator":"Daniel Balog, Robin Houtmeyers","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-30","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"159":{"title":"Testbed-12 Aviation Security Engineering Report","alternative":"Testbed-12 Aviation Security Engineering Report","URI":null,"identifier":"16-040r1","URL":"http://docs.opengeospatial.org/per/16-040r1.html","type":"PER","creator":"Aleksandar Balaban","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-30","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"160":{"title":"OGC Moving Features Encoding Extension - JSON","alternative":"OGC Moving Features Encoding Extension - JSON","URI":null,"identifier":"16-140r1","URL":"http://docs.opengeospatial.org/bp/16-140r1/16-140r1.html","type":"BP","creator":"Kyoung-Sook KIM, Hirotaka OGAWA","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-28","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"161":{"title":"Testbed-12 FIXM GML Engineering Report","alternative":"Testbed-12 FIXM GML Engineering Report","URI":null,"identifier":"16-028r1","URL":"http://docs.opengeospatial.org/per/16-028r1.html","type":"PER","creator":"Thomas Disney","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-19","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"162":{"title":"Testbed-12 Aviation Semantics Engineering Report","alternative":"Testbed-12 Aviation Semantics Engineering Report","URI":null,"identifier":"16-039r2","URL":"http://docs.opengeospatial.org/per/16-039r2.html","type":"PER","creator":"Aleksandar Balaban","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-19","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"163":{"title":"Testbed-12 Semantic Portrayal, Registry and Mediation Engineering Report","alternative":"Testbed-12 Semantic Portrayal, Registry and Mediation Engineering Report","URI":null,"identifier":"16-059","URL":"http://docs.opengeospatial.org/per/16-059.html","type":"PER","creator":"Stephane Fellah","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-16","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"164":{"title":"Testbed-12 WCS Profile Update Engineering Report","alternative":"Testbed-12 WCS Profile Update Engineering Report","URI":null,"identifier":"16-033r1","URL":"http://docs.opengeospatial.org/per/16-033r1.html","type":"PER","creator":"Ranjay Shrestha, Liping Di, Eugene G. Yu","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-04-28","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"165":{"title":"Testbed-12 Asynchronous Messaging for Aviation","alternative":"Testbed-12 Asynchronous Messaging for Aviation","URI":null,"identifier":"16-017","URL":"http://docs.opengeospatial.org/per/16-017.html","type":"PER","creator":"Matthes Rieke, Aleksandar Balaban","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-04-25","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"166":{"title":"Testbed-12 Vector Tiling Engineering Report","alternative":"Testbed-12 Vector Tiling Engineering Report","URI":null,"identifier":"16-068r4","URL":"http://docs.opengeospatial.org/per/16-068r4.html","type":"PER","creator":"Daniel Balog, Robin Houtmeyers","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-16","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"167":{"title":"Testbed-12 OWS Context: JSON, JSON-LD and HTML5 ER","alternative":"Testbed-12 OWS Context: JSON, JSON-LD and HTML5 ER","URI":null,"identifier":"16-053r1","URL":"http://docs.opengeospatial.org/per/16-053r1.html","type":"PER","creator":"Joan Masó","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-16","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"168":{"title":"Testbed-12 Multi-Tile Retrieval ER","alternative":"Testbed-12 Multi-Tile Retrieval ER","URI":null,"identifier":"16-049r1","URL":"http://docs.opengeospatial.org/per/16-049r1.html","type":"PER","creator":"Joan Masó","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-16","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"169":{"title":"Testbed-12 Aviation Architecture Engineering Report","alternative":"Testbed-12 Aviation Architecture Engineering Report","URI":null,"identifier":"16-018","URL":"http://docs.opengeospatial.org/per/16-018.html","type":"PER","creator":"Charles Chen","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"170":{"title":"Testbed-12 — Catalog Services for Aviation","alternative":"Testbed-12 — Catalog Services for Aviation","URI":null,"identifier":"16-024r2","URL":"http://docs.opengeospatial.org/per/16-024r2.html","type":"PER","creator":"R. Martell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"171":{"title":"OGC Coverage Implementation Schema - ReferenceableGridCoverage Extension","alternative":"Coverage Implementation Schema - ReferenceableGridCoverage Extension","URI":null,"identifier":"16-083r2","URL":"http://docs.opengeospatial.org/is/16-083r2/16-083r2.html","type":"IS","creator":"Eric Hirschorn","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"172":{"title":"Testbed-12 WMS/WMTS Enhanced Engineering Report","alternative":"Testbed-12 WMS/WMTS Enhanced Engineering Report","URI":null,"identifier":"16-042r1","URL":"http://docs.opengeospatial.org/per/16-042r1.html","type":"PER","creator":"Lingjun Kang, Liping Di, Eugene Yu","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-06-14","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"173":{"title":"Testbed-12 OWS Context / Capabilities Engineering Report","alternative":"Testbed-12 OWS Context / Capabilities Engineering Report","URI":null,"identifier":"16-052","URL":"http://docs.opengeospatial.org/per/16-052.html","type":"PER","creator":"Joan Masó","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-22","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"174":{"title":"Testbed-12 Vector Tiling Implementation Engineering Report","alternative":"Testbed-12 Vector Tiling Implementation Engineering Report","URI":null,"identifier":"16-067r4","URL":"http://docs.opengeospatial.org/per/16-067r4.html","type":"PER","creator":"Daniel Balog, Robin Houtmeyers","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"175":{"title":"Testbed-12 Compression Techniques Engineering Report","alternative":"Testbed-12 Compression Techniques Engineering Report","URI":null,"identifier":"16-055","URL":"http://docs.opengeospatial.org/per/16-055.html","type":"PER","creator":"Jeff Harrison","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"176":{"title":"Testbed-12 TopoJSON, GML Engineering Report","alternative":"Testbed-12 TopoJSON, GML Engineering Report","URI":null,"identifier":"16-056","URL":"http://docs.opengeospatial.org/per/16-056.html","type":"PER","creator":"Jeff Harrison","contributor":null,"description":"This OGC document evaluates TopoJSON as an encoding that may be delivered across a common, standard OGC service interface such as WFS.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"177":{"title":"Testbed-12 Testbed-12 GeoPackage Mobile Apps Integration Engineering Report","alternative":"Testbed-12 Testbed-12 GeoPackage Mobile Apps Integration Engineering Report","URI":null,"identifier":"16-030","URL":"http://docs.opengeospatial.org/per/16-030.html","type":"PER","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"178":{"title":"Testbed-12 Catalogue and SPARQL Engineering Report","alternative":"Testbed-12 Catalogue and SPARQL Engineering Report","URI":null,"identifier":"16-062","URL":"http://docs.opengeospatial.org/per/16-062.html","type":"PER","creator":"Gobe Hobona, Roger Brackin","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-15","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"179":{"title":"Testbed-12 REST Architecture Engineering Report","alternative":"Testbed-12 REST Architecture Engineering Report","URI":null,"identifier":"16-035","URL":"http://docs.opengeospatial.org/per/16-035.html","type":"PER","creator":"Christoph Stasch, Simon Jirka","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"180":{"title":"Testbed-12 Semantic Enablement Engineering Report","alternative":"Testbed-12 Semantic Enablement Engineering Report","URI":null,"identifier":"16-046r1","URL":"http://docs.opengeospatial.org/per/16-046r1.html","type":"PER","creator":"Martin Klopfer","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"181":{"title":"Testbed-12 Javascript-JSON-JSON-LD Engineering Report","alternative":"Testbed-12 Javascript-JSON-JSON-LD Engineering Report","URI":null,"identifier":"16-051","URL":"http://docs.opengeospatial.org/per/16-051.html","type":"PER","creator":"Joan Masó","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"182":{"title":"Testbed-12 Low Bandwidth & Generalization Engineering Report","alternative":"Testbed-12 Low Bandwidth & Generalization Engineering Report","URI":null,"identifier":"16-021r1","URL":"http://docs.opengeospatial.org/per/16-021r1.html","type":"PER","creator":"Benjamin Pross","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"183":{"title":"Testbed-12 General Feature Model Engineering Report","alternative":"Testbed-12 General Feature Model Engineering Report","URI":null,"identifier":"16-047r1","URL":"http://docs.opengeospatial.org/per/16-047r1.html","type":"PER","creator":"Martin Klopfer","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"184":{"title":"Testbed-12 Web Service Implementation Engineering Report","alternative":"Testbed-12 Web Service Implementation Engineering Report","URI":null,"identifier":"16-027","URL":"http://docs.opengeospatial.org/per/16-027.html","type":"PER","creator":"Johannes Echterhoff, Clemens Portele","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"185":{"title":"Testbed-12 GeoPackage Routing and Symbology Engineering Report","alternative":"Testbed-12 GeoPackage Routing and Symbology Engineering Report","URI":null,"identifier":"16-029r1","URL":"http://docs.opengeospatial.org/per/16-029r1.html","type":"PER","creator":"Jeff Yutzler","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"186":{"title":"Testbed-12 GeoPackage Change Request Evaluations","alternative":"Testbed-12 GeoPackage Change Request Evaluations","URI":null,"identifier":"16-031r1","URL":"http://docs.opengeospatial.org/per/16-031r1.html","type":"PER","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"187":{"title":"Testbed-12 NSG GeoPackage Profile Assessment Engineering Report","alternative":"Testbed-12 NSG GeoPackage Profile Assessment Engineering Report","URI":null,"identifier":"16-038","URL":"http://docs.opengeospatial.org/per/16-038.html","type":"PER","creator":"Chris Clark","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"188":{"title":"Testbed-12 GeoPackage US Topo Engineering Report","alternative":"Testbed-12 GeoPackage US Topo Engineering Report","URI":null,"identifier":"16-037","URL":"http://docs.opengeospatial.org/per/16-037.html","type":"PER","creator":"Robert Cass","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"189":{"title":"Testbed-12 Imagery Quality and Accuracy Engineering Report","alternative":"Testbed-12 Imagery Quality and Accuracy Engineering Report","URI":null,"identifier":"16-050","URL":"http://docs.opengeospatial.org/per/16-050.html","type":"PER","creator":"Joan Masó and Alaitz Zabala","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"190":{"title":"Testbed-12 PubSub / Catalog Engineering Report","alternative":"Testbed-12 PubSub / Catalog Engineering Report","URI":null,"identifier":"16-137r2","URL":"http://docs.opengeospatial.org/per/16-137r2.html","type":"PER","creator":"Lorenzo Bigagli","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-05-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"191":{"title":"OGC OWS Context GeoJSON Encoding Standard","alternative":"OWS Context GeoJSON Encoding Standard","URI":null,"identifier":"14-055r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=68826","type":"IS","creator":"Pedro Gonc&#807;alves, Roger Brackin","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-04-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"192":{"title":"Testbed-12 ShapeChange Engineering Report","alternative":"Testbed-12 ShapeChange Engineering Report","URI":null,"identifier":"16-020","URL":"http://docs.opengeospatial.org/per/16-020.html","type":"PER","creator":"Johannes Echterhoff","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-04-04","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"193":{"title":"Standardized Information Models to Optimize Exchange, Reusability and Comparability of Citizen Science Data (SWE4CS)","alternative":"Standardized Information Models to Optimize Exchange, Reusability and Comparability of Citizen Science Data (SWE4CS)","URI":null,"identifier":"16-129","URL":"https://portal.opengeospatial.org/files/?artifact_id=70328","type":"DP","creator":"Ingo Simonis, Rob Atkinson","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-03-31","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"194":{"title":"OGC Moving Features Access","alternative":"Moving Features Access","URI":null,"identifier":"16-120r3","URL":"http://docs.opengeospatial.org/is/16-120r3/16-120r3.html","type":"IS","creator":"Hideki Hayashi, Akinori Asahara, Kyoung-Sook Kim, Ryosuke Shibasaki, Nobuhiro Ishimaru","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-03-12","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"195":{"title":"Testbed-12 Arctic Spatial Data Infrastructure Engineering Report","alternative":"Testbed-12 Arctic Spatial Data Infrastructure Engineering Report","URI":null,"identifier":"16-063","URL":"http://docs.opengeospatial.org/per/16-063.html","type":"PER","creator":"Stefano Cavazzi, Roger Brackin","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-03-08","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"196":{"title":"Testbed-12 OWS Common Security Extension ER","alternative":"Testbed-12 OWS Common Security Extension ER","URI":null,"identifier":"16-048r1","URL":"http://docs.opengeospatial.org/per/16-048r1.html","type":"PER","creator":"Andreas Matheus","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-03-10","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"197":{"title":"Testbed-12 Web Feature Service Synchronization","alternative":"Testbed-12 Web Feature Service Synchronization","URI":null,"identifier":"16-044","URL":"http://docs.opengeospatial.org/per/16-044.html","type":"PER","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-03-09","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"198":{"title":"Testbed-12 Web Integration Service","alternative":"Testbed-12 Web Integration Service","URI":null,"identifier":"16-043","URL":"http://docs.opengeospatial.org/per/16-043.html","type":"PER","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-03-10","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"199":{"title":"Testbed-12 LiDAR Streaming Engineering Report","alternative":"Testbed-12 LiDAR Streaming Engineering Report","URI":null,"identifier":"16-034","URL":"http://docs.opengeospatial.org/per/16-034.html","type":"PER","creator":"Simon Jirka, Arne de Wall, Christoph Stasch","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-03-09","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"200":{"title":"OGC WaterML 2: Part 4 – GroundWaterML 2 (GWML2)","alternative":"WaterML 2: Part 4 – GroundWaterML 2 (GWML2)","URI":null,"identifier":"16-032r2","URL":"http://docs.opengeospatial.org/is/16-032r2/16-032r2.html","type":"IS","creator":"Boyan Brodaric","contributor":null,"description":"This standard describes a conceptual and logical model for the exchange of groundwater data, as well as a GML/XML encoding with examples.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-03-06","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"201":{"title":"OGC® Open Geospatial APIs - White Paper","alternative":"Open Geospatial APIs - White Paper","URI":null,"identifier":"16-019r4","URL":"http://docs.opengeospatial.org/wp/16-019r4/16-019r4.html","type":"WhitePaper","creator":"George Percivall","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"202":{"title":"Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values","alternative":"Volume 12: OGC CDB Navaids Attribution and Navaids Attribution Enumeration Values","URI":null,"identifier":"16-003r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=72724","type":"BP","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"203":{"title":"Volume 11: OGC CDB Core Standard Conceptual Model","alternative":"Volume 11: OGC CDB Core Standard Conceptual Model","URI":null,"identifier":"16-007r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=72723","type":"IS","creator":"Sara Saeedi","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"204":{"title":"Volume 10: OGC CDB Implementation Guidance","alternative":"Volume 10: OGC CDB Implementation Guidance","URI":null,"identifier":"16-006r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=72722","type":"BP","creator":"Carl Reed","contributor":null,"description":"This document provides detailed implementation guidance for developing and maintaining a CDB compliant data store. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"205":{"title":"Volume 8: CDB Spatial and Coordinate Reference Systems Guidance","alternative":"Volume 8: CDB Spatial and Coordinate Reference Systems Guidance","URI":null,"identifier":"16-011r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=72719","type":"BP","creator":"Carl Reed","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"206":{"title":"Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2","alternative":"Volume 7: OGC CDB Data Model Guidance Formerly Annex A Volume Part 2","URI":null,"identifier":"16-010r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=72718","type":"BP","creator":"Carl Reed","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"207":{"title":"Volume 6: OGC CDB Rules for Encoding Data using OpenFlight","alternative":"Volume 6: OGC CDB Rules for Encoding Data using OpenFlight","URI":null,"identifier":"16-009r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=72717","type":"BP","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"208":{"title":"Volume 5: OGC CDB Radar Cross Section (RCS) Models","alternative":"Volume 5: OGC CDB Radar Cross Section (RCS) Models","URI":null,"identifier":"16-004r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=72716","type":"BP","creator":"Carl Reed","contributor":null,"description":"(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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"209":{"title":"Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage","alternative":"Volume 4: OGC CDB Best Practice use of Shapefiles for Vector Data Storage","URI":null,"identifier":"16-070r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=72715","type":"BP","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"210":{"title":"Volume 3: OGC CDB Terms and Definitions","alternative":"Volume 3: OGC CDB Terms and Definitions","URI":null,"identifier":"15-112r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=72714","type":"IS","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"211":{"title":"Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes","alternative":"Volume 2: OGC CDB Core: Model and Physical Structure: Informative Annexes","URI":null,"identifier":"16-005r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=72713","type":"BP","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"212":{"title":"Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure","alternative":"Volume 1: OGC CDB Core Standard: Model and Physical Data Store Structure","URI":null,"identifier":"15-113r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=72712","type":"IS","creator":"Carl Reed","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"213":{"title":"Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure","alternative":"Volume 0: Primer for the OGC CDB Standard: Model and Physical Data Store Structure","URI":null,"identifier":"15-120r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=72711","type":"BP","creator":"Carl Reed","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"214":{"title":"OGC Geoscience Markup Language 4.1 (GeoSciML)","alternative":"Geoscience Markup Language 4.1","URI":null,"identifier":"16-008","URL":"http://docs.opengeospatial.org/is/16-008/16-008.html","type":"IS","creator":"GeoSciML Modeling Team","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2017-01-31","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"215":{"title":"OGC® GeoPackage Encoding Standard","alternative":"GeoPackage Encoding Standard","URI":null,"identifier":"12-128r12","URL":"https://portal.opengeospatial.org/files/?artifact_id=64506","type":"IS","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-08-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"216":{"title":"OGC® Geospatial User Feedback Standard: XML Encoding Extension","alternative":"Geospatial User Feedback Standard: XML Encoding Extension","URI":null,"identifier":"15-098r1","URL":"http://docs.opengeospatial.org/is/15-098r1/15-098r1.html","type":"IS","creator":"Joan Masó and Lucy Bastin ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-12-22","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"217":{"title":"OGC® Geospatial User Feedback Standard: Conceptual Model","alternative":"Geospatial User Feedback Standard: Conceptual Model","URI":null,"identifier":"15-097r1","URL":"http://docs.opengeospatial.org/is/15-097r1/15-097r1.html","type":"IS","creator":"Joan Masó and Lucy Bastin ","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-12-22","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"218":{"title":"OGC® Web Query Service ","alternative":"Web Query Service ","URI":null,"identifier":"16-121r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=72295","type":"DP","creator":"Peter Baumann","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-12-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"219":{"title":"Comparing CityGML and IndoorGML based on a use case at Lotte World Mall","alternative":"Comparing CityGML and IndoorGML based on a use case at Lotte World Mall","URI":null,"identifier":"16-012r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=68824","type":"DP","creator":"Ki-Joune Li, Hyung-Gyu Ryu, Hak-Cheol Kim, Jun Hee Lee, Joo-Ho Lee","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-12-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"220":{"title":"OGC® Land and Infrastructure Conceptual Model Standard (LandInfra)","alternative":"Land and Infrastructure Conceptual Model Standard (LandInfra)","URI":null,"identifier":"15-111r1","URL":"http://docs.opengeospatial.org/is/15-111r1/15-111r1.html","type":"IS","creator":"Paul Scarponcini","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-12-20","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"221":{"title":"OGC® OpenSearch Extension for Earth Observation","alternative":"OGC OpenSearch Extension for Earth Observation","URI":null,"identifier":"13-026r8","URL":"http://docs.opengeospatial.org/is/13-026r8/13-026r8.html","type":"IS","creator":"Pedro Gonçalves, Uwe Voges","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-12-16","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"222":{"title":"OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding (OpenSearch)","alternative":"Catalogue Services 3.0 Specification - HTTP Protocol Binding (OpenSearch)","URI":null,"identifier":"12-176r7","URL":"http://docs.opengeospatial.org/is/12-176r7/12-176r7.html","type":"CC","creator":"Doug Nebert, Uwe Voges, Panagiotis Vretanos, Lorenzo Bigagli, Bruce Westcott","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-06-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"223":{"title":"OGC Web Coverage Service Interface Standard – Transaction Extension","alternative":"Web Coverage Service Interface Standard – Transaction Extension","URI":null,"identifier":"13-057r1","URL":"http://docs.opengeospatial.org/is/13-057r1/13-057r1.html","type":"IS","creator":"Peter Bauman","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-11-17","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"224":{"title":"OGC® GML Application Schema - Coverages JPEG2000/JPIP Coverage Encoding Extension","alternative":"GML Application Schema - Coverages JPEG2000/JPIP Coverage Encoding Extension","URI":null,"identifier":"14-110r2","URL":"http://docs.opengeospatial.org/bp/14-110r2/14-110r2.html","type":"BP","creator":"Dimitri Sarafinof","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-11-02","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"225":{"title":"OGC Web Feature Service Implementation Specification with Corrigendum","alternative":"Web Feature Service Implementation Specification with Corrigendum","URI":null,"identifier":"04-094r1","URL":"http://docs.opengeospatial.org/is/04-094r1/04-094r1.html","type":"ISC","creator":"Panagiotis A. Vretanos","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-10-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"226":{"title":"Spatial Data on the Web Use Cases & Requirements","alternative":"Spatial Data on the Web Use Cases & Requirements","URI":null,"identifier":"15-074r2","URL":"http://docs.opengeospatial.org/dp/15-074r2/15-074r2.html","type":"DP","creator":"Frans Knibbe, Alejandro Llaves","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-10-25","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"227":{"title":"OpenGIS Web Feature Service (WFS) Implementation Specification (Basic)","alternative":"Web Feature Service (WFS) Implementation Specification (Basic)","URI":null,"identifier":"04-094","URL":"https://portal.opengeospatial.org/files/?artifact_id=8339","type":"CC","creator":"Peter Vretanos","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-05-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"228":{"title":"Topic 11 - Metadata","alternative":"Topic 11 - Metadata","URI":null,"identifier":"11-111r1","URL":"http://www.iso.org/iso/home/store/catalogue_ics/catalogue_detail_ics.htm?csnumber=53798","type":"AS","creator":"ISO","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-09-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"229":{"title":"OGC® GeoPackage Encoding Standard: Metadata","alternative":"GeoPackage Encoding Standard: Metadata","URI":null,"identifier":"12-128r12","URL":"https://portal.opengeospatial.org/files/?artifact_id=56357","type":"CC","creator":"Paul Daisey","contributor":null,"description":"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<br /><br />\r\nFor the online version of the standard and the developer resources, visit <a href=http://www.geopackage.org/>http://www.geopackage.org/</a>","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-04-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"230":{"title":"OGC® GeoPackage Encoding Standard: Tiling","alternative":"GeoPackage Encoding Standard: Tiling","URI":null,"identifier":"12-128r12","URL":"https://portal.opengeospatial.org/files/?artifact_id=56357","type":"CC","creator":"Paul Daisey","contributor":null,"description":"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<br /><br />\r\nFor the online version of the standard and the developer resources, visit <a href=http://www.geopackage.org/>http://www.geopackage.org/</a>","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-04-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"231":{"title":"TimeseriesML 1.0 – XML Encoding of the Timeseries Profile of Observations and Measurements","alternative":"TimeseriesML 1.0 – XML Encoding of the Timeseries Profile of Observations and Measurements","URI":null,"identifier":"15-042r3","URL":"http://docs.opengeospatial.org/is/15-042r3/15-042r3.html","type":"IS","creator":"James Tomkins and Dominic Lowe","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-09-09","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"232":{"title":"OGC® Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension","alternative":"Publish/Subscribe Interface Standard 1.0 SOAP Protocol Binding Extension","URI":null,"identifier":"13-133r1","URL":"http://docs.opengeospatial.org/is/13-133r1/13-133r1.html","type":"IS","creator":"Aaron Braeckel, Lorenzo Bigagli","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-08-22","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"233":{"title":"OGC® Publish/Subscribe Interface Standard 1.0 - Core","alternative":"Publish/Subscribe Interface Standard 1.0 - Core","URI":null,"identifier":"13-131r1","URL":"http://docs.opengeospatial.org/is/13-131r1/13-131r1.html","type":"IS","creator":"Aaron Braeckel , Lorenzo Bigagli , Johannes Echterhoff","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-08-22","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"234":{"title":"OGC® CityGML Quality Interoperability Experiment","alternative":"CityGML Quality Interoperability Experiment","URI":null,"identifier":"16-064r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=68821","type":"PER","creator":"Detlev Wagner, Hugo Ledoux","contributor":null,"description":"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&#1048576; Definition of data quality;\r\n&#1048576; Data quality requirements and their specification;\r\n&#1048576; Quality checking process of CityGML data; and\r\n&#1048576; 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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-08-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"235":{"title":"OGC Benefits of Indoor Location -  Use Case Survey of Lessons Learned and Expectations ","alternative":"OGC Benefits of Indoor Location -  Use Case Survey of Lessons Learned and Expectations ","URI":null,"identifier":"16-084","URL":"https://portal.opengeospatial.org/files/?artifact_id=68604","type":"DP","creator":"Giuseppe Conti, Fabio Malabocchia,  Ki-Joune Li, George Percivall, Kirk Burroughs, Stuart Strickland","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-08-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"236":{"title":"OGC Soil Data Interoperability Experiment","alternative":"Soil Data Interoperability Experiment","URI":null,"identifier":"16-088r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=69896","type":"PER","creator":"Alistair Ritchie","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-07-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"237":{"title":"OGC SensorThings API Create-Update-Delete","alternative":"SensorThings API Create-Update-Delete","URI":null,"identifier":"15-078r6","URL":"http://docs.opengeospatial.org/is/15-078r6/15-078r6.html","type":"CC","creator":"Steve Liang, Chih-Yuan Huang, Tania Khalafbeigi","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-07-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"238":{"title":"OGC SensorThings API Filtering Extension","alternative":"SensorThings API Filtering Extension","URI":null,"identifier":"15-078r6","URL":"http://docs.opengeospatial.org/is/15-078r6/15-078r6.html","type":"CC","creator":"Steve Liang, Chih-Yuan Huang, Tania Khalafbeigi","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-07-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"239":{"title":"OGC SensorThings API Sensing Core","alternative":"SensorThings API Sensing Core","URI":null,"identifier":"15-078r6","URL":"http://docs.opengeospatial.org/is/15-078r6/15-078r6.html","type":"CC","creator":"Steve Liang, Chih-Yuan Huang, Tania Khalafbeigi","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-07-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"240":{"title":"OGC SensorThings API Part 1: Sensing","alternative":"SensorThings API Part 1: Sensing","URI":null,"identifier":"15-078r6","URL":"http://docs.opengeospatial.org/is/15-078r6/15-078r6.html","type":"IS","creator":"Steve Liang, Chih-Yuan Huang, Tania Khalafbeigi","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-07-26","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"241":{"title":"OGC® Catalogue Services Specification - HTTP protocol binding - Abstract Test Suite","alternative":"Catalogue Services Specification - HTTP protocol binding - Abstract Test Suite","URI":null,"identifier":"14-014r3","URL":"http://docs.opengeospatial.org/is/14-014r3/14-014r3.html","type":"TS","creator":"Lorenzo Bigagli, Doug Nebert, Uwe Voges, Panagiotis Vretanos, Bruce Westcott","contributor":null,"description":"See OGC 12-176r7 -- OGC® Catalogue Services Specification - HTTP Protocol Binding.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-06-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"242":{"title":"OGC® Catalogue Services 3.0 Specification - HTTP Protocol Binding","alternative":"Catalogue Services 3.0 Specification - HTTP Protocol Binding","URI":null,"identifier":"12-176r7","URL":"http://docs.opengeospatial.org/is/12-176r7/12-176r7.html","type":"IS","creator":"Doug Nebert, Uwe Voges, Panagiotis Vretanos, Lorenzo Bigagli, Bruce Westcott","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-06-10","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"243":{"title":"OGC® Catalogue Services 3.0 - General Model","alternative":"Catalogue Services 3.0 - General Model","URI":null,"identifier":"12-168r6","URL":"http://docs.opengeospatial.org/is/12-168r6/12-168r6.html","type":"IS","creator":"Douglas Nebert, Uwe Voges, Lorenzo Bigagli","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-06-10","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"244":{"title":"OGC® Earth Observation Metadata profile of Observations & Measurements","alternative":"Earth Observation Metadata profile of Observations & Measurements","URI":null,"identifier":"10-157r4","URL":"http://docs.opengeospatial.org/is/10-157r4/10-157r4.html","type":"IS","creator":"Jerome Gasperi, Frédéric Houbie, Andrew Woolf, Steven Smolders ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-06-09","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"245":{"title":"Timeseries Profile of Observations and Measurements ","alternative":"Timeseries Profile of Observations and Measurements ","URI":null,"identifier":"15-043r3","URL":"http://docs.opengeospatial.org/is/15-043r3/15-043r3.html","type":"IS","creator":"James Tomkins , Dominic Lowe ","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-09-09","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"246":{"title":"OGC® Groundwater Interoperability Experiment FINAL REPORT","alternative":"Groundwater Interoperability Experiment FINAL REPORT","URI":null,"identifier":"10-194r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=43545","type":"PER","creator":"Boyan Brodaric, Nate Booth","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-03-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"247":{"title":"OGC GroundWaterML 2 – GW2IE FINAL REPORT","alternative":"GroundWaterML 2 – GW2IE FINAL REPORT","URI":null,"identifier":"15-082","URL":"https://portal.opengeospatial.org/files/?artifact_id=64688","type":"PER","creator":"Boyan Brodaric","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-04-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"248":{"title":"AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper","alternative":"AHA-ML (Active and Healthy Ageing Mark-up Language) an O&M profile - Discussion Paper","URI":null,"identifier":"15-116","URL":"https://portal.opengeospatial.org/files/?artifact_id=68040","type":"DP","creator":"Giuseppe Conti, Fabio Roncato","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-04-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"249":{"title":"Implications for an OGC GeoPackage  Symbology Encoding Standard","alternative":"Implications for an OGC GeoPackage  Symbology Encoding Standard","URI":null,"identifier":"15-122r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=66606","type":"DP","creator":"Randolph Gladish","contributor":null,"description":"The GeoPackage Standards Working Group (SWG) presents a discussion of symbology encapsulation for conveying presentation information for vector features contained within in a GeoPackage. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-04-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"250":{"title":"OGC GML in JPEG 2000 (GMLJP2) Encoding StandardPart 1: Core","alternative":"GML in JPEG 2000 (GMLJP2) Encoding StandardPart 1: Core","URI":null,"identifier":"08-085r5","URL":"http://docs.opengeospatial.org/is/08-085r5/08-085r5.html","type":"IS","creator":"Lucio Colaiacomo, Joan Masó, Emmanuel Devys ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-04-07","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"251":{"title":"Use of Geography Markup Language (GML) for Aviation Data","alternative":"Use of Geography Markup Language (GML) for Aviation Data","URI":null,"identifier":"12-028r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=62061","type":"DP","creator":"OGC Aviation Domain Working Group","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-03-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"252":{"title":"The Specification Model - Standard for Modular specifications","alternative":"The Specification Model - Standard for Modular specifications","URI":null,"identifier":"08-131r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=34762&version=2","type":"POL","creator":"Policy SWG","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-10-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"253":{"title":"OGC Identifiers - the case for http URIs","alternative":"OGC Identifiers - the case for http URIs","URI":null,"identifier":"10-124r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=39467","type":"WhitePaper","creator":"Simon Cox","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-07-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"254":{"title":"OGC Compliance Testing White Paper","alternative":"OGC Compliance Testing White Paper","URI":null,"identifier":"OGC 10-128","URL":"https://portal.opengeospatial.org/files/?artifact_id=41359","type":"WhitePaper","creator":"Luis Bermudez","contributor":null,"description":"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 ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-10-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"255":{"title":"OGC Standards and Cloud Computing","alternative":"OGC Standards and Cloud Computing","URI":null,"identifier":"OGC 11-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=43743","type":"WhitePaper","creator":"Lance McKee, Carl Reed, Steven Ramage","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-04-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"256":{"title":"Open Source and Open Standards","alternative":"Open Source and Open Standards","URI":null,"identifier":"OGC 11-110","URL":"https://portal.opengeospatial.org/files/?artifact_id=45126","type":"WhitePaper","creator":"Arnulf Christl and Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-08-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"257":{"title":"Geospatial Business Intelligence (GeoBI)","alternative":"Geospatial Business Intelligence (GeoBI)","URI":null,"identifier":"OGC 09-044r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=49321","type":"WhitePaper","creator":"George Percivall, Raj Singh","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-07-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"258":{"title":"Architecture of an Access Management Federation for Spatial Data and Services in Germany","alternative":"Architecture of an Access Management Federation for Spatial Data and Services in Germany","URI":null,"identifier":"OGC 12-026","URL":"https://portal.opengeospatial.org/files/?artifact_id=47848","type":"WhitePaper","creator":"Andreas Matheus","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-04-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"259":{"title":"OGC Sensor Web Enablement: Overview and High Level Architecture","alternative":"OGC Sensor Web Enablement: Overview and High Level Architecture","URI":null,"identifier":"OGC 07-165r1","URL":"http://docs.opengeospatial.org/wp/07-165r1/","type":"WhitePaper","creator":"Mike Botts, George Percivall, Carl Reed, John Davidson","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-04-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"260":{"title":"The Open Geospatial Consortium and EarthCube","alternative":"The Open Geospatial Consortium and EarthCube","URI":null,"identifier":"OGC 11-159","URL":"https://portal.opengeospatial.org/files/?artifact_id=46471&version=1","type":"WhitePaper","creator":"David Maidment, Ben Domenico, Alastair Gemmell, Kerstin Lehnert, David Tarboton, Ilya Zaslavsky","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-10-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"261":{"title":"OGC Smart Cities Spatial Information Framework","alternative":"OGC Smart Cities Spatial Information Framework","URI":null,"identifier":"14-115","URL":"https://portal.opengeospatial.org/files/?artifact_id=61188","type":"WhitePaper","creator":"George Percivall","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-01-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"262":{"title":"OGC Information Technology Standards for Sustainable Development","alternative":"OGC Information Technology Standards for Sustainable Development","URI":null,"identifier":"14-095","URL":"https://portal.opengeospatial.org/files/?artifact_id=60920","type":"WhitePaper","creator":"Lance McKee","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-01-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"263":{"title":"OGC Compliance Overview - Guide for Software Acquisition","alternative":"OGC Compliance Overview - Guide for Software Acquisition","URI":null,"identifier":"15-002r5","URL":"http://docs.opengeospatial.org/wp/15-002r5/15-002r5.html","type":"WhitePaper","creator":"Luis Bermudez","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-04-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"264":{"title":"OGC WaterML2.0: part 2 - Ratings, Gaugings and Sections","alternative":"WaterML2.0: part 2 - Ratings, Gaugings and Sections","URI":null,"identifier":"15-018r2","URL":"http://docs.opengeospatial.org/is/15-018r2/15-018r2.html","type":"IS","creator":"Peter Taylor","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-02-03","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"265":{"title":"OGC® Testbed-11 SOAP Interface Engineering Report: Comparison on the Usage of SOAP Across OGC Web service interfaces","alternative":"Testbed-11 SOAP Interface Engineering Report: Comparison on the Usage of SOAP Across OGC Web service interfaces","URI":null,"identifier":"15-077r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=64406","type":"PER","creator":"Ingo Simonis","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-02-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"266":{"title":"DGIWG - Web Feature Service 2.0 Profile","alternative":"DGIWG - Web Feature Service 2.0 Profile","URI":null,"identifier":"15-005r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=66933","type":"BP","creator":"Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-02-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"267":{"title":"DGIWG - Web Map Service 1.3 Profile - Revision","alternative":"DGIWG - Web Map Service 1.3 Profile - Revision","URI":null,"identifier":"09-102r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=66915","type":"BP","creator":"Stefan Strobel, Dimitri Sarafinof, David Wesloh, Paul Lacey","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"268":{"title":"OGC Testbed-11 Multiple WFS-T Interoperability","alternative":"Testbed-11 Multiple WFS-T Interoperability","URI":null,"identifier":"15-011r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=66906","type":"PER","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"269":{"title":"OGC® Testbed-11 WFS-T Information Exchange Architecture","alternative":"Testbed-11 WFS-T Information Exchange Architecture","URI":null,"identifier":"15-010r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=66905","type":"PER","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"270":{"title":"Testbed 11 Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Round Trip Engineering Report","alternative":"Testbed 11 Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Round Trip Engineering Report","URI":null,"identifier":"15-030r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=65451","type":"PER","creator":"Scott Serich","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"271":{"title":"Testbed-11 OGC IP Engineering Report Geo4NIEM Architecture Design and Implementation Guidance and Fact Sheet ","alternative":"Testbed-11 OGC IP Engineering Report Geo4NIEM Architecture Design and Implementation Guidance and Fact Sheet ","URI":null,"identifier":"15-051r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=65419","type":"PER","creator":"Jeff Harrison","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"272":{"title":"OGC Testbed-11 Test and Demonstration Results for NIEM using IC Data Encoding Specifications Engineering Report","alternative":"Testbed-11 Test and Demonstration Results for NIEM using IC Data Encoding Specifications Engineering Report","URI":null,"identifier":"15-050r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=65421","type":"PER","creator":"Jeff Harrison","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"273":{"title":"OGC Testbed-11 NIEM & IC Data Encoding Specification Assessment and Recommendations Engineering Report","alternative":"Testbed-11 NIEM & IC Data Encoding Specification Assessment and Recommendations Engineering Report","URI":null,"identifier":"15-048r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=65420","type":"PER","creator":"Jeff Harrison","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"274":{"title":"Testbed-11 NIEM-IC Feature Processing API using OGC Web Services","alternative":"Testbed-11 NIEM-IC Feature Processing API using OGC Web Services","URI":null,"identifier":"15-047r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=65418","type":"PER","creator":"Jeff Harrison","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"275":{"title":"Use Cases and Applications of the OGC Moving Features Standard: The Requirements for a Moving Feature API","alternative":"Use Cases and Applications of the OGC Moving Features Standard: The Requirements for a Moving Feature API","URI":null,"identifier":"15-096","URL":"https://portal.opengeospatial.org/files/?artifact_id=64623","type":"DP","creator":"Akinori Asahara, Hideki Hayashi, Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"276":{"title":"OGC® Testbed 11 REST Interface Engineering Report","alternative":"Testbed 11 REST Interface Engineering Report","URI":null,"identifier":"15-052r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=64860","type":"PER","creator":"Frédéric Houbie","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"277":{"title":"OGC® Testbed-11 High Resolution Flood Information Scenario Engineering Report","alternative":"Testbed-11 High Resolution Flood Information Scenario Engineering Report","URI":null,"identifier":"15-046r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=64174","type":"PER","creator":"Eugene G. Yu, Liping Di, Ranjay Shrestha","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"278":{"title":"OGC® Testbed 11 Digital Notice to Airmen (NOTAM) Validation and Enrichment Service Engineering Report","alternative":"Testbed 11 Digital Notice to Airmen (NOTAM) Validation and Enrichment Service Engineering Report","URI":null,"identifier":"15-027r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=64141","type":"PER","creator":"Aleksandar Balaban","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"279":{"title":"Spatial Data on the Web Use Cases & Requirements","alternative":"Spatial Data on the Web Use Cases & Requirements","URI":null,"identifier":"15-074r1","URL":"http://docs.opengeospatial.org/dp/15-074r1/15-074r1.html","type":"D-DP","creator":"Frans Knibbe, Alejandro Llaves","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-12-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"280":{"title":"OGC Observations and Measurements – JSON implementation","alternative":"Observations and Measurements – JSON implementation","URI":null,"identifier":"15-100r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=64910","type":"DP","creator":"Simon J D Cox, Peter Taylor ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-12-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"281":{"title":"A Use-Case for Mobile Location Services with IndoorGML - Indoor Navigation for Visually Impaired People","alternative":"A Use-Case for Mobile Location Services with IndoorGML - Indoor Navigation for Visually Impaired People","URI":null,"identifier":"15-075r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=64644","type":"DP","creator":"Ki-Joune Li, Hyung-Gyu Ryu, Taehoon Kim, and Hack-Cheol Kim","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-11-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"282":{"title":"OGC® Testbed-11 Multi-dimensional GeoPackage Supporting Terrain and Routes Engineering Report","alternative":"Testbed-11 Multi-dimensional GeoPackage Supporting Terrain and Routes Engineering Report","URI":null,"identifier":"15-067","URL":"https://portal.opengeospatial.org/files/?artifact_id=63663","type":"PER","creator":"Gobe Hobona;Roger Brackin","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-11-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"283":{"title":"OGC® Testbed11 Referenceable Grid Harmonization Engineering Report","alternative":"Testbed11 Referenceable Grid Harmonization Engineering Report","URI":null,"identifier":"15-065r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=64145","type":"PER","creator":"Eric Hirschorn, Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-11-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"284":{"title":"OGC® Testbed-11 Symbology Mediation","alternative":"Testbed-11 Symbology Mediation","URI":null,"identifier":"15-058","URL":"https://portal.opengeospatial.org/files/?artifact_id=64385","type":"PER","creator":"Stephane Fellah","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-11-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"285":{"title":"OGC® Testbed-11 Incorporating Social Media in Emergency Response Engineering Report","alternative":"Testbed-11 Incorporating Social Media in Emergency Response Engineering Report","URI":null,"identifier":"15-057r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=64353","type":"PER","creator":"Matthes Rieke, Simon Jirka, Stephane Fellah","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-11-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"286":{"title":"OGC® Testbed-11 Implementing Linked Data and Semantically Enabling OGC Services Engineering Report","alternative":"Testbed-11 Implementing Linked Data and Semantically Enabling OGC Services Engineering Report","URI":null,"identifier":"15-054","URL":"https://portal.opengeospatial.org/files/?artifact_id=64405","type":"PER","creator":"Stephane Fellah","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-11-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"287":{"title":"OGC® CF-netCDF 3.0 encoding using GML Coverage Application Schema","alternative":"CF-netCDF 3.0 encoding using GML Coverage Application Schema","URI":null,"identifier":"14-100r2","URL":"http://docs.opengeospatial.org/is/14-100r2/14-100r2.html","type":"IS","creator":"Ben Domenico, Stefano Nativi","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-11-18","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"288":{"title":"OGC® Testbed-11 DGIWG GMLJP2 testing results Engineering Report","alternative":"Testbed-11 DGIWG GMLJP2 testing results Engineering Report","URI":null,"identifier":"15-073","URL":"https://portal.opengeospatial.org/files/?artifact_id=65887","type":"PER","creator":"E. Devys, L.Colaiacomo, P. Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-11-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"289":{"title":"OGC® Testbed-11 Aviation Feature Schema Recommendations Engineering Report","alternative":"Testbed-11 Aviation Feature Schema Recommendations Engineering Report","URI":null,"identifier":"15-026","URL":"https://portal.opengeospatial.org/files/?artifact_id=63306","type":"PER","creator":"Thomas Forbes, Alberto Olivares, Richard Rombouts","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-10-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"290":{"title":"OGC® Web Feature Service 2.0 Interface Standard - With Corrigendum","alternative":"Web Feature Service 2.0 Interface Standard - With Corrigendum","URI":null,"identifier":"09-025r2","URL":"http://docs.opengeospatial.org/is/09-025r2/09-025r2.html","type":"IS","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-10","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"291":{"title":"OGC® Testbed 11 Catalogue Service and Discovery Engineering Report ","alternative":"Testbed 11 Catalogue Service and Discovery Engineering Report","URI":null,"identifier":"15-056","URL":"https://portal.opengeospatial.org/files/?artifact_id=64382","type":"PER","creator":"Wenwen Li, Sheng Wu","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-10-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"292":{"title":"OGC® Testbed 11 Use of Semantic Linked Data with RDF for National Map NHD and Gazetteer Data Engineering Report ","alternative":"Use of Semantic Linked Data with RDF for National Map NHD and Gazetteer Data Engineering Report ","URI":null,"identifier":"15-066r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=64173","type":"PER","creator":"Gobe Hobona;Roger Brackin","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-10-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"293":{"title":"OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response","alternative":"OGC IOGP/IPIECA Recommended Practice for a Common Operating Picture for Oil Spill Response","URI":null,"identifier":"15-037","URL":"https://portal.opengeospatial.org/files/?artifact_id=63334","type":"BP","creator":"George Percivall ","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-10-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"294":{"title":"Envisioning a Tiled Elevation Extension for the OGC GeoPackage Encoding Standard","alternative":"Envisioning a Tiled Elevation Extension for the OGC GeoPackage Encoding Standard","URI":null,"identifier":"15-039","URL":"https://portal.opengeospatial.org/files/?artifact_id=63289","type":"DP","creator":"Jeff Yutzler","contributor":null,"description":"The GeoPackage Standards Working Group (SWG) presents a vision for storing tiled gridded elevation data in a GeoPackage.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-08-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"295":{"title":"OGC® Testbed 11 GeoPackaging Engineering Report","alternative":"Testbed 11 GeoPackaging Engineering Report","URI":null,"identifier":"15-068r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=64189","type":"PER","creator":"Gobe Hobona;Roger Brackin","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-08-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"296":{"title":"OGC® Testbed 11 Implementing JSON/GeoJSON in an OGC Standard Engineering Report","alternative":"Testbed 11 Implementing JSON/GeoJSON in an OGC Standard Engineering Report","URI":null,"identifier":"15-053r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=64595","type":"PER","creator":"Joan Masó","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-08-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"297":{"title":"OGC® Testbed 11 Data Broker Specifications Engineering Report","alternative":"Testbed 11 Data Broker Specifications Engineering Report","URI":null,"identifier":"15-028","URL":"https://portal.opengeospatial.org/files/?artifact_id=63281","type":"PER","creator":"Daniel Balog","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-08-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"298":{"title":"OGC® Testbed 11 Aviation - Architecture Engineering Report","alternative":"Testbed 11 Aviation - Architecture Engineering Report","URI":null,"identifier":"15-025r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=63793","type":"PER","creator":"Johannes Echterhoff","contributor":null,"description":"This OGC® document describes the architecture implemented in the OGC Testbed 11 Aviation thread.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-08-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"299":{"title":"OGC® Testbed 11 Aviation - Guidance on Using Semantics of Business Vocabulary and Business Rules (SBVR) Engineering Report","alternative":"Testbed 11 Aviation - Guidance on Using Semantics of Business Vocabulary and Business Rules (SBVR) Engineering Report","URI":null,"identifier":"15-024r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=63794","type":"PER","creator":"Johannes Echterhoff","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-08-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"300":{"title":"OGC GeoPackage Plugfest Discussion Paper","alternative":"GeoPackage Plugfest Discussion Paper","URI":null,"identifier":"15-012r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=63285","type":"DP","creator":"Jeff Yutzler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-08-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"301":{"title":"OGC® Testbed 11 Engineering Report: Implementing Common Security Across the OGC Suite of Service Standards","alternative":"Testbed 11 Engineering Report: Implementing Common Security Across the OGC Suite of Service Standards","URI":null,"identifier":"15-022","URL":"https://portal.opengeospatial.org/files/?artifact_id=63312","type":"PER","creator":"Andreas Matheus","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-08-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"302":{"title":"OGC® Web Map Tile Service (WMTS) Simple Profile","alternative":"Web Map Tile Service (WMTS) Simple Profile","URI":null,"identifier":"13-082r2","URL":"http://docs.opengeospatial.org/is/13-082r2/13-082r2.html","type":"Profile","creator":"Joan Masó","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2016-01-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"303":{"title":"OGC KML 2.3","alternative":"KML 2.3","URI":null,"identifier":"12-007r2","URL":"http://docs.opengeospatial.org/is/12-007r2/12-007r2.html","type":"IS","creator":"David Burggraf","contributor":null,"description":"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&#8209;mail, hosted locally for sharing within a private internet, or hosted on a web server.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-08-04","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"304":{"title":"OGC Common DataBase Volume 1 Main Body","alternative":"Common DataBase Volume 1 Main Body","URI":null,"identifier":"15-003","URL":"https://portal.opengeospatial.org/files/?artifact_id=61935","type":"BP","creator":"David Graham","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-07-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"305":{"title":"OGC Common DataBase Volume 2 Appendices","alternative":"Common DataBase Volume 2 Appendices","URI":null,"identifier":"15-004","URL":"https://portal.opengeospatial.org/files/?artifact_id=61936","type":"BP","creator":"David Graham","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-07-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"306":{"title":"Spatial Data on the Web Use Cases & Requirements","alternative":"Spatial Data on the Web Use Cases & Requirements","URI":null,"identifier":"15-074","URL":"http://docs.opengeospatial.org/dp/15-074/15-074.html","type":"DP","creator":"Frans Knibbe, Alejandro Llaves","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-07-22","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"307":{"title":"OpenGIS Web Map Service Client (Queryable) (WMS) Implementation Specification","alternative":"Web Map Service Client (Queryable) (WMS) Implementation Specification","URI":null,"identifier":"06-042","URL":"https://portal.opengeospatial.org/files/?artifact_id=14416","type":"CC","creator":"Jeff de La Beaujardiere","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-03-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"308":{"title":"OGC® GeoPackage Encoding Standard - With Corrigendum","alternative":"GeoPackage Encoding Standard - With Corrigendum","URI":null,"identifier":"12-128r12","URL":"http://www.geopackage.org/spec","type":"ISC","creator":"Paul Daisey","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-04-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"309":{"title":"Geographic information — Well known text representation of coordinate reference systems","alternative":"Well known text representation of coordinate reference systems","URI":null,"identifier":"12-063r5","URL":"http://docs.opengeospatial.org/is/12-063r5/12-063r5.html","type":"IS","creator":"Roger Lott","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-05-01","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"310":{"title":"OGC Filter Encoding 2.0 Encoding Standard - With Corrigendum ","alternative":"Filter Encoding 2.0 Encoding Standard - With Corrigendum ","URI":null,"identifier":"09-026r2","URL":"http://docs.opengeospatial.org/is/09-026r2/09-026r2.html","type":"ISC","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"311":{"title":"OGC® and Ordnance Survey - UK Interoperability Assessment Plugfest (UKIAP) Engineering Report ","alternative":"UK Interoperability Assessment Plugfest (UKIAP) Engineering Report ","URI":null,"identifier":"14-057","URL":"https://portal.opengeospatial.org/files/?artifact_id=61057","type":"PER","creator":"Bart De Lathouwer, Peter Cotroneo, Paul Lacey","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-03-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"312":{"title":"OGC® WPS 2.0 Interface Standard","alternative":"WPS 2.0 Interface Standard","URI":null,"identifier":"14-065","URL":"http://docs.opengeospatial.org/is/14-065/14-065r0.html","type":"IS","creator":"Matthias Mueller","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-03-05","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"313":{"title":"OGC Augmented Reality Markup Language 2.0 (ARML 2.0)","alternative":"Augmented Reality Markup Language 2.0 (ARML 2.0) ","URI":null,"identifier":"12-132r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=62168","type":"IS","creator":"Martin Lechner","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-02-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"314":{"title":"OGC® Moving Features Encoding Extension: Simple Comma Separated Values (CSV)","alternative":"Moving Features Encoding Extension: Simple Comma Separated Values (CSV)","URI":null,"identifier":"14-084r2","URL":"http://docs.opengeospatial.org/is/14-084r2/14-084r2.html","type":"IS","creator":"Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf","contributor":null,"description":"This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-02-17","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"315":{"title":"OGC® Moving Features Encoding Part I: XML Core","alternative":"Moving Features Encoding Part I: XML Core","URI":null,"identifier":"14-083r2","URL":"http://docs.opengeospatial.org/is/14-083r2/14-083r2.html","type":"IS","creator":"Akinori Asahara, Ryosuke Shibasaki, Nobuhiro Ishimaru, David Burggraf","contributor":null,"description":"This OGC® Standard specifies standard encoding representations of movement of geographic features. The primary use case is information exchange.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-02-17","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"316":{"title":"OGC® Testbed 10 Summary Engineering Report","alternative":"Testbed 10 Summary Engineering Report","URI":null,"identifier":"14-044","URL":"https://portal.opengeospatial.org/files/?artifact_id=61108","type":"PER","creator":"Lew Leinenweber","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-02-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"317":{"title":"USGS OGC® Interoperability Assessment Report","alternative":"USGS OGC® Interoperability Assessment Report","URI":null,"identifier":"14-079r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=59983","type":"PER","creator":"Ingo Simonis","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-02-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"318":{"title":"Unified Geo-data Reference Model for Law Enforcement and Public Safety","alternative":"Unified Geo-data Reference Model for Law Enforcement and Public Safety","URI":null,"identifier":"14-106","URL":"http://docs.opengeospatial.org/bp/14-106/14-106.html","type":"BP","creator":"Carl Reed, Jennifer Harne","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-01-30","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"319":{"title":"OGC Information Technology Standards for Sustainable Development","alternative":"Information Technology Standards for Sustainable Development","URI":null,"identifier":"14-095","URL":"https://portal.opengeospatial.org/files/60920","type":"WhitePaper","creator":"Lance McKee","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-01-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"320":{"title":"OGC Smart Cities Spatial Information Framework","alternative":"Smart Cities Spatial Information Framework","URI":null,"identifier":"14-115","URL":"https://portal.opengeospatial.org/files/61188","type":"WhitePaper","creator":"George Percivall","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2015-01-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"321":{"title":"WaterML2.0 part 2 – rating tables, gauging observations and cross-sections: Interoperability Experiment Results","alternative":"WaterML2.0 part 2 – rating tables, gauging observations and cross-sections: Interoperability Experiment Results","URI":null,"identifier":"14-114r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=61224","type":"PER","creator":"Peter Taylor ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-12-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"322":{"title":"OGC® OpenSearch Extension for Earth Observation Satellite Tasking: Best Practice","alternative":"OpenSearch Extension for Earth Observation Satellite Tasking: Best Practice","URI":null,"identifier":"13-039","URL":"http://docs.opengeospatial.org/bp/13-039/13-039.html","type":"BP","creator":"Nicolas Fanjeau, Sebastian Ulrich","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-12-29","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"323":{"title":"OGC® IndoorGML","alternative":"IndoorGML","URI":null,"identifier":"14-005r3","URL":"http://docs.opengeospatial.org/is/14-005r3/14-005r3.html","type":"IS","creator":"Jiyeong Lee, Ki-Joune Li, Sisi Zlatanova, Thomas H. Kolbe, Claus Nagel, Thomas Becker","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-12-02","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"324":{"title":"WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data","alternative":"WaterML-WQ – an O&M and WaterML 2.0 profile for water quality data","URI":null,"identifier":"14-003","URL":"http://docs.opengeospatial.org/bp/14-003/14-003.html","type":"BP","creator":"Simon J D Cox, Bruce A Simons","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-12-02","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"325":{"title":"OGC® Aircraft Access to SWIM (AAtS) Harmonization Project Summary Report","alternative":"Aircraft Access to SWIM (AAtS) Harmonization Project Summary Report","URI":null,"identifier":"14-086r1","URL":"https://portal.opengeospatial.org/files/60176","type":"PER","creator":"Josh Lieberman, Johannes Echterhoff, Matt de Ris, George Wilber","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-11-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"326":{"title":"OGC® Aircraft Access to SWIM (AAtS) Harmonization Architecture Report","alternative":"Aircraft Access to SWIM (AAtS) Harmonization Architecture Report","URI":null,"identifier":"14-073r1","URL":"https://portal.opengeospatial.org/files/60175","type":"PER","creator":"George Wilber, Johannes Echterhoff, Matt de Ris, Joshua Lieberman","contributor":null,"description":"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). ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-11-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"327":{"title":"OGC® Sensor Observation Service 2.0 Hydrology Profile","alternative":"Sensor Observation Service 2.0 Hydrology Profile","URI":null,"identifier":"14-004r1","URL":"http://docs.opengeospatial.org/bp/14-004r1/14-004r1.html","type":"BP","creator":"Volker Andres, Simon Jirka , Michael Utech","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-10-20","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"328":{"title":"Testbed 10 Performance of OGC® Services in the Cloud: The WMS, WMTS, and WPS cases","alternative":"Testbed 10 Performance of OGC® Services in the Cloud: The WMS, WMTS, and WPS cases","URI":null,"identifier":"14-028r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=59618","type":"PER","creator":"Edric Keighan, Benjamin Pross, Hervé Caumont","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-10-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"329":{"title":"OGC® GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core ","alternative":"GML in JPEG 2000 (GMLJP2) Encoding Standard Part 1: Core ","URI":null,"identifier":"08-085r4","URL":"http://docs.opengeospatial.org/is/08-085r4/08-085r4.html","type":"IS","creator":"Lucio Colaiacomo, Joan Masó, Emmanuel Devys","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-09-23","dateAccepted":null,"dateSubmitted":null,"format":"text/html","hasFormat":null,"extent":null},"330":{"title":"OGC® Web Services Facade for OGC IP Engineering Report","alternative":"Web Services Facade for OGC IP Engineering Report","URI":null,"identifier":"12-133","URL":"https://portal.opengeospatial.org/files/?artifact_id=51178","type":"PER","creator":"John Hudson","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-08-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"331":{"title":"OGC KML (Level 3)","alternative":"KML (Level 3)","URI":null,"identifier":"07-147r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=27810","type":"CC","creator":"Tim Wilson","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-04-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"332":{"title":"OGC KML (Level 2)","alternative":"KML (Level 2)","URI":null,"identifier":"07-147r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=27810","type":"CC","creator":"Tim Wilson","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-04-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"333":{"title":"OGC RESTful encoding of OGC Sensor Planning Service  for Earth Observation satellite Tasking","alternative":"RESTful encoding of OGC Sensor Planning Service  for Earth Observation satellite Tasking","URI":null,"identifier":"14-012r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=57203","type":"BP","creator":"Nicolas FANJEAU, Sebastian ULRICH","contributor":null,"description":"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&#8195;\r\n","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"334":{"title":"OGC® Testbed 10 Cross Community Interoperability (CCI) Ontology Engineering Report","alternative":"Testbed 10 Cross Community Interoperability (CCI) Ontology Engineering Report","URI":null,"identifier":"14-049","URL":"https://portal.opengeospatial.org/files/?artifact_id=58974","type":"PER","creator":"Ingo Simonis, Stephane Fellah","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"335":{"title":"OGC® Testbed 10 Cross Community Interoperability (CCI) Hydro Model Interoperability Engineering Report","alternative":"Testbed 10 Cross Community Interoperability (CCI) Hydro Model Interoperability Engineering Report","URI":null,"identifier":"14-048","URL":"https://portal.opengeospatial.org/files/?artifact_id=58944","type":"PER","creator":"Genong (Eugene) Yu, Liping Di","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"336":{"title":"OGC® Testbed 10 Aviation Human Factor Based Portrayal of Digital NOTAMs ER","alternative":"Testbed 10 Aviation Human Factor Based Portrayal of Digital NOTAMs ER","URI":null,"identifier":"14-039","URL":"https://portal.opengeospatial.org/files/?artifact_id=58929","type":"PER","creator":"Thibault Dacla, Daniel Balog","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"337":{"title":"OGC® Testbed 10 Engineering Report:  Aviation Dissemination of Weather Data","alternative":"Testbed 10 Engineering Report:  Aviation Dissemination of Weather Data","URI":null,"identifier":"14-038r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=58117","type":"PER","creator":"Mark Hughes","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"338":{"title":"OGC® Testbed 10 Flight Information Exchange Model GML Schema","alternative":"Testbed 10 Flight Information Exchange Model GML Schema","URI":null,"identifier":"14-037","URL":"https://portal.opengeospatial.org/files/?artifact_id=58956","type":"PER","creator":"Thomas Forbes, Ballal Joglekar","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"339":{"title":"OGC® Testbed 10 Virtual Global Gazetteer Engineering Report","alternative":"Testbed 10 Virtual Global Gazetteer Engineering Report","URI":null,"identifier":"14-029r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=59336","type":"PER","creator":"Martin Klopfer","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"340":{"title":"OGC Web Feature Service (WFS) Temporality Extension","alternative":"Web Feature Service (WFS) Temporality Extension","URI":null,"identifier":"12-027r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=58922","type":"DP","creator":"Timo Thomas","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"341":{"title":"OGC® Testbed-10 CCI VGI Engineering Report","alternative":"Testbed-10 CCI VGI Engineering Report","URI":null,"identifier":"14-016","URL":"https://portal.opengeospatial.org/files/?artifact_id=58925","type":"PER","creator":"Arne Bröring;Simon Jirka;Matthes Rieke, Benjamin Pross","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"342":{"title":"OGC® Testbed 10 Report on Aviation Architecture","alternative":"Testbed 10 Report on Aviation Architecture","URI":null,"identifier":"14-008","URL":"https://portal.opengeospatial.org/files/?artifact_id=58927","type":"PER","creator":"Matthes Rieke","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"343":{"title":"OGC® Testbed 10 Report on Aviation Binding AIXM to Development Tools","alternative":"Testbed 10 Report on Aviation Binding AIXM to Development Tools","URI":null,"identifier":"14-007","URL":"https://portal.opengeospatial.org/files/?artifact_id=58931","type":"PER","creator":"Matthes Rieke","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"344":{"title":"OGC® Testbed 10 Recommendations for Exchange of Terrain Data","alternative":"Testbed 10 Recommendations for Exchange of Terrain Data","URI":null,"identifier":"14-006r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=59793","type":"PER","creator":"Daniel Balog","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"345":{"title":"OGC® Testbed 10 Annotations Engineering Report","alternative":"Testbed 10 Annotations Engineering Report","URI":null,"identifier":"14-002","URL":"https://portal.opengeospatial.org/files/?artifact_id=58965","type":"PER","creator":"Joan Masó and Raj Singh","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"346":{"title":"OGC® Testbed 10 Provenance Engineering Report","alternative":"Testbed 10 Provenance Engineering Report","URI":null,"identifier":"14-001","URL":"https://portal.opengeospatial.org/files/?artifact_id=58967","type":"PER","creator":"Joan Masó, Guillem Closa Yolanda Gil and Benjamin Proß","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"347":{"title":"Testbed 10 Engineering Report: GML for Aviation Conformance Testing","alternative":"Testbed 10 Engineering Report: GML for Aviation Conformance Testing","URI":null,"identifier":"14-000","URL":"https://portal.opengeospatial.org/files/?artifact_id=58995","type":"PER","creator":"R. Martell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-07-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"348":{"title":"OGC® GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile","alternative":"GML Application Schema - Coverages - GeoTIFF Coverage Encoding Profile","URI":null,"identifier":"12-100r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=54813","type":"IS","creator":"Stephan Meissl","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-05-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"349":{"title":"OGC Open Modelling Interface Interface Standard","alternative":"Open Modelling Interface Interface Standard","URI":null,"identifier":"11-014r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=59022","type":"IS","creator":"Stanislav Vanecek, Roger Moore","contributor":null,"description":"<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. \r\n</p>\r\n<p>\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-­&#8208;compliant components are provided by the OpenMI Association and third-­&#8208;party software vendors – visit www.openmi.org for further documentation.</p>\r\n<p>\r\n<a href=https://portal.opengeospatial.org/files/?artifact_id=59022>pdf</a> <br>\r\n<a href=https://portal.opengeospatial.org/files/?artifact_id=59022&format=docx>docx</a>\r\n</p>","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-05-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"350":{"title":"Cyberarchitecture for Geosciences   White Paper","alternative":"Cyberarchitecture for Geosciences   White Paper","URI":null,"identifier":"OGC 11-145","URL":"https://portal.opengeospatial.org/files/?artifact_id=46388","type":"WhitePaper","creator":"George Percivall","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-05-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"351":{"title":"OGC® Testbed-10 Service Integration Engineering Report","alternative":"Testbed-10 Service Integration Engineering Report","URI":null,"identifier":"14-013r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=58892","type":"PER","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-05-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"352":{"title":"OGC I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0","alternative":"I15 (ISO19115 Metadata) Extension Package of CS-W ebRIM Profile 1.0","URI":null,"identifier":"13-084r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=56905","type":"ISx","creator":"Uwe Voges, Frédéric Houbie, Nicolas Lesage, Marie-Lise Vautier","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-04-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"353":{"title":"OGC User Management Interfaces for Earth Observation Services","alternative":"User Management Interfaces for Earth Observation Services","URI":null,"identifier":"07-118r9","URL":"https://portal.opengeospatial.org/files/?artifact_id=54929","type":"BP","creator":"P. Denis, P. Jacques","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-04-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"354":{"title":"OGC RESTful Encoding of Ordering Services Framework For Earth Observation Products","alternative":"RESTful Encoding of Ordering Services Framework For Earth Observation Products","URI":null,"identifier":"13-042","URL":"https://portal.opengeospatial.org/files/?artifact_id=55209","type":"BP","creator":"Daniele Marchionni","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-04-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"355":{"title":"OGC® Testbed 10 CCI Profile Interoperability Engineering Report","alternative":"Testbed 10 CCI Profile Interoperability Engineering Report","URI":null,"identifier":"14-021r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=57336","type":"PER","creator":"Gobe Hobona, Roger Brackin","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-04-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"356":{"title":"OGC® Testbed 10 OWS Context in NIEM Engineering Report","alternative":"Testbed 10 OWS Context in NIEM Engineering Report","URI":null,"identifier":"14-017","URL":"https://portal.opengeospatial.org/files/?artifact_id=57334","type":"PER","creator":"Gobe Hobona, Roger Brackin","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-04-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"357":{"title":"OGC® Climate Challenge Integration Plugfest 2009 Engineering Report","alternative":"Climate Challenge Integration Plugfest 2009 Engineering Report","URI":null,"identifier":"10-002","URL":"https://portal.opengeospatial.org/files/?artifact_id=37839","type":"PER","creator":"Raj Singh","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-04-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"358":{"title":"Topic 2.1: Spatial Referencing by Coordinates - Extension for Parametric Values","alternative":"Topic 2.1: Spatial Referencing by Coordinates - Extension for Parametric Values","URI":null,"identifier":"10-020","URL":"https://portal.opengeospatial.org/files/?artifact_id=37761","type":"D-AS","creator":"Paul Cooper","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-04-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"359":{"title":"OGC Sensor Observation Service 2.0 Hydrology Profile","alternative":"Sensor Observation Service 2.0 Hydrology Profile","URI":null,"identifier":"14-004","URL":"https://portal.opengeospatial.org/files/?artifact_id=57327","type":"D-DP","creator":"GEOWOW Consortium","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-04-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"360":{"title":"OGC® OWS-7 Schema Automation Engineering Report","alternative":"OWS-7 Schema Automation Engineering Report","URI":null,"identifier":"10-088r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=50438","type":"PER","creator":"Clemens Portele","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-04-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"361":{"title":"OGC® Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context","alternative":"Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context","URI":null,"identifier":"14-009r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=57477","type":"PER","creator":"Pedro Gonçalves","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-04-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"362":{"title":"OGC Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data","alternative":"Best Practice for using Web Map Services (WMS) with Time-Dependent or Elevation-Dependent Data","URI":null,"identifier":"12-111r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=56394","type":"BP","creator":"Marie-Françoise Voidrot-Martinez, Chris Little, Jürgen Seib, Roy Ladner, Adrian Custer, Jeff de La B","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-04-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"363":{"title":"OGC® OpenSearch Geo and Time Extensions","alternative":"OpenSearch Geo and Time Extensions","URI":null,"identifier":"10-032r8","URL":"https://portal.opengeospatial.org/files/?artifact_id=56866","type":"IS","creator":"Pedro Gonçalves","contributor":null,"description":"<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>\r\n<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>\r\n<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.\r\nServices that support the OpenSearch Specification, the Geo and Time extensions defined in this document are called OpenSearch GeoTemporal Services.</p>\r\n","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-04-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"364":{"title":"OGC® Web Coverage Service Interface Standard - CRS Extension","alternative":"Web Coverage Service Interface Standard - CRS Extension","URI":null,"identifier":"11-053r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=54209","type":"ISx","creator":"Peter Baumann, Jinsongdi Yu","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-03-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"365":{"title":"OGC® Web Coverage Service Interface Standard -  Interpolation Extension","alternative":"Web Coverage Service Interface Standard -  Interpolation Extension","URI":null,"identifier":"12-049","URL":"https://portal.opengeospatial.org/files/?artifact_id=54502","type":"ISx","creator":"Peter Baumann, Jinsongdi Yu","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"366":{"title":"OGC® Web Coverage Service Interface Standard - Range Subsetting Extension","alternative":"Web Coverage Service Interface Standard - Range Subsetting Extension","URI":null,"identifier":"12-040","URL":"https://portal.opengeospatial.org/files/?artifact_id=54503","type":"ISx","creator":"Peter Baumann, Jinsongdi Yu","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"367":{"title":"OGC® Web Coverage Service Interface Standard -  Scaling Extension","alternative":"Web Coverage Service Interface Standard -  Scaling Extension","URI":null,"identifier":"12-039","URL":"https://portal.opengeospatial.org/files/?artifact_id=54504","type":"ISx","creator":"Peter Baumann, Jinsongdi Yu","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"368":{"title":"OGC® Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile","alternative":"Web Coverage Service 2.0 Interface Standard - Earth Observation Application Profile","URI":null,"identifier":"10-140r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=42722","type":"Profile","creator":"Peter Baumann, Stephan Meissl, Jinsongdi Yu","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"369":{"title":"OGC® Web Coverage Service WCS Interface Standard - Processing Extension","alternative":"Web Coverage Service WCS Interface Standard - Processing Extension","URI":null,"identifier":"08-059r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=54506","type":"ISx","creator":"Peter Baumann, Jinsongdi Yu","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"370":{"title":"OGC Best Practice for Sensor Web Enablement: Provision of Observations through an OGC Sensor Observation Service (SOS)","alternative":"Provision of Observations through an OGC Sensor Observation Service (SOS)","URI":null,"identifier":"13-015","URL":"https://portal.opengeospatial.org/files/?artifact_id=52675","type":"BP","creator":"EO2HEAVEN Consortium","contributor":null,"description":"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/ ).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"371":{"title":"OGC® Best Practice for Sensor Web Enablement Lightweight SOS Profile for Stationary In-Situ Sensors","alternative":"Best Practice for Sensor Web Enablement Lightweight SOS Profile for Stationary In-Situ Sensors","URI":null,"identifier":"11-169r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=52803","type":"BP","creator":"Simon Jirka, Christoph Stasch, Arne Bröring","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"372":{"title":"OGC OpenSearch Extension for Correlated Search","alternative":"OpenSearch Extension for Correlated Search","URI":null,"identifier":"13-068","URL":"https://portal.opengeospatial.org/files/?artifact_id=55219","type":"DP","creator":"Pedro Gonçalves","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"373":{"title":"OGC CHISP-1 Summary Engineering Report","alternative":"CHISP-1 Summary Engineering Report","URI":null,"identifier":"13-046r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=55432","type":"PER","creator":"Lew Leinenweber","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"374":{"title":"OGC® CHISP-1 Engineering Report","alternative":"CHISP-1 Engineering Report","URI":null,"identifier":"130=-053r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=55244","type":"PER","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"375":{"title":"OGC HY_Features: a Common Hydrologic Feature Model","alternative":"HY_Features: a Common Hydrologic Feature Model","URI":null,"identifier":"11-039r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=55157","type":"DP","creator":"Irina Dornblut, Rob Atkinson","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"376":{"title":"OGC® WaterML 2.0: Part 1- Timeseries","alternative":"WaterML 2.0: Part 1- Timeseries","URI":null,"identifier":"10-126r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=57222","type":"IS","creator":"Peter Taylor","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"377":{"title":"OGC® GeoPackage Encoding Standard","alternative":"GeoPackage Encoding Standard","URI":null,"identifier":"12-128r10","URL":"https://portal.opengeospatial.org/files/?artifact_id=56357","type":"IS","creator":"Paul Daisey","contributor":null,"description":"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<br /><br />\r\nFor the online version of the standard and the developer resources, visit <a href=http://www.geopackage.org/>http://www.geopackage.org/</a>","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"378":{"title":"OGC® SensorML: Model and XML Encoding Standard","alternative":"SensorML: Model and XML Encoding Standard","URI":null,"identifier":"12-000","URL":"https://portal.opengeospatial.org/files/?artifact_id=55939","type":"IS","creator":"Mike Botts, Alexandre Robin","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-02-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"379":{"title":"Modeling an application domain extension of CityGML in UML","alternative":"Modeling an application domain extension of CityGML in UML","URI":null,"identifier":"12-066","URL":"https://portal.opengeospatial.org/files/?artifact_id=49000","type":"BP","creator":"Linda van den Brink, Jantien Stoter, Sisi Zlatanova","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-01-31","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"380":{"title":"OGC Download Service for Earth Observation Products Best Practice","alternative":"Download Service for Earth Observation Products Best Practice","URI":null,"identifier":"13-043","URL":"https://portal.opengeospatial.org/files/?artifact_id=55210","type":"BP","creator":"Daniele Marchionni, Raul Cafini","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-01-31","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"381":{"title":"OGC OWS Context Conceptual Model","alternative":"OWS Context Conceptual Model","URI":null,"identifier":"12-080r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=55182","type":"IS","creator":"Roger Brackin, Pedro Gonçalves ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-01-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"382":{"title":"OGC OWS Context Atom Encoding Standard","alternative":"OWS Context Atom Encoding Standard","URI":null,"identifier":"12-084r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=55183","type":"IS","creator":"Roger Brackin, Pedro Gonçalves ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2014-01-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"383":{"title":"OGC® Sensor Planning Service (SPS) - Core","alternative":"SPS - Core","URI":null,"identifier":"09-000","URL":"https://portal.opengeospatial.org/files/?artifact_id=38478","type":"CC","creator":"Ingo Simonis, Johannes Echterhoff","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"384":{"title":"OpenGIS Geography Markup Language (GML) - Documents","alternative":"GML - Documents","URI":null,"identifier":"07-036","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"385":{"title":"OGC Sensor Observation Service (SOS) - SOAP","alternative":"SOS - SOAP","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"386":{"title":"OGC Sensor Observation Service (SOS) - GetFeatureOfInterest KVP Binding","alternative":"SOS - GetFeatureOfInterest KVP Binding","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"387":{"title":"OGC Sensor Observation Service (SOS) - KVP Binding Extension","alternative":"SOS - KVP Binding Extension","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"388":{"title":"OGC Sensor Observation Service (SOS) - XML Encoding","alternative":"SOS - XML Encoding","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"389":{"title":"OGC Sensor Observation Service (SOS) - Spatial Filtering Profile","alternative":"SOS - Spatial Filtering Profile","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"390":{"title":"OGC Sensor Observation Service (SOS) - Result Retrieval","alternative":"SOS - Result Retrieval","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"391":{"title":"OGC Sensor Observation Service (SOS) - Result Insertion","alternative":"SOS - Result Insertion","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"392":{"title":"OGC Sensor Observation Service (SOS) - Observation Insertion","alternative":"SOS - Observation Insertion","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"393":{"title":"OGC Sensor Observation Service (SOS) - Sensor Deletion","alternative":"SOS - Sensor Deletion","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"394":{"title":"OGC Sensor Observation Service (SOS) - Sensor Insertion","alternative":"SOS - Sensor Insertion","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"395":{"title":"OGC Sensor Observation Service (SOS) - Insertion Capabilities","alternative":"SOS Insertion Capabilities","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"396":{"title":"OGC Sensor Observation Service (SOS) - Observation Retrieval By ID","alternative":"SOS - Observation Retrieval By ID","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"397":{"title":"OGC Sensor Observation Service (SOS) - Feature of Interest Retrieval","alternative":"SOS Feature of Interest Retrieval","URI":null,"identifier":"12-006","URL":"","type":"CC","creator":"","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":null,"dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"398":{"title":"OGC Sensor Observation Service (SOS) - Core","alternative":"SOS - Core","URI":null,"identifier":"12-006","URL":"https://portal.opengeospatial.org/files/?artifact_id=47599","type":"CC","creator":"Arne Bröring, Christoph Stasch, Johannes Echterhoff","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-04-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"399":{"title":"OpenGIS Web Feature Service - Locking","alternative":"Locking WFS","URI":null,"identifier":"09-025r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=39967","type":"CC","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-11-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"400":{"title":"OpenGIS Web Feature Service - Basic","alternative":"Basic WFS","URI":null,"identifier":"09-025r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=39967","type":"CC","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-11-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"401":{"title":"Summary and Recommendations of the Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Interoperabi","alternative":"Summary and Recommendations of the Geospatial Enhancement for the National Information Exchange Model (Geo4NIEM) Interoperabi","URI":null,"identifier":"13-054r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=55342","type":"PER","creator":"Richard Martell","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-11-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"402":{"title":"OGC® Military Operations Geospatial Interoperability Experiment (MOGIE)","alternative":"Military Operations Geospatial Interoperability Experiment (MOGIE)","URI":null,"identifier":"13-080r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=55252","type":"PER","creator":"Frank Klucznik, Matthew Weber, Robin Houtmeyers, Roger Brackin","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-10-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"403":{"title":"OGC Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 GML 3.2.1 Encoding Extension","alternative":"Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 GML 3.2.1 Encoding Extension","URI":null,"identifier":"13-101","URL":"https://portal.opengeospatial.org/files/?artifact_id=55232","type":"DP","creator":"Andreas Matheus","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-11-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"404":{"title":"OGC GeoXACML and XACML  Policy Administration Web Service (PAWS)","alternative":"GeoXACML and XACML  Policy Administration Web Service (PAWS)","URI":null,"identifier":"13-099","URL":"https://portal.opengeospatial.org/files/?artifact_id=55230","type":"DP","creator":"Jan Herrmann, Andreas Matheus","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-11-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"405":{"title":"OGC Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core","alternative":"Geospatial eXensible Access Control Markup Language (GeoXACML) 3.0 Core","URI":null,"identifier":"13-100","URL":"https://portal.opengeospatial.org/files/?artifact_id=55231","type":"DP","creator":"Andreas Matheus ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-11-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"406":{"title":"OGC® SWE Implementation Maturity  Engineering Report","alternative":"SWE Implementation Maturity  Engineering Report","URI":null,"identifier":"13-032","URL":"https://portal.opengeospatial.org/files/?artifact_id=53823","type":"PER","creator":"George Percivall","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-09-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"407":{"title":"OGC Naming Authority – Policies and Procedures ","alternative":"OGC Naming Authority – Policies and Procedures ","URI":null,"identifier":"09-046r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=51857","type":"POL","creator":"Simon Cox","contributor":null,"description":"The OGC Naming Authority (OGC-NA) controls the assignment of OGC Names to resources of interest in geographic information infrastructures. 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. \r\nThe scope of the resources that may be identified with OGC Names is indicated by the set of items in the register http://www.opengis.net/register/ogc-na/type/ .\r\n","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"408":{"title":"OGC® Name Type Specification for Coordinate Reference Systems","alternative":"Name Type Specification for Coordinate Reference Systems","URI":null,"identifier":"11-135r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=53819","type":"BP","creator":"Peter Baumann","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"409":{"title":"OGC Web Feature Service (WFS) Temporality Extension ","alternative":"OGC Web Feature Service (WFS) Temporality Extension ","URI":null,"identifier":"12-027r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=51815","type":"D-DP","creator":"Timo Thomas","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"410":{"title":"Name type specification – ontology resources","alternative":"Name type specification – ontology resources","URI":null,"identifier":"12-081","URL":"https://portal.opengeospatial.org/files/?artifact_id=51856","type":"POL-NTS","creator":"Simon Cox","contributor":null,"description":"An OGC name is required for ontology resources published by OGC. This includes OWL\r\nontologies, classes and properties.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"411":{"title":"OGC® OWS-9 Engineering Report - CCI - Single Point of Entry Global Gazetteer","alternative":"OWS-9 Engineering Report - CCI - Single Point of Entry Global Gazetteer","URI":null,"identifier":"12-104r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=52065","type":"PER","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"412":{"title":"OGC® OWS-9 - OWS Context evaluation IP Engineering Report","alternative":"OWS-9 - OWS Context evaluation IP Engineering Report","URI":null,"identifier":"12-105","URL":"https://portal.opengeospatial.org/files/?artifact_id=52018","type":"PER","creator":"Joan Masó","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"413":{"title":"OGC® OWS-9 Architecture - Registry Engineering Report","alternative":"OWS-9 Architecture - Registry Engineering Report","URI":null,"identifier":"12-144","URL":"https://portal.opengeospatial.org/files/?artifact_id=53255","type":"PER","creator":"David Burggraf","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"414":{"title":"OGC® OWS-9 Web Feature Service Temporality Extension Engineering Report","alternative":"OWS-9 Web Feature Service Temporality Extension Engineering Report","URI":null,"identifier":"12-146","URL":"https://portal.opengeospatial.org/files/?artifact_id=51811","type":"PER","creator":"Timo Thomas","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"415":{"title":"OGC® OWS-9 CITE Help Guide Engineering Report","alternative":"OWS-9 CITE Help Guide Engineering Report","URI":null,"identifier":"12-152r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=52112","type":"PER","creator":"Luis Bermudez","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"416":{"title":"OGC® OWS-9 OWS Innovations WCS for LIDAR Engineering Report ","alternative":"OWS-9 OWS Innovations WCS for LIDAR Engineering Report ","URI":null,"identifier":"12-155","URL":"https://portal.opengeospatial.org/files/?artifact_id=51891","type":"PER","creator":"Weiguo Han, Yuanzheng Shao, Liping Di","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"417":{"title":"OGC® OWS-9 Engineering Report - OWS Innovations - Map Tiling Methods Harmonization","alternative":"OWS-9 Engineering Report - OWS Innovations - Map Tiling Methods Harmonization","URI":null,"identifier":"12-157","URL":"https://portal.opengeospatial.org/files/?artifact_id=52757","type":"PER","creator":"Joan Masó","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"418":{"title":"OGC® OWS-9 Report on Aviation Performance Study","alternative":"OWS-9 Report on Aviation Performance Study","URI":null,"identifier":"12-158","URL":"https://portal.opengeospatial.org/files/?artifact_id=51817","type":"PER","creator":"Matthes Rieke","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"419":{"title":"OGC® OWS 9 Data Quality and Web Mapping Engineering Report","alternative":"OWS 9 Data Quality and Web Mapping Engineering Report","URI":null,"identifier":"12-160r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=52884","type":"PER","creator":"Jon Blower, Xiaoyu Yang, Joan Masó and Simon Thum","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"420":{"title":"OWS-9 WCS Conformance Testing Engineering Report","alternative":"OWS-9 WCS Conformance Testing Engineering Report","URI":null,"identifier":"12-162r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=51911","type":"PER","creator":"Jinsongdi Yu, Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"421":{"title":"OGC® OWS-9 Data Transmission Management","alternative":"OWS-9 Data Transmission Management","URI":null,"identifier":"12-163","URL":"https://portal.opengeospatial.org/files/?artifact_id=51812","type":"PER","creator":"Thibault Dacla; Eriza Hafid Fazli; Charles Chen; Stuart Wilson","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"422":{"title":"WaterML2.0 - part 2: Ratings, Gaugings and Sections Discussion Paper","alternative":"WaterML2.0 - part 2: Ratings, Gaugings and Sections Discussion Paper","URI":null,"identifier":"13-021r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=54423","type":"DP","creator":"Peter Taylor","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"423":{"title":"OGC® OWS-9 Innovation - Coverages: Coverage Access (OPeNDAP) Study","alternative":"OWS-9 Innovation - Coverages: Coverage Access (OPeNDAP) Study","URI":null,"identifier":"12-095","URL":"https://portal.opengeospatial.org/files/?artifact_id=52783","type":"PER","creator":"James Gallagher, Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-06-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"424":{"title":"OpenGIS Geography Markup Language (GML) - Application Schemas Defining Values","alternative":"GML - Application Schemas Defining Values","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"CC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"425":{"title":"OpenGIS Geography Markup Language (GML) - Application Schemas Defining Dictionaries and Definitions","alternative":"GML - Application Schemas Defining Dictionaries and Definitions","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"CC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"426":{"title":"OpenGIS Geography Markup Language (GML) - Application Schemas Defining Observations","alternative":"GML - Application Schemas Defining Observations","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"CC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"427":{"title":"OpenGIS Geography Markup Language (GML) - Application Schemas Defining Coverages","alternative":"GML - Application Schemas Defining Coverages","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"CC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"428":{"title":"OpenGIS Geography Markup Language (GML) - Application Schemas Defining Coordinate Reference Systems","alternative":"GML - Application Schemas Defining Coordinate Reference Systems","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"CC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"429":{"title":"OpenGIS Geography Markup Language (GML) - Application Schemas Defining Time","alternative":"GML - Application Schemas Defining Time","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"CC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"430":{"title":"OpenGIS Geography Markup Language (GML) - Application Schemas Defining Spatial Toplogies","alternative":"GML - Application Schemas Defining Spatial Toplogies","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"CC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"431":{"title":"OpenGIS Geography Markup Language (GML) - Application Schemas Defining Spatial Geometries","alternative":"GML - Application Schemas Defining Spatial Geometries","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"CC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"432":{"title":"OpenGIS  Geography Markup Language (GML) Application Schemas Defining Features and Feature Collections","alternative":"GML - Application Schemas Defining Features and Feature Collections","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"CC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"433":{"title":"OpenGIS Geography Markup Language (GML) Encoding Standard","alternative":"GMLSF (Level 2)","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"CC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"434":{"title":"OpenGIS Geography Markup Language (GML) Encoding Standard","alternative":"GMLSF (Level 1)","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"CC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"435":{"title":"OpenGIS Geography Markup Language (GML) Encoding Standard","alternative":"GMLSF (Level 0)","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"CC","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"436":{"title":"OpenGIS Web Feature Service - Transactional","alternative":"Transactional WFS","URI":null,"identifier":"09-025r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=39967","type":"CC","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-11-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"437":{"title":"CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW","alternative":"CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW","URI":null,"identifier":"07-110r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=31137","type":"CC","creator":"Richard Martell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-02-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"438":{"title":"CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW","alternative":"CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW","URI":null,"identifier":"07-110r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=31137","type":"CC","creator":"Richard Martell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-02-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"439":{"title":"OpenGIS Geography Markup Language (GML) Encoding Specification","alternative":"Geography Markup Language (GML) Encoding Specification","URI":null,"identifier":"03-105r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=4700","type":"D-BP","creator":"Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-04-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"440":{"title":"OpenGIS Geography Markup Language (GML) Encoding Specification","alternative":"Geography Markup Language (GML) Encoding Specification","URI":null,"identifier":"03-105r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=4700","type":"D-BP","creator":"Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-04-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"441":{"title":"OpenGIS Geography Markup Language (GML) Encoding Specification","alternative":"Geography Markup Language (GML) Encoding Specification","URI":null,"identifier":"03-105r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=4700","type":"D-BP","creator":"Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-04-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"442":{"title":"OpenGIS Web Map Service Client (WMS) Implementation Specification","alternative":"Web Map Service Client (WMS) Implementation Specification","URI":null,"identifier":"06-042","URL":"https://portal.opengeospatial.org/files/?artifact_id=14416","type":"CC","creator":"Jeff de La Beaujardiere","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-03-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"443":{"title":"OGC® Sensor Web Enablement: Overview And High Level Architecture","alternative":"Sensor Web Enablement: Overview And High Level Architecture","URI":null,"identifier":"07-165r1","URL":"http://docs.opengeospatial.org/wp/07-165r1/","type":"WhitePaper","creator":"Carl Reed, Mike Botts, George Percivall, John Davidson","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-04-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"444":{"title":"OWS-9: Summary of the  OGC Web Services, Phase 9 (OWS-9) Interoperability Testbed","alternative":"OWS-9: Summary of the  OGC Web Services, Phase 9 (OWS-9) Interoperability Testbed","URI":null,"identifier":"13-011","URL":"https://portal.opengeospatial.org/files/?artifact_id=53036","type":"PER","creator":"Nadine Alameh","contributor":null,"description":"This report summarizes the results of OGC Web Services Initiative, Phase 9 (OWS-9).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-04-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"445":{"title":"OWS-9 Engineering Report - SSI - Bulk Data Transfer (GML Streaming)","alternative":"OWS-9 Engineering Report - SSI - Bulk Data Transfer (GML Streaming)","URI":null,"identifier":"12-097","URL":"https://portal.opengeospatial.org/files/?artifact_id=51998","type":"PER","creator":"Jeff Harrison","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-03-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"446":{"title":"OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - Corrigendum  ","alternative":"Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension - Corrigendum  ","URI":null,"identifier":"09-147r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=50140","type":"ISC","creator":"Peter Baumann","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-03-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"447":{"title":"EO Product Collection, Service and Sensor Discovery using the CS-W ebRIM Catalogue","alternative":"EO Product Collection, Service and Sensor Discovery using the CS-W ebRIM Catalogue","URI":null,"identifier":"11-035r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=53276","type":"BP","creator":"Frédéric Houbie, Steven Smolders","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-03-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"448":{"title":"OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report","alternative":"OWS-9 Reference Architecture Profile (RAP) Advisor Engineering Report","URI":null,"identifier":"12-156","URL":"https://portal.opengeospatial.org/files/?artifact_id=51842","type":"PER","creator":"George Percivall","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-02-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"449":{"title":"OWS-9 Aviation Portrayal Engineering Report","alternative":"OWS-9 Aviation Portrayal Engineering Report","URI":null,"identifier":"12-151","URL":"https://portal.opengeospatial.org/files/?artifact_id=51898","type":"PER","creator":"Daniel Balog, Roger Brackin, Robin Houtmeyers","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-02-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"450":{"title":"OWS-9 Aviation Architecture Engineering Report","alternative":"OWS-9 Aviation Architecture Engineering Report","URI":null,"identifier":"12-147","URL":"https://portal.opengeospatial.org/files/?artifact_id=51823","type":"PER","creator":"Claude Speed","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-02-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"451":{"title":"OWS-9 Security Engineering Report ","alternative":"OWS-9 Security Engineering Report ","URI":null,"identifier":"12-118","URL":"https://portal.opengeospatial.org/files/?artifact_id=51806","type":"PER","creator":"Andreas Matheus","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-02-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"452":{"title":"OWS-9 Aviation: AIRM Derivation","alternative":"OWS-9 Aviation: AIRM Derivation","URI":null,"identifier":"12-094","URL":"https://portal.opengeospatial.org/files/?artifact_id=51807","type":"PER","creator":"Debbie Wilson, Clemens Portele","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-02-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"453":{"title":"OWS-9 CCI Conflation with Provenance Engineering Report","alternative":"OWS-9 CCI Conflation with Provenance Engineering Report","URI":null,"identifier":"12-159","URL":"https://portal.opengeospatial.org/files/?artifact_id=51818","type":"PER","creator":"Matthes Rieke, Benjamin Pross","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-02-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"454":{"title":"OWS-9 OWS Innovations GMLJP2 for National Imagery Transmission Format (NITF) Engineering Report ","alternative":"OWS-9 OWS Innovations GMLJP2 for National Imagery Transmission Format (NITF) Engineering Report ","URI":null,"identifier":"12-154","URL":"https://portal.opengeospatial.org/files/?artifact_id=51889","type":"PER","creator":"Darko Androsevic","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-02-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"455":{"title":"OWS-9 CCI Semantic Mediation Engineering Report","alternative":"OWS-9 CCI Semantic Mediation Engineering Report","URI":null,"identifier":"12-103r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=51840","type":"PER","creator":"Gobe Hobona, Roger Brackin","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-02-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"456":{"title":"OWS-9: UML-to-GML-Application-Schema (UGAS) Conversion Engineering Report","alternative":"OWS-9: UML-to-GML-Application-Schema (UGAS) Conversion Engineering Report","URI":null,"identifier":"12-093","URL":"https://portal.opengeospatial.org/files/?artifact_id=51784","type":"PER","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-02-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"457":{"title":"OWS-9: SSI Security Rules Service Engineering Report","alternative":"OWS-9: SSI Security Rules Service Engineering Report","URI":null,"identifier":"12-139","URL":"https://portal.opengeospatial.org/files/?artifact_id=51833","type":"PER","creator":"Jan Herrmann, Andreas Matheus","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-02-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"458":{"title":"OWS-9: Engineering Report: Use of SWE Common and SensorML for GPS Messaging ","alternative":"OWS-9: Engineering Report: Use of SWE Common and SensorML for GPS Messaging ","URI":null,"identifier":"12-096","URL":"https://portal.opengeospatial.org/files/?artifact_id=52162","type":"PER","creator":"Mike Botts","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-02-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"459":{"title":"OWS-9: OGC Mobile Apps: Definition, Requirements, and Information Architecture","alternative":"OWS-9: OGC Mobile Apps: Definition, Requirements, and Information Architecture","URI":null,"identifier":"12-119r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=52272","type":"PER","creator":"Ingo Simonis","contributor":null,"description":"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)","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-02-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"460":{"title":"NetCDF Uncertainty Conventions ","alternative":"NetCDF Uncertainty Conventions ","URI":null,"identifier":"11-163","URL":"https://portal.opengeospatial.org/files/?artifact_id=46702","type":"DP","creator":"Lorenzo Bigagli, StefanoNativi","contributor":null,"description":"This Discussion Paperproposes a set of conventions for managing uncertainty information within the netCDF3 data model and format: the NetCDF Uncertainty Conventions (NetCDF-U).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-01-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"461":{"title":"CF-netCDF3 Data Model Extension standard","alternative":"CF-netCDF3 Data Model Extension standard","URI":null,"identifier":"11-165r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=51908","type":"IS","creator":"Ben Domenico and Stefano Nativi ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2013-01-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"462":{"title":"OGC Standard for Moving Features; Requirements","alternative":"OGC Standard for Moving Features; Requirements","URI":null,"identifier":"12-117r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=51623","type":"DP","creator":"Ryosuke Shibasaki","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-12-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"463":{"title":"A Primer for Dissemination Services for Wide Area Motion Imagery ","alternative":"A Primer for Dissemination Services for Wide Area Motion Imagery ","URI":null,"identifier":"12-077r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=50485","type":"Primer","creator":"Rahul Thakkar","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-12-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"464":{"title":"WAMI Services: Dissemination Services for Wide Area Motion Imagery - Best Practice","alternative":"WAMI Services: Dissemination Services for Wide Area Motion Imagery - Best Practice","URI":null,"identifier":"12-032r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=50486","type":"BP","creator":"Rahul Thakkar, Michael Maraist","contributor":null,"description":"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.opengeospatial.org/files/?artifact_id=50485>WAMI - Primer</a> has been developed to help you implement this Best Practice.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-12-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"465":{"title":"OpenGIS Catalogue Service Implementation Specification","alternative":"Catalogue Service Implementation Specification","URI":null,"identifier":"04-021r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=5929","type":"D-IS","creator":"Doug Nebert","contributor":null,"description":"The OpenGIS Catalogue Services Specification defines common interfaces to discover, browse, and query metadata about data, services, and other potential resources.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-08-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"466":{"title":"OpenGIS Catalogue Service Implementation Specification","alternative":"Catalogue Service Implementation Specification","URI":null,"identifier":"07-006r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=20555","type":"IS","creator":"Nebert, Whiteside, Vretanos, editors","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-04-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"467":{"title":"Filter Encoding Implementation Specification Corrigendum 1","alternative":"Filter Encoding Implementation Specification Corrigendum 1","URI":null,"identifier":"04-095c1","URL":"https://portal.opengeospatial.org/files/?artifact_id=51130","type":"D-IS","creator":"Peter Vretanos","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-05-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"468":{"title":"Semantic annotations in OGC standards","alternative":"Semantic annotations in OGC standards","URI":null,"identifier":"08-167r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=47857","type":"BP","creator":"Frédéric Houbie, Philippe Duchesne, Patrick Maué","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-10-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"469":{"title":"OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard","alternative":"OGC Network Common Data Form (NetCDF) NetCDF Enhanced Data Model Extension Standard","URI":null,"identifier":"11-038R2","URL":"https://portal.opengeospatial.org/files/?artifact_id=50294","type":"IS","creator":"Ben Domenico","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-10-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"470":{"title":"OGC® WaterML 2.0: Part 1- Timeseries","alternative":"WaterML 2.0: Part 1- Timeseries","URI":null,"identifier":"10-126r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=48531","type":"D-IS","creator":"Peter Taylor","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-08-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"471":{"title":"OGC® Surface Water Interoperability Experiment FINAL REPORT ","alternative":"Surface Water Interoperability Experiment FINAL REPORT ","URI":null,"identifier":"12-018r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=50166","type":"PER","creator":"Peter Fitch","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-08-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"472":{"title":"OGC 3D Portrayal Interoperability Experiment  FINAL REPORT ","alternative":"3D Portrayal Interoperability Experiment  FINAL REPORT ","URI":null,"identifier":"12-075","URL":"https://portal.opengeospatial.org/files/?artifact_id=49068","type":"PER","creator":"Arne Schilling, Benjamin Hagedorn, Volker Coors ","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-08-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"473":{"title":"OGC WCS 2.0.1 Corrigendum Release Notes","alternative":"WCS 2.0.1 Corrigendum Release Notes","URI":null,"identifier":"12-052","URL":"https://portal.opengeospatial.org/files/?artifact_id=48650","type":"Notes","creator":"Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-07-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"474":{"title":"OGC® WCS 2.0 Interface Standard- Core:  Corrigendum ","alternative":"WCS 2.0 Interface Standard- Core:  Corrigendum ","URI":null,"identifier":"09-110r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=48428","type":"IS","creator":"Peter Baumann","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-07-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"475":{"title":"WaterML 2.0 - Timeseries - NetCDF Discussion Paper","alternative":"WaterML 2.0 - Timeseries - NetCDF Discussion Paper","URI":null,"identifier":"12-031r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=49025","type":"DP","creator":"Doug Palmer","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-07-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"476":{"title":"Modeling an application domain extension of CityGML in UML","alternative":"Modeling an application domain extension of CityGML in UML","URI":null,"identifier":"12-066","URL":"https://portal.opengeospatial.org/files/?artifact_id=49000&version=2","type":"D-DP","creator":"Linda van den Brink, Jantien Stoter, Sisi Zlatanova","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-07-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"477":{"title":"Cataloguing Earth Observation Products for ebXML Registry Information Model 3.0 based Catalogues","alternative":"Cataloguing Earth Observation Products for ebXML Registry Information Model 3.0 based Catalogues","URI":null,"identifier":"10-189r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=47409","type":"BP","creator":"Frédéric Houbie; Fabian Skivee","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-06-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"478":{"title":"Earth Observation Metadata profile of Observations & Measurements","alternative":"Earth Observation Metadata profile of Observations & Measurements","URI":null,"identifier":"10-157r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=47040","type":"D-IS","creator":"Jerome Gasperi, Frédéric Houbie, Andrew Woolf, Steven Smolders","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-06-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"479":{"title":"OGC GeoSPARQL - A Geographic Query Language for RDF Data","alternative":"GeoSPARQL - A Geographic Query Language for RDF Data","URI":null,"identifier":"11-052r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=47664","type":"IS","creator":"Matthew Perry and John Herring","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-06-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"480":{"title":"Guidance and Profile of GML for use with Aviation Data","alternative":"Guidance and Profile of GML for use with Aviation Data","URI":null,"identifier":"12-028","URL":"https://portal.opengeospatial.org/files/?artifact_id=47859","type":"D-DP","creator":"OGC Aviation Domain Working Group","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-05-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"481":{"title":"Surface Water Interoperability Experiment FINAL REPORT","alternative":"Surface Water Interoperability Experiment FINAL REPORT","URI":null,"identifier":"12-018r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=47989","type":"PER","creator":"Peter Fitch","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-05-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"482":{"title":"OWS-8 Tracking: Moving Target Indicator Process, Workflows and Implementation Results ER","alternative":"OWS-8 Tracking: Moving Target Indicator Process, Workflows and Implementation Results ER","URI":null,"identifier":"11-134","URL":"https://portal.opengeospatial.org/files/?artifact_id=46372","type":"PER","creator":"Rob Cass, Mark Simms","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-05-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"483":{"title":"OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report)","alternative":"OWS-8 Analysis of OGC Standards for Supporting Mobile Object Processing Implementation (Engineering Report)","URI":null,"identifier":"11-108","URL":"https://portal.opengeospatial.org/files/?artifact_id=46170","type":"PER","creator":"Ingo Simonis","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-05-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"484":{"title":"OGC® Coverage Implementation Schema","alternative":"Coverage Implementation Schema","URI":null,"identifier":"09-146r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=48553","type":"SAP","creator":"Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-05-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"485":{"title":"Simple Features - SQL - Types and Functions","alternative":"Simple Features - SQL - Types and Functions","URI":null,"identifier":"06-104r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=25354","type":"CC","creator":"John Herring","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"486":{"title":"Simple Features - SQL - Normalized Geometry ","alternative":"Simple Features - SQL - Normalized Geometry ","URI":null,"identifier":"06-104r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=25354","type":"CC","creator":"John Herring","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"487":{"title":"Simple Features - SQL - Binary Geometry","alternative":"Simple Features - SQL - Binary Geometry","URI":null,"identifier":"06-104r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=25354","type":"CC","creator":"John Herring","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"488":{"title":"OGC® Sensor Observation Service Interface Standard","alternative":"Sensor Observation Service Interface Standard","URI":null,"identifier":"12-006","URL":"https://portal.opengeospatial.org/files/?artifact_id=47599","type":"IS","creator":"Arne Bröring, Christoph Stasch, Johannes Echterhoff","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-04-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"489":{"title":"OGC® Engineering Report for the OWS Shibboleth Interoperability Experiment","alternative":"Engineering Report for the OWS Shibboleth Interoperability Experiment","URI":null,"identifier":"11-019r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=47852","type":"PER","creator":"Chris Higgins","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-04-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"490":{"title":"HY_Features: a Common Hydrologic Feature Model Discussion Paper","alternative":"HY_Features: a Common Hydrologic Feature Model Discussion Paper","URI":null,"identifier":"11-039r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=47831","type":"D-DP","creator":"Rob Atkinson, Irina Dornblut","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-04-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"491":{"title":"OGC City Geography Markup Language (CityGML) Encoding Standard","alternative":"City Geography Markup Language (CityGML) Encoding Standard","URI":null,"identifier":"12-019","URL":"https://portal.opengeospatial.org/files/?artifact_id=47842","type":"IS","creator":"Gerhard Gröger, Thomas H. Kolbe, Claus Nagel, Karl-Heinz Häfele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-04-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"492":{"title":"OWS-8 Report on Digital NOTAM Event Specification","alternative":"OWS-8 Report on Digital NOTAM Event Specification","URI":null,"identifier":"11-092r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=46243","type":"PER","creator":"Johannes Echterhoff, Matthes Rieke","contributor":null,"description":"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:  <a href=http://dp.schemas.opengis.net/11-092r2>http://dp.schemas.opengis.net/11-092r2</a>","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-04-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"493":{"title":"Web Processing Service Best Practices Discussion Paper","alternative":"Web Processing Service Best Practices Discussion Paper","URI":null,"identifier":"12-029","URL":"https://portal.opengeospatial.org/files/?artifact_id=47860","type":"DP","creator":"Bastian Schäffer","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-04-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"494":{"title":"Topic 19: Geographic information - Linear referencing","alternative":"Topic 19: Geographic information - Linear referencing","URI":null,"identifier":"10-030","URL":"https://www.iso.org/standard/32566.html","type":"AS","creator":"Paul Scarponcini","contributor":null,"description":"Same as ISO IS 19148: 2012.  Download at http://www.iso.org","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-03-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"495":{"title":"Gazetteer Service - Application Profile of the Web Feature Service Best Practice","alternative":"Gazetteer Service - Application Profile of the Web Feature Service Best Practice","URI":null,"identifier":"11-122r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=46964","type":"BP","creator":"Panagiotis (Peter) A. Vretanos, Jeff Harrison","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-02-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"496":{"title":"OWS-8 Review of the WXXS exchange schemas","alternative":"OWS-8 Review of the WXXS exchange schemas","URI":null,"identifier":"11-091","URL":"https://portal.opengeospatial.org/files/?artifact_id=46094","type":"PER","creator":"Richard Martell","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-02-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"497":{"title":"OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0","alternative":"OWS-8 Aviation: Guidance for Retrieving AIXM 5.1 data via an OGC WFS 2.0","URI":null,"identifier":"11-073r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=46666","type":"PER","creator":"Debbie Wilson, Ian Painter ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-02-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"498":{"title":"OWS-8 AIXM Metadata Guidelines Engineering Report","alternative":"OWS-8 AIXM Metadata Guidelines Engineering Report","URI":null,"identifier":"11-061r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=45380","type":"PER","creator":"David Burggraf","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-02-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"499":{"title":"OGC® Geography Markup Language (GML) - Extended schemas and encoding rules","alternative":"Geography Markup Language (GML) - Extended schemas and encoding rules","URI":null,"identifier":"10-129r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=46568","type":"IS","creator":"Clemens Portele","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-02-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"500":{"title":"OWS-8 Aviation Thread - Authoritative AIXM Data Source Engineering Report","alternative":"OWS-8 Aviation Thread - Authoritative AIXM Data Source Engineering Report","URI":null,"identifier":"11-086r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=46019","type":"PER","creator":"Jan Herrmann, Andreas Matheus","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-01-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"501":{"title":"OWS-8 Aviation - WXXM Engineering Report","alternative":"OWS-8 Aviation - WXXM Engineering Report","URI":null,"identifier":"11-072r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=46322","type":"PER","creator":"Wenny Rahayu, Torab Torabi, Andrew Taylor-Harris, Florian Puersch","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-01-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"502":{"title":"Ordering Services for Earth Observation Products  Adoption Voting Comments and Answers","alternative":"Ordering Services for Earth Observation Products  Adoption Voting Comments and Answers","URI":null,"identifier":"11-111","URL":"https://portal.opengeospatial.org/files/?artifact_id=45124","type":"Notes","creator":"Daniele Marchionni","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-01-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"503":{"title":"OGC® Web Coverage Service 2.0 Primer:  Core and Extensions Overview","alternative":"Web Coverage Service 2.0 Primer:  Core and Extensions Overview","URI":null,"identifier":"09-153r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=46442","type":"BP","creator":"Peter Baumann","contributor":null,"description":"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 &quot;living document&quot; 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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-01-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"504":{"title":"OGC® PUCK Protocol Standard ","alternative":"OGC® PUCK Protocol Standard ","URI":null,"identifier":"09-127r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=47604","type":"IS","creator":"Tom O’Reilly ","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-01-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"505":{"title":"OGC®: Open GeoSMS Standard - Core","alternative":"Open GeoSMS Standard - Core","URI":null,"identifier":"11-030r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=44146","type":"IS","creator":"Kuan-Mei Chen, Carl Reed","contributor":null,"description":"The OpenGIS® Open GeoSMS standard defines an encoding for location enabling a text message to be communicated using a Short Messages System (SMS). ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-01-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"506":{"title":"Ordering Services Framework for Earth Observation Products  Interface Standard","alternative":"Ordering Services Framework for Earth Observation Products  Interface Standard","URI":null,"identifier":"06-141r6","URL":"https://portal.opengeospatial.org/files/?artifact_id=43928","type":"IS","creator":"Daniele Marchionni, Stefania Pappagallo ","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2012-01-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"507":{"title":"OGC Reference Model","alternative":"OGC Reference Model","URI":null,"identifier":"08-062r7","URL":"https://portal.opengeospatial.org/files/?artifact_id=47245","type":"ORM","creator":"George Percivall","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"508":{"title":"OWS-8 Aviation Architecture Engineering Report","alternative":"OWS-8 Aviation Architecture Engineering Report","URI":null,"identifier":"11-093r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=46242","type":"PER","creator":"Johannes Echterhoff","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"509":{"title":"OWS-8 WCS 2.0 Earth Observation Application Profile Compliance Tests Engineering Report","alternative":"OWS-8 WCS 2.0 Earth Observation Application Profile Compliance Tests Engineering Report","URI":null,"identifier":"11-095r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=47826","type":"PER","creator":"Stephan Meissl, Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"510":{"title":"OWS-8 AIXM 5.1 Compression Benchmarking","alternative":"OWS-8 AIXM 5.1 Compression Benchmarking","URI":null,"identifier":"11-097","URL":"https://portal.opengeospatial.org/files/?artifact_id=46394","type":"PER","creator":"Jérôme JANSOU, Thibault DACLA","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"511":{"title":"OWS-8 Digital NOTAM Refactor","alternative":"OWS-8 Digital NOTAM Refactor","URI":null,"identifier":"11-106r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=46227","type":"PER","creator":"Rob Atkinson, James Groffen","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"512":{"title":"OWS-8 Geoprocessing for Earth Observations Engineering Report","alternative":"OWS-8 Geoprocessing for Earth Observations Engineering Report","URI":null,"identifier":"11-116","URL":"https://portal.opengeospatial.org/files/?artifact_id=46793","type":"PER","creator":"Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"513":{"title":"Summary of the OGC Web Services, Phase 8 (OWS-8) Interoperability Testbed","alternative":"Summary of the OGC Web Services, Phase 8 (OWS-8) Interoperability Testbed","URI":null,"identifier":"11-139r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=47018","type":"PER","creator":"David Arctur","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"514":{"title":"Lightweight SOS Profile for Stationary In-Situ Sensors Discussion Paper","alternative":"Lightweight SOS Profile for Stationary In-Situ Sensors Discussion Paper","URI":null,"identifier":"11-169","URL":"https://portal.opengeospatial.org/files/?artifact_id=46693","type":"D-DP","creator":"Simon Jirka, Christoph Stasch, Arne Bröring","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-12-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"515":{"title":"Gazetteer Service - Application Profile of the Web Feature Service Candidate Implementation Standard","alternative":"Gazetteer Service - Application Profile of the Web Feature Service Candidate Implementation Standard","URI":null,"identifier":"11-122r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=46964","type":"D-RFC","creator":"Jeff Harrison, Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-11-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"516":{"title":"WS-Agreement Application Profile for OGC Web Services","alternative":"WS-Agreement Application Profile for OGC Web Services","URI":null,"identifier":"11-094","URL":"https://portal.opengeospatial.org/files/?artifact_id=45403","type":"DP","creator":"Bastian Baranski","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-11-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"517":{"title":"OGC® Event Service - Review and Current State","alternative":"Event Service - Review and Current State","URI":null,"identifier":"11-088r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=45850","type":"DP","creator":"Johannes Echterhoff, Thomas Everding","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-11-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"518":{"title":"OWS-8 Information Model for Moving Target Indicators and Moving Object Bookmarks (Engineering Report)","alternative":"OWS-8 Information Model for Moving Target Indicators and Moving Object Bookmarks (Engineering Report)","URI":null,"identifier":"11-113r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=46171","type":"PER","creator":"Ingo Simonis","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-11-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"519":{"title":"OWS-8 Engineering Report - Guidelines for International Civil Aviation Organization (ICAO) portrayal using SLD/SE","alternative":"OWS-8 Engineering Report - Guidelines for International Civil Aviation Organization (ICAO) portrayal using SLD/SE","URI":null,"identifier":"11-089r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=46228","type":"PER","creator":"Daniel Tagesson","contributor":null,"description":"This OGC® document gives guidelines to portrayal of AIXM according to ICAO aviation symbology using SLD/SE. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-11-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"520":{"title":"OWS-8 WCS 2.0 Earth Observation Application Profile Engineering Report","alternative":"OWS-8 WCS 2.0 Earth Observation Application Profile Engineering Report","URI":null,"identifier":"11-096","URL":"https://portal.opengeospatial.org/files/?artifact_id=45404","type":"PER","creator":"Stephan Meissl, Peter Baumann","contributor":null,"description":"This Engineering Report describes progress on EO-WCS in the course of OWS-8.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-11-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"521":{"title":"OWS-8 CCI Schema Automation Engineering Report","alternative":"OWS-8 CCI Schema Automation Engineering Report","URI":null,"identifier":"11-064r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=46324","type":"PER","creator":"Clemens Portele, Reinhard Erstling","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-11-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"522":{"title":"OWS-8 Cross Community Interoperability (CCI) Semantic Mediation Engineering Report","alternative":"OWS-8 Cross Community Interoperability (CCI) Semantic Mediation Engineering Report","URI":null,"identifier":"11-063r6","URL":"https://portal.opengeospatial.org/files/?artifact_id=46342","type":"PER","creator":"Gobe Hobona, Roger Brackin","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-11-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"523":{"title":"OGC SAA Pilot Study Engineering Report","alternative":"OGC SAA Pilot Study Engineering Report","URI":null,"identifier":"11-055","URL":"https://portal.opengeospatial.org/files/?artifact_id=44939","type":"PER","creator":"Steve Miller","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-11-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"524":{"title":"OWS-8 CCI Portrayal Registries Engineering Report","alternative":"OWS-8 CCI Portrayal Registries Engineering Report","URI":null,"identifier":"11-062r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=46548","type":"PER","creator":"David Burggraf, Ron Lake","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-11-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"525":{"title":"OWS-8 Bulk Geodata Transfer with File Geodatabase","alternative":"OWS-8 Bulk Geodata Transfer with File Geodatabase","URI":null,"identifier":"11-114","URL":"https://portal.opengeospatial.org/files/?artifact_id=45754","type":"PER","creator":"David Danko, Lance Shipman, Paul Ramsey","contributor":null,"description":"This document provides an overview of the File Geodatabase  API and documents the testing performed in the OWS 8 Testbed.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-11-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"526":{"title":"OWS-8 Bulk Geodata Transfer Using GML Engineering Report","alternative":"OWS-8 Bulk Geodata Transfer Using GML Engineering Report","URI":null,"identifier":"11-085r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=46679","type":"PER","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-11-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"527":{"title":"Corrigendum 1 for OGC Web Services Common Standard v2.0.0 - Multilingual","alternative":"Corrigendum 1 for OGC Web Services Common Standard v2.0.0 - Multilingual","URI":null,"identifier":"11-157","URL":"https://portal.opengeospatial.org/files/?artifact_id=46435","type":"ISC","creator":"Jim Greenwood","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-10-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"528":{"title":"Corrigendum 2 for OGC Web Services Common Specification v 1.1.0 - Exception Report","alternative":"Corrigendum 2 for OGC Web Services Common Specification v 1.1.0 - Exception Report","URI":null,"identifier":"11-158","URL":"https://portal.opengeospatial.org/files/?artifact_id=46436","type":"ISC","creator":"Jim Greenwood","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-10-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"529":{"title":"OGC® Engineering Report: Water Information Services Concept Development Study","alternative":"Water Information Services Concept Development Study","URI":null,"identifier":"11-013r6","URL":"https://portal.opengeospatial.org/files/?artifact_id=44834","type":"PER","creator":"Luis Bermudez, David Arctur","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-07-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"530":{"title":"*FL Starfish Fungus Language for Sensor Description ","alternative":"*FL Starfish Fungus Language for Sensor Description","URI":null,"identifier":"11-058r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=44438","type":"DP","creator":"Ingo Simonis, Chrsitian Malewski","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-07-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"531":{"title":"Geospatial eXtensible Access Control Markup Language (GeoXACML) Version 1 Corrigendum","alternative":"Geospatial eXtensible Access Control Markup Language (GeoXACML) Version 1 Corrigendum","URI":null,"identifier":"11-017","URL":"https://portal.opengeospatial.org/files/?artifact_id=42734","type":"IS","creator":"Andreas Matheus, Jan Herrmann","contributor":null,"description":"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]). ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-05-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"532":{"title":"OGC Geography Markup Language (GML) simple features profile Technical Note","alternative":"OGC Geography Markup Language (GML) simple features profile Technical Note","URI":null,"identifier":"11-044","URL":"https://portal.opengeospatial.org/files/?artifact_id=43999","type":"Notes","creator":"Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-05-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"533":{"title":"Geography Markup Language (GML) simple features profile (with Corrigendum)","alternative":"Geography Markup Language (GML) simple features profile (with Corrigendum)","URI":null,"identifier":"10-100r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=42729","type":"Profile","creator":"Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-05-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"534":{"title":"GeoAPI 3.0 Implementation Standard","alternative":"GeoAPI 3.0 Implementation Standard","URI":null,"identifier":"09-083r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=39397","type":"IS","creator":"Adrian Custer","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-04-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"535":{"title":"NetCDF Binary Encoding Extension Standard: NetCDF Classic and 64-bit Offset Format","alternative":"NetCDF Binary Encoding Extension Standard: NetCDF Classic and 64-bit Offset Format","URI":null,"identifier":"10-092r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=43734","type":"ISx","creator":"Ben Domenico","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-04-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"536":{"title":"CF-netCDF Core and Extensions Primer","alternative":"CF-netCDF Core and Extensions Primer","URI":null,"identifier":"10-091r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=43733","type":"Primer","creator":"Ben Domenico","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-04-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"537":{"title":"OGC Network Common Data Form (NetCDF)  Core Encoding Standard version 1.0","alternative":"Network Common Data Form (NetCDF)  Core Encoding Standard version 1.0","URI":null,"identifier":"10-090r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=43732","type":"IS","creator":"Ben Domenico","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-04-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"538":{"title":"License-Based Access Control","alternative":"License-Based Access Control","URI":null,"identifier":"11-018","URL":"https://portal.opengeospatial.org/files/?artifact_id=42735","type":"DP","creator":"Rüdiger Gartmann, Bastian Schäffer","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-03-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"539":{"title":"OGC® Sensor Planning Service Interface Standard 2.0 Earth Observation Satellite Tasking ExtensionOGC® Sensor Planning Service","alternative":"Earth Observation Satellite Tasking Extension for SPS 2.0","URI":null,"identifier":"10-135","URL":"https://portal.opengeospatial.org/files/?artifact_id=40185","type":"ISx","creator":"Alexandre Robin, Philippe Mérigot","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-03-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"540":{"title":"Guidance on the Aviation Metadata Profile","alternative":"Guidance on the Aviation Metadata Profile","URI":null,"identifier":"10-196r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=41668","type":"DP","creator":"OGC Aviation Domain Working Group","contributor":null,"description":"This paper explains how to map the Requirements for Aviation Metadata into a metadata profile.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-03-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"541":{"title":"Requirements for Aviation Metadata","alternative":"Requirements for Aviation Metadata","URI":null,"identifier":"10-195","URL":"https://portal.opengeospatial.org/files/?artifact_id=41667","type":"DP","creator":"OGC Aviation Domain Working Group","contributor":null,"description":"This OGC Discussion Paper details the user requirements for metadata in the aviation domain. The requirements are at a high-level.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-03-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"542":{"title":"OGC® Sensor Planning Service Implementation Standard","alternative":"Sensor Planning Service Implementation Standard","URI":null,"identifier":"09-000","URL":"https://portal.opengeospatial.org/files/?artifact_id=38478","type":"IS","creator":"Ingo Simonis, Johannes Echterhoff","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-03-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"543":{"title":"Observations and Measurements - XML Implementation","alternative":"Observations and Measurements - XML Implementation","URI":null,"identifier":"10-025r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=41510","type":"IS","creator":"Simon Cox","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-03-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"544":{"title":"OpenGIS® SWE Service Model Implementation Standard","alternative":"SWE Service Model Implementation Standard","URI":null,"identifier":"09-001","URL":"https://portal.opengeospatial.org/files/?artifact_id=38476","type":"IS","creator":"Johannes Echterhoff","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-03-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"545":{"title":"OpenGIS Web Feature Service (WFS) Implementation Specification (Transactional)","alternative":"Web Feature Service (WFS) Implementation Specification (Transactional)","URI":null,"identifier":"04-094","URL":"https://portal.opengeospatial.org/files/?artifact_id=8339","type":"CC","creator":"Peter Vretanos","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-05-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"546":{"title":"Ocean Science Interoperability Experiment Phase II Report ","alternative":"Ocean Science Interoperability Experiment Phase II Report ","URI":null,"identifier":"09-156r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=37373","type":"PER","creator":"Luis Bermudez","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-01-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"547":{"title":"OGC® SWE Common Data Model Encoding Standard","alternative":"SWE Common Data Model Encoding Standard","URI":null,"identifier":"08-094r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=41157","type":"IS","creator":"Alexandre Robin","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-01-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"548":{"title":"Authentication IE Enginerring Report ","alternative":"Authentication IE Enginerring Report ","URI":null,"identifier":"10-192","URL":"https://portal.opengeospatial.org/files/?artifact_id=41734","type":"PER","creator":"Jeff Harrison","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-01-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"549":{"title":"Ocean Science Interoperability Experiment Phase 1 Report","alternative":"Ocean Science Interoperability Experiment Phase 1 Report ","URI":null,"identifier":"08-124r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=29535","type":"PER","creator":"Luis Bermudez","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-01-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"550":{"title":"OGC Fusion Standards Study, Phase 2 Engineering Report","alternative":"OGC Fusion Standards Study, Phase 2 Engineering Report","URI":null,"identifier":"10-184","URL":"https://portal.opengeospatial.org/files/?artifact_id=41573","type":"PER","creator":"George Percivall","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-12-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"551":{"title":"Requirements and Space-Event Modeling for Indoor Navigation","alternative":"Requirements and Space-Event Modeling for Indoor Navigation","URI":null,"identifier":"10-191r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=41727","type":"DP","creator":"Claus Nagel, Thomas Becker, Robert Kaden, Ki-Joune Li, Jiyeong Lee, Thomas H. Kolbe","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-12-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"552":{"title":"OpenGIS® Georeferenced Table Joining Service Implementation Standard","alternative":"Georeferenced Table Joining Service Implementation Standard","URI":null,"identifier":"10-070r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=40095","type":"IS","creator":"Peter Schut","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-11-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"553":{"title":"OpenGIS Filter Encoding 2.0 Encoding Standard","alternative":"Filter Encoding 2.0 Encoding Standard","URI":null,"identifier":"09-026r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=39968","type":"IS","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-11-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"554":{"title":"Topic 20: Observations and Measurements","alternative":"Topic 20: Observations and Measurements","URI":null,"identifier":"10-004r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=41579","type":"AS","creator":"Simon Cox","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-11-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"555":{"title":"OpenGIS Web Feature Service 2.0 Interface Standard (also ISO 19142)","alternative":"Web Feature Service 2.0 Interface Standard (also ISO 19142)","URI":null,"identifier":"09-025r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=39967","type":"D-IS","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-11-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"556":{"title":"OGC® Web Coverage Service 2.0 Interface Standard - XML/SOAP Protocol Binding Extension","alternative":"Web Coverage Service 2.0 Interface Standard - XML/SOAP Protocol Binding Extension","URI":null,"identifier":"09-149r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=41441","type":"IS","creator":"Peter Baumann","contributor":null,"description":"This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using SOAP with XML encoding.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-10-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"557":{"title":"OGC® Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension","alternative":"Web Coverage Service 2.0 Interface Standard - XML/POST Protocol Binding Extension","URI":null,"identifier":"09-148r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=41440","type":"IS","creator":"Peter Baumann","contributor":null,"description":"This document specifies how Web Coverage Service (WCS) clients and servers can commu-nicate over the Internet using HTTP POST with XML encoding.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-10-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"558":{"title":"OGC® Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension","alternative":"Web Coverage Service 2.0 Interface Standard - KVP Protocol Binding Extension","URI":null,"identifier":"09-147r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=41439","type":"D-IS","creator":"Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-10-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"559":{"title":"OGC® GML Application Schema - Coverages","alternative":"GML Application Schema - Coverages","URI":null,"identifier":"09-146r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=41438","type":"D-SAP","creator":"Peter Baumann","contributor":null,"description":"This document specifies the GML coverage structure to be used by OGC standards.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-10-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"560":{"title":"OGC® WCS 2.0 Interface Standard - Core","alternative":"WCS 2.0 Interface Standard - Core","URI":null,"identifier":"09-110r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=41437","type":"D-IS","creator":"Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-10-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"561":{"title":"OWS-7: Summary of the  OGC Web Services, Phase 7 (OWS-7) Interoperability Testbed","alternative":"OWS-7: Summary of the  OGC Web Services, Phase 7 (OWS-7) Interoperability Testbed","URI":null,"identifier":"10-094","URL":"https://portal.opengeospatial.org/files/?artifact_id=40840","type":"PER","creator":"David Arctur","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-10-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"562":{"title":"Sensor Observable Registry (SOR) Discussion Paper","alternative":"Sensor Observable Registry (SOR) Discussion Paper","URI":null,"identifier":"09-112r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=40571","type":"DP","creator":"Simon Jirka, Arne Bröring, Daniel Nüst","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-10-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"563":{"title":"Sensor Instance Registry Discussion Paper ","alternative":"Sensor Instance Registry Discussion Paper ","URI":null,"identifier":"10-171","URL":"https://portal.opengeospatial.org/files/?artifact_id=40609","type":"DP","creator":"Simon Jirka, Daniel Nüst","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-10-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"564":{"title":"Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0","alternative":"Revision Notes for OpenGIS® Implementation Specification: Geography Markup Language (GML) simple features profile v2.0","URI":null,"identifier":"10-099r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=39852","type":"Notes","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"This document provides revision notes for version 2.0 of the OpenGIS® Implementation Specification Geography Markup Language (GML) simple feature profile.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-10-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"565":{"title":"Geography Markup Language (GML) simple features profile","alternative":"Geography Markup Language (GML) simple features profile","URI":null,"identifier":"10-100r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=39853","type":"D-Profile","creator":"Linda van den Brink, Clemens Portele, Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-10-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"566":{"title":"OWS-7 Aviation Architecture Engineering Report","alternative":"OWS-7 Aviation Architecture Engineering Report","URI":null,"identifier":"10-079r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=40133","type":"PER","creator":"Thomas Everding","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-09-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"567":{"title":"OWS-7 Information Sharing Engineering Report","alternative":"OWS-7 Information Sharing Engineering Report","URI":null,"identifier":"10-035r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=40441","type":"PER","creator":"David Rosinger, Stan Tillman","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-09-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"568":{"title":"User Management for Earth Observation Services","alternative":"User Management for Earth Observation Services","URI":null,"identifier":"07-118r8","URL":"https://portal.opengeospatial.org/files/?artifact_id=40677","type":"BP","creator":"P Denis","contributor":null,"description":"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]). ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-09-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"569":{"title":"OWS-7 Motion Video Change Detection","alternative":"OWS-7 Motion Video Change Detection","URI":null,"identifier":"10-036r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=40313","type":"PER","creator":"Stan Tillman","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"570":{"title":"OWS-7 Web Processing Service Profiling Engineering Report","alternative":"OWS-7 Web Processing Service Profiling Engineering Report","URI":null,"identifier":"10-059r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=40310","type":"PER","creator":"Christian Kiehle, Theodor Foerster","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"571":{"title":"OWS-7 Feature and Statistical Analysis Engineering Report","alternative":"OWS-7 Feature and Statistical Analysis Engineering Report","URI":null,"identifier":"10-074","URL":"https://portal.opengeospatial.org/files/?artifact_id=40311","type":"PER","creator":"Theodor Foerster, Bastian Schäffer","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"572":{"title":"OWS-7 - Authoritative Data Source Directory Engineering Report","alternative":"OWS-7 - Authoritative Data Source Directory Engineering Report","URI":null,"identifier":"10-086r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=40334","type":"PER","creator":"Andrew Turner","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"573":{"title":"OWS-7 Motion Imagery Discovery and Retrieval  Engineering Report","alternative":"OWS-7 Motion Imagery Discovery and Retrieval  Engineering Report","URI":null,"identifier":"10-087","URL":"https://portal.opengeospatial.org/files/?artifact_id=40139","type":"PER","creator":"Wenli Yang, Liping Di","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"574":{"title":"OWS-7 Engineering Report - Aviation Portrayal","alternative":"OWS-7 Engineering Report - Aviation Portrayal","URI":null,"identifier":"10-127r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=40134","type":"PER","creator":"Roger Brackin","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"575":{"title":"OWS-7 Aviation - FUSE Deployment Engineering Report","alternative":"OWS-7 Aviation - FUSE Deployment Engineering Report","URI":null,"identifier":"10-130","URL":"https://portal.opengeospatial.org/files/?artifact_id=40114","type":"PER","creator":"Debbie Wilson","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"576":{"title":"OWS-7 Aviation - AIXM Assessment Report","alternative":"OWS-7 Aviation - AIXM Assessment Report","URI":null,"identifier":"10-131r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=40502","type":"PER","creator":"Debbie Wilson","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"577":{"title":"OWS-7 Aviation - WXXM Assessment Engineering Report","alternative":"OWS-7 Aviation - WXXM Assessment Engineering Report","URI":null,"identifier":"10-132","URL":"https://portal.opengeospatial.org/files/?artifact_id=40149","type":"PER","creator":"Bruno Simmenauer","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"578":{"title":"OWS-7 - Towards secure interconnection of OGC Web Services with SWIM","alternative":"OWS-7 - Towards secure interconnection of OGC Web Services with SWIM","URI":null,"identifier":"10-155","URL":"https://portal.opengeospatial.org/files/?artifact_id=40144","type":"PER","creator":"Andreas Matheus","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"579":{"title":"OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option","alternative":"Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option","URI":null,"identifier":"06-104r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=25354","type":"IS","creator":"John Herring","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"580":{"title":"OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture","alternative":"Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture","URI":null,"identifier":"06-103r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=25355","type":"IS","creator":"John Herring","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-05-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"581":{"title":"OWS-7 Engineering Report  - Geosynchronization service","alternative":"OWS-7 Engineering Report - Geosynchronization service","URI":null,"identifier":"10-069r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=39476","type":"PER","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"582":{"title":"OWS-7 Event Architecture Engineering Report","alternative":"OWS-7 Event Architecture Engineering Report","URI":null,"identifier":"10-060r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=39509","type":"PER","creator":"Johannes Echterhoff","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-08-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"583":{"title":"OGC® NSG Plugweek Engineering Report","alternative":"OGC® NSG Plugweek Engineering Report","URI":null,"identifier":"09-140r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=36336","type":"PER","creator":"Paul Daisey","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-07-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"584":{"title":"Sensor Interface Descriptors","alternative":"Sensor Interface Descriptors","URI":null,"identifier":"10-134","URL":"https://portal.opengeospatial.org/files/?artifact_id=39664","type":"DP","creator":"Arne Broering, Stefan Below","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-06-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"585":{"title":"OWS-7 CCSI-SWE Best Practices Engineering Report","alternative":"OWS-7 CCSI-SWE Best Practices Engineering Report","URI":null,"identifier":"10-073r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=39728","type":"PER","creator":"Scott Fairgrieve","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-06-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"586":{"title":"OWS-7 Dynamic Sensor Notification Engineering Report","alternative":"OWS-7 Dynamic Sensor Notification Engineering Report","URI":null,"identifier":"10-061r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=39513","type":"PER","creator":"Johannes Echterhoff, Ingo Simonis","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-06-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"587":{"title":"Harmonising Standards for Water Observation Data - Discussion Paper","alternative":"Harmonising Standards for Water Observation Data - Discussion Paper ","URI":null,"identifier":"09-124r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=39090","type":"DP","creator":"Peter Taylor","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-06-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"588":{"title":"Summary of the Architecture, Engineering, Construction, Owner Operator Phase 1 (AECOO-1) Joint Testbed","alternative":"Summary of the Architecture, Engineering, Construction, Owner Operator Phase 1 (AECOO-1) Joint Testbed","URI":null,"identifier":"10-003r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=37223","type":"BP","creator":"Louis Hecht, Jr., Raj Singh","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-06-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"589":{"title":"GIGAS Methodology for comparative analysis of information and data management systems","alternative":"GIGAS Methodology for comparative analysis of information and data management systems","URI":null,"identifier":"10-028r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=39475","type":"BP","creator":"Andrea Biancalana, Pier Giorgio Marchetti, Paul Smits","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-06-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"590":{"title":"Topic 2 - Spatial referencing by coordinates","alternative":"Topic 2 - Spatial referencing by coordinates","URI":null,"identifier":"08-015r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=39049","type":"D-AS","creator":"Roger Lott","contributor":null,"description":"This document is consistent with the second edition (2007) of ISO 19111, Geographic Information - Spatial referencing by coordinates  [ISO 19111:2007]","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-04-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"591":{"title":"OGC Web Service Common Implementation Specification","alternative":"Web Service Common Implementation Specification","URI":null,"identifier":"06-121r9","URL":"https://portal.opengeospatial.org/files/?artifact_id=38867","type":"IS","creator":"Arliss Whiteside Jim Greenwood ","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-04-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"592":{"title":"OpenGIS Web Map Tile Service Implementation Standard","alternative":"Web Map Tile Service Implementation Standard","URI":null,"identifier":"07-057r7","URL":"https://portal.opengeospatial.org/files/?artifact_id=35326","type":"IS","creator":"Joan Masó, Keith Pomakis and Núria Julià","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-04-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"593":{"title":"sensorML Extension Package for ebRIM Application Profile","alternative":"sensorML Extension Package for ebRIM Application Profile","URI":null,"identifier":"09-163r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=37944","type":"DP","creator":"Fre&#769;de&#769;ric Houbie, Fabian Skive&#769;e, Simon Jirka","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-04-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"594":{"title":"SANY Fusion and Modelling Architecture","alternative":"SANY Fusion and Modelling Architecture","URI":null,"identifier":"10-001","URL":"https://portal.opengeospatial.org/files/?artifact_id=37139","type":"DP","creator":"Stuart E. Middleton","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-03-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"595":{"title":"Fusion Standards Study Engineering Report","alternative":"OGC®  Fusion Standards Study Engineering Report","URI":null,"identifier":"09-138","URL":"https://portal.opengeospatial.org/files/?artifact_id=36177","type":"PER","creator":"George Percivall","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-03-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"596":{"title":"AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report","alternative":"AIP-2 Use Cases GEOSS Architecture Implementation Pilot, Phase 2 Engineering Report","URI":null,"identifier":"09-129","URL":"https://portal.opengeospatial.org/files/?artifact_id=35634","type":"PER","creator":"Nadine Alameh","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-02-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"597":{"title":"End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2","alternative":"End to End Discovery and Access Engineering Report GEO Architecture Implementation Pilot, Phase 2","URI":null,"identifier":"09-182r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=36889","type":"PER","creator":"Josh Lieberman","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-02-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"598":{"title":"OGC® Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products","alternative":"Catalogue Services Standard 2.0 Extension Package for ebRIM Application Profile: Earth Observation Products","URI":null,"identifier":"06-131r6","URL":"https://portal.opengeospatial.org/files/?artifact_id=35528","type":"IS","creator":"Frédéric Houbie, Lorenzo Bigagli","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-02-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"599":{"title":"Technical Committee Policies and Procedures: MIME Media Types for GML","alternative":"MIME Media Types for GML","URI":null,"identifier":"09-144r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=59324","type":"POL","creator":"Clemens Portele","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-02-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"600":{"title":"OGC®: Open GeoSMS Specification","alternative":"Open GeoSMS Specification","URI":null,"identifier":"09-142r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=36261","type":"D-DP","creator":"Chun-fu Lin, Zhong-Hung Lee, Jen-Chu Liu, Kuo-Yu Chuang","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-02-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"601":{"title":"Web View Service Discussion Paper","alternative":"Web View Service Discussion Paper","URI":null,"identifier":"09-166r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=37257","type":"DP","creator":"Benjamin Hagedorn","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-02-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"602":{"title":"GML 3.1.1 Application Schema for EO products","alternative":"GML 3.1.1 Application Schema for EO products","URI":null,"identifier":"06-080r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=31065","type":"SAP","creator":"Jerome Gasperi","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-02-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"603":{"title":"Draft for Candidate OpenGIS® Web 3D Service Interface Standard","alternative":"Draft for Candidate OpenGIS® Web 3D Service Interface Standard","URI":null,"identifier":"09-104r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=36390","type":"DP","creator":"Arne Schilling, Thomas H. Kolbe","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2010-01-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"604":{"title":"GeoRM Role Model","alternative":"GeoRM Role Model","URI":null,"identifier":"09-123","URL":"https://portal.opengeospatial.org/files/?artifact_id=35516","type":"DP","creator":"Roland M. Wagner","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-10-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"605":{"title":"Sensor Observable Registry Discussion Paper","alternative":"Sensor Observable Registry Discussion Paper","URI":null,"identifier":"09-112","URL":"https://portal.opengeospatial.org/files/?artifact_id=35471","type":"DP","creator":"Simon Jirka, Arne Bröring","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-10-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"606":{"title":"CF-netCDF Encoding Specification","alternative":"CF-netCDF Encoding Specification","URI":null,"identifier":"09-122","URL":"https://portal.opengeospatial.org/files/?artifact_id=35505","type":"DP","creator":"Ben Domenico","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-10-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"607":{"title":"3D-Symbology Encoding Discussion Draft","alternative":"3D-Symbology Encoding Discussion Draft","URI":null,"identifier":"09-042","URL":"https://portal.opengeospatial.org/files/?artifact_id=32904","type":"DP","creator":"Steffen Neubauer, Alexander Zipf","contributor":null,"description":"This document present an extension of the Symbology Encoding (SE) /Styled Layer Descriptor (SLD) specifications into 3D as a separate profile.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-10-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"608":{"title":"Grid coverage Coordinate Reference Systems (CRSs)","alternative":"Grid coverage Coordinate Reference Systems (CRSs)","URI":null,"identifier":"09-085r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=35653","type":"DP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-10-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"609":{"title":"OpenSearch Geospatial Extensions Draft Implementation Standard","alternative":"OpenSearch Geospatial Extensions Draft Implementation Standard","URI":null,"identifier":"09-084r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=35983","type":"DP","creator":"Jo Walsh, Pedro Gonçalves, Andrew Turner","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-10-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"610":{"title":"OWS-6 Geoprocessing Workflow Architecture Engineering Report","alternative":"OWS-6 Geoprocessing Workflow Architecture Engineering Report","URI":null,"identifier":"09-053r5","URL":"https://portal.opengeospatial.org/files/?artifact_id=34968","type":"PER","creator":"Bastian Schäffer","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-10-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"611":{"title":"OWS-6 Security Engineering Report","alternative":"OWS-6 Security Engineering Report","URI":null,"identifier":"09-035","URL":"https://portal.opengeospatial.org/files/?artifact_id=35461","type":"PER","creator":"Rüdiger Gartmann, Lewis Leinenweber","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-10-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"612":{"title":"OWS-6 Common CBRN Sensor Interface (CCSI)-Sensor Web Enablement (SWE) Engineering Report","alternative":"OWS-6 Common CBRN Sensor Interface (CCSI)-Sensor Web Enablement (SWE) Engineering Report","URI":null,"identifier":"09-007","URL":"https://portal.opengeospatial.org/files/?artifact_id=33355","type":"PER","creator":"Scott Fairgrieve","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-10-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"613":{"title":"Specification of the Sensor Service Architecture (SensorSA)","alternative":"Specification of the Sensor Service Architecture (SensorSA)","URI":null,"identifier":"09-132r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=35888","type":"DP","creator":"Thomas Usländer (Ed.)","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-10-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"614":{"title":"Web Map Services - Application Profile for EO Products","alternative":"Web Map Services - Application Profile for EO Products","URI":null,"identifier":"07-063r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=30912","type":"BP","creator":"Thomas H.G. Lankester","contributor":null,"description":"This OGC document specifies a constrained, consistent interpretation of the WMS specification that is applicable to government, academic and commercial providers of EO products. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-11-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"615":{"title":"Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0","alternative":"Corrigendum for OpenGIS Implementation Standard Web Processing Service (WPS) 1.0.0","URI":null,"identifier":"08-091r6","URL":"https://portal.opengeospatial.org/files/?artifact_id=32766","type":"ISC","creator":"Peter Schut","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-09-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"616":{"title":"Uses and summary of Topic 2: Spatial referencing by coordinates","alternative":"Uses and summary of Topic 2: Spatial referencing by coordinates","URI":null,"identifier":"09-076r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=35042","type":"DP","creator":"Arliss Whiteside","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-09-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"617":{"title":"OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report","alternative":"OWS-6 Outdoor and Indoor 3D Routing Services Engineering Report","URI":null,"identifier":"09-067r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=35334","type":"PER","creator":"Akiko Sato, Nobuhiro Ishimaru, Guo Tao, Masaaki Tanizaki","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-10-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"618":{"title":"OWS-6 GeoProcessing Workflow Thread Summary ER","alternative":"OWS-6 GeoProcessing Workflow Thread Summary ER","URI":null,"identifier":"09-063","URL":"https://portal.opengeospatial.org/files/?artifact_id=34127","type":"PER","creator":"Lewis Leinenweber","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-09-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"619":{"title":"OWS-6 Sensor Web Enablement (SWE) Engineering Report","alternative":"OWS-6 Sensor Web Enablement (SWE) Engineering Report","URI":null,"identifier":"09-064r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=34147","type":"PER","creator":"Ingo Simonis","contributor":null,"description":"This OGC® document summarizes work completed in the OWS-6 Sensor Web Enablement (SWE) thread.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-09-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"620":{"title":"OWS-6 Symbology Encoding (SE) Changes ER","alternative":"OWS-6 Symbology Encoding (SE) Changes ER","URI":null,"identifier":"09-016","URL":"https://portal.opengeospatial.org/files/?artifact_id=33515","type":"PER","creator":"Craig Bruce","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-09-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"621":{"title":"OWS-6 Styled Layer Descriptor (SLD) Changes ER","alternative":"OWS-6 Styled Layer Descriptor (SLD) Changes ER","URI":null,"identifier":"09-015","URL":"https://portal.opengeospatial.org/files/?artifact_id=33516","type":"PER","creator":"Craig Bruce","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-09-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"622":{"title":"DGIWG WMS 1.3 Profile and systems requirements for interoperability for use within a military environment","alternative":"DGIWG WMS 1.3 Profile and systems requirements for interoperability for use within a military environment","URI":null,"identifier":"09-102","URL":"https://portal.opengeospatial.org/files/?artifact_id=34833","type":"BP","creator":"Cyril Minoux","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-09-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"623":{"title":"OWS-6 Symbology-Encoding Harmonization ER","alternative":"OWS-6 Symbology-Encoding Harmonization ER","URI":null,"identifier":"09-012","URL":"https://portal.opengeospatial.org/files/?artifact_id=33519","type":"PER","creator":"Craig Bruce","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-08-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"624":{"title":"OWS-6 GML Profile Validation Tool ER","alternative":"OWS-6 GML Profile Validation Tool ER","URI":null,"identifier":"09-038r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=34099","type":"PER","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-08-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"625":{"title":"OWS-6 SWE PulseNet™ Engineering Report","alternative":"OWS-6 SWE PulseNet™ Engineering Report","URI":null,"identifier":"09-073","URL":"https://portal.opengeospatial.org/files/?artifact_id=34145","type":"PER","creator":"James Ressler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-08-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"626":{"title":"OWS-6 3D Flythrough (W3DS) Engineering Report","alternative":"OWS-6 3D Flythrough (W3DS) Engineering Report","URI":null,"identifier":"09-075r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=33949","type":"PER","creator":"Arne Schilling","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-08-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"627":{"title":"OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS","alternative":"OWS-6 DSS Engineering Report - SOAP/XML and REST in WMTS","URI":null,"identifier":"09-006","URL":"https://portal.opengeospatial.org/files/?artifact_id=33269","type":"PER","creator":"Keith Pomakis","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-08-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"628":{"title":"OWS-6 CITE TEAM Engine Engineering Report","alternative":"OWS-6 CITE TEAM Engine Engineering Report","URI":null,"identifier":"09-072","URL":"https://portal.opengeospatial.org/files/?artifact_id=34146","type":"PER","creator":"James Ressler","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-08-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"629":{"title":"OWS-6 Secure Sensor Web Engineering Report","alternative":"OWS-6 Secure Sensor Web Engineering Report","URI":null,"identifier":"08-176r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=34273","type":"PER","creator":"Andreas Matheus","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"630":{"title":"OWS-6 SensorML Profile for Discovery Engineering Report","alternative":"OWS-6 SensorML Profile for Discovery Engineering Report","URI":null,"identifier":"09-033","URL":"https://portal.opengeospatial.org/files/?artifact_id=33284","type":"PER","creator":"Simon Jirka, Arne Bröring","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"631":{"title":"OWS-6 Georeferencable Imagery Engineering Report","alternative":"OWS-6 Georeferencable Imagery Engineering Report","URI":null,"identifier":"09-034","URL":"https://portal.opengeospatial.org/files/?artifact_id=33925","type":"PER","creator":"Genong (Eugene) Yu, Liping Di","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"632":{"title":"OWS-6 SWE Event Architecture Engineering Report","alternative":"OWS-6 SWE Event Architecture Engineering Report","URI":null,"identifier":"09-032","URL":"https://portal.opengeospatial.org/files/?artifact_id=33347","type":"PER","creator":"Thomas Everding, Johannes Echterhoff","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"633":{"title":"OGC® Catalogue Services - OWL Application Profile of CSW","alternative":"OGC® Catalogue Services - OWL Application Profile of CSW","URI":null,"identifier":"09-010","URL":" http://portal.opengeospatial.org/files/?artifact_id=32620","type":"DP","creator":"Kristin Stock","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"634":{"title":"Sensor Web Enablement Application for Debris Flow Monitoring System in Taiwan","alternative":"Sensor Web Enablement Application for Debris Flow Monitoring System in Taiwan","URI":null,"identifier":"09-082","URL":"https://portal.opengeospatial.org/files/?artifact_id=34126","type":"DP","creator":"Hsu-Chun James Yu, Zhong-Hung Lee, Cai-Fang Ye, Lan-Kun Chung, Yao-Min Fang","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"635":{"title":"OGC OWS-6-AIM Engineering Report","alternative":"OGC OWS-6-AIM Engineering Report","URI":null,"identifier":"09-050r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=34032","type":"PER","creator":"Hans Schoebach","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"636":{"title":"OWS-6 WPS Grid Processing Profile Engineering Report","alternative":"OWS-6 WPS Grid Processing Profile Engineering Report","URI":null,"identifier":"09-041r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=34977","type":"PER","creator":"Bastian Baranski","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"637":{"title":"OWS-6 GeoXACML Engineering Report","alternative":"OWS-6 GeoXACML Engineering Report","URI":null,"identifier":"09-036r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=34976","type":"PER","creator":"Jan Herrmann, Andreas Matheus","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"638":{"title":"Compliance Test Language (CTL) Best Practice","alternative":"Compliance Test Language (CTL) Best Practice","URI":null,"identifier":"06-126r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=33085","type":"BP","creator":"Chuck Morris","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"639":{"title":"OWS-6 UTDS-CityGML Implementation Profile","alternative":"OWS-6 UTDS-CityGML Implementation Profile","URI":null,"identifier":"09-037r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=34098","type":"PER","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"640":{"title":"OWS-6 SWE Information Model Engineering Report","alternative":"OWS-6 SWE Information Model Engineering Report","URI":null,"identifier":"09-031r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=34118","type":"PER","creator":"Thomas Everding","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"641":{"title":"Semantic annotations in OGC standards","alternative":"Semantic annotations in OGC standards","URI":null,"identifier":"08-167r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=34916","type":"D-DP","creator":"Patrick Maué","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-07-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"642":{"title":"OpenGIS Web Feature Service (WFS) Implementation Specification with XLinks","alternative":"Web Feature Service (WFS) Implementation Specification with XLinks","URI":null,"identifier":"04-094","URL":"https://portal.opengeospatial.org/files/?artifact_id=8339","type":"CC","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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•\tTraverse XLinks\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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-06-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"643":{"title":"PDF Geo-registration Encoding Best Practice Version 2.2","alternative":"PDF Geo-registration Encoding Best Practice Version 2.2","URI":null,"identifier":"08-139r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=40537","type":"BP","creator":"George Demmy, Carl Reed","contributor":null,"description":"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] .","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2011-01-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"644":{"title":"Web Coverage Service (WCS) 1.1 extension for CF-netCDF 3.0 encoding","alternative":"Web Coverage Service (WCS) 1.1 extension for CF-netCDF 3.0 encoding","URI":null,"identifier":"09-018","URL":"https://portal.opengeospatial.org/files/?artifact_id=32195","type":"DP","creator":"Ben Domenico, Stefano Nativi","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-04-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"645":{"title":"Uncertainty Markup Language (UnCertML)","alternative":"Uncertainty Markup Language (UnCertML)","URI":null,"identifier":"08-122r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=33234","type":"DP","creator":"Matthew Williams, Dan Cornford, Lucy Bastin & Edzer Pebesma","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-04-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"646":{"title":"Web Coverage Processing Service (WCPS) Abstract Test Suite","alternative":"Web Coverage Processing Service (WCPS) Abstract Test Suite","URI":null,"identifier":"08-069r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=32314","type":"TS","creator":"Peter Baumann","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-03-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"647":{"title":"WCS Processing Extension (WCPS) Abstract Test Suite","alternative":"WCS Processing Extension (WCPS) Abstract Test Suite","URI":null,"identifier":"08-053r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=32888","type":"TS","creator":"Peter Baumann","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-03-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"648":{"title":"OpenGIS Web Coverage Service (WCS) - Processing Extension (WCPS)","alternative":"Web Coverage Service (WCS) - Processing Extension (WCPS)","URI":null,"identifier":"08-059r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=32416","type":"IS","creator":"Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-03-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"649":{"title":"OpenGIS Web Coverage Processing Service (WCPS) Language Interface Standard","alternative":"Web Coverage Processing Service (WCPS) Language Interface Standard","URI":null,"identifier":"08-068r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=32319","type":"IS","creator":"Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-03-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"650":{"title":"GML 3.2 implementation of XML schemas in 07-000","alternative":"GML 3.2 implementation of XML schemas in 07-000","URI":null,"identifier":"08-127","URL":"https://portal.opengeospatial.org/files/?artifact_id=29542","type":"DP","creator":"Simon Cox","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-08-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"651":{"title":"GML 3.2 implementation of XML schemas in 07-022r1","alternative":"GML 3.2 implementation of XML schemas in 07-022r1","URI":null,"identifier":"08-128","URL":"https://portal.opengeospatial.org/files/?artifact_id=29543","type":"D-DP","creator":"Simon Cox","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-03-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"652":{"title":"GML 3.2 implementation of XML schemas in 07-002r3","alternative":"GML 3.2 implementation of XML schemas in 07-002r3","URI":null,"identifier":"08-129","URL":"https://portal.opengeospatial.org/files/?artifact_id=29544","type":"D-DP","creator":"Simon Cox","contributor":null,"description":"","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-03-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"653":{"title":"CSW-ebRIM Registry Service - Part 3: Abstract Test Suite","alternative":"CSW-ebRIM Registry Service - Part 3: Abstract Test Suite","URI":null,"identifier":"08-103r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=31139","type":"TS","creator":"Richard Martell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-02-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"654":{"title":"CSW-ebRIM Registry Service - Part 2: Basic extension package","alternative":"CSW-ebRIM Registry Service - Part 2: Basic extension package","URI":null,"identifier":"07-144r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=31138","type":"IS","creator":"Richard Martell","contributor":null,"description":"Incorporates Corrigendum 1 (OGC 08-102r1).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-02-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"655":{"title":"CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW","alternative":"CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW","URI":null,"identifier":"07-110r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=31137","type":"IS","creator":"Richard Martell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-02-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"656":{"title":"OGC® KML Standard Development Best Practices","alternative":"KML Standard Development Best Practices","URI":null,"identifier":"08-125r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=30203","type":"BP","creator":"Tim Wilson, David Burggraf","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-02-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"657":{"title":"Web Coverage Service (WCS) - Transaction operation extension","alternative":"Web Coverage Service (WCS) - Transaction operation extension","URI":null,"identifier":"07-068r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=28506","type":"IS","creator":"Arliss Whiteside","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-01-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"658":{"title":"Topic 5 - Features","alternative":"Topic 5 - Features","URI":null,"identifier":"08-126","URL":"https://portal.opengeospatial.org/files/?artifact_id=29536","type":"AS","creator":"Cliff Kottman and Carl Reed","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-01-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"659":{"title":"Definition identifier URNs in OGC namespace","alternative":"Definition identifier URNs in OGC namespace","URI":null,"identifier":"07-092r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=30575","type":"BP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2009-01-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"660":{"title":"Event Pattern Markup Language (EML)","alternative":"Event Pattern Markup Language (EML)","URI":null,"identifier":"08-132","URL":"https://portal.opengeospatial.org/files/?artifact_id=29566","type":"DP","creator":"Thomas Everding, Johannes Echterhoff","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-11-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"661":{"title":"OpenGIS® Sensor Event Service Interface Specification","alternative":"Sensor Event Service Interface Specification","URI":null,"identifier":"08-133","URL":"https://portal.opengeospatial.org/files/?artifact_id=29576","type":"DP","creator":"Johannes Echterhoff, Thomas Everding","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-10-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"662":{"title":"OWS-5 KML Engineering Report","alternative":"OWS-5 KML Engineering Report","URI":null,"identifier":"07-124r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=28086","type":"DP","creator":"Chris Holmes","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-09-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"663":{"title":"OWS-5 GeoProcessing Workflow Architecture Engineering Report","alternative":"OWS-5 GeoProcessing Workflow Architecture Engineering Report","URI":null,"identifier":"07-138r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=30065","type":"DP","creator":"Michael Werling","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-09-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"664":{"title":"OWS-5 Conflation Engineering Report","alternative":"OWS-5 Conflation Engineering Report","URI":null,"identifier":"07-160r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=30064","type":"DP","creator":"Pete Brennen","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-09-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"665":{"title":"OWS-5 WCS JPIP Coverage Subsetting Engineering Report","alternative":"OWS-5 WCS JPIP Coverage Subsetting Engineering Report","URI":null,"identifier":"07-169","URL":"https://portal.opengeospatial.org/files/?artifact_id=27047","type":"DP","creator":"Steven Keens","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-09-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"666":{"title":"OWS-5 Earth Observation Web Processing Services (WPS) Engineering Report","alternative":"OWS-5 Earth Observation Web Processing Services (WPS) Engineering Report","URI":null,"identifier":"08-058r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=30061","type":"DP","creator":"Stefan Falke","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-09-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"667":{"title":"OWS 5 Engineering Report:  Supporting Georeferenceable Imagery","alternative":"OWS 5 Engineering Report:  Supporting Georeferenceable Imagery","URI":null,"identifier":"08-071","URL":"https://portal.opengeospatial.org/files/?artifact_id=29466","type":"DP","creator":"Mike Botts","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-09-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"668":{"title":"Summary of the OGC Web Services, Phase 5 (OWS-5) Interoperability Testbed","alternative":"Summary of the OGC Web Services, Phase 5 (OWS-5) Interoperability Testbed","URI":null,"identifier":"08-073r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=29426","type":"DP","creator":"Jessica Cook, Raj Singh","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-09-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"669":{"title":"OWS-5 GeoRM License Broker Discussion Paper","alternative":"OWS-5 GeoRM License Broker Discussion Paper","URI":null,"identifier":"08-076","URL":"https://portal.opengeospatial.org/files/?artifact_id=28162","type":"DP","creator":"Rüdiger Gartmann","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-09-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"670":{"title":"OWS5: OGC Web feature service, core and extensions","alternative":"OWS5: OGC Web feature service, core and extensions","URI":null,"identifier":"08-079","URL":"https://portal.opengeospatial.org/files/?artifact_id=28176","type":"DP","creator":"John Herring","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-09-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"671":{"title":"OpenGIS Location Service (OpenLS) Implementation Specification: Core Services","alternative":"Location Service (OpenLS) Implementation Specification: Core Services","URI":null,"identifier":"07-074","URL":"https://portal.opengeospatial.org/files/?artifact_id=22122","type":"IS","creator":"Marwa Mabrouk","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-09-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"672":{"title":"OGC Location Services (OpenLS): Tracking Service Interface Standard","alternative":"Location Services: Tracking Service Interface Standard","URI":null,"identifier":"06-024r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=25487","type":"IS","creator":"CS Smyth","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-09-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"673":{"title":"OpenGIS Location Services (OpenLS): Part 6 - Navigation Service","alternative":"Location Services (OpenLS): Part 6 - Navigation Service","URI":null,"identifier":"08-028r7","URL":"https://portal.opengeospatial.org/files/?artifact_id=28493","type":"IS","creator":"Gil Fuchs","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-09-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"674":{"title":"OpenGIS®  City Geography Markup Language (CityGML) Encoding Standard","alternative":"City Geography Markup Language (CityGML) Encoding Standard","URI":null,"identifier":"08-007r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=28802","type":"IS","creator":"Gerhard Gröger, Thomas H. Kolbe, Angela Czerwinski, Claus Nagel","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-08-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"675":{"title":"OWS-5 Considerations for the WCTS Extension of WPS","alternative":"OWS-5 Considerations for the WCTS Extension of WPS","URI":null,"identifier":"08-054r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=29406","type":"DP","creator":"Max Martinez","contributor":null,"description":"This document details considerations for using the WPS specification to define a standard coordinate transformation service.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-08-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"676":{"title":"OWS-5 CITE Summary Engineering Report","alternative":"CITE Summary Engineering Report","URI":null,"identifier":"08-084r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=29505","type":"DP","creator":"Jen Marcus","contributor":null,"description":"This document summarizes work completed in the OWS5 Compliance & Interoperability Test & Evaluation thread.  This  document is applicable to the OGC Compliance Test Program.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-08-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"677":{"title":"Sensor Web Enablement Architecture","alternative":"OGC® Sensor Web Enablement Architecture","URI":null,"identifier":"06-021r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=29405","type":"BP","creator":"Ingo Simonis","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-08-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"678":{"title":"OGC OWS-5 Engineering Report on WCPS","alternative":"OWS-5 Engineering Report on WCPS","URI":null,"identifier":"07-166r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=27052","type":"DP","creator":"Peter Baumann","contributor":null,"description":"This document represents the Engineering Report for the WCPS activity within the OWS-5 SWE thread. It summarizes tasks and outcomes.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-08-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"679":{"title":"EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0","alternative":"OGC® Catalogue Services Specification 2.0 Extension Package for ebRIM (ISO/TS 15000-3) Application Profile: Earth Observation","URI":null,"identifier":"06-131r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=28152","type":"D-BP","creator":"Renato Primavera","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-07-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"680":{"title":"Sensor Web Enablement Architecture","alternative":"OGC® Sensor Web Enablement Architecture","URI":null,"identifier":"06-021r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=27775","type":"D-BP","creator":"Ingo Simonis","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-07-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"681":{"title":"OGC® OWS-5 ER: GSIP Schema Processing","alternative":"OWS-5 ER: GSIP Schema Processing","URI":null,"identifier":"08-078r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=29029","type":"DP","creator":"Clemens Portele","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-07-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"682":{"title":"OGC® OWS-5 Engineering Report: Local MSD Implementation Profile (GML 3.2.1)","alternative":"OWS-5 Engineering Report: Local MSD Implementation Profile (GML 3.2.1)","URI":null,"identifier":"08-077","URL":"https://portal.opengeospatial.org/files/?artifact_id=28170","type":"DP","creator":"Clemens Portele","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-07-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"683":{"title":"Feature Type Catalogue Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0","alternative":"Feature Type Catalogue Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0","URI":null,"identifier":"07-172r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=26730","type":"DP","creator":"Kristin Stock","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-05-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"684":{"title":"Change Request - O&M Part 1 - Move extensions to new namespace","alternative":"Change Request - O&M Part 1 - Move extensions to new namespace","URI":null,"identifier":"08-022r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=27697","type":"CR","creator":"Simon Cox","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-05-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"685":{"title":"A URN namespace for the Open Geospatial Consortium (OGC)","alternative":"A URN namespace for the Open Geospatial Consortium (OGC)","URI":null,"identifier":"07-107r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=27357","type":"BP","creator":"Carl Reed","contributor":null,"description":" 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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-05-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"686":{"title":"OWS-5 Data View Architecture Engineering Report","alternative":"Data View Architecture Engineering Report","URI":null,"identifier":"07-163","URL":"https://portal.opengeospatial.org/files/?artifact_id=27330","type":"DP","creator":"David Rosinger, Stan Tillman","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-05-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"687":{"title":"OpenGIS Web Map Context Documents Corrigendum 1","alternative":"Web Map Context Documents Corrigendum 1","URI":null,"identifier":"08-050","URL":"https://portal.opengeospatial.org/files/?artifact_id=27286","type":"ISC","creator":"Tom Kralidis","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-05-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"688":{"title":"Corrigendum 2 for the OGC Standard Web Coverage Service 1.1","alternative":"Corrigendum 2 for the OGC Standard Web Coverage Service 1.1","URI":null,"identifier":"07-066r5","URL":"https://portal.opengeospatial.org/files/?artifact_id=27298","type":"Notes","creator":"Arliss Whiteside","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-04-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"689":{"title":"Web Coverage Service (WCS) Implementation Standard","alternative":"Web Coverage Service (WCS) Implementation Standard","URI":null,"identifier":"07-067r5","URL":"https://portal.opengeospatial.org/files/?artifact_id=27297","type":"D-IS","creator":"Arliss Whiteside","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-04-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"690":{"title":"OGC® Canadian Geospatial Data Infrastructure WFS and GML Best Practices","alternative":"CGDI WFS and GML Best Practices","URI":null,"identifier":"08-002","URL":"https://portal.opengeospatial.org/files/?artifact_id=26610","type":"DP","creator":"Peter Rushforth","contributor":null,"description":"This document gives guidelines and recommendations for administrators, users and implementers of Web Feature Services serving Geography Markup Language encoded response documents.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-04-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"691":{"title":"OGC® Loosely Coupled Synchronization of Geographic Databases in the Canadian Geospatial Data Infrastructure Pilot","alternative":"Loosely Coupled Synchronization of Geographic Databases in the CGDI","URI":null,"identifier":"08-001","URL":"https://portal.opengeospatial.org/files/?artifact_id=26609","type":"DP","creator":"Raj Singh","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-04-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"692":{"title":"OGC® Canadian Geospatial Data Infrastructure Summary Report","alternative":"Canadian Geospatial Data Infrastructure Summary Report","URI":null,"identifier":"08-000","URL":"https://portal.opengeospatial.org/files/?artifact_id=26608","type":"DP","creator":"Raj SIngh","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-04-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"693":{"title":"OpenGIS® Abstract Specification Proposed Topic 19: General Reference Systems","alternative":"Proposed Topic 19: General Reference Systems","URI":null,"identifier":"08-008r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=27711","type":"D-DP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-04-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"694":{"title":"OGC KML 2.2 -Abstract Test Suite","alternative":"KML 2.2 - Abstract Test Suite","URI":null,"identifier":"07-134r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=27811","type":"TS","creator":"Richard Martell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-04-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"695":{"title":"OGC KML","alternative":"KML","URI":null,"identifier":"07-147r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=27810","type":"IS","creator":"Tim Wilson","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-04-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"696":{"title":"CSW-ebRIM Registry Service - Part 2: Basic extension package","alternative":"CSW-ebRIM Registry Service - Part 2: Basic extension package","URI":null,"identifier":"07-144r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=27093","type":"D-IS","creator":"Richard Martell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-03-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"697":{"title":"CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW","alternative":"CSW-ebRIM Registry Service - Part 1: ebRIM profile of CSW","URI":null,"identifier":"07-110r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=27092","type":"D-IS","creator":"Richard Martell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-03-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"698":{"title":"GeoXACML Implementation Specification - Extension B (GML3) Encoding","alternative":"GeoXACML Implementation Specification - Extension B (GML3) Encoding","URI":null,"identifier":"07-099r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=25220","type":"IS","creator":"Andreas Matheus","contributor":null,"description":"This specification is a normative extension to the GeoXACML core Implementation Specification. It defines the GML3 encoding for geometries.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"699":{"title":"GeoXACML Implementation Specification - Extension A (GML2) Encoding","alternative":"GeoXACML Implementation Specification - Extension A (GML2) Encoding","URI":null,"identifier":"07-098r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=25219","type":"IS","creator":"Andreas Matheus","contributor":null,"description":"This document defines an extension to the GeoXACML Implementation Specification, Verison 1.0 for the GML2 geometry encoding as specified in the GML2 standard.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"700":{"title":"Geospatial eXtensible Access Control Markup Language (GeoXACML)","alternative":"Geospatial eXtensible Access Control Markup Language (GeoXACML)","URI":null,"identifier":"07-026r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=25218","type":"D-IS","creator":"Andreas Matheus, Jan Herrmann","contributor":null,"description":"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]). ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-02-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"701":{"title":"OWS 5 SOAP/WSDL Common Engineering Report","alternative":"OWS 5 SOAP/WSDL Common Engineering Report","URI":null,"identifier":"08-009r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=26521","type":"DP","creator":"Bastian Schaeffer","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-02-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"702":{"title":"Revision Notes for OpenGIS® Implementation Specification: Geographic information - Geography Markup Language Version 3.2.1","alternative":"Revision Notes for OpenGIS® Implementation Specification: Geographic information - Geography Markup Language Version 3.2.1","URI":null,"identifier":"07-061","URL":"https://portal.opengeospatial.org/files/?artifact_id=26765","type":"Notes","creator":"Clemens Portele","contributor":null,"description":"This document provides revision notes for version 3.2.1 of the OpenGIS® Implementation Specification Geographic information – Geography Markup Language (GML).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-02-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"703":{"title":"FedEO Pilot Engineering Report","alternative":"FedEO Pilot Engineering Report (07-152)","URI":null,"identifier":"07-152","URL":"https://portal.opengeospatial.org/files/?artifact_id=25184","type":"DP","creator":"Corentin Guillo","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-01-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"704":{"title":"OpenGIS Sensor Planning Service Application Profile for EO Sensors","alternative":"Sensor Planning Service Application Profile for EO Sensors","URI":null,"identifier":"07-018r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=25199","type":"BP","creator":"Philippe M","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-01-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"705":{"title":"OpenGIS Sensor Observation Service","alternative":"Sensor Observation Service","URI":null,"identifier":"06-009r6","URL":"https://portal.opengeospatial.org/files/?artifact_id=26667","type":"IS","creator":"Arthur Na, Mark Priest","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-02-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"706":{"title":"Wrapping OGC HTTP-GET/POST Services with SOAP","alternative":"Wrapping OGC HTTP-GET/POST Services with SOAP","URI":null,"identifier":"07-158","URL":"https://portal.opengeospatial.org/files/?artifact_id=25280","type":"DP","creator":"R","contributor":null,"description":"Discussion of how to wrap OGC HTTP-GET/POST Services with SOAP","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2008-01-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"707":{"title":"Topic 6 - Schema for coverage geometry and functions","alternative":"Topic 6 - Schema for coverage geometry and functions","URI":null,"identifier":"07-011","URL":"https://portal.opengeospatial.org/files/?artifact_id=19820","type":"AS","creator":"OGC","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-12-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"708":{"title":"Observations and Measurements - Part 2 - Sampling Features","alternative":"Observations and Measurements - Part 2 - Sampling Features","URI":null,"identifier":"07-002r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=22467","type":"D-IS","creator":"Simon Cox","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-12-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"709":{"title":"Observations and Measurements - Part 1 - Observation schema","alternative":"Observations and Measurements - Part 1 - Observation schema","URI":null,"identifier":"07-022r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=22466","type":"D-IS","creator":"Simon Cox","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-12-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"710":{"title":"KML 2.2 Reference - An OGC Best Practice","alternative":"KML 2.2 Reference - An OGC Best Practice","URI":null,"identifier":"07-113r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=23689","type":"D-BP","creator":"Google, Galdos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-11-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"711":{"title":"Definition identifier URNs in OGC namespace","alternative":"Definition identifier URNs in OGC namespace","URI":null,"identifier":"07-092r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=24045","type":"D-BP","creator":"Arliss Whiteside","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-11-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"712":{"title":"OGC Web Services Summaries","alternative":"Web Services Summaries","URI":null,"identifier":"07-095r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=23979","type":"DP","creator":"Arliss Whiteside","contributor":null,"description":"This document provides brief and consistent summaries of several OGC Web Service interface specifications that serve data.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-11-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"713":{"title":"OpenGIS SensorML Encoding Standard v 1.0 Schema Corregendum 1","alternative":"SensorML Encoding Standard v 1.0 Schema Corregendum 1","URI":null,"identifier":"07-122r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=24757","type":"ISC","creator":"Mike Botts, Simon Cox","contributor":null,"description":"Changes to the 1.0 schemas","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-11-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"714":{"title":"OpenGIS Tiled WMS Discussion Paper","alternative":"Tiled WMS Discussion Paper","URI":null,"identifier":"07-057r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=23206","type":"D-DP","creator":"Keith Pomakis","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"715":{"title":"Web Coordinate Transformation Service","alternative":"Web Coordinate Transformation Service","URI":null,"identifier":"07-055r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=24314","type":"DP","creator":"Arliss Whiteside, Markus U. M","contributor":null,"description":"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 ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"716":{"title":"Reference Model for the ORCHESTRA Architecture","alternative":"Reference Model for the ORCHESTRA Architecture","URI":null,"identifier":"07-097","URL":"https://portal.opengeospatial.org/files/?artifact_id=23286","type":"BP","creator":"Thomas Uslander (Ed.)","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"717":{"title":"OpenGIS Geography Markup Language (GML) Encoding Standard","alternative":"Geography Markup Language (GML) Encoding Standard","URI":null,"identifier":"07-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=20509","type":"IS","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"718":{"title":"Web Processing Service","alternative":"Web Processing Service","URI":null,"identifier":"05-007r7","URL":"https://portal.opengeospatial.org/files/?artifact_id=24151","type":"IS","creator":"Peter Schut","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"719":{"title":"Compliance Test Engine Interoperability Program Report","alternative":"Compliance Test Engine Interoperability Program Report","URI":null,"identifier":"07-012","URL":"https://portal.opengeospatial.org/files/?artifact_id=20582","type":"DP","creator":"Jennifer Marcus, Chuck Morris","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-09-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"720":{"title":"OpenGIS Web Coverage Service (WCS) Implementation Specification Corrigendum 1","alternative":"Web Coverage Service (WCS) Implementation Specification Corrigendum 1","URI":null,"identifier":"07-067r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=22560","type":"D-IS","creator":"Arliss Whiteside, John Evans","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"721":{"title":"Corrigendum 1 (one) for OpenGIS Implementation Specification GML 2.1.2","alternative":"Corrigendum 1 (one) for OpenGIS Implementation Specification GML 2.1.2","URI":null,"identifier":"06-189","URL":"https://portal.opengeospatial.org/files/?artifact_id=19208","type":"D-ISC","creator":"Chris Holmes","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"722":{"title":"GML Application Schema for EO Products","alternative":"GML Application Schema for EO Products","URI":null,"identifier":"06-080r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=22161","type":"D-BP","creator":"Jerome Gasperi","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"723":{"title":"Web Map Services - Application Profile for EO Products","alternative":"Web Map Services - Application Profile for EO Products","URI":null,"identifier":"07-063","URL":"https://portal.opengeospatial.org/files/?artifact_id=21742","type":"D-BP","creator":"Thomas H.G. Lankester","contributor":null,"description":"This OGC document specifies a constrained, consistent interpretation of the WMS specification that is applicable to government, academic and commercial providers of EO products.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"724":{"title":"Ordering Services for Earth Observation Products","alternative":"Ordering Services for Earth Observation Products","URI":null,"identifier":"06-141r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=22114","type":"D-BP","creator":"Daniele Marchionni","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"725":{"title":"OpenGIS Sensor Planning Service Application Profile for EO Sensors","alternative":"Sensor Planning Service Application Profile for EO Sensors","URI":null,"identifier":"07-018r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=21465","type":"D-BP","creator":"Philippe M","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"726":{"title":"GeoDRM Engineering Viewpoint and supporting Architecture","alternative":"GeoDRM Engineering Viewpoint and supporting Architecture","URI":null,"identifier":"06-184r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=21285","type":"DP","creator":"Christian Elfers, Roland M. Wagner","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"727":{"title":"OWS 4 WFS Temporal Investigation","alternative":"WFS Temporal Investigation","URI":null,"identifier":"06-154","URL":"https://portal.opengeospatial.org/files/?artifact_id=19580","type":"DP","creator":"David S. Burggraf, Ron Lake, Darko Androsevic","contributor":null,"description":"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).  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"728":{"title":"City Geography Markup Language","alternative":"City Geography Markup Language","URI":null,"identifier":"07-062","URL":"https://portal.opengeospatial.org/files/?artifact_id=22120","type":"D-BP","creator":"Gerhard Gr","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"729":{"title":"OpenGIS Styled Layer Descriptor Profile of the Web Map Service Implementation Specification","alternative":"Styled Layer Descriptor Profile of the Web Map Service Implementation Specification","URI":null,"identifier":"05-078r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=22364","type":"IS","creator":"Markus Lupp","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"730":{"title":"OGC Web Services Architectural Profile for the NSG","alternative":"OGC Web Services Architectural Profile for the NSG","URI":null,"identifier":"07-009r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=22873","type":"DP","creator":"Shayne Urbanowski","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"731":{"title":"Change Request: WCS: Proposal for WCS Transactional - WCS-T","alternative":"Proposal for WCS Transactional - WCS-T","URI":null,"identifier":"06-098","URL":"https://portal.opengeospatial.org/files/?artifact_id=20257","type":"CR","creator":"Michael Gerlek","contributor":null,"description":"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 ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"732":{"title":"OpenGIS Sensor Planning Service Implementation Specification","alternative":"Sensor Planning Service Implementation Specification","URI":null,"identifier":"07-014r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=23180","type":"D-IS","creator":"Ingo Simonis","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"733":{"title":"OpenGIS Catalogue Services Specification 2.0.2 - ISO Metadata Application Profile","alternative":"ISO Metadata Application Profile","URI":null,"identifier":"07-045","URL":"https://portal.opengeospatial.org/files/?artifact_id=21460","type":"SAP","creator":"Uwe Voges, Kristian Senkler","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-08-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"734":{"title":"Reference Model for the ORCHESTRA Architecture","alternative":"Reference Model for the ORCHESTRA Architecture","URI":null,"identifier":"07-024","URL":"https://portal.opengeospatial.org/files/?artifact_id=20300","type":"D-DP","creator":"Thomas Uslander (Ed.)","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-07-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"735":{"title":"OpenGIS Sensor Model Language (SensorML)","alternative":"Sensor Model Language (SensorML)","URI":null,"identifier":"07-000","URL":"https://portal.opengeospatial.org/files/?artifact_id=21273","type":"IS","creator":"Mike Botts","contributor":null,"description":"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://vast.uah.edu/SensorML.-->","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-07-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"736":{"title":"The Specification Model -- Structuring an OGC specification to encourage implementation","alternative":"The Specification Model -- Structuring an OGC specification to encourage implementation","URI":null,"identifier":"07-056r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=21976","type":"DP","creator":"John Herring, OAB, Architecture WG","contributor":null,"description":"This standard specifies some desirable characteristics of a standards specification that will encourage implementations by minimizing difficulty and optimizing usability and interoperability. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-07-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"737":{"title":"OpenGIS Transducer Markup Language *RETIRED*","alternative":"Transducer Markup Language","URI":null,"identifier":"06-010r6","URL":"https://portal.opengeospatial.org/files/?artifact_id=19371","type":"Retired","creator":"Steve Havens","contributor":null,"description":"*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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-07-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"738":{"title":"Revision Notes for Corrigendum for OpenGIS 07-006: Catalogue Services, Version 2.0.2","alternative":"Revision Notes for Corrigendum for OpenGIS 07-006: Catalogue Services, Version 2.0.2","URI":null,"identifier":"07-010","URL":"https://portal.opengeospatial.org/files/?artifact_id=20561","type":"ISC","creator":"Doug Nebert","contributor":null,"description":"This document is a corrigendum for OGC Document 04-021r3. All changes described herein are published in OGC Document 07-006r1.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-06-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"739":{"title":"Feature Styling IPR","alternative":"Feature Styling IPR","URI":null,"identifier":"06-140","URL":"https://portal.opengeospatial.org/files/?artifact_id=19084","type":"DP","creator":"Dr. Markus M","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-06-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"740":{"title":"OWS-4 CSW ebRIM Modelling Guidelines IPR","alternative":"OWS-4 CSW ebRIM Modelling Guidelines IPR","URI":null,"identifier":"06-155","URL":"https://portal.opengeospatial.org/files/?artifact_id=20430","type":"DP","creator":"Tim Wilson, Renato Primavera, Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-06-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"741":{"title":"Discussions, findings, and use of WPS in OWS-4","alternative":"Discussions, findings, and use of WPS in OWS-4","URI":null,"identifier":"06-182r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=19424","type":"DP","creator":"Steven Keens","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-06-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"742":{"title":"OGC Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W","alternative":"Cataloguing of ISO Metadata (CIM) using the ebRIM profile of CS-W","URI":null,"identifier":"07-038","URL":"https://portal.opengeospatial.org/files/?artifact_id=20596","type":"D-DP","creator":"Nicolas Lesage, Marie-Lise Vautier","contributor":null,"description":"This document extends the ebRIM application profile of CS-W for the cataloguing of ISO 19115 and ISO 19119 compliant metadata.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-06-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"743":{"title":"OWS4 - Topology Quality Assessment Interoperability Program Report","alternative":"OWS4 - Topology Quality Assessment Interoperability Program Report","URI":null,"identifier":"07-007r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=21821","type":"DP","creator":"Paul Watson","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-06-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"744":{"title":"Frame image geopositioning metadata GML 3.2 application schema","alternative":"Frame image geopositioning metadata GML 3.2 application schema","URI":null,"identifier":"07-032","URL":"https://portal.opengeospatial.org/files/?artifact_id=20586","type":"DP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-06-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"745":{"title":"CUAHSI WaterML","alternative":"CUAHSI WaterML","URI":null,"identifier":"07-041r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=21743","type":"DP","creator":"Ilya Zaslavsky, David Valentine, Tim Whiteaker","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"746":{"title":"Local MSD Implementation Profile (GML 3.2.1)","alternative":"Local MSD Implementation Profile (GML 3.2.1)","URI":null,"identifier":"07-027r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=21702","type":"DP","creator":"Clemens Portele","contributor":null,"description":"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 ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"747":{"title":"OpenGIS Sensor Planning Service Application Profile for EO Sensors","alternative":"Sensor Planning Service Application Profile for EO Sensors","URI":null,"identifier":"07-018","URL":"https://portal.opengeospatial.org/files/?artifact_id=20583","type":"D-DP","creator":"Philippe M","contributor":null,"description":"This Discussion Paper explains how a Sensor Planning Service is organised and implemented for the Earth Observation domain.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"748":{"title":"GEOINT Structure Implementation Profile Schema Processing","alternative":"GEOINT Structure Implementation Profile Schema Processing","URI":null,"identifier":"07-028r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=21628","type":"D-DP","creator":"Clemens Portele","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"749":{"title":"GML Encoding of Discrete Coverages (interleaved pattern)","alternative":"GML Encoding of Discrete Coverages (interleaved pattern)","URI":null,"identifier":"06-188r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=20794","type":"BP","creator":"Simon Cox","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"750":{"title":"Sensor Alert Service","alternative":"Sensor Alert Service","URI":null,"identifier":"06-028r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=15588","type":"BP","creator":"Ingo Simonis","contributor":null,"description":"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). ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"751":{"title":"OGC Web Services Architecture for CAD GIS and BIM","alternative":"OGC Web Services Architecture for CAD GIS and BIM","URI":null,"identifier":"07-023r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=21622","type":"DP","creator":"Paul Cote","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"752":{"title":"Change Request: WCS: Add Transaction operation","alternative":"WCS: Add Transaction operation","URI":null,"identifier":"06-043r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=17909","type":"CR","creator":"Arliss Whiteside","contributor":null,"description":"Specify an additional optional ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"753":{"title":"KML 2.1 Reference - An OGC Best Practice","alternative":"KML 2.1 Reference - An OGC Best Practice","URI":null,"identifier":"07-039r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=21469","type":"D-BP","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"754":{"title":"OWS-4 Workflow IPR","alternative":"Workflow Descriptions and Lessons Learned","URI":null,"identifier":"06-187r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=19778","type":"DP","creator":"Steven Keens","contributor":null,"description":"This document examines five workflows discussed during the course of the OWS-4 project.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"755":{"title":"GeoDDS Mass Market (formerly GeoRSS) Interoperability Program Report","alternative":"GeoDDS Mass Market","URI":null,"identifier":"07-004","URL":"https://portal.opengeospatial.org/files/?artifact_id=20431","type":"DP","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"756":{"title":"Trusted Geo Services IPR","alternative":"Trusted Geo Services IPR","URI":null,"identifier":"06-107r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=20859","type":"DP","creator":"Cristian Opincaru","contributor":null,"description":"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]. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"757":{"title":"Requirements for some specific simple solid, plane and line geometry types","alternative":"Requirements for some specific simple solid, plane and line geometry types","URI":null,"identifier":"07-001r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=21352","type":"DP","creator":"Simon Cox","contributor":null,"description":"This specification describes requirements for specific geometry types, including some simple solids, and planes and lines defined using an implicit parameterization.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"758":{"title":"OpenGIS Catalogue Service Implementation Specification [Catalogue Service for the Web]","alternative":"Catalogue Service Implementation Specification [Catalogue Service for the Web]","URI":null,"identifier":"07-006r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=20555","type":"CC","creator":"Nebert, Whiteside, Vretanos, editors","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-04-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"759":{"title":"OpenGIS Web Service Common Implementation Specification","alternative":"Web Service Common Implementation Specification","URI":null,"identifier":"06-121r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=20040","type":"IS","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-04-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"760":{"title":"OWS Integrated Client (GeoDSS Client)","alternative":"OWS Integrated Client (GeoDSS Client)","URI":null,"identifier":"05-116","URL":"https://portal.opengeospatial.org/files/?artifact_id=12911","type":"DP","creator":"Stan Tillman, Jody Garnett","contributor":null,"description":"This Interoperability Program Report (IPR) provides an overview of the general requirements, architecture, and design considerations of ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-03-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"761":{"title":"OpenGIS Web Coverage Service (WCS) Implementation Specification","alternative":"Web Coverage Service (WCS) Implementation Specification","URI":null,"identifier":"06-083r8","URL":"https://portal.opengeospatial.org/files/?artifact_id=18153","type":"D-IS","creator":"John Evans","contributor":null,"description":"The Web Coverage Service (WCS) supports electronic retrieval of geospatial data as coverages ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-02-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"762":{"title":"GML Application Schema for EO Products","alternative":"GML Application Schema for EO Products","URI":null,"identifier":"06-080r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=19094","type":"D-DP","creator":"Jerome Gasperi","contributor":null,"description":"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]","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-02-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"763":{"title":"A URN namespace for the Open Geospatial Consortium (OGC)","alternative":"A URN namespace for the Open Geospatial Consortium (OGC)","URI":null,"identifier":"06-166","URL":"https://portal.opengeospatial.org/files/?artifact_id=18747","type":"D-DP","creator":"Carl Reed","contributor":null,"description":" 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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-01-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"764":{"title":"Specification best practices","alternative":"Specification best practices","URI":null,"identifier":"06-135r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=17566","type":"D-BP","creator":"Carl Reed","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-01-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"765":{"title":"OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option","alternative":"Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option","URI":null,"identifier":"06-104r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=18242","type":"D-IS","creator":"John Herring","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-01-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"766":{"title":"OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture","alternative":"Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture","URI":null,"identifier":"06-103r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=18241","type":"D-IS","creator":"John Herring","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-01-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"767":{"title":"Topic 18 - Geospatial Digital Rights Management Reference Model (GeoDRM RM)","alternative":"Topic 18 - Geospatial Digital Rights Management Reference Model (GeoDRM RM)","URI":null,"identifier":"06-004r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=17802","type":"AS","creator":"Graham Vowles","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-01-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"768":{"title":"Web Notification Service","alternative":"Web Notification Service","URI":null,"identifier":"06-095","URL":"https://portal.opengeospatial.org/files/?artifact_id=18776","type":"BP","creator":"Ingo Simonis, Johannes Echterhoff","contributor":null,"description":" 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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-01-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"769":{"title":"GML PIDF-LO Geometry Shape Application Schema for use in the IETF","alternative":"GML PIDF-LO Geometry Shape Application Schema for use in the IETF","URI":null,"identifier":"06-142r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=21630","type":"BP","creator":"Carl Reed, PhD. and Martin Thomson","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-05-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"770":{"title":"Geographic information - Rights expression language for geographic information - Part xx: GeoREL","alternative":"Geographic information - Rights expression language for geographic information - Part xx: GeoREL","URI":null,"identifier":"06-173r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=19054","type":"DP","creator":"John Herring","contributor":null,"description":" 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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-01-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"771":{"title":"OpenGIS Symbology Encoding Implementation Specification","alternative":"Symbology Encoding Implementation Specification","URI":null,"identifier":"05-077r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=16700","type":"IS","creator":"Dr. Markus Mueller","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2007-01-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"772":{"title":"FGDC CSDGM Application Profile for CSW 2.0","alternative":"FGDC CSDGM Application Profile for CSW 2.0","URI":null,"identifier":"06-129r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=16936","type":"BP","creator":"Patrick Neal, John Davidson, Bruce Westcott","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-12-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"773":{"title":"OpenGIS Web Map Services - Application Profile for EO Products","alternative":"Web Map Services - Application Profile for EO Products","URI":null,"identifier":"06-093","URL":"https://portal.opengeospatial.org/files/?artifact_id=16075","type":"D-DP","creator":"Thomas H.G. Lankester","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-10-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"774":{"title":"EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0","alternative":"EO Products Extension Package for ebRIM (ISO/TS 15000-3) Profile of CSW 2.0","URI":null,"identifier":"06-131","URL":"https://portal.opengeospatial.org/files/?artifact_id=17689","type":"D-DP","creator":"Renato Primavera","contributor":null,"description":"This document describes the Data Model of Earth Observation Products for the OGC","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-10-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"775":{"title":"OpenGIS Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW","alternative":"Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW","URI":null,"identifier":"05-025r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=12604","type":"D-DP","creator":"Richard Martell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-10-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"776":{"title":"GeoRSS, An Introduction to","alternative":"GeoRSS, An Introduction to","URI":null,"identifier":"06-050r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=15755","type":"CAN","creator":"Carl Reed","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"777":{"title":"Compliance Test Language (CTL) Discussion Paper","alternative":"Compliance Test Language (CTL) Discussion Paper","URI":null,"identifier":"06-126","URL":"https://portal.opengeospatial.org/files/?artifact_id=16860","type":"D-DP","creator":"Chuck Morris","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-10-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"778":{"title":"Observations and Measurements","alternative":"Observations and Measurements","URI":null,"identifier":"05-087r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=17038","type":"D-BP","creator":"Simon Cox","contributor":null,"description":"The general models and XML encodings for observations and measurements, including but not restricted to those using sensors.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-10-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"779":{"title":"OpenGIS Web Feature Service (WFS) Implementation Specification (Corrigendum)","alternative":"Web Feature Service (WFS) Implementation Specification (Corrigendum)","URI":null,"identifier":"06-027r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=14145","type":"ISC","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-08-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"780":{"title":"Geospatial Semantic Web Interoperabiltiy Experiment Report","alternative":"Geospatial Semantic Web Interoperabiltiy Experiment Report","URI":null,"identifier":"06-002r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=15198","type":"DP","creator":"Joshua Lieberman","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-08-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"781":{"title":"City Geography Markup Language","alternative":"City Geography Markup Language","URI":null,"identifier":"06-057r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=16675","type":"D-DP","creator":"Thomas Kolbe, Gerhard Groeger and Angela Czerwinski","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-08-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"782":{"title":"GML 3.1.1 common CRSs profile Corrigendum","alternative":"GML 3.1.1 common CRSs profile Corrigendum","URI":null,"identifier":"06-113","URL":"https://portal.opengeospatial.org/files/?artifact_id=16572","type":"PC","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"783":{"title":"GML 3.1.1 grid CRSs Profile Corrigendum","alternative":"GML 3.1.1 grid CRSs Profile Corrigendum","URI":null,"identifier":"06-111","URL":"https://portal.opengeospatial.org/files/?artifact_id=16571","type":"PC","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"784":{"title":"Gazetteer Service - Application Profile of the Web Feature Service Implementation Specification","alternative":"Gazetteer Service - Application Profile of the Web Feature Service Implementation Specification","URI":null,"identifier":"05-035r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=15529","type":"BP","creator":"Jens Fitzke, Rob Atkinson","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"785":{"title":"GML Application Schema for EO Products","alternative":"GML Application Schema for EO Products","URI":null,"identifier":"06-080","URL":"https://portal.opengeospatial.org/files/?artifact_id=15546","type":"D-DP","creator":"Jerome Gasperi","contributor":null,"description":"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].","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"786":{"title":"WMS - Proposed Animation Service Extension","alternative":"WMS - Proposed Animation Service Extension","URI":null,"identifier":"06-045r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=14698","type":"DP","creator":"Eric LaMar","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"787":{"title":"Web Coverage Processing Service (WCPS)","alternative":"Web Coverage Processing Service (WCPS)","URI":null,"identifier":"06-035r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=14895","type":"D-BP","creator":"Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"788":{"title":"EO Application Profile for CSW 2.0","alternative":"EO Application Profile for CSW 2.0","URI":null,"identifier":"06-079r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=15547","type":"DP","creator":"Marc Gilles","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-06-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"789":{"title":"Definition identifier URNs in OGC namespace","alternative":"Definition identifier URNs in OGC namespace","URI":null,"identifier":"06-023r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=16339","type":"D-BP","creator":"Arliss Whiteside","contributor":null,"description":"*** 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.<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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-08-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"790":{"title":"GML 3.1.1 simple dictionary profile","alternative":"GML 3.1.1 simple dictionary profile","URI":null,"identifier":"05-099r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=13206","type":"Profile","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"791":{"title":"GML 3.1.1 grid CRSs profile","alternative":"GML 3.1.1 grid CRSs profile","URI":null,"identifier":"05-096r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=13205","type":"Profile","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"792":{"title":"GML 3.1.1 CRS support profile","alternative":"GML 3.1.1 CRS support profile","URI":null,"identifier":"05-094r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=13203","type":"Profile","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"793":{"title":"GML 3.1.1 common CRSs profile","alternative":"GML 3.1.1 common CRSs profile","URI":null,"identifier":"05-095r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=13204","type":"Profile","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"794":{"title":"OpenGIS GML 3.2 image geopositioning metadata application schema","alternative":"GML 3.2 image geopositioning metadata application schema","URI":null,"identifier":"06-055r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=16081","type":"D-DP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"795":{"title":"OpenGIS Image Geopostioning Service","alternative":"Image Geopostioning Service","URI":null,"identifier":"06-054r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=16080","type":"D-DP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-07-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"796":{"title":"OWS3 GML Topology Investigation","alternative":"OWS3 GML Topology Investigation","URI":null,"identifier":"05-102r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=14337","type":"DP","creator":"David Burggraf, Stan Tillman","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-05-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"797":{"title":"Access Control & Terms of Use (ToU)  \"Click-through\" IPR Management","alternative":"Access Control & Terms of Use (ToU)  \"Click-through\" IPR Management","URI":null,"identifier":"05-111r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=13958","type":"DP","creator":"Roland M. Wagner","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-05-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"798":{"title":"Catalog 2.0 IPR for ebRIM","alternative":"Catalog 2.0 IPR for ebRIM","URI":null,"identifier":"05-109r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=14143","type":"D-DP","creator":"Panagiotis (Peter) A. Vretanos, Rento Primavera","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-05-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"799":{"title":"Catalog 2.0 Accessibility for OWS3","alternative":"Catalog 2.0 Accessibility for OWS3","URI":null,"identifier":"05-084","URL":"https://portal.opengeospatial.org/files/?artifact_id=12597","type":"DP","creator":"Vincent Delfosse","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-05-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"800":{"title":"GML 3.1.1 simple features profile","alternative":"GML 3.1.1 simple features profile","URI":null,"identifier":"06-049r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=15201","type":"D-Profile","creator":"Peter Vretanos","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-05-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"801":{"title":"Web Coverage Processing Service","alternative":"Web Coverage Processing Service","URI":null,"identifier":"06-035r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=14022","type":"D-DP","creator":"Peter Baumann","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-05-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"802":{"title":"GML Performance Investigations by CubeWerx","alternative":"GML Performance Investigations by CubeWerx","URI":null,"identifier":"05-050","URL":"https://portal.opengeospatial.org/files/?artifact_id=12983","type":"DP","creator":"Craig Bruce","contributor":null,"description":"This report proposes and executes methods to evaluate the performance of the use of the Geography Markup Language (GML) as encoded in various ways.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-05-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"803":{"title":"Schema Maintenance and Tailoring","alternative":"Schema Maintenance and Tailoring","URI":null,"identifier":"05-117","URL":"https://portal.opengeospatial.org/files/?artifact_id=12893","type":"DP","creator":"Clemens Portele","contributor":null,"description":"Description of the schema tailoring process for the application schema development in the decision support services thread (GeoDSS) during the OWS-3 initiative","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-05-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"804":{"title":"OGC Web Services (OWS) 3 UGAS Tool","alternative":"OGC Web Services (OWS) 3 UGAS Tool","URI":null,"identifier":"05-118","URL":"https://portal.opengeospatial.org/files/?artifact_id=12894","type":"DP","creator":"Clemens Portele, Rafael Renkert","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-04-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"805":{"title":"Symbology Encoding Implementation Specification","alternative":"Symbology Encoding Implementation Specification","URI":null,"identifier":"05-077","URL":"https://portal.opengeospatial.org/files/?artifact_id=12636","type":"D-DP","creator":"Dr. Markus M","contributor":null,"description":"This Specification defines Symbology Encoding, an XML language for styling information that can be applied to digital Feature and Coverage data.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-04-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"806":{"title":"Temporal Standard Recommendations","alternative":"Temporal Standard Recommendations","URI":null,"identifier":"06-022r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=14898","type":"DP","creator":"James Resler","contributor":null,"description":"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). ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-04-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"807":{"title":"Styled Layer Descriptor Profile of the Web Map Service Implementation Specification","alternative":"Styled Layer Descriptor Profile of the Web Map Service Implementation Specification","URI":null,"identifier":"05-078","URL":"https://portal.opengeospatial.org/files/?artifact_id=12637","type":"D-DP","creator":"Dr. Markus M","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-04-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"808":{"title":"Feature Portrayal Service","alternative":"Feature Portrayal Service","URI":null,"identifier":"05-110","URL":"https://portal.opengeospatial.org/files/?artifact_id=13186","type":"Retired","creator":"Arliss Whiteside, Bill Woodward, co-editor","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-04-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"809":{"title":"Symbology Management","alternative":"Symbology Management","URI":null,"identifier":"05-112","URL":"https://portal.opengeospatial.org/files/?artifact_id=13285","type":"D-DP","creator":"Milan Trninic","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-04-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"810":{"title":"OWS 3 GML Investigations - Performance Experiment by Galdos Systems","alternative":"OWS 3 GML Investigations - Performance Experiment by Galdos Systems","URI":null,"identifier":"05-101","URL":"https://portal.opengeospatial.org/files/?artifact_id=13396","type":"DP","creator":"David Burggraf","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-04-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"811":{"title":"Sensor Alert Service","alternative":"Sensor Alert Service","URI":null,"identifier":"06-028","URL":"https://portal.opengeospatial.org/files/?artifact_id=13921","type":"D-DP","creator":"Ingo Simonis","contributor":null,"description":"A service providing active (push-based) access to sensor data.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-04-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"812":{"title":"Observations and Measurements","alternative":"Observations and Measurements","URI":null,"identifier":"05-087r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=14034","type":"D-DP","creator":"Simon Cox","contributor":null,"description":"The general models and XML encodings for observations and measurements, including but not restricted to those using sensors.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-04-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"813":{"title":"OpenGIS Web Coverage Service (WCS) Implementation Specification (Corrigendum)","alternative":"Web Coverage Service (WCS) Implementation Specification (Corrigendum)","URI":null,"identifier":"05-076","URL":"https://portal.opengeospatial.org/files/?artifact_id=12582","type":"D-IS","creator":"John Evans","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-03-31","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"814":{"title":"OWS-3 Imagery Workflow Experiments: Enhanced Service Infrastructure Technology Architecture and Standards in the OWS-3 Testbe","alternative":"OWS-3 Imagery Workflow Experiments: Enhanced Service Infrastructure Technology Architecture and Standards in the OWS-3 Testbe","URI":null,"identifier":"05-140","URL":"https://portal.opengeospatial.org/files/?artifact_id=13916","type":"DP","creator":"Yves Coene","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-03-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"815":{"title":"Geo Video Web Service","alternative":"Geo Video Web Service","URI":null,"identifier":"05-115","URL":"https://portal.opengeospatial.org/files/?artifact_id=12899","type":"DP","creator":"Joe Lewis","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-03-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"816":{"title":"OpenGIS Sensor Web Enablement Architecture Document","alternative":"Sensor Web Enablement Architecture Document","URI":null,"identifier":"06-021r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=14140","type":"DP-Draft","creator":"Mike Botts, Alex Robin, John Davidson, Ingo Simonis","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-03-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"817":{"title":"OpenGIS Catalogue Services - Best Practices for for Earth Observation Products","alternative":"Catalogue Services - Best Practices for for Earth Observation Products","URI":null,"identifier":"05-057r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=14443","type":"D-BP","creator":"Jolyon Martin","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-03-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"818":{"title":"Minimal Application Profile for EO Products","alternative":"Minimal Application Profile for EO Products","URI":null,"identifier":"05-057r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=13885","type":"D-DP","creator":"Jolyon Martin","contributor":null,"description":"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 ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-02-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"819":{"title":"Reference Model for the ORCHESTRA Architecture","alternative":"Reference Model for the ORCHESTRA Architecture","URI":null,"identifier":"05-107","URL":"https://portal.opengeospatial.org/files/?artifact_id=12574","type":"D-DP","creator":"Thomas Uslander (Ed.)","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-01-31","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"820":{"title":"OpenGIS GML in JPEG 2000 for Geographic Imagery  Encoding Specification","alternative":"GML in JPEG 2000 for Geographic Imagery  Encoding Specification","URI":null,"identifier":"05-047r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=13252","type":"IS","creator":"Martin Kyle, David Burggraf, Sean Forde, Ron Lake","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-01-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"821":{"title":"Binary Extensible Markup Language (BXML) Encoding Specification","alternative":"Binary Extensible Markup Language (BXML) Encoding Specification","URI":null,"identifier":"03-002r9","URL":"https://portal.opengeospatial.org/files/?artifact_id=13636","type":"BP","creator":"Craig Bruce","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-01-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"822":{"title":"Sensor Observation Service","alternative":"Sensor Observation Service","URI":null,"identifier":"05-088r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=12846","type":"D-DP","creator":"Arthur Na, Mark Priest","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-01-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"823":{"title":"Sensor Planning Service","alternative":"Sensor Planning Service","URI":null,"identifier":"05-089r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=12971","type":"D-DP","creator":"Ingo Simonis","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-12-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"824":{"title":"OpenGIS Implementation Specification for Geographic information - Simple feature access -","alternative":"Implementation Specification for Geographic information - Simple feature access - Part 2: SQL option","URI":null,"identifier":"05-134","URL":"https://portal.opengeospatial.org/files/?artifact_id=13228","type":"D-IS","creator":"Keith Ryden","contributor":null,"description":"This part of OpenGIS","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-11-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"825":{"title":"OpenGIS Implementation Specification for Geographic information - Simple feature access - Part 1: Common architectu","alternative":"Implementation Specification for Geographic information - Simple feature access - Part 1: Common architecture","URI":null,"identifier":"05-126","URL":"https://portal.opengeospatial.org/files/?artifact_id=13227","type":"D-IS","creator":"Keith Ryden","contributor":null,"description":"This part of OpenGIS","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-11-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"826":{"title":"OpenGIS Sensor Model Language (SensorML)","alternative":"Sensor Model Language (SensorML)","URI":null,"identifier":"05-086","URL":"https://portal.opengeospatial.org/files/?artifact_id=12606","type":"D-BP","creator":"Mike Botts","contributor":null,"description":"The general models and XML encodings for sensors. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-11-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"827":{"title":"OpenGIS Web services architecture description","alternative":"Web services architecture description","URI":null,"identifier":"05-042r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=13140","type":"BP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-11-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"828":{"title":"Web Processing Service","alternative":"Web Processing Service","URI":null,"identifier":"05-007r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=12184","type":"D-RFC","creator":"Peter Schut, Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-09-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"829":{"title":"GML Point Profile","alternative":"GML Point Profile","URI":null,"identifier":"05-029r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=11606","type":"DP","creator":"Ron Lake, Carl Reed, George Percivall","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-08-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"830":{"title":"GML simple features profile","alternative":"GML simple features profile","URI":null,"identifier":"05-033r9","URL":"https://portal.opengeospatial.org/files/?artifact_id=11266","type":"D-RFC","creator":"Peter Vretanos","contributor":null,"description":"This profile defines a restricted but useful subset of XML-Schema and GML to lower the ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-07-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"831":{"title":"Topic 0 - Overview","alternative":"Topic 0 - Overview","URI":null,"identifier":"04-084","URL":"https://portal.opengeospatial.org/files/?artifact_id=7560","type":"AS","creator":"Carl Reed","contributor":null,"description":"Introduction and roadmap to the Abstract specification. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-06-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"832":{"title":"Web Processing Service","alternative":"Web Processing Service","URI":null,"identifier":"05-007r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=10634","type":"D-DP","creator":"Peter Schut","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-06-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"833":{"title":"GeoXACML, a spatial extension to XACML","alternative":"GeoXACML, a spatial extension to XACML","URI":null,"identifier":"05-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=10471&version=2","type":"Retired","creator":"Andreas Matheus","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-06-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"834":{"title":"OpenGIS Location Services (OpenLS): Core Services [Part 4 Presentation Service]","alternative":"Location Services (OpenLS): Core Services [Part 4 Presentation Service]","URI":null,"identifier":"03-006r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=3418","type":"CC","creator":"Marwa Mabrouk","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-01-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"835":{"title":"OpenGIS Location Services (OpenLS): Core Services [Part 3 Location Utility Service]","alternative":"Location Services (OpenLS): Core Services [Part 3 Location Utility Service]","URI":null,"identifier":"03-006r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=3418","type":"CC","creator":"Marwa Mabrouk","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-01-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"836":{"title":"OpenGIS Location Services (OpenLS): Core Services [Parts 5 Route Service]","alternative":"Location Services (OpenLS): Core Services [Parts 5 Route Service]","URI":null,"identifier":"03-006r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=3418","type":"CC","creator":"Marwa Mabrouk","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-01-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"837":{"title":"OpenGIS Location Services (OpenLS): Core Services [Part 2 Gateway Service]","alternative":"Location Services (OpenLS): Core Services [Part 2 Gateway Service]","URI":null,"identifier":"03-006r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=3418","type":"CC","creator":"Marwa Mabrouk","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-01-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"838":{"title":"OpenGIS Location Services (OpenLS): Core Services [Parts 1 Directory Service]","alternative":"Location Services (OpenLS): Core Services [Parts 1 Directory Service]","URI":null,"identifier":"03-006r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=3418","type":"CC","creator":"Marwa Mabrouk","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-01-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"839":{"title":"Coordinate Transformation Services - OLE/COM","alternative":"Coordinate Transformation Services - OLE/COM","URI":null,"identifier":"01-009","URL":"https://portal.opengeospatial.org/files/?artifact_id=999","type":"SAP","creator":"Martin Daly","contributor":null,"description":"Provides interfaces for general positioning, coordinate systems, and coordinate transformations.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-01-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"840":{"title":"Simple Features - SQL - Types and Functions","alternative":"Simple Features - SQL - Types and Functions","URI":null,"identifier":"05-134","URL":"https://portal.opengeospatial.org/files/?artifact_id=13228","type":"CC","creator":"Keith Ryden","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-05-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"841":{"title":"Simple Features - SQL - Normalized Geometry","alternative":"Simple Features - SQL - Normalized Geometry","URI":null,"identifier":"05-134","URL":"https://portal.opengeospatial.org/files/?artifact_id=13228","type":"CC","creator":"Keith Ryden","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-05-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"842":{"title":"Simple Features - SQL - Binary Geometry","alternative":"Simple Features - SQL - Binary Geometry","URI":null,"identifier":"05-134","URL":"https://portal.opengeospatial.org/files/?artifact_id=13228","type":"CC","creator":"Keith Ryden","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-05-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"843":{"title":"Web Feature Service (Transactional)","alternative":"Web Feature Service (Transactional)","URI":null,"identifier":"02-058","URL":"https://portal.opengeospatial.org/files/?artifact_id=7176","type":"D-SAP","creator":"Peter Vretanos","contributor":null,"description":"The purpose of the Web Feature Server Interface Specification (WFS) is to describe data manipulation operations on OpenGIS","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-05-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"844":{"title":"OpenGIS Geographic Objects Implementation Specification *RETIRED*","alternative":"Geographic Objects Implementation Specification *RETIRED*","URI":null,"identifier":"03-064r10","URL":"https://portal.opengeospatial.org/files/?artifact_id=10378","type":"Retired","creator":"Greg Reynolds","contributor":null,"description":"*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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-05-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"845":{"title":"OpenGIS Web Map Context Implementation Specification","alternative":"Web Map Context Implementation Specification","URI":null,"identifier":"05-005","URL":"https://portal.opengeospatial.org/files/?artifact_id=8618","type":"IS","creator":"Jerome Sonnet","contributor":null,"description":"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 ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-05-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"846":{"title":"OpenGIS Web Feature Service (WFS) Implementation Specification","alternative":"Web Feature Service (WFS) Implementation Specification","URI":null,"identifier":"04-094","URL":"https://portal.opengeospatial.org/files/?artifact_id=8339","type":"IS","creator":"Peter Vretanos ","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-05-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"847":{"title":"OpenGIS Filter Encoding Implementation Specification","alternative":"Filter Encoding Implementation Specification","URI":null,"identifier":"04-095","URL":"https://portal.opengeospatial.org/files/?artifact_id=8340","type":"D-IS","creator":"Peter Vretanos","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-05-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"848":{"title":"OpenGIS Location Service (OpenLS) Implementation Specification: Core Services","alternative":"Location Service (OpenLS) Implementation Specification: Core Services","URI":null,"identifier":"05-016","URL":"https://portal.opengeospatial.org/files/?artifact_id=8836","type":"D-IS","creator":"Marwa Mabrouk","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-05-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"849":{"title":"ISO19115/ISO19119 Application Profile for CSW 2.0 (CAT2 AP ISO19115/19)","alternative":"ISO19115/ISO19119 Application Profile for CSW 2.0 (CAT2 AP ISO19115/19)","URI":null,"identifier":"04-038r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=8305","type":"D-BP","creator":"Uwe Voges, Kristian Senkler","contributor":null,"description":"This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-04-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"850":{"title":"WCS Change Request: Support for WSDL & SOAP","alternative":"WCS Change Request: Support for WSDL & SOAP","URI":null,"identifier":"04-049r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=9540","type":"D-DP","creator":"Philippe Duschene, Jerome Sonnet","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-04-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"851":{"title":"WMS Change Request: Support for WSDL & SOAP","alternative":"WMS Change Request: Support for WSDL & SOAP","URI":null,"identifier":"04-050r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=9541","type":"DP","creator":"Philippe Duschene, Jerome Sonnet","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-04-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"852":{"title":"EA-SIG Mediation White Paper","alternative":"EA-SIG Mediation White Paper","URI":null,"identifier":"04-088","URL":"https://portal.opengeospatial.org/files/?artifact_id=7561","type":"Retired","creator":"Paul Lunceford,Steve Matney,Tom Huggins,Chuck Heazel","contributor":null,"description":"*RETIRED* This document focuses on the goals, objectives, capabilities and recommendation for the Mediation Core Enterprise\r\nService.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-02-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"853":{"title":"EA-SIG Enterprise Service Management White Paper","alternative":"EA-SIG Enterprise Service Management White Paper","URI":null,"identifier":"04-087","URL":"https://portal.opengeospatial.org/files/?artifact_id=7562","type":"Retired","creator":"Matt Murray,Jeff Stollman,Shue-Jane Thompson,Terry Plymell,Eli Hertz,Chuck Heazel","contributor":null,"description":"*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?","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-02-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"854":{"title":"EA-SIG Discovery White Paper","alternative":"EA-SIG Discovery White Paper","URI":null,"identifier":"04-086","URL":"https://portal.opengeospatial.org/files/?artifact_id=7563","type":"Retired","creator":"Jeff Harrison,A.J. Maren,Jeff Stohlman,Mike Meyer,Glenn Pruitt,John Clink,Hans Polzer,Mark Schiffner","contributor":null,"description":"*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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-02-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"855":{"title":"EA-SIG Collaboration White Paper","alternative":"EA-SIG Collaboration White Paper","URI":null,"identifier":"04-085","URL":"https://portal.opengeospatial.org/files/?artifact_id=7564","type":"Retired","creator":"Richard Creps,Victor Brown,Bill Floyd,John Garcia,Jeff Grinstead,Robert Kraus,Steve Matney,Robert Qu","contributor":null,"description":"*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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-02-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"856":{"title":"Web Coordinate Transformation Service","alternative":"Web Coordinate Transformation Service","URI":null,"identifier":"05-013","URL":"https://portal.opengeospatial.org/files/?artifact_id=8847","type":"D-DP","creator":"Arliss Whiteside, Markus U. M","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-04-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"857":{"title":"Recommended XML/GML 3.1.1 encoding of common CRS definitions","alternative":"Recommended XML/GML 3.1.1 encoding of common CRS definitions","URI":null,"identifier":"05-011","URL":"https://portal.opengeospatial.org/files/?artifact_id=8837","type":"D-BP","creator":"Arliss Whiteside","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-01-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"858":{"title":"OWS-2 Application Schema Development","alternative":"OWS-2 Application Schema Development","URI":null,"identifier":"04-100","URL":"https://portal.opengeospatial.org/files/?artifact_id=8071","type":"DP","creator":"Clemens Portele","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-04-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"859":{"title":"Recommended XML/GML 3.1.1 encoding of image CRS definitions","alternative":"Recommended XML/GML 3.1.1 encoding of image CRS definitions","URI":null,"identifier":"05-027r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=10048","type":"D-BP","creator":"Arliss Whiteside","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-04-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"860":{"title":"Image CRSs for IH4DS","alternative":"Image CRSs for IH4DS","URI":null,"identifier":"05-014","URL":"https://portal.opengeospatial.org/files/?artifact_id=8848","type":"DP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-01-31","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"861":{"title":"Imagery Metadata","alternative":"Imagery Metadata","URI":null,"identifier":"05-015","URL":"https://portal.opengeospatial.org/files/?artifact_id=8826","type":"DP","creator":"Barry Schlesinger","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-01-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"862":{"title":"URNs of definitions in ogc namespace","alternative":"URNs of definitions in ogc namespace","URI":null,"identifier":"05-010","URL":"https://portal.opengeospatial.org/files/?artifact_id=8814","type":"D-BP","creator":"Arliss Whiteside","contributor":null,"description":"*** Superceded by 06-023r1 - Definition identifier URNs in OGC namespace ***\r\nThis Recommendation Paper specifies Universal Resource Names (URNs) for definitions in the ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-01-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"863":{"title":"OpenGIS Web Service Common Implementation Specification","alternative":"Web Service Common Implementation Specification","URI":null,"identifier":"05-008c1","URL":"https://portal.opengeospatial.org/files/?artifact_id=8798","type":"D-IS","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-05-03","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"864":{"title":"GML in JPEG 2000 for Geographic Imagery","alternative":"GML in JPEG 2000 for Geographic Imagery","URI":null,"identifier":"05-047r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=11418","type":"D-RFC","creator":"Ron Lake","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-03-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"865":{"title":"Style Management Services for Emergency Mapping Symbology","alternative":"Style Management Services for Emergency Mapping Symbology","URI":null,"identifier":"04-040","URL":"https://portal.opengeospatial.org/files/?artifact_id=7470","type":"D-DP","creator":"Bill Lalonde","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-02-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"866":{"title":"OWS 2 Common Architecture: WSDL SOAP UDDI","alternative":"OWS 2 Common Architecture: WSDL SOAP UDDI","URI":null,"identifier":"04-060r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=8348","type":"DP","creator":"Jerome Sonnett","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-02-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"867":{"title":"Topic 2 - Spatial Referencing by Coordinates","alternative":"Topic 2 - Spatial Referencing by Coordinates","URI":null,"identifier":"04-046r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=6716","type":"D-AS","creator":"Roger Lott","contributor":null,"description":"Describes modelling requirements for spatial referencing by coordinates.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-02-11","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"868":{"title":"Web Image Classification Service (WICS)","alternative":"Web Image Classification Service (WICS)","URI":null,"identifier":"05-017","URL":"https://portal.opengeospatial.org/files/?artifact_id=8981","type":"DP","creator":"Wenli Yang, Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-02-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"869":{"title":"Web 3D Service","alternative":"Web 3D Service","URI":null,"identifier":"05-019","URL":"https://portal.opengeospatial.org/files/?artifact_id=8869","type":"D-DP","creator":"Udo Quadt, Thomas Kolbe","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-02-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"870":{"title":"Web Processing Service","alternative":"Web Processing Service","URI":null,"identifier":"05-007","URL":"https://portal.opengeospatial.org/files/?artifact_id=8723","type":"D-DP","creator":"Peter Schut","contributor":null,"description":"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 ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2005-01-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"871":{"title":"Sensor Model Language (SensorML) for In-situ and Remote Sensors","alternative":"Sensor Model Language (SensorML) for In-situ and Remote Sensors","URI":null,"identifier":"04-019r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=7927","type":"D-RP","creator":"Mike Botts","contributor":null,"description":"The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-11-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"872":{"title":"Topic 7 - Earth Imagery","alternative":"Topic 7 - Earth Imagery","URI":null,"identifier":"04-107","URL":"https://portal.opengeospatial.org/files/?artifact_id=7467","type":"AS","creator":"George Percivall","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-10-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"873":{"title":"OGC Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW","alternative":"Catalogue Services - ebRIM (ISO/TS 15000-3) profile of CSW","URI":null,"identifier":"04-017r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=7048","type":"D-DP","creator":"Richard Martell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-10-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"874":{"title":"ISO19115/ISO19119 Application Profile for CSW 2.0","alternative":"ISO19115/ISO19119 Application Profile for CSW 2.0","URI":null,"identifier":"04-038r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=6495","type":"D-DP","creator":"Uwe Voges, Kristian Senkler","contributor":null,"description":"This document explains how Catalogue Services based on the ISO19115/ISO19119 Application Profile for the OpenGIS","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-10-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"875":{"title":"Some image geometry models","alternative":"Some image geometry models","URI":null,"identifier":"04-071","URL":"https://portal.opengeospatial.org/files/?artifact_id=7257","type":"DP","creator":"Arliss Whiteside","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-10-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"876":{"title":"OWS1.2 Image Handling Requirements","alternative":"OWS1.2 Image Handling Requirements","URI":null,"identifier":"04-052","URL":"https://portal.opengeospatial.org/files/?artifact_id=6660","type":"DP","creator":"Arliss Whiteside","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-09-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"877":{"title":"OWS1.2 Image Handling Design","alternative":"OWS1.2 Image Handling Design","URI":null,"identifier":"04-051","URL":"https://portal.opengeospatial.org/files/?artifact_id=6621","type":"DP","creator":"George Percivall","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-09-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"878":{"title":"A URN namespace for the Open Geospatial Consortium (OGC)","alternative":"A URN namespace for the Open Geospatial Consortium (OGC)","URI":null,"identifier":"04-013r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=6944","type":"D-DP","creator":"Carl Reed","contributor":null,"description":"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   ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-09-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"879":{"title":"Geospatial Portal Reference Architecture","alternative":"Geospatial Portal Reference Architecture","URI":null,"identifier":"04-039","URL":"https://portal.opengeospatial.org/files/?artifact_id=6669","type":"DP","creator":"Louis Rose","contributor":null,"description":"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.    ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-09-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"880":{"title":"OpenGIS Catalogue Service Implementation Specification [Catalogue Service for the Web]","alternative":"Catalogue Service Implementation Specification [Catalogue Service for the Web]","URI":null,"identifier":"04-021r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=5929","type":"D-IS","creator":"Doug Nebert","contributor":null,"description":"The OpenGIS Catalogue Services Specification defines common interfaces to discover, browse, and query metadata about data, services, and other potential resources.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-08-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"881":{"title":"OpenGIS Web Map Service (WMS) Implementation Specification","alternative":"Web Map Service (WMS) Implementation Specification","URI":null,"identifier":"06-042","URL":"https://portal.opengeospatial.org/files/?artifact_id=14416","type":"IS","creator":"Jeff de La Beaujardiere","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-03-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"882":{"title":"OGC Technical Document Baseline","alternative":"OGC Technical Document Baseline","URI":null,"identifier":"04-014r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=5393","type":"D-ATB","creator":"Carl Reed, George Percivall","contributor":null,"description":"Spreadsheet of OGC Technical Document Baseline","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-04-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"883":{"title":"GO-1 Application Objects","alternative":"GO-1 Application Objects","URI":null,"identifier":"03-064r5","URL":"https://portal.opengeospatial.org/files/?artifact_id=5936","type":"D-RP","creator":"Eric Bertel","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-06-25","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"884":{"title":"OWS Common Recomendation Paper","alternative":"OWS Common Recomendation Paper","URI":null,"identifier":"04-016r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=6324","type":"D-RP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-06-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"885":{"title":"Geolinking Service","alternative":"Geolinking Service","URI":null,"identifier":"04-011r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=5859","type":"DP","creator":"Peter Schut","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-05-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"886":{"title":"Geolinked Data Access Service","alternative":"Geolinked Data Access Service","URI":null,"identifier":"04-010r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=5858","type":"DP","creator":"Peter Schut","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-05-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"887":{"title":"Level 0 Profile of GML3 for WFS","alternative":"Level 0 Profile of GML3 for WFS","URI":null,"identifier":"03-003r10","URL":"https://portal.opengeospatial.org/files/?artifact_id=4347","type":"Retired","creator":"Peter Vretanos","contributor":null,"description":"*RETIRED* This is a GML application profile known as Level 0 - also known as Simple GML.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-05-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"888":{"title":"OpenGIS Geography Markup Language (GML) Encoding Specification","alternative":"Geography Markup Language (GML) Encoding Specification","URI":null,"identifier":"03-105r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=4700","type":"D-BP","creator":"Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-04-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"889":{"title":"Web Map Service","alternative":"Web Map Service (Recommendation Paper)","URI":null,"identifier":"03-109r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=4756","type":"D-RP","creator":"Jeff de La Beaujardiere","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-02-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"890":{"title":"OGC Web Services Common","alternative":"OGC Web Services Common","URI":null,"identifier":"03-088r6","URL":"https://portal.opengeospatial.org/files/?artifact_id=4550","type":"D-RP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-01-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"891":{"title":"OpenGIS Location Services (OpenLS): Core Services [Parts 1-5]","alternative":"Location Services (OpenLS): Core Services [Parts 1-5]","URI":null,"identifier":"03-006r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=3418","type":"D-RFC","creator":"Marwa Mabrouk","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2004-01-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"892":{"title":"OpenGIS Web Terrain Service RFC","alternative":"Web Terrain Service RFC","URI":null,"identifier":"03-081r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=11499","type":"RFC","creator":"Joshua Lieberman","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-11-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"893":{"title":"OGC Web Services Common","alternative":"OGC Web Services Common","URI":null,"identifier":"03-088r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=11519","type":"D-DP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-10-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"894":{"title":"Recommended XML Encoding of CRS Definitions","alternative":"Recommended XML Encoding of CRS Definitions","URI":null,"identifier":"03-010r9","URL":"https://portal.opengeospatial.org/files/?artifact_id=11517","type":"D-RP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-10-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"895":{"title":"Topic 2 - Spatial Referencing by Coordinates","alternative":"Topic 2 - Spatial Referencing by Coordinates","URI":null,"identifier":"03-073r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=11518","type":"D-AS","creator":"Roel Nicolai","contributor":null,"description":"Describes modelling requirements for spatial referencing by coordinates.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-10-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"896":{"title":"OpenGIS Web Coverage Service (WCS) Implementation Specification","alternative":"Web Coverage Service (WCS) Implementation Specification","URI":null,"identifier":"03-065r6","URL":"https://portal.opengeospatial.org/files/?artifact_id=3837","type":"D-IS","creator":"John Evans","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-10-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"897":{"title":"Observations and Measurements","alternative":"Observations and Measurements","URI":null,"identifier":"03-022r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=1324","type":"D-RP","creator":"Simon Cox","contributor":null,"description":"This document describes a framework and encoding for measurements and observations.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-02-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"898":{"title":"OpenGIS Location Services (OpenLS): Navigation Service [Part 6]","alternative":"Location Services (OpenLS): Navigation Service [Part 6]","URI":null,"identifier":"03-007r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=3840","type":"D-RFC","creator":"Tom Bychowski","contributor":null,"description":"OpenGIS ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-06-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"899":{"title":"Binary-XML Encoding Specification","alternative":"Binary-XML Encoding Specification","URI":null,"identifier":"03-002r8","URL":"https://portal.opengeospatial.org/files/?artifact_id=1386","type":"D-DP","creator":"Craig Bruce","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-05-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"900":{"title":"Critical Infrastructure Collaborative Environment Architecture: Information Viewpoint","alternative":"Critical Infrastructure Collaborative Environment Architecture: Information Viewpoint","URI":null,"identifier":"03-062r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1271","type":"Retired","creator":"Richard Martell","contributor":null,"description":"*RETIRED* specifies the information viewpoint for the Critical Infrastructure Collaborative Environment (CICE).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-06-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"901":{"title":"Critical Infrastructure Collaborative Environment Architecture: Enterprise Viewpoint","alternative":"Critical Infrastructure Collaborative Environment Architecture: Enterprise Viewpoint","URI":null,"identifier":"03-061","URL":"https://portal.opengeospatial.org/files/?artifact_id=1273","type":"Retired","creator":"Geoffrey Ehler","contributor":null,"description":"*RETIRED* specifies the Enterprise viewpoint for the Critical Infrastructure Collaborative Environment (CICE).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-05-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"902":{"title":"Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint","alternative":"Critical Infrastructure Collaborative Environment Architecture: Engineering Viewpoint","URI":null,"identifier":"03-055r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1282","type":"Retired","creator":"Louis Rose","contributor":null,"description":"*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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-06-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"903":{"title":"Critical Infrastructure Collaborative Environment Architecture: Computational Viewpoint","alternative":"Critical Infrastructure Collaborative Environment Architecture: Computational Viewpoint","URI":null,"identifier":"03-063r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1269","type":"Retired","creator":"Joshua Lieberman","contributor":null,"description":"*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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-06-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"904":{"title":"GO-1 Application Objects Report","alternative":"GO-1 Application Objects Report","URI":null,"identifier":"03-064r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1267","type":"D-DP","creator":"Phillip C. Dibner","contributor":null,"description":"This document is a draft of the OpenGIS","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-06-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"905":{"title":"Web Map Context Documents","alternative":"Web Map Context Documents","URI":null,"identifier":"03-036r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=3841","type":"D-IS","creator":"Jean-Philippe Humblet","contributor":null,"description":"Create, store, and use state information from a WMS based client application","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-06-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"906":{"title":"Service Information Model","alternative":"Service Information Model","URI":null,"identifier":"03-026","URL":"https://portal.opengeospatial.org/files/?artifact_id=1319","type":"DP","creator":"Joshua Lieberman","contributor":null,"description":"SIM specifies and discusses a common information model for OGC Web Services, also known variously or in part as service capabilities or service metadata.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-01-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"907":{"title":"Web Services Architecture","alternative":"Web Services Architecture","URI":null,"identifier":"03-025","URL":"https://portal.opengeospatial.org/files/?artifact_id=1320","type":"DP","creator":"Josh Lieberman","contributor":null,"description":"Specifies and discusses a common architectural framework for OGC Web Services","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-01-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"908":{"title":"Web Pricing and Ordering","alternative":"Web Pricing and Ordering","URI":null,"identifier":"02-039r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=11500","type":"D-DP","creator":"Roland Wagner","contributor":null,"description":"This specification covers all standard geo-eBusiness processes like pricing, ordering and online delivery for spatial products.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-10-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"909":{"title":"Web Object Service Implementation Specification","alternative":"Web Object Service Implementation Specification","URI":null,"identifier":"03-013","URL":"https://portal.opengeospatial.org/files/?artifact_id=1338","type":"D-DP","creator":"Panagiotis (Peter) A. Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-01-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"910":{"title":"Web Notification Service","alternative":"Web Notification Service","URI":null,"identifier":"03-008r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=1367","type":"D-DP","creator":"Ingo Simonis, Andreas Wytzisk","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-04-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"911":{"title":"Web Map Context Documents","alternative":"Web Map Context Documents","URI":null,"identifier":"03-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=1306","type":"D-RFC","creator":"Jean-Philippe Humblet","contributor":null,"description":"Create, store, and use state information from a WMS based client application","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-01-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"912":{"title":"Style Management Service","alternative":"Style Management Service","URI":null,"identifier":"03-031","URL":"https://portal.opengeospatial.org/files/?artifact_id=1313","type":"D-DP","creator":"William Lalonde","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-01-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"913":{"title":"Recommended XML Encoding of CRS Definitions","alternative":"Recommended XML Encoding of CRS Definitions","URI":null,"identifier":"03-010r7","URL":"https://portal.opengeospatial.org/files/?artifact_id=1345","type":"D-RP","creator":"Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-05-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"914":{"title":"OGC Web Services SOAP Experiment Report","alternative":"OGC Web Services SOAP Experiment Report","URI":null,"identifier":"03-014","URL":"https://portal.opengeospatial.org/files/?artifact_id=1337","type":"DP","creator":"J","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-01-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"915":{"title":"OGC Web Services UDDI Experiment","alternative":"OGC Web Services UDDI Experiment","URI":null,"identifier":"03-028","URL":"https://portal.opengeospatial.org/files/?artifact_id=1317","type":"DP","creator":"Josh Lieberman, Lou Reich, Peter Vretanos","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-01-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"916":{"title":"OWS Messaging Framework","alternative":"OWS Messaging Framework","URI":null,"identifier":"03-029","URL":"https://portal.opengeospatial.org/files/?artifact_id=1315","type":"DP","creator":"Stephane Fellah, Steven Keens","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-01-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"917":{"title":"OpenGIS Location Services (OpenLS): Core Services [Parts 1-5]","alternative":"Location Services (OpenLS): Core Services [Parts 1-5]","URI":null,"identifier":"03-006r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=3839","type":"D-RFC","creator":"Marwa Mabrouk","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-06-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"918":{"title":"OGC Reference Model","alternative":"OGC Reference Model","URI":null,"identifier":"03-040","URL":"https://portal.opengeospatial.org/files/?artifact_id=3836","type":"D-ORM","creator":"George Percivall","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-09-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"919":{"title":"OGC Technical Document Baseline","alternative":"OGC Technical Document Baseline","URI":null,"identifier":"03-053r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=3835","type":"D-ATB","creator":"Carl Reed, George Percivall","contributor":null,"description":"Spreadsheet of OGC Technical Document Baseline","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-05-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"920":{"title":"Integrated Client for Multiple OGC-compliant Services","alternative":"Integrated Client for Multiple OGC-compliant Services","URI":null,"identifier":"03-021","URL":"https://portal.opengeospatial.org/files/?artifact_id=1328","type":"D-DP","creator":"Jeff Yutzler","contributor":null,"description":"Provides an overview of the requirements, architecture, and design of Integrated Clients developed during the OGC Open Web Services","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-01-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"921":{"title":"Sensor Model Language (SensorML) for In-situ and Remote Sensors","alternative":"Sensor Model Language (SensorML) for In-situ and Remote Sensors","URI":null,"identifier":"02-026r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=11516","type":"D-DP","creator":"Mike Botts","contributor":null,"description":"The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-12-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"922":{"title":"Geography Markup Language","alternative":"Geography Markup Language","URI":null,"identifier":"02-009","URL":"https://portal.opengeospatial.org/files/?artifact_id=1108","type":"D-IS","creator":"Ron Lake","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-01-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"923":{"title":"OpenGIS Geography Markup Language (GML) Encoding Specification","alternative":"Geography Markup Language (GML) Encoding Specification","URI":null,"identifier":"02-023r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=7174","type":"D-IS","creator":"Simon Cox, Paul Daisey, Ron Lake, Clemens Portele, Arliss Whiteside","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2003-01-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"924":{"title":"Catalog Interface","alternative":"Catalog Interface","URI":null,"identifier":"02-087r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=3843","type":"D-IS","creator":"Doug Nebert","contributor":null,"description":"Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-12-13","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"925":{"title":"Units of Measure and Quantity Datatypes","alternative":"Units of Measure and Quantity Datatypes","URI":null,"identifier":"01-044r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=1050","type":"D-DP","creator":"John Bobbitt","contributor":null,"description":"Common semantic for units of measurement to be used across all OGC specifications.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-06-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"926":{"title":"CT Definition Data for Coordinate Reference","alternative":"CT Definition Data for Coordinate Reference","URI":null,"identifier":"01-014r5","URL":"https://portal.opengeospatial.org/files/?artifact_id=1012","type":"D-RP","creator":"Arliss Whiteside","contributor":null,"description":"A data model for coordinate reference systems to provide a common framework across all OGC specifications.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-10-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"927":{"title":"Units of Measure Recommendation","alternative":"Units of Measure Recommendation","URI":null,"identifier":"02-007r4","URL":"https://portal.opengeospatial.org/files/?artifact_id=11498","type":"BP","creator":"John Bobbitt","contributor":null,"description":"Common semantic for units of measurement to be used across all OGC specifications.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-08-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"928":{"title":"Filter Encoding","alternative":"Filter Encoding","URI":null,"identifier":"02-059","URL":"https://portal.opengeospatial.org/files/?artifact_id=1171","type":"D-IS","creator":"Peter Vretanos","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-05-01","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"929":{"title":"OpenGIS Styled Layer Descriptor (SLD) Implementation Specification","alternative":"Styled Layer Descriptor (SLD) Implementation Specification","URI":null,"identifier":"02-070","URL":"https://portal.opengeospatial.org/files/?artifact_id=1188","type":"D-IS","creator":"Bill Lalonde","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-08-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"930":{"title":"Web Feature Service","alternative":"Web Feature Service","URI":null,"identifier":"02-058","URL":"https://portal.opengeospatial.org/files/?artifact_id=7176","type":"D-IS","creator":"Peter Vretanos","contributor":null,"description":"The purpose of the Web Feature Server Interface Specification (WFS) is to describe data manipulation operations on OpenGIS","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-05-17","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"931":{"title":"OpenGIS Grid Coverage Service Implementation Specification","alternative":"Grid Coverage Service Implementation Specification","URI":null,"identifier":"01-004","URL":"https://portal.opengeospatial.org/files/?artifact_id=6628","type":"Retired","creator":"Louis Burry","contributor":null,"description":"**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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-01-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"932":{"title":"Geography Markup Language","alternative":"Geography Markup Language","URI":null,"identifier":"02-069","URL":"https://portal.opengeospatial.org/files/?artifact_id=11339","type":"D-IS","creator":"Ron Lake","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-08-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"933":{"title":"Catalog Interface","alternative":"Catalog Interface","URI":null,"identifier":"99-051","URL":"https://portal.opengeospatial.org/files/?artifact_id=831","type":"D-IS","creator":"Doug Nebert","contributor":null,"description":"Defines a common interface that enables diverse but conformant applications to perform discovery, browse and query operations against distributed and potentially heterogeneous catalog servers.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-07-16","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"934":{"title":"OpenGIS Coordinate Transformation Service Implementation Specification","alternative":"Coordinate Transformation Service Implementation Specification","URI":null,"identifier":"01-009","URL":"https://portal.opengeospatial.org/files/?artifact_id=999","type":"IS","creator":"Martin Daly","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-01-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"935":{"title":"Web Map Service","alternative":"Web Map Service","URI":null,"identifier":"01-068r3","URL":"https://portal.opengeospatial.org/files/?artifact_id=1081&format=pdf","type":"D-IS","creator":"Jeff de La Beaujardiere","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-04-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"936":{"title":"OpenGIS Simple Features Implementation Specification for SQL","alternative":"Simple Features Implementation Specification for SQL","URI":null,"identifier":"99-049","URL":"https://portal.opengeospatial.org/files/?artifact_id=829","type":"D-IS","creator":"Keith Ryden","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-05-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"937":{"title":"OpenGIS Simple Features Implementation Specification for CORBA","alternative":"Simple Features Implementation Specification for CORBA","URI":null,"identifier":"99-054","URL":"https://portal.opengeospatial.org/files/?artifact_id=834","type":"IS","creator":"Peter Ladstaetter","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-06-02","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"938":{"title":"OpenGIS Simple Features Implementation Specification for OLE/COM","alternative":"Simple Features Implementation Specification for OLE/COM","URI":null,"identifier":"99-050","URL":"https://portal.opengeospatial.org/files/?artifact_id=830","type":"IS","creator":"TC Chair","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-05-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"939":{"title":"Sensor Collection Service","alternative":"Sensor Collection Service","URI":null,"identifier":"02-028","URL":"https://portal.opengeospatial.org/files/?artifact_id=1141","type":"IPR","creator":"Tom  McCarty","contributor":null,"description":"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. ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-04-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"940":{"title":"Coverage Portrayal Service","alternative":"Coverage Portrayal Service","URI":null,"identifier":"02-019r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1121","type":"IPR","creator":"Jeff Lansing","contributor":null,"description":"The Coverage Portrayal Service (CPS) IPR proposes a standard interface for producing visual pictures from coverage data.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-02-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"941":{"title":"SensorML","alternative":"SensorML","URI":null,"identifier":"02-026r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1133","type":"D-DP","creator":"Mike Botts","contributor":null,"description":"The Sensor Model Language work proposes an XML schema for describing the geometric, dynamic, and observational characteristics of sensor types and instances.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-04-22","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"942":{"title":"Geography Markup Language","alternative":"Geography Markup Language","URI":null,"identifier":"00-029","URL":"https://portal.opengeospatial.org/files/?artifact_id=7197","type":"D-RP","creator":"Ron Lake","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2000-05-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"943":{"title":"High-Level Ground Coordinate Transformation Interface","alternative":"High-Level Ground Coordinate Transformation Interface","URI":null,"identifier":"01-013r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1006","type":"D-DP","creator":"Arliss Whiteside","contributor":null,"description":"This document specifies a ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-02-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"944":{"title":"Web Coordinate Transformation Service","alternative":"Web Coordinate Transformation Service","URI":null,"identifier":"02-061r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1174","type":"D-DP","creator":"Andreas Poth, Markus Muller","contributor":null,"description":"This document specifies the transformations of geo-spatial coordinates from one Coordinate Reference System (CRS) into another by means of a Web Service","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-09-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"945":{"title":"Web Map Context Documents","alternative":"Web Map Context Documents","URI":null,"identifier":"02-066r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1181","type":"D-RP","creator":"Jean-Philippe Humblet","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-08-29","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"946":{"title":"WMS Part 2: XML for Requests using HTTP Post","alternative":"WMS Part 2: XML for Requests using HTTP Post","URI":null,"identifier":"02-017r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1118","type":"DP","creator":"Jeff de La Beaujardiere","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-08-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"947":{"title":"Observations and Measurements","alternative":"Observations and Measurements","URI":null,"identifier":"02-027","URL":"https://portal.opengeospatial.org/files/?artifact_id=1137","type":"D-DP","creator":"Simon Cox","contributor":null,"description":"This document describes a framework and encoding for measurements and observations.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-05-31","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"948":{"title":"Web Terrain Server","alternative":"Web Terrain Server","URI":null,"identifier":"01-061","URL":"https://portal.opengeospatial.org/files/?artifact_id=1072","type":"DP","creator":"Raj Singh","contributor":null,"description":"The purpose of theWeb Terrain Server (WTS) is to produce perspective views of georeferenced data - typically 3-dimensional coverages.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-08-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"949":{"title":"XML for Image and map Annotation","alternative":"XML for Image and map Annotation","URI":null,"identifier":"01-019","URL":"https://portal.opengeospatial.org/files/?artifact_id=1020","type":"DP","creator":"John Evans","contributor":null,"description":"Defines an XML vocabulary to encode annotations on imagery, maps, and other geospatial data. This vocabulary draws on the Geography Markup Language (OpenGIS","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-02-06","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"950":{"title":"Web Registry Server","alternative":"Web Registry Server","URI":null,"identifier":"01-024r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1028","type":"D-DP","creator":"Louis Reich","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-01-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"951":{"title":"Basic Services Model","alternative":"Basic Services Model","URI":null,"identifier":"01-022r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1024","type":"D-DP","creator":"Jeff de La Beaujardiere","contributor":null,"description":"The Basic Services Model is an implementation of the ISO TC211 services architecture as found in ISO 19119 Geographic Information ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-05-05","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"952":{"title":"Location Organizer Folder","alternative":"Location Organizer Folder","URI":null,"identifier":"01-037","URL":"https://portal.opengeospatial.org/files/?artifact_id=1042","type":"Retired","creator":"Ron Lake","contributor":null,"description":"*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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-03-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"953":{"title":"Geoparser","alternative":"Geoparser","URI":null,"identifier":"01-035","URL":"https://portal.opengeospatial.org/files/?artifact_id=1040","type":"Retired","creator":"Jeff Lansing","contributor":null,"description":"*RETIRED* Geoparsing refers to the capability to process a textual document and identify key words and phrases that have a spatial context.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-03-27","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"954":{"title":"Gazetteer","alternative":"Gazetteer","URI":null,"identifier":"01-036","URL":"https://portal.opengeospatial.org/files/?artifact_id=1041","type":"D-DP","creator":"Rob Atkinson","contributor":null,"description":"An authority for place names. Returns their associated geometries","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-03-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"955":{"title":"Gazetteer Service Profile of a WFS","alternative":"Gazetteer Service Profile of a WFS","URI":null,"identifier":"05-035r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=13593","type":"D-DP","creator":"Jens Fitzke, Rob Atkinson","contributor":null,"description":"Provides web access to an authority for place names. Returns their associated feature representations","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2006-01-12","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"956":{"title":"Geocoder","alternative":"Geocoder","URI":null,"identifier":"01-026r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=1031","type":"Retired","creator":"Serge Margoulies","contributor":null,"description":"*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.)","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-03-28","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"957":{"title":"Web Coverage Service","alternative":"Web Coverage Service","URI":null,"identifier":"02-024","URL":"https://portal.opengeospatial.org/files/?artifact_id=1131","type":"D-RP","creator":"John Evans","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-06-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"958":{"title":"Geography Markup Language","alternative":"Geography Markup Language","URI":null,"identifier":"01-029","URL":"https://portal.opengeospatial.org/files/?artifact_id=1034","type":"D-RP","creator":"Ron Lake","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-02-20","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"959":{"title":"Web Map Service","alternative":"Web Map Service","URI":null,"identifier":"01-047r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=1058","type":"D-IS","creator":"Jeff de La Beaujardiere","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-06-21","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"960":{"title":"Web Map Service","alternative":"Web Map Service","URI":null,"identifier":"00-028","URL":"https://portal.opengeospatial.org/files/?artifact_id=7196","type":"D-IS","creator":"Allan Doyle","contributor":null,"description":"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.  ","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2000-04-19","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"961":{"title":"Topic 9 - Accuracy","alternative":"Topic 9 - Accuracy","URI":null,"identifier":"99-109r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=896","type":"D-AS","creator":"Cliff Kottman, Arliss Whiteside","contributor":null,"description":"Topic 9 has been combined into AS Topic 11","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-03-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"962":{"title":"Topic Domain 1 - Telecommunications Domain","alternative":"Topic Domain 1 - Telecommunications Domain","URI":null,"identifier":"01-042","URL":"https://portal.opengeospatial.org/files/?artifact_id=1046","type":"AS","creator":"Tom Strickland","contributor":null,"description":"Domain Model for telecommunications Networks","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-10-09","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"963":{"title":"Topic 17 - Location Based Mobile Services","alternative":"Topic 17 - Location Based Mobile Services","URI":null,"identifier":"00-117","URL":"https://portal.opengeospatial.org/files/?artifact_id=988","type":"AS","creator":"Cliff Kottman","contributor":null,"description":"Draft Abstract Spec for Location Based Services. Never formally adopted","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2000-05-15","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"964":{"title":"Topic 16 - Image Coordinate Transformation Services","alternative":"Topic 16 - Image Coordinate Transformation Services","URI":null,"identifier":"00-116","URL":"https://portal.opengeospatial.org/files/?artifact_id=7200","type":"AS","creator":"Cliff Kottman, Arliss Whiteside","contributor":null,"description":"Covers image coordinate conversion services.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2000-04-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"965":{"title":"Topic 15 - Image Exploitation Services","alternative":"Topic 15 - Image Exploitation Services","URI":null,"identifier":"00-115","URL":"https://portal.opengeospatial.org/files/?artifact_id=7199","type":"AS","creator":"Cliff Kottman, Arliss Whiteside","contributor":null,"description":"Describes the categories and taxonomy of image exploitation services needed to support the use of images and certain related coverage types.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2000-04-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"966":{"title":"Topic 13 - Catalog Services","alternative":"Topic 13 - Catalog Services","URI":null,"identifier":"99-113","URL":"https://portal.opengeospatial.org/files/?artifact_id=901","type":"AS","creator":"Cliff Kottman","contributor":null,"description":"Covers the Geospatial Information Access Services","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-03-31","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"967":{"title":"Topic 14 - Semantics and Information Communities","alternative":"Topic 14 - Semantics and Information Communities","URI":null,"identifier":"99-114","URL":"https://portal.opengeospatial.org/files/?artifact_id=902","type":"AS","creator":"Cliff Kottman","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-04-04","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"968":{"title":"Topic 10 - Feature Collections","alternative":"Topic 10 - Feature Collections","URI":null,"identifier":"99-110","URL":"https://portal.opengeospatial.org/files/?artifact_id=897","type":"AS","creator":"Cliff Kottman","contributor":null,"description":"An OpenGIS Feature Collection is an abstract object consisting of Feature Instances, their Feature Schema, and Project Schema.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-04-07","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"969":{"title":"Topic 8 - Relationships Between Features","alternative":"Topic 8 - Relationships Between Features","URI":null,"identifier":"99-108r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=894","type":"AS","creator":"Cliff Kottman","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-03-26","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"970":{"title":"Topic 5 - Features","alternative":"Topic 5 - Features","URI":null,"identifier":"99-105r2","URL":"https://portal.opengeospatial.org/files/?artifact_id=890","type":"D-AS","creator":"Cliff Kottman","contributor":null,"description":"A feature object (in software) corresponds to a real world or abstract entity.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-03-24","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"971":{"title":"Topic 4 - Stored Functions and Interpolation","alternative":"Topic 4 - Stored Functions and Interpolation","URI":null,"identifier":"99-104","URL":"https://portal.opengeospatial.org/files/?artifact_id=887","type":"AS","creator":"Cliff Kottman","contributor":null,"description":"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).","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-03-30","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"972":{"title":"Topic 3 - Locational Geometry Structures","alternative":"Topic 3 - Locational Geometry Structures","URI":null,"identifier":"99-103","URL":"https://portal.opengeospatial.org/files/?artifact_id=886","type":"AS","creator":"Cliff Kottman","contributor":null,"description":"Provides essential and abstract models for GIS technology that is widely used.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-03-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"973":{"title":"Topic 12 - The OpenGIS Service Architecture","alternative":"Topic 12 - The OpenGIS Service Architecture","URI":null,"identifier":"02-112","URL":"https://portal.opengeospatial.org/files/?artifact_id=1221","type":"AS","creator":"ISO","contributor":null,"description":"Same as ISO 19119","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-09-14","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"974":{"title":"Topic 11 - Metadata","alternative":"Topic 11 - Metadata","URI":null,"identifier":"01-111","URL":"http://www.iso.org/iso/en/CatalogueDetailPage.CatalogueDetail?CSNUMBER=26020","type":"D-AS","creator":"ISO","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-06-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"975":{"title":"Topic 7 - Earth Imagery","alternative":"Topic 7 - Earth Imagery","URI":null,"identifier":"99-107","URL":"https://portal.opengeospatial.org/files/?artifact_id=892","type":"D-AS","creator":"Cliff Kottman","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-03-31","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"976":{"title":"Topic 6 - The Coverage Type","alternative":"Topic 6 - The Coverage Type","URI":null,"identifier":"00-106","URL":"https://portal.opengeospatial.org/files/?artifact_id=7198","type":"D-AS","creator":"Cliff Kottman, Charles Roswell","contributor":null,"description":"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.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2000-04-18","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"977":{"title":"Topic 2 - Spatial Referencing by Coordinates","alternative":"Topic 2 - Spatial Referencing by Coordinates","URI":null,"identifier":"02-102","URL":"https://portal.opengeospatial.org/files/?artifact_id=1220","type":"D-AS","creator":"Roel Nicolai","contributor":null,"description":"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","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2002-03-08","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"978":{"title":"Topic 1 - Feature Geometry","alternative":"Topic 1 - Feature Geometry","URI":null,"identifier":"01-101","URL":"https://www.iso.org/standard/26012.html","type":"AS","creator":"John Herring","contributor":null,"description":"Same as ISO 19107, available at http://www.iso.org.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"2001-05-10","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null},"979":{"title":"Topic 0 - Overview","alternative":"Topic 0 - Overview","URI":null,"identifier":"99-100r1","URL":"https://portal.opengeospatial.org/files/?artifact_id=11496","type":"D-AS","creator":"Cliff Kottman","contributor":null,"description":"Introduction and roadmap to the Abstract specification.","publisher":"Open Geospatial Consortium","language":"English","license":null,"source":null,"rights":"","isPartOf":null,"date":"1999-06-23","dateAccepted":null,"dateSubmitted":null,"format":null,"hasFormat":null,"extent":null}}

data/lib/relaton_ogc/data/etag.txt

@@ -0,0 +1 @@
+"71818c439e4326ccb4b24a797aaf5ba2f6fcb949"

data/lib/relaton_ogc/editorial_group.rb

@@ -0,0 +1,66 @@
+module RelatonOgc
+  # OGC project group.
+  class EditorialGroup
+    include RelatonBib
+
+    COMMITTEES = %w[technical planning strategic-member-advisory].freeze
+
+    # @return [String]
+    attr_reader :committee
+
+    # @return [RelatonIsoBib::IsoSubgroup]
+    attr_reader :subcommittee
+
+    # @return [RelatonIsoBib::IsoSubgroup]
+    attr_reader :workgroup
+
+    # @param committee [String]
+    #
+    # @param subcommittee [Hash, RelatonIsoBib::IsoSubgroup]
+    # @option subcommittee [String] :name
+    # @option subcommittee [String] :type
+    # @option subcommittee [Integer] :number
+    #
+    # @param workgroup [Hash, RelatonIsoBib::IsoSubgroup]
+    # @option workgroup [String] :name
+    # @option workgroup [String] :type
+    # @option workgroup [Integer] :number
+    def initialize(committee:, **args)
+      unless COMMITTEES.include? committee
+        raise ArgumentError, "committee is invalid: #{committee}"
+      end
+
+      @committee    = committee
+      @subcommittee = subgroup args[:subcommittee]
+      @workgroup    = subgroup args[:workgroup]
+    end
+
+    # @param builder [Nokogiri::XML::Builder]
+    def to_xml(builder)
+      builder.editorialgroup do
+        builder.committee committee
+        builder.subcommittee { subcommittee&.to_xml builder } if subcommittee
+        builder.workgroup { workgroup&.to_xml builder } if workgroup
+      end
+    end
+
+    # @return [Hash]
+    def to_hash
+      hash = { "committee" => committee }
+      hash["subcommittee"] = subcommittee.to_hash if subcommittee
+      hash["workgroup"] = workgroup.to_hash if workgroup
+      hash
+    end
+
+    private
+
+    # @param group [Hash, RelatonIsoBib::IsoSubgroup]
+    # @return {RelatonIsoBib::IsoSubgroup}
+    def subgroup(group)
+      if group.is_a?(Hash)
+        RelatonIsoBib::IsoSubgroup.new(group)
+      else group
+      end
+    end
+  end
+end