1 / 18

Reference Information Specifications for Europe RISE Test Environment (RTE) Overview

Reference Information Specifications for Europe RISE Test Environment (RTE) Overview. wcudlip@qinetiq.com www.eu-rise.org. Wyn Cudlip (QinetiQ). RTE Objectives. The main objectives of the RTE are to: Demonstrate the creation of harmonised data products “on-the fly” from existing data sets

medwin
Télécharger la présentation

Reference Information Specifications for Europe RISE Test Environment (RTE) Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Reference Information Specifications for EuropeRISE Test Environment (RTE) Overview wcudlip@qinetiq.com www.eu-rise.org Wyn Cudlip (QinetiQ)

  2. RTE Objectives • The main objectives of the RTE are to: • Demonstrate the creation of harmonised data products • “on-the fly” from existing data sets • Allow users to test and evaluate the data products (and hence the specifications) • Achieved through interactive website that: • Provides access to background information • Allows harmonised vector data products to be generated through the use of “schema-translation” software and WFS. • Allows harmonised raster data products to be generated through the use of a WCS. • Allows harmonised data products to be compared to the input datasets • Additional testing requires external additional GIS processing Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  3. USE Case Architecture modelling Use Case Actors: Users LAN, WAN, WWW WFS/WCS harmoniseddata products Use Case Actors: Data Integrators Processing Services LAN, WAN, WWW (WFS/WCS) Use Case Actors: Data Providers Source Data Hydrography Attributes Landcover Clearcuts DEM Hydrography Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  4. Users RISE Test Environment RISEWeb User Interface http web pages MOTIIVE Services: Data Portrayal Directory WMS Client Cascading WMS Access/display Service WMS FTP hDP: harmonised Data Product FTP Other Services: GMES INSPIRE SSE Etc. hDP GML GML Create new hDP based on automatic schema translation as far as possible WFS Transform Services WCS Internet Data Store Ingestion of existing datasets RISE Test Environment: Components View Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  5. Main Software Components • Oracle database 10g • Snowflake Go Publisher for: • Schema Translation • WFS • Minnesota Map Server for WMS and WCS; • and cascading to the WFS for GML portrayal Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  6. Testing • Three Themes • Hydrography (i.e. catchment area polygons; river and lake segments) • Landcover (i.e. RISE defined scheme based on CORINE classification) • Elevation (i.e. uniform grid of Digital Elervation Model (DEM) • Two Test Areas • Vindan (East Sweden) • Enningsdalsalven (Swedish Norwegian Borders) Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  7. RISE Test Areas Enningsdalsalven Vindan Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  8. RISE Hydrography dataset for Vindan Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  9. RISE Landcover dataset (Enningsdalsalven) • RISE Landcover classes: • arableLand • coveredSurfaces • Forest • inlandWaters • Meadows • noOrSparseVegetation • otherLandCoverClasses Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  10. RISE DEM (Enningsdalsalven) Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  11. Landcover Elevation UML Diagram Hydrography(riverbasin and river/lake network) Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  12. Use of Matching Tables • Schema translation definitions created with the use of Matching Tables. • These have to be generated by domain experts. Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  13. QinetiQ data store GoPublisher project RISE web portal User RISE schema Add tables Join tables (according to schema relationships) Map table columns to xml (1) Create WFS Validate WFS GML against schema Shapefiles (Swedish data set) Oracle GoPublisher WFS (2) Add missing attributes to tables GML Shapefiles (Norwegian data set) Original data stored locally MapServer WMS Add layer(s) to WMS Web browser (3) DEM data Add layer(s) to WCS MapServer WCS Create hillshade DEMs DEM (e.g. TIFF) (4) Process flows within RTE Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  14. Schema Mapping process in Go Publisher Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  15. Proposed Data Product testing • Via the website: • Display pre and post harmonised data products • Display data with other layers to demonstrate consistency • Capture data products for additional external testing • External testing: • Hydrography: network analysis • Landcover: generate % landcover for given catchment • DEM: Carry out Thalweg analysis • RISE-User Meeting planned for 26th June. Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  16. Current status • Hardware and software installed. • Website created • http://www.pinkbox.space.qinetiq.com:8080/rise • For username and password please contact wyn cudlip • Test data ingested and example harmonised Data Products produced. • Example hDPs passed to externals for further testing. • Further work: • Improve website • Improve hDP creation process • Carry out further product testing • Document results Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  17. WMS Client snapshot Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

  18. Conclusion • RISE RTE can produce hDP “on the fly”. • In general, “missing information” can be created automatically without any database intervention. • In practice, the degree of automation will depend on how much information is missing from the input existing datasets. • External testing of hDP is being established. • Scalability issues (i.e. to cope with national datasets) needs to be thought about. Presentation to HACPB3, Brussels, 6th June, 2007. V1.0

More Related