Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on September 15, 2018, 05:03:11 pm
-
http://forum.travelmapping.net/index.php?topic=2321.msg11336#msg11336
I looked at I-66 as a result of vdeane's post above, and I noticed that I-66 and US 50 are not lined up on their concurrency in VA, at the VA/DC line, or at Exit 57 near Fairfax.
EDIT: I also just saw that US 50 is not lined up at the VA/WV line either though this may be worked on in conjunction with rickmastfan67's WV recentering project.
-
corrected the US 50/I-66 points...
-
Bumping as I found the other following points on I-66 that should most likely be lined up:
1 (I-81), 28 (US 17 BUS (Marshall)), 40 (US 15), 57 (US 50-mentioned above), 64 (I-495)
Mike, it may be best to check all of the interstates on this when you get extra free time. I looked at the VA NMP list (http://travelmapping.net/logs/nmpbyregion/va.nmp) and saw many related to just the interstates.
-
Further thoughts:
US 50 (DC): I-66 label should IMO be I-66_E.
I-66 (DC): US50 should be US50_E.
I-66 (VA):
Double half interchanges: Usually use one central point and treat both halves as a single, full interchange. Exceptions: a clear gap of at least 0.5 mi/0.8 km separates the two halves, or each half connects to a different highway that we are also mapping.
How would this rule affect Exit 71? The eastern half with the WB exit directly connects to VA 120. The western half does not directly connect to a route. I would most likely move 71 to the western half, and create 71A to line up with VA 120. VA 120 already has points at both set of ramps.
US 50 (VA):
1. The point at VA 286 needs to be lined up with it.
2. Maybe add a point at SR 645 (Stringfellow Rd) as it directly connects to the I-66 HOV (Future HOT) Lanes. Maybe SR 657 (Centreville Rd and Walney Rd) as well due to connecting to VA 28 via the Williard Rd and SR 662 (Westfields Blvd) interchanges.
3. Reed St would be better served at SR 626 (Plains Rd) (https://www.google.com/maps/@38.9677473,-77.7387661,3a,15y,89.49h,84.35t/data=!3m6!1e1!3m4!1s_BJRGwfRYFweztWsi1Vw9Q!2e0!7i13312!8i6656).
-
I made all the fixes to US 50 in Virginia. The I-66 in Virginia exit 71 does not meet the criteria to make two interchanges (distances are <0.5 mi).
I did not assess or address the DC items...
-
Regarding the WV/VA point in both 'WV US50Rom' & 'VA US50', I think the WV point is the closest to being in the correct location.
mapmikey, is it possible that you can sync 'VA US50' to the WV coordinates for this point?
WV/VA http://www.openstreetmap.org/?lat=39.284743&lon=-78.392448
Thanks!
-
The I-66 in Virginia exit 71 does not meet the criteria to make two interchanges (distances are <0.5 mi).
I think it does do to the fact that VA-120 not having it's proper graph connection with I-66. Plus, it's about ~0.4 mi. I think that's close enough to do the fudge especially when you factor in the VA-120 issue.
71 http://www.openstreetmap.org/?lat=38.882166&lon=-77.121685
71A http://www.openstreetmap.org/?lat=38.886540&lon=-77.117758
(Note: those are the coordinates from VA-120's file (for the '71A' point), so it doesn't need to be updated, only I-66.)
==
On another note when it comes to I-66, shouldn't it have a point for it's partial interchange with US-29/VA-237 @ Exit #69? Sure, it would cut down the spacing between points here, but since we do map both of the intersecting routes, and the graph connection that should be here is missing, it's a logical addition. Right?
69A http://www.openstreetmap.org/?lat=38.887901&lon=-77.161499No changes would be needed to US-29 & VA-237's files since those are the same coordinates from them. It just needs to be plopped into I-66's file.
==
A few other minor issues I've noticed with I-66 is that there are a few other interchanges with other routes that aren't synced with each other that should be. They are as follow:
1 (I-81)
28 (US17BusMar (http://travelmapping.net/hb/?units=miles&u=null&r=va.us017busmar) -- US-17 there is fine, just the Business Route that needs to be synced to both of them)
40 (US-15)
57 (US-50)
64 (I-495)
Fixing those between each route would clear quite a few lines from the NMP log that shouldn't be there. ;)
EDIT: I just saw that Markkos1992 mentioned this in reply #2 (http://forum.travelmapping.net/index.php?topic=2690.msg12453#msg12453) as well. Sorry for the double post here on that.
-
69A would make sense, as we map both intersecting routes.
71A, the CHM manual would have us use a single point in between the halves, even if the point on the intersecting route is elsewhere / on one of the halves, etc.
Compare I-95@30|CT vs CT113@I-95.
Is this one of Tim's rules we'd want to move away from a bit, considering the increased emphasis on graph connections, for Jim's students etc.?
-
Is this one of Tim's rules we'd want to move away from a bit, considering the increased emphasis on graph connections, for Jim's students etc.?
I had already previously believed we were in that direction.
-
I did that for CA 70(48A&48B), where only 48B intersects a TM-mapped route (CA70BusOro).
In that instance, we could remove 48A, and rename 48B => 48. Not so simple for I-66, since removing 71A would require adding a shaping point there or somewhere in the vicinity.
I think splitting I-66(71) is the way to go.
-
I believe I made adjustments on everything here including re-syncing of the I-66 points...thanks...
In the queue
-
The tweaks look good to me on I-66. And you fixed the US-50 border issue. :)
I don't see any other issues. Anybody else? If not, we can mark this as solved. ;)
-
I found some further issues. Addressing these should finally take care of everything:
I-66:
1. I think 61 should be changed to 62A. The Metro Access is a part of the Exit 62 C/D Road System (https://www.google.com/maps/@38.8766228,-77.2764798,3a,75y,101.15h,86.35t/data=!3m6!1e1!3m4!1sBeUdIoTQXlHNJ_5JMrqMxg!2e0!7i13312!8i6656).
2. I think a shaping point should be added between 72 and 73. The current line in the HB runs just north of the US 29/VA 124 intersection.
US 50:
1. Should be synced with I-495.
Both:
1. Should I-66, US 50, and the George Washington Pkwy all be synced with one point based on the I-66 "76" label? US 50 should probably keep a separate GWPkwy point though?
2. (DC only) I thought that the I-66 US50 label and the US 50 I-66 label should have been changed to US50_E and I-66_E respectively.
-
I found some further issues. Addressing these should finally take care of everything:
I-66:
1. I think 61 should be changed to 62A. The Metro Access is a part of the Exit 62 C/D Road System (https://www.google.com/maps/@38.8766228,-77.2764798,3a,75y,101.15h,86.35t/data=!3m6!1e1!3m4!1sBeUdIoTQXlHNJ_5JMrqMxg!2e0!7i13312!8i6656).
2. I think a shaping point should be added between 72 and 73. The current line in the HB runs just north of the US 29/VA 124 intersection.
Since the toll lanes will have a direct exit to Vaden Dr, I renamed the 61 point to Vaden Dr, eliminating the non-existent exit designation. The ramps to/from I-66 could be viewed as being a partial interchange with Vaden Rd as-is
US 50:
1. Should be synced with I-495.
Both:
1. Should I-66, US 50, and the George Washington Pkwy all be synced with one point based on the I-66 "76" label? US 50 should probably keep a separate GWPkwy point though?
2. (DC only) I thought that the I-66 US50 label and the US 50 I-66 label should have been changed to US50_E and I-66_E respectively.
I actually think the 76 point should be moved into DC where US 50 comes/goes from I-66 on the Potomac River Br. This makes sense because the way it is in TM is that I-66 and US 50 are concurrent in Virginia which is not true (confirmed via traffic logs that the US 50 ramps there are in fact US 50 and not ramps).
I took no action with these items other than syncing US 50 and I-495
-
New error has popped up on I-66's file.
va.i066;53;;;DUPLICATE_LABEL;
72 http://www.openstreetmap.org/?lat=38.896043&lon=-77.098875
+53 http://www.openstreetmap.org/?lat=38.898063&lon=-77.091091
73 http://www.openstreetmap.org/?lat=38.896644&lon=-77.082524
Looks like an 'x' was forgotten to be added before the number causing this issue.
However, this error is causing list file issues, as '53' is a currently in-use point, so it should be fixed asap.
-
fixed and submitted
-
Resurrecting this thread because I actually now agree with mapmikey on the I-66 "76" point.
In my opinion, the "76" point should just be put under VA/DC. VA/DC on both I-66 and US 50 should be moved to the southeast slightly. We can debate on whether there should be a GWPkwy point synced with I-66, but the I-66(76) point on US 50 should be put under VA/DC as well.
In DC, I would still change US50 on I-66 to US50_E and I-66 on US 50 to I-66_E.
In the meantime for US 50:
1. NBraSt should be BraSt_N. SBraSt should be BraSt_S. (in Winchester)
2. FairOak should be changed to FairOaks. FairOaksMall IMO would go against the three-word rule since Mall is not a road abbreviation.
3. FairPkDr should be FaiParkDr.
4. CHRd should be CouHouRd since Court House Rd is two words here.
5. QueenSt should be QueSt.
Also for VA 110, is PenAccRd correct?
-
Also for VA 110, is PenAccRd correct?
Much to my surprise, it's actually not. I'm guessing Mike got that from OSM because that's what OSM calls it. But both Arlington County GIS (https://gis.arlingtonva.us/Html5Viewer/Index.html?viewer=ACMaps.HTML5) and the Pentagon's Transportation Management Plan (https://www.ncpc.gov/files/projects/Pentagon_Reservation_Master_Plan_Update_and_Transportation_Management_Plan_Transportaton_Management_Plan_MP174_May2015.pdf) call it "Connector Road".
Street blades on each end call it "South Parking Conn.". From my own time at the Pentagon, neither name is really in general use. Given the official sources mentioned above, I'd use ConRd.
-
This predates my involvement in TM. Oddly there is no sign on VA 110 itself telling you what the offramp is for.
I will change this to ConRd when I do the VA NMP changes...
-
Resurrecting this thread because I actually now agree with mapmikey on the I-66 "76" point.
In my opinion, the "76" point should just be put under VA/DC. VA/DC on both I-66 and US 50 should be moved to the southeast slightly. We can debate on whether there should be a GWPkwy point synced with I-66, but the I-66(76) point on US 50 should be put under VA/DC as well.
In DC, I would still change US50 on I-66 to US50_E and I-66 on US 50 to I-66_E.
In the meantime for US 50:
1. NBraSt should be BraSt_N. SBraSt should be BraSt_S. (in Winchester)
2. FairOak should be changed to FairOaks. FairOaksMall IMO would go against the three-word rule since Mall is not a road abbreviation.
3. FairPkDr should be FaiParkDr.
4. CHRd should be CouHouRd since Court House Rd is two words here.
5. QueenSt should be QueSt.
Also for VA 110, is PenAccRd correct?
I made all the changes. Here is what I did with US 50/I-66 at the Potomac River:
US 50: Made 76 an alt name for the VA/DC point
US 50: Deleted the I-66(76) point
I-66: Moved the 76 point to sync with the GW Pkwy point, made 76 an alt name for it
In DC, I added a point on both I-66 and US 50 where they diverge before reaching Virginia
While making the DC/VA line point more accurate per the post above, I also made the US 50 and I-66 coordinates slightly different so that there would be no concurrency at the boundary line. This will almost certainly create a FP NMP
-
While making the DC/VA line point more accurate per the post above, I also made the US 50 and I-66 coordinates slightly different so that there would be no concurrency at the boundary line. This will almost certainly create a FP NMP
Looking at the updated list, you are correct on that.
-
https://github.com/TravelMapping/HighwayData/pull/3596
The NMPs being added to nmpfps.log should finalize this thread.