Recent Posts

Pages: [1] 2 3 ... 10
1
CA US66HisHol/CA US66HisAzu:
What's the deal at the west end of CA US66HisHol? US 66 never went that way; it always turned down Lincoln to end at Olympic. As of December 2017 this was backed up by signage, along with an end sign at Olympic.
How was it decided what route CA US66HisHol would follow through LA? I can't find any signs on the Goog, but if you're going for the longest-lasting alignment, that would be Sunset-Figueroa, then onto the Arroyo Seco Parkway to Pasadena. Pre-freeway (opened 1940!) it used Figueroa (partly repurposed for the freeway through Elysian Park) all the way to Pasadena. If it ever used Broadway to Mission, that was before 1934 (at which time the route was San Fernando-Eagle Rock-Colorado).
I did find two signs at Figueroa and Colorado. So unless anyone has a good reason for a different alignment (such as signs I missed), we should change it to turn off the current route at Sunset and Figueroa, north on Figueroa to SR 110, then overlapping SR 110 between 24B and 26, then taking over CA US66HisAzu.

CA US66HisCaj should also be combined with these two, now that Cajon Boulevard has been built across I-15.
2
Other than the California State Highway resync issue, I think we can push this system further along the road to activation now.

Don't forget neroute2's point requests which include some historic routes in CA, erroneously posted in the Updates form. Neither I nor anyone else appears to have made those changes, but his suggestions for changes to usaca routes (which I haven't finished reviewing) seem to be mostly reasonable. I plan to move his point requests re: historic routes here, as well as move his usaca-related requests to the usaca thread, so they'll be in the right place.

In addition to changes to usaca routes, all the active system routes in California were redone after usaush was drafted, and so would need to be part of the resync. The NMP log should flag them, Also, there is some danger that possible future removals of relinquished state route segments concurrent with historic routes, like CA 2/US 66 His (Hollywood), would require additional re-synching changes to usaush routes, though I hope such changes will be manageable in number.
3
I've purged US20His segements that I couldn't find evidence of.

Other than the California State Highway resync issue, I think we can push this system further along the road to activation now.
6
In-progress Highway Systems & Work / Re: usanyp: New York Parkways
« Last post by yakra on Yesterday at 01:13:15 am »
So do I assume correctly that:
- the proposed routing would name the point at the Caton Ave Overpass "OcePkwy"
I'm thinking, leave it labeled "5", and just change its coords.

- Ocean Parkway in usanyp would be extended to have its northern terminus at the same coordinates
- the point name for said northern terminus would be "NY27"
Correct on both of these.

It still leaves the northernmost 3 blocks of Ocean Parkway (which are part of the named road "Ocean Parkway" but not part of reference route 908H) unmapped, but... that's short enough that I'm not terribly bothered letting it get lost in the noise in the area.
"OCEAN PWY svce rds" per GIS -- fudged in the field for simplicity?  ;D
7
Updates to Highway Data / Re: NJ: I-80 WB at Hainesburg Rd (west of Exit 4)
« Last post by compdude787 on July 20, 2018, 03:00:26 pm »
I agree with Yakra here. No need to make up an exit number if the exit doesn't have one.
8
Other Discussion / Re: Waypoint splitting at interchanges
« Last post by rickmastfan67 on July 19, 2018, 11:02:47 pm »
FL826 itself for the most part looks pretty straightforward.
• The segment from I-95(12A) to 2ndAve looked like it was pretty difficult to handle. Without looking over it in too gory detail I'm pretty OK with how this was done.

Don't get me started on that one. lol.  Too many posted routes in that little clusterfuck.

I was and forgot to mention specifying the interchange with the Turnpike. and just realized I meant FL836 (wrong #) and for that matter the turnpike itself at exit.  26 and 26A waypoints on the turnpike and FlTpk(26) & FlTpk(26A) on FL836.  The flyovers from the south oppose the loop ramps from the north.  It doesn't help that NW 12th street interchange (27) with the turnpike is really close to the 26A waypoint (Which is actually Exit 26).

Ok, for the 'FLTpk(26)' & 'FLTpk(26A)' points on FL-836.  There's a simple reason for that.  The route used to end on the 'ramps' to "FLTpk(26A)".  Then, back in 2007, they built the new 'extension', "FLTpk(26)", which was also only 'SunPass' for the start.  So, both points are there to allow people who clinched the original route, or couldn't use the new 'SunPass' alignment (till it became all electronic).
9
Other Discussion / Re: New Travels and Stats Discussion
« Last post by oscar on July 19, 2018, 08:40:50 pm »
I just got back from a few weeks on the road, taking a sidewinding southern route out to Colorado then a more direct northern route on the return. Part of the plan was to clinch several US routes, plus the long TX 114 across Texas. I was able to clinch US 601 and TX 114, plus re-clinch US 33 after its recent relocation in Goshen IN, and re-clinch in advance US 29 in Lawrenceville GA once its pending relocation is implemented (not yet). I wasn't quite able to finish off US 501, US 80, and US 138 due to mid-route construction closures, so I'll have to go back and finish off the missing route segments once those projects are completed.

Between the outbound and return trips, I spent several days soaking at a favorite hot springs resort in southern Colorado, a mountain location with limited cellphone or Internet access. I did some light travel around Colorado before returning home, including becoming the only user so far to clinch CO 65, CO 92, and CO 330 east of Grand Junction, and CO 17 and CO 136 in the Alamosa area.
10
In-progress Highway Systems & Work / Re: usanyp: New York Parkways
« Last post by Duke87 on July 19, 2018, 07:23:52 pm »
So do I assume correctly that:
- the proposed routing would name the point at the Caton Ave Overpass "OcePkwy"
- Ocean Parkway in usanyp would be extended to have its northern terminus at the same coordinates
- the point name for said northern terminus would be "NY27"
?

If so then... yeah that's a reasonable enough solution.

It still leaves the northernmost 3 blocks of Ocean Parkway (which are part of the named road "Ocean Parkway" but not part of reference route 908H) unmapped, but... that's short enough that I'm not terribly bothered letting it get lost in the noise in the area.
Pages: [1] 2 3 ... 10