SatCen faces significant challenges when integrating GIS datasets from multiple sources, which are often in different formats, scales, data models, granularity, and segmentation. Data integration requires converting data into a common format and data model, which can result in issues with precision, scale, meaning, and structure of the data. For instance, the same object may be duplicated among different sources, such as a street represented as one line feature in one dataset and as multiple line features in another. In response to the need to increase the efficiency of migrating Open Street Map (OSM) data sources to their own data model, known as SatCen Data Dictionary (SCDD), EUSC has developed an Extract, Cleanse, Transform, and Load (ECTL) workflow using FME Desktop from Safe Software. To facilitate the mapping of OSM data to the SCDD, an analysis of OSM data sources is performed to define the schema mapping document. The analysis utilizes OSM tags consisting of a key and value. For the results, typical values are targeted rather than exceptional values. E.g. an aeroway tag with navigationaid is the typical value while navigation_aid and navigationalaid would be exceptional values. The TagInfo (https://taginfo.openstreetmap.org/) website lists these combinations and relative counts and provides a SQLite Database for download. This is the primary source of information for analysis. This workflow is based on standards for vector and raster data. The process for mapping Open Street Map data to EU SatCen data dictionary (Compatible with Multinational geospatial co-production program, MGCP), has been replicated with HERE/NAVTEQ mapping to the EU SatCen data dictionary and for the raster side from geotiff to GMLJP2 image compression/decompression with area blurring.

1. EU SatCen workflow automation for
data (vector, imagery) processing

2. The
Peak
of
Data
Integration
20
23
SatCen Goal
To produce timely, relevant, reliable, accurate geospatial intelligence
products and services (GEOINT) resulting from the exploitation of relevant
space assets and collateral data, including satellite and aerial imagery.
Value added products and services (solutions, not only data!)

3. The
Peak
of
Data
Integration
20
23
Our Comprehensive Mission
Support the decision making and actions
of the European Union in the field of CFSP
and CSDP, by exploiting relevant space
assets and collateral data..
..while maximizing synergies and
complementarities with other EU activities in
space & security
Directorate
Operations
Capability
Development
IT Admin Finance
Support to EU INTEL and the Member States
is at the core of SatCen’s Mission
Mix between civilian/military backgrounds
151 Staff,
18 Nationalities

4. The
Peak
of
Data
Integration
20
23
SatCen History
1992:
Foundation
(WEU)
2002:
EU Agency
(Council)
30th anniversary in 2022!
☺
2016:
EU Global
Strategy
2014:
SatCen Council
Decision
2009:
Lisbon
Treaty
2022:
EU Strategic
Compass

5. The
Peak
of
Data
Integration
20
23
SatCen Activities
Support to
CFSP/CSDP
Geospatial
Intelligence
Capability
Development
Cooperation
with EU
Bodies an
MSs
Training
Information
technology

6. The
Peak
of
Data
Integration
20
23
Users
EEAS
Member
States
International
Organizations
Missions
and
Operations
EU
Agencies
European
Commission
Key Partners

7. Presenters
The
Peak
of
Data
Integration
20
23
Lucio
Colaiacomo
Chief Technology Officer
EU SatCen
Soren
Dupke
Software Engineer
Con terra GmbH

8. The
Peak
of
Data
Integration
20
23
Agenda Option 1
1. Workflow
2. Imagery
3. Vector
4. Products

9. The
Peak
of
Data
Integration
20
23
Introduction

10. The
Peak
of
Data
Integration
20
23
Heterogenous data sources
harmonization
Satcen Data Model

11. The
Peak
of
Data
Integration
20
23
More in details
Data harmonization can help to:
• To create an homogeneous data base based on open
and commercial sources
• Common data model (EU Satcen, DGIWG (Defence
Geospatial Information Working Group approved)
• Common framework to enable a reusable and scalable
approach

12. The
Peak
of
Data
Integration
20
23
Common frustrations people face with this topic are:
● Standards interoperability
● Metadata harmonization
● Time consuming
Standardized data formats and integration in a
common data model

13. The
Peak
of
Data
Integration
20
23
Main workflow
INPUT
S
PROCESSING
i.e. Satcen Image Analysts’ and
SW/HW Platform
OUTPU
TS

14. The
Peak
of
Data
Integration
20
23
Imagery processing

15. The
Peak
of
Data
Integration
20
23
The request is to provide an automated mechanism to
compress geotiff input images with the possibility to blur or
not the data using a input file in shp format (zipped). The
result is compressed (GMLJP2) in lossy and lossless quality
.

16. The
Peak
of
Data
Integration
20
23
Image compression geot

17. The
Peak
of
Data
Integration
20
23
<gmljp2:GMLJP2CoverageCollection gml:id="ID_GMLJP2_0" xmlns:gml="http://www.opengis.net/gml/3.2"
xmlns:gmlcov="http://www.opengis.net/gmlcov/1.0" xmlns:gmljp2="http://www.opengis.net/gmljp2/2.0"
xmlns:swe="http://www.opengis.net/swe/2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://www.opengis.net/gmljp2/2.0 http://schemas.opengis.net/gmljp2/2.0/gmljp2.xsd http://www.opengis.net/eop/2.0
http://schemas.opengis.net/omeo/1.0/eop.xsd http://www.opengis.net/om/2.0 http://schemas.opengis.net/om/2.0/observation.xsd">
<gml:domainSet nilReason="inapplicable" />
<gml:rangeSet>
<gmljp2:featureMember>
…..
<gmljp2:GMLJP2RectifiedGridCoverage gml:id="RGC_1_ID_GMLJP2_0">
<gml:domainSet>
<gml:RectifiedGrid gml:id="RGC_1_GRID_ID_GMLJP2_0" dimension="2" srsName="{fme:get-attribute("_coordsys_raster")}">
<gml:limits>
<gml:GridEnvelope>
…..

18. The
Peak
of
Data
Integration
20
23
Vector data processing

19. The
Peak
of
Data
Integration
20
23
Mapping to SatCen Data Model (Open Street Map,
HERE/Navteq,…

20. The
Peak
of
Data
Integration
20
23
● Reading the input imagery in a specified directory
(defined by the user) associated gml file and zipped
blurring area (eventually) with the same name root of the
image.
● The image show the different functions involved:

21. The
Peak
of
Data
Integration
20
23
● Once the image has `passed the above steps the gml
metadata file is read

22. The
Peak
of
Data
Integration
20
23
● At this moment the metadata are associated to the image
file
● The next step is important because following the requests
the sw has to create a directory based on the YEAR of
acquisition of the image and so allocating properly the
image.

23. The
Peak
of
Data
Integration
20
23
● The final steps is to compress (in parallel depending
availability of resources) the 2 images lossless and lossy
● In the server side an email is sent to a specified address
to confirm the successful or not process execution.
● On the server side the system is programmed in listing
waiting for images to be processed.
● It is also available a version with manual activation just
drag and drop data on a html interface.

24. The
Peak
of
Data
Integration
20
23
● Open street map to Satcen DD (from sep 2021 )
available and tested with geoserver and postgis also on
k8s (kubernetes)
● HERE/NAVTEQ to Satcen DD
● Data Conflation

25. The
Peak
of
Data
Integration
20
23
Gazetteer - geonames
Vector – OSM, HERE
Heterogeneous Sources

26. The
Peak
of
Data
Integration
20
23
Conflation –
e.g. Roads
HERE OSM
INTEGRATION

27. The
Peak
of
Data
Integration
20
23
Product

28. The
Peak
of
Data
Integration
20
23
QGIS-QFIELD (compressed image with vectors
embedded)

29. The
Peak
of
Data
Integration
20
23

30. The
Peak
of
Data
Integration
20
23

31. The
Peak
of
Data
Integration
20
23
● Data centric security
Information security can be applied either on the infrastructure
(perimeter-security) or in a data-centric fashion.

32. The
Peak
of
Data
Integration
20
23
Conclusion

33. The
Peak
of
Data
Integration
20
23
Summary
● Standardized formats
● Common data model (ideally seamless data model)
● Heterogeneous sources
● Values added value products (produced with high quality
standards)

34. The
Peak
of
Data
Integration
20
23
Cast a vision of success for the
customer. What can they achieve
with this knowledge?

35. The
Peak
of
Data
Integration
20
23
Call to Action
List 3 simple next steps for the audience to
take.
1. Importance of standardized approach
(data/services)
2. Support production of data as much as
possible following standards
3. Enforce trust and provenance of data

36. ThankYou!
lucio.Colaiacomo@satcen.europa.eu