
Welcome to the Birder's Diary Forum for Support And General Questions
Use the Support forum for all questions or issues.
Use the Wish List forum to leave your ideas for improving Birder’s Diary.
Use the Community Sharing forum for sharing Photos, Trips, Stories, etc.
Setup your Forum photo and profile here.
I have found that the Duration that appears in the Ebird export window is usually a few minutes less than the Elapsed Time that shows in the Edit Trip window. (This comes from the mobile app.) For example: Duration 52, Elapsed Time: 0:57:12. Why is that?
When does the timer stop counting? When I tap Finish Outing, so that if I spend 5 minutes filling out various things on that screen, that 5 minutes does not count? If so, then that still does not explain the discrepancy.
I have found that the Duration that appears in the Ebird export window is usually a few minutes less than the Elapsed Time that shows in the Edit Trip window. (This comes from the mobile app.) For example: Duration 52, Elapsed Time: 012. Why is that?
Hi David,
I am not sure I follow this paragraph. If you have the latest Mobile (1.45) and Desktop (Build 25) versions, then this is what I get.
That seems correct on every field.
See this prior post started by you here.
When does the timer stop counting? When I tap Finish Outing, so that if I spend 5 minutes filling out various things on that screen, that 5 minutes does not count? If so, then that still does not explain the discrepancy.
No, when you click on Submit, or Close Only. That is when the timer stops.
Let me know.
My apologies. I seen to have forgotten that I posted on this in early July. And you have a detailed answer, which I just now saw. It says you have made some changes to build 25 to address this, which I do not have yet.
🙂 No problem David. Glad it was this easy.
Take care.
I hate to say, but I noticed a time discrepancy again today. Duration was off by a few minutes and the Start Time was 1 minute later than what is in the trip. Using v 1.45.
I have sent you an email.
With David's help I was able to isolate the problem. It is fixed in v2.0 of BD Mobile; due out soon (maybe 2 weeks).
The problem is the following:
- The Sightings Import file emailed to you has a Trip End Date/Time of the last sighting of the Outing (what it used to be before deciding to make that match the actual start/end times for the Mobile Outing).
- Even though the comments in the same import file correctly showed the Outing End Date/Time.
The solution, until v2.0 is available, is to Edit your trip after import from BD Mobile and correctly set the Trip End Date/Time to that specified in the Comments for the trip, as shown below. If you do this after importing the Outing, it will take an extra 20 seconds.
fyi