Reprojects a set of features to a local coordinate system with units of meters centered on the bounding box of the features.
This transformer is useful if you need a number of features reprojected into the same local coordinate system.
If attributes are not specified, all features will be reprojected to the same local coordinate system. If attributes are specified, each group of features will be reprojected to a local coordinate system centered on that group.
Note: How parallel processing works with FME: see About Parallel Processing for detailed information.
This parameter determines whether or not the transformer should perform the work across parallel processes. If it is enabled, a process will be launched for each group specified by the Group By parameter.
Parallel Processing Levels
For example, on a quad-core machine, minimal parallelism will result in two simultaneous FME processes. Extreme parallelism on an 8-core machine would result in 16 simultaneous processes.
You can experiment with this feature and view the information in the Windows Task Manager and the Workbench Log window.
No: This is the default behavior. Processing will only occur in this transformer once all input is present.
By Group: This transformer will process input groups in order. Changes of the value of the Group By parameter on the input stream will trigger batch processing on the currently accumulating group. This will improve overall speed if groups are large/complex, but could cause undesired behavior if input groups are not truly ordered.
Using Ordered input can provide performance gains in some scenarios, however, it is not always preferable, or even possible. Consider the following when using it, with both one- and two-input transformers.
Single Datasets/Feature Types: Are generally the optimal candidates for Ordered processing. If you know that the dataset is correctly ordered by the Group By attribute, using Input is Ordered By can improve performance, depending on the size and complexity of the data.
If the input is coming from a database, using ORDER BY in a SQL statement to have the database pre-order the data can be an extremely effective way to improve performance. Consider using a Database Readers with a SQL statement, or the SQLCreator transformer.
Multiple Datasets/Feature Types: Since all features matching a Group By value need to arrive before any features (of any feature type or dataset) belonging to the next group, using Ordering with multiple feature types is more complicated than processing a single feature type.
Multiple feature types and features from multiple datasets will not generally naturally occur in the correct order.
One approach is to send all features through a Sorter, sorting on the expected Group By attribute. The Sorter is a feature-holding transformer, collecting all input features, performing the sort, and then releasing them all. They can then be sent through an appropriate filter (TestFilter, AttributeFilter, GeometryFilter, or others), which are not feature-holding, and will release the features one at a time to the transformer using Input is Ordered By, now in the expected order.
The processing overhead of sorting and filtering may negate the performance gains you will get from using Input is Ordered By. In this case, using Group By without using Input is Ordered By may be the equivalent and simpler approach.
In all cases when using Input is Ordered By, if you are not sure that the incoming features are properly ordered, they should be sorted (if a single feature type), or sorted and then filtered (for more than one feature or geometry type).
As with many scenarios, testing different approaches in your workspace with your data is the only definitive way to identify performance gains.
Choose the local projection from the drop-down list based on whether preservation of distances or areas is more important. Choices are:
- AZMED (Lambert Azimuthal Equidistant)
- AZMEA (Lambert Azimuthal Equal Area)
This parameter determines how Z values will be handled:
- Ignore heights and leave them unchanged: Z values will not affect the reprojection and will not be changed.
Heights are relative to the ellipsoid or geocentric: Z values will be treated as ellipsoid heights with the same units as the horizontal units (or meters, for geographic coordinate systems). If the source coordinate system is geocentric, coordinates will be converted to geographic+ellipsoid height before being processed.
Note: Note that rasters can only be reprojected in 2D (that is, with Ignore heights and leave them unchanged).
Local coordinate systems have the following limitation:
- Height is not considered so areas or distances are best preserved for geometry at an ellipsoid height of 0 meters. Despite height not affecting the coordinate system that will be generated, Z values may undergo a unit shift or geocentric to ellipsoid height conversion if a Vertical Handling mode of Heights are relative to the ellipsoid or geocentric is chosen.
Editing Transformer Parameters
Using a set of menu options, transformer parameters can be assigned by referencing other elements in the workspace. More advanced functions, such as an advanced editor and an arithmetic editor, are also available in some transformers. To access a menu of these options, click beside the applicable parameter. For more information, see Transformer Parameter Menu Options.
Search FME Knowledge Center
Search for samples and information about this transformer on the FME Knowledge Center.