PLS2CART
converts Public
Land Survey (PLS) descriptions into cartesian coordinate points (e.g. lat/long
or UTM). For example, the input PLS description might be: "T0280S
R0030E S021","SENW" and the output lat/long coordinates might be: -122.470414
43.122811.
___________________________________________________________________________
pls2cart
{DMS | DEC} {in_pls_file} {out_gen_file} {pls_gen_file}
{pls_att_file}
ARGUMENTS
{DMS | DEC}
- the format for the output coordinates in the
{out_gen_file}.
DMS - the
coordinates are output in degrees, minutes, and seconds in the format
DDD.MMSSSS. In other words, if the coordinate is latitude - 122
degrees, 28 minutes, 13.49 seconds, then it will be output as: -
122.281349. DMS is the default
DEC - the
coordinates are output in decimal values, e.g. decimal degrees for lat/long
coordinates and meters for UTM coordinates. For example, if the
coordinate is latitude -122 degrees, 28 minutes, 13.49 seconds, then it will be
output as: -122.470414 (i.e. -1 * (122 + 28/60 +
13.49/3600)).
{in_pls_file}
- the file containing PLS descriptions to be converted to cartesian
coordinates.
If no file is
specified, the user is prompted to enter the PLS
descriptions.
Each record of
input must have 3 comma-delimited values: township/range/section (TRS)
attribute, subsection code, and ID number. For
example:
"T0280S R0030E
S021","SENW", 8
This format is
the same as the output format used by CART2PLS and the input format used by the
PLSARC AML.
NOTE: The TRS
values and the PLS polygon attributes (see {pls_att_file}) must be in the same
format.
NOTE: In the
above example the section code is "SENW". This means the southeast
quarter of the northwest quarter of the section.
-------------
|__|__| |
| |x
| |
|-----|-----|
| | |
| | |
-------------
{out_gen_file}
- the name for the output file to contain the cartesian coordinates
generated from the input PLS descriptions.
If no file is
specified, the results are displayed to the screen.
The file may
not be the name of an existing file or directory.
The file will
be created in ARC GENERATE point format. In other words, each record
will contain 3 space-delimited values: ID number, X coordinate, Y
coordinate. For example:
8 -122.281349
43.072212
This format is
the same as the input format used by CART2PLS.
The output
points are generated at the center of the TRS subsections referenced by the
input PLS description.
For each input
PLS description whose TRS attribute does not occur among the list of PLS polygon
attributes (see {pls_att_file}), this is recorded to a reject file named the
same as the {out_gen_file} with a '.rej' extension. If no
{out_gen_file} is specified, the rejects are also displayed to the
screen.
{pls_gen_file}
- the file containing the PLS section polygons.
The file should
be in ARC GENERATE polygon format. Create it using the ARC UNGENERATE
command to export an ARC polygon coverage of the PLS
sections.
PLS2CART will
convert this file into a binary format in the following 6 files: section.hdr,
section.fea, section.isl, section.crd, section.qtq, and
section.qtf. These files will be created in the directory from which
PLS2CART is executed. These files are in the same format as those
created by CART2PLS.
If
{pls_gen_file} is not specified, then the 6 section.??? files must already
exist.
Therefore, only
specify {pls_gen_file} the first time PLS2CART or CART2PLS is
run.
NOTE: In the
case of lat/long data, the coordinates should be formatted in decimal
degrees.
{pls_att_file}
- the file containing the PLS section attributes.
Each record of
the file should contain the Township, Range, and Section description of the
corresponding section polygon in the {pls_gen_file}. It can be
created using the UNLOAD command in ARC TABLES, and will look
like:
''
'T0180N R0080E
S006'
'T0180N R0080E
S005'
'T0180N R0080E
S008'
etc.
NOTE: The
attributes must be sequenced in the same order as the section
polygons. However, there is one extra attribute, and it is the first
record. It belongs to the universe polygon. Do not delete
it or else the attributes and polygons will become out of
sync.
PLS2CART
incorporates the attributes into the section.fea file.
As with
{pls_gen_file}, {pls_att_file} need only be specified the first time PLS2CART or
CART2PLS is run.
NOTES
- ARGUMENTS
listed within angle brackets (<>) are required, and those within squiggly
brackets ({}) are optional. To accept the default value for any
optional argument, enter a carrot (^), or enter nothing if no more arguments are
to be supplied.
EXAMPLES
To see the
usage:
%
pls2cart
Usage: pls2cart
{DMS | DEC} {in_pls_file}
{out_gen_file}
{pls_gen_file} {pls_att_file}
The initial run
to create the section files:
% pls2cart dms
^ ^ rr_sec.gen rr_sec.att
Enter:
<"TRS"> <"subsection"> <id> (type END to exit)
"T0280S R0030E S021","NENESENW", 8
8 -122.281349
43.072212
Enter:
<"TRS"> <"subsection"> <id> (type END to
exit)
end
A subsequent
run to convert a file of input PLS descriptions:
% pls2cart ^
firepls firell