Recent Posts

Pages: 1 [2] 3 4 ... 10
11
(For US 6/US 19)  PennDOT - District 1 News: Route 6 Reconstruction Project Moving into Final Phase

Quote
Work on the Route 6 Reconstruction Project is working into the final phase as traffic transitions to the new lanes later this month.

Traffic is expected to start using the reconstructed lanes of Route 6 on July 21, 2025, weather permitting. Drivers are reminded that the roadway will be one lane in each direction.

In Phase 3 of the project work will include updates to the intersection with Bessmer Street and Reynolds Avenue. Additional drainage updates will be made and the existing pavement from the southern side of the road and the temporary crossover will be removed. Construction of the multi-purpose travel in the area formerly used by westbound lanes will also be complete along with landscaping.

The temporary signal near Service Road and Meadville Forging Company in West Mead Township will remain in place but will only be used as needed to complete work.

Drivers should be alert for traffic pattern changes, lane restrictions controlled by flaggers and other short-term detours on Stan Road and Reynolds Avenue.

The project started in August 2024 and is on schedule for completion in fall 2025.

The contractor is Glenn O. Hawbaker, Inc. of State College, PA. The contract cost is $16,616,006, which is to be paid with a combination of federal and state funds.

Additional information on the Route 6 Reconstruction Project is available online under the Projects Near You portion of the PennDOT website.

This year PennDOT’s Northwest Region expects to do work on more than 100 projects. To see a full listing of all the anticipated work, check out the 2025 Construction Book available online at www.penndot.pa.gov/District1.

PennDOT urges motorists to slow down when driving in work zones, and also to be alert to changing conditions, avoid distractions and to pay attention to signs and flaggers. Drive responsibly in work zones for your safety and the safety of the workers.

Motorists can check conditions on major roadways by visiting www.511PA.com. 511PA, which is free and available 24 hours a day, provides traffic delay warnings, weather forecasts, traffic speed information and access to more than 1,000 traffic cameras.

511PA is also available through a smartphone application for iPhone and Android devices, by calling 5-1-1, or by following regional X alerts accessible on the 511PA website.

Subscribe to PennDOT news and traffic alerts in Crawford, Erie, Forest, Mercer, Venango, and Warren counties at www.penndot.pa.gov/District1.

Find PennDOT news for the northwest region on X or Facebook.

# # #

MEDIA CONTACT: Jill Harry, jharry@pa.gov or 814-678-5035
12
Updates to Highway Data / Re: NY: I-190/NY-266
« Last post by rickmastfan67 on Yesterday at 03:14:52 am »
Since yarka sorta gave a green light to doing this on Github, I decided to at least quickly knock this out so the error on the error log can finally disappear after 2+ years.

https://github.com/TravelMapping/HighwayData/pull/8492
13
Updates to Highway Data / NC: NC-74 'northern' end
« Last post by rickmastfan67 on Yesterday at 02:48:01 am »
Currently, NC-74 & US-52 share 'Separate' carriageways for a short distance thru the NC-65 interchange north of the major Winston-Salem Loop interchange.  Since I-74 will be taking over NC-74 & overlay US-52 in this area, we need to properly fix this before label issues become a major hassle when US-52's exit numbers convert to I-74 mileage 'soon'.

Changes to NC-74 that are needed as follows:
1) Extend the route north to north of the NC-65 interchange to the current start of the split carriageways.  This is currently where US-52 got new 'separate' Exit 119 signage, signifying it's being completely separate from Exit 117, & justifies NC-74 (I-74) carriageways are a completely separate entity from US-52's.  This should IMO, become the 'new' 41 point, since the PR from the US-52 renumber says it will become this.
    N.C. 74 (Winston-Salem Northern Beltway): Old Exit 119 → New Exit 41​
2) Add a shaping point here to break a false multiplex with US-52 since we need a graph connection with NC-65 in #3.
3) Add in a point for the NC-65 interchange here.  While, all the main ramps for it, only connect to the US-52 carriageways, there is a single solo ramp that directly connects to NC-74, justifying a graph connection with both NC-65 & US-52 here, as the center point for it all should be the same. As for the label in NC-74's file for this interchange, we could do either 118(52) or 41B, up to you.
4) Add a shaping point here to break a false multiplex with US-52 since we need a graph connection with NC-65 in #3.
5) 'current' 41 -> 41A

Changes to US-52 as follows:
1) Add Exit 119 for where the split with NC-74 happens.  No other changes will be needed, as all the multiplex breakage points will be in NC-74's file.

Changes to NC-65 as follows:
No changes needed till I-74 comes along in this area IMO.

Changes to NC I-74FutPil:
I would recommend shortening the route to the 'new' US-52 Exit 119 point, keeping the southern ending label 'as-is' & hiding the 'NC65' label under it.  Since the 'Future Interstate' files are on their death beds, this is the best option IMO till I-74 finally takes over this area and kills this file.
14
Updates to Highway Data / Re: CA: US-101 southern end issue?
« Last post by rickmastfan67 on Yesterday at 02:18:02 am »
Well, we have a similar issue to this over in NY, where both two routes are on separate carriageways: I-90 & US-219
Another example would be I-40 & I-240's western junction in TN.

This is one of the reasons I brought this up.
15
Seems like they jumped the gun on this PR, as none of the changes had happened yet as of May '25 GSV imagery.

Exit 123 still as-is as an example.
16
Updates to Highway Data / Re: PRT A19 wrong exit numbers
« Last post by rickmastfan67 on Yesterday at 02:01:30 am »
Especially if those users don't seem particularly concerned (or simply don't check the updates entries religiously)?

This is why I suggested that there should be an update log entry for these changes.  The entire route got renumbered.  That's a news worthy change.
17
Updates to Highway Data / Re: MN: MN263 unsigned/decommissioned
« Last post by froggie on Yesterday at 12:00:57 am »
Was already looking at MnDOT's mapping app earlier this evening.  267 is still there, which tells me that MnDOT and Murray County have not come to agreement yet.

263 is gone, so removing that will be on my to-do list.
18
Updates to Highway Data / IL: IL 157 point request
« Last post by aterrypenak on July 14, 2025, 07:06:21 pm »
Could I get a point on IL 157 at East University Drive/Governors Parkway in Edwardsville (38.79530, -89.97819)? It's the eastern entrance to SIU Edwardsville, and Governors Parkway is a decent-sized crossroad in its own right.
19
Updates to Highway Data / Re: SD: US 14/83 Relocation (Pierre)
« Last post by TBKS1 on July 14, 2025, 05:03:10 pm »
A little update, I got a response back from SDDOT saying the route is not signed. Obviously this may be subject to change, someone may accidentally discover it signed later, who knows.
20
Updates to Highway Data / NY: NY 128 Point Request
« Last post by webny99 on July 14, 2025, 01:07:02 pm »
I would like to recommend a point somewhere along the length of NY 128  (this is personal, as I mentioned in the new travels/stats thread :D)

At 5.48 miles it's reasonable to have one or more waypoints, but it is admittedly lacking possibilities. I would suggest Lei Far Dr as it could be added by moving an existing shaping point.

Map Ave, Sch St, or Wri Cor Rd could also be options.


Pages: 1 [2] 3 4 ... 10