Datatypes › Geographic identifiers
Bearing (heading in degrees)
ID bearing
DatatypeNot PIIDraft
This record is a draft: it has not been reviewed yet and may be incomplete or wrong. Do not rely on it for compliance decisions. Help improve it (see CONTRIBUTING.md).
Direction a vehicle, a vessel or a person travels or faces, in degrees clockwise from true north: 0 is north and 90 is east. GPS receivers and the vehicle positions of GTFS Realtime feeds report it as a decimal number (126.87); fleet tracking exports call it bearing, heading or course. A number from 0 to 360 alone can be any angle, so a value is a bearing only in a field named after it; a compass point in letters (NE) is compass_point, the direction a wind blows from wind_direction.
- Parent datatype
- Numeric value
numeric - Categories
- Geographic identifiers, Transportation, All measurable values (percentage, amount and e.t.c)
- Countries
- Global (not tied to a country)
- Languages
- Common to most languages
- Quality
- 90/100 · missing: mapping (Wikidata, Schema.org, ...)
- Metacrafter rules
- 1 rule (1 by field name, 0 by value)
bearingbynamefield, common/transport.yaml
- Supported by tools
- metacrafter
Regular expression
^(?:360(?:[.,]0+)?|3[0-5]\d(?:[.,]\d+)?|[12]?\d{1,2}(?:[.,]\d+)?)$
Python re syntax.
Test a value
Examples
| Value | Description |
|---|---|
| 126.8724594116211 | bearing of a Canberra Metro light rail vehicle (GTFS Realtime archive) |
| 0 | north |
| 270 | west |
| NE invalid | a compass point |
| 361 invalid |
Translations
| Language | Name | Description |
|---|---|---|
| Russian | Курс (азимут движения, градусы) |
Sources
Use this record
- Page URL:
https://registry.apicrafter.io/datatype/bearing - JSON: API v1 · legacy shape (used by metacrafter) · Markdown (for LLMs)
- Improve it: edit
data/datatypes/any/transport/bearing.yamlon GitHub