codeforamerica / OpenTrails

OpenTrails (Open Trail System Specification) Converter & Validator
http://open-trails.herokuapp.com/
39 stars 9 forks source link

"wheelchair" identification/creation #32

Closed alanjosephwilliams closed 10 years ago

alanjosephwilliams commented 10 years ago

Goal

Identify whether or not there is an existing column that specifies biking as an appropriate use. In OpenTrails parlance, we refer to that field as "wheelchair" (derived from OSM).

The appropriate value is a boolean "yes" or "no"

"biking" should be read as synonymous with road biking, but discrete from mountain biking.

Sample Data Use Case A: Discrete "wheelchair" Field Exists

In the majority of sample data we have on hand, a column specifying whether or not hiking is appropriate does exist. Most use the NRPA standard "accessible". However, there is heterogeneity in how the boolean values are expressed (y, yes, no, n, Yes, No).

Key strings for that column name include: "accessible", "adaaccess", "accesibil", "ada"

  1. Identify whether or not a column with key strings exists.
  2. Assign "yes" or "no" value to "wheelchair" attribute based on range of aforementioned boolean values found in sample data.

    Sample Data Use Case B: No Use Data Exists

Among the sample data, two agency shapefiles contain no data about appropriate use of trails. In OpenTrails, "use" attributes are not required to exist or have a value.

  1. Identify that no accessibility column exists.
  2. Make it clear to the user that we will create an attribute in their OpenTrails output, as it is recommended.
  3. Leave that value null.
migurski commented 10 years ago

Implemented in find_segment_wheelchair_use().