Author Topic: DC: US 29 Point Errors  (Read 652 times)

0 Members and 1 Guest are viewing this topic.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 821
  • Last Login:Today at 08:15:31 pm
DC: US 29 Point Errors
« on: January 31, 2019, 05:59:59 pm »
1.  The GeoAve_S point is incorrect.  US 29 is oddly following both 7th St NW (SB) and 6th St NW (NB) at this point.  Due to US 1 being at the 6th St NW intersection, I am unsure what the point label should truly be.
2.  The 11thAve_N and 11thAve_S points should be for 11th St instead.
3.  ConnAve should be ConAve (Connecticut Ave).

EDIT: Added GSV link to note below post.
« Last Edit: January 31, 2019, 07:08:18 pm by Markkos1992 »

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 518
  • Last Login:Today at 10:52:27 pm
Re: DC: US 29 Point Errors
« Reply #1 on: January 31, 2019, 06:34:49 pm »
I see that southbound has been rerouted to stay on 7th there. (Anyone want to correct it on OSM? Here's an acceptable source: https://www.mapillary.com/map/im/DH3oFqD6fN9eeKBEG0HGig ) Both directions used to use Florida to 6th: https://www.google.com/maps/@38.9155399,-77.0202861,3a,75y,144.89h,81.19t/data=!3m7!1e1!3m5!1sObxHQgF5001X3aYHYrZutA!2e0!5s20090701T000000!7i13312!8i6656

Offline froggie

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 517
  • Last Login:Today at 11:15:01 pm
Re: DC: US 29 Point Errors
« Reply #2 on: January 31, 2019, 11:34:08 pm »
Officially, US 29 does not follow 6th St at all.  The reason it's signed that way northbound is because you cannot make a left turn from eastbound Rhode Island Ave to northbound 7th.  I do agree that the GeoAve_S point is in error, but I would note the error is in the label name.  Should be either RhoIslAve or 7thSt, depending on how one would want to do it.

I would suggest fixing this in one of two ways:

- Leave the GeoAve_S point in its current location, but relabel it as mentioned above since the road is no longer Georgia Ave (per DDOT the changeover from 7th to Georgia is at Florida Ave).
- Relabel the GeoAve_S point to RhoIslAve and move it to between 6th and 7th...to take into account that northbound traffic must use 6th.  I would also add a point at 7th and Florida and label it FloAve.

Correct that the "11thAve" errors should be "11thSt" instead.

Since we're on the subject of US 29...

- RocCrkPkwy could arguably be removed.  There are only two direct ramps between it and K St (US 29)...and both ramps meet 29 at the same location as the I-66 point.  Even if it's not removed, it should be relabeled to "RockCrePkwy".
- Going by road importance, instead of "NewHamAve", it should be "23rdSt".
- It's mentioned upthread that "ConnAve" is mislabeled, but an argument could be made that for "17thSt".
- Same as at New Hampshire Ave..."15thSt" is far more important than "VerAve".
- A point should be added at Missouri Ave.  It's a major east-west route across northern D.C....the only one that goes continuously across Rock Creek Park, for that matter.

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 518
  • Last Login:Today at 10:52:27 pm
Re: DC: US 29 Point Errors
« Reply #3 on: February 01, 2019, 07:21:00 am »
Officially
What's the source (other than signage) for official routings?

Offline froggie

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 517
  • Last Login:Today at 11:15:01 pm
Re: DC: US 29 Point Errors
« Reply #4 on: February 01, 2019, 11:19:57 am »
Maps.  DDOT and FHWA GIS data.

Offline neroute2

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 518
  • Last Login:Today at 10:52:27 pm
Re: DC: US 29 Point Errors
« Reply #5 on: February 01, 2019, 02:22:32 pm »
FHWA GIS data shouldn't be taken as authoritative. DDOT data would depend on how internally consistent it is...in other words, are route numbers an afterthought or is the data being maintained?

Offline Duke87

  • TM Collaborator
  • Sr. Member
  • *****
  • Posts: 336
  • Last Login:February 20, 2020, 09:45:58 pm
Re: DC: US 29 Point Errors
« Reply #6 on: February 01, 2019, 08:02:13 pm »
- RocCrkPkwy could arguably be removed.  There are only two direct ramps between it and K St (US 29)...and both ramps meet 29 at the same location as the I-66 point.  Even if it's not removed, it should be relabeled to "RockCrePkwy".

Couple things to keep in mind here:
1) There is precedent for using "Crk" as short for "Creek" (see usamts, for example) where it has been accepted. Doesn't necessarily need to be "Cre" instead.
2) RockCrkPkwy (yes, with "Crk") is a route in usanp: http://travelmapping.net/hb/index.php?units=miles&u=si404&r=dc.rockcrkpkwy
Removing this point would break the intersection between the two routes. Relocating the I-66 point to avoid such a break would be slightly awkward since I-66 does not have any direct connection to Rock Creek Parkway here, but collocating all three would make the system show I-66 and RockCrkPkwy as intersecting.

