Algorithmic Regulation of Transportation.
summary
Cities increasingly demand fine-grained vehicle or bike location data as a condition for permits, while GDPR turns much of that pseudo‑anonymous telemetry into personal data requiring lawfulness and minimization. Practical fixes discussed include query-on-suspicion instead of continuous feeds, contractual bans on re‑identification, and using privacy-by-design and geofencing so enforcement happens without full tracking. Amsterdam scraped Google’s “popular times,” trained a predictive model of neighborhood crowding, then negotiated API access — showing prototypes can work but raise legal and governance gaps.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 3:50Policy responsive regulation
- 5:14Data collection
- 5:54Government role
- 9:02Realtime data
- 9:55Planning vs investment
- 13:52Sharing individual data
- 15:34What data do we need
- 17:52Data used for enforcement
- 23:49Interests
- 24:50Compliance
- 29:37Data Privacy
- 32:05Mobility Data Specification
- 34:03Data Protection
- 41:24Data Sharing
- 43:51WiFi Tracking
- 47:11Open Data
- 51:28Public sector oversight
- 54:57Global mobility
related talks
01h 19mAcademic sessions 1.
01h 16mData protection and Big Data: what about regulating Big Data analytics?
04mDeep Dive: Identity, Privacy, and Informed Consent in the...
01h 15mCOLLECTIVELY MAKING IT WORK: (F)LAWS OF INDIVIDUAL APPROACHES TO RESIST PLATFORM POWER
01h 20mLocation privacy: what problems - which solutions?
01h 07mAcademic sessions 2.
47mDesigning for User-Centered Privacy
19mDesigning for Civic Trust: An Infrastructure to Help Long Beach Residents Manage Their...