Open ideas have been reviewed by our Product Management and are open for commenting and voting.
Please consider adding a reader for Cesium 3D tiles, for users who want to convert 3D tiles to other formats.
It would be great if an FME user could see in the workbench where a particular record drops out of the translation. This would save us a ton of time in hunting for issues in complex workbenches.
A function/transformer to calculate pointcloud points local normals would help a lot the classification process and to extract groups and planes from pointclouds.Example with CGAL
Hi everyone!Is there any chance we could see support for the fits (.fits, .fit, .fts ) format, it's a format used by professional and amateur astronomers, and some other parts of the scientific community. Some info here:https://en.wikipedia.org/wiki/FITSand here:https://fits.gsfc.nasa.gov/fits_documentation.htmland here:https://photographingspace.com/how-to-use-fits/Libraries for it are available here:https://fits.gsfc.nasa.gov/fits_libraries.htmlIt's an open format, free to use.I would *love* to get FME to process/automate this stuff. After an observing session, I end up with thousands images and gigabytes of data, each in a separate R,G,B and L channel, which I have to sort and process and then recombine into a colour RGB image. It literally takes me hours and hours to do.Typically I use a program like deepsky stacker or registax, but it is pretty labour intensive at times. We have to register the images, so that they are properly aligned (objects move even when tracking them, so the software learns to keeps the same stars lined up for each image) and then stacked to boost the signal to noise ratio. They get aligned so that they don't appear smeared out. I would provide a sample fits image but it's not supported here for upload! :(Happy to go into further detail, and answer any questions.Thanks!
Support Apple's new image format natively.
Hi, I need to calculate the rolling 90% percentile of the last 30 records, but I found that there is no percentile in the math function. Please do add this kind of basic math function
There should be a conversion option from .3mx to GDB and vice-versa, since Bentley and other providers are offering their products in this format and there is no easy way to import it into ArcGIS.
***Note from Migration:*** Original Title was: Network Authentication parameters in Readers when reading from parameters or attributes If you want to read from a URL stored in an attribute or a parameter in a FeatureReader you lose the possibility of setting the Network Authentication parameters, they only show up if the dataset value starts with http:// or similar
The GLTF Writer doesn't support the addition of feature attributes to Nodes/Groups in the written GLTF files.The GLTF schema allows for both a "name:string" property and an "extras:map/object" property for both Nodes and Meshes. This could be used in combination with the schema definition/user attributes of the writer. Perhaps with options to apply at Node or Mesh??I currently use a workaround to this with the FeatureWriter using GLTF/json and then on write, read this back in with the JSON Reader file, merge with the original feature dataset using JSON Templating. I then write this to local disk and compile the result as a GLB (with Draco compression) from the command line. (This last step could conceivably be a python script)It would definitely be beneficial to go straight to the GLB from the original writer.
MrSID Reader currently support Generation 3 MrSID files. Generation 4 is now available, having support for a fourth band for transparency. Since we cannot always control the version we are sent by data providers we would like the MrSID reader to support all available generations of the format.
We use FME Desktop and FME Server to manage important processes that read from and write to ArcGIS Online (and to a lesser degree Portal for ArcGIS / ArcGIS Enterprise). The interface to specify an item for ArcGIS Online readers and writers has improved dramatically in recent versions. A major limitation is that items are specified using a group name and the item name. It appears that more recently the item ID is also incorporated, which will help to resolve conflicts if items and/or groups have the same name. It seems that folders within an owners content may also be used in lieu of groups, which is convenient, but when used to specify an item, only adds to the issue described below.We propose that ArcGIS Online items should only be specified by their ID in readers and writers. The ID is unique and constant, and is how Esri references and manages content within their systems. It's also how other third-party vendors often reference items. We'd still like to be able to search by item name, but as a large organization, there are various circumstances where item names need to change. These changes currently cause process breakage in FME and require significant re-work.Please consider this for future releases of FME. We're happy to provide additional information, if helpful. If it is currently possible to specify items solely by their ID, we're interested in that.
***Note from Migration:*** Original Title was: Excel Reader - select Worksheets to read by order in XLS/XLSX file rather than Worksheet name I would like to be able to choose the Worksheet to read from an XLS/XLSX file by the order it appears in the file, rather than have to specify the name. I have recently had to batch process a large number of Excel files where the Worksheet names were not known. There didn't seem to be a satisfactory way of dealing with this (I searched the Knowledge Center) so I end up creating 2 Workspaces and using the SchemaReader, WorkspaceRunner and FeatureReader to do what I needed. Even then, the process crashes randomly if I try to process more than 2 pairs of Excel files at a time (FME 2016.1, need to try in FME 2017).It would have been a lot easier if I could have specified the Worksheet number in the Excel Reader, as I was always only reading the first Worksheet and the name wasn't important. OK, so I only had one Worksheet in each Excel file, but for multiple sheets you could specify which numbers you wanted e.g. read sheets 1,3,4,6 (or zero based if you prefer). Worksheet name could be exposed as a Format Attribute.
There is currently no simple way to have truly dynamic attribute mapping.I would like the ability to provide an input file, a mapping file (old attribute, new attribute) and get an output that is identical to the input except for the attribute names.While the schemaMapper allows you to dynamically rename attributes referencing an external lookup table, that lookup table is hardcoded, you cannot use a parameter to specify it.Additionally you cannot dynamically write out the changed attributes. All the schemaMapper examples assume hard coded attributes on the writer, which can lead to issues if the mapping table is updated and the writer is not. Both automatic and dynamic mode use the original schema unless schema from schema feature is selected.While one can use the SchemaSetter custom transformer to generate the new schema feature, it has the flaw that all strings are mapped to varchar(256) , leading to significant bloat in the output file when the original attribute might only be a few characters.Two updates to the schema mapper would allow this dynamic ability without having to script it in python. Allow the Schema mapping table to be set by a user parameter, or even an attribute.Have an output port on the SchemaMapper with an updated schema feature
I would like to be able to use voice recording to help with reporting for incident/emergency report apps. The recording should be available from FME Data Express as workspace/app parameter value input.
I had the idea to add the "download from fme server" button directly on the "Start" page of FME Desktop when the application launches. I know the button exists on the toolbar as well, but so do the "New" and "Generate" options. In teaching new FME users this is always something they seem to overlook.
The Native Revit reader in 2019.0 doesn't recognize RFA files. It would be nice to have that supported. @rollo
The middle line in road construction is often represented in LandXML and it's proposed vertical alignment for the profile is save in the ProfAlign element. Right now FME can't interpret the ProfAlign element which means that the data is in 2D without the vertical alignment.See also this old question
Hy,is it jet possible to import a 3D object (IFC) to QGIS?I am trying with the workflow IFC – FME Destop to gml – QGIS.I am getting just a 2D projection in QGIS. Is it possible to get 3D object with right dimensions in QGIS?Kind regards,Jaka
Rather than the *U_XX temporary name. (PR 65258)
Wouldn't it be nice to introduce a Jupyter Notebook <-> FME Server Python API? This could be a parallel development next to the existing Python FMEObjects API (and it could also leverage it), like Esri did for instance with their well-known ArcPy library and their newer ArcGIS API for Python.
***Note from Migration:*** Original Title was: TestConditions in TestFilter , support list elements index range in Test Clauses In TestFilter, allow specifying the list index range in the Test Clausee.g., _list{[0-2]}.fruit = 'Apple'rather than specifying each element index to test for individually:_list{0}.fruit = 'Apple'AND _list{1}.fruit = 'Apple'AND _list{2}.fruit = 'Apple'without going into PythonCaller, or custom transformer way
The ChangeDetector transformer is great particularly when enriching source data and updating a target database, but it is sometimes difficult to track which attributes are shared between the Original and Revised ports. It would be terrific if the attribute lists could be color coded, or have some other kind of indicator to quickly shed light on the attributes that are on both ports vs those that are only on one port. More than once I have been confused why I was seeing so many updates when some enriched attribute hadn't yet been considered before reaching the revised port. I'm sure there are other transformers that could benefit from similar treatment.
In the workspace, attributes have their own datatype which is sometimes different from the original data type (in the source).For exemple, a "date attribute" in the datasource is automaticaly converted into a "string attribute" into the workspace.Really anoying for Python scripts to work on these attributes and to detect the type of the data without auditing every value of the attribute.In this case, it is nearly impossible to create a dynamic schema with date columns without auditing every values.It would be really easier to work with original datatype.
***Note from Migration:*** Original Title was: The ability to automatically remove all attributes from the reader that are not used inside the workspace After authoring a workspace I would like to have the ability to automatically remove all attributes from the readers that are not used by transformers and/or writers inside the workspace. Removing these attributes will have a positive effect on performance. It’s sometimes a hassle to do this manually in large workspaces.
***Note from Migration:*** Original Title was: Automations "Merge messages" action should synchronize/merge output from "Run a workspace" actions Automations "Merge messages" action should synchronize/merge output from "Run a workspace" action jobs. For example, for cleanup operations or notifications following completion of multiple workspace jobs.
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.
