FME Form

Hi allI want to define the Geometry Type in PostGIS-Writer. I recently changed from an old version of FME to version 2025.2 In the user dialog of the writer there ist still a field for the definition (feature type/user attributes/spatial definition/geometry type, but the field is de-activated (grayed out).Is there a way to “manually” define the geometry type for postgis tables?  Thank you for any help.

I developed a small MCP server that exposes an FME workbench (.fmw) as a service that can be invoked via natural language, using an AI client (e.g., Claude).The interesting aspect is the architecture and the simplicity of "assembling" the various components:1) I build the FME flow that executes the workflow, managing logic, transformations, and formats (we leave to FME what belongs to FME),2) the MCP server exposes operations and parameters in a controlled manner,3) the AI ​​client interprets the request in natural language and translates it into a structured call. 

Linked to this query, that i believe is now closed, it would be great to be able to export GOCAD TS files.

Hi,I’ve created an FME workflow which successfully creates a csv and zipped shapefile and emails a recipient. However, I want to use the TempPathnameCreator so that the output files are wiped after emailing. I’ve adapted the workflow but it fails to create the files. On inspecting the rejected email output it couldn’t find the files in the temp folder, but when testing with just the writer 0 features are output. I assume I need a separate TempPathnameCreator for both zip and csv file or can they be in the same folder? Here is the final part of my workflow. Is my configuration wrong? Josh

Hi,I have a file geodatabase (.gdb) containing feature classes, along with an Excel file that includes ArcGIS Pro SQL definition queries intended for specific feature classes.Example: gdb with feature classes ArcPro definition querySchema = '1' And Rodzaj NOT LIKE '%B%' I’d like to understand how I can automatically convert these ArcGIS Pro SQL queries into FME SQL syntax. The queries will vary each time and are tailored to individual feature classes. This SQL works in FeatureReader but it requires a lot of manual work   

Hi,  I get an error “unable to open primary document entity” if I have a XML-file with a space-character “ “ in the filename of the XMLfile I want to validate in XMLValidator. (2024.2) My questions: is there a work around to set up “Manage User Parameters”, so I can’t upload XML-files with a space in the filename? Best regards,Inka

Hi,I want to tile LiDAR data. My project contains about 550 tiles (1 km × 1 km), so processing everything at once in a standard FME workspace is not practical, as my PC would struggle with the memory requirements.At the moment, I use a shapefile that contains a "to_run" attribute. In QGIS, I select a group of tiles and update this attribute. In FME, I use a Tester together with a Feature Reader so that only the selected tiles are processed.While this works, the workspace still consumes a lot of memory, and I have to monitor the process more closely than I would like.I think a solution using WorkspaceRunner could be more efficient, as it would allow FME to process one tile at a time instead of loading a large batch at once.I have:A shapefile containing all tiles that need to be generated. The LiDAR source data.What I am struggling with is that I don’t know how to do it exactly. I feed the workspacerunner the shapefile with tiles but then in the bench that needs to run I also load in the

Hello Community,in FME 2024 I was able to find out whether I was running a workspace on FME Flow or locally by checking FME_SERVER_WEB_URL or FME_SERVER_HOST values. Both values would be empty unless the workspace was actually running on FME Flow. Fast forward to after upgrading FME to 2026, in FME Form, FME_SERVER_* parameter values are URL/host of the FME Flow FME Form is connected to. Knowing whether a workspace is ran locally is important e.g. if it calls a child workspace (using WorkspaceRunner vs. FMEFlowJobSubmitter). It is also very helpful during authoring/troubleshooting. How can I do this in 2026? Thank you in advance for any tips/ideas

Hi all,I’m working with FME 2025.1 on a LandXML export-import workflow and encountering an issue: LandXML Reader and Writer do not have a Version 1.2 option. My goal is to export a corridor alignment, but the vertical alignment (profile) data is not coming through correctly. Without 1.2 support, how can I tolerate or work around these missing elements in FME? Specifically, I’m wondering: Is there a way to properly bring vertical alignment data from a LandXML 1.2 file into FME? Are there alternative formats or preprocessing steps to compensate for missing data? How can I avoid data loss on the Writer side, since 1.2 is not supported for export? Thanks in advance for any guidance!

