Highway 14 Utah Update Download Free Software

23-04-2021

Highway 14 Utah Update Download Free Software

Highway 14 Utah Update Download free. software download
Highway 14 Utah Update download free, software Free
Highway 14 Utah Update Download free. software downloads

The UP SP Lone Pine Branch starts at the Main 2 Switch just north of Mojave Yard, heading northeast across Highway 14. This branch originally ran for about 150 miles to Lone Pine, CA. In the early 1980's, the Southern Pacific Railroad filed for abandonment of roughly 100 miles from Searles, CA, to Lone Pine. Mobile user - Highway conditions - Enter highway for text of restrictions, closures. (Caltrans Division of Traffic Operations) Mountain pass closures - Includes pass (Ebbetts, Monitor, Lassen Loop, Sonora, Tioga, June Lake Loop, Mammoth Lakes, Lake Sabrina to Aspendell), route, period. Click route for details. Ramps / Collectors / Other. Download Driver air print. The easiest way to print the RedPrint Cloud (Requires OSX 10.6 or later). SALT LAKE CITY, UTAH 84112 801.581.5013. (KUTV) United States Highway 89 in Davis and Weber counties is approved to become a full freeway but faces possible legal action from citizens.Utah Department of Transportation made the decision.

Roads and Highway System

Category:Transportation
Data Type: GIS Data Layer
Steward(s): AGRC, Local Government partners
Abstract: This dataset contains GIS mapping data representing the statewide roads centerline dataset for Utah and other road and highway related data such as milepost locations, exit numbers and names, polylineM highway linear referencing system (LRS) routes, and label lines for dynamic rendering of highway shields.

Transportation.Roads is a multi-purpose statewide roads dataset for cartography, routing, and range based-address location. This dataset is also used as the base geometry for deriving the GIS-representation of UDOT’s highway linear referencing system (LRS) as well as AGRC's network analysis datasets.

This layer also plays an important role in active transportation planning in Utah. Recent collaborative efforts between AGRC, UDOT, and WFRC have led to significant enhancements in the bike and pedestrian data in both the Roads and Trails-and-Pathways layers. These efforts have focused on better connectivity between the layers (along the Wasatch Front), as well as improvements in the statewide bike data. You can contribute to the on-street bike data by letting us know where we have gaps or inaccurate information.

Transportation.Roads utilizes a data model based on Next-Generation 911 standards and the Federal Highway Administration's All Roads Network Of Linear-referenced Data (ARNOLD) reporting requirements for state DOTs. AGRC adopted this data model on September 13th, 2017.

To see specific information about the data model including field names and descriptions, data types, coded value domains, and data model updates, see the data model spreadsheet and the corresponding tabs for update notes and coded value domains. The color-coded section titled Addressing is primarily maintained by the local stewards, where as the section titled DOT/FHWA is primarily maintained by UDOT. AGRC spatially assigns fields in the section titled Placename/Area, based on current SGID polygon boundaries. AGRC also generates the UNIQUE_ID field based on the segment's location in the US National Grid, with the street name then tacked on. The UNIQUE_ID field is static and is AGRC's current, ad hoc solution to a persistent global id.

This data model is meant to suggest 'best practices'. It is not the intent that all stewards will change their current data management process to match this standard, but rather that stewards will evaluate their current practices to see how well their data 'maps' to this schema for data sharing and Next Generation 911 preparedness.

Comments, questions, compliments, or concerns can be directed to Greg Bunce from AGRC at GBunce@utah.gov or 801-349-0039.

The native spatial reference for this dataset is UTM Zone 12N, NAD83 (0.01 meter coordinate precision). The statewide roads dataset is maintained by AGRC in partnership with local government, the Utah 911 Committee, and UDOT.

Related Resources

Updates to this dataset are published every month, with approximately nine counties receiving detailed review.

Transportation.UDOTRoutes_LRS is a polylineM dataset wherein each state and federal route is a single feature whose vertices include a milepost measure coordinate.

Major routes are named using UDOT’s 5 character convention (ex. 0089P is US 89 in the positive direction). Ramps and collectors are also included and have 11 character identifiers (ex. 0080PR18501 is the east bound off ramp at exit 185 on I-80). ‘P’ direction routes are those in the direction of increasing milepost values. ‘N’ direction routes for the Utah’s 5 freeways (0015, 0070, 0080, 0084, 0215) should be ignored (use ‘X’ instead) except when working with UDOT-specific LRS event features.

