Recent Posts

1

Updates to Highway Data / Re: KY/AR: New I-169 and I-57!

« Last post by TBKS1 on Yesterday at 07:47:54 pm »

I am assuming I-57 still isn't signed in the wild in Arkansas, right (not counting "future" signs)?

I literally live right off it, it's not signed yet. I remember when the "Future I-57" designation became official in late 2017, and "FUTURE I-57" shields weren't installed until February 2018. Biggest difference between adding those signs and the official designation, is replacing all of the BGSes and all of the individual US 67/167 shields, which could take weeks or months. I have no idea what the status of any future signs going up are, I haven't stopped by the ARDOT sign printing shop since its designation meeting, but I imagine they're in the process of working on it, it'll just take a while. I'll be one of the first people to know when it gets signed, and I'll let you guys know about it here (and on aaroads) once it's designated.

2

Updates to Highway Data / Re: OR: US 97 in Bend

« Last post by Bickendan on Yesterday at 07:24:29 pm »

Does sound tasty, with some cheese, almonds, strawberries, and a good vinaigrette...


All changes done locally. Will submit with the Sikkim and Uttar Pradesh drafts I'm working on.

3

General Web Design Discussion / Re: What are mileages based on?

« Last post by bejacob on Yesterday at 05:22:52 pm »

Depending on the trip, I do sometimes highlight the "untraveled routes." You're right that it can be especially helpful spotting the relevant routes especially very short ones. I've definitely found a few I would have missed otherwise by switching between "traveled" and "untraveled."

Like you, the bulk of my planning is done in advance and put into my route plan (I use CoPilot GPS by Trimble). If I have extra time to grab a few miles, I can change course on the fly which is where having this info at my fingertips comes in handy. It's not always easy to do on my phone when behind the wheel, especially in bad weather or heavy traffic, though I've pulled up the TM site often enough while in transit.

This is more of "nice to have" request that a need. Everyone has their method to figure out a driving plan. This one works for me.

I agree that the number of segments is irrelevant.

4

Updates to Highway Data / NC: US 220 (Future I-73/I-74) Rockingham Bypass

« Last post by Markkos1992 on Yesterday at 04:30:10 pm »

https://www.aaroads.com/forum/index.php?msg=2965119

NCDOT has announced that the Rockingham Bypass will open Tuesday. 

5

General Web Design Discussion / Re: What are mileages based on?

« Last post by michih on Yesterday at 02:04:47 pm »

The attachment is an example of a screenshot from TM near Ashland, OH when I was heading up there last fall. After grabbing the image, I would have written in the route numbers and mileage between junctions with particular note of the untraveled portions so I might be able to figure out in advance what I wanted to cover.

Why don't you highlight "Untraveled routes"? I think that's better to spot the relevant routes on the road.
I do the planning in advance. The exact route is in my GPS. I just follow it on the road. I'd love to see the new mileage per route in showroute when mapping the travel after the trip. If possible with %. The number of segments is irrelevant for me.

6

General Web Design Discussion / Re: What are mileages based on?

« Last post by bejacob on Yesterday at 01:07:43 pm »

I think you might be misunderstanding the way I would use such a feature were it to be added to TM.

Before hitting the road, I often grab a screenshot of the area I plan to visit. I then print it out and jot down the mileage along all the routes visible. I would omit the routes I've already driven unless I think I would need to traverse them in the process of covering previously undriven routes. On a recent trip to Jacksonville, I took over a dozen such printouts with me, all calculated and labeled by hand with routes and mileage I was thinking of driving.

The attachment is an example of a screenshot from TM near Ashland, OH when I was heading up there last fall. After grabbing the image, I would have written in the route numbers and mileage between junctions with particular note of the untraveled portions so I might be able to figure out in advance what I wanted to cover.

As noted originally, I currently do this by adding up the mileage of each segment. All I'm wondering is if there is a faster way or if one could be added. If not, I'll keep doing it by hand. No problem.

On a side note, I use Google Maps frequently when on the road and review/update the "Your Timeline" feature.

As for the accuracy of the mileage, for my purposes, the TM approximation is sufficient. It's more of a guide as to whether I want to drive a couple miles out and back or dozens of miles. Sometimes it's not worth the time commitment just to clinch a road. Other times, getting that clinch might justify the drive.

7

General Web Design Discussion / Re: What are mileages based on?

« Last post by pderocco on Yesterday at 03:14:37 am »

Let's say I wanted to drive US1 in Florida (I've driven a little over half of it already), but perhaps on a future trip, I am only interested in the section from Vero Beach to Melbourne, just part of what I have not done yet. For this section the southern waypoint is FL60 and the northern one is US192. That looks like about 14 segments to me, with the only ones intersecting other TM routes being FL510 and FL514. Maybe in planning a hypothetical trip, I want to know the distance on US1 between FL60 and FL510, FL510 and FL514, and FL 514 and US192. I don't really care about any of the other waypoints, as I would probably use one of those routes as my entry/exit point. I can click on each segment of US1 and add up the individual mileage of the 6 segments between FL60 and FL510 which totals to 8.7 miles. I could do the same for the other parts as well. I think the entire stretch between FL60 and US192 is 34.39 miles (for my purposes, the approximation TM uses is fine). Adding up all the pieces by hand seems like a brute force/tedious way to find the distance between two points on a route.

I find Google Maps to be a very good tool for this, if you go to Saved->Maps->Open My Maps->Create a new map, and then use the line tool, Create Driving Route. If you've never done this, it will take a little sleuthing to figure out how this tool works, but it allows you to draw any route, and if it chooses the wrong route, you can grab the line and drag a waypoint to wherever you want. In the end, you can choose Step-By-Step Instructions from the layer containing the route, and it will give you a much more accurate mileage. You can also save the entire map as .kml or .kmz, if you want. So I don't think TM needs this function for planning trips.

8

Updates to Highway Data / Re: OR: US 97 in Bend

« Last post by the_spui_ninja on January 23, 2025, 10:26:08 pm »

So, if you 'must' keep it, probably should be *RomVilWay instead.

Never been to a village of lettuce before...

9

Updates to Highway Data / Re: OR: US 97 in Bend

« Last post by rickmastfan67 on January 23, 2025, 08:57:57 pm »

A few more issues with US-97 in that area:

142 -> ChiHatRd or PonSt (There is NO exit number posted there.)
141A -> Was there really an exit here?  Doesn't seem to be, at least anymore.  Seems per GSV from 2012, it was just a 'named' road.  So, if you 'must' keep it, probably should be *RomVilWay instead.

10

Updates to Highway Data / OR: US 97 in Bend

« Last post by Bruce on January 23, 2025, 01:56:27 pm »

An extension of the Bend Parkway opened a few months ago, with a new alignment up to the Cooley Road area for US 97: https://www.oregon.gov/odot/projects/pages/project-details.aspx?project=21229

Updated Street View imagery indicates that the old alignment is now an extension of Business Route 97: https://maps.app.goo.gl/mWXV1FCFtd82zCL68