Compliance first: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.
Home / Guidelines / Open data policy guideline 18
Open data policy guideline 18

Data Portals and Websites: Open Data Policy Guideline 18

Data Portals and Websites: Open Data Policy Guideline 18

Guideline 18 calls for a central, searchable home for public data and for the policy that governs it, so residents, journalists and developers know exactly where to look and what is available.

Of all the provisions found in municipal open data policies, the requirement for a central portal is among the most widely adopted. It is also the provision most often mistaken for the whole policy.

What the guideline means

Data scattered across department web pages is hard to find and easy to forget. Guideline 18 asks a government to create one central location for publishing datasets and explaining its open data policy. That hub can be a general-purpose catalog or a family of topical portals (spending, ethics, transit), as long as related portals point to one another.

A good portal does more than list files. It documents each dataset (see Guideline 13), shows what exists through an inventory, lets search engines index it, and ideally publishes usage analytics so both users and publishers can see which datasets matter most.

Model policy language patterns

Typical portal provisions, paraphrased:

  • The city shall maintain a single web portal through which all public datasets are made available, managed by a named department.
  • Departments shall publish datasets to the portal, or to an approved departmental site linked from it.
  • The portal shall include the open data policy, the dataset inventory, technical standards and a feedback mechanism.
  • The portal shall go live within a stated number of days of adoption (see Guideline 27).

Where it appears in adopted policies

Portal language is close to universal among cities that have passed an open data policy. A few illustrations from this index:

Chicago, Philadelphia, Louisville, Austin, Washington DC and dozens of others in the full index include similar provisions.

Common pitfalls

  • Portal as finish line. Launching a catalog is visible and satisfying; keeping it current is not. Many portals filled quickly and then went stale.
  • Blocking search engines. If datasets cannot be indexed, they are effectively hidden.
  • Thin documentation. A table without definitions, units or a contact person generates confusion rather than reuse.
  • Fragmentation. Topic portals that do not link to each other recreate the scattered-website problem the guideline was meant to solve.

A practical checklist for portal provisions

  • Designate one office responsible for the portal and its uptime.
  • Require that the portal list every published dataset and link to the full inventory, including datasets not yet released.
  • Allow search engines and other third parties to index the catalog.
  • Publish the open data policy, technical standards and annual reports on the portal itself.
  • Offer both bulk downloads and programmatic access for each dataset.
  • Show usage statistics and provide a visible feedback channel.
  • Plan for migrations: stable dataset identifiers and redirects keep links working when platforms change.

What portals teach about the value of operational data

A public portal is a lesson in packaging. Buyers of data, whether civic developers or AI/ML teams, judge a dataset first by whether they can find it, understand it and trust that it will be maintained. The same is true of private operational data: a clean catalog, a data dictionary and a clear refresh schedule raise what a dataset is worth.

If your business holds operational records that could inform models, you do not need to build a portal. You need an honest inventory and a de-identified extract. The guide from open data policy to data value walks through the parallel, and sell my data explains how a de-identified dataset is listed and priced.

We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Our compliance promise: We never take HIPAA/PHI data or personal customer data. Everything is de-identified before it leaves your control.

Frequently asked questions

Is launching an open data portal the same as having an open data policy?

No. A portal is infrastructure; a policy sets the rules for what goes on it, how fast, in which formats, under what license and with what oversight. Many cities launched portals before adopting a policy, and those portals often stalled because no one was accountable for keeping them current.

Should every department have its own data site?

Departmental or topical sites can work, but the guideline recommends a single central catalog that lists everything and links to specialized portals. Users should not need to know a city's organizational chart to find a dataset.

What features make a portal useful?

A searchable catalog tied to the data inventory, clear metadata for each dataset, bulk downloads and APIs, a feedback channel, indexing by search engines, and published usage statistics. Usage numbers help residents see what others find valuable and help agencies prioritize maintenance.

How quickly did cities typically launch portals after adopting a policy?

Timelines varied. Some policies set a short deadline, such as the 120-day requirement in Minneapolis's 2014 policy, while others relied on an implementation plan drafted after adoption. Short, specific deadlines tended to produce faster launches.

Policies in the index that reflect guideline 18

PlaceAdoptedInstrumentGuidelines
Washington, DCJun 12, 2006Executive memorandum1131822
San Francisco, CAOct 21, 2009Executive directive11824
San Francisco, CAOct 29, 2010Ordinance47811182526
Cook County, ILMay 4, 2011Ordinance12378131825
Raleigh, NCFeb 7, 2012Council resolution381618
New York, NYMar 7, 2012Local law (Local Law 11 of 2012)14578101118
Providence, RIMar 19, 2012Resolution31824262729
Philadelphia, PAApr 26, 2012Executive order (No. 1-12)34578182224
Madison, WIAug 15, 2012Ordinance457810111318
Chicago, ILDec 10, 2012Executive order34678101113
Montgomery County, MDDec 17, 2012County legislation (Bill 23-12, Open Data Act)457811131822
San Francisco, CAMar 28, 2013Ordinance34578101118
South Bend, INAug 22, 2013Executive order237810182528
Austin, TXAug 26, 2013Administrative memo123457810
Louisville, KYOct 11, 2013Executive order (No. 1, Series 2013)1234781018
Oakland, CAOct 15, 2013Council resolution (No. 84659)2345781011
Honolulu, HINov 27, 2013Ordinance237810111820
Los Angeles, CADec 18, 2013Executive directive (No. 3)37818222630
Pittsburgh, PAMar 19, 2014Ordinance12345678
Hartford, CTMar 26, 2014Executive order34789182224
Boston, MAApr 7, 2014Executive order3891318202425
Nashville, TNMay 12, 2014Executive order (No. 043)2345781011
Chattanooga, TNMay 31, 2014Executive order123467810
Kansas City, MOJun 19, 2014Ordinance (No. 140443)81018242713
Washington, DCJul 21, 2014Executive directive (Mayor's Order 2014-170)12356789
Minneapolis, MNAug 1, 2014Council-adopted policy34568131819
Houston, TXSep 18, 2014Administrative policy (AP 8-7)234567810
San Diego, CANov 24, 2014Administrative policy45818202427
Denton, TXFeb 9, 2015Administrative directive357811121618
Detroit, MIFeb 19, 2015Executive order818
Suffolk County, NYJul 31, 2015Administrative policy78131820222426
Jackson, MSSep 1, 2015Executive order (No. 2015-06)12345678
Cambridge, MASep 21, 2015Ordinance12345678
Asheville, NCOct 13, 2015Council resolution13489101118
Durham, NCNov 23, 2015Administrative policy7818192430
Tulsa, OKDec 21, 2015Executive order123458910
Seattle, WAFeb 1, 2016Administrative policy (CTO policy)14678101112
Baltimore, MDMar 7, 2016Ordinance1781113182426
San Jose, CAApr 5, 2016Council policy1681113182230
Las Vegas, NVApr 12, 2016Administrative policy (City Manager policy CM510)12345678
Saint Paul, MNApr 27, 2016Council resolution12578101113
Milwaukee, WIJul 14, 2016Council resolution12356789
Bellevue, WAAug 1, 2016Management policy15678101118
New Orleans, LASep 1, 2016Executive order (MJL 16-01)124511182124
Naperville, ILNov 15, 2016Council resolution45789101112
Fort Collins, COFeb 7, 2017Council resolution12345678

Sources

  1. Sunlight Foundation Open Data Policy Guidelines (historical reference)
  2. Sunlight Foundation open data policy collection (public repository)

Updated December 31, 2024.