[Resquest] showing targeted area before scanning

[kaiyan910]

is it possible to create a simple html page like TBTerra's viewWork.html to show the scan area ?

currently I can just guess the area to set the "range" in settings it is quite trouble for me ... BTW may I ask what does "120r in m" means in the range settings ? If I set range = 8 the real world radius equal 120 * 8 meters ?

thanks in advance

[furier]

It would be cool to be able to see all registered spawn points as well, and just put a map overlay over the map for the estimated scan area.

[furier]

Anyways @kaiyan910 to my understanding the range is layers of hexagons around the center hexagon, each hexagon has an approx diameter of 70 meters (i can't confirm that) so it should be 70 * 8 + (70 / 2) when adding the radius of the center hexagon, which the other layers are stacked around.

[seikur0]

"If I set range = 8 the real world radius equal 120 * 8 meters ?"

Yes, only approximately though. In the next version, I'll get rid of that system and make it possible to just set a real circular area and a radius.

[darkforcesjedi]

There are existing tools for tiling a map with hexagons (Seikur0 linked one on the main page). I created a tool for myself to subdivide my map into smaller regions (http://jsfiddle.net/darkforcesjedi/5yunzf1q/).

@seikur0 it would be beneficial to leave the hexagonal layering as an option instead of replace it entirely. The "snowflake" shape that is generated by a circle fully covered by hexagons does not easily tile to cover complex shapes.

Alternatively, the bounds could be specified by a polyline. There are online tools (like plotaroute.com) that can be used to click points to generate a KML or GPX file with the coordinates of each point. To test if a point ("x") is inside the polyline, you just need to know a point outside of the shape ("z"). If the line connecting x-z intersects an odd number of the line segments comprising the polyline, then x is inside the shape. You could get a rough estimate the center of the shape using the average lat/lng of all the points and start tiling outward from there. For each hex you generate you can test (all 6 corners) if it is inside the shape and delete the ones you don't need. The lat/lng coordinate system will cause issues if the shape contains or wraps around one of the poles, but I don't think it is likely someone will search for pokemon at the north or south pole.