Coverage Zones
Example polygons for delivery zones, coverage areas or service regions.
About this Spatial Dataset
Six adjacent service-area polygons with a category and a coverage rating on each, shaped the way operational zone data usually is: they share edges, so they are the right dataset for testing union, difference and overlap detection, and for checking that a point-in-polygon lookup returns exactly one zone rather than two along a shared border. The category and coverage fields give you something real to drive categorical styling and filtering from.
- Geometry type: Polygon (6 features).
- Coordinate Reference System (CRS): EPSG:4326 (Longitude / Latitude).
- Format: GeoJSON FeatureCollection.
- Source: Synthetic geometry authored for WKT Studio.
- Licence: Public domain — example data, free to use and modify.
- Compatible With: PostGIS, QGIS, Leaflet, Mapbox GL JS, Turf.js, Python GeoPandas, Shapely.
Feature properties
Every feature in the FeatureCollection carries these keys.
| Property | Type | Description |
|---|---|---|
| name | string | Zone label, e.g. "North Zone". |
| category | string | Zone type, e.g. "delivery" — useful for testing categorical styling. |
| coverage | string | Service level: high, medium or low. |
| color | string | Hex colour used for the default fill style. |
Frequently Asked Questions
Do the zones overlap?+
They share borders but are not meant to overlap in area. That makes them a good control case: a correct point-in-polygon query should return exactly one zone for any interior point, and a union of all six should produce a single polygon with no internal gaps.
Can I use this as a starting point for my own service areas?+
Yes. Import the template, then redraw the boundaries over your own city with the polygon tool and edit the category and coverage values in the attribute table. Export as GeoJSON or PostGIS SQL when the shapes are right.