Responsible data use

WAC exists because many public agencies and traveler-information platforms make useful transportation information available to the public. The docs should make that provenance visible while respecting the services that publish the original data.

Our approach

• Credit upstream agencies and platforms wherever practical.
• Prefer official access paths and published terms when they exist.
• Keep data collection modest and purpose-limited.
• Cache, normalize, and deduplicate so the public map does not repeatedly ask upstream systems for the same work.
• Avoid publishing instructions that would make it easier to duplicate WAC's collection layer or amplify load against upstream services.

What we document

We document who the source is, what kind of data WAC uses, how that data appears on the map, how fresh it is expected to be, and what limitations users should understand.

What we intentionally omit

We do not document hidden endpoint discovery, request parameters, query shapes, pagination behavior, retry strategy, rate-limit workarounds, scraper code, production ETL commands, or private infrastructure details.

If you need direct data access, use the upstream provider's official developer program, open-data portal, public documentation, or contact channel.