• Welder@lemmy.ca
    link
    fedilink
    English
    arrow-up
    76
    ·
    1 year 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.

    • Leviathan@lemmy.world
      link
      fedilink
      English
      arrow-up
      14
      ·
      edit-2
      1 year 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@lemmy.ca
        link
        fedilink
        arrow-up
        7
        ·
        edit-2
        1 year 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.

        • Leviathan@lemmy.world
          link
          fedilink
          arrow-up
          2
          arrow-down
          1
          ·
          1 year ago

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

      • Someone@lemmy.ca
        link
        fedilink
        arrow-up
        1
        ·
        edit-2
        1 year 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.

    • blindsight@beehaw.org
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year 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.