California State Route 125

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

<templatestyles src="Module:Hatnote/styles.css"></templatestyles>

For the cancer marker, see CA-125.

State Route 125 marker

State Route 125
Lua error in Module:Infobox_road/map at line 16: attempt to index field 'wikibase' (a nil value).
SR 125 highlighted in red
Route information
Defined by Streets and Highways Code § 425
Maintained by Caltrans and SANDAG
Length: 23.839 mi[1] (38.365 km)
Major junctions
South end: Otay Mesa Road in Otay Mesa
  <templatestyles src="Plainlist/styles.css"/>
North end: SR 52 in Santee
Location
Counties: San Diego
Highway system
← SR 124 SR 126 →

State Route 125 (SR 125) is a state highway in the US state of California. As a freeway, it runs from Otay Mesa Road (former SR 905) in Otay Mesa near the U.S.–Mexico border to SR 52 in Santee. SR 125 serves as an additional north–south route in the San Diego metropolitan area, also connecting SR 54, SR 94, and Interstate 8 (I-8). The definition of the route continues to SR 56, but this portion has not been constructed, and there are no plans to do so.

The first parts of SR 125 were added to the state highway system in 1933, connecting Route 94 with U.S. Route 80 (US 80). In the 1964 state highway renumbering, what was signed as Route 67 was transferred to the new SR 125. After several delays in funding and in planning, the highway was extended north to SR 52 and south to SR 54 in the early 2000s.

The southern portion of SR 125 from Otay Mesa Road to SR 54 near Chula Vista is a toll road called the South Bay Expressway; this portion was completed in 2007. The toll road was operated by a public-private partnership known as South Bay Expressway LLC. However, the partnership declared bankruptcy in 2010 and sold the road to the San Diego Association of Governments (SANDAG) in 2011. Since then, following a decrease in the toll amount, traffic using the highway has increased.

Route description

SR 125 begins as the South Bay Expressway toll road at an interchange with Otay Mesa Road,[2] the former alignment of SR 905. The route heads north, encountering its first toll plaza just before entering the city of Chula Vista. The freeway cuts through the Eastlake neighborhood of Chula Vista before leaving the city and passing through Sweetwater Regional Park near Sweetwater Reservoir. SR 125 intersects with SR 54, where the tolled portion ends, before turning north again through the unincorporated area of La Presa. The freeway briefly enters Lemon Grove before intersecting with SR 94 and entering La Mesa.[3]

SR 125 interchanges with Interstate 8 (I-8) before continuing north through the city of El Cajon and passing near Grossmont College. The freeway continues into Santee, where the route terminates at the SR 52 interchange. Traffic can continue onto SR 52 or onto Mission Gorge Road at the terminus.[3]

SR 125 is part of the California Freeway and Expressway System,[4] and south of I-8 is part of the National Highway System,[5] a network of highways that are essential to the country's economy, defense, and mobility.[6] The route is eligible for the State Scenic Highway System,[7] but it is only a scenic highway from SR 94 to I-8 as designated by Caltrans,[8] meaning that it is a substantial section of highway passing through a "memorable landscape" with no "visual intrusions", where the potential designation has gained popular favor with the community;[9] In 2013, SR 125 had an annual average daily traffic (AADT) of 29,000 at the northern terminus, and 161,000 between SR 94 and Lemon Avenue, the latter of which was the highest AADT for the highway.[10]

History

Route 67

Added to the state highway system in 1933,[11] and defined in 1935,[12] Route 198 extended from US 80 onto La Mesa Boulevard and Palm Avenue to SR 94 by 1938.[13] In 1947, the San Diego County Highway Development Association requested that the highway from Sixth Avenue in Mission Valley to US 80 be constructed as a freeway.[14] Although state senator Fred Kraft criticized the proposal in July 1953 because he believed that it would be too expensive and would not reduce congestion in the long-term, especially around the junction with US 80 in Grossmont,[15] approval for the Route 94 freeway extended to the junction with U.S. Route 80 (US 80) by October, with the Grossmont part of the route signed as Route 67.[16] The Route 67 freeway was completed in March 1957, from Campo Road and Route 94 to US 80; the project was completed for $1,625,000.[17][18]

