Loading...

2018-08-22This 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.

Reports - royal academy of engineering

As a result of this work, the IE participants agree that the extension is fit for use and consideration as a standard by OGC 6 Jul 2018 - Technical reports that are not available in full text on the web or in Novanet libraries There is also a search bar in the top right hand corner..

2018-04-26The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives.

•Apply Open Geospatial Consortium (OGC) principles and practices for collaborative development to existing standards and technology to prototype an IoT approach to sensor use for incident management. •Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability.

•Develop profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability. •Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario.

2018-04-23The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives: • Apply OGC principles and practices for collaborative development to existing standards and technology to prototype an IoT approach to sensor use for incident management; • Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability; • Develop profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability; and • Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario. Based on the findings gathered during the implementation and work on these objectives, this Engineering Report describes recommendations on profiles for OGC Web services that shall be used to build IMIS systems.

2018-03-05Portrayal 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. , eXtensible Markup Language (XML) schemas and Style Layer Descriptors (SLD)). With this approach, interoperability does not extend to the semantic level, which makes it difficult to share, reuse and mediate unambiguous portrayal information between agencies.

This Engineering Report (ER) captures the requirements, solutions, models and implementations of the Testbed 13 Portrayal Package. This effort leverages the work on Portrayal Ontology development and Semantic Portrayal Service conducted during Testbed 10, 11 and 12.

The objective of this Testbed 13 is to identify and complete the gaps in the latest version of the portrayal ontology defined in Testbed 12, complete the implementation of the Semantic Portrayal Service by adding rendering capabilities and performing a demonstration of the portrayal service that showcases the benefits of the proposed semantic-based approach. 2018-03-05This OGC Testbed 13 Engineering Report (ER) documents the overall architecture developed in the "Interoperability of 3D Tiles and I3S using a 3D Portrayal Service and performance study of 3D tiling algorithms" activity.

The report also summarizes a proof-of-concept of the use of 3D Tiles and I3S as data delivery formats for the OGC 3D Portrayal Service interface standard. The report captures the results from the interoperability tests performed as part of the 3D Tiles and I3S testbed work package.

Specifically, this OGC Testbed activity focused on the following tasks: CityGML files converted into Cesium 3D Tiles using Analytical Graphics (AGI’s) 3D Tiling Pipeline, and Cesium as the rendering client; An OGC CDB data store converted into 3D Tiles using Compusult’s Streaming engine, Cesium and Ecere’s GNOSIS as rendering client; CityGML data store GeoRocket, 3DPS with 3D Tiles as data delivery format, and Cesium as rendering client; CityGML converted into I3S, 3DPS with I3S as data delivery format, and Cesium as rendering client; CityGML converted into I3S using ArcGIS and FME, 3DPS with I3S as data delivery format, and rendering in ArcGIS client; CityGML with application domain extension stored in GeoRocket, converted to 3D Tiles, and Cesium as the rendering client; 3D Tiles (generated by all streaming engines visualized) from Ecere’s GNOSIS rendering client; CDB visualized directly from Ecere’s GNOSIS rendering client; and I3S visualized from Ecere’s GNOSIS rendering client. 2018-03-05This Engineering Report (ER) has been produced in conjunction with two other engineering reports from the OGC Testbed 13, the Abstract Data Quality ER 4 and the Data Quality Specification ER 5 to capture status quo, discussions, and results in the context of requirements for data quality assessment for Quality of Service in the Aviation Domain.

It will, in particular, provide a Data Quality Assessment Service Specification. Much of the ER is presented in the future tense, using terms such as 'shall', in order to express requirements and constraints on future Data Quality Assessment Service implementations.

The service specification includes design patterns, extension mechanisms, and service interface considerations. In recent years, the concept of data quality has generated a notable interest among System Wide Information Management (SWIM) 17 implementers, both organization-specific and global.

In the context of SWIM — and Service Oriented Architecture (SOA) implementations in general — data quality pertains to two major use cases, service advertising and service validation: Service advertisinga service makes known to a potential consumer the quality of the data provided by the service. Based on this information, the consumer can determine whether or not the service meets its needs.

Service validationassurance is given that the quality of the data provided by a service is consistent with the quality that is explicitly defined in a service contract or any kind of agreement that may exist between a service provider and service consumer. Both use cases share two common preconditions: An unambiguous definition of the concept of data quality exists.

A set of measurable parameters that allow specifying data quality is defined. These are tasks that were performed as part of Testbed 13.

The findings of the tasks are documented in the Abstract Data Quality ER (FA001) 4 and the Data Quality Specification ER (FA002) 5 . 2018-02-22The design of core OGC Web Services (OWS) does not entertain the possibility of network unavailability, internet unavailability, or disconnected clients and datastores.

Deployments of these services, and the clients that consume them, often happen in networking environments that have limited bandwidth, sporadic connectivity and no connection to the internet. This Engineering Report (ER) focuses on situations of Denied, Degraded, Intermittent, or Limited Bandwidth (DDIL).

Due to these DDIL networking limitations, OWS services and clients may not be capable of effective data exchange and interpretation due to a reliance on external resources and "always-on" networks. This ER concerns the behavior of common OWS services when used in DDIL environments.

The ER documents proposed practices/considerations for implementation of these services to support these environments. The ER also describes software modules or extensions that might mitigate the effects of these environments on both clients and services.

This ER intends to guide client and service implementation, as well as deployment strategies for these challenging environments. 2018-02-22This 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: /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. 2018-02-07Disasters are responsible for major socioeconomic damages.

Global initiatives call for the improvement of information technology infrastructure to better share data and advance multinational collaboration. The "Strengthening Disaster Risk Reduction Across the Americas: A Regional Summit on the Contributions of Earth Observations" held on September 3-8 in 2017 in Buenos Aires, Argentina strengthened the collective ability to share the many challenges of disaster risk reduction in Latin America and the Caribbean (LAC) while promoting the awareness and better use of earth observations (EO).

A simulation exercise took place during the summit. The exercise brought together government, emergency managers, earth observation data providers, academics, non-governmental organizations, and commercial companies.

The participants assessed the capabilities and needs of policymakers, regional and on-the-ground decision makers, and learned what information products can be produced, and when and how such products are available. This ER describes the description and results of the simulated scenario including the post-exercise activity that captured the lessons learned from the participants.

2018-01-30The Application Package OGC Engineering Report (ER) defines a data model and serialization for Thematic Exploitation Platforms (TEP) Application Packages. A TEP refers to a computing platform that follows a given set of scenarios for users, data and ICT provision aggregated around an Earth Science thematic area.

This ER is part of the Testbed-13 Earth Observation Clouds (EOC) effort to support the development by the European Space Agency (ESA) of the TEP by exercising envisioned workflows for data integration, processing, and analytics based on algorithms developed by users that are deployed in multiple clouds. The wide usage of virtualization and the possibility to start virtual environments within Cloud services significantly simplifies the creation of environments and provisioning of resources.

However, it still leaves a problem of portability between infrastructures. This ER identifies a strategy for packaging an application in a Cloud environment that will be able to run in a predictable manner in different computing production environments.

The application packaging specifies the elements that will ensure: Scientific reproducibility, Dependencies identification and management, Maintainability from an operational perspective and avoid version pilling, Portability in different Cloud providers The ER proposes the use of containers, defining everything required to make a piece of software run packaged into isolated containers. Unlike a Virtual Machine (VM), a container does not bundle a full Operating System (OS) - only libraries and settings required to make the software work are needed.

This makes for efficient, lightweight, self-contained systems and guarantees that software will always run the same, regardless of where it’s deployed. A discussion on application deployment and execution is presented in the separate OGC Testbed-13 Application Deployment and Execution Service ER 1 .

2018-01-26This 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.

2018-01-26OGC 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.

2018-01-26The 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. National System for Geospatial-Intelligence (NSG). NGA utilizes the open source software tool ShapeChange as an integral piece in NAS development.

This tool is used to take NAS-based UML models and create Extensible Markup Language (XML) and Resource Description Framework (RDF) based schemas. Testbed-12 began development of capabilities for extracting profiles supporting specific mission functions from the full NAS content.

Testbed-13 further refined the approach to NAS Profiling by investigating how a specific profile ("Urban Military Profile") can be processed in an automated way and used to derive implementation schemas for the OGC standards CDB and CityGML. This OGC Engineering Report describes: The specification of a NAS-based Military Urban Profile as a Unified Modeling Language (UML) model (chapter 5); How mission-specific sub-profiles can be specified and maintained using ShapeChange and the new ShapeChange Profile Management Tool (chapter 6); and How the model and profile information are processed to derive output for a CDB data store (chapter 7, chapter 8) and a CityGML Application Domain Extension (chapter 9).

This work provides insights into: The requirements and constraints on managing profiles of complex ISO 19109 compliant application schemas such as the NAS; and Using a model-driven approach to generate implementation schemas of an ISO 19109 compliant application schema profile for different environments. The target audience of this document is anyone interested in these topics.

The implementation environments discussed in this report are the OGC standards CDB and CityGML. This report assumes that readers are familiar with the key concepts and technologies discussed in this document. This document does not provide an introduction to them, but the table below provides a brief summary and pointers to more information.

