Open ideas have been reviewed by our Product Management and are open for commenting and voting.
At this moment the option to redirect writers to inspector is adjustable for every workspace. When working in a large project involving a lot of WorkspaceRunners calling other workspaces, I tend to forget to disable this option in some of the workspaces. This results in having to run the complete process (or at least a big part of it) again when I notice my mistake the next morning.Therefore it would be very useful if there was a way of overruling this per-workspace setting with a global setting.
When running a workspace via a workspacerunner it would be useful if you could select an option to disable any inspectors in the child workspace without having to edit and save the workspace.
Hi, are there any plans to make the Snapper or AnchoredSnapper 3D? This would greatly assist my team as we work mainly in 3D these days. Thanks
I love the new feature writer capabilities. It's a great way to put a writer where you need it. But with the new feature writer transformer, it ignores the previously very helpful Redirect to Inspector functionality as well as being included in the Output Features Written report. Would it be possible to have the Writer transformer work the same way a feature writer worked?Also, can the Reader and Writer transformers be made a different color. They kind of get lost in the crowd when they're all the same blue.
The unique port of the duplicate filter outputs the first feature for any key value. It does not only output unique values in a dataset and can be misleading to newcomers to FME.
***Note from Migration:*** Original Title was: Simple user-selected pattern fills in Data Inspector for easier area overlap visualization While we can adjust fill opacity and pens, having some simple fill patterns with transparent backgrounds would make overlapping areas more visually obvious - hatch fills at different angles, for example.
***Note from Migration:*** Original Title was: Removing parameters should invalidate transformers instead of resolving default value Currently if you delete a user parameter that is referenced by a transformer, the transformer parameter is changed to be hardcoded to the default value of the user parameter.It would be nice if the behaviour was instead like that of a missing attribute, where the transformer becomes invalid (red gear) and the missing attribute (user parameter) is highlighted.
Currently when you rename a user parameter, all references to that parameter are also renamed. However there are times when it would be nice to override that behaviour, and keep all the references pointing to the old name.
2016.1 gives us the ability to control the line width of features in the inspector. It would be nice if the Inspector transformer Vector Parameters included this along with opacity.
In the Data Inspector, we have the option to set the pen width, pen opacity, and fill opacity from the legend. I would like this capability to be built into the Inspector transformer for repeated testing.
Edit: Similar to this idea.Add the opacity parameter to the Inspector Parameters like it exists in the Inspector Drawing Style.
I'd really like to be able to add images into workspace bookmarks to aid documentation. To include things like company logos, small screen grabs of source table structure or source arget architecture, styling examples as per the native environment... etc etc. All images need to be able to have a link associated with them ideally.
It would be great if you could embed images (e.g. JPG or PNG) into the workbench.These images are intended only to overview.In many projects, graphics are used to represent the process flow.These pictures give a quick overview of what the workflow is doing.For Example theese images could be stored in the workbench encoded to base64.
add possibility to add a raster image as a background item on the canvas, same way as a bookmark or transformer
You have a disable transformer but when a work flow gets to it that stops the whole chain - if you had a "Bypass Transformer" it would just pass the input to the output, doing nothing to it - for multiple outputs maybe a bypass on each output
One user at FME WT suggested, that there could be an option for passing a transformer additionally to Enable/Disable. When Pass would be on, features would pass the transformer. When developing a workspace, many times you have to test the workspace with/without certain transformers. Now the fastest way is to use Ctrl-x and Ctrl-z. Passing a transformer would be like in coding: You can comment certain functionality, and the rest of the code is still executed. In FME, disable just stops the feature flow, and the user has to build new links for passing a transformer.
a method to disable but you want to let the data flow to an output (the default output - or choose which output) especially when testing but - disable stops the data flow -- this would be the same as a disable but allows the data thru with no changes
Add disable function to FeatureReader and FeatureWriter feature types. You can disable Reader's and Writer's feature types, but not FeatureReader's nor FeatureWriter's.And please bring the rest of the functionality from Readers and Writers to FeatureReader and FeatureWriter, which are currently missing.
It would be helpfull if it would be possible to attach an annotation to another annotation. Very often when I start building a workspace, I input different annotations describing the proces I would to build. Later on I replace the annotation by one or more transformers, somethings grouping them in bookmarks. A different way of working would be to use bookmarks, especially with the introduction of collapsable bookmarks in FME2018.0, add a transformer and a description in the bookmark and connect them, but I prefer only having the annotations.
I would like to see the possibility to connect an annotation to another annotation. This way you can discuss matters in a workbench or comment on a comment.
There are numerous implements of the various cluster algorithms within open source libraries including DBSCAN and Kmeans. An FME transformer for clustering would be really useful in trying to map more complex datasets. I know that people have used 3D terrains and distance matrices to do something similar but there doesn't appear to be any out of the box FME solutions and to create clustered areas in FME is quite a challenge. I guess python running scikit-learn would probably be the easiest way? But a transformer would be very useful and would help make FME more of a mapping tool.
This would allow for further geospatial and general data analytics within FME, including types of cluster analysis like Jenkins Natural Breaks or K-means analysis. Currently the best options seem to be scripts (Python, R) or other software (ESRI, QGIS).
Like the SchemaMapper which takes mapping rules from external file, the AttributeValidator could read validation rules from a table.This would also allow validation rules maintenance by non FME people.
It would be great if you could copy and paste a list of attributes for each validation rule rather than a pick list. I know you can copy and paste rules in the new version but it would be nice to be able to copy in lists of attributes from text files.
Hello, Recently i was need AttributeValidator transformer to check 700 attributes. I think it would be a good idea if Safe added an Import button like AttributeValueMapper. Please i need it ! Loïc, Sitdi-france.fr, FMEAddict
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.
