Appendix J_Database_Data_Dictionary.xlsx

XLSX spreadsheet 36 KB Posted

Attached to
Road Inventory Program Data Collection, Processing, and Viewing
Solicitation number
693C7322R000014
Issued by

View the file

Other files

File Type Posted
Amendment-0006-TPP_SAMPLE_FILES.zip ZIP file
Amendment-0006-693C7322R000014 .pdf PDF
Amendment-0005-693C7322R000014 .pdf PDF
Amendment 0004-Copy of HPMS Template.xlsx XLSX spreadsheet
Amendment 0004 - Copy of Appendix_L_Evaluation_Site_Submittal.xlsx XLSX spreadsheet
Amendment 0004 - Copy of Appendix_L_Evaluation_Site_Submittal.pdf PDF
Amendment-0004-693C7322R000014 .pdf PDF
Amendment 0004-Copy of HPMS Template.pdf PDF
Amendment-0003-693C7322R000014 .pdf PDF
Amendment-0003-GPD-NPS_ROADS_PARKING.zip ZIP file
Amendment-0002-693C7322R000014 .pdf PDF
TRANSCRIPT - Technical Field Evaluation - Overview Meeting - Road Inventory Services IDIQ_2022-04-07.pdf PDF
Amendment-0001-693C7322R000014 .pdf PDF
Appendix K_Past Performance Evaluation Questionnaire.pdf PDF
Appendix E_FHWA_Distress_Identification_Manual.pdf PDF
Appendix C_Scheduling Pre-Data Collection Information and Vehicle Certifications Verifications.pdf PDF
Appendix B_Data Collection Protocols and Database Population.pdf PDF
Appendix I_Sign Inventory Guide.pdf PDF
Appendix G_Viewing Software Specifications.pdf PDF
Appendix F_Quality Control Manual.pdf PDF
Appendix A _Location List (Excel Version).xlsx XLSX spreadsheet
Solicitation 693C7322R000014.pdf PDF
Appendix H_Roadside Features Inventory Guide.pdf PDF
Appendix D_Video Measurements.pdf PDF
Appendix_L_Evaluation_Site_Submittal.xlsx XLSX spreadsheet
Show all 25

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

CUMULATIVE_STATUS

CUMULATIVE_STATUS
COLUMN_NAMEDATA_TYPENULLABLEDATA_DEFAULTCOMMENTS
OBJECTIDNUMBER(38,0)NoInternal sequential number required by ESRI Geodatabase.
GLOBAL_IDVARCHAR2(38 CHAR)NoGlobal ID - Unique identifier with time stamp
AGENCYVARCHAR2(5 BYTE)NoLand Management Agency (NPS, BOR, FWS)
UNIT_IDVARCHAR2(10 BYTE)NoUnique code assigned within orginazation to differenciate collection units (NPS- PARK_ALPHA, FWS - ORG_CODE, BOR-AREA_OFFICE)
CYCLENUMBER(2,1)No6Current RIP cycle
INITIALSVARCHAR2(5 BYTE)NoInitials of person making adjustment to database
ENTRY_DATEDATENoDate of change
COMMENTSVARCHAR2(200 BYTE)NoThese notes indicate how the park database has progressed through the various stages of processing toward final completion status.
UNIT_NAMEVARCHAR2(100 BYTE)NoName of Unit

EXCEPTION_NOTES

EXCEPTION_NOTES
COLUMN_NAMEDATA_TYPENULLABLEDATA_DEFAULTCOMMENTS
OBJECTIDNUMBER(38,0)NoInternal sequential number required by ESRI Geodatabase.
GLOBAL_IDVARCHAR2(38 CHAR)NoGlobal ID - Unique identifier with time stamp
AGENCY

tc={6234A052-408E-4776-AEC5-50165B9F5BAD}: [Threaded comment]

Your version of Excel allows you to read this threaded comment; however, any edits to it will get removed if the file is opened in a newer version of Excel. Learn more: https://go.microsoft.com/fwlink/?linkid=870924

Comment:

How do we determine overlaps - FWS & BOR both have the same parking lots when the names are differentVARCHAR2(5 BYTE)NoLand Management Agency (NPS, BOR, FWS)
COLLECTION_TYPE
ROUTE_IDENTVARCHAR2(15 BYTE)NoUnique record identifier: PARK_ALPHA – RTE_NO
CYCLENUMBER(2,1)No6Current RIP cycle
UNIT_IDVARCHAR2(4 BYTE)NoUnique four letter code assigned to NPS unit.
ENTRY_DATEDATENoDate of change
INITIALSVARCHAR2(5 BYTE)NoInitials of person making adjustment to database
REMARKSCLOBYesRemarks for the data contractor
BEG_MPNUMBER(7,3)NoStarting Mile Point
END_MPNUMBER(7,3)YesEnding Mile Point
REASONVARCHAR2(25 BYTE)YesReason
FORCED_PCRNUMBER(1,0)YesForced PCR Flag: Identifies when a DCV route has a majority of its PCR assessed manually. Default: “0” (No majority or forced PCR). Flag: “1” (Forced PCR on majority of route).
PCRNUMBER(3,0)YesPavement Condition Rating

