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.
Hi,As pointed at in : Please add a writer for on-disk mode.Thanks!
Its not obvious but it would be nice to make it easier to see.Without clicking on the value cell, it looks like a single value parameter. When I click on the cell, I see both the drop down and the ellipsis menu. Since there is a default value for MIME_TYPE, user would just populate the drop down and can easily ignore the mime-type. A further enhancement to this would be to make mime_type configured to an Attribute Value choice similar to “value”. If this is available, then I can add a MimeTypeFinder transformer in my workflow to populate the Mime-type parameter of the Multipart Upload.The use case for this would be when using the AddAttachments REST API and a feature with multiple attachments of different mime types supported by the destination format, eg, AGOL and Portal format writers.
Hi Will FME FORM is getting an object detection functionality.Can FME Users will be able to train a machine to recognise objects of interest within images supplied to it. We see great potential for this machine learning capability in areas of asset management and surveying and train a model by labeling . Thanks
Often, I’m dealing with large datasets and I want to do a quick comparison of the schemas. I only want one record from each. I appreciate that you can set Schema Scanner or Sampler to only sample one record, but it still processes the remaining features to an output port, which is wasting resource in many cases. How about a setting in both made available, that just takes the first (specified) number of features and then stops reading from the source?
Currently the FME Flow logfile cleanup is a one-size fits all setting. So all job logs older than the interval that’s set get deleted.I would like to propose a more fine-grained control, so on a per-workspace level be able to override that setting. Let’s say for example we have it set to 7 days, but have some jobs that run monthly. It could be beneficial to be able to see the log from the previous run if the current run fails. And on the other hand, if we have jobs that run many (say hundreds), I see limited value in being able to see one from a week ago, so I may want to shorten that retention period to say 1-2 days.
It would be nice to be able to give each FME instance an individual name (and possible icon) to be able to distinguish different instances without checking the sometimes cryptic or long url. Handling different stages in the same browser sometimes leads to tab change after tab change to get the right instance.Different Instances of FME FlowIt would be possible to directly chose the correct instance if the admin defined name could be shown instead of FME Flow as title and possibly a selected favicon - that is already possible to change going into the webapp but not documented and the path may vary between versions.
Lots of organisations have several FME Flow Instances, Dev, Test, Prod for example.It would be helpful to have the ability to select different colour pallets for each environment to quickly differentiate between each env.For example, you would be able to change the sidebar colour to blue for dev, green for test and red for prod
Please add support for colors / appearances to the I3S writer. Currently, colors which are set within the feature in ArcSDE are lost, and all features within the published scene become white.
I’d like to request a more prominent notification flag for when FME packages need updates rather than the manual review process now. Unless a person manually checks you are only made aware of an issue when the workspace generates an error. Thanks!
It would be very helpful if the number of neighbors found were returned as an additional attribute (e.g. _count). This would save the effort of creating a list and subsequently using a ListElementCounter.
Currently, in FME Flow, when a user edits and saves an existing schedule, the scheduled job appears to run under the username of the last person who saved it, even though the ownership of the schedule has not changed. This behavior can cause issues when the last editor does not have the necessary permissions to access specific data sources or resources, leading to unexpected job failures.We request that schedules retain the original owner's execution context, regardless of who last modified or saved the schedule settings. Saving or editing a schedule should not modify the account under which the schedule executes unless the schedule's ownership is explicitly changed.
In AutoCAD you can choose if it should display your MText with or without text frame and with or without text background color. Wouldn't it be nice if the dwg writer would offer/accept such format attributes like i.e. autocad_text_frame <yes/no> or autocad_text_background <color> to define the MText appearance?Even better, when the dwg styler can set these attributes.
It would be great if loading spinner is displayed while streaming is in process. Current way of displaying two sentences is not as intuitive as spinner like in this examplehttps://getbootstrap.com/docs/5.3/components/spinners/
It looks like that either the Postgres Reader and Writer doesn't support multiple column / field constraints. See discussion:https://knowledge.safe.com/questions/78765/multiple-column-key-constraint-is-wrong-interprete.html?childToView=78768#answer-78768If you ask me it's a shortcomming that should be fixed!
Make ProjectWiseWSGConnector able to retrieve and download specific file version and attributes
Hi there,Depending upon their source Coordinate Systems in FME may or may not have EPSG codes matched to them.For example if our user picks NZGD2K.MountEden from the list I can use the CoordinateSystemDescriptionConverter transformer to extract the EPSG code and use it in the workspace. However if they choose MOUNT_EDEN_2000 then there is no EPSG code associated with it and the CoordinateSystemDescriptionConverter returns nothing.Would it be possible to sync the various coordinate systems so that all available information is available to FME no mater which CS version they choose? I am not able to limit the end users choice in the Server app as I need to cater for all possible coordinate systems.I understand the different coordinate systems have different "metadata" with them, depending upon their source, however this can lead to an inconsistent experience for the end user.Regards,Marc
When adding components to an FME Server project sometimes it can be that I want to add just specific files - e.g., 3rd party python dependencies which are in the root python3.XX folder. 9 times out of 10 its fine to have just the folder, however, if I add the python311 folder to my project because I was just one file from the folder then I end up with all of the other stuff in the folder. Then if I choose to delete the project (and all of it’s contents) then all of the files in that python311 folder are gone too. The same is true if I have just a file sitting in the $(FME_SHAREDRESOURCE_DATA) folder. The fix here is easy enough - just put it in a folder, however, that then requires changing the workspace which may use that file which might not always be that easy or my have knock on effects.
Innovyze, now part of the Autodesk Group, have a number of hydraulic software packages which are used world wide. The InfoAsset and ICM suites are used by the majority of UK water companies to manage asset survey data and model their clean and wastewater networks. The software utilises a proprietary database format, across the suit of software. The spatial data held within the database can we exported from within the application to a variety of standard data formats shp, tab, csv etc although there would be a significant benefit if data could be manipulated without the using the software directly
Hi everyone,I’d like to share an idea that could significantly streamline our workflows in FME Form, particularly when working with a lot of fields with the AttributeManager.Imagine this: an AI-powered enhancement that automatically detects and intelligently renames attribute fields based on your past workbenches or predefined naming preferences.🔍 Here’s how it could work:The AI would analyze field names like horizon_canopy_trees_percentage and suggest a cleaner, more intuitive name like CANOPY_PERCENTAGE. It could learn from your previous projects to suggest consistent naming conventions. You could set parameters such as: Use of capital letters or snake_case Abbreviation rules Context-aware naming (e.g., recognizing that “canopy” and “percentage” are key descriptors) Share an Excel file with fields name that the AI could associate with the fields in the AttributeManager.💡 Why this matters:Reduces manual renaming effort Promotes consistency across projects Makes workspaces easier to read and maintain Saves time, especially in large or complex datasetsI believe this could be a powerful addition to FME’s smart automation capabilities. I’d love to hear your thoughts, feedback, or any ideas to expand on this concept!
Working with readers that are either single merged feature types or datasets that do not expose attributes, e.g. CAD, XML, JSON or OSM PBF, as an author, I’d like to have as an option to be able to see attributes that are imported in the AttributeExposer to show the number of features that have values..Adding an option to show null, missing and empty values would be a nice feature too. When I import from cache, it would be nice to see the attribute value stats when Importing attributes. There’s room for columns to show the count for all.With this feature, the author can pick attributes that have values, keeping the destination cleaner. AI Assist recommends a Tester transformer plus counter to do this.The community hub transformer AttributeValueCounter was a good option to use for this but it does not work in FME ENGINE 2025.0.x. Just some random ideas, when Feature Cache is enabled for a workspace, during a translation run a background process can calculate the stats on the source feature types initially. Perhaps add that to the reading of the schema when a reader is configured to be added to the canvas.Get the unexposed attribute stats immediately optionally. Maybe just have a checkbox on the Import from Feature Cache or Import from Dataset dialog to allow the option.
In the Data Inspector and the Visual Preview pane, I would like to suggest a function that uses an LLM to automatically assign styling to the shown data layers (best effort), based on the name of the layers.This function should allow quick symbolization and automatically suggests fitting colors and symbols for vector layers. It should not replace the existing style dialog.The result should be predictable and reproducible layer styling between workspace executions on the same, or similar, datasets.
Today we did an upgrade to FME Flow 2025.1. Unfortunately we noticed it is not possible to have a clean start (completely back to default) of FME Flow, without doing a new installation. Of course there is an option of overwrite items via a 'clean' back up file (.fsconfig). However, folders already present in FME Flow will not be overwritten if they are not present in the clean back up file. See also this link.It would be nice to have something like a 'clean up button' to restore the FME Flow default without a complete new installation. Is that possible?
At the moment the VoronoiDiagrammer only calculates distance "as the crow flies" this may not produce the best results. By taking land boundaries into account the transformer would produce much better results for land-based travel.
When testing/debugging unexpected behaviour on FME Flow one of the first steps is to use FME Form to run it locally and take advantage of the sweet sweet feature caching.In some cases there can be quite a few parameters which need to be copied which is a real pain. A feature which would save a lot of time is to be able to auto populate the local settings of a workspace based on a FME Flow job.
There are many transformers that have a tolerance parameter (ex Clipper, Dissolver). While they default to automatic calculated tolerance, for features in lat/long, that generally works out to something like 8.800000000000009e-14. It would be nice if we could set the tolerance on the workspace, and any transformer that does not have an explicit tolerance set would then use the workspace tolerance and not something sub-atomic.
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.
