Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
Clipping features by using a search envelope currently requires a user to manually enter the bounding box coordinates.It would be very useful if you could simply set the current map extent as a search envelop.
As of FME 2017.1.2, it appears that only TomTom / Tele Atlas MultiNet 3.2 is supported, with partial support for 3.3/3.4.
Nice idea from QGIS 3 : preview the valid bounds of coordinate systems. I like it.https://www.youtube.com/embed/LUCZBcJu_uo
Add a Reader and Writer for Dynamics CRM Online using the new REST WebAPI interface, similar to the ones for Salesforce?
Add support for an FME date calculation function (either as a datetime function or within a transformer such as DateTimeCalculator) that works on a 5-day week or 'business days' system. Excel has a NETWORKDAYS function that takes a start date, end date, and holidays input to do this kind of calculation.
I would like a simple transformer to be able to append a value to an existing list.Currently either I need to use a PythonCaller or a ListElementCounter followed by an AttributeCreator with the list index as {@Value(_element_count)} (which works but gives an ugly output on the canvas)
When you find an "item on hub.safe.com - you should be able to discuss this in the knowledge center in its own folder. For instance autocreate /WebConnections/Github as a "product"/"folder" on knowledgebase to dicuss enhancements that can be done on that particular FME hub item. Also it would be nice to pubish everything on FME Hub on github. So anyone with a github-account can upload a new version of that transformer. The goal here is to get many users to contribute to improve errors and features for Custom Transformers / Webconnections etc. https://hub.safe.com/web_connections/github
There are cases where users need to create a structured list after splitting two or more attributes corresponding each other.e.g.Source attributes:Names = 'aaa,bbb,ccc'Types = 'x,y,z'Values = '1,2,3'Required list:_list{0}.Name = 'aaa', _list{1}.Name = 'bbb', _list{2}.Name = 'ccc'_list{0}.Type = 'x', _list{1}.Type = 'y', _list{2}.Type = 'z'_list{0}.Value = '1', _list{1}.Value = '2', _list{2}.Value = '3'To ease that,- add an parameter (optional) to the AttributeSplitter, so that the user can specify component (member) name that will be added to the resulting list name.and/or- enhance the functionality of ListRenamer (List Action: Rename), so that the user can add a component (member) name to the selected list name optionally. i.e. allow set "_newName{}.member" for "_oldName{}".
When working with workspaces with large numbers of embedded custom transformers it can become difficult to navigate between them. The tabs at the top of the screen become too small to read the transformer names and there is no easy way to go back and forth between views. A web browser style "back" button would be very handy, for example, if navigating in to edit a custom transformer that is embedded in another transformer, then needing to go back to where you came from.
A prompt that asks for parameters when all data has reached the transformer so that decisions can be made by a user based on results and will not continue until the user confirms or cancels.
I know FME can read groups, but it would be great to be able to write these as well.
Tools for handling voxels would be great.At present we switch between meshes, point clouds, rasters and extruded polygons to get voxel like functionality.Output is multiple solids/volumes for BIM applications.
Hi,sometimes it is helpful to know the drawing order of AutoCAD features to make some kind of sorting, espacially when trying to rasterize AutoCAD-data. In AutoCAD the drawing order can be changed and the information is saved in AcDbSortentsTable.Maybe you can create format-attributes for AutoCAD- Reader and Writer to access that information.Thanks,Thomas
FME currently has the AttributeValidator transformer. It would be nice if this transformer was able to validate Parameters too. Currently it's necessary to use a ParameterFetcher / AttributeRemove combo (because I don't need to keep Parameters around). It would be nice if this wasn't necessaryMy use-case:A RESTful service which will have users entering various tolerances via the parameters. Because it's using REST we can't rely on the interface to handle validation, so we're explicitly validating .FME is being aimed more and more at providing services, so input (parameter) validation is becoming more important.
Simplify input of Search Envelopes somehow - it would be nice to only have to deal with one dialog box (actually, ideally one text box even) rather than the current 4-6.
Either a new transformer (DateTimeSorter) or an extra option in the regular Sorter to sort on date/time attributes as depending on the notation the alphabetic/numeric options don't always give the right results.
Really just promoting this question to an "idea". External attributes which are exposed on a custom transformer input port get applied to all input ports in that custom transformer. It would be nice if the exposed attributes could be tied to specific input ports.As was noted in the original question, if different features are coming into different input ports, then they will not all necessarily contain all of the attributes being exposed and this can lead to confusion within the custom transformer as to what is really available on a feature.Similarly for output ports. If features exiting a specific output port only contain certain attributes, then invalid attributes should not be made available to the caller.
I would like to suggest some enhancements for the WMS Reader:Allow the user to choose the exception type if the WMS propagates more than one via getCapabilitiesIf the WMS servers sends an exception, FME 2017.0 does currently show:<WMS> Exception detected for the GetMap operation, requested Content-Type, 'image/png', returned Content-Type, 'application/vnd.ogc.se_xml; charset=utf-8;charset=utf-8'. It would be nice if FME could parse the exception xml and show the contained error message.Bonus: Even handle the error xml if the server sends it with the wrong content type ;).Allow choosing of WMS version 1.1.1/1.3.0
Add an additional column to enter an error text or concatenated text in the AttributeValidator would be cool...
I would like some mechanism to dynamically add attributes to a writer – presumably linked to some transformer. Note that this is not a dynamic schema -- The attributes do not exist on the source data, and I don’t know ahead of time what the attributes will be so I can’t manually add them to the writer. An example is any key/value pair from a list (ListHistogrammer for instance) where I would like the attribute name (key) added to the writer.
***Note from Migration:*** Original Title was: Add the ability to create a new layer in an existing feature service on ArcGIS Online
DEBUG mode for workspaces called by WorkspaceRunners. For linked worksheets I would like to have the option (debug mode if you will) for the caller to open multiple copies of FME (if not already open for that target worksheet) so that you can see what is going on, instead of running it like a command line. There is nothing more frustrating than debugging a target worksheet when having to manually populate the published parameters so you can figure out what went wrong.
When running WorkspaceRunner,Cannot display the running status of the workspace called in real time.If can display the canves of WorkspaceRunner called on the run time, And like the usual workspace,Display the number of Feature that has been processed And real-time processing log. Then it will be more convenient to debug, And better grasp the running situation.Of course, It is not necessary to display the working space at any time.So can add an option in the WorkspaceRunner parameter, such as the "show canves", only when this option is selected to show the canves.
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.
