
Portland's Resolution No. 36735, adopted in 2009, paired open data with open source software: it directed the city's technology bureau to publish freely available public datasets with regional partners, adopt open standards and consider open source in purchasing.
What the resolution does
Resolution No. 36735 is one of the earliest local government actions in this index. Its stated aim was to grow the Portland region's technology community by promoting open government, open data and partnerships across the public, private and nonprofit sectors, academia and labor.
Unlike later open data policies, it does not set up a governance structure, an inventory or deadlines. It is a statement of direction backed by a short list of tasks for the Bureau of Technology Services.
Adoption context
In 2009, very few cities had passed an open data policy. Portland framed the issue around its local open source industry: the preamble argues that publishing structured, standardized, machine-readable data lets information be combined in new ways and opens niche markets, and that open source lets the city customize and redistribute the software it uses.
Key provisions
- Enter into agreements with regional partners to publish and maintain public datasets that are open and freely available, while respecting privacy and security concerns identified by the City Attorney.
- Develop a strategy to adopt prevailing open standards for data, documents, maps and other media.
- Organize a regional contest for software that collects, organizes and shares public data.
- Consider open source software when commercial licenses come up for renewal.
- Promote Portland as a host for open source conferences, and circulate technology contracting opportunities to the local software community.
Which guidelines it reflects
The resolution touches goals and values, sensitive information, open formats, open access, open code, real-time updates and partnerships. Its heavy emphasis on open source makes it a reference point for guideline 16.
Portland returned to the subject in 2017 with a council ordinance, which the original collection also listed.
Why this matters for your business data
Portland's resolution made an explicitly economic argument: structured, machine-readable data creates markets that did not exist before. That argument applies just as well to private operational data. Transaction logs, scheduling records and inventory movements become valuable when they are clean, consistent and documented. Our guide from open data policy to data value walks through that logic, and the valuation calculator gives a first estimate.
We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Frequently asked questions
Did Portland's 2009 resolution require departments to publish specific datasets?
No. It directed the Bureau of Technology Services to pursue agreements, standards and a contest, but it did not list required datasets, deadlines or reporting duties. That lighter structure is typical of first-generation policies adopted before model language became common.
Why does an open data resolution talk about open source software?
Portland treated open data and open source as two parts of one openness agenda. Publishing data in open standards and using software the city can inspect and modify were both seen as ways to cut lock-in, support the local tech sector and let residents build tools on public information.
Guidelines this policy reflects
Sources
Updated December 31, 2024.