Project ID
For seismic datasets the ProjectID can contain a NDR9 code as an attribute for new projects, for existing projects which already have a NDR9 code, it can be selected as part of the ProjectID creation process.
The identification code of a project will be defined by an alphanumeric character code where the format of the characters is defined as: CCCCYYYYtypeNNNN and detailed below:
Project ID: CCCCYYYYtypeNNNN definition |
|
CCCC |
4 character alphanumeric code for company - See company code list, for 2 character companies append trailing underscores to make it 4 characters, e.g BP__ or WOS_ or WSOC
|
YYYY |
4 character numeric year in which project was performed (if between years, choose earliest), this is not the acquisition year of the input datasets |
Type |
4 lower case character code defining the type of project– e.g. well, seis |
NNNN |
4 character numeric project designator, right justified, padded with zeros |
The “type” four lower case character code defines the type of project as follows:
Code |
Types of project per code |
well |
Wellbore projects - All pre and post drill data, including drilling reports, digital well log, joined well logs, log images, vsp data, checkshot, reports etc. |
seis |
Seismic projects - Acquisition, processing or reprocessing projects. This includes all types of acquisition (e.g. 2d,3d,4d) and all data types, supporting information and reports etc. |
mhaz |
Near surface high resolution site survey projects - shallow investigation seismic, shallow boreholes, acoustic, sonar, bathymetry surveys, shallow hazard reports. All data types, supporting information and reports etc. |
rems |
Remote sensing, potential and diffusive field projects - CSEM surveys, stand alone gravity and/or magnetic surveys, Lidar, satellite observations. All data types, supporting information and reports etc. |
intp |
Remote sensing, potential and diffusive field projects - CSEM surveys, stand alone gravity and/or magnetic surveys, Lidar, satellite observations. All data types, supporting information and reports etc. |
The NNNN four character number will be a sequence number as each project from the same company in the same year for the same project type is loaded.
0001 |
first project from company EG in year 2007 |
0002 |
second project from company EG in year 2007 |
Example of ProjectID names
Acquisiton ProjectID examples |
|
EG__2016seis0001 |
first seismic 2D survey, company EG in year 2016 |
EG__2016seis0002 |
second seismic 3D survey, company EG in year 2016 |
EG__2019seis0001 |
first seismic 3D survey, company EG in year 2019 |
EG__2019mhaz0002 |
second Site investigation survey, company EG in year 2019 |
EG__2019mhaz0003 |
second Site investigation survey, company EG in year 2019 |
BZC_2017rems0001 |
first 3D CSEM survey, company BZC in year 2017 |
BQ__2018well0001 |
first wellbore logging project, company BQ in year 2018 |
BQ__2018well0001 |
first stand alone borehole seismic, company BQ in year 2018 |
Projects are independently named and do not refer to other projects as part of the ProjectID. The creation of the ProjectID can include metadata to show what the related datasets that form part of this project, this may include other ProjectID’s.
Processing and reprocessing ProjectID examples |
||
Example project |
ProjectID |
Comment |
2020 CCS potential study |
GWG_2020intp0001 |
ProjectID metadata can mention multiple input datasets |
2009 Acquisition survey |
GWG_2009seis0002 |
none |
2009 Processing project |
GWG_2009seis0003 |
ProjectID metadata can mention GWG_2009seis002 as input dataset
|
2012 Acquisition survey |
AVC_2012seis0001 |
none |
2012 Processing project |
AVC_2012seis0002 |
ProjectID metadata can mention AVC_2012seis001 as input dataset |
2014 Reprocessing project |
GWG_2014seis0002 |
ProjectID metadata can mention GWG_2009seis002 as input dataset
|
2016 merge processing project |
BR__2016seis0003 |
ProjectID metadata can mention GWG_2009seis002 and AVC_2012seis001 as input datasets
|
Comments
0 comments
Article is closed for comments.