P Formats – A Review, Changes and Implementation

Encana Corporation, THE BOW, 500 Centre Street SE, Calgary, AB, T2G 1A6 Canada

Current Revision Status

• The revisions have been ratified by OGP and have now been published on the OGP Website

• During 2013 we hope to see an increased rollout of the formats in the field.

Introduction to Existing Formats and Reasons for Change.

History

• Since the early 1990, the marine seismic industry has recorded field positioning data in two formats• P1/90 for Post-plot (processed position) data

exchange.• P2/94 for raw positioning data.

• A third format, P6/98 for defining Bin Grids was also developed but hasn’t seen wide acceptance

Ownership

• These formats were originally developed by UKOOA but ownership was transferred to the International Association of Oil & Gas Producers (OGP) Geomatics Committee in 2006.

These formats were originally developed by

P1/90: Post Plot Data Exchange

• Defined in 1990 to replace the existing P1/84 format.

• Originally intended for use in Offshore and Onshore surveys, but has only really been used Offshore.

• The standard for Marine Post Plot exchange between Positioning and Seismic systems

• Also used for Pre Plot and Bin Centre position exchange.

P1/90: Data Content

• A simple header containing survey information, geodetic configuration and a very basic survey spread layout.

• Single Position Records• One Record per Position Type, e.g. Source, Vessel,

Tailbuoy etc.• Grid and Geographical Coordinates of the Point.

• Multiple Position Records (Receiver Groups)• Each Record contains the position of three receiver

groups.• Grid Coordinates only.

P1/90: Post Plot

P1/90: Data Format

• Data is encoded in an 80-character fixed width ASCII or EBCDIC format, with an optional “CR” and or “LF” character at the end of each record.

H0100SURVEY AREA UKCS Block 93 H0101GENERAL SURVEY DETAILS 3D, SINGLE VESSEL, SIX STREAMERS, DUAL SOURCE

H1400GEODETIC DATUM AS SURVEY ED50 INTERNAT1924 6378388.000 297.0000000H1401ED50 Sector TO WGS84 -89.5 -93.8-123.1 0.000 0.000-0.156 1.2000000 H1500GEODETIC DATUM FOR POST. ED50 INTERNAT1924 6378388.000 297.0000000H1501ED50 Sector TO WGS84 -89.5 -93.8-123.1 0.000 0.000-0.156 1.2000000 H1600DATUM TRANSFORMATION 00.0 00.0 000.0 0.000 0.000 0.000 0.0000000

V358I1-016 1 2089583338.11N 03738.16E 361959.46493712.6 147.0215 15918 S358I1-016 12 2089583335.40N 03754.89E 362226.76493619.2 147.0215 15918

R 1 362438.96493852.4 6.7 2 362451.06493849.4 6.5 3 362463.26493846.4 6.51R 4 362475.36493843.4 6.5 5 362487.56493840.4 6.5 6 362499.76493837.4 6.51R 7 362511.86493834.4 6.5 8 362524.06493831.4 6.5 9 362536.26493828.5 6.51

P2/94: Raw Positioning Data

• P2/94 was implemented as a minor update to P2/91 which replaced P2/86, the first common standard for storing raw positioning data.

• The standard for storing Marine positioning data.

• Allows for post processing, exchange and quality control, and also provides a backup if the Post Plot data is lost.

P2/94: Data Content

• A comprehensive header containing survey information, geodetic configuration and survey spread layout.

• Event Data Records• Record the Data Acquisition Event (Shot) and any

data related to the event time

• Time Data Records• Record data from the positioning sensors (GNSS,

Gyro, Echo Sounder, Acoustic, Compass, Depth etc)

• Raw GNSS Data• Limited Recording of raw GNSS data observed by the

GNSS systems on board the vessel.

P2/94: Raw Positioning Data

Reasons for Updating

• A revision has been proposed for some time, as the existing formats are being made obsolete by changes in acquisition and processing technologies, resulting in an increasing number of non-standard variations and “add-ons” being used.

Reasons for Updating

• In P1/90, a single digit was used for the streamer number, as 1-9 was considered sufficient in 1990.

• As 10 streamer spreads occurred, this record varied to include A-Z for streamers above 10.

