I’ve been doing more testing with this. I’m quite certain the Pokemon Radar doesn’t work. Thinking about it, as an IT guy, if I were implementing the Pokemon Go game and it was vastly oversubscribed and struggling, turning off the GIS radius search (Pokemon Radar) feature would save a lot of CPU on the servers and be a good option to increase logon performance.
I imagine it will be a number of months before The Pokemon Company decides whether it’s worth investing in the hardware to implement the Pokemon radar search feature. They’ll be wanting to ensure that the peak usage isn’t just a fad that’ll fade away.
Using the Pokemon API, I can see that the Pokemon Radar kind of works. It’s not doing a radius search, so the proximity to the user isn’t accurate (hence why they are always show all Pokemon being 3 steps away). Instead, it’s showing all Pokemon within a square coordinate range.
I would work out how big this range is, but there’s no point now that I’ve found websites like PokeVision, that let me show the exact locations of Pokemon as they appear on my radar.
I doubt they’ll be in a rush to fix it. GIS radius search is not simple and uses lots of CPU. What they currently show is all Pokemon inside a square map – much easier because you just compare the horizontal and vertical coordinates (basic maths).
That said, they seem to have fixed the login server issue so far.