Author Topic: WA Cleanup of broken multiplexes, NMPs, etc.  (Read 4155 times)

0 Members and 1 Guest are viewing this topic.

Offline compdude787

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 298
  • Gender: Male
  • Last Login:February 09, 2024, 02:19:30 am
WA Cleanup of broken multiplexes, NMPs, etc.
« on: January 13, 2017, 02:19:03 am »
Having seen yakra's thread about the WA 20/US 395 multiplex being broken, I went thru the HDX and found lots of other errors of this sort, as well as quite a few near-miss points (NMPs). So, just so I have an idea of what I need to fix, I'm compiling a list of all the broken multiplexes and NMPs that need fixing:

Broken Multiplexes:
  • WA 9/WA 20: WA 20 is missing HarSt waypoint
  • WA 215/US 97BusOka: WA 215 is missing the following waypoints: OakSt, OmakAve
  • WA 20/US 395:WA 20 is missing the following waypoints: PeaRd, MeySt, WilLakeRd
  • WA 171/I-90BLMos: I-90BL is missing the MarDr waypoint, WA 171 is missing the following waypoints: AldSt, WA171_E

NMPs
  • I-90BLMos@I-90_E and I-90(179)/WA17
  • WA17@PioWay and I-90BLMos@WA17
  • I-82@I-90 and I-90(110)/US97
  • US97@I-82(31) and I-82(31)/US12
  • WA823@I-82 and I-82(30)/US97
  • US2@I-5 and I-5@194
  • I-5@133 and I-705@I-5&WA7@I-5/705
  • WA303@WA3_S and WA3@KitMallBlvd
  • I-5@154 and I-405@I-5(154)&WA518@I-5
  • WA599@I-5 and I-5@156
  • I-5@104 and US101@I-5

Hopefully, that's all...
« Last Edit: February 03, 2017, 11:12:49 pm by compdude787 »

Offline compdude787

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 298
  • Gender: Male
  • Last Login:February 09, 2024, 02:19:30 am
Re: WA Cleanup of broken multiplexes, NMPs, etc.
« Reply #1 on: February 05, 2017, 01:45:18 am »
Pull request made for this: https://github.com/TravelMapping/HighwayData/pull/1105

I also corrected border NMPs (I-5 at the OR/WA border, US 730 at the OR/WA border, and US 395 at the US/Canada border) using the logfile.

Offline compdude787

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 298
  • Gender: Male
  • Last Login:February 09, 2024, 02:19:30 am
Re: WA Cleanup of broken multiplexes, NMPs, etc.
« Reply #2 on: February 05, 2017, 03:37:10 pm »
Found more NMPs! Woohoo! :D

  • I-5@48 and I-5BLCas@I-5_S
  • I-5(49)/WA411/WA504 and I-5BLCas@I-5_N
  • I-5@59 and WA506@I-5(59)
  • I-90(279)/US2/US395 and US195@I-90

This is not an NMP but the waypoint for I-5(1C)/WA501 is not positioned on the center of the interchange. Sloppiness much? Also, Exits 7A and B are missing, so I'll need to add them. EDIT: I'll probably not add 7B since it's so close to 7, but I'll add 7A.
« Last Edit: February 05, 2017, 04:20:25 pm by compdude787 »

Offline compdude787

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 298
  • Gender: Male
  • Last Login:February 09, 2024, 02:19:30 am
Re: WA Cleanup of broken multiplexes, NMPs, etc.
« Reply #3 on: February 05, 2017, 04:41:36 pm »
Another day, another pull request: https://github.com/TravelMapping/HighwayData/pull/1110

Also, out of curiosity, how come the waypoints along the interstates in Washington seemed to be positioned a bit off? What I mean is that they seem to be, in many cases, just to the east of what they should be. I was of the understanding that the points should be positioned in the median of the freeway, and in many cases they are not. Is this something I should be concerned about?

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1627
  • Last Login:Today at 04:37:32 pm
Re: WA Cleanup of broken multiplexes, NMPs, etc.
« Reply #4 on: February 05, 2017, 05:53:13 pm »
Also, out of curiosity, how come the waypoints along the interstates in Washington seemed to be positioned a bit off? What I mean is that they seem to be, in many cases, just to the east of what they should be. I was of the understanding that the points should be positioned in the median of the freeway, and in many cases they are not. Is this something I should be concerned about?

Not sure how long ago these were drafted, but in defense of whoever created the files, there are a few possibilities (and more than I've thought of, I'm sure):
  • The lat/long positions may have changed on the maps
  • The roads may have moved due to reconstruction
  • They were drafted using a different basemap no longer available to us
"Point drift" is a fairly common issue sitewide. I'm not sure what contributes to it, but whenever you see users referring to their cleanup of this system or that, it's one of the issues we're dealing with.

Re your decision to add Exit 7A to I-5, that one certainly makes sense, but if it were up to me, I'd squeeze 7B in there as well. The interchange is separate from both Exit 7 and Exit 7A.
« Last Edit: February 05, 2017, 05:55:35 pm by mapcat »
Clinched:

Offline compdude787

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 298
  • Gender: Male
  • Last Login:February 09, 2024, 02:19:30 am
Re: WA Cleanup of broken multiplexes, NMPs, etc.
« Reply #5 on: February 05, 2017, 07:16:10 pm »
Not sure how long ago these were drafted, but in defense of whoever created the files, there are a few possibilities (and more than I've thought of, I'm sure):
  • The lat/long positions may have changed on the maps
  • The roads may have moved due to reconstruction
  • They were drafted using a different basemap no longer available to us
"Point drift" is a fairly common issue sitewide. I'm not sure what contributes to it, but whenever you see users referring to their cleanup of this system or that, it's one of the issues we're dealing with.

Probably the third one was what happened. Fixing this is a pretty low priority given the amount of work it's going to take.

Re your decision to add Exit 7A to I-5, that one certainly makes sense, but if it were up to me, I'd squeeze 7B in there as well. The interchange is separate from both Exit 7 and Exit 7A.


Okay, I just added it to my pull request.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:February 13, 2024, 07:19:36 pm
  • I like C++
Re: WA Cleanup of broken multiplexes, NMPs, etc.
« Reply #6 on: February 05, 2017, 11:25:23 pm »
Quote
They were drafted using a different basemap no longer available to us
my suspicion as well.
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline Bickendan

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 543
  • Last Login:March 26, 2024, 08:55:56 pm
Re: WA Cleanup of broken multiplexes, NMPs, etc.
« Reply #7 on: February 06, 2017, 01:00:05 am »
Quote
They were drafted using a different basemap no longer available to us
my suspicion as well.
Washington never got updated from the old Terraserver coordinates Tim drafted when he first started the entire project, apparently.

Offline Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2732
  • Last Login:Today at 02:09:10 pm
Re: WA Cleanup of broken multiplexes, NMPs, etc.
« Reply #8 on: February 06, 2017, 09:58:16 am »
Yes, some of the Interstate highway files have been around a very long time.  I think it remains a low priority to go through and update those old routes to our current naming and shaping standards, improve accuracy, and reduce the chances we are inadvertently using an inappropriate derived work from a copyrighted source.

Offline compdude787

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 298
  • Gender: Male
  • Last Login:February 09, 2024, 02:19:30 am
Re: WA Cleanup of broken multiplexes, NMPs, etc.
« Reply #9 on: February 07, 2017, 03:09:33 pm »
Quote
They were drafted using a different basemap no longer available to us
my suspicion as well.
Washington never got updated from the old Terraserver coordinates Tim drafted when he first started the entire project, apparently.

Apparently not...

Someday I'll fix them. It's a higher priority for me to fix the waypoints on state routes first, so that there aren't any waypoints on a side street where they could be better placed on an arterial nearby. This issue has always bothered me.