RIEDP PDG Telecon12 – 20 October 2015 Summary of RIEDP DM Foundations Document informal Review n°2 Référence – Date : E2Cxxxx du RIEDP-PDG - Telecon12

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.  Introduction  Members and Quorum  Status of Informal Review n°2 - RIEDP DM Foundations Document  Other issues  Glossary  Additional Formats requirements  Way Forward  AOB  Conclusion Agenda RIEDP-PDG - Telecon October 2015

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. Web connection information  Tuesday, 20 October 2015  4:30 PM France, 3: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  Introduction Web connection information RIEDP-PDG - Telecon October 2015

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. 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 New 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 3 RIEDP - Fall 14 SIW Meeting 10/09/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. Introduction DG2 members - Attendance - Quorum RIEDP-PDG - Telecon12 4 NomPrénomOrganismeSISO StatusDG2AttendingVoting BAILEYGrant UK MoD Current SISO Member Yes CASTANERGilbert SOGITEC Current SISO Member Yes COGMANJack DATASIM Current SISO Member Yes COXRob PEO STRI / RDG YesNo ENOCHIANDavid USAF Not a SISO Member YesNo FAULKMark LEIDOS unclearNo FOLEYPaul DOD Terrain MSEA NGA Current MemberYes HOPKINSONBill MSCO unclearNo HUMPHRIESRoland XPI Simulation Expired Membership 2014 YesNo IGARZAJean-Louis Antycip Simulation France Current SISO Member Yes MACCHIWarren ABAMIS YesNo MAMAGHANIFarid Self Expired Membership 2013 YesNo MARROULance LEIDOS Current SISO Member Yes MOORERonald LEIDOS Expired in 2014YesNo PEELEGreg ARA Expired in 2014YesNo REIFAndreas BwB Current SISO Member Yes ROBBINSBruce US Army/PEO STRI/OneSAF Expired in 2012YesNo SCRUDDERRoy Univ Texas Current SISO Member Yes SIEGFRIEDRobert ADITERNA Current SISO Member Yes TABOURETYann TT&S Current SISO Member Yes GOUGEATJean-Louis SOGITEC Current SISO Member PDG ChairNo 20 October 2015

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. First NameLast NameAffiliation Created 12:04 PM 1:54 AM Jean-Louis GougeatSogitec 3:57 AM PatriceLe 4:51 AM ArjanLemmersNetherlands Aerospace Centre 4:25 AM LanceMarrouSE Core 5:28 PM AndreasReifGerman Armed 8:21 AM DavidRonnfeldtAustralian Defence S&T 5:55 PM RobertSiegfriedaditerna 4:53 AM SimonSkinnerXPI Simulation Ltd - Thales 4:22 AM Introduction PDG Affiliation List Members RIEDP-PDG - Telecon October 2015

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. 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 - 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 - Find DGM consensus - Align with Doc 1 § allocation § wording Doc 1 = RIEDP Data Model Foundations (RPM+RADM) Doc 2 = RIEDP Detailled Features Description 6

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. RPM with Import/Export Stage RIEDP-PDG - Telecon October 2015

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. RADM RIEDP-PDG - Telecon October 2015

