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.
***Note from Migration:*** Original Title was: Ability to Set Attribute Order in AttributeExposer: Alphabetical vs. Default Order via Import It would be nice if the AttributeExposer could honor the sort order of attributes if they are imported via a CSV or other type of source. Currently the AttributeExposer defaults to put them in alphabetical order vs. honoring the order they we were listed in the CSV. Alternatively, if the CSV contains a separate attribute for 'sort order' could the AttributeExposer transformer use that to maintain the sort order? Maybe give the users a choice: Maintain Existing Order or Alphabetical? Manually moving attributes in AttributeManager or in the Writer seems like something a transformer should be able to do.
I recently received several .numbers files with data that I want to relate to points on a map using FME. I had to ask the sender to export them from her Mac as Excel or CSV. Fortunately, she was willing and able. This is the first time that I have received .numbers files, so I don't know if this is a larger problem for the community. For the current project, I anticipate receiving more data in this format.This from the web: "You can only open NUMBERS files with Apple Numbers in macOS and iOS. You can also upload NUMBERS files to the iCloud version of Numbers in your web browser (requires an Apple ID). This is helpful for Windows users who don't have access to the Mac or iOS versions of Numbers. In the iCloud application you can view, edit, save, and download NUMBERS files."
We need an Active Directory connection with group managed service account (gMSA).We can only use gMSA (for the "search account") to connect to the AD. Right now, FME Server supports only regular accounts. So, i cannot use our AD.That's the interesting point for me. Please support the gMSA in FME Server :-)
When using FME Desktop, the "Run" button is always enabled, allowing a user to potentially run a workspace at any time, and therefore overwrite data at any time. While the "Redirect to FME Data Inspector" option is available for Writers in a workspace, that does not disable all transformers, including Executors and FeatureWriters.This idea is proposing a "Disable Run" option for the entire workspace, allowing a user to toggle on/off the ability to run a workspace. An additional functionality is to allow an author to "Lock" the "Disable Run", therefore if the workspace is opened by a colleague (or other unauthorized user) the workspace will not run unless the enabled.
Integration frameworks like Make, Power Automate & Tray support the creation of webhooks when connecting to Online hosted feature services, FME should too, including managing them (events, frequency, payload URL etc). This should come to Portal too when it gets webhooks.
This thread outlines it pretty well:https://community.safe.com/s/question/0D54Q00009QoujHSAR/best-way-to-remove-fractional-seconds-in-date-timeCurrently if you want to drop the fractional component of seconds you need to do extra steps. This is fine, however, it feels like it would be neater it the DateTimeConverter/DateTimeFormat function could handle this. Just a nice to have really.
What happens on FME Server 2017 and later versions (Linux) - when FME_TEMP is out of free space during translation, FME Engines are just crashing with "ResourceManager: Optimizing Memory Usage. Please wait..." message. The message is quite confusing and we had to dug many days about the cause. I propose to change message so the user know exactly what happened: "FME TEMP is out of space, please reserve more free space in temporary directory" or something similar.BTW - Shouldn't the memory to FME_TEMP be dumped in a clever way to use only what's available and not crash?
Fonts like Fira Code (open source) make source code more readable by representing common character combinations with unified symbols. For example, == looks like a double-wide equals, -> looks like an arrow, >= looks like a standard mathematical greater-than-or-equal symbol. I already have support for fonts like this in my JetBrains editors, but it would be nice to also have it in the PythonCreator, PythonCaller, RCaller, and TclCaller transformers, as well as the scripted user parameter editor.
***Note from Migration:*** Original Title was: Autocad DWD/DXF Parameters allow Read ALL Paper Spaces beside of manually choosen ones When I read several DWG's, I don't know the names of all the Paper Spaces that may be there.I want to filter the viewports, or reading the Model Space Entities through viewports with Name starting with....When I read in all DWG's only with all Paper Spaces and without Model Space, then I can read in the right Paper Spaces with a second feature Reader.
The Group By option on transformers with several input ports is usually used with attributes which occur on both/all input ports.Can there be an option in the attribute selection window to only show attribute names that both input ports have in common?For instance, on the clipper, both the Clipper and the Clippee should contain the attribute I want to group on. So it would be great if I could display attributes that are existing on both input ports.
Okay, I know it's irrelevant to most people here,But this is a small idea, which can enhance the user experience for a many people!In Hebrew, as in other languages, we read and write from right to left.When I publish a server app for our clients, the title of the parameter is to the left of the box that needs to be filled.It makes perfect sense if the parameter was also written in English, but for our customers, we prefer the local language,So it creates confusion in the eyes.If there was such an option to set where we want the title of our parameters, it would be great!Thank you!
As a Python developer, I would like to be able to import an FME Python API package/module from a Python module on a machine with FME Desktop/Server installed and call any transformer that is present in the gallery.This would be similar to Esri ArcGIS Desktop arcpy package exposing all the geoprocessing tools from ArcToolbox.This would let streamline integration of FME and Python ecosystem!
It would be good if for AnchoredSnapper, a Snapping Tolerance could be an attribute? Currently it only accepts parameters. I understand why not for a Snapper - because everything might move around, but for an AnchoredSnapper, that's not a problem, the base doesn't move.The attribute could come from the "Candidate" (and only the candidate). Then each candidate can snap to a different tolerance to the base.
http://www.simplecloud.info/The System for Cross-domain Identity Management (SCIM) specification is designed to make managing user identities in cloud-based applications and services easier. The specification suite seeks to build upon experience with existing schemas and deployments, placing specific emphasis on simplicity of development and integration, while applying existing authentication, authorization, and privacy models. Its intent is to reduce the cost and complexity of user management operations by providing a common user schema and extension model, as well as binding documents to provide patterns for exchanging this schema using standard protocols. In essence: make it fast, cheap, and easy to move users in to, out of, and around the cloud.
GLTF 2.0 supports double sided material, however, even if a surfaces has a double-sided appearance in FME the output does data not honour this.For reference, here is the gltf specification the double-sided materials can be defined. https://www.khronos.org/registry/glTF/specs/2.0/glTF-2.0.html#double-sidedThis is of particular importance because it can be really difficult to correct incorrectly oriented surfaces - being able to create double sided materials can help to overcome this challenge.Here is an example workspace which shows the issue
Create an option for all raster transformer, to specify a template output grid. Basically ESRI's snap raster.
Hi,It would be great if run-time metrics of a Workbench are also part of a full FME Server Backup. This is especially important when these metrics (state) are used in the Engine Rulesets. Now when a backup is restored, the Engine Ruleset do not work the same as the runtime metrics are back to zero and thus cannot be used to determine the Engine.https://user-images.githubusercontent.com/8686001/153906648-e05aa4b5-0ae4-4520-8b33-547f3533d2f7.png
I don't know, this is an Idea or an error.Python Caller's error line number in the fme log, always +1for ex :if the error is in line number 10 and fme log says error in line 11.Please fix this issue in the next release. this has been there in many releases.
FME Server records the job information of the jobs that have been run, and usually a system cleanup task will remove these after some time. That's great for what has recently occurred. But in the scenario that you want to find if a workspace has been used over a long period of time, then you would have been required to store this information and long periods of time. So right now, I can't tell and will need to records these details for the foreseeable future.So I would like a new table in the FME database with an api call in front of it, that records the last date a workspace was run and maybe a couple of other fields such what ran it (e.g. an App, webhook etc) and what user. Over time this could be expanded, so it also said also recorded the last time a Server App was run, or when a token was run (especially as users often create tokens for a range of things and it is very hard for admin to confirm they are used)
Would be great if the internal "guts" of password protected custom transformers wouldn't be logged at all - even in debug.You should only see # features per input port and # features per output port (much like with regular transformers).
When working with an Oracle database you usually get the option to remove the table qualifier within the connection parameters (Reader, Writer). However, this option is missing within the Joiner transformer resulting in a minor inconsistency within your workspace. Could you include this option in the Joiner, too?
I routinely perform QA checks on ECW and GeoTIff files. When I use transformers like CoordinateSystemExtractor, it seems that FME gets confused by the presence of the sidecar files (.ers and .tab). I can check these via another work bench, text file reader, or a string transformer. But right now, to check only the ECW or GeoTiff files, I first have to move or delete thousands of side car files; these are often found in multiple directories, so this can take a long time. I think it would be a good idea for FME to include the option to ignore the sidecar files, either in the ECW/GeoTiff reader, or within the transformer settings.
Since FME 2018 there are Quick Filter options in the translation log (https://community.safe.com/s/bridea/a0r4Q00000HbrcEQAR/translation-log-quick-filter). This has been a great improvement, but I'm still missing a more general filter where you can type in any keyword like for example a transformer name, an attribute that is causing trouble, etc. and see only those messages in the log. Basically the same as in a job log in the FME Server
***Note from Migration:*** Original Title was: FME Desktop 2022: Having an equivalent tool to “spatial join” that’s available in ArcGIS, FME Desktop 2022: Having an equivalent tool to “spatial join” that’s available in ArcGIS,It would be great if the FME is enhanced to have a tool the is equivalent to “spatial join” available on ArcGIS.I’m aware that same functionalities are available in other tools in FME but no one single tool that has all these functionalities in one toolThis issue is already discussed here:FME 2020: How to pass the Blocks number to their Parcels?https://community.safe.com/s/question/0D54Q00008PqAo8SAF/fme-2020-how-to-pass-the-blocks-number-to-their-parcels
Running into this and it would be a lot cleaner if it was integrated into the Snipper transformer. See this Question
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.
