Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Ducky's InfoVis Project ProposalProposal specs![]() | ||||||||
Added: | ||||||||
> > | Proof of concept: somebody's overlaying transpart gmaps over gsatelite![]() | |||||||
Participants | ||||||||
Line: 22 to 23 | ||||||||
Proposed solutionyour proposed infovis solution. You should propose an infovis solution, and of course relate it to your domain task and dataset. Abstraction is critical here! | ||||||||
Changed: | ||||||||
< < | I will 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 Javascript and the Google Maps API to serve maps, capture pan/zoom events, and to overlay area data on top of the Google Maps. | |||||||
Changed: | ||||||||
< < | I will 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 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![]() ![]() | |||||||
Deleted: | ||||||||
< < | I will use either @@@
| |||||||
Scenario |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
Ducky's InfoVis Project ProposalProposal specs![]() ParticipantsOnly me, Kaitlin Duck Sherwood, ducky@csDELETEthisTEXT.ubc.caDescriptionDisplay of @@@ area-based GIS data via a Google Maps mashupPersonal expertise:
Proposed solutionyour 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 will 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 will use the gd library, probably with a perl wrapper, to generate a transparent PNG image to overlay on top of the maps. I will use either @@@
Scenarioa 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 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. @@@ GMaps API, javascript, gdMilestonesInclude a list of project milestones with dates, breaking down the work into a series of smaller chunks. @@@ |