Unanswered questions

I want to convert OSM data downloaded in .osm.pbf format into OSM format, but I’m encountering the following issue:When converting from .osm.pbf to .osm in FME, the OSM XML data is incorrect: all polygons (areas) become lines, and many objects are missing. I tried using Osmium Docker for the conversion, and the OSM data remained intact.Is there a way to achieve the same result as Osmium within FME? Am I missing something?

Hi All, I’m sure this is very simple but I can’t seem to get it to work.I want to take the text body sent to my automation via a webhook and use it as the input to my workspace.So this would be the POST I’d then like to pass “this is not a test” into the workspace POST_test (below) so that I can process it further in the workspace. I imagine the issue is that I’m not defining where the information is coming from when entering the workspace, which is just a text file reader and text file writer for the purposes of this test.I followed this tutorial and can trigger the workspace using this method but I cannot get it to read the text directly from the body.Send Source Data to FME Flow with HTTP POST – FME Support CenterFurther searching suggested setting the source as a user parameter.I’ve tried to set the input as text string using a user parameter but this doesn’t remain in the reader after clicking ‘ok’.I’m using Flow 2024.0.5 and the V3 REST APITIA

I have got an inital line featureclass from which I make a new one with splitted the lines, based on a measure table (MeasureGenerator, FeatureMerger, Snipper). I want to make a fme tool that can update this featureclass based on an updated measure table.  I want to conditional handle the attribute values of all changes in the new feature class. Measure:0-2000;2000-4000;4000-8000 (measure in meters)Becomes Measure:0-1000;1000-2000;2000-2500;2500-5000;5000-8000Makes combined:0-1000;1000-2000;2000-2500;2500-4000;4000-5000; 5000-8000In the record of 0-1000 should be the attributes (Start, End, etc) of ‘Measure’ and ‘Becomes Measure’ so I can check from which former feature the new feature will get the attributes. This will be based on the largest overlap in length. I have tried this with the LinOnLineOverlayer. Here the line output does not give the answer and the point output gives all the answers except for when the endpoint is the same (0-2000 and 1000-2000).How should I do this? Am I

The white rectangle is my polygon and the orange line is my line. I am trying to clip the polygon based on the length of the line.I was looking for an output like this. I have looked at this step  and also this step but i am not getting a correct clip.  Any ideas will be highly appreciated Thanks in advance,Keller. 

Happy May Day!This works in 2024-2025 and breaks at 2026.1.I have several autocad format attributes selected (confusing methods to select see below). I go through many transformers and can see those same format attributes (1 for example autocad_entity_handle) all the way up to and including the attributemanagers (pictured). But looking in the attribute manager (This was an issue before upgrading the attributemanager transformer and is also an issue since I have upgraded the attribute managers). Many of the format attributes are gray. 1.What is the significance of this?Why if the autocad_entity_handle format attribute is enabled does it show as “not found” (red)?

Has anyone got any tried and tested methods for testing ArcSDE connections that are stored in FME Flow, en masse rather than one by one.I thought i could use an SQL Executor but it appears FME doesn’t handle the error messages when they’ve come from a failed SDE connection so the workspace terminates if there is one bad connection.

I’ve tried out the AI assist this week for the first time and it worked fine until it suddenly threw and error. When now starting the AI Assist within a workbench, it throws the following error: “Unknown Error. SSL connect error. When login out and back into the FME account, it sometimes works for 1 prompt and then throws the error again. It seems to work for a colleague within the same network as of now. Any suggestions?