FEATURES

FEATURES
COLUMN_NAMEDATA_TYPENULLABLEDATA_DEFAULTCONSTRAINTUSE A LOOKUP TABLECOMMENTS
OBJECTIDNUMBER(38,0)NoNoInternal sequential number required by ESRI Geodatabase.
GLOBAL_IDVARCHAR2(38 CHAR)NoNoGlobal ID - Unique identifier with time stamp
AGENCYVARCHAR2(5 BYTE)NoFKYesLand Management Agency (NPS, BOR, FWS)
REGIONVARCHAR2(100 BYTE)YesYesInternal Agency Region
ROUTE_IDENTVARCHAR2(25 BYTE)NoFKNoUnique record identifier: PARK_ALPHA – RTE_NO
UNIT_IDVARCHAR2(10 BYTE)NoFKYesUnique code assigned within orginazation to differenciate collection units (NPS- PARK_ALPHA, FWS - ORG_CODE, BOR-AREA_OFFICE)
CYCLE_COLLECTEDNUMBER(2,1)RIP cycle feature was collected
INSP_DATEDATEData Collection Date
ASSET_TYPERoad or Parking lot
FEATURE_EVENTFKFeature Type - pulled from Lookup table
EVENT_DESCRIPTIONMP or speed limit
FEATURE_GEOMETRYLine or Point
EVENT_CODESign or agency code
STR_NUMBERStructure number - BIP,WIP # etc
BEG_MPStarting Mile Point
END_MPEnding Mile Point
BEG_LATGPS Latitude Coordinate at BEG_MP (decimal degrees)
BEG_LONGPS Longitude Coordinate at BEG_MP (decimal degrees)
END_LATGPS Latitude Coordinate at END_MP (decimal degrees)
END_LONGPS Longitude Coordinate at END_MP (decimal degrees)
SIDEEvent Location relative to lane driven. No blank entries allowed.
CURBVARCHAR2(35 BYTE)No'NOT APPLICABLE'Type of Curb present anywhere in Parking Lots - Curb is NOT collected for any roads. Please see the CURB_TYPES table for a listing of the possible Curb types.
CURB_GUTTERVARCHAR2(35 BYTE)No'NOT APPLICABLE'Type of Curb and Gutter present anywhere in Parking Lots - Curb is NOT collected for any roads. Please see the CURB_GUTTER_TYPES table for a listing of the possible Curb and Gutter types.
CURB_RECOMMENDATIONVARCHAR2(20 BYTE)No'NOT APPLICABLE'Manually Assigned Curb Rating. Please see the CURB_RECOMMENDATIONS table for a listing of the possible Curb ratings.
AVG_CURB_REVEALNUMBER(2,0)YesNULLAverage height of Curb visible (rounded to nearest inches). Used only on Parking Lots - Curb is NOT collected for any roads.
ADA_SPACESNUMBER(3,0)YesDescription Needed
LIGHTPOLESNUMBER(3,0)YesDescription Needed
PKG_SPACESNUMBER(4,0)YesNumber of parking spaces

PARKING Feature Class

PARKING Feature Class
COLUMN_NAMEDATA_TYPENULLABLEDATA_DEFAULTCOMMENTS
OBJECTIDNUMBER(38,0)NoInternal sequential number required by ESRI Geodatabase.
GLOBAL_IDVARCHAR2(38 CHAR)NoGlobal ID - Unique identifier with time stamp
SHAPEST_GEOMETRYYesESRI Generated field holding the types of geometry (ST_GEOMETRY)
AGENCYVARCHAR2(5 BYTE)NoLand Management Agency (NPS, BOR, FWS)
ROUTE_IDENTVARCHAR2(15 BYTE)NoUnique record identifier: PARK_ALPHA – RTE_NO
CYCLENUMBER(2,1)NoCurrent RIP cycle
UNIT_IDVARCHAR2(10 BYTE)NoUnique code assigned within orginazation to differenciate collection units (NPS- PARK_ALPHA, FWS - ORG_CODE, BOR-AREA_OFFICE)
ROUTE_NUMVARCHAR2(15 BYTE)NoFWS Route Number. Extracted from the NAT_RTE_ID.
SURF_TYPEVARCHAR2(2 BYTE)NoSurface type for the majority of the route. Please see the SURFACE_TYPES table for a listing of the possible PAVED and UNPAVED surface types.
LOT_AREANUMBER(11,2)YesBOR database field; Same as SQFT. Consider removal.
SQ_FEETNUMBER(7,0)No-1Area of route in square feet.
CENT_LATNUMBER(9,6)YesGPS Latitude Coordinate at route centroid (decimal degrees)
CENT_LONGNUMBER(9,6)YesGPS Longitude Coordinate at route centroid (decimal degrees)
SHAPE.AREADouble
SHAPE.LENDouble

ROAD_CONDITION

