Technical Ramblings

Make a map of my trip to North Carolina, including route information and foursquare checkins; using the trip log I recorded, make a graph of average speed over various spans. Highlight all the points along the trip where something went terribly wrong.

Create a game out of taking photos of POIs — sort of like foursquare, but for photos. Come up with an algorithm to suggest what places should get photos based on number of times they show up in things like search results, or are clicked, and which ones don’t have photos. (I think this is probably what that Google thing is, but I don’t really know.)

Try to build a tool which can decide what place a particular photo is attached to via text recognition or by associated metadata on a photo sharing site like flickr. Start with geocoded photos; see if it’s possible to extend somehow to non-geocoded photos (though I can’t think of anything obvious).

Build a dotmap-style map of every point address that NAVTEQ has in its database, possibly adding in POIs or something. Also, see if it’s possible to rewrite the dot map as something that looks as good, but can be dynamically generated for lower zoom levels.

Using the streetview-style imagery that Nokia has, build a tool which would let users pick a ‘good’ view for POI, using a suggestion starting from a geocoded coordinate. This would probably involve building a slippymap based viewer for Nokia’s streetview imagery, because as far as I know, there’s no dynamic scriptable viewer for that data.

These are just a few of the things that I’ve thought of over the past month or so, but the motivation to do any of them is always pretty low. Maybe I should get a new hobby. Or weed the garden instead.

This entry was posted on Sunday, August 4th, 2013 at 10:10 pm and is filed under default. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.