An observation near a public entrance
National institutions, museums and landmark sites often have several teams working around the same location. Clear timestamps and a common map reference help reception, estates and authorised operations staff discuss the same observation.
A member of staff reports a drone during a busy visiting period. The designated reviewer opens the received track and compares its reported movement with the entrance, public space and adjacent buildings.
The team keeps the observation time and track reference alongside its own notes. If a later review is needed, eligible history provides the recorded sequence rather than a reconstruction from recollection.
Questions worth answering
- Where was the reported activity relative to the site?
- Which observations are current and which belong to an earlier report?
- How can the relevant team review a consistent record?
The features that fit this setting.
Keep the timing clear
Reception age and live, coasting or ended states help reviewers distinguish a current report from an older position.
Live map and track detailsExplore this feature →Inspect the received sequence
Use recorded trails and report evidence to describe observed movement around the site.
Compact redesign awaiting publication · photos: CRJ9, A320 and C172 only · IAS/TAS not suppliedExplore this feature →Focus a review on the relevant place
Available saved-area rules can prompt a nominated reviewer when received activity matches the site’s area.
Limited rollout · account/channel availability appliesExplore this feature →Scope an institutional integration
Approved live and history API scopes can support a separately agreed data workflow for your organisation.
Approval and scope limits applyExplore this feature →Set an area. Choose what brings you back.
Name the area after the actual site and choose its extent with the team responsible for reviewing it. Include the approaches relevant to the review without turning every distant observation into a site incident.
Use available notifications as prompts for the authorised team to inspect the timestamp and track. Agree how this information fits the institution’s existing reporting and assessment process.
- 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.
- Start with the site’s information requirements and the team that owns the review process. Agree what a useful observation and handover look like.
- Plan receiver equipment and placement with estates and IT, including maintenance access and connection-health checks.
- For an integration, define the data fields and access scopes required and request business API approval before implementation.
Questions for this setting.
Does a receiver control the airspace around a building?
No. It receives supported drone broadcasts and contributes observations to the map. It does not stop a flight or create an exclusion zone.
Can an existing operations system consume the data?
Discuss the workflow through the business API programme. Access is approved for defined scopes and limits; a bespoke integration is a separate piece of work.