RIEDP Data Model Foundations

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

Version 1.1

16 November 2016

Prepared by

Reuse and Interoperation of Environmental Data and Processes (RIEDP)

Product Development Group (PDG)

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

The information that appears in red italicized text is hidden text and is not seen when viewed in Print Preview and/or when the document is printed. The template is a Word Document and edited like any other Word Document. This template establishes standard format and contentso that all Standards Products contain the same basic information and have the same basic look. Replace the YYYY in the copyright statement with the current year. The SAC Editor will ensure the final approved product contains the year the product is published. Be sure to overwrite or delete the <inline instructions> throughout the document.

P.O. Box 781238

Orlando, FL 32878-1238, USA

Select the appropriate copyright statement. This is the copyright statement that will appear in the draft SISO Standards Product while it is under development, balloted, and processed for final approval.

Permission is hereby granted for SISO developing committee participants to reproduce this document for purposes of SISO product development activities only. Prior to submitting this document to another standards development organization for standardization activities, permission must first be obtained from the SISO Standards Activity Committee (SAC). Other entities seeking permission to reproduce this document, in whole or in part, must obtain permission from the SISO Inc. Board of Directors.

This is the copyright statement that will appear in the published SISO Standards Product. The SAC Editor will ensure the correct copyright statement appears in the SAC-approved version provided to the EXCOM to validate that the SAC’s approval was given in accordance with the SISO-ADM-002 and the Standards Product does not conflict with SISO operations as a standards development organization or as a not-for-profit organization.

SISO Inc. Board of Directors

P.O. Box 781238

Orlando, FL 32878-1238, USA

The appropriate header and footer notation will be used. Complete the header information with the Standards Product title. The appropriate footer notation will be used in conjunction with the copyright statements above. For draft Standards Products, the second line of the footer will contain only the “unapproved” statement. The SAC Editor will ensure the SAC-approved version containsthe “approved” statement in the second line prior to providing to the EXCOM.

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

Revision History

Version / Section / Date
(MM/DD/YYYY) / Description
1.0 / 07/19/2016 / Version provided for review by RIEDP DG2 Members for Summer 2016 Informal Review
1.1 / 11/15/2016 / Incorporate comment resolutions from Informal Review.
This version is provided for November Formal review by RIEDP PDG Members

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

It takes a village to produce, ballot, and approve SISO Standards Products. Standards Products take multiple years to develop, achieve consensus, ballot, resolve comments, undergo multiple committee reviews, achieve SISO approval, and be published. This section recognizes all involved and acknowledges the role(s) played in the lifecycle of a SISO Standards Product.

Participants

At the time this product was submitted to the Standards Activity Committee (SAC) for approval, the RIEDPProduct Development Grouphad the following membership and was assigned the following SACTechnical Area Director:

Product Development Group

Jean-Louis Gougeat(Chair)

Simon Skinner (Vice-Chair)

?(Secretary)

▬ ▬ ▬

Lance Marrou(SACTechnical Area Director)

▬ ▬ ▬

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

Gilbert Castaner,

Jack Cogman

Rob Cox

Greg Enochian

Paul Foley

Lance Marrou

Farid Mamaghani

Ron Moore

Roy Scrudder

Andreas Reif

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

The Product Development Group would like to especially acknowledge those individuals that significantly contributed to the preparation of this product as follows:

PDG Drafting Group

(Editor)

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

Co-DGE2Gilbert Castaner

Co-DGE2Farid Mamaghani

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

Ballot Group

TBD(Editor)

Standards Activity Committee

Paul Lowe (Chair)

Marcy Stutzman (Vice Chair)

Jeff Abbot (Secretary)

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

Bailey, Grant

Blais, Curt

Burnette, Michael

Gravitz, Peggy

Gupton, Kevin

Loper, Margaret

Lopez-Rodriguez, Jose Maria

McGlynn, Lana

Oates, William

Riggs, Bill

Tapp, Martin

Youngblood, Simone

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

When the Executive Committee approved this product on DD Month YYYY, it had the following membership:

Executive Committee

Bob Lutz(Chair)

James Coolahan(Vice Chair)

Jane Bachman(Secretary)

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

Daly, John

Gustavson, Paul

Igarza, Jean-Louis

Lowe, Paul

Morse, Katherine

McCall, Mark

O’Connor, Michael

Scrudder, Roy

Swenson, Steve

Whittington, Eric

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

Preface

This introduction is optional, is informative in nature only, and is not part of the standard. If there is a need to provide readers background and/or history of development information, etc., then that information should be included here. Provide only the information a reader and potential user needs to understand how and why this Standards Product was developed and why the Standards Product is needed. If there is no need for an introduction, delete this section.

An environmental database may include an integration of terrain, ocean, weather/atmosphere, space, sub-surface, and all related data required for Modeling and Simulation (M&S)of phenomena and/or entities. Production of environmental databases is a significant part of the overall M&S development and deployment cost. Capitalizing on approaches that reduce the overall cost is an important topic of interest to the broader M&S community.