ROAD_CONDITION
COLUMN_NAMEDATA_TYPENULLABLEDATA_DEFAULTCOMMENTS
OBJECTIDNUMBER(38,0)NoInternal sequential number required by ESRI Geodatabase.
GLOBAL_IDVARCHAR2(38 CHAR)NoGlobal ID - Unique identifier with time stamp
AGENCYVARCHAR2(5 BYTE)NoLand Management Agency (NPS, BOR, FWS)
UNIT_IDVARCHAR2(10 BYTE)NoUnique code assigned within orginazation to differenciate collection units (NPS- PARK_ALPHA, FWS - ORG_CODE, BOR-AREA_OFFICE)
ROUTE_IDENTVARCHAR2(15 BYTE)NoUnique record identifier: PARK_ALPHA – RTE_NO
ROUTE_NUMVARCHAR2(15 BYTE)NoFHWA-RIP Route Number unique to linear referencing system
CYCLENUMBER(2,1)YesThe Cycle that the data was collected. Routes that were not collected should be coded as NC.
STATEVARCHAR2(2 BYTE)NoALL: State abbreviation in which the interval is located.

SURF_TYPE VARCHAR2(2 BYTE) No ALL: Surface type for interval of road being collected. Please see the SURFACE_TYPES table for a listing of the possible PAVED and UNPAVED surface types.

COLL_METHOD VARCHAR2(10 BYTE) No ALL: Method by which the data is collected.

INSP_DATE DATE Yes ALL: Data Collection Date.

INSPECTOR VARCHAR2(30 BYTE) Yes ALL: Name of the field collector

BEG_MP NUMBER(7,3) No ALL: Starting Mile Point

END_MP NUMBER(7,3) No ALL: Ending Mile Point

INT_LENGTH NUMBER(x,x) Yes ALL: Interval Length = Measured in feet (END_MP - BEG_MP) * 5280)

RTE_LENGTHNUMBER(7,3)YesLength of route in miles. Calculated from GIS or prior GPS readings
NUM_LANESNUMBER(1,0)No-1Number of travel lanes on route.
LANE_NONUMBER(1,0)YesThe number assigned to the lane in which the DCV collected data. Numbered 1,2,3, etc. from centerline or median from left to right.
LANE_WIDTHNUMBER(7,1)No-1ALL: Lane Width = From inside centerline to inside fogline. When there is no fogline present, from inside centerline to edge-of-pavement. When no striping at all, one-half PAVE_WIDTH (for 2-lane roads).

ROAD_WIDTH NUMBER(7,1) No -1 ALL: Paved Width = From edge-of-pavement to edge-of-pavement.

SHOULDER_WIDTH_RNUMBER(7,1)YesFog line to pavement edge
SHOULDER_WIDTH_LNUMBER(7,1)YesFog line to pavement edge
FUNCTIONAL_CLASSNVARCHAR2(10 CHAR)Yes
REMARKSCLOBYesALL: Any remarks needed regarding the collection or data of the tenth section.
URGENT_REMARKSNVARCHAR2(255 CHAR)YesUrgent remarks on record and data collection operations.
REMARKS_REPORTCLOBYesRemarks describing special circumstances related to this park that will appear exactly as written in the report.
TREATMENTVARCHAR2(50 BYTE)YesALL: Recommended repair type based on distress ratings.

TREATMENT_COST NUMBER(9,0) Yes ALL: Cost of recommended repair for this section.

TREATMENT_DESCRIPTION VARCHAR2(255 BYTE) Yes ALL: Description of the recommended treatment.

UNPAVED_RATING NUMBER(3,0) No -1 DYNAMIC-UNPAVED: DYNAMIC-UNPAVED: Condition Rating for unpaved routes. A PASER score is arrived at based on the scores of the distresses (excludes dust). The score would be populated here and would be 1,2,3,4, or 5.

UNP_CROWN_SCORE NUMBER(1,0) No -1 DYNAMIC-UNPAVED: DYNAMIC-UNPAVED: This will be scored based on the longest length of Crown after weighting has occurred. Should only be be populated with 1,2, or 3.

UNP_CROWN_URG NUMBER(4,1) No -1 DYNAMIC-UNPAVED: DYNAMIC-UNPAVED: Crown - urgent severity. LENGTH NOT PERCENTAGE. Measured in feet. This will be the raw length in feet (from GPS breadcrumbs) of crown of URGENT severity. This number would be populated prior to any weighting.

UNP_CROWN_HI NUMBER(4,1) No -1 DYNAMIC-UNPAVED: Crown - high severity. LENGTH NOT PERCENTAGE. Measured in feet. This will be the raw length in feet (from GPS breadcrumbs) of crown of HIGH severity. This number would be populated prior to any weighting.

UNP_CROWN_MED NUMBER(4,1) No -1 DYNAMIC-UNPAVED: Crown - medium severity. LENGTH NOT PERCENTAGE. Measured in feet. This will be the raw length in feet (from GPS breadcrumbs) of crown of MEDIUM severity. This number would be populated prior to any weighting.

