Travel Mapping
Highway Data Discussion => Updates to Highway Data => Topic started by: mapcat on March 16, 2025, 03:47:04 pm
-
The points are pretty far apart, so the automated check didn't detect it.
-
The points are pretty far apart, so the automated check didn't detect it.
CA 178 never connected to Badwater Rd. It ends at the former national park boundary (the boundary has since moved a few miles east), with the coordinates from my handheld GPS receiver at the End CA 178 sign. However, usanp includes as part of Badwater Rd. the part of Jubilee Pass Rd. that fills in (imperfectly) the gap between Badwater and CA 178.
cl94 is now managing CA, so I'll let him make the fix.
-
I'll make the fix this afternoon. CA 178 has the correct endpoint (matches the postmile log). There will be some more CA cleanup coming in the next few weeks.
-
CA 178 never connected to Badwater Rd. It ends at the former national park boundary (the boundary has since moved a few miles east), with the coordinates from my handheld GPS receiver at the End CA 178 sign. However, usanp includes as part of Badwater Rd. the part of Jubilee Pass Rd. that fills in (imperfectly) the gap between Badwater and CA 178.
According to this (https://www.nps.gov/deva/learn/news/jubilee-pass-jubilation.htm), what OSM calls Jubilee Pass Rd is part of Badwater Rd.
-
Done. https://github.com/TravelMapping/HighwayData/pull/8257