API reference / @zaes/tactical-graphics / RadarSearchDoctrine
Class: RadarSearchDoctrine
Defined in: tacticalgraphics/graphics/MaritimeArea.ts:312
Extends
TacticalGraphicsBase<RangeFanOptions>
Constructors
Constructor
new RadarSearchDoctrine(): RadarSearchDoctrine;Returns
RadarSearchDoctrine
Inherited from
TacticalGraphicsBase<RangeFanOptions>.constructorProperties
name
name: string = TacticalGraphicName.RadarSearchDoctrine;Defined in: tacticalgraphics/graphics/MaritimeArea.ts:313
Overrides
TacticalGraphicsBase.nametype
type: string = 'Point';Defined in: tacticalgraphics/graphics/MaritimeArea.ts:329
One anchor point, as 200700 states. "This symbol requires one anchor point that defines the axis of angular rotation." Everything else the shape needs is named in Size/Shape as a number rather than a place: "determined by additional numeric values, a search axis azimuth, a start range, a stop range, and a stop relative bearing."
It was three anchor points from 2026-09-04 to 2026-09-05 — the radar, a point on the start arc and a point on the stop arc, all on the axis. That encoded exactly the same four numbers, but as geometry, and it is not what the plate describes: a base that carries a start range as a coordinate cannot be typed, only dragged. The four values now live where the standard puts them, on rangeFan — which already carried them, because the field registry has offered this symbol the range-fan editor with two fixed bands since it was built. (User's call, 2026-09-05.)
Overrides
TacticalGraphicsBase.typeMethods
asGeometryCollectionFeature()
asGeometryCollectionFeature(geometries, props?): Feature<GeometryCollection<Geometry>>;Defined in: tacticalgraphics/graphics/TacticalGraphicsBase.ts:83
Parameters
geometries
Geometry[]
props?
GeoJsonProperties
Returns
Feature<GeometryCollection<Geometry>>
Inherited from
TacticalGraphicsBase.asGeometryCollectionFeatureasLineStringFeature()
asLineStringFeature(coords, props?): Feature<LineString>;Defined in: tacticalgraphics/graphics/TacticalGraphicsBase.ts:39
Parameters
coords
Position[]
props?
GeoJsonProperties
Returns
Feature<LineString>
Inherited from
TacticalGraphicsBase.asLineStringFeatureasMultiLineStringFeature()
asMultiLineStringFeature(coords, props?): Feature<MultiLineString>;Defined in: tacticalgraphics/graphics/TacticalGraphicsBase.ts:28
Parameters
coords
Position[][]
props?
GeoJsonProperties
Returns
Feature<MultiLineString>
Inherited from
TacticalGraphicsBase.asMultiLineStringFeatureasMultiPointFeature()
asMultiPointFeature(coords, props?): Feature<MultiPoint>;Defined in: tacticalgraphics/graphics/TacticalGraphicsBase.ts:61
Parameters
coords
Position[]
props?
GeoJsonProperties
Returns
Feature<MultiPoint>
Inherited from
TacticalGraphicsBase.asMultiPointFeatureasPointFeature()
asPointFeature(coords, props?): Feature<Point>;Defined in: tacticalgraphics/graphics/TacticalGraphicsBase.ts:50
Parameters
coords
Position
props?
GeoJsonProperties
Returns
Feature<Point>
Inherited from
TacticalGraphicsBase.asPointFeatureasPolygonFeature()
asPolygonFeature(coords, props?): Feature<Polygon>;Defined in: tacticalgraphics/graphics/TacticalGraphicsBase.ts:72
Parameters
coords
Position[][]
props?
GeoJsonProperties
Returns
Feature<Polygon>
Inherited from
TacticalGraphicsBase.asPolygonFeaturegenerate()
generate(base, opts?): ITacticalGraphic;Defined in: tacticalgraphics/graphics/TacticalGraphicsBase.ts:107
The one place a generator is handed its base, and so the one place APP-06's point numbering is applied.
Thirty-two graphics store their points tip first, because that is how the standard numbers them; every generateGraphics in this package was written to build its head at the last vertex. featureInGeneratorOrder reconciles the two by reversing the line on the way in, which leaves the shape, the decoration sizes and the handle contracts exactly as they were and keeps the reversal out of thirty-two generators.
base on the way out is the caller's own feature, not the reversed copy: the caller drew it, saves it, and edits its vertices.
Parameters
base
Feature
opts?
Returns
See
drawOrder.ts
Inherited from
TacticalGraphicsBase.generategenerateGraphics()
generateGraphics(base, opts): Feature<GeometryCollection<Geometry>>;Defined in: tacticalgraphics/graphics/MaritimeArea.ts:394
Parameters
base
Feature<Point>
opts
RangeFanOptions | undefined
Returns
Feature<GeometryCollection<Geometry>>
Overrides
TacticalGraphicsBase.generateGraphicsgenerateHandles()
generateHandles(base, opts): Feature<MultiPoint>;Defined in: tacticalgraphics/graphics/MaritimeArea.ts:480
The three grips: the radar, the start arc and the stop arc — all on the search axis, whatever the clicks that produced them looked like.
A vertex line, so each grip is the anchor point it was placed as.
Parameters
base
Feature<Point>
opts
RangeFanOptions | undefined
Returns
Feature<MultiPoint>
See
- anchorVertex, which makes the radar inert under a reshape so the sector cannot be bent about its own origin — the same contract fields of fire and the search area have.
The middle grip is re-derived rather than published where it was dropped. It used to be handed back raw, so a click off to one side left a handle sitting beside the symbol, on nothing, and the base line drawn through it made a V of a straight run. The frame has already projected it; this draws it where the frame put it.
- projectOntoAxis
Overrides
TacticalGraphicsBase.generateHandlesgenerateLabels()
generateLabels(base, opts): Feature<Point>;Defined in: tacticalgraphics/graphics/MaritimeArea.ts:514
Where field T goes: "positioned in the centre of the search area aligned with the search axis" — so on the axis, midway between the two arcs, not at the anchor point. The anchor is the radar; the search area is out in front of it.
Parameters
base
Feature<Point>
opts
RangeFanOptions | undefined
Returns
Feature<Point>
Overrides
TacticalGraphicsBase.generateLabels