Updates:
- 2025-08-03 – added new error “GPS timestamps do not overlap with Video timestamps.”
- 2025-09-03 – added “GPS data contains gaps greater than 5 seconds in between GPS points.”
This is another research article which I am posting so others may find it in the search engines.
Uploading to Google Street View involves uploading a video file with embedded GPS, or a non-GPS enabled video file and a separate .gpx file containing the GPS data.
Here are some of the errors I have been getting:
GPS data contains gaps greater than 5 seconds in between GPS points. 32 sec gap found after 0 seconds
This was from two separate recording where the Insta360 GPS Remote did not embed GPS data. Instead, I used a .KML file generated by an iPhone app (Geotag Photos 2) I was using for my digital camera photos. I tried to use the KML file as a backup, but apparently there are data problems in it that Google will not accept.
Video does not contain more than 10 GPS points. Only 0 GPS points found
This one is problematic because the GPX file contains hundreds of GPS points. I had converted my video file down to 1 frame per second, per Google recommendations. One theory was that the points in the GPX file did not line up enough times with a specific frame in the video, and thus the file gets rejected. Google Gemini says this should not matter, but a different file I uploaded at 1 fps did not have any issue, and resubmitting the same erroring file converted to 5 fps did not receive this error.
GPS time range (9/12/24, 8:35 AM to 9/12/24, 8:39 AM) does not overlap with Video time range (7/20/25, 6:49 PM to 7/20/25, 6:53 PM)
This was caused when I converted a video file to 1 fps using Apple Compressor. The resulting file had a different creation date, and thus did not match the GPX file. It looks like Apple Compressor cannot be used by itself to get the requested 1 fps, 5fps or other frame rates to Street View.
GPS data jumps around a lot
This one puzzles me the most. If I convert the GPX file to a KML file for uploading to Google Maps…
…that file displays on the map and looks quite accurate to the trail on the map:
GPS timestamps do not overlap with Video timestamps. GPS time range: (6:00:00 PM UTC-6 to 6:00:00 PM UTC-6). Video time range: (6:00:00 PM UTC-6 to 6:00:00 PM UTC-6).
This one happened after I used Apple Compressor to reduce the video file down to 5 fps. There are some settings I was told about on Reddit that should allow the metadata to pass through to the converted file. That helped get past an earlier error, but now this one shows up.
Can you help?
Please leave a comment with any solutions to these errors, and I will update this page.
Until then…