Status of Informal Review n°2 RIEDP DM Foundations Document RIEDP-PDG - Telecon12

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. Informal Review n°2  Final comments from PDG members25 September 2015  Integration of commentsEnd October 2015  Introduction (Preface, § 1, §2, § 3, § 4.1)~ finished ?  Glossary  RPM (§ 4.2)~ finished ?  RADM (§ 4.3)~ to be discussed/improved  Boarder with Product n°2  Data Organization to be discussed/improved  Data Profileto be moved into conformance ?  Conformanceto be discussed/improved Submission to Formal Review and Balloting : December 2015 ?  Process to be prepared  Guidance from TAD Principles of IR n°2 10/09/2014 RIEDP - Fall 14 SIW Meeting 10

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. What  The RIEDP DM Foundations Document : Version 0.9f When  Launched on August 25  Dead Line : Initial Septembre 25 - Extension 2 weeks Objective  Finalization of Introductory Sections  Finalization of § 4.2 : RPM section  Review of § 4.3 : New RADM section  General Comments Target  DGE2 to provide updated version October 25. Informal Review n°2 RIEDP-PDG - Telecon October 2015 Foundations

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. Action Items summary RIEDP-PDG - Telecon12 12 Foundations 20 October 2015

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. Feedback so far:  Paul  Greg  Rob (Partially)  Sylvie (Sogitec expert) Expected  Rob  TTS  Ron/Lance ?  Other Informal Review n°1 20 October 2015 RIEDP-PDG - Telecon12 13

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.  RPM : Through all of 4.2, I only have some minor items:  In 2.2 Other References : AFCD v3 is the current version;AFCD v3  I will forward a copy to Jean-Louis (Done)  DGIWG is used in the document, but not defined in the acronym table.  There's probably more, but this one caught my attention.  Typos to be checked.  RADM :  I thought 4.3 was coming together well and had no particular content issues.  I didn't bother to try to correct format(style) issues at this stage in development. Informal Review n°1 / Greg 20 October 2015 RIEDP-PDG - Telecon12 14

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. Informal Review n°1 / Paul  RPM  Glossary  Data is or are ?  Figure #  Gaming area vs Area of interest  Will vs Shall (may, can, must, is)  Geotypical vs Generic  Geospecific vs Approx of real obj  PSR / ASR  § 4.1 : Other formats may be used, but must support the content of the listed RIEDP format and be provided with any special tools required for their processing and use in a RIEDP- compliant data exchange.  RADM  Figure #  EDS Ref  Catalog vs Repository  Geographical vs Environemental  OTW  Links between objects (TBD clearly) 20 October 2015 RIEDP-PDG - Telecon12 15 Doc

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. Rob To ?  I took an action at the last RIEDP meeting (yea - based on my view of a changing landscape) to look at and provide updated text for Section 4.1 Data Format section:  Data Formats: To accomplish the interoperability and data exchange goals, and to support the user community, the RPM and the RADM use an existing set of formats for communicating the data produced in accordance with this specification. The terrain-related data formats required for RIEDP-compliant data exchange, and collectively referred to as the RIEDP formats, include the following:  GeoTIFF (revision 1.0 October 1995), for terrain elevation data.  ESRI Shapefile (technical description White Paper July 1998), for terrain features and vector data such as transportation networks, hydrology, physiography, and terrain regions.  GeoTIFF (revision 1.0 October 1995) or JPEG 2000 (ISO/IEC Part 1) for imagery data.  OpenFlight (version 16.0 or higher), for 3D objects and models, both natural and man-made, placed on the terrain or dynamically included in the environment.  PNG (ISO/IEC 15948:2004), SGI RGB or SGI RGBA, image formats for texture maps, used in portraying object surfaces and some terrain surfaces (geotypical or generic textures).  I am soliciting your opinion/input on this before I draft the text. Any suggestions or re- writes would be greatly appreciate.  If I could have your input by COB on 5 October, it would be greatly appreciated. Informal Review n°1 / Rob 20 October 2015 RIEDP-PDG - Telecon12 16

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. Introduction and RPM  No Comments  Except : No familiar with EDS …  And Figures numbering  Task « Create Feature Mapping » in Intensification to be moved to Baseline ? RADM  Elevation Layer : Duplication of metadata (format and Layer) is bad  Imagery Layer : Idem  Feature Layer : Elevation may also appear  Feature attributes : Table Updated  4.4 Organization of the Data : where are stored the DB Metadata ?  Level 2 – Tiles Folder : Layer metadata to be merged above tiles  Level 2 - Metadata Folder : Shapefiles list modified Informal Review n°1 / Sylvie RIEDP-PDG - Telecon12 17 Doc 20 October 2015

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. This update includes:  addition of new text about criteria for RIEDP and non-RIEDP formats  addition of new sections for both RIEDP and non-RIEDP format criteria  (but the sections have no content, yet)  re-organization of 4.1  some consistency changes discussed in Core Team  Greg's comments, most of Paul's changes, Sylvies’s comments  Reintroduction of the informative section on RPM use that was deleted  misc. minor changes; change-tracking is on, but for some minor things  Figure numbers fixing  Document metadata updated : ToC, ToF, Date, Version Number, History table … New version of the Foundations document RIEDP-PDG - Telecon12 18 Foundations 20 October 2015

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. What is missing:  need to populate the new sections for format criteria  after we discuss the criteria details  not all singular/plural uses of "data" are done consistently  another pass is needed on this  "shall", "will" issues  needs careful review  Some other consistency issues  needs careful review  Some comments from Paul to be discussed with him on Tuesday  Complete review of Section 4.3  Review of the informative section on RPM  Updating through  Writing the missing sections (such as Profile, more on Conformance, etc.) New version of the Foundations document RIEDP-PDG - Telecon October 2015

