Open ideas have been reviewed by our Product Management and are open for commenting and voting.
If there is an error in python code(python caller) fme shoex error_line_number + 1I mean if there is an error in line 42 , fme log window tells us error in Line 43. So what I am doing is ... I am minus 1 , and and looking at Line number 42 and fixing the code.it is better to show exact line number in fme log window
During a FME training class, a trainee suggested the option to sort the Data Inspector table window in a way that the selected features would appear at the top of the list.This seems to be possible and useful in the ArcGis Table View.
It would be great to be able to expose attributes at runtime for dynamic workspaces.
https://community.tibco.com/wiki/tibco-spotfire-sbdf-libraryThe TIBCO Spotfire® SBDF Library is a programming library for reading and writing files in the Spotfire Binary Data File (SBDF) format. The library can be used to add support for this format to an application, enabling it to natively create and consume data in a way optimized for analysis in Spotfire. The library is available for both .NET and Java applications.Note: If you are writing an Spotfire extension you should not use this DLL. Instead, use the DLL provided by the Spotfire SDK.
Include HERE Maps Flexible Polyline as format much like the Encoded Polyline is included in the Geometry Encoding.Documentation can be found here: https://github.com/heremaps/flexible-polyline Unfortunately HERE Maps uses another type of encoded polyline as a variation from the standard.This would be great to make API requests and return their version of the polyline, and feed directly into Geometry Replacer to create the Geometry.
Today we can only make use of fme.macroValues[]. This is just a list of ALL parameters in the entire workspace. This no longer works at the moment you start creating custom transformers because the parameter name get extended with the name of the custom transformers it's embedded and you can retrieve those. The parameter content is also not escaped or evaluated when linked to an attribute.A method maybe called fme.getParameter(<parameter name>) that has the same behaviour as the ParameterFetcher would do wonders. Today we need to transform parameters into attributes, pass them through the PythonCaller and remove them again after the PythonCaller. Many additional steps that could be avoided and reduce performance and potential errors.
When working with git and FME together it's pretty difficult to perform code review and to merge changes, at least if the same .fmw file is touched.What would really help is the ability to split up an .fmw into a number of files so that changes and merge conflicts can (more) easily be resolved.For example, one file could be just list the transformers and parameters set, one file to handle the content of comments and bookmarks etc, and one project file which has the positions and workspace parameters etc.If a developer could use a structure like this changes would be much clearer and it would be much easier to compare git-branches.Opening the project file would be the same as opening up a workspace, the files would be compiled together.There would also need to be a way to compile the files into a normal .fmw file so you could include this step in a build pipeline.
Add nextCloud / ownCloud in "select file from web" and add a nextCloudConnector transformer.
If a workspace is set to "ignore failed readers" I notice that there is still an ERROR logged, however, I feel like this should be logged as a warning instead.
To make data inspecting easier sometimes will help to have some of the hidden attributes available in the Table View. Exposing attributes inside the FME Workbench is great but it will be also good to have the same option inside FME Data Inspector; to avoid reprocessing. That is very useful when working with a large dataset with many attributes. I've experienced a need for this while working with BIM/IFC files. Attributes inside Table View can be used for data filtering and that helps a lot while inspecting some dataset. Expose attribute/s functionality inside FME Data inspector can be, for example, implemented as an context menu that opens on the right click while selecting one or more hidden attributes from the Feature Information Window.
In order to switch between connectors styles in the workbench we can just press "Shift+Ctrl+c" in the keyboard. Would it be possible to add "Shift+Ctrl+Mouse Wheel" ?
Reading data from the Esri Mobile Geodatabase will always prefix Tables/FeatureClasses with "main."According to Esri this is the logical database name. It seems this is mainly caused by Esri logics and NOT by SQLite.It would be helpful if the reader had an option to remove this. Similar to what Oracle reader (and maybe others) also allows to do.
Hi, I do a lot of image QA on ECW files and have automated much of my workflow via FME. Two tasks are still manual; checking ECW version number and the compression ratio (actual and target) of the image. The RasterPropertyExtractor can see the attributes, but does not always extract these values despite them being available via other software packages for all ECW files. I'd like to see the RasterPropertyExtractor being updated so that it is able to extract these values reliably.Thanks
As an editor of an FME-Workbench I would like to pan the workbench while holding the right mouse button for faster moving around without switching the funtion between select and move.
I notice that there are transformers like a JSONExtractor transformer that can extract attributes from JSON using a JSON Query, and an HTMLExtractor transformer that can extract attributes from HTML using CSS selectors. Why not an XMLExtractor transformer that can extract attributes from XML using Xpath?I know that creating attributes for specific XML elements is already possible using Xpath using the XMLXqueryExtractor, but just seeing anything that even looks the slightest like code can already be a bit scary to some users (and also for some XML that uses explicit namespaces in the XML element names you would need to declare those in the XML, etc. So that also looks a bit scary to users (although probably in a transformer you might need to have the same option to make it work?)So my Idea would be that if you have some XML like this:<?xml version="1.0" encoding="UTF-8"?><root> <student> <id>01</id> <name>Tom</name> <lastname>Price</lastname> <hobbys>football</hobbys> <hobbys>hockey</hobbys> </student> <student> <id>02</id> <name>Nick</name> <lastname>Thameson</lastname> <hobbys>reading</hobbys> <hobbys>gardening</hobbys> <hobbys>painting</hobbys> </student></root>Currently you would be able to create (specific) XML attributes using the XMLXQueryExtractor, like e.g. a list for only the name and the lastname of both students:fme:set-list-attribute("student{}.name", data(//student/name)),fme:set-list-attribute("student{}.lastname", data(//student/lastname))I guess the implementation might look very similar to the HTMLExtractor. Actually, it even seems that in some (or all?) situations you might even be able to change your xPath to CSS selectors, and use the HTMLExtractor for the same job.Target Attribute, CSS Selector, Tag Part/HTML Attributestudent_name, student > name, Valuestudent_lastname, student > lastname, ValueReturn Format: List Attribute
The Directory and File Pathnames reader is useful for getting the files paths as an attribute without reading in the data itself. However it currently only takes a folder as the input parameter.There are situations where the user should be able to pick any combination of files/folders through the Select Multiple Folders/Files parameter interface and the result is one feature per file (not selection) with an attribute containing the full path to the file.It currently takes 8 transformers to achieve this result.
It would be nice is there was a ConnectedComponentCalculator that would work similar to the NetworkTopologyCalculator except with Area features that are intersecting.The features would be output with an attribute _component_id that would be shared by all the features that belong to the same graph.Bonus would be an optional attribute that contains the number of features that are part of the graph.
Sometimes I come across a source dataset within nested zip file, like this: "root.zip/sub.zip/data.shp".Looks like FME doesn't support reading features from such a dataset currently. It would be convenient if FME could unzip nested zip files recursively and read features from the archived dataset.
What is the result list, _relative_position, sorted on?I would like to see it being sorted on distance to used base feature. Any thoughts?
Could the attribute accumulation option, as it is added with many Spatial comparison transformer, be added to the LeftRigthSpatialCalculator?Currently only an attribute containing LEFT or RIGHT is added in an attribute, but I would also like to use the transformers as a NeighborFinder. If the 'Attribute accumulation' is added, it saves a transformer in the workspace.
It would be nice to be able to connect to OneDrive for Business via a Web Service connection. Currently it is only possible to connect to a regular OneDrive account.
Hello,I adore working in dark mode on all software I use (ADOBE suite, Visual Studio, Office, etc)I use FME very often and I was really excited once I heard about the new dark mode. However, after testing it in the beta version, it seems that it still need some more ameliorations to become perfect.1.The toolbar needs a new redesigned set of icons. A new entirely grey set, designed only for the dark mode will be really beautifull ;2.The blue color of transformers doesn't really go with the dark theme. It would be nice to allow the user to change it to some shade of grey maybe ;3.It will be appreciated to allow the user to make the toolbar with a darker shade of grey than the workbench transformers space ;4. It will also be very appreciated to change the default title bar included with windows to some new one redesigned especially for FME5. if it has to be dark, it has to be dark for the whole interface :6. This selection effect isn't reealy esthetic. Better can be madePlease find below some pictures which may help in ameliorating the dark mode : Best regards.
Will FME Desktop ever be available for Arch-based Linux distributions? Would love to eventually see this happen. Although, I don't know how difficult it would be to release for rolling release distribution.
***Note from Migration:*** Original Title was: Run FME Job using active directory account of user (not windows service logOn user) I was chatting with a customer and they said they'd love to be able to let their users run scripts that access data and directories they are already entitled to using the Active Directory account. Currently, the jobs all run as the single account specified as the Log On user for the FME Engine windows service). That account needs permission to access ANY data that might be processed by ANY job on FME Server.I'd prefer if the jobs ran as the user that creates them.
As an Autodesk Dynamo user, FME is a natural fit. There are features that FME could benefit from, and vice versa. I find the transformer Align/Spread feature lacking. It is too easy to turn your slightly messy workspace into a knot of nodes. Dynamo has a feature which automatically aligns the nodes(transformers) that is superior. Right-click on a Group (Bookmark), select Clean up Node Layout, and it auto-arranges:It isn't perfect, but way easier than what is offered currently.
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.
