Author Topic: usanyp: New York Parkways  (Read 1165 times)

0 Members and 1 Guest are viewing this topic.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1045
  • Last Login:Today at 02:24:48 am
Re: usanyp: New York Parkways
« Reply #15 on: August 07, 2017, 02:53:27 pm »
Up-D*te!
https://github.com/TravelMapping/HighwayData/pull/1521

Robert Moses and Bronx-Pelham Pakways renamed to Niagara Scenic and Pelham Parkways respectively.
Intersecting point labels changed to match route names as shown in the HB, for both new and existing (usasf) parkways. (AltLabels retained as needed.)
SevLakDr endpoint added to US9W/202.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1045
  • Last Login:Today at 02:24:48 am
Re: usanyp: New York Parkways
« Reply #16 on: August 08, 2017, 02:25:14 am »
Jumping up & down making ape noises, and hitting my computer with a femur.

Code: [Select]
27thSt http://www.openstreetmap.org/?lat=40.772283&lon=-73.919830
45 http://www.openstreetmap.org/?lat=40.770564&lon=-73.917475
+X981717 http://www.openstreetmap.org/?lat=40.770028&lon=-73.916252
*31stSt http://www.openstreetmap.org/?lat=40.769476&lon=-73.912936
31ST-STREET http://www.openstreetmap.org/?lat=40.768639&lon=-73.906965
EXIT-5-ACC-ASTORIA-BLVD http://www.openstreetmap.org/?lat=40.766851&lon=-73.896972
+X159377 http://www.openstreetmap.org/?lat=40.766258&lon=-73.892691
+5 http://www.openstreetmap.org/?lat=40.766867&lon=-73.887734
EXIT-6-94TH-ST http://www.openstreetmap.org/?lat=40.770284&lon=-73.879538
2014

Code: [Select]
31-ST-EX-STRT-I-278-OLP http://www.openstreetmap.org/?lat=40.772283&lon=-73.919830
+45 http://www.openstreetmap.org/?lat=40.770564&lon=-73.917475
+X981717 http://www.openstreetmap.org/?lat=40.770028&lon=-73.916252
+31stSt http://www.openstreetmap.org/?lat=40.769476&lon=-73.912936
EX-4-END-OLP-I-278-WEST-B-Q-E-PKY http://www.openstreetmap.org/?lat=40.768452&lon=-73.906123
EXIT-5-ACC-ASTORIA-BLVD http://www.openstreetmap.org/?lat=40.766770&lon=-73.896441
+X159377 http://www.openstreetmap.org/?lat=40.766258&lon=-73.892691
+5 http://www.openstreetmap.org/?lat=40.766867&lon=-73.887734
EXIT-6-94TH-ST http://www.openstreetmap.org/?lat=40.769951&lon=-73.880133
2011

I mean, uhh... saving these code blocks in case I want to reference them in the future.
« Last Edit: August 08, 2017, 02:32:11 am by yakra »

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1045
  • Last Login:Today at 02:24:48 am
Re: usanyp: New York Parkways
« Reply #17 on: August 09, 2017, 03:12:38 pm »
Another concurrent task will be a review and cleanup of existing parkways in the usasf system, making sure their endpoints are in the right places, etc.
Click on the link for a post detailing what I've found after looking at the termini of each usasf parkway.
I just checked the termini; there may be other points along the routes' length still needing attention, but I'm not focusing my attention there right now.

I'll hold off on making any changes until usanyp is ready to go live. I figure that with the excitement & attention over its activation, people will be going over their .lists to make edits, and can look at what's changed in existing parkways and make any needed edits at the same time.

The biggest inconvenience I see is the FDRooDr / HarRivDr endpoint change; HarRivDr travelers will lose 100% clinches and need to edit .list files.  Reminiscent of the issue with HenHudPkwy when SawMillPkwy was first added to the system.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1045
  • Last Login:Today at 02:24:48 am
Re: usanyp: New York Parkways
« Reply #18 on: August 13, 2017, 02:13:01 pm »
Thinking a few things through here...

Names:
Even NYSDOT sources aren't consistent in how the names of some parkways are presented. For instance, the TDR lists "Bear Mountain Parkway", whereas the Touring Route Book lists "Bear Mountain State Parkway". Thus I'll be going with what's commonly known and signed, I.E. "Bear Mountain Parkway", "Pelham Parkway", etc.

Spurs:
TMK there are no existing instances of "Spr" being part of the "route" field in a CSV, and not part of the "banner" field. I don't really want to break with precedent here & start doing this for no good reason. Take the example of the Interstates in Maryland. There are a few routes apparently considered spurs by MD DOT. Since the CHM days, these have had "Spr" in the banner field, and thus the shields show up in the CHM HB with the "Spur" banner, even if they're not signed like that in the field. So, there's that precedent.
ETA:The way the TM shield generator works now, the route name is shown as "LakeOntPkwySpr", which does look wrong. OK, I've made up my mind; Spr goes out of the "route" field and into the "banner" field.
The standard for bannered routes is they all get a city/abbrev, even if they're the only bannered route of a particular designation. Thus the Lake Ontario State & Niagara Scenic Parkway spurs would get a city & abbrev.
As for the option I floated of omitting the Spur designation and just having a vanilla route segment with city/abbrev specifiers, I'm cooling down on that a bit. Take the Maryland precedent again -- there's another segment, of I-395, not marked as a spur, considered as a different segment of a mainline route. The M.O. seems to be to recognize spurs as spurs. This will better highlight the distinction from other mainline segments with a city/abbrev specifier, such as BearMtnPkwyCro and NiaScePkwyNia.

