...
To assign a Camera Area to a particular Camera, the Area needs to be created in that Camera's settings.
Enable the Config Function. Select the Areas folder in the Configuration Tree, then select New in the configuration panel.
...
In the configuration panel, select New Area.
...
This will open the New Area Wizard window. Name the area, and select Camera for Area Type. Select Finish.
...
The new Camera Area will appear on the PPI.
...
Use https://navtechradar.atlassian.net/wiki/spaces/TUN/pages/206602339/Creating+and+Editing to configure the Camera Area shape, the select Save.
...
The new Camera Area will also be listed in the Configuration Tree.
...
Next, enable the Config Function, then select the desired Camera in the Configuration Tree (or on the PPI Display).
...
In the Configuration Panel, the Camera Settings will appear. Maximise the Areas section.
The Area will appear as a grey row in the Areas table. Select Edit, then check Selected to assign the new Camera Area to the Camera.
...
Select Private if you wish to create a Private Area. By default, Areas are created Public. Fill colours are only visible on Public Areas - Private Areas have a grey cross-hatching fill.
...
Select Save when finished. Your new Area will only be visible on the PPI when the Camera is selected. The second image is a graphic translation of the first image, as used in Camera Area diagrams below.
...
Camera Viewer and Private Areas
...
Below are some examples of how Public and Private Areas can be used, including potential mistakes that can be made when employing Camera Areas. The graphics are to simplify the examples - compare an actual PPI to its graphic version.
Public Areas: designate the only zones that the Camera can focus on. Ergo, anywhere else within the Camera's scope, or within the detection area, is incidentally made private. In the example below, a track is in one of the Public Areas, and so the Camera can focus on and follow the track. Due to the Camera view, this means the Camera does incidentally view the area between the Camera and the Public Area, even though it isn't specified public. In the 'real life' AdvanceGuard® example, the Public Area is represented as a magenta dashed perimeter. Note that the Camera no longer follows the track in the second image, despite the track still being within the Detection Area.
...
...
Private Areas: designate zones in which the Camera cannot focus or follow tracks. Therefore, anywhere else within the Camera's scope, or within the detection area, is incidentally made public. In the first example below, a track is passing through an incidentally public area, and so the Camera follows it. However, the Camera's line of sight infringes on a Private Area. If you desire the Private Area to be completely invisible, it must instead be drawn to encompass all of the Camera's angle of sight. This is illustrated below in the second example.
...
Public and Private Areas: are rarely necessary given how the introduction of one incidentally creates the other, and vice versa. However, there are some examples where both Public and Private Areas may be employed. In the example below, a Public Area has been drawn within the detection area, and encompasses about 135° of the Camera's range of vision. However, within the Public Area is a building that requires privacy e.g. Lavatories. Therefore, a Private Area has been drawn within the Public Area to encompass the angle of the Camera.
...
| Info |
|---|
Private Areas always take priority over Public Areas, therefore there will be no clash by having two overlapping Areas. |
...
| Filter by label (Content by label) | ||||||
|---|---|---|---|---|---|---|
|
...