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.
Please consider adding rotation to text in power point writer. It would be nice to rotate street names.
Please consider adding a reader for Cesium 3D tiles, for users who want to convert 3D tiles to other formats.
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, 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
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.
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
The Native Revit reader in 2019.0 doesn't recognize RFA files. It would be nice to have that supported. @rollo
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.
There are cases where the BulkAttributeRenamer cannot expose new attributes / hide old attributes automatically, especially in the Regular Expression Replace mode. It might be useful if these parameters would be added to the BulkAttributeRenamer.Attributes to ExposeAttributes to HideLists to Hide
The FME i3s writer to output SLPK files is working great - but it only includes textures that can be displayed in ArcGIS Pro:Once uploading and publishing the SLPK to AGOL or ArcGIS Enterprise, the web scene does not display any textures.With the workaround to output the read 3D data as multipatch feature classes to a (scratch) gdb to be picked up from there in ArcGIS Pro, it would be way nicer to have the option to write SLPK-files with some texturing options like here: https://pro.arcgis.com/en/pro-app/latest/tool-reference/data-management/create-3d-object-scene-layer-package.htm
***Note from Migration:*** Original Title was: Allow Esri ArcGIS Portal Feature Service Reader/Writer to use a custom token for authentification Hello,It would be nice to be able to authenticate with simply a token for 'Esri ArcGIS Portal Feature Service Reader/Writer'.Currently it is only possible with 'Esri ArcGIS Server Feature Service Reader' but there is no writer:"To read directly from a Feature Service without authentication, or with a manually-supplied token, use the Esri ArcGIS Server Feature Service Reader." (ref: https://docs.safe.com/fme/html/FME_Desktop_Documentation/FME_ReadersWriters/arcgisportalfeatures/arcgisportalfeatures.htm) Usage of built-in account is not recommended in my organisation and I don't like the default OAuth one because it expired. I built a CLI to acquire a token because our SAML provider configured with Portal for ArcGIS has kerberos enabled but I can only use it for reader !Please help !Thanks
***Note from Migration:*** Original Title was: Attribute Value Mapper could take in an attribute value as the destination attribute? I am resolving domains codes to descriptions. I may be walking the wrong road but I decide to use a attribute exploder which gave me the attribute name and the coded value. I have a sheet that contains all my coded values and their description so I used a feature merger to merge on the the value and the code. I was left with many values that needed to be updated. I had hoped to use the Attribute Value Mapper to quickly move the description to the attribute using the _attr_name from the exploder but the Destination Attribute in the mapper does not accept the parameter.
***Note from Migration:*** Original Title was: Let ArcGIS Online readers access features shared with your organization, rather than only group or owned content
Would it be possible to have a repository of XML templates that are compliant with various metadata standards (personal interest in EU-INSPIRE and UK Gemini) that could be easily loaded into the XMLTemplater? I think this would be a really useful starting point for users with limited XML knowledge like myself.Thank you
Mike by DHI is a common used software for e.g urban flooding analysis, seehttps://www.mikepoweredbydhi.com/. It would be great to be able to work with the format dfs0 (time series) and dfs2 (raster data) in FME Desktop. If possible to read data in FME it can be used for volume calculations of flooded areas, calculate flow to be used for design of stormwater solutions etc. Also makes it possible to perform spatial analysis (flooded area vs buildings etc).
Wouldn't it be fantastic to have the LeftRigthSpatialCalculator functionality to be included in the NeighborFinder? I just thought of it when I saw the "idea" below:Attribute accumulation for LeftRightSpatialCalculatorhttps://community.safe.com/s/idea/0874Q000000TlehQAC/detailCommunity, what do you think? Pros/Cons?
Would be nice to work with features supporting a 4th dimension. x,y,z,t coordinates. Render is not important, but would make a lovely visual effect if the data inspector supported the timeseries rendering. Scaling time is difficult, but having a max span of T seconds might work?
I am running a process that has 53 stored procedures and its been painful to manually expose the attributes from the stored proc. Can we have a check box/ option to expose all or only some, but have the transformer read the schema? Thanks!
I realized that when you're doing a loop inside a linked custom transformer, you don't have the possibility to redirect the loop to a private input. If you do that, you'll have a "LOOPBACK_INPUT_TAG" error.So you have to publish the input (even if you don't want it to be visible on the custom transformer).
It would be great to be able to expose attributes at runtime for dynamic workspaces.
Include HERE Maps Flexible Polyline as format much like the Encoded Polyline is included in the Geometry Encoding.Documentation can be found here: https://github.com/heremaps/flexible-polyline Unfortunately HERE Maps uses another type of encoded polyline as a variation from the standard.This would be great to make API requests and return their version of the polyline, and feed directly into Geometry Replacer to create the Geometry.
Today we can only make use of fme.macroValues[]. This is just a list of ALL parameters in the entire workspace. This no longer works at the moment you start creating custom transformers because the parameter name get extended with the name of the custom transformers it's embedded and you can retrieve those. The parameter content is also not escaped or evaluated when linked to an attribute.A method maybe called fme.getParameter(<parameter name>) that has the same behaviour as the ParameterFetcher would do wonders. Today we need to transform parameters into attributes, pass them through the PythonCaller and remove them again after the PythonCaller. Many additional steps that could be avoided and reduce performance and potential errors.
Hi, I do a lot of image QA on ECW files and have automated much of my workflow via FME. Two tasks are still manual; checking ECW version number and the compression ratio (actual and target) of the image. The RasterPropertyExtractor can see the attributes, but does not always extract these values despite them being available via other software packages for all ECW files. I'd like to see the RasterPropertyExtractor being updated so that it is able to extract these values reliably.Thanks
I notice that there are transformers like a JSONExtractor transformer that can extract attributes from JSON using a JSON Query, and an HTMLExtractor transformer that can extract attributes from HTML using CSS selectors. Why not an XMLExtractor transformer that can extract attributes from XML using Xpath?I know that creating attributes for specific XML elements is already possible using Xpath using the XMLXqueryExtractor, but just seeing anything that even looks the slightest like code can already be a bit scary to some users (and also for some XML that uses explicit namespaces in the XML element names you would need to declare those in the XML, etc. So that also looks a bit scary to users (although probably in a transformer you might need to have the same option to make it work?)So my Idea would be that if you have some XML like this:<?xml version="1.0" encoding="UTF-8"?><root> <student> <id>01</id> <name>Tom</name> <lastname>Price</lastname> <hobbys>football</hobbys> <hobbys>hockey</hobbys> </student> <student> <id>02</id> <name>Nick</name> <lastname>Thameson</lastname> <hobbys>reading</hobbys> <hobbys>gardening</hobbys> <hobbys>painting</hobbys> </student></root>Currently you would be able to create (specific) XML attributes using the XMLXQueryExtractor, like e.g. a list for only the name and the lastname of both students:fme:set-list-attribute("student{}.name", data(//student/name)),fme:set-list-attribute("student{}.lastname", data(//student/lastname))I guess the implementation might look very similar to the HTMLExtractor. Actually, it even seems that in some (or all?) situations you might even be able to change your xPath to CSS selectors, and use the HTMLExtractor for the same job.Target Attribute, CSS Selector, Tag Part/HTML Attributestudent_name, student > name, Valuestudent_lastname, student > lastname, ValueReturn Format: List Attribute
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.
