polespotter

Find stage poles given fracture zones and abyssal hills

Synopsis

gmt polespotter [ -Aabyssalhills ] [ -Dspacing ] [ -Ea|fsigma ] [ -Ffracturezones ] [ -Goutgrid ] [ -Iincrement ] [ -N ] [ -Rregion ] [ -Sl|p|s[modifiers] ] [ -V[level] ] [ -bibinary ] [ -di[+ccol]nodata ] [ -eregexp ] [ -hheaders ] [ -iflags ] [ -oflags ] [ -rreg ] [ -:[i|o] ] [ --PAR=value ]

Note: No space is allowed between the option flag and the associated arguments.

Description

polespotter reads line segments (abyssal hill fabric lineaments and/or fracture zone lineaments) and performs one of three types of scans. In spot mode it computes great circles for each individual segment along these lines. The bisector great circles to fracture zones and the great circle extensions of abyssal hills are expected to intersect at potential rotation poles. The assumption is that abyssal hill lines are meridians and fracture zones are parallels with respect to the rotation pole. Line density may be computed and returned via a grid, the great circle lines may be returned via stdout, and the intersections of the great circles may be saved to file. In line mode it will determine which line segments are compatible with a given trial pole, while in pole mode it will compute chi-squared misfits for all the poles defined by the grid.

Optional Arguments

-Aabyssalhills

File with multiple segments of abyssal hill lineaments. These are assumed to reflect the great circle direction towards the rotation pole in effect when the seafloor was formed.

-Dstep

Sets the line increment for all great circles produced, in km [5]. Actual spacing will be adjusted to give an integer number of steps along the full circle.

-E

Provide different 1-sigma angular uncertainty (in degrees) in the orientation of abyssal hills or fracture zones. Give -Easigma to set the former [1] and -Efsigma for the latter [1]. These sigma values are then used to form weights = 1/sigma.

-Ffracturezones

File with multiple segments of fracture zone lineaments. These are assumed to reflect small circles about the rotation pole in effect when the seafloor was formed.

-Goutgrid[=ID][+ddivisor][+ninvalid] [+ooffset|a][+sscale|a] [:driver[dataType][+coptions]]

Specify name for output grid. For spot mode we will accumulate great circle line density for the grid. Each bin that is crossed by a great circle is incremented by 1, multiplied by cos(latitude), the length of the fracture zone or abyssal line segment used to define the great circle, and any overall weight set via -E. In pole mode we return the chi-squared misfit surface. Not used in line mode. Optionally, append =ID for writing a specific file format (See full description). The following modifiers are supported:

  • +d - Divide data values by given divisor [Default is 1].

  • +n - Replace data values matching invalid with a NaN.

  • +o - Offset data values by the given offset, or append a for automatic range offset to preserve precision for integer grids [Default is 0].

  • +s - Scale data values by the given scale, or append a for automatic scaling to preserve precision for integer grids [Default is 1].

Note: Any offset is added before any scaling. +sa also sets +oa (unless overridden). To write specific formats via GDAL, use = gd and supply driver (and optionally dataType) and/or one or more concatenated GDAL -co options using +c. See the “Writing grids and images” cookbook section for more details.

-Ix_inc[+e|n][/y_inc[+e|n]]

Set the grid spacing as x_inc [and optionally y_inc].

Geographical (degrees) coordinates: Optionally, append an increment unit. Choose among:

  • m to indicate arc minutes

  • s to indicate arc seconds

  • e (meter), f (foot), k (km), M (mile), n (nautical mile) or u (US survey foot), in which case the increment will be converted to the equivalent degrees longitude at the middle latitude of the region (the conversion depends on PROJ_ELLIPSOID). If y_inc is given but set to 0 it will be reset equal to x_inc; otherwise it will be converted to degrees latitude.

All coordinates: The following modifiers are supported:

  • +e to slightly adjust the max x (east) or y (north) to fit exactly the given increment if needed [Default is to slightly adjust the increment to fit the given domain].

  • +n to define the number of nodes rather than the increment, in which case the increment is recalculated from the number of nodes, the registration (see GMT File Formats), and the domain. Note: If -Rgrdfile is used then the grid spacing and the registration have already been initialized; use -I and -R to override these values.

-N

Normalize the grid so max value equals 1 [no normalization].

-Rwest/east/south/north[/zmin/zmax][+r][+uunit]

Specify the region of interest.

