0. RIEDP PDG I/ITSEC Meeting
Modèle pour les Présentations Techniques sous PowerPoint 2003
RIEDP PDG I/ITSEC Meeting
Sous-Titre
Référence – Date : E2Cxxxx du
RIEDP-PDG - I/ITSEC 2014
Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data.

1. Modèle pour les Présentations Techniques sous PowerPoint 2003
Agenda
Introduction
Summary of past events
Status of RPM
Status of RADM
Review of actions
AOB
Conclusion
RIEDP-PDG - I/ITSEC 2014
02/11/2014
Ce document est la propriété intellectuelle de Sogitec Industries, il ne peut être utilisé, reproduit, modifié ou communiqué sans son autorisation. SOGITEC Industries Proprietary Data.

2. Introduction Web connection information
Wednesday, 29 October 2014
3:30 PM France, 2:30 PM UK, 10:30 AM ET, 7:30 AM PT
Tel
Germany:
France:
Netherlands:
United Kingdom:
United States:
Connection code:
Phone numbers for other countries are also available
RIEDP-PDG - I/ITSEC 2014
02/11/2014

3. Introduction Status of RIEDP
RIEDP SG documentation :
Final Report approved by SAC and Executive Committee (06 Nov 2012)
Product Nomination approved by SAC and Executive Committee (July 2013)
RIEDP PDG
Kick-off during Fall SIW in Orlando 19 Sept 2013
Standard activity process
Standard Activity Committee (SAC)
Product Nomination
Study Group
(SG)
Study Group
(SG)
Product Development Group
(PDG)
Product Development Group
(PDG)
Product Support Group
(PSG)
Final Report
Product Nomination
Standard
RIEDP-PDG - I/ITSEC 2014
02/11/2014

4. Introduction Scope of RIEDP : Environmental Data
Standardization efforts needed in following areas :
Data model, formats, attribution and “miscellaneous” (incl. metadata).
Divided along two axes  leading to two products:
RIEDP Data Model Foundations with:
A Reference Process Model (RPM)
A Reference Abstract Data Model (RADM): Tiles, Layers, Library, ...
An (optional) tiling scheme to facilitate reuse
RIEDP Detailed Features description at the lower level part of the RADM
Objects: Identification of geo-specific object instances and classes (features, 3D objects, textures) within the Library, and the linkage between instances and classes;
Dictionary: choice of semantics and mapping with existing dictionaries
Attribution:
Identification of a common list of features and attributes
Identification and definition of common attribution rules.
RIEDP-PDG - I/ITSEC 2014
02/11/2014

5. Introduction RIEDP PDG Officers
Chairman
Jean-Louis GOUGEAT SOGITEC
Vice Chairman
Simon SKINNER XPI Simulation
Technical Area Director
Peggy Gravitz Aegis
Drafting Groups
DG1 Editor : RIEDP Core Team
DG2 Co-Editors : Amos Kent – Gilbert Castaner
Please Volunteer for Member and Editor Positions
RIEDP-PDG - I/ITSEC 2014
02/11/2014

6. Introduction RIEDP PDG – Communication Method
Please join the RIEDP Community
PDG SISO Discussion - Register for Discussion:
Logon to SISO Discussions and select
SAC-PDG-RIEDP (Don’t forget to select SUBMIT !)
PDG SISO Webpage - Complete Affiliation Form:
Standards Activities > Development Groups >
Reuse and Interoperation of Environmental Data and Processes (RIEDP) PDG
PDG SISO Library File Folder – Access PDG Documents:
SISO Digital Library > Development Groups > RIEDP PDG
RIEDP-PDG - I/ITSEC 2014
02/11/2014

7. Summary of Past Events
RIEDP-PDG - I/ITSEC 2014
02/11/2014

8. Current status Summary of past events
Previous Meetings
F13 SIW KickOff
Telecon1 15/11/2013
IITSEC'13 Day1, Day2
Telecon2 29/01/14
Telecon3 16/07/14
Fall SIW 2014
Telecon4
Approval of Telecon4 Notes
All Notes posted on RIEDP Library XL
Notes
RIEDP-PDG - I/ITSEC 2014
02/11/2014

9. DG1 DG2 DG3 DG principles Check Consistency Find PDG Consensus
Approve within PDG
Towards Balloting
- Reference Doc
- Copyrights
Define for Doc1 & 2 :
Doc Headlines
Sections principles
Guidances
Wording by DGM
Cross Reviews
Identify
Use
Draft Doc1
Draft Doc2
Recommandations
V0 Doc1 & 2 for PDG approval
V1 Doc1 & 2 for balloting
§ allocation
§ wording
Flesh out Doc 1
Find DGM consensus
Align with Doc 2
Flesh out Doc 2
Align with Doc 1
DG2
DG3
Doc 1 = RIEDP Data Model Foundations (RPM+RADM)
Doc 2 = RIEDP Detailled Features Description

