Difference between revisions of "Talk:Multiple elevations achievement"
imported>Mystrsyko |
imported>Gefrierbrand |
||
| Line 1: | Line 1: | ||
I support this, mostly because I'm a pilot and I could hope to some day pull of the simultaneous air and land geohashes (with the help of a friend, of course). [[User:Neimster| Neimster : 33, -97 ]] ([[User talk:Neimster|talk]]) 17:03, 3 June 2013 (EDT) | I support this, mostly because I'm a pilot and I could hope to some day pull of the simultaneous air and land geohashes (with the help of a friend, of course). [[User:Neimster| Neimster : 33, -97 ]] ([[User talk:Neimster|talk]]) 17:03, 3 June 2013 (EDT) | ||
| − | + | :'''support''' trying to get some life in here --[[User:Gefrierbrand|Gefrierbrand]] ([[User talk:Gefrierbrand|talk]]) 22:16, 29 June 2015 (EDT) | |
Perhaps some clarification is needed in the section on positioning geohashers for the team stack? I know it was just pasted over from the [[Stacking achievement]] page, but as I read it now it sounds like it requires that all parties involved be directly over the top of each other. In the case of a multistory building or a bridge, how could hashers be expected to position themselves with such precision? I understand that in the cliff example it would be impossible for one person to be directly over another, but I don't think it's fair to invalidate such a situation and yet allow others to roam within their GPS margin of error. I don't really see the need to nit pick like that when in every other hashing situation the margin of error is accepted as "good enough". [[User:Mystrsyko|Mystrsyko]] ([[User talk:Mystrsyko|talk]]) 13:09, 17 September 2013 (EDT) | Perhaps some clarification is needed in the section on positioning geohashers for the team stack? I know it was just pasted over from the [[Stacking achievement]] page, but as I read it now it sounds like it requires that all parties involved be directly over the top of each other. In the case of a multistory building or a bridge, how could hashers be expected to position themselves with such precision? I understand that in the cliff example it would be impossible for one person to be directly over another, but I don't think it's fair to invalidate such a situation and yet allow others to roam within their GPS margin of error. I don't really see the need to nit pick like that when in every other hashing situation the margin of error is accepted as "good enough". [[User:Mystrsyko|Mystrsyko]] ([[User talk:Mystrsyko|talk]]) 13:09, 17 September 2013 (EDT) | ||
Revision as of 02:16, 30 June 2015
I support this, mostly because I'm a pilot and I could hope to some day pull of the simultaneous air and land geohashes (with the help of a friend, of course). Neimster : 33, -97 (talk) 17:03, 3 June 2013 (EDT)
- support trying to get some life in here --Gefrierbrand (talk) 22:16, 29 June 2015 (EDT)
Perhaps some clarification is needed in the section on positioning geohashers for the team stack? I know it was just pasted over from the Stacking achievement page, but as I read it now it sounds like it requires that all parties involved be directly over the top of each other. In the case of a multistory building or a bridge, how could hashers be expected to position themselves with such precision? I understand that in the cliff example it would be impossible for one person to be directly over another, but I don't think it's fair to invalidate such a situation and yet allow others to roam within their GPS margin of error. I don't really see the need to nit pick like that when in every other hashing situation the margin of error is accepted as "good enough". Mystrsyko (talk) 13:09, 17 September 2013 (EDT)
