Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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!
Reader and Writer for OpenOffice-Table (*.ods)
I would like to see that Inspectors are seen as a separate class (and not as a transformer), so it is easier to find them in the navigator.
Given a 3D Model and a camera location, render out an image.
***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'.
***Note from Migration:*** Original Title was: Clicking on a Selection Instead of Directly on a Transformer when Displacing a Group of Transformers When selecting a lot of transformers in the aim of displacing them, you have now to click exactly on a transformer to make the move. Would it be possible to just click somewhere of the selection without having to select one of the transformer/box.
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.
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 =).
Dissolver and LineJoiner: Add an optional field for an attribute to store accumulated values, just like in the aggregator. For the LineJoiner also the other Statistics fields (sum, average, etc.) could be added.
Durability. Ability to have a warm failover of FME sever core components that would guarantee 99.9999% uptime.
Support CartoCSS in the MapnikRasterizer
AreaBuilder: Add a standard/optional attribute _area: In most cases I want to do something with the area size, and now I always have to add an AreaCalculator to do this.
Add the option to use _list{@Value(AttributeName)}.Attribute as the value in the AttributeCreator. At this point the string above will be recognized as a string and not as a list/attribute reference.
Never go to "parameters" to pick tables, set options etc -- important "5" parameters will be right there. An "advanced" button to get to the rest
The Excel reader now has the option to freeze titles. It would be very nice if it would also be possible to already add the Filter to a certain row.
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.
It would be great to have a single instal (64bit) that knows by itself, or behaves as if it is 32bit, when it has to downscale to 32bit for a certain reader or writer.This way you don't open models in 64bit to find out after ten minutes that the model crashes because it needs 32bit.
Ability to adjust the height or the width of the 'SummaryAnnotation' Or Start standard annotation with 'SummaryAnnotation' contents
Change the Pan tool to Zoom In temporarily by pressing and holding a key on the keyboard. I use this feature all the time in ArcMap, where the Pan tool changes to Zoom In by pressing down the C key.
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:
Find out the number of features that have actually been written, rather than the number that have been sent to the writer. This would make it easier to tell at a glance that something has gone wrong with the workspace.
Add expose all attributes transformer for when working with Dynamic workflows.
Adjust FeatureReader parameter 'ConstraintsSpatial Filter' so it becomes a list of checkboxes in stead of a list where only a single value can be chosen.
For both transformers and reader/writer parameters, ensure the navigator retains and reflects the grouping and group headings from the original dialogs from whence these parameters originated.
In the "Check for Update..." modal, it should have an option to download in background and install the update, that would be launched after the FME programs are closed by the user, if the user agrees. The software paint.net (http://www. getpaint. net) uses this kind of aproach.
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.
