Temp. Job. Def. Sid. Con. Raw. Lsa. Sd. Add. Not. Iid. Pgc. LX. An




Yüklə 80.79 Kb.
tarix28.02.2016
ölçüsü80.79 Kb.


1 Formats of GMM Files
TEMP.JOB .DEF .SID .CON .RAW .LSA .SD .ADD .NOT .IID .PGC .LX .AN
TEMP.JOB
The first 1-8 characters of the file are the project name, usually just township/range. There is no other data in this file.

.DEF
A sample .DEF file is on the left, descriptive comments on the right:
Y not applicable to GMM

5 ARIZONA WEST MERCATOR state plane zone

1 NAD27=1 NAD83=2

2 (meters=1, Survey ft=2, Int. ft=3)

5000.000 default elevation

N read elevations from .LEV file

Y read error estimates from .SD

.100 1000.0 default for distance error estimate

4.0 default for angle error estimate

120.0 default for bearing error estimate

40.000 default for control N error estimate

40.000 default for control E error estimate

Y (mean geodetic brgs=Y, grid brgs=N)

.000 (Distance residual printout limit)

.0 (Angle residual printout limit)

.0 (Azimuth residual printout limit)

N error ellipses computed

N readjust w/ robusted error estimates

N (print adjusted grid brgs/dists)

Y (update .COR file)

T05NR14W Project name

14 Meridian

AZ State designation

12 UTM zone number

not applicable to GMM

1 not applicable to GMM




.SID
Below is a shortened example of a .SID file created by an Oracle query:
S5071 1.000 9999.0 1800.0 30.000 30.000

C GLO 11-DEC-1872 O FOREMAN

S5905 1.000 9000.0 1600.0 30.000 30.000

C GLO 04-APR-1880 O VULTURE CITY

C ----------------------------------------MINERALS:

S22151 1.000 7000.0 1200.0 30.000 30.000

C GLO 05-JUL-1908 O MS2511 m2400
For the lines starting with “S”:

The 1st field in Column 1 identifies SID data(S).

The 2nd field is the SID number and must start in the +2nd column.

The 3rd field is the Distance Error Estimate Constant, ft units.

The 4th field is the Distance Error Estimate PPM, no units.

The 5th field is the Bearing Error Estimate Constant, second units.

The 6th and 7th fields are obsolete.
Lines following the SID data are comment lines and start with the letter C. In the BLM, the standard for the first comment line after each “S” line is:

The 1st field in Column 1 identifies line as a Comment line(C).

The 2nd field is Source Agency, 3-4 character abbreviation, i.e. BLM, USFS.

The 3rd field is date that the plat was signed


The 4th field is the Survey Type, O = original, D = dependent resurvey, etc

The 5th field is the Surveyor’s name or MS number and Volume number.


The next comment line may be an entry in a .SID file specifying “non-GLO” units
S36970BT 0.100 5000.0 900.0 0.001 0.001

C BDY TR FROM T33NR30E

C DT:P

C DU:F

C DC:-1 +50

C BT:GA 0.0530

C BC:-2.1040
The 3 unit types are:

(1) DT: distance type, value consists of 1 character value

Allowable values: G (ground), E (ellipsoid), or P (plane/grid)

(2) DU: distance units as stored in RAW. Default is chains.

Allowable values: F (feet), C (chains), M (meters)

(3) BT: bearing type, value consists of 1 char value or 2 char value followed by a numeric value.

Allowable values: M (mean), F (forward), G (grid), C (compass/magnetic), or L (local/assumed). Column 7 can be blank or nil or an A (convert bearings to angles). If an A exists in column 7 it must be followed by an error estimate for the angles in DD.MMSS format. The error estimate can immediately follow the A or have leading spaces
The 2 corrections are:

(1) DC: distance correction (two numeric values)

