Pipeline integrity · Pilot

External land and infrastructure context for your pipeline corridor.

Send a centreline as GeoJSON and a buffer width. We return one record per intersected LSD, in chainage order, with wells, facilities, pipeline and water crossings, land use, and drought, and the source and data date on every section.

325K+
Pipeline segments (AB)
532K+
Wells tracked (AB)
125K+
Facilities (AB)
Request a sample packTechnical integration
Evidence pack
Pipeline Corridor Context Pack
You send

A centreline as GeoJSON (LineString or MultiLineString) and a buffer width in metres

The pack returns
  • Intersected LSDs
  • Pipeline and water crossings
  • Wells
  • Facilities
  • Land use
  • Drought
  • Source and data date
You get
JSONCSVGeoJSONPrintable report
The job it removes

Less portal work before the real work.

Integrity systems hold inspection, repair, and operating history. The external picture along the line usually means looking up wells, crossing lines, facilities, land use, and water one legal location at a time, across regulator and agriculture sources. The pack assembles that context for every LSD the corridor touches and names the source of each value.

Who it is for

Integrity engineers and consultants

External threat and consequence context for the legal locations a line crosses, next to the inspection data you already hold.

Pipeline software vendors

A land and infrastructure context layer you can load into an integrity or GIS platform instead of building one.

Land and right-of-way teams

What else sits on each LSD along the route: wells, other lines, facilities, cropland, and water crossings.

What's in the pack

One record per LSD the corridor touches.

Records run in chainage order from the start of the line, and every section carries its dataset, publisher, and data date. The corridor summary rolls up LSD count, pipeline and water crossings, segments crossed, wells and orphan wells in the buffer, and the substances in crossed lines.

Intersected LSDs
Buffer in metres
Every legal subdivision the buffered centreline intersects, with chainage and the metres of centreline inside it. Your asset ID is passed through.
Pipeline and water crossings
AB · SK · 1:50,000 water
Every point where a published pipeline, a mapped watercourse, or a water body meets your centreline, with chainage. Pipeline crossings list licence and line, licensee, substance, status, and diameter where published. Tie-ins at line ends are listed separately.
Wells
AB · SK · MB
Wells in each LSD and within the buffer, with licence status, licensee, distance from the centreline, and abandoned and orphan flags. Orphan flags come from the AER well list and the Orphan Well Association inventory in Alberta, and the orphan sites list in Saskatchewan.
Facilities
AB · SK
Facilities within the buffer, with category, status, licensee, and distance from the centreline.
Land use
AAFC
The AAFC land-use class of each LSD's parent quarter section, and centreline length by land-use class.
Drought
Canadian Drought Monitor
The current Canadian Drought Monitor class at each LSD.
Source and data date
Every section
Each section names its dataset and publisher, with the licence, refresh cadence, and an as-of date where the data load records one, so you can cite it or check it.
Real sample

Pipeline Corridor Context Pack

The 32.6 km centreline touches 136 LSDs in 62 quarter sections, has 42 crossing points with 40 other published pipeline segments and 18 mapped water crossings, and has 10 wells within 100 m (3 orphan, 4 abandoned, 1 reclaimed).

Input: Gas line crossing the Red Deer River valley, Kneehill and Starland counties (public AER licence 80574 centreline as a stand-in) Generated 2026-09-22
Corridor length
32.6 km
LSDs intersected
136

100 m buffer

Pipeline crossings
42

40 segments crossed

Water crossings
18

1:50,000 mapping

Wells within buffer
10

3 orphan

Facilities within buffer
5

Flags

32.6 km centreline across 136 LSDs at a 100 m buffer.
42 crossing points with 40 other published pipeline segments (Natural Gas).
2 points where another published segment meets the centreline at a line end (tie-in or shared node).
18 mapped water crossings on 1:50,000 hydrology.
3 orphan wells within 100 m of the centreline.
4 abandoned wells within 100 m of the centreline.
1 reclaimed well (AER reclamation certified or exempt) within 100 m of the centreline.

Crossings of the centreline (showing 25 of 62 rows)

