Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: Jim on June 05, 2022, 10:44:26 pm

Title: AL: NMPs
Post by: Jim on June 05, 2022, 10:44:26 pm

Looks like the current unmarked NMPs are really just in two locations.  There's a set of 3 in Tuskegee that might be better to simplify (and it looks like some non-standard labels there also).  Then the points in Birmingham where I-20/I-59/US 31/US 280 all meet should be matched.  I'll make the latter change soon unless I hear an objection.  I'd like to get that graph connection.

Title: Re: AL: NMPs
Post by: clong on June 09, 2022, 05:44:38 pm

I think this will clear up the I-20/59, end 280, 31 not having an intersection with I-20/59 mystery:
https://www.google.com/maps/@33.5210185,-86.7993744,3a,75y,347.51h,89.71t/data=!3m6!1e1!3m4!1sx5mnHU4Pwjy8hu6AxbYrmQ!2e0!7i16384!8i8192 (https://www.google.com/maps/@33.5210185,-86.7993744,3a,75y,347.51h,89.71t/data=!3m6!1e1!3m4!1sx5mnHU4Pwjy8hu6AxbYrmQ!2e0!7i16384!8i8192)

I don't know all the Travel Mapping interchange rules, but that Google Street View shows where US280 ends and drivers make a choice to go 31 or to I-20/59.

Title: Re: AL: NMPs
Post by: froggie on June 14, 2022, 11:48:03 am

Cleaned up 20/59/31/280 NMP today.

Explained the Tuskegee situation in another thread and why I did things the way I did, though I cleaned up the AL 81 labels.  Label this as FP.

Title: Re: AL: NMPs
Post by: michih on October 15, 2022, 11:29:37 am

Quote from: froggie on June 14, 2022, 11:48:03 am

Explained the Tuskegee situation in another thread and why I did things the way I did, though I cleaned up the AL 81 labels.  Label this as FP.

If so, I think that you just need to copy these lines

Code: [Select]

al.al081 US29/80 (32.423614,-85.690489) NMP al.us029 AL81_N (32.423863,-85.690066) al.us080 AL81_N (32.423863,-85.690066) al.us080 AL81_S (32.423352,-85.690924)
al.us029 AL81_N (32.423863,-85.690066) NMP al.al081 US29/80 (32.423614,-85.690489) al.us029 US80_W (32.423614,-85.690489) al.us080 US29_S (32.423614,-85.690489)
al.us029 US80_W (32.423614,-85.690489) NMP al.us029 AL81_N (32.423863,-85.690066) al.us080 AL81_N (32.423863,-85.690066) al.us080 AL81_S (32.423352,-85.690924)
al.us080 AL81_N (32.423863,-85.690066) NMP al.al081 US29/80 (32.423614,-85.690489) al.us029 US80_W (32.423614,-85.690489) al.us080 US29_S (32.423614,-85.690489)
al.us080 AL81_S (32.423352,-85.690924) NMP al.al081 US29/80 (32.423614,-85.690489) al.us029 US80_W (32.423614,-85.690489) al.us080 US29_S (32.423614,-85.690489)
al.us080 US29_S (32.423614,-85.690489) NMP al.us029 AL81_N (32.423863,-85.690066) al.us080 AL81_N (32.423863,-85.690066) al.us080 AL81_S (32.423352,-85.690924)
to https://github.com/TravelMapping/HighwayData/blob/master/nmpfps.log so that we can close the issue.

Title: Re: AL: NMPs
Post by: froggie on October 15, 2022, 04:32:36 pm

I have no idea what I'm looking at there.

Title: Re: AL: NMPs
Post by: Jim on October 15, 2022, 08:04:22 pm

I've got these in for tonight, thanks.

Title: Re: AL: NMPs
Post by: michih on October 20, 2022, 03:46:11 pm

Done (https://github.com/TravelMapping/HighwayData/commit/ed8d49943a608bbae59c37a6b897438511f4b702). Closing.