Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
***Note from Migration:*** Original Title was: better understanding of projections within FME. If doing operations and coordinate systems don't match then output warning or terminate.
***Note from Migration:*** Original Title was: Ensure that Named connections think about the migration problem between different servers. No description.
***Note from Migration:*** Original Title was: Add a dialog to terminate or continue a translation if a writer receives a bad feature When a writer crashes due to an invalid object push a dialog to quit the translation or to skip the object.
While typing, press the tab key to change from transformers to Readers to Writers
At the moment you can add PRE- and POST-sql task to Oracle (Spatial) writer only in the Navigator tree. Fine, but misleading, when you should see those probably important tasks/transformations on the canvas (too) !
Turn on or off functionality based on format spaces. ie. if you have no intention of using BIM/3D get rid of all formats and transformers that play in this space.
Change Transformers section in Navigator to be organized into collapsible groups by FME transformer name (not the name assigned when the transformer is used multiple times in the workbench (e.g. AttributeCreator, AttributeCreator_2, etc.).
***Note from Migration:*** Original Title was: Enhance transformers that modify results to be able to use a previous result in a subsequent calculation Enhance transformers that modify results to be able to use a previous result in a subsequent calculation. e.g. AttributeCreator could create a attributes "A" and "B", then create attribute "C" = "A" + "B" in the same transformer. This functionality would be especially useful in the InlineQuerier, to be able to build "views" (Output Ports) that could be used in subsequent OutputPort SQL Queries.
***Note from Migration:*** Original Title was: Option to Trace Upstream or Downstream by Clicking on a Transformer, Reader or Writer I'd like to be able to right click (or click on a toolbar tool) on a reader/writer/transformer and choose trace upstream or trace downstream and highlight the connected links/objects on the workbench.This would be useful for tracking data flow through the workspace.
I would like to be able to add an annotation to an individual output port of a transformer. This way you can describe the development of the subsequent steps of your model from a specific point.Another option would be the possibility to connect an output port of a transformer to an annotation object. In reality the model will stop running after the last transformer.
highlight readers, writers, sqlcreators, sqlexecutors, etc. that don't use parameters. especially useful as an alarm notification when uploading a workspace to fme server
Pages update automatically as system changes. Could be job queue, system resources, etc.
Add an option to the AttributeKeeper to also remove the geometry of a feature. Maybe it should be renamed to Keeper. In that case it can also replace the GeometryRemover
Do you mean a kind of folder-tree structure only use transformers instead of folders? That would improve the current alphabetical list of transformers.
If I would make an external custom transformer, I can't run it with the inspection inside of it. Can you add the testing parameters for external custom transformer. (Testing readers and writers inside of exported custom transformer edition mode)
***Note from Migration:*** Original Title was: Installer Default to override the existing install. Put buildnumber in install directory so can have multiple installers.
Allow to import code from external libraries in PythonCaller or JavascriptCaller from the packet managers (e.g. pip, npm).This would allow to easily include a huge amount of different functionalities.
Add "read metadata only" to all formats. Ie read the header with boundingbox instead of the whole raster, lidar or other. this is usefull in combination with File and Directory Pathnames reader an featurereader to read only files that are within the spatial area of an object. Today it seems for instance DEM does not support this, and the complete file is read which takes a lot of time
Link a parameter to a certain dataset. It would be nice if you could, particularly, link a choice parameter dynamically to a dataset. This way the workbench does not need to be updated when the dataset is updated. Now you have to import the data and a change in the dataset will not automatically be added to the parameter. When both are managed by different people this can cause issues.
"promote" custom transformer parameters to full workspace parameters. the value for the custom transformer parameter automatically gets assigned to the workspace parameter value. for nested custom transformers, i imagine you'd need to be able to go n levels up...
Possibility to add junctions to connections between transformers, when a transformer receives data from multiple transformers.
Easily invoke REST APIs that are pre-configured. Ideally configuration allows for transformers to be auto-created for webservices like Twilio, Trello, Gmail, etc etc.
I would like to have a "preview $(n)" as a right click option on a connection or output port. A pull request "preview to here" sort of thing thrown to Inspector. I think this would speed up my debug iterations in a big way.
In the new 'Attribute Accumulation' I miss the option 'do not accumulate attributes' / 'Only use base'
Why not create an iFilter or Apache Lucene interface that makes it possible to extract the text content of any file for further processing? This would make it possible extract a lot of data, even OCR from images...
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.
