Rencontre du Grouped’usagers FME 2011<br />Yves St-Julien, <br />Spécialisted’applications, Consortech<br />MitaHajirakr, ...
Mot de bienvenue<br />Présentation des nouveautés FME 2011<br />Pause<br />Témoignageutilisateur<br />Présentation techniq...
Programme (Suite)<br />Dîner-libre/Consultez un expert<br />Présentation des nouveautés FME Server 2011<br />Présentation ...
Notre mission<br />Consortech offre, depuis plus de 20 ans, des solutions logicielles innovatrices en génie civil, génie d...
Présentation de Consortech<br />Près de 22 ans d’expérience en intégration de solutions technologiques<br />Expert en solu...
Notre vision<br />Un leader des technologies 3D appliquées aux processus de décisions<br />Consortech veut demeurer à l’av...
Notre vision<br />Notre vision est appuyée par différentes initiatives telles que : <br />Introduction de nouvelles techno...
Revealing Your New Sidekicks: FME 2011<br />MitHajirakr et Yves St-Julien<br />Safe Software et Solutions Consortech<br />...
FME 2011: Spatial Data at Your Command<br />
FME 2011: Spatial Data at Your Command<br />
FME 2011: Makes you the Superhero!<br />Make you the Super Heroes!<br />
Spatial Data at Your Command<br />FME 2011 gives you more power than ever before<br />Access new formats<br />Experience u...
FME 2011 Power Unleashed<br />
What’s Coming out of the Laboratory in Surrey?<br />Platform<br />
More For Your Utility Belt<br />Database<br />Web<br />3D/BIM<br />Point Clouds<br />GIS<br />CAD<br />Raster<br />
More Formats<br />16<br />Trends and Directionsin Spatial Data Exchange<br />9/2/10<br />
<ul><li> Added new formats:
 LAS, POD, LiDAR XYZ
 OpenStreetMap
 TIBCO OpenSpirit
 Cloud formats
 Added new versions:
 Esri ArcGIS 10
 Autodesk FDO 2011</li></ul>New Formats<br />  CAD       VECTOR     RASTER  DATABASE  BIM/3D          WEB      POINT CLOUD...
