Welcome
Welcome to the TCAT Wiki!⚓︎
This site explains how to use the open-source transportation accessibility tools and data developed by the Taskar Center for Accessible Technology (TCAT), especially OS-CONNECT (Washington State's connected pedestrian network dataset) and the TDEI (the infrastructure that stores and serves that data).
What's Your Goal?⚓︎
| If you want to… | Use |
|---|---|
| View | OS-CONNECT Data Viewer — a view-only map; no GIS required |
| Download | TDEI Portal — manage accounts, API keys, and access controls |
| Plan | Walksheds — scenario planning, project proposal evaluation, and prioritization |
| Route | AccessMap — a public routing app, no portal required |
User Journeys⚓︎
Choose your path: each one starts with the simplest document and then offers deeper options.
I want to use AccessMap: find and share accessible, customized pedestrian routes
Get Started: View the AccessMap user manual.
I work for a jurisdiction or agency: view pedestrian infrastructure and decide what to do next
Get Started: View the data and read a Jurisdiction Snapshot.
I want to import existing sidewalk, curb ramp, bus stop, or other data into the TDEI
Get Started: Review the Curb Points in TDEI tutorial.
I want to contribute as a mapper: map sidewalks, crossings, and curbs
Get Started: Follow the Mapping for OSW in OSM tutorial, and get started in your area or choose a Tasking Manager project.
I want to improve the data: validate OS-CONNECT data and report issues
Get Started: Open the OS-CONNECT Data Viewer, then report an issue.
I want to use OS-CONNECT data for planning, equity, and accessibility work
Get Started: Read the OS-CONNECT QA/QC reports and use Walksheds for scenario planning and prioritization.
I want to develop or research with the data: download data, use APIs, and work with schemas
Get Started: Follow the OS-CONNECT download guide and review the OpenSidewalks Schema documentation.
Key Takeaways⚓︎
If you remember only three things, remember these:
OS-CONNECT is the dataset — It is a connected pedestrian network for Washington State (sidewalks, crossings, curb ramps, and related features) in the OpenSidewalks schema, organized so it can be used for routing and analysis.
TDEI is the platform — It is where data can be accessed for downloads and APIs, and where tools like AccessMap, Walksheds, AVIV ScoutRoute, and Workspaces connect to the data.
AccessMap is the router — It uses OpenSidewalks Schema-formatted data to provide custom accessible pedestrian routing without requiring specialized tools.
Projects⚓︎
OS-CONNECT — Washington State connected pedestrian network dataset.
TDEI — Platform infrastructure for storing, serving, and integrating transportation accessibility data.
OpenSidewalks — The data standard/schema used to represent pedestrian networks as a connected graph.
Workspaces — Tools for creating and maintaining OSW datasets (via editors like Rapid and AVIV ScoutRoute).
AccessMap — Accessible multimodal routing and trip planning.
Walksheds — Analysis of access to destinations using the pedestrian network.
AVIV ScoutRoute — Mobile app for adding data into the existing pedestrian map. AVIV ScoutRoute enables everyone to make structured, clear, and direct contributions of surveyed data to enhance it or keep it up to date.
Additional TCAT projects are listed on the TCAT website.
Quick Concepts⚓︎
New to this? If you are unfamiliar with some of this terminology, start with these short explanations to learn the concepts in less than 5 minutes:
Points of Interest (POIs)
A point of interest (POI) is a specific, identifiable location that is relevant to pedestrians or travelers, such as a transit stop, park entrance, business, public facility, or other amenity. In the context of TCAT projects, POIs are used alongside pedestrian network data to analyze access to destinations and services.
Connected Networks
A connected network is a graph of pedestrian infrastructure — sidewalks, crossings, curb ramps, and other paths — where all elements are linked as Nodes, Edges, and Zones forming a complete, traversable network. This is in contrast to disconnected or partial datasets where features exist in isolation.
Why this matters:
- Routing — A connected network enables turn-by-turn pedestrian navigation and accessibility-focused trip planning (as in AccessMap), because every path segment connects to the next.
- Analysis — Connectivity allows for network-level analyses (such as walksheds), enabling gap detection and equity assessments — computations that require understanding how infrastructure elements relate to one another.
Walksheds
A walkshed is the area reachable via a specified mode of transport from a given location within a specified travel time or distance, considering the actual pedestrian network. Unlike a simple radius, a walkshed accounts for real-world path connectivity, barriers, and infrastructure conditions. The Walksheds tool uses pedestrian network data to compute and visualize these areas, enabling analysis of access to amenities and services.
Routing Profiles
A routing profile is a set of preferences and constraints that customize how a pedestrian route is calculated. For example, a routing profile may specify maximum acceptable incline, preference for curb ramps, or avoidance of unpaved surfaces. Tools like AccessMap use routing profiles to generate personalized, accessibility-aware directions based on individual needs.
Tutorials, User Manuals, and Guides⚓︎
Looking for step-by-step instructions? Start with our full Guides List or try Ctrl+K Search!