Open-Harbor/osrm-backend
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 3 Wiki Activity

[skip ci] Rephrased the API docs in terms of adding new types

Browse Source
This commit is contained in:
Patrick Niklaus 2016-05-09 18:39:30 +02:00
parent d15cc77b0b
commit 6aed145dae
No known key found for this signature in database
GPG Key ID: E426891B5F978B1B
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/http.md
View File

@ -421,7 +421,8 @@ step.
direction of travel immediately before the maneuver. direction of travel immediately before the maneuver.
- `bearing_after`: The clockwise angle from true north to the - `bearing_after`: The clockwise angle from true north to the
direction of travel immediately after the maneuver. direction of travel immediately after the maneuver.
- `type` A string indicating the type of maneuver - `type` A string indicating the type of maneuver. **new identifiers might be introduced without API change**
Types unknown to the client should be handled like the `turn` type, the existance of correct `modifier` values is guranteed.
| `type` | Description | | `type` | Description |
|-------------------|--------------------------------------------------------------| |-------------------|--------------------------------------------------------------|
@ -476,7 +477,7 @@ step.
| `turn` or `end of road`| Indicates the number of intersections passed until the turn. Example instruction: `at the fourth intersection, turn left` | | `turn` or `end of road`| Indicates the number of intersections passed until the turn. Example instruction: `at the fourth intersection, turn left` |
New maneuver `type` and `modifier` and new properties (potentially depending on `type`) may be introduced in the future without an API version change. New properties (potentially depending on `type`) may be introduced in the future without an API version change.
### Waypoint ### Waypoint