Open ideas have been reviewed by our Product Management and are open for commenting and voting.
It would be a real addition if two navigation buttons were added to the DataInspector, being 'GoTo previous extent' and 'GoTo next extent'.Often when I navigate through my geometry in the DataInspector I want to go previous extents. Sometimes because I accidentilly moved my map, other times because I want to compare different features that are not adjecent. I think it is really helpfull when these to buttons are added.
A useful basic feature of GIS apps is the ability to go to the previously viewed extent or the next extent (where applicable). This would save a lot of time (as opposed to viewing the whole extent and re-zooming.
Creator, SQLCreator, PythonCreator, RasterCreator. Why not an HTTPCreator?
It would be great if it would be possible to give views in the data inspector a name. So I could rename view 1 to "other name".The reason for this is when I am testing I have often have multiple views open. Some of these views I want to keep open the whole time I am working on a workbench. When I could rename the view it gives a better overview.
I often use the Data Inspector to test out and demonstrate different scenarios so it would be helpful to have the ability to rename the tabs (views) with something more descriptive than View 1, View 2 etc. It would also be great to be able to save the whole thing as a 'data inspector file' for later reference without having to re-run the whole model.
There are a lot of users that only run FME workspaces. For them it would be nice if you can choose to only install the FME Quick Translator. My suggestion is to add an option to choose which FME components you want to install. In practice this would mean a full install or a light install, leaving out the FME Workbench.I know it is possible to adjust things afterwards, like linking the *.fmw extension to the FME Quick Translator and removing the FME Workbench from the Start-menu. But that takes time and needs to be done after every install and update.
FME is a great tool. Why a customer not interested in spatial data would have to pay for so many spatial formats and tools? Could it be possible to have a specific light product cheaper for non spatial users?
As alternative to FME server for running authored workflows, a license model that provides users with standalone access to FME Quick Translator(not a full install with workbench). As a business we have developed workflows, that could be run by any user in Quick Translator, they do not need to author/edit workflows. The cost of FME server is high to justify this year and the data volumes are too large for cloud. This could be free with x number of licenses of Pro or say $100 per user.
I would do some SQL LIKE statements or REGEX work, but my problem is how to compare a single feature against every value in entire database field.For example. I have 150 address records in my billing dataset. I need to compare that against a master database that has over 100,000 address entries. The problem is that the data is not consistent in either of the sources and normalizing the data is not an option. My billing data may have an address of “150 Main St” and there is a record in the master database that has “Parkview Apartments 150 Main St”. I want to take each of the 100 input values for address and compare that to all 100,000 entries in the master database to generate a list of matched records where the master database “CONTAINS” the value of my input billing address.The only way I could figure out to make every one of my input records compare against each of the 100,000 records in the master database was to build a massive matrix combining each of my address record billing records with each of the records in the master database and then just brute force through the process with a conditional TestFilter..
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.
The ability to change the color of the "Reader/Writer Features" icons. This would be helpful when you have multiple feature with multiple designation and multiple projections etc... The ability to color code so at a glance you know what you are editing. ( example: My destination UTMZ11 .shp features are Blue, destination WGS83 .shp feature are yellow, my destination gdb feature are purple and destination .csv feature are green....)
I wanted to put forward an idea to help to differentiate between readers and writers on the canvas to avoid the need for bookmarks or lots of annotation to describe the data container's sourcedestination. It doesn't need to be as overt as my dodgy Photoshop skills suggest but along these lines:It could also be added to FeatureReadersWriters though that would likely be much harder as it would need to be more dynamic.Anyway, just wondered what people think?
When working with huge amounts of featuretypes it would be nice to give every single reader a certain color. All featuretypes of that reader will be the same color so you can easily see to what reader a featuretype belongs. Probably this would also be nice with writers.
As I started to use a variety of 3D viewers besides FME DataInspector I came across a very useful feature.It is a constrained orbit mode tool which "restricts" orbiting in a way that it always keeps the ground horizontal. That way you avoid tilting your view in ways as if you are doing 3D aerobatics and get lost in the strangest rotations.Especially in dealing with 3D geographic and building data, which is the vast majority in FME context I think, this is what you want to do most of the time.So my suggestion is to add such a "Constrained Orbit Tool" to FME DataInspector.
As an FME user, I want to have the ability to easily and interactively re-order my attributes, test clauses, join on, etc. so that I don't have to waste as much time clicking the item I want re-ordered and the move up/down button.
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.
As there seems to be no way in FME DataInspector to make 3D solids "partly" transparent, like area filling is now, I suggest to add a rendering option for 3D features which allows to see through solids.I have quite hard times to inspect the parts of a solid when I need to always rotate it so that the marked vertex/point is in foreground.It would help greatly if it would be possible to see through the surfaces. One application would be to investigate CityGML datasee also: Knowledge Center Discussion
I like "run with feature caching" a lot and have it default on. However I have a few workspaces that can newer run with feature caching because they just stores to much data (think raster, lists, 3d-models++++) - and from taking a couple of hours withouth caching to never finishing with the caching on its a big difference.Is it possible to make a setting on the each workspace itself - WorkspaceParameters - Translation - Run with feature caching with the options:- As default in FME Desktop- Always off- Always on
***Note from Migration:*** Original Title was: Create documentation that lists all the changes for Readers/Writers/Transformers between different versions of FME? It would be wonderful to have documentation available (outside of the information found in upgrade transformer inside FME Desktop) that lists all differences per transformer/reader/writer.For example, if I'm upgrading from an older release (e.g. 2015) and want to understand what is new for transformers, I cannot find this without loading each workspace in the new build and looking at each transformer in depth. For Readers/Writers this information is harder to find.The 'What's New' is great but it doesn't detail the history past the current release.
When choosing help on a transformer - for instance GeographicBufferer the following page opens: http://docs.safe.com/fme/2018.0/html/FME_Desktop_Documentation/FME_Transformers/Transformers/geographicbufferer.htm Right under the description it should show the changelog for that transformer. Right now you need to have an old transformer - then choose upgrade and then see the changelog to be aware of the changes. There is no easy way to see the changes done to a transformer, or have i missed something?
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 be great to be able to move datasets between two different Data Inspector views just by drag and drop, instead of having to use the add dataset to view dialog
When inspecting a dataset from workbench, add a choice of open data "into View 3".Also, add chioce of merging Views withing the Data Inspector.It would be helpful to view and compare datasets in the same map. Or even compare the 'same' data at different stages of the process.(I know you can do some of this today, by connecting the interesting points to one Inspector each on the canvas, or even add dataset from a temporary ffs-file and find the right featuretype in there, but I find this somewhat anoying.)
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.