Chainage (km)TypeFeatureDetailLicenseeDiameterLSD
0.00Pipeline58004-6Natural Gas, OperatingPine Cliff Energy Ltd.168 mm5-34-30-22-W4
1.54WatercourseGhostpine CreekMapped channel--3-33-30-22-W4
3.26Pipeline57869-39Natural Gas, OperatingPine Cliff Energy Ltd.114 mm14-29-30-22-W4
3.28Pipeline45287-82Natural Gas, AbandonedLexin Resources Ltd.89 mm14-29-30-22-W4
3.85WatercourseUnnamed watercourseMapped channel--12-29-30-22-W4
4.94Pipeline42762-1Natural Gas, OperatingPine Cliff Energy Ltd.89 mm2-30-30-22-W4
5.66Pipeline49514-2Natural Gas, OperatingPine Cliff Energy Ltd.219 mm14-19-30-22-W4
6.55WatercourseUnnamed watercourseMapped channel--9-24-30-23-W4
6.81Pipeline57886-38Natural Gas, OperatingPine Cliff Energy Ltd.114 mm8-24-30-23-W4
6.93WatercourseUnnamed watercourseMapped channel--7-24-30-23-W4
7.49Pipeline57886-142Natural Gas, OperatingPine Cliff Energy Ltd.168 mm2-24-30-23-W4
7.55Pipeline49514-1Natural Gas, OperatingPine Cliff Energy Ltd.273 mm2-24-30-23-W4
8.00Pipeline45287-65Natural Gas, OperatingLexin Resources Ltd.89 mm15-13-30-23-W4
8.32WatercourseUnnamed watercourseMapped channel--10-13-30-23-W4
8.67WatercourseThreehills CreekMapped channel--11-13-30-23-W4
9.24Pipeline tie-in61658-3Natural Gas, Operating, meets the centreline at a line endPine Cliff Energy Ltd.324 mm5-13-30-23-W4
9.27Pipeline57886-241Natural Gas, OperatingPine Cliff Energy Ltd.168 mm5-13-30-23-W4
9.49Pipeline57869-15Natural Gas, OperatingPine Cliff Energy Ltd.114 mm8-14-30-23-W4
10.17Pipeline tie-in45287-13Natural Gas, Abandoned, meets the centreline at a line endLexin Resources Ltd.168 mm16-11-30-23-W4
10.31Pipeline62764-2Natural Gas, OperatingPine Cliff Energy Ltd.324 mm16-11-30-23-W4
10.69Pipeline45287-10Natural Gas, AbandonedLexin Resources Ltd.356 mm10-11-30-23-W4
10.73WatercourseUnnamed watercourseMapped channel--10-11-30-23-W4
11.48WatercourseUnnamed watercourseMapped channel--3-11-30-23-W4
11.78Pipeline57886-37Natural Gas, OperatingPine Cliff Energy Ltd.89 mm3-11-30-23-W4
12.49WatercourseUnnamed watercourseMapped channel--16-3-30-23-W4

Per-LSD context (showing 8 of 136 rows)

Chainage (km)LSDCentreline in LSDWells in LSDAbandonedOrphanPipelines crossedPipelines in bufferFacilities in bufferWater crossingsLand use (quarter)Drought now
0.005-34-30-22-W4271 m2004000CroplandD0
0.014-34-30-22-W4383 m0000000CroplandD0
0.421-33-30-22-W4400 m0000000Prairie grasslandD0
0.812-33-30-22-W4400 m1100000Prairie grasslandD0
1.213-33-30-22-W4401 m0000001Prairie grasslandD0
1.614-33-30-22-W4401 m0000000Prairie grasslandD0
2.031-32-30-22-W4400 m0000000Vegetated settlementD0
2.432-32-30-22-W4461 m0000000Vegetated settlementD0

Wells within 100 m of the centreline (showing 8 of 10 rows)

UWI / licenceLicenceStatusLicenseeOrphanOrphan inventoryDistance
00/05-13-030-23W4/00398377AbandonedLexin Resources Ltd.YesOWA: Environment92 m
00/03-11-030-23W4/00362137AbandonedLexin Resources Ltd.YesOWA: Environment82 m
00/06-03-030-23W4/00360161AbandonedLexin Resources Ltd.YesOWA: Environment99 m
00/16-33-029-23W4/00334878IssuedLynx Energy ULCNo-78 m
00/05-34-030-22W4/00018313IssuedPine Cliff Energy Ltd.No-89 m
00/01-11-031-21W4/00161373IssuedPine Cliff Energy Ltd.No-91 m
00/14-02-031-21W4/0M0004386FRecExemptGulf Canada LimitedNo-20 m
00/11-04-031-21W4/00381896AbandonedPine Cliff Energy Ltd.No-75 m

Sources

