"[Analysis] Distance Polling Frequency Test"

#PokemonGO: So, got into a bit of a debate with another traveler over distance polling frequency, and as a result ran a test to dispute some of his findings based on contrary information I had from a while back. As our comment chain is a bit long and has received a fair few downvotes, I figured it was worth reposting my findings as a separate thread in order to be an easier to find source of information for those that may be interested.(if you wish to read the bickering that prompted this, it can be found here )Edit: It has been pointed out to me bu /u/Onad55 that it would be more effective to crowd source better theories/more rigorous (or simply repeat) testing in order to better understand this issue as a community.So; where we are currently:I have run some prior testing into polling frequency, hit a brick wall in terms of getting any way to test conclusively (basically, as I see it, we are using the app to get data on how the app communicates data, so if we don't know exactly how the app is communicating this data, how do we verify the data we are collecting - kind of a conundrum). I had satisfied myself with an answer stemming from MITM data (capturing the packets sent to the server) on an old version of the apk, showing a distance polling frequency of 15sec (a command getmapobjects was sent to the server every 15sec, it was understood this was used for gps tracking and to draw the game objects the user should be in range of at a given time). However, given the many changes to the game since, this is not necessarily still the case.In the comment thread I linked above, when giving this as an answer to somebody's question, /u/Onad55 posted an opposing point tested hypothesis (can be found in his response to this thread here ), to which I posted a test I believed countered his findings that can be found in my response here which lined up (roughly speaking) with the historic MITM data.Now, the only way to consolidate both tests is that either (or both) of our tests have (a) confounding variable(s) that have not been taken into account. Both of us have made suggestions during our bickering (see above) as to what could be wrong with each other's methodology, and are now opening the floor to suggestions; further testing; more rigorous analysis, better understanding of GPS communications etc.So, fellow travelers, lets see if we can't crack this one together and come out with a solid theory and have a better understanding of the accuracy (or, arguably, lack-thereof) of in game distance tracking. via /r/TheSilphRoad http://ift.tt/2fEDVZI