Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: yakra on November 07, 2019, 03:11:36 pm

Title: TN: Foothills Parkway, Great Smoky Mtns NP
Post by: yakra on November 07, 2019, 03:11:36 pm

Back in 2012ish when AltRouteNames were implemented, we moved away from directional suffixes to disambiguate route segments, instead using Abbrevs & Cities. For example, NS104_E became NS104Por.
Suggest...
usanp;TN;FooPkwyW;;;Foothills Parkway, Great Smoky Mtns NP (West);tn.foopkwyw;
usanp;TN;FooPkwyE;;;Foothills Parkway, Great Smoky Mtns NP (East);tn.foopkwye;
->
usanp;TN;FooPkwy;;;Foothills Parkway, Great Smoky Mtns NP (Main);tn.foopkwyw;FooPkwyW
usanp;TN;FooPkwy;;Cos;Foothills Parkway, Great Smoky Mtns NP (Cosby);tn.foopkwye;FooPkwyE

Title: Re: TN: Foothills Parkway, Great Smoky Mtns NP
Post by: mapcat on November 11, 2019, 09:03:55 pm

https://github.com/TravelMapping/HighwayData/pull/3301 (https://github.com/TravelMapping/HighwayData/pull/3301)

(with corrected names for new roots)

Title: Re: TN: Foothills Parkway, Great Smoky Mtns NP
Post by: yakra on November 19, 2019, 06:08:08 pm

Oops, goofed that bit. Glad you picked up on it.

Title: Re: TN: Foothills Parkway, Great Smoky Mtns NP
Post by: compdude787 on May 14, 2020, 12:54:58 am

This has been solved, right?