Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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
I would like to see the option to completely remove an account from the knowledge center. I (accidentily) have three accounts and only want to keep one. But the one I want to keep should get the mail account from one of the two accounts that should be removed.
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?
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
***Note from Migration:*** Original Title was: Could the tweeter transformer include the ability to tag an image with up to 10 people
Hi,It would be nice to have in FME Desktop Options - Web Connections ability to duplicate web connections. For Database connections, duplication is possible via Context menu.Sometimes you have number of same users on DEV, STG and PROD servers, and duplication would help greatly.Thanks,
Probably no one is going to vote for this, but I need the user to be able to select only the deepest nested list in a published parameter. For example, consider these list attributes:_list{0}.sublist{0}_list{0}.sublist{0}.attribute1_list{0}.sublist{0}.attribute2_list{0}.sublist{1}_list{0}.sublist{1}.attribute1_list{0}.sublist{1}.attribute2_list{1}.sublist{0}_list{1}.sublist{0}.attribute1_list{1}.sublist{0}.attribute2_list{1}.sublist{1}_list{1}.sublist{1}.attribute1_list{1}.sublist{1}.attribute2Currently, in FME, a user can only select the whole nested list above (e.g. _list{}.sublist{}) or a single item in the list by specifying all list keys (e.g. _list{1}.sublist{0}.attribute1).What I would like, is to return a specific set of "children" as a list, e.g. _list{1}.sublist{} (notice the 1!!). When I'd call feature.getAttribute('_list{1}.sublist{}') in a PythonCaller, it will fetch the following list attributes:_list{1}.sublist{0}_list{1}.sublist{1}Those are the "root children" of the second "parent".Specifying _list{0}.sublist{}.attribute1 will fetch:_list{0}.sublist{0}.attribute1_list{0}.sublist{1}.attribute1Those are "named children" of the first "parent".I already have 2 situations (the ListKeyValuePairExtractor and the ListAppender I'm currently working on) for which a new/modified GUI type for a published parameter would be very helpful.
So you need not use a cloner-transformer or search in the logfile to get the exaxt number of Features entering a transformer in the workbench
***Note from Migration:*** Original Title was: Create a breakpoint that saves all of the data up until that point, so when you run the workbench again it will continue from that point instead of starting over from the beginning.
When using the Quick Translator for running multiple workspaces it is hard so see wich workspace is open.I think it would help if a dialogs appears that shows the workspace name and/or workspace description.
When working with workspaces with large numbers of embedded custom transformers it can become difficult to navigate between them. The tabs at the top of the screen become too small to read the transformer names and there is no easy way to go back and forth between views. A web browser style "back" button would be very handy, for example, if navigating in to edit a custom transformer that is embedded in another transformer, then needing to go back to where you came from.
When creating a custom transformer, and editing it in the canvas, it would be nice to right-click on the output port to add an output object (like you would to add an inspector/logger) . Currently the only way to do so is Transformers>Insert Transformer Output, or right click on the canvas.Maybe a hot key as well?
Hi,MS/SQL is quite picky about geometry validation, and as such, a prior pass by a GeometryValidator seems to be a sensible choice at all times. Especially if one has 20+ feature connections in a "generated" workspace.How about making this an easy option on the writer itself, turning validation on/off ?This might even be a beneficial feature on all spatial database writers, maybe on all spatial writers ?CheersLars
A transformer to create word clouds based on attribute names and/or values would be pretty coolA FOSS Python library exists here
The RasterBandInterpretationCoercer allows only for hardcoded choice or user parameter for all of its parameters like Destination Interpretation Type, and Conversion Options.It would be nice if these value could be set by an attribute on the Raster. The Conversion options could also be simplified to Convert from Color, Convert from Numeric, Convert from Float to Integer, as the "to" interpretation is redundant when supplying the Destination Interpretation Type.Any features with invalid combinations (like palettes restricted to UINT) could be output the Rejected port.
https://www.actian.com/data-management/ingres-sql-rdbms/ The fastest Hybrid RDBMS on the market with Geospatial capabilities. Previous versions of Actian Ingres have worked with FME so it would be great to see this latest version certified especially since they have improved Geospatial performance.
I recognized that the XMLXQueryUpdater can be used to update not only an XML document but also the schema of the input feature.Example from Extract attributes from XML attribute:Assuming that the source XML is:<SHD> <feature datadefinitie="Sleutels" code="SLEUTELS"> <attribuut naam="gisobjectnummeer">105963</attribuut> </feature> <feature datadefinitie="IMG" code="SHDV"> <attribuut naam="type">muur</attribuut> <attribuut naam="IMGEO status">bestaand</attribuut> <attribuut naam="In onderzoek">Nee</attribuut> <attribuut naam="relatieveHoogteligging">0</attribuut> <attribuut naam="identificatie">P0027.cdffbb11ae7c4f56a96a</attribuut> <attribuut naam="tijadstipRegistratie">20170626172844000</attribuut> </feature> <feature datadefinitie="GBK_LKI" code="C"></feature> </SHD> An XMLXQueryUpdater with this small XQuery expression extracts pairs of attribute name and value from the source XML and adds the attributes to the input feature.for $a in //attribuut return fme:set-attribute($a/@naam, $a/text()) I think the XMLXQueryUpdater (XQuery expressions) would be a powerful and elegant solution in some scenarios such as the example above. However, depending on the situation, you have to add some other transformers e.g. AttributeExposer, AttributeRemover to clean up the feature.It might be nice if these improvements would be done on the XMLXQueryUpdater.Add some new XQuery functions to process feature attributes. e.g. "fme:remove-attribute" and "fme:remove-list-attribute".Add "Attributes to Expose", "Attributes to Hide", and "Lists to Hide" parameters.Make the "Result Attribute" parameter optional.Rename the output ports (QueryResults -> Output, Invalid -> <Rejected>).
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.
