jxmorris12 / PokemonGo-Finder

Live visualization of all the pokemon in your area... and more!
GNU General Public License v3.0
171 stars 43 forks source link

Scan radius changed from API #54

Open xcheneric opened 8 years ago

xcheneric commented 8 years ago

https://www.reddit.com/r/pokemongodev/comments/4v73aj/psa_scan_radius_was_changed_from_100m_to_70m/

How do we apply the fix here?

Silvawar14 commented 8 years ago

+1

Greatly Needed.

StraightCircle commented 8 years ago

hmm. Ive modified this code for myself quite a bit but if you edit main.py with notepad and look under the def main(): function you will see a line that says: set_location_coords(x * 0.0025 + origin_lat, y * 0.0025 + origin_lon, 0)

the 0.0025 are the latitude and longitude offsets per step. so you will need to change those numbers. Note that the offsets are in degrees not in meters so you would need to figure out the meter to degrees lat and meters to degrees long conversion. this depends on your geographical location.

To have full coverage @ the now 70m scan radius your per step offset distance should be 70 * 1.4 = 100 meters (due to overlap between scans).

Also note the this code also scans at a few cell tower locations near your specified point as well so the actual visible radius per specified scan location is larger than the 70m (albeit its a bit random).

JaredBanyard commented 8 years ago

+1

bonswouar commented 8 years ago

This has been fixed on the original repo : https://github.com/AHAAAAAAA/PokemonGo-Map/pull/2610 Maybe it'd be a good idea to merge the original master ? (" 54 commits ahead, 402 commits behind AHAAAAAAA:master." )

i8aNooB commented 8 years ago

The scanning logic is different between the master and this fork. As per StraightCircle's comment - I changed my value to 0.0017, its working well again for me.

xcheneric commented 8 years ago

@i8aNooB Did you change both line 620 and 630, or just 620?

i8aNooB commented 8 years ago

@xcheneric Just 620, 630 is a print stmt that has no affect on the scanning. I also included a 3 second delay at the start of the scanning method - apprently the server needs it now? Just note you will need to increase the step size in your config.json if you want to scan the same size area as before.

Silvawar14 commented 8 years ago

Where/how did you incorporate a 3 second delay?