Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Add functionality to selectively import parts of a project. For example: don't import the users.
If a transformer has a tabular sort of GUI, like an AttributeManager, or TestFilter, the default column width is determined by the length of the column header. This should be user-set, or FME Workbench should remember the width of column the user last set it to.For example, in the AttributeCreator, the column widths are set according to the lengths of the headers "Output Attribute", "Value", "Type", leading to the name of the attribute taking up over half the transformer window, and the space for where the attribute value is being set is squeezed to the side. In FME 2022, these were balanced roughly 50:50, because the column headers were "New Attribute", "Attribute Value".The appearance of several transformers in FME 2023 is significantly less readable than before. Column width needs to be user controlled, and not dependent on the arbitrary header name chosen in the latest update. It's not enough that this width can be modified in the transformer window, as it is not saved and reverts to default the next time it is viewed.
In transformers that build/create lists, perhaps we could check a box to immediately explode them so we don't have to add the ListExploder each time.
Add Writer for ArcGIS Pro Layer Packages (.lpkx) format.
Add Reader for ArcGIS Pro Project file (*.aprx).
Hi there,The current method of handling attribute aliases is confusing and does not appear to work for all formats that support aliases. I have tried to use it to write to a geopackage (a format that does support aliases) and the alias is not written. Other people are also struggling to write to formats such as ArcGIS Online that support aliases.I would like to suggest that you add a new column in all writer for formats that support aliases, where you can specify the alias value. Aliases should also be read in on all readers for formats that support them and persist through transformations to the written output if the writer also supports them. They should also be exposed and editable in transformers such as the attribute manager.Regards,Marc
Right now the process of assigning an alias to a file geodatabase field when writing is a bit laborious: https://knowledge.safe.com/articles/22423/working-with-geodatabase-field-aliases.html It would be neat if when providing attribute names without underscores, the File GDB writer could take these and set them as the aliases for those fields as well as doing its usual thing of adding the underscores for the real field names. A 'use aliases' parameter may be needed in the feature type or writer parameters.
I am able to write to a local MySQL database, but I would like to write to a remote MySQL database through an ssh connection. I don't see that the Add Database Connection interface allows this. Is there a way to do this?
Examify has been nothing but a hassle to deal with, from beginning to end. Their GUI scheduled me for a time that I did not sign up for, it was painstaking to move it, and the requests of the online proctors are absolutely ridiculous. Please, move away from this format.
For readability/layout sake it would be GREAT to select two (or more) transformers and then select a toolbar button to make all the selected transformers the same with. Ideally the last transformer selected is the the target width for all other selected transformers.Give a little (more) desktop publishing fare to workbench.
Suggestion:Would it be possible for FME to enhance its reading capabilities, especially for DWG layers? Ideally, I'd like to read empty layers and access all the attributes present in an AutoCAD layer. Extracting comprehensive information from the AutoCAD layer table, even for empty layers, would greatly improve data analysis tasks in FME. Now: DWG reader can only read non empty layersFeaturereader, Any schema can read all layers even the empty. But does not contain layer information like for example Autocad_layer_frozen and Autocad_layer_description.Background: I'm currently working on a script that needs to analyze certain parameters across numerous DWG files. Specifically, I'm focused on attributes like Autocad_layer_frozen and Autocad_layer_description.From my observations:When using the DWG reader set to individual file types, I can make empty layers visible. However, since these layers are empty, no data gets read.Both the DWG reader and the feature reader seem to only process non-empty layers.The feature reader, when set to "Any schema", recognizes all layers, including the empty ones. Yet, it fails to capture native AutoCAD attributes like Autocad_layer_frozen and Autocad_layer_description.
HiWe would like to have the possibility to add line breaks in FME Server gallery labels (and maybe even the tooltip). This to get more control on how the FME Server Gallery looks.Right now the linebreaks seem to be based on a space character after a certain width is reached. It would be nice to have some control on this ourselves. For example with some HTML code:Kind regards,Jurgen
I find the FileDeleter Transformer downloaded from FME Hub super useful:FileDeleter | FME Hub (safe.com)Please build this Transformer into FME Form permanently.
Hi,As-is, it's cumbersome to share custom transformers developed with Python, as there's no provision for adding the separate code files.My suggestion is to add some tags to the FMX file format for embedding the Python code directly in the FMX file, and have FME extract and compile such code on load or runtime.The current FMX file has tags "TEMPLATE_START" and "TEMPLATE_END" for mapping file content, so how about adding some "PYTHON_START" and "PYTHON_END" tags for this ?It might also be prudent to add some sort of Python version switch.Cheers
Currently, FTPCaller can only process a single named file at a time. It would be nice to modify this transformer with the ability to process multiple files of the same type using a wildcard. For example, a user wants to upload 10 PDF files to an FTP site. Modify the FTPCaller parameters to allow the user to use *.pdf instead of explicitly using the file name for each file which would result in 10 transformer runs as opposed to if a wildcard was used there would only be a single run of the transformer, where all the pdf files in a folder would be grabbed at once and uploaded.
I added a multi-select choice User Parameter to my FME form, but there are more than 100 values to choose from. It would be a great enhancement to have support for shift+click (or similar) shortcut for selecting multiple options in a choice User Parameter.Thanks,
When I hit backspace in FME Flow Hosted, it can potentially delete an action on the canvas. Surely this functionality should only be reserved for the DELETE key. You're often typing in other parts of the window and hitting backspace all the time so if your cursor is not in the dialog box...boom! you've deleted some of your work on the canvas.Maybe others will vote this up or please correct me if I'm wrong here. Thanks :)
Support writing transparent rasters to Adobe Geospatial PDF.
Add the WMTS format to the list of formats supported by the Data Inspector background map.
***Note from Migration:*** Original Title was: Parameters for 'Number of Retry' and 'Time Delay' in some transformers when failed. It is nice to have parameters to set number of retries and time delay between retries in case of connection failure in some transformers connecting to external services such as HTTPCaller, FTPCaller.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.