Zone editing for drones and airspace restrictions

Draw no-fly zones, geofences and temporary restriction areas on a web map, review them with your team and pass clean polygons to the system that serves them.

No-fly zoneRestrictedshared edge

At a glance

vectorstream is a geometry editor for web maps in which adjoining polygons share one stored border. Drone operators and drone-service platforms use it to draw and maintain no-fly zones, geofences, flight-restriction areas and temporary restrictions: where two zones meet, moving the line changes both, so no unassigned strip opens between them. The source of truth for the zones stays in your own authority data or service, and vectorstream is where the polygons are drawn, reviewed and corrected before they are exported as GeoJSON.

Editing model
Topology: shared borders are stored once
Map libraries
Leaflet, OpenLayers, MapLibre GL
Data
GeoJSON import with geometry check, GeoJSON export
Status
Pre-release, no package published yet

Use cases

Airspace zone work on the map

01

No-fly zones and geofences

A drone platform keeps a set of areas where its aircraft may not fly, plus the geofence that each mission has to stay inside. Many of these areas touch: the zone around an airfield meets a nature reserve, and the reserve meets a stadium. When the line between two of them is corrected, both zones need the same new line.

  • Move a border shared by two zones once
  • Drag a circle zone out from its centre point
  • Reshape a circle zone vertex by vertex afterwards
  • Draw a mission geofence as a polygon or rectangle
  • Snap new zone corners onto existing corners
02

Temporary restrictions

Events, construction cranes and emergency operations create short-lived restriction areas on top of the standing zones. Keeping them in their own layer and their own document lets a team prepare, review and withdraw them without touching the permanent set.

  • Keep temporary areas in a separate layer
  • Prepare each restriction as its own document in the browser
  • Note the reason and the dates in a text label
  • Copy a recurring event area instead of redrawing it
  • Delete a withdrawn area, and undo if it was the wrong one
03

Review and correction before export

Zone polygons often arrive from published datasets, partner files or older tools, with self-intersections or far too many vertices. The import refuses a file with broken geometry such as self-intersections and says why, and the polygons that pass are corrected here and go back out as GeoJSON to your own system.

  • Import zone files with a geometry check
  • Simplify outlines that carry too many vertices
  • Split a zone when only part of it changes
  • Group zones by restriction type in a layer tree
  • Export the reviewed zones as GeoJSON

Why topology

Why airspace zones benefit from topology

No unassigned strip between zones

When two restriction areas are drawn as separate shapes, their common line exists twice and the copies drift apart with every correction. vectorstream stores that line once, so the zones stay flush and the map shows no sliver that belongs to neither.

Corrections you can take back

A zone edit that goes wrong should never be repaired by hand. Exact undo in vectorstream returns the zone and every neighbour it touched to their previous shape.

Your data stays the reference

vectorstream holds no airspace data of its own and publishes nothing. Zones come in as GeoJSON from your source, are checked and edited, and leave as GeoJSON for the system that remains the reference.

How it works

From your zone data to reviewed polygons

  1. Step 01

    Import the current zones

    Load the zone set from your own authority data or service as GeoJSON. Broken shapes are reported first.

  2. Step 02

    Draw and correct

    Add new areas, drag circle zones out from a centre point and move borders shared by neighbouring zones.

  3. Step 03

    Review with the team

    Walk through the changes, keep temporary restrictions in a separate document and undo anything that should not stay.

  4. Step 04

    Export to your system

    Export the reviewed polygons as GeoJSON and load them into the system that publishes or applies them.

FAQ

Drone and airspace zone questions

Can vectorstream draw circular no-fly zones?
vectorstream has a circle tool: drag outwards from the centre point to draw a circular zone. The circle is stored as a polygon, so its outline can be reshaped like any other zone afterwards.
Do adjoining restriction areas share their border in vectorstream?
Yes. Where two zones meet, vectorstream stores one shared border, so moving it changes both zones and no gap or overlap opens between them.
Does vectorstream provide airspace data?
No. vectorstream contains no airspace data. Zones come from your own authority data or service, and vectorstream is where they are drawn, reviewed and corrected before export as GeoJSON.
Does vectorstream keep a drone out of a zone?
No. vectorstream edits polygons on a web map. Keeping aircraft out of an area is the job of the flight software or platform that receives the zones as GeoJSON.
Which map libraries can a drone platform use with vectorstream?
vectorstream ships adapters for Leaflet, OpenLayers and MapLibre GL on one editing core, so a drone-service platform can keep the map library it already renders with.

More questions

Review airspace zones on a map that keeps them flush.