Difference between revisions of "User:Pinecone"
imported>Pinecone (→Decicules and Driving Directions) |
imported>Pinecone (→Decicules and Driving Directions) |
||
| Line 31: | Line 31: | ||
=== Decicules and Driving Directions === | === Decicules and Driving Directions === | ||
| − | # Divide each graticule into tenths called <b> | + | # Divide each graticule into tenths called <b>decicules</b>. For example, if I live in graticule (42,-71) then some decicules near me are |
{| cellpadding="0" cellspacing="0" | {| cellpadding="0" cellspacing="0" | ||
| ||(42.0,-71.0) ||(42.0,-71.1) ||(42.0,-71.2) ||... | | ||(42.0,-71.0) ||(42.0,-71.1) ||(42.0,-71.2) ||... | ||
| Line 41: | Line 41: | ||
| || etc. | | || etc. | ||
|} | |} | ||
| − | # Pick the urban center you are closest to. | + | # Pick the urban center you are closest to. The day's hash for your graticule will define four <b>decihashes</b> surrounding that location. For example, if I am near Boston, and the graticule hash is (42.1234,-71.5678) then the decihashes around me are |
{| cellpadding="0" cellspacing="0" | {| cellpadding="0" cellspacing="0" | ||
| ||(42.4234,-71.1678) || ||(42.4234,-71.0678) | | ||(42.4234,-71.1678) || ||(42.4234,-71.0678) | ||
| Line 49: | Line 49: | ||
|| || (42.3234,-71.1678)|| ||(42.3234,-71.0678) | || || (42.3234,-71.1678)|| ||(42.3234,-71.0678) | ||
|} | |} | ||
| − | # Use Google Directions to find which of these decihashes | + | # Use Google Directions to find which of these decihashes has the shortest driving distance from "Boston". |
# The end point for that set of Google Directions is today's "Boston decicule hash". | # The end point for that set of Google Directions is today's "Boston decicule hash". | ||
Revision as of 04:58, 9 June 2008
Pinecone is a Boston based conifer.
An Immodest Proposal
The issue:
A typical hash is about 25 miles away from you. Ramifications of this:
- An long drive each way for those with car.
- Somewhat more problematic for those without.
- On the social front, you meet a lot of nice people but they live far away from you.
- Nobody is ever going to get the damn Couch Potato ribbon.
- You usually get sent to less populated areas:
- Ironic to burn a lot of oil to go see greenery.
- You don't often get to play with cities.
- In populated graticules you have to find a park to hang out in. This is nice for frisbee but less handy for table games.
- In unpopulated graticules most expeditions are less social club and more hiking trip.
- It's a bigger problem for everyone in the winter.
Reasons I might like something nearer at hand:
- Lacking transport
- Want a local group to socialize with
- Want to play with cities
- The regular hash is someplace god-awful
- I am feeling lazy
Obviously we could just divide up the graticules into smaller pieces, but this would scatter the children of XKCD far and wide. I present a solution here that I think can solve these issues.
Decicules and Driving Directions
- Divide each graticule into tenths called decicules. For example, if I live in graticule (42,-71) then some decicules near me are
| (42.0,-71.0) | (42.0,-71.1) | (42.0,-71.2) | ... | |
| (42.1,-71.0) | (42.1,-71.1) | (42.1,-71.2) | ... | |
| (42.2,-71.0) | (42.2,-71.1) | (42.2,-71.2) | ... | |
| etc. |
- Pick the urban center you are closest to. The day's hash for your graticule will define four decihashes surrounding that location. For example, if I am near Boston, and the graticule hash is (42.1234,-71.5678) then the decihashes around me are
| (42.4234,-71.1678) | (42.4234,-71.0678) | ||
| Boston | |||
| (42.3234,-71.1678) | (42.3234,-71.0678) |
- Use Google Directions to find which of these decihashes has the shortest driving distance from "Boston".
- The end point for that set of Google Directions is today's "Boston decicule hash".
This will generally result in a location within 6 miles of the city center. It doesn't matter where Google Maps thinks "Boston" is, or that you won't be driving the route it finds. What matters is that it's consistent for everyone who checks it.
This system is intended to solve one additional problem. When a hash is inaccessible, there can be confusion about where people should meet up. When you give Google Directions an inaccessible destination, it gets as close as it can using public roads. That endpoint will be unique and accessible.
An Example
| On 5-24-08 the (42,-71) meet up was at 42.126648,-71.547534: | Meanwhile, back in Boston: |
So in this case, those who are able go to the graticule hash in Hopedale, MA while those more local could meet up at 695 William J Day Blvd, Boston which is where the driving directions for the winning decicule finish. Best to mention who has what plans on the graticule board ahead of time.
In a graticule with high population there might be several active decicules. Around here one would expect Boston, Worcester, and Nashua to have their own contingent. These locations being overridden if the graticule hash itself was nearby.
A little complicated but an implementation will help and you only need this for urban areas were population density makes submeet ups feasible.
Notes
Naming conventions: boston grat, bost dec
You can use any location. the boston decicule will sometimes go to then same location as a Brookline decicule, sometimes not. only if a lot of people.
The decicule location can be used as a fallback for everyone if the graticule location is going to suck. if the decicule location is also going to suck, you can pick the one with 2nd shortest driving distance, etc. You would name the decicule locations Boston1, Boston2, Boston3, etc. "Today's graticule hash is in the middle of a swamp but Boston3 is in the hardware department at Sears. Let's go there!"
During weekdays i'm certainly not be able to road trip, but it would be great to meet people at Boston1 at, say, 8pm.
All this is not meant to detract from the pre-eminance of the mighty graticule
Pick up more people who generally don't go on road trips for any of the above reasons.
Issues
Boundary problem: Do you use a neighboring graticule to get the closest decicule?
The "dangerous areas" problem.
