Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Ducky's InfoVis Project ProposalProposal specs![]() | ||||||||
Line: 4 to 4 | ||||||||
Proposal specs![]() | ||||||||
Deleted: | ||||||||
< < | ||||||||
ParticipantsOnly me, Kaitlin Duck Sherwood, ducky@csDELETEthisTEXT.ubc.caDescriptionI plan to do a Google Maps mashup that overlays semi-translucent images on Google Maps in order to show area-based data. | ||||||||
Deleted: | ||||||||
< < | Note: I had worried that the overlaying might be too slow, but I have seen someone else overlay transpart Google Maps over Google satellite images![]() | |||||||
Personal expertise:
| ||||||||
Line: 23 to 21 | ||||||||
Proposed solution | ||||||||
Changed: | ||||||||
< < | 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 Shapefile C library![]() ![]() | |||||||
> > | @@@ | |||||||
Scenario | ||||||||
Changed: | ||||||||
< < | a scenario of use. Preview from Evaluation reading hcibib.org/tcuid/chap-2.html | |||||||
> > | @@@ scenario | |||||||
Changed: | ||||||||
< < | 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 | |||||||
Deleted: | ||||||||
< < | @@@ | |||||||
Changed: | ||||||||
< < | 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. | |||||||
> > | Implementation approach | |||||||
Changed: | ||||||||
< < | @@@ (ready two: one for the Vancouver desirable-living-places, one for STAR scores) | |||||||
> > | 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. | |||||||
Added: | ||||||||
> > | 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. | |||||||
Changed: | ||||||||
< < | Implementation approachYou 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. | |||||||
> > | I plan to use C language Shapefile C library![]() ![]() | |||||||
Changed: | ||||||||
< < | @@@ GMaps API, javascript, gd | |||||||
> > | @@@ library for dBASE files | |||||||
MilestonesInclude a list of project milestones with dates, breaking down the work into a series of smaller chunks. | ||||||||
Added: | ||||||||
> > | Tasks (not milestones): | |||||||
| ||||||||
Added: | ||||||||
> > |
| |||||||
| ||||||||
Changed: | ||||||||
< < |
| |||||||
> > |
| |||||||
|