Analyze Boston and the 2014 Open Data Executive Order
Boston's duty to publish rests on a mayoral order of 7 April 2014 and the administrative policy the CIO issued in July 2015 — no ordinance, and no reporting duty. The CKAN portal that followed in April 2017 carries 232 datasets. The policy names CC BY 4.0 as the default licence; the portal ships PDDL public-domain dedications instead.
Live
📅 since 2014
✔ Editor-reviewed
📊 Impact
232 datasets in the catalogue, read 26 July 2026, and current: 311 Service Requests was last modified 25 July 2026. Licence at dataset-metadata level: 216 datasets carry the Open Data Commons PDDL public-domain dedication, 14 carry none, 1 the share-alike ODbL. The 2015 policy names Creative Commons Attribution 4.0 as its default, so 93% of the catalogue ships a more permissive licence than the rule requires. No open-data compliance report and no published dataset inventory were found; the policy sets no reporting cadence.
🎓 Lesson
Read the API, not the policy page. Boston's written default is CC BY 4.0 and its datasets ship a public-domain dedication instead — more permissive than the rule they were meant to follow. The policy also sets no reporting duty, so there is nothing to audit in either direction.
Evidence🏛️ Official
Scale🏙️ City-wide
Sources
↗ Analyze Boston — CKAN package_search, licence facetPrimary scale and licence evidence, read 26 July 2026. Total: "count": 232. Licence facet at dataset level: odc-pddl "Open Data Commons Public Domain Dedication and License (PDDL)" 216; notspecified "License not specified" 14; odc-odbl "Open Data Commons Open Database License (ODbL)" 1. Read through CKAN rather than the portal's marketing pages, because the licence is carried per dataset in the license_id field and is stated nowhere else. A sampled record confirms it at field level: license_id "odc-pddl", license_url "http://www.opendefinition.org/licenses/odc-pddl".
↗ Analyze Boston — CKAN package_show, 311 Service RequestsCurrency check on the portal's highest-traffic dataset, read 26 July 2026: metadata_created 2017-01-10, metadata_modified 2026-07-25, with the 2026 resource file itself modified 25 July 2026 and annual files back to 2011. licence odc-pddl. Also the source for the live migration: a "311 Service Requests — NEW SYSTEM" resource created 28 October 2025 alongside a "311 Service Requests Data Transition Guide" and a note titled "311 Technology Transformation Project and the Open Data Portal" — 311 is moving to a new backend and the new cases land in a differently structured dataset.
↗ Sunlight Open Data Policy Hub — Boston, MA, Administrative Policy (30 July 2015)The instrument, independently transcribed and classified — as an administrative policy, not an ordinance. Sentence-level source for the licence divergence: "The default license for all City of Boston Open Data is the Creative Commons Attribution International 4.0 license", with attribution reading "City of Boston" and a link back to the source data, and "While this license is the default, other licenses may be used for specific data sets." For responsibility: "The City of Boston's Chief Information Officer (CIO) and whomever the CIO designates is responsible and manages this policy." For the catalogue duty: "The Chief Information Officer and the CIO's designee shall establish and maintain a Data Catalog." And for the accountability gap: the only cadence language is "The CIO or the CIO's designee will regularly review the catalog…"; the analysis records no annual compliance reporting requirement and no enforcement mechanism.
↗ Analyze Boston — Open and Protected Data Policy (dataset)The policy as the city itself publishes it, on its own portal. Description: "Following April 7, 2014 Executive Order from Mayor Walsh, an Open and Protected Data Policy was drafted to guide the City in defining, protecting, and ultimately making Open Data available and useful to the public. The policy provides working definitions for Open Data, along with information on how it is to be published, reviewed, and licensed." Metadata created 11 December 2016, last modified 15 May 2019, licence odc-pddl. The PDF resource is a scanned image and cannot be machine-read, which is why the policy's operative sentences are quoted from the independent transcription above.
↗ Analyze Boston — COB Executive Order, Open Data, 4-7-2014 (dataset)The originating order, published by the city on the portal it created. Description: "On April 7, 2014, Mayor Walsh signed an executive order directing the creation of an Open Data policy, pursuant with the City's goals toward Open Government. The Executive Order requires that the policy contain guidance on Open and Protected data classification, format, publishing, accessibility, and more." The order delegates: it tells the CIO to write a policy rather than imposing publication duties on departments directly. Also a scanned PDF.
↗ Sunlight Foundation — Boston: the tale of two open data policies (11 April 2014)Why Boston has a policy and not a law. Councillor Michelle Wu filed a draft open-data ordinance on 7 April 2014 for introduction on 9 April, modelled on the codified duties in San Francisco, New York City and Philadelphia; Mayor Walsh signed his executive order the same day. No record of the ordinance being adopted was found, and the policy registry lists only the order and the 2015 administrative policy for Boston — so the entry says the ordinance was not enacted rather than that it was defeated. Wu became mayor in 2021.
↗ City of Boston — Open Data to Open KnowledgeOperator and launch date from the city: the programme is run by the Department of Innovation and Technology, and the page dates the "Official release of Analyze Boston" to April 2017. Its stated goals include to "Inventory, catalog, and build out the City's first ever comprehensive data catalog" — the policy's Data Catalog restated as an aspiration three years later. The page carries no licence statement and no compliance or reporting commitment.
↗ Route Fifty — Boston seeks a more tech-savvy audience with new open data platform (March 2017)The platform switch, from trade press: Boston moved off its Socrata-powered portal to a CKAN-based platform delivered through OpenGov, reachable at data.boston.gov, with a beta in March 2017. CKAN rather than Socrata is what makes Boston's licence position directly checkable per dataset — the atlas's Chicago and San Francisco entries had to read Socrata's licenseId field instead. The vendor press release for the same launch claims the move merged the city's separate maps site into the portal; that claim is not repeated here, because the BostonMaps ArcGIS open-data site still exists alongside it, although geospatial datasets do appear inside CKAN under a "Boston Maps" organization.
↗ Analyze Boston — portal home pageRead 26 July 2026. The public face of the portal says only "Analyze Boston is the City of Boston's open data hub. We invite you to explore our datasets, read about us, or see our tips for users." It displays no dataset count, no licence statement and no link to the open data policy — the licence exists solely in per-dataset metadata. Basis for the entry's lesson.
↗ Open Data Commons — Public Domain Dedication and License (PDDL) v1.0What the shipped licence actually grants, for readers comparing the atlas's licence positions: a dedication of the database to the public domain, with no attribution and no share-alike condition. This places Boston alongside San Francisco at the most permissive end — and above its own written policy, whose CC BY 4.0 default would require attribution. The single ODbL dataset is the outlier in the other direction: ODbL carries a share-alike condition the rest of the catalogue does not.
↗ Northeastern University — Building a 'thriving civic data ecosystem' in Boston (6 July 2017)Kept as context and deliberately not merged into this entry. The Boston Area Research Initiative is an inter-university partnership of Northeastern and Harvard, launched 2011, whose NSF-funded Boston Data Portal "harvests and publishes a variety of data related to Boston and its neighborhoods — from census and social media data, to city building records and 311 calls", hosted on Harvard Dataverse. It is a separate institution with its own platform and its own terms, and republishing cleaned research versions of municipal records is its own work, not the city's. It belongs in a separate entry if it belongs in the atlas at all.
📎 Cite this project
1001 Smart Cities (2026). “Analyze Boston and the 2014 Open Data Executive Order” — Boston, United States. The Smart City Atlas. https://1001smartcities.org/projects/boston-analyze-boston/ (last verified 2026-07-26). Data: CC BY 4.0.
The underlying data is free to reuse with attribution — see the open data page.
🔗 Related projects
🇺🇸 Chicago's Open Data Executive Order and Portal · Chicago
Chicago's 2012 order did demand annual reports — and the city stopped filing them in 2014, as its Inspector General found in 2020.
🇺🇸 DataSF and San Francisco's Open Data Law · San Francisco
Both ship PDDL, from opposite instruments: San Francisco's duty sits in the city code, Boston's in a 2014 mayoral order that demands none.
🇺🇸 NYC Open Data and the 2012 Open Data Law · New York City
Councillor Wu filed a Boston ordinance modelled on New York's law on the same day in 2014; it never passed, and the mayor's order stands.
🇹🇭 Open Bangkok: Data Catalogue & Policy Scorecard · Bangkok
Opposite ends of the licence scale: Bangkok's files carry no licence at all; 93% of Boston's ship a public-domain dedication.
→ Open this project in the interactive atlas · → 📡 Data & IoT category · 🚩 Report an error