World Library  
Flag as Inappropriate
Email this Article

North Central Freeway (Washington, D.C.)

Article Id: WHEBN0009390503
Reproduction Date:

Title: North Central Freeway (Washington, D.C.)  
Author: World Heritage Encyclopedia
Language: English
Subject: Interstate 70, Interstate 95, Interstate 95 in Maryland
Collection:
Publisher: World Heritage Encyclopedia
Publication
Date:
 

North Central Freeway (Washington, D.C.)

North Central Freeway
Highway system
}|}}|}}}|yes|1|0}}|0}}+

}|{{#ifeq:{{Infobox road/hide/regions The North Central Freeway was a planned freeway in the District of Columbia that would have run from the Inner Loop in D.C. to the Capital Beltway (I-495) at Silver Spring.

The entire route was canceled in 1977 amid vitriolic protest from D.C. residents, angered at earlier proposed alignments for the route through the northern suburbs. The cancellation of the route led to the truncation of Interstate 95 at the College Park Interchange and its subsequent rerouting onto the eastern half of the Capital Beltway, and the truncation of Interstate 70S (now I-270) at its current terminus at Bethesda.

Contents

  • Route description 1
  • History 2
    • 1959 North Central Freeway 2.1
    • 1962 North Central Freeway 2.2
    • 1963-64 North Central Freeway Study 2.3
    • 1966 Supplementary Study 2.4
    • 1968 Major Transportation Plan 2.5
    • 1971 De Leuw-Weese Study 2.6
  • See also 3
  • References 4
  • External links 5

Route description

In the final plans published in the 1971 D.C. Interstate System program, the North Central Freeway, ten lanes wide, would have begun at the Union Station interchange (where the East Leg Freeway (I-295), North Leg Freeway (I-66/I-95) and New York Avenue (US 50) would meet) and run north, paralleling the B&O railroad corridor as far as the Brookland area, where it would have entered a 3/4-mile tunnel south of Rhode Island Ave., emerging to the north of Michigan Avenue. Running north it would have continued along the railroad corridor to Fort Totten, Washington, D.C., where it would have junctioned the eight-lane Northeast Freeway. I-95 would have joined the North Central Freeway from the North Leg Freeway and followed it to Fort Totten, where it would have turned east onto the Northeast Freeway and exited the District, eventually junctioning I-495 at the College Park Interchange.

The remainder of the North Central Freeway, now part of I-70S and six lanes wide, would have continued along the B&O railroad corridor, passing beneath Takoma Park, Washington, D.C. in a 1/2-mile tunnel, and terminated at a large wye junction with I-495. I-70S would have begun at the southern terminus of the Northeast Expressway and followed the North Central Freeway all the way to I-495, with I-70S following the western leg of the wye and a short section of the Beltway to its existing wye junction in Bethesda.

History

1959 North Central Freeway

In 1959, the Mass Transportation Plan outlined a North Central Freeway routing that would parallel Georgia Avenue through northern D.C. However, no detailed studies into the feasibility or impact of this route were undertaken at the time. A later study conducted in 1964 included diagrams of the 1959 route, but with the roadway in a 4-2-4 configuration instead of a 3-3 configuration. [1]

1962 North Central Freeway

In November 1962, the Kennedy administration released a document "Recommendations for Transportation in the National Capital Region; A Report to the President for transmittal to Congress by the National Capital Transportation Agency".

It replaced the 1959 concept of 3 separate northern radial mixed traffic highways with that of a 2 into 1 "Y" route for a North Central Freeway as inside-the-Beltway I-70S, joined by an I-95 North East Freeway near Fort Totten, and continue together as the I-95 North Central Freeway.

The I-70S and I-95 portions of the North Central would be routed along the existing B&O Metropolitan Branch RR (today's WMATA Red Line). Accordingly, this avoids "the substantial relocation of persons, loss of taxable property and disruption of neighborhoods that would result from construction of the Northeast, North Central and Northwest Freeways proposed in the 1959 plan. Further savings are realized by placing the rapid transit lines to Silver Spring and Queen's Chapel in this same railroad corridor."

This B&O "Y" route concept North Central Freeway was later politically undermined by planning that failed to follow it. [2]

1963-64 North Central Freeway Study

In a series of proposals published in 1963 and 1964, the subsequent study of the North Central Freeway and Northeast Freeway indirectly ignored earlier suggestions regarding the use of the B&O railroad corridor; instead, no fewer than 17 separate alignments were proposed for the NCF south of the Northeast Freeway, and a staggering 35 were proposed for the NCF (I-70S) north of it, many of which did not make much use of the railroad alignment.

One important aspect of the study was the consideration of consolidating the North Central Freeway (I-70S) and Northeast Freeway (I-95) into a single freeway that would run south to the

  • : Washington D.C. Interstates and FreewaysRoads to the Future
  • : 1965 Elevated Multi-LevelA Trip Within the Beltway
  • : 1971 plansA Trip Within the Beltway

External links

  1. ^ Willinger, Douglas. 1959 North Central FreewayA Trip Within the Beltway: URL accessed 13:57, 13 February 2007.
  2. ^ Willinger, Douglas. 1962 North Central FreewayA Trip Within the Beltway:
  3. ^ a b c Willinger, Douglas. 1963-64 North Central Freeway StudyA Trip Within the Beltway: URL accessed 13:33, 13 February 2007.
  4. ^ a b c d Willinger, Douglas. : 1966 North Central Freeway Supplemental StudyA Trip Within the Beltway URL accessed 15:15, 8 February 2007.
  5. ^ a b Willinger, Douglas. : And so does the US National Capital Planning CommissionA Trip Within the Beltway URL accessed 14:45, 8 February 2007.
  6. ^ Willinger, Douglas. : 1971 DeLuewA Trip Within the Beltway URL accessed 14:56, 8 February 2007.
return p

end

', table.concat(classes, ' '), s )
%s
function p._hatnote(s, options) checkType('_hatnote', 1, s, 'string') checkType('_hatnote', 2, options, 'table', true) local classes = {'hatnote'} local extraclasses = options.extraclasses local selfref = options.selfref if type(extraclasses) == 'string' then classes[#classes + 1] = extraclasses end if selfref then classes[#classes + 1] = 'selfref' end return string.format( '

function p.hatnote(frame) local args = getArgs(frame) local s = args[1] local options = {} if not s then return p.makeWikitextError( 'no text specified', 'Template:Hatnote#Errors', args.category ) end options.extraclasses = args.extraclasses options.selfref = args.selfref return p._hatnote(s, options) end


-- Hatnote -- -- Produces standard hatnote text. Implements the template.


function p._formatLink(link, display) -- Find whether we need to use the colon trick or not. We need to use the -- colon trick for categories and files, as otherwise category links -- categorise the page and file links display the file. checkType('_formatLink', 1, link, 'string') checkType('_formatLink', 2, display, 'string', true) link = removeInitialColon(link) local namespace = p.findNamespaceId(link, false) local colon if namespace == 6 or namespace == 14 then colon = ':' else colon = end -- Find whether a faux display value has been added with the | magic -- word. if not display then local prePipe, postPipe = link:match('^(.-)|(.*)$') link = prePipe or link display = postPipe end -- Find the display value. if not display then local page, section = link:match('^(.-)#(.*)$') if page then display = page .. ' § ' .. section end end -- Assemble the link. if display then return string.format('%s', colon, link, display) else return string.format('%s%s', colon, link) end end

function p.formatLink(frame) local args = getArgs(frame) local link = args[1] local display = args[2] if not link then return p.makeWikitextError( 'no link specified', 'Template:Format hatnote link#Errors', args.category ) end return p._formatLink(link, display) end


-- Format link -- -- Makes a wikilink from the given link and display values. Links are escaped -- with colons if necessary, and links to sections are detected and displayed -- with " § " as a separator rather than the standard MediaWiki "#". Used in -- the template.


function p.makeWikitextError(msg, helpLink, addTrackingCategory) -- Formats an error message to be returned to wikitext. If -- addTrackingCategory is not false after being returned from -- Module:Yesno, and if we are not on a talk page, a tracking category -- is added. checkType('makeWikitextError', 1, msg, 'string') checkType('makeWikitextError', 2, helpLink, 'string', true) yesno = require('Module:Yesno') local title = mw.title.getCurrentTitle() -- Make the help link text. local helpText if helpLink then helpText = ' (help)' else helpText = end -- Make the category text. local category if not title.isTalkPage and yesno(addTrackingCategory) ~= false then category = 'Hatnote templates with errors' category = string.format( '%s:%s', mw.site.namespaces[14].name, category ) else category = end return string.format( '%s', msg, helpText, category ) end

function p.formatPageTables(...) -- Takes a list of page/display tables and returns it as a list of -- formatted links. Nil values are not allowed. local pages = {...} local links = {} for i, t in ipairs(pages) do checkType('formatPageTables', i, t, 'table') local link = t[1] local display = t[2] links[i] = p._formatLink(link, display) end return links end

function p.formatPages(...) -- Formats a list of pages using formatLink and returns it as an array. Nil -- values are not allowed. local pages = {...} local ret = {} for i, page in ipairs(pages) do ret[i] = p._formatLink(page) end return ret end

function p.findNamespaceId(link, removeColon) -- Finds the namespace id (namespace number) of a link or a pagename. This -- function will not work if the link is enclosed in double brackets. Colons -- are trimmed from the start of the link by default. To skip colon -- trimming, set the removeColon parameter to true. checkType('findNamespaceId', 1, link, 'string') checkType('findNamespaceId', 2, removeColon, 'boolean', true) if removeColon ~= false then link = removeInitialColon(link) end local namespace = link:match('^(.-):') if namespace then local nsTable = mw.site.namespaces[namespace] if nsTable then return nsTable.id end end return 0 end

local function removeInitialColon(s) -- Removes the initial colon from a string, if present. return s:match('^:?(.*)') end

local function getArgs(frame) -- Fetches the arguments from the parent frame. Whitespace is trimmed and -- blanks are removed. mArguments = require('Module:Arguments') return mArguments.getArgs(frame, {parentOnly = true}) end


-- Helper functions


local p = {}

local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local mArguments -- lazily initialise Module:Arguments local yesno -- lazily initialise Module:Yesno


return p-------------------------------------------------------------------------------- -- Module:Hatnote -- -- -- -- This module produces hatnote links and links to related articles. It -- -- implements the and meta-templates and includes -- -- helper functions for other Lua hatnote modules. --

end

', table.concat(classes, ' '), s )
%s
function p._hatnote(s, options) checkType('_hatnote', 1, s, 'string') checkType('_hatnote', 2, options, 'table', true) local classes = {'hatnote'} local extraclasses = options.extraclasses local selfref = options.selfref if type(extraclasses) == 'string' then classes[#classes + 1] = extraclasses end if selfref then classes[#classes + 1] = 'selfref' end return string.format( '

function p.hatnote(frame) local args = getArgs(frame) local s = args[1] local options = {} if not s then return p.makeWikitextError( 'no text specified', 'Template:Hatnote#Errors', args.category ) end options.extraclasses = args.extraclasses options.selfref = args.selfref return p._hatnote(s, options) end


-- Hatnote -- -- Produces standard hatnote text. Implements the template.


function p._formatLink(link, display) -- Find whether we need to use the colon trick or not. We need to use the -- colon trick for categories and files, as otherwise category links -- categorise the page and file links display the file. checkType('_formatLink', 1, link, 'string') checkType('_formatLink', 2, display, 'string', true) link = removeInitialColon(link) local namespace = p.findNamespaceId(link, false) local colon if namespace == 6 or namespace == 14 then colon = ':' else colon = end -- Find whether a faux display value has been added with the | magic -- word. if not display then local prePipe, postPipe = link:match('^(.-)|(.*)$') link = prePipe or link display = postPipe end -- Find the display value. if not display then local page, section = link:match('^(.-)#(.*)$') if page then display = page .. ' § ' .. section end end -- Assemble the link. if display then return string.format('%s', colon, link, display) else return string.format('%s%s', colon, link) end end

function p.formatLink(frame) local args = getArgs(frame) local link = args[1] local display = args[2] if not link then return p.makeWikitextError( 'no link specified', 'Template:Format hatnote link#Errors', args.category ) end return p._formatLink(link, display) end


-- Format link -- -- Makes a wikilink from the given link and display values. Links are escaped -- with colons if necessary, and links to sections are detected and displayed -- with " § " as a separator rather than the standard MediaWiki "#". Used in -- the template.


function p.makeWikitextError(msg, helpLink, addTrackingCategory) -- Formats an error message to be returned to wikitext. If -- addTrackingCategory is not false after being returned from -- Module:Yesno, and if we are not on a talk page, a tracking category -- is added. checkType('makeWikitextError', 1, msg, 'string') checkType('makeWikitextError', 2, helpLink, 'string', true) yesno = require('Module:Yesno') local title = mw.title.getCurrentTitle() -- Make the help link text. local helpText if helpLink then helpText = ' (help)' else helpText = end -- Make the category text. local category if not title.isTalkPage and yesno(addTrackingCategory) ~= false then category = 'Hatnote templates with errors' category = string.format( '%s:%s', mw.site.namespaces[14].name, category ) else category = end return string.format( '%s', msg, helpText, category ) end

function p.formatPageTables(...) -- Takes a list of page/display tables and returns it as a list of -- formatted links. Nil values are not allowed. local pages = {...} local links = {} for i, t in ipairs(pages) do checkType('formatPageTables', i, t, 'table') local link = t[1] local display = t[2] links[i] = p._formatLink(link, display) end return links end

function p.formatPages(...) -- Formats a list of pages using formatLink and returns it as an array. Nil -- values are not allowed. local pages = {...} local ret = {} for i, page in ipairs(pages) do ret[i] = p._formatLink(page) end return ret end

function p.findNamespaceId(link, removeColon) -- Finds the namespace id (namespace number) of a link or a pagename. This -- function will not work if the link is enclosed in double brackets. Colons -- are trimmed from the start of the link by default. To skip colon -- trimming, set the removeColon parameter to true. checkType('findNamespaceId', 1, link, 'string') checkType('findNamespaceId', 2, removeColon, 'boolean', true) if removeColon ~= false then link = removeInitialColon(link) end local namespace = link:match('^(.-):') if namespace then local nsTable = mw.site.namespaces[namespace] if nsTable then return nsTable.id end end return 0 end

local function removeInitialColon(s) -- Removes the initial colon from a string, if present. return s:match('^:?(.*)') end

local function getArgs(frame) -- Fetches the arguments from the parent frame. Whitespace is trimmed and -- blanks are removed. mArguments = require('Module:Arguments') return mArguments.getArgs(frame, {parentOnly = true}) end


-- Helper functions


local p = {}

local libraryUtil = require('libraryUtil') local checkType = libraryUtil.checkType local mArguments -- lazily initialise Module:Arguments local yesno -- lazily initialise Module:Yesno


-- Module:Hatnote -- -- -- -- This module produces hatnote links and links to related articles. It -- -- implements the and meta-templates and includes -- -- helper functions for other Lua hatnote modules. --


References

See also

In 1971, a study released by DeLeuw retained the I-70S/I-95 North Central Freeway configuration. The study's various alternatives differed little from one another; one major similarity was the I-70S/I-95 wye junction, with the six-lane I-70S and the eight-lane I-95 (narrowing to six lanes, with the remaining two forming off ramps to North Capitol St.) merging into a 12-lane freeway that would quickly narrow to 10 lanes within the Union Station interchange. The plans included the 3/4-mile Rhode Island Ave.-Michigan Ave. tunnel, as well as revisions to an earlier 1970 proposal that would reduce the number of homes required to be removed from 69 to 34. [6]

1971 De Leuw-Weese Study

The justification used for this deletion, as recorded in the NCPC's "Red Book", was that traffic with destinations beyond the District should not be permitted to travel through the District, but instead bypass it via the Beltway. Traffic with destinations within the District, as noted above, were expected to use the street grid; the NCPC further justified this by stating that the Interstate Highway System as defined did not guarantee direct inner-city access. Furthermore, the NCPC also baldly stated that the construction of the North Central Freeway would simply provide another way into the District for commuters, which was seen as undesirable and unnecessary. [5]

In 1968, the U.S. National Capital Planning Commission released an updated Major Transportation Plan for the D.C. area which deleted the North Central Freeway and Northeast Freeway from the city's freeway grid. Traffic that would have made use of these freeway corridors was expected to either use the local street grid or the Capital Beltway. I-70S would have terminated on the Capital Beltway (as I-270 does now), and I-95 would have followed New York Avenue to the Baltimore-Washington Parkway, then continued north to its original routing, possibly via the Capital Beltway. [5]

1968 Major Transportation Plan

The final length of the NCF would have been 7.71 miles (12.41 km), cost approximately $193 million to build, and would have displaced 535 homes and 159 businesses. Ultimately, the plan was doomed by further opposition as a direct result of indecisiveness on the part of D.C. and Maryland transportation officials. [4]

The 1966 plan included separate ramp connections to and from both freeways and North Capitol Street, but deleted 'round-the-corner' connections to and from southbound I-70S and northbound I-95. South of the Northeast Freeway, the North Central Freeway would run to the east of the railroad, after passing through a 950-foot (290 m) tunnel in the Brookland area. At the point where the railroad curves to the southwest, the freeway would continue south and enter the site of the Union Station interchange, sparing 3 blocks near Jackson St. NE but removing 69 homes in the freeway's path. Also, the 196 plans for the North Central Freeway removed the reversible roadway that had been previously considered. [4]

The low-level option relocated the I-70S/I-495 wye interchange to a point 3/4 mile west of Georgia Avenue (MD 97), with the western wye of the interchange closely hugging the railroad alignment on its western edge; various short tunnels would be constructed to carry the freeway across parking lots and under the railroad, where it would join the eastern leg of the wye and continue south as a six-lane freeway. One major characteristic of this alignment, as compared to previous alignments, is its close companionship with the railroad; the separate carriageways would cross under/over it repeatedly to avoid housing developments and other areas; in Takoma Park, the railroad would be flanked by I-70S's carriageways, while south of Van Burean Street the southbound carriageway would shift to the northern side of the railroad and meet the Northeast Freeway near Riggs Road and New Hampshire Avenue. [4]

[4] The option chosen was the low-level option. Tunnels would be constructed in the vicinity of

  • a high-level option, with the freeway elevated over the railroad, allowing most of the industrial properties to remain in situ
  • a low-level option, with the freeway directly adjacent to the railroad or slightly below it
  • a below-grade option, with the railroad and Metro facilities suspended over the freeway
  • a concealed-railroad option, with the railroad and Metro buried beneath the freeway alignment

The enormous opposition to the 1964 and 1965 alignments for the North Central Freeway led to a supplementary study being conducted in 1966 that more closely examined routings that paralleled the existing B&O railroad corridor. Most of the alternatives created during this study retained a six-lane configuration for the northern I-70S segment and an eight-lane configuration for the southern I-95 segment. Three major options were considered:

1966 Supplementary Study

The study itself recommended the construction of a consolidated alignment, with the North Central Freeway following the B&O all the way through the District and outside it, within the Capital Beltway, before turning to follow 16th St. to the Beltway, which it would meet, and continue north of, near Sligo Park. Surprisingly, the study stated that the North Central Freeway north of the Beltway would not carry an Interstate designation throughout. [3]

[3] The study as a whole generally rejected alignments paralleling Georgia Avenue in favor of alignments along the

[3]

This article was sourced from Creative Commons Attribution-ShareAlike License; additional terms may apply. World Heritage Encyclopedia content is assembled from numerous content providers, Open Access Publishing, and in compliance with The Fair Access to Science and Technology Research Act (FASTR), Wikimedia Foundation, Inc., Public Library of Science, The Encyclopedia of Life, Open Book Publishers (OBP), PubMed, U.S. National Library of Medicine, National Center for Biotechnology Information, U.S. National Library of Medicine, National Institutes of Health (NIH), U.S. Department of Health & Human Services, and USA.gov, which sources content from all federal, state, local, tribal, and territorial government publication portals (.gov, .mil, .edu). Funding for USA.gov and content contributors is made possible from the U.S. Congress, E-Government Act of 2002.
 
Crowd sourced content that is contributed to World Heritage Encyclopedia is peer reviewed and edited by our editorial staff to ensure quality scholarly research articles.
 
By using this site, you agree to the Terms of Use and Privacy Policy. World Heritage Encyclopedia™ is a registered trademark of the World Public Library Association, a non-profit organization.
 


Copyright © World Library Foundation. All rights reserved. eBooks from Project Gutenberg are sponsored by the World Library Foundation,
a 501c(4) Member's Support Non-Profit Organization, and is NOT affiliated with any governmental agency or department.