H0104STREAMER DETAILS Streamer_008 1 8 8H0104STREAMER DETAILS Streamer_009 1 9 9H0104STREAMER DETAILS Streamer_010 1 A A

R4423 339694.3 577969.849.14424 339688.7 577958.649.14425 339683.1 577947.549.19R4426 339677.5 577936.349.14427 339671.9 577925.249.14428 339666.3 577914.049.19R4429 341972.2 583619.1 6.44430 341967.7 583607.4 6.54431 341963.3 583595.7 6.6AR4432 341958.9 583584.0 6.64433 341954.5 583572.2 6.74434 341950.1 583560.5 6.8A

Reasons for Updating

• In P2/94, support was added for a number of data types common in the early 1990s. As techniques have changed, more and more data values are being recorded in the “user defined” data area, resulting in non-standard files from different sources.

H7000 1 2 ANNEMOMETER H7000 2 3 ACOUSTIC DOPPLER CURRENT METER H7000 3 2 Ships Doppler Log H7010 1 1 12 WIND DIRECTION RELATIVE TO SHIPS HEADING H7010 1 2 12 WIND SPEED IN KNOTS H7010 2 1 12 TEMPERATURE H7010 2 2 12 VESSEL WATER SPEED H7010 2 3 12 VESSEL WATER SPEED VECTOR H7010 3 1 12 Speed (m/s) over water H7010 3 2 12 Speed (knots) over water

Reasons for Updating

• In P2/94, support was added for recording raw GNSS data, supporting GNSS systems as they existed in the early 1990s. As available systems have changed, data values are being forced into existing records.

• Lack of clarity on the GNSS data that should be logged has caused confusion.

Reasons for Updating

• P6/98 has not seen widespread acceptance, and commonly P1/90 is used to exchange bin centre position.

• With the growing use of GIS systems and the automation of data exchange between workstations, the requirement for a bin grid and survey coverage exchange format is seen as increasingly important.

Reasons for Updating

• Also it is seen that an update can bring the formats into line with recent changes in handling common data – such as the increased use of the EPSG Dataset, and of GeoDatabases.

• Updating the formats as a group also allows for more commonality between the formats.

Reasons for Updating• Currently P1/90, P2/94 and P6/98 all have

different headers, even when defining common data.

P1/90H1800PROJECTION TYPE 1 UNIVERSAL TRANSVERSE MERCATOR (NORTH) H1900PROJECTION ZONE 28 NORTHERN HEMISPHERE H2000GRID UNIT 1METRES 1.000000000000 H2200LONG OF CENTR. MERID 0150000.000W H2301GRID ORIGIN 0000000.000N0150000.000W H2302GRID COORD. AT ORIGIN 500000.00E 0.00N H2401SCALE FACTOR 0.9996000000 H2402LAT/LON WHERE SCALE DEF 0000000.000N0150000.000W

P2/94H0140 001 1.00000000 U.T.M. H0150 28 0000000.000N 0150000.000W 0.00N 500000.00E 0.9996000000

P6/98H0500 Projection Method 001 UNIVERSAL TRANSVERSE MERCATORH0510 Projection Zone Name ZONE 28 NORTHERN HEMISPHEREH0530 Lon of CM (dms E/W) 15 0 0.000W

SEG P1

• The SEG P1 format is still used, mostly within North America, for Post-plot position exchange.

• Following discussions with the Society of Exploration Geophysicists (SEG), it was agreed that the new P1 format should also be developed to replace SEG P1 and that, following the release of P1, the SEG P1 format would be deprecated.

SPS

• SPS is the most common 3D land position exchange format.

• The SEG Technical Standards Committee are working on an update to SPS.

• It is currently planned that the full revision will align SPS with the new P1 format.

Structure and Features of the New Format

Format Changes• Move to a Variable-Width Format.• Common Header for all formats.• Increased Flexibility.

Format Changes• Move to CSV Format.

• Existing formats are encoded as fixed-width 80-character ASCII or EBCDIC files.

• New formats are variable length ASCII comma separated data records.

• A variable length format removes the restrictions on column widths that require the expected range and precision of a data value to be specified when the format is defined.

Fixed Width FormatData to be Logged

Fixed Format

File Output

Result: Precision is lost

Variable Width FormatData to be Logged

Variable Format

File Output

Result: Precision is preserved

Fixed vs Variable• Fixed Width is too restrictive and requires the format

