tecznotes

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

Jan 6, 2013 7:31pm

loading artifacts, google maps for iOS

The new GMaps for iOS uses the same/similar vector loading process as its longtime Android counterpart. The high-res stuff, including buildings and tiny streets, looks like it comes in right at zoom level 16, which is about where I would’ve put it given the choice.

The transition between zooms is a bit odd. I would not have expected the difference in street widths between the loaded and unloaded sections here. OpenGL does how (as far as I know) have its own concepts like round line caps or joins, so maybe there’s some client-side buffering these that’s expensive to run more than once per geometry load? The “hot dog” street endings show that each tile’s worth of geometry data comes clipped; I haven’t tested to see whether street names straddle z16 tile boundaries or not.

Interestingly, GMaps makes no attempt to model elevated freeways, terrain, or anything else vertical beyond buildings. In use, this feels like a satisfactory compromise. The road names here are in perspective, applied to the ground as textures, while the route numbers are all billboards facing forward.

I’m not sure why the Grand Avenue label below is not tilted back like Elita or Perkins.

The translucent handling of the building is very good. It’s sketchy enough that you can recognize them and navigate without being distracted by their incompleteness.

Comments (1)

  1. If I recall correctly I heard in a google talk about webgl and maps that they were rendering circles to create the roads joins (and endings). I though they were not cutting the geometry but your image points they are.

    Posted by javisantana on Friday, January 11 2013 12:41pm EST

Sorry, no new comments on old posts.

July 2016
Su M Tu W Th F Sa
     
      

Recent Entries

  1. quoted in the news
  2. dockering address data
  3. blog all dog-eared pages: the best and the brightest
  4. five-minute geocoder for openaddresses
  5. notes on debian packaging for ubuntu
  6. guyana trip report
  7. openaddresses population comparison
  8. blog all oft-played tracks VII
  9. week 1,984: back to the map
  10. bike eleven: trek roadie
  11. code like you don’t have the time
  12. projecting elevation data
  13. the bike rack burrito n’ beer box
  14. a historical map for moving bodies, moving culture
  15. the other openstreetmap churches post
  16. platforminess, smartness, and meaningfulness
  17. writing a new continuous integration service for openaddresses
  18. state of the map 2015
  19. bike ten: schwinn touring, v2
  20. blog all oft-played tracks VI

Archives