Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 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
-
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 (https://github.com/TravelMapping/HighwayData/pull/1344).
-
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.
-
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.
-
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?
-
Pull requests submitted for US 53 & US 71.
-
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 :)
-
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).
-
My US 53/US 71 changes have gone in. Is ON 61 fixed?
-
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.
-
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...
-
Oscar and I just had a short discussion about SK35 / US85. Looks like NDDOT's data may be better than GeoBase...
From personal experience, Canada's GeoBase may have some private data mixed in
Private data?
-
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.
-
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 (https://github.com/TravelMapping/HighwayData/pull/1404).