Recently active posts

I’m using FMW Reader to read and analyze FME workspaces, and I have a question about custom transformers.There is an attribute called Custom Parent Name. When this field exists, it shows me the connection to the custom transformer inside it. However, how can I determine whether that specific custom transformer is enabled or disabled in the main FME workspace?For example, suppose an FME workspace contains multiple instances of the same custom transformer, such as: LineDivider LineDivider_2 LineDivider_3 The Custom Parent Name attribute may contain only LineDivider, without the _2 or _3 suffix.In this case, how can I distinguish which specific instance of the custom transformer the connection belongs to?More specifically, how can I reliably identify: The exact instance of the custom transformer in the main workspace. Whether that specific instance is enabled or disabled. The relationship between the transformer instance and its Custom Parent Name, especially when multiple instanc

We are working through the setup of a service user for a project, intended to only be able to create and run its own Data Virtualization APIs and nothing else.  The aim is to avoid excessive permissions. I have been searching for a list of recommended or minimum permissions but have not yet established that, so I’m putting the question out here.We have granted:Create/manage for data virtualization Run jobs Access Resources/DataWe’re looking into other permissions.We’ll work through it but I am definitely thinking that documentation of this would be handy from the Safe point of view to save time, if possible.  Possibly as an addition to https://support.safe.com/hc/en-us/articles/36098228739469-Secure-Data-Virtualization-Endpoints-with-Authentication 

HelloWe have FME Server v2022.2.2 installed on Windows 2022 server and need to apply manual patch for security vulnerability, as per FME alert / articlehttps://support.safe.com/hc/en-us/articles/31265482270349-Security-Update-FME-Flow-Privilege-Escalation-Vulnerability#h_01JB2AENHZEBG9VCCFBJFTWX1RThe instructions include a note:*When moving/overwriting files, please ensure that the original permissions of the file being overwritten are preserved, this is ./opt/fmeflow.How best to do this?  We were planning on a simple copy and paste of the files themselves to the various directories, however this may overwrite existing permissions.  What method of copy & replace files is recommended, it would be helpful if the windows command or powershell script could be provided to assist Please adviseThanks 

I'd like to read a DGN file, which contains a terrain model. In version 2025.1.2 it is being read as igds_polygon_collection. The fme_Geometry is “fme_undifined” and the fme_type is “fme_no_geom”.When using a Civil 3D file, it can read a surface model, which is the same principle as the terrain model in a DGN. The terrain model is created in OpenRoads.Or is another option available to read the terrain model directly from a DGN file without converting it to another fileformat or element type?  

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? 

As per this post last year, Salesforce is retiring the SOAP API login().  Any news from FME on when the Salesforce readers and writers will be updated?  

I want to calculate upstream and downstream distances along river polylines between barrier points. I’ve got as far as generating a topologically correct river network divided at barrier locations, river intersections and junctions complete with network_id. I’m stuck on the next steps! The main challenge is what to do upstream when a river branches out. Any help would be greatly appreciated! Process so far 

How do i fix this error:  

Hi everyone, I am having the strangest issue with FME Flow. I have a Form that process some data and then creates a pdf file. It works just fine locally with a UNC path. My issue is Flow, when I publish it, i get a permission denied, but the strange thing is it has no issue writing .txt file to that folder and to make it even more strange, it worked correctly two times out of the 50 tries I did changing things. I have even tried adding this UNC path as a resource in Flow and same result. Has anyone had such issues before? Any suggestions? 

I have a QGIS .model3 file that uses PostgreSQL tables as its inputs and writes to other PostgreSQL tables as its outputs. I am having trouble getting this model to run as part of an FME Workbench.What I have done so far:Copied the tool parameters from the QGIS graphical interface (Advanced > Copy as qgis_process command) Edited the command so that “--” only appears in front of the first parameter Added “” around each PostgreSQL parameter as they contain spaces and special characters and were causing Invalid parameter errors in Windows command prompt Thanks to these changes, running the tool with qgis_process in Windows command prompt no longer throws invalid parameter errorsThe tool fails silently through the SystemCaller transformer in FME.In Windows command prompt, the parameters now seem to be read properly but I am now getting “File could not be found” for PostgreSQL addresses.Still in command prompt, dialing psql first with my database credentials makes it say \PROGRA~1 is an

