NY: I-190/NY-266

[rickmastfan67]

Only noticed this due to an error message.

Code: [Select]

ny.i190;NY266;;;VISIBLE_HIDDEN_COLOC;ny.ny266@+x190(14B)
So, taking a look @ it, I wouldn't do any changes on I-190.

As for NY-266:
I-190/325 -> NY325
+x190(14B) -> I-190

Mainly due to how we've delt with other ramps intersecting @ numbered routes (like US-17 @ I-81 in VA).

[Markkos1992]

Only noticed this due to an error message.

Code: [Select]

ny.i190;NY266;;;VISIBLE_HIDDEN_COLOC;ny.ny266@+x190(14B)
So, taking a look @ it, I wouldn't do any changes on I-190.

As for NY-266:
I-190/325 -> NY325
+x190(14B) -> I-190

Mainly due to how we've delt with other ramps intersecting @ numbered routes (like US-17 @ I-81 in VA).

Yeah,  NY 266 should have a point at I-190 here.  (see I-80 at PA 42 and PA 44 just north of Bloomsburg)

[rickmastfan67]

(Decided to split this out of the "NJ/NY: Point Concerns since 8/5-8/7/2022 Trip" thread, due to it having an error on the Error check page.)

[yakra]

TLDR I've been thinking about reverting that change.

[rickmastfan67]

Since yarka sorta gave a green light to doing this on Github, I decided to at least quickly knock this out so the error on the error log can finally disappear after 2+ years.

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

[cockroachking]

I noticed that the pull request omits the Seaway Trail, which is concurrent with NY266 here. Shouldn't this issue be fixed there too?

[rickmastfan67]

I noticed that the pull request omits the Seaway Trail, which is concurrent with NY266 here. Shouldn't this issue be fixed there too?

Added in the pull request.