OpenStreetMap
Someone expects Canadians to sail their boats into the rocks.
It appears that the Alaska / BC border has been modified. In this area, the US side of the border takes up the whole channel. I think the border may be inaccurate between US and Canada.
Screenshot of the border area. http://www.use.com/6915458a0a159c770df4
Diskuse
Komentář od z-dude z 22. 11. 2012 v 23:58
The official coordianates are listed at http://internationalboundarycommission.org/products.html#coordinates
How do we convert Nad27 or nad 83 into a format that osm can import as a gps track?
Komentář od DENelson83 z 23. 11. 2012 v 01:58
The official coordinates would need to be integrated into all of the relations that follow that boundary, such as the boroughs of Alaska and the Regional Districts of BC.
Komentář od z-dude z 23. 11. 2012 v 02:40
Ok. well, here’s the Nad83 coordinates in decimal format Degree + minute/60 + second/3600
1 54.6622202778 N -132.6841925 E ; 2 54.7074736111 N -130.6156275 E ; 3 54.7247319444 N -130.62864 E ; 4 54.7380730556 N -130.6257208333 E ; 5 54.7630575 N -130.6590380556 E ; 6 54.7827197222 N -130.6288736111 E ; 7 54.7921533333 N -130.5682030556 E ; 8 54.836665 N -130.4802538889 E ; 9 54.8512925 N -130.4543875 E ; 10 54.8733730556 N -130.4227158333 E ; 11 54.9177283333 N -130.3459375 E ; 12 54.9739641667 N -130.2733277778 E ; 13 55.0628413889 N -130.1875622222 E ; 14 55.0912511111 N -130.1808855556 E ; 15 55.1246161111 N -130.1524297222 E ; 16 55.1428422222 N -130.1461247222 E ; 17 55.1926022222 N -130.1028416667 E ; 18 55.2819186111 N -129.9741669444 E ; 19 55.3003713889 N -129.9766486111 E ; 20 55.3379161111 N -130.0211072222 E ; 21 55.4517252778 N -130.0412161111 E ; 22 55.4979780556 N -130.0898527778 E ; 23 55.5810344444 N -130.1279044444 E ; 24 55.6829013889 N -130.1116569444 E ; 25 55.7149033333 N -130.1477586111 E ; 26 55.7662872222 N -130.1524055556 E ; 27 55.8056416667 N -130.1247644444 E ; 28 55.8217075 N -130.0834930556 E ; 29 55.9074416667 N -130.0037847222 E ; 30 55.9119305556 N -130.003785 E ;
I used gpsbabel to create a gpx file but OSM didn’t like the format. I tried to upload a gpx, and got to a point where I could edit with the waypoints on the screen. I’ll leave the data here for now. It’s clear the portland canal should only have 28 markers in it.
Komentář od z-dude z 23. 11. 2012 v 04:32
Could someone double check this before we fix the boundary? osm.org/browse/way/192178744
Komentář od pnorman z 23. 11. 2012 v 08:06
I did some work with the BC/Washington State border some time ago using the IBC data
The IBC data is legally okay to use, so there’s no worries there.
By far the biggest task on the border is de-duplicating the various ways. Simply put, the border is a mess. The position is relatively easy to fix once the duplicate ways are fixed and all the boundary relations are okay.
I’ve prepared .osm files for the SE Alaska and Portland parts of the border at http://took.paulnorman.ca/ibc/
The best workflow I’ve found is to first clean up the border, making all of the boundary relations topologically consistent and then merge through point by point the turning points and monuments, merging existing nodes to them.
I’m currently working on SEAlaska.osm
I did not convert from NAD83 to WGS84 but this is in practice a non-issue as the differences are minimal.
Komentář od z-dude z 23. 11. 2012 v 08:51
if it helps, I double checked the Georgia straight, and those navigation points appeared ok.