The two numbers are the constant correction and the ppm correction. A negative value means the distance will get shorter. The constant correction is in the units of the desired linear units in .LSA (ft. or meters). The constant correction can immediately follow the : or any number of spaces can exist. Any number of spaces must exist between the constant correction and the ppm. You can have a zero constant and a non-zero ppm, and vice versa.
(2) BC: bearing correction (one numeric value)

DD.MMSS format with positive being clockwise and negative being a counter-clockwise correction.



.CON

TWP 0070N RNG 0260E PM GilaSalt R Arizona(AZ) DATE 93/12/15

ORIGIN 337976.0000 1093540.0000 5000.000 0 0 2000.0000 5000.0000

700140 335733.0015 1093232.0338 9600.000 23 23 27

700140 335733.1745 1093234.3656 9600.000 23 23 83

*700700 340220.2080 1093232.0520 9200.000 15 15 27

*700700 340220.3764 1093234.3880 9200.000 15 15 83
The control data fields are:

Columns 01-01: If non-space, is a comment line, data will not be used.

Columns 02-07: Point ID 6-digit format,

Columns 12-22: Latitude in DDMMSS.SSSS format,

Columns 24-35: Longitude in DDDMMSS.SSSS format,

Columns 37-44: Elevation in feet units,

Columns 45-48: Estimated Northing error in whole feet units,

Columns 50-53: Estimated Easting error in whole feet units,

Columns 56-57: North American Datum, either 27 or 83. HP = HARN
Optional: “Merge control” data.

*MT08NR26E 200100 200700


*M is a special comment line code for merging control.

T08NR26E is the adjacent township that is the source of coordinate data.

200100 is the point ID in the adjacent township

200700 is the point ID to be used in the current township, T07NR26E.



.RAW
T09NR13E 14 AZ 999999 100100 100140 40.070 1 500.0 11340

100140 100200 40.000 1 0.0 11340

100200 100240 40.110 1 100.0 11340

...


120700 100700 20.02 3 895900.0 6010

999998
The data between the 999999 and 999998 lines represent data from survey plats. The fields are:


The 1st field is the Point Identifier for the beginning of the line.

The 2nd field is the Point Identifier for the ending of the line.

The 3rd field is distance, in chain units.

The 4th field is the quadrant of the bearing; 1 = NE, 2 = SE.

The 5th field is the value of the bearing, DDMMSS.S format.

The 6th field is the Survey Identifier number (SID), refer to the .SID file, above.




.LSA.
The .LSA. has 5 segments. Below is a shortened list:
700100 653137.527 1055152.756 0

700200 653126.637 1060413.534 0

700300 653100.770 1065747.464 0

700700 653010.374 1086873.400 1

700100 700200 5280.000 0

700200 700300 5280.000 0

700300 700400 5280.000 1

0 0 0 0 0 .00 1

700100 700200 0 0 .00 0

700200 700300 0 0 .00 0

700300 700400 0 0 .00 1

700600 653059.258 1081552.147 0

600660 647756.151 1085478.873 0

700640 653046.086 1084201.999 0

700660 653039.534 1085526.250 1

The first segment is a list of known control imported from .CON. X and Y are in State Plane coords, see .DEF file for zone number.

The second segment is the distances in feet

The third segment is the angles. Not used in GMM at this time

The fourth segment is the azimuths, clockwise from North

The fifth segment is the approximate coordinates computed for points that are not control. After an adjustment this segment contains all adjusted coordinates.

Each line is ended with a 0 or 1. The 1 signifies the end of the segment.

.SD
The .SD has 4 segments. Below is a shortened list:
700503 33.000 33.000 0

700600 33.000 33.000 0

700603 33.000 33.000 0

700700 33.000 33.000 1

100100 100200 32.680 0

100200 100300 32.680 0

100300 100400 32.680 0

600200 910010 3.430 0

600300 920010 2.585 1

0 0 0 4.00 1

100100 100200 600.00 0

100200 100300 600.00 0

100300 100400 600.00 0

600200 910010 240.00 0

600300 920010 400.00 1
The first segment is a list of known control imported from .CON.

