26. New Format Roundup ESRIJSON (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)
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.
58.
Hinweis der Redaktion
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
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
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
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
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
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
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.
Show how easy it is to go to both Azure and SQL Azure. (Azure is not spatial) Also show the inspector here.
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.
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.
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