Author Topic: NY/CT: Point observations  (Read 469 times)

0 Members and 1 Guest are viewing this topic.

Offline cockroachking

  • Newbie
  • *
  • Posts: 8
  • Gender: Male
  • Last Login:Today at 12:56:48 am
NY/CT: Point observations
« on: July 22, 2022, 10:17:02 pm »
1. NY116: The NY/CT waypoint is currently 500ft or so west of the actual state line. The state line shown on OSM appears to be correct, as verified by NYSDOT and CTDOT GIS maps.
2. CT116: see point 1
3. NY121: The NY124_N waypoint should be renamed since NY124 has not existed this far north since 1980. I would suggest naming it JunRd or JuneRd.
4. TacStaPkwy: The CR10 waypoint is too far north, as it is currently placed at Post Hill Rd, 1.15 miles north of CR10.
5. NY9A: I would suggest a new waypoint at Ashford Ave in Ardsley (or Heatherdell Rd since there is already an AshAve waypoint at Ashburton Ave) in order to reduce confusion with I-87 through here. I am suggesting a waypoint rather than a shaping point because Ashford Ave connects to the SawMillPkwy at Exit 17.
6. NY9A: I would suggest a shaping point near Belmont Rd in Hawthorne in order to reduce line overlap with the SawMillPkwy here.
7. SawMillPkwy: I would suggest adding a waypoint at NY9A/NY100, since they both have a waypoint for the SawMillPkwy there, and it would further reduce the line overlap mentioned in point 6.
8. NY US9: US9 could really use a waypoint between NY52 and NY9D at either CR28 or CR93. I would suggest CR93 since CR28 is already in use as a waypoint and more traffic would use it between US9 and NY9D, but only CR28 is already a waypoint on NY9D.
9. NY US9: US9 could also use a waypoint between FelNewRd and CR19. I would suggest CR4 or CR6, though both are already in use further north on US9.
10. NY96: Not sure why exactly TM has it ending at UniSt when the signage basically ends at WinRd, but it officially extends to East Main St. One way or another, I would imagine it should either end at one of those rather than UniSt.
11. NY74: Since TM does not count ferries, should the eastern terminus be renamed from NY/VT to something regarding the ferry (like NY373)?
12. NY35: Minor point drift at NY123 and NY/CT.
13. NY207: Minor point drift at CR8.
14. CT I-84: Point “24” is not centered at the interchange. This is probably a relic from before I-84 was reconstructed through here.

Offline vdeane

  • Sr. Member
  • ****
  • Posts: 337
  • Gender: Female
  • Last Login:Yesterday at 09:31:49 pm
    • New York State Roads
