Track logs 20,000 point limit..?

The specs for the 66i state a track logs point limit of 20,000 (https://buy.garmin.com/en-GB/GB/p/623975#specs).. is this truly the case, specifically for *recording* of tracks by the unit itself?

That would suggest using 1-second recording you can only record a track for a maximum of just over 5.5 hours - that doesn't sound right for a device with 16Gb internal storage (even if the majority of that might be taken up by maps etc.)?

(I'd expect there to potentially be a hard limit on the number of track/route points on an imported track/route attempting to be routed.. but for the creation of a track file surely that's just appending another point to a file / series of files until storage space is full up, no?)

As comparison, I've just had a look a long ride (450km) I did last year recorded with an Edge 1030, again using 1-second recording: moving time of 17hrs10min51secs = calculator suggest this should be 61,851 track points = looking at the resulting GPX file there are 61,777 track points (I'll let it off for missing a small number over that time/distance!).

Does anyone have experience of recording for say 6hrs+ (using 1-second recording) on the 66 series?

TIA

0 SpikySimonW over 3 years ago

Following up my own question for others, I found this info from https://www.gpsrchive.com/inReach/GPSMAP%2066i/index.htm

Activity Limits

The GPSMAP 66i can index up to 300 individual Activity (*.fit) files, each up to 20,000 points in length.
Activity files over 20,000 points are filtered on device to maximize rendering efficiency without modifying the original *.fit files.
The GPSMAP 66i will auto-archive the current activity and begin a new recording (as configured) when approaching the 20,000 activity point limit.
Garmin Connect limits files to 25MB and 99,999 total points (maximum length of 27 hours when using a one second recording interval).

0 SpikySimonW over 3 years ago

Also, think I need to start adjusting my mindset from the fitness product lines / use cases (where 1 second recording is needed to ensure a smooth capture of all the relevant metics for accurate averaging/trending), whereas for all-day hiking tracks I hope the auto recording intervals will work as described to capture the information to an appropriate resolution (ie. where I don't so much care about my exact average speed, power output nor heart rate but instead just want an accurate capture of the track I've travelled).