3 ms·
I don't exactly understand how it works. E.g. in NYC, Bushwick to Flatbush is notoriously slow (meandering buses only), while Flatbush to Chinatown is quite fas
by nine_k 2y ago
I don't exactly understand how it works. E.g. in NYC, Bushwick to Flatbush is notoriously slow (meandering buses only), while Flatbush to Chinatown is quite fast (direct trains over the Manhattan bridge). Despite that, no matter where I click, I only see same twitching map, not a map twitching in a way that would reflect the travel time from the point I click.
(I ignore the idea of traveling by car in thickly populated areas of Manhattan and Brooklyn; it only makes sense if you value your personal space way more than you value both your money and time, and don't have to park.)
- tuukkah 2y agoIf you turn on "Focus on hover" in the settings, then it matters where you tap (on mobile).
- nine_k 2y agoIndeed, this helps, thanks! Also there's a switch between car and public transport. The thing remains weird nevertheless. I'd assume that if you click a point at this mode, the point stays put, because the time from this point to this point remains zero and does not change. But the map twitches so that the point under cursor / tap moves away. I suspect that the map shows some other kind of approximation, not the time to the point clicked. Likely the grid that defines effective times is somehow sparse, and approximating the distortion well when a click hits rather away from a node is hard. But that would still be weird, because I suppose that points like airports and train terminals should definitely be major nodes of that grid.
- Hnrobert42 2y agoI too was confuse initially. The map doesn't care where you click. Clicking just toggles to the time based map. In that map, physical distance between any two points represents the time to get between those two points. Whether it accurately does that, as in your Bushwick Flatbush example, I don't know.