Telemetry Map Editor
Join several drone clips into one track, mark a bypass or an alignment change on the map, and export clean SRT, GPX, CSV and KML. Everything runs in your browser — nothing is uploaded.
Clips
Add clips with the button above, or drop the files anywhere on this tool. A video pairs with the .SRT of the same name and is read in place — never uploaded.
Between the clips
What the combined video's timeline does at each boundary. Nothing is decided for you.
Alignments
Chainage,Latitude,Longitude CSV (or Easting/Northing with a zone) or a KML/KMZ centre line. The first one loaded is the main alignment.
Export the track as recorded
More export options
Add clips to see them on the map. Then click the track: first click sets Point-1, second sets Point-2.
Telemetry table
The table follows the slider: 60 fixes around it. Every fix is in the CSV.
Edit segments
- No edits yet.
Edit log
What this is. A map-first editor for the telemetry of a survey flight recorded as several clips.
Each clip's telemetry (DJI SRT / ASS, the subtitle track inside a DJI MP4/MOV, GPX, KML/KMZ, CSV) is read
by the same engine as the Telemetry Extractor; a video is only opened to pair it with its sidecar and give a
duration — it is never re-encoded, cut or uploaded. The clips are joined into one track with two clocks:
the device's own time on every fix, untouched, and the project time of the combined video, in which a gap
between clips is kept, removed or set by hand at each boundary — never decided silently. Click the track
twice to set Point-1 and Point-2, then say what the stretch between them is: a bypass (five explicit
outcomes), an alignment change, a removal, a bridge across a gap, or a replacement with telemetry generated
along the design alignment — positions distributed along the alignment's geometry between the two chainages
on the original timestamps, flagged DERIVED_ALIGNMENT, with the original recoverable.
What goes out. An SRT in the clips' own dialect with sequential cues and valid timing; GPX; CSV with
provenance, source file, both clocks, chainage and offset on every row; KML/KMZ with the original, edited,
bypass and point layers. Export refuses while validation finds a serious problem. A project file keeps the
references, decisions and edit log — not the footage — and reopens when the same files are chosen again.
Everything runs in the browser; nothing is uploaded.
What the Telemetry Map Editor does, and how
What does the BTPL Telemetry Map Editor do?
The BTPL Telemetry Map Editor joins the telemetry of several drone clips into one track on a map, lets you mark a bypass or an alignment change, replace a stretch along the design alignment, and export the cleaned result as SRT, GPX, CSV or KML.
Is anything uploaded?
Nothing is uploaded: the BTPL Telemetry Map Editor reads, joins, edits and exports the telemetry in your browser, and the clips and their telemetry are never sent to a server. The map, where the edits are made, needs an internet connection: it loads the map library and satellite imagery tiles for the area on screen from third-party servers, which can therefore see which area is displayed. Without a connection, opening files, joining and export still work.
Survey video, delivered to the standard
BTPL records, processes and delivers chainage-referenced survey video for highways and railways — telemetry overlay, inspection registers and GIS-ready tracks.