Difference between revisions of "User:Aperfectring/Notification"

From Geohashing
imported>Robyn
(This is awesome. I'm sure you can figure out how to have e-mails processed automatically.)
imported>Robyn
(Wow, this is harder than I thought to work out what sector things I want fall in.)
Line 206: Line 206:
 
* Printout from the program - Implemented
 
* Printout from the program - Implemented
 
* A template on the wiki
 
* A template on the wiki
 +
==Requests for future enhancements==
 
* Automatic processing of notification request e-mails so Aperfect ring doesn't have to code them by hand
 
* Automatic processing of notification request e-mails so Aperfect ring doesn't have to code them by hand
 +
* A cool interface (or any interface) to help determine (and submit?) notification requests.

Revision as of 01:10, 26 October 2008

Notification Program

This page is to describe the implementation and testing of the notification program. For discussion, please use the Talk page. Credit goes to Robyn on the original idea.

Current Implementation

The current implementation is based off of the tenths digit of the latitude and longitude for the area(s) notification should be generated for. This is your section ID. Take the tenths digit of the latitude, multiply it by ten, and add the tenths digit of the longitude.

e.g. If your coordinates were 26.026599°, -80.196111° then your "notify me" number would be 01. With 26.324963°, -80.845496° it would be 38.

You can also use this table as a reference. The coordinates for W-30 will all notify the same section ID on the same day, and the coordinates for non-W-30 will notify another (possibly different than W-30) section ID. The table is not intended to be placed on top of a graticule and give a reference for the coordinates. If you have any confusion on how to determine your section IDs, contact me.

Long *.9* *.8* *.7* *.6* *.5* *.4* *.3* *.2* *.1* *.0*
Lat
*.9* 99 98 97 96 95 94 93 92 91 90
*.8* 89 88 87 86 85 84 83 82 81 80
*.7* 79 78 77 76 75 74 73 72 71 70
*.6* 69 68 67 66 65 64 63 62 61 60
*.5* 59 58 57 56 55 54 53 52 51 50
*.4* 49 48 47 46 45 44 43 42 41 40
*.3* 39 38 37 36 35 34 33 32 31 30
*.2* 29 28 27 26 25 24 23 22 21 20
*.1* 19 18 17 16 15 14 13 12 11 10
*.0* 09 08 07 06 05 04 03 02 01 00

Testing Effort

Notifications should go out at about 11 AM US Eastern Time (following US observance of Daylight Savings). This means notification should go out about 1.5 hours after the DOW is available.

Rules for participation

All of these rules are not hard and fast laws, but more of I would really appreciate you to follow them.

  • Notify me (email or IRC) if you see any notification problems. These include:
    • Getting a whole lot more information in your e-mail than what is listed below.
    • Getting a notification when the coordinates don't match your section ID.
    • Not getting a notification when the coordinates do match your section ID.
    • The coordinates in the e-mail do not match the actual coordinates for the day.
  • Make suggestions on improving the system. If there is a quirk of the system which you don't like, let me know!
  • Please don't blame me if the coordinates in the notification send you to a non-official location.

How to join the effort

Send an e-mail to the address specified later in this section with the following information:

  • Latitude of the grat.
  • Longitude of the grat.
  • Section ID (described above)
  • E-mail address
  • Extra notes to include in the notification.

It would be nice, though not necessary, to put it into this format: 26 80 37 youraddress@someplace.com the mall

The e-mail will come back as follows: The 26, 80 graticule is near the mall 26.3791180901449 80.7210165649848

The geohashing notifications e-mail address is those two words with no space @gmail.com.

I have to add all of these entries by hand, so allow for the fact that it may take me a couple days to get your entry in.

Future Enhancements

How to notify people

  • E-Mail - Implemented
  • Printout from the program - Implemented
  • A template on the wiki

Requests for future enhancements

  • Automatic processing of notification request e-mails so Aperfect ring doesn't have to code them by hand
  • A cool interface (or any interface) to help determine (and submit?) notification requests.