Apparently since fixing this problem https://support.safe.com/hc/en-us/articles/25407612007949-Known-Issue-FME-Flow-Apache-Tomcat-Vulnerability-with-X-Frame-Options-headerIn FME Flow 2025.1, embedding FME Flow content to other pages is disabled entirely by default.  Is there any chance to allow embedding from known sources or is embedding considered so risky that this would not be even considered? 

FME Hub user takashi just uploaded a new transformer to the FME Hub.Replaces geometry of input feature with a rectangular polygon or a point which represents the location of Japanese standard mesh code stored in an attribute. This transformer determines mesh type automatically based on format of the mesh code. The mesh type (a number) will be stored in an attribute whose name was specified to the "Mesh Type Attribute" parameter. Mesh Type | Description | Mesh Code Format 1 | Primary Standard Mesh | AABB 2 | Secondary Standard Mesh | AABB<delim>CD 3 | Tertiary Standard Mesh | AABB<delim>CD<delim>EF 4 | 1/2 Subdivided Mesh | AABB<delim>CD<delim>EF<delim>G 5 | 1/4 Subdivided Mesh | AABB<delim>CD<delim>EF<delim>G<delim>H 6 | 1/8 Subdivided Mesh | AABB<delim>CD<delim>EF<delim>G<delim>H<delim>I 10 | 1/10 Subdivided Mesh | AABB<delim>CD<delim>EF<delim>XY or AABB<delim>CD<delim&

FME Hub user takashi just uploaded a new transformer to the FME Hub.Replaces the input features with a grid of polygons or points based on the Japanese geographic mesh dividing standard. Resulting polygons or points will cover all the input features, and the output features will have a new attribute storing its mesh code. Notes: This transformer is valid only for a geographic data on Japanese area with LL coordinate system. Unavoidable slight computational errors caused by calculation for floating point numbers may occur in the resulting coordinate values. Consider applying the CoordinateRounder or something similar operations to absorb such errors if necessary. This transformer supports these Japanese standard grid types. - Primary Standard Mesh - spacing (W x H): 3600sec. x 2400sec., mesh code format: "AABB" - Secondary Standard Mesh - spacing (W x H): 450sec. x 300sec., mesh code format: "AABB-CD" - Tertiary Standard Mesh - spacing (W x H): 45sec. x 30sec., mesh code format: "AABB-C

FME Hub user takashi just uploaded a new transformer to the FME Hub.Extracts Japanese Standard Mesh Code of the mesh containing a representative location (First Vertex, Center of Bounding Box, or Center of Gravity) of the input feature.You can select the representative location with "Location to Extract Mesh Code" parameter. If the input feature doesn't have coordinates, it will be output from the <Rejected> port. Notes: This transformer is valid only for a geographic data on Japanese area with LL coordinate system. This transformer rounds the coordinate values into milliseconds when computing mesh code. So an computational error may not be avoided if the coordinate is very close to a mesh boundary. This transformer supports these Japanese standard mesh types. Primary Standard Mesh - spacing (W x H): 3600sec. x 2400sec., mesh code format: "AABB" Secondary Standard Mesh - spacing (W x H): 450sec. x 300sec., mesh code format: "AABB-CD" Tertiary Standard Mesh - spacing (W x H): 45se

I was checking through the list of possible job status for an asynchronous (Data Virtualization) workflow I have going and didn’t find a definition for ‘complete’, or a comparison of that value to ‘success’.  I was referring to the REST API V4 documentation here: https://support.safe.com/hc/en-us/articles/38420159907213-Submitting-a-Job-through-the-FME-Flow-REST-API-V4 Would someone with familiarity around those statuses be able to clarify the meaning of ‘complete’ and how it contrasts to ‘success.  AI relented from guessing and admitted it didn’t know. An update to this is that ‘complete’ is not listed in the OpenAPI spec for the FME Flow REST API V4, so at this stage is the documentation incorrect?https://docs.safe.com/fme/html/fmeapiv4/docs/schema/static.json "status": { "type": "string", "description": "The current status of this job", "enum": [ "queued", "running", "success", "failure",