Skip to content

Instantly share code, notes, and snippets.

@arsatiki
Created October 23, 2009 08:26
Show Gist options
  • Save arsatiki/216747 to your computer and use it in GitHub Desktop.
Save arsatiki/216747 to your computer and use it in GitHub Desktop.
From be4b3a6b8c59c0a5ca291d40a187f970ccc4084d Mon Sep 17 00:00:00 2001
From: Antti Rasinen <[email protected]>
Date: Fri, 23 Oct 2009 08:21:30 +0000
Subject: [PATCH] Fixed latitude/longitude parsing.
"I assume that you worked out that whole
longitude-latitude thing. I know you get confused
sometimes."
"You're right, you're right. I keep mixing them
up... I got it right. Well, I *think* I got it
right. Okay, fine. Which goes vertically,
longitude or latitude?"
- Franklin and Garibaldi: Babylon 5, "Endgame"
git-svn-id: http://code.dev.muxlim.com/django-contrib/branches/dev@17910 175ec6be-eeff-4b60-847c-a1dcdc42cbf2
---
muxlim/util/geo.py | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/muxlim/util/geo.py b/muxlim/util/geo.py
index d63acb7..26f6908 100644
--- a/muxlim/util/geo.py
+++ b/muxlim/util/geo.py
@@ -99,7 +99,7 @@ def parse_place(placetree, q):
name = placetree.find(q.name).text
centroid = placetree.find(q.centroid)
lat = find_float(centroid, q.latitude)
- lon = find_float(centroid, q.latitude)
+ lon = find_float(centroid, q.longitude)
return Place(woeid, typ, name, lat, lon)
--
1.6.5.1+GitX
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment