Travel Mapping
Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on October 07, 2017, 02:47:29 am
-
Starting work on re-centering stuff that needs to be fixed where intersections are way off-centered. Will be starting with WV-2 and go upwards from there.
Threads mentioning intersections being off:
http://tm.teresco.org/forum/index.php?topic=2240.0 (WV-14; solved)
http://tm.teresco.org/forum/index.php?topic=2243.0 (WV-705; solved)
http://tm.teresco.org/forum/index.php?topic=463.0 (US-52; solved)
http://forum.travelmapping.net/index.php?topic=1895.0 (WV-112; solved)
-
First update has been submitted fixing the longest route in the state, WV-2, including anything intersecting it.
As a side bonus, also quickly converted US-22 to exit numbers as it's the only US Highway in the state to be completely freeway and have numbers.
https://github.com/TravelMapping/HighwayData/pull/1645
-
Just pushed an update that deals with the cleanup of WV-3.
Also as a side note, had to correct the two 'end' point labels on WV-12 for it's multiplex with WV-3, as they were flipped (WV3_E should have been WV3_W & vice versa). A mention of this was added for the 'update' page.
https://github.com/TravelMapping/HighwayData/pull/1654
-
Just submitted cleanups of WV-4 to WV-8.
https://github.com/TravelMapping/HighwayData/pull/1669
-
Cleanups of WV-9 to WV-12 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/1690
-
When starting to take a look at getting to work on cleaning up WV-16 tonight, I noticed right at the beginning that we have a WV route that splits WV & VA. That would be WV-161. WV fully maintains it, and no indication in StreetView of any VA State Line postings. Still, when I get to that route's overhaul, it will be split up into 3 parts because of this (similar to NY-17's segment in PA). So, be ready to update list files when I get to it if you have it clinched, or traveled the segment that touches WV-16.
-
Cleanups of WV-14 to WV-17 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/1705
-
Just submitted cleanup of WV-18. https://github.com/TravelMapping/HighwayData/pull/1743
-
Cleanups of WV-20 to WV-25 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/1813
-
Cleanups of WV-26 to WV-38 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/1886
-
Cleanups of WV-39 to WV-45 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/2057
-
Cleanups of WV-46 to WV-54 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/2086
-
Cleanups of WV-55 to WV-67 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/2133
-
Cleanups of WV-68 to WV-76 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/2493
-
Cleanups of WV-80 to WV-90 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/2629
-
Cleanups of WV-92 to WV-103 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/2659
Includes a missing reroute of WV-98 (http://travelmapping.net/hb/?units=miles&u=null&r=wv.wv098) from the mid-00's for a bridge replacement that must have been completed right after the original file was made and has been missed till now.
-
Cleanups of WV-104 to WV-131 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/2679
Also solved the old WV-115 topic (http://forum.travelmapping.net/index.php?topic=1906.0) we have here.
-
Cleanups of WV-150 to WV-310 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/2715
When starting to take a look at getting to work on cleaning up WV-16 tonight, I noticed right at the beginning that we have a WV route that splits WV & VA. That would be WV-161. WV fully maintains it, and no indication in StreetView of any VA State Line postings. Still, when I get to that route's overhaul, it will be split up into 3 parts because of this (similar to NY-17's segment in PA). So, be ready to update list files when I get to it if you have it clinched, or traveled the segment that touches WV-16.
This has also been pushed finally. A hidden '+WV16' has been left in the main file of WV-161 on the 'new' border point to prevent list breakage, but you will still have to enter the new routes to regain any complete clinch of the route.
-
Cleanups of WV-311 to WV-971 have just been submitted. https://github.com/TravelMapping/HighwayData/pull/2763
And thus, brings to this project to a close finally!! 8)
All that is left is to mark the FP's in the NMP list later once this has been pulled in. :)
-
All that is left is to mark the FP's in the NMP list later once this has been pulled in. :)
https://github.com/TravelMapping/HighwayData/pull/2768
Will mark this as solved once that's been pulled in. :)
-
All that is left is to mark the FP's in the NMP list later once this has been pulled in. :)
https://github.com/TravelMapping/HighwayData/pull/2768
Will mark this as solved once that's been pulled in. :)
Everything looks good in the NMPFPs log, so marking this project as completed. 8)