Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: the_spui_ninja on April 12, 2024, 11:20:30 am

Title: ND: Bismarck Expressway (usasf)
Post by: the_spui_ninja on April 12, 2024, 11:20:30 am

Quote from: neroute2 on April 11, 2024, 12:07:54 am

There is also one on ND 810 in Bismarck (west end (https://www.google.com/maps/@46.8222669,-100.8473991,3a,27.4y,154.66h,88.39t/data=!3m6!1e1!3m4!1s9ky_H5QTULoOUkguICQm5g!2e0!7i16384!8i8192?entry=ttu), east end (https://www.google.com/maps/@46.7961105,-100.7818152,3a,26y,208.87h,91.38t/data=!3m6!1e1!3m4!1sxCpHdjxGccouWLEVOcCUXw!2e0!7i16384!8i8192?entry=ttu)). Finally this freeway gets added :)

Don't know why I never added this to usasf before. I'm planning to add in the freeway segment (west of Washington Street); should I add it as nd.nd810 (only to I-194) or as nd.bisexpy (all the way to I-94)?

Title: Re: ND: Bismarck Expressway (usasf)
Post by: vdeane on April 12, 2024, 12:52:55 pm

nd.bisexpy would probably be best to match signage.

Title: Re: ND: Bismarck Expressway (usasf)
Post by: the_spui_ninja on April 12, 2024, 02:05:58 pm

Quote from: vdeane on April 12, 2024, 12:52:55 pm

nd.bisexpy would probably be best to match signage.

That's what I thought too, just wanted to see if anyone was particular about the unsigned designation. Will add as nd.bisexpy unless there are objections.