Do I need an account with Cambridge MA Open Data?

No. The data is public, so there is nothing to sign up for and nothing to paste in.

How fresh is the data?

As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.

Will running it again create duplicate rows?

No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.

Do I need to write code?

No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

Cambridge MA Open Data

Public data

Ready to useNo account needed

Cambridge MA Open Data data, published as Cambridge MA Open Data publishes it. Ingest delivers this data to a data warehouse you own as 21 tables, and updates it on the schedule you choose. There is no code to write and nothing to install.

154,824rows as of October 2026
About 540new rows a week
21 tablesin your warehouse

What you get

Table	Each row is
building_permits_alterations `building_permits_alterations`	Building permits for additions and alterations since 2018: address, status, submit and issue dates, the work described, cost estimates by trade, and the reviews required. Applicant, licensed contractor and firm names land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
building_permits_new_construction `building_permits_new_construction`	Building permits for new construction since 2018: address, status, submit and issue dates, proposed use, dwelling units, parking, cost estimates and the reviews required. The city publishes a permit once per matched address point, so a permit id can appear on more than one row. Applicant, architect and licensed contractor names and the contractor's license number land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
certificates_of_occupancy `certificates_of_occupancy`	Certificates of occupancy issued by Inspectional Services since 2018: address and location, status, submit and issue dates, certificate type, building use, residential units, gross floor area, parking, inspection dates and the fire safety features listed. id is missing on a few rows from 2020. Applicant and business names land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
contracts `contracts`	City contracts from the Purchasing Department: vendor, title, contract and requisition ids, term, status, start and end dates, renewals, department and type. Times are Cambridge local time, published without a time zone. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
crash_log `crash_log`	Cambridge Police Department crash log: one row per reported motor vehicle crash since 2016, with the intersection or address, neighborhood, and the motorists, cyclists, pedestrians, injuries and hospitalizations involved. The city publishes those counts as decimals (1.0), so they are stored as double. Times are Cambridge local time, published without a time zone. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
demolition_permits `demolition_permits`	Demolition permits since 2018: address, status, submit and issue dates, project dates, stories, units demolished, cost and debris removal. debris_removal_date is text, exactly as published, because a row carries an impossible year. Applicant names and license numbers land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
development_log `development_log`	The current edition of the city's Development Log, from the Community Development Department: one row per large development project, from permitting through construction to completion in the current calendar year, with address, project name and description, developer, status, year complete, project and permit type, zoning, floor area, primary use, residential and affordable units, hotel rooms and parking spaces. The city replaces the edition each quarter in this same dataset, whose title names it (2026 Q2 on 2026-10-03); projects completed in earlier years are in a separate historical dataset that this table does not read. affordable_units is published as text and is empty on most rows. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
dispatch_calls `dispatch_calls`	Computer Aided Dispatch entries for police and fire calls since 2015: type and group, priority, primary agency, address or intersection, when each call was received and closed, alarm level, police sector and route, and fire box, engine and ladder districts. The dataset carries no call or incident number. Times are Cambridge local time, published without a time zone. The city republishes the whole dataset about once a month, so each sync replaces this table with the current snapshot. By default it is read at most once every 7 days (a run that starts less than 6 days and 23.5 hours after the last complete read began reads nothing), and a setting on this table changes that. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
electrical_permits `electrical_permits`	Electrical permits since 2018: address, status, submit and issue dates, estimated value, the fixtures, outlets and equipment counted, and service details. Applicant and licensee names land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
excavation_permits `excavation_permits`	Excavation permits for street and sidewalk work since 2019: address, status, submit and issue dates, work dates, who performs the work, and the size of each street and sidewalk cut. hoisting_license_expiration is text, exactly as published, because a few rows carry impossible years. Applicant and company names and Massachusetts hoisting license numbers land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
food_establishment_permits `food_establishment_permits`	Food establishment permits since 2018, one row per permit year: business name and DBA, address and location, permit type, seats, opening hours, and the application's answers on equipment, food handling, waste and pest control. allergen_awareness and food_protection_expiration are text, exactly as published, because some rows carry impossible years. id is the establishment's permit and repeats on each yearly renewal (about four rows per id), so the row with the latest issue_date is the current permit; viewpoint_id is unique to each row. Applicant names land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
housing_code_violations `housing_code_violations`	Housing code violations cited by Inspectional Services since 2021: address, code and description, corrective action, status and case dates. id is the case and repeats once per violation. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
housing_permits `housing_permits`	Residential building permits since 1996 from the Community Development Department, limited to projects that removed or built a building or changed its number of units: project id and permit order, address, neighborhood, year and fiscal year permitted, permit type, prior and permitted use and units, net change, housing starts and a description. The year is when the permit was issued, not when the project finished. project_id repeats once per permit in a project, and project_id with permit_order is not unique either. The city updates it about twice a year. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
medical_events `medical_events`	Medical emergency calls in Cambridge since 2016: category, when each call was received and closed, and the reporting area and neighborhood. The dataset carries no call or incident number. Times are Cambridge local time, published without a time zone. The city republishes the whole dataset about once a month, so each sync replaces this table with the current snapshot. By default it is read at most once every 7 days (a run that starts less than 6 days and 23.5 hours after the last complete read began reads nothing), and a setting on this table changes that. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
participatory_budgeting `participatory_budgeting`	Participatory Budgeting final ballot projects from the Budget Department, every cycle since the first (September 2014 to April 2015): cycle and its date range, the project, its cost, descriptions and location, total votes, and whether it won (winning_project is Yes or No). pb_cycle and project together are unique today. The city adds a cycle about once a year. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
sanitary_inspections `sanitary_inspections`	Sanitary (food) inspection violations since 2021: business, address, code and description, inspector comments, status, and when the case opened, closed and was corrected. unique_identifier is the city's own row key. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing.
service_requests `service_requests`	Cambridge MA Commonwealth Connect (311) service request records.
smart_rat_boxes `smart_rat_boxes`	The city's smart rat boxes: device, address and location, whether the site is active, and rodent counts since installation, by year and by month of the current year. serial_number is not unique. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
solar_permits `solar_permits`	Solar installation permits since 2018: address and location, status, submit and issue dates, building use, the system's type and size, watt capacity, panel and inverter counts, battery storage, and cost estimates. battery_storage_capacity is true or false, not a capacity. Solar thermal permits carry no photovoltaic figures. Applicant, authorized agent and firm names land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
street_occupancy_permits `street_occupancy_permits`	Street occupancy permits since 2020, all eight types the city issues in one table (moving van, special event, tool truck, moving container, other street occupancy, funeral and wake parking, traffic clearance, block party): address, status, issue date, days, parking meters and spaces affected. A permit id can appear on more than one row, notably for special events. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.
tow_log `tow_log`	Vehicles towed in Cambridge since 2015: classification, location, when the vehicle was towed, its state, year, make, model and color, the towing company and the reason. trackingnumber is not unique (about a quarter as many distinct values as rows). Times are Cambridge local time, published without a time zone. The city republishes the whole dataset about once a month, so each sync replaces this table with the current snapshot. By default it is read at most once every 7 days (a run that starts less than 6 days and 23.5 hours after the last complete read began reads nothing), and a setting on this table changes that. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.

