Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
It would be nice to be able to select an existing parameter as a target dataset for Readers and Writers. Often I have to update the same dataset as I am reading. It would be convenient if I can select the existing dataset parameter from the Reader directly when I am adding the Writer or when I am adding the same dataset as a Reader for whatever purpose.
If there is not a spell checker transformer in FME (I couldn't find one), could you please create one?Have a large, free-form entry string field and want to flag words that don't match an English dictionary. Think of this as an ongoing tester w/ QC .CSV output (examples in attached image), rather than a "fail over point" in an ongoing automation.
That would be easier if we could sort attributes (like on a writer) inside an AttributeValueMapper
We can configure the S3Watch publisher to poll every x minutes/hours/etc., but we cannot specify at what time of day the poll occurs. It'd be great to set up the publisher to poll at specific times e.g. noon and midnight.
Hi,It would be very handy if ChartGenerator supported datetime values as input for X axe for example.Using FME 2017.1 32-bit, when I try to use datetime values, ChartGenerator throws a warning saying that not numeric data received.Thanks,
Currently the SQLExecutor acts in a 'blocky' or 'groupwise' mode, with features output all at once. This can cause problems, for example, in looping transformers. Replacements for the SQLExecutor in this situation (database readers or FeatureReader) are also 'blocky'. Allowing the SQLExecutor to output a feature immediately would provide more creative options for custom transformers.
Ok, these 2 articles explain nicely how FME chooses from the available ArcGIS products on the system and how to "force" which license level is used: https://knowledge.safe.com/questions/36948/can-i-specify-whether-fme-desktop-uses-my-arcgis-d.htmlhttps://knowledge.safe.com/articles/31613/setting-different-license-levels-for-arcgis-and-fm.html My proposal is to introduce FME specific environment variables (or FME options Settings) to allow the user exactly what to use at FME runtime, e.g.: FME_ARCGIS_PRODUCT_USE=Engine|Server|DesktopFME_ARCGIS_LEVEL_USE=Basic|Standard|Advanced This should override the internal FME logic and of course fail, if the user chooses a product which is not installed, licensed or if the combination violates either Esri or Safe usage agreements.
Wouldn't it be awesome to have a quick keyboard shortcut to publish to server?
This morning a colleague indicated to me that it would be useful if we could indicate how long a job is likely to run for on FME Server. Clearly there are a lot of moving parts including source data sizes, transformers used (blocking vs feature), number of transformers, readers/writers etc. going on which could make it hard to auto-forecast, but I wanted to throw the idea out there.Of course a simpler solution is a private parameter that the author of the workspace supplies, to give an indication once they have run the workspace enough times to know how long it should take.If this was done it could appear on the workspace summary window after submission, and/or be emailed to the user who wanted to know.
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
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.
