Map editing for utilities and network operators

Keep service areas and pressure zones flush along their borders, and sketch routes for new pipe segments and cables on the same map.

Zone NorthZone Southshared edge

At a glance

vectorstream is a web map editor that stores the boundary between two areas as one shared edge. Utilities use it to maintain service areas, supply districts and pressure zones: when a zone boundary is redrawn, the neighbouring zone takes the same line, so no strip of the network is left between two zones or claimed by both. Planned pipe and cable routes are drawn on the same map and 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

Network tasks on a shared map

01

Service areas and supply zones

Every pressure zone, supply district or maintenance territory borders others. When a valve setting changes or a district is reorganised, the line between two zones moves, and both zones must change in the same edit.

  • Move a zone border once for both zones
  • Split a supply district when the network grows
  • Merge two maintenance territories into one
  • Trace a new zone along existing zone borders
  • Keep zones, routes and labels in a layer tree
02

Route sketches for pipes and cables

Before detailed design starts, planners sketch where a new main or cable could run. A line on the map, with its vertices snapped to existing corners, is enough to discuss the route and pass it to engineering.

  • Draw routes with the line tool
  • Snap route vertices to existing corners
  • Remove one point from a line without redrawing it
  • Trace part of a route along an existing border
  • Export routes as GeoJSON for the design team
03

Work areas and outage polygons

For planned works, operators mark the area that will lose supply and the area where crews will dig. Freehand drawing is fast for a rough first outline that is refined vertex by vertex later.

  • Draw a rough area freehand, then refine it
  • Lasso-select several areas at once
  • Copy an outage area to a similar location
  • Label work areas with text labels
  • Undo a sketch back to the exact previous state

Why topology

Why network data benefits from topology

Zones without slivers

Service territories drawn as independent polygons slowly collect thin gaps and overlaps along their borders. With one shared edge per border, a gap cannot open when one zone is redrawn.

Corrections you can reverse

Operational maps are changed under time pressure. Undo in vectorstream returns every touched zone to its exact previous geometry, so a wrong click never turns into a data repair job.

Between your systems, not instead of them

Network data lives in GIS and asset systems. vectorstream imports GeoJSON with a geometry check and exports GeoJSON, so the editor sits between those systems rather than replacing them.

How it works

How an operations team uses it

  1. Step 01

    Import zones and routes

    Load service areas and existing route sketches as GeoJSON from the GIS or asset system.

  2. Step 02

    Adjust the zone boundary

    Move or retrace the line between two zones. Both zones update in a single edit.

  3. Step 03

    Sketch the work

    Draw a route with the line tool and snap its points to existing corners. Outline a rough work area freehand.

  4. Step 04

    Return the changes

    Export the changed zones and new routes as GeoJSON to the system of record.

FAQ

Utility and network questions

Can vectorstream keep pressure zones and service areas aligned?
Yes. Neighbouring zones in vectorstream share one stored border, so redrawing that border updates both zones together.
Can vectorstream draw pipe or cable routes?
vectorstream includes a line tool with snapping to existing corners, and a single point can be removed from a line without redrawing the whole route.
Does vectorstream replace a utility GIS?
No. vectorstream is an editing component for web maps. The asset register and the network model stay in the GIS, which exchanges geometry with vectorstream as GeoJSON.
Which map libraries can an operations portal use with vectorstream?
vectorstream runs one editing core on Leaflet, OpenLayers and MapLibre GL, so an operations portal does not need to change its map library to use it.
How does vectorstream treat imported network data?
GeoJSON imported into vectorstream passes a geometry check first, so invalid shapes are reported before anyone starts editing them.

More questions

Keep your service areas flush.