Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
HiWhen data is to be arranged based on ranges none of the current transformers support import or export functionality. The current transformers looked at are AttributeRangeMapper and PointCloudSplitter.Would be most valuable to have an import function to fetch ranges from an external database or lookup table. If a unique data range have been created in a workflow it would be great if the generated range could be copied, exported or saved to a csv/xlsx fileThanksandre@mmt
***Note from Migration:*** Original Title was: Data Inspector: Need ability to copy selected column definition from one table view to another We use the Data Inspector extensively for QC checks. It is very burdensome to recreate filters from one view to another (especially if there are a lot of columns). Therefore, I suggest a method from copying or replicating a filter from one view to others.I was told this was a good idea a while back. As of 2020.0.0.0 (20191105 - Build 20121, I haven't noticed an enhancement for this.
Right now we can only define token/server app permissions down to the repository folder. Would be great if we could dive deeper and be able to define access (download/read/publish/run/remove) only to a single workspace within a repository instead of the entire repository.
When working on large definitions, sometimes you need to add space in the middle of a definition. But if the workspace is large already, it's a pain and potentially dangerous to select a lot of transformers and move them to make space (sometimes you can inadvertently mess up connections etc.). I have recently started using another visual scripting application called Grasshopper (by McNeel) which drives geometry in the very popular Rhinocerous, and came across a great feature that tackles this very issue very elegantly (see below). So I thought to post it here and suggest it for FME! You can click and drag as shown below to move the contents of the canvas and open up space without having to make any selection and move the actual components/transformers etc. Works both horizontally and vertically...really nice UI enhancement.
Please support reading and writing Esri representations geometry. A lot of effort has gone into creating and maintaining representations at out utility. https://community.safe.com/s/idea/0874Q000000cTwAQAU/detail
Reader / Writer for EagleView Pictometry would be awesome (to update the uploaded .shp files that are used to overlay on their imagery)
We use field Aliases in our SDE Geodatabase and it would be nice to be able to read them and then write them to Oracle as field comments. That way we can have them show up in a metadata report. Currently we have to manually copy them between ArcCatelog and Toad
We have a common shared drive with common custom transformers. It would be great to see this Categorized in a single "group" since they are usually categorized in the correct category (like Coordinates for instance)
For instance the AttributeExposer (and all embedded exposers in other transformers) require you to enter data one row at a time or import a file to populate.Look at the workflow for an AttributeExposer.Current process, copy attributes from FME inspector -> open Excel -> paste attributes -> save file -> import/navigate to file -> mess with settings -> import files -> repeat if it is wrong.If text boxes were a standard feature on basically all transformers it would be, copy attributes from FME inspector -> paste into transformer text box. That is two steps vs 8, but I'd argue it is much more like a >10x saving in time than a 4x saving.But this is true for many more transformers, Testers require you to click on multiple columns per row to create rules.Even if all that could be exposed was the current user input portion of the XML of the transformer in the FMW file I would find it much more appealing to dump raw text lists into something like Notepad++ and coerce it into the format that FME wanted then paste it into a text box rather than saving files to import. Or in the case of things like Testers simply not having any option to copy and paste multiple rows of rules.
It would be great to have a data partition tool or an addition to sampler. This would be very useful especially for big data.
The RasterDEMGenerator currently includes 2 inputs: Points/LinesBreaklines.I find I almost always follow this with a Clipper to clip the DEM to the shape of my input data - typically terrestrial LiDAR along a road or rail corridor; using a polygon (hull) to remove unwanted interpolated cells. As the RasterDEMGenerator is interpolating all those cells outside the pointcloud it is very taxing on performance. A built-in clipper or another way of tiling the DEM generation process would vastly improve performance.
With the 1.17 Caves and Cliffs update the world height and depth has changed. Can the reader/writer support this change please.Thanks
Why is there not a tunnel transformer? It would save time being able to create a tunnel and allow you to label the output and input in 1 parameter box rather than having to create two junctions and then label both separately.
It would be great if there was an option to remove all permissions from a user or role. "Clear Permissions".E g after loading a permissive template it becomes very tedious unchecking every single permission checkbox manually if you want to load a more restrictive template instead.
There is a frequent need to expose full filename with its extension. It is possible to extract this from fme_dataset but it would be more efficient to have this info existing automatically in format parameters.Currently the fme_basename only stores filename without extension and the fme_dataset stores full path.
Note:The suggested idea Is created as a poc and are used with combinations of fme transformers and it works fast. To summarize1. Create temp table2. Bulk insert into temp table3. SQL queries between temp table and other tables within the server.4. remove temp table Problem Statement:When FME handles large datasets and performs joins with features from FME flow with a databaes table, particularly with databases containing many attributes, the process can become time-consuming. This is due to the row-by-row attribute comparison FME typically employs, and the potential communication overhead when interacting with the database.Current State:FME handles joins within its own environment. While functional, this approach can lead to performance bottlenecks when dealing with substantial data volumes and complex join conditions, especially when interacting with external databases. This one by one comparision applies for both the existing databas joiner and sql executor ( SQL executor is fast if all the data is within the sql server, not if you want to join data from the fme flow with sql, then its one by one)Proposed Feature:I propose the introduction of a new transformer, proposed name: the " Large Dataset Join ", which would seamlessly integrate with various database systems. This transformer would leverage the database's native capabilities for handling joins, leading to significant performance.Here's how it would work:Bulk Insert into Temporary Table: The transformer would efficiently transfer large datasets from FME to a temporary table within the target database using bulk insert operations. This feature already exist in FME and can be re-used. Database-Side Join: The join operation itself would be executed directly within the database, utilizing the temporary table and the target table. Users would have the flexibility to specify join conditions using either SQL queries or a visual interface. Retrieve Joined Data: Only the necessary joined data would be retrieved back into FME, minimizing data transfer overhead. Automatic Temporary Table Management: The transformer would handle the creation and cleanup of the temporary table, streamlining the process for the user.Key Benefits:Significant performance improvement for large dataset joins, particularly with databases containing many attributes. Reduced processing burden on FME, freeing up resources for other tasks. Streamlined workflow for leveraging the database's optimized join capabilities.
FME Server should have a system event which triggers when a FME Engine can't be started.For example two FME Engines are licensed and also configured to be used but only one FME Engine is started and the other one is down for more than 10 minutes.So the administrator can be notified and investigate the reason.
Currently, the little triangle arrows for connecting reader/writer/transformers are quite small. It requires a high level of accuracy to move the cursor to the arrow to make connections. Please consider making them bigger so it's easier to use them for making connections on the canvas.
Working with FME Desktop 2018It is hard to differentiate between disabled and enabled tunnels. It would be great to better visualize when a tunnel is disabled or enabled.Use for example a forbidden or stop sign / icon, placed over or under the tunnel entrance and tunnel exit...
I went to assign a job queue to a Server App in FME Server 2021.0 and was shocked to find it is not available! Why not? It should be :) Really, I mean it.
Amazon EventBridge allows you to subscribe to events from AWS services, SaaS applications and even your own applications. By adding support for this service, it would allow you to build event-driven workflows on FME Server that could respond to AWS events. Here are some example events EventBridge supports:Amazon EC2 generates an event when the state of an EC2 instance changes from pending to runningAmazon EC2 Auto Scaling generates events when it launches or terminates instances.AWS CloudTrail publishes events when you make API calls.The Saas applications supported are listed here. Several key services include:DatadogMongoDBNew RelicPagerdutyZendesk
***Note from Migration:*** Original Title was: Right Click on supported file to just bring up the add reader to blank workspace option I find a lot of the time I want to do something really quick on a file in FME. For example calculate the area or some other minor task.I often use the Right-Click inspect option to look at a file, however, the other two: Quick Translator and Transform I really don't use.I think having the option to just being up the add reader dialog on a blank canvas would be pretty handy shortcut. Would save quite a few clicks.(Just a rant really - but I'd be interested to see if others would also want this too)
It would be really nice and useful to have Summary Annotations showing only selected paramaters/information instead of having all the parameters from a transformer, but still be updated when a change is made on selected parameters
Add option to turn logging of python exception stack trace on and off
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.
