CA: Broken concurrency in Southern Calif with CA/usaush routes

[bejacob]

Noticed two broken concurrencies in southern CA.

One is with CA111Pal and US99HisInd. The segment on CA111Pal between PalmSprLim and CA111Bus_S should be concurrent with US99HisInd. It may be as simple as adding adding a waypoint on US99His at PalmSprLim and removing the hidden shaping point there or changing the current hidden waypoint to a visible one (or something like that).

The other is with CA66 and US66HisAzu. Not sure which waypoint is causing the issue (PepAve at one end or MtVerAve/CA66_E at the other). Guessing one or the other is a NMP. Whatever the cause, the 2.29 mile segment should be concurrent.

[cockroachking]

The other is with CA66 and US66HisAzu. Not sure which waypoint is causing the issue (PepAve at one end or MtVerAve/CA66_E at the other). Guessing one or the other is a NMP. Whatever the cause, the 2.29 mile segment should be concurrent.

Worth noting that between Euclid Ave and Vineyard Ave further west, there is also a broken concurrency with these two routes. The issue with this one seems to be the fact that CA66 has a point at Campus Ave while US66HisAzu does not.

[oscar]

All of this seems to be that usaush routes in CA (which were drafted while I was in the middle of overhauling usaca and other routes) still need to synch up with changes made to usaca as that system was readied for activation. There might be more such changes elsewhere in southern California, not limited to NMPs.

[bejacob]

All of this seems to be that usaush routes in CA (which were drafted while I was in the middle of overhauling usaca and other routes) still need to synch up with changes made to usaca as that system was readied for activation. There might be more such changes elsewhere in southern California, not limited to NMPs.

I suspected that might be the case. I noticed the two I mentioned having just driven them this past weekend.