Produces a raster digital elevation model (DEM) by uniformly sampling a Delaunay triangulation generated from input points and breaklines.
Typical Uses
- Creating raster elevation models from non-gridded features such as contours or point clouds.
How does it work?
The RasterDEMGenerator receives input features, triangulates a surface based on them, and then outputs a raster DEM with elevation values sampled from the surface at a specified regular interval. The output raster will contain a single numeric band, of the interpretation type Real64.
The input features are discarded.
Input features can be of a variety of types, including points, lines, areas, rasters, and point clouds. Aggregate geometries are supported, and multiple input features and types may be combined to produce one raster DEM output feature.
There are two input ports - Points/Lines and Breaklines. At least one input feature must be provided, which may be routed into either of these ports.
Input features may be either 2D or 3D - however, 2D features will be forced to 3D with an elevation (z value) of zero (0). If the source dataset’s z values are not stored as z coordinates (for example, contours with elevation stored as an attribute), a 3DForcer transformer may be used to convert them to a z coordinate prior to entering the RasterDEMGenerator.
A choice of interpolation methods is available. Surface tolerance and cell spacing may be adjusted, and a nodata value may be defined.
This transformer is unaffected by raster band and palette selection.
Example: Generating a raster DEM from contours with an elevation attribute
In this example, we will generate a DEM from a set of contour lines, spaced at a ten meter interval. Note that the source data does not have elevation values as a z coordinate - though it is a 3D dataset, the z values are all zero (0).
The elevation values are stored as an attribute, named ELEVATION, and so need to be applied as z values before the DEM is generated.
The contours are routed first into a 3DForcer, and then to the RasterDEMGenerator.
In the 3DForcer parameters dialog, Elevation is set to the ELEVATION attribute, and Preserve Existing Z Values is set to No. The attribute values will overwrite the existing z values.
Next, in the RasterDEMGenerator’s parameters dialog, we set Surface Tolerance to zero (0), which means that no vertex filtering will take place, and all points will be considered.
Cell Spacing (both X and Y) is set to 10. The output cells will be 10 meters square, as the source data’s coordinate system is in meters.
The default Interpolation Method and Nodata Value are left as is.
The output DEM raster has a single Real64 band, 10 meter square cells, and the specified nodata value.
Usage Notes
- If input features’ elevation values are not stored as Z coordinates, use a 3DForcer prior to the RasterDEMGenerator.
- To produce individual elevation points instead of a raster, consider using the DEMGenerator.
- When processing large input datasets, increasing the Surface Tolerance may provide performance gains, but may reduce accuracy.
- For more complex elevation modelling tasks, such as including contour generation, accessing components of the underlying surface model, feature draping, or creating multiple representations of a surface model, consider using the SurfaceModeller.
Choosing a Raster Transformer
FME has an extensive selection of transformers for working with raster data. They can be generally categorized as working with whole rasters, bands, cells or palettes, and those designed for workflow control or combing raster with vector data.
For information on raster geometry and properties, see Rasters (IFMERaster).
Raster Transformers
Working with Rasters
These transformers generally apply to whole rasters.
| RasterCellOriginSetter | Sets the cell origin point within cells in a raster. |
| RasterConvolver |
Applies a convolution filter (sometimes called a kernel or lens) to raster features and outputs the results. |
| RasterExpressionEvaluator | Evaluates expressions on each cell in a raster or pair of rasters, including algebraic operations and conditional statements. |
| RasterExtentsCoercer | Replaces the geometry of input raster features with a polygon covering either the extents of a raster or the extent of data within a raster. |
| RasterGCPExtractor | Extracts Ground Control Point (GCP) coordinate system and point values from a raster feature and exposes them as attributes. |
| RasterGCPSetter | Sets Ground Control Points (GCPs) on a raster, pairing cell positions with known coordinates. |
| RasterGeoreferencer | Georeferences a raster by either known corner coordinates or origin, cell size, and rotation. |
| RasterHillshader | Generates a grayscale shaded relief representation of terrain, based on elevation values. |
| RasterInterpretationCoercer |
Alters the interpretation type of rasters, including all bands, and converts cell values if necessary. |
| RasterMosaicker | Merges multiple raster features into a single raster feature. |
| RasterPropertyExtractor | Extracts the geometry properties of a raster feature and exposes them as attributes. |
| RasterPyramider | Resamples rasters to multiple resolutions, based on either number of levels or dimensions of the smallest output raster. |
| RasterResampler | Resamples rasters, based on specified output dimensions, cell size in ground units, or percentage of original, and interpolates new cell values. |
| RasterRotationApplier |
Rotates a raster feature according to its rotation angle property, interpolating new cell values, updating all other affected raster properties, and producing an output raster feature with a rotation angle of zero. |
| RasterSubsetter | Clips raster features using pixel bounds instead of ground coordinates, and optionally adds cells around the perimeter. |
| RasterTiler | Splits each input raster into a series of tiles by specifying either a tile size in cells/pixels or the number of tiles. |
| RasterToPolygonCoercer | Creates polygons from input raster features. One polygon is output for each contiguous area of pixels with the same value in the input raster. |
| WebMapTiler | Creates a series of image tiles that can be utilized by web mapping applications such as Bing™ Maps, Google Maps™, or Web Map Tile Service. This is done by resampling rasters to various different resolutions and then splitting them into tiles. |
Working with Bands
These transformers generally apply to bands.
| RasterBandAdder | Adds a new band to a raster feature. |
| RasterBandCombiner | Merges coincidental raster features into a single output raster feature, preserving and appending all bands. |
| RasterBandInterpretationCoercer |
Alters the interpretation type of individual raster bands, converting cell values if necessary. |
| RasterBandKeeper |
Removes all unselected bands from a raster feature. |
| RasterBandMinMaxExtractor | Extracts the minimum and maximum band values, palette keys, and palette values from a raster feature, and adds them to a list attribute. |
| RasterBandNameSetter | Sets the band name of selected bands on a raster, making raster contents simpler to understand compared to band numbers. |
| RasterBandNodataRemover | Removes the existing nodata identifier from selected bands of a raster feature. Any values previously equal to the nodata value are considered valid data. |
| RasterBandNodataSetter | Sets a new nodata value on selected bands of a raster feature. |
| RasterBandOrderer | Specifies the required order of bands in a raster. Bands are reordered according to the input band indices. |
| RasterBandPropertyExtractor | Extracts the band and palette properties of a raster feature and exposes them as attributes. |
| RasterBandRemover | Removes any selected bands from a raster feature. |
| RasterBandSeparator | Separates bands or unique band and palette combinations, and outputs either individual raster features or a single new raster feature containing all combinations. |
| RasterStatisticsCalculator | Calculates statistics on raster bands and adds the results as attributes. |
Working with Cells
These transformers generally apply to individual cells.
| RasterAspectCalculator |
Calculates the aspect (direction of slope) for each cell of a raster. Aspect is measured in degrees from 0 to 360, clockwise from north. |
| RasterCellCoercer | Creates individual points or polygons for each cell in a raster, optionally extracting band values as z coordinates or attributes. |
| RasterCellValueCalculator | Evaluates basic arithmetic , minimum, maximum or average operations on the cell values of a pair of rasters. |
| RasterCellValueReplacer | Replaces a range of band values in a raster with a new single value. |
| RasterCellValueRounder | Rounds off raster cell values. |
| RasterSingularCellValueCalculator | Performs basic arithmetic operations on the cell values of a raster against a numeric value. |
| RasterSlopeCalculator | Calculates the slope (maximum rate of change in z) for each cell of a raster. |
Working with Palettes
These transformers generally apply to palettes.
| RasterPaletteAdder |
Creates a palette from an attribute, and adds this palette to all selected bands on a raster. |
| RasterPaletteExtractor | Creates a string representation of an existing palette on a raster and saves it to an attribute. |
| RasterPaletteGenerator | Generates a palette out of the selected band(s) of a raster. The output raster will have the selected band(s) replaced by a new band with a palette. |
| RasterPaletteInterpretationCoercer |
Alters the interpretation type of raster palettes. |
| RasterPaletteNodataSetter |
Identifies the palette key that matches a raster band’s nodata value, and sets a value on it. |
| RasterPaletteRemover | Removes selected palette(s) from raster features. |
| RasterPaletteResolver | Resolves the palette(s) on a raster by replacing cell values with their corresponding palette values. Palette values with multiple components, such as RGB, are broken down and the individual values assigned to multiple, newly-added bands. |
Workflow Control
These transformers generally control the flow of features in a workspace.
| RasterCheckpointer | Forces accumulated raster operations to be processed, saving the state to disk and releasing resources to tune performance or assist with memory limitations. |
| RasterConsumer | Reads raster features for testing purposes, including any accumulated raster operations. No additional operations are performed, and nothing is done with the features. |
| RasterExtractor | Serializes the geometry of a raster feature into a Blob attribute, encoding the contents according to a choice of common binary raster formats. |
| RasterNumericCreator | Creates a numeric raster of specified size and resolution, with default cell values. |
| RasterReplacer | Decodes a binary attribute containing encoded rasters stored as Blobs, replacing the feature’s geometry with the decoded raster. |
| RasterRGBCreator | Creates a color raster feature of specified size, resolution, and interpretation type, with default cell values. |
| RasterSelector |
Selects specific bands and palettes of a raster for subsequent transformer operations. |
Vectors and Rasters
These transformers generally involve using rasters and vector data together.
| ImageRasterizer | Creates a raster representation of vector or point cloud input features, using the fme_color attribute over a solid background fill for vector features. Point clouds may be rendered using their color or intensity components. |
| NumericRasterizer | Creates a numeric raster representation of vector or point cloud input features, where cell values are taken from the z coordinates of the input features and overlaid on a uniform background. |
| MapnikRasterizer | Generates a raster from input vector and raster features, with fine control over symbolization and labeling, using the Mapnik toolkit. |
| PointOnRasterValueExtractor | Extracts the band and palette values from a raster at the location of one or more input points and sets them as attributes on the feature. |
| RasterDEMGenerator | Produces a raster digital elevation model (DEM) by uniformly sampling a Delaunay triangulation generated from input points and breaklines. |
| VectorOnRasterOverlayer | Rasterizes vector or point cloud features onto an existing raster. For vector features the fme_color attribute sets pixel color, and point clouds may be rendered using their color or intensity components. |
Configuration
Input Ports
Points/Lines
These input features may be 2D or 3D. Other than points, lines and area geometries, they may also be raster, point cloud, and aggregate geometries.
2D features will be forced to 3D by adding a z value of 0. In most cases, all points extracted from this port will be found in the vertex pool of the underlying surface model. A minimum of 3 unique points are required to construct a surface model. Points with duplicate x and y values will be dropped.
Breaklines
These input features may be 2D or 3D, and may reside inside an aggregate structure.
2D features will be forced to 3D by adding a z value of 0. Breakline edges will be found in the edge pool of the underlying surface model. Sometimes, a breakline edge will be split up to allow an optimal triangulation of the surface model. Points with duplicate x and y values will be dropped.
Output Ports
DEMRaster
This output port samples the underlying surface model according to the sampling rates specified in Output DEM X Cell Spacing, and Output DEM Y Cell Spacing, and produces a single raster feature consisting of evenly spaced 3D points arranged by rows and columns.
<Rejected>
Invalid input features will be routed to the <Rejected> port.
Rejected features will have an fme_rejection_code attribute with one of the following values:
INVALID_POINT_GEOMETRY_VERTICES
INVALID_BREAKLINES_GEOMETRY_VERTICES
INVALID_GEOMETRY_VERTICES
INVALID_POINTS_GEOMETRY_RASTER_NUM_BANDS
INVALID_POINTS_GEOMETRY_RASTER_NUM_PALETTES
INVALID_GEOMETRY_DIMENSION
Rejected Feature Handling: can be set to either terminate the translation or continue running when it encounters a rejected feature. This setting is available both as a default FME option and as a workspace parameter.
Parameters
Transformer
| Group By |
This parameter allows groups to be formed by attribute values. Zero or more attributes may be specified. Input features with the same attribute values are placed into the same group. The transformer then operates independently on each group of input features. If this parameter is left blank, the transformer will treat the entire set of input features as one group. |
| Group By Mode |
Process At End (Blocking): This is the default behavior. Processing will only occur in this transformer once all input is present. Process When Group Changes (Advanced): This transformer will process input groups in order. Changes of the value of the Group By parameter on the input stream will trigger processing on the currently accumulating group. This may improve overall speed (particularly with multiple, equally-sized groups), but could cause undesired behavior if input groups are not truly ordered. Considerations for Using Group By
There are two typical reasons for using Process When Group Changes (Advanced) . The first is incoming data that is intended to be processed in groups (and is already so ordered). In this case, the structure dictates Group By usage - not performance considerations. The second possible reason is potential performance gains. Performance gains are most likely when the data is already sorted (or read using a SQL ORDER BY statement) since less work is required of FME. If the data needs ordering, it can be sorted in the workspace (though the added processing overhead may negate any gains). Sorting becomes more difficult according to the number of data streams. Multiple streams of data could be almost impossible to sort into the correct order, 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. In this case, using Group By with Process At End (Blocking) may be the equivalent and simpler approach. Note: Multiple feature types and features from multiple datasets will not generally naturally occur in the correct order. As with many scenarios, testing different approaches in your workspace with your data is the only definitive way to identify performance gains. |
Parameters
| Surface Tolerance |
This parameter is used to determine which input points to add to the surface model as vertices. Specifying a value of 0 turns off vertex filtering. Tip: A larger value will speed up surface model construction. The larger the value, the more input points will be filtered out. For input files with millions – or even billions – of points, it becomes essential to increase this value. When a positive value for surface tolerance is specified, it works as follows. For each vertex that is being added to the model:
|
| Interpolation Method |
This parameter is used for the output ports DEMPoints and DEMRaster when these output ports exist on the transformer. It is also used if DrapeFeatures are input to the model.
|
| Output DEM X Cell Spacing
Output DEM Y Cell Spacing |
These parameters specify the x and y sampling intervals for the output DEMPoints. |
| Output DEM Raster Nodata Value |
This parameter is used only when Interpolation Method is set to PLANAR, and it only affects the output port DEMRaster. All output raster cells that fall outside the underlying surface model’s boundaries will be assigned the value of this parameter. When this parameter is blank, it is interpreted as NaN (Not a Number). Note: To ensure consistent raster output, it is highly recommended that you do not leave this parameter blank. |
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.
Defining Values
There are several ways to define a value for use in a Transformer. The simplest is to simply type in a value or string, which can include functions of various types such as attribute references, math and string functions, and workspace parameters. There are a number of tools and shortcuts that can assist in constructing values, generally available from the drop-down context menu adjacent to the value field.
How to Set Parameter Values
Using the Text Editor
The Text Editor provides a convenient way to construct text strings (including regular expressions) from various data sources, such as attributes, parameters, and constants, where the result is used directly inside a parameter.
Using the Arithmetic Editor
The Arithmetic Editor provides a convenient way to construct math expressions from various data sources, such as attributes, parameters, and feature functions, where the result is used directly inside a parameter.
Conditional Values
Set values depending on one or more test conditions that either pass or fail.
Parameter Condition Definition Dialog
Content
Expressions and strings can include a number of functions, characters, parameters, and more - whether entered directly in a parameter or constructed using one of the editors.
Content Types
| These functions manipulate and format strings. | |
| A set of control characters is available in the Text Editor. | |
| Math functions are available in both editors. | |
| These operators are available in the Arithmetic Editor. | |
| These return primarily feature-specific values. | |
| FME and workspace-specific parameters may be used. | |
| Working with User Parameters | Create your own editable parameters. |
Reference
|
Processing Behavior |
|
|
Feature Holding |
Yes |
| Dependencies | None |
| FME Licensing Level | FME Professional Edition and above |
| Aliases | DEMGridGenerator |
| History | This transformer was previously named DEMGridGenerator. |
| Categories |
FME Community
The FME Community is the place for demos, how-tos, articles, FAQs, and more. Get answers to your questions, learn from other users, and suggest, vote, and comment on new features.
Search for all results about the RasterDEMGenerator on the FME Community.
Examples may contain information licensed under the Open Government Licence – Vancouver