I’ve corrected the number of drives in this version. I was unknowingly counting non-drives (e.g a site number change without moving) . I’ve now added the Traverse JSON as an additional data source. This provides some additional data, such as drive times and the Traverse JSON data also makes it simpler to count the actual numbers of drives.

Credits: NASA/JPL-Caltech

  • ShadowAEnglish
    3·
    25 days ago

    Just a suggestion, but maybe stick to metric? Having a table format like this where multiple columns are showing the same thing in a mix of units, hurts my head.

    At least make that 4th row 2nd column not have KM in the column that’s otherwise all ft / miles. We don’t need to know 10970.06 m vs 10.97km