CS382:Unit-mashup: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 17: | Line 17: | ||
== Lab activity - materials, process and software == | == Lab activity - materials, process and software == | ||
* Quaker meetings, <metric X> mashed up on map ( [http://quakermeetings.com database; we own it] ) | * Quaker meetings, <metric X> mashed up on map ( [http://quakermeetings.com database; we own it] ) | ||
* Using WebDB to map dorms to major, possibly over time (This one may not work due to not being able to access relevant data) | |||
== Scheduling - early, late, dependencies on other units, length of unit == | == Scheduling - early, late, dependencies on other units, length of unit == | ||
=== Timing === | === Timing === | ||
Revision as of 01:49, 18 February 2009
Data Visualization with Mashups
Background reading, one or more pointers/documents and a brief synopsis of what's covered in them
- web tool for non-programmers for making mashups
- chapter 1 of book on power of geo mashups
- KML documentation
Lecture notes - outline form
- what data do i need?
- where do i find data?
- coordinating multiple data sources
- how do i encode that data to be useful?
- what can i discover through visualization?
- how much data do i need to be useful?
- examples
Classroom response questions - at least three
Lab activity - materials, process and software
- Quaker meetings, <metric X> mashed up on map ( database; we own it )
- Using WebDB to map dorms to major, possibly over time (This one may not work due to not being able to access relevant data)
Scheduling - early, late, dependencies on other units, length of unit
Timing
Doesn't matter
Length
One week; but if we find enough material it could be (and would serve well as) two