Geophysical Plans (1996-2004)
Final plan spatial data for geophysical applications received between 1996 and 2004. Final plans identify the locations cleared at the conclusion of all operations.
Background
Geophysical programs study the physical characteristics and properties of subsurface formations relating to oil and gas deposits, derived artificially by explosives or other means to map subsurface structure. Final plan spatial data is included for applications received between 1996 and 2004. Final plans identify the locations cleared at the conclusion of all operations.
Data Properties
Attributes / Column Name
Field Alias
Data Type
Data Precision
Comments
OBJECTID
Object ID
SHAPE
Geometry
FILE_NUM
File Number
Text
10
File number assigned to each application for tracking purposes within the Oil and Gas Commission. E.g., 9632012
GEO_NUM
Geophysical Program Number
Text
10
Date the application is received and recorded into the database.
APPL_RECD
Application Received Date
Date
The number provided by the Regulator and assigned to the geophysical program. The name is included on the application permit and all operations and final plan documentation. E.g., 2001-105
PROJ_NAME
Geophysical Program Name
Text
50
Program name provided by the operator. The name is included on the application permit and all operations and final plan documentation. E.g., Cheves Creek 3D
PROG_TYPE
Geophysical Program Type
Text
2
Indicates if the geophysical was a 2D or 3D program.
CLEARING
Clearing Type
Text
5
Indicates if the clearing was newly cut or already existed (NEW or EXIST).
METHOD
Operation Type
Text
5
Operation type indicates if a line is minimal impact, low impact or conventional (MIN, LOW, CONV).
LINE_NAME
Geophysical Line Name
Text
16
Name of an individual line within the geophysical program provided by the operator. E.g., S-224
LINE_TYPE
Geophysical Line Type
Text
6
Indicates whether geophysical lines are source, receiver or a combination of both (SOURCE, REC or COMBO).
CUT_TYPE
Geophysical Cut Type
Text
5
Indicates whether a line already exists or is newly cut and the clearing method used. E.g., NCC (New Cat Cut)
WIDTH
Geophysical Line Width (m)
Double
Width of the seismic line in meters.
CLIENT_NAM
Client Name
Text
40
Organization name of the oil and gas operator.
LAND_TYPE
Land Type
Text
1
Indicates whether the oil and gas application is on Private or Crown land (P or C).
COMP_DATE
Completion Date
Date
The date construction for the entire program has been completed.
CAPT_METHD
Capture Method
Text
40
Data capture method. E.g., scanning
SRC_FILE
Source File
Text
10
Format of the source data file. E.g., ANSII
Renewal Triggers and Service Levels
Never
Downstream Applications
Web Application
Map Service
REST SERVICE
https://geoweb-ags.bc-er.ca/arcgis/rest/services/REFERENCE/GEO_FINAL_PLAN_1996_2004_LN/MapServer/0
BC DATA CATALOGUE
https://catalogue.data.gov.bc.ca/dataset/ogc-geophysical-final-plans-1996-2004)
Contact Information:
For further information please contact
BC Energy Regulator [email protected]
Attention Geospatial Services Manager
Datasets available for download
-
Geophysical Final Plans (1996-2004)Feature Layer
Layer 0 via ArcGIS REST API
Additional Info
| Field | Value |
|---|---|
| Last Updated | March 24, 2026, 21:09 (UTC) |
| Created | March 24, 2026, 21:09 (UTC) |
|
Domain / Topic
Domain or topic of the dataset being cataloged.
|
|
|
Title
Title for the Dataset.
|
Geophysical Plans (1996-2004) |
|
Description
A description of the dataset.
|
Final plan spatial data for geophysical applications received between 1996 and 2004. Final plans identify the locations cleared at the conclusion of all operations. Background Geophysical programs study the physical characteristics and properties of subsurface formations relating to oil and gas deposits, derived artificially by explosives or other means to map subsurface structure. Final plan spatial data is included for applications received between 1996 and 2004. Final plans identify the locations cleared at the conclusion of all operations. Data Properties Attributes / Column Name Field Alias Data Type Data Precision Comments OBJECTID Object ID SHAPE Geometry FILE_NUM File Number Text 10 File number assigned to each application for tracking purposes within the Oil and Gas Commission. E.g., 9632012 GEO_NUM Geophysical Program Number Text 10 Date the application is received and recorded into the database. APPL_RECD Application Received Date Date The number provided by the Regulator and assigned to the geophysical program. The name is included on the application permit and all operations and final plan documentation. E.g., 2001-105 PROJ_NAME Geophysical Program Name Text 50 Program name provided by the operator. The name is included on the application permit and all operations and final plan documentation. E.g., Cheves Creek 3D PROG_TYPE Geophysical Program Type Text 2 Indicates if the geophysical was a 2D or 3D program. CLEARING Clearing Type Text 5 Indicates if the clearing was newly cut or already existed (NEW or EXIST). METHOD Operation Type Text 5 Operation type indicates if a line is minimal impact, low impact or conventional (MIN, LOW, CONV). LINE_NAME Geophysical Line Name Text 16 Name of an individual line within the geophysical program provided by the operator. E.g., S-224 LINE_TYPE Geophysical Line Type Text 6 Indicates whether geophysical lines are source, receiver or a combination of both (SOURCE, REC or COMBO). CUT_TYPE Geophysical Cut Type Text 5 Indicates whether a line already exists or is newly cut and the clearing method used. E.g., NCC (New Cat Cut) WIDTH Geophysical Line Width (m) Double Width of the seismic line in meters. CLIENT_NAM Client Name Text 40 Organization name of the oil and gas operator. LAND_TYPE Land Type Text 1 Indicates whether the oil and gas application is on Private or Crown land (P or C). COMP_DATE Completion Date Date The date construction for the entire program has been completed. CAPT_METHD Capture Method Text 40 Data capture method. E.g., scanning SRC_FILE Source File Text 10 Format of the source data file. E.g., ANSII Renewal Triggers and Service Levels
Downstream Applications Web Application Map Service REST SERVICE https://geoweb-ags.bc-er.ca/arcgis/rest/services/REFERENCE/GEO_FINAL_PLAN_1996_2004_LN/MapServer/0 BC DATA CATALOGUE https://catalogue.data.gov.bc.ca/dataset/ogc-geophysical-final-plans-1996-2004) Contact Information: For further information please contact BC Energy Regulator [email protected] Attention Geospatial Services Manager |
|
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.
|
2016-02-26 |
|
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/81d619920b6848e9a3f0f0201d126cae |
|
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.
|
2024-02-03 |
| Field | Value |
|---|---|
|
Identifier
Unique identifier for the dataset.
|
81d619920b6848e9a3f0f0201d126cae |
|
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/81d619920b6848e9a3f0f0201d126cae |
|
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.
|
229486 |
|
Number of data columns
If tabular dataset, total number of unique columns.
|
36 |
|
Number of data cells
If tabular dataset, total number of cells with data.
|
8261496 |
|
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