Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Markkos1992 on October 27, 2024, 10:24:51 pm

Title: VA: VA 379 Parking Lot Leg
Post by: Markkos1992 on October 27, 2024, 10:24:51 pm

Since this entrance is signed, should there be a second segment of VA 379 here into the parking lot? (https://www.google.com/maps/@36.6736233,-76.9390328,3a,79.4y,70.19h,85.81t/data=!3m6!1e1!3m4!1sw99iKmzuU2UOFIKPinUsiA!2e0!7i13312!8i6656!5m1!1e1?coh=205409&entry=ttu&g_ep=EgoyMDI0MTAyMy4wIKXMDSoASAFQAw%3D%3D)

Title: Re: VA: VA 379 Parking Lot Leg
Post by: mapmikey on January 28, 2025, 08:41:26 pm

route added

Title: Re: VA: VA 379 Parking Lot Leg
Post by: michih on February 02, 2025, 01:41:57 am

@mapmikey, the site update failed:

Quote

1: Abbrev > 3 bytes in usava.csv line: usava;VA;VA379;;Main;Main Entrance;va.va379main;

Title: Re: VA: VA 379 Parking Lot Leg
Post by: rickmastfan67 on February 02, 2025, 03:02:29 am

Quote from: michih on February 02, 2025, 01:41:57 am

@mapmikey, the site update failed:

Quote

1: Abbrev > 3 bytes in usava.csv line: usava;VA;VA379;;Main;Main Entrance;va.va379main;

Also, shouldn't it be 'va.va379mai' instead since we don't go 4 letters on the route abbreviations?

Title: Re: VA: VA 379 Parking Lot Leg
Post by: michih on February 02, 2025, 03:42:05 am

An alt route name is also wrong:

usava;VA;VA43;;;;va.va043;va.peard
->
usava;VA;VA43;;;;va.va043;PeaRd

Title: Re: VA: VA 379 Parking Lot Leg
Post by: mapmikey on February 02, 2025, 10:17:51 am

corrected .csv files submitted to Jim

Title: Re: VA: VA 379 Parking Lot Leg
Post by: Jim on February 02, 2025, 11:41:53 am

And the site update has now successfully completed.

Title: Re: VA: VA 379 Parking Lot Leg
Post by: rickmastfan67 on February 02, 2025, 05:42:00 pm

Quote from: Jim on February 02, 2025, 11:41:53 am

And the site update has now successfully completed.

News entries weren't updated for VA-379.  Also, NC I-74's news entry was referencing the wrong I-74 segment.  I've gone ahead and submitted a fix for those so they link to the correct files. ;)

https://github.com/TravelMapping/HighwayData/pull/8138