Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Bickendan on November 07, 2016, 01:49:10 am

Title: WA 100
Post by: Bickendan on November 07, 2016, 01:49:10 am

Just clinched WA 100 tonight.
There are two segments, both bannered: The segment we have in the browser is signed as SR 100 Loop (no directional banners), and a short SR 100 Spur from the southern most point to Fort Canby. That point, BeaHolSP, needs to renamed to WA100Spur and the BeaHolSP tag hidden to prevent any .list breaks.
WA 100 Spur Ilwaco needs to be added to the system.
To reiterate:
WA100 -> WA100Loop Ilwaco
BeaHolSP -> WA100Spur +BeaHolSP
Create: WA100Spur Ilwaco, points at WA100Loop and FtCan

Title: Re: WA 100
Post by: mapcat on November 07, 2016, 10:32:04 am

Nobody is currently responsible for Washington, so go for it.

Title: Re: WA 100
Post by: yakra on November 07, 2016, 02:03:26 pm

What to use in the CSV banner field for "loop"?

Title: Re: WA 100
Post by: Jim on November 07, 2016, 04:03:44 pm

Quote from: yakra on November 07, 2016, 02:03:26 pm

What to use in the CSV banner field for "loop"?

Looks like this would be the first example, so I guess it's time to pick something.  I can verify that the DB field is 3 characters, so I'd say "Lp" makes the most sense.  Better than "Loo" or "Lop".

Title: Re: WA 100
Post by: dfilpus on November 07, 2016, 04:45:17 pm

The last time I checked WA 100 Spur was not signed. It is signed now, so it should be added. WA 100 Loop is signed as vanilla WA 100 at US 101. Its reassurance signs have Loop banners. I would leave wa100.wpt as is and add wa100sprfor.wpt for WA 100 Spur Fort Canby.

Title: Re: WA 100
Post by: mapcat on November 07, 2016, 07:05:17 pm

Regardless of how WA 100 is signed, it would still be good to have a "Loop" banner, especially for usaga. Unless we want to do special templates for the usaga loops, since I believe most are signed with "Loop" inside the Georgia outline.

Title: Re: WA 100
Post by: yakra on November 07, 2016, 11:18:12 pm

Quote from: Jim on November 07, 2016, 04:03:44 pm

Looks like this would be the first example, so I guess it's time to pick something.  I can verify that the DB field is 3 characters, so I'd say "Lp" makes the most sense.  Better than "Loo" or "Lop".

At least the second example, actually:
usaok;OK;OK56;Lp;Okm;Okmulgee;ok.ok056lpokm;
So that precedent being set, along with the same "Lp" abbreviation being used throughout Texas, I second "Lp."

Quote from: mapcat on November 07, 2016, 07:05:17 pm

Regardless of how WA 100 is signed, it would still be good to have a "Loop" banner, especially for usaga. Unless we want to do special templates for the usaga loops, since I believe most are signed with "Loop" inside the Georgia outline.

I also think having a Loop banner is a good idea; more of these could show up. CHM has a Loop banner in use for the above route: cmap.m-plex.com/hb/hwymap.php?r=ok.ok056lpokm
I'll stay officially neutral re special shield templates.

Title: Re: WA 100
Post by: compdude787 on November 12, 2016, 03:32:30 pm

Quote from: mapcat on November 07, 2016, 10:32:04 am

Nobody is currently responsible for Washington, so go for it.

As I've mentioned previously, I'd be more than happy to take over maintenance for WA.

Title: Re: WA 100
Post by: compdude787 on December 17, 2016, 01:21:03 am

Finally did a pull request for this: https://github.com/TravelMapping/HighwayData/pull/1009