KML Media Reconciler

Connect

Personal access token Folders to scan

Every sub-folder is included, and all folders are reviewed together so poles can move between them.

Not connected.

Saved views

Advanced and offline

GraphQL endpoint Extra metadata fields

A capture-time field here is preferred over upload time. Unknown fields make the query fail, so add one at a time.

Load a JSON export instead

From fetch_media_drive.py, for when the browser is blocked from calling the API.

Add corridors

KML, KMZ or GeoJSON (a line, or waypoints to connect)

No corridor loaded.

If the file is waypoints (Points), connect them in this order Segments longer than this are "bridges" across missing waypoints (m, blank = auto 2.5× median)

Buffer each side (m)

Bridge buffer (m)

Coverage bin length along the line (m)

Site-map feeders are added from the Site map panel after georeferencing. Each image is assigned to the nearest corridor within its buffer.

Time window (optional)

From

Also require GPS matches to fall inside the window

Images with no GPS inside the window are flagged as time-only candidates. Times are your local time.

Corridors and target folders

No corridors yet. Load a KML/GeoJSON or georeference a site map.

Images on a corridor that are not under that corridor's folder are listed as misfiled. Leave a folder blank to only report which feeder each image sits on.

Re-file by neighbours

Poles that were uploaded under the wrong mission stand out from the poles around them. Find them, select, and move them into the right folder in one go.

Move

Detection settings

Neighbours

Within (m)

Agreement %

Use shot order (capture time from DJI file names)

A pole is flagged when at least this share of the neighbouring poles, within this distance, sit under one other folder.

–

Pole folders

–

Images

–

Look misfiled

–

Selected

–

In move list

Scan Media Drive or load demo data first.

Remove

No images yet

Connect and scan your folders, or try it with demo data.

Looks misfiled Selected In move list (shown in its new folder's colour) B box · L lasso · P pan · Esc clear

Use Box or Lasso to select many at once, or click dots one by one.

Move selected pole folders into

	Pole folder	Images	Now in	Belongs in	Why	Shot
Press "Find odd ones out", or select on the map yourself.

Move list is empty.

Merge loose and split shots

Shots taken seconds apart at the same spot belong in one pole folder. This finds loose shots sitting in a feeder folder, and bursts of photos split across folders, so you can put each set back together.

Shots withinseconds andmetres

Same drone only Skip duplicate copies

–

To fix

–

Folders involved

–

Selected

–

Shots to move

Scan Media Drive or load demo data first.

No images yet

Connect and scan your folders, or try it with demo data.

Other images To fix, in the tab you are viewing (coloured by the folder each shot is in now) Selected Click a dot or a row to select its group

	Captured	Shots	Split across	Merge into	Moves
Press Find shots to merge after scanning.

Nothing selected.

Check folders

Every asset folder should hold the same number of RGB shots. This flags folders with too few or too many, and suggests the closest spare shots to refolder into each short one: from its own Archive, loose shots in the feeder, or extras from an over-full folder nearby.

RGB images per folder

Rules

Not RGB: file names matching

A regular expression. The default leaves out DJI thermal files (…_T.JPG). Clear it to count every image.

Archive folders: names containing

Archive folders are never checked themselves; their images are the first place to look for a short folder's missing shots.

Candidates within (s)

and (m)

A spare shot is a candidate when it was taken within this time of the folder's own shots (same drone) and this distance of the nearest one. Shots in the folder's own Archive always qualify.

–

Folders checked

–

Complete

–

Too few

–

Too many

–

Moves ticked

Scan Media Drive or load demo data first.

No images yet

Connect and scan your folders, or try it with demo data.

Other images Flagged folder's shots Suggested shot (line to where it goes) Click a row to zoom to that folder

Folder	RGB	Closest shots to refolder
Press Check folders after scanning.

No moves ticked.

Organise a dump into captures

Splits a folder of loose images into captures by time and distance, links captures of the same structure from different missions, and creates a folder for each one.

Source

Include sub-folders

Capture rules

New capture after a gap of (s)

or a move of more than (m)

Same structure when captures are within (m) Same drone only A nadir shot starts a new capture

Camera pitch field

Nadir at or below (°)

A capture is a run of consecutive shots with no gap longer than the time above, staying within the distance of where it started, and (when camera pitch is available) beginning at a nadir shot. Captures whose centres are within the structure distance are the same structure; repeat visits are shown together so you can decide whether they were one capture or several.

–

Images in source

–

Captures

–

Structures

–

Visited more than once

–

Selected

Scan Media Drive or load demo data first.

No images yet

Connect and scan your folders, or try it with demo data.

Capture outline (one colour per structure) Structure visited more than once Selected capture Click an outline or a row to select a capture

Structure	Visits	Captures and folder names
Choose the source folder and press Find captures.

Folders to create

Create them inside

Layout

Structure folder name

Capture folder name

Fields: {sid} structure number, {date} {time} of the first shot, {n} shots, {visit} visit number, {visits} visits to that structure. Names can also be edited per row. Existing folders with the same name are reused.

Nothing to create yet.

Corridor analysis

Check images against a corridor line for misfiled shots and coverage gaps. Add corridors on the left, set their target folders, then run the analysis.

Corridor (own colour per feeder) Bridged segment Waypoint / control point In target folder Misfiled In target, off corridor No folder set Other Coverage gap

Site map: georeference a feeder drawing (from extract_site_map.py) and turn its feeders into corridors

Site map JSON (*.sitemap.json)

No site map loaded.

highlight enabled feeders

Scroll to zoom, drag to pan. Pick 3 or more landmarks you can find on both the drawing and the map (substation, road crossing, tank farm corner, well pad). More spread-out points give a better fit. Exclude detail insets, the legend and the title block so their linework is not placed on the ground.

Feeder groups (tick to use, rename freely)

Control points

#	Drawing x,y	Lat	Lng	Resid (m)

Click a landmark on the drawing to start a pair.

Images scanned

Correctly filed

Misfiled (to move)

Strays in target

On a corridor (any)

Time-only (no GPS)

Coverage gaps

Run the analysis to see results.

The corridor analysis moves nothing. The CSV and the mutation text are for you (or support) to action after review; to move poles here, use Re-file.