UNP_CROWN_LOW NUMBER(4,1) No -1 DYNAMIC-UNPAVED: Crown - low severity. LENGTH NOT PERCENTAGE. Measured in feet. This will be the raw length in feet (from GPS breadcrumbs) of crown of LOW severity. This number would be populated prior to any weighting.

UNP_CROWN_REPORTNVARCHAR2(20 CHAR)YesText version of segment severity for Crown distress: High, Med, or Low
UNP_DRAIN_REPORTNVARCHAR2(20 CHAR)YesText version of segment severity for Drainage distress: High, Med, or Low
UNP_RUT_WB_REPORTNVARCHAR2(20 CHAR)YesText version of segment severity for Rutting & Washboarding distress: High, Med, or Low
UNP_POT_LA_REPORTNVARCHAR2(20 CHAR)YesText version of segment severity for Potholes & Loose Aggregate distress: High, Med, or Low
UNP_DUST_REPORTNVARCHAR2(20 CHAR)YesText version of segment severity for Dust distress: High, Med, or Low
PAVED_RATINGNUMBER(3,0)No-1DCV/DYNAMIC-ASPHALT: Pavement Condition Rating: PCR = (0.60*SCR)+(0.40*RCI)

IF SCR = -1, then the formula simply reduces to: PCR = RCI.

IF RCI = “-1” meaning roughness was not collected for the route, then the formula simply becomes PCR = SCR.

DCV_SCR NUMBER(3,0) No -1 DCV/DYNAMIC-ASPHALT: Surface Condition Rating: SCR = Lowest Index Value of [SC_INDEX or TC_INDEX or PATCH_INDEX or RUT_INDEX].

DCV_RCINUMBER(3,0)No-1DCV ONLY: Roughness will only be rated on paved routes longer than 0.5 miles and with a posted speed limit of 25mph or higher. The following Roughness Condition Index (RCI) will be used for each category.
AC_INDEXNUMBER(3,0)No-1DCV/DYNAMIC-ASPHALT: Alligator Cracking Index: AC_INDEX = 100 - (40 * ( (AC_LOW / 35) + (AC_MED / 15) + (AC_HI / 5) ) ). Should be a number between 0 and 100, rounded to the nearest whole number.

LC_INDEX NUMBER(3,0) No -1 DCV/DYNAMIC-ASPHALT: Longitudinal Cracking Index: LC_INDEX = 100 - (40 * ( (LC_LOW / 175) + (LC_MED / 75) + (LC_HI / 25) ) )

MRL_LC_SEV
TC_INDEXNUMBER(3,0)No-1DCV/DYNAMIC-ASPHALT: Transverse Cracking Index: TC_INDEX = (100 - (40 * ( (TC_LOW / ((INT_LENGTH / 105.6) * 21.1)) + (TC_MED / ((INT_LENGTH / 105.6) * 4.4)) + (TC_HI / ((INT_LENGTH / 105.6) * 2.6)) ) ) )

PATCH_INDEX NUMBER(3,0) No -1 DCV/DYNAMIC-ASPHALT: Patching Index: PATCH_INDEX = 100 - (40 * (PATCHING / 80) )

RUT_INDEX NUMBER(3,0) No -1 DCV/DYNAMIC-ASPHALT: Rutting Index: RUT_INDEX = 100 - (40 * ( (RUT_LOW / 535) + (RUT_MED / 205) + (RUT_HI / 40) ) ). MRL - number input

SC_INDEX NUMBER(3,0) No -1 DCV ONLY: Structural Cracking Index: SC_INDEX = 100 - ((100 - AC_INDEX) + (100 – LC_INDEX))

PATCHINGNUMBER(7,2)YesPatching (percentage of the total lane area).
MRL_RATING_METHODVARCHAR2(9 BYTE)NoMRL Rating method - Simple or Detailed
CO_JOINT_FAULT_INDEXNUMBER(3,0)YesManual Rating PCR Index Score for CONCRETE Joint Faulting (Excellent = 97; Good = 90; Fair = 73; Poor = 53)
CO_JOINT_DISTRESS_INDEXNUMBER(3,0)YesManual Rating PCR Index Score for CONCRETE Joint Distresses (Excellent = 97; Good = 90; Fair = 73)
CO_SLAB_CRACK_INDEXNUMBER(3,0)YesManual Rating PCR Index Score for CONCRETE Slab Cracking (Excellent = 97; Good = 90; Fair = 73; Poor-53 = 53; Poor-30 = 30)
CO_DELAM_POP_INDEXNUMBER(3,0)YesManual Rating PCR Index Score for CONCRETE Surface Delamination and Popouts (Excellent = 97; Good = 90; Fair = 73; Poor = 53)
CO_PATCH_INDEXNUMBER(3,0)YesPatch index equals (100 - 40*Percent of patching / 80)
DCV_D_LANE_WIDTHNUMBER(7,3)YesDCV: Distress Lane Width: Software or operator measured. Do NOT use as LANE_WIDTH. This field is used in INDEX calculation only.

