Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Cannot decode values in input field for above. Could the inclusion of extract parameters be added to a future release?
This enhancement will allow full automation of attachment backup workflows using ESRI ArcGIS feature services or geodatabase attachments being backed up to ArcGIS feature services.Currently, even with the ESRI ArcGIS package, you need to manually configure the feature service feature URL on a FeatureReader so that the features’ featureID can be passed to the ArcGISAttachment connector.Implementation would be sinmilar to the Publish Action item of the ArcGISOnlineConnector which exposes the _webservice_url
***Note from Migration:*** Original Title was: Apply "Max Feature to Read Per Feature Type" to all features listed in Feature Types to Read. Max Feature Types to Read applies to the feature types on the workbench canvas. So if you use Merge Feature Type (and only have one feature type on the canvas) then that will count as only one feature type. Say you set Max Feature Types to read to 2. If you use Merge Feature Type, only two features are read instead of two features per feature listed in the Feature Types to read parameter. Max Feature Types to Read should also be applied when Merge Feature Type Filter is used along with the Feature Types to Read.
Due to the way decimals get stored one dataset may, for example, contain 1.7 and another 1.700000003. I can tell by looking that they’re the same as the data has no more than 4 decimal places. It would be nice if the ChangeDetector had a tolerance for numbers. If I used 0.00001 for the above, as the difference between them is less than that, it would treat the data as unchanged.
Hi,I noticed that the GeoTIFF and COG writers in FME do not expose a visible option to define the TIFF predictor (PREDICTOR), equivalent to the GDAL option:-co PREDICTOR=2or-co PREDICTOR=3This option is very useful when using compressions like LZW, DEFLATE, or ZSTD, since it can significantly improve compression efficiency, especially for continuous rasters or floating-point data.For example:PREDICTOR=2 for integer data PREDICTOR=3 for Float32/Float64 dataIt would be very useful to have this option directly available in the writer interface, similar to compression, tiling, or block size settings.I think this would be a valuable improvement to make GeoTIFF and COG optimization easier and more accessible in FME.Thanks.
Please create an FME option to connect to GCP (Google Cloud Platform) using “Workload Identity Federation” method in addition to Service account (current option).Thank you!
I'm curious if there's a straightforward way to make FME lineage information accessible for data catalog systems. Have you all thought about enabling FME with OpenLineage? I’m not sure how that could work, but I’ve noticed that data catalog products are beginning to adopt this standard. Imagine how great it would be if FME could effortlessly share lineage info with popular data catalog tools like Microsoft Purview, Collibra, and Alation! This could be a game-changer for organizations that truly value solid data governance and tracking. What do you all think? Is this feasible, or are there other existing alternatives?
The FME Flow interface allows for custom System Cleanup Tasks to be created but there is currently no way to trigger these tasks to run manually. Instead, you need to wait for the automated scheduler to reach the time period defined for the Normal Conditions Task Interval, which is 1 Day by default: Being able to trigger a task manually would be very useful when creating a custom task as it would allow for rapid testing to ensure the task is correctly defined and working as expected.Please add the ability to manually trigger a cleanup task.
In large and complex FME workspaces, memory usage can become a major performance bottleneck, especially when feature caching is enabled for debugging or when large feature streams are processed sequentially.It would be incredibly useful to have a dedicated transformer (e.g., DropFeatureCache, ClearMemory, or similar) that can be placed mid-flow to explicitly clear cached data, or release memory from earlier processing paths.This would be especially helpful in long chains of transformations, loops, or branching logic where intermediate data is no longer needed but still retained in memory.
Basemapping available to our org is limited. Several are dark or the level of colour obfuscates point geoms in particular. Can we have a basemapping transparency/colour intensity setting?
As a follow-on from my question and the response from @zoe.forbes after we upgraded to 2026.1 and I found the info icon and blue banner in workspace apps have been removed for message-type user parameters. The icon and banner were useful and I think important aspects of the message parameter and outlining information in workspace apps. I haven’t found any requests to remove them and I think it is well worth restoring them.
I would like to be able to attach a role to an API token rather than having to rebuild all the permissions directly on the token.
I would want to be able to retrieve information about automation schedule.I see several similar requests in Ideas, and it looks like it was possible to do with FME Flow v3 API using schedules endpoint. I’ve tried <FME_URL>/fmeapiv4/schedules?limit=100&offset=0&includeAutomations=trueThe API call didn’t fail, however it returned only schedules and no scheduled automations. The v4 API documentation doesn’t have includeAutomations param, so I am rather surprised the call didn’t fail.The automations endpoint has nothing about triggers or schedules either.In general, it would be helpful to be able to retrieve information about automation trigger and, if the trigger is a schedule, information about the schedule. One of the use cases for this would be administration of an FME Flow hosting multiple projects and used by many users/teams. Somehow, midnight seems to be the most popular choice when scheduling automations. As a result, there is a long list of automations triggered at midnight, and if one of them gets stalled… there is a surprisingly long queue with time sensitive jobs in it in the morning. If I was able to retrieve schedule info, I would create a dashboard to monitor scheduled triggers distribution
Currently a User Parameter of type Choice can be configured as a drop-down, and the user is permitted to edit the choice, or it can be defined as a list or tree and allow multiple selection. But it cannot be both multi-select and allow choice edit.I would like the ability for the user to add values to the tree view in multi-select mode.
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.
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.
White Box Tools is an open source geoprocessing package made by the University of Guelph.Its key benefit is its extreme speed, being able to process tools between 5 and 50 times faster than ArcGIS Pro. It would extremely beneficial if FME included an WBT transformer which could allow users to pass FME data to WBT and allow the user to select which WBT to run (there are hundreds). This would greatly expand the raster capabilities of FME, and include some functionality which is currently lacking in FME (viewshed)Whitebox Geospatial
Currently FME Server is routing jobs to available engines with the round robin circulation. One of the main benefits of dynamic engines is that job can use these (only) if there is peak demand. Currently jobs can also be assigned to dynamic engines if a standard engine is available but the circulation system decides to use the dynamic engine.My suggestion is to have FME Server 'see' dynamic engines differently than standard engines to be able to only assign jobs to dynamic engines if no standard engine is available.With this we don't have to pay for standard engines that are idle most of the time, can use dynamic engines only when needed and we don't lose credits on using dynamic engines when a standard engine is available.See also discussion here.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK