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.
***Note from Migration:*** Original Title was: Improve Accessibility of Newly Created Attributes in AttributeCreator/Manager GUI In FME 2016+, you can access newly created attributes in an AttributeCreator/Manager for setting other attributes in the same transformer through the GUI (e.g. Text Editor, Arithmetic Editor, etc.) like this.However, in the Conditional Value setting, the new attributes cannot be accessed. Although you can enter an expression with the new attributes manually (e.g. "@Value(new_attr1)") and it works fine, the background of the parameter field is still colored with pink.It would be convenient if new attributes could also be accessed through GUI for conditional value setting.
For instance: I use a system parameter to define a folder for a writer, in this case an Excel writer.Problem: A writer set to $(FME_SHAREDRESOURCE_DATA)${USERNAME} est.xls will find or create the appropriate folder. But right click on the feature type and select Inspect and the Data Inspector gets confused because it will look for D:FME_support${USERNAME} est.xls.Idea: Either let FME Desktop resolve the system parameter before sending the path to the Data Inspector or make the Data Inspector able to resolve the parameter on its own.Result: Much more easy to do a quick Inspect when using system parameters.
Is it possible to add the index/PK/not null constraint creation feature on User Attributes to FeatureWriter when the Format is a database? Just like in the writers.
This might be old news, but I want the VertexCreator to be improved. This idéa goes back to the age of 2DPointCreator-days.I guess I'm not the only one to, at first, mix the x and y attributes up, and has to change their settings after first run. Well, changing them is quite a few clicks and scrolls in the list of attributes.I'd like to have a "change places" button next to the x and y fields och the VertexCreator.In addition, it would be nice for the fields to be auto populated on connection, finding attribute values like x/y lat/long n/e etc.
The ESRIJSON writer apparently does not write 3D coordinates in FME 2016Writing 3D coordinates would be very interesting in future releases given the 3D developments in the ESRI JS API 4.x.
***Note from Migration:*** Original Title was: Add Additional Tables to a reader after it has been creaded with workflow option: Individual Feature Type After you add a some tables to a reader, as a individual feature type, It is not possible to add tables from that same database. This slows down the process of loading tables into FME as the user has to go back and add the connection information or change it (if their last database was different). It would be really great if I could simply add more tables to an existing reader that appears as a separate feature type.
Tool set for creating cartographic output, similar to pdf styler but for designing map layouts, north arrows, legends, inserts etc. This tool set would then be fed into by other transformers- Mapnik for the image, a table for legends and attributes for text etc. I rasied a similar idea regarding creating legends but I think a whole carotographic output tool would be very useful.
There are some geospatial tools based on Accumulo or HBase databases residing in a Hadoop environment, e.g., GeoMesa, GeoTrellis, GeoWave. It would be nice if FME supports some of those NoSQL data streams.
Due to the variety of FME Desktop versions used by clients, I have 6 versions of FME Desktop installed on my work computer. It would be nice if there was a way to to apply/update a license to all installed versions of FME simultaneously. My thought is that, when I open the Licensing Assistant for any of the installed versions, and apply a new license, it would be awesome if a dialog appeared asking if I would like to apply the license to all installed versions of FME Desktop, with Yes and No response buttons.
Would be great to have a transformer to read RavenDB format.
FME has the ability to write a compressed shapefile. However, the standard extension is .shz, which is not recognized by QGIS, which can read compressed shapefiles, but not with the shz extension, only zip.I would like to extend the functionality in FME to write to a zip extension, without having to run some shutdown script.
As a user, I want to use the exif metadata of my picture file to be read by the Exif reader so I could use the metadata for my translation.
Hi,The raw text string that we get back from the FTPCaller at the moment is hard to process. When selecting Download to an Attribute, it would be cool if you could select the response type to JSON or XML instead.
Would make it a lot easier to read in a CSV (that is formatted in a non-data-friendly manner) in 'chunks' by specifying one reader for one part of the CSV, say lines 1-10, and another CSV reader for lines 11-20.
When designing an async download service I would like to send an email - which works fine, but I would also like to display the download link on the webpage if the user sticks around long enough. Currently thats not possible with async calls to the download service.
It would be handy if it was possible to configure a workspace so that it triggered a notification for every n features written or processed.It is currently possible to implement something similar manually using e.g. a ModuloCounter and an FMEServerNotifier, but the workspace gets a bit crowded when there are multiple data streams.
You can run Workspaces from Python using FMEWorkspaceRunner but not apply transformers to feature objects.
Make it possible to "merge feature types" when reading Excel-files
***Note from Migration:*** Original Title was: Add Function to Populate TestCondition in TesterFilter with Unique Values of Selected Attribute Add Function to Populate TestCondition in TesterFilter with Unique Values of Selected Attribute
I'm trying to create a workspace that fetches (among other data) all addresses as a CSV from a web portal. I need to do this with the FeatureReader and a generated URL for "Dataset".It seems that FME is trying to download the whole dataset (with 3+ million records/lines) when I'm setting up the workspace.It would be beneficial to have FME _not_ read a huge web based dataset when setting up the workspace, i.e. in design mode. In any case, it has no practical application, since I do have to manually type in the CSV field names even though they're given as line #1 in the dataset (and I did check the "Field names follow Header" in parameters).E.g. by abstaining to read any dataset that starts with "http://", or at least just read a suitable small fraction.Cheers
At the moment the Apply to functionality is bit confusing. E.g. if I would change Table Handling for all other Feature Types, I have to click Apply to -> then go to Parameters to change -> then choose the parameter. Usually it's just one parameter that I want to change quickly for all other feature types of one Writer.My suggestion: Go to the drop down menu of the parameter -> Choose Apply to all feature types
DEBUG mode for workspaces called by WorkspaceRunners. For linked worksheets I would like to have the option (debug mode if you will) for the caller to open multiple copies of FME (if not already open for that target worksheet) so that you can see what is going on, instead of running it like a command line. There is nothing more frustrating than debugging a target worksheet when having to manually populate the published parameters so you can figure out what went wrong.
When running WorkspaceRunner,Cannot display the running status of the workspace called in real time.If can display the canves of WorkspaceRunner called on the run time, And like the usual workspace,Display the number of Feature that has been processed And real-time processing log. Then it will be more convenient to debug, And better grasp the running situation.Of course, It is not necessary to display the working space at any time.So can add an option in the WorkspaceRunner parameter, such as the "show canves", only when this option is selected to show the canves.
Would be great if all WRITERS / Featurewriters (files) would have a "Cache" option. Ie the workspace would do a "speedtest" towards all related folders before a workspace runs:For instance:- C: 100 MB/sec R - 50 MB/sec write- D: 10 MB/sec R - 5 MB/sec write- J: 1 MB/sec R - 1MB/sec writeSo when writing to J: FME would instead write to FME TEMP and then copy the files to J: after the process because it is slow to work against a network drive, when "Cache" enabled on writer.
An option to remove the GDAL intermediate processing done by the JPEG reader if the translation is only for reading the exif metadata to extract points from the georeferenced pictures.
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.
