from AP records to Observation records

[Don Park]

Over the weekend I realized what Geomena is recording is not APs
themselves but observations of APs. Code has been pushed, mostly
couchdb code changes, to treat entries as observations, of which there
could be many for a single access point.

What this paves the way for:
* averaging of the location of multiple records
* observing an ESSID (name) change over time

The POST action always creates a new couchdb record. This is what the
client apps are using. The front page now calls the total count
"observations" which is more accurate. I'm still working on a way to
count the unique access points among the observation records.

When looking at an individual AP on the website, it shows how many
observations exist for that AP. The rest of the page is always from
the most recent observation. Also a W3C lookup (what the browser does)
uses the most recent observation.

Let me know if anything seems weird. There are some unit tests and
cucumber tests to help catch problems, too.

Don


--
Subscription settings: http://groups.google.com/group/geomena/subscribe?hl=en