Border Surveillance,
Planned on Real Terrain
Border Security extends SESMA with a register of watch sites, cameras and radars, and an engine that shows what each sensor can actually see through terrain, haze and clutter. Find the gaps, test the next tower before it is built, and map where a target could go — on one map, with one audit trail.
Explore at resonixtech.com →
The Questions It Answers
Which stretch of border is not watched at all? If this tower fails, what do we lose? Where should the next three towers go, and what do they add? If someone is seen here, which sensors see them, and where can they get to in the next twenty minutes? Each question is answered on the same map, from the same register, and every answer can be exported as a report.
Why You Can Defend the Numbers
Every result is computed from terrain elevation, earth curvature, refraction, land cover and weather, never drawn by hand. Ranges are datasheet figures scaled by a realism factor, models stay flagged unverified until tested in the field, and every route is a candidate route, not a prediction. Outputs that reveal where the border is not watched sit behind a separate analyst role.
Border Security is a module of SESMA: same deployment, same sign-in, same audit trail.
Watch-Site Register
Sites carry cameras and radars, each with boresight, sector, tilt and status (planned, commissioned, decommissioned). CSV import with dry-run preview and export, and a change log that records who changed what, when, before and after.
Coverage by Selection
Tick any combination of sensors and see their coverage at once: best level, radar and camera together, overlap, or which sensor sees each cell best. Per-sensor results are cached, so a new selection redraws in a moment.
Real-World Line of Sight
Terrain elevation, earth curvature and refraction, mast and target height, sensor sector, tilt and minimum range, plus land-cover clutter that lifts the ground: a built-up block or an orchard hides what lies behind it.
Weather & Day / Night
Nine editable scenarios from clear to thick fog, rain and dust storm. Visible and thermal channels degrade by their own physics, and cameras can be run by day, by night or best of both.
Place a Target, See Who Sees It
Drop a what-if target, or open a real one, and drag it. For every sensor you get the level reached, distance and bearing, or the reason it fails: terrain, sector or range. Sight lines are drawn green or red on the map.
Scenarios & Gain Analysis
Propose new towers or take existing ones out in a scenario that never touches the register. Compare baseline against proposal with a delta map and a gain table, then let an administrator promote what is accepted.
Site Search
Ask where the next N towers should go. The engine scans candidate locations and terrain high points, picks the sites with the greatest added coverage, and re-checks each choice sensor by sensor before it is reported.
Escape Routes
From any target or map point: isochrones for how far it can be by now, diverse candidate routes with ETA and slope, a corridor of near-best alternatives, the sensors along each route, and interception points for responders.
Border-Line Reports
For analysts: percentage of the border covered at each level, the list of gaps with lengths, a dead-ground map and each site's unique contribution. Every output is watermarked and exports to CSV or KML.
One map for every tower, camera and radar
The module opens on its own room, separate from the spectrum Mission Room and open only to Border Security holders. Layers organise the picture: vectors (border lines, barriers, tracks), heat-maps, targets and watch sites. The status bar counts what is on the map, and everything a user draws or places stays inside this room.
- Backdrops of imagery, terrain or clutter, light or dark, and one global 2D / 3D switch.
- Site markers take the colour of their site type; a solid mast is commissioned, dashed is planned, grey is decommissioned.
- Border lines and areas are imported or drawn on the map and reused by every analysis.
- Nothing is shared with the Mission Room: targets, vectors, heat-maps and preferences are the room's own.
A register that remembers every change
The register is the single list of what is built, planned or retired. Each row is a site; open it to see its cameras and radars. Everyone with the module can read it, administrators edit it, and every edit leaves a trail, so a coverage figure can always be traced back to the configuration it was computed from.
- Filter and search by status, site type, sensor kind, model, capability or distance from a point; sort on any column.
- Inline status changes move a site between planned, commissioned and decommissioned.
- CSV import with a dry-run preview of every row (new, update, unchanged, error) before anything is committed, and CSV export in the same format.
- Change log: who, when, which field, before and after; History on any row opens it narrowed to that site or sensor.
Tick the sensors, choose a view, set the conditions
Coverage is not run per study. Each sensor's result is computed once and cached; whatever you tick is composed on the fly. The tree holds the sites, the three controls below decide what you see.
Seen or not seen: coverage that follows the terrain
Teal ground is seen at the chosen level, red ground is not. Each sensor's view is a radial sweep over the elevation model, with the earth's curvature and refraction applied, so a ridge casts a real shadow and a near blind zone appears under a down-looking camera. Switch the backdrop and the same result reads against imagery, terrain or land cover.
- Mast and target height are explicit: 0.5 m for a person crawling, 1.8 m standing, 2.3 m for a vehicle.
- Sector, tilt and minimum range are applied per sensor, including sectors that wrap through north.
- Cached per sensor, keyed on every input and the terrain version, so editing one sensor recomputes only that sensor.
- Under-cursor read-out names the level reached and the best sensor at any point.
State the question, and the grid is cached for it
A coverage figure means nothing without its conditions. The dialog sets them in one place, and every cached grid is stored against that exact set, so two analysts asking the same question get the same answer instantly.
- Target height with one-click presets, and refraction (standard optical 0.13, hot day, night inversion).
- Camera channel, weather scenario and radar target class (person, vehicle and others).
- Clutter switch: land cover lifts the ground along every line of sight.
- Honest ranges: datasheet figures times each model's realism factor, limited only by terrain.
Weather that behaves like weather
Each scenario is a meteorological optical range, plus an optional rain rate and a hot-day flag: from clear at 20 km, through haze, dust and fog, down to thick fog at 120 m. Weather caps every level at the same distance, so Detect, which reaches furthest, is the first to shrink.
- Visible and near-infrared follow Koschmieder visibility, about 0.6 × the optical range.
- Thermal uses ITU-R P.1814-1 fog attenuation, so it holds up in haze but not in thick fog.
- Rain and dust are modelled, and a hot-day shimmer rule derates Identify and Recognise. Heuristic rules are labelled as such.
- Manual factors per scenario override physics where vendor tests or field results exist.
Buildings and trees block sight lines too
Terrain is the main obstacle; clutter is what stands on it. A 10 m land-cover raster and an editable class-to-height table lift the ground along every line of sight, so a town or a plantation hides what lies behind it. Roads and tracks are burned in from OpenStreetMap so a narrow road does not become a false wall.
- Used everywhere: coverage, who-sees-it, dead ground, site search and the terrain profile.
- Cursor read-out names the class under the pointer and the height it adds.
- Sensor and target stand on the ground; only the stretch between them carries clutter.
- Stated limits: a class height is a statistic, the land cover is dated, vegetation is treated as opaque.
When a sensor cannot see, the profile says why
Click two points on the map, or snap to a site, and the profile appears: ground, curvature, the straight line of sight, the closest approach and a plain verdict. In the example the sight line is blocked by clutter standing 15 m on the ground, 10 m above the line of sight.
- Editable heights at both ends; a snapped site starts at its mast height.
- Clutter drawn as a band, so the obstruction is visible, not just reported.
- Right-click undoes a point, Esc clears, and a new click starts another cut.
- Geometry only: it answers line of sight, not radio propagation, and is available in every room.
Propose towers without touching the register
The register holds what is real or approved. A scenario is a named what-if workspace on top of it: proposed sites, or changes to existing ones, such as taking a tower out to see what its failure costs. Proposals are drawn as ghosts with a P badge, so they are never mistaken for built equipment.
- Site templates place a whole kit at once (radar panels, a long-range EO/IR PTZ, thermal cameras) around a reference bearing you rotate on the map.
- Any Border Security user can create and share scenarios; an administrator promotes accepted proposals into the register as planned.
- Delta view and gain table compare baseline with proposal: area gained, improved, lost or degraded, redundancy, and what only the new site sees.
- Optional cost per template: when set, the gain table reports new coverage per 1,000 of cost.
Where should the next sites go?
Draw the area to search and the area, or border line, to cover. Choose the kit, how many sites, and what counts as covered. The dialog shows the size of the problem before it starts: candidates, objective cells, the reach of the kit and an estimated run time.
- Constraints are optional: spacing between sites, maximum ground slope, candidate mast heights, exclusion polygons.
- Kit bearing is fixed or optimised over eight directions.
- Baseline is the register or an open scenario, so only the added coverage counts.
- Runs on the server with progress on the map, and can be cancelled at any time.
Ranked sites, each one checked twice
The search scores a grid of candidates plus the high points of the terrain, then picks sites one at a time by the coverage each adds. The shortlist is recomputed sensor by sensor at 20–45 m, and the chosen sites are checked again at full resolution; a difference above 15 % from the estimate is called out in the result.
- Numbered pins with mast height and bearing, and runner-up locations.
- Suitability dots show how good every candidate is, useful even without the final picks.
- Add to scenario in one click, so gain analysis and reports apply straight away.
- Limits are stated: terrain and clutter only, near-optimal rather than optimal, roads, power and land are as good as the vectors drawn.
From any target or point: where can it go, and how fast?
A cost-distance run over the terrain, where speed depends on the slope in the direction of travel: uphill is not downhill. Choose a mobility profile and the dialog fills in its limits; override them for the run. Candidate routes, not predictions: people do not walk pure least-cost paths, and the report says so.
- Profiles for foot, off-road vehicle, motorbike and camel, editable, with hard limits on climb, descent and side slope.
- Criterion: fastest with slope, shortest, or an analyst-only stealthiest route that bends round the sensors.
- Destinations: the border line, areas, the nearest road or settlement, or picked points.
- Barriers and fast lanes from drawn vectors, and ground cover read from the clutter raster.
Where can it be by now?
Colour bands show how far the target can have travelled in five, ten, twenty, thirty and more minutes, and the band for the time since the sighting is highlighted. Each route reports its time, length, steepest and average slope, and how much of it runs on roads, tracks or slow cover.
- Since-sighting clock reruns the picture as time passes.
- Sensors along each route, and when the target would enter each one's coverage, so a post or PTZ can be pre-pointed.
- Who sees the target now, listed per sensor with the reason for each miss: outside the sector, terrain, range.
- Select sensors that see it ticks them in the tree and shows their coverage.
Diverse routes, a corridor, and a chip that answers as you move
Up to k routes per destination are drawn with time ticks, made diverse by penalising ground an earlier route already used. Beneath them, a corridor shows every cell within a chosen percentage of the best total time, a more honest picture than one line. Wherever the cursor rests, a chip gives the ETA, distance, slope and movement class.
- Interception from responder positions you enter or pick, such as patrol posts: where a responder arrives first, with ETAs.
- Choke points are found as the narrowest cross-section of the corridor.
- Exposure statistics and the stealthiest criterion need the analyst role.
- Seen / not seen underneath shows how much of each route a sensor can watch.
Reports that can leave the room
An escape-route run or a scenario becomes a PDF with the marking you choose printed on every page. The report opens with the bottom line (time to the border, time to vanish at a road or settlement, earliest warning, interception feasibility), then the figures, every route with a waypoint table in latitude and longitude and in UTM, the method, the data and its limits.
- Scenario reports show before and after maps, areas at each level, and a page per proposed site with its mast, sectors and ranges.
- Reports page keeps what you choose to keep, searchable by title, author, profile and marking.
- Analyst reports that carry gaps or exposure are restricted, watermarked and served to analysts only.
- Data credited on the page: AW3D30 terrain and ESA WorldCover land cover.
Camera Models
Fixed or PTZ, with field of view, pan and tilt limits, and separate day and night channels (illuminator, laser or thermal), each with Detect, Recognise and Identify ranges. A calculator derives ranges from pixel density using IEC 62676-4 (2014 or 2025) or Johnson criteria for thermal, and a realism factor tempers datasheet figures that field tests rarely reach.
Radar Models
Rotating, electronically scanned or hybrid, with sectors, tilt, beamwidth and minimum range. Ranges are given per target class (person, vehicle, small UAS, boat); a class the datasheet omits is scaled from another by radar cross-section, and flagged as scaled. Several panels on one mast are simply several sensors.
One Geometry for Every Sensor
Boresight from true north, mechanical tilt, and horizontal and vertical sectors relative to both. Windows wrap through north correctly, rotating heads cover 360°, and the vertical test creates the near blind zone under a down-looking camera or a tilted radar face.
Types, Templates & Status
Site types and sensor types set marker and fan colours and glyphs. Status is held on both site and sensor, and the lower of the two applies, so a planned camera can sit on a commissioned tower. Kits of sensors are saved as site templates and placed as a whole.
Operators
Open the Border Security room and its own targets. Run coverage, overlap and best-sensor views; place a target and see who sees it; build scenarios and run site search; run fastest and shortest escape routes, isochrones and interception.
Register keepers
The only role that edits the register. Creates and edits sites, sensors, models, types, templates, weather scenarios and mobility profiles; imports and exports CSV; promotes accepted proposals into the register.
Analysts
Granted on top of the operator role. Border-line reports, gap lists, dead-ground maps, unique contribution, the stealthiest escape route and route exposure figures. Every output is watermarked RESTRICTED.