|
Top-level
 @whitequark @siderea Here's a Google Street View image of about where the dotted line in that screenshot crosses the street. And it's even worse because right here the road is coming out from a tunnel under a pedestrian plaza where you can cross with ease; but that is not at all apparent on the map, it just looks like road the whole way. 14 comments
@rivetgeek @whitequark @siderea But the confusing thing about it is that it's not just a single "shrug" dotted line; it's not a single segment, there's some kind of waypoint in between. And it's a regression; Google Maps is capable of generating plausible walking directions for this route, and I believe that it used to do so for transit directions (though it's been a while since I've used transit directions, moved out of the city several years back), but it now seems to just give the "shrug."  That's because the two different hops are on two different planes. The first hop is the pedestrian path inside the station, from the train platform to the surface, and then the second hop is on the surface from the headhouse of the station to the destination. @siderea @rivetgeek @whitequark Ah, right. So they do have some notion of pedestrian routing; the question is why they don't continue to do the pedestrian routing after exiting the headhouse? It feels like this may be some kind of limiting of the route complexity; they've changed a constant somewhere where it will just give the "shrug" rather than trying to route you if the route goes over a certain complexity. @whitequark @siderea It's even more puzzling because Google Maps is perfectly capable of generating reasonable-ish walking directions for the same start point and destination if you ask for walking directions. I just have no idea what's going on with the dotted line in the transit directions; it's not even just a single "dotted line to your destination", it seems to have a waypoint that explicitly leads you astray. @whitequark @siderea I'll also note that the first time I tried to take this screenshot, Google Maps caused Firefox to bog down, and then crash. Now, who knows if that's a Firefox bug, or a graphics driver issue, but it's kind of funny when it happened, and it looks like the new Google Maps rendering may be a lot more demanding. I'll note that one of the reasons that path is different from the other, is that you asked for directions from "Harvard Square" or maybe "Harvard Square Station", right? If you're actually coming in on a northbound train, it saves you about a block's worth of walking to use the exit that the bad Google Maps public transit directions use, instead of walking back down the platform, and down the ramp, and then up to the surface in Harvard Square proper, as per that. I'd argue that the correct directions, if you're coming from a northbound red line train, are to use the north head house to exit on the east side of Mass Ave, next to Harvard Yard, and just stay on the damn sidewalk. You have to trust the process, but it will deliver you unimpeded directly to the Science Center plaza. And it has the advantage of being a path that works even with Harvard has locked the gates to Harvard Yard (e.g. around graduation time.) The problem is it looks like it doesn't work. It curves around the wrong way, and all you can see is the road dropping down and forming a massive obstacle. There's no visual confirmation that the sidewalk crosses to the other side. So the obvious thought, looking at a map, is "Oh I suppose I have to cross the street here" – the street being four lanes of Mass Ave at its worst. And then you discover you have to cross back the other way on the far side of that mess. Which depending on how bad the traffic is and how fast you walk, something like a 20 to 30 minute pedestrian detour. @siderea @whitequark Yeah. I guess I've always just gotten off at the north head house and then gone through Harvard Yard; I supposed I've never been there when the gates are locked. But yes, this is a very complex place to navigate through, and one where good walking directions could help a lot, and it's very easy to get misled and take a route that is circuitous at best and could be dangerous if you don't navigate it carefully. @siderea @unlambda @whitequark I know someone who works there. That is not working as intended. Bug was filed. @siderea @whitequark Yeah, I just put it where I saw the end of your transit route; at Harvard Square. I hadn't realized that Google Maps was actually doing one smart thing, which is telling you to get out at the northern head house, but then failing to route you past that. If I look at Google Maps in my browser, it even gives you fairly detailed instructions within the station, and then just gives up once you exit the head house. It's weird where it gives up on walking directions. @whitequark @siderea Oh, and for some more context, if you did try to roughly follow the dotted line, of course you wouldn't try to cross at the point pictured. You would naturally follow the path in the little island park up to the intersection, where there is technically a crossing. But this is the crossing; one of the most confusing intersections I have ever encountered. |
Gregory's Server
@unlambda @whitequark @siderea I'd note the curved dotted line is *not* supposed to be your projected path. It's a :shrug: response that indicates you're on your own. No, it's not great in any measure. At least since we moved to WA three years ago, Google Maps has done that consistently for walking directions. It's been a PITA when we go into downtown Seattle and are going to park and walk because I have to fiddle with the options to get a walking path.