Recent Posts

Pages: [1] 2 3 ... 10
1
Updates to Highway Data / Missing waypoint on US 76 in NC?
« Last post by ohroadscholar on Today at 04:02:18 pm »
Should there be a waypoint on in Wrightsville Beach, NC on US 76 at Sunset Ave and South Lumina Ave between waypoints StoSt and JackParAve. I have it down in my .list file as a waypoint of SLumAve.
2
I was thinking that jpnh would be type 3, but I see that US national highways are type 2.  Would type 3 be the better choice?  Japan already has systems for type 1 and 2.

It should be tier 4 like the other national highway systems in Asia (and Europe) but the Indian one is tier 3 - likely a mistake.
3
So happy to see Pyrénées-Orientales go to preview! Thanks for your work on this.

Happy to get positive feedback on my work :)

On FRA-OCC D627-11 it looks like there are a couple points near Port Leucate to fix. D627 does not have access to the two roads immediately on either side of the canal there. So PortLeu should be moved a few hundred meters south to ramps, and CheGrau should be moved a few hundred meters north to its ramps. Thanks again!

I think that the points are correct. Both are grade-separate junctions, and the points are at the underpasses. I know that it might look odd but there are numerous examples like that at other places. si404 often demanded the points when reviewing my systems.

https://travelmapping.net/hb/showroute.php?r=fraocc.d062711
4
6-Month+ Outlook / Re: New Jersey Outlook
« Last post by yakra on Today at 09:37:54 am »
2021
Oct 1: Wittpenn Bridge

2022
2022: US 1-9 Truck west of the tracks north of Tonnelle Circle
5
Updates to Highway Data / AZ: US-60/AZ-77 broken
« Last post by rickmastfan67 on Yesterday at 10:19:43 pm »
Seems the changes done to US-60 a few days ago broke it's multiplex with AZ-77 in the same area.


Code: [Select]
az.az077;+X143770;;;HIDDEN_JUNCTION;4
az.az077;+X210167;;;HIDDEN_JUNCTION;3
az.az077;+X304736;;;HIDDEN_JUNCTION;4
az.az077;+X476924;;;HIDDEN_JUNCTION;3
az.us060;+X599190;+X476924;+X709533;SHARP_ANGLE;158.35
az.us060;+X709533;PriRd;+X672105;SHARP_ANGLE;150.74
az.us060;+X917930;+X304736;+X599190;SHARP_ANGLE;164.24
6
Updates to Highway Data / Re: ON: Ontario Highway 427 extension open
« Last post by rickmastfan67 on Yesterday at 10:08:37 pm »
In addition, the freeway should have full exit numbers as a result.

Only the new segment has numbers (sans Major Mackenzie Drive).  However, video evidence has been posted that both ON-409 (13) & Derry Road (15) have been given exit numbers in the last month.
https://www.aaroads.com/forum/index.php?topic=59.msg2662221#msg2662221

This has now been submitted.
https://github.com/TravelMapping/HighwayData/pull/5119
7
So happy to see Pyrénées-Orientales go to preview! Thanks for your work on this. I wanted to bring one item to your attention.

On FRA-OCC D627-11 it looks like there are a couple points near Port Leucate to fix. D627 does not have access to the two roads immediately on either side of the canal there. So PortLeu should be moved a few hundred meters south to ramps, and CheGrau should be moved a few hundred meters north to its ramps. Thanks again!
8
I'll follow your advice about using devel-only systems to split up the work.

I think jpnh should be the system name for the national highways.

Devel-only systems can be used for each island, or island section for Honshu. They can be swept into jpnh as they are completed.
   jpnhky - Kyushu and Okinawa
   jpnhsh - Shikoku
   jpnhhk - Hokkaido
   jpnhkt - Kanto (east Honshu / Tokyo)
   jpnhks - Kansai (west Honshu / Osaka)

 I was thinking that jpnh would be type 3, but I see that US national highways are type 2.  Would type 3 be the better choice?  Japan already has systems for type 1 and 2.