Various practices exist that deal with the data production process and/or the subsequent sharing of environmental data, and they address different aspects of the end-to-end problem. The practices are at various levels of formalization, ranging from international standards to ad hoc methods. On-going projects in a number of international government programs, as well as separate initiatives and innovative approaches from industry, continue to contribute to solutions in this area.

However, activities within and across similar communities, projects, or nations are often fragmented or disjoint, and sometimes do not or cannot leverage existing capabilities, standards, or lessons-learned. These activities often vary in scope, breadth, or depth. In some cases, the results that are produced are driven by the special requirements of specific projects or activities. However, in general, this fragmented approach reduces the reuse of data and the interoperability of the systems that use them, because it generates multiple incompatible solutions.

A survey by the RIEDP Study Group (SG) showed that many of these initiatives, a large subset of which are mainlyfocused on producing data for aviation-related training applications, use the same geospatial source data formats and a very similar high level data generation process. Therefore, the RIEDP SG compared several initiatives against an initial concept version of a process model and a data model to identify areas of convergence and divergence. Based on these results, the objectives of a next-step Product Development Group (PDG) were defined.

The RIEDP PDGprovides two complementary products to address this.

The first product is the RIEDP Data Model Foundations, which is a SISO Guidance product. It is composed of two (tightly coupled) parts, the RIEDP Reference Process Model (RPM) and the RIEDP Reference Abstract Data Model (RADM). These form the foundations for existing and/or emerging database generation projects to compare, contrast, and map their database generation process and data model capabilities to these models. In this regard, use of the RIEDP Data Model Foundations serves as a guide in establishing database generation process models and their corresponding data models within the community.

Thesecond product is the RIEDP Detailed Features Description. It is a SISO Standard product and its concepts complement the RIEDP Data Model Foundations. It provides the required information for identifying and describing specific instances and/or abstracted typesof environmental featuresthat, along with their specific attributes, value ranges, and metadata, will be utilized in environmental data products. The use of the RIEDP Detailed Features Description as a standard product improvesdata interoperability through the identification of features, their definitions (by using standardized dictionaries), their corresponding attributes, and any associated metadata.

This document is the RIEDP Data Model Foundations.

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

TABLE OF CONTENTS

1Overview

1.1Scope

1.2Purpose

1.3Objectives

1.4Intended Audience

1.4.1Users of the document

1.4.2Targeted community of interest

1.5Intellectual Property Rights

1.6Document outline

2NORMATIVE References

3Definitions, Acronyms, and Abbreviations

3.1Acronyms and Abbreviations

3.2Definitions

4Concepts

4.1Introduction

4.1.1Overview

4.1.2Common RPM and RADM Concepts

4.1.3RPM and RADM Data Formats

4.2Reference Process Model

4.2.1Overview

4.2.2Summary Description of the RPM Stages

4.2.3Detailed description of the RPM stages

4.2.4Detailed view of the RPM

4.3Reference Abstract Data Model

4.3.1Introduction

4.3.2Key RADM Concepts and Conventions

4.3.3Description of the RADM

4.4RIEDP-required Formats - Rules and Criteria

4.5Organization of the Data on Media

4.5.1Root Folder

4.5.2Tiles Folder

4.5.3Region Folder

4.5.4Library Folder

4.5.5Metadata Folder

4.6Guidelines for Evaluation of Candidate Formats

4.6.1Procedure for extensions and modifications

4.6.2Criteria for proposed extensions and modifications

4.7RIEDP Profiles

5Conformance

5.1Overview

5.2Conformance to RPM Stages

5.3Conformance to RADM Classes

5.4Conformance to RIEDP Profiles

5.4.1Basic-Cleaned Profile

5.4.2Library-Only Profile

5.4.3Basic-Aligned Profile

5.4.4Basic-Baseline Profile

5.4.5Full-Intensified Profile

5.4.6Full-Specialized Profile

5.4.7Profiles Overview

5.5Conformance of RIEDP-compliant Data Products

Appendix ABibliography (Informative)

Appendix BRIEDP-required Formats - DETAILED specifications (Normative)

B.1GeoTIFF for Elevation

B.2GeoTiff for Imagery

B.3Openflight

B.4Shapefile

B.4.1.shp File

B.4.2.shx File

B.5JPEG 2000

LIST OF FIGURESinsert table of figures below

Figure 1 – RPM overview – Activity Flow

Figure 2 – RPM overview – Data Flow

Figure 3 – Collect Source Data

Figure 4 – Clean Source data

Figure 5 – Create/modify Library data

Figure 6 – Align Source layers

Figure 7 – Establish Baseline Data

Figure 8 – Intensify Baseline Data

Figure 9 – Specialize Data for Target Applications

Figure 10 – Generate Runtime database

Figure 11 – Export data

Figure 12 – Detailed view of the RPM

Figure 13 – Overview of the RADM

Figure 14 – Top-level classes of the RADM

Figure 15 – Main components of the Database

