Read the line every morning without scrubbing tiles.

Border Monitoring flags new crossings, tracks, fencing changes and staging areas along your boundary line from daily VHR imagery, so the shift starts from a list of what changed since yesterday.

Get startedSee the comparison

THE JOB TODAY

Where the tile scrub runs out

You open the archive, pick a segment and compare its tiles against the last set you looked at. Then the next segment. The ground teams cut sign on the drag roads they can reach, which covers the stretches an agent has walked or driven and little else.

Before the shift is over the desk has read part of the line, and the handover note goes to the next watch officer as a memory of what you saw. Nobody can say from a record what was new on segment nine on Tuesday.

A fence line of wooden posts running across open sand into haze
CH-01

The morning read, step by step

StepThe tile scrubWith Border Monitoring
01Deciding where to look firstThe tile scrubYou start at the segment where the last incident was, or work the line in order from one end.With Border MonitoringThe feed lists the segments with something new since yesterday, and you start with those.
02Spotting new tracks and crossingsThe tile scrubYou compare tiles by eye against the last set and try to remember what the ground looked like before.With Border MonitoringNew tracks and crossing points arrive as dated point features along the line, so you check each one rather than hunt for it.
03Watching the fence lineThe tile scrubA change in the fence shows up when an agent drives past it, or when someone happens to notice on a tile.With Border MonitoringNew and removed fence segments are flagged against the previous pass, by segment.
04Staging areasThe tile scrubVehicles gathering near the line are found by chance, if the tile you happen to open shows them.With Border MonitoringNew groupings of vehicles or structures near the boundary are flagged, with the date they first appeared.
05The handover logThe tile scrubA note written from memory at the end of the shift, plus whatever screenshots you saved.With Border MonitoringA daily log export, referenced to segment, that the next shift opens as it is.
06Tasking and the judgment callThe tile scrubYou decide what a mark on a tile is and which asset goes to which segment.With Border MonitoringYou decide the same. A flag is a place to look, and the feed does not say what a mark is.
Still yoursDeciding what each flag means, tasking patrols and aircraft, and any response. Nothing in the feed is an operational instruction.
CH-02

What arrives each day

  1. Point features

    Crossing and track detections

    Each new crossing or track is a dated point along the line, tied to its segment. This serves the "spotting new tracks and crossings" row, and it loads into a GIS workstation or common operating picture as a layer.

    Ledger row 02
  2. Segment flags

    Fence-line change flags

    New or removed fence segments, compared with the previous pass. A flag says what changed and where on the line, and leaves the judgment on cause to you.

    Ledger row 03
  3. Area flags

    Staging-area flags

    New groupings of vehicles or structures near the boundary, with the date they first showed. Read them before you task.

    Ledger row 04
  4. CSV

    Daily log export

    One row per flag, with segment, date and type, so the handover note becomes a file. This serves the log row.

    Ledger row 05
CH-03

How it works

  1. 01

    The line goes in

    You send the boundary line and the corridor to watch, and the segment names your desk already uses.

  2. 02

    A daily pass

    A VHR pass covers the corridor each day, whenever a clear one can be taken. Where cloud blocks a segment, that segment waits for the next pass.

  3. 03

    Change against the last pass

    Detection and change models compare each new pass with the previous one along the line and mark new crossings, tracks, fence changes and staging activity.

  4. 04

    The feed and the log

    Flags appear in the console feed for the shift, with a CSV log for handover. Your analysts review each one.

A weathered wooden fence post and wire in dry sagebrush country

Where it fits in your workflow

First read of the shift

The feed is the first thing the desk opens, before assets are tasked to specific segments. It stands in for the tile scrub. The rest of the shift, and every decision in it, stays with your people.

CH-04

Limits

These are the places the old routine still does something the feed does not.

Cloud sets the date
A segment under cloud on a given day is not read that day. It shows in the feed as not covered, and it lags until a clear pass. Ground teams and local knowledge keep covering it.
Resolution is a floor
At 0.3 m a pixel is about a foot across. A vehicle is several pixels long. A worn footpath is narrow, so it can only show where it contrasts with the ground around it. A wire fence is thinner than a pixel: what can show is a cleared strip, a line of posts, a shadow or a gap.
A daily snapshot
One pass a day. What moved through between two passes shows only if it left something behind. This is not video and it does not watch continuously.
It flags, it does not identify
The feed does not say who or what made a mark, or why. That is for the analyst and the ground team.
Not every crossing
A missed flag is possible. A clear feed is not a report that nothing crossed.

Switch if

  • You stand watch on a desk that reads a defined boundary line every shift.
  • Your analysts scrub archive tiles by segment and the handover is a note.
  • You want a dated log to point to, so a segment can be checked against the day before.

Stick with the tile scrub if

  • Your line is short enough that one analyst reads all of it every shift with time to spare.
  • You need identification, live tracking or camera coverage. That takes sensors and people on the ground.
  • You are looking for an enforcement tool. This feed points at places, and it makes no decisions.
CH-05

Questions from the desk

Q01Is the feed truly daily along the whole line?

It depends on a usable pass across each segment that day. On a cloudy day some segments lag and are marked as not covered.

Q02Does it replace the analyst?

No. It replaces the scrub. Every flag is reviewed by your analyst, and tasking is yours.

Q03Does it identify who is crossing?

No. It flags tracks and crossing activity from imagery. It does not say who made them.

Q04Can this trigger an enforcement response?

No. It is a monitoring flag for analyst review, not an operational directive.

Q05How long is a segment?

You set the segments per corridor, so they follow the names your desk already uses.

Q06Is this continuous or a daily snapshot?

A daily snapshot pass. It is not live video.

Q07How do we check it against our own ground truth?

Compare the flags with your sign-cutting reports and patrol logs for the same segment and day. Each flag is dated and tied to a segment, so the two line up. Tell us where your ground truth lives when the line is scoped.

Q08What does it plug into?

The point features and segment flags open in common GIS workstations, and the log is a CSV. Confirm your format at scoping.

Q09Who owns the imagery and the flags?

Ownership and use terms are set in the contract before work starts. The imagery providers keep their own licenses.

Q10How is it priced?

Each line is scoped on its own: length, corridor width and how you want the feed delivered. You get a written scope.

Send us the line and the segments you name.

We will tell you what the morning read would look like for it.

Get started