Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
Make use of PlantText UML editor or short PlantUML to generate diagrams that can help the reader of a workbench to understand the flow. To be used in FME Desktop for workbenches. A hierarchical view of custom transformers, bookmarks and readers and writers etcetera, can quickly give an overview of the workbench as an UML diagram.
It would be helpful to get logged information about the quality of the individual control vectors in the AffineWarper or to get exact information about their residuals (in order to delete or replace one or more control vectors with a negative impact on the result)
I am using FME 2022.1.3.0 (20220928 - Build 22630 - WIN64).I like that the log file now includes the transformer name of the transformer that is running, and even names it when running parallel processing. Now I'm wondering if it would be possible to dynamically update the Transformer name so that it would include which parallel processing group is calling it. If I could reference the Group By parameter in the transformer name, then it would include the information that would make it easier to debug errors. It is not always easy to count and figure out which subprocess is running.
Visual preview/inspector seems to automatically reproject the data, thus making the data appear as if it overlays, however the transformers don't see it that way. I spent a couple hours trying to figure out why the segments were appearing overlaid in visual preview, when the results (in my case I was using a lineonlineoverlayer) was not showing the same thing.
Although Three.js is nice (created using the JSONTemplater), it's more "ad hoc" than glTF, which has mature specifications and is actually designed to be a runtime 3D asset delivery format. Furthermore, glTF is supported by an increasing number of WebGL viewers, like Three and Cesium.I am about to create my own Writer for it, but I'd rather have FME deal with it of course :)
I know that it is intended for the SQL Executor to wait for the SQL result before moving on in a workspace, but in the case where I want to send a statement to refresh materialised views or trigger a function in Postgres, I only require it to wait 20 seconds or so to ensure there is no immediate error (like any missing dependent objects). Being deployed on FME Server, I do not want the workspace using up an engine for 2 hours while the database does it's thing. So an "Advanced" section with a tick box to tell it not to wait for the result, and an integer value for seconds to wait before moving on if a result is not returned in that time.
It would be nice have auto-layout work on selected objects by default, and if selected object is a bookmark only objects within the bookmark, and if nothing is selected then the whole workspace.Why? The auto-layout feature is generally only useful in simple workspaces. The larger and more complex the canvas gets the more using it just makes for more post-auto fixing up. However it's the complex workspaces that most need it.
When an existing table schema is read containing a primary key the primary key is identified in the list of features.This would be useful in dynamically reading tables with different primary key attribute names.Something like Property: attribute{17}.fme_index; Value: PRIMARY KEYThank you.
In the parameters of the oData Reader a Web Connection can be specified for authentication. But there is no Web Service for oData Services. HTTP authentication can be used, but there are options for oData, for example using an apikey
The option to send header options in the oData reader is missing. Similar to the headers option in HTTPCaller, authentication to an oData service can be done via an apikey. This option is missing in the oData Reader
Simple: Remove all attributes for which all rows are empty/null/missing/...Better: List all attributes for which all rows are empty and allow selection of which ones to remove.This would really help to reduce the number of columns when normalizing data sets from various sources. My continuous need is for normalizing addresses from various county, city and open sources.When you have a couple hundred thousand rows, it is hard to figure out which attributes actually add value via the AttributeRemover or AttributeKeeper.
It would be really useful to get FTPCaller to rename a remote file.Common task is to rename the remote file by adding a .DONE file extension once FTP Download is complete.I'm of course using different methods and preferred one is PowerShell.
It would be nice if the 2DGridAccumulator had the standard options for propagating attributes.Accumulation ModeUse Attributes From One Feature, Merge Incoming Attributes, Drop Incoming Attributes (current behaviour)Generate ListAll AttributesSelected Attributes
FME server currently supports importing and authenticating Azure Active Direcory (AAD) users. Would it be possible to also authenticate AAD guest users?
It would be nice if the ListExploder could work with irregular lists instead of rejecting them with fme_rejection_code' has value `MISSING_PARAMETER_LIST'.An irregular list is a list that either does not start at 0 or does not have continuous indexes.ex. _list{1}_list{2}_list{3}or _list{0}_list{2}_list{3}_list{5}
I'd like it to be easier to find a certain workspace published on the FME Server. There's a search function on the fmeserver/repositories, but it does not search the workspaces, just the repo name... Please extend the search to include all the containing workspace names too.
Currently FME can read 12dxml file format (.12dxml), but cannot directly read the zipped version of this file (.12dxmlz).This is similar to the difference between a Google Earth KML file and a KMZ file. A current work around is the routine can have a user parameter for file name, it starts with a creator, uses the "ZipExtractorAnyExtension" from FME hub to extract the file, then the file path can be used in a feature reader with the format set to 12dxml. There are two issues with the workaround - it requires a user parameter to be setup within the routine, and it requires unzipping the file contents to a folder prior to being usable in the routine. 12dxml files can be large compared to 12dxmlz (7mb vs 206kb) so file size is significant, especially when 12dxmlz files get into 100mb's+.That is why a dedicated 12dxmlz reader would be great.
The SurfaceFootprintReplacer is an excellent tool, it produces nice clean results and is a nice clean result especially when compared to the 2DForcer. But it would be really nice to have the option to keep the holes instead of producing more of a dissolved result.
In the AEC industry the use of RTEXT in AutoCAD is widely used to print information on the drawings. You can read more about the command and entity here: https://knowledge.autodesk.com/support/autocad/learn-explore/caas/CloudHelp/cloudhelp/2021/ENU/AutoCAD-Core/files/GUID-28585C1C-65B8-41E0-90A3-7C043123EF7A-htm.htmlThe RTEXT command in AutoCAD creates a RTEXT entitiy that can:Show the content in a external txt fileShow the file name and path to the current DWG-fileShow the current date and timeShow the list of the external references (xrefs) linked in the current DWG-fileRight now, FME doesn't support the RTEXT entities. The "Autodesk AutoCAD DWG/DXF" reader just inform that the AutoCAD Reader: Entity type of 'RText' found, but not supported. Skipping entityThe "Autodesk Autodesk AutoCAD RealDWG DWG/DXF" reader reads the RTEXT entities as proxy entities but with no attribute information that these entities are RTEXT entities. (if you have the parameter "Read Proxy Entity Graphics" turned on you get a bounding box and two crossing lines as geometries for each RTEXT entity)As FME is widely used to make the quality control for these DWG-files we really need support for reading RTEXT entities.
It would be nice if we could apply varying 3d affine transformation and not just 2d. Like the 3DAffiner but with parameters from a set of vectors, if possible with rubbersheeting approach.
It seems that XYZ Tiles cannot be read by FME Desktop or be added as a background to the FME Data Inspector. URL example of such service: https://tile.openstreetmap.org/{z}/{x}/{y}.pngThe url works fine in QGIS: Thanks in advance!Olivier
With a workspace that includes many transformers, the ability to remember the map's current zoom and centre coordinates.The current behaviour is unpredictable. Clicking a magnifying glass displays the map and the current selection. Clicking on a different magnifying glass in the same transformer moves the map to a new location. The user is forced to pan and zoom back to the area of interest.The desire is to see the current status of any geometry at any point in the workspace.Background info via: https://community.safe.com/s/question/0D54Q00009q8A6dSAE/how-do-i-lock-the-bounding-box-of-the-graphics-view
I am working on a support case where a client is trying to convert a mapinfo TAB file to a shapefile (easy enough) but wishes to also retain the symbology information. It appears that the functionality to create a Esri .lyr file to pair with a shapefile/feature class does not currently exist. A "EsriStyler" transformer/Layer File writer would be an excellent addition.
Apache Ignite is a distributed database management system for high-performance computing with in-memory speed. Posting this idea to gauge interest in the development of a formal format. Note: FME can likely connect to this database already via the JDBC Reader/Writer as Ignite has a driver that you can download here: https://ignite.apache.org/docs/latest/SQL/JDBC/jdbc-driverFME's JDBC Reader/Writer documentation: https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/jdbc/jdbc.htm
Hi,I really like the FeatureWriter Transformer but I think there are two important features that are currently missing:Update the feature types (as it is possible for normal writers)Allow to expand the attribute list of the feature types to check the attribute mappingKind regards,Dennis
In-depth courses for all FME skill levels.
Explore our extensive collection of how-to guides and tutorials.
Log an issue with us. Our support team is ready to help.
