Fixed problem with duplicate check in storeCityInfo only using apiKeyId and not guestId.  The issue is that reverse IP checkin records have apiKeyId=0 for all users, so any user having logged in in a given city on a given day would prevent a cities entry being recorded for subsequent users.  Unfortunately, the system assumes Facet_VisitedCity will never be empty for a given user and fails pretty badly if it is.