Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
I see the Aggregator has an option to calculate average values weighted by area. It would be handy to see a weighted by length when used for lines. it’s easy enough to handle this calculation without the help of the Aggregator but it would be a nice little improvement.
this string compare mode would help simplify workspaces changing case on keys and such just for comparing.
When downloading data using Data Download service (e.g. from an FME Workspace App), a Zip file is created containing the output files. The zip file is automatically named something that looks like “FME_4B425D3A_1772473610895_13172.zip”. It would be nice if an option was implemented to allow customizing that name to something that is more user friendly. For example allow authors to specify what exact name the Zip file should have, or allow the use of parameters to create a string to use as file name. Even if the final filename has to have some extra characters at the end like 4B425D3A_1772473610895_13172, giving authors some customization capability would be beneficial.
It would be nice if the ChangeDetector match all attributes could exclude unexposed workspace level attributes like multi_reader_id, multi_reader_full_id, multi_reader_keyword, multi_reader_type.As it is, I need to either use match selected attributes and select them all (not possible in dynamic scenarios) or expose the multi_ attributes prior to the ChangeDetector so that match all except can be used.
Add a 'Case sensitive' option to the Joiner. Sometimes capitalization of attributes differs between source and target attributes. It would be nice if you could just use an option to take this into account or not.
I’ll start by saying I think FME Form is one of the greatest software tools ever created. With that said I have been waiting for one additional Zoom function since I started using it 15 years ago. Why can we not get a Zoom to Previous Extent action/button? I don’t want to pretend I know all that is involved with doing this, but it just seems obvious that it would be one of the most used features when dealing with extremely large workspaces. Are we ever going to get it?Safe team, please consider it.Thanks for your time!
Within FME Flow I am using several Deployment Parameters in a multitude of workspaces. When managing those, I would like to be able to see which workspaces and automations are referencing a specific deployment parameter, similar to how you can see within a workspace which transformers are using this deployment parameter.The reason why? I want to be able to see my impact whenUpdating/altering a deployment parameter → which workspaces and automations do I need to test Deleting a deployment parameter → can I delete this deployment parameter or is it still being used?Currently the only way to see this is to open every single workspace and check which deployment parameters are being used. Or managing a separate list with an overview of all deployment parameters and workspaces + automations.
I’m trying to write features to an esri feature service, but getting “fatal errors” from the feature service that is causing the entire FME workspace to fail. I should be allowed to decide what to do if a “fatal error”, much in the same way that I can choose how to handle rejected features (Terminate Translation or Continue Translation).FME should just “fail” that single request and continue writing features out. Examples of where this would be useful:
This question has been asked so many times and is ridiculously confusing and hard for something that should have been added ages ago. I have a table that has table or layer names that I want to process in FME. I should be able to Dynamic SQLExecutor or FeatureReader to read the list and add them in to form without having to know the schema ahead of time. The issue is the schema they read comes from the input table and not the features it reads. The attributes are returned so you can write them with a dynamic writer, you just can see or use them in form. It needs the ability to dynamically return a value as defined in the source table (for example the @layerID or allow a wildcard to return all fields) and the fme_feature_type, fme_basename and fme_dataset not from the initiator but from the dynamically read table/layers. In this case I have the layer/table name and the ID I want to expose in the initiator table there just doesn’t seem to be a way get the attributes to dynamically read from the imitator table or to just dynamically read all attributes back.fme_attributes should come from the feature it is reading not the initiator, same with the schema it should be the schema of the feature it is reading not the initiatorIt can read the list of tables in but cannot read the attribute I want dynamically. For example, when it reads TRAILSIGNS the attribute I want returned is TRAILSIGNID
It would be useful to allow a way to group related transformers together without having to use a bookmark. Bookmarks can take up too much space, or also the grouping might not be logical to put in a bookmark. Would be nice to just be able to select a group of transformers and make them ‘stick’ to each other, so if you need to move them again you don’t have to manually select the whole area they cover (and accidentally select other things you don’t want), all this can make working with FME more productive
Hi there,If you click on the log out of FME account menu item, then you see this dialog:There is no way to cancel this. I think it would benefit from a cancel button, in case you change your mind.Thanks,Marc
Add .ods reader and writer (LibreOffice OR OpenOffice) !
I would like to propose a new feature for the Excel Writer in FME Form: the ability to automatically enable Excel’s built-in “Sort and Filter” functionality on the output file.This enhancement would allow users to generate Excel files where the column headers are immediately interactive, making it easier for end users to sort and filter data without additional formatting steps in Excel.Proposed Implementation:Add a checkbox option in the Excel Writer parameters (e.g., “Enable Excel Sort and Filter”). When enabled, the writer would apply Excel’s AutoFilter to the header row of the output sheet.Benefits:Improves usability of Excel outputs for non-technical stakeholders. Saves time by eliminating the need to manually apply filters in Excel. Enhances the presentation and interactivity of exported data.This small but impactful feature would streamline reporting workflows and improve the end-user experience.
Geometry Collections can be very difficult to intercept. They sometimes are nothing ore than a fairly simple polygon, where one of the segments is an arc for example. Trying to write these to quite a few formats usually results in problems, and some GIS applications like QGis can’t handle them properly.But there is no surefire way to catch these, since they are not always aggregates. There have been a few threads about this already, like this one: Geopackages and different polygon types in same layer ? | Community and this one: Aggregated surfaces written in wrong file format in SQL server | CommunityIt would be very helpful if the option ‘Collection’ was added to the GeometryFilter’s Simple definition list. It might already be possible using the Detailed mode, but that is not very obvious (I haven’t figured out how...).
FME24 provides an overly simplified and bland user interface and experience. Even as a long time FME user I find it difficult to use and even train new users. Personally, I’m yet to find a single benefit of the change.E.g. Simple icon colours which categorise items in the navigator (Purple = Parameters) are gone.Similar to being able to select dark mode, I think it would be extremely helpful to enable users to select the theme and icon styles that improve their user experience.
IFC-writer - support textures
I am looking for a way to write to a self-created GeoPackage that contains multiple foreign keys and check constraints. To ensure the data loads correctly without ordering conflicts, I need to temporarily disable foreign key validation by executing:PRAGMA foreign_keys = OFF;Once all feature classes are written, I need to re-enable the checks.Currently, the GeoPackage writer lacks the option to execute SQL scripts before or after the translation process. Using a separate SQLExecutor is not a viable workaround because it operates in a different session; therefore, the pragma command does not affect the writer's connection.Interestingly, I can achieve the desired behavior using a SpatiaLite writer with a SQL statement on the same file, but this method fails to handle geometry correctly. Due to these limitations, I am considering switching from GeoPackage to SpatiaLite as a temporary measure, though this is not my preferred solution.Could you please add SQL before and SQL after parameters to the GeoPackage writer to support these types of database operations?
It would be really helpful in the “Search in Workspace” Function would include an option to also search through all populated Feature Caches in the Workspace.Related to this it would also be great if there were more search parameters like “whole word”/”match case”/”regular expression”.
I’d like to request a feature for the AttributeManager transformer (or all tables really) that allows users to export the hover table output (attribute actions table) directly to the clipboard. This would make it much easier to document, share, and review attribute configuration settings outside of FME, especially for workspace audits and reporting. Ideally, this could be enabled via a right-click menu or a dedicated export button.This would be very useful for the amount of documentation I have to do for all my Workspaces.
Hi!Thew new FME Form GUI is amazing, thanks! Could you consider bringing back some colors to the navigator to distinguish more easily the Reader/Writer part to the parameter part and also the enable vs disabled status? Thanks!
The Safe Software Product Team is actively looking at the possibility of adding support for B-Spline geometry natively to the FME Geometry Model.Currently, we read in BSpline Curves in FME from MicroStation DGN files for example, by stroking the B-Spline into line segments, which FME then store as lines, which might not be what you want in your output if your target format or system does support this geometry natively. Currently B-Splines are read as stroked lines. Image markup is only an example for visualizing. Are you someone who uses AutoCAD DWG, MicroStation DGN, IFC files or other formats/systems where you encounter B-Spline curves? Do you care about bézier and NURBS curves (but really, do you?)? If any of the above sounds like you, especially about B-Splines, please drop us a comment if you’d be open to being contacted to provide feedback and early testing!
The ISO-8601 standard for week numbers in the DateTimeConverter is missing the Week 01 - 53 implementation, where week 01 is the one with the first Thursday of the year. This is referred to as %V in other scripting languages. Can this be added as a DateTime function?
Hi,It would be a nice feature to add support for SLD files. They're XML files, so it ought to be fairly straight forward.Some sort of cross-format support to input/output styles handled by the various style transformers, so I could e.g. read an SLD at designate it to output as MapInfo styles directly, or e.g. output an SLD file based on MapInfo styles, would also be very neat. This is nice-to-have though, and may be a little more complicated.Note that there may be version issues to consider.If this can be achieved by packaging some templaters etc., that's great too.Cheers.
Some general improvements for the Terminator transformer I am thinking of:The ability to terminate with a FME_FAILURE or ABORTED or maybe even a new TERMINATED status (relevant for Server). An FME_FAILURE happens when FME crashes or experiences some other problem (e.g. missing transformer). When the Terminator caused the workspace to quit, this typically happens because of a "user handled exception", which might also be interpreted as a cancellation, but now it's always FME_FAILURE as well. Either way, it gives me better insight in what went wrong if this status type could be changed.The ability to set custom data that should be sent upon failure, which can then be used as the "Data To Post" for notification topics. Upon failure, nothing gets written to the "Data To Post" writer, but it would be nice if we could at least get something back. In this case, that would be the custom data that was set in the Terminator.I would like the error message that I specified in the Terminator to stay exactly the way it is. When a job terminates on Server, it passes the Termination Message on to the statusMessage attribute from the job result. Just like in workbench, it always prefixes this message with "<Transformer Name>: Aborting Translation as directed by mapping file. Message is ...". I would love to see that prefix removed, because now I need to remove it myself since it is confusing to an end user who is not familiar with FME. Might as well officially integrate the functionality of the MessageLogger by 1Spatial.Any other suggestions...?
Adding the row number on the interface helps you to avoid errors or forget something.For example, row number to check the amount of conditions that the Tester has.Moreover, highlight the row number if the attribute name already exists.
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.