DatasetPublisherRefreshAs of
Township Canada DLS grid (quarter and LSD polygons)Township CanadaStatic grid 
Municipal boundariesTownship Canada compilationNot documented 
Watercourses and water bodies, 1:50,000Township Canada compilationNot documented 
AAFC Annual Crop Inventory (quarter-section rollup)Agriculture and Agri-Food CanadaAnnual2021 to 2025 crop years
AAFC Land Use (quarter-section rollup)Agriculture and Agri-Food CanadaAnnual2026-06
Canadian Drought Monitor (current month)Agriculture and Agri-Food CanadaMonthly2026-08
AER ST37 List of WellsAlberta Energy RegulatorMonthly2026-09
AER ST76 Pipeline SystemAlberta Energy RegulatorMonthly2026-09
AER ST102 Facility ListAlberta Energy RegulatorMonthly2026-09
Orphan Well Association inventoryOrphan Well AssociationMonthly2026-09
External land, infrastructure, and environmental context from public records. Not an integrity assessment: it excludes in-line inspection, corrosion, cathodic protection, coating, and operating data, and it assigns no risk score.
Request this pack for your parcels
What it is not

Evidence for a professional, not the professional's work.

The Pipeline Corridor Context Pack assembles what the public record shows. The judgment, the site work, and the signature stay with you.

  • Not an integrity assessment, risk score, or failure probability.
  • No inline inspection, corrosion, dents or cracks, coating, cathodic protection, wall thickness, pressure cycling, repair, or SCADA data. That stays in your integrity system.
  • Not a crossing survey or engineering review. Water is 1:50,000 mapped hydrology that crosses your centreline or sits inside your buffer, not an inspection.
  • No road or railway crossings. Those layers are not in the product yet.
  • Crossing records carry diameter, not maximum operating pressure or H2S content per crossing. The summary counts crossed Alberta segments whose record lists H2S.
  • Pipelines and facilities cover Alberta and Saskatchewan. Manitoba LSDs report wells only, and British Columbia (NTS) corridors are not supported yet.
Pilot

Request a sample pack for your parcels.

We run the pack for your parcels and send you the files. No account or checkout needed for the pilot.

  1. 1. Send your parcels

    Legal land descriptions (DLS quarter sections or LSDs in Alberta, Saskatchewan, or Manitoba), or a corridor as a GeoJSON line. A handful is enough for a first pack.

  2. 2. We run the pack

    We build the pack from the same data behind the Township Canada parcel report, with the source and data date on every section.

  3. 3. You get the files

    JSON, CSV, and GeoJSON for your own tools, plus a printable report you can put in the file.

Request a sample pack for your parcels Technical integration
FAQ

Common questions

Does this replace our integrity management system?
No. It adds external land, infrastructure, and environmental context to the legal locations your line crosses. Operator integrity data (inline inspection, corrosion, cathodic protection, SCADA) stays where it is.
What do we need to send?
A GeoJSON LineString, MultiLineString, or FeatureCollection in WGS84, plus two settings for the whole request: an asset ID and a buffer width in metres (100 m by default). You can also list your own licence numbers so your line is not counted as a crossing. Lists of legal land descriptions are not accepted for corridor packs yet. The integration page has the exact input and output shape.
Is there an API?
Not yet. During the pilot we deliver files (JSON, CSV, GeoJSON, and a printable report). The request and response shape for a future endpoint is drafted, and we can share it with design partners who want to build against it.
Which provinces are covered?
Wells in Alberta, Saskatchewan, and Manitoba. Pipelines and facilities in Alberta and Saskatchewan. Land use, drought, and 1:50,000 water in all three. The line has to run through the DLS grid: British Columbia NTS areas are not supported yet.
Is there a risk score?
No. The pack reports what the public record shows on each parcel. How that context feeds a risk model is your team's decision.
How current is the data?
Alberta regulator well, pipeline, and facility data refresh monthly, and Saskatchewan loads run weekly to monthly. The Canadian Drought Monitor refreshes monthly and the AAFC crop inventory is annual. Every section names its source and refresh cadence, with an as-of date where the data load records one, so you can see which vintage you are looking at.
Related

Available today

Technical integration

Input formats, output fields, CRS, provenance, and delivery.

Learn more

Energy Bundle

Wells, pipelines, facilities, and tenure on every parcel report in the app.

Learn more

Developer APIs

Energy and Agriculture report APIs keyed by legal land description.

Learn more

Pricing

Plans, add-on bundles, and API tiers that are available today.

Learn more