New Mexico

From Geohashing
Revision as of 09:10, 19 March 2022 by Arlo (talk | contribs) (add greeting for non-geohashers I link here)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Have you seen our geohashing marker? We'd love to hear from you! Click here to say "hi" and tell us what you've seen!

Curious about what geohashing is? Read more!

This is a map of all graticules containing parts of New Mexico, U.S.A. (see also: Mexico, Arizona, Utah, Colorado, Oklahoma, and Texas)

Graticules that have not been hashed or only unsuccessfully hashed (or successfully hashed but not reported on the wiki) are orange, whereas the graticule rectangles shaded other colours list the usernames of the first geohashers to achieve a successful documented expedition, and a link to said expedition writeup on the wiki (light green is for expeditions within the borders of New Mexico, light blue for expeditions that fell in the non-New Mexico portion of a border-containing graticule).

N\W 109 108 107 106 105 104 103
36 Chinle, Arizona Farmington
Redaragorn #
Bloomfield
Redaragorn #
Chama
Redaragorn #
Taos
Redaragorn #
Raton Clayton
35 Window Rock,
Arizona
Gallup
Redaragorn #
Grants
Redaragorn #
Albuquerque
Bishop Wash #
Santa Fe
David & Gina #
Conchas Lake Tucumcari
34 Eagar, Arizona Quemado
Redaragorn #
Magdalena
Redaragorn #
Los Lunas
Bishop Wash #
Vaughn
Redaragorn #
Santa Rosa Clovis
33 Whiteriver,
Arizona
Reserve Truth or
Consequences

Redaragorn #
Tularosa
Redaragorn #
Ruidoso Roswell Tatum
32 Safford, Arizona Silver City Deming
GPSMen #
Las Cruces
Fugads & Kids #
Alamogordo Carlsbad Hobbs
31 Douglas,
Arizona

AuricTech? #
Antelope Wells Columbus El Paso, Texas
Updraft58 & GPSmen #

names

discuss whether the following graticules should keep their old name, or adopt the suggested new name or a different one at geohashing:Community Portal/Renaming suggestions#30s

globalhashes

There have been at least 6 globalhashes landing in the borders of New Mexico from 1950 to March 2022, only some of which are likely available for retrohashing via ambassador means:

derivation and statistics notes

The above is according to the Geohashing Shotgun app (search URL http://geohashing-shotgun.appspot.com/showmap?radsearch=1&globhash=1&YLh=.01&YHh=.21&XLh=.10&XHh=.35&radlimit=500000&centrey=34&centrex=-106&yearmask=****&monthmask=**&daymask=**&startdate=1950-01-01&enddate=&View=View for which a guide exists at the homepage to explain the various URL parameters) which uses Dow data but has a bug that makes some of these invalid -- see following list.

  • 1975-01-28 global shown to be near US 84 between Santa Rosa and Lake Sumner, but actually in the sea far west of Australia
  • 1976-07-14 global shown to be near Fairview peak on the White Sands missile range, but actually near Gardner Pinnacles, Hawaiʻi
  • 1978-01-16 global shown to be near Canjilon in the Carson National Forest, but actually north of Greenland
  • 1980-02-12 global shown to be outside Acoma near the Malpais, but actually between Spitsbergen and mainland Norway
  • 1980-09-12 global shown to be near US 550 between Nageezi and Huerfano, but actually north of Antarctica
  • 2005-05-02 global shown to be near where Sawmill Creek joins the eastern fork of the Red River on the back side of the Wheeler Peak from the Taos Ski area, but actually in the sea east of Madagascar.
  • 2010-12-05 global shown to be near Techado, but actually (again) in the sea far west of Australia

The expected value of how many geohashes we would expect in New Mexico for that date range can be calculated thusly: since there is a little greater than 1 in 3 chance (~.395 specifically) that a graticule would host the globalhash on any of the days during the specified period (around 25600 days' duration), there are ~25600 chances for a graticule to host the globalhash divided by the 64800 graticules worldwide that 'compete' each day to host the globalhash, and around 33 hashes worth of area that the state occupies (although as you see, due to the borders not being exactly snapped to graticule boundaries, that is shared between 39 graticules). This matches around twice the observed number of hashes, within a margin of error.