Currently we create origin/destination records for the simulator with randomly generated coordinates that lead to routing errors in the dispatcher.
Instead, let's generate these records with real (routable) locations. We still keep the area definitions and radius, but the number will act as a max number.
https://overpass-turbo.eu/ - this open API helps to extract POIs from openstreetmap data, so we can easily run queries like the following and get enough locations back:
[out:json][timeout:25];
(
node["amenity"~"cafe|restaurant"](around:5000.0,-6.1813448922772185,106.8372344970703);
);
out body;
>;
out skel qt;
Obviously around and lat/long coordinate values will be passed as parameters.
The key amenity seems to be quite extensively filled out (building tag is not e.g.: in Jakarta).
Query language guide here if needed to extend the above query.
Currently we create origin/destination records for the simulator with randomly generated coordinates that lead to routing errors in the dispatcher.
Instead, let's generate these records with real (routable) locations. We still keep the
areadefinitions andradius, but the number will act as a max number.https://overpass-turbo.eu/ - this open API helps to extract POIs from openstreetmap data, so we can easily run queries like the following and get enough locations back:
Obviously
aroundandlat/longcoordinate values will be passed as parameters.The key
amenityseems to be quite extensively filled out (buildingtag is not e.g.: in Jakarta).Query language guide here if needed to extend the above query.
POSThttps://overpass-api.de/api/interpreter{ data: thatQueryStringAbove }const { lat, lon } = response.elements[i]