Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
***Note from Migration:*** Original Title was: Change Feature Joiner behavior so records with Null in the left join on field are not ignored Currently, if you use Feature Joiner to join two data sets and you set it to be a Left join the Left join On field is null, the record will NOT emerge from the joined port. This is contrary to what one would expect from a left hand join where ALL records from the left table should emerge from the port (eg as in ESRI, MS Access, SQL etc). This is dangerous behavior and will no doubt cause a huge number of errors.To get something that looks like an actual left join, you have to filter out the null values in the left key and add them back in later, which is utterly crazy in my opinion.Please could you either change the behavior so that a left join behaves as would be expected, change the nomenclature so that you don't use left, right join etc (the very nature of naming conventions the transformer makes it seem more SQL like) or at the very least have a warning to indicate it is unable to process null keys.
It would be very useful for @Timestamp function to return @Timestamp("^Y^m^d^H^M^S") by default
In Tester 2019 there was a UI change, which changed setting composite tests totally. I prefer the old way of one composite test clause, in which it's much easier to put opening and closing brackets and faster to define the test.Idea: Keep the old composite test. The new UI doesn't need to be changed, just add the old composite test syntax under the test clauses.
Hi,I have a .las file which I'm trying to convert it to .obj. I also have .dwg of the point cloud file. Since I'm new to FME, I was wondering if anyone here already has done this process and I can use their experience. Thanks for your help
Catches a translation error and outputs a feature containing an attribute that stores the last error message. If this transformer exists in the workspace (or a Bookmark?), a fatal error can be detected without stopping the translation, and the user can handle the error as a part of the workspace.Works like the 'catch' clause in a C++ program or the 'except' clause in a Python script, the user could improve the robustness of the workspace.The Terminator transformer should work like the 'throw' in C++ or 'raise' in Python if the 'ErrorCathcer' exists in the workspace.[Addition] It might be ideal if a Bookmark could work like the 'try' clause.
There isn't quick way to clip surfaces by areas currently. Perhaps introduce a new transformer which performs clipping surfaces by areas, or upgrade the Clipper transformer to accept surfaces as Clippee.It would be ideal if solids could also be clipped by areas.
I'm liking the new stats calculator setup in 2020, however i think the fact that you cant rename the output attribute inside it like the previous version is a bit limiting, meaning you have to add a subsequent transformer to handle that.
We often run long workspaces on secondary machines, and that means that floating licences are tied up unnecessarily once the workspace is complete, until someone checks the session and closes FME workbench.It would be nice to have an option to "save and close workpace on successful completion". That way the licences become available as soon as they are not needed, but if there was a failure we would still have access to the feature counts and inspection bubbles to help troubleshoot the issue.
Add support for FeatureWriter as a source for the zip file content of the data download. At the moment only Writers are supported.
The message should tell the user which version of FME the workspace was created with so that they know which version to use. At present I have to open the workspace in a text editor to determine the version.
It would be nice to be able to handle information about the lifecycle of Workbench I make. Not only attributes like version numbers , create dates etc., but also status like 'in development', 'ready for test', 'accepted', 'in production', 'end-of-life'. And it would be marvelous if FME Server would support this info too. E.g. that I can filter all WorkBenches that are not accepted, or that I can easily take all 'accepted' WorkBenches into production.
The ability to be able to send and receive data streams to an ArcGIS GeoEvent Server (like what we can currently do with the KafkaConnector)
Duplicate of Workbench connects directly to revision control
When building workspaces that needs to run on various platforms with various operate systems I use the FME parameter FME_OS to create OS specific attributes to read/write data. But this parameter is excluded in the documentation:https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Workbench/!Transformer_Parameters/FME_parameters.htm and it's not in the help at all: https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_Workbench/Search.htm?q=fme_osOne specific thing I think should be useful (at least for me) is which values this parameter could hold. Right now I need to find a computer which have that specific OS and try the parameter to see which value the parameter holds. Not that streamlined.
In a recent project, I realized that the collaboration of Google Vision AI and FME through the GoogleVisionConnector is very helpful to solve a text detection problem.The current GoogleVisionConnector has three detection types - Text, Object, Face, but the Google provides more types. It would be wonderful if the GoogleVisionConnector would support other detection types as well. Especially I'd like to use Document Text Detection.
In a FMEServerJobSubmitter transformer, the published parameters are not automatically updated.So if you change the parameters of a workspace (create or delete parameters), and call that workspace via a FMEServerJobSubmitter, it will cause a problem.When running a process on FME Server that has an outdated FMEServerJobSubmitter transformer in it, the process is not even called or you don't get an error message.I would suggest to throw somekind of error message so you are aware that you have to update the FMEServerJobSubmitter transformer.
Single Sign-on is working fine when accessing SharePoint in a web browser Web or or via the SOAP/REST API even with HTTPCaller.It would be nice to be able to use Single Sign-On authentication in SharePoint List reader writer, too. I'm OK with the APIs but it takes more time than a List reader...
Can we ad ADFS support for sharepoint?
Hi, at the moment FME support the OGP P1/90 format, and this has now been replaced with the OGP P1/11 Geophysical position data exchange format. Suggest that FME implement this new format as well"Originally released in 2012 to replace the UKOOA P1/90 and P2/94 formats, Version 1.1, released in August 2018, incorporates industry feedback from the first release and provides greater flexibility – without changing the fundamental format structure. For example, the format now enables the recording of land and OBC formats and additional peripheral sensor, or QC data. It also includes enhancements such as: handling channel grouping, ‘virtual’ position objects such as mid-points, global pre-plot attributes, event-based attributes, receiver and source relation records."URL: https://www.iogp.org/bookstore/product/ogp-p111-geophysical-position-data-exchange-format-user-guide/
Use SlackConnector to send a message to a person. You can currently only publish a message in a channel.
***Note from Migration:*** Original Title was: Change the behaviour of the fme:get-list-attribute("") function in a JSONTemplater, to always return an array (not just when the list contains more than 1 element) I hope the title is already quite self explanatory.Let me explain with an example.Consider the following two lists;Note that list_1 has a single element, and list_2 has two elements.When I then use the following text in a JSON templater;I obtain the following result;{ "list_1" : "a", "list_2" : [ "b", "c" ] }Whereas the following addition of square brackets in the JSONTemplater;does produce the result I would consider to be the the desirable result from the 'fme_get-list-attribute("")' function.{ "list_1" : [ "a" ], "list_2" : [ "b", "c" ] }undesired_behaviour_getList_function_in_JSONTemplator.fmw
***Note from Migration:*** Original Title was: Google BigQuery Package: Add an optional parameter to Google BigQuery Writer to specify Service Account Key File Path The Google BigQuery writer has an option to use a Service Account Key File to authenticate Google BigQuery connection.In my observation, if you use a Service Account Key File, you have to define an environment variable called GOOGLE_APPLICATION_CREDENTIALS in your system to specify its file path, so you need to modify the variable whenever you run the workspace for different project. Also there could be a case where you aren't allowed to define the environment variable in the server system due to the limits of your user permissions.It would be better if the key file path could be specify through a writer parameter explicitly.
It seems that the current Google BigQuery writer firstly writes all the features into a temporary CSV file then loads them into the destination BigQuery table. I thinks it's a good mechanism if you load many features into a BigQuery table at once, but it may not be good if you need to write a single (or a few) records into the table frequently (e.g. write 1 feature per a minute), since BigQuery has limits the maximum rate of incoming requests.Quotas and limits: https://cloud.google.com/bigquery/quotasHowever, there is another option - Streaming data into BigQuery in order to perform frequently writing features into BigQuery table avoiding the limits above.Streaming data into BigQuery: https://cloud.google.com/bigquery/streaming-data-into-bigqueryIt would be wonderful if the Google BigQuery writer could also support Streaming data into BigQuery optionally or you could add a new transformer (e.g. GoogleBigQueryStreamer) to the package.
The FME AR app is really easy to use and is an incredibly quick way of making models usable in augmented reality. I am however missing the ability to know at what scale I'm viewing content within the app. So here are a few improvements to the app that I would like to see added:Tap for real life scale: A simple button that scales between "model sized" and its true real life scale.Stats for context: The ability to show stats that show some context to the model. For instance, what scale the model is shown in, the current dimensions of the model and the real life dimensions of the model.
Since 2016, "all HTTP-based formats received a new SSO authentication option". At about the same time this announcement was made, Portal reader and writer were also released but the reader has issues depending on your authentication options; the writer is also somewhat broken as it works with writing new feature layers only but not updating existing feature layers. I wonder if the update would work if SSO is added.
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.
