From 311c1301c056e2d5c6c7497667437fc30e2b4c16 Mon Sep 17 00:00:00 2001 From: gabrielwol <80077912+gabrielwol@users.noreply.github.com> Date: Wed, 31 Jul 2024 13:59:18 +0000 Subject: [PATCH] #984 replace missing readme sections --- volumes/ecocounter/readme.md | 47 +++++++++++++++++++++++++++++++----- 1 file changed, 41 insertions(+), 6 deletions(-) diff --git a/volumes/ecocounter/readme.md b/volumes/ecocounter/readme.md index 3f8c36d65..5e249ca1a 100644 --- a/volumes/ecocounter/readme.md +++ b/volumes/ecocounter/readme.md @@ -1,11 +1,17 @@ +# Ecocounter + - - [Discontinuities](#discontinuities) - - [Using the Ecocounter API](#using-the-ecocounter-api) - - [Note](#note) - - [Historical data](#historical-data) - - [ecocounter_pull DAG](#ecocounter_pull-dag) - - [ecocounter_check DAG](#ecocounter_check-dag) +- [Bicycle loop detectors](#bicycle-loop-detectors) + - [Installation types](#installation-types) + - [Ecocounter data](#ecocounter-data) + - [Flows - what we know](#flows---what-we-know) + - [Discontinuities](#discontinuities) + - [Using the Ecocounter API](#using-the-ecocounter-api) + - [Note](#note) + - [Historical data](#historical-data) + - [`ecocounter_pull` DAG](#ecocounter_pull-dag) + - [`ecocounter_check` DAG](#ecocounter_check-dag) - [SQL Tables](#sql-tables) - [Main Tables](#main-tables) - [`ecocounter.sites_unfiltered`](#ecocountersites_unfiltered) @@ -21,6 +27,35 @@ +# Bicycle loop detectors + +This dataset comes from a small but growing number of permanent [loop detectors](https://en.wikipedia.org/wiki/Induction_loop) installed within designated bicycle infrastructure such as bike lanes and multi-use paths. This is actually one of our older data collection programs, and the data have been handled in a number of ways over the years and now reside in a couple different places in the `bigdata` database. + +Ecocounter is the vendor that manages our current sensor installations. There is a web dashboard at https://www.eco-visio.net that should show all active installations. + +## Installation types +There are two types of sensors, which can be easily distinguished. The single sensor installations, as below simply count the number of bikes that pass over the sensor. These are installed in one-way infrastructure such as a typical bike lane. + +![a single ecocounter sensor installed in a one-way bike lane](./single-sensor.jpg) + +Increasingly however newer installations are using a double sensor that can detect the direction of travel as well. In cases like the image below this allows us to measure contra-flow travel within the bike lane. + +![a double sensor installed in a one-way bike lane](./double-sensor.jpg) + +Sometimes these paired sensors are themselves installed in pairs, giving four measured flows per site, two per lane. + +![a pair of bidirectional sensors recently installed in a multi-use path](double-double-sensor.jpg) + +## Ecocounter data + +Data from these sensors is stored in the `ecocounter` schema in three **views**: + +* `sites` +* `flows` +* `counts` + +A **site** is a distinct location, sometimes referring to one and sometimes to two directions of travel on the same path or street. A site is recorded as a point geometry at the centroid of the sensor(s) it represents. + A **flow** (sometimes also referred to as a _channel_) is a direction of travel recorded at a site. A site may have 1, 2, or 4 flows depending on whether one or two sensors are installed and whether they record the two directions of travel separately. Each flow has `counts` of bikes at regularly spaced intervals. All sensors now use 15 minute bins though some previously were configured with 30 minute or one-hour bins. The bin size is indicated in the `flows` table and the `counts` table gives the _start_ time of the bin.