Comments for Ex Nihilo

Comment on CPU Usage in Processing by Dave

Dave — Sun, 20 Dec 2009 01:59:25 +0000

That actually seems a more elegant way of doing it, yeah. Wasn’t aware of the noLoop() function, thanks!

Comment on CPU Usage in Processing by J David Eisenberg

J David Eisenberg — Sat, 19 Dec 2009 07:16:58 +0000

I’m no Processing expert, but would noLoop() help here?

Comment on Elevation by Rubbishcorp ® .::. Elevation | 3D Spacial GPS Rendering :

Rubbishcorp ® .::. Elevation | 3D Spacial GPS Rendering : — Fri, 16 Oct 2009 05:41:04 +0000

[...] Here. [...]

Comment on Elevation by New Project: Elevation › Ex Nihilo

New Project: Elevation › Ex Nihilo — Mon, 12 Oct 2009 20:35:47 +0000

[...] cleaned up my 3D elevation code and released it as a project, source and all. Go check out Elevation to grab Mac and Windows executables, or hit up GitHub to grab the [...]

Comment on Manual Geodata by New Project: Elevation › Ex Nihilo

New Project: Elevation › Ex Nihilo — Mon, 12 Oct 2009 20:34:48 +0000

[...] « Manual Geodata [...]

Comment on Elevation by Tweets that mention Elevation › Ex Nihilo -- Topsy.com

Tweets that mention Elevation › Ex Nihilo -- Topsy.com — Mon, 12 Oct 2009 20:28:01 +0000

[...] This post was mentioned on Twitter by Rob Porter. Rob Porter said: COOL RT @mezzoblue: Done! My first open source code release ever: http://bit.ly/15jxS [...]

Comment on Manual Geodata by Dave S.

Dave S. — Thu, 01 Oct 2009 17:04:57 +0000

An update: I found someone who provides elevation data free on the web, so I wrote the code to replace RunKeeper’s elevation metrics with API calls. For a number of reasons, that particular provider didn’t work out, and I can’t seem to find anywhere else online that I can query for elevation data (Google included).

For now, I’m giving up on the idea of routing around RunKeeper’s incorrect elevation measurements. I still have the code, so if I can ever find an accurate, reliable provider, I’ll swap it back in.

Also, I’ve just added support for KML files. I think with a bit more polish, I might be ready to actually release this code in some form. Stay tuned.

Comment on Manual Geodata by Dave S.

Dave S. — Wed, 23 Sep 2009 17:21:42 +0000

I just thought of a way around the elevation problem. RunKeeper seems pretty good at getting the lat/long coordinates right, so if I can find a free service to throw them at and have elevation data returned (Google Maps API key may help out here) then I can ignore the data from RunKeeper and use the correct data instead. Must experiment…

Comment on Manual Geodata by Kevin Haggerty

Kevin Haggerty — Tue, 22 Sep 2009 13:30:11 +0000

Dave – just made some data available to you and sent you an email telling you where to find it.

Comment on Manual Geodata by Dave

Dave — Mon, 21 Sep 2009 20:03:25 +0000

Thanks Kevin, I’ll be sure to try re-uploading. You’re right about the elevation being off, even in most recent versions. I’m noticing the exact same route is plotted differently when travelled at different times. I’ve been theorizing it might have been something to do with the fact I was listening to music on one trip and not the other, or it got an inaccurate lock at the beginning that persisted throughout the route, or something else. But maybe it is just the app itself.

Would love to play around with some routes from Ottawa, yes! That would be a great way to fix my manual fudging of the math that makes it Vancouver-specific at the moment. If you get a chance, throw a few GPX files onto a server somewhere and send me an email:

http://mezzoblue.com/contact/