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 the "Destination Attribute" parameter Optional: Currently this parameter is required, but there are cases where user defined Tcl script returns no value. In such a case, the destination attribute name would be useless.Add "Attributes to Hide" and "Lists to Hide" parameters: There also are cases where the script removes and/or renames feature attributes. It would be convenient if there were these parameters similar to the PythonCaller, so that the user can hide attribute/list names optionally.
The possibility to get/set individual raster cell values using the Python fmeobjects library. This would make it possible to perform e.g. advanced linear regression analysis that isn't already supported by the RasterCellValueCalculator.Exploding the raster into points using the RasterCellCoercer isn't a good alternative for larger raster datasets because of the large memory footprint.
Json reader writer that understands Json schema and reference hierarchy. For example: https://github.com/AnalyticalGraphicsInc/czml-writer/tree/master/Schema
Redirect to Inspection application should not only redirect WRITERS, but also all SQLExecutors and other Transformers that "writes" data.
An Excel-Reader with supporting Microsoft Office XML formats would be very useful.At this time only 'normal' xls and xlsx files can be read, but when i have an xml-based xls or xlsx file the data cannot be read.
Use different symbols in the reader/writers that already show the type of data your are dealing with. Now a table is always shown, but perhaps that can be changed in symbols for points, lines, polygons, 3d or a combination (if it is not clear).
Is it possible to change the Esri Filegeodatabase writer in such a way that the Writer Mode (Advanced parameter) can be set per feature class, in stead of the full database?
Add the possibility to use 'Stop Translation' with the function to output (temp) results to writers/loggers/inspectors where data is knocking at the door.
GeometryExtractor: The GeometryReplacer has an option to remove the attribute that contains the geometry. It would be nice if the GeometryExtractor gets an option to also remove the geometry after it is extracted.
***Note from Migration:*** Original Title was: Store a Snapshot of which Connectors, Transformers, Readers, and Writers are Enabled or Disabled Store a snapshot of which connectors/transformers and readers/writers are enabled or disabled in a project at any given time. I often run part of a workspace, and then disble some connections and run it again. It would be really useful if I could store a "bookmark" or "snapshot" of the enabled/disabled settings, and name them appropriately. I could then have "Run this first", "Run this second", "Run this to see if everything went smoothly"...
Not strictly a Canvas idea, but... As a consultant, we often have to use specific versions of FME for different projects. But it is too easy to open a workspace in the wrong (newer) version of FME Workbench, and by the time the save dialog comes up you might have done a lot of work that gets lost because of lacking backwards compatibility.How about an opt-in setting that prints the Workbench version clearly somewhere on the interface? e.g "FME 2014 SP5" either on the main window title bar or watermarked on the canvas somewhere? This information would stay there as long as the GUI is open.
I would like to see clasification transformers such as maximum likelihood classification (MLC), Inverse Distance weighting. Also auto object recognition for raster digitising would be brilliant- i.e. extract buildings from a raster map.
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.).
Rather than having them as separate transformers, just have these as "decorations" on links (or ports). Con: the new Run With Inspection effectively does this with Inspectors everywhere automatically.
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.
In the new 'Attribute Accumulation' I miss the option 'do not accumulate attributes' / 'Only use base'
Possibility to add junctions to connections between transformers, when a transformer receives data from multiple transformers.
***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: Generic Writer: Add the Option to use an Attribute to Set the 'Output Parameter'. For the Generic Writer: Add the option to use an attribute to set the 'output parameter'.
ALT + TAB to switch between the windows shows now (2015) the format of the reader and no more the file name (2013). With multiple opened workspaces it could be tricky to navigate between the different or similar format name. It was easier before =).
I think someone suggested something similar, but I'd like to be able to right click on a Tester, and turn it into a TestFilter. Copying the rules across is very painful!
***Note from Migration:*** Original Title was: Ensure that Named connections think about the migration problem between different servers. No description.
Ability to adjust the height or the width of the 'SummaryAnnotation' Or Start standard annotation with 'SummaryAnnotation' contents
For the IFC and Revit reader add the option to distinct between true attributes and settings/parameter properties. Now it is often hard to distinct between both.
Integration not just with Hadoop but Apache Spark in particular for reading and writing to RDD:s would be very useful for anyone with a Big Data Hadoop cluster. The machine learning algorithms and the graph database features of Spark would complement FME really well.:smiley_cat:
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.
