Skip to content

For trail managers

You don't buy counters from us. You subscribe to a measured, managed site. Everything below is our problem, not yours.

What a site includes

  • The hardware, installed and maintained. Solar-powered radar counters, placed where they answer your questions. We install them, monitor them, swap batteries, and replace units. The equipment stays ours, so upgrades never cost you a procurement cycle.
  • A portal for your organization. Your trails, your team's logins, and data scoped to your organization.
  • A dashboard that answers the real questions first. How many today? How many over the past twelve months? Is usage growing? Every figure is labeled observed, estimated, or modeled, so you always know what kind of number you're quoting.
  • Grant-ready exports. CSV downloads and a documented API, with the methodology citation your grant application needs.
  • A published method. Our How We Count page is public. When a council member or auditor asks where your number came from, you link them to it.

What your dashboard shows

  • Daily, weekly, and seasonal usage by site, with cyclists and pedestrians counted separately.
  • Directional flow: which way people travel by time of day.
  • Weather-adjusted patterns and a 7-day outlook from our usage model.
  • Counter health and coverage. Uptime is part of your data, so you always know what was observed.

Numbers that hold up

Counts are observed. Site visits are estimated by merging overlapping sensors. Trail-wide trips come from a published model. Each is labeled as what it is, so a figure that goes into a grant application or a council presentation already has a public, citable method behind it.

Start with your question

An annual figure for a grant. Set the range to Last 12 months, pick the Trips lens, and export it. Cite it as: "Modeled trail trips from Swamp Rabbit Analytics; method published at docs.swamprabbitanalytics.com/how-we-count/." Trips are published as a range; if your report needs a single value, use the displayed central estimate and keep the citation.

Why usage changed. Compare the same site and range across periods, then read the weather-adjusted growth and pattern views. Both come from the usage model, so fleet growth and changing weather are not counted as changes in trail demand.

Where the next counter goes. Use coverage and spacing to find the largest unobserved gaps. The best next site is the one that narrows uncertainty on the question you need answered, not the busiest available location.