San Dimas Technology & Development Center
444 E Bonita Ave
San Dimas, CA 91773
(909) 599-1267
|
Automated Road Monitoring and Analysis System (ARMAS)
T & D Project No. TE01EM37
The issue of road use and needs
on National Forests has grown in visibility and importance.Road use data can
be a surrogate indicator of human impact, sedimentation, vectors for pathogens
etc. Maintaining extensive road monitoring systems is cost prohibitive in
most areas. This project is to review current data collection methods, and
statistically develop and verify a design, which would utilize a minimum number
of monitors (traffic counters) to predict road use across a forest. The potential
for cost effectively retrieving the data automatically will also be reviewed.
FY 2000 Continuing Actions:
-
Define the frequency
of data collection needed and the type of information traffic counters need
to collect and store.
-
Based on preliminary
methods and algorithms developed by the Forestry & Range Sciences Laboratory,
prepare a counter placement procedure, data collection instructions and
procedures, data collection forms and a data collection relational database
that can be integrated seamlessly into data analysis.
-
Define test equipment
needs and prepare a test plan for FY 01 testing of a developmental system.
-
Procure all needed
test equipment and install it, if necessary, at test locations.
-
Develop final
data analysis algorithms and software. ready for beta testing by test forests
and R6 engineering by the end of April 2001. The software shall be an integrated
package consisting of the following modules:
-
Data Collection
& Review Module
-
Allows
review of raw data prior to final entry into database.
-
Formats
data into predefined fields and enters it into a data table.
-
Provides
for exportation of the data to Oracle, Access and INFRA.
-
Counter Location
Map w/ Data Filter Module
-
Recalls
data from database, with attributes, and creates a map overlay of
counter locations.
-
Allows
interactive count comparisons between selected counters in a group.
-
Allows
the user to set an interactive comparison filter to determine the
significance of count differences within a group, and for the elimination
of redundant counters from the data set if desired by the user.
-
Allows
display of a revised counter layout on the map after each iteration
of the data filter.
-
Cluster Analysis
Module
-
Builds
routes and determines the interrelationship between counters.
-
Allows
user to make final selection of counters to be used for future traffic
estimates and year-by-year revalidation of forest traffic count
model.
-
Forest Count
Modeling Module
-
Uses future
count data to estimate road use by week, month and season.
-
Provides
statistical algorithms to predict future road use and measure modeling
validity.
-
May provide
interactive graphic displays (if desirable) for user decision making.
-
Help Module
-
Develop ARMAS
user guides as follows:
-
Scan R6 Traffic
Surveillance Guide for electronic distribution as a ARMAS user general
reference.
-
Develop a
Counter Placement Guide for ARMAS Users.
-
Develop, if
necessary, instructions for the use of ARMAS software. This
document would supplement the ARMAS Program Help Module.
-
Develop a
ARMAS Training Module. This would most likely be a PowerPoint Slide
Presentation to support the training of new ARMAS users.
-
R6 Engineering
and Forests to commence ARMAS system and software beta testing by end of
April 2001.
-
After 3 months
of testing, based on preliminary testing results, define and make any software
or hardware changes indicated.
-
Prepare an interim
memo report at the end of FY 01.
-
Complete Module
1 and hardcopy of User's Guide. Deliver to R6 test Forests December 14,
2001
-
Complete Module
2 March 1, 2002.
-
IMI Steering Comm.
meeting 2002: Demo Module 1 & 2, display reports, maps, route analysis and
SAS routines.
-
Edit and reprint
R6 Traffic Surveillance Manual.
FY 2003 Planned Actions
(If SDTDC project funding permits)
ARMAS development
was discontinued in FY03. Further development will be determined by available
funding and revised project goals.
- Verify software algorithms and
modify software as indicated.
- Complete context sensitive help.
Package software for distribution.
- Support and/or monitor system
implementation as needed.
- Publish final report with instructions
on system use, and recommendations on system implementation.
Top
of Page
|