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.
It would be good to replace the attribute value mapper with a ‘bulk attribute value mapper’ tool that could do the following: 1. Instead of importing data and it being static - it would be good for the tool to reference a db table/file dynamically so as to always pull in the latest data. 2. Instead of only handling one attribute at a time, it would be good to update multiple attributes at once from multiple lookup locations. Examples Source AttributeDatabase/FileFeatureTypeLookup Code AttributeLookup Value AttributeMATERIALOracle GIS_DBLU_MATERIALLCODELVALUEBEDDINGBeddingLookup.xlsxSheet 1CodeValue In this example the Material AC would be value mapped to Asbestos Cement and the bedding type SND would be value mapped SandI understand that this can be done at the moment using a series of feature mergers with process duplicates enables, but this is something that comes up quite frequently as we have multiple datasources that only store the codes and regularly need to be updates to have the description field.
This would be a transformer that would simply unexposed all attributes without having to do it manually like in AttributeExposer or PythonCaller. Not sure why this is not an option and why they have made it so hard to do things dynamically with new attributes when the schema changes.
The Safe Software Product Team is looking into the possibility of developing a Connector for 12d Synergy. Right now, FME Form ships with a 12d Model Reader and Writer, which enables users to work with their .12dxml design files. This Reader and Writer, however, does not work with the 12d Synergy system which means that users are missing out on the storage, metadata, and permissions capabilities that 12d Synergy provides. Either that, or users are having to create an API connection and workaround workflows which can create extra overhead. We are looking for users who:Would love to see a 12d Synergy Connector: please upvote this Idea! Would be interested in being contacted to participate in early testing and providing feedback: please comment on this Idea!
The Date time conversion takes only single input type (FME, ISO or dd/mm/yyyy etc.) It does not allow or take multiple input types. Many times, the input data (Excel files, CSV files) comes with different string for date type field resulting the date time conversion rejection. To address the issue with the date type we have created a custom transformer. The custom transformer uses the FME “Date Time conversion” transformer multiple times with different input type for rejected part. If the FME “Date Time conversion” gets enhancement to support multiple input date types the workspace will be simplified and will improve the performance also.
The SQLExecutor / SQLCreator should support bind variables rather than string substitution in SQL statements for the following two reasons:Security, preventing injection attacksPerformance, see http://www.akadia.com/services/ora_bind_variables.htmlI suggest making bind or string substitution an option within the SQLExecutor.
An Export Action Item completes the backup FeatureServer item type workflow into a local computer or another cloud storage system like S3 or OneDrive.The portal UI for this Action Item is shown below:The backup workflow would be a combination of Export, Download, and Delete action items. Adding a List Action item in the beginning would complete a batch export and download.In addition the Export Action item can be used to download formats of the FeatureServer for use in other clients beside ESRI applications.The best part to the export API (on FGDB), it includes the attachments, if there’s any.Reference: https://developers.arcgis.com/rest/users-groups-and-items/export-item/ Current available solution is the Hub transformer from Abley. Its a great tool but it’s limited to FGDB. Quite the obvious after all since its called ArcGIS_AP_FILEGDBExport.
I'm using FME Desktop 2020 and have a workbench with several SQLExecutor transformers. These are performing 1000s of SQL queries against a PostGIS database and working fine. The only issue I have is that every SQL statement is being logged in the FME log, which is creating a bloated log file (100s of MBs in size). I don't need to see the individual SQL statements in the FME log, but these are coming through as INFO level messages (I would actually class this type of logging as DEBUG not INFO level log messages). I know there are options to turn off INFO messages, but other INFO messages may be useful. So it would be beneficial to either:Treat logging of SQL statements as DEBUG level messages so that they do not get logged with the default INFO level set.Have an option to turn off logging of SQL statements globally.Have an option to turn off logging of SQL statements on the individual transformers (e.g. SQLExecutor, SQLCreator).This would prevent bloated log files when hundreds/thousands of SQL statements are executed during a workbench run.
We need a reader for the format of Nemetscheck Vectorworks *.vwx. We would like to be able to read out project files directly and not have to go via the DXF/DWG export.
When using the Parallel processing option in FME the number of threads always depends on the number of cores of the machine. For example 'Moderate' is one process per core on the machine. If your machine has a tonne of core you can potentially get a tonne of threads. This is really nice on one hand but on the other hand maybe you want to restrict the process to just a few threads. Especially if the process is memory intensive and the machine perhaps doesn't have enough to support so many parallel threads.If you want to restrict your process to a certain number of threads then you need to do a few backflips in order to figure out which level or parallel processing to use and in the end the least you can use is half the number of available cores.It would be pretty nice to be able to just specify the number of parallel processes you want to be able to use.
Hi there, It would be a good idea to allow to remove attributes after they have been used in a transformer. For example, I could keep an attribute to be used in a tester transformer, and once it is used in the tester transformer I don’t need it anymore so I set up an ‘AttributeRemover’ afterwards to remove the attribute. Doing this often clutters up the workspace, so it would be good to have a checkbox inside a transformer to remove the attribute after it has been used within a transformer so no need to have an attribute remover afterwards. This can apply to any transformer that uses an attribute, like AttributeCreator, StringConcatenator etc.
Add Writer for ArcGIS Pro Layer (.lyrx) format.
Would it be possible to add the “Measure Distance” tool that we have in the Data Inspector in the Visual Preview window of the workbench?It would be really helpful when deciding what distance needs to be chosen for any tolerance parameter.Thank you!
Yet another geocoder you say, well yes, but the Placekey service does offer some enrichment.Placekeys encode both what is at a location plus where it is in a resolution 10 H3 cell.If you include a location name (aka POI name) in your query the response can include base placekey, address placekey and building placekey, all potentially different.My understanding is this is backed by the SafeGraph Places database, so you are getting a POI validation service with the geocode.
When updating several workspaces including several custom transformers, I’d love to see these enhancements to make upgrading faster:Upgrade all the transformers inside embedded custom transformers from the Main view. Now the user has to go to each custom transformer tab, and upgrade the transformers separately. Disable warning when upgrading multiple transformers, and automatically create a backup. Many users are already aware of the risks. Perhaps add an option to disable it in FME Options. Disable Transformer Upgrade report. You could similarly disable the report in FME Options with an option to automatically export the upgrade report.Hope to see these enhancements in a future FME version!
ArcGIS Server has a web page where you can "Validate Data Stores". You can test the connections to all of the databases that you have in your ArcGIS Server with a few clicks. This would be a great feature for FME Server.
I would love for the bookmarks to snap to the grid when they are created Would be a small change, but big QoL update !
Using FME as a mail merge tool to fill in form content to a word document with pre-defined fields would be great. Currently the data has to be written to excel then mail merged to the template document. It would be good to do this within FME.
As FME continues to grow in popularity and power, it would be incredibly valuable to have an official FME mobile app that connects users more closely with both the community and their FME workflows. ield teams can stay connected and monitor automation workflows. New users can learn anytime, anywhere. Community engagement will increase, especially for those using mobile devices. It enhances the overall reach and impact of the FME platform. I believe this app could significantly enhance the FME ecosystem and empower both professionals and learners in more flexible, modern ways.Looking forward to the community’s thoughts and Safe Software’s consideration!
Hi there,In ArcGIS Online/Portal if you are writing to a feature service, and that feature service already exists, then almost always you want to write to an existing layer. However the current workflow is:Add writer Add bogus feature type Import Feature type from existing layers Delete bogus feature typeI feel like this could be optimised. When you add a Portal/Agol Writer, and you choose an existing feature service, you should be prompted to select from the existing layers from that feature service.This would be a great quality of life update for people that write to Esri Web Layers often.Thanks,Marc
Currently FME can’t guess a format, if the dataset is a zip file, and the user has to select the Format manually.
I’ve become a fan of AI assist, particularly for writing regex. However, I note that on returning to a workspace after a break, I can’t remember exactly what the prompt I gave it was.Might be useful to be able to expose that prompt as an annotation or as a comment within the transformer, as I see now with certain transformers.
When joining data sources with lots of attributes, it can be a little difficult to track what came from where. One potential solution would be to be able to add a coloured tag based upon the input. E.g.
When accessing the FME Flow WebUI, the initial focus should be set to the username field again.This used to be the case.Currently, it takes four tabs to get there. This isn't particularly user-friendly.
It would be really helpful if the FME Flow RUN WORKSPACE UI could display the workspace start time directly during runtime.I think switching to the log for this is a possibility but unnecessary.
Currently, searching for a location in a workspace app’s geometry parameter window appends the search bar contents to Nominatim’s URL. Example 1:Nominatim URL: https://nominatim.openstreetmap.org/ Search entered in workspace app: “vancouver” Appended Content: “search.php?q=vancouver&format=jsonv2” Resulting GET request: https://nominatim.openstreetmap.org/search.php?q=vancouver&format=jsonv2 What gets appended does not allow users or workspace app authors to include additional parameters limiting users’ search results in the Nominatim URL. Adding parameters that are compatible with the q parameter such as countrycodes, limit, and layer to the Nominatim URL breaks the resulting GET request. Example 2:Nominatim URL with parameters added: https://nominatim.openstreetmap.org/search.php?countrycodes=ca&limit=1 Search entered in workspace app: “vancouver” Appended Content: “search.php?q=vancouver&format=jsonv2” Resulting GET request (invalid): https://nominatim.openstreetmap.org/search.php?countrycodes=ca&limit=1search.php?q=vancouver&format=jsonv2 FME Flow should check if the Nominatim URL already includes parameters designed to limit users’ search results before deciding what to append so the final result is always a valid GET request such as: https://nominatim.openstreetmap.org/search.php?countrycodes=ca&limit=1&q=vancouver&format=jsonv2 The current workaround is to add the additional parameters in the search bar. Example: “vancouver&countrycodes=ca&limit=1” This is cumbersome for users. Posted from:
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.
