forked from Project-OSRM/osrm-backend
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Oasis API design #128
Labels
Design
Documentation
Comments
Initial fake response:
and with fixed value for other parameters |
|
Yes, thanks for the suggestions :) |
CodeBear801
added a commit
that referenced
this issue
Jan 9, 2020
CodeBear801
added a commit
that referenced
this issue
Jan 10, 2020
CodeBear801
added a commit
that referenced
this issue
Jan 10, 2020
CodeBear801
added a commit
that referenced
this issue
Jan 13, 2020
wangyoucao577
pushed a commit
that referenced
this issue
Jan 14, 2020
UpdateDue to new information found in:#132 (comment)
|
CodeBear801
added a commit
that referenced
this issue
Jan 17, 2020
- Remove "Location field", add "Address" field which contains geo_coordinates + a list of nav_coordinates - Add field of detail_url, external user could retrieve all information related with specific charge station - Add field of estimate remaining range for each solution issue: #132 (comment) #128
wangyoucao577
pushed a commit
that referenced
this issue
Jan 22, 2020
* feat: Implement initial connector with telenav search Only support nearest charge station search for now. issues: #132 * fix: update oasis api - Remove "Location field", add "Address" field which contains geo_coordinates + a list of nav_coordinates - Add field of detail_url, external user could retrieve all information related with specific charge station - Add field of estimate remaining range for each solution issue: #132 (comment) #128 * fix: resolve conflict issue: #128
This was referenced Jan 28, 2020
To do:
|
2 tasks
CodeBear801
added a commit
that referenced
this issue
Mar 16, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Subtask of #120. API design for POC. For deployment information, could go to here.
Oasis API expect user input orig point, destination point and vehicle information, it will select needed charge station to achieve the trip and return them as
waypoints
.Input
The input contains information related with user's vehicle status, where to go and specific settings.
The unit is alined with OSRM, distance's unit is
meter
, time's unit issecond
Response
Response contains information for charge station needed to complete the route.
Reference
The text was updated successfully, but these errors were encountered: