FME 2024.1 - Feature Highlights

FME 2024.1 - Feature Highlights

Introducing FME 2024.1! This latest release focuses on significantly improving workflow efficiency. With enhanced capabilities for API interactions and JSON visualization, you can streamline complex tasks and reduce manual efforts. The update also brings a refreshed user interface for FME Flow, making it more intuitive and user-friendly. Upgrade to FME 2024.1 to experience these valuable enhancements that boost productivity and precision in your data workflows.

Feature Highlights

New OpenAPICaller Transformer: The new OpenAPICaller enables you to directly import OpenAPI specifications to automatically configure your transformer to call your endpoint of choice. The OpenAPICaller also introduces a way for you to visualize your JSON in a tree format, helping you fragment your JSON body and output it into features.

Preview and Test: Preview URLs, test requests, and view responses directly within HTTPCaller and OpenAPICaller Parameters dialog. This integrated approach reduces setup time, provides immediate feedback, and simplifies the process of configuring and analyzing HTTP requests.


Additional Enhancements

Parameter Annotations within FME Form: Enhance your ability to document and understand your data workflows by allowing context-specific Annotations directly within Parameter Editor dialogs, ensuring that relevant information is always visible without cluttering the workspace. 

Improved Quick Add: Easily find and select the most relevant transformers, readers, and writers for your data integration tasks with new filtering options, sort options, and an updated information hierarchy. 

New IFC Reader: The updated IFC reader now supports the latest IFC versions, making it easier to read and translate IFC data to GIS. The new simplified relational view improves readability and data management. Enhanced support for new feature types and properties in IFC 4.3 and above, along with better spatial reference system compatibility, ensures smoother integration with GIS applications.

New DuckDB Reader: FME now supports DuckDB, an in-memory, columnar SQL database management system designed for analytical workloads. This new integration includes a native DuckDB reader and the ability to submit queries to DuckDB via the SQLExecutor transformer. This allows you to read data from DuckDB databases and efficiently query cloud-native data formats, such as Parquet files on S3. Learn more at

Enhanced GeoJSON support in the Creator Transformer:  Geometry integration is now streamlined using the Geometry published parameter with FME Flow,  and a redesigned Coordinates tab in the Creator transformer makes it easier to input coordinates from FME Data Inspector, log files, or in your custom formats, including matching brace sets for lines and polygons.

FME Flow Dashboard: Replacing the FME Flow home page, the new dashboard is your central hub. It  focuses on actionable information, quick access to frequently used tools, and provides an overview of FME Flow jobs and automations.

Simplified FME Flow Hosted Upgrade: Upgrade FME Flow instances running on Flow Hosted easily, without any downtime and with limited configuration changes required. New clone functionality allows you to clone all settings and configurations from an existing FME Flow Hosted instance to a new one, simplifying the upgrade process. New URL modification capability allows you to change the URL of running or paused FME Flow Hosted instances, offering greater control over instance management.

Surface Model Transformers: New "Breakline Method" parameter in the TINGenerator, DEMGenerator, and RasterDEMGenerator transformers provides you with the flexibility to choose between preserving the Delaunay condition or maintaining breakline edges.


The parameter annotations look awesome!!!

‘Data Virtualization’ did not make it to 2024.1 release 😔

When I do an ‘duplicate on writer’ with multipolygone geopackage , the reader show ‘All’ as allowed geometry, but in the writer I cannot see the geometry type.

In FME 2023, we could see the allowed geometry type


Hi @pabloolivaresm thanks for bringing this issue to our attention. I’ve created a separate thread in the FME Community to further discuss this issue. You can see my follow-up response here: 


SQLCreator not working anymore if an geometry is included in the select statement!!!

(FME Form 2024.1 Build 24612) In 2024.0.2.2 Build 24219 it was ok...(→ Oracle DB)

Hi @orkng, I can’t reproduce your SQLCreator and Oracle issue.  Please fine a ticket with us to investigate or share more information with us.

I’m interested in the stored geometry (point, line, polygon), Coordinate system, and Oracle database version and client version please.  

I tested SQLCreator with a select statement that included an attribute and the attribute that is the SDO_GEOMETRY data type. Just point data.  Tested 2024.0 and 2024.1 (b24612) but geometry came back and i was able to view it in Data Inspector. 

Where are you seeing it not work now if a geometry is included in the SQL?