Other Important Issues : - Glossary - Formats specifications - Additional Formats requirements RIEDP-PDG - Telecon12 20 October

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. Initiated by Lance Reviewed by Core Team  (Cleaned, Added … to be Aligned before Intensification !!) Status of Glossary RIEDP-PDG - Telecon12 21 Glossary 20 October 2015

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. Motions Issue : Extension of Format lists - Requirements RIEDP-PDG - Telecon12 MotionsMeetingResult Object Motion 1Telecon8OK Guidance document’s specified formats apply only to external data exchange, not to internal storage Motion 2Telecon8OK To comply with RIEDP data exchange (at output of any of the stages), the data provider should be compliant with a specific list of RIEDP identified formats (TBD formats). If other formats are to be used by the data provider for external data exchange, a specific set of requirements (TBD) for those additional formats shall be followed/abided Motion2 Reworded Telecon9 If other formats are to be used by the data provider for RIEDP data exchange, these formats shall comply with a specific set of requirements (TBD) October 2015

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. Sogitec meeting with ESRI France  Purpose :  Understand ESRI Geodatabase  Understand the situation of Shape Files, Geodatabase and Geopackage  Content  Shapefiles  Various Geodatabases  What about Geopackage  Conclusion Brief on meeting with ESRI 20 October 2015 RIEDP-PDG - Telecon12 23 Doc

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.  Shapefiles is simple and commonly used,  but some limitations are proposed in Geodatabase for Data production.  Geodatabase is both a container and a data model,  which is close to Attribution and Dictionary components from RIEDP.  ESRI considers that Shapefile remains a good solution to export des vector data  Attribution / Data model information must be stored in a separate (xml) file  Geopackage is supported by ESRI.  It is an interesting Export solution allowing to capture other types of data (RASTER)  Note that Simulation specific components (3D Models and attributes) require additional specifications relevant to RIEDP.  Non adherence to proprietary solutions is to be considered, knowing that Shapefile is a de facto standard in Air Training and Mission Rehearsal community.  For RIEDP a solution may be :  Core Export Formats : Geotiff, OF, Shapefiles, … for all stages  Additional Export Formats : FGDB, Geopackage … from Stage 4  DataModel (xml for Shape and DM part of Geodatabase) need to be consistent : Product n°2  Compliance statement needs to be established … Brief on meeting with ESRI / Conclusion 20 October 2015 RIEDP-PDG - Telecon12 24

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. Mainly  Current Formats specifications  Additional Formats requirements And  This is a lot of work  This delays issuing the first product  This could be differed to second product as related to attribution What about it ? Missing elements 20 October 2015 RIEDP-PDG - Telecon12 25

Way Forward RIEDP-PDG - Telecon12 20 October

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. Main steps of the Process  PDG Chair sends document to SAC  SAC reviews and approves document for Official Review  SAC establishes Comment Tracking System  SAC asks for volunteers for ReviewHow ?  Volunteers identify themselvesHow ?  SAC check validity of the Group  Review Period is launched  Reviewers feed the CTS and Vote (Y/N/?)  Comments are resolved by DG  Resolutions are voted  Reviewers reassess their vote  Recirculation ???  ????? Towards Balloting 10/09/2014 RIEDP - Fall 14 SIW Meeting 27

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.  Product 1 – Foundations  Without Product 2  After informal Review n°2 comments Resolution  Especially Section 4.3 and subsequent  Start the process end of October ? Instanciation to RIEDP 10/09/2014 RIEDP - Fall 14 SIW Meeting 28

