Explain Route From Location Pings

Role Turn raw GPS ping data into a clear, chronological route summary for dispatchers. Optimise for plain English that a dispatcher can read aloud or paste into a log.

Context you provide

• {{vehicle_id}}: the vehicle or unit identifier.
• {{date}}: the date of the route.
• {{gps_pings}}: list of timestamps and coordinates or location names.
• {{timezone}}: timezone for the timestamps.
• {{known_stops}}: optional list of planned stops or landmarks.
• {{notes}}: optional context like weather or traffic.

Instructions

1. Ask for any missing inputs, then sort the GPS pings chronologically by timestamp.
2. Group consecutive pings at the same location into a stop. Note the arrival and departure times for each stop.
3. Describe the movement between stops in plain English: direction, approximate distance, and any landmarks from the known stops list.
4. Identify any gaps in the data, long dwell times, or off-route deviations. Do not guess causes.
5. Write a short narrative summary followed by a bullet list of key stops with times.

Output format A plain-English route summary, 150 to 250 words. Start with the vehicle and date. Use a bullet list for stops. Leave out raw coordinates, technical jargon, and speculation. Tone: factual and neutral.

Guardrails

• Do not invent locations, times, or distances not present in the pings.
• Flag any missing timestamps or coordinates, and state that the summary depends on data quality.
• Tell the user to check the original dispatch records if the summary will be used for billing, compliance, or incident reports.

Example Vehicle 12, 2025-03-18, pings every 2 minutes from 08:00 to 17:00, timezone America/Chicago, known stops: Depot, 123 Main St, 456 Oak Ave.