Architecture & Site Planning

How Drone-Mapper Works

This page is for the person who has to make it work on site—IT, security systems, facilities, or radio-curious ops. It explains the data path, what each piece does, and how to think about coverage and detector count. It is guidance, not a site survey.

1. The data path (end to end)

Think of Drone-Mapper as a short pipeline:

Drone (broadcasts Remote ID)
        ↓
Remote detector (hears the broadcast)
        ↓
Mesh link (moves data across the site)
        ↓
Wi‑Fi gateway (puts the site on the network)
        ↓
Software (map, history, alerts)

Drone

Many drones are required to broadcast Remote ID—identity and location-style data over the air (similar in spirit to a digital license plate). Drone-Mapper does not control the drone. It listens for those broadcasts when they are present and in range.

Important: If a drone is not broadcasting Remote ID (non-compliant, out of range, blocked, or not required), it will not appear. This is a Remote ID awareness system, not a radar or RF “detect everything” suite.

Remote detector

Each remote detector is a field node placed where you care about coverage. It:

  • Listens for Remote ID broadcasts in its local RF environment
  • Packages detections for the rest of the system
  • Forwards traffic over the site mesh toward the gateway

Detectors are the “ears.” More ears, better chance of hearing activity across a large or cluttered property—especially if height and line-of-sight are good.

Mesh

Detectors form a site mesh: short-range multi-hop links so a node that cannot see the gateway over Wi‑Fi can still deliver data through neighboring nodes.

  • Useful for campuses, fences, multiple buildings, and places where running Ethernet everywhere is painful
  • Still physics-limited: buildings, terrain, metal, and distance matter
  • Plan mesh as a reliable path to the gateway, not infinite range

Wi‑Fi gateway

One gateway is the site’s head-end. It:

  • Aggregates traffic from the mesh
  • Connects to a WiFi network
  • Sends data upstream to software (cloud Web Service, or a local install where you run that model)

If the gateway cannot reach the internet, cloud software will not update. For off-grid sites, use a solid backhaul (including Managed Starlink where appropriate).

Software

Software is where people work:

  • Live map and tracks
  • History / export
  • Zones and classifications
  • Alerts (e.g. email)

With Drone-Mapper Web Service, we host that layer. Your team uses a browser. Hardware still lives on your site; software is the operational picture.

2. What “good coverage” actually means

Coverage is not a single magic radius on a brochure. It is the overlap of:

  1. RF path from drone → detector (can the detector hear the Remote ID broadcast?)
  2. Path from detector → gateway (can the mesh deliver the packet?)
  3. Path from gateway → software (is the network/backhaul up?)

If any stage fails, the map goes quiet—even if a drone is nearby.

3. Height is the highest-leverage decision

For Remote ID receive, height almost always beats buying another node too early.

  • Higher is better — rooftops, poles, towers, upper walls beat ground-level bushes and loading docks
  • Clear the clutter — get above cars, people, temporary structures, and dense foliage when you can
  • Prefer line-of-sight to the airspace you care about (fields, approach paths, open campus quads)
  • Avoid RF sinks when possible — deep courtyards, metal warehouses, under bleachers, inside faraday-ish rooms

Rule of thumb: Before you double the number of detectors, ask whether the first ones can go higher or to a better corner of the building. One well-placed high node often outperforms two low ones.

4. How many detectors might you need?

There is no universal formula. Use these planning patterns, then adjust after a walk / pilot install.

Start simple

Site type Typical starting point
Small facility / single building interest area Starter Kit (1 gateway + 1 remote), both high if possible
Medium campus / multi-building 1 gateway + 2–4 remotes on high points covering main open airspace
Large campus / long perimeter 1 gateway + remotes along the perimeter or at corners; often 4–10+ depending on size and obstruction
Second geographic site Additional gateway (and its own detectors)—treat as its own system head-end

Add a detector when…

  • You have a blind side of the property (other side of a large building, far parking, back field)
  • Two interest areas are separated by structure or terrain that kills RF
  • Mesh path to the gateway is weak and an intermediate node would create a better hop
  • You care about a specific corridor (road approach, river, fence line) that the current nodes barely hear

Don’t assume that…

  • Acreage alone sets the count — open flat land behaves differently than dense urban campus
  • Indoor mounting equals outdoor performance — glass and walls attenuate
  • More nodes fix a bad gateway internet path — backhaul is separate
  • Every drone will always show — only broadcasting Remote ID aircraft in effective range

A practical planning sequence

  1. Mark the airspace you care about on a map (not just property lines—where threats or complaints actually happen).
  2. Pick the highest practical mounting points with power or solar options.
  3. Place the gateway where it has reliable network (or planned Starlink) and a reasonable mesh position relative to detectors.
  4. Deploy minimum viable nodes (often 1–3), run for a trial period, watch what you hear and where gaps show up.
  5. Add remotes only for measured gaps—not for anxiety.

5. Power, network, and ops (checklist for IT / facilities)

  • Power: Plan solar + battery or USB-C/powered locations per node; maintenance access matters
  • Network: Gateway needs stable path to software; firewalls should allow required outbound connectivity for Web Service
  • Physical security: Nodes are outdoor assets—mounting, theft, weather, and cable strain
  • Ownership: Who gets alerts? Who owns the Web Service login? Who swaps a failed node?
  • Expansion: Leave headroom in mounting and mesh layout for a future detector without redesigning the whole site

6. How this maps to products

  • Remote detector — field “ear” + mesh participant
  • Wi‑Fi gateway — site head-end to software
  • Starter Kit — one gateway + one remote (minimum useful system)
  • Web Service — hosted map, history, alerts
  • Managed Starlink — optional backhaul when terrestrial internet is missing

7. Bottom line for technical buyers

Drone-Mapper is a distributed receive + mesh + gateway + software stack for Remote ID awareness. Performance is dominated by placement (especially height), then by detector count, then by backhaul quality to the software layer.

If you want a second set of eyes on a layout, send a simple site sketch (buildings, heights you can use, where internet exists) via Contact.

Starter Kit · Web Service · Additional remote · Simple overview