OPERATIONAL/INCIDENT_LOCATION

View In: ArcGIS JavaScript ArcGIS Online Map Viewer

Service Description: <div style='text-align:Left;'><div><div>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<table><tbody><tr><td>Attributes / Column Name</td><td>Field Alias</td><td>Data Type</td><td>Data Precision</td><td>Comments</td></tr><tr><td>OBJECTID</td><td>OBJECTID</td><td>Object ID</td><td>10</td><td>Unique row value assigned by database</td></tr><tr><td>SHAPE</td><td>SHAPE</td><td>Geometry (Point)</td><td></td><td></td></tr><tr><td>INCIDENT_ID</td><td>Incident ID</td><td>Text</td><td>15</td><td>Unique identifier for each incident.</td></tr><tr><td>SITE_TYPE</td><td>Site Type</td><td>Text</td><td>255</td><td>Type of site where the incident occurred. e.g., pipeline, Riser, etc.</td></tr><tr><td>PERMIT_HOLDER</td><td>Permit Holder</td><td>Text</td><td>255</td><td>Name of the company responsible for the pipeline.</td></tr><tr><td>INCIDENT_DATE</td><td>Incident Date</td><td>Date</td><td></td><td>Date when the incident occurred.</td></tr><tr><td>UTMZONE</td><td>UTM Zone</td><td>Short</td><td>5</td><td></td></tr><tr><td>UTMNORTHING</td><td>UTM Northing</td><td>Double</td><td>10</td><td></td></tr><tr><td>UTMEASTING</td><td>UTM Easting</td><td>Double</td><td>9</td><td></td></tr><tr><td>SPILL_FLAG</td><td>Spill (Y/N)</td><td>Text</td><td>3</td><td>Indicates whether a spill occurred, i.e., Yes, No</td></tr><tr><td>SPILL_PRODUCT</td><td>Spill Product</td><td>Text</td><td>255</td><td>Type of product spilled (if applicable)</td></tr><tr><td>SPILL_VOLUME_M3</td><td>Spill Volume (m3)</td><td>Double</td><td>4</td><td>Spill volume (if applicable) in cubic meters.</td></tr><tr><td>SPILL_VOLUME_STATUS</td><td>Spill Volume Status</td><td>Text</td><td>18</td><td>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.</td></tr><tr><td>CAUSE</td><td>Cause</td><td>Text</td><td>255</td><td>CAUSE is a value indicating of failure cause classification of the incident, e.g., Metal Loss, Construction Defect, Cracking, External Factors, etc… </td></tr><tr><td>CAUSE_DESCRIPTION</td><td>Cause Description</td><td>Text</td><td>1000</td><td></td></tr></tbody></table>Renewal Triggers and Service Levels<ol><li> Nightly</li></ol></div></div></div>

All Layers and Tables

Has Versioned Data: false

MaxRecordCount: 2000

Supported Query Formats: JSON

Supports Query Data Elements: true

Layers:

Incidents in BC (0)

Description: 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 NameField AliasData TypeData PrecisionCommentsOBJECTIDOBJECTIDObject ID10Unique row value assigned by databaseSHAPESHAPEGeometry (Point)INCIDENT_IDIncident IDText15Unique identifier for each incident.SITE_TYPESite TypeText255Type of site where the incident occurred. e.g., pipeline, Riser, etc.PERMIT_HOLDERPermit HolderText255Name of the company responsible for the pipeline.INCIDENT_DATEIncident DateDateDate when the incident occurred.UTMZONEUTM ZoneShort5UTMNORTHINGUTM NorthingDouble10UTMEASTINGUTM EastingDouble9SPILL_FLAGSpill (Y/N)Text3Indicates whether a spill occurred, i.e., Yes, NoSPILL_PRODUCTSpill ProductText255Type of product spilled (if applicable)SPILL_VOLUME_M3Spill Volume (m3)Double4Spill volume (if applicable) in cubic meters.SPILL_VOLUME_STATUSSpill Volume StatusText18When 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.CAUSECauseText255CAUSE is a value indicating of failure cause classification of the incident, e.g., Metal Loss, Construction Defect, Cracking, External Factors, etc… CAUSE_DESCRIPTIONCause DescriptionText1000Renewal Triggers and Service Levels Nightly

Service Item Id: 1a8e4cfd101044bf9d7ec987c83745c6

Copyright Text: BC Energy Regulator

Spatial Reference: 102190 (3005) LatestVCSWkid(0)

Initial Extent:

Full Extent:

Units: esriMeters

Document Info:

Enable Z Defaults: false

Supports ApplyEdits With Global Ids: false

Support True Curves : true

Only Allow TrueCurve Updates By TrueCurveClients : false

Supports Return Service Edits Option : true

Supports Dynamic Layers: false

Child Resources: Info Query Data Elements Relationships SharedTemplates

Supported Operations: Query Query Contingent Values QueryDomains Extract Changes

OPERATIONAL/INCIDENT_LOCATION_PT (FeatureServer)