Re: NY/CT: Point observations
« Reply #1 on: July 23, 2022, 06:44:20 pm »
10. NY96: Not sure why exactly TM has it ending at UniSt when the signage basically ends at WinRd, but it officially extends to East Main St. One way or another, I would imagine it should either end at one of those rather than UniSt.
I'm guessing that's because the 2017 Touring Route book has it ending at the Inner Loop, and that's where the Inner Loop used to be.  In any case, cities in NY tend to be hit or miss with their signage, but in this case, it wasn't signed from the Inner Loop either, so there might indeed be a case for truncating it to Winton Road.  Yes, there's the signs saying it continues, but the same exists for NY 404 at NY 590 exit 8, and it doesn't (the rest of Empire Boulevard is a reference route and isn't signed anywhere else) (never mind, they fixed that).
Please note: All comments here represent my own personal opinion and do not reflect the official position of NYSDOT or its affiliates.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3900
  • Last Login:Yesterday at 08:26:21 pm
Re: NY/CT: Point observations
« Reply #2 on: July 24, 2022, 10:33:42 am »
Welcome to the TM forum, cockroachking, and thanks fo the corrections & suggestions!

1-2. Done.
3. Relabeled JuneRd.
4. Whoopsie. This was originally PostHillRd, but was erroneously changed back in 2018. Holding off on making changes for the moment, as "CR10" is in use in cockroachking.list only -- do you need Post Hill Rd, or the actual CR 10 farther south?
5. AshfAve added, as it connects to a Saw Mill River Pkwy interchange.
6-7. NY9A/100 point added to SawMillPkwy. No new point on NY9A/100. This is sufficient to keep the lines from crossing.
8. I don't see any compelling reason to add a new point here. I would remove CR28 from NY9D, but OldHopRd is in use.
9. +X19 replaced with a visible point at BinMilRd. This is the only solution that keeps shaping within tolerance without increasing the total number of points.
10. See vdeane's post.
11. Changed to TicFry. I'll put a note in the pull request to ping froggie. This reminds me of NJ US9, which was similarly changed pretty early in TM's lifetime.
12-13. Repositioned, though normally this is pretty low priority.
14. Repositioned. I thought about adding a point (or even 2) for *OldI-84, but didn't, at least for now. At the E end, the old & new alignments separate at just about exactly the diverge point for the old WB exit 24. 1PPI would imply leaving that one out. W end, the point would wanna be at the Nolan Bridge. With the aux lane setup there, it's kinda borderline 1PPI with both 23 and 24. I'm not including an updates entry, though this is arguably newsworthy. Discuss!

https://github.com/TravelMapping/HighwayData/pull/5934
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2573
  • Last Login:Yesterday at 11:25:38 pm
Re: NY/CT: Point observations
« Reply #3 on: July 24, 2022, 10:59:19 am »
NY 9A:  Should SawMillPkwy(26) have been changed to plain SawMillPkwy? (Ok it actually does look intentional.)

NY 16:  Did I miss something or should NY400_S have actually been changed to OleRd?
« Last Edit: July 24, 2022, 11:06:06 am by Markkos1992 »

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3900
  • Last Login:Yesterday at 08:26:21 pm
Re: NY/CT: Point observations
« Reply #4 on: July 24, 2022, 11:46:37 am »
OleRd has been the point label since 2017-01-19.
Only difference now is NY400_S is unused & thus removed. NY400 simply ends at an intersection with Olean Rd; there is no multiplex split.
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2573
  • Last Login:Yesterday at 11:25:38 pm
Re: NY/CT: Point observations
« Reply #5 on: July 24, 2022, 01:14:52 pm »
Oh I see now.  I thought NY 400 follow Olean Rd between the two NY 16 intersections for some reason.   :pan:

Offline cockroachking

  • Newbie
  • *
  • Posts: 8
  • Gender: Male
  • Last Login:Today at 12:56:48 am
Re: NY/CT: Point observations
« Reply #6 on: August 01, 2022, 04:03:31 pm »
Welcome to the TM forum, cockroachking, and thanks fo the corrections & suggestions!

1-2. Done.
3. Relabeled JuneRd.
4. Whoopsie. This was originally PostHillRd, but was erroneously changed back in 2018. Holding off on making changes for the moment, as "CR10" is in use in cockroachking.list only -- do you need Post Hill Rd, or the actual CR 10 farther south?
5. AshfAve added, as it connects to a Saw Mill River Pkwy interchange.
6-7. NY9A/100 point added to SawMillPkwy. No new point on NY9A/100. This is sufficient to keep the lines from crossing.
8. I don't see any compelling reason to add a new point here. I would remove CR28 from NY9D, but OldHopRd is in use.
9. +X19 replaced with a visible point at BinMilRd. This is the only solution that keeps shaping within tolerance without increasing the total number of points.
10. See vdeane's post.
11. Changed to TicFry. I'll put a note in the pull request to ping froggie. This reminds me of NJ US9, which was similarly changed pretty early in TM's lifetime.
12-13. Repositioned, though normally this is pretty low priority.
14. Repositioned. I thought about adding a point (or even 2) for *OldI-84, but didn't, at least for now. At the E end, the old & new alignments separate at just about exactly the diverge point for the old WB exit 24. 1PPI would imply leaving that one out. W end, the point would wanna be at the Nolan Bridge. With the aux lane setup there, it's kinda borderline 1PPI with both 23 and 24. I'm not including an updates entry, though this is arguably newsworthy. Discuss!

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

1. Thank you
2. Thank you
3. Thank you
4. I have only taken it up to the real CR10 intersection. Nevertheless, I would still say that having the CR10 waypoint would be more useful in general, since it is a county route, rather than a one lane residential road like PostHillRd.
5. Thank you
6. Noted, makes sense
7. Thank you
8. I trust your judgement.
9. Thank you
10. Interesting. The Traffic Data Viewer still shows NY96 going all the way to East Main, so I guess even NYSDOT is conflicting itself. Typical  ::)
11. Thank you
12. Thank you
13. Thank you
14. Thanks. I personally don't think that the *OldI-84 point is necessary either due to 1PPI.

