Weather along a route
route_weatherWhat weather you will meet as you move along a route, at the moment you reach each part of it. Not "the weather on the trail" but "what will I encounter, where, and when". Accepts a known trail_id, a GPX file, GeoJSON, an encoded polyline, coordinates, or place names. With a start_time and a pace it works out when you reach each checkpoint, reads the forecast for that place at that time, and reports what changes: rain starting, the cold coming in, the light going. For someone already out there, pass progress (how far they are, or where) and it answers for the rest of the route from now. Returns checkpoints with arrival time, place, weather and light, the changes, and a bottom line. Use get_trail_weather for an hour-by-hour timeline and clothing advice.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| gpx | No | The text of a GPX file (track points). Up to about 450 KB. | |
| pace | No | How fast the person moves, as a value and a unit. | |
| units | No | imperial (F, mph, inches) or metric (C, km/h, mm). Defaults to imperial in the United States and metric elsewhere. | |
| geojson | No | GeoJSON as an object or a string: a LineString, MultiLineString, or Features holding them. Longitude first, as GeoJSON has it. | |
| activity | No | What the person is doing, if known. One of: walking, hiking, trail_running, road_running, cycling, camping, hunting, fishing, yard_work, construction, painting_finishing, general_outdoor. Plain words work too ("run", "hike", "stain the deck"). "Running" with no more words is treated as road_running. | |
| polyline | No | An encoded polyline (Google format). | |
| progress | No | For someone already on the route: how far along they are right now. The answer is for the rest of the route, starting now. Give distance_miles or distance_km, or a latitude and longitude. The position is used for this answer only and is never stored or logged. | |
| trail_id | No | A trail we know by name. Call list_trails to see them. Use this OR one of the route formats below. | |
| intensity | No | How hard the effort is, which changes what to wear. Defaults to the usual effort for the activity. | |
| waypoints | No | Two to twelve places to travel between, each a name like "Glenbeulah, WI" or { "latitude": 43.79, "longitude": -88.05 }. They are joined by straight lines, so distances are approximate. | |
| start_time | No | When the trip starts. Defaults to now. Ignored when progress is given. An ISO 8601 time such as 2026-10-03T18:00:00-05:00 (read in the place's own time zone when it has no offset), or plain words: "now", "tonight", "tomorrow morning", "Saturday", "6 PM", "between 6 PM and midnight". A bare hour with no AM or PM is refused rather than guessed. | |
| coordinates | No | A list of [latitude, longitude] pairs, latitude FIRST. | |
| preferences | No | Optional: { "feel": "runs_cold" | "runs_warm", "avoid": ["shorts"] }. | |
| out_and_back | No | True if the route is walked out and then back along the same line. | |
| polyline_precision | No | Digits of precision in the polyline. 5 is usual, 6 is what some routers send. | |
| total_duration_hours | No | Instead of a pace: how long the whole trip is expected to take. The pace is worked out from the length of the route. | |
| break_minutes_per_hour | No | Minutes of stops per hour of moving, which stretches arrival times. | |
| rest_at_turnaround_hours | No | Hours spent resting at the turn of an out-and-back (a night's sleep, say). |