Open koebi opened 3 years ago
Isochrone requests with intersections=true
return a GeoJSON that one can think of consisting of two parts:
Each isochrone returned has a group_index
-property and a value
-property.
The group_index
-property is equal to the index of the point in the locations-array in the query. The value
property corresponds to the range given in the query. If you consider the values
as an array, you can assign an index to each value that will be needed below.
Each isochrone here has a contour
-property. This property has the form [[A,x],[B,y]], and will be the intersection of the two isochrones with group_index
A, value-"index" x and group_index
B, value
-"index" y.
The following images may serve to illustrate this:
Here's what I did
I tried to write an API-Test for Isochrone requests with
intersections:true
in body. To do s, I wanted to figure out how isochrone intersections work and what will be returned, as to be able to check for correct returns.Here's where I got
nothing - isochrone intersections aren't documented. In fact, Isochrone responses aren't documented at all, as far as I could tell.
Here's what I was expecting
Some documentation
Here's what I think could be improved
Isochrone documentation :)