Recommended File Naming Standards for EnCana SEGY
So why do we want a long line name?
The geophysicist would like to be able to identify certain types of information just by looking at the file name. Information such as:
- Unique reference number -- where can I get another copy of the data?
- Line name -- how do my partners identify the seismic line?
- Stack type -- am I looking at a migration or at a stack?
- Date -- when were these data processed, is this a recent version of the line?
- Processor -- who did the processing, is this version the best that I have?
What does our existing AEC legacy CORPORATE DATA look like?
Here are some of the CD's that have been copied to spinning disk. This group of lines have both a CD and a SAM number. The additional fields in the name contain useful information but much of it is unclear. It is possible to extract additional descriptions from the SAM data base.CD-21055.a37403.91-1479.un.sfk.sgy CD-21260.a34279.AC-6.gox92.um.sgy CD-21717.a35195.MAR-ZSR-6.echo97.fs.sgy CD-21820.a19020.81-A4R16.ksp01.fscmigwhtfxdcn.sgy CD-30481.a57658.FBAG00016.stack.gox2002._fstk.sgy CD-31728.a16589.OMR-88-03.un.um.sgySome CD's we can't identify (without a research effort with SAM). This group of data (approx 25%) appears not to contain a SAM number. At least we can look a SAM and see what is suppose to be on the physical CD.CD-11506.52.egs97.um.sgy CD-11506.322.egs97.us.sgy CD-12455.slimlk-99-01.vgdc1999.sl1fxfm.sgy CD-12479.aec_west.cabincreek.ps-migs.unfiltered.kak-7.sgyAfter the data is converted into SeisX, shot points are corrected and XY's are inserted. This is the "good" data I'd want to use, only if I could identify what it is! Here we have SeisX data under fs06. What are these data? We have lost our link of CD name to SAM. Are these SAM numbers? Are there any line names here?42504_es_nov00.FXFMG.0.sgy 5700.MIGUL.0.sgy 5701.MIGUL.0.sgy 76762_DUB-02-04.FMD.0.sgy ApodmomigA.MIG.0.sgy Apostr1.MIG.0.sgy psmig_s.PSMIG.0.sgy psmigfxy_n.PSMIGF.0.sgy psmigfxy_s.PSMIGF.0.sgy SUFF-02-01B.FMG.0.sgy SUFF-02-01B.FMZ.0.sgy suff1714.MIGPSD.0.sgyHere is a script to pull out some key information re these line. Little b means Big Endian (Unix) and the little l means Little Endian (PC).~ekeyser/perl/spids.pl External_File_Name Trace Spid/li Cdp/tr Xcoord Ycoord Trace Spid/li Cdp/tr Xcoord Ycoord Cdp's Num_Spid Ratio b 42504_es_nov00.FXFMG.0.sgy 1 101 1 490275 5529968 313 257 313 485047 5529978 313 156 2.01 b 5700.MIGUL.0.sgy 1 1 1 530908 5587560 341 171 341 530902 5581862 341 170 2.01 b 5701.MIGUL.0.sgy 1 1 1 532513 5587937 275 138 275 532578 5583358 275 137 2.01 b 76762_DUB-02-04.FMD.0.sgy 1 105 210 515876 5565858 2013 1111 2222 505819 5565614 2013 1006 2.00 l ApodmomigA.MIG.0.sgy 3D 1 1 520344 5617436 135 467 506372 5613419 l Apostr1.MIG.0.sgy 3D 1 1 520344 5617436 135 467 506372 5613419 b psmig_s.PSMIG.0.sgy 3D 66 1 496362 5586643 391 317 488462 5578518 b psmigfxy_n.PSMIGF.0.sgy 3D 1 1 496710 5602285 555 412 488490 5585665 b psmigfxy_s.PSMIGF.0.sgy 3D 66 1 496362 5586643 391 317 488462 5578518 b SUFF-02-01B.FMG.0.sgy 1 277 554 512551 5610369 897 725 1450 511375 5614660 897 448 2.00 b SUFF-02-01B.FMZ.0.sgy 1 277 554 512551 5610369 897 725 1450 511375 5614660 897 448 2.00 b suff1714.MIGPSD.0.sgy 3D 305 341 495120 5602263 587 642 489098 5593804Here is another script to pull some more information out of the headers. Notice how the internal name provides some more clues to the data:~ekeyser/Perl/phase.pl External_File_Name Internal Format Samples SI Max_amp RMS_amp End_Y End_X Phase 42504_es_nov00.FXFMG.0.sgy 42504_es_nov00 1 1500 2 17720.1 2778.6 313 0 0.0 5700.MIGUL.0.sgy 5700 1 1001 2 6.2 1.3 0 0 0.0 5701.MIGUL.0.sgy 5701 1 1001 2 5.8 1.3 0 0 0.0 76762_DUB-02-04.FMD.0.sgy 76762 1 2000 1 21596.2 3001.2 2013 0 0.0 psmig_s.PSMIG.0.sgy s_3d_merge 1 801 2 5.64e+04 1e+03 317 391 0.0 psmigfxy_n.PSMIGF.0.sgy n_3d_merge 1 799 2 7660.6 999.1 412 555 0.0 psmigfxy_s.PSMIGF.0.sgy s_3d_merge 1 801 2 6.39e+04 999 317 391 0.0 SUFF-02-01B.FMG.0.sgy SUFF-02-01B 1 2000 1 18466.1 3074.2 897 0 0.0 SUFF-02-01B.FMZ.0.sgy SUFF-02-01B 1 2000 1 7.62e+04 1.16e+04 897 0 0.0 suff1714.MIGPSD.0.sgy suff1714 1 750 2 5.35e+04 6.99e+03 0 0 0.0I can look at the ebcdic header for more clues but it is very time consuming. A better solution is to adopt some Long Line Name definition for Data Management purposes. The following is recommended:Proposed File Naming Conventions
The following naming convention be used:Naming Examples:
- 2D : reference number.line name.stack type & version.month & year of generation.processing company name.sgy
- Use either version for 3D :
- reference number.line name.3D-area_name.stack type & version.month & year of generation.processing company name.sgy
- reference number.3D-area_name.3D.stack type & version.month & year of generation.processing company name.sgy
F73379.ECA-VER-993D-02P.Type.042000.abc.sgy A44267.MKD-5.f-fk-mig-100.022003.gox.sgy P172939.02-SBL-2.f-fk-mig-94.022003.gox.sgy A43572.01-KUG-13.f-fk-mig.022003.gox.sgy A44263.MKD-2N.f-fk-str.022003.gox.sgy P173286.3D-JENSEN.3D.test-istk.022003.gox.sgy P81848.PCP-MERG-003DM-08.3D-JENSEN.f-ma-mig-2of5.042000.gox.sgyThe external line names must adhere to unix naming conventions. Spaces, dots, brackets, special characters, & are not to be used!Dashes and Underscores are the only valid field delimiters. If the data are brute stack, the descriptor temp should be included in the stack type field. These data will automatically be removed from out system after a period of time.
Here is the current list of valid stack types and the list of current valid processor names. Note that only the first sub field of the stack type has to be valid. Please contact the author if these lists are not sufficient.
In order to identify data on our ftp data server and to verify that we have all data, an ascii text file is required to the following format:
To: eric@arnica.ws From: morgand@geo-x.com Size File 1424000 P12345.MODEL1-876.mig.032003.gox.sgy 14415 P12345.MODEL1-876.mig.032003.gox.sgy.txt 1424000 P12345.MODEL1-876.ro.032003.gox.sgy 14755 P12345.MODEL1-876.ro.032003.gox.sgy.txtThe common name is be added to a 3D data set as the third field for those contractors use to the former PCP specifications. If the 3D does not have a line name (former AEC) , the 3D-area_name becomes the second field and just the flag 3D in the third field. Here is a 3D Example from the former AEC naming:
P173286.3D-JENSEN.3D.test-istk.022003.gox.sgyIf a 3D has to be broken into separate parts it should be named as follows:P81848.PCP-MERG-003DM-08.3D-JENSEN.f-ma-mig-1of5.042000.gox.sgy P81848.PCP-MERG-003DM-08.3D-JENSEN.f-ma-mig-2of5.042000.gox.sgy P81848.PCP-MERG-003DM-08.3D-JENSEN.f-ma-mig-2of5.042000.gox.sgy P81848.PCP-MERG-003DM-08.3D-JENSEN.f-ma-mig-2of5.042000.gox.sgy P81848.PCP-MERG-003DM-08.3D-JENSEN.f-ma-mig-2of5.042000.gox.sgyNote the 3D prefix, this will permit the 3D's to sort together. Note that the new EnCana standard will work for data from both the way AEC and PCP use to describe data.Changes to the reference numbers will be required for EnCana. We have decided to use a series of prefix characters to preserve data integrity. The new prefix codes are:
Prefix Reference Number A XAEC (North America including Alaska) P XPCE (International) F EnCana (International) I- XAEC (International) N EnCana (North America) Blank Don't know or unknown
How do we work with Long Line names in SeisX?
Here are a new lines that meet the new, proposed standard:A43572.01-KUG-13.f-prfk-prmig.022003.gox.MIG.0.sgy A4764.ESSO-CA-84946-84.f-pr-mig.072003.gox.MIG.0.sgy F101680.ECC-NWT-2003-13.f-pr-fk-fx-mig.042003.gox.MIG.0.sgy F102409.IMP-CA-83655B-81.stk.012003.lyx.STK.0.sgy P172939.02-SBL-2.f-prfk-prmig.022003.gox.MIG.0.sgyRecommended to change the Internal Line name (used for pick files and labelling the base map to the last two subfields of the second dot deliminated field.ls *sgy > junk bash-2.03$ ~ekeyser/perl/phase.pl External_File_Name Internal Format Samples SI Max_amp RMS_amp End_Y End_X Phase A43572.01-KUG-13.f-prfk-prmig.022003.gox.MIG.0.sgy 01KUG13 3 2000 4 19205.6 3110.6 2135 0 0.0 A4764.ESSO-CA-84946-84.f-pr-mig.072003.gox.MIG.0.sgy 84946-84 3 1750 4 21518.3 3113.6 313 0 0.0 F101680.ECC-NWT-2003-13.f-pr-fk-fx-mig.042003.gox.MIG.0.sgy 2003-13 3 2000 4 23851.4 3115.9 1659 0 0.0 F102409.IMP-CA-83655B-81.stk.012003.lyx.STK.0.sgy F102409 1 3051 2 40.5 8.0 1477 0 0.0 P172939.02-SBL-2.f-prfk-prmig.022003.gox.MIG.0.sgy 02SBL2 3 2000 4 20251.2 3122.7 1112 0 0.0Here is how to change the internal line name to the first dot deliminated fieldbash-2.03$ ~ekeyser/perl/fixname.pl -f1 A43572.01-KUG-13.f-prfk-prmig.022003.gox.MIG.0.sgy 01KUG13 to A43572 A4764.ESSO-CA-84946-84.f-pr-mig.072003.gox.MIG.0.sgy 84946-84 to A4764 F101680.ECC-NWT-2003-13.f-pr-fk-fx-mig.042003.gox.MIG.0.sgy 2003-13 to F101680 F102409.IMP-CA-83655B-81.stk.012003.lyx.STK.0.sgy F102409 to F102409 P172939.02-SBL-2.f-prfk-prmig.022003.gox.MIG.0.sgy 02SBL2 to P172939Here is how to change the internal line name to the last two sub fields of the second field. This is the name that appears on the map and the name for the pick files.bash-2.03$ ~ekeyser/perl/fixname.pl -f22 A43572.01-KUG-13.f-prfk-prmig.022003.gox.MIG.0.sgy A43572 to KUG-13 A4764.ESSO-CA-84946-84.f-pr-mig.072003.gox.MIG.0.sgy A4764 to 84946-84 F101680.ECC-NWT-2003-13.f-pr-fk-fx-mig.042003.gox.MIG.0.sgy F101680 to 2003-13 F102409.IMP-CA-83655B-81.stk.012003.lyx.STK.0.sgy F102409 to 83655B-81 P172939.02-SBL-2.f-prfk-prmig.022003.gox.MIG.0.sgy P172939 to SBL-2Here's how to get a list of the internal line namebash-2.03$ ~ekeyser/perl/phase.pl External_File_Name Internal Format Samples SI Max_amp RMS_amp End_Y End_X Phase A43572.01-KUG-13.f-prfk-prmig.022003.gox.MIG.0.sgy KUG-13 3 2000 4 19205.6 3110.6 2135 0 0.0 A4764.ESSO-CA-84946-84.f-pr-mig.072003.gox.MIG.0.sgy 84946-84 3 1750 4 21518.3 3113.6 313 0 0.0 F101680.ECC-NWT-2003-13.f-pr-fk-fx-mig.042003.gox.MIG.0.sgy 2003-13 3 2000 4 23851.4 3115.9 1659 0 0.0 F102409.IMP-CA-83655B-81.stk.012003.lyx.STK.0.sgy 83655B-81 1 3051 2 40.5 8.0 1477 0 0.0 P172939.02-SBL-2.f-prfk-prmig.022003.gox.MIG.0.sgy SBL-2 3 2000 4 20251.2 3122.7 1112 0 0.0Yup, that's what I want.Use the Unix link command to create a short name
I have heard that many people do not like the long line name because this long name get's truncated in the SeisX listing as seen below. My answer is to use the spids.pl and phase.pl listing to see the same information. It's actually a better listing because it contains more information and contains data for all versions of a seismic line. Click on the image to see the readable version.
Long Name
Choice number 2 is to use a link to make a link with the shortened line name. Here is an awk script to make the link. Notice that the advantage is SeisX get's to use a short name but the user can still identify where the data came from.ls *sgy > junk find /auto/fs63/ekeyser/seisx/segy/2d -name "*.0.sgy" > junk bash-2.03$ more junk /auto/fs63/ekeyser/seisx/segy/2d/F102409.IMP-CA-83655B-81.stk.012003.lyx.STK.0.sgy /auto/fs63/ekeyser/seisx/segy/2d/F101680.ECC-NWT-2003-13.f-pr-fk-fx-mig.042003.gox.MIG.0.sgy /auto/fs63/ekeyser/seisx/segy/2d/A43572.01-KUG-13.f-prfk-prmig.022003.gox.MIG.0.sgy /auto/fs63/ekeyser/seisx/segy/2d/A4764.ESSO-CA-84946-84.f-pr-mig.072003.gox.MIG.0.sgy /auto/fs63/ekeyser/seisx/segy/2d/P172939.02-SBL-2.f-prfk-prmig.022003.gox.MIG.0.sgy awk -f ~ekeyser/Ak/2last3link.ak < junk bash-2.03$ awk -f ~ekeyser/Ak/2last3link.ak < junk ln -s /auto/fs63/ekeyser/seisx/segy/2d/F102409.IMP-CA-83655B-81.stk.012003.lyx.STK.0.sgy IMP-CA-83655B-81.STK.0.sgy ln -s /auto/fs63/ekeyser/seisx/segy/2d/F101680.ECC-NWT-2003-13.f-pr-fk-fx-mig.042003.gox.MIG.0.sgy ECC-NWT-2003-13.MIG.0.sgy ln -s /auto/fs63/ekeyser/seisx/segy/2d/A43572.01-KUG-13.f-prfk-prmig.022003.gox.MIG.0.sgy 01-KUG-13.MIG.0.sgy ln -s /auto/fs63/ekeyser/seisx/segy/2d/A4764.ESSO-CA-84946-84.f-pr-mig.072003.gox.MIG.0.sgy ESSO-CA-84946-84.MIG.0.sgy ln -s /auto/fs63/ekeyser/seisx/segy/2d/P172939.02-SBL-2.f-prfk-prmig.022003.gox.MIG.0.sgy 02-SBL-2.MIG.0.sgy cd links awk -f ~ekeyser/Ak/2last3link.ak < ../junk > run chmod +x run ./runHere's what the files look like:bash-2.03$ ls 01-KUG-13.MIG.0.sgy 02-SBL-2.MIG.0.sgy ECC-NWT-2003-13.MIG.0.sgy ESSO-CA-84946-84.MIG.0.sgy IMP-CA-83655B-81.STK.0.sgyHere are all the files with the link:ls -al total 64 lrwxrwxrwx 1 ekeyser expl 83 Oct 23 12:49 01-KUG-13.MIG.0.sgy -> /auto/fs63/ekeyser/seisx/segy/2d/A43572.01-KUG-13.f-prfk-prmig.022003.gox.MIG.0.sgy lrwxrwxrwx 1 ekeyser expl 83 Oct 23 12:49 02-SBL-2.MIG.0.sgy -> /auto/fs63/ekeyser/seisx/segy/2d/P172939.02-SBL-2.f-prfk-prmig.022003.gox.MIG.0.sgy lrwxrwxrwx 1 ekeyser expl 92 Oct 23 12:49 ECC-NWT-2003-13.MIG.0.sgy -> /auto/fs63/ekeyser/seisx/segy/2d/F101680.ECC-NWT-2003-13.f-pr-fk-fx-mig.04200 3.gox.MIG.0.sgy lrwxrwxrwx 1 ekeyser expl 85 Oct 23 12:49 ESSO-CA-84946-84.MIG.0.sgy -> /auto/fs63/ekeyser/seisx/segy/2d/A4764.ESSO-CA-84946-84.f-pr-mig.072003.gox. MIG.0.sgy lrwxrwxrwx 1 ekeyser expl 82 Oct 23 12:49 IMP-CA-83655B-81.STK.0.sgy -> /auto/fs63/ekeyser/seisx/segy/2d/F102409.IMP-CA-83655B-81.stk.012003.lyx.STK .0.sgyHere is what the SeisX listing looks like:
Links Name
Now we have the link short name in our display.Copy files to your short line name
Last choice is to copy the files to the new short name. This is a one way street, you can make it smaller, but you cannot go back.ls *sgy > junk awk -f ~ekeyser/Ak/2last3.ak < junk cp A43572.01-KUG-13.f-prfk-prmig.022003.gox.MIG.0.sgy 01-KUG-13.MIG.0.sgy cp A4764.ESSO-CA-84946-84.f-pr-mig.072003.gox.MIG.0.sgy ESSO-CA-84946-84.MIG.0.sgy cp F101680.ECC-NWT-2003-13.f-pr-fk-fx-mig.042003.gox.MIG.0.sgy ECC-NWT-2003-13.MIG.0.sgy cp F102409.IMP-CA-83655B-81.stk.012003.lyx.STK.0.sgy IMP-CA-83655B-81.STK.0.sgy cp P172939.02-SBL-2.f-prfk-prmig.022003.gox.MIG.0.sgy 02-SBL-2.MIG.0.sgy awk -f ~ekeyser/Ak/2last3.ak < junk > run chmod +x run runNaming Recommendation
It is recommended that the Long Line Name be adopted in order to simplify the identification of data for Data Management purposes. The fully described data will be part of the Corporate Archive.Note: Then end user is free to use what ever line name they desire!
As a Post Script, both SeisX and SeisWare support the idea of having a long, dot delimited line name. They both will add options to support the additional information that can do some of the following:
Here are some useful links for more information for those in the Intranet at EnCana:
- Sort display on year, processor, flow, owner
- Grid sets defined by these additional fields
- Grid Balance your data grouped by processor
- The why for EnCana segy, examples of using some additional header information
- Advantages of EnCana segy, attaching multiple versions, 3D examples
- Workstation SEGY Standards (2D, 3D and field data exchange) The definition
Site Owner: Eric Keyser
Last Updated: October, 26 2003