The native spatial reference for this dataset is UTM Zone 12N, NAD83 (0.01 meter x,y coordinate precision; 0.001 mile m coordinate precision). The GIS dataset representing the UDOT LRS is stewarded by UDOT with assistance from DTS, AGRC and local government.

The CARTO code can be used to query subsets or classify different types of UDOT routes:

1: Interstate highways
2: US highways
3: State highways
5: Miscellaneous routes associated with interchanges
6: Ramps, Interstates
7: Ramps, US Highways
8: Ramps, State highways
9: Local routes, federal aid eligible
I: Institutional roads designated as state highways

Related Resource

Updates to this dataset are published periodically to refine route representation, add additional routes, and in response to route realignment.

Transportation.UDOTMileposts represents the approximate location of state and federal highway mileposts as a single point. This dataset is derived directly from SGID10.Transportation.UDOTRoutes_LRS.

See this info sheet to learn more about the difference between mile reference posts that are seen on the side of the road and linear referencing system mile point measures (milepost points).

Major routes are named using UDOT’s 5 character convention (ex. 0089P is US 89 in the positive direction). ‘P’ direction routes are those in the direction of increasing milepost values. ‘N’ direction routes for the Utah’s 5 freeways (0015, 0070, 0080, 0084, 0215) should be ignored (use ‘X’ instead) except when working with UDOT-specific LRS event features.

Per UDOT policy the actual location of mileposts can vary up to 50 feet, from the measured position where intersections and physical infrastructure make a more 'true' positioning impractical or undesirable.

The native spatial reference for this dataset is UTM Zone 12N, NAD83 (0.01 meter coordinate precision). The GIS dataset representing the UDOT LRS is stewarded by UDOT with assistance from DTS, AGRC and local government.

Updates to this dataset are published periodically.

Transportation.UDOTTenthMileRefPoints represents the approximate location of state and federal highway tenth of a mile locations as a single point. This dataset is derived directly from SGID10.Transportation.UDOTRoutes_LRS.

See this info sheet to learn more about the difference between mile reference posts that are seen on the side of the road and linear referencing system mile point measures (milepost points).

Highway 14 utah update download free, software free

Per UDOT policy the actual location of tenth of mile locations can vary up to 50 feet, from the measured position where intersections and physical infrastructure make a more ‘true’ positioning impractical or undesirable.

The native spatial reference for this dataset is UTM Zone 12N, NAD83 (0.01 meter coordinate precision). This dataset was assembled by UDOT for general purpose cartography.

Updates to this dataset are published periodically.

Transportation.Roads_FreewayExits contains point locations for each freeway and limited access highway exit along with the exit number, name, associated route, and connected streets/routes.

The EXITNAME field provides the primary route name and exit number plus the connecting route number or street name and place name carried by the exit sign. Route number and exit number are also carried in separate fields.

The native spatial reference for this dataset is UTM Zone 12N, NAD83 (0.01 meter coordinate precision). This dataset was assembled by AGRC from resources provided by UDOT, as a resource for 911 dispatch and for general map reference.

Highway 14 Utah Update download free, software

Updates to this dataset are published infrequently.

Transportation.RoadsShieldLines consists of highway route lines edited to best enable non-redundant, dynamic label rendering of highway shields for freeways, US highways, and state highways.

In ArcMap, define a label class for each CLASS field value. 1 is for freeways, 2 for US highways, and 3 is for state highways. Each label class should use a SQL expression to define the class and the default class should be disabled or deleted.

When defined labeling properties are defined properly, the minimum number of freeway and highway shields should be displayed without introducing ambiguity.

The native spatial reference for this dataset is UTM Zone 12N, NAD83 (0.01 meter coordinate precision). This dataset was assembled by AGRC for general purpose cartography.

Updates to this dataset are published infrequently.

Windows Printing Options

windows setup

Send your print job directly to the RedPrint Cloud from your desktop.

Email printing

Send your print job to the RedPrint Cloud from any device using your email.

Mac Printing Options

mac setup

Send your print job directly to the RedPrint Cloud from your desktop.

mac driver

Dowload the Mac printer driver to send print jobs directly to the RedPrint Cloud.