FME inside Arc GIS the Data Interoperability Extension

FME inside Arc. GIS – the Data Interoperability Extension Bruce Harold Product Manager, Arc. GIS Data Interoperability

Why DIE? § Get out of the game of chasing formats § Use partner technology § Make known formats “just work” § Direct read in maps, geoprocessing § Direct write § Embed SAFE’s transformation technology § SAFE are the industry standard

OK, but what is the user story of Data Interop versus FME? § SAFE have FME for Arc. GIS § FME has the raster writers, Py. FME § FME has standalone FMW § Esri has Data Interoperability § Many users prefer a single channel § Data Interop has the vector functionality § Data Interop has the spatial DBMS readers/writers § Data Interop works with Arc. GIS Server § There is a price difference

How is FME “delivered” in Data Interoperability? § Direct Read (adds 120 formats to Catalog tree) § Quick Import Tool § Quick Export Tool § Demo #1 § Direct Read, Import, Export § Which subdivision is most flood prone? § But wait there’s more…

How is FME “delivered” in Data Interoperability? § Handling Feeds and other formats § Demo #2 § Geo. RSS § What is the footprint of the Japanese quakes? § But wait there’s more…

How is FME “delivered” in Data Interoperability? § The real fun begins with Workbench in Arc. GIS § Spatial ETL Tools § Demo #3 – set the scene: § If you remember (when) § Top milk from glass bottles § Washers had wringers § Hardware stores sold dynamite § You’ll know these guys: § od § vi § “Loading Geodatabase Attachments with DI”

Thank You! § Questions? § For more information: § § § Bruce Harold Esri bharold@esri. com http: //www. esri. com All other problems call Don!