Recently active posts

Hi FME Folks,I’m working with a georeferenced PDF that contains several annotations/marked-up text. I also have an existing point shapefile/point feature class.My requirement is to:Read the georeferenced PDF in FME. Extract the annotation text. Get the location/coordinates of each annotation. Transfer the extracted annotation text to the corresponding point feature in the shapefile. Write the annotation text into an attribute field of the point feature class.Has anyone implemented a similar workflow in FME?I would appreciate any suggestions on the appropriate FME reader/transformers or the best approach to extract both the annotation text and its spatial location from a georeferenced PDF.Thanks in advance for your suggestions!Anand 

I have been using FME2026.2 -26333 - for all my current projects which includes analysing larger datasets (2-5mil records).  These aren't really that large.I have found when building the analysis with data cached FME can be highly unresponsive and lag when trying to modify the existing transformation.  Adding a new transformer, modify an existing transformer, even moving objects on the canvas.  The system will lag and can often crash.My laptop is the highest spec our company supports - Dell Precision 7680, 1Tb HD, 6gb GPU, 32gb RAM.  Even clicking too quickly after the transformation is run for that transformer can crash FME.   Surely I’m not the only person with this issue?  Stability in this version seems unbelievably poor which makes me wonder if this is known or overcome somehow.

FME Hub user daveatsafe just uploaded a new fme_project to the FME Hub.OGC WFS Service - Data Virtualization APIWould you like to know more? Click here to find out more details!

I’m trying to figure out how to add new attribute and calculate a specific value.I have a Survey123 survey that submits records to ArcGIS Online. Each survey contains one location, and one or more inspections (this is an example). In ArcGIS, this is stored in two tables with a one-to-many relationship. Each location has a field with a unique ID and each inspection has a field with the inspection number literally 1, 2, 3, and so on. Records in the two tables look like this.Locations table Location A. Location B. Location C. Location D.  Inspections table A. Inspection 1. B. Inspection 1.  B. Inspection 2.  C. Inspection 1. C. Inspection 2. C. Inspection 3. D. Inspection 1.  In FME Form, I join the tables so the records look like this. Location A. Inspection 1. Location B. Inspection 1.  Location B. Inspection 2.  Location C. Inspection 1. Location C. Inspection 2. Location C.

I am using FME Flow 2026.1.1. The trigger for the automation I created is Resource of Network Directory (updated). I have a folder that FME Flow can read/write to/from. This is the Directory to Watch. This folder is in Resources.Events to Watch for is set to CREATE.The Poll Interval is 1 minutes. The automation is supposed to trigger when a file is added to the folder. But it is not triggering. Is there something else I need to do when using this type of trigger or maybe another trigger? I tried setting the Events to Watch for to CREATE, MODIFY, DELETE and the automation still did not trigger. Any ideas on how to get a Directory Watch to trigger when a file is added to a folder? 

I have created a very simple workspace with a creator which creates a line and writes it to a GeoPackage using a FeatureWriter.The line is 2D, no measures, but the geometry type in the resulting GeoPackage is reported by ogrinfo as “3D Measured Multi Curve”.I would expect the result to be a 2D LineString instead - or maybe just LineString. As seen in the image I have exported the geometry to WKT and it indeed reports it as “LINESTRING (400000 6040000,900000 6400000)”.Is this the expected behaviour and is the FeatureWriter geometry type detection headed towards the broadest category for data instead of a more narrow approach?The test has been done using FME Form 2026.2 (26333) on Windows.

I am working with FME Flow 2025.2.4I have an automation with several Workspace Actions. Parameters are passed between the workspaces using JSON automation parameters.One of the Workspace Actions needs to be dynamic, so I pass the workspace name through a string automation parameter and the remaining parameters through a JSON automation parameter.Everything works correctly when I use only standard Workspace Actions. However, as soon as I replace one of them with a Dynamic Workspace Action, the JSON can no longer be parsed inside the workspace. It appears that FME Flow automatically deserializes the JSON parameter before it reaches the workspace.As a result, the value is no longer a valid JSON string, and transformers such as JSONExtractor or JSONFlattener fail when trying to parse it.For example, a parameter that arrives as:JSON{"umgebung": "tst","parameters": {"port": 54322}}is transformed into something like:Plain Text{ umgebung : tst, parameters : { port: 54322 } } which is no longer

Hi FME Community,We are currently exploring the possibility of integrating a VUE file reader with FME and would like to understand whether there is interest in this capability within the community.The VUE reader we have developed can read 3D model data associated with Hexagon Smart 3D / SmartPlant, including:3D geometry Object properties and attributes Model hierarchy / object structure VUE and related MDB2 dataOne of the main workflows we are considering is:Hexagon Smart 3D → VUE → FME → IFC / other formatsIn projects using Smart 3D, it can be difficult to transfer both the 3D geometry and the associated engineering properties into open or downstream formats.A VUE Reader in FME could potentially enable workflows such as:VUE → IFC VUE → databases VUE → other 3D formats Extraction and transformation of Smart 3D object properties Integration of Smart 3D model information with other AEC / engineering systemsWe already have a working and production-tested VUE reader capable of extracting g

Hi everyone,I’ve been noticing that when i connect to AGOL feature service to read a layer with over 1m features, it only reads up to 1m and ignores the rest. I’ve been improvising with “ArcGISOnlinefeatureGetter” transformer to read above 1m features.What could be the cause please, is it my setting?i’m currently on 2026.1