[Accessibility] Similar project

Ota Procházka otaprochazka at gmail.com
Tue Mar 2 12:03:55 GMT 2010


Hello,

my name is Ota, I am student of computer science (exactly system
programming on Czech Technical University). I am writing my thesis.
Topic is "System for creation of route description for visually
impaired". It's based on OpenStreetMap project. Task of this project
is similar to my task, at least at some points.

I am guessing from main page of LoroDux, that now there is a stage,
when you found student for programming task. I went throught nearly
all pages linked from main page, mailing list and found a lot of
interesting pages. The best summarization I found is on
http://wiki.openstreetmap.org/wiki/LoroDux/Requirements. However it is
not so general.

1. What i am looking for is some summary page of proposed tags for
accessibility. I am nearly sure, there was one, but I am not able to
find it again. The best matching page is
http://wiki.openstreetmap.org/wiki/Category:Visual_Impairment, but
it's not really related to proposed tags for accessibility.
In mailing list, it was discussed once. Some guy asked for it and he
got reply, that he should try something and then refer, what was good.
So may be I am just asking, if there is any change.

2. I have question about architecture. Do you plan to use only OSM
servers to put your tags in and render from them to
http://www.blind.accessiblemaps.org/ or do you want to have a copy on
other machine and make actualization periodically(and render from your
server). In case of your own server, do you plan to allow direct
editation (not just throught actuallizations).

2.1 Do you plan to use server technologies (for routing, for some
webpage, some customization etc...) or there will be just mobile
phones and some low lovel server or DB (2 tier)

2.2 Do you plan to have phones connected to internet and communicate
with server or maps will by uploaded to device and program will
contain everything needed?

3. Do you plan to use custom stylesheets for Osmarender and Mapnik for
rendering, or will you use only layers with txt fles like used on
blind.accessiblemaps.org.

4. Routing. Is there some plan? As proposed in
http://lists.openstreetmap.org/pipermail/accessibility/2009-November/000045.html
to use Gosmore or Navit, or I found
http://wiki.openstreetmap.org/wiki/Traveling_Salesman, which can be
probably after customization used on JEE server. Good routing work is
on http://map.umd.edu/map/# , it's good base for routing disabled
people.

I am sorry, i am little bit confused. I have absolutely no idea and I
am not able to find it anywhere, how do you plan to make your
achitecture. And it is being already programmed.

I will try to describe, what i am going to do.

What is my plan:
Task: Create text description of way for visually impaired person,
which contains enought information to go on their own. There is no GPS
expected. It is going to be used only on some frequently used ways.

a. Collect some tags for accessibility and propose new tags. There
should be one page with all tags related.
b. Make decision about point 2.
c. Install and prepare server in case its needed.
d. Make some stylesheets for Mapnik and Osmarender.
e. Make page, which is showing specially rendered map.
f. Find some test area.

This allows to start efficient mapping.

g. Find parameters needed for routing. (no stairs, no crossing without
sound, ....)
h. Make some server code
     1. Create routing alghoritm.
     2. Prepare web page for disabled.
i. Output of routing algorith should be some special language, which
can be translated to text in all languages or used in another way(draw
way on map etc). It should be able to contain not just way, but POI
near way, which can be usefull for disabled (specially blind)
Not universal but needed for my task
j. Make transformation of routing language to text.
k. Give a chance to people interested in to change output.

I am sure, we can cooperate in some tasks. But as I wrote, i don't
know, how your application will work. Can you make some suggestion?

Thanks for reading such long mail :)




More information about the Accessibility mailing list