Help for NSYTWKSP

PURPOSE:

NSYTWKSP computes a mask showing the workspace boundaries for the
InSight mission.  The boundaries are computed by comparing the XYZ
coordinates with precomputed polygons indicating the edges of the
workspace.

The output is a single-band BYTE image, containing a code 0-5 showing
which polygons the point is inside.  See below for values.

This program could easily by multimission-ized.

EXECUTION:

nsytwksp inp=data.xyz out=data.wss -seis
where:
data.xyz is an input 3-band image of type REAL with the X, Y and Z values
at that pixel in meters (the unit is actually irrelevant).

METHOD:

The actual core algorithm was developed by Steven Myint from Section 347.
It was then refactored to meet VICAR standards by Bob Deen.

The algorithm is simple: for each point, it checks if the XY coordinate
is within the boundary specified by the input polygon file.  Z is ignored.
The XYZ coordinate is converted to the coordinate system specified in
COORD first.

The files are different based on instrument: HP3 and SEIS (actually a
combination of SEIS and WTS).  Selection is made via a parameter.

OUTPUT FORMAT:

The output is a 1-band file in BYTE format.

For HP3 the possible values are:

  0 = no data
  1 = outside HP3 boundary, or no data
  2 = n/a
  3 = inside HP3 workspace, outside HP3 grapple point boundary
  4 = n/a
  5 = inside HP3 grapple point boundary 

For SEIS/WTS the possible values are:

  0 = no data
  1 = outside all SEIS/WTS areas, or no data
  2 = inside WTS boundary, outside SEIS boundary
  3 = n/a
  4 = inside WTS and SEIS boundaries, outside SEIS/WTS grapple point boundary
  5 = inside SEIS/WTS grapple point boundary 

The assigned numbers max at 5 (where 5 is best) in order to maintain
consistency across all InSight masks.  The 1-4 numbers are arbitrary but
were chosen so they would be different between WSH and WSS products.

Note: it is assumed the polygons strictly nest, with higher numbers above
being smaller than previous polygons.  If not, the highest number wins
(in other words, polygons are traversed in order from highest to lowest, and
once a number is assigned to a given pixel, no other polyons are checked).


HISTORY:
2015-05-02	rgd	Initial version, based on code from Steven Myint (347)
COGNIZANT PROGRAMMER: B. Deen

PARAMETERS: