GEOCOM PROJECT INTEGRATING DATA & TECHONOLOGIES

Size: px

Start display at page:

Download "GEOCOM PROJECT INTEGRATING DATA & TECHONOLOGIES"

Eugenia Hawkins
10 years ago
Views:

1 GEOCOM PROJECT INTEGRATING DATA & TECHONOLOGIES Lucio Colaiacomo Chief Technology Officer

2 Rationale for the project Providing support through our domain background & tech. expertise Facilitate the EUSC staff work : Have an updated internal data dictionary, compliant with the actual missions and production of EUSC Have an updated, flexible, DB export capability, and image and vector DB ingestion (Apollo data manager) Have a capability to easily «ingest» GEOINT existing productions, allowing EUSC analysts to concentrate on their most demanding tasks Improve the diffusion channels of the EUSC products : Capability to better deliver data through standards to Defense customers Coding capability toward GEOINT standards (MGCP-TRD is a prime candidate) Maximize the data sharing processes : Standard Web Services to foster On-line Geo-browsing, instead of off-line CDs or DVDs Enhance compliance with SDI ongoing initiatives in Europe (in the defense & security fields)

3 Rationale for the project Goal statement Provide support to formalize and communicate the EUSC approach to cope with different export capabilities (MGCP, VMAP/FACC, ) from the new revised EUSC Data Model

4 Support Team: ERDAS / Geo212 / Exprivia Working experience in IMINT / GEOINT harmonization projects Expertise with interoperability & standardization programs and projects at international (NATO, DGIWG, VaCWG, OGC, ISO, GEOSS), european (CEN, UE, GMES ) and national levels Technological knowledge IMINT OSINT GEOINT

5 Open source intelligence (OSINT) is a form of intelligence collection management that involves finding, selecting, and acquiring information from publicly available unstructured sources and analyzing it to produce actionable intelligence. In the intelligence community (IC), the term open refers to overt, publicly available sources (as opposed to covert or classified sources); it is not related to open-source software or public intelligence. Source:

6 Results from geocom 2008 prototype geocom use cases for seamless data access and data sharing

7 OGC standard used CAT2 AP ebrim * CAT CS-W * WMS POST WMS (compliant) * WMS * WMS 1.1 WMS 1.0 WMC 1.1 * WMC 1.0 WMC WFS(T) (compliant) *(+/-) WFS * WFS (compliant) WCS-WSDL WCS (compliant) WCS 1.0 * WCS 0.7 And more, like e.g.: SLD 1.0 OWS common GMLsf GML GML 3.0 GML Filter 1.1 Filter 1.0 KML ImageCRS 1.1.0

8 Way ahead geocom 2009/2010 Objectives of the 2009 activity is to put in place all the instruments in order to simplify the distribution and integration of the EUSC products in your repositories Data Dictionary Harmonization Data Model definition Along with, early 2010, test cases scenarios based on a common operational picture (to be agreed jointly), for distribution & integration Integration with OSINT data (Deep Knowledge engine)

9 Schedule Step 1 : Data model / Data dictionary correspondences EUSC users requirements for services Week 48 (November ) Step 2 : Production of test data sets based on the agreed scenarios Evolution of the EUSC Rapid Coder Week 2 (January ) Step 3 : Definition of portrayal rules Tests of web services based on users requirements & EUSC wishes Step 4 Deep Knowledge engine integration Step 5 EUSC Coder operational installation Week 15 (April ) Week 22 (May ) Week 38 (September )

10 Step 1 Step 1 : Data model / Data dictionary correspondances EUSC users requirements for services Data model / Data dictionary correspondences Objects & attributes Metadata requirements initial analysis EUSC Data Dictionary MGCP Data Dictionary Other relevant Data Dictionary

11 Step 1 (Cont ) Actions : Internal EUSC data dictionary evolution Data model definition 27/11/09 Comparison EUSC / MGCP data dictionary 27/11/2009 EUSC Users expertise on the document 12/2009 EUSC Users requirements for services Interview of National Users on their specific requirements for data access (geo-browsing, visualization, subset on line recovery, 30/11/2009 Production of a detailed report for EUSC Definition of test cases scenarios based on a common operational picture (to be agreed jointly), for distribution & integration

12 Step 2 Step 2 : Production of test data sets based on the agreed scenarios Evolution of the EUSC Rapid Coder Production of test data based on the agreed scenarios Based on real life unclassified EUSC products Production of the required metadata Data preparation & integration Evolution of the EUSC Rapid Coder Integration of the new internal data dictionary Impact on the extraction guides and rules Definition of a «MGCP» export coding Evolution analysis

13 Step 3 Step 3 : Definition of portrayal rules Tests of web services based on users requirements & EUSC wishes Definition of portrayal rules for the data integrated in the test Based on existing EUSC products Tests with participating countries Experimentation report

14 Step 4 Step 4 : OSINT integration Setting up of a Common OSINT Data Repository Introduction of automatic classification and geo-referencing of the data in the Common OSINT Data Repository through the adoption of the DeepKnowledge engine (DK) Use of the STANAG Standard 3769 as a classification schema Use of a geographical gazetteer derived by the NGA, GNIS and geonames.org including more than locations (countries, cities, etc.) providing multi-language support (local language, english) Including GIS coordinates for each location Use of advanced semantic analysis techniques Feeding of APOLLO Data Manager with classified and geo-referenced OSINT data Data as External Custom Objects (GIM format) Direct use of ERDAS Imagine Client to search OSINT data 14 23

19 Arc gis connected to Apollo

The FGDC Geospatial Metadata Standard and Other Initiatives

The FGDC Geospatial Metadata Standard and Other Initiatives Norman C. Andersen NGA Metadata Officer, National Center for Geospatial Intelligence Standards Overall Classification of this briefing is UNCLASSIFIED