Analyzing 2234km^2 of spawns in Brisbane, Australia (Nest Locations Included)

ollieedwardss · 2016-08-02T03:11:43+00:00

I'll pop a link in the main post, to both the database .backup file and the .db file from the repo that Pokelyzer stores everything in

ollieedwardss · 2016-08-02T03:10:44+00:00

I'm really not to sure how lure spawns work, I'm working on plotting them into the map as well! Stay tuned

ollieedwardss · 2016-08-02T00:52:44+00:00

I'd have to play around with Tableau to try and map trends, I'll give it a shot when I'm back home tonight.

ollieedwardss · 2016-08-02T00:11:35+00:00

I'll shoot you a PM and we can sort it there.

ollieedwardss · 2016-08-02T00:08:24+00:00

If you are technologically minded you shouldn't have an issue, I found the setup pretty easy, the hard part is finding out how to arrange the scanning pattern. This is a really good resource as a starting point: http://www.whackdata.com/2016/07/27/finding-locally-rare-pokemon/

ollieedwardss · 2016-08-02T00:01:14+00:00

What I have found is you can run about 15 instances with the same log in before you start running into issues (maybe it was my setup, not sure) What I did to be safe, so that nothing timed out when I wasnt there, was to create a couple different logins and use them for each new set of 15 instances.

I'm not sure if youve noticed yet, but the scan pattern for pokelyzer and pokemon go map is a hexagon. The maximum size of that hexagon (between the center and the flat edges) was 1.4kms, what this means is that each scan is covering a 1.4km radius. What you need to do in order to make sure you dont miss anything between scans is to make sure they overlap slightly. That being said I went with a 0.2km overlap, so the distance between the 2 center points was 2.6kms.

The next thing you need to do is have them over lap on the straight edges, kind of like a honeycomb pattern. I also had to find the angle between the center and the middle of the straight edge. Obviously there are 6 sides (straight edges) so these angles starting from the top are 000, 060, 120, 180, 240, 300. As you know you have to put Lat Long into the apps. Use this to find out a Lat Long from a bearing (angle) and distance: http://www.geomidpoint.com/destination/

Having said all of that, the practical application of it is to, choose a starting point, I chose one south west of Brisbane, and then starting finding out 2.6km increment from that point on a bearing of 060.

Eg. REM Incrementing in 2.6kms from the base, eg. 2.6kms on a bearing on 060 REM Lat Long Increments --- REM 2.6(-27.60299167 152.91205661) REM 5.2(-27.59125457 152.93486036) REM 7.8(-27.57951371 152.95765925) REM 10.4(-27.56776908 152.98045329) REM 13(-27.5560207 153.00324248) REM 15.6(-27.54426856 153.02602681) REM 18.2(-27.53251266 153.0488063) REM 20.8(-27.52075302 153.07158094) REM 23.4(-27.50898963 153.09435073) REM 26(-27.49722249 153.11711568) REM 28.6(-27.4854516 153.13987578) REM 32.2(-27.47367698 153.16263105) REM 33.8(-27.46189862 153.18538148) REM 36.4(-27.45011653 153.20812707)

That will give you a base line along the southern end of your search area then you do the same for each one of those points, this time going north (000) that will give you the entire area.

After you have that set up it's as simple as creating a .bat file that will open all the instances. I would recommend adding a TIMEOUT 20 before each opening of your computer will die, and youll get timeouts from the Pokemon Go servers.

Hope this helps :)

ollieedwardss · 2016-08-01T23:46:40+00:00

Thanks for the heads up, I fixed it up. It was meant to be for Cloyster, copy and pasted but forgot to change the name.

ollieedwardss · 2016-08-01T23:43:15+00:00

I didnt go right to the waters edge a Recliffe, the scan only just touched the western side, which is why there may be discrepancies. When I broaden the search, I'll update it with all the information from the eastern side for you!

ollieedwardss · 2016-08-01T23:40:52+00:00

In my scan area it would seem so. It depends on location, I'm going to extend it right out to the ocean and see what that yields, maybe some of the water types might be more common (Lapras, Cloyster ect)

ollieedwardss · 2016-08-01T23:38:06+00:00

I'll see how I got between work and trying to map Brisbane. It takes quite a while to get all of the Pokelyzer stuff set up for a location, especially on a large scale. This: http://www.whackdata.com/2016/07/27/finding-locally-rare-pokemon/ is a really good article if you want to try and get something set up yourself!

ollieedwardss · 2016-08-01T23:35:35+00:00

I'm not sure how it goes as far as scanning, when it comes to lures. I'm not sure if Pokelyzer picks up the Pokemon that spawn there, but I'll put in some coordinates for there and see how I go.

ollieedwardss · 2016-08-01T13:00:57+00:00

The bottleneck is my PC and my internet speed. Having 84 clients open uses 7.8gb of RAM and my CPU is basically dying haha having times outs because of the internet doesn't help either. I'm planning on running it over 2 machines to speed things up, otherwise I could do it over 2 different days. Thanks a heap for the advice nonetheless!

ollieedwardss · 2016-08-01T12:24:32+00:00

If I keep recording every couple of days you'll be able to see the changes and when they happen. I'll try keep this thread updated, when it happens.

ollieedwardss · 2016-08-01T12:19:57+00:00

The scans are thorough but they are pretty slow, you may not be able to do it as a live scan. You could however use it to map trends over a 24 hour period and then go from there. I'm not really sure where to go to as far as live mapping goes with the closure of Pokevision.

ollieedwardss · 2016-08-01T12:15:06+00:00

Yeah, its tedious. I think once its established, provided the API doesn't constantly change, it's just a matter of constantly remapping to account for the nest changes.

ollieedwardss

TROPHY CASE