report sara 1910 - transportation€¦ · sara: aran road condition summary route number route name...
TRANSCRIPT
The Road Inventory
of
Saratoga National Historical Park
SARA – 1910 Cycle 4
Prepared By:
Federal Highway Administration
Road Inventory Program
Cycle 4
_̂
_̂
_̂_̂
_̂_̂
_̂̂_
_̂_̂
_̂_̂
_̂
Saratoga National Historical Park
in
New York
Saratoga NationalHistorical Park
Providence
Concord
New York
Harrisburg
C a n a d aC a n a d a
Philadelphia
Trenton
HartfordBuffalo
Newark
Montpelier
TABLE OF CONTENTS
SECTION PAGE
1. INTRODUCTION 1 - 1
2. PARK SUMMARY INFORMATION
Paved Route Miles and Percentages by Functional Class and PCR 2 – 1
ARAN Road Condition Summary 2 – 2
Parkwide Condition Summary 2 – 3
Cycle 2 vs Cycle 3 vs Cycle 4 Condition Comparisons 2 – 4
3. PARK ROUTE LOCATION / CONDITION MAPS
Route Location Key Map 3 – 1
Route Location Area Map 3 – 2
Route Condition Key Map – PCR Mile by Mile 3 – 4
Route Condition Area Map – PCR Mile by Mile 3 – 5
4. PARK ROUTE INVENTORY
Route Identification Report 4 – 1
5. PAVED ROUTE CONDITION RATING SHEETS (CRS)
CRS Pages 5 – 1
6. MANUALLY RATED PAVED ROUTE CONDITION
RATING SHEETS (MRR)
MRR Pages 6 – 1
7. PARKING AREA CONDITION RATING SHEETS
Paved Parking Area Pages 7 – 1
8. PARKWIDE / ROUTE MAINTENANCE FEATURES
SUMMARIES
Parkwide Maintenance Features Summary 8 – 1
Route Maintenance Features Summary 8 – 2
Structure List 8 – 3
9. PARK ROUTE MAINTENANCE FEATURES ROAD LOGS
Route Maintenance Features Road Logs 9 – 1
10. APPENDIX
A. Glossary of Terms and Abbreviations 10 – 1
B. Description of Rating System 10 – 2
C. General Information on RIP Systems 10 – 8
D. Metadata 10 – 11
Saratoga National Historical Park
Section 1
Introduction
INTRODUCTION
Background: In 1976, the National Park Service (NPS) and the Federal Highway Administration (FHWA) entered into a Memorandum of Agreement(MOA), establishing the Road Inventory Program (RIP). In 1980, the NPS and the FHWA terminated the 1976 MOA and entered into a new MOA that provided for the completion of the initial phase of the RIP. The purpose of the RIP, per the 1980 MOA was to maintain and update RIP data in order to develop long-range costs and programs to bring National Park Service (NPS) roads up to, or to maintain, designated standards, and establish a maintenance managementprogram.
The FHWA’s Federal Lands Highway (FLH) was assigned the task of identifying condition deficiencies and corrective priorities along with associated corrective costs, inventorying maintenance features (e.g., culverts, signs, guardrail, etc.), summarizing the data and findings in a report and providing a photographic record of the road system.
The FLH completed the initial phase of the RIP in the early 1980’s. As a result of this effort, each park received a RIP book, also known as the “Brown Book,” that included the information collected during this initial RIP phase.
In an effort to maintain and update the RIP data, a cyclical data collection and reporting process was reestablished in the 1990’s. The FLH completed two cycles of RIP data collection between 1994 and 2001. Cycle 1 was collected in 44 large parks from 1994 to 1996. This data was found to be unusable for comparison to future cycles. Cycle 2 data was collected from March 1997 to January 2001 in 79 large parks and 5 small parks containing 4,874 route miles.Each park received a copy of a Cycle 2 RIP Report, also known as the “Blue Book”. Cycle 3 was completed from 2001 through 2004, and included data collection in all parks that contain pavement.
Since 1984, the RIP Program has been funded through the Federal Lands Highway Program’s Park Roads and Parkways (PRP) Program. Currently, the NPS Washington Headquarters’ Park Facility Management Division is responsible for coordinating the RIP program with the FLH. The FLH Washington office coordinates policy and prepares national reports and needsassessment studies for congress.
In 1998, the Transportation Equity Act for the 21st Century (TEA-21) amendedTitle 23 U.S.C., and inserted Section 204(a)(6) which requires the Federal Highway Administration and the National Park Service, to develop, by rule, a Pavement Management System (PMS) for the park roads and parkways serving the National Park System. As a result of the requirements in TEA-21, the NPS and FHWA are in the process of developing a PMS. The PMS will assist thedecision-makers in effectively spending limited PRP Program funds. The PMS
1 - 1
will provide information for planning and programming road maintenance,rehabilitation, and reconstruction activities. RIP data will provide the basic information for this system.
Key information included in the RIP is the mileage inventory and conditionassessments accomplished by the RIP Program. The mileage and condition dataare used in the current allocation formula of PRP Program funds.
RIP Cycle 4: Cycle 4 data collection was initiated in spring 2006, where 86 large parks, consisting of 5,553 route miles and 6,232 paved parking areas, were selected as a representative sample of the entire NPS paved road network. Cycle 4 is scheduled for completion in spring 2009 and will serve the PMS in further development of its pavement preservation techniques.
In the Cycle 4 Reports, a general condition rating of excellent, good, fair and poor is ascribed to each one-mile section of paved roadway, and to each paved parking area. This condition rating system provides a realistic means of assessing the general funding needs for road improvements. Along with these descriptive condition ratings, a numerical rating between 0 and 100 is ascribed to each mileof road and to each parking area. This numerical rating is called a PavementCondition Rating (PCR). The PCR rating system is described in Section 10 of this report.
All of the fieldwork required for obtaining inventory, condition, and maintenancefeature information is coordinated with each park and the regional offices to ensure that the information in the RIP reports is accurate.
The FLH is responsible for all the data presented in this report. Anyone having questions or comments regarding the contents of this report is encouraged to contact the FHWA RIP Coordinator. It is our aim to provide exceptional customer satisfaction in our delivery of the RIP program.
The FHWA RIP Team
FHWA/EFLHD FHWA/CFLHD21400 Ridgetop Circle 12300 West Dakota Ave. Sterling, VA 20166 Lakewood, CO 80228 (703) 404-6371 (720) 963-3560
1 - 2
Saratoga National Historical Park
Section 2
Park Summary Information
SARA: PAVED ROUTE MILES AND PERCENTAGES
BY FUNCTIONAL CLASS AND PCR
Pavement Condition Rating (PCR)
Poor (<=60) Fair (61-84) Good (85-94) Excellent (95-100) TOTAL
F.C. MILES % MILES % MILES % MILES % MILES
1 0.34 3.17% 1.78 16.62% 0.52 4.86% 2.64
2 0.02 0.19% 0.23 2.15% 0.16 1.49% 0.23 2.15% 0.64
3 0.34 3.17% 4.05 37.82% 1.94 18.11% 1.02 9.52% 7.35
456 0.08 0.75% 0.08
78
Totals 0.78 7.28% 6.06 56.58% 2.62 24.46% 1.25 11.67% 10.71
2-1
SARA: ARAN ROAD CONDITION SUMMARY
ROUTE
NUMBER ROUTE NAME
FUNCT
CLASS
ROUTE
LENGTH
SURFACE
TYPE
AVERAGE
SURFACE
CONDITION
RATING (SCR)
AVERAGE
PAVEMENT
CONDITION
RATING (PCR)
0010 ENTRANCE ROAD 1 2.64 ASPHALT 66 75
0100 ROOSEVELT ROAD 2 0.11 ASPHALT 67 67
0200 TOUR ROAD TO STOP 3 2 0.53 ASPHALT 86 90
0401 HEADQUARTERS LOOP ROAD 6 0.08 ASPHALT 46 46
0500 TOUR ROAD 3 7.35 ASPHALT 75 81
Data Collected 11/04/2008
ARAN ROAD CONDITION SUMMARY
66 67
86
46
757567
90
46
81
0
10
20
30
40
50
60
70
80
90
100
0010 0100 0200 0401 0500
ROUTE NUMBER
SC
R/P
CR
AVERAGE SURFACECONDITION RATING (SCR)
AVERAGE PAVEMENTCONDITION RATING (PCR)
2-2
SARA: PARKWIDE CONDITION SUMMARY
**AVERAGE
PAVEMENT
CONDITION
RATING (PCR)
*AVERAGE
ROUGHNESS
CONDITION
INDEX (RCI)
*AVERAGE
SURFACE
CONDITION
RATING (SCR)
*AVERAGE
RUT INDEX
*AVERAGE
ALLIGATOR
CRACKING
INDEX
*AVERAGE
LONGITUDINAL
CRACKING
INDEX
*AVERAGE
TRANSVERSE
CRACKING
INDEX
*AVERAGE
PATCHING
INDEX
81 91 74 75 100 100 100 100
** PCR Index is based on all ARAN-driven roads, parking areas, and manually rated routes.
* Index values are based on ARAN-driven roads only.
Data Collected 11/04/2008
PARKWIDE CONDITION SUMMARY
81
91
74 75
100 100 100 100
0
10
20
30
40
50
60
70
80
90
100
**AVERAGE PAVEMENTCONDITION RATING
(PCR)
*AVERAGEROUGHNESS
CONDITION INDEX (RCI)
*AVERAGE SURFACECONDITION RATING
(SCR)
*AVERAGE RUT INDEX *AVERAGE ALLIGATORCRACKING INDEX
*AVERAGELONGITUDINAL
CRACKING INDEX
*AVERAGETRANSVERSE
CRACKING INDEX
*AVERAGE PATCHINGINDEX
RA
TIN
G
2-3
������
������
���
������
���
����
�����
�� ��
�����
�� ��
�����
�� �� ������
�����
�����
���������������
� ���������
���� ������������
� ����������
�������������������
����������
���� ������������ ����������������������������
������
������
������
������
������
������
������
������
������
���� ����� ��� ���� � !��" !��" !�"�# $% &% �# $% �# $% $�
���� ����� ���������� !�$" !�$" �# ����'()�*(++,*),-�.'�
�/*+,����# $% & �# $% & �# $% �#
���� ����� ���%����%� !0" !��" !�"�# $0 $� �# $& 0 �# $0 $
���� ����� ����0����0 !�%" !�%" �# ����'()�*(++,*),-�.'�
�/*+,���(1��/*+,����# 0� � �# 0� � �# �# �#
�%�� ����� �&��%�&��% !� " !��" !�"�# $ 0� �# $& &% �# $� $�
�
��
��
��
��
���
����
����
����
����
����
�� ��
�� ��
�� ��
���
�
��
��
��
��
���
����
����
����
����
����
�� ��
�� ��
�� ��
���
�
��
��
��
��
���
����
����
����
����
����
�� ��
�� ��
�� ��
���
�������������������� ���������������������� ��� �����
Saratoga National Historical Park
Section 3
Park Route Location / Condition
Maps
3-1ºPark Owned Routes
Saratoga National Historical Park
Route Location Map
Key Map
1
1 0 10.5
Miles
2
Rte 0901Rte 0900Rte 0100
Rte 0903ZZRte 0401
Rte 0907
Rte 0913
Rte 0902
Rte 0910
Rte 0911
Rte 0904
Rte 0909
Rte 0908
Rte 0905
Rte 0912
Rte 0914
Rte 0010
Rte 0500
Rte 0200
3-2ºUnique colors used to differentiate routes
Saratoga National Historical Park
Route Location Map
Area 1
0.5 0 0.50.25
Miles
Rte 0915
Rte 0916
Rte 0919
3-3ºUnique colors used to differentiate routes
Saratoga National Historical Park
Route Location Map
Area 2
0.2 0 0.20.1
Miles
3-4º
Saratoga National Historical Park
Route Condition Map
PCR - Mile by Mile
Key Map
1 0 10.5
Miles
* If the PCR rating is not available for a section, the SCR rating will be displayed. See appendix for definitions and formulas.
PCR(<=60)
Poor(61 - 84)
Fair(85 - 94)
Good(95 - 100)
Excellent No Data
1
Rte 0010
Rte 0500
Rte 0200
Rte 0100
Rte 0401
3-5º
Saratoga National Historical Park
Route Condition Map
PCR - Mile by Mile
Area 1
0.5 0 0.50.25
Miles
* If the PCR rating is not available for a section, the SCR rating will be displayed. See appendix for definitions and formulas.
PCR(<=60)
Poor(61 - 84)
Fair(85 - 94)
Good(95 - 100)
Excellent No Data
Saratoga National Historical Park
Section 4
Park Route Inventory
������������� ������������������������������������� ����������������� ! �����"�#��
����������� ��� ������������������������������������������������ ���!���"�����#���������������� ���!"�����
���������������� ���!���"�����
$������������������������
�����%��������
�����%&'������$��(������������ )�(��������������*!�������� ���!"����� ���(�����������+���,!
--�����������������������������������.������/��'+0������.��������������������.�����1��������������'2�1�3
�$�$ �������������������� �������
%��&�
'��((
���� �(����������&�
�&��������
������
)���(
��#&�
*���
+�,
������
)���(%�� *
*����
���
-����.
%)����
�&
)����
�����
�/�%*
���&
-���(
$���
)��(
'���((�
��� )����&
�(�����
����������� ���� ����� ������������� ������ ������ ���������������������� �� ���� ������
����������������
�������������� �����!�
���������"���
����� ����#�"������ ������ ������ �����������!�#����������� �� ���� ������
����������������������
���� �����!����������
����
����� ���������������!�� ������ ������ ������������������!���
!��$���
����% �� ���� ������
����������������
�������������� �����!�
���%���������
����� ���&�������"��!�
����
����%� ������ �����������"��!����� �� ���� ����%�
����������������������
���� �����!����������"���
����� ���������������� ������ ������ ����������������������
���� �����!����%�����"���
����� ����� ������
����������������������
����
����� �������������� ������ ������ ��������������������������
����
����� ����� ������
����������������������
����
����� �""���������� ������ ����%� ������������� ����� ����%�
����������������������
����
����� ���������������
����
������ ������ ��������������������������
����
������ ����� ������
����������������
�����������������
����� '�������������
����
������ ����%� ������������������������ ����� ����%�
����������������������
����
����� �������������
���������
������ ������ ������������������������ ����� ������
����������� ���� ����% ���"���������
����
������ ������ �����!��$�'���������%�� ����� ������
�������$���������� ����� #������� ����
����
������ ������ �������������� ����� ������
����������������������
���� �����!����������"���
����� #�������������
��#��������
������ ������ �������������� ����� ������
����������� ���� ����� ���"���������
�������������
������ ������ ��������������������"���
������!��$���
������ ����� ������
�����������������#������
�������!��$���
����� ��������� ������ ������ �������������������������
���� �����!����������
����
����� �� ���� ������
����������������
�������������� �����!�
���������"���
���� #�������������
!��$���
������ ������ ���������������������
���� ��������
����� ���(��% ���� ������
��)��������������������
�����#�"������ �����!�
�������������
���� ����#�"�������
!��$���
������ ������ ������% ��(��� ���� ������
������������� ������������������������������������� ����������������� ! �������#��
����������� ��� ������������������������������������������������ ���!���"�����#���������������� ���!"�����
���������������� ���!���"�����
$������������������������
�����%��������
�����%&'������$��(������������ )�(��������������*!�������� ���!"����� ���(�����������+���,!
--�����������������������������������.������/��'+0������.��������������������.�����1��������������'2�1�3
�$�$ �������������������� �������
%��&�
'��((
���� �(����������&�
�&��������
������
)���(
��#&�
*���
+�,
������
)���(%�� *
*����
���
-����.
%)����
�&
)����
�����
�/�%*
���&
-���(
$���
)��(
'���((�
��� )����&
�(�����
����������������
�������������� �����!�
���%�����"���
���� ���������������� ������ ������ ����!��$�������� ���(��� ���� ������
����������������
����&�������"��!�
���� �����!����������
����
����** �!!��������"����
!��$��������
������ ������ ���������������
����&�������"��!�
���� �����!����������
����
��%�� ��(��� ���� ������
����������������������
���� �����!����������"���
���� ��!���!��$��� ������ ������ ���������������������
���� �����!����������"���
%���� �%(��� ���� ������
����������������������
���� �����!����������"���
���� ��!���!��$��� ������ ������ ���������������������
���� �����!����%�����"���
%���� �%(��� ���� ������
����������������������
����
���� ��!����#���"� �
!��$���
������ ������ �����!��$��������� ����� ������
����������������������
����������!�� �������
���� ��!���!��$��� ������ ������ ����!��$���%���% ���(��� ���� ������
����������������������
���� �����!����������
����
���% ��!���!��$��� ������ ������ ���������������������
���� �����!����������
����
%���� �%(��� ���� ������
����������������������
���� �����!���%������"���
���� ��!���!��$��� ������ ������ ���������������������
���� �����!���%������"���
%���� �%(��� ���� ������
����������������������
���� �����!����%�����
����
���� ��!���!��$��� ������ ������ ���������������������
���� �����!����������
����
%���� ���(��� ���� ������
����������������������
���� �����!���%������"���
���� ��!���!��$��� ������ ������ ���������������������
���� �����!����������"���
%���� ��(%�� ���� ������
����������������������
���� �����!����������
����
���� ��!�%�!��$��� ������ ������ ���������������������
���� �����!����������
����
%���% �%(��% ���� ������
����������������������
���� �����!����������
����
���� ��!���!��$��� ������ ������ ����!��$���%���� ���(%%� ���� ������
����������������������
���� �����!���%%�����
����
���� ��!����!��$��� ������ ������ ���������������������
���� �����!����������
����
%���� ��(��� ���� ������
����������� �������� ���"���������
!��$���
������ ������ ����!��$��������� ���(��� ���� ������
���������������������� ���������!��$��� ������ ������ ����!��$����%�%� ���(��% ���� ������
����������������
����"���������
!��$���
���� ���"���������
���������!��$���
������ ������ ����!��$��������� ��(��� ���� ������
������������� ������������������������������������� ����������������� ! �����0�#��
����������� ��� ������������������������������������������������ ���!���"�����#���������������� ���!"�����
���������������� ���!���"�����
$������������������������
�����%��������
�����%&'������$��(������������ )�(��������������*!�������� ���!"����� ���(�����������+���,!
--�����������������������������������.������/��'+0������.��������������������.�����1��������������'2�1�3
�+))$�1�*2*$-��%2���$�$*23$��$*�2�$-�4��*2��'$-��$�5
$�������������)���(
$���+�����������)���(
*2*$-��$�5��2+*6�)�-6�
$�$�� ����������)���( '���((�������������)���($�$�� ������-����)���(
'���((���+�����������)���(���������7����-����)���(
������)���-����)���(
*2*$-��$86 �-$�6�)�-6�
$������������7������/%*!
$���)����������������(���/%*!
�'���+,-./
�"�&9"�
��&�:�
�"�&9��
�"�&9"� ��&���
��&���
��"0;�<�
��
�:"&�:
�2+*6�*2*$-�
'���((������������7����$�����/%*
��
��
'���((���������)����/%*
�"=&=9=
�0&=9<
��&���
���&0<"
-$�6�)�-6�*2*$-� '2�'6���2��*2*$-�
$���+����������7������/%*!
��"0;�<�
'���((���+����������7����$�����/%* ��
*2*$-�$--��$�5��3���/%*!
��
�$�5��3�$�6$�*2*$-�
�'���+,-./
�'���+,-./
>6�34*6 �$86�$36��$�5�8$-+6�
��"&�0�9�&�9
�+*���.012
$'��.012
-'��.012
*'��.012
�$*'4��.012
�'����3.4155-3.
��$�9�&=� ���&�: ���&=� ���&9= �"��&��
������������� ������������������������������������� ����������������� ! �������#��
����������� ��� ������������������������������������������������ ���!���"�����#���������������� ���!"�����
���������������� ���!���"�����
$������������������������
�����%��������
�����%&'������$��(������������ )�(��������������*!�������� ���!"����� ���(�����������+���,!
--�����������������������������������.������/��'+0������.��������������������.�����1��������������'2�1�3
��#����*����$??��������(@
$��,�$(�.������'���������������
'2�,���������'������'���������������
'��,�'??���������������
���,�����7��������(��������
3��,�3�������������
�$�,�������������
�8�,���������� ����)���������������
2*�,�2�.���)�������(��������
3����������7�����%��������'��((�#�������*�?��
'��((�"����� !6-.4-7+8�!+69��3+0��:6+8�!+69;+<��!:=8-4��3+05 ����3+05�;>-4>�43.5,-,:,1�,>1�?+-.�+44155�63:,1(�4-64:8+,36<�,3:6(�36�,>363:/>@+61�@36�7+69�A-5-,365�
�3:,1��:?=165���B�������3,1C���:6+8�7+69;+<5���1�/���+,4>1D��6+41 �+61�.:?=1610���B��� ,+,1��3:,15��.A1.,36-10�@36�!+69���3:,1��:?=165�����B������
'��((��� �3..14,36�!+69��3+0��!:=8-4��3+05 �B��3+05�;>-4>�763A-01�+44155�;-,>-.�+�7+69�,3�+61+5�3@�541.-4(�54-1.,-@-4(�61461+,-3.+8�36�4:8,:6+8�-.,1615,(�5:4>�+5�3A1683395(�
4+?7/63:.05(�1,4����3:,1��:?=165����B����
'��((�0� 714-+8�!:67351�!+69��3+0���!:=8-4��3+05 �B��3+05�;>-4>�763A-01�4-64:8+,-3.�;-,>-.�7:=8-4�+61+5(�5:4>�+5�4+?7/63:.05(�7-4.-4�+61+5(�A-5-,36�41.,16�43?781215(�
43.4155-3.+-61�@+4-8-,-15(�1,4����>151�63+05�/1.16+88<�516A1�83;B57110�,6+@@-4�+.0�+61�3@,1.�015-/.10�@36�3.1B;+<�4-64:8+,-3.����3:,1��:?=165����B����
'��((�� !6-?-,-A1�!+69��3+05���!:=8-4��3+05 �B��3+05�;>-4>�763A-01�4-64:8+,-3.�,>63:/>�61?3,1�+61+5�+.0�36�+44155�,3�76-?-,-A1�4+?7/63:.05�+.0�:.01A183710�+61+5����>151�
63+05�@61E:1.,8<�>+A1�.3�?-.-?:?�015-/.��5,+.0+605�+.0�,>1-6�:51�?+<�=1�8-?-,10�,3�5714-+88<�1E:-7710�A1>-4815����3:,1��:?=165����B�����
���������������� �3,1C���:.4,-3.+8��8+5515���+.0���>+A1�,>1�5+?1�63:,1�.:?=165�=14+:51(�>-5,36-4+88<(�,>1<�;161�.:?=1610�5-?-8+68<�
'��((�< �0?-.-5,6+,-A1��44155��3+0����0?-.-5,6+,-A1��3+05 �B��88�7:=8-4�63+05�-.,1.010�@36�+44155�,3�+0?-.-5,6+,-A1�01A1837?1.,5�36�5,6:4,:615�5:4>�+5�7+69�3@@-415(�1?783<11�
E:+6,165(�36�:,-8-,<�+61+5����3:,1��:?=165����B����
'��((�= �15,6-4,10��3+0����0?-.-5,6+,-A1��3+05 �B��88�63+05�.36?+88<�483510�,3�,>1�7:=8-4(�-.48:0-./�7+,638�63+05(�,6:49�,6+-85(�+.0�3,>16�5-?-8+6�63+05����3:,1��:?=165����B����
����������������� �3,1C����:.4,-3.+8��8+5515���+.0���>+A1��,>1�5+?1�63:,1�.:?=165�=14+:51�>-5,36-4+88<�,>1<�;161�.:?=1610�5-?-8+68<�+.0�3@,1.�,>161�-5�8-,,81�0-5,-.4,-3.�=1,;11.�
,>151�63:,15����36�12+?781(�=14+:51�:,-8-,<�+61+5�+.0�1?783<11�>3:5-./�+61�3@,1.�483510�,3�,>1�7:=8-4(�,>-5�615,6-4,-3.�;3:80�615:8,�-.�48+55-@-4+,-3.�3@�������6+,>16�
,>+.������
'��((�9 �6=+.�!+69;+<���6=+.�!+69;+<5�+.0��-,<�,611,5 �B��>151�@+4-8-,-15�516A1�>-/>�A38:?15�3@�7+69�+.0�.3.B7+69�618+,10�,6+@@-4�+.0�+61�615,6-4,10(�8-?-,10B+44155�@+4-8-,-15�-.�
+.�:6=+.�+61+����>-5�4+,1/36<�3@�63+05�76-?+6-8<�1.43?7+5515�,>1�?+F36�7+69;+<5�;>-4>�516A1�+5�/+,1;+<5�,3�3:6�.+,-3.G5�4+7-,+8����,>16�?+F36�7+69�63+05�36�736,-3.5�
,>1613@(�>3;1A16(�?+<�=1�-.48:010�-.�,>-5�4+,1/36<����3:,1��:?=165��B��
'��((�: �-,<�,611,5���6=+.�!+69;+<5�+.0��-,<�,611,5 �B��-,<�5,611,5�+61�:5:+88<�12,1.5-3.5�3@�,>1�+0F3-.-./�5,611,�5<5,1?�,>+,�+61�3;.10�+.0�?+-.,+-.10�=<�,>1��+,-3.+8�!+69�
16A-41�����>1�43.5,6:4,-3.�+.0�36�6143.5,6:4,-3.��5>3:80�43.@36?�;-,>�+4417,10�834+8�1./-.116-./�76+4,-41�+.0�834+8�43.0-,-3.5����3:,1��:?=165����B����
HHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHHH
�������7+69�63+0�5<5,1?�43.,+-.5�,>351�63+05�;-,>-.�36�/-A-./�+44155�,3�+�7+69�36�3,>16�:.-,�3@�,>1��!�;>-4>�+61�+0?-.-5,1610�=<�,>1��!(�36�=<�,>1�16A-41�-.�433716+,-3.�;-,>�3,>16�
+/1.4-15����>1�+55-/.?1.,�3@�+�@:.4,-3.+8�48+55-@-4+,-3.���� �,3�+�7+69�63+0�-5�.3,�=+510�3.�,6+@@-4�A38:?15�36�015-/.�57110(�=:,�3.�,>1�-.,1.010�:51�36�@:.4,-3.�3@�,>+,�63+0�36�63:,1�
������>1�>-5,36-4�63:,1�.:?=16-./�5<5,1?�+853�-.48:010�+�����.:?=16�516-15�@36�-.,16761,-A1�63+05(�+.0�+�����516-15�@36�3.1B;+<�63+05����>161�+61�+77632-?+,18<�����63+05�
.+,-3.;-01�;>-4>�+61�015-/.+,10�=<�,>1�����+.0�����516-15����>1�.:?=165�@36�,>151�63+05�;-88�=1�?+-.,+-.10�@36�61736,-./�43.5-5,1.4<���3;1A16(�5-.41�,>151�-.,16761,-A1�+.0�
3.1B;+<�63:,15�+61�.3,�+5�481+68<�,-10�,3�+�5714-@-4�@:.4,-3.+8�48+55(�,>1�����+.0�����516-15�;-88�=1�0-543.,-.:10�@36�@:,:61�:51�
�����63:,1�.:?=165�+61�+55-/.10�,3��3.B�!��3:,15�,>+,�+61�,+,1(��3:.,<�36��-,<�3;.10�;>-4>�=36016(�,6+A1651(�36�763A-01�+44155�,3�!+69��+4-8-,-15�36��551,5���������3:,15�
+61�06-A1.�@36��!(�#-013�"3/�+.0��3+0��1+,:615�3.8<��
����������������������� �������������������������������������������� ��������� ������������������ �����������
������������� ���������
�������������� ������������������ �������� ����������������� ����������� ����� ������������������ ������������ ���!
������������� ��������"���#���������� � �$�%������������ �����&������� �$�'�'��(�������� �) ����� ��
�����)*�������
"������'������������#���'���
+��������������� �$�'�'���� �(����
,- ������������� �$�'�'��(���� .������������������� �$�'�'���� �(���� +�������'��������������#���'����-�����������/��0
���� �������������������� �������
��� �
����
���!
"�������
����
����
"�����#�
��#
$%����
��# ��������� $���
��������������
�� $���#�
" ��� ������
%� ��
&�'
������
%� ��
%����
����
�(�$�
�����)���������$%��������
���������������������������
����������������������
������
������ ����������� �������������� ����� ������������������������������
����������������������������
����� �����������
����������'���*++�����������������,��-���� �
����
���!
"�������
����
����
"�����#�
��#
$%����
��# ��������� $���
��������������
�� $���#�
" ��� ������
%� ��
&�'
������
%� ��
%����
����
�(�$�
��������������������
����������� ����������
������������������
����� ����������� ����������� ����� ���������� �����������
��������������������
����������� ����������
������������������
����� ����������� ����������� ����� ���������� �����������
��������������������
����������� ����������
������������������
����� ����������� ������������ ����� ���������� ����!������
Saratoga National Historical Park
Section 5
Paved Route Condition Rating Sheets
(CRS)
!
!
!Rte 0010
2
1
0
º* If the PCR rating is not available for a section, the SCR rating will be displayed. See appendix for definitions and formulas.
PCR(<=60)
Poor(61 - 84)
Fair(85 - 94)
Good(95 - 100)
Excellent No Data
ROUTE: 0010 ENTRANCE ROAD
SARA : SARATOGA NATIONAL HISTORICAL PARK
COLLECTED: 11/4/2008
NORTHEAST REGION TOTAL LENGTH: 2.64 Miles
Section Number 0 1 2
Section Length (mi) 1.00 1.00 0.64Traffic
AADT
SADT
ADT Date
Cross Section Information
Number of Lanes 1 2 2
Paved Width (ft) 19 19 19
Lane Width (ft) 9 9 9
Shoulder Width Right (ft) NC NC NC
Shoulder Width Left (ft) NC NC NC
Roadway Condition Information
SCR (Surface Condition Rating) 65 67 66
PCR (Pavement Condition Rating) 72 78 74
Distress Index Values
Alligator Cracking Index 100 100 100
Longitudinal Cracking Index 99 99 99
Tranverse Cracking Index 99 99 99
Patching Index 100 100 100
Rutting Index 68 68 67
Roughness Condition Index (RCI) 85 96 96
NC - Not Collected 5-1
Traffic data may be found at www.efl.fhwa.dot.gov
Click on PROGRAMS / NPS Traffic Data
(Note: Not all parks have traffic data)
RO
UT
E:
0010
EN
TR
AN
CE
RO
AD
! 0Rte
0100
º* If the PCR rating is not available for a section, the SCR rating will be displayed. See appendix for definitions and formulas.
PCR(<=60)
Poor(61 - 84)
Fair(85 - 94)
Good(95 - 100)
Excellent No Data
ROUTE: 0100 ROOSEVELT ROAD
SARA : SARATOGA NATIONAL HISTORICAL PARK
COLLECTED: 11/4/2008
NORTHEAST REGION TOTAL LENGTH: 0.11 Miles
Section Number 0
Section Length (mi) 0.11Traffic
AADT
SADT
ADT Date
Cross Section Information
Number of Lanes 1
Paved Width (ft) 11
Lane Width (ft) 11
Shoulder Width Right (ft) NC
Shoulder Width Left (ft) NC
Roadway Condition Information
SCR (Surface Condition Rating) 68
PCR (Pavement Condition Rating) 68
Distress Index Values
Alligator Cracking Index 100
Longitudinal Cracking Index 100
Tranverse Cracking Index 100
Patching Index 100
Rutting Index 68
Roughness Condition Index (RCI) NC
NC - Not Collected 5-2
Traffic data may be found at www.efl.fhwa.dot.gov
Click on PROGRAMS / NPS Traffic Data
(Note: Not all parks have traffic data)
RO
UT
E:
0100
RO
OS
EV
EL
TR
OA
D
!
0
Rte 0200
º* If the PCR rating is not available for a section, the SCR rating will be displayed. See appendix for definitions and formulas.
PCR(<=60)
Poor(61 - 84)
Fair(85 - 94)
Good(95 - 100)
Excellent No Data
ROUTE: 0200 TOUR ROAD TO STOP 3
SARA : SARATOGA NATIONAL HISTORICAL PARK
COLLECTED: 11/4/2008
NORTHEAST REGION TOTAL LENGTH: 0.53 Miles
Section Number 0
Section Length (mi) 0.53Traffic
AADT
SADT
ADT Date
Cross Section Information
Number of Lanes 2
Paved Width (ft) 24
Lane Width (ft) 12
Shoulder Width Right (ft) NC
Shoulder Width Left (ft) NC
Roadway Condition Information
SCR (Surface Condition Rating) 86
PCR (Pavement Condition Rating) 90
Distress Index Values
Alligator Cracking Index 100
Longitudinal Cracking Index 100
Tranverse Cracking Index 100
Patching Index 100
Rutting Index 86
Roughness Condition Index (RCI) 96
NC - Not Collected 5-3
Traffic data may be found at www.efl.fhwa.dot.gov
Click on PROGRAMS / NPS Traffic Data
(Note: Not all parks have traffic data)
RO
UT
E:
0200
TO
UR
RO
AD
TO
ST
OP
3
! 0Rte
0401
º* If the PCR rating is not available for a section, the SCR rating will be displayed. See appendix for definitions and formulas.
PCR(<=60)
Poor(61 - 84)
Fair(85 - 94)
Good(95 - 100)
Excellent No Data
ROUTE: 0401 HEADQUARTERS LOOP ROAD
SARA : SARATOGA NATIONAL HISTORICAL PARK
COLLECTED: 11/4/2008
NORTHEAST REGION TOTAL LENGTH: 0.08 Miles
Section Number 0
Section Length (mi) 0.08Traffic
AADT
SADT
ADT Date
Cross Section Information
Number of Lanes 2
Paved Width (ft) 19
Lane Width (ft) 10
Shoulder Width Right (ft) NC
Shoulder Width Left (ft) NC
Roadway Condition Information
SCR (Surface Condition Rating) 46
PCR (Pavement Condition Rating) 46
Distress Index Values
Alligator Cracking Index 100
Longitudinal Cracking Index 95
Tranverse Cracking Index 99
Patching Index 100
Rutting Index 53
Roughness Condition Index (RCI) NC
NC - Not Collected 5-4
Traffic data may be found at www.efl.fhwa.dot.gov
Click on PROGRAMS / NPS Traffic Data
(Note: Not all parks have traffic data)
RO
UT
E:
0401
HE
AD
QU
AR
TE
RS
LO
OP
RO
AD
!
!
!
!
!
!
4
3
2
1
0
Rte 0500
º* If the PCR rating is not available for a section, the SCR rating will be displayed. See appendix for definitions and formulas.
PCR(<=60)
Poor(61 - 84)
Fair(85 - 94)
Good(95 - 100)
Excellent No Data
ROUTE: 0500 TOUR ROAD
SARA : SARATOGA NATIONAL HISTORICAL PARK
COLLECTED: 11/4/2008
NORTHEAST REGION TOTAL LENGTH: 7.35 Miles
Section Number 0 1 2 3 4
Section Length (mi) 1.00 1.00 1.00 1.00 1.00Traffic
AADT
SADT
ADT Date
Cross Section Information
Number of Lanes 1 1 1 1 1
Paved Width (ft) 16 16 17 16 16
Lane Width (ft) 12 12 13 12 12
Shoulder Width Right (ft) NC NC NC NC NC
Shoulder Width Left (ft) NC NC NC NC NC
Roadway Condition Information
SCR (Surface Condition Rating) 88 94 73 72 65
PCR (Pavement Condition Rating) 91 94 79 80 74
Distress Index Values
Alligator Cracking Index 100 100 100 100 100
Longitudinal Cracking Index 100 100 100 100 99
Tranverse Cracking Index 100 100 100 100 100
Patching Index 100 100 100 100 100
Rutting Index 89 94 73 73 66
Roughness Condition Index (RCI) 96 95 90 92 86
NC - Not Collected 5-5
Traffic data may be found at www.efl.fhwa.dot.gov
Click on PROGRAMS / NPS Traffic Data
(Note: Not all parks have traffic data)
RO
UT
E:
0500
TO
UR
RO
AD
!
!
!
7
65
Rte 0500
º* If the PCR rating is not available for a section, the SCR rating will be displayed. See appendix for definitions and formulas.
PCR(<=60)
Poor(61 - 84)
Fair(85 - 94)
Good(95 - 100)
Excellent No Data
ROUTE: 0500 TOUR ROAD
SARA : SARATOGA NATIONAL HISTORICAL PARK
COLLECTED: 11/4/2008
NORTHEAST REGION TOTAL LENGTH: 7.35 Miles
Section Number 5 6 7
Section Length (mi) 1.00 1.00 0.35Traffic
AADT
SADT
ADT Date
Cross Section Information
Number of Lanes 1 1 1
Paved Width (ft) 16 16 12
Lane Width (ft) 12 13 12
Shoulder Width Right (ft) NC NC NC
Shoulder Width Left (ft) NC NC NC
Roadway Condition Information
SCR (Surface Condition Rating) 66 70 72
PCR (Pavement Condition Rating) 76 76 77
Distress Index Values
Alligator Cracking Index 100 100 100
Longitudinal Cracking Index 100 100 99
Tranverse Cracking Index 100 100 100
Patching Index 100 100 100
Rutting Index 66 70 73
Roughness Condition Index (RCI) 91 89 84
NC - Not Collected 5-6
Traffic data may be found at www.efl.fhwa.dot.gov
Click on PROGRAMS / NPS Traffic Data
(Note: Not all parks have traffic data)
RO
UT
E:
0500
TO
UR
RO
AD
Saratoga National Historical Park
Section 6
Manually Rated Paved Route
Condition Rating Sheets (MRR)
Section 6: Manually Rated Paved Route Condition Rating Sheets
No data available for this section.
Saratoga National Historical Park
Section 7
Parking Area Condition Rating Sheets
SARATOGA NATIONAL HISTORICAL PARK
Route 0900
VISITOR CENTER PARKINGFROM ROUTE 0010 (ENTRANCE ROAD) AT MP 2.56 (ON LEFT)
TO ROUTE 0500 (TOUR ROAD) AT START
Route
Number
Public /
NonPublic Lane Miles *
0900 PUBLIC 0.64
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 6 0 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-1
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
37,418
Surface Type
AS
PCR
FAIR/73
º360 0 360180
Feet
Rte 0010
Rte
050
0
Rte
010
0
Rte0401
Rte 0900
Rte 0902
Rte 0901
Rte 0903Z
Rte 0918Z Rte 0917Z
SARATOGA NATIONAL HISTORICAL PARK
Route 0901
ROOSEVELT ROAD PARKINGADJACENT TO ROUTE 0100 (ROOSEVELT ROAD) AT MP 0.10 (ON RIGHT)
Route
Number
Public /
NonPublic Lane Miles *
0901 PUBLIC 0.02
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 0 0 0 NO CURB
* Lane miles are based on 11' lane widths
7-2
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
1,347
º60 0 6030
Feet
Rte
01
00
Rte 0901
SARATOGA NATIONAL HISTORICAL PARK
Route 0902
MAINTENANCE AREAFROM ROUTE 0010 (ENTRANCE ROAD) AT MP 2.58 (ON LEFT)
TO PARKING
Route
Number
Public /
NonPublic Lane Miles *
0902 NONPUBLIC 0.35
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 2 2 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-3
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
20,566
º240 0 240120
Feet
Rte 0010
Rte
0500
Rte 0401
Rte 0900
Rte 0902
SARATOGA NATIONAL HISTORICAL PARK
Route 0903ZZ
SUPPORT FACILITY PARKING AREASFROM ROUTE 0401 (HEADQUARTERS LOOP ROAD) AT MP 0.04 (ON RIGHT)
TO ROUTE 0401 (HEADQUARTERS LOOP ROAD) AT MP 0.07 (ON RIGHT)Summary Record
Route
Number
Public /
NonPublic Lane Miles *
0903ZZ NONPUBLIC 0.07
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 0 0 0 NO CURB
* Lane miles are based on 11' lane widths
7-4
Surface Type
AS
PCR
SUMMARY/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
3,930
º110 0 11055
Feet
Rte 0010
Rte 0401Rte 0903Z
Rte 0918Z
Rte 0917Z
SARATOGA NATIONAL HISTORICAL PARK
Route 0903Z
SUPPORT FACILITY PARKING AADJACENT TO ROUTE 0401 (HEADQUARTERS LOOP ROAD) AT MP 0.04 (ON RIGHT)
Subcomponent Record
Route
Number
Public /
NonPublic Lane Miles *
0903Z NONPUBLIC 0.03
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 0 0 0 NO CURB
* Lane miles are based on 11' lane widths
7-5
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
1,427
º110 0 11055
Feet
Rte 0010
Rte 0401Rte 0903Z
Rte 0918Z
Rte 0917Z
SARATOGA NATIONAL HISTORICAL PARK
Route 0917Z
SUPPORT FACILITY PARKING BADJACENT TO ROUTE 0401 (HEADQUARTERS LOOP ROAD) AT MP 0.05 (ON RIGHT)
Subcomponent Record
Route
Number
Public /
NonPublic Lane Miles *
0917Z NONPUBLIC 0.02
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 0 0 0 NO CURB
* Lane miles are based on 11' lane widths
7-6
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
1,239
º110 0 11055
Feet
Rte 0010
Rte 0401Rte 0903Z
Rte 0918Z
Rte 0917Z
SARATOGA NATIONAL HISTORICAL PARK
Route 0918Z
SUPPORT FACILITY PARKING CADJACENT TO ROUTE 0401 (HEADQUARTERS LOOP ROAD) AT MP 0.07 (ON RIGHT)
Subcomponent Record
Route
Number
Public /
NonPublic Lane Miles *
0918Z NONPUBLIC 0.02
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 0 0 0 NO CURB
* Lane miles are based on 11' lane widths
7-7
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
1,264
º110 0 11055
Feet
Rte 0010
Rte 0401Rte 0903Z
Rte 0918Z
Rte 0917Z
SARATOGA NATIONAL HISTORICAL PARK
Route 0904
STOP 1 PARKINGFROM ROUTE 0500 (TOUR ROAD) AT MP 0.46 (ON LEFT)
TO ROUTE 0500 (TOUR ROAD) AT MP 0.51 (ON LEFT)
Route
Number
Public /
NonPublic Lane Miles *
0904 PUBLIC 0.15
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 0 0 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-8
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
8,602
º180 0 18090
Feet
Rte
0500
Rte 0904
SARATOGA NATIONAL HISTORICAL PARK
Route 0905
STOP 2 PARKINGFROM ROUTE 0500 (TOUR ROAD) AT MP 2.04 (ON LEFT)
TO ROUTE 0500 (TOUR ROAD) AT MP 2.08 (ON LEFT)
Route
Number
Public /
NonPublic Lane Miles *
0905 PUBLIC 0.15
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 2 0 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-9
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
8,445
º180 0 18090
Feet
Rte 0905
Rte
0500
SARATOGA NATIONAL HISTORICAL PARK
Route 0907
STOP 3 PARKINGFROM ROUTE 0200 (TOUR ROAD TO STOP 3) AT END
TO PARKING
Route
Number
Public /
NonPublic Lane Miles *
0907 PUBLIC 0.40
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 1 0 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-10
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
22,949
º290 0 290145
Feet
Rte 0907
Rte
0200
SARATOGA NATIONAL HISTORICAL PARK
Route 0908
STOP 4 PARKINGFROM ROUTE 0500 (TOUR ROAD) AT MP 3.30 (ON RIGHT)
TO ROUTE 0500 (TOUR ROAD) AT MP 3.34 (ON RIGHT)
Route
Number
Public /
NonPublic Lane Miles *
0908 PUBLIC 0.15
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 2 0 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-11
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
8,523
º150 0 15075
Feet
Rte
0500
Rte 0908
SARATOGA NATIONAL HISTORICAL PARK
Route 0909
STOP 5 PARKINGFROM ROUTE 0500 (TOUR ROAD) AT MP 3.85 (ON LEFT)
TO ROUTE 0500 (TOUR ROAD) AT MP 3.89 (ON LEFT)
Route
Number
Public /
NonPublic Lane Miles *
0909 PUBLIC 0.15
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 1 0 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-12
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
8,590
º250 0 250125
Feet
Rte 0909
Rte
0500
SARATOGA NATIONAL HISTORICAL PARK
Route 0910
STOP 6 PARKINGFROM ROUTE 0500 (TOUR ROAD) AT MP 4.58 (ON RIGHT)
TO ROUTE 0500 (TOUR ROAD) AT MP 4.64 (ON RIGHT)
Route
Number
Public /
NonPublic Lane Miles *
0910 PUBLIC 0.20
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 1 0 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-13
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
11,497
º200 0 200100
Feet
Rte 0500
Rte 0910
SARATOGA NATIONAL HISTORICAL PARK
Route 0911
STOP 7 PARKINGFROM ROUTE 0500 (TOUR ROAD) AT MP 4.89 (ON LEFT)
TO ROUTE 0500 (TOUR ROAD) AT MP 4.94 (ON LEFT)
Route
Number
Public /
NonPublic Lane Miles *
0911 PUBLIC 0.17
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 1 0 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-14
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
9,831
º200 0 200100
Feet
Rte
0500
Rte 0911
SARATOGA NATIONAL HISTORICAL PARK
Route 0912
STOP 8 PARKINGFROM ROUTE 0500 (TOUR ROAD) AT MP 6.07 (ON RIGHT)
TO ROUTE 0500 (TOUR ROAD) AT MP 6.12 (ON RIGHT)
Route
Number
Public /
NonPublic Lane Miles *
0912 PUBLIC 0.15
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 1 0 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-15
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
8,428
º190 0 19095
Feet
Rte
05
00
Rte 0912
SARATOGA NATIONAL HISTORICAL PARK
Route 0913
STOP 9 PARKINGFROM ROUTE 0500 (TOUR ROAD) AT MP 6.79 (ON RIGHT)
TO PARKING
Route
Number
Public /
NonPublic Lane Miles *
0913 PUBLIC 0.41
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 2 0 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-16
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
23,885
º300 0 300150
Feet
Rte 0010
Rte
0500Rte 0913
SARATOGA NATIONAL HISTORICAL PARK
Route 0914
STOP 10 PARKINGFROM ROUTE 0500 (TOUR ROAD) AT MP 6.88 (ON RIGHT)
TO ROUTE 0500 (TOUR ROAD) AT MP 6.91 (ON RIGHT)
Route
Number
Public /
NonPublic Lane Miles *
0914 PUBLIC 0.13
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 0 0 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-17
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
7,491
º150 0 15075
Feet
Rte
0500
Rte 0914
SARATOGA NATIONAL HISTORICAL PARK
Route 0915
SCHUYLER ESTATE PARKINGFROM U.S. HIGHWAY 4
TO PARKING
Route
Number
Public /
NonPublic Lane Miles *
0915 PUBLIC 0.27
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 0 0 1 NO CURB
* Lane miles are based on 11' lane widths
7-18
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
15,926
º290 0 290145
Feet
Rte 0915
Rte 0919
SARATOGA NATIONAL HISTORICAL PARK
Route 0916
MONUMENT PARKINGFROM CEMETERY ROAD
TO PARKING
Route
Number
Public /
NonPublic Lane Miles *
0916 PUBLIC 0.23
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 2 0 0
CONCRETE
CURB
* Lane miles are based on 11' lane widths
7-19
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
13,378
º230 0 230115
Feet
Rte 0916
SARATOGA NATIONAL HISTORICAL PARK
Route 0919
SCHUYLER ESTATE RESIDENCE PARKINGFROM ROUTE 0915 (SCHUYLER ESTATE PARKING)
TO PARKING
Route
Number
Public /
NonPublic Lane Miles *
0919 NONPUBLIC 0.05
Culverts Drop Inlets Gates
Fire
Hydrants Curb
0 1 0 0 NO CURB
* Lane miles are based on 11' lane widths
7-20
Surface Type
AS
PCR
GOOD/90
Curb & Gutter
NO CURB AND
GUTTER
Date Visited
9/23/2008
Area (sq ft)
2,646
º170 0 17085
Feet
Rte 0915
Rte 0919
Saratoga National Historical Park
Section 8
Parkwide / Route Maintenance
Features Summaries
SARA: PARKWIDE MAINTENANCE FEATURES SUMMARY
FEATURE LINEAR FEET COUNT
BARRIER 1,003 --
BOLLARD 0 --
BRIDGE -- 3
CABLE 0 --
CATTLE GUARD -- 0
CULVERT -- 2
CURB 1,241 --
DROP INLET -- 22
FIRE HYDRANT -- 1
GATE -- 5
GUARD/GUIDE RAIL 1,003 --
GUARD/GUIDE WALL 0 --
INTERSECTION -- 55
LOW WATER CROSSING 0 0
MILE MARKER -- 0
OVERPASS -- 1
OVERHEAD SIGN -- 0
PARK BOUNDARY -- 0
PAVED DITCH 945 --
PULLOUT -- 5
RAILROAD CROSSING -- 0
RETAINING WALL 0 0
SIGN -- 131
STATE BOUNDARY -- 0
TEMPORARY BARRIER 0 --
TRAFFIC LIGHT -- 0
TUNNEL 0 0
TURNOUT 0 --
Data Collected 11/4/2008
Notice: Drop Inlets along ARAN-driven routes were NOT marked by NPS nor were they
inventoried by RIP. Culverts that lack a BIP assigned Structure Number along ARAN-
driven routes were NOT marked by NPS nor were they inventoried by RIP. Culverts that
have a BIP assigned Structure Number along ARAN-driven routes were marked by NPS
and were inventoried by RIP. Culverts and Drop Inlets that are associated with Manually
Rated Routes and Paved Parking Areas are included in the Cycle 4 counts. To view the
Cycle 3 culvert and drop inlet inventory, please refer to the Cycle 3 RIP Report.
8-1
SARA: ROUTE MAINTENANCE FEATURES SUMMARY
FEATURE RO
UT
E 0
01
0
EN
TR
AN
CE
RO
AD
RO
UT
E 0
10
0
RO
OS
EV
EL
T R
OA
D
RO
UT
E 0
20
0
TO
UR
RO
AD
TO
ST
OP
3
RO
UT
E 0
40
1
HE
AD
QU
AR
TE
RS
LO
OP
RO
AD
RO
UT
E 0
50
0
TO
UR
RO
AD
UNIT
BARRIER LINEAR FEET
BOLLARD LINEAR FEET
BRIDGE EACH
CABLE LINEAR FEET
CATTLE GUARD EACH
CULVERT EACH
CURB LINEAR FEET
DROP INLET EACH
FIRE HYDRANT EACH
GATE EACH
GUARD/GUIDE RAIL LINEAR FEET
GUARD/GUIDE WALL LINEAR FEET
INTERSECTION EACH
LOW WATER CROSSING EACH
LOW WATER CROSSING LINEAR FEET
MILE MARKER EACH
OVERHEAD SIGN EACH
OVERPASS EACH
PARK BOUNDARY EACH
PAVED DITCH LINEAR FEET
PULLOUT EACH
RAILROAD CROSSING EACH
RETAINING WALL EACH
RETAINING WALL LINEAR FEET
SIGN EACH
STATE BOUNDARY EACH
TEMPORARY BARRIER LINEAR FEET
TRAFFIC LIGHT EACH
TUNNEL EACH
TUNNEL LINEAR FEET
TURNOUT LINEAR FEET
Data Collected 11/4/2008
00 0 0 0
0 0 0 0
0
14
422
0
0
0
0
422
0
0
2
0
0
232
1
0
0
0
0
0
1
586
0
Notice: Drop Inlets along ARAN-driven routes were NOT marked by NPS nor were they inventoried by RIP. Culverts that
lack a BIP assigned Structure Number along ARAN-driven routes were NOT marked by NPS nor were they inventoried by
RIP. Culverts that have a BIP assigned Structure Number along ARAN-driven routes were marked by NPS and were
inventoried by RIP. To view the Cycle 3 culvert and drop inlet inventory for ARAN-driven routes, please refer to the Cycle 3
RIP Report.
0
0
65
0
0
0 0
0
0
0
0 0 0
0
0
0
1
0
0
0
0
0
0
5
0
0
0
0
0
8
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3
0
0
0
0
0
0
0
0
0
0
0
0
0
5
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
8
0
0
0
0
0
1
0
0
0
0
0
0
0
0
2
0
0
1
581
0
25
0
0
0
0
0
0
0
0
359
5
0
0
0
0
0
581
0
1
0
0
1,008
52
0
8-2
SARA: STRUCTURE LIST
ROUTE
NUMBER
FUNCTIONAL
CLASS
MILEPOST
START
MILEPOST
END FEATURE
STRUCTURE
NUMBER
0010 1 0.544 0.552 BRIDGE 1910-002
0010 1 0.66 0.667 BRIDGE 1910-003
0010 1 0.679 0.679 OVERPASS 1910-001
0010 1 0.84 0.84 CULVERT 1910-005
0500 3 3.636 3.636 CULVERT 1910-004
0500 3 6.413 6.451 BRIDGE 1910-001
Data Collected 11/4/2008 8-3
Saratoga National Historical Park
Section 9
Park Route Maintenance Features
Road Logs
FROM
MILEPOST
TO
MILEPOST FEATURE SIDE COMMENT
ROUTE 0010: ENTRANCE ROAD
SARA: ROUTE MAINTENANCE FEATURES ROAD LOG
Culverts and drop inlets were marked by NPS and
inventoried by RIP in Cycle 4, therefore the culvert and drop inlet
count below includes those on ARAN-driven routes, Manually
Rated Routes and in Paved Parking Areas.
Notice:
0.000 ROUTE BEGIN N/A FROM U.S. HIGHWAY 40.000
0.000 INTERSECTION N/A PAVED ROUTE (U.S. HIGHWAY 4)0.000
0.000 INTERSECTION LEFT PAVED ROUTE (U.S. HIGHWAY 4)0.000
0.043 SIGN RIGHT REGULATORY, NO PARKING ANY TIME0.043
0.079 SIGN RIGHT REGULATORY, NO PARKING ANY TIME0.079
0.091 SIGN RIGHT REGULATORY, STOP0.091
0.095 SIGN RIGHT GUIDE, SCHUYLER HOUSE0.095
0.095 SIGN RIGHT GUIDE, SCHUYLERVILL 7 STILLWATER 4 MECHANICVILLE 70.095
0.095 SIGN RIGHT GUIDE, SARATOGA MONUMENT0.095
0.095 SIGN RIGHT GUIDE, GRAPHIC SIGN, NO TEXT0.095
0.099 INTERSECTION RIGHT PAVED ROUTE (U.S. HIGHWAY 4)0.099
0.099 INTERSECTION LEFT PAVED ROUTE (U.S. HIGHWAY 4)0.099
0.111 SIGN RIGHT GUIDE, GRAPHIC SIGN, NO TEXT0.111
0.111 SIGN RIGHT REGULATORY, 40.111
0.111 SIGN RIGHT REGULATORY, SOUTH0.111
0.111 SIGN RIGHT REGULATORY, NORTH0.111
0.111 SIGN RIGHT REGULATORY, GRAPHIC SIGN, NO TEXT0.111
0.111 SIGN RIGHT REGULATORY, GRAPHIC SIGN, NO TEXT0.111
0.111 SIGN RIGHT REGULATORY, 40.111
0.111 SIGN RIGHT GUIDE, TO0.111
0.111 SIGN RIGHT GUIDE, TO0.111
0.111 SIGN RIGHT GUIDE, SOUTH0.111
0.111 SIGN RIGHT GUIDE, NORTH0.111
0.111 SIGN RIGHT GUIDE, INTERSTATE 870.111
0.111 SIGN RIGHT GUIDE, GRAPHIC SIGN, NO TEXT0.111
0.111 SIGN RIGHT GUIDE, INTERSTATE 870.111
0.114 SIGN RIGHT REGULATORY, STOP0.114
0.116 INTERSECTION RIGHT PAVED ROUTE (U.S. HIGHWAY 4) SPUR0.116
0.122 SIGN RIGHT GUIDE, SARATOGA NATIONAL HISTORICAL PARK0.122
0.133 SIGN RIGHT REGULATORY, LOAD LIMIT 20 TONS0.133
9-1Data Collected 11/4/2008
FROM
MILEPOST
TO
MILEPOST FEATURE SIDE COMMENT
ROUTE 0010: ENTRANCE ROAD
SARA: ROUTE MAINTENANCE FEATURES ROAD LOG
Culverts and drop inlets were marked by NPS and
inventoried by RIP in Cycle 4, therefore the culvert and drop inlet
count below includes those on ARAN-driven routes, Manually
Rated Routes and in Paved Parking Areas.
Notice:
0.133 SIGN RIGHT REGULATORY, AREA SPEED LIMIT 300.133
0.175 PAVED DITCH RIGHT0.136
0.145 SIGN RIGHT REGULATORY, DO NOT FEED WILDLIFE0.145
0.145 SIGN RIGHT REGULATORY, NO PARKING ON ROADWAY PARKING
PERMITTED IN DESIGNATED AREAS ONLY
0.145
0.208 SIGN RIGHT WARNING, STOP AHEAD0.208
0.314 PAVED DITCH RIGHT0.242
0.553 GUARD/GUIDE RAIL LEFT0.541
0.555 GUARD/GUIDE RAIL RIGHT0.543
0.552 BRIDGE N/A 1910-002 (KROMA KILL BRIDGE #2)0.544
0.632 GUARD/GUIDE RAIL LEFT0.628
0.639 GUARD/GUIDE RAIL LEFT0.634
0.668 GUARD/GUIDE RAIL RIGHT0.652
0.676 GUARD/GUIDE RAIL LEFT0.659
0.667 BRIDGE N/A 1910-003 (KROMA KILL BRIDGE #3)0.660
0.679 OVERPASS N/A 1910-001 (KROMA KILL BRIDGE #1)0.679
0.740 SIGN RIGHT REGULATORY, AREA SPEED LIMIT 300.740
0.759 SIGN RIGHT REGULATORY, DO NOT FEED WILDLIFE0.759
0.759 SIGN RIGHT REGULATORY, NO PARKING ON ROADWAY PARKING
PERMITTED IN DESIGNATED AREAS ONLY
0.759
0.766 INTERSECTION RIGHT ROUTE 0500 (TOUR ROAD)0.766
0.796 SIGN RIGHT GUIDE, VISITOR CENTER PARK HEADQUARTERS 2 1/2 KM 1 1/2
MI
0.796
0.826 GUARD/GUIDE RAIL LEFT0.812
0.820 INTERSECTION RIGHT PAVED ROUTE (PHILLIPS ROAD)0.820
0.828 SIGN RIGHT REGULATORY, COMMERCIAL VEHICLES EXCLUDED0.828
0.828 SIGN RIGHT REGULATORY, NO TRUCKS0.828
0.840 CULVERT N/A 1910-005 (KROMA KILL CULVERT)0.840
0.855 SIGN RIGHT REGULATORY, NO PARKING ON ROADWAY PARKING
PERMITTED IN DESIGNATED AREAS ONLY
0.855
0.870 SIGN RIGHT REGULATORY, AREA SPEED LIMIT 300.870
2.234 SIGN RIGHT WARNING, GRAPHIC SIGN, NO TEXT2.234
9-2Data Collected 11/4/2008
FROM
MILEPOST
TO
MILEPOST FEATURE SIDE COMMENT
ROUTE 0010: ENTRANCE ROAD
SARA: ROUTE MAINTENANCE FEATURES ROAD LOG
Culverts and drop inlets were marked by NPS and
inventoried by RIP in Cycle 4, therefore the culvert and drop inlet
count below includes those on ARAN-driven routes, Manually
Rated Routes and in Paved Parking Areas.
Notice:
2.437 SIGN RIGHT WARNING, STOP AHEAD2.437
2.512 SIGN RIGHT REGULATORY, AREA SPEED LIMIT 302.512
2.558 CURB RIGHT2.522
2.531 SIGN RIGHT REGULATORY, DO NOT FEED WILDLIFE2.531
2.531 SIGN RIGHT REGULATORY, NO PARKING ON ROADWAY PARKING
PERMITTED IN DESIGNATED AREAS ONLY
2.531
2.534 SIGN RIGHT GUIDE, GRAPHIC SIGN, NO TEXT2.534
2.534 SIGN RIGHT GUIDE, GRAPHIC SIGN, NO TEXT2.534
2.534 SIGN RIGHT GUIDE, PARKING2.534
2.534 SIGN RIGHT REGULATORY, STOP2.534
2.535 SIGN RIGHT GUIDE, U.S. 42.535
2.535 SIGN RIGHT REGULATORY, RESERVED PARKING2.535
2.538 INTERSECTION LEFT ROUTE 0100 (ROOSEVELT ROAD)2.538
2.540 INTERSECTION LEFT ROUTE 0900 (VISITOR CENTER PARKING)2.540
2.542 SIGN LEFT GUIDE, ROOSEVELT RD2.542
2.544 SIGN RIGHT REGULATORY, STOP2.544
2.557 CURB-AND-GUTTER LEFT2.549
2.556 SIGN LEFT REGULATORY, DO NOT ENTER2.556
2.557 INTERSECTION LEFT ROUTE 0900 (VISITOR CENTER PARKING)2.557
2.558 SIGN RIGHT REGULATORY, ONE WAY2.558
2.565 SIGN LEFT REGULATORY, DO NOT ENTER2.565
2.565 SIGN LEFT REGULATORY, ONE WAY2.565
2.575 SIGN RIGHT GUIDE, VISITOR CENTER2.575
2.579 INTERSECTION LEFT ROUTE 0902 (MAINTENANCE AREA)2.579
2.579 INTERSECTION RIGHT ROUTE 0401 (HEADQUARTERS LOOP ROAD)2.579
2.588 SIGN LEFT GUIDE, PARK HEADQUARTERS RANGER STATION DELIVERIES
MON-FRI
2.588
2.589 SIGN RIGHT GUIDE, PARK HEADQUARTERS RANGER STATION DELIVERIES
MON-FRI
2.589
2.609 SIGN RIGHT REGULATORY, DO NOT FEED WILDLIFE2.609
2.621 SIGN RIGHT REGULATORY, AREA SPEED LIMIT 302.621
9-3Data Collected 11/4/2008
FROM
MILEPOST
TO
MILEPOST FEATURE SIDE COMMENT
ROUTE 0010: ENTRANCE ROAD
SARA: ROUTE MAINTENANCE FEATURES ROAD LOG
Culverts and drop inlets were marked by NPS and
inventoried by RIP in Cycle 4, therefore the culvert and drop inlet
count below includes those on ARAN-driven routes, Manually
Rated Routes and in Paved Parking Areas.
Notice:
2.625 SIGN RIGHT REGULATORY, 322.625
2.625 SIGN RIGHT REGULATORY, GRAPHIC SIGN, NO TEXT2.625
2.629 SIGN RIGHT REGULATORY, STOP2.629
2.640 SIGN N/A GUIDE, SARATOGA MONUMENT2.640
2.640 SIGN N/A GUIDE, SCHUYLER HOUSE2.640
2.640 SIGN N/A GUIDE, N.Y. 32 STILLWATER 7 KM 4 MI SCHUYLERVILLE 12
KM 7 MI
2.640
2.640 SIGN N/A GUIDE, GRAPHIC SIGN, NO TEXT2.640
2.640 INTERSECTION RIGHT PAVED ROUTE (STATE ROUTE 32)2.640
2.640 INTERSECTION LEFT PAVED ROUTE (STATE ROUTE 32)2.640
2.640 ROUTE END N/A TO STATE ROUTE 322.640
9-4Data Collected 11/4/2008
FROM
MILEPOST
TO
MILEPOST FEATURE SIDE COMMENT
ROUTE 0100: ROOSEVELT ROAD
SARA: ROUTE MAINTENANCE FEATURES ROAD LOG
Culverts and drop inlets were marked by NPS and
inventoried by RIP in Cycle 4, therefore the culvert and drop inlet
count below includes those on ARAN-driven routes, Manually
Rated Routes and in Paved Parking Areas.
Notice:
0.000 ROUTE BEGIN N/A FROM ROUTE 0010 (ENTRANCE ROAD) AT MP 2.54 (ON LEFT)0.000
0.000 INTERSECTION N/A ROUTE 0010 (ENTRANCE ROAD)0.000
0.000 INTERSECTION RIGHT ROUTE 0900 (VISITOR CENTER PARKING)0.000
0.000 INTERSECTION LEFT ROUTE 0010 (ENTRANCE ROAD)0.000
0.003 SIGN RIGHT REGULATORY, STOP0.003
0.006 SIGN RIGHT GUIDE, PARKING0.006
0.006 SIGN RIGHT GUIDE, GRAPHIC SIGN, NO TEXT0.006
0.006 GATE N/A0.006
0.006 SIGN RIGHT GUIDE, GRAPHIC SIGN, NO TEXT0.006
0.025 SIGN RIGHT WARNING, SLOW CHILDREN0.025
0.055 SIGN RIGHT WARNING, SLOW CHILDREN0.055
0.083 SIGN RIGHT REGULATORY, SPEED LIMIT 150.083
0.099 INTERSECTION RIGHT ROUTE 0901 (ROOSEVELT ROAD PARKING)0.099
0.110 INTERSECTION N/A ROUTE 0100 (ROOSEVELT ROAD)0.110
0.110 SIGN N/A REGULATORY, NO PARKING0.110
0.110 ROUTE END N/A TO END OF PAVEMENT0.110
9-5Data Collected 11/4/2008
FROM
MILEPOST
TO
MILEPOST FEATURE SIDE COMMENT
ROUTE 0200: TOUR ROAD TO STOP 3
SARA: ROUTE MAINTENANCE FEATURES ROAD LOG
Culverts and drop inlets were marked by NPS and
inventoried by RIP in Cycle 4, therefore the culvert and drop inlet
count below includes those on ARAN-driven routes, Manually
Rated Routes and in Paved Parking Areas.
Notice:
0.000 ROUTE BEGIN N/A FROM ROUTE 0500 (TOUR ROAD) AT MP 2.60 (ON RIGHT)0.000
0.000 INTERSECTION N/A ROUTE 0500 (TOUR ROAD)0.000
0.000 INTERSECTION RIGHT ROUTE 0500 (TOUR ROAD)0.000
0.007 SIGN RIGHT WARNING, GRAPHIC SIGN, NO TEXT0.007
0.015 SIGN RIGHT REGULATORY, GRAPHIC SIGN, NO TEXT0.015
0.041 SIGN RIGHT WARNING, GRAPHIC SIGN, NO TEXT0.041
0.041 SIGN RIGHT WARNING, GRAPHIC SIGN, NO TEXT0.041
0.507 SIGN RIGHT GUIDE, AMERICAN RIVER FORTIFICATIONS0.507
0.530 INTERSECTION N/A ROUTE 0907 (STOP 3 PARKING)0.530
0.530 ROUTE END N/A TO ROUTE 0907 (STOP 3 PARKING)0.530
9-6Data Collected 11/4/2008
FROM
MILEPOST
TO
MILEPOST FEATURE SIDE COMMENT
ROUTE 0401: HEADQUARTERS LOOP ROAD
SARA: ROUTE MAINTENANCE FEATURES ROAD LOG
Culverts and drop inlets were marked by NPS and
inventoried by RIP in Cycle 4, therefore the culvert and drop inlet
count below includes those on ARAN-driven routes, Manually
Rated Routes and in Paved Parking Areas.
Notice:
0.000 ROUTE BEGIN N/A FROM ROUTE 0010 (ENTRANCE ROAD) AT MP 2.58 (ON RIGHT)0.000
0.000 INTERSECTION LEFT ROUTE 0010 (ENTRANCE ROAD)0.000
0.000 INTERSECTION RIGHT ROUTE 0010 (ENTRANCE ROAD)0.000
0.027 INTERSECTION LEFT ROUTE 0401 (HEADQUARTERS LOOP ROAD)0.027
0.043 INTERSECTION RIGHT ROUTE 0903Z (SUPPORT FACILITY PARKING A)0.043
0.047 SIGN RIGHT REGULATORY, NO PARKING0.047
0.052 INTERSECTION RIGHT ROUTE 0917Z (SUPPORT FACILITY PARKING B)0.052
0.069 INTERSECTION RIGHT ROUTE 0918Z (SUPPORT FACILITY PARKING C)0.069
0.080 INTERSECTION LEFT ROUTE 0401 (HEADQUARTERS LOOP ROAD)0.080
0.080 INTERSECTION N/A ROUTE 0401 (HEADQUARTERS LOOP ROAD)0.080
0.080 ROUTE END N/A TO END OF LOOP0.080
9-7Data Collected 11/4/2008
FROM
MILEPOST
TO
MILEPOST FEATURE SIDE COMMENT
ROUTE 0500: TOUR ROAD
SARA: ROUTE MAINTENANCE FEATURES ROAD LOG
Culverts and drop inlets were marked by NPS and
inventoried by RIP in Cycle 4, therefore the culvert and drop inlet
count below includes those on ARAN-driven routes, Manually
Rated Routes and in Paved Parking Areas.
Notice:
0.000 ROUTE BEGIN N/A FROM ROUTE 0900 (VISITOR CENTER PARKING)0.000
0.000 INTERSECTION N/A ROUTE 0900 (VISITOR CENTER PARKING)0.000
0.020 SIGN RIGHT GUIDE, GRAPHIC SIGN, NO TEXT0.020
0.020 SIGN RIGHT REGULATORY, LOAD LIMIT 20 TONS0.020
0.020 SIGN RIGHT REGULATORY, NOTICE NO IN-LINE SKATING0.020
0.023 GATE N/A0.023
0.023 SIGN N/A GUIDE, GROUNDS OPEN SUNRISE-SUNSET0.023
0.023 SIGN N/A REGULATORY, NO PARKING ANY TIME0.023
0.024 SIGN RIGHT REGULATORY, HUNTING PROHIBITED ON NATIONAL PARK
LANDS NOTICE TO HIKERS
0.024
0.039 SIGN RIGHT REGULATORY, DO NOT FEED WILDLIFE0.039
0.049 SIGN RIGHT REGULATORY, AREA SPEED LIMIT 300.049
0.146 INTERSECTION LEFT ROUTE 0410 (VISITOR CENTER SERVICE ROAD)0.146
0.151 SIGN RIGHT REGULATORY, WATCH FOR OPPOSING EMERGENCY
VEHICLES
0.151
0.151 SIGN RIGHT GUIDE, BICYCLES MUST OBEY TRAFFIC LAWS0.151
0.427 SIGN RIGHT GUIDE, FREEMAN FARM OVERLOOK STOP 10.427
0.457 INTERSECTION LEFT ROUTE 0904 (STOP 1 PARKING)0.457
0.514 INTERSECTION LEFT ROUTE 0904 (STOP 1 PARKING)0.514
0.515 SIGN RIGHT REGULATORY, ONE WAY0.515
0.534 INTERSECTION LEFT ROUTE 0402 (TOUR ROAD CUTOFF)0.534
0.542 SIGN LEFT GUIDE, SERVICE ROAD PLEASE WALK BICYCLES0.542
1.278 PULLOUT RIGHT1.258
1.920 SIGN LEFT GUIDE, ENTERING AMERICAN FORTIFIED LINES1.920
2.015 SIGN RIGHT GUIDE, NEILSON FARM STOP 22.015
2.037 INTERSECTION LEFT ROUTE 0905 (STOP 2 PARKING)2.037
2.074 CURB LEFT2.043
2.080 INTERSECTION LEFT ROUTE 0905 (STOP 2 PARKING)2.080
2.081 SIGN RIGHT REGULATORY, ONE WAY2.081
2.099 CURB LEFT2.085
2.126 CURB RIGHT2.090
9-8Data Collected 11/4/2008
FROM
MILEPOST
TO
MILEPOST FEATURE SIDE COMMENT
ROUTE 0500: TOUR ROAD
SARA: ROUTE MAINTENANCE FEATURES ROAD LOG
Culverts and drop inlets were marked by NPS and
inventoried by RIP in Cycle 4, therefore the culvert and drop inlet
count below includes those on ARAN-driven routes, Manually
Rated Routes and in Paved Parking Areas.
Notice:
2.122 PULLOUT RIGHT2.098
2.177 INTERSECTION RIGHT UNPAVED ROUTE2.177
2.382 PULLOUT RIGHT2.360
2.383 CURB RIGHT2.360
2.598 SIGN RIGHT REGULATORY, STOP2.598
2.600 SIGN LEFT REGULATORY, STOP2.600
2.602 INTERSECTION RIGHT ROUTE 0200 (TOUR ROAD TO STOP 3)2.602
2.603 SIGN RIGHT GUIDE, AMERICAN RIVER FORTIFICATIONS STOP 32.603
2.669 CURB LEFT2.647
2.667 PULLOUT LEFT2.650
2.789 SIGN RIGHT GUIDE, LEAVING AMERICAN FORTIFIED LINES2.789
3.254 SIGN RIGHT GUIDE, CHATFIELD FARM STOP 43.254
3.297 INTERSECTION RIGHT ROUTE 0908 (STOP 4 PARKING)3.297
3.333 CURB RIGHT3.305
3.336 INTERSECTION RIGHT ROUTE 0908 (STOP 4 PARKING)3.336
3.338 SIGN LEFT REGULATORY, ONE WAY3.338
3.636 CULVERT N/A 1910-004 (MILL CREEK CULVERT)3.636
3.672 PULLOUT RIGHT3.642
3.804 SIGN RIGHT GUIDE, BARBER WHEATFIELD STOP 53.804
3.847 INTERSECTION LEFT ROUTE 0909 (STOP 5 PARKING)3.847
3.890 CURB LEFT3.853
3.893 INTERSECTION LEFT ROUTE 0909 (STOP 5 PARKING)3.893
3.903 SIGN RIGHT REGULATORY, ONE WAY3.903
4.077 INTERSECTION LEFT ROUTE 0402 (TOUR ROAD CUTOFF)4.077
4.487 SIGN RIGHT GUIDE, UNABLE TO READ FROM VIDEO4.487
4.498 SIGN RIGHT GUIDE, ENTERING BRITISH FORTIFIED LINES4.498
4.542 SIGN RIGHT GUIDE, BALCARRES REDOUBT STOP 64.542
4.580 INTERSECTION RIGHT ROUTE 0910 (STOP 6 PARKING)4.580
4.640 INTERSECTION RIGHT ROUTE 0910 (STOP 6 PARKING)4.640
4.650 SIGN LEFT REGULATORY, ONE WAY4.650
9-9Data Collected 11/4/2008
FROM
MILEPOST
TO
MILEPOST FEATURE SIDE COMMENT
ROUTE 0500: TOUR ROAD
SARA: ROUTE MAINTENANCE FEATURES ROAD LOG
Culverts and drop inlets were marked by NPS and
inventoried by RIP in Cycle 4, therefore the culvert and drop inlet
count below includes those on ARAN-driven routes, Manually
Rated Routes and in Paved Parking Areas.
Notice:
4.705 SIGN LEFT GUIDE, GRAPHIC SIGN, NO TEXT4.705
4.719 SIGN RIGHT GUIDE, UNABLE TO READ FROM VIDEO4.719
4.844 SIGN RIGHT WARNING, 15 M.P.H.4.844
4.865 SIGN RIGHT GUIDE, BREYMANN REDOUBT STOP 7 ARNOLD MONUMENT4.865
4.885 INTERSECTION LEFT ROUTE 0911 (STOP 7 PARKING)4.885
4.942 INTERSECTION LEFT ROUTE 0911 (STOP 7 PARKING)4.942
4.942 SIGN RIGHT REGULATORY, ONE WAY4.942
6.048 SIGN RIGHT GUIDE, BURGOYNE'S HEADQUARTERS STOP 86.048
6.066 INTERSECTION RIGHT ROUTE 0912 (STOP 8 PARKING)6.066
6.123 INTERSECTION RIGHT ROUTE 0912 (STOP 8 PARKING)6.123
6.124 SIGN LEFT REGULATORY, ONE WAY6.124
6.166 SIGN RIGHT REGULATORY, SPEED LIMIT 156.166
6.328 PAVED DITCH LEFT6.265
6.268 SIGN RIGHT WARNING, GRAPHIC SIGN, NO TEXT6.268
6.268 SIGN RIGHT WARNING, SLOW6.268
6.370 PAVED DITCH LEFT6.365
6.458 GUARD/GUIDE RAIL LEFT6.403
6.459 GUARD/GUIDE RAIL RIGHT6.404
6.451 BRIDGE N/A 1910-001 (KROMA KILL BRIDGE #1)6.413
6.734 SIGN RIGHT WARNING, STOP AHEAD6.734
6.788 SIGN LEFT REGULATORY, STOP6.788
6.788 SIGN RIGHT REGULATORY, STOP6.788
6.792 INTERSECTION RIGHT ROUTE 0913 (STOP 9 PARKING)6.792
6.793 SIGN RIGHT GUIDE, GREAT REDOUBT STOP 96.793
6.849 SIGN RIGHT GUIDE, FRASER BURIAL SITE AND TRAIL STOP 106.849
6.875 INTERSECTION RIGHT ROUTE 0914 (STOP 10 PARKING)6.875
6.905 INTERSECTION RIGHT ROUTE 0914 (STOP 10 PARKING)6.905
6.908 SIGN LEFT REGULATORY, ONE WAY6.908
7.140 SIGN RIGHT WARNING, GRAPHIC SIGN, NO TEXT7.140
7.140 SIGN RIGHT WARNING, HILL7.140
9-10Data Collected 11/4/2008
FROM
MILEPOST
TO
MILEPOST FEATURE SIDE COMMENT
ROUTE 0500: TOUR ROAD
SARA: ROUTE MAINTENANCE FEATURES ROAD LOG
Culverts and drop inlets were marked by NPS and
inventoried by RIP in Cycle 4, therefore the culvert and drop inlet
count below includes those on ARAN-driven routes, Manually
Rated Routes and in Paved Parking Areas.
Notice:
7.148 SIGN RIGHT GUIDE, BICYCLES HILL7.148
7.244 SIGN RIGHT GUIDE, BICYCLES7.244
7.276 SIGN RIGHT WARNING, CAUTION GATE AHEAD7.276
7.296 SIGN RIGHT WARNING, STOP AHEAD7.296
7.340 GATE N/A7.340
7.349 SIGN RIGHT REGULATORY, STOP7.349
7.350 SIGN N/A GUIDE, THE GREAT RAVINE TO U.S. VISITOR CENTER TO N.Y.
32
7.350
7.350 INTERSECTION LEFT ROUTE 0010 (ENTRANCE ROAD)7.350
7.350 INTERSECTION RIGHT ROUTE 0010 (ENTRANCE ROAD)7.350
7.350 ROUTE END N/A TO ROUTE 0010 (ENTRANCE ROAD) AT MP 0.77 (ON RIGHT)7.350
9-11Data Collected 11/4/2008
Saratoga National Historical Park
Section 10
Appendix
APPENDIX A: GLOSSARY OF TERMS AND ABBREVIATIONS
TERM OR
ABBREVIATION DESCRIPTION OR DEFINITION
AADT (Annual Average Daily Traffic) The estimate of typical daily traffic on a road segment for all days of the week over the period of one year.
CRS Condition Rating Sheets. (Section 5)
Excellent Excellent rating with an index value of 95 or greater
Fair Fair rating with an index value from 61 to 84
Func. Class Funtional Classification (see Route ID, Section 4)
Good Good rating with an index value from 85 to 94
IRI International Roughness Index
Lane Width Width from road centerline to fogline, or from centerline to edge-of-pavement when no fogline exists
MRR Manually Rated Route
N/A Not Applicable
NC Not Collected
Paved Width Width from edge-of-pavement to edge-of-pavement
PCR Pavement Condition Rating (Appendix B, Section 10)
Poor Poor Rating with an index value of 60 or less
RCI Roughness Condition Index
SADT (Seasonal Annual Daily Traffic) The AADT adjusted to represent just the period of the year containing 80 percent of the total annual traffic.
SCR Surface Condition Rating (Appendix B, Section 10)
Shoulder Width Distance from fogline to hinge point, or if no fogline, from edge-of-pavement to hinge point.
10-1
APPENDIX B: DESCRIPTION OF RATING SYSTEM
A numerical roadway rating system is used to describe the overall condition of the paved roadways and pavedparking areas. In this system, a numerical rating between 0 and 100 is ascribed to each 0.02 miles of road. Thisnumerical rating is called a Pavement Condition Rating (PCR). A “perfect” road, newly constructed with no surfacedistresses and a smooth surface, would be assigned a PCR rating of 100. Based on the type, severity, and extent ofsurface distresses points are deducted from 100 to arrive at the final PCR.
Data is collected on the following distresses and conditions:
- Alligator Cracking - a series of interconnecting cracks resembling alligator skin orchicken wire, which can occur anywhere in the lane.
- Longitudinal Cracking - cracks which are parallel to the pavement centerline or asphaltlay-down direction.
- Transverse Cracking - cracks perpendicular to the pavement centerline.
- Pothole (patch) - a bowl-shaped hole in the pavement surface. May be patched or not.
- Rutting - surface depressions in the wheel paths.
- Roughness is collected as International Roughness Index (IRI) and is used in the PCRformula. Roughness is measured in inches of vertical displacement of the vehicle permile traveled.
A Distress Rating Index value is calculated for each of the individual distresses at the 0.02 mile, or every105.6 feet.
Calculation of Index Values
Note: Index values < 0 default to 0. Index values > 100 default to 100.For all indices, a higher value indicates a better road condition, and a lower value indicates a poorer roadcondition.All severity protocols are taken from the SHRP Distress Identification Manual.
Condition Ranges for all Indices
Excellent >=95 Good >=85 and <95 Fair >60 and <85 Poor <=60
Alligator Crack Index
AC_INDEX = 100 – 40 * [(%LOW / 70) + (%MED / 30) + (%HI / 10)]
Where :
The values %LOW, %MED and %HI describe the percent of the total WX measured area that is affectedby alligator cracking of each severity level. These values range from 0 to 100.
%LOW = (Total square area WX measured low severity alligator cracking) / (Section length * WXmeasured lane width)
10-2
%MED = (Total square area WX measured medium severity alligator cracking) / (Section length * WXmeasured lane width)%HI = (Total square area WX measured high severity alligator cracking) / (Section length * WX measuredlane width)
The denominators 70, 30, and 10 are the maximum allowable extents for the numerator value in the same units. Forexample, low severity alligator cracking totaling 70% of the measured section area would alone fail that section ofroad for this index.
The threshold for failure for this index is AC_INDEX = 60.
Severity Levels:
Low severity alligator cracking describes an area of cracks with no or only a few connecting cracks; cracksare not spalled (cracked, broken, chipped, frayed along the cracks); pumping (water seepage from beneaththe pavement through the cracks) is not evident. Any sealed alligator cracks are low severity alligatorcracks, as long as the sealant is still in good condition. If the sealant has reopened, and the crack is visibleand can be measured, the crack severity is assigned according to that measurement.
Medium severity alligator cracking describes an area of interconnected cracks forming a complete pattern;cracks may be slightly spalled; pumping is not evident.
High severity alligator cracking describes an area of moderately or severely spalled interconnected cracks forming a complete pattern; pieces may move when subjected to traffic; pumping may be evident.
Longitudinal Crack Index
LC_INDEX = 100 – 40 * [(%LOW / 350) + (%MED / 200) + (%HI / 75)]
Where:
The values %LOW, %MED and %HI describe the length of longitudinal cracking of each severity as apercent of the section length. These values are 0 and can exceed 100.
%LOW = (Total linear feet WX measured low severity longitudinal cracking) / (Section length in linearfeet)%MED = (Total linear feet WX measured medium severity longitudinal cracking) / (Section length inlinear feet)%HI = (Total linear feet WX measured high severity longitudinal cracking) / (Section length in linear feet)
The denominators 350, 200, and 75 are the maximum allowable extents for the numerator value in the sameunits. For example, medium severity longitudinal cracking with a total length that is 200% of the length ofthe section would alone fail that section of road for this index.
The threshold for failure for this index is LC_INDEX = 60.
Severity Levels:
Low severity longitudinal cracks have a mean width ¼”, or are sealed cracks of indeterminate width whose sealant material is in good condition.
Medium severity longitudinal cracks have a mean width > ¼” and ¾”.
High severity longitudinal cracks have a mean width > ¾”.
10-3
Transverse Crack Index
TC_INDEX = 100 – {[20 * ((LOW / 15.1) + (MED / 7.5))] + [40 * (HI / 1.9)]}
Where:
The values LOW, MED and HI describe a count of the total number of transverse cracks of each severitylevel, where one transverse crack unit is equal to the WX measured lane width. These values are 0.
LOW = (Total linear feet WX measured low severity transverse cracking) / (WX measured lane width)MED = (Total linear feet WX measured medium severity transverse cracking) / (WX measured lane width)HI = (Total linear feet WX measured high severity transverse cracking) / (WX measured lane width)
The denominators 15.1, 7.5, and 1.9 are the maximum allowable extents for the numerator value in thesame units. For example, high severity transverse cracking with a total length that amounts to 1.9 times theWX measured lane width would alone fail that section of road for this index.
The threshold for failure for this index is TC_INDEX = 60.
Severity Levels:
Low severity transverse cracks have a mean width ¼”, or are sealed cracks of indeterminatewidth whose sealant material is in good condition.
Medium severity transverse cracks have a mean width > ¼” and ¾”.
High severity transverse cracks have a mean width > ¾”.
Patching Index
PATCH_INDEX = 100 – 40 * (%PATCHING / 80)
Where:
The value %PATCHING describes the percent of the total WX measured area that is affected by patching.This value ranges from 0 to 100.
%PATCHING = (Total area WX measured patching) / (Section length * WX measured lane width)
The denominator 80 is the maximum allowable extent for the numerator value in the same units. Patchingtotaling 80% or more of the measured section area fails a section of road for this index.
The threshold for failure for this index is PATCH_INDEX = 60.
There are no severity levels for patching.
Rutting Index
RUT_INDEX = 100 – 40 * [(%LOW / 160) + (%MED / 80) + (%HI / 40)]
Where:
10-4
10 ARAN rut depth measurements are taken per full .02 section for each of 2 wheel paths (left and right),resulting in a total of 20 measurements taken for both wheel paths. The values %LOW, %MED and %HIdescribe the number of ARAN rut depth measurements of both wheel paths in the section whose values are of each severity level, calculated as a percentage of the total number of ARAN rut depth measurementstaken for a single wheel path in the section. These values range from 0 to 200.
%LOW = (Total number of ARAN measured low severity ruts in section for both wheel paths) / (Totalnumber of ARAN rut measurements in section for a single wheel path)%MED = (Total number of ARAN measured medium severity ruts in section for both wheel paths) / (Totalnumber of ARAN rut measurements in section for a single wheel path)%HI = (Total number of ARAN measured high severity ruts in section for both wheel paths) / (Totalnumber of ARAN rut measurements in section for a single wheel path)
The denominators 160, 80, and 40 are the maximum allowable extents for the numerator value in the sameunits. For example, low severity ruts recorded in 16 of the 20 total readings (or 160% of a full wheel path’sworth of readings) for a full .02 section would fail that section for this index.
The threshold for failure for this index is RUT_INDEX = 60.
Severity Levels:
Ruts with an ARAN measured depth < 0.20” are not included in the distress calculations.
Low severity ruts have an ARAN measured depth 0.20” and 0.49”.
Medium severity ruts have an ARAN measured depth 0.50” and 0.99”.
High severity ruts have an ARAN measured depth 1.00”.
Roughness Condition Index
RCI = 32 * [5 * (2.718282 ^ (-0.0041 * AVG IRI))]
Where:
The value AVG IRI describes the average value of the Left IRI and Right IRI measurements for the section.This value can range from approximately 40 to over 1000.
AVG IRI = (ARAN measured Left IRI + ARAN measured Right IRI) / 2
There is no applicable threshold for failure for this index.
NOTE: Collection of roughness data is dependent on the data collection vehicle traveling at a minimum speed of 12mph. In the event that a route cannot be safely traveled at this minimum speed, and results in no roughness data, theSCR only will be calculated.
Surface Condition Rating Index
SCR = 100 - [(100 - AC_INDEX) + (100 - LC_INDEX) + (100 - TC_INDEX) + (100 - PATCH_INDEX)+ (100 - RUT_INDEX)]
Where:
10-5
See above for determinations of AC_INDEX, LC_INDEX, TC_INDEX, PATCH_INDEX andRUT_INDEX.
The threshold for failure for this index is SCR = 60.
Pavement Condition Rating Index Asphaltic Concrete Pavement (AS)
PCR = (0.60 * SCR) + (0.40 * RCI)
Where:
See above for determinations of SCR and RCI.
The values 0.60 and 0.40 function as weights within the formula.
If SCR equals zero (which means that the road surface condition is very poor), then the formula simplyreduces to: PCR = 0.40 * RCI.
If RCI equals zero (which means that this value was not available for some reason), then the formulabecomes: PCR = SCR.
The threshold for failure for this index is PCR = 60.
Pavement Condition Rating Index Portland Cement Concrete Pavement (CO)
Concrete PCR = -0.0012(IRI^2)+0.0499(IRI)+99.542Where:
The threshold for failure for this index is PCR = 60.
Parking Lot and Manually Rated Road Condition Rating
Surface Condition Distresses- Chip Seal:
Raveling – loss of surface rock chips revealing previous surfaceBleeding – asphalt or tar is bleeding through to the surface where surface looks slick with asphaltRuttingPotholes/Patching
Ratings - Chip Seal:
Excellent – None of the surface affected by the above (recently constructed)Good – Less than 10% of surface affected by the aboveFair – Between 10% and 40% of surface affected by the abovePoor – More than 40% of surface affected by the above
Surface Condition - Asphalt:
Cracking of any typeRuttingPotholes/Patching
10-6
Ratings - Asphalt:
Excellent – None of the surface affected by the above (recently constructed)Good – Less than 10% of surface affected by the aboveFair – Between 10% and 40% of surface affected by the abovePoor – More than 40% of surface affected by the above
Index Values of Visual Ratings on Parking Lots and Manually Rated Roads
Under Construction 100
Excellent 97
Good 90
Fair 73
Poor 45
10-7
APPENDIX C: GENERAL INFORMATION ON RIP SYSTEMS
DMI (Distance Measuring Instrument) The DMI (Distance Measuring Instrument) obtains road length measurements that are highly accurate (to 0.001 miles). The DMI is connected to the outside of the rear wheel on the driver’s side, and is wired into the antilockbraking system (ABS). The number of pulses recorded for each wheel rotation by the ABS is registered by the DMI,which transmits a measurement of distance traveled to the processing computers in the ARAN. The DMI distancemeasurements are the foundation to which all the other subsystems are tied.
Digital Image InformationAll images collected in Cycle 4 are digital images in .jpg format. These images provide adequate resolution foridentifying sign and feature inventories and pavement evaluations. The images can be viewed with an interactivesoftware program called VisiData. Each park will receive a copy of the VisiData program. Cycle 4 data, as well as Cycle 3 data, can be viewed using the Visi-Data software program. This program is a data presentation and analysistool that can be accessed either at the individual park, park region or at NPS headquarters. The data is organized ina hierarchical manner and presented in tabular and graphical formats. The user is able to perform queries and drilldown through the data to find the particular information they are looking for. Associated digital right-of-way imagesfrom either the LAN, USB port, individual DVD can be presented along with GPS locations.
Right-of-way (ROW) Video Three digital cameras are mounted above the vehicle’s windshield that point directly forward and slightly to the leftand right. These cameras each collect one image every 0.002 miles (10.56 feet) in the primary-direction lane, to givea panoramic field-of-view of about 160 degrees. (Forward-facing video from the center camera only is collected inthe opposite-direction lane of travel.)If data collection speed exceeds 35-40 mph, the network and storage computers may become overwhelmed and maybegin to drop individual video frames. Occasional common video quality issues include sun glare and rapid changesbetween sunlight and shadow. The camera system is equipped with auto risers that sometimes cannot adjust quickly enough to collect optimal video images.
FHWA ARAN CAMERA SPECIFICATIONSForward-Facing Cameras (ROW)
Focal length 10 mm
Chip size 8.71mm X 6.90mm
Naming convention of each image chainage.jpg
Image resolution 1300 X 1030
Image pixel size depends on distance
Relative position of the GPS unit to eachcamera
2.104 meters from front-center rutbar tocamera
The ARAN has a lever arm setting which tells the POS system where the center of the
rutbar is with respect to the GPS antennas.
Pavement Video Pavement video images are collected by the data collection vehicle to use in later analysis to determine extents andseverities of different types of pavement distress. The pavement in the primary-direction road lane is filmedcontinuously by two analog cameras attached to booms extended from the rear of the ARAN on the left and rightsides. Strobe lights fire synchronously with the opening of the camera shutters to eliminate shadows and motionblur. The images from the two cameras overlap, and are stitched together in real time to create a continuous stripimage of the pavement in the primary direction lane. This strip has a maximum width of 3.0 meters (actual widthdepends on pavement camera calibration) and is sectioned for ease of file management every 0.010 miles (52.8 feet).
10-8
The cameras both have a resolution of 640 x 480, making the threshold of visible pavement cracks about 3 mm.Because the cameras are triggered by time and not distance traveled, this subsystem requires a minimum operating speed of 6 mph, otherwise images are taken on top of one another and result in checkered or black pavement video.
FHWA ARAN CAMERA SPECIFICATIONSPavement Cameras
Image Pixel size 3.135 mm /side
Image Resolution 640 X 480
Area that images cover 1.5 m X 1.2 m
Full color or grayscale grayscale
Vehicle speed limitations 80km/h
Aperture setting Auto-iris
Exposure setting 1/50000
FHWA ARAN GPS & Inertial SystemGPS is collected by a NovAtel MiLLenium, 12 channel, dual frequency L1/L2, DGPS ready receiver with a MiLLennium 502 GPS antenna. An OmniStar 3000 LR provides real-time differential correction. An ApplanixPOS/LV is the inertial system that fills in when GPS is unavailable. The antenna is mounted in the center of the roof, slightly toward the rear of the vehicle, but a lever arm is applied to place the operational location of GPS recordingat the center of the rutbar on the front bumper of the vehicle. Expected accuracy under ideal conditions is sub meter.
GPS Collected on Manually Rated Routes Parking areas and roads that are not fully drivable with the ARAN data collection vehicle are collected manually by field technicians. GPS is collected for these routes using GPS field data collection utilizes Trimble ProXRS orProXH Receivers matched with Trimble TSC1 or Ranger handheld Data Loggers, connected to Trimble Hurricane Antennas giving sub meter accuracy in ideal conditions. This collection equipment has varied as technology hasimproved over the years of RIP data collection. Some GPS files collected as early as 1998 have been verified for accuracy and perpetuated through the current cycle of data collection.
GPS SHAPEFILES
Type of Route and Collection
Shape Filename
Roads driven by ARAN Line park_road_04.dbf/.shp/.shx
Parking Areas Polygon park_pkg_04.dbf/.shp/.shx
Roads Manually Rated as Lines(not in every park)
Line park_mrl_04.dbf/.shp/.shx
Roads Manually Rated as Polygons(not in every park)
Polygon park_mrp_04.dbf/.shp/.shx
• Datum for all GPS shapefiles is LL_WGS84_DD (Latitude Longitude _World Geodetic Survey 1984_DecimalDegrees)• In filename, “park” is NPS four-letter alphabetic code.• The source for route data required for data processing and report production is the PARK_RouteInfo.mdb.
10-9
Condition Photos Taken of Manually Rated Roads One or more digital photos are taken by Canon Power Shot G2 4.0 Mega Pixel digital camera for each manuallyrated route in a National Park. They are stored in .jpg format named with the four-letter NPS park alphabetic code,route number, and the photo number assigned by the camera. For example, YOSE_0900_4434.jpg is the filename of the photo named 4434 by the camera that was taken of Yosemite National Park route 0900.
Scenic Photos Scenic photos are taken by Canon Power Shot G2 4.0 Mega Pixel digital camera throughout each park and arenamed with the four-letter NPS park alphabetic code and the count of the photo taken in that park. For example,GRCA003.jpg is the filename of the third scenic photo taken in Grand Canyon National Park. The number of scenic
photos provided will vary between parks.
10-10
APPENDIX D: METADATA
FHWA – NPS Road Inventory Program Cycle 4 Metadata
The purpose of these sheets is to provide users of the Road Inventory Program’s data with data accuracies and tolerances to help users define ways in which the RIP data can and cannot be used. For further information onspecifics of data collection equipment, data collection procedures, equipment calibrations, or quality control/qualityassurance procedures, please contact Jim Kennedy, Project Manager, Data Quality Assurance, at 720-963-3560 [email protected].
All Road Inventory Program data undergoes quality control and quality assurance testing. This document representsthe known data accuracies and tolerances for the data collection equipment, data collection procedures, and dataprocessing procedures currently in use. Many additional tests conducted on the park databases during the qualityassurance phase to ensure data integrity are not listed as a part of this document. Before it is delivered, a parkdatabase undergoes a large set of table design consistency, field data format consistency, data completeness,uniqueness of key fields, data reasonableness, acceptable data range, within-field data consistency, between-fielddata consistency, and between-table data consistency tests. Additional data sampling checks are conducted to ensureproper data upload from raw files into the park database and to quality check the pavement crack analysis. Furtherinformation is detailed in the FHWA – NPS RIP Quality Assurance Manual, available upon request.
This description of metadata includes only the known accuracies with which a data field matches its expected value.The tables that follow this page show each database field’s:
Field – field name
Format – data type and number of characters of field
Expected Value – meaning of value assigned to field
Source – when in process field value obtained
Validation – how field value obtained
Expected Accuracy – accuracy with which contents of field match Expected Value
Verifying and continually improving the accuracy of Road Inventory Program data is an ongoing goal of the FederalHighway Administration and the National Park Service. Field testing and post-collection analysis of ARAN(Automatic Road ANalyzer) -collected data will continue in Cycle 4. Data quality is expected to improve as theFHWA – NPS Road Inventory Program continues to operate, due to the fact that future data collection cycles will consist in large part of data updates. Also, technological improvements are expected to render the data increasinglyconsistent with actual roadway conditions as data collection cycles progress.
Specific Caveats
MUTCD based on contents & colors of sign, not on size
Database records that show a Portland Cement Concrete (CO) surface type sometimes include distressindex values that seem to show a perfect roadway. Condition assessments on concrete pavements are not conducted for Alligator Cracking, Transverse or Longitudinal Cracking, Patching, or Rutting. Perfect values for concrete road sections for these indexes are default values and do not represent a conditionassessment of the concrete surfaces.
On the USB drive, in the Database folder, parks are provided with intersection lists and exceptions lists.These documents should be treated as raw files and are not accurate. Refer to the final database for accurately post-processed intersection data.
Most roadway data is collected in the primary direction lane of a roadway. To save data storage space andto reduce data analysis efforts, the assumption was made that the paved surface condition of a route’sprimary lane adequately represents the surface condition of the full roadway. Therefore, in the database,opposite-direction records in the PMS_Tenth table do not include assessed values for roadway surface distresses. Values such as 0, N/A, -1, or a repeat of the primary-direction assessed value indicate that no assessment was performed. The PMS_20 and PMS_Mile tables simply exclude all opposite routes.
10-11
10-12
Roadway Data is collected in intervals of 0.010 miles (52.8feet) constituting a “station”.
Most roadway features are collected relative to the primary direction lane of a roadway, using the primary-direction video and mileage. Signs and Mile Markers are the only features collected using the opposite-direction video with mileage location referenced to the primary direction lane of the roadway.
Route_GPS table contains GPS positional information collected by the ARAN and post processed with Applanix POSPac Land 5.0 post-processing software. No manual adjustments have occurred on this table.
Modifications to the Park_ROAD_04.dbf/.shp/.shx files may have been necessary for report esthetics.
Modifications to the Park_PKG_04. dbf/.shp/.shx files may have been necessary for report esthetics.
Cycle 4 utilizes the Microsoft Office 2003 suite of products and Crystal Reports XI for document and data file generation and reporting.
All PDF files are in Adobe Acrobat 7.0 Professional format.
All ArcGIS files are created using ESRI Version 9.x software.
Thumbnail images are created at 1/10 original image size for Right-of-Way and Pavement Images.
FHWA is investigating the rutting methodology and calculated values it currently reports. Equipment limitations and analysis methods may be over reporting, low severity rutting.
Key to Notes in Tables
(1): Note that only one value fits in field, so even if this value varies throughout the route, only predominant value is recorded here. (2): Shoulder width is measured at route start and every half-mile along the route in the primary direction. Width is the entire width of the drivable shoulder, regardless of the presence or absence of pavement, from the fog line to the shoulder hinge point, or if no fog line exists, from the edge of pavement to the hinge point. Identification of shoulder hinge point can be problematic using video analysis. Some paved ditches may be mistakenly recorded as shoulders where the shoulder hinge point and change in slope are not easily distinguished from the video. (3): Mileage is measured by the ARAN (Automatic Road ANalyzer) data collection vehicle out to the 0.001 decimal place. The DMI (distance measuring instrument) is very accurate, with extremely slight variations in measurement due to air temperature, tire inflation, curves, hills, and equipment calibration. (4): Features are measured differently depending on whether they are visible in the forward-facing video of the roadway, but every feature milepost measurement depends on the baseline measurement of the data collection vehicle’s mileage. The ARAN (Automatic Road ANalyzer) data collection vehicle’s mileage is measured by the DMI (distance measuring instrument) out to the 0.001 decimal place. The DMI is very accurate, with extremely slight variations in measurement due to air temperature, tire inflation, curves, hills, and equipment calibration. If a feature will not be visible in the forward-facing video, its milepost is determined by the data collectors’ key press tagging the milepost when the ARAN passes the feature. Key presses are entered into the ARAN software when the vehicle travels typically between 15 and 45 miles/hour, so a delay of a single second as the vehicle passes a feature would result in an inaccuracy of 0.004 miles (22 feet) to 0.012 miles (66 feet). If a feature is visible in the video, its milepost is determined during post-processing using a video measurement software called Surveyor. (5): Condition assessments on concrete (PCC) pavements are not conducted for Alligator Cracking, Transverse or Longitudinal Cracking, Patching, or Rutting. Perfect values for concrete road sections for these indexes are default values and do not represent a condition assessment of the concrete surfaces. (6): Roadway cracking presence, type, severity, and extent are determined by filming the roadway in the primary lane continuously with two overlapping analog cameras of 640 x 480 resolutions. The images from both cameras are stitched together in real time to create a continuous strip image of the roadway pavement in the primary lane. Cracks 3 mm or greater in width are visible in this video. A semi-automatic process running the WiseCrax software with additional input by human operators provides the cracking quantities recorded in these database fields. Quality checks have determined that a consistent 80% or better of the visible cracks are recorded.
Access Database Metadata
MASTER Table Metadata:
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION
EXPECTED
ACCURACY
1 RIP_CYCLE XX 4, for data collection cycle 4 Route ID Meeting FHWA Determination100% Referenced toother tables
2 STATE XX State where route is located Route ID Meeting Park Input / FHWA Determination100%, Referenced toother tables (1)
3 PARK_ALPHA XXXX Park alpha code Route ID Meeting NPS References100%, Referenced toother tables
4 PARK_NO XXXX Park numeric code Route ID Meeting NPS References100%, Referenced toother tables
5 RTE_NO 9999XXX Route number Route ID Meeting Park Input / FHWA Classification100%, Referenced toother tables
6 RTE_NAME (Text) Route name Route ID Meeting Park Input
100%, Referenced toother tables. 100characters fit in field
7 FUNCT_CLASS X Route functional classification Route ID Meeting Park Input / FHWA Classification100%, Referenced toother tables
8 DIRECTION XXXSurvey lane: PRI (primary) orOPP (opposite) Route ID Meeting Park Input / FHWA Determination 100%,
9 BEG_MP_EST 999.999 (miles) Estimated starting MP Route ID Meeting Park Input / FHWA DeterminationEstimated before datacollected
10 END_MP_EST 999.999 (miles) Estimated ending MP Route ID Meeting Park Input / FHWA DeterminationEstimated before datacollected
11 RTE_LENGTH 999.999 (miles) Collected route length ARAN Data Collection Automatic Output 100%
12 FROM_DESC (Text) Beginning terminus of route Route ID Meeting Park Input / FHWA Determination100% Referenced toother tables
13 TO_DESC (Text) Ending terminus of route Route ID Meeting Park Input / FHWA Determination100% Referenced toother tables
14 NO_LANES X Number of lanes in route ARAN Data Collection Survey Crew Input Untested. (1)
15 SURF_TYPE XX Surface type of route ARAN Data Collection Survey Crew Input 100%, Referenced toother tables (1)
16 COMP_DIR XX
Compass direction of route’sprimary lane (nearest cardinaldirection) Route ID Meeting Park Input / FHWA Determination Untested
17 COMMENTS (Text) Special information, if any Contractor Post-processing Contractor Input Untested
18 FILENAME (Text) Filename of raw data files ARAN Data Collection Automatic Output 100%
19 SECTION (Text) Route section ID Route ID Meeting/ARANData Collection
Survey Crew Input/AutomaticOutput 100%
10-13
20 FKEY 9999999 Unique record ID Contractor Post-processing Database Processing 100%
21 DATE MM/DD/YY Data collection date ARAN Data Collection Automatic Output 100%
22 BEG_MP 999.999 (miles) Beginning MP collected ARAN Data Collection Automatic Output 100% (3)
23 END_MP 999.999 (miles) Ending MP collected ARAN Data Collection Automatic Output 100% (3)
10-14
PMS_FEATURE Table Metadata:
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION
EXPECTED
ACCURACY
1 RIP_CYCLE XX 4, for data collection cycle 4 Route ID Meeting FHWA Determination100% Referenced toother tables
2 STATE XX State where route is located Route ID Meeting Park Input / FHWADetermination Untested (1)
3 PARK_ALPHA XXXX Park alpha code Route ID Meeting NPS References100% Referenced toother tables
4 PARK_NO XXXX Park numeric code Route ID Meeting NPS References100% Referenced toother tables
5 RTE_NO 9999XXX Route number Route ID MeetingPark Input / FHWAClassification
100% Referenced toother tables
6 FMSS_EQUIP XXXXXXX
Facility ManagementSoftware System Equipmentnumber NPS FMSS application NPS References Untested
7 FUNCT_CLASS X Route functional class Route ID MeetingPark Input / FHWAClassification
100% Referenced toother tables
8 DIRECTION XXXSurvey lane: PRI (primary)or OPP (opposite) Route ID Meeting
Park Input / FHWADetermination 100%
9 MP 999.999 (miles) Feature location along route
ARAN Data Collection/Contractor Post-processing Video Analysis <=0.001 mile
10 BEG_MP 999.999 (miles)Feature Beginning locationalong route Contractor Post-processing Video Analysis <=0.001 mile
11 END_MP 999.999 (miles)Feature Ending locationalong route Contractor Post-processing Video Analysis <=0.001 mile
12 FEATURE_LENGTH 999.99 (Feet) Linear Feature Length Contractor Post-processing Database Processing 100%
13 EVENT XXXX Event category of feature Contractor Post-processing Video Analysis Untested
14 EVENT_CODE XXXXEvent sub-category offeature Contractor Post-processing Video Analysis Untested
15 FEATURE_TYPE (Text)Feature designation:LINEAR or POINT Contractor Post-processing Video Analysis Untested
16 EVENT_DESC (Text)Description offeature/contents of sign Contractor Post-processing Video Analysis Untested
17 MUTCD (Text) MUTCD Code of Sign Contractor Post-processing Database Processing 95%
18 CONDITION “N/A”Sign condition. N/A. Not tobe populated Contractor Post-processing Video Analysis
Values inaccurate,defaulted to “N/A”
19 COMMENT (Text)Sign label, intersectingroute, etc. Contractor Post-processing Database Processing Untested
20 OFFSET “N/A”Offset from Road Edge.N/A. Not to be populated Contractor Post-processing Database Processing
Values inaccurate,defaulted to “N/A”
10-15
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION
EXPECTED
ACCURACY
21 SIDE (Text)Side of route relative to lanedriven Contractor Post-processing Video Analysis 95%
22 STR_NUMBER (Text)FHWA bridge structurenumber FHWA Post-processing Database Processing Untested
23 BARR_MAT (Text) Barrier Material Type Contractor Post-processing Video Analysis Untested
24 BARR_TYPE (Text) Barrier Type Contractor Post-processing Video Analysis Untested
25 BARR_POST_MAT (Text) Barrier Post Materials Contractor Post-processing Video Analysis Untested
26 BARR_BEG_TERM (Text) Barrier Approach Treatment Contractor Post-processing Video Analysis Untested
27 BARR_END_TERM (Text) Barrier End Treatment Contractor Post-processing Video Analysis Untested
28 CURB_MAT (Text) Curb Material Type Contractor Post-processing Video Analysis Untested
29 PAVED_DITCH_MAT (Text) Paved Ditch Material Type Contractor Post-processing Video Analysis Untested (2)
30 GATE_MAT (Text) Gate Material Type Contractor Post-processing Video Analysis Untested
31 GATE_STYLE (Text) Gate Style Contractor Post-processing Video Analysis Untested
32 BEG_GPS_LAT 999.999999GPS Latitude Co-ordinate(decimal degrees) Contractor Post-processing Video Analysis <= 3.00 feet
33 BEG_GPS_LON -999.999999GPS Longitude Co-ordinate(-decimal degrees) Contractor Post-processing Video Analysis <= 3.00 feet
34 BEG_GPS_ELEV 99999.9 GPS Elevation Feet Contractor Post-processing Video Analysis Untested
35 BEG_GPS_MODE (Text) GPS Satellite Mode Contractor Post-processing Video Analysis Untested
36 END_GPS_LAT 999.999999GPS Latitude Co-ordinate(decimal degrees) Contractor Post-processing Video Analysis <= 3.00 feet
37 END_GPS_LON -999.999999GPS Longitude Co-ordinate(-decimal degrees) Contractor Post-processing Video Analysis <= 3.00 feet
38 END_GPS_ELEV 99999.9 GPS Elevation Feet Contractor Post-processing Video Analysis Untested
39 END_GPS_MODE (Text) GPS Satellite Mode Contractor Post-processing Video Analysis Untested
40 DATUM (Text) LL_WGS84_DD Contractor Post-processing Database Processing 100%
41 VIDEO <Park>C04VID<#>Removable USB video harddrive number Contractor Post-processing Database Processing Untested
42 IMAGE (Text)Filename of .jpg imageshowing feature Contractor Post-processing Automatic Output Untested
43 DATE MM/DD/YY Data collection date ARAN Data Collection Automatic Output 100%
44 FILENAME (Text) Filename of raw data files ARAN Data Collection Automatic Output 100%
45 SECTION (Text) Route section ID Route ID Meeting/ARANData Collection
Survey CrewInput/Automatic Output 100%
46 FKEY (Numeric) Unique record ID Contractor Post-processing Database Processing 100%
47 VISI_FROM 999999 (millimiles)Raw MP of first video frameshowing feature Contractor Post-processing Database Processing Untested
48 VISI_TO 999999 (millimiles)Raw MP of last video frameshowing feature Contractor Post-processing Database Processing Untested
10-16
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION
EXPECTED
ACCURACY
49 IDKEY (Text)Unique record ID used byVisiData Contractor Post-processing Database Processing Untested
50 MP_REF (Text)Range of mileage to play inVisiData Contractor Post-processing Database Processing Untested
List of Roadway Features
# EVENT EVENT_CODE FEATURE_TYPE EVENT_DESC STRUCTURE # COLLECTED BY
1 BRIDGE BRDG LINEAR BRIDGE ALWAYS ARAN
2 CATTLE GUARD CGD POINT CATTLE GUARD - VIDEO RATING
3 CONSTRUCTION CNST LINEARCONSTRUCTION WORK
ZONE - ARAN
4 CULVERT CUL POINT CULVERT SOMETIMES ARAN
5 CURB CRBL LINEAR CURB ON LEFT - VIDEO RATING
"" CRBR LINEAR CURB ON RIGHT - VIDEO RATING
6CURB-AND-
GUTTER CAGL LINEARCURB-AND-GUTTER ON
LEFT - VIDEO RATING
"" CAGR LINEARCURB-AND-GUTTER ON
RIGHT - VIDEO RATING
7 DROP INLET DINL POINT DROP INLET ON LEFT - ARAN
"" DINR POINT DROP INLET ON RIGHT - ARAN
8 GATE GATE POINT GATE - VIDEO RATING
9 FIRE HYDRANT FHDL POINTFIRE HYDRANT ON
LEFT - VIDEO RATING
"" FHDR POINTFIRE HYDRANT ON
RIGHT - VIDEO RATING
10GUARD/GUIDE
WALL GGWL LINEARGUARD/GUIDE WALL
ON LEFT - VIDEO RATING
"" GGWR LINEARGUARD/GUIDE WALL
ON RIGHT - VIDEO RATING
11GUARD/GUIDE
RAIL GGRL LINEARGUARD/GUIDE RAIL ON
LEFT - VIDEO RATING
"" GGRR LINEARGUARD/GUIDE RAIL ON
RIGHT - VIDEO RATING
12 INTERSECTION INTL POINT INTERSECTION ON LEFT - ARAN
"" INTR POINTINTERSECTION ON
RIGHT - ARAN
"" INTN POINT INTERSECTION SIDE N/A - ARAN
10-17
13LANE
DEVIATION LADV LINEAR LANE DEVIATION - ARAN
14LOW WATER
CROSSING LWCR LINEAR LOW WATER CROSSING SOMETIMES VIDEO RATING
15 MILE MARKER MML POINT MILE MARKER ON LEFT - VIDEO RATING
"" MMR POINTMILE MARKER ON
RIGHT - VIDEO RATING
16 OVERPASS OPV POINT OVERPASS VEHICULAR SOMETIMES ARAN
"" OPP POINT OVERPASS PEDESTRIAN SOMETIMES ARAN
"" OPRX POINTOVERPASS RAILROAD
CROSSING SOMETIMES ARAN
17PARK
BOUNDARY PRK POINT PARK BOUNDARY - ARAN
18 PAVED DITCH PVDL LINEAR PAVED DITCH ON LEFT - VIDEO RATING
"" PVDR LINEARPAVED DITCH ON
RIGHT - VIDEO RATING
19 PULLOUT PLOL LINEAR PULLOUT ON LEFT - VIDEO RATING
"" PLOR LINEAR PULLOUT ON RIGHT - VIDEO RATING
20RAILROADCROSSING RRX POINT RAILROAD CROSSING - VIDEO RATING
21RETAINING
WALL RTWL LINEARRETAINING WALL ON
LEFT - VIDEO RATING
"" RTWR LINEARRETAINING WALL ON
RIGHT - VIDEO RATING
22 ROUTE BEGIN RBEG POINT ROUTE BEGIN - ARAN
23 ROUTE END REND POINT ROUTE END - ARAN
24 SIGNREGU, WARN, GUID, UNKN POINT
DOCUMENT CONTENTSOF SIGN. (WHAT THE
SIGN SAYS) FORGRAPHICS ONLY SIGNS
POPULATED WITH("GRAPHIC SIGN, NO
TEXT") FORUNREADABLE TEXTPOPULATED WITH
("UNABLE TO READFROM VIDEO") - VIDEO RATING
25STATE
BOUNDARY STB POINT STATE BOUNDARY - ARAN
26 TRAFFIC LIGHT TRF POINT TRAFFIC LIGHT - VIDEO RATING
27 TUNNEL TUN LINEAR TUNNEL ALWAYS ARAN
10-18
PMS_20, PMS_MILE, & PMS_TENTH Tables Metadata:
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION EXPECTED ACCURACY
1 RIP_CYCLE XX4, for RIP data collectionCycle 4 Route ID Meeting FHWA Determination
100% Referenced to othertables
2 STATE XX State where route is located Route ID Meeting Park Input/FHWADetermination Untested. (1)
3 PARK_ALPHA XXXX Park alpha code Route ID Meeting NPS References100% Referenced to othertables
4 PARK_NO XXXX Park numeric code Route ID Meeting NPS References100% Referenced to othertables
5 RTE_NO 9999XXX Route number Route ID MeetingPark Input/FHWAClassification
100% Referenced to othertables
6 FUNCT_CLASS X Route functional class Route ID MeetingPark Input/FHWAClassification
100% Referenced to othertables
7 DIRECTION XXXSurvey lane: PRI (primary)or OPP (opposite) Route ID Meeting
Park Input/FHWADetermination 100%
8 BEG_MP 999.999 (miles)
MP at start of road interval described by databaserecord Contractor Post-processing Database Processing 100% (3)
9 END_MP 999.999 (miles)
MP at end of road interval described by databaserecord Contractor Post-processing Database Processing 100% (3)
10 INT_LENGTH 999.9 (ft)Length of road interval as aggregated for data table Contractor Post-processing Database Processing 100%
11 RTE_LENGTH 999.999 (miles) Collected route length ARAN Data Collection Automatic Output 100% (3)
12 NO_LANES 99 Number of lanes in route ARAN Data Collection Survey Crew Input Untested. (1)
13 LANE_NO 99 Data collection lane Contractor Post-processing Database Processing Untested
14 D_LANE_WIDTH 99.999 (ft)WiseCrax (crack detectionsoftware) analysis width Contractor Post-processing Automatic Output Untested
15 LANE_WIDTH 99.9 (ft) Width of lane Contractor Post-processing Video Analysis 95%, <=1.0 foot
16 PAVE_WIDTH 99.9 (ft) Full pavement width Contractor Post-processing Video Analysis 95%, <=1.0 foot
17 SHLD_WIDTH_L 99.9 (ft) Left shoulder width Contractor Post-processing Video Analysis 95%, <=1.0 foot (2)
18 SHLD_WIDTH_R 99.9 (ft) Right shoulder width Contractor Post-processing Video Analysis 95%, <=1.0 foot (2)
19 SHLD_COND_L N/AN/A. Intended to be Left shoulder condition ARAN Data Collection Survey Crew Input
Values inaccurate, defaultedto “N/A”
20 SHLD_COND_R N/AN/A. Intended to be Rightshoulder condition ARAN Data Collection Survey Crew Input
Values inaccurate, defaultedto “N/A”
21 DRAIN_COND_L N/AN/A. Intended to be Left drainage condition ARAN Data Collection Survey Crew Input
Values inaccurate, defaultedto “N/A”
22 DRAIN_COND_R N/AN/A. Intended to be Rightdrainage condition ARAN Data Collection Survey Crew Input
Values inaccurate, defaultedto “N/A”
10-19
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION EXPECTED ACCURACY
23 SURF_TYPE XX Surface type of route ARAN Data Collection Survey Crew Input Untested. (1)
24 PCR 999 Pavement Condition Rating Contractor Post-processing Database Processing 100% for calculation (6)
25 RCI 999Roughness Condition Index;-1 if invalid IRI Contractor Post-processing Database Processing 100% for calculation
26 SCR 999 Surface Condition Rating Contractor Post-processing Database Processing 100% for calculation (5) (6)
27 IRI_AVG 999.9 (inches/mile) Average IRI Contractor Post-processing Database Processing Untested
28 IRI_SD 999.9 (inches/mile) IRI standard deviation Contractor Post-processing Database Processing Untested
29 IRI_L 999.9 (inches/mile) Left wheel path IRI ARAN Data Collection Automatic Output Untested
30 IRI_R 999.9 (inches/mile) Right wheel path IRI ARAN Data Collection Automatic Output Untested
31 IRI_FLAG 0 or -1 -1 if invalid IRI data Contractor Post-processing Database Processing Untested
32 RUT_INDEX 999 Rut index Contractor Post-processing Database Processing 100% for calculation (5)
33 RUT_AVG 99.99 (inches)Average rut depth of bothwheelpaths Contractor Post-processing Database Processing Untested (5)
34 RUT_MAX 99.99 (inches)Maximum rut depth of bothwheelpaths Contractor Post-processing Database Processing Untested (5)
35 RUT_SD 9.9 Rut depth standard deviation Contractor Post-processing Database Processing Untested (5)
36 RUT_LOW 999 (%)
Percent of low severity ruts(on a 0-200% scale) in bothwheelpaths Contractor Post-processing Database Processing Untested (5)
37 RUT_MED 999 (%)
Percent of medium severityruts (on a 0-200% scale) inboth wheelpaths Contractor Post-processing Database Processing Untested (5)
38 RUT_HI 999 (%)
Percent of high severity ruts(on a 0-200% scale) in bothwheelpaths Contractor Post-processing Database Processing Untested (5)
39 XFALL 999.9 (% slope)Cross fall at start of roadinterval ARAN Data Collection Automatic Output Untested
40 GRADE 999.9 (% slope)Grade at start of roadinterval ARAN Data Collection Automatic Output Untested
41 AC_INDEX 999 Alligator cracking index Contractor Post-processing Database Processing 100% for calculation (5) (6)
42 AC_LOW 999.9999 (%)
Percent of WiseCraxmeasured lane area with low-severity alligatorcracking Contractor Post-processing Pavement Video Analysis
As a Computed 95%Confidence Level (5) (6)
43 AC_MED 999.9999 (%)
Percent of WiseCraxmeasured lane area with medium-severity alligatorcracking Contractor Post-processing Pavement Video Analysis
As a Computed 95%Confidence Level (5) (6)
44 AC_HI 999.9999 (%)
Percent of WiseCraxmeasured lane area with high-severity alligator Contractor Post-processing Pavement Video Analysis
As a Computed 95%Confidence Level (5) (6)
10-20
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION EXPECTED ACCURACY
cracking
45 LC_INDEX 999 Longitudinal cracking index Contractor Post-processing Database Processing 100% for calculation (5) (6)
46 LC_LOW 999.99 (%)
Low-severity longitudinalcracking in lane as a percentage of road intervallength Contractor Post-processing Pavement Video Analysis
As a Computed 95%Confidence Level (5) (6)
47 LC_MED 999.99 (%)
Medium-severitylongitudinal cracking in laneas a percentage of roadinterval length Contractor Post-processing Pavement Video Analysis
As a Computed 95%Confidence Level (5) (6)
48 LC_HI 999.99 (%)
High-severity longitudinalcracking in lane as a percentage of road intervallength Contractor Post-processing Pavement Video Analysis
As a Computed 95%Confidence Level (5) (6)
49 TC_INDEX 999 Transverse cracking index Contractor Post-processing Database Processing 100% for calculation (5) (6)
50 TC_LOW 999.99 (cracks)
Count of low-severitytransverse cracks, where one crack unit equals the WiseCrax measured lanewidth Contractor Post-processing Pavement Video Analysis
As a Computed 95%Confidence Level (5) (6)
51 TC_MED 999.99 (cracks)
Count of medium-severitytransverse cracks, where one crack unit equals the WiseCrax measured lanewidth Contractor Post-processing Pavement Video Analysis
As a Computed 95%Confidence Level (5) (6)
52 TC_HI 999.99 (cracks)
Count of high-severitytransverse cracks, where one crack unit equals the WiseCrax measured lanewidth Contractor Post-processing Pavement Video Analysis
As a Computed 95%Confidence Level (5) (6)
53 PATCH_INDEX 999 Patching index Contractor Post-processing Database Processing 100% for calculation (5) (6)
54 PATCHING 999.9999 (%)
Percent of WiseCraxmeasured lane area affected by patching Contractor Post-processing Pavement Video Analysis
As a Computed 95%Confidence Level (5) (6)
55 GPS_LAT 999.999999 Latitude coordinate ARAN Data Collection Automatic Output <= 3.00 feet
56 GPS_LON -999.999999 Longitude coordinate ARAN Data Collection Automatic Output <= 3.00 feet
57 GPS_ELEV 99999.9 Elevation ARAN Data Collection Automatic Output Untested
58 GPS_MODE XXXGPS Satellite Modeduring collection ARAN Data Collection Automatic Output Untested
59 DATUM (Text) LL_WGS84_DD ARAN Data Collection Database Processing 100%
60 VIDEO <Park>C04VID<#> Removable USB video hard Contractor Post-processing Database Processing Untested
10-21
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION EXPECTED ACCURACY
drive number
61 IMAGE (Text)Filename of .jpg imageshowing road interval Contractor Post-processing Automatic Output Untested
62 SPEED 999 (miles/hour)Average ARAN speedduring data collection ARAN Data Collection Automatic Output Untested
63 BRIDGE_FLAG 0 or 1Flag indicating presence of bridge in interval ARAN Data Collection Survey Crew Input Untested
64 CONSTR_FLAG 0 or 1Flag indicating constructionin interval ARAN Data Collection Survey Crew Input Untested
65 LANEDEV_FLAG 0 or 1Flag indicating lanedeviation in interval ARAN Data Collection Survey Crew Input Untested
66 DATE MM/DD/YY Data collection date ARAN Data Collection Automatic Output 100%
67 NODISTRESS 0 OR 1Flag indicating absence ofpavement distress Contractor Post-processing Database Processing 100%
68 FILENAME (Text) Filename of raw data files ARAN Data Collection Automatic Output 100%
69 SECTION (Text) Route section ID Route ID Meeting/ARAN DataCollection
Survey Crew Input/AutomaticOutput 100%
70 FKEY (Numeric) Unique record ID Contractor Post-processing Database Processing 100%
71 CONTRACTOR1 (Numeric)Raw MP of first video framein section Contractor Post-processing Database Processing Untested
72 CONTRACTOR2 (Numeric)Raw MP of last video framein section Contractor Post-processing Database Processing Untested
73 CONTRACTOR3 (Text)Unique record ID used byVisiData Contractor Post-processing Database Processing Untested
74 CONTRACTOR4 (Text)Range of mileage to play inVisiData Contractor Post-processing Database Processing Untested
10-22
ROUTE_GPS table metadata:
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION EXPECTED ACCURACY
1 RIP_CYCLE XX 4, for RIP data collection Cycle 4 Route ID Meeting FHWA Determination100% referenced to othertables
2 STATE XX State where route is located Route ID Meeting Park Input/FHWADetermination Untested
3 PARK_ALPHA XXXX Park alpha code Route ID Meeting NPS References100% Referenced to othertables
4 PARK_NO XXXX Park numeric code Route ID Meeting NPS References100% Referenced to othertables
5 RTE_NO 9999XXX Route number Route ID MeetingPark Input/FHWAClassification
100% Referenced to othertables
6 FUNCT_CLASS X Route functional classification Route ID MeetingPark Input/FHWAClassification
100% Referenced to othertables
7 RTE_NAME (Text) Route name Route ID Meeting Park Input
100% Referenced to othertables . 100 characters fit in field
8 LANE_NUMBER 99 Data collection lane Contractor Post-processing Database Processing Untested
9 DIRECTION XXXSurvey lane: PRI (primary) orOPP (opposite) Route ID Meeting
Park Input/FHWADetermination Untested
10 MP 999.999 Mile Post (at 0.01 record)ARAN Data Collection,Contractor Post-processing
Survey Crew Input/GPS Processing Untested (3)
11 GPS_LAT 999.999999GPS Latitude Co-ordinate(decimal degrees)
ARAN Data Collection,Contractor Post-processing Automatic Output <= 3.00 feet
12 GPS_LON -999.999999GPS Longitude Co-ordinate(-decimal degrees)
ARAN Data Collection,Contractor Post-processing Automatic Output <= 3.00 feet
13 GPS_ELEV 99999.9 ElevationARAN Data Collection,Contractor Post-processing Automatic Output Untested
14 GPS_MODE XXXGPS Satellite Modeduring collection
ARAN Data Collection,Contractor Post-processing Automatic Output Untested
15 XFALL 999.9
Cross Fall: % Slope at GPS Location (Caution, Data notValidated)
ARAN Data Collection,Contractor Post-processing Automatic Output Untested
16 GRADE 999.9Grade: % Slope at GPS Location(Caution, Data not Validated)
ARAN Data Collection,Contractor Post-processing Automatic Output Untested
17 HEADING 999.9 Heading Relative to True North ARAN Data Collection Automatic Output Untested
18 DATUM (Text) LL_WGS84_DD ARAN Data Collection Database Processing Untested
19 FILENAME (Text) Filename of raw data files ARAN Data Collection Automatic Output Untested
20 FKEY 9999999 Unique record ID Contractor Post-processing Database Processing Untested
10-23
21 DATE MM/DD/YY ARAN Data Collection Date ARAN Data Collection Automatic Output Untested
22 COMMENT (Text) Source of Any Digitized Data ARAN Data Collection Database Processing Untested
23 CONTRACTOR1 (Numeric) Visi_from Contractor Post-processing Database Processing Untested
24 CONTRACTOR2 (Numeric) Visi_to Contractor Post-processing Database Processing Untested
25 CONTRACTOR3 (Text) Visi_dir (ipdated to chapter 1) Contractor Post-processing Database Processing Untested
26 CONTRACTOR4 (Text) Comments/exceptions Contractor Post-processing Database Processing Untested
10-24
FHWA "Route ID Program" Database
Database Name: ROUTEINFO.mdb
Table Name: ROUTE_ID
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION EXPECTED ACCURACY
1 ROUTE_IDENT XXXX-9999XXXThe Park's Alpha Code + "-" +RTE_NO (below). Route ID Meeting Automatic Output
100%, Reference source for alltables
2 RIP_CYCLE 99 4, for RIP data collection Cycle 4 Route ID Meeting FHWA Determination100%, Reference source for alltables
3 PARK_ALPHA XXXX Park Alpha Code Route ID Meeting NPS References100%, Reference source for alltables
4 GROUP_ALPHA XXXX Group Alpha Code Route ID Meeting NPS References100%, Reference source for alltables
5 PARK_NO 9999 Park Numeric Code Route ID Meeting NPS References100%, Reference source for alltables
6 PARK_NAME (text) NPS Name of Park Route ID Meeting NPS References100%, Reference source for alltables
7 RTE_NO 9999XXX Route Number Route ID Meeting Park Input100%, Reference source for alltables
8 RTE_NAME (Text) Route Name Route ID Meeting Park Input100%, Reference source for alltables
9 FROM_DESC (Text) Beginning terminus of route Route ID Meeting Park Input/FHWA Determination100%, Reference source for alltables
10 TO_DESC (Text) Ending terminus of route Route ID Meeting Park Input/FHWA Determination100%, Reference source for alltables
11 INSP_DATE MM/DD/YYYY Collection DateARAN Data Collection FHWA Determination
100%, Reference source for alltables
12 FUNCT_CLASS XX Functional Class Route ID Meeting Park Input/FHWA Determination100%, Reference source for alltables
13 STATE XX State where route is located Route ID Meeting Park Input/FHWA Determination Untested (1)
14 STATE2 XXAdditional State Park Routetraverses Route ID Meeting Park Input/FHWA Determination Untested (1)
15 FMSS_NO (Text)
NPS's Facility ManagementSoftware System (FMSS) Assetnumber Route ID Meeting Park Input
100%, Reference source for alltables
16 FMSS_SUR_EQP (Text)FMSS Surface EquipmentNumber Route ID Meeting Park Input Untested
17 M_DISTRICT (Text)Park Maintenance District Route resides in Route ID Meeting Park Input
100%, Reference source for alltables (1)
18 TOPOGRAPHY (Text) Predominate Terrain condition for Route ID Meeting FHWA Determination 100%, Reference source for all
10-25
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION EXPECTED ACCURACY
Route. (FLAT, ROLLING,MOUNTAINOUS, or URBAN)
tables (1)
19 POSTED_SPEED 99
Posted Speed Limit for Route(Value is Predominate Speed Limit along Route) Route ID Meeting Park Input/FHWA Determination Untested (1)
20 ARAN_ROUTE XXX Yes/No Route ID Meeting Park Input/FHWA Determination100%, Reference source for alltables
21 PARKING_AREA XXX Yes/No Route ID Meeting Park Input/FHWA Determination100%, Reference source for alltables
22 CONCESSION XXX Yes/No Route ID Meeting Park Input100%, Reference source for alltables
23 PAVED_MI 999.999Paved mileage (to the nearest0.001)
ARAN Data Collection Automatic Output
100%, Reference source for alltables
24 UNPAVED_MI 999.999Unpaved mileage (to the nearest0.001) Route ID Meeting Automatic Output
100%, Reference source for alltables
25 RTE_LENGTH 999.999 Official Route LengthContractor Post-processing Automatic Output
100%, Reference source for alltables
26 SURF_TYPE XX
Surface type (PAVED: AS(asphalt, includes composite), CO (concrete), BR (brick/pavers), CB (cobblestone), OT (other)) Route ID Meeting Survey Crew Input
100%, Reference source for alltables (1)
27 UNPAVED XXXX Unpaved Route (Yes/No/Both) Route ID Meeting Automatic Output100%, Reference source for alltables
28 UNPAVED_CAT XXX Unpaved Road Category Route ID Meeting Automatic Output Untested
29 CURB (Text)Parking Area with Curb aroundperimeter. Route ID Meeting Park Input/FHWA Determination Untested
30 CURB_GUTTER (Text)Parking Area with Curb andGutter around perimeter. Route ID Meeting Park Input/FHWA Determination Untested
31 ADJ_ROUTE 9999XXX Route number Route ID Meeting Automatic Output100%, Reference source for alltables
32 USER_ACCESS (Text) Access Designation for Parking Route ID Meeting Park Input/FHWA Determination100%, Reference source for alltables
33 PHOTO_NO (Text) Photo or Image Route ID Meeting Survey Crew Input 100%, Reference source for alltables
34 PLOT_SIZE (Text) Unpaved Parking Area Size Route ID Meeting Automatic Output100%, Reference source for alltables
35 SQ_FEET 999.999 Route Square FootageContractor Post-processing Automatic Output
100%, Reference source for alltables
36 M_RATING (Text) Manual Rating Route ID Meeting Automatic Output100%, Reference source for alltables
10-26
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION EXPECTED ACCURACY
37 SQ_YARDS 999.999 Route Square YardageContractor Post-processing Automatic Output
100%, Reference source for alltables
38 LANES XX Route travel lanes Route ID Meeting Automatic Output Untested (1)
39 PAVE_WIDTH 999.99Pavement Width (Weightedaverage) RIP Post-processing Automatic Output 100% Referenced to other tables
40 LANE_MILES 999.999 Route Equivalent Lane Miles RIP Post-processing Automatic Output100%, Reference source for alltables
41 AREA_MAP (Text) 1 or 2-digit numberContractor Post-processing FHWA/Contractor Input
100%, Reference source for alltables
42 REMARKS (Memo)General remarks on Park routeand data collection operations.
Contractor Post-processing FHWA/Contractor Input Untested
43 SUMMARY_REC XXXX-9999XXXROUTE_IDENT of summaryPark Asset Route ID Meeting Park Input/FHWA Determination
100%, Reference source for alltables
44 NPS_REGION (Text) Park Region Route ID Meeting Park Input/FHWA Determination100%, Reference source for alltables
45 DIVISION (Text) FHWA Division Route ID Meeting Park Input/FHWA Determination100%, Reference source for alltables
46 PCR 999.99Route Weighted Average PCRvalue RIP Post-processing Automatic Output 100% Referenced to other tables
47 SCR 999.99Route Weighted Average SCRvalue RIP Post-processing Automatic Output 100% Referenced to other tables
48 AADT 999 Average Adjusted Daily Traffic RIP Automatic Output Untested
49 SADT 999 Seasonal Adjusted Daily Traffic RIP Automatic Output Untested
50 ADT_DATE MM/DD/YYYY Traffic Date of Collection RIP Automatic Output Untested
51 BEG_LAT 999.999999
Route Begin GPS Latitude Co-ordinate(decimal degrees)
ARAN Data Collection Automatic Output
<= 3.00 feet, Referenced fromother tables
52 BEG_LON -999.999999
Route Begin GPS Longitude Co-ordinate(-decimal degrees)
ARAN Data Collection Automatic Output
<= 3.00 feet, Referenced fromother tables
53 BEG_ELEV 99999.9 Route Begin ElevationARAN Data Collection Automatic Output 100% Referenced to other tables
54 BEG_MODE XXXRoute Begin GPS Satellite Modeduring collection
ARAN Data Collection Automatic Output 100% Referenced to other tables
55 END_LAT 999.999999
Route End GPS Latitude Co-ordinate(decimal degrees)
ARAN Data Collection Automatic Output
<= 3.00 feet, Referenced fromother tables
10-27
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION EXPECTED ACCURACY
56 END_LON -999.999999
Route End GPS Longitude Co-ordinate(-decimal degrees)
ARAN Data Collection Automatic Output
<= 3.00 feet, Referenced fromother tables
57 END_ELEV 99999.9 Route End ElevationARAN Data Collection Automatic Output 100% Referenced to other tables
58 END_MODE XXXRoute End GPS Satellite Modeduring collection
ARAN Data Collection Automatic Output 100% Referenced to other tables
59 DATUM (Text) LL_WGS84_DDARAN Data Collection Automatic Output 100% Referenced to other tables
60 CHILD_ROUTE XXX Yes/No Route ID Meeting Automatic Output100% Reference source for alltables
61 CULVERT_CNT 999 Route Culvert Count RIP Post-processing Automatic Output 100% Referenced to other tables
62 DROP_INLET_CNT 999 Route Drop Inlet Count RIP Post-processing Automatic Output 100% Referenced to other tables
63 GATE_CNT 999 Route Gate Count RIP Post-processing Automatic Output 100% Referenced to other tables
64 TRAFLIGHT_CNT 999 Route Traffic Light Count RIP Post-processing Automatic Output 100% Referenced to other tables
65 SIGN_CNT 999 Route Sign Count RIP Post-processing Automatic Output 100% Referenced to other tables
66 LWCROSS_CNT 999 Route Low Water Crossing Count RIP Post-processing Automatic Output 100% Referenced to other tables
67 BRIDGE_CNT 999 Route Bridge Count RIP Post-processing Automatic Output 100% Referenced to other tables
68 TUNNEL_CNT 999 Route Tunnel Count RIP Post-processing Automatic Output 100% Referenced to other tables
69 PULLOUT_CNT 999 Route Pullout Count RIP Post-processing Automatic Output 100% Referenced to other tables
70 INTERSEC_CNT 999 Route Intersection Count RIP Post-processing Automatic Output 100% Referenced to other tables
71 ST_BNDRY_CNT 999 Route State Boundary Count RIP Post-processing Automatic Output 100% Referenced to other tables
72 PRK_BNDRY_CNT 999 Route Park Boundary Count RIP Post-processing Automatic Output 100% Referenced to other tables
73 RETWALL_CNT 999 Route Retaining Wall Count RIP Post-processing Automatic Output 100% Referenced to other tables
74 RR_CROSS_CNT 999 Route RR Crossing Count RIP Post-processing Automatic Output 100% Referenced to other tables
75 CATTLE_CNT 999 Route Cattle Guard Count RIP Post-processing Automatic Output 100% Referenced to other tables
76 OVHDSIGN_CNT 999 Route Overhead Sign Count RIP Post-processing Automatic Output 100% Referenced to other tables
77 MILEMARK_CNT 999 Route Mile Marker Count RIP Post-processing Automatic Output 100% Referenced to other tables
78 FHYD_CNT 999 Route Fire Hydrant Count RIP Post-processing Automatic Output 100% Referenced to other tables
79 OVERPASS_CNT 999 Route Overpass Count RIP Post-processing Automatic Output 100% Referenced to other tables
80 CABLE_TLNG 9999.999 (ft)Route Total Length CableBarriers RIP Post-processing Automatic Output 100% Referenced to other tables
10-28
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION EXPECTED ACCURACY
81 GDRAIL_TLNG 9999.999 (ft)Route Total Length Guard/GuideRail Barriers RIP Post-processing Automatic Output 100% Referenced to other tables
82 GDWALL_TLNG 9999.999 (ft)Route Total Length Guard/GuideWall Barriers RIP Post-processing Automatic Output 100% Referenced to other tables
83 TEMP_BARR_TLNG 9999.999 (ft)Route Total Length TemporaryBarriers RIP Post-processing Automatic Output 100% Referenced to other tables
84 BOLLARD_TLNG 9999.999 (ft)Route Total Length BollardBarriers RIP Post-processing Automatic Output 100% Referenced to other tables
85 BARRIER_TLNG 9999.999 (ft) Route Total Length All Barriers RIP Post-processing Automatic Output 100% Referenced to other tables
86 CURB_TLNG 9999.999 (ft)Route Total Length Curbing(excludes Parking Areas) RIP Post-processing Automatic Output 100% Referenced to other tables
87 LWCROSS_TLNG 9999.999 (ft)Route Total Length Low WaterCrossings RIP Post-processing Automatic Output 100% Referenced to other tables
88 PAVDITCH_TLNG 9999.999 (ft) Route Total Length Paved Ditch RIP Post-processing Automatic Output100% Referenced to other tables(2)
89 TURNOUT_TLNG 9999.999 (ft) Route Total Length Turnouts RIP Post-processing Automatic Output 100% Referenced to other tables
90 LANE_NUMBER 99 Number of Lane Tested RIP Post-processing Automatic Output 100% Referenced to other tables
91 LOCAL_FACTOR 9.9999 Park Location Factor NPS Partner Automatic Output100% Reference source for alltables
92 E_ZONE XXX Route Environmental Zone FHWA HPMA Automatic Output100% Reference source for alltables
93 PAVEMENT_DM $99,999,999.99 Pavement Deferred Maintenance FHWA HPMA Automatic Output100% Reference source for alltables
94 CRV $99,999,999.99 Current Replacement Value RIP Post-processing Automatic Output100% Reference source for alltables
10-29
Database Name: ROUTEINFO.mdb
Table Name: PARK_TOTALS
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION
EXPECTED
ACCURACY
1 RIP_CYCLE 99 4, for RIP data collection Cycle 4 Route ID Meeting FHWA Determination100% Referenced to othertables
2 PARK_ALPHA XXXX Park Alpha Code Route ID Meeting FHWA Determination100% Referenced to othertables
3 GROUP_ALPHA XXXX Group Alpha Code Route ID Meeting NPS References100% Referenced to othertables
4 PARK_NO 9999 Park Numeric Code Route ID Meeting NPS References100% Referenced to othertables
5 PARK_NAME XXXX NPS Name of Park Route ID Meeting NPS References100% Referenced to othertables
6 INSP_DATE MM/DD/YYYYDate that data was collected in the park(completion date).
Route ID Meeting andARAN Data Collection FHWA Determination
100% Referenced to othertables
7 NPS_REGION XXXX Park Region Route ID Meeting Park Input100% Referenced to othertables
8 DIVISION XXXX FHWA Division Route ID Meeting FHWA Determination100% Referenced to othertables
9 T_PAVED_MI 999.999 Total Park Paved Miles RIP Post-processing Automatic Output100% Referenced to othertables
10 T_UNPAVED_MI 999.999 Total Park Unpaved Miles RIP Post-processing Automatic Output100% Referenced to othertables
11 T_ROUTE_MILES 999.999 Total Park Route Miles RIP Post-processing Automatic Output100% Referenced to othertables
12 T_ARAN_DRIVEN 999.999 Total Park ARAN Driven Miles RIP Post-processing Automatic Output100% Referenced to othertables
13 T_ARAN_LMILES 999.999 Total Park ARAN Lane Miles RIP Post-processing Automatic Output100% Referenced to othertables
14 T_CONCESS_PAVED 999.999 Total Park Concession Paved Miles RIP Post-processing Automatic Output100% Referenced to othertables
15 T_CONCESS_UNPAVED 999.999 Total Park Concession Unpaved Miles RIP Post-processing Automatic Output100% Referenced to othertables
16 T_PRK_PAVEDSQFT 999.999 Total Park Parking Paved Square Feet RIP Post-processing Automatic Output100% Referenced to othertables
17 T_PRK_UNPAVEDSQFT 999.999Total Park Parking Unpaved SquareFeet RIP Post-processing Automatic Output
100% Referenced to othertables
18 T_CPRK_PAVEDSQFT 999.999Total Park Concession Parking PavedSquare Feet RIP Post-processing Automatic Output
100% Referenced to othertables
10-30
10-31
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION
EXPECTED
ACCURACY
19 T_CPRK_UNPAVEDSQFT 999.999Total Park Concession Parking Unpaved Square Feet RIP Post-processing Automatic Output
100% Referenced to other tables
20 T_PARKING_SQFT 999.999 Total Park Parking Square Feet RIP Post-processing Automatic Output 100% Referenced to other tables
21 T_PARKING_LMILES 999.999Total Park Parking Equivalent Lane Miles RIP Post-processing Automatic Output
100% Referenced to other tables
22 T_MRR_SQFT 999.999Total Park Manually Rated Road Square Feet RIP Post-processing Automatic Output
100% Referenced to other tables
23 T_CMRR_SQFT 999.999Total Park Concession Manually Rated Road Square Feet RIP Post-processing Automatic Output
100% Referenced to other tables
24 T_MRR_LMILES 999.999Total Park Manually Rated Road Equivalent Lane Miles RIP Post-processing Automatic Output
100% Referenced to other tables
25 T_LMILES 999.999 Total Park Lane Miles RIP Post-processing Automatic Output100% Referenced to other tables
26 T_CULVERT_CNT 999 Total Park Culvert Count RIP Post-processing Automatic Output100% Referenced to other tables
27 T_DROP_INLET_CNT 999 Total Park Drop Inlet Count RIP Post-processing Automatic Output100% Referenced to other tables
28 T_GATE_CNT 999 Total Park Gate Count RIP Post-processing Automatic Output100% Referenced to other tables
29 T_TRAFLIGHT_CNT 999 Total Park Traffic light Count RIP Post-processing Automatic Output100% Referenced to other tables
30 T_SIGN_CNT 999 Total Park Sign Count RIP Post-processing Automatic Output100% Referenced to other tables
31 T_LWCROSS_CNT 999 Total Park Low Water Count RIP Post-processing Automatic Output100% Referenced to other tables
32 T_BRIDGE_CNT 999 Total Park Bridge Count RIP Post-processing Automatic Output100% Referenced to other tables
33 T_TUNNEL_CNT 999 Total Park Tunnel Count RIP Post-processing Automatic Output100% Referenced to other tables
34 T_PULLOUT_CNT 999 Total Park Pullout Count RIP Post-processing Automatic Output100% Referenced to other tables
35 T_INTERSEC_CNT 999 Total Park Intersections Count RIP Post-processing Automatic Output100% Referenced to other tables
36 T_ST_BNDRY_CNT 999 Total Park State Boundaries Count RIP Post-processing Automatic Output100% Referenced to other tables
37 T_PRK_BNDRY_CNT 999 Total Park Boundaries Count RIP Post-processing Automatic Output100% Referenced to other tables
38 T_RETWALL_CNT 999 Total Park Retaining Wall Count RIP Post-processing Automatic Output100% Referenced to other tables
39 T_RR_CROSS_CNT 999 Total Park RR Crossing Count RIP Post-processing Automatic Output 100% Referenced to other
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION
EXPECTED
ACCURACY
tables
40 T_CATTLE_CNT 999 Total Park Cattle Guard Count RIP Post-processing Automatic Output100% Referenced to othertables
41 T_OVHDSIGN_CNT 999 Total Park Overhead Sign Count RIP Post-processing Automatic Output100% Referenced to othertables
42 T_MILEMARK_CNT 999 Total Park Mile Marker Count RIP Post-processing Automatic Output100% Referenced to othertables
43 T_FHYD_CNT 999 Total Park Fire Hydrant Count RIP Post-processing Automatic Output100% Referenced to othertables
44 T_OVERPASS_CNT 999 Total Park Overpass Count RIP Post-processing Automatic Output100% Referenced to othertables
45 T_CABLE_TLNG 9999.999 (ft) Total Length Park Cable Barriers RIP Post-processing Automatic Output100% Referenced to othertables
46 T_GDRAIL_TLNG 9999.999 (ft)Total Length Park Guard/Guide RailBarriers RIP Post-processing Automatic Output
100% Referenced to othertables
47 T_GDWALL_TLNG 9999.999 (ft)Total Length Park Guard/Guide WallBarriers RIP Post-processing Automatic Output
100% Referenced to othertables
48 T_TEMP_BARR_TLNG 9999.999 (ft) Total Length Park Temporary Barriers RIP Post-processing Automatic Output100% Referenced to othertables
49 T_BOLLARD_TLNG 9999.999 (ft) Total Length Park Bollard Barriers RIP Post-processing Automatic Output100% Referenced to othertables
50 T_BARRIER_TLNG 9999.999 (ft) Total Length All Park Barriers RIP Post-processing Automatic Output100% Referenced to othertables
51 T_CURB_TLNG 9999.999 (ft) Total Length Park Curbing RIP Post-processing Automatic Output100% Referenced to othertables
52 T_LWCROSS_TLNG 9999.999 (ft) Total Length Park Low Water Crossings RIP Post-processing Automatic Output100% Referenced to othertables
53 T_PAVDITCH_TLNG 9999.999 (ft) Total Length Park Paved Ditches RIP Post-processing Automatic Output100% Referenced to othertables (2)
54 T_TURNOUT_TLNG 9999.999 (ft) Total Length Park Turnouts RIP Post-processing Automatic Output100% Referenced to othertables
55 PARK_PCR 99.99 Overall Park PCR Rating RIP Post-processing Automatic Output100% Referenced to othertables
56 PARK_RCI 99.99 Overall Park RCI Rating RIP Post-processing Automatic Output100% Referenced to othertables
57 PARK_SCR 99.99 Overall Park SCR Rating RIP Post-processing Automatic Output100% Referenced to othertables
58 PARK_RUT_INDEX 99.99 Overall Park Rutting Index Rating RIP Post-processing Automatic Output100% Referenced to othertables
59 PARK_AC_INDEX 99.99Overall Park Alligator Cracking IndexRating RIP Post-processing Automatic Output
100% Referenced to othertables
10-32
FIELD FORMAT EXPECTED VALUE SOURCE VALIDATION
EXPECTED
ACCURACY
60 PARK_LC_INDEX 99.99Overall Park Longitudinal CrackingIndex Rating RIP Post-processing Automatic Output
100% Referenced to othertables
61 PARK_TC_INDEX 99.99Overall Park Transverse Cracking IndexRating RIP Post-processing Automatic Output
100% Referenced to othertables
62 PARK_PATCH_INDEX 99.99 Overall Park Patching Index Rating RIP Post-processing Automatic Output100% Referenced to othertables
63 PARK_CONC_PCR 99.99 Overall Park Concession PCR Rating RIP Post-processing Automatic Output100% Referenced to othertables
10-33
10 - 34
Business Practices for Route Numbering and Roadway Asset Identification
Introduction and Background:
Beginning in November 2006, inventory and condition information gathered by the Federal Highway Administration (FHWA) has been stored in FMSS to enable NPS to report Deferred Maintenance (DM) and Current Replacement Value (CRV) for NPS paved roads, paved parking areas, bridges, and tunnels. The NPS Roads Working Group (RWG) has been tasked with developing and implementing the procedures necessary to transfer DM and CRV from FHWA’s databases to NPS’ Facility Management Software System (FMSS).
Current business practices for roadway definition in national parks involve face-to-face meetings between FHWA personnel and individual park staff known as “Route ID” meetings. These meetings have been ongoing for several years and have been performed within the context of the Road Inventory Program (RIP) executed mainly by FHWA. The primary focus of these meetings has been on defining roadway static information such as route names, numbers, functional class, etc. The FHWA personnel are the primary individuals responsible for implementing the RIP and the route ID meetings are an integral and fundamental part of that process. The RIP process provides route numbers for each individual road and parking area in each park. After the route ID meetings establish a given park’s roadway asset base, various types of condition and inventory data are collected either manually or with a data collection van that drives each individual road with an individual route number.
The FMSS requires asset numbers as unique identifiers for all asset types including roadways. The current practice is that all roadways that are assigned a route
number at route ID, also are defined as assets and therefore also receive an FMSS
asset number (Route names and functional classes are also collaboratively assigned during the face-to-face route ID meetings). This practice began midway through the third RIP data collection cycle (ending in 2003) and was further reinforced during an asset alignment process conducted in the summer of 2006. The alignment process ensured that each route number in RIP and each asset number in FMSS were matched to the correct road and parking area.
Issue Statement:
As a result of various pre-existing business practices associated with the RIP, which predates FMSS by several years, route numbers are assigned for routes that are often very small. In tandem with the current business practice that all routes with route numbers are considered assets, this has caused a proliferation of asset numbers within FMSS. Over the past year, the RWG has learned that this business practice has significantly increased time and resources that parks must dedicate to administering FMSS data entry and management. This additional work effort is due to the fact that tying FMSS asset records to the more detailed, granular RIP route numbers has generated numerous new assets that require additional database and work order management. This has led to a situation where assets are not being defined the way they are managed.
10 - 35
The following proposed practices seek to create an asset definition process that is dictated by to how road assets are managed at the park level, not according to the pre-existing practices used in RIP for collecting detailed road information. RIP practices assign route numbers mainly based on how data are collected and driven with a data collection device.These procedures will disassociate the driving of roads with the data collection van from the process of assigning them asset status. The end goal is to only assign asset
numbers based on how parks manage their facilities within guidelines set up within
FMSS and herein. Driving the road with the data collection van allows for the collection of higher quality data as well as the ability to view road segments with video viewing software (Visidata). By de-linking driving the roads with the assignment of “asset status”, we are able to get the best quality data without the proliferation of assets that has serious negative ramifications for managing roadways in parks using asset management tools.
Proposed Actions:
1. Make a distinction within the route number field in the RIP database between those route numbers that represent assets, those that are subcomponents of assets and those that are groups of sub-components. The route number field in the RIP database will be expanded from 6 to 7 characters. The additional character will denote the asset status of the route in question. Combined routes will be designated with a double “zz”, while subcomponents will be designated with one “z”. Whenever possible, a combined route should use the lowest route number to be combined as the combined route number.
2. Only show assets, whether a group of subcomponents or a single component, on the Route ID report. Assets that are composed of subcomponents will have “zz” in the route number. Individual routes will have no additional characters in the route number. Subcomponents (designated in RIP with a “z”) will not be listed on the route ID report. Only assign asset numbers to those routes listed on the route ID report.
3. Provide a separate reporting function (other than the Route ID report) to identify and display information for route numbers not representing assets. Specific reporting requirements and format TBD.
4. Add a new field to the RIP database to indicate the “asset status” of a route number. The flag will have three possible values:
a. Asset with no subcomponents. b. Asset with subcomponents. c. Non-asset (i.e. subcomponent).
Both a change in the route number and a new “asset ID” field in the RIP database are recommended. It is easier to perform queries and other database manipulations using a separate field instead of a character within the route number field. The character in the route number field allows for rapid identification of the asset status of a road without having to access the database as a whole. Even thought non-asset routes will not be included in the route ID report (the primary location for parks to view road information in RIP), there are many other reports as well as the Visidata application where the route number is
10 - 36
displayed. In these cases, the character in the route number will clearly identify the asset status of the roadway.
5. Focus asset definition practices on NPS asset management needs. Create roadway assets based on how parks manage these assets within the following guidelines:
a. Individual road segments (asset subcomponents) may be combined into a single asset. Note that all the attributes of individual subcomponents
(paved area, equipment, work orders, etc) will be included in the
combined asset.
b. In general, combination should be used in complex circulatory environments such as campground areas, housing and other administrative areas, maintenance areas, etc.
c. Public and non-public segments may not be combined. d. Segments with differing functional classes may not be combined. e. Discrete parking areas may be combined into a single asset where they
service the same facility or resource and are within walking distance of each other.
f. Parking areas and roads may not be combined. This includes short road segments that may be near or adjacent to parking areas. See 5h below for exceptions to this.
g. Where the primary purpose of a road is to provide access to a parking area, and that road segment is approximately 0.25 miles in length or shorter, the access road should be considered part of the parking area (Note that this is an existing RIP business practice).
h. Particularly long routes may be divided into multiple assets based on how a park manages the roadway network. This should not be confused with the use of sub-components listed in 5a.
i. Roads that are actively managed by concession operations may not be combined with those managed by the NPS.
Discussion:
The first four items listed above are actions required by FHWA RIP to allow for the adoption of the practices shown in 5a-i. The following will provide additional direction and examples for guidelines listed.
Individual road segments (asset subcomponents) may be combined into a single asset.Where previous route ID practices have generated more assets (routes) than are practical from an asset management standpoint, small, discrete road lengths may be designated as asset subcomponents and then combined into a larger single asset. A subcomponent is NOT an FMSS term. Subcomponents will be used in RIP to indicate which routes are small, drivable individual road segments and which routes may include these segments. Once a piece of road is designated a subcomponent of another route, it will no longer have any individual identity in FMSS. Only those routes listed on the RIP Route ID report will have asset numbers in FMSS. As stated in business rule 2 above, subcomponents will not be listed on the route ID. The quantity information (length, area) will be included into the larger route of which they are a part. See Figures 1 and 2 for an example of how existing assets may be combined using subcomponents. Note that
10 - 37
subcomponents will have an identity in the RIP database and, if driven by RIP team, may be referenced in RIP reports, Visidata, or other RIP documentation.
Figure 1: Campground with five routes and five assets
Figure 2: Campground with all loops combined into one route and one asset. This has eliminated
four assets.
In general, combination should occur in complex circulatory environments such as campground areas, housing and other administrative areas, maintenance areas, etc.
00204zz
10 - 38
Typically these complex situations are where too many assets have been used to define roadways. Combining simple “point A to point B” roads that are clearly defined and provide access to different facilities or locations may not be done.
Public and non-public segments may not be combined. Roads that are posted as closed to the public or are intended as administrative access only (maintenance areas, housing areas, fire roads, etc) can not be combined with roads open to the public.
Segments with differing functional classes may not be combined. The roadway functional class is found on the Route ID report. Functional class indicates the type of circulatory function a given road provides. Functional class is used in a variety of applications (engineering, safety, funding) so it is important to maintain the correct functional class attributes of individual roads/assets. There are some cases where functional class was erroneously assigned in prior Route ID meetings such as where campground loops have a different functional class than the campground road. Functional classes of individual roads may be modified to correct discrepancies. The functional class definitions may not be modified.
Discrete parking areas may be combined into a single asset where they service the same facility or resource and are within walking distance of each other. These combined areas should be maintained as one asset. There are many instances where small (5-10 space), discrete parking areas have been separated into individual assets even though they provide parking for the same area or facility. These may be combined into a single asset. Figures 3 and 4 shows examples of combining parking areas.
10 - 39
Figure 3: Parking with access route 204 and multiple parking areas (1160 A-L). Currently, this
parking area is 12 routes and 12 assets ( one 1100 asset and 11 1300 assets).
Figure 4: Parking with access route 204 and one parking area 1160zz. Route 204 is assumed longer
than 0.25 miles. There are now 2 assets (one 1100 asset, one 1300 asset) instead of 12.
10 - 40
Parking areas and roads may not be combined. Parking areas and roads are tracked as separate asset types (1300 vs. 1100) in FMSS and as such should not be combined except in situations described by 5g. In Figure 5, Route 207 is a spur road from the main route running through parking area 1102. Since the spur road continues through and beyond the parking area, it will remain a separate route.
Figure 5: Parking with access route 207 running through and continuing beyond parking 1102. This
access route cannot be considered a part of the parking area and two routes and two assets continue
to exist.
Where the primary purpose of a road is to provide access to a parking area, and that road segment is less than 0.25 miles in length, the access road should be considered part of the parking area. See Figures 8. Where a road continues on past a parking area to another facility or destination, even if it is less than 0.25 miles to the initial parking area, the road and parking area may not be combined.
10 - 41
Figure 6: Since the access route is less than .25 miles in length and the only use of the access is to the
parking, one route for both the access and the parking area can be established.
Particularly long routes may be divided into multiple assets based on how a park manages the roadway network. This should not be confused with the use of sub-components listed in 5a. Routes like the Blue Ridge Parkway or the Yellowstone Grand Loop may not lend themselves to management as a single asset by virtue of their length. Often management districts are created for sections of these routes and maintenance activities occur primarily within these districts. Parks may break routes up into separate assets during the Route ID process if the road is managed as discrete sections. This should only be done for very long roads.
The following example illustrates a complex road system and how the proposed business practice and several of the guidelines could be applied to create fewer assets that are consistent with local management.
6B
6A
Rte 206 less than 0.25 miles
10 - 42
Figure 7 – Current Housing area access configuration. Route 409 is less than 0.25 miles long.
The area serviced by Routes 409, 421, 422, 968A, and 968B is all employee housing. Route 940 provides access to visitor services and not to the housing area. Routes may be combined to create assets that reflect local management. Routes 409, 421, and 422 are all the same functional class, provide access to one type of activity (housing) and are all posted as non-public. These routes may be combined. They should not be combined with any parking areas even though they are all less than 0.25 miles long. This is because their main function is not to provide access to parking. Routes 968A and B provide parking for access to the same facility (housing). Even though these discrete areas may provide parking to different housing units, it’s reasonable to manage them as a single asset. They may also be combined.
Figure 8 – Combined housing area access configuration – Parking and road assets combined to
eliminate 3 assets.