RIEDP Detailed Features Description RIEDP-PDG - Telecon12

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. 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.  Core Team work current results :  DG3 has now an impact on DG2  Attribution RIEDP-PDG - Telecon October 2015

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. 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 - Telecon October 2015

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. 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 - Telecon October 2015

Next Events RIEDP-PDG - Telecon12

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. Next Events Telecon 13  To be held during Week ?Date to be agreed I/ITSEC 2015  Who plans to attend ?  Availability of a Room ? MSCO as last Year ? Target for Foundations document finalization RIEDP-PDG - Telecon October 2015

Action Items RIEDP-PDG - Telecon12

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. Action Items Attendance RIEDP-PDG - Telecon October 2015

AOB RIEDP-PDG - Telecon12

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. AOB ?? RIEDP-PDG - Telecon October 2015

Conclusion RIEDP-PDG - Telecon12

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. Conclusion During Session RIEDP-PDG - Telecon October 2015

Backup RIEDP-PDG - Telecon12

ESRI RIEDP-PDG - Telecon12 42

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.  Shapefiles  Created in 1996 by ESRI  Still ESRI IPR but  No Royalties,  Open  Not Open source  Notion of independant Layer for features  Point, Line, Areal  4 files at least per layer  DBase 4, with limitation to 2 Go per layer Brief on meeting with ESRI / Shapefiles 20 October 2015 RIEDP-PDG - Telecon12 43

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. Geodatabase  Geodatabases are at the same time  A container (Directory & Files)  A data model  2 types of Geodatabases :  Entreprise Geodatabase  Personal or File-based Geodatabase  Entreprise Geodatabase  Based on a standard DBGS (BM, ORACLE, SQL, )  Improvement to keep up with DBGS evolutions (~every 18 months)  Requires an extented version of ARCGIS  Suitable for multi user production efforts Brief on meeting with ESRI / Geodatabase 20 October 2015 RIEDP-PDG - Telecon12 44

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. File-based GeoDataBase (FGDB)  Origins  1er version début année 2000 basée sur Access  2ème version vers 2004, basée sur un moteur SGBD propriétaire.  FGDB Content  Multiple layers of Vector data  May also refer to Raster data via a catalog (requires « Standard » version of ARCGIS  FGDB export features  Basic ArcGIS allows export of Geodabase to Shapefiles (one shapefile per layer).  Open API avaiable to non customer to access to the FGDB  No up to date documentation available on FGDB structure  No tile in a FGDB  one FGDB per tile or other solution ?.  L’éditeur SME dispose aussi d’outils d’import/export pour passer d’une FGDB à des shapefile.  Data model  A Geodabase is always associated to a User Defined Data Model (via Tables).  This DM may be exported via ArcGIS in an xml file Brief on meeting with ESRI / Geodatabase 20 October 2015 RIEDP-PDG - Telecon12 45

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.  Shapefiles limits disappear in FGBD  File size, File and Attributes name size, …  1 TeraByte FGDB file  Faster access to information  Characterization of data in domain and sub types  Definition of data ranges to facilitate data manipulation  Note :  More than 50 layer FGDB is difficult to manage  Note :  MGCP (Multinational Geospatial Co-production Program) interchange format is Shapefiles. Brief on meeting with ESRI / Shape vs FGDB 20 October 2015 RIEDP-PDG - Telecon12 46

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.  GEOPACKAGE :  OGC Standard.  2 documents : Spécification + Implémentation  Based on SQL Lite  Supported by ESRI  Suitable for Mobile applications Brief on meeting with ESRI / GEOPACKAGE 20 October 2015 RIEDP-PDG - Telecon12 47

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.  Shapefiles is simple and commonly used,  but some limitations are proposed in Geodatabase for Data production.  Geodatabase is both a container and a data model,  which is close to Attribution and Dictionary components from RIEDP.  ESRI considers that Shapefile remains a good solution to export des vector data  Attribution / Data model information must be stored in a separate (xml) file  Geopackage is supported by ESRI.  It is an interesting Export solution allowing to capture other types of data (RASTER)  Note that Simulation specific components (3D Models and attributes) require additional specifications relevant to RIEDP.  Non adherence to proprietary solutions is to be considered, knowing that Shapefile is a de facto standard in Air Training and Mission Rehearsal community.  For RIEDP the solution may be :  Core Export Formats : Geotiff, OF, Shapefiles, … for all stages  Additional Export Formats : FGDB, Geopackage … from Stage 4  DataModel (xml for Shape and DM part of Geodatabase) need to be consistent : Product n°2  Compliance statement needs to be established … Brief on meeting with ESRI / Conclusion 20 October 2015 RIEDP-PDG - Telecon12 48

Alternate formats RIEDP-PDG - Telecon12 49

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.  SE Core uses OpenFlight and FilmBox for internal storage and external data sharing.  SE Core evaluated COLLADA for model sharing, but determined that exporting to COLLADA was not worth the cost. OpenFlight supports a complex simulation- centric model hierarchy using defined organization nodes, whereas, COLLADA would require defining these organization nodes. Reading and writing to OpenFlight is supported by all of the Modeling and Simulation (M&S) applications used by SE Core, reading and writing to COLLADA would require developing extensions and plug-in to some of the SE Core M&S applications. COLLADA does provide a more flexible data organization, but would require developing a specification to facilitate consistent reading, writing and sharing. COLLADA is maintained by the Khronos Group, a member-funded industry consortium. OpenFlight is maintained by Presagis. SE Core uses Creator for 3D modeling. Creator is owned by Presagis.Khronos Group  Additionally, SE Core uses Maya and 3D Studio Max for 3D modeling. FilmBox, provides the most complete storage of these Maya and Max complex models, and is easily exported to OpenFlight.  To keep SE Core 3D model production as simple as possible, FilmBox and OpenFlight are used for internal storage, and for no-conversion sharing. SE Core Update OpenFlight – FilmBox - RIEDP-PDG - Telecon October 2015

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.  Use of FilmBox size (FBX) is actually a practical choice and completely justified for the exchange of complex models between Maya and 3ds max, both published by Autodesk that owns the format in question.  My reluctance on the FBX are:  That the support for this format is conditioned to use the Autodesk SDK, and relies on the goodwill of a community of users to benefit from an unofficial format specification (http: // code.blender.org / 2013/08 / FBX-binary-file-format-specification /). The open source SDK is an individual initiative whose sustainability is uncertain at best.blender.org  That this poses problems of distribution of our own SDK, which can only include the FBX SDK.  That this SDK imposes de facto technological guidance in terms of language and type of information exchanged.  We use the FBX rather as a graphic interchange format, not as an exchange format simulation data. Yann Update TT&S Use of FBX RIEDP-PDG - Telecon October 2015

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.  My arguments for the COLLADA  Supported by a strong and representative consortium, which remains agnostic. It does not promote a software publisher using COLLADA.  With Open Flight or FBX, a blank check is made to a Canadian publisher or American publisher respectively, relying on these publishers to make technological developments available.  Supported also by Autodesk through the same plugin as for FBX for Maya and 3DS Max.  The format is designed to be easily extensible. The corollary is that extensions for exchange must be agreed upon in the community.  Relies on XML, so from a technical point of view, is easily assimilated.  Already extended by Thales to support simulation specific features (georeferencing, LOD DOF, switch, characterization, IR / NVG data, materials animations....) and we have a SDK. This is our exchange format for data simulation environment. They have also been exploited by third parties.  I hope these elements will help develop the solution to a set of recommendations whose spirit is to facilitate the exchange limiting the constraints of use of specific Tools. Yann Update COLLADA vs FBX and OpenFlight RIEDP-PDG - Telecon October 2015