Replies: 1 comment 4 replies
-
@tarung interesting point. Can you please share a real-world example of how this would look like for the user? |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Currently we only have GPS coordinates for the two locations i.e.
"fulfillment": {
"stops": [
{
"type": "START",
"location": {
"gps": "13.008935, 77.644408"
}
},
{
"type": "END",
"location": {
"gps": "12.971186, 77.586812"
}
}
]
},
Adding these fields here would be beneficial - textual representation of pickup and drop locations and the estimated distance between pickup locations.
This addition will help avoid the need for distance calculations between the pickup and drop locations, thus minimizing unnecessary overheads. The underlying assumption here is that the passenger interface already allows users to check the accuracy of the two location selected by the user by showing the textual representation of the selected locations, and another way is to also show the distance between the two locations. So, while sending search request the passenger side can also provide the textual address and estimated distance, this allows the provider side to reduce overhead costs of distance calculations and geocoding the locations.
Beta Was this translation helpful? Give feedback.
All reactions