User talk:Crox

birthday greeting

Happy Birthday? Juventas 00:28, 11 April 2010 (UTC)

it was a few days ago, but thanks! --Crox 21:42, 11 April 2010 (UTC)

hashcard

Thanks for the Hashcard of 2010-07-13 45,7- looks like a beautiful place! MagicIan 19/07/10 21:38 (GMT)

You are welcome. I hope you were able to decypher my script, I wrote it on the train down to Zermatt, which proved to be a challenge :o) --Crox 21:00, 20 July 2010 (UTC)

todo

to check: Public_transport_probability

30W Time Zone Rule#Testing for 30W compliance

edit this page link:

 [{{fullurl:{{FULLPAGENAME}}|action=edit&section=1}} edit]

expedition talk page follow-ups

RE: 2013-05-04 47 9 : Thanks, I was looking every now and then for a reachable geohash in Liechtenstein and this time I couldn't resist. --TheOneRing 07:37, 05 May 2013 (UTC)
RE: 2013-05-27 46 7 : The opportunity might be very good (even the weather would be in favour) but I'm afraid I will not come out of the office in time for an attempt. --TheOneRing 06:51, 27 May 2013 (UTC)

Source error

Hi Crox. I've been building a small database of Dow openings. While checking the values I found that some of your Dow holidays are filled in with the closing value of the previous day. E.g. 2008-11-27, 2008-12-25, and several more following those. While I'm at it, how much discrepancy do you see on 2008-07-03? That's the only difference from Peeron/Google (back to the invention of the geohash) after fixing the more obvious stuff. Edit: Happy birthday, maybe, seeing the above. :-) --62.163.112.228 17:43, 5 April 2011 (EDT)

Hello 62.163.112.228, thanks for taking the time to report this and also for the birthday wishes :o)

For 2008-07-03, I've stored the following opening values:

 11215.9967544 from djindexes.com
 11216.00 from SunGard
 11216.00 from google.com/finance

If I remember correctly, Yahoo had a different value for that day, and I removed it manually. If you have a list of the other fixes you've done, or all historical Dow holidays, I'd be happy to have it. --Crox 16:30, 6 April 2011 (EDT)

Maybe I shouldn't have used the word database. It's more of a list of a few hundred Dow days, in an attempt to have a more accurate list than Yahoo's CSV (plotting nearby hashes to look for interesting ones is no fun when many are wrong). It currently runs from 2008-05-21 until now. I didn't keep the original data, but I think it only differs from your data on holidays, and definitely only from Peeron on 2008-07-03. You could diff against Peeron and see if it's all on holidays. I think checking for absent days in Yahoo's CSV also works.

Hmm, now that I look at my list, I think my first day — 2008-05-21, when the comic was posted — actually has the highest value. I guess geohashing is bad for the economy. --62.163.112.228 10:13, 7 April 2011 (EDT)

historical Dow data?

I'm interested in doing some serious retrohashing number crunching, and would like to get copies of your historical Dow opening data. Is this feasible? JesseW 02:02, 23 May 2012 (EDT)

Ping... I totally understand if you are busy, but I'd love to get my hands on that data... JesseW 21:22, 10 July 2012 (EDT)

hi, haven't forgotten :o) hopefully I can get back to you in the next few days... --Crox 16:22, 19 July 2012 (EDT)

No worries. Thanks for the reply! JesseW 01:22, 2 August 2012 (EDT)

JesseW, are you doing something similar to User talk:AeroIllini/GeoHistory ? I'm also interested in historical tracking, but for 47,-122 in my case. --Thomcat 18:05, 15 October 2012 (EDT)

2013-12-03 47 11

Thanks for the hashcard ribbon, crox :D It was earned with a stubborn cold from which EleanorAbernathy and me are recovering these days... --LeslieHapablap (talk) 12:18, 8 December 2013 (EST)

2012-09-15 46 6

Can you confirm whether or not this expedition was attempted? It looks like expedition planning but that's all. -- Jevanyn (talk) 12:11, 19 December 2013 (EST)

Hello, as you can tell from this edit, it was attempted and reached. This is one of the reports that I still need to complete (mardked with an asterisk on my user page). I will get to do it, eventually... --Crox (talk) 19:22, 21 December 2013 (EST)

DJIA source for the wiki

Since the Peeron DJ source is unreliable and has now left parts of the wiki non-functional again, it would seem much more sensible to change the DJ source for the wiki to your servers. Do you think they could manage the load? Or is there another reason why this hasn't been done already? --Calamus 12:22, 6 March 2015 (EST)

And/or possibly even APB, which of course does a lot of requests too? --Calamus 12:34, 6 March 2015 (EST)

Hello, I'm not worried about the load, but maybe this needs to be part of a wider discussion about making the wiki more robust? --Crox (talk) 16:21, 20 April 2015 (EDT)

KML Tool

Thanks for your reply on the DJIA page. Also the link to Marble was interesting and useful. --Sourcerer (talk) 04:41, 28 January 2016 (EST)

