Zone editing for micromobility and shared mobility

Lay out operating areas, parking spots, no-parking, no-ride and slow zones for scooters and shared bikes, city by city, and hand clean polygons to your fleet backend.

Slow zoneNo-ride zoneshared edge

At a glance

vectorstream is a web map geometry editor in which neighbouring zones share one stored border. Shared mobility operators and city mobility teams use it to maintain operating areas, parking spots, no-parking zones, no-ride zones and slow zones for e-scooters and shared bikes: a slow zone moved along a street changes the zone next to it in the same edit. Zones are organised per city and per operator in a layer tree and exported as GeoJSON to the fleet or permit system.

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

Fleet zone tasks on one map

01

Operating areas and speed zones

An operating area covers the part of a city where vehicles may be rented and left, and inside it slow zones and no-ride zones cover pedestrian streets, parks and waterfronts. The zones sit edge to edge, so redrawing one street boundary has to update both zones that meet there.

  • Move a slow-zone boundary once for both zones
  • Split the operating area when a new district opens
  • Cut a waterfront strip off the operating area edge
  • Take a park at the edge off the operating area with difference
  • Trace a new zone along existing zone borders
02

Parking spots and no-parking zones

Parking spots for scooters and bikes are small rectangles on pavements and squares, often placed in rows along a street. No-parking zones cover station entrances, crossings and narrow pavements where vehicles must not be left.

  • Draw parking spots with the rectangle tool
  • Copy a spot and rotate it to follow the kerb
  • Straighten hand-drawn spots into clean rectangles
  • Lasso-select a row of spots to move them together
  • Mark drop-off points with markers
03

One city, several operators

Cities often ask every operator to apply the same zone set, and operators run fleets in many cities at once. A layer tree with one layer per city or per operator keeps those sets apart, and a separate document holds each draft until it is agreed.

  • One layer per city or per operator in the layer tree
  • Keep a draft zone set for a city as its own document
  • Check a zone file from the city on import
  • Export the zones of each operator as GeoJSON

Why topology

Why mobility zones need shared borders

Zones that hand over cleanly

A rider crossing from a slow zone into a no-ride zone crosses one line. When that line is stored twice, a thin strip between the copies belongs to neither zone. vectorstream stores it once.

Drafts per city

Zone sets are negotiated city by city. Each draft lives in its own document, saved automatically in the browser, so a proposal for one city never mixes with the agreed set of another.

Fits the operations dashboard

Fleet operations dashboards run on Leaflet, OpenLayers or MapLibre GL. vectorstream puts the same editing core behind all three, so zone editing behaves alike in every tool the team uses.

How it works

How a fleet operations team uses it

  1. Step 01

    Load the city zones

    Import the operating area and the zones a city has shared as GeoJSON, one layer per city.

  2. Step 02

    Draw the street-level detail

    Add parking spots, no-parking areas and slow zones, snapping to existing corners.

  3. Step 03

    Adjust after feedback

    Move shared zone borders, split or merge zones and undo any change that should not stay.

  4. Step 04

    Hand over to the fleet backend

    Export the agreed zones as GeoJSON for the fleet system or the permit portal of the city.

FAQ

Micromobility and shared mobility questions

Can vectorstream keep slow zones and no-ride zones flush?
Yes. A slow zone and a no-ride zone that meet in vectorstream share one stored border, so redrawing the line along a street changes both zones together.
Can parking spots for scooters and shared bikes be drawn quickly?
vectorstream draws parking spots with the rectangle tool, and copying and rotating a spot lines up a row of them along a kerb.
Can zones for several cities or operators be kept apart?
vectorstream organises shapes in a layer tree, so a team can keep one layer per city or per operator and show or hide each set on its own.
Does vectorstream slow down or stop vehicles in a zone?
No. vectorstream edits zone polygons. Speed limits and parking rules are applied by the fleet software that receives the zones from vectorstream as GeoJSON.
Which map libraries can a fleet dashboard use with vectorstream?
A fleet or city dashboard on Leaflet, OpenLayers or MapLibre GL can add vectorstream, because one editing core drives all three adapters.

More questions

Keep every city zone set flush.