Author Topic: MN/ON: Border point resync needed  (Read 9712 times)

0 Members and 1 Guest are viewing this topic.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 2064
  • Gender: Male
  • Last Login:Yesterday at 11:42:03 pm
MN/ON: Border point resync needed
« on: June 11, 2017, 09:06:23 am »
Along MN/ON-61, it seems we have the border point put in incorrectly.  Both OSM & Google agree on the location between the US & Canada here.  There's also currently a NMP error here as well, so, it's a perfect chance to get the correct location in place for both routes.
Here's the URL I just put into ON-61's file to correct the location: http://www.openstreetmap.org/?lat=48.001440&lon=-89.585172
« Last Edit: June 11, 2017, 10:15:43 am by rickmastfan67 »

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 2064
  • Gender: Male
  • Last Login:Yesterday at 11:42:03 pm
Re: MN/ON: Border point resync needed
« Reply #1 on: June 12, 2017, 07:50:26 am »
Add the US-53/71 & ON-71 border crossing as well to that list.  Both Google & OSM agree on the location of the border there, and where we have it is south of the correct location.  There's also another NMP error here as well for all 3 routes, so, it's a perfect chance to get the correct location in place.

I would recommend the following location for this one: http://www.openstreetmap.org/?lat=48.607792&lon=-93.401487

I've already applied the fix to ON-71 pending a merge.

Offline froggie

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 858
  • Last Login:Yesterday at 06:24:33 pm
Re: MN/ON: Border point resync needed
« Reply #2 on: June 12, 2017, 11:07:16 am »
Concur with the US 53/71 change.

But per state of MN GIS data (MnDOT boundary shapefiles plus MnGEO WMS data), the MN 61 point is in the proper location...OSM and Google are a bit off there.

Offline froggie

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 858
  • Last Login:Yesterday at 06:24:33 pm
Re: MN/ON: Border point resync needed
« Reply #3 on: June 12, 2017, 11:11:43 am »
Here's what the MN GIS stuff shows for MN/ON 61.  As you can see, it's a lot closer to the MN side of the river...roughly where the existing MN 61 point already is.  I'd trust this more than I'd trust OSM/Goog.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 2064
  • Gender: Male
  • Last Login:Yesterday at 11:42:03 pm
Re: MN/ON: Border point resync needed
« Reply #4 on: June 12, 2017, 03:46:49 pm »
Here's what the MN GIS stuff shows for MN/ON 61.  As you can see, it's a lot closer to the MN side of the river...roughly where the existing MN 61 point already is.  I'd trust this more than I'd trust OSM/Goog.

Alright, I'll mod ON-61 and sync it with the point in MN-61.

Do you want me to do the US-53/71 sync Froggie, or will you handle it?

Offline froggie

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 858
  • Last Login:Yesterday at 06:24:33 pm
Re: MN/ON: Border point resync needed
« Reply #5 on: June 12, 2017, 04:06:29 pm »
Pull requests submitted for US 53 & US 71.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4422
  • Last Login:November 11, 2024, 12:50:03 pm
  • I like C++
Re: MN/ON: Border point resync needed
« Reply #6 on: June 13, 2017, 12:51:21 pm »
I couldn't resist checking what the Canadian shapefiles have to say:
234482-3 http://www.openstreetmap.org/?lat=48.001438&lon=-89.585158
If you guys already have it sorted, no problem :)
« Last Edit: June 13, 2017, 12:54:14 pm by yakra »
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 2064
  • Gender: Male
  • Last Login:Yesterday at 11:42:03 pm
Re: MN/ON: Border point resync needed
« Reply #7 on: June 13, 2017, 01:12:46 pm »
I couldn't resist checking what the Canadian shapefiles have to say:
234482-3 http://www.openstreetmap.org/?lat=48.001438&lon=-89.585158
If you guys already have it sorted, no problem :)

Wow, that's pretty much spot on to what I suggested first for ON-61/MN-61 (and currently still have in ON-61's file as I haven't submitted a change yet).

Offline froggie

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 858
  • Last Login:Yesterday at 06:24:33 pm
Re: MN/ON: Border point resync needed
« Reply #8 on: June 16, 2017, 11:37:19 am »
My US 53/US 71 changes have gone in.  Is ON 61 fixed?

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 2064
  • Gender: Male
  • Last Login:Yesterday at 11:42:03 pm
Re: MN/ON: Border point resync needed
« Reply #9 on: June 16, 2017, 02:58:17 pm »
My US 53/US 71 changes have gone in.  Is ON 61 fixed?

Would like your opinion on what yakra found in reference to 61 before I push another update to it.

Offline froggie

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 858
  • Last Login:Yesterday at 06:24:33 pm
Re: MN/ON: Border point resync needed
« Reply #10 on: June 16, 2017, 05:44:59 pm »
Call me biased, but I'd prefer to stick with the MnDOT data.  From personal experience, Canada's GeoBase may have some private data mixed in...

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4422
  • Last Login:November 11, 2024, 12:50:03 pm
  • I like C++
Re: MN/ON: Border point resync needed
« Reply #11 on: June 17, 2017, 02:12:36 am »
Oscar and I just had a short discussion about SK35 / US85. Looks like NDDOT's data may be better than GeoBase...
Quote
From personal experience, Canada's GeoBase may have some private data mixed in
Private data?
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 2064
  • Gender: Male
  • Last Login:Yesterday at 11:42:03 pm
Re: MN/ON: Border point resync needed
« Reply #12 on: June 18, 2017, 09:40:17 pm »
Call me biased, but I'd prefer to stick with the MnDOT data.  From personal experience, Canada's GeoBase may have some private data mixed in...

Alright.  I'll sync it with MN with some other changes that I'm working on.

Offline rickmastfan67

  • TM Collaborator (A)
  • Hero Member
  • *****
  • Posts: 2064
  • Gender: Male
  • Last Login:Yesterday at 11:42:03 pm
Re: MN/ON: Border point resync needed
« Reply #13 on: June 25, 2017, 06:46:48 am »
Call me biased, but I'd prefer to stick with the MnDOT data.  From personal experience, Canada's GeoBase may have some private data mixed in...

Alright.  I'll sync it with MN with some other changes that I'm working on.

Sneaked in the change with some WV updates.