DCV_FORCED_PCR NUMBER(1,0) Yes DCV: When a manual PCR is applied to DCV route this field will be populated with “YES” when not applied, field will be “NO.”

DCV_IRI_AVG NUMBER(7,1) Yes DCV: IRI_AVG = Average of Left Wheelpath IRI_L and Right Wheelpath IRI_R: (( IRI_L + IRI_R) / 2). When IRI_FLAG = 1 then IRI_AVG = -1. The IRI_AVG High Limit is 999.9

DCV_IRI_SD NUMBER(7,1) Yes DCV: Standard deviation of original roughness data for the Left Wheelpath and the Right Wheelpath. The IRI_AVG High Limit is 999.9

DCV_IRI_L NUMBER(7,1) Yes DCV: Left Wheelpath IRI. The IRI_AVG High Limit is 999.9

DCV_IRI_R NUMBER(7,1) Yes DCV: Right Wheelpath IRI. The IRI_AVG High Limit is 999.9

DCV_IRI_FLAGNUMBER(1,0)YesDCV: IRI Flag: The IRI Flag indicates invalid or non-attainable IRI. Default = “0”. Flag = 1" (Invalid IRI Data or when ROUTE_ID.IRI_STATUS = NO).
DCV_RUT_AVGNUMBER(7,2)YesDCV: Average Rut Depth value (both wheel paths).

DCV_RUT_MAX NUMBER(7,2) Yes DCV: Maximum Rut Depth value (both wheel paths)

DCV_RUT_SD NUMBER(7,1) Yes DCV: Standard Deviation of Left Wheelpath and Right Wheelpath Rut Depth values

DCV_RUT_LOW NUMBER(3,0) Yes DCV: Percent of LOW severity ruts in Left Wheelpath based on 20 ruts, plus percent of LOW severity ruts in Right Wheelpath based on 20 ruts. A LOW severity rut is > or = 0.20” and < or = 0.49”

DCV_RUT_MED NUMBER(3,0) Yes DCV: Percent of MEDIUM severity ruts in Left Wheelpath based on 20 ruts, plus percent of MEDIUM severity ruts in Right Wheelpath based on 20 ruts. A MEDIUM severity rut is > or = 0.50” and < or = 0.99”

DCV_RUT_HI NUMBER(3,0) Yes DCV: Percent of HIGH severity ruts in Left Wheelpath based on 20 ruts, plus percent of HIGH severity ruts in Right Wheelpath based on 20 ruts. A HIGH severity rut is > or = 1.00”

DCV_AC_LOW NUMBER(7,2) Yes DCV: Alligator Cracking - low severity. Percentage of summarized segment that has Low severity selected. Percentage should be multiplied by 100 and reported to 2 decimals.

DCV_AC_MED NUMBER(7,2) Yes DCV: Alligator Cracking - medium severity. Percentage of summarized segment that has Medium severity selected. Percentage should be multiplied by 100 and reported to 2 decimals.

DCV_AC_HI NUMBER(7,2) Yes DCV: Alligator Cracking - high severity. Percentage of summarized segment that has High severity selected. Percentage should be multiplied by 100 and reported to 2 decimals.

DCV_LC_LOW NUMBER(7,2) Yes DCV: Longitudinal Cracking - low severity (percent based on length of lane). % of length with low severity longitudinal cracks per lane, multiplied by 100.

DCV_LC_MED NUMBER(7,2) Yes DCV: Longitudinal Cracking - medium severity (percent based on length of lane). % of length with medium severity longitudinal cracks per lane, multiplied by 100.

DCV_LC_HI NUMBER(7,2) Yes DCV: Longitudinal Cracking - high severity (percent based on length of lane). % of length with high severity longitudinal cracks per lane, multiplied by 100

DCV_TC_LOW NUMBER(7,2) Yes DCV: Transverse Cracking - low severity (total number of full length cracks based on LANE_WIDTH). Number of low severity full lane width cracks per summarized segment.

DCV_TC_MED NUMBER(7,2) Yes DCV: Transverse Cracking - medium severity (total number of full length cracks based on LANE_WIDTH). Number of medium severity full lane width cracks per summarized segment.

DCV_TC_HI NUMBER(7,2) Yes DCV: Transverse Cracking - high severity total number of full length cracks based on LANE_WIDTH. Number of high severity full lane width cracks per summarized segment.

DCV_VIDEO NUMBER(3,0) Yes DCV: Three digit set number that was assigned in the field by the DCV crew.

DCV_IMAGE_NAME VARCHAR2(16 BYTE) Yes DCV: JPEG Image Reference Number (Contractor designated)

DCV_SPEED NUMBER(2,0) Yes DCV: Collection Vehicle Test Speed