The second segment is the distances in feet

The third segment is the angles in mean bearing.

The final segment is the azimuths, clockwise from true North.



.ADD
1 107140 100140 140140 .00000 1 15.310 55.310

2 107120 100120 140120 .00000 1 .000 .000

2 0 107100 107140 .00000 1 .000 .000

2 107160 100160 140160 .00000 1 .000 .000

2 0 107140 107200 .00000 1 .000 .000

1 910040 910030 1 89.59380 1 22.720 0.000

1 910050 910040 1 89.59380 1 9.090 0.000

2 908025 910050 3 0.01170 1 0.000 0.000

2 0 908030 908020 0.00000 2 0.000 0.000

3 910001 460560


The first 5 lines show how elongated 1/16ths (107xxx) of sec 31 are stored.

107140 is put in at proportion between two point IDs and the other 1/16ths are put in at intersection of two lines, whose endpoint IDs are stored.


The 1st field describes the type of action. 1 = traverse/proportion, 2 = intersection, 3 = add a line. Intersections require 2 lines of data.
The 2nd field is the point being generated. Value is 0 if not applicable.
The 3rd field is the known point starting the procedure. Intersections have two such points.
The 4th field is either the endpoint ID defining the bearing from the base point or the quadrant of a user-entered bearing. Not applicable = 0.
The 5th field is the bearing value of a user-entered bearing. Not applicable value is 0.
The 6th field is a digit describing whether the computation is based on a geodetic line (1) or plane line (2).
The 7th field is the record distance to the new corner.
The 8th field, if nonzero, is the record distance to the endpoint, in which case the record distances will be used as a proportion to apply to the adjusted overall distance.


.NOT
0

4

100565 813020



100568 813020

240132 260126

260126 300123
The first line describes how many “NOT points” follow. In Arizona the value is always 0.
The number after the “NOT” points describes how many “NOT lines” will follow.
The last segment is the listing of lines to be removed for post-subdivision display. The “from” and “to” IDs must be entered one each line in the same order as they exist in the .RAW file. Points (950xxx) generated through automatic intersections in APROP can be entered in this file.

.IID

SECTION 31 LOT 3 HAS 40.0 ACRES (COOR.) 40.0 ACRES (PLAT)

REPLACES NW 1/4 OF THE SW 1/4

Sec_031 J T_L 3 39.950; M14T0010NR0090E

100140 100120 120120 120140 100140

PARCEL N,E 867587.708 635133.435


The .IID file has an entry for each minimal polygon.

The 1st line has a verbose description of the parcel and acreage.

The 2nd line has a verbose description of the nominal location.

The 3rd line has the NILS-compliant text that is found in .AN file.

The 4th line is a list of IDs defining the polygon, in sequence.

The 5th line is the state plane coordinates of a point in the polygon.


If more attributes can define the polygon, then they can be listed as NILS-compliant text, positioned after the 3rd line.
Lines of data such as the 3rd line can be prepended with tags such as “ GLINK Edited:” or

“ Obsolete:”, which turn the existing data line into a comment line by starting data in the second column.


.PGC
The .PGC file is a backward-compatible file produced by GMM, but not used by it.
Columns 02-45: Identical format as in the .CON file.

Columns 45-48: Feet along the y ordinate to the intersection with the error ellipse.

Columns 50-53: Feet along the x ordinate to the intersection with the error ellipse.


  • Note: The error ellipse is computed to represent a 95% chance that the coordinate value is within the ellipse. Refer to the .ADJ file for exact description of the error ellipse. The error “diamond” created by these two values is a shorthand way of describing the amount of unreliability in the horizontal positioning.


.UTM
The .UTM file is a backward-compatible file produced by GMM and used to make DXF files
Columns 02-53: Identical format as in the .PGC file.

Columns 55-64: X value in UTM meters. See .DEF file for UTM zone.

Columns 65-74: Y value in UTM meters. See .DEF file for UTM zone.


