Michal Migurski's notebook, listening post, and soapbox. Subscribe to this blog. Check out the rest of my site as well.

Jan 22, 2013 8:55pm

week 1,836: back at shiny

Last week I announced my departure and many friends said nice, encouraging things on Twitter and here. Thank you. I’m sort of leaping into the abyss here, and it makes a huge difference to know I’m not just twisting in the wind.

Chicago and Denver were both cold and fun. I attended Chris Helm, Steve Citron-Pousty and Brian Timoney’s event JS.Geo. Peter Batty has a complete writeup, which doesn’t quite do justice to the absolute ubiquity of D3 at the conference. It was a good opportunity for me to finally/again get my head straight with D3 data joins with Seth and Aaron Ogle. I remain convinced that as D3’s primary feature, this is sadly under-documented. In Denver, my mustache repeatedly iced over. In Chicago, less so but it was still pretty cold.

I’m back now, and picking up a few projects.

Green Means Go is due for some thinking about individual counties. I’d like to create a single, printable view for each of 3000+ counties with some information about OSM coverage attached.

I’m starting to look at tiled data, D3 and WebGL together for the Nokia WebGL Maps. I’m super excited about the possibilities of shaders here, and need to get my head around tile-like loading of linear ArrayBuffers.

The Metro Extracts are overdue for an update, and I’d like to start doing these more regularly using OSM-US Foundation hardware. Some recent interest in the project suggests that I’ve been paying too little attention to it.

Some small potential consulting gigs, and general future planning.

Comments (3)

  1. Michal, Best of luck in your new pursuits. It would definitely be great to get an update of the Metro Extracts. Thanks, David.

    Posted by David on Tuesday, January 22 2013 10:00pm EST

  2. Hey, I've been interested in rendering OpenStreetMap data in 3d for some time now, and it'll be cool to see where your experiments with WebGL lead [I'm also obsessed with shaders!]. I'm curious as to why you're looking at how Nokia's maps work though -- is it just out of (non-OSM related) interest? To maybe download tiles and have 'em for offline use? Since I can't see Nokia wanting the data being used/repurposed for separate applications, etc. Regards, Preet

    Posted by Preet on Wednesday, January 23 2013 2:03pm EST

  3. Preet, I’m looking at Nokia because they have an excellent source of interesting data to play with to understand things like LIDAR and WebGL. It’s not republishable but it’s already been pre-treated in a few important ways.

    Posted by Michal Migurski on Thursday, January 24 2013 2:12am EST

Sorry, no new comments on old posts.

February 2018
Su M Tu W Th F Sa

Recent Entries

  1. planscore: a project to score gerrymandered district plans
  2. blog all dog-eared pages: human transit
  3. the levity of serverlessness
  4. three open data projects: openstreetmap, openaddresses, and who’s on first
  5. building up redistricting data for North Carolina
  6. district plans by the hundredweight
  7. baby steps towards measuring the efficiency gap
  8. things I’ve recently learned about legislative redistricting
  9. oh no
  10. landsat satellite imagery is easy to use
  11. openstreetmap: robots, crisis, and craft mappers
  12. quoted in the news
  13. dockering address data
  14. blog all dog-eared pages: the best and the brightest
  15. five-minute geocoder for openaddresses
  16. notes on debian packaging for ubuntu
  17. guyana trip report
  18. openaddresses population comparison
  19. blog all oft-played tracks VII
  20. week 1,984: back to the map