i can't edit the spreadsheet on google, don't have permission,etc.
But i think i can see the data format and will try to decode the first few lines or "frames" of the short capture. Here is the raw data from your spreadsheet, all values are expressed in hexadecimal format, 0xnnnn or xnn are short-hand notations that are sometimes used to indicate that the values are Hex and not decimal numbers.:
t102607836480c900
t2028d859f0961405b414
t34288000000008002000
t2125000770ff80
t35280000000000000000
t2226000000000000
t3b280000000000000000
t2324320fab3a
The first 3 values after the "t" are the CAN ID, aka PID.
The fourth field contains the number of data bytes in the frame (max number of data bytes in a frame is (0x08) = 8.
The fifth thru the end then contain the data.
Here is a parsed version:
pid # data
102 6 07 83 64 80 c9 00
202 8 d8 59 f0 96 14 05 b4 14
342 8 80 00 00 00 08 00 20 00
212 5 00 07 70 ff 80
352 8 0000000000000000
222 6 000000000000
3b2 8 0000000000000000
232 4 32 0f ab 3a
Once you parse the fields in the spreadsheet, then you can convert the hex data values to decimal numbers and make calculations to determine the engineering values, eg temperature, volts, amps, etc.
The lower the PID number, the higher importance and priority it has on the CAN buss. So you can sort the spreadsheet to filter by PID to group them and notice changes and trends in values quickly. For example pid x102 and x202 seem to have rich data fields.
Usually the PIDs are not converted to decimal, only the data.
here's the first line again with conversion of the data fields:
hex, decimal
102 pid, not converted
6 6
07 7
83 131
64 100
80 128
c9 201
00 0
Generally folks work on this to develop a PID dictionary, which identifies what the data fields of the PID represent and how to convert the hex to engineering values.