Specify a file to which to write a formatted backtrace. The file will only be created if there is a backtrace created, typically when an error occurs.

Specify the format of the backtrace written to the files specified by --backtrace-file, one of plain, xml or json.

Read the comments from the specified path and add them to the output gradient.

The format is custom XML which should be fairly easy to generate, see the output of --comments-write for examples.

Write the comments in the input to the specified path.

Use the comments in the input file as the comments for the output file.

Create a comment with summary data (the date of creation, name and version of the cptutils package) in the output file.

Brief help.

Specify the z-value of the hinge in the cpt file. If there is no hinge directive (i.e., a SOFT_HINGE or HARD_HINGE) in the input, then this option has no effect.

When normalising (with the --z-normalise option), this gives the z-value in the input which is mapped to zero. That z-value must be one of the stops in the input.

When denormalising (with the --z-denormalise option), this gives the value in the output to which zero in the input is mapped. This option can be viewed as the counterpart to the +hvalue appended to the -C option for the makecpt (1) .

If the input cpt has a SOFT_HINGE directive, then activate that hinge (resulting in independent scaling of the two halves of the gradient either side of the hinge).

If the input does not have such a directive, then this option has no effect.

On writing the output, convert all colours to the specified model, one of "rgb" or "hsv". This has no effect on non-colour segments.

Write the output to path, rather than stdout.

The (z) range of the output, or the segments if the --segments switch is also given.

The min and max arguments of the --range switch are interpreted as the segment numbers (starting at one).

Verbose operation.

Version information.

Normalise the z-values in the cpt output into the range 0/1 (or to -1/1 if a hinge is present) and add a RANGE directive if not present in the input. This is the form used in GMT master files.

This option requires that output cpt version is at least 5.

Set the z-values in the cpt output into the range given by the RANGE directive, and remove that directive. If there is no RANGE then this option does nothing.

Use GMT 4 conventions when writing the cpt output: the colour-model code is uppercase, and the colours are separated by spaces.

This is incompatible with the -5 and -6 options of course.

At present this option is the default, but that will change at some point. So specify this option if your use of the output depends on the GMT 4 layout (consumed by a custom parser, for example).

Use GMT 5 conventions when writing the cpt output: the colour-model code is lowercase, and the colours are separated by a solidus for RGB, CMYK, by a dash for HSV.

This is incompatible with the -4 and -6 options of course.

As the -5 option, but allows the HARD_HINGE and SOFT_HINGE directives in place of the explicit HINGE = directive.

This is incompatible with the -4 and -5 options of course.