Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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.
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...
***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
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.
Hello,I was thinking, in the Python transformers it is possible to save your work as default. Why not expand this option to be able to save to, or load from a template? And maybe Safe want to deliver FME with some great templates for accessing various parts of the Python API?
Usually I have the Feature caching turned ON - and its quite a nice way and a lot faster to debugg a large workspace with this option. However as I am used to hitting F5 I accidentally hit it every now and then and then "resets" all the caching. Is it possible to disable F5 when feature caching is on - or get a pop-up showing: "You currently have Feature caching turned on - do you really-really-REALLY want to delete all your cache and start all over again?" ?Thx :)
The StatisticsCalculator has received a much needed interface update in FME 2019 to limit the volume of automatically generated stats that are tagged onto outgoing features, but I'd like to see even more done here. 90% of the time you actually only need to calculate 1 statistic so I'd much rather see the transformer adapted to operate more like the GeometryFilter where you chose which stats you wish to generate and add them on. This has the impact of people not over generating stats and then having to delete them later, plus it'll be quicker because users don't call more functions than is necessary.This change is focused on efficiency because in training, delegates rarely realise immediately that statistics in here are 'optional' to generate and when they do they spend time fiddling trying to remove them.
It would be of great use, if the settings for feature caching and appending logs are available as workspace settings too.It would necessitate a "tri-state" setting, and have the workbench setting overrule any unset setting in the workspace (which probably should be the default).It might even be good to add them to the Workbench prompt dialog, so the settings are up front.
***Note from Migration:*** Original Title was: Add support for the familiy category Structural Connections in the Revit reader. When constructing in Autodesk Revit the familiy category Structural Connections is widely used for any kind of bolts. The geometry and parameters of these bolts are often exported to a land surveyer so they can stakeout the positions.Right now FME cannot read the familiy category Structural Connections. FME doesn't even post an error message, it just skips the objects.This idea is for adding support of reading these objects.The workaround right now is to change the family category to something else that FME supports but this is certainly not bulletproof and requires manual work inside Revit.
There are times when a workspace (or automation) initiates several processes in parallel.However, it is not always clear which path FME will choose to tackle first.It would be really cool if the physical design of the workspace or automation had an impact. For example, if the order of Reader Feature Types, or the length of the connection line determined the order of submission.Feature Types within a Bookmark might be read from left to right, or top to bottom.Parallel processes that can all start after a trigger would be decided by which path was shortest submitting to the job queue first, to that with the longest path being submitted last.
***Note from Migration:*** Original Title was: Change default value of AttributeValueMapper transformer from 'empty string' to 'No action' A couple days ago I used the AttributeValueMapper transformer to map some values from a database column, to a new attribute value for use in an api. The thing is that only a couple of values had to be 'remapped' for the use in the api, while others could remain the same. In this usecase I was using the same Destination attribute as the source attribute.Unfortunately I was a bit too hasty, and after a while I discovered that some of my original values were remapped to an empty string. Personally I was expecting the default value to remain the same in case no mapping is specified for that specific source value, however by default attributes are mapped to an empty string, as an empty string is the default (of the 'default value' parameter). For my usecase, but also in general, I feel it would be more natural to use the default value 'no action' (for the 'default value' parameter). Also, when using 'no action' for the 'default value' parameter, the (~default) setting of mapping to a different destination attribute, would return a 'missing value' in case no mapping is specified for the source value (which I believe to be more appropriate than an empty string).
At present FME can determine if a layer is frozen in model space but if a layer is only frozen in a specific viewport, it does not appear that FME has that attribute able to be exposed. It would be great if this were an option as at present I am unable to create a TIFF or PDF output that matches what is shown in the drawing.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.