LineOfSightOperator.VolumeOutputResolutionFactor Property
Gets or sets a factor controlling the resolution of volume output (mesh or volume-encoding raster).
Syntax
public AttributeVariable< System.Int64 > VolumeOutputResolutionFactor { get; set; }Property Value
Default: Differs depending on type. See the table below.
A factor controlling the resolution of volume output (mesh or volume-encoding raster).
Default values
| Class | Default value |
|---|---|
| AirspaceCoverageOperator | Not used. |
| LineOfSightOperator | 1 |
| TargetLineOfSightOperator | Not used. |
Remarks
The operator can calculate with multiple resolutions (see FirstResolutionChange). If the input elevation rasters are available in 10 m resolution and overviews, then the operator can calculate in 10 m, 20 m, 40 m and 80 m resolutions, for example.
The ordinary raster output (see OutputMinVisibilityHeights) will keep the multiple resolutions. However, when generating the two other kinds of output, see OutputVolumeMesh and OutputVolumeEncodingRaster, the operator must first resample the multiple resolutions to a single resolution. By default, the operator will resample to the highest resolution, so it would be 10 m in the example.
By setting VolumeOutputResolutionFactor = 2, the operator would instead resample to 20 m resolution, which should be more efficient although coarser. Setting the factor to 4 would force resampling to 40 m resolution, etc. The possible volume resolutions are the resolutions that the operator has used for its basic calculations. So the sensible values of the factor are 1, 2, 4, 8, 16, ..., etc., up to the value corresponding to the coarsest resolution used. Other values are accepted but will be rounded down to the nearest sensible value.
One could force the operator to produce coarser volumes in another way. In our example, one could keep VolumeOutputResolutionFactor = 1 and instead set DesiredInputResolution = 20.0, to make the operator calculate in 20 m, 40 m, 80 m and 160 m resolutions, ignoring the 10 m resolution (or calculate in just 20 m, 40 m and 80 m resolutions if FirstResolutionChange is also increased). However, ignoring the available 10 m elevations would increase the inaccuracies for sight obstacles in the terrain nearest the observer, and such errors would have effects that propagate beyond the obstacles and grow linearly with distance.
Platforms
Windows, Linux, Android