Author Topic: WI: I-43 Exit 131  (Read 471 times)

0 Members and 1 Guest are viewing this topic.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1840
  • Gender: Male
  • Last Login:April 17, 2024, 10:09:21 am
WI: I-43 Exit 131
« on: June 17, 2022, 12:17:36 am »
Just curious, but why are we missing this 'part time' exit Rowe Road?  Sure, it's only open for Golf events in the area, but we should have it.  StreetView got lucky and caught it being open!

Heck, it's even finally gotten exit signage & and number posted now!
https://goo.gl/maps/s4vdQ7q7CA62cZAj8

==

On a side note, TONs of exits could use re-centering along the entire route.  Some of the worst IMO, are 72A, 75, 76 (missing graph connection here with WI-190 IMO).

Offline Highway63

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 532
  • Gender: Female
  • Last Login:April 17, 2024, 11:00:05 pm
Re: WI: I-43 Exit 131
« Reply #1 on: June 28, 2022, 04:43:54 pm »
Just curious, but why are we missing this 'part time' exit Rowe Road?
Because it didn't exist until the mid-2010s, most likely.

Quote
On a side note, TONs of exits could use re-centering along the entire route.  Some of the worst IMO, are 72A, 75, 76 (missing graph connection here with WI-190 IMO).
I understand the issue, although I'm still befuddled by the existence of point drift. I fear creating giant messes with NMPs of not just intersecting routes but, because it's Wisconsin, inconsistency on multiplexes. This isn't to say I should completely ignore it.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4234
  • Last Login:April 07, 2024, 11:18:57 pm
  • I like C++
Re: WI: I-43 Exit 131
« Reply #2 on: June 29, 2022, 12:08:40 pm »
What I refer to as "point drift" was just an (early?) CHM thing -- I'd noticed coords getting out of sync on junctions/multiplexes, too much to be explained by collaborator failure to copy/paste coords from existing files.
Nowadays, that won't happen unintentionally -- any changes to .wpt files will be recorded as part of a commit in the HighwayData repo.

One might also use the term to refer to points gradually moving farther away from center lines as shown in OSM. This can be explained by the fact that we're now using more mature datasets, with more accurate geometry than what was available in the 2000s. Little to worry about here IMO; there's probably much less room left for improvement.
In the early days also, I think less attention was paid to point precision. ISTR that the earliest days of the (pre-Clinched Interstate Mapping) HB used TerraServer. Converting from that would yield much lower resolution coords in the first .ggm files.
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1975
  • Last Login:Yesterday at 11:52:55 am
Re: WI: I-43 Exit 131
« Reply #3 on: June 29, 2022, 06:44:40 pm »
 Pretty sure that points not syncing was deliberate in the early days of CHM. When I started drafting frae, none of the junctions were connected, which made routes changing which route they were concurrent with hard to draft. I went and tidied up fraa to have the points sync up where routes intersected, not just the ones where I needed it for the E roads. I was told not to do that.
« Last Edit: June 29, 2022, 06:49:00 pm by si404 »

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 1840
  • Gender: Male
  • Last Login:April 17, 2024, 10:09:21 am
Re: WI: I-43 Exit 131
« Reply #4 on: July 12, 2023, 12:29:11 am »
Looking back at this, the 131 point in I-43's file should be centered on the Rowe Road overpass, instead of at the gore point area.