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 OffsetCurveGenerator comes in handy sometimes, but I think there's something confusing about it: it flips direction of the line for the 'Right' output.Would be beter and more logical if both outputs would keep the same direction as the incoming line
***Note from Migration:*** Original Title was: Log: include the FeatureReader transformer name in "Suppliers First option is enabled..." warnings Is it possible to add the rransformer name to the Suppliers First option is enabled and a new Supplier has been detected after the processing of Requestors has begun. Ignoring all new Suppliers warning in the log?It is a hard time to find the 'offending' FeatureMerger when there are many ones in a workspace.
Hi, I have a simple idea / request: if you search in text (CTRL+F in the different text editors, in the python caller window, ...) you can now choose between "Previous", "Next" and "Close". Universal, functional and simple!However, sometimes I would also like to know how often the searched string appears in the text: would it be possible to add an extra "Count" button to indicate the number of occurences of the searched string?My workarounds now are:Use replace instead of Find, which then gives the number of occurences:Afterwards I have to think about undoing or canceling of course...Or copy the entire text in Notepad++ and use the functionality that I would like to also have in FME:Would be nice and handy sometimes!
Option to have a version control of automations in FME Server
This wish/idea applies to parameters with aliases. I’m finding cases where I need to make a decision somewhere in the workspace based on the Display Name of a parameter, not the Value (for parameters with aliases such as the following):However only the "Value" is visible in the workspace. The only way I have found to get around this is to avoid using this type of parameter and only use the “Choice” version, then use an AttributeMapper in the workspace to map the needed value to a new attribute. It would be great if the "Display Name" was also accessible in the workspace to avoid having to use the AttributeMapper workaround.
I think this granular email notification for scheduled tasks must b much easier. Like the one when task in run ad-hoc. Not like now via topics/subscriptions.
Add the link to FME Functions and Factories documentation (https://docs.safe.com/fme/html/FME_FactFunc/index.html ) to Help menu to quickly access it.
To better organize the entries from the dashboard tables (especially the "Daily..." tables), it would be helpful if the date on the x-axis would be supplemented with the day of the week.
Spent 30 minutes scratching my head why LineCombiner wouldn't merge together some segments on a common Attribute, until figured out that it refused to combine line segments that had a common Attribute, but had unequal Geometry traits (that had been picked up from an earlier GeometryValidator that checked for 2D self-intersections). In most case as the LineCombiner is a type of merger/dissolver, would it be better for the default behaviour to ignore if Geometry traits were equal or not? There is a workaround in using a GeometryPropertyRemover prior to LineCombiner, but maybe at the very least this should be in LineCombiner's usage notes in the Help.
The "Industry Foundation Class STEP/XML Files (IFC)"-reader can today not read the Application Protocol 214, Automotive Design.This protocol/format is seen as an industry data exchange standard, so having FME supporting it (read and write) is important.There is an open source library that supports step-file read/write, Open Cascade (OCCT), that seems quite competent!Today I use FreeCad (which uses occt) to open step-files and save them in IFC, and that file I can open in FME. But this is not an option when we need to automate things with FME.Another topic addressing this: https://knowledge.safe.com/questions/71863/convert-step-files-stp-using-fme.html@daleatsafe @frro
Still don't know why right-clicking on table feature row doesn't give a pop-up menu with options to perform target-based functions (e.g., zoom to, pan to, flash, save, save as...a la ESRI's ArcMap). For a significant number of us who use ArcMap, this is a natural action to take since it doesn't require navigating to the top and clicking on an icon or selecting a menu from the top menu. We consider the Data Inspector a very valuable part of the FME suite. As an experienced user I consider Usability/User Experience functionality fairly seriously since the rest of the product's functionality is flawless based on what I use it for. Please strongly consider this enhancement request.
The workflow for entry doesn't seem as intuitive as it was in the past (primarily when editing the schedule of existing jobs).1) If you start typing in the date, it isn't saved when you click off of it. You have to hit <tab> to keep the value you entered.2) The start date can't be in the past.3) It would be better from a user's perspective to allow me to put a date in the date field without popping the calendar up. If I wanted the calendar, I would click on the green calendar icon.
Within the MapboxStyler transformer it would be great to have the option of an attribute value in the Marker Symbol option. For instance if my attribute values are integers 0-99, Mapbox can take that number and put it in the marker symbol (ref here:https://github.com/mapbox/simplestyle-spec/tree/master/1.1.0) and basically create a label. Right now the only option is to choose from the marker symbol list and then use StringReplacer for the marker symbol attribute and replace it with the integer attribute value to create that marker
***Note from Migration:*** Original Title was: Setting ArcGIS Pro 2.4 in the python interpreter is not available yet - fixed in 2019.2 release? Hi,We are finally switching to FME 64 bit and have new machines to test it on.We are going to install version 2019.2 and are wondering if ArcGIS Pro 2.4.2 is the best choice due to the notice on the esri compatability matrix that Setting ArcGIS Pro 2.4 in the python interpreter is not available yet?Was this issue fixed in the 2019.2 release?Or should we go with ArcGIS Pro version 2.3.3? Thanks,AnnetteStedin, Rotterdam
Kind of an addition to:https://knowledge.safe.com/content/idea/18817/pdf-page-formatter-parameters-from-attributes.html Would love to be able to see some extra options for the Page object location based on values in the attribute table. With the idea that you don't need input ports but can use a generic input port that filters the objects that need placing based on basename, feature type or some kind of group (i.e. map, legend, rasters). Adding a generic input port where you need to define an attributes for the upper left x, left y, height en width of the object. By doing so all object can be placed in the PDF page mathematically instead of drawing boxes by hand and always have check if the aspect ratio is in order.
Would be great with improved logging on the TINGenerator, right now it is not possible to know how long the operation takes. In percent or in time or in vertices. For instance a % of points used or % of vertices created (estimate) would be handy. Then you can easily spot neverending and huge TINGenerators.
FMECommunity - add all transformers as topics or add a new category called "Transformer" so you can find all topics related to a specific transformer.
Make it possible to upgrade existing Reader / Writer to a FeatureReader / Writer with the same parameters, featuretypes and attributes.
I'd like to be able to configure the text paramater to set a maximum length. The use case is quite simple. People have an option to make a remark with a certain workspace. The remark will be added to the dataset in a field. However the field has a maximum of characters allowed. I would like to set this number of characters, so I want have to make the workspace fail if people add to many characters in the Parameter.
***Note from Migration:*** Original Title was: Ability to move down and up feature types in Navigator to specify their order of reading Its possible to move up and down datasets in Navigator to specify their order of reading by FME. Why not the same ability for feature types ? Maybe because each reader has his own characteristics of reading ?
Hi,I quite often want to know how well my workbenches are running and check the status of the last few jobs. The sort of summary stats i pull out are, avg runtime, max runtime, avg feature count, max feature count, it'd be also nice to plot specific jobs on a graph for these types of stats.Historically i have always accessed this data through a database connection to the repository fme_job_history table (and it's predecessor), however i'd like to move to using REST if possible.To do that efficiently though i need a new end point which is something like:GET transformations<repository><workbench>jobsThis would return a list of all jobs running, queued, and finished etc, relating to that workbench.ideally i'd also like to be able to pass a query parameter to filter the response, maybe start_date=<ISOdatetime> and end_date=<ISOdatetime>Surely i can't be the only person doing this?
Would be very nice to send a workbench with a token using FMEJobSubmitterBye Bye the username and password !!
***Note from Migration:*** Original Title was: Integrate Desktop and Server more closely. Execute tasks on Server thru workbench gui.
XMLXqueryExploder and XMLXQueryUpdater are very powerful transformers when you use XML inside FME but they lack an easy starting point. It would be such an improvement if the "XQuery Expression window" had code samples in the left panel (similar to the XQuery Functions) providing the user with basic code snippets that would help them forward quickly.Such snippets for example could be- How do you count child-nodes - Replace content of a property- Replace content of a node based on a string in child-node- Find domains from an XML
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.
