Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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.
The PointConnector (LineBuilder in 2017) transforms the resulting line into a polygon automatically if the start and end nodes matched in 2D, but this is annoying when you want to only create line geometry even if the resulting line is closed.It would be nice if a parameter could be added to the transformer so that the user choose an option how to handle lines closed, including connect Z mode.
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
It was suggested on this thread to open a new idea.My use case is converting a point cloud with associated colors to a mesh and preserving the color/texture. The PointCloudSurfaceBuilder does this but the colors are saved on the mesh vertices and when exporting to most formats that data is lost. OBJ seems to be the only one that works and not all viewers seem to display that data (colors do not show up in Blender but do in MeshLab).The above thread lists a work around using MeshLab which I will post at the end. It would be nice if FME could convert the mesh vertices color into a texture preventing the need to go to FME -> 3rd party and back to FME if OBJ isn't the final preferred form. This is also an issue for other use cases as the above thread was about a different issue that I found as a solution. I believe I'm the first to document it as an issue with the PointCloudSurfaceBuilder. The work around steps from daveatsafe:Please install and start MeshLab and do the following steps:File -> Import Mesh, then choose the OBJ filePick Filters -> Texture -> Parameterization: Trivial Per-Triangle - set Texture Dimension to 8192Pick Filters -> Texture -> Transfer Vertex Attributes to Texture (1 or 2 meshes) - set texture height and width to 8192File -> Export Mesh As - Save to another OBJ in same folder.
Merge Solids
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.
Reader/writer for 12d file formats http://www.12d.com/company/about.html (to keep our surveyors happy!)
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
Expose the ArcGIS Online Feature Layer URL as and attribute that can be accessed from the ArcGIS Online Reader and Writer
When creating DWG-files that are used for production of blue prints the mappning between colors in AutoCAD and eg. linewidth in the PDF/paper are controlled with a plot style table in a filed called ctb. Every paper space in the DWG-file can be associated with a ctb-file. It is important to verify that the correct ctb-file is used.FME cannot read the information about which ctb-file that is associated with the paper space. This idea is for reading the name of the ctb-file for the DWG-formats in FME.
I'm getting BIM data in nowhere space but I can get coordinates for control points, but I have no idea how to derive parameters A-L for the 3DAffiner.
Now if you specify to attach a file in the Emailer the file is mandatory. It will be nice to specify if the attachment is mandatory or not. In some cases my attachment is not created in the procedure, for example an error log.
It would be nice if the Cesium 3D Point Cloud Writer would automatically create "tileset.json" file corresponding to the point cloud dataset (*.pnts).
When developing against APIs it is often common practice to test and get familiar with the API in postman before bringing it into your solution (FME). We have also found that it is becoming increasingly common for platforms to share how their API's work by sharing a postman package (JSON). I have found that sometimes an API will work in postman, but when you mimic the setup in the HTTPCaller, it doesn't work. Or its not always clear how the postman setup should be applied to the HTTPCaller configuration. A helpful solution, would be the ability to import configuration into the HTTPCaller, a postman package (JSON) file could be loaded in and used to populate the HTTPCaller configuration and parameters.
I'd love to see FME using the same number formatting as your computer locale, both for data inspection purposes but mainly for authoring.Alright, data inspection in FME is just for a quick view, but still it would be nice to have a setting in the FME Options where you could choose a decimal and thousands separator, default being the same settings as your locale. In fact I'd say you don't need this setting if you could just use the same number formatting as in the locale.However, what I find more annoying is having to use a different comma separator when writing numbers. The decimal separator in my locale and in my numpad is a comma, every time I write a number I instinctively use a comma as I do in any other software, and then when I see a wrong parameter I have to go and look for a different key in a different side of the keyboard. And that's when you see a wrong parameter, which might not always be the case.
A simple global update option to upgrading an FME Package (i.e. Safe Emailer) rather than having to re-publish updated workflows.
PGPOINTCLOUD (PostGIS extension) is an open source project very interesting when dealing with a large amount point data in PostGIS. Compared to PostGIS multipoints format, we can use for each point as much dimension as we want, (PostGIS Multipoint is limited to 4 Dimensions). Another advantage is the data is compressed. I think this format is a relevant alternative of multipoint format in some cases.Here is the website for further information : https://pgpointcloud.github.io/pointcloud/We use this format to store and request the sounds in production from French Hydrographic Service, it works well. I would be very happy if FME could read and write directly to pgpointclouds.
As the title of this idea says, I would love to be able to rename incoming attributes within the readers themselves. I understand that the attribute renamer can be used directly after reading features for this same purpose, but it'd be great if we had the option to do it at the reader level as well.The why for this need:I work with several layers that are often imported into the same tools all at once. Most of these layers have attributes with the same names (County, St_Name, etc.), hence why it's important for me to be able to tell which layer each attribute comes from at a glance. Attribute renamers, removers, etc. do the trick, but it would be nice if I could remove the extra transformers and do it at the reader level.
Hi there,Currently the jpeg writer supports writing exif tags that are read in from the input data. Please add exif tag support to other raster writers as appropriate. I am specifically interested in tiffs, as with the new Cloud Optimised Geotiff format we want to transform our geotagged jpg's into COG's for ingestion into Esri Oriented Imagery Catalogs and streaming across the internet. This process is only possible if the images still have all the EXIF tags that they were captured with.Thanks,Marc
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.
