Import Highway Projects Tool

This tool builds polyline features of all coded projects contained within a highway project coding spreadsheet (specified as the tool's sole parameter), appends them to the hwyproj feature class (or replaces existing versions) and stores all of the spreadsheet coding for the project in the hwyproj_coding table.

The program import_highway_projects_2.sas is automatically called (via sasrun.bat) to import the coding data directly from the spreadsheet, perform some error checking and reformat the data for import into the geodatabase.

This tool checks for the following errors:

• Highway link coding missing any of the four required fields: TIPID, ANODE, BNODE or ACTION
• Highway link coding using unavailable ANODE-BNODE combinations
• Incorrect action code applied to skeleton links
• Duplicate ANODE-BNODE coding within a single project
• Missing required attributes on new links (ACTION = 4)
• Missing or invalid replace node values, or unusable attribute values on replace links (ACTION = 2)
• If errors are encountered, they are written to temp/import_highway_projects_2.lst, all processing stops before any data are imported into the geodatabase and the user is prompted to correct the issues

When updating the coding for an existing project, this process can be facilitated by exporting the existing coding with the Export Highway Project Coding utility, then modifying the coding in the output CSV and saving it in XLSX format before re-importing it.

Neither this tool nor the project coding spreadsheet provides a means of specifying a project's completion year. The COMPLETION_YEAR attribute in the hwyproj attribute table can be edited manually after a successful import. Alternatively, if the project is imported for use in a Conformity analysis, the COMPLETION_YEAR attribute will be adjusted automatically when the Update Highway Project Years tool is run.