StarBrand, on 01 May 2012 - 07:07 PM, said:
I understand that v2 of the new cache submission process will have some form of a distance checker but I imagine it will be somewhat limited.
I'll be curious to see what they come up with. Here's how I would do it.
Upon clicking on a "Confirm Coordinates on Map" button in the "Location" step of the new CSP it would do the following:
First, it would query to database to get a list of caches within 2.1 miles of the specified coordinates and stuff the results in a list.
When displaying the icon on a map it would test if there are any traditional caches on that list within .1 miles of the coordinates. If so, it would draw a red circle .1 miles around the icon, display any other caches within that circle (with a popup that will allow you to get to the complete listing), and disable the "Continue" button. If the user was not a PM it would not display any PMO caches on the map, but it could list the Name/GC code so that the user could contact the owner to get general idea for which way they may need to move their cache.
Next, it would check for Multi/Puzzle caches (all physical waypoints) that were within 2.1 miles. If there are any multi/puzzle caches on the list that are within 2.1 miles it could display an icon at the published coordinates of any caches which might
cause a proximity conflict, and a yellow circle with a 2.1 mile radius around the specified coordinates. Granted, there may be other puzzle/multi cache outside the 2.1 mile radius but it would at least warn the person trying to submit a cache that there are (and identify which ones) caches which might cause a problem.
It's not a perfect solution, but at least it would keep someone from submitting a listing when there is a confirmed proximity issue, and save some reviewer time. It would also identify caches which might
cause proximity issues without exposing a means of "battleshipping" the final coordinates of a puzzle/multi. Heck, it could even suggest that there are already a bunch of caches nearby, and recommend choosing a different location "where cache saturation [may not be] a concern."