2018-01-18The objective of the Fit for Purpose (FFP) effort in Testbed 13 was to develop and test filters and encodings in a platform that can ease the work of end-users, especially those who are not expert in dealing with geospatial data and satellite imagery. The platform was demonstrated in a scenario that showed how these filters can enable information exchange for humanitarian relief and analysis of mass movement of populations.

This section provides a summary of the interoperability tools and practices used by Testbed 13 participants in this platform. It includes descriptions and testing results of filters and encodings to help simplify access to satellite imagery.

This technology was tested in a scenario that showed how OGC-based services, encodings, filters and applications can help coordinate humanitarian relief activities among nations and organizations. 2018-01-18The Incident Management Information Sharing (IMIS) Internet of Things (IoT) Pilot established the following objectives.

· Apply Open Geospatial Consortium (OGC) principles and practices for collaborative development to existing standards and technology in order to prototype an IoT approach to sensor use for incident management. · Employ an agile methodology for collaborative development of system designs, specifications, software and hardware components of an IoT-inspired IMIS sensor capability.

· Development of profiles and extensions of existing Sensor Web Enablement (SWE) and other distributed computing standards to provide a basis for future IMIS sensor and observation interoperability. · Prototype capabilities documented in engineering reports and demonstrated in a realistic incident management scenario.

These principles continued through the IoT Pilot Extension, with additional objectives of: · Integration into the existing Next Generation First Responder (NGFR) Apex development program process as part of Spiral 1; · Defining steps to begin the integration of existing incident management infrastructure, e. , pulling in National Institute of Emergency Management (NIEM) message feeds; and · Demonstration and experimentation in a ‘realistic’ incident environment using two physically separate sites–an incident site within an active first responder training facility (Fairfax County Lorton site), and a command center (DHS S&T Vermont Avenue facility). The initial Pilot activity has been documented in three OGC public engineering reports.

The present report describes and documents the additional activities and innovations undertaken in the Extension. 2018-01-17The objective of the Mass Migration Source Integration effort in OGC Testbed 13 was to understand and document how interoperability tools and practices, including open geospatial and security standards, can enable information exchange on an international level for humanitarian relief and analysis of mass movement of populations.

This Engineering Report describes how Testbed 13 participants tested and demonstrated situational awareness using Internet and web technologies in a shared information exchange platform. The purpose of this platform was to help realize a Common Operational Picture (COP) for coordinating humanitarian relief activities among nations and organizations.

In addition, the platform exercised security-enabled interoperable exchange of messages. 2018-01-11This 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. This Engineering Report describes: The conceptual model of an OGC CDB 1.

0 datastore as a UML (Unified Modeling Language) diagram to show different datasets (the 3D models, vector features and coverages) structure; How to process and use a NAS-based Profile as a CDB feature/attribute data model or a GML-SF0 application schema; How to access, navigate and visualize a CDB dataset using OGC web services (such as WFS and WCS). This work provides insights into: The in-depth study of the OGC CDB 1.

0 feature data dictionary and attribution schema; The requirements and constraints for extending the CDB feature data dictionary (FDD) and attribute schemas; The development and prototyping of the WFS and WCS access to the CDB datastore for a NAS based urban military scenario.

Technical report writing - online course for engineers - futurelearn

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 Get a writing assistance engineering report Formatting Academic online Best website to purchase a engineering report British High School Academic Editing..

MapML is needed because while Web browsers implement HTML and Scalable Vector Graphics (SVG), including theelement, 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 theelement in HTML to include the accessible user interface functions of modern web maps (e.

panning, zooming, searching for, and zooming to, styling, identifying features’ properties, etc.

), while maintaining a simple, declarative, accessible interface for HTML authors. The objective of this Engineering Report is to explore how MapML can be harmonized with the OGC standards mainstream and contribute to the progress of the specification avoiding unnecessary duplication.

In particular, the ER proposes Web Map Service (WMS) or Web Map Tile Service (WMTS) as services that can be used to deliver MapML documents with small modifications. Another consideration on the ER is the inclusion of the time dimension and directions operation in MapML.

2018-01-11The Security Engineering Report (ER) covers two Testbed 13 topics: The implementation of authentication and authorization plugins for the QGIS open source desktop GIS client and the implementation of secured workflow. The authentication plugins implement the SAML2 ECP with PAOS binding and IdP discovery from the SAML2 federation metadata URL.

The access right delegation plugin implements applicable OAuth2 grant types. Regarding the first topic, this ER discusses the "fit for purpose" aspects for the OAuth2 and SAML2 in the context of an open source desktop application.

It also covers the QGIS development as well as building and deployment aspects. Most of the work related to this topic was provided by Secure Dimensions.

Regarding the second topic, this ER outlines the architecture approach and the implications to implementations for security in OGC service workflows as well as the implementation approach itself. Most of the work related to this topic was provided by 52°North.

2018-01-11This 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. Such a set of metadata (commonly referred to as a service description) has been defined by Federal Aviation Administration (FAA) and European Organization for the Safety of Air Navigation (EUROCONTROL) and formalized in a Service Description Conceptual Model (SDCM) SDCM .

The SDCM is currently used in standard service description documents and service registries by both FAA and EUROCONTROL. As part of the effort of enhancing service discovery, both organizations also use a number of categories that can be associated with all services and are generally referred to as taxonomies.

