(r2) DuckyInfoVisProjectProposal < Main

Tags: view all tags
---+ Ducky's <nop>InfoVis [[DuckyInfoVisProject][Project]] Proposal
[[http://www.cs.ubc.ca/~tmm/courses/cpsc533c-05-fall/projectdesc.html#proposals][Proposal specs]]

Proof of concept: [[http://www.kokogiak.com/gmaps-transparencies.html][somebody's overlaying transpart gmaps over gsatelite]]


---++++++ Participants
Only me, Kaitlin Duck Sherwood, ducky@cs.ubc.ca

---++++++ Description
Display of @@@ area-based GIS data via a Google Maps mashup

---++++++ Personal expertise: 
   * I did a project integrating maps, floorplans, and a virtual walkthrough years ago at UIUC.  
   * I have investigated several maps/census schemes in the past 10 years, but never gotten past the exploratory stages.
   * I am sort of aware of 
   * I have never written anything in Javascript before, nor any dynamic client-side code of any kind, but would like to learn. 
   * This could be a really cool project.


---++++++ Proposed solution
 your proposed infovis solution. You should propose an infovis solution, and of course relate it to your domain task and dataset. Abstraction is critical here!

I plan to use Javascript and the Google Maps API to serve maps, capture pan/zoom events, and to overlay area data on top of the Google Maps.

I plan to use the gd library, probably with a perl wrapper, to generate a transparent PNG image to overlay on top of the maps.

I plan to use C language [[http://shapelib.maptools.org/][Shapefile C library]] to parse a variant of the TIGER/Line data -- the [[http://shapelib.maptools.org/dl/shapefile.pdf][ESRI shapefile data]].



---++++++ Scenario
 a scenario of use. Preview from Evaluation reading hcibib.org/tcuid/chap-2.html

    A scenario spells out what a user would have to do and what he or she would see step-by-step in performing a task using a given system. The key distinction between a scenario and a task is that a scenario is design-specific, in that it shows how a task would be performed if you adopt a particular design, while the task itself is design-independent: it's something the user wants to do regardless of what design is chosen. 

@@@

---++++++ Interface mock-ups
# illustrations of what the interface will look like must be included in scenario. Hand-drawn sketches scanned in or mockups made with a drawing program are fine.

@@@ (ready two: one for the Vancouver desirable-living-places, one for STAR scores)


---++++++ Implementation approach
 You don't need lots of detail, just high-level things like which language and platform(s) you will use, and whether you will build on any pre-existing software or toolkits.

@@@ GMaps API, javascript, gd


---++++++ Milestones
 Include a list of project milestones with dates, breaking down the work into a series of smaller chunks.

@@@
Topic revision: r2 - 2005-10-29 - TWikiGuest
~~Edit~~
~~Attach~~