A second TRUCK US 2 in St. Johnsbury, VT

 
Post new topic   This topic is locked: you cannot edit posts or make replies.    Clinched Highway Mapping Forum Index -> Old topics
View previous topic :: View next topic  
Author Message
froggie



Joined: 14 Jul 2008
Posts: 848
Location: Norfolk, VA (when not out to sea)

PostPosted: Mon Dec 29, 2008 8:34 pm    Post subject: A second TRUCK US 2 in St. Johnsbury, VT Reply with quote

Yes, you read that correctly.

This is mostly for Tim and Yakra. I've been meaning to mention this for some time now, but just never got around to it.

There is a second TRUCK US 2 in St. Johnsbury, in the downtown area. It's signed to the south of mainline US 2, utilizing US 5 and ALT US 5.

I first noticed it when I started making regular runs north (Meaghan lives in Lyndonville, the next town to the north).

So the question, mainly to Tim, is how to "filename" such a route. I was thinking US2TrkStJ2 but I'm open to suggestion.
_________________
Froggie
http://www.ajfroggie.com
Back to top View user's profile Send private message Visit poster's website
admin
Site Admin


Joined: 13 Jul 2008
Posts: 4053
Location: Maryland

PostPosted: Mon Dec 29, 2008 10:02 pm    Post subject: Reply with quote

Well, if you are sure it's not just a weird multiplex, make two files and we'll treat them separately.

For a precedent, see US 67 Business in San Angelo, TX. I think there was another case in one of the western states, but I can't remember where.
Back to top View user's profile Send private message
rickmastfan67



Joined: 14 Jul 2008
Posts: 2031
Location: Pittsburgh, PA

PostPosted: Mon Dec 29, 2008 10:04 pm    Post subject: Reply with quote

Franklin, TN.
Back to top View user's profile Send private message AIM Address
yakra



Joined: 30 Jul 2008
Posts: 2600
Location: Area Code 207

PostPosted: Tue Dec 30, 2008 1:07 pm    Post subject: Reply with quote

Weird multiplex? Not sure what you mean. Certainly no weirder than NC US17BusTrkEli, which is piggybacked onto other existing US routes. I'm sure there are others like that, but I can't think of any examples.
The existing VT US2TrkStJ is a `plex with I-91 & I-93 with a pinch of VT18 for flavor.

And between San Angelo, TX & Franklin, TN, I see we've established two filenaming precedents. So going forward, I propose using a "wing it!" convention to name such routes. =)

So how about US2TrkStJ & US2TrkStJ_S (us002trkstj & us002trkstjs)?

I kinda shy away from a 1/2 suffix, as I think it implies one route somehow takes precedence over the other. (Importance, chronology, what-have-you...) I see that in TN we have one sensible & one silly route. =)
Or it could imply that one loop comes before the other as you travel the parent route W->E... but is this really the case here? One loop is contained entirely within the diameter of the other.

In TX, is US67 signed E/W? Hence the letter suffixes on these routes. Though it's a rather different case from my proposal for the suffixes in VT differing from the overall signed direction, there is precedent.

My existing US2TrkStJ would become US2TrkStJ_S, and Froggie's would become the new US2TrkStJ. I want to avoid using a _N, as that maybe could be taken to imply that one route lies north of the mainline US2.
Back to top View user's profile Send private message
admin
Site Admin


Joined: 13 Jul 2008
Posts: 4053
Location: Maryland

PostPosted: Tue Dec 30, 2008 1:24 pm    Post subject: Reply with quote

Keep the city abbreviations to exactly 3 letters. If you want to say (South) St. Johnsbury, use SSJ. Let the direction "South" refer to the location of the route relative to the city rather than to the route's direction.

Hmm, I like using a descriptive distinction (like a direction such as "South") rather than the arbitrary numbers used for Trk US 31 in Franklin, TN. Let's change this case to match Johnsbury and San Angelo.

Actually, if I'm reading this right, the two truck routes in Franklin are continguous? The end of one is the beginning of the other? In that case, we ought to just have one long route.
Back to top View user's profile Send private message
andytom



Joined: 14 Jul 2008
Posts: 412
Location: Beaverton, OR

PostPosted: Tue Dec 30, 2008 4:31 pm    Post subject: Reply with quote

admin wrote:
Actually, if I'm reading this right, the two truck routes in Franklin are continguous? The end of one is the beginning of the other? In that case, we ought to just have one long route.


We did this with contiguous business route pairs in Kenedy and Karnes City, TX along US-181.

--Andy
Back to top View user's profile Send private message Visit poster's website
andytom



Joined: 14 Jul 2008
Posts: 412
Location: Beaverton, OR

PostPosted: Tue Dec 30, 2008 4:42 pm    Post subject: Reply with quote

yakra wrote:
In TX, is US67 signed E/W? Hence the letter suffixes on these routes.


No. The published (and usually signed) business route suffixes on these routes are H and J (the appropriate position in the alphabet percentage-wise with relation to the business routes' locations along the entire primary route, as is done with all bannered routes in TX).

As for the directionals on the primary route, I don't know what they are. We handled it as a N/S route even though it goes mostly E/W through TX. It does go E/W through San Angelo.

--Andy
Back to top View user's profile Send private message Visit poster's website
yakra



Joined: 30 Jul 2008
Posts: 2600
Location: Area Code 207

PostPosted: Tue Dec 30, 2008 5:42 pm    Post subject: Reply with quote

Quote:
No. The published (and usually signed) business route suffixes on these routes are H and J (the appropriate position in the alphabet percentage-wise with relation to the business routes' locations along the entire primary route, as is done with all bannered routes in TX).

Aye, I remember the letter-suffixed designations from when I was helping with TX. When I saw Tim citing a precedent from TX, I had to wonder if the files used these letter designations as suffixes. Though it's not something that would be relevant to extend to other states. Either way, this wasn't used for the filenaming, so it's kinda moot, eh? ^^

Quote:
As for the directionals on the primary route, I don't know what they are. We handled it as a N/S route even though it goes mostly E/W through TX. It does go E/W through San Angelo.

Right, keeping with the overall direction of the route rather than the signed direction in a state. I remember there were some issues with US52 & US275, being signed different dirs in different states. Order of points was changed to keep a uniform direction appropriate the route's overall direction across all states.

So this suffix refers the the route's "compass" direction in the immediate area, not overall direction...
Back to top View user's profile Send private message
Display posts from previous:   
Post new topic   This topic is locked: you cannot edit posts or make replies.    Clinched Highway Mapping Forum Index -> Old topics All times are GMT - 4 Hours
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


2005 Powered by phpBB © 2001, 2005 phpBB Group

Free Web Hosting | File Hosting | Photo Gallery | Matrimonial


Powered by PhpBB.BizHat.com, setup your forum now!
For Support, visit Forums.BizHat.com