Bearing to 32-point compass box

How degrees map onto the 32-point compass rose

Zero degrees means north; ninety means east; one hundred eighty means south; two hundred seventy means west. Values outside zero to three hundred sixty are reduced modulo three hundred sixty, and negative headings wrap the same way, so a sensor that reports minus five point six two five still lands on North by West. Each sector is eleven point two five degrees wide; the implementation chooses the nearest center with standard half-up rounding and wraps three hundred sixty back to north. Send a required field named bearing as a JSON number or a numeric string. Aliases degrees, deg, azimuth, heading, and angle are accepted when your upstream schema uses those names. The thirty-two rose points sit on centers every eleven point two five degrees: N at zero, NbE at eleven point two five, NNE at twenty two point five, NEbN at thirty three point seven five, NE at forty five, and so on around to NbW at three hundred forty eight point seven five. On success you receive direction as the short classical label, full_name as the English phrase used when reciting the box, bearing_in as the finite value accepted, bearing_deg as the normalized angle on zero inclusive to three hundred sixty exclusive, index from zero through thirty-one, points equal to thirty-two, sector_center_deg, sector_from_deg, sector_to_deg, and method set to thirty_two_point_compass_rose. Identical finite inputs always produce identical JSON because the path is pure arithmetic with no network, no random seed, and no wall clock. This finer rose is the traditional full boxing used in classical navigation training, not the coarser sixteen-label set found on many consumer maps.

Validation, errors, and reading the response fields

The only hard rejection is a bearing that is not a finite number. Finite floating-point values including large magnitudes and scientific-notation strings that parse to a finite Number are accepted and then normalized. Use direction when a chart legend, status line, CSV column, or drill command needs a compact traditional label such as NEbE or WSW. Missing input, empty strings, booleans, objects, non-numeric text, NaN, and positive or negative Infinity all fail with invalid_input and are not charged after the engine rejects the request. Use full_name when a training manual, accessibility label, or spoken readout needs Northeast by East spelled out in classical English. Use bearing_deg when you must show the wrapped angle next to the label, and bearing_in when audit logs should preserve the raw reading before modulo. Sector bounds describe the angular window associated with the chosen center under the half-width of five point six two five degrees, with north wrapping across the zero meridian so sector_from_deg is three hundred fifty four point three seven five and sector_to_deg is five point six two five. This product does not convert a compass name into degrees; that reverse search intent is a separate endpoint. It also does not coarsen to a sixteen-point-only landing, compute a heading from two coordinates, or solve great-circle geodesy on a sphere.

API usage, pricing, workflows, and practical limits

Use the prepaid API when a sailing log importer, historical chart annotator, drone telemetry normalizer, or logistics dashboard needs a stable contract under KIT balance at $0.002 per successful item. Pair the endpoint with a coordinate bearing calculator when you first obtain a heading from two points, then label it with the full classical rose for humans; keep the steps separate so each landing matches a distinct search intent. There is no per-request size limit beyond ordinary JSON, and the work is a handful of floating-point operations inside a Worker isolate, so latency stays analytic and predictable.