Skip navigation
All Places > Open Platform, Standards and Interoperability > Blog

Hello Interoperators!


If you watched the video ArcGIS Data Interoperability In Action you might have some questions on how some of the demos were built.


I tend to create Spatial ETL tools with external sources - namely .fmw files - as I can easily drag them into Workbench after opening it from the Analysis ribbon or share them with FME users.  They are attached below to give you the pattern, but they will not all work for you without repair and replacement of credentials.  Contact me if you need help with any of them.


To head off one question - how did I create the New York county name pulldown parameter and attribute value mapping in the Simple Powerful ETL demo, see the CountyParameter.fmw workspace.  It scrapes the NY website and writes a CSV file that can be used to import parameter values for the demo tool.  You can see the pattern and recycle it elsewhere.


At Pro 2.3 (and classic Desktop 10.7) we have gone from 308 supported formats in Pro 2.2 to 372.  But, since one of the formats is GDAL Generic Raster that embodies more than 100 actual raster formats, the real format count has exploded.

The background story to this has been both a closer relationship to the underlying FME product plus a decision to support raster and imagery workflows.


Again we have made sure to adopt as much (in fact almost all) FME transformers possible.  The main area of difference are transformers related to FME Server interaction.  If anyone has need of those, please drop us a line.

Latest FME Engine!

Pro 2.3 (and 10.7) ships with the FME 2018.1.1.0 engine, and as soon as we can manage it we'll ship the FME 2019 engine.


How does this help me?

Shipping all this new functionality means you can enjoy equivalence with your FME workspaces, sharing FMW files with other users knowing things will not break, and building raster workflows into your ETL practice.