Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: yakra on December 18, 2019, 11:25:17 am
-
These are the only NMPs not marked FP in SC (http://travelmapping.net/logs/nmpbyregion/sc.nmp).
ga.ga150@GA/SC 33.6612 -82.199836 LI
sc.us221@GA/SC 33.661201 -82.199836 LI
ga.us221@GA/SC 33.6612 -82.199836 LI
sc.us221@GA/SC 33.661201 -82.199836 LI
They "look intentional", but should still be fixed.
-
http://forum.travelmapping.net/index.php?topic=104.msg16437#msg16437
This would have been done if ntallyn's last pull request was not a complete disaster.
-
What are "NMPs"?
-
What are "NMPs"?
Stands for "near-miss points", which are points so close together that we should be suspicious that they were intended to be a single point but not entered as such. They're important in relation to the academic offshoot of TM (http://courses.teresco.org/metal/).
-
What are "NMPs"?
I addition to what Jim wrote, it's also important in the Highway Browser.
For instance, click on the first waypoint of GA2 (http://travelmapping.net/hb/index.php?&r=ga.ga002). You can see the 'Intersecting/Concurrent Routes' in the info window. When you click on the link (GA193), the route is opened. It makes it easy to navigate through the routes.
Intersection/concurrent routes are detected by their waypoint coordinates. They must match. If a waypoint has slightly different coordinates, we call it 'near-miss point' (NMP).
-
One more thing to add: we don't assume all NMPs are erroneous and automatically merge them together because there are some cases where two waypoints are legitimately very close together but should not be considered a single point, and false concurrencies are often broken by placing two points very close together but intentionally not exactly the same.
The "LI" part means "Looks Intentional" because points are offset by exactly 0.000001 when it's being done intentionally.
-
http://forum.travelmapping.net/index.php?topic=104.msg16437#msg16437
This would have been done if ntallyn's last pull request was not a complete disaster.
Aah, thanks for the reminder. A reconstruction of it has just been lurking on my HD for a couple weeks. Gotta see what I can do about starting to get that merged in.
-
These should be fixed with my last pull request (I fixed the bad one and resubmitted tonight).
-
This was done via ntallyn's last pull request.