Globalhash Alert

On Monday, 2016-04-18 global there's a globalhash at 46.917574, 5.554271 in the graticule next to your's. It's 18 km from 2016-04-18 46 5. --Sourcerer (talk) 14:35, 15 April 2016 (UTC)

Thank you very much for the notice! Unfortunately, I estimate an expedition would take me about 5 hours, which I don't have today. --Crox (talk) 08:15, 18 April 2016 (UTC)

You have another close globalhash tomorrow: 2019-08-28 global at 45.60854,6.93040 --Fippe (talk) 13:38, 27 August 2019 (UTC)

Thank you for the alert! From what I can see ([1] and [2]) it should even be relatively reachable. Unfortunately it currently looks unlikely that I can free up the required time tomorrow to get there... --Crox (talk) 14:09, 27 August 2019 (UTC)

Changing the algorithm

There is a discussion about changing the algorithm. I'd like you to be involved because you are a developer.

SMS tool

Hi Crox, it seems that your SMS tool doesn't work any more, I didn't get a response message when I tried it earlier today. In a few hours I'll be off to visit a not-so-free country where I don't know if they have accessible/uncensored internet so I wanted to use your service as a backup. - Danatar (talk) 21:39, 3 October 2017 (UTC)

Hello, sorry for that. Unfortunately either the SIM or the modem have an issue, so it's not going to be an easy fix. I'll check again this week-end and post an update afterwards. --Crox (talk) 20:31, 12 October 2017 (UTC)

It's been a bit longer than I expected (and wished). I have to replace the modem, which will take me another couple of weeks unfortunately... --Crox (talk) 00:35, 3 January 2018 (UTC)

poster fractions

Looking at http://geo.crox.net/poster/2020-02-09_global, the fractions don't seem to match the final one. Although including the proper md5 is a nice touch. Arlo (talk) 16:00, 7 February 2020 (UTC)

Could you be more specific as to what you think is incorrect? I've tested the poster generation tool against some of the test cases here, and as far as I can tell there should be no calculation errors. From your example, looking at it "manually" the figures appear correct too. c0 is approximately 3/4 of ff, or 0.75, and 45° N is about 3/4 from South pole to North pole. As for longitude, 48 hex is 72 dec, 72/255 = 0.28. And (0.28 * 360) - 180 is -79.2, which again roughly matches the calculated values. --Crox (talk) 21:21, 7 February 2020 (UTC)

I had a major brain fart and was for some reason thinking a meridian or parallel encompassed 100 degrees rather than 360 or 180...(slaps forehead) so yeah, seems all good now. Arlo (talk) 00:33, 8 February 2020 (UTC)

Okay, this time a real bug: "United States of Aerica" (as much as I love the http://aericanempire.com...): http://geo.crox.net/poster/2020-02-12_35_-105 Arlo (talk) 20:33, 12 February 2020 (UTC)

Hmm, can't reproduce this. The location info ("reverse geocoding") is currently not cached (although this has been on the to-do list for a while) - I guess it was a mistake on the OSM side, which has been fixed in the meanwhile. --Crox (talk) 21:19, 18 February 2020 (UTC)

How soon should I check geo.crox.net?

Hi Crox! I'm building an iPhone app to calculate cashpoints, and I'd like to use geo.crox.net for the DJ source. Just wanted to check that you're OK with that?

And if so, what time should I check it? I'm guessing it takes a few seconds (or minutes?) after 9.30am, so if I start checking at *exactly* 9.30am then I'm guessing that's a bit too early?

Roughly how long would you suggest I wait?

Thanks! BrendanTWhite (talk) 03:50, 20 February 2024 (UTC)

Hi BrendanTWhite,

I've checked the logs for 2023 and 2024, from what I can see, most days there is a DJIA available by 09:30:15 NYC time, so that's probably a good time for a first check. After that I suggest implementing a reasonable delay between retries, and caching of positive results.

Also, if your app is using a specific user-agent for its requests, this will help in identifying potential issues (but we hope this won't be necessary of course!).

Best regards, --Crox (talk) 22:23, 20 February 2024 (UTC)

Thanks Crox, that's good to know. I won't send any requests before 9:30:15am (NYC).

And yes, I'll definitely give gaps between retries. I was thinking 30 seconds for the first gap, and double each time (so 1 min gap the second time, then 2 min then 4 min etc). Does that sound reasonable?

Of course I'm hoping the app will be wildly successful and will cause a massive resurgence in geohashing! :-) But if I'm honest it probably won't have more than a handful of users, at least to begin with. So hopefully I won't cause you any issues ... but if there are any problems, do please let me know.

I'm not sure exactly what user-agent an iPhone app uses, but I'll see if I can work out how to make it as specific as I can.

And yes, I'll definitely cache positive results so it doesn't need to request it again.

Thanks! - BrendanTWhite (talk) 00:26, 21 February 2024 (UTC)