# Boston parcels and administrative boundaries (2025)

## Facts

- Provider: City of Boston (Boston Maps, Assessing Department)
- License: Open Data Commons Public Domain Dedication and License (PDDL) 1.0
- Format: Parquet (in sampled files)
- Stored at: Amazon S3, s3://scigantic-boston-open-data/parcels-boundaries (us-east-1)
- Access: public, readable without an account
- Category: Earth Observation & Geospatial
- Source: https://data.boston.gov/dataset/parcels-2025
- Page: https://scigantic.com/archive/ebb7af17-b86a-5e8f-a3d8-b6fdd0685137
- Keywords: Earth Observation & Geospatial, Parquet, AWS Open Data

## About

The geometric base layers that every other Boston dataset joins to: the 2025 tax parcel fabric plus the administrative boundaries the city reports against. The parcel layer holds 98,829 parcels created by the Assessing Department, with MAP_PAR_ID and LOC_ID identifiers, polygon type (FEE, ROW and others), map number, source, a town id and edit provenance. The boundary layers are Boston's 26 BPDA neighborhoods, 22 wards, 9 city council districts for the 2023 to 2032 cycle, and 207 census tracts from the 2020 decennial census. MAP_PAR_ID joins to GIS_ID in the Property Assessment rolls, which is the documented route from a polygon on a map to an owner, an assessed value and a building's physical attributes, and from there to permits, violations, RentSmart conditions and BERDO emissions, all of which carry the same parcel identifier. The neighborhood, ward and council district layers are what turn point-level 311, crime, crash and fire records into rates per area or per capita. The schema card documents the trap that makes the parcel layer look broken on first contact: the CSV resource that CKAN loads into the DataStore, and that a query-first workflow naturally reaches for, has a shape_wkt column that is null for every row, so the CSV carries the parcel attributes but no geometry at all. The geometry lives only in the separate GeoJSON and Shapefile downloads, and the resource CKAN labels 'GeoJSON' is in fact a zip archive named parcels_2025_geojson.zip rather than a plain .geojson file, so it must be read through a zip path rather than handed straight to a GeoJSON reader. The boundary layers, by contrast, are served as genuine unzipped .geojson files that load directly. Published by Boston Maps, the Assessing Department and the Planning Department under PDDL 1.0. This archive is served from a Scigantic mirror rather than live from the portal: s3://scigantic-boston-open-data/parcels-boundaries/ carries a byte-verbatim copy of every parcel and boundary resource under raw/, including the GeoJSON, Shapefile and KML geometry the CKAN DataStore does not hold, FUSE-mounted read-only at ~/archive. The zipped parcel GeoJSON is mirrored as-is, so geopandas still reads it through a zip path.

## Load the data

```python
import os
import pandas as pd
df = pd.read_csv(os.path.join(os.environ['SCIGANTIC_MOUNT_PATH'], 'raw/parcels_2025.csv'), nrows=1000)
df.head()
```

Run in a Scigantic notebook on 2026-09-14 against `raw/parcels_2025.csv`: CSV/TSV: columns ['\ufeffMAP_PAR_ID', 'LOC_ID', 'POLY_TYPE', 'MAP_NO', 'SOURCE', 'PLAN_ID', 'BND_CHK', 'NO_MATCH', 'TOWN_ID', 'last_edited_date', 'created_user', 'created_date'], dtypes ['int64', 'object', 'object', 'int64', 'object', 'float64', 'float64', 'object', 'int64', 'object', 'float64', 'fl.

From any machine:

```python
import boto3
from botocore import UNSIGNED
from botocore.client import Config
s3 = boto3.client('s3', region_name='us-east-1', config=Config(signature_version=UNSIGNED))
s3.list_objects_v2(Bucket='scigantic-boston-open-data', Prefix='parcels-boundaries/', Delimiter='/')
```

Lists the files with anonymous access. Runs on any machine, with no cloud account.

## Data structure

File types in sampled files: Parquet

Example file: `parcels-boundaries/parquet/boston_neighborhood_boundaries.parquet`

## Open it

- In a hosted notebook with the data mounted: https://scigantic.com/archive/ebb7af17-b86a-5e8f-a3d8-b6fdd0685137
- Full record as JSON (schema card included): https://api.scigantic.com/api/archives/ebb7af17-b86a-5e8f-a3d8-b6fdd0685137
- Over MCP: `get_schema_card` with id `ebb7af17-b86a-5e8f-a3d8-b6fdd0685137` at https://api.scigantic.com/mcp

## Related topics

- [Earth Observation & Geospatial datasets](https://scigantic.com/topics/earth-observation-and-geospatial)
- [Parquet datasets](https://scigantic.com/topics/parquet)
