Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Many organizations that have paid subscriptions to online basemap subscriptions (ESRI, Bing, Google, etc) or have access to open source online basemaps use the same web services as background context for digital maps. For workbenches that use writers that produce digital maps, it would be nice to have this reader format or transformer so that maps produced from FME would be more meaningful. Can Safe use the FME options basemap functionality in Inspector and convert that to a reader and/or transformer format? Another option here is to add that FME option to the writers that produce digital maps (CAD, DGN, PDF, JPEG, LYR) as a baseline maps parameter. With a reader and a transformer you could do more. A writer option would be simpler but also be beneficial to a lot of organizations as well.
I'd really like to be able to test my attributes that should have a sequence of numbers 1-n where I'd like every number not necessarily in order but in the sequence so that I know if I've lost a feature along the way somewhere. I tried to achieve this using the In Range rule with an upper limit of a combination of @count() and max(@count()) but to no avail. Otherwise I can use a StatisticsCalculator and Tester do this but it would be great to be able to do this in the Validator.
In FME 2015 Workbench, the zoom slider control could be double clicked to return to 100% zoom. This disappeared in FME 2016. Can we have it back please?
EUROCONTROL has developed a new model, the Terrain Information Exchange Model (TIXM), to support the exchange of terrain data.
AttributeRemover, add an option to remove all attributes that aren't mapped or enable a user to right click an attribute from the drop down of the transformer and delete each without having to go into properties.Would be very useful and increase efficiency when you have more than 200 columns from multiple sources.
When using an overlay transformer in the result geometry all measures are gone.Being able to select the measures to be kept help in code reducing.
It might be useful if template functions could be used for generic string operation. The expected transformer should support some control statements (e.g. "if - else", "for") and relation operators to construct a string conditionally or iteratively. It would be better if it could also support sub templates similar to the XMLTemplater.
Hi, Please can you add the 'OutputLocation' parameter to the 'Job' 'Response Class' returned by the REST service?This would allow you to calculate the download link from Asynchronous Data Download requests.Many thanks,Paul Wittle
Ability to calculate speed and efficiency of workspace without having to run it similar to the execution plan and stats page of SQL Server Management Studio.
Provide the option to save edits to an FMWT without having to re-export it each time you make a change.
Arrange Transformers with StraightConnection
A light version of FME Desktop on Cloud to troubleshoot workspaces
***Note from Migration:*** Original Title was: Creating an Extension (or plug-in) for QGIS to preview/import data or export data Something similar to the ArcGIS extension but perhaps as a plugin for QGIS.
As far as my knowledge goes, it is only possible to call a similar version(32 or 64 bit) of another FME workspace by using a Workspacerunner tranformer. Calling a 64 bit FME workspace withing a 32 bit workbench or the other way around is not possible, but would be nice to have to take advantage of the difference in readers & writers that the two versions support.
***Note from Migration:*** Original Title was: Add a Workspace Explorer to find old workspaces by name or format or transformer content Add a Workspace Explorer to allow me to find all those workspaces I worked on for the past years on my machine up to the level of searching the transformers used within the workspace itself, formats I used ...
It would be good if the ChangeDetector tranformer could operate based on the 'fme_feature_type'. This would avoid using multiple ChangeDetector transformers in a workspace especially when a writer has the capability to writtten via a dynamic schema definition.
Joiners with a 1:M cardinality do not allow features with zero matches to pass through. I'd want to know what falls off for data validation purposes...adding a (1:M..0) cardinality would let me test _matched_records for values of 0.Alternatively, Change all cardinality levels to not include 0 matches and add a Failed output for features that fail to join
It would be nice if the XMLFormatter could point to an attribute for the XML Output File parameter instead of just a paramter or being hardcoded
Sometimes I run Desktop Jobs with multiple Inspectors, each of which has a group by. I would like to be able to see those inspectors as another layer on the display tree.so it looks something like: View 1 - Inspector - - Inspector 1 - - - group 1.1 - - - group 1.2 - - - group 1.3 - - Inspector 2 - - - group 2.1 - - - group 2.2 - - - group 2.3 with the usual check boxes I could turn off the related data with one click instead of having to click on several (perhaps several dozen) check boxes
***Note from Migration:*** Original Title was: Add a Transformer to Perform Iterative Operations for List Attributes - ListIterator (tentative) The expected transformer performs iterative operations for every element of specified lists, and then stores the result into new lists or overwrites source lists by the result. The user can declare aliases of source lists and define math or string expressions through the parameters dialog, like this.The index surrounded by square brackets in the expressions indicates relative position of elements. i.e. [0] indicates every element, [<negative>] indicates a prior element, [<positive>] indicates a subsequent element. An editor similar to the Arithmetic or Text Editor can also be used to enter each expression. This transformer should support both simple list (e.g. _list{}) and complex (structured) list (e.g. _list{}.foo, _list{}.bar).Example: If the source list and non-list attributes contain these values:_list{}.foo = [1,2,3,4,5] _list{}.bar = [10,20,30,40,50] n = 1 prefix = 'P'the destination list should be:_list{}.a = [2,3,4,5,6] _list{}.b = [<null>,20,30,40,<null>] _list{}.c = [11,22,33,44,55] _list{}.d = ['001_S','002_S','003_S','004_S','005_S'] _list{}.e = ['P_101','P_202','P_303','P_404','P_505'] [Addition] It would be ideal if each expression could have "circular list" option. If the option is ON, the _list{}.b should be:_list{}.b = [26.66666...,20,30,40,33.33333...]
After admiring the work of Owen Powell I am wandering if its possible to add blender 3D rendering into FME? Being able to render out images of scenes would be amazing.
As with the StringCaseChanger (see image) the option to act on all attributes would be very interesting with for example the StringReplacer, StringSearcher, DateFormatter and most likely more transformers. If you have ideas about additional transformers that can be added to this, please add a comment.That would allow dynamic workspaces with automatic writer attribute handling to use these transformers without identifying the attributes in the workspace.
It would be very helpful (for very large workspaces), if you could set a lock to the connection lines. May be in the properties or in the context menue.In my case, there are very large workspace with lots of transformers an connections. It unfortunately happens, that you accidentally remove or change the connections.Here one worspace with only some overlapping connections. Yes, i know that you can zoom in and choose one connection very well, but i'd prefer a lock to disable unintentional changes on the connections.
I'm missing a AttributeFilter in the DataInspector. Some Features have many Attributes, I know a part of the Attributename, but I have to search in a long list. Possible to place a searchfield under the Attributlist?
Mouse cursorWhen copy/pasting a transformer, it can go quite far from mouse cursor. Usually next thing is to drag the transformer and link it to another transformer or a feature type. Could the pasted transformer be located just where mouse cursor is?LinkingNow when a port is selected, a new added transformer is linked to the port. This could work similarly for copy/pasting a transformer. If a port is selected, and you copy/paste a transformer, it will be linked to the port.Of course all this works for feature types too.
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.