DCV_CONSTR_FLAGNUMBER(1,0)YesDCV: Construction Flag: The Construction Flag indicates that there is construction on the road at the time of data collection. Value of 1" indicates construction on road. Default = “0”. Flag = "1" (Construction on Road Occurrence).
DCV_DOR_FLAGNUMBER(1,0)YesDCV: Debris On Road Flag: The Debris on Road Flag indicates that the debris on road inhibits accurate data collection. Value of 1" indicates debris on road (water, leaves, dirt, etc.). Default = “0”. Flag = "1" (Debris On Road Occurrence).
QUICK_RATINGVARCHAR2(20 BYTE)No'NOT APPLICABLE'Field used to input Quick Rating value for ASPHALT and CONCRETE routes. CONCRETE MRLs with FC 3-6 ONLY get a Quick Rating. When the Quick Rating does NOT equal NOT APPLICABLE, the other distress values MUST equal to NOT APPLICABLE.

ROADS Feature Class

ROADS FEATURE CLASS
COLUMN_NAMEDATA_TYPENULLABLEDATA_DEFAULTCOMMENTS
OBJECTIDNUMBER(38,0)NoInternal sequential number required by ESRI Geodatabase.
GLOBAL_IDVARCHAR2(38 CHAR)NoGlobal ID - Unique identifier with time stamp
SHAPEST_GEOMETRYYesESRI Generated field holding the types of geometry (ST_GEOMETRY)
AGENCYVARCHAR2(5 BYTE)NoLand Management Agency (NPS, BOR, FWS)
ROUTE_IDENTVARCHAR2(25 BYTE)NoUnique record identifier: UNIT_ID – RTE_NO
CYCLENUMBER(2,1)YesCurrent RIP cycle
UNIT_IDVARCHAR2(10 BYTE)NoUnique code assigned within orginazation to differenciate collection units (NPS- PARK_ALPHA, FWS - ORG_CODE, BOR-AREA_OFFICE)
ROUTE_NUMVARCHAR2(6 BYTE)YesRoute number of the BOR asset
ROUTE_LENGTHNUMBER(7,3)YesLength of the entire route in miles
SURF_TYPEVARCHAR2(2 BYTE)NoSurface type for the majority of the route. Please see the SURFACE_TYPES table for a listing of the possible PAVED and UNPAVED surface types.
SOURCEVARCHAR2(50 BYTE)Yes
SHAPE.LENDouble

ROUTE_GPS

ROUTE_GPS
COLUMN_NAMEDATA_TYPENULLABLEDATA_DEFAULTCOMMENTS
OBJECTIDNUMBER(38,0)NoInternal sequential number required by ESRI Geodatabase.
ROUTE_IDENTVARCHAR2(15 BYTE)NoUnique record identifier: PARK_ALPHA – RTE_NO
CYCLENUMBER(2,1)NoCurrent RIP cycle
UNIT_IDVARCHAR2(4 BYTE)NoUnique four letter code assigned to NPS unit.
MILEAGE_GPS_MATCH_CYCLENUMBER(1,1)YesIndicates whether to use LANE_MILES, PAVE_WIDTH, LANE_WIDTH, PAVED_MI, UNPAVED_MI, RTE_LENGTH, and the route’s GPS information from the previous cycle’s ROUTE_GPS table. (Cycle Number)
MILEAGE_GPS_MATCH_ITERATIONNUMBER(1,0)YesIF ROUTE_ID.MILEAGE_GPS_MATCH = 6, this field will indicate which iteration to match to. Otherwise the value will be "1".
STATEVARCHAR2(2 BYTE)YesState abbreviation in which route resides
MPNUMBER(7,3)NoMile Post of GPS coordinate
GPS_LATNUMBER(9,6)YesGPS Latitude Coordinate at BEG_MP (decimal degrees)
GPS_LONNUMBER(9,6)YesGPS Longitude Coordinate at BEG_MP (decimal degrees)
GPS_ELEVNUMBER(7,1)YesGPS Elevation at BEG_MP (feet)
CROSS_SLOPENUMBER(7,1)YesCross Fall: % Cross slope at station
GRADENUMBER(7,1)YesGrade: % Profile slope at station
HEADINGNUMBER(7,1)YesHeading Relative to True North
INSP_DATEDATEYesDCV Collection Date of when GPS was collected.
COMMENTSCLOBYesSource of any digitized data

ROUTE_ID

