« previous next »
Pages: [1]

Author Topic: OK: OK20 issues  (Read 1133 times)

0 Members and 1 Guest are viewing this topic.

Offline Duke87

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 959
  • Last Login:Yesterday at 09:06:02 pm
OK: OK20 issues
« 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
Logged

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:April 07, 2024, 11:18:57 pm
  • I like C++
Re: OK: OK20 issues
« Reply #1 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
Logged
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca
Pages: [1]
« previous next »