Thursday 12-2PM, 03-08-2007
From CENS Urban Sensing
Urban Sensing Meeting Notes
Thursday, March 08, 2007
Contents |
Campaign Meeting (12-1pm)
Update – how are the two current campaigns running
Weekly Campaign Ideas:
Thomas – Red-light/Green-light campaign idea. How many red/green lights do you encouter in a walk through LA. How long do you wait at the red lights.
Aitan – Day in the life photo idea – perhaps ‘minute/hour in the life of’ for us using the cell cam
David – Emotional mapping. Sensing of location / (surrounging environment) and emotion.
Nicolai – Extension of above, measure the heart beat of certain geographical locations (by having a heart monitor and GPS info uploaded)
Eric – Light sensing
Sasank – Day as a ‘day laborer’ (follow day laborers for a day) extension. Extend into different professions.
Jason – Bye
August – Query what’s interesting with what’s going on around me. A location-based social/event networking.
Andrew – Virtual Grad Student: Alerts for free-food (with extra info – quality of food, closeness, relatedness of lecture to research interests).
Elisa – Take pictures of fast food places that we frequent or pass by. Looking for density of fast-food joints in various locations. Menu/price change from city-to-city.
??? – Bedroom – correlate noise patterns and quality of sleep (maybe adaptability as well).
Jeff – Photograph or record things people consider the ‘edge’ of privacy – one step further would be invasive, but one step back would be acceptable. Could be public persona vs. private (esp. where there is not control over what is being recorded)
Vids – Bye
Soundscape update
- Problem with noise spikes (brushing the mic, etc.)
- Idea of getting multiple users’ data at the same location/time
- All should upload to the same table (w/ a unique ID) for test phase.
- Ideally, we would like to use the Soundscape tool (fully operational) over the Summer
Action Items
- Elisa & Stephen – Come up with a test plan and date for the soundscape campaign.
- Diet Sense II participants – Finish Diet Sense
How do we choose which campaigns to do?
[Nicolai] Run campaigns that solved currently open technical issues in order to build a better framework. Classify campaigns by what technologies they require.
[Jeff] What should the criteria be between technology value vs. cultural value in the campaigns we choose to run.
[Sasank] Base it on stakeholders: Medical, Urban Planning, Indiviual-interest, Cultural Choose campaigns with breadth (multiple coverage areas). Choose campaigns that get good information about various collection methods (autonomous, triggered, …).
Look at pros/cons of past campaigns:
Locationscape – Pros: Easy to run Almost all campaigns will need location, thus THIS is critical functionality
Dietsense –
ls ds applic. specificity low high purpose? tech. feasibility tech. feas. primary data for tech. data app secondary data for app data for tech data quality ok? lower data integrity? sampling freq always trigger/meal ease of constr. high high primary use high lower can eval? n/a ? secondary use yes, yes ? intrusion not so much yes, more
privacy issues? how sensitive is the data? how useful is the data as privacy protecting measures are applied?
Architecture Meeting (1-2PM)
How Ordinary Internet Users can have a Chance to Influence Privacy Policies… paper
[Elisa]
(see slide deck)
PAPER: http://remap.ucla.edu/jburke/misc/Petterson06.pdf
SLIDES: http://www.lecs.cs.ucla.edu/urban-sensing/images/3/3b/InfluencingPrivacyPolicies.pdf
Pop-up boxes for the data you allow to be sent and for what purpose (e.g. when you’re ordering a book, there is certain data REQUIRED – name, address, cc. But the company would also like to use your data for other marketing purposes – do you allow this?)
IETF’s Geopriv
[Andrew](see slide deck)
http://www.lecs.cs.ucla.edu/~adparker/kansas/2007-03-08%20Notes%20on%20IETF%20Geopriv.ppt
- Location can be expressed in either Lat/Lon or Logical Address. Logical Address could be a postal address, followed by floor, room, cube, … (for finer granularity)
- Location Generator, Location Server, Lcoation Recipient, Rule Holder
- LG sends LO to LS; LS queries RH for rules about user; LR queries LS for location data about targets.
- There is an override in the even of an emerency generated by the target/location generator. Any data required may be released. This is seen as a trade-off between privacy and health/safety in emergency situations.
Had to leave for class….
