Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
An in-depth look at the parameters and techniques involved in creating custom coordinate systems.
A look at cloud-native and cloud-optimized formats and how FME can be used to deal with them efficiently.This idea is a potential webinar to be presented during October-December, 2022.
A look at FME Server triggers that handle file-based events, such as adding/deleting a file, modifying a file, directory changes, date changes, and others.This idea is a potential webinar to be presented during October-December, 2022.
Looking at how Mapnik can be integrated and used with FME, including the MapnikRasterizer transformer.This idea is a potential webinar to be presented during October-December, 2022. It is an updated version of a previous webinar.
This webinar will cover the absolute basics of using both raster data and point cloud data within FME.This idea is a potential webinar to be presented during October-December, 2022.
A webinar that explores the use of FME for transportation and transit projects, including DoTs.This idea is a potential webinar to be presented during October-December, 2022.
This webinar is an in-depth look at how to use parameters. It will include best practices on where/when to use them across FME products.This idea is a potential webinar to be presented during October-December, 2022.
A deep dive into coordinate systems in FME. A follow-up to Coordinate Systems 101.This idea is a potential webinar to be presented during October-December, 2022.
We can already write into an existing table in h_store format using text type (thanks to Takashi for the tips). It would be great that postgres/gis writer recognise h_store type. Consequently, we would be able to create a new table containing h_store type using FME ( currently, I use SQL instead)
The ProjectWiseWGSConnector List action needs an option to add search filter (e.g. regex on doc name), so it can improve the performance of the list action and narrow down the returned results.
Currently, the Geometry Parameter only supports the LL84 coordinates. It would be nice if we can generate the value with a different coordinate system when a user specifies a location/shape.
It's not uncommon to gzip files before uploading to s3. A nice to have would be the option to auto unzip following download and the option to gzip on upload.It's a bit tricky right now to achieve this
With the release of the final version (10.8.1) of ArcGIS Desktop and the publication of its end-of-life plan, it should be time to start building the transition plan to ArcGIS Pro. This will obviously impact many transformers.
Currently there is no real version control with FME Workspaces. There are metadata options where you can manually input changed and datesThere is a github connection in FME Server which lets to make commitsThere are CustomTransformer versionsThere is no workspace versionAlmost all tools have a command line option to check the version. fme.exe will do this for example - or almost anything. The option to set a version in a workspace and be able to call "fme my_workspace.fmw --version" would be great. The version should also be in the log fileIn addition to being able to fetch a version there should be command line options to update the version. This would greatly assist in build pipelines. An example of this is npm (nodejs)Being able to know and control the version is pretty important if working in support
support PipeReplacer custom profiles,PipeReplacer can't change the closed circle face,and the point quantity
Right now is not possible to directly update a web connection in FME Server. You have to either duplicate an existing one or create a new one and then remove the old one and go back and change the name of the new one to match the old one (https://docs.safe.com/fme/html/FME_Server_Documentation/WebUI/Web-Connections.htm). I know, it's absurd. An update button would be much easier than that.
I love being able to use cached values from a workspace run to populate various Transformer choices and I think the AttributeFilter would benefit hugely from this. Please add the capability to import values from the cache for the list of attribute values to filter.
***Note from Migration:*** Original Title was: Provide a convinient way to dynamically set writer attribute width according to incoming data Sometimes, we have the need to be economical with the output string attribute width, to avoid creating large datasets. Especially when the dataset already has a large number of attributes, and features. It would be really helpful to be able to set the output string attribute width to accommodate the longest string in each field, but no longer. Currently, the only way I can think of is the method suggested by david_r here, which involves exploding all attributes, calculating string length, and find the max length of each attribute. This process will be quite slow when dealing with a large dataset. Any way to make this easier will be appreciated.
In order to speed up performance of certain 3D workflows it would be nice to be able to have the option to have FME skip applying the textures to features.When reading large CityGML files for example if there are textures it can be a bit of a performance in certain workflows where textures are really not needed.While it is possible to first move any textures out of the correct location this can add complexity to the process, especially for more generic workflows and when it is unknown if textures are included or not.
This is an idea for the FME Server in the FME Cloud.Being able to choose your own naming for the folder within the zip when using the data download service.See:https://knowledge.safe.com/questions/88197/naming-data-download-output-folder.html
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.