[OSRM-talk] SafestWay: OSRM + OSM = Making walking safer, one step at a time.

[Jeffrey Mealo]

Hello,

I'm writing an open source stack called Safest Way. It provides pedestrians
the safest way to walk based on crime data through a mobile application.

SafestWay began as a civic hackathon project in the city of Philadelphia
(USA). Due to a budget crunch, a number of our schools closed. This
lengthened the walk to/from school for many students.

The immediate goal is to help students find the safest way to walk to
school in my city. I present whatever I have done 12 days from now.

The overall goal is to make a software stack that any city with crime data
can roll out on modest hardware with as little technical experience as
possible.

OSRM is the easiest and fastest routing engine by far, but I have some
questions that cannot be easily communicated via the mailing list.

I want to make sure I'm going about things the right way.

In brief:

I need impedance, turn restrictions, and no one ways.

Since impedance is in a feature branch; right now the plan was just to feed
in crime as speed data.

The speed data would be fed into the .osm via a changeset.

I'm trying to find the fastest way to match crimes to ways, which ideally,
would break at every intersection.

Right now I'm using the GEOS library from Node.JS.

If possible would anyone be available for Skype or interested in working on
the project?

I was thinking of using the LUA profile to weight the crimes and do some
geospatial operations using SpatiaLite, however, getting SQLite working
from LUA isn't consistent with an easy to use and deploy stack :-)

Kudos on all your work so far; I hope my project helps bring more attention
to yours.

Thanks for your time,

Jeffrey Mealo
http://safestway.org/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/osrm-talk/attachments/20130411/f0bbf105/attachment.html>