MN Updates - #9455
Conversation
Added interchange at CR12 near Mankato
Added new and planned interchanges in Savage and Burnsville. LynnAve will no longer have a connection once construction is complete so have demoted that to a hidden point as it is still in-use.
Added 2 missing interchanges in St. Cloud.
Added new and under construction interchange locations and removed Keats Ave as it is no longer a primary point and is not in use.
Relocated onto the Pequot Lakes bypass
MN 263 removal and MN 371 Pequot Lakes bypass relocation
MN 263 turned back
MN 263 turned back
Added "50A" for a split interchange and separated the two "halves" of Exit 212.
Split US 169 and Washington Ave ramps.
Split US 169 and Washington Ave ramps on I-494 concurrency.
Slight recentering of I-494 point.
Added false positive on mn.grr due to distance.
Recentered Exit 132 (US 8)
Recentered I-35 interchange.
Added/renamed points to account for Exit 108 relocation.
Relabeled I-35E concurrency points and added point for relocated Exit 108.
Recentered US 10 interchange point due to recent interchange reconstruction.
Recentered CR 56 and CR 57 points along US 10 concurrency due to interchange construction.
Recentered I-694 point.
Various point relabelings and recenterings and added CR34 interchange near Perham.
Exit renumberings and slight relocation at MN 51.
Recentered CR8 and US52 points due to interchange construction.
Various interchange additions, point relabelings, and point removals.
A few point relabelings and new interchange at 65th St along US 52 concurrency.
Exit renumberings
|
At least one of the changes flagged by the check is a new point (the new 50A on I-94) that is confusing the checker. It seems to be thinking 50A was moved from a very distant location. I assume it's safe to ignore but something for me to look at. See the Issue mentioned above. |
| LynnAve http://www.openstreetmap.org/?lat=44.779063&lon=-93.336432 | ||
| DakAve http://www.openstreetmap.org/?lat=44.777997&lon=-93.359368 | ||
| QueAve http://www.openstreetmap.org/?lat=44.779025&lon=-93.344463 | ||
| +LynnAve http://www.openstreetmap.org/?lat=44.779082&lon=-93.336400 |
There was a problem hiding this comment.
Why mark this as hidden? Did you mean to mark it as closed instead?
There was a problem hiding this comment.
First time in the saddle in awhile. My original intention was to remove that point entirely since an impeding construction project will upgrade 13 to freeway and eliminate that access. But someone's using that point. In retrospect, should get an asterisk to be "closed".
| OsgAve http://www.openstreetmap.org/?lat=45.035807&lon=-92.807565 | ||
| MN95 +MN95_S http://www.openstreetmap.org/?lat=45.03602&lon=-92.79286 | ||
| MN/WI http://www.openstreetmap.org/?lat=45.04206&lon=-92.78487 | ||
| MN95 +MN95_S http://www.openstreetmap.org/?lat=45.036020&lon=-92.792860 |
There was a problem hiding this comment.
Change didn't get applied to MN-95's file. That's where one of the that error checks came from.
There was a problem hiding this comment.
Something got royally screwed up here. All of the changes I was making to 36 are WEST of Stillwater. There should have been NO change to the 95 point or the state line.
There was a problem hiding this comment.
Looks like this is another case of 'missing' zero's being added to the end of the coordinates.
@jteresco this is fine, but maybe somehow tweak the code that if the last digit in the coordinates is '0', that as long as the other 5 digits pass that it can be ignored?
There was a problem hiding this comment.
I assume it‘s likely easier to run a script adding missing digits once instead of implementing code to ignore. Just my 2ct. I‘m not able to implement the script.
There was a problem hiding this comment.
| MN95 +MN95_S http://www.openstreetmap.org/?lat=45.03602&lon=-92.79286 | ||
| MN/WI http://www.openstreetmap.org/?lat=45.04206&lon=-92.78487 | ||
| MN95 +MN95_S http://www.openstreetmap.org/?lat=45.036020&lon=-92.792860 | ||
| MN/WI http://www.openstreetmap.org/?lat=45.042060&lon=-92.784870 |
There was a problem hiding this comment.
This is the other error because it's now no longer snyced with WI-64. @Highway63
|
Will hold off on merging this until @ajfroggie can fix the one issue and Highway63 the other. |
| DakAve http://www.openstreetmap.org/?lat=44.777997&lon=-93.359368 | ||
| QueAve http://www.openstreetmap.org/?lat=44.779025&lon=-93.344463 | ||
| +LynnAve http://www.openstreetmap.org/?lat=44.779082&lon=-93.336400 | ||
| HunAve http://www.openstreetmap.org/?lat=44.778606&lon=-93.331009 |
There was a problem hiding this comment.
Has something changed here in the last 4 months? Apr '26 GSV shows no intersection or even construction work to install something here. https://maps.app.goo.gl/nsYQhkWQfUSZF5N97
There was a problem hiding this comment.
https://www.dot.state.mn.us/metro/projects/hwy13savageburnsville/index.html
Multiyear project to upgrade to freeway which will eliminate Lynn Ave access. Added the other points because those will ultimately be full/partial interchange locations.
|
So, I say this is all fine to pull in, once the 'LynnAve' label in MN-13 is changed from a '+' to a '*'. @ajfroggie can you make that fix very quickly here? |
4 participants
A series of point relabelings, a few point removals, new interchanges, and a couple relocations.