Author Topic: AUT: B65 / B319  (Read 5465 times)

0 Members and 1 Guest are viewing this topic.

Offline Duke87

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1018
  • Last Login:November 20, 2024, 06:49:51 pm
AUT: B65 / B319
« on: March 11, 2024, 05:24:23 pm »
B65 needs to be split into two routes. The segment that's also mapped as B319 is only signed as B319 and not as B65 (can confirm by field check).

Online neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1141
  • Last Login:Today at 01:14:03 am
Re: AUT: B65 / B319
« Reply #1 on: March 11, 2024, 06:20:26 pm »
But it's signed on either end of B319? Sounds like an "unsigned but implied" overlap, despite the strangeness of B319 only existing there: https://travelmapping.net/devel/manual/hwydata.php

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4849
  • Last Login:November 20, 2024, 11:21:09 am
Re: AUT: B65 / B319
« Reply #2 on: March 13, 2024, 12:09:30 pm »
Exactly. It's an implied multiplex. I think that mapcat and me defined the same logic back then. From the top of my head: We keep it as one route if the routing is clear, the number is not changing on the concurrency, and if the overlap is not noticeably longer than the shortest remainder. I rawly followed that "unwritten rule".

B65 is an implied multiplex according to that. Closing.