Difference between revisions of "New York, New York"
imported>KDinCT (graticule-ized) |
imported>KDinCT |
||
| Line 4: | Line 4: | ||
|n = Danbury, Connecticut | |n = Danbury, Connecticut | ||
|ne = Hartford, Connecticut | |ne = Hartford, Connecticut | ||
| − | |w = Newark, | + | |w = Newark, New Jersey |
|e = | |e = | ||
| − | |sw = Atlantic City, | + | |sw = Atlantic City, New Jersey |
|s = | |s = | ||
|se = | |se = | ||
Revision as of 02:18, 22 May 2008
| – | Danbury, Connecticut | Hartford, Connecticut |
| Newark, New Jersey | New York, New York | – |
| Atlantic City, New Jersey | – | – |
[[Category:Meetup in {{{lat}}} {{{lon}}}| ]]
The New York City graticule is at latitude 40, longitude -73. It includes most of New York City (minus the West Village & Chelsea and downtown Manhattan -- who needs 'em? -- and extreme western Brooklyn) and a whole hell of a lot of Long Island. (If only over half of our graticule wasn't over water)
Today's Location: [New York, NY]
Activities
Oleo will try to get to the coordinates, but doesn't have a car.
There is a facebook group for New York, NY geohashers. http://www.facebook.com/group.php?gid=19859510038
Notable Events
Local Geohashers
Issues
This seems to be one instance where the incredibly cool XKCD geohashing scheme fails. Many New Yorkers located in the city do not have cars due to the availability of public transportation and the lack of space to park said car. This means that traveling to 90% of the locations in the graticule isn't feasible. There are plenty of people and places to explore within the city though. Would recommend a second version of the algorithm that takes population density into account and uses a few more decimals as a baseline if that is the case.
