Measure a Spherical Coordinate Chain Without Calling It a Road Route — Free
Longitudes on opposite sides of the date line can be neighbors. Keep shortest spherical arcs, waypoint order and the assumed radius visible rather than mistaking raw coordinate differences for travel distance.
The proof surface
Road legs assume drivable routes; this measures a spherical coordinate chain, explicitly not road distance, including shortest date-line crossings.
Rare deviceRoad legs assume drivable routes; this measures a spherical coordinate chain, explicitly not road distance, including shortest date-line crossings.
Output artifactOrdered shortest-arc chain distance plus complete labeled working
Cost$0 local core · no account, card, paid key or subscription · filing proposal has no checkout
Sample, not your facts: Invented records: Cedar origin | 0 | 0; Willow waypoint | 0 | 1; Pine endpoint | 0 | 2. Assumed sphere radius (km) = 6371; expected Ordered shortest-arc chain distance: 222.389853 km on entered spherical chain. These are not quotations, verified observations or personal evidence.
Before using the geodesic traverse strip
Enter an ordered chain of at least two fictional or non-sensitive waypoints. Latitude is north-positive and longitude east-positive, both in decimal degrees. The sphere radius is an explicit modeling assumption, not a measured Earth shape or a travel recommendation. The haversine method returns the shortest great-circle arc between each adjacent pair on that sphere. It ignores terrain, coastlines, roads, airspace, border controls, access, weather and the Earth’s ellipsoidal shape. The page has no map or location lookup. Use real route services and responsible travel advice for a journey; do not navigate or estimate safe travel time from this coordinate worksheet.
Why the flat version breaks
The date line becomes a nearly full-world leg
Subtracting 179.5 from minus 179.5 as an ordinary linear position yields 359 degrees of apparent travel. Longitude wraps around the sphere. This strip uses the shortest wrapped difference and explicitly labels the date-line example. It still cannot tell you which route is practical or permitted, so the shorter arc must not be sold as a booking recommendation.
Running totals are added a second time
Every row can show the cumulative chain distance for orientation, but only its new leg belongs in the final sum. Summing cumulative figures double-counts earlier travel. The first row is a labeled origin with no prior leg. The copyable result preserves both roles rather than listing unlabeled distances that could be mistaken for interchangeable quantities.
Geometric distance is treated as a route forecast
The sphere omits road networks, elevation, access restrictions and actual travel paths. More decimal places do not repair those omissions. A real journey requires current routing and provider information. Keep the radius and spherical qualifier in any shared result; do not remove the boundary to make a modeled chain appear more precise or actionable than it is.
How to work the geodesic traverse strip
Check coordinate order and signs
Use waypoint codes that do not reveal a home or private location. Transcribe latitude first, longitude second, with latitude between minus and plus 90 and longitude between minus and plus 180. Swapped columns can remain numerically legal yet describe another place, so compare them with the source convention. The calculator cannot geocode a name or verify coordinates. Missing fields, unit suffixes and nonfinite syntax are rejected rather than interpreted as zero.
State the radius and intended chain
The shared radius setting must be a positive plain number between one and 100,000 kilometers. The sample uses 6,371 for a simple spherical exercise, not a precision navigation standard. Waypoint order is load-bearing; the first row has no previous leg and contributes zero. A repeated physical coordinate with a new code contributes a zero-length leg. Do not remove a stop from the source just because the direct arc looks shorter.
Compute shortest arcs with wrapped longitude
Convert angles to radians. For adjacent points compute h = sin²(Δlatitude/2) + cos(latitude1)cos(latitude2)sin²(Δlongitude/2), with the longitude difference wrapped to minus 180 through 180 degrees. Clamp h to zero through one against rounding drift, then use central angle 2atan2(√h, √(1−h)). Multiply by the assumed radius. Row workings show the leg and running chain total; the headline sums legs once, not cumulative totals.
Keep geometry separate from itinerary claims
Compare the source coordinates and all leg distances before copying. A spherical arc may cross water or inaccessible terrain, and distance alone supplies no journey time, fare or safe route. The radius can be changed for a classroom sphere, but that does not create a verified planetary route planner. For an actual trip, use an appropriate current route service and confirm access with a responsible travel provider. The optional filing prototype saves the modeled chain and its boundary, not a navigable map.
What the geodesic traverse strip keeps distinct
Question
Before
Check this working
The date line becomes a nearly full-world leg
Subtracting 179.5 from minus 179.5 as an ordinary linear position yields 359 degrees of apparent travel. Longitude wraps around the sphere. This strip uses the shortest wrapped difference and explicitly labels the date-line example. It still cannot tell you which route is practical or permitted, so the shorter arc must not be sold as a booking recommendation.
State the radius and intended chain
Running totals are added a second time
Every row can show the cumulative chain distance for orientation, but only its new leg belongs in the final sum. Summing cumulative figures double-counts earlier travel. The first row is a labeled origin with no prior leg. The copyable result preserves both roles rather than listing unlabeled distances that could be mistaken for interchangeable quantities.
Compute shortest arcs with wrapped longitude
Geometric distance is treated as a route forecast
The sphere omits road networks, elevation, access restrictions and actual travel paths. More decimal places do not repair those omissions. A real journey requires current routing and provider information. Keep the radius and spherical qualifier in any shared result; do not remove the boundary to make a modeled chain appear more precise or actionable than it is.
Keep geometry separate from itinerary claims
The geodesic traverse strip replaces this named manual reconciliation, not source verification or the responsible human's decision.
Run it on the samples, right here
FIRST-LOAD
HYPOTHESIS / PROTOTYPE — checkout unavailable. Calculation is local. A draft is saved automatically in this browser profile when storage is available; Reset to sample clears it. Optional Pro history stores only five summaries and has its own deletion control. State links encode your inputs and can remain in browser history, clipboard or recipients’ records; share only non-sensitive rows. Optional external AI formatting leaves this device. The required site analytics beacon reports page activity; shared URLs contain encoded inputs. Do not treat an encoded URL as private. The calculator has no input-collection endpoint.
Spherical geometry only: no road, flight, walking, border or safety routing and no navigation guarantee. Verify source coordinates and use a current appropriate route service or travel provider before planning an actual journey.
Data note: This geodesic traverse strip calculates in the tab from Waypoint code | latitude degrees | longitude degrees. No input-collection endpoint, AI request or file upload is built into it. Drafts may be saved locally; explicit input-state links and optional external formatting can disclose the records. Use non-sensitive codes and clear the draft when finished.
Go deeper: the companion app files the same reading as a paper ticker strip
The article demo above runs without limits. The companion app keeps a local history, exports the rows as CSV, prints the geodesic traverse strip reading, and holds your drafts on this device — one complete free app run; the proposed $4 one-time filing layer is not for sale.
Keep the complete geodesic traverse strip answer free; optional filing proposes its boundary-preserving print, row-and-summary CSV and five local reading summaries. The $4 one-time prototype is not for sale; another calculation remains free in the article demo.
Spherical geometry only: no road, flight, walking, border or safety routing and no navigation guarantee. Verify source coordinates and use a current appropriate route service or travel provider before planning an actual journey.
What this is built on
Declared local method: Convert angles to radians. For adjacent points compute h = sin²(Δlatitude/2) + cos(latitude1)cos(latitude2)sin²(Δlongitude/2), with the longitude difference wrapped to minus 180 through 180 degrees. Clamp h to zero through one against rounding drift, then use central angle 2atan2(√h, √(1−h)). Multiply by the assumed radius. Row workings show the leg and running chain total; the headline sums legs once, not cumulative totals.
Every sample code, measurement, date, price, fingerprint and scenario is invented. Artifact checks do not verify reader data, policies, actual files, tickets, votes or health/accessibility outcomes.
Google’s official Gemini pricing page, fetched 2026-10-01, lists AI Studio access in its Free section, limited model access and free input/output tokens. Free-tier content may be used to improve products. Optional external formatting may require an account; limits/access can change. Manual local entry needs none. Do not send sensitive records.
Before: raw longitude differences and road-distance assumptions distorted the route. After: wrapped spherical legs and their radius-defined chain total have a clearly limited geometric meaning.
Three worked readings, with different inputs
Sample A — typical inputs
Cedar origin | 0 | 0
Willow waypoint | 0 | 1
Pine endpoint | 0 | 2
Setting: Assumed sphere radius (km) = 6371. Expected summary: 222.389853 km on entered spherical chain.
Two one-degree equatorial legs each measure about 111.194927 kilometers on the entered 6,371-kilometer sphere. The chain total is about 222.389853. This is the sum of shortest spherical arcs between the entered ordered waypoints, not a street route or an airline itinerary. Adding a waypoint changes the chain even when a direct origin-to-end arc exists.
Sample B — changed plan
Harbor west point | 0 | 179.5
Orchard east point | 0 | -179.5
Setting: Assumed sphere radius (km) = 6371. Expected summary: 111.194927 km on entered spherical chain.
The two longitudes are one degree apart across the date line, not 359 degrees apart. The wrapped longitude difference selects the shortest arc, giving about 111.194927 kilometers on the same sphere. This geometric crossing has no date, timezone or entry-permission information. The app does not infer a travel day or schedule from a longitude.
Setting: Assumed sphere radius (km) = 6371. Expected summary: 0 km on entered spherical chain.
Both coordinate pairs identify the north pole despite different longitudes, so their spherical distance is zero to displayed precision. This is a useful coordinate degeneracy, not missing movement. Near-antipodal points are another boundary: the haversine intermediate is clamped to its mathematical zero-to-one domain before taking square roots, preventing rounding drift from creating a nonfinite distance.
Optional AI formatting, never the calculation
Manual entry completes this geodesic traverse strip for free without signup. If available to you, the free AI Studio interface linked in the sources may format fictional or non-sensitive notes; external access may require an account. No API key or AI call is built into this tool. Free-tier content may be used to improve products. Review each cell and transcribe it to the labeled row schema; do not paste the JSON object into the row box.
Format only these fictional or non-sensitive notes for a geodesic traverse strip. Return strict JSON shaped as {"rows": [{"label": "string", "cells": ["string", "string"]}], "setting": "string"}. The columns are Waypoint code | latitude degrees | longitude degrees; the setting is Assumed sphere radius (km). Keep all supplied strings and quantities exactly; do not calculate, infer missing entries, invent dates or add advice. If any required value is missing, return an empty rows array and ask me for it separately. I will verify every cell against my source and manually transcribe rows using vertical bars before running the local calculator.
An AI response is not executed, fetched or trusted as a result. Missing values remain questions; the strict local parser checks the rows you actually enter.