Incidents in BC
Incidents in BC locations as provided through the BCER's Audit and Integrity Engineering group locations of pipeline incidents by year in the province.
The Incidents in BC locations are a subset of all other incidents that are reported to the BCER through an incident reporting system. The incidents layer represents pipeline incidents that occurred on pipelines that are in active, deactivated or abandoned status and includes a brief description of the incident cause.
The associated attribute table contains details that elaborate on the incident information.
Data Properties
Attributes / Column Name
Field Alias
Data Type
Data Precision
Comments
OBJECTIDOBJECTID
Object ID
10
Unique row value assigned by databaseSHAPESHAPE
Geometry (Point)
INCIDENT_ID
Incident ID
Text
15
Unique identifier for each incident.SITE_TYPESite Type
Text
255
Type of site where the incident occurred.
e.g., pipeline, Riser, etc.
PERMIT_HOLDERPermit Holder
Text
255
Name of the company responsible for the pipeline.INCIDENT_DATEIncident Date
Date
Date when the incident occurred.UTMZONE
UTM Zone
Short
5
UTMNORTHINGUTM Northing
Double
10
UTMEASTINGUTM Easting
Double
9
SPILL_FLAGSpill (Y/N)
Text
3
Indicates whether a spill occurred, i.e., Yes, NoSPILL_PRODUCTSpill Product
Text
255
Type of product spilled (if applicable)SPILL_VOLUME_M3Spill Volume (m3)
Double
4
Spill volume (if applicable) in cubic meters.SPILL_VOLUME_STATUSSpill Volume Status
Text
18
When no spill volume is reported the status indicates the reason why: Null, Unknown, Not Applicable, Historical No Data. When a spill volume has a value this value will be null.CAUSECause
Text
255
CAUSE is a value indicating of failure cause classification of the incident, e.g., Metal Loss, Construction Defect, Cracking, External Factors, etc… CAUSE_DESCRIPTIONCause Description
Text
1000
Renewal Triggers and Service Levels
Nightly
Contact Information
For further information please contact
BC Energy Regulator [email protected]
Datasets available for download
-
Incidents in BCFeature Layer
Layer 0 via ArcGIS REST API
Additional Info
| Field | Value |
|---|---|
| Last Updated | August 15, 2026, 07:13 (UTC) |
| Created | March 24, 2026, 21:09 (UTC) |
|
Domain / Topic
Domain or topic of the dataset being cataloged.
|
|
|
Title
Title for the Dataset.
|
Incidents in BC |
|
Description
A description of the dataset.
|
Incidents in BC locations as provided through the BCER's Audit and Integrity Engineering group locations of pipeline incidents by year in the province. The Incidents in BC locations are a subset of all other incidents that are reported to the BCER through an incident reporting system. The incidents layer represents pipeline incidents that occurred on pipelines that are in active, deactivated or abandoned status and includes a brief description of the incident cause. The associated attribute table contains details that elaborate on the incident information. Data PropertiesAttributes / Column Name Field Alias Data Type Data Precision Comments OBJECTIDOBJECTID Object ID 10 Unique row value assigned by databaseSHAPESHAPE Geometry (Point) INCIDENT_ID Incident ID Text 15 Unique identifier for each incident.SITE_TYPESite Type Text 255 Type of site where the incident occurred. e.g., pipeline, Riser, etc. PERMIT_HOLDERPermit Holder Text 255 Name of the company responsible for the pipeline.INCIDENT_DATEIncident Date Date Date when the incident occurred.UTMZONE UTM Zone Short 5 UTMNORTHINGUTM Northing Double 10 UTMEASTINGUTM Easting Double 9 SPILL_FLAGSpill (Y/N) Text 3 Indicates whether a spill occurred, i.e., Yes, NoSPILL_PRODUCTSpill Product Text 255 Type of product spilled (if applicable)SPILL_VOLUME_M3Spill Volume (m3) Double 4 Spill volume (if applicable) in cubic meters.SPILL_VOLUME_STATUSSpill Volume Status Text 18 When no spill volume is reported the status indicates the reason why: Null, Unknown, Not Applicable, Historical No Data. When a spill volume has a value this value will be null.CAUSECause Text 255 CAUSE is a value indicating of failure cause classification of the incident, e.g., Metal Loss, Construction Defect, Cracking, External Factors, etc… CAUSE_DESCRIPTIONCause Description Text 1000 Renewal Triggers and Service Levels
Contact Information For further information please contact BC Energy Regulator [email protected]
|
|
Tags / Keywords
Keywords/tags categorizing the dataset.
|
|
|
Format (CSV, XLS, TXT, PDF, etc)
File format of the dataset.
|
|
|
Dataset Size
Dataset size in megabytes.
|
0.09 |
|
Metadata Identifier
Metadata identifier – can be used as the unique identifier for catalogue entry
|
|
|
Published Date
Published date of the dataset.
|
2025-05-09 |
|
Time Period Data Span (start date)
Start date of the data in the dataset.
|
|
|
Time Period Data Span (end date)
End date of time data in the dataset.
|
|
|
GeoSpatial Area Data Span
A spatial region or named place the dataset covers.
|
| Field | Value |
|---|---|
|
Access category
Type of access granted for the dataset (open, closed, service, etc).
|
public |
|
License
License used to access the dataset.
|
This data is for representation purposes only. The BC Energy Regulator provides this data "as is" with the understanding that it is not guaranteed to be accurate, correct or complete and conclusions drawn from such information are the responsibility of the user. It carries no guarantee of any kind, express or implied. Please review the BCER Open Data License for complete details. |
|
Limits on use
Limits on use of data.
|
|
|
Location
Location of the dataset.
|
https://data-bc-er.opendata.arcgis.com/datasets/d3663d0c1f61408eb2f51f4db69846da |
|
Data Service
Data service for accessing a dataset.
|
|
|
Owner
Owner of the dataset.
|
BC_Energy_Regulator |
|
Contact Point
Who to contact regarding access?
|
|
|
Contact Point Email
The email to contact regarding access?
|
|
|
Publisher
Publisher of the dataset.
|
|
|
Publisher Email
Email of the publisher.
|
|
|
Author
Author of the dataset.
|
BC_Energy_Regulator |
|
Author Email
Email of the author.
|
|
|
Accessed At
Date the data and metadata was accessed.
|
2026-08-14 |
| Field | Value |
|---|---|
|
Identifier
Unique identifier for the dataset.
|
d3663d0c1f61408eb2f51f4db69846da |
|
Language
Language(s) of the dataset
|
English |
|
Link to dataset description
A URL to an external document describing the dataset.
|
https://data-bc-er.opendata.arcgis.com/datasets/d3663d0c1f61408eb2f51f4db69846da |
|
Persistent Identifier
Data is identified by a persistent identifier.
|
|
|
Globally Unique Identifier
Data is identified by a persistent and globally unique identifier.
|
|
|
Contains data about individuals
Does the data hold data about individuals?
|
|
|
Contains data about identifiable individuals
Does the data hold identifiable data about individual?
|
|
|
Contains Indigenous Data
Does the data hold data about Indigenous communities?
|
|
|
Portal Type
Platform type of the source portal.
|
| Field | Value |
|---|---|
|
Version
Version of the datatset
|
None |
|
Source
Source of the dataset.
|
None |
|
Version notes
Version notes about the dataset.
|
|
|
Is version of another dataset
Link to dataset that it is a version of.
|
|
|
Other versions
Link to datasets that are versions of it.
|
|
|
Provenance Text
Provenance Text of the data.
|
|
|
Provenance URL
Provenance URL of the data.
|
|
|
Temporal resolution
Describes how granular the date/time data in the dataset is.
|
|
|
GeoSpatial resolution in meters
Describes how granular (in meters) geospatial data is in the dataset.
|
|
|
GeoSpatial resolution (in regions)
Describes how granular (in regions) geospatial data is in the dataset.
|
| Field | Value |
|---|---|
|
Indigenous Community Permission
Who holds the Indigenous Community Permission. Who to contact regarding access to a dataset that has data about Indigenous communities.
|
|
|
Community Permission
Community permission (who gave permission).
|
|
|
The Indigenous communities the dataset is about
Indigenous communities from which data is derived.
|
| Field | Value |
|---|---|
|
Number of data rows
If tabular dataset, total number of rows.
|
471 |
|
Number of data columns
If tabular dataset, total number of unique columns.
|
21 |
|
Number of data cells
If tabular dataset, total number of cells with data.
|
9891 |
|
Number of data relations
If RDF dataset, total number of triples.
|
|
|
Number of entities
If RDF dataset, total number of entities.
|
|
|
Number of data properties
If RDF dataset, total number of unique properties used by the triples.
|
|
|
Data quality
Describes the quality of the data in the dataset.
|
|
|
Metric for data quality
A metric used to measure the quality of the data, such as missing values or invalid formats.
|
0 Comments