Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
There is currently no simple way to have truly dynamic attribute mapping.I would like the ability to provide an input file, a mapping file (old attribute, new attribute) and get an output that is identical to the input except for the attribute names.While the schemaMapper allows you to dynamically rename attributes referencing an external lookup table, that lookup table is hardcoded, you cannot use a parameter to specify it.Additionally you cannot dynamically write out the changed attributes. All the schemaMapper examples assume hard coded attributes on the writer, which can lead to issues if the mapping table is updated and the writer is not. Both automatic and dynamic mode use the original schema unless schema from schema feature is selected.While one can use the SchemaSetter custom transformer to generate the new schema feature, it has the flaw that all strings are mapped to varchar(256) , leading to significant bloat in the output file when the original attribute might only be a few characters.Two updates to the schema mapper would allow this dynamic ability without having to script it in python. Allow the Schema mapping table to be set by a user parameter, or even an attribute.Have an output port on the SchemaMapper with an updated schema feature
I would like to be able to use voice recording to help with reporting for incident/emergency report apps. The recording should be available from FME Data Express as workspace/app parameter value input.
I had the idea to add the "download from fme server" button directly on the "Start" page of FME Desktop when the application launches. I know the button exists on the toolbar as well, but so do the "New" and "Generate" options. In teaching new FME users this is always something they seem to overlook.
The Native Revit reader in 2019.0 doesn't recognize RFA files. It would be nice to have that supported. @rollo
The middle line in road construction is often represented in LandXML and it's proposed vertical alignment for the profile is save in the ProfAlign element. Right now FME can't interpret the ProfAlign element which means that the data is in 2D without the vertical alignment.See also this old question
Rather than the *U_XX temporary name. (PR 65258)
***Note from Migration:*** Original Title was: TestConditions in TestFilter , support list elements index range in Test Clauses In TestFilter, allow specifying the list index range in the Test Clausee.g., _list{[0-2]}.fruit = 'Apple'rather than specifying each element index to test for individually:_list{0}.fruit = 'Apple'AND _list{1}.fruit = 'Apple'AND _list{2}.fruit = 'Apple'without going into PythonCaller, or custom transformer way
The ChangeDetector transformer is great particularly when enriching source data and updating a target database, but it is sometimes difficult to track which attributes are shared between the Original and Revised ports. It would be terrific if the attribute lists could be color coded, or have some other kind of indicator to quickly shed light on the attributes that are on both ports vs those that are only on one port. More than once I have been confused why I was seeing so many updates when some enriched attribute hadn't yet been considered before reaching the revised port. I'm sure there are other transformers that could benefit from similar treatment.
In the workspace, attributes have their own datatype which is sometimes different from the original data type (in the source).For exemple, a "date attribute" in the datasource is automaticaly converted into a "string attribute" into the workspace.Really anoying for Python scripts to work on these attributes and to detect the type of the data without auditing every value of the attribute.In this case, it is nearly impossible to create a dynamic schema with date columns without auditing every values.It would be really easier to work with original datatype.
***Note from Migration:*** Original Title was: The ability to automatically remove all attributes from the reader that are not used inside the workspace After authoring a workspace I would like to have the ability to automatically remove all attributes from the readers that are not used by transformers and/or writers inside the workspace. Removing these attributes will have a positive effect on performance. It’s sometimes a hassle to do this manually in large workspaces.
***Note from Migration:*** Original Title was: Automations "Merge messages" action should synchronize/merge output from "Run a workspace" actions Automations "Merge messages" action should synchronize/merge output from "Run a workspace" action jobs. For example, for cleanup operations or notifications following completion of multiple workspace jobs.
Currently FME Server Job Log Lines are restricted to 500 per page. Let's allow to choose this number by user. It may be for example choice between 500/2000/5000 lines per page.
Versioned SDE Geodatabase writing is exceptionally slow, which limits the functionality of FME for bulk data updates on large versioned datasets.Is there an ability for FME to "skip" creating a new version, and instead write directly to the default version in these cases?
It would be great if FME can show cached projection information off all the layers used in the workbench.
Hi, fellow FME-lovers!I have an interesting problem that you can help me solve in an efficient way.I have many pipe segements as solids in an ifc-file, see example in Test2.ifc. The pipes are in 3D and can be connected in all directions. (I'm not sure about the fittings but for now don't mind them.). Now, I need to calculate length per segment and I started working no a complicated scripts (2D and algebra...) but there must be more of an FME-way. I'm thinking along the lines of creating a center line from pipe start to end...If you have any ideas I will gladly listen. Bonus: what if segments are bent? Will this be handled in you solution?Peter
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.