From e5ece2e047454bf100ee467e3730054569053d69 Mon Sep 17 00:00:00 2001 From: glax Date: Sun, 23 Apr 2023 15:19:02 +0200 Subject: [PATCH] Update 'Features' --- Features.md | 13 ++++++++++++- 1 file changed, 12 insertions(+), 1 deletion(-) diff --git a/Features.md b/Features.md index 8636c3c..4ca463e 100644 --- a/Features.md +++ b/Features.md @@ -1,5 +1,16 @@ +* Splitting osm.XML files into regions for faster loading +* AStar routing with custom factors for modifying weights of roadpriority +* Output result as JSON +* Render Image of resulting path, weights, and loaded regions + At the moment, the program is able to split a give OSM-XML-Dataset into smaller "regions" that contain the *needed* information (e.g. nodes with coordinates, connections and some information on the ways) used for routing. This excludes borders, adresses, etc. Using those regions, we can dynamically load needed data for any routing-requests, therefor reducing memory-usage. -Routing is based on an A*-Algorithm using the direct point(node-coordinates)-to-point(goal-coordinates)-distance as base for queueing. \ No newline at end of file +Routing is based on an A*-Algorithm using a combination of distance-to-goal, roadPriority (e.g. highways over local roads) and turning-angles to get the heuristic value for next-node-visiting. + +After calculation we can output the path JSON formatted including total-distance and time (based on roadspeed), as well as each step (node). + +All of the aforementioned can be accessed via an API. + +Also we can render different images (path, area(loaded regions), weights) or a combination thereof. \ No newline at end of file