Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
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
It would be really useful to be able to check how long an FME Cloud instance has been running since it was last started up from the paused state. Could a call be added to the FME Cloud API to either get the time the instance was started up or how long it has been running since it started?
I would really want to have Georeferencing possibilities in the FME AR app/FME AR Writer to be able to view planned and current objects in real life at 1:1 scale through mobile devices. That could range from existing plumbing to planned buildings. We have tried the FME AR app out and found we lack this functionality to find the app useful to us.
I have observed that data present in seed file of dgn file is not considered while writing the dgn file. Instead FME is extracting the file settings like units and writing the destination file.It is better to retain the data (i.e. lines, tags, so on) as it is. It will be like updating the dgn file with the data just like UPDATE CELLS option to Excel
Currently, when the page content is set to table, the user needs to manually choose all column's content and name. Really hope there is an import button to auto-import all upstream columns or import from CSV to speed up the process.
To be able to encode text strings into metaphone and soundex representations would be a useful addition to FME's capabilities, and would perhaps fits within the existing TextEncoder transformer.My use case is with regard to place names, specifically to aid checking that candidate new names do not clash phonetically with existing names.Thanks!
AGOL & ArcGIS Portal right now do not support .esrijson files as an item type. To share small/modest/moderate size static data Esri JSON is easily convertible to features, emailed, shared to a platform that doesn't speak Esri and so on. Reply with your user story here and we can get it coming!
Using the new compare and merge tool, it would be great if we select and "ignore" elements from the reference workspace, if we do not want to merge them. It would help to go through all steps of the merging process.
When right clicking an object on the workspace canvas, you could publish disable/enable as a parameter. Then you could control the flow of the workspace and Readers/Writers straight with published parameters, and I wouldn't need to use filter transformers.
As someone who uses the FME chat feature, it would be nice to be able to drag and drop pics and possibly files instead of the current attachment button. I understand you want to have control over what gets uploaded, but as a Google Chat user, this feature would greatly speed up communication.
FME Server currently supports Active Directory on premises. Is there a need to support Azure Active Directory as another user security solution?
FME need to be able to set precision control when writing point cloud data (xyz). Without precision control:435263.4 6036064.7 15.08435263.6 6036064.7 15.08435263.2 6036064.9 15.08435263.4 6036064.9 15.08435263.6 6036064.9 15.08435263 6036065.1 15.08435263.2 6036065.1 15.08Using precision control with 2 decimals:435263.40 6036064.70 15.08435263.60 6036064.70 15.08435263.20 6036064.90 15.08435263.40 6036064.90 15.08435263.60 6036064.90 15.08435263.00 6036065.10 15.08435263.20 6036065.10 15.08Since the point cloud writer is converting numeric values to string, one way to achivie this would be to control number of characters for X Y and Z. For example, easting value would be 6 integers followed be 2 decimals and 1 decimal point would correspond to 9 characters. So one string statement could be; If less than 2 then RightPad else leave as is..Best regardsAndré
I am hoping that you could start putting the version of FME that a function or transformer was first available in your documentation, tutorials and knowledge base articles on every page. Or a statement of "applies to version yyyy.x" to clarify.I'm often disappointed that the golden nugget of information that I have found isn't available to me due to our current version of FME Server. So, my idea is to put in brackets the FME version that the functionality first existed with perhaps a dash followed by the FME version this particular item applies to. In a perfect world we would all be using the most recent version of FME possible, but that isn't the reality, especially for us. We are currently on FME Server 2019. All, I'm really looking for is the version of when the ability was first available. For example, I was looking for information on SFTP and found documentation on SFTP Directory. I had to navigate all the way to the top of the documentation to find out that I was looking at 2022 documentation. But that still doesn't tell me when that was first available and whether that is available to me in 2019.
When having a big workspace running, for the most of the the workspace components I wouldn't need detailed logging, just errors and warnings. But for some transformers, readers or writers I'd need very detailed logging (not just errors but all possible information for debugging).At the moment there's no separate logging settings for individual components of a workspace.
Providing 3D models of technical data (in our case geological) publically is increasing so it would be great for us to be able to do all our data transformations within one FME job. Currently we read our data in FME as .obj files to do coordinate transformations but then need to save the output of this in other software to generate GOCAD files. Our current range of file formats for public 3D data downloads is dxf, GOCAD & Leapfrog Viewer.
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.
