Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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.
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.
***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.
When inspecting features that have filtered user attributes, only show the attributes selected in the reader/in the workflow in the Feature Information Window. The Table View does this currently - could it be implemented for the Feature Information view as well?
Hello all,Since the revamped date/time implementations in FME, my use of small python-snippets has been reduced dramatically. No more 'import datetime' to do some simple operation.Now the bulk of my python-use involves the os.path library, like splitting, joining or testing for existence.There are a couple of transformers who have path-functionality, but I often need it in text-editor like situations. e.g. building the output-file-name of a writer from parts of the input parameters. Splitting and concatenating using 'text-methods' is not platform-agnostic due to the path-separator. So I put in some python-scripted-parameter.So please, give the os.path methods the same treatment as the datetime library got some years ago.Martin
It would be great to have FME Cloud hosted in France (Paris Region)
See https://knowledge.safe.com/questions/74063/not-able-to-install-fme-desktop-on-fedora-28.html
So we have the good old writer with that nice feedback if all attributes are connected. But yes it's a dead end an I'm not using it that much anymore.Then we have for some year the FeatureWriter with the ability to keep flowing. It's great and I can not do without it anymore.Shoulden't we combine the strengths of both solutions and make an enhanced FeatureWriter?
Since the Inspector supports changing the drawing style of geometry it would be nice to have the FeatureColorSetter have opacity and width parameters.
We can list any files from folders in Google Drive and add useful attributes like _file_last_modified or _sharable_link. But we don't read and list the actual Google items like sheets, docs, presentations etc.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.