ROUTE_ID
COLUMN_NAMEDATA_TYPENULLABLEDATA_DEFAULTCOMMENTS
OBJECTIDNUMBER(38,0)NoInternal sequential number required by ESRI Geodatabase.
GLOBAL_IDVARCHAR2(38 CHAR)NoGlobal ID - Unique identifier with time stamp
AGENCYVARCHAR2(5 BYTE)NoLand Management Agency (NPS, BOR, FWS)
REGIONVARCHAR2(100 BYTE)YesInternal Agency Region
ROUTE_IDENTVARCHAR2(25 BYTE)NoUnique record identifier: PARK_ALPHA – RTE_NO
CYCLENUMBER(2,1)YesCurrent RIP cycle
UNIT_IDVARCHAR2(10 BYTE)NoUnique code assigned within orginazation to differenciate collection units (NPS- PARK_ALPHA, FWS - ORG_CODE, BOR-AREA_OFFICE)
CYCLE_COLLECTEDVARCHAR2(2 BYTE)YesThe Cycle that the data was collected. Routes that were not collected should be coded as NC.
ROUTE_NUMVARCHAR2(15 BYTE)NoFHWA-RIP Route Number unique to linear referencing system
ROUTE_NAMEVARCHAR2(100 BYTE)YesRoute Name
FROM_DESCVARCHAR2(255 BYTE)YesDescription of beginning point of route.
TO_DESCVARCHAR2(255 BYTE)YesDescription of end point of route.
INSP_DATEDATEYesData Collection Date: Only populate if route was rated for condition.
FUNCT_CLASSNUMBER(1,0)YesFunctional Classification (1-8)
USER_ACCESSVARCHAR2(20 BYTE)YesAccess Designation for ALL ROUTES (Public or Nonpublic).
STATE1VARCHAR2(2 BYTE)YesState abbreviation in which route resides
STATE1VARCHAR2(2 BYTE)YesAdditional state in which route resides
STATE1VARCHAR2(2 BYTE)YesAdditional state in which route resides
ASSET_NUMVARCHAR2(15 BYTE)YesAgency Asset number associated with Route.
SUB_UNITVARCHAR2(50 BYTE)YesAgency Sub-Unit in which Route resides. Leave field empty when an Agency site is NOT split into Sub-Units.
COLL_METHODVARCHAR2(10 BYTE)YesMethod by which route was collected. Routes that were not collected should be coded as NC.
CONCESSIONNUMBER(1,0)No0Concession Flag: Value of 1 indicates that Route is maintained by Concessionaire. Default: 0. Flag: 1 (Concession route).
MILEAGE_GPS_MATCH_CYCLENUMBER(1,1)No-1Indicates whether to use PAVED_MI, UNPAVED_MI, RTE_LENGTH, and the route’s GPS information from the previous cycle’s ROUTE_GPS table. (Cycle Number)
MILEAGE_GPS_MATCH_ITERATIONNUMBER(1,0)No-1IF ROUTE_ID.MILEAGE_GPS_MATCH = 6, this field will indicate which iteration to match to. Otherwise the value will be 1.
PAVED_LENGTHNUMBER(7,3)Yes0Length of paved portion of route in miles.
UNPAVED_LENGTHNUMBER(7,3)Yes0Length of unpaved portion of route in miles. Routes can have both paved and unpaved mileage
RTE_LENGTHNUMBER(7,3)No0RTE_LENGTH = PAVED_MI + UNPAVED_MI
SURF_TYPEVARCHAR2(2 BYTE)NoSurface type for the majority of the route. Please see the SURFACE_TYPES table for a listing of the possible PAVED and UNPAVED surface types.
UNPAVED_STATUSVARCHAR2(4 BYTE)NoNULLIndicates whether the route is paved, unpaved, or both. (“YES, “NO”, “BOTH”)
SQFTNUMBER(7,0)No-1Area of route/parking lot in square feet.
LANE_NONUMBER(1,0)No-1The number assigned to the lane in which data was collected. Numbered 1,2,3, etc. from centerline or median from left to right. All non-linear features or routes not collected should be populated with -1.
NUM_LANESNUMBER(1,0)No-1Number of travel lanes on route.
WIDTH_FLAGNUMBER(1,0)No0Width Flag: Used to indicates if new widths need to be taken for the record by the DATA CONTRACTOR. Value of 1 indicates that a new width must be taken. Default: “0”. Flag: 1 (Width Flag).
DISTRESS_FLAGNUMBER(1,0)No0Distress Flag: Used to indicate if distress to reported for the record by the DATA CONTRACTOR. Value of 1 indicates that distress must be taken. Default: “0”. Flag: 1 (Distress Flag).
ROAD_WIDTHNUMBER(7,1)No-1Weighted Average Road Width for entire route for DCV routes. Calculated using PMS_20.PAVE_WIDTH weighted by PMS_20.INT_LENGTH. MRL PAVE_WIDTH value is field collected.
LANE_MILESNUMBER(7,3)No-1DCV and MRL routes Lane Miles = (PAVE_WIDTH x PAVED_MI) / 11 foot lane. Parking Area Lane Miles = SQ_FEET / 5280 / 11. Manually Rated Polygons = SQ_FEET / 5280 / 11. Unpaved Routes = Not reported. (Represents a summation of all Subcomponent records for Summary Routes)
AREA_MAPVARCHAR2(20 BYTE)YesReference Area Map Number for current cycle report.
COMMENTSCLOBYesGeneral remarks on record and data collection operations.
ROUTE_PARENTVARCHAR2(20 BYTE)YesField specifies if record should be reported in the Route ID Report (populate field with REPORT) or if it’s a subcomponent and must appear in the Subcomponent Route ID Report (populate field with a valid ROUTE_IDENT).
SUBCOMPONENTNUMBER(1,0)No0Subcomponent Flag: Identifies a route as a Subcomponent of another park route: Value of 1 indicates that route is a Subcomponent route. Default: 0. Flag: 1 (Subcomponent Flag).
BEG_LATNUMBER(9,6)YesGPS Latitude Coordinate at BEG_MP (decimal degrees), Parking the centroid Latitude
BEG_LONNUMBER(9,6)YesGPS Longitude Coordinate at BEG_MP (decimal degrees), Parking the centroid Longitude
END_LATNUMBER(9,6)YesGPS Latitude Coordinate at End of route milepost (decimal degrees)
END_LONNUMBER(9,6)YesGPS Longitude Coordinate at End of route milepost (decimal degrees)
WIP_DATANUMBER(3,0)No-1WIP Data: Used to indicates total retaining wall count on the route. Default: “-1” (indicates no data available). Other values are actual retaining wall count.
GIP_DATANUMBER(3,0)No-1GIP Data: Used to indicates total barrier count on the route. Default: “-1” (indicates no data available). Other values are actual barrier count.
ACTION_TIMESTAMPDATEYesThe date an alignment action (Add New, Match, Remove, Combine, and Split) took place on the record.
ALIGNMENT_ACTIONVARCHAR2(15 BYTE)YesThe action performed on the record. Please see the ALIGNMENT_ACTION table for a listing of the possible Alignment Action values.
TEMP_RIP_IDVARCHAR2(15 BYTE)YesTEMP_RIP_ID is created and used by the Alignment Tool.
RTE_SERIESNUMBER(4,0)YesThe series of numbers that the RTE_NO falls into (Values are 100,200,300,400,500,600,700,800,900,1000,5000). Value is calculated by triggers from ROUTE_IDENT.
FURTHER_ACTION_REQNUMBER(1,0)No0Field is used to show if follow-up work is required (i.e., if route was added during Alignment) before route entry is considered complete. Default: 0 (Route ID is up-to-date). Flag: 1 (Route ID is NOT up-to-date. A common use of value 1 will be to show the PKG need to be collected by the DCV.)
LANE_WIDTHNUMBER(7,1)No-1Weighted calculated Lane Width
BEG_MP_DCVNUMBER(7,3)Yes-1Starting Mile Point for DCV Route
END_MP_DCVNUMBER(7,3)Yes-1Ending Mile Point for DCV Route
PARTNERVARCHAR2(5 BYTE)NoThe partnering agency that requested this data to be collected for the Road Inventory Program: NPS, FWS, USACE, BLM, USFS, BOR.
FLTPVARCHAR2(3 BYTE)YesIndicates if the route is eligible for funding under the Federal Lands Transportation Program.
NHS_MINUMBER(7,3)No-1Indicates how many miles are in the National Highway System (NHS) network.
OWNERVARCHAR2(25 BYTE)YesEntity who ownes the feature
MAINTAINERVARCHAR2(25 BYTE)YesEntity responsible for maintaining the feature
FACILITY_TYPEVARCHAR2(40 BYTE)YesHPMS manual one way, two way, ramp or Parking - match HPMS
ASSET_TYPEVARCHAR2(20 BYTE)YesRoad or parking
COUNTY_CODENUMBER(4,0)YesFIPS code
TIERNUMBER(1,0)YesFWS priority level
REPORT_COMMENTSCLOBYesUrgent items to address and show on report - specific to current cycle
ISVALIDNUMBER(1,0)YesUsed for Rival appliction
LENGTH_UNITNUMBER(2,0)YesUnit of measure - miles, feet
DISTRICTVARCHAR2(50 BYTE)YesFWS - Congressional District code

