SEDRIS: A Tool for the Management and Exchange of Multidomain Environmental Data

1
SEDRIS A Tool for the Management and Exchange of
Multi-domain Environmental Data

• Fall Simulation Interoperability Workshops
• Orlando, Florida
• September 11-14, 2006

Michael J. Leite, PE Virginia Dobey Peggy Gravitz
DISTRIBUTION STATEMENT A Approved for public
release distribution is unlimited. Contract
GS09K99BHD0010, DoD Case 06-S-0160
2
Outline

• Introduction
• History
• SEDRIS Concepts
• SEDRIS Components
• Application Examples
• Potential Applications
• Continuing Development
• Summary Conclusion

3
Introduction

• Need for Environmental Data Exchange
• Disasters Natural Man-made
• Multi-jurisdiction Response
• Mutual-aid Agreements
• Regional Planning
• Research
• Training

4
Needed Environmental Data Mediation

• Lessons Learned from Recent Events
• Inability to Exchange Data in Timely Manner
• Lack of Interoperability
• Failure to Model/Forecast Damage Progression
• Current Situation
• Environmental Data in Multiple Formats
• Different Coordinate Systems
• Distributed Data Storage Facilities

What if . . . a system could facilitate the
rapid exchange of environmental data?
5
SEDRIS History

• 1984 Deficiencies in Environmental
  Representations Identified
• 1994 SEDRIS Program Initiated
• 1996 First SEDRIS Release
• 1999 SEDRIS 2.5 Released
• 1999 SEDRIS Standardization Effort Initiated
  through ISO/IEC
• 2000 SEDRIS 3.0 Released
• 2000 SISO Establishes EDCS Product Development
  Group
• 2003 Final Committee Draft Standard for EDCS
• 2004 Final Committee Draft Standard for SRM and
  SEDRIS
• 2005 EDCS Standard Approved Published
  Registry Established
• 2005 SEDRIS SRM Balloted as Final Draft
  International Standards
• 2006 SEDRIS and SRM Standards Approved and
  Published

6
SEDRIS Concepts

• SEDRIS Objectives
• Articulate and capture the complete set of data
  elements and associated relationships needed to
  fully represent environmental data
• Provide a standard interchange mechanism to
  distribute environmental data and promote
  database reuse among heterogeneous applications.
• Support the full range of applications across all
  environmental domains (terrain, ocean,
  atmosphere, and space) and 3-D models of the
  physical environment.

7
All Environmental Data Types
Space
Atmosphere
Terrain
Ocean
8
Environmental Data Challenges

• Environmental data producers provide
  domain-specific data in product- and
  producer-specific formats
• Effect Constructs of environmental
  data/products are often incompatible across
  domain boundaries, making reuse and interchange
  difficult
• Effect Users tailor such data and create
  application- and platform-specific environmental
  data sets
• Many systems and applications require the
  integration of data
• from many sources
• that cross domain boundaries
• Creation, update, and tailoring for reuse of
  environmental data are resource-intensive and
  expensive (and have high recurring costs)
• Regardless of format(s) or product(s) utilized,
  users must represent all of their data in a
  unified manner

9
A Middleware Approach
To
From
Point-to-Point Connectivity

• Expensive and time consuming
• Often unreliable and non-interoperable
• Unique conversion needed for each source
• Increase in sources geometrically increases
  number of conversions

• Significant reduction in conversion cost
• Higher reliability, interoperability,
  integration, and reduction of correlation error
• Common and open standards, tools, and software
  reuse

10
The SEDRIS Implementation

• Cost-effective, unified representation and
  interchange of environmental data
• Eliminate expensive recurrent costs
• Compatible across domain boundaries
• Accommodate multiple product formats
• Support for legacy and new applications
• Decrease initial (development) and recurring
  costs.
• Joint and networked applications
• Tools improve validation quality and decrease
  validation time
• Validate data sets
• Find errors

11
SEDRIS Concepts

• Separate format and data representation
• Separate object semantics from representation
• Separate science and the mathematics of location
  specification and conversion techniques from
  location data representation
• Provide a mechanism for reconciling different
  spatial reference frames (coordinate conversions
  and transformations)
