Travel Mapping

Highway Data Discussion => In-progress Highway Systems & Work => Completed Highway Systems Threads => Topic started by: froggie on February 29, 2016, 02:19:04 pm

Title: usava (Virginia State Highways)
Post by: froggie on February 29, 2016, 02:19:04 pm
This is mapmikey's system, but I've been working on a peer review prior to activation.  Backtracking in a way on this, as I started at the end and am working my way forward.  Some of these are pure suggestions...some are suggests to replace shaping points with regular points...some are definitely action items.  If I skipped a route in between entries, I didn't have any comment on it.

VA 598:  I think a shaping point would be useful.

VA 415:  Convert shaping point to regular point at Salters Creek Rd.

VA 413:  Given that there is a direct connection from the Main St/Memorial Dr intersection to the outbound bridge, the VA 293/VA413 point should be moved to the intersection instead of being mid-block.

VA 401:  A couple items with this one.  First, the Eisenhower Ave intersection is just north of the given endpoint (at the Fairfax/Alexandria line).  The point labeled as "EisAve" is actually Metro Rd.  There are two possible solutions to this:  A) use a single point for the endpoint and have it at Eisenhower Ave.  B) have two points in short succession...the endpoint, and a point at Eisenhower Ave.  In either case, the point at Metro Rd could be renamed MetRd or removed altogether (personally, I'd leave it).

Second item is more of a suggestion.  I think a point at Sanger Ave would be useful, both as a "shaping point" but also because it's one of the few ways to cross I-395 in Alexandria.

VA 360:  Instead of a point at RicLn, why not at SR 716?  Also, towards the west side of Halifax, I could see "shaping points" at SR 671 and SR 681.

VA 359:  The Colonial Pkwy point is a little off from the intersection.

VA 352:  Doesn't this route need shaping points?

VA 351:  Should include a point at the "39th Street Connector", its indirect connection to VA 143/Jefferson Ave.

VA 344:  I think it be worth replacing the shaping point in Scottsburg with a point at SR 613.

VA 343:  Should the stub north of US 60 to the campground be included?  It's signed with trailblazers along US 60 (at least it was as of 2014).

VA 337:  Still suggesting that, given the urban nature, there should probably be a point somewhere between 247 and 165/Little Creek Rd.  Still suggesting at Jamestown Crescent, as that's a partial traffic split.  Former guidance from Tim was that, in urban areas, we should have points roughly 1.5 miles apart (or closer as necessary).  It's almost 3 miles along Hampton Blvd from West 27th to Little Creek Rd.

VA 311:  To avoid the "sharp angle" error and for better shaping, I'd add a point at SR 624 west of Catawba and move the existing shaping point near SR 624 a little to the northwest.

The VA/WV point north of Paint Bank looks to be a bit off from the state line.

VA 304:  The point at US 360 is off slightly, probably due to the 4-laning project along 360 (which OSM still doesn't show properly).

VA 294:  294 is signed east/west, so the point order should be reversed.

Because of their area significance, I would replace the EllRd point with one at SR 612/Yates Ford Rd, and add points at SR 642/Hoadly Rd and SR 640/Minnieville Rd.

VA 293:  Mentioned above that the 293/413 point should be moved from mid-block.  Also, with VA 41's extension to US 29, the VA 41/VA 293 intersection has been moved slightly south of where the current list point is.

VA 269:  I could see adding a point at SR 635 and/or SR 633.  Also, something to double-check:  is the VA 42/VA269 termini point at I-64 or at SR 632?  We currently have it at I-64, which signage on the I-64 ramps supports, but signage at SR 632 suggests it's there instead.  2015 shapefiles also suggest it's at SR 632.  (this also affects our entries on VHP).

VA 249:  On VHP, we have VA 249 ending at US 60, but the draft list in the browser has it ending at I-64.  Which one's correct?

VA 242:  Point at SR 611?

VA 239:  "TryPl" is misspelled...should be "TyrPl".

Suggest replacing the shaping point near Dahlgren Ave with a regular point at Dahlgren Ave.

VA 238:  The last two points are mislabeled.  The 2nd to last point (on the east side of old Yorktown) should be the BalSt point, with the endpoint labeled one of "Gate", "USCGTraCen", or "NelRd" (the side road right before the gate being Nelson Rd).

VA 236:  Suggest adding points at SR 620/Braddock Rd and at Quaker Ln in Alexandria.

VA 235:  Suggest moving the Patton Blvd point to Ferry Landing Rd and adding a shaping point (or regular point) at/near the Walker Gate access to Fort Belvoir.

VA 234:  Suggest adding points at SR 640/Minnieville Rd, Bristow Rd (connector to SR 646/Aden Rd and SR 619), SR 642/Hoadly Rd, and Sudley Manor Dr.  All are major roads.  Also suggest replacing the shaping point near Sudley Springs with a point at SR 659/Gum Spring Rd.

VA 231:  SR606 is mislabeled.  It should be SR608.

VA 230:  A point at SR 621 north of Stannardsville could potentially replace the shaping point a short distance north of there.

Technically, the US29 point should be labled US29_S and same thing for the VA231 point.

VA 229:  Suggest a point at SR 621.  It's a pretty important road in the area.

VA 228:  The southern endpoint of this route is a bit different than what's in the HB.  While technically defined as the southern town limit of Herndon, the reality is that the town line follows the roadway for about a half mile.  Based on shapefiles and the distances listed in VDOT's traffic log (0.24mi s of Herndon Pkwy, 0.34mi N of DTR), I would put the endpoint as about halfway between the traffic signal at Worldgate Dr/Parcher Ave and the next signal to the north at a retail entrance...roughly here (http://www.openstreetmap.org/#map=19/38.96020/-77.40101).

VA 227:  The southern endpoint is a bit off from the actual intersection.

VA 226:  Given its connection to a bridge across the river, suggest a point at SR 600.

VA 224:  Suggest a point at SR 704.

VA 222:  Suggest replacing the shaping point with a point at SR 709.

VA 218:  Suggest replacing the shaping point near Passapatanzy with a point at SR 605.

VA 215:  Suggest replacing the shaping point with a point at Rollins Ford Rd.

VA 208:  Suggest a point at SR 652 near Lake Anna (main access point to the southern reaches of Lake Anna).

VA 205:  Suggest replacing the shaping point near Oak Grove with a point at SR 631.

VA 202:  Suggest adding a point at SR 612 Hague.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on February 29, 2016, 10:27:06 pm
VA 249:  On VHP, we have VA 249 ending at US 60, but the draft list in the browser has it ending at I-64.  Which one's correct?

VA 249 is posted as ending at US 60 for the record.  (also verified on GSV)

VA 234:  Suggest adding points at SR 640/Minnieville Rd, Bristow Rd (connector to SR 646/Aden Rd and SR 619), SR 642/Hoadly Rd, and Sudley Manor Dr.  All are major roads.  Also suggest replacing the shaping point near Sudley Springs with a point at SR 659/Gum Spring Rd.

Also I would consider moving the shaping point at Olympic Dr (subdivision entrance but definitely no outlet there) to Purcell Rd or Lake Jackson Dr (both signalized intersections-the latter more likely to work if either do, I do realize that this area is close to VA 294 as well).


-Mark (AKA 74/171FAN on AARoads)
Title: Re: usava (Virginia State Highways)
Post by: yakra on March 01, 2016, 01:40:28 am
Also I would consider moving the shaping point at Olympic Dr (subdivision entrance but definitely no outlet there) to Purcell Rd or Lake Jackson Dr (both signalized intersections-the latter more likely to work if either do, I do realize that this area is close to VA 294 as well).
Lake Jackson alone doesn't work, as in that case it puts the VA234 centerline outside of tolerance at the Meadowgate Drive intersection.
Purcell alone doesn't work, as in that case it puts the VA234 centerline outside of tolerance at the Lake Jackson intersection.
Both points together do work, however.
Title: Re: usava (Virginia State Highways)
Post by: rickmastfan67 on March 01, 2016, 06:03:22 am
VA 311:  To avoid the "sharp angle" error and for better shaping, I'd add a point at SR 624 west of Catawba and move the existing shaping point near SR 624 a little to the northwest.

The VA/WV point north of Paint Bank looks to be a bit off from the state line.

It does seem to be.  It doesn't sync with the VA/WV point in wv.wv311swe (Sweet Springs) (https://github.com/TravelMapping/HighwayData/blob/master/hwy_data/WV/usawv/wv.wv311swe.wpt) point at all.  Would recommend just taking the line out of the WV file and plopping it in.
VA/WV http://www.openstreetmap.org/?lat=37.606616&lon=-80.240879
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on March 05, 2016, 04:37:30 pm
I did all of the suggested with these notes:

For VA 413, I put a point at both legs of VA 293.  I did not change VA 293 because it still runs on the one-way pair.  VA 413 does run east to Patton and signs on 413 still direct you to go to Patton to reach VA 293 NB, despite the ability to do so directly from Main

VA 343 does not seem to be posted north of US 60 anymore, per GMSV 2007-15

VA 311cro also needed WV state line match so I did that

VA 269 ends at I-64 on both ends per traffic logs and also 2003 route log; I'm not sure the shapefiles show overlays; 2004 VDOT County Atlas shows VA 42-269 on that piece.

VA 249 is exactly the opposite: posted from US 60 but all sources above show it ending at I-64. 

In my queue for submission after I resolve one other thing in Virginia...

Mike
Title: Re: usava (Virginia State Highways)
Post by: froggie on March 07, 2016, 07:46:01 am
Continuing to work backwards (from 200):

VA 199:  Old York Rd (east of I-64) is now Water Country Pkwy.

VA 198:  Perhaps a point at SR 678 Harcum?

VA 191:  The southern endpoint is where 13/460 turn onto Military Hwy, just south of I-664.

VA 190:  For the River Walk, Greenbrier, and Lynnhaven Parkway points, should it be Pkwy or Pky?  Also, since it's in Chesapeake, the Lynnhaven Pkwy point should be Volvo Pkwy instead.

Suggest adding points at Centerville Tpk (major arterial) and Providence Rd (former VA 409).

With the reconstruction/realignment in Kempsville, the VA 165/VA 190 point needs to be shifted south.

VA 189:  Suggest a point at Wyanoke Trl, near the river, for shaping purposes.

VA 187:  The eastern endpoint is about a quarter-mile farther north than it should be.  It should be roughly here (http://www.openstreetmap.org/#map=19/37.81597/-75.56320).

VA 184:  Given how it's signed (east/west), the point order should be reversed.

VA 183:  The shaping point should be replaced with a regular point at either SR 611 or SR 634.

Suggest adding a point at SR 606 Wardtown.

A point should be added at SR 652 for shaping purposes.

VA 179:  The west end is slightly off.  It should be even with the north end of the Wharf area, approximately here (http://www.openstreetmap.org/#map=19/37.71219/-75.75523).

VA 175:  Given its area importance (plus the only traffic signal on 175 between its endpoints), suggest a point at SR 798.

For those who haven't been across the new Chincoteague Bridge yet, perhaps a point at Old 175?

VA 173:  The VDOT route log specifies the western end as being "310 feet from the Warwick River at the beginning of pavement".  While the pavement edge is currently less than that distance from the river, that 310 feet is roughly even with the east end of the parking lot at Denbeigh Park.

VA 171:  The LawRd point is a bit off.

VA 168 BUSINESS:  Suggest a point at Volvo Pkwy (local arterial and also on the VA 190 list).

VA 168:  Instead of exit numbers, should we use regular labels instead on the freeway portion?  Hidden exit number labels could be used in order to not break any user lists using the existing 168 freeway list.

Instead of a point at MusAve, suggest a point at Norview Ave instead.

Given the funkiness that is WB US 60's routing and turn restrictions, suggest a point at Mason Creek Rd.

VA 166:  Now that the new connection to US 17 at Dominion Lakes Blvd is open, the south end should be revised to meet US 17 there (also affecting the US 17 list).  Suggest an "Old166" point where Dominion Lakes Blvd meets Bainbridge Blvd.

Suggest a point at either Ballentine Blvd or Ingleside Rd in Norfolk.

Given precedent, should a point be added at (unsigned) VA 332?

VA 165:  For those who haven't driven the new(ish) Moses Gandy Trail, perhaps add points at old Cedar Rd on each end?

Given their area importance, suggest points at Centerville Tpk, Indian River Rd, Nimmo Pkwy, and Dam Neck Rd.

With the reconstruction/realignment in Kempsville, the VA 165/VA 190 point needs to be shifted south (also mentioned above under 190 corrections).

The I-64(281) point is a bit off.  This should be addressed on the I-64 list as well.

VA 152:  Suggest points at Big Bethel Rd and Coliseum Dr.

VA 144:  Suggest replacing the shaping point near the Appomattox River with a point at SR 645/Puddledock Rd.

VA 143:  Suggest a point where US 60/VA 143 turn off of Settlers Landing Rd. (also would be needed on US 60 list)

Add a point at 40th St in Newport News? (Connector to VA 351)

Technically, VA 143 extends up to the front gate at Camp Peary.

VA 141:  The I-264 point should be relocated so that it's properly on VA 141.  It was likely placed where it is because the Effingham and Court St interchanges were consolidated into a single point on the I-264 list, though it does not reflect the reality...while they share the same ramps to/from the Downtown Tunnel, they are effectively two separate interchanges.  Whether or not the I-264 list gets adjusted, the point on the 141 list should be relocated so that it's not a block off the street.
Title: Re: usava (Virginia State Highways)
Post by: oscar on March 07, 2016, 08:31:11 am
VA 168:  Instead of exit numbers, should we use regular labels instead on the freeway portion?  Hidden exit number labels could be used in order to not break any user lists using the existing 168 freeway list.

Why not use the existing exit numbers? I see no problem with a route file including both exit numbers on freeway portions and regular labels on non-freeway portions.
Title: Re: usava (Virginia State Highways)
Post by: froggie on March 07, 2016, 08:34:15 am
I never did like that particular rule of Tim's.  I think it creates more confusion than it solves.
Title: Re: usava (Virginia State Highways)
Post by: mapcat on March 07, 2016, 11:35:00 am
I think it creates more confusion than it solves.

Maybe it's just a personal preference, but I find 5, 10A, and 13 less ambiguous than VA168Bus_B, VA168Bus_C, and VA168Bus_D.
Title: Re: usava (Virginia State Highways)
Post by: froggie on March 07, 2016, 12:00:42 pm
In this particular case, I could see that, but 168 crossing and interchanging with its business route as often as it does is the exception rather than the rule.
Title: Re: usava (Virginia State Highways)
Post by: yakra on March 07, 2016, 01:52:35 pm
I never did like that particular rule of Tim's.  I think it creates more confusion than it solves.
Not sure what rule you mean. Do you mean, a rule to not use exit numbers?
When beginning work on the select state routes, "route file(s) including both exit numbers on freeway portions and regular labels on non-freeway portions" were specifically allowed. See: NH101 (http://tm.teresco.org/devel/hb.php?r=nh.nh101), which I labeled following direction from Tim, though I can't find the relevant thread or email now.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on March 07, 2016, 06:00:47 pm
Froggie-  I will note that Mike already did a couple of these (VA 171, VA 165 at VA 190).   If I am correct, I mentioned the OldYorkRd one too but remembered that VA 199 is currently in usansf so I am unsure what happened to the VA 199 usava file.

-Mark
Title: Re: usava (Virginia State Highways)
Post by: Bickendan on March 08, 2016, 01:00:29 am
I never did like that particular rule of Tim's.  I think it creates more confusion than it solves.
Not sure what rule you mean. Do you mean, a rule to not use exit numbers?
When beginning work on the select state routes, "route file(s) including both exit numbers on freeway portions and regular labels on non-freeway portions" were specifically allowed. See: NH101 (http://tm.teresco.org/devel/hb.php?r=nh.nh101), which I labeled following direction from Tim, though I can't find the relevant thread or email now.
It's also what I did with California's routes when I drafted them.
Title: Re: usava (Virginia State Highways)
Post by: froggie on March 08, 2016, 08:54:20 am
I never did like that particular rule of Tim's.  I think it creates more confusion than it solves.
Not sure what rule you mean. Do you mean, a rule to not use exit numbers?
When beginning work on the select state routes, "route file(s) including both exit numbers on freeway portions and regular labels on non-freeway portions" were specifically allowed. See: NH101 (http://tm.teresco.org/devel/hb.php?r=nh.nh101), which I labeled following direction from Tim, though I can't find the relevant thread or email now.

The rule to use exit numbers where they existed and regular labels otherwise.  Was not a fan of that rule, and the way I read Tim's comments/responses at the time, he made it a requirement, not an option.
Title: Re: usava (Virginia State Highways)
Post by: yakra on March 09, 2016, 10:36:30 am
The rule to use exit numbers where they existed and regular labels otherwise.
Aah, gotcha.

Was not a fan of that rule, and the way I read Tim's comments/responses at the time, he made it a requirement, not an option.
By my reading of the Manual, I come to the same conclusion.
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on March 12, 2016, 02:05:50 pm
I have gone through Set #2 of Froggie's feedback and done what was suggested with the following comments:

VA 199 I previously addressed by eliminating the point

VA 191 is a mixed bag: traffic log says what froggie says; route log, postings say it ends at Airline; Shapefiles call it US 13 (as US 13 S/460 W must use this for continuity); 2004 VDOT county atlas doesn't label it at all; VHP says it ends at Military Hwy and I can't remember why I specifically have it that way.  I added the waypoint based on the example of VA 32 being done into Newport News despite no postings past its southern US 17 split

VA 190 - note that Jim ran a routine to change all my pky to pkwy throughout the entire route lists

VA 189 - I also changed the SR 666 name to Gates Rd as it is within the City of Suffolk

VA 179 - official sources disagree between Dave's choice and yours but I moved it to yours because that is where the pavement changes.

VA 168 - I left MusRd because it is an interchange but added Norview.  Also added one at the Government Rd location north of US 460 because there is an on and off ramp in that location.  I chose to leave the exit numbers for the toll road.  They are referenced on VA 168 Business waypoints anyway.


I have sent both rounds of Virginia changes to Jim...

Mike
Title: Re: usava (Virginia State Highways)
Post by: froggie on March 13, 2016, 08:12:16 am
Quote
VA 191 is a mixed bag: traffic log says what froggie says; route log, postings say it ends at Airline; Shapefiles call it US 13 (as US 13 S/460 W must use this for continuity); 2004 VDOT county atlas doesn't label it at all; VHP says it ends at Military Hwy and I can't remember why I specifically have it that way.

At one point in the not-too-distant past, postings continued it south of Airline.  That, in conjunction with the traffic log, is likely why we had it at Military Hwy on VHP.

Quote
VA 179 - official sources disagree between Dave's choice and yours but I moved it to yours because that is where the pavement changes.

I ran the mileages from the traffic log and what we have on VHP and came up with my suggested point as a result.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on March 13, 2016, 08:41:27 am
Minor changes in Prince George County

VA 156:  The point at SR 630 (Lamore Drive) needs to be slightly relocated.  I remember this intersection was relocated sometime in the 2000s, but I cannot remember offhand exactly when.
VA 106:  The point at SR 634 (Allin Rd) needs to be recentered onto the roundabout completed around 2010.
Title: Re: usava (Virginia State Highways)
Post by: froggie on March 13, 2016, 03:30:05 pm
Continuing backward from where I left off...

VA 138:  Suggest replacing the shaping point south of VA 137 with a point at SR 617.

VA 134:  I'm not sure I like the placement of the point at I-64(265).  On the one hand, there are two direct ramps between westbound 64 and VA 134.  On the other hand, the primary reason for that interchange is LaSalle Ave (former VA 167), and the LaSalle Ave intersection with 134 splits where the 64 ramps connect to 134.  Personally, I'd ditch the 64 point and add a point at LaSalle Ave.

HamRoaPkwy, properly labeled, should be HamRoaCenPkwy.

Suggest a point at SR 600/Big Bethel Rd, which is a north-south arterial.

VA 130:  Suggest replacing the VolHudRd point with a point at SR 650/W Perch Rd in conjunction with replacing the shaping point near the Pedlar River with a point at SR 635/Buffalo Springs Turnpike.

VA 128:  Is a shaping point needed between Odd Fellows Rd and BUSINESS 460/501?

VA 123:  Given the built-up suburban nature of this road, and the arterial nature of the intersecting roads, I could see adding points at three more locations:  SR 641/Old Bridge Rd, SR 643/Lee Chapel Rd, and SR 620/Braddock Rd.

VA 117:  Suggest a point at Cove Rd NW.

VA 116:  Suggest replacing the AerRd point with a point at SR 681 (main access road to the east of Roanoke and south of the river).

VA 114:  What's labeled as SR 659 is *NOT* SR 659 (which is actually at the PriForkRd point).  It should be relabeled ConRd (for Constitution Rd).

VA 106 (besides what was just mentioned):  Suggest replacing the shaping point east of I-295 with a point at SR 616.

Suggest a point at SR 607 near Wayside.

VA 103:  Suggest replacing the western shaping point with a point at SR 645.

VA 100:  Suggest replacing the shaping point north of DeerRidRd with a point at SR 749/Sylvatus, adding a point at SR 693/Sylvatus, and moving the BrimRd point to SR 607/Patterson.

Suggest moving the WooFarmRd point south to SR 609.
Title: Re: usava (Virginia State Highways)
Post by: yakra on March 14, 2016, 11:42:41 am
Quote
HamRoaPkwy, properly labeled, should be HamRoaCenPkwy.
The guideline (http://cmap.m-plex.com/tools/manual_wayptlabels.php) is as follows:
Quote
If the cross road name has more than 3 words, use one of two options:
1. Pick out the two most important words besides the road type and use only those: Martin Luther King Boulevard becomes MarKingBlvd. Three words in total are included in shortened form.
2. Pick out one important word besides the road type and use it and the initials of the other words: Martin Luther King Boulevard becomes MLKingBlvd. Two words in total are included in shortened form along with initials of the rest.
Thus HamRoaPkwy is correct. HRCenPkwy, HamRCPkwy or HRoaCPkwy would also be compliant, but IMO calling "Center" one of "the two most important words" (as in HamCenPkwy or RoaCen Pkwy) is a stretch. I like HamRoaPkwy best.
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on March 14, 2016, 12:23:05 pm
Have to say I am a little fuzzy on the need for strict guidelines on aspects of TM that don't affect how the computer code interprets it (e.g. proper overlay calculation).  The users who create lists aren't provided with the rules so they have to click on the point to see what it is named anyway (and the rule list is long enough that clicking on the point is faster anyway).

My 2 cents...

I will continue to follow whatever guidelines are asked of me...

Mike

Title: Re: usava (Virginia State Highways)
Post by: froggie on March 14, 2016, 12:37:37 pm
Quote
Thus HamRoaPkwy is correct. HRCenPkwy, HamRCPkwy or HRoaCPkwy would also be compliant, but IMO calling "Center" one of "the two most important words" (as in HamCenPkwy or RoaCen Pkwy) is a stretch. I like HamRoaPkwy best.

If this is the case, then HRCenPkwy would be the best fit.  Because for this roadway, Center *IS* the most important word.  It's so named because it's adjacent to the Hampton Roads Center development area of Hampton.
Title: Re: usava (Virginia State Highways)
Post by: michih on March 14, 2016, 02:30:04 pm
Have to say I am a little fuzzy on the need for strict guidelines on aspects of TM that don't affect how the computer code interprets it (e.g. proper overlay calculation).  The users who create lists aren't provided with the rules so they have to click on the point to see what it is named anyway (and the rule list is long enough that clicking on the point is faster anyway).

Agree!
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on March 14, 2016, 08:07:57 pm
all items VA100-156 are addressed and are in my queue...

mike
Title: Re: usava (Virginia State Highways)
Post by: yakra on March 14, 2016, 09:58:12 pm
At the end of the day, the guidelines can produce multiple results, so clicking the point is still necessary. That said though, I do think consistency and brevity are worthy goals.

I agree with froggie's assessment of HRCenPkwy.
Title: Re: usava (Virginia State Highways)
Post by: Jim on March 14, 2016, 10:25:16 pm
At the end of the day, the guidelines can produce multiple results, so clicking the point is still necessary. That said though, I do think consistency and brevity are worthy goals.

Pretty much what I was going to post.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on April 12, 2016, 09:28:32 pm
I was considering waiting on Froggie finishing his peer review to mention this but I will go ahead and mention it now.

VA 28:points at Severn Way (SR847) and Dulles Center Blvd (DulCenBlvd) should be marked as closed. The SteDr point should remain but possibly be renamed???

 I just finally clinched VA 28 north of I-66 less than two weeks ago when in the area about 10 days ago.

-Mark AKA 74/171FAN
Title: Re: usava (Virginia State Highways)
Post by: dave1693 on April 28, 2016, 07:15:47 pm
Quick note...

VA 203: the waypoint marked as SR601 should be SR604. 601 doesn't come anywhere near this intersection, which is the southwestern end of SR604, locally dubbed the "Sandy Point Speedway". (My wife grew up in the area, and my mother-in-law still lives there, so we have been to this intersection rather a lot.)

Dave
Title: Re: usava (Virginia State Highways)
Post by: dave1693 on April 28, 2016, 07:22:20 pm
Quote
VA 28:points at Severn Way (SR847) and Dulles Center Blvd (DulCenBlvd) should be marked as closed. The SteDr point should remain but possibly be renamed???

Well, all the signs on 28 now say "Warp Drive" so perhaps it should be renamed...

Dave
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on May 06, 2016, 07:45:15 pm
I have fixed the VA 28 and VA 203 files.

I did not fix the VA 28 freeway file as it is going away so I didn't see the need to do so...
Title: Re: usava (Virginia State Highways)
Post by: yakra on May 07, 2016, 01:24:05 am
I'd suggest fixing it anyway, as all occurrences of "VA28" in a .list file will continue to point to the freeway version, until USAVA is activated & replaces it.
Title: Re: usava (Virginia State Highways)
Post by: froggie on May 07, 2016, 07:11:58 am
Mike's idea is probably that usava will be activated soon, once reviews and such are completed.

And on that note, I apologize that it's taken me so long...semester got in the way.  But this upcoming week is our last week (finals! yay!) so I should be able to get back to reviewing by next weekend.
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on May 07, 2016, 09:32:01 am
I'd suggest fixing it anyway, as all occurrences of "VA28" in a .list file will continue to point to the freeway version, until USAVA is activated & replaces it.

All of the fixes are either closing a waypoint or renaming one so existing .list files should still work just fine...?
Title: VA 7, VA7 Freeway
Post by: johninkingwood on July 01, 2016, 07:35:03 pm
I am a longtime lurker and road tracker on this site and its predecessor. The new site looks great! I appreciate everyone's hard work.

I keep getting log errors on my line for VA 7. Currently, there is an active line for VA7Fwy (I believe that is how it is presented), and one for VA7. Every time I submit a list, I get errors on both of them. I have attempted multiple submissions on both versions of VA 7. Will the two versions of VA 7 eventually be combined? The freeway bypass around Leesburg and the highway are a continuous road.

On my most recent log, it is not finding the waypoint label between VA28 and VA287. My error reads: "Waypoint label(s) not found in line: VA VA7 VA28 VA287"

I just want to make sure I get the line right on my log.

Thank you so much for your help!
Title: Re: usava (Virginia State Highways)
Post by: rickmastfan67 on July 02, 2016, 06:51:07 pm
I think it's because the Virginia routes are in the 'preview' stage.  We've been throwing around just copying over all of the VA-7 file into the 'Fwy' file till we active the system.  Same thing is happening with VA-28.

@mapmikey @froggie @Jim
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on July 02, 2016, 07:21:18 pm
Froggie, what is the status of your peer review?  I have noticed the points on VA 80 around SR 609 are off (due to the slight relocation as a result of the US 460/Corridor Q Extension- I saw this area as a part of the Pikeville meet a couple years ago, but I cannot remember if VA 80 was relocated yet).

-Mark
Title: Re: usava (Virginia State Highways)
Post by: Jim on July 02, 2016, 09:28:42 pm
Does anyone have comments on the routes that are in usava but which have shorter versions in usansf?  They should be copied over unless usava is really close to full activation.
Title: Re: usava (Virginia State Highways)
Post by: froggie on July 03, 2016, 09:22:14 am
I've provided comment on everything above VA 100.  I can shift my priority to looking at the rest of the routes this week.
Title: Re: usava (Virginia State Highways)
Post by: johninkingwood on July 03, 2016, 05:04:47 pm
Thanks for the input! I'll leave VA7 off my list until all of VA is active.

Thanks for all your hard work!
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on July 12, 2016, 08:22:08 pm
Froggie, what is the status of your peer review?  I have noticed the points on VA 80 around SR 609 are off (due to the slight relocation as a result of the US 460/Corridor Q Extension- I saw this area as a part of the Pikeville meet a couple years ago, but I cannot remember if VA 80 was relocated yet).

-Mark

Per online maps it appears VA 80 has been temporarily routed on the much older alignment through Breaks.  It will eventually follow the new road with overpass up to Corr Q to go into Kentucky.  VDOT estimates this will occur in late 2017.

What I did to the file was move the BreParRd point to where VA 80 leaves the eventual new VA 80 and renamed it SR 693.  I took the next point up (SR 609) which is right at the overpass and turned it into a "closed" point.  Once VA 80 is moved onto Corr Q the last 3 waypoints on VA 80 will have to be eliminated and a couple new ones installed in their place.

Will be submitted with my next updates...
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on September 16, 2016, 10:08:44 pm
Quote
VA 165:  Given their area importance, suggest points at Centerville Tpk, Indian River Rd, Nimmo Pkwy, and Dam Neck Rd.

For some reason, the Dam Neck Rd (https://www.google.com/maps/@36.7755966,-76.0912156,3a,90y,159.92h,82.8t/data=!3m6!1e1!3m4!1s9rff_Z8iqP4_2GpbJ7DB5g!2e0!7i13312!8i6656) point is marked as DamNeckBlvd.

Also since the VA 192 file does not exist due to it being unposted, should that point just be for Azalea Garden Rd?  (applies to VA 170 as well)

VA 36:  The SR 600 point in Matoaca needs to be moved to the intersection at Pickett Ave.
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on September 16, 2016, 11:09:02 pm
Quote
VA 165:  Given their area importance, suggest points at Centerville Tpk, Indian River Rd, Nimmo Pkwy, and Dam Neck Rd.

For some reason, the Dam Neck Rd (https://www.google.com/maps/@36.7755966,-76.0912156,3a,90y,159.92h,82.8t/data=!3m6!1e1!3m4!1s9rff_Z8iqP4_2GpbJ7DB5g!2e0!7i13312!8i6656) point is marked as DamNeckBlvd.

Also since the VA 192 file does not exist due to it being unposted, should that point just be for Azalea Garden Rd?  (applies to VA 170 as well)

VA 36:  The SR 600 point in Matoaca needs to be moved to the intersection at Pickett Ave.

I have corrected the VA 36 and the Dam Neck Rd points.  In my queue for submittal.

I am inclined to leave VA 192 labels alone.  There are other examples in the Virginia set where an unposted primary route is given a label...
Title: Re: usava (Virginia State Highways)
Post by: mapcat on September 18, 2016, 04:28:20 pm
If you'd consider adding some waypoints, these would be useful to me:

On VA40 at SR681 west of Stony Ctreek
On VA49 at SR625 south of Crewe

Also, I found two concurrency issues. In Bedford, US221 is missing a waypoint for US460Bus that VA122 has. And at SR613 west of Appomattox, VA24 has a waypoint but US460 doesn't.



Title: Re: usava (Virginia State Highways)
Post by: mapmikey on October 01, 2016, 03:31:22 pm
Files edited and submitted...
Title: Re: usava (Virginia State Highways)
Post by: dfilpus on October 03, 2016, 11:14:44 am
Now US221 has two waypoints labelled US460Bus_W, one in Bedford and one in Lynchburg. There are five places where US221 and a US460Bus intersect:
1. US221/US460Bus, west of Bedford.
2. US460_E, the eastern end of US460Bus Bedford.
3. US460Bus_W, where US 221 turns north from US460Bus Bedford.
4. US460Bus_W, where US 221 turns north from US460Bus Lynchburg.
5. US29Bus. where US221 ends, ending the concurrency with US460Bus Lynchburg.

My suggestion is to relabel points 1 and 3 to use US460BusBed and point 4 to use US460BusLyn.
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on October 03, 2016, 08:21:39 pm
oops...didn't catch that...

I have made a fix and is in the queue for next set of submissions...

Thanks-
Mike
Title: Re: usava (Virginia State Highways)
Post by: Jim on October 03, 2016, 09:02:18 pm
oops...didn't catch that...

I have made a fix and is in the queue for next set of submissions...

Thanks-
Mike

Might be worth sending that right away, since it's an error that likely affects people's stats.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on October 07, 2016, 11:47:53 am
Also it looks like the points need to be recentered at US 221/VA 122 intersection (seems to have been realigned when Independence Blvd was built) on the north end of the concurrency where both routes meet their respective business routes.  (Forest Rd at Longwood Ave/Independence Blvd, this affects both business routes as well)

Mark
Title: Re: usava (Virginia State Highways)
Post by: mapcat on October 09, 2016, 08:29:28 pm
Thanks for adding the points I requested.

One more issue: US460 & VA83 don't line up exactly through Grundy along their concurrency.
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on November 14, 2016, 09:05:54 pm
Fixes for the Bedford intersection and the US 460/VA 83 were submitted to Jim this evening...
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on November 15, 2016, 10:45:26 pm
Fixes for the Bedford intersection and the US 460/VA 83 were submitted to Jim this evening...

I just opened the VA 83 file.  It looks like  all but the US 460 concurrency itself got deleted (and it does not even show all of that clinched for me, I have an error in my log file due to this).

Also for the Bedford intersection, the point on US 221 was not relocated.
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on November 16, 2016, 06:26:30 am
oops...shouldn't do fixes while tired....

Anyway, I have corrected the VA 83 file and resubmitted.  I will fix the US 221 relocation with my next set of updates...
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on November 30, 2016, 12:39:14 am
VA 22, VA 208, VA 231, and VA 20 all have multiplexes with US 33 but have N/S labels instead of E/W labels. (http://tm.teresco.org/forum/index.php?topic=1818.msg4407#new)

Other notes with above routes:
VA 22:  WhiPineRd is marked as White Pine Ln on Google Maps but cannot be seen in GSV (https://www.google.com/maps/@38.075917,-78.2192306,3a,75y,311.63h,84.79t/data=!3m6!1e1!3m4!1szbMJzEh3o7WGpD_dhR9DhA!2e0!7i3328!8i1664).  (seems to maybe be a private drive??)

VA 208:  Labels for US 522 should be S/N instead of W/E

VA 231:  Point at SR 621 needs to be recentered


Other note:
VA 10:  RivDr is actually for Riverside Ave (http://tm.teresco.org/hb/index.php?u=markkos1992&r=va.va010).  Having the ramps to/from VA 10 EB being called Riverside Loop Rd make this confusing IMO. 

Title: Re: usava (Virginia State Highways)
Post by: mapmikey on November 30, 2016, 08:51:06 pm
All fixed, plus I also changed VA 28 and VA 215 files from the relocation of VA 215 onto newly constructed alignment that meets VA 28 1/4 mile further southwest...in the queue
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on December 12, 2016, 08:55:20 pm
VA 365 has a second posted segment that I found for the first time on Saturday.

A new file has been created and sent in with all stuff in the queue going with it...
Title: Re: usava (Virginia State Highways)
Post by: Jim on December 12, 2016, 10:33:33 pm
VA 365 has a second posted segment that I found for the first time on Saturday.

A new file has been created and sent in with all stuff in the queue going with it...

It's in, but is there's a better name than "East"?
Title: Re: usava (Virginia State Highways)
Post by: yakra on December 13, 2016, 01:36:56 am
I assume it's all in the same municipality as all of the rest -- Wytheville Community College, perhaps?
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on December 25, 2016, 04:20:15 pm
I just noticed that the VA 337 ALT in Downtown Norfolk is not in TM.  Is there a reason for that?
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on December 26, 2016, 12:00:14 am
Never been posted
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on December 26, 2016, 05:37:50 am
Never been posted

Sorry I had forgotten about that when I posted it.
Title: Re: usava (Virginia State Highways)
Post by: Jim on January 18, 2017, 02:42:13 pm
I think it's because the Virginia routes are in the 'preview' stage.  We've been throwing around just copying over all of the VA-7 file into the 'Fwy' file till we active the system.  Same thing is happening with VA-28.

@mapmikey @froggie @Jim

This is probably the single most common question I get from people when submitting list files.  Unless usava activation is imminent, could we extend the versions on usansf to reduce that confusion?
Title: Re: usava (Virginia State Highways)
Post by: froggie on January 19, 2017, 11:01:14 am
On that note, besides the rest of my peer review (which I admit has been bogged down to to work/home/school priorities), is there anything else preventing usava from being activated?
Title: Re: usava (Virginia State Highways)
Post by: Jim on January 19, 2017, 11:59:35 am
It has been in preview for almost 14 months, so I think many of the problems have likely been worked out as people have been adding the routes to their list files.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on January 19, 2017, 03:56:57 pm
I have submitted a few issues here and there, but I did not want to impede but so much into Froggie's review.

Mark AKA 74/171FAN
Title: Re: usava (Virginia State Highways)
Post by: yakra on January 21, 2017, 02:29:33 pm
I don;t think a review should have to be primarily done by one person. The more the merrier, I say.
Title: Re: usava (Virginia State Highways)
Post by: mapcat on January 21, 2017, 02:43:50 pm
At some point after preview has begun, and numerous reports have come in and been addressed, and over a year has passed, and the primary reviewer has more pressing obligations, activation ought to be considered.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on January 21, 2017, 06:18:47 pm
I'll go ahead and do a quick check below VA 100(where I believe Froggie stopped) for anything glaring for the moment so it can at least get activated.
Title: Re: usava (Virginia State Highways)
Post by: froggie on January 22, 2017, 07:34:07 am
Don't do a "quick check".  Do a detailed check.  With that, I'd agree with that route (pun intended).

(as a side note to Jim and mapcat, this peer review began less than a year ago...look at the date I started this thread)
Title: Re: usava (Virginia State Highways)
Post by: mapcat on January 22, 2017, 11:14:10 am
(as a side note to Jim and mapcat, this peer review began less than a year ago...look at the date I started this thread)

Fair point. I was going by the date usava went to preview (November 26, 2015) and assumed that your initial post included items you had noticed before February.
Title: Re: usava (Virginia State Highways)
Post by: froggie on January 22, 2017, 11:48:32 am
Nope...was on February break that week last year and that's when I had started the peer review.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on January 26, 2017, 10:32:32 pm
I think my biggest confusion with the rules still seems to be the shaping points from what I have seen going through all of these rural VA routes.  (any route with shaping point confusion has an asterisk beside it)

This post contains VA 100 (I found a few issues here)-VA 69.  I did not realize that I could not copy hyperlinks directly from MS Word to here so be forewarned if the links are wrong or if I forgot one.

*VA 100: Shaping point at SR 794 should be for SR 784, but this is probably better served being moved to SR 749 (https://www.google.com/maps/@36.8542181,-80.762717,3a,90y,344.58h,61.78t/data=!3m6!1e1!3m4!1sNZLg-WuUU0HfraJGhng4SA!2e0!7i13312!8i6656). Point at WooFarmRd should be for Pine Run Rd (https://www.google.com/maps/@36.947396,-80.7899343,3a,15y,64.29h,83t/data=!3m6!1e1!3m4!1s5Sr2sXVSnwbKdSm2NSC78A!2e0!7i13312!8i6656).  Shaping Point at TigLn (https://www.google.com/maps/@37.2757284,-80.742366,3a,37.1y,321.05h,80.67t/data=!3m6!1e1!3m4!1sAjB2PBWJ5spnSdKiVkKrQw!2e0!7i3328!8i1664) should be replaced by one at nearby SR 622 to the north.
VA 99: Point at RaiAve should be for RanAve (Randolph Ave) (https://www.google.com/maps/@37.0479209,-80.7847587,3a,75y,91.68h,60.66t/data=!3m6!1e1!3m4!1sy7VImyw0mBjch3CLnN-hPg!2e0!7i13312!8i6656)
*VA 97: Shaping Point at LogLn (for Logans Ln) (https://www.google.com/maps/@36.6202341,-80.8097093,3a,90y,30.43h,73.44t/data=!3m6!1e1!3m4!1s7l2ioX3ISe6f-vXVCoIcTA!2e0!7i3328!8i1664) looks to be just for a driveway and is not at an intersection.
*VA 94: Possibly move shaping point from HorRd to nearby intersection at SR 815 (https://www.google.com/maps/@36.713678,-81.0045642,3a,75y,288.28h,66.53t/data=!3m6!1e1!3m4!1suLABVVTrzfE_E3P0wc8wCQ!2e0!7i13312!8i6656) if doable. Point at LeoRd (for nearby Leonard Rd) should be changed to SR 604 (https://www.google.com/maps/@36.7484769,-80.9868488,3a,75y,210.16h,78.98t/data=!3m7!1e1!3m5!1smHOWsAA-DVOPKu5_-IRLNw!2e0!6s%2F%2Fgeo2.ggpht.com%2Fcbk%3Fpanoid%3DmHOWsAA-DVOPKu5_-IRLNw%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D140.68579%26pitch%3D0%26thumbfov%3D100!7i3328!8i1664) (name looks to be Mount Olive St from GSV but I cannot verify that).  Shaping Point for BulRd (Bullet Rd) is not at the intersection but could maybe be put at nearby SR 602 (https://www.google.com/maps/@36.7861119,-80.9815727,3a,70.5y,4.04h,86.96t/data=!3m6!1e1!3m4!1sBCyvOfosqUohr3Ixsozegw!2e0!7i3328!8i1664). StrHolRd (https://www.google.com/maps/@36.7991024,-80.9908874,0a,95.6y,63.36h,71.82t/data=!3m4!1e1!3m2!1sUoe6PRU-pLGUP4uBjmkBMw!2e0?source=apiv3) shaping point should be moved to nearby SR 738.  Point at SR 658 should maybe be for SR 743 (https://www.google.com/maps/@36.7991024,-80.9908874,0a,95.6y,63.36h,71.82t/data=!3m4!1e1!3m2!1sUoe6PRU-pLGUP4uBjmkBMw!2e0?source=apiv3). 
VA 93:  NC/VA line point needs to be recentered.
VA 92: Should the End point be marked as closed due to the Roanoke River Bridge closure?
VA 91 BUS (Glade Spring): Not sure if the road it intersects at SR 1309 is Crescent Dr or Crescent Rd (according to VDOT Traffic Logs (http://virginiadot.org/info/resources/Traffic_2015/AADT_095_Washington_2015.pdf))
*VA 91: EdmLn label should probably be changed to be for Liberty Hall Dr. The labels for the shaping points at ShaRd and MaiRd could be removed more than likely.  Besides if I drive the gravel section, why would I not do it all at once?
VA 86: Point at College Park Dr (ColParkDr) (https://www.google.com/maps/@36.5626632,-79.405327,3a,73.7y,48.56h,81.27t/data=!3m6!1e1!3m4!1sHMKPZCqByM7e_y4FBchcww!2e0!7i13312!8i6656) is barely off.
*VA 83: Shaping point at Cedar Rd should probably be moved to nearby SR 631 (https://www.google.com/maps/@37.1308761,-82.586369,3a,73.7y,354.76h,71.78t/data=!3m6!1e1!3m4!1sVvgpgfE-dMV8tzy2EETf6Q!2e0!7i13312!8i6656).    Point at SR 750 should be for SR 718 (https://www.google.com/maps/@37.2212189,-82.1459561,3a,75y,78.57h,78.97t/data=!3m6!1e1!3m4!1sOsB-RFRZi5x1bVszCSqXHw!2e0!7i3328!8i1664).  (other unsure shaping points-GolWaveDr and EnoBraRd (this could be moved to nearby SR 642))
*VA 80: Point at RivChuRd should probably be renamed to reflect N Fork River Rd as that is the more important road there it seems.  RavRidRd (https://www.google.com/maps/@36.8647473,-81.9469891,3a,73.7y,176.76h,76.28t/data=!3m6!1e1!3m4!1sKgtEptGdzvRbubEZpgyWpA!2e0!7i13312!8i6656) looks to be a trail entrance/sight-seeing spot so I guess it should stay?? Shaping point at BalDr is not at a road and could probably be replaced by one at nearby Coxtown Rd.  GarHoleRd (https://www.google.com/maps/@37.2722423,-82.2889849,3a,73.7y,300.27h,77.3t/data=!3m6!1e1!3m4!1sQ-D9uKp6U6wgU5hr5VEMMQ!2e0!7i3328!8i1664) seems to be a trail entrance as well.
VA 78:  Main St point should probably stay based on this seeming to be an old US 23 Bus routing.
VA 74:   All of the points are off slightly but 11th St is by far the worst
*VA 72:  The postings around Coeburn show it using Front St (NB) (https://www.google.com/maps/@36.9399334,-82.4717439,3a,90y,295.24h,73.39t/data=!3m6!1e1!3m4!1s15fFy6yEQ16WI0KsmHuM-A!2e0!7i13312!8i6656) and 2nd St (SB) (https://www.google.com/maps/@36.942763,-82.4703395,3a,75y,159.43h,78.08t/data=!3m6!1e1!3m4!1sC-Wk62fQatgQrmPRqMOMQg!2e0!7i13312!8i6656) to the US 58 ALT Bypass then follows that back to VA 72 (https://www.google.com/maps/@36.9404289,-82.4604918,3a,75y,129.49h,81.37t/data=!3m6!1e1!3m4!1sXwEkJC29OHxOVcGYX7BZeQ!2e0!7i13312!8i6656).  (Traffic Logs still show it going through Coeburn via its current routing with VA 158 (http://virginiadot.org/info/resources/Traffic_2015/AADT_198_Coeburn_2015.pdf)). Shaping Point at Edna Rd does not seem to have a good replacement.
*VA 71: Icicle Dr (IciDr (https://www.google.com/maps/@36.6850206,-82.5079932,3a,73.7y,82.03h,72.53t/data=!3m6!1e1!3m4!1szEvnWuSKQGg2dHmew5uKcw!2e0!7i13312!8i6656)) is for a driveway though a point should maybe be added for SR 671 due to the zoo.  Point at Addington St should be moved to SR 680 (https://www.google.com/maps/@36.7496332,-82.4234706,3a,45y,277.32h,71.33t/data=!3m6!1e1!3m4!1sVpDB-Lc3Tkk0rqkURSOdrw!2e0!7i13312!8i6656). Shaping point at SerLn could possibly fit better at nearby SR 686 or SR 611.  SR 784 point (not really a road it seems) should be moved to nearby SR 604 (https://www.google.com/maps/@36.7837212,-82.3257425,0a,75.1y,96.93h,74.33t/data=!3m4!1e1!3m2!1sWYVPKEuULlT2CrRip9pgWA!2e0?source=apiv3).  OldFortCir point could fit at Gray Farm Rd (https://www.google.com/maps/@36.8978884,-82.1220847,3a,73.7y,104.43h,83.2t/data=!3m6!1e1!3m4!1sHvQtvkMzSantjYnC-LJ_WQ!2e0!7i13312!8i6656)??  US19Bus point needs to be recentered.
*VA 69: Is HapRd shaping point label necessary?
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on January 27, 2017, 08:32:32 pm
Just started a two week vacation but will take a look at all feedback when I return.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on January 27, 2017, 09:33:46 pm
Mike-I remember you mentioning the two week vacation.  I am just getting it done now.  This post covers VA 63-VA 39.


VA 63 Truck(St Paul):  This seems to just follow VA 63.  Could this just be deleted entirely?
VA 63: SR616_Haz Point should be changed to SR 657 (https://www.google.com/maps/@36.9901457,-82.2548923,3a,75y,85.16h,88.62t/data=!3m6!1e1!3m4!1sOSoGqGhJWSkg4l6UmADE8A!2e0!7i3328!8i1664).  SR 652 (https://www.google.com/maps/@37.0884248,-82.361406,3a,75y,354.51h,75.26t/data=!3m6!1e1!3m4!1sPvC351FkCr74zc0hytc8OA!2e0!7i3328!8i1664) should maybe be moved to Dyers Chapel Rd though SR 643 should be recentered anyway.
*VA 61: CorHolRd may be a driveway but it is not at the right spot anyway.  LamDr and ChrHolRd seem to be unnecessary shaping points. US 52 points should be S and N instead of E and W.  OldWolfDr should be recentered.
*VA 57: SoaRd should be for Iron Belt Ln (http://virginiadot.org/info/resources/Traffic_2015/AADT_070_Patrick_2015.pdf) (SR 789 (https://www.google.com/maps/@36.7661629,-80.1719006,3a,75y,295.57h,74.14t/data=!3m6!1e1!3m4!1syOx2PtYpbfNIed_-tkSgZw!2e0!7i3328!8i1664)).  A point should be added at SR 701 (https://www.google.com/maps/@36.701855,-79.9324168,3a,75y,204.98h,75.59t/data=!3m6!1e1!3m4!1sNti4Qbg3c920Rf0oYYQBtw!2e0!7i13312!8i6656) near Fieldale. (connects to US 220) Shaping point at OakGroLn should be replaced with one at Hunts Town Rd or SR 612.
*VA 56: Driveways seem to be at NarPasLn. FishHatLn is not at that intersection.  Should NorForkRd just be ForkRd? US29Bus_N should maybe be recentered.  WilCreRd should be MeaCreRd (for SR 604/Meadow Creek Rd (http://virginiadot.org/info/resources/Traffic_2015/AADT_014_Buckingham_2015.pdf)).
*VA 55: Shaping point at BobLn is not at that intersection.  IndRocRd and NatWayLn may be for driveways.  Note that there may be changes necessary soon at the north end of the concurrency with US 340/US 522.
*VA 53: Other points may be fine (JefLakeDr may be a private road) due to tourist attractions, but point at US 15 may need to be recentered unless that is the location of the roundabout currently under construction.
*VA 51:  Maybe try to replace the shaping points with roads that connect to US 58 BUS
*VA 49: Replace shaping point at BurRd with ones at SR 609 (Trottinridge Rd and/or SR 701 (Wilbourne Rd).  Maybe replace shaping point at SubStaRd with one at SR 698 to the south.
*VA 47: RetFarmLn shaping point may be unnecessary, should be for Sunrise Ln anyway 
*VA 46: WooLn seems to just be a driveway
*VA 45: US15/460 point does not reference the BUS routes that VA 45 actually intersects here.  EarSt point could be represented at River Rd nearby. CarRd (Cartersville Rd) should be CarExt (Cartersville Ext (https://www.google.com/maps/@37.657884,-78.0996586,3a,73.7y,43.09h,95.84t/data=!3m6!1e1!3m4!1sKjl1KKfKpX5d-r2_eombdg!2e0!7i3328!8i1664)).
*VA 43: Driveway seems to be at KiraLn.  RockHolRd shaping point should be replaced with one at nearby SR 723 (Skinnell Mill Rd)
*VA 42: US 52 points should be S and N instead of E and W.  (Shaping Points-SkyLarkLn, SprCreRd, NorAve-New Castle)
(Harrisonburg): BraSt shaping point could be replaced with one at SR 720.  MusCreRd point I am unsure what the road name is (I would suggest to just name it SR809 (https://www.google.com/maps/@38.3576789,-79.0292141,3a,75y,261.93h,80.16t/data=!3m6!1e1!3m4!1sY4ZeiFCnMUiqnfhGU0DufQ!2e0!7i13312!8i6656) and recenter.) CanAve point should be changed to reflect MLK Jr Way.  (Shaping Points-RedHillDr, JacTr)
VA 41: VA 293 point needs to be recentered. 
*VA 40: RaiSt (Railroad St) shaping point seems to not be much of a road.   Maybe replace LynAve point (may not be at a road) with one at nearby SR 600 (Dog Creek Rd).  WicRd seems to be a driveway.  Replace VirSt shaping point with one at nearby SR 727.  TwoFarLn should be moved to nearby SR 709.  GrerRd should be GreRd (Greenfield Rd).  OldCreRd should be for Owl Creek Rd (https://www.google.com/maps/@37.0112306,-78.4241122,3a,75y,113.03h,76.09t/data=!3m6!1e1!3m4!1sx5KAwI_ZFFtz9TaILM8k2Q!2e0!7i3328!8i1664).  Should TraRd even be one at all?  ThoDr is not at correct intersection. 
*VA 39: SR 600_S needs to be recentered onto the correct location.  Shaping point at RivRd is not at an intersection.  MareRunTrl (https://www.google.com/maps/@38.0447687,-79.7441804,0a,77.2y,150.11h,71.47t/data=!3m4!1e1!3m2!1sKHBxMoQOrW6y5dh4y5qmvA!2e0?source=apiv3) (I am unsure that this is a public road).  PaxDr label is probably unnecessary.  BraRunRd should just be BraRun (https://www.google.com/maps/@37.9722919,-79.5076902,0a,73.7y,173.79h,81.91t/data=!3m4!1e1!3m2!1s8lQmK24L55_Da1g3wjtbNQ!2e0?source=apiv3). 


Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on January 29, 2017, 04:47:40 pm
This post covers VA 36-VA 13.  The next post will cover the rest.

*VA 36: Should ColAve be VA 327?  Note that points for VA 36 through downtown Petersburg may be tricky. For consistency with VA 144, possibly add a point at Puddledock Rd.
*VA 35: GarHillRd should be GarMillRd (for Garris Mill Rd).  SouSt (for South St) should be moved to nearby Deloatche Ave.
*VA 33: LeaAve should be LeiSt.  Mosby should be MosbySt and should be slightly recentered. Saw some shaping point concerns near Deltaville.
*VA 32:  Consider adding a point or two between the NC/VA line and US 13 (not sure where one could go offhand, obviously any Suffolk points with SRs can be changed).  Shaping point at PemLn could be replaced with one at Everets Rd (https://www.google.com/maps/@36.8516334,-76.5895405,3a,73.7y,292.87h,68.72t/data=!3m6!1e1!3m4!1synEWsHfyE5hW9lOxB7PAQw!2e0!7i13312!8i6656) (old SR 603). Do the points at US 258/VA 10 need to be redone due to the new intersection configuration?
*VA 31: Shaping point at BraSt in Dendron should be replaced with a point at SR 618 (https://www.google.com/maps/@37.0580136,-76.9054105,3a,75y,70.22h,73.3t/data=!3m6!1e1!3m4!1ssmC1DKcIabWjklDV6DF5-g!2e0!7i13312!8i6656) to the northeast.  I would suggest a point at SR 637 on the south side of the ferry if VA 31 was not split into two lists.
*VA 30:  Replace shaping point at Dupont St in West Point with one at nearby Thompson Ave.  Shaping points at Olde Footpath Rd (SR 644) and SR 671 could be replaced with points at SR 604 SB (Dabneys Mill Rd) and SR 604 NB (Herring Creek Rd) respectively.  I am also not sure what name the point for DomPotBlvd (the Kings Dominion point) should be.
*VA 28: Replace shaping point at SR 843 with one at nearby SR 605.  Replace SilCt shaping point with one at the ramp to Wellington Rd. Maybe delete shaping point label at Church St (ChuSt) replaced with a point at the Sudley Rd/Prescott Ave intersection.  Should ManDr (Manassas Dr) be changed to VA 213 despite it being unsigned?  A point should probably be added at New Braddock Rd.
VA 27: Does VA 27 really have two interchanges with VA 244 (or what was VA 244)?
*VA 24: Replace shaping point at 4th St with one at 3rd St (https://www.google.com/maps/@37.2762875,-79.9030948,3a,73.7y,347.97h,80.99t/data=!3m6!1e1!3m4!1sT2czCR4UDhGmeMqEeB-rBw!2e0!7i13312!8i6656) (looks to be a recommended Truck Route).  Replace shaping point at SheDr with one at SR 635 (Lovers Ln) (https://www.google.com/maps/@37.2710599,-79.7666002,3a,73.7y,304.21h,72.06t/data=!3m6!1e1!3m4!1sEw0KCYLsXnFtZK_BoOYoFQ!2e0!7i13312!8i6656).  Maybe replace shaping point at BraRd with one at SR 801 to the west. Point for SR 811 should be for SR 709 (https://www.google.com/maps/@37.2456468,-79.3477432,3a,73.7y,308.29h,74.57t/data=!3m6!1e1!3m4!1s-04G6TW0lsYxpliCOejEQA!2e0!7i13312!8i6656).  Replace shaping point at HalfMoonLn with one at SR 615 (Red House Rd).  Replace VilHwy shaping point with one at nearby SR 646.
VA 20 BUS (Orange): It seems to be that MayFraeAve should be MayFrayAve.
*VA 20: ChaLn seems to be a driveway.  MakRd should maybe be Maxeys Rd (MaxRd). Replace shaping point at PebDr (Private Road) with one at SR 742 (Avon St Ext) or Mill Creek Dr.  StoPoiRd point should be for SR 600 (Watts Passage) (https://www.google.com/maps/@38.1127661,-78.3711731,3a,15y,351.1h,88t/data=!3m6!1e1!3m4!1s8Gn-xY4PKoGQhiORKUu4AQ!2e0!7i13312!8i6656). (BarSetDr-Not a Road) It looks like a point was supposed to be at SR 629(LaHore Rd) (https://www.google.com/maps/@38.2423712,-78.0594723,3a,73.7y,148.94h,87.95t/data=!3m6!1e1!3m4!1sOMql4r5E6l2YBRJarecfwQ!2e0!7i13312!8i6656).  Replace shaping point at OakLakeDr with one at SR 611 to the east.
*VA 18: *(Shaping points should be fine-SR 607, VinePatRd, ParLn).  Maybe replace shaping point at TroSt with one at nearby Pitzer Ridge Rd/Gilliam St. (except that this point already exists at another intersection to the west, maybe call this GillSt)
*VA 16: DoeLn is not at a road.  CarDr point should be moved to Upper Valley Rd (SR 604 (https://www.google.com/maps/@37.0797369,-81.5280454,3a,73.7y,157.54h,68.12t/data=!3m6!1e1!3m4!1s9Aoov_WAu5xmtuavDLyWvQ!2e0!7i3328!8i1664)).
*VA 14: HornHalRd should be for Sand Bank Rd (SR 602 (https://www.google.com/maps/@37.3477541,-76.2908238,3a,73.7y,15.21h,84.04t/data=!3m6!1e1!3m4!1syQawG023NHPhgkqdgmzaWg!2e0!7i13312!8i6656)).  SR606_Glo? In Mathews County.  Switch point at PopGroLn to SR 613 (Beaver Dam Rd).  Suggest replacing shaping point at LoveLn with one at SR 626 (Ridge Rd) nearby.  SR 605 point should be for SR 604 (https://www.google.com/maps/@37.4244522,-76.5056762,3a,73.7y,37.33h,79.85t/data=!3m6!1e1!3m4!1sUD9U_LYiZxt_fDgJT2D3rg!2e0!7i13312!8i6656). (see VA 3). Heartquake Trail and Mill Pond Rd seem to be driveways.
*VA 13: Maybe replace MouMorRd point with maybe one nearby at SR 630.  Maybe replace HatRd shaping point with one at SR 621.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on January 29, 2017, 09:46:42 pm
This post covers VA 10-VA 2.

*VA 10: Shaping point at PemLn could be replaced with one at Everets Rd (https://www.google.com/maps/@36.8516334,-76.5895405,3a,73.7y,292.87h,68.72t/data=!3m6!1e1!3m4!1synEWsHfyE5hW9lOxB7PAQw!2e0!7i13312!8i6656) (old SR 603). Do the points at US 258/VA 32 need to be redone due to the new intersection configuration?  Point at SR 634 (HighGate Rd) needs to be moved to the west slightly (https://www.google.com/maps/@37.1108866,-76.7423366,3a,75y,118.87h,61.35t/data=!3m6!1e1!3m4!1sqFjuP8m4T3dteDCKcQIrPg!2e0!7i13312!8i6656).  The point at VA156Bus_W should be VA156Bus_S.  I remember mentioning before that the shaping point at GillSt would be better served at SR 609 (Old Centralia Rd) or SR 616 (Curtis St/Osborne Rd), but I believe that it was outside tolerance.  Should IroBlvd point (at SR 632) be for SR 632 (Lewis Rd) instead? A point could be added at SR 655 (Beach Rd/Lori Rd). (Maybe SR 604/Courthouse Rd or Whitepine Rd though the latter would only be for the Chesterfield County Airport.)  Note that there are currently no points between VA 288 and VA 150.  Either replace BelRd (W Belmont Rd) point with WBelRd (due to confusion with the nearby Belmont Rd), but a point at Walmsley Blvd seems to be preferable anyway due to a direct connection to VA 150 via Belmont Rd.

VA 9: The VA/WV point needs to be recentered.  Though for WV 9 I noticed a possible extension of WV 115 using its old route east of US 340 but that is its own topic.

*VA 8: Replace MemLn point with one at nearby SR 653.  (no road at RocBraRd)  Replace shaping point at Ashby Dr with one at Wayside Rd nearby.  ParRd point should be moved to Parkview Rd.  (HomRd shaping point should be for Little Camp Rd???)  Replace shaping point at AveLn with one at nearby SR 693. 

VA 7: CityCenPkwy should be CityCenBlvd (https://www.google.com/maps/@39.0359235,-77.4121182,3a,75y,322.37h,75.97t/data=!3m6!1e1!3m4!1s7MweaXqUKBURePtWsYD0qQ!2e0!7i13312!8i6656). Maybe a point at SR 660 (https://www.google.com/maps/@39.1855774,-78.1015192,3a,73.7y,97.11h,81.59t/data=!3m6!1e1!3m4!1sYiub76D3sWufIyXAqVCFSg!2e0!7i13312!8i6656) due to the ramp to/from VA 7 EB.  The points at Piccadilly St and Fairfax Lane (https://www.google.com/maps/@39.1857775,-78.1604498,3a,90y,217.51h,78.06t/data=!3m6!1e1!3m4!1sEkVBZBX06Ghk_5Wsn6XS7Q!2e0!7i13312!8i6656) in Winchester need to be redone due to a roundabout there now.

VA 7 Bus(Purcellville): VA 287 and DryMillRd may need to be recentered.

*VA 6:  Point at SR 640 should be SR 840 (http://virginiadot.org/info/resources/Traffic_2015/AADT_062_Nelson_2015.pdf) (page 32 of PDF-also affects VA 151). VA639 should be SR 639 (https://www.google.com/maps/@37.8215141,-78.7228584,3a,75y,293.66h,78.92t/data=!3m6!1e1!3m4!1s1thmekDBKOIQwy3xmjNXag!2e0!7i3328!8i1664).  SwiDr point is not at a road?  Replace shaping point at Canal St in Scottsville with one nearby at Poplar Spring Rd.  Replace shaping point at SR 651 with one at nearby SR 671 to the west.  Replace point at StoMillRd with one at nearby SR 676.  Maybe add points at West Creek Pkwy just west of VA 288, Lauderdale Dr, and/or Pump Rd.  Is a point preferable at Horsepen Rd or Three Chopt Rd?  Is I-195 point at the right place considering the access to VA 6 only seems to be on the right side?

*VA 5: HarLakeRd label is probably pointless with SR 640 and SR 609 nearby.  Possibly replace shaping point at SR 616 with one nearby at Sturgeon Point Rd (SR 614).  Holly Point Rd is private?  Was the SR 614 done this way on purpose due to the two intersections? Replace shaping point at SaiGeoBlvd with one at SR 615 (Ironbound Rd). (Unsure point-MillNeckRd)

*VA 4: Move shaping point at SunBlvd to nearby SR 616.

*VA 3: SR 605 point should be for SR 604 (https://www.google.com/maps/@37.4244522,-76.5056762,3a,73.7y,37.33h,79.85t/data=!3m6!1e1!3m4!1sUD9U_LYiZxt_fDgJT2D3rg!2e0!7i13312!8i6656). (see VA 14)  VA 200 points should be S and N at duplex. HeaRd is not at an intersection.  SR 602 should be SR 692 (https://www.google.com/maps/@37.8871127,-76.6290368,3a,68.9y,359.28h,82.43t/data=!3m6!1e1!3m4!1sF56-nTjrvAELn_Pf-hr4vA!2e0!7i3328!8i1664).  Possibly move Court Square Point to Polk St (SR 622)  VA 205_E is off the intersection.  (LauLn (not at the intersection) point could be replaced at nearby intersection with Round Hill Rd to the west or SR 647 to the east.  Points at SR 609 and SR 607 look slightly off.  Point at FleOrcRd should be changed to reflect Fletchers Chapel Rd (https://www.google.com/maps/@38.2618321,-77.3317783,3a,73.7y,316.59h,82.68t/data=!3m6!1e1!3m4!1sw3ZtiklVAZCHiiidPBLttg!2e0!7i13312!8i6656).  Replace SheForRd with one at nearby SR 601.  Maybe a point on VA 3 just west of I-95 (definitely Salem Church Rd as it connects to VA 208). (Unsure shaping points that may be at driveways-WooLn, SanSprRd, WinAcrRd)

VA 2:  (includes US 17 Bus)  I am not 100% sure of the routing between VA 3 and US 1 Bus.   
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on February 11, 2017, 02:10:26 pm
I think my biggest confusion with the rules still seems to be the shaping points from what I have seen going through all of these rural VA routes.  (any route with shaping point confusion has an asterisk beside it)

This post contains VA 100 (I found a few issues here)-VA 69.  I did not realize that I could not copy hyperlinks directly from MS Word to here so be forewarned if the links are wrong or if I forgot one.

*VA 100: Shaping point at SR 794 should be for SR 784, but this is probably better served being moved to SR 749 (https://www.google.com/maps/@36.8542181,-80.762717,3a,90y,344.58h,61.78t/data=!3m6!1e1!3m4!1sNZLg-WuUU0HfraJGhng4SA!2e0!7i13312!8i6656). Point at WooFarmRd should be for Pine Run Rd (https://www.google.com/maps/@36.947396,-80.7899343,3a,15y,64.29h,83t/data=!3m6!1e1!3m4!1s5Sr2sXVSnwbKdSm2NSC78A!2e0!7i13312!8i6656).  Shaping Point at TigLn (https://www.google.com/maps/@37.2757284,-80.742366,3a,37.1y,321.05h,80.67t/data=!3m6!1e1!3m4!1sAjB2PBWJ5spnSdKiVkKrQw!2e0!7i3328!8i1664) should be replaced by one at nearby SR 622 to the north.
VA 99: Point at RaiAve should be for RanAve (Randolph Ave) (https://www.google.com/maps/@37.0479209,-80.7847587,3a,75y,91.68h,60.66t/data=!3m6!1e1!3m4!1sy7VImyw0mBjch3CLnN-hPg!2e0!7i13312!8i6656)
*VA 97: Shaping Point at LogLn (for Logans Ln) (https://www.google.com/maps/@36.6202341,-80.8097093,3a,90y,30.43h,73.44t/data=!3m6!1e1!3m4!1s7l2ioX3ISe6f-vXVCoIcTA!2e0!7i3328!8i1664) looks to be just for a driveway and is not at an intersection.
*VA 94: Possibly move shaping point from HorRd to nearby intersection at SR 815 (https://www.google.com/maps/@36.713678,-81.0045642,3a,75y,288.28h,66.53t/data=!3m6!1e1!3m4!1suLABVVTrzfE_E3P0wc8wCQ!2e0!7i13312!8i6656) if doable. Point at LeoRd (for nearby Leonard Rd) should be changed to SR 604 (https://www.google.com/maps/@36.7484769,-80.9868488,3a,75y,210.16h,78.98t/data=!3m7!1e1!3m5!1smHOWsAA-DVOPKu5_-IRLNw!2e0!6s%2F%2Fgeo2.ggpht.com%2Fcbk%3Fpanoid%3DmHOWsAA-DVOPKu5_-IRLNw%26output%3Dthumbnail%26cb_client%3Dmaps_sv.tactile.gps%26thumb%3D2%26w%3D203%26h%3D100%26yaw%3D140.68579%26pitch%3D0%26thumbfov%3D100!7i3328!8i1664) (name looks to be Mount Olive St from GSV but I cannot verify that).  Shaping Point for BulRd (Bullet Rd) is not at the intersection but could maybe be put at nearby SR 602 (https://www.google.com/maps/@36.7861119,-80.9815727,3a,70.5y,4.04h,86.96t/data=!3m6!1e1!3m4!1sBCyvOfosqUohr3Ixsozegw!2e0!7i3328!8i1664). StrHolRd (https://www.google.com/maps/@36.7991024,-80.9908874,0a,95.6y,63.36h,71.82t/data=!3m4!1e1!3m2!1sUoe6PRU-pLGUP4uBjmkBMw!2e0?source=apiv3) shaping point should be moved to nearby SR 738.  Point at SR 658 should maybe be for SR 743 (https://www.google.com/maps/@36.7991024,-80.9908874,0a,95.6y,63.36h,71.82t/data=!3m4!1e1!3m2!1sUoe6PRU-pLGUP4uBjmkBMw!2e0?source=apiv3). 
VA 93:  NC/VA line point needs to be recentered.
VA 92: Should the End point be marked as closed due to the Roanoke River Bridge closure?
VA 91 BUS (Glade Spring): Not sure if the road it intersects at SR 1309 is Crescent Dr or Crescent Rd (according to VDOT Traffic Logs (http://virginiadot.org/info/resources/Traffic_2015/AADT_095_Washington_2015.pdf))
*VA 91: EdmLn label should probably be changed to be for Liberty Hall Dr. The labels for the shaping points at ShaRd and MaiRd could be removed more than likely.  Besides if I drive the gravel section, why would I not do it all at once?
VA 86: Point at College Park Dr (ColParkDr) (https://www.google.com/maps/@36.5626632,-79.405327,3a,73.7y,48.56h,81.27t/data=!3m6!1e1!3m4!1sHMKPZCqByM7e_y4FBchcww!2e0!7i13312!8i6656) is barely off.
*VA 83: Shaping point at Cedar Rd should probably be moved to nearby SR 631 (https://www.google.com/maps/@37.1308761,-82.586369,3a,73.7y,354.76h,71.78t/data=!3m6!1e1!3m4!1sVvgpgfE-dMV8tzy2EETf6Q!2e0!7i13312!8i6656).    Point at SR 750 should be for SR 718 (https://www.google.com/maps/@37.2212189,-82.1459561,3a,75y,78.57h,78.97t/data=!3m6!1e1!3m4!1sOsB-RFRZi5x1bVszCSqXHw!2e0!7i3328!8i1664).  (other unsure shaping points-GolWaveDr and EnoBraRd (this could be moved to nearby SR 642))
*VA 80: Point at RivChuRd should probably be renamed to reflect N Fork River Rd as that is the more important road there it seems.  RavRidRd (https://www.google.com/maps/@36.8647473,-81.9469891,3a,73.7y,176.76h,76.28t/data=!3m6!1e1!3m4!1sKgtEptGdzvRbubEZpgyWpA!2e0!7i13312!8i6656) looks to be a trail entrance/sight-seeing spot so I guess it should stay?? Shaping point at BalDr is not at a road and could probably be replaced by one at nearby Coxtown Rd.  GarHoleRd (https://www.google.com/maps/@37.2722423,-82.2889849,3a,73.7y,300.27h,77.3t/data=!3m6!1e1!3m4!1sQ-D9uKp6U6wgU5hr5VEMMQ!2e0!7i3328!8i1664) seems to be a trail entrance as well.
VA 78:  Main St point should probably stay based on this seeming to be an old US 23 Bus routing.
VA 74:   All of the points are off slightly but 11th St is by far the worst
*VA 72:  The postings around Coeburn show it using Front St (NB) (https://www.google.com/maps/@36.9399334,-82.4717439,3a,90y,295.24h,73.39t/data=!3m6!1e1!3m4!1s15fFy6yEQ16WI0KsmHuM-A!2e0!7i13312!8i6656) and 2nd St (SB) (https://www.google.com/maps/@36.942763,-82.4703395,3a,75y,159.43h,78.08t/data=!3m6!1e1!3m4!1sC-Wk62fQatgQrmPRqMOMQg!2e0!7i13312!8i6656) to the US 58 ALT Bypass then follows that back to VA 72 (https://www.google.com/maps/@36.9404289,-82.4604918,3a,75y,129.49h,81.37t/data=!3m6!1e1!3m4!1sXwEkJC29OHxOVcGYX7BZeQ!2e0!7i13312!8i6656).  (Traffic Logs still show it going through Coeburn via its current routing with VA 158 (http://virginiadot.org/info/resources/Traffic_2015/AADT_198_Coeburn_2015.pdf)). Shaping Point at Edna Rd does not seem to have a good replacement.
*VA 71: Icicle Dr (IciDr (https://www.google.com/maps/@36.6850206,-82.5079932,3a,73.7y,82.03h,72.53t/data=!3m6!1e1!3m4!1szEvnWuSKQGg2dHmew5uKcw!2e0!7i13312!8i6656)) is for a driveway though a point should maybe be added for SR 671 due to the zoo.  Point at Addington St should be moved to SR 680 (https://www.google.com/maps/@36.7496332,-82.4234706,3a,45y,277.32h,71.33t/data=!3m6!1e1!3m4!1sVpDB-Lc3Tkk0rqkURSOdrw!2e0!7i13312!8i6656). Shaping point at SerLn could possibly fit better at nearby SR 686 or SR 611.  SR 784 point (not really a road it seems) should be moved to nearby SR 604 (https://www.google.com/maps/@36.7837212,-82.3257425,0a,75.1y,96.93h,74.33t/data=!3m4!1e1!3m2!1sWYVPKEuULlT2CrRip9pgWA!2e0?source=apiv3).  OldFortCir point could fit at Gray Farm Rd (https://www.google.com/maps/@36.8978884,-82.1220847,3a,73.7y,104.43h,83.2t/data=!3m6!1e1!3m4!1sHvQtvkMzSantjYnC-LJ_WQ!2e0!7i13312!8i6656)??  US19Bus point needs to be recentered.
*VA 69: Is HapRd shaping point label necessary?

all routes not commented upon - made fixes based on suggestions
VA 99 - renamed Rai -> Ran and also moved this point to btw 3rd and 4th and also the one at US 11, since VA 99 has a backwards one-way pair west of US 11.  VA 99 EB uses 4th to US 11 then south to 2nd and thus both directions of VA 99 pass through the US 11 at 3rd intersection where I moved the point (plus did this with US 11 file)
VA 92 - not sure marking the END point as a closed point does anything...didn't know we were even doing this for points where there was no former departure from the route (normally an exit).  If anything, the route should be split into two routes a la VA 125 although since the bridge is still present AFAIK there is theoretical possibility of it being continuous again.  Plus there are people on TM who have driven the bridge (like me!).  Open to hearing other opinions on VA 92...
VA 72 - I elected to keep the routing through Coeburn
VA 69 - a shaping point is needed somewhere so I moved it to SR 608
Title: Re: usava (Virginia State Highways)
Post by: mapcat on February 11, 2017, 02:25:11 pm
VA 92 - not sure marking the END point as a closed point does anything...didn't know we were even doing this for points where there was no former departure from the route (normally an exit).  If anything, the route should be split into two routes a la VA 125 although since the bridge is still present AFAIK there is theoretical possibility of it being continuous again.  Plus there are people on TM who have driven the bridge (like me!).  Open to hearing other opinions on VA 92...
I'd treat this as a closure and split the route at the barricades. It can always be updated if the bridge is reopened.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on February 11, 2017, 04:40:10 pm
Mike, the only route I did not mention that you way want to look at is VA 37 due to the construction at its southern terminus at I-81, but I think it is fine as-is for now until it gets (maybe) an eastern extension to at least US 522.  I met my parents in Winchester a couple weeks ago and saw that the new ramps at that interchange.

My ultimate thought on VA 72 was that as long as you have clinched US 58 ALT and VA 158 around Coeburn, VA 72 is clinched either way.

-Mark
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on February 11, 2017, 10:05:39 pm
Mike-I remember you mentioning the two week vacation.  I am just getting it done now.  This post covers VA 63-VA 39.


VA 63 Truck(St Paul):  This seems to just follow VA 63.  Could this just be deleted entirely?
VA 63: SR616_Haz Point should be changed to SR 657 (https://www.google.com/maps/@36.9901457,-82.2548923,3a,75y,85.16h,88.62t/data=!3m6!1e1!3m4!1sOSoGqGhJWSkg4l6UmADE8A!2e0!7i3328!8i1664).  SR 652 (https://www.google.com/maps/@37.0884248,-82.361406,3a,75y,354.51h,75.26t/data=!3m6!1e1!3m4!1sPvC351FkCr74zc0hytc8OA!2e0!7i3328!8i1664) should maybe be moved to Dyers Chapel Rd though SR 643 should be recentered anyway.
*VA 61: CorHolRd may be a driveway but it is not at the right spot anyway.  LamDr and ChrHolRd seem to be unnecessary shaping points. US 52 points should be S and N instead of E and W.  OldWolfDr should be recentered.
*VA 57: SoaRd should be for Iron Belt Ln (http://virginiadot.org/info/resources/Traffic_2015/AADT_070_Patrick_2015.pdf) (SR 789 (https://www.google.com/maps/@36.7661629,-80.1719006,3a,75y,295.57h,74.14t/data=!3m6!1e1!3m4!1syOx2PtYpbfNIed_-tkSgZw!2e0!7i3328!8i1664)).  A point should be added at SR 701 (https://www.google.com/maps/@36.701855,-79.9324168,3a,75y,204.98h,75.59t/data=!3m6!1e1!3m4!1sNti4Qbg3c920Rf0oYYQBtw!2e0!7i13312!8i6656) near Fieldale. (connects to US 220) Shaping point at OakGroLn should be replaced with one at Hunts Town Rd or SR 612.
*VA 56: Driveways seem to be at NarPasLn. FishHatLn is not at that intersection.  Should NorForkRd just be ForkRd? US29Bus_N should maybe be recentered.  WilCreRd should be MeaCreRd (for SR 604/Meadow Creek Rd (http://virginiadot.org/info/resources/Traffic_2015/AADT_014_Buckingham_2015.pdf)).
*VA 55: Shaping point at BobLn is not at that intersection.  IndRocRd and NatWayLn may be for driveways.  Note that there may be changes necessary soon at the north end of the concurrency with US 340/US 522.
*VA 53: Other points may be fine (JefLakeDr may be a private road) due to tourist attractions, but point at US 15 may need to be recentered unless that is the location of the roundabout currently under construction.
*VA 51:  Maybe try to replace the shaping points with roads that connect to US 58 BUS
*VA 49: Replace shaping point at BurRd with ones at SR 609 (Trottinridge Rd and/or SR 701 (Wilbourne Rd).  Maybe replace shaping point at SubStaRd with one at SR 698 to the south.
*VA 47: RetFarmLn shaping point may be unnecessary, should be for Sunrise Ln anyway 
*VA 46: WooLn seems to just be a driveway
*VA 45: US15/460 point does not reference the BUS routes that VA 45 actually intersects here.  EarSt point could be represented at River Rd nearby. CarRd (Cartersville Rd) should be CarExt (Cartersville Ext (https://www.google.com/maps/@37.657884,-78.0996586,3a,73.7y,43.09h,95.84t/data=!3m6!1e1!3m4!1sKjl1KKfKpX5d-r2_eombdg!2e0!7i3328!8i1664)).
*VA 43: Driveway seems to be at KiraLn.  RockHolRd shaping point should be replaced with one at nearby SR 723 (Skinnell Mill Rd)
*VA 42: US 52 points should be S and N instead of E and W.  (Shaping Points-SkyLarkLn, SprCreRd, NorAve-New Castle)
(Harrisonburg): BraSt shaping point could be replaced with one at SR 720.  MusCreRd point I am unsure what the road name is (I would suggest to just name it SR809 (https://www.google.com/maps/@38.3576789,-79.0292141,3a,75y,261.93h,80.16t/data=!3m6!1e1!3m4!1sY4ZeiFCnMUiqnfhGU0DufQ!2e0!7i13312!8i6656) and recenter.) CanAve point should be changed to reflect MLK Jr Way.  (Shaping Points-RedHillDr, JacTr)
VA 41: VA 293 point needs to be recentered. 
*VA 40: RaiSt (Railroad St) shaping point seems to not be much of a road.   Maybe replace LynAve point (may not be at a road) with one at nearby SR 600 (Dog Creek Rd).  WicRd seems to be a driveway.  Replace VirSt shaping point with one at nearby SR 727.  TwoFarLn should be moved to nearby SR 709.  GrerRd should be GreRd (Greenfield Rd).  OldCreRd should be for Owl Creek Rd (https://www.google.com/maps/@37.0112306,-78.4241122,3a,75y,113.03h,76.09t/data=!3m6!1e1!3m4!1sx5KAwI_ZFFtz9TaILM8k2Q!2e0!7i3328!8i1664).  Should TraRd even be one at all?  ThoDr is not at correct intersection. 
*VA 39: SR 600_S needs to be recentered onto the correct location.  Shaping point at RivRd is not at an intersection.  MareRunTrl (https://www.google.com/maps/@38.0447687,-79.7441804,0a,77.2y,150.11h,71.47t/data=!3m4!1e1!3m2!1sKHBxMoQOrW6y5dh4y5qmvA!2e0?source=apiv3) (I am unsure that this is a public road).  PaxDr label is probably unnecessary.  BraRunRd should just be BraRun (https://www.google.com/maps/@37.9722919,-79.5076902,0a,73.7y,173.79h,81.91t/data=!3m4!1e1!3m2!1s8lQmK24L55_Da1g3wjtbNQ!2e0?source=apiv3).

I agree regarding VA 63 TRUCK.  I have removed it from the .csv files

VA 56 - North Fork Rd is correct (refers to North Fork of Tye River); point location at US 29 Bus Lovingston is ok...it is a Y setup just like the VA 56-151 jct.

VA 53 - point at US 15 was at its location when the 1931 bridge was still open...moved it to current end which is where the circle will also be...
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on February 12, 2017, 07:40:02 am
Quote
VA 56 - North Fork Rd is correct (refers to North Fork of Tye River)

I mentioned this due to what Jim had stated with a point on GA 42 and GA 236 (see below).  In this case, I think your reasoning is justifiable. 

http://tm.teresco.org/forum/index.php?topic=215.msg5100#msg5100 (http://tm.teresco.org/forum/index.php?topic=215.msg5100#msg5100)
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on February 12, 2017, 07:30:57 pm
This post covers VA 36-VA 13.  The next post will cover the rest.

*VA 36: Should ColAve be VA 327?  Note that points for VA 36 through downtown Petersburg may be tricky. For consistency with VA 144, possibly add a point at Puddledock Rd.
*VA 35: GarHillRd should be GarMillRd (for Garris Mill Rd).  SouSt (for South St) should be moved to nearby Deloatche Ave.
*VA 33: LeaAve should be LeiSt.  Mosby should be MosbySt and should be slightly recentered. Saw some shaping point concerns near Deltaville.
*VA 32:  Consider adding a point or two between the NC/VA line and US 13 (not sure where one could go offhand, obviously any Suffolk points with SRs can be changed).  Shaping point at PemLn could be replaced with one at Everets Rd (https://www.google.com/maps/@36.8516334,-76.5895405,3a,73.7y,292.87h,68.72t/data=!3m6!1e1!3m4!1synEWsHfyE5hW9lOxB7PAQw!2e0!7i13312!8i6656) (old SR 603). Do the points at US 258/VA 10 need to be redone due to the new intersection configuration?
*VA 31: Shaping point at BraSt in Dendron should be replaced with a point at SR 618 (https://www.google.com/maps/@37.0580136,-76.9054105,3a,75y,70.22h,73.3t/data=!3m6!1e1!3m4!1ssmC1DKcIabWjklDV6DF5-g!2e0!7i13312!8i6656) to the northeast.  I would suggest a point at SR 637 on the south side of the ferry if VA 31 was not split into two lists.
*VA 30:  Replace shaping point at Dupont St in West Point with one at nearby Thompson Ave.  Shaping points at Olde Footpath Rd (SR 644) and SR 671 could be replaced with points at SR 604 SB (Dabneys Mill Rd) and SR 604 NB (Herring Creek Rd) respectively.  I am also not sure what name the point for DomPotBlvd (the Kings Dominion point) should be.
*VA 28: Replace shaping point at SR 843 with one at nearby SR 605.  Replace SilCt shaping point with one at the ramp to Wellington Rd. Maybe delete shaping point label at Church St (ChuSt) replaced with a point at the Sudley Rd/Prescott Ave intersection.  Should ManDr (Manassas Dr) be changed to VA 213 despite it being unsigned?  A point should probably be added at New Braddock Rd.
VA 27: Does VA 27 really have two interchanges with VA 244 (or what was VA 244)?
*VA 24: Replace shaping point at 4th St with one at 3rd St (https://www.google.com/maps/@37.2762875,-79.9030948,3a,73.7y,347.97h,80.99t/data=!3m6!1e1!3m4!1sT2czCR4UDhGmeMqEeB-rBw!2e0!7i13312!8i6656) (looks to be a recommended Truck Route).  Replace shaping point at SheDr with one at SR 635 (Lovers Ln) (https://www.google.com/maps/@37.2710599,-79.7666002,3a,73.7y,304.21h,72.06t/data=!3m6!1e1!3m4!1sEw0KCYLsXnFtZK_BoOYoFQ!2e0!7i13312!8i6656).  Maybe replace shaping point at BraRd with one at SR 801 to the west. Point for SR 811 should be for SR 709 (https://www.google.com/maps/@37.2456468,-79.3477432,3a,73.7y,308.29h,74.57t/data=!3m6!1e1!3m4!1s-04G6TW0lsYxpliCOejEQA!2e0!7i13312!8i6656).  Replace shaping point at HalfMoonLn with one at SR 615 (Red House Rd).  Replace VilHwy shaping point with one at nearby SR 646.
VA 20 BUS (Orange): It seems to be that MayFraeAve should be MayFrayAve.
*VA 20: ChaLn seems to be a driveway.  MakRd should maybe be Maxeys Rd (MaxRd). Replace shaping point at PebDr (Private Road) with one at SR 742 (Avon St Ext) or Mill Creek Dr.  StoPoiRd point should be for SR 600 (Watts Passage) (https://www.google.com/maps/@38.1127661,-78.3711731,3a,15y,351.1h,88t/data=!3m6!1e1!3m4!1s8Gn-xY4PKoGQhiORKUu4AQ!2e0!7i13312!8i6656). (BarSetDr-Not a Road) It looks like a point was supposed to be at SR 629(LaHore Rd) (https://www.google.com/maps/@38.2423712,-78.0594723,3a,73.7y,148.94h,87.95t/data=!3m6!1e1!3m4!1sOMql4r5E6l2YBRJarecfwQ!2e0!7i13312!8i6656).  Replace shaping point at OakLakeDr with one at SR 611 to the east.
*VA 18: *(Shaping points should be fine-SR 607, VinePatRd, ParLn).  Maybe replace shaping point at TroSt with one at nearby Pitzer Ridge Rd/Gilliam St. (except that this point already exists at another intersection to the west, maybe call this GillSt)
*VA 16: DoeLn is not at a road.  CarDr point should be moved to Upper Valley Rd (SR 604 (https://www.google.com/maps/@37.0797369,-81.5280454,3a,73.7y,157.54h,68.12t/data=!3m6!1e1!3m4!1s9Aoov_WAu5xmtuavDLyWvQ!2e0!7i3328!8i1664)).
*VA 14: HornHalRd should be for Sand Bank Rd (SR 602 (https://www.google.com/maps/@37.3477541,-76.2908238,3a,73.7y,15.21h,84.04t/data=!3m6!1e1!3m4!1syQawG023NHPhgkqdgmzaWg!2e0!7i13312!8i6656)).  SR606_Glo? In Mathews County.  Switch point at PopGroLn to SR 613 (Beaver Dam Rd).  Suggest replacing shaping point at LoveLn with one at SR 626 (Ridge Rd) nearby.  SR 605 point should be for SR 604 (https://www.google.com/maps/@37.4244522,-76.5056762,3a,73.7y,37.33h,79.85t/data=!3m6!1e1!3m4!1sUD9U_LYiZxt_fDgJT2D3rg!2e0!7i13312!8i6656). (see VA 3). Heartquake Trail and Mill Pond Rd seem to be driveways.
*VA 13: Maybe replace MouMorRd point with maybe one nearby at SR 630.  Maybe replace HatRd shaping point with one at SR 621.

VA 36 through Petersburg cannot be done per normal TM guidelines for one-way pairs because of how far apart and non-parallel the alignments are.  I will be leaving its points alone through there (36 EB is concurrent with US 460 Bus which is on a proper one-way pair schematic).

VA 32 - there isn't enough visual information for me to figure out how to rearrange the points for VA 10 ,VA 32, and US 258 at their junction.  I'll have to wait for an updated GMSV to confirm what I think each route does....

VA 27 - yes, 2 interchanges with VA 244



Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on February 12, 2017, 09:11:27 pm
Quote
VA 32 - there isn't enough visual information for me to figure out how to rearrange the points for VA 10 ,VA 32, and US 258 at their junction.  I'll have to wait for an updated GMSV to confirm what I think each route does....

The Isle of Wight County website (http://www.co.isle-of-wight.va.us/transportation/transportation-in-isle-of-wight/transportation-project-management/benns-church-intersection-route-1032258/) shows the true final configuration though I still consider all routes clinched as I am considering it all as one intersection.  I do have two photos from my Christmas Hampton Roads Trip that shows that you have to use Benns Grant Blvd to follow VA 32 SB (also to get to VA 10 EB) from US 258 SB. 

Personally, I think the best option is to put this on hold and maybe to try to sneak by the intersection when you go to Hampton Roads next time.
Title: Re: usava (Virginia State Highways)
Post by: froggie on February 13, 2017, 10:41:18 am
VA 92:  Despite having driven the old bridge as well, I concur with mapcat regarding how to handle this one...a split in the route.

VA 32 at VA 10/US 258:  My read on this is that VA 32 will move to Benns Grant Blvd (the only way to make the connection).  We have precedent for adjusting lists in this situation...namely US 60 in Norfolk.  Only real change to the US 258 and VA 10 lists would be to add points at Benns Grant for VA 32.
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on February 14, 2017, 08:57:38 pm
This post covers VA 10-VA 2.

*VA 10: Shaping point at PemLn could be replaced with one at Everets Rd (https://www.google.com/maps/@36.8516334,-76.5895405,3a,73.7y,292.87h,68.72t/data=!3m6!1e1!3m4!1synEWsHfyE5hW9lOxB7PAQw!2e0!7i13312!8i6656) (old SR 603). Do the points at US 258/VA 32 need to be redone due to the new intersection configuration?  Point at SR 634 (HighGate Rd) needs to be moved to the west slightly (https://www.google.com/maps/@37.1108866,-76.7423366,3a,75y,118.87h,61.35t/data=!3m6!1e1!3m4!1sqFjuP8m4T3dteDCKcQIrPg!2e0!7i13312!8i6656).  The point at VA156Bus_W should be VA156Bus_S.  I remember mentioning before that the shaping point at GillSt would be better served at SR 609 (Old Centralia Rd) or SR 616 (Curtis St/Osborne Rd), but I believe that it was outside tolerance.  Should IroBlvd point (at SR 632) be for SR 632 (Lewis Rd) instead? A point could be added at SR 655 (Beach Rd/Lori Rd). (Maybe SR 604/Courthouse Rd or Whitepine Rd though the latter would only be for the Chesterfield County Airport.)  Note that there are currently no points between VA 288 and VA 150.  Either replace BelRd (W Belmont Rd) point with WBelRd (due to confusion with the nearby Belmont Rd), but a point at Walmsley Blvd seems to be preferable anyway due to a direct connection to VA 150 via Belmont Rd.

VA 9: The VA/WV point needs to be recentered.  Though for WV 9 I noticed a possible extension of WV 115 using its old route east of US 340 but that is its own topic.

*VA 8: Replace MemLn point with one at nearby SR 653.  (no road at RocBraRd)  Replace shaping point at Ashby Dr with one at Wayside Rd nearby.  ParRd point should be moved to Parkview Rd.  (HomRd shaping point should be for Little Camp Rd???)  Replace shaping point at AveLn with one at nearby SR 693. 

VA 7: CityCenPkwy should be CityCenBlvd (https://www.google.com/maps/@39.0359235,-77.4121182,3a,75y,322.37h,75.97t/data=!3m6!1e1!3m4!1s7MweaXqUKBURePtWsYD0qQ!2e0!7i13312!8i6656). Maybe a point at SR 660 (https://www.google.com/maps/@39.1855774,-78.1015192,3a,73.7y,97.11h,81.59t/data=!3m6!1e1!3m4!1sYiub76D3sWufIyXAqVCFSg!2e0!7i13312!8i6656) due to the ramp to/from VA 7 EB.  The points at Piccadilly St and Fairfax Lane (https://www.google.com/maps/@39.1857775,-78.1604498,3a,90y,217.51h,78.06t/data=!3m6!1e1!3m4!1sEkVBZBX06Ghk_5Wsn6XS7Q!2e0!7i13312!8i6656) in Winchester need to be redone due to a roundabout there now.

VA 7 Bus(Purcellville): VA 287 and DryMillRd may need to be recentered.

*VA 6:  Point at SR 640 should be SR 840 (http://virginiadot.org/info/resources/Traffic_2015/AADT_062_Nelson_2015.pdf) (page 32 of PDF-also affects VA 151). VA639 should be SR 639 (https://www.google.com/maps/@37.8215141,-78.7228584,3a,75y,293.66h,78.92t/data=!3m6!1e1!3m4!1s1thmekDBKOIQwy3xmjNXag!2e0!7i3328!8i1664).  SwiDr point is not at a road?  Replace shaping point at Canal St in Scottsville with one nearby at Poplar Spring Rd.  Replace shaping point at SR 651 with one at nearby SR 671 to the west.  Replace point at StoMillRd with one at nearby SR 676.  Maybe add points at West Creek Pkwy just west of VA 288, Lauderdale Dr, and/or Pump Rd.  Is a point preferable at Horsepen Rd or Three Chopt Rd?  Is I-195 point at the right place considering the access to VA 6 only seems to be on the right side?

*VA 5: HarLakeRd label is probably pointless with SR 640 and SR 609 nearby.  Possibly replace shaping point at SR 616 with one nearby at Sturgeon Point Rd (SR 614).  Holly Point Rd is private?  Was the SR 614 done this way on purpose due to the two intersections? Replace shaping point at SaiGeoBlvd with one at SR 615 (Ironbound Rd). (Unsure point-MillNeckRd)

*VA 4: Move shaping point at SunBlvd to nearby SR 616.

*VA 3: SR 605 point should be for SR 604 (https://www.google.com/maps/@37.4244522,-76.5056762,3a,73.7y,37.33h,79.85t/data=!3m6!1e1!3m4!1sUD9U_LYiZxt_fDgJT2D3rg!2e0!7i13312!8i6656). (see VA 14)  VA 200 points should be S and N at duplex. HeaRd is not at an intersection.  SR 602 should be SR 692 (https://www.google.com/maps/@37.8871127,-76.6290368,3a,68.9y,359.28h,82.43t/data=!3m6!1e1!3m4!1sF56-nTjrvAELn_Pf-hr4vA!2e0!7i3328!8i1664).  Possibly move Court Square Point to Polk St (SR 622)  VA 205_E is off the intersection.  (LauLn (not at the intersection) point could be replaced at nearby intersection with Round Hill Rd to the west or SR 647 to the east.  Points at SR 609 and SR 607 look slightly off.  Point at FleOrcRd should be changed to reflect Fletchers Chapel Rd (https://www.google.com/maps/@38.2618321,-77.3317783,3a,73.7y,316.59h,82.68t/data=!3m6!1e1!3m4!1sw3ZtiklVAZCHiiidPBLttg!2e0!7i13312!8i6656).  Replace SheForRd with one at nearby SR 601.  Maybe a point on VA 3 just west of I-95 (definitely Salem Church Rd as it connects to VA 208). (Unsure shaping points that may be at driveways-WooLn, SanSprRd, WinAcrRd)

VA 2:  (includes US 17 Bus)  I am not 100% sure of the routing between VA 3 and US 1 Bus.

All changes have been sent to Jim for updating...

I did the VA 10-32/US 258 changes and split VA 92 into two routes...

Thank you very much for the detailed review...

Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on February 15, 2017, 07:07:14 am
You're welcome.  I have to think yours (and Froggie's) website plus this website for giving me the knowledge to even do something like this. 

Quick notes:  VA 10:  The US258_W point should be US258_S.  Also the US258/32 label should probably be hidden and replaced with US258_N.

US 258:  The VA10_S point should be VA10_E.  My photos from US 258 SB show VA 10 still being posted E-W at this intersection.


-Mark
Title: Re: usava (Virginia State Highways)
Post by: rickmastfan67 on February 26, 2017, 05:13:22 am
mapmikey, I've noticed that when you did some tweaks to WV-55, you didn't port them over to US-48's file.  It seems the problem lies with the 'CoalMineRd' point, as it has different coordinates in each file.  After looking at the files, VA-55's the correct location.  So, porting over that line to US-48's file should eliminate the error mentioned below.

Code: [Select]
va.us048;US48/VA55@+8;;;HIDDEN_JUNCTION;3
=====

Also see 5 other errors on the datacheck page that should be addressed before any possible activation of the system.

Code: [Select]
va.us033;RawSprRd;VA/WV;;VISIBLE_DISTANCE;10.03
va.va039;VA39/VA42Har@+x72;;;HIDDEN_JUNCTION;3
va.va091;+x32;+x40;LitTumRd;SHARP_ANGLE;155.67
va.va091;+x44;+x45;+x49;SHARP_ANGLE;165.30
va.va365eas;VA365;;;LABEL_SELFREF;

If those 'errors' on US-33, VA-91, & VA-365(eas) aren't really errors, let me know and I'll push an update to the FP file for those entries to get them removed. ;)
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on February 26, 2017, 10:33:42 am
I can confirm that VA 91 (sharp switchbacks) and VA 365Eas (branch route off VA 365) are false errors.

I have found a road on the US 33 stretch that can be added as a point...

I have changed the VA 39 file to match VA 42 and the US 48 file to match VA 55...

I will send in to Jim today...

Thanks-
Mike
Title: Re: usava (Virginia State Highways)
Post by: rickmastfan67 on February 26, 2017, 12:11:56 pm
I can confirm that VA 91 (sharp switchbacks) and VA 365Eas (branch route off VA 365) are false errors.

Submitted an update for the FPs for ya. ;)  (Pull Request #1132 (https://github.com/TravelMapping/HighwayData/pull/1132))

-----

Also, I missed this other error in VA that you might want to look into as well:
Code: [Select]
va.i066;I-66/US17/VA55@+x10;;;HIDDEN_JUNCTION;3
Seems to me that the problem here stems with the 'I-66(23)' point on VA-55's file, as the coordinates are different for it from both I-66's and US-17's files.  Looks like to me it would be safe to just copy the coordinates right out of either I-66's or US-17's file for that interchange into VA-55's to fix the problem here.
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on February 26, 2017, 01:56:44 pm
corrected and sent in...
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on March 26, 2017, 03:39:41 pm
Though this will not affect my .list file, I did notice that there were no points on VA 234 between US 29 and its northern terminus at US 15.
Title: Re: usava (Virginia State Highways)
Post by: oscar on March 26, 2017, 05:08:09 pm
There's an intersection with SR 659 near a shaping point, that perhaps could replace that point.
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on April 01, 2017, 02:29:53 pm
I followed Oscar's suggestion and sent in for update...
Title: Re: usava (Virginia State Highways)
Post by: mapcat on May 07, 2017, 04:49:04 pm
What are we waiting on in order to activate this system?
Title: Re: usava (Virginia State Highways)
Post by: froggie on May 07, 2017, 06:24:37 pm
Quote from: mapcat
What are we waiting on in order to activate this system?

Believe we're waiting on a finishing of peer review.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on May 07, 2017, 06:53:13 pm
I was done awhile ago, and I believe Mike did everything.  If he is good with it being activated, then activate it.
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on May 08, 2017, 06:44:50 am
I don't know of any reason not to...

I did field check VA 337 ALT (Portsmouth) this weekend to see how VA 164's completion affected it and I could not determine what they are doing with it...a new posting is east of VA 164's overpass at the intersection of Turnpike and Constitution but there is no arrow (and also no alternate banner either).

Possibilities are it turns left on Constitution to go to VA 141; continues on County to VA 141 on Effingham; continues on County to Elm, then south to connect back with VA 337.

I drove County to Effingham and saw no further shields and also went through the intersection where Elm becomes VA 337 and no signage there either.

Whoever physically activates this system will have to reconcile the several Virginia routes in the state freeways pile...

Title: Re: usava (Virginia State Highways)
Post by: michih on May 30, 2017, 04:17:45 pm
There are some mistakes in usava.csv file:

ERROR: Duplicate list name: VA VA7
ERROR: Duplicate list name: VA VA28
ERROR: Duplicate list name: VA VA168
ERROR: Duplicate list name: VA VA262

https://github.com/TravelMapping/DataProcessing/issues/45#issuecomment-304973676
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on May 30, 2017, 04:26:55 pm
There are some mistakes in usava.csv file:

ERROR: Duplicate list name: VA VA7
ERROR: Duplicate list name: VA VA28
ERROR: Duplicate list name: VA VA168
ERROR: Duplicate list name: VA VA262

https://github.com/TravelMapping/DataProcessing/issues/45#issuecomment-304973676

Are we sure that these are not just the ones that were originally in usansf (which all of the usava ones need to be removed from) before usava was created?
Title: Re: usava (Virginia State Highways)
Post by: Jim on May 30, 2017, 04:58:49 pm
I believe these are because of the entries in both usava and usansf.

What are we waiting on to be able to activate usava and get this recurring problem behind us?
Title: Re: usava (Virginia State Highways)
Post by: mapmikey on May 30, 2017, 08:34:17 pm
Should I just update the .csv files with the full Virginia set and make sure the .wpt files have the entire waypoint list?  Then take the two usansf.csv files and delete the Virginia entries from them?  Would this take care of the reconciliation part of the activation or is there more to fixing that aspect of it?

Title: Re: usava (Virginia State Highways)
Post by: Jim on May 30, 2017, 08:39:05 pm
Should I just update the .csv files with the full Virginia set and make sure the .wpt files have the entire waypoint list?  Then take the two usansf.csv files and delete the Virginia entries from them?  Would this take care of the reconciliation part of the activation or is there more to fixing that aspect of it?

That sounds right.  I'll take care of it now.
Title: Re: usava (Virginia State Highways)
Post by: Jim on May 30, 2017, 08:53:54 pm
Minor note: VA 199 in usansf has a point in use for OldYorkRd that is not in the usava version, so I'm adding it.
Title: Re: usava (Virginia State Highways)
Post by: Markkos1992 on May 30, 2017, 10:18:22 pm
Quote
VA 199 I previously addressed by eliminating the point
Minor note: VA 199 in usansf has a point in use for OldYorkRd that is not in the usava version, so I'm adding it.

I think I had caught an error with that, and Mike took that point out in usava but not in usansf.


Mike, please correct if I am wrong.

EDIT:  Froggie had mentioned this as well.
Quote
VA 199:  Old York Rd (east of I-64) is now Water Country Pkwy.

Quote
VA 199 I previously addressed by eliminating the point

This was Mike's response to Froggie so I am pretty sure that this point should not have been added back.

Title: Re: usava (Virginia State Highways)
Post by: mapcat on May 30, 2017, 10:23:18 pm
Thanks for finally activating this! Good to see the log errors are gone.
Title: Re: usava (Virginia State Highways)
Post by: dfilpus on May 31, 2017, 05:31:53 pm
SR 7100 was renumbered to VA 286. It is in the system under both numbers. va.sr7100 should be removed from the system and added as a former label for va.va286
Title: Re: usava (Virginia State Highways)
Post by: Jim on May 31, 2017, 05:59:45 pm
SR 7100 was renumbered to VA 286. It is in the system under both numbers. va.sr7100 should be removed from the system and added as a former label for va.va286

I'll take care of this for tonight's update, thanks.
Title: Re: usava (Virginia State Highways)
Post by: bejacob on May 31, 2017, 09:36:27 pm
Thanks for finally activating this! Good to see the log errors are gone.

For the first time in ages, my log file has no errors.  :)