In going through data from this year I noticed that some days had numerous transects in a row that showed up as one segment in the geodatabase rather than separate features with on/off observing for each. When I looked at the iPad the data showed separate features. I reran the import of those poz separately to isolate the files. Looking at the geodatabase, the GpsPoints feature class has the correct tracklog ID values for each point and the TrackLogs attribute table has entries with the right data but each of the entries for these missing segments has a shape length of 0.
One of these POZ files was on a day when the iPad crashed while collecting data and the point at which the track is being combined is for everything after the crash. Another case occurred on the same day that an iPad crashed but we don't remember exactly where the iPad crashed.
I would attach the POZ files but they contain specific location data for a harvested species so they should be e-mailed or shared directly.

In going through data from this year I noticed that some days had numerous transects in a row that showed up as one segment in the geodatabase rather than separate features with on/off observing for each. When I looked at the iPad the data showed separate features. I reran the import of those poz separately to isolate the files. Looking at the geodatabase, the GpsPoints feature class has the correct tracklog ID values for each point and the TrackLogs attribute table has entries with the right data but each of the entries for these missing segments has a shape length of 0.
One of these POZ files was on a day when the iPad crashed while collecting data and the point at which the track is being combined is for everything after the crash. Another case occurred on the same day that an iPad crashed but we don't remember exactly where the iPad crashed.
I would attach the POZ files but they contain specific location data for a harvested species so they should be e-mailed or shared directly.