Planning

Route 282 was defined as a route from Brown Field through La Mesa extending to Route 277 in 1959,[19] and in 1961 the latter terminus was changed to Route 278.[20] The California Highway Commission selected a route for the highway in mid-1963.[21] In the 1964 state highway renumbering, SR 125 was designated as the highway from SR 75 near Brown Field to SR 56. Route 198 was renumbered as State Route 67; the portion south of I-8 was renumbered as SR 125.[22]

At the beginning of that year, the La Mesa City Council expressed their preference for Route 282, which had been nicknamed the Ramona Freeway, to run on the routing of Fletcher Parkway, contrary to local businesses that wanted the highway to be routed 0.25 miles (0.40 km) west of the parkway.[23] A few months later, state engineer Jacob Dekema indicated that there were four routes under consideration for the portion from Brown Field to Sweetwater Lake, and the project would not be completed until well after 1972.[24] The state had selected a route for that part of the highway by June,[25] and for the routing west of Fletcher Parkway extending to Mission Gorge Road by July.[26] The next year, the California Highway Commission approved a routing north of Mission Gorge Road into Poway and ending at SR 56.[27]

In the 1970s, planning continued for the construction of the route, as well as modifications to the existing roadway. The City of La Mesa began discussions regarding adding SR 125 from SR 94 to I-8 into the scenic highway system in 1968;[28] the county Planning Commission continued pursuing these plans in 1970.[29] SR 125 was lengthened by the Legislature to extend to the border in 1972.[30]

