Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Either by renaming the current "Tiler" to "DatasetTiler" (or similar), and create a new "GeometryTiler" transformer, that works on individual tiles/geometries.Or by adding a dropdown or checkbox to "Tiler" that enables tiling of individual tiles/geometries instead of the whole dataset.In a feature-by-feature workflow it makes sense to have this kind of feature based functionality.CheersLars I.
***Note from Migration:*** Original Title was: InlineQuerier and SQLExecutor text editor behavior changed in 2016, revert to 2015 The text editing of SQL in the InlineQuerier and SQLExecutor used to allow for simple drag-and-drop of the field names into the notepad space,now in FME2016 dragging a field name creates double quotes and a line feed character, all of which have to be deletedplease can the drag-and-drop behaviour return to just the field name - or ideally with the addition of its table prefixed e.g table_name.field_name
Many times when using the ListBuilder I am only interested in seeing the exposed attributes in the list.A feature read from text_line reader (text_line_data only visible attribute) for instance produces a list that contains_list{}.text_line_data _list{}.fme_basename _list{}.fme_dataset _list{}.fme_feature_type _list{}.multi_reader_keyword _list{}.text_line_eol _list{}.text_line_length _list{}.text_line_number _list{}.text_line_type And only the first is visible on the transformer, all the rest have to be explicitly exposed before they can be removed.
Hi! This is an idea, or more a request to close a trap I seem to fall into every time I use the Data Inspector.When you switch to 3D view, the next thing you want to do is rotate the view. But the Select & display tool is on by default, so I end up mistakenly selecting some random objects.I would like that the Orbit mode tool goes on by default when you switch to 3D, like it goes off when you switch back to 2D.
Not so much a format as a source/destination for data files. Idea is that FME would retrieve or push data in / out.
***Note from Migration:*** Original Title was: Backup and Restore: migrate a subset of FME Server configuration (e.g. one repository)
We have mostly data in meters, and I can't zoom close enough to see e.g. holes in geometry. There's some kind of limit. In many other data viewers zoom goes to millimeter or even smaller scale. I hope the zoom in FME Data Inspector could be updated.
When I try to create a screen shot of a canvas as a PDF it does not scale, but spans multiple pages. I end up creating an A0 just to get it all on one page. It would be much better if it would scale to an A4.
(basically copy the options from Merge Rasters in ArcMap)
A richer search experience for transformers, including full access to help. And the ability to plop down readers/writers from the same interface.
The FMW reader reader need to return more information for it to be truly useful, notablyTransformer connectionsBookmarks (which transformer is in which bookmark)
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.
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.
