Attribute
Describes attributes considered within an XML section Attributes are the field provided within the opening tag, for field "href" in the following example: //...">
Usage: | ATTRIB | SECTION |
SECTION |
Section name. In case of ambiguity, the name may include the name of the enclosing section, for example: "station.epoch". If the section was not defined in list SECTION, it is added. |
|
This repeat list gives the names of XML attributes (fields given within the main tag) of section NAME from which trace headers may be loaded. Multiple references to the same subsection (SUBSECT) can be used to output multiple trace headers (for example, in different formats)
ATTRIB |
Name of XML attribute considered within this section |
|
FIELD |
Number of the field in the record written into HEADER. The fields can be separated by white spaces, tabs, newlines, commas, semicolons, or colons |
|
HEADER |
Trace header loaded from this attribute |
|
FORMAT |
Format of the trace header created. |
|
TRNSFRM |
Name of the transformation of the string for converting into trace header value (case-insensitive):
|
|
Data values
Describes handling of the DATA string within an XML section.
The DATA is the text contained between the opening and closing tags,
for example for tag 'georss:point' from NRCAN: '
Usage: | DATA | SECTION |
SECTION |
Section name. In case of ambiguity, the name may include the name of the enclosing section, for example: "station.epoch". If the section was not defined in list SECTION, it is added. |
|
This repeat list describes output of trace headers from DATA field
FIELD |
Number of the field in the record written into HEADER. The fields can be separated by white spaces, tabs, newlines, commas, semicolons, or colons |
|
HEADER |
Trace header loaded from this field |
|
FORMAT |
Format of the trace header created. |
|
TRNSFRM |
Name of the transformation of the string for converting into trace header value (case-insensitive):
|
|
Generate trace
Specifies which sections generate seismic traces. When such a section is processed, a trace is generated and all enclosing sections put their trace headers into it.
Usage: | GENTRC | DT NSAMP SECTION |
DT |
Sampling interval set in the output trace |
|
NSAMP |
Number of samples in the output trace |
|
SECTION |
Section name. In case of ambiguity, the name may include the name of the enclosing section, foir example: "station.epoch". If the section was not defined in list SECTION, it is added. |
|
Print out contents of selected sections (done when reading traces)
Usage: | WHAT FNAME | |
WHAT |
Key word specifying what to print in sections whose names are given in REPEAT lists:
|
|
FNAME |
Name of output file for printout. "*" will mean current job output |
|
This repeat list lists masks for selecting sections that need to be printed out. Multiple masks are combined using 'or' operation
SECTION |
String selecting what sections to print. Text string matching can be used, and subsections can be concatenated with ".". For example, "*" prints all sections in the XML input, "*.chan*" selects second-level sections with names starting from "chan", etc.) |
|
Section
These lists contain the sections considered within the XML document. For each section NAME, the Repeat list gives the subsections from which outputs will be made. If no SECTION lists are used, all XML sections will be loaded. Within the loaded sections, data selections aer made by lists ATTRIB, DATA, and GENTRC
Usage: | SECTION | SECTION |
SECTION |
Section name. In case of ambiguity, the name may include the name of the enclosing section, for example: "station.epoch". Empty name means the whole XML document. |
|
This repeat list gives the names of XML subsections (tags) of section NAME from which trace headers may be loaded. Multiple references to the same subsection (SUBSECT) can be used to output multiple trace headers (for example, in different formats)
SUBSECT |
Name of subsection considered within this section |
|
Print template
Reads through the XML file and prints out its structure in the format ready for editing, adding trace headers, and using in the call to READXML in the job. When using this option, no other operations are performed by READXML
Usage: | TEMPLAT | FNAME |
FNAME |
File name for the output template |
|