Open himynamesdave opened 7 months ago
known good video before fix
exiftool -ee -G3 -X 8-FRVT-1-GS019025-trek_view_processed_full_nadir-1_with-nadir.mp4 > 8-FRVT-1-GS019025-trek_view_processed_full_nadir-1_with-nadir.xml
known good video uploaded to gsv
exiftool -ee -G3 -X UKEH002-trek_view_processed_full_nadir-1_with-nadir.mp4 > UKEH002-trek_view_processed_full_nadir-1_with-nadir.xml
known bad video
exiftool -ee -G3 -X UKSD049-trek_view_processed_full_nadir-1_with-nadir.mp4 > UKSD049-trek_view_processed_full_nadir-1_with-nadir.xml
Regardless of video, the GPSSpeed and GPSSpeed3D between GPS points is always 0.865 and 0.89
<Track2:GPSSpeed>0.865</Track2:GPSSpeed> <Track2:GPSSpeed3D>0.89</Track2:GPSSpeed3D>
These values should be calculated using; speed m/s = distance (meters) / time (seconds)
This calculation should take the values from the current and next point.
The last point in the video telemetry should have the value 0 (b/c no subsequent point, so speed can be assumed to stopped). 8-FRVT-1-GS019025-trek_view_processed_full_nadir-1_with-nadir.txt UKSD049-trek_view_processed_full_nadir-1_with-nadir.txt UKEH002-trek_view_processed_full_nadir-1_with-nadir.txt
known good video before fix
known good video uploaded to gsv
known bad video
Regardless of video, the GPSSpeed and GPSSpeed3D between GPS points is always 0.865 and 0.89
These values should be calculated using; speed m/s = distance (meters) / time (seconds)
This calculation should take the values from the current and next point.
The last point in the video telemetry should have the value 0 (b/c no subsequent point, so speed can be assumed to stopped). 8-FRVT-1-GS019025-trek_view_processed_full_nadir-1_with-nadir.txt UKSD049-trek_view_processed_full_nadir-1_with-nadir.txt UKEH002-trek_view_processed_full_nadir-1_with-nadir.txt