Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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.
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.
***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.
Please add vector formats such as eps and svg to the content types allowed by MSWordStyler. My work around is to produce eps or svg files and word docs separately then open a word document using the MS Word program and insert the eps or svg file in the appropriate location. When there are many word docs and many images per doc it is very tedious and time consuming. Thanks.
Is it possible to add an "Ignore Failed FeatureReaders" workspace parameter, in the same way as it is possible to "Ignore Failed Readers"?
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.
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
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.
When working with a big shared Revit project the use of Worksets is essential for being able to collaborate in the same file. Every object in the Revit file is assigned to a Workset and when the user wants to work in the Revit file he/she checks out a Workset.It would be useful to be able to use these Worksets in FME when reading a Revit file. Sometimes the need is just to read the objects inside a certain Workset and then this parameter could filter out what the user need.So this idea is for creating the same possibility to choose Worksets as to choose Views in the Revit reader.
***Note from Migration:*** Original Title was: Create a igds_info feature with Drawing System Variables like autocad_info but for Microstation V8 DGN-reader The parameter Read Drawing System Variable in the AutoCAD DWG-readers are much used to retrieve information about a DWG-file. Currently there's no equivalent when reading Microstation DGN-files. This idea is for creating a new parameter in the DGN V8-reader: Read Drawing System Variable which creates an igds_info feature which holds information like DGN-version, units, current level an so on.
It would be useful to be able to configure the CouchDB reader to read from a view using a startkey and endkey to limit the returned documents. Since we have views in the database for other uses, it would be convenient to be able to query the views directly from FME instead of having to return all documents from the database and filter them.For example, a database with a view where the keys are built from a retailer name and unix timestamp. The view design document looks something like this:function (doc) { // code for only returning the subset of documents this view is for. // E.g. maybe this view is only for returning sale records if (doc.type != 'sale'){ return; } // output the view keys and values emit([doc.retailer, (new Date(doc.createddate)).getTime()], doc); }I am getting around this currently using the CouchDB http API and an HTTPCaller with the request URL directed to the view and parsing the returned JSON. As shown below, I am getting the records for "retailer1" in the month of February 2020.
What I'd like to see is an option that shows, if you click a transformer, transformer port, feature type or connection, all the places where features upstream or downstream are.I can't seem to attach images right now but here's a mockup I made:exampleImagine you clicked the SpatialFilter's Passed port. The red line shows all features/streams on the input side affecting that port, the green line shows all features/streams where results from this port can end up.I think this could be very helpful in trying to debug complex workspaces, it would make it easier to understand the flow of data. In addition to that it could be very useful for novice users to gain that understanding of FME.
I've been meaning to post this for a long time, because it's a frustrating issue but by nature of where it appears it's usually just when I'm getting into something so I've never prioritised posting this.The 'generate workspace' dialog has a memory within the same session of the last workplace that you built. This IS very handy when you make a mistake adding readers and writers as you can go back and make the small change to a parameter without completely updating the whole dialog box. But, if you start a new workspace and have to update each parameter and perhaps are not thinking about reprojection for example, you might accidentally end up filling in a projection if you reprojected in the previous process!Simple fix, please just provide us with a 'clear all' button on this dialog!
At the moment in the Workbench settings under Tools > FME Options it IS possible to reset the settings on one page, for example on the 'Translation' tab. But if you want to reset all settings back to factory default you have to do every page, one at a time.Please can we have a 'Reset All' button that will clear back all system settings. Or force you to a selection dialog box where you can tick off which settings to revert.This would be especially useful for test deployments, training machines and debugging.It is the opposite of being able to export all settings and share them with a colleague or another machine, but no less important than @takashi's suggestion here https://knowledge.safe.com/content/idea/84078/backuprestore-fme-options-configuration.html .
Universally in transformers, readers and writers that have the ability for the user to select a coordinate reference system, the pick list presented to the user can really easily be broken and can force an error. For old-FME-timers like me that's just a well trodden peril. But for new users, just starting out it's awkward to tell them that this is just the way things are.So, in the Reprojector if a user searches for 4326 and finds "EPSG:4326" but doesn't have the foresight to pick it from the list of presented CRS', and instead just clicks the focus away (which is really easy to do)... the user ends up with this getting filled into the dialog "4326". When the process runs that CRS is found not to exist and the process errors at worst and does nothing at best.Please can this CRS pick list become an uneditable and fixed picklist that allows you to select something from the list or nothing at all. A very simple change but will remove a lot of very frustrating and difficult to debug workspace failures.
If you need a polygon,line or a point as input for a workspace then it would be nice if the user interface provides a map component to draw the object so you can use it.For now I use a custom form with some javascript: WicketBut it would be nice to have it implemented into the standard web interface of FME server.
Derived from: Where are the fme_dataset and fme_basename attributes when reading with the FeatureReader?In most formats, you can read "fme_basename" and "fme_dataset" with a FeatureReader by selecting them through the Additional Attributes to Expose parameter in the reader parameters.It's good but then the schema feature output from the Schema port of the FeatureReader would contain those attributes in the schema definition (attribute{} list), as in:It's just annoying when configuring dynamic schema writer feature type using the schema feature as the schema source. You will have to remove them through the Attributes to Remove parameter in the writer feature type if you don't want to write them into the destination dataset, and I think you don't want to write them usually.In my observation, not only "fme_basename" and "fme_dataset" but also other format attributes will be added to the attribute{} list in the schema feature if you expose them via the Additional Attributes to Expose parameter.I think it would be better if the FeatureReader would never add any format attributes to the attribute{} list in the schema feature.
The ability to add colour to a connection line, so it is easier to distinct between different feature routes
Currently when I use the Directory Watch trigger (or any other watcher) to watch for modified files FME Server will watch on file size only. This means that even if my file has been updated, if the file size remains the same my Automation/Notification will not be triggered. I'd like the watchers to watch the timestamp on files when available.
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.
