Shape the future of FME with your ideas
New and Open ideas are awaiting review or have been reviewed by our Product Management team, and are open for commenting and voting.
***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.
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.
Aggregator supports sum and average, I'm dealing with dates and want to know earliest and latest in the aggregate feature, it is easy enough to use ListRangeExtractor after aggregation but while we're there....
Add an option to the TimeStamper to create a global time stamp, similar as the counter creates a global count. Also add an option to create the timestamp attribute only once for the time of the first or last feature passing the transformer. This is relevant, for example, when fanning out on a filename with a timestamp where different timestamps on the filename result in separate files.
Instead of use many engines to generate a dashboard, you can use the notification stream in FME Server. Example: for each job started by FME Server, you send an notification to dashboard page (realtime ws)
Add a dynamic header based on attributes.
I think the option to save favourite workspaces in place or addition to the recently used option, like in web browsers. So workspaces that are important or use regularly save in your favourites for easy access in case they get bumped out of the recently used.
HiEIVA is a industry leading softwares for bathymetry pipeline data used by oil and gas companies world wide. The EIVA NModel application uses a common db (spatialite) which can be utilized in FME. But these tables also contain BLOB data in binary forms. It would be most valuable to have a FME reader to extract the processed depth data to streamline data exports etc and make validations.Best regardsAndre Reinlert @ mmt
When I use the VectorCreator transformer in mode Replace Point At Index, I would like to specify a value by selecting the attribute name from the pull-down list or by other advanced functions (Advanced editor, arithmetic editor, etc.). Here is the option availables :Here is what I would like to be able to do :
This is small potatoes, I know, but would be a simple and common relief.As the workspace name is shown as the first text on the window title, this is an important feature when working with multiple workspaces.And here's the text "None -> None (untitled)" or similar auto-generated gibberish not very helpful.Cheers
I see there is a new formats webpage - when clicking one format it would be great to easily see which types of geometry was supproted - the Quick Facts about each format on each page below the reader/wrriter summary (on for instance http://www.safe.com/integrate/microsoft-sharepoint-list/)
***Note from Migration:*** Original Title was: Add a Warning message whenever the PointOnAreaOverlayer transformer deaggregates MultiPart polygons I recently discovered that the PointonAreaOverlayer deaggregates MultiPart polygons. I often both need the output points and areas for the rest of my model and it is a bit weird that the number of features before the analysis differs from the number of features afterwards. It would be nice to have a Warning message appear in your logfile each time MultiPart polygons are send to the PointOnAreaOverlayer (similar to the message you receive when sending MultiPart polygons to the dissolver transformer). I added a small workspace to clarify this 'deaggregating' behaviour.poa.png
Would like to select multiple connections and right click and Add Breakpoint to these selected connections. Currently have to add to each one separately. Already existing when right click with multiple connections selected is the option to Disable/Enable and Delete.
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.
