This program provides easy screen flow and simple data entry. Trail data is automatically stored and sorted, thus eliminating the need to manually enter data using Trailware software. Detailed trail data and summary reports can be analyzed and printed directly using  the HETAP software. UTAP data can also be manually entered into HETAP software as an economical work around using manual assessment tools using traditional UTAP trail assessment methods.

The Wheeled Instrumentation Sensor Package (WISP) and the HETAP software provide high-speed data collection. On average, an individual using HETAP can collect detailed and accurate trail information at one mile per hour, while recording many features. It is also feasible to collect detailed trail data for a backcountry trail several miles long in only one day. As a result, longer trail lengths can be assessed with a greater amount of detail in a shorter amount of time.

HETAP is designed to enable one person to collect trail information. However, two or more individuals can still be used in the assessment process. Managers often require at least two individuals to work together for safety reasons. It is encouraged during training exercises that all available trail assessors work together as a team for review and consistency in measuring trail data. When two individuals are collecting trail data, the second person can measure trail width and features using a tape measure and a notepad or datasheet. The second data collector can periodically enter the features into HETAP or they can be entered later as long as feature locations (distance) are recorded with the feature notes. If compass readings are being recorded without a GPS, this person can also use a compass to record trail directions.

Stations can be recorded at the push of a keystroke as often as desired along the trail. More frequent stations increase the accuracy of trail data. The HETAP data collection cart is only required to advance a distance of 0.1 foot/0.03 meters to record another station. The ability to record stations anywhere along the trail allow for a more accurate trail assessment. It is strongly encouraged to use this to your advantage by taking as many stations along the trail as possible whenever there is any noticeable change in any trail condition.

All grade, cross-slope, tread width and surface data in the HETAP software program is related to the station that has most recently been recorded by selecting the [Record Station] or [Record Feature] button. Distances, grades and cross slopes are continuously displayed in the HETAP program and as soon as a trail tread attribute changes a new station should be recorded to automatically record the new grade and cross-slope. You can also record stations and features that have the same tread width, surface type and characteristics as the previous station since the HETAP software copies the data from the previous station or feature for you.

All necessary data fields are present in the HETAP program. There is no need to write data down on paper that can be miswritten, illegible or lost. Trail data can be easily backed up to any location on your computer or to an external thumb drive.

Station marking isn’t necessary with the HETAP program. There is no lag time waiting for your partner to catch up and find your exact location. HETAP software allows you to use the GPS coordinates to relocate any specific station in the future if needed.

The identification and recording of maximum grades and cross slopes happens automatically using HETAP software. Simply record a station any time there is any change in grade or cross slope. Stations should be recorded often to reflect changing trail conditions. This can be determined visually or by comparing the previous and current grade/cross slope in the HETAP Stations screen. HETAP also allows you to set alarms to tell you when the grade or cross slope has changed by more than a set amount. 

Any significant change in tread width requires a new station. Simply record a station at the beginning of any significant change in tread width. In addition, when the tread width is less than the specified design width, it should be recorded as a ‘Minimum Clearance Width’ feature. The feature should be recorded at the start of the minimum width.