Sign in Schedule a meeting
SensorLogiX
Book a briefingDataLogiX

SENSORLOGIX · CIVIL, PUBLIC SAFETY AND COMMERCIAL

One live picture for emergencies, ports and public safety

Drone video, satellite hotspots, AIS, radar and fixed cameras in one live picture for emergency managers, coast guards, port and border authorities, utilities and police.

Every area and count in the report is computed twice, every detection is confirmed by a person before it counts, and past flights are searchable by what they show. The defaults keep people out of the picture unless the law and a second decision put them in.

Talk to usSee the uses
SATELLITE HOTSPOTSDRONE IMAGERYGROUND TEAMS (TAK)AFFECTED ASSETS

Damage assessment · revision 3

Ridge fire, east sector

Burned area 1,240 ha computed twice. Affected assets 37, each traced to its frame.

Public alert, EDXL-CAP 1.2: awaiting release

USES

One engine for the people who respond

Each use starts from data you already have and ends in a product you can release: to the public, to a partner agency, or to court.

Wildfire and disaster assessment

DATA IN

NASA FIRMS hotspots, drone imagery, NOAA and USGS feeds, the agency’s own asset records

WHAT COMES OUT

A damage assessment with the burned or flooded area as a verified value, affected assets and a map; public alerts in EDXL-CAP 1.2

CONTROLS

Person tracking off; every area computed twice; public release through the gate

Infrastructure inspection

DATA IN

Drone imagery and video of lines, bridges or pipelines

WHAT COMES OUT

Findings on a map, each detection confirmed by an inspector and traced to its frame

CONTROLS

Detections provisional until confirmed

Search and rescue

DATA IN

Drone video, ground teams’ TAK positions

WHAT COMES OUT

A search-grid product updated as teams report; confirmed sightings sent back to TAK

CONTROLS

Only confirmed items go out

Maritime domain awareness

DATA IN

AIS from receivers or providers, coastal radar, patrol video, charts

WHAT COMES OUT

Vessels of interest, AIS gaps, loitering and rendezvous alerts, port activity counts

CONTROLS

Thresholds from the pack, judged against a baseline; every count computed twice

Port and border monitoring

DATA IN

Fixed cameras and radars, ground sensors, AIS

WHAT COMES OUT

Spot and situation reports that revise as observations are confirmed

CONTROLS

Every earlier revision kept

Police drone programs

DATA IN

Video, imagery and telemetry from the agency’s drones and fixed cameras

WHAT COMES OUT

Flight and incident reports, court exports, redacted public copies and the annual UAS use report

CONTROLS

A legal authority on file and in scope; a signed custody log; persistent tracking without a warrant refused

PRIVACY AND AUTHORITY

People stay out of the picture unless the law puts them in

The defaults are set for civil use, and only a second decision changes them.

  • Civil defaults. Civil packs don’t make people subjects. Turning on person tracking is a pack decision a civil organization’s administrators can’t take alone.
  • Law enforcement inside its authority. Before a source collects, and before a query over its records runs, a current warrant, exigency, consent, public-airspace rule or mission policy must cover its area, time window and subjects. An expired warrant stops collection; refusals are audited. State drone laws come as a pack reviewed by counsel.
  • No live biometric identification. Real-time remote biometric identification is never offered, in line with the EU AI Act’s prohibition.
  • Custody and redaction. Every segment’s hash is chained in a signed custody log covering capture, landing, every access and every export; court exports follow SWGDE’s guidance for forensic video. Redacted copies blur faces, plates, bystanders and chosen areas and never replace the original.
  • Pictures described, never judged. A model’s caption or tag is labeled as a model’s description, GPS is dropped unless the pack keeps it, faces are off, and emotion, age, gender and ethnicity are never inferred.
  • Files from other agencies. Encrypted files open with your keys or a password supplied once, damaged files are repaired where possible with the loss shown, and nothing reaches a parser before the security checks. How intake works
  • Commercial operators. Utilities, pipeline and port operators, and insurers assessing damage can use the same products under their own records and retention rules.

IN THE FIELD

Works when the network doesn’t

Disasters take out the links first. The same forward deployment built for defense keeps an incident command post working.

A node at the incident

A forward node at an incident command post or on a patrol vessel runs feeds, maps, detection, search and situation products locally.

Works when the network fails

Offline map tiles, low-bandwidth layouts and controls usable with gloves. It keeps working with no link and syncs when one returns.

Over whatever link is up

Satellite, cellular, mesh radio or a ship-to-shore link. Confirmed items and decisions go first.

On your own GPUs

Detection runs on a managed GPU pool, on GPUs you own, or on the node’s own GPU, with the same models and rules.

How forward deployment works · Analysis on your GPUs · Links and uplinks

OPEN STANDARDS

Fed by the feeds you already have

Open data such as satellite fire detections and weather comes in beside your own drones, cameras and records. Alerts and exports leave in the formats other agencies read.

Every supported standard

  • EDXL-CAP 1.2
  • NIEM 6.0
  • OGC SensorThings API 1.1
  • OGC Moving Features JSON 1.0
  • STAC 1.1
  • GeoTIFF and Cloud-Optimized GeoTIFF
  • FAA Remote ID (14 CFR Part 89)
  • MAVLink 2
  • AIS (ITU-R M.1371-6)
  • ADS-B
  • IHO S-57 charts
  • Cursor on Target to TAK
  • SWGDE 18-V-001-2.0 court exports
  • MQTT 5

WITH DATALOGIX

Reports that stand up after the incident

SensorLogiX is a separate offering that adds sensing, image and video search, and analysis on your own GPUs to DataLogiX. Confirmed observations flow into DataLogiX, which turns them into the reports, briefings and releases you have to stand behind.

  • Verified numbers. Every burned area, count and distance in a report is computed twice by independent methods; a disagreement stops the report.
  • Signed files. Reports leave as Excel, PowerPoint, Word, PDF and web pages, each tracing every number and map to its source in a signed record.
  • Controlled release. Public, partner and redacted versions, each recorded with who received it and why.
See DataLogiX

Start with one incident’s data

Talk to usDefense and intelligence