Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
The Aggregator transformer allows string attributes to be concatenated, which is great for generating separated lists. But if I have multiple identical input values, the list is less useful.An option to only add distinct values would be nice.
The Dynamic Workspace action in Auomations on FME Server allows you to run multiple workspace with the same parameters with the input from a FME Server Auomation Writer. Instead of using the FME Server Auomation Writer as input to the Dynamic Workspace, this should allow one to select multiple workspace from multiple repositories with same parameters, in an Auomation directly in a Dynamic Workspace Action. This makes it easier configure an Auomation Writer with the use of only one Action, instead of multiple actions for multiple workspaces.
When a ParameterFetcher (or AttributeCreator/Manager) is used to obtain the values of a "Choice (Multiple)" published parameter the result is a space-delimited string. However, when any of the published parameter choices contain spaces the values are wrapped in double quotes. If there are no spaces in the choice value then it is not wrapped in quotes. This makes extracting the actual chosen values problematic in an FME workspace.As an example, if my published parameter choice values are:'a a''b''c c'Then the ParameterFetcher would return an attribute with a string containing:"a a" b "c c"It is not a simple task to retrieve the individual choice values from this string. The AttributeSplitter will not work because the delimiter <space> can appear in the quoted strings. A simple regex is not easy to construct because not all values are quoted. The simplest solution seems to be a TCLCaller or PythonCaller but this is not easy for someone with limited programming experience.My idea suggestion is to make accessing these values easier. To do this I would propose two alternative solutions:wrap all values in quotes, even if they do not contain spaces, to make constructing a regex simpler;enhance the ParameterFetcher to return an FME list of the choice values.
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.
Three suggestions:Add non-geometry layers (wkb_none) support in the SpatiaLite reader so that both non-geometry and geometry features can be loaded using a single reader.Improve the mapping of SpatiaLite and FME data types in the SpatiaLite writer. VARCHAR(n) is not a SQLite native data type.Allow specifying a custom primary key in the SpatiaLite writer. Now FME adds OGC_FID.Support for SpatiaLite as a GeoPackage would be great.
1. Directory watch does not trigger topic when new folder is created in the directory unless you tell it to watch sub directories. I want to know when a new folder or sub directory is created within the directory, but do not want to monitor changes withing that sub directory.2. There is a bug where if you create a new folder or file within the directory and rename it, it will notify that the old document name has been deleted, but does not send a create or modify notification for the new document name.
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 option to get the number of features located in front of the tools arrows, FME Desktop 2022: Having an option to get the number of features located in front of the tools arrows,IIt would be great if the FME is enhanced to have an option to get the number of features located in front of the tool arrow is made available.Currently, the number that represents the features is placed at the middle of the line that’s connected between two tools. As per the screenshot below, in particular arrangement for the tools, it gets hidden if the fields are expanded, for example.This issue is already discussed here:FME Desktop 2020: How to get the number of features located in front of the tools arrows,https://community.safe.com/s/question/0D74Q000008sguL/detail?s1oid=00D30000000ePES&s1nid=0DB0c000000Gmzx&emkind=chatterBestAnswerNotification&s1uid=0054Q00000Ewv80&emtm=1642551543431&fromEmail=1&s1ext=0
***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
Hi,It would be awsome if it was possible to parameterize which interpreter to use. (store the settings in the fmw workspace) This would make FME much better to work with different python environments and it would be easy to work with different python virtual environments.
Add S3 Storage Class to the S3Connector. Right now it lands as Standard. Then we have to add a lifecycle rule to transition to S3 Intelligent-Tiering and then we can leverage our Intelligent-Tiering Archive configs.
Surprised this isn't a thing... Would sure be nice to have @DateTimeFormat support epoch Milliseconds instead of pushing it out to seconds and then having to multiply that by 1000.
Please add support for 'variance' column type to ODBC 3 driver. Or your next version of that driver.
I have been using the SnowFlake (spatial) writer now for some projects, and experience Snowflake to be quite picky when it comes to the geography it accepts...Not particular Safe Softwares problem, but while struggling I often enounteredIf you would like to continue loading when an error is encountered, use other values such as 'SKIP_FILE' or 'CONTINUE' for the ON_ERROR option. For more information on loading options, please run 'info loading_data' in a SQL client.after the error message generated by the copy-command (copy-ing the contence of a .gz file to the table).Could I please have some way of setting these ON_ERROR flags in the snowflake writer? Ofcourse aware of possible data corruption, I still would like them, if even only for debugging...Kind regards,Martin
When testing workspaces on FME Desktop I usually have many log messages turned on. When I publish them to FME Server I want to turn some of them off. When I go back again to developing I have to turn them on again on FME Desktop.Solutions:1. Add an option when pushint "Publish to FME Server" to change logging level when publishing a workspace - so you can keep the logging level you have on Desktop, and publish another loging level on the same workspace on FME Serveror2. Be able to change loging-level on workspaces through FME Server GUI
A Priority Attribute like in the AreaGapAndOverlapCleaner would be good for the anchor features. Use case is, there are many areas which have to be snapped to different line features with different priority.e.g. road has a higher priority than wall
The extent of the canvas begins limited to your screen area, and the normal way to expand that available area is to click and drag an item on the canvas out beyond the screen space.What if the canvas could also be expanded simply by panning and scrolling across the canvas?I like to work with the transformers always centre screen, because the space on the right is the space to develop, the space to think. I never want to be cramped against the canvas edge on the right of the screen without space to add more transformers. So when I start authoring a workspace I always drag an empty annotation far off to the bottom corner to expand the canvas to give me space to work with. That is a workaround, but it would be far simpler if the act of panning to the edge of the canvas would expand the canvas.Or, another way of solving this would be to make it that when you pan to the right edge of the canvas, the maximum panning extent should be reached when that canvas edge touches the left edge of the screen, instead of the right edge of the screen as it does currently. Then, adding new transformers in this state would be done past the edge of the canvas, which would automatically extend it same as it currently does. Limiting the panning extent in this way would also prevent a possible issue of new users panning around an infinite canvas unable to find their transformers.Example:
Manifold GIS is a software package that performs spatial data inspection and analysis. It's extremely lightweight and fast, taking advantage of GPGPU processing. Allowing FME to interact with Manifold directly as well as its .map files would be a huge advantage for many GIS analysts.
In the Alert section in FME Cloud, it is only possible to choose one email to notify if e.g. Primary Disk Usage above 90% for 10 minutes , but we often collaborate on projects and need to get notified as soon as possible even when a colleague is sick or not able to view his/hers mail. What about being able to choose several emails, or at least two, instead of making several alerts for the same notification, just so that more people can get the same notification.
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.
