Downloaded 52 times
![Thank You! Don’t hesitate to drop us suggestions, comments, ideas, opportunities, etc: Email: [email_address] @DonAtSafe http://fmepedia.com http://www.safe.com http://blog.safe.com](https://image.slidesharecdn.com/tastetestfme2011beyond-101021134420-phpapp01/85/Taste-Test-FME-2011-Beyond-57-320.jpg)
Uploaded bySafe Software
Taste Test: FME 2011 & Beyond
The document summarizes new features and enhancements in FME 2011 and beyond, including improved branding, workspace look and feel, data inspection capabilities, support for new formats like point clouds and SQL Azure, and future plans like more 3D transformations and large scale point cloud handling. REST APIs and server security improvements are also mentioned.
More Related Content
Similar to Taste Test: FME 2011 & Beyond
Taste Test: FME 2011 & Beyond
- 1. Taste of FME2011 & Beyond
- 2. New FME Branding!Achieve Total Spatial Data Mastery Cooking
- 3.
- 4.
- 5. Focus of BrandingMake you the master chefs!
- 6. What’s Coming outof the Big Oven in Surrey? FME Workbench
- 7. Presentation is importantto the sophisticated palete!
- 8.
- 9. Make Your OwnTheme!
- 10.
- 11. Workspace Inline DataInspection
- 12. Workspace Inline DataInspection
- 13. Workbench Inspection DemoTrends and Directions in Spatial Data Exchange
- 14. Download Recipes with….Trends and Directions in Spatial Data Exchange
- 15. Workspace Templates Trendsand Directions in Spatial Data Exchange
- 16. What’s coming outof the Big Oven in Surrey?
- 17. REST API RESTAPI will make it much easier to work with FME Server and leverage the services that it provides. Obligatory Cat Photo
- 18.
- 19. FME Server Securitycontinues Currently security is server wide. Repository Level Security Define Repositories that users can access Define type of access that they have.
- 20. Scheduler Slide Scheduling capabilities are part of FME 2011 Server
- 21.
- 22. What’s Coming outof the Big Oven in Surrey? Platform
- 23. More Ingredients tocook with… GIS CAD Raster Database Web 3D/BIM Point Clouds
- 24. FME Formats byRelease 9/2/10 Trends and Directions in Spatial Data Exchange
- 25. Format Usage Patterns9/2/10
- 26. New Format RoundupESRIJSON (ESRI JavaScript Object Notation) FDO Providers (Autodesk 2011) Google Spreadsheet LiDAR (XYZ) Microsoft Windows Azure Microsoft Windows Azure OGDI Netezza Netezza Spatial PointTools (POD) Schema (From Table) World Meteorological Organization GRIB (GRIdded Binary)
- 27. Point Cloud SupportPoint Cloud debuts in FME 2011.
- 28. Point Cloud SupportWhat can you do with Point Clouds?
- 29. Point Cloud Scenario#1 Read: LAS (several flavours) Oracle Spatial Point Cloud POD (PointTools) Write: LAS (several flavours) Oracle Spatial Point Cloud POD (PointTools) ESRI Geodatabase Any FME Format Translate
- 30. Point Cloud Scenario#2 Thin
- 31. Point Cloud Scenario#3 Reproject
- 32. Point Cloud Scenario#4 Split
- 33. Point Cloud Scenario#5 Clip
- 34. Point Cloud Scenario#6 Combine
- 35. Point Cloud Scenario#7 Tile
- 36. Point Cloud Scenario#8 Surface Model
- 37. Point Cloud Scenario#9 Inspect
- 38. Point Cloud Scenario#10 Chip
- 39. Point Cloud Demo9/2/10
- 40. Light and FluffyEngine
- 41. Cloud Database Demo:SQL Azure Demo 9/2/10 Read/Write to Azure and SQL Azure
- 42. Baking Complex XML The Saga continues…
- 43. XML Reading Demo9/2/10
- 44. Verification? How dowe know the XML we write is valid? Writing Complex XML
- 45.
- 46.
- 47.
- 48.
- 49.
- 50.
- 51.
- 52.
- 53. Journey to the3 rd Dimension continues
- 54. Geometry Instancing: EfficiencyConcerns Demo: FME 2011 vs FME 2010 FME 2010: 75 Mins (4 GB) FME 2011: 40 Seconds (2 GB)
- 55. Looking Ahead: TheWild West More Formats Revit R, Sketchup W, GML 3.2, improved CAD, ArcGIS 10, … More 3D/BIM specific Transformations Roof creation Containment Union / Intersection / Difference Clipping / Shearing Validity checking / Snapping Improved Geometry Large Scale Point Clouds (Lidar) Clothoids, nurbs, rotated points 3D Symbology: Geometry Instancing
- 56. And more …Python Plugin Builder New XML Template Writer Database Transformers Improved Database Query Support FME Server Deployment Management Performance Named Geometries Server GUI Modernization POSTGIS unicode/arc geographic support OSM Writer More Generalization Looping for Blocking Transformers Google Docs Support True arc Intersections
- 57. Thank You! Don’thesitate to drop us suggestions, comments, ideas, opportunities, etc: Email: [email_address] @DonAtSafe http://fmepedia.com http://www.safe.com http://blog.safe.com
- 58. Thank You! Questions?For more information: Enter name and email address Enter company name Enter other resources
Editor's Notes
- #8 D&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
- #9 D&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
- #10 D&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
- #11 D&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
- #12 D&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
- #13 D&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
- #17 Yesterday we talked about how with FME 2008, we’re taking spatial ETL to new dimensions. Today, we’ll focus on how FME Server helps raise the bar in how you leverage the power of spatial ETL across the enterprise and beyond.
- #42 Show how easy it is to go to both Azure and SQL Azure. (Azure is not spatial) Also show the inspector here.
- #43 Problem Lots of user data is stored in relational databases or files with flat table structures, and increasingly there are requirements to generate difficult/complex XML from this data are on the increase (OGC, INSPIRE, etc). State of Montana’s desire to convert their Spatial Names Database from ESRI Personal Geodatabase into the ISO 19112 XML standard ( Spatial referencing by geographic identifiers). Previous attempts at XML writing with FME have required specialized knowledge of an additional XML language (XSLT, XFMAP, XQUERY). Solution XMLTemplater allows us to use the power of xQuery but hide a lot of the complexity using a ‘Hierarchical Template Representation’ methodology. How it works Start with complete XML document representing your desired output. Determine which pieces of the document will change and make XML templates. In this case, need to turn features into iso19112:SI_LocationInstance XML elements. The iso19112:SI_LocationInstance XML template specifies which attributes will be used to generate the XML. All of the iso19112:SI_LocationInstance XML snippets will then be inserted into the complete wfs:FeatureCollection XML template. The workflow in FME is: read the geodatabase table, read a XML template and use attributes from each feature to generate XML, Logger: see the attributes values from the feature are present in the XML, read another XML template and use the XML from the previous XMLTemplater to generate the final XML, write it out with the text file writer. Pitfalls Easy to generate invalid XML (no validation) Hasn’t been tested with very complicated source data and XML output.
- #44 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.
- #57 D&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