Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: rickmastfan67 on December 30, 2020, 02:15:51 am

Title: NC: US-15/401/501 offset point issues
Post by: rickmastfan67 on December 30, 2020, 02:15:51 am

US-15:
US15Bus_S --- offset a good distance from the intersection.  Needs to be recentered.  Also affect US401, US15BusLau, & US401BusLau.  Could also be renamed as well in both US-15 & US-401's files to US15/401Bus.
NC144 --- this needs to be recentered, as they build a brand new roundabout to the north of the original intersection.  This will also effect US501 & NC144.

US-401:
US401BusLau -> US401BusLau_N --- Also needs to be recentered too. Would affect US401BusLau as well.

Title: Re: NC: US-15/401/501 offset point issues
Post by: mapmikey on February 04, 2021, 08:43:52 pm

fixed and in the queue

Title: Re: NC: US-15/401/501 offset point issues
Post by: Markkos1992 on February 06, 2021, 01:05:44 pm

It looks like the US 15 label is now just "US" instead of US15/401Bus.

Title: Re: NC: US-15/401/501 offset point issues
Post by: rickmastfan67 on February 06, 2021, 02:29:52 pm

Quote from: Markkos1992 on February 06, 2021, 01:05:44 pm

It looks like the US 15 label is now just "US" instead of US15/401Bus.

Plus I don't think the point is in the correct place.  IMO, it should be at the traffic light.

Title: Re: NC: US-15/401/501 offset point issues
Post by: Markkos1992 on February 06, 2021, 02:47:12 pm

Actually the issue is that the line ended up being  "US +15/401Bus +US15Bus_S".  So "15/401Bus" is now a hidden alternate label under "US".

Title: Re: NC: US-15/401/501 offset point issues
Post by: rickmastfan67 on February 06, 2021, 03:32:38 pm

Quote from: Markkos1992 on February 06, 2021, 02:47:12 pm

Actually the issue is that the line ended up being  "US +15/401Bus +US15Bus_S".  So "15/401Bus" is now a hidden alternate label under "US".

I know.  That's why I said 'plus'.

Title: Re: NC: US-15/401/501 offset point issues
Post by: mapmikey on February 09, 2021, 05:09:38 pm

fixed the error

Title: Re: NC: US-15/401/501 offset point issues
Post by: Markkos1992 on February 28, 2021, 04:12:25 pm

I want to note here that the use of US15/401Bus created a self-reference error for US 15.  I presume that we will just consider it a FP, but I did want to note that.

EDIT (3-2-2021):  https://github.com/TravelMapping/HighwayData/pull/4592 (added FP)

Title: Re: NC: US-15/401/501 offset point issues
Post by: yakra on March 02, 2021, 04:30:28 pm

Quote from: Markkos1992 on February 28, 2021, 04:12:25 pm

I want to note here that the use of US15/401Bus created a self-reference error for US 15.  I presume that we will just consider it a FP, but I did want to note that.

Overall, LABEL_SELFREF needs some attention (https://github.com/TravelMapping/DataProcessing/issues?q=is%3Aissue+is%3Aopen+label%3ALABEL_SELFREF)...
What we have here is (US15/401)(Bus) rather than (US15)/(401Bus).
There are a lot of these cases in HighwayData; it makes sense to continue to allow them, and not force a bunch of conversions to US15Bus/401Bus.
Perhaps in the future, these could be detected and not flagged, and we won't have to worry about marking the FPs.
https://github.com/TravelMapping/DataProcessing/issues/420

As an aside, I dislike the ambiguity in US15/401Bus style on the one hand and the lack of brevity in US15Bus/401Bus on the other (still think they should be allowed though), and resolve these cases by just going with US15Bus.