WI: Route point concerns and exit numbers

[Highway63]

The above issues should be resolved shortly. Those related to US 10 and WI 120 were known because those routes were part of the last batch I sent this week.

[Markkos1992]

One more minor thing for US 53 in Superior:  US2Trk should be US2Trk_W.

I do not think I can fully justify changing the I-535 label.  I think that I-535/35 may be better than just plain I-535, but I have no problem with you leaving it alone since I-535 basically ends there now.

[Highway63]

Since US 53 does not intersect US 2 Truck twice, I believe US2Trk is the correct name on 53.

This does bring up a related issue, though: On US 2, the point US53 should probably be US53/2Trk. I say "probably" because the east end of the truck route is poorly signed. There are no signs at the 2/53 intersection, the one from US 53 points to generic "Truck Route", and the first one we see is an old unbannered 2 shield.

However, the rest of the route is well-signed at surface streets.

[Markkos1992]

Since US 53 does not intersect US 2 Truck twice, I believe US2Trk is the correct name on 53.

This does bring up a related issue, though: On US 2, the point US53 should probably be US53/2Trk. I say "probably" because the east end of the truck route is poorly signed. There are no signs at the 2/53 intersection, the one from US 53 points to generic "Truck Route", and the first one we see is an old unbannered 2 shield.

However, the rest of the route is well-signed at surface streets.

I would stick with US53_N for US 2, but this is mainly out of my PA bias where truck routes are not worth putting in labels where possible because they get changed so often.

[terminal_moraine]

The following appear to be broken concurrencies in WI (my apologies if these have already been noted/are being remediated):

The US10 concurrency with I-39/US51 between exits 163 and 158 is broken (appears to be missing exit 161 point)

The WI27 concurrency with US14 and US61 between Viroqua and Westby is broken (appears to be missing points for CRY_Ver and the north end of the concurrency)


The current total mileage in WI is 11768.3, which is ~42 miles higher than it was before May.  I don't think the above broken concurrencies are enough to account for the difference, but I haven't located any others yet.

[rickmastfan67]

The US10 concurrency with I-39/US51 between exits 163 and 158 is broken (appears to be missing exit 161 point)

The issue here seems to be two points sharing the same coordinates, 161(39) & +X29a, in US-10's file.

Code: [Select]

163(39) http://www.openstreetmap.org/?lat=44.569895&lon=-89.597948
161(39) http://www.openstreetmap.org/?lat=44.547774&lon=-89.553420
+X29a http://www.openstreetmap.org/?lat=44.547774&lon=-89.553420
159(39) http://www.openstreetmap.org/?lat=44.540630&lon=-89.544067
The solution here is to correct 161(39) in US-10's file to the following:

Code: [Select]

161(39) http://www.openstreetmap.org/?lat=44.548277&lon=-89.576125

[rickmastfan67]

US 10:
20.  CRG_Por and CRO_Por should be marked as closed. (also affects WI 34)

Are we sure they should be marked as closed?  Seems to me that was a brand new expressway bypass built there and there was never any intersection between those two routes and US-10 (except on the old road).

CR O (10/08)
CR G (10/08)

Thus, I think they should both be removed instead.

[Markkos1992]

Looking at the current Datacheck list, there seem to be concurrencies broken on I-39, I-94, and US 53 somewhere.  I did not look deeper at this than looking at the list.

wi.i039   +X11   HIDDEN_JUNCTION   3   wi.i039;+X11
wi.i094   *325   VISIBLE_HIDDEN_COLOC   wi.i041@+325(94)   wi.i094;*325
wi.us053   +X08   HIDDEN_JUNCTION   3   wi.us053;+X08

[Highway63]

I-39 point: Concurrent with US 51, beats the snot out of me. Their files are identical there.
I-94 point: I mislabeled the closure of Exit 325 on the I-41 list (+ instead of *).
US 53 point: Missing CRS point on WI 121.

[Markkos1992]

I-39 point: Concurrent with US 51, beats the snot out of me. Their files are identical there.

Looking in the area, it looks like some shaping points from US 51's file needs to be added to I-39.

[bejacob]

Broken concurrency in Manitowoc between WI42Bus and the two US routes in town. The issue appears to be with the waypoint on WI42Bus labeled US10_E. The concurrency with US151 between 21st St and the intersection(s) with US10 is broken as is the concurrency with US10 between Washington St and Waldo Blvd. The fix may be as simple as moving the waypoint on WI42Bus to match the point in use at the intersection of US10 and US151 on both US routes.

EDIT:  Merged into general WI thread that is still open as it may be related to that.

[bejacob]

Please don't edit my posts. I purposely did not add to this existing thread because I did not want this post to get lost among all the other meaningless "point concern" posts that have become so prevalent in the last year.

I titled my post "broken concurrency" because that's what it is. I was not concerned about any of the points or what they are named. I care that a concurrency is broken.

While I appreciate the good intentions, I kindly request any future posts I make not be merged into another topic unless they specifically duplicate something previously posted.

I rarely post anything on this forum for a couple reasons. 1) If someone else doesn't agree with my POV, I get verbally abused and essentially get told that being a user and not a contributor makes me a second class user of this site, and 2) because other users think they know better than me about how my posts should be titled and where they belong. I've gotten to the point now that about the only time I post anything is when I discover an error that needs to be corrected. That was the core of my prior post, not some vague concern about points or exit numbers.

I love the Travel Mapping site and will continue to update my maps and use those maps when travel planning. I'm less fond of the forum side of the site due to how I am treated by a handful of users who seem to think that because I infrequently post, that must not know what I'm doing or that my contributions are not as relevant as those who post multiple times a day.

[Highway63]

I want to apologize if my preference for having consolidated or semi-consolidated state threads for minor issues felt like an infringement on trying to get certain things pointed out.

I think the issue with WI 42 Business can be solved by using the point common to US 10/151. It had been at the west intersection of a one-way pair.

[Markkos1992]

I want to apologize if my preference for having consolidated or semi-consolidated state threads for minor issues felt like an infringement on trying to get certain things pointed out.

I think the issue with WI 42 Business can be solved by using the point common to US 10/151. It had been at the west intersection of a one-way pair.

You are good.  This issue is why I have started to consolidate these issues more often myself personally when possible.

[Markkos1992]

While working on the other WI Updates, I think I was able to straighten out I-39 to fix the broken concurrencies.

I also straightened out I-41, US 41, and WI 121 based on Highway63's posts above.

Anyway, I am going to consider this thread solved so that things can now be posted separately.

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

EDIT (11-11-2021):  Found one more concurrency to fix on I-39/US 51 (https://github.com/Markkos1992/HighwayData/commit/039841b5226b945ba8e75bb35922f733c6402ce9).