The Army Battlespace Environment Registry of Federated Feature Data Dictionaries

1
The Army Battlespace Environment Registry of
Federated Feature Data Dictionaries

• Melissa E. Nakanishi
• Dr. Dale D. MillerAnnette Janett Filer
• Lockheed Martin Simulation, Training Support
• Advanced Simulation Center
• Dr. Paul A. Birkel
• The MITRE Corporation
• Denise HovanecKevin Mullane
• U.S. Army Engineer Research and Development
  Center, Topographic Engineering Center

2
Why Army Battlespace Environment (ABE) now?

• In accordance with recent DoD direction 1,
  concerning data made available within the GIG by
  any DoD organization,

Data assets shall be made understandable by
publishing associated semantic and structural
metadata in a federated DoD metadata registry.
1 DoD Directive 8320.2, "Data Sharing in a
Net-Centric Department of Defense", 12/02/2004
3
Why ABE now?

• In accordance with recent DoD direction 1,
  concerning data made available within the GIG by
  any DoD organization,

Data assets shall be made understandable by
publishing associated semantic and structural
metadata in a federated DoD metadata registry.
1 DoD Directive 8320.2, "Data Sharing in a
Net-Centric Department of Defense", 12/02/2004
4
Why ABE now?

• In accordance with recent DoD direction 1,
  concerning data made available within the GIG by
  any DoD organization,

Data assets shall be made understandable by
publishing associated semantic and structural
metadata in a federated DoD metadata registry.
1 DoD Directive 8320.2, "Data Sharing in a
Net-Centric Department of Defense", 12/02/2004
5
Community of Interest (COI).

• According to the DoD 1 , a Community of
  Interest (COI) is defined as

A collaborative group of users that must
exchange information in pursuit of its shared
goals, interests, missions, or business processes
and therefore must have shared vocabulary for the
information it exchanges.
1 DoD Directive 8320.2, "Data Sharing in a
Net-Centric Department of Defense", 12/02/2004
6
Why ABE now?

• In accordance with recent DoD direction 1,
  concerning data made available within the GIG by
  any DoD organization,

Data assets shall be made understandable by
publishing associated semantic and structural
metadata in a federated DoD metadata registry.
1 DoD Directive 8320.2, "Data Sharing in a
Net-Centric Department of Defense", 12/02/2004
7
ISO TC211 Geographic Information/Geomatics
19103
-19103 - Conceptual schema language -19107 -
Spatial schema -19108 - Temporal schema -19109 -
Rules for application schema -19110 - Methodology
for feature cataloguing -19111 - Spatial
referencing by coordinates -19112 - Spatial
referencing by geographic identifiers -19113 -
Quality principles -19114 - Quality evaluation
procedures -19115 - Metadata -19121 - Imagery
and gridded data -19123 - Schema for coverage
geometry and functions -19124 - Imagery and
gridded data components -19126 Feature data
dictionaries, feature catalogues and their
registers -19127 - Geodetic codes and
parameters -19128 - Web Map server
interface -19129 - Imagery, gridded and coverage
data -19130 - Sensor and data models -19131 -
Data product specifications -19135 - Procedures
for registration of GI items -19136 - Geography
Markup Language -19137 - Generally used profiles
of spatial schema -19138 - Data quality
measures -19139 - Metadata - Implementation
specification
19123
19109
19107
19111
19127
19110
19124
19112
19137
19115
19108
19135
19126
19113
19114
19138
19131
8
ABEBuilt upon Standards

• ISO 19110 Geographic information Methodology
  for feature cataloguing, Published Standard, Feb.
  2005
• a feature catalogue contains bindings among
  feature types, attributes, operations and
  associations.
• ISO 19126 Geographic information Feature data
  dictionaries, feature catalogues and registers,
  Draft Standard, May 2005.
• ISO 19135 Geographic information Procedures for
  registration of items of geographic information,
  Unpublished Standard, May 2005,

9
ABEA Registry of Feature Data Dictionaries

• A feature data dictionary defines
• feature types, e.g. road
• attribute types, e.g. length, road surface
• enumerants, e.g. pavement, gravel
• feature association types, e.g. connects to,
  and
• feature operation types , e.g. get length
• a feature catalogue would differ in that it
  contains bindings among the feature types,
  attributes, operations and associations.

10
(No Transcript)
11
ABEA registry of registers

• A register is a set of files containing
  identifiers assigned to items with descriptions
  of the associated items
• A register will have a register owner and a
  register manager
• A register may have subregisters
• A profile of a register is a register subset
• A registry is an information system upon which a
  register is maintained
• A compound registry is one which contains
  multiple registers.

12
Federating Geospatial COI Data DictionariesSpiral
1
AeronauticFDD Registry
Hydrographic LittoralFDD Registry
TopographicFDD Registry
Foundation Feature Data (FFD)
Foundation Feature Data (FFD)
Foundation Feature Data (FFD)
Digital Topographic Data (DTOP)
Digital Topographic Data (DTOP)
Digital Topographic Data (DTOP)
ABE Virtual Register
Geo Intel FDD Registry
Meteorology OceanographicFDD Registry
Sum of Profiles Of FDD Registries
Facilities InfrastructureFDD Registry
Digital Topographic Support System
(DTSS) Extended with Theater Geospatial Database
(TGD)
Integrated Meteorological System (IMETS)
Urban Vector Map (UVMap)
Battlespace Terrain Reasoning and Awareness (BTRA)
Imagery
13
Common Data Modeling Framework (CDMF) Export
Capability
ABE
CDMF
Profile(s)
EDM
14
Common Data Modeling Framework (CDMF) Import
Utility
CDMF
EDM
EDM
EDM
Dictionaries, Profiles
EDM
15
Army Stakeholder Concepts Spiral One

