Next: B.1.2 Binary tables Up: B.1 Table data Previous: B.1 Table data Contents Index

##
B.1.1 ASCII tables

The first data record may be preceded by 1 or more header records. When using such files, make sure to use the -H option and set the parameter N_HEADER_RECS in the .gmtdefaults file (System default is 1 header record if -H is set; you may also use -H nrecs directly). Fields within a record must be separated by spaces, tabs, or commas. Each field can be an integer or floating-point number or a geographic coordinate string using the [+-]dd[:mm[:ss]][WSNEwsne] format. Thus, 12:30:44.5W, 17.5S, 1:00:05, and 200:45E are all valid input strings. When dealing with time- or (x,y)-series it is usually convenient to have each profile in separate files. However, this may sometimes prove impractical due to large numbers of profiles. An example is files of digitized lineations where the number of individual features may range into the thousands. One file per feature would in this case be unreasonable and furthermore clog up the directory. GMT provides a mechanism for keeping more than one profile in a file. Such files are called multiple segment files and are identical to the ones just outlined except that they have subheaders interspersed with data records that signal the start of a segment. The subheaders may be of any format, but all must have the same character in the first column. When using such files, you must specify the -M option. The unique character is by default '', but you can override that by appending your chosen character to the M option. E.g., -MH will look for subheaders starting with H, whereas -M'*' will check for asterisks (The quotes are necessary since * has special meaning to UNIX). The subheaders may contain -W and -G options for specifying pen and fill attributes for individual segments. These settings will override the corresponding command line options.

Next: B.1.2 Binary tables Up: B.1 Table data Previous: B.1 Table data Contents Index