forked from pratikjain1993/jainprat-DJANGO
-
Notifications
You must be signed in to change notification settings - Fork 0
/
Copy pathfare.txt
11 lines (4 loc) · 974 Bytes
/
fare.txt
1
2
3
4
5
6
7
8
9
10
11
So I propose this for fare calculation:
ESTIMATED FARE CALCULATION MODULE:
Screen 4 wil call estimateFareCalculate Module before the journey starts. Google distance matrix API will return the optimum distance and time as JSON objects. The Estimated fare will be calculated as : (base fare + time amount + distance amount) where Time rate and distance rate will be defined by us and will be multiplied by the time and distance values provided by Google maps API.
ACTUAL FARE CALCULATION MODULE: Actual Fare will be shown on the end screen, i.e, Screen 7, after the journey ends. We will be making continuous GPS calls to monitor the actual distance travelled and the journey time will also be recorded. So actual fare will be calculated as: (base fare + time amount + distance amount) where Time rate and distance rate will be defined by us(similar to that in estimated fare module) and will be multiplied by the time and distance values recorded by GPS monitoring.