Difference: DuckyInfoVisMilestones (3 vs. 4)

Revision 42005-12-09 - DuckySherwood

Line: 1 to 1
 
META TOPICPARENT name="DuckyInfoVisProject"

Ducky's Info Vis Milestones

Bugs

Added:
>
>
  • fix intersectsRectangle better -- coll terr must do 1982 but not 1937
 
  • Can't drag
Changed:
<
<
  • sometimes tracts don't draw -- see College Terrace
>
>
 

Current worries

Added:
>
>
  • What are storage needs?
    • in Palo Alto, .005 degrees long for 500 pixels at max zoom in => 100,000 pixels / degree
    • in Palo Alto, .002 degrees lat for 300 pixels at max zoom in => 150,000 pixels / degree
    • US is about (-66 to -124) 58 degrees wide => 12,000 images wide (at 5K apiece)
    • US is about (32 to 48) 16 degrees tall => 8,000 images tall (at 5K apiece)
    • so at max zoom level, 96M images to cover the whole US * 5K => 480G
    • roughly powers of two as zoom out; 15 zoom levels before whole US fits (after that, it's just silly?)
    • so roughly 2*480G worth of space needed for whole US, or about 1000G
    • if it takes about 5 sec to render a little one =>

  • What are units of boundary areas?
 
  • What if different browsers don't work?
  • caching
  • How do I deal with the huge dynamic range?
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2025 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback