User talk:CaptainSpam

From Geo Hashing
Jump to: navigation, search

Yay, a new wiki person. Go forth and geohash! P.S. It's bad wiki manners to upload a photograph to the main page before you have finished your expedition report. We forgive you this time because you're new, but please write one up, here. -Robyn 01:41, 8 May 2009 (UTC)

Ah, sorry, my mistake. Said writeup is en route as we type (and as soon as I get the other pictures edited and uploaded). CaptainSpam 01:55, 8 May 2009 (UTC)
Awesome. Occasionally people upload pictures and just disappear. Also the main page updates at intervals, so if someone links a picture and then does the report, the link on the main page can remain bad for a few hours. Plus why put a picture on the main page if there is nothing for people to find out about when they click on it. I'm glad you're sticking around. Lots of new people on the wiki lately. How dod you find out about geohashing? -Robyn 01:59, 8 May 2009 (UTC)
The usual way, really. Reading xkcd. :-) And then writing a Geohashing Android app, which I finally got the chance to give a full test to today. Nice to be here! -CaptainSpam 02:04, 8 May 2009 (UTC)
There we go! One writeup posted, complete with pictures! I noticed too late that the pictures were supposed to be categorized, too; thanks for catching that. -CaptainSpam 02:23, 8 May 2009 (UTC)

[edit] Praise for the geohashdroid.

Woo! Yay! Houpla! Excellent tool. I love it.

Some suggestions for the roadmap (no matter how far away):
  • Google maps routing from source to geohash (for that approach)
  • Automatic saving of tracklogs
  • EXIF tagged photos (actually I would assume they are already?)
  • Automatically appending short messages to the wiki
  • Automatically uploading photos and inserting them to the gallery.

Hey, I might even help coding once I find my way with the android. -- relet 12:28, 5 August 2009 (UTC)

  • I can't quite do map routing, I'm afraid. Part of the developer agreement forbids me from using Google Maps to plot a route like that. Probably something to do with the deal Google has with whoever gives them their street information, I'd guess.
I guess it's time for a decent OpenStreetMap/PyRoute port or something. :D -- relet 14:26, 5 August 2009 (UTC)
  • A tracklog? Like, remembering the path you took to a given hash point? Hm. That might be an interesting idea, and perhaps not too difficult (later on), now that I have the database calls in place...
Yup. Like the ones that are being posted to the wiki all the time. ;) GPX or KML format or something along these semi-standard lines. -- relet 14:26, 5 August 2009 (UTC)
  • The entire picture-taking stuff is next on my list, actually, right after "Quick change to a nearby graticule" and "Automatically pick whatever graticule has the closest point". So, yep, eventually there'll be EXIF-tagged photos! And hopefully I'll have it upload to the wiki directly from the phone!
Woo! -- relet 14:26, 5 August 2009 (UTC)
  • Appending short messages to the wiki is also in the pipeline, though that'll probably come after picture-taking and other stuff.
More woo! -- relet 14:26, 5 August 2009 (UTC)

But, thanks! Glad you're liking it! :-) CaptainSpam 14:03, 5 August 2009 (UTC)


I was wondering if I could nudge you to include a quick INSTALL readme in the source tree, or in the wiki. Would I have to create a new android sdk project before checking out your source, or did you just not check in some files required for building the app? TIA, -- relet 14:22, 10 August 2009 (UTC)

Ah, yeah, the project part... I probably should include a readme for working with the source, or maybe just include the Eclipse project files. I was intending to keep anything Eclipse-specific out of the source tree for people who don't use it, but then again, since Eclipse IS the more or less de facto way to code Android, it makes a bit of sense to include such things...
But yes, as it stands now, you'd have to create a new Android SDK project to check out the code. It shouldn't take too much beyond that to get it to compile under Eclipse with the Android ADT plugin. For the time being, I still use the 1.1 SDK (until I get to the widget idea someone gave me or do something else that needs 1.5, it'll probably stay there for now... not to mention I use one method in the map interface that's deprecated in 1.5 which I still need to rewrite).
You ARE the first person to check out my code (or, at least the first person who actually told me), so it might be a bit rough at first. Oh, and incidentally, as of right now, the most recent SVN code won't work right, as I'm halfway into refactoring the stock price grabbing routine significantly, so don't count on a quick compile-and-run just yet. :-) CaptainSpam 15:22, 10 August 2009 (UTC)
Actually, I was hoping not to use that bulky eclipse thingy anyway. As I am not yet too familiar with the SDK, I was just wondering if I would need any information to set up the project correctly. I guess I can gather the correct package name from the source, and make up the rest. Did you tag the latest release version in svn? I might just start playing with that one. Well, I'll tell you how I fare. :D Are there any other means to contact you? -- relet 20:05, 10 August 2009 (UTC)
Hm... offhand, I'm not sure what other information you'd need, if any. But, I'm also not too familiar with not using the Eclipse plugin to do the job, so it may take some twiddling. The plugin is quite astoundingly convenient, really, but that could mostly be because I like Eclipse in general. You may disagree. :-)
Each release is tagged in the SVN tree. I think they're in tags/release-X.Y.Z. And if you need some other means to contact me, you can use the email address I should have listed in the market with GeohashDroid, or the Google Group I've got set up.
Enjoy! CaptainSpam 22:16, 10 August 2009 (UTC)