Offline yakra

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 2451
  • Last Login:February 15, 2020, 10:58:37 am
Re: DC: US 29 Point Errors
« Reply #7 on: February 01, 2019, 11:56:21 pm »
There's precedent for both Cre & Crk for Creek.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 821
  • Last Login:Today at 08:15:31 pm
Re: DC: US 29 Point Errors
« Reply #8 on: January 06, 2020, 07:29:44 pm »
Even though I am not interested in taking over DC, I got in the mood to attempt to take care of this.  I took all of Froggie's suggestions (including the latter one involving the 6th St/7th St one-way issue) and got the following tentatively:

VA/DC http://www.openstreetmap.org/?lat=38.901153&lon=-77.070508
MSt +MStNW http://www.openstreetmap.org/?lat=38.904159&lon=-77.069027
I-66 +RocCrkPkwy http://www.openstreetmap.org/?lat=38.902543&lon=-77.056915
23rdSt +NewHamAve http://www.openstreetmap.org/?lat=38.902539&lon=-77.050123
17thSt +ConnAve http://www.openstreetmap.org/?lat=38.902539&lon=-77.039426
15thSt +KStNW_E +VerAve http://www.openstreetmap.org/?lat=38.902531&lon=-77.033643
11thSt_S +11thAve_S http://www.openstreetmap.org/?lat=38.902522&lon=-77.027045
11thSt_N +11thAve_N http://www.openstreetmap.org/?lat=38.910537&lon=-77.027056
RhoIslAve_E +GeoAve_S http://www.openstreetmap.org/?lat=38.912687&lon=-77.020874
FloAve http://www.openstreetmap.org/?lat=38.916264&lon=-77.021901
ColRd http://www.openstreetmap.org/?lat=38.927691&lon=-77.023033
RCChuRd http://www.openstreetmap.org/?lat=38.936346&lon=-77.024291
GalSt http://www.openstreetmap.org/?lat=38.951883&lon=-77.027421
MisAve http://www.openstreetmap.org/?lat=38.961129&lon=-77.028024
PinBraRd http://www.openstreetmap.org/?lat=38.967526&lon=-77.027486
DC/MD http://www.openstreetmap.org/?lat=38.984550&lon=-77.026625

Outside of putting RocCrkPkwy under I-66, the only other major change I want to mention is that I added Rock Creek Church Rd (RCChuRd) at the northern New Hampshire Ave intersection due to the connection to MD 650 since NewHamAve is already in-use.

Offline froggie

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 517
  • Last Login:Today at 11:15:01 pm
Re: DC: US 29 Point Errors
« Reply #9 on: January 07, 2020, 10:02:40 am »
You could arguably relabel RCChuRd as "NewHamAve_N" instead.

The only other thing I'd suggest is perhaps moving the Gallatin St (GalSt) point slightly south to Arkansas Ave (ArkAve).  Compared to other street points that we've omitted, Gallatin St is not that important of a roadway.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 821
  • Last Login:Today at 08:15:31 pm
Re: DC: US 29 Point Errors
« Reply #10 on: January 07, 2020, 04:33:58 pm »
You could arguably relabel RCChuRd as "NewHamAve_N" instead.

The only other thing I'd suggest is perhaps moving the Gallatin St (GalSt) point slightly south to Arkansas Ave (ArkAve).  Compared to other street points that we've omitted, Gallatin St is not that important of a roadway.

I am thinking just adding the suffix to make it NewHamAveNW.  Maybe change it to NewHamAve later if the other users eventually remove the current NewHamAve from their last files (I found at least 5 currently using it based on my last Github search).  We could also forget about the change to 23rdSt and go with NewHamAve_S and NewHamAve_N then.

For the record, I am not planning on submitting changes here until the I-66/US 50 thread is resolved.

Offline Markkos1992

  • TM Collaborator
  • Hero Member
  • *****
  • Posts: 821
  • Last Login:Today at 08:15:31 pm
Re: DC: US 29 Point Errors
« Reply #11 on: January 12, 2020, 03:53:55 pm »
I decided to stick with NewHamAve_S and NewHamAve_N.

I did replace Gallatin St (GalSt) with Arkansas Ave (ArkAve).

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