Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Duke87 on October 02, 2021, 12:19:17 pm

Title: OK: OK20 issues
Post by: Duke87 on October 02, 2021, 12:19:17 pm

- the concurrency with US169 is broken due to a coord mismatch at 136thSt
- 19thSt_S and 19thSt_N need to be combined into a single point, the road has been realigned slightly such that there is now only one intersection here

Title: Re: OK: OK20 issues
Post by: yakra on October 03, 2021, 04:31:22 pm

Quote from: Duke87 on October 02, 2021, 12:19:17 pm

- the concurrency with US169 is broken due to a coord mismatch at 136thSt

Fixed.

Quote from: Duke87 on October 02, 2021, 12:19:17 pm

- 19thSt_S and 19thSt_N need to be combined into a single point, the road has been realigned slightly such that there is now only one intersection here

Treating this as a newsworthy change, with points at 21stSt & 17thSt.

Elsewhere, +X02002 was placed on an old alignment that dates back to 1981. Not treating this as newsworthy; moved to modern alignment. An amusing example of how inaccurate/outdated Google's cartography was that we used in the early days. What was their source, maybe TIGER?

https://github.com/TravelMapping/HighwayData/pull/5178