Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
In the FeatureReader, one does have the possibility to filter features based on a WHERE-clause and based on a Spatial filter.It would be very helpful in specific situations when there is an extra dropdown list in between those with options 'AND' & 'OR' allowing to select all those features which match a spatial filter AND / OR the where clause.
Fanout Dataset is a great mechanism, but it could consume huge temporary disk space. Similar to the 'Input is Ordered by Group' option for Group By setting in transformers, it might be better if Fanout Dataset (writers and FeatureWriter) could have 'Input is Ordered by Fanout Expression' option so that the processing could be more efficiently in some cases.
Just as a shortcut to "spherical mercator" for those of us who can never remember what FME calls it...
Especially in larger or heavily edited workspaces there may be attributes which become obsolete. They may cause useless calculations or reading large amount of unnecessary data from big tables. Now it is a manual tracking back to find from where an attribute is not used any more.If it is possible to highlight lines that carry obsolete attributes and list them when hoovering or in the parameter editor, that would be a great help.
The following GDAL/OGR writers provide support for fme_db_operation writing. Unfortunately, it is only possible to match (UPDATE | DELETE) records against a [system id] field, which is internally generated. This issue affects the following formats:spatialitecartocloudant couchdb elasticsearch geopackage mongodbothers?In most of my scenarios, I am wanting to take incremental updates as "changeset" data from a data custodian and synchronise it as (UPDATEs | INSERTs| DELETEs) against the existing data in my tables. The new changeset data has no knowledge (in advance) of what the internal [system id] values are, so the UPDATEs and DELETEs can never be matched and processed.The fme_db_operation format attribute does not behave like this on non-GDAL/OGR FME writers, i.e. this would be like only being able to do a fme_db_operation match on an Esri geodatabase [OBJECT_ID] field (which is also internally generated).Can we have the Match-ID reference any "unique id" field when working with fme_db_operation writes to these formats please?
Hi,A small addition: Add an option under Workspace Parameters/Advanced to have the workspace check the existence and accessability of all input data before starting the translation.I've just had two workspaces fail after half an hour each because of a simple typing error (in an input path involving a ZIP fil, which cannot be point'n'click'ed).It would be nice to see this error immidiatedly instead of after however long it takes the workspace to try to access the faulty input.Cheers.
Hi,The ability to read data sets directly from a ZIP package is great, as described here.It would be even nicer, if one could select files using a point'n'click interface just like with regular files.Cheers
www.qps.nl/display/qimera
When developing a workspace you often find yourself to use the Inspector to inspect your output data. When you are finished with developing your workspace, wouldn´t it be great if you could right-click the Inspector and convert it to a Writer?
The new Sentinel-2 on AWS reader has different feature types for each subdataset (10, 20, 60, preview). It would be nice if the same functionality was also available on the MSI reader.
I have noticed that in FME 2017, you can choose to build a list of attributes in the parameter settings of the transformers that supports the list. Instead of using all attributes to build the list as before. This is a very good feature, but I also noticed that it does not allow users to select any attributes (although it can run, but there will be a warning prompt). But in some cases I just want to build a list, and I don't want to choose any attributes, such as the _relationships{}.de9im that just wants to get the SpatialRelator list properties.I suggest Selected Attributes as an option. When the user does not select any attributes, use the default attributes of supplier to build a list. Do not generate a list if there are no default attributes.
It would be good if these enhancements could be done for the DatabaseDeleter.Allow users to select multiple target tables or an attribute value as a target table name.Add an output port, which outputs a single feature containing summary of the result after completion of the delete operation, something like the Summary port of the FeatureWriter.
***Note from Migration:*** Original Title was: Separated coordinate list to be supported in GeometryExtractor and GeometryReplacer I would like to suggest that the GeometryExtractor and GeometryReplacer support a separated list of xy or xyz coordinates as encoding. Useful additional parameters could be:Separation character (potentially two, one for coordinate values, one for vertices)Dimension (2D or 3D, although that could be derived from the separation characters)Form areas (if the first and last point are the same a polygon is created, otherwise it'll be a polyline or point)I often come across Excel or CSV data with XY coordinates in a single column, separated by a comma or something like that. Right now I have to use an AttributeSplitter and VertexCreator to deal with that, it'd be nice if it could be handled directly by the GeometryExtractor.
It would be very handy if FME (Desktop and Server) had a mechanism for storing key/value paris in an external database, similar to the database connections introduced in FME 2016.These key/value pairs could be used to store local workspace settings, similar to this post.The idea would be to define a list of key/value pairs on Desktop and then upload it as a resource to FME Server, where it would contain settings for each server instance (e.g. development, staging, production, etc).It should be very easy to retrieve these settings inside the workspace, e.g. as a type of parameter.This would enable workspaces to retrieve an external configuration and not being dependent on hardcoded settings or python scripting.
It would be great to have the option to right click "Duplicate on Writer" for Feature Types listed in the FeatureReader. It's a great option to have on a normal Reader.
As of right now the GoogleDriveConnector does not account for user rate limit set by the Google Drive API. As suggested by FME support and Google Drive API documentation would be to add batch request functionality to the GoogleDriveConnector. See here for batch requesting functionality available with the Google Drive API:https://developers.google.com/drive/v3/web/batch
This Coordinate System is China’s new-generation geodetic coordinate system, was officially put into operation. And more and more geo-softwares support it, such as ArcGIS.
It would be awesome to be able to add a new/custom coordinate system to FME from within FME Workbench, rather than having to manually add or modify a document within the file directory. Maybe there could be an "Add New" button within Tools>FME Options>Coordinate Systems, that would allow the user to define a new/custom coordinate system?
The Filecopy writer can be used to copy a folder structure and populate it with files. However sometimes the folder structure will contain empty folders that you want to copy because they will be polulated manually when you work on a project. This works on FME Workbench, but not when you move the workspace to FME Server.
I would like to suggest some enhancements for the WMS Reader:Allow the user to choose the exception type if the WMS propagates more than one via getCapabilitiesIf the WMS servers sends an exception, FME 2017.0 does currently show:<WMS> Exception detected for the GetMap operation, requested Content-Type, 'image/png', returned Content-Type, 'application/vnd.ogc.se_xml; charset=utf-8;charset=utf-8'. It would be nice if FME could parse the exception xml and show the contained error message.Bonus: Even handle the error xml if the server sends it with the wrong content type ;).Allow choosing of WMS version 1.1.1/1.3.0
A tiny addition.My workspaces tends to quickly have many runtime parameters, and these are easiest maintained in the "Run with translation parameters" dialog. Unfortunately you either need to cancel, cancelling any changes, or press ok to save the changes _and_ run the workspace.My tiny suggestion is adding an "Apply" button to save any changed parameter values without running the workspace.Cheers
@XiaomengAtSafe this one is for you.I made a throwaway comment that there should be an Entomologist Badge (aka Bug Hunter) for those who find and report a given number of bugs to Safe support, and got asked to post it as an idea.
With the addition of being able to set execution order on Creator transformers and Connections a great method of workspace control has been added. This functionality is a little bit obscure, and that's fine, you don't always need to change it. But the information about that order seems more important and should be visible to the user.I would suggest a small numbered icon that from now on would mean 'Order'. This could be shown on the corner of a Creator transformer or on the first half of a Connection to inform the user on which parts of the workspace would execute in which order. This should only be shown when there are actually multiple Creators/Connections.
When performing a merge there are often records which one would like to exclude - e.g. where a field used has a few entries with no/a dummy value.It would be a nice addition to be able to integrate optional testing conditions as a pre-requisite to merging data (without having to employ additional transformers).
Currently FME Desktop asks for elevated permissions several times during the installation. Could it ask for it only once?
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.
