I'd suggest an additional point (US36_A?) at the eastbound entrance/exit ramps to/from US36 just west of MO151. It's used for eastbound access from/to US36 and MO151.
I don't recall the distance needed for a shaping point, but with the shortness of the route, a shaping point between EHazSt and US36_E might be worth looking at.
US136 is missing a point at MOsO in Mercer County. This also would result in a renaming (hiding?) of MOsO in Atchison County.
Should the point at MO151/156 be moved to the curve? And based on the signage, the point at MO15, MO151, and MO156 should probably be split. (Signage on MO15 makes it appear that MO151 continues to MO15, but signage on MO151 and 156 indicate that MO151 ends at MO156.)
MO 15: Move point to curve.
MO 151: Rename MO15/156 to MO156.
MO 156: Add point for new MO 15 intersection. Rename MO15/151 to MO151.
Also, point OldUS36 on MO151 should probably be renamed US36Bus.
Quote from: ntallyn on January 01, 2016, 05:50:02 PM
I don't recall the distance needed for a shaping point, but with the shortness of the route, a shaping point between EHazSt and US36_E might be worth looking at.
Actually, short routes (this one is less than two miles long) rarely need any shaping points at all. None of the non-endpoint waypoints already in that file are needed just for shaping (might be needed for other reasons), even with the route's short southward jog between EHazSt and US36_E.
ntallyn, since we're going to soon have a proper place for reporting errors to active routes, can you please just keep it all to one thread per state, or post in the "Highway Data Discussion" thread? Alex was kind enough to allow us to have a temporary section here on the forums, so we don't want to overdo it here. :) I've merged all three of your threads together for now into a mass MO thread.
Quote from: ntallyn on January 01, 2016, 05:50:02 PM
I'd suggest an additional point (US36_A?) at the eastbound entrance/exit ramps to/from US36 just west of MO151. It's used for eastbound access from/to US36 and MO151.
The real issue is that the old west end of Business 36 is blocked off, and Business 36 now goes up with MO 151. It's easy to say there should only be one point now, the interchange, for US 36/MO 151, and that's what I think I will do. It would not be fair to say eastbound and westbound traffic need different segments traveled to clinch. The point US36BusCla_W will become a closed intersection.
Quote from: ntallyn on January 01, 2016, 06:15:07 PM
Should the point at MO151/156 be moved to the curve? And based on the signage, the point at MO15, MO151, and MO156 should probably be split. (Signage on MO15 makes it appear that MO151 continues to MO15, but signage on MO151 and 156 indicate that MO151 ends at MO156.)
MO 15: Move point to curve.
MO 151: Rename MO15/156 to MO156.
MO 156: Add point for new MO 15 intersection. Rename MO15/151 to MO151.
I suppose this can be done.
Jeff, there are several more errors & updates in the states you manage reported as GitHub issues. Do you want to address them there, or would you prefer to get a list here?
Put them here for now, maybe? I do not want to have to log into five different places to find out what's needing to be updated.
EDIT: I found the GitHub page and will address those issues. I was aware of WI 74 being decommissioned except I didn't send an update because I was going to throw it in with the creation of IA 471, and that got delayed until Christmas and then spring. Am I going to need to create an account there too?
See also the thread elsewhere on the forum for the recent relocation of US 50 in the Loose Creek MO area (https://www.aaroads.com/forum/index.php?topic=16770.msg2104215#msg2104215).
Quote from: Jeff Morrison on January 25, 2016, 10:15:16 PM
Am I going to need to create an account there too?
Once the TravelMapping forum is up and running, I would expect most of the discussion will migrate there, although on our own we should probably continue to check AAroads to stay up to date with new construction, etc.