Select Tools > FME Options > Workspace Defaults.
Tolerance when Stroking Geometry
FME uses this setting whenever arcs need be stroked into lines to make sure the distance between the resulting line and the true mathematical arc is never more than the value specified. For more information about how arc stroking works, see Stroking Tolerance.
When you update this setting, it affects stroking tolerance for all new workspaces. To update stroking tolerance on previous workspaces, or to apply a different setting on individual workspaces, see Stroking Tolerance.
Rejected Feature Handling Default
Specifies the default behavior of newly-created workspaces with transformers that contain <Rejected> output ports, and a translation outputs a feature to one of these ports.
- Terminate Translation: The translation terminates when the first feature is output to a <Rejected> port that does not connect to another input port.
- Continue Translation: The translation continues to run regardless of any features output to a <Rejected> port.
Specifies the requirements for a workspace equipped with any format that requires an Esri ArcGIS license. This setting controls the default setting of the Esri ArcGIS Compatibility workspace parameter setting.
- Auto (default): If required, Esri ArcMap, Esri ArcGIS Pro, or equivalent must be installed and licensed on the system.
- Esri ArcMap: Esri ArcMap or equivalent must be installed and licensed on the system.
- Esri ArcGIS Pro: Esri ArcGIS Pro or equivalent must be installed and licensed on the system.
Max Features to Log
To prevent the accidental creation of extremely large log files, FME controls the number of features that may be logged during an FME session.
FME logs features found to be invalid during translation so, for example, if a bad input data file is encountered, or if you inadvertently route lines through a cell feature, FME can literally log thousands of features and a log file several megabytes in size may result.
The value of this setting imposes a limit on the number of features that can be logged during a translation. This prevents excessively large log files from being inadvertently generated. Any features beyond the set limit are not logged at all. A statistic is output at the end of the log that states the number of suppressed features that were not logged.
To remove this limit and log all features, select All Features.
To control this setting for individual workspaces, see Max Features to Log.
Max Features to Record
Any feature that is recorded in the log window (or file) will also get written to an FFS log dataset. This dataset takes the same name as the log file but with “_log” added and an FFS extension.
This setting determines the number of features that will get written to this log dataset.
It’s important to be aware that the log feature maximums apply an overall cap to accumulated log totals. For example, three Logger transformers each have a limit of 10 features to log, giving a theoretical maximum of 30 features. However, the “Max Features to Log” setting will restrict the overall total; for example, if set to 10, then it will restrict the theoretical maximum from 30 to 10.
You should also note that these settings affect not just manually logged features – using the Logger for example – but also features that are logged for another reason. For example, text features rejected by the AreaBuilder are logged in this way, and their logging affected by these logging maximums.
To control this setting for individual workspaces, see Max Logged Features to Record.