the elevation of the ground and land cover directly below the route (the colors depend on the type of land cover),

a road line at the point where it intersects the route,

water polygons and airspace polygons where they intersect the route.

the 3D points inside the buffer zone,

the airspace polygons where they intersect the buffer zone,

the water names that are attached to points inside the buffer zone.

the roads appear as lines, where they intersect the buffer zone,

the ground and trees show the highest elevation along a line perpendicular to the route within the buffer zone.

Point. A 3D point from ElevationInput, within MaxDistance from the fence, will normally generate a corresponding point on the fence surface, with the height taken from the z coordinate of the 3D point. More generally, the 3D point can be interpreted as having a vertical extent from a minimal to a maximal elevation. The minimal elevation is then specified via the BottomElevation that can depend on the 3D point attributes, but if this evaluates to its default value, the minimal elevation will be the z coordinate. The maximal elevation is specified via TopElevation in the same way. If the minimal elevation differs from the maximal one, the output feature will be a vertical line instead of a point.

Line. A 3D line from ElevationInput will first be clipped by a buffer zone that extends MaxDistance horizontally from the fence. Only the line parts that are inside the buffer zone will generate output lines. If the MaxDistance is zero, then clipped parts are usually just the points where the 3D line intersects the fence, so the output will be points instead of lines, although a 3D line that coincides with a part of the fence can still generate output lines. Normally, the z coordinate of each node in the input line is used as the elevation of the corresponding node in the output feature. However, as for input point features, it is possible to fetch a minimal and/or a maximal elevation for each input line from its attributes; if this is done, the output features will be polygons that extend down to the bottom elevation, and/or up to the top elevation (or, if MaxDistance is zero and the 3D line passes through the fence, the output can be a vertical line segment).

Polygon. For a polygon feature, it is seldom useful to have a distinct elevation (z coordinate) at each node, since it would be ambiguous how to interpolate the elevation in the interior. In aeronautics, one uses 3D volumes known as airspaces, whose horizontal extent is given by a 2D polygon while the vertical extent is given by two numbers: the lower and upper vertical limits. The VerticalProfileOperator assumes that each polygon feature from ElevationInput has a lower and an upper limit that can be retrieved via BottomElevation and TopElevation. In the unlikely case that these are evaluated to their absurd default, the lower (or upper) limit is instead taken from the smallest (or largest) z coordinate of the polygon. When the lower and upper limits are known, the polygon is clipped by the buffer zone that extends MaxDistance horizontally from the fence. Each remaining part generates a rectangular polygon feature in the output.

Elevation raster. A raster of ground elevations will generate a line on the fence, normally where the fence touches the ground. If Close is True, the raster will also generate a polygon below the ground level (or above the ground, if ClosingHeight is higher than the ground). Raster cells within MaxDistance from the fence can also affect the result. Note that input rasters that describe land cover are handled in a special way; see LandCoverInput.

Volume-encoding rasters. Apart from vector data and ordinary elevation rasters, the ElevationInput can also give the special volume-encoding rasters that can be produced by a LineOfSightOperator or an AirspaceCoverageOperator and represent viewshed volumes. The results from these will always be polygon features representing where the fence cuts through the volumes.

The route itself. When the route represents a 3D flight route, you can get an output line that corresponds to the route by letting OutputRoute be True. An alternative way would be to make the route appear also as an input feature from ElevationInput, but this would be less efficient. However, the alternative can be used if each segment of the route has its own set of attributes that should affect the output; maintaining the different sets of attributes would then require that each route segment appears as a separate input feature from ElevationInput. Of course, another possibility is to use some application code to calculate how the route segments shall appear in the profile View, and then store the results in a MemoryDataSet, whose features can be sent to the profile View without passing through a VerticalProfileOperator.

