ForHosting KIT · Travel & geography

32-point compass to bearing

On the full 32-point rose, NNE sits at 22.5°, Southeast by East at 123.75° and North by West at 348.75°: every point is an exact multiple of 11.25°. Type a short or full English name and get its central bearing from true north. Free in your browser.

  • Free
  • Runs in your browser
  • No sign-up
  • Your data stays on your device
Use it from WebAPIEmailTelegramApp soon
If you enter
Name
NNE
You get
Canonical
NNE
Display
North-Northeast
Bearing deg
22.5
Point index
2

Navigators, surveyors, outdoor educators, game developers, and data pipelines still encounter labels such as N, NE, NNE, NbE, SW by S, Southwest by South, and North-Northeast; this tool resolves those strings to exact multiples of eleven point two five degrees without magnetic models or guesswork. North is zero degrees, East is ninety, South is one hundred eighty, West is two hundred seventy, North-Northeast is twenty-two point five, and Southwest by South is two hundred thirteen point seven five.

The 32-point rose and what you get back

The traditional full boxing of the compass divides the full circle into thirty-two named points spaced exactly eleven point two five degrees apart. Starting at North as index zero and zero degrees, the sequence runs North by East, North-Northeast, Northeast by North, Northeast, Northeast by East, East-Northeast, East by North, then East, and continues through the southern and western quadrants until North by West closes the rose at three hundred forty-eight point seven five degrees.

This converter accepts both short abbreviations such as N, NE, NNE, NbE, SWbS, and WNW, and expanded English forms such as North, Northeast, Southwest by South, East by North, and North-Northwest. Spacing, hyphens, and letter case are normalized so SW by S, swbs, and Southwest by South resolve to the same point when they refer to the standard label.

Where 32-point compass-to-bearing conversion fits in practice

Navigators still meet thirty-two-point language in coastal pilots, historical logs, and traditional sailing courses that say haul Southwest by South rather than two hundred thirteen degrees. Outdoor educators convert trail notes written with NNE or WNW into map bearings before plotting a course on a topographic sheet. Game and simulation developers map wind labels, spawn facing directions, and compass UI strings onto engine yaw angles without hand-maintaining a fragile local table that drifts between builds.

Cartography students verify that Northeast is forty-five degrees and that Southeast by East is one hundred twenty-three point seven five before labeling a rose diagram for a portfolio or exam. Data pipelines that ingest weather bulletins or archival ship journals normalize free-text points into numeric headings for analytics and geospatial joins. Use this capability whenever the search intent is specifically the thirty-two-point rose name to central bearing, and keep magnetic or grid-bearing converters for variation and projection work that sits outside traditional boxing.

Traditional boxing on charts and pilots

Turn 32-point rose phrases such as SW by S or North by East into central bearings for plotting courses and labeling compass roses.

Games, sims, and outdoor education

Map wind, heading, and compass UI labels to engine degrees for classrooms, simulations, and trail lesson plans.

What does the 32-point compass to bearing converter cost?

It is free in your browser on this page.

Which name forms are accepted?

Short abbreviations (N, NE, NNE, NbE, SWbS), spaced by-forms (SW by S), and full English names (Southwest by South, North-Northeast). Matching is case-insensitive.

What happens if the name is not a recognized 32-point compass point?

Empty strings, pure numbers, and unknown tokens never produce a guessed bearing.

Does this apply magnetic declination or true/magnetic conversion?

No. It only maps the standard 32-point rose name table to degrees from north. Magnetic variation and grid bearings are out of scope.

How is the bearing worked out from a point's place on the rose?

Each point is numbered clockwise from North at 0, and its bearing is that number times 11.25 degrees, a 32nd of the full circle. NNE is point 2, so it sits at 22.5 degrees.

Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.

POSThttps://api.kit.forhosting.com/geo/cardinal32-to-bearing

Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.

curl -X POST https://api.kit.forhosting.com/geo/cardinal32-to-bearing \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"NNE"}'
{
  "name": "NNE"
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "geo.cardinal32_to_bearing",
  "status": "queued",
  "_links": {
    "result": "/tasks/tsk_…/result"
  }
}

The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

This 32-point compass to bearing converter decodes the traditional full boxing of the compass: every named point on the thirty-two-point rose maps to a single central heading in degrees measured clockwise from true north. The engine is a pure deterministic lookup over the classic marine rose with no network call, no random sampling, and no Date dependency: either the name matches a recognized thirty-two-point label or the request fails with invalid_input.

What the thirty-two-point rose is and what the response returns

The success payload includes the original name string you sent, a canonical abbreviation such as SWbS or NNE, a human-readable display name, the central bearing in degrees from north clockwise, the zero-based point index, the constant points_total of thirty-two, the step size of eleven point two five degrees, a method tag cardinal32_rose, and a short formula reminder that bearing equals index times three hundred sixty over thirty-two. There is no magnetic declination correction and no reverse conversion from degrees back to a name: the page answers only rose-name-to-bearing. Unrecognized tokens, empty strings, pure numeric degrees, and strings longer than the documented limit are rejected with invalid_input so a typo never becomes a silent wrong heading. Pair this tool with other geo endpoints when you need distances or coordinate transforms; keep this one for traditional boxing labels that must stay identical across browser and API runs.

How names are read and why bearings stay reproducible

Cardinals N, E, S, and W map to zero, ninety, one hundred eighty, and two hundred seventy degrees. Intercardinals NE, SE, SW, and NW sit at forty-five degree multiples. Intermediate points such as NNE, ESE, and WSW occupy the half-steps at twenty-two point five degree offsets, while the eight by-points such as North by East and Southwest by South fill the remaining eleven point two five degree slots that complete the traditional boxing. Prefer the reverse bearing-to-compass tools when you need degrees to a name; this capability is deliberately one-way from traditional rose labels into degrees. The preferred input field is name, but aliases direction, compass, point, cardinal, and bearing_name are accepted so forms, spreadsheets, and query strings can reuse the same contract without renaming columns. The parser trims outer whitespace, lowercases letters, and strips punctuation and spaces for lookup, which is why SW by S and SWbS share a path when aliases register both compact and by-forms. Bearing is computed as point_index times three hundred sixty divided by thirty-two, which is exactly index times eleven point two five, then rounded to a stable four decimal places so JSON goldens compare cleanly without floating-point noise. Free browser runs on this page match the priced API result, so you can prototype interactively and then automate without re-implementing the thirty-two-point table yourself.

Where 32-point compass-to-bearing conversion fits in practice

On this page every conversion runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split — free interactive exploration and a priced identical API — matches the rest of the KIT tier-A catalog and lets you move from a classroom demo to an automated pipeline without changing the mathematical result.

Deterministic navigation fixtures

Generate reproducible bearing_deg values and canonical abbreviations for unit tests, demos, and CI assertions over the full rose.

How is the central bearing calculated from a rose name?

Each of the 32 points has an index from 0 (North) to 31 (North by West). bearing_deg = point_index × (360/32) = point_index × 11.25, measured clockwise from north.

Read the full KIT documentation →