Figure 16 – Library main components

Figure 17 – Components of a Tile

Figure 18 – Strips and Tiles

Figure 19 – Examples of tile convention for two areas of interest

Figure 20 – Components of a Region

Figure 21 – Special Area

Figure 22 – Elevation Layer

Figure 23 – Imagery Layer

Figure 24 – Other Raster Layer

Figure 25 – Feature Layer

Figure 26 – Feature Template

Figure 27 – 3D Model

Figure 28 – Texture

Figure 29 – Reference Table

Figure 30 – Value and Index attributes

Figure 31 – An Implementation Relating Instance and Template Classes through Attributes

Figure 32 – First Level of the RDB arborescence

Figure 33 – Example of Folders for Areas 1 and 2

Figure 34 – Example of division of a tile

Figure 35 – Content of individual tiles folder

Figure 36 – Content of a Region folder

Figure 37 – Library Folder

Figure 38 – FeatureTemplates Folder

Figure 39 – 3DStaticModels Folder

Figure 40 – 3DMovingModels Folder

Figure 41 – Textures Folder

Figure 42 – Special Areas Folder

Figure 43 – Reference Tables Folder

Figure 44 – Metadata Folder

Figure 45 – SpatialReference Folder

Figure 46 – ProductInformation File

Figure 47 – Elevation Layer Metadata

Figure 48 – Imagery Layer Metadata

Figure 49 – FeatureLayerMetadata

Figure 50 – FeatureTemplateMetadata

Figure 51 – 3D Models Metadata

Figure 52 – SpecialAreaMetadata

Figure 53 – ReferenceTableMetadata

Figure 54 – TextureMetadata

LIST OF TABLES

insert table of tables below

Table 1 – Metadata classes and their corresponding fields

Table 2 – RIEDP-required Formats - Rules and Criteria

Table 3 – Profiles overview

This is an unapproved SISO Guidance Product Draft, subject to change.

SISO-REF-xxx - RIEDP

RIEDP Data Model Foundations

1Overview

1.1Scope

Standards Products should describe concisely the scope of the document. The scope will be within the technical boundaries of the scope described in the Product Nomination. Be sure to delete all inline instructions.

This SISO Guidance product formalizes:

The high-level process, and theassociated data flow stages and tasks, that are used in the creation of environmental databases for Modeling and Simulation (M&S), and
Provides a reference data model for expressing the data produced through that process.

These are identified as the RIEDP Reference Process Model (RPM) and the RIEDP Reference Abstract Data Model (RADM), and together comprise this RIEDP Data Model Foundations product.

Although the initial core focus of the RIEDP products is the Aircrew Training and Mission Rehearsal community applications, the RPM and RADMare applicable,with extensions, to other communities with similar processes and data use.

Ocean and weather data requirements are notincluded in the current RIEDP process and data model, but may be incorporated in future evolutions of the RIEDP products.

1.2Purpose

Standards Products should describe concisely the purpose for the document. The purpose will be within the technical boundaries of the purpose described in the Product Nomination.

This document promotes reusability of environmental database generation efforts and fosters interoperability between simulation systems through a standardized understanding of both their environmental data products and generation processes. The focus is on the harmonization of environmental database generation processes, and the means to exchange such generated data, at various points in the process, after the source data collection stage but before the runtime/proprietary database creation stage, recognizing that there is a broad range within this band. Added to this is the desire to not introduce specific target application constraints prior to that point in the process (such constraints should be addressed separately by each target application during or just prior to creating the runtime database). In addition, it is desirable and valuable to retain the data form (or format) as close to the source data as possible throughout the data generation process in order to benefit from GIS tools and any intrinsic correlation factor they may provide.

1.3Objectives

Standards Products should describe concisely theobjectives the document achieves.

The combination of the RPM and the RADM will allow different database generation processes and systems to relate to each other, and compare, contrast, and map their database generation process and data model capabilities usingthe RIEDPproducts.

In this regard, use of the RIEDP Data Model Foundations serves as a guide in establishing common database generation processes and data models within the M&S community. In addition, it aids in the development of the RIEDP Detailed Features Description product, which is a companion standard product to this guidance document.

1.4Intended Audience

Standards Products should describe concisely the intended audience for the document

The intended audience of this SISO Guidance document includes (but is not limited to):

Systems engineers, program managers, and software engineers involved in the use or development of M&S environmentaldatabase generation products, processes, and systems;
Users and subject matters experts who define and specify requirements for environmental databases in M&S and distributed simulation applications, as well as those who evaluate and select databases for reuse.

1.4.1Users of the document

Users of this guidance document are the environmental database producers who are interestedin sharing their data in the M&S community, facilitating reuse of their data in other database production efforts, and/or fostering interoperability between different simulation systems through a common understanding of both their environmental dataproducts and generation processes.

It is not envisioned that the environmental database producers would be required to change their creation process to conform to this document. Hence, the specificationsof the RPM and RADM are primarily a guidance that aims to help share a common vision based on common concepts.