Sample Routes
Example lines for logistics routes, roads or transit paths.
About this Spatial Dataset
Five LineString features modelled on urban delivery and transit corridors, each carrying a pre-computed length in kilometres. Line geometry behaves differently from polygons in almost every operation that matters — buffering produces a corridor rather than a ring, length replaces area, and simplification can drop the vertices that define a turn — so this is a deliberately small set for checking that a routing, tracking or corridor-analysis pipeline handles LineStrings correctly before real GPS traces go through it.
- Geometry type: LineString (5 features).
- Coordinate Reference System (CRS): EPSG:4326 (Longitude / Latitude).
- Format: GeoJSON FeatureCollection.
- Source: Synthetic geometry authored for WKT Studio, loosely based on Lima–Callao corridors.
- 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 | Route label, e.g. "Central Lima - Callao Route". |
| distance_km | number | Route length in kilometres, pre-computed so you can verify your own length calculations against it. |
| color | string | Hex colour used for the default stroke style. |
Frequently Asked Questions
Is this real road network data?+
No. These are synthetic corridors for testing and demos. For real road geometry, use OpenStreetMap extracts or a routing API — this dataset exists so you can exercise LineString handling without waiting on a download.
What can I use it to test?+
Buffer corridors around a path, total length in metres or kilometres, snapping and vertex editing, and how your styling handles stroke width and dash patterns on lines rather than polygon fills.