Skip to content

Commit

Permalink
[los] update documentation
Browse files Browse the repository at this point in the history
  • Loading branch information
stronnag committed Dec 22, 2024
1 parent d58633d commit 3ab73c3
Show file tree
Hide file tree
Showing 3 changed files with 27 additions and 27 deletions.
Binary file modified docs/manual/docs/images/los-menu.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file removed docs/manual/docs/images/los_manual.png
Binary file not shown.
54 changes: 27 additions & 27 deletions docs/manual/docs/mwp-los-tool.md
Original file line number Diff line number Diff line change
Expand Up @@ -13,29 +13,16 @@ There are a number of issues to take into consideration.

* Online DEMs (Digital Elevation Model) vary [significantly](Mission-Elevation-Plot-and-Terrain-Analysis.md/#datum), with implications for accuracy.

{{ mwp }} uses [Mapzen DEM](https://registry.opendata.aws/terrain-tiles/) data, which improves accuracy (more users get 30m data) with better accuracy, as well as a significant performance boost and offline usage after the initial data download.
{{ mwp }} uses [Mapzen DEM](https://registry.opendata.aws/terrain-tiles/) data, which improves accuracy (more users get one arc-second data ) with better accuracy, as well as a significant performance boost and offline usage after the initial data download.

Please be aware of these accuracy / fidelity issues when evaluating the results of any elevation analysis.

## Invocation

!!! note "Legacy Images"
The images this section are from legacy mwp, however the capability is the same.

LOS is invoked from any waypoint using the right mouse button.
is invoked from any waypoint using the right mouse button.

![Menu Options](images/los-menu.png){: width="30%" }

## Line of sight ...

The user can select locations on the mission via a slider and run an analysis. A LOS calculation is performed, a graphical view is shown and a red (no LOS), orange (LOS below a user defined margin) or green (unconditional LOS) line is displayed on the map from the observer (home location) to the chosen location. This may be repeated as required.

## Area LOS

Pressing a modifier key (Shift or Control) while selecting "Line of Sight ..." will invoke **Area LOS** ; the calculation is performed automatically with 1% increments of the [naive mission length](#miscellaneous-notes). A set of resulting green/orange/red LOS lines is displayed on the map.

Note that both options are available from the LOS analysis window; the modifier option is merely a convenience.

## Examples

When the LOS slider is displayed, the only UI actions available are:
Expand All @@ -44,37 +31,50 @@ When the LOS slider is displayed, the only UI actions available are:
* Zoom the map
* Change the map product

This restriction means that the mission cannot be changed while a LOS Analysis is being performed.
This restriction means that the mission cannot be changed while a LOS Analysis is being performed. This is currently a feature (to reduce implementation complexity).

### Manual LOS Analysis

In the image below, the user has selected "Line of Sight ..." from the right mouse menu at WP9. The slider is positioned appropriate to WP9. Note that if the mission contains JUMP WPs, these are executed once only (regardless of the mission setting). This is why the slider might appear less advanced compared to the mission length if the JUMP is ignored. The user can reposition the WP using the slider (or the start / end buttons).
The LOS dialog presents:

* A slider to position the 'puck` (to which LOS is calculated) along the mission path.
* Start and End buttons to move the puck to start / end.
* A Margin selection (the clearance required at the puck location).
* A High resolution button (for Area LOS puck increments)
* A "Point LOS" button.
* An "Area LOS" button.
* A "Clear" button.

![Manual LOS](images/los-manual.png)


In the image above the user has selected "Line of Sight ..." from the right mouse menu at WP6. The slider is positioned appropriate to WP6. Note that if the mission contains JUMP WPs, these are executed once only (regardless of the mission setting). This is why the slider might appear less advanced compared to the mission length if the JUMP is ignored. The user can reposition the WP using the slider (or the start / end buttons).

When "Point LOS" is clicked, the LOS is calculated between planned home (brown icon, lower left) and the red "⨁" "Point of Interest" (POI) icon. This is displayed as a terrain plot with the LOS line superimposed over the terrain elevation. The line is red as there is no LOS (and it would be green where there is LOS). A red "dot-dash" is also displayed on the map. If a margin is specified, then LOS lines with clearance between the terrain and the margin value are shown in orange.

The user may repeat the "move slider" / "Point LOS" action as required. The prior terrain plot is removed each time "Point LOS" is selected; the lines on the map are removed when the slider dialog is closed. "Area LOS" may be used to run a continuous analysis from the currently selected location. "Area LOS" may be started / stopped at any point (and Point Analysis invoked at any time when stopped).

When an analysis results in an orange or red LOS line, the first point where the LOS break is detected is shown on the line as a coloured blob. This is apparent in the Area image below.

![Manual LOS](images/los_manual.png)
When an analysis results in an orange or red LOS fill, the first point where the LOS break is detected is also shown as a coloured blob. This is apparent in the Area image below.

### Area LOS

This analysis is iterated along the mission path automatically, providing Area coverage for the mission.

![Auto LOS](images/auto-los.png)
![Auto LOS](images/low-res-los.png)

The image shows the state after a complete "Area" analysis. While the analysis is running, the slider and "Point LOS" are not sensitive; once the run has completed, these controls are available if the user wishes to investigate further. The user can stop (and restart) Area using the "Area LOS" / "Stop" button.

The image shows the state after a complete "Area" analysis. While the analysis is running, the slider and "Point LOS" are not sensitive; once the run has completed, these controls are available if the user wishes to investigate further. The user can stop (and restart) Area using the "Area LOS" / "Stop" button. (Note: in earlier versions, "Area LOS" was called "Auto LOS").
Note the areas indicated in the SE part of the mission.

Here, the user has subsequently used "Point LOS" to examine a point in the orange region. As expected, there is very little clearance between the LOS line and the terrain. This is confirmed on the map plot where the "blobs" (immediately to the right of the plot window close button) indicate the point where LOS is compromised.
If the user now runs a "High Resolution" Area LOS, note how the more fidelity is revealed in the SE part of the mission.

It is important to note that Area LOS is performed at 1% increments of the [naive mission length](#miscellaneous-notes), it is not contiguous. In the above case, there is a point at 34.1% where there is no LOS.
![Auto LOS](images/high-res-los.png)

![Bad LOS](images/fail-los.png)
The user can use the "Point LOS" to examine a point.

If you selection the "High Resolution" when running "Area LOS", you get 0.1% increments, which may be used to investigate small segments (it will be slower ... and resource intensive). Here a detailed analysis has been run from 33.6% to 34.6% which captures the instance of complete loss of LOS.
![Auto LOS](images/point-los.png)

![Auto_no LOS](images/auto-bad-los.png)
It is important to note that Area LOS is performed at 1% increments of the [naive mission length](#miscellaneous-notes), it is not contiguous.

Caveat user!

Expand Down

0 comments on commit 3ab73c3

Please sign in to comment.