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 get annoyedof all the inspectors I sometimes have to use and the worksheet looks like a spiderweb - making it hard to follow the workspce-flow. It would be nice if I could choose to show the inspector as an icon in the transformer/reader where it came from.
Another idea from the same colleague who suggested job time reporting to me. In a discussion about job routing and engine tags he suggested that if a job has a preferred engine tag and gets submitted to an engine that is already being used, but it could actually run on another engine, then the job could be re-routed to the other engine. Perhaps if that second engine was also busy, it would just be returned to the original engine's queue (in the same spot in the queue, ideally!).This might be best as a private parameter that only the workspace author could set, unless a trusted user who knew the implications of running on different engines could be allowed to choose if re-routing should be tried. An example is that we might run a job on a 32-bit engine normally to avoid clashes with long-running raster-based processes on a 64-bit engine, and we'd need to think about those potential clashes were the job to be sent to 64-bit engine.
I like to use the MicroStation GeoGraphics writer to help create mslinks for my dgn. It makes it easy. This only works in Linux if I use an Oracle DB but I would love it to have MDB as an option like I can in Windows
It would be nice if the sentinel-2 readers had the option to read in the QI files as a feature type in addition to the bands.
A toolbar button, which allows to toggle behaviour for rejected feature ports similar to redirect writer output, would help to bring similar settings back together ...
I would like to see an FME Desktop reader that would read in a HYPACK Project folder and its contents, the contents being the various files of survey data within the Project folder and its subfolders. A HYPACK Project is just a typical Windows folder, but contains a .ini file (of the same name as the Project folder) that the HYPACK software recognizes. This .ini contains metadata about the project, including coordinate system, color tables for sounding data, and other relevant metadata. Many of the HYPACK data file formats are simple ASCII data, but being able to read that data in and preserve its connection/relationship to a HYPACK Project is far more valuable than just being able to convert ASCII to .shp. If an entire Project reader is not possible, it would be nice to have at least a series of readers added for some of the different HYPACK file formats like .lnw, .mtx, .tgt. and more.
This would be a very useful feature since Idrisi is still being used quite a lot for processing raster files.
Both these composite expressions are wrong. That is to say, FME will probably run them just fine but the end result will most likely not be what you need.I'd like to suggest adding a check to the composite expression: it will light up red if you're not using all of your sub-expressions -or- if you're using more than your sub-expressions.
Ability to customize the User Parameters Prompt UI.Maybe with a custom header and a custom footer.So we could add some text (description, general help) and why not a logo in the User Parameters Prompt UI.Could be two workspace parameters with HTML content.
In FME Server 2016, AD (Active Directory) security was based on AD groups.In FME Server 2017, AD security is based on Users.Upgrading to FME Server 2017 (using Backup and Restore) is not importing the AD users for a logical reason (they were not in the FME Server 2016).Using the AD import function in FME Server 2017 the users are imported by name.It would be great if the Import would allow importing an AD group of users (created for FME Server 2016) in one action: Creating the Role from the Group name, Importing the Users and assigning the Role to the Users.That leaves only the manual task of assigning privileges to the Role.And would save a lot of work for larger companies that use AD for security.
I have 80 reader feature types going to 80 writer feature type.But as a result of case sensitivity none of the attributes are mapped.I would like to select all links or all objects in my workspace and use the "Auto Connect Attributes" option to connect all attributes without having to repeat this for all links one by one.
I have an extremely large model for which I need a way to (First:) automatically identify and select any transformers that are connected to a writer that I already have selected. (Second:), I need a way to "Switch the Selection" so that everything else gets selected. Once I'm at that point, I can choose to disable those selected objects. Then I run my model to publish ONLY my original selected feature type.
Currently, the PointCloudExpressionEvaluator does not have a working option for a conditional value. The option is available but it does not work (error is "PointCloudExpressionEvaluator(PointCloudEvaluationFactory): Failed to parse the EXPRESSION_LIST clause..."). I've also logged this as C115855.However, the function should not be removed but fixed. Otherwise we have to convert point clouds to points to do the conditional calculation and re-assemble the point cloud which adds to processing time.
The RasterPropertyExtractor produces 23 attributes and in 99% of cases I'm only interested in a small subset of them (1-4) being able to select only the properties I'n interested in should improve performance when dealing with a large number of rasters and obviate the need for an AttributeRemover just after (I don't think I've ever used an RPE in production without an AR immediately afterwards).Bonus points if I can change the name of the attributes.
It would be nice if the ListSearcher could have additional search types similar to those available in the Tester such as:LikeContainsBegins WithEnds With
The issue is :I need support for the ACAD Civil 3d readerHere is the error:Starting translation... FME 2018.0.0.0 Beta (20170730 - Build 18138 - WIN64) FME Desktop Smallworld Edition (floating) Permanent License. Machine host name is: SLD-RichLap Operating System: Microsoft Windows 10 64-bit (Build 15063) Copyright (c) 1994 - 2017, Safe Software Inc. Safe Software Inc. Creating reader for format: Autodesk AutoCAD Civil 3D Trying to find a DYNAMIC plugin for reader named `CIVIL3D' Loaded module 'CIVIL3D' from file 'C:Program FilesFMEplugins/ACAD.dll' FME API version of module 'CIVIL3D' matches current internal version (3.8 20170623) SOURCE_CIVIL3D Reader: Using rich geometry. AutoCAD Reader: Unknown or unsupported version of AutoCAD file 'AC1032'. Most recent supported version is 'AC1027', which is also known as 'Release2013' A fatal error has occurred. Check the logfile above for details Failed to obtain any schemas from reader 'CIVIL3D' from 1 datasets. This may be due to invalid datasets or format accessibility issues due to licensing, dependencies, or module loading. See logfile for more information FME Session Duration: 2.1 seconds. (CPU: 0.5s user, 0.2s system) END - ProcessID: 15856, peak process memory usage: 74336 kB, current process memory usage: 44648 kB Failed to obtain any schemas from reader 'CIVIL3D' from 1 datasets. This may be due to invalid datasets or format accessibility issues due to licensing, dependencies, or module loading. See logfile for more information Program Terminating Translation FAILED.
I would like a simple transformer to be able to append a value to an existing list.Currently either I need to use a PythonCaller or a ListElementCounter followed by an AttributeCreator with the list index as {@Value(_element_count)} (which works but gives an ugly output on the canvas)
I would like to be able to visually monitor jobs in real-time. Something like a page with three visible lists: queued, running and completed, all visible at the same time. The lists should be continuously updated without having to press refresh.
If a translation fails, the error can be quite hard to find from a huge log file in Translation Log window. I'm using Find Text button for that, but it would be faster to have a button, which would take you straight to the first error in the log. When clicking it again, it would go to the next error in the log.
Some processes fail due to insufficient memory, especially when working on 32 bit systems. It would be useful to be able to catch a memory error in some way. At the moment the workspace just fails and it is sometimes hard for the user to understand the cause, especially on FME Server. Maybe someone has a good idea how to best handle this - like a rejected port or a terminator message that displays for the user?
Currently, the FMEServerJobSubmitter has all this information about the job that ran, but no workspacePath or name . the only way I could find to get it is by doing an HTTPCaller when it failed or succeeded. Very cumbersome. Could we please get that info as well?
It would be nice if we could bring geometry directly into the RCaller, so that we may manipulate that geometry with our R code. Currently, we have to write a temporary file and read that temporary geometry file in the RCaller. It would be nice if R could recognize incoming geometry and build that geometry in the R spatial data model. Then we can manipulate the geometry in R code, and output the manipulated geometry back to our FME workspace.
When generating topology, sometimes what looks like an intersection may not really be one - for example, a street dataset where a street passes under an overpass but doesn't physically connect to it. Flyovers, bridges, cloverleafs. Adding a "Consider Node Elevation" parameter would support correct topology building for datasets where elevation matters, and make the z coordinate handling behavior explicit and predictable. @Mark2AtSafe
When a job fails or works unsuspected it is a real painful task to track down what happened by comparing the workspace and the log.The data is in the log, it would be a big big help to "label the lines" with the feature counts from the log file.
***Note from Migration:*** Original Title was: Hybrid Deployment: central management of FME processing with execution performed both on-premises and in the cloud I've got some systems that I have invested a lot in that are on-premises. I'm not ready or able to move them for the foreseeable future. I also have newer cloud based systems that are doing important work. I'd like to process data in these various systems and integrate them as well. These systems each have massive amounts of data. So, want to minimize data transmissions between on-premises and cloud to only what is required.
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.