10. RIEDP Data Model Foundations - Reference Process Model (RPM)
RIEDP-PDG - I/ITSEC 2014
02/11/2014

11. RIEDP Data Model Foundations – RPM Recent step
Population of the RIEDP DM Foundations / Section 4.2 RPM
Based on
Existing Description from Final Report
Complement from SE Core Documentation
Elements From NPSI and AFCD
Elements From Sogitec Sindbad
Who ?
DG 2 : Gilbert as Co-DGE – Other Co-DGE Missing
SE Core : Contribution as Co DGE2 ?
USAF : Back in RIEDP PDG ?
Schedule
End of 2014
Status during Telecon4 Done
Status during IITSEC
RIEDP-PDG - I/ITSEC 2014
02/11/2014

12. New Draft of the RPM
I/ITSEC 2014
05 dec 2013

13. RPM vs SE Core
SE CORE Requirements
I/ITSEC 2014
05 dec 2013

14. RPM vs AFCD/NPSI « Intermediate Level » AFCD/NPSI Requirements area
SE CORE Requirements
I/ITSEC 2014
05 dec 2013

15. RPM vs FAF « Intermediate Level » AFCD/NPSI Requirements area
French Airforce Requirements area
SE CORE Requirements
I/ITSEC 2014
05 dec 2013

16. Enhanced Intermediate Level
Out of scope
AFCD/NPSI Requirements area
French Airforce Requirements area 16
SE CORE Requirements
I/ITSEC 2013
I/ITSEC 2014
05 dec 2013

17. Population of RIEDP Data Model Foundations
Every contribution to this effort is welcome
in Section 1, 2 and 3 (Definitions),
more specifically to 4.2 (Reference Process Model):
A diagram has been established (§ 4.2.1)
based on the best of SE Core/CVEM, NPSI and AFCD, Sindbad and RIEDP SG initial model, with stages identified.
A guidance is provided :
Each stage is to be described in terms of actions to be performed, input / outputs data.
Quality and metadata activities in the process are to be described in a dedicated chapter.
Available information from SE Core, NPSI and AFCD processes has been inserted in each section. This has to be taken into account if relevant to establish the description of the stage. Inconsistencies have to be solved.
RIEDP-PDG - I/ITSEC 2014
02/11/2014

18. Population of RIEDP Data Model Foundations
A draft description has been established
for Stage 1 (Define Requirements)
Stage 2 (Collect Source Data).
Stage 3 (Clean Terrain Source dataset)
Stage 4 (Create Additional Data)
The new text is proposed in Blue.
For traceability purposes
what has been selected from original wordings is highlighted in Green,
what was not selected is highlighted in Green.
This draft will be discussed and Contributors  to the various stages will be identified.
It is essential that participants to the webmeeting:
have reviewed the document prior to the event,
have asked for clarifications if needed,
have identified their area of possible contributions (not only in § 4).
Report
RIEDP-PDG - I/ITSEC 2014
02/11/2014

19. RIEDP Data Model Foundations - Reference Abstract Data Model (RADM)
RIEDP-PDG - I/ITSEC 2014
02/11/2014

20. Shareable Data : Three steps
n % ?
Quality Check - Improvement
Requirements :
Areas
Insets
LOD
Terravista,
Terratools, VBS2
Arc GIS
Arc GIS + Plugin
Arc GIS + Plugin
N Steps Process
Source :
- Vectors
- Imagery
- Elevation
- 3D Models
Various Targets
Cleaned Source
Data Sets
Intensified Source
Data Sets
Specialized Source
Data Sets
Runtime DB
Specialized Source
Data Sets
Runtime DB
LOD :
1: 250K
1: 50K
1: 25K
1.12,5K
ConfederateSpecialized Source
Data Sets
Runtime DB
Runtime DB
Applications :
- Training
- Mission Rehearsal
No Tiling
Imagery used to extract features
Scattering Features
Adapted consistent
Data Sets
Synthetic Imagery
70 %
80 % ?
90 % ?
Geography
Simulation
Machine
RIEDP-PDG - I/ITSEC 2014
02/11/2014

21. Where is the Intermediate Level ?
Stages of enhanced reuse
RIEDP-PDG - I/ITSEC 2014
02/11/2014

22. Reference Abstract Data Model @ Intermediate Level
High Level Concepts of a Database
Showing areas of convergence and variability
Tiles, Layers Library,
Elevation Layer
Feature Layer
3D Objects Layer
Texture Layer
…….
The upper part of the RADM (highlighted in solid purple) means that all initiatives may share (even though the RADM may not cover all cases) a similar view of the high level concepts of a database at the integrated level:
The DB is composed of geo-referenced tiles containing a set of layers: elevation, features, object, texture …
Feature instances of the real world are attached to tiles, and their rendering characteristics (visual, behavior …) are provided by the objects (and their attributes) from the library to which they are linked.
The middle part of the RADM (highlighted in dashed purple) may also be shared by all initiatives, as it is supported by their use of common GIS formats:
DTED, GeoTIFF, … for elevation;
Shapefiles for features;
OpenFlight for 3D objects;
JPEG2K, GeoTIFF, … for textures.
The lower part of the RADM (highlighted in yellow) corresponds to the attribution aspect of Shapefiles which is not constrained by the format. As a consequence, this is an area of divergence between initiatives.
Miscellaneous: other possible areas of divergence have been identified (yellow areas):
The Special areas, including for example airports and urban areas, that may be described either as features not related to tiles, or as OpenFlight objects;
The linkage between the objects of the Library and the Features;
Metadata associated to the database, which eventually feeds the catalog associated to the repository.
COTS
Variability
Common format
User Defined options
For features
Convergence
RIEDP-PDG - I/ITSEC 2014
02/11/2014

