Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
When you find an "item on hub.safe.com - you should be able to discuss this in the knowledge center in its own folder. For instance autocreate /WebConnections/Github as a "product"/"folder" on knowledgebase to dicuss enhancements that can be done on that particular FME hub item. Also it would be nice to pubish everything on FME Hub on github. So anyone with a github-account can upload a new version of that transformer. The goal here is to get many users to contribute to improve errors and features for Custom Transformers / Webconnections etc. https://hub.safe.com/web_connections/github
Hi,The "Choice with Alias" user parameter is great because we are able to import coordinate systems, readers and writers.Why not the ability to import "Character Encoding" items too ?It would be great ie for a shapefile writer. We could import easily a selection of character encoding in a user parameter.Mathieu.
Currently the ESRI Reprojector does not support composite transformations like ArcMap does. It would be great to see FME could adopt this functionality. A common reprojection from NAD27 to WGS84 typically requires a composite transformation and the way to do this with FME at present (FME 2017.1) is to use two ESRIReprojectors. For those used to the ESRI workflows this can be a big trip up.
It might be nice if FME had improved database transaction support.Here are some ideas:Continue with the load if a record fails to insert and is rejected?Ensure that child-parent records are written inside the same transaction.Share a transaction between the FeatureWriter and the SQLExecutor.In the FeatureWriter, output features (via rejected port) that failed to commit, but also continue to write the remaining data.Control when transactions are shared between SQLExecutors and writers.I wonder what others think is important?
If I have shared FME folders, FME_TEMP set, use a TempPathnameCreator and so on those file name options are hard to apply to the File Name parameter. How about adding those options to the file name picker?
It might be good for FME to support reading and/or writing Redis.I wonder how others might work with Redis and FME?Would reading or writing be more interesting?
It would be nice to have a publication service for REST services (like MapServices & FeatureServices). This would be useful for those organizations who want to set up something to run to either do a complex field calculation or send an email notification automatically when a new record is added to the REST service.
Add Support for reading AutoCad Extended Data Documentation attributes such as "Notes", "Hyperlink", and "Reference Documents".
I am playing with a series chained of DatabaseJoiners which receive a recordset of parcels and i would like to join the 'failed unjoined' again to the same table using a Substring of the Key.e.g. where APN = PARCEL_NUMBER fails tryAPN_sub = @Substring(@Value(PARCEL_NUMBER),0,10)The text editor on the TableField side of the join does not allow normal attribute manipulation FMEness to happen. Can this B.Table.Key side be extended to do @Value field trickery? I would very much like to only read the records i want from the database, this will require more than normal field Selections.
Sometimes a format or transformer that I use gets updated. Currently, I can’t figure out what exactly changed, why it changed, or whether the change is relevant to me. It would be nice when a component has a changed, to be able to discover the details of the change.
I would like to see the option to automatically explode the 'list' that is created when adding suppliers to requestors. Right now I create a _list variable and then need to use the ListExploder transformer. This works but the option box to automatically explode my list into additional merged records would be nice. The use case is that I want to create a union or intersection table between two tables - for example. I have two documents, that 'document' four features. Each feature needs to be 'merged' with each document. For a total of eight records. FeatureMerger by itself returns four. Adding the list captures the second related document for the feature and then I have to explode the list to get my 'eight' records. It works but it could be simpler.
Sometimes I go to the official documentation and look for help. It's pretty good in general, but it's not always got great examples, few tips and tricks and never known issues, etc. To find that info, I have to search and wade through Q&A and articles in the knowledge center, which is really hit or miss. I want this stuff to be right there when I click the help link on a transformer in FME or find the doc in general. Let me comment on the doc and add examples. Let me read examples and rich user-contributed information in the doc. Don't make me search for this and have to parse through it in a completely separate system.
***Note from Migration:*** Original Title was: Save As menu to down/upgrade current workspace compatible with a targeted version of FME This could make FME consultants' life much easier, as their clients may not be able to keep up with the latest versions. This is especially the case with FME servers, the upgrade of which often involves IT departments with their own schedule and procedures to follow.
An option in the data inspector to control if a feature is selectable as well as visible in the map window.
I posted a request some years ago about the old raster format CALS. I got the respons that if we write a GDAL driver to it Safe might add it in FME. As times moves on we never find the time to write the CALS driver. Currently we use http://www.imagemagick.org/ and run from FME with SystemCaller. But it would be very nice to both read and write CALS. Any chances for this?More about CALS: http://en.wikipedia.org/wiki/CALS_Raster_file_format
***Note from Migration:*** Original Title was: Could the tweeter transformer include the ability to tag an image with up to 10 people
it will be very helpful if we add sql creator to fme inspector. In my case i am reading the source data from multiple oracle spatial tables . and input query is very big. to check the source data(if there is any problem) i have to write to shape file then read it in inspector. instead i can give this to inspector just to check source. i know this can be done inside workbench... but still it is good if we include this in fme inspector or viewer
Anyone else miss it when they can't just touch the TouchID button when install FME on the Mac? I'm seeing a lot of Mac Apps embrace the TouchID. Will FME join those apps?
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.