Difference between revisions of "User talk:Claribanter"
imported>Claribanter |
imported>Robyn (I don't know.) |
||
(9 intermediate revisions by 2 users not shown) | |||
Line 2: | Line 2: | ||
Thanks Robyn. -[[User:Claribanter|Claribanter]] 23:53, 02 April 2009 (UTC) | Thanks Robyn. -[[User:Claribanter|Claribanter]] 23:53, 02 April 2009 (UTC) | ||
+ | |||
+ | hey, did you solve the problem already? What was the answer? I was curious. -[[User:Robyn|Robyn]] 00:52, 3 April 2009 (UTC) | ||
+ | |||
+ | |||
+ | Yup, crisis averted! Turns out, that a fractional hexadecimal number is different than just a hexadecimal number. The algorithm doesn't just prepend a 0 before the hexadecimal number that is generated by the MD5 hash, that 0 actually changes the number into a fractional hexadecimal number. So it turns a plain old integer hexadecimal number into a hexadecimal fraction and then converts that hexadecimal fraction into a decimal fraction. Since hex is in base 16 and decimal is base 10 fractions work a little differently. -[[User:Claribanter|Claribanter]] 00:04, 03 April 2009 (UTC) | ||
+ | |||
+ | Excellent. I assume you saw [[User:Shmoula|Vaclav's]] implementation? -[[User:Robyn|Robyn]] 01:17, 3 April 2009 (UTC) | ||
+ | |||
+ | I did find Vaclav's implementation today. Is Vaclav's geoANDhash application the same as geohashdroid? http://code.google.com/p/geohashdroid/ If they're not the same, then I guess we'll have three. I really just want to work on adding some features to the standard geohashing application as a project for a class. My team and I might be better off using some of the open source code available and building on that though. -[[User:Claribanter|Claribanter]] 00:34, 03 April 2009 (UTC) | ||
+ | |||
+ | I don't know. You'll have to ask Vaclav. -[[User:Robyn|Robyn]] 01:42, 3 April 2009 (UTC) |
Latest revision as of 01:42, 3 April 2009
I don't know the answer to your question, but recommend you post your Main Page question on Talk:The Algorithm and/or Talk:Implementations to best get the attention of those who can answer it. -Robyn 23:37, 2 April 2009 (UTC)
Thanks Robyn. -Claribanter 23:53, 02 April 2009 (UTC)
hey, did you solve the problem already? What was the answer? I was curious. -Robyn 00:52, 3 April 2009 (UTC)
Yup, crisis averted! Turns out, that a fractional hexadecimal number is different than just a hexadecimal number. The algorithm doesn't just prepend a 0 before the hexadecimal number that is generated by the MD5 hash, that 0 actually changes the number into a fractional hexadecimal number. So it turns a plain old integer hexadecimal number into a hexadecimal fraction and then converts that hexadecimal fraction into a decimal fraction. Since hex is in base 16 and decimal is base 10 fractions work a little differently. -Claribanter 00:04, 03 April 2009 (UTC)
Excellent. I assume you saw Vaclav's implementation? -Robyn 01:17, 3 April 2009 (UTC)
I did find Vaclav's implementation today. Is Vaclav's geoANDhash application the same as geohashdroid? http://code.google.com/p/geohashdroid/ If they're not the same, then I guess we'll have three. I really just want to work on adding some features to the standard geohashing application as a project for a class. My team and I might be better off using some of the open source code available and building on that though. -Claribanter 00:34, 03 April 2009 (UTC)
I don't know. You'll have to ask Vaclav. -Robyn 01:42, 3 April 2009 (UTC)