Non-Road Boards > Travel Mapping

MO errors

(1/2) > >>

ntallyn:
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.

ntallyn:
US136 is missing a point at MOsO in Mercer County. This also would result in a renaming (hiding?) of MOsO in Atchison County.

ntallyn:
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.

oscar:

--- 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.
--- End quote ---

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.

rickmastfan67:
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.

Navigation

[0] Message Index

[#] Next page