3D Terrain Database Generation System

1
3D Terrain Database Generation System
Final Technical Presentation
( Área reservada a imagen )
M. Ancochea / J.A. Redondo / S. Villanueva
M4 (SA), Frascati - ESRIN, November 29th of 2007
2
Contents
01 General Objectives 02 Vision of the system 03
Functional Architecture overview 04 Conflicting
Problems
3
General Objectives

• The integrated system offers
• Identify the data flow required to build the
  terrain databases.
• Determine the high level functions required to
  cover the defined data flow
• Provide a technical solution for each defined
  high level function.

4
Vision of the System
5
Input-output
Vision of the system
Input data

• Satellite Images
• Altimetry data
• Planimetry data
• Generic Textures data

Input-output
6
Functional Architecture Overview
Decomposition of the system
7
Functional Architecture Overview
Dataflow
8
DBGS Workflow Manager (DBGS WM)
Functional Architecture Overview

• Provides an integration front-end to every other
  subsystem.
• Allows the user to invoke each stage/subsystem
• XML configuration contains parameters like
  storage paths, executable paths, new publishers.

9
DBGS Workflow Manager (DBGS WM)
Functional Architecture Overview

• Main functionalities
• Configuration
• Load configuration
• Modify configuration (configured publishers)
• Save configuration
• Launch SDE
• Launch Browser
• Publisher Operations
• Launch Publisher
• Register Publisher
• Un-register Publisher
• Help on-line

10
Source Data Editor (SDE)
Functional Architecture Overview

• The selected COTS for SDE is Erdas Imagine 9.1
  and Imagine Developers Toolkit 9.1 for
  developing two components
• Monoscopic Component
• Catalogation Component

11
Monoscopic Component
Functional Architecture Overview

• Provide a rapid way to extract 3D models from
  monoscopic data. Two techniques could be applied
• Shadow technique
• Photo-interpretation technique

• high shadow tan(sun_elev)

12
Catalogation Component
Functional Architecture Overview

• This component allows the user to loaded data
  into the repository from Erdas using oracle
  capabilities. It is broken down in four modules
• Spatial Catalogation Module
• Category Texture Catalogation Module
• Subcategory Texture Catalogation Module
• Generic Texture Catalogation Module

13
GUI Catalogation Module
Functional Architecture Overview
14
Repository Component
Functional Architecture Overview
15
Browser
Functional Architecture Overview

• Provides functional capabilities to
• Introduce selection parameters for a catalogue
  request
• Show spatial information retrieved according to
  these parameters
• Download selected data
• Generate Publisher input XML

16
Browser
Functional Architecture Overview
GUI of Browser component
17
3D Terrain Publisher
Functional Architecture Overview

• Implements all the functions required to build a
  3D terrain database from downloaded data using
  Browser component
• Read XML file with necessary data to generate 3D
  terrain database.
• View 3D terrain database

18
3D Terrain Publisher
Functional Architecture Overview

• Implements all the functions required to build a
  3D terrain database from downloaded data using
  Browser component
• Read XML file with necessary data to generate 3D
  terrain database.
• Altimetry
• Geos-pecific Texture
• Planimetry (optional)
• 3D models
• Generic trees textures (optional)
• Check referenced data in xml file.
• Build the triangulation of altimetry data.
• Assign geo-specific texture in LODs
• Attach 3D models using interpolation methods to
  localise them
• If exits, attach trees in areas of interest
• View 3D terrain database

19
3D Terrain Publisher (GUI)
Functional Architecture Overview
20
3D Terrain Publisher (Results)
Functional Architecture Overview
21
Conflicting Problems
Functional Architecture Overview

• Capabilities based on Oracle Spatial 10g from
  Erdas Imagine Enterprise Loader Module
• Read access for
• GeoRaste
• Vector data (points, lines and polygons
• Spatial selector tool for GeoRaster
• Minimum Bounding Rectangular (MBR) footprint
  display
• Thumbnail image display
• Image selection
• GeoRaster issues
• Mosaicking operations are very limited, slow and
  require a temporary table
• Deegree/WCS and GeoRaster for raster data
  extraction
• Deegrees GeoRaster compatibility on a very
  initial stage, undocumented
• Many technical problems made necessary to modify
  source code
• HTTP socket timeouts when downloading big images,
  slow extraction from GeoRaster
• These issues made this product combination more
  suitable for viewing than heavy extraction or
  processing
• Decided to avoid WCS and Deegree direct
  connection to Oracle

22

• Miguel Ancochea
• José Antonio Redondo
• Susana Villanueva
• Remote Sensing Department
• Indra Espacio S.A