You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on a project that suggests routes based on a street's perceived safety, primarily for women who seek an added assurance of security as they navigate.
We have employed Itinero as our routing engine and are pleased with its performance. Our goal is to combine OpenStreetMap (OSM) data with external sources to give each street a "safety score" based on factors such as reported crime rates, presence of street lighting, etc. We hope to then prioritize these scores when generating routes.
From my examination of the code, Itinero seems to compute weights generally during the initial OSM data load. Subsequent route calculations seem to use this pre-calculated weight data. Given this, for our project, it appears we'd need to regenerate our routing database frequently—every time our safety score data is updated, in fact.
Is our understanding and approach accurate? Is there a way for us to dynamically adjust weight calculations by incorporating our safety scores? What would be your recommended method to achieve our objectives?
Any insights would be greatly appreciated, and thank you for the invaluable work you've put into Itinero.
The text was updated successfully, but these errors were encountered:
Hello @xivk ,
I am working on a project that suggests routes based on a street's perceived safety, primarily for women who seek an added assurance of security as they navigate.
We have employed Itinero as our routing engine and are pleased with its performance. Our goal is to combine OpenStreetMap (OSM) data with external sources to give each street a "safety score" based on factors such as reported crime rates, presence of street lighting, etc. We hope to then prioritize these scores when generating routes.
From my examination of the code, Itinero seems to compute weights generally during the initial OSM data load. Subsequent route calculations seem to use this pre-calculated weight data. Given this, for our project, it appears we'd need to regenerate our routing database frequently—every time our safety score data is updated, in fact.
Is our understanding and approach accurate? Is there a way for us to dynamically adjust weight calculations by incorporating our safety scores? What would be your recommended method to achieve our objectives?
Any insights would be greatly appreciated, and thank you for the invaluable work you've put into Itinero.
The text was updated successfully, but these errors were encountered: