Highway Data Discussion > Solved Highway data updates

IN: I-69 Extension north to I-465

<< < (2/2)

mapcat:
Just got a call from INDOT with the needed exit number and the future of 37. https://github.com/TravelMapping/HighwayData/pull/7620

I-69 (Wheatonville) and I-69 Future (Indianapolis) are no more.

All routes with I-465 have been updated to include the new I-69 interchange.

Some .list problems will occur. Anyone who had been using the alternate waypoint labels "0" or "156" in their I-69 file will have inaccurate maps, since those labels are associated with exit numbers in the new file (inherited from I-69 (Wheatonville)).

rickmastfan67:
A few 'errors' now show up on the datacheck page in reference to this.


--- Code: ---in.in037 *MorSt VISIBLE_HIDDEN_COLOC in.i069@+X734056 in.in037;*MorSt;;;VISIBLE_HIDDEN_COLOC;in.i069@+X734056
in.in037 *WhiRd VISIBLE_HIDDEN_COLOC in.i069@+X589127 in.in037;*WhiRd;;;VISIBLE_HIDDEN_COLOC;in.i069@+X589127
--- End code ---

Pretty much, those 'former' intersections are visible in IN-37's file, but not I-69's.  I honestly think they should be visible in both routes, especially due to all the other 'closed' points both north & south of that that are shown in both routes.

mapcat:
https://github.com/TravelMapping/HighwayData/pull/7752

yakra:
I coded up a CLOSED_OPEN_COLOC once upon a time, but stashed it without ever committing & pushing.
Should probably finish that off.

Navigation

[0] Message Index

[*] Previous page