Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update overview and accessibility docs [ci skip] #5680

Merged
merged 4 commits into from
May 7, 2024
Merged

Update overview and accessibility docs [ci skip] #5680

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
ffd8828
update overview and accessibility docs
abyrd Feb 10, 2024
28dd158
add link to analysis section
abyrd Feb 10, 2024
4d3e2df
Merge remote-tracking branch 'origin/dev-2.x' into abyrd/access-overv…
abyrd Apr 23, 2024
6588a9f
add separate Travel Time Analysis docs page
abyrd Apr 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
21 changes: 17 additions & 4 deletions docs/Accessibility.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,10 +2,23 @@

## Preamble

GTFS and Netex define accessibility primarily in terms of binary access for wheelchair users: it's
either on or off. Whilst it is the desire of the OTP developers to broaden the scope of
accessibility the lack of data limits us to use this definition in the implementation and in this
document.
In this document and in OTP, the term "accessibility" is used with what has become its most common
meaning: design of products, devices, services, vehicles, or environments to ensure they are usable by
people with disabilities. It has other meanings in other contexts (see below).
While accessibility is a complex subject, at this point GTFS and Netex mostly represent it very
simply as a yes/no possibility of wheelchair use. While OTP developers hope to broaden the
scope and nuance of accessibility support in OTP, the lack of detailed data from data producers
currently limits implementation and discussion in this document to this binary
"wheelchair accessible" definition.

The term "accessibility" has a completely separate, unrelated definition in the fields of
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Who is the intended audience for this explanation?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The audience is people who search for "OTP accessibility" when looking for analysis uses and land on this page of the docs. People who are trying to understand the situation with travel time surfaces and isochrones, and ending up on the wrong page. It is indeed a bit out of place here.

The ideal would be to expand and revise the other page that is specifically about analysis uses. That other page will probably just redirect people to other tools (after giving them some background in case they're following up on past projects / articles). Then this page (on the more common meaning of accessibility) would only need a single sentence along the lines of "if you're looking for the other meaning of accessibility, see analysis page (link)".

So I'll just move this text over to the analysis page and suggest a short link here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that would be great.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This update to the analysis docs page has long been on my mind since we talked about it in the past. But my sense in meetings is always that the fate/state of isochrone and one-to-many functionality is still being decided and I am not yet sure of those final decisions. But I think we can get this finalized soon.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Entur have publicly stated that they want to remove it, but haven't actually done it.

spatial analysis, urban transportation planning, and associated social sciences, where it refers to
quantitative indicators of how well-connected a particular location is to people or opportunities.
OpenTripPlanner has been widely used in research settings for the calculation of such accessibility
indicators. If this is what you're looking for, see the documentation sections [on isochrones](sandbox/TravelTime.md) and [analysis](Version-Comparison.md/#analysis).
Although this meaning of the term dates back many decades, it is less well known and has become a
source of confusion, so the academic and planning communities are gradually shifting to the
expression "access to opportunities", often shortened to "access".

## Unknown data

Expand Down
7 changes: 4 additions & 3 deletions docs/Product-Overview.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,16 +3,17 @@
## OpenTripPlanner project

OpenTripPlanner is a group of open source software applications that help individuals and organizations
calculate and deliver multimodal trip plans based on OpenStreetMap (OSM) and other standardized data
sources (e.g. GTFS, GBFS, NeTEx).
calculate and deliver multimodal trip plans based on a combination of open-standard data sources.
These include public transit services and schedules (GTFS and NeTEx) and OpenStreetMap (OSM), as
well as sources describing bicycle sharing or rental, ride hailing, and other services (e.g. GBFS).

A community of dozens of individuals and organizations work on OpenTripPlanner collaboratively to
improve multimodal trip planning best practices and to make it easier for public transit agencies and
public transit riders to publish and access information about transit services.

OpenTripPlanner deployments are locally managed in many different ways by many different types of organizations.
OpenTripPlanner consistently and dependably delivers multimodal trip plans to millions of riders
everyday in dozens of countries around the globe. The project is actively maintained by the community,
every day in dozens of countries around the globe. The project is actively maintained by the community,
with more than 50 commits most weeks during 2022, and 20 different developers having made 50 or more
commits during the life of the project.

Expand Down
Loading