Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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.
As far as I know, at the moment the only options available for offsetting a 3D polyline is the Offsetcurvegenerator or the offsetter transformers. The Offsetcurvegenerator even with the 'miter' option still generates additional unwanted points along the line and the Offsetter is unable to do a parallel of the original element. Us survey folks would really appreciate a more robust and reliable transformer capable of this function.
***Note from Migration:*** Original Title was: Make the default of 'search' or 'replace' stringfunctions case insensitive instead of case sensitive to match the default of the equivalent stringsearcher/stringreplacer transformers Today I noticed that the for the 'search' or 'replace' string functions that are discussed here, the default setting is to match 'case sensitive', where one needs to specify the optional parameter [caseSensitive] to 'FALSE' to make it match case insensitive. I thought this is a bit confusing, as the default for the equivalent transformers, i.e. the stringsearcher and the stringreplacer, are set to case insensitive. The string functions this concerns are;FindRegEx(str, regExp, [startIdx], [caseSensitive], [caretMode])FindString(str, findStr, [startIdx], [caseSensitive])ReplaceRegEx(str, regExp, newStr, [caseSensitive])ReplaceString(str, oldStr, newStr, [caseSensitive])Personally I prefer the default in searches to be case insensitive, so I would like it if the default of these string functions can be changed to 'case insensitive'. However, besides my personal preferences, I think it is even more important that the case sensitivity setting of these string functions and the equivalent transformers should be consistent with each other.
***Note from Migration:*** Original Title was: Add option to string function 'ReplaceRegEx(str, regExp, newStr, [caseSensitive])' on what value to return in case no matches are found (similar to the option in the equivalent stringreplacer transformer) I hope the title is self explanatory. Today I was using the string function 'ReplaceRegEx(str, regExp, newStr, [caseSensitive])', and found out that in case no match is found by the regExp, the 'newStr' is set to 'str'. To start, I think it would be nice if a description on the behaviour of this function in case no matches are found, could be added to the string function documentation.Depending on what you aim to achieve with the function, the default behaviour can be a bit confusing. For my case it would have been better to have the option to set the value to an empty string (as I was using the string function to replace the original string, with parts of the original string, using replacements based on 'capturing groups' of regex). However, I can also imagine that in most use cases the preferred default behaviour would indeed be to return the original string in case no match is found. In the equivalent stringreplacer transformer it is possible to specify a value in case the attribute value does not contain the text/regex, by using the option 'Set Attribute Value To'. It would be nice if this option can also be added to the string function (as an optional parameter?).
It would be nice to assume that text width 1073741822 is matching to "unlimited" width text format
It would be useful if the workspaceRunner when set to wait for job to complete Yes could return the fme global variables like fme.featuresRead, fme.featuresRead, fme.totalFeaturesRead , fme.totalFeaturesWritten, fme.logFileName etc.I imagine this would be a list added to the feature and ideally you could pick and choose which variables to include.
Hello Team,I have small idea regarding installation of Python27 while installing FME desktop or server.As we all know Python27 is going to be deprecated soon, So why can't we suggest Python installation with latest version which could be compatible with latest versions of FME desktop or server.Hope if we have given a option to install latest compatible python version along with the FME desktop or server installation then it may save some time and no need do go for other configurations to map to the latest version of python.Thanks...
To count the number of features I use the StatisticsCalulator. I don't want to use an attribute to analyse, I only want to know how many features have past the flow to continue if it is below a certain amount. Bij (optionally) adding a count-attribute to the featuerholder it is more efficient to achieve this. The attribute is added to all the features.
I'm running a workflow where I need to publish files to an SFTP Site, then delete the local files on my system. It would be really nice to be able to setup a SFTP Subscriber on FME Server, then on completion, you notify a topic that can trigger another Subscriber (in this case I want to delete local files). I can use a workspace to do this but I think this type of a workflow may come up for others and would make a great enhancement.
Client machine bandwidth tester / reporter (e.g. speedtest.net) I think it would be useful for certain jobs to only run if they have the bandwidth needed. Transformer could run test and report.
I would like to be able to set user-defined guides in FME (like arcgis's guides in layout space). Say, I have a large number of readers I want to line up. Right now this can be tedious.
There are two symbols for readers and writers, arrow comes out from cylinder for reader and aroow goes in to cylinder for writer. instead , its better to have different colors and symbols for reader and writer. Because its very difficult to identify the reader and writer from top off head or overview
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.