WIDTH_MEASURE

WIDTH_MEASURE
COLUMN_NAMEDATA_TYPENULLABLEDATA_DEFAULTCOMMENTS
OBJECTIDNUMBER(38,0)NoInternal sequential number required by ESRI Geodatabase.
GLOBAL_IDVARCHAR2(38 CHAR)NoGlobal ID - Unique identifier with time stamp
AGENCYVARCHAR2(5 BYTE)NoLand Management Agency (NPS, BOR, FWS)
ROUTE_IDENTVARCHAR2(15 BYTE)NoUnique record identifier: PARK_ALPHA – RTE_NO
CYCLENUMBER(2,1)NoCurrent RIP cycle
UNIT_IDVARCHAR2(4 BYTE)NoUnique four letter code assigned to NPS unit.
MEASUREMENT_MPNUMBER(7,3)YesThe Mile Post where the measurement was taken.
BEG_MPNUMBER(7,3)NoThe beginning Mile Post for the section of road for which the width measurement is to be used.
END_MPNUMBER(7,3)YesThe ending Mile Post for the section of road for which the width measurement is to be used.
LANE_WIDTHNUMBER(7,1)YesFrom inside centerline to inside fogline. When no fogline, from inside centerline to edge-of-pavement. When no striping at all, PAVE_WIDTH / NO_LANES.
PAVE_WIDTHNUMBER(7,1)YesFrom edge of pavement to edge of pavement.
SHOULDER_WIDTHNUMBER(7,1)Primary lane - Fog line to edge of pavement.
BIKE_LANE_WIDTHNUMBER(7,1)
COMMENTSCLOBYesRemarks describing special circumstances related to this park.

File details come from the government source that posted it. Updated .