Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Any hope of getting a way to write 3D output directly to BabylonJS, a webgl driven javascript 3D game engine (physics, interaction, 3D rendering etc.) Could be a great way to push out 3D city-size models of areas (like what ArcGIS does with CityEngine (http://www.esri.com/software/cityengine) to explore 3D city environnents
Itwould be useful to rotate results in inspector as sometimes we are given mapsthat contain previous results and the only way to compare them is by twistingyour head so that you can compare them—the new FME Output with an old map—side byside. It might seem like a silly request but it can be very useful. Sometimes itjust makes sense to review the data by zooming in, rotating it to put thingsinto the right context.
***Note from Migration:*** Original Title was: Add a transformer like the AttributeSplitter that allows attributes to be split based on a delimeter or on a start and end index into multiple new attributes. Example:Input attribute TEST value 1,2,3,4Split based on delimiter: ,Output attributes TEST1, TEST2, TEST3, TEST4Example2:Input attribute TEST value 1,2,3,4Split based on index:start 0 end 2, new attribute TEST1 value 1,2start 3 end 6, new attribute TEST2 value ,3,4This can be done, but requires multiple transformers insequence.
In the FeatureMerger you can have the following combination:- Feature Merge Type = Attributes Only - Process Duplicate Suppliers = YesWith the scenario above, the Geometry Merge Type should not become active, since it is only allowed to merge attributes. However it does become active (and probably doesn't work) and it confuses me everytime.
I am doing more and more with Javascript frameworks (bablylonJs, a 3D webgl game framework, KendoUI Javascript controls, etc.) The nice thing about their documetation is that they not only describe the api, but also have a online playground (like DOJO, JSBIN, JSFiddle, etc.) where you can see how feature works.Here is my brainstorm. For some of the more confusing transformers, eg. FeatureMerger, what about a limited FME cloud driven space which gives you a JSBIn like framework where one can see an example of how the transformer works? So that it does not cost you much $$ to leave up. It could be restricted to a very limited data set, and only be one transformer linked to a "online version" of the Data Inspector. All the levers I would have would be to change the parameters of the transformer from the default demo to different values so I could play with it?
Give a count on every unique value inside an attribute would be extremely useful to improve cleanup of data flows. A simply popup after a right click on the attribute would be such an improvement and reduces the development cycle.
I need a GroupBy function in the ListRangeExtractor transformer. Now the complete range is extracted, but I need it to be extracted per group.
Managing multiple FME Cloud instances (and I guess this could apply to FME Server too) could be a bit easier if the instance name is mentioned in the page title, so that it also shows up as the tab title in the browser.
Sometimes FMEJobSubmitter lost the connection to FME Server because there is a time out or an another IT reason.Add an option where the transformer retry x times to connect to the workbench (example: Recovery mode).
Netty is a great tool but Nodejs is very powerful. Do you have any plan to integrate a node server with FME Server ? :)
I created a Python Creator to export some features from Oracle Database using this python library cx_Oracle. And for each test, Python is more faster than Oracle reader with a where clause.43 features.Python results: 4.0 seconds to export Oracle to Json fileOracle results:6.1 secondsMay be Oracle Reader loses time in the initialization.
Ability to select multiple attributes in StringPairReplacer (like StringReplacer). So don't create a result attribute or propose a table with source attributes name and destination attributes name.
I would like to throw any file at a (Feature)Reader, no matter what the extension is. So whether the extension is something weird or it's missing, if I have a KML Reader for instance, I would like to have the file opened as a KML (and if that fails, try it as a KMZ etc.).I realize this would require some additional checks for the Reader (check if it's zipped and so on), but I don't think this is too hard to implement?
The number of regular transformers is now more than 450. This allows users to perform various translations depending on requirement. On the other hand, this also brings some difficulty when searching a required transformer, especially to beginners.To reduce user's effort to search a transformer, how about adding a special folder (e.g. "Favorites") to the Transformer Gallery?- The folder contains most frequently used and/or most fundamental transformers (30-50) by default.- The user can add/remove any transformer to/from the folder optionally through easy operations on the Gallery interface. Maybe right-click menu commands are preferable.- The default transformers set can be restored. FME Options | Transformers: Click a button -> Show a message "Are you sure...?" [OK] -> Restore the default.- The folder can also be hidden optionally. FME Options | Transformers: Uncheck a checkbox e.g. "Show Favorites Folder in Transformer Gallery".The folder may be useless to users who are familiar with most transformers, but I think it would help beginners to make things easier.
How about merging these items?Run > Enable All BreakpointsRun > Disable All BreakpointstoRun > Enable/Disable All Breakpointscf.Readers > Enable/Disable Feature TypesTransformers > Enable/Disable TransformersTransformers > Enable/Disable InspectorsWriters > Enable/Disable Feature Types
Highlight all canvas objects for whom an updated version is available in the current FME release. Then provide a way to upgrade each one, one at a time, to engage the latest functionality while allowing any parameter/port changes to be dealt with. (Readers and writers updatability can be voted on over here: https://knowledge.safe.com/content/idea/18878/versioning-of-readers-and-writers.html
Just today FME 2015.1.3.1 build 15573 has been available. Users who have registered in the download page received a notification mail, but others may not know yet. Since the update could contain some important hot-fixes, I think it should be informed to every user.How about checking for updates automatically whenever the user opened Workbench and other components of FME Desktop?- check for updates automatically when opened by default,- show a message box to prompt update if a newer version has been available,- the user can stop/start the automatic checking optionally. e.g. check a checkbox in the message box to stop; stop/start by a setting in the About dialog or FME Options.- manual checking can also be used (current menu: Help > Check for Updates).It may also be good if the user could choose the frequency of the automatic checking for updates. Once per Day, Once per Week, None, and so on.
1. In WorkspaceRunner, it is better if we have option to disable the reader or writer, it will be better. Disabling writer/reader should be done with the help of input itself.2. We are passing the parameters to workspacerunner with the help of csv/xls file. For each parameter even the format of attributes from coming in are same still we have to select manually. Automatic mapping of attributes with parameters will also help even better
***Note from Migration:*** Original Title was: Oracle SDO Writer to use calculated CS extents when creating sdo_geom_metadata entry When an Oracle spatial table is written, a metadata entry in user_sdo_geom_metadata is created with layer CS extents (Max X Coord, Min X Coord ....) in DIMINFO column taken from "Format Parameters" setting of the Writer Property menu. I think it will be helpful if FME allows CS extent settings on the "Format Parameters" tab to be OPTIONAL, in which case FME automatically calculate the extents from the source data for use in the created metadata entry.
The default behavior of the ListExploder in 2015+ is different from 2014 and earlier. Many users expect that the transformer behaves with "Use Incoming List" mode (it's equivalent to the default in 2014), but the current default is "Use Original" in fact. In the Community Answers, I have seen several questions caused by the conflict, and I myself often forget to check this setting too.The default itself is not an issue. It's the issue that the "Attribute Accumulation" parameters group is not expanded by default.Hope that the parameters group will be expanded (shown) by default.
***Note from Migration:*** Original Title was: Contrast enhancing transformer for rasters with various contrast enhancement algorithms A contrast enhancing transformer for rasters with various contrast enhancement algorithms.Technically a user can achieve this themselves, but the maths to do so is probably beyond most users (certainly is me).
I'd like to have an transformer to update data (e.g. ESRI File Geodatabase) for an ArcGIS Server Service. So the transformer should manage to stop the service, then update the data and last to start the service again...
To be able to run the workspace from a compiled executable. A valid FME Desktop installation would be required.
For Workspace Runner, it would be nice if when you right click on the transformer, you can "Open workspace in new FME instance".Similar to the "Open destination folder" business.
Provide an Admin user an interface to create a custom SHARED RESOURCE FOLDER that is parallel to the default Data folder (ex. not under the default Data folder).The Admin user can then create subfolders in the custom SHARED RESOURCE FOLDER and have control over each subfolder's access by roles/users.Support Instance Reference ID: C108149
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.
