Route card to print

# Without a key, leave out the Authorization line (500 credits a day per address).
curl --fail-with-body 'https://api.trailsplits.com/v1/route-card' \
  -H "Authorization: Bearer $TRAILSPLITS_API_KEY" \
  -H 'Content-Type: application/json' \
  --data '{"geometry":{"type":"LineString","coordinates":[[6.97178,45.79266],[6.98409,45.80185],[6.98629,45.80488],[6.98231,45.80634],[6.9782,45.80782],[6.9784,45.81286],[6.98961,45.82424],[7.00303,45.82901],[7.0139,45.83525],[7.02084,45.83669],[7.02859,45.84621],[7.03402,45.84664]]},"name":"Courmayeur – Rifugio Bonatti","waypoints":[{"lon":6.971776,"lat":45.792663,"name":"Courmayeur"},{"lon":6.979459,"lat":45.817503,"name":"Midway"},{"lon":7.034022,"lat":45.846641,"name":"Rifugio Bonatti"}],"link":"https://trailsplits.com/planner"}'

A card to print and keep, for a line you post. It comes as self-contained HTML (images inline, so it works offline) or as a PDF on A4 or Letter paper. It carries:

• the map;
• the elevation profile;
• legs between your waypoints, with distance, climb and moving time;
• water and huts along the line;
• weather and sun, only when you give a date;
• a cue sheet, when you send one;
• the sources;
• a QR code to the link you give.

What it is, and what it is not.

• Nothing is stored or published. Making a card saves nothing and carries no identity. The QR code points only where you say, and only to a trailsplits.com address: your /r/ share or the Planner.
• Hazards and caveats. Fords, aided passages and via ferratas the analysis finds come first, with where they are. The analysis' caveats follow, such as a stretch off any mapped path. When the hike time is outside its calibration (T4 or harder, or much of the line off paths), the time note says it may be too fast.
• Figures add up to the line. Surfaces, roads and untagged paths are counted on the matched paths, so they are scaled to the line's length.
• Water and huts are always said. Either listed, or "none within 150 m", or "not available" when the index did not answer.
• The same facts as the route pages. Climb is "not measured" without heights (never +0 m), and "≈" when it is a terrain estimate. The hardest SAC grade comes with where it starts. Untagged paths are unknown, not easy, and roads are reported apart. Surfaces are tagged on the map or inferred from the kind of way.
• Weather only for a date. With no departure there is no weather section, never an implied "today". With one, the forecast is read at the hour you reach each point (route weather), the start is printed in the route's own time, and each model is named. On ECMWF hours near freezing, the card says that rain and snow are not told apart.
• Times and climb are yours when you send them. leg_seconds or moving_seconds makes the card match your screen, and climb makes it state your route page's climb (one route, one climb). Without them, the TrailSplits hike time model's total is shared across legs by their effort, at your pace. Breaks are not included.

Request

A flat object: only the line is required.

{ "geometry": { "type": "MultiLineString", "coordinates": [[[lon, lat], …], [[lon, lat], …]] }, "name": "Tour du Mont Blanc, days 1–2",
  "waypoints": [{ "lon": 6.87, "lat": 45.92, "name": "Les Houches" }, …], "leg_seconds": [16200, 19800],
  "units": "metric", "paper": "a4", "format": "pdf", "link": "https://trailsplits.com/r/abc123" }

Response

• format: html: 200, text/html; charset=utf-8. One self-contained page, with the map as an inline PNG, the profile and the QR code as inline SVG, a print size for the paper, and no scripts or outside resources.
• format: pdf: 200, application/pdf. Pages of the chosen size in Helvetica: the map, a vector profile, the QR code, the legs, the water and huts, the weather, the cue sheet and the sources. Characters outside WinAnsi print as "?", and "≈" prints as "~".
• Missing parts: a part that could not be had (the map, the places index, the forecast) is left out, and the card lists it under "Not on this card".

Errors

JSON, { "error": { "code", "message" } }.

Versioning

Additive content may appear in route-card/1. A change of what a card states, or of a request field's meaning, is route-card/2.