Hello, I am currently working on adding data (a source file in Geopackage format containing point and polygon tables) to our Oracle enterprise database. I am using a dynamic workspace to process the data and an external table (CSV file) to define the required schema in the FeatureWriter. When writing the data to the database, three additional attributes (not defined in my schema) were recorded. They are called “rotation”, “textstring” and “height”. After some research, I realised that these are likely linked to the following FME attributes: fme_rotation, fme_text_string and fme_text_size and that this is related to the “fme_point” geometry. I have tried several ways to remove these attributes but have not succeeded (exposing the attributes and removing them before the writer, telling the writer not to write them in ‘attribute to remove’, writing the tables containing polygons and those containing points separately in different writers.Do you have any ideas to guide me in this task, or

Hi again, I hope you don’t get an impression I am spamming the group, but I took my previous output a few steps further (thanks ​@janrykr) - after all, how can I measure that I actually achieved the desired goal - turning labels into something meaningful. So, I vectorized the isolines, overlaid labels over lines, forced lines to 3D with the elevations received from points, built a TIN, added the source raster as a texture, and used my 3DModelVideoRenderer to visualize the output, giving this post the necessary for this group AI-component - the Python code in the transformer is generated with AI. Considering that not all lines got elevations, I think the result is actually quite good.Dmitri

Hello,I am trying to create a workflow reading a file from one path, rename to respect Autodesk Forma naming convention and upload to the Autodesk platform with a new name.However, I can only input the existing full path (so with the not yet adapted name) in the AutodeskDocsConnector.I don’t want to create a local intermediate copy, and wish to run this on Flow later, any idea ?Thank you !

Has anyone else encountered issues with the FeatureReader now returning fme_basename and fme_dataset information in 2025.2.1?In 2024, the FME attributes that were returned automatically are fme_feature_type, fme_geometry and fme_type. fme_basename and fme_dataset were only returned if they were set under Additional Attributes to Expose.In 2025, the Feature Reader returns both fme_basename and fme_dataset.This can cause issues where a workspace is merging data and it’s assumed the attributes coming from the Feature Reader don’t have these attributesJust to complicate matters further, a workspace written in 2024 but run on FME Flow 2025 follows the 2024 behaviour. If you download that same workspace and run it on FME Form 2025, the behaviour is different.

I am facing issue when reading Google Sheets v4 in FME, below error occurred. Help you know how it gets rid of it.DEBUG: urllib3.connectionpool Retrying (Retry(total=9, connect=None, read=None, redirect=None, status=None)) after connection broken by 'SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to get local issuer certificate (_ssl.c:1006)'))': 

Is it possible to turn off log entries like these?Workspace was last saved in FME version: FME 2025.1.3.1 (20251021 - Build 25645 - WIN64) Failed to free sufficient memory to reach the process usage limit. To improve stability and performance please increase the memory available to FME. Available memory can be increased by adding physical RAM, increasing swap space, or closing other applicationsThese just add clutter to the job reviewing process.   

I am using the Esri ArcGIS Feature Service Writer to write to ArcGIS Enterprise (11.*). The writer is set to truncate the existing data and writing the data as such goes without any problem.However, when looking at the attribute table of the Feature Service Layer I can see that some of the timestamps are wrong.To write timestamps to the existing Feature Service Layer I am converting the timestamps to Unix epoch time and multiply by 1000 to get my milliseconds.Quick example: 2025110163722 → 1762011442000When writting data to the Feature Service Layer the attribute for the Unix epoch time is set to type ‘Date’. For the majority of the data the resulting timestamps in the Feature Service Layer is correct, but e.g. in case of the example above the epoch time is interpreted as:1762011442000 → 1/14/1762, 8:53 PM.I checked if there are leading or trailing white spaces… nothing the Unix timestamps in question are just like all the others where the interpretation goes well.I have to admit that

Hello FME Community,When using the Navisworks Reader, I encounter a constant issue when trying to preserve the element GUID as a feature attribute. The GUID attribute is exposed by the reader, but some values return a string of zeros (e.g., 00000000-0000-0000-0000-000000000000) even though those same elements display a valid GUID in Navisworks. This seems to occur for elements originating from certain authoring tools, such as Tekla. The GUID is a 128-bit unique identifier assigned to every element in a Navisworks model. This value serves for element traceability.Is there a workaround for correctly extracting this value?   

