Re: Coordinate proximity challenge question

I started another thread here that was marked "cancelled" so I'm asking my tangent question here... I hope that's alright (sorry, I'm new here).

Link to old thread: http://project-gc.com/forum/read?8,1681

In that thread I was given a link to an old thread: http://project-gc.com/forum/read?8,1104,1104#msg-1104
In that thread TravelingGeek says:

"Well, the state of Washington is easy.

Defining the cemeteries is not so easy. Since we can't look for the word "Cemetery" in cache name any more.

IF (and it's a really big IF) you could identify the center point coordinate of ALL cemeteries (is there a master list?) and define the radius (say .2 miles). For bigger cemeteries, you could use multiple center points to cover or actually draw or otherwise find the polygon data.

Anyway you luck at it, there is a lot of data gathering you would have to do to make it possible to write a checker or script."

I have before me a list of all of the cemeteries in my county. If I calculated the center point to every one of them, could code be written that would find every cache within .10 of those coordinates? And if so would that challenge be publishable then?

Basic info:
Cache name: Cemetery Challenge: AG
Cache #: GC6M6TE
Goal: Find 10 caches located within a cemetery.

Thanks for your time!

If you have that information a checker can be created
The config has to be in the format below validate the json at http://jsonlint.com/
notice that there i not a , on the last point definition
{
"polygons":{
"01. Sandstone Peak (Mount Allen)":{"point":[34.1203,-118.9319,0.2,"miles"]},
"02. Tri Peaks":{"point":[34.122179,-118.950192,0.3,"miles"]},
"03. Boney Peak":{"point":[34.11072,-118.9577,0.2,"miles"]}
}}

But you might have a problem with
Guideline 4

Quote

must be verifiable through information on Geocaching.com.

Guideline 5
quote]The challenge requirements should be simple, and easy to explain, follow and document. A long list of rules or restrictions may prevent publication.[/quote]
I would read that as that the coordinates of the cemeteries has to be available on gc.com but that would be a to long list if there are many cemeteries.
I would ask a reviewer before stating to create a config

I agree that this should be referred to a reviewer however personally I wouldn't say that it violates guidelines 4 or 5.

The requirement is simple to explain "It must be within .1 miles of the centre of a cemetery located in washington." (probably with a further few sentences saying the centre point is wherever google plots the location when you put in the cemetery name in.

The information is actually verifiable on geocaching.com as at least openstreetmap and map quest both show cemeteries deliminated on the map.

I'd probably make sure your cache page links to the master list of cemeteries and state that is what you are using as your definitive source, but whilst the list of locations may be long the list of rules are short and simple to follow and explain.

However as said at the beginning ultimately it is up to your local reviewer to decide how they interpret the rules.

Look at this one http://project-gc.com/Challenges/GC22B68/19568 and you can have a pretty good idea what can be done

Challenges based on user-defined mapping polygons. (new 2016) are from the 2016/06/24 not acceptable.

Because of no futher feetback I am archieving this thread in "ARCHIVE Checker requests (impossible)"