definition to be overly predictive. It also causes problems with fitting all required data into a single record.• P1/90 defines the streamer number as a single digit.• P1/90 defines shot time to integer seconds (and P2/94 defines it

to 1 decimal place)• P1/90 Grid Position field widths were not defined with enough

space to record Feet.

• Variable Width moves the requirement to determine the correct output precision to the system writing the file.

Record StructureHC,0,1,0,Project Name,34642,Demo,2010:04:03

• The first field is the record type. • For the first record in the file, this is “OGP”• For the other records in the file, this is a two digit record identifier

where the first digit is the record identifier and the second digit identifies the format type.

Record Structure

• Data Types can also be used in Lists, separated by the Ampersand (&)

A good example is the GNSS “satellites used” field from the P2/11 format where the satellite SV numbers are listed as “5&6&7&8”

T2,5,5,0,1151,36.978791944,-16.219869722,4.5,,,,5&6&7&8&9&10&11&12&13&14,,2,2010:246:14:55:29.1,4.09:3.91:4.84:2.24:2.45

Record StructureThus, for Text Fields we have 4 reserved characters• Comma (Field Separator)• Semi-Colon (Extension Separator)• Colon (Used in Time and Date Values)• Ampersand (List Separator)

Record Readability• Although the format will most often be interpreted

by a computer and is primarily designed for that purpose, a couple of features have been added to aid human readability, especially in the general header• The general header has line descriptions• Value padding to ensure columnar layout of similar data is

recommended (header only).HC,1,1,0,Unit of Measure , 1, angle, , 1, 1, radian,9101,EPSG,7.6, 9101HC,1,1,0,Unit of Measure , 2, angle,1, 3.141592654, 180, degree,9102,EPSG,7.6, 9102HC,1,1,0,Unit of Measure , 3, scale, , 1, 1, unity,9201,EPSG,7.6, 9201HC,1,1,0,Unit of Measure , 4, length, , 1, 1, metre,9001,EPSG,7.6, 9001HC,1,1,0,Unit of Measure , 5, time, , 1, 1, second, ,POSC,2.2, sHC,1,1,0,Unit of Measure , 6, time,5, 1,1000,milliseconds, ,POSC,2.2, msHC,1,1,0,Unit of Measure , 7, volume, , 1, 1,cubic metres, ,POSC,2.2, m3HC,1,1,0,Unit of Measure , 8, volume,7,0.00001638706, 1, cubic inch, ,POSC,2.2,cu_inHC,1,1,0,Unit of Measure , 9,pressure, , 1, 1, pascal, ,POSC,2.2, PaHC,1,1,0,Unit of Measure ,10,pressure,9, 6894.757, 1, psi, ,POSC,2.2, psiHC,1,1,1,Example Unit Conversion ,1,1,2,0.40142572,2,2,23.000

