Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Export and import your history (to a certain level?. This way you can continue some different testing paths without having to save multiple versions of your workbench.
Change the current "view 1" etc to the workbench name so that when multiple inspection windows are open it is easier to tell which is which
If I want to expose the list with PythonCaller,I must expose elements of list. eg._listField{}.name,_listField{}.typeIf can add "Lists to Expose" to Advanced Parameters,expose list will be easy better.
The Regular Expression Editor has been newly introduced in FME 2016 beta. It's a great enhancement, welcome.In my observation, the Test String which the user entered will not be preserved once the editor has been closed. The editor restores the default string "Enter a string to test here..." whenever the user opens it.The usability would be further better if the field could preserve the user entered test string for each transformer.
Allow for more projection systems in the webmaptiler. Some people need/want their web services in local projection systems. British National Gird would be very useful. Also give it more options for pyrmid prodduciton.
Sometimes I just want to trace the follow of features through the Workspace when debugging. I have to define a Breakpoint somewhere after one of the Feature Types - and make an educated guess for the first one, or maybe I've disabled a Reader/Feature Type.However it would be nice to be able to 'Run with Breakpoint' without one defined and popup a confirmation that says none found but would you like to use the first feature read to start the Breakpoint process. Clearly you couldn't 'Continue to next breakpoint' but could 'Step to next connection'. A very quick way of tracing a flow especially with multiple readers/feature types.
It would be nice to have the option to add the 'Redirect to Inspector' to your Translation Parameter Dialog. This could either be done to add it as a parameter (this way you can define to show or not to show it in the Translation Paramaters Dialog) or to add it standard to the Translation Parameters Dialog (but sometimes you don't want to show it there).
It's possible to define a condition to filter a breakpoint (right click the breakpoint > Edit Breakpoint). It can use the condition builder to define a test to trigger the breakpoint. If I have multiple breakpoints across a Workspace and trying to debug a feature with a given identifier, I'd like to specify that identifier value at runtime as a Parameter and fetch it into the condition builder. All breakpoints would then only trigger for that specific feature. You could use the operator 'like' for multiple.
***Note from Migration:*** Original Title was: Allow Selecting Multiple List Elements for Old (Input) Attribute Column in AttributeRenamer Updated: 2016-02-06In FME 2016.0, the ability to rename list attributes has been added to the AttributeRenamer. Instead, the List Element Selection dialog has been retired, and now you will have to edit the "Input Attribute" column manually if you need to rename individual elements of the list. e.g. change "_list{}" to "_list{0}". I feel a bit inconvenience.It might be better if the dialog would be restored with some enhancements:The user can choose "Rename List" or "Rename List Elements" in the dialog.If "Rename List" is chosen, the list name (e.g. "_list{}") will be set to the column.If "Rename List Elements" is chosen, the user can select one or more elements (indices), and then the element(s) (e.g. "_list{0}") will be set to the column.The column still can be edited directly.=====Original Idea:The "List Element Selection" dialog for the AttributeRenamer only allows a single element selection currently.If it would allow selecting multiple elements and insert rows into the Old Attribute column automatically, could reduce user's effort to enter multiple elements one by one, in the case where the user needs to rename multiple elements at once.
The XMLUpdater has two input ports - Document and Update, and at least one Update feature is always required even if the update operations don't require any Update feature. For example, this simple Rename operation also requires a useless Update feature input.I think it would be better that the user can omit inputting Update features if the update operations don't require them.The JSONUpdater may also be so.
Add a Python/Tcl function which defines a global variable with initial value, so that the user can call the function in Startup Python/Tcl script.
I have been tinkering around with some of the new transformers in FME 2016. I think the AttributeValidator and AttributeManager transformers are a fantastic addition but I would like to make one recommendation. When dealing with large data, I think its acceptable not to know what is in every field. Therefore I think it would be very useful if, as well as the field headings, it loaded the first line from the table. That way you get a snapshot of the data while filling in the parameters in these transformers.
AttributeCreator: If you create a series of attributes in the AttributeCreator, it is not possible to reference to an attribute that you created previously on the same AttributeCreator. Would it be possible to create a mechanism that makes it possible to call an attribute that is created in the same AttributeCreator.
***Note from Migration:*** Original Title was: Add Parameters to Control Decimal Places to GeometryExtractor and GMLFeatureComposer Hope decimal places will be controllable, similar to the Maximum/Minimum Decimal Places parameters of the GML writer.
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.
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?
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).
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"...
***Note from Migration:*** Original Title was: Distributed deployment doesn't follow from express. Express deployment should be distributed ready
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.
