geodesic traverse strip · paper ticker strip

Measure a Spherical Coordinate Chain Without Calling It a Road Route

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.

1 · Waypoint code | latitude degrees | longitude degrees

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.

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.

Perspective: 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.

2 · Read the geodesic traverse strip

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.

Paid layer: geodesic traverse strip filing layer

one-time step · the free reading above stays complete

hidden patterns detected after your first run

Free tier

one full, unwatermarked geodesic traverse strip App execution
three invented readings and unlimited calculations in the paired article demo
copy the complete working and boundary; voluntarily share non-sensitive input state

What $4 one-time adds

subsequent geodesic traverse strip App calculations through a browser-local convenience signal
boundary-preserving print and row-and-summary CSV of this geodesic traverse strip; conditional retyping budget uses only your entered minutes
five local headline/count/time summaries, separately deletable; full-input draft is separate and not a backup

HYPOTHESIS / PROTOTYPE: the proposed $4 one-time price concerns filing this geodesic traverse strip, not obtaining its answer. No checkout is available. An optional manual-retyping baseline computes a conditional one-export retyping budget; preparation, review, measured savings and buyer demand are not implied.

Local history (this device)

No saved runs yet — your first run files here.

Filing prototype — checkout unavailable

Checkout is unavailable. Browser-local, profile-scoped convenience gating is best-effort, not server-verified access. A URL or browser flag is not proof of payment. Clearing browser data removes local state; no account or cross-device recovery is provided.

Optional filing controls are a local prototype.

Checkout is unavailable. The reading above is complete; print, CSV and five local summaries are optional enhancements, not hidden answers.

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.

Boundary and sources

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.

Mechanism: competence-autonomy-loop

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.