Telemetry Map Editor
Join the telemetry of several drone clips into one project track, click two points on the map, and mark the stretch between them as a bypass, an alignment change, or replace it with telemetry generated along the design alignment. Time stays continuous for a combined client video; the result goes out as SRT, GPX, CSV and KML. Videos are only identified — never edited or uploaded.
Advanced
Add clips to see them on the map. Then click the track: first click sets Point-1, second sets Point-2.
The table follows the slider: 60 fixes around it. Every fix is in the CSV.
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.
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.