Coordinates. The coordinates of the output features are defined in a coordinate system that is 2D but vertical; it is the same Crs as the one used by the View, and it is normally the Crs.NonGeoreferenced. The x coordinates of the output give horizontal distance along the fence, with zero at the start of the fence (first point of the route). The y coordinates of the output give elevation, so they normally correspond to the z coordinates of 3D points and 3D lines, and to the cell values of rasters. However, some of the y coordinates of the output can come from the BottomElevation and TopElevation that are evaluated for each input vector feature from ElevationInput.

Attributes. The output attributes are copied from the original input features, except the geoType.

• vpopSourceGeoType. The geoType value for an input feature (#raster, #line, #point or #polygon) is copied to a new attribute vpopSourceGeoType for the corresponding output feature(s). (The geoType attribute of an output feature must tell whether the output feature itself is a point, line, or polygon.) A special case occurs when outputRoute is True, which will transform the route into an output line with a vpopSourceGeoType that is #routeLine.

• vpopLandCoverCode. If the LandCoverInput and LandCoverHeightInput are used to get land-cover raster data, the operator will generate land-cover features for forest, shrubs, cities, etc. These features will be lines and polygons that stand on top of the ground profile feature. Each land cover feature will get an integer attribute vpopLandCoverCode, containing the raster cell value that represented the type of land cover. For example, 42 could represent "Evergreen Forest".

• vpopDistanceToRoute. Each output feature will also get a new attribute vpopDistanceToRoute, expressed in meters.

  • If the original input feature was a 3D point, the value will be its horizontal distance to the fence. The value is a signed number, with positive numbers meaning left of the fence (walking along the fence in the order of the points in the route).

  • If the original input feature was a raster, the attribute value will be zero.

  • If the original input feature was a line or polygon, it can have some parts that are close enough to the route to generate output, while other parts are too far away (farther than MaxDistance). This means that a single line or polygon can generate several output features, which will each have their own value for vpopDistanceToRoute, expressing the minimal horizontal distance from the part to the route. The value is signed, and a positive number means left of the fence.

• Attributes giving highest terrain points. These attributes have become obsolete since the VerticalClearanceOperator is easier to use, but they are documented at Elevation Attributes in a Vertical Profile.

the elevation of the ground and land cover directly below the route (the colors depend on the type of land cover),

a road line at the point where it intersects the route,

water polygons and airspace polygons where they intersect the route.

the 3D points inside the buffer zone,

the airspace polygons where they intersect the buffer zone,

the water names that are attached to points inside the buffer zone.

the roads appear as lines, where they intersect the buffer zone,

the ground and trees show the highest elevation along a line perpendicular to the route within the buffer zone.

Point. A 3D point from elevationInput, within maxDistance from the fence, will normally generate a corresponding point on the fence surface, with the height taken from the z coordinate of the 3D point. More generally, the 3D point can be interpreted as having a vertical extent from a minimal to a maximal elevation. The minimal elevation is then specified via the bottomElevation that can depend on the 3D point attributes, but if this evaluates to its default value, the minimal elevation will be the z coordinate. The maximal elevation is specified via topElevation in the same way. If the minimal elevation differs from the maximal one, the output feature will be a vertical line instead of a point.

Line. A 3D line from elevationInput will first be clipped by a buffer zone that extends maxDistance horizontally from the fence. Only the line parts that are inside the buffer zone will generate output lines. If the maxDistance is zero, then clipped parts are usually just the points where the 3D line intersects the fence, so the output will be points instead of lines, although a 3D line that coincides with a part of the fence can still generate output lines. Normally, the z coordinate of each node in the input line is used as the elevation of the corresponding node in the output feature. However, as for input point features, it is possible to fetch a minimal and/or a maximal elevation for each input line from its attributes; if this is done, the output features will be polygons that extend down to the bottom elevation, and/or up to the top elevation (or, if maxDistance is zero and the 3D line passes through the fence, the output can be a vertical line segment).

Polygon. For a polygon feature, it is seldom useful to have a distinct elevation (z coordinate) at each node, since it would be ambiguous how to interpolate the elevation in the interior. In aeronautics, one uses 3D volumes known as airspaces, whose horizontal extent is given by a 2D polygon while the vertical extent is given by two numbers: the lower and upper vertical limits. The VerticalProfileOperator assumes that each polygon feature from elevationInput has a lower and an upper limit that can be retrieved via bottomElevation and topElevation. In the unlikely case that these are evaluated to their absurd default, the lower (or upper) limit is instead taken from the smallest (or largest) z coordinate of the polygon. When the lower and upper limits are known, the polygon is clipped by the buffer zone that extends maxDistance horizontally from the fence. Each remaining part generates a rectangular polygon feature in the output.

Elevation raster. A raster of ground elevations will generate a line on the fence, normally where the fence touches the ground. If close is True, the raster will also generate a polygon below the ground level (or above the ground, if closingHeight is higher than the ground). Raster cells within maxDistance from the fence can also affect the result. Note that input rasters that describe land cover are handled in a special way; see landCoverInput.

Volume-encoding rasters. Apart from vector data and ordinary elevation rasters, the elevationInput can also give the special volume-encoding rasters that can be produced by a LineOfSightOperator or an AirspaceCoverageOperator and represent viewshed volumes. The results from these will always be polygon features representing where the fence cuts through the volumes.

The route itself. When the route represents a 3D flight route, you can get an output line that corresponds to the route by letting outputRoute be True. An alternative way would be to make the route appear also as an input feature from elevationInput, but this would be less efficient. However, the alternative can be used if each segment of the route has its own set of attributes that should affect the output; maintaining the different sets of attributes would then require that each route segment appears as a separate input feature from elevationInput. Of course, another possibility is to use some application code to calculate how the route segments shall appear in the profile View, and then store the results in a MemoryDataSet, whose features can be sent to the profile View without passing through a VerticalProfileOperator.

Coordinates. The coordinates of the output features are defined in a coordinate system that is 2D but vertical; it is the same Crs as the one used by the View, and it is normally the Crs::nonGeoreferenced. The x coordinates of the output give horizontal distance along the fence, with zero at the start of the fence (first point of the route). The y coordinates of the output give elevation, so they normally correspond to the z coordinates of 3D points and 3D lines, and to the cell values of rasters. However, some of the y coordinates of the output can come from the bottomElevation and topElevation that are evaluated for each input vector feature from elevationInput.

Attributes. The output attributes are copied from the original input features, except the geoType.

• vpopSourceGeoType. The geoType value for an input feature (#raster, #line, #point or #polygon) is copied to a new attribute vpopSourceGeoType for the corresponding output feature(s). (The geoType attribute of an output feature must tell whether the output feature itself is a point, line, or polygon.) A special case occurs when outputRoute is True, which will transform the route into an output line with a vpopSourceGeoType that is #routeLine.

• vpopLandCoverCode. If the landCoverInput and landCoverHeightInput are used to get land-cover raster data, the operator will generate land-cover features for forest, shrubs, cities, etc. These features will be lines and polygons that stand on top of the ground profile feature. Each land cover feature will get an integer attribute vpopLandCoverCode, containing the raster cell value that represented the type of land cover. For example, 42 could represent "Evergreen Forest".

• vpopDistanceToRoute. Each output feature will also get a new attribute vpopDistanceToRoute, expressed in meters.

  • If the original input feature was a 3D point, the value will be its horizontal distance to the fence. The value is a signed number, with positive numbers meaning left of the fence (walking along the fence in the order of the points in the route).

  • If the original input feature was a raster, the attribute value will be zero.

  • If the original input feature was a line or polygon, it can have some parts that are close enough to the route to generate output, while other parts are too far away (farther than maxDistance). This means that a single line or polygon can generate several output features, which will each have their own value for vpopDistanceToRoute, expressing the minimal horizontal distance from the part to the route. The value is signed, and a positive number means left of the fence.

• Attributes giving highest terrain points. These attributes have become obsolete since the VerticalClearanceOperator is easier to use, but they are documented at Elevation Attributes in a Vertical Profile.

the elevation of the ground and land cover directly below the route (the colors depend on the type of land cover),

a road line at the point where it intersects the route,

water polygons and airspace polygons where they intersect the route.

the 3D points inside the buffer zone,

the airspace polygons where they intersect the buffer zone,

the water names that are attached to points inside the buffer zone.

the roads appear as lines, where they intersect the buffer zone,

the ground and trees show the highest elevation along a line perpendicular to the route within the buffer zone.

Point. A 3D point from elevationInput, within maxDistance from the fence, will normally generate a corresponding point on the fence surface, with the height taken from the z coordinate of the 3D point. More generally, the 3D point can be interpreted as having a vertical extent from a minimal to a maximal elevation. The minimal elevation is then specified via the bottomElevation that can depend on the 3D point attributes, but if this evaluates to its default value, the minimal elevation will be the z coordinate. The maximal elevation is specified via topElevation in the same way. If the minimal elevation differs from the maximal one, the output feature will be a vertical line instead of a point.

Line. A 3D line from elevationInput will first be clipped by a buffer zone that extends maxDistance horizontally from the fence. Only the line parts that are inside the buffer zone will generate output lines. If the maxDistance is zero, then clipped parts are usually just the points where the 3D line intersects the fence, so the output will be points instead of lines, although a 3D line that coincides with a part of the fence can still generate output lines. Normally, the z coordinate of each node in the input line is used as the elevation of the corresponding node in the output feature. However, as for input point features, it is possible to fetch a minimal and/or a maximal elevation for each input line from its attributes; if this is done, the output features will be polygons that extend down to the bottom elevation, and/or up to the top elevation (or, if maxDistance is zero and the 3D line passes through the fence, the output can be a vertical line segment).

Polygon. For a polygon feature, it is seldom useful to have a distinct elevation (z coordinate) at each node, since it would be ambiguous how to interpolate the elevation in the interior. In aeronautics, one uses 3D volumes known as airspaces, whose horizontal extent is given by a 2D polygon while the vertical extent is given by two numbers: the lower and upper vertical limits. The VerticalProfileOperator assumes that each polygon feature from elevationInput has a lower and an upper limit that can be retrieved via bottomElevation and topElevation. In the unlikely case that these are evaluated to their absurd default, the lower (or upper) limit is instead taken from the smallest (or largest) z coordinate of the polygon. When the lower and upper limits are known, the polygon is clipped by the buffer zone that extends maxDistance horizontally from the fence. Each remaining part generates a rectangular polygon feature in the output.

Elevation raster. A raster of ground elevations will generate a line on the fence, normally where the fence touches the ground. If close is True, the raster will also generate a polygon below the ground level (or above the ground, if closingHeight is higher than the ground). Raster cells within maxDistance from the fence can also affect the result. Note that input rasters that describe land cover are handled in a special way; see landCoverInput.

Volume-encoding rasters. Apart from vector data and ordinary elevation rasters, the elevationInput can also give the special volume-encoding rasters that can be produced by a LineOfSightOperator or an AirspaceCoverageOperator and represent viewshed volumes. The results from these will always be polygon features representing where the fence cuts through the volumes.

The route itself. When the route represents a 3D flight route, you can get an output line that corresponds to the route by letting outputRoute be True. An alternative way would be to make the route appear also as an input feature from elevationInput, but this would be less efficient. However, the alternative can be used if each segment of the route has its own set of attributes that should affect the output; maintaining the different sets of attributes would then require that each route segment appears as a separate input feature from elevationInput. Of course, another possibility is to use some application code to calculate how the route segments shall appear in the profile View, and then store the results in a MemoryDataSet, whose features can be sent to the profile View without passing through a VerticalProfileOperator.

Coordinates. The coordinates of the output features are defined in a coordinate system that is 2D but vertical; it is the same Crs as the one used by the View, and it is normally the Crs.nonGeoreferenced. The x coordinates of the output give horizontal distance along the fence, with zero at the start of the fence (first point of the route). The y coordinates of the output give elevation, so they normally correspond to the z coordinates of 3D points and 3D lines, and to the cell values of rasters. However, some of the y coordinates of the output can come from the bottomElevation and topElevation that are evaluated for each input vector feature from elevationInput.

Attributes. The output attributes are copied from the original input features, except the geoType.

• vpopSourceGeoType. The geoType value for an input feature (#raster, #line, #point or #polygon) is copied to a new attribute vpopSourceGeoType for the corresponding output feature(s). (The geoType attribute of an output feature must tell whether the output feature itself is a point, line, or polygon.) A special case occurs when outputRoute is True, which will transform the route into an output line with a vpopSourceGeoType that is #routeLine.

• vpopLandCoverCode. If the landCoverInput and landCoverHeightInput are used to get land-cover raster data, the operator will generate land-cover features for forest, shrubs, cities, etc. These features will be lines and polygons that stand on top of the ground profile feature. Each land cover feature will get an integer attribute vpopLandCoverCode, containing the raster cell value that represented the type of land cover. For example, 42 could represent "Evergreen Forest".

• vpopDistanceToRoute. Each output feature will also get a new attribute vpopDistanceToRoute, expressed in meters.

  • If the original input feature was a 3D point, the value will be its horizontal distance to the fence. The value is a signed number, with positive numbers meaning left of the fence (walking along the fence in the order of the points in the route).

  • If the original input feature was a raster, the attribute value will be zero.

  • If the original input feature was a line or polygon, it can have some parts that are close enough to the route to generate output, while other parts are too far away (farther than maxDistance). This means that a single line or polygon can generate several output features, which will each have their own value for vpopDistanceToRoute, expressing the minimal horizontal distance from the part to the route. The value is signed, and a positive number means left of the fence.

• Attributes giving highest terrain points. These attributes have become obsolete since the VerticalClearanceOperator is easier to use, but they are documented at Elevation Attributes in a Vertical Profile.

the elevation of the ground and land cover directly below the route (the colors depend on the type of land cover),

a road line at the point where it intersects the route,

water polygons and airspace polygons where they intersect the route.

the 3D points inside the buffer zone,

the airspace polygons where they intersect the buffer zone,

the water names that are attached to points inside the buffer zone.

the roads appear as lines, where they intersect the buffer zone,

the ground and trees show the highest elevation along a line perpendicular to the route within the buffer zone.

Point. A 3D point from elevationInput, within maxDistance from the fence, will normally generate a corresponding point on the fence surface, with the height taken from the z coordinate of the 3D point. More generally, the 3D point can be interpreted as having a vertical extent from a minimal to a maximal elevation. The minimal elevation is then specified via the bottomElevation that can depend on the 3D point attributes, but if this evaluates to its default value, the minimal elevation will be the z coordinate. The maximal elevation is specified via topElevation in the same way. If the minimal elevation differs from the maximal one, the output feature will be a vertical line instead of a point.

Line. A 3D line from elevationInput will first be clipped by a buffer zone that extends maxDistance horizontally from the fence. Only the line parts that are inside the buffer zone will generate output lines. If the maxDistance is zero, then clipped parts are usually just the points where the 3D line intersects the fence, so the output will be points instead of lines, although a 3D line that coincides with a part of the fence can still generate output lines. Normally, the z coordinate of each node in the input line is used as the elevation of the corresponding node in the output feature. However, as for input point features, it is possible to fetch a minimal and/or a maximal elevation for each input line from its attributes; if this is done, the output features will be polygons that extend down to the bottom elevation, and/or up to the top elevation (or, if maxDistance is zero and the 3D line passes through the fence, the output can be a vertical line segment).

Polygon. For a polygon feature, it is seldom useful to have a distinct elevation (z coordinate) at each node, since it would be ambiguous how to interpolate the elevation in the interior. In aeronautics, one uses 3D volumes known as airspaces, whose horizontal extent is given by a 2D polygon while the vertical extent is given by two numbers: the lower and upper vertical limits. The VerticalProfileOperator assumes that each polygon feature from elevationInput has a lower and an upper limit that can be retrieved via bottomElevation and topElevation. In the unlikely case that these are evaluated to their absurd default, the lower (or upper) limit is instead taken from the smallest (or largest) z coordinate of the polygon. When the lower and upper limits are known, the polygon is clipped by the buffer zone that extends maxDistance horizontally from the fence. Each remaining part generates a rectangular polygon feature in the output.

Elevation raster. A raster of ground elevations will generate a line on the fence, normally where the fence touches the ground. If close is True, the raster will also generate a polygon below the ground level (or above the ground, if closingHeight is higher than the ground). Raster cells within maxDistance from the fence can also affect the result. Note that input rasters that describe land cover are handled in a special way; see landCoverInput.

Volume-encoding rasters. Apart from vector data and ordinary elevation rasters, the elevationInput can also give the special volume-encoding rasters that can be produced by a LineOfSightOperator or an AirspaceCoverageOperator and represent viewshed volumes. The results from these will always be polygon features representing where the fence cuts through the volumes.

The route itself. When the route represents a 3D flight route, you can get an output line that corresponds to the route by letting outputRoute be True. An alternative way would be to make the route appear also as an input feature from elevationInput, but this would be less efficient. However, the alternative can be used if each segment of the route has its own set of attributes that should affect the output; maintaining the different sets of attributes would then require that each route segment appears as a separate input feature from elevationInput. Of course, another possibility is to use some application code to calculate how the route segments shall appear in the profile View, and then store the results in a MemoryDataSet, whose features can be sent to the profile View without passing through a VerticalProfileOperator.

Coordinates. The coordinates of the output features are defined in a coordinate system that is 2D but vertical; it is the same Crs as the one used by the View, and it is normally the Crs.nonGeoreferenced. The x coordinates of the output give horizontal distance along the fence, with zero at the start of the fence (first point of the route). The y coordinates of the output give elevation, so they normally correspond to the z coordinates of 3D points and 3D lines, and to the cell values of rasters. However, some of the y coordinates of the output can come from the bottomElevation and topElevation that are evaluated for each input vector feature from elevationInput.

Attributes. The output attributes are copied from the original input features, except the geoType.

• vpopSourceGeoType. The geoType value for an input feature (#raster, #line, #point or #polygon) is copied to a new attribute vpopSourceGeoType for the corresponding output feature(s). (The geoType attribute of an output feature must tell whether the output feature itself is a point, line, or polygon.) A special case occurs when outputRoute is True, which will transform the route into an output line with a vpopSourceGeoType that is #routeLine.

• vpopLandCoverCode. If the landCoverInput and landCoverHeightInput are used to get land-cover raster data, the operator will generate land-cover features for forest, shrubs, cities, etc. These features will be lines and polygons that stand on top of the ground profile feature. Each land cover feature will get an integer attribute vpopLandCoverCode, containing the raster cell value that represented the type of land cover. For example, 42 could represent "Evergreen Forest".

• vpopDistanceToRoute. Each output feature will also get a new attribute vpopDistanceToRoute, expressed in meters.

  • If the original input feature was a 3D point, the value will be its horizontal distance to the fence. The value is a signed number, with positive numbers meaning left of the fence (walking along the fence in the order of the points in the route).

  • If the original input feature was a raster, the attribute value will be zero.

  • If the original input feature was a line or polygon, it can have some parts that are close enough to the route to generate output, while other parts are too far away (farther than maxDistance). This means that a single line or polygon can generate several output features, which will each have their own value for vpopDistanceToRoute, expressing the minimal horizontal distance from the part to the route. The value is signed, and a positive number means left of the fence.

• Attributes giving highest terrain points. These attributes have become obsolete since the VerticalClearanceOperator is easier to use, but they are documented at Elevation Attributes in a Vertical Profile.