Shape the future of FME with your ideas
Open ideas have been reviewed by our Customer Success team and are open for commenting and voting.
I like to have the option to disable (and enable of course) parameters.For example specific user parameters. So not all user parameters at once, but very specific user parameters in the User Parameter management window.
Hi there, When using readers in a larger workspace, sometimes I might need to reference the reader (or a bookmark involving the reader after some post processing like changing coordinate system or renaming some attributes) multiple times in the workspace, either at the start, middle, or end. If something is being used, say 5 times, and crosses multiple bookmarks and transformers, I will use hidden connections to keep things readable, however it can still be a hassle if I need to use a certain reader/transformer/junction that is at a certain place in a large workspace, where I might currently be working in another area. I will then need to zoom out and scroll to it, and then drag the connection all the way over to where I want to use it. A way to get around this, is to have the ability to pin readers/transformers/junctions that are used a lot in a workspace and have many connections already, so that if it needs to be used again, you can simply connect to it wherever it is pinned in the window (and then can unpin it again after that if preferred), so that you can connect to any part of a workspace from any other location without having zoom in and out and scroll and repeat, just to create one connection Cheers!
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!
It would be nice if FME Server supported the modern, standardized OpenID Connect authentication technology to enhance the security experience of logging into FME Server.
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.
Just for clarification - this is not about fme workspace parameters, rather about SQL named parameters.Named parameters provides better security against SQL injection, improved query plan caching, ensures proper type handling among other things. Another advantage is that it makes it easier to just copy/paste the sql-code from a sql editor (like ADS, Dbeaver etc) where one would be provided with prompts to fill in the parameters.It would be amazing if one just name a sql paramter the same as an attribute in the feature, and it would be picked up that way… !
Hi there, Sometimes in a large workspace, I need to zoom out and select a large area of transformers (to either create a bookmark, select them to move or delete, etc.), however at a certain zoom level I don’t have the granularity to control exactly what I’m selecting (I might be selecting things that I don’t want to select, then I need to zoom in and unselect these things). It would be helpful, at a certain level of zooming out a workspace, to show a little pop up window when you start clicking and dragging the cursor to select things, so that you can see where in the workspace the cursor is and then control what is being selected. Cheers
Hi there, I’ve built workspaces for clients that I need to go over and show them. It is very helpful if I add annotations and bookmarks so the client can follow along with me. However, in a workspace a lot of secondary or unimportant transformers are used (things that are not useful for a client to see to understand the logic of a workspace - think things like attribute removers, csmapreprojectors, list exploders, area and gap overlap cleaners, etc.) It would be nice to have a tickbox inside a transformer to mark the transformer as important to the workspace. So then there could be a toggle to select that could, say, highlight all the important transformers (a different colour, a glow etc.), or it could generate a separate, collaborative workspace that you can use to go over with clients, that just show the important transformers that have been tagged, this can act as a sort of ‘pseudocode’ for FME Cheers,
hi there, it could be a good idea to be able to add pinned annotations on a workbench for important messages or things to keep in mind for a workbench, so that no matter where you scroll in the workbench the pinned annotation will show in the exact same place. Ideally the annotations would be around the sides of the workspace frame
Hi there, Can we add a way to manually create the shape of a bookmark, not just a rectangle. When bookmarking transformers, rectangles can make a lot of wasted space and can make large workflows too spread out, whereas creating custom shapes or a nice fit (can use an auto-fit option) can allow space to be used more effectively in the workflow.
hi there,I am working on a translation for some heavy 3d data. This creates lag when I want to check on some feature attributes in the visual preview window as FME has to load the geometry in the graphical preview window.I would like to turn this off so I can just see the table and not the geometry.Thanks,Marc
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.
In a number of situations schema scanning and bulk mode can drastically decrease performance.One example is when reading a few records from a database with big blobs and writing to another database (postgres to postgres in this case). Reorganizing records into feature tables and then reorganizing them back into records at once was in one case causing a lot of unnecessary work and io.By editing the metafile for postgres we could avoid this but tampering with the installation-files is probable often very inconvenient.. Having the option to configure readers and transformers in this aspect would really help. It would also help in many situations to be able to control of the process of supplying the schema.One example here is the SQLExecutor-transformer. The extra execution of the SQL-statement that take place in order to resolve schema could have side-effects that can be hard to forsee. I’d vote for making this “not default behaviour” and also marked as advanced. Another idea here could be to give the developer some support to specify (and validate?) a “canned schema” instead. To summerize - convenience should in my opinion never stand in the way of fine grained control and I belive that the promotion of bulk mode and dynamic schema has in some situations led to that.
In a number of situations schema scanning and bulk mode can drastically decrease performance.One example is when reading a few records from a database with big blobs and writing to another database (postgres to postgres in this case). Reorganizing records into feature tables and then reorganizing them back into records at once was in one case causing a lot of unnecessary work and io.By editing the metafile for postgres we could avoid this but tampering with the installation-files is probable often very inconvenient.. Having the option to configure readers and transformers in this aspect would really help.It would also help in many situations to be able to control of the process of supplying the schema.One example here is the SQLExecutor/transformer. The extra execution of the SQL statement that take place in order to resolve schema could have side effects that can be hard to forsee. I’d vote for making this "not default behaviour" and also marked as advanced. Another idea here could be to give the developer some support to specify (and validate?) a "canned schema" instead. To summarize: convenience should in my opinion never stand in the way of fine grained control and I belive that the promotion of bulk mode and dynamic schema has in some situations led to that.
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!
In FME Server 2019 on the email subscriptions protocol settings there is a drop down Load Template menu to populate some of the settings as per popular email services.It would be nice if we could add a custom template to that list, to use when setting up new subscriptions, rather than having to duplicate an existing subscription.
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.
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.