Record Readability - ExampleOGP,OGP P1,1,1.0,1,2010:01:21,12:23:33,spsexample.p111,OGPHC,0,1,0,Project Name ,12345,SPSDEMO,2002:01:22HC,0,2,0,Survey Description ,2D Transition Zone,Single Source,Indonesia,360,IDNHC,0,3,0,Approximate Data Location ,-2.37,-2.43,133.39,133.47HC,0,4,0,Client ,Wight Oil LimitedHC,0,5,0,Geophysical Contractor ,OilFinder LLCHC,0,6,0,Positioning Contractor ,TruePos IncHC,0,7,0,Position Processing Contractor ,Navigation Positioning Solutions LtdHC,1,0,0,Reference Systems Summary ,10,1,2,0HC,1,1,0,Unit of Measure , 1, angle, , 1, 1, radian,9101,EPSG,7.6, 9101HC,1,1,0,Unit of Measure , 2, angle,1, 3.141592654, 180, degree,9102,EPSG,7.6, 9102HC,1,1,0,Unit of Measure , 3, scale, , 1, 1, unity,9201,EPSG,7.6, 9201HC,1,1,0,Unit of Measure , 4, length, , 1, 1, metre,9001,EPSG,7.6, 9001HC,1,1,0,Unit of Measure , 5, time, , 1, 1, second, ,POSC,2.2, sHC,1,1,0,Unit of Measure , 6, time,5, 1,1000,milliseconds, ,POSC,2.2, msHC,1,1,0,Unit of Measure , 7, volume, , 1, 1,cubic metres, ,POSC,2.2, m3HC,1,1,0,Unit of Measure , 8, volume,7,0.00001638706, 1, cubic inch, ,POSC,2.2,cu_inHC,1,1,0,Unit of Measure , 9,pressure, , 1, 1, pascal, ,POSC,2.2, PaHC,1,1,0,Unit of Measure ,10,pressure,9, 6894.757, 1, psi, ,POSC,2.2, psiHC,1,1,1,Example Unit Conversion ,1,1,2,0.40142572,2,2,23.000HC,1,2,0,Time Reference System ,1,1,0.0,UTC,0,,5,12HC,1,3,0,CRS Number/EPSG Code/Name/Source ,1,2310,WGS 84 / TM 132 SE,7.6,2010:11:02,EPSG,EPSG_v7_6.mdbHC,1,3,0,CRS Number/EPSG Code/Name/Source ,2,4326, WGS 84,7.6,2010:11:02,EPSG,EPSG_v7_6.mdbHC,1,4,0,CRS Number/Type/Name ,1,2310,1,projected,WGS 84 / TM 132 SEHC,1,4,3,Geodetic Datum ,1,6326,World Geodetic System 1984HC,1,4,4,Prime Meridian ,1,8901,Greenwich,0,2,degree,0.0174533HC,1,4,5,Ellipsoid ,1,7030,WGS 84,6378137,298.257223563,4,metreHC,1,5,0,Projection ,1,16732,TM 132 SEHC,1,5,1,Projection Method ,1,9807,Transverse Mercator,1,5HC,1,5,2,Base Geographical CRS ,1,4326,2HC,1,5,3,Latitude of natural origin ,1,8801, 0,2,degreeHC,1,5,3,Longitude of natural origin ,1,8802, 132,2,degreeHC,1,5,3,Scale factor at natural origin ,1,8805, 0.9996,3, unityHC,1,5,3,False easting ,1,8806, 500000,4, metreHC,1,5,3,False northing ,1,8807,10000000,4, metreHC,1,6,0,Coordinate System ,1,4400,Cartesian 2D CS,Cartesian,2HC,1,6,1,Coordinate System Axis 1 ,1,1,1, Easting, east,E,4,2,metreHC,1,6,1,Coordinate System Axis 2 ,1,2,2,Northing,north,N,4,2,metre

Common Header• The new formats share a common header.

• File Identification Record• Survey Summary• Reference Systems Definitions

o Units of Measureo Time Reference Systemso Coordinate Reference Systems

• General Survey Configuration Information (P1 and P2 only)

• The common header is followed by a format specific header.

File Example – a P1/11 FileOGP,OGP P1,1,1,1,2012:07:13,08:09:31,CSL-T21021P1002.p111,OGP

HC,0,1,0,Project Name ,Test,TEST01,2012:03:19,2012:03:22HC,0,2,0,Survey Description ,Marine 3D Towed Streamer,…HC,0,3,0,Approximate Data Location ,-16.222,-16.177,36.976,37.04HC,0,4,0,Client ,Oil Company LimitedHC,0,5,0,Geophysical Contractor ,Oil Finder IncHC,0,6,0,Positioning Contractor ,General Positioning LimitedHC,0,7,0,Position Processing Contractor ,Position Processing LimitedHC,1,0,0,Reference Systems Summary ,5,1,7,1HC,1,1,0,Unit of Measure ,1, metre,length, 2, , , , , ,…HC,1,1,0,Unit of Measure ,2,radian, angle, 2, , , , , ,…HC,1,1,0,Unit of Measure ,3,degree, angle, 2,2,0,3.141592654,180,0,…HC,1,1,0,Unit of Measure ,4, unity, scale, 2, , , , , ,…HC,1,1,0,Unit of Measure ,5,second, time,12, , , , , ,…HC,1,1,1,Example Unit Conversion ,1,2,1,3,57.295779513HC,1,2,0,Time Reference System ,1,1,0,UTC,0,,5HC,1,3,0,CRS Number/EPSG Code/Name/Source ,1,32628, WGS 84 / UTM zone 28N,…HC,1,3,0,CRS Number/EPSG Code/Name/Source ,2, 4326, WGS 84,…HC,1,3,0,CRS Number/EPSG Code/Name/Source ,3, 5715, msl depth,…HC,1,3,0,CRS Number/EPSG Code/Name/Source ,4, ,WGS 84 / UTM zone 28N + msl depth,……HC,2,3,0,Tailbuoy on S9 ,33, T9,10, Float,,,12,,,,, ,,HC,2,3,0,Tailbuoy on S10 ,34, T10,10, Float,,,13,,,,, ,,