Cities:
I consider it best practice to use a city as a city name when practicable, and not another specifier such as a state park, and maintain as much consistency here as we can here. (I suppose that if a parkway can change names, it's possible for a state park to do so too. A town/city/village, probably less likely. So why not use naming that will head off accounting for this (admittedly remote) possibility).
Thus right now I'm leaning more toward "Carlton" and "Porter", and not "Lakeside State Park" and "Fort Niagara State Park" for the Lake Ontario State & Niagara Scenic Parkway spurs.
ETA: I found some assurance in an unexpected place recently when looking over the NS Scenic Travelways. Seeing I consistently used town/city/village names there helps me feel more confident in standardizing around that approach.
Similarly, for consistency, thinking of changing Bear Mountain Parkway (Crompond) to Bear Mountain Parkway (Yorktown).
(Ocean Parkway (Long Island) -> Ocean Parkway (Babylon)? Brooklyn *is* on Long Island, after all...) Or maybe just leave it blank...
NiaScePkwyNia: "Niagara Falls" is good enough for a city specifier. I'm not a fan of unnecessary parenthetical bits in the city field. "(South) Niagara Falls" would add a second set of double parentheses to the name in the HB display. Yecch.
« Last Edit: August 16, 2017, 04:03:01 pm by yakra »

Offline Duke87

  • TM Collaborator
  • Jr. Member
  • *****
  • Posts: 85
  • Last Login:Yesterday at 11:44:09 pm
Re: usanyp: New York Parkways
« Reply #19 on: August 13, 2017, 02:32:39 pm »
(Ocean Parkway (Long Island) -> Ocean Parkway (Babylon)? Brooklyn *is* on Long Island, after all...) Or maybe just leave it blank...

And if you want to be super technical about it, this Ocean Parkway *is not* on Long Island - it is on Jones Beach Island. ;D

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1045
  • Last Login:Today at 02:24:48 am
Re: usanyp: New York Parkways
« Reply #20 on: August 16, 2017, 04:08:29 pm »
And if you want to be super technical about it, this Ocean Parkway *is not* on Long Island - it is on Jones Beach Island. ;D
Works for me. "Ocean Parkway (Long Island)" is out, and either "Ocean Parkway (Babylon)" or just plain "Ocean Parkway" is in.
Any preferences as to which?

Offline Duke87

  • TM Collaborator
  • Jr. Member
  • *****
  • Posts: 85
  • Last Login:Yesterday at 11:44:09 pm
Re: usanyp: New York Parkways
« Reply #21 on: August 26, 2017, 11:54:30 pm »
I'd go with plain "Ocean Parkway".

If there is a desire for some parenthetical name, "Jones Beach" would be best - that is the location most people would associate with the road. "Babylon" is undesirable since while much of the road is technically within the town of Babylon, towns in Long Island are purely political entities - people don't think of geography in terms of them. You say "Babylon" and people will think of the village of Babylon, which Ocean Parkway does not serve.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1045
  • Last Login:Today at 02:24:48 am
Re: usanyp: New York Parkways
« Reply #22 on: August 28, 2017, 12:27:16 am »
Vanilla "Ocean Parkway" it is.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 1045
  • Last Login:Today at 02:24:48 am
Re: usanyp: New York Parkways
« Reply #23 on: September 03, 2017, 03:58:26 am »
Up-D*te!
https://github.com/TravelMapping/HighwayData/pull/1581

ProMtnHwy extended from overlook to summit.
BearMtnPkwy (Crompond) -> BearMtnPkwy (Yorktown)
LakeOntPkwySpr -> LakeOntPkwySpr (Carlton)
NiaScePkwySpr -> NiaScePkwySpr (Porter)
...these last two have "Spr" in the Banner field of the CSVs, instead of the Route field.

Offline dave1693

  • Newbie
  • *
  • Posts: 17
  • Last Login:Today at 12:01:32 am
Re: usanyp: New York Parkways
« Reply #24 on: September 10, 2017, 04:28:31 pm »
Regarding 907V - ny.henhudpkwy - Henry Hudson Parkway
"S: The 2014 TDR description looks a little screwy, but a milepost of 1.14 for "W 79TH ST UNDER" is a very close fit for (1.13 mi) a terminus at Exit 8, as we have it now. GMSV suggests that it's parkway this far down too. Leaving as-is."

I can add personal confirmation for GMSV's suggestion, having traveled down 9A/HHP from the GWB to exit 8 last winter. It's definitely a parkway at least that far.