Travel Mapping

Highway Data Discussion => Updates to Highway Data => Topic started by: rickmastfan67 on February 27, 2025, 03:52:31 am

Title: OR: OR-217 labeling issue
Post by: rickmastfan67 on February 27, 2025, 03:52:31 am

2A(OR8) -> 2A
2C(OR10) -> 2

We shouldn't be having full route labels in the '()' part.

Also, the graph connection is currently broken between OR-10 & OR-217 & needs to be fixed.

Code: [Select]

or.or010 OR217 (45.486553,-122.792881) NMP or.or217 2C(OR10) (45.486538,-122.792881)
or.or217 2C(OR10) (45.486538,-122.792881) NMP or.or010 OR217 (45.486553,-122.792881)

Title: Re: OR: OR-217 labeling issue
Post by: Bickendan on February 28, 2025, 08:04:24 pm

Those tags are a holdover from the original draft back on CHM.
Also, OR 8 should be 2, and OR 10 should be 2A; reversed 0 point for most non-Interstate north-south Oregon highways.

Title: Re: OR: OR-217 labeling issue
Post by: rickmastfan67 on February 28, 2025, 08:37:24 pm

Quote from: Bickendan on February 28, 2025, 08:04:24 pm

Also, OR 8 should be 2, and OR 10 should be 2A; reversed 0 point for most non-Interstate north-south Oregon highways.

I only mentioned it that way due to what the current labels were.  If you want to flip them when you submit the fix, then even better. :)

Title: Re: OR: OR-217 labeling issue
Post by: Bickendan on March 02, 2025, 10:21:09 pm

I think I labeled the two points the way I did because they're both signed as 2A, but far enough that they needed two points and needed disambiguation.

They should have been
2A(OR8)
2A(OR10)

but I'm going to go with
2A_N
2A_S
as that fits better with our labeling practices.

Title: Re: OR: OR-217 labeling issue
Post by: Bickendan on March 02, 2025, 10:22:19 pm

Fixed locally, including the graph connection.