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.
It seems as though the FeatureTypeFilter randomly places features when using the Update option. It would be nice to have this order the features alphabetically or numerically.
When viewing data in Inspector and having both the table and 3D view visible, behavior is such that when a feature is selected in the table, it is also selected in the 3D view. However the reverse is not true and I think it would be great if it did. With the 2D view, selection behavior seems to be bi-directional with the table.As part of this, I would also like to see an "isolate in view" option for the 2D & 3D views so one can inspect and orbit around just the selected feature. Being able to make the rest of the features transparent would also be nice and would provide context.
In the FME Data Inspector, Add datasets to the two views, then they are independent, but many times we may want to view the dataset in view2 and the dataset in view1 overlap. Currently, you can only add a new data set again.If the dataset is a file that is saved on disk, it may be cumbersome, but if the dataset is from an inspector, you can only connect them to the same Inspector and run the workspace again.Added feature caching mode in FME 2018. This mode is very helpful for debugging work space, but each view can only display the result of one output port. In many cases, the results of different output ports need to be superimposed and viewed.If you can allow the user to use a drag or Ctrl+C to copy or move the dataset directly in different views, it will be very helpful to inspect the data.
It would allow the user to insert a Junction anywhere more quickly.
I love using feature caching in FME whenever I can. I find it's the easiest way for me to test whether my transformation is working correctly. Sometimes I am testing a workspace to see if it will filter objects the way I expect. So I might make changes to a database or a file after I have features cached. If I run the workspace using caching, it won't load new features, because they are cached. Even if I say "Run just this", I get an updated feature in the inspector on that reader, but not on the next transformer. So the rest of my cached workspace runs the same as before even though there's a different feature up the pipe. I know I can get what I'm asking for just by renaming a transformer, if I'm using a SQLReader or FeatureReader. But I'd like to have an option for any type of reader where I can do something like right click and clear cached values. That way on any reader, I can update a feature without updating the rest of the workspace. I don't know of a way to do this now, but I'm definitely not an expert.
The Reprojector Transformer has been around for a while now but the CsmapReprojector clearly has the same capabilities with the added capabilities of transformation and vertical handling. There doesn't appear to me to be much point in retaining both, so perhaps it's time to alias the name of one in favour of the other for the sake of simplicity.
Hi, would it be possible to make the clipper coordinate system aware? Like data inspection which displays data in different coordinate systems on the right position with respect to the background. Currently, the clipper just treads geometries as coordinate lists and if two feature have different coordinate systemen (for example the first has a projected cs and the second a geocentric cs) the results are unpredictable, since projected cs usually have large coordinate values and geocentric cs usually have angular values in general smaller than 360 degrees. There is allready an idea to have the Clipper flag a message if coordinate systems are different, however, not every one studies log files thoroughly. See Clipper: Add a note in the log when coordinate systems are different
In a serverapp you can choose to add a map with Geometry Picker. You can also change map within the app.I would be nice to be able to set a default map to help the user.
Currently these parameters in the RasterDEMGenerator cannot be specified through feature attributes.Output DEM X SpacingOutput DEM Y SpacingOutput DEM Raster Nodata ValueThere could be a case where those attributes should be set dynamically based on the source dataset. In fact, recently I had to implement this workflow.Read a 1-band numeric raster with Nodata cells. The properties including cell spacing and Nodata value could be vary for each input.RasterPropertyExtractor and RasterBandPropertyExtractor: Extract cell spacing and Nodata value.PointCloudCombiner: Convert the ratser to a pointcloud.RasterDEMGenerator: Fill the Nodata cells and re-create a raster with the same cell spacing and Nodata as the source raster.Currently cell spacing and Nodata value cannot be specify via feature attributes, so you will have to create two workspaces to implement the workflow above. The first workspace reads a source raster and performs the step 3 and 4. The second workspace reads the source raster, extracts properties and then calls the first workspace with WorkspaceRunner/FMESurverJobSubmitter, passing the cell spacing and Nodata value which are extracted from the source raster.It's possible but not elegant. Especially I don't like the latter workspace should have both WorkspaceRunner and FMEServerJobSubmitter if you want to use the workflow with either FME Desktop or FME Server.It would be nice if you could set feature attributes to those parameters in the RasterDEMGenefator.Alternatively it would also be nice if the NumericRasterizer would have an option to perform fill operation, equivalent to Elevation Void Fill function.Comparison: Similar parameters in the NumericRasterizer can be set via feature attributes.
This came up during a training course today.When the list of readers and writers in the navigator is rather long it's not very easy to see where the readers end and the writers start. An option to add some visual separation between them would be nice.I've simulated it here by adding a NULL writer and blanking out its name (which, I guess, could be a useful workaround)
It will be nice if I can open a workspace and display feature counts on connections from the last run of that workspace. Is it possible to store these numbers somewhere and load it into the workspace without running it again?
It would be great to be able to right click on a reader and update its features. I know this can be done through the Readers menu but a right click option would make this easier for workspaces with a lot of similar readers.
At the moment it is not possible to snap vertices on connections, and bookmarks, to the grid. On connections this prevents me from making perfectly horizontal/vertical lines, which is a bit annoying.The location of bookmarks can be snapped, but on a resize it does not snap. This makes it hard to create a visually pleasing bookmark layout.My proposal would be to add full 'snap to grid' functionality to these two workspace items.
As a user of FMEI would like to have the option for a non-unique transformer name visible together with the transformer typeso I can use transformer naming to tidy up and clarify the workspace without losing information on what kind of transformer it is.From a developer background, function naming is important. A clear and concise name is generally all that's required for function documentation, and it's something I'd love to see in FME.Currently:Adding multiple copies of a Transformer gives it numbered names like 'AttributeCreator_17' which is ugly.You can name a transformer, but the name has to be unique, and you lose some information on the type of transformer used.Summary Annotation could be used, but that gives more detail than necessary and isn't very pretty.
Feature Caching is a great addition to FME that gives the user a much better ability to inspect what happens inside of a workspace. One addition that I would like to see to feature caching is the ability to cache multiple runs/iterations from a transformer. This would be of a help for iterative workflows when creating a workspace. For instance, I'm working with OCR-reading and rasterization techniques at the moment trying to find the parameters that gives the best OCR-reading result from tesseract. A task that is far from clear cut and that relies heavily on trial and error. Having the ability to cache multiple runs would help this iterative workflow a lot in comparing which changes give the best result. Ideally multiple-run caching would be set on a transformer level, as to not exponentially increase the amount of memory that is used. With a parameter that specifies the amount of runs to cache.
While editing a complex workspace, sometimes happens to disconnect unintentionally a connection with a slightly rough mouse operation. It would be nice if the user can switch lock (uneditable) / unlock (editable) a connection, in order to prevent unintentional disconnection of important connections.
In the installation wizard of FME Flow(2023.0, and still in 2023.2.1), you are prompted the default database username “fmeflow”, but in the installation script’s for the SQL server database, the default username is “fmeserver”. I suggest there would be nice with an alignment here.
There are several ideas around improving the functionality available in Annotations, but why not go the whole hog and (as per Leaflet popups for example) have each annotation being its own HTML page - capable of displaying images, tables, even video if required.As a slightly lesser alternative, annotations could be created using Markdown.
Hello all,Today again, I dropped a filter in an automation I was building, and immediately missed the ability to filter on a regular expression. I actually never have to search for an exact case sensitive string, but always need some flexibility.I searched the Idea's section to vote up any idea posted already for this, but did not find any. So here it is... Add regular expressions to the automations filter..ps. If I recall correctly, Don promised something like that on one of the first presentations of the whole Automations concept.
In large Workbenches it is sometimes necessary to edit the same parameter on multiple Reader/Writer/Transformer to change it to the same value e.g.: I have 36 SQL Server Spatial Writers in one Workbench and want to change from "Drop and Create" to "Truncate" mode. Now I have to click trough all of them and apply the change.It would be nice to mark all Reader/Writer/Transformer that I want to change, click "Properties" and apply the change only once and all marked Reader/Writer/Transformer are changed.
Hi together, I was looking for a way to create a custom header/footer template using our corporate colors/icons/favicon for FME Server based workspace apps. The idea is that whenever any of our FME admins wants to create a new workspace app on the server, he/she would work with a customized header/footer from the get go - without reapplying the color hex to the header, inserting some text to the footer etc. Such a functionality would save time and is less error prone.
It would be great to show feature counts on the output ports, instead of on the connection lines. A couple of reasons:Feature counts will still be available when nothing is connected to the output portWhen connection lines overlap/intersect, the numbers won't overlap each other, making it hard to read. (When two numbers overlap, it could look like a different number)
***Note from Migration:*** Original Title was: Database Connections - make connection parameters available as published parameters Make it possible to make the connection parameters such as host or database name available as published parameters so that they can be used in other readers, writers, or transformers, such as SystemCaller.More details in this Forum discussion: Database connections retrieve parameters programmatically
Hi,Wouldn't it be great to have a parameter to define the initial window size of the geometry picker parameter?Yes you can adjust the size of the window once it is open, but it would be great to be able to define it yourself.Cheers,Itay
A possible way to improve working with FME Workspaces and informing the end-users about changes.Documenting the workspaces with Bookmarks and Annotations is the first step in creating a well documented workspace. But what if you want a better way to work, and save all the minor changes you do every day? And find back to a previous version? Also if you share the same workspace with more colleagues either through Github or through a shared drive? Can we benefit more by working a bit more similar by looking to our coders even if we are non-code people? YES!We also want to inform all the end users of our workspaces / FME Server workspaces / Gallery apps of any changes we have made with the workspace. NOT with a separate word-document we have prepared and they have to look at. NOT by sending an e-mail and say: Hey, we have added a new format. But within the actual workspace itself.A suggestion to Safe Software to consider would be like this?1. Start FME Workbench2. Select Workspace you want to work with3. Get pop-up:a. What are you doing today? Enter short description: For instance (Check errors when writing to Shape)4. Open workbench and you have a new textfield floating on the top left cornver of the canvas5. When you have “found and fixed” what you should (should only take 5min – 1 hour is) hit SAVE button and a new pop-up. Prefilled with the text already enteretd:6. This will now be saved in the workspace “History- which few people use?”. And you now have a good track history of the changes. 7. When published on FME Server the last change (and older) can be showcased on the Run Workspace:And also on the FME Server Apps side.
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.
