Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: michih on January 02, 2020, 06:27:55 am

Title: OR: data errors
Post by: michih on January 02, 2020, 06:27:55 am
I had a look on the open issues for active systems: http://travelmapping.net/devel/datacheck.php?rg=OR

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 (https://github.com/TravelMapping/HighwayData/blob/master/datacheckfps.csv) this way, should I add the FP entries for you?
Title: Re: OR: data errors
Post by: Bickendan on January 02, 2020, 09:27:35 pm
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!
Title: Re: OR: data errors
Post by: michih on January 03, 2020, 03:22:24 am
And yes please on the FPs.

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

2 FP entries were already marked FP but unmatching (http://travelmapping.net/logs/unmatchedfps.log) due to label changes. I've removed all unmatching FP entries for OR.
Title: Re: OR: data errors
Post by: Bickendan on August 15, 2020, 10:53:18 pm
NMPs have been synced locally.
Title: Re: OR: data errors
Post by: Bickendan on August 26, 2020, 02:44:01 am
Submitted and live.