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,The raw text string that we get back from the FTPCaller at the moment is hard to process. When selecting Download to an Attribute, it would be cool if you could select the response type to JSON or XML instead.
Would make it a lot easier to read in a CSV (that is formatted in a non-data-friendly manner) in 'chunks' by specifying one reader for one part of the CSV, say lines 1-10, and another CSV reader for lines 11-20.
When designing an async download service I would like to send an email - which works fine, but I would also like to display the download link on the webpage if the user sticks around long enough. Currently thats not possible with async calls to the download service.
It would be handy if it was possible to configure a workspace so that it triggered a notification for every n features written or processed.It is currently possible to implement something similar manually using e.g. a ModuloCounter and an FMEServerNotifier, but the workspace gets a bit crowded when there are multiple data streams.
You can run Workspaces from Python using FMEWorkspaceRunner but not apply transformers to feature objects.
Make it possible to "merge feature types" when reading Excel-files
***Note from Migration:*** Original Title was: Add Function to Populate TestCondition in TesterFilter with Unique Values of Selected Attribute Add Function to Populate TestCondition in TesterFilter with Unique Values of Selected Attribute
I'm trying to create a workspace that fetches (among other data) all addresses as a CSV from a web portal. I need to do this with the FeatureReader and a generated URL for "Dataset".It seems that FME is trying to download the whole dataset (with 3+ million records/lines) when I'm setting up the workspace.It would be beneficial to have FME _not_ read a huge web based dataset when setting up the workspace, i.e. in design mode. In any case, it has no practical application, since I do have to manually type in the CSV field names even though they're given as line #1 in the dataset (and I did check the "Field names follow Header" in parameters).E.g. by abstaining to read any dataset that starts with "http://", or at least just read a suitable small fraction.Cheers
At the moment the Apply to functionality is bit confusing. E.g. if I would change Table Handling for all other Feature Types, I have to click Apply to -> then go to Parameters to change -> then choose the parameter. Usually it's just one parameter that I want to change quickly for all other feature types of one Writer.My suggestion: Go to the drop down menu of the parameter -> Choose Apply to all feature types
DEBUG mode for workspaces called by WorkspaceRunners. For linked worksheets I would like to have the option (debug mode if you will) for the caller to open multiple copies of FME (if not already open for that target worksheet) so that you can see what is going on, instead of running it like a command line. There is nothing more frustrating than debugging a target worksheet when having to manually populate the published parameters so you can figure out what went wrong.
When running WorkspaceRunner,Cannot display the running status of the workspace called in real time.If can display the canves of WorkspaceRunner called on the run time, And like the usual workspace,Display the number of Feature that has been processed And real-time processing log. Then it will be more convenient to debug, And better grasp the running situation.Of course, It is not necessary to display the working space at any time.So can add an option in the WorkspaceRunner parameter, such as the "show canves", only when this option is selected to show the canves.
***Note from Migration:*** Original Title was: Provide the ability to expose child workspace information (reader/writer names with record counts, etc) when running in a parent workspace with workspacerunner.
Would be great if all WRITERS / Featurewriters (files) would have a "Cache" option. Ie the workspace would do a "speedtest" towards all related folders before a workspace runs:For instance:- C: 100 MB/sec R - 50 MB/sec write- D: 10 MB/sec R - 5 MB/sec write- J: 1 MB/sec R - 1MB/sec writeSo when writing to J: FME would instead write to FME TEMP and then copy the files to J: after the process because it is slow to work against a network drive, when "Cache" enabled on writer.
An option to remove the GDAL intermediate processing done by the JPEG reader if the translation is only for reading the exif metadata to extract points from the georeferenced pictures.
At the moment if you have a published parameter in Main workspace, you can't access it straight from an embedded custom transformer. You have to create a new published parameter in the custom transformer, and link the parameter in main view to the custom transformer's parameter. It would be nice to have Workspace Parameters or similar in the User Parameters section of the custom transformer's navigator.Especially with embedded transformers I mostly clean up my workspace, but if I need to use 10 parameters of the main workspace inside the custom transformer, it's a hassle to create all the parameters again in the custom transformer.
Long time annoyance:Why do Sorters not indicate red / broken when the defined sort is no longer going to work as requested?During stages of design, I have to proactively seek out Sorters and look “inside” the Sorter to see that the atts it was sorting on have not changed. Some sort operations are quite critical to the overall job (e.g. sort before duplicate remover) - if it is not working (has red inside), it needs to tell us on the outside of the transformer (and prior to run, like other transformers).All transformers should notify when something is "off". Are there any others with this behavior?
Have you ever been creating a custom transformer -- thinking you are finally complete -- and then go through the process of uploading to FME Hub, but seconds later realize you have made one spelling mistake in the documentation?Even though FME Hub has opened up and refined the workflow for uploading content, wouldn't it be nice to be able to push those small edits directly from FME Workbench, without switching applications?As an enhancement this is likely quite a few kilometres down the road, but let us know what you think!
Sometimes I copy writers, do other work, get distracted and lose track as to whether or not my writers have all the same atts. Often requires me to throw away, re-copy or manually verify. Would be an easy addition to add a count of attributes and this would add a little peace of mind at a glance.
Today, we often add or rename atts 30 revs into fmw design -- we then have to "know" all 19 of those and go visit the writer and cognitively hit the plus, find each of the 19 in the pile of 100 to make sure they make their way into our schema. I currently keep track of these elsewhere and then go visit the writer.Automatic isn't a good option for this, as it adds things we don't want (intermediate substrings and calcs, source purposefully unused, atts accidentally not removed, etc.). Automatic also jumbles the order again -- which we may have just spent 15 minutes ordering.Similar to symbolizing by category in ArcMap, with the underlying data changing later.......you can hit Add and it will only show you what has fallen out of symbology. I would prefer there was an add atts button in writers that would show me only the unused atts. We could pick from those and add only what we want to the end of the list -- then move them around from there.
I find lists hard to understand and work with, they are a ragged edge sparsely populated table you carry around, and are hard to query and store. JSON on the other hand is well behaved and amenable to querying, Python handling and storage. JSON can do everything lists can, so lets get rid of lists. In the short term a transformer that casts lists to JSON would work - with a way to inspect JSON values as pretty JSON!
Add the option to calculate overlap in SpatialRelator. Area overlap is something I greatly desire!, but line overlap will also be nice. I know it is possible to implement this using the AreaOnAreaOverlayer but IDing and assembling all the pieces correctly add a lot of complexity to workspaces and an enormous amount of computational overhead. I know this will add a lot of computational overhead to the SpatialRelator, and it should therefore be left as an option.
To keep it sane here, it might be a good idea if moderators on the FME Knowledge Center could merge ideas together? Would be nice if the votes are also merged then (in such a way that duplicate users only count once of course), so that Safe gets a good idea of how popular an idea really is.I'm seeing more and more duplicate posts here because people are either too lazy to search if something exists already or they are using the wrong search terms so nothing shows up.Take these 2 ideas for instance:https://knowledge.safe.com/idea/25230/expose-attributes-in-the-attributemanager.htmlhttps://knowledge.safe.com/idea/28164/add-exposer-to-attributemanager.html For questions, it might be nice if related/duplicate questions could be linked somehow?
When you use Feature Inspector or FME Data Inspector to inspect features.Usually in addition to the usual visible attributes, there are a lot of FME additional attributes.Especially format like DWG format data,It has very many attributes.But a lot of times the user just wants to see the specific attributes.Because there are a lot of attributes, to find the attributes you want to view, you must spend some time on the mouse scrolling and lookup attributes.I suggest adding a filter function.that can be quickly found attributes through to input keyword.
Extract values from a raster using an area as input. E.g. max, min values.
SIS product seems to bundle FME Reader/Writer plugin for SIS formats, but SIS product installation is needed to use the plugin. Hope FME will support SIS formats (especially reading) without needing SIS installation.
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.
