Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
There are numerous implements of the various cluster algorithms within open source libraries including DBSCAN and Kmeans. An FME transformer for clustering would be really useful in trying to map more complex datasets. I know that people have used 3D terrains and distance matrices to do something similar but there doesn't appear to be any out of the box FME solutions and to create clustered areas in FME is quite a challenge. I guess python running scikit-learn would probably be the easiest way? But a transformer would be very useful and would help make FME more of a mapping tool.
This would allow for further geospatial and general data analytics within FME, including types of cluster analysis like Jenkins Natural Breaks or K-means analysis. Currently the best options seem to be scripts (Python, R) or other software (ESRI, QGIS).
Like the SchemaMapper which takes mapping rules from external file, the AttributeValidator could read validation rules from a table.This would also allow validation rules maintenance by non FME people.
It would be great if you could copy and paste a list of attributes for each validation rule rather than a pick list. I know you can copy and paste rules in the new version but it would be nice to be able to copy in lists of attributes from text files.
Hello, Recently i was need AttributeValidator transformer to check 700 attributes. I think it would be a good idea if Safe added an Import button like AttributeValueMapper. Please i need it ! Loïc, Sitdi-france.fr, FMEAddict
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?
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.
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.
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
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.
