You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -28,7 +28,7 @@ Releasing is documented in RELEASE.md
28
28
## [unreleased]
29
29
30
30
### Added
31
-
31
+
- documentation on the fields of JSON and GeoJSON responses of the directions endpoint ([#2084](https://github.com/GIScience/openrouteservice/issue/2084))
32
32
- docs: comment on API key usage ([#2179](https://github.com/GIScience/openrouteservice/pull/2179))
33
33
- type-specific filtering for mapping point features to graph edges ([#2156](https://github.com/GIScience/openrouteservice/pull/2156))
34
34
- documentation on the matching endpoint ([#2156](https://github.com/GIScience/openrouteservice/pull/2156))
Copy file name to clipboardExpand all lines: docs/api-reference/endpoints/directions/instruction-types.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,12 +5,12 @@
5
5
6
6
The following table contains the encoding of the instruction types present in the `type`-field of a directions response in a step of a segment of a route.
|**`bbox`**| Bounding box `[minLon, minLat, maxLon, maxLat]` covering all of the routes in the response. |
27
+
|**`routes`**| List of routes. |
28
+
|**`metadata`**| Additional details about the request and routing engine, including `attribution`, `service`, `timestamp`, `query`, and `engine` info. |
29
+
30
+
Each of the `routes` entries can contain the following fields.
|**`summary`**| Properties of the route such as total `distance` (m) and `duration` (s). |
35
+
|**`segments`**| List of route sections between waypoints, each with `distance`, `duration`, and `steps` containing turn-by-turn navigation instructions if these have been requested. |
36
+
|**`bbox`**| Bounding box of the route. |
24
37
25
-
The **GPX** return type is an XML dialect from openrouteservice based on the [GPS Exchange Format](https://www.topografix.com/gpx.asp) with an own [XML Schema](https://raw.githubusercontent.com/GIScience/openrouteservice-schema/main/gpx/v2/ors-gpx.xsd).
26
-
It is a very old standard for lightweight interchange of GPS data and thus being used by hundreds of software programs and Web services.
38
+
Furthermore, if route geometry has been requested (which is the default), the following fields are present.
|**`geometry`**| The path of the route. In JSON it is [encoded](https://developers.google.com/maps/documentation/utilities/polylinealgorithm), while in GeoJSON it is a `LineString` with explicit coordinates. |
43
+
|**`way_points`**| Indices of way points corresponding to the `geometry`. |
27
44
28
45
### GeoJSON
29
46
30
-
**GeoJSON** is a format for encoding a variety of geographic data structures, see [geojson.org](https://datatracker.ietf.org/doc/html/rfc7946).
31
-
It is widely used and can therefore be easily processed or displayed in many applications, e.g. in [QGIS](https://qgis.org/) or on [geojson.io](http://geojson.io/)
47
+
**GeoJSON** is a standardized format for encoding a variety of geographic data structures, see [geojson.org](https://datatracker.ietf.org/doc/html/rfc7946).
48
+
It is widely used and can therefore be easily processed or displayed in many applications, e.g. in [QGIS](https://qgis.org/) or on [geojson.io](http://geojson.io/).
49
+
50
+
The **GeoJSON** output contains the same routing information as its **JSON** counterpart, but organized in slightly different way.
51
+
52
+
In the **GeoJSON** format, the route data is structured as a standard **FeatureCollection** where individual routes are represented as `features`.
53
+
Each **Feature** includes a `geometry` of type `LineString` and `properties` that contain the same fields as the `routes` elements in the JSON format, i.e. `summary`, `segments`, `way_points`, etc.
54
+
55
+
### GPX
56
+
57
+
The **GPX** return type is an XML dialect from openrouteservice based on the [GPS Exchange Format](https://www.topografix.com/gpx.asp) with its own [XML Schema](https://raw.githubusercontent.com/GIScience/openrouteservice-schema/main/gpx/v2/ors-gpx.xsd).
58
+
It is a very old standard for lightweight interchange of GPS data and thus being used by a wide range of software applications and Web services.
32
59
33
-
More information about the result types can be found in the [API Playground](https://openrouteservice.org/dev/#/api-docs/directions_service).
60
+
More details on the structure of the different return types can be found in the [API Playground](https://openrouteservice.org/dev/#/api-docs/directions_service).
Copy file name to clipboardExpand all lines: docs/api-reference/endpoints/directions/routing-options.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,7 +34,7 @@ A string array of features to avoid. The available features are :
34
34
|`steps`| cycling-\*, foot-\*, wheelchair |
35
35
36
36
### `options.avoid_polygons`
37
-
Comprises areas to be avoided for the route. Formatted as [geojson polygon](https://datatracker.ietf.org/doc/html/rfc7946#appendix-A.3) or [geojson multipolygon](https://datatracker.ietf.org/doc/html/rfc7946#appendix-A.6).
37
+
Comprises areas to be avoided for the route. Formatted as [GeoJSON polygon](https://datatracker.ietf.org/doc/html/rfc7946#appendix-A.3) or [GeoJSON multipolygon](https://datatracker.ietf.org/doc/html/rfc7946#appendix-A.6).
38
38
39
39
### `options.profile_params`
40
40
An object of additional routing parameters for all profiles except `driving-car`:
| boundaries | string | The path to a geojson file containing polygons representing country borders. Ignored if `preprocessed = true` is set. |`borders.geojson.tar.gz`|
162
+
| boundaries | string | The path to a GeoJSON file containing polygons representing country borders. Ignored if `preprocessed = true` is set. |`borders.geojson.tar.gz`|
163
163
| preprocessed | boolean | Indicates whether the source OSM file has been enriched with country data. If set to `true` then country codes are read from `country` node tags rather than being resolved at build time based on geometries provided in `boundaries`. |`true`|
164
164
| ids | string | Path to a csv file containing a unique id for each country, its local name and its English name |`ids.csv`|
165
165
| openborders | string | Path to a csv file containing pairs of countries where the borders are open (i.e. Schengen borders) |`openborders.csv`|
0 commit comments