#1926
  • Created on
    2016-11-08 14:44
  • Reported by
    rbergl
  • Status
    Fixed (Completed)
  • Priority
    Normal (3)
  • Assigned to
    darrinc
  • Milestone
    6.0.0
  • Plan Level
    -
  • Estimate
    0.0
  • Due Date
    -

Attachments

errors due to bad dates from cybertracker

several sites are experiencing issues with getting bad patrol or patrol leg start dates from cybertracker (i.e., getting the default device date which is typcially several years in the past). I am not sure how this can be happening, since CT is supposed to get the date and position from gps before allowing a patrol to begin). This causes problems when patrols/legs are imported because patrol length can be many years and patrols can't be opened for editing since the time is too long. Can we figure out either:

1. how Cybertracker is getting bad dates despite the "use time from gps" option being activated?
2. a way to open patrols for editing so that we can manually adjust the patrol/let start date.
User picture
  on 2016-11-08 20:07 *
By jeffloun2
#2) Maybe the simplest option would be to have a right-click menu on the list of patrols that have "edit patrol dates". Then you could edit the dates without running into the too-big-to-load error for ones that accidentally get set to 500 days long or however many. I think I will separate out this task as a new bug to keep it separate from the potential bug that is #1.

see #1927
User picture
  on 2016-11-08 20:11 *
By rbergl
It's, and ideally it would be"edit patrol legs" since this sometimes happens in the middle of a patrol, strangely enough.
User picture
  on 2017-05-09 12:11 *
By rbergl
so this appears not to have been addressed? please see also the ticket i submitted today.
User picture
  on 2017-05-16 16:05 *
By egouge
related to #2033, #2023
User picture
  on 2017-05-16 16:05 *
By egouge
Milestone set to 5.0.1
User picture
  on 2017-05-30 16:29 *
By egouge
Assigned to changed from justin.steventon to egouge
Status changed from New to Test
In SMART, I've added a check when you open a patrol. If the patrol is longer than 60 days your have the option to edit the dates before opening the patrol. If you edit the dates you may loose data for dates you remove. This does not fix the source of the problem (the dates from CT data are wrong), but it at least allows users to fix their data.
User picture
  on 2017-06-16 22:03 *
By egouge
Assigned to changed from egouge to darrinc
User picture
  on 2017-07-12 18:07 *
By darrinc
Status changed from Test to Fixed (Completed)
No further issues in 5.0.1.a7
User picture
  on 2017-12-06 18:22 *
By egouge
Assigned to changed from darrinc to -none-
Status changed from Fixed (Completed) to Accepted
Reopening as there is a bug where data is being deleted that should not be. Rich has provided a sample patrol that when imported and the dates modified the observation/track data is being deleted.
User picture
  on 2017-12-06 18:22 *
By egouge
Milestone changed from 5.0.1 to 6.0.0
Milestone updated at set to 2017-12-06 10:22:50 -0800
User picture
  on 2017-12-12 23:37 *
By egouge
Assigned to set to egouge
Status changed from Accepted to Test
fixed. rev 6216
User picture
  on 2017-12-15 00:26 *
By egouge
Assigned to changed from egouge to darrinc
User picture
  on 2017-12-21 18:17 *
By darrinc
Status changed from Test to Fixed (Completed)
No further issues in 6.0.a6