{ "currentVersion": 11.3, "cimVersion": "3.3.0", "serviceDescription": "

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. <\/span><\/span><\/p>

The associated attribute table contains details that elaborate on the incident information.<\/span><\/span><\/p>

Data Properties<\/span><\/span><\/p>

Attributes / Column Name<\/span><\/span><\/p><\/td>

Field Alias<\/span><\/span><\/p><\/td>

Data Type<\/span><\/span><\/p><\/td>

Data Precision<\/span><\/span><\/p><\/td>

Comments<\/span><\/span><\/p><\/td><\/tr>

OBJECTID<\/span><\/span><\/p><\/td>

OBJECTID<\/span><\/span><\/p><\/td>

Object ID<\/span><\/span><\/p><\/td>

10<\/span><\/span><\/p><\/td>

Unique row value assigned by database<\/span><\/span><\/p><\/td><\/tr>

SHAPE<\/span><\/span><\/p><\/td>

SHAPE<\/span><\/span><\/p><\/td>

Geometry<\/span><\/span> (Point)<\/span><\/span><\/p><\/td>

<\/td>

<\/td><\/tr>

INCIDENT_ID<\/span><\/span><\/p><\/td>

Incident ID<\/span><\/span><\/p><\/td>

Text<\/span><\/span><\/p><\/td>

15<\/span><\/span><\/p><\/td>

Unique identifier for each incident.<\/span><\/span><\/p><\/td><\/tr>

SITE_TYPE<\/span><\/span><\/p><\/td>

Site Type<\/span><\/span><\/p><\/td>

Text<\/span><\/span><\/p><\/td>

255<\/span><\/span><\/p><\/td>

Type of site where the incident occurred. <\/span><\/span><\/p>

e.g., pipeline, Riser, etc.<\/span><\/span><\/p><\/td><\/tr>

PERMIT_HOLDER<\/span><\/span><\/p><\/td>

Permit Holder<\/span><\/span><\/p><\/td>

Text<\/span><\/span><\/p><\/td>

255<\/span><\/span><\/p><\/td>

Name of the company responsible for the pipeline.<\/span><\/span><\/p><\/td><\/tr>

INCIDENT_DATE<\/span><\/span><\/p><\/td>

Incident Date<\/span><\/span><\/p><\/td>

Date<\/span><\/span><\/p><\/td>

<\/td>

Date when the incident occurred.<\/span><\/span><\/p><\/td><\/tr>

UTMZONE<\/span><\/span><\/p><\/td>

UTM Zone<\/span><\/span><\/p><\/td>

Short<\/span><\/span><\/p><\/td>

5<\/span><\/span><\/p><\/td>

<\/td><\/tr>

UTMNORTHING<\/span><\/span><\/p><\/td>

UTM Northing<\/span><\/span><\/p><\/td>

Double<\/span><\/span><\/p><\/td>

10<\/span><\/span><\/p><\/td>

<\/td><\/tr>

UTMEASTING<\/span><\/span><\/p><\/td>

UTM Easting<\/span><\/span><\/p><\/td>

Double<\/span><\/span><\/p><\/td>

9<\/span><\/span><\/p><\/td>

<\/td><\/tr>

SPILL_FLAG<\/span><\/span><\/p><\/td>

Spill (Y/N)<\/span><\/span><\/p><\/td>

Text<\/span><\/span><\/p><\/td>

3<\/span><\/span><\/p><\/td>

Indicates whether a spill occurred, i.e., Yes, No<\/span><\/span><\/p><\/td><\/tr>

SPILL_PRODUCT<\/span><\/span><\/p><\/td>

Spill Product<\/span><\/span><\/p><\/td>

Text<\/span><\/span><\/p><\/td>

255<\/span><\/span><\/p><\/td>

Type of product spilled (if applicable)<\/span><\/span><\/p><\/td><\/tr>

SPILL_VOLUME_M3<\/span><\/span><\/p><\/td>

Spill Volume (m3)<\/span><\/span><\/p><\/td>

Double<\/span><\/span><\/p><\/td>

4<\/span><\/span><\/p><\/td>

Spill volume (if applicable) in cubic meters.<\/span><\/span><\/p><\/td><\/tr>

SPILL_VOLUME_STATUS<\/span><\/span><\/p><\/td>

Spill Volume Status<\/span><\/span><\/p><\/td>

Text<\/span><\/span><\/p><\/td>

18<\/span><\/span><\/p><\/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.<\/span><\/span><\/p><\/td><\/tr>

CAUSE<\/span><\/span><\/p><\/td>

Cause<\/span><\/span><\/p><\/td>

Text<\/span><\/span><\/p><\/td>

255<\/span><\/span><\/p><\/td>

CAUSE is a value indicating of failure cause classification of the incident, e.g., Metal Loss, Construction Defect, Cracking, External Factors, etc… <\/span><\/span><\/p><\/td><\/tr>

CAUSE_DESCRIPTION<\/span><\/span><\/p><\/td>

Cause Description<\/span><\/span><\/p><\/td>

Text<\/span><\/span><\/p><\/td>

1000<\/span><\/span><\/p><\/td>

<\/td><\/tr><\/tbody><\/table>

Renewal Triggers and Service Levels<\/span><\/span><\/p>

  1. Nightly<\/span><\/span><\/p><\/li><\/ol><\/div><\/div><\/div><\/p><\/p><\/p><\/p><\/p><\/p><\/p>", "mapName": "INCIDENT_LOCATION_PT", "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", "copyrightText": "BC Energy Regulator", "supportsDynamicLayers": true, "layers": [ { "id": 0, "name": "Incidents in BC", "parentLayerId": -1, "defaultVisibility": true, "subLayerIds": null, "minScale": 0, "maxScale": 0, "type": "Feature Layer", "geometryType": "esriGeometryPoint", "supportsDynamicLegends": true } ], "tables": [], "spatialReference": { "wkid": 102190, "latestWkid": 3005, "xyTolerance": 0.001, "zTolerance": 0.001, "mTolerance": 0.001, "falseX": -13239300, "falseY": -8610100, "xyUnits": 3.162795662266049E8, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 }, "singleFusedMapCache": false, "initialExtent": { "xmin": 249523.1322189126, "ymin": 290045.235076998, "xmax": 2091435.5505810878, "ymax": 1723869.2733230027, "spatialReference": { "wkid": 102190, "latestWkid": 3005, "xyTolerance": 0.001, "zTolerance": 0.001, "mTolerance": 0.001, "falseX": -13239300, "falseY": -8610100, "xyUnits": 3.162795662266049E8, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 } }, "fullExtent": { "xmin": 704320.8759, "ymin": 383431.8947, "xmax": 1799663.6977, "ymax": 1660842.1195, "spatialReference": { "wkid": 102190, "latestWkid": 3005, "xyTolerance": 0.001, "zTolerance": 0.001, "mTolerance": 0.001, "falseX": -13239300, "falseY": -8610100, "xyUnits": 3.162795662266049E8, "falseZ": -100000, "zUnits": 10000, "falseM": -100000, "mUnits": 10000 } }, "datesInUnknownTimezone": false, "minScale": 0, "maxScale": 0, "units": "esriMeters", "supportedImageFormatTypes": "PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP", "documentInfo": { "Title": "Incidents in BC", "Author": "", "Comments": "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\u2026 CAUSE_DESCRIPTIONCause DescriptionText1000Renewal Triggers and Service Levels Nightly", "Subject": "Incidents in BC locations as provided through the BCER's Audit and Integrity Engineering group locations of pipeline incidents by year in the province.", "Category": "", "Version": "3.3.0", "AntialiasingMode": "None", "TextAntialiasingMode": "Force", "Keywords": "BCER,Incident,Audit & Integrity,Engineering,EXTERNAL" }, "supportsQueryDomains": true, "capabilities": "Map,Query,Data", "supportedQueryFormats": "JSON, geoJSON, PBF", "exportTilesAllowed": false, "referenceScale": 0.0, "supportsDatumTransformation": true, "archivingInfo": {"supportsHistoricMoment": false}, "supportsClipping": true, "supportsSpatialFilter": true, "supportsTimeRelation": true, "supportsQueryDataElements": true, "mapUnits": {"uwkid": 9001}, "maxRecordCount": 2000, "maxImageHeight": 4096, "maxImageWidth": 4096, "supportedExtensions": "FeatureServer, KmlServer", "serviceItemId": "ddcc81d81dc1457e86b36674b6f07126" }