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 might be interesting if FME could read data from the Pleiades constellation of satellites. I think AIRBUS has a API to their imagery.I wonder how others would do with this imagery once read into FME?I wonder what aspects of the Pleiades / AIRBUS imagery are most interesting?
I want to use best practices in my workspaces, but I don't want to have to be an expert in them and remember to check - and I get busy and forget and don't know all. I need it to be easy.It would be nice if workbench highlighted what aspect or even what parts of the workspace were not using best practices.Then it would be easy to be best!
Please could FME floating licences be supported over IPv6.
I often want to copy attributes form another FT in a workspace, but more often than not, I only want to use a selection of those. It would be a great bonus if there was a selection box where one could choose which attributes to copy. This would make it easier to combine attributes from different FTs in the output data.
Currently, the only way to specify a Service Account to run the Windows Services is by selecting the Custom/Distributed installation option.
It would be helpful and make my life with three different FME versions on the same machine easier if I could see in the DataInspector Window Title which version is running. It would also be consistent with workbench behaviour.As ffs files are mostly incompatible between major FME versions I have to switch between DIs frequently.
It would be interesting to write the Esri i3s format.I wonder what aspects of i3s are most interesting to others?
While we have flow control to route features along specific connections using the tester, it is inefficient to retest the value of parameter for each feature, especially when dealing with a large number of features.It would be nice if there was some sort of FlowController which could route all incoming feature out of a specific port based on parameter value(s), which is only tested for once, and not a few million times redundantly.
I frequently translate data into Esri geodatabase format. I get the Geodatabase Error (-2147219115): The row contains a bad value regularly when creating a new workbench. this normally just has to do with field length or data type and is easy to fix once I identify the row with a "BAD" value. It would be great if that row was identified somewhere in the log.
It would be nifty if FME could support Azure Cosmos DB. I have some ideas for using it, but I wonder what others want to do with it?[Update] in FME 2017.1 we've renamed Microsoft Document DB to Microsoft Azure Cosmos DB, which support the JSON document store (through SQL API,as referenced here). It would be great to hear what other data models you are interested in using FME to integrate and transform.
Clipping features by using a search envelope currently requires a user to manually enter the bounding box coordinates.It would be very useful if you could simply set the current map extent as a search envelop.
Existing LineCombiner is limited to some 2.5D like behaviour and cannot handle vertical polygons.Suggestion is to provide a 3DLineCombiner which is not limited to special Z handling like the existing transformer.see also discussion: How to create vertical face from 3D linesa related Suggestion is: Solids or Faces from Wireframe
I'm kind of surprised there isn't an Active Directory reader already. Sounds like we can use Python in FME to read from Active Directory, but having it's own reader would be so much easier. Looking to export lists of users in specific groups, but can envision many other uses too.
***Note from Migration:*** Original Title was: Better workflow control of multi-step workspace jobs. Automation of event flows too.
I’m trying to call a SOAP service from FME Desktop using the HTTPCaller. This service is secured with WS-Security and requires a username token and digital signature (from a PKCS#12 bundle). I’ve managed to get this working in SoapUI by following this documentation. Is there any way to apply this type of security in FME Workbench?Thanks in advance!
Backup and restore: migrate a single workspace and associated resources (for publishing between different environments, e.g. DEV->TQA->PROD)
As of FME 2017.1.2, it appears that only TomTom / Tele Atlas MultiNet 3.2 is supported, with partial support for 3.3/3.4.
The current version included in SQLITE is almost three years old - 2013-12-06 (3.8.2). There have been quite a few enhancements...
The current FeatureWriter only have a summary port, so If I want to continue my translation after the FeatureWriter, I will need a featureholder to wait for the summary port. I propose to add an output port to FeatureWriter with all the features, so I can continue to process my data after the data is safely written with FeatureWriter.
The idea here is that bookmarks could be collapsed to hide their contents and reduce clutter on the canvas. You could temporarily "expand" them but they would open up "above" the canvas in their own floaty window, with scroll bars etc. A bit like a custom transformer that can't have more than one instance going at a time.
After the support in FME 2018 for CALS-files I think the next step is to support the old format PLT. The format was widely used in CAD systems when plotting to HP plotters using HPGL and/or HPGL/2 during the 1980ies and 1990ies but we still find them often when helping customers. As the format stores vector data the data is still usable and many blue prints for houses and other constructions are stored in PLT.
***Note from Migration:*** Original Title was: Can Safe FME add Bentley Geopak Database Reader and Writer to their repertoire translators? We have thousands of actuate legacy Open Roads Geopak databases to add to the life cycle of roads infrastructure.
COINS is an emerging linked data standard for the exchange of BIM information. So far we've seen it mainly in the Netherlands but perhaps it's getting used in other countries. http://www.coinsweb.nl/
At the moment the order of input/output ports on a Custom Transformer is determined by the vertical ordering in the workspace. This seems awkward at best. I would like to propose a system similar to that of ordering Creator transformers or Connections. An alternative would be to use drag 'n drop in the Navigator to set the order, similar to the order of Readers and Writers.I am aware that it is now possible for the user to change this order. That's fine, but I would still like to be able to provide a reasonable default. For example: I'd like my Rejected output port to be the bottom one.
There are occasions when developing that I create a complicated set of test conditions in a tester or via the conditional attributeCreator, and then find that I need to use a testFilter, or consolidate attributeCreators instead and there is no easy way to copy the information from one transformer to another.
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.