The region may be specified in one of several ways:

  1. -Rwest/east/south/north[+uunit]. This is the standard way to specify geographic regions when using map projections where meridians and parallels are rectilinear. The coordinates may be specified in decimal degrees or in [±]dd:mm[:ss.xxx][W|E|S|N] format. Optionally, append +uunit to specify a region in projected units (e.g., UTM meters) where west/east/south/north are Cartesian projected coordinates compatible with the chosen projection (-J) and unit is an allowable distance unit; we inversely project to determine the actual rectangular geographic region.

  2. -Rwest/south/east/north+r. This form is useful for map projections that are oblique, making meridians and parallels poor choices for map boundaries. Here, we instead specify the lower left corner and upper right corner geographic coordinates, followed by the modifier +r. This form guarantees a rectangular map even though lines of equal longitude and latitude are not straight lines.

  3. -Rg or -Rd. These forms can be used to quickly specify the global domain (0/360 for -Rg and -180/+180 for -Rd in longitude, with -90/+90 in latitude).

  4. -Rcode1,code2,…[+e|r|Rincs]. This indirectly supplies the region by consulting the DCW (Digital Chart of the World) database and derives the bounding regions for one or more countries given by the codes. Simply append one or more comma-separated countries using the two-character ISO 3166-1 alpha-2 convention. To select a state within a country (if available), append .state, e.g, US.TX for Texas. To specify a whole continent, prepend = to any of the continent codes AF (Africa), AN (Antarctica), AS (Asia), EU (Europe), OC (Oceania), NA (North America), or SA (South America). The following modifiers can be appended:

    • +r to adjust the region boundaries to be multiples of the steps indicated by inc, xinc/yinc, or winc/einc/sinc/ninc [default is no adjustment]. For example, -RFR+r1 will select the national bounding box of France rounded to nearest integer degree.

    • +R to extend the region outward by adding the amounts specified by inc, xinc/yinc, or winc/einc/sinc/ninc [default is no extension].

    • +e to adjust the region boundaries to be multiples of the steps indicated by inc, xinc/yinc, or winc/einc/sinc/ninc, while ensuring that the bounding box extends by at least 0.25 times the increment [default is no adjustment].

  5. -Rjustifylon0/lat0/nx/ny, where justify is a 2-character combination of L|C|R (for left, center, or right) and T|M|B (for top, middle, or bottom) (e.g., BL for lower left). The two character code justify indicates which point on a rectangular region region the lon0/lat0 coordinates refer to and the grid dimensions nx and ny are used with grid spacings given via -I to create the corresponding region. This method can be used when creating grids. For example, -RCM25/25/50/50 specifies a 50x50 grid centered on 25,25.

  6. -Rgridfile. This will copy the domain settings found for the grid in specified file. Note that depending on the nature of the calling module, this mechanism will also set grid spacing and possibly the grid registration (see Grid registration: The -r option).

  7. -Ra[uto] or -Re[xact]. Under modern mode, and for plotting modules only, you can automatically determine the region from the data used. You can either get the exact area using -Re [Default if no -R is given] or a slightly larger area sensibly rounded outwards to the next multiple of increments that depend on the data range using -Ra.

-Sl|p|s[modifiers]

Set the scan mode for this run. Choose from lines, poles, or spots. Depending on the mode there may be required and optional arguments as indicated below:

-Slplon/plat[+m]

Line mode means we accept a plon/plat trial pole location and determine how compatible each data segment is with the predictions of small circles (for fracture zones) and meridians (for abyssal hills). By default we report summary statistics (chi2, table, segment, type) for each line segment. Append +m to instead report the misfit information (mlon, mlat, del_angle, chi2, table, segment, type) for each mid-point along all multi-point line segments. The information is written to standard output.

-Sp

Pole mode means we search for all poles on the given grid and determine the weighted chi-square misfit to all given line constraints. This mode requires -G, -R, -I (and optionally -r).

-Ss[+cxfile][+l]

Spot mode means we compute bisectors to fracture zones and meridians along abyssal hills and determine intersections of all these great circles. You can append any of two modifiers: +l will dump all great circles produced to standard output [no output], and +cxfile will compute the intersections of all great circles and write the locations to xfile. This output has 5 columns: lon, lat, weight, cos, type, where weight is the combined length weight from the two generating line segments, cos is the cosine of the angle between the intersecting lines, and type is either 0 (AH intersect AH), 1 (AH intersect FZ), or 2 (FZ intersect FZ), where AH means an abyssal hill great circle and FZ means a bisector great circle to a fracture zone.

-V[level]

Select verbosity level [w]. (See full description) (See cookbook information).

-birecord[+b|l] (more …)

Select native binary format for primary table input. [Default is 5 input columns].

-dinodata[+ccol] (more …)

Replace input columns that equal nodata with NaN.

-e[~]“pattern” | -e[~]/regexp/[i] (more …)

Only accept data records that match the given pattern.

-h[i|o][n][+c][+d][+msegheader][+rremark][+ttitle] (more …)

Skip or produce header record(s).

-icols[+l][+ddivisor][+sscale|d|k][+ooffset][,][,t[word]] (more …)

Select input columns and transformations (0 is first column, t is trailing text, append word to read one word only).

-ocols[,…][,t[word]] (more …)

Select output columns (0 is first column; t is trailing text, append word to write one word only).

-r[g|p] (more …)

Set node registration [gridline].

-:[i|o] (more …)

Swap 1st and 2nd column on input and/or output.

-^ or just -

Print a short message about the syntax of the command, then exit (NOTE: on Windows just use -).

-+ or just +

Print an extensive usage (help) message, including the explanation of any module-specific option (but not the GMT common options), then exit.

-? or no arguments

Print a complete usage (help) message, including the explanation of all options, then exit.

--PAR=value

Temporarily override a GMT default setting; repeatable. See gmt.conf for parameters.

Geodetic versus Geocentric Coordinates

All spherical rotations are applied to geocentric coordinates. This means that incoming data points and grids are considered to represent geodetic coordinates and must first be converted to geocentric coordinates. Rotations are then applied, and the final reconstructed points are converted back to geodetic coordinates. This default behavior can be bypassed if the ellipsoid setting PROJ_ELLIPSOID is changed to Sphere.

Notes

  1. Each input line is expected to contain two or more points, and each consecutive pairs of points define a great circle line segment. For fracture zones, these points should be digitized often enough so that the great circle between then can approximate the small circle.

  2. All line segments are given equal angular uncertainty [1, unless changed by -E]. However, individual line segments can override this weight by adding a -Dsigma argument in the segment headers (in degrees).

Examples

To create a polespotting image from the abyssal hill and fracture zone fabric (lon,lat) data in the files hills.txt and fractures.txt, on a 1x1 degree grid for the northern hemisphere, sampling the great circles every 10 km, and also dump the great circles to standard output, try

gmt polespotter -Ahills.txt -Ffractures.txt -D10 -Gpoles.nc -R0/360/0/90 -I1 -V -Ss+l > lines.txt

This file can then be plotted with grdimage.