Using transformers to modify data.
Recently active
I'm trying to use the AreaGapAndOverlapCleaner to fill gaps in my polygons. This works fine without grouping, but as soon grouping is enabled, the donuts and other slivers in the polygons are not filled any more. See screenshots below. The tolerance in both situations is 25cm. The only changed setting is the grouping. I used the AreaGapAndOverlapCleaner for many years now and never experienced this before. In most situations I used ‘automatic’ as tolerance.I'm using Form 2026.2. I also tried to recreate the process in 2025.2.4 and still experience the same issue. Does anyone know why the donuts and slivers are not removed when grouping is enabled? Grouping disabled: all small holes are filled (as expected) Grouping enabled: small holes and slivers still present.
Hi all,I’m trying to create points at 1 m intervals along a line, with a sequential ID starting at 2000.As shown in the screenshot below, I need the sequence to start at the south-western end of the line with ID 2000, then increase by 1 for every metre as it follows the line towards the north-east and then back towards the north-west.So essentially:Start of line = ID 2000 Next point, 1 m along the line = 2001 Next point = 2002 Continue incrementing by 1 following the actual direction/path of the lineI have tried using the DistanceChopper from the FME Hub to split the line into 1 m segments. I then calculate the X/Y coordinates of the start/end points, use a VertexCreator, and finally a Sorter based on the X coordinate.This works up to the location marked X in my screenshot. However, because the line curves back on itself in the X direction, sorting by X no longer represents the correct order along the line. What I really need is a way of ordering the generated points by their distance/
Can anyone give me some advice on getting GIS-styling symbols and polygon fills using the AutoCAD DWG writer?I’m not an AutoCAD expert but have this week been getting to grips with concepts such as blocks. With help from a colleague, we’ve managed to create a template with blocks for a range of point symbols and got my Form script to output points to a layer referencing the appropriate block name so that an appropriate symbol appears. Note: I have too many symbol types to put each on a separate layer. Is this the use of blocks to implement cartographic symbols a sound approach?The next thing I’d like to do is have some symbol fills for polygon features. e.g. trees representing woodland. What approach would be best to implement what would be a simple custom pattern fill in GIS software? I’m already aware than Form outputs simple polygons as normal, but complex ones (e.g. with holes) via sequentially named blocks. What about using custom hatches?Finally, I’d like my AutoCAD drawing to ha
Dear Feature Manipulation Experts,The GeometryPropertyExtractor is a transformer I never used before. So of course, my first experiment with it failed.I wanted to know what type of geometry the GeometryValidator spits out after having repaired them. I put in areas (polygons) and expected all output, whether repaired or not, to be areas as well. Sometimes, however this was not the case. I used the GeometryFilter to separate the areas from other geometries.In an attempt to find out what the others are, I discovered the GeometryPropertyExtractor. To see how it works, I attached it to the area-output of the GeometryFilter, expecting to find a geometryproperty (area or polygon) attached to all features. Instead, all input is rejected!As you can see in the Feature Information pane, the rejected features do have a geometry (polygon) and a type (area):As I am writing this I wonder why I did not think of simply using these FME attributes. I blame friday afternoon for that.But still I wonder: w
I have discovered a bug (and a workaround) concerning TempPathnameCreator version 1 in FME Form 2024.2.5.2.First of all, because of the Security Hardening in FME 2026.2+ and Backport Versions (in this case FME Form 2024.2.5.2) the TempPathnameCreator must be updated to version 1 in all workspaces that use this transformer (for more information see https://support.safe.com/hc/en-us/articles/49062482561421-TempPathnameCreator-in-FME-2026-2-and-backports).The bug I discovered is that in FME Form 2024.2.5.2 the attribute after 'Pathname’ is not exposed. This breaks all workspaces in FME Form 2024.2.5.2 that use the TempPathnameCreator, even after updating the transformer to version 1. The workaround is simple: add an AttributeExposer to manually expose this attribute.Edit: I notice that after manually exposing the attribute it often ends up as an extra attribute in my output. So the attibute has to be removed explicitly as well.Note: I also tested this in version 2026.3.1.1; in that versio
so, i’m trying to use Json Extractor on a response body that looks like this: { "Events": [ { "Id": "MSU_S1:GmsDevice_1_860100_12582917.Alarm.OffNormal:_alert_hdl.2._value~639301453601600000~3216~8311", "Deleted": false, "EventId": 8311, "InformationText": "", "CategoryId": 9, "CategoryDescriptor": "High", "State": "Unprocessed", "Cause": "Off Normal (OK)", "SrcPropertyId": "MSU_S1:GmsDevice_1_860100_12582917.Alarm.OffNormal:_alert_hdl.2._value", "SrcObservedPropertyId": "MSU_S1:GmsDevice_1_860100_12582917.Alarm.OffNormal:_alert_hdl.2._value", "SrcState": "Quiet", "Timer": "0001-01-01T00:00:00Z", "SrcSystemId": 2, "SrcViewName": "ManagementView", "SrcViewDescriptor": "Management View", "SrcDesignation": "ManagementView.FieldNetworks.PSS_BT.Hardware.HVACPSS01.Local_IO.PSS001100", "SrcLocation": "Project.Field Networks.PSS BT.Hardware.RM A51 PXM01(OLD MBC32).Local_IO.STATUS", "SrcName": "PSS0011
I am trying to extract some GIS data from an IFC file containing manholes, pipes and ducts. The IFC file have some small gaps at bends, like this: I’m extracting the top facing faces in the IFC and simplify to one polygon per IFC element. I still get these small gaps in my GIS data:I have tested the Generalizer with a lot of different algorithms and settings, but those that seem to be able to remove these (like the Wang algorithm) removes my Z values… Is there a way to simplify or smoothen the data to remove these while retaining the 3D area boundaries?
Good day,I have a line with a center point on it. I would like to create a polygon around this line that should intersect the last and first vertex of the line. The longer side should be 2m long (as long as the line) and parallel to the line. The shorter side should be perpendicular to the line, 1.6m long and intersecting the line halfway. How can I achieve this ?
FME Form 2026.1We use a custom coordinate system based on transverse Mercator centred on 147E and using mm units.When reprojecting polygons to the west of the central meridian the polygon gets shifted out of the correct location. When the same polygon is chopped into vertices, the result is ok. Using the same CS definition using metres instead of millimetres works for both polygons and vertices.Attached is a sample workbench with the coordinate system definitions and a sample object under test.If anyone can suggest a solution it would be greatly appreciated.
The prefetch query option seems to have been removed from the database joiner in 2026.2.1Is there a work around? I found in the past that the prefetch query drastically improved performance when I was joining to my postgresql tables. Now i don’t have that option.
Hello there,I’m a new FME user and trying to get into custom functionality via the PythonCaller transformer. I’m using VS Code as my primary code editor and I set it up in the FME Options menu.My problem is, that VSCode keeps showing me the onboarding dialogs (Login to Github Copilot, Choose theme, ...) everytime I open the PythonCallers code in the external editor.I did a little bit of digging and found out: VSCode is called by FME Form with a temporary directory. (Flag: --user-data-dir). In that directory information about how VSCode is setup is stored. Is there anyway I can get rid of this behavior and it just points to the standard user-data-dir or the option is left out completely? I did not find any option to disable this behavior in the FMEOptions, so I’m asking here now. Thanks for taking the time, Johannes
When outputting ESRI Enterprise records on FLOW 2026.2.1 via FeatureWriter with Dynamic settings and supplying ‘native_data_type’ attribute{} payload and ‘fme_format_short_name’ attribute (supplied from a FeatureReader schema port that connects the original data table) the workbench run generates masses of warnings around data-type mismatches whereby the fme_data_type is being attempted and not aligning with the target data-type:FLOW messages on data-type mismatchFollowing details from Dynamic Workflows: Destination Schema is Derived from a Schema Feature – FME Support Center on initial testing results in the above messages. I have attempted to remove the fme_data_type and force recognition of the native, without success. What is missing for the engine to honour the ‘native_data_type’ directive?Attribute output payloadThe fme_format_short_name is “SAFE.ESRI-AGOL.ARCGISFEATURESERVICE”The ‘native_data_type’ payload for each attribute is correct from the source table - it is the self-same
Hi,This concerns the Oracle Reader.When a workspace created in FME 2025.x is opened and edited in FME 2026.3, I encounter an unexpected error with Oracle Readers.We have Oracle tables that contain two SDO_GEOMETRY columns. Until now, it was possible to specify which spatial column to use directly in the Oracle Reader.This still works in FME 2026.3, but only until you click Update Reader. If a spatial column is specified in the Spatial Column option after updating the reader, the following error occurs:ORACLE Reader: 'Spatial Column' and 'Handle Multiple Spatial Columns' cannot be specified together In previous versions of FME, the Oracle Reader had an option to specify whether the table contained multiple spatial columns. This option is no longer available, so I don't understand why this error occurs.The workspace still runs if no spatial column is specified in the reader. However, in our case, the reader may select the wrong column, resulting in no usable geometry for the subsequent p
Hi,I’m using FME Workbench (2025.1.3.3) to transfer data between different databases.The workflow is as follows:Creator → FeatureReader → DatabaseQuerier → FeatureWriterThe FeatureReader reads one feature from the source database to initialize the process. The DatabaseQuerier then executes a query against the source PostgreSQL database and returns the actual data to be written. The schema attributes are passed through the workflow, and the FeatureWriter writes the resulting features to an existing table in the destination PostgreSQL database.The problem occurs when one of the source columns has the PostgreSQL bytea data type.The source and destination tables have the following relevant column:geom byteaWhen both the source and destination databases are PostgreSQL, FME does not appear to transfer this binary attribute correctly.With Bulk Insert enabled, the FeatureWriter fails with the following PostgreSQL error:ERROR: missing data for column "geom"The log also reports:Bulk copy failed
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
Hello everyone, I am having an issue when creating a PDF file as an output. I have tried this, with both “document PDF [Writer]” and “FeatureWriter”.The file I am creating has many incoming attributes, one of which is a date. My problem is, when I add this date to the file name, it exports two files for me, one without the date and one with it. The file without the date has everything in it except for the date, the file with the date, only has the date value in it. This happens not just with the date, if I add any of the other variables, they will end up creating two files for me. What am I doing wrong that is causing this? How can I troubleshoot this?
Hi everyone,Brand new to FME (ArcGIS Interoperability) - like 6 hours into it. I have a process in ArcGIS Pro that I’m trying to replicate in FME. It starts with a one to many spatial join where I also keep all target features. I have parcel data (Target) that I want to join to address points. Multple address points can sit on a single parcel (think apartments and duplexes), also 1 address point can be snapped to multple parcels (think of a property owner that also owns the adjoining lot. I am trying to create a layer : that will duplicate the parcel for every time an address intersects with it - 5 apartments on one parcel will produce 5 stacked parcels If an address is snapped on the edge of two parcels, both output parcels will inherit the attributes of the address point If a parcel has no address, it will still be included in the output.This is very simple in ArcPro with a one to many spatial join set to keep all target features But I’ve been struggling for hours trying to get
So I have a process that extracts data from a database, converts that data into a fairly complex xml, downloads a PDF from Sharepoint, and at the end it uses the ZipArchiver to add both PDF and XML to a zipfile. This works fine, except that at some point in time the XML in the zipfile is truncated. This of course results in invalid xml, so it is not accepted downstream. The file itself is fine, since I leave that in it’s original location that’s easy to check. Somewhere inside the ZipArchiver or inside the zip the XML is cut off. It does not seem to have to do with the number of characters in the xml, since it differs between various zipfiles as tohow many characters of the xml have survived. Strangely enough the PDF inside the same zipfile is fine, usually many times larger than the xml (one example has a 39.2 Mb PDF, and a 349kB xml...), so I don’t think it’s the filesize (unless 349 is too small...). Has anybody else seen this before? I’ve been looking at the Python-code inside the
Hi, I have a LAS file already normalized, ground z value = 0, and other class z = height above ground. I need to set the z value to “0” to building class. I try this workflow and it’s seem to work but when I check the LAS writer, build and ground have the 8.847607091e-10 z value.I dont know why this, but when I check property in FME, I realize that z value it’s different.In my normalized LAS the z valueBut in the output LAS I get this in z valueI tryied with PointCluidExpressionEvaluator instead remove and adder component but I get the same in Z valueAny idea why this happens?
Hi All,I’m exploring whether FME could help automate a manual process for extracting pipe diameter information from rasterised PDF drawings.The PDFs also need be georeferenced, although the raster quality is relatively poor. The aim is to extract pipe diameter annotations using OCR, create point locations from the recognised text, and then spatially associate these with the corresponding GIS pipe lines to populate the diameter attribute.I’ve tried TesseractCaller, but the results have not been sufficiently reliable so far.Has anyone successfully implemented something similar in FME? I’d be particularly interested in recommendations for OCR libraries, Python libraries, FME packages, or other approaches that perform well with low-quality engineering drawings.Below of an example of the pdf Thanks :)
Hello,with the upgrade to version 2026.1.2.0 I have run into a strange behaviour when using Excel writers.FME Workbench simply says at the end:FME was unable to finish the workspace translation due to an unexpected termination. Any data caches will be cleared because their data integrity is compromised.This is currently not much to work with. For pinpointing the cause, I deactivated all excel-writers in my workbench and it just ran fine.Has anybode experienced this with Version 2026.1.2.0?Kind regards,Ryoung
Hi everyone,I currently use FME Form 2026.2 in various large customer projects (bulk coordinate/geometry updates of GIS databases with public/municipal infrastructure), where it is critical that data quality is not degraded when processing data with FME.I read through the release notes for FME Form 2026.3 and saw that the following bug has been added to the backlog:VertexCreator: Point Inserted Into Incorrect Index [26550]If I'm interpreting this correctly, this is an existing bug in VertexCreator that has been present in earlier FME versions and was only added to the known issues list with 2026.3 - ?Due to the potentially catastrophic consequences this could have on the data quality for my customers, we would like to get more clarifications about:How the problem is triggered and if it is data-specific (maybe a particular format?) How can I detect whether this bug is affecting my conversion workflows? What workarounds are available? Is this bug new and introduced in 2026.3? Which othe
Hello,I have a task to evaluate whether it is possible to create an IMDF dataset from DWG files using FME.There is a good tutorial from Safe Software (Converting CAD Datasets to IMDF: Part 1 – FME Support Center) that uses a master drawing file with Xrefs. However, in my case I only have separate DWG files for each floor, so I cannot replicate the tutorial in exactly the same way.At the moment, I do not have access to AutoCAD and I am not a CAD expert. I have read that properly converting DWG data into the IMDF format can be quite challenging. Does anyone have experience with or examples of an FME workflow that does not use Xrefs, but instead uses separate DWG files for each floor? Or do you think that creating a valid IMDF dataset from this kind of source data is not feasible without further preparation of the DWG files?Thanks in advance!
Have a WKT csv, with lines like these two: MULTIPOLYGON (((3.751446328848148 51.09789238333794,3.7514744771186774 51.09785395106413,3.7515454118479563 51.09787454834335)),((3.7486227439488014 51.10188366613414,3.7471867226749627 51.101468672794745,3.745208081250554 51.1041693453312)));2003001POLYGON ((3.743757864908372 51.08620899834685,3.744266505912946 51.0833952986076,3.7433015994552856 51.08332946064444));2003002However, the receiving software can only handle multipolygons. So in the second line, I need to replace “POLYGON” bij “MULTIPOLYGON” (which is easy), but also the two opening round brackets “((“ need to be replaced by three opening round brackets “(((“ and the same for the closing brackets.I don’t seem to find a way of escaping the brackets. Even in regex expressions FME interprets the brackets as real brackets and not characters to look for.Can anyone help here?
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.