File Example – a P1/11 FileOGP,OGP P1,1,1,1,2012:07:13,08:09:31,CSL-T21021P1002.p111,OGP

HC,0,1,0,Project Name ,Test,TEST01,2012:03:19,……HC,2,3,0,Tailbuoy on S10 ,34, T10,10,Float,,,13,,,,, ,,

H1,0,0,0,File Contents Description ,MEAN CMP,Imported from P190H1,0,1,0,Processing Details ,Converted from P190 FileH1,0,2,0,Receiver Groups Per Shot ,1,4800,,H1,0,2,0,Original File ,2,CSL-T21021P1002.WGS-84.p190,,H1,1,0,0,Position Record Type Definition ,1,1,2,2,1,0,H1,1,0,0,Position Record Type Definition ,2,1,2,2,1,1,1;5;Water Depth;1H1,1,0,1,Position Record Quality Definition ,1,0,No Quality Data Recorded,,,0,H1,1,0,1,Position Record Quality Definition ,2,0,No Quality Data Recorded,,,0,H1,2,0,0,Receiver Record Type Definition ,30,6,2,2,1,0,H1,2,0,1,Receiver Record Quality Definition ,0,No Quality Data Recorded,3,1,0,

File Example – a P1/11 FileOGP,OGP P1,1,1,1,2012:07:13,08:09:31,CSL-T21021P1002.p111,OGP

HC,0,1,0,Project Name ,Test,TEST01,2012:03:19,……HC,2,3,0,Tailbuoy on S10 ,34, T10,10,Float,,,13,,,,, ,,

H1,0,0,0,File Contents Description ,MEAN CMP,Imported from P190…H1,2,0,1,Receiver Record Quality Definition ,0,No Quality Data Recorded,3,1,0,

S1,0,T21021P1002,,1001,,1,2010:246:14:56:23.0,3,G2,1,391297.20,4092985.70,,36.97671040,…P1,0,T21021P1002,,1001,,1,2010:246:14:56:23.0,2,G1,1,391341.10,4092961.70,,36.97649917,…P1,0,T21021P1002,,1001,,1,2010:246:14:56:23.0,3,G2,1,391297.20,4092985.70,,36.97671040,…P1,0,T21021P1002,,1001,,1,2010:246:14:56:23.0,3&4,G2&S1,1,391436.30,4092730.50,,36.97442649,…P1,0,T21021P1002,,1001,,1,2010:246:14:56:23.0,3&5,G2&S2,1,391392.60,4092755.00,,36.97464225,…R1,0,T21021P1002,,1001,,1,2010:246:14:56:23.0,4,S1,480,391575.40,4092475.40,7.50,36.97214346,…R1,0,T21021P1002,,1001,,1,2010:246:14:56:23.0,4,S1,450,391410.10,4092139.40,7.50,36.96909622,… R1,0,T21021P1002,,1001,,1,2010:246:14:56:23.0,4,S1,420,391244.90,4091803.90,7.50,36.96605347,…

Format Changes - Review• Move to Variable-Width Format.• Common Header for all formats.• Increased Flexibility.

Format Adoption

• As the new formats have a robust, common header, software should directly consume this header by reading it.

• This eliminates the typing of metadata by hand.• The header must not be separated from the data.

• Increased Potential for retaining positional integrity on loading into the workstation.

• Less Overhead for Data Manager.• Adoption will be a transitional process as

application vendors and seismic data processors adjust their software and loading scripts over to the new formats.

More Detailed Information

• This is an amended version of the training slides which can be downloaded in their original version from OGP website at http://www.ogp.org.uk/news/events1/2012/p-formats-seminars.

• We want to thank the OGP for aiding in this presentation.

Contact Information

• Dean C. Mikkelsen, Terra ETL Ltd.• dcmikkelsen@gmail.com• (403) 919-1646