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 have a scenario where I have to apply an expression to a raster that is more complicated than can be captured by the RasterSingularCellValueCalculator, but the RasterExpressionEvaluator is complicated because a) there are a lot of bands and b) I don't know in advance the number of bands.My current workaround is to use a RasterBandSeparator, RasterExpressionEvaluator (using A[0]), RasterBandCombiner sequence.Bonus points if the expression can reference a list attribute with the list index corresponding to the band number.Side note, @Value(A:_list{0}.x) works fine in the RasterExpressionEvaluator, but @Value(A:_list{@Value(A:_index}.x) fails to parse.
Sometimes I may wish to make a slight change to a FeatureReader but even just amending the Transformer Name results in the Generating Output Ports pop up box. This is really irritating if amending a workspace that runs on FME server where parameters for file locations may not work locally.If minor changes have been made to the reader but are ones that would not impact the output ports, e.g. max features to read, transformer name there should be the option to keep the FeatureReader output ports set up as is
Need to show up the parameters when running the server app via fme server.For data download service we should be able to specify the files or folders at the time of server app creation not at the time of publish to server.
Most formats contain format attributes that are unexposed by default, but still present on the feature. It would be nice if there was a simple way to remove them regardless of format.This could either be a parameter on the reader to remove unexposed Format Attributes, or an option in the AttributeRemover.I would differentiate between format specific attributes and fme attributes, though the reader attributes like multi_reader_id would fall into format specific.
I love the simplicity of the HTMLReportGenerator + HTMLLayouter to create simple web pages. However, sometimes it would be nice to be able to add a little more "zing".Please consider adding an option to the HTMLLayouter for "code injection" into the <head> section of the produced HTML. I know this can be done with existing XML transformers but it would be nice not to have to mess around with that and simply have an option when generating the HTML in the first place.This would allow for simple JavaScript includes and custom CSS styling.
It would be nice if the PythonCaller had a parameter for a group-by so I don't have to code the logic each time I need it.
When converting seconds to hours/minutes/seconds like this:86399s converts to 23:59:59 but 86401s converts to 00:00:01 while I actually want 24:00:01It's easy to calculate yourself but feels a bit cumbersome, especially if you could do this for several attributes at once with the DateTimeConverter.An option (similar to Excel) where for example [%H]:%M:%S would give 24:00:01 would be useful sometimes.
At a customer site I have the need to "calculate" the name of a web connection based on a number of environment settings.So, I use an AttributeCreator to create the _FMEServerName attribute.But then the FMEServerJobsubmitter and FMEServerLogFileRetriever do not accept an attribute to define the named connection.I would like this to be changed, so the name can be taken from an attribute (not just from a published parameter or a hard-coded value).
***Note from Migration:*** Original Title was: Undo the change in the order of the 'Apply' and 'Reset' button in the Parameter Editor window of FME 2020 Hi,Today I updated from FME 2019.2.3.0 to FME 2020.0.2.1 in which I noticed that the order of the 'Apply' and 'Reset' buttons have been swapped around in FME 2020.0.2.1.Initially I was trying to apply changes and by 'auto pilot' I was clicking on the right button. Unfortunately this now seems to be the Reset button, clearing my changes. Although this might be something that can be used to, I think the original order of having the 'Apply' button to the right is more intuitive, so I would like to see this change to be reverted.See below screenshots for some more clarification;FME 2019 (and I believe also previous versions), Apply button in (bottom) rightFME 2020, Apply button in (bottom) left
You can add and download the FME Hub custom transformer by searching for keywords, as well as adding a general transformer, Once you have downloaded the custom transformer, FME will always use the downloaded local transformer. Even when the custom FME Hub transformer is upgraded, the user will not be notified of the upgrade.I suggest that when you add a transformer that is downloaded from the FME Hub, If the FME Hub has an updated version, the upgrade prompt is displayed in the transformer brief.
Currently, when editing an automation you can right-click on a Workspace action and go to View Workspace to see what the workspace is doing. When the automation is started right-clicking on the action does nothing. It would be very handy to be able to check this without having to navigate through the View Workspace menu.
Ability to run a batch script using automation as an action
The performance of USB 3 connected external SSD seems to be much better than internal HDD, so I'd like to use a directory in the external SSD drive as FME temporary directory. It's of course possible by setting the SSD directory to the FME_TEMP variable. However, the external SSD is not always connected. When SSD is not connected, I don't want to use system temporary directory as FME_TEMP since sometimes FME doesn't clean up temp files completely and therefore I would like to manage the remnant temporary files separately from other files.In my observation, this setting (use D:FME_TEMP if an external drive D is available, C:FME_TEMP otherwise) doesn't seem to be available. It's troublesome to modify FME_TEMP whenever connecting/disconnecting the SSD.D:FME_TEMP;C:FME_TEMPIt would be nice if FME could configure the temporary directory path from multiple paths set in the FME_TEMP variable.
Please upvote GitHub Issue to develop Cesium Ion API so it is possible to update assets and FME be able to develop CesiumIonConnector for this kind of POST requests
Currently if using a FeatureWriter to write a shapefile, the information in the summary attributes includes the folder location (dataset) and the filename (feature_type) but nothing to indicate that it was a shapefile and associated sidecar files written. It would be helpful if this information could be automatically included/exposed
It would be very nice if there were FME Server releases (and to a lesser degree, FME Desktop releases, though I realise they're tightly coupled) that received Long Term Support (LTS). As it stands without it, FME isn't really well suited to anything but a very small deployment to an organisation that is trying to follow proper development and system maintenance practices.Wikipedia has a full definition of LTS (https://en.wikipedia.org/wiki/Long-term_support), but the short version is - the release doesn't get new features, only bug fixes and security patches.Examples of software that do it: QGIS, CentOS/RHEL, PostGres, Python, FireFoxWithout this, an organisation with a large FME Server install-base that does proper due-diligence on service releases could easily end up spending tens-of-thousands of ($£€) doing acceptance testing just to upgrade FME Server from say 2016.0 to 2016.1 to get the bug-fixes in that next version.This is necessary because almost anything could have changed between .0 and .1, and if you've ever tried reading the change logs, you'll see a massive amount of changes.If I report a bug to Safe and am told "Yes, it's fixed in 2016.1", that's great, but a user shouldn't then have to get all the other 2016.1 stuff just to get the fix. That's not how corporate installs of production software work. It should just be able to get the fix.If however there's an LTS, the patches are considerably smaller and far less testing is required.
Add functionality in FME Workbench to within a reader/tester generate a query by graphically clicking on features to make a quick selection without having to write the conditions. Say I want to select a couple of objects that has nothing to do with eachother. By simply selecting them in a graphical UI inside a reader or tester.I know there are several other ways to do exactly what I want to achieve, but it requires a lot more steps.So this would be a more efficent way in some cases, without having to look to much into data.
Often I want to copy the name of the source dataset in the reader. Easy enough with the writers but not able to be done with readers.
Hello,I wounder if it would be possible to develope feature query of sketchup trait for setting angle between normals and controlling smooth normals and soften coplanar. The intended usage is to write a sketchupfile as a template with buildings and terrain with different angle between normals for visual effect and easer reading of those geometries by controlling visibility of edges on object level. Another trait request, if it's not available already would be to set a sketchup group (geometry name in GeometryPropertySetter) to be locked. Manually done in sketchup by right clicking the group and choose locked. This would also add to the value of a properly set sketchup template written from fme.Thanks!
Per this article: https://knowledge.safe.com/articles/87453/getting-started-with-automations.html Automations display their errors/warnings on the Automations management page under the Status column. The number of errors/warnings displayed is calculated from the total number in the log file. If you want to view current errors you need to view the log file and if you always only want current errors you'd need to remember to clear the log file.It would be great if there was an option (or change default behaviour) to only have errors/warnings from the latest Automation run displayed in the Manage screen. This would make it much simpler to tell at a glance if the latest Automation run has any issues, rather than having to remember how many errors were reported last time you looked at the page.If you need to see errors/warnings from previous Automation runs you can always look in the log file...
Snowflake cloud data warehouse is in use by some big customers and connects well with BI tools, so lets read and write it.
At the moment when you click 'update' in the Workbench 'Packages' UI, it immediately updates the package polling the web and grabbing the latest content. The first time I did this I was surprised because that's an inconsistent approach with the very risk averse approach that's been taken around upgrading transformers where you get warned about proceeding and you get to check what's changed in the UI. To find out the changes with the package you need to know to go to the Hub.Safe.com and go and look at the changes there. Can we have a 'View Changes' button for packages in Workbench please?
Along the lines of this idea and this idea, but I would really love FME to be able to support PBR materials as appearances.With modern 3D formats like GLTF (and 3DTiles) gaining popularity and wider use, it would be really nice to have some way to support PBR material types. I wouldn't expect the Data Inspector to render based on these, although that would be very cool. It seems like it is pretty difficult to interchange between the two types of materials so being able to support PBR materials would allow for better preservation of the original dataset.At the moment, there is no real way to properly preserve a file which carries a PBR material, I must convert these back into a standard appearance, losing information.
Related to the FME Server 2017 "running job expiry time" (tm_ttc) parameter that cancels a job if it runs beyond a specified length of time: https://knowledge.safe.com/idea/18984/configure-time-limits-for-a-job-and-alertcancel-if.html ----- I'd very much like to have the ability to set a global time limit. Would the same/similar functionality be available as system wide defaults (e.g. max threshold of like 12 hours).
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.
