Boston Approved Building Permits, 2006 to present
- Provider
- City of Boston (Inspectional Services Department)
- License
- Open Data Commons Public Domain Dedication and License (PDDL) 1.0
- Size
- 1 file
- Records
- 659,934 rows
- Stored at
- data.boston.gov
- Access
- Free and public. No account with the data provider is needed.
- Category
- Urban & Civic
- Source
- https://data.boston.gov/dataset/approved-building-permits
About Boston Approved Building Permits, 2006 to present
Every building permit approved by the City of Boston Inspectional Services Department from 26 September 2006 to the present: 659,934 rows in a single DataStore-loaded resource, refreshed daily. One row is one approved permit. Each carries the permit number, a work-type code (INTEXT, ERECT, EXTREN, RAZE, ELECTRICAL, PLUMBING, and about thirty others), the permit type description (long form, short form, amendment, certificate of occupancy, electrical, plumbing, gas, fire alarm), a free-text description and applicant comments, the applicant name, the declared valuation and total fees, issued and expiration dates, permit status, occupancy type, square footage, the full address with ZIP and ward, the assessing property and parcel identifiers, and coordinates in both Massachusetts State Plane (gpsx, gpsy) and WGS84 (x_longitude, y_latitude). Because the parcel_id and property_id columns join directly to the Property Assessment rolls and to the 2025 parcel geometry, this dataset is the standard instrument for measuring physical investment in the city: construction and renovation intensity by neighborhood over two decades, the pipeline of new housing units, teardown and conversion activity, and the lag between permit issue and completion. Two columns need care and are covered in the schema card. declared_valuation and total_fees are text formatted as currency ('$36,500.00') including negative amendments, so they need the dollar sign and commas stripped before a cast; the declared valuation is what the applicant self-reported at filing, not an appraised cost, and amendment permits restate rather than add to the original. issued_date and expiration_date are the only genuinely typed timestamp columns in the resource, which makes them safe to compare directly, while sq_feet is zero for the large majority of permits rather than null. Published by the Inspectional Services Department under PDDL 1.0.
How to load Boston Approved Building Permits, 2006 to present in Python
import io, json, urllib.error, urllib.parse, urllib.request
import pandas as pd
CKAN = "https://data.boston.gov/api/3/action"
def ckan(action, **params):
"""Any CKAN action endpoint. Plain urllib works; no auth, no headers."""
url = f"{CKAN}/{action}?" + urllib.parse.urlencode(params)
with urllib.request.urlopen(url, timeout=300) as r:
return json.load(r)["result"]
def sql(query):
"""Server-side SQL over the DataStore. Warns when the 32,000-row cap clips."""
res = ckan("datastore_search_sql", sql=query)
if res.get("records_truncated"):
print("WARNING: clipped at the 32,000-row cap; aggregate or page with OFFSET")
return pd.DataFrame(res["records"])
PERMITS = "6ddcd912-32a0-43df-9908-63574f8c7e77" # 659,934 rows, 2006 to present
# Twenty years of permitting activity and declared value by work type.
# issued_date is a real timestamp here, so date_part needs no cast.
val = "replace(replace(\"declared_valuation\", '$', ''), ',', '')::numeric"
df = sql(f'''
SELECT date_part(\'year\', "issued_date")::int AS yr,
"worktype",
count(*) AS permits,
sum({val}) AS declared_valuation
FROM "{PERMITS}"
WHERE "issued_date" IS NOT NULL
AND "declared_valuation" IS NOT NULL AND "declared_valuation" <> \'\'
GROUP BY 1, 2
''')
top = df.groupby("worktype")["permits"].sum().nlargest(8).index
print(df[df.worktype.isin(top)].pivot_table(
index="yr", columns="worktype", values="permits", aggfunc="sum").fillna(0).astype(int))Data structure
Fields
_id | int |
permitnumber | text |
worktype | text |
permittypedescr | text |
description | text |
comments | text |
applicant | text |
declared_valuation | text |
total_fees | text |
issued_date | timestamp |
expiration_date | timestamp |
status | text |
occupancytype | text |
sq_feet | numeric |
address | text |
city | text |
state | text |
zip | text |
ward | numeric |
property_id | numeric |
and 5 more
Files
One row is one approved building permit. 659,934 rows in a single DataStore resource, verified range 2006-09-26 to 2026-08-14 and refreshed daily. Unusually for this portal, the numeric and date columns are GENUINELY TYPED: issued_date and expiration_date are timestamps, and sq_feet, ward, property_id, parcel_id, gpsy, gpsx, y_latitude and x_longitude are numeric, so they need no cast. declared_valuation and total_fees are the exception and are text currency.
WHAT EACH ROW CARRIES: permitnumber; worktype (a short code such as INTEXT, ERECT, EXTREN, RAZE, INTDEM, EXTDEM, SRVCHG, FSTTRK, SOL, INSUL); permittypedescr (the human form: "Amendment to a Long Form", "Short Form Bldg Permit", "Electrical Permit", "Plumbing Permit", "Certificate of Occupancy"); description; comments (applicant free text, often carrying the amended permit number); applicant; declared_valuation; total_fees; issued_date; expiration_date; status; occupancytype; sq_feet; address, city, state, zip, ward; property_id and parcel_id; and coordinates in both Massachusetts State Plane (gpsx, gpsy) and WGS84 (x_longitude, y_latitude).
THE JOINS ARE THE POINT. parcel_id and property_id are the same identifiers used by the Property Assessment rolls (GIS_ID / PID) and by RentSmart, and parcel_id maps to MAP_PAR_ID in the 2025 parcel geometry. That chain is what turns a permit into an owner, an assessed value, a building age and a polygon on a map.
RESOURCES:
Approved Building Permits (data.boston.gov/dataset/approved-building-permits): 1 DataStore resources of 2 total
6ddcd912-32a0-43df-9908-63574f8c7e77 659934 rows Approved Building PermitsExample file: Annual declared construction value, cleaned:
SELECT date_part('year', "issued_date") AS yr, count(*) permits,
sum(replace(replace("declared_valuation", '$', ''), ',', '')::numeric) AS declared
FROM "6ddcd912-32a0-43df-9908-63574f8c7e77"
WHERE "declared_valuation" IS NOT NULL AND "decl
Sample notebook
Sample notebook for Boston Approved Building Permits, 2006 to present: worked code with the output it printed.
Analyze this dataset without downloading it
On Scigantic, Boston Approved Building Permits, 2006 to present opens in a hosted JupyterLab notebook with the data already mounted, so you can read files where they are stored instead of copying them first. Each notebook includes an AI assistant that can see the mounted files and write and run analysis code. Open the dataset page to launch a notebook, or browse the full catalog.
This page is also available as Markdown and as JSON.
Related Urban & Civic datasets
- City Safety Data: 311 and 911 Fire Calls for Five US Cities
- Boston RentSmart housing conditions by address
- OpenCUP - Italian public investment projects (Parquet mirror)
- Boston Employee Earnings Report, 2011 to 2025
- Boston Checkbook Explorer city expenditures, FY2012 to present
- Boston Crime Incident Reports, 2012 to present
- Boston Property Assessment Rolls, FY2004 to FY2026
- Boston Police Field Interrogation and Observation (FIO) records, 2011 to 2025