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.
Extend the HTMLReportGenerator Parameters window some more to make more room on the Content Settings side. At present it's too difficult to review / write codes. I'm having to use VS Code first then Add the Attribute Values where needed.
For easier readability: Add icon in Feature Information window showing datatype . Similar to what is here: https://ux.stackexchange.com/questions/43695/graphic-representation-of-various-data-types
I'm a big fan of the History window. I don't think that many people know about it and it's really useful.I think it could do with a bit of care though. For example recently I was missing the Save action in the timeline. There's probably other actions I can't think of right now that should appear there too.
Add Timeout Parameters to JSON Readers, you can put a API URL into the json readers and it works, however some API's are really slow and it will timeout. You can work around this by using the HTTP Caller, but having the json reader is a lot nicer, as the reader parses the json into attributes itself.
It looks like FME's SketchUp Reader only supports the .skp file extension.We have customers who use Rapid Sketch files (.rs) and require conversion to Esri format. Is it feasible to add support for the .rs sketch file format in FME? Thanks!
FME Desktop 2022.1 Build 22618: Having the functionality to connect C or D drive to FME to be able to drag and drop data decently, Elaboration:FME Desktop 2022.1 Build 22618: How to connect C or D drive to FME to be able to drag and drop data decently?
Currently when you set-up automation in FME Server, the trigger option include email received. One of the option for email received is download attachments. You can specify a location to save the attachment. This can be on FME server or network location where FME server account can write to. However there is a new folder created each time the automation is trigger and this can be annoying. It would be great there is an option to enable/disable creation of subfolder and also possibly save the attachment and overwrite the existing file.
The inclusion of the ability to compare workspaces in workbench as part of the git workflow is a really big step forward when it comes to including FME in the typical development workflow.Another really helpful addition would be having the ability to either embed or link certain custom transformers via command line.We work on a number of projects with often each contain several Custom Transformers - Each of which are maintained in separate Git repos. During development of the 'main' workspace these CustomTransformers are linked to the latest version. When it comes time to releasing the new version of the workspace it is a manual task of opening up the workspace and embedding the transformers. The alternative option is to deliver the CustomTrasformers in addition to the workspace and have the end user install the CustomTransfomers before opening the workspace. Being able to automatically embed select custom transformers would enable a proper build pipeline.
It would be nice to have some options in the Geometry Picker. The vertices are quite large. Also it would be nice to be able to change the colour of the geometry
MDX is a format associated with Microdrainage hydraulic modelling software, widely used in the UK by developers for the design of foul and surface water sewers. Whilst it possible to export the data spatial data from within the package to csv dxf etc it would be useful to migrate with the likes of FME in order to under take bulk conversions. Microdrainage is now part of the Autodesk Group
I'm missing the capability in FME for reading SVG images so you can use them as icons in reports or when plotting pdf maps that works in FME Desktop and FME server/cloud.
For automating processes an option to set up an automatic update of readers would help. An option to update readers at run, or a .bat command
The FeatureReader and FeatureWriter are ideal candidates to allow concurrent data reading and writing, something that you can't do with multiple readers and writers right now. Adding these parameters is currently possible if you wrap them up in custom transformers like I explain in this webinar, but ideally you shouldn't have to go to this effort.https://www.youtube.com/embed/YnCot12FA9ULooking forward to the performance gains this change would bring. In tests my timings suggest in some examples it reduces the readwrite times to a third or even less.Cheers, Dave
Even though it would limit the interaction with transformers in the outside workspace it would make it easier to inspect what's inside without possibly breaking the layout by opening the bookmark.
Hi there,The Coordinate System User Parameter does not allow the user to select Vertical coordinate systems. These are supported in various ways as listed here: https://community.safe.com/s/article/which-transformer-do-i-use-to-do-3d-reprojection-vI cannot currently use the esri reprojector in an automation and provide user parameters for the input/output vertical and horizontal coordinate systems. I can only select horizontal coordinate systems.It would be good to be able to have a drop down that lets you filter by type (Vertical/Horizontal) as well as by region similar to how the others work e.g. CS-MAP Thanks,Marc
Would be great if FME Server was able to log Referer, User-Agent, From, or other identifying headers to the REST API so that I could easily track origins of where jobs are ran from so I can easily notify people when I have to update a Form workspace or during Flow system maintenance.
Add version control with Azure Devops as many organizations use it already
File Copy Writer has an option to switch from warnings to errors if overwrite is set to No and a file already exists in the destination.Could users also be allowed to completely skip such files / suppress those warnings, the way one can in, say, the Windows UI ("Skip these files") ? We'd like to be able to copy only new files, without overwhelming the log file with no-issue-here-intended-behavior-is-occurring warnings.
It would be useful to allow configuration of the FME Server / Flow Data Download Service to automatically split large zip files. Ideally I would like large zip files to be split into 2GB chunks{name}.z01{name}.z02{name}.zipI would expect this to be an optional line in fmeEngineconfig.txt or something similar
In FME Server, it is currently possible to add a connection to an Amazon S3 bucket as a resource, but because the S3 Bucket is not mounted as a drive, these external resources can not be used as input or output data locations when running a job on FME Server.When working with a large volume of cloud-based data, it would be helpful to be able to read from and write to the data without having to first copy the data into FME Server Resources.
So this is a simple thing. When using ArcSDE with max features to read per feature type, the reader reads all records, then filters afterwards. When querying the database use groupby and top or limit to limit the number of feature before fetching all the data. Why is this important?Well sometimes we have huge databases, and to make testing and development smooth and fast, we shouldn't sit and waste our time for a simple feature to come out of the reader, because of this elementary thing.
ElasticSearch allows for aliases to be defined on indexes (which are similar to views on a traditional database table). The FME ElasticSearch reader does not currently support reading an alias. It does not show alias names in the list of available features to read from the reader, and explicitly specifying an alias name results in a reader error.Please update the ElasticSearch reader to provide support for aliases.
Currently I can format JSON to an attribute and I can create a file in Azure from that attribute data. I cannot however see how I can take that attribute and create a new attribute which is the zipped contents of the Json Attribute so that I could then write that directly to Azure.Maybe I've missed something here, as it seems an obvious extension of the current file handling processes.
I had a use case where I had to build a gallery app that contains server apps and custom-built apps (via URL). These custom-built apps are created using a workspace (triggered by webhook) which produces custom built HTML page. Further, that HTML contains pre-created buttons/links that trigger another webhook, and so on. In other words, all these workspace apps and custom-built apps should work as one functional website interconnected with webhooks.One issue I have encountered was authentication of user. When I use only workspace/gallery apps, I can setup “require authentication” for each app and user has to login only one time (using FME login page that allows AD). When it comes to the custom-built app, user has to login again, but this time with browser default login page which does not support AD.Would it be possible to build “require authentication” option for webhooks, in a same way that is done for server/gallery apps? This would allow us to build websites powered by FME Server (which are combination of workspace/gallery and custom-built apps) that require only one authentication. Or alternatively, it would be great if webhooks could be authenticated with AD on its own.
The SchemaScanner is a very useful tool in dynamic workflows. However if dynamically creating an output dataset from an attribute [ex. FeatureWriter Dataset:@Value(_outputfilename)] the <Schema> feature from the SchemaScanner does not contain this attribute and the writer fails because it can't find the schema.No definition found for input feature type '...In most transformers, attributes included in the group-by parameter are propagated onto the output feature. If this were the case with the schemaScanner, then the required attributes can be included in the group-by and the dynamic writer would work as expected. No additional transformer required.As it is, a FeatureMerger or equivalent is required to attach the desired attribute(s) onto the schema feature(s), which adds extra overhead to the transformation, and can cause issues with the schema features arriving first. To account for that a featureHolder needs to be placed on the Output data stream
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.
