In the - performance report- at the -Driving/Stopped Time Summary- if you click on the -Based on 0 Minute Minimum Stop- The generated report is RIGHT! ….but if you click on –Based on 5..or..10..or..30..Minute Minimum Stop- the resulting reports are missing data that did show in the 0 Minute report and SHOULD be in the 5 or 10….results report.
This error is happening also in the OpenGTS demo site.
To replicate go to the demo site and generate a >>0 Minute Minimum Stop<<report for the "Demo device 2"
you will see stopped times like 19:12, 27:32, 44:17, 22:00, 15:05,....ALL of this SHOULD show up in the 5 Minute report and so on.
Next bug? is when you log in, it is not discriminating between uppercase/lowercase, it let you in either way.
The problem begins when you click on the >> Vehicle Detail>>Event Detail>>Get report>>..then if you click on one of the #links on the left that open up a map it will give you a “INVALID LOGIN/PASSWORD” error sign if you are logged in with the wrong username (upper/lower case)
To replicate:
Let's say you have an user registered as “richard” , Try to log in as “Richard” once in go to >>Vehicle Detail>>Event Detail …..Get Report ….then click on one of the numerical hyperlinks on the left and you will see the “INVALID LOGIN/PASSWORD” error.
I think it should not let you sign in with the wrong upper/lower combination to begin with…but if it does let you in, it should let you see the popup map then, right?.
Thanks
Last edit: Gabriel 2013-10-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
About the report based on 5 or more stop minutes, it's important to understand how it works.
In the 0 minutes are reported each stop event, for 5 minutes report it's required that the device remain in the stop status for at least 5 minutes, if this is false you not find the information in the report.
Please compare the report with the device track to verify if there are errors.
I tested this report in earlier OpenGTS version and works fine.
Regards,
- Pierluigi
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi all!
I’m using OpenGTS 2.4.5
In the - performance report- at the -Driving/Stopped Time Summary- if you click on the -Based on 0 Minute Minimum Stop- The generated report is RIGHT! ….but if you click on –Based on 5..or..10..or..30..Minute Minimum Stop- the resulting reports are missing data that did show in the 0 Minute report and SHOULD be in the 5 or 10….results report.
This error is happening also in the OpenGTS demo site.
To replicate go to the demo site and generate a >>0 Minute Minimum Stop<<report for the "Demo device 2"
you will see stopped times like 19:12, 27:32, 44:17, 22:00, 15:05,....ALL of this SHOULD show up in the 5 Minute report and so on.
Next bug? is when you log in, it is not discriminating between uppercase/lowercase, it let you in either way.
The problem begins when you click on the >> Vehicle Detail>>Event Detail>>Get report>>..then if you click on one of the #links on the left that open up a map it will give you a “INVALID LOGIN/PASSWORD” error sign if you are logged in with the wrong username (upper/lower case)
To replicate:
Let's say you have an user registered as “richard” , Try to log in as “Richard” once in go to >>Vehicle Detail>>Event Detail …..Get Report ….then click on one of the numerical hyperlinks on the left and you will see the “INVALID LOGIN/PASSWORD” error.
I think it should not let you sign in with the wrong upper/lower combination to begin with…but if it does let you in, it should let you see the popup map then, right?.
Thanks
Last edit: Gabriel 2013-10-03
Hello.
have you found the solution about reports?
Last edit: memento 2014-08-05
About the report based on 5 or more stop minutes, it's important to understand how it works.
In the 0 minutes are reported each stop event, for 5 minutes report it's required that the device remain in the stop status for at least 5 minutes, if this is false you not find the information in the report.
Please compare the report with the device track to verify if there are errors.
I tested this report in earlier OpenGTS version and works fine.
Regards,
- Pierluigi