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.
The GridInquest Transformer is currently only available in the 32-bit version of FME Desktop. We currently use the GridInquest Transformer within a process to convert data from a local grid system to British National Grid and vice-versa. Having this transformer available in the 64-bit version of FME would enable us to take advantage of the benefits of 64-bit processing (e.g. ability to access more memory than in the 32-bit version). I would imagine that this would benefit a significant number of FME users in the UK.
Write to MBTiles and then publish up to MapBox directly.
I think it would nice to have the standard options 'Inspect' and 'Open containing folder' available on both the FeatureReader and the FeatureWriter. These are great functions available on normal Readers and Writers and as we move more and more towards their Transformer-based counterparts, the existing functionality should be moved over.As both the FeatureReader and the FeatureWriter support multiple Feature Types, the Inspect option could have a pop-out on the side to select the desired Feature Type. This would be a screen similar to the 'Attribute Value' selection menu. You could even include an option to inspect 'All' Feature Types.
Possibility to save FME Server connections in named connections like databases and web services and to use them in "Publish to FME Server", "Download to FME Server" and FME Server transformers.
Never hit the Gear button again. When you select a transformer, its parameters get shown and you can edit them right away. Maybe an APPLY button to make them take effect. Should reduce clicking.
Automatically route connection lines around transformers using a square boxy style -- all turns 90 degrees.
Quite often I need to calculate the difference between two dates. The result can be needed in days, hours, minutes or formatted like a date.This is hard to accomplish in FME.A DateCalculator transformer would resolve this.
Directly read/write data from S3, DropBox, etc without manually downloading/uploading.
In the same way as you can duplicate a transformer, adjust it slightly and reuse it without having to fill in all the details again, I'd like the ability to duplicate a parameter that I've just created and then edit it slightly for another intended purpose.
***Note from Migration:*** Original Title was: I want to share with the FME users my experince in how to categories the polygons by Selecting all points in a polygon, add the value of the majority of points - FME Desktop
Currently if you use Feature Reader (PostGIS) with a Spatial filter of anything other than Envelope Intersects, the log says: 2017-03-08 09:22:40| 306.5| 0.0|INFORM|Notice - reader format `POSTGIS' does not support querying by spatial predicate, but supports envelope queries. FME will create equivalent results by performing spatial predicate calculations locally. Performance should not be affected. Obviously PostGIS *does* support the FeatureReader spatial predicates and many others besides - http://postgis.net/docs/reference.html#Spatial_Relationships_Measurements It would be nice if FME could use these native filters rather than read in all data within the envelope and use its internal spatial filter to decide which to keep/remove. I'd be surprised if there wouldn't be a performance gain doing it entirely in the database, despite what the log say.
It would be very helpful to be able to select the SRS when requesting data from WFS. Please add an optional parameter to select the CRS.
Current functionality only permits connecting to Postgresql/PostGIS as a user. However the user may need to connect using a 'rolename' in order to carry out certain actions within a schema.Scenario:A user belongs to rolename: "data_readers"They want to read data form schema: "the_data"Schema "the_data" only permits 'SELECT' for rolename "data_readers". Individual users do not have 'SELECT' privileges on the schemaIn this scenario FME cannot be used to read from schema "the_data"For Postgresql and probably other database connections.
Currently the ListRenamer New Name parameter can only be hardcoded. It would be nice if the new name can reference attributes or parameters, or even better have access to to the full text editor.
I'd never bothered reporting this before as I'd always assumed someone at Safe would notice. Why is Background Color under View > Background Color, whereas Background Map is under Tools > FME Options > Background Color?
I have noticed that FME tends to be installed to C:appsFME. If you are installing several versions you could easily overwrite the previous installation. I think it would be useful to add release number to installation folder, say C:appsFME2017
Folder Agent (http://www.folderagent.com is a Free program that allows active folder watching for files and folders then allows you to apply multiple manipulations to the file or folder.
I use more and more QGIS and usually I like to check things in QGIS. I think it would be a nice way to ease this, giving the chance of opening QGIS instead of FME Data Inspector with the inspectors outputs as temporary layers.
One of my concern is the stability of the Data Inspector. It is by far not as stable as the old Universal Viewer. This is caused by, in my opinion, data having no coordinate system attached. Won't it be a good idea to have a "default coordinate system" setting for data without a CS? I hope this would make Data Inspector a lot more useable.
Can we have a transformer for detecting similarity between geometries? This post may be a good starting point: https://lin-ear-th-inking.blogspot.co.uk/2009/01/computing-geometric-similarity.html
Similar to this idea ( https://knowledge.safe.com/content/idea/19290/two-input-port-ordered-by-group-asynchronously.html - which I still really need to be able to optimise many workspaces), it would be good if the FeatureMerger could handle Join On fields that come in synchronously (Note: Join On, not Group By - assume Group By is empty for this example), but not grouped as All Suppliers, then All Requesters. Currently if I have this input: Requester_id = 1 ....Supplier_id = 1 Requester_id = 2 ....Supplier_id = 2 And so FeatureMerger will cache the both Request and Supplier entirely before doing the merges; a massive problem for anything more than a medium sized dataset, and makes quite a few workspaces effectively impossible. I guess a cardinality parameter like DatabaseJoiner has could be used, but that's optional. This would make a lot of workspaces for any large datasets actually workable. Currently I spend a lot of time splitting up datasets in overly-complex ways so that I can process them in chunks to work around memory limits.
Possibility of copy a parameter and paste it in public or private tab, editing it in order to create a new parameter using the same information.
On a 3-point arc I'd really like a way to retrieve the Mid Point. The data is visible in the Data Inspector, but there doesn't seem to be a way to retrieve it outside of Python.The Transformer that I would've expected to help me here would be the ArcPropertyExtractor. As shown below, it contains most of the arc properties, however the Mid Point is not one of them.The Center property is the center of the circle on which the arc is based, i.e. not the Mid Point halfway on the arc.Not all arcs are 3-point arcs, so I can imagine giving a calculated value or leaving the attribute empty for non-3-point arcs.
Ref this post: https://knowledge.safe.com/questions/40520/write-sketchup-with-colors.html It would be nice if FME translated from RenderingOptions.GroundColorRGB -> fme_color on reading of Sketchup, and the other way when writing to Sketchup
MongoDB (from "humongous") is an open-source document database, and the leading NoSQL database. Written in C++
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.
