Skip to content

Main content

Navigation Light Relative Sector Membership

Test an explicit relative bearing against a supplied clockwise angular sector without selecting statutory navigation-light sectors.

Loading tool…

Description

Check a bearing against a supplied circular sector and end-inclusion rule.

Nautical quantities require explicit north, datum, sign, station and unit conventions. A wrapped bearing error has a chosen opposite-direction endpoint, while a circular sector has its own start and end policy. Supplied polar speeds, tank factors and tide labels are references rather than verified navigation or vessel conditions.

Check a bearing against a supplied circular sector and end-inclusion rule.

When to use this tool

Use Navigation Light Relative Sector Membership when you already have bearingDegrees, sectorStartDegrees, sectorWidthDegrees, includeEnd and need to check a bearing against a supplied circular sector and end-inclusion rule.

How to use the tool and how it works

  1. Enter bearingDegrees, sectorStartDegrees, sectorWidthDegrees, includeEnd. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read inSuppliedSector. Inspect inSuppliedSector before interpreting the associated values.

Require sector width in [0,360]. Normalize start and bearing to a turn, take the forward wrapped offset, and compare offset<width or equality when includeEnd; width=360 includes every bearing.1

Input fieldMeaning and unitsAccepted input
bearingDegreesBearing DegreesRequired. Finite number.
sectorStartDegreesSector Start DegreesRequired. Finite number.
sectorWidthDegreesWidth from 0 through 360; zero width is empty unless includeEnd=true, which includes the start.Required. Finite number; minimum 0; maximum 360.
includeEndControls the far boundary; the start is normally included. Width 360 includes every bearing.Required. Boolean.
Output fieldInterpretationReturned shape
inSuppliedSectorIn Supplied SectorRequired. Boolean.
json
{
  "input": {
    "bearingDegrees": 355,
    "sectorStartDegrees": 350,
    "sectorWidthDegrees": 20,
    "includeEnd": false
  },
  "output": {
    "inSuppliedSector": true
  }
}

Limitations and assumptions

  • For zero width only includeEnd=true accepts the start bearing. The sector is supplied, not a selected navigation-light rule or a verified legal/safe visibility sector.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Use verified charts, observations, vessel documentation and the complete relevant geometric or hydrostatic model for a navigational question. Preserve the local bearing/datum convention and treat scalar factors or sector checks as limited inputs rather than operational decisions.

References

  1. Calculation and input contract: nautical/navigation-light-relative-sector-membership — tool.io

Similar or alternative tools