Hello,I have a workbench that converts GIS data to an AutoCAD Map 3D object data file. In this workbench, I’m creating new layers that don’t exist in the template file being used, and would like to set their default lineweight of these new layers to “Default” or “ByLayer”. I am able to successfully define an “autocad_lineweight” attribute in the workbench and set it equal to -3 or -1 and the GIS line features that are translated receive the correct lineweight value.However, the layers themselves do not. The layer default lineweight appears to be controlled by the “Default Lineweight” parameter in the writer feature type. Unfortunately, there doesn’t appear to an option to select -3 or -1. Additionally, attempting to set that parameter to the previously defined attribute leads to a failure w/the following messages (xyz is the path & file name of the output):AutoCAD Writer: An error occurred for dataset ‘xyz’ in function RealDWGWriter::checkToCreateDynamicObjectDataTable. Unknown exc

When I attempted to upgrade to StringPairReplacer, Show Changes displays:StringPairReplacer Version 2 replaced by StringReplacer Version 6StringReplacer Change Log, version 6Added multi-attribute string replace support.My Replacement Pairs in StringPairReplacer v2 has multiple lines and quotes. This has worked great for years, and now I can’t upgrade. My first impression is that StringPairReplacer was changed so dramatically that it might have been better to leave it alone (and not replace it with StringReplacer). Here’s what my old StringPairReplacer looked like. And here are my Replacement Pairs (using the Open Text Editor). I use multiple lines and quotes, and it works great.Apparently, the upgrader is not expecting multiple lines or quotes. It’s a mess.I tried creating a csv file but, I couldn’t figure out the proper format.Finally, I removed the quotes (replacing spaces with underscores) and put it on a single line. Now, the upgrade works. I wouldn’t call this success. It will be

Hello ,I would like to create a complete review list of all FME workspaces and processes in our environment.The first requirement is to generate a list of all FME names available in FME Server, including: Which users have access to export them Whether they are automated If automated, on which day and at what time they run  Where is the FME output stored? If they are manually exported, which users have permission or access to perform the export The second requirement is to create a list of all FME workspaces built and stored on local Windows environments.I would also like to export all names and related information into Excel files.What would be the best solution or approach to manage both requirements and create a complete review list of all active and working FME .Thanks in advance 

I got this error when trying to add attachments to AGO: The ArcGIS REST API returned an error: HTTP Error Code: 413 : '' Message Code . Further details: 'The page was not displayed because the request entity is too large.'Esri community has a solution to edit the header, but there’s no option to edit header on transformer? 

With the now depreciated IFC with Data Views, I was able to extract colour properties using an Appearance Extractor which I could then write to the resulting multipatch. Having looked at the IFC_API reader, it doesn’t seem to have any of the colour properties and all fail in the Appearance Extractor. Can anyone advise on how to access the colour using this reader? 

Hello FME-Communtiy,With the advent of the new IFC-Writer we wanted to update and hopefully slim down our FME Workspace, which reads Multipatch Geometries via an Esri Geodatabase (File Geodb) Reader and writes IFC-Features via an IFC XML/STEP (deprecated) writer. Sadly we’ve not managed to get the new writer working as needed and have found the documentation rather lackluster, which is why I’d appreciate any pointers from the knowledgeable people on here.The new workspace has managed to correctly export the feature geometries, but the attributes seem to be missing/not written at all. Inside the new Workspace the features have the correct attributes and values up until the very end where they are sent to the IFC-writer (In this Case I tried Slab as the Element Type, BuildingElementProxy gave the same results and SpatialZone doesn’t work at all anymore).New Workspace final export inside Data Inspector (red color intentional)Old Workspace final export inside Data InspectorIn the old Works

.

