search

ghelobytes / python-geohash

Automatically exported from code.google.com/p/python-geohash
0 stars 0 forks source link

geohash.bbox returns different results if c library is used #2

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Try the geohash.bbox method on the same geohash with the _geohash c
library present and without

What is the expected output? What do you see instead?

Without _geohash C library:

>>> geohash.bbox('b')
{'e': -135.0, 'n': 90.0, 's': 45.0, 'w': -180.0}

With _geohash C Library:

>>> geohash.bbox('b')
{'e': -180.0, 'n': 90.0, 's': 45.0, 'w': -135.0}

What version of the product are you using? On what operating system?

python-geohash 0.3, python 2.6.1, OS X 10.6

Please provide any additional information below.

It looks like the 'e' and 'w' are just swapped, I believe the attached
patch is the correct fix.

Original issue reported on code.google.com by wsimm...@gmail.com on 6 May 2010 at 4:38

Attachments:

GoogleCodeExporter commented 9 years ago 
Thank you for pointing the issue :)

Original comment by Hiroaki.Kawai@gmail.com on 11 May 2010 at 11:45