It seems for the specific start & end combinations in question the station locations just like really suck
There was some dispute about whether 2AS should continue to the Bronx after 116th or if they should move the 2nd ave station but that side lost the argument I think
The actual reason is that extending a project for which the TBM is already in the ground is vastly easier than launching it again. If they wanted to come back and do this later it would be a lot of additional work, and this is a reasonable spot for a route graph-theoretically
Lucas Pombo (aka Lib Development) retweeted
When I talk about Hoboken's land use being a disaster, this is what I have in mind. Yes, it's better than the suburbs, but this is not nearly dense enough that close to PATH. jerseydigs.com/425-newark-st…
Honestly this may be a situation where it's better to just not apply for federal funding and front the entire cost using state + local contributions
It seems that the MTA is going to try to speedrun the funding process for their proposed 125th street subway; very exciting
The MTA is proposing a new 125 Street Subway, which would extend west from the future 125 St/Lexington Av Q station. The project would connect existing subway lines—including the Second Avenue Subway—and bus routes along the corridor.
Learn more about this project at a public scoping meeting; we're hosting two virtual sessions on October 22, and one in-person session on October 27. Register for a session and get all the details: mta.info/project/125-street-…
ALT Map of proposed 125 Street Subway. The map includes streets, landmarks, and color-coded subway lines.
Assuming similar performance to Waymo, though, you'd expect it to still be zero. At this point, Robotaxi has not driven far enough to know the at-fault crash rate. But then again, that itself is enough to know it's clearly good enough.
If we use Waymo's definitions of any-injury-crashes, Tesla is probably at two over ~3 million miles, which is almost exactly the same rate as Waymo. In both incidents, Tesla was clearly not at fault.
The report says they went to the hospital "for an unknown reason", and there would be no reason to make this reason known to Tesla. But... 4 car accident, someone goes to the hospital, not an injury? That's, uh, surprising to say the least.
In the second crash, the description says "unknown" but this probably is because information didn't make it back to Tesla. The description is that the robotaxi was stationary when hit by two other vehicles in a collision of at least 4 cars. And someone went to the hospital.
Waymo: Any SGO reported crash with the field “Highest Injury Severity Alleged” is “Minor”, “Moderate”, or “Serious”, or “Fatality”). “Unknown” reported severity where the SGO narrative mentions injuries of unknown severity are also included.
waymo.com/safety/impact/#met…
lmfao. I kind of can't help but laugh at this one. It's a reportable incident, and it caused an injury, but it isn't a crash. Under Waymo definitions (see below) it would count, but I kind of forgive Tesla for not counting it.
The first injury is described as follows:
"Summary: The ADS was proceeding straight through a work zone on a street and drove over a pothole at approximately 29MPH. The ADS had two riders present in the vehicle. One customer alleged they sought medical care."
Oh, very clever. Tesla is using a really strange definition of "injured"; in practice, Tesla's SGO data lists two events with injuries (thread)
Tesla now has a robotaxi safety page to match Waymo:
tesla.com/robotaxi/safety
Of course, no Robotaxi has been in a serious crash yet, so it makes for an excellent looking dashboard. But Tesla has driven just over 1% of Waymo's 271 million driverless miles.
