Figured I'd start a thread on this since I didn't see anything mentioned other than a couple of notations in the catch-all 2013 meet.
Facebook page at https://www.facebook.com/events/158183621023513/?ref=ts&fref=ts.
Hosts are Cody Goodman and Jason Ilyes.
Not many confirmed participants as of yet. I'm going to be there, but not confirming on the FB event page.
I will probably have to split from the tour about 4 p.m. EDT. Planning on doing US 127 down and US 27 up, or vice versa, to clinch both highways in Tennessee.
Thanks for posting on here HB. I know it is probably short notice for a lot of you, but if we can get some locals to come it would be awesome!
The routing of the tour can be found here: https://mapsengine.google.com/map/edit?mid=zLF8lxjYMAkg.kRpDYOcl1bRE
We will be meeting at 11 AM at the Terminal Brewhouse located at 6 East 14th Street, Chattanooga, Tennessee 37408.
11 a.m.? FB page says 12.
Not sure if I will stay in Chattanooga Friday night, or somewhere on the route (Crossville, Harriman, etc.) and finish the drive Saturday morning.
I meant to make it 11 Am local time but I must have put it in CDT instead of EDT. I will go change it.
time zone sensitivity is great for events which are held simultaneously in multiple places (i.e. "conference call with Austin and San Jose offices") but really, there should be an override on Google calendar, Facebook, etc which says simply "event is held at local time".
currently, certain events during my upcoming vacation in Mountain time are shown as consistently one hour off, as my calendar sits in Pacific time. those events will, upon my landing in Denver, magically correct themselves as my phone adjusts its concept of local time. this will break the events which I have not bothered to label "Mountain time", because honestly it's a pain in the ass, and for planning purposes it defeats the purpose of a calendar to have everything shown 1 hour off, simply because the calendar sits in a different time zone than the event.
again, the solution is to have a special time zone called "local time" which always shows up as the same time, regardless of which time zone I am in, and regardless of which time zone the event is in.
Chattanooga is right on the boundary between Eastern and Central Time. It's in the Eastern time zone. When you leave Tennessee going west on I-24 and then re-enter after dipping into Georgia, you go from Eastern to Central time.
Steph and I plan to drive down Friday takeing a "back way" from my house in Lebanon, TN VIA Smithville\ McMinnville and Dunlap and staying Friday night. Sorry guys for the short notice on this but we all have been busy, between work and getting ready for my BIG road trip to the south west next month, been crazy but looking forward to seeing everyone at this meet! :-)
Quoteagain, the solution is to have a special time zone called "local time" which always shows up as the same time, regardless of which time zone I am in, and regardless of which time zone the event is in.
Already exists. It's called UTC or Zulu.
Quote from: froggie on June 21, 2013, 01:23:51 AM
Already exists. It's called UTC or Zulu.
no, this is not what I mean. Zulu time is a well-defined exact time: approximately GMT, not observing daylight savings, with some leap seconds and other complexities thrown in.
what I am looking for is indeed an ambiguous time. it is, say, "10am pacific daylight (GMT-7)" when I am in pacific time, and "10am mountain daylight (GMT-6)" when I am in mountain time... and it would be "10am GMT" if I were standing in Greenwich in winter.
if I set an event to occur at "10am zulu time", then my calendar would show it occurring at 3am when I am at work here in San Diego, and would show it occurring at 4am when I get off the plane in Denver. so, using zulu time is not the solution.
basically, I want it to say "10am" on my calendar regardless of where I am, where the calendar is, where the event is being held... I have no idea what to call it - "Solipsistic Coordinated Time"?
it would certainly be useful to describe, for example, the Chattanooga meet as occurring at "11am" without needing to take into account that the Facebook event was made by someone who happened to be in a different time zone. in short, I want it to appear as "11am local time" for all readers in all time zones, because by the time they get there, they don't care that "11am central" is equivalent to "12pm eastern", so why show 12pm to anyone at any time for any reason? it just breeds confusion.
Understand where you're coming from, but this is why most things operational (at least in those fields I work in) work in Zulu/UTC. Don't have to worry about time zone differences. 12Z is the same whether you're on the East Coast, West Coast, Argentina, Somalia, North Pole, etc etc...
I really wanted to go to this, and I could make this work - I have off work the 4th and 5th, but Mike would not be able to go and it's a pretty long way to go by myself. (I can and have done trips solo - I find that they are much more fun and less lonely with friends and/or Mike.) Plus, I'm still contemplating spending the holiday with my family in Central PA, which is in the opposite direction.
Thats ok Laura, we will see you guys in August! ;-)
Quote from: froggie on June 22, 2013, 07:23:12 AM
Understand where you're coming from, but this is why most things operational (at least in those fields I work in) work in Zulu/UTC. Don't have to worry about time zone differences. 12Z is the same whether you're on the East Coast, West Coast, Argentina, Somalia, North Pole, etc etc...
Why not just use the old Indiana Time and guess what time it is in the county you are in. A coin toss says you might be right or you might be wrong. :biggrin:
Quote from: froggie on June 22, 2013, 07:23:12 AM
Understand where you're coming from, but this is why most things operational (at least in those fields I work in) work in Zulu/UTC. Don't have to worry about time zone differences. 12Z is the same whether you're on the East Coast, West Coast, Argentina, Somalia, North Pole, etc etc...
very sensible.
as far as I can tell, Google Calendar doesn't have Zulu time as an option. I'll bet if they did, though, they would still display the events in the local time zone of the computer doing the viewing, which is precisely what I am railing against.
Just a reminder this road meet is coming up on Saturday July 6 at 11AM Eastern time, hope to see you all there!!
I'm planning on it unless something happens.
I'm thinking about attending. Since I'd need to leave Friday morning if I were to attend, I would need to decide by Thursday. Is there an earlier RSVP deadline on the Facebook page (which I can't access)?
Just say something here the day before the meet and all will be good. :)
Is the US 41/64/72 bridge crossing the Tennessee River (the one visible from I-24 as you're heading west out of Georgia toward Monteagle Mountain) open now?
Quote from: hbelkins on July 02, 2013, 11:37:24 PM
Is the US 41/64/72 bridge crossing the Tennessee River (the one visible from I-24 as you're heading west out of Georgia toward Monteagle Mountain) open now?
It is not.
We will be stopping at a marina/gas station to take pictures of both the old and the new bridges as part of the tour, time pending.
Quote from: codyg1985 on July 03, 2013, 07:18:58 AM
Quote from: hbelkins on July 02, 2013, 11:37:24 PM
Is the US 41/64/72 bridge crossing the Tennessee River (the one visible from I-24 as you're heading west out of Georgia toward Monteagle Mountain) open now?
It is not.
We will be stopping at a marina/gas station to take pictures of both the old and the new bridges as part of the tour, time pending.
OK, then I know not to waste any time trying to clinch US 72 in Tennessee Friday evening.
I will probably have to peel off the tour sometime between 3:30 and 4, if we're still out on the road at that hour. My guess is that lunch will go pretty quickly since we seem to be destined for a small attendance, so the tour will probably go pretty quickly as well.
I will be there! Last minute decision to go south instead of north for the long weekend.
I read over the itinerary and probably will depart the tour route at #68. I probably won't go out to the bridge since I have been out there several times. I want to wait until the new bridge is built so I can clinch US 72 in Tennessee.
(That's dependent on time. If we are at that spot around 2 to 2:30 p.m., I may continue on).
What is the unsigned routing of US 127 after its signed ending at US 27? I need to drive it in order to get a clinch of that route in Tennessee.
It is the official routing of US 127 per the US-ends website. (http://www.usends.com/Focus/Chattanooga/index.html). We will be driving the entire length of it during the tour.
Here is the itinerary (https://dl.dropboxusercontent.com/u/21716577/chattanooga%20meet%20itinerary.pdf) that HB is talking about. My apologies for not posting it here at the same time.
QuoteWhat is the unsigned routing of US 127 after its signed ending at US 27? I need to drive it in order to get a clinch of that route in Tennessee.
Basically east then south into downtown Chattanooga. Dayton Blvd to Market St to MLK Blvd.
Quote from: froggie on July 04, 2013, 08:53:20 AM
QuoteWhat is the unsigned routing of US 127 after its signed ending at US 27? I need to drive it in order to get a clinch of that route in Tennessee.
Basically east then south into downtown Chattanooga. Dayton Blvd to Market St to MLK Blvd.
http://www.tdot.state.tn.us/Maps/city/Chattanooga_SW.PDF
Looks as if US 127 ends and US 76 begins as Market crosses MLK.
Why US 76 exists in Tennessee at all, and why US 72 doesn't end out west of Chattanooga at US 41/64 is beyond me.
Looks like the end of US 72 may be different than we've been thinking as well.
^I wonder if US 72 ends at MLK as well?
Heading out from home soon. See ya in Chattanooga tomorrow morning.
QuoteI wonder if US 72 ends at MLK as well?
It doesn't. I went back through the AASHTO SCOH minutes/approvals. The US 11/64 reroute and the US 76 extension were approved by AASHTO in 2002. No application submitted (or mention at all) of US 72. So US 72 still ends at Main and Broad.
That said, I agree with HB in that it should be truncated back to Kimball.
Why does US 74 end at the state line on I-75? It is not even marked in the field if I can recall.
Quote from: Avalanchez71 on July 05, 2013, 10:38:18 AM
Why does US 74 end at the state line on I-75? It is not even marked in the field if I can recall.
That is a mystery to me. US 74 is a red-headed step-child in Tennessee, anyway. There is no mention of it west of Cleveland, TN.
Quote from: Avalanchez71 on July 05, 2013, 10:38:18 AM
Why does US 74 end at the state line on I-75? It is not even marked in the field if I can recall.
It doesn't. It ends at I-24.
Might need to adjust the tour itinerary a little. W Road is closed, according to signs at both ends along US 127.
Was there ever a US 27 BUSINESS through Chattanooga? I seem to recall seeing something like that in the 90s.
Quote from: hbelkins on July 05, 2013, 11:35:39 PM
Might need to adjust the tour itinerary a little. W Road is closed, according to signs at both ends along US 127.
That explains why when I tried to use Google to route myself along W Road it wouldn't let me.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fmedia.timesfreepress.com%2Fimg%2Fphotos%2F2013%2F05%2F03%2Fphoto-5_copy_t618.jpg&hash=4b9505a7d91f5edafbb84c72ebe917d22a8c2663)
http://www.timesfreepress.com/news/2013/may/03/photo-exactly-why-w-road-closed-traffic/
Holy crap. I can see why it's closed.
http://www.chattanoogan.com/2013/6/26/254031/W-Road-Expected-To-Reopen-On-July-15.aspx
Quote from: jpi on June 27, 2013, 04:33:36 PM
Thats ok Laura, we will see you guys in August! ;-)
Thanks! Mike did end up getting off but we went north for the 4th.
Enjoyable meet, but it rained constantly all day, which eliminated photo opportunities. I'm sure the views from Lookout Mountain and Signal Mountain would have been more scenic if not for the rain and fog.
Tennessee DOT signage sets an example for FAIL in Chattanooga, for sure.
Quote
Tennessee DOT signage sets an example for FAIL in Chattanooga, for sure.
Agree. On SB US 27 at I-24, the overheads fail to show you how to continue south on US 27.; The overheads for US highway multiplexes leave off some of the designations at exits on I-24, I-75, and SR 153.
The route markers on Broad at Cummings are confusing/misleading also. A short distance later there is a JCT US 11 sign when you are already on 11.
QuoteThe route markers on Broad at Cummings are confusing/misleading also. A short distance later there is a JCT US 11 sign when you are already on 11.
That would be the city of Chattanooga, not TDOT, in this instance.
There is at least one stray US 27 sign left in downtown Chattanooga (northbound on Market at Main), and the proper routing of US 76 is not marked at all. Plus, there's lots of signage on Broad indicating that US 11 and US 64 are still on that route.
Quote from: froggie on July 08, 2013, 12:44:58 AM
QuoteThe route markers on Broad at Cummings are confusing/misleading also. A short distance later there is a JCT US 11 sign when you are already on 11.
That would be the city of Chattanooga, not TDOT, in this instance.
Does the city do its own signage?
Yes...Tennessee cities do their own signage, not unlike what happens in Virginia with its independent cities. Hence why local route signage within those cities is usually crap.
Quote from: froggie on July 09, 2013, 05:32:35 AM
Yes...Tennessee cities do their own signage, not unlike what happens in Virginia with its independent cities. Hence why local route signage within those cities is usually crap.
They must get their signage from TDOT, however, because there's a unique type of US shield shape that I've seen only in Tennessee that is used on a lot of Chattanooga sign assemblies.
Quote from: froggie on July 09, 2013, 05:32:35 AM
Yes...Tennessee cities do their own signage, not unlike what happens in Virginia with its independent cities. Hence why local route signage within those cities is usually crap.
I don't think that is quite right. I have never seen that as an agenda item on some city budgets that I have monitored. That may be the case if there is a private act (law of local application). However, I know that in most cases the cities are pretty keen on stating that they cannot do this or that as the road is a state road.
You likely wouldn't see road signs as an agenda item on city budgets anyway, as (depending on the situation) it usually falls under road maintenance. The main exception being when signs are replaced en masse, where you'll usually see a contract.
Here's the meet photo. It rained during most of our tour, but at least at this spot we had partial cover from some train tracks overhead. I think this was on the North Access Road shortcut we took between TN 153 and TNs319, northeast of downtown Chattanooga.
(https://www.aaroads.com/forum/proxy.php?request=http%3A%2F%2Fwww.alaskaroads.com%2FChattanooga-meet-group_DSC9437.jpg&hash=079a5846b19a3d220dab1d37e0b503ae0763d927)
From left to right: Oscar Voss, Mike Tantillo, Cody Goodman, Jason Ilyes, and (with "SEND HELP" sign) H.B. Elkins.
It was a great meet, and revisit to a favorite city. The tour itinerary was pretty ambitious, covering most or all of Chattanooga's tunnels, a lot of winding roads on the west side of the city, and even quick dives into Georgia and Alabama. The early start (11am lunch), small group (most of us were in Cody's car), and few stops due to the rain helped.
As is customary, even though Mike and I live only a few miles away from each other, we traveled separately and had completely different itineraries before and after the meet (Mike's was Atlanta-centric; mine was US 11-centric, extending my clinch of US 11 including its 11W and 11E branches from Bristol VA south to the GA/TN state line).
QuoteYes...Tennessee cities do their own signage
Is it just cities of a certain population or greater?
There is some substandard signage in Kimball, including a NO PASSING ZONE sign that is rectangular; it replaced a normal one that was faded.
I too have though that US 72 should end at Kimball.
I think US 72 and US 76 should be one route number instead of how it is set up now. It would free up the other number for use elsewhere if needed.