From ccae81c549ddf8ec0ccf4e55c1bb2830faeb7ff8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Felix=20G=C3=BCndling?= Date: Sun, 22 Sep 2024 21:09:29 +0200 Subject: [PATCH] Update README.md --- README.md | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index f110280..0d68d9d 100644 --- a/README.md +++ b/README.md @@ -112,9 +112,8 @@ and "right") on that `way_idx_t` can be initialized. All attributes of the OpenStreetMap ways that are relevant for routing are packed into a compact struct. Distances between routing nodes (i.e. `node_idx_t`) on a way are stored for fast access. -A `profile_edge_weight(distance, way_attributes, direction) -> duration` function then computes the edge weight for this -specific profile. In case of one-way streets or other ways that should not be used by a profile, the function can -return `kInfeasible` to indicate this case. +The profile (see blow) function then computes the edge weights and feasibility of a way based on the stored OpenStreetMap attributes. +To implement more finegrained control over path finding, it might be necessary to extract more attributes from OpenSteetMap. The current set of routing profiles can be found in the [`include/osr/routing/profiles`](https://github.com/motis-project/osr/tree/master/include/osr/routing/profiles) folder. Here's what a profile needs to provide in order to be usable by the shortest path algorithm: