Implementing a Safety Score-Based Routing Strategy in Valhalla #4240
-
Hello everybody, I am currently involved in a project aimed at suggesting routes considering a given route's perceived safety. The primary audience is women looking to navigate their surroundings with an additional layer of safety in mind. Our approach is to utilize OpenStreetMap (OSM) data, supplemented with additional data sources, to assign a "safety score" to each street (reported crime rates, presence of street lighting, etc.). The goal is to integrate this data into OSM and subsequently alter Valhalla's routing engine to consider this safety score as a penalty when determining optimal routes. Before delving deep into implementation, I'd like to get some feedback on whether this approach seems feasible. Is adding the score to OSM data the best approach? Can that information be added as a penalty in the routing calculation easily? Would it need to change something else? Is there an alternative method or approach we should consider? Additionally, is anyone aware of a similar project or implementation I could reference? Having some guidance or a starting point would be great. Any insights, guidance, or points of reference would be greatly appreciated. Thank you for taking the time to read. Best regards, |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 5 replies
-
When setting up a route for female preferences (on OpenStreetMap) , consider: Safety & Comfort:
Accessibility:
Amenities:
Rest & Weather Protection:
Public Transport:
1.) This is a good research topic, so check Google Scholar :
2.) 3.) |
Beta Was this translation helpful? Give feedback.
-
we've been asked this question in one form or another at least 10 times. i think it's about time to write up a proposal for supporting this feature. at a high level the idea is to allow a person running the routing service to include an 'overlay' layer on top of the graph which can hold a proprietary metric. the routing algorithms costing model and API then need to allow the request to specify whether or not the overlay should be used in edge/node costing and how. I'll volunteer to write up an official issue about this topic and some options on how we could add support for it. in the short term we don't have very good options. you could co opt the traffic data or the regular osm speed limit data but you still need to associate that data to osm/graph. you'd also need to modify the highway tags so that the hierarchies play nice with your data or disable hierarchies at request or data building time. it would work but I'd say the effort would be better spent adding first class support for the general feature as a whole |
Beta Was this translation helpful? Give feedback.
-
related: GIScience started a new "Safer Route" project: https://github.com/GIScience/Safer-Route |
Beta Was this translation helpful? Give feedback.
we've been asked this question in one form or another at least 10 times. i think it's about time to write up a proposal for supporting this feature.
at a high level the idea is to allow a person running the routing service to include an 'overlay' layer on top of the graph which can hold a proprietary metric. the routing algorithms costing model and API then need to allow the request to specify whether or not the overlay should be used in edge/node costing and how.
I'll volunteer to write up an official issue about this topic and some options on how we could add support for it.
in the short term we don't have very good options. you could co opt the traffic data or the regular osm speed lim…