AARoads Forum

Please login or register.

Login with username, password and session length

Author Topic: MO errors  (Read 3288 times)

ntallyn

  • *
  • Offline Offline

  • Posts: 16
  • Last Login: March 30, 2016, 06:55:18 PM
MO errors
« 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.

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.
Logged

ntallyn

  • *
  • Offline Offline

  • Posts: 16
  • Last Login: March 30, 2016, 06:55:18 PM
MO US136
« Reply #1 on: January 01, 2016, 05:57:10 PM »

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

ntallyn

  • *
  • Offline Offline

  • Posts: 16
  • Last Login: March 30, 2016, 06:55:18 PM
MO MO15, MO151, AND MO156
« Reply #2 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.

Also, point OldUS36 on MO151 should probably be renamed US36Bus.
Logged

oscar

  • *
  • Offline Offline

  • Posts: 8794
  • Age: 65
  • Location: Arlington, VA
  • Last Login: Today at 09:31:24 AM
    • my Hot Springs and Highways pages
Re: MO US36BusCla
« Reply #3 on: January 01, 2016, 06:18:27 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.
Logged
my Hot Springs and Highways pages, with links to my roads sites:
http://www.alaskaroads.com/home.html

rickmastfan67

  • The Invisible One
  • *
  • *
  • Offline Offline

  • Posts: 2941
  • I want I-67 in PA!!!!

  • Age: 36
  • Location: Pittsburgh, Pa, USA
  • Last Login: Today at 08:30:43 AM
Re: MO US36BusCla
« Reply #4 on: January 01, 2016, 08:26:15 PM »

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.

Highway63

  • *
  • Offline Offline

  • Posts: 143
  • Location: Iowa
  • Last Login: July 27, 2021, 09:36:00 PM
    • Iowa Highway Ends
Re: MO MO15, MO151, AND MO156
« Reply #5 on: January 25, 2016, 09:26:45 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.

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.

mapcat

  • *
  • Offline Offline

  • Posts: 80
  • Last Login: June 19, 2019, 05:35:22 PM
Re: MO MO15, MO151, AND MO156
« Reply #6 on: January 25, 2016, 09:28:59 PM »

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?
Logged

Highway63

  • *
  • Offline Offline

  • Posts: 143
  • Location: Iowa
  • Last Login: July 27, 2021, 09:36:00 PM
    • Iowa Highway Ends
Re: MO errors
« Reply #7 on: January 25, 2016, 10:15:16 PM »

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?
« Last Edit: January 25, 2016, 10:18:46 PM by Jeff Morrison »
Logged

oscar

  • *
  • Offline Offline

  • Posts: 8794
  • Age: 65
  • Location: Arlington, VA
  • Last Login: Today at 09:31:24 AM
    • my Hot Springs and Highways pages
Re: MO errors
« Reply #8 on: January 25, 2016, 10:30:08 PM »

See also the thread elsewhere on the forum for the recent relocation of US 50 in the Loose Creek MO area.
Logged
my Hot Springs and Highways pages, with links to my roads sites:
http://www.alaskaroads.com/home.html

mapcat

  • *
  • Offline Offline

  • Posts: 80
  • Last Login: June 19, 2019, 05:35:22 PM
Re: MO errors
« Reply #9 on: January 25, 2016, 10:59:27 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.
Logged

 


Opinions expressed here on belong solely to the poster and do not represent or reflect the opinions or beliefs of AARoads, its creators and/or associates.