[Accessibility] Contents of Accessibility digest...

[Miloš Šmíd]

Hello friends,
after reading the last post I opened a discussion on AI Gemini to learn
more. I offer it as open.
https://gemini.google.com/app/8760b0c0ef383599
You can attribute. I communicate primarily in Czech, but with the help of a
translator I can have a discussion with you in English as well.
In the discussion there is also a summary of what I have saved and what I
would like to look at so that I can continue after a longer period of time
to help with the addition of Open Street Map accessibility data.
Here is the summary:
1. Key foreign projects (Inspiration from the USA)
• AccessMap (accessmap.app): A personalized route planner that uses
OpenStreetMap (OSM) data. Unlike regular maps, it can work with details
such as pavement slope, sound signaling and tactile elements.
• OpenSidewalks / OpenThePaths: Initiatives from the University of
Washington (Taskar Center). They create standards for how sidewalks and
paths should be mapped as a separate network, not just a "road feature".
• Philosophy: Maximum openness and use of global data (OSM) so that anyone
can create a navigation application without having to hold a monopoly on
data.
2. How to join from home (Web Tools for PC)
Instead of complex and often conservative OSM editors, we recommend:
• MapComplete (web version): mapcomplete.org/accessibility. It allows you
to click on the map and answer simple accessibility questions from your
computer. The data is automatically saved to OpenStreetMap with the correct
technical tags.
• JOSM: For advanced users who want to edit data in bulk (eg import metro
station descriptions).
3. Recommended set of tags (Brand) for the visually impaired
To "overprint" stagnant local projects, it is best to use internationally
comprehensible tags that are read by applications such as Lazarillo or
OsmAnd:
• tactile_paving=yes/no (Tactile paving/guide line)
• tactile_paving:type=ribbed/natural (Type: grooves / natural line - wall)
• crossing:sound=yes/no (Acoustic traffic light)
• crossing:vibration=yes (Vibration button on the traffic light)
• handrail=left/right/both (Handrail by the stairs - key for orientation)
• blind:description:cs=* (Custom detailed text description in Czech for
specifications that do not have a global tag).
________________________________________
FORM DESIGN (MapComplete Custom Theme)
If you would like to create your own "layer" in MapComplete specifically
for the Czech blind (e.g. for those metro stations), the form could look
like this:
1. Point of interest: Subway entrance / Crossing / Stop
2. Question 1: Is there a guide line? (Writes tactile_paving=yes)
3. Question 2: What type is it? (Options: Grooves in paving / Natural
guiding element)
4. Question 3: Is there an acoustic beacon? (Writes blind:beacon=yes)
5. Question 4: Activation type: (Options: VPN transmitter / Continuous beep)
6. Question 5: Free description for the blind: (Writes
blind:description:cs=...)
________________________________________
Next steps for you:
1. Explore the site: Open MapComplete Accessibility and try to find a place
you know well to see if the data is correct.
2. Contact Anat Caspi: If you want to offer your Mapotic data to the
AccessMap project, write to uwtcat at uw.edu. You can state that you are
mapping the Prague metro and looking for a way to standardize this data for
their system.
3. Local community: If you encounter resistance in the Czech OSM community,
simply enter the data with the blind: prefix. No one will delete them for
you, and the global application for the blind will see them.
I look forward to further discussion with you.
I am interested in the issue of mapping for the visually impaired, I am
visually impaired myself, and also in mapping mainly transport hubs, metro
stations and railway stations and cities in the Czech Republic and
compiling route descriptions for the blind.
I wish you all the best and have a great day.
Miloš Šmíd
Czech Republic
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/accessibility/attachments/20260118/60bd56c9/attachment.htm>