How it works

Choose Cambridge MA Open Data. The data is public, so there is nothing to sign in to.
Pick where it goes. BigQuery, Snowflake, Databricks, Redshift and 10 more, in an account you own.
Pick a schedule. Daily is the default, and weekly and monthly are there too.
Ingest runs it from then on. If a run fails, your dashboard shows which table and why.

Questions

Do I need an account with Cambridge MA Open Data?: No. The data is public, so there is nothing to sign up for and nothing to paste in.
Which warehouses can Cambridge MA Open Data data go to?: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL and Snowflake, in an account you own.
How fresh is the data?: As fresh as your schedule: daily by default, or weekly or monthly. Schedules as often as every 15 minutes are on the Enterprise plan.
Will running it again create duplicate rows?: No. Each row is stored once, by its key: when a run reads a row that is already there, it replaces that copy instead of adding a second one.
Do I need to write code?: No. Ingest builds, runs and maintains the connector. Someone with access to your warehouse connects it once, following a short guide.

For your data team: technical reference

Connector cambridgema, version 0.1.0, a REST source, status beta, authentication none.

Vendor documentation: https://data.cambridgema.gov/

Configuration

No configuration required.

Resources

Resource	Status	Plan	Write	Primary key	Overrides
`building_permits_alterations` Building permits for additions and alterations since 2018: address, status, submit and issue dates, the work described, cost estimates by trade, and the reviews required. Applicant, licensed contractor and firm names land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`building_permits_new_construction` Building permits for new construction since 2018: address, status, submit and issue dates, proposed use, dwelling units, parking, cost estimates and the reviews required. The city publishes a permit once per matched address point, so a permit id can appear on more than one row. Applicant, architect and licensed contractor names and the contractor's license number land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`certificates_of_occupancy` Certificates of occupancy issued by Inspectional Services since 2018: address and location, status, submit and issue dates, certificate type, building use, residential units, gross floor area, parking, inspection dates and the fire safety features listed. id is missing on a few rows from 2020. Applicant and business names land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`contracts` City contracts from the Purchasing Department: vendor, title, contract and requisition ids, term, status, start and end dates, renewals, department and type. Times are Cambridge local time, published without a time zone. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`crash_log` Cambridge Police Department crash log: one row per reported motor vehicle crash since 2016, with the intersection or address, neighborhood, and the motorists, cyclists, pedestrians, injuries and hospitalizations involved. The city publishes those counts as decimals (1.0), so they are stored as double. Times are Cambridge local time, published without a time zone. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`demolition_permits` Demolition permits since 2018: address, status, submit and issue dates, project dates, stories, units demolished, cost and debris removal. debris_removal_date is text, exactly as published, because a row carries an impossible year. Applicant names and license numbers land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`development_log` The current edition of the city's Development Log, from the Community Development Department: one row per large development project, from permitting through construction to completion in the current calendar year, with address, project name and description, developer, status, year complete, project and permit type, zoning, floor area, primary use, residential and affordable units, hotel rooms and parking spaces. The city replaces the edition each quarter in this same dataset, whose title names it (2026 Q2 on 2026-10-03); projects completed in earlier years are in a separate historical dataset that this table does not read. affordable_units is published as text and is empty on most rows. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`dispatch_calls` Computer Aided Dispatch entries for police and fire calls since 2015: type and group, priority, primary agency, address or intersection, when each call was received and closed, alarm level, police sector and route, and fire box, engine and ladder districts. The dataset carries no call or incident number. Times are Cambridge local time, published without a time zone. The city republishes the whole dataset about once a month, so each sync replaces this table with the current snapshot. By default it is read at most once every 7 days (a run that starts less than 6 days and 23.5 hours after the last complete read began reads nothing), and a setting on this table changes that. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	staleness_days
`electrical_permits` Electrical permits since 2018: address, status, submit and issue dates, estimated value, the fixtures, outlets and equipment counted, and service details. Applicant and licensee names land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`excavation_permits` Excavation permits for street and sidewalk work since 2019: address, status, submit and issue dates, work dates, who performs the work, and the size of each street and sidewalk cut. hoisting_license_expiration is text, exactly as published, because a few rows carry impossible years. Applicant and company names and Massachusetts hoisting license numbers land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`food_establishment_permits` Food establishment permits since 2018, one row per permit year: business name and DBA, address and location, permit type, seats, opening hours, and the application's answers on equipment, food handling, waste and pest control. allergen_awareness and food_protection_expiration are text, exactly as published, because some rows carry impossible years. id is the establishment's permit and repeats on each yearly renewal (about four rows per id), so the row with the latest issue_date is the current permit; viewpoint_id is unique to each row. Applicant names land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`housing_code_violations` Housing code violations cited by Inspectional Services since 2021: address, code and description, corrective action, status and case dates. id is the case and repeats once per violation. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`housing_permits` Residential building permits since 1996 from the Community Development Department, limited to projects that removed or built a building or changed its number of units: project id and permit order, address, neighborhood, year and fiscal year permitted, permit type, prior and permitted use and units, net change, housing starts and a description. The year is when the permit was issued, not when the project finished. project_id repeats once per permit in a project, and project_id with permit_order is not unique either. The city updates it about twice a year. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`medical_events` Medical emergency calls in Cambridge since 2016: category, when each call was received and closed, and the reporting area and neighborhood. The dataset carries no call or incident number. Times are Cambridge local time, published without a time zone. The city republishes the whole dataset about once a month, so each sync replaces this table with the current snapshot. By default it is read at most once every 7 days (a run that starts less than 6 days and 23.5 hours after the last complete read began reads nothing), and a setting on this table changes that. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	staleness_days
`participatory_budgeting` Participatory Budgeting final ballot projects from the Budget Department, every cycle since the first (September 2014 to April 2015): cycle and its date range, the project, its cost, descriptions and location, total votes, and whether it won (winning_project is Yes or No). pb_cycle and project together are unique today. The city adds a cycle about once a year. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`sanitary_inspections` Sanitary (food) inspection violations since 2021: business, address, code and description, inspector comments, status, and when the case opened, closed and was corrected. unique_identifier is the city's own row key. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing.	beta	staleness	replace	`unique_identifier`	-
`service_requests` Cambridge MA Commonwealth Connect (311) service request records.	beta	watermark	merge	`ticket_id`	backfill_days
`smart_rat_boxes` The city's smart rat boxes: device, address and location, whether the site is active, and rodent counts since installation, by year and by month of the current year. serial_number is not unique. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`solar_permits` Solar installation permits since 2018: address and location, status, submit and issue dates, building use, the system's type and size, watt capacity, panel and inverter counts, battery storage, and cost estimates. battery_storage_capacity is true or false, not a capacity. Solar thermal permits carry no photovoltaic figures. Applicant, authorized agent and firm names land as the city publishes them. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`street_occupancy_permits` Street occupancy permits since 2020, all eight types the city issues in one table (moving van, special event, tool truck, moving container, other street occupancy, funeral and wake parking, traffic clearance, block party): address, status, issue date, days, parking meters and spaces affected. A permit id can appear on more than one row, notably for special events. The city republishes the whole dataset each time it updates it, so each sync replaces this table with the current snapshot. It is read at most once a day: a run that starts less than 23.5 hours after the last complete read began reads nothing. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	-
`tow_log` Vehicles towed in Cambridge since 2015: classification, location, when the vehicle was towed, its state, year, make, model and color, the towing company and the reason. trackingnumber is not unique (about a quarter as many distinct values as rows). Times are Cambridge local time, published without a time zone. The city republishes the whole dataset about once a month, so each sync replaces this table with the current snapshot. By default it is read at most once every 7 days (a run that starts less than 6 days and 23.5 hours after the last complete read began reads nothing), and a setting on this table changes that. socrata_row_id is the portal's internal row id: unique within one snapshot and reassigned whenever the city republishes, so it is not a key to join on across syncs.	beta	staleness	replace	`socrata_row_id`	staleness_days

Setting up the destination is its own short guide, one per warehouse or lake: Amazon S3, Google Cloud Storage, Azure Blob Storage, Apache Iceberg, Ingest Managed Lakehouse, MotherDuck, Postgres, Amazon Athena, Databricks, Redshift, BigQuery, ClickHouse, MySQL / generic SQL, Snowflake.

Other sources Ingest connects for government teams: Abilene TX 311, Albany NY 311, Ann Arbor MI 311, Anne Arundel County MD 311, Auburn WA 311, Aurora IL 311.

Get Cambridge MA Open Data data into your warehouse

Last updated 2026-10-16.