geopy was the focus of the second session of C³, which was held on November 16, 2008, and is scheduled for the third session, to be held on December 14, 2008. Code, documentation, and a bug tracking tool can be found on the Google Code project page for geopy.
Plan of action
We will be working on geopy at the upcoming third session of C³, which will be held on Sunday, December 14, 2008 at 1PM in the meeting room of Gypsy Beans, located at the corner of West 65th and Detroit Avenue. Also, note that we hang out in #C3 on irc.freenode.net; even if you can't make it to the meeting in person, you are welcome to hack with us remotely.
See the description of geopy, from our first session, for a brief introduction.
Things to work on
- Unit tests
- Reverse geocoding (finding locations near a point)
- Higher level Points and Locations instead of tuples and strings
- Update interfaces to third-party geocoders
- Merge pending patches (bug fixes, Python 2.3 support, accuracy support)
- Parsing and generation of various location encodings:
Geohash encoding/decoding (including xkcd geohashing)
November 16, 2008 session
About geopy
geopy "is a geocoding toolbox for Python." geopy allows you to query public map services for locations and obtain latitude and longitude coordinates for those locations. It also provides functionality for calculating the distance between geographical locations.
geopy has been used for many location-aware applications, including directing mobile robots at Carnegie Mellon, calculating stream lengths for the U.S. Geological Survey, and updating addresses for the Barack Obama presidential campaign.
Results
Brian, Adam, Gary, and John showed up in person, and sgillies showed up on IRC. Brian suggested things to work on, and put some work into the "November Sprint" page to map out some of those ideas. Adam fixed issue 4, and a couple Vincenty distance functions, and then moved to getting familiar with using Nose for testing. Gary dove into the tests, where he taught John and Adam how to use Nose and spent most of his time creating tests (but not unit tests) for the distance functionality. John worked on a combination of design, testing, and implementation of some initial functionality in the GPX parser. After his coordination work, Brian continued his work on the geocoding functionality. I think it's fair to say that we had a lot of fun.