• Welder
    link
    fedilink
    English
    8511 months ago

    I find everyone uses time for long distances. I know it’s a 13 hour drive to Edmonton but damned if I know how many kilometres it is.

    • @[email protected]
      link
      fedilink
      English
      14
      edit-2
      11 months ago

      I always convert using 100km/h. So a 13 hour drive is probably North of 1250km.

      That being said I only measure distance in time as well.

      • Rentlar
        link
        fedilink
        8
        edit-2
        11 months ago

        100km/h is a good estimator, because you’re probably going 120km/h most of the way but you need to account for toilet breaks and lunch.

        • @[email protected]
          link
          fedilink
          111 months ago

          And city driving where you might spend 20 or thirty minutes getting to our from the actual highway.

      • @[email protected]
        link
        fedilink
        1
        edit-2
        11 months ago

        My car tracks my average speed for some reason, and I believe it’s based on engine hours vs. distance. After 2½ years and ~70,000km it’s stayed pretty consistent at about 60km/h.

        My driving is probably 90% highway by distance, or 60% by time.

    • @[email protected]
      link
      fedilink
      English
      1111 months ago

      Yep, I can tell you Toronto is 17 hours away and the QC border is 7, but I have no clue how many KM those are.

    • @[email protected]
      link
      fedilink
      English
      211 months ago

      This is what I came here to say. Even short distances.

      Basically, any time you’re describing a trip to a destination, it’s in time, based on the mode of travel. Hell, I even describe our family hikes in time it takes our littles to walk it, then estimate how long it would take an adult.

      My kids school is 3 minutes away or an 8 minute adult-pace bike ride. Fucked if I know how many km that is.