Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
FME Desktop / and or Server should use default python installation, so that all existing packages and or fmeobjects should be in the same python interpreter.I think the use C:WindowsSysWOW64python27.dll is not a very good implemetation (due to various installation of python).During installation of FME Desktop / Server it should be able to detect python installations (if none install a python interpreter), and then setup accordingly. so the custom / default python should be combinedWith this you then can choose between for example 2.7 32-bit and 3.4/3.5 64-bit etc.
The 'Set Connection Runtime Order' at the output port for every transformer has been introduced in FME 2016.1. It's very useful to control the feature flow, but it might be further better if the user could also control the connection order at the input port optionally.In-Flow Control: Optionally the user can specify the order of the input connections flowing into a transformer. Also it should have the "Group By" parameter.This would allow the user to control the input order for some transformers which combine features coming from multiple connections, such as RasterMosaicker, RasterBandCombiner etc., without using the Sorter. The expected function may not be useful to most transformers, so it's also good to add the function to the Junction.
If you want to detach a transformer from a connection, you have to delete the connections and create a new one between the neighboring objects. It would be great to have a feature that does the same as when you delete a transformer: conserving the connection, but at the same time keeping the transformer.
The FeatureMerger has the option for 'Suppliers first'. Checking the box indicates that all Suppliers should arrive before any Requestors arrive. If a Supplier arrives after a Requestor has arrived, it is ignored.However, I've run into a few cases where I can't get all the suppliers in first. I can guarantiee that a specific Supplier arrives before any of the Requestors that match it. My proposal would be to not ignore Suppliers arriving later, but just add them into the mix. A warning could be shown in the log to indicate this happened and a possible mismatch could have occurred. The alternative is not enabling 'Suppliers first', which is quite detrimental to performance.
Go back to where we used to get ESRI access by buying the ESRI edition.If not possible get a plugin at the same price users pay for the interop extra plugin ie.$1000 rather than having to buy a full license to stick on an FME desktop or server box to enable all the ESRI formats.
Would be nice if:There was more space between readers by default Annotation addition would attempt to space things out automaticallyThe second way might be useful across the board.
When searching for objects in Workbench with Workspace Search for a second time, the text in the field Find need to be cleared manually. (Backspace or select all delete.)Suggestion is to always select the text in the field Find. This way you can hit a new search text without having to backspace the previous search text. This is the way other software (for example Notepad, Notepad++, Excel, etc.) works, feels naturally and speeds up multiple searches.Current:Proposed:I understand this isn't a groundbreaking idea but it feels a bit annoying every now and then when I fail the second search.
Write Autodesk Filmbox format. Useful format, when lots of game engines are reading it in. Would help with city modeling and working with 3D material.
***Note from Migration:*** Original Title was: Exclude junctions in the objects to be aligned (vertically or horizontally) on the canvas When aligning horizontally or vertically objects on the canvas, if a junction is selected it will align it as well giving unwanted results. Could junctions be automatically omited?https://www.youtube.com/watch?v=eVFaJqe-bIw&feature=youtu.be
I want to split features that are paths so I can access polyline and circular arc components along a parcel boundary course. First I need to detect paths!
To help with the clutter in the big list you get with some formats and you want to see the set you are adjusting.
There are some parameters I use in a lot of different workspaces (ex the scripted parameter that put's a time stamp on the log file name). It would be nice if I can save them to a favourites list and then add parameters from favourites.
***Note from Migration:*** Original Title was: Add a new parameter Common Attribute Values for transformers that group attributes and builds list like TopologyBuilder Using TopologyBuilder, to retain the common values of an attribute as an edge and node attribute. Add a new parameter Common Attribute Values with a predicate textbox named _common_ to attributes found to have the same values on the grouped attributes. E.G. a road or a network line which has a common ObjectID or unique name, 30526 or Happy Hill road, an attribute called _common_ObjectID = 3052 and _common_Road_name = Happy Hill road will appear on the attributes of each edge and each node.
Use the TAB key as selector of a choice in pull downs and to go to the next focus, instead of using Enter first for selection and than TAB to go to the next focus.
I think the documentation is in desparate need of improvement. Some examples and clearer wording would be very helpful.This excerpt from the Intersector Transformer is a good example of a help page that needs some improvement:"Note that you could also access the individual street names by "exposing" some elements of your list (by right clicking on the attribute unqualified list name (in our example, "all_streets{}.NAME") and saying "Expose Elements", and entering the number of elements to expose. You'd then have to do something with those elements in your translation. (The disadvantage of this approach is that you need to know ahead of time how many list elements you want to work with -- so if 3 streets intersect at the same node and you only set yourself up to handle two, you'd have to do something special to handle that.)"Ok, I need to do something special. Care to elaborate?
Problem: FME has hundreds of transformers, with sometimes interesting names, that can be difficult for a newer user to understand. In this scenario, we borrow from online shopping sites (like Amazon) and provide recommendations for other similar-ish transformers based on our usage stats. Hopefully users then discover "new powers" to get the job done and don't feel so lost. Hypothetical example: "Other FME users who placed a Clipper also used a FeatureMerger, Tester, and AttributeCopier." Then use the Transformer Help to port in the quick description and/or image for context (maybe that information is hidden by default?). Where and how does this information get presented? I'm not sure, but I imagine it'd get most use if in product. Whether or not it's a good idea or even feasible is something I leave for you to assess.
Some of the ideas are very common problems and have either a non-obvious solution or have been implemented. It would help if all the implemented and solved ideas were collected together into a hot tips or put into the knowledge base or even the help for relevant transformers.I really liked the method for bulk changing of the width of 200 char fields on the writer. Who knew that? Yet I have been using and teaching FME for years!
The Transformer Reference Guide in A5 format is much prized by students in the Basic Course. It would be great if there were similar handbooks for other parts of FME such as readers and writers, server and maybe the store. i know the trend is to webify all documentation and help for ease of updating, but a small summary booklet when learning is a great aid - and marketing giveaway.
I think the opacity of the bookmarkfilling is not enough sometimes the connections between the transformers aren't really vissible.
The same way fmwt files can install data , fme would delete the files and directories it has created.
In FME 2016.1 RC, I found that the user has to click [Help] button or an equivalent command to access the help doc of a transformer. It's good for regular transformers, but custom transformers don't have [Help] button, so you cannot change the Help window to the help doc for a custom transformer while editing its parameters. [Defaults] button in the parameters dialog of custom transformers is useless, but [Help] button might be helpful.
Currently the Dataset Fanout cannot create multiple zip files. A workspace with this setting will archive all destination files into a single zip file, even if the value of "_fanout" varies depending on the features. Hope FME will do fanout zip archiving.
Add an .fmw reader - reads a workspace and outputs stats from the workspace -Reader/FeatureTypes/Attributes -Transformers/Count of/output ports connected -Testers/Query/etc.. Mainly the first point there, the ability to output a table that gives you the workspace name, reader type, feature types per reader, attributes per feature type. Would allow for a quick assessment of what scripts interact with what data and hence give a sense of what is impacted if a source or destination is changed.
***Note from Migration:*** Original Title was: Introduce "Attribute Accumulation" parameters group into SpatialFilter and SpatialRelator In FME 2015, a common parameters group called "Attribute Accumulation" has been introduced into some transformers, which allows users to control how to resolve conflict between attribute names. e.g. Clipper, FeatureMerger, NeighborFinder.Like that, I think that the SpatialFilter and SpatialRelator may also have the "Attribute Accumulation" parameters group.
Regarding these commands in the Options menu of the Text / Arithmetic Editor.Show Line NumbersShow Spaces/TabsWord WrapCurrently the initial status of those commands (checked or unchecked) is always the same.I think the most suitable status is different depending on user's preference and the current context that the user is working with, so it would be better if the status that the user has set could be preserved as the next initial status.
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.
