Skip to content

Integrating Third-Party Tools with FME (No Coding Required)

Yes, FME can translate a lot of data formats, and yes, it can perform a lot of transformations on your data… but after all those hundreds of readers, writers, and...

Yes, FME can translate a lot of data formats, and yes, it can perform a lot of transformations on your data… but after all those hundreds of readers, writers, and transformers, what if it still doesn’t support the functionality you need?

There are a few ways users can extend FME with more readers, writers, and transformers. The traditional way is to code a plug-in using one of the various SDKs that comes with FME. This and other methods are mentioned below. Now, as of FME 2016, if you have a third-party command-line tool that can read, write, or manipulate data, you can integrate it with FME by building an ordinary workspace.

More specifically, you would use the FeatureReader and/or FeatureWriter and build a custom transformer. This brings the tool’s full capabilities into the FME workflows we all know and love, and hides the tool’s complexities beneath a friendly dialog box.

Using a tool on the command line vs. using a tool as part of an FME workflow.
Using a tool on the command line vs. using a tool as part of an FME workflow.

Check out the FME Hub to see a few custom formats and transformers other FME users have created.

I want to transform my data in a way FME does not support.

If you have a command-line tool that processes data in this way, create a custom transformer. Your custom transformer should collect parameters, use the FeatureWriter to save the data in the format expected by the tool, build and execute a command line, then read the processed features back with the FeatureReader. Learn how to do this.

LAStools and FME
This data was processed with the LAStools functions lasnoise, lasground, lasheight, and lasclassify.

I want to read a format FME does not support.

If you have a command-line tool that can read the format and save it as something FME can read, create a custom transformer that will act as a Reader. Your custom transformer should collect parameters from the user, build the command line and execute it, then use the FeatureReader to read the data created by the command-line tool. The data features will leave your custom transformer as though imported by any standard FME reader, and you can do any manipulation you want and write to any supported format. Learn how to do this.

This Candy World was created with the SVGReader, a custom transformer that leverages ImageMagick.
This Candy World was created with the SVGReader, a custom transformer that leverages ImageMagick.

I want to convert my data to a format FME does not support.

If you have a command-line tool that can save to the format, create a custom transformer that will act as a Writer. Your custom transformer should collect parameters, save the data features to temporary file(s) with the FeatureWriter, then assemble a command line and execute it on the temporary file. The results will go to the location specified by the user, just like a normal FME writer. Learn how to do this.

This animated GIF was created with the AnimatedGIFWriter, a custom transformer that leverages ImageMagick.
This animated GIF was created with the AnimatedGIFWriter, a custom transformer that leverages ImageMagick.

Some tools and libraries to consider.

Functionality with some of the above has been integrated with FME by our users and the FME wizard himself (this how-to guide has downloadable workspaces for the examples shown in the above images).

If you have a toolkit or library you want included in this list, leave a comment and I’ll add it!

What if I don’t have a third-party tool for the functionality I want?

To read/write simple data: Create a custom format

If you know how the format stores data, you can create your own reader as a Custom Format. (See custom format examples in the FME Hub.) To do this, use existing readers (most often CSV, Text, XML) along with a few transformers to restructure the data, then save the Workspace as a custom format. Note that custom formats are limited to readers, and a custom transformer as discussed above offers a lot more flexibility in terms of where you can place it in your workspace.

For coders: Use scripts

You can use Python or Tcl scripts within a workspace, via startup/shutdown scripts and the following transformers:

For serious coders: Use the FME Plug-in SDK

Developers, you can code your own reader/writer or transformer with the FME Plug-in SDK. Lots of our partners use this to add new functionality to FME. These days I prefer not to touch coding with a 39½-foot pole, so I’ll leave you with those links and move on…

What if I want to integrate FME with my own application?

If you are actually looking to extend your own application with FME (i.e. having FME directly integrated into your software, like the FME Exporter for Revit or the Esri Data Interoperability extension), you can develop a plug-in to read/write your format or run an FME Workspace.

*

Custom transformers make FME’s potential truly limitless. FME already supports hundreds of formats and transformations, and now the FeatureReader and FeatureWriter bring a whole lot more within reach. By creating a custom reader or writer, you can leverage the full power of FME for any data you have, regardless of format. By creating a custom transformer, you can bring even more transformation power to the formats FME already supports. What third-party tools would you like to leverage with FME?

With custom transformers, you can transform ALL THE THINGS!
With custom transformers, you can transform ALL THE THINGS!

To learn more about integrating third-party tools with FME, register for next week’s LiDAR webinar.

Safe product icons
Reach out and get started with FME today

Real change is just a platform away.

198575