what:
a flat ascii table of data: raw, un-filtered, no quality control.
spot units for all 3 types of platforms that we are using are contained in the file.
- drifters (SCOPE_nnn, nnn=001-105)
- SAR boats & jet-skis (SAR_nnn)
- moored mini-CAT buoys (CAT_nnn)

where: w/ carthe pswd protection
http://www.rsmas.miami.edu/personal/eryan/scope/

file name:
scope_spot_xml_data.dat

how often is the file updated:
cron will run every hour at :?? after the hour and will take a few minutes to run.
check the file update time in the main table.

columns:
1) unique message id
2) spot esn number ( e.g. 0-8245281 )
3) spot esn Name ( e.g. SCOPE_082 )
4) DateTtime (utc) (e.g. yyyy-mm-ddThh:mm:ss.000Z )
5) Seconds from Epoch in GMT
6) latitude
7) longitude

sorted:
by drifter name ( SCOPE_001 ), then dateTtime ( i.e. columns 3, 4 ).

date & time:
if all is working as it should, there should be a data record every 5 minutes for each spot unit.
that is how often the SPOT Messenger transmits 'up' in SOS mode.

position: -99999.0
if the spot unit can not see enough satellites to get a position fix, it still sends a message (time stamp), but the lat/lon are set to -99999.0
these records are included in the data file, that way, you at least know the spot is transmitting ok, but is needs a better view of the sky to receive a position fix.