OR: data errors

[michih]

I had a look on the open issues for active systems: http://travelmapping.net/devel/datacheck.php?rg=OR

• OR233's wp OR18/99W needs to get aligned to OR18 and OR99W wp coordinates.
• OR19's and OR207's AltCreRd wp need to be synced. Shouldn't the wp be renamed to AltCrkRd?
• OR99EBusSal's OR22 wp needs to be synced to OR22's OR99EBus wp.

The LABEL_SELFREF error of OR39 and the SHARP ANGLE errors of OR99 and OR207 are false positives.

Since you deliver by email and cannot edit datacheckfps.csv this way, should I add the FP entries for you?

[Bickendan]

Couldn't track these down when I did my pass but now I can fix them.

I personally agree with the AltCreRd -> AltCrkRd change, but Tim at the time did not want to use the common abbreviation and preferred the first three letters. If the point's not in use, I'll swap it.

And yes please on the FPs.

Ta!

[michih]

And yes please on the FPs.

https://github.com/TravelMapping/HighwayData/pull/3496/commits/ad3df76cffa017c177315a2fccef294d7507ccb7

2 FP entries were already marked FP but unmatching due to label changes. I've removed all unmatching FP entries for OR.

[Bickendan]

NMPs have been synced locally.

[Bickendan]

Submitted and live.