ME: I-395/Route 9 connector

[yakra]

https://www.maine.gov/mdot/projects/I395rt9connector/
https://www.arcgis.com/apps/Cascade/index.html?appid=564602686db24531838b62583a4c6296

HOLDEN, Maine — It's been years in the planning and now the construction for the I-395/Route 9 Connector project is scheduled to begin in September.

The Maine Department of Transportation (MaineDOT) project is expected to last three to four years and will cost an estimated $104 million.

That'd put anticipated completion in the Sept 2024 - Sept 2025 timeframe.

• The project will also create a "T" intersection with the current Route 9.
• The new Connector will be designated Route 9. The section of Route 9 from this intersection to Brewer will be designated Route 9 Business.

[vdeane]

Bumping this to note that it's looking pretty close, at least the end from I-395, and the signage for the new ME 9 and ME 9 Business routing are up.  Interesting style sign for the business route.

[vdeane]

Looks like it's opening next week, which explains why all the signage is up.  It appears that ME 9 will follow US 202 to I-395, so ME 9 Business will be from the end of the US 202 overlap to where the new connector will end.  I've seen the signage on US 1A referencing this.

https://www.foxbangor.com/news/local/mainedot-officials-announce-when-the-i-395-route-9-connector-will-open/article_869f9c50-57ca-45c2-b66b-bdc5ce721614.html#//

[vdeane]

The ME 9 connector opened yesterday: https://www.bangordailynews.com/2025/06/27/bangor/bangor-government/i-395-connector-route-9-opens/

I should have the first batch of photos (uploaded to the Northeast Roads Facebook group) showing the new routes of ME 9 and ME 9 Business on my website tomorrow.  Future batches to follow in subsequent updates.

EDIT: First batch up on the I-395 and US 1A (Bangor) pages.

https://nysroads.com/photos.php?route=i395&state=ME
https://nysroads.com/photos.php?route=us1ab&state=ME

[vdeane]

I've finished uploading photos to my site.  In addition to the above, I also have a couple relevant photos on the US 202 page.

Of particular interest:
https://nysroads.com/photos.php?route=us202&state=ME&file=102_9648.JPG
https://nysroads.com/photos.php?route=us202&state=ME&file=102_9651.JPG
https://nysroads.com/photos.php?route=us1ab&state=ME&file=102_9528.JPG
https://nysroads.com/photos.php?route=us1ab&state=ME&file=102_9531.JPG
https://nysroads.com/photos.php?route=i395&state=ME&file=102_9382.JPG
https://nysroads.com/photos.php?route=i395&state=ME&file=102_9653.JPG

[yakra]

https://github.com/TravelMapping/HighwayData/pull/8501

[yakra]

Travelers on the relocated portion of ME9:

1995hoo 7_8 Cw9 SK220 Stevashe alex bejacob chaddean charliezeb cinx cl94 deathtopumpkins dharwood drebbin37 duke87 epzik8 flroads froggie fwydriver405 highprioritycorridors htm_duke jayhawkco jonsamuels jpinyan kevinmc lkefct mapcat mapmikey neilbert nezinscot ngrier ntallyn okroads oscar pderocco pnrrth terescoj terminal_moraine thehighwayman3561 trobster vdeane vespertine wadsteckel

If you'd .listed all of what's now ME9BusBan in one entry, your maps/stats will now show the bypass instead, and you may want to change your .list entry.

If one or both of your waypoints were inside the relocated section, either:

• your travels will still be shown correctly, or
  
• you'll have a "waypoint label not found" error and need to re-enter that .list line.
• Probably. I don't think anyone's travels will be shown incorrectly (as opposed to just not shown), but you'll probably want to check & be sure.

[Jim]

Thanks for this heads up.  I think my travels are still correct.  I had the "old" route marked as US1AltBan anyway so it is still marked even though I don't have an entry for ME9AltBan.  And my US202 entry there is now obsolete because that part's gone.  And my old ME9 entry is broken but not needed anyway since I haven't been on any of the "new" ME9.  I think I just delete the two offending entries to clean up my log and I'm good...

[vdeane]

I actually preemptively split my travel entry for ME 9 to prepare, though I still had a broken line because it didn't recognize the old section as actually being ME9Bus.

[bejacob]

Updated my file to reflect driving the new section of ME9 plus all of ME9BusBan on July 12. After the latest site update, everything in the area is correct

[yakra]

Dropping this here for future reference...

Code: [Select]

Route* ME9 = Route::pri_list_hash.at("ME ME9");
unsigned int i1 = ME9->pri_label_hash.at("US202_HAM");
unsigned int i2 = ME9->pri_label_hash.at("ME46");
cout << i1 << ' ' << i2 << endl;
TMBitset<TravelerList*, uint32_t> travelers(TravelerList::allusers.data, TravelerList::allusers.size);
for (unsigned int i=i1; i<i2; ++i)
travelers.fast_union(ME9->segments[i].clinched_by);
cout << "Travelers on ME ME9 US202_Ham ME46:";
for (TravelerList* t : travelers)
cout << ' ' << t->traveler_name << flush;
cout << endl;
return 0;
...because relocation.sh is unreadable & unmaintainable and has too many problems.