docs(tools): say heading values wrap into 0-359, not that 359.5 and up read 0

Co-Authored-By: Claude Opus 5.5 <[email protected]>
This commit is contained in:
quanticsoul4772andClaude Opus 5.5 committed 2026-11-03 07:00:27 -08:00
1 parent d1ed2e8e6f
commit ccd83c5fa2
2 files changed
+5 -5

No files matched your search

+4 -4
View File
@@ -1,4 +1,4 @@
- The agent and voice query tools report a direction of 359.5° or more as 0
instead of 360: vessel course and heading, aircraft course, transit bearing,
camera heading and satellite azimuths now round through the shared heading
helper the layers use (@quanticsoul4772, #1524).
- The agent and voice query tools report a direction that rounds to 360 as 0:
vessel course and heading, aircraft course, transit bearing, camera heading
and satellite azimuths now round through the shared heading helper the
layers use, which wraps into 0–359 (@quanticsoul4772, #1524).
+1 -1
View File
@@ -207,7 +207,7 @@ shared `area` argument (place name, bounding box, or point and radius) and cap
lists at 25 rows by default. Vessel `course_deg` and `heading_deg`, aircraft
`course_deg`, transit `bearing_deg`, camera `heading_deg` and satellite
`rise_azimuth_deg` and `azimuth_deg` are whole degrees from 0 to 359; a
direction of 359.5° or more reads 0 rather than 360. `aircraft_in_area` and `vessels_in_area` can also
direction that rounds to 360 reads 0, and larger or negative values wrap. `aircraft_in_area` and `vessels_in_area` can also
count every match by a field (`group_by`: airline, read from the ICAO
designator in the callsign, or operator, country or type for aircraft; type or
destination for ships; the ten largest groups, then other and unknown counts;