Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
It would be very useful to get what version is being used to execute a pythoncaller when using for example the arcpy library. Is is therefore possible to add this information to the macroValues provided in the module fme? example. fme.macroValues['FME_VERSION'] = 32bit Example of situation in which it would be useful: https://knowledge.safe.com//questions/40448/how-to-determine-whether-the-current-fme-is-32bit.html
Let's say that I have hundreds of jobs in the FME Server queue and that these jobs notify a specific topic (JOB_FAILED) on failure.If I publish a workspace to the Notification service (subscribing to the JOB_FAILED topic), the triggered workspace will be placed in the queue at lowest priority letting me know that there is an issue only when all my jobs already queued are completed.Currently, I can work around this by appending &tm_priority=10 to the target URL of the push subscription but I have to do this manually each time I publish the workspace.
I would like to monitor how often a workspace is run. This helps to understand usage. This would be great to see in the Dashboard.
It would be useful if there was more support for accepting files that had unicode characters in them. An easy work around is to simply rename your source files to be processed and then map them back to the desired name afterwards, but that shouldn't be necessary.Currently, some files with unicode in their name are simply rejected with a source file is not valid message.
I'd like the option in the date formatter to choose whether to Create New Attribute or Overwrite the existing Attribute, similar to that in the Expression Evaluator.
There's scope for improvement of the Change Detector. It's only version 1, so I don't think it's something that has received any real love since its creation. This is particularly surprising given it's a fairly highly used transformer at #62Suggestions (probably not all feasible): Group By Parallelism (workspace optimisation) Original/Revised first (workspace optimisation)Input is ordered by.... (workspace optimisation) Pairing - like Group By - one original feature should match one revised feature and then the changes compared between them. Potentially in combination with some of the above, this could also allow comparison of features without needing to store them all first.Split the dialog up so that the attribute stuff is all together and the geometry stuff is all together. Currently it's all mushed together. * Following from last item, disable "geometry" portion of dialog if only attribute matching. And disable attribute section if only geometry matching. (as standard in other dialogs).
In FME Server the UNC path permissions come from the account running the Engine service. It would be interesting if optionally the permissions could come from the Active Directory users.
Currently looping with blocking transformers is only allowed in linked custom transformers. (see http://knowledge.safe.com/articles/1273/looping-with-blocking-transformers.html)However there are transformers that force a linked rather than embedded custom transformer are only blocking if they have a Group By, or other parameter setting that causes them to block.It would be nice if these transformers could be used in an embedded loop when they are not in "blocking-mode"ex. Bufferer (No Group By), AreaAmalgamtor (Self-Amalgamation Mode), PythonCaller (Function)
The rejected port functionality showing the red circle and number and allow for features to be inspected on Desktop transformers has been of great benefit.However there is currently no way to add this functionality to a Rejected port in a custom transformer. Instead, a port created for "rejected" features in a custom transformer requires a connection to be fully aware that something was rejected. Any chance for the option for "Insert Transformer Rejected Output"?
I encountered an issue when I started with a shapefile line feature which held on to it's format attribute SHAPE_GEOMETRY as being an arc even though I had used the buffer it and area on area overlay transformers during the workbench. I took me an age to figure out why it wasn't writing out as area features despite everything else within FME told me they were in fact areas: inspector showing the features as areas, was able to calculate the areas of each feature, my features were definitely areas! Eventually I found the SHAPE_GEOMETRY format attribute (is this new?) and found this doesn't update throughout the workbench automatically. Once I changed this using an attribute_creator to shp_polygon the problem was fixed. I'm not sure why this has just started happening (I've never had this issue in the past) but if Safe if you could update this in one way or another that would be much appreciated.
It is not possible to read an attribute from a text file, and to evaluate in the AttributCreator.Example:Attribut A with Value "Some text @Value(fme_feature_tpye) some more text". If the text in the editor of the AttributCreator entered, it works of course. But I read the text from a text file (AttributeFileReader).@Evaluate(@Value(A)) delivers the desired result as error message as attribut likeFailed to evaluate numeric expression 'Some text my_feature_type some more text'. Result is set to null.It would be useful if a function @Result directly returns the result.
More "watchers" like Google Drive Watcher, S3 Watcher, Dropbox Watcher... etc.
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...
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.
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.
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
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?
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.
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.