.LX
The .LX file is a backward-compatible file that is used to support the BLM’s NILS environment. It is produced by GMM, but not used by it.
Line 1 is a header line with township and file creation date info, somewhat free-format.

Line 2 is an obsolete line.

The remainder of the file is in 3-4 segments, each ending with a 999999 code in column 2.
The first data segment is PLSS lines going Northerly, beginning with the Southwest corner.
The second data segment is PLSS lines going Westerly, beginning with the Southeast corner.
The third data segment is the remaining lines of the township
The fourth data segment is a list of points that are not on parcel boundaries. No lines in LX touch them. If there are no such lines in the township, then this segment does not exist.
In the data segments the data format is as follows:
Columns 02-07 Six digit GCDB point identifier

Columns 09-19 Latitude in format DDMMSS.ssss See .DEF for datum information.

Columns 21-19 Longitude in format DDDMMSS.ssss See .DEF for datum information.

Columns 34-41: Elevation in feet

Columns 42-45: Feet along the y ordinate to the intersection with the error ellipse.

Columns 47-50: Feet along the x ordinate to the intersection with the error ellipse.

Columns 51-53: Line sequence code, starting with 1.

Columns 55-55: Line type code. See table below

Columns 57-57: Pen code. See table below

Columns 59-68: UTM X coordinate. See .DEF file for zone and datum.

Columns 71-80: UTM Y coordinate. See .DEF file for zone and datum.

Line type code:



0

Section line or special survey

1

Sixteenth line, s or w of centerline

2

Section centerline

3

Sixteenth line, n or e of centerline



Pen code instruction:



1

Plot point at coord and lift up pen

2

Drop pen down to start line at coord

3

Drag pen to coordinate

4

Drag pen to coordinate and lift up






.AN
The .AN file is a backward-compatible file that is used to support the BLM’s NILS environment. It is produced by GMM, but not used by it.
Columns 06-07: Section number.

Columns 09-09: Nominal location, See table below

Columns 13-13: “Survey Type” is actually the parcel type. See table below.

Columns 15-19: Survey number

Columns 20-21: Survey suffix. Further defines uniqueness of parcel

Columns 25-25: Survey note. D=do not add acres R=replaced E=Exception to topology rules

Columns 27-35: Acreage in acres

Columns 39-52: Meridian & township identifier

Columns 54-64: Latitude. Format is DDDMMSS.ssss

Columns 66-77: Longitude. Format is DDDMMSS.ssss




Nominal location code and translation:



A

NE ¼ of the NE ¼

B

NW ¼ of the NE ¼

C

SW ¼ of the NE ¼

D

SE ¼ of the NE ¼

E

NE ¼ of the NW ¼

F

NW ¼ of the NW ¼

G

SW ¼ of the NW¼

H

SE ¼ of the NW ¼

I

NE ¼ of the SW ¼

J

NW ¼ of the SW ¼

K

SW ¼ of the SW ¼

L

SE ¼ of the SW ¼

M

NE ¼ of the SE ¼

N

NW ¼ of the SE ¼

O

SW ¼ of the SE ¼

P

SE ¼ of the SE ¼

Q

All nominals in the section

Z

Nominal location does not apply



Survey type code and translation:



A

Aliqout part

B

Aliquot part less than 40 acres

D

Allotment

E

Metes-and-bounds (reserved)

F

Farm Unit (reserved)

G

Land Grant (reserved)

H

Homestead

I

Indian allotment

J

Small tract and small holding claim

K

Block and lot within a townsite

L

Lot

M

Mineral suvey

N

Townsite

O

Fractional part of a section

R

Private land (reserved)

T

Tract

U

Unsurveyed

W

Water

Z

Unsurveyed, Unprotracted

2

Tract other than cadastral survey







p.


Verilənlər bazası müəlliflik hüququ ilə müdafiə olunur ©www.azrefs.org 2016
rəhbərliyinə müraciət

    Ana səhifə