API & MCP

Everything a person can do on Ohmforge GPS Trip Stats (GPX → speed and distance), a program or AI agent can do with the same inputs and get the identical result.

HTTP API

Ohmforge GPS Trip Stats (GPX → speed and distance)

Reads a GPX track from a bike computer, sports watch, phone app or Ohmforge's Pocket instruments speedometer and works out the trip: distance along the WGS84 ellipsoid, total, moving and stopped time, average, moving-average and maximum speed, elevation gain and loss, a speed profile and per-kilometre splits. Speeds come from positions and times, so jittery GPS points do not inflate the maximum.

Inputs of Ohmforge GPS Trip Stats (GPX → speed and distance)
FieldTypeDefaultDescription
filefile—GPX file. Tracks (and routes with times); every point needs a <time>. Up to 200 000 points. Processed in memory and not kept.
gpxtextarea—Or paste the GPX. Used when no file is uploaded.
stopKmhnumber2Counts as stopped below
windowSecondsnumber5Shortest window for the maximum speed. Speeds are averaged over at least this time; longer windows smooth out GPS jumps.
minStepnumber0Jitter filter: ignore steps shorter than. Phones standing still or walking slowly scatter around the true position and add distance. 0 = keep every point; 5–10 m suits walking with a phone.
elevationThresholdnumber5Elevation noise threshold. Ups and downs smaller than this are ignored when adding up the climb.

Every result contains

inputs (normalised, defaults applied), summary, result (validated against the published schema), units, assumptions, sources, warnings, computedAt and links.

MCP (Model Context Protocol)

{
  "mcpServers": {
    "ohmforge-gps-trip-stats": { "type": "http", "url": "https://ohmforgegpstripstats.usefulweb.app/mcp" }
  }
}