New Format Roundup<br />
Format Usage Patterns<br />19<br />9/2/10<br />
Unleashing the Power ofPoint Clouds<br />http://www.fmepedia.com/index.php/Category:Dmitris_Point_Cloud_Lab<br />
Point Clouds<br />
Point Clouds: Thinning<br />
Point Clouds: Splitting<br />
Point Clouds: Clip and Tile<br />
Point Clouds: Combining<br />
Point Clouds: Surface Modeling<br />The workspace also generates TIN (as a PDF 3D file) with DEM as a texture:<br />
Point Clouds: Viewing and Inspection<br />
Point Clouds: Demo 	<br />28<br />9/2/10<br />
New reading and writing capabilities for <br />  Windows Azure<br />  SQL Azure<br />  OGDI<br />  Google Spreadsheets<br ...
FME 2011:More Powerful than Before!<br />
New Transformer Roundup<br />
FME 2011 New Transformer:SherbendGeneralizer<br />
What’s Coming out of the Laboratory in Surrey?<br />Desktop<br />
Workspace Look Refresh<br />
Make Your Own Theme<br />
Tackle Data Villains Easier <br />
Getting Started is Easy<br />
Scripted Parameters<br />
Workspace Inline Data Inspection<br />
Workspace Inline Data Inspection<br />
Workbench Inspection Demo<br />Trends and Directionsin Spatial Data Exchange<br />
Performance Improvements<br />11%+ increase on long run (over 7 seconds) workspaces<br />
SQLCreator and SQLQuerier<br />Execute SQL queries against a database, creating new features or querying existing features...
Improved Stylers<br />Reduce the number of transformers with centralized symbology application using Stylers -<br /><ul><l...
MapInfoStyler
DWGStyler</li></li></ul><li>SchemaMapper <br />Completely revamped in FME 2011!<br />http://evangelism.safe.com/fmeevangel...
New Tester Predicates<br />
XML to the Next Level…<br />XML handling takes a leap forward in efficiency and ease-of-use with:<br />XMLTemplater<br />V...
Verification?<br />How do we know if XML is valid?<br />Writing Complex XML<br />
What’s Coming out of the Laboratory in Surrey?<br />Server<br />
REST API<br />REST API makes it much easier to leverage the services of FME Server.<br />51<br />
FME Server Security<br />Repository Level Security<br />Define Repositories that users can access<br />Define type of acce...
FME Server Scheduler<br />Scheduling capabilities are part of FME Server 2011<br />
Slide 54<br />Scheduler Demo<br />
Future-Proof Your Investment<br />
Future-Proof Your Investment<br />What will tomorrow bring?<br />The evolution of current formats, brand new formats and p...
Pause-café<br />Pause<br />
Témoignageutilisateur:Utilisation de FME dans le cadre d’un projet de vectorisation<br />Judith-Marie Beaudoin<br />Chargé...
Utilisation de FME dans le cadre d’un projet de vectorisation<br />Présenté par Judith-Marie Beaudoin<br />Chargée de proj...
Présentation<br />Mise en contexte du projet I<br />Stratégie de développement<br />Exemple de programme FME réalisé<br />
Mise en contexte du projet I – Présentation globale<br />Projet I : Vectorisation de plan et association de données descri...
Mise en contexte du projet I – Présentation globale<br />Données de base<br />Plans papier<br />Réglementation <br />Donné...
Mise en contexte du projet I – Étapes de réalisation<br />Numérisation des plans papier<br />Géoréférencement des plans nu...
Mise en contexte du projet I – Étapes de réalisation<br />Peuplement de la base de données<br />MicroStation V8 (Bentley) ...
Mise en contexte du projet I – Principes méthodologiques exigés<br />Numérisation vectorielle complète et représentative d...
Mise en contexte du projet I – Principes méthodologiques exigés<br />Exclusion de A<br />Chevauchement<br />A<br />B<br />...
Mise en contexte du projet I – Principes méthodologiques exigés<br />A<br />B<br />Règles topologiques exigées<br />pour l...
Mise en contexte du projet I – Principes méthodologiques exigés<br />Toutes limites communes devront être partagées<br />A...
Stratégie de développement – outils sélectionnés<br />mdl – outils de manipulation<br />Application déjà disponible pour l...
Exemple de programme FME réalisé pour le projet I<br />
Exemple de programme FME réalisé pour le projet I<br />Programme de validation de la structuration des éléments de la sous...
Validation de la structuration de la sous-classe « zone »<br />Fichier de<br />travail.dgn<br />Vérifie la géométrie<br />...
Validation de la structuration de la sous-classe « zone »<br />Précision sur le fichier de sortie error_struc.dgn<br />Pas...
Validation de la structuration de la sous-classe « zone »<br />Quelques transformers utilisés lors de la vérification de l...
Validation de la structuration de la sous-classe « zone »<br />Moins de 8 mm d’ouverture  	             Extraction des se...
Validation de la structuration de la sous-classe « zone »<br />Quelques transformers  utilisés lors de la recherche des ch...
Validation de la structuration de la sous-classe « zone »<br />Éléments mal partagés		      Création d’une ellipse et d’u...
Validation de la structuration de la sous-classe « zone »<br />Quelques transformers utilisés lors de la recherche des tro...
Validation de la structuration de la sous-classe « zone »<br />Quelques transformers  utilisés lors de la vérification du ...
Validation de la structuration de la sous-classe « zone »<br />Erreur : Il n’y a pas de sommet au         Erreur corrigée...
Validation de la structuration de la sous-classe « zone »<br />Résultat de la vectorisation<br />
Questions ?<br />Merci!<br />Judith-Marie Beaudoin<br />judith-marie.beaudoin@groupetrifide.com<br />
Standard de programmation<br />Interface utilisateur<br />Intrants<br />Custom transformer<br />Extrants<br />Published pa...
Présentation technique<br />Yves St-Julien<br />Spécialisted’applications, Solutions Consortech<br />
The Armoury<br />Flow Control<br />Filters, Testers and Mappers<br />Dynamic Workflows<br />Schema Mapping Transformers<br...
Most Popular Gadgets<br />Top Gadgets<br />
Flow ControlFilters, Testers & Mappers<br />Transformers that control the flow of data in your workspace<br />Testers<br /...
Dynamic Workflows<br />Dynamic SchemaIntroduced in FME 2010 		Improved in FME 2011<br />SchemaMapper<br />Dynamic Schemas<...
Schema Mapping<br />What is a Schema?<br />Feature Types (Tables, Feature Classes, Layers, Collections, Levels…)<br />Attr...
Schema Mapping<br />What is Schema Mapping?from “what we have” to “what we want”<br />Renaming feature types (WATERLINES ...
Schema Mapping<br />Schema mapping in FME Workbench:<br />Feature Type renaming<br />AttributeCopier<br />AttributeCreator...
The Armoury<br />
SchemaMapper<br />SchemaMapper:<br />Combines: Feature Type renaming, AttributeCopier, AttributeCreator, AttributeValueMap...
 Feature Type Map
 Attribute Map
 New Attribute</li></ul>Example<br />Problem:<br />The workspace is still very repppppetitive<br />
Traditional Workspaces(Static Schema)<br />Workspaces are tightly bound to the source and destination schemas<br />This wo...
Dynamic Schemas<br />Dynamic Schema breaks the dependence on the reader and writer schemas<br /><ul><li>Used when:
Simple transformations applied to all feature types
Reader schema is not predictable or may vary
Reader or writer format might vary
Long term maintenance of the workspace is required</li></li></ul><li>Example – Dynamic Workflow<br />Example Clipper works...
Dynamic Workflow<br />What can be made dynamic?<br />Schema: Reader Feature Types<br />Read any set of feature types from ...
Summary<br />Dynamic workspaces give maximum flexibility for minimum effort<br />Dynamic Schema can handle source data wit...
Dîner-libre:Consultez un expert<br />Dîner<br />
New Superpowers for FME Server<br />MitaHajirakr, <br />FME Desktop Support Manager, Safe Software<br />MitaHajirakr , FME...
Setup<br />See the –readme.txt file for set-up details and the “story”<br />
Session Overview<br />Why FME Server?<br />Scenario Example<br />
The Battle for Resources…CADwoman vs. GISguardian<br />
What Are They Battling Over…<br />CADwoman wants to run:<br />DWG Data validation & Oracle Loader workspace<br /><ul><li>G...
Water pipe network validation workspace
Database to DWG data conversion workspace</li></li></ul><li>Safe Products…<br />
Why FME Server?<br />FME Server is a scalable platform that offers flexible spatial data distribution and loading services...
FME Server uses thesame FME Engine thatunderlies the FME Desktop application</li></li></ul><li>What is FME Server?<br /><u...
FME Server software makes it possible for organizations to deliver up-to-date spatial data exactly how it’s needed. </li><...
Why FME Server?<br />How FME Server can meet your needs:<br />Data Distribution <br />Data Download Service<br />Live Data...
FME Server in Action!<br /><ul><li>Live Demo: Arkansas GeoStor</li></li></ul><li>How Can We Stream Data?<br />Streaming Se...
FME Workbench: Author Workflows for FME Server<br />Use the proven power of FME Workbench to author workflows for FME Serv...
FME Server Works with FME Desktop <br />FME Desktop<br />Author and run spatial transformation tasks<br />FME Server<br />...
Using FME Server<br />Typical steps for using FME Server are:<br />Author an FME workspace (Spatial ETL task) <br />Share ...
Author a Transformation Task<br />FME Workbench - graphical authoring environment<br />Step 1 Extract: Select and drag a s...
Share Transformation Tasks<br />Publish workspace to FME Server<br />Store the workspace in a central repository<br />Make...
Run the Transformation Task<br />Run the Data Transformation Task from a web interface<br /><ul><li>Default FME Server web...
Custom web forms
WFS client applications</li></ul>118<br />
Maintain the Transformation Task<br />Maintain the Spatial ETL task by editing the FME Workspace<br />Download the workspa...
Scenario<br /><ul><li>Add new water lines to water distribution network; validate the network
CADwoman: CAD Contractor tasks
Validate CAD data
Upload clean CAD data
GISguardian: GIS Analyst tasks
Validate network
Maintain workspaces</li></li></ul><li>Summary<br />FME Workspaces for different tasks:<br />CAD validation & data loading<...
Introducing CADwomanCAD to GIS / GIS to CAD<br />Mita H<br />MitaHajirakr, <br />FME Desktop Support Manager, Safe Softwar...
CAD & GIS: Differences<br /><ul><li>What’s important to CAD users?
Visual clarity / Editing tools
Symbology
Labels & white space
Dimensions
Which CAD Formats?
AutoCAD DWG
AutoCAD Map 3D
AutoCAD Civil 3D
MicroStation
PLS-CADD (XML)
etc…</li></li></ul><li>CAD & GIS: Differences<br /><ul><li>What drives the GIS?
Data structure / model
Consistency
Attribution / domains
Location
Connectivity
Analysis</li></ul>Example: <br />GIS as-built  CAD Design  GIS Proposed<br />
GIS to CAD<br />GIS  CAD Key Points:<br />Create AutoCAD blocks or MicroStation cells<br />Preserve attributes as object ...
CAD to GIS<br />CAD  GIS<br />Preserve attribution<br />Data improvement<br />Create connectivity (snapping)<br />Recover...
Storm: The Power of Data in the Cloud<br />MitaHajirakr<br />FME Desktop Support Manager, Safe Software<br />
The Power of the Cloud<br />Storm uses the power of the cloud to combat data villains <br />
Supported Cloud Data Storage<br />Engine<br />
Advantages of Data in the Cloud<br />Data available to you and others,regardless of location<br />You control who has acce...
Advantages of Data in the Cloud cont…<br />Scalability<br />The cloud service looks after all scaling issues<br />Cost sav...
Disadvantages of Data in the Cloud<br />Data available to you and others,regardless of location<br />Make sure you control...
Disadvantages of Data in the Cloud cont…<br />Cost savings<br />Communication costs can be significant<br />Best strategy ...
Upcoming SlideShare
Loading in …5
×

Présentation de la rencontre du Groupe d'usagers FME_mars 2011

1,419
-1

Published on

Revoyez les sujets abordés lors de la rencontre du Groupe d'usagers FME tenue par Consortech en mars dernier.

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,419
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  •  
  •  
  • D&amp;D: Show:Dale’s Sydney Harbor Bridge KML tour,PDF with links: http://www.fmepedia.com/index.php/PDF_Mapping,Before and after of Tom’s XML workspaces
  • D&amp;D: Show:Dale’s Sydney Harbor Bridge KML tour,PDF with links: http://www.fmepedia.com/index.php/PDF_Mapping,Before and after of Tom’s XML workspaces
  • D&amp;D: Show:Dale’s Sydney Harbor Bridge KML tour,PDF with links: http://www.fmepedia.com/index.php/PDF_Mapping,Before and after of Tom’s XML workspaces
  • D&amp;D: Show:Dale’s Sydney Harbor Bridge KML tour,PDF with links: http://www.fmepedia.com/index.php/PDF_Mapping,Before and after of Tom’s XML workspaces
  • D&amp;D: Show:Dale’s Sydney Harbor Bridge KML tour,PDF with links: http://www.fmepedia.com/index.php/PDF_Mapping,Before and after of Tom’s XML workspaces
  •  
  • JC – Can we make this image even larger?
  • At this point create a workspace with:Static SchemaDynamic SchemaAdd CityExtents.gmlAdd Clipper
  •  
  • Many organizations are using both GIS and CAD systems. It’s important that we are able to move data smoothly between the two systems. Although there’s a great deal of overlap in functionality each has their strengths, in general: CAD users are focused on visual clarity and editing toolsImage shows a electric layout with detailed symbology and annotation, but no connectivity
  • GIS users are focused on data models &amp; data structures Image shows topological connectivity – How to get from a hotel to a pub in CambridgeA typical example is exporting GIS as-built features to a CAD design tool. Designing a new layout and then importing the new design back into the GIS.
  • Symbolization approaches can be quite different be CAD &amp; GIS. Key point: FME helps symbolization with StylersIn the workspace open DWGStyler_3 – block creation
  • This is what we’re going to demo.The requirements are the same as GIS to CAD – to preserve the meaning of the data in the different format. Issues with CAD is that the environment can be less stringent so entities may not be on the correct layer or have different attributes that represent the same information. Or different attributes values that mean the same thing: Phase = ABC and Phase = 123DEMOFor this example, we have a Microstation design file that contains road lines and lables for those roads. [open roads.dgn in Viewer]To successfully load the data into a GIS, we must attach the road label text to the road lines as attributes.The the problem is that labels may be close to several roads, so we have to use some logic to match the labels to the correct roads, and send any roads that don’t match a lable to a separate output for further investigation.
  • Show how easy it is to go to both Azure and SQL Azure. (Azure is not spatial)Also show the inspector here.
  • Show how easy it is to go to both Azure and SQL Azure. (Azure is not spatial)Also show the inspector here.
  • Show KML updates. With URL. Also show the inspector here.
  • Initial Data link is a Viewer Viewspace. You’ll have to re-save the viewspace with you DB connection details.
  • This combines Translate and Reproject. Use Example #3 Reproject since it also includes a translate.
  • Example 6-Mosaic and 6a-Mosaic 6a- Mosaic includes a reprojector – reproject after the mosaic to ensure clean overlaps
  • Point out that tile &amp; clip are more or less the same. Make a comment that you can clip with irregular polygons.Reprojector – ensure all output features are in the same coordinate system
  • Idea here is to explain that when FME 2011 ships you will be able to specify the “tags” that are the feature type and also the name of the “Feature Type”.Currently this is done by a custom transformer. You could show it to just drive home that they will not need to know this or not.
  • XML document CONTAINS a substation feature which CONTAINS several Feeder objects
  • Copy the XML template from an exiting sample of the XML replace the attribute values with XQuery statements repeat for other XML tags (i.e. substation)
  • Copy the XML template from an exiting sample of the XML replace the attribute values with XQuery statements repeat for other XML tags (i.e. substation)
  • Présentation de la rencontre du Groupe d'usagers FME_mars 2011

    1. 1. Rencontre du Grouped’usagers FME 2011<br />Yves St-Julien, <br />Spécialisted’applications, Consortech<br />MitaHajirakr, <br />FME Desktop Support Manager, Safe Software<br />Place your logo here<br />
    2. 2. Mot de bienvenue<br />Présentation des nouveautés FME 2011<br />Pause<br />Témoignageutilisateur<br />Présentation technique<br />Programme<br />
    3. 3. Programme (Suite)<br />Dîner-libre/Consultez un expert<br />Présentation des nouveautés FME Server 2011<br />Présentation des problèmesd’interopérabilité<br />Période de questions et conclusion<br />
    4. 4. Notre mission<br />Consortech offre, depuis plus de 20 ans, des solutions logicielles innovatrices en génie civil, génie du bâtiment et géomatique visant à assurer le succès des projets de ses clients privés et gouvernementaux en optimisant leur investissements et en favorisant l’autonomie de leurs ressources.<br />
    5. 5. Présentation de Consortech<br />Près de 22 ans d’expérience en intégration de solutions technologiques<br />Expert en solutions de :<br />Géomatique<br />Génie civil<br /> Génie du bâtiment<br /> BIM (Building Information Modeling)<br /> Visualisation et simulation 3D<br />
    6. 6. Notre vision<br />Un leader des technologies 3D appliquées aux processus de décisions<br />Consortech veut demeurer à l’avant-garde dans les solutions technologiques offertes en génie et en géospatial afin d’être perçue comme une instigatrice d’innovation auprès des organismes gouvernementaux et des firmes privées via.<br />
    7. 7. Notre vision<br />Notre vision est appuyée par différentes initiatives telles que : <br />Introduction de nouvelles technologies (Subassembly Studio, LandXplorer, Transoft Solutions, FME, etc.)<br />Participation à des projets pilotes (ponts, digues et barrages, etc.)<br />Développements de produits (SOLO)<br />Organisation d’événement spéciaux (Événement 3D de février dernier)<br />Organisation de rencontres d’échanges (Municipal, Transport, Ouvrages d’art)<br />
    8. 8. Revealing Your New Sidekicks: FME 2011<br />MitHajirakr et Yves St-Julien<br />Safe Software et Solutions Consortech<br />Yves St-Julien, <br />Spécialisted’applications, Consortech<br />MitaHajirakr, <br />FME Desktop Support Manager, Safe Software<br />
    9. 9. FME 2011: Spatial Data at Your Command<br />
    10. 10. FME 2011: Spatial Data at Your Command<br />
    11. 11. FME 2011: Makes you the Superhero!<br />Make you the Super Heroes!<br />
    12. 12. Spatial Data at Your Command<br />FME 2011 gives you more power than ever before<br />Access new formats<br />Experience usability enhancements<br />Perform FME tasks even faster<br />
    13. 13. FME 2011 Power Unleashed<br />
    14. 14. What’s Coming out of the Laboratory in Surrey?<br />Platform<br />
    15. 15. More For Your Utility Belt<br />Database<br />Web<br />3D/BIM<br />Point Clouds<br />GIS<br />CAD<br />Raster<br />
    16. 16. More Formats<br />16<br />Trends and Directionsin Spatial Data Exchange<br />9/2/10<br />
    17. 17. <ul><li> Added new formats:
    18. 18. LAS, POD, LiDAR XYZ
    19. 19. OpenStreetMap
    20. 20. TIBCO OpenSpirit
    21. 21. Cloud formats
    22. 22. Added new versions:
    23. 23. Esri ArcGIS 10
    24. 24. Autodesk FDO 2011</li></ul>New Formats<br /> CAD VECTOR RASTER DATABASE BIM/3D WEB POINT CLOUD<br />
    25. 25. New Format Roundup<br />
    26. 26. Format Usage Patterns<br />19<br />9/2/10<br />
    27. 27. Unleashing the Power ofPoint Clouds<br />http://www.fmepedia.com/index.php/Category:Dmitris_Point_Cloud_Lab<br />
    28. 28. Point Clouds<br />
    29. 29. Point Clouds: Thinning<br />
    30. 30. Point Clouds: Splitting<br />
    31. 31. Point Clouds: Clip and Tile<br />
    32. 32. Point Clouds: Combining<br />
    33. 33. Point Clouds: Surface Modeling<br />The workspace also generates TIN (as a PDF 3D file) with DEM as a texture:<br />
    34. 34. Point Clouds: Viewing and Inspection<br />
    35. 35. Point Clouds: Demo <br />28<br />9/2/10<br />
    36. 36. New reading and writing capabilities for <br /> Windows Azure<br /> SQL Azure<br /> OGDI<br /> Google Spreadsheets<br />Spatial Data in the Cloud<br />
    37. 37. FME 2011:More Powerful than Before!<br />
    38. 38. New Transformer Roundup<br />
    39. 39. FME 2011 New Transformer:SherbendGeneralizer<br />
    40. 40.
    41. 41. What’s Coming out of the Laboratory in Surrey?<br />Desktop<br />
    42. 42. Workspace Look Refresh<br />
    43. 43. Make Your Own Theme<br />
    44. 44. Tackle Data Villains Easier <br />
    45. 45. Getting Started is Easy<br />
    46. 46. Scripted Parameters<br />
    47. 47. Workspace Inline Data Inspection<br />
    48. 48. Workspace Inline Data Inspection<br />
    49. 49. Workbench Inspection Demo<br />Trends and Directionsin Spatial Data Exchange<br />
    50. 50. Performance Improvements<br />11%+ increase on long run (over 7 seconds) workspaces<br />
    51. 51. SQLCreator and SQLQuerier<br />Execute SQL queries against a database, creating new features or querying existing features.<br />
    52. 52. Improved Stylers<br />Reduce the number of transformers with centralized symbology application using Stylers -<br /><ul><li>DGNStyler
    53. 53. MapInfoStyler
    54. 54. DWGStyler</li></li></ul><li>SchemaMapper <br />Completely revamped in FME 2011!<br />http://evangelism.safe.com/fmeevangelist71/<br />“Complex data mapping - spatial and nonspatial - doesn’t get any better than this.” <br />- Mike Oberdries, we-do-IT(NZ) Ltd.<br />
    55. 55. New Tester Predicates<br />
    56. 56. XML to the Next Level…<br />XML handling takes a leap forward in efficiency and ease-of-use with:<br />XMLTemplater<br />Validation<br />Styling<br />Metadata <br />Cataloging<br />
    57. 57. Verification?<br />How do we know if XML is valid?<br />Writing Complex XML<br />
    58. 58. What’s Coming out of the Laboratory in Surrey?<br />Server<br />
    59. 59. REST API<br />REST API makes it much easier to leverage the services of FME Server.<br />51<br />
    60. 60. FME Server Security<br />Repository Level Security<br />Define Repositories that users can access<br />Define type of access that they have<br />
    61. 61. FME Server Scheduler<br />Scheduling capabilities are part of FME Server 2011<br />
    62. 62. Slide 54<br />Scheduler Demo<br />
    63. 63. Future-Proof Your Investment<br />
    64. 64. Future-Proof Your Investment<br />What will tomorrow bring?<br />The evolution of current formats, brand new formats and platforms, and entirely new data types<br />Point cloud data is here<br />Count on FME to keep up with industry and format changes<br />With FME, you’ll beready<br />
    65. 65. Pause-café<br />Pause<br />
    66. 66. Témoignageutilisateur:Utilisation de FME dans le cadre d’un projet de vectorisation<br />Judith-Marie Beaudoin<br />Chargée de projetrecherche et développement, GroupeTrifide<br />
    67. 67. Utilisation de FME dans le cadre d’un projet de vectorisation<br />Présenté par Judith-Marie Beaudoin<br />Chargée de projet Recherche et Développement<br />Groupe Trifide<br />
    68. 68. Présentation<br />Mise en contexte du projet I<br />Stratégie de développement<br />Exemple de programme FME réalisé<br />
    69. 69. Mise en contexte du projet I – Présentation globale<br />Projet I : Vectorisation de plan et association de données descriptives<br />Format MID/MIF<br />MIF:<br />VERSION 300<br />DELIMITER ","<br /> CoordSys Earth Projection 3, 33, "m", 3, 46.5, 44, 49, 700000, 6600000 <br />COLUMNS 3<br /> ID char(10)<br /> NATTRAC char(40)<br /> INSEE char(5)<br />DATA<br />LINE 898573.99 6502546.77 898594.64 6502590.83<br />LINE 897119.97 6504607.15 897063.87 6504637.44<br />LINE 898984.76 6501855.8 899031.22 6501877.82<br />MID:<br />HL392,,38124<br />HL382,,38124<br />HL407,,38124<br />HL401,,38124<br />
    70. 70. Mise en contexte du projet I – Présentation globale<br />Données de base<br />Plans papier<br />Réglementation <br />Données cadastrales vectorielles (MapInfo)<br />Livrables<br />MID/MIF<br />PDF<br />
    71. 71. Mise en contexte du projet I – Étapes de réalisation<br />Numérisation des plans papier<br />Géoréférencement des plans numériques<br />MicroStation V8i Descartes (Bentley)<br />Transformation affine sur la couche vectorielle cadastrale<br />Vectorisation des plans numériques<br />MicroStation V8 (Bentley)<br />Vectorisation manuel à l’aide de la couche vectorielle cadastrale<br />
    72. 72. Mise en contexte du projet I – Étapes de réalisation<br />Peuplement de la base de données<br />MicroStation V8 (Bentley) associé à une base de données Access <br />Peuplement manuel  les attributs variables<br />Peuplement automatique  les attributs constants<br />Livraison des données<br />Étapes de réalisation incluant les programmes FME :<br />Numérisation<br />Validation de<br /> la structure<br />Géoréférencement<br />Vectorisation<br />Cadastre.dgn<br />Validation de<br /> la BD<br />Création des<br /> MID/MIF<br />Peuplement BD<br />Livraison<br />
    73. 73. Mise en contexte du projet I – Principes méthodologiques exigés<br />Numérisation vectorielle complète et représentative du plan original<br />Respect de la géométrie des éléments associés à chaque classe d’objet<br />Classes ponctuelles<br />Classes textuelles<br />Classes linéaires<br />Classes surfaciques<br />Classes sémantiques<br />Un élément linéaire peut être une ligne ou une polyligne ouverte<br />Un élément surfacique doit être une polyligne fermée, sans boucle<br />
    74. 74. Mise en contexte du projet I – Principes méthodologiques exigés<br />Exclusion de A<br />Chevauchement<br />A<br />B<br />Trou<br />A<br />La notion de région permet d’éviter le chevauchement.<br />Règles topologiques exigée pour les éléments de la sous-classe « zone » (classe surfacique)<br />Pas de chevauchement<br />Recouvrement total du territoire<br />
    75. 75. Mise en contexte du projet I – Principes méthodologiques exigés<br />A<br />B<br />Règles topologiques exigées<br />pour les éléments de la sous-classe « zone » (classe surfacique)<br />Partage entre les limites de cette classe <br />Partage entre les limites de cette classe et les données cadastrales<br />Les étoiles oranges représentent les sommets partagés entre la zone A et B. <br />Le client désirait l’indépendance entre les surfaces, malgré le partage. C’est pourquoi, les segments entre les étoiles oranges ont été vectorisés deux fois: une fois pour la zone A et une fois pour la zone B.<br />
    76. 76. Mise en contexte du projet I – Principes méthodologiques exigés<br />Toutes limites communes devront être partagées<br />Attributs et format d’attribut prédéterminés pour les données descriptives pour chaque classe d’objet<br />Livraison des données en centimètre<br /><ul><li>Conclusion : beaucoup de géométrie et de relations topologiques à valider (particulièrement pour la sous-classe surfacique « zone »)</li></li></ul><li>Stratégie de développement – analyse des besoins<br />Besoin d’outils pour faciliter la numérisation<br />partage des éléments<br />Besoin d’outils pour remplir la base de données<br />Besoin d’outils de validation<br />Analyse de la géométrie des éléments vectorisés<br />Géométrie versus classe<br />Analyses topologiques entres les éléments vectorisés<br />Relation de chevauchement, d’égalité, de proximité, etc.<br />Analyse du contenu d’une BD<br />Reconnaissance des attributs et de leur format<br />Besoin de convertir les format .dgn et .mdb en format MID/MIF<br />
    77. 77. Stratégie de développement – outils sélectionnés<br />mdl – outils de manipulation<br />Application déjà disponible pour la production<br />Partage des éléments<br />Remplir les attributs de la BD<br />FME – outils de validation<br />Temps de programmations réduits vs mdl<br />Librairie de fonctions d’analyse spatiale existante<br />Réponds aux besoins suivants:<br />Toutes les analyses spatiales <br />Permet de lire une BD et son contenu<br />Permet d’analyser la géométrie des éléments<br />Permet la création du format MID/MIF<br />Temps de formation nul pour les techniciens – standard de programmation en place et connu<br />Volume de données raisonnable<br />
    78. 78. Exemple de programme FME réalisé pour le projet I<br />
    79. 79. Exemple de programme FME réalisé pour le projet I<br />Programme de validation de la structuration des éléments de la sous-classe « zone » <br />Beaucoup d’exigence du client quant aux relations topologiques au sein des éléments de cette sous-classe<br />Principale sous-classe présente sur les plans à vectoriser<br />Présente sur toutes les cartes<br />Couvre l’ensemble du territoire<br />Présentation de l’algorithme général<br />Présentation et précision sur le fichier de sortie du worbench<br />Présentation des résultats des algorithmes particuliers composants le workbench<br />
    80. 80. Validation de la structuration de la sous-classe « zone »<br />Fichier de<br />travail.dgn<br />Vérifie la géométrie<br /> de tous les éléments<br />incorrecte<br />Error_struc.dgn<br />correcte<br />Isole les éléments de<br /> la sous-classe ZONE<br />Recherche les<br />chevauchements<br />chevauchement<br />ZONE<br />Recherche les<br />trous<br />trous<br />Cadastre.dgn<br />Vérifie le partage<br />Avec la limite<br />cadastrale<br />Problème de partage<br />Algorithme général:<br />
    81. 81. Validation de la structuration de la sous-classe « zone »<br />Précision sur le fichier de sortie error_struc.dgn<br />Pas de correction automatique, modification du fichier de travail (.dgn) d’entrée, car besoin du technicien pour l’interprétation de l’erreur<br />Circonscrire l’erreur au maximum<br />Un niveau et une couleur pour chaque type d’erreur<br />Extraire seulement les <br /> sommets ou les segments <br /> en erreur et non pas l’élément <br /> dans son ensemble<br />Présence d’un texte explicatif <br /> pour chaque erreur<br />Nombre d’erreur raisonnable…<br />
    82. 82. Validation de la structuration de la sous-classe « zone »<br />Quelques transformers utilisés lors de la vérification de la géométrie de tous les éléments :<br />AttributeFilter (séparation des classes) <br />GeometryFilter (séparation des géométries)<br />PolygonBuilder (polylignes fermées deviennent des polygones)<br />LineJoiner (création de polylignes ouvertes)<br />SpatialRelator (analyses topologiques)<br />Recherche des éléments en double et les polygones ouvert<br />
    83. 83. Validation de la structuration de la sous-classe « zone »<br />Moins de 8 mm d’ouverture  Extraction des segments qui ne se<br />Difficile à trouver par une analyse touchent pas (circonscrire l’erreur)<br />visuel<br />
    84. 84. Validation de la structuration de la sous-classe « zone »<br />Quelques transformers utilisés lors de la recherche des chevauchements entre les zones :<br />AreaBuilder (création de régions)<br />Chopper (extraction des sommets)<br />SpatialRelator (analyses topologiques)<br />
    85. 85. Validation de la structuration de la sous-classe « zone »<br />Éléments mal partagés  Création d’une ellipse et d’un = chevauchement texte d’erreur sur les sommets qui chevauchent une surface<br />
    86. 86. Validation de la structuration de la sous-classe « zone »<br />Quelques transformers utilisés lors de la recherche des trous entre les zones :<br />Chopper (extraction des sommets)<br />SpatialRelator (analyses topologiques)<br />PointOnAreaOverlay (analyses topologiques)<br />Pas le même nombre de sommets  création d’une ellipse et d’un texte sur le = « trou » sommet solitaire<br />
    87. 87. Validation de la structuration de la sous-classe « zone »<br />Quelques transformers utilisés lors de la vérification du partage avec la limite cadastrale :<br />GeometryCoercer (modification de la géométrie)<br />Chopper (extraction des sommets)<br />NeighborFinder (analyses topologiques)<br />PointOnPointOverlay (analyses topologiques)<br />
    88. 88. Validation de la structuration de la sous-classe « zone »<br />Erreur : Il n’y a pas de sommet au  Erreur corrigée: il y a un sommet au<br />croisement avec la limite cadastrale croisement avec la limite cadastrale (rouge) (rouge)<br />
    89. 89. Validation de la structuration de la sous-classe « zone »<br />Résultat de la vectorisation<br />
    90. 90. Questions ?<br />Merci!<br />Judith-Marie Beaudoin<br />judith-marie.beaudoin@groupetrifide.com<br />
    91. 91. Standard de programmation<br />Interface utilisateur<br />Intrants<br />Custom transformer<br />Extrants<br />Published parameters<br />Utilisation des custom transformer permet de structurer le programme selon l’algorithme<br />Utilisation du viewer seulement pour souligné un problème à l’utilisateur lors du traitement<br />Présence de commentaire comme dans n’importe quel programme<br />
    92. 92. Présentation technique<br />Yves St-Julien<br />Spécialisted’applications, Solutions Consortech<br />
    93. 93. The Armoury<br />Flow Control<br />Filters, Testers and Mappers<br />Dynamic Workflows<br />Schema Mapping Transformers<br />Dynamic Schemas<br />
    94. 94. Most Popular Gadgets<br />Top Gadgets<br />
    95. 95. Flow ControlFilters, Testers & Mappers<br />Transformers that control the flow of data in your workspace<br />Testers<br />Tester<br />StringSearcher<br />Filters<br />TestFilter<br />AttributeFilter<br />AtributeRangeFilter<br />Mappers<br />AttributeValueMapper<br />AttributeRangeMapper<br />SchemaMapper<br />Example workspace<br />
    96. 96. Dynamic Workflows<br />Dynamic SchemaIntroduced in FME 2010 Improved in FME 2011<br />SchemaMapper<br />Dynamic Schemas<br />Review traditional workspaces<br />Examples of Dynamic Workflows<br /> Dynamic workspaces are a way of providing maximum translation flexibility and minimizing the longer term maintenance of workspaces<br />
    97. 97. Schema Mapping<br />What is a Schema?<br />Feature Types (Tables, Feature Classes, Layers, Collections, Levels…)<br />Attributes (and their types: char, int, float, number, blob)<br />Domains, Subtypes, Enumerated Lists<br />Geometry(point, text, symbol, line, area, multi-part, …)<br />Reader Schema: what we have<br />Writer Schema: what we want<br />
    98. 98. Schema Mapping<br />What is Schema Mapping?from “what we have” to “what we want”<br />Renaming feature types (WATERLINES  D-WATER-DW~~)<br />Renaming attributes (PR_ZONE  Zone)<br />Creating attributes (FCode = AQ113)<br />Domain mapping<br />Schema map is usually defined in a crosswalk table<br />
    99. 99. Schema Mapping<br />Schema mapping in FME Workbench:<br />Feature Type renaming<br />AttributeCopier<br />AttributeCreator<br />AttributeValueMapper<br />What’s the problem? Very repppppetitive Harder to maintain<br />What we need is a “Swiss Army” gadget for schema mapping…<br />Example workspace<br />
    100. 100. The Armoury<br />
    101. 101. SchemaMapper<br />SchemaMapper:<br />Combines: Feature Type renaming, AttributeCopier, AttributeCreator, AttributeValueMapper and others…<br />SchemaMapper actions:<br /><ul><li> Filter
    102. 102. Feature Type Map
    103. 103. Attribute Map
    104. 104. New Attribute</li></ul>Example<br />Problem:<br />The workspace is still very repppppetitive<br />
    105. 105. Traditional Workspaces(Static Schema)<br />Workspaces are tightly bound to the source and destination schemas<br />This works well when:<br />Each feature type requires unique transformation<br />Feature types interact (i.e. merged data, spatial overlap)<br />Not so well for:<br />A relatively simple transformation that is applied to all feature types<br />Workspace maintenance – it can be tedious<br />These are the pros & cons of workspace example<br />Static Schema Example<br />
    106. 106. Dynamic Schemas<br />Dynamic Schema breaks the dependence on the reader and writer schemas<br /><ul><li>Used when:
    107. 107. Simple transformations applied to all feature types
    108. 108. Reader schema is not predictable or may vary
    109. 109. Reader or writer format might vary
    110. 110. Long term maintenance of the workspace is required</li></li></ul><li>Example – Dynamic Workflow<br />Example Clipper workspace<br />
    111. 111. Dynamic Workflow<br />What can be made dynamic?<br />Schema: Reader Feature Types<br />Read any set of feature types from a dataset<br />Schema: Writer Feature Types<br />Mirror the source feature types on the destination<br />Schema: Attributes<br />Read any set of attributes on source feature types and mirror them on the writer feature types<br />Format: Generic Reader and Generic Writer<br />Select the reader or writer format at run time<br />Review of Workspace<br />
    112. 112. Summary<br />Dynamic workspaces give maximum flexibility for minimum effort<br />Dynamic Schema can handle source data with any schema<br />Dynamic Writer can be used to minimize the workspace complexity<br />The Generic reader or writer can process data in nearly any format<br />
    113. 113. Dîner-libre:Consultez un expert<br />Dîner<br />
    114. 114. New Superpowers for FME Server<br />MitaHajirakr, <br />FME Desktop Support Manager, Safe Software<br />MitaHajirakr , FME desktop Support Manager, Safe Software<br />Yves St-Julien, Spécialisted’applications, Solutions Consortech<br />
    115. 115. Setup<br />See the –readme.txt file for set-up details and the “story”<br />
    116. 116. Session Overview<br />Why FME Server?<br />Scenario Example<br />
    117. 117. The Battle for Resources…CADwoman vs. GISguardian<br />
    118. 118. What Are They Battling Over…<br />CADwoman wants to run:<br />DWG Data validation & Oracle Loader workspace<br /><ul><li>GISguardian wants to run:
    119. 119. Water pipe network validation workspace
    120. 120. Database to DWG data conversion workspace</li></li></ul><li>Safe Products…<br />
    121. 121. Why FME Server?<br />FME Server is a scalable platform that offers flexible spatial data distribution and loading services<br /><ul><li>FME Server allows you to run FME Workspaces using a variety of different services
    122. 122. FME Server uses thesame FME Engine thatunderlies the FME Desktop application</li></li></ul><li>What is FME Server?<br /><ul><li>Efficiently exchange data on demand across the widest range of formats.
    123. 123. FME Server software makes it possible for organizations to deliver up-to-date spatial data exactly how it’s needed. </li></li></ul><li>Why FME Server?<br />You need to distribute data and meta data access to your team, your manager, contractors, public etc. <br />More and more data is available live or updated constantly. You need to make this available to decision makers.<br />You need to load data from outside but you need to ensure it’s valid and matches your format and data model<br />You already process a lot of data through FME, perhaps nightly. You want to push this to a server.<br />109<br />
    124. 124. Why FME Server?<br />How FME Server can meet your needs:<br />Data Distribution <br />Data Download Service<br />Live Data Streams <br />Data Streaming Service<br />Upload and Validation<br />Data Upload Service<br />Centralize Data Transformation <br />Job Submitter Service<br />
    125. 125. FME Server in Action!<br /><ul><li>Live Demo: Arkansas GeoStor</li></li></ul><li>How Can We Stream Data?<br />Streaming Service Data to PDF<br />Anyone can view a PDF file!<br />See www.fmepedia.com example<br />
    126. 126. FME Workbench: Author Workflows for FME Server<br />Use the proven power of FME Workbench to author workflows for FME Server<br />
    127. 127. FME Server Works with FME Desktop <br />FME Desktop<br />Author and run spatial transformation tasks<br />FME Server<br />Run and share <br />spatial transformation capabilities<br />114<br />
    128. 128. Using FME Server<br />Typical steps for using FME Server are:<br />Author an FME workspace (Spatial ETL task) <br />Share the Spatial ETL task in an FME Server repository<br />Run the Spatial ETL task from a web interface or equivalent<br />Maintain the Spatial ETL task by editing in FME Workbench<br />115<br />
    129. 129. Author a Transformation Task<br />FME Workbench - graphical authoring environment<br />Step 1 Extract: Select and drag a source dataset on to the workspace<br />Step 2 Transform: Adjust the way the data flows from its source to the destination <br />Step 3 Load: Load the transformed data into the destination<br />116<br />
    130. 130. Share Transformation Tasks<br />Publish workspace to FME Server<br />Store the workspace in a central repository<br />Make your FME workspaces available to others –over the web<br />Register the workspace with one or more services(Data Streaming, Data Download, etc.)<br />117<br />
    131. 131. Run the Transformation Task<br />Run the Data Transformation Task from a web interface<br /><ul><li>Default FME Server web pages
    132. 132. Custom web forms
    133. 133. WFS client applications</li></ul>118<br />
    134. 134. Maintain the Transformation Task<br />Maintain the Spatial ETL task by editing the FME Workspace<br />Download the workspace from the FME Server repository<br />Modify the workspace<br />Publish the workspace back to the repository<br />Step 3<br />Step 2<br />Step 1<br />119<br />
    135. 135. Scenario<br /><ul><li>Add new water lines to water distribution network; validate the network
    136. 136. CADwoman: CAD Contractor tasks
    137. 137. Validate CAD data
    138. 138. Upload clean CAD data
    139. 139. GISguardian: GIS Analyst tasks
    140. 140. Validate network
    141. 141. Maintain workspaces</li></li></ul><li>Summary<br />FME Workspaces for different tasks:<br />CAD validation & data loading<br />OGCGeometryValidator<br />GIS data validation<br />NetworkTopologyCalculator<br />GIS data distribution<br />Scripted Published Parameters<br />FeatureReader<br />FME Server<br />Makes workspaces accessible to different users<br />Simplifies workspace maintenance <br />Scalability<br />Security allows different roles<br />121<br />
    142. 142. Introducing CADwomanCAD to GIS / GIS to CAD<br />Mita H<br />MitaHajirakr, <br />FME Desktop Support Manager, Safe Software<br />
    143. 143. CAD & GIS: Differences<br /><ul><li>What’s important to CAD users?
    144. 144. Visual clarity / Editing tools
    145. 145. Symbology
    146. 146. Labels & white space
    147. 147. Dimensions
    148. 148. Which CAD Formats?
    149. 149. AutoCAD DWG
    150. 150. AutoCAD Map 3D
    151. 151. AutoCAD Civil 3D
    152. 152. MicroStation
    153. 153. PLS-CADD (XML)
    154. 154. etc…</li></li></ul><li>CAD & GIS: Differences<br /><ul><li>What drives the GIS?
    155. 155. Data structure / model
    156. 156. Consistency
    157. 157. Attribution / domains
    158. 158. Location
    159. 159. Connectivity
    160. 160. Analysis</li></ul>Example: <br />GIS as-built  CAD Design  GIS Proposed<br />
    161. 161. GIS to CAD<br />GIS  CAD Key Points:<br />Create AutoCAD blocks or MicroStation cells<br />Preserve attributes as object data, tags or text<br />Translate the annotation (text justification)<br />Schema transformation (i.e. National CAD Standard, etc.)<br />Example<br />Symbolizing with DWGStyler<br />
    162. 162. CAD to GIS<br />CAD  GIS<br />Preserve attribution<br />Data improvement<br />Create connectivity (snapping)<br />Recover attribution from text or blocks<br />Data quality<br />Layer / Level consistency<br />Valid attributes<br />Example<br />Merging text onto geometry<br />
    163. 163. Storm: The Power of Data in the Cloud<br />MitaHajirakr<br />FME Desktop Support Manager, Safe Software<br />
    164. 164. The Power of the Cloud<br />Storm uses the power of the cloud to combat data villains <br />
    165. 165. Supported Cloud Data Storage<br />Engine<br />
    166. 166. Advantages of Data in the Cloud<br />Data available to you and others,regardless of location<br />You control who has access<br />In some cases you control where access is from too<br />Reduced administration<br />Backup strategy simplified<br />No hardware maintenance<br />
    167. 167. Advantages of Data in the Cloud cont…<br />Scalability<br />The cloud service looks after all scaling issues<br />Cost savings<br />Hardware, administration<br />Need to verify as communication costs can be more<br />
    168. 168. Disadvantages of Data in the Cloud<br />Data available to you and others,regardless of location<br />Make sure you control access<br />Scalability<br />Performance is not entirely under your control<br />
    169. 169. Disadvantages of Data in the Cloud cont…<br />Cost savings<br />Communication costs can be significant<br />Best strategy is to be totally in or totally out<br />Keeping a copy local and remote for a large amount of data can be expensive<br />
    170. 170. Cloud Database Demo:SQL Server Azure Demo<br />Read/Write to Azure and SQL Azure<br />Check out our blog posting here<br />
    171. 171. Amazon S3 Cloud Demo<br />
    172. 172. DropBox Data Sharing Demo<br />
    173. 173. Bulk Up Your Database:FME and Database Loading<br />MitaHajirakr<br />FME Desktop Support Manager, Safe Software<br />
    174. 174. Demonstration Set-up & Run<br />To run this demonstration you need:<br />Oracle or SQLServer (can be run with SDF but it’s not tested in FME 2011)<br />Run DataInitializer_CSV_to_DemoData.fmw BEFORE your demo starts<br />Loads Address points into the database of your choice – ADDRESS_POINTS table<br />Configure the Update workspaces corresponding to your database:<br />AddressUpdates_GML_to_SQLServer.fmw – my preference<br />AddressUpdates_GML_to_OracleSpatial.fmw<br />AddressUpdates_GML_to_SDF.fmw<br />For the demo<br />Display ZipCodes & Original ADDRESS_POINTS & the address updates in FME UV - <br />Run the update workspace:<br />Change the zipcode boundary (78723 & 78752 work well)<br />Change the user name <br />Refresh and in FME UV filter by LA_UPD_BY (Last Update By) to show the updated address points<br />
    175. 175. Data Updates<br />What’s the big deal about bulking up your databases?<br />Choices:<br />Truncate & load<br />Incremental Updates<br />
    176. 176. Data Updates<br />The key to successful database updates:<br />Persistent key<br />History or journal table<br />
    177. 177. Database and Table Level Updates<br /> Reloading Everything<br /> Updates Only Writing<br />
    178. 178. Feature Level Updates<br />Using Format Attributes<br />fme_db_operation<br />fme_where or database Key Column<br />
    179. 179. Transformers for Databases<br />Joiner <br />SQLCreator<br />SQLExecutor<br />FeatureReader<br />ArcSDEQuerier<br />OracleQuerier<br />
    180. 180. Database Update Example<br />Update Address Points for selected Zip Code boundaries<br />Read the Zip Codes<br />Spatial query for the Address Point updates (based on the zip code boundary)<br />Create the fme_db_operation attribute<br />Write to database with INSERT | UPDATE | DELETE<br />Initial Data<br />Example<br />
    181. 181. Tools for RasterMan<br />MitaHajirakr,<br />FME Desktop Support Manager, Safe Software<br />
    182. 182. Who is RasterMan?<br />RasterMan is a superhero that battles raster problems of all sizes<br />With FME you too can tackle raster data challenges<br />This is not RasterMan!<br />
    183. 183. Raster Challenges<br />Challenge #1: Translate & Reproject<br />Challenge #2: Mosaic<br />Challenge #3: Tile or Clip<br />Challenge #4: Drape<br />
    184. 184. Challenge #1Translate & Reproject<br />More than 50 raster formats to choose from<br />ArcSDE&GeoDatabase Raster<br />CADRG<br />ECW<br />Geodatabase Raster<br />GIF / PNG<br />JPEG / JPEG2000<br />Oracle Spatial GeoRaster<br />etc…<br />
    185. 185. Superpower #1 FME Raster Formats List<br />ADRG <br />ASRP<br />Aircom ENTERPRISE <br />BMP<br />Bathymetric Attributed Grid (BAG)<br />CADRG <br />CDED <br />DMDF<br />DTED<br />ECW<br />ENVI .hdr RAW Raster<br />ER Mapper ERS<br />ESRI .hdr RAW Raster<br />ESRI ASCII Grid<br />ESRI ArcGIS Binary Grid <br />ESRI ArcGIS Image Server<br />ESRI ArcSDE Raster Catalog<br />ESRI ArcSDE Raster Map<br />ESRI Geodatabase Raster <br />GIF <br />GeoTIFF<br />Golden Software Surfer Binary Grid<br />Hierarchical Data Format 4 (HDF4) <br />JPEG<br />JPEG 2000 <br />Landmark Z-MAP<br />LeicaGeosystems ERDAS IMAGINE<br />LeicaGeosystems ERDAS RAW<br />Maptech BSB Nautical Chart<br />Marconi PlaNet<br />MrSID<br />NETCDF<br />NITF <br />Oracle Spatial GeoRaster<br />PCI Geomatics Database File<br />PNG<br />R Statistical Raster (RDATA)<br />RADARSAT-2 XML<br />Shuttle Radar Topography Mission Height (SRTM HGT)<br />TIFF <br />USGS DEM <br />Vertical Mapper Grid (NGrid)<br />Web Map Service<br />X11 Pixmap (XPM)<br />
    186. 186. Challenge #1Translate & Reproject<br />
    187. 187. Challenge #2 - Mosaic<br />
    188. 188. Challenge #3 - Clip<br />
    189. 189. Challenge #4 - Tile<br />
    190. 190. Challenge #5 – Web Tiling<br />
    191. 191. Challenge #6 - Drape<br />
    192. 192. Resources<br />Dmitri’s Raster Studio<br />http://bit.ly/dmitri_raster<br />20+ examples, including:<br />Non-rectangular raster clipping<br />Point clouds<br />Raster to 3D translation <br />RasterExpressionEvaluator <br />Rasterization for Web Mapping Platforms<br />Raster Palette Manipulations<br />Avoiding black edges while reprojectiong rasters<br />Raster Mask for KML output<br />And more!<br />
    193. 193. MitaHajirakr<br />FME Desktop Support Manager, Safe Software<br />Battling the Forces of XML<br />
    194. 194. Why is XML So Difficult?<br />XML is a language<br />Describes the data structures as well as content<br />Capable of defining complex data structures<br />Hierarchical data structures<br />Non relational data structures<br />GIS are usually based on relational data models<br />
    195. 195. FME 2011 Power Unleashed:The Power of XML-MEN<br />
    196. 196. Safe XML Strategy<br />Leverage industry XML tools such as XSLT and XQuery<br />Users must know these complex technologies.<br />
    197. 197. Safe XML Strategy<br />Higher Level Function<br />Minimal understanding of XML required<br />
    198. 198. Reading XML with FME<br />GML 3.2 & XSD (XML Schema)<br />Most GML can be interpreted if FME can use the XSD<br />This will work if the OGC spec. is followed and internal feature constructs are not overly complex<br />Xfmap<br />Script for mapping XML structure to FME features<br />Powerful but not for the faint of heart<br />Xquery<br />W3C compliant Xquery<br />Map XML tags to features or attributes using XQueryExploder & XQueryExtractor<br />Powerful but not for the faint of heart<br />162<br />
    199. 199. XML Formats - Reading<br />163<br />
    200. 200. FME 2011 Power Unleashed:XML Reading Transformers<br />XQueryExploder<br />Split XML documents into “features” using XQuery<br />XQueryExtractor<br />Extract attributes and other structures using XQuery<br />XMLFeatureMapper<br />Construct “features” from XML using xfmaps.<br />164<br />Require XQuery or xfMap knowledge!!!<br />
    201. 201. FME 2011 Power Unleashed:XML Reading Made Easier<br />
    202. 202. FME 2011 Power Unleashed:XML Reading Transformers<br />XMLFragmenter<br />Split XML documents into manageable “features”<br />Includes “flatten option” in FME 2011<br />166<br />No XQuery or xfMap needed!!!<br />
    203. 203. FME 2011 Power Unleashed:XML Reading Demo<br />167<br />
    204. 204. Writing XML with FME<br />GML standard formats<br />FME supports a wide range of GML profiles (GML SF0, OS MasterMap, CityGML, etc.)<br />GML 3.2.1 & XSLT<br />Apply an XSLT (Extensible Stylesheet Language Transformations) to the output<br />Xquery<br />W3C compliant Xquery <br />Map FME features to XML templates using XMLTemplater transformer<br />168<br />
    205. 205. XML Formats - Writing<br />169<br />
    206. 206. FME 2011 Power Unleashed:XML Writing Made Easier<br />
    207. 207. FME 2011 Power Unleashed:XML Writing Transformers<br />Writing<br />XMLTemplator<br />Convert FME attributes to XML<br />XMLFormatter<br />Formats and beautifies XML documents.<br />171<br />
    208. 208. Writing XML - XMLTemplater<br />172<br /><feederObjectobjectID="{fme:get-attribute("objectID")}"><br /> <feederName>{fme:get-attribute("feederName")}</feederName><br /> <feederNo>{fme:get-attribute("feederNo")}</feederNo><br /> <eaLoc>{fme:get-attribute("eaLoc")}</eaLoc><br /></feederObject><br />
    209. 209. Example: XML Object Hierarchy<br />Creating an electricsubstation XML:<br />Coordinates<br />and<br />Attributes<br />and contains<br />Feeder(s) contain<br />Attributes<br />XML Document<br />Substation<br />Feeder A<br />Feeder B<br />
    210. 210. XML Writing Demo<br />Sample XML:<br />Source of XML templates<br />Add Xquery: replace attribute values with Xquery statements<br />Sample XML <br /> <substationobjectID="Vancouver Substation"><br /> <mapLocation><br /> <coord><br /> <X>669170.169</X><br /> <Y>1000199.534</Y><br /> </coord><br /> </mapLocation><br /> <facilityID>5E67B377</facilityID><br /> <sectionID>RPG123</sectionID><br /> <phaseCode>ABC</phaseCode><br /> <feederList><br /> <feederObjectobjectID="8-64"><br /> <feederName>10-24</feederName><br /> <feederNo>8763</feederNo><br /> <eaLoc>9D2D</eaLoc><br /> </feederObject><br /> <feederObjectobjectID="8-65"><br /> <feederName>10-25</feederName><br /> <feederNo>8766</feederNo><br /> <eaLoc>9D3F</eaLoc><br /> </feederObject><br /> </feederList><br /> <name>Vancouver Central</name><br /> </substation><br /><feederObjectobjectID="{fme:get-attribute("objectID")}"><br /> <feederName>{fme:get-attribute("feederName")}</feederName><br /> <feederNo>{fme:get-attribute("feederNo")}</feederNo><br /> <eaLoc>{fme:get-attribute("eaLoc")}</eaLoc><br /></feederObject><br /><br />
    211. 211. XML Writing Demo<br />
    212. 212. XML Writing:Deeply Nested Demo<br />There was an old lady who swallowed a fly!<br />
    213. 213. FME 2011 Power Unleashed:Other XML Transformers<br />XMLValidator<br /><ul><li>Ensures XML is valid.
    214. 214. Useful for reading and writing</li></ul>XMLFormatter<br /><ul><li>Formats and beautifies XML documents.</li></ul>177<br />
    215. 215. Spatial Data at Your Command<br />FME 2011: Take Command of Your Spatial Data<br />New format support enables you to work with a whole new world of data<br />Easier than ever to get started and use<br />Faster than before<br />
    216. 216. Merci!<br />Questions?<br />Techniques<br />Yves St-Julien:<br />yvess@consortech.com<br />Ventes<br /><ul><li>Louise Doyon:louised@consortech.com</li></ul>Gerry McCoubrey: gerrym@consortech.com<br />www.consortech.com<br />1-888-276-0543<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×