Author Topic: HUN: Issues introduced with recent M30 opening  (Read 1293 times)

0 Members and 1 Guest are viewing this topic.

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4573
  • Last Login:Yesterday at 10:17:38 am
HUN: Issues introduced with recent M30 opening
« on: October 29, 2021, 10:15:12 am »
@panda80!

https://github.com/TravelMapping/HighwayData/pull/5258

I already fixed two issues but there are still more I cannot "simply" fix, i.e. should be fixed by you:
  • F306 truncation needs an update entry
  • Should the F3/M30 junction be a one-point-per-interchange?
  • E71's wp 29(M30) matches F3's + E79's H3605 wp but the wp is missing on concurrent M30. If we go with 1PPI, the issue would be solved, and F3's M30 wp could be renamed to M30(29) which is currently an alt label.
  • Should E71 be moved onto M30?
  • Should E79 be extended at north end?
  • F3 misses a wp for M30's exit 39
  • M30's wp 73 is off
  • F3's wp H2627 is off (at M30's 73 exit)
  • F3's wp H2624/H3703 is off and might be renamed to M30(51)
  • M30's wp F3Her should be renamed to 80, shouldn't it? If so, F3's M30Her -> M30(80)

I hope it's all.

btw: Maybe E66 should be moved onto M80 too?

Offline si404

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1982
  • Last Login:Today at 06:40:35 am
Re: HUN: Issues introduced with recent M30 opening
« Reply #1 on: October 29, 2021, 12:56:57 pm »
F39's point for F3 is on the wrong side of the motorway (on the former F3) - it should have moved

M30's wp F3Her should be renamed to 80, shouldn't it? If so, F3's M30Her -> M30(80)
That junction number only recently appeared on OSM. This wasn't a mistake in the original pull, but new information.

Quote
Should E71 be moved onto M30?
E71 is signed on the motorway.

Quote
Should E79 be extended at north end?
No change needed here.

The route is officially described as ending at Miskloc. And the old end of the M30 might have been a guess for the end of E79, but it is the correct place looking at videos of the new M30, and GMSV from earlier this year.  Sure, GMSV has E79 turn off at exit 30 onto the F3, along with E71. However E71 and E79 immediately diverge to go different ways - E71 to Kosice, E79 towards Miskolc. Then signage for E79 immediately stops (well, northbound - there's signs for southbound E79)

E79 ought to be extended in the real world along the Via Carpathia route north through Slovakia and Poland, to match it being the Via Carpathia route south of Miskolc. But that hasn't happened, so we can't do it.

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4573
  • Last Login:Yesterday at 10:17:38 am
Re: HUN: Issues introduced with recent M30 opening
« Reply #2 on: October 30, 2021, 03:29:43 am »
  • E71 / F3 concurrency is broken, but since E71 should be moved onto M30, it's not relevant
  • However, E71/E79 and M30 concurrency b/n exit 24 and 29 is broken

I'm surprised why mapview indicates the latter untraveled for me, but the routes itself are indicated being traveled. When I select highlighting "untraveled", everything is "untraveled". Anyone?

mapview traveled: untraveled:

routes:


I'd expect E71 and E79 indicated untraveled in showroute (there is no entry in my user list file!), but M30 indicated traveled on mapview  :o

Code: [Select]
HUN M30 1 29
HUN M30 86 HUN/SVK
« Last Edit: October 30, 2021, 03:37:19 am by michih »

Offline michih

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 4573
  • Last Login:Yesterday at 10:17:38 am
Re: HUN: Issues introduced with recent M30 opening
« Reply #3 on: November 04, 2021, 05:23:25 am »
https://github.com/TravelMapping/HighwayData/pull/5282 fixed all issues but:

  • E79 should be lined up with concurrent M30 and E71. E79 currently ends at F3's H3605 wp which is wrong. Well, it was the former M30 end. The M30 wp was merged into wp 29, and E79 end point should just get the same coords. The label name is already fine.
  • M30's, E71's and E79's shaping point between exit 29 and 24 is slightly off