How corridor context fits into your integrity workflow.
The input we accept, the records we return for each legal subdivision and crossing, where every value comes from, and how the files reach you during the pilot.
A centreline as GeoJSON (LineString or MultiLineString) and a buffer width in metres
- Request and summary
- Per-LSD records
- Crossing records
- Map layers
- Provenance
Send a centreline and a few settings.
The corridor pack takes geometry only: we find the intersected LSDs for you. Lists of legal land descriptions are not accepted yet, and the line has to run through the DLS grid in Alberta, Saskatchewan, or Manitoba (British Columbia NTS areas are not supported).
Centreline geometry
A GeoJSON LineString or MultiLineString in WGS84, sent as a bare geometry, a Feature, or a FeatureCollection. Feature properties are ignored. We buffer the line on the ellipsoid and intersect it with the LSD grid, up to 400 LSDs and 250 km per request, so split longer lines.
Request settings
The asset ID, buffer width, and your own licence numbers are set once for the whole request, not per feature. The buffer runs from 5 to 2,000 m (100 m by default). Segments on the licences you list are left out and reported as a count, so your own line is not counted as a crossing.
One record per intersected LSD, plus crossings and sources.
Each section lists the sources it uses. Where a province does not publish a value, the field is empty. The Coverage column shows where each field is available.
Request and summary
One per pack.
| Field | Description | Coverage |
|---|---|---|
input.asset_id | Your identifier, passed through unchanged | All |
input.buffer_m | Buffer width used, in metres | All |
input.excluded_licences | The licence numbers you asked us to leave out | All |
summary | One factual sentence: length, LSDs, crossings, and wells in the buffer | All |
highlights[] | Corridor length, LSDs, pipeline and water crossings, wells and facilities in the buffer | All |
Per-LSD records
records.lsds[]: one per intersected LSD, in chainage order. The CSV has one row per LSD.
| Field | Description | Coverage |
|---|---|---|
legal_location | Legal subdivision (DLS) | AB, SK, MB |
chainage_start_m, chainage_end_m | Where the centreline enters and leaves the LSD, in metres from the start of the line (empty when only the buffer touches it) | All |
centreline_m | Metres of centreline inside the LSD | All |
wells_in_buffer | Wells in the LSD that sit inside the buffer | AB, SK, MB |
orphan_in_buffer, abandoned_in_buffer | Orphan and abandoned wells among them | Orphan: AB, SK. Abandoned: AB, SK, MB |
reclaimed_in_buffer | Wells among them with an AER reclamation certificate or exemption | AB |
facilities_in_buffer | Facilities inside the buffer in the LSD | AB, SK |
pipeline_crossings | Number of published pipelines crossing the centreline in the LSD | AB, SK |
water_crossings | Number of mapped watercourse and water body crossings in the LSD | AB, SK, MB |
land_use | AAFC land-use class of the parent quarter section | AB, SK, MB |
drought_class | Current Canadian Drought Monitor class at the LSD | AB, SK, MB |
Crossing records
records.crossings[]: one per point where a pipeline or mapped water meets the centreline, in chainage order.
| Field | Description | Coverage |
|---|---|---|
type | pipeline, tie-in (a line end on the centreline), watercourse, or water_body | All |
chainage_m | Distance along the line to the crossing, in metres | All |
lsd | The LSD the crossing falls in | AB, SK, MB |
licence, line | Regulator licence and line number of a crossed pipeline | AB, SK |
operator | Licensee of the crossed pipeline | AB, SK |
substance, status | What the crossed pipeline carries and its status | AB, SK |
name | Name of a crossed watercourse or water body, where mapped | AB, SK, MB |
lat, lng | Crossing point, WGS84 | All |
Map layers
pack.geojson: one FeatureCollection, with properties.role naming each layer.
| Field | Description | Coverage |
|---|---|---|
role: buffer | The buffered corridor, with buffer_m | All |
role: lsd | LSD polygons with centreline_m, a well count, and pipelines crossed | AB, SK, MB |
role: centreline | Your line, with asset_id | All |
role: crossing | Crossing points, with crossing_type (pipeline, tie-in, watercourse, water_body) | All |
role: well, facility | Wells and facilities inside the buffer, with status and distance | Wells: AB, SK, MB. Facilities: AB, SK |
Provenance
One entry per dataset the pack used.
| Field | Description | Coverage |
|---|---|---|
provenance[].dataset, publisher | Dataset name and who publishes it | All |
provenance[].licence, refresh | Open-data licence and refresh cadence | All |
provenance[].as_of | Data date read from our load logs; empty when only the cadence is known | All |
unavailable[] | What the pack could not cover and why, such as road and railway crossings | All |
How the files are built and how they reach you.
Provenance and data vintage
Every pack carries a provenance list: dataset, publisher, licence, refresh cadence, and an as-of date read from our load logs where one is recorded. Alberta regulator wells, pipelines, and facilities refresh monthly, Saskatchewan loads run weekly to monthly, the Drought Monitor refreshes monthly, and the AAFC crop inventory is annual. The pack also records the date it was generated.
Delivery today
Pilot by file exchange. You send the GeoJSON and the request settings. We return JSON (the full pack, including the wells and facilities inside the buffer), CSV (one row per LSD), GeoJSON (the map layers above), and a printable report. The request and response shape for a future endpoint is drafted as a v0.1 spec. There is no live endpoint yet.
Coordinate reference system
WGS84 (EPSG:4326) for input and output, longitude then latitude, as in the GeoJSON specification. Buffer widths, chainage, and lengths are in metres.
Field names
Field names follow the v0.1 pack spec and may change before an endpoint is published. Your asset ID is always passed through unchanged.
External context only.
The pack is not an integrity assessment. Operator integrity data stays in your system, and the pack does not try to replace or infer it.
- Inline inspection (ILI) results
- Corrosion, dents, cracks, and coating condition
- Cathodic protection (CP) data
- Wall thickness, pressure cycling, and repair history
- SCADA and operating history
- Any other operator-held integrity data
- Risk scores or failure probabilities
- Maximum operating pressure and H2S content per crossing
- Road and railway crossings (not in the product yet)
- Manitoba pipelines and facilities, and British Columbia (NTS) corridors
Send a corridor. Get the context back as files.
We run the pack for your centreline and send you JSON, CSV, GeoJSON, and a printable report.