A report at a different part of the site
Industrial estates, utility facilities and ports combine buildings, equipment and open space. Begin with the locations where observations would be useful and the people who will review them, then plan the receiver installation around that actual footprint.
A site team reports a drone near an outlying facility. The reviewer checks the received trail and timestamp against that location, rather than assuming the activity was directly over the main control building.
Where multiple stations receive a track, receiver evidence adds context about reception. Retained history can support a later review, and approved API access can be scoped for a defined organisational workflow.
Questions worth answering
- Which working area is the observation near?
- What reception evidence accompanies the track?
- What receiver positions and data access suit this particular site?
The features that fit this setting.
See the reception behind the track
Inspect receiving-station information behind a consolidated track when more than one station heard it.
Track details · internal provenanceExplore this feature →Keep site areas meaningful
Available saved-area rules can focus review on a named facility or working area.
Limited rollout · account/channel availability appliesExplore this feature →Maintain the listening points
Check reporting health and station details from the owner account as part of equipment routines.
Signed-in receiver ownerExplore this feature →Plan data access around the workflow
Approved API scopes support agreed live and history data integrations, with explicit keys and request limits.
Approval and scope limits applyExplore this feature →Set an area. Choose what brings you back.
Use recognisable site names and focus each available area on a specific review need. Treat a port-side building or outlying utility facility as a location to plan, rather than assume the central receiver represents the whole estate.
Available notifications can prompt the designated site reviewer to inspect an observation. For an integration, agree how an approved data feed fits the existing system and who evaluates the result.
- Choose the place. Use the map’s area-alert entry to select your centre and radius, then name the saved area in your account.
- Choose the activity. Review the rules available to your account and enable the ones relevant to this place.
- Choose the channel. Configure an available email, browser push or webhook channel, check quiet hours and send a test.
- Open the observation. Use the event timeline’s Live or Playback link as available to inspect what triggered your attention.
Area alerts · limited rollout. Account and channel availability apply. Email, opt-in browser push and signed webhooks have separate delivery states; notification timing depends on the rule, quiet hours and delivery channel. Check your account’s options and send a test before building a routine around notifications.
Explore your account’s area-alert options →
An area selects relevant received activity. It does not change the receiver’s listening range or create a flight restriction.
Give the receiver a useful home.
- Map the relevant facilities and potential fixed receiver positions with the local site team.
- Assess power, connectivity, obstructions, weather protection and maintenance access for each proposed installation.
- Agree practical reception and delivery checks, equipment ownership and the review workflow before handing over a business deployment.
Questions for this setting.
Is this suitable for a vessel?
This guide covers fixed shore-side sites. Moving vessels and other mobile platforms need a separately agreed deployment plan.
Does a larger area automatically mean more reception?
No. A saved area determines which received activity is relevant to a rule. Receiver placement and the actual installation determine what the local listening point receives.