docs.ourhike.org/data

How the data is built

OurHike does not survey trails. It gathers what parks, forests, agencies and trail clubs publish, checks it, and turns it into the files your phone downloads. Closures, warnings and other notices are rebuilt several times a day. Trail lines, waypoints and elevation reach your phone in a release, about once a month.

  1. 1 · Gather What 0 organizations and shared sources publish, from national agencies to local trail clubs, fetched as published into a private store.
  2. 2 · Build and check 319 dbt models clean and join it, and every build runs its checks. How the last ones went is on Data quality.
  3. 3 · Phone files Map tiles and the files the app downloads, such as trail_closures.json, published at data.ourhike.org.

Every table, in dbt’s docs →

The counts on this page are taken from OurHike’s source code each time the page is built: the organizations’ folders under pipeline/extract/ and the models under pipeline/dbt/models/.