In 1973, then-governor Ronald Reagan vetoed a bill to delete part of SR 125 from state plans, over concerns that not enough transportation studies had been done on the matter.[31][32] An improved interchange with SR 94 was being planned the next year.[33] Soon after, Caltrans raised concerns about the remainder of SR 125 not being constructed, due to objections from the community relating to freeway construction in general.[34] Construction began on the SR 94 interchange in October, and continued into late 1975, at a cost of $11 million (about $NaN in Error: undefined index "US-NGDPPC" when using {{Inflation/year}}. dollars).[[#cite_note-inflation.2Ffn-US-NGDPPC-35|[ 1]]] Parts of the interchange with SR 94 were open by July 20.[35] The City of Chula Vista considered SR 125 as possibly having scenic value when constructed, and considered asking the state to add it to the state highway system;[36] this influenced a rule that construction projects near possible scenic routes in the city had to take natural aesthetics into account.[37] The La Mesa City Council asked the state to modify the interchange with I-8 in July; the original interchange did not allow for access to SR 125 from I-8 east or to I-8 west from SR 125.[38]

In January of the following year, state Assemblyman Wadie Deddeh proposed legislation to remove the southern portion of SR 125 from the state highway plans again.[39] Soon afterward, the Comprehensive Planning Organization (CPO) moved to support retaining SR 125 from Poway to Santee in the county transportation plan, despite opposition from a county supervisor and the mayor of Escondido.[40] Deddeh's bill passed the state Assembly Transportation Committee a month later; in the meeting, Deddeh noted the construction of I-805 to handle the traffic demands of the region, as well as a lack of funding that would result in the construction being delayed for at least 20 years.[41] Despite a petition from the mayor of Escondido, the CPO again declined to remove SR 125 from the county transportation plan in March.[42]

The new interchange with SR 94 was completed in July 1976.[43] In August, the CHC announced that SR 75 south of SR 54 had been removed from the state highway plan.[44] The next year, the county supervisor, a San Diego City councilman, and the mayors of La Mesa and National City wrote a letter to then-Governor Jerry Brown to ask for the construction of this portion of SR 125 and other freeways, due to concerns about the types of congestion seen in Los Angeles coming to San Diego due to the incomplete freeway system.[45] San Diego City Councilman Tom Gade wrote a telegram to the Caltrans Director Adriana Gianturco about the possible deletions; in response, Gianturco clarified that the plans were only being reconsidered and had not been removed, and a CHC member criticized the tone of the original telegram, calling it "intemperate".[46] However, the city of Chula Vista was opposed to the construction at the time, which was a factor in the removal of SR 125 from the highway plans.[47]

In March 1980, the CPO approved the funding for the redesign of the interchange with I-8.[48] By early 1980, SR 125 was denoted with signs saying "To 94" at Grossmont Summit; plans were to provide access north to Fletcher Parkway in the revamp of the interchange.[49] On December 30, 1980, the City of Poway included SR 56 in the city plan extending east through the city to a northern extension of SR 125.[50]

By 1981, the environmental impact report had been completed on the proposed changes to the I-8 intersection, and the $50 million (about $NaN in Error: undefined index "US-NGDPPC" when using {{Inflation/year}}. dollars)[[#cite_note-inflation.2Ffn-US-NGDPPC-35|[ 1]]] project to add ramps and widen I-8 was awaiting clearance from the Federal Highway Administration.[51] That year, Poway removed SR 125 from their city plan, leading to a lawsuit from the City of San Diego.[52] In 1983, both the cities of San Diego and Poway supported the extension of SR 56 to SR 67, although the City of Poway wanted the route moved and had reservations about the freeway ending in the city.[53] The next year, the San Diego Association of Governments (SANDAG) suggested routing SR 125 through the city of Poway, rather than terminating the route in the southern part of the city like that city wanted.[54] Jacob Dekema was asked to advise the city of Poway in the dispute following his departure from the Caltrans district director position.[55]

Construction

In 1986, the project revamping the I-8 interchange was under way, at a cost of $80 million (about $NaN in Error: undefined index "US-NGDPPC" when using {{Inflation/year}}. dollars);[[#cite_note-inflation.2Ffn-US-NGDPPC-35|[ 1]]] it would allow for SR 125 to be extended north past I-8 to Fletcher Parkway.[56] That year, SR 125 was truncated to begin at SR 905 by the Legislature, as the latter was formed as a route from I-5 to the border.[57]

Environmental impact studies began on the part of SR 125 south of SR 54 in 1987.[58] The next year, work was under way to add lanes to SR 125 from south of Lemon Avenue to the northern terminus, at a cost of $17.2 million.[59] In 1989, some Bonita residents raised objections about the proposed extension south of La Mesa, as they were concerned about additional congestion and urbanization from the freeway going through Bonita.[60]

The next year, Caltrans proposed building the southern portion as a toll road, operated by private firms; California Transportation Ventures and PrivaCAL both applied for the role.[61] In September, the California Transportation Commission decided to reallocate the funding for the part of SR 125 from SR 94 to SR 54; they shifted it towards finishing the 40th Street portion of I-15.[62]

The northernmost portion of the current SR 125 was built in stages. After weather-related construction delays due to the El Niño season of the winter of 1997–1998, as well as a contractor declaring bankruptcy, the extension of SR 52 between Mission Gorge Road and SR 125 was dedicated on May 9, 1998, as well as SR 125 from Mission Gorge Road to Grossmont College Drive.[63] The portion from Fletcher Parkway to ramps located at Amaya Drive was finished at the beginning of 2001, with the segment north to Navajo Road to open later that year, and the part from there to Grossmont College Drive was to begin construction in early 2001.[64] The entire freeway from SR 52 to I-8 was completed by 2004.[65]

SR 125 near Santee, CA

The first phase of the construction of the eastern portion of the SR 54 freeway corresponded with construction of SR 125 north of Jamacha Boulevard to SR 94; construction began in 1996 and was completed in 2003.[66][67]

The second phase consisted of the construction of the SR 125 toll road and opened on November 19, 2007. While California Transportation Ventures owned the franchise on the tolled portion of SR 125, the interchange with SR 54 was constructed with $160 million of public funding.[68] From 2005 to 2007, 1.5 million cubic meters of rock were blasted through in 160 separate explosions to allow for the interchange to be built.[69] The South Bay Expressway extended SR 125 southward from SR 54 to Otay Mesa. Construction of this portion was opposed by community and environmental groups.[70] This toll road was one of four privately financed toll highway projects, including the 91 Express Toll Lanes, that were approved in 1990;[71] it was also one of two toll roads financed and controlled by both public and private sources, although the 91 Express Lanes, the other road, soon became entirely publicly owned. A partnership known as the South Bay Expressway operated the road, while an Australian company, Maquarie Group Ltd., handled financial and construction matters.[72]

Bankruptcy

In 2008, 30,000 vehicles a day traveled on the expressway, which fulfilled state expectations;[73] however, the toll machines resulted in complaints due to the low height and needing exact change.[74] In late 2009, the resulting South Bay Expressway partnership that operated the road questioned the value of the toll road for property tax purposes, saying that it was worth $330 million less than it was originally valued due to the low volumes of traffic using the road.[75] On March 22, 2010, the toll road's operator filed for Chapter 11 bankruptcy protection, citing traffic counts running at less than 40 percent of initial estimates due to the economic downturn. Some drivers chose not to use the toll road due to a recent increase in tolls.[76] An editorial in the San Diego Union-Tribune also blamed the delay in opening the toll road and the associated penalties, interest, and legal fees for the company's financial status.[77] According to the bankruptcy filing, the expressway had $510 million of loans outstanding, of which $170 million was owed to the U.S. Department of Transportation. In addition, there was over $600 million of unresolved litigation with the construction contractors. The EBITDA for the fiscal year ending June 30, 2009 was approximately $3 million on revenues of $21 million.[78]

Discussions regarding a potential SANDAG purchase of the road began in October 2010.[79] On July 29, 2011, SANDAG agreed to purchase the lease of the freeway from South Bay Expressway LLC;[80] even though a study suggested that the agency might have to spend millions of dollars to maintain and repair parts of the highway.[81] Objections raised to the purchase during the negotiation phase included a loan from the federal government of $1.5 million to complete the purchase, and a possible increase in traffic through Lemon Grove.[82] The sale of the franchise rights until the year 2042 was finalized on December 16, 2011, at a price of $341.4 million, and $10.2 million in additional fees, with $254 million from TransNet sales tax revenue, some of it to be repaid with toll revenue. SANDAG claimed at the time that they would reduce the tolls to attract increased use and decrease traffic on I-805, which would mean that additional lanes would not need to be constructed on that route.[83] The San Diego Union-Tribune criticized the decision of the operator to increase tolls rather than decreasing them despite the low demand for using the road;[84] in mid-2011, it cost $4 to drive the entire toll portion of the road.[80]

Due to toll reductions in 2012 that were 25 to 40 percent less than their privately owned amounts, the number of vehicles using the toll portion of the expressway increased by 19 percent that year, as compared to the previous year.[85] It was estimated that the road would be fully paid off in 2014, and there were reports of decreased traffic on Chula Vista streets and an increase in retail business.[86]

Tolls

Toll plazas are located along the South Bay Expressway at all northbound onramps and southbound offramps; there is also a mainline Otay Mesa Toll Plaza at the southern end of the facility just north of Otay Mesa Road.[3]

The toll road is equipped with the FasTrak electronic toll collection system, with drivers being charged a prorated toll based on the distance traveled (similar to the ticket systems employed by the Pennsylvania Turnpike and several other toll roads located on the East Coast of the United States). Those paying by cash or credit card are instead charged a more expensive flat rate depending on which toll booth they pass through, using a barrier toll system. For example, any cash- or credit-paying driver that passes through the Otay Mesa Toll Plaza ends up paying $3.50 regardless of the distance they actually traveled.[87][88]

The following table lists the toll rates for passenger cars, both with and without FasTrak (as of June 12, 2012). The toll rate is doubled for vehicles with more than two axles.[87]

Southern end of trip Northern end of trip Fastrak Cash/Credit
Otay Mesa Road SR 54 $2.75 $3.50
East H Street $2.00 $3.50
Birch Road, Olympic Parkway, or Otay Lakes Road $1.95 $3.50
Between Birch Road and East H Street $0.50 $2.50
Birch Road, Olympic Parkway, Otay Lakes Road, or East H Street SR 54 $1.70 $2.50
San Miguel Ranch Road $1.55 $2.00

Future

The proposal to extend SR 125 north into Poway was discussed as late as 2003 by a local advisory group working with the San Diego Association of Governments.[89] However, none of these proposals to extend SR 125 have been included in SANDAG's 2050 Regional Transportation Plan.[90]

Previously, SR 125 had a direct connection with SR 905 via two at-grade intersections on Otay Mesa Road.[3] With the completion of the freeway segment of SR 905 and the freeway-to-freeway connection to SR 125 unconstructed, traffic on SR 125 must head west on Otay Mesa Road and south on La Media Road to make the connection.[2] A freeway-to-freeway interchange is planned for the connection between SR 125 and SR 905;[91] there are also plans to connect to the new SR 11 freeway once it is constructed. SR 11 is planned to be a toll facility that will serve a new border crossing east of Otay Mesa.[92]

Exit list

Except where prefixed with a letter, postmiles were measured on the road as it was in 1964, based on the alignment that existed at the time, and do not necessarily reflect current mileage. R reflects a realignment in the route since then, M indicates a second realignment, L refers an overlap due to a correction or change, and T indicates postmiles classified as temporary (for a full list of prefixes, see the list of postmile definitions).[1] Segments that remain unconstructed or have been relinquished to local control may be omitted. The entire route is in San Diego County.

Location Postmile
[1][10][93]		 Exit
[94]		 Destinations Notes
Otay Mesa   SR 905 / SR 11 east Interchange under construction; future southbound exit and northbound entrance; future south end of SR 125; future I-905
​ L0.50 1 To SR 905 / Otay Mesa Road Southbound exit and northbound entrance; current south end of SR 125
San Diego   Otay Mesa Toll Plaza
Chula Vista 2.29 5 Birch Road
3.06 6 Olympic Parkway
4.04 7 Otay Lakes Road
5.08 8 East H Street
6.93 9 San Miguel Ranch Road, Mt. Miguel Road Southbound exit and northbound entrance
​   North end of toll road
​ 9.59 11 SR 54 west (South Bay Freeway)
​ 9.90 12 Jamacha Boulevard, Paradise Valley Road (CR S17)
​ 10.62 13 Jamacha Road
Lemon Grove 12.97 15 SR 94 (Martin Luther King Jr. Freeway) Southbound exit to SR 94 east is via exit 17A; SR 94 exits 9A-B
​ 13.50 17A Spring Street – La Mesa Northbound exit is via exit 15
La Mesa 14.74 17A Lemon Avenue Northbound exit and southbound entrance
R15.09 17B Grossmont Boulevard
R15.41 18A I-8 I-8 west exit 14A, east exit 14B.
18.66 18B Fletcher Parkway
El Cajon 19.53 20A Navajo Road
20.39 20B Grossmont College Drive
Santee 22.17 21 SR 52 – San Diego, Santee Northbound exit and southbound entrance; north end of SR 125
22.30 Mission Gorge Road At-grade intersection
1.000 mi = 1.609 km; 1.000 km = 0.621 mi

See also

References

  1. ↑ 1.0 1.1 1.2 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ 3.0 3.1 3.2 3.3 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  5. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.0 10.1 Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  13. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  14. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  15. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  16. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  20. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  21. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  22. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  23. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  24. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  25. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  26. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  27. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  28. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  29. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  30. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  31. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  32. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  33. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  34. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  35. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  36. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  37. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  38. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  39. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  40. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  41. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  42. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  43. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  44. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  45. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  46. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  47. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  48. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  49. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  50. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  51. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  52. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  53. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  54. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  55. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  56. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  57. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  58. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  59. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  60. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  61. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  62. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  63. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  64. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  65. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  66. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  67. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  68. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  69. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  70. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  71. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  72. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  73. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  74. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  75. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  76. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  77. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  78. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  79. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  80. ↑ 80.0 80.1 Lua error in package.lua at line 80: module 'strict' not found.
  81. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  82. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  83. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  84. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  85. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  86. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  87. ↑ 87.0 87.1 Lua error in package.lua at line 80: module 'strict' not found.
  88. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  89. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  90. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  91. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  92. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  93. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  94. ↑ Lua error in package.lua at line 80: module 'strict' not found.
    Lua error in package.lua at line 80: module 'strict' not found.

External links

Script error: No such module "Attached KML".


Cite error: <ref> tags exist for a group named "", but no corresponding <references group=""/> tag was found, or a closing </ref> is missing

Retrieved from "https://infogalactic.com/w/index.php?title=California_State_Route_125&oldid=2063906"