# Talk:New Jersey Route 35

Why isn't NJ 66 listed, that's very big it goes around a traffic circle, I'd think that's pretty big? please answer that. —The preceding unsigned comment was added by 24.228.70.72 (talk • contribs) 22:08, 17 August 2006  (UTC)

The traffic circle isn't what would make a junction major.  It's where the connecting road goes.  The infobox as it is remains slightly longer than it should be, and Route 66 was sacrificed because it parallels Route 33 so closely. -- NORTH talk 23:30, 17 August 2006 (UTC)

Route 36 doesn't intersect with NJ 35 in Keyport, does it? I know it does Southbound with the GSP on Route 35, Northbound. —The preceding unsigned comment was added by Nextbarker (talk • contribs) 03:19, 18 August 2006  (UTC)
I think where Route 9 merges in is considered Sayreville, cause I live in that area, and that's considered Sayreville. —The preceding unsigned comment was added by Nextbarker (talk • contribs) 04:14, 18 August 2006  (UTC)

The GSP/NJ 35/NJ 36 interchange is in Keyport -- although the ramps to the parkway merge to the parkway in Hazlet Township.
If you look at the straight line diagram, the junction between US 9 and NJ 35 is actually just north of the Sayreville/South Amboy city line. -- NORTH talk 15:20, 18 August 2006 (UTC)
It looks like there is a 1.25 mile concurrency with US 9, 0.54 miles of which are in South Amboy and 0.71 miles in Sayreville. Using either city should be ok. --Polaron | Talk 15:32, 18 August 2006 (UTC)
Okay, my bad.  I was in a rush and looked only at the south junction.  In that case, I agree with Nextbarker, as I am also fairly familiar with that area, and think Sayreville would be a better description. -- NORTH talk 15:40, 18 August 2006 (UTC)
Was a NJ 36 shield necassary to put next to the GSP shield in Keyport, since GSP & 36 meet at the same junction?
Nextbarker 05:35, 17 November 2006 (UTC)nextbarker

Was NJ 36 ok to add next to the GSP shield in the info box, I know NJ 36 and the GSP both meet at the same point on Route 35 in Keyport.
Nextbarker 00:24, 7 December 2006 (UTC)nextbarker

Yes. -- NORTH talk 00:56, 7 December 2006 (UTC)
OK, I thought it might not've been because the NJ 35 and GSP and NJ 36 junction are right there at the same point.
Nextbarker 06:12, 10 December 2006 (UTC)nextbarker

With the GSP shield gone is it ok to put 2 NJ 36 shields in the same info box.
Nextbarker 01:28, 27 December 2006 (UTC)nextbarker

It doesn't make a difference which shields are there.  We could list all the junctions with no shields, and the decisions would still be the same. -- NORTH talk 08:02, 27 December 2006 (UTC)

35 and Broad Street (in Red Bank) aren't even the same road...who came up with this? DodgerOfZion

Route 35 runs along the Atlantic Ocean coast only from Seaside Heights to Bay Head. It is an exaggeration to say it is an ocean coast road, except for that small section of roadway. From Neptune through Eatontown to Red Bank it travels inland on its way towards the western reaches of the Navesink River. Route 36 can claim being more of an oceanside route from Deal and Allenhurst to Sandy Hook, at which point it continues west near but not directly along the Raritan Bay all the way to Keyport, where it intersects with Route 35. Route 35 follows close to the bayshore to South Amboy, where it crosses the Raritan River. From there Route 35 travels north and inland towards Rahway. It might be better called a Jersey Shore route, which would include the ocean and bayshore areas and not so narrowly suggest it is a road that hugs the shoreline. Something to ponder, at least. --Pat (talk) 03:49, 28 May 2008 (UTC)

I believe the town where Route 35 North ends is Rahway, not Woodbridge.  —Preceding unsigned comment added by 24.228.70.72 (talk) 01:33, 6 July 2009 (UTC) 

Its in the article.Mitch/HC32 01:41, 6 July 2009 (UTC)

Hello fellow Wikipedians,
I have just modified 4 external links on New Jersey Route 35. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

Added archive https://web.archive.org/web/20071031111034/http://www.jimmyandsharonwilliams.com/njroads/1920s/images/1927_routes.gif to http://www.jimmyandsharonwilliams.com/njroads/1920s/images/1927_routes.gif
Added archive https://web.archive.org/web/20110514153745/http://www.jimmyandsharonwilliams.com/njroads/1920s/maps/1927tt2.jpg to http://www.jimmyandsharonwilliams.com/njroads/1920s/maps/1927tt2.jpg
Added archive https://web.archive.org/web/20110628183145/http://en.wikisource.org/wiki/1953_New_Jersey_state_highway_renumbering to http://en.wikisource.org/wiki/1953_New_Jersey_state_highway_renumbering
Added archive https://web.archive.org/web/20080514013630/http://www.whereroadsmeet.8k.com/article/clover.htm to http://whereroadsmeet.8k.com/article/clover.htm
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 5 June 2024).

If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
If you found an error with any archives or the URLs themselves, you can fix them with this tool.
Cheers.—InternetArchiveBot (Report bug) 03:59, 17 February 2018 (UTC)