WI: I-41/I-43/I-94/I-894 Interchange

[yakra]

In addition, Iowa's total mileage, and my total there, both mysteriously increased by 13 miles this past week.

IA13/US151 broken
US18 missing a shaping point from IA27, exits 190 to 195
US18@CRS36 -> http://www.openstreetmap.org/?lat=43.105342&lon=-93.260786

[Markkos1992]

In addition, Iowa's total mileage, and my total there, both mysteriously increased by 13 miles this past week.

IA13/US151 broken
US18 missing a shaping point from IA27, exits 190 to 195
US18@CRS36 -> http://www.openstreetmap.org/?lat=43.105342&lon=-93.260786

I noted to Highway63 via PM that the US 18 point at 183 is not synced with the IA 27 point there at the moment.

[Highway63]

*sighs*

That's because I sent up a cleaned up IA 13 but not US 151 because I'm working on exit numbers for the latter, and sent IA 27 with exit numbers and cleaned-up waypoints but not US 18.

This is why I was reluctant to do this all along - things are going to break all over the place, at least temporarily, as I refine some files while working on others.

I'm going to send IA US 18 and 151, with exit numbers, and see if that clears it up.

Maybe I just have to do a complete file-dump of all I've got.

[SSOWorld]

*sighs*

That's because I sent up a cleaned up IA 13 but not US 151 because I'm working on exit numbers for the latter, and sent IA 27 with exit numbers and cleaned-up waypoints but not US 18.

This is why I was reluctant to do this all along - things are going to break all over the place, at least temporarily, as I refine some files while working on others.

I'm going to send IA US 18 and 151, with exit numbers, and see if that clears it up.

Maybe I just have to do a complete file-dump of all I've got.

or maybe start using GitHub directly as that is the source of truth and having uncontrolled copies increases risk of unsynchronized data.

This is the software engineer in me speaking...

[Markkos1992]

*sighs*

That's because I sent up a cleaned up IA 13 but not US 151 because I'm working on exit numbers for the latter, and sent IA 27 with exit numbers and cleaned-up waypoints but not US 18.

This is why I was reluctant to do this all along - things are going to break all over the place, at least temporarily, as I refine some files while working on others.

I'm going to send IA US 18 and 151, with exit numbers, and see if that clears it up.

Maybe I just have to do a complete file-dump of all I've got.

or maybe start using GitHub directly as that is the source of truth and having uncontrolled copies increases risk of unsynchronized data.

This is the software engineer in me speaking...

While I agree in the sense of uncontrolled copies, updating IA 13 but not US 151 in Github in this scenario would have still caused the same situation. 

[Jim]

I'm not planning to force anyone into using GitHub to be able to contribute to the project, but I do believe this is an excellent example of the benefits of having version control and working with branches.  You have a branch in which you're working through something substantial that will take some time like the exit numbers.  If you want to make an unrelated fix that you want to get in immediately, just switch back to the master branch, make that change and issue the pull request, and merge that commit into your branch to carry on.

Again, I don't plan to force it on anyone, but any time spent learning to work with version control pays back many times over down the road.

[Highway63]

Airport Fwy concurrencies are all broken.
I-43 & US45 are broken on the Rock Fwy.
Zoo Fwy concurrencies are broken S of Exit 39.

I don't understand why these are broken, at least not right away. I sent all of I-894, I-41, I-43, US 41 on April 25 and US 45 yesterday. I spent the better half of two days trying to make all the points work, including on the intersecting state routes.

Please do whatever you plan on doing to get the point syncs then let me know which files changed and where to get them. I will redo my other waypoint edits as necessary. US 18 will be getting some new stuff, for sure.

[yakra]

Merged.
Changed files can be seen at:
https://github.com/TravelMapping/HighwayData/pull/4799/files?file-filters%5B%5D=

Click on the "..." at the far right and there's a "View file" option.

These links though, will always point to the latest revisions:
https://github.com/TravelMapping/HighwayData/blob/master/hwy_data/WI/usai/wi.i041.wpt
https://github.com/TravelMapping/HighwayData/blob/master/hwy_data/WI/usai/wi.i894.wpt
https://github.com/TravelMapping/HighwayData/blob/master/hwy_data/WI/usaus/wi.us018.wpt
https://github.com/TravelMapping/HighwayData/blob/master/hwy_data/WI/usaus/wi.us041.wpt
https://github.com/TravelMapping/HighwayData/blob/master/hwy_data/WI/usaus/wi.us045.wpt

[Highway63]

I'm going to factor these in to my files. I will be sending new ones soon with exit numbers throughout each route as needed. The good news is, many of these coordinates match the ones I have in the new versions.

Heads up to all: There will be changes to I-41's exit numbers in Green Bay when I submit new files, based on Markkos1992's notes/examination of the area.

[Highway63]

Has anyone discovered any new issues in the Milwaukee area?

[yakra]

Has anyone discovered any new issues in the Milwaukee area?

A quick glance at "Color by Concurrencies" in Mapview looks OK.

Couple random things I did notice:
JanSt_N on WI59 should be moved south a bit.
WI164 could use shaping points at SkyAve and south of CRL. Adding one right there at that curve brings the route out of tolerance near the S terminus and begs for another shaper there too.

[Markkos1992]

Has anyone discovered any new issues in the Milwaukee area?

Any examining by me would probably only be when your latest updates are put in the HB.  This is mainly because I am working on finalizing further travel plans above anything else at the moment.