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 use feature caching extensively while developing and testing FME Workbench workspaces. I think something similar would be helpful for developing and testing Automations, in addition to the "Log a message" action.
Hi, it would be great to have RSS feed for these items :Forums (one feed for all post + one feed per forum)Knowlege base (same as forum : one feed for all + one feed per topic)IdeasUser groups (one feed per group)BlogRSS are really helpful to stay tuned over what's going on the community without having lots of emails...
This webinar would be about manipulating XML and JSON content using FME transformers.This idea is a potential webinar to be presented during October-December, 2022.
A pretty simple one - if data inspector (not within Workbench) had a side-by-side table view that could be useful for comparing two tables. I use inspector a lot for looking at data while building workbenches on another screen and this would be a nice enhancement to that workflow.
Exploring how FME can integrate with machine-learning and artificial-intelligence systems.This idea is a potential webinar to be presented during October-December, 2022.
A webinar about integrating CAD and GIS systems, with particular reference to MicroStation.This idea is a potential webinar to be presented during October-December, 2022. It is an updated version of a previous webinar.
It would be great if an alternate shared resource path for custom transformers could be implemented (with associated fine-grained security settings).This idea is a duplicate of:https://community.safe.com/s/bridea/a0r4Q00000FuTxPQAV/finer-control-over-fme-server-shared-resources-location-and-permissionsRe-posted to help with searches looking specifically for FME Server custom transformer configuration.
This idea is targeted to custom transformer deployment on FME Server but can be applied more generally to shared resources on FME Server.Currently, custom transformers can be deployed to either a Repository, or to the Resources > Engine > Transformers folder as a shared resource.Transformers deployed as a shared resource are available to all workspaces at runtime, which is very effective for ensuring consistency across an organisation.The issue is that there is no simple way to manage this single resource across a large organisation with multiple development groups and I'm currently working with an organisation that has the "Engine" resource folder locked down so that only administrators can upload data there, to avoid inadvertent uploading of transformers that could potentially impact multiple workspaces.It would be great if alternate shared resource paths could be implemented, either as entirely separate locations, or as sub-folders under the current path. (e.g. Engine > Transformers > [my sub-folder name]). In conjunction with this, sub-folders should allow for separate permissions than those of the main Engine folder.Implementing the above would allow for different development teams to manage their own shared resources without impacting the entire organisation, and without needing to grant blanket permissions to the entire "Engine" folder.
This is a follow on from my previous idea C658999. The latest version works well and outputs the target compression ratio used for my ECW files but the "Actual Compression Ratio" attribute is not working / does not seem to have been fixed. I am struggling to calculate the ratio myself. I have the correct formula, but I can't combine all of the necessary attributes (particularly file size) to perform the calculation. I can use some transformers to generate the file size but it takes hours if I have geometry attached, but I need the geometry for other things. I also can't subtract the header information to get a more accurate compression value. Can you please update the ECW reader to include / fix the Actual Compression Ratio. Thanks.
Workspace authors are important, but so too are the persons who install and administer FME. This webinar will suggest ways to administer FME and how to optimize your FME Server setup.This idea is a potential webinar to be presented during October-December, 2022.
As more data becomes available in three dimensions, it's possible to create town and city models that are highly detailed and realistic. But how can you integrate all that spatial data? With FME of course, and this webinar will show you how.This idea is a potential webinar to be presented during October-December, 2022.
In this webinar, we'll explore how FME can be used with Microsoft Azure web services, (particularly Data Storage and Data Management services) and cover some of the different transformers and formats that exist to support this.This idea is a potential webinar to be presented during October-December, 2022.
Here we'll look at open data portals (for example, CKAN) and how to use FME to publish data.This idea is a potential webinar to be presented during October-December, 2022.
In this webinar, we'll look at different scenarios and decide which transformers to use. In particular, we'll look at SpatialFilter vs SpatialRelator vs Clipper vs Overlayers.This idea is a potential webinar to be presented during October-December, 2022.
A series of webinars, each about how FME can work with a different database; includes Postgres, SQL Server, Azure, Snowflake, BigQuery, AWS, Aurora, etc.This idea is a potential webinar to be presented during October-December, 2022.
This webinar covers the different Reprojector transformers in FME. Which have specific purposes? How do they differ from each other?This idea is a potential webinar to be presented during October-December, 2022.
How to validate and fix address data using FME, including how to meet standards such as NENA.This idea is a potential webinar to be presented during October-December, 2022.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.