Travel Mapping

Highway Data Discussion => Updates to Highway Data => Solved Highway data updates => Topic started by: yakra on November 17, 2020, 02:18:11 pm

Title: OR: duplicate label breaks .list file
Post by: yakra on November 17, 2020, 02:18:11 pm

Quote from: imgoph.log (https://travelmapping.net/logs/users/imgoph.log)

OR: duplicate label 32NDST in or.us101. Please report this error in the TravelMapping forum. Unable to parse line: OR US101 32ndSt BroRd

There's a collision between the 32ndSt point and AbaSt, which has +32ndSt as an AltLabel.
At the time imgoph's .list line was created, only the one corresponding to AbaSt existed.
Suggest keeping the old one as an AltLabel, and deleting the new standalone 32ndSt point, which is not in use or necessary for shaping. Visible waypoints in that area are already a bit overdense. If you want to retain access in that general area, +x63 could be replaced with HighSchDr (http://www.openstreetmap.org/?lat=44.939141&lon=-124.022067). +x64 isn't really needed either.

All of Oregon's datacheck errors:
https://travelmapping.net/devel/datacheck.php?rg=OR&showmarked=1
(Only 4 of `em, though the OR255 one reveals issues a bit deeper than it 1st appears...)

Title: Re: OR: duplicate label breaks .list file
Post by: Bickendan on February 12, 2021, 07:55:33 am

Fixed and submitted.

Title: Re: OR: duplicate label breaks .list file
Post by: Bickendan on February 12, 2021, 08:15:19 am

Before I mark this as solved... can someone figure out why the OR 22 point +x1(OR99EBus) is flagged as a hidden junction? It's the same point as OR 99EB's +x1(OR22) point.

The OR 39 self-reference flag is a false positive.

Title: Re: OR: duplicate label breaks .list file
Post by: rickmastfan67 on February 12, 2021, 08:45:26 am

Quote from: Bickendan on February 12, 2021, 08:15:19 am

Before I mark this as solved... can someone figure out why the OR 22 point +x1(OR99EBus) is flagged as a hidden junction? It's the same point as OR 99EB's +x1(OR22) point.

Simple, the following two points aren't synced with each other:
or.or022: OR99EBus
or.or099ebussal: OR22

Because of that, the first point both routes share the coordinates is that hidden point.  Thus, triggering the error.

Title: Re: OR: duplicate label breaks .list file
Post by: yakra on February 12, 2021, 10:14:07 am

Quote from: https://travelmapping.net/devel/manual/syserr.php#HIDDEN_JUNCTION

Concurrent route splits off at a hidden waypoint. The concurrency is most likely broken by accident, or the waypoint needs to be visible.

Title: Re: OR: duplicate label breaks .list file
Post by: michih on February 12, 2021, 01:48:15 pm

@Bickendan, the link to the error description provided by yakra is on the error cell: https://travelmapping.net/devel/datacheck.php?rg=OR

Title: Re: OR: duplicate label breaks .list file
Post by: Bickendan on February 15, 2021, 02:39:01 am

Hopefully my submission will fix it. Leaving it unsolved for the moment.

Title: Re: OR: duplicate label breaks .list file
Post by: rickmastfan67 on February 15, 2021, 02:40:49 am

Quote from: Bickendan on February 15, 2021, 02:39:01 am

Hopefully my submission will fix it. Leaving it unsolved for the moment.

As long as you synced these two points

Code: [Select]

or.or022: OR99EBus
or.or099ebussal: OR22you should be good to go. ;)

Title: Re: OR: duplicate label breaks .list file
Post by: rickmastfan67 on May 20, 2021, 11:56:28 pm

Quote from: rickmastfan67 on February 15, 2021, 02:40:49 am

Quote from: Bickendan on February 15, 2021, 02:39:01 am

Hopefully my submission will fix it. Leaving it unsolved for the moment.

As long as you synced these two points

Code: [Select]

or.or022: OR99EBus
or.or099ebussal: OR22you should be good to go. ;)

Don't see this error anymore.  So, we can mark it as solved. ;)