Recently active posts

Hi all! It was a big hit last year, so we're bringing it back! This week we're playing This or That — pick your favourites and drop them in the comments below. 🎉This week's Question of the Week: This or That!Tester or TestFilter Beach or Mountains Dark Mode or Light Mode Morning Person or Night OwlNo wrong answers — but we do want receipts! 🧾 Tell us your picks and feel free to defend your choices in the comments!💡 New to the Question of the Week? Each week, we post a simple but thought-provoking question. It might be about your FME journey, the power of spatial data, FME innovation, or even a little something personal like this one.Every answer you share earns you an entry in our monthly draw for exclusive Safe swag (a $50 value) — plus points toward community badges!🗓️ Answer all of this month's Questions of the Week by May 31st at 5:00 PM PST to be entered into the draw.🎖️ Answer your first question to earn the Socializer (Ice Breaker) badge — and keep it up to reach the Social

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

FME Hub user hydroflynn just uploaded a new transformer to the FME Hub.FME currently calculates the numerical week of the year based on what day the first of January lands on. This means that if the first of January is on any day other than a Monday, the first week is considered week '00'. This model determines what day of the week January 1st is of the current year, and determines if a +1 should be added to the weekly count so that the first week is always '01'.Would you like to know more? Click here to find out more details!

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

FME Hub user dmitribagh just uploaded a new transformer to the FME Hub.Creates vector point labels using Mapnik as a placement engine. PointLabeller positions labels around input points using collision-aware placement, then extracts the resulting placements as true vector geometry — fully styleable, exportable to any format, and free of overlap.Unlike LabelPointReplacer, which generates label geometry from a fixed text-and-anchor calculation, PointLabeller delegates placement to Mapnik and recovers vector positions from the rendered output. The result is professional cartographic placement with directional priority, automatic font size reduction when space is tight, and clean fallback behavior for points that cannot be placed.Useful for any pipeline that needs vector text geometry rather than rendered pixels: print maps, PDF atlases, GIS deliverables with editable labels, and downstream processes that consume label position as data.How does it workPointLabeller runs a four-stage pipeli

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. 

I am using the “StringReplacer” transformer to replace commas with line breaks.My attribute value looks like this:ANGLE: von 115.65130615 auf 116,ident: von --- auf ON,ADRESSCODE: von 6 aufI tried replacing , with \n, but it does not create a new line.How can I correctly insert line breaks in FME? 

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)?

Hi FME’ers,Recently I wanted to set up FME Flow to receive notifications from a notification service. My initial thought was to use an Automation with a Webhook trigger. Unfortunately this didn't work, because I couldn't register the Webhook URL in the external notification service, because it resulted in a validation error. After further investigation, it turned out that the notification service was set up using the Guidelines for NL-GOV profile CloudEvents 1.0. In 3.1.3 Abuse protection it's indicated thatThe validation request uses the HTTP OPTIONS methodFor this purpose, I thought about using the new Data Virtualization functionality of FME Flow, and found this article Webhook Verification Using Data Virtualization that looks very promising for my usecase. When I had a further look though, it seemed to me that the the HTTP OPTIONS method isn't supported for Data Virtualization endPoints (it appears that only GET, POST, PUT and DELETE are supported).See also this page on the Web Use

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 !

Hello there FME community! I am working as an external consult with the GIS-team at a company where I have a shared responsibility of the FME environment. We are managing about 200 workspaces, each running more or less every day on Flow moving data around and generating reports.Every second year we upgrade the FME instances, setting up new virtual machines for FME Form, installing new FME Flow instances and upgrading all the workspaces. This takes a long time, as we have to open all workspaces, save them in the new version and then test that they behave like before. While this works for us and the customer is pleased, I really believe that the process could be more efficient. Are you in a similar situation? How are you approaching the upgrade? Are you upgrading the FME environment in a similar way, or do you have a more efficient approach?  Best regards,Jacques de Flon Current situation (AI generated). 

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

We are implementing a CI/CD pipeline for FME Flow using an Azure YAML pipeline. When exporting an FME project from DEV with deployment parameters enabled under Advanced Options, those parameters overwrite the values in ACC and PRD during deployment. If the same project is imported manually, this issue does not occur.Is this a known bug in the FME Flow API? Or is there a recommended way to prevent deployment parameters from being overwritten during automated deployments?Additional details:If all advanced options are manually unchecked, deployments work as expected. The token used for the pipeline requires full permissions (fmesuperuser); otherwise, roles cannot be deployed. Restricting permissions or deployment parameter rights results in nothing being deployed.FME Flow version we have is 2024.1.2Any insights or best practices would be appreciated!