Utah State Route 63

Utah State Route 63 (SR-63) is a state highway in the U.S. state of Utah. Just 2.63 miles (4.23 km) long, it serves as a connection between Utah State Route 12 (a scenic byway) and Bryce Canyon National Park.

State Route 63
Route information
Defined by Utah Code §72-4-112
Maintained by UDOT
Length2.630 mi[1] (4.233 km)
Existed1975[2]–present
Major junctions
South endNorth boundary of Bryce Canyon National Park
North end SR-12 at Tropic Junction
Highway system
  • State highways in Utah
SR-62SR-64

Route description

SR-63 approaching its terminus at SR-12

Starting from the northern edge of Bryce Canyon National Park, the route runs northward, passing a view area, and exiting Dixie National Forest within the first mile. It continues north until its terminus at the intersection with SR-12 less than two miles later.

Bryce Canyon National Park entrance near South terminus of SR-63

History

Previous designation

This route number was originally in use from 1931  1971 as a route from Salina to Scipio. The route number was withdrawn when this route was transferred to SR-26, and subsequently designated as part of US-50.

Current designation

Utah State Route 12 originally had a short spur serving Bryce Canyon. This spur was split off into a distinct highway, SR-63, in 1975.[2]

Major intersections

The entire route is in Garfield County.

Locationmi[1]kmDestinationsNotes
0.0000.000North boundary of Bryce Canyon National ParkSouthern terminus
0.4940.795View area
Tropic Junction2.6304.233 SR-12Northern terminus
1.000 mi = 1.609 km; 1.000 km = 0.621 mi
gollark: I've heard that Apple's Swift does it "properly", no idea about anything else.
gollark: I think most languages which don't have string handling explicitly designed for new Unicode thingies will have that sort of issue.
gollark: If JS was replaced with some other language but `script` tags and whatnot were still used, we would still have the exploits, probably.
gollark: It's mostly not really a JS problem.
gollark: I mean, the main reason JS is used in websites is just that you couldn't use anything else until... about three years ago with WASM, and that has a bunch of problems, more than its actual merits as a language, but I haven't heard much about it being particularly exploit-prone.

References

This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.