When an Iridium file is downloaded, it is processed to create a results (csv) file with TDC. With Argos processing, we store the ParameterId from CollarParameters in the CollarParameterID field of the collarFiles. This allows us to find and fix results files that should be un (or re) processed because a new parameter file applies to the download file. This is not being done for Iridium processing
You need to fix the Iridium processing step to insure the CollarParameterID is included in the results file record in future processing
You can recreate the missing data as typically there is only one parameter file appropriate for a collar. If there are two, then we need to look at the dates of the files/transmissions/fixes to see which parameter file applies.
When an Iridium file is downloaded, it is processed to create a results (csv) file with TDC. With Argos processing, we store the ParameterId from CollarParameters in the CollarParameterID field of the collarFiles. This allows us to find and fix results files that should be un (or re) processed because a new parameter file applies to the download file. This is not being done for Iridium processing
You need to fix the Iridium processing step to insure the CollarParameterID is included in the results file record in future processing
You can recreate the missing data as typically there is only one parameter file appropriate for a collar. If there are two, then we need to look at the dates of the files/transmissions/fixes to see which parameter file applies.