Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Add numpy and scipy to FME's python and support for treating raster features as numpy arrays in PythonCaller. Numpy and Scipy include a whole host of tools that are really useful and powerful for handling mainly raster data and to a lesser extent point data. I would love if it was easy to use these tools to manipulate features in a PythonCaller
It would be really helpful if the writes which had the 'Move to Local Coordinate System' had the option to only offset the data (preserve scale and rotation).Alternatively it would be nice to have an option in the Offsetter/3DRotator/Scaler/3DAffiner to not add a Transformation Matrix but actually perform the offset on the coordinates.The desired result is a robust (and easy) method to place a model centered on the origin (0,0) with preserved scale and rotation without a Transformation Matrix in the output data.Here are some more details on why having this would be useful: https://knowledge.safe.com/questions/98552/move-to-local-coordinate-system.html
When a single parameter is selected, right-clicking will give you the option to convert from a public to a private parameter and vice versa. But that option is not available if multiple parameters are selected.
When you add a Reader to a workspace, it has the "Features to Read" option, which allows you to set the start feature and min/max features to read. I think it would be really great if this functionality is also available for the FeatureReader transformer.
When using FeatureReader, often need to be exposed to some of the properties, can be use [Attribute to Expose] to specify the Attribute names. But must be manually enter the attribute name, if add an Import function (eg.AttributeExposed's Import function),I think it can more convenient to use.
Could you include S3 bucket creation/billing through FME Cloud account? This would avoid to create an AWS account for some small project.
Currently the FeatureWriter for Postgis throws an error under the following situation:- table with an id-column (as serial) has been created.- if the table-name will be changed in Postgres, the column-definition of the id-column changes from"<id> Serial Not NULL"to"<id> integer NOT NULL DEFAULT nextval('<old_table_name>_<id>_seq'::regclass),- while Postgres is able to handle this reference to the old sequence, FME can't and crashes with the errror, that it can't write NULL into a serial id column.
Several of the calls in the FME Cloud API require the numeric ID of the instance I want to interact with. The first place I usually look for this is in the FME Cloud console, but it's not listed there. Could the ID be added somewhere in there to make it easier to find?
Realm database is a database format used for mobile apps (both iOS and Android). I would like to read from and write data to this database, without having to use a third party app.
Transformers which have Group By do the groupping in case sensitive alpahabetic mode.Casing is not always important and time to time I'd like group by numbers where the numeric values come inconsistently with or without leading zeros or .00 at the end.It would save some preparation and clean up transformers before and after the groupping transformers (eg. Aggregator, StatisticsCalculator) if the Group By settings would have comparison options (case sensitive, case insensitive, numeric, etc, like in testers).
Put the title bar dark instead of white.See this post : White Title bar
Parcel Fabric is a key component in the ESRI local government model. Unfortunately FME desktop does not recognize parcel fabric dataset features. Please consider enhancing the ESRI data readers to recognize this type of data
Hello, I don't see a "count" option for the PointCloudStatisticsCalculator. Could it be added? It should be possible to know how many data points were used to generate a statistics; It's very useful when reporting stats. Since it's needed to generate the mean, I am guessing the tool already calculates it, but fails to give the user the option to output it without using extra transformers.Seems like a miss for this otherwise very useful tool.Cheers, MelanieMontreal
***Note from Migration:*** Original Title was: Add "All attributes" in CRCCalculator and why not a fme_crc attribute for all readers ? Change "Included Attributes" parameter of CRCCalculator by a list like for ChangeDetector or Matcher :- Selected Attributes - All except... - All..Because we cant use CRCCalculator dynamically by specifing attributes manually.And why not a fme_crc attribute for each reader basing on geometry and user attributes ? Too time consuming ? So maybe as an option for each reader : "Generate CRC ?"
It would be useful to extend the Emailer to include extra originator fields as per https://tools.ietf.org/html/rfc5322#section-3.6.2 At the moment it has From, To, CC and BCC fields. Sender and Reply-To fields would allow the email to be sent on behalf of someone and replies to be directed elsewhere.from = "From:" mailbox-list sender = "Sender:" mailbox reply-to = "Reply-To:" address-list
I was just thinking, since FME Server 2019, has a way to interpret .fmw files, maybe safe would be interested in building a plugin for MS Office, to make it easy to view a .fmw file directly in Outlook, Powerpoint, Word and so on?
In System Events rather than having to enable and configure the Send Email parameters for each system event individually I would like to see an option to set this up once and apply to all.
It would be easier and nice to have, to locate an attribute(s) order number, or see how many attributes available in a reader writer has if there's sequence in the attribute definition window, as shown in the snapshot as a draft idea.
The FeatureJoiner does not have an Accumulation Mode the way the FeatureMerger and DatabaseJoiner do, to allow for prefixing the joined attributes.It would be nice to take advantage of the efficiencies of the featureJoiner while allowing better conflict resolution by prefixing the attributes, rather than have to rename them ahead of time, or use just the left (or right).
In the JSON returned from the System Events- Successful/Failed Log In I would like to see the user email listed as well as the user name. For my use case I am triggering a workspace to monitor the number of failed log ins and will disable a user account if the failed log in count has reached X over Y time. Having the email returned in the JSON will allow me to configure the automation to send notifications to that user.
***Note from Migration:*** Original Title was: Add option for whether to ignore leading and trailing spaces in transformers that matches attribute values In FME there are a lot of transformers that compares values of attributes, as part of their function. e.g. FeatureMerger, Matcher, DuplicateFilter, etc.These transformers don't all behave consistently, when it comes to whether they ignore the leading and training spaces. For example FeatureMerger will consider values "a", " a", and " a " the same, in matching key attributes; While DuplicateFilter will consider these values different from one another. It would be nice to add an option, which allow users to specify whether these spaces should be ignored or not.
It would be really handy if you could set Precedence on a Featurewriter (in my case specifically when writing to Postgres/Oracle/SQLServer).Therefore enabling multiple tables to be written in a single transformer with a single opening of the connection but ensuring the writing of one table does not start until the writing of another is complete.I recognise this can be achieved with a feature holder but would be a nice additional feature for feature writer which would enable hierarchically linked tables to be landed with ease.
***Note from Migration:*** Original Title was: FME Data Express : Allow user to draw geometries (as leaflet draw) as input on top of location. Allow user to draw geometries (as leaflet draw) as input on top of location.
***Note from Migration:*** Original Title was: If FME 3d tile writer provides some optimizations like cesium it would be helpful. 3D tiles generated by FME are too slow to load on cesuim ion. If FME 3d tile writer provides some optimizations like cesium it would be helpful.
Hello, I think it would be nice to have an overhaul on the report generator style settings. Currently, it outputs into Bootstrap v3.3, and the most updated version is 4.3. It would be nice to have a selection option for which to choose if you have legacy apps that require 3.3 integration. There are also a number of features that can be utilized from Bootstrap that would make a lot of html pages more visually appealing.
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.
