Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: ntallyn on February 18, 2021, 09:50:31 pm

Title: FL 112 and FL 953
Post by: ntallyn on February 18, 2021, 09:50:31 pm

FL 112 and FL 953 don't share any pavement, yet have separate points for FL953_N and FL953_S (on FL112), and FL112_S and FL112_N (on FL953)

I believe the FL953_S point on FL112 (and the matching FL112_S point on FL953) only covers a single movement (southbound FL 953 to westbound FL112 for airport access), and should be removed/hidden. Incidentally, FL112 is marked as E/W, so if the points are not combined, the FL112 points on FL953 should be renamed.

Title: Re: FL 112 and FL 953
Post by: Markkos1992 on February 19, 2021, 11:37:51 am

Minus the renaming of the FL 112 points on FL 953, I think the points are fine as-is.

Title: Re: FL 112 and FL 953
Post by: rickmastfan67 on February 20, 2021, 09:23:41 am

0.5 miles apart, lots of partial interchanges in that area as well.  I honestly see no issues to how I did this.

Quote from: Markkos1992 on February 19, 2021, 11:37:51 am

Minus the renaming of the FL 112 points on FL 953, I think the points are fine as-is.

Yeah, I think I could rename them to _W & _E.

Fixed in my local copy.

Title: Re: FL 112 and FL 953
Post by: rickmastfan67 on February 27, 2021, 05:39:17 am

Now submitted.
https://github.com/TravelMapping/HighwayData/pull/4581