Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Optimizing Rail Data for Google Earth Mashup

3,822 views

Published on

Presented by Lawrence Chong of Transport Canada
Abstract:
Displaying a huge data set for Google Earth can be a challenge. The data must be properly processed for efficient display. Using FME, the KML output is structured using grouping, networklink, tiling and region for optimization.

Published in: Business
  • Be the first to comment

  • Be the first to like this

Optimizing Rail Data for Google Earth Mashup

  1. 1. Optimizing Rail Data forGoogle Earth Mashup TMLawrence ChongTechnical Data SupportTransport Canada April 24, 2012
  2. 2. Optimizing Rail Data forGoogle Earth Mashup TMOVERVIEW Preparing huge dataset for display in Google Earth can be a challenge. The data must be properly structured for efficient display. Recent release of FME 2012 includes several transformer enhancements specifically for KML translation. This presentation is to demonstrate how to achieve KML optimization using Grouping, Tiling, NetworkLink, Folder, Region and Styling with FME.
  3. 3. Optimizing Rail Data forGoogle Earth Mashup TMBACKGROUND Transport Canada (TC) is responsible for transportation policies and programs. TC regulations, standards and programs work to ensure that air, marine, road and rail transportation are safe, secure, efficient and environmentally responsible. With 48,000 kilometres of tracks and over 25,000 road crossings, Canada has one of the largest rail networks in the world.OBJECTIVE Implement a cost effective, efficient and portable system for viewing Rail Data. Provide Rail Inspectors the visualization tool to access rail information using Google EarthTM and Google Street ViewTM for planning, review and analysis, anywhere, anytime.Google EarthTM and Google Street ViewTM are trademarks of Google Inc.
  4. 4. Optimizing Rail Data forGoogle Earth Mashup TMRail Data Mashup Layers Road Crossings Main Tracks Yards Spurs Crossing Collisions Source: Google EarthTM and Google StreetTM View
  5. 5. Optimizing Rail Data forGoogle Earth Mashup TMBasic FME Workflow Multi-steps parallel processing to create • Grouping data for various LOD • Tiling utilizing thinning and •NetworkLink cluster sampling • Folder MS Access Database technique •Regioning Excel Spreadsheet • Date formatting Output to 5 folders ESRI SHP Files • Label formatting Level 1 KML grouped by TC MapInfo TAB Files Validation • Attribute cleanup (Low LOD) Optimization Symbolization Regions Pass Rail Data KML KML Verification Level 2 Styling Data Integrity Optimization Output Fail Level 3 KML (High LOD) Optimization Terminate Display Error
  6. 6. Optimizing Rail Data forGoogle Earth Mashup TM FME Workbench for Road CrossingsData Integrity Loading KML Optimization Output Style Definition LOD 1 Cascading Folders (Levels 1 & 2) Cluster Sampling LOD 2 Cascading NetworkLink (Level 3) Tiling Level 1 (Low LOD) LOD 3 Level 2 Level 3 (High LOD) Grouping Styling Regioning
  7. 7. Optimizing Rail Data forGoogle Earth Mashup TM FME Workbench for Road Crossings Data Integrity Original: yyyymmdd00000000000 Formatted: yyyy-mm-dd
  8. 8. Optimizing Rail Data forGoogle Earth Mashup TM FME Workbench for Road Crossings KML Optimization – Cluster Sampling & Tiling Loading LOD 1
  9. 9. Optimizing Rail Data forGoogle Earth Mashup TM FME Workbench for Road Crossings KML Optimization – Cluster Sampling & Tiling LOD 2
  10. 10. Optimizing Rail Data forGoogle Earth Mashup TM FME Workbench for Road Crossings KML Optimization – Tiling LOD 3
  11. 11. Optimizing Rail Data forGoogle Earth Mashup TM FME Workbench for Road Crossings KML Optimization – Step 1 Cascading Folder •kml_document=Destination KML document •kml_id=kml_name=Folder Label Cascading NetworlLink •kml_link_href=Output KML file •kml_id=kml_name=NetworkLink label Cascading Folder
  12. 12. Optimizing Rail Data forGoogle Earth Mashup TM Cascading Folder •kml_document=Destination KML document FME Workbench for Road Crossings •kml_parent=Previous Grouping (fanout) •kml_id=kml_name=Current Grouping Cascading NetworlLink KML Optimization – Step 2 •kml_document=Previous Grouping (fanout) •kml_link_href=Output KML file •kml_id=kml_name=NetworkLink label Cascading Folder Cascading NetworkLink
  13. 13. Optimizing Rail Data forGoogle Earth Mashup TM FME Workbench for Road Crossings KML Optimization – Cascading Folder
  14. 14. Optimizing Rail Data forGoogle Earth Mashup TM FME Workbench for Road Crossings KML Optimization – Cascading NetworkLink
  15. 15. Optimizing Rail Data forGoogle Earth Mashup TM FME Workbench for Road Crossings KML Optimization – Step 3 KML Output LOD 1 (High Altitude) Single file-Folder structure LOD 2 Single file-Folder structure Cascading Folder •kml_document=Destination KML document •kml_parent=Previous Grouping (fanout) LOD 3 •kml_name=Placemark Label (Street Level) Multiple files- Cascading NetworlLink NetworkLink •kml_document=Previous Grouping (fanout) structure •kml_name=Placemark label Styling Regioning
  16. 16. Optimizing Rail Data forGoogle Earth Mashup TM FME Workbench for Road Crossings Style Definition
  17. 17. Optimizing Rail Data forGoogle Earth Mashup TM FME Workbench for Crossing Collisions Data Integrity Loading KML Optimization Output Style Definition Cascading NetworkLink Tiling > Grouping Styling Regioning
  18. 18. Optimizing Rail Data forGoogle Earth Mashup TM FME Workbench for Rail Network Pre-processing KML Optimization Output Style Definition NetworkLink Cascading Level 1 (Low LOD) Main Tracks Tiling Level 2 (High LOD) Main Tracks Main Tracks Spurs Yards Level 3 (Street Level) Yards & Spurs Grouping Regioning Styling
  19. 19. Optimizing Rail Data forGoogle Earth Mashup TMOutput
  20. 20. Thank You! Questions? For more information:  Lawrence Chong Lawrence.chong@tc.gc.ca Transport Canada

×