Skip to main content
October 3, 2024
Question

Interpret GPS tracking CSV report (Quickbooks time)

  • October 3, 2024
  • 1 reply
  • 0 views

Hi,

 

I am trying to understand how to interpret the csv file generated by Reports->Tracking->GPS points.

 

For example, how do I interpret local_timestamp in the following table. I am trying to calculate the actual time a person was present at the scheduled location. THanks!

fnamelnameusernamelocal_timestamplatitudelongitudeaccuracy_in_meters
AAABBB[email address removed]10/1/24 11:1511.11111-22.2222210.9
AAABBB[email address removed]10/1/24 12:5711.11111-22.222223.1
AAABBB[email address removed]10/1/24 12:5711.11111-22.222226.3
AAABBB[email address removed]10/2/24 11:0211.11111-22.222221.5
AAABBB[email address removed]10/2/24 14:1111.11111-22.2222211.4
AAABBB[email address removed]10/2/24 15:4611.11111-22.2222219.5
AAABBB[email address removed]10/2/24 17:1011.11111-22.2222243.9
AAABBB[email address removed]10/2/24 18:1311.11111-22.2222216.2
AAABBB[email address removed]10/2/24 19:5411.11111-22.2222211
AAABBB[email address removed]10/2/24 21:0311.11111-22.222222.8
AAABBB[email address removed]10/2/24 21:0311.11111-22.2222263.3

1 reply

October 3, 2024

Hi there, mkic.  I’m here to help you interpret the data from the CSV file related to your employees' locations.

 

The local_timestamp field indicates the exact date and time when a GPS point was recorded for the individual listed. This timestamp is essential for calculating how long a person was present at a scheduled location. To determine the actual time a person was present at a location, you'll need to look at time local_timestamp and accuracy_in_meters columns. A change in the accuracy_in_meters column means a change in location. Thus, the duration between subsequent timestamps represent the time spent at a location. 

 

For example, if an employee's first timestamp is at 11:15 at 10.9 accuracy_in_meters, and then a change in the accuracy_in_meters column is observed at the next timestamp (12:57), this would mean that the employee was at 10.9 accuracy_in_meters for 1 hour and 42 minutes.

 

For more detailed guidance on reading data from QuickBooks Time, refer to these articles:

 

You may also use our help articles on tracking time for further help on the matter.

 

Understanding the local_timestamp and accuracy_in_meters fields is crucial for accurately calculating the time spent at scheduled locations. If you have any further questions or need additional assistance, please don’t hesitate to reach out, mkic. We’re here to help you make the most of QuickBooks Time.

mkicAuthor
October 3, 2024

Thank you so much for the prompt reply AnneMarie! 

 

This is super helpful, clarified a lot of things for me. A few follow-up questions!

 

1) A quick confirmation - is accuracy in meters measured from latitude/longitude included in that row or the latitude/longitude of the scheduled address? Said other way, accuracy in meters = scheduled latitude/longitude - actual latitude/longitude (as shown in data)?

 

2) Also, sometimes I see some discrepancies between this report and Report->Payroll Report->Individual timesheets. For example, the GPS report would show that person A was at location A for 10 hours but the individual timesheets would show that person A was at location A for 4.5 hours and location B for 5.5 hours. I am assuming hours in individual timesheets are actual hours based on their GPS location. Am I interpreting this wrong?

 

3) Also, what would happen if geofence flag was turned off at store level?

 

Sorry that is a lot of questions but this will help my understanding a lot! Thanks!

mkicAuthor
October 4, 2024

Can anyone please help me with this? I am really stuck with this discrepancy in our reports. Thanks!