WA: US395 / WA20 multiplex broken

[yakra]

PeaRd is in US395 with no corresponding point on WA20.
MeySt is in US395 with no corresponding point on WA20.
WilLakeRd is in US395 with no corresponding point on WA20.

[compdude787]

Oh yeah, I'd noticed that there was an issue with this when I was inputting all my travels over the years into my list file a few months ago, but I'd since forgotten about it. Thanks for reminding me! There's also another place where this is an issue: the WA 20/ WA 9 concurrency in Sedro-Wooley. So I'm going to have to fix these and perhaps check through all of WA's multiplexes and make sure there aren't any other problems.

EDIT: After looking on the highway browser some more, I've also noticed some other issues. Will post in another thread.

[mapcat]

So I'm going to have to fix these and perhaps check through all of WA's multiplexes and make sure there aren't any other problems.

You know about using the HDX to find broken concurrencies, right? Saves a lot of time.

[compdude787]

So I'm going to have to fix these and perhaps check through all of WA's multiplexes and make sure there aren't any other problems.

You know about using the HDX to find broken concurrencies, right? Saves a lot of time.

No...

[mapcat]

http://tm.teresco.org/forum/index.php?topic=333.msg1739#msg1739

[compdude787]

Thanks!! Will put it to good use.

[compdude787]

Having looked at Washington state on the HDX, I noticed some other errors like this; see this thread: http://tm.teresco.org/forum/index.php?topic=1890.0

[yakra]

Having looked at Washington state on the HDX, I noticed some other errors like this; see this thread: http://tm.teresco.org/forum/index.php?topic=1890.0

Marking as solved, since the errors I posted in the OP are also listed in the new thread.

[compdude787]

Pull-requested: https://github.com/TravelMapping/HighwayData/pull/1105