• Foundation Feature Data (FFD)
• NGA Product, Medium-scale, Planning Data,
  Worldwide
• Digital Topographic Data (DTOP)
• Basis for Mission Specific Data Sets (MSDS)
• Integrated Meteorological System (IMETS)
• Supports WX obs, forecast, and WX effects
  decision aids
• Urban Vector Map (UVMap)
• Standard NGA product for the urban domain
• Digital Topographic Support System (DTSS)
• with Battlespace Terrain Reasoning and Awareness
  (BTRA)
• Theater Geospatial Database (TGD)
• an extension to the DTSS, supports data
  production in theater

16
Data Elements in Spiral 1
17
Army Stakeholder Concepts Spiral Two

• Vector Interim Terrain Data (VITD)
• NGA product that supports terrain analysis
• Objective OneSAF Terrain (OOS-T)
• Terrain component of emerging high-resolution
  (MS) system
• WARSIM Terrain Common Data Model (TCDM)
• Captured with terrain component of OOS
• Mission Specific Data (MSD) Level 3
• Unified Profile of MSD is under development by
  NGA
• Level 3 150,000 scale cartographic
  representation
• Objective OneSAF Atmos, Ocean, Space (AOS)
• Various phenomena necessary to model AOS
• Objective OneSAF Urban High Resolution Building
  (UHRB)
• OOS-UHRB supports the description of buildings

18
Army Stakeholder Concepts Spiral Two (Continued)

• Maneuver Control System Engineering (MCS-ENG)
• Combat Engineer C2 system with bridge, obstacle
  and route concepts
• Command and Control Information Exchange Data
  Model (C2IEDM)
• negotiated multinational C2 information exchange
  model
• (ABE captures environmental concepts only)

19
Data Elements in Spirals 1 and 2
20
ABE Profile Data Element Count by Register
21
Registers currently supported in ABE

• National System for Geospatial-Intelligence FDD
  (NFDD)
• National profile of the Digital Geographic
  Information Working Group FDD (DFDD) with
  extensions
• Based on Feature and Attribute Coding Catalogue
  (FACC)
• Army Geospatial Concepts FDD
• Identifies additional geographic information
  concepts used by U.S. Army
• Army Geospatial Intelligence Concepts FDD
• Identifies additional geographic intelligence
  concepts used by U.S. Army
• SDS Facilities, Infrastructure, Environment
  (SDSFIE) FDD
• ANSI standard used for representation of
  facilities and infrastructure

22
Registers currently supported in ABE (continued)

• Environmental Data Coding Standard (EDCS)
  Graphical Items Dictionary
• Concepts from EDCS version 4.0,
• Designed to support modeling and simulation
• C2 Information Exchange Data Model Register
• contains geospatial information concepts from the
  C2IEDM 6.1.5
• Joint METOC Broker (JMB) FDD
• identifies concepts from the Joint METOC Broker
  Language (JMBL) v. 3.0

23
ABE Registry Web Accessible

• Online information resource
• Supports cross-register browse, search and
  download
• Stores source and lineage metadata
• Offers multi-lingual support
•  
• Provides full life-cycle recordkeeping
• Allows for distributed collaboration
• SSL encryption, password management, and
  multi-role access control

24
ABE Registry Technology Agile Denotation

• Vector Product Format for VPF-based products and
  applications
• Satisfied by ASCII short code
• Shapefiles, and Shapefile-based applications
• ASCII short code
• Web-based services, in particular Geography
  Markup Language (GML)
• ASCII long code
• Geodatabases and other COTS object-relational
  environments
• ASCII medium code
• IDEF-1X (relational) models
• ASCII medium code
• Unified Modeling Language (UML)
• ASCII medium code
• Human-friendly presentation and analysis (e.g.,
  names)
• Compatible with FACC

25
ABE Registry Technology Agile Denotation
26
Adjudication and Harmonization

• Embrace
• existing dictionary element
• Extend
• dictionary as necessary
• Collaboratively evolve
• the COI DEDs and the ABE Profile

27
Federating Geospatial COI Data DictionariesSpiral
1
AeronauticFDD Registry
Hydrographic LittoralFDD Registry
TopographicFDD Registry
Foundation Feature Data (FFD)
Foundation Feature Data (FFD)
Foundation Feature Data (FFD)
Digital Topographic Data (DTOP)
Digital Topographic Data (DTOP)
Digital Topographic Data (DTOP)
ABE Virtual Register
Geo Intel FDD Registry
Meteorology OceanographicFDD Registry
Sum of Profiles Of FDD Registries
Facilities InfrastructureFDD Registry
Digital Topographic Support System
(DTSS) Extended with Theater Geospatial Database
(TGD)
Integrated Meteorological System (IMETS)
Urban Vector Map (UVMap)
Battlespace Terrain Reasoning and Awareness (BTRA)
Imagery
28
Summary

• The ABE Registry specifies concepts, definitions,
  and encodings for the geospatial domain
• The ABE profiles required concepts from COI
  feature data dictionaries.
• The ABE establishes a federated registry of
  Community of Interest (COI) feature data
  dictionaries based on an ISO-compliant
  information model and management mechanism.
• The ABE will continue to encompass additional
  critical Army requirements as we
• Embrace authoritative concept representations
• Engage, coordinate and communicate with COI data
  dictionary owners,
• Evolve towards a DED that fully covers and
  supports the geospatial and intelligence aspects
  of the Army mission space.