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.
Currently, when building a workspace app that includes a geometry parameter, the parameter is collapsed by default. This means users have to know to expand it before they can provide any input.It would be great to have the option to set the geometry parameter to display inline (expanded) by default. This would make the input more intuitive and improve the overall user experience.
If I want to find intersection points between two feature classes but I do not want to include the points where lines within the same feature class intersect.As in these two examples: A check box option to be able to exclude intersections within the same feature type would be one solution. Or, having two input ports and having an option to exclude intersections within the same input would be another solution. As stated in one of the above cited threads it would be similar to the opposite results of using the “Group By” function on the fme_feature_type.It seems unnecessarily complicated to have to add topologyBuilder just to be able to do this task as seems to be the general solution offered in both threads above. The resulting functionality would be similar to the Intersect geoprocessing tool in ArcGIS Pro.
I know you can expose list attributes by right clicking on them on the results on transformer before you need them however they can easily disappear and you have no visibility that they were exposed at one point. Also it takes me ages to remember where it is. What I would like is a transformer that look similar to attribute renamer but gives the option to expose the list elements. Maybe call it ListAttributeRenamer where you select the list (in the yellow area) and it exposes all of the elements as attributes. Bonus point if it could expose all of the list elements and defaults to give them a name plus a sequence like 1,2,3 or A, B,C. This would mean you don’t have to guess at the number of list values, it would only push out an attribute if the list has one and if there is a new one it is visible in the transformer instead of buried with you guessing if it exists or not. You could then update the ones you want to a name you want. This would make it so much more intuitive and useful.
Could there be an option so that if no features make it to the FeatureWriter, there is still a way to know that the workspace has run but that there were no outputs? I have found a workaround by generating a count_id from the transformer before the writer and another count_id directly from a creator. From the creator, the count will always = 1. From the transformer, the count varies depending on how many features pass through. These are input to a FeatureJoiner which joins on both count_id’s and if there is any output from the UnjoinedLeft port then this feeds an AttributeFileWriter to inform the user there was no output.
Hi, using other ETL and data processing tools I have noticed diagnostic tools that collect and present in a clear way the processes being performed. I know that there is a log for information and debugging the script, but it would be nice if there was an alternative tool built into FME Form for presenting processes (e.g. elapsed time, function, process, RAM, CPU, etc.). Especially comparing the times of tool operation would give a general idea of the length of the processes (the log is not perfect in this respect)
On complex workbenches with multiple bookmarks, it can be difficult to read the bookmark titles. I think it would be good to be able to adjust the bookmark title text size and colour, to enhance readability and improve presentation. I appreciate this would potentially have complications for bookmark spacing, etc.
Allow exporting/importing of toolbar configuration. When upgrading to a new version or working from a different workspace, it takes time to reconfigure the toolbar manually.
under View menu, you can't turn back on Feature Information window should it be closed by a useraltering the windows view and lack of Feature Information window?The only way to show this window, is launch the hard to find “Info” button in visual preview show hide Feature Information window
When using FME Server the standard approach is to provide the service account access to the relevant files and folders used by the workspaces. This would technically allow other authors to publish and run workspaces on files they shouldn’t be able to access if they know where the service account has access. This idea is to propose that for any reader/writer that accesses files that set of credentials can be supplied to be used for that read or write operation similar to the way web connections are handled.
As the dash (-) is not allowed in ArcGIS Portal File names, it would be great if FME could update that on the fly if an invalid filename is passed in, similar how characters like { } are changed to _ for attributes.
Hi FME team,Referring to the post Read AEC Objects (Geometries and Attributes) in FME | Community we’re also very interested in reading AutoCAD AecDbSpace objects. It would be great if it’s implement in the next version. Thanks,cart
It would be nice if you could select a Web Connection to connect to ArcGIS Portal and have the Portal URL in the reader/writer populate from that.
We run many Parent-Child jobs where the amount of Child workbenches can be in the hundreds with different User Parameter values for each. Therefore it can be very time-consuming to search each log file to find the right one.What would be very handy is a search box in Completed Jobs that searches the User Parameters for jobs with that value.
Hi there,Similar to this idea: I would like to be able to filter FME Flow completed jobs more effectively.Things I would like to be able to do:Exclusion filtering on all filter categories Apply multiple filters at once Be able to select multiple items in a single filter - i.e. show all jobs from repository1 and repository2 Be able to permanently hide certain workspaces or repositories from the job queue and then unhide them if required. For example: we have a job that runs every 5 minutes to query an api and update a sharepoint page. It is simple and low risk if it fails, but it clutters up the completed job list. I would like to be able to hide it. Thanks,Marc
I recently discovered that when using a TestFilter in FME, Null values are treated as numbers, seemingly to behave like negative infinityIf someone is not aware of this (such as myself) this leads to incorrect output data. My expectation was that Null should be routed to the 'Unfiltered' port, rather than being processed as a valid numerical value. It is not even treated as zero, as it is in other applications/programming languages, which would at least have some logic to it. I am of the opinion that this issue has impacted MANY of your users who were unaware of this.If there are default options which can be set somewhere to change this functionality, the default should be to rout the null values to the unfiltered port.try it out for yourself:
I would be great if the PolylineAnalyzer had a group by option as I find it currently only works if a polyline / polygon does not share a boundary with another feature.
Please add a "Maintenance Mode" to FME Server.This should be activated during restore and (maybe) backup (or manually by the admin):Disable all schedules and automationsDisable services (JobSubmitter/Streaming/Download)Forbid publishing of new ressourcesIn other words: The server should be in a read-only-state during restore.Doing some larger backups lately to FME Server 2019.2 I noticed that jobs got already triggered during restore but failed, because the database connections used had not been restored at that point.
Hi there,At the moment if you list the roles the associated users are in a long comma separated string, which is very hard to parse. If you click on the role the users get hidden further into a drop down radio box style selector.Could you please enhance the user information in the role page with a more user friendly selection/user information presentation style.Thanks,Marc
I propose that more options be added to the Polling Interval for a Directory Watch Trigger:Allow for the Trigger to check only the hours of Mon - Fri 8a to 5p, or Sat & Sun only, for example. I will suggest adding CRON Expressions if that will achieve what I suggest in #1.
Hi everyone,I think a new action “delay” (like the Decelerator transformer) would be a good addition to automations.My current scenario:Data is inserted into an external system and I need to check via HTTP calls if the external system has processed the data yet. I don’t want to do this check in the main Workspace, since the external system can take between 1 and 30 minutes. I’ve solved this for now using the Workspace Retry in automations. However, this results in a unpleasant Job history, since I need to design the Check-Workspace to run into an error to trigger the retry. A delay would allow me to loop back to a Check-Workspace on my own terms. I’m sure there are plenty more use cases where a delay could be useful. Especially in combination with loops. What do you think?Kind regardsDennis
WEBP makes MBTiles a lot smaller than using current options.WEBP is now supported in GDAL writing MBTiles.
This would be helpful for exposing attributes that are already passed in as a comma separated list for a oslc.select statement and would allow for better encapsulation when creating custom transformers. This would be very similar to the way the AttributeKeeper works.
Using letters that are not in the standard english alphabet is causing issues when running workspaces. To take one exemple, passing a user parameter to a child workspace using WorkspaceRunner, will fail if the parameter contains ie. norwegian letters. “å” becomes “ Ă¥” (unicode \u00E5 ). If the parameter is a file path, child workspace will fail finding the folder/file.A workaround is to manually convert unsupported unicode characters with StringPairReplacer.This is suboptimal for 3 main reasons:Most often we need to handle these characters in inputs and outputs. Non english letters are meaningful, they convey sense for users. Scaling down to an english subset can sometimes create confusion between two similar words that are differentiated with these extra letters. Creating datastructure (and being able to handle these characters in our FME flows) in native language is adding value to our customers.
Like running a workspace normally, it would be nice to have the option to select which service to run the workspace as within an Automation.
As per https://gisgeography.com/arcgis-shapefile-files-types-extensions/ a shapefile is made of a number of manditory and optional files.Shapefile Writers output some of these optional files.In some cases these can cause issues in external/legacy systems.It would be helpful if there was an advanced option in the writer to select what optional files are in/excluded
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.