I have a parent workspace and that is calling a child workspace in FME Form using a WorkspaceRunner transformer. The child workspace references deployment parameters. When the child workspace is run from the WorkspaceRunner I receive the following error: ERROR : 2: Undefined macro `APP_API_URL' dereferenced in file. APP_API_URL is the name of a deployment parameter that I have permission granted. I tried creating a published parameter in the child workspace whose default value is the deployment parameter but I get the same result. Are deployment parameters not supported with WorkspaceRunner? FME(R) 2025.2.0.0 (20251120 - Build 25810 - WIN64)

Hello,I created an FME script in which I have 10 Readers and 10 Writers. I would like to run this script in a specific order. I don’t want FME to execute everything in parallel, but instead wait for Writer A to finish before reading Reader B… How is it possible to run things sequentially?Thank you for your help

Hi All,I keep exploring Gemini’s spatial vision capabilities. Here is another example — a simple geology map of isolines with lots of hand-written labels on them. Can Gemini read these labels? The image "as is" is too big for AI, so FME has to do some work first.If I resample the image to AI-suitable sizes, the labels will be 3-4 pixels high, then even a human won’t be able to read them. Tiling is the only way to preserve the label pixels. I tile the raster into 1024×1024 chunks — the size Gemini likes — and send them to the AI. But I don't ask it to read the labels yet because the results weren’t great — I’ve got a lot of misread or missed labels. Instead I ask for the pixel coordinates of each label, which I turn into points, then buffer them into tiny clippers — each one just big enough to fit a single label. I can pack a few hundred of these tiny rasters into a single request, which, for this sheet, was a very reasonable 370 KB. I ask for text and rotation in the response, and sinc

Has anyone else run into issues with how things are displayed in FME Flow 2025.2.1 Examples: Engine Assignment Rules - we have two hosts which differ in name by suffix only. The way engines are displayed on the Engine Assignment Rules tab means you can’t quickly tell which engines are assigned as the critical bit is displayed as … (the full names are available on mouseover) The hostnames displayed in No proxy also have their urls partially replaced with …. so there appears to be no way to actually check via the user interface what values are entered here. In 2024.1 these values were displayed in full 

I am really stuck on trying to cut some labels that overflow my frame when using the PDFPageFormatter. I have a bounding box which is used as the clipper extent for my data. It clips my lines, my points, but not my text labels. I guess that has to do with the fact that the anchor point is inside the frame, while the labels are too long and go over the clipping box, and don’t have real geometry. I have tried TextStroker - that does cut my labels, but they are not keeping the symbology I added + in a PDF, they are no longer selectable or searchable (I need them to be). I also tried buffering, but that will innevitably also discard labels that are supposed to be in the frame. In the PDFPageFormatter, I also set the “Clip Input Features” = Yes. I have had the same problem in FME 2025.2.3.0, FME 2026.1, and now in FME(R) 2026.2.0.0 20260401 - Build 26291. Updating did not help.Even if I tried to mask the overflowing labels by creating a thick white border around the map, the problem would r

We have an automation that is triggered daily with a CRON expression which runs 4 workspaces. The first 3 workspaces are run in parallel and the fourth runs on successful completion of one of the workspaces. Last night, two events appear to have been triggered at the scheduled time and so each workspace was run twice. Has anyone ever come across anything similar? I can’t see any obvious errors in the logs

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

Hello, In FME Form, I am trying to generate a line from 3 parameters: lon/lat (WGS 84) length geographic orientation (from geographic north, in degrees)I have tried several ways to build this line (2DDirectionExtender, VertexCreator + Offsetter (tested polar coordinates or spherical coordinates), VertexCreator + Rotator)Always the same result, when I measure the angle from geographic north, there is a difference for instance, with my input:lon/lat : -4.49027778, 48.02000000 length : 0.002 orientation : 100.478°In both methods, FME gives me this result:When I calculate the bearing from start point to generated end point, it gives me the same result 105.411° (same with online bearing calculators using coords)Any idea on what could be wrong? Thank you

Hi all.I’m experimenting with calling WFS services with custom filtering expressions, including spatial filtering.According to the filtering documentation, spatial filtering is possible with GML, but it doesn’t seem to work in FME ?The geometry column is present but has no value in the output from FeatureReader, and FeatureReader has its own spatial filtering parameter separate from the “normal” filtering parameter (using <Filter/>)Am I correct in assuming, that FME effectively prohibits any spatial filtering via the “normal” filtering parameter, and requires you to always use the special FeatureReader spatial filtering parameter ?And maybe this is neccesitated because FeatureReader removes the WFS geometry column values ?Thanks for any insights.

Hi,I’m using FME Flow 2025.2.4.I have an FME Flow Automation which runs 4 workspaces. Each workspace takes an email address parameter (which will be the same value for each workspace).I would like to use the same Automation to run on a bi-weekly schedule but also allow it to be run on demand via an Automation App, so I have 2 triggers: Schedule and Manual When the Automation is run on Schedule it should pass a pre-defined email address to the workspaces.When the Automation is run manually via the Automation App the user needs to be able to provide an email address at runtime.Is this possible? Or do I need to create 2 separate Automations?I know I can create a manual parameter that gets passed from the manual trigger to the downstream workspaces but if I configure the workspaces to use this value it won’t exist when the Automation is run on schedule.Similarly, if I use an Automation Parameter for the workspaces when run on a schedule I can’t specify the value at runtime for the manual t