Wireless Access Point collection, processing and reporting applications.

A Mellow Heeler collector observes wireless beacons and shares the observation w/a Mellow Heeler backend for parsing, storage and reporting.

Fixed site collectors assets use a dedicated Raspberry Pi which periodically write WAP observations to AWS S3 for storage. Mobile collection is performed using a Raspberry Pi augmented w/a GPS HAT for location and time reporting, and also writes observations to AWS S3.

Back end processing reads collected observations from AWS S3 and loads the results into postgresql for analysis and reporting. Here are some report examples.

1. Autonomous collection of wireless beacons.
2. Beacon database.
3. Markdown based summary of observations.

1. All times UTC
2. Location are +North, +East and truncated to fit a PostGreSQL float.
3. Collectors typically have two WLAN devices: wlan0 is organic to rPi and wlan1 is a TP-Link AC-1300 wlan0 is configured for local WAP, and wlan1 is used for collection.

1. bin/iwlist-header.sh reads the output of iwlist-scan.sh and produces a file with timestamp, location and other configuration details.
2. bin/iwlist-scan.sh invokes iwlist(8) to scan for WAP and write to file
3. bin/wombat*-to-s3.sh copy collected observations to AWS S3
4. bin/skunk-post.sh updates local mellow skunk instance.

1. bin/fresh-from-s3.sh copies from S3 to local file system
2. bin/full_cycle.sh performs full downlowd, parse/load and report cycle
3. bin/archiver.sh collects processed files into a tar(1) and save to AWS S3