Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
***Note from Migration:*** Original Title was: A transformer, which combines AttributeValueMapper, AttributeRangeMapper and TestFilter I'm using AttributeValueMapper, AttributeRangeMapper and TestFilter quite a lot, but I'm missing a transformer, which would have similar interface as AttributeValueMapper, but you could set a Test Condition to the source value like in TestFilter. If the value of the source attribute passes the test condition, the destination attribute would get the value from the corresponding Destination Value.At the moment I usually have a TestFilter with AttributeCreators for each output port of the TestFilter. AttributeValueMapper is a good tool, but lacks the capabilities of TestFilter.Of course I could use Conditional Values in e.g. AttributeManager, but they're always hidden inside the transformer.
For the HTTPCaller, the certificate authentication was introduced. (see )Is it possible to add it to the RabbitMQ Hub Transformer as well?
It would be nice if the OffsetCurveGenerator allowed you to specify Buffer Distance Units the way the Bufferer does.
There are certain situations where it would be nice to have a Group-By on the matcher and a corresponding Complete Groups When...
The issue with FME vs Shapefile datatypes has been around for nearly a decade. See It would be really nice if there was a parameter to use explicit numeric types on the reader. I should not end up with a different schema if I read a shapefile and write it dynamically, going straight from reader to writer.
Hello,The URLs of host FME Flow services used to be customable. Now only the option "Change All Hosts" is available. While simplicity and user experience is important, let’s not lose the flexibility FME Flow has offered for many years. Networks and architecture become more and more complex and dynamic in organizations.
I have multiple FME Flow instances, it’d be helpful to be able to import/export deployment parameters from/to the deployment parameter store on FME Flow. At the moment I can create via Form and Create/Remove via web interface. A nice import/Export button here with the option to overwrite would be great: Thanks!
It would be helpful to be able to execute external programs and scripts from within an automation, without having to use a workspace and accompanying engine.An example use case would be starting long-running batch jobs as part of an automation, without having to block an engine while the external job is running.In short, something like the SystemCaller but as a native automation action.
I’d like to request native support in FME for reading B3DM files, which are a core component of the OGC 3D Tiles standard. B3DM is widely used in web-based GIS applications, especially with CesiumJS and other 3D visualization platforms.Currently, FME can write 3D Tiles but cannot read them. For workflows such as converting 3D Tiles to OBJ, IFC, or CityGML, a native B3DM Reader would be extremely valuable.Direct import of B3DM would greatly enhance FME’s capabilities in 3D GIS and BIM workflows and improve interoperability with open standards. I hope this feature will be considered in a future release. Greetings Michael!
Some ArcGIS Server FeatureServices serve Relationship Classes, similar to Relationship Classes in FileGDBs.These don’t show up in the Esri ArcGIS Server Feature Service Reader, however. It would be very convenient if FME would support these Relationship Classes, as some FeatureServices don’t have foreign keys in their tables. In such cases the Relationship Class is the only way to join tables. Relationship Classes are listed in [ArcGIS Server URL]/FeatureServer/relationships. For example: ttps://basisregistraties.arcgisonline.nl/arcgis/rest/services/BAG/BAGv3/FeatureServer/relationships
Problem:FME apparently only looks in the MDSYS.USER_SDO_GEOM_METADATA table for metadata on Oracle spatial data. When it can't find this, it currently falls back to assuming data is in two dimensions. This is not ideal given the rapid increase in use of 3/4D data.FME advice currently (not updated since v2015.1) is to manually create the metadata in the USER_SDO_GEOM_METADATA table. With the release of Oracle 23ai, this is something that's no longer advised because Oracle now creates the metadata itself. This also introduces further problems when the tabe owner updates their metadata, but the user copy then won't be updated.This appears to be an assumption by FME that assumes that the database connection user is then automatically the schema/table ownerProposal:Any data using the Oracle Spatial reader should continue to first search MDSYS.USER_SDO_GEOM_METADATA and then progress to MDSYS.ALL_SDO_GEOM_METADATA should there be no valid metadata This would support this user-schema database setup, but additionally maintain any user-defined metadata where this is required.
Please add CRS EPSG 20047 BCSG2020 to the list of available CRS in ReprojectorEPSG:20047 GDA2020 / BCSG2020 -- Spatial Reference
When selecting output format JSON, datetime attributes should be default be written in ISO 8601 format. There should be no need to format each datetime attribute manually before sending to a writer.Not only is ISO 8601 the de-facto standard for JSON, but it is THE international standard for exchanging serialized dates between systems.In addition, when reading JSON, FeatureReader should detect ISO formatted dates and automatically transform them into datetime data type.
hi there,In Automations you can select multiple items and edit their tags together. This is not possible with Schedules.I would like Schedules to have the same tag management options as automations.Thanks,Marc
Being able to store the HTML, JasvaScript, CSS, or other static content in FME Flow Resources folders and serve them via Data Virtualisation Manual Endpoints directly (without a workspace that feed the Data Virtualisation Writer attributes) would be more straightforward and engine saving way to provide HTML pages, so the Workspace Endpoints could deal with the dynamic contents.OK, it needs the ability to set the content_type header as well.
Hi,Wouldn’t it be great if FME could automatically generate a link to your API docs, just like the FME Flow API does? This would make the APIs you create almost self-documenting and ensure compliance with the Dutch national API guidelines.
Hi Safe team!I think it would be handy to create some separation of job logs, between Data Virtualization and ‘standard’ FME jobs.Depending on what you create with Data Virtualization, the volume of jobs which trigger could be substantial - and I think users will have very different needs for those two categories.As an administrator, it will be very challenging to find particular ‘standard’ job(s) amongst all the DV job logs.You may also want to configure the settings quite differently for the age of logs to keep. It’s much more likely you’ll want to keep logs which trigger as a batch job weekly/monthly for a longer period of time (i.e 3 cycles so you have a comparison between jobs). Whereas with the DV job logs, they’re probably a bit more disposable, and not something you’re likely to be looking back on a few weeks/months ago for a single API request.
It would be great if the email of the user running an app could be delivered as an automation app parameter so that the person who pushed the button could easily be emailed without additional workflow or having to enter via a parameter which is open to error.
Now AttributeExposer can only add each attribute name manually.but in many cases,There are some rules for the attributes name that needs to be exposed.Therefore I suggest that add wildcards and regular expression support to AttributeExposer.
See this discussion. It would be useful if the url of FME Flow is available in an Automation as an attribute, just like it is available as a parameter in Workspace
A bit of a pipe dream, probably not possible to implement and for the most part there are workarounds, however, having some kind of compatibility mode would really help as a consultant / solution provider.When working with a large number of customers all of which have a different version of FME you need to make sure you have a lot of versions of FME installed to cater to all of them.This is mostly fine, however, with each release of FME the Installation grows in size, and, depending on the size of your disk it puts a cap on the number of different Installations you can have. If, however, I could always work with the latest version of FME (and take advantage of all the nice UI upgrades and things like workspace compare and merge like in FME 2023+) then it would really streamline the development process. Expected behaviour:When opening an old workspace in a newer version of FME a prompt asks if you'd like to open in compatibility mode.Compatibility mode would essentially be a restricted version of FME - formats and transformers would be limited to the appropriate versions etc.Saving a workspace in while in compatibility mode would enable a workspace to be opened up in that version. An option with new workspace to set the compatibility version. It should be noted that there would likely be sometimes differences in behaviour when actually running the workspace so warnings need to be put in place and the authors need to know the limitations. This perhaps would likely end up being a showstopper for some.Another benefit would be when the FME Server version is older than then your FME Desktop version. This means the feature would not only benefit solution providers but also users who work with an FME server in a rigid IT infrastructure with slow upgrade cycles. It would be acceptable if this functionality only supported a limited number of previous versions.Being able to reduce the number of FME installations and being able to use some new UI features would be a real benefit.
I'd like other users to see schedules and connections but not to change.Now there is "None" or "Full Access" (edit/delete) options only (unlike Read, Write, Remove for Topics, Subscriptions, etc.) per schedule/connection. A "Visible" or similar option would be really helpful.There are shared connections that I would promote to use but not to changed (same as in Desktop). Similarly schedules are OK to be visible for reference but shouldn't be editable to anyone.
I think it would be beneficial if there was a fourth option for Severity Level in the Logger, perhaps called LOGGER, and to go along with this a filter button in the Translation Log window. That way we would have the option to view all logs just from the loggers that have this option set.Thoughts?
According to safe: Tthe user parameters behave a little bit differently inside a custom transformer. They are in fact prefixed with the name of the custom transformer to avoid collisions with the main workspace parameters. Example: if you have a custom transformer called "custtransf" with a published parameter called "custparam", you will have to refer to it like this.value = FME_MacroValues["custtransf_custparam"] The issue is that a user can change the name of the custom transformer in the main canvas, or could have multiple copies ("custtransd_2") and the reference breaks. Ideally I would like to just refer to the user parameter without prefixing anything, and have FME figure it out when interpreting the python. If that's not possible, then having the ability to insert a "transformer name" into the python call would also work. value = FME_MacroValues[transformerName + "_custparam"]
This was actually raised by @ctredinnick and I think it makes a lot of sense.The FME log files in both Flow and Form are great for finding out what went on with a process. But wouldn’t it be great if you could load the Log file into Form against the same workspace and see the numbers coming from each port. Visually, it could help pinpoint issues in the flow of features quickly, subsequent to the run, and would be especially useful for Flow logs.
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.
