Recent Posts

Pages: [1] 2 3 ... 10
Updates to Highway Data / Re: AR: US 63 rerouted
« Last post by the_spui_ninja on Yesterday at 10:58:12 pm »
Here's a 63 North sign from I-40 in Brinkley: link
Updates to Highway Data / Re: MD: MD 7 (Perryville)
« Last post by Duke87 on Yesterday at 08:54:12 pm »
Think that label is tidier as "PerPoiHos" so let's go with that.

As for Coudon Blvd, I'm not going to bother with it unless someone explicitly needs it for their travels.
Updates to Highway Data / NJ: I-295/US-30 interchange
« Last post by rickmastfan67 on Yesterday at 08:10:30 pm »
Shouldn't we have a graph connection here between the two routes?  There are 3 direct ramps between each of them that would warrant a point centered on the overpass there.

What I would change is the following:
NEW -> 29A (centered on the overpass of I-295 over US-30)
29 -> 29B +29

NEW -> I-295 (centered on the overpass of I-295 over US-30)
I-295 (current) -> CR666

While the 'I-295' point would have to move, it's close enough that I'd think no update mention for the update page would be necessary in this case.

I also want to thank Roadsguy from the AARoads Forum for making the changes in OSM yesterday after I updated this old thread about this project (
Other Discussion / Re: New Travels and Stats Discussion
« Last post by oscar on September 20, 2020, 09:12:37 pm »
Always bring flip flops because you never know when you’ll need them.
i never have any sort of footwear along.

My feet injure too easily to avoid footwear on the road. For example, two broken little toes while barefoot (pain but no hassle --  they were just "buddy-taped" to adjacent uninjured toes, until the little toes healed).

My doctor told me to stop walking around naked inside my apartment (with the blinds closed), for that reason. She asked me to at least wear flip-flops.
Other Discussion / Re: New Travels and Stats Discussion
« Last post by dave1693 on September 20, 2020, 08:46:45 pm »
I've only made two trips since the middle of March, both of which were between northern VA and eastern PA that I've done hundreds of times before. I did manage some new mileage though.

New clinches:

US30BusTrkDow in PA (completely by accident), US202AltTrkNor in PA, PA238, PA340, PA341Truck, PA392, PA463, PA921, MD134, MD139, MD162, MD170, MD198, MD652

New mileage on still-not-clinched roads:

US30Business (Downingtown) in PA, US322 in PA, PA23, PA23 Alt Truck (King of Prussia), PA24, PA74, PA896, MD176, MD648

Between the pandemic and vehicle problems, both of which have heavily curtailed my travel, I expect most of the rest of 2020 and early 2021 to have very little, if any, more new mileage from me.
How To? / Re: I-485 Charlotte Format
« Last post by yakra on September 20, 2020, 07:33:57 pm »
NC I-485 51 10 should work.

I was noticing that on NC I-485 around Charlotte that waypoints start and end at MM30, not MM0 like typical beltways.
Your intuition is right here; one needs to look at where the route starts and ends. Every TM route can be thought of as a line. Sometimes, these lines happen to start & end at the same place.
Clinched segments are connected along this line -- you get the segments between 51 and 10.
Now, if you had passed along the north side, via TM's begin/end @ MM30 aka I-85(48)? Then the .list line above would show the opposite of what you want, and you'd need to split it up. One line from Exit 51 to the beginning, and another line from Exit 10 to the end.

So, don't be confused by where a MM0 ever is. You just need to pay attention to where TM's beginning & end are.
(Think of a loop that would look more normal with just crossroad style labels and no exit numbers, such as TXLp7...)

Why's I-485 so weird?
When Tim first created "Clinched Interstate Mapping", I-485 wasn't a complete loop, and the exit numbers just reset in the middle of the partial loop. So, he created a single file for the route as it existed at that time.
When the loop was finally completed in 2015, Oscar extended the route by adding the new points on to the end of the line. He kept the existing point ordering, because to do otherwise would mess up people's .list files.

Meanwhile, in Canada...
AB201 is split up into two segments to avoid this exact situation.
When the loop is complete, the segments can all be joined together in the right order in a way that maintains .list compatibility, the same way that I-74Sea, I-74_E, I-74FutEll and I-74FutHig all refer to NC I-74Hig now.
This feature wasn't introduced until CHM was several years old, so this kind of future-proofing wouldn't have even crossed Tim's mind in the early days. By then, I-485 as we know (knew?) it was well established, as were people's .list lines. And so it is what it is...
Updates to Highway Data / MD: MD 327 Short Extension
« Last post by Markkos1992 on September 20, 2020, 06:42:01 pm »
As of 2018, it seems that MD 327 was extended to the dead end on Ikea Way east of Marion Tapp Pkwy.  I am glad I drove to the dead end when I drove this yesterday.
Updates to Highway Data / Re: AR: US 63 rerouted
« Last post by yakra on September 20, 2020, 06:38:51 pm »
The Marked Tree city map shows AR149 taking over the vacated alignment on Frisco St.
In Jonesboro, AR463 gets extended.

I've seen no evidence of this in GMSV (haven't exactly been searching old US63); haven't been paying attention to what's been said on AARoads.
Updates to Highway Data / MD: MD 7 (Perryville)
« Last post by Markkos1992 on September 20, 2020, 06:29:19 pm »
yakra, would PerPoiVHos have made your grepped labels list?

Also a point for Coudon Blvd may be useful on both MD 7 and US 40, but I am fine with them being omitted due to the proximity of MD 327 and MD 222 respectively on both routes.
Pages: [1] 2 3 ... 10