usava (Virginia State Highways)

[oscar]

There's an intersection with SR 659 near a shaping point, that perhaps could replace that point.

[mapmikey]

I followed Oscar's suggestion and sent in for update...

[mapcat]

What are we waiting on in order to activate this system?

[froggie]

What are we waiting on in order to activate this system?

Believe we're waiting on a finishing of peer review.

[Markkos1992]

I was done awhile ago, and I believe Mike did everything.  If he is good with it being activated, then activate it.

[mapmikey]

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...

[michih]

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

[Markkos1992]

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?

[Jim]

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?

[mapmikey]

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?

[Jim]

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.

[Jim]

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.

[Markkos1992]

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.

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

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.

[mapcat]

Thanks for finally activating this! Good to see the log errors are gone.

[dfilpus]

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