Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: yakra on February 16, 2022, 10:28:05 am
-
usaif_con.csv:
usaif;I-265;Fut;Louisville, KY;in.i265futlou
usaif;I-265;Fut;Louisville, KY;ky.i265futlou
->
usaif;I-265;Fut;Louisville, KY;ky.i265futlou,in.i265futlou
We have a DE/NJ/PA I-295 (https://travelmapping.net/hb/showroute.php?r=nj.i295&cr) situation here where one of the routes gets internally flipped around to display the ConnectedRoute in the HB.
So it doesn't really matter what order the roots are listed in. I like KY first as there's more mileage there, making the I-295/I-295Fut complex more N-S overall.
KY I-265FutLou:
Recommend moving exit 37 hereish (http://www.openstreetmap.org/?lat=38.322771&lon=-85.618373). This is one of those places a graph connection really isn't appropriate.
It's good to see America actually building a tunnel for a change.
-
Should this be merged with the existing I-265 thread (or will I confuse mapcat even more)?
-
Didn't think to check for an existing thread.
If anyone thinks it's appropriate, go for it.
Edit: Let's keep this topic separate though. I'm about to link to it from GitHub (https://github.com/TravelMapping/DataProcessing/issues/492), and merging would break the link.
-
KY I-265FutLou:
Recommend moving exit 37 hereish (http://www.openstreetmap.org/?lat=38.322771&lon=-85.618373). This is one of those places a graph connection really isn't appropriate.
That's silly. It's a pretty simple interchange between two roads. The point should be where the centerlines cross.
-
I am in agreement with keeping it separate mainly because this is a simple file change. If Indiana and Kentucky would just sign I-265 across the Ohio River already.... (yes I am sure that someone will do it)
KY I-265FutLou:
Recommend moving exit 37 hereish (http://www.openstreetmap.org/?lat=38.322771&lon=-85.618373). This is one of those places a graph connection really isn't appropriate.
That's silly. It's a pretty simple interchange between two roads. The point should be where the centerlines cross.
https://travelmapping.net/devel/manual/points.php#trumpet
Trumpet interchanges: Where the access road centerline crosses the freeway centerline. Double trumpet interchanges get separate points at each trumpet.
Yes, US 42 actually has an at-grade intersection with the ramps to/from I-265/KY 841 SB, but that rule still applies. That is why you see very few graph connections on roads such as the PA Turnpike, the New York State Thruway, etc.
-
Or, same principle but not specifically referencing a trumpet:
There are common exceptions to positioning at centerline crossings, such as interchanges where ramps connect nearby, non-intersecting highways, or where a short access road connects a road to another with a trumpet or similar interchange. In these cases, the waypoints for the same interchange on the separate highways cannot be at the same coordinates. Instead, the waypoints should be where the connecting ramps or access road interchange with each highway.
Emphasis in original.
-
Yeah this looks like a situation best treated the same as a typical turnpike trumpet. The points are best placed at the location you would have clinched the road up to if you are using them. This means no graph connection but oh well.
-
https://github.com/TravelMapping/HighwayData/pull/5624
Point moved to where centerlines cross.