Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Would be really nice to have the option to set the log level at FME server instead of have each job log differently based on what the user's options were set to when they uploaded it. This would help with consistency, and allow those who want debug level logs for each job to keep those.
When you read in a CAD file, it reads EVERYTHING, including entities that are not used in the file but still remain. These ‘purgeable’ features can add a significant burden to the Workspace right off the bat. Especially when working with a large number of files, these unpurged entities can crash your Workspace (ask me how I know). It may also be worth it to add some extra handling to prevent errors from killing the process.If we had a checkbox to filter these entities and maybe output to a separate port, this would be a huge boost to efficiency, with the added bonus of a clean file being written out!
This is a point cloud format that is often converted to LAS. Format spec: https://nsgreg.nga.mil/doc/view?i=4202
Could it be possible to create a transformer that uses AI image recognition to georeference for example aerial images? AI detects similarities between image and reference imagery and creates reference points that can be used in georeferencing.
A trigger for GCP buckets.
Migrate the history of jobs with logs in the backup and therefore in the restoration would ensure the continuity of production during a product version upgrade. This step is fundamental in monitoring production events (anomaly, justification, etc.)Tanks!
To add the current date and time into the name of the log fie, you have to use a scripted parameter using Python or Tcl.As not all of us are able to do so, I would like to see a setting in the FME Options panel, that enables suffixing the Log File Name with the current date and time.Preferred would be the ability to choose a format for the TimeStamp.
Sometimes it would be very helpful in Data Inspector if it were possible to step through the selected features with an automatic zoom to each selected feature in the view window.At the moment it requires 2 clicks. One click for the next feature in the Feature Info window and a second click for each new feature on the "zoom to selected feature" button.
When running with feature Cashing to a selected transformer, I some time want to run to the same transformer again even if nothing has changed in the workspace except for the data source. Even if the DataSource has changed, the workspace will not run from start, but instead it runs the cashed source data. I would therefore like to be able to empty the cash with just one click, without having to run the workspace without feature cashing and stop the workspace immediatly to empty cashe, or run between selected. Shift + F5 empty the cashe, but runs the whole workspace, but instead I just want to empty the cashe and run with feature cashing again.
Named connections (database and web) get uploaded to FME Server along with the workspace but I have a lot of named connections that I've defined on Desktop that are not actively used in a workspace (ie. different versions of connections for DEV, TEST, QA, PROD) and there's no easy way to get them all up onto FME Server.I would like a mechanism to allow me to sync named connections between Desktop and Server without needing to publish a workspace.
It would be nice to have the ability to utilize connections that are on FME Server within your FME Desktop workflows. This would be nice as it makes managing connections for FME Server Admins/Publishers easier. It also feeds into the mentality of create once, allow users access. It also would provide security by allowing users to utilize it in their workflows without having to provide credentials to access it.Currently if someone creates a named connection in their workspace (that is different from the one up on Server, even with the same user) and uploads it, it will still need to be authorized (ie. ArcGIS Online User).
FME Flow Resource connections can be named with dash characters (example: my-resource), however, you cannot use dash characters in User Parameters. This means you cannot reference that Shared Resource Connection as a Private Parameter to be used locally in FME Form
As I worked to resolve errors with attempting to reference a User Parameter from within a Python Scripted User Parameter, I discovered the issue was previously mentioned 5 years ago in this thread: When I double-clicked on a user parameter (‘DAYS_PRIOR’) in version 2023.2.1 (build 23774) within the Python Scripted Configuration interface, FME Form inserted: FME_MacroValues['DAYS_PRIOR']In order to get the scripted parameter to function properly, I ended up changing the call to: fme.macroValues['DAYS_PRIOR']I also had to explicitly import the fme library.
When using an ESRI Geodatabase (ArcSDE Geodb) reader (or other formats that support aliases as well) set to read the schema it would be great if the alias names of the fields are stored in the list as well. The Alias Mode now has two options:Replace Attribute Names With Aliases → this will replace the attribute names in the schemaExpose Aliases as Metadata Attributes → this only works for data and not the schema If I have an attribute 'ElevationUOM’ with alias ‘Unit of Measurement for Elevation' I would like the schema to haveattribute{0}.name = ElevationUOMattribute{0}.alias = Unit of Measurement for Elevation
I have recently being creating some custom HTML reports, combining the output of an HTMLReportGenerator with some additional scripts to add custom graphics. Having zero HTML experience, I created these scripts in ChatGPT and then parameterized them for use in my template. This template is then streamed into a web browser as the output of a Flow web app. It strikes me that HTML functionality could be a incredibly useful extension to the current capabilities of AI Assist.
The GeometryReplacer accepts GeoJSON as an input format but will fail if _full _ compliant GeoJSON is supplied. Instead, the GeometryReplacer expects just the geometry component of the GeoJSON, which means this needs to be extracted from the JSON somehow prior to being passed into the GeometryReplacer.It would be great if the GeometryReplacer could be enhanced to accept any valid GeoJSON.If the GeoJSON is a multi-feature object, then the GeometryReplacer could either create aggregate geometry, or provide an option to create multiple FME features.There are several questions in the FME Community about this. Here's an example:https://community.safe.com/s/question/0D54Q00008IYY6fSAH/error-converting-geojson-to-geometry-using-geometryreplacer-invalidparametergeometrysource
FME is not recognised enough in the BIM world.It would be interesting to have it certified as an IFC compliant application for IFC2x3 and IFC4 specifications.https://www.buildingsmart.org/compliance/software-certification/
At this moment all saved database connections are available as soon as you open FME workspace. So once someone is able to enter your device, he is also able to enter all databases you ever entered as a database connection. It is possible to use embedded connections without saving the password as an bad alternative, but this is no practical workaround since you'd have to enter the password on every run. Besides that it requires a lot of extra maintenance upon changing database credentials. Another alternative would be to add a password to your fme workspace, but this only works for existing workspaces, while database connections also can be used in a new FME workspace.My suggestion/idea is to add a master password for all databaseconnections which has to be entered once every time a database connection is used for the first time within a session. You can compare it to a master password like Bitwarden, Keepass or any other key vault uses. I think without this master password on the database connections, FME currently contains a big security vulnerability. So hopefully this feature can be added soon!
I would like to see an option added to FME Form where I could specify a Flow or Flow Hosted connection as my "defaults for FME Server parameters". This would make it easier when developing new Form Workspaces to test locally against the paths that my user will have access to in FME Flow or Flow Hosted. I don't think this should override the option to set these manually, but having an option on the toolbar to match them to an FME Flow, or clear them where they match the FME Flow would be useful for testing and when preparing for publishing to a multi-tier environment.
I number of software packages I have used have a collaboration tool to allow multiple users to work on the development of a project over the internet (eg Unity game engine). Would be great if FME had this funtionality.
How about creating "global" features like a dictionnary accessible from anywhere instead of a variable (like accessing the previous feature with @Value(feature[-1]._creation_instance)? This would help to limit multiple joins.Close ideas:https://community.safe.com/s/idea/0874Q000000TlDuQAK/detailhttps://community.safe.com/s/idea/0874Q000000TkqEQAS/detail
The Minecraft Writer only allows to generate worlds for the desktop version of Minecraft.What about the other platforms? (playstation, xbox etc.).Are there any plannings to support these formats as well?
Create a portal to transport data within the workspace by preventing processing lines from crossing. For an inbound portal, there can be one or more outbound portals. The Portal would be a circular element with the ID written in the middle.
FME is an awesome ETL tool that is very efficient at transforming data. However, when moving large datasets on a schedule from on-site GIS databases over the WAN to cloud databases it has to reprocess and re-trasmit all of the data while very little of it has changed. For popular database sources (e.g. Postgres, Oracle, SQL Server) it would be optimal to mine database logs to only process the data deltas from the last time the workspace ran, instead of the entire dataset. This would greatly reduce the time required and data volumes to be transmitted.
Ideally if the fmeobjects.so had docstring compiled it might be possible to stubgen a .pyi file from it. As it is, it is a black box. While the python API docs are good it would be helpful to have access to the signatures and types within an authoring package. I don't currently have this.
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.
