Travel Mapping

Highway Data Discussion => Updates to Highway Data => Topic started by: rickmastfan67 on July 13, 2025, 01:58:01 pm

Title: CA: I-580 exit number issues
Post by: rickmastfan67 on July 13, 2025, 01:58:01 pm

missing? -> shaping point (between 2B & 7A) - while it doesn't go out of tolerance here, just adding a single shaping point here on the long bridge could add significance mileage to the route.
7B -> 7 (https://maps.app.goo.gl/PrtshRhmMPNxZybw6)
7C -> 7B (https://maps.app.goo.gl/oPH3fGi83zL8go9JA)
13(80) -> 13 (https://maps.app.goo.gl/SMEtT5VfNc17auNz7) - while you'd probably not want to split up this mess here, with I-580 having it's own exit here before the merge with I-80, I think we can justify dropping the '(80)' part, as this 13 is based on I-580's mileage.
missing -> 22A (https://maps.app.goo.gl/eVhK49TRCqThnzjs5) for Lakeshore Ave (WB only)
22A (current) -> 22B (https://maps.app.goo.gl/bvzhimPnqg7o639p9)
23A -> 24A (https://maps.app.goo.gl/zoodhgfQxz51RX56A) (best solution to not have to move current 24)
31A -> 31 (https://maps.app.goo.gl/iVk1epcEer45SxK9A) - Since we're using '30' WB for the '31A' going EB, we should use the WB number here too.
31B -> 32A (https://maps.app.goo.gl/TqDR6JQbFbfKa8EBA)
missing -> 76A (https://maps.app.goo.gl/XmwGDt8jmccePgDr7) - If we have a full separate point for 'Exit 1' on CA-132, we should have the other part of Exit 76 on I-580 here.

Title: Re: CA: I-580 exit number issues
Post by: cl94 on July 26, 2025, 07:10:56 pm

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

Sorry about the delay here, unusually hectic few weeks.