The current set of taxonomies used by both EUROCONTROL and FAA categorizes (i. , 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. 2018-01-11This 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. 2018-01-08This Engineering Report (ER) addresses the development of a consistent, flexible, adaptable workflow that will run behind the scenes.

A user should be able to discover existing workflows via a catalog and execute them using their own datasets. An expert should be able to create workflows and to publish them.

Previous OGC Testbed initiatives investigated workflows in the geospatial domain: OWS 3 Imagery Workflow Experiments OWS 4 WPS IPR Workflow descriptions and lessons learned OWS 4 Topology Quality Assessment Interoperability Program Report OWS 5 Data View Architecture Engineering Report OWS 6 Geoprocessing Workflow Architecture Engineering Report These initiatives mostly favored Business Processing Execution Language (BPEL) as the workflow execution language. More recent studies ( 6 , 7 ) were performed using BPMN as a means for describing and executing workflows comprised of OGC Web services.

This ER will give an overview about existing approaches to compose and execute geospatial workflows and will describe the approach taken in Testbed-13, taking into account security aspects. 2018-01-08This 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. 2018-01-08This OGC Engineering Report (ER) will describe the use of OGC Web Processing Service (WPS) for cloud architecture in the OGC Testbed 13 Earth Observation Cloud (EOC) Thread.

This report is intended to address issues in lack of interoperability and portability of cloud computing architectures which cause difficulty in managing the efficient use of virtual infrastructure such as in cloud migration, storage transference, quantifying resource metrics, and unified billing and invoicing. This engineering report will describe the current state of affairs in cloud computing architectures and describe the participant architectures based on use case scenarios from sponsor organizations.

Cloud computing is paving the way for future scalable computing infrastructures and is being used for processing digital earth observation data. In this EOC thread effort, data is stored in various storage resources in the cloud and accessed by an OGC Web Processing Service.

The methods in which these processes are deployed and managed must be made interoperable to mitigate or avoid the complexities of administrative effort for the scientific community. In other words, the intent of this effort is to develop a way for scientists to acquire, process, and consume earth observation data without needing to administer computing cloud resources.

2018-01-08This Engineering Report (ER) describes the development of the compliance tests and implementation in GeoServer of the Web Feature Service (WFS) 2. 0 National System for Geospatial Intelligence (NSG) profiles. The NSG of the United States (US) National Geospatial Intelligence Agency (NGA) is the combination of technologies, policies, capabilities, doctrine, activities, people, data and communities needed to produce geospatial intelligence (GEOINT) in an integrated, multi-intelligence, multi-domain environment.

The work can be grouped into four main topics: critical review of the NSG profiles for WFS 2. 0 implementation of the profiles in GeoServer validation of the implementation using OGC Compliance tests and tools lessons learn during the implementation of these profiles and their validation Both NSG profiles are Class 2 profiles. The first topic provides a review of these profiles along with a description of the main extensions and restrictions introduced by them.

The second topic covers the implementation of the NSG profiles in GeoServer. It describes the software architecture and technical decisions, along with the deployment and configuration of the server.

The third topic covers the validation process of the implementation using OGC validation (sometimes referred to as CITE) tests and tools. It also covers how the tests can be run and how to configure GeoServer for these tests.

The last topic contains an evaluation of the work, reached goals, lessons learned and the best practices that can be applied in future work. 2018-01-01This OGC document provides an analysis of the prototype implementations, approaches and performance aspects of data serialization techniques explored in OGC Testbed 13.

Specifically, it describes work done during Testbed 13 investigating serialization for geospatial data sets on OGC Web Feature Service (WFS) using Google Protocol Buffers (Protobuf) and Apache Avro. Protocol buffers are Google’s language-neutral, platform-neutral, extensible mechanism for serializing structured data.

They are described by Google in the following manner - 'think XML, but smaller, faster, and simpler'. With Protobuf Google indicates developers can define how they want their data to be structured once, then they can use special generated source code to easily write and read structured data to and from a variety of data streams and using a variety of languages.

Apache Avro is described as a remote procedure call and data serialization framework developed within Apache’s Hadoop project. It uses JavaScript Object Notation(JSON) for defining data types and reportedly serializes data in a compact binary format.

2017-10-20The 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. 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. 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:// /aSQFIPwf2oM2017-08-18his 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.

2017-06-30One 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.

Service profiles are an important aspect of the WPS 2.

0 Conflation Profile could look like in the hierarchical profiling approach of WPS 2. 2017-06-30This Data Quality Engineering Report describes data quality handling requirements, challenges and solutions.

Best website to get engineering report 2018 reportfast.win

In addition, it discusses WPS data quality solutions School of Engineering and Informatics (for staff and students) and gives hints on how to go about drafting and refining a report in order to in the text (including any lecture notes and URL addresses of any websites used. Binding, A single staple in the top left corner or 3 staples spaced down the left hand margin..

The ultimate goal is for it to be nominated as a WPS ISO Data Quality Service Profile.

ISO 19139 is used as the base to encode the data quality. WPS and workflows are used to streamline and standardize the process of data quality assurance and quality control.

The main topics include: (1) generalized summary and description of the design and best practices for analyzing data quality of all feature data sources used in the Citizen Observatory WEB (COBWEB) project, (2) solutions and recommendations for enabling provenance of data quality transparent to end users when the data is processed through a WPS, (3) best practices and recommendations for designing and prototyping the WPS profile to support data quality service conformant to the NSG Metadata Framework, and (4) general solution for data quality fit for both raster-based imageries and vector-based features. 2017-06-30An important principle of a Service Oriented Architecture (SOA) is the notion of composing capabilities provided by individual services into complex behavior.

A requester should be able to compose a solution using functionality or data offered by multiple services without worrying about underlying differences in those services. Each OGC service is designed to offer a specific type of data product via a service-specific interface.

This Engineering Report (ER) describes a single service interface that allows access to multiple data sources, possibly heterogeneous with respect to the types of data provided. This report advances the work started in OGC Testbed 11 with the addition of heterogeneous data sources, as well as several other enhancements.

2017-06-30Most of current OGC specifications define synchronous communication patterns, i. after sending a request to an OGC service, clients need to wait for the response. 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. 2017-06-30The amount of (geospatial) data collected and transferred is rapidly increasing.

The purpose of this ER is to describe options and recommendations for the delivery of large amounts of data as database delivery. This ER therefore describes and evaluates different aspects of this challenge: Data management: How to organize large amounts of data so that it can be efficiently accessed through OGC service interfaces? Encoding: Transferring large amounts of vector data in XML based formats (e.

GML, O&M) leads to specific challenges as the parsing of large XML files is often problematic.

Available implementation: Several software packages exist to handle large amounts of geospatial data. We will investigate to which these approaches are in-line with OGC standards or how standards compliance could be achieved.

The evaluation and findings in the related Big Data Tile Database Implementation are documented in this ER as well. The objective of this ER is to provide recommendations of how the delivery of large amounts of raster data as database delivery can be considered within OGC specifications and future activities.

2017-06-19This engineering report examines the role of geospatial semantic technology in the domain of civil aviation. Many aeronautical services (providing information on request or processing the data) are based on OGC Web Service specifications.

A number of aeronautical services possess geospatial attributes. The aviation services follow OWS Common Service requirements but also have domain specific capabilities.

Services metadata is often very relevant for service consumption, especially in the SOA environment of aviation’s System Wide Information Management (SWIM). Therefore, it shall be exposed to consumer stakeholders for either design or runtime service discovery in an efficient, standardized way.

This ER starts introducing the WSDOM service ontology developed by FAA for semantic service discovery. It proposes several extensions useful for OWS compatible, geospatial aviation services.

It combines GeoSPARQL with WSDOM ontology and FAA service classification taxonomies and elaborates the interoperability between ontology based WSDOM and OWS compatible service descriptions. 2017-06-19The FAA and EUROCONTROL, in conjunction with multiple other international partners, are currently in the process of developing the Flight Information Exchange Model (FIXM).

FIXM is an exchange model capturing Flight and Flow information that is globally standardized. The need for FIXM was identified by the International Civil Aviation Organization (ICAO) Air Traffic Management Requirements and Performance Panel (ATMRPP) in order to support the exchange of flight information as prescribed in Flight and Flow Information for a Collaborative Environment (FF-ICE).

FIXM is the equivalent, for the Flight domain, of Aeronautical Information Exchange Model (AIXM) and Weather Information Exchange Model (WXXM), both of which were developed in order to achieve global interoperability for, respectively, Aeronautical Information Systems (AIS) and Meteorological Information (MET) exchange. FIXM is therefore part of a family of technology independent, harmonized and interoperable information exchange models designed to cover the information needs of Air Traffic Management.

Previous OGC IP initiatives developed an architecture that supports the exchange of AIXM and WXXM data. This report shall describe the integration of Geography Markup Language (GML) profile elements into FIXM, specifically, the Feature, Time, Geometries and Units of Measure (UOM), into FIXM version 3.

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.

2017-06-16This 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.

2017-06-16At the time of finalizing this ER the OGC TC has approved the OWS Context JSON encoding that is available here: /standards/owc This is the second encoding proposed for the OWS context standard precided by the Atom Encoding OGC 12-084r2 . The OWS Context JSON enconding is based on the GeoJSON IETF standard RFC7946 .

The standard is a combination of two approaches: mapping between the OWS Context conceptual model 12-080r2 to the basic structure of a GeoJSON file. a direct conversion of the rest of the atom keys and the specific OWS Context XML into JSON following OGC 14-009r1.

The conversion was designed with current GeoJSON viewers in mind (including the one embedded in GitHUB) and making possible that they can visualize a OWS Context GeoJSON file without any modifications. This ER focus on describing another encoding (a 3rd alternative) that allows for exposing geospatial resources on the web in a way that web browsers and search engines can better understand.

It is widely known that HTML was designed with the linking capacity in mind. Both, users reading HTML and automatic crawlers, transverse links constantly.

HTML seems the natural selection for linking geospatial data on the web. The question is how to complement the linking mechanism with some additional metadata that search engines could use for indexing.

A solution could come from a mechanism which web search engines already have agreed to use for better indexing: . 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 model to recognize that they are very similar and propose a encoding in HTML5 that can be done in the 3 alternative proposed by . 2017-06-16With the consolidation of tiling services and the increasing number of instances implementing the WMTS standard, there is a need for having a way to transfer a collection of tiles from one service to another.

This might also be useful to transfer all necessary tiles from a WMTS service to a GeoPackage. Currently the only available solution is a client that is able to resolve the identifiers of the tiles needed and that builds a WMTS independent request for each tile.

This ER explores different solutions that are more appropriate depending on how many tiles we need to move and the final application of them. Some of the proposed solutions involve changes in the WMTS standard and the use of a WPS.

The WPS standard also shows some limitations and extensions that should be addressed. In essence all solutions should describe two things: A request that contains a filter to a collection of tiles filling regions of the space and a multipart response that contains the tiles preferably in a single package.

Depending on the proposed architecture, these tasks are done directly in the client, in the WMTS server or in an intermediate WPS. 2017-06-16This OGC Testbed 12 Engineering Report discusses the topic of vector tiling.

While tiling and the use of multiple levels of details are a proven technique for raster data, it is relatively new for vector data. This is due to the increased complexity for tiling vector data compared to raster tiling.

Further, there is a lack of standardization on the topic. Yet vector tiles can provide the same benefits as for raster tiles: Services can easily cache tiles and return them upon request, without the need for any additional pre/post processing (assuming no geometry construction is needed in the server).

Consequently, clients can request and receive tiles quickly, ensuring better user experience. Due to tiled, multileveled data representations, clients can better access the data most suitable for their current map location and scale.

This avoids the need to load too much data, which can cause both excessive memory usage and network traffic resulting in reduced overall performance. An example of vector tiling that illustrates the impact of these benefits is the OpenStreetMap (OSM) data store, which includes over 30 GB of data with worldwide coverage consisting of millions of vector features.

Loading and visualizing all the OSM data into an application would either result in a memory shortage or unacceptable performance. By means of vector tiling and the generation of multiple levels of detail, apps using OSM data can load such data sets very efficiently into applications.

This Engineering Report (ER) focuses on the general aspects of vector tiling. One of the main goals is to characterize what vector tiling is and how it can be approached.

Highlighted topics include tiling approaches and strategies, tiling schemes, data coherence, simplification, scalability and styling. With respect to tiling schemes, existing standards material related to raster tiling schemes is incorporated to align both topics and to maximize interoperability.

This includes the Defence Geospatial Information Working Group (DGIWG) Web Map Tiling Standard (WMTS) profile and the National System for Geospatial-Intelligence (NSG) WMTS profile as defined by the U. The topic of implementing vector tiles using a tile encoding / storage format is not covered.

A study of implementing vector tiles in OGC GeoPackage is part of a separate Engineering Report, OGC 16-067, that builds on the results of this ER. 2017-05-22The OGC service metadata document (sometimes also called "capabilities" document) is a key part in the service discovery.

It describes the service and also the resources that the service expose. Resources are listed in the service metadata document inside a section named as Contents by OWS Common.

There are two main limitations to the current Contents section approach: OWS Common offers flexibility for describing resources and it only proposes a very minimum set of metadata in figure 7 of OGC 06-121r9 called DatasetSummary that need to be sub-classed (i. As a result, each standard proposes its own alternative for it.

Integrated client developers need to implement them separately. If the number of resources is very large or the service is highly dynamic, the Contents section can be too long or useless and neither the service nor the client can handle it efficiently.

This Engineering Report proposes a double solution to the Contents section of the service metadata documents: It proposes ways to encode the Contents section using the OWS Context encoding data types and it introduces the use OpenSearch as a way to request a subset of the resources that the service can provide access to. In that sense, the use of the OGC 10-032r8 OpenSearchGeo can provide the long time needed geospatial and temporal filter capabilities.

2017-05-15This OGC Testbed 12 Engineering Report (ER) discusses the topic of implementing vector tiles in an OGC GeoPackage. This report builds on the general topic of vector tiling discussed in OGC Testbed 12 Engineering Report OGC 16-068r4 .

Since its public release in 2012, OGC GeoPackage has been getting increasingly popular within the geospatial industry for a variety of use cases, such as a means to package geospatial data for use on a mobile device and as a means to exchange geospatial data between two systems. The OGC GeoPackage standard currently specifies requirements (rules) for storing raster tiles and vector (simple) features.

This Engineering Report proposes an extension to the supported data types by introducing an implementation for vector tiles.

While tiling and the use of multiple levels of details are a proven technique for accessing and visualizing raster data, it is less commonly applied for vector data An engineering report presents to the reader an engineering problem and the will find that the significance of good form in reports becomes more critical: once .

This is due to the increased complexity compared to raster tiling and lack of standardization on the topic.

Find technical reports - chemical engineering - libguides at

Services can easily cache tiles and return them instantly upon request, without the need for any additional pre/post processing. Consequently, clients can get tiles very fast, ensuring fast and responsive maps.

Using tiled, multileveled data representations, clients can always access the data most suitable for their current map location and scale. This avoids the need to load too much data, which can cause excessive memory usage and reduce overall performance.

The goal is to enable systems to use OGC GeoPackage as a means to store and access vector tiles in an efficient way, similar to raster tiles. 2017-05-15This 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. The investigation focused on extending WFS with EXI output formats, and the associated performance aspects of data size reduction and compression techniques. EXI is a compact representation for the Extensible Markup Language (XML) Information Set.

EXI is intended to simultaneously optimize performance and the utilization of computational resources. From a practical viewpoint, EXI is designed to reduce the size of XML data exchanged between computer systems.

EXI uses a grammar-driven approach designed to achieve efficient encodings using an encoding algorithm and a small set of datatype representations. Consequently, EXI processors are described by the W3C as €˜relatively simple €™ and €˜can be implemented on devices with limited capacity.

€™ An EXI processor is used by application programs to encode their structured data into EXI streams and/or to decode EXI to make the structured data accessible. 2017-05-15This engineering report has been produced by the OGC ® Testbed-12 initiative.

The engineering report evaluates interoperability between a variety ofcatalogues. The report presents a comparison of the catalogues, with the samedatasets uploaded.

The catalogues discussed in the report include servicesconforming to Catalogue Service for Web (CSW) version 2. 0, includingservices based on the ebRIM profile of CSW 2.

The engineering report presents results from testsusing a multi-catalogue client to interact with each service.

The engineeringreport also provides a comparison of CSW and services based on the DataCatalogue (DCAT) specification covering functionality, expressiveness andusability of CSW and DCAT. The comparison is supported by a discussion on theimplementation of a SPARQL / GeoSPARQL service.

2017-05-12With 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.

2017-05-12The National System for Geospatial-Intelligence (NSG) GeoPackage Profile defines and tailors the implementable provisions prescribed for the NSG for a GeoPackage based on the OGC GeoPackage encoding standard. The profile provides detailed directions on how to use the clauses, options and parameters defined in the base GeoPackage standard.

The goal is to ensure that NSG GeoPackages, GeoPackage SQLite Extensions, and supporting utilities and services fulfill their intended purposes and are fit for use. The goal of this Engineering Report (ER) is to assess whether requirements as specified in the proposed profile are specific enough to allow for any two independent GeoPackage implementers to produce and consume interoperable NSG GeoPackages.

Concerns with the profile are outlined and recommendations for improvement are provided. Thoughts on the viability of the profile approach and guidance on how the profile could apply to Vector Tiling are also provided.

2017-05-12The 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.

2017-05-12This document is a deliverable of the OGC Testbed-12. It describes the results of analyzing the Testbed-12 web service implementations.

OGC has been developing web service specifications since the OGC Web Mapping Testbed in 1999. In particular, the original OGC Web Map Service specification has been developed during that testbed.

17 years later most current OGC web service standards still follow the general approach that had been developed in 1999 (the capabilities document, the remote procedure call via HTTP paradigm, etc). Over time, the OGC web service approach has been amended and extended in different ways by different OGC standards and profiles.

In addition, some of the more flexible mechanisms have been used in practice in different ways by different software vendors or communities. The OGC Web Service Common standard had been a response by OGC to these developments and aimed at maintaining a consistent approach across the different OGC web service standards.

However, this effort has been only partially successful for several reasons, including shortcomings in the OWS Common standard, the existence of multiple incompatible OWS Common versions and a reluctance by working groups and communities to introduce incompatible changes to existing service types in order to harmonize. All attempts in recent years to continue the work on OWS Common have not seen much traction.

While there seems to be general agreement that the current situation is not optimal and that consistency is desirable, it is unclear how to improve in a way that meets market demands. This document summarizes information about the web service implementations in Testbed-12.

It is not and should not be understood as a general analysis or assessment of the OGC web service architecture, but a low-key effort to gain some insights from looking at a significant number of web service implementations and their use in interoperability experiments and demos. During the years since 1999 not only the OGC standards baseline has evolved, but also the Web itself.

The W3C has been working on identifying Best Practices for Data on the Web and W3C and OGC are jointly working on extending this with Best Practices for Spatial Data on the Web. The analysis also includes an assessment about the OGC approach to web services with respect to the draft best practices at the time of writing of this report.

To the extent possible, we draw conclusions and recommendations from the information that has been gathered. These fall into three categories: Improving the interoperability of OGC web services as they are today Support for new requirements in a consistent way across service types Improvements to the standardization process In addition, there is also a specific case that does not fit into these general categories.

2017-05-12For 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.

2017-05-12The Testbed-11 deliverable OGC 15-053 Implementing JSON/GeoJSON in an OGC Standard ER enumerated strategies for implementing JSON in OGC services and OGC encodings. Previously, a mechanism to migrate XML into JSON was proposed by Pedro Gon §alves in 14-009r1 OGC Testbed-10 Rules for JSON and GeoJSON Adoption: Focus on OWS-Context.

In contrast, this engineering report (ER) proposes a mechanism to derive JSON and JSON-LD encodings from UML modeling without using XML as an intermediate step. The rules provided can be divided into rules for JSON instances and rules for JSON schemas.

These rules have been applied to the UML diagrams in OWS common 2. 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.

Finally, this ER discusses the applicability to data geospatial formats, both for coverage formats (compared to the CIS standard) and feature formats (compared to GeoJSON).

Readers unfamiliar with JSON, JSON-LD and JSON Schema should first read OGC 16-122 (Geo)JSON User Guide. OGC 16-122 includes guidelines and recommendations for the use of JSON and JSON-LD in OGC data encodings and services.

2017-05-12This 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.

2017-05-12The scenario of rapidly growing geodata catalogues requires tools focused on facilitating users the choice of products. Having populated quality fields in metadata allows the users to rank and then select the best fit-for-purpose products.

For example, decision-makers would be able to find quality and uncertainty measures to take the best decisions as well as to perform dataset intercomparison. In addition, it allows other components (such as visualization, discovery, or comparison tools) to be quality-aware and interoperable.

This ER deals with completeness, logical consistency, positional accuracy, temporal accuracy and thematic accuracy issues to improve quality description in the metadata for imagery. Based on ISO 19157, UncertML and QualityML standardized measures, this ER describes how to encode quality measures in order to allow datasets comparison.

Moreover, description of pixel-level quality measures is also included. Finally, alternatives to communicate tile level quality as well as mosaic products quality are proposed.

2017-05-12This 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. In particular, this document proposes the following: Specific PubSub 1.

0, leveraging on standard functionalities, data models, and semantics to enable sending notifications based on user-specified area of interest and/or keywords; A general, basic mechanism for enabling PubSub for the generic OGC Web Service over the existing request/reply OWS €™s, i.

usual requests as filters, usual responses as appropriate updates/data pushes, existing semantics and syntax expressiveness.

This document is the result of activity performed within the Large-Scale Analytics (LSA) Thread of the OGC Testbed 12 Interoperability initiative, being identified as document deliverable "A074 PubSub / Catalog Engineering Report". This document also captures lessons learnt from the implementation of component deliverable "A016 CSW 2.

2017-04-28This 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.

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 Engineering & Science Professional Body Benchmarking Report 2017 The Royal Academy of Engineering and ECUK have together produced a We use cookies to optimise site functionality and give you the best possible experience..

Engineering reports | ogc

The example of GetCapabilites, DescribeEOCoverageSet, and GetCoverage request in the updated EO-WCS1. 1 is shown with use case on fire emission data in San Francisco.

Following the recommendation for EO-WCS to fully embrace the N-D, multi-dimensional, concept of Coverages as a function of time and other coordinates alongside the geospatial ones, the proposed recommendations/changes in the extension for WCS DescribeCoverage, EO-WCS DescribeEOCoverageSet, and WCS GetCoverage are discussed with use case example using National Centers for Environmental Prediction (NCEP) Global 0. Based on the mutual recommendation from the US National Aeronautics and Space Administration (NASA) and Baart et. al (2012), Network Common Data Form (NetCDF) was the output format due to presence of its libraries in multiple languages to lower the burden in changing on developers of WCS-compliant servers and clients.

For the extension of the WCS DescribeCoverage, it is recommended that CIS1. 1 should be considered adopting a scheme for transmitting coordinates similar to the cis:rangeSet where data are referred to as an attached Multipurpose Internet Mail Extensions (MIME) part.

Time, as much as possible, be treated as just another coordinates dimension so that it could be access with the same tools used for other coordinate dimensions. To tackle the issue on order of coordinate dimensions, it is recommended to add implementation note to the EO-WCS specifications so that implementers are aware of the mismatches between dataset coordinate reference systems (CRSs) and actual axis order.

For the extension of EO WCS DescribeEOCoverageSet, the issue on missing range of results API needed to be resolved by adding a request mechanism for requesting a range of matching results. It is also recommended that DescribeEOCoverageSet activity might be of more use to the client if the client need to supply only the subset conditions, and not a list of identifiers.

For the extension of WCS GetCoverage, it was discovered that for the GetCoverage operation for higher dimensioned datasets, existing WCS-2. 0 request interface provided adequate syntax for subsetting higher dimensional data.

Scaling (re-gridding) operation appears to be a natural fit for the EO-WCS subsetting, specifically SCALEEXTENT activity, however simpler explanation might be needed to fully understand its use as it appears other scaling and subsetting commands may be more than adequate for the desired outcomes. Additionally allowing SlicePoint subsetting is also recommended.

After performing the testing in the client side, there were few potential recommendations for improvements. More information on whether the coverage is 2D or 3D form the GetCapalilites request might be helpful to client so it can limit the number of DescribeCoverage requests to construct a list of available coverage on the server.

Furthermore additional metadata information for displaying meaningful native gird coordinates is also recommended for clarification. Finally automatic detection of lat/lon axes along with clear treatment of XY and lat/lon axes ordering would be an improvement in the existing operations.

2017-04-28This 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. 1 OGC 10-140r2 ) have removed the requirement for the 2D coverages so that it can explicitly allow coverages with more dimensions as long as they have geographic footprint. Furthermore it also clarified the use of rangeType when non-NCNAME characters are present in a band identifier.

The example of GetCapabilites, DescribeEOCoverageSet, and GetCoverage request in the updated EO-WCS1. 1 is shown with use case on fire emission data in San Francisco.

Following the recommendation for EO-WCS to fully embrace the N-D, multi-dimensional, concept of Coverages as a function of time and other coordinates alongside the geospatial ones, the proposed recommendations/changes in the extension for WCS DescribeCoverage, EO-WCS DescribeEOCoverageSet, and WCS GetCoverage are discussed with use case example using National Centers for Environmental Prediction (NCEP) Global 0. Based on the mutual recommendation from the US National Aeronautics and Space Administration (NASA) and Baart et. al (2012), Network Common Data Form (NetCDF) was the output format due to presence of its libraries in multiple languages to lower the burden in changing on developers of WCS-compliant servers and clients.

For the extension of the WCS DescribeCoverage, it is recommended that CIS1. 1 should be considered adopting a scheme for transmitting coordinates similar to the cis:rangeSet where data are referred to as an attached Multipurpose Internet Mail Extensions (MIME) part.

Time, as much as possible, be treated as just another coordinates dimension so that it could be access with the same tools used for other coordinate dimensions. To tackle the issue on order of coordinate dimensions, it is recommended to add implementation note to the EO-WCS specifications so that implementers are aware of the mismatches between dataset coordinate reference systems (CRSs) and actual axis order.

For the extension of EO WCS DescribeEOCoverageSet, the issue on missing range of results API needed to be resolved by adding a request mechanism for requesting a range of matching results. It is also recommended that DescribeEOCoverageSet activity might be of more use to the client if the client need to supply only the subset conditions, and not a list of identifiers.

For the extension of WCS GetCoverage, it was discovered that for the GetCoverage operation for higher dimensioned datasets, existing WCS-2. 0 request interface provided adequate syntax for subsetting higher dimensional data.

Scaling (re-gridding) operation appears to be a natural fit for the EO-WCS subsetting, specifically SCALEEXTENT activity, however simpler explanation might be needed to fully understand its use as it appears other scaling and subsetting commands may be more than adequate for the desired outcomes. Additionally allowing SlicePoint subsetting is also recommended.

After performing the testing in the client side, there were few potential recommendations for improvements. More information on whether the coverage is 2D or 3D form the GetCapalilites request might be helpful to client so it can limit the number of DescribeCoverage requests to construct a list of available coverage on the server.

Furthermore additional metadata information for displaying meaningful native gird coordinates is also recommended for clarification. Finally automatic detection of lat/lon axes along with clear treatment of XY and lat/lon axes ordering would be an improvement in the existing operations.

2017-04-25This 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.

2017-04-25The 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.

The design of this architecture will cover methods for subscribing for specific subsets of data (e.

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. This report focuses on the interface design required to define an interoperable approach for Aviation using this OGC PubSub 1. , 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. 2017-04-25The 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. The design of this architecture will cover methods for subscribing for specific subsets of data (e. 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.

This report focuses on the interface design required to define an interoperable approach for Aviation using this OGC PubSub 1.

, 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.

2017-03-10The 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.

However, OWS Common neglected to address security. As soon as a service endpoint (an OGC Web Service instance) is secured, there is no guarantee of interoperability.

The OWS Common - Security Standards Working Group (SWG) was approved by the TC in September 2015 ( /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.

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).

This ER shall serve as the technical background to the OWS Common - Security SWG to ensure that the standard that is to be created is comprehensive and suitable for all OGC Web Services standards, to overcome the interoperability hurdle, and - at the same time - maintain backwards compatibility. 2017-03-10For 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.

A client or user cannot easily determine which source data was used to create the map and how to download that source data though an OGC data service such as WFS or WCS.

Furthermore when one considers the Publish-Find-Bind paradigm, OGC can only partially support the full potential of this paradigm. This is because OGC structured catalogues can only register services in isolation of other related services and cannot automatically determine the relationships among services and the resources they offer.

In order to achieve better integration between OGC web services and enhance the publish-find-bind paradigm, this OGC Engineering Report defines and discusses three key elements. These are: Defining a new service, called the Web Integration Service (WIS), which allows for the discovery and access to integrated sets of OGC web services deployed at an endpoint.

Specifying a means of discovering and describing associations between web resources (both OGC and non-OGC). Defining extensions to the OGC catalogue to allow the service to harvest and make discoverable a rich set of linked OGC and non-OGC resources.

The Web Integration Service (WIS) is an aggregation service whose only purpose is to provide a list of references to a suite of other, perhaps related OGC services available at an endpoint. A new operation, named GetAssociations, is defined as an extension such that existing OGC services (WMS, WFS, WCS, etc.

) may implement this operation in order to support rich auto-discovery. This operation enables OGC web services to externalize their internal association knowledge about their content and relationships to other OGC and external resources.

For example, a WMS would know if the source data for a layer it offers is a Shapefile, or a WFS feature type, or another WMS layer (i. 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 This PowerPoint slide presentation covers major aspects of writing reports in Engineering. Click on the link above in the Media box to download the slides..

Currently, OGC Catalogues Service instances can harvest the capabilities document of an OGC web service, register that service, register the existence of the individual offerings that the service offers and also register the association between the service and the content it offers.

Engineering reports - the purdue university online writing lab

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.

2017-03-09This engineering report describes a protocol for synchronizing data between two enterprise servers. While the protocol itself is generic, this engineering report describes its application to web feature servers.

In the simplest terms, the protocol involves each synchronization peer accessing the other’s "Sync" resource to get the set of changed objects since the last time the "Sync" resource was accessed. In the case of web feature servers, the objects are features.

The requesting peer then compare that list of changed features with the identically identified features in its data store and performs any necessary changes so that the feature states match. Continuing the work done in Testbed-11, this engineering report describes the implementation of a Sync operation in a WFS server that: Enhances the Sync operation from Testbed-11 to include an abstract query element where each service type can then substitute their specific query syntax for identifying the specific sub-set of changed features to be synchronized.

In the case of the WFS, several query syntaxes may be used including the wfs:Query element and a REST based feature type URI with query parameters. Extends the definition of the Sync operation with the addition of a "resultType" parameter to allow a client to obtain a hit count of the number of features that a Sync operation shall return.

Shall investigate the proper procedure for handling resource references. Implementing the resolvePath parameter alone is not sufficient to ensure complete data set synchronization.

Shall investigate concurrency and consistency issues. 2017-03-08This 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. 2016-08-01This OGC Engineering Report specifies the results and findings of the CityGML QualityInteroperability Experiment.

Guidelines were developed for the following concepts:􀀀 Definition of data quality;􀀀 Data quality requirements and their specification;􀀀 Quality checking process of CityGML data; and􀀀 Description of validation results. The desired outcomes of this Interoperability Experiment are to improve theinteroperability of CityGML data by removing some ambiguities from the currentstandard and formally defining data quality requirements for a general CityGML dataspecification.

Further, the results of this work provides to the community (organizationsinvested in capturing, procuring, or utilizing CityGML data) recommendedimplementation guidance for 3D data and a suite of essential quality checking tools tocarry out quality assurance on CityGML data. 2016-07-26This engineering report describes the results of the Soil Data Interoperability Experiment(the IE) conducted under the auspices of the OGC Agriculture Domain Working Group in2015.

Soil data exchange and analysis is compromised by the lack of a widely agreedinternational standard for the exchange of data describing soils and the sampling andanalytical activities relating to them. Previous modeling activities in Europe andAustralasia have not yielded models that satisfy many of the data needs of global soilscientists, data custodians and users.

This IE evaluated existing models and proposed acommon core model, including a GML/XML schema, which was tested through thedeployment of OGC web services and demonstration clients. IE time constraints andlimited participant resources precluded extensive modeling activities.

However, theresulting model should form the core of a more comprehensive model to be developed bya future OGC Soil Data Standards Working Group. 2016-02-03A 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.

aspects that should be harmonized by a cross-standard working group.

This document seeks to provide an overview of the current situation and guidance on future SOAP harmonization across all OGC Web services. A number of change requests have been developed during the development process for this document.

Though this document provides recommendations in chapter 8, it is highly recommended to either form a new SOAP working group, or preferably to assign the development of SOAP best practices to reduce the risk of missed requirements and architecture arguments to the newly reformed OWS Common SWG. The best practices could then be applied to all OGC service standards that offer SOAP bindings.

2016-01-28This document presents an assessment of the conformance level, with respect to the WFS standard (OGC 09-025r2), of the web feature servers used in the OGC Testbed-11. Each server is accessed to determine if it conforms to the minimum requirements of the WFS standard.

Each server is further accessed to determine whether the server offers additional, upcoming and complimentary capabilities just as support for the WFS REST API and GeoJSON. This document offers recommendations to aid implementers of the WFS standard (OGC 09-025r2).

This document presents options available to WFS implementers for achieving interoperability between WFS clients and server at the schemas level. This document includes a survey of available WFS clients and an assessment of their capabilities.

This document reviews tools and standards, such as the GeoSynchronization Service (OGC 10-069r3), that are complimentary components that may be used with a WFS to address requirements such as verification and notification, data and access security, exception handling and system hardening. Finally, this document includes a FAQ composed of questions raised during the OGC Testbed-11.

2016-01-25The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community(IC) concurrence of the National Information Exchange Model (NIEM) Version 3. 0architecture through the development, implementations, test, and robust demonstrationmaking use of IC specifications, Geography Markup Language (GML), and NIEM in asimulated “real-world” scenario.

The demonstration scenario begins with NIEMconformantInformation Exchange Packages (IEPs) containing operational data and ICsecurity tags from the Information Security Marking (ISM) and Need-To-Know (NTK)access control metadata, and the Trusted Data Format (TDF) for binding assertionmetadata with data resource(s). Those instance documents are deployed using OpenGeospatial Consortium (OGC) standards enabled Web Services for use by clientapplications.

Access control is based on attributes of the end-user and the instance data. Recommendations to update these information exchanges were provided to reflect NIEM3.

0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessment testedthis data encoding in OGC Web Feature Services (WFS) and Policy Enforcement Points(PEP) accessed by multiple client applications.

Results from this task provided apreliminary architecture that was tested and demonstrated in Testbed 11, and summarizedin other OGC Testbed 11 Engineering Reports. The demonstrations also highlighted howNIEM and IC data encodings together may support more agile and customer-centricframeworks driven by collaborative partnerships.

This transformation is vital toconfronting the security challenges of the future. 2016-01-25The goal of the Geo4NIEM thread in Testbed 11 was to assess the potential for the National Information Exchange Model (NIEM) to be combined with security tags from Intelligence Community (IC) Data Encoding Specifications for information exchange.

The assessment included reviewing Information Exchange Package Documentation (IEPD) populated with relevant content and IC security tags – and then deploying these instance documents on Open Geospatial Consortium (OGC) standards enabled Web Services for testing. The security tags included Information Security Marking Metadata (ISM) and Need-to-Know (NTK) Metadata for secure information exchange.

The assessment included reviewing example IEPDs and performing tests and demonstrations using OGC web services, such as Transactional Web Feature Services (WFS-T), Policy Enforcement Points (PEPs) and OGC Attribute Stores to process geographic feature with NIEM components and security tags. The Test and Demonstration included, but was not limited to, feature retrieval and transactions.

Results were documented in this task to provide a preliminary architecture for Geo4NIEM in Testbed 11, and were described in technical detail in other OGC Testbed 11 Engineering Reports. This document describes background considerations – and an overview of the services, data encodings and access control frameworks that compose the Geo4NIEM Testbed 11 architecture.

This document must be reviewed in conjunction with the following Testbed 11 Geo4NIEM ERs:•15-048 Testbed11 Engineering Report NIEM-IC Data Encoding Specification Assessment and Recommendations•15-047 Testbed11 Engineering Report NIEM-IC Feature Processing API using OGC Web Services•15-050 Testbed11 Engineering Report Test and Demonstration Results for NIEM using IC Data Encoding Specifications 2016-01-25The 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 dataRecommendations 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. 2016-01-25The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community (IC) concurrence of the National Information Exchange Model (NIEM) Version 3.

0 architecture through the development, implementations, test, and robust demonstration making use of IC specifications, Geography Markup Language (GML), and NIEM in a simulated “real-world” scenario. The demonstration scenario begins with NIEM-conformant Information Exchange Packages (IEPs) containing operational data and IC security tags from the Information Security Marking (ISM) and Need-To-Know (NTK) access control metadata, and the Trusted Data Format (TDF) for binding assertion metadata with data resource(s).

Those instance documents are deployed on Open Geospatial Consortium (OGC) Web Services to be used by client applications. Access control is based on attributes of the end-user and the instance data.

The assessment included reviewing example IEPDs and performing test and demonstrations using OGC web services, such as Transactional Web Feature Services (WFS-T), Policy Enforcement Points (PEPs) and OGC Attribute Stores to process geographic feature with NIEM components and security tags. The Test and Demonstration included, but was not limited to feature retrieval and transactions.

Recommendations to update these information exchanges were provided to reflect NIEM 3. 0 architecture and security tags in a ‘NIEM/IC Feature Processing API’.

Results from this task helped provide a preliminary architecture for Geo4NIEM in Testbed 11, summarized in other OGC Testbed 11 Engineering Reports. This task also identified potential change requests to OGC WFS or other OGC Services for handling security information in a federated role-based access control environment.

These changes may help the NIEM/IC transform into more agile and customer-centric frameworks driven by collaborative partnerships. This transformation is vital to confronting the security challenges of the future.

2016-01-25The goal of the Geo4NIEM thread in Testbed 11 was to gain Intelligence Community(IC) concurrence of the National Information Exchange Model (NIEM) Version 3. 0architecture through the development, implementations, test, and robust demonstrationmaking use of IC specifications, Geography Markup Language (GML), and NIEM in asimulated “real-world” scenario.

The demonstration scenario begins with NIEMconformantInformation Exchange Packages (IEPs) containing operational data and ICsecurity tags from the Information Security Marking (ISM) and Need-To-Know (NTK)access control metadata, and the Trusted Data Format (TDF) for binding assertionmetadata with data resource(s). Those instance documents are deployed on OpenGeospatial Consortium (OGC) Web Services to be used by client applications.

Accesscontrol is based on attributes of the end-user and the instance data. Recommendations to update these information exchanges were provided to reflect NIEM3.

0 architecture and security tags in a ‘NIEM/IC Data Encoding’. The assessmentexercised this data encoding in OGC Web Feature Services (WFS) and PolicyEnforcement Points (PEP) accessed by multiple client applications.

Results from this taskprovided a preliminary architecture that was tested and demonstrated in Testbed 11, andsummarized in other OGC Testbed 11 Engineering Reports. 2016-01-18This 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. 2015-11-19Routing 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. 2015-11-18This OGC Engineering Report (ER) describes work done in OGC Testbed 11 to testGMLJP2 in terms of defining a DGIWG GMLJP2 version 1 profile.

The requirements for a DGIWG profile of GMLJP2 have been documented in theDGIWG GMLJP2 version 1 profile.

Where to get engineering report 2018 reporthlp.win

The DGIWG implementation of the GMLJP2 profile is based on the OGC GMLJP2 v2and other requirements are coming directly from the adoption inside the DGIWG of thenew OGC GMLJP2 version 2 Communicating and Learning in Engineering Online Resources. 1 Engineering Faculty, Monash University. Key features of reports. Reports: You don't have to place the number i on the title page. Good reference for report writing:..

This Testbed 11 activity is a response to the need of harmonization between DGIWG andOGC. 2015-10-30Developed by EUROCONTROL, the Aviation Feature Schema (AFX) is a template forapplication schemas to implement by adding their operational attributes.

For example, theAirport Mapping format can be implemented by extending AFX. The AFX definesconcepts of geometry and temporality through predefined classes and properties.

Therefore, these elements need not be redefined by application schemas. This meansimplementations of the AFX abide by the same structure, therefore aiding interoperabilityand allowing the rapid development of schemas.

The AFX schema is designed to begeneric and easily reusable and it is not intended to replace the standard aviation modelssuch as WXXM and AIXM. This Engineering Report assesses the suitability of the AFX as a template for loweringthe GIS entry level for aviation data, providing recommendations of suitability and areasof improvement.

The report is aimed at system and client developers that shall use AFX. 2015-10-01Over 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. , 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.

2015-10-01This 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. 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.

2011), (2) semantic association, which enables current catalogue information models to support semantic search (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. 2015-08-19Mobile location based service applications and users have an increasing need for access to geospatial data from any place in the world, including locations with limited or intermittent connectivity to communications networks.

Maintaining consistency between copies of the same data held by different mobile devices can be a significant challenge when connectivity is limited or intermittent. This OGC Engineering Report describes the work carried out in OGC Testbed-11 in relation to the creation and synchronization of SQLite databases that conform to the OGC GeoPackage standard .

This Engineering Report describes an approach for the use of various standards to achieve such synchronization. The document also presents the results and lessons learnt from the experimentation conducted in the Testbed.

2015-08-19This 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.

2015-03-26The 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.

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.

0 Part 2, is a candidate standard that defines how to exchange rating tables, gauging observations and cross-sections in an interoperable manner.

This engineering report outlines the design and results of an OGC Interoperability Experiment (IE) that implemented and tested the current WaterML2. The OGC IE experiment ran was conducted from November 2013 to August 2014. The use case for the IE involved exchange of data in three scenarios in Australia, US and the UK.

This report describes the software requirements, design, deployments and challenges faced by the experiment. 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.

2014-11-03This OGC® document summarizes the Aircraft Access to SWIM (AAtS) Harmonization activity developed by a team funded by the FAA and led by the Open Geospatial Consortium (OGC). The activity involved assembling a core team of industry participant experts to analyze and harmonize four standards suites and/or standards-based architectures relevant to air-ground information exchange:•The Aircraft Access to SWIM (AAtS) concept, •RTCA aeronautical information services (AIS) and meteorological (MET) information data link service committee’s (SC-206) concepts and standards, •Air-Ground Information Exchange A830 (AGIE) standard and •OGC standards and architectural perspectives.

Elements of this effort have included:•Creation and public release of a Request for Information•Analysis of the fits and overlaps between the four standards suites•Engagement with ongoing standards development efforts to reduce incompatibilities 2014-08-22This document describes the Web Services Fa ade which was developed by LISAsoft as part of the OWS-9 testbed. The document also includes discussions about lessons learned during the development, and suggestions for future development.

This Engineering Report documents the Web Services Fa ade work done within OWS-9 as an extensible, open source tool, which supports translations between different protocols for a specific web service. For the OWS-9 testbed, it has been set up to translate between POST and SOAP services for a Web Feature Service.

However, it can be configured to support translations between multiple protocols, such as REST, SOAP, KVP, JSON, as well as supporting multiple web services. The Web Services Fa ade is an extensible, open source tool, which supports translations between different protocols for a specific web service.

For the OWS-9 testbed, it has been set up to translate between POST and SOAP services for a Web Feature Service. However, it can be configured to support translations between multiple protocols, such as REST, SOAP, KVP, JSON, as well as supporting multiple web services.

2014-07-16This report provides guidance for implementing the Flight Information Exchange Model (FIXM) using the same best practice as the Aeronautical Information Exchange Model (AIXM) and the Weather Information Exchange Model (WXXM) by adopting ISO and OGC standards. The report is aimed at system and client developers that shall use the FIXM data encoding for the exchange of flight information.

This document is a deliverable for the OGC Testbed 10 (Testbed-10) testbed activity. OWS testbeds are part of OGC's Interoperability Program, a global, hands-on and collaborative prototyping program designed to rapidly develop, test and deliver proven candidate standards or revisions to existing standards into OGC's Standards Program, where they are formalized for public release.

In OGC's Interoperability Initiatives, international teams of technology providers work together to solve specific geoprocessing interoperability problems posed by the Initiative's sponsoring organizations. OGC Interoperability Initiatives include testbeds, pilot projects, interoperability experiments and interoperability support services - all designed to encourage rapid development, testing, validation and adoption of OGC standards.

The Testbed-10 sponsors are organizations seeking open standard for their interoperability requirements. After analyzing their requirements, the OGC Interoperability Team recommends to the sponsors that the content of the Testbed-10 initiative be organized around the following threads:•Cross-Community Interoperability (CCI)•Open Mobility•AviationMore information about the Testbed-10 tested can be found at: /standards/requests/1032014-07-16This activity is part of OGC Testbed 10.

The aviation thread was focused on developing and demonstrating the use of the Aeronautical Information Exchange Model (AIXM) and the Flight Information Exchange Model (FIXM), building on the work accomplished in prior testbeds to advance the applications of OGC Web Services standards in next generation air traffic management systems to support European and US aviation modernization programs. This document provides the result of the Testbed 10 to assess the compliance between the OGC standards and the guidelines provided by the SAE in their latest published document regarding portraying of NOTAMs.

Specifically, the Human Based Portrayal of DNOTAM work attempts to fulfill the high level requirements identified in the OGC Testbed-10 RFQ Annex B . The purpose of this investigation was to analyze the recommendations of the SAE comity and to evaluate the feasibility of their application using OGC standards for portraying, namely the Symbology Encoding standard, version 1.

2014-07-15This document is a deliverable of the OGC Testbed 10 (Testbed-10).

Its contents cover the summary of the work carried out regarding the recommendations for the exchange of terrain data. Suggested additions, changes, and comments on this draft report are welcome and encouraged.

Such suggestions may be submitted by email message or by making suggested changes in an edited copy of this document. The changes made in this document version, relative to the previous version, are tracked by Microsoft Word, and can be viewed if desired.

If you choose to submit suggested changes by editing this document, please first accept all the current changes, and then make your suggested changes with change tracking on. 2014-07-14The provenance activities reported in this document were part of the OGC Testbed 10Cross Community Interoperability (CCI) thread.

This OGC® document gives guidelinesfor the capture and documentation of provenance information at dataset, feature andattribute level. It only considers vector features (mainly, points and lines) and does notelaborate on the coverage data model (so it does not talk about provenance of rasterinformation).

It proposes an approach to use the W3C PROV standard with geospatialinformation that can come from different sources and are integrated through differentprocessing steps. It also reviews the applicability of ISO19115 and ISO19115-2 lineage.

2014-07-14This activity is part of OGC Testbed 10. The aviation thread was focused on developingand demonstrating the use of the Aeronautical Information Exchange Model (AIXM) andthe Flight Information Exchange Model (FIXM), building on the work accomplished inprior testbeds to advance the applications of OGC Web Services standards in next generationair traffic management systems to support European and US aviation modernizationprogramsThis document summarizes technical work relating to the enhancement of the GML 3.

1conformance test suite in accord with the requirements in the OWS-10 RFQ, Annex B1,section 6.

6: “GML for Aviation Compliance Test Suite + GML for Aviation ConformanceTesting ER”.

The essential aim is to advance compliance with respect to the use ofGML geometry representations in aviation (AIXM) data. 2014-04-28This Engineering Report was prepared as a deliverable for OGC Testbed 10, an initiative of the OGC Interoperability Program.

The document presents the work completed with respect to the Cross Community Interoperability (CCI) thread within the testbed. The work has been commissioned in order to inform geospatial information frameworks of the Defence Geospatial Information Working Group (DGIWG), National System for Geospatial Intelligence (NSG) of the US National Geospatial Intelligence Agency (NGA) and the UK Ministry of Defence (MOD).

The Engineering Report presents an analysis and assessment of interoperability between DGIWG, NSG and UK MOD profiles of Web Map Service (WMS) and Web Feature Service (WFS) standards of the OGC. The engineering report also presents findings from the implementation of the reference profiles.

2014-02-24This document provides a technical description of the work completed for the Climatology-Hydrology Information Sharing Pilot, Phase 1 project. This document describes a profile of SOS, the NRCan GIN SOS 2.

0 profile, developed in order to define a baseline of interoperability among the sensor observation services used in the project. This document describes the use cases used to drive the component development during the project.

The first use case was a flood scenario that involved exchanging cross-border hydrologic data with a unified alert service. The second use case involved calculating nutrient loads to the Great Lakes, which also involved the cross-border exchange of analytic data.

This document describes each component developed during the project and the challenges encountered and overcome during the development.

Engineering reports | department of electrical and computer

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 Get an introduction to technical report writing with this online course from The Explain what a good technical engineering report is and what they are used for..

2013-11-07Geospatial information technologies are increasingly a foundation for supporting Information Sharing Environment (ISE), homeland security (HLS), homeland defense (HLD), law enforcement (LE), emergency management (EM) and public safety missions in the US. The inability to transport, deliver and exchange geospatial information for critical geospatial assets increases the risk to the nation.

Many ISE HLS/HDS/LE mission partners have developed stand-alone geospatial information systems (GIS) or Common Operating Picture (COP) applications to support their stakeholder communities during incidents and for daily operational support. While different missions, these GIS/COP capabilities rely upon much of the same data or generate specific data during an event.

The data are often stove-piped and not exposed to a broader community that could benefit from these data, resulting in duplication and delayed or incorrect decisions. While mission partners do not need to use the same GIS/COP tools, they could benefit from shared access to the common operating data and services used within these systems if they were exposed and exchanged using open standards.

Under the auspices of the Program Manager for the Information Sharing Environment (PM-ISE), an identified government-wide information sharing shortfall will be resolved by funding work to enhance the National Information Exchange Model (NIEM). The focus of this work is to further enhance the framework’s geospatial exchange capability in light of guidelines and standards issued by the Open Geospatial Consortium (OGC) so as to significantly improve inter-government information sharing.

2013-06-18This document is a deliverable of the OGC Web Services (OWS) Initiative - Phase 9 (OWS-9). This Engineering Report summarizes the OWS-9 activity regarding the extension of the Web Feature Service (WFS) and Filter Encoding (FE) standards to support dynamic feature data.

Specifically this document describes the result work performed in OWS 9 on the WFS Temporality Extension. The technical specification including background is discussed and defined in the OGC Discussion Paper 12-027r1.

This document gives a summary about issues, lessons learned, recommendations, accomplishments and benefits for the Aviation Architecture. It also gives an outlook on future work items and change requests.

2013-06-18This OGC Engineering Report describes the results of the OWS-9 IP on OWS Context 1. 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.

2013-02-19The Reference Architecture Profiler (RAP) Advisor™ is a web based application thatrecommends OGC Standards and OGC Reference Model (ORM) Sections that arerelevant to a system development; such that a community of interest could derive andbuild a profile of suitable OGC standards to meet their specific needs. This EngineeringReport contains the requirements, conceptual design, development methodology, andimplementation of the RAP Advisor.

Initial development of the RAP Advisor™ was concurrent with the OGC Web ServicesTestbed, Phase 9 (OWS-9) with NGA sponsorship. During OWS-9 timeframe, keyconcepts of the RAP Advisor were confirmed through prototyping.

Future developmentis required to complete the functions and content of the Advisor. 2013-02-06This 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.

2013-02-05The OWS-9 Cross Community Interoperability (CCI) thread built on progress made in the recent OWS-8 initiative by improving interoperability between communities sharing geospatial data through advances in semantic mediation approaches for data discovery, access and use of heterogeneous data models and heterogeneous metadata models. This OGC engineering report aims to present findings from CCI thread activities towards advancement of semantic mediation involving heterogeneous data models, gazetteers and aviation data available through web services conformant to OGC standards.

This Engineering Report was prepared as a deliverable for the OGC Web Services, Phase 9 (OWS-9) initiative of the OGC Interoperability Program. The document presents the work completed with respect to the Cross Community Interoperability thread within OWS-9.

2013-02-05The main scope of the schema automation activities in the OWS-9 initiative was twofold:•Support for the SWE Common 2. 0 XML Schema encoding rule•Development of and support for an encoding rule for JSON instance dataIn both cases the scope includes implementation of the encoding rules in ShapeChange.

In addition, an initial analysis of the possibilities for generating SWE Common 2. 0 record descriptions from schemas in UML has been conducted and the results are described in this document.

The approach and results to both work items are described and discussed in this engineering report. This Engineering Report has been prepared as part of the OGC Web Services Phase 9 (OWS-9) initiative.

2013-02-05In this engineering report we describe how to administrate XACML v2. 1 access control policies through a “Security Rules Service”. Following the XACML and ISO terminology this service plays the role of a Policy Administration Point (PAP) and is therefore called XACML Policy Administration Point (XACML PAP) or XACML Policy Administration Web Service (XACML PAWS).

After introducing OWS-9’s Common Rule Encoding and motivating all components required to administrate (Geo)XACML policies, we describe the interface of a powerful XACML PAP on a conceptual level. This interface definition could serve as a baseline for a future OASIS or OGC XACML Policy Administration Web Service (e.

2012-05-15This document describes the usability of OGC services and encodings to implement theOWS-8 observation fusion and tracking thread in an abstract way. The real deploymentand an actual perspective on the engineering and technology viewpoint can be found inOWS-8 engineering report OGC 11-134, ‘OWS-8 Tracking: Moving Target IndicatorProcess, Workflows and Implementation Results’.

In addition, it describes an XMLSchemabased implementation of the UML information models defined in OWS-8engineering report “Information Model for Moving Target Indicators and Moving ObjectBookmarks” (OGC 11-113). The report is also based on the results of the VMTI/GMTI and STANAG 4676 realizationin the OGC concept of operations study; performed as part of OWS 8 and the EC cofundedresearch project Emergency Support System - ESS” (contract number 217951).

2011-12-19AIXM stands today for the de-facto standard for Aeronautical Information Publication, used by air control service providers from Europe, USA and Australia. 1, it reaches a level of maturity allowing the support of Digital NOTAMs, as the first official version of these messages was published this year. In a near future, AIXM will be carried inside WFS requests but also into notification messages along WS event services.

This last channel will be the one dedicated to D-NOTAMs. As D-NOTAM is aimed at aircrafts pilots, their transmission to the aircraft will use air/ground data link.

Today, datalink communications lack bandwidth and future datalink will still have a limited capacity. 2011-11-23This OGC® document specifies improvements to the processing of information represented in or referenced from an application schema in UML to create derived, implementation level resources, in particular:•XML Schema documents to represent types and their properties•Schematron schema documents to represent constraints•XSLT-Stylesheets to create KML instances of featuresThe documented improvements have been specified, implemented in the ShapeChange tool and tested in the context of schemas developed as part of the NGA's Topographic Data Store (TDS) schemas.

The work is a continuation of the work documented in OGC® document 10-088r2, the OWS-7 Schema Automation Engineering Report. 2011-11-23This 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.

An information model – so called ‘bookmark’ – to conserve the trace from a moving object back to the original base data is discussed briefly.

2011-11-23The OWS-8 Cross Community Interoperability (CCI) thread built on progress made in the recent OWS-7 initiative to cover key technology areas that could not be addressed within the scope of that initiative. The OWS-8 CCI thread aimed to increase interoperability within communities sharing geospatial data, including advancing of interoperability among heterogeneous data models, advancing strategies to share styles to provide a more common and automated use of symbology, improvement of KML, and advancing schema automation allowing communities to better share their information artefacts.

This OGC engineering report aims to present findings from CCI thread activities towards advancement of semantic mediation involving data retrieved from heterogeneous data models that are available through web services conformant to OGC standards. The engineering report will briefly introduce relevant details of the semantic web and mediation.

The document will make recommendations on establishing a semantic mediation architecture that uses OGC web services and emerging practice from the semantic web community. Based on the scenario adopted by the CCI thread, the document will also discuss the pros and cons of adopting relevant standards.

The engineering report will offer recommendations on how specific OGC standards may be adopted or modified in order to support semantic mediation. 2011-11-17The 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 subthread2011-11-07This 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). 2010-08-18This 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.

, 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. 2010-06-30This 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. 2010-02-16This 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.

2010-02-16This 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. 2009-07-16This OGC® document is an OGC Engineering Report for the “Harmonization of SWE Information Models” activity within the OWS-6 SWE thread.

The document discusses relations between OGC standards SensorML, SWE Common and GML and investigates solutions for increased synergy between these standards. This activity also created UML models of the data types used in SWE and GML.

This report shows how UncertML can be integrated into different SWE encodings, namely SWE Common and Observations and Measurements. This report further discusses the integration of MathML and EML into the SWE environment with an emphasis on SensorML processes and processing.

This document does not discuss the SWE information model related aspects of catalog entries for sensor services and discovery. This topic is covered in a separate Engineering Report.