9
6-Month+ Outlook / Re: AR/MO: Bella Vista Bypass
« Last post by ntallyn on September 19, 2021, 12:47:12 pm »
Sadly, I was there just last week and have no plans to return to the area any time soon.
10
Updates to Highway Data / Re: IL: I-64 Exit Revisions
« Last post by yakra on September 19, 2021, 11:19:06 am »
Apologies in advance...
Jim asked if I could process Highway63's .zip file and maybe come up with a list of users with broken .lists, as done with the Massachusetts exit renumberings.
Taking a look at the changes, I'm gonna offer my copper two-cent piece.

I-55 et al:
I-55/64/US 40: ... Change 2->2A (Eads Bridge/3rd St). NEW point labeled 2C (signed as MLK Bridge) to the WB exit/EB entrance point of that. Current location labeled 2C on I-55/US 40/IL 3, the new I-64/70 junction, needs to become 3, as you say. (Marked as 3 on I-64 already.) Current location labeled 3 on I-55/US 40 becomes 3C.

The latter set might break/move a few people's points, but I think that's unavoidable.
I think a better solution would be to not add a new point for 2C, go 1PPI, and consider it part of existing Exit 2 on Where the centerlines would cross if it were an at-grade intersection with the same shape grounds.
2 could stay 2, as 2A/B/C in one interchange.
This would free up 2C to become an AltLabel, and avoid breaking 16 .list files at this interstate-interstate junction.
Per that same rule, we can optionally keep the A, so 3A label can become the new label for the existing 2C, allowing 3 to be an AltLabel for 3C.
This would avoid breaking any .list files.
Code: [Select]
2 http://www.openstreetmap.org/?lat=38.628874&lon=-90.160203
3A +2C http://www.openstreetmap.org/?lat=38.633198&lon=-90.144153
3C +3 http://www.openstreetmap.org/?lat=38.634171&lon=-90.140462

IL3:
This looks kinda awkward, because the interchange layout is kinda awkward. Looks like SB does take the obvious right-turn ramp, though northbound gets more convoluted as there's no direct ramp.
IMO a better visual solution is to "cut the diagonal" as I like to term it, of the couplet, and put a point here, or even more precisely, maybe here? What to call it, maybe StCAve_S?
This would break the graph connection (& thus concurrency) at I-70 et al but would still leave one one point over at Exit 2 for surfing between intersecting/connected routes, or for Jim's students to do algorithms.

64/40:
Don't forget to change 28C -> 28B on I-64 itself. :)
FortyDr -> ForDr

Downtown / Downtown West: Reconstruction, renumbering? Yowch, what a mess!
38A looks appropriate.
That next point that peels off just after the Ewing overpass and touches down at Market & Garrison... Looks like its exit number has been removed but it's still open? Weird. Maybe not for long? 38B is not in use; if it's needed elsewhere it could become MarSt or eventually *MarSt?
38C looks like an appropriate label given that 38A is already used a couple points west. Probably should still be centered on Jefferson though.
22nd St: Moved from the demolished connector (something MoDOT originally had bigger plans for?). The new coordinates make sense. It's gone through some different exit numbers, switching from 39A to plain 39 between Oct 2011 & and May 2013, then to 38B between May & Aug 2021. I assume 38B is not a contractor error, and is the correct new 38B, along with removing the signage at the other exit farther west. 38D should still be kept as an AltLabel.
14th St: 39B -> 39A +39B
39B: Probably just as well calling 11th St a 1PPI along with Exit 40 (like you're already doing), not giving it its own separate point, and allowing 39B to stay in use as an AltLabel for 39A.
40: I can get behind collapsing the 2 points into one here. Just remember to include both 39C and 40A as AltLabels to avoid breaking .lists.
40C -> 40B makes sense.
Pages: [1] 2 3 ... 10