CDOT HUTF Help :: Edit Segments By File Upload

Colorado Department of Transportation HUTF Edit Segment Page

Help Home

Welcome to the HUTF Edit Segments By File Upload page!

The Edit Roadway Segments by File Upload is a tool for editing your jurisdiction's entire roadway inventory by simply uploading an Excel (.xlsx) file.

Process

Step 1. Download the Requirements and Change Validation

Download the Requirements and Change Validation document. This document describes the validation requirements.

Step 2. Download Roadway Inventory

Download your jurisdiction's roadway inventory. Select Download Roadway Inventory link. The application will save an Excel (.xlsx) file to your Downloads folder. You will need to have an Excel version 2007 or newer edit your jurisdiction's roadway inventory. You may be prompted to save the file. The file is safe to save. The application additionally saves a copy of your jurisdiction's roadway inventory in the Upload / Download Data section of the site. Do not change the order or rename the columns on the worksheet.

As WebHUTF generates the Excel file it will validate each segment in your inventory. Rows with validation errors are orange. Red cells are invalid and need to be addressed. The last column of the worksheet reports the specific error(s). Tan columns are 'read-only'. Their values should not change. Note, for city jurisdictions the ROUTE NAME columns is ‘read-only.' It will be highlighted in tan. This column is editable for county jurisdictions and is not highlighted.

Step 3. Upload Edits

Using Excel 2007 or newer edit your jurisdiction's roadway inventory. At this time the tool only supports certain attribute changes. Adding, deleting, annexing, removing annexes, combining, splitting, and renaming roadway segments is not supported. Also, it is not necessary to edit each item in your inventory. You may 1) choose to remove segment rows that do not have changes from your file; or, 2) leave them untouched (they will be skipped when uploading changes in the next step). All previous WebHUTF validation rules apply (see the Validation section for more information). Do not change the order or rename the columns on the worksheet. When done, save the file as an Excel (.xlsx) with a new name.

Step 4. Upload Changes.

Upload roadway inventory edits by browsing to the file and upload it by clicking the "Apply Changes" button.

On uploading the file the application will:

Validate that the file is an Excel (.xlsx) workbook.
Append a time stamp to the file name and save the file under the Upload / Download Data section of the site.
Validate data in each row.
Read each row and update the roadway segment if it has changes and is valid. Rows with errors are skipped.
Create an error log file.
Save the error log file to the Upload / Download Data section of the site for your review.

If the upload was successful and there were no errors a green notice will appear in the top section of the page.

If there were errors a red notice would appear with instructions to download the error report. The report provides information as to the excel row, segment route, segment ID, and type of error. For a description of error types, refer to the Validations section. In most cases, the errors will need to be resolved before a successful change will be recorded in the Apply Changes function. Once they are fixed, you will need to upload the file after saving your changes, then Apply Changes once again.

Validation Requirements

The following validation requirements apply. Please read these carefully. As the application consumers your Excel changes, only rows that are valid will be saved.

FIP

FIPS is required and read-only. It should not be changed.

ROUTE

ROUTE is required and read-only. It should not be changed.

SEGMENT PREFIX

SEGMENT PREFIX is not required. However, if it is giving the value must be one of the following:

N – North
S – South
E – East
W – West

ROUTE NAME

ROUTE NAME is required and must be 1 to 30 characters long. ROUTE NAME is read-only and cannot be changed by city jurisdictions.

SEGMENT ID

SEGMENT ID is required and read-only. Is should not be changed.

FROM FEATURE

FROM FEATURE is required and must be between 1 and 30 characters long.

SEGMENT DIRECTION

SEGMENT DIRECTION is not required. However, if it's supplied it must be one of the following values:

N – North
S – South
E – East
W – West
NW – Northwest
SW – Southwest
NE – Northeast
SE – Southeast

TO FEATURE

TO FEATURE is required and must be between 1 and 30 characters long.

FOREST ROUTE

FOREST ROUTE is not required. However, if it's supplied it cannot exceed 10 characters in length.

LENGTH

LENGTH is required and must be a numeric value of .001 to 30. LENGTH cannot have more than 7 characters.

SURFACE TYPE

SURFACE TYPE is required and must be one of the numeric values below.

0 – (0) No Data
1 – (1) Asphalt
2 – (2) Asphalt over Concrete
3 – (3) Concrete
4 – (4) Concrete over Asphalt
11 – (11) Other
13 – (13) Primitive
14 – (14) Unimproved
15 – (15) Graded & Drained
16 – (16) Soil, Gravel, or Stone

Additionally if the ADMINISTRATIVE CLASS is 9, SURFACE TYPE must be 13.
If the SURFACE TYPE is 0 (zero), the ADMINISTRATIVE CLASS must be 4.

SURFACE CONDITION

SURFACE CONDITION is required and must be one of the values below:

G – Good
F – Fair
P – Poor

SURFACE WIDTH

SURFACE WIDTH is required and must be a non-decimal value between 1 and 200 feet.

THROUGH LANE QUANTITY

THROUGH LANE QUANTITY is required. This field must be a non-decimal value between 1 and 99. It additionally must be less that the SURFACE WIDTH.

THROUGH LANE WIDTH

THROUGH LANE WIDTH is required. This field must be a non-decimal value between 1 and 999.

OPERATION

OPERATION is required and must be one of the numeric values below:

1 – One-Way
2 – Two-Way

OVERLAY THICK

OVERLAY THICK is not required. However, if it's given the value must be a decimal value between 0 and 100 inches.

INSPECTION YEAR

INSPECTION YEAR is not required. However, if it's given the value must be between 1952 and the 2018.

PROJECT YEAR

PROJECT YEAR is not required. However, if it's given the value must be between 1952 and the 2018.

BUILT YEAR

BUILT YEAR is not required. However, if it's given the value must be between 1952 and the 2018.

ADMINISTRATIVE CLASS

ADMINISTRATIVE CLASS is required and must be one of the numeric values below:

0 – (0) Non-chargable Overlap
1 – (1) Arterial Service
2 – (2) Local Service
4 – (4) Proposed Local Jurisdiction
6 – (6) Toll Road
8 – (8) Open non-HUTF Eligible
9 – (9) Primitive/Non-maintained

Additionally, ADMINISTRATIVE CLASS cannot be changed from 0 to 1 or 2 – OR – 1 or 2 to 0.
If the SURFACE TYPE is 0 (zero), the ADMINISTRATIVE CLASS must be 4.

JURISDICTIONAL SPLIT

JURISDICTIONAL SPLIT is not required. However, if it's given the value must be one of the numeric values below:

0 – (0) None
1 – (1) County-County
2 – (2) City-County
3 – (3) City-City
5 – (5) State-State

HOV TYPE

HOV TYPE is required and must be one of the numeric values below:

0 – No HOV Lanes
1 – 24-Hour Exclusive Lanes
2 – Through Lanes used for HOV
3 – Shoulder / Parking used for HOV

SEGMENT KEY

SEGMENT KEY is required and read-only. It should not be changed.