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
{{ message }}
This repository was archived by the owner on Mar 1, 2021. It is now read-only.
Copy file name to clipboardExpand all lines: map-matching/api-reference.md
+32-34
Original file line number
Diff line number
Diff line change
@@ -20,40 +20,6 @@ The Map Matching Service is in active development. You can follow the [Mapzen bl
20
20
21
21
The default logic for the OpenStreetMap tags, keys, and values used when routing are documented on an [OSM wiki page](http://wiki.openstreetmap.org/wiki/OSM_tags_for_routing/Valhalla).
22
22
23
-
24
-
## Criteria For More Accurate Map-Match Results
25
-
26
-
* GPS accuracy is "good" meaning that there are few obstructions affecting GPS signals, which can be difficult in urban areas.
27
-
* Trace point density is within the approximate range of one per second and one per 10 seconds. The greater the range between them, the more chance of inaccurate results.
28
-
* Each trace represents one continuous path
29
-
* Corresponding match with the OpenStreetMap network
30
-
* NOTE: Traces in urban areas will have a negative effect on GPS accuracy
31
-
32
-
33
-
## Improving Map Matching Results
34
-
35
-
*`turn_penalty_factor` - To penalize turns from one road segment to next. For a pedestrian trace_route, you may see a back-and-forth on side streets for your path. Try increasing the turn penalty factor to 500 to smooth out jittering of points. Note that if GPS accuracy is already good, increasing this will have a negative affect on your results.
36
-
*`gps_accuracy` - GPS accuracy in meters.
37
-
*`search_radius` - To specify the search radius (in meters) within which to search road candidates for each measurement. The `max_search_radius` is 100 so this can only be increased to 100. Note that performance will decrease the higher the `search_radius`.
*`max_distance` - The maximum input shape distance is 200000.0 meters.
52
-
*`max_gps_accuracy` - The maximum input gps accuracy is 100 meters.
53
-
*`max_search_radius` - The maximum of the upper bounds of the search radius is 100 meters.
54
-
*`max_shape` - The maximum number of input shape points is 16000.
55
-
56
-
57
23
## Map Matching Service Actions:
58
24
59
25
Our Map Matching Service includes two separate service calls that perform different operations on an input set of latitude, longitude coordinates, depending on your interest: `/trace_route?` or `/trace_attributes?`. It is important to note that all service requests should be *POST* since shape or encoded_polyline can be fairly large.
@@ -313,3 +279,35 @@ Each `admin` may include:
313
279
|`state_code`| State code. |
314
280
|`state_text`| State name. |
315
281
282
+
## Criteria For More Accurate Map-Match Results
283
+
284
+
* GPS accuracy is "good" meaning that there are few obstructions affecting GPS signals, which can be difficult in urban areas.
285
+
* Trace point density is within the approximate range of one per second and one per 10 seconds. The greater the range between them, the more chance of inaccurate results.
286
+
* Each trace represents one continuous path
287
+
* Corresponding match with the OpenStreetMap network
288
+
* NOTE: Traces in urban areas will have a negative effect on GPS accuracy
289
+
290
+
291
+
## Improving Map Matching Results
292
+
293
+
*`turn_penalty_factor` - To penalize turns from one road segment to next. For a pedestrian trace_route, you may see a back-and-forth on side streets for your path. Try increasing the turn penalty factor to 500 to smooth out jittering of points. Note that if GPS accuracy is already good, increasing this will have a negative affect on your results.
294
+
*`gps_accuracy` - GPS accuracy in meters.
295
+
*`search_radius` - To specify the search radius (in meters) within which to search road candidates for each measurement. The `max_search_radius` is 100 so this can only be increased to 100. Note that performance will decrease the higher the `search_radius`.
0 commit comments