Category:Not reached - Time constraints

From Geohashing
Revision as of 20:45, 31 March 2009 by imported>Relet (New page: In this category the geohasher would have arrived at the coordinates, and really really wanted to, but had to turn back because of, you guessed it, time constraints. That could be time bef...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

In this category the geohasher would have arrived at the coordinates, and really really wanted to, but had to turn back because of, you guessed it, time constraints. That could be time before midnight, time before curfew or time before their prearranged search and rescue activation. It could also just be all the time the geohashers concerned were willing to spend on the expedition.

If the expedition took far longer than planned because of headwinds or transportation problems, consider Category: Not reached - Mother Nature or Category: Not reached - Technology, respectively. If the geohashers eventually reached the coordinates, but on the wrong day, class the expedition as Category: Failed - Incorrect date.

If any geohasher reaches the coordinates on the correct day then the expedition should be classed instead as Category:Coordinates reached. Class it here only if no one reaches the coordinates.

If the expedition was cancelled because of time constraints, it instead counts as Category:Expedition Planning and receives no Expedition Outcome category.

This category was created to replace Category:Failed - Time Constraints to remove the stigma of failure from someone following the rules of geohashing.

Pages in category "Not reached - Time constraints"

The following 166 pages are in this category, out of 166 total.

2