I think I'll try to set the trend for a bimonthly status update. At this point the data retrieval process is essentially complete and contains the following functionality:
- The ability to add/update geocaches, geocachers, and logs in the LCP database from pocket queries via the Geocaching.com Live API.
- The ability to add/update geocaches, geocachers, and logs in the LCP database directly via the Geocaching.com Live API.
- The ability to detect archived geocaches and remove them and their associated logs from the LCP DB via the Geocaching.com Live API.
- The ability to utilize any number of geocaching.com accounts concurrently for the data collection process.
- All Geocaching.com Live API transaction/cache limits are honored.
- A cache update will be scheduled 7 days after the last cache update. A cache update will synch geocache data and retrieve the latest 30 geocache logs.
- A full cache update will be scheduled 90 days after the last full cache update. A full cache update will synch both geocache data and all geocache logs.
What's left with data retrieval is to add some smarts to how error conditions are handled. For example, if the Geocaching.com Live API is down for maintenance, it is probably best to not continuously attempt to access it.
So far, running the data retrieval processes on my laptop, I have a database with 52,277 geocaches, 96,613 geocachers, and 3,700,621 found logs. From what I'm seeing, I believe my laptop could handle a 100,000 cache DB (about the size of the LonelyCache Project

). I'm looking forward to running this on real web and DB servers

.
Again, I want to emphasize that though we've made a lot of progress, there is still a lot more left to do. For example, we still need to generate the statistics and design and create the web pages. Heck, we don't even
have a logo yet

.
--
Russell