Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Survey to FGDB not properly creating tracklogs for specific POZ files #12

Open
DylanSchertz opened this issue Sep 9, 2021 · 3 comments

Comments

@DylanSchertz
Copy link

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.

OddTracklogIDs

@rsarwas
Copy link
Collaborator

rsarwas commented Sep 9, 2021

Hi Dylan, It sounds like before a crash, and on days without a crash, the tracks were properly segmented. Can you please confirm. That would indicate there is a problem in PO and something amiss in the POZ file due to the crash. Otherwise the problem is in the poz2fgdb tool.

It would also be good to hear about these crashes. I don’t like PO crashing for any reason. If you can provide some details, I will look into it.

I will send you an email address for the POZ file.

@DylanSchertz
Copy link
Author

DylanSchertz commented Sep 9, 2021

Hi Regan,
Yes, I believe that is correct. Before a crash (and on days without a crash) the data seems to be importing correctly.

I think the main crashes we were having may have already been mostly resolved by iOS updates. We had a mix of different iOS versions (I believe it was 14.4.X vs 14.5.X) and I remember that the older ones would crash if you hit the move to GPS location button multiple times (tapping it incorrectly then wanting to update the location again). I apologize for being vague on this but sometimes it's difficult to figure out what's going on from other observers in planes and I viewed this as largely resolved by updating the iOS.

POZ files were e-mailed.

Thanks,
Dylan

@rsarwas
Copy link
Collaborator

rsarwas commented Sep 9, 2021

Thanks for the clarification. I’ll ignore the crashing and hope it is resolved in later versions of iOS.

I got the poz files. I hope to look at them in the next day or so. Stay tuned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants