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 submitted this question 5 yrs ago. Still not a solid solution for this issue. To date i have had to create 3 different systems (matching records) between, autodesk, esri, fme and trimble. And for some unexplained reason fme started obfuscating their naming system when you use CSExtractor to Coordinate System `_UTM83-13_0' parameters: CS_NAME=`_UTM83-13_0' CS_ORIGINAL_NAME=`UTM83-13' But the Idea is. Add a method of smartly matching the trimble projection found in the jxl to the fme espg, or esri or even autodesk projection. Find a way to standardize this. I know if i try to project something to the incorrect project it tells me outside of coordinates. It seems there are many ways to get these matched especially when there is an existing system name.https://docs.safe.com/fme/html/FME-Form-Documentation/FME-ReadersWriters/jobxml/jobxml.htm this indicates that coordinate systems are now supported in jxl. is that the case?
It would be helpful if FME Server 2017 had an SFTP Watcher. Currently the regular FTP Watcher does not support SFTP. I am aware that the Notification Service supports SFTP subscriptions but currently in 2017.0.1.1 there is no corresponding SFTP publication option.
Hi,Is there any way to optimize the FME Inspector?In my case, I'm opening a DWG containing approximately 600,000 features, and it takes nearly 7 minutes to open.It appears that the Inspector indexes all attribute columns when the dataset is loaded. In some cases, I don't think this is necessary, especially when working with very large datasets.It would be great to have an option to disable attribute indexing for large datasets, or even better, allow users to select which attributes should be indexed when needed. I believe this could significantly improve loading performance for large files.Is there already an option to control this behavior, or would this be a good feature request?Thanks!
I've noticed that the Safe Software YouTube channel has recently started publishing more short tips, tricks, and workflow videos, which is great to see. I really appreciate the effort to create more educational content for the FME community.I do have a few suggestions that I think could make these videos even more engaging and effective.1. Audio qualityThe biggest issue, in my opinion, is the sound quality. It often sounds like it was recorded with a fairly basic microphone and includes noticeable background noise. Since audio quality has a huge impact on viewer retention, investing in a better microphone, cleaner recording setup, or basic audio post-processing would make a significant difference.2. Editing and pacingMany videos feel longer than necessary. Tips that could often be explained in 30–60 seconds are sometimes stretched to 3–5 minutes. Today's audiences are used to concise, information-dense content, so tighter editing and faster pacing would likely make the videos more useful and easier to watch.3. Overall production qualityThe videos would also benefit from a more polished production style. A simple screen recording is useful, but adding zoom-ins, highlights, annotations, quick cuts, clearer structure, or occasional graphics would help viewers focus on the key points.If video production is not a primary focus for the internal team, it might be worth collaborating with someone who specializes in educational video production, YouTube content, or short-form technical content. Even a small improvement in production quality could make the videos feel more professional and help present FME in the best possible light.The technical content itself is valuable. I simply think that better audio, tighter editing, faster pacing, and a more polished presentation would help these videos reach a wider audience and make them more enjoyable to watch.Thanks again for creating more content for the FME community. I hope you'll continue publishing more videos.
It would be nice to add tunnels to FME Flow Automations like you can with FME Form workspaces. It would help organize complex automations and make them fit better in the UI.
A function to enable|disable the Startup|Shutdown Python Script at once would be desirable.It is always very expensive if you have to comment out all lines just jor testing
We are interested in the integration of the data format INTREST (=intermodal referencing system for traffic related data). Background is: traffic routing with FME. Thank you in advance
add webservice definitions to FME Flow roles, so we can control who can access them, it seems if you use FME Flow as connection storage for FME Form, connections are controlled by roles, but anyone can see and use any webservice definition. If I am wrong about this, then this idea can be dropped.
In recent security audit, one of the concerns was with the FME Server log-in.As there is no limit on the amount of retries, the login can be brute-forced.Please add a toggle and a parameter for limited login-retries, just like 'Password Policy' in the system configuration.Perhaps also adjust the system-event to only trigger after a set number of attempts, and have the IP-address of the source as one of the keys.Kind regards,Martin
I would like to have the ability to transfer ownership of all items (eg. workspace, automation, app, schedule, connections) to another user in FME Flow.At the moment, we use Azure DevOps agent to publish our content to FME Flow and it has to use the username/password of that account. Our security guys would like to see this more granular (eg. devops account publish the content and then transfer ownership to another account to own the content) to see who/where the interactions occur within the platform. Thanks
To connect to a PostgreSQL database, many tools allow to use a pgpass file (https://www.postgresql.org/docs/current/libpq-pgpass.html) or a pg_service file (https://www.postgresql.org/docs/current/libpq-pgservice.html).It could be great to use such files in FME with the postgresql reader/writer and the SQL executor.Three options :Use the selected connexion (current behaviour) Use the pgpass file, fme display a form to set infromations on the connexion and use the selected pgpass line corresponding to the data specified in FME (nothing = 1st line, host or host+port or host+port+user or host+port+user+db = 1st corresponding line) to get the required data to connect For pg_service file, fme display a “service name” input and use the configuration specified by the service name.
An option in the BulkAttributeRemover to remove Unexposed attributes only would be useful.Some transformer eg.: JSONFlattener or JSONFragmenter create all new (potentially unknown) attributes, even though usually the exposed ones are used only - which may be excessive. Now the exposed attributes must be (bulk) renamed before bulk removing the unexposed, but prefixed attributes.An alternative way would be adding a “create Exposed attributes only” option in these transformers, so they wouldn’t even create unnecessary attributes..
The following improvements to Role Based Security would be useful:1.Increased Granularity for Job Viewing and Job Management PermissionsI need the ability to allow users to see specific other user’s jobs and logs rather than all jobs and logs. We use different service accounts for different enterprise projects and currently I am having to share all jobs/logs with users so they can monitor their processes. Since not all groups need to see each other’s jobs this is not the best solution. (Thank you Safe for new search options in 2019 as they slightly help with this issue.)Likewise, in the current Role system being able to view all jobs requires job management permissions which let users cancel jobs in the queue or terminate running jobs. This puts me in a difficult position regarding how we implement SOX compliance. It is preferred users be locked out from managing running production processes. If the ability to view all logs but not manage jobs was made available that would be a move in a positive direction. If the option to say kill queued jobs but not running jobs was an option that may also be useful.2. Additional Options on Database ConnectionsHaving a Read option alongside the Full Control option for database connections would be excellent. I am seeing issues when I grant users access to connections without giving them full control over a connection. Since we have many processes using the same named database connection it is not ideal to grant users management access since one incorrect change by any user with access could disrupt jobs for all users using the connection. Something similar to how the Notification items are broken out would be amazing.3. Automatic Content Sharing with Administrator AccountsIt would be helpful if FME Server automatically shared user created content with members of the Super User role. If this could be an option for the FME Admin role that would also be appreciated. I have a plethora of users creating content and when they ask for help it is cumbersome to have to share their content with myself and my fellow Admins before I can help troubleshoot.
To Clear the entire feature cache a user has to go to the first transformer, right click it and select clear data cache. Or start and stop the translation quickly.I’d like the option to clear the entire cache when I right click anywhere in the canvas and additionally a clear cache button in the toolbar would be nice.This would help speed up the development process and improve user workflow for a feature that already exists but could be improved.
I’d like to suggest FME exposes the Database Spatial Tolerance in the Feature Information window, alongside the projection, dimension, min/max extents etc.This information is critical when understanding spatial filtering, and can account for features being inside or outside specific areas of interest when using a spatial filter within a Reader/FeatureReader, and gives context to the features being retrieved.In Oracle, this would mean reading the sdo_metadata table in the database, but other database types would require differing tables to be read. It would also be useful for FME to perform a simple calculation using the projection and the tolerance together, and write a warning message in the translation log if the tolerance (on the ground) is of a large distance - especially useful when spatially filtering data.Thanks,
The Readers now give out more warnings than before, it’s becoming an issue for some when monitoring from FME Flow or when someone who isn’t a daily FME user needs to run a workflow.A way to tone down those types of warning would be a great addition, because sometime the warnings are actually meaningfull and we don’t want to have look at all the jobs or remember that X numbers of warning for this specific workspace are meaningless. Two examples are these: Spatial and Non Spatial Reader/Writer got merged together, if you don’t have a spatial component it warns you about it each time, but it’s useless.Oracle Reader: Username and Password in lower case cause a warning that can be interpretted as an error (copied the error from an older post)
In the Autodesk AutoCAD DWG/DXF-writer (and in the other DWG writers too) it would be good if you could choose an attribute for Layer Description, Default Linetype, Default Color and the states: On, Frozen, Hidden, Locked, Plottable. It's not so usable right now when you need to hard code these values which makes all layers look the same.
I’m interested in using FME Flow for Connection Storage in FME Workbench.We have a single FME Flow instance that does not have redundancy. I’m concerned that if Flow is unavailable, that FME Workbench will effectively also be rendered unusable if I use Flow for connection storage, based on what I’ve read in the documentation.Further, FME Form provides me a sort of redundancy at the moment - if Flow is unavailable or if the engines are consumed, I can run my processes locally, as a last resort. In my understanding, moving my connections to Flow would remove this redundancy and leave me more vulnerable to network/infrastructure/system issues.If the above is true, would it be possible to maintain a local cache of connections, similar to the default Personal Database Connection Storage, where it prompts for and perhaps even requires connection and syncing to Flow, but has some sort of fail-back mechanism in the event of failure?I could keep an export of connections locally, or a Shared Database copy, but this will go stale and defeats the purpose of the FME Flow option, I imagine.Thanks for any thoughts or corrections on the above.
As I have many jobs running and a lot doing well, I frequently is called on Failed jobs that are deep in the line and I happen to have a message of the server telling me“Error: The log file for job ID ‘290047’ does not exist”I don’t want to give more space to my logs in general but would appreciate to have the logs of jobs which raised errors (and maybe warnings) longer. FME Flow can destroy logs for OK jobs and keep the error ones longer.
Hi,We have a large SharePoint deployment. The site dialog does not have a search button. The document library does. I suggest you add search to the site dialog. Thanks,Marc
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...?
The FME ArcGIS Online writer should expose a time zone setting that allows you to set the time zone of your data when publishing or appending data. By default, ArcGIS Online assumes all data is stored in UTC but when publishing directly to ArcGIS Online through the UI or using the ArcGIS Python API the time zone can be set to the time zone of your data. This setting in the writer would allow dates to be published and updated accurately.
In the current situation + Finland & Sweden joining NATO there is more demand to support Nato Vector Graphics (NVG) -format. Just read a RFP where it’s a must and waiting for more similar RFP’s to come. It’s not just the military people who ask for it, it’s also e.g. border control and who ever is providing services for them.
When writing PDF it would be good if I could choose to write PDF/A version of the files. PDF/A is an ISO standard specialized for the digital preservation of electronic documents and in several cases it's a requirement when delivering PDF-files to a customer.
Please vote for this format if you think it should be in FME: https://www.geonovum.nl/uploads/documents/220405-JSON-FG.pdf https://docs.ogc.org/DRAFTS/21-045.html
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.
