United States Systems Laboratory
Environmental Environmental Monitoring
Protection P.O. Box 93478
Agency Las Vegas, NV 89193-3478
Research and Development
&EPA DATABASE DICTIONARY
DENVER BROWN CLOUD
AIRSHED STUDY
•8 «
-------
DATABASE DICTIONARY
DENVER BROWN CLOUD AIRSHED STUDY
A GEOGRAPHIC INFORMATION SYSTEMS DEMONSTRATION PROJECT
REGION 8, U.S. ENVIRONMENTAL PROTECTION AGENCY
by
Jonathan Pickus
Environmental Programs
Lockheed Engineering and Sciences Company
Las Vegas, Neveda 89119
Contract No. 68-03-3245
Project Officer
Mason Hewitt
Advanced Monitoring Systems Division
Remote and Air Monitoring Branch
ENVIRONMENTAL MONITORING SYSTEMS LABORATORY
OFFICE OF RESEARCH AND DEVELOPMENT
U.S. ENVIRONMENTAL PROTECTION AGENCY
P.O. BOX 93478
LAS VEGAS, NV 8 9114
-------
NOT ICS!
Although the information in this document has been funded wholly or in
part by the United States Environmental Protection Agency under Contract
No. 68-03-3245 to Lockheed Engineering and Science Company, Inc., it does
not necessarily reflect the views of the Agency and no official
endorsement should be inferred.
Mention of trade names or commercial products does not constitute
endorsement or recommendation for use.
This document is a preliminary draft. It has not been formally released
by the U.S. Environmental Protection Agency and should not at this stage
be construed to represent Agency Policy. It is being circulated for
comments on its technical merit and policy implications.
-------
CONTENTS
Abstract iv
Project Summary v
Definitions and Acronyms xii
1. DBC Data Dictionary 1
2. Data Dictionary Listings 2
Census 2
Cultural 5
Elevation 17
ESRI 24
Lidar 41
Quality Assurance 138
-------
ABSTRACT
The Denver Brown Cloud project attempted to model atmospheric particulate
distribution utilizing the technologies of Light Direction and Ranging
(LIDAR) and geographic information systems (GIS). Project objectives
included the development of GIS methods to analyze LIDAR data to study
the structure, sources, and impacts of haze associated with wintertime
inversion (brown cloud) in Denver, Colorado. Contour, polygonal and point
planimetric data structures for specific dates, times and elevations were
developed. An early morning and mid-afternoon event were modeled for
January 13, and 20, 1988 respectively. Preliminary statistical tests
indicated a non-parametric correlation between LIDAR and carbon monoxide
data for the January 20, 1988 model. Incomplete ground monitoring data
and lack of real time air quality measurements hampered the statistical
approach necessary for calibration of population risk assessment models.
In addition to the development of methodology for the analysis of LIDAR
data, this study contributed to the Agency's understanding of the Denver
airshed and could be used in planning future LIDAR missions.
iv
-------
PROJECT SUMMARY
I. INTRODUCTION
The Denver airshed during winter is often characterized by high densities
of particulate matter suspended in the air. The winter climatology of the
Denver basin promotes the trapping of air pollution in shallow inversion
layers when downslope flow off the Rocky Mountains warms as it subsides
and overrides cooler local areas. Local, and Federal, authorities have
been concerned about this problem for the last ten years.
The Denver Brown Cloud (DBC) project attempted to characterize
atmospheric particulate distribution of the Denver airshed utilizing the
technologies of Light Direction and Ranging (LIDAR) and geographic
information systems (GIS). LIDAR, an active airborne laser-based system,
has been used over the last decade to observe and to study a variety of
atmospheric boundary layer structures. GIS technology integrates,
displays and analyzes geographic data, and it has been adopted by EPA as
a standard tool for environmental analysis by regional and program
offices.
EPA Region 8 sponsored a LIDAR mission to acquire data in January 1988
during a winter inversion period. The LIDAR instrument was on-board a
Las Vegas-based aircraft and was operated by personnel from the EPA
Environmental Monitoring Systems, Las Vegas, NV (EMSL-LV). The GIS system
employed was ARC/INFO. The data collection and analysis was performed by
the Remote and Air Monitoring Branch, Lockheed Engineering and Science
Co. (LESC), under EPA contract number 68-03-3245, and the Environmental
Research Center of the University of Nevada at Las Vegas.
EMSL-LV sought to take advantage of the superior spatial data management
tools within GIS to devise innovative methods for analyzing LIDAR data.
GIS methods research involved the incorporation of LIDAR, and other air
quality data, for use in new techniques of analysis toward air quality
evaluation. The principal project goal was to develop methodology to use
GIS to analyze LIDAR data in order to better characterize haze associated
with wintertime inversion (brown cloud) in Denver Colorado.
II. LIDAR TECHNICAL REVIEW
LIDAR basically operates on the same principle as radar technology. A
beam of light is transmitted from the airborne laser and is intercepted
by suspended particulates and the ground. Part of the intercepted light
is reflected (or backscattered) into the receiver (normally a telescope).
LIDAR provides information on the character and distribution of the
aerosol.
The main component of the EMSL-LV LIDAR is the frequency doubled
Neodymium Yag laser. The laser light is transmitted at wavelengths 1.02 4
um (Infrared) and 0.532 um (Green). These wavelengths enable detection
of particulate backscattering as well as some due to molecular
v
-------
backscattering. The light from the aerosols is collected through a 36-cm
Newtonian telescope receiver. The signal processing is accomplished done
by a subsystem which corrected the background and instantaneous laser
peak-power values, and converted the signals to digital format. The
entire LIDAR system is flown in a downward-looking configuration in an
aircraft. The airborne-based nature of LIDAR enables the sampling of
large volumes of air in a short time span.
The EPA airborne LIDAR has been used successfully for several years to
track and monitor large point-source plumes, urban plumes, polluted air
masses and aerosol transport mechanisms (McElroy, 1987; Wakimoto and
McElroy, 1986) . The instrument's design and aircraft platform make it
particularly useful for studies covering regional-scale problems and
complex terrain/urban areas.
III. GIS MOTIVATION AND METHODS
Prior to GIS applications, the principal method of LIDAR data analysis
involved vertical profiles derived from a two dimensional height verses
ground distance graphs. This transect analysis used data which was
essentially unaltered other than for data normalization. Each transect
plot would present plume and aerosol concentrations along the aircraft
flight lines. The limitation of this form of analysis made the study of
the whole airshed difficult. GIS offered the tools to integrate, analyze,
and display LIDAR's large datasets in a more intuitive planimetric model.
The DBC LIDAR mission was undertaken during the period of January 6-26,
1988. Each mission, during this period, collected data for morning or
afternoon events and was flown primarily along transects in a east-west
direction. There was a vast quantity of data generated by these missions.
Each transect, taking about 6-10 minutes to fly, approximated distances
of nine miles, with a LIDAR shot executed and measured about every 150
meters. LIDAR data was generated from reflectance values, or feedback
measured by the instrument. This feedback was measured 512 times per
shot, or every 20 vertical feet. Total data generated for a afternoon or
morning event exceeded 3,300,000 observations.
EMSL-LV adopted an approach based on modeling at a specific elevation
above ground level. Elevation specific models were derived from absolute
LIDAR shots along transects and interpolated LIDAR data between
transects. Data was assumed to behave in a uniform manner. Given the
potential dynamics at work with atmospheric phenomenon, this assumption
of uniformity may limit the representativeness of the model. However,
because the DBC study concentrated on the wintertime inversion, which is
characterized by a more stationary air mass at lower elevations, an
argument can be made in favor of this assumption.
The LIDAR to ARC integration required a program which read and normalized
the infrared LIDAR data return. In this way, data for a particular
transect and elevation above ground level (AGL) was obtained,
significantly reducing the data management overhead.
vi
-------
Mission LIDAR data files were converted to locational and attribute
ARC/INFO point generate files. The completed LIDAR to ARC link was
comprised of multiple transects, appended together, based on LIDAR data
at a common elevation AGL. The point topology format naturally
represented LIDAR returns making it an ideal platform for integrating
LIDAR with GIS.
Data Selection Criteria
The January 13 and January 20, 1988 events were selected for modeling
based, in part, on requests made by the EPA Region 8 office. Other data
selection criteria attempted to balance spatial extent and temporal
variability. The January 20, 1988 mission produced 31 transects ranging
in time from 0753 to 1759 central time. Seventeen transects, with times
from 0744 through 1406 central time, were generated for the January 13,
1988 mission. Transects were selected or excluded to maximize spatial
bounds while minimizing temporal variability. Spatial extent was critical
to avoid over or under representation of LIDAR data. Time was equally
important, considering the dynamic nature of atmospheric phenomena, and
was limited to the extent possible given the available data set.
Final transect model selection defined time extents of 1145 - 1430, for
the January 20, 1988 model and 0804 - 0944 central time for the January
13, 1988 model. Transect selections were converted to ARC/INFO point
topology and grouped together. These intermediate GIS coverages were in
excess of 6,500 data points and served as the basis for surface model
development.
Interpolation Methods
LIDAR surface models were created using actual and derived values from
the intermediate POINT GIS coverage. TIN, (Triangulated Irregular
Network), was the surface modeling software used because it contained a
variety of interpolation processes which allowed full compatibility with
the rest of the ARC/INFO system. TIN supported both non-regular and
regularly-spaced surface data. The data structure was comprised of
non-overlapping irregular triangles derived from spatially-significant
points. Each triangle contained X,Y,Z coordinates and information
concerning the neighboring triangles. This structure was extremely
efficient for data storage and surface modeling. Linear and Bivariate
Quintic (BQ) were two interpolation methods available using TIN. The BQ
interpolation method was used to generate the LIDAR surfaces. BQ, its
name derived in part from its assumption of a 5th order polynomial, was
an effective smoothing algorithm which allowed for the least number of
data points required to model the irregular surface.
The large volume of data points along each transect necessitated a
sampling criteria to avoid exaggerated interpolation along aircraft
flight lines. Exaggeration was caused by spatial limitations related to
distance between and along flight transects. Proximal tolerances was
adjusted to avoid any apparent distortion of the surface.
vii
-------
IV. GIS ANALYSIS AND QUALITY ASSURANCE
Quality assurance of the LIDAR model relied upon correlation to air
quality data derived from ground-based stations and known pollution
sources. Correlation was evaluated based on proximity analysis between
backscatter values of each LIDAR model and pollution measurements.
Strength of relationships was a function of distance and rankings of
pollution sources. This type of analysis was used to evaluate the utility
of the model to relate plumes and pollution sources. Correlation was
restricted to the 30 meter AGL model for analysis. The 30 meter AGL mark
was the lowest elevation level before distortion from ground reflectance
became evident.
The lack of point source pollution data limited the LIDAR model's quality
assurance and calibration tasks to correlation to data obtained from the
Atmospheric Information Retrieval System (AIRS) air monitoring network.
This network contained ten AIRS stations located in Denver's most
urbanized areas. High correlation to specific types of pollutants may
allow calibration, and, thus, a confident assessment modeling of the
Denver Brown Cloud. However, not enough data calibration and analysis has
been performed at this time to associate LIDAR measurements to
particulate type and concentration.
Usable air quality data for model correlation, monitored by the Denver
AIRS network, were limited to carbon monoxide (CO) because of incomplete
collection records. Because CO is considered to be a proportionally
significant compound among those which constitute the Denver haze, a
direct relationship between CO and particulates was assumed.
Relating time and location between the model and AIRS data became
problematic. The AIRS network locations, data temporal resolution and
inconsistent number of observations hampered the usefulness of the
network for testing purposes. The AIRS network locations were limited and
could be used to test only a small portion of each model's extent. The
lack of adequate spatial representation prevented meaningful correlation
tests for the January 13, 1988 model. The temporal resolution of air
quality data was also less than ideal for comparison to the higher
resolution LIDAR data: air quality data were averaged at hourly
increments, while LIDAR data measurements were timed to the nearest
second.
Quality assurance to the AIRS network for the event, was applied in a two
phased approach. First, if raw (non-interpolated) LIDAR data supported
a viable relationship to air quality, then interpolated GIS LIDAR model
evaluation became realistic. This approach permitted a pragmatic
assessment of the interpolation process. Statistical testing was compiled
using the Statistical Analysis System (SAS). Data transfer between both
SAS and ARC/INFO proved to be simple because of the similarities and
flexibilities of INFO, and SAS. Data extracted from the ARC/INFO data
models included: distances from each LIDAR data point to each monitoring
stations, LIDAR values, and time. The AIRS data included station
viii
-------
location, time, and CO values. INFO and Fortran programs generated
distance matrices, and related all data into a common file format.
Subsequent tasks included parsing the data based on distance from any
station and creating a system file for transfer to SAS.
January 13 LIDAR Models
The January 13, 1988 model was developed from data collected between 0804
and 0944 central time. The limited temporal range of the selected LIDAR
data should improve the validity of the model. For these models, high
reflectance areas were pronounced over downtown and residential
locations. These high reflectance areas may coincide with commuter
impacts which appear to relate well with the model's time period. Lower
overall intensity ranges, as compared with the January 20, 1988,
afternoon model, also coincided with the less severe inversion
characteristics reported for this day.
Correlation analysis for the January 13, 1988 model proved inconclusive
as few transect data points were within close proximity to AIRS ground
monitoring stations. Over 94% of the LIDAR data were between 1500 and
2500 meters from any one monitoring station. The lack of a sufficient
proximal relationship prevented statistical testing of the January 13,
198 8 data model.
January 20, 1988 LIDAR Model
The January 20, 1988 LIDAR models were generated from data collected from
1145 to 1430, and were used for the first LIDAR/GIS modeling effort
undertaken by EMSL-LV. LIDAR ranges were identified based on the LIDAR
backscatter measured. A relationship was assumed based on a correlation
between aerosols and particulates, and reflectance values.
The highest intensity areas were north of Denver, a relatively under-
populated area. Atmospheric transport, in conjunction with topographical
influences, may present a plausible explanation. Mountain ranges east and
north of the city compound inversion episodes. During these winter
inversion events, the Denver brown cloud tends to migrate north
throughout the morning early-afternoon periods. A reversal of these
migration tendencies was known to occur during later afternoon-early
evening periods, further exacerbating air quality (Watson and Chow,
1988). Ancillary geographic data, such as roads and municipal boundary
information, provided locational reference and potential insights into
spatial relationships. High LIDAR plumes appear to relate well to
north-eastern highway locations and airport locations.
Statistical results were mixed, which are shown in Tables 1-3. The
January 20, 1988 models, indicated a strong relationship between the AIRS
monitoring stations and both transect (raw) data and the interpolated
model data. Correlation coefficients demonstrated that distance from
LIDAR data to AIRS monitoring stations appeared to have an inverse
influence on the correlation coefficients.
ix
-------
Table I
Correlation Analysis
Spearmans Test - 1/20/88 Flight Transect Data Only
lu = Lidar Backscatter Units
Distance Corr.
Coeff.
N
Mean (lu)
Median (lu)
Min (lu)
Max (lu)
< 2500 meters
.25
264
78 . 5
74
0
249
< 1500 meters
. 49
100
71.6
67
0
249
< 1000 meters
. 72
38
70 . 8
64
8
249
Table II
Correlation Analysis CO/LIDAR
Spearmans Test - 1/20/88 Interpolated Model Data
lu = Lidar Backscatter Units
Distance Corr.
Coeff.
N
Mean (lu)
Median (lu)
Min (lu)
Max (lu)
< 1500 meters
.34
123
69. 8
83
13
121
< 1250 meters
.54
84
63.1
80.5
13
117
< 1000 meters
.75
58
71. 4
83.5
13
117
Table III
Regression Analysis CO/LIDAR
Interpolated Data 1/20/88 Interpolated Model
Distance N R-Square Adj-R-Square Coeff. Var.
< 1500 meters 122 .01 .00 80.5
< 1000 meters 58 .56 .55 55.6
Linear regression analysis, for the January 20, 1988 model, illustrated
the possible existence of relationships between CO and LIDAR, when the
distance was less then 1000 meters. The nature of the non-parametric
correlation and weak linear relationship precluded calibration of the
January 20, 1988 LIDAR model.
V. CONCLUSIONS
The DBC project provided a framework for the integration of data from
LIDAR, or other active remote sensors for advanced air characterization
studies using the GIS. These methodologies could also be applied to
other active remote sensing instruments as well. An elevation-specific
analysis technique was used to study boundary layers in conjunction with
other air quality, geographic, and anthropogenic data. Quality assurance
provided some insight into the feasibility of using LIDAR for assessment
modeling. While GIS provided the tools and data structures for
contaminant characterization, the nature of the spatial and temporal
x
-------
distribution of data precluded accurate calibration of the LIDAR data
model to ground-based air quality measurements. However the test results
indicated a strong relationship between LIDAR and CO, and were consistent
between the raw LIDAR data and the interpolated model for the January 20,
1988 mission. A more favorable distribution of transects, in relationship
to ground monitoring instrumentation and each other, and a smaller study
size are recommended for any future LIDAR/GIS studies.
VI. REFERENCES
1. J.L. McElroy, "Estimation of Pollutant Transport and Concentration
Distributions over Complex Terrain of Southern California Using Airborne
Lidar," JAPCA 37:1046-1051 (1987).
2. R.M. Wakimoto, and J.L. McElroy, "Lidar Observation of Elevated
Pollution
Layers over Los Angeles," Journal of Climate and Applied Meteorology,
Vol. 25, No. 11, November 1986.
3. Watson, and Chow et al, "Metropolitan Denver Brown Cloud Study",
Desert Research Institute, Volume 1, October 1988.
xi
-------
DBC DATA DICTIONARY
The Denver Brown Cloud Data Dictionary is a technical description of
each GIS dataset compiled to meet the project's objectives. Data
descriptions were organized alphabetically within six major categories.
These categories included:
Census : Socioeconmic data by census tract level.
Cultural : Boundaries, transportation, hydrography etc.
Elevation : Topography analysis
ESRI : Special coverages used to make plots for 1989 ESRI
conference.
Lidar : Lidar elevation specific models for 1/13 and 1/20/88,
QA : AIRS ground monitoring and 1/20/88 data files.
All datasets within this report were in the form of either ARC/INFO
coverages or INFO database files. The data descriptions provided in this
document quantify many technical features of these datasets, and
summarizes other information including dataset type, use and processing
steps.
All GIS data coverages, with the exception of the ESRI category, were
compiled in the Universal Transverse Mercator (UTM) map projection using
Zone 13 and a y-shift of -4,000,000 meters as projection parameters.
1
-------
DATA DICTIONARY LISTINGS
CENSUS
Census track information was digitzed from 1:24000 7.5 Minute USGS
Quarangles . Map data was manually transfered to each Quadrangle from the
1980 Census for Denver Standard Metropolitan Statistical Area Maps.
Socioenconmic information was obtained from digital Donnelly Marketing
statistical files for the same area. There may be some map errors due to
the poor map quality of the Statistical Area Maps.
Census Attribute Information
Name
Definition
Name
Definition
CENSUS
STATE
BG/ED
HH-93
POP-93
FLAG
M/0-5/88
M/14-17/88
M/18-24/88
M/30-34/88
M/35-44/88
M/55-64/88
M/0-5/93
M/14-17/93
M/18-24/93
M/30-34/93
M/35-44/93
M/55-64/93
F/6-13/88
F/X8-24/88
F/30-34/88
F/35-44/88
F/55-64/88
F/0-5/93
F/14-17/93
F/18-24/93
F/30-34/93
F/35-44/93
F/55-64/93
Tract Identification Numeric
State Numeric Code
1993 Population (Derived)
Used for Processing (N/A)
Male Age 0-5 1988
Male Age 14-17 1988
Male Age 18-24 1988
Male Age 30-34 1988
Male Age 35-44 1988
Mala Age 55-64 1988
Male Age 0-5 1993
Male Age 14-17 1993
Male Age 18-24 1993
Male Age 30-34 1993
Male Age 35-44 1993
Male Age 55-64 1993
Female Age 6-13 198 8
Female Age 18-24 1988
Female Age 30-34 1988
Female Age 35-44 1988
Female Age 55-64 1988
Female Age 0-5 1993
Female Age 14-17 1993
Female Age 18-24 1993
Female Age 30-34 1993
Female Age 35-44 1993
Female Age 55-64 1993
TRACT Tract Identification Integer
COUNTY County Numeric Code
HH-88
POP-88 1988 Population (Derived)
POP-80 1980 Population
SESI Socioeconomic Statistical
Index
M/6-13/88 Male Age 6-13 1988
M/25-29/88 Male Age 25-29 1988
M/35-44/88 Male Age 35-44 1988
M/45-54/88 Male Age 45-54 1988
M/65+/88 Male Age 65 and over 1988
M/6-13/93 Male Age 6-13 1993
M/25-29/93 Male Age 25-29 1993
M/35-44/93 Male Age 35-44 1993
M/45-54/93 Male Age 45-54 1993
M/65+/93 Male Age 65 and over 1993
F/0-5/88 Female Age 0-5 1988
F/14-17/88 Female Age 14-17 1988
F/25-29/88 Female Age 25-29 1988
F/35-44/88 Female Age 35-44 1988
F/45-54/88 Female Age 45-54 1988
F/65+/88 Female Age 65 and over 1988
F/6-13/93 Female Age 6-13 1993
F/25-29/93 Female Age 25-29 1993
F/35-44/93 Female Age 35-44 1993
F/45-54/93 Female Age 45-54 1993
F/65+/93 Female Age 65 and over 1993
Daaaription of Covaraga: CENSUS-UTM
Location: DISK$USER3:[DENVER.CENSUS]
Summary: Census track digitized from 1:24000 7.5 USGS Quadrangles
Covaraga Typa: Census
7aatura Typa: Polygon
Manuaaript Produaar: U.S. Department of Commerce, Bureau of the Census
Manuaari.pt: Map data transfered from Denver Standard Metropolitan Statistical Area Maps
Manuaari.pt Data: 1980
Manuaarlpt RMS error: < .005
Input Soala: 1:24000
Digitisad by: Jonathan Pickus, Lockheed Engineering and Sciences Co.
Data Produoad: 11/10/88
2
-------
CENSUS Continued...
DESCRIPTION OF SINGLE PRECISION COVERAGE CKNS09-UTM
ARCS
Arcs = 1039
Segments = 7239
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 384
Polygon Topology is present.
4 58 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
382
TOLERANCES
Fuzzy
Dangle
Xmin =
Xmax =
ITEMS 03/22/90
TYPE NAME
Tics =
Annotations =
Links =
STATUS
25
0
0
1.000 V
100.000 V
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
467814.813
532185 .188
Ymin =
Ymax =
INTERNAL NAME
385928.000
455362.500
NO. RECS LENGTH EXTERNL
DF
CENSUS-UTM.PAT
ARCOOODAT
375
449
XX
DF
CENSUS-UTM.BND
ARC001DAT
1
16
XX
DF
CENSUS-UTM.TIC
ARC002DAT
25
12
XX
CENSUS-UTM.PAT
375 Records Selected.
COLUMN ITEM NAME
1 AREA
5 PERIMETER
9 CENSUS-UTM#
13 CENSUS-UTM-ID
17 CENSUS
24 TRACT
30 STATE
32 COUNTY
35 BG/ED
42 HH-88
51 HH-93
60 POP-88
69 POP-93
78 POP-80
87 FLAG
88 SESI
90 M/0-5/88
99 M/6-13/88
108 M/14-17/88
117 M/18-24/88
126 M/25-29/88
135 M/30-34/88
144 M/35-44/88
153 M/45-54/88
162 M/55-64/88
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
4
12
F
3
-
4
12
F
3
-
4
5
B
0
-
4
5
B
0
-
7
7
N
2
-
6
6
I
-
-
2
2
I
-
-
3
3
I
-
-
7
7
-
-
9
9
I
-
-
9
9
I
-
-
9
9
I
-
-
9
9
I
-
-
9
9
I
-
-
1
1
I
-
-
2
2
I
-
-
9
9
I
-
-
9
9
I
-
-
9
9
I
-
-
9
9
I
-
-
9
9
I
-
-
9
9
I
-
-
9
9
I
-
-
9
9
I
-
-
9
9
I
-
-
3
-------
CENSUS Continued...
171
M/65+/88
9
9
I
-
-
180
M/0-5/93
9
9
I
-
-
189
M/6-13/93
9
9
I
-
-
198
M/14-17/93
9
9
I
-
-
207
M/18-24/93
9
9
I
-
-
216
M/25-29/93
9
9
I
-
-
225
M/30-34/93
9
9
I
-
-
234
M/35-44/93
9
9
I
-
-
243
M/45-54/93
9
9
I
-
-
252
M/55-64/93
9
9
I
-
-
261
M/65+/93
9
9
I
-
-
270
F/0-5/88
9
9
I
-
-
279
F/6-13/88
9
9
I
-
-
288
F/14-17/88
9
9
I
-
-
297
F/18-24/88
9
9
I
-
-
306
F/25-29/88
9
9
I
-
-
315
F/30-3 4/88
9
9
I
-
-
324
F/35-44/88
9
9
I
-
-
333
F/45-54/88
9
9
I
-
-
342
F/55-64/88
9
9
I
-
-
351
F/65+/88
9
9
1
-
-
360
F/0-5/93
9
9
I
-
-
369
F/6-13/93
9
9
I
-
-
378
F/14-17/93
9
9
I
-
-
387
F/18-24/93
9
9
I
-
-
396
F/25-29/93
9
9
I
-
-
405
F/30-34/93
9
9
I
-
-
414
F/35-4 4/93
9
9
I
-
-
423
F/45-54/93
9
9
I
-
-
432
F/55-64/93
9
9
I
-
-
441
F/65+/93
9
9
I
-
-
** REDEFINED ITEMS
•k *
24
ALL1
200
200
C
-
-
224
ALL2
200
200
C
-
-
30
ALL3
500
200
c
-
-
06 03/22/90
Date Time Elap CPU
I/O
Command
min sec
opr
8/25/88 19:43 0 5
8/25/88 19:46 0 11
9/ 6/88 16:29 0 0
11/ 9/88 14:37 1 16
11/10/88 13:39 7 140
11/14/88 15:35 2 20
3/26/90 14:39 0 6
3/26/90 14:42 1 28
237 CREATE CENSUS-UTM
566 COPY DUA1:[DENVER.CENSUS]CENSUS-UTM
57 EXTERNALALL
1016 COPY CENSUS-UTM CENSUS-UTM2
2410 CLEAN CENSUS-UTM2 CENSUS-UTM4 100 1
1086 copy [denver.census-final]census-utm4 census-utm
155 EXTERNAL CENSUS-UTM
1393 COPY [DENVER.RESTORE.CENSUS]CENSUS-UTM
4
-------
CULTURAL
Data was aquired from Petroleum Institute
transportation, hydrography and boundary data.
which represented
Hun* of Covtrag*: BOUNDARY
Location: DUBO:[DENVER.PI]
Summary: Boundary data representing state and national parka, military reservations,
grants and ranchos.
Covaraga Typa: Cultural
Faatura Typa: Polygon
Manuscript Producar: Petroleum Institute
Manuscript: Unknown
Manuscript Data: Unknown
Manuscript RMS mrroc: Unknown
Avsrag* RMS arror: Unknown
Input Soala: 1:24,000
Data Producad: 8/2/88
DESCRIPTION OT SINGLE PRECISION COVERAGE BOUNDARY
ARCS
POLYGONS
Arcs = 799
Segments = 2046
42 bytes of Arc Attribute Data
Polygons = 59
Polygon Topology is present.
30 bytes of Polygon Attribute Data
POINTS
Label Points =
58
TOLERANCES
SECONDARY FEATURES
Tics
Annotations
Links
STATUS
16
113
0
Fuzzy
Dangle
11.099 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
456932.375
Ymin -
358302.500
Xmax =
543067.625
Ymax —
469289.094
ITEMS
03/22/90
TYPE
NAME
INTERNAL NAME
NO. RECS
LENGTH
EXTERNL
DF
BOUNDARY.LKUP
ARC030DAT
4
37
DF
BOUNDARY. AAT
ARC031DAT
799
42
XX
DF
BOUNDARY.PAT
ARC032DAT
59
30
XX
DF
BOUNDARY.BND
ARC033DAT
1
16
XX
DF
BOUNDARY.TIC
ARC038DAT
16
12
XX
5
-------
BOUNDARY Continued.
BOUNDARY.PAT
59 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT
1
AREA
4
12
5
PERIMETER
4
12
9
BOUNDARY#
4
5
13
BOUNDARY-ID
4
5
17
FEATURE
4
4
21
SEARCH
10
10
31
SYMBOL
3
3
34
TYPE
30
30
TYPE N.DEC ALTERNATE NAME INDEXED?
F 3
F 3
BO
BO
I -
C -
I -
C
BOUNDARY.AAT
799 Records Selected.
COLUMN ITEM NAME
1
FNODE#
5
TNODE#
9
LPOLY#
13
RPOLY#
17
LENGTH
21
BOUNDARY#
25
BOUNDARY-ID
29
FEATURE
33
SEARCH
WIDTH
OUTPUT
TYPE
N.DEC
4
5
B
0
4
5
B
0
4
5
B
0
4
5
B
0
4
12
F
3
4
5
B
0
4
5
B
0
4
4
I
-
10
10
C
-
ALTERNATE NAME INDEXED?
LOG 03/22/90
Date Time Elap CPU I/O Command
min sec opr
8/
2/88
11:39
1
45
1062
8/
2/88
14:59
0
3
217
8/
3/88
8:58
2
74
2538
3/
6/90
11:36
0
2
118
import cover cult-l.eOO bound-1
RENAME BOUND-1 BOUNDARY
build boundary
EXTERNALALL [.PI]
6
-------
Ham* of Covaraga: CITY
Location: DUBO:(DENVER.PI]
Summary: City boundary coveraged obtained from Petrolium Institute. Item SEARCH contains
the first 10 characters of each city. Full city names can be displayed using the
Annotation commands in ARC/PLOT.
Covaraga Typa: Cultural
Faatura Typa: Polygon
Manuscript Produoar: Petroleum Institute
Manuscript: Unknown
Manuaoript Data: Unknown
Manuscript RMS arror: Unknown
Input Soala: 1:24,000
Data Produced: 8/3/89
DESCRIPTION OP SINSLS PRECISION COVERAGE CITY
ARCS
POLYGONS
Arcs = 1112
Segments = 3715
42 bytes of Arc Attribute Data
POINTS
Label Points =
46
TOLERANCES
Polygons = 7 6
Polygon Topology is present.
30 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics =
Annotations =
Links =
STATUS
16
40
0
Fuzzy -
Dangle =
8.988 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
457153.906
541492.563
Ymin =
Ymax =
379405.625
469289.094
ITEMS 03/22/90
DF CITY-RES.TIC
DF CITY-RES.BND
DF CITY-RES. PAT
DF CITY-RES.AAT
ARC005DAT
ARC052DAT
ARC053DAT
ARC054DAT
16
1
76
1112
12
16
30
42
XX
XX
XX
XX
CITY.PAT
7 6 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
AREA
4 12
F
3
-
5
PERIMETER
4 12
F
3
-
9
CITY#
4 5
B
0
-
13
CITY-ID
4 5
B
0
-
17
FEATURE
4 4
I
-
-
21
SEARCH
10 10
C
-
-
7
-------
CITY Continued.
CITY.AAT
1112 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
FNODE#
4
5
B
0
-
5
TNODE#
4
5
B
0
-
9
LPOLY#
4
5
B
0
-
13
RPOLY#
4
5
B
0
-
17
LENGTH
4
12
F
3
-
21
CITY-RES#
4
5
B
0
-
25
CITY-RES-ID
4
5
B
0
-
29
FEATURE
4
4
I
-
-
33
SEARCH
10
10
C
-
-
LOG 03/22/90
Date Time Elap CPU I/O Command
min sec opr
8/
2/88
12: 7
2
61
1075
IMPORT COVER CULT-2.E00 CITY
8/
3/88
13:57
3
97
2672
BUILD CITY
8/
3/88
14:35
3
96
2248
BUILD CITY
8/
3/88
14 :36
0
2
128
IDEDIT CITY
8/
3/88
14 : 51
3
57
2107
RESELECT CITY CITY-RES
3/
6/90
11:36
0
2
111
EXTERNALALL (.PI]
3/
6/90
11:36
0
2
101
EXTERNALALL [.PI]
8
-------
Hama of Covaraga: COUNTY
Location: DUBO:[DENVER.PI]
Summary: This coverage containes numerious boundary data. County boundaries are also
clearly marked. However, this coverage needs further processing to clearly delineate
county boundaries.
Covaraga Typa: Cultural
7aatura Typa: Polygon
Manuaaript Produoar: Petroleum Institute
Manuaaript: Unknown
Manuaaript Data: Unknown
Manuaaript RMS trior: Unknown
Input Scala: 1:24,000
Data Produoad: 8/2/88
DESCRIPTION OT SINGLE PRECISION COVERAGE COUNTY
ARCS
POLYGONS
Arcs = 812
Segments = 2062
42 bytes of Arc Attribute Data
POINTS
Label Points =
63
TOLERANCES
Polygons = 64
Polygon Topology is present.
30 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics
Annotations
Links
STATUS
16
113
0
Fuzzy
Dangle
11.099 V
0.000 V
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
456932.375
543067.625
Ymin =
Ymax =
358302.500
469209.094
ITEMS
TYPE
03/22/90
NAME
INTERNAL NAME
NO. RECS LENGTH
EXTERNL
DF
COUNTY.TIC
ARC008DAT
16
12
XX
DF
COUNTY.PAT
ARC00 9DAT
64
30
XX
DF
COUNTY.BND
ARC010DAT
1
16
XX
DF
COUNTY.AAT
ARC011DAT
812
42
XX
COUNTY.PAT
64 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT
TYPE N.DEC
ALTERNATE NAME
INDEXED?
1
AREA
4
12
F 3
-
5
PERIMETER
4
12
F 3
-
9
COUNTY#
4
5
B 0
-
13
COUNTY-ID
4
5
B 0
-
17
FEATURE
4
4
I
-
21
SEARCH
10
10
C
-
9
-------
COUNTY Continued.
COUNTY.AAT
812 Records Selected.
COLUMN ITEM NAME
1
FNODE#
5
TNODE#
9
LPOLY#
13
RPOLY#
17
LENGTH
21
COUNTY#
25
COUNTY-ID
29
FEATURE
33
SEARCH
LOG 03/22/90
Date Time Elap CPU
min sec
8/ 2/88 14: 7 2 47
3/ 6/90 11:36 0 2
WIDTH
OUTPUT
TYPE
N.DEC
4
5
B
0
4
5
B
0
4
5
B
0
4
5
B
0
4
12
F
3
4
5
B
0
4
5
B
0
4
4
•I
-
10
10
C
-
I/O Command
opr
693 IMPORT COVER COUNTY
95 EXTERNALALL [.PI]
ALTERNATE NAME INDEXED?
COUNTY
10
-------
Description of Covaraga: ROADS
Location: DUBO:[DENVER.PI]
Summary: Transportation coverage. Feature codes represent road categories. SEARCH is an
attribute which contains the first 10 characters of each road name. ROADS.LKUP is an INFO
lookup tables which can be related by FEATURE for plotting different road types.
Covaraga Typa: Cultural
Faatura Typa: Line
Manuscript Produaar: Petroleum Institute
Manuaaript: Unknown
Manuscript Data: Unknown
Manuscript RMS arror: Unknown
Input Saala: 1:24,000
Data Produaad: 8/2/88
DESCRIPTION OF SINCLE PRECISION COVERAGE ROADS
ARCS
POLYGONS
Arcs = 2265
Segments = 12044
42 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
Label Points =
TOLERANCES
SECONDARY FEATURES
Tics
Annotations
Links
STATUS
16
0
0
Fuzzy =
Dangle =
11.099 V
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
456953.844
542950.938
Ymin =
Ymax =
358302.500
469294.563
ITEMS 03/22/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF ROADS.AAT
DF ROADS.BND
DF ROADS.TIC
DF ROADS.LKUP
ARC012DAT
ARC013DAT
ARC014DAT
ARC029DAT
2265
1
16
5
42 XX
16 XX
12 XX
7
ROADS.AAT
2265 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
FNODE#
4
5
B
0
-
5
TNODE#
4
5
B
0
-
9
LPOLY#
4
5
B
0
-
13
RPOLY#
4
5
B
0
-
17
LENGTH
4
12
F
3
-
21
ROADS#
4
5
B
0
-
25
ROADS-ID
4
5
B
0
-
29
FEATURE
4
4
I
-
-
33
SEARCH
10
10
C
-
-
11
-------
ROADS Continued.
ROADS.LKUP
5 Records Selected
COLUMN ITEM NAME
1 FEATURE
5 SYMBOL
LOG 03/22/90
Date
WIDTH OUTPUT
4 4
3 3
Time Elap CPU
min sec
TYPE N.DEC
I
I
ALTERNATE NAME
INDEXED?
I/O Command
opr
8/ 2/88 12:12 2 102
3/ 6/90 11:37 0 1
932 IMPORT COVER CULT-4.E00 ROADS
75 EXTERNALALL [.PI]
12
-------
Nam* of Covaraga: SECTION
Location: DUBO:[DENVER.PI]
Summary: Public Land Survey section data. Attributes are the section number.
Covaraga Typa: Cultural
Fsatuc* Typa: Polygon
Manuaaript Produaar: Petroleum Institute
Manuaaript: Unknown
Manuaaript Data: Unknown
Manuaaript RMS arror: Unknown
Input Soala: 1:24000
Data Produaad: 8/2/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE SECTION
ARCS
Arcs = 8345
Segments = 0742
28 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 3774
Polygon Topology is present.
19 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
3785
TOLERANCES
Tics =
Annotations =
Links =
STATUS
16
0
0
Fuzzy =
Dangle =
11.099 V
0.000 V
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
456932.375
543067.625
Ymin -
Ymax =
358302.500
469289.094
ITEMS 03/23/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF SECTION.PAT
DF SECTION.AAT
DF SECTION.BND
DF SECTION.TIC
ARC026DAT
ARC043DAT
ARC04 4DAT
ARC051DAT
0
8345
1
0
19
28
16
12
XX
XX
XX
SECTION.PAT
3774 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
SECTION#
4
5
B
0
-
13
SECTION-ID
4
5
B
0
-
17
SECTION
3
3
I
-
-
13
-------
SECTION Continued...
SECTION.AAT
8345 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
FNODE#
4
5
B
0
-
5
TNODE#
4
5
B
0
-
9
LPOLY#
4
5
B
0
-
13
RPOLY#
4
5
B
0
-
17
LENGTH
4
12
F
3
-
21
SECTION#
4
5
B
0
-
25
SECTION-ID
4
5
B
0
-
LOG 03/23/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
8/ 2/88 12: 3 9
8/ 2/88 15: 1 1
3/23/90 10: 5 0
3/23/90 10: 7 1
3/23/90 10: 8 0
3/23/90 13:49 23
414 1655 IMPORT COVER SEC.E00 SECTION
9 641 COPY [DENVER.TRS]SECTION
2 100 EXTERNAL SECTION
14 1067 COPY [DENVER.RESTORE]SECTION SECTION
2 83 EXTERNAL SECTION
531 26821 export cover SECTION dubl:[pearl.denver]SECTION.eOO
14
-------
Man* of Covaraga: TOWNSHIP
Location: DUBO:[DENVER.PI]
Summary: Township coverage from T2S R72W tc T5N R64W.
Coverage Type: Cultural
Feature Type: Polygon
Manuscript Producer: Petroleum Institute
Manuscript: Unknown
Manuscript Data: Unknown
Manuscript RMS error: Unknown
Input Saala: 1:24,000
Data Produced: 8/2/88
DESCRIPTION OF SINGLE PRECISION COVERAGE TOWNSHIP
ARCS
Arcs = 353
Segments = 1592
28 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 127
Polygon Topology is present.
31 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
120
TOLERANCES
Tics
Annotations —
Links —
STATUS
16
0
0
Fuzzy =
Dangle =
10.000 V
10.000 V
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
456932.375
543067.625
Ymin
Ymax
358302.500
469289.094
ITEMS
TYPE
03/23/90
NAME
INTERNAL NAME
NO. RECS LENGTH
DF
TOWNSHIP.AAT
ARC021DAT
353 28
DF
TOWNSHIP.PAT
ARC023DAT
127 31
DF
TOWNSHIP.BND
ARC041DAT
1 16
DF
TOWNSHIP.TIC
ARC042DAT
0 12
TOWNSHIP.PAT
127 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT
TYPE N.DEC
ALTERNATE NAME
1
AREA
4
12
F 3
5
PERIMETER
4
12
F 3
9
TOWNSHIP#
4
5
B 0
13
TOWNSHIP-ID
4
5
B 0
17
TNAME
15
15
C
XX
XX
XX
XX
INDEXED?
15
-------
TOWNSHIP Continued.
TOWNSHIP.AAT
353 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT TYPE
N.DEC ALTERNATE
NAME INDEXED?
1 FNODE#
4
5
B
0
-
5 TNODE#
4
5
B
0
-
9 LPOLY#
4
5
B
0
-
13 RPOLY#
4
5
B
0
-
17 LENGTH
4
12
F
3
-
21 TOWNSHIP#
4
5
B
0
-
25 TOWNSHIP-
ID
4
5
B
0
-
LOG 03/23/90
Date Time
Elap
CPU
I/O
Command
min
sec
opr
8/ 2/88 12: 9
1
27
624
IMPORT COVER
TWN.E00 TOWNSHIP
8/ 2/88 13:55
1
8
598
COPY [DENVER.
.TRS]TOWNSHIP
3/23/90 10: 5
0
2
101
EXTERNAL
TOWNSHIP
3/23/90 10: 8
0
10
605
COPY [DENVER.
.RESTORE]TOWNSHIP
TOWNSHIP
3/23/90 10: 8
0
2
95
EXTERNAL
TOWNSHIP
3/23/90 13:2G
1
36
1995
export
cover TOWNSHIP dubl:
[pearl.denver]TOWNSHIP
16
-------
ELEVATION
Digital Elevation Models representing the Denver's topography was
developed by EMSL-LV from 1:24000 USGS topographic quadrangles. A point
coverage was created consisting of 13259 spot elevations. Elevation
sampling was based on the homogenity of the topography. A greater number
of elevation samples were collected in areas of higher relief. TIN,
ARC/INFO's surface modeling system was used to generate surfaces,
contours and views.
Mam* of Covaraga: ELEV-DBC
Looation: DISKSUSER3:[DENVER.ELEV]
Summary: A collection of points representing elevation. Used as input to TIN for surface
generation.
Coverage Typ«: Elevation
Feature Type: Point
Hanucoript Producer: USGS
Manusaript: 7.5 Minute Topographic Maps
Manuaori.pt Data: N/A
Manuaoript RMS arror: < .005
Input. Saale: 1:24,000
Digitized by: Jonathan Pickus, Lockheed Engineering and Science Co.
Data Produced: 8/25/88
DESCRIPTION Or SINGLE PRECISION COVERAGE ELEV-DBC
ARCS
POLYGONS
Arcs — 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 13259
22 bytes of Attribute Data/Point
TOLERANCES
Tics =
Annotations =
Links =
STATUS
39
0
0
Fuzzy =
Dangle =
6.952 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
467814 .344
532138.125
Ymin =
Ymax =
385837.594
455356.781
ITEMS 03/22/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF
ELEV-DBC.PAT
ARC184DAT
13259
22
XX
DF
ELEV-DBC.BND
ARC 18 5D AT
1
16
XX
DF
ELEV-DBC.TIC
ARC18 6DAT
39
12
XX
17
-------
ELEV-DBC Continued...
ELEV-DBC.PAT
13259 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
1 AREA 4 12 F 3
5 PERIMETER 4 12 F 3
9 ELEV-DBC# 4 5 B 0
13 ELEV-DBC-ID 4 5 B 0
17 ELEV 6 6 1
LOG 03/22/90
Date Time Elap CPU I/O Command
min sec opr
8/25/98 9:56 0 5 237 CREATE ELEV—DBC-UTM
3/ 6/90 9:50 0 5 137 EXTERNALALL [.ELEV]
0
5
0
5
0
5
0
10
3/22/90 13:20 0 5 139 EXTERNALALL
3/22/90 13:26 0 10 257 RENAME ELEV-DBC-UTM ELEV-DBC
INDEXED?
18
-------
Description of C ova rag®: ELEV-POLY
Location: DISK$USER3:[DENVER.ELEV]
Summary: A coverage represent elevation at 500 feet intervals.
Covaraga Typa: Elevation
Faatura Typa: Polygon
Data Producad: 8/29/88
DESCRIPTION OF SINGLE PRECISION COVERAGE ELEV-POLY
ARCS
Arcs = 617
Segments = 19169
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 365
Polygon Topology is present.
27 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points
364
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
6.952 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
467814.344
532138 .125
Ymin =
Ymax =
385837 .594
455356.781
ITEMS 03/22/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF ELEV-POLY.PAT
DF ELEV-POLY.BND
DF ELEV-POLY.TIC
ARCI78DAT
ARC179DAT
ARC180DAT
365
1
4
27 XX
16 XX
12 XX
ELEV-POLY.PAT
365 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE N.
. DEC ALTERNATE NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
ELEV-POLY#
4
5
B
0
-
13
ELEV-POLY-ID
4
5
B
0
-
17
RANGE-CODE
4
5
B
0
-
21
ELEV
7
7
I
-
-
LOG 03/22/90
Date Time Elap
CPU
I/O
Command
min
sec
opr
8/29/88 9:12
7
128
6667 LATTICEPOLY ELEV-UTM-LAT ELEV-POLY
ELEV-RANGE.LKUP
9/ 6/88 16:39 0
10
878
COPY DUA2:[KANSAS.DENVER.ELEV]ELEV-POLY-UTM
3/ 6/90 9:50 0
5
137
EXTERNALALL [.ELEV]
3/22/90 13:20 0
5
139
EXTERNALALL
3/22/90 13:25 0
10
257
RENAME ELEV-POLY-UTM ELEV-POLY
19
-------
Main* of Coverage: ELEV-TIN
Location: DISK$USER3:[DENVER.ELEV]
Suiranary: A TIN (Triangulated Integrated Network) structure used to model a surface.
ELEV-TIN was created from the point coverage ELEV-DBC.
Coverage Type: Elevation
Feature Type: TIN
Date Produced: 8/29/88
TIN DESCRIPTION FOR BLEV-TIN
Tin Topology
Nodes = 13259 Triangles = 264 96
Hull nodes = 20
Min Z
Surface value range
4765.000 Max Z
9795.000
Tin Boundary
Xmin = 467814.344
Xmax = 532138.125
Ymin = 395837.594
Ymax = 455356.781
LOC 03/22/90
Date
8/29/88
3/ 6/90
3/22/90
Time
Elap
CPU
I/O
Command
min
sec
opr
8 :10
3
128
1402
ARCTIN ELEV-DBC-UTM
ELEV-TIN
9:51
0
5
158
EXTERNALALL [.ELEV]
13:21
0
6
179
EXTERNALALL
13:28
0
4
106
RENAME ELEV-TIN-UTM
ELEV-TIN
20
-------
Nam* of Coverage: ELEV-TIN-HULL
Location: DISK$USER3:[DENVER.ELEV]
Summary: A coverage representing the boundary extent of TIN ELEV-TIN.
used to produce plots for overlaying (draping) over surface views.
Covartg* Typ«: Elevation
Faatura Typa: Polygon
Data Produaad: 3/22/90
This coverage is
DESCRIPTION 07 SINGLE PRECISION COVERAGE ELEV-TIN-HULL
ARCS
POLYGONS
Arcs = 20
Segments = 20
0 bytes of Arc Attribute Data
Polygons = 2
Polygon Topology is present.
16 bytes of Polygon Attribute Data
POINTS
Label Points =
TOLERANCES
SECONDARY FEATURES
Tics
Annotations
Links
STATUS
Fuzzy
Dangle
6.952 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin
COVERAGE BOUNDARY
467814 .344 Ymin =
385837.594
Xmax = 532138.125
Ymax =
455356.
781
ITEMS 03/22/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH
EXTERNL
DF ELEV-TIN-HULL.BND
ARC183DAT
1
16
XX
DF ELEV-TIN-HULL.PAT
ARC188DAT
2
16
XX
DF ELEV-TIN-HULL.TIC
ARC189DAT
4
12
XX
ELEV-TIN-HULL.PAT
2 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT TYPE N.DEC
ALTERNATE NAME
INDEXED?
1 AREA
4
12
F 3
-
5 PERIMETER
4
12
F 3
-
9 ELEV-TIN-HULL#
4
5
B 0
-
13 ELEV-TIN-HULL-ID
4
5
B 0
-
LOG 03/22/90
Date
Time Elap CPU 1/0 Command
min sec opr
3/22/90 13:36
11 747 TINARC ELEV-TIN ELEV-TIN-HULL HULL
21
-------
Nam* of Covaraga: ELEV-31545-V3D
Loaation: DUBO:[DENVER.ELEV]
Summary: A 3D view of Denver's elevation. View from 315 degrees at 45 degree angle.
Generated using TIN's View commands. View coverages are used for display purposes only
and do not contain topology.
Covaraga Typa: Elevation
Faatura Typa: Line
Data Produoad: 9/8/88
DESCRIPTION OF SINGLE PRECISION COVERAGE ELEV-TIN-HULL
COVERAGE BOUNDARY
Xmin = 1.031 Ymin = 1.373
Xmax = 8.178 Ymax = 7.617
22
-------
Mara* o£ Coverage: ELEV-UTM-LAT.DAT
Location: DUBO:[DENVER.ELEV]
Summary: A Lattice file is a system binary file used by TIN for creating polygon
coverages.
Covaraga Typa: Elevation
7aature Type: LATTICE
Data Produced: 9/6/88
LATTICE DESCRIPTION FOR ELBV-UTM-LAT.DAT
Lattice size and origin
Points in X/Y = 500 500 Origin (x,y)= 467814.344 385837.594
Lattice distance between points
Distance in X = 128.648 Distance in Y = 139.038
Surface value range
Min Z = 4765.000 Max Z = 9782.598
Lattice boundary
Xmin = 467814.344 Ymin = 385837.594
Xmax = 532009.500 Ymax = 455217.750
23
-------
ESRI (Final Demonstration Plot and Data Files)
These coverages were developed for the Environmental System Research
Institutes conference in 1989. These data files were transformed to
provide a perspective view of the "Denver Brown Cloud" elevation specific
slices from 50 through 200 meters AGL. All coverages were transformed to
a template tic file. These coordinates are in inches.
Daaaription of Cov«rag«: BOUND-T
Location: DISK$USER3:[DENVER.ESRI]
Summary: The linear transformation of the
Covaraga Typa: ESRI
Faatura Typa: Polygon
Avaraga RMS arror: N/A
Input Soala: 1:24 000
Data Froduaad: 4/4/89
[DENVER.PI]BOUNDARY file.
DESCRIPTION OF SINGLE PRECISION COVERAGE BOOND-T
ARCS
POLYGONS
Arcs = 364
Segments — 970
0 bytes of Arc Attribute Data
Polygons = 28
Polygon Topology is present.
30 bytes of Polygon Attribute Data
POINTS
Label Points =
27
TOLERANCES
SECONDARY FEATURES
Tics
Annotations
Links
STATUS
20
58
0
Fuzzy =
Dangle =
0.000 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
47.620
60.650
Ymin =
Ymax =
10.851
15.770
ITEMS 03/28/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF
BOUND-T.BND
ARC018DAT
1
16
XX
DF
BOUND-T.TIC
ARC019DAT
20
12
XX
DF
BOUND-T.PAT
ARC04 0DAT
28
30
XX
BOUND-T.PAT
28 Records Selected.
COLUMN
1
5
9
13
17
21
ITEM NAME
AREA
PERIMETER
BOUND-T#
BOUND-T-ID
FEATURE
SEARCH
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
4
12
F
3
-
4
12
F
3
-
4
5
B
0
-
4
5
B
0
-
4
4
I
-
-
10
10
C
-
-
2 4
-------
BOUND-T Continued.
LOC 03/28/90
Date Time Elap CPU I/O Command
min sec opr
4/ 4/89 9:56 1 6 702 CREATE BOUND-T TIC_FRAME
4/ 4/89 9:59 1 15 1008 TRANSFORM BOUNDARY BOUND-T
25
-------
Nam* of Cov*rag*: CITY-T
Location: DISK$USER3:[DENVER.ESRI]
Summary: The linear transformation of the coverage [DENVER.PI]CITY.
Corarag* Typ«: ESRI
F*at.ur« Typ*: Polygon
Avarag* RMS error: N/A
Input Seal*: 1:24,000
Dat* Produced: 4/4/89
DESCRIPTION or SINGLE PRECISION COVERAGE CITY-T
ARCS
Arcs = 980
Segments = 3301
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 63
Polygon Topology is present.
30 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
TOLERANCES
63
Tics =
Annotations =
Links =
STATUS
16
27
0
Fuzzy
Dangle
0.001 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
49.716
59.119
Ymin =
Ymax =
10.851
15.675
ITEMS 03/28/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF CITY-T.PAT
DF CITY-T.BND
DF CITY-T.TIC
ARC002DAT
ARC003DAT
ARC004DAT
63
1
16
30 XX
16 XX
12 XX
CITY-T.PAT
63 Records Selected.
COLUMN ITEM NAME
1
5
9
13
17
21
AREA
PERIMETER
CITY-T#
CITY—T-ID
FEATURE
SEARCH
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
10
12
12
5
5
4
10
F
F
B
B
I
C
LOG 03/26/90
Date Time Elap CPU I/O Command
min sec opr
3/30/89
13:39
0
4
288
3/30/89
13:42
1
19
764
3/31/89
8: 6
0
7
489
4/ 4/89
9:40
0
3
169
3/28/90
9:17
2
50
2559
26
-------
Description of Coverage: E30-RNG-T
Location: DISKSUSER3:[DENVER.ESRI]
Summary: The linear transformation of the coverage [DENVER.JAN20.DEV-30]E30-RANGE.
Coverage Type: ESRI
Feature Type: Polygon
Average RMS error: N/A
Input Scale: N/A
Date Froduaed: 4/5/89
DESCRIPTION 07 SINGLE PRECISION COVERAGE E30-RNG-T
ARCS
POLYGONS
Arcs = 127
Segments = 8080
0 bytes of Arc Attribute Data
Polygons = 67
Polygon Topology is present.
38 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points =
66
TOLERANCES
Tics =
Annotations =
Links =
STATUS
20
0
0
Fuzzy =
Dangle =
0.000 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
47.664
60.665
Ymin
Ymax
13.775
18.774
ITEMS 03/28/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF
E30-RNG-T.PAT
ARC027DAT 67 38
XX
DF
E30-RNG-T.BND
ARC028DAT 1 16
XX
DF
E30-RNG-T.TIC
ARC030DAT 20 12
XX
E30-RNG-T.PAT
67 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E30-RNG-T#
4
5
B
0
-
13
E30-RNG-T-ID
4
5
B
0
-
17
E30-RANGE#
4
5
B
0
-
21
E30-RANGE-ID
4
5
B
0
-
25
RNGE
3
3
I
-
-
28
SYMBOL
3
3
I
-
-
31
MAPEXBOX#
4
5
B
0
-
35
MAPEXBOX-ID
4
5
B
0
-
LOG 03/28/90
Date Time Elap
CPU
I/O
Command
min
sec
opr
4/ 5/89 9:36 0
4/ 7/89 9:37 0
3/28/90 9:35 5
5
7
52
294
476
2532
CREATE
copy (
EXPORT
E30-RNG-T TIC_FRAME
workl]e30-rng-t
COVER E30-RNG-T DUB1:[PEARL.DENVER]E30-RNG
27
-------
Nana of Covaraga: E100-RNG-T
Location: DISK$USER3:[DENVER.ESRI]
Summary: The linear transformation of the coverage E100-RANGE. Note that E100-RANGE was
developed using the same parameters as [DENVER.JAN20.DEV-30]E30-VTC.
Covaraga Typa: ESRI
Faatura Typa: Polygon
Avarag* RMS «rror: N/A
Input Saala: N/A
Data Produaad: 4/5/89
DESCRIPTION OF SINGLE PRECISION COVERAGE E100-RNG-T
ARCS
POLYGONS
Arcs = 136
Segments = 8539
0 bytes of Arc Attribute Data
POINTS
Label Points =
66
TOLERANCES
Fuzzy =
Dangle =
Polygons = 67
Polygon Topology is present.
38 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics
Annotations
Links
STATUS
20
0
0
0.000 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/28/90
TYPE NAME
47.664
60.665
Ymin =
Ymax =
INTERNAL NAME
17.775
22.774
NO. RECS LENGTH EXTERNL
DF E100-RNG-T.PAT
DF E100-RNG-T.BND
DF E100-RNG-T.TIC
E100-RNG-T.PAT
67 Records Selected.
ARC04 7DAT
ARC04 8DAT
ARC056DAT
67
1
20
38 XX
16 XX
12 XX
COLUMN
ITEM NAME
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E100-RNG-T*
4
5
B
0
-
13
E100-RNG-T-ID
4
5
B
0
-
17
E100-RANGE#
4
5
B
0
-
21
E100-RANGE-ID
4
5
B
0
-
25
RNGE
3
I
-
-
28
MAPEXBOX#
4
5
B
0
-
32
MAPEXBOX-ID
4
5
B
0
-
36
SYMBOL
3
3
I
-
-
LOG 03/28/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
4/ 5/89 9:23 0 6 694 CREATE E100-RNG-T TIC_FRAME
4/ 7/89 9:36 0 9 862 copy [.workl]elOO-rng-t
28
-------
Nain* of Covacag*: E150-RNG-T
Location: DISK$USER3:[DENVER.ESRI]
Summary: The linear transformation of the coverage E150-RANGE. Note that E150-RANGE was
developed using the same parameters as [DENVER.JAN20.DEV-30]E30-VTC.
Covaraga Typa: ESRI
Faatura Typa: Polygon
Avarag* RMS arror: N/A
Input Soala: N/A
Data Produaad: 4/4/8 9
DESCRIPTION OF SINGLE PRECISION COVERAGE K150-RNG-T
ARCS
Arcs = 96
Segments = 7 689
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 59
Polygon Topology is present.
22 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
TOLERANCES
59
Tics =
Annotations =
Links =
STATUS
20
0
0
Fuzzy =
Dangle =
0.001 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
48.603
60.166
Ymin =
Ymax =
22.444
26.275
ITEMS 03/28/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E150-RNG-T.TIC
DF E150-RNG-T.BND
DF E150-RNG-T.PAT
ARC035DAT
ARC03 6DAT
ARC039DAT
20
1
59
12 XX
16 XX
22 XX
E150-RNG-T.PAT
59 Records Selected.
COLUMN
1
5
9
13
17
20
ITEM NAME
AREA
PERIMETER
E150-RNG-T#
E150-RNG-T-ID
RNGE
SYMBOL
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
12
12
5
5
3
3
F
F
B
B
I
I
LOG 03/28/90
Date Time Elap CPU I/O Command
min sec opr
4/ 5/99
9:27
0
4
4/ 7/89
9:37
0
8
3/27/90
16:21
0
2
3/28/90
8:53
0
2
3/28/90
9:23
2
46 :
285 CREATE E150-RNG-T TIC_FRAME
469 copy [.workl]el50-rng-t
88 EXTERNALALL
83 EXTERNALALL
2366 EXPORT COVER E150-RNG-T DUB1:[PEARL.DENVER]E150-RNG-T.E00
29
-------
Description of Coverage: E200-RNG-T
Location: DISK$USER3:[DENVER.ESRI]
Summary: The linear transformation of the coverage E200-RANGE. Note that E200-RANGE was
developed using the same parameters as [DENVER.JAN20.DEV-30]E30-VTC.
Coverage Type: ESRI
Feature Type: Polygon
Average RMS error: N/A
Input Scale: N/A
Data Produced: 4/4/89
DESCRIPTION OF SINGLE PRECISION COVERAGE E200-RNG-T
ARCS
Arcs = 100
Segments = 5780
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 47
Polygon Topology is present.
22 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points = 4 6 Tics = 20
Annotations = 0
Links = 0
TOLERANCES STATUS
Fuzzy =
Dangle =
0.002 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/28/90
TYPE NAME
48 .783
60.166
Ymin =
Ymax =
INTERNAL NAME
26.459
30.275
NO. RECS LENGTH EXTERNL
DF E200-RNG-T.BND
DF E200-RNG-T.TIC
DF E200-RNG-T.PAT
ARC073DAT
ARC074DAT
ARC07 8DAT
1
20
47
16
12
22
XX
XX
XX
E200-RNG-T.PAT
47 Records Selected.
COLUMN
1
5
9
13
17
20
ITEM NAME
AREA
PERIMETER
E200-RNG-T#
E200-RNG-T-ID
RNGE
SYMBOL
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
12
12
5
5
3
3
F
F
B
B
I
I
INDEXED?
LOG 03/28/90
Date Time Elap CPU I/O Command
min sec opr
4/
4/89
13:34
0
5
2 94
4/
4/89
13:39
1
12
600
4/
5/89
9: 7
3
120
2193
4/
5/89
10: 40
4
107
2320
4/
5/89
10:56
4
62
2162
4/
5/89
15:35
0
5
206
30
-------
Nam* of Covaraga: E30-VTC-T
Location: DISKS0SER3:[DENVER.ESRI]
Summary: The linear transformation of the coverage [DENVER.JAN20.DEV-30]E30-VTC.
Coveraga Typ«: ESRI
Faatura Typa: Polygon
Avarago RMS error: N/A
Input Saala: N/A
Data Produaed: 4/5/8 9
DESCRIPTION OF SINGLE PRECISION COVERAGE E30-VTC-T
ARCS
POLYGONS
Arcs = 286
Segments = 12838
35 bytes of Arc Attribute Data
POINTS
Label Points = 0
TOLERANCES
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics =
Annotations =
Links =
STATUS
20
0
0
Fuzzy
Dangle
0.002 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
50.724
59.341
Ymin
Ymax
14 .428
18 .284
ITEMS 03/28/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E30-VTC-T.AAT
DF E30-VTC-T.BND
DF E30-VTC-T.TIC
ARC023DAT
ARC024DAT
ARC025DAT
286
1
20
35 XX
16 XX
12 XX
E30-VTC-T.AAT
286 Records Selected.
COLUMN
ITEM NAME
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
1
FN0DE#
4 5
B
0
-
5
TNODE#
4 5
B
0
-
9
LPOLY#
4 5
B
0
-
13
RPOLY#
4 5
B
0
-
17
LENGTH
4 12
F
3
-
21
E30-VTC-T#
. 4 5
B
0
-
25
E30-VTC-T-ID
4 5
B
0
-
29
LIDAR
4 12
F
3
-
33
RNGE
3 3
I
-
-
LOG 03/28/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
4/ 5/89
9:34
0
6
708
CREATE E30-VTC-T TIC FRAME
4/ 7/89
9:38
0
7
391
copy [.workl]e30-vtc-t
3/27/90
16:22
0
2
96
EXTERNALALL
3/28/90
8:53
0
2
83
EXTERNALALL
3/28/90
9:38
3
74
3694
EXPORT COVER E30-VTC-T DUB1
31
-------
Description of Coverage: E100-VTC-T
Location: DISK$USER3:[DENVER.ESRI]
Summary: The linear transformation of the coverage E100-VTC. Note that E100-VTC was
developed using the same parameters as [DENVER.JAN20.DEV-30]E30-VTC.
Coverage Type: ESRI
Feature Type: Polygon
Average RMS error: N/A
Input Scale: N/A
Date Produaed: 4/5/8 9
DESCRIPTION OF SINGLE PRECISION COVERAGE E100-VTC-T
ARCS
POLYGONS
Arcs = 308
Segments = 13086
32 bytes of Arc Attribute Data
POINTS
Label Points = 0
TOLERANCES
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics
Annotations
Links
STATUS
20
0
0
Fuzzy
Dangle
0.002 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
50.675
59.530
Ymin
Ymax
18.435
22.268
ITEMS 03/28/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E100-VTC-T.AAT
DF E100-VTC-T.BND
DF E100-VTC-T.TIC
E100-VTC-T.AAT
308 Records Selected.
COLUMN ITEM NAME
ARC041DAT
ARC045DAT
ARC046DAT
308
1
20
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
32 XX
16 XX
12 XX
INDEXED?
1
FNODE#
4 5
B
0
-
5
TNODE#
4 5
B
0
-
9
LPOLY#
4 5
B
0
-
13
RPOLY#
4 5
B
0
-
17
LENGTH
4 12
F
3
-
21
E100-VTC-T*
4 5
B
0
-
25
E100-VTC-T-ID
4 5
B
0
-
29
LIDAR
4 12
F
3
-
LOG 03/28/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
4/ 5/89
9:24
0
4
4/ 7/89
9:36
0
6
3/27/90
16:21
0
2
3/28/90
0:53
0
2
3/28/90
9:21
3
75
287 CREATE E100-VTC-T TIC_FRAME
384 copy [.workl]elOO-vtc-t
94 EXTERNALALL
88 EXTERNALALL
3793 EXPORT COVER E100-VTC-T DUB1:[PEARL.DENVER]E100-VTC-T.E00
32
-------
Deaoription of Coverage: E150-VTC-T
Location: DISK$USER3:[DENVER.ESRI]
Summary: The linear transformation of the coverage E150-VTC. Note that E150-VTC was
developed using the same parameters as [DENVER.JAN20.DEV-30]E30-VTC.
Coverage Typ«: ESRI
Feature Type: Polygon
Average RMS arror: N/A
Input 9oala: N/A
Data Produced: 4/5/89
DESCRIPTION OF SINGLE PRECISION COVERAGE E150-VTC-T
ARCS
POLYGONS
Arcs = 244
Segments = 10164
32 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
Label Points =
TOLERANCES
SECONDARY FEATURES
Tics
Annotations =
Links =
STATUS
20
0
0
Fuzzy =
Dangle =
0.002 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
50.646
59.460
Ymin
Ymax
22.453
26.269
ITEMS 03/20/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF
E150-VTC-T.AAT
ARC031DAT
244
32
XX
DF
E150-VTC-T.BND
ARC033DAT
1
16
XX
DF
E150-VTC-T.TIC
ARC034DAT
20
12
XX
E150-VTC-T.AAT
244 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
FNODE#
4
5
B
0
-
5
TNODE#
4
5
B
0
-
9
LPOLY#
4
5
B
0
-
13
RPOLY#
4
.5
B
0
-
17
LENGTH
4
12
F
3
-
21
E150-VTC-T#
4
5
B
0
-
25
E150-VTC-T-ID
4
5
B
0
-
29
LIDAR
4
12
F
3
-
LOG 03/28/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
4/ 5/89
9:29
0
4
4/ 7/89
9:37
0
7
3/27/90
16:21
0
2
3/28/90
8:53
0
2
3/28/90
9:25
2
60
298 CREATE E150-VTC-T TIC_FRAME
388 copy [.workl]el50-vtc-t
85 EXTERNALALL
83 EXTERNALALL
3005 EXPORT COVER E150-VTC-T DUB1:[PEARL.DENVER]E150-VTC-T.E00
33
-------
Daaaription of Covaraga: E200-VTC-T
Location: DISK$USER3:[DENVER.ESRI]
Summary: The linear transformation of the coverage E200-VTC. Note that E200-VTC was
developed using the same parameters as [DENVER.JAN20.DEV-30]E30-VTC.
Coverage Type: ESRI
Feature Type: Polygon
Average RMS error: N/A
Input Saala: N/A
Data Produaed: 4/5/89
DESCRIPTION OF SIHGLS PRECISION COVERAGE B200-VTC-T
ARCS
POLYGONS
Arcs = 156
Segments = 6640
32 bytes of Arc Attribute Data
POINTS
Label Points = 0
TOLERANCES
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics
Annotations =
Links =
STATUS
20
0
0
Fuzzy =
Dangle =
0.002 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax —
ITEMS 03/28/90
TYPE NAME
48 .784
60 .286
Ymin —
Ymax =
INTERNAL NAME
26.460
30.259
NO. RECS LENGTH EXTERNL
DF E200-VTC-T.TIC
DF E200-VTC-T.BND
DF E200-VTC-T.AAT
ARC000DAT
ARC052DAT
ARC053DAT
20
1
156
12 XX
16 XX
32 XX
E200-VTC-T.AAT
156 Records Selected.
COLUMN
ITEM NAME
WIDTH OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
FNODE#
4 5
B
0
-
5
TNODE#
4 5
B
0
-
9
LPOLY#
4 5
B
0
-
13
RPOLY#
4 5
B
0
-
17
LENGTH
4 12
F
3
-
21
E200-VTC-T#
4 5
B
0
-
25
E200-VTC-T-ID
4 5
B
0
-
29
LIDAR
4 12
F
3
-
LOG 03/28/90
Date Time Elap CPU I/O
min sec opr
Command
4/ 4/89
13:35
0
5
4/ 4/89
13:38
1
8
3/27/90
16:21
0
2
3/28/90
8 : 53
0
2
3/28/90
9:30
5
44
295 CREATE E200-VTC-T TIC_FRAME
356 TRANSFORM E200-VTC E200-VTC-T
88 EXTERNALALL
84 EXTERNALALL
2078 EXPORT COVER E200-VTC-T DUB1:[PEARL.DENVER]E200-VTC-T.E00
34
-------
Daaoription of Covaraga: LAYERS
Location: DISK$USER3:[DENVER.ESRI]
Summary: Layers is the five vertical elements which define the plot perspective.
Covaraga Typa: ESRI
Faatura Typa: NET
Avaraga RMS arror: N/A
Input Saala: N/A
Data Froduoad: 4/7/89
DESCRIPTION Or SINGLE PRECISION COVERAGE LAYERS
ARCS
POLYGONS
Arcs = 20
Segments = 35
28 bytes of Arc Attribute Data
POINTS
Label Points = 2
TOLERANCES
Polygons = 8
Polygon Topology is present.
19 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics =
Annotations =
Links =
STATUS
20
0
0
Fuzzy =
Dangle =
0.001 V
0.001 V
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/28/90
TYPE NAME
47.659
60.665
Ymin —
Ymax =
INTERNAL NAME
10.483
30.774
NO. RECS LENGTH EXTERNL
DF
LAYERS.AAT
ARC072DAT
13
28
XX
DF
LAYERS.TIC
ARC075DAT
20
12
XX
DF
LAYERS.BND
ARC07 6DAT
1
16
XX
DF
LAYERS.PAT
ARC093DAT
8
19
XX
LAYERS
¦ PAT
8 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC
ALTERNATE NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
LAYERS#
4
5
B
0
-
13
LAYERS-ID
4
5
B
0
-
17
SYMBOL
3
3
I
-
-
LAYERS
.AAT
20 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC
ALTERNATE NAME
INDEXED?
1
FNODE#
4
5
B
0
-
5
TNODE#
4
5
B
0
-
9
LPOLY#
4
5
B
0
-
13
RPOLY#
4
5
B
0
-
17
LENGTH
4
12
F
3
-
21
LAYERS#
4
5
B
0
-
25
LAYERS-ID
4
5
B
0
-
35
-------
XJIYKRS Continued. . .
LOG 03/28/90
Date Time Elap CPU I/O Command
min
sec
opr
4/ 5/89
10:54
1
12
679
BUILD LAYERS
4/ 7/89
10:53
3
39
2306
CLEAN LAYERS
3/27/90
16:22
0
4
166
EXTERNALALL
3/28/90
8:53
0
4
124
EXTERNALALL
3/28/90
9:39
0
10
445
EXPORT COVER
LINE
# .001 .001
LAYERS DUB1:[PEARL.DENVER]LAYERS.E00
36
-------
Description of Covaraga: LEVEL1-T, LEVEL2-T, LEVEL3-T, LEVEL4-T, LEVEL5-T
Location: DISKSUSER3:[DENVER.ESRI]
Summary: Transformed coverages used to display each vertical level
Covaraga Typa: ESRI
Taatura Typa: NET
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produoad: 4/5/89
DESCRIPTION or SINGLE PRECISION COVERAGE LEVEL1,2, 3, 4 , 5-T
ARCS
POLYGONS
Arcs = 1
Segments = 4
2 8 bytes of Arc Attribute Data
Polygons = 2
Polygon Topology is present.
16 bytes of Polygon Attribute Data
POINTS
Label Points =
TOLERANCES
SECONDARY FEATURES
Tics =
Annotations =
Links =
STATUS
20
0
0
Fuzzy
Dangle
0.000 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
37
-------
Description of Covaraga: ROADS-T
Location: DISK$USER3:{DENVER.ESRI]
Summary: The linear transformation of the coverage [DENVER.PI]ROADS.
Covaraga Typa: ESRI
Faatura Typa: Polygon
Avaraga RMS arror: N/A
Input Saala: N/A
Data Producad: 3/30/89
DESCRIPTION OF SINGLE PRECISION COVERAGE ROADS-T
ARCS
POLYGONS
Arcs = 1489
Segments = 5898
4 2 bytes of Arc Attribute Data
POINTS
Label Points = 0
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics =
Annotations =
Links =
16
0
0
TOLERANCES
STATUS
Fuzzy =
Dangle =
0.001 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
47.619
60.685
Ymin =
Ymax =
10.851
15.769
ITEMS 03/28/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF
ROADS-T.TIC
ARC008DAT
16
12
XX
DF
ROADS-T.BND
ARC0 0 9DAT
1
16
XX
DF
ROADS-T.AAT
ARC010DAT
1489
42
XX
ROADS
-T.AAT
1489 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC
ALTERNATE NAME
INDEXED?
1
FNODE#
4
5
B
0
-
5
TNODE#
4
5
B
0
-
9
LPOLY*
4
5
B
0
-
13
RPOLY#
4
.5
B
0
-
17
LENGTH
4
12
F
3
-
21
ROADS-T#
4
5
B
0
-
25
ROADS-T-ID
4
5
B
0
-
29
FEATURE
4
4
I
-
-
33
SEARCH
10
10
C
-
-
LOG 03/28/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
3/30/89 15:54 0 6
3/30/89 15:56 1 24
3/31/89 8: 7 0 6
720 CREATE ROADS-TRANS [DENVER.DEV]TIC_FRAME
873 TRANSFORM ROADS ROADS-TRANS
401 copy [denver.graph-covers]roads-trans
38
-------
Description of Covaraga: TRANS-T
Location: DISKSUSER3:[DENVER.ESRI]
Summary: The linear transformation of the coverage [DENVER.JAN20.FLT]FLIGHT_DBC-U..
Coverage Type: ESRI
Feature Typa: Polygon
Average RMS arror: N/A
Data Produaad: 4/5/8 9
DESCRIPTION Of SINGLE PRECISION COVERAGE TRANS-T
ARCS
POLYGONS
Arcs = 11
Segments = 3904
4 9 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 205
20 bytes of Attribute Data/Point
Tics =
Annotations =
Links =
20
33
0
TOLERANCES
STATUS
Fuzzy =
Dangle =
0.002 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
48 .466
60.450
Ymin =
Ymax =
11.519
15.283
ITEMS 03/28/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF TRANS-T.AAT
DF TRANS-T.PAT
DF TRANS-T.BND
DF TRANS-T.TIC
ARC051DAT
ARC069DAT
ARC070DAT
ARC071DAT
11
205
1
20
49 XX
20 XX
16 XX
12 XX
TRANS-T.AAT
11 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
FN0DE#
4
5
B
0
-
5
TN0DE#
4
5
B
0
-
9
LPOLY#
4
5
B
0
-
13
RP0LY#
4
5
B
0
-
17
LENGTH
4
12
F
3
-
21
TRANS-T#
4
5
B
0
-
25
TRANS-T-ID
4
5
B
0
-
29
TIN FLAG
3
3
I
-
-
32
FLIGHT
3
3
I
-
-
35
TAPE
5
5
C
-
-
40
START.TIME
5
5
N
2
-
45
END.TIME
5
5
N
2
-
LOG 03/28/90
Date Time Elap CPU I/O Command
min sec opr
4/ 5/89 13: 1 0 7 718 CREATE TRANS-T TIC_FRAME
4/ 5/89 13: 2 0 12 942 TRANSFORM [DENVER.JAN20.FLT]FLIGHT DBC-U TRANS-T
39
-------
Description of Coverage: TIC_FRAME
Location: DISK$USER3:[DENVER.ESRI]
Summary: TIC_FRAME contains annotation and vertical arcs providing plot perspective.
Coverage Type: ESRI
Feature Type: LINE
Averege RMS error: N/A
Input Scale: N/A
Date Produced: 5/17/8 8
DESCRIPTION 07 SINGLE PRECISION COVERAGE TIC FRAME
ARCS
Arcs = 70
Segments = 70
31 bytes of Arc Attribute Data
POINTS
Label Points = 16
POLYGONS
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics =
Annotations =
Links =
20
4
39
TOLERANCES
Fuzzy =
Dangle =
0.002 N
0.000 N
COVERAGE BOUNDARY
STATUS
Coverage has 147 edit maslc(s), use
BUILD or CLEAN to restore topology
Xmin =
Xmax =
ITEMS 03/28/90
TYPE NAME
47.656
61.019
Ymin =
Ymax =
INTERNAL NAME
10.845
30 .790
NO. RECS LENGTH EXTERNL
DF TIC_FRAME.BND
DF TIC_FRAME.TIC
DF TIC FRAME.AAT
ARC012DAT
ARC013DAT
ARC038DAT
1
20
70
16 XX
12 XX
31 XX
TIC_FRAME.AAT
70 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
FN0DE#
4 5
B
0
-
5
TNODE#
4 5
B
0
-
9
LPOLY#
4 5
B
0
-
13
RPOLY#
4 5
B
0
-
17
LENGTH
4 12
F
3
-
21
TIC FRAME#
4 5
B
0
-
25
TIC FRAME-ID
4 5
B
0
-
29
SYMBOL
3 3
I
-
-
LOG 03/28/90
Date Time Elap CPU I/O Command
min sec opr
5/17/88 13:54 1 11 665 BUILD TICJFRAME LINE
5/23/88 9:48 0 1 67 EXTERNALALL
3/31/89 8:10 1 7 404 copy [denver.d«v]tic_frame
40
-------
LIDAR
Surface analysis was performed for Lidar data collection missions
conducted on January 13th, 1988 and January 20th, 1988. LIDAR was
integrated into ARC/INFO based on elevations above ground level (AGL).
The relative nature of LIDAR precludes comparisons between days. All
LIDAR data ranges from 0 through 255.
January 13 and January 20 analysis are organized in system directories
JAN13 and JAN20, respectively. Sub-directories store analysis based on
AGL. Directory DEV-30 organized various coverages which represented
analysis for 30 meters AGL. A standard naming convention was adopted for
each of these Lidar coverages. For example, the directory DEV-30 will
contain the following ARC/INFO coverages:
E30_APP: Point file representing raw Lidar values for various
transects.
E30-RANGE: Lidar returns represented as a set of discrite range
values.
E30-TIN: TIN based on a proximal sample of Lidar values
E30-VIP: Points most important in representing the surface.
E30-VT: TIN created from E30-VIP.
E30-VTC: Lidar Contours from E30-VT.
E30-VTLP: Polygon coverage created from LATTICE file E30-VTL.LAT.
INFO: Contains INFO database files externalled to each ARC/INFO
coverage.
Within each Lidar Surface Directory there exists a file recording all
specification used to create each of these ARC/INFO coverages. This file
is named "ARCTIN_999999.999999" (Where "9" represents the data and time
stamp when this file was created).
41
-------
JAN13 (January 13, 1988 Lidar Collection Mission)
Listings for January 13, 1988 are organized by directories DEV-30, DEV-
50, DEV-60, DEV-80 and FLT.
I. DEV-30 (Lidar surfaces generated based on 30 meters AGL).
Nam* of Coveraga: E30_APP
Location: DISK$USER3:[DENVER.JAN13.DEV-30]
Summary: E30_APP represents Lidar return values collected 1/13/88 at 30 meters AGL from
08:00 to 09:44. Mission data was organized by transect and was obtained from data file
(denver.exe]DB3.GND. Data was generated from locational values collected at time of
mission.
Coverage Type: Lidar
Feature Type: Point
Input Scale: N/A
Digitized by: N/A
Data Produced: 11/1/88
DESCRIPTION OF SINGLE PRECISION COVERAGE E30 APP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 4008
37 bytes of Attribute Data/Point
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy
Dangle
6.295 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
463284.469
531264.125
Ymin =
Ymax =
385006.719
447956.094
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF
E30 APP.TIC
ARC001DAT
4
12
XX
DF
E30 APP.BND
ARC002DAT
1
16
XX
DF
E30_APP.PAT
ARC004DAT
4008
37
XX
E30_APP.PAT
4008 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT
TYPE N.DEC
ALTERNATE NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E30 APP#
4
5
B
0
-
13
E30 APP-ID
4
5
B
0
-
17
LIDAR
3
3
I
-
-
20
FLIGHT
3
3
I
-
-
23
TAPE
5
5
C
-
-
28
START.TIME
5
5
N
2
-
33
END.TIME
5
5
N
2
-
42
-------
E30_AFP Continued...
LOG 03/26/90
Date Time Eiap CPU I/O Command
min sec opr
11/ 1/88
8
14
2
59
1214
APPEND E30 APP-21 POINT FEATURES
11/ 1/88
8
16
3
104
859
BUILD E30_APP-21 point
11/ 1/88
8
31
2
93
835
build e30 app-21 point
11/ 1/88
8
32
0
8
791
copy [denver.janl3.dev-30-old]e30
11/ 1/88
8
32
0
2
158
rename e30 app-21 e30 app
3/26/90
10
7
0
1
74
EXTERNALALL
3/26/90
10
16
0
1
77
EXTERNALALL
43
-------
Mam* of Coverage: E30-TIN
Location: DISK$USER3:[DENVER.JAN13.DEV-30]
Summary: A TIN created from E30_APP using a proximal sampling distance of 1000 meters.
E30-TIN is the first surface model in a series of surface generations.
Covaraga Typa: Lidar
Taatura Typa: TIN
Avaraga RMS arror: N/A
Input Soala: N/A
Data Produaad: 11/1/88
TIN DESCRIPTION FOR K30-TIN
Tin Topology
Nodes
Hull nodes
404
44
Triangles = 762
Surface value range
Min Z
0 .000
Max Z
113.000
Tin Boundary
Xmin = 463284.469
Xmax = 531264.125
Ymin = 385006.719
Ymax = 447954 .906
LOG 03/26/90
Date Time Elap CPU I/O Command
min sec opr
11/ 1/88 16:27 1 28 739 ARCTIN E30_APP E30-TIN POINT LIDAR # 1000
3/26/90 10: 6 0 2 118 EXTERNALALL
3/26/90 10:15 0 3 135 EXTERNALALL
44
-------
Nama of Lattica: E30-LAT.LAT
Location: DISK$USER3:[DENVER.JAN13.DEV-30]
Summary: A LATTICE created from TIN E30-TIN. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E30-LAT.LAT was used to create the VIP coverage E30-VIP.
Covaraga Typa: Lidar
Faatura Typa: LATTICE
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produaad: 11/2/88
Lattice description for E30-LAT.LAT
Lattice size _and origin
Points in X/Y = 250 250 Origin (x,y)= 463284.469 385006.719
Lattice distance between points
Distance in X = 273.011 Distance in Y = 252.804
Surface value range
Min Z = 0.000 Max Z = 113.000
Lattice boundary
Xmin = 463284.469 Ymin =* 385006.719
Xrnax = 531264 .125 Ymax = 447954 .906
45
-------
Ham* of Covaraga: E30-VIP
Location: DISK$USER3:[DENVER.JAN13.DEV-30]
Summary: E30-VIP is a point coverage which represents, based on a 15% sample of E30-
LAT.LAT, the Lidar "Z" values which were most important in describing the surface. Two
attributes SPOT, representing Lidar "Z" values, and SFCODE are contained in the INFO file
E30-VIP.PAT. SFCODE was a SPOT feature code, coded as one of the following:
2 for a surface maximum or convexity.
-2 for a surface minimum or concavity
1 for an inflection or transition close to a maximum
-1 an inflection or transition feature close to a minimum
0 for a point that is both a local surface maximum and a local surface surface
minimum.
Covarag* Typa: Lidar
Feature Typa: Point
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produoad: 11/1/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE E30-VIP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 9585
24 bytes of Attribute Data/Point
TOLERANCES
Tics =
Annotations —
Links —
STATUS
Fuzzy =
Dangle =
6.244 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin —
Xmax =
464376.500
529899.063
Ymin
Ymax
385259.500
447699.281
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF
DF
E30-VIP.BND
E30-VIP.TIC
ARC015DAT
ARC016DAT
16
12
XX
XX
DF
E30-VIP.PAT
ARC017DAT
9585
24 XX
E30-VIP.PAT
9585 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC
ALTERNATE NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E30-VIP#
4
5
B
0
-
13
E30-VIP-ID
4
5
B
0
-
17
SPOT
4
12
F
3
-
21
SFCODE
4
5
B
0
-
LOG 03/26/90
Date Time Elap CPU
min sec
I/O Command
opr
11/ 1/88 16:11
59
777
VIP E30-LAT E30-VIP 15
46
-------
Nam* of Covaraga: E30-VT
Location: DISK$USER3:[DENVER.JAN13.DEV-30]
Summary: A TIN created from coverage E30-VIP using a proximal sampling distance of 1500
meters.
Covaraga Typa: Lidar
Faatura Typa: TIN
Avaraga RMS error: N/A
Input Seal*: N/A
Data Produoad: 11/1/88
TIN DESCRIPTION FOR E30-VT
Tin Topology
Nodes
Hull nodes
749
41
Triangles = 1455
Surface value range
Min Z
0 .000
Max Z
90.569
Tin Boundary
Xrnin = 464649.531
Xinax = 528807.063
Ymin = 385259.500
Ymax = 447699.281
LOG 03/26/90
Date Time Elap CPU I/O Command
min sec opr
11/ 1/88 16:40 1 44 775 ARCTIN E30-VIP E30-VT POINT SPOT ~ 1500
3/26/90 10: 6 0 2 118 EXTERNALALL
3/26/90 10:16 0 3 134 EXTERNALALL
47
-------
Nan* of Covaraga: E30-VT-HULL
Location: DISK$USER3:[DENVER.JAN13.DEV-30]
Summary: A coverage representing the boundary extent of TIN E30-VT. This coverage was used
to set mapextents for plotting and creating views.
Covaraga Typa: Lidar
Faatura Typa: Polygon
Avaraga RMS arror: N/A
Input Soala: N/A
Data Produaad: 11/1/88
DESCRIPTION Of SINGLE PRECISION COVERACK E30-VT-HULL
ARCS
Arcs = 41
Segments = 41
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 2
Polygon Topology is present.
16 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy
Dangle
Xmin =
Xmax =
ITEMS 03/26/90
TYPE NAME
6.244 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
464649.531
528807.063
Ymin =
Ymax =
INTERNAL NAME
385259.500
447699.281
NO. RECS LENGTH EXTERNL
DF E30-VT-HULL.BND
ARC022DAT
1
16
XX
DF E30-VT-HULL.TIC
ARC023DAT
4
12
XX
DF E30-VT-HULL.PAT
ARC027DAT
3
16
XX
E30-VT-HULL.PAT
3 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT
TYPE N.DEC
ALTERNATE NAME
INDEXED?
1 AREA
4
12
F 3
-
5 PERIMETER
4
12
F 3
-
9 E30-VT-HULL#
4
5
B 0
-
13 E30-VT-HULL-ID
4
5
B 0
-
LOG 03/26/90
Date Time Elap
CPU I/O
Command
min
sec opr
11/ 2/88 11:38 1 10
3/26/90 10: 6 0 1
3/26/90 10:16 0 1
907 tinarc e30-vt e30-vt-hull hull
81 EXTERNALALL
81 EXTERNALALL
48
-------
Nama of Covtrig*: E30-VTC
Location: DISK$USER3:[DENVER.JAN13.DEV-30]
Summary: A Lidar contour coverage at intervals of 10 Lidar Units. E30-VTC was interpolated
from E30-VT. Contours range from 10 to 80 Lidar Units.
Coverage Type: Lidar
Faatura Typa: Line
Avaraga RMS arror: N/A
Input Soala: N/A
Data Froduaad: 11/1/88
DESCRIPTION OF SINGLE PRECISION COVERAGE E30-VTC
ARCS
POLYGONS
Arcs = 189
Segments = 5752
32 bytes of Arc Attribute Data
POINTS
Label Points = 0
TOLERANCES
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics
Annotations =
Links =
STATUS
Fuzzy
Dangle
6.243 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/26/90
TYPE NAME
464655.938
528800.625
Ymin
Ymax
INTERNAL NAME
385265.750
447693.031
NO. RECS LENGTH EXTERNL
DF E30-VTC.AAT
DF E30-VTC.TIC
DF E30-VTC.BND
ARC019DAT
ARC020DAT
ARC021DAT
189
4
1
32 XX
12 XX
16 XX
E30-VTC.AAT
189 Records Selected.
COLUMN
ITEM NAME
WIDTH OUTPUT
TYPE N
DEC ALTERNATE NAME
INDEXED?
1
FNODE#
4 5
B
0
-
5
TNODE#
4 5
B
0
-
9
LPOLY#
4 5
B
0
-
13
RPOLY#
4 5
B
0
-
17
LENGTH
4 12
F
3
-
21
E30-VTC#
4 5
B
0
-
25
E30-VTC-ID
4 5
B
0
-
29
LIDAR
4 12
F
3
-
LOG 03/26/90
Date Time Elap CPU I/O Command
min sec opr
11/ 1/88 16:47 7 228 531 TINCONTOUR E30-VT E30-VTC 10 0 LIDAR SMOOTH
3/26/90 10: 7 0 1 76 EXTERNALALL
3/26/90 10:16 0 1 76 EXTERNALALL
49
-------
Nan* of Lattiaa: E30-VTL.LAT
Location: DISK$USER3:[DENVER.JAN13.DEV-30]
Summary: A LATTICE created from TIN E30-VT. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E30-VTL.LAT was used to create polygon coverage E30-VTLP.
Coverage Type: Lidar
Feature Type: LATTICE
Average RMS error: N/A
Input Soala: N/A
Data Produoad: 11/2/88
LATTICE DESCRIPTION FOR E30-VTL.LAT
Lattice size ^nd origin
Points in X/Y = 250 250 Origin (x,y) = 464649.531 385259.500
Lattice distance between points
Distance in X = 257.661 Distance in Y = 250.762
Surface value range
Min Z = 0.000 Max Z = 86.644
Lattice boundary
Xmin = 464649.531 Ymin = 385259.500
Xmax = 528807.063 Ymax = 447699.281
50
-------
Hum of Covaraga: E30-VTLP
Location: DISK$USER3:[DENVER.JAN13.DEV-30]
Summary: A polygon coverage representing Lidar backscatter based on 5 Lidar Unit
intervals. Interpolated from LATTICE E30-VTL using the INFO lookup table LIDAR2_LKUP.
Lidar ranges from 5 to a maximum value of 90.
Covaraga Typa: Lidar
Faatura Typa: Polygon
Avaraga SMS azror: N/A
Input Soala: N/A
Data Preduaad: 11/1/88
DESCRIPTION OF SINCLB PRSCI8I0N COVERAGE B30-VTLP
ARCS
Arcs = 1864
Segments = 18576
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 824
Polygon Topology is present.
23 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
823
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy =
Dangle =
6.269 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin
464907.188
Ymin
385259.500
Xmax =
529064.750
Ymax =
447950.
031
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH
EXTERNL
DF E30-VTLP.TIC
ARC02 8DAT
4
12
XX
DF E30-VTLP.BND
ARC029DAT
1
16
XX
DF E30-VTLP.PAT
ARC030DAT
824
23
XX
E30-VTLP.PAT
824 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT TYPE N.DEC
ALTERNATE NAME
INDEXED?
1 AREA
4
12
F 3
-
5 PERIMETER
4
12
F 3
-
9 E30-VTLP#
4
5
B 0
-
13 E30-VTLP-ID
4
5
B 0
-
17 RANGE-CODE
4
5
B 0
-
21 RNGE
3
3
I
-
LOG 03/26/90
Date Time Elap
CPU I/O
Command
min
sec opr
11/ 2/88 9:17 3 77 2142 ELIMINATE E30-VTLP E30-VTLP-ELIM NOKEEPEDGE POLY
11/ 2/88 9:32 0 3 179 RENAME E30-VTLP-ELIM E30-VTLP
3/26/90 10: 7 0 2 81 EXTERNALALL
3/26/90 10:16 0 2 81 EXTERNALALL
51
-------
Nam* of Covaraga: E30-RANGE-M
Loaation: DISK$USER3:[DENVER.JAN13.DEV-30]
Summary: E30-RANGE-M represents Lidar intensities at 8 specific ranges coded as: 11, 22,
34, 45, 56, 67, 78 and > 78. E30-RANGE-M was dissolved from E30-VTLP baaed on these eight
Lidar intensities.
Covaraga Typa: Lidar
Faatura Typa: Polygon
Avaraga RMS arror: N/A
Input Soala: N/A
Data Produoad: 11/2/88
DESCRIPTION OF SINGLE PRECISION COVERAGE Z30-RANCS-M
ARCS
Arcs = 201
Segments = 9380
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 108
Polygon Topology is present.
22 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points = 107 Tics = 4
Annotations = 0
Links = 0
TOLERANCES STATUS
Fuzzy
Dangle
6.269 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
464907.108
529064.750
Ymin
Ymax
385259.500
447950.031
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E30-RANGE-M.BND
DF E30-RANGE-M.TIC
DF E30-RANGE-M.PAT
ARC025DAT
ARC026DAT
ARC032DAT
1
4
108
16 XX
12 XX
22 XX
E30-RANGE-M.PAT
108 Records Selected.
COLUMN ITEM NAME
1 AREA
5 PERIMETER
9 E30-RANGE-M#
13 E30-RANGE-M-ID
17 RNGE
20 RANGE-CODE
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
12
12
5
5
3
3
F
F
B
B
I
I
LOG 03/26/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
11/ 2/88 10:25 5 69
3/26/90 10: 6 0 2
3/26/90 10:15 0 2
3114 DISSOLVE E30-VTLP E30-RANGE-M RNGE
78 EXTERNALALL
81 EXTERNALALL
52
-------
II. DEV-50 (Lidar surfaces generated based on 50 maters ACL).
Nam* of Cevartga: E50_APP
Loaation: DISK$USER3:[DENVER.JAN13.DEV-50]
Summary: E50_APP represents Lidar return values collected 1/13/88 at 50 meters AGL from
08:00 to 09:44. Mission data was organized by transect and was obtained from data file
[denver.exe]DB3.GND. Data was generated from locational values collected at time of
mission.
Covaraga Typ«: Lidar
Faatura Typa: Point
Avaraga SMS arror: N/A
Input Saala: N/A
Data Produoad: 11/2/8 8
DESCRIPTION OF SINGLE PRECISION COVERAGE E50 APP
ARCS
POLYGONS
Arcs = 0
Segments — 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 3599
22 bytes of Attribute Data/Point
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy =
Dangle =
6.295 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
463284.469
531264.125
Ymin =
Ymax =
385006.719
447956.094
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E50_APP.PAT
DF E50_APP.TIC
DF E50 APP.BND
ARC000DAT
ARC020DAT
ARC024DAT
3599
4
1
22 XX
12 XX
16 XX
E50_APP.PAT
3599 Records Selected.
COLUMN
1
5
9
13
17
20
ITEM NAME
AREA
PERIMETER
E50_APP#
E50_APP-ID
LIDAR
FLIGHT
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
12
12
5
5
3
3
F
F
B
B
I
I
LOG 03/26/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
11/ 1/88 18:25 2
11/ 1/88 18:28 3
3/26/90 13:13 9
63 134 4 APPEND E50_APP POINT FEATURES
84 826 BUILD E50_APP POINT
124 5153 export cover E50_APP dubl:[pearl.denver]J13-E50_APP.e00
53
-------
Hum of Coverage: E50-TIN
Location: DISK5USER3:[DENVER.JAN13.DEV-50]
Summary: A TIN created from E50_APP using a proximal sampling distance of 1000 meters.
E50-TIN is the first surface model in a series of surface generations.
Coverage Typ«: Lidar
Feature Type: TIN
Average RMS arror: N/A
Input Scale: N/A
Data Produced: 11/1/88
TIN DESCRIPTION FOR Z50-TIN
Tin Topology
Nodes
Hull nodes
357
44
Triangles = 668
Surface value range
Min Z
0 .000
Max Z
88.000
Tin Boundary
Xmin = 463284.469
Xmax = 531264.125
Ymin = 385006.719
Ymax = 447954.906
LOO 03/26/90
Date Time Elap CPU I/O Command
min sec opr
11/ 2/88 8:15 1 25 1066 ARCTIN E50_APP E50-TIN POINT LIDAR # 1000
3/26/90 10:26 0 2 120 EXTERNALALL
54
-------
Mama of Lattiaa: E50-LAT.LAT
Location: DISK$USER3:[DENVER.JAN13.DEV-50]
Summary: A LATTICE created from TIN E50-TIN. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E50-LAT.LAT was used to create the VIP coverage E50-VIP.
Covaraga Typa: Lidar
Faatura Typa: LATTICE
Avaraga RMS arror: N/A
Input Soala: N/A
Data Produoad: 11/2/88
LATTId DESCRIPTION FOR B50-LAT.LAT
Lattice size ?nd origin
Points in X/Y = 250 250 Origin (x, y) = 463284.469 385006.719
Lattice distance between points
Distance in X = 273.011 Distance in Y = 252.804
Surface value range
Min Z = 0.000 Max Z = 78.110
Lattice boundary
Xmin = 463284.469 Ymin = 385006.719
Xmax = 531264.125 Ymax = 447954.906
55
-------
Nam* of Covaraga: E50-VIP
Location: DISK$USER3:[DENVER.JAN13.DEV-50]
Summary: E50-VIP is a point coverage which represents, based on a 15% sample of E50-
LAT.LAT, the Lidar "Z" values which were most important in describing the surface. Two
attributes SPOT, representing Lidar "Z" values, and SFCODE are contained in the INFO file
E50-VIP.PAT. SFCODE was a SPOT feature code, coded as one of the following:
2 for a surface maximum or convexity.
-2 for a surface minimum or concavity
1 for an inflection or transition close to a maximum
-1 an inflection or transition feature close to a minimum
0 for a point that is both a local surface maximum and a local surface surface
minimum.
Covaraga Typa: Lidar
Taafcura Typa: Point
Input SoaXa: N/A
Data Produaad: 11/2/8 8
DESCRIPTION 07 SINGLE PRECISION COVERAGE E50-VIP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 9568
24 bytes of Attribute Data/Point
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy
6.244 N
The coverage has not been Edited
Dangle =
0.000 N
since the last BUILD
or CLEAN.
COVERAGE
BOUNDARY
Xmin =
463830.
500
Ymin =
385259.
531
Xmax =
529899.
063
Ymax =
447702.
094
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME NO.
RECS LENGTH
EXTERNL
DF E50-VIP.BND
ARC043DAT
1
16
XX
DF E50-VIP.TIC
ARC04 5DAT
4
12
XX
DF E50-VIP.PAT
ARC04 6DAT
9568
24
XX
E50-VIP.PAT
9568 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
1 AREA
4
12
F 3
-
5 PERIMETER
4
12
F 3
-
9 E50-VIP#
4
5
B 0
-
13 E50-VIP-ID
4
5
B 0
-
17 SPOT
4
12
F 3
-
21 SFCODE
4
5
B 0
-
LOG 03/26/90
Date Time Elap CPU
min sec
11/ 2/88 8:19 2 58
I/O Command
opr
808 VIP E50-LAT E50-VIP 15
56
-------
Nan* of Covaraga: E50-VT
Location: DISK$USER3:[DENVER.JAN13.DEV-50]
Summary: A TIN created from coverage E50-VIP using a proximal sampling distance of 1500
meters.
Covaraga Typa: Lidar
Faatura Typa: TIN
Avaraga RMS arroc: N/A
Input Saala: N/A
Data Produaad: 11/1/88
TIM DESCRIPTION FOR E50-VT
Tin Topology
Nodes
Hull nodes
748
30
Triangles = 1464
Surface value range
Min Z
0 .000
Max Z
78 . 110
Tin Boundary
Xmin = 464376.500
Xmax = 529899.063
Ymin = 385259.531
Ymax = 447702.094
LOG 03/26/90
Date Time Elap CPU I/O Command
min sec opr
11/ 2/88 8:20 1 41 381 ARCTIN E50-VIP E50-VT POINT SPOT # 1500
3/26/90 10:27 0 2 122 EXTERNALALL
3/26/90 12:47 0 6 234 export cover E50-VT dubl:[pearl.denver]J13-E50-VT.eOO
57
-------
Nam* of Covaraga: E50-VT-HULL
Loaation: DISK$USER3:[DENVER.JAN13.DEV-50]
Summary: A coverage representing the boundary extent of TIN E50-VT. This coverage was used
to set mapextents for plotting and creating views.
Covaraga Typa: Lidar
Faatura Typa: Polygon
Avaraga RMS error: N/A
Input Soala: N/A
Data Froduaad: 11/2/88
DESCRIPTION OF SINGLE PRECISION COVERAGE E50-VT-HULL
ARCS
Arcs = 30
Segments = 30
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 2
Polygon Topology is present.
16 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy =
Dangle =
6.244 N
0.000 N
COVERAGE BOUNDARY
The coverage ha9 not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
464376.500
529899.063
Ymin =
Ymax =
385259.531
447702.094
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E50-VT-HULL.BND
DF E50-VT-HULL.TIC
DF E50-VT-HULL.PAT
ARC038DAT
ARC 03 9D AT
ARC04 IDAT
16
12
16
XX
XX
XX
E 5 0-VT-HULL.PAT
3 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E50-VT-HULL#
4
5
B
0
-
13
E50-VT-HULL-ID
4
5
B
0
-
LOG 03/26/90
Date
Time Elap CPU
min sec
I/O
opr
Command
11/ 2/88 15:33 1 11 1269 tinarc e50—vt e50-vt-hull hull
3/26/90 10:27 0 2 82 EXTERNALALL
3/26/90 12:47 0 8 355 export
dubl:[pearl.denver]J13-E50-VT-HULL.eOO
cover E50-VT-HULL
58
-------
Nam* of Covarag*: E50-VTC
Location: DISK$USER3:[DENVER.JAN13.DEV-50]
Summary: A Lidar contour coverage at intervals of 10 Lidar Units. E50-VTC was interpolated
from E50-VT. Contours range from 10 to 70 Lidar Units.
Coverage Type: Lidar
Faatura Type: Line
Avaraga RMS arroc: N/A
Input Saala: N/A
Data Produoad: 11/2/8 8
DESCRIPTION OF SINGLE PRECISION COVERAGE E50-VTC
ARCS
Arcs = 165
Segments = 4310
32 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy =
Dangle =
6.243 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
464383.063
529892.500
Ymin =
Ymax j
385265.781
447695.844
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E50-VTC.BND
DF E50-VTC.TIC
DF E50-VTC.AAT
ARC033DAT
ARC034DAT
ARC03 7DAT
1
4
165
16 XX
12 XX
32 XX
E50-VTC.AAT
165 Records Selected.
LUMN
ITEM NAME
WIDTH OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
FNODE#
4 5
B
0
-
5
TNODE#
4 5
B
0
-
9
LPOLY#
4 5
B
0
-
13
RPOLY#
4 5
B
0
-
17
LENGTH
4 12
F
3
-
21
E50-VTC#
4 5
B
0
-
25
E50-VTC-ID
4 5
B
0
-
29
LIDAR
4 12
F
3
-
LOG 03/26/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
11/ 2/88 8:24 4
3/26/90 10:27 0
3/26/90 12:50 3
194 524 TINCONTOUR E50-VT E50-VTC 10 0 LIDAR SMOOTH
2 82 EXTERNALALL
34 1563 export cover E50-VTC dubl:[pearl.denver]J13-E50-VTC.eOO
5 9
-------
Nam* of Lattiaa: E50-VTL.LAT
Location: DISK$USER3:[DENVER.JAN13.DEV-50]
Summary: A LATTICE created from TIN E50-VT. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E50-VTL.LAT was used to create polygon coverage E50-VTLP.
Coverag* Typ*: Lidar
Faafcur* Typa: LATTICE
Avaraga RMS error: N/A
Input Saala: N/A
Data Produced: 11/2/88
LATTICE DESCRIPTION FOR E50-VTL.LAT
Lattice size §nd origin
Points in X/Y = 250 250 Origin (x,y)= 464376.500 385259.531
Lattice distance between points
Distance in X = 263.143 Distance in Y = 250.773
Surface value range
Min Z = 0.000 Max Z = 78.110
Lattice boundary
Xmin = 464376.500 Ymin = 385259.531
Xmax = 529899.063 Ymax = 447702.094
60
-------
Nam* of Covaraga: E50-VTLP
Location: DISKSUSER3:[DENVER.JAN13.DEV-50]
Summary: A polygon coverage representing Lidar backscatter baaed on 5 Lidar Unit
intervals. Interpolated from LATTICE E50-VTL using the INFO lookup table LIDAR2_LKUP.
E50-VTLP ranges from 5 to a maximum value of 80 Lidar Units.
Covaraga Typa: Lidar
Faafcura Typa: Polygon
Avaraga RMS arror: N/A
Input. Soala: N/A
Data Produoad: 11/2/88
DESCRIPTION OF SINGLE PRECISION COVERAGE ESO-VTLP
ARCS
POLYGONS
Arcs = 920
Segments = 15329
0 bytes of Arc Attribute Data
POINTS
Label Points =
429
TOLERANCES
Polygons = 430
Polygon Topology is present.
23 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
6.269 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
464376.500
530162.188
Ymin =
Ymax =
385259.531
447952.875
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E50-VTLP.BND
DF E50-VTLP.TIC
DF E 5 0-VTLP.PAT
ARC026DAT
ARC027DAT
ARC030DAT
1
4
430
16 XX
12 XX
23 XX
E50-VTLP.PAT
430 Records Selected.
COLUMN
1
5
9
13
17
21
ITEM NAME
AREA
PERIMETER
E50-VTLP#
E50-VTLP-ID
RANGE-CODE
RNGE
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
LOG 03/26/90
Date
Time Elap
min
CPU
sec
I/O
opr
12
12
5
5
5
3
Command
F
F
B
B
B
I
11/ 2/88 9:33 2
11/ 2/88 11:49 0
3/26/90 10:27 0
3/26/90 13: 4
51 2367 ELIMINATE E50-VTLP E50-VTLP-ELIM NOKEEPEDGE POLY
4 183 RENAME E50-VTLP-ELIM E50-VTLP
2 82 EXTERNALALL
14 127 6051 export cover E50-VTLP
dubl:[pearl.denver]J13-E50-VTLP.e00
61
-------
Nam* of Covaraga: E50-RANGE-M
Location: DISKSUSER3:[DENVER.JAN13.DEV-50]
Summary: E50-RANGE-M represents Lidar intensities at 8 specific ranges coded as: 11, 22,
34, 45, 56, 67, 78 and > 78. E50-RANGE—M was dissolved from E50—VTLP based on these eight
Lidar intensities.
Covaraga Typa: Lidar
Faafcura Typa: Polygon
Avarag* SMS arror: N/A
Input Soala: N/A
Data Produaad: 11/2/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE E50-RANGE-M
ARCS
POLYGONS
Arcs = 140
Segments = 7 640
0 bytes of Arc Attribute Data
POINTS
Label Points =
86
TOLERANCES
Polygons = 87
Polygon Topology is present.
19 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
6.269 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
464376.500
530162.188
Ymin =
Ymax =
385259.531
447952.875
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E50-RANGE-M.PAT
DF E50-RANGE-M.BND
DF E50-RANGE-M.TIC
ARC023DAT
ARC025DAT
ARC029DAT
87
1
4
19 XX
16 XX
12 XX
E50-RANGE-M.PAT
87 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E50-RANGE-M#
4
5
B
0
-
13
E50-RANGE-M-ID
4
5
B
0
-
17
RNGE
3
3
I
-
-
LOG 03/26/90
Date Time Elap CPU I/O Command
min sec opr
11/ 2/88 12: 0 5 50 2095 DISSOLVE E50-VTLP E50-RANGE-M RNGE
3/26/90 10:26 0 2 91 EXTERNALALL
3/26/90 12:32 2 50 2803 export cover E50-RANGE-M
dubl:[pearl.denver]J13-E50-RANGE-M.eOO
62
-------
III. DEV-60 (Lidar surfaces generated basad on 60 meters AGL).
Nam* of Covmrmg*: E60_APP
Location: DUBO:[DENVER.JAN13.DEV-60]
Summary: E60_APP represents Lidar return values collected 1/13/88 at 60 meters AGL from
08:00 to 09:44. Mission data was organized by transect and was obtained from data file
[denver.exe]DB3.GND. Data was generated from locational values collected at time of
mission.
Coverage Typa: Lidar
Feature Type: Point
Avaraga RMS error: N/A
Input Soala: N/A
Data Produced: 11/2/88
DESCRIPTION OF SINGLE PRECISION COVERAGE E60 APP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 3599
22 bytes of Attribute Data/Point
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy
Dangle
6.295 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xrain =
Xmax =
463284.469
531264.125
Ymin
Ymax
385006.719
447956.094
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E60_APP.PAT
DF E60_APP.TIC
DF E60 APP.BND
ARC002DAT
ARC022DAT
ARC024DAT
3599
4
1
22 XX
12 XX
16 XX
E60 APP.PAT
3599 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT TYPE
N.DEC ALTERNATE NAME INDEXED?
1 AREA
4
12
F
3
5 PERIMETER
4
12
F
3
9 E60 APP#
4
5
B
0
13 E60 APP-ID
4
5
B
0
17 LIDAR
3
3
I
-
20 FLIGHT
3
3
I
-
LOG 03/26/90
Date Time Elap
CPU
I/O
Command
min
sec
opr
11/ 1/88 19:18 2
62
1346
APPEND
E60
APP POINT FEATURES
11/ 1/88 19:20 2
85
825
BUILD E60
APP
POINT
3/26/90 13:57 4 118
5129
export cover
E60_APP dubl:[pearl.denver]J13-E60 .
63
-------
Ham* of Coverage: E60-TIN
Location: DUBO:[DENVER.JAN13.DEV-60]
Summary: A TIN created from E60_APP using a proximal sampling distance of 1000 meters.
E60-TIN is the first surface model in a series of surface generations.
Coverage Type: Lidar
Feature Type: TIN
Average RMS error: N/A
Input Scale: N/A
Date Produaed: 11/2/8 8
TIM DESCRIPTION FOR E60-TIN
Tin Topology
Nodes
Hull nodes
357
44
Triangles = 668
Surface value range
Min Z
0 .000
Max Z
101.000
Tin Boundary
Xmin = 463284.469
Xmax = 531264 . 125
Ymin = 385006.719
Ymax — 4 47 954.906
LOG 03/26/90
Date Time Elap CPU I/O Command
min sec opr
11/ 2/88 8:30 1 26 1074 ARCTIN E60_APP E60-TIN POINT LIDAR # 1000
3/26/90 10:37 0 3 173 EXTERNALALL
64
-------
Nam* of Lattiaa: E60-LAT.LAT
Location: DISK$USER3:[DENVER.JAN13.DEV-60]
Summary: A LATTICE created from TIN E60-TIN. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E60-LAT.LAT was used to create the VIP coverage E60-VIP.
Coverage Type: Lidar
F«atur« Type: LATTICE
Average RMS error: N/A
Input Scale: N/A
Data Produced: 11/2/88
LATTICE DESCRIPTION FOR K60-LAT.LAT
Lattice size ^nd origin
Points in X/Y = 250 250 Origin (x,y)= 463284.469 385006.719
Lattice distance between points
Distance in X = 273.011 Distance in Y = 252.804
Surface value range
Min Z = 0.000 Max Z = 77.947
Lattice boundary
Xmin = 463284.469 Ymin = 385006.719
Xmax = 531264.125 Ymax = 447954.906
65
-------
Nam* of Covaraga: E60-VIP
Location: DUBO:[DENVER.JAN13.DEV-60]
Summary: E60-VIP is a point coverage which represents, based on a 15% sample of E60-
LAT.LAT, the Lidar "Z" values which were moat important in describing the surface. Two
attributes SPOT, representing Lidar "Z" values, and SFCODE are contained in the INFO file
E80-VIP.PAT. SFCODE was a SPOT feature code, coded as one of the following:
2 for a surface maximum or convexity.
-2 for a surface minimum or concavity
1 for an inflection or transition close to a maximum
-1 an inflection or transition feature close to a minimum
0 for a point that is both a local surface maximum and a local surface surface
minimum.
Covarag* Typa: Lidar
Faatura Typa: Point
Input Soala: N/A
Oat* Produaad: 11/2/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE E60-VTP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 9498
24 bytes of Attribute Data/Point
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy =
Dangle =
6.244 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
463830.500
Ymin =
385259.
531
Xmax =
530172.063
Ymax =
447702.
094
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH
EXTERNL
DF E60-VIP.BND
ARC04 7DAT
1
16
XX
DF E60-VIP.TIC
ARC04 9DAT
4
12
XX
DF E60-VIP.PAT
ARC050DAT
9498
24
XX
E60-VIP.PAT
9498 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT TYPE N.DEC
ALTERNATE NAME
INDEXED?
1 AREA
4
12 F 3
-
5 PERIMETER
4
12 F 3
-
9 E60-VIP#
4
5 B 0
-
13 E60-VIP-ID
4
5 B 0
-
17 SPOT
4
12 F 3
-
21 SFCODE
4
5 B 0
-
LOG 03/26/90
Date Time Elap
CPU I/O
Command
min
sec opr
11/ 2/88 8:36
58
797
VIP E60-LAT E60-VIP 15
66
-------
Nam* of Coverage: E60-VT
Location: DISK$USER3:[DENVER.JAN13.DEV-60]
Summary: A TIN created from coverage E60-VIP using a proximal sampling distance of 1500
meters.
Covaraga Typa: Lidar
Faatura Typa: TIN
Avaraga RMS trior: N/A
Input Saala: N/A
Data Produoad: 11/1/88
TIM DESCRIPTION FOR K60-VT
Tin Topology
Nodes
Hull nodes
732
34
Triangles = 1428
Surface value range
Min Z
0 .000
Max Z
77.947
Tin Boundary
Xmin = 464376.500
Xmax = 529899.063
Ymin = 385259.531
Ymax = 447702.094
LOG 03/26/90
Date Time Elap CPU I/O Command
min sec opr
11/ 2/88 8:37 1 42 390 ARCTIN E60-VIP E60-VT POINT SPOT # 1500
3/26/90 10:37 0 3 137 EXTERNALALL
3/26/90 13:46 0 5 223 export cover E60-VT dubl:[pearl.denver]J13-E60-VT.eOO
67
-------
Mam* of Covaraga: E60-VT-HULL
Location: DISK$USER3:[DENVER.JAN13.DEV-60]
Summary: A coverage representing the boundary extent of TIN E60-VT. This coverage was used
to set mapextents for plotting and creating view3.
Covarsg* Typa: Lidar
Faatura Typa: Polygon
Avaraga RMS mrror: N/A
Input Saala: N/A
Data Produaad: 11/2/8 8
DESCRIPTION Or SINGLE PRECISION COVERAGE E60-VT-HULL
ARCS
Arcs = 34
Segments = 34
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 2
Polygon Topology is present.
16 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy =
Dangle =
6.244 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
464376.500
529899.063
Ymin =
Ymax =
305259.531
447702.094
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E 60-VT-HULL.BND
DF E60-VT-HULL.TIC
DF E60-VT-HULL.PAT
ARC023DAT
ARC02 5DAT
ARC034DAT
16
12
16
XX
XX
XX
E60-VT-HULL.PAT
3 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E60-VT-HULL#
4
.5
B
0
-
13
E60-VT-HULL-ID
4
5
B
0
-
LOG 03/26/90
Date Time Elap CPU I/O Command
min sec opr
11/ 2/88 14:56 1 10 511 TINARC E60-VT E60-VT-HULL HULL
3/26/90 10:37 0 2 82 EXTERNALALL
3/26/90 13:45 0 8 360 export cover E60-VT-HULL
dubl:[pearl.denver]J13-E60-VT-HULL.eOO
68
-------
Nam* of Coverage: E60-VTC
Location: DUBO:(DENVER.JAN13.DEV-60]
Summary: A Lidar contour coverage at intervals of 10 Lidar Units. E60-VTC was interpolated
from E60-VT. Contours range from 10 to 70 Lidar Units.
Coverage Type: Lidar
Feature Type: Line
Average RMS arror: N/A
Input Soala: N/A
Data Produced: 11/2/88
DESCRIPTION Or SINGLE PRECISION COVERAGE B60-VTC
ARCS
POLYGONS
Arcs = 175
Segments = 4565
32 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
Label Points =
TOLERANCES
SECONDARY FEATURES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
6.243 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
464383.063
529892.500
Ymin =
Ymax =
385265.781
447695.844
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E60-VTC.BND
DF E60-VTC.TIC
DF E60-VTC.AAT
ARC035DAT
ARC037DAT
ARC038DAT
1
4
175
16 XX
12 XX
32 XX
E60-VTC.AAT
175 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
FNODE#
4
5
B
0
-
5
TNODE#
4
5
B
0
-
9
LPOLY#
4
5
B
0
-
13
RPOLY#
4
5
B
0
-
17
LENGTH
4
12
F
3
-
21
E60-VTC#
4
5
B
0
-
25
E60-VTC-ID
4
5
B
0
-
29
LIDAR
4
12
F
3
-
LOG 03/26/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
11/ 2/88 8:41 4 193 535 TINCONTOUR E60-VT E60-VTC 10 0 LIDAR SMOOTH
3/26/90 10:37 0 2 82 EXTERNALALL
3/26/90 13:47 1 32 1598 export cover E60-VTC dubl:[pearl.denver]J13-E60-VTC.eOO
69
-------
Mara* of Lattiaa: E60-VTL.LAT
Location: DISK$USER3:[DENVER.JAN13.DEV-60]
Summary: A LATTICE created from TIN E60-VT. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E60-VTL.LAT was used to create polygon coverage E60-VTLP.
CoT«rig« Typ*: Lidar
Faatura Typa: LATTICE
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produoad: 11/2/8 8
LATTICE DESCRIPTION FOR E60-VTL.LAT
Lattice size ^nd origin
Points in X/Y = 250 250 Origin (x,y)= 464376.500 385259.531
Lattice distance between points
Distance in X = 263.143 Distance in Y = 250.773
Surface value range
Min Z = 0.000 Max Z = 70.189
Lattice boundary
Xmin = 464376.500 Ymin = 385259.531
Xmax = 529899.063 Ymax = 447702.094
70
-------
Mam* of Coverage: C60-VTLP
Location: DISK$USER3:[DENVER.JAN13.DEV-60]
Summary: A polygon coverage representing Lidar backscatter based on 5 Lidar Unit
intervals. Interpolated from LATTICE E60-VTL using the INFO lookup table LIDAR2_LKUP.
E60-VTLP ranges from 5 to a maximum value of 75 Lidar Units.
Coverage Type: Lidar
Feature Type: Polygon
Average RMS error: N/A
Input Scale: N/A
Data Produced: 11/2/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE ECO-VTLP
ARCS
Arcs = 1074
Segments = 16051
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 501
Polygon Topology is present.
23 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
500
TOLERANCES
Fuzzy
Dangle
Xmin =
Xmax =
ITEMS 03/26/90
TYPE NAME
Tics
Annotations
Links
STATUS
6.269 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
464376.500
530162 .188
Ymin =
Ymax =
INTERNAL NAME
385259.531
447952.875
NO. RECS LENGTH EXTERNL
DF E60-VTLP.BND
DF E60-VTLP.TIC
DF E60-VTLP.PAT
ARC029DAT
ARC030DAT
ARC033DAT
1
4
501
16 XX
12 XX
23 XX
E60-VTLP.PAT
501 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E60-VTLP#
4
5
B
0
-
13
E60-VTLP-ID
4
5
B
0
-
17
RANGE-CODE
4
5
B
0
-
21
RNGE
3
3
I
-
-
LOC 03/26/90
Date
Time Elap CPU
min sec
I/O Command
opr
11/ 2/88 9:31 3 57
11/ 2/88 14:41 0 4
3/26/90 10:37 0 2
3/26/90 13:52 5
dubl:[pearl.denver]J13-E60-VTLP
2409 ELIMINATE E60-VTLP E60—VTLP—ELIM NOKEEPEDGE POLY
183 rename e60-vtlp-elim e60-vtlp
110 EXTERNALA1L
133 6557 export cover E60-VTLP
eOO
71
-------
Nam* of Coverage: E60-RANGE-M
Location: DISK$USER3:[DENVER.JAN13.DEV-60]
Summary: E60-RANGE-M represents Lidar intensities at 8 specific ranges coded as: 11, 22,
34, 45, 56, 67, 78 and > 78. E60-RANGE-M was dissolved from E60-VTLP based on these eight
Lidar intensities .
Coverage Type: Lidar
Feature Type: Polygon
Average RMS error: N/A
Input Scale: N/A
Data Produoad: 11/2/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE E60-RANGE-M
ARCS
Arcs = 181
Segments = 8028
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 103
Polygon Topology is present.
19 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
102
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
6.269 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/26/90
TYPE NAME
464376.500
530162.188
Ymin
Ymax
INTERNAL NAME
385259.531
447952.875
NO. RECS LENGTH EXTERNL
DF
E60-RANGE-M.PAT
ARC026DAT
103
19
XX
DF
E60-RANGE-M.BND
ARC027DAT
1
16
XX
DF
E60-RANGE-M.TIC
ARC031DAT
4
12
XX
E60-RANGE-M.PAT
103 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E60-RANGE-M#
4
5
B
0
-
13
E60-RANGE-M-ID
4
5
B
0
-
17
RNGE
3
3
I
-
-
LOG 03/26/90
Date Time Elap CPU I/O Command
min sec opr
11/ 2/88 14:48 3 52 2150 DISSOLVE E60-VTLP E60-RANGE-M RNGE
3/26/90 10:36 0 2 90 EXTERNALALL
3/26/90 13:28 14 57 2990 export cover E60-RANGE-M
dubl:[pearl.denver]J13-E60-RANGE-M.eOO
72
-------
Ill. DEV-80 (Lidar surfacas generated baaed on 80 maters AGL).
Daaoription of Covaraga: E80_APP
Location: DISKSUSER3:[DENVER.JAN13.DEV-80]
Location: DUBO:[DENVER.JAN13.DEV-60]
Summary: E80_APP represents Lidar return values collected 1/13/88 at 80 meters AGL from
08:00 to 09:44. Mission data was organized by transect and was obtained from data file
[denver.exe]DB3.GND. Data was generated from locational values collected at time of
mission.
Covaraga Typa: Lidar
Paatura Typa: Point
Avaraga SMS arror: N/A
Input Saala: N/A
Data Producad: 11/2/88
DESCRIPTION Or SINGLE PRECISION COVERAGE E80 APP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 3599
22 bytes of Attribute Data/Point
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
6.295 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
463284.469
531264 .125
Ymin =
Ymax =
385006.719
447956.094
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E80_APP.TIC
DF E80_APP.BND
DF E80 APP.PAT
ARC020DAT
ARC024DAT
ARC053DAT
4
1
3599
12 XX
16 XX
22 XX
E80_APP.PAT
3599 Records Selected.
COLUMN ITEM NAME
1
5
9
13
17
20
AREA
PERIMETER
E80_APP#
E80_APP-ID
LIDAR
FLIGHT
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
12
12
5
5
3
3
F
F
B
B
I
I
LOG 03/27/90
Date Time Elap CPU
min sec
I/O Command
opr
11/ 1/88 19:54 2
11/ 1/88 19:56 2
3/26/90 14:23 4
62 1339 APPEND E80_APP POINT FEATURES
84 824 BUILD E80_APP POINT
117 5133 export cover E80_APP dubl:[pearl-denver]J13-E80_APP.eOO
73
-------
Daaoription of Covaraga: E80-TIN
Looation: DISK$CJSER3:[DENVER.JAN13.DEV-80]
Summary: A TIN created from ESO_APP using a proximal sampling distance of 1000 meters.
E80-TIN is the first surface model in a series of surface generations for 80 meters AGL.
Covaraga Typa: Lidar
Faatura Typa: TIN
Avaraga SMS arror: N/A
Input Seal*: N/A
Data Produoad: 11/2/88
TIM DESCRIPTION FOR E80-TIN
Tin Topology
Nodes
Hull nodes
357
44
Triangles = 668
Surface value range
Min Z
0.000
Max Z
85.000
Tin Boundary
Xmin = 463284.469
Xmax = 531264.125
Ymin = 385006.719
Ymax = 447954.906
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
11/ 2/88 8:46 1 27 1083 ARCTIN E80_APP E80-TIN POINT LIDAR # 1000
3/26/90 10:41 0 2 136 EXTERNALALL
7 4
-------
Nan* of Lattice: E80-LAT.LAT
Location: DISK$USER3:[DENVER.JAN13.DEV-80]
Summary: A LATTICE created from TIN E80-TIN. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E80-LAT.LAT was used to create the VIP coverage E80-VIP.
Coverage Type: Lidar
Feature Type: LATTICE
Average RMS error: N/A
Input Soale: N/A
Date Produaed: 11/2/88
LATTICE DESCRIPTION FOR H0O-LAT.LAT
Lattice description for E80-LAT.LAT
Lattice size and origin
Points in X/Y = 250 250 Origin (x,y)= 463284.469 385006.719
Lattice distance between points
Distance in X = 273.011 Distance in Y = 252.804
Surface value range
Min Z = 0.000 Max Z = 85.000
Lattice boundary
Xmin = 463284.469 Ymin = 385006.719
Xmax = 531264.125 Ymax = 447954.906
75
-------
Daaaripfcion of Covaraga: E80-VIP
Location: DISK$USER3:[DENVER.JAN13.DEV-80]
Summary: E80-VIP is a point coverage which represents, based on a 15% sample of E80-
LAT.LAT, the Lidar "Z" values which were most important in describing the surface. Two
attributes SPOT, representing Lidar "Z" values, and SFCODE are contained in the INFO file
E80-VIP.PAT. SFCODE was a SPOT feature code, coded as one of the following:
2 for a surface maximum or convexity.
-2 for a surface minimum or concavity
1 for an inflection or transition close to a maximum
-1 an inflection or transition feature close to a minimum
0 for a point that is both a local surface maximum and a local surface surface
minimum.
Covaraga Typa: Lidar
Faatura Typa: Point
Input Seal*: N/A
Data Produaad: 11/2/8 8
DESCRIPTION OF SINGLE PRECISION COVERAGE E60-VIP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 9864
24 bytes of Attribute Data/Point
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy
Dangle
6.244 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
464376.500
529626.063
Ymin
Ymax
385259.531
447702.094
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E80-VIP.BND
DF E80-VIP.TIC
DF E80-VIP.PAT
ARC043DAT
ARC045DAT
ARC05 2D AT
1
4
9864
16 XX
12 XX
24 XX
E80-VIP.PAT
9864 Records Selected.
COLUMN
1
5
9
13
17
21
ITEM NAME
AREA
PERIMETER
E80-VIP#
E80-VIP-ID
SPOT
SFCODE
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
12
12
5
5
12
5
F
F
B
B
F
B
LOG 03/27/90
Date Time Elap CPU I/O
min sec opr
Command
11/ 2/88 8:51
3/26/90 14:11
2 60 817 VIP E80-LAT E80-VIP 15
13 338 14461 export cover E80-VIP dubl:[pearl.denver]J13-E80-VIP.eOO
76
-------
Description of Covaraga: E80-VT
Location: DISKSUSEE3:[DENVER.JAN13.DEV-80]
Stannary: A TIN created from coverage E80-VIP using a proximal sampling distance of 1500
meters.
Covaraga Typa: Lidar
Faatura Typa: TIN
Avaraga RMS arror: N/A
Input Saala: N/A
Data Froduaad: 11/1/88
TIN DESCRIPTION FOR E60-VT
Tin Topology
Nodes
Hull nodes
735
34
Triangles = 1434
Surface value range
Min Z
0.000
Max Z
85.000
Tin Boundary
Xmin = 464376.500
Xmax = 529353.063
Ymin = 385259.531
Ymax = 447702.094
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
11/ 2/88 8:52 1 42 390 ARCTIN E80-VIP E80-VT POINT SPOT # 1500
3/26/90 10:41 0 2 121 EXTERNALALL
3/26/90 14:12 0 6 226 export cover E80-VT dubl:[pearl.denver]J13-E80-VT.eOO
77
-------
Daaaription of Covaraga: E80-VT-HULL
Location: DISK$USER3:[DENVER.JAN13.DEV-80]
Summary: A coverage representing the boundary extent of TIN E80-VT. This coverage was used
to set mapextents for plotting and creating views.
Covaraga Typa: Lidar
Faatura Typa: Polygon
Avaraga RMS arror: N/A
Input Soala: N/A
Data Produead: 11/2/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE E60-VT-HULL
ARCS
Arcs = 34
Segments = 34
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 2
Polygon Topology is present.
16 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points
TOLERANCES
Fuzzy =
Dangle =
Tics =
Annotations =
Links =
STATUS
6.244 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
X.max =
ITEMS 03/27/90
TYPE NAME
464376.500
529353.063
Ymin =
Ymax =
INTERNAL NAME
385259.531
447702.094
NO. RECS LENGTH EXTERNL
DF E80-VT-HULL.BND
DF E80-VT-HULL.TIC
DF E80-VT-HULL.PAT
ARC022DAT
ARC023DAT
ARC038DAT
16 XX
12 XX
16 XX
E80-VT-HULL.PAT
3 Records Selected.
COLUMN ITEM NAME
1 AREA
5 PERIMETER
9 E80-VT-HULL#
13 E80-VT-HULL-ID
WIDTH OUTPUT
4
12
F
4
12
F
4
5
B
4
5
B
TYPE N.DEC
3
3
0
0
ALTERNATE NAME
INDEXED?
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
11/ 3/88 10: 9 0 9 508 TINARC E80-VT E80-VT-HULL HULL
3/26/90 10:41 0 2 82 EXTERNALALL
3/26/90 14:12 0 8 360 export cover E80-VT-HULL
dubl:[pearl.denver]J13-E80-VT-HULL.eOO
78
-------
Description of Covaraga: E80-VTC
Location: DISK$USER3:[DENVER.JAN13.DEV-80]
Summary: A Lidar contour coverage at intervals of 10 Lidar Units. E80-VTC was interpolated
from E80-VT. Contours range from 10 to 80 Lidar Units.
Covaraga Typa: Lidar
Faatura Typa: Line
Avaraga RMS arror: N/A
Input Saala: N/A
Data Froduaad: 11/2/88
DESCRIPTION OF SINGLE PRECISION COVERAGE ESO-VTC
ARCS
POLYGONS
Arcs = 168
Segments = 4538
32 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
Label Points =
TOLERANCES
SECONDARY FEATURES
Tics =
Annotations =
Links =
STATUS
Fuzzy
6.243 N
The coverage has not been Edited
Dangle =
0.000 N
since the last
BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
464383.000
Ymin =
385265.
781
Xmax =
529346.563
Ymax =
447695.
844
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH
EXTERNL
DF E80-VTC.BND
ARC029DAT
1
16
XX
DF E80-VTC.TIC
ARC030DAT
4
12
XX
DF E80-VTC.AAT
ARC042DAT
168
32
XX
E80-VTC.AAT
168 Records Selected
COLUMN ITEM NAME
WIDTH
OUTPUT TYPE N.DEC
ALTERNATE NAME
INDEXED?
1 FNODE#
4
5
B 0
-
5 TNODE#
4
5
B 0
-
9 LPOLY#
4
5
B 0
-
13 RP0LY#
4
5
B 0
-
17 LENGTH
4
12
F 3
-
21 E80-VTC#
4
5
B 0
-
25 E80-VTC-ID
4
5
B 0
-
29 LIDAR
4
12
F 3
-
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
11/ 2/88 8:56 4 195 531 TINC0NT0UR E80-VT E80-VTC 10 0 LIDAR SMOOTH
3/26/90 10:41 0 2 82 EXTERNALALL
3/26/90 14:14 2 34 1581 export cover E80-VTC dubl:(pearl.denver]J13-E80-VTC.eOO
79
-------
Mama of Lattiae: E80-VTL.LAT
Location: DISK$USER3:(DENVER.JAN13.DEV-80]
Summary: A LATTICE created from TIN E80-VT. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E80-VTL.LAT was used to create polygon coverage E80-VTLP.
Coverage Type: Lidar
Feature Type: LATTICE
Average RMS error: N/A
Input Saale: N/A
Data Produced: 11/2/88
LATTICE DESCRIPTION FOR B80-VTL.LAT
Lattice size send origin
Points in X/Y = 250 250 Origin (x,y)= 464376.500 385259.531
Lattice distance between points
Distance in X = 260.950 Distance in Y = 250.773
Surface value range
Min Z = 0.000 Max Z = 81.621
Lattice boundary
Xmin = 464376.500 Ymin = 385259.531
Xmax = 529353.063 Ymax = 447702.094
80
-------
Daaoription of Covaraga: E80-VTLP
Location: DISK$USER3:[DENVER.JAN13.DEV-80]
Summary: A polygon coverage representing Lidar backscatter based on 5 Lidar Unit
intervals. Interpolated from LATTICE E80-VTL using the INFO lookup table LIDAR2 LKUP.
E80-VTLP ranges from 5 to a maximum value of 85 Lidar Units.
Covaraga Typa: Lidar
Faatura Typa: Polygon
Avaraga SMS arror: N/A
Input Soala: N/A
Data Produoad: 11/2/88
DESCRIPTION OF SINGLE PRECISION COVERAGE E80-VTLP
ARCS
Arcs = 1045
Segments = 15610
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 488
Polygon Topology is present.
23 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points
487
TOLERANCES
Tics =
Annotations =
Links —
STATUS
Fuzzy
Dangle
6.269 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
464637.438
529614.000
Ymin =
Ymax =
385259.531
447952.875
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E80-VTLP.BND
DF E80-VTLP-TIC
DF E80-VTLP.PAT
ARC027DAT
ARC031DAT
ARC037DAT
1
4
488
16 XX
12 XX
23 XX
E80-VTLP.PAT
488 Records Selected.
COLUMN
1
5
9
13
17
21
ITEM NAME
AREA
PERIMETER
E80-VTLP#
E80-VTLP-ID
RANGE-CODE
RNGE
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
12
12
5
5
5
3
F
F
B
B
B
I
LOG 03/27/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
11/ 3/88 9:23 2 56 2352 ELIMINATE E80-VTLP E80-VTLP-ELIM NOKEEPEDGE POLY
11/ 3/88 10: 1 0 4 175 RENAME E80-VTLP-ELIM E80-VTLP
3/26/90 10:41 0 2 104 EXTERNALALL
3/26/90 14:19 6 131 6368 export cover E80-VTLP dubl:[pearl.denver]J13-E80-VTLP.eOO
81
-------
Description of Coverage: E8 0-RANGE-M
Location: DISK$USER3:[DENVER.JAN13.DEV-80]
Summary: E80-RANGE-M represents Lidar intensities at 8 specific ranges coded as: 11, 22,
34, 45, 56, 67, 78 and > 78. E80-RANGE-M was dissolved from E80-VTLP based on these eight
Lidar intensities.
Coverage Type: Lidar
Feature Type: Polygon
Average RMS error: N/A
Input Soale: N/A
Data Produced: 11/2/88
DESCRIPTION OF SINGLE PRECISION COVERAGE E0O-RANCE-M
ARCS
POLYGONS
Arcs = 82
Segments = 7472
0 bytes of Arc Attribute Data
POINTS
Label Points =
62
TOLERANCES
Polygons = 63
Polygon Topology is present.
19 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
6.269 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
464637.438
529614.000
Ymin =
Ymax =
385259.531
447952.875
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E80-RANGE-M.PAT
ARC025DAT 63
19
XX
DF E 8 0-RANGE-M.BND
ARC02 6DAT 1
16
XX
DF E80-RANGE-M.TIC
ARC033DAT 4
12
XX
E80-RANGE-M.PAT
63 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT
TYPE N.DEC ALTERNATE NAME
INDEXED?
1 AREA
4
12
F 3
-
5 PERIMETER
4
12
F 3
-
9 E80-RANGE-M#
4
5
B 0
-
13 E80-RANGE-M-ID
4
5
B 0
-
17 RNGE
3
3
I
-
LOG 03/27/90
Date Time Elap
CPU
I/O
Command
min
sec
opr
11/ 3/88 10: 8 3
50
2129
DISSOLVE E80-VTLP E80-RANGE-M RNGE
3/26/90 10:40 0
2
91
EXTERNALALL
3/26/90 13:59 2
47
2627
export
cover E80-RANGE-M
dubl:[pearl.denver]J13-E80-RANGE-M.e00
82
-------
V. FLT - (Transact Mission Flight Linas)
Daaoription ot Covaraga: FLIGHT_DBC-U
Location: DUBO:[DENVER.JAN13.FLT]
Summary: Transect flight lines which were used in the interpolation of Lidar surfaces for
the January 13, 1988 mission. Mission coordinates were used to generate the flight lines.
Cov*raga Typa: Lidar
Faatura Typa: Lines
Avaraga SMS arror: N/A
Input Saala: N/A
Data Produoad: 3/28/90
DESCRIPTION Of SINGLE PRECISION COVERAGE FLIGHT DBC-U
ARCS
POLYGONS
Arcs = 11
Segments = 4032
4 9 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points =
TOLERANCES
Tics =
Annotations =
Links =
STATUS
4
38
0
Fuzzy =
Dangle =
7.035 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin
COVERAGE BOUNDARY
4 63284.4 69 Ymin =
385006.719
Xmax =
531264.125
Ymax =
447956.094
ITEMS
03/29/90
TYPE
NAME
INTERNAL NAME
NO. RECS LENGTH
EXTERNL
DF
FLIGHT DBC-U.AAT
ARC013DAT
11 49
XX
DF
FLIGHT DBC-U.BND
ARC016DAT
1 16
XX
DF
FLIGHT DBC-U.TIC
ARC017DAT
4 12
XX
FLIGHT_DBC-U.AAT
11 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE N
DEC ALTERNATE NAME
INDE)
1
FNODE#
4
5
B
0
-
5
TNODE#
4
5
B
0
-
9
LPOLY#
4
5
B
0
-
13
RPOLY#
4
5
B
0
-
17
LENGTH
4
12
F
3
-
21
FLIGHT DBC-U#
4
5
B
0
-
25
FLIGHT DBC-U-ID
4
5
B
0
-
29
FLT
3
3
I
-
-
32
FLIGHT
3
3
I
-
-
35
TAPE
5
5
C
-
-
40
START.TIME
5
5
N
2
-
45
END.TIME
5
5
N
2
-
83
-------
FLIGHT_DBC-U Continued...
LOG 03/29/90
Date Time Elap CPU I/O Command
min sec opr
3/28/90 11:10 2 36 1649 RESELECT FLIGHT_UTM FLIGHT_DBC-U LINE
3/28/90 11:21 1 29 1748 EXPORT COVER DUBO:[DENVER.JAN13.FLT]FLIGHT_DBC-U
J13-FLIGHT DBC-U.E00
84
-------
Description of Covarag*: FLIGHT_UTM
Location: DUBO:[DENVER.JAN13.FLT]
Summary: January 13, 19S8 mission transect flight lines. Coordinates taken at time of
mission were used to generate this coverage.
Coverage Type: Lidar
feature Type: Line
Average RMS error: N/A
Input Seal*: N/A
Date Produoed: 7/21/88
DESCRIPTION OF SINGLE PRECISION COVERAGE FLIGHT UTM
ARCS
POLYGONS
Arcs = 17
Segments = 5823
4 9 bytes of Arc Attribute Data
POINTS
Label Points = 0
TOLERANCES
Polygons =* 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics
Annotations
Links
STATUS
4
38
0
Fuzzy =
Dangle =
7.035 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/28/90
TYPE NAME
463284.469
531264.125
Ymin
Ymax
INTERNAL NAME
377606.469
447956.094
NO. RECS LENGTH EXTERNL
DF FLIGHT_UTM.AAT
DF FLIGHT_UTM.TIC
DF FLIGHT UTM.BND
ARC009D AT
ARC012DAT
ARC014DAT
17
4
1
49 XX
12 XX
16 XX
FLIGHT_UTM.AAT
17 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
FNODE#
4
5
B
0
-
5
TNODE#
4
5
B
0
-
9
LPOLY#
4
5
B
0
-
13
RPOLY#
4
5
B
0
-
17
LENGTH
4
12
F
3
-
21
FLIGHT UTM#
4
5
B
0
-
25
FLIGHT UTM-ID
4
5
B
0
-
29
FLT
3
3
I
-
-
32
FLIGHT
3
3
I
-
-
35
TAPE
5
5
C
-
-
40
START.TIME
5
5
N
2
-
45
END.TIME
5
5
N
2
-
85
-------
FLIGHT UTM Continued...
LOG 03/28/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
7/20/88
16:33
2
84
484
GENERATE FLT-DB3 DD
7/20/88
16:35
1
11
1042
BUILD FLT-DB3 DD LINE
7/21/88
11: 5
1
19
1549
PROJECT COVER FLT-DB3 DD FLT-DB3 UTM
7/21/88
11: 6
0
9
584
BUILD FLT-DB3 UTM LINE
7/21/88
11: 8
1
12
696
BUILD FLT-DB3 UTM LINE
10/31/88
14 :17
0
3
165
RENAME FLT-DB3 UTM FLIGHT UTM
3/26/90
10:48
0
1
92
EXTERNALALL
3/26/90
14:25
2
39 2159 export
cover FLIGHT UTM
dubl:[pearl.denver]J13-FLIGHT_UTM.eOO
86
-------
87
-------
JAN20 (January 20, 1988 Lidar Collection Mission)
Listings for January 20, 1988 are organized by directories DEV-30, DEV-
50, DEV-60, DEV-80 and FLT.
I. DEV-30 (Lidar suxfacas ganaratad baaad on 30 matara AGL).
Description of Coverage: E30_APP
Location: DUBO:[DENVER.JAN20.DEV-30]
Summary: E30_APP represents Lidar return values collected 1/20/88 at 30 meters AGL from
11:45 to 02:30 PM. Mission data was organized by transect and was obtained from data file
[denver.exe]DB3.GND. Data was generated from locational values collected at time of
mission.
Coverage Type: Lidar
Feature Type: Point
Input Soale: N/A
Digitised by: N/A
Data Produaed: 11/1/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE E30 APP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 3923
37 bytes of Attribute Data/Point
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
5.348 N
0.000 N
The coverage has not been Edited
since the la9t BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
469049.438
534380.188
Ymin =
Ymax =
395002.500
448487.000
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF
E30 APP.PAT
ARC051DAT
3923
37
XX
DF
E30_APP.BND
ARC052DAT
1
16
XX
DF
E30 APP.TIC
ARC053DAT
4
12
XX
87
-------
E30_APP Continued...
E30_APP.PAT
3923 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1 AREA
5 PERIMETER
9 E30_APP#
13 E30_APP-ID
17 LIDAR
20 FLIGHT
23 TAPE
28 START.TIME
33 END.TIME
4
12
F
3
-
4
12
F
3
-
4
5
B
0
-
4
5
B
0
-
3
3
I
-
-
3
3
I
-
-
5
5
C
-
-
5
5
N
2
-
5
5
N
2
-
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
10:55
0
4 224
11:32
0
5 196
11: 3
0
2 96
15:34
7
167 6889
export cover E30_APP dubl:[pearl.denver]J20-E30_APP.eOO
88
-------
Daaaription of Covaraga: E30-TIN
Location: DUBO:[DENVER.JAN20.DEV-30]
Sunmary: A TIN created from E30_APP using a proximal sampling distance of 1000 meters.
E30-TIN is the first surface model in a series of surface generations.
Coverage Typa: Lidar
Faatura Type: TIN
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produced: 7/20/88
TIM DESCRIPTION FOR K30-TIN
Tin Topology
Nodes
Hull nodes
166
11
Triangles = 319
Surface value range
Min Z
0 .000
Max Z
252 .000
Tin Boundary
Xmin = 469049.438
Xmax = 534380.188
Ymin = 395002.500
Ymax = 448487.000
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
7/20/98 17:43 1 26 1082 ARCTIN E30_APP E30-TIN POINT LIDAR # 2250.0
3/26/90 11: 2 0 3 128 EXTERNALALL
89
-------
Mam* of Lattice: E30-LAT.LAT
Location: DISKSUSER3:[DENVER.JAN20.DEV-30]
Summary: A LATTICE created from TIN E30-TIN. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E30-LAT.LAT was used to create the VIP coverage E30-VIP.
Covaraga Typa: Lidar
7aatura Typa: LATTICE
Avaraga RMS arror: N/A
Input Soala: N/A
Data Produoad: 11/2/88
LATTICE DESCRIPTION FOR R30-LAT.LAT
Lattice size and origin
Points in X/Y = 250 250 Origin (x,y)= 469049.438 395002.500
Lattice distance between points
Distance in X = 262.372 Distance in Y = 214.797
Surface value range
Min Z = 0.000 Max Z = 252.000
Lattice boundary
Xmin = 469049.438 Ymin = 395002.500
Xmax = 534380.188 Ymax = 448487.000
90
-------
Description of Coverage: E30-VIP
Location: DUBO:[DENVER.JAN20.DEV-30]
Summary: E30-VIP is a point coverage which represents, based on a 10% sample of E30-
LAT.LAT, the Lidar "Z" values which were most important in describing the surface. Two
attributes SPOT, representing Lidar "Z" values, and SFCODE are contained in the INFO file
E30-VIP.PAT. SFCODE was a SPOT feature code, coded as one of the following:
2 for a surface maximum or convexity.
-2 for a surface minimum or concavity
1 for an inflection or transition close to a maximum
-1 an inflection or transition feature close to a minimum
0 for a point that is both a local surface maximum and a local surface surface
minimum.
Coverage Type: Lidar
Feature Type: Point
Average RMS error: N/A
Input Saala: N/A
Date Produoed: 11/1/88
DESCRIPTION OF SINGLE PRECISION COVERAGE E30-VIP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 6809
24 bytes of Attribute Data/Point
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy
5.305 N
The coverage has not been Edited
Dangle =
0.000 N
since the last
BUILD or CLEAN.
COVERAGE
BOUNDARY
Xmin =
472197.
906
Ymin =
395217.
313
Xmax =
532018 .
813
Ymax =
448272
219
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH
EXTERNL
DF E30-VIP.BND
ARC0 62DAT
1
16
XX
DF E30-VIP.TIC
ARC0 63DAT
4
12
XX
DF E30-VIP.PAT
ARC064DAT
6809
24
XX
E30-VIP.PAT
6809 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT TYPE N.DEC
ALTERNATE NAME
INDEXED?
1 AREA
4
12
F 3
-
5 PERIMETER
4
12
F 3
-
9 E30-VIP#
4
5
B 0
-
13 E30-VIP-ID
4
5
B 0
-
17 SPOT
4
12
F 3
-
21 SFCODE
4
5
B 0
-
91
-------
E30-VIF Continued.
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
7/20/88 17:46 1 49 768 VIP E30-LAT E30-VIP 10
3/2 6/90 11: 2 0 3 98 EXTERNALALL
3/26/90 14:52 13 242 10093 export cover E30-VIP dubl:[pearl.denver]J20-E30-VIP.eOO
92
-------
Daaaxiption of Covarag*: E30-VT
Location: DUBO:[DENVER.JAN20.DEV-30]
Summary: A TIN created from coverage E30-VIP using a proximal sampling distance of 1500
meters.
Covaraga Typa: Lidar
7*atur« Typa: TIN
Average RMS arror: N/A
Input Soala: N/A
Data Produced: 11/1/88
TIN DBSCRIPTION FOR B30-VT
Tin Topology-
Nodes
Hull nodes
270
20
Triangles = 518
Surface value range
Min Z
0.000
Max Z
= 252.000
Tin Boundary
Xmin = 472985.031
Xmax = 531494.125
Ymin = 395217.313
Ymax = 448272.219
LOO 03/27/90
Date Time Elap CPU I/O Command
min sec opr
7/20/88 17:46 1 30 360 ARCTIN E30-VIP E30-VT POINT SPOT # 2250.0
3/26/90 11: 2 0 3 127 EXTERNALALL
3/26/90 14:53 1 6 227 export cover E30-VT dubl:[pearl.denver]J20-E30-VT.eOO
93
-------
Deaaription o£ Coverage: E30-VT-HULL
Location: DUBO :[DENVER.JAN20.DEV-30]
Summary: A coverage representing the boundary extent of TIN E30-VT. This coverage was used
to set mapextents for plotting and creating views.
Coverage Type: Lidar
Feature Type: Polygon
Averag* RMS tiror: N/A
Input Saale: N/A
Data Produced: 11/1/88
DESCRIPTION OF SIN6LE PRECISION COVERAGE E30-VT-HULL
ARCS
Area = 20
Segments = 20
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 2
Polygon Topology is present.
16 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy
Dangle
5.305 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
472985.031
531494.125
Ymin =
Ymax =
395217.313
448272.219
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E30-VT-HULL.BND
DF E30-VT-HULL.TIC
DF E30-VT-HULL.PAT
ARC041DAT
ARC042DAT
ARC043DAT
16 XX
12 XX
16 XX
E30-VT-HULL.PAT
3 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE N.DEC ALTERNATE NAME
INDEXED?
1
AREA
4
12
F 3
-
5
PERIMETER
4
12
F 3
-
9
E30-VT-HULL#
4
5
B 0
-
13
E30-VT-HULL-ID
4
5
B 0
-
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
8/29/88 10: 6 1 9 523 TINARC E30-VT E30-VT-HULL HULL
3/26/90 11: 2 0 2 91 EXTERNALALL
3/26/90 14:52 1 8 342 export cover E30-VT-HULL
dubl:[pearl.denver]J20-E30-VT-HULL.eOO
94
-------
Daaaxiption of Coverage: E30-VTC
Location: DUBO:[DENVER.JAN20.DEV-30]
Summary: A Lidar contour coverage at intervals of 10 Lidar Units. E30-VTC was interpolated
from E30-VT. Contours range from 10 to 250 Lidar Units.
Coverage Type: Lidar
Feature Type: Line
Average RMS arror: N/A
Input Soala: N/A
Data Produced: 11/1/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE E30-VTC
ARCS
POLYGONS
Arcs =
Segments =
32 bytes of Arc
286
12838
Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY
FEATURES
Label Points = 0
TOLERANCES
Tics =
Annotations =
Links =
STATUS
4
0
0
Fuzzy =
Dangle =
5.304 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
472990.875
531488.250
Ymin =
Ymax =
395222.625
44S266.906
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH
EXTERNL
DF E30-VTC.BND
DF E30-VTC.TIC
DF E30-VTC.AAT
ARC05 9DAT
ARC060DAT
ARC061DAT
1 16
4 12
286 32
XX
XX
XX
E30-VTC.AAT
286 Records Selected.
COLUMN
ITEM NAME
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
1
FNODE#
4 5
B
0
-
5
TNODE#
4 5
B
0
-
9
LPOLY#
4 5
B
0
-
13
RPOLY#
4 5
B
0
-
17
LENGTH
4 12
F
3
-
21
E30-VTC#
4 5
B
0
-
25
E30-VTC-ID
4 5
B
0
-
29
LIDAR
4 12
F
3
-
LOG 03/27/90
Date
Time
Elap
CPU
I/O
Command
min
sec
opr
7/20/88
17:52
6
320
550
TINCONTOUR E30-VT E30-VTC 10 0 LIDAR SMOOTH
3/26/90
11: 3
0
2
97
EXTERNALALL
3/26/90
14 :57
4
77
3680
export cover E30-VTC dubl: [pearl.denver]J20-E30-VTC
95
-------
Nam* of Lattiaa: E30-VTL.LAT
Location: DISK$USER3:[DENVER.JAN20.DEV-30]
Summary: A LATTICE created from TIN E30—VT. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E30-VTL.LAT was used to create polygon coverage E30-VTLP.
Covaraga Type: Lidar
Feature Type: LATTICE
Average RMS error: N/A
Input Saale: N/A
Data Produced: 11/2/88
LATTICE DESCRIPTION FOR B30-VTL.LAT
Lattice size and origin
Points in X/Y = 250 250 Origin
-------
Deaaciption of Coverage: E30-VTLP
Loeation: DUBO:[DENVER.JAN20.DEV-30]
Summary: A polygon coverage representing Lidar backscatter based on 5 Lidar Unit
intervals. Interpolated from LATTICE E30-VTL using the INFO lookup table LIDAR2_LKUP.
Lidar ranges from 5 to a maximum value of 2 60.
Coverage Type: Lidar
Feature Type: Polygon
Average RMS arror: N/A
Input. Soala: N/A
Data Produced: 11/1/88
DESCRIPTION OF SINGLE PRECISION COVERAGE K30-VTLP
ARCS
Arcs = 12961
Segments = 43845
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 5803
Polygon Topology is present.
23 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points = 5802 Tics = 4
Annotations = 0
Links =» 0
TOLERANCES STATUS
Fuzzy =
Dangle =
5.327 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/27/90
TYPE NAME
472985 .031
531729.125
Ymin «=
Ymax =
INTERNAL NAME
395217.313
448485.281
NO. RECS LENGTH EXTERNL
DF E 3 0-VTLP.BND
DF E30-VTLP.TIC
DF E30-VTLP.PAT
ARC05 6DAT
ARC057DAT
ARC058DAT
1
4
5803
16
12
23
XX
XX
XX
E30-VTLP.PAT
5803 Records Selected.
COLUMN
1
5
9
13
17
21
ITEM NAME
AREA
PERIMETER
E30-VTLP*
E30-VTLP-ID
RANGE-CODE
RNGE
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
12
12
5
5
5
3
F
F
B
B
B
I
LOG 03/27/90
Date Time Elap CPU I/O
min sec opr
Command
7/20/88 18:59 66
3/26/90 11: 3 0
3/26/90 15:27 30
631 59026 LATTICEPOLY E30-VTL E30-VTLP RANGE LIDAR2_LKUP
2 96 EXTERNALALL
804 42395 export cover E30-VTLP dubl:[pearl.denver]J20-E30-VTLP.eOO
97
-------
Daaoription of Coverage: E30-RANGE
Location: DUBO:[DENVER.JAN20.DEV-30]
Summary: E30-RANGE represents Lidar intensities at 9 specific ranges coded as: 30, 60,
95, 125, 160, 190, 225, 250 and > 250. E30-RANGE was dissolved from E30-VTLP based on
these nine Lidar intensities.
Covarag* Typa: Lidar
Faatura Type: Polygon
Average RMS error: N/A
Input Saala: N/A
Data Produoed: 11/2/88
DESCRIPTION Or SINGLE PRECISION COVERAGE S30-RANGE
ARCS
Arcs = 122
Segments = 8076
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 66
Polygon Topology is present.
19 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
66
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy
Dangle
5.305 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
473220.000
531494.125
Ymin —
Ymax =
395430.375
448485 .281
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E30-RANGE.PAT
DF E30-RANGE.BND
DF E30-RANGE.TIC
ARC04 9DAT
ARC050DAT
ARC054DAT
66
1
4
19 XX
16 XX
12 XX
E30-RANGE.PAT
66 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E30-RANGE#
4
5
B
0
-
13
E30—RANGE—ID
4
5
B
0
-
17
RNGE
3
3
I
-
-
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
8/24/88 16:51 66 372 59185 DISSOLVE E30-VTLP E30-RANGE RNGE
3/26/90 11: 2 0 2 96 EXTERNALALL
3/26/90 14:38 3 52 2496 export cover E30-RANGE
dubl:[pearl.denver]J20-E30-RANGE.eOO
98
-------
Description ot Covaraga: E30-DEM0TIN
Location: DUBO:[DENVER.JAN20.DEV-30]
Summary: A coverage which represents the TIN structure of E30-VT. The DBC demo use9 this
coverage for display purposes.
Covaraga Typa: Lidar
Faitura Typa: Line
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produaad: 10/27/88
DESCRIPTION Of SINGLE PRECISION COVERAGE E30-DEM0TIN
ARCS
POLYGONS
Arcs = 787
Segments = 787
56 bytes of Arc Attribute Data
POINTS
Label Points = 0
TOLERANCES
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics
Annotations
Links
STATUS
Fuzzy =
Dangle =
5.305 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/27/90
COVERAGE BOUNDARY
472985.031 Ymin
531494.125 Ymax
395217.313
448272.219
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E30-DEMOTIN.BND
DF E30-DEMOTIN.TIC
DF E30-DEMOTIN.AAT
ARC035DAT
ARC036DAT
ARC038DAT
1
4
787
16 XX
12 XX
56 XX
E30-DEMOTIN.AAT
787 Records Selected.
COLUMN ITEM NAME
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
1
FNODE#
4 5
B
0
-
5
TNODE#
4 5
B
0
-
9
LPOLY#
4 5
B
0
-
13
RPOLY#
4 5
B
0
-
17
LENGTH
4 12
F
3
-
21
E30-DEMOTIN#
4 5
B
0
-
25
E30-DEMOTIN-ID
4 5
B
0
-
29
PERCENT SLOPE
4 12
F
3
-
33
LSLOPE
4 12
F
3
-
37
RSLOPE
4 12
F
3
-
41
LASPECT
4 12
F
3
-
45
RASPECT
4 12
F
3
-
49
ZFROM
4 12
F
3
-
53
ZTO
4 12
F
3
-
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
99
-------
10/26/88 17:20 1 16
1392 TINARC E30-VT E30-SHOWTIN LINE PERCENT
100
-------
II. DEV-50 (Lidar aurfacas ganaratad basad on 50 matars AGL)
Daaaription of Covaraga: E50_APP
location: DISK$USER3:[DENVER.JAN20.DEV-50]
Summary: E50_APP represents Lidar return values collected 1/20/88 at 50 meters AGL from
11:45 to 02:30 PM. Mission data was organized by transect and was obtained from data file
[denver.exe]DB3.GND. Data was generated from locational values collected at time of
mission.
Covaraga Typa: Lidar
Faatura Typa: Point
Input Scala: N/A
Digitized by: N/A
Data Produoad: 11/1/88
DESCRIPTION OF SINGLE PRECISION COVERAGE E50 APP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 3923
22 bytes of Attribute Data/Point
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
5.348 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
469049.438
534380.188
Ymin =
Ymax =
395002.750
448487.063
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E50_APP.PAT
DF E50_APP.BND
DF E50 APP.TIC
ARC03 2D AT
ARC036DAT
ARC040DAT
3923
1
4
22 XX
16 XX
12 XX
E50_APP.PAT
3923 Records Selected.
COLUMN ITEM NAME
1 AREA
5 PERIMETER
9 E50_APP#
13 E50_APP-ID
17 LIDAR
20 FLIGHT
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
12
12
5
5
3
3
F
F
B
B
I
I
LOG 03/27/90
Date Time Elap CPU I/O
min sec opr
Command
3/26/90 13:39 3
3/26/90 13:40 1
3/26/90 16:59 5
77 2157 APPEND E50_APP POINT FEATURES
29 362 BUILD E50_APP POINT
128 5532 export cover E50_APP dubl:[pearl.denver]J20-E50_APP.eOO
101
-------
Description of Covaraga: E50-TIN
Location: DISKSUSER3:[DENVER.JAN20.DEV-50]
Sunmary: A TIN created from E50_APP using a proximal sampling distance of 1000 meters.
E50-TIN is the first surface model in a series of surface generations.
Covaraga Typa: Lidar
Faatura Typa: TIN
Avaraga RMS arror: N/A
Input Soala: N/A
Data Froduoad: 7/20/88
riH DESCRIPTION FOR E50-TIN
Tin Topology
Nodes
Hull nodes
168
11
Triangles = 323
Surface value range
Min Z
0 .000
Max Z
260.000
Tin Boundary
Xmin = 469049.438
Xmax = 534380.188
Ymin = 395002.750
Ymax = 448487.031
LOO 03/27/90
Date Time Elap CPU I/O Command
min sec opr
7/20/88 11:54 2 28 1084 ARCTIN E50_APP E50-TIN POINT LIDAR # 2250
3/26/90 11: 6 0 3 137 externalall
102
-------
Mara* of Lattioa: E50-LAT.LAT
Location: DISK$USER3:[DENVER.JAN20.DEV-50]
Summary: A LATTICE created from TIN E50-TIN. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E50-LAT.LAT was used to create the VIP coverage E50-VIP.
Covaraga Typa: Lidar
Featura Typa: LATTICE
Avarag* SMS arcox: N/A
Input Soala: N/A
Data Produaad: 11/2/88
LATTICE DESCRIPTION FOR E50-LAT.LAT
Lattice size and origin
Points in X/Y = 250 250 Origin (x,y)= 469049.438 395002.750
Lattice distance between points
Distance in X = 262.372 Distance in Y = 214.796
Surface value range
Min Z = 0.000 Max Z = 249.092
Lattice boundary
Xmin = 469049.438 Ymin = 395002.750
Xraax = 534380.188 Ymax = 448487.031
103
-------
Description of Covaraga: E50-VIP
Location: DISK$USER3:[DENVER.JAN20.DEV-50]
Summary: E50-VIP is a point coverage which represents, based on a 15% sample of E50-
LAT.LAT, the surface. Attributes SPOT represent surface Z values, and SFCODE was a SPOT
feature code, coded as one of the following:
2 for a surface maximum or convexity.
-2 for a surface minimum or concavity
1 for an inflection or transition close to a maximum
-1 an inflection or transition feature close to a minimum
0 for a point that is both a local surface maximum and a local surface surface
minimum.
Covaraga Typa: Lidar
Faatura Typa: Point
Avaraga RMS arror: N/A
Input Soala: N/A
Data Produaad: 7/20/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE E50-VIP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 6457
24 bytes of Attribute Data/Point
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
5.305 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
471410.781
533855.438
Ymin =
Ymax =
395217.531
448272.250
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E50-VIP.BND
DF E50-VIP.TIC
DF E50-VIP.PAT
ARC03 9DAT
ARC041DAT
ARC042DAT
1
4
6457
16
12
24
XX
XX
XX
E50-VIP.PAT
6457 Records Selected.
COLUMN
ITEM NAME
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
1
AREA
4 12
F
3
-
5
PERIMETER
4 12
F
3
-
9
E50-VIP#
4 5
B
0
-
13
E50-VIP-ID
4 5
B
0
-
17
SPOT
4 12
F
3
-
21
SFCODE
4 5
B
0
-
104
-------
S50-VIP Continued...
LOG 03/27/90
Date Time Elap CPU I/O Command
min
sec
opr
7/20/88
12:
2
4
50
743
VIP E50-LAT E50-VIP 10
3/26/90
11:
6
0
2
83
externalall
3/26/90
16:
0
11
22B
9570
export cover E50-VIP dubl:[pearl.denver]J20-E50-VIP.eOO
105
-------
Daaaription of Covaraga: E50-VT
Location: DISK$USER3:[DENVER.JAN20.DEV-50]
Summary: A TIN created from coverage E50-VIP using a proximal sampling distance of 1500
meters.
Covaraga Typ«: Lidar
Faatura Typ«: TIN
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produced: 11/1/88
TIM DESCRIPTION FOR K50-VT
Tin Topology
Nodes
Hull nodes
- 275
= 21
Triangles = 527
Surface value range
Min Z
0 .000
Max Z
249.092
Tin Boundary
Xmin = 471410.781
Xmax = 533855.438
Ymin = 395217.531
Ymax = 448272.250
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
7/20/88 12: 4 1 32 360 ARCTIN E50-VIP E50-VT POINT SPOT # 2250
3/26/90 11: 6 0 2 119 externalall
3/26/90 16: 10 6 221 export cover E50-VT dubl:[pearl.denver]J20-E50-VT.e00
106
-------
Daaaription ot Covaraga: E50-VT-HULL
Location: DISK$USER3:[DENVER.JAN20.DEV-50]
Summary: A coverage representing the boundary extent of TIN E50-VT. This coverage was used
to set mapextents for plotting and creating views.
Covaraga Typa: Lidar
Feature Typa: Polygon
Avaraga RMS arror: N/A
Input Soala: N/A
Data Produaad: 11/1/8 8
DESCRIPTION OT SINGLE PRECISION COVERAGE E50-VT-H0LL
ARCS
Arcs = 21
Segments = 21
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 2
Polygon Topology is present.
16 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
TOLERANCES
Fuzzy =
Dangle =
Tics
Annotations
Links
STATUS
5.305 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/27/90
TYPE NAME
471410.781
533855.438
Ymin =
Ymax =
INTERNAL NAME
395217.531
448272.250
NO. RECS LENGTH EXTERNL
DF E50-VT-HULL.BND
DF E50-VT-HULL.TIC
DF E50-VT-HULL.PAT
E50-VT-HULL.PAT
3 Records Selected.
ARC022DAT
ARC023DAT
ARC02 9DAT
16
12
16
XX
XX
XX
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E50-VT-HULL#
4
5
B
0
-
13
E50-VT-HULL-ID
4
5
B
0
-
LOG 03/27/90
Date
Time
Elap
CPU
I/O
Command
min
sec
opr
8/30/88
19:33
1
10
903
tinarc e50-vt e50-vt-hull
3/26/90
11: 6
0
2
82
externalall
3/26/90
16: 0
0
8
341
export cover E50-VT-HULL
dubl:[pearl.denver]J20-E50-VT-HULL.eOO
107
-------
Dasoription of Covaraga: E50-VTC
Location: DISK$USER3:[DENVER.JAN20.DEV-50]
Summary: A Lidar contour coverage at intervals of 10 Lidar Units. E50-VTC was interpolated
from E50-VT. Contours range from 10 to 240 Lidar Units.
Coverage Type: Lidar
Ftaturt Typa: Line
Avaraga RMS error: N/A
Input Saala: N/A
Data Produaad: 11/1/88
DESCRIPTION OF SINGLE PRECISION COVERAGE E50-VTC
ARCS
POLYGONS
Arcs = 329
Segments = 12432
32 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
Label Points =
TOLERANCES
SECONDARY FEATURES
Tics =
Annotations =
Links =
STATUS
Fuzzy
5.304 N
The coverage has not been Edited
Dangle =
0.000 N
since the last
BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
471417.031
Ymin =
395222.
844
Xmax =
533849.188
Ymax =
448266.
938
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH
EXTERNL
DF E50-VTC.BND
ARC035DAT
1
16
XX
DF E50-VTC.TIC
ARC037DAT
4
12
XX
DF E50-VTC.AAT
ARC038DAT
329
32
XX
E50-VTC.AAT
329 Records Selected
COLUMN ITEM NAME
WIDTH
OUTPUT TYPE N.DEC
ALTERNATE NAME
INDEXED?
1 FNODE#
4
5
B 0
-
5 TNODE#
4
5
B 0
-
9 LPOLY#
4
5
B 0
-
13 RPOLY#
4
5
B 0
-
17 LENGTH
4
12
F 3
-
21 E50-VTC#
4
5
B 0
-
25 E50-VTC-ID
4
5
B 0
-
29 LIDAR
4
12
F 3
-
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
7/20/88 12:19 16 333 546 TINCONTOUR E50-VT E50-VTC 10 0 LIDAR SMOOTH
3/26/90 11: 6 0 2 83 externalall
3/26/90 16: 3 3 74 3652 export cover E50-VTC dubl:[pearl.denver]J20-E50-VTC.eOO
108
-------
Mara* of Lattiaa: E50-VTL.LAT
Location: DISK$USER3:[DENVER.JAN20.DEV-50]
Summary: A LATTICE created from TIN E50-VT. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E50-VTL.LAT was used to create polygon coverage E50-VTLP.
Covaraga Typa: Lidar
Faatura Typa: LATTICE
Avaraga RMS arror: N/A
Input Soala: N/A
Data Produced: 11/2/88
LATTICE DESCRIPTION FOR E50-VTL.LAT
Lattice size and origin
Points in X/Y = 250 250 Origin (x,y)= 471410.781 395217.531
Lattice distance between points
Distance in X = 250.782 Distance in Y = 213.071
Surface value rang©
Min Z = 0.000 Max Z = 247.910
Lattice boundary
Xmin = 471410.781 Ymin = 395217.531
Xmax = 533855.438 Yrnax = 448272.250
109
-------
Daaaription of Coverag*: E50-VTLP
Location: DISK$USER3:[DENVER.JAN20.DEV-50]
Summary: A polygon coverage representing Lidar backscatter based on 5 Lidar Unit
intervals. Interpolated from LATTICE E50-VTL using the INFO lookup table LIDAR2_LKUP.
Lidar ranges from 5 to a maximum value of 250.
Covarag* Typa: Lidar
Faatura Typa: Polygon
Avaraga RMS arror: N/A
Input Scsala: N/A
Data Produced: 11/1/88
DESCRIPTION Or SINGLE PRECISION COVERAGE E50-VTLP
ARCS
Arcs = 14145
Segments = 42560
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 6261
Polygon Topology is present.
23 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points
6260
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy
Dangle
5.327 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
471410.781
534106.250
Ymin =
Ymax =
395217.531
448485.313
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E50-VTLP.BND
DF E50-VTLP.TIC
DF E50-VTLP.PAT
ARC030DAT
ARC031DAT
ARC033DAT
1
4
6261
16 XX
12 XX
23 XX
E50-VTLP.PAT
6261 Records Selected.
COLUMN
1
5
9
13
17
21
ITEM NAME
AREA
PERIMETER
E50-VTLP#
E50-VTLP-ID
RANGE-CODE
RNGE
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
12
12
5
5
5
3
F
F
B
B
B
I
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
7/20/88 13:50 87 665 59467 LATTICEPOLY E50-VTL E50-VTLP RANGE LIDAR2_LKUP
3/26/90 11: 6 0 2 82 externalall
3/26/90 16:53 50 895 45250 export cover E50-VTLP dubl:[pearl.denver]J20-E50-VTLP.eOO
110
-------
Description of Covaraga: E50-RANGE
Location: DISK$USER3:[DENVER.JAN20.DEV-50 ]
Summary: E50-RANGE represents Lidar intensities at 9 specific ranges coded as: 30, 60,
95, 125, 160, 190, 225, 250 and > 250. E50-RANGE was dissolved from E50-VTLP based on
these nine Lidar intensities.
Covaraga Typa: Lidar
7aatura Typa: Polygon
Avaraga RMS arror: N/A
Input Scala: N/A
Data Produaad: 11/2/8 8
DESCRIPTION 07 SINGLE PRECISION COVERAGE E50-RANGE
ARCS
Arcs = 189
Segments = 8173
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 94
Polygon Topology is present.
19 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
93
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy
Dangle
0.100 V
1.000 V
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin —
Xmax =
ITEMS 03/27/90
TYPE NAME
471661.563
534106.250
Ymin =
Ymax =
INTERNAL NAME
395430.594
448485.313
NO. RECS LENGTH EXTERNL
DF E50-RANGE.PAT
DF E50-RANGE.BND
DF E50-RANGE.TIC
ARC017DAT
ARC025DAT
ARC026DAT
94
1
4
19 XX
16 XX
12 XX
E50-RANGE.PAT
94 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT TYPE
N.DEC ALTERNATE NAME
INDEXED?
1 AREA
4
12
F
3
-
5 PERIMETER
4
12
F
3
-
9 E50-RANGE#
4
5
B
0
-
13 E50-RANGE-ID
4
5
B
0
-
17 RNGE
3
3
I
-
-
LOG 03/27/90
Date Time Elap
CPU
I/O
Command
min
sec
opr
8/30/88 22:47 128
429
70439
DISSOLVE
E50-
¦VTLP E50-RANGE RNGE
8/31/88 8:49 3
129
2130
CLEAN E50
-RANGE # 1 .1
3/26/90 11: 6 0
2
98
externalall
3/26/90 15:49 3
55
2653
export cover
E50-RANGE
dubl:[pearl.denver]J20
-E5C
i-RANGE.eOO
111
-------
Hun* of Covaraga: E50-DEMOTIN
Location: DISK$USER3:[DENVER.JAN20.DEV-50]
Summary: A coverage which represents the TIN structure of E50-VT. The DBC demo uses this
coverage for display purposes.
Coverage Type: Lidar
Feature Type: Line
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produoad: 3/28/90
DESCRIPTION 07 SINGLE PRECISION COVERAGE B50-DEM0TIN
ARCS
POLYGONS
Arcs = 801
Segments = 801
56 bytes of Arc Attribute Data
POINTS
Label Points = 0
TOLERANCES
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
5.305 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/29/90
TYPE NAME
471410 .781
533855.438
Ymin =
Ymax —
INTERNAL NAME
395217.531
448272.250
NO. RECS LENGTH EXTERNL
DF E50-DEMOTIN.BND
DF E50-DEMOTIN.AAT
DF E50-DEMOTIN.TIC
E50-DEMOTIN.AAT
801 Records Selected.
ARC059DAT
ARC060DAT
ARC062DAT
1
801
4
16 XX
5 6 XX
12 XX
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE N,
.DEC ALTERNATE NAME
INDEXED?
1
FNODE#
4
5
B
0
-
5
TNODE#
4
5
B
0
-
9
LPOLY#
4
5
B
0
-
13
RPOLY#
4
5
B
0
-
17
LENGTH
4
12
F
3
-
21
E50-DEMOTIN*
4
5
B
0
-
25
E50-DEMOTIN-ID
4
5
B
0
-
29
PERCENT SLOPE
4
12
F
3
-
33
LSLOPE
4
12
F
3
-
37
RSLOPE
4
12
F
3
-
41
LASPECT
4
12
F
3
-
45
RASPECT
4
12
F
3
-
49
ZFROM
4
12
F
3
-
53
ZTO
4
12
F
3
-
LOG 03/29/90
Date Time Elap CPU I/O Command
112
-------
min sec opr
3/28/90 12:43 0 13 904 tinarc e50-vt e50-demotin line percent
113
-------
III. DEV-60 (Lidar surfaces generated based on 60 meters AGL)
Description of Covartg*: E60_APP
Location: DUBO:[DENVER.JAN20.DEV-60]
Summary: E60_APP represents Lidar return values collected 1/20/88 at 60 meters AGL from
11:45 to 02:30 PM. Mission data was organized by transect and was obtained from data file
[denver.exe]DB3.GND. Data was generated from locational values collected at time of
mission.
Covaraga Typa: Lidar
Faatura Typa: Point
Input Soala: N/A
Digitized by: N/A
Data Produced: 11/1/88
DESCRIPTION Or SINGLE PRECISION COVERAGE E60 APP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 3923
22 bytes of Attribute Data/Point
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
5.348 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
469049.438
534380 .188
Ymin =
Ymax =
395002.500
448487.000
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E60_APP.PAT
DF E60_APP.BND
DF E60 APP.TIC
ARC050DAT
ARC051DAT
ARC052DAT
3923
1
4
22
16
12
XX
XX
XX
E60_APP .PAT
3923 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC
ALTERNATE NAME INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E60 APP#
4
5
B
0
-
13
E60 APP-ID
4
5
B
0
-
17
LIDAR
3
3
I
-
-
20
FLIGHT
3
3
I
-
-
LOG 03/27/90
Date Time Elap CPU 1/0 Command
min sec opr
7/20/88 11:47 0 4
7/20/88 11:49 0 4
212 CREATE E60_APP-UTM
184 RENAME E60 APP-UTM E60 APP
114
-------
3/26/90 11:22 0 2 89 externalall
3/26/90 17:50 4 124 5528 export cover E60_APP dubl:(pearl.denver]J20-E60_APP.eOO
115
-------
Daaoription of Covaraga: E60-TIN
Location: DUBO:(DENVER.JAN20.DEV-60]
Summary: A TIN created from E60_APP using a proximal sampling distance of 1000 meters.
E60-TIN is the first surface model in a series of surface generations.
Covaraga Typa: Lidar
Faatura Type: TIN
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produaad: 7/20/8 8
TIN DESCRIPTION FOR E60-TIN
Tin Topology
Nodes
Hull nodes
168
11
Triangles = 323
Surface value range
Min Z
0.000
Max Z
258.000
Tin Boundary
Xmin = 469049.438
Xmax = 534380.188
Ymin = 395002.500
Ymax = 448487.000
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
7/20/88 13:51 1 26 1078 ARCTIN E60_APP E60-TIN POINT LIDAR # 2250.0
3/26/90 11:21 0 2 122 externalall
116
-------
Mama of Lattiaa: E60-LAT.LAT
Location: DISK$USER3:[DENVER.JAN20.DEV-60]
Summary: A LATTICE created from TIN E60-TIN. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E60-LAT.LAT was used to create the VIP coverage E60-VIP.
Covaraga Typa: Lidar
Faatura Typa: LATTICE
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produced: 11/2/9 8
LATTICE DESCRIPTION FOR E60-LAT.LAT
Lattice size and origin
Points in X/Y = 250 250 Origin (x,y)= 469049.438 395002.500
Lattice distance between points
Distance in X = 262.372 Distance in Y = 214.797
Surface value range
Min Z = 0.000 Max Z = 249.220
Lattice boundary
Xmin = 469049.438 Ymin = 395002.500
Xmax = 534380.188 Ymax = 448487.000
117
-------
Description of Covaraga: E60-VIP
Location: DUBO:[DENVER.JAN20.DEV-60]
Summary: E60-VIP is a point coverage which represents, based on a 15% sample of E60-
LAT.LAT, the surface. Attributes SPOT represent surface Z values, and SFCODE was a SPOT
feature code, coded as one of the following:
2 for a surface maximum or convexity.
-2 for a surface minimum or concavity
1 for an inflection or transition close to a maximum
-1 an inflection or transition feature close to a minimum
0 for a point that is both a local surface maximum and a local surface surface
minimum.
Covaraga Type: Lidar
Faatura Typa: Point
Avaraga RMS arror: N/A
Input Soala: N/A
Data Produced: 7/20/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE E60-VIP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
POINTS
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points = 6689
24 bytes of Attribute Data/Point
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
5.305 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
470623 . 688
533593.063
Ymin
Ymax
395217.313
448272.219
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E60-VIP.BND
DF E60-VIP.TIC
DF E60-VIP.PAT
ARC054DAT
ARC055DAT
ARC056DAT
1
4
6689
16 XX
12 XX
24 XX
E60-VIP.PAT
6689 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E60-VIP#
4
5
B
0
-
13
E60-VIP-ID
4
5
B
0
-
17
SPOT
4
12
F
3
-
21
SFCODE
4
5
B
0
-
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
118
-------
7/20/88 13:54 1 50 751 VIP E60-LAT E60-VIP 10
3/26/90 11:21 0 2 89 externalall
3/26/90 17:10 7 220 9892 export cover E60-VIP dubl:[pearl.denver]J20-E60-VIP.eOO
119
-------
Description of Covaraga: E60-VT
Location: DUBO:[DENVER.JAN20.DEV-60]
Summary: A TIN created from coverage E60-VIP using a proximal sampling distance of 1500
meters.
Covaraga Typa: Lidar
Faatura Typa: TIN
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produaad: 11/1/8 8
TIM DESCRIPTION FOR S60-VT
Tin Topology
Nodes
Hull nodes
292
25
Triangles = 557
Surface value range
Min Z
0 .000
Max Z
249.220
Tin Boundary
Xmin = 471673.156
Xrnax = 533593.063
Ymin = 395432.094
Ymax = 448272.219
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
7/20/88 13:54 1 30 355 ARCTIN E60-VIP E60-VT POINT SPOT # 2250.0
3/26/90 11:22 0 2 122 externalall
3/26/90 17:10 0 5 222 export cover E60-VT dubl:[pearl.denver]J20-E60-VT.eOO
120
-------
Description of Coverage: E60-VT-HULL
Loaation: DUBO:[DENVER.JAN20-DEV-60]
Summary: A coverage representing the boundary extent of TIN E60-VT. This coverage was used
to set mapextents for plotting and creating views.
Coverage Typ«: Lidar
Feature Type: Polygon
Avcrag* RMS «rror: N/A
Input Scale: N/A
Data Produced: 11/1/88
DESCRIPTION OF SIHGLE PRECISION COVERAGE E60-VT-HULL
ARCS
Arcs = 25
Segments = 25
0 bytes of Arc Attribute Data
POINTS
Label Points = 0
TOLERANCES
POLYGONS
Polygons = 2
Polygon Topology is present.
16 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics =
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
5.284 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/27/90
TYPE NAME
471673.156
533593.063
Ymin =
Ymax =
INTERNAL NAME
395432.094
448272.219
NO. RECS LENGTH EXTERNL
DF E60-VT-HULL.BND
DF E60-VT-HULL.TIC
DF E60-VT-HULL.PAT
ARC039DAT
ARC04 0DAT
ARC042DAT
16 XX
12 XX
16 XX
E60-VT-HULL.PAT
3 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E60-VT-HULL#
4
. 5
B
0
-
13
E60-VT-HULL-ID
4
5
B
0
-
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
8/31/88 9:16 1 12 1276 tinarc e60-vt e60-vt-hull hull
3/26/90 11:21 0 2 83 externalall
3/26/90 17:10 0 8 355 export cover E60-VT-HULL
dubl:[pearl.denver]J20-E60-VT-HULL.eOO
121
-------
Description of Covaraga: E60-VTC
Location: DUBO:[DENVER.JAN20.DEV-60]
Summary: A Lidar contour coverage at intervals of 10 Lidar Units. E60-VTC was interpolated
from E60-VT. Contours range from 10 to 230 Lidar Units.
Coverage Type: Lidar
Faatura Typa: Line
At*rag* SMS arror: N/A
Input Saala: N/A
Data Produoad: 11/1/68
DESCRIPTION 07 SIHGLE PRECISION COVERAGE E60-VTC
ARCS
POLYGONS
Arcs =
325
Polygons = 0
Segments =
13507
There is NO Polygon Topology.
32 bytes of Arc Attribute Data
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points =
0
Tics = 4
Annotations = 0
Links = 0
TOLERANCES
STATUS
Fuzzy =
5.283 N
The coverage has not been Edited
Dangle =
0.000 N
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
471679.344
Ymin = 395437.375
Xmax =
533586.875
Ymax = 448266.938
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME NO. RECS LENGTH
EXTERNL
DF E60-VTC.BND
ARC047DAT 1 16
XX
DF E60-VTC.TIC
ARC04 8DAT 4 12
XX
DF E60-VTC.AAT
ARC04 9DAT 325 32
XX
E60-VTC.AAT
325 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
1 FNODE#
4
5
B 0
-
5 TNODE#
4
5
B 0
-
9 LPOLY#
4
5
B 0
-
13 RPOLY#
4
5
B 0
-
17 LENGTH
4
12
F 3
-
21 E60-VTC#
4
5
B 0
-
25 E60-VTC-ID
4
5
B 0
-
29 LIDAR
4
12
F 3
-
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
7/20/88 14: 1 6 340 552 TINCONTOUR E60-VT E60-VTC 10 0 LIDAR SMOOTH
3/26/90 11:22 0 2 89 externalall
3/26/90 17:13 2 77 3882 export cover E60-VTC dubl:[pearl.denver]J20-E60-VTC.eOO
122
-------
Name of Lattice: E60-VTL.LAT
Loaation: DISK$USER3:[DENVER.JAN20.DEV-60]
Summary: A LATTICE "created from TIN E60-VT. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E60-VTL.LAT was used to create polygon coverage E60-VTLP.
Coverage Type: Lidar
Feature Type: LATTICE
Average RMS error: N/A
Input Saale: N/A
Date Produoed: 11/2/8 8
LATTICE DESCRIPTION FOR K60-VTL.LAT
Lattice size and origin
Points in X/Y = 250 250 Origin (x,y)= 471673.156 395432.094
Lattice distance between points
Distance in X = 248.674 Distance in Y = 212.209
Surface value range
Min Z = 0.000 Max Z = 233.903
Lattice boundary
Xmin = 471673.156 Ymin = 395432.094
Xmax = 533593.063 Ymax = 448272.219
123
-------
Daaaription of Covaraga: E60-VTLP
Location: DUBO:[DENVER.JAN20.DEV-60]
Summary: A polygon coverage representing Lidar baokscatter baaed on 5 Lidar Unit
intervals. Interpolated from LATTICE E60-VTL using the INFO lookup table LIDAR2 LKUP.
Lidar ranges from 5 to a maximum value of 230.
Covaraga Typa: Lidar
Faatura Typa: Polygon
Av«rag« RMS error: N/A
Input Seal*: N/A
Data Produaad: 11/1/88
DESCRIPTION OF SINGLE PRECISION COVBRAGX EGO-VTLP
ARCS
POLYGONS
Arcs = 15674
Segments = 45961
0 bytes of Arc Attribute Data
POINTS
Label Points —
6917
Polygons = 6918
Polygon Topology is present.
23 bytes of Polygon Attribute Data
SECONDARY FEATURES
TOLERANCES
Tics
Annotations =
Links =
STATUS
Fuzzy =
Dangle =
5.305 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/27/90
TYPE NAME
471673.156
533841.750
Ymin =
Ymax =
INTERNAL NAME
395432.094
448484.438
NO. RECS LENGTH EXTERNL
DF E60-VTLP.BND
DF E60-VTLP.TIC
DF E60-VTLP.PAT
ARC043DAT
ARC04 4DAT
ARC04 6DAT
1
4
6918
16 XX
12 XX
23 XX
E60-VTLP.PAT
6918 Records Selected.
COLUMN
1
5
9
13
17
21
ITEM NAME
AREA
PERIMETER
E60-VTLP#
E60-VTLP-ID
RANGE-CODE
RNGE
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
LOG 03/27/90
Date
Time Elap
min
CPU
sec
I/O
opr
12
12
5
5
5
3
Command
F
F
B
B
B
I
7/20/88 16:18 136 712 61467 LATTICEPOLY E60-VTL E60-VTLP RANGE LIDAR2_LKUP
3/26/90 11:22 0 2 90 externalall
3/26/90 17:46 33 932 49830 export cover E60-VTLP dubl:[pearl.denver]J20-E60-VTLP.eOO
124
-------
Description of Coverage: E60-RANGE
Loaation: DUBO:(DENVER.JAN20.DEV-60]
Summary: E50-RANGE represents Lidar intensities at 9 specific ranges coded as: 30, 60,
95, 125, 160, 190, 225, 250 and > 250. E50—RANGE was dissolved from E50-VTLP based on
these nine Lidar intensities.
Coverage Type: Lidar
Feature Type: Polygon
Average RMS error: N/A
Input. Scale: N/A
Data Produced: 11/2/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE E60-RANCE
ARCS
POLYGONS
Arcs = 140
Segments = 8881
0 bytes of Arc Attribute Data
POINTS
Label Points =
73
TOLERANCES
Polygons = 73
Polygon Topology is present.
19 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics =
Annotations =
Links —
STATUS
Fuzzy
Dangle
5.305 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
471921.844
533593.063
Ymin =
Ymax =
395432.094
448484.438
ITEMS 03/27/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E60-RANGE.PAT
DF E60-RANGE.BND
DF E60-RANGE.TIC
ARC034DAT
ARC035DAT
ARC036DAT
73
1
4
19 XX
16 XX
12 XX
E60-RANGE.PAT
73 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E60-RANGE#
4
5
B
0
-
13
E60-RANGE-ID
4
5
B
0
-
17
RNGE
3
3
I
-
-
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
8/31/88 16: 8 122 507 79502 DISSOLVE E60-VTLP E60-RANGE RNGE
3/26/90 11:21 0 2 82 externalall
3/26/90 17: 3 2 53 2715 export cover E60-RANGE
dubl:[pearl.denver]J20-E60-RANGE.eOO
125
-------
Daaaription of Covaraga: E60-DEMOTIN
Location: DUBO:[DENVER.JAN20.DEV-60]
Summary: A coverage which represents the TIN structure of E60-VT. The DBC demo uses this
coverage for display purposes.
Covaraga Typa: Lidar
Faatura Typa: Line
Avarag* RMS arror: N/A
Input Scala: N/A
Data Producad: 10/28/88
DESCRIPTION Or SINGLE PRECISION COVERAGE E60-DEM0TIN
ARCS
Arcs = 848
Segments = 848
56 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points
TOLERANCES
Fuzzy
Dangle
Xmin =
Xmax ~
ITEMS 03/27/90
TYPE NAME
Tics
Annotations
Links
STATUS
471673.156
533593.063
5.284 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Ymin =
Ymax =
INTERNAL NAME
395432.094
448272.219
NO. RECS LENGTH EXTERNL
DF E60-DEMOTIN.BND
DF E60-DEMOTIN.TIC
DF E60-DEMOTIN.AAT
ARC031DAT
ARC032DAT
ARC038DAT
1
4
848
16 XX
12 XX
56 XX
E60-DEMOTIN.AAT
848 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
FNODE#
4 5
B
0
-
5
TNODE#
4 5
B
0
-
9
LPOLY#
4 5
B
0
-
13
RPOLY#
4 5
B
0
-
17
LENGTH
4 12
F
3
-
21
E60-DEMOTIN*
4 5
B
0
-
25
E60-DEMOTIN-ID
4 5
B
0
-
29
PERCENT SLOPE
4 12
F
3
-
33
LSLOPE
4 12
F
3
-
37
RSLOPE
4 12
F
3
-
41
LASPECT
4 12
F
3
-
45
RASPECT
4 12
F
3
-
49
ZFROM
4 12
F
3
-
53
ZTO
4 12
F
3
-
LOG 03/27/90
Date Time Elap CPU I/O Command
min sec opr
126
-------
10/28/88 10:23 1 13 590 TINARC E60-VT E60-DEMOTIN LINE PERCENT
127
-------
IV. DEV-80 (Lidar aurfiau ganaratad baaad on 80 tnatara ACL) .
Daacripfcion of Covaraga: E80_APP
Loaation: DUBO:[DENVER.JAN20.DEV-80]
Summary: E80_APP represents Lidar return values collected 1/20/88 at 80 meters AGL from
11:45 to 02:30 PM. Mission data was organized by transect and was obtained from data file
[denver.exe]DB3.GND. Data was generated from locational values collected at time of
mission.
Covaraga Typa: Lidar
Faatura Typa: Point
Input Scale: N/A
Digitized by: N/A
Data Produaad: 11/1/88
DESCRIPTION Or SINGLE PRECISION COVERAGE EB0 APP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 3923
22 bytes of Attribute Data/Point
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy =
Dangle =
5.348 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
469049.438
534380.188
Ymin =
Ymax =
395002.500
448487.000
ITEMS 03/28/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E80_APP.PAT
DF E80_APP.BND
DF E80 APP.TIC
ARC061DAT
ARC062DAT
ARC063DAT
3923
0
0
22 XX
16 XX
12 XX
E80_APP.PAT
3923 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1 AREA 4 12 F 3
5 PERIMETER 4 12 F 3
9 E80_APP# 4 5 B 0
13 E80_APP-ID 4 5 B 0
17 LIDAR 3 3 1-
20 FLIGHT 3 3 1-
LOC 03/28/90
Date Time Elap CPU I/O Command
min sec opr
7/20/88 13:35 0 4 212 CREATE E80_APP
3/26/90 11:22 0 2 89 EXTERNALALL
128
-------
3/27/90 9:40 6 132 5545 export cover E80_APP dubl:[pearl.denver]J20-E80_APP.eOO
129
-------
Daaaription of Coverage: E80-TIN
Location: DUBO:[DENVER.JAN20.DEV-80]
9ummary: A TIN created from E80_APP using a proximal sampling distance of 1000 meters.
E80-TXN is the first surface model in a aeries of surface generations.
Coverage Type: Lidar
Feature Typa: TIN
Average RMS arror: N/A
Input Saala: N/A
Data Produced: 7/20/88
TIN DESCRIPTION FOR S80-TIN
Tin Topology
Nodes
Hull nodes
166
11
Triangles = 319
Surface value range
Min Z
0.000
Max Z
= 247.000
Tin Boundary
Xmin = 469049.438
Xmax = 534380.188
Ymin = 395002.500
Ymax = 448487.000
LOG 03/28/90
Date Time Elap CPU I/O Command
min sec opr
7/20/88 16:21 2 27 1084 ARCTIN E80_APP E80-TIN POINT LIDAR # 2225.0
3/26/90 11:22 0 3 127 EXTERNALALL
130
-------
Mam* of Lattiaa: ESO-LAT.LAT
Location: DISK$USER3:[DENVER.JAN20.DEV-80]
Summary: A LATTICE created from TIN E80-TIN. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E80-LAT.LAT was used to create the VIP coverage E80-VIP.
Covarag* Typ«: Lidar
Faatura Typa: LATTICE
Avaraga RMS arror: N/A
Input Saala: N/A
Data Froduaad: 11/2/88
LATTICE DESCRIPTION FOR ESO-LAT.LAT
Lattice size and origin
Points in X/Y = 250 250 Origin (x,y)= 469049.438 395002.500
Lattice distance between points
Distance in X = 262.372 Distance in Y = 214.797
Surface value range
Min Z = 0.000 Max Z = 247.000
Lattice boundary
Xmin = 469049.438 Ymin = 395002.500
Xmax = 534380.188 Ymax = 448487.000
131
-------
Description of Covaraga: E80-VIP
Location: DUBO:[DENVER.JAN20.DEV-80]
Summary: E80-VXP is a point coverage which represents, based on a 15% sample of E80-
LAT.LAT, the surface. Attributes SPOT represent surface Z values, and SFCODE was a SPOT
feature code, coded as one of the following:
2 for a surface maximum or convexity.
-2 for a surface minimum or concavity
1 for an inflection or transition close to a maximum
-1 an inflection or transition feature close to a minimum
0 for a point that is both a local surface maximum and a local surface surface
minimum.
Covaraga Typa: Lidar
Faatura Typa: Point
Avaraga RMS arror: N/A
Input Soala: N/A
Data Produoad: 7/20/8 8
DESCRIPTION OF SINGLE PRECISION COVERAGE E80-VIP
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
POINTS
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points = 6870
24 bytes of Attribute Data/Point
TOLERANCES
Tics =
Annotations =
Links =
STATUS
Fuzzy
Dangle
5.305 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xraax =
471935.531
533855.438
Ymin =
Ymax =
395217.313
448272.219
ITEMS 03/28/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E80-VIP.BND
DF E80-VIP.TIC
DF E80-VIP.PAT
ARC064DAT
ARC065DAT
ARC066DAT
1
4
6870
16 XX
12 XX
24 XX
E80-VIP.PAT
6870 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E80-VIP#
4
5
B
0
-
13
E80-VIP-ID
4
5
B
0
-
17
SPOT
4
12
F
3
-
21
SFCODE
4
5
B
0
-
LOG 03/28/90
Date Time Elap CPU I/O
min sec opr
Command
132
-------
7/20/88 16:26 2 52 776 VIP E80-LAT E80-VIP 10
3/26/90 11:22 0 2 94 EXTERNALALL
3/27/90 8:34 8 232 10176 export cover E80-VIP dubl:[pearl-denver]J20-E80-VIP.eOO
133
-------
Description of Covaraga: E8 0-VT
Location: DUBO:[DENVER.JAN20.DEV-80]
Summary: A TIN created from coverage E80-VIP using a proximal sampling distance of 1500
meters.
Covaraga Typa: Lidar
Faatura Typa: TIN
Avaraga RMS arror: N/A
Input Soala: N/A
Data Produoad: 11/1/88
TIN DESCRIPTION TOR B80-VT
Tin Topology
Nodes
Hull nodes
284
28
Triangles = 538
Surface value range
Min Z
0 .000
Max Z
247 .000
Tin Boundary
Xmin = 471935.531
Xmax = 533855.438
Ymin = 395432.094
Ymax = 448272.219
LOG 03/28/90
Date Time Elap CPU
min sec
I/O Command
opr
7/20/88 16:28 1 33 363 ARCTIN E80-VIP E80-VT POINT SPOT # 2225.0
3/26/90 11:22 0 3 127 EXTERNALA1L
3/27/90 8:34 0 5 223 export cover E80-VT dubl:[pearl.denver]J20-E80-VT.eOO
134
-------
Description of Coverage: E8 0-VT-HULL
Location: DUBO:[DENVER.JAN20.DEV-80]
Summary: A coverage representing the boundary extent of TIN E80-VT. This coverage was used
to set mapextents for plotting and creating views.
Coverage Typa: Lidar
Feature Type: Polygon
Average RMS arror: N/A
Input Saala: N/A
Data Produced: 11/1/88
DESCRIPTION OF SINGLE PRECISION COVERAGE E60-VT-HULL
ARCS
Arcs = 28
Segments = 28
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 2
Polygon Topology is present.
16 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy =
Dangle =
5.284 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
471935.531
533855.438
Ymin =
Ymax =
395432.094
448272.219
ITEMS 03/26/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E 8 0-VT-HULL.BND
DF E80-VT-HULL.TIC
DF E80-VT-HULL.PAT
ARC04 8DAT
ARC 0 4 9D AT
ARC050DAT
16 XX
12 XX
16 XX
E80-VT-HULL.PAT
3 Records Selected.
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
E80-VT-HULL#
4
5
B
0
-
13
E80-VT-HULL-ID
4
5
B
0
-
LOG 03/28/90
Date Time Elap CPU 1/0 Command
min sec opr
8/31/88
3/26/90
3/27/90
9:16
2
12
1275
11:22
0
2
90
8:34
0
8
353
dubl:[pearl.denver]J20-E80-VT-HULL.eOO
135
-------
Daaaription of Covaraga: E80-VTC
Location: DUBO:[DENVER.JAN20.DEV-80]
Summary: A Lidar contour coverage at intervals of 10 Lidar Units. E80-VTC was interpolated
from E80-VT. Contours range from 10 to 240 Lidar Units.
Coverage Type: Lidar
Faatura Typa: Line
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produoad: 11/1/88
DESCRIPTION OF SINGLE PRECISION COVERAGE E80-VTC
ARCS
Arcs = 310
Segments = 12806
32 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy =
Dangle =
5.283 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
471941.719
Ymin -
395437.375
Xmax =
533849.250
Ymax -
448266.
938
ITEMS 03/28/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH
EXTERNL
DF E80-VTC.BND
ARC055DAT
1
16
XX
DF E80-VTC.TIC
ARC05 6DAT
4
12
XX
DF E80-VTC.AAT
ARC05 9DAT
310
32
XX
E80-VTC.AAT
310 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPU1
I TYPE N.DEC
ALTERNATE NAME
INDEXED?
1 FNODE#
4
5
B 0
-
5 TNODE#
4
5
B 0
-
9 LPOLY#
4
,5
B 0
-
13 RPOLY#
4
5
B 0
-
17 LENGTH
4
12
F 3
-
21 E80-VTC#
4
5
B 0
-
25 E80-VTC-ID
4
5
B 0
-
29 LIDAR
4
12
F 3
-
LOG 03/28/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
7/20/88 16:39 11 324 564 TINCONTOUR E80-VT E80-VTC 10 0 LIDAR SMOOTH
3/26/90 11:22 0 2 90 EXTERNALALL
3/27/90 8:37 2 73 3696 export cover E80-VTC dubl:[pearl.denver]J20-E80-VTC.eOO
136
-------
Man* of Lattioa: E80-VTL.LAT
Location: DISK$USER3:[DENVER.JAN20.DEV-80]
Summary: A LATTICE created from TIN E80-VT. A LATTICE is a binary system file which is
interpolated from TIN based on starting origin, and number of points in X/Y direction.
E80-VTL.LAT was used to create polygon coverage E80-VTLP.
Covaraga Typa: Lidar
Faatura Typa: LATTICE
Avaraga RMS trior: N/A
Input Saala: N/A
Data Produead: 11/2/88
LATTICE DESCRIPTION FOR ESO-VTL.LAT
Lattice size and origin
Points in X/Y = 250 250 Origin (x,y)= 471935.531 395432.094
Lattice distance between points
Distance in X = 248.674 Distance in Y = 212.209
Surface value range
Min Z = 4.422 Max Z = 247.000
Lattice boundary
Xmin = 471935.531 Ymin = 395432.094
Xmax = 533855.438 Ymax = 448272.219
137
-------
Daaaription of Covacaga: E80-VTLP
Location: DUBO:[DENVER.JAN20.DEV-80]
Summary: A polygon coverage representing Lidar backscatter based on 5 Lidar Unit
intervals. Interpolated from LATTICE E80-VTL using the INFO lookup table LIDAR2 LKUP.
Lidar ranges from 5 to a maximum value of 250.
Covarag* Typa: Lidar
Faatura Typa: Polygon
Avaraga RMS trror: N/A
Input Soala: N/A
Data Produced: 11/1/38
DESCRIPTION or SINGLE PRECISION COVERAGE E80-VTLP
ARCS
Arcs = 13801
Segments = 42986
0 bytes of Arc Attribute Data
POINTS
POLYGONS
Polygons = 6041
Polygon Topology is present.
23 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points =
6040
TOLERANCES
Tics
Annotations =
Links =
STATUS
Fuzzy
Dangle
5.305 N
0 . 000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
471935.531
534104.125
Ymin =
Ymax =
395432.094
448484 .438
ITEMS 03/28/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF E80-VTLP.BND
DF E80-VTLP.TIC
DF E 8 0-VTLP.PAT
ARC051DAT
ARC052DAT
ARC054DAT
1
4
6041
16 XX
12 XX
23 XX
E80-VTLP.PAT
6041 Records Selected.
COLUMN
1
5
9
13
17
21
ITEM NAME
AREA
PERIMETER
E80-VTLP#
E80-VTLP-ID
RANGE-CODE
RNGE
WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME
INDEXED?
12
12
5
5
5
3
F
F
B
B
B
I
LOG 03/26/90
Date Time Elap CPU I/O Command
min sec opr
7/20/88 17:42 61 622 60990 LATTICEPOLY E80-VTL E80-VTLP RANGE LIDAR2_LKUP
3/26/90 11:22 0 2 90 EXTERNALALL
3/27/90 9:34 57 868 44376 export cover E80-VTLP dubl:[pearl.denver]J20-E80-VTLP.eOO
138
-------
Description of Coverage: E8 0-RANGE
Location: DUBO:[DENVER.JAN20.DEV-80]
Summary: E80-RANGE represents Lidar intensities at 9 specific ranges coded as: 30, 60,
95, 125, 160, 190, 225, 250 and > 250. E80-RANGE was dissolved from E80-VTLP based on
these nine Lidar intensities.
Coverage Type: Lidar
Feature Type: Polygon
Average RMS error: N/A
Input Scale: N/A
Date Produced: 11/2/88
DESCRIPTION OF SINGLE PRECISION COVERAGE E80-RANGE
ARCS
POLYGONS
Arcs = 158
Segments = 8405
0 bytes of Arc Attribute Data
POINTS
Label Points =
81
TOLERANCES
Polygons = 81
Polygon Topology is present.
19 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics
Annotations
Links
STATUS
Fuzzy =
Dangle =
5.305 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ITEMS 03/26/90
TYPE NAME
472184.219
533855.438
Ymin =
Ymax =
INTERNAL NAME
395432.094
448484.438
NO. RECS LENGTH EXTERNL
DF E80-RANGE.PAT
ARC043DAT
81
19
XX
DF E80-RANGE.BND
ARC044DAT
1
16
XX
DF E80-RANGE.TIC
ARC04 6DAT
4
12
XX
E80-RANGE.PAT
81 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT
TYPE N.DEC
ALTERNATE NAME
INDEXED?
1 AREA
4
12
F 3
-
5 PERIMETER
4
12
F 3
-
9 E80-RANGE#
4
5
B 0
-
13 E80-RANGE-ID
4
5
B 0
-
17 RNGE
3
3
I
-
LOG 03/28/90
Date Time Elap CPU I/O Command
min sec opr
8/31/88 17:41 92 448 70332 DISSOLVE E80-VTLP E80-RANGE RNGE
3/26/90 11:21 0 2 90 EXTERNALALL
3/27/90 8:26 2 51 2660 export cover E80-RANGE
dubl:[pearl.denver]J20-E80-RANGE.eOO
139
-------
Daaaription of Covaraga: E80-DEMOTIN
Location: DUBO:[DENVER.JAN20.DEV-80]
Summary: A coverage which represents the TIN structure of E80-VT. The DBC demo uses this
coverage for display purposes.
Covaraga Typa: Lidar
Faatura Typa: Line
Avaraga RMS error: N/A
Input Saala: N/A
Data Produaad: 10/28/88
DESCRIPTION 07 SINGLE PRECISION COVERAGE E80-DEMOTIN
ARCS
POLYGONS
Arcs = 821
Segments = 821
56 bytes of Arc Attribute Data
POINTS
Label Points = 0
TOLERANCES
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Tics
Annotations
Links
STATUS
Fuzzy
Dangle
5.284 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xrnax =
ITEMS 03/28/90
TYPE NAME
471935.531
533855.438
Ymin
Ymax
INTERNAL NAME
395432.094
448272.219
NO. RECS LENGTH EXTERNL
DF E80-DEMOTIN.BND
DF E80-DEMOTIN.TIC
DF E 8 0-DEMOTIN.AAT
E80-DEMOTIN.AAT
821 Records Selected.
ARC040DAT
ARC04 2DAT
ARC047DAT
1
4
821
16 XX
12 XX
56 XX
COLUMN ITEM NAME WIDTH OUTPUT TYPE N.DEC ALTERNATE NAME INDEXED?
1
FN0DE#
4 5
B
0
-
5
TNODE#
4 5
B
0
-
9
LP0LY#
4 5
B
0
-
13
RPOLY#
4 5
B
0
-
17
LENGTH
4 12
F
3
-
21
E80-DEMOTIN#
4 5
B
0
-
25
E80-DEMOTIN-ID
4 5
B
0
-
29
PERCENT_SLOPE
4 12
F
3
-
33
LSLOPE
4 12
F
3
-
37
RSLOPE
4 12
F
3
-
41
LASPECT
4 12
F
3
-
45
RASPECT
4 12
F
3
-
49
ZFROM
4 12
F
3
-
53
ZTO
4 12
F
3
_
LOG 03/20/90
Date Time Elap CPU I/O Command
min sec opr
140
-------
10/28/88 10:10 1 15 973 TINARC E80-VT E80-DEMOTIN LINE PERCENT
141
-------
V. FLT (January 20, Transact Flight Linaa)
Daaaription of Covaraga: FLIGHT_DBC-U
Location: DUBO:[DENVER.JAN20.FLT]
Summary: Transect flight lines which were used in the interpolation of Lidar surfaces for
the January 20, 1988 mission. Mission coordinates were used to generate the flight lines.
Covaraga Typa: Lidar
Faatura Typa: Line
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produaad: 9/21/8 8
DESCRIPTION OF SIHGL2 PRECISION COVERAGE FLIGHT DBC-U
ARCS
POLYGONS
Arcs = 11
Segments = 3904
4 9 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
SECONDARY FEATURES
Label Points = 205
20 bytes of Attribute Data/Point
TOLERANCES
Tics
Annotations
Links
STATUS
4
14
0
Fuzzy
5.313 N
The coverage has not been Edited
Dangle
¦ = 0.000 N
since the last
BUILD
or CLEAN.
COVERAGE BOUNDARY
Xinin =
469185.281
Ymin =
395361.500
Xmax =
534244.250
Ymax =
448486.500
ITEMS
03/26/90
TYPE
NAME
INTERNAL NAME
NO.
RECS LENGTH
EXTERNL
DF
FLIGHT DBC-U.AAT
ARC030DAT
11 49
XX
DF
FLIGHT DBC-U.TXT
ARC034DAT
14 404
DF
FLIGHT DBC-U.PAT
ARC035DAT
205 20
XX
DF
FLIGHT_DBC-U.BND
ARC036DAT
1 16
XX
DF
FLIGHT DBC-U.TIC
ARC037DAT
4 12
XX
FLIGHT_DBC-U.AAT
11 Records Selected.
COLUMN
ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC ALTERNATE NAME
INDEXED?
1
FNODE#
4
5
B
0
-
5
TNODE#
4
5
B
0
-
9
LPOLY#
4
5
B
0
-
13
RPOLY#
4
5
B
0
-
17
LENGTH
4
12
F
3
-
21
FLIGHT DBC-U#
4
5
B
0
-
25
FLIGHT DBC-U-ID
4
5
B
0
-
29
TIN FLAG
3
3
I
-
-
32
FLIGHT
3
3
I
-
-
35
TAPE
5
5
C
-
-
40
START.TIME
5
5
N
2
-
45
END.TIME
5
5
N
2
-
142
-------
FLIGHT DBC-U Continued...
LOG 03/28/90
Date
Time Elap
min
CPU
sec
I/O
opr
Command
213 CREATE FLIGHT_DBC-U
713 BUILD FLIGHT_DBC-U LINE
2 64 UNLOADANNO FLIGHT_DBC-U
164 LOADANNO FLIGHT_DBC-U
161 LOADANNO FLIGHT_DBC-U
152 LOADANNO FLIGHT_DBC-U
108 externalall
2 39 2034
dubl:[pearl.denver]J20-FLIGHT_DBC-U.eOO
7/20/88
14:46
0
3
9/21/88
14:10
1
13
9/21/88
14:15
1
5
9/21/88
14:17
0
2
9/21/88
14 :20
0
2
9/21/88
14:22
0
2
3/26/90
11:35
0
2
3/27/90
9:
: 43
export cover FLIGHT DBC-U
143
-------
Daaaription of Cov«r«g«: FLIGHT_UTM
Location: DUBO:[DENVER.JAN20.FLT]
Summary: January 20, 1988 mission transect flight lines. Coordinates taken at time of
mission were used to generate this coverage.
Covaraga Typa: Lidar
Faatura Typa: Lines
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produoad: 10/18/88
DESCRIPTION 07 SINGLE PRECISION COVERASB FLIGHT 01W
ARCS
POLYGONS
Arcs = 18
Segments = 6397
4 6 bytes of Arc Attribute Data
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
POINTS
Label Points =
TOLERANCES
SECONDARY FEATURES
Tics
Annotations
Links
STATUS
4
45
0
Fuzzy =
Dangle =
7.088 N
0.000 N
The coverage has not been Edited
since the last BUILD or CLEAN.
COVERAGE BOUNDARY
Xmin =
Xmax =
469185.281
534244.250
Ymin =
Ymax =
377606.500
448486.500
ITEMS
TYPE
03/28/90
NAME
INTERNAL
NAME
NO. RECS LENGTH
EXTERNL
DF
FLIGHT_UTM.TXT
ARC02 9DAT
0 404
DF
FLIGHT UTM.AAT
ARC031DAT
18 46
XX
DF
FLIGHT UTM.BND
ARC032DAT
1 16
XX
DF
FLIGHT UTM.TIC
ARC033DAT
4 12
XX
FLIGHT_UTM.AAT
18 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT
TYPE N
DEC
ALTERNATE NAME
INDEXED?
1
FNODE#
4
5
B
0
-
5
TNODE#
4
5
B
0
-
9
LPOLY#
4
5
B
0
-
13
RPOLY#
4
5
B
0
-
17
LENGTH
4
12
F
3
-
21
FLIGHT UTM#
4
5
B
0
-
25
FLIGHT UTM-ID
4
5
B
0
-
29
FLIGHT
3
3
I
-
-
32
TAPE
5
5
C
-
-
37
START.TIME
5
5
N
2
-
42
END.TIME
5
5
N
2
-
144
-------
FLIGHT OTM Continued...
LOG 03/26/90
Date
Time Elap
rain
CPU
aec
I/O
opr
Command
7/20/88
14 : 52
0
3
211
CREATE FLIGHT KMUTM
7/20/88
14:54
0
4
171
RENAME FLIGHT KMUTM FLIGHT UTRM
7/20/88
14:54
0
3
171
RENAME FLIGHT UTRM FLIGHT UTM
10/18/88
16:54
0
6
637
UNLOADANNO FLIGHT_UTM
3/26/90
11:35
0
2
87
externalall
3/27/90
9:
: 4 5
2
43 204 6 export
FLIGHT UTM
dubl:[pearl.denver]J20-FLIGHT_UTM.e00
145
-------
QUALITY ASSURANCE
Quality assurance consists of GIS coverages representing AIRS and
Nephelometer monitoring stations, and hourly AIRS data from 10:00 through
17:00 on January 20, 1988. These coverages were used to calculate data
including:
1) Distance from each Lidar shot (30 meters AGL) to each monitoring
station.
2) Time of Lidar shot, Lidar backscatter value and respective Air
quality measurement for CO, S02, N02, and 03.
These information was input to SAS for simple and multiple correlation
and regression analysis.
Mama of Covaraga: AIRS
Location: DISK$USER3:[DENVER.JAN20.QA]
Summary: Atmoshperic Information Retrieval Service montoring stations locations, and
hourly measurements for 1/20/88. AIRs geographic coordinates were used to generate
locations. AIRS.LKUP contains the air monitoring data and is related to AIRS.PAT by
STATION-ID.
Coverage Typa: QA
Feature Typa: Point
Manuscript RMS arror: N/A
Average RMS arror: N/A
Input Soala: N/A
Data Produoed: 11/1/8 8
DKSCRIFTIOH OF SINGLK PRECISION COVKRAGK AIRS
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
POINTS
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points = 10
53 bytes of Attribute Data/Point
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy
Dangle
4.963 N
0.000 N
COVERAGE BOUNDARY
The coverage has not been Edited
since the last BUILD or CLEAN.
Xmin =
Xmax =
ZTSMS 03/29/90
TYPE NAME
477219.000
513595.000
Ymin =
Ymax =
INTERNAL NAME
379393.000
429024.000
NO. RECS LENGTH EXTERNL
DF AIRS.TIC
DF AIRS.BND
DF AIRS.LKUP
ARCOOODAT
ARC001DAT
arc003DAT
4 12 XX
1 16 XX
10 186
146
-------
AIRS.PAT ARC004DAT
147
-------
AIRS Continued.
AIRS.PAT
10 Records Selected.
COLUMN
ITEM NAME
WIDTH OUTPUT
TYPE
N.DEC
1
AREA
4
12
F
3
5
PERIMETER
4
12
F
3
9
AIRS#
4
5
B
0
13
AIRS-ID
4
5
B
0
17
X-COORD
4
12
F
3
21
Y-COORD
4
12
F
3
25
NAME
15
15
C
-
40
SITE-ID
11
11
C
-
51
SYMBOL
3
3
• I
-
** REDEFINED ITEMS
* *
25
ALL
26
26
C
-
ALTERNATE NAME
INDEXED?
AIRS.LKUP
10 Records Selected.
COL ITEM NAME
1 NAME
16 SITE-ID
27 S02-10
32 S02-11
37 S02-12
42 S02-13
47 S02-14
52 S02-15
57 S02-16
62 S02-17
67 N02-10
72 N02-11
77 N02-12
82 N02-13
87 N02-14
92 N02-15
97 N02-16
102 N02-17
107 CO-10
112 CO-11
117 CO-12
122 CO-13
127 CO-14
132 CO-15
137 CO-16
142 CO-17
147 03-10
152 03-11
157 03-12
162 03-13
167 03-14
172 03-15
177 03-16
182 03-17
** REDEFINED ITEMS
1 ALL
WDTH OPUT TYP N.DEC
15 15 C
3/29/1990
ALTERNATE NAME
1/20/88
11
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
**
26
11
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
5
26
C
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
N
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
LOG 03/29/90
Date
Time Elap CPU I/O Command
min sec opr
10/13/88 10:22
8 795 generate stations
148
-------
10/13/88 10:
11/ 1/88 14:
3/29/90 10:
23
1
9
47
1
12
57
0
4
594 build stations point
665 ADDXY STATIONS
186 RENAME STATIONS AIRS
149
-------
Nam* of INFO Fila: DIST-NEPHVIP20
Location: DUBO:[DENVER.JAN20.QA.INFO]
Summary: A file comprised of distances from each (VIP) Lidar shot (30 meters agl) for
1/20/88 mission and each NEPHELOMETER monitoring station. VIP were interpolated Lidar
shots derived from the ARC/INFO coverage E30-VIP.
Coveraga Typa: QA
F«atur* Type: INFO Data File
Avaraga RMS error: N/A
Input: Soala: N/A
Data Produced: 3/1/88
DESCRIPTION 07 INTO FILE DIST-NEFHVIP20
LIDAR is the value of each shot recorded in backscatter units. XCOORD and YCOORD contain
the geographic location of each Lidar shot. STAT1 through 6 were distances (meters) from
each Lidar shot to each Nephelometer monitoring stations. The name of each monitoring
station appears below.
6744 RECORD(S) SELECTED
DATAFILE NAME: DIST-NEPHVIP20 3/29/1990
11 ITEMS: STARTING IN POSITION 1
COL ITEM NAME WDTH OPUT TYP N.DEC ALTERNATE NAME
1
VIP-TIME-ID
4
5
B
0
5
RECNO
4
4
I
-
9
LIDAR
4
4
I
-
13
XCOORD
10
10
N
1
23
YCOORD
10
10
N
1
33
STAT1
10
10
N
1
AURARIA
43
STAT2
10
10
N
1
FEDERAL
53
STAT3
10
10
N
1
PLAZA
63
STAT 4
10
10
N
1
TOWER
73
STAT5
10
10
N
1
WELBY
83
STAT 6
** REDEFINED
10
ITEMS **
10
N
1
BRIGHTON
5
ALL
200
200
C
-
150
-------
Mama of INFO Fila: DIST-RAW20JAN
Location: DCBO:[DENVER.JAN20.QA.INFO]
Summary: A file comprised of distances from each Lidar shot (30 meters agl) for 1/20/88
mission and each AIRs monitoring station.
Covacaga Typa: QA
Taatur* Typm: INFO Data File
Average RMS arror: N/A
Input Saala: N/A
Data Produoad: 3/1/80
DKSCRIPTIOH OF INFO FILE DIST-RAW20JAN
LIDAR is the value of each shot recorded in backscatter units. XCOORD and YCOORD contain
the geographic location of each Lidar shot. STAT1 through 10 were distances (meters) from
each Lidar shot to each AIRS monitoring stations. The name of each monitoring station
appears below.
6471 RECORD(S) SELECTED
DATAFILE NAME: DIST-RAW20JAN
15 ITEMS: STARTING IN POSITION 1
COL ITEM NAME WDTH OPUT TYP N.DEC
3/29/1990
ALTERNATE NAME
1
JAN20—FLIGHTS-ID
4
5
B
0
5
RECNO
4
4
I
-
9
LIDAR
4
4
I
-
13
XCOORD
10
10
N
1
23
YCOORD
10
10
N
1
33
STAT1
10
10
N
1
WELBY
43
STAT2
10
10
N
1
MYLAND RESERVIOR
53
STAT 3
10
10
N
1
AURORA
63
STAT 4
10
10
N
1
BOULDER
73
STAT 5
10
10
N
1
CAMP
83
STAT 6
10
10
N
1
RJH
93
STAT 7
10
10
N
1
CARRIAGE
103
STAT 8
10
10
N
1
ARVADA
113
STAT 9
10
10
N
1
AURARIA
123
STAT10
** REDEFINED ITEMS
10
* *
10
N
1
PALMER
5
ALL
200
200
C
-
151
-------
Name of INTO File: DIST-VIP20JAN
Location: DUBO:[DENVER.JAN20.QA.INFO]
Summary: A file comprised of distances from each (VIP) Lidar shot (30 meters agl) for
1/20/88 mission and each AIRs monitoring station. VIP were interpolated Lidar shots
derived from the ARC/INFO coverage E30-VIP.
Coverage Type: QA
Feature Type: INFO Data File
Average RMS error: N/A
Input Soale: N/A
Date Produced: 2/1/8B
DESCRIPTION OF INFO FIL2 DIST-VIP20JAN
LIDAR is the value of each shot recorded in backscatter units. XCOORD and YC00RD contain
the geographic location of each Lidar shot. STAT1 through 10 were distances (meters) from
each Lidar shot to each AIRS monitoring stations. The name of each monitoring station
appears below.
67 4 4 RECORD(S) SELECTED
DATAFILE NAME: DIST-VIP2 0JAN
15 ITEMS: STARTING IN POSITION
3/29/1990
COL ITEM NAME
WDTH OPUT TYP N.DEC ALTERNATE NAME
1
VIP-TIME-ID
4
5
B
0
5
RECNO
4
4
I
-
9
LIDAR
4
4
I
-
13
XCOORD
10
10
N
1
23
YCOORD
10
10
N
1
33
STAT1
10
10
N
1
WELBY
43
STAT 2
10
10
N
1
MYLAND RESERVI0R
53
STAT3
10
10
N
1
AURORA
63
STAT 4
10
10
N
1
BOULDER
73
STAT 5
10
10
N
1
CAMP
83
STAT 6
10
10
N
1
RJH
93
STAT 7
10
10
N
1
CARRIAGE
103
STATS
10
10
N
1
ARVADA
113
STAT 9
10
10
N
1
AURARIA
123
STAT10
** REDEFINED
10
ITEMS **
10
N
1
PALMER
5
ALL
200
200
C
-
152
-------
Ham* of INTO Til®: FLIGHT_INFO
Location: DUBO:[DENVER.JAN20.QA.INFO]
Summary: A file comprised of distances from each Lidar shot (30 meters agl) for 1/20/88
mission and each AIRs monitoring station.
Covaraga Typ*: QA
Faatura Typa: INFO Data File
Avaraga RMS arror: N/A
Input Saala: N/A
Data Produoad: 3/1/88
DESCRIPTION Or INFO FILB DIST-RAM20JAN
DIST-RAW20JAN is an INFO file containing information for each Denver Lidar mission flown
by EMSL-LV. TAPE contains the datafile name, DATE stores the mission date, FLIGHT contains
the transect number and transect times are stored in items START and END.
58 RECORD(S) SELECTED
DATAFILE NAME: FLIGHT
INFO
5
ITEMS: STARTING
IN POSITION
1
COL
ITEM NAME
WDTH
OPUT
TYP N -
¦ DEC
1
TAPE
4
4
C
-
5
DATE
7
7
C
-
12
FLIGHT
2
2
I
-
14
START
5
5
N
2
19
END
5
5
N
2
3/29/1990
ALTERNATE NAME
153
-------
Mara* of Coverage: NEPHAL
Location: DISK$USER3:[DENVER.JAN20.QA]
Stannary: Nephelometer monitoring station locations. Locations were generated from
locations received from EMSL-LV AMD / AIRS group.
Coverage Type: QA
Feature Type: Point
Average RMS error: N/A
Input Soale: N/A
Date Produoed: 1/18/89
DBSCRIPTXON OF SXNGLB PRECISION COVERAGE NEPHAL
ARCS
POLYGONS
Arcs = 0
Segments = 0
0 bytes of Arc Attribute Data
POINTS
Polygons = 0
There is NO Polygon Topology.
0 bytes of Polygon Attribute Data
SECONDARY FEATURES
Label Points = 6
44 bytes of Attribute Data/Point
TOLERANCES
Tics
Annotations
Links
STATUS
Fuzzy =
Dangle =
3.310 N
0.000 N
COVERAGE BOUNDARY
Coverage has 1 edit mask(s), use
BUILD or CLEAN to restore topology
Xmin =
Xmax =
499564.000
516075.313
Ymin =
Ymax «=
399396.000
432500.000
ITEMS 03/29/90
TYPE NAME
INTERNAL NAME
NO. RECS LENGTH EXTERNL
DF
NEPHAL.BND
ARC002DAT
1
16
XX
DF
NEPHAL.TIC
ARC006DAT
4
12
XX
DF
NEPHAL.PAT
ARCO0 9DAT
6
44
XX
NEPHAL.PAT
6 Records Selected.
COLUMN ITEM NAME
WIDTH
OUTPUT
TYPE
N.DEC ALTERNATE
NAME
INDEXED?
1
AREA
4
12
F
3
-
5
PERIMETER
4
12
F
3
-
9
NEPHAL#
4
5
B
0
-
13
NEPHAL-ID
4
5
B
0
-
17
STATION
15
15
C
-
-
32
TIME
5
5
N
2
-
37
X-COORD
4
12
F
3
-
41
Y-COORD
4
12
F
3
-
LOG 03/29/90
Date Time Elap
CPU
I/O
Command
min
sec
opr
1/18/89 11:48 0
7
806
GENERATE NEPHALIMETER
1/18/89 11:49 0
2
113
RENAME
NEPHALIMETER NEPHAL
1/18/89 14:46 1
11
996
BUILD
NEPHAL
POINT
1/18/89 15: 6 1
12
632
ADDXY
NEPHAL
154
-------
CONTENTS
Abstract iv
Project Summary v
Definitions and Acronyms xii
1. DBC Data Dictionary 1
2. Data Dictionary Listings 2
Census 2
Cultural 5
Elevation 17
ESRI 24
Lidar 41
Quality Assurance 138
-------
NOTICE
Although the information in this document has/Deen funded wholly or in
part by the United States Environmental Protection Agency under Contract
No. 68-03-3245 to Lockheed Engineering nnrl M inngnmr inti fn i n i nnr Company,
Inc., it does not necessarily reflect the views of the Agency and no
official endorsement should be inferred.
Mention of trade names or commercial products does not constitute
endorsement or recommendation for use.
This document is a preliminary draft. It has not been formally released
by the U.S. Environmental Protection Agency and should not at this stage
be construed to represent Agency Policy. It is being circulated for
comments on its technical merit and policy implications.
-------
3/29/90 11: 9 0 1 70 EXTERNALALL
3/29/90 12:50 1 8 341 EXPORT COVER NEPHAL DUB1:[PEARL.DENVER]QAXNEPHAL.E00
155
------- |