1. FME inside ArcGIS – the Data Interoperability Extension
Bruce Harold
Product Manager, ArcGIS Data Interoperability

2. Get out of the game of chasing formats Make known formats “just work”
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

3. OK, but what is the user story of Data Interop versus FME?
SAFE have FME for ArcGIS
FME has the raster writers, PyFME
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 ArcGIS Server
There is a price difference

4. 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…
ArcCatalog – extension off, browse tutorial data sources, note GML behaviour
ArcCatalog – turn extension on, show data visibility
ArcMap – show thematic mapping, do an Intersect of two data sources
ArcMap – show Quick Import, discuss Quick Export

5. How is FME “delivered” in Data Interoperability?
Handling Feeds and other formats
Demo #2
GeoRSS
What is the footprint of the Japanese quakes?
But wait there’s more…
ArcCatalog – show Interop Connection to GeoRSS data
ArcMap – calculate footprint of the recent quakes in Japan

6. How is FME “delivered” in Data Interoperability?
The real fun begins with Workbench in ArcGIS
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”

7. Thank You! Questions? For more information: Bruce Harold Esri
All other problems call Don!