Hi there, I have about 230 workspaces that run daily to import data using the ArcGIS Feature Services Reader. The issue is, with every run I get warnings that don’t seem to be a problem, but make it seem like the workspaces aren’t running right.NOT changing coordinate system of reader identified by keyword `SAFE.ESRI-AGOL.ARCGISFEATURESERVICE_1' from `EPSG:7844' to `LL-GDA2020_FME' -- mapping file setting of `EPSG:7844' overrides coordinate system `LL-GDA2020_FME' read from fileThis warning just seems to be stating the coordinate system will not be overridden by FME’s LL-GDA2020_FME Coordinate System. It is logged for every reader feature type ArcGISFeatureServiceReader: Querying feature server 'https://public-services.OrganisationURL.com/public/rest/services/ServiceName/MapServer/This warning should not be a warning in my opinion, as it's just stating that the reader is querying the feature service. This occurs once for every reader feature type as well. Debugging is disabled, however

Hi,So I would like to try to work out a point source ID for point clouds based on continuous chunks of time. Basically separating out flightlines. For example, a point should has 30 points. The first 10 are collected in the first 10 seconds, then there is a gap of 1 minute before capture, and then another 10 are collected, then another minute gap, then the last points. So in this case I would like to determine a unique component value for each of the 3 time related groups.I think I can do this if I coerce the cloud to points. But that really isn’t efficient for billions of points.I also won’t know beforehand how many different continuous capture periods there are.Can anyone think of a way to do this? It’s pretty easy to do in lastools. But in this case I’d like to do it in FME. I don’t know any python which I presume could do it.I am ideally wanting this to work in version 2022, but I’m open to a newer version if that is the only chance of doing this.Thanks

I have this data that I want to be treated as immutable (read as strings) in the format CSV (but i suspect that this issue is true for other formats as well?) but FME keeps auto format it to a different format. I think this started with FME 2024 or possibly 2023. Since then I’ve somewhat changed methodology for new work spaces, but yesterday a revisited an old WS and got reminded of this source of frustration. I hope that someone can cure this case of “excel-autoformat-hell” with a solution or an explanation? I really don’t want my data changed automatically in any shape or form.Example.CSV-file states that attribute “Datum” has the value ‘2026-05-20’ FME (CSV) reader keeps format it to  ‘20260520’. Even if i manually change the attribute to data type string or varchar FME still formats the date according to above.

Hi, I have two local authority boundary datasets that should align along a river but don’t and this is causing the Master Lookup between the two boundary datasets to be wrong. These two should be aligned and coterminous. How do I easily solve it? 

Newer versions of FME Form can be connected to FME Flow for the purpose of obtaining Deployment Parameter values at runtime:Given that FME Form is connected to Flow I was wondering if anyone knows of a way of obtaining details of that connection when a workspace is run in Form. It does not appear to be exposed anywhere.A workaround would be to create a Deployment Parameter in my Flow instances and reference that in Form but it seems there should be an out of the box solution to this.Specifically, what I want to do is to query the FME Flow API for the connected instance, without having to hard-code the FME Flow URL in the HTTPCaller.

Please create an FME option to connect to GCP (Google Cloud Platform) using “Workload Identity Federation” method in addition to Service account (current option).Thank you!

Hello everyone,We just upgraded to FME Form 2024.2.1 and we currently encounter one problem. For the users, the personal database- and web connections were inititally not migrated. Thus we sent first a mail to the users that they coud export the database- and webconnections in FME Form 2023 and then import  the exported file in FME Form 2024. It looked like it solved the problem, however when the users logged in the next day on an new machine, they lost all their personal database-  and webconnections.We read the following link: Changes to Connection Storage in FME Form 2024 – FME Support Center and it became clear to us that's due to the new way that personal database- and webconnections are stored. They are stored in fme_userconnection.data and the machineID is hardcoded in this file.In our organization we work on a virtual machine and thus also everytime we log into a new machine. It's now clear why the database- and webconnections are not visible in FME Form 2024.I was wondering if

Hi All,I’m trying to calculate volumes on meshes in a dgn file. The dgn file represents rail embankment / earthworks (ballast, formation, etc.). Below a screengrab of the design:My current workaround is DGN Reader → SurfaceBuilder → SolidBuilder → VolumeCalculator but am finding that some of the meshes are not closed. Before calculating any volume I need to close the meshes but can’t work it out,Any idea about how close the unclose meshes? Thanks!