Citizen Portal
Sign In

Get Full Government Meeting Transcripts, Videos, & Alerts Forever!

Get email alerts on the Open Data topic

No spam. Unsubscribe anytime.

Committee advances open data ordinance to create Chief Data Officer and departmental data coordinators

San Francisco Board of Supervisors, Government Audit and Oversight Committee · March 28, 2013
AI-Generated Content: All content on this page was generated by AI to highlight key points from the meeting. For complete details and context, we recommend watching the full video. so we can fix them.

Summary

The Government Audit and Oversight Committee advanced an ordinance to establish a Chief Data Officer, require departmental data coordinators and set standards for open datasets and procurement, with a 60-day compliance plan once the CDO is appointed.

The Government Audit and Oversight Committee voted to forward an ordinance to the full Board of Supervisors that would amend Administrative Code Sections 22D.2 and 22D.3 to strengthen San Francisco—s open data program by creating a Chief Data Officer (CDO), requiring departmental data coordinators and establishing consistent publication and licensing standards.

Supervisor David Chu, the ordinance sponsor alongside Mayor Lee, said the legislation aims to restore San Francisco—s national leadership on open data by making open data the city—s default and by improving standards and procurement language so the city retains ownership of datasets and APIs. "First, it creates a chief data officer position...Second, it requires that each city department designates a data coordinator...Thirdly, this legislation requires the development of consistent standards in how data is presented," Chu said.

Jay Nath, the Mayor—s Chief Innovation Officer, described the policy goals and implementation timeline. He said the CDO will work with agency data coordinators, help ensure new technology purchases have public APIs or equivalents, and push for open licensing (for example, Creative Commons 0). Nath said agencies will be required to produce a compliance plan — a catalog of datasets they manage — within 60 days after the CDO is appointed.

City department staff who spoke in support described existing datasets and projects: Travis Fox (SFMTA) pointed to real-time transit predictions, asset and bike-facility data, and plans for a Taxi Data Access System; Rajiv Bhatia (Department of Public Health) highlighted restaurant health inspection data and a Sustainable Communities Index and said open data has improved internal data organization.

More than a dozen public commenters representing tech companies, startups, civic organizations and national open data initiatives urged passage. App developers and companies such as CurbText and Appolicious described practical uses, including real-time towing alerts and tools to help drivers avoid being towed; CurbText requested access to towing plate data at the moment a tow is dispatched. Multiple speakers urged a transparent CDO search and attention to equitable access for nonprofit and underserved communities.

Chair and supervisors accepted technical edits suggested by the City Attorney to clean up redundant language and renumber sections; Supervisor David Campos moved to forward the ordinance with a positive recommendation and the committee approved the item for the full Board.

Next steps: the ordinance will be placed on the Board of Supervisors agenda for further consideration; the CDO appointment will trigger a 60-day clock for agency compliance plans as described in testimony.