Open ideas have been reviewed by our Product Management and are open for commenting and voting.
It would be really useful if the Choice (multiple) and its "alias" counterpart parameters could output comma-separated strings at the user's request, rather than just space-separated. Useful for including in SQL-like IN tests without further manipulation
A useful addition to FME Desktop would be the use of a non-acting terminator - effectively just an indicator to show that you have considered the output port in question and have determined that there is no need to connect it to anything else or do anything else with it. This could be a small discrete symbol (diamond, stop sign, etc) in place of the right-pointing triangle or just the removal of the triangle itself.
Please create a parameter to allow the USA / Canadian grid transformation for NAD27/NAD83 to be defined at the workspace level.This article:https://docs.safe.com/fme/html/FME_Server_Documentation/AdminGuide/Configuring-Datum-Shifts.htmexplains various methods of configuring FME to work with USA and Canadian grid shift files. However, the company I'm working for routinely works with both USA and Canadian data, so it's not practical to set this value for all of FME. Rather than performing a manual CSMapReproject everywhere it's needed in the workspace, it would be great if it was possible to define the grid shift file to be used just once for an entire workspace, via a workspace parameter.
CUT and FILL volume calculation between Existing surface dem with Planned surface dem.
Certain characters are not allowed when creating files & folders in the OS. So if you pick data from some source and then use it to create files/folders without any validation, there's a good chance things will fail because of these special characters (see below for an example in Windows). It would be great to have a string function and transformer that will clean up a string to ensure it is compliant with these restrictions (maybe a way to also map to whether certain characters are just removed vs. replaced with a character such as an underscore, etc.). Currently this is doable with a series of nested ReplaceString or ReplaceRegEx functions for example, but not as easy to format each time you need to do this. This function & "cleaner" transformer would simplify such tasks and ensure you have no failures in your translations and data writing tasks.
ArcGIS Field Maps and Workforce support URL-driven app launching, see this topic. Workbench should be able to generate app links and then send them by email or other message.
Making the application available as Flatpak would offer the benefit of targeting many Linux operating systems and versions.
for an output table (in my case esri sde) could you add the option to "Truncate - Create if Needed" i seem to come across this need somewhat often
It would be nice to have a transformer that produces Plant UML sequence diagrams.The potential source could be :attribute or parameterfile/url orfme workbenchPlant UML uses plain text to generate proffesional looking sequence diagrams as well as other diagrams.
It would be nice to have an "open containing folder" button to open the log file folder similar to that available on the writer feature types.
Personally, I'm always a bit cautious when allowing workspaces to continue translation upon rejected features, since they might mess things up down the line in the workspace. I'd like to see a rejected feature handling on transformer level rather than just being able to set it for the whole workspace! Any workarounds/ideas/input? :)
It would be great if the "Run to this" / "Run from this" options within a workspace could be extended to have a "force run" or "rerun" option. Feature caching is fairly smart and will re-run stale caches when required. The problem is when an underlying dataset has changed and the feature caches aren't aware.For example, when using a FeatureReader or DatabaseJoiner, the underlying data may have changed and, currently, the only way to get the workspace to pick this up is to either re-run the entire workspace, or make a temporary edit in the workspace that causes the cached data to become stale.Another scenario in which this is an issue is if a custom transformer is updated, then the main workspace feature caches do not account for this unless the custom transformer interface changes.
***Note from Migration:*** Original Title was: Add a SQL Server Date format to @DateFormatter function and DateCalculator transformer Microsoft SQL Server (at least on 2012) only allows timestamps containing milliseconds (3 decimal places for fractional seconds) to be written to datetime and datetime2 columns. Dates generated by the @DateTimeNow() function automatically include nanoseconds (9 decimal places for fractional seconds). There is currently no way in the @DateTimeFormat function or DateCalculator transformer to only return milliseconds. Using either the "ISO" format shortcut, or using the %S flag always passes nanoseconds. One workaround I found was to wrap the @DateTimeNow() in a @Format() function like this: @DateTimeFormat(@Format(%.3f,@DateTimeNow()),ISO) to truncate the extra digits.I propose adding a "SQLServer" shortcut that returns the timestamp with only millisecond precision, and a flag of some sort that returns the seconds to millisecond precision.
Sometime a feature has an unacceptable set/combination of attributes, which means that the feature must be stopped from being output normally. If this is detected in AttributeManager, e.g. in a conditional value, there's no mechanism to block the feature. It has to be done using Testers before or after.If a "rejected" value could be set, and the action could be expanded to react on such a rejected value (or do it automatically) by either terminating the feature or outputting it via another port (e.g. <Rejected>), it would simplify the overall logic and minimize the clutter of transformers.Cheers
The FeatureReader provides an option to prefix _initiator_ attribute names when merging results. I would like an option to be able to prefix _result_ attribute names.
It can be cumbersome to write master/detail features using FME as you have to pay close attention to the order you write the features if there are foreign key constraints in the database. I propose giving the FeatureWriter a Group By option, where all the features in the same group (across all input ports) are written to the database inside a single transaction, when the output format allows it. It should also have the option "Input is ordered by group" to prevent the FeatureWriter from being blocking, whenever possible.This would solve the issue about writing master/detail features in a simple and intuitive way.
Ability to read and apply styler to a Bentley AecoSIM BXC file (format and styler). Currently can create 2D cells in dgn format from source (GIS) data however want capability to produce 3D format as well (compound cell). This way can establish one single data model from source data and output in 2D or 3D to use going forward. Also subsequent transformer to automate.
On a Mac, and only in FME 2019, if you right click and the mouse moves at all the first select of the dialog is picked. This is using a MagicMouse and I have gone through all forums (Mac and Safe) to see if there was some kind of fix. This was an issue before but appeared to have been fixed in 2018.1 but has now come back causing a lot of accidental cutting deleting inspecting. I have a VM on the same machine running in Windows and do not have the same issue.But congrats!!! The data inspector on cached data is BLAZING fast. ;)
Il would be nice to have a transformer that prevents any feature to pass before the rest of the workspace had run. It would behave as a disabled connection than becomes enabled once the rest of the workspace had run completely.
When FME server and license server are on the 1 x server machine, uninstalling FME server stops the license server. You have to manually start the license service again for desktop users
This post explains the issue in detail. Dates from FME Cloud are returned in UTC and you have to customize a workspace and associated functions to convert the time to the required zone. The handling of datetimes should be improved so the posted solutions (which I feel are a bit convoluted, especially the first one) are not required.
If merging datasets or use the StatisticsCalculator grouped by many attributes it would be great if there was an option on writers to remove empty attributes. Especcialy if the filename (or sheet name in Excel) is set by an attribute. In this cases ther can be many attributes in the written files that are empty.
I need to apply a merge cell to a series of cells in the excel writer. if the styler could do this that would be sufficient. It would be nice to be able to manually identify for instance O34:V34 and apply a value to that merged cell.ultimately if it could all the building of the cell range like O( _count+1):V(_count+1) so that it could always follow the data being written in the preceding rows.
Would be great to be about to output Dynamic blocks to AutoCAD, things like Visstate and Flip setting would be great, Distances for stretch, rotation and Alignment parameters might be a bit harder to achieve.
The AttributeValidator currently outputs the results in English. Since it is sometimes necessary to provide localized or custom messages, I suggest that the AttributeValidator include "message numbers" in addition to the full message, much like Oracle does with error messages (ORA-nnnn):Currently: Attribute 'abc' with value 'a' fails check for Type is 'INT'Suggested: Attribute 'abc' with value 'a' fails check for Type is 'INT' (FME-AV-1234)Where 1234 would be a unique integer that identifies the message.To translate, one could then search for FME-AV-nnnn rather than a specfic wording interspersed with attribute names etc.
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.
