[Accessibility] Accessible routing service

[Simone Gadenz]

Dear all,

I have already posted a previous message about a participatory process we
are coordinating in one small town of Italy. It is about accessibility for
people with reduced mobiity and we are interested in shatring with similar
experience and also in coordinating for putting the results on OSM.

Anybody with similar experience?

Thanks

Simone

2010/5/8 ant <antofosm at gmail.com>

> Hi Ota,
>
> sounds interesting. The web page idea you described is very similar to
> ours. Btw, there are already some tags introduced especially for the
> blind, e.g. for tactile pavings. See
> http://wiki.openstreetmap.org/wiki/OSM_for_the_blind for related stuff.
>
> For the routing part, you might want to consider pgRouting:
> http://pgrouting.postlbs.org/
>
> Keep up the good work.
>
> Greetings
> ant
>
> On 08.05.2010 09:59, Ota Procházka wrote:
> > Hi,
> >
> > I am just finishing my project. The aim is to create text description
> > of some route for visualy impaired person. In first phase  of
> > project(finished), the description will be created by operators
> > working in small organization called SONS - it contains navigation
> > call center for blind. In second stage, there will be web page with
> > two input fields, where you put the start point and end point and
> > optionally some settings and then just press button to generate
> > description.
> >
> > I collected some tags and proposed missing tags needed for visualy
> > impaired and mapped with them some small test area (in Prague). I
> > updated Mapnik rendering style to be able to render important places,
> > footways etc. and used it as extra layer (for some aerial maps, where
> > operator can better check generated description). The layer containing
> > objects from OSM on map is active and operator can select points on it
> > to create route - I have no routing implemened yet. I have webservice
> > (written in JEE), which takes coordinates params and generates
> > description. It uses Postgis (Mapnik's database) for orientation and
> > it uses libosm (I had to little bit extend DownloadingDataSet class)
> > to comunicate with OSM server and to download exact information about
> > elements.
> >
> > I did some testing with operators from SONS navigation call center to
> > test generated description. There were some problems, but in fact, it
> > was succesffull.
> > On monday, I plan to test it with blind person in terrain.
> >
> > I wrote about this project to this forum, but nobody reply - may be I
> > wrote it in little bit stupid way :(.
> >
> > The biggest problem is, that I need it for Czech organisation and
> > nearly all my texts are in Czech language. But if you are in some part
> > interested, i can translate it.
> >
> > Ota
> >
> > 2010/5/7 ant<antofosm at gmail.com>:
> >> Hi,
> >>
> >> I want to inform you about a student project I'm doing about an
> >> accessible routing service. Please see the Wiki page:
> >>
> >> http://wiki.openstreetmap.org/wiki/Accessible_Routing
> >>
> >> Greetings
> >> ant
> >>
> >> _______________________________________________
> >> Accessibility mailing list
> >> Accessibility at openstreetmap.org
> >> http://lists.openstreetmap.org/listinfo/accessibility
> >>
> >> To unsubscribe from this mailing list send an empty email to
> accessibility-unsubscribe at openstreetmap.org
> >>
> >
> > _______________________________________________
> > Accessibility mailing list
> > Accessibility at openstreetmap.org
> > http://lists.openstreetmap.org/listinfo/accessibility
> >
> > To unsubscribe from this mailing list send an empty email to
> accessibility-unsubscribe at openstreetmap.org
>
>
> _______________________________________________
> Accessibility mailing list
> Accessibility at openstreetmap.org
> http://lists.openstreetmap.org/listinfo/accessibility
>
> To unsubscribe from this mailing list send an empty email to
> accessibility-unsubscribe at openstreetmap.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/accessibility/attachments/20100510/68851b0f/attachment.html>