• Provide standard interface data representation
  schema
• Provide tools to facilitate users job

12
SEDRIS Applications

• Data Repository or Library
• Data Discovery
• Database Generation or Authoring Tool
• Database Conversion
• Environmental Databases
• Simulation Scenario Generation
• Data ExchangeIncluding Time Domain

13
SEDRIS Components

• SEDRIS ISO/IEC SC 24 Standards
• International Standards
• Environmental Data Coding Specification (EDCS) -
  ISO/IEC 18025
• EDCS C Binding - ISO/IEC 18041-4
• Spatial Reference Model (SRM) - ISO/IEC 18026
• SRM C Binding - ISO/IEC 18042-4
• SEDRIS Functional Specification (DRM and API) -
  ISO/IEC 18023-1
• SEDRIS Abstract Transmittal Format - ISO/IEC
  18023-2
• STF Binary Encoding - ISO/IEC 18023-3
• SEDRIS C Binding - ISO/IEC 18024-4

DRM Data Representation Model API
Application Program Interface STF SEDRIS
Transmittal Format
14
SEDRIS Tool Set

• Tools Freely Available at http//www.SEDRIS.org
• EDCS Query Tool - SEE-IT
• Transmittal Browser - VPF to STF converter
• Syntax Checker - DTED to STF converter
• Depth - CTDB to STF converter
• Rules Checker - STF to CTDB converter
• Model Viewer - GeoTIFF to STF converter
• Focus - STF utilities
• Side-by-Side (an AcuSoft Inc. product)
• STF (previous version) to STF (current version)
  converter

15
SEDRIS Standard Applications
16
How SEDRIS is Used -
Use
To transfer using
To produce
Space
Atmosphere
Terrain
Ocean
To
Data Consumers
17
Application Examples

• Terrain Data Inspection
• Manipulation of Data Sets
• Visualization
• Coordinate Transformation

18
Terrain Data Inspection

• Synthetic Environment Evaluation-Inspection Tool
  (SEE-IT)
• Topology Holes, elevation mismatches, T
  vertices, incorrect 2-D surface area
• Polygons Duplicate, highly sloped, narrow, small
  area, or sliver polygons
• Networks Disconnects - Road segments with
  excessive slope, sharp turns, incorrect
  elevations, width changes, or that intersect
  NO-GO areas
• Models
• Gaps and skews between bridge segments
• Bridge segments without associated road networks
  or that include road network ends, intersections,
  or width changes
• Static models placed on high slope surface
  polygons or on a collection of polygons that have
  high slope variance
• Static models, other than bridges, that have
  bounding volumes which intersect or otherwise
  overlap road network locations

19
Vertical Tear Locations
Cross section of a single tear instance with a
magnitude of 135m
900Km X 900Km terrain skin
20
Connectivity Problems
Road centerlines do not connect
Road intersects water feature without a bridge
Road intersects a model bounding volume
21
Manipulation of Data Sets
WIND MAP SEDRIS Transmittal Format can carry the
content of various meteorological databases. The
wind map program reads multiple data from a
SEDRIS transmittal, via the SEDRIS API, for
display using a graphics viewer.
22
Manipulation of Data Sets
Ocean Profile Viewer The SEDRIS API can be used
to extract data from a transmittal to drive
applications. The user selects a rectangular
ocean surface area from the transmittal. The
application uses the API to extract bathymetry,
sound speed, temperature, and salinity in the
selected ocean volume for visualization.
23
Visualization

• Simultaneous viewing of multiple databases, up
  to hardware limit
• Independent orsynchronizednavigation modes
• Designed fordatabase comparison
• Modular design toaccepting userspecific
  processingplug-in

24
Model Data Transformation
Data conversion
3ds Max
SEDRIS
Maya

• Support 3D Formats Max, Maya,
• CAD etc.
• Keep data hierarchy structure

Animation data conversion
Plug-in Exporter
SEDRIS

• Support Geometry Entities
• - Polygon Geometry
• - Undeformed NURBS geometry
• (converted to polygons on export)
• - Rigid and Soft body object
• - Texture Maps and Lights

Cloth Animation
Maya
SEDRIS
Mobile

• Use Self-developed Algorithm
• Instable Self Collision Detection
• Support Aerodynamic Effects
• Support Polygon Reduction

25
Spatial Reference ModelConceptual Relationships

• Object independent aspect
• An abstract coordinate system (CS) is based on
  the underlying Euclidean structure of
  position-space.
• Object empirical measurement/model dependent
  aspect
• The reference datums bound to an object determine
  how position-space relates to object-space.
• The relationship may be mathematically expressed
  by a normal embedding.
• The relationship is specified as an object
  reference model (ORM).
• Combined as a spatial reference frame (SRF)
• An SRF combines an abstract CS with an ORM to
  specify a spatial coordinate system.

26
Abstract and Spatial Coordinate Systems
An abstract coordinate system for position-space
composed with a normal embedding determines a
spatial coordinate system for object-space. A
normal embedding expresses the position-space/obje
ct-space relationship asspecified by an object
reference model.
27
Spatial Operations with SRM
Change coordinate from source SRF to target SRF
G coordinate system generating function H
object reference model transformation

• Uniform treatment of abstract coordinate systems,
  and uniform treatment of object reference models,
  leads to uniform treatment of spatial operations.
• Intrinsically extensible
• Operations inside the source SRF are independent
  of the operations inside target SRF
• Supports an object-oriented API

28
Test and TrainingEnabling Architecture (TENA)

• U.S. DoD SEDRIS Application
• Connects Test Ranges, Labs Simulation Sites
• On-the-fly SRM Coordinate Transformation
• Real-time Data Exchange

29
Potential Applications

• Tie Local Grids to State and National Grids and
  GPS Positions (SRM)
• Exchange MS Operational Data
• Standard Metadata (EDCS with Registry)
• Coordinate Conversion (SRM)
• Pass Data Among Operational Commanders (SEDRIS)
• Disaster Management (Full SEDRIS Implementation)
• Pass Data to First Responders
• Prebrief/prepare Mutual Aid Responders
• Simulation of Potential EffectsDamage Progression

30
Continuing Development

• Use Registries to Extend Applications
• Metadata
• Implementations
• Continue Tool Development Evolution
• Develop Logical Data Model for Environmental Data
• Normalized
• Provide linkage between dictionaries presently in
  use

31
Summary Conclusion

• Representation of location for the various
  coordinate systems (spatial reference frames),
  local or global, that will be natural for
  individual systems or sub-systems
• Accurate, efficient, and fast conversion of
  location data between different spatial reference
  frames
• Comprehensive dictionary of terms that not only
  deals with terrain data, but also atmosphere,
  ocean, littoral, and space data. And is also
  extensible in a predictable and supported manner
• A representation schema that can handle any
  resolution, type, organization, and extent of
  environmental data through a uniform approach for
  all domains of the environment

• The SRM is designed for this
• The SRM implementation does this
• The EDCS is designed for this
• The DRM is designed for this

32
Summary Conclusion

• A mechanism to access and interact with any data
  sets or data collectors through a robust software
  interface
• Capture and communicate the resulting data in a
  persistent, efficient, and platform independent
  format designed to handle large and distributed
  data sets
• Tools to manipulate, evaluate, visualize, or
  analyze the data
• Automatically evaluate and validate data sets
  against stated requirements

• The API implementations do this
• The STF is designed for this
• An array of tools and utilities
• TCRS uses the DRM, SRM, and EDCS for this

33
More Information. . .

• ISO/IEC standards activities
• Information at http//wg8.sedris.org
• SEDRIS Standards (Download _at_ no charge)
• - Available at http//isotc.iso.org/l
  ivelink/livelink/fetch/2000/2489/Ittf_Home/ITTF.ht
  m
• Technical Information
• Open source software SDK releases, videos of
  tutorials, papers
• SEDRIS technology components (EDCS, SRM, DRM,
  API)
• Proceedings from past conferences
• Available at http//www.sedris.org
• Free Tools Utilities, and Pointers to
  Commercial Tools
• Available at http//tools.sedris.org
• Data samples
• Available at http//data.sedris.org
• Questions
• Can be sent to help_at_sedris.org
• ms_standards_at_dmso.mil