The load files will be in
preformatted courier textand comments will be in colored italic text. It should be noted that the comments cannot appear in the actual file.
This example will use tables of the Haddock data. There will be four tables that will load a well and its surface location, and the wellbore.
Note: The columns are separated by a tab character, and do not necessarily line up.
The first table: well
well Row 1: The entity name. One column only. from puits.par using puits sondage Row 2:This row for comments 5 Row 3: Number of columns Row 4: This row for comments. *identifier description ref_naming_system ref_existence_kind ref_well_structure_rule row 5 (above) has a column for every attribute ref_naming_system.kind ref_existence_kind.name ref_well_structure_rule.name Row 6 (above). For each attribute: If the column is blank, then store the value. If not blank, it finds a relationship. M O O M O Row 7: O = optional, M = mandatory NDT_NAME NDT_COMMENT NDT_NAME NDT_NAME NDT_NAME A A A A A Row 9: All are alphanumeric (strings) ENDHEADER 100160245675301001 Haddock well CARMEN6 project name actual simplex 100160244580056008 Haddock well HELENE-5A project name actual simplex 100160384184044008 Haddock well IRMA-7Y project name actual simplex 100160425973177002 Haddock well CARMEN1 project name actual simplex 100160315175012000 Haddock well CARMEN4A project name actual simplex 100160315282331004 Haddock well CARMEN9A project name actual simplex 100160295384056008 Haddock well CARMEN10 project name actual simplex 100160413687230002 Haddock well NATACHA-13 project name actual simplex 100160444888076092 Haddock well INGRID-N17 project name actual simplex 100160373974311008 Haddock well NATACHA-3 project name actual simplex
Table 2: well_surface_point. This table has two columns: the first is the well, and gets the instance handle by giving the well.identifier. The second is identifier, and is a string that is the identifier for the well_surface_point instance.
well_surface_point from puits.par using puits sondage 2 *well identifier well.identifier M O NDT_NAME NDT_NAME A A ENDHEADER 100160245675301001 locates 100160245675301001 100160244580056008 locates 100160244580056008 100160384184044008 locates 100160384184044008 100160425973177002 locates 100160425973177002 100160315175012000 locates 100160315175012000 100160315282331004 locates 100160315282331004 100160295384056008 locates 100160295384056008 100160413687230002 locates 100160413687230002 100160444888076092 locates 100160444888076092 100160373974311008 locates 100160373974311008
Table 3: pty_location_2d. This table gives the 2d (easting, northing) projection location of the well surface point. Note that the second column is a location datatype, and takes up 7 rows. See the DAE Specification Appendix for details on this format.
To locate the proper instance of well_surface_point, the select statement has to traverse two entities. Thus, you have the well_surface_point attribute, well, which has attribute, identifier.
pty_location_2d from puits.par using puits sondage 2 well_surface_point data_value well_surface_point.well.identifier Note the 2 entity dot notation. O M NDT_NAME NDT_LOCATION A L ENDHEADER 100160245675301001 # The # indicates multiple rows. Australian TM 146 E 156632.96806749736425 m 8575069.1396889891475 m @ The @ indicates this is the last row. 100160244580056008 # Australian TM 146 E 165745.7024146662734 m 8563095.2799644991755 m @ 100160384184044008 # Australian TM 146 E 183246.04854218594846 m 8516452.8111880123615 m @ 100160425973177002 # Australian TM 146 E 189423.96912318642717 m 8586506.9645642116666 m @ 100160315175012000 # Australian TM 146 E 168500.54972715082113 m 8556686.8056857772171 m @ 100160315282331004 # Australian TM 146 E 169096.41803685543709 m 8560009.9055160284042 m @ 100160295384056008 # Australian TM 146 E 165745.7024146662734 m 8563095.2799644991755 m @ 100160413687230002 # Australian TM 146 E 188575.4674927610904 m 8497371.9359257519245 m @ 100160444888076092 # Australian TM 146 E 193225.21932100597769 m 8544669.7467309553176 m @ 100160373974311008 # Australian TM 146 E 181432.77829407612444 m 8509749.5081651713699 m @
Table 4: wellbore. This table assigns a wellbore to the well. In most cases, this is 1-1 (one well, one wellbore), but there are some exceptions in haddock. None of them are here. Note also the wellbore shape and purpose are given.
wellbore from sondage.par using sondage puits trajectoire-sond 6 well identifier ref_wellbore_trajectory_shape ref_naming_system ref_wellbore_purpose ref_existence_kind well.identifier ref_wellbore_trajectory_shape.name ref_naming_system.kind ref_wellbore_purpose.kind ref_existence_kind.name M M O O O M NDT_NAME NDT_NAME NDT_NAME NDT_NAME NDT_NAME NDT_NAME A A A A A A ENDHEADER 100160245675301001 100160245675301001 vertical project name wildcat actual 100160244580056008 100160244580056008 vertical project name wildcat actual 100160384184044008 100160384184044008 deviated project name wildcat actual 100160425973177002 100160425973177002 vertical project name wildcat actual 100160315175012000 100160315175012000 vertical project name wildcat actual 100160315282331004 100160315282331004 deviated project name wildcat actual 100160295384056008 100160295384056008 vertical project name wildcat actual 100160413687230002 100160413687230002 vertical project name wildcat actual 100160444888076092 100160444888076092 deviated project name development actual 100160373974311008 100160373974311008 vertical project name wildcat actual
[Return to text file]
[Return to Getting Started Introduction]