Offline cockroachking

  • Newbie
  • *
  • Posts: 8
  • Gender: Male
  • Last Login:Today at 12:56:48 am
Re: NY/CT: Point observations
« Reply #7 on: August 09, 2022, 09:19:01 am »
Any changes to the CR10 point on TacStaPkwy yet? I think that is the only thing left that needs to be fixed here.

Offline cockroachking

  • Newbie
  • *
  • Posts: 8
  • Gender: Male
  • Last Login:Today at 12:56:48 am
Re: NY/CT: Point observations
« Reply #8 on: August 19, 2022, 01:41:21 pm »
Any changes to the CR10 point on TacStaPkwy yet? I think that is the only thing left that needs to be fixed here.

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

Since nothing has been done yet in regard to this point, I went ahead and put in a pull request on Github.

Offline mapcat

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1397
  • Last Login:September 22, 2022, 06:11:37 pm
Re: NY/CT: Point observations
« Reply #9 on: August 19, 2022, 01:52:09 pm »
Since nothing has been done yet in regard to this point, I went ahead and put in a pull request on Github.

Don't do that. There is a collaborator who volunteers to maintain New York (yakra) and unless he authorizes someone else to make changes, he's the only one who should be making edits in his regions. Be patient.
Clinched:

Offline Duke87

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 693
  • Last Login:Yesterday at 02:06:34 pm
Re: NY/CT: Point observations
« Reply #10 on: August 19, 2022, 06:49:14 pm »
Since nothing has been done yet in regard to this point, I went ahead and put in a pull request on Github.

For what it's worth, what you committed is a correct fix to the stated issue. I for one appreciate the enthusiasm. :)

But yes, SOP here is that each state/"region" has a single individual responsible for managing all changes and updates with it, and no one else should be making changes unless said responsible individual explicitly says go ahead and do so. This is how we: 1) maintain version control, 2) avoid having edit wars.
« Last Edit: August 19, 2022, 06:51:39 pm by Duke87 »

Offline webny99

  • Newbie
  • *
  • Posts: 17
  • Last Login:September 20, 2022, 06:19:06 pm
Re: NY/CT: Point observations
« Reply #11 on: August 20, 2022, 06:32:32 pm »
I understand the need for only one person to be making edits within a region, but it's also problematic when requests for edits/changes aren't being addressed. Any response, even if it's "no, this isn't needed" or "yes, you can make this change" is better than none at all.

At a certain point practicality plays a role too; if the maintainer doesn't have time to address concerns and someone else does, is there any precedent for maintenance of that region changing hands?

Offline Jim

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2422
  • Last Login:Today at 12:02:19 am
Re: NY/CT: Point observations
« Reply #12 on: August 20, 2022, 08:23:55 pm »
Of course, if a contributor becomes inactive, someone else would take over.  Everyone has different schedules to be able to contribute to the process.  I wouldn't worry about yakra addressing things as his time permits.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 3900
  • Last Login:Yesterday at 08:26:21 pm
Re: NY/CT: Point observations
« Reply #13 on: August 22, 2022, 10:11:47 am »
I've reviewed & merged cockroachking's pull request. Thanks for the contribution.
Before marking this as closed, any more opinions on CT I-84?
Sri Syadasti Syadavaktavya Syadasti Syannasti Syadasti Cavaktavyasca Syadasti Syannasti Syadavatavyasca Syadasti Syannasti Syadavaktavyasca

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2573
  • Last Login:Yesterday at 11:25:38 pm
Re: NY/CT: Point observations
« Reply #14 on: August 22, 2022, 10:21:43 am »
I am fine with a no-build on CT I-84.