23. RIEDP Data Model Foundations – RADM Next step
Population of the RIEDP DM Foundations / Section 4.3 RADM
Based on
Existing Description from Final Report
Complement from :
SE Core Documentation on MDB
NPSI Documentation
Who ?
New DG 2
Schedule
End of 2014
Status during IITSEC
RIEDP-PDG - I/ITSEC 2014
02/11/2014

24. RIEDP Detailed Features Description
RIEDP-PDG - I/ITSEC 2014
02/11/2014

25. RIEDP Detailed Features Description Approach
During Telecon2, it was agreed that it was currently difficult to go into high detail on DG3 (Attribution subject) before the RADM is sufficiently stabilized.
However, preliminary discussion was held during Telecon3 to analyze possible approaches.
RIEDP-PDG - I/ITSEC 2014
02/11/2014

26. RIEDP Detailed Features Description Approach
Process
Assess available Dictionaries and select the most suitable as the RIEDP reference dictionary
Check what is available and what is missing in these dictionnaries
Identify required extensions or additions to the dictionary
Identify the required collection of Features (classes) and Attributes needed for RIEDP
Define what is mandatory and what is optional
Define how this collection can be described with the reference dictionary
Identify mappings between RIEDP Attributions and those used by the initiatives/users
This process will be incremental (for initialization and as for updates), it is important to define a flexible way of characterizing the underlying “Data model” of the attribution Features and Attributes.
RIEDP-PDG - I/ITSEC 2014
02/11/2014

27. RIEDP Detailed Features Description Next step
Initialization of the RIEDP DFD
Based on
???
Who ?
DG 3
Volunteers ?
Schedule
End of 2014
Status during IITSEC
RIEDP-PDG - I/ITSEC 2014
02/11/2014

28. Next Meetings
RIEDP-PDG - I/ITSEC 2014
02/11/2014

29. MSCO Geo Spatial event at IITSEC
Next Meetings
MSCO Geo Spatial event at IITSEC
RIEDP PDG Brief as usual
Coordination with RDG ?
Telecon 5
TBD
ITEC 2015 RIEDP PDG Meeting
Who plans to attend ?
RIEDP-PDG - I/ITSEC 2014
02/11/2014

30. Action Items
RIEDP-PDG - I/ITSEC 2014
02/11/2014

31. Action Items Attendance
RIEDP-PDG - I/ITSEC 2014
02/11/2014

32. AOB
RIEDP-PDG - I/ITSEC 2014
02/11/2014

33. AOB
RIEDP-PDG - I/ITSEC 2014
02/11/2014

34. Conclusion
RIEDP-PDG - I/ITSEC 2014
02/11/2014

35. Conclusion
During Session
RIEDP-PDG - I/ITSEC 2014
02/11/2014

36. Collect Source Data
I/ITSEC 2014
05 dec 2013

37. Convert & Geoprocess attributes,
Clean Dataset
Convert & Geoprocess attributes,
Combine, Geoposition,
Reproject, rectify,
Merge, Balance,
I/ITSEC 2014
05 dec 2013

38. Create Additional Data
I/ITSEC 2014
05 dec 2013

39. Correlate between layers!
Align Source Layers
Correlate between layers!
I/ITSEC 2014
05 dec 2013

40. Establish Baseline Source Dataset
Convert Dataset components
to RIEDP « formats »
I/ITSEC 2014
05 dec 2013

41. Intensify Baseline Source Dataset
Associate Library objects
with terrain features !
I/ITSEC 2014
05 dec 2013

42. Specialize Application Datasets
Derive simplified datasets to
cope with simulators’ capabilities !
I/ITSEC 2014
05 dec 2013

43. (R,G,B,Nir; hyperspectral) SimSys eCognition data base MERLIN
Database Generation
New input from BwB (German MOD) German example of DB Generation process
ERDAS
Imagine
LPS
textures,
plan
DSM
ortho imagery
imagery
DSM
Ortho imagery
(R,G,B,Nir; hyperspectral)
SimSys
eCognition
data
base
MERLIN
Vector data
ArcGIS stereo
analyst
ERDAS IMAGINE, LPS Photogrammetry tool
eCognition Classification tool